Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset in Bionic 18.04
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Medium
|
Unassigned | ||
Bionic |
Confirmed
|
Medium
|
Unassigned |
Bug Description
A typo at line 184 in /drivers/
183 if (pdev->vendor == PCI_VENDOR_
184 pdev->device == 0x0014)
185 xhci->quirks |= XHCI_TRUST_
186 if (pdev->vendor == PCI_VENDOR_
187 pdev->device == 0x0015)
188 xhci->quirks |= XHCI_RESET_
Line 184 should be identical to line 187, ie: should read pdev->device == 0x0015)
I've compiled the kernel both with and without the typo. As written, hundreds of messages fill dmesg suggesting XHCI_TRUST_
The typo is still present in 4.15.0-22.24
For more background, you may refer to bug ID #1710548
Changed in linux (Ubuntu Bionic): | |
status: | New → Triaged |
Changed in linux (Ubuntu): | |
status: | Confirmed → Triaged |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Bionic): | |
importance: | Undecided → Medium |
tags: | added: kernel-da-key |
Changed in linux (Ubuntu Bionic): | |
assignee: | nobody → Joseph Salisbury (jsalisbury) |
Changed in linux (Ubuntu): | |
assignee: | nobody → Joseph Salisbury (jsalisbury) |
Changed in linux (Ubuntu Bionic): | |
status: | Triaged → In Progress |
Changed in linux (Ubuntu): | |
status: | Triaged → In Progress |
Changed in linux (Ubuntu Bionic): | |
status: | In Progress → Confirmed |
Changed in linux (Ubuntu): | |
status: | In Progress → Confirmed |
Changed in linux (Ubuntu Bionic): | |
assignee: | Joseph Salisbury (jsalisbury) → nobody |
Changed in linux (Ubuntu): | |
assignee: | Joseph Salisbury (jsalisbury) → nobody |
tags: | added: cscc |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1773704
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.