From: Alan <alan@lxorguk.ukuu.org.uk>
To: Mark Lord <liml@rtr.ca>
Cc: Tejun Heo <htejun@gmail.com>, Linus Torvalds <torvalds@osdl.org>,
Jeff Garzik <jeff@garzik.org>, Andrew Morton <akpm@osdl.org>,
linux-ide@vger.kernel.org
Subject: Re: Scary Intel SATA errors..
Date: Fri, 1 Dec 2006 19:42:05 +0000 [thread overview]
Message-ID: <20061201194205.4313c508@localhost.localdomain> (raw)
In-Reply-To: <456DD08E.4050402@rtr.ca>
On Wed, 29 Nov 2006 13:25:18 -0500
Mark Lord <liml@rtr.ca> wrote:
> Mmmm.. Tejun, here's a clue for what Linus saw on his system:
>
> Right now I'm implementing support for READ/WRITE LONG commands via libata.
>
> And the ata_piix driver gets into a non-recoverable state after successfully
> doing a READ LONG command for me, a very similar state to what Linus reported.
Looks like it may in fact be a chip erratum. Turn off PPE unconditionally
and try and repeat it (if you look at ata_piix right now its turned off
for ATAPI only).
Alan
next prev parent reply other threads:[~2006-12-01 19:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 15:04 [git patches] libata fixes Jeff Garzik
2006-11-14 16:32 ` Mark Lord
2006-11-14 16:41 ` Jeff Garzik
2006-11-14 18:11 ` Mark Lord
2006-11-28 16:56 ` Scary Intel SATA errors Linus Torvalds
2006-11-29 18:25 ` Mark Lord
2006-11-29 18:42 ` Alan
2006-12-01 19:42 ` Alan [this message]
2006-11-28 17:31 ` Scary Intel SATA problem: "frozen" Linus Torvalds
2006-11-28 17:37 ` Mark Lord
2006-11-28 17:55 ` Sergei Shtylyov
2006-11-28 20:12 ` Eric D. Mudama
2006-11-28 20:36 ` Sergei Shtylyov
2006-11-29 1:12 ` Tejun Heo
2006-11-28 18:05 ` Alan
2006-11-28 18:33 ` Linus Torvalds
2006-11-28 21:03 ` Jeff Garzik
2006-11-28 21:45 ` Linus Torvalds
2006-11-28 22:18 ` Jeff Garzik
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=20061201194205.4313c508@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.