> How can I do this? I have installed mcelog but I > cannot run it after the MCE error because the whole PC > hangs. If I try it after a reboot with 'mcelog --k8 > --ascii' or whatever parameter, there is no output at You could type error back in from the email ? > Isn't it strange to say that the controller does > something bad if there is just a bad sector on the > drive that is reported and handled correctly in an > older kernel Not really. Its very strange it gives an MCE at all but this is a known failure path (and should be a fixed known failure path) for the Nvidia SATA. - 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/
- Follow-Ups:
- Re: Reading a bad sector does not report failure as 'read error' but hangs PC with 'Machine Check Exception'
- From: "Hendrik ." <chasake@yahoo.com>
- Re: Reading a bad sector does not report failure as 'read error' but hangs PC with 'Machine Check Exception'
- From: "Hendrik ." <chasake@yahoo.com>
- Re: Reading a bad sector does not report failure as 'read error' but hangs PC with 'Machine Check Exception'
- References:
- Re: Reading a bad sector does not report failure as 'read error' but hangs PC with 'Machine Check Exception'
- From: Robert Hancock <hancockr@shaw.ca>
- Re: Reading a bad sector does not report failure as 'read error' but hangs PC with 'Machine Check Exception'
- From: "Hendrik ." <chasake@yahoo.com>
- Re: Reading a bad sector does not report failure as 'read error' but hangs PC with 'Machine Check Exception'
- Prev by Date: Re: RFT: updatedb "morning after" problem [was: Re: -mm merge plans for 2.6.23]
- Next by Date: Re: RFT: updatedb "morning after" problem [was: Re: -mm merge plans for 2.6.23]
- Previous by thread: Re: Reading a bad sector does not report failure as 'read error' but hangs PC with 'Machine Check Exception'
- Next by thread: Re: Reading a bad sector does not report failure as 'read error' but hangs PC with 'Machine Check Exception'
- Index(es):
![]() |