| 1 |
On Sun, Jun 10, 2018 at 19:18:25 +0000, Alan Mackenzie wrote: |
| 2 |
> Hello again, Dale. |
| 3 |
|
| 4 |
> On Sun, Jun 10, 2018 at 11:23:14 -0500, Dale wrote: |
| 5 |
|
| 6 |
> > To, OP. I was hoping you found a solution. Maybe you will at some |
| 7 |
> > point, You have certainly eliminated a lot of potential causes. I |
| 8 |
> > can't recall if you have or not, have you tried a different version of |
| 9 |
> > the kernel? In the past, I've upgraded to a new kernel and it be |
| 10 |
> > buggy. I go back to a older version until I see a new update then try |
| 11 |
> > again. Generally it works. Don't know if it was a kernel bug or just |
| 12 |
> > some stray code that something didn't like but . . . |
| 13 |
|
| 14 |
> I've been running on my (no longer quite so) new box since about last |
| 15 |
> August. I don't recall crashes from that long ago, though that could be |
| 16 |
> to do with my memory. |
| 17 |
|
| 18 |
> I've just configured and build a 4.17.0 kernel (thanks for the |
| 19 |
> suggestion!), having previously been running on 4.15.15 for quite some |
| 20 |
> time. Maybe this will help. We'll see. |
| 21 |
|
| 22 |
I was about to post saying my problem appeared solved. But not ten |
| 23 |
minutes ago, my system hung for the first time with it's 4.17.0 kernel. |
| 24 |
:-( |
| 25 |
|
| 26 |
It's annoying, and unsettling, but living with it might be the least |
| 27 |
worst option. |
| 28 |
|
| 29 |
> > Dale |
| 30 |
|
| 31 |
> > :-) :-) |
| 32 |
|
| 33 |
-- |
| 34 |
Alan Mackenzie (Nuremberg, Germany). |
Archives