From owner-freebsd-bugs  Tue Feb 11 22:50:08 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id WAA08611
          for bugs-outgoing; Tue, 11 Feb 1997 22:50:08 -0800 (PST)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id WAA08592;
          Tue, 11 Feb 1997 22:50:04 -0800 (PST)
Date: Tue, 11 Feb 1997 22:50:04 -0800 (PST)
Message-Id: <199702120650.WAA08592@freefall.freebsd.org>
To: freebsd-bugs
Cc: 
From: Bruce Evans <bde@zeta.org.au>
Subject: Re: kern/2717: Panic with daily script (find)
Reply-To: Bruce Evans <bde@zeta.org.au>
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR kern/2717; it has been noted by GNATS.

From: Bruce Evans <bde@zeta.org.au>
To: freebsd-gnats-submit@FreeBSD.ORG, futagi@csctk.jcsnet.or.jp
Cc:  Subject: Re: kern/2717: Panic with daily script (find)
Date: Wed, 12 Feb 1997 17:40:11 +1100

 >We added our original 'firewall' code to some modules in /sys/netinet
 >This firewall module puts many 'printf' messages to syslog and console.
 
 The standard (syscons) console driver and perhaps the pcvt console driver
 have some races when kernel printfs from interrupt handlers are mixed with
 normal console output.
 
 Workarounds: don't put (m)any printfs in interrupt handlers, or don't use
 /dev/ttyv0 for normal applications (it's still used for console output by
 syslogd etc so this only reduces the problem), or use a serial console.
 
 >>How-To-Repeat:
 
 Do `printf("*");' every clock tick in a timeout handler while an application
 is writing to the console.
 
 Bruce