Add missing ARM-cores to support Vera-based systems

Bug #2123886 reported by Joao Andre Simioni
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
util-linux (Ubuntu)
Status tracked in Resolute
Noble
In Progress
Undecided
Zachary Raines
Plucky
In Progress
Undecided
Zachary Raines
Questing
In Progress
Undecided
Zachary Raines
Resolute
In Progress
Undecided
Zachary Raines

Bug Description

[Impact]

When running "lscpu" on a Vera-based system, it doesn't report a model name:

Vendor ID: ARM
Model: 0

[Fix]

Adding the additional arm_part to sys-utils/lscpu-arm.c solves the problem. The commit below adds the specific codes missing from Noble's (and previous) versions.

https://github.com/util-linux/util-linux/commit/908777470d403ec30c525472ba0d3701c9c5a223

[Test Steps]

* Verify whether output of lscpu is correct on new CPUs; eg:
Vendor ID: ARM
Model name: Olympus

* Verify whether output of lscpu doesn't change on old CPUs; eg:
Vendor ID: ARM
Model name: Neoverse-N1

[What Could Go Wrong]

The fix only introduces additional model identifiers to match
against and print a model name string, thus regression impact
should be contained within lscpu and printing cpus model name
on ARM systems.

Output doesn't change on systems with non-affected CPU models.

Tags: se-sponsors

Related branches

Revision history for this message
Zachary Raines (raineszm) wrote :

Added a debdiff for noble cherry-picking the patch from upstream (thanks ~jasimioni).

TESTED: lscpu output is identical in a fresh noble lxd container on my machine.

Changed in util-linux (Ubuntu Noble):
assignee: nobody → Zachary Raines (raineszm)
status: New → In Progress
tags: added: se-sponsors
Revision history for this message
Zachary Raines (raineszm) wrote :
Changed in util-linux (Ubuntu Plucky):
status: New → In Progress
assignee: nobody → Zachary Raines (raineszm)
Changed in util-linux (Ubuntu Questing):
status: New → In Progress
assignee: nobody → Zachary Raines (raineszm)
Revision history for this message
Zachary Raines (raineszm) wrote :
Revision history for this message
Simon Chopin (schopin) wrote :

Hi,

I'm sorry to have to tell you this, but you'll have to rework your questing patch since questing has been released and resolute is now the new development series.

For resolute, I'd check whether the issue would be fixed by a merge from Debian, as their upstream version is higher.

Please resubscribe ubuntu-sponsors once you feel this is ready for another round of reviews.

Revision history for this message
Zachary Raines (raineszm) wrote :

Thanks, Simon. I've confirmed that the fix is in the debian version and I'm working on a merge proposal to merge that into resolute. I'll update the debdiff for questing.

Revision history for this message
Zachary Raines (raineszm) wrote :

I've submitted a merge proposal for the Debian version, linked above. As far as I can tell the questing debdiff still applies cleanly on top of the current questing version.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.