From owner-freebsd-stable Tue Apr 4 6:35:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from email.spcgroup.nl (mail.spc.nl [193.79.3.34]) by hub.freebsd.org (Postfix) with ESMTP id C420937B6CC for ; Tue, 4 Apr 2000 06:35:16 -0700 (PDT) (envelope-from e.mons@spcgroup.nl) Received: from spcgroup.nl (firewall.spcgroup.nl [193.79.3.33]) by email.spcgroup.nl (8.9.3/8.9.3) with ESMTP id PAA19022; Tue, 4 Apr 2000 15:34:56 +0200 Message-ID: <38E9EFE2.7F62E91E@spcgroup.nl> Date: Tue, 04 Apr 2000 15:36:34 +0200 From: Edwin Mons X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Soren Schmidt Cc: freebsd-stable@freebsd.org Subject: Re: ata sad combinatorics References: <200004041322.PAA87696@freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt wrote: > > It seems Mike Tancsa wrote: > > > > Have a search through the archives as I think someone else had problems > > with the Fujitsus. What if you disable DMA. Are you actually using the > > drive in Win98 with DMA drivers ? What if go back to PIO mode. Perhaps the > > maintainer can shed light on it ? > > > >atapci0: > >ATA controller> port 0xffa0-0xffaf at device 7.1 on pci0 > > >ata0: at 0x1f0 irq > > >14 on atapci0 > > >ata1: at 0x170 irq 15 on atapci0 > > The old Intel PIIX is know to have DMA problems, I never intended to > support it, but the current code (from luiqi IIRC) was found to be > sufficient IF the BIOS did its job right. I seems that we have a > BIOS here that doesn't setup things the way they should be, and the > DMA setup fails because of that. Is there any way you could upgrade > your BIOS ?? I've seen similar problems with a machine with an old VIA chipset. FWIW: I think we need a way to tell the kernel before booting that it shouldn't even try to use DMA/UDMA. Something like the good old device flags.. Regards, Edwin Mons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message