Re: Kernel 2.2.0 on a 486DX2/66
- To: firstname.lastname@example.org
- Subject: Re: Kernel 2.2.0 on a 486DX2/66
- From: Carey Evans <email@example.com>
- Date: 01 Feb 1999 20:36:49 +1300
- Message-id: <firstname.lastname@example.org>
- In-reply-to: "Ralf G. R. Bergs"'s message of "Sat, 30 Jan 1999 11:19:55 +0100"
- References: <199901301019.LAA03153@Server.RZ.RWTH-Aachen.DE>
"Ralf G. R. Bergs" <rabe@RWTH-Aachen.DE> writes:
> This is strange -- I too had a mysterious lockup with the same symptom you
> describe, but with 2.2.0 (the release version.). I'm running a 5X86-133 (this is
> a 486 from AMD) on an ASUS PCI/I-SP3.
OK, so it might not have been the one-off I thought it was. If it
happens again I'll have to report it to linux-kernel.
I _did_ use Alt-SysRq-P to find out that it seemed to be looping in
schedule(), but didn't record anything else. This is with a Pentium
166 and a no-name motherboard.
Carey Evans http://home.clear.net.nz/pages/c.evans/
"The risk of U.S. national security resting in the hands of adults who play
with children's toys during office hours is left as an exercise to the reader."
- Bruce Martin in RISKS