Nicholas Herriot

Important changes to forums and questions

All forums and questions are now archived. To start a new conversation or read the latest updates go to forums.mbed.com.

10 years, 8 months ago.

More problems on USB host controller connecting to C027

Hi Michael,

here is some more debug from dmesg on my Linux machine from inserting the USB plug onto my machine. The output is quite verbos - but you can see some errors apear on the bus which seems to be causing the irratic behaviour.

usb failure on bus from using c027 on Linux mint 13

[ 2572.575369] scsi7 : usb-storage 3-1:1.0
[ 2572.575448] usbcore: registered new interface driver usb-storage
[ 2572.575450] USB Mass Storage support registered.
[ 2572.581444] cdc_acm 3-1:1.1: ttyACM0: USB ACM device
[ 2572.673427] usbcore: registered new interface driver cdc_acm
[ 2572.673429] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 2573.574605] scsi 7:0:0:0: Direct-Access     MBED     microcontroller  1.0  PQ: 0 ANSI: 2
[ 2573.575247] sd 7:0:0:0: Attached scsi generic sg3 type 0
[ 2573.575781] sd 7:0:0:0: [sdd] 1072 512-byte logical blocks: (548 kB/536 KiB)
[ 2573.576164] sd 7:0:0:0: [sdd] Write Protect is off
[ 2573.576167] sd 7:0:0:0: [sdd] Mode Sense: 03 00 00 00
[ 2573.576442] sd 7:0:0:0: [sdd] No Caching mode page present
[ 2573.576445] sd 7:0:0:0: [sdd] Assuming drive cache: write through
[ 2573.578633] sd 7:0:0:0: [sdd] No Caching mode page present
[ 2573.578636] sd 7:0:0:0: [sdd] Assuming drive cache: write through
[ 2573.588796]  sdd:
[ 2573.590356] sd 7:0:0:0: [sdd] No Caching mode page present
[ 2573.590365] sd 7:0:0:0: [sdd] Assuming drive cache: write through
[ 2573.590372] sd 7:0:0:0: [sdd] Attached SCSI removable disk
[ 2758.474774] usb 3-1: reset full-speed USB device number 7 using xhci_hcd
[ 2778.448725] xhci_hcd 0000:00:14.0: Timeout while waiting for address device command
[ 2798.626580] xhci_hcd 0000:00:14.0: Timeout while waiting for address device command
[ 2798.830292] usb 3-1: device not accepting address 7, error -62
[ 2798.942201] usb 3-1: reset full-speed USB device number 7 using xhci_hcd
[ 2798.942218] usb 3-1: Device not responding to set address.
[ 2799.145949] usb 3-1: Device not responding to set address.
[ 2799.349674] usb 3-1: device not accepting address 7, error -71
[ 2799.461573] usb 3-1: reset full-speed USB device number 7 using xhci_hcd
[ 2799.461587] usb 3-1: Device not responding to set address.
[ 2799.665237] usb 3-1: Device not responding to set address.
[ 2799.868993] usb 3-1: device not accepting address 7, error -71
[ 2799.980824] usb 3-1: reset full-speed USB device number 7 using xhci_hcd
[ 2799.980829] usb 3-1: Device not responding to set address.
[ 2800.184566] usb 3-1: Device not responding to set address.
[ 2800.388302] usb 3-1: device not accepting address 7, error -71
[ 2800.388373] usb 3-1: USB disconnect, device number 7
[ 2800.388375] sd 7:0:0:0: Device offlined - not ready after error recovery
[ 2800.388382] sd 7:0:0:0: [sdd] Unhandled error code
[ 2800.388383] sd 7:0:0:0: [sdd]  Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK
[ 2800.388386] sd 7:0:0:0: [sdd] CDB: Write(10): 2a 00 00 00 00 29 00 00 1b 00
[ 2800.388392] end_request: I/O error, dev sdd, sector 41
[ 2800.388402] sd 7:0:0:0: rejecting I/O to offline device
[ 2800.388404] sd 7:0:0:0: killing request
[ 2800.388412] sd 7:0:0:0: rejecting I/O to offline device
[ 2800.388414] sd 7:0:0:0: [sdd] killing request
[ 2800.388420] sd 7:0:0:0: rejecting I/O to offline device
[ 2800.388426] sd 7:0:0:0: rejecting I/O to offline device
[ 2800.388433] sd 7:0:0:0: [sdd] Unhandled error code
[ 2800.388435] sd 7:0:0:0: [sdd]  Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 2800.388438] sd 7:0:0:0: [sdd] CDB: Write(10): 2a 00 00 00 00 07 00 00 01 00
[ 2800.388444] end_request: I/O error, dev sdd, sector 7
[ 2800.388447] Buffer I/O error on device sdd, logical block 7
[ 2800.388448] lost page write due to I/O error on sdd
[ 2800.389599] VFS: busy inodes on changed media or resized disk sdd
[ 2800.390485] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88011428a9c0
[ 2800.390489] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88011428a980
[ 2800.390492] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88011428ad40
[ 2800.390494] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88011428ad00
[ 2800.390497] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800bdbf3440
[ 2800.390500] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88011428ac00
[ 2800.390503] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88011428ac40
[ 2800.556143] usb 3-1: new full-speed USB device number 8 using xhci_hcd
[ 2800.556150] xhci_hcd 0000:00:14.0: ERROR: unexpected command completion code 0x0.
[ 2800.759851] xhci_hcd 0000:00:14.0: ERROR: unexpected command completion code 0x0.
[ 2800.963535] usb 3-1: device not accepting address 8, error -22
[ 2801.075435] usb 3-1: new full-speed USB device number 9 using xhci_hcd
[ 2801.075451] xhci_hcd 0000:00:14.0: ERROR: unexpected command completion code 0x0.
[ 2801.279127] xhci_hcd 0000:00:14.0: ERROR: unexpected command completion code 0x0.
[ 2801.482932] usb 3-1: device not accepting address 9, error -22
[ 2801.594782] usb 3-1: new full-speed USB device number 10 using xhci_hcd
[ 2801.594798] xhci_hcd 0000:00:14.0: ERROR: unexpected command completion code 0x0.
[ 2801.798507] xhci_hcd 0000:00:14.0: ERROR: unexpected command completion code 0x0.
[ 2802.002189] usb 3-1: device not accepting address 10, error -22
[ 2802.114113] usb 3-1: new full-speed USB device number 11 using xhci_hcd
[ 2802.114132] xhci_hcd 0000:00:14.0: ERROR: unexpected command completion code 0x0.
[ 2802.317822] xhci_hcd 0000:00:14.0: Setup ERROR: address device command for slot 9.
[ 2802.521574] usb 3-1: device not accepting address 11, error -22
[ 2802.521619] hub 3-0:1.0: unable to enumerate USB device on port 1

Notice the device try's to enumerate on the bus over and over but fails. Sometimes it works! But not this morning...

enumeration failure

[ 2800.556143] usb 3-1: new full-speed USB device number 8 using xhci_hcd
[ 2800.556150] xhci_hcd 0000:00:14.0: ERROR: unexpected command completion code 0x0.
[ 2800.759851] xhci_hcd 0000:00:14.0: ERROR: unexpected command completion code 0x0.
[ 2800.963535] usb 3-1: device not accepting address 8, error -22
[ 2801.075435] usb 3-1: new full-speed USB device number 9 using xhci_hcd
[ 2801.075451] xhci_hcd 0000:00:14.0: ERROR: unexpected command completion code 0x0.
[ 2801.279127] xhci_hcd 0000:00:14.0: ERROR: unexpected command completion code 0x0.
[ 2801.482932] usb 3-1: device not accepting address 9, error -22
[ 2801.594782] usb 3-1: new full-speed USB device number 10 using xhci_hcd
[ 2801.594798] xhci_hcd 0000:00:14.0: ERROR: unexpected command completion code 0x0.
[ 2801.798507] xhci_hcd 0000:00:14.0: ERROR: unexpected command completion code 0x0.
[ 2802.002189] usb 3-1: device not accepting address 10, error -22
[ 2802.114113] usb 3-1: new full-speed USB device number 11 using xhci_hcd
[ 2802.114132] xhci_hcd 0000:00:14.0: ERROR: unexpected command completion code 0x0.
[ 2802.317822] xhci_hcd 0000:00:14.0: Setup ERROR: address device command for slot 9.
[ 2802.521574] usb 3-1: device not accepting address 11, error -22
[ 2802.521619] hub 3-0:1.0: unable to enumerate USB device on port 1

It gives up and then fails. Eventually I'll get to a state where all devices stop working on my machine - which is probably a Linux bug, however the C027 fails to enumerate many times which is not I believe a fault with the USB host controller.

Any ideas on ways around this?

Kind regards, Nicholas

Question relating to:

Last updated: 27 Aug 2020
The u-blox-C027 is a complete starter kit that allows quick prototyping of a variety of applications for the Internet of Things. The application board has a MAX-M8Q GPS/GNSS receiver and …

1 Answer

prasanna karthik
9 years, 9 months ago.

I also face the same Issue with nucleo re401. ttyACM0 gets reset when cutecom/minicom/cat tries to read from it. Could be bug in linux usb subsystem ?