From: Jeff Garzik <jgarzik@pobox.com>
To: "Prakash K. Cheemplavam" <PrakashKC@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.7-rc1-mm1: libata flooding my log
Date: Sat, 29 May 2004 15:56:55 -0400 [thread overview]
Message-ID: <40B8EB07.6000700@pobox.com> (raw)
In-Reply-To: <40B8E8D4.1010905@gmx.de>
Prakash K. Cheemplavam wrote:
> Hi,
>
> I noticed following messages appearing very often in my log:
>
> FAILED
> status = 1, message = 00, host = 0, driver = 08
> Current sd: sense = 70 5
> ASC=20 ASCQ= 0
> Raw sense data:0x70 0x00 0x05 0x00 0x00 0x00 0x00 0x06 0x00 0x00 0x00
> 0x00 0x20 0x00
> FAILED
> status = 1, message = 00, host = 0, driver = 08
> Current sd: sense = 70 5
> ASC=20 ASCQ= 0
> Raw sense data:0x70 0x00 0x05 0x00 0x00 0x00 0x00 0x06 0x00 0x00 0x00
> 0x00 0x20 0x00
> FAILED
> status = 1, message = 00, host = 0, driver = 08
> Current sd: sense = 70 5
> ASC=20 ASCQ= 0
> Raw sense data:0x70 0x00 0x05 0x00 0x00 0x00 0x00 0x06 0x00 0x00 0x00
> 0x00 0x20 0x00
> FAILED
> status = 1, message = 00, host = 0, driver = 08
> Current sd: sense = 70 5
> ASC=20 ASCQ= 0
> Raw sense data:0x70 0x00 0x05 0x00 0x00 0x00 0x00 0x06 0x00 0x00 0x00
> 0x00 0x20 0x00
> FAILED
> status = 1, message = 00, host = 0, driver = 08
> Current sd: sense = 70 5
> ASC=20 ASCQ= 0
> Raw sense data:0x70 0x00 0x05 0x00 0x00 0x00 0x00 0x06 0x00 0x00 0x00
> 0x00 0x20 0x00
> FAILED
> status = 1, message = 00, host = 0, driver = 08
> Current sd: sense = 70 5
> ASC=20 ASCQ= 0
> Raw sense data:0x70 0x00 0x05 0x00 0x00 0x00 0x00 0x06 0x00 0x00 0x00
> 0x00 0x20 0x00
>
>
> Any idea of what is going on? Is dmesg output needed? The system seesm
> to behave rel normal, beside a bit performance degration, I think.
Reading REPORTING-BUGS for the info that is needed.
I wonder if you have a bad SATA cable, initially, though.
> BTW, the new libata version does two good things:
> - write back is activated
this is cosmetic, it was always activated.
> - now hdparm -t /dev/sda gives high throughoutput straight form the
> first time.
this is because Andrew Morton fixed a bug unrelated to libata :)
Jeff
next prev parent reply other threads:[~2004-05-29 19:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-29 19:47 2.6.7-rc1-mm1: libata flooding my log Prakash K. Cheemplavam
2004-05-29 19:56 ` Jeff Garzik [this message]
2004-05-29 20:43 ` Prakash K. Cheemplavam
2004-06-02 8:10 ` Prakash K. Cheemplavam
2004-06-03 5:33 ` Prakash K. Cheemplavam
2004-06-03 9:36 ` Daniel Drake
2004-06-03 11:49 ` Prakash K. Cheemplavam
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=40B8EB07.6000700@pobox.com \
--to=jgarzik@pobox.com \
--cc=PrakashKC@gmx.de \
--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