From owner-freebsd-current Thu Apr 18 8:45:41 2002 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id 0164F37B405 for ; Thu, 18 Apr 2002 08:45:32 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.12.2/8.12.2) id g3IFjOs0048563; Thu, 18 Apr 2002 17:45:24 +0200 (CEST) (envelope-from sos) From: Søren Schmidt Message-Id: <200204181545.g3IFjOs0048563@freebsd.dk> Subject: Re: ATA errors on recent -current In-Reply-To: To: msch@snafu.de Date: Thu, 18 Apr 2002 17:45:24 +0200 (CEST) Cc: Terry Lambert , freebsd-current@FreeBSD.ORG Reply-To: sos@freebsd.dk X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 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 It seems Matthias Schuendehuette wrote: > > > I didn't mean for the reset itself, I meant for the process. You > > > can't "take back" writes that are in progress and not acknowledged, > > > in order to retry them after the reset, so as to not lose data. > > > > Oh yes you can, the ATA driver does just that in case of the drive > > loosing its marbels. > > Does that mean that the driver isn't aware of the 'tags-problem'? If I > understand you right, it should be possible to reset the drive and > continue, maybe without tags or at a reduced UDMA-Speed or whatever > actions seem appropriate... > > ...ahh, I mean, the driver *does* take an action (it/he(?) switches > back to PIO4), but why is any UDMA-Mode no longer usable afterwards? Is > the drive been reset or just switched back? What is the impact of a > reset compared to a switch back? The driver always resets the ATA channel if a command times out, thats the only way to gain control of the device(s) again. The driver always falls back to PIO if it encounters a DMA problem, be it with tags or not, as chances are DMA doesn't work at all if a problem shows up. Now this could be changed, but in 99% of the cases it will just make the pain last longer, until it finally switches back to PIO. I chose this route because most users prefers to keep thier data intact at (almost) any price. However in -current and recent -stables you can switch on DMA again with atacontrol, if you think it was a fluke that got it set back to PIO. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message