lscpu: Skip aarch64 decode path for rest of the architectures
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
util-linux (Ubuntu) | Status tracked in Oracular | |||||
Noble |
New
|
Undecided
|
Unassigned | |||
Oracular |
New
|
Undecided
|
Unassigned |
Bug Description
lscpu behaves differently when run sudo vs non-sudo on AMD architectures.
On sudo runs, it adds a BIOS model name and BIOS CPU family which it
does not add for the latter. However since this parsing from the DMI is
primarily catered to aarch64, for AMD platform the BIOS model name is
printed out as follows "AMD XXX Processor *Unknown* CPU @ X.XGHz" due
to the part number is not populated on the platform.
The issue boils down to an unconditional call to arm_decode() which
attempts to read the DMI path and populate the processor information
such as processor version and part number which is set to Unknown on AMD
CPUs.
81d6de9 (lscpu: remove the old code) changed the DMI path from
/sys/firmware/
/sys/firmware/
issue to light as DMI was starting to be parsed incorrectly.
Therefore, do not perform aarch64 parsing for other architectures.
https:/
Changed in linux (Ubuntu): | |
status: | New → Invalid |
no longer affects: | linux (Ubuntu Noble) |
no longer affects: | linux (Ubuntu Oracular) |
This is a userspace utility in the util-linux package, and not a kernel issue. Removed the kernel from the Affected projects.