Date: Fri, 11 Jun 1999 16:02:35 -0600 (MDT) From: "Kenneth D. Merry" <ken@plutotech.com> To: gpalmer@FreeBSD.ORG (Gary Palmer) Cc: alpha@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: SPL bug? Message-ID: <199906112202.QAA51435@panzer.plutotech.com> In-Reply-To: <9901.929138223@noop.colo.erols.net> from Gary Palmer at "Jun 11, 1999 05:57:03 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Gary Palmer wrote... > > I just tried putting a newer kernel on the Alphastation I have at > work, and ran into an unusual problem. For months and months, I've had > `boot_osflags' set to include `v'. It seems a kernel from todays > (i.e. fri 11th June) source tree, refuses to boot properly with the > `-v' flag set. Why? Because when its going through listing the SCSI > devices (specifically the pass<n> devices), it seems to not always > register the corresponding da<n> device. e.g., without -v > > da2 at isp0 bus 0 target 2 lun 0 > da2: <SEAGATE ST15150W 0017> Fixed Direct Access SCSI-2 device > da2: 20.000MB/s transfers (10.000MHz, offset 12, 16bit), Tagged Queueing Enabled > da2: 4095MB (8388315 512 byte sectors: 255H 63S/T 522C) > da1 at isp0 bus 0 target 1 lun 0 > da1: <SEAGATE ST15150W 0022> Fixed Direct Access SCSI-2 device > da1: 20.000MB/s transfers (10.000MHz, offset 12, 16bit), Tagged Queueing Enabled > da1: 4095MB (8388315 512 byte sectors: 255H 63S/T 522C) > da0 at isp0 bus 0 target 0 lun 0 > da0: <DEC RZ28D (C) DEC 0010> Fixed Direct Access SCSI-2 device > da0: 20.000MB/s transfers (10.000MHz, offset 12, 16bit), Tagged Queueing Enabled > da0: 2007MB (4110480 512 byte sectors: 255H 63S/T 255C) > cd0 at isp0 bus 0 target 5 lun 0 > cd0: <DEC RRD45 (C) DEC 1645> Removable CD-ROM SCSI-2 device > cd0: 4.032MB/s transfers (4.032MHz, offset 12) > cd0: Attempt to query device size failed: NOT READY, Medium not present > > However, with -v, it would never register all the da<n> devices, it > would print out the large ammount of info from pass<n>, and > OCCASIONALLY see one or two of the disks as da<n>, but never all of > them. > > The only guess that I have is that while the SCSI layer is printing > the pass info, its blocking da<n> registration (like I said, this is a > guess, I don't understand all the ins-and-outs of CAM). Since the > console on this box is a 9600 baud serial console, printing the > pass<n> diags takes a non-trivial ammount of time. Without the diags, > the system works fine. How does the system not work with -v is turned on? It "refuses to boot properly" doesn't really come close to describing the problem. I think the disappearing messages can probably be traced to your 9600 baud console. My guess is that some of the messages are getting dropped. Matt Jacob had a similar problem one time, I think. Ken -- Kenneth Merry ken@plutotech.com 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?199906112202.QAA51435>