Bug#667858: linux-image-2.6.32-5-amd64: Crash in ext3 mark_inode_dirty

2012-04-07 Thread Steven Ihde
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

Bug#667858: linux-image-2.6.32-5-amd64: Crash in ext3 mark_inode_dirty

2012-04-07 Thread Ben Hutchings
On Fri, 2012-04-06 at 23:07 -0700, Steven Ihde wrote: 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,

Bug#667858: linux-image-2.6.32-5-amd64: Crash in ext3 mark_inode_dirty

2012-04-06 Thread Steven Ihde
Package: linux-2.6 Version: 2.6.32-41squeeze2 Severity: important The kernel sometimes crashes, rendering the system unresponsive. The stack trace is visible on the TV monitor connected via HDMI. The stack trace is always the same, beginning at a write system call and ending at

Bug#667858: linux-image-2.6.32-5-amd64: Crash in ext3 mark_inode_dirty

2012-04-06 Thread Ben Hutchings
On Fri, 2012-04-06 at 22:27 -0700, Steven Ihde wrote: [...] ** Tainted: PM (17) * Proprietary module has been loaded. * System experienced a machine check exception. [...] The nvidia driver probably isn't responsible, but I suggest you disable it so we can rule it out. More importantly, a