From owner-freebsd-current Tue Mar 14 10:14:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from radiac.mine.nu (h186n2fls20o974.telia.com [212.181.170.186]) by hub.freebsd.org (Postfix) with ESMTP id C77BB37B711 for ; Tue, 14 Mar 2000 10:14:34 -0800 (PST) (envelope-from ps@radiac.mine.nu) Received: (from ps@localhost) by radiac.mine.nu (8.9.3/8.9.3) id TAA13848; Tue, 14 Mar 2000 19:14:14 +0100 (CET) (envelope-from ps) Date: Tue, 14 Mar 2000 19:14:03 +0100 From: Patrik Sundberg To: Will Saxon Cc: current@FreeBSD.ORG Subject: Re: ATA timeout errors Message-ID: <20000314191403.A13766@radiac.mine.nu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from saxonww@ufl.edu on Tue, Mar 14, 2000 at 12:17:15PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 14, 2000 at 12:17:15PM -0500, Will Saxon wrote: > 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 also get this when booting - think it started happening when I started using the new ata-driver. For me it happens when the root is supposed to be mounted (from dmesg): atapci0: port 0xffa0-0xffaf at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ad0: 2015MB [4095/16/63] at ata0-master using WDMA2 ad2: 814MB [1654/16/63] at ata1-master using PIO3 acd0: CDROM at ata0-slave using PIO3 Mounting root from ufs:/dev/ad0s1a 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 and then everything proceeds as normal. > I dont get any panics or anything, and after the reset to PIO everything > seems to work fine. agree. > 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? As you can see I am using a seagate disk and I am having the same problem. > 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. There are probably many people out there affected by this so I really think it ought to be fixed - preferably before -RELEASE. -- Patrik Sundberg - email: ps@raditex.se || ps@radiac.mine.nu ---> telefon: 013-178 567 - mobiltelefon: 070-760 22 40 <--- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message