Messages in this thread | | | Date | Tue, 21 Mar 2006 18:11:59 +0000 | From | David Greaves <> | Subject | Re: LibPATA code issues / 2.6.15.4 |
| |
David Greaves wrote:
> Mark Lord wrote: > >> David Greaves wrote: >> >>> Just FYI - I'm away (in Canada) for 2 weeks so can't do any additional >>> testing until I return. >> >> >> Am I correct, in that your last test on rc5-git4 was a failure? > > It was *much* better than rc4 but it did have an error. > I *think* the problem I'm seeing is likely to be similar to the one I > orginally reported (on 2.6.15 IIRC) > Same sporadic warning/error which didn't usually trigger the > raid-boot-the-disk behaviour that the FUA code seemed to. > >> But without the "opcode" display in the error messages, >> so we have no idea exactly what caused the errors (again!)? > > Yes. I thought the/a opcode-verbose patch was in there but I guess not. > I don't have remote console access to the machine so wouldn't be able > to carry out reliable kernel tests - sorry. > Of course I'll do this as soon as I return.
Hi
Back now :)
I've upgraded to 2.6.16 and applied your verbosity patches.
I've persuaded my array to re-assemble and during the resync I got these messages
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 } ...(18mins later) ata1: no sense translation for op=0x28 cmd=0x25 status: 0x51 ata1: translated op=0x28 cmd=0x25 ATA stat/err 0x51/00 to SCSI SK/ASC/ASCQ 0x3/11/04 ata1: status=0x51 { DriveReady SeekComplete Error }
smartd is not running This did not cause the raid subsystem to boot the disk (thank goodness!)
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/
| |