[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: DMA Transfer
- To: tech_(_at_)_openbsd_(_dot_)_org
- Subject: Re: DMA Transfer
- From: Philipp Buehler <OpenBSD_(_at_)_fips_(_dot_)_de>
- Date: Thu, 25 Jul 2002 09:52:37 +0200
- Mail-followup-to: tech_(_at_)_openbsd_(_dot_)_org
- Reply-to: Philipp Buehler <OpenBSD_(_at_)_fips_(_dot_)_de>
On 25/07/2002, Meishing Wang <meishingw_(_at_)_yahoo_(_dot_)_com> wrote To tech_(_at_)_openbsd_(_dot_)_org:
> Is it on Ultra-DMA mode 3?
yes.
> wd0c: aborted command, interface CRC error reading
> fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying
> wd0: transfer error, downgrading to Ultra-DMA mode 4
> wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 4
> wd0c: aborted command, interface CRC error reading
> fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying
> wd0: transfer error, downgrading to Ultra-DMA mode 3
> wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 3
> wd0c: aborted command, interface CRC error reading
> fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying
> wd0: soft error (corrected)
Here it can recover from the first error after downgrading to UDMA-3
You can fix this value w/ config(8), read wd(4) what the flag
values mean. If you dont understand it, leave it alone, it will just
take a little longer to boot.
A shorter and/or better cable could help also.
ciao
--
Philipp Buehler, aka fips | sysfive.com GmbH | BOfH | NUCH | <double-p>
#1: Break the clue barrier!
#2: Already had buzzword confuseritis ?
Visit your host, monkey.org