Re: Empty dmesg output
- From: Dan Nelson <dnelson@xxxxxxxxxxxxxxx>
- Date: Fri, 29 Sep 2006 21:00:19 -0500
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
dnelson@xxxxxxxxxxxxxxx
_______________________________________________
freebsd-questions@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: Empty dmesg output
- From: Nicholas Killewald
- Re: Empty dmesg output
- References:
- Empty dmesg output
- From: Nicholas Killewald
- Empty dmesg output
- Prev by Date: Empty dmesg output
- Next by Date: Can't ping localhost?
- Previous by thread: Empty dmesg output
- Next by thread: Re: Empty dmesg output
- Index(es):
Relevant Pages
|
|
