Date: Sun, 7 Oct 2001 14:49:16 +1000 (EST) From: Bruce Evans <bde@zeta.org.au> To: Doug Barton <DougB@DougBarton.net> Cc: <freebsd-current@FreeBSD.ORG> Subject: Re: panic: blockable sleep lock (sx) allproc @ /usr/local/src/sys/kern/kern_proc.c:212 Message-ID: <20011007142123.A6012-100000@delplex.bde.org> In-Reply-To: <3BBF6540.AF950344@DougBarton.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011007142123.A6012-100000>