1791726 - Collect CPU microcode version on Linux

Status: RESOLVED FIXED

(Toolkit :: Crash Reporting, enhancement)

Description

[Henri Sivonen (:hsivonen)]

Of the operating systems that Firefox runs on, Linux systems are the most prone to fail to have the latest CPU microcode updates applied.

We should collect the CPU microcode version like we do on Windows (bug 1305120). This is a necessary prerequisite to filtering crash reports by stale microcode (or even alerting users to the fact they may have a bad time if they don't update the microcode).

Comment 1

[Henri Sivonen (:hsivonen)]

The back end bug is bug 1320921.

Comment 2

[Gabriele Svelto [:gsvelto]]

Interestingly we already have the CPU microcode information in Linux crash reports, because the minidump contains the whole contents of /proc/cpuinfo, so we only need to surface it, I'll file a bug in rust-minidump for that.

Comment 3

[Gabriele Svelto [:gsvelto]]

Mmm... actually we already put that in the stackwalker output, it's just that Socorro doesn't pick it up yet. If I run the stack-walker on this crash the system info field has the following:

"system_info": {
    "cpu_arch": "amd64",
    "cpu_count": 2,
    "cpu_info": "family 6 model 23 stepping 10",
    "cpu_microcode_version": 2571,
    "os": "Linux",
    "os_ver": "5.4.0-126-generic #142-Ubuntu SMP Fri Aug 26 12:12:57 UTC 2022"
}

So there's a few things that need to happen:

• We need to teach Socorro to look at that field when the CPUMicrocodeVersion annotation is missing
• We should teach the stack walker to print it in hex format because that's what we use on Windows
• We should also teach the stack walker to populate that field when the input includes the crash annotations and the CPUMicrocodeVersion one is populated

Comment 4

[Gabriele Svelto [:gsvelto]]

I filed issue 683 for the stack walker part.

Comment 5

[Gabriele Svelto [:gsvelto]]

We fixed this when bug 1791742 went into prod.