Empty dmesg output

Is there any situation in which dmesg should give no output
whatsoever?
   Currently, my FreeBSD machine (RELEASE-6.0) isn't
reporting anything
at all when I call up dmesg.  It has been on for quite some
time, and to
the best of my knowledge there isn't much of interest it
should have
reported recently.  It DID say something back at its initial
bootup and
for some time thereafter, but nothing now.  Is this normal,
or should I
be a bit concerned?
-- 
Nicholas Killewald
_______________________________________________
freebsd-questionsfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribefreebsd.org"

In the last episode (Sep 29), Nicholas Killewald said:
> Is there any situation in which dmesg should give no
output whatsoever?
>    Currently, my FreeBSD machine (RELEASE-6.0) isn't
reporting anything
> at all when I call up dmesg.  It has been on for quite
some time, and to
> the best of my knowledge there isn't much of interest
it should have
> reported recently.  It DID say something back at its
initial bootup and
> for some time thereafter, but nothing now.  Is this
normal, or should I
> be a bit concerned?

Things printed to the console (via syslog or writing to
/dev/console)
get logged to the dmesg buffer but aren't printed by the
dmesg command.
If you've had lots of console output all your kernel
messages may have
been pushed out.  Try running "dmesg -a" to see
the raw buffer.  You
can see the kernel bootup log at /var/run/dmesg.boot .

-- 
	Dan Nelson
	dnelsonallantgroup.com
_______________________________________________
freebsd-questionsfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribefreebsd.org"

Dan Nelson wrote:
> In the last episode (Sep 29), Nicholas Killewald said:
>> Is there any situation in which dmesg should give
no output whatsoever?
>>    Currently, my FreeBSD machine (RELEASE-6.0)
isn't reporting anything
>> at all when I call up dmesg.  It has been on for
quite some time, and to
>> the best of my knowledge there isn't much of
interest it should have
>> reported recently.  It DID say something back at
its initial bootup and
>> for some time thereafter, but nothing now.  Is this
normal, or should I
>> be a bit concerned?
> 
> Things printed to the console (via syslog or writing to
/dev/console)
> get logged to the dmesg buffer but aren't printed by
the dmesg command.
> If you've had lots of console output all your kernel
messages may have
> been pushed out.  Try running "dmesg -a" to
see the raw buffer.  You
> can see the kernel bootup log at /var/run/dmesg.boot .
> 

Aha... that makes sense.  Yep, that was it, the console
messages must've
flooded out any kernel messages.  Thanks!

-- 
Nicholas Killewald
_______________________________________________
freebsd-questionsfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribefreebsd.org"