On Mon, 11 Jun 2001, Manuel Bouyer wrote:

> On Mon, Jun 11, 2001 at 09:22:10AM +0200, Samuel.Hornus wrote:
> >
> > Hi,
> >
> > It seems that wdc and pciide provides the same functionnality at the same
> > level of abstraction for the 'upper' driver wd.
> > 'man wdc' says that "PCI IDE controllers in legacy mode are also
> >      supported, but the pciide(4) driver may provide more functionality"
> >
> > I have a G4 with a IBM brand new IDE hard disk.
> > I have problems with it (see 'daily cronjob freezes the machine' post)
> > So I would like to know wether, on my machine, changing wdc for pciide is
> > an (better) alternative ? in order to avoid the lost_interrupt crash.
>
> What kind of controller is it (dmesg please) ?

Here is part of dmesg (/var/run/dmesg.boot) that seems(car je suis
debutant !) relevant :
(there is also a scsi card for a cd burner)
==================================================================
ppb0 at pci1 dev 13 function 0: vendor 0x1011 product 0x0026 (rev. 0x05)
pci2 at ppb0 bus 1
pci2: i/o space, memory space enabled
siop0 at pci2 dev 2 function 0: Symbios Logic 53c875 (ultra-wide scsi)
siop0: using on-board RAM
siop0: interrupting at irq 52
scsibus0 at siop0: 16 targets, 8 luns per target
obio0 at pci2 dev 7 function 0: addr 0x80000000
[...]
obio0 at pci2 dev 7 function 0: addr 0x80000000
wdc0 at obio0 offset 0x1f000 irq 19: DMA transfer
wd0 at wdc0 channel 0 drive 0: <IC35L040AVER07-0>
wd0: drive supports 16-sector PIO transfers, LBA addressing
wd0: 39266 MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 80418240 sectors
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
wd1 at wdc0 channel 0 drive 1: <QUANTUM FIREBALLP KX20.5>
wd1: drive supports 16-sector PIO transfers, LBA addressing
wd1: 19609 MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 40160988 sectors
wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 4 (Ultra/66)
wd0(wdc0:0:0): using PIO mode 4, DMA mode 2 (using DMA data transfers)
wd1(wdc0:0:1): using PIO mode 4, DMA mode 2 (using DMA data transfers)
wdc1 at obio0 offset 0x20000 irq 20: DMA transfer
atapibus0 at wdc1 channel 0: 2 targets
cd0 at atapibus0 drive 0: <HITACHI DVD-ROM GD-3000, , 020S> type 5 cdrom removable
cd0: drive supports PIO mode 4, DMA mode 2
sd0 at atapibus0 drive 1: <IOMEGA  ZIP 100       ATAPI, , 14.A> type 0 direct removable
sd0: drive offline
cd0(wdc1:0:0): using PIO mode 4, DMA mode 2 (using DMA data transfers)
sd0(wdc1:0:1): using PIO mode 3
wdc2 at obio0 offset 0x21000 irq 21: DMA transfer
=====================================================================
> pciide has knowledges of chips-specific features (in order to use DMA, mainly).
> It's possible that the OF didn't set up timing properly and that pciide
> corrected this.

Does that mean you believe this may be the cause of the "wdc0 lost
interrupt" ?
Could this problem come from a bas configuration of 'slave'/'master'
jumper-configuration of the disk ?

-- 
Samuel.