From owner-freebsd-ppc@FreeBSD.ORG Sun Sep 8 02:23:44 2013 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A73958CD; Sun, 8 Sep 2013 02:23:44 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 6777B21DD; Sun, 8 Sep 2013 02:23:44 +0000 (UTC) Received: from dommail.onthenet.com.au (dommail.OntheNet.com.au [203.13.70.57]) by alto.onthenet.com.au (Postfix) with ESMTPS id 5483D11BB0; Sun, 8 Sep 2013 12:23:41 +1000 (EST) Received: from Peters-MacBook-Pro.local (c-67-161-27-37.hsd1.ca.comcast.net [67.161.27.37]) by dommail.onthenet.com.au (MOS 4.2.4-GA) with ESMTP id BOM61519 (AUTH peterg@ptree32.com.au); Sun, 8 Sep 2013 12:23:40 +1000 Message-ID: <522BDFA5.8010803@freebsd.org> Date: Sat, 07 Sep 2013 19:23:33 -0700 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Justin Hibbits Subject: Re: Kernel panic during page-out References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD PowerPC ML X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Sep 2013 02:23:44 -0000 Hi Justin, > I'm seeing a kernel panic on my G5, I think when it tries to page out to > swap, with the message: > > Lock vm object not exclusively locked @ .../aim/mmu_oea64.c:1529 > backtrace: > .kdb_backtrace+0x5c > .vpanic+0x13c > .panic+0x38 > .__rw_assert+0x184 > .moea64_is_modified+0x54 > .moea64_remove_all+0x78 > .vm_pageout_object_deactivate_pages+0x2e4 > .vm_daemon+0x358 > .fork_exit+0xdc > .fork_trampoline+0x10 > > This machine has 12GiB RAM, running r254922. This is the same panic I saw on the g5 imac when I only had 512MB of RAM - 'twas much too easy to reproduce. The fix is moea64_is_modified ... - VM_OBJECT_ASSERT_WLOCKED(m->object); + VM_OBJECT_ASSERT_LOCKED(m->object); This is consistent with locking higher up in the call chain. Apologies for not submitting that when I found it (and discussed it with Nathan). later, Peter.