Re: Reading a bad sector does not report failure as 'read error' but hangs PC with 'Machine Check Exception'

["Hendrik ." <chasake@yahoo.com>]

Ok, I did actually not copy the coreret code in the
mcelog, leaving me some errors about the Northbridge.
If I do it again it gives me something else. I made 2
digital photo's of 2 lockups when it happened and this
is the result of the tool, the TSC is different in
both errors, the rest is the same:

--------------------
CPU 0 4 northbridge TSC b7d4a144d0 
  Northbridge Watchdog error
       bit57 = processor context corrupt
       bit61 = error uncorrected
  bus error 'generic participation, request timed out
      generic error mem transaction
      generic access, level generic'
STATUS b200000000070f0f MCGSTATUS 4
This is not a software problem!
--------------------
CPU 0 4 northbridge TSC c4dd3a549f 
  Northbridge Watchdog error
       bit57 = processor context corrupt
       bit61 = error uncorrected
  bus error 'generic participation, request timed out
      generic error mem transaction
      generic access, level generic'
STATUS b200000000070f0f MCGSTATUS 4
This is not a software problem!
--------------------

It's a bit strange but if I copy the results from my
first post I get the Northbridge error, perhaps
because there is an 'enter' between the first line
with the 'bank 4' and the 'b200000000070f0f' line. The
mcelog tool handles this different from the error in 1
line. 

Regards,
Hendrik


       
____________________________________________________________________________________
Got a little couch potato? 
Check out fun summer activities for kids.
http://search.yahoo.com/search?fr=oni_on_mail&p=summer+activities+for+kids&cs=bz 
-
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/