Hans Zimmerman wrote: ... > OpenBSD 3.6-stable (GENERIC) #1: Wed Apr 6 20:23:57 CEST 2005 > [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC ... > pciide0 at pci1 dev 11 function 0 "CMD Technology SiI3112 SATA" rev > 0x02: DMA, channel 0 wired to native-PCI, channel 1 wired to native-PCI > pciide0: using irq 11 for native-PCI interrupt > wd0 at pciide0 channel 0 drive 0: <Maxtor 6Y080M0> > wd0: 16-sector PIO, LBA, 78167MB, 160086528 sectors > wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 > wd1 at pciide0 channel 1 drive 0: <Maxtor 6Y080M0> > wd1: 16-sector PIO, LBA, 78167MB, 160086528 sectors > wd1(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 5
> OpenBSD 3.7 (GENERIC) #50: Sun Mar 20 00:01:57 MST 2005 > [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC ... > pciide0 at pci1 dev 11 function 0 "CMD Technology SiI3112 SATA" rev > 0x02: DMA > pciide0: using irq 11 for native-PCI interrupt > pciide0: port 0: device present, speed: 1.5Gb/s > wd0 at pciide0 channel 0 drive 0: <Maxtor 6Y080M0> > wd0: 16-sector PIO, LBA, 78167MB, 160086528 sectors > wd0(pciide0:0:0): using BIOS timings, Ultra-DMA mode 6 > pciide0: port 1: device present, speed: 1.5Gb/s > wd1 at pciide0 channel 1 drive 0: <Maxtor 6Y080M0> > wd1: 16-sector PIO, LBA, 78167MB, 160086528 sectors > wd1(pciide0:1:0): using BIOS timings, Ultra-DMA mode 6 ... > wd0(pciide0:0:0): timeout > type: ata > c_bcount: 512 > c_skip: 0 > pciide0:0:0: bus-master DMA error: missing interrupt, status=0x21 > pciide0 channel 0: reset failed for drive 0 > wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying > pciide0:0:0: not ready, st=0xd0<BSY,DRDY,DSC>, err=0x00 > pciide0 channel 0: reset failed for drive 0 > wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying > pciide0:0:0: not ready, st=0xd0<BSY,DRDY,DSC>, err=0x00 > > It continues here .... Looks like the problem is the CMD Tech SATA chip is now recognized and handled as an SATA system, rather than as an IDE system as it was for 3.6. Unfortunately, looks like there is a bug in the SATA support. A couple ideas: 1) Try a -current snapshot. It might be fixed by now. 2) See if there are any options in the BIOS of the machine that will let you treat the drives more as IDE and less as SATA (or the other way around). Might return the machine to a working state. Nick.
