My own linux kernel testing experience tells that the first thing to do after kernel oops is memtest86. Bad memory may or may not be the case, but anyway narrowing down the source of problem is a good thing.
Jeff Breidenbach wrote:
Mail-Archive went down this morning arond 6am Pacific time and was offline for several hours. When I eventually noticed, I went over to the facility to poke around. The computer had crashed, with a nice "OOPS" message from the linux kernel that looked to me like a null pointer in the virtual memory subsystem. Not that impressive in terms of reliability - it has only been about two months since the last reboot, Things started up again just fine - I would have been just as well off remotely requesting a powercycle.
-- == kir_at_asplinux.ru == 7551596_at_ICQ == 6722750_at_sms.beemail.ru == There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies and the other is to make it so complicated that there are no obvious deficiencies. - Charles Anthony Richard Hoare
_______________________________________________ Gossip mailing list [EMAIL PROTECTED] http://www.mail-archive.com/cgi-bin/mailman/listinfo/gossip
