Date: Tue, 22 Jan 2002 17:47:00 -0800 From: Michael Smith <msmith@freebsd.org> To: Greg Black <gjb@gbch.net> Cc: Brian Reichert <reichert@numachi.com>, "Roger 'Rocky' Vetterberg" <listsub@rambo.simx.org>, Brooks Davis <brooks@one-eyed-alien.net>, hackers@freebsd.org Subject: Re: cpu info in userland Message-ID: <200201230147.g0N1l0d04015@mass.dis.org> In-Reply-To: Your message of "Wed, 23 Jan 2002 11:41:24 %2B1000." <nospam-1011750084.73718@bambi.gbch.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> Brian Reichert wrote: > > | I've seen situations where 'dmesg' (and by extension dmesg.boot) > | will contain multiple passes of device probes, etc. I could easily > | be imagining this, as I can't think of a mechanism to allow for > | it, nor a reason to do it... > > You're not imagining it -- certainly 4.4-RELEASE does this. The message buffer is not perturbed by the boot process unless the BIOS overwrites it. If the BIOS doesn't overwrite it, it's preserved from one boot to the next. This, this symptom varies from system to system. -- Go where you may, search where you will, roam throughout all the monarchies and despotisms of the Old World, travel through South America, search out every abuse and when you have found the last, lay your facts by the everyday practices of this nation, and you will say with me that, for revolting barbarity and shameless hypocrisy, America reigns without a rival... - Frederic Douglass, Independence Day Address, 1852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200201230147.g0N1l0d04015>