|
Bugzilla – Full Text Bug Listing |
| Summary: | VL805/806 xHCI USB 3.0 Controller driver not working on opensuse Tumbleweed | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Michał Szczepaniak <m.szczepaniak.000> |
| Component: | Kernel | Assignee: | openSUSE Kernel Bugs <kernel-bugs> |
| Status: | IN_PROGRESS --- | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | m.szczepaniak.000, oneukum, tiwai |
| Version: | Current | Flags: | oneukum:
needinfo?
(m.szczepaniak.000) |
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE Tumbleweed | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
lspci -v output
lspci -vn Revert the obvious suspect |
||
|
Description
Michał Szczepaniak
2023-06-14 11:57:32 UTC
The log tells us what is happening but not why. Is this on a Raspberry? The device is known to be quirky and initialization has been canged comparatively recently. Please also provide the output of "lspci -v" Created attachment 867574 [details]
lspci -v output
It's not raspberry pi, it's a pciex1 card that I've purchased
Please also provide te output of "lspci -vn" Created attachment 867575 [details]
lspci -vn
As this is a regression, the obvious culprit is
5255660b208aebfdb71d574f3952cf48392f4306 ("xhci: add quirk for host controllers that don't update endpoint DCS")
Created attachment 867594 [details]
Revert the obvious suspect
I could create branch on obs and apply the patch to test it or do you want me to do it some other way? (In reply to Michał Szczepaniak from comment #7) > I could create branch on obs and apply the patch to test it or do you want > me to do it some other way? Yes, it is fine to test this with a kernel generated in obs. Obvious suspect is the correct one :) It works now. Now we need to detain the suspect! OK, this needs to go upstream. Please provide the output of "lspci -vvvn" for meto include in the upstream changelog. without pasting entire thing i think this is what you need
0b:00.0 0c03: 1106:3483 (rev 01) (prog-if 30 [XHCI])
Subsystem: 1106:3483
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 66
Region 0: Memory at fb400000 (64-bit, non-prefetchable) [size=4K]
Capabilities: [80] 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: [90] MSI: Enable+ Count=1/4 Maskable- 64bit+
Address: 00000000fee007b8 Data: 0000
Capabilities: [c4] Express (v2) Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 89W
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend-
LnkCap: Port #0, Speed 5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <2us, L1 <16us
ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp-
LnkCtl: ASPM Disabled; RCB 64 bytes, Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 5GT/s, Width x1
TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Range B, TimeoutDis+ NROPrPrP- LTR-
10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix-
EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
FRS- TPHComp- ExtTPHComp-
AtomicOpsCap: 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- 10BitTagReq- OBFF Disabled,
AtomicOpsCtl: ReqEn-
LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
Compliance Preset/De-emphasis: -6dB de-emphasis, 0dB preshoot
LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete- EqualizationPhase1-
EqualizationPhase2- EqualizationPhase3- LinkEqualizationRequest-
Retimer- 2Retimers- CrosslinkRes: unsupported
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- AdvNonFatalErr-
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
AERCap: First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn-
MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
HeaderLog: 00000000 00000000 00000000 00000000
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
We got something from upstream: Odd. There are many third party VLI cards in the field and this is the first I've heard of an incompatibility. Can you please report the output of lspci -s 0b:00.0 -xxx and pastebin a dmesg trace with xhci debug printks (and the quirk) turned on? I'm on it but if you would like to help me with enabling the printk's i would be thankful 0b:00.0 USB controller: VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller (rev 01) 00: 06 11 83 34 07 04 10 00 01 30 03 0c 10 00 00 00 10: 04 00 40 fb 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 06 11 83 34 30: 00 00 00 00 80 00 00 00 00 00 00 00 ff 01 00 00 You can enable dynamic debugging on the kernel command line. In this case dyndbg="module xhci_hcd +fpm" (on the unfixed kernel) should do the job. I was about to get the debug log but… I'm currently at 6.4.3 and it seems to be working just fine. 6.3.8 was the one with the fix, so maybe something changed between 6.3 and 6.4. And indeed I booted 6.3.9 (without fix) and it indeed doesn't work. |