From owner-freebsd-stable Sat Nov 25 0:41:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from yez.hyperreal.org (3ff8f8da.dsl.flashcom.net [63.248.248.218]) by hub.freebsd.org (Postfix) with SMTP id C071637B4C5 for ; Sat, 25 Nov 2000 00:41:35 -0800 (PST) Received: (qmail 78184 invoked by uid 1000); 25 Nov 2000 08:41:33 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 25 Nov 2000 08:41:33 -0000 Date: Sat, 25 Nov 2000 00:41:33 -0800 (PST) From: Brian Behlendorf X-Sender: brian@localhost To: Kal Torak Cc: FreeBSD-stable Subject: Re: more ata0 problems In-Reply-To: <3A1E88A0.7C9C6BA@quake.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 25 Nov 2000, Kal Torak wrote: > ad0: WRITE command timeout tag=0 serv=0 - resetting > ata0: resetting devices .. done [..] > This was on my IBM laptop, and I have had no problems with any of > the previous versions... > It would seem there must be some bug in the ata driver? I suspect that it's a matter of a new diagnostic suddenly causing people to think there's a new error present, when they simply didn't see it before. I started seeing it when I did an upgrade a month ago too, and thought it was an error, before I realized I really WAS having drive problems. The only other explanation is that the ata driver is somehow causing these new errors to appear, but I consider that unlikely; since getting a new hard drive (same model, same machine, etc) I'm not seeing the errors, and the old hard drive died hard (unable to even boot now) not something I'd suspect the ata driver of causing. Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message