On Sat, 2010-08-21 at 01:00 +0200, Thiemo Nagel wrote:
> Package: linux-2.6
> Version: 2.6.32-18
> Severity: normal
>
> this killed my X:
[...]
> [101389.218478] EIP: 0060:[<c10bd1ab>] EFLAGS: 00213293 CPU: 0
> [101389.218487] EIP is at do_vfs_ioctl+0x3ad/0x4e5
[...]
> [101389.218641] Code: f2 ff ff ff e9 31 01 00 00 8b 40 0c 8b 58 10 e8
> 26 e3 1a 00 8b 83 a4 00 00 00 8b 4c 24 58 8b 40 0c e8 b7 d1 72 00 e9
> fd 00 00 3d <8b> 80 0c 8b 70 10 0f b7 46 72 25 00 f0 00 00 3d 00 80 00
> 00 0f
[...]
The kernel image in the above package contains this machine code around
the address of the faulting instruction:
f2 ff ff ff e9 31 01 00 00 8b 40 0c 8b 58 10 e8
26 e3 1a 00 8b 83 a4 00 00 00 8b 4c 24 58 8b 40 0c e8 46 d1 07 00 e9
fd 00 00 00 <8b> 43 0c 8b 70 10 0f b7 46 72 25 00 f0 00 00 3d 00 80 00
00 0f
Notice that several bytes around the faulting instruction (<8b>) differ
from this in the recorded 'oops'. This indicates memory or filesystem
corruption, possibly due to a hardware fault. You should check the
integrity of the package on disk using debsums, and you can check the
system RAM with memtest86+.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
Attachment:
signature.asc
Description: This is a digitally signed message part