Closed Bug 1791742 Opened 2 years ago Closed 2 years ago

Use the `system_info.cpu_microcode_version` field when available

Categories

(Socorro :: Processor, task, P2)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: gsvelto, Assigned: willkg)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

Our Windows crashes usually contain a CPUMicrocodeVersion annotation that can be useful for detecting crashes coming from machines missing microcode updates. On Linux we don't populate that annotation but we do have the field stored in the minidump, the stack walker surfaces it in the system_info.cpu_microcode_version field. It would be nice to use this as the source of the microcode version instead of the annotation if possible. I filed issues 683 to populate this field in the stackwalker whenever the CPUMicrocodeVersion annotation is present.

Would it be possible to have the processor prefer the value of system_info.cpu_microcode_version if it's available and fall back to CPUMicrocodeVersion if not?

Currently, it's pulled from the annotation:

https://github.com/mozilla-services/socorro/blob/98ded7173f547ddd0b52d19c00a3a0b46d5f575b/socorro/schemas/processed_crash.schema.yaml#L1057-L1061

We can change that to pull from the stackwalker output and degrade to the annotation if present. We'll need a new rule for that.

Assignee: nobody → willkg
Status: NEW → ASSIGNED
Priority: -- → P2

Oops--turns out that the value the stackwalker emits is a different type.

https://sentry.io/organizations/mozilla/issues/3719279295/?project=6700122

Example: bp-875b8cdf-f0c6-47df-a045-4c9270221104

Duplicate of this bug: 1320921
Duplicate of this bug: 1320944

This was deployed just now in bug #1799933. Marking as FIXED.

Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: