From owner-freebsd-alpha Tue May 9 6: 0:58 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from burka.carrier.kiev.ua (burka.carrier.kiev.ua [193.193.193.107]) by hub.freebsd.org (Postfix) with ESMTP id 448A237B743 for ; Tue, 9 May 2000 06:00:54 -0700 (PDT) (envelope-from netch@lucky.net) Received: from netch@localhost by burka.carrier.kiev.ua id QAI88139 for freebsd-alpha@freebsd.org; Tue, 9 May 2000 16:00:51 +0300 (EEST) (envelope-from netch) Date: Tue, 9 May 2000 16:00:51 +0300 From: Valentin Nechayev To: freebsd-alpha@freebsd.org Subject: multi-session dmesg Message-ID: <20000509160051.B83860@lucky.net> Reply-To: netch@lucky.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-42: On Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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. -- NVA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message