Re: Multimedia keys on Dell SK-8135
On Thursday 25 November 2010 04:42:30 Peter Jeremy wrote: I have a Dell SK-8135 keyboard which has multimedia keys in addition to the normal PC105 keyboard. As far as I can tell (by setting hw.usb.debug, hw.usb.ugen.debug, hw.usb.uhid.debug and hw.usb.ukbd.debug), the keys aren't generating any output. I've done some searching and it looks like some people have had sucess getting the keys to work, at least on Linux, though it's not clear how. Can anyone help? The keyboard includes an integrated hub and I have my mouse plugged into it. I'm running FreeBSD-8.1/amd64 Have you looked at: http://wiki.freebsd.org/uhidd --HPS Relevant output: dmesg: ugen0.2: Dell at usbus0 uhub6: Dell USB Keyboard Hub on usbus0 uhub6: 3 ports with 2 removable, bus powered ugen0.3: Dell at usbus0 ukbd0: Dell USB Keyboard on usbus0 kbd0 at ukbd0 uhid0: Dell USB Keyboard on usbus0 ugen0.4: vendor 0x413c at usbus0 ums0: vendor 0x413c product 0x3010, class 0/0, rev 2.00/2.30, addr 4 on usbus0 ums0: 3 buttons and [XYZ] coordinates ID=0 $ usbconfig ugen0.1: UHCI root HUB Intel at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen1.1: UHCI root HUB Intel at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen2.1: UHCI root HUB Intel at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen3.1: UHCI root HUB Intel at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen4.1: EHCI root HUB Intel at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen4.2: USB2.0 Hub Controller NEC Corporation at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen0.2: Dell USB Keyboard Hub Dell at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen0.3: Dell USB Keyboard Dell at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen0.4: product 0x3010 vendor 0x413c at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON $ usbconfig -u 0 -a 3 dump_device_desc ugen0.3: Dell USB Keyboard Dell at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0110 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0008 idVendor = 0x413c idProduct = 0x2010 bcdDevice = 0x0200 iManufacturer = 0x0001 Dell iProduct = 0x0003 Dell USB Keyboard iSerialNumber = 0x no string bNumConfigurations = 0x0001 $ usbconfig -u 0 -a 3 dump_curr_config_desc ugen0.3: Dell USB Keyboard Dell at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x003b bNumInterfaces = 0x0002 bConfigurationValue = 0x0001 iConfiguration = 0x0003 Dell USB Keyboard bmAttributes = 0x00a0 bMaxPower = 0x0019 Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x bAlternateSetting = 0x bNumEndpoints = 0x0001 bInterfaceClass = 0x0003 bInterfaceSubClass = 0x0001 bInterfaceProtocol = 0x0001 iInterface = 0x0003 Dell USB Keyboard Additional Descriptor bLength = 0x09 bDescriptorType = 0x21 bDescriptorSubType = 0x10 RAW dump: 0x00 | 0x09, 0x21, 0x10, 0x01, 0x00, 0x01, 0x22, 0x41, 0x08 | 0x00 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0081 IN bmAttributes = 0x0003 INTERRUPT wMaxPacketSize = 0x0008 bInterval = 0x000a bRefresh = 0x bSynchAddress = 0x Interface 1 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0001 bAlternateSetting = 0x bNumEndpoints = 0x0001 bInterfaceClass = 0x0003 bInterfaceSubClass = 0x bInterfaceProtocol = 0x iInterface = 0x0003 Dell USB Keyboard Additional Descriptor bLength = 0x09 bDescriptorType = 0x21 bDescriptorSubType = 0x10 RAW dump: 0x00 | 0x09, 0x21, 0x10, 0x01, 0x00, 0x01, 0x22, 0x8e, 0x08 | 0x00 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0082 IN bmAttributes = 0x0003 INTERRUPT wMaxPacketSize = 0x0004 bInterval = 0x00ff bRefresh = 0x bSynchAddress = 0x ___ 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
selecting configuration
I have a USB device with two alternative configurations. After enumerating the device I need to switch the device to configuration 1 via usbconfig. Do we have any kind of support to do this automatically? -- B.Walter be...@bwct.de http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. ___ 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
Re: selecting configuration
On Thursday 25 November 2010 13:30:18 Bernd Walter wrote: I have a USB device with two alternative configurations. After enumerating the device I need to switch the device to configuration 1 via usbconfig. Do we have any kind of support to do this automatically? Yes, see the USB quirks. UQ_CFG_INDEX_1 --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
Re: selecting configuration
On Thu, Nov 25, 2010 at 02:37:31PM +0100, Hans Petter Selasky wrote: On Thursday 25 November 2010 13:30:18 Bernd Walter wrote: I have a USB device with two alternative configurations. After enumerating the device I need to switch the device to configuration 1 via usbconfig. Do we have any kind of support to do this automatically? Yes, see the USB quirks. UQ_CFG_INDEX_1 Ok - this is something to be compiled into the kernel - right? Is it possible to add a quirk with usbconfig after the device is already detected? devd won't work since it won't say anything as config 0 won't attach to any driver and ugen isn't listed there. Also the devd data would be missing the bus number. -- B.Walter be...@bwct.de http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. ___ 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
Re: selecting configuration
On Thursday 25 November 2010 16:50:46 Bernd Walter wrote: On Thu, Nov 25, 2010 at 02:37:31PM +0100, Hans Petter Selasky wrote: On Thursday 25 November 2010 13:30:18 Bernd Walter wrote: I have a USB device with two alternative configurations. After enumerating the device I need to switch the device to configuration 1 via usbconfig. Do we have any kind of support to do this automatically? Yes, see the USB quirks. UQ_CFG_INDEX_1 Hi, Ok - this is something to be compiled into the kernel - right? Is it possible to add a quirk with usbconfig after the device is already detected? You can load the usb_quirk.ko. Plug the device and run: usbconfig -d x.y add_quirk quirk At next plug the setting is remembered. devd won't work since it won't say anything as config 0 won't attach to any driver and ugen isn't listed there. Also the devd data would be missing the bus number. --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
Re: External usb HDD disconnects, system gets messed up
On Thu, Nov 25, 2010 at 09:40:19AM +0100, Hans Petter Selasky wrote: On Thursday 25 November 2010 03:55:26 Nezmer wrote: Hi, FreeBSD 8.1-STABLE r215402M GENERIC amd64 I'm having a weird issue. I have a 300GB external usb HDD with one ext2 partition. I use ZFS for my internal HDD. Almost daily, The usb HDD disconnects(according to dmesg) and the system gets messed up. Running processes keep responding but they would not exit. And no new processes would start running. I eventually would have to hard reset and run fsck.ext2 on the next run. Any idea what's going on? Do you need any specific information? Hi, When this hang happens you can try to turn on umass debugging: sysctl hw.usb.umass.debug=-1 You need this option in your kernel config or when building the umass module to enable the sysctl above: options USB_DEBUG --HPS Thank you for the hint. I managed to freeze the system this time. 1st, I tried to cd to a dir and got an I/O error. Here is some debug output: umass0:umass_bbb_dump_csw: CSW 208387: sig = 0x53425355 (valid), tag = 0x00032e03, res = 4096, status = 0x01 (failed) umass0:umass_t_bbb_status_callback: Command failed, residue = 4096 umass0:umass_cam_cb: Fetching 32 bytes of sense data umass0:umass_bbb_dump_cbw: CBW 208388: cmd = 6b (0x03002000), data = 32b, lun = 0, dir = in umass0:umass_transfer_start: transfer index = 4 umass0:umass_t_bbb_data_read_callback: max_bulk=131072, data_rem=32 umass0:umass_t_bbb_data_read_callback: max_bulk=131072, data_rem=0 umass0:umass_transfer_start: transfer index = 8 umass0:umass_t_bbb_status_callback: Failed to read CSW: USB_ERR_STALLED, try 0 umass0:umass_transfer_start: transfer index = 5 umass0:umass_transfer_start: transfer index = 8 umass0:umass_bbb_dump_csw: CSW 208388: sig = 0x53425355 (valid), tag = 0x00032e04, res = 14, status = 0x00 (good) (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 0 30 57 0 0 8 0 (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI status: Check Condition (da0:umass-sim0:0:0:0): SCSI sense: UNIT ATTENTION asc:28,0 (Not ready to ready change, medium may have changed) umass0:umass_cam_action: 2:0:0:XPT_SCSI_IO: cmd: 0x28, flags: 0x40, 10b cmd/4096b data/32b sense umass0:umass_bbb_dump_cbw: CBW 208389: cmd = 10b (0x28003057...), data = 4096b, lun = 0, dir = in umass0:umass_transfer_start: transfer index = 4 umass0:umass_t_bbb_data_read_callback: max_bulk=131072, data_rem=4096 umass0:umass_transfer_start: transfer index = 5 umass0:umass_transfer_start: transfer index = 8 umass0:umass_bbb_dump_csw: CSW 208389: sig = 0x53425355 (valid), tag = 0x00032e05, res = 4096, status = 0x01 (failed) umass0:umass_t_bbb_status_callback: Command failed, residue = 4096 umass0:umass_cam_cb: Fetching 32 bytes of sense data umass0:umass_bbb_dump_cbw: CBW 208390: cmd = 6b (0x03002000), data = 32b, lun = 0, dir = in umass0:umass_transfer_start: transfer index = 4 umass0:umass_t_bbb_data_read_callback: max_bulk=131072, data_rem=32 umass0:umass_t_bbb_data_read_callback: max_bulk=131072, data_rem=0 umass0:umass_transfer_start: transfer index = 8 umass0:umass_t_bbb_status_callback: Failed to read CSW: USB_ERR_STALLED, try 0 umass0:umass_transfer_start: transfer index = 5 umass0:umass_transfer_start: transfer index = 8 umass0:umass_bbb_dump_csw: CSW 208390: sig = 0x53425355 (valid), tag = 0x00032e06, res = 14, status = 0x00 (good) (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 0 30 57 0 0 8 0 (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI status: Check Condition (da0:umass-sim0:0:0:0): SCSI sense: UNIT ATTENTION asc:28,0 (Not ready to ready change, medium may have changed) umass0:umass_cam_action: 2:0:0:XPT_SCSI_IO: cmd: 0x28, flags: 0x40, 10b cmd/4096b data/32b sense umass0:umass_bbb_dump_cbw: CBW 208391: cmd = 10b (0x28003057...), data = 4096b, lun = 0, dir = in umass0:umass_transfer_start: transfer index = 4 umass0:umass_t_bbb_data_read_callback: max_bulk=131072, data_rem=4096 umass0:umass_transfer_start: transfer index = 5 umass0:umass_transfer_start: transfer index = 8 umass0:umass_bbb_dump_csw: CSW 208391: sig = 0x53425355 (valid), tag = 0x00032e07, res = 4096, status = 0x01 (failed) umass0:umass_t_bbb_status_callback: Command failed, residue = 4096 umass0:umass_cam_cb: Fetching 32 bytes of sense data umass0:umass_bbb_dump_cbw: CBW 208392: cmd = 6b (0x03002000), data = 32b, lun = 0, dir = in umass0:umass_transfer_start: transfer index = 4 umass0:umass_t_bbb_data_read_callback: max_bulk=131072, data_rem=32 umass0:umass_t_bbb_data_read_callback: max_bulk=131072, data_rem=0 umass0:umass_transfer_start: transfer index = 8 umass0:umass_t_bbb_status_callback: Failed to read CSW: USB_ERR_STALLED, try 0 umass0:umass_transfer_start: transfer index = 5 umass0:umass_transfer_start: transfer index = 8 umass0:umass_bbb_dump_csw: CSW 208392: sig = 0x53425355 (valid), tag = 0x00032e08, res = 14, status = 0x00
Re: USB controller error logged when resuming after suspend
On Sun, Nov 14, 2010 at 3:36 PM, Bruce Cran br...@cran.org.uk wrote: I've been trying to get my laptop working with suspend/resume. It comes back, but USB seems rather unhappy about something for a while. Despite this, plugging a flash drive in does attach to the EHCI controller at usbus6. You have better luck than me! On my system, port 2 reset fails, port is disabled, an none of my external ports work at all, like this: [SNIP] uhub_reattach_port: port 2 reset failed, error=USB_ERR_TIMEOUT uhub_reattach_port: device problem (USB_ERR_TIMEOUT), disabling port 2 [SNIP] It's becoming more well known that the USB stack isn't suspend/resume safe at this point. Have you tried building your USB systems as kernel modules and unloading/loading them via /etc/rs.suspend|resume? I used to have luck doing that here, but recently that has broken as well (running HEAD). Also, it's been my experience that multiple suspend/resume cycles can permanently shut down your ports... -Brandon ___ 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
Re: Multimedia keys on Dell SK-8135
[adding kaiw@ as per the wiki page] On 2010-Nov-25 09:38:15 +0100, Hans Petter Selasky hsela...@c2i.net wrote: On Thursday 25 November 2010 04:42:30 Peter Jeremy wrote: I have a Dell SK-8135 keyboard which has multimedia keys in addition ... http://wiki.freebsd.org/uhidd Thanks. I didn't think to search for multimedia keyboards in general. I've tried uhidd and, using it to manage the multimedia keys, it mostly works. I want to use ukbd because I want a functioning keyboard in single-user mode and my mouse didn't get cleanly handled so I switched back to ums (which handles all my mouse functions). The bit that doesn't work is the volume control: The knob returns a HID code and a 7-bit 2-complement number defining the direction and rate (ie '1' is one click up, '127' is one click down). Unfortunately, xev shows that as soon as I move the volume control, I start receiving a continuous stream of alternating KeyPress and KeyRelease events until I kill uhidd. I have attached my uhidd.conf file and the debug output from uhidd (the second execution shows the effect of turning the volume control faster). Sample output from xev showing the volume control events: KeyPress event, serial 27, synthetic NO, window 0x101, root 0x120, subw 0x0, time 7007489, (172,122), root:(913,147), state 0x0, keycode 191 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 27, synthetic NO, window 0x101, root 0x120, subw 0x0, time 7007530, (172,122), root:(913,147), state 0x0, keycode 191 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 27, synthetic NO, window 0x101, root 0x120, subw 0x0, time 7007530, (172,122), root:(913,147), state 0x0, keycode 191 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 27, synthetic NO, window 0x101, root 0x120, subw 0x0, time 7007571, (172,122), root:(913,147), state 0x0, keycode 191 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 27, synthetic NO, window 0x101, root 0x120, subw 0x0, time 7007571, (172,122), root:(913,147), state 0x0, keycode 191 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 27, synthetic NO, window 0x101, root 0x120, subw 0x0, time 7007612, (172,122), root:(913,147), state 0x0, keycode 191 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False -- Peter Jeremy Script started on Fri Nov 26 14:30:49 2010 # uhidd -vvv /dev/ugen1.3 ugen1.3[0]- HID interface ugen1.3[0]- Report descriptor size = 65 ugen1.3[0]- Find IN interrupt ep: 0x81 packet_size=0x8 ugen1.3[1]- HID interface ugen1.3[1]- Report descriptor size = 142 ugen1.3[1]- Find IN interrupt ep: 0x82 packet_size=0x4 HID APPLICATION COLLECTION (Keyboard) size(65) HID REPORT: ID 0 INPUT: POS:0 SIZE:1 COUNT:8 [VARIABLE] USAGE Keyboard LeftControl USAGE Keyboard LeftShift USAGE Keyboard LeftAlt USAGE Keyboard Left GUI USAGE Keyboard RightControl USAGE Keyboard RightShift USAGE Keyboard RightAlt USAGE Keyboard Right GUI POS:8 SIZE:8 COUNT:1 [CONST] POS:16 SIZE:8 COUNT:6 [ARRAY] USAGE [0 - 255] (Keyboard) OUTPUT: POS:0 SIZE:1 COUNT:5 [VARIABLE] USAGE Num Lock USAGE Caps Lock USAGE Scroll Lock USAGE Compose USAGE Kana POS:5 SIZE:3 COUNT:1 [CONST] HID APPLICATION COLLECTION (Consumer Control) size(31) HID REPORT: ID 1 INPUT: POS:0 SIZE:7 COUNT:1 [VARIABLE] USAGE Volume POS:7 SIZE:1 COUNT:1 [VARIABLE] USAGE Mute HID APPLICATION COLLECTION (System Control) size(29) HID REPORT: ID 2 INPUT: POS:0 SIZE:1 COUNT:3 [VARIABLE] USAGE System Sleep USAGE System Sleep USAGE System Sleep POS:3 SIZE:1 COUNT:5 [CONST] HID APPLICATION COLLECTION (Consumer Control) size(82) HID REPORT: ID 3 INPUT: POS:0 SIZE:1 COUNT:1 [VARIABLE] USAGE AC Refresh POS:1 SIZE:1 COUNT:1 [VARIABLE] USAGE AL Local Machine Browser POS:2 SIZE:1 COUNT:1 [VARIABLE] USAGE AC Home POS:3 SIZE:1 COUNT:1 [VARIABLE] USAGE AL Email Reader POS:4 SIZE:1 COUNT:1 [VARIABLE] USAGE AL Calculator POS:5 SIZE:1 COUNT:1 [VARIABLE] USAGE AC Stop POS:6 SIZE:1 COUNT:1 [VARIABLE] USAGE AC Forward POS:7 SIZE:1 COUNT:1 [VARIABLE] USAGE AC Back POS:8 SIZE:1 COUNT:1 [VARIABLE] USAGE Scan Next Track
Re: External usb HDD disconnects, system gets messed up
On Friday 26 November 2010 03:01:59 Nezmer wrote: On Thu, Nov 25, 2010 at 09:40:19AM +0100, Hans Petter Selasky wrote: On Thursday 25 November 2010 03:55:26 Nezmer wrote: Hi, FreeBSD 8.1-STABLE r215402M GENERIC amd64 I'm having a weird issue. I have a 300GB external usb HDD with one ext2 partition. I use ZFS for my internal HDD. Almost daily, The usb HDD disconnects(according to dmesg) and the system gets messed up. Running processes keep responding but they would not exit. And no new processes would start running. I eventually would have to hard reset and run fsck.ext2 on the next run. Any idea what's going on? Do you need any specific information? Hi, When this hang happens you can try to turn on umass debugging: sysctl hw.usb.umass.debug=-1 You need this option in your kernel config or when building the umass module to enable the sysctl above: options USB_DEBUG --HPS Thank you for the hint. I managed to freeze the system this time. 1st, I tried to cd to a dir and got an I/O error. Here is some debug output: umass0:umass_bbb_dump_csw: CSW 208387: sig = 0x53425355 (valid), tag = 0x00032e03, res = 4096, status = 0x01 (failed) umass0:umass_t_bbb_status_callback: Command failed, residue = 4096 umass0:umass_cam_cb: Fetching 32 bytes of sense data umass0:umass_bbb_dump_cbw: CBW 208388: cmd = 6b (0x03002000), data = 32b, lun = 0, dir = in umass0:umass_transfer_start: transfer index = 4 umass0:umass_t_bbb_data_read_callback: max_bulk=131072, data_rem=32 umass0:umass_t_bbb_data_read_callback: max_bulk=131072, data_rem=0 umass0:umass_transfer_start: transfer index = 8 umass0:umass_t_bbb_status_callback: Failed to read CSW: USB_ERR_STALLED, try 0 umass0:umass_transfer_start: transfer index = 5 umass0:umass_transfer_start: transfer index = 8 umass0:umass_bbb_dump_csw: CSW 208388: sig = 0x53425355 (valid), tag = 0x00032e04, res = 14, status = 0x00 (good) (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 0 30 57 0 0 8 0 (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI status: Check Condition (da0:umass-sim0:0:0:0): SCSI sense: UNIT ATTENTION asc:28,0 (Not ready to ready change, medium may have changed) umass0:umass_cam_action: 2:0:0:XPT_SCSI_IO: cmd: 0x28, flags: 0x40, 10b cmd/4096b data/32b sense umass0:umass_bbb_dump_cbw: CBW 208389: cmd = 10b (0x28003057...), data = 4096b, lun = 0, dir = in umass0:umass_transfer_start: transfer index = 4 umass0:umass_t_bbb_data_read_callback: max_bulk=131072, data_rem=4096 umass0:umass_transfer_start: transfer index = 5 umass0:umass_transfer_start: transfer index = 8 umass0:umass_bbb_dump_csw: CSW 208389: sig = 0x53425355 (valid), tag = 0x00032e05, res = 4096, status = 0x01 (failed) umass0:umass_t_bbb_status_callback: Command failed, residue = 4096 umass0:umass_cam_cb: Fetching 32 bytes of sense data umass0:umass_bbb_dump_cbw: CBW 208390: cmd = 6b (0x03002000), data = 32b, lun = 0, dir = in umass0:umass_transfer_start: transfer index = 4 umass0:umass_t_bbb_data_read_callback: max_bulk=131072, data_rem=32 umass0:umass_t_bbb_data_read_callback: max_bulk=131072, data_rem=0 umass0:umass_transfer_start: transfer index = 8 umass0:umass_t_bbb_status_callback: Failed to read CSW: USB_ERR_STALLED, try 0 umass0:umass_transfer_start: transfer index = 5 umass0:umass_transfer_start: transfer index = 8 umass0:umass_bbb_dump_csw: CSW 208390: sig = 0x53425355 (valid), tag = 0x00032e06, res = 14, status = 0x00 (good) (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 0 30 57 0 0 8 0 (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI status: Check Condition (da0:umass-sim0:0:0:0): SCSI sense: UNIT ATTENTION asc:28,0 (Not ready to ready change, medium may have changed) umass0:umass_cam_action: 2:0:0:XPT_SCSI_IO: cmd: 0x28, flags: 0x40, 10b cmd/4096b data/32b sense umass0:umass_bbb_dump_cbw: CBW 208391: cmd = 10b (0x28003057...), data = 4096b, lun = 0, dir = in umass0:umass_transfer_start: transfer index = 4 umass0:umass_t_bbb_data_read_callback: max_bulk=131072, data_rem=4096 umass0:umass_transfer_start: transfer index = 5 umass0:umass_transfer_start: transfer index = 8 umass0:umass_bbb_dump_csw: CSW 208391: sig = 0x53425355 (valid), tag = 0x00032e07, res = 4096, status = 0x01 (failed) umass0:umass_t_bbb_status_callback: Command failed, residue = 4096 umass0:umass_cam_cb: Fetching 32 bytes of sense data umass0:umass_bbb_dump_cbw: CBW 208392: cmd = 6b (0x03002000), data = 32b, lun = 0, dir = in umass0:umass_transfer_start: transfer index = 4 umass0:umass_t_bbb_data_read_callback: max_bulk=131072, data_rem=32 umass0:umass_t_bbb_data_read_callback: max_bulk=131072, data_rem=0 umass0:umass_transfer_start: transfer index = 8 umass0:umass_t_bbb_status_callback: Failed to read CSW: USB_ERR_STALLED, try 0 umass0:umass_transfer_start: transfer index = 5
Re: USB controller error logged when resuming after suspend
On Thu, 25 Nov 2010 20:46:42 -0600 Brandon Gooch jamesbrandongo...@gmail.com wrote: It's becoming more well known that the USB stack isn't suspend/resume safe at this point. Have you tried building your USB systems as kernel modules and unloading/loading them via /etc/rs.suspend|resume? I used to have luck doing that here, but recently that has broken as well (running HEAD). I'm not so interested in using suspend/resume as a real feature, but more as a developer to report issues so that in the future we can perhaps have it working for end-users. Apparently there's lots of infrastructure work that still needs to be done before it's going to be reliable unfortunately. -- Bruce Cran ___ 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
