Re: port-amd64/37461 (x86 cpu dmesg output is noisy)

["Greg A. Woods; Planix, Inc." <woods%planix.ca@localhost>]

The following reply was made to PR port-amd64/37461; it has been noted by GNATS.

From: "Greg A. Woods; Planix, Inc." <woods%planix.ca@localhost>
To: "Jared D. McNeill" <jmcneill%invisible.ca@localhost>
Cc: gnats-bugs%NetBSD.org@localhost
Subject: Re: port-amd64/37461 (x86 cpu dmesg output is noisy)
Date: Mon, 12 May 2008 08:59:40 -0400

 On 12-May-08, at 8:38 AM, Jared D. McNeill wrote:
 
 > Greg A. Woods wrote:
 >> Can we please get the verbose CPU dmesg output back with "boot -v"?
 >>  I'd really like to still be able to see the details on demand.
 >
 > This information should be available now with cpuctl(8).
 
 Ah, I see.
 
 I wish I didn't actually have to install -current on the machine  
 though.  It's nice to be able to see details about the CPU in a box by  
 just booting a CD or kernel (even if the details are not always  
 complete -- I'm often just wanting to compare between machines, so  
 even just the hex features flag values and the cache sizes, etc. are  
 sufficient as I don't care about the names or if all the flags are  
 also printed correctly in slightly more human readable form).
 
 
 (on the other hand since I do normally always compile all of user-land  
 statically I can just copy the binary over onto my machine and run it  
 once I've booted a -current kernel -- but that won't always help for  
 those of you who do rely on shared libraries)
 
 -- 
                                        Greg A. Woods; Planix, Inc.
                                        <woods%planix.ca@localhost>