Date: Tue, 9 May 2000 20:50:46 +0100 (BST) From: Doug Rabson <dfr@nlsystems.com> To: Valentin Nechayev <netch@lucky.net> Cc: freebsd-alpha@freebsd.org Subject: Re: multi-session dmesg Message-ID: <Pine.BSF.4.21.0005092049460.47945-100000@salmon.nlsystems.com> In-Reply-To: <20000509160051.B83860@lucky.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 9 May 2000, Valentin Nechayev wrote: > At our current system (4.0-20000502-STABLE), dmesg buffer is not cleared > during system boot and contains previous data. This looks as following: > > === cut part of /var/run/dmesg === > dc0: TX underrun -- increasing TX threshold > dc0: TX underrun -- increasing TX threshold > dc0: TX underrun -- increasing TX threshold > Waiting (max 60 seconds) for system process `bufdaemon' to stop...stopped > Waiting (max 60 seconds) for system process `syncer' to stop...stopped > > syncing disks... 31 30 27 20 9 > done > Uptime: 26m9s > Rebooting... > Copyright (c) 1992-2000 The FreeBSD Project. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 4.0-STABLE #0: Tue May 2 23:54:37 EEST 2000 > root@aleph.carrier.kiev.ua:/var/src/sys/compile/ALEPH > EB164 > Digital AlphaPC 164SX 533 MHz, 531MHz > === end cut === > > Is it bug or feature? > I strongly want it to be feature because this buffer may contain panic report > and previous important messages in panic case. This is a feature. The message buffer is always in the same place in memory and if its contents survive the reboot (there are magic numbers which are checked), then the kernel keeps the contents. Its extremely useful when hacking on kernels. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 20 8442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0005092049460.47945-100000>