From owner-freebsd-current Sat Jan 8 5: 5:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 35CAA158DA for ; Sat, 8 Jan 2000 05:05:28 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id OAA44258; Sat, 8 Jan 2000 14:05:16 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001081305.OAA44258@freebsd.dk> Subject: Re: ATA driver timeout In-Reply-To: from Theo van Klaveren at "Jan 8, 2000 01:47:00 pm" To: havoc@Cal30B054.student.utwente.nl (Theo van Klaveren) Date: Sat, 8 Jan 2000 14:05:16 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Theo van Klaveren wrote: > > I still can't seem to be able to boot -CURRENT with the ATA driver, > much as I'd like to, due to the `timeout-resetting device' error, which > I've seen more people report. I've sacrificed some dead trees to give > you the exact boot messages: > > ad0: ATA-0 disk at ata0 as master > ad0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S > ad0: 16 secs/int, 1 depth queue, WDMA2 > ad1: ATA-3 disk at ata0 as slave > ad1: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S > ad1: 16 secs/int, 1 depth queue, UDMA33 > . > . > Mounting root from ufs:/dev/ad0s1a > ad0: ad_timeout: lost disk contact - reseting > ata0: resetting devices .. > > After which the machine hangs _hard_ (i.e. no respone except to the > reset key). > > The information given is mostly correct: The second drive is > UDMA33 and can handle it with the WD driver. Also, when this drive > is removed, the error still occurs. > > I'm in doubt as to the first drive though: The BIOS says it's 'Mode 4', > is that the same as WDMA2? Could the harddisk be reporting the wrong > value, even though the BIOS is giving the correct one? I'm just grasping > at straws here. Mode 4 is PIO4 that is no DMA, it could very well be the problem, WD has made a lot of problematic drives in this area. You could try to comment out the dmainit call in ata-disk.c and see if that helps you. And yes, I'm working on a way to set this from useland... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message