From owner-freebsd-stable@FreeBSD.ORG Sun Mar 13 17:20:53 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 E9FE516A4CE; Sun, 13 Mar 2005 17:20:53 +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 1939443D1F; Sun, 13 Mar 2005 17:20:53 +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 j2DHKmML004287; Sun, 13 Mar 2005 17:20:48 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 j2DHKmp8010511; Sun, 13 Mar 2005 17:20:48 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from localhost (gavin@localhost)j2DHKm9w010508; Sun, 13 Mar 2005 17:20:48 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) X-Authentication-Warning: ury.york.ac.uk: gavin owned process doing -bs Date: Sun, 13 Mar 2005 17:20:47 +0000 (GMT) From: Gavin Atkinson X-X-Sender: gavin@ury.york.ac.uk To: Alan Cox In-Reply-To: <20050311192009.GK28845@cs.rice.edu> Message-ID: <20050313172004.A10449@ury.york.ac.uk> References: <20050311184658.Q63048@ury.york.ac.uk> <20050311192009.GK28845@cs.rice.edu> 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 cc: alc@freebsd.org cc: stable@freebsd.org Subject: Re: 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: Sun, 13 Mar 2005 17:20:54 -0000 On Fri, 11 Mar 2005, Alan Cox wrote: > I'm pretty sure that I understand the cause. Please apply and test > the attached patch. [snip patch-agp] Sorry for the delay in getting back yo you, this patch does indeed fix the problem. Thanks! Gavin