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