From owner-freebsd-current@freebsd.org Tue Aug 7 05:09:48 2018 Return-Path: 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 47D7110741D3 for ; Tue, 7 Aug 2018 05:09:48 +0000 (UTC) (envelope-from eadler@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 E959B7D399 for ; Tue, 7 Aug 2018 05:09:47 +0000 (UTC) (envelope-from eadler@freebsd.org) Received: from mail-yb0-f170.google.com (mail-yb0-f170.google.com [209.85.213.170]) (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: eadler) by smtp.freebsd.org (Postfix) with ESMTPSA id AFB72106E4 for ; Tue, 7 Aug 2018 05:09:47 +0000 (UTC) (envelope-from eadler@freebsd.org) Received: by mail-yb0-f170.google.com with SMTP id n10-v6so1886497ybd.7 for ; Mon, 06 Aug 2018 22:09:47 -0700 (PDT) X-Gm-Message-State: AOUpUlHmpALH0NPpRt7ntulNlBaHey06Gcz9FNzU+UAZkINA0cpOh3AV AidVG8QUq/8I2APMqIz5oIERL/RBPM6SWhC79HAffA== X-Google-Smtp-Source: AAOMgpfu0CdubfQo2G8/ywkk8OS92gfdgugiLzZheKJqH1Pj2oiuCMfR/xva4MmmQSmMHA2K9N4KQuLiMuiZgOvaMvs= X-Received: by 2002:a25:7c1:: with SMTP id 184-v6mr9270852ybh.338.1533618587007; Mon, 06 Aug 2018 22:09:47 -0700 (PDT) MIME-Version: 1.0 References: <20180804083720.GJ6049@kib.kiev.ua> <20180805104341.GX6049@kib.kiev.ua> In-Reply-To: From: Eitan Adler Date: Mon, 6 Aug 2018 22:09:20 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: panic: mutex pmap not owned at ... efirt_machdep.c:255 To: Kyle Evans Cc: Kostik Belousov , freebsd-current Current 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Aug 2018 05:09:48 -0000 On Mon, 6 Aug 2018 at 11:27, Kyle Evans wrote: > > On Sun, Aug 5, 2018 at 5:43 AM, Konstantin Belousov 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. -- Eitan Adler Source, Ports, Doc committer Bugmeister, Ports Security teams