--Signature=_Tue__21_Sep_2004_12_21_52_+0200_=TrsxukODhumHuMO
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 7bit


Hi, I'm getting the following messages on 2.0_BETA (sources
from today):

wd0: transfer error, downgrading to Ultra-DMA mode 2
cd0(viaide0:0:0): using PIO mode 4, DMA mode 2 (using DMA data transfers)
wd0(viaide0:0:1): using PIO mode 4, Ultra-DMA mode 2 (Ultra/33) (using DMA data
transfers) wd0e: error reading fsbn 7889664 of 7889664-7889691 (wd0 bn 10048863;
cn 9969 tn 1 sn 48), retrying wd0: (aborted command, interface CRC error)
wd0: soft error (corrected)
viaide0:0:1: intr with DRQ (st=0x58)
wd0: transfer error, downgrading to Ultra-DMA mode 1
cd0(viaide0:0:0): using PIO mode 4, DMA mode 2 (using DMA data transfers)
wd0(viaide0:0:1): using PIO mode 4, Ultra-DMA mode 1 (using DMA data transfers)
wd0a: device timeout writing fsbn 30816 of 30816-30831 (wd0 bn 30879; cn 30 tn
10 sn 9), retrying wd0: soft error (corrected)

dmesg(1):

cd0 at atapibus0 drive 0: <LG      CD-ROM CRD-8521B, , 1.03> cdrom removable
cd0: 32-bit data port
cd0: drive supports PIO mode 4, DMA mode 2
wd0 at atabus0 drive 1: <ST340810A>
wd0: drive supports 16-sector PIO transfers, LBA addressing
wd0: 38165 MB, 77542 cyl, 16 head, 63 sec, 512 bytes/sect x 78163247 sectors
wd0: 32-bit data port
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
cd0(viaide0:0:0): using PIO mode 4, DMA mode 2 (using DMA data transfers)
wd0(viaide0:0:1): using PIO mode 4, Ultra-DMA mode 5 (Ultra/100) (using DMA data
transfers)

viaide0 at pci0 dev 7 function 1
viaide0: VIA Technologies VT82C686A (Apollo KX133) ATA100 controller
viaide0: bus-master DMA support present
viaide0: primary channel configured to compatibility mode
viaide0: primary channel interrupting at irq 14
atabus0 at viaide0 channel 0
viaide0: secondary channel configured to compatibility mode
viaide0: secondary channel interrupting at irq 15
atabus1 at viaide0 channel 1


What does that mean? and do you know which might be the problem?

Thanks.

--Signature=_Tue__21_Sep_2004_12_21_52_+0200_=TrsxukODhumHuMO
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (NetBSD)

iD8DBQFBUADAypkLYVDran0RAtC4AJ9+IkZ6owqJvbjExmXEMZ3grnlCLwCgu/On
1MuQ6mPqETZRwrMBngVui3I=
=E32P
-----END PGP SIGNATURE-----

--Signature=_Tue__21_Sep_2004_12_21_52_+0200_=TrsxukODhumHuMO--