Don't WARN_ON_ONCE() for a broken discovery table
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Medium
|
Tim Gardner | ||
Lunar |
Won't Fix
|
Medium
|
Tim Gardner |
Bug Description
SRU Justification
[Impact]
perf/x86/uncore: Don't WARN_ON_ONCE() for a broken discovery table
The kernel warning message is triggered, when SPR MCC is used.
[ 17.945331] ------------[ cut here ]------------
[ 17.946305] WARNING: CPU: 65 PID: 1 at
arch/
intel_
[ 17.946305] Modules linked in:
[ 17.946305] CPU: 65 PID: 1 Comm: swapper/0 Not tainted
5.4.
It's caused by the broken discovery table of UPI.
The discovery tables are from hardware. Except for dropping the broken
information, there is nothing Linux can do. Using WARN_ON_ONCE() is
overkilled.
Use the pr_info() to replace WARN_ON_ONCE(), and specify what uncore unit
is dropped and the reason.
[Fix]
Commit 5d515ee40cb57ea
[Test]
AWS tested
[Regression potential]
Low regression potential. Only the code that prints the warning has been changed.
[Other Info]
SF: #00347830
Changed in linux (Ubuntu): | |
status: | New → Fix Released |
description: | updated |
Changed in linux (Ubuntu Lunar): | |
status: | In Progress → Won't Fix |
Changed in linux (Ubuntu Jammy): | |
status: | In Progress → Fix Committed |
https:/ /lists. ubuntu. com/archives/ kernel- team/2024- January/ 147974. html