From owner-freebsd-current Sat Oct 6 21:50:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id D213E37B405 for ; Sat, 6 Oct 2001 21:50:09 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id OAA08250; Sun, 7 Oct 2001 14:49:57 +1000 Date: Sun, 7 Oct 2001 14:49:16 +1000 (EST) From: Bruce Evans X-X-Sender: To: Doug Barton Cc: Subject: Re: panic: blockable sleep lock (sx) allproc @ /usr/local/src/sys/kern/kern_proc.c:212 In-Reply-To: <3BBF6540.AF950344@DougBarton.net> Message-ID: <20011007142123.A6012-100000@delplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 6 Oct 2001, Doug Barton wrote: > Bruce Evans wrote: > > > This is a well-know bug in printf(9). The TIOCCONS ioctl always gave > > non-deterministic crashes. Now it gives determinstic panics when > > pintf() is called while sched_lock is held. Work-around: don't use > > anything that uses TIOCCONS (xconsole?). > > Yes, I'm using xconsole, and I find it very useful. How hard would it be > to actually fix this? I'm still crashing fairly often with this same exact > problem. Thanks. No one actually acknowledged my diagnosis of this bug before (I don't use xconsole and haven't got around to trying it). Is using xconsole significantly better than "tail -f /var/log/messages"? Both have the problem of not being able to show any output if userland can't run, but I think this problem would be only slightly larger for syslogd and tail combined than for xconsole. A fix would involve more buffering in the kernel, or perhaps more elegantly, dropping TIOCCONS and putting "tail -f"-like support in dmesg. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message