From owner-freebsd-current@FreeBSD.ORG Wed Nov 29 18:21:22 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9F77516A5C8; Wed, 29 Nov 2006 18:21:22 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3393243CA3; Wed, 29 Nov 2006 18:21:19 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id kATIL8qp092792; Wed, 29 Nov 2006 13:21:20 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 29 Nov 2006 12:04:03 -0500 User-Agent: KMail/1.9.1 References: <45622068.2050705@student.tue.nl> In-Reply-To: <45622068.2050705@student.tue.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200611291204.03716.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Wed, 29 Nov 2006 13:21:20 -0500 (EST) X-Virus-Scanned: ClamAV 0.88.3/2258/Wed Nov 29 07:04:15 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: jb@freebsd.org, Rene Ladan Subject: Re: calcru-triggered panic? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Nov 2006 18:21:22 -0000 On Monday 20 November 2006 16:38, Rene Ladan wrote: > Hi, > > I got the attached panic on CURRENT 2006-11-17. > > It was preceded by a lot of 'calcru' messages. The calcru messages you can ignore. This is the real problem: panic: blockable sleep lock (sleep mutex) tty @ /usr/src-current/sys/kern/kern_event.c:1670 This panic is due to the recent changes to printf to try to buffer the printf output. It now runs cnputc() under a critical section and syscons(4) tries to do a ttwakeup() which invokes KNOTE() and tries to lock a regular mutex while inside the critical section. I'm not sure how best to fix this. -- John Baldwin