On Sat, Oct 27, 2012 at 9:59 PM, Andrew Lutomirski <luto@xxxxxxx> wrote: > I have a Lenovo X220, and d3cold seems to break hotplug on xhci. This > is 3.6.2-4.fc17.x86_64. > > The device is: > > 0e:00.0 USB Controller [0c03]: NEC Corporation uPD720200 USB 3.0 Host > Controller [1033:0194] (rev 04) (prog-if 30 [XHCI]) > Subsystem: Lenovo Device [17aa:21da] > 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 18 > Region 0: Memory at f0c00000 (64-bit, non-prefetchable) [size=8K] > Capabilities: [50] Power Management version 3 > Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA 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 L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+ > ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt- > LnkSta: Speed 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: -6dB, EqualizationComplete-, > EqualizationPhase1- > EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- > Capabilities: [100 v1] 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 v1] Device Serial Number ff-ff-ff-ff-ff-ff-ff-ff > Capabilities: [150 v1] Latency Tolerance Reporting > Max snoop latency: 0ns > Max no snoop latency: 0ns > Kernel driver in use: xhci_hcd > > (read while the port was functioning and in use.) > > Inserting a USB3 flash stick has absolutely no effect, other than some > lights on the stick flickering for a couple seconds. When I wrote 0 > to /sys/devices/pci0000:00/0000:00:1c.6/0000:0e:00.0/d3cold_allowed > with the stick inserted, the kernel immediately detected it, and it > worked. dmesg said: > > [13829.364050] hub 3-0:1.0: unable to enumerate USB device on port 1 > [13829.570044] usb 4-1: new SuperSpeed USB device number 2 using xhci_hcd > [13829.582636] usb 4-1: Parent hub missing LPM exit latency info. > Power management will be impacted. > [13829.585194] usb 4-1: New USB device found, idVendor=1b1c, idProduct=1a01 > [13829.585203] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 > [13829.585208] usb 4-1: Product: Voyager GT 3.0 > [13829.585213] usb 4-1: Manufacturer: Corsair > [13829.585216] usb 4-1: SerialNumber: 1111800000000051 > [13829.586555] scsi13 : usb-storage 4-1:1.0 > [13830.588360] scsi 13:0:0:0: Direct-Access Corsair Voyager GT > 3.0 1.00 PQ: 0 ANSI: 5 > [13830.590394] sd 13:0:0:0: [sdb] 31260672 512-byte logical blocks: > (16.0 GB/14.9 GiB) > [13830.590403] sd 13:0:0:0: Attached scsi generic sg1 type 0 > [13830.590574] sd 13:0:0:0: [sdb] Write Protect is off > [13830.590584] sd 13:0:0:0: [sdb] Mode Sense: 23 00 00 00 > [13830.590755] sd 13:0:0:0: [sdb] Write cache: disabled, read cache: > disabled, doesn't support DPO or FUA > [13830.595257] sdb: unknown partition table > [13830.596046] sd 13:0:0:0: [sdb] Attached SCSI removable disk > [13952.583378] ehci_hcd 0000:00:1d.0: power state changed by ACPI to D0 > [13952.684487] ehci_hcd 0000:00:1d.0: setting latency timer to 64 > [13952.685039] ehci_hcd 0000:00:1a.0: power state changed by ACPI to D0 > [13952.695332] ehci_hcd 0000:00:1d.0: power state changed by ACPI to D3cold > [13952.785385] ehci_hcd 0000:00:1a.0: setting latency timer to 64 > [13952.802164] ehci_hcd 0000:00:1a.0: power state changed by ACPI to D3cold > [13963.727363] ehci_hcd 0000:00:1d.0: power state changed by ACPI to D0 > [13963.828153] ehci_hcd 0000:00:1d.0: setting latency timer to 64 > [13963.828533] ehci_hcd 0000:00:1a.0: power state changed by ACPI to D0 > > I suspect the ehci_hcd noise is something else. Eek. It's not what I thought it was. The problem persists regardless of the setting of d3cold_allowed. The stick is only recognized when I insert it and then *toggle* d3cold_allowed. Setting power/control to "on" seems to fix it. --Andy -- 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
