Date: Mon, 05 Jun 2006 18:27:28 -0700 From: Chris Maness <chris@chrismaness.com> To: Reko Turja <reko.turja@liukuma.net> Cc: freebsd-questions@freebsd.org Subject: Re: dmesg not working on new system Message-ID: <4484DA00.6040201@chrismaness.com> In-Reply-To: <023401c688f6$090458d0$0a0aa8c0@rivendell> References: <44843B61.5050209@chrismaness.com><448469D5.8060700@scls.lib.wi.us><20060605105358.Q54670@ns1.internetinsite.com><44847336.9050908@scls.lib.wi.us> <448xobpi30.fsf@be-well.ilk.org> <20060605145453.S55741@ns1.internetinsite.com> <023401c688f6$090458d0$0a0aa8c0@rivendell>
next in thread | previous in thread | raw e-mail | index | archive | help
Reko Turja wrote: > > ----- Original Message ----- From: "Chris Maness" <chris@chrismaness.com> > >> Yes, it does, but why would it not show anything without the flag >> right after a reboot? Wierd. I almost suspect hard drive issues. > > I got the exactly same happen to me with 6.1-RELEASE updated just > after 6.1 was released. Didn't think about the weirdness really until > now seeing your messages. The symptoms were exactly the same, > /var/dmesg file was empty right after the boot and of course dmesg > command didn't print the booting messages either. > > Things seems to be normalized for me with 6.1-STABLE from yesterday, > but haven't booted since buildworld process after which I got proper > dmesg output. > > -Reko Well, that makes me feel better. I thought my hardrive (old as hek) was going bad. This is my slave name server so I'm not too terribly concerned.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4484DA00.6040201>