Fix hp_wmi_read_int() reporting error (0x05)
Bug #1979051 reported by
Andy Chi
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OEM Priority Project |
Fix Released
|
Critical
|
Andy Chi | ||
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Invalid
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Medium
|
Unassigned | ||
linux-oem-5.14 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Invalid
|
Undecided
|
Unassigned | ||
linux-oem-5.17 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Invalid
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
Fix hp_wmi_read_int() reporting error (0x05)
[Fix]
commit id 12b19f14a: platform/x86: hp-wmi: Fix hp_wmi_read_int() reporting error (0x05)
[Test]
Verified on EliteBook 840 G9 Notebook and it won't report 0x05 after wmi query
[Where problems could occur]
Fix the return error should not have impact on DUTs rather than HP.
CVE References
tags: | added: oem-priority originate-from-1974120 stella |
Changed in oem-priority: | |
status: | New → Confirmed |
importance: | Undecided → Critical |
assignee: | nobody → Andy Chi (andch) |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
Changed in linux (Ubuntu Jammy): | |
importance: | Undecided → Medium |
status: | New → In Progress |
Changed in linux (Ubuntu): | |
status: | Incomplete → Invalid |
Changed in linux-oem-5.14 (Ubuntu Jammy): | |
status: | New → Invalid |
no longer affects: | linux-oem-5.14 (Ubuntu) |
no longer affects: | linux-oem-5.14 (Ubuntu Jammy) |
no longer affects: | linux-oem-5.14 (Ubuntu) |
no longer affects: | linux-oem-5.17 (Ubuntu) |
no longer affects: | linux-oem-5.14 (Ubuntu) |
no longer affects: | linux-oem-5.17 (Ubuntu Jammy) |
Changed in linux (Ubuntu Jammy): | |
status: | In Progress → Fix Committed |
Changed in linux-oem-5.17 (Ubuntu Focal): | |
status: | New → Invalid |
Changed in linux-oem-5.14 (Ubuntu): | |
status: | New → Invalid |
Changed in linux (Ubuntu Focal): | |
status: | New → Invalid |
no longer affects: | linux (Ubuntu Jammy) |
Changed in linux (Ubuntu Jammy): | |
importance: | Undecided → Medium |
status: | New → Fix Committed |
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.14 (Ubuntu Focal): | |
status: | New → Fix Committed |
Changed in oem-priority: | |
status: | Confirmed → Fix Released |
Changed in linux-oem-5.17 (Ubuntu Jammy): | |
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 1979051
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.