From owner-freebsd-current  Fri Mar  8 14: 0:54 2002
Delivered-To: freebsd-current@freebsd.org
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20])
	by hub.freebsd.org (Postfix) with SMTP id C329E37B435
	for <current@freebsd.org>; Fri,  8 Mar 2002 14:00:41 -0800 (PST)
Received: (qmail 14512 invoked by uid 0); 8 Mar 2002 22:00:36 -0000
Received: from pd9e16a58.dip.t-dialin.net (HELO forge.local) (217.225.106.88)
  by mail.gmx.net (mp011-rz3) with SMTP; 8 Mar 2002 22:00:36 -0000
Received: from tmm by forge.local with local (Exim 3.34 #1)
	id 16jSPj-0002Ab-00; Fri, 08 Mar 2002 23:00:35 +0100
Date: Fri, 8 Mar 2002 23:00:35 +0100
From: Thomas Moestl <tmoestl@gmx.net>
To: Doug Barton <DougB@FreeBSD.org>
Cc: Murray Stokely <murray@FreeBSD.org>, bmah@FreeBSD.org,
	current@FreeBSD.org
Subject: Re: Preparing innocent users for -current
Message-ID: <20020308220035.GA4209@crow.dom2ip.de>
Mail-Followup-To: Doug Barton <DougB@FreeBSD.org>,
	Murray Stokely <murray@FreeBSD.org>, bmah@FreeBSD.org,
	current@FreeBSD.org
References: <20020308101724.GA8515@freebsdmall.com> <20020308110442.G32653-100000@zoot.corp.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20020308110442.G32653-100000@zoot.corp.yahoo.com>
User-Agent: Mutt/1.3.27i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

On Fri, 2002/03/08 at 11:23:36 -0800, Doug Barton wrote:
> 3. xconsole causes periodic panics. The problem (according to BDE) is "a
> well-know bug in printf(9)," caused by "The TIOCCONS ioctl ... panics when
> printf() is called while sched_lock is held." I reported this bug in
> October 2001, if anyone wants to look through the archives.

While this issue is still present, printf()s with sched_lock held seem
to fortunately be quite rare. IIRC your panics were caused by the
"microuptime went backwards" message, which was recently removed. The
only other relatively frequently reported printf() in this category I
can think of at the moment is for the "calcru: negative time..."
message.

	- thomas

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message