amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x0000 to IRQ, err -517
Bug #1971597 reported by
You-Sheng Yang
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
Critical
|
Unassigned | ||
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Invalid
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
High
|
You-Sheng Yang | ||
linux-oem-5.14 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
High
|
You-Sheng Yang | ||
Jammy |
Invalid
|
Undecided
|
Unassigned | ||
linux-oem-5.17 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Invalid
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
High
|
You-Sheng Yang |
Bug Description
Commit 5467801f1fcb ("gpio: Restrict usage of GPIO chip irq members before initialization") attempted to fix a race condition that lead to a NULL pointer, but in the process caused a regression for _AEI/_EVT declared GPIOs.
This manifests in messages showing deferred probing while trying to allocate IRQs like so:
amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x0000 to IRQ, err -517
amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x002C to IRQ, err -517
amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x003D to IRQ, err -517
[ .. more of the same .. ]
The code for walking _AEI doesn't handle deferred probing and so this leads to non-functional GPIO interrupts.
CVE References
Changed in linux (Ubuntu): | |
status: | New → Incomplete |
tags: | added: amd oem-priority originate-from-1971572 |
Changed in linux (Ubuntu): | |
status: | Incomplete → Invalid |
Changed in linux (Ubuntu Focal): | |
status: | New → Invalid |
Changed in linux (Ubuntu Jammy): | |
assignee: | nobody → You-Sheng Yang (vicamo) |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in linux-oem-5.14 (Ubuntu): | |
status: | New → Invalid |
Changed in linux-oem-5.14 (Ubuntu Focal): | |
assignee: | nobody → You-Sheng Yang (vicamo) |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in linux-oem-5.14 (Ubuntu Jammy): | |
status: | New → Invalid |
Changed in linux-oem-5.17 (Ubuntu): | |
status: | New → Invalid |
Changed in linux-oem-5.17 (Ubuntu Focal): | |
status: | New → Invalid |
Changed in linux-oem-5.17 (Ubuntu Jammy): | |
assignee: | nobody → You-Sheng Yang (vicamo) |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in linux (Ubuntu Jammy): | |
status: | Confirmed → Fix Committed |
Changed in linux-oem-5.14 (Ubuntu Focal): | |
status: | Confirmed → Fix Committed |
Changed in linux-oem-5.17 (Ubuntu Jammy): | |
status: | Fix Committed → Fix Released |
Changed in hwe-next: | |
importance: | Undecided → Critical |
status: | New → Fix Released |
To post a comment you must log in.
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 1971597
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.