On Thu, Dec 01, 2005 at 11:44:32PM -0500, Jason Dixon wrote:
> I recently purchased a pair of Iron Systems A210 servers for a  
> firewall installation.  The systems were ordered with no hard drives  
> and ide-to-CF adapters onboard.  They are running 3.8 -release on  
> 512MB compact flash (SanDisk SDCFB-512).  I'm seeing the following  
> error in the same place on both systems at boot:
> 
> wd0(pciide0:0:0): timeout
>         type: ata
>         c_bcount: 512
>         c_skip: 0
> pciide0:0:0: bus-master DMA error: missing interrupt, status=0x21
> wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying
> wd0(pciide0:0:0): timeout
>         type: ata
>         c_bcount: 512
>         c_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: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying
> wd0: soft error (corrected)
> 
> Everything then continues as usual, although I'm also not doing any  
> intentional writes to disk.  Anyone have any idea what might be  
> causing this and if it's safe to ignore (yeah, right).

OpenBSD tries to talk to the controller in the fastest way possible
(usually some (U)DMAx setting). If this fails, it figures it's running
at too high a speed and downgrades.

It does the same on my box, and seems to work just fine:

OpenBSD 3.8-stable (GENERIC_WITH_RAID) #1: Fri Nov 18 13:06:07 CET 2005
    [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC_WITH_RAID
<booting stuff...>
pcib0 at pci0 dev 17 function 0 "VIA VT8233 ISA" rev 0x00
pciide0 at pci0 dev 17 function 1 "VIA VT82C571 IDE" rev 0x06: ATA133, channel 
0 configured to compatibility, channel 1 configured to compatibility
wd0 at pciide0 channel 0 drive 0: <Maxtor 6E040L0>
wd0: 16-sector PIO, LBA, 39205MB, 80293248 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 6
<more booting...>
Kernelized RAIDframe activated
wd0c:  aborted command, interface CRC error reading fsbn 64 (wd0 bn 64; cn 0 tn 
1 sn 1), retrying
wd0: transfer error, downgrading to Ultra-DMA mode 5
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
wd0c:  aborted command, interface CRC error reading fsbn 64 (wd0 bn 64; cn 0 tn 
1 sn 1), retrying
wd0: soft error (corrected)
cd0(atapiscsi0:0:0): Check Condition (error 0x70) on opcode 0x0
    SENSE KEY: Not Ready
     ASC/ASCQ: Medium Not Present
dkcsum: wd0 matches BIOS drive 0x80
root on wd0a
rootdev=0x0 rrootdev=0x300 rawdev=0x302
wd0: transfer error, downgrading to Ultra-DMA mode 4
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 4
wd0a:  aborted command, interface CRC error reading fsbn 357728 of 
357728-357791 (wd0 bn 357791; cn 354 tn 15 sn 14), retrying
wd0: transfer error, downgrading to Ultra-DMA mode 3
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 3
wd0a:  aborted command, interface CRC error reading fsbn 357728 of 
357728-357791 (wd0 bn 357791; cn 354 tn 15 sn 14), retrying
wd0: soft error (corrected)
<yet more messages...>

The same happens with GENERIC, by the way.

It's pretty harmless, just a little noisy at boot. (And of course, you
want to run your disks at the highest speed possible, so if it ends up
somewhere below that it's suboptimal. But better than not working at
all.)

                Joachim

Reply via email to