Subject: port-i386/29813: trm0: parity error in 2.0 after reboot.
To: None <port-i386-maintainer@netbsd.org, gnats-admin@netbsd.org,>
From: None <dan4l-nospam@verizon.net>
List: netbsd-bugs
Date: 03/28/2005 08:15:00
>Number: 29813
>Category: port-i386
>Synopsis: trm0: parity error in 2.0 after reboot.
>Confidential: no
>Severity: serious
>Priority: low
>Responsible: port-i386-maintainer
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon Mar 28 08:15:00 +0000 2005
>Originator: Daniel LaBell
>Release: 2.0
>Organization:
>Environment:
NetBSD quinn 2.0 NetBSD 2.0 (QUINN-07805) #0: Sat Mar 26 03:45:27 EST 2005 root@quinn:/usr/src/sys/arch/i386/compile/QUINN2 i386
>Description:
I have a tekram scsi controller (trm0). In 1.6 I had no problems w/ it,
In 2.0 its fine on the 1st boot after power-cycle, but after a reboot, I get:
trm0: parity error
sd1(trm0:0:0:1:0) generic HBA error.
whenever I try to access, sd1, and device not configured to disklabel /dev/sd1 , etc.
If I boot into 1.6, it works fine, but boot back into 2.0 and the problem comes back, unless I power-cycle (or halt -p) -- reset-button is not enough. The drive is configured to /not/ spin up initially, if that matters. sd0 is a atapi-zip
sd1 is ultra-star 18 <IBM, DXHS, 0430>. Also the cpu is a VIA C3 Ezra
Partial dmesg:
NetBSD 2.0 (QUINN-07805) #0: Sat Mar 26 03:45:27 EST 2005
root@quinn:/usr/src/sys/arch/i386/compile/QUINN2
total memory = 95804 KB
avail memory = 91336 KB
BIOS32 rev. 0 found at 0xfd960
<...>
trm0 at pci0 dev 11 function 0: Tekram DC395U, DC315/U (TRM-S1040) Fast20 Ultra SCSI Adapter
trm0: interrupting at irq 5
scsibus0 at trm0: 8 targets, 8 luns per target
<...>
scsibus0: waiting 2 seconds for devices to settle...
<...>
sd0(siside0:1:1): using PIO mode 3, DMA mode 1 (using DMA data transfers)
sd1 at scsibus0 target 6 lun 0: <IBM, DXHS18Y, 0430> disk fixed
sd1: 17366 MB, 8154 cyl, 20 head, 218 sec, 512 bytes/sect x 35566480 sectors
sd1: sync (50.00ns offset 15), 16-bit (40.000MB/s) transfers
sd0(siside0:1:1): Check Condition on CDB: 0x00 00 00 00 00 00
SENSE KEY: Not Ready
ASC/ASCQ: Medium Not Present
trm0: parity error
sd1(trm0:0:6:0): generic HBA error
trm0: parity error
sd1(trm0:0:6:0): generic HBA error
sd0(siside0:1:1): Check Condition on CDB: 0x00 00 00 00 00 00
SENSE KEY: Not Ready
ASC/ASCQ: Medium Not Present
trm0: parity error
sd1(trm0:0:6:0): generic HBA error
trm0: parity error
sd1(trm0:0:6:0): generic HBA error
---------------------------
When it works looks like this:
<...>
sd1 at scsibus0 target 6 lun 0: <IBM, DXHS, 0430> disk fixed
sd1(trm0:0:6:0): Check Condition on CDB: 0x00 00 00 00 00 00
SENSE KEY: Not Ready
ASC/ASCQ: Logical Unit Not Ready, Initialization Command Required
sd1: drive offline
sd0(siside0:1:1): Check Condition on CDB: 0x00 00 00 00 00 00
SENSE KEY: Not Ready
ASC/ASCQ: Medium Not Present
sd1(trm0:0:6:0): Check Condition on CDB: 0x00 00 00 00 00 00
SENSE KEY: Not Ready
ASC/ASCQ: Logical Unit Not Ready, Initialization Command Required
sd0(siside0:1:1): Check Condition on CDB: 0x00 00 00 00 00 00
SENSE KEY: Not Ready
ASC/ASCQ: Medium Not Present
>How-To-Repeat:
Reboot w/o powering off.
>Fix: