From owner-freebsd-current Thu Apr 18 8:51:11 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 6D95637B400 for ; Thu, 18 Apr 2002 08:51:07 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.12.2/8.12.2) id g3IFp6F2048629; Thu, 18 Apr 2002 17:51:06 +0200 (CEST) (envelope-from sos) From: Søren Schmidt Message-Id: <200204181551.g3IFp6F2048629@freebsd.dk> Subject: Re: ATA errors on recent -current In-Reply-To: <3CBEEA3A.50347DD9@mindspring.com> To: Terry Lambert Date: Thu, 18 Apr 2002 17:51:06 +0200 (CEST) Cc: msch@snafu.de, 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 Terry Lambert wrote: > "Søren Schmidt" 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. > > If it worked, people wouldn't be having this problem. Hmm, since I havn't been able to get my hands on the problem (I've been running 3 systems here with tags all over since the first report, not a single hickup yet :( ) I can't tell whats going on, it might be that the drive somehow gets really confused I dont know, for now those having tags problems should just not enable it... > What's your theory on it? None so far, I've instrumented the code here, and I simply cannot see what should go wrong (yet). BUT recent current with the busdma'd ATA driver screws up with tags, fix is coming as soon as I get a few hours to commit it... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message