2001-11-09 16:29:58

by Anthony Campbell

[permalink] [raw]
Subject: Total lockup with 2.4.14

I've had 3 total lockups with kernel 2.4.12 and now one with 2.4.14.

I was online at the time, using Acroread on this occasion. No key would
work, nor would the mouse.

This doesn't seem to happen with the Alan Cox patches, so perhaps it is
something to do with VM.


--
Anthony Campbell - running Linux GNU/Debian (Windows-free zone)
For an electronic book (The Assassins of Alamut), skeptical
essays, and over 140 book reviews, go to: http://www.acampbell.org.uk/

Our planet is a lonely speck in the great enveloping cosmic dark. In our
obscurity, in all this vastness, there is no hint that help will come
from elsewhere to save us from ourselves. [Carl Sagan]




2001-11-09 20:58:02

by Mike Fedyk

[permalink] [raw]
Subject: Re: Total lockup with 2.4.14

On Fri, Nov 09, 2001 at 04:29:34PM +0000, Anthony Campbell wrote:
> I've had 3 total lockups with kernel 2.4.12 and now one with 2.4.14.
>
> I was online at the time, using Acroread on this occasion. No key would
> work, nor would the mouse.
>
> This doesn't seem to happen with the Alan Cox patches, so perhaps it is
> something to do with VM.
>

Don't assume that.

The -ac patch includes many more things than just the previous VM.

You should include the Oops, if it did oops.

Also, you should include your .config, and a "lspci -vv" of the affected
system.

Mike

2001-11-10 07:38:50

by Tommi Kyntola

[permalink] [raw]
Subject: Re: Total lockup with 2.4.14

> > I've had 3 total lockups with kernel 2.4.12 and now one with 2.4.14.
> >
> > I was online at the time, using Acroread on this occasion. No key would
> > work, nor would the mouse.
> >
> > This doesn't seem to happen with the Alan Cox patches, so perhaps it is
> > something to do with VM.
> >
>
> Don't assume that.
>
> The -ac patch includes many more things than just the previous VM.
>
> You should include the Oops, if it did oops.
>
> Also, you should include your .config, and a "lspci -vv" of the affected
> system.

It would also make sense to make sure it's in fact a kernel lock up.
>From time to time X may lock up _but_ the machine pings and you
can gain access via ssh/telnet and try to fix it by shutting down
X from there...

Tommi "Kynde" Kyntola
/* A man alone in the forest talking to himself and
no women around to hear him. Is he still wrong? */