Subject: Re: IDE Breakage in 1.5: false alarm?
To: None <current-users@netbsd.org>
From: Wolfgang Rupprecht <wolfgang@wsrcc.com>
List: current-users
Date: 02/07/2001 14:02:22
My newest drive always gets hit with a downgrade after a standby-mode
spin-up.  I wonder if this is a bug...

During boot:
    wd1 at pciide0 channel 0 drive 1: <IBM-DTLA-307075>
    wd1: drive supports 16-sector PIO transfers, LBA addressing
    wd1: 73308 MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 150136560 sectors
    wd1: 32-bit data port
    wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
    ...
    wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 4 (Ultra/66) (using DMA data transfers)

Later on after the disk is idle for a while, spins down and then gets
accessed:

    Feb  6 14:55:37 capsicum /netbsd: pciide0:0:1: lost interrupt
    Feb  6 14:55:37 capsicum /netbsd: 	type: ata tc_bcount: 8192 tc_skip: 0
    Feb  6 14:55:37 capsicum /netbsd: pciide0:0:1: device timeout, c_bcount=8192, c_skip0
    Feb  6 14:55:37 capsicum /netbsd: wd1: transfer error, downgrading to Ultra-DMA mode 2
    Feb  6 14:55:37 capsicum /netbsd: wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 (Ultra/33) (using DMA data transfers)
    Feb  6 14:55:37 capsicum /netbsd: wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 2 (Ultra/33) (using DMA data transfers)
    Feb  6 14:55:37 capsicum /netbsd: wd1h: device timeout reading fsbn 16 of 16-31 (wd1 bn 27769408; cn 27549 tn 0 sn 16), retrying
    Feb  6 14:55:37 capsicum /netbsd: wd1: soft error (corrected)

So initially it is accessed as an ultra-66 and later gets downgraded
to an ultra-33.

-wolfgang
-- 
       Wolfgang Rupprecht <wolfgang+gnus@dailyplanet.wsrcc.com>
		    http://www.wsrcc.com/wolfgang/
Coming soon: GPS mapping tools for Open Systems. http://www.gnomad-mapping.com/