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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <626611.9154.qm@web52007.mail.re2.yahoo.com>
Date:	Sun, 29 Jul 2007 09:43:54 -0700 (PDT)
From:	"Hendrik ." <chasake@...oo.com>
To:	linux-kernel@...r.kernel.org
Subject: Re: Reading a bad sector does not report failure as 'read error' but hangs PC with 'Machine Check Exception'

> > HARDWARE ERROR
> > CPU 0: Machine Check Exception: 4  Bank 4:
> > b200000000070f0f
> > TSC b7d4a144d0
> > This is not a software problem!
> > Run through mcelog --ascii to decode and contact
> your
> > hardware vendor
> > Kernel panic - not syncing: Machine check
> 
> You should run this through mcelog as it suggests
> and see what it shows. 
>   The kernel should be handling this properly,
> unless the drive problem 
> is causing the controller to do something bad. Note
> that kernels 2.6.20 
> and later use ADMA mode on the nForce4 SATA
> controller whereas previous 
> versions used it essentially like a PATA controller,
> so it is not 
> surprising that the behavior is different.

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
all. If I try to redirect the output to the syslog,
nothing is in there because the computer stopped
working and did not save the log anymore.

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 (I have confirmed a bad sector on the
drive using the Seatools software from Seagate)? In my
opinion a kernel should not stop responding at all
with a bad sector on the disk. I cannot change the
controller's behavior and did all the updates there
are to make in function, but the problem is introduced
using the newer kernel series.

Perhaps nobody has tried accessing a bad SATA drive
before, to simulate such an error? If it helps I could
try a different type of motherboard to see what
happens there? (Asus M2NPV-VM)

Regards,
Hendrik

____________________________________________________________________________________
Moody friends. Drama queens. Your life? Nope! - their life, your story. Play Sims Stories at Yahoo! Games.
http://sims.yahoo.com/  
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/