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
Prakash K. Cheemplavam wrote:
> 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.
>>
So I tried something new. I enabled the SCSI error reporting and now get
this:
FAILED
status = 1, message = 00, host = 0, driver = 08
Current sd: sense key Illegal Request
Additional sense: Invalid command operation code
FAILED
status = 1, message = 00, host = 0, driver = 08
Current sd: sense key Illegal Request
Additional sense: Invalid command operation code
I found another interesting thing: It seems those errors only appear
when I use mozilla thunderbird! Any idea what tb is trying to do to the
hd? As I said earlier kernels didn't report such errors. (Are those
actually errors?)
Prakash
Prakash K. Cheemplavam wrote:
> I found another interesting thing: It seems those errors only appear
> when I use mozilla thunderbird! Any idea what tb is trying to do to the
> hd? As I said earlier kernels didn't report such errors. (Are those
> actually errors?)
I'm having similar problems (posted to linux-ide last week). Its not just
thunderbird though, I can easily reproduce this under heavy disk activity
(e.g. rsync'ing lots of data with a local server while unpacking/patching a
kernel).
Daniel
Daniel Drake wrote:
> Prakash K. Cheemplavam wrote:
>
>> I found another interesting thing: It seems those errors only appear
>> when I use mozilla thunderbird! Any idea what tb is trying to do to
>> the hd? As I said earlier kernels didn't report such errors. (Are
>> those actually errors?)
>
>
> I'm having similar problems (posted to linux-ide last week). Its not
> just thunderbird though, I can easily reproduce this under heavy disk
> activity (e.g. rsync'ing lots of data with a local server while
> unpacking/patching a kernel).
>
I seems 2.6.7-rc2-mm2 fixed the issue. At least since 2h no entry in my
logs. Well done, Jeff (if it was you :-)).
Prakash