Empty dmesg output
Nicholas Killewald
captainspam at speakeasy.net
Fri Sep 29 19:20:55 PDT 2006
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
More information about the freebsd-questions
mailing list