On Sun, 2005-07-31 at 12:13 +0200, capsel wrote: > > This is the 2nd time I've seen this this week. > > > > Could it be a HD or memory curruption issue? > > attached output from dmesg from now working kernel - there is nothing > about buggy hardware like in 2.6.12-hardened. It is too risky now to > reboot into 2.6.12 to check dmesg one more time.
Don't see anything interesting there. > Is it possible not to have any errors about such corruption in logs? Well, if the kernel didn't have enough time to write to the logs, then it most definitely won't have it there. Kernel OOPs are most of the time one of these. -- Ow Mun Heng Gentoo/Linux on DELL D600 1.4Ghz 1.5GB RAM 98% Microsoft(tm) Free!! Neuromancer 10:07:22 up 8 days, 16:19, 5 users, load average: 1.06, 0.68, 0.70 -- [email protected] mailing list
