On Apr 6, 2012, at 10:51 PM, Ben Hutchings wrote: > More importantly, a machine check exception (MCE) indicates faulty > hardware - this could be the processor, motherboard, memory (if it has > ECC) or even an expansion card. Whatever it is, that is quite likely to > be the cause of the problem and must be fixed before we do any > investigation of software. You should find some record of the MCE in > the kernel log which may provide a hint as to what is faulty.
Thanks for responding. /var/log/mcelog contains a few cycles of thermal events (like below), but nothing since Feb. 3. The most recent crash was yesterday morning. Is the mention of MCE generated by reportbug talking about this thermal event, or does that mean there is something more recent that's not showing up in /var/log/mcelog? $ ls -l /var/log/mcelog -rw-r--r-- 1 root root 23569 Feb 3 08:15 /var/log/mcelog $ tail /var/log/mcelog MCE 0 HARDWARE ERROR. This is *NOT* a software problem! Please contact your hardware vendor CPU 1 THERMAL EVENT TSC 11634544f0 Processor core is above trip temperature. Throttling enabled. STATUS 3 MCGSTATUS 0 MCE 1 HARDWARE ERROR. This is *NOT* a software problem! Please contact your hardware vendor CPU 1 THERMAL EVENT TSC 11636e2d01 Processor core below trip temperature. Throttling disabled STATUS 2 MCGSTATUS 0 -- 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/1e6633af-ba43-4d16-a514-5b85af0cd...@x2.hamachi.us
