Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 7 Aug 2000 17:58:24 -0700 (PDT)
From:      Kelly Yancey <kbyanc@egroups.net>
To:        Matthew Jacob <mjacob@feral.com>
Cc:        freebsd-scsi@freebsd.org
Subject:   Re: Using the ses driver
Message-ID:  <Pine.BSF.4.21.0008071750350.24356-100000@kbyanc.corp.ONElist.com>
In-Reply-To: <Pine.BSF.4.10.10008071710070.85898-100000@beppo.feral.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 7 Aug 2000, Matthew Jacob wrote:

> 
> 
> Yuck. Looks like this box doesn't like VPD Inquiries- that'll need a patch in
> cam_xpt.c. It also doesn't like a Mode Sense either. But neitehr should fatal.

  Would you like a PR? :)

> 
> Interesting- you've got a JMR JBOD, cool! Mine (fibre channel) nevr seems to
> want to show up- it's really annoying. I think I actually may have the unit
> that *doesn't* have the SES module.
> 
> So- did you add
> 
> 	device ses0
> 
> and remove
> 
> 	device pt0
> 
> from your config file? The latter step shouldn't be *required*, but it would
> clarify some confusion.
> 
> Because it's showing up as a Processor device, it'll actually be SAF-TE
> instead of SES, so you'll see something like:
> 
> ses0 at isp1 bus 0 target 15 lun 0
> ses0: <SYMBIOS  2> Fixed Processor SCSI-2 device
> ses0: Serial Number 1
> ses0: 3.300MB/s transfers
> ses0: SAF-TE Compliant Device

  Yep. Worked like a charm when we took out pt0. Apparently this model
does have it. :)

> 
> The one thing required for SAF-TE to actually be probed out correctly is for
> the second Inquiry command that comes in and does a longer read of Inquiry
> data- bytes 44..47 contain info that says that this Processor type device is a
> SAF-TE compliant device.
> 
> -matt
> 

  Thanks,

  Kelly

> 
> On Mon, 7 Aug 2000, Kelly Yancey wrote:
> 
> > 
> >   We're trying to configure a 4.1-stable box with the ses driver to talk
> > to a Chaparrel RAID. However, after rebuilding the kernel with the ses
> > driver and MAKEDEV'ing a few ses devices, we still get:
> > 	# pwd
> > 	/usr/share/examples/ses/getencstat
> > 	# ./getencstat /dev/ses0
> > 	/dev/ses0: Device not configured
> > 
> >   There is nothing in the dmesg about ses. All we have is:
> > 
> > Waiting 5 seconds for SCSI devices to settle
> > (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered.
> > (probe0:sym0:0:0:0): INQUIRY. CDB: 12 1 80 0 ff 0 
> > (probe0:sym0:0:0:0): ILLEGAL REQUEST asc:24,0
> > (probe0:sym0:0:0:0): Invalid field in CDB
> > (probe0:sym0:0:0:1): Vendor Specific Command. CDB: 1a 20 a 0 14 0 
> > (probe0:sym0:0:0:1): ILLEGAL REQUEST asc:20,0
> > (probe0:sym0:0:0:1): Invalid command operation code
> > (probe0:sym0:0:0:1): INQUIRY. CDB: 12 21 80 0 ff 0 
> > (probe0:sym0:0:0:1): ILLEGAL REQUEST asc:24,0
> > (probe0:sym0:0:0:1): Invalid field in CDB
> > Creating DISK da0
> > pt0 at sym0 bus 0 target 0 lun 1
> > pt0: <CHAPTEC G5312 GV22> Fixed Processor SCSI-2 device 
> > pt0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing
> > Enabled
> > pt1 at sym0 bus 0 target 5 lun 0
> > pt1: <JMR ELEC FORTRA SERIES. 1.00> Fixed Processor SCSI-2 device 
> > pt1: Serial Number 1
> > pt1: 3.300MB/s transfers
> > pass0 at sym0 bus 0 target 0 lun 0
> > pass0: <CHAPTEC G5312 GV22> Fixed Direct Access SCSI-2 device 
> > pass0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing
> > Enabl
> > ed
> > pass1 at sym0 bus 0 target 0 lun 1
> > pass1: <CHAPTEC G5312 GV22> Fixed Processor SCSI-2 device 
> > pass1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing
> > Enabl
> > ed
> > pass2 at sym0 bus 0 target 5 lun 0
> > pass2: <JMR ELEC FORTRA SERIES. 1.00> Fixed Processor SCSI-2 device 
> > pass2: Serial Number 1
> > pass2: 3.300MB/s transfers
> > da0 at sym0 bus 0 target 0 lun 0
> > da0: <CHAPTEC G5312 GV22> Fixed Direct Access SCSI-2 device 
> > da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing
> > Enabled
> > da0: 277227MB (567761920 512 byte sectors: 255H 63S/T 35341C)
> > 
> >   What are we missing? Thanks,
> > 
> >   Kelly
> > 
> 



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?Pine.BSF.4.21.0008071750350.24356-100000>