On Mon, Nov 07, 2011 at 10:53:32PM +0200, Tomi Orava wrote: > Hi, > > On 11/07/2011 08:29 PM, Sarah Sharp wrote: > > On Mon, Nov 07, 2011 at 05:22:24PM +0800, Andiry Xu wrote: > >> This event is extremely suspicious. It points to a Set Address > >> command TRB, but the offest 08h and 0ch are totally messed up. The > >> completion code is invalid, ResvZ field is filled with value, and > >> the TRB type is not right. The driver regards the Set Address > >> command as failed, try to disable and enable the slot again, but > >> never receive the response. > >> > >> Sarah, do you have AsMedia host controller? Have you seen this issue before? > > > > I've never had an AsMedia host controller (although a couple people have > > reported problems with it before that I was able to solve). I haven't > > received reports of this particular issue before. I do know that the > > AsMedia host is stricter about inputs to some commands than other xHCI > > host controllers, so it's possible software is doing something > > unexpected to the host, but the mangled event seems more like a hardware > > failure. > > > > Tomi, can you try re-running with the attached patch applied? It fixes > > at least one issue with the AsMedia host, but the patch hasn't been > > queued up by Greg for 3.1 yet. I'm not sure if it will fix your > > particular issue, but I'd like to rule out known issues first. > > Ok, the attached log is from stright from the reboot of the system with > your patch applied. >From your log file, it looks like you booted with the USB 2.0 hub plugged into the USB 3.0 port, with a USB mouse and webcam attached to the hub. > Nov 7 22:26:32 tipoca kernel: Kernel logging (proc) stopped. > Nov 7 22:28:22 knummi kernel: imklog 4.2.0, log source = /proc/kmsg started. ... > Nov 7 22:28:23 knummi kernel: [ 1.778550] xhci_hcd 0000:04:00.0: xHCI Host Controller > Nov 7 22:28:23 knummi kernel: [ 1.778612] xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 2 > Nov 7 22:28:23 knummi kernel: [ 1.783851] xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 3 ... > Nov 7 22:33:52 knummi kernel: [ 342.606677] hub 2-0:1.0: state 7 ports 2 chg 0000 evt 0002 > Nov 7 22:33:52 knummi kernel: [ 342.606701] hub 2-0:1.0: port 1, status 0100, change 0001, 12 Mb/s The hub disconnects and reconnects once: > Nov 7 22:33:52 knummi kernel: [ 342.606709] usb 2-1: USB disconnect, device number 2 > Nov 7 22:34:35 knummi kernel: [ 385.835098] usb 2-1: new high speed USB device number 3 using xhci_hcd > Nov 7 22:34:35 knummi kernel: [ 385.850783] hub 2-1:1.0: USB hub found Then the low speed mouse is enumerated: > Nov 7 22:35:21 knummi kernel: [ 431.566084] usb 2-1.1: new low speed USB device number 4 using xhci_hcd > Nov 7 22:35:21 knummi kernel: [ 431.653258] usbhid 2-1.1:1.0: usb_probe_interface - got id Then the webcam gets enumerated as well: > Nov 7 22:35:41 knummi kernel: [ 452.012086] usb 2-1.3: new high speed USB device number 6 using xhci_hcd > Nov 7 22:35:41 knummi kernel: [ 452.281011] uvcvideo 2-1.3:1.0: usb_probe_interface > Nov 7 22:35:41 knummi kernel: [ 452.281014] uvcvideo 2-1.3:1.0: usb_probe_interface - got id > Nov 7 22:35:41 knummi kernel: [ 452.281038] uvcvideo: Found UVC 1.00 device <unnamed> (046d:0825) > Nov 7 22:35:41 knummi kernel: [ 452.281700] usb 2-1.3: Successful Endpoint Configure command At this point, you probably don't have the webcam open, so the USB core tries to suspend the unused webcam. It has to cancel the interrupt URB for the webcam though, and the host doesn't respond to the stop endpoint command properly. > Nov 7 22:35:51 knummi kernel: [ 462.368058] xhci_hcd 0000:04:00.0: xHCI host not responding to stop endpoint command. > Nov 7 22:35:51 knummi kernel: [ 462.368069] xhci_hcd 0000:04:00.0: Assuming host is dying, halting host. > Nov 7 22:35:51 knummi kernel: [ 462.368108] xhci_hcd 0000:04:00.0: HC died; cleaning up I'll have to look through your first log (which seemed to have CONFIG_USB_DEBUG and CONFIG_USB_XHCI_HCD_DEBUGGING turned on) to see what input we're giving the host controller. But if the host controller really can't respond to stop endpoint commands properly, your system is probably not going to work well. You won't be able to use USB auto-suspend (CONFIG_USB_SUSPEND) or even be able to switch video sizes on your webcam. > The third and last log is taken, when I connected the "problematic" cypress usb 2.0 hub to usb 2.0 port: This log shows other errors that might be issues with your device hardware. > Nov 7 22:38:38 knummi kernel: [ 628.706217] hub 7-0:1.0: state 7 ports 5 chg 0000 evt 0008 > Nov 7 22:38:38 knummi kernel: [ 628.706241] ehci_hcd 0000:00:12.2: GetStatus port:3 status 001003 0 ACK POWER sig=se0 CSC CONNECT > Nov 7 22:38:38 knummi kernel: [ 628.706258] hub 7-0:1.0: port 3, status 0501, change 0001, 480 Mb/s > Nov 7 22:38:38 knummi kernel: [ 628.810106] hub 7-0:1.0: debounce: port 3: total 100ms stable 100ms status 0x501 > Nov 7 22:38:38 knummi kernel: [ 628.861107] ehci_hcd 0000:00:12.2: port 3 high speed > Nov 7 22:38:38 knummi kernel: [ 628.861122] ehci_hcd 0000:00:12.2: GetStatus port:3 status 001005 0 ACK POWER sig=se0 PE CONNECT > Nov 7 22:38:38 knummi kernel: [ 628.912099] usb 7-3: new high speed USB device number 7 using ehci_hcd > Nov 7 22:38:38 knummi kernel: [ 628.963105] ehci_hcd 0000:00:12.2: port 3 high speed > Nov 7 22:38:38 knummi kernel: [ 628.963119] ehci_hcd 0000:00:12.2: GetStatus port:3 status 001005 0 ACK POWER sig=se0 PE CONNECT > Nov 7 22:38:38 knummi kernel: [ 629.014109] usb 7-3: device descriptor read/64, error -32 > Nov 7 22:38:38 knummi kernel: [ 629.166079] ehci_hcd 0000:00:12.2: port 3 high speed > Nov 7 22:38:38 knummi kernel: [ 629.166094] ehci_hcd 0000:00:12.2: GetStatus port:3 status 001005 0 ACK POWER sig=se0 PE CONNECT > Nov 7 22:38:38 knummi kernel: [ 629.217055] usb 7-3: device descriptor read/64, error -32 > Nov 7 22:38:38 knummi kernel: [ 629.369127] ehci_hcd 0000:00:12.2: port 3 high speed > Nov 7 22:38:38 knummi kernel: [ 629.369143] ehci_hcd 0000:00:12.2: GetStatus port:3 status 001005 0 ACK POWER sig=se0 PE CONNECT > Nov 7 22:38:39 knummi kernel: [ 629.420069] usb 7-3: new high speed USB device number 8 using ehci_hcd > Nov 7 22:38:39 knummi kernel: [ 629.471088] ehci_hcd 0000:00:12.2: port 3 high speed > Nov 7 22:38:39 knummi kernel: [ 629.471103] ehci_hcd 0000:00:12.2: GetStatus port:3 status 001005 0 ACK POWER sig=se0 PE CONNECT > Nov 7 22:38:39 knummi kernel: [ 629.522064] usb 7-3: device descriptor read/64, error -32 > Nov 7 22:38:39 knummi kernel: [ 629.674061] ehci_hcd 0000:00:12.2: port 3 high speed > Nov 7 22:38:39 knummi kernel: [ 629.674076] ehci_hcd 0000:00:12.2: GetStatus port:3 status 001005 0 ACK POWER sig=se0 PE CONNECT > Nov 7 22:38:39 knummi kernel: [ 629.725109] usb 7-3: device descriptor read/64, error -32 > Nov 7 22:38:39 knummi kernel: [ 629.877109] ehci_hcd 0000:00:12.2: port 3 high speed > Nov 7 22:38:39 knummi kernel: [ 629.877124] ehci_hcd 0000:00:12.2: GetStatus port:3 status 001005 0 ACK POWER sig=se0 PE CONNECT > Nov 7 22:38:39 knummi kernel: [ 629.928107] usb 7-3: new high speed USB device number 9 using ehci_hcd > Nov 7 22:38:39 knummi kernel: [ 630.330065] usb 7-3: device not accepting address 9, error -32 > Nov 7 22:38:39 knummi kernel: [ 630.381114] ehci_hcd 0000:00:12.2: port 3 high speed > Nov 7 22:38:39 knummi kernel: [ 630.381130] ehci_hcd 0000:00:12.2: GetStatus port:3 status 001005 0 ACK POWER sig=se0 PE CONNECT > Nov 7 22:38:40 knummi kernel: [ 630.432072] usb 7-3: new high speed USB device number 10 using ehci_hcd > Nov 7 22:38:40 knummi kernel: [ 630.834065] usb 7-3: device not accepting address 10, error -32 > Nov 7 22:38:40 knummi kernel: [ 630.834180] hub 7-0:1.0: unable to enumerate USB device on port 3 The USB 2.0 hub doesn't want to enumerate under EHCI. -32 is -EPIPE, which is a protocol error, maybe a stall? In any case, it looks like your hub is just not working. Have you tried a different hub? Or a different cable to the hub? Sarah Sharp -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
