From: Bruce Allen <ballen@gravity.phys.uwm.edu>
To: Jeff Garzik <jeff@garzik.org>,
Kai Makisara <Kai.Makisara@kolumbus.fi>,
Douglas Gilbert <dougg@torque.net>
Cc: Mark Lord <liml@rtr.ca>, David Greaves <david@dgreaves.com>,
Tejun Heo <htejun@gmail.com>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jan Dvorak <fermentol@gmail.com>,
Klaus Fuerstberger <kfuerstberger@arcor.de>,
Bruce Allen <bruce.allen@aei.mpg.de>,
Robert Hancock <hancockr@shaw.ca>
Subject: Re: SMART problems in 2.6.22
Date: Tue, 10 Jul 2007 20:31:11 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.63.0707102024300.4142@trinity.phys.uwm.edu> (raw)
In-Reply-To: <469309FA.6040501@torque.net>
On Tue, 10 Jul 2007, Douglas Gilbert wrote:
> Kai Makisara wrote:
>> I have done some more debugging on this one. An easy way to reproduce
>> the
<SNIP>
>> The log shows that the sense data returned by the commands differ: with
>> 2.6.22 the bytes 4f and 2c (tf.lbam and tf.lbah) are not returned. Both
>> of the status commands fail to return these bytes but the tests in
>> smartctl are more strict for the second case. This is why the second
>> status command seems to be failing.
<SNIP>
> Kai, Thanks for the analysis.
<SNIP>
> So when smartmontools sees 0 and 0 in those positions it pulls out the
> red card for that device. My guess is that libata in lk 2.6.22 is
> corrupting those FIS device to host register values.
Kai, Doug: thank you very much for tracking down the source of this
problem.
Jeff: OK, from what I am reading here I think that this is a genuine
libata/kernel bug. But I'm out of my depth here, so the ball is in your
court. Hopefully you'll understand what's going on and how to fix it.
Cheers,
Bruce
next prev parent reply other threads:[~2007-07-11 1:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 0:32 Bruce Allen
2007-07-09 1:14 ` Bruce Allen
2007-07-09 2:09 ` Jeff Garzik
2007-07-09 17:35 ` Bruce Allen
2007-07-09 17:52 ` Jeff Garzik
2007-07-09 18:02 ` Bruce Allen
2007-07-09 23:35 ` [smartmontools-support] " Adam Spiers
2007-07-10 18:22 ` Mark Lord
2007-07-09 11:55 ` David Greaves
2007-07-09 17:56 ` Bruce Allen
2007-07-09 18:00 ` David Greaves
2007-07-09 18:43 ` Jeff Garzik
2007-07-09 21:11 ` Kai Makisara
2007-07-10 4:24 ` Douglas Gilbert
2007-07-11 1:31 ` Bruce Allen [this message]
2007-07-16 10:48 ` Kai Makisara
2007-07-16 11:22 ` Tejun Heo
2007-07-16 11:58 ` Kai Makisara
2007-07-16 13:12 ` Klaus Fuerstberger
2007-07-16 21:27 ` Bruce Allen
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=Pine.LNX.4.63.0707102024300.4142@trinity.phys.uwm.edu \
--to=ballen@gravity.phys.uwm.edu \
--cc=Kai.Makisara@kolumbus.fi \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bruce.allen@aei.mpg.de \
--cc=david@dgreaves.com \
--cc=dougg@torque.net \
--cc=fermentol@gmail.com \
--cc=hancockr@shaw.ca \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=kfuerstberger@arcor.de \
--cc=liml@rtr.ca \
--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
all inboxes | Powered by JetHome®