On 08/21/2010 05:19 AM, Ben Hutchings wrote:
The kernel image in the above package contains this machine code around the address of the faulting instruction: [...] 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+.
Many thanks Ben! I've been suspecting something along these lines, but that's the best evidence I've got up to now. (I've been running memtest86 for 19h without any errors. debsums gives no errors.)
Cheers, Thiemo -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c6f8cb6.6070...@googlemail.com
