Skip to contentSkip to conversation

ATA warnings in dmesg

DISCUSSION Aaron Gyes 2 participants 4 messages Oct 18, 2005

lore
Share & tools
lore

Aaron Gyes

author
#0 lore raw

For the last few -mm releases (maybe longer, maybe it's in non-mm also) my dmesg is full of this:

ata1: translated ATA stat/err 0xb0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
ata1: translated ATA stat/err 0xb0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
ata1: translated ATA stat/err 0xb0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
ata1: translated ATA stat/err 0xb0/00 to SCSI SK/ASC/ASCQ 0xb/47/00

I've got a Western Digital Raptor 74GB, using sata-via on a K8T800 Pro. Should I be scared?

Aaron Gyes

#1 lore raw
Quoted 8 lines · Aaron Gyes

For the last few -mm releases (maybe longer, maybe it's in non-mm also) my dmesg is full of this:

ata1: translated ATA stat/err 0xb0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
ata1: translated ATA stat/err 0xb0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
ata1: translated ATA stat/err 0xb0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
ata1: translated ATA stat/err 0xb0/00 to SCSI SK/ASC/ASCQ 0xb/47/00

Quoted 6 lines

I've got a Western Digital Raptor 74GB, using sata-via on a K8T800 Pro. Should I be scared?

Aaron Gyes

I don't think you need to worry. Those messages are produced from the libata passthough code, whenever sense data has been requested...

0xb0 looks like a SMART command, so I would guess (haven't looked at -mm) that the ata ioctl handlers have been updated to request it.

Regards,
Jon.

______________________________________________________________
Email via Mailtraq4Free from Enstar (www.mailtraqdirect.co.uk)

author
#2 lore raw
Quoted 5 lines · Jon Escombe

I don't think you need to worry. Those messages are produced from the libata passthough code, whenever sense data has been requested...

0xb0 looks like a SMART command, so I would guess (haven't looked at -mm) that the ata ioctl handlers have been updated to request it.

That would make sense. I have a daemon running that requests the temperature via SMART every minute or so. Even still, this fills up my entire dmesg after not a very long time, can I turn these messages off somehow? If not, can you point me to where in the code I could kill a printk?

Aaron Gyes

#3 lore raw
Quoted 8 lines · Aaron Gyes
Quoted 4 lines · Jon Escombe

I don't think you need to worry. Those messages are produced from the libata passthough code, whenever sense data has been requested...

0xb0 looks like a SMART command, so I would guess (haven't looked at -mm) that the ata ioctl handlers have been updated to request it.

Quoted 7 lines

That would make sense. I have a daemon running that requests the temperature via SMART every minute or so. Even still, this fills up my entire dmesg after not a very long time, can I turn these messages off somehow? If not, can you point me to where in the code I could kill a printk?

Aaron Gyes

Sure, the printk is in drivers/scsi/libata-scsi.c, right at the end of ata_to_sense_error()..

Regards,
Jon.

______________________________________________________________
Email via Mailtraq4Free from Enstar (www.mailtraqdirect.co.uk)