Date: Thu, 5 Jun 2003 17:45:20 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Malcolm Kay <malcolm.kay@internode.on.net> Cc: freebsd-stable@freebsd.org Subject: Re: dmesg -- multiple boot messages Message-ID: <20030605164520.GC32515@happy-idiot-talk.infracaninophile.co.uk> In-Reply-To: <200306060117.39607.malcolm.kay@internode.on.net> References: <200306060117.39607.malcolm.kay@internode.on.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--bKyqfOwhbdpXa4YI
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Jun 06, 2003 at 01:17:39AM +0930, Malcolm Kay wrote:
> I observe the 'dmesg' gives startup information not only for the latest=
=20
> boot but also information generated in a number of previous boots.
>=20
> I've not seen this with earlier FreeBSD realeases including 4.7.
>=20
> 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.
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
--bKyqfOwhbdpXa4YI
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (FreeBSD)
iD8DBQE+33OgdtESqEQa7a0RAtr3AJ9gTpzLZnwN1U5EcpgkDE83rEjbbQCgnAZY
VPaVsP7V9ipCk6GozUcXhpc=
=W2+o
-----END PGP SIGNATURE-----
--bKyqfOwhbdpXa4YI--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030605164520.GC32515>