From owner-freebsd-alpha Fri Jan 26 16:20:20 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8285937B69C for ; Fri, 26 Jan 2001 16:20:00 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0R0K0G00132; Fri, 26 Jan 2001 16:20:00 -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 3F73037B698 for ; Fri, 26 Jan 2001 16:15:08 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0R0F8v99660; Fri, 26 Jan 2001 16:15:08 -0800 (PST) (envelope-from nobody) Message-Id: <200101270015.f0R0F8v99660@freefall.freebsd.org> Date: Fri, 26 Jan 2001 16:15:08 -0800 (PST) From: kjkoster@kjkoster.org To: freebsd-gnats-submit@freebsd.org X-Send-Pr-Version: www-1.0 Subject: alpha/24663: Console output gets scribbled into /var/log/messages Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24663 >Category: alpha >Synopsis: Console output gets scribbled into /var/log/messages >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-alpha >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jan 26 16:20:00 PST 2001 >Closed-Date: >Last-Modified: >Originator: Kees Jan Koster >Release: FreeBSD 4.2-stable >Organization: n/a >Environment: FreeBSD slugout.kjkoster.org 4.2-STABLE FreeBSD 4.2-STABLE #4: Thu Jan 25 00:56:30 CET 2001 kjkoster@slugout.kjkoster.org:/usr/src/sys/compile/SLUGOUT alpha NoName Alpha, trident ISA VGA card. My x86 PC does not exhibit this problem. >Description: When generating large chunks of console output on a graphics console on my Alpha bits and pieces of it end up in /var/log/messages. Here's what I see: Jan 27 01:03:40 slugout /kernel: 0 b681 4826 0005 f420 f000 203f 9681 4821 Jan 27 01:04:05 slugout /kernel: 5f74 6564 6376 616c 7373 Jan 27 01:04:35 slugout /kernel: 0 bf20 0036 fc00 ffff 0104 0000 0000 0000 Jan 27 01:04:40 slugout /kernel: 0 23e0 0046 fc00 ffff 0000 0000 0000 0000 Jan 27 01:04:40 slugout /kernel: b0e118>0258590 0018 0000 0000 0000 2b5e 0001 00 0007 Message from syslogd@slugout at Sat Jan 27 01:04:40 2001 ... slugout /kernel: b0e118>0258590 0018 0000 0000 0000 2b5e 0001 0001 0007 Jan 27 01:05:00 slugout /kernel: 0 6963 6b5f 756c 6764 5f65 6e75 7469 7300 Jan 27 01:05:05 slugout /kernel: 00 0000 0778 0000 0000 0000 Jan 27 01:05:35 slugout /kernel: 0 0020 a46b 0000 a483 0004 a044 f622 4841 Notice that the information has its date stamps intact although the strings are only parts of the original, they're logged from /kernel and they sometimes get written onto my terminal as messages. >How-To-Repeat: In one terminal start tail -f /var/log/messages On the console of the box start while true; do hexdump /kernel done Watch the messages. This problem does not happen when the hexdumps go to xterminals. I have no serial console to see if that is affected. >Fix: Dunno. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message