NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

kern/38696: cpu information in dmesg is badly formatted



>Number:         38696
>Category:       kern
>Synopsis:       cpu information in dmesg is badly formatted
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun May 18 23:10:04 +0000 2008
>Originator:     Henry Bent
>Release:        4.99.63
>Organization:
>Environment:
NetBSD aelfric 4.99.63 NetBSD 4.99.63 (AELFRIC) #3: Sun May 18 18:24:26 EDT 
2008  root@aelfric:/usr/obj/src-current/sys/arch/i386/compile/AELFRIC i386

>Description:
The errata message chops up the cpu info in dmesg like so:

cpu0 at mainbus0 apid 0cpu0: WARNING: AMD errata present, BIOS upgrade may be
cpu0: WARNING: necessary to ensure reliable operation
: AMD 686-class, 1808MHz, id 0x20f32
cpu0: AMD Power Management features: f<TTP,VID,FID,TS>
cpu0: AMD Cool`n'Quiet Technology 1800 MHz
cpu0: available frequencies (Mhz): 1000 1800
cpu0: 16 page colors
cpu1 at mainbus0 apid 1x86_ipi_init: ESR 00000004
: AMD 686-class, 1808MHz, id 0x20f32
cpu1: AMD Power Management features: f<TTP,VID,FID,TS>

And while I agree with the decision to clean up CPU information printing, why 
aren't we printing the CPU's self-identification string?  I used to see

cpu0: "Dual Core AMD Opteron(tm) Processor 165"

Which is a lot more helpful than just saying "AMD 686-class, 1800MHz" or 
whatever.
>How-To-Repeat:
Boot a sufficiently new kernel on a machine that reports CPU errata.
>Fix:
n/a



Home | Main Index | Thread Index | Old Index