Date: Tue, 2 May 1995 14:30:05 -0700 From: Peter Dufault <dufault@hda.com> To: freebsd-bugs Subject: kern/377: Can't config any but first bus of a host adapter Message-ID: <199505022130.OAA16589@freefall.cdrom.com> In-Reply-To: Your message of Tue, 2 May 1995 17:19:54 -0400 <199505022119.RAA00698@hda.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>Number: 377 >Category: kern >Synopsis: Can't config any but first bus of a host adapter >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue May 2 14:30:03 1995 >Originator: Peter & >Organization: Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 >Release: FreeBSD 2.1.0-Development i386 >Environment: >Description: You can not configure a device on the second bus of a multiple bus adapter. scsiconf uses a "key" of (host adapter, unit) to tell what belongs on a given bus, and if the device on the second bus collides with a device on the first bus the device slot allocation will fail and the system will panic during boot. >How-To-Repeat: Try to configure a device on the second bus that collides with something on the first bus and boot. >Fix: Work around: Don't try to configure the devices, but live with the "autocounting" devices; Real fix: Modify config to support a new keyword so that you can do things like: controller scbus0 at aic0 bus 0 controller scbus2 at ahc0 bus 1 and modify scsiconf to use (host adapter, unit, bus) as the key. >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199505022130.OAA16589>