From owner-freebsd-current Mon Apr 15 6:35: 0 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailout08.sul.t-online.com (mailout08.sul.t-online.com [194.25.134.20]) by hub.freebsd.org (Postfix) with ESMTP id 273AC37B400 for ; Mon, 15 Apr 2002 06:34:55 -0700 (PDT) Received: from fwd05.sul.t-online.de by mailout08.sul.t-online.com with smtp id 16x6dB-0006ab-03; Mon, 15 Apr 2002 15:34:53 +0200 Received: from Magelan.Leidinger.net (520065502893-0001@[217.83.22.213]) by fmrl05.sul.t-online.com with esmtp id 16x6d8-1urWiWC; Mon, 15 Apr 2002 15:34:50 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.12.2/8.12.2) with ESMTP id g3FDYwRD091397; Mon, 15 Apr 2002 15:35:02 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200204151335.g3FDYwRD091397@Magelan.Leidinger.net> Date: Mon, 15 Apr 2002 15:34:58 +0200 (CEST) From: Alexander Leidinger Subject: Re: ATA errors on recent -current To: sos@freebsd.dk Cc: tlambert2@mindspring.com, keramida@ceid.upatras.gr, dwcjr@inethouston.net, current@FreeBSD.ORG In-Reply-To: <200204151318.g3FDIoL43045@freebsd.dk> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT X-Sender: 520065502893-0001@t-dialin.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 15 Apr, Sĝren Schmidt wrote: > Again that has *nothing* to do with the DTLA drives and DMA speed > and the phase of the moon... But perhaps it depends on the distance between the drive and the nordpole... the ones with the problems are all more far away from it than you... ;-) > But it shows (as we already know) that using tags on any drive > that supports it, can fail on some systems. More strangely: it worked for me a lot longer than for other people. The first kernel which showed the problem to me was a Apr 8(?) kernel, Martin Schündehütte complained already with a Mar xx (xx < 28) kernel in de.comp.os.unix.bsd. >> I wonder if limiting outstanding tagged commands to less than the >> number advertised by the drive would also work... can't be worse >> than the initialization reordering patch that failed (e.g the >> worst case is it still has the problems). A lot safer than banging >> bits in the firmware, I'm sure, though... >> >> Limiting the outstanding tagged commands to less than the advertised >> amount would actually be my first choice of a hack for a software >> workaround. > > Thats not the problem either, the problem is that I apparently > changed some subtle bits that make it fail on some systems, regardless > of controller and disk type, but which is marginal enough that I > cant reproduce the problem here in the lab... What about Brian's offer to give you access to his machine? Isn't this enough in this case to play a little bit? Bye, Alexander. -- The best things in life are free, but the expensive ones are still worth a look. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message