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-next>] [day] [month] [year] [list]
Date:	Mon, 30 Jul 2007 13:30:10 -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'

After even more tests I found out the following:

- Running 'dd_rescue /dev/sda1 /dev/zero' on the
on-board Silicon Image Inc. SiI 3114 controller
handles the bad sector just fine and does not give a
MCE. This is on the same motherboard that does give
the MCE error on the Nvidia port.

The following SATA controllers are in that machine:
* IDE interface: nVidia Corporation CK804 Serial ATA
Controller (rev f3)
* RAID bus controller: Silicon Image, Inc. SiI 3114
[SATALink/SATARaid] Serial ATA Controller (rev 02)

- Running the dd_rescue command om another PC with a
different type of motherboard (M2NPV-VM) also with a
Nvidia Nforce 4 (altough different) chipset work fine
and reports the bad sector like the SiL 3114
controller on the other PC.

This PC has the following lspci listing for SATA
controller:
* IDE interface: nVidia Corporation MCP51 Serial ATA
Controller (rev a1)

So I think there is a problem with this specific CK804
ATA controller causing the MCE... Any clues?



       
____________________________________________________________________________________
Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out. 
http://answers.yahoo.com/dir/?link=list&sid=396545433
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ