Subject: Re: promise ultra 66 ide controller not working
To: Russell McManus <russell_mcmanus@yahoo.com>
From: Manuel Bouyer <bouyer@antioche.eu.org>
List: netbsd-help
Date: 10/01/2003 21:32:04
On Mon, Sep 29, 2003 at 05:53:06PM -0400, Russell McManus wrote:
>
> (I previously sent this to port-macppc, and got no response, and upon
> reflection, have decided to try posting it here. Sorry for the
> duplication).
>
> I've (finally) gotten my powermac 9600MP up and running 1.6. I've
> moved over a bunch of hardware goodies from my old 7300 into this new
> beast, and one of them is not working. I wonder whether the problem
> is a toasted disk, or a hardware incompatibility, who knows.
>
> The controller and disk are identified OK during boot up:
>
> pciide0 at pci0 dev 14 function 0: Promise Ultra66/ATA Bus Master IDE Accelerator (rev. 0x01)
> pciide0: bus-master DMA support present
> pciide0: primary channel configured to native-PCI mode
> pciide0: using irq 24 for native-PCI interrupt
> wd0 at pciide0 channel 0 drive 0: <WDC WD1600BB-00DAA0>
> wd0: drive supports 16-sector PIO transfers, LBA48 addressing
> wd0: 149 GB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 312581808 sectors
> wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
> wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 4 (Ultra/66) (using DMA data transfers)
> pciide0: secondary channel configured to native-PCI mode
> pciide0: disabling secondary channel (no drives)
>
> But when I try to mount a filesystem on the sucker, I get this
> horrible sequence of messages:
>
> pciide0:0:0: lost interrupt
> type: ata tc_bcount: 512 tc_skip: 0
> pciide0:0:0: bus-master DMA error: missing interrupt, status=0x21
> wd0: transfer error, downgrading to Ultra-DMA mode 2
> wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 (Ultra/33) (using DMA data transfers)
> wd0c: DMA error reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying
> pciide0:0:0: lost interrupt
> type: ata tc_bcount: 512 tc_skip: 0
> pciide0:0:0: bus-master DMA error: missing interrupt, status=0x21
> wd0: transfer error, downgrading to Ultra-DMA mode 1
> wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 1 (using DMA data transfers)
> wd0c: DMA error reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying
> pciide0:0:0: lost interrupt
> type: ata tc_bcount: 512 tc_skip: 0
> pciide0:0:0: bus-master DMA error: missing interrupt, status=0x21
> wd0: transfer error, downgrading to DMA mode 2
> wd0(pciide0:0:0): using PIO mode 4, DMA mode 2 (using DMA data transfers)
> wd0c: DMA error reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying
> pciide0:0:0: lost interrupt
> type: ata tc_bcount: 512 tc_skip: 0
> pciide0:0:0: bus-master DMA error: missing interrupt, status=0x21
> wd0: transfer error, downgrading to PIO mode 4
> wd0(pciide0:0:0): using PIO mode 4
> wd0c: DMA error reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying
> wd0: soft error (corrected)
>
>
> At that point, the drive appears inoperable, for example one can start
> an fsck_ffs on it, but it does not appear to make progress. Any ideas
> about what might be wrong? I've included a full dmesg output to
> provide any necessary context...
Could be an interrupt problem. Can you try a recent current kernel, and see if
the drive is probed ?
ftp://releng.netbsd.org/pub/NetBSD-daily/current/200309280000/macppc/binary/kernel/netbsd-GENERIC.gz
--
Manuel Bouyer <bouyer@antioche.eu.org>
NetBSD: 24 ans d'experience feront toujours la difference
--