Date: Fri, 11 Mar 2005 13:04:17 -0600 From: Alan Cox <alc@cs.rice.edu> To: Gavin Atkinson <gavin.atkinson@ury.york.ac.uk> Cc: stable@freebsd.org Subject: Re: panic: mutex vm object not owned Message-ID: <20050311190417.GJ28845@cs.rice.edu> In-Reply-To: <20050311184658.Q63048@ury.york.ac.uk> References: <20050311184658.Q63048@ury.york.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Mar 11, 2005 at 06:59:02PM +0000, Gavin Atkinson wrote: > > Hi, > > I'm tracking RELENG_5 and since my last update I can no longer start X > without getting the following panic: > > panic: mutex vm object not owned at /usr/src/sys/vm/vm_page.c:334 > cpuid = 0 > KDB: enter: panic > [ thread pid 2762 tid 100116 ] > stopped at kdb_enter+0x2b: nop > > At which point the machine hangs solid (note this is over a serial console > - it is after X has claimed the display). > > I've done a binary chop to find where the bug was introduced, and it > started at some point between 19:00 on 2005/02/25 and 00:00 on 2005/02/26. > The MFC to vm_page.c which added the assertion I'm tripping up on happened > between those two points: > $FreeBSD: src/sys/vm/vm_page.c,v 1.290.2.4 2005/02/25 23:38:22 alc Exp $ > > vm_page.c:334 seems to correspond to the line > VM_OBJECT_LOCK_ASSERT(m->object, MA_OWNED); > within vm_page_wakeup() > > Any suggestions? I'll try to coerce it into generating a backtrace but > given the machine wedges before even giving the DDB prompt I'm not sure > I'll be able to. > Are you using an Nvidia driver? Regards, Alan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050311190417.GJ28845>