From owner-freebsd-current@FreeBSD.ORG Fri Jun 17 06:34:07 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 664) id 365D816A41F; Fri, 17 Jun 2005 06:34:07 +0000 (GMT) Date: Fri, 17 Jun 2005 06:34:07 +0000 From: David O'Brien To: Eric Anderson Message-ID: <20050617063407.GA45182@hub.freebsd.org> References: <42AD8270.8060906@centtech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42AD8270.8060906@centtech.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 4.11-STABLE Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Cc: FreeBSD Current Subject: Re: _mtx_lock_sleep kernel crash.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Jun 2005 06:34:07 -0000 On Mon, Jun 13, 2005 at 07:56:16AM -0500, Eric Anderson wrote: > I'm getting this: > panic: _mtx_lock_sleep: recursed on non-recursive mutex system map @ > /usr/src/sys/vm/vm_kern.c:295 > > cpuid = 0 > KDB: enter: panic > [thread pid 0 tid 0 ] > Stopped at kdb_enter+0x2b: nop > > On bootup with my -current from a few days ago. Here's how I reproduce it: > With a GENERIC kernel, add any of these to your /boot/loader.conf: > vkbd_load="YES" > snd_pcm_load="YES" > snd_ich_load="YES" > > Removing 'smp' option from the kernel seems to fix it. I finally was able to get a traceback of my insta-reboots after marius' atkbd commit (2005-06-10 20:56:38 UTC) and it was exactly this same traceback. So it wasn't really 'smp' related, but a resource issue. alc increase of UMA_BOOT_PAGES fixes this panic. -- -- David (obrien@FreeBSD.org)