From owner-freebsd-stable@FreeBSD.ORG Fri Mar 11 18:59:09 2005 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 6495416A4CE; Fri, 11 Mar 2005 18:59:09 +0000 (GMT) Received: from mail-gw1.york.ac.uk (mail-gw1.york.ac.uk [144.32.128.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id C5B3743D49; Fri, 11 Mar 2005 18:59:08 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from ury.york.ac.uk (ury.york.ac.uk [144.32.108.81]) by mail-gw1.york.ac.uk (8.12.10/8.12.10) with ESMTP id j2BIx3ML027388; Fri, 11 Mar 2005 18:59:03 GMT Received: from ury.york.ac.uk (localhost.york.ac.uk [127.0.0.1]) by ury.york.ac.uk (8.12.9p2/8.12.9) with ESMTP id j2BIx2p8063375; Fri, 11 Mar 2005 18:59:02 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from localhost (gavin@localhost)j2BIx2er063372; Fri, 11 Mar 2005 18:59:02 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) X-Authentication-Warning: ury.york.ac.uk: gavin owned process doing -bs Date: Fri, 11 Mar 2005 18:59:02 +0000 (GMT) From: Gavin Atkinson X-X-Sender: gavin@ury.york.ac.uk To: stable@freebsd.org, alc@freebsd.org Message-ID: <20050311184658.Q63048@ury.york.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin.atkinson@ury.york.ac.uk Subject: panic: mutex vm object not owned 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: Fri, 11 Mar 2005 18:59:09 -0000 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. Thanks, Gavin