From owner-freebsd-current Tue Mar 14 9:17:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp.ufl.edu (sp28fe.nerdc.ufl.edu [128.227.128.108]) by hub.freebsd.org (Postfix) with ESMTP id B35FC37B7CA for ; Tue, 14 Mar 2000 09:17:18 -0800 (PST) (envelope-from saxonww@ufl.edu) Received: from n44-230.dhnet.ufl.edu (gremlin@[128.227.44.230]) by smtp.ufl.edu (8.9.3/8.9.3/2.2.1) with ESMTP id MAA65208 for ; Tue, 14 Mar 2000 12:17:15 -0500 Date: Tue, 14 Mar 2000 12:17:15 -0500 (EST) From: Will Saxon X-Sender: gremlin@localhost To: current@freeBSD.org Subject: ATA timeout errors Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I think this may have already been presented/answered but I am not certain. I have noticed recently that every so often I will get the following set of messages, generally right after the bootup sequence finishes: ad0: READ command timeout - resetting ata0: resetting devices .. done ad0: READ command timeout - resetting ata0: resetting devices .. done ad0: READ command timeout - resetting ata0: resetting devices .. done ad0: READ command timeout - resetting ata0-master: WARNING: WAIT_READY active=ATA_ACTIVE_ATA ad0: trying fallback to PIO mode ata0: resetting devices .. done This latest episode is on a 5.0-Current machine cvsupped yesterday, I got those messages while trying to log in after a reboot. I dont get any panics or anything, and after the reset to PIO everything seems to work fine. ad0 is an IBM Deskstar 22GXP. I recall something about Deskstars resetting their heads every week as a possible explanation for a similar problem, is that what this is too? I would of course prefer to be in DMA mode all the time rather than PIO. If there is something I can do to fix this I'm all ears. -Will To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message