From: "Hendrik ." <chasake@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Reading a bad sector does not report failure as 'read error' but hangs PC with 'Machine Check Exception'
Date: Sun, 29 Jul 2007 11:39:50 -0700 (PDT) [thread overview]
Message-ID: <415666.7221.qm@web52004.mail.re2.yahoo.com> (raw)
In-Reply-To: <46ACB357.4030006@shaw.ca>
Probably a similar problem is described in the
linux-ide mailing list a while ago:
http://www.opensubscriber.com/message/jgarzik@pobox.com/6490911.html
>> Argh. I'm seeing a show stopper bug on sata_nv
here.
>> ata_exec_internal
>> is MCE-ing on the READ_NATIVE_MAX_EXT command on
>> both i386 and amd64, with
>> top of Linus' tree + this patch. :(
>
>Oddly, the command at least executes and doesn't MCE
>(but it's not at all
>happy either) if I use ATA_PROT_PIO. I wonder if
>ATA_PROT_NODATA is buggered on this sata_nv chip
>(Asus A8N-E).
At least it is a similar motherboard that is used
(however I have explicitly have the A8N-E Deluxe
edition).
I try not to repair my SATA disk for now with the
Seatools, so if there is some testing to be done, I
can run it with the bad disk.
Regards,
Hendrik
____________________________________________________________________________________
Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos & more.
http://mobile.yahoo.com/go?refer=1GNXIC
next prev parent reply other threads:[~2007-07-29 18:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.0jeOedb9xyA9k8S1VmCEkqHxsyw@ifi.uio.no>
2007-07-29 15:33 ` Robert Hancock
2007-07-29 16:43 ` Hendrik .
2007-07-29 20:30 ` Alan Cox
2007-07-29 21:45 ` Hendrik .
2007-07-29 22:14 ` Hendrik .
2007-07-29 18:39 ` Hendrik . [this message]
[not found] <fa.tKSW2T164UTRMvntkUO/fGg0UlM@ifi.uio.no>
[not found] ` <fa.iA7ClD7fNtxdfJ9YhG0lqougi/0@ifi.uio.no>
2007-08-01 9:42 ` Robert Hancock
2007-07-30 20:30 Hendrik .
2007-08-01 18:28 ` Phillip Susi
-- strict thread matches above, loose matches on Subject: below --
2007-07-29 15:04 Hendrik .
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=415666.7221.qm@web52004.mail.re2.yahoo.com \
--to=chasake@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome