From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Greaves Subject: Re: LibPATA code issues / 2.6.15.4 Date: Tue, 21 Mar 2006 18:11:59 +0000 Message-ID: <442041EF.7030107@dgreaves.com> References: <43F2050B.8020006@dgreaves.com> <200602141300.37118.lkml@rtr.ca> <440040B4.8030808@dgreaves.com> <440083B4.3030307@rtr.ca> <4400A1BF.7020109@rtr.ca> <4400B439.8050202@dgreaves.com> <4401122A.3010908@rtr.ca> <44017B4B.3030900@dgreaves.com> <4401B560.40702@rtr.ca> <4403704E.4090109@rtr.ca> <4403A84C.6010804@gmail.com> <4403CEA9.4080603@rtr.ca> <44042863.2050703@dgreaves.com> <44046CE6.60803@rtr.ca> <44046D86.7050809@pobox.com> <4405DCAF.6030500@dgreaves.com> <4405DDEA.7020309@rtr.ca> <4405E42B.9040804@dgreaves.com> <4405E83D.9000906@rtr.ca> <4405EC94.2030202@dgreaves.com> <4405FAAE.3080705@dgreaves.com> <4408C729.50401@dgreaves.com> <4409A369.1040607@rtr.ca> <440BD31C.9090801@dgreaves.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from s2.ukfsn.org ([217.158.120.143]:39082 "EHLO mail.ukfsn.org") by vger.kernel.org with ESMTP id S932407AbWCUSLf (ORCPT ); Tue, 21 Mar 2006 13:11:35 -0500 In-Reply-To: <440BD31C.9090801@dgreaves.com> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Mark Lord Cc: Justin Piszcz , Jeff Garzik , Tejun Heo , linux-kernel@vger.kernel.org, IDE/ATA development list , albertcc@tw.ibm.com, axboe@suse.de, Linus Torvalds 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