> When I arrived at my machine tonight it was dead, with a nice
> panic on the screen as a greeting. On rebooting I found something
> in the logs, which is rare because it said "not syncing". So I'm
> assuming this isn't the panic that killed the box, but she
> probably knows (of) him, so let's interrogate her anyway:
>
> Unable to handle kernel paging request at virtual address 00020008
> c0139fad
> *pde = 00000000
> Oops: 0002
> CPU: 0
> EIP: 0010:[bdput+5/96]
> EFLAGS: 00010206
> eax: 00020000 ebx: 00020000 ecx: ca59a648 edx: c15ddfa4
> esi: c15ddfa4 edi: c97b9428 ebp: c15ddfac esp: c15ddf6c
inode with ->i_bdev == 0x20000. Very likely to be a one-bit memory
corruption. May be hardware, may be not - unfortunately, all we know
is that bit 18 in that word had been flipped. Whatever had done that
had no idea that word stores the pointer - that's for sure...
Check the memory - it _may_ be a hardware problem.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/