Follow up? LibPATA code issues / 2.6.15.4 (found the opcode=0x35)!

From: Justin Piszcz
Date: Mon Jul 10 2006 - 09:57:44 EST


Any follow up now that we have the failed ata-translated op codes?

On Sun, 9 Jul 2006, Justin Piszcz wrote:

[4294810.556000] ata_gen_ata_desc_sense: failed ata_op=0x51
[4294810.556000] ata4: status=0x51 { DriveReady SeekComplete Error }
[4294810.556000] ata4: error=0x04 { DriveStatusError }
[4295514.668000] ata_gen_fixed_sense: failed ata_op=0x35
[4295514.668000] ata3: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
[4295514.668000] ata_gen_ata_desc_sense: failed ata_op=0x51
[4295514.668000] ata3: status=0x51 { DriveReady SeekComplete Error }
[4295514.668000] ata3: error=0x04 { DriveStatusError }
[4297033.649000] ata_gen_fixed_sense: failed ata_op=0xca
[4297033.649000] ata4: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
[4297033.649000] ata_gen_ata_desc_sense: failed ata_op=0x51
[4297033.649000] ata4: status=0x51 { DriveReady SeekComplete Error }
[4297033.649000] ata4: error=0x04 { DriveStatusError }
[4297741.057000] ata_gen_fixed_sense: failed ata_op=0x35
[4297741.057000] ata4: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
[4297741.057000] ata_gen_ata_desc_sense: failed ata_op=0x51
[4297741.057000] ata4: status=0x51 { DriveReady SeekComplete Error }
[4297741.057000] ata4: error=0x04 { DriveStatusError }

Also got a 0xca.


On Sun, 9 Jul 2006, Justin Piszcz wrote:



On Sun, 9 Jul 2006, Justin Piszcz wrote:



On Sun, 9 Jul 2006, Justin Piszcz wrote:

I made my own patch (following Mark's example) but also added that printk in that function.

Jul 9 16:37:52 p34 kernel: [4294810.556000] ata_gen_fixed_sense: failed ata_op=0x35
Jul 9 16:37:52 p34 kernel: [4294810.556000] ata4: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
Jul 9 16:37:52 p34 kernel: [4294810.556000] ata_gen_ata_desc_sense: failed ata_op=0x51
Jul 9 16:37:52 p34 kernel: [4294810.556000] ata4: status=0x51 { DriveReady SeekComplete Error }
Jul 9 16:37:52 p34 kernel: [4294810.556000] ata4: error=0x04 { DriveStatusError }

Now that we have found the ata_op code of 0x35, what does this mean? Is it generated from a bad FUA/unsupported command from the kernel/SATA driver?

Justin.

-
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/


In /usr/src/linux/include/linux/ata.h:

ATA_CMD_WRITE_EXT = 0x35,

Perhaps these drives do not support this command or do not support it properly?

Any idea, Jeff/Alan?

Justin.



Here are all the errors (when reading/writing heavily):

[4294810.556000] ata_gen_fixed_sense: failed ata_op=0x35
[4294810.556000] ata4: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
[4294810.556000] ata_gen_ata_desc_sense: failed ata_op=0x51
[4294810.556000] ata4: status=0x51 { DriveReady SeekComplete Error }
[4294810.556000] ata4: error=0x04 { DriveStatusError }
[4295514.668000] ata_gen_fixed_sense: failed ata_op=0x35
[4295514.668000] ata3: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
[4295514.668000] ata_gen_ata_desc_sense: failed ata_op=0x51
[4295514.668000] ata3: status=0x51 { DriveReady SeekComplete Error }
[4295514.668000] ata3: error=0x04 { DriveStatusError }

Jeff/Mark, from these errors can we reach a consensus as to the cause of these errors and how to eliminate the problem?

Thanks,

Justin.


-
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/