Re: 2.6.7-rc1-mm1: libata flooding my log

From: Prakash K. Cheemplavam
Date: Thu Jun 03 2004 - 00:36:41 EST


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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/