Not to belabor this thread too much more, but if you peruse the openchrome-users mailing list for a bit, you will see that these boards are developing a reputation for hard lockups under linux, so it is not just me. The developing consesnus over there is that the only way to prevent lockups is to disable all DMA in the BIOS.
I left the DMA enabled for the OpenBSD tests as an experiment. I was actually pleased to see that OpenBSD detected the problem and downgraded the DMA mode rather than descend into a frozen state. -- Mark On Mon, Jan 29, 2007 at 09:38:03AM -0600, Marco Peereboom wrote: > Or missing interrupts... > > On Mon, Jan 29, 2007 at 04:29:52PM +0100, Dimitry Andric wrote: > > Mark Zimmerman wrote: > > > You will notice the sucky DMA of the Jetway board in all of them. > > ... > > > wd0a: aborted command, interface CRC error reading fsbn 671456 of > > > 671456-0 (wd0 bn 5571281; cn 5527 tn 1 sn 2), retrying > > > wd0: transfer error, downgrading to Ultra-DMA mode 4 > > > wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 4 > > > wd0a: aborted command, interface CRC error reading fsbn 671456 of > > > 671456-0 (wd0 bn 5571281; cn 5527 tn 1 sn 2), retrying > > > wd0: soft error (corrected) > > > wd0: transfer error, downgrading to Ultra-DMA mode 3 > > > wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 3 > > > wd0a: aborted command, interface CRC error reading fsbn 671168 of > > > 671168-0 (wd0 bn 5570993; cn 5526 tn 12 sn 29), retrying > > > wd0: soft error (corrected) > > > > These sorts of errors are usually caused by bad cabling, connectors, or > > dying drives. Try replacing the cables or drives, to see if it helps.
