From owner-freebsd-questions Wed Nov 1 12:23: 9 2000 Delivered-To: freebsd-questions@freebsd.org Received: from gateway.telecom.ksu.edu (gateway-1.telecom.ksu.edu [129.130.63.239]) by hub.freebsd.org (Postfix) with ESMTP id 080AA37B4CF for ; Wed, 1 Nov 2000 12:23:06 -0800 (PST) Received: from sioux.telecom.ksu.edu(129.130.60.32) by pawnee.telecom.ksu.edu via smap (V2.0) id xma003085; Wed, 1 Nov 00 14:22:46 -0600 Message-ID: <3A007B6D.CC73786B@telecom.ksu.edu> Date: Wed, 01 Nov 2000 14:22:05 -0600 From: nathan X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Arcady Genkin Cc: freebsd-questions@FreeBSD.ORG Subject: Re: ad0: DMA problem fallback to PIO mode; HARD READ ERROR blk#25418687 References: <3A006927.D10FC9E0@telecom.ksu.edu> <87wven1mlu.fsf@tea.thpoon.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Arcady Genkin wrote: > > make sure DMA is NOT enabled in the kernel ... that MIGHT be whats > > happening, your kernel is tryin to use DMA through a non-dma channel > > (your p166 onboard ctrl) > > How can I find out if my mobo's IDE controller supports DMA? It > appears that the second disk has been running in DMA mode for months, > and no problem... i hear what you're saying... however, the 82371SB (430HXchipset) only supports ATA/16 (ie. PIO Mode 4 -- NOT UDMA) you can verify this at: http://developer.intel.com/design/chipsets/drivers/busmastr/ you can go into your BIOS(CMOS) and it should list exactly what its detecting your harddrives at, like transfer mode, size, etc it'll prolly be like PIOMode4, and LBA enabled... > > i don't know what brand of mobo you have, but, being an ex-hardware guy, i've > > RARELY seen onboard IDE controllers go bad.. even on OLD hardware... > > It's a Gygabit with an HX chipset. any chance you could take a peek inside your box and get exact make/model? or it might show up on POST (this is why i never 'cover' my boxes) > Here are relevant boot-up messages: > > pcib0: on motherboard > pci0: on pcib0 > isab0: at device 7.0 on pci0 > isa0: on isab0 > atapci0: port 0xf000-0xf00f at device 7.1 on pci0 > ata1: at 0x170 irq 15 on atapci0 > ata1-master: DMA limited to UDMA33, non-ATA66 compliant cable > ad2: 13042MB [26500/16/63] at ata1-master WDMA2 > ad3: 18366MB [37317/16/63] at ata1-slave WDMA2 > Mounting root from ufs:/dev/ad2s1a > > It's the IBM drive that's giving me grief. That cable message, is it > of any importance? I don't think the controller can do ATA-66 > anyways, so I figured that DMA33 would do. well... it WON'T if your controller doesn't support it ): > Any further thoughts? rebuild your kernel withOUT DMA and see what happens good luck! nathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message