* Re: LibPATA/ATA Errors Continue - Will there be a fix for this?
@ 2006-06-20 15:15 Al Boldi
2006-06-20 15:48 ` Justin Piszcz
2006-06-20 16:25 ` Mark Lord
0 siblings, 2 replies; 12+ messages in thread
From: Al Boldi @ 2006-06-20 15:15 UTC (permalink / raw)
To: linux-kernel
Justin Piszcz wrote:
> On Tue, 20 Jun 2006, Mark Lord wrote:
> > Justin Piszcz wrote:
> >> Should someone comment this code out that produces the printk()'s as
> >> these are useless information as there is no problem with the disk?
> >
> > MMm.. probably "barrier" commands that the drive doesn't like.
> > Pity those messages don't also dump the failed opcode.
> >
> >> Jun 20 03:14:20 p34 kernel: [4339456.678000] ata3: status=0x51 {
> >> DriveReady SeekComplete Error }
> >> Jun 20 03:14:20 p34 kernel: [4339456.678000] ata3: error=0x04 {
> >> DriveStatusError }
> >> Jun 20 03:36:44 p34 kernel: [4340801.772000] ata3: no sense translation
> >> for status: 0x51
> >> Jun 20 03:36:44 p34 kernel: [4340801.772000] ata3: status=0x51 {
> >> DriveReady SeekComplete Error }
>
> Mark, what would be the proper direction to move towards? Is Jeff or
> another SATA/ATA maintainer going to have to look at this or is there
> something else I can do, or?
I once sent a patch to -mm:
Mark Lord wrote:
> Al Boldi wrote:
>> Also apply this one to get rid of this message:
>>
>> hdb: set_drive_speed_status: status=0x40 { DriveReady }
>> ide: failed opcode was: unknown
>>
>> Maybe someone on the ide list can comment on this first though.
>>
>> --- 16/include/linux/ide.h.orig 2006-03-31 19:12:51.000000000 +0300
>> +++ 16/include/linux/ide.h 2006-04-23 13:06:32.000000000 +0300
>> @@ -120,7 +120,7 @@ typedef unsigned char byte; /* used ever
>> #define IDE_BCOUNTL_REG IDE_LCYL_REG
>> #define IDE_BCOUNTH_REG IDE_HCYL_REG
>>
>> -#define OK_STAT(stat,good,bad) (((stat)&((good)|(bad)))==(good))
>> +#define OK_STAT(stat,good,bad) (((stat)&((good)|(bad)))==((stat)&(good)))
>> #define BAD_R_STAT (BUSY_STAT | ERR_STAT)
>> #define BAD_W_STAT (BAD_R_STAT | WRERR_STAT)
>> #define BAD_STAT (BAD_R_STAT | DRQ_STAT)
>
> Assuming hdb is a CDROM/optical drive, then this change makes sense for
> that. But I don't think it is a valid (good) change for regular ATA disks.
>
> A more complex patch is required, one which correctly handles each drive
> type.
Thanks!
--
Al
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: LibPATA/ATA Errors Continue - Will there be a fix for this?
2006-06-20 15:15 LibPATA/ATA Errors Continue - Will there be a fix for this? Al Boldi
@ 2006-06-20 15:48 ` Justin Piszcz
2006-06-20 16:25 ` Mark Lord
1 sibling, 0 replies; 12+ messages in thread
From: Justin Piszcz @ 2006-06-20 15:48 UTC (permalink / raw)
To: Al Boldi; +Cc: linux-kernel
On Tue, 20 Jun 2006, Al Boldi wrote:
> Justin Piszcz wrote:
>> On Tue, 20 Jun 2006, Mark Lord wrote:
>>> Justin Piszcz wrote:
>>>> Should someone comment this code out that produces the printk()'s as
>>>> these are useless information as there is no problem with the disk?
>>>
>>> MMm.. probably "barrier" commands that the drive doesn't like.
>>> Pity those messages don't also dump the failed opcode.
>>>
>>>> Jun 20 03:14:20 p34 kernel: [4339456.678000] ata3: status=0x51 {
>>>> DriveReady SeekComplete Error }
>>>> Jun 20 03:14:20 p34 kernel: [4339456.678000] ata3: error=0x04 {
>>>> DriveStatusError }
>>>> Jun 20 03:36:44 p34 kernel: [4340801.772000] ata3: no sense translation
>>>> for status: 0x51
>>>> Jun 20 03:36:44 p34 kernel: [4340801.772000] ata3: status=0x51 {
>>>> DriveReady SeekComplete Error }
>>
>> Mark, what would be the proper direction to move towards? Is Jeff or
>> another SATA/ATA maintainer going to have to look at this or is there
>> something else I can do, or?
>
> I once sent a patch to -mm:
>
> Mark Lord wrote:
>> Al Boldi wrote:
>>> Also apply this one to get rid of this message:
>>>
>>> hdb: set_drive_speed_status: status=0x40 { DriveReady }
>>> ide: failed opcode was: unknown
>>>
>>> Maybe someone on the ide list can comment on this first though.
>>>
>>> --- 16/include/linux/ide.h.orig 2006-03-31 19:12:51.000000000 +0300
>>> +++ 16/include/linux/ide.h 2006-04-23 13:06:32.000000000 +0300
>>> @@ -120,7 +120,7 @@ typedef unsigned char byte; /* used ever
>>> #define IDE_BCOUNTL_REG IDE_LCYL_REG
>>> #define IDE_BCOUNTH_REG IDE_HCYL_REG
>>>
>>> -#define OK_STAT(stat,good,bad) (((stat)&((good)|(bad)))==(good))
>>> +#define OK_STAT(stat,good,bad) (((stat)&((good)|(bad)))==((stat)&(good)))
>>> #define BAD_R_STAT (BUSY_STAT | ERR_STAT)
>>> #define BAD_W_STAT (BAD_R_STAT | WRERR_STAT)
>>> #define BAD_STAT (BAD_R_STAT | DRQ_STAT)
>>
>> Assuming hdb is a CDROM/optical drive, then this change makes sense for
>> that. But I don't think it is a valid (good) change for regular ATA disks.
>>
>> A more complex patch is required, one which correctly handles each drive
>> type.
>
> Thanks!
>
> --
> Al
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
Did the patch get applied to -mm?
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: LibPATA/ATA Errors Continue - Will there be a fix for this?
2006-06-20 15:15 LibPATA/ATA Errors Continue - Will there be a fix for this? Al Boldi
2006-06-20 15:48 ` Justin Piszcz
@ 2006-06-20 16:25 ` Mark Lord
1 sibling, 0 replies; 12+ messages in thread
From: Mark Lord @ 2006-06-20 16:25 UTC (permalink / raw)
To: Al Boldi; +Cc: linux-kernel
Al Boldi wrote:
>
> I once sent a patch to -mm:
>
..
>>> -#define OK_STAT(stat,good,bad) (((stat)&((good)|(bad)))==(good))
>>> +#define OK_STAT(stat,good,bad) (((stat)&((good)|(bad)))==((stat)&(good)))
>>> #define BAD_R_STAT (BUSY_STAT | ERR_STAT)
>>> #define BAD_W_STAT (BAD_R_STAT | WRERR_STAT)
>>> #define BAD_STAT (BAD_R_STAT | DRQ_STAT)
>> Assuming hdb is a CDROM/optical drive, then this change makes sense for
>> that. But I don't think it is a valid (good) change for regular ATA disks.
>>
>> A more complex patch is required, one which correctly handles each drive
>> type.
That patch was very ATAPI-specific, and would break other things.
It also would not correctly help anything in Justin's case.
-ml
^ permalink raw reply [flat|nested] 12+ messages in thread
* LibPATA/ATA Errors Continue - Will there be a fix for this?
@ 2006-06-20 12:17 Justin Piszcz
2006-06-20 13:01 ` Mark Lord
0 siblings, 1 reply; 12+ messages in thread
From: Justin Piszcz @ 2006-06-20 12:17 UTC (permalink / raw)
To: linux-kernel; +Cc: linux-ide, jgarzik, Mark Lord
Jeff,
I've done many RSYNCs to this disk (writing is what makes these errors
seem to occur) and I have MD5's the files on both sides, they are OK on
each side.
Should someone comment this code out that produces the printk()'s as these
are useless information as there is no problem with the disk?
Jun 20 03:14:20 p34 kernel: [4339456.678000] ata3: status=0x51 {
DriveReady SeekComplete Error }
Jun 20 03:14:20 p34 kernel: [4339456.678000] ata3: error=0x04 {
DriveStatusError }
Jun 20 03:20:27 p34 kernel: [4339823.900000] ata3: status=0x51 {
DriveReady SeekComplete Error }
Jun 20 03:20:27 p34 kernel: [4339823.900000] ata3: error=0x04 {
DriveStatusError }
Jun 20 03:36:44 p34 kernel: [4340801.772000] ata3: no sense translation
for status: 0x51
Jun 20 03:36:44 p34 kernel: [4340801.772000] ata3: status=0x51 {
DriveReady SeekComplete Error }
Jun 20 03:41:04 p34 kernel: [4341061.844000] ata3: no sense translation
for status: 0x51
Jun 20 03:41:04 p34 kernel: [4341061.844000] ata3: status=0x51 {
DriveReady SeekComplete Error }
Jun 20 03:46:27 p34 kernel: [4341384.974000] ata3: no sense translation
for status: 0x51
Jun 20 03:46:27 p34 kernel: [4341384.974000] ata3: status=0x51 {
DriveReady SeekComplete Error }
Justin.
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: LibPATA/ATA Errors Continue - Will there be a fix for this?
2006-06-20 12:17 Justin Piszcz
@ 2006-06-20 13:01 ` Mark Lord
2006-06-20 13:03 ` Justin Piszcz
2006-06-20 14:23 ` David Greaves
0 siblings, 2 replies; 12+ messages in thread
From: Mark Lord @ 2006-06-20 13:01 UTC (permalink / raw)
To: Justin Piszcz; +Cc: linux-kernel, linux-ide, jgarzik
Justin Piszcz wrote:
>
> Should someone comment this code out that produces the printk()'s as
> these are useless information as there is no problem with the disk?
MMm.. probably "barrier" commands that the drive doesn't like.
Pity those messages don't also dump the failed opcode.
> Jun 20 03:14:20 p34 kernel: [4339456.678000] ata3: status=0x51 {
> DriveReady SeekComplete Error }
> Jun 20 03:14:20 p34 kernel: [4339456.678000] ata3: error=0x04 {
> DriveStatusError }
> Jun 20 03:20:27 p34 kernel: [4339823.900000] ata3: status=0x51 {
> DriveReady SeekComplete Error }
> Jun 20 03:20:27 p34 kernel: [4339823.900000] ata3: error=0x04 {
> DriveStatusError }
> Jun 20 03:36:44 p34 kernel: [4340801.772000] ata3: no sense translation
> for status: 0x51
> Jun 20 03:36:44 p34 kernel: [4340801.772000] ata3: status=0x51 {
> DriveReady SeekComplete Error }
> Jun 20 03:41:04 p34 kernel: [4341061.844000] ata3: no sense translation
> for status: 0x51
> Jun 20 03:41:04 p34 kernel: [4341061.844000] ata3: status=0x51 {
> DriveReady SeekComplete Error }
> Jun 20 03:46:27 p34 kernel: [4341384.974000] ata3: no sense translation
> for status: 0x51
> Jun 20 03:46:27 p34 kernel: [4341384.974000] ata3: status=0x51 {
> DriveReady SeekComplete Error }
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: LibPATA/ATA Errors Continue - Will there be a fix for this?
2006-06-20 13:01 ` Mark Lord
@ 2006-06-20 13:03 ` Justin Piszcz
2006-06-20 14:23 ` David Greaves
1 sibling, 0 replies; 12+ messages in thread
From: Justin Piszcz @ 2006-06-20 13:03 UTC (permalink / raw)
To: Mark Lord; +Cc: linux-kernel, linux-ide, jgarzik
On Tue, 20 Jun 2006, Mark Lord wrote:
> Justin Piszcz wrote:
>>
>> Should someone comment this code out that produces the printk()'s as these
>> are useless information as there is no problem with the disk?
>
> MMm.. probably "barrier" commands that the drive doesn't like.
> Pity those messages don't also dump the failed opcode.
>
>> Jun 20 03:14:20 p34 kernel: [4339456.678000] ata3: status=0x51 { DriveReady
>> SeekComplete Error }
>> Jun 20 03:14:20 p34 kernel: [4339456.678000] ata3: error=0x04 {
>> DriveStatusError }
>> Jun 20 03:20:27 p34 kernel: [4339823.900000] ata3: status=0x51 { DriveReady
>> SeekComplete Error }
>> Jun 20 03:20:27 p34 kernel: [4339823.900000] ata3: error=0x04 {
>> DriveStatusError }
>> Jun 20 03:36:44 p34 kernel: [4340801.772000] ata3: no sense translation for
>> status: 0x51
>> Jun 20 03:36:44 p34 kernel: [4340801.772000] ata3: status=0x51 { DriveReady
>> SeekComplete Error }
>> Jun 20 03:41:04 p34 kernel: [4341061.844000] ata3: no sense translation for
>> status: 0x51
>> Jun 20 03:41:04 p34 kernel: [4341061.844000] ata3: status=0x51 { DriveReady
>> SeekComplete Error }
>> Jun 20 03:46:27 p34 kernel: [4341384.974000] ata3: no sense translation for
>> status: 0x51
>> Jun 20 03:46:27 p34 kernel: [4341384.974000] ata3: status=0x51 { DriveReady
>> SeekComplete Error }
>
Mark, what would be the proper direction to move towards? Is Jeff or
another SATA/ATA maintainer going to have to look at this or is there
something else I can do, or?
Justin.
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: LibPATA/ATA Errors Continue - Will there be a fix for this?
2006-06-20 13:01 ` Mark Lord
2006-06-20 13:03 ` Justin Piszcz
@ 2006-06-20 14:23 ` David Greaves
2006-06-20 15:45 ` David Greaves
1 sibling, 1 reply; 12+ messages in thread
From: David Greaves @ 2006-06-20 14:23 UTC (permalink / raw)
To: Mark Lord; +Cc: Justin Piszcz, linux-kernel, linux-ide, jgarzik
Mark Lord wrote:
> MMm.. probably "barrier" commands that the drive doesn't like.
> Pity those messages don't also dump the failed opcode.
For me:
smartctl -data -o on /dev/sda
produces this on 2.6.17-rc5
(I thought the opcode patch went into 2.6.17...)
ata1: PIO error
ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: error=0x04 { DriveStatusError }
ata1: PIO error
ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: error=0x04 { DriveStatusError }
ata1: PIO error
ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: error=0x04 { DriveStatusError }
ata1: PIO error
ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: error=0x04 { DriveStatusError }
ata1: PIO error
ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: error=0x04 { DriveStatusError }
ata1: PIO error
ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: error=0x04 { DriveStatusError }
David
>
>> Jun 20 03:14:20 p34 kernel: [4339456.678000] ata3: status=0x51 {
>> DriveReady SeekComplete Error }
>> Jun 20 03:14:20 p34 kernel: [4339456.678000] ata3: error=0x04 {
>> DriveStatusError }
>> Jun 20 03:20:27 p34 kernel: [4339823.900000] ata3: status=0x51 {
>> DriveReady SeekComplete Error }
>> Jun 20 03:20:27 p34 kernel: [4339823.900000] ata3: error=0x04 {
>> DriveStatusError }
>> Jun 20 03:36:44 p34 kernel: [4340801.772000] ata3: no sense
>> translation for status: 0x51
>> Jun 20 03:36:44 p34 kernel: [4340801.772000] ata3: status=0x51 {
>> DriveReady SeekComplete Error }
>> Jun 20 03:41:04 p34 kernel: [4341061.844000] ata3: no sense
>> translation for status: 0x51
>> Jun 20 03:41:04 p34 kernel: [4341061.844000] ata3: status=0x51 {
>> DriveReady SeekComplete Error }
>> Jun 20 03:46:27 p34 kernel: [4341384.974000] ata3: no sense
>> translation for status: 0x51
>> Jun 20 03:46:27 p34 kernel: [4341384.974000] ata3: status=0x51 {
>> DriveReady SeekComplete Error }
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: LibPATA/ATA Errors Continue - Will there be a fix for this?
2006-06-20 14:23 ` David Greaves
@ 2006-06-20 15:45 ` David Greaves
2006-06-20 15:46 ` Justin Piszcz
0 siblings, 1 reply; 12+ messages in thread
From: David Greaves @ 2006-06-20 15:45 UTC (permalink / raw)
To: Mark Lord; +Cc: Justin Piszcz, linux-kernel, linux-ide, jgarzik
[Some email archaeology later]
Back in March I was running 2.6.16 (with the opcode patch) and I sent an
email with the following info:
dmesg:
ata1: translated op=0x28 cmd=0x25 ATA stat/err 0x51/04 to SCSI
SK/ASC/ASCQ 0xb/00/00
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: error=0x04 { DriveStatusError }
Does that help with the diagnosis?
Also see my emails: SMART on SATA reporting errors?
http://marc.theaimsgroup.com/?l=linux-ide&m=113933732903205&w=2
I did reply but got no response so I assumed I was just so far off base
that I was being ignored :)
David
David Greaves wrote:
> Mark Lord wrote:
>
>> MMm.. probably "barrier" commands that the drive doesn't like.
>> Pity those messages don't also dump the failed opcode.
>>
> For me:
> smartctl -data -o on /dev/sda
> produces this on 2.6.17-rc5
>
> (I thought the opcode patch went into 2.6.17...)
>
> ata1: PIO error
> ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
> ata1: status=0x51 { DriveReady SeekComplete Error }
> ata1: error=0x04 { DriveStatusError }
> ata1: PIO error
> ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
> ata1: status=0x51 { DriveReady SeekComplete Error }
> ata1: error=0x04 { DriveStatusError }
> ata1: PIO error
> ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
> ata1: status=0x51 { DriveReady SeekComplete Error }
> ata1: error=0x04 { DriveStatusError }
> ata1: PIO error
> ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
> ata1: status=0x51 { DriveReady SeekComplete Error }
> ata1: error=0x04 { DriveStatusError }
> ata1: PIO error
> ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
> ata1: status=0x51 { DriveReady SeekComplete Error }
> ata1: error=0x04 { DriveStatusError }
> ata1: PIO error
> ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
> ata1: status=0x51 { DriveReady SeekComplete Error }
> ata1: error=0x04 { DriveStatusError }
>
> David
>
>
>>> Jun 20 03:14:20 p34 kernel: [4339456.678000] ata3: status=0x51 {
>>> DriveReady SeekComplete Error }
>>> Jun 20 03:14:20 p34 kernel: [4339456.678000] ata3: error=0x04 {
>>> DriveStatusError }
>>> Jun 20 03:20:27 p34 kernel: [4339823.900000] ata3: status=0x51 {
>>> DriveReady SeekComplete Error }
>>> Jun 20 03:20:27 p34 kernel: [4339823.900000] ata3: error=0x04 {
>>> DriveStatusError }
>>> Jun 20 03:36:44 p34 kernel: [4340801.772000] ata3: no sense
>>> translation for status: 0x51
>>> Jun 20 03:36:44 p34 kernel: [4340801.772000] ata3: status=0x51 {
>>> DriveReady SeekComplete Error }
>>> Jun 20 03:41:04 p34 kernel: [4341061.844000] ata3: no sense
>>> translation for status: 0x51
>>> Jun 20 03:41:04 p34 kernel: [4341061.844000] ata3: status=0x51 {
>>> DriveReady SeekComplete Error }
>>> Jun 20 03:46:27 p34 kernel: [4341384.974000] ata3: no sense
>>> translation for status: 0x51
>>> Jun 20 03:46:27 p34 kernel: [4341384.974000] ata3: status=0x51 {
>>> DriveReady SeekComplete Error }
>>>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
--
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: LibPATA/ATA Errors Continue - Will there be a fix for this?
2006-06-20 15:45 ` David Greaves
@ 2006-06-20 15:46 ` Justin Piszcz
2006-06-20 22:20 ` David Greaves
0 siblings, 1 reply; 12+ messages in thread
From: Justin Piszcz @ 2006-06-20 15:46 UTC (permalink / raw)
To: David Greaves; +Cc: Mark Lord, linux-kernel, linux-ide, jgarzik
Dave, what is the make/model of the drives you get errors with by the way?
On Tue, 20 Jun 2006, David Greaves wrote:
> [Some email archaeology later]
>
> Back in March I was running 2.6.16 (with the opcode patch) and I sent an
> email with the following info:
>
> dmesg:
> ata1: translated op=0x28 cmd=0x25 ATA stat/err 0x51/04 to SCSI
> SK/ASC/ASCQ 0xb/00/00
> ata1: status=0x51 { DriveReady SeekComplete Error }
> ata1: error=0x04 { DriveStatusError }
>
> Does that help with the diagnosis?
>
> Also see my emails: SMART on SATA reporting errors?
> http://marc.theaimsgroup.com/?l=linux-ide&m=113933732903205&w=2
>
> I did reply but got no response so I assumed I was just so far off base
> that I was being ignored :)
>
> David
>
> David Greaves wrote:
>> Mark Lord wrote:
>>
>>> MMm.. probably "barrier" commands that the drive doesn't like.
>>> Pity those messages don't also dump the failed opcode.
>>>
>> For me:
>> smartctl -data -o on /dev/sda
>> produces this on 2.6.17-rc5
>>
>> (I thought the opcode patch went into 2.6.17...)
>>
>> ata1: PIO error
>> ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
>> ata1: status=0x51 { DriveReady SeekComplete Error }
>> ata1: error=0x04 { DriveStatusError }
>> ata1: PIO error
>> ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
>> ata1: status=0x51 { DriveReady SeekComplete Error }
>> ata1: error=0x04 { DriveStatusError }
>> ata1: PIO error
>> ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
>> ata1: status=0x51 { DriveReady SeekComplete Error }
>> ata1: error=0x04 { DriveStatusError }
>> ata1: PIO error
>> ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
>> ata1: status=0x51 { DriveReady SeekComplete Error }
>> ata1: error=0x04 { DriveStatusError }
>> ata1: PIO error
>> ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
>> ata1: status=0x51 { DriveReady SeekComplete Error }
>> ata1: error=0x04 { DriveStatusError }
>> ata1: PIO error
>> ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
>> ata1: status=0x51 { DriveReady SeekComplete Error }
>> ata1: error=0x04 { DriveStatusError }
>>
>> David
>>
>>
>>>> Jun 20 03:14:20 p34 kernel: [4339456.678000] ata3: status=0x51 {
>>>> DriveReady SeekComplete Error }
>>>> Jun 20 03:14:20 p34 kernel: [4339456.678000] ata3: error=0x04 {
>>>> DriveStatusError }
>>>> Jun 20 03:20:27 p34 kernel: [4339823.900000] ata3: status=0x51 {
>>>> DriveReady SeekComplete Error }
>>>> Jun 20 03:20:27 p34 kernel: [4339823.900000] ata3: error=0x04 {
>>>> DriveStatusError }
>>>> Jun 20 03:36:44 p34 kernel: [4340801.772000] ata3: no sense
>>>> translation for status: 0x51
>>>> Jun 20 03:36:44 p34 kernel: [4340801.772000] ata3: status=0x51 {
>>>> DriveReady SeekComplete Error }
>>>> Jun 20 03:41:04 p34 kernel: [4341061.844000] ata3: no sense
>>>> translation for status: 0x51
>>>> Jun 20 03:41:04 p34 kernel: [4341061.844000] ata3: status=0x51 {
>>>> DriveReady SeekComplete Error }
>>>> Jun 20 03:46:27 p34 kernel: [4341384.974000] ata3: no sense
>>>> translation for status: 0x51
>>>> Jun 20 03:46:27 p34 kernel: [4341384.974000] ata3: status=0x51 {
>>>> DriveReady SeekComplete Error }
>>>>
>>
>> -
>> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>>
>
>
> --
>
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: LibPATA/ATA Errors Continue - Will there be a fix for this?
2006-06-20 15:46 ` Justin Piszcz
@ 2006-06-20 22:20 ` David Greaves
2006-06-20 22:22 ` Justin Piszcz
2006-06-21 11:39 ` Justin Piszcz
0 siblings, 2 replies; 12+ messages in thread
From: David Greaves @ 2006-06-20 22:20 UTC (permalink / raw)
To: Justin Piszcz; +Cc: Mark Lord, linux-kernel, linux-ide, jgarzik
Justin Piszcz wrote:
> Dave, what is the make/model of the drives you get errors with by the
> way?
>
> On Tue, 20 Jun 2006, David Greaves wrote:
>> [Some email archaeology later]
>>
>> Back in March I was running 2.6.16 (with the opcode patch) and I sent an
>> email with the following info:
>>
>> dmesg:
>> ata1: translated op=0x28 cmd=0x25 ATA stat/err 0x51/04 to SCSI
>> SK/ASC/ASCQ 0xb/00/00
>> ata1: status=0x51 { DriveReady SeekComplete Error }
>> ata1: error=0x04 { DriveStatusError }
Model Family: Maxtor DiamondMax 10 family
Device Model: Maxtor 6B200M0
Serial Number: B4038RRH
Firmware Version: BANC1980
this is sata_sil
Another machine has :
Device Model: SAMSUNG SP2504C
Serial Number: S09QJ10Y720963
Firmware Version: VT100-33
User Capacity: 250,059,350,016 bytes
running through sata_via
that's running 2.6.16.18 and just gives:
ata1: PIO error
ata1: status=0x50 { DriveReady SeekComplete }
David
--
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: LibPATA/ATA Errors Continue - Will there be a fix for this?
2006-06-20 22:20 ` David Greaves
@ 2006-06-20 22:22 ` Justin Piszcz
2006-06-21 11:39 ` Justin Piszcz
1 sibling, 0 replies; 12+ messages in thread
From: Justin Piszcz @ 2006-06-20 22:22 UTC (permalink / raw)
To: David Greaves; +Cc: Mark Lord, linux-kernel, linux-ide, jgarzik
On Tue, 20 Jun 2006, David Greaves wrote:
> Justin Piszcz wrote:
>> Dave, what is the make/model of the drives you get errors with by the
>> way?
>>
>> On Tue, 20 Jun 2006, David Greaves wrote:
>>> [Some email archaeology later]
>>>
>>> Back in March I was running 2.6.16 (with the opcode patch) and I sent an
>>> email with the following info:
>>>
>>> dmesg:
>>> ata1: translated op=0x28 cmd=0x25 ATA stat/err 0x51/04 to SCSI
>>> SK/ASC/ASCQ 0xb/00/00
>>> ata1: status=0x51 { DriveReady SeekComplete Error }
>>> ata1: error=0x04 { DriveStatusError }
> Model Family: Maxtor DiamondMax 10 family
> Device Model: Maxtor 6B200M0
> Serial Number: B4038RRH
> Firmware Version: BANC1980
>
> this is sata_sil
>
> Another machine has :
> Device Model: SAMSUNG SP2504C
> Serial Number: S09QJ10Y720963
> Firmware Version: VT100-33
> User Capacity: 250,059,350,016 bytes
>
> running through sata_via
>
> that's running 2.6.16.18 and just gives:
> ata1: PIO error
> ata1: status=0x50 { DriveReady SeekComplete }
>
>
> David
>
> --
>
I also use sata_sil, perhaps it is a controller-specific problem? I use a
WD WD4000KD-00N.
I also ahve that same exact samsung drive but I have it on an Intel ICH5
controller and I do not seem to get that error.
# grep PIO\ error *
#
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: LibPATA/ATA Errors Continue - Will there be a fix for this?
2006-06-20 22:20 ` David Greaves
2006-06-20 22:22 ` Justin Piszcz
@ 2006-06-21 11:39 ` Justin Piszcz
1 sibling, 0 replies; 12+ messages in thread
From: Justin Piszcz @ 2006-06-21 11:39 UTC (permalink / raw)
To: David Greaves; +Cc: Mark Lord, linux-kernel, linux-ide, jgarzik
On Tue, 20 Jun 2006, David Greaves wrote:
> Justin Piszcz wrote:
>> Dave, what is the make/model of the drives you get errors with by the
>> way?
>>
>> On Tue, 20 Jun 2006, David Greaves wrote:
>>> [Some email archaeology later]
>>>
>>> Back in March I was running 2.6.16 (with the opcode patch) and I sent an
>>> email with the following info:
>>>
>>> dmesg:
>>> ata1: translated op=0x28 cmd=0x25 ATA stat/err 0x51/04 to SCSI
>>> SK/ASC/ASCQ 0xb/00/00
>>> ata1: status=0x51 { DriveReady SeekComplete Error }
>>> ata1: error=0x04 { DriveStatusError }
> Model Family: Maxtor DiamondMax 10 family
> Device Model: Maxtor 6B200M0
> Serial Number: B4038RRH
> Firmware Version: BANC1980
>
> this is sata_sil
>
> Another machine has :
> Device Model: SAMSUNG SP2504C
> Serial Number: S09QJ10Y720963
> Firmware Version: VT100-33
> User Capacity: 250,059,350,016 bytes
>
> running through sata_via
>
> that's running 2.6.16.18 and just gives:
> ata1: PIO error
> ata1: status=0x50 { DriveReady SeekComplete }
>
>
> David
>
> --
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
What model SiL? Perhaps the kernel folk could ignore that error on our
chipset.
0000:02:03.0 RAID bus controller: Silicon Image, Inc. SiI 3112
[SATALink/SATARaid] Serial ATA Controller (rev 02)
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2006-06-21 11:39 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-06-20 15:15 LibPATA/ATA Errors Continue - Will there be a fix for this? Al Boldi
2006-06-20 15:48 ` Justin Piszcz
2006-06-20 16:25 ` Mark Lord
-- strict thread matches above, loose matches on Subject: below --
2006-06-20 12:17 Justin Piszcz
2006-06-20 13:01 ` Mark Lord
2006-06-20 13:03 ` Justin Piszcz
2006-06-20 14:23 ` David Greaves
2006-06-20 15:45 ` David Greaves
2006-06-20 15:46 ` Justin Piszcz
2006-06-20 22:20 ` David Greaves
2006-06-20 22:22 ` Justin Piszcz
2006-06-21 11:39 ` Justin Piszcz
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox