From owner-freebsd-stable@FreeBSD.ORG Mon Aug 14 14:17:18 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A4E5416A5B7 for ; Mon, 14 Aug 2006 14:17:18 +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 DBDAE43D5C for ; Mon, 14 Aug 2006 14:17:09 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id k7EEGn9m013497; Mon, 14 Aug 2006 10:17:03 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-stable@freebsd.org Date: Mon, 14 Aug 2006 09:44:00 -0400 User-Agent: KMail/1.9.1 References: <44DED670.9050601@wfeet.za.net> In-Reply-To: <44DED670.9050601@wfeet.za.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200608140944.01232.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [192.168.0.1]); Mon, 14 Aug 2006 10:17:08 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/1659/Mon Aug 14 04:44:22 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.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Peter van Heusden Subject: Re: Unexplained kernel panic on 5-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Aug 2006 14:17:18 -0000 On Sunday 13 August 2006 03:36, Peter van Heusden wrote: > Hi everyone > > Almost every day, some time around midnight, my FreeBSD 5-STABLE kernel > panics. I've attached the output of a kgdb session of the saved core > file - is there any further info that would be useful to debugging? I've > got no idea where to start looking for a solution to this problem, so > please help!! A thread is sleeping while holding a mutex. > (kgdb) list *0xc066dfc3 > 0xc066dfc3 is in propagate_priority > (/usr/src/sys/kern/subr_turnstile.c:245). > 240 /* > 241 * Pick up the lock that td is blocked on. > 242 */ > 243 ts = td->td_blocked; > 244 MPASS(ts != NULL); > 245 tc = TC_LOOKUP(ts->ts_lockobj); > 246 mtx_lock_spin(&tc->tc_lock); > 247 > 248 /* > 249 * This thread may not be blocked on this > turnstile anymore > (kgdb) backtrace > #19 0xc066dfc3 in propagate_priority (td=0xc1e22c00) at > /usr/src/sys/kern/subr_turnstile.c:243 Do the following in 'kgdb': frame 19 p td->td_proc->p_pid (this will output the 'pid' of the misbehaving thread) proc ( is the pid from the previous command, this switches you to that thread) backtrace That backtrace will then show you which thread slept while holding a mutex. -- John Baldwin