Date: Sat, 29 Apr 1995 07:17:45 -0400 (EDT) From: Peter Dufault <dufault@hda.com> To: gibbs@estienne.CS.Berkeley.EDU (Justin T. Gibbs) Cc: hackers@FreeBSD.org, wpaul@skynet.ctr.columbia.edu Subject: Shutting up the SCSI probe noise Message-ID: <199504291117.HAA13172@hda.com> In-Reply-To: <199504290622.XAA29018@estienne.cs.berkeley.edu> from "Justin T. Gibbs" at Apr 28, 95 11:22:48 pm
next in thread | previous in thread | raw e-mail | index | archive | help
General agreement: Yes there is too much noise, especially if you configure some multiport serial cards. >- The SCSI disk probe messages also irritate the hell out of me: You seem to mean SCSI probe noise in general. Only one line here is from the disk probe. One problem is we have two separate authors here: the author of the low level driver code (some of who have lately has been having a fair amount of trouble and are inclined to print out lots of noise) and the author of the SCSI type driver. >ahc0: reading board settings >ahc0: 274x Twin Channel, A SCSI Id=7, B SCSI Id=7, aic7770 >= Rev E, 16 SCBs >ahc0: Downloading Sequencer Program...Done >ahc0 at 0x1000-0x10ff irq 11 on eisa slot 1 >ahc0: Probing channel A >ahc0: target 0 synchronous at 10.0MB/s, offset = 0x19 This is all ahc probe code. The driver is green, and too noisy. Much of this should be buried in "verbose". >(ahc0:0:0): "SEAGATE ST31200N 9022" type 0 fixed SCSI 2 This is from the SCSI bus probe code. Note that it hasn't figured out which driver to use. >sd0(ahc0:0:0): Direct-Access 1006MB (2061108 512 byte sectors) And finally something from the disk code. > I'd rather see something like: (elide ahc probe) >sd0 at ahc0 target 0 unit 0 >sd0: <SEAGATE ST31200N 9022> (1006MB, 2061108 512 byte sectors) You have deferred printing out what you are probing until after you've matched which driver to use, which includes talking to the device (and potentially hanging up for some funky device). The driver matching code goes beyond just looking at the type code, both to permit special drivers for exact device matches and to support devices that report the wrong type (of which we know of several). If you hang up somewhere talking to the device you'll hang without getting the ID string out. The type drivers are also set up to be demand loaded via an LKM, so that is even more stuff that can go wrong before we even know what we're probing (the "sd" string is inside the "sd" driver; we don't even know the name until the match is complete). >(ahc0:0:0): "SEAGATE ST31200N 9022" type 0 fixed SCSI 2 >sd0(ahc0:0:0): Direct-Access 1006MB (2061108 512 byte sectors) Or, since at this point we've probably seen "ahc0:0:0" enough times, maybe: >(ahc0:0:0): "SEAGATE ST31200N 9022" type 0 fixed SCSI 2 >sd0: Direct-Access 1006MB (2061108 512 byte sectors) And if you really want angle brackets just twist my arm and I'll be happy to put them in. > > (Everything else should probably also be hidden under bootverbose.) > > The latter strikes me as more consistent and more BSDish. (We are > still BSD, right? ;) > > (...) >- When I tried to 'wire down' sd0, sd1 and cd0 in my new kernel config, > the system panicked when it went to probe channel B of the 2740T. The > messages I got were: > >ahc0: Probing Channel B >extend_set: entry 0 already has storage >panic: scsi_attachdevs: malloc > > Exactly how does the ahc driver handle the other channel? > I call this a big bug. It looks like it is trying to reuse the same bus structure, and surprise - we already have stuff on that bus. I didn't know about it; when you stumble on something like this please open a bug report using send-pr. -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504291117.HAA13172>