Subject: Re: scsi disk generic HBA error after reboot
To: Dan LaBell <dan4l-nospam@verizon.net>
From: Manuel Bouyer <bouyer@antioche.eu.org>
List: netbsd-help
Date: 04/16/2005 15:41:30
On Sat, Apr 16, 2005 at 06:59:48AM -0400, Dan LaBell wrote:
> >OK, I see the problem. The driver is ignoring the card's model or
> >eeprom
> >setting for negotiating sync/wide, because the checks are not at the
> >proper
> >place.
> >Please try the (untested) attached patch
> Cool, thanks. AND it works!
>
> %dmesg | grep 'trm0\|sd[12]'
> 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
> sd1 at scsibus0 target 0 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), 8-bit (20.000MB/s) transfers
> sd2 at scsibus0 target 1 lun 0: <IBM, DXHS18Y, 0430> disk fixed
> sd2: 17366 MB, 8154 cyl, 20 head, 218 sec, 512 bytes/sect x 35566480
> sectors
> sd2: sync (50.00ns offset 15), 8-bit (20.000MB/s) transfers
Good. I'm commiting it and requesting pullups.
>
> [...]
>
> Curious, when the drive spins up on the initial boot, the kernel prints
> out less
> info, actually <IBM, DXHS, 0430> disk fixed and no line about
> geometry, was it just skipping the negotiation because it didn't have
> enough info about the drive?
Yes, this is quite possible
But the kernel should spin up the drives and process with the normal
identification and negotiation then. I have a 1.6.2 system with drives
configured to not spin up at poweron, and it works as expected.
--
Manuel Bouyer <bouyer@antioche.eu.org>
NetBSD: 26 ans d'experience feront toujours la difference
--