Re: Deadlock v3.10.35 with FTD_SIO usb-serial adapter

[Matteo Fortini]

After some time, we finally had another hangup on kernel 3.14.
@Alan: Here's the info we got in the files you mentioned. At any rate, 
we're keeping the board in the same state so that we can run/produce any 
other needed info.

http://pastebin.com/DZPAqjcd


Thank you,
Matteo



Il 16/04/2014 18:01, Alan Stern ha scritto:
On Wed, 16 Apr 2014, Matteo Fortini wrote:

It's and AMD Geode single board computer, using CS5535 companion chip.

Here's the pertaining lspci -vvv section:

00:0f.4 Class 0c03: Device 1022:2094 (rev 02) (prog-if 10)
      Subsystem: Device 1022:2094
      Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
      Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
      Latency: 0, Cache Line Size: 32 bytes
      Interrupt: pin D routed to IRQ 11
      Region 0: Memory at efffd000 (32-bit, non-prefetchable) [size=4K]
      Capabilities: [40] Power Management version 2
          Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
          Status: D0 PME-Enable- DSel=0 DScale=0 PME-
      Kernel driver in use: ohci-pci

00:0f.5 Class 0c03: Device 1022:2095 (rev 02) (prog-if 20)
      Subsystem: Device 1022:2095
      Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
      Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
      Latency: 0, Cache Line Size: 32 bytes
      Interrupt: pin D routed to IRQ 11
      Region 0: Memory at efffc000 (32-bit, non-prefetchable) [size=4K]
      Capabilities: [40] Power Management version 2
          Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
          Status: D0 PME-Enable- DSel=0 DScale=0 PME-
      Kernel driver in use: ehci-pci
This doesn't answer my question.  Which controller was the device
attached to when the hang occurred?  Was it the EHCI controller or the
OHCI controller?

If you enable CONFIG_USB_DEBUG, what shows up in the files under the
corresponding directory in /sys/kernel/debug/usb/ehci/ or
/sys/kernel/debug/usb/ohci/ when the hang occurs?

Alan Stern


--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html