Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 19 May 1999 12:03:55 -0400 (EDT)
From:      Chuck Robey <chuckr@picnic.mat.net>
To:        "Justin T. Gibbs" <gibbs@narnia.plutotech.com>
Cc:        scsi@FreeBSD.org
Subject:   Re: ahc boot messages
Message-ID:  <Pine.BSF.4.10.9905191202350.69006-100000@picnic.mat.net>
In-Reply-To: <199905191538.JAA08634@narnia.plutotech.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 19 May 1999, Justin T. Gibbs wrote:

> In article <Pine.BSF.4.10.9905181706210.25906-100000@picnic.mat.net> you wrote:
> > I recently got my new DK440LX motherboard cranking (it's great!) and
> > I've not seen the ahc driver since back in 1.1.5.1 days.  It went real
> > smoothly getting it going (well, one f-u, but we won't talk about that
> > :-) .... anyhow, I noticed the boot messages produced by the ahc driver,
> > it seemed excessively verbose.  The DK440LX has the 7895 controller
> > which has 2 busses, and all targets on both buses get a line each to
> > announce their status.  I get a LOT of these lines:
> > 
> > ahc0: Selection Timeout on A:1. 1 SCBs aborted
> 
> If you don't like the messages, stop booting with the verbose flag.
> You asked for the system to be verbose, and so it is.

Actually, I didn't, but you're telling me that I'm getting it anyway.
OK, I can stop perstering the scsi list, at least.

I specifically turned off verbose booting in /boot/loader.conf, darn it!

> 
> > 32 lines of this.  Isn't this really excessive?  For anyone?  Even if
> > the messages are needed (and I like having the message) it wouldn't be
> > all that difficult to come up with a format to squeeze all messages from
> > each buss into 2 lines (one header, one data line) so all the info could
> > still be displayed, but in a far more readable format.
> 
> Each of those messages occurs ~250ms apart.  How does the
> controller know in advance if a device will respond to selection?
> It doesn't.  The main reason I added the message is so you can
> determine why a device was either not found at boot, or disappears
> after boot has completed.
> 
> --
> Justin
> 

----------------------------+-----------------------------------------------
Chuck Robey                 | Interests include any kind of voice or data 
chuckr@picnic.mat.net       | communications topic, C programming, and Unix.
213 Lakeside Drive Apt T-1  |
Greenbelt, MD 20770         | I run picnic (FreeBSD-current)
(301) 220-2114              | and jaunt (Solaris7).
----------------------------+-----------------------------------------------






To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9905191202350.69006-100000>