Subject: Re: generic HBA error messages on 1.6beta2
To: Matthias Buelow <mkb@mukappabeta.de>
From: Matthew Jacob <mjacob@feral.com>
List: port-alpha
Date: 06/25/2002 11:00:23
On Tue, 25 Jun 2002, Matthias Buelow wrote:

> Matthew Jacob wrote:
> 
> > It's also be nice to see the /var/log/messages file...
> 
> the only thing in there are the "generic HBA error" messages
> (and syslogd's "restart" message because I set the time)...
> 
> I've now set the debuglevel to 0x3f with your attached program
> and did a scsictl /dev/scsibus0 reset.  The kernel reports:
> 
> Jun 25 19:50:45 digibus /netbsd: isp0: driver initiated bus reset of bus 0
> Jun 25 19:50:45 digibus /netbsd: sd0(isp0:0:0:0): generic HBA error
> Jun 25 19:50:45 digibus /netbsd: sd0(isp0:0:0:0): generic HBA error
> Jun 25 19:50:51 digibus /netbsd: isp0: (0.0.0): FIN dl8192 resid 8192 
> STS 0x2 SKEY 6 XS_ERR=0x1
> Jun 25 19:50:51 digibus /netbsd: sd0(isp0:0:0:0): generic HBA error


Was this right after reboot?


Sense Key of 6 is plain old Unit Attention. 

The 'generic HBA error' can be set by a lot of conditions.

I'm trying to find the one that doesn't say anything else at all. So far, all
I see as possible is a corrupted response queue. Try isp_debug of 0x7f- let's
see what the actual command being failed is.

-matt