Date: Fri, 17 Jun 2005 06:34:07 +0000 From: David O'Brien <obrien@FreeBSD.ORG> To: Eric Anderson <anderson@centtech.com> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: _mtx_lock_sleep kernel crash.. Message-ID: <20050617063407.GA45182@hub.freebsd.org> In-Reply-To: <42AD8270.8060906@centtech.com> References: <42AD8270.8060906@centtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050617063407.GA45182>