On Sun, Jun 10, 2018 at 19:18:25 +0000, Alan Mackenzie wrote:
> Hello again, Dale.

> On Sun, Jun 10, 2018 at 11:23:14 -0500, Dale wrote:

> > To, OP.  I was hoping you found a solution.  Maybe you will at some
> > point,  You have certainly eliminated a lot of potential causes.  I
> > can't recall if you have or not, have you tried a different version of
> > the kernel?  In the past, I've upgraded to a new kernel and it be
> > buggy.  I go back to a older version until I see a new update then try
> > again.  Generally it works.  Don't know if it was a kernel bug or just
> > some stray code that something didn't like but . . .

> I've been running on my (no longer quite so) new box since about last
> August.  I don't recall crashes from that long ago, though that could be
> to do with my memory.

> I've just configured and build a 4.17.0 kernel (thanks for the
> suggestion!), having previously been running on 4.15.15 for quite some
> time.  Maybe this will help.  We'll see.

I was about to post saying my problem appeared solved.  But not ten
minutes ago, my system hung for the first time with it's 4.17.0 kernel.
:-(

It's annoying, and unsettling, but living with it might be the least
worst option.

> > Dale

> > :-)  :-) 

-- 
Alan Mackenzie (Nuremberg, Germany).

Reply via email to