From owner-freebsd-stable@FreeBSD.ORG Thu Jun 5 15:20:03 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 88DCC37B401 for ; Thu, 5 Jun 2003 15:20:03 -0700 (PDT) Received: from smtp0.adl1.internode.on.net (smtp0.adl1.internode.on.net [203.16.214.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E2F843FBD for ; Thu, 5 Jun 2003 15:20:02 -0700 (PDT) (envelope-from malcolm.kay@internode.on.net) Received: from beta.home (ppp304.sa.padsl.internode.on.net [150.101.245.47]) h55MJxCT000322; Fri, 6 Jun 2003 07:49:59 +0930 (CST) Content-Type: text/plain; charset="iso-8859-1" From: Malcolm Kay Organization: At home To: freebsd-stable@freebsd.org Date: Fri, 6 Jun 2003 07:49:58 +0930 User-Agent: KMail/1.4.3 References: <200306060117.39607.malcolm.kay@internode.on.net> <20030605164520.GC32515@happy-idiot-talk.infracaninophile.co.uk> In-Reply-To: <20030605164520.GC32515@happy-idiot-talk.infracaninophile.co.uk> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200306060749.58906.malcolm.kay@internode.on.net> Subject: Re: dmesg -- multiple boot messages X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jun 2003 22:20:03 -0000 It's a relief to know it is not indicitive of hardware problems. And yes, I do see the value. I take it this is not then so much a function of the release version of FreeBSD but the available characteristics of this new hardware. On Fri, 6 Jun 2003 02:15, Matthew Seaman wrote: > On Fri, Jun 06, 2003 at 01:17:39AM +0930, Malcolm Kay wrote: > > I observe the 'dmesg' gives startup information not only for the late= st > > boot but also information generated in a number of previous boots. > > > > I've not seen this with earlier FreeBSD realeases including 4.7. > > > > Is it normal for FreeBSD 4.8 or should I be looking for hardware > > problems? > > Yes, that's normal. Certain BIOSes can be persuaded not to clear the > memory buffer where the dmesg data are stored during reboots. If this > feature is available, FreeBSD will take advantage of it -- that dmesg > buffer might be your only clue as to why the machine just rebooted at > all. > > The /var/log/dmesg.{today,yesterday} files will be produced overnight > by the 700.kernelmsg periodic security script. Should be automatic in > the default configuration. > On Fri, 6 Jun 2003 02:19, Michael Sierchio wrote: > Normal. > > /var/run/dmesg.boot contains just the dmesg from the most recent boot. Thanks guys, Malcolm Kay