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-questions@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"



Relevant Pages

  • Re: Empty dmesg output
    ... my FreeBSD machine isn't reporting anything ... 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 ...
    (freebsd-questions)
  • Re: Kernel Badness 2.6.14-Git
    ... > I just pulled from Linus Tree and I'm getting this badness in dmesg. ... > Please let me know if it is too soon to start reporting this. ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)
  • Re: Empty dmesg output
    ... my FreeBSD machine isn't reporting anything ... get logged to the dmesg buffer but aren't printed by the dmesg command. ... can see the kernel bootup log at /var/run/dmesg.boot. ...
    (freebsd-questions)
  • Re: Dual core CPUs, but only 2 CPUs in-use?
    ... Under FreeBSD 6.3, dmesg is reporting the 4 CPUs, but systat is only ...
    (freebsd-questions)
  • Re: Dual core CPUs, but only 2 CPUs in-use?
    ... Under FreeBSD 6.3, dmesg is reporting the 4 CPUs, but systat is only ...
    (freebsd-questions)