Date: Tue, 19 Mar 2002 14:26:53 -0800 (PST) From: chris <cherbst@hotpop.com> To: freebsd-gnats-submit@FreeBSD.org Subject: misc/36110: dmesg output corrupt if /dev/console is busy Message-ID: <200203192226.g2JMQrc36898@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200203192226.g2JMQrc36898>