CPU information is not always correct/complete

Bug #1714304 reported by Jeff Lane 
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Checkbox Provider - Resource
Fix Released
Medium
Jeff Lane 

Bug Description

The information displayed on certificates for CPU is not always complete.

For example, on a recent ARM certification:
https://certification.ubuntu.com/certification/hardware/201708-25656/

CPU is listed as aarch64 aarch64

I have a feeling this is because there is no CPU identifying data in cpuinfo and lshw. However, DMI DOES have accurate CPU identifier data:

Handle 0x001D, DMI type 4, 48 bytes
Processor Information
        Socket Designation: CPU01
        Type: Central Processor
        Family: ARM
        Manufacturer: Hisilicon
        ID: 82 D0 0F 41 00 00 00 00
        Version: Hi1616
        Voltage: 0.9 V
        External Clock: 50 MHz
        Max Speed: 2400 MHz
        Current Speed: 2400 MHz
        Status: Populated, Enabled
        Upgrade: Unknown
        L1 Cache Handle: 0x001A
        L2 Cache Handle: 0x001B
        L3 Cache Handle: 0x001C
        Serial Number: To be filled by O.E.M.
        Asset Tag: To be filled by O.E.M.
        Part Number: To be filled by O.E.M.
        Core Count: 32
        Core Enabled: 32
        Thread Count: 32
        Characteristics:
                64-bit capable
                Multi-Core
                Execute Protection
                Enhanced Virtualization
                Power/Performance Control

Note the Manufacturer and Version fields provide the desired Identifier data for this ARM64 CPU/SoC.

Jeff Lane  (bladernr)
tags: added: hwcert-server
Revision history for this message
Jeff Lane  (bladernr) wrote :

This was actually fixed by a different bug fix that took care of running DMI jobs when applicable.

Changed in plainbox-provider-resource:
status: New → Fix Released
assignee: nobody → Jeff Lane (bladernr)
importance: Undecided → Medium
Jeff Lane  (bladernr)
Changed in plainbox-provider-resource:
milestone: none → 0.34.0
milestone: 0.34.0 → none
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.