Here’s a breakdown of what that string means, followed by content you can use for documentation, a blog post, a system report, or a troubleshooting guide.
As of 2024, Family 6 Model 58 (Ivy Bridge) is considered legacy hardware. acpi genuineintel---intel64-family-6-model-58
The exact triple-dash string is not standard in any major Linux distribution’s clean logs. Searching the internet yields few direct results; those who see it often ask on forums about “strange CPU identifier” or “acpi genuineintel---”. It is likely an artifact of a custom build, an old kernel (2.6.32 era with certain ACPI debug flags), or a poorly written kernel module that prints raw CPUID and ACPI concatenated fields. Here’s a breakdown of what that string means,
Nevertheless, family 6 model 58 is very common in the wild. Millions of Ivy Bridge systems were sold from 2012–2014, and many still run Linux as home servers, media centers, or legacy workstations. Part 5: Common Issues and Debugging
5
If you expect to see it but don’t, your kernel might have been compiled with CONFIG_DEBUG_KERNEL=n or CONFIG_ACPI_DEBUG=n. The string is debug-level (KERN_DEBUG), so it may be hidden by default. Run dmesg -l debug to reveal it.
\_PR.CPUx – Each logical processor (core + HT). Model 58 has up to 4 cores / 8 threads (desktop/mobile), or up to 10 cores / 20 threads (Xeon E5 v2)._PSS (Performance Supported States) – Defines P-states (frequency/voltage pairs). The OS expects:
PERF_CTL (0x199) and PERF_STATUS (0x198) for P-state transitions._PPC (Performance Present Capabilities) – Dynamic limit for thermal/power throttling._TSS (Throttling Supported States) – T-states via clock modulation (MSR 0x19A). Rarely used in modern OS, but ACPI includes it.As of kernel 6.x, Ivy Bridge (model 58) is considered legacy but still supported:
intel_pstate driver no longer enables itself by default (requires intel_pstate=force).acpi-cpufreq remains the default scaling driver.intel_idle driver is fully functional.If you see the malformed string on a modern kernel, it is harmless if no functional issues exist. If you’re maintaining a distribution or embedded system based on Ivy Bridge, you can safely ignore cosmetic printk anomalies.