From owner-freebsd-bugs  Tue Mar 19 14:30:27 2002
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP id A530F37B42F
	for <freebsd-bugs@hub.freebsd.org>; Tue, 19 Mar 2002 14:30:01 -0800 (PST)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.11.6/8.11.6) id g2JMU1S37795;
	Tue, 19 Mar 2002 14:30:01 -0800 (PST)
	(envelope-from gnats)
Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP id 5FB6D37B404
	for <freebsd-gnats-submit@FreeBSD.org>; Tue, 19 Mar 2002 14:26:53 -0800 (PST)
Received: (from nobody@localhost)
	by freefall.freebsd.org (8.11.6/8.11.6) id g2JMQrc36898;
	Tue, 19 Mar 2002 14:26:53 -0800 (PST)
	(envelope-from nobody)
Message-Id: <200203192226.g2JMQrc36898@freefall.freebsd.org>
Date: Tue, 19 Mar 2002 14:26:53 -0800 (PST)
From: chris <cherbst@hotpop.com>
To: freebsd-gnats-submit@FreeBSD.org
X-Send-Pr-Version: www-1.0
Subject: misc/36110: dmesg output corrupt if /dev/console is busy
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-bugs.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-bugs>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-bugs>
X-Loop: FreeBSD.org


>Number:         36110
>Category:       misc
>Synopsis:       dmesg output corrupt if /dev/console is busy
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Mar 19 14:30:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     chris
>Release:        4.5-RELEASE
>Organization:
>Environment:
FreeBSD testing 4.5-RELEASE FreeBSD 4.5-RELEASE #4: Mon Mar 18 13:18:54 EST 2002     chris@testing:/usr/src/sys/compile/LOCAL  i386
>Description:
     At version 4.3 dmesg -a was added, so you can see console output remotely.  If you have lots of output going to /dev/console (happened at 32k of data here) dmesg output will not be readable eventually.  The LINT file says MSGBUF_SIZE=40960, but "dmesg -a >file;du file" reports 32(k) when it is broken.  It should push out old lines and append new ones when it is full.
>How-To-Repeat:
Set up syslog to log to /dev/console, and send more than ~32k (or whatever your MSGBUF_SIZE is) of data to that facility.  Then run dmesg.  If it is corrupt, run dmesg -a, redirect to a file, and see how large the file is.  It should be about the same as MSGBUF_SIZE.
>Fix:
      Reboot to get a sane dmesg output back.
>Release-Note:
>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message