From owner-freebsd-current@FreeBSD.ORG Thu Aug 10 18:05:58 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C607E16A4DE for ; Thu, 10 Aug 2006 18:05:58 +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 E4AAA43D4C for ; Thu, 10 Aug 2006 18:05:57 +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 k7AI5pXL075318; Thu, 10 Aug 2006 14:05:51 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Thu, 10 Aug 2006 13:19:48 -0400 User-Agent: KMail/1.9.1 References: <44BA5E58.6060306@cs.chalmers.se> In-Reply-To: <44BA5E58.6060306@cs.chalmers.se> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200608101319.48698.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]); Thu, 10 Aug 2006 14:05:52 -0400 (EDT) X-Virus-Scanned: ClamAV 0.87.1/1644/Wed Aug 9 23:55:42 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: Niklas Sorensson Subject: Re: 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: Thu, 10 Aug 2006 18:05:58 -0000 On Sunday 16 July 2006 11:42, Niklas Sorensson wrote: > Hi, > > I've got a panic with a very recent current while running portupgrade. It was > triggered while running tcltest as part of building tcl. Backtrace/dmesg/kernel > config attached. Is this problem known? > > It's repeatable in case more information is necessary. > > /Niklas Can you still reproduce this (panic, lock not initialized) on latest -CURRENT? -- John Baldwin