Every time we tried, we were able to reproduce it, usually it only took
two virtual consoles to burn out before the kernel paniced. Instead of the
original paragraph, it usually prints out screenfulls of junk. Sometimes
the screen even turns funky colors :).
This box is a 486SX/40. Its got a NCR scsi card, and that's about it.
There are 16 megabytes of ram, so memory should not be a problem unless
some of it is bad. I predict that this is the symtom of a bug in the
kernel, since as long as my friend has had it (month or so) it has not
crashed and has run pretty reliably. It is always possible that some
hardware is crashing it.
Idea: I'm going to try this on my 2.1.129 PPC G3. Be back in a second.
Update: None of my computers (2 Pentiums running 2.1.128 and 2.0.36 and 1
PowerPC running 2.1.129) are affected by this. That suggests that this bug
is either a hardware problem on that particular 486, only in
2.1.127, or only present with the hardware configuration of that machine.
Would anyone who has a few spare moments please see if they can generate
the same results by holding down ^D until init geys mad on each virtual
console? Thanks.
Aaron Lehmann
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/