From owner-freebsd-current@freebsd.org  Sat Aug  4 04:27:25 2018
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id E76CA105D79D
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Sat,  4 Aug 2018 04:27:24 +0000 (UTC)
 (envelope-from kevans@freebsd.org)
Received: from smtp.freebsd.org (smtp.freebsd.org
 [IPv6:2610:1c1:1:606c::24b:4])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "smtp.freebsd.org",
 Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 9BAC684466;
 Sat,  4 Aug 2018 04:27:24 +0000 (UTC)
 (envelope-from kevans@freebsd.org)
Received: from mail-lj1-f173.google.com (mail-lj1-f173.google.com
 [209.85.208.173])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G3" (verified OK))
 (Authenticated sender: kevans)
 by smtp.freebsd.org (Postfix) with ESMTPSA id 3A6E814D34;
 Sat,  4 Aug 2018 04:27:24 +0000 (UTC)
 (envelope-from kevans@freebsd.org)
Received: by mail-lj1-f173.google.com with SMTP id p10-v6so6520409ljg.2;
 Fri, 03 Aug 2018 21:27:24 -0700 (PDT)
X-Gm-Message-State: AOUpUlGP0n6GtCsbsePVe+p1ZLvwCE+HkjzWTMkLWVTpEZlm2SOlpkTY
 kR/47Q3cTcQ29+2uCI2zm/1BclhHfyphR5SH7uA=
X-Google-Smtp-Source: AAOMgpfLNxhzbNbATsCEWX1h+meKrvZKG+mM6AQfNbC47+xP7C8M8Iou/gJtF9htoHFOKHB3kQ9L0GmHjZRcWKPAEhg=
X-Received: by 2002:a2e:1004:: with SMTP id j4-v6mr7453302lje.2.1533356842820; 
 Fri, 03 Aug 2018 21:27:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a2e:5742:0:0:0:0:0 with HTTP;
 Fri, 3 Aug 2018 21:27:02 -0700 (PDT)
In-Reply-To: <CAF6rxg=4OnHEJa1OnJerMeEKD66nZg3j-H-XZ-9YAA1TE_NoDQ@mail.gmail.com>
References: <CAF6rxg=4OnHEJa1OnJerMeEKD66nZg3j-H-XZ-9YAA1TE_NoDQ@mail.gmail.com>
From: Kyle Evans <kevans@freebsd.org>
Date: Fri, 3 Aug 2018 23:27:02 -0500
X-Gmail-Original-Message-ID: <CACNAnaFv9Gj+M2Gb8FbwY5q56dnTR6OgjZ5qth9gjr8LreHeow@mail.gmail.com>
Message-ID: <CACNAnaFv9Gj+M2Gb8FbwY5q56dnTR6OgjZ5qth9gjr8LreHeow@mail.gmail.com>
Subject: Re: panic: mutex pmap not owned at ... efirt_machdep.c:255
To: Eitan Adler <lists@eitanadler.com>
Cc: Konstantin Belousov <kib@freebsd.org>,
 freebsd-current Current <freebsd-current@freebsd.org>
Content-Type: text/plain; charset="UTF-8"
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Aug 2018 04:27:25 -0000

On Fri, Aug 3, 2018 at 10:10 PM, Eitan Adler <lists@eitanadler.com> wrote:
> Hi all,
>
> After installing the latest current kernel I get the following panic:
>
> panic: mutex pmap not owned at ... efirt_machdep.c:255
> cpuid =3
> time = 1
> ...
> mtx_assert()
> efi_arch_enter()
> efirt_modevents()
> module_register_init()
> mi_startup()
> btext()
>

This seems odd- pmap lock is acquired at [1], then asserted shortly
later at [2]... I avoid some of this stuff as well as I can, but is it
actually possible for PCPU_GET(...) acquired curpmap to not match
curthread->td_proc->p_vmspace->vm_pmap in this context?

[1] https://svnweb.freebsd.org/base/head/sys/dev/efidev/efirt.c?view=markup#l260
[2] https://svnweb.freebsd.org/base/head/sys/amd64/amd64/efirt_machdep.c?view=markup#l254