Re: xhci

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi

On 09/11/2014 05:18 PM, Jay Larson wrote:
> Mathias,
> 
> I was not able to locate an official method of inquiring about issues with xhci, 
> so I'm writing directly to you. If this is not the appropriate method please 
> accept my apologies and kindly direct me to the proper place.
> 

Me, including the linux usb mailing list (added to cc), is the right combination to ask
questions regarding xhci. 

> We have had a failure for which I have been asked to provide an explanation. A 
> process that was accessing a USB 3.0 disk unexpectedly failed (Killed). We have 
> had other issues where users have had to reboot to restore USB connectivity 
> (possibly just reloading the module would have had the same effect). I can only 
> surmise that there is either a problem with the hardware, or xhci. I am in 
> particular curious if we could expect any significant benefits to using a more 
> recent kernel.
> 

You should definitely use a more recent kernel, there are tons of changes since 2.6.32,
and It's impossible for me to support old kernels.

> [uname -a]
> Linux kdmlinux3 2.6.32-279.el6.x86_64 #1 SMP Fri Jun 22 12:19:21 UTC 2012 x86_64 
> x86_64 x86_64 GNU/Linux
> 
> [lcpci -vv]
> 04:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 

For example this quirk was added to 3.2 kernel concerning the NEC host:

commit df711fc9962b9491af2b92bd0d21ecbfefe4e5fa

    xHCI: reset-on-resume quirk for NEC uPD720200
    
    Julian Sikorski reports NEC uPD720200 does not work stable after suspend
    and resume. Re-initialize the host in xhci_resume().
    

If you can, please try with a 3.16 or 3.17-rc kernel and see if the issue still exists.

-Mathias

(leaving rest of message here for reference for linux-usb readers)


> 04) (prog-if 30 [XHCI])
>          Physical Slot: 0-1
>          Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
> Stepping- SERR- FastB2B- DisINTx+
>          Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- 
> <MAbort- >SERR- <PERR- INTx-
>          Latency: 0, Cache Line Size: 64 bytes
>          Interrupt: pin A routed to IRQ 16
>          Region 0: Memory at fe9fe000 (64-bit, non-prefetchable) [size=8K]
>          Capabilities: [50] Power Management version 3
>                  Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
> PME(D0+,D1-,D2-,D3hot+,D3cold-)
>                  Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
>          Capabilities: [70] MSI: Enable- Count=1/8 Maskable- 64bit+
>                  Address: 0000000000000000  Data: 0000
>          Capabilities: [90] MSI-X: Enable+ Count=8 Masked-
>                  Vector table: BAR=0 offset=00001000
>                  PBA: BAR=0 offset=00001080
>          Capabilities: [a0] Express (v2) Endpoint, MSI 00
>                  DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s 
> unlimited, L1 unlimited
>                          ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
>                  DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
>                          RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
>                          MaxPayload 128 bytes, MaxReadReq 512 bytes
>                  DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend-
>                  LnkCap: Port #0, Speed 5GT/s, Width x1, ASPM L0s L1, Latency L0 
> <4us, L1 unlimited
>                          ClockPM+ Surprise- LLActRep- BwNot-
>                  LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- Retrain- 
> CommClk+
>                          ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
>                  LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ 
> DLActive- BWMgmt- ABWMgmt-
>                  DevCap2: Completion Timeout: Not Supported, TimeoutDis+
>                  DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-
>                  LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-, 
> Selectable De-emphasis: -6dB
>                           Transmit Margin: Normal Operating Range, 
> EnterModifiedCompliance- ComplianceSOS-
>                           Compliance De-emphasis: -6dB
>                  LnkSta2: Current De-emphasis Level: -3.5dB
>          Capabilities: [100] Advanced Error Reporting
>                  UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- 
> RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
>                  UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- 
> RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
>                  UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- 
> RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
>                  CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
>                  CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
>                  AERCap: First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn-
>          Capabilities: [140] Device Serial Number ff-ff-ff-ff-ff-ff-ff-ff
>          Capabilities: [150] Latency Tolerance Reporting
>                  Max snoop latency: 0ns
>                  Max no snoop latency: 0ns
>          Kernel driver in use: xhci_hcd
>          Kernel modules: xhci-hcd
> 
> [dmesg]
> xhci_hcd 0000:04:00.0: xHCI xhci_drop_endpoint called with disabled ep 
> ffff88006e7a6ec0
> xhci_hcd 0000:04:00.0: xHCI xhci_drop_endpoint called with disabled ep 
> ffff88006e7a6f08
> xhci_hcd 0000:04:00.0: ERROR: unexpected command completion code 0x0.
> usb 13-2: new SuperSpeed USB device number 18 using xhci_hcd
> usb 13-2: New USB device found, idVendor=1058, idProduct=1140
> usb 13-2: New USB device strings: Mfr=1, Product=2, SerialNumber=5
> usb 13-2: Product: My Book 1140
> usb 13-2: Manufacturer: Western Digital
> usb 13-2: SerialNumber: 504C313332314C414733595A5248
> usb 13-2: configuration #1 chosen from 1 choice
> scsi26 : SCSI emulation for USB Mass Storage devices
> usb-storage: device found at 18
> usb-storage: waiting for device to settle before scanning
> usb-storage: device scan complete
> usb 13-2: reset SuperSpeed USB device number 18 using xhci_hcd
> xhci_hcd 0000:04:00.0: xHCI host not responding to stop endpoint command.
> xhci_hcd 0000:04:00.0: Assuming host is dying, halting host.
> xhci_hcd 0000:04:00.0: Non-responsive xHCI host is not halting.
> xhci_hcd 0000:04:00.0: Completing active URBs anyway.
> xhci_hcd 0000:04:00.0: HC died; cleaning up
> 
> I would be appreciative of any insight you might have.
> 
> Thanks
> 

--
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




[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux