From: "Prakash K. Cheemplavam" <PrakashKC@gmx.de>
To: unlisted-recipients:; (no To-header on input)
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.7-rc1-mm1: libata flooding my log
Date: Wed, 02 Jun 2004 10:10:34 +0200 [thread overview]
Message-ID: <40BD8B7A.2010901@gmx.de> (raw)
In-Reply-To: <40B8F601.2000600@gmx.de>
Prakash K. Cheemplavam wrote:
> Jeff Garzik wrote:
>
>> Prakash K. Cheemplavam wrote:
>>
> [snip]
>
>>> 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
>>>
>>>
>>
>
>
>>
>> I wonder if you have a bad SATA cable, initially, though.
>
>
> I don't think so, because previous mm kernels didn't show anything like
> this.
>
I tried again a 2.6.6 based mm kernel and all is OK. Furthermore I am
not the only one getting these messages with the 2.6.7-rcX mm kernels.
Any idea? I tried to copy the older libata to the new kernel, but didn't
work as I got a compilation failure...
Prakash
next prev parent reply other threads:[~2004-06-02 8:10 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
2004-05-29 20:43 ` Prakash K. Cheemplavam
2004-06-02 8:10 ` Prakash K. Cheemplavam [this message]
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=40BD8B7A.2010901@gmx.de \
--to=prakashkc@gmx.de \
--cc=jgarzik@pobox.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