Date: Fri, 29 Sep 2006 21:00:19 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: Nicholas Killewald <captainspam@speakeasy.net> Cc: freebsd-questions@freebsd.org Subject: Re: Empty dmesg output Message-ID: <20060930020018.GB77128@dan.emsphone.com> In-Reply-To: <451DCDB9.1090306@speakeasy.net> References: <451DCDB9.1090306@speakeasy.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060930020018.GB77128>