Hi, Joao Pinto <Joao.Pinto@xxxxxxxxxxxx> writes: > Hi Felipe, > > On 5/19/2016 11:32 AM, Felipe Balbi wrote: >> >> Hi, >> >> Joao Pinto <Joao.Pinto@xxxxxxxxxxxx> writes: >>> Hi Felipe and Mathias, >>> >>> Sending kernel log with extra xhci messages in attachment! >>> Thanks you for the help! >> >> yeah, no problems. So here's the interesting part: >> >> *********************************INSERTING PEN DRIVE >> >> # xhci-hcd xhci-hcd.0.auto: Port Status Change Event for port 1 >> xhci-hcd xhci-hcd.0.auto: resume root hub >> xhci-hcd xhci-hcd.0.auto: handle_port_status: starting port polling. >> xhci-hcd xhci-hcd.0.auto: get port status, actual port 0 status = 0x206e1 >> xhci-hcd xhci-hcd.0.auto: Get port status returned 0x10101 >> xhci-hcd xhci-hcd.0.auto: clear port connect change, actual port 0 status = 0x6e1 >> xhci-hcd xhci-hcd.0.auto: xhci_hub_status_data: stopping port polling. >> xhci-hcd xhci-hcd.0.auto: get port status, actual port 0 status = 0x6e1 >> xhci-hcd xhci-hcd.0.auto: Get port status returned 0x101 >> xhci-hcd xhci-hcd.0.auto: xhci_hub_status_data: stopping port polling. >> xhci-hcd xhci-hcd.0.auto: // Ding dong! >> xhci-hcd xhci-hcd.0.auto: Command timeout >> xhci-hcd xhci-hcd.0.auto: Abort command ring >> >> Note that we really did get a command timeout. Can you add a little >> extra debugging to try and figure out why that command failed? >> > > After instrumenting and capturing FPGA signals, the driver could go a bit > further... Could this be a FPGA timming issue? possible. But before we blame FPGA, can you test Mathias' suggestion? Thanks -- balbi
Attachment:
signature.asc
Description: PGP signature
