Date: Fri, 28 Apr 1995 23:22:48 -0700 From: "Justin T. Gibbs" <gibbs@estienne.CS.Berkeley.EDU> To: "House of Debuggin'" <wpaul@skynet.ctr.columbia.edu> Cc: faulkner@mpd.tandem.com, kelly@fsl.noaa.gov, hackers@FreeBSD.org, jkh@time.cdrom.com, root@morton.cdrom.com Subject: Re: What I'd *really like* for 2.0.5 Message-ID: <199504290622.XAA29018@estienne.cs.berkeley.edu> In-Reply-To: Your message of "Fri, 28 Apr 1995 22:02:48 EDT." <199504290202.WAA02751@skynet.ctr.columbia.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
>- The printf()s from the slicing code irritate the hell out of me: > >sd0s4: type 0xa5, start 32, end = 2061107, size 2061076 >sd0s4: C/H/S start 0/1/1 (20) != start 32: invalid >sd0s4: C/H/S end 1006/25/20 (523639) != end 2061107: invalid >sd0: rejecting partition in BSD label: it isn't entirely within the slice >sd0: start 32, end 2061107, size 2061076 >sd0d: start 0, end 2061107, size 2061108 >[same thing repeated 2 more times] > > I installed FreeBSD on slice four, using the default values provided > by the install program. In spite of these ominous warnings, the system > seems to work fine. I think I know what it's telling me, but I'm not > in the mood to fiddle with the thing now that I have it working. > Regardless, I have this terrible urge to sweep this all under > bootverbose. Its experimental code. The printfs will die when Bruce believes the code to be stable or you make all of your partitions conform to where the slice code says they should be. Your problem is that you installed using the old sysinstall which is not "slice aware". >- The SCSI disk probe messages also irritate the hell out of me: > >ahc0: reading board settings >ahc0: 274x Twin Channel, A SCSI Id=7, B SCSI Id=7, aic7770 >= Rev E, 16 SCBs All of the information on this line is currently relevent because the driver is "green". Most people don't know if they have a Rev E aic7770 or not (in fact, its not even printed on the chip) and I need to know this when I get bug reports. >ahc0: Downloading Sequencer Program...Done This should go. >ahc0 at 0x1000-0x10ff irq 11 on eisa slot 1 >ahc0: Probing channel A >ahc0: target 0 synchronous at 10.0MB/s, offset = 0x19 >(ahc0:0:0): "SEAGATE ST31200N 9022" type 0 fixed SCSI 2 >sd0(ahc0:0:0): Direct-Access 1006MB (2061108 512 byte sectors) > > I'd rather see something like: > >ahc0 at 0x1000-0x10ff irq 11 on eisa slot 1 >aha0: <Adaptec 274x Twin Channel> >ahc0: Probing channel A >ahc0: target 0 synchronous at 10.0MB/s, offset = 0x19 >sd0 at ahc0 target 0 unit 0 >sd0: <SEAGATE ST31200N 9022> (1006MB, 2061108 512 byte sectors) > > (Everything else should probably also be hidden under bootverbose.) > > The latter strikes me as more consistent and more BSDish. (We are > still BSD, right? ;) > > I may be overly critical here, but the last time I saw a Linux > box boot, I was stunned by the jumble of inconsistent probe messages > that it generated. Every driver author seemed to have his own idea > of what the probe messages should look like, and I hated all of them. A linux boot and a FreeBSD boot don't even come close to being in the same league. Your nits are to a driver that is just becoming stable and slice code that needs more testing before the debugging info gets swept under the bootverbose flag or more likely a kernel #ifdef. >- 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? It registers it as another scsibus. > If ahc0:0:0 on channel A is sd0, what does that make ahc0:0:0 on channel B? > Maybe I should be disabling channel B since I have no devices on it? ahc0:0:0 is not specific enough. It should really be: scsibus0:0:0 and scsibus1:0:0 I'll talk to Peter Dufault about it. It doesn't make sense to increment both the unit number of the device and the bus because they are on one contoller. >-Bill > >-- >~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~T~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >-Bill Paul (212) 854-6020 | System Manager >Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research >Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City >~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >The Møøse Illuminati: ignore it and be confused, or join it and be confusing! >~~~~~~~~~ FreeBSD 2.1: "We can kick your operating system's ass!" ~~~~~~~~~~ -- Justin T. Gibbs ============================================== TCS Instructional Group - Programmer/Analyst 1 Cory | Po | Danube | Volga | Parker | Torus ==============================================
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504290622.XAA29018>