From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 15:38:47 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3FDF810656A6; Mon, 29 Sep 2008 15:38:47 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id D55508FC2A; Mon, 29 Sep 2008 15:38:46 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [IPv6:::1]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m8TFcMlh045541; Mon, 29 Sep 2008 11:38:39 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-stable@freebsd.org Date: Mon, 29 Sep 2008 11:15:36 -0400 User-Agent: KMail/1.9.7 References: <48DE7D83.2070205@comcast.com> In-Reply-To: <48DE7D83.2070205@comcast.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200809291115.36776.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [IPv6:::1]); Mon, 29 Sep 2008 11:38:39 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93.1/8353/Mon Sep 29 05:57:09 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=4.2 tests=AWL,BAYES_00,NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: "John L. Templer" , sos@freebsd.org Subject: Re: 7.1-PRELEASE sporadically panicking with fatal trap 12 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, 29 Sep 2008 15:38:47 -0000 On Saturday 27 September 2008 02:37:55 pm John L. Templer wrote: > I'm running 7.1-PRERELEASE, with /usr/src and /usr/ports last csup-ed > just a few days ago. After being up for about a day or so the system > will panic because of a page fault. I'm not completely sure, but it > seems that the system is more stable when gdm and gnome are disabled in > rc.conf. At least it stayed up for several days when I did that. > > I've run memtest several times, so I'm pretty confident it's not a > memory problem. Also the stack trace is always the same, so I'm > thinking it's not hardware related. > > I've attached a stack trace from kgdb, and the output from dmesg. I'd > appreciate any help you could give me with this. Generally when I see this panic (at this source line in mtx_lock() and with an offset of 0x188 or 0x18c), it is because the mutex is destroyed (mtx_lock == 6 (MTX_DESTROYED). In this case since you got it in a task, I'm guessing ata destroyed a structure w/o draining the task, so the task executed after the structure containing the mutex was destroyed. -- John Baldwin