On 02/10/15 10:06, Gary Jennejohn wrote:
On Mon, 09 Feb 2015 22:48:48 +0100
Hans Petter Selasky <h...@selasky.org> wrote:

Hans,

Can you test this change:
https://svnweb.freebsd.org/changeset/base/278477


Thanks, but it doesn't help.  I updated to 278499.

Here's the relevant dmesg output using the new kernel:

Feb 10 09:45:20 ernst kernel: ugen0.4: <vendor 0x152d> at usbus0
Feb 10 09:45:20 ernst kernel: umass0: <vendor 0x152d product 0x0539, class 0/0, 
rev 3.00/28.03, addr 3> on usbus0
Feb 10 09:45:20 ernst kernel: (probe0:umass-sim0:0:0:0): REPORT LUNS. CDB: a0 
00 00 00 00 00 00 00 00 10 00 00
Feb 10 09:45:20 ernst kernel: (probe0:umass-sim0:0:0:0): CAM status: SCSI 
Status Error
Feb 10 09:45:20 ernst kernel: (probe0:umass-sim0:0:0:0): SCSI status: Check 
Condition
Feb 10 09:45:20 ernst kernel: (probe0:umass-sim0:0:0:0): SCSI sense: ILLEGAL 
REQUEST asc:20,0 (Invalid command operation code)
Feb 10 09:45:20 ernst kernel: (probe0:umass-sim0:0:0:0): Error 22, Unretryable 
error
Feb 10 09:45:20 ernst kernel: da0 at umass-sim0 bus 0 scbus8 target 0 lun 0
Feb 10 09:45:20 ernst kernel: da0: <ST320006 41AS 0X03> Fixed Direct Access 
SCSI-6 device
Feb 10 09:45:20 ernst kernel: da0: Serial Number
Feb 10 09:45:20 ernst kernel: da0: 400.000MB/s transfers
Feb 10 09:45:20 ernst kernel: da0: 1907729MB (3907029168 512 byte sectors: 255H 
63S/T 243201C)
Feb 10 09:45:20 ernst kernel: da0: quirks=0x2<NO_6_BYTE>

Note that the vendor/product strings are missing.

I'm not certain whether the failure of REPORT LUNS has anything
to do with my problem, but it seems like a failed SCSI command
shouldn't prevent enumerating the disks in the enclosure.

When the enumeration succeeds I always see da0, da1 and da2.

Note that I tried a slightly older HEAD (from yesterday, so it
already had 278477 in it) with dma_bits forced to 32 and the
enumeration also failed.  So, there's more to my problem than
just the DMA width.  There have been so many changes to CAM
lately that the cause may lie there.


Hi,

Could you run:

usbdump -i usbusX -vvv -s 65535 -f Y

In the failing and working case?

That would reveal what is actually going on in the CAM and USB layers.

Thank you!

--HPS
_______________________________________________
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

Reply via email to