Problem with USB4BSD on DesktopBSD 1.6 (i386)

Steve Anelay steve at anelay.net
Mon Jan 21 10:39:55 PST 2008


Hi Peter

yes, many failed command, always at the umass0:umass_bbb_dump_csw:
CSW ??: sig = 0x53425355 point.  A few goods amongst the fails as well
e.g. 

Jan 17 18:44:45 TekBSD kernel: umass0:umass_cam_action:
11:0:0:XPT_SCSI_IO: cmd: 0x25, flags: 0x40, 10b cmd/8b data/32b sense
Jan 17 18:44:45 TekBSD kernel: umass0:umass_bbb_dump_cbw: CBW 100: cmd =
10b (0x250000000000...), data = 8b, lun = 0, dir = in
Jan 17 18:44:45 TekBSD kernel: umass0:umass_transfer_start: transfer
index = 4
Jan 17 18:44:45 TekBSD kernel: umass0:umass_t_bbb_data_read_callback:
max_bulk=131072, data_rem=8
Jan 17 18:44:45 TekBSD kernel: umass0:umass_t_bbb_data_read_callback:
max_bulk=131072, data_rem=0
Jan 17 18:44:45 TekBSD kernel: umass0:umass_transfer_start: transfer
index = 8
Jan 17 18:44:45 TekBSD kernel: umass0:umass_bbb_dump_csw: CSW 100: sig =
0x53425355 (valid), tag = 0x00000064, res = 0, status = 0x00 (good)
Jan 17 18:44:45 TekBSD kernel: umass0:umass_cam_action:
11:0:0:XPT_SCSI_IO: cmd: 0x1e, flags: 0xc0, 6b cmd/0b data/32b sense
Jan 17 18:44:45 TekBSD kernel: umass0:umass_bbb_dump_cbw: CBW 101: cmd =
6b (0x1e0000000100), data = 0b, lun = 0, dir = out
Jan 17 18:44:45 TekBSD kernel: umass0:umass_transfer_start: transfer
index = 8
Jan 17 18:44:45 TekBSD kernel: umass0:umass_bbb_dump_csw: CSW 101: sig =
0x53425355 (valid), tag = 0x00000065, res = 0, status = 0x01 (failed)

the corsair voyagers are meant to be fast, but the generic one behaves
in the same way.

Steve



More information about the freebsd-usb mailing list