kern/102612: da0 not detected when sharing bus with ch0 device on 2100s controller

[Adam Ulmer]

The following reply was made to PR kern/102612; it has been noted by GNATS.

From: Adam Ulmer <fbsd at globalmegahost.com>
To: Cc: bug-followup at FreeBSD.org, freebsdreport at yahoo.com
Subject: Re: kern/102612: da0 not detected when sharing bus with ch0 device
 on 2100s controller
Date: Thu, 28 Sep 2006 20:33:18 +0000 (GMT)

 The fix for this, in my case, is to remove the asr(4) zero channel raid
 controller.  Without the asr(4) device to muck things up, freebsd can
 access both scsi channels and see the hard drives on the first bus and
 access the lto-3 tape drive and jukebox on the second bus.
 
 This is the second time asr(4) has bitten me.
 
 Adam Ulmer
 
 On Wed, 27 Sep 2006, Adam Ulmer wrote:
 
 > I'm having a similar problem with slightly different hardware.
 >
 > Environment:
 >
 >  - FreeBSD 6.1-RELEASE-p6 #2: Tue Sep 12 09:30:07 MDT 2006 i386
 >  - kernel compiled with "options ASR_COMPAT"
 >  - Adaptec 2015S Zero-channel raid controller
 >  - Motherboard has two scsi channels (one internal, one external)
 >  - HP Storageworks MSL2024 Tape Library (one LTO-3 drive)
 >
 > Description:
 >
 > The loader cannot see devices on the first scsi bus when the changer is
 > attached to the second bus.
 >
 > Console capture with jukebox powered up, ses0 and da0 are not found.
 > ---------------------
 > [snip]
 > asr0: <Adaptec Caching SCSI RAID> mem
 > 0xf8300000-0xf83fffff,0xfb000000-0xfbffffff,0xfc000000-0xfdffffff irq 30 at device 3.0 on pci3
 > asr0: [GIANT-LOCKED]
 > asr0: ADAPTEC 2015S FW Rev. 3B0A, 2 channel, 256 CCBs, Protocol I2O
 > [snip]
 > sa0 at asr0 bus 1 target 10 lun 0
 > sa0: <HP Ultrium 3-SCSI G54W> Removable Sequential Access SCSI-3 device
 > sa0: Tagged Queueing Enabled
 > ch0 at asr0 bus 1 target 10 lun 1
 > ch0: <HP MSL G3 Series 2.40> Removable Changer SCSI-5 device
 > ch0: Tagged Queueing Enabled
 > ch0: 23 slots, 1 drive, 1 picker, 1 portal
 > Trying to mount root from ufs:/dev/da0s1a
 >
 > Manual root filesystem specification:
 >   <fstype>:<device>  Mount <device> using filesystem <fstype>
 >                        eg. ufs:da0s1a
 >   ?                  List valid disk boot devices
 >   <empty line>       Abort manual input
 >
 > mountroot> ?
 >
 > List of GEOM managed disk devices:
 >   acd0 fd0
 > ---------------------
 >
 > Console capture with jukebox powered down, ses0 and da0 are found.
 > ---------------------
 > [snip]
 > asr0: <Adaptec Caching SCSI RAID> mem
 > 0xf8300000-0xf83fffff,0xfb000000-0xfbffffff,0xfc000000-0xfdffffff irq 30 at device 3.0 on pci3
 > asr0: [GIANT-LOCKED]
 > asr0: ADAPTEC 2015S FW Rev. 3B0A, 2 channel, 256 CCBs, Protocol I2O
 > [snip]
 > ses0 at asr0 bus 0 target 6 lun 0
 > ses0: <SUPER GEM318 0> Fixed Processor SCSI-2 device
 > ses0: SAF-TE Compliant Device
 > da0 at asr0 bus 0 target 0 lun 0
 > da0: <ADAPTEC RAID-5 3B0A> Fixed Direct Access SCSI-2 device
 > da0: Tagged Queueing Enabled
 > da0: 70006MB (143372288 512 byte sectors: 255H 63S/T 8924C)
 > Trying to mount root from ufs:/dev/da0s1a
 > Loading configuration files.
 > [snip]
 > ---------------------
 >
 > The puzzling thing is that the changer is on the second bus while da0 and
 > ses0 are on the first channel (bus).
 >
 > Adam Ulmer
 >