Re: USB umass device not working on -current

Hans Petter Selasky schrieb am 09.08.2009 15:20 (localtime):
...
> Can you try attaching at FULL speed?
> 
> sysctl hw.usb.ehci.no_hs=1

Thanks for your quick response!

Here's what I get with high-speed disabled:
Aug  9 22:15:35 titan root: Unknown USB device: vendor 0x04e8 product 
0x5050 bus uhub1
Aug  9 22:15:35 titan kernel: ugen1.2: <Samsung> at usbus1
Aug  9 22:15:36 titan kernel: umass1: <Internal Device> on usbus1
Aug  9 22:15:36 titan kernel: umass1:  SCSI over Bulk-Only; quirks = 0x0110
Aug  9 22:15:40 titan kernel: umass1:umass_init_shuttle: Shuttle init 
returned 0x0000
Aug  9 22:15:41 titan kernel: umass1:umass_cam_action: 
11:-1:-1:XPT_PATH_INQ:.
Aug  9 22:15:41 titan kernel: umass1:11:1:-1: Attached to scbus11
Aug  9 22:15:41 titan kernel: umass1:umass_cam_rescan: scbus11: scanning 
for 11:1:-1
Aug  9 22:15:41 titan kernel: umass1:umass_cam_action: 
11:-1:-1:XPT_PATH_INQ:.
Aug  9 22:15:41 titan kernel: umass1:umass_cam_action: 11:0:0:XPT_PATH_INQ:.
Aug  9 22:15:41 titan kernel: umass1:umass_cam_action: 11:0:0:XPT_PATH_INQ:.
Aug  9 22:15:41 titan kernel: umass1:umass_cam_action: 
11:0:0:XPT_GET_TRAN_SETTINGS:.
Aug  9 22:15:41 titan kernel: umass1:umass_cam_action: 
11:0:0:XPT_SET_TRAN_SETTINGS:.
Aug  9 22:15:41 titan kernel: umass1:umass_cam_action: 11:0:0:XPT_PATH_INQ:.
Aug  9 22:15:41 titan kernel: umass1:umass_cam_action: 11:0:0:XPT_PATH_INQ:.
Aug  9 22:15:41 titan kernel: umass1:umass_cam_action: 
11:0:0:XPT_SCSI_IO: cmd: 0x12, flags: 0x40, 6b cmd/36b data/18b sense
Aug  9 22:15:41 titan kernel: umass1:umass_attach: Attach 
finishedumass1:umass_bbb_dump_cbw: CBW 1: cmd = 6b (0x120000002400), 
data = 36b, lun = 0, dir = in
Aug  9 22:15:41 titan kernel:
Aug  9 22:15:41 titan kernel: umass1:umass_transfer_start: transfer 
index = 4
Aug  9 22:15:41 titan kernel: umass1:umass_t_bbb_data_read_callback: 
max_bulk=131072, data_rem=36
Aug  9 22:15:41 titan kernel: umass1:umass_t_bbb_data_read_callback: 
max_bulk=131072, data_rem=0
Aug  9 22:15:41 titan kernel: umass1:umass_transfer_start: transfer 
index = 8
Aug  9 22:15:41 titan kernel: umass1:umass_bbb_dump_csw: CSW 1: sig = 
0x53425355 (valid), tag = 0x00000001, res = 0, status = 0x00 (good)
Aug  9 22:15:41 titan kernel: umass1:umass_cam_action: 
11:0:0:XPT_SCSI_IO: cmd: 0x12, flags: 0x40, 6b cmd/56b data/18b sense
Aug  9 22:15:41 titan kernel: umass1:umass_bbb_dump_cbw: CBW 2: cmd = 6b 
(0x120000003800), data = 56b, lun = 0, dir = in
Aug  9 22:15:41 titan kernel: umass1:umass_transfer_start: transfer 
index = 4
Aug  9 22:15:41 titan kernel: umass1:umass_t_bbb_data_read_callback: 
max_bulk=131072, data_rem=56
Aug  9 22:15:41 titan kernel: umass1:umass_t_bbb_data_read_callback: 
max_bulk=131072, data_rem=0
Aug  9 22:15:41 titan kernel: umass1:umass_transfer_start: transfer 
index = 8
Aug  9 22:15:41 titan kernel: umass1:umass_bbb_dump_csw: CSW 2: sig = 
0x53425355 (valid), tag = 0x00000002, res = 0, status = 0x00 (good)
Aug  9 22:15:41 titan kernel: umass1:umass_cam_action: 11:0:0:XPT_PATH_INQ:.
Aug  9 22:15:41 titan kernel: umass1:umass_cam_action: 11:0:0:XPT_PATH_INQ:.
Aug  9 22:15:41 titan kernel: umass1:umass_cam_action: 
11:0:0:XPT_GET_TRAN_SETTINGS:.
Aug  9 22:15:41 titan kernel: umass1:umass_cam_action: 
11:0:0:XPT_SET_TRAN_SETTINGS:.
Aug  9 22:15:41 titan kernel: umass1:umass_cam_action: 
11:0:0:XPT_SCSI_IO: cmd: 0x12, flags: 0x40, 6b cmd/255b data/18b sense
Aug  9 22:15:41 titan kernel: umass1:umass_bbb_dump_cbw: CBW 3: cmd = 6b 
(0x12010000ff00), data = 255b, lun = 0, dir = in
Aug  9 22:15:41 titan kernel: umass1:umass_transfer_start: transfer 
index = 4
Aug  9 22:15:41 titan kernel: umass1:umass_t_bbb_data_read_callback: 
max_bulk=131072, data_rem=255
Aug  9 22:15:41 titan kernel: umass1:umass_transfer_start: transfer 
index = 5
Aug  9 22:15:46 titan kernel: umass1:umass_tr_error: transfer error, 
USB_ERR_TIMEOUT -> reset
Aug  9 22:15:46 titan kernel: umass1:umass_cam_action: 
11:0:0:XPT_SCSI_IO: cmd: 0x12, flags: 0x40, 6b cmd/255b data/18b sense
Aug  9 22:15:46 titan kernel: umass1:umass_t_bbb_reset1_callback: BBB reset!
Aug  9 22:15:47 titan kernel: umass1:umass_tr_error: transfer error, 
USB_ERR_STALLED -> reset
Aug  9 22:15:47 titan kernel: umass1:umass_cam_action: 
11:0:0:XPT_SCSI_IO: cmd: 0x12, flags: 0x40, 6b cmd/255b data/18b sense
Aug  9 22:15:47 titan kernel: umass1:umass_t_bbb_reset1_callback: BBB reset!

> Another idea is that your device does not support certain SCSI commands, and 
> will crash upon any non-support command.

Hmm, if I remember correctly there was some quirk file with devices that 
need special treatment. Is it still the same? Maybe there has been an 
entry for my player which got lost. Or should the new code auto-detect 
such devices? How's redmond treating such devices? Needless to say that 
the player doesn't crash on windows, nor does windows crash ;)

Thanks,

-Harry