From owner-freebsd-current@freebsd.org  Tue Aug  7 17:30:00 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 BAA541065810
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Tue,  7 Aug 2018 17:30:00 +0000 (UTC)
 (envelope-from kostikbel@gmail.com)
Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 1F94E79130;
 Tue,  7 Aug 2018 17:30:00 +0000 (UTC)
 (envelope-from kostikbel@gmail.com)
Received: from tom.home (kib@localhost [127.0.0.1])
 by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id w77HTnQC072572
 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
 Tue, 7 Aug 2018 20:29:52 +0300 (EEST)
 (envelope-from kostikbel@gmail.com)
DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w77HTnQC072572
Received: (from kostik@localhost)
 by tom.home (8.15.2/8.15.2/Submit) id w77HTn9u072571;
 Tue, 7 Aug 2018 20:29:49 +0300 (EEST)
 (envelope-from kostikbel@gmail.com)
X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com
 using -f
Date: Tue, 7 Aug 2018 20:29:49 +0300
From: Konstantin Belousov <kostikbel@gmail.com>
To: Kyle Evans <kevans@freebsd.org>
Cc: Eitan Adler <eadler@freebsd.org>,
 freebsd-current Current <freebsd-current@freebsd.org>
Subject: Re: panic: mutex pmap not owned at ... efirt_machdep.c:255
Message-ID: <20180807172949.GD1884@kib.kiev.ua>
References: <CAF6rxg=4OnHEJa1OnJerMeEKD66nZg3j-H-XZ-9YAA1TE_NoDQ@mail.gmail.com>
 <CACNAnaFv9Gj+M2Gb8FbwY5q56dnTR6OgjZ5qth9gjr8LreHeow@mail.gmail.com>
 <20180804083720.GJ6049@kib.kiev.ua>
 <CACNAnaF1anCXzjivX0jqur+omy_+6Xv4D+DttzLQY9g6qaxYbw@mail.gmail.com>
 <20180805104341.GX6049@kib.kiev.ua>
 <CACNAnaHAoVE57aw7UUPO=psOXz0nnUaCSXtJSFhpBo+Bhp_qnw@mail.gmail.com>
 <CAF6rxgmGLbLnMacc_Bb7_RKEAb6vazBjXwcECzsuVqJWKMrBvQ@mail.gmail.com>
 <CACNAnaHdgbe+VDZC-gV-oU7=DgNZhEfg1Uanrs0Lh4MgkLXsOQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CACNAnaHdgbe+VDZC-gV-oU7=DgNZhEfg1Uanrs0Lh4MgkLXsOQ@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00,
 DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no
 autolearn_force=no version=3.4.1
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home
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: Tue, 07 Aug 2018 17:30:00 -0000

On Tue, Aug 07, 2018 at 11:50:44AM -0500, Kyle Evans wrote:
> On Tue, Aug 7, 2018 at 12:09 AM, Eitan Adler <eadler@freebsd.org> wrote:
> > On Mon, 6 Aug 2018 at 11:27, Kyle Evans <kevans@freebsd.org> wrote:
> >>
> >> On Sun, Aug 5, 2018 at 5:43 AM, Konstantin Belousov <kostikbel@gmail.com> wrote:
> >> > On Sat, Aug 04, 2018 at 09:46:39PM -0500, Kyle Evans wrote:
> >> >>
> >> >> He now gets a little further, but ends up with the same panic due to
> >> >> efirtc_probe trying to get time to verify the rtc's actually
> >> >> implemented. What kind of approach must we take to ensure curcpu is
> >> >> synced?
> >> >
> >> > It does not panic for me, when I load efirt.ko from the loader prompt.
> >> > Anyway, try this
> >>
> >> Right, I also don't get a panic on any of my machines from this.
> >> Hopefully he'll have a chance to try this soon.
> >
> > This change has no impact: it still panics in the same way as without the patch.
> >
> 
> That seems indicative of a bigger problem, since we use proc0
> throughout all these bits so we should still be dealing with the same
> pmap that got passed to pmap_pinit0 when we grab
> curthread->td_proc->p_vmspace->vm_pmap.

Can you confirm that you get the early efi_enter() call from rtc code,
when you preload the module or compile it into the kernel ?