From owner-freebsd-current Sat Jan 8 5:56: 6 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 274EE158F7 for ; Sat, 8 Jan 2000 05:56:03 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id OAA56905; Sat, 8 Jan 2000 14:56:00 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001081356.OAA56905@freebsd.dk> Subject: Re: ATA driver timeout In-Reply-To: from Theo van Klaveren at "Jan 8, 2000 02:19:03 pm" To: havoc@Cal30B054.student.utwente.nl (Theo van Klaveren) Date: Sat, 8 Jan 2000 14:56:00 +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: > > > > 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. > > That helps me, but if I'm not mistaken it also disabled UDMA33 on the > second drive. Yup, it was more to determine is DMA really was your problem... > Ah well.. at least I can boot an ATA kernel now. > > > And yes, I'm working on a way to set this from useland... > > That'd be really nice, though if the kernel doesn't even boot to single > user mode, I don't see how this would help users with this problem, as > you'd have to do it before reboot. The idea is to boot in non-DMA mode, and then have a script setup the wanted modes from etc/rc*. That way you can always boot into singleuser mode and change the access modes... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message