dmesg -- multiple boot messages
Malcolm Kay
malcolm.kay at internode.on.net
Thu Jun 5 15:20:03 PDT 2003
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 latest
> > 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
More information about the freebsd-stable
mailing list