From owner-freebsd-hackers Wed Jan 23 0:29:20 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (dhcp45-21.dis.org [216.240.45.21]) by hub.freebsd.org (Postfix) with ESMTP id A7E4837B438 for ; Wed, 23 Jan 2002 00:28:58 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.6) with ESMTP id g0N1l0d04015; Tue, 22 Jan 2002 17:47:00 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200201230147.g0N1l0d04015@mass.dis.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Greg Black Cc: Brian Reichert , "Roger 'Rocky' Vetterberg" , Brooks Davis , hackers@freebsd.org Subject: Re: cpu info in userland In-reply-to: Your message of "Wed, 23 Jan 2002 11:41:24 +1000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 22 Jan 2002 17:47:00 -0800 From: Michael Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > 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