From owner-freebsd-ppc@FreeBSD.ORG  Sun Sep  8 05:27:31 2013
Return-Path: <owner-freebsd-ppc@FreeBSD.ORG>
Delivered-To: freebsd-ppc@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id 1C35ABFE;
 Sun,  8 Sep 2013 05:27:31 +0000 (UTC)
 (envelope-from chmeeedalf@gmail.com)
Received: from mail-bk0-x236.google.com (mail-bk0-x236.google.com
 [IPv6:2a00:1450:4008:c01::236])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 4F51629C2;
 Sun,  8 Sep 2013 05:27:30 +0000 (UTC)
Received: by mail-bk0-f54.google.com with SMTP id mz12so1859964bkb.13
 for <multiple recipients>; Sat, 07 Sep 2013 22:27:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:in-reply-to:references:date:message-id:subject
 :from:to:cc:content-type;
 bh=D3KC+DySUZG4LUipFrJnmcB8osJXertEcRKpjxP5zJI=;
 b=M0j3DlR3sXW2ESZdZjFruki2e8OYbojPsRGYjqD0g8bk0Vp40v2ve64igJMYKww02N
 YcmW4ZPtQW3fExCqBK57usVOfUySCi6vPs3HCi0ezzMl4PXcS7gsuT9jegjeWU1OHACq
 grScfObQ6gb3EFPaKLvrWmtRMKrCUITbhZHxxDiVQTrlNtbHUPd2v3PC/fgSamr1Yig9
 W2QbimeKK1xwSf03co1I331f3p0d9bu0SHexIFc+q3w9VghWLqKT1iY5iPDh/9mkXBGI
 hOdF0wrIUOUOw0Pf8ZDcHQZF9zC1cXZ8X9UGRkLdhCDvT8366piv9eRXwxdJ0ivdPrpu
 0k5Q==
MIME-Version: 1.0
X-Received: by 10.205.10.200 with SMTP id pb8mr9277687bkb.16.1378618048491;
 Sat, 07 Sep 2013 22:27:28 -0700 (PDT)
Sender: chmeeedalf@gmail.com
Received: by 10.205.13.199 with HTTP; Sat, 7 Sep 2013 22:27:28 -0700 (PDT)
In-Reply-To: <522BDFA5.8010803@freebsd.org>
References: <CAHSQbTCmr5ofovvAYXtrQP86JLsOinGePet57hT1437K03=GKA@mail.gmail.com>
 <522BDFA5.8010803@freebsd.org>
Date: Sat, 7 Sep 2013 22:27:28 -0700
X-Google-Sender-Auth: ZZC1iPFnlIpoRIaM1hLUD6aLaBI
Message-ID: <CAHSQbTC4ye9SEZWmiCh2voJRXCk2nPibjhzy-saLq2S6xaK0aA@mail.gmail.com>
Subject: Re: Kernel panic during page-out
From: Justin Hibbits <jhibbits@freebsd.org>
To: Peter Grehan <grehan@freebsd.org>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.14
Cc: FreeBSD PowerPC ML <freebsd-ppc@freebsd.org>
X-BeenThere: freebsd-ppc@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Porting FreeBSD to the PowerPC <freebsd-ppc.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ppc>,
 <mailto:freebsd-ppc-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ppc>
List-Post: <mailto:freebsd-ppc@freebsd.org>
List-Help: <mailto:freebsd-ppc-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ppc>,
 <mailto:freebsd-ppc-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 08 Sep 2013 05:27:31 -0000

Hi Peter


On Sat, Sep 7, 2013 at 7:23 PM, Peter Grehan <grehan@freebsd.org> wrote:

> 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.
>
>
If this is the correct fix, it should be pushed in through re@, and go into
10.  Is this correct?  I haven't checked the full locking on it.

- Justin