From owner-freebsd-stable@FreeBSD.ORG Sat Dec 25 21:30:29 2004 Return-Path: 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 D4A3B16A4CE for ; Sat, 25 Dec 2004 21:30:29 +0000 (GMT) Received: from mail10.syd.optusnet.com.au (mail10.syd.optusnet.com.au [211.29.132.191]) by mx1.FreeBSD.org (Postfix) with ESMTP id 185E843D1F for ; Sat, 25 Dec 2004 21:30:29 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) iBPLU67G012964 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 26 Dec 2004 08:30:07 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])iBPLU6xP012725; Sun, 26 Dec 2004 08:30:06 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)iBPLU5CG012724; Sun, 26 Dec 2004 08:30:05 +1100 (EST) (envelope-from pjeremy) Date: Sun, 26 Dec 2004 08:30:05 +1100 From: Peter Jeremy To: Benjamin Lutz Message-ID: <20041225213005.GB7189@cirb503493.alcatel.com.au> References: <200412230408.48770.benlutz@datacomm.ch> <20041223170124.GA89886@midgard.intranet> <20041224082137.GA7189@cirb503493.alcatel.com.au> <200412251036.07070.benlutz@datacomm.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200412251036.07070.benlutz@datacomm.ch> User-Agent: Mutt/1.4.2i cc: freebsd-stable@freebsd.org Subject: Re: slow system freeze - panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Dec 2004 21:30:29 -0000 On Sat, 2004-Dec-25 10:35:43 +0100, Benjamin Lutz wrote: >> Hmm. I can't find that string anywhere in the sources. Are you sure >> "rm.mutex_mtx" is correct? > >yes. It seems that it's inside the NVidia driver - which isn't in the source tree. That explains why I couldn't find it. I think this panic is a side-effect of enabling INVARIANTS and/or WITNESS. >> I suggest you read ddb(4) and the developer's handbook URL that I >> posted. > >I did. It doesn't mean much to me, really, since the kernel code is >totally unfamiliar to me. I don't really know what I'm looking for... >(ok, in this case, the mention of nvidia_* was kind of obvious :) ) Basically, if the system panics, run a 'trace'. If the system is frozen, the trace is less important. Since you're now back to the previous problem, can you try the same ddb commands when the system is frozen. It would probably be useful if you can force a crashdump (see the developer's handbook for details). Remember to set "dumpdev" to a suitable location (eg your swap partition) in your /etc/rc.conf. You can enable it without rebooting using "dumpon -v [dumpdevice]" (or /etc/rc.d/dumpon start). -- Season's Greetings Peter Jeremy