From owner-freebsd-current@freebsd.org Wed Aug 29 16:31:10 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 CBB8C108E808 for ; Wed, 29 Aug 2018 16:31:10 +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 33B77739B9; Wed, 29 Aug 2018 16:31:10 +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 w7TGUx6V094551 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 29 Aug 2018 19:31:02 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w7TGUx6V094551 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w7TGUxf7094550; Wed, 29 Aug 2018 19:30:59 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 29 Aug 2018 19:30:59 +0300 From: Konstantin Belousov To: Yuri Pankov Cc: Kyle Evans , FreeBSD Current Subject: Re: r336921 broke booting on MBP 2017, EFIRT related Message-ID: <20180829163059.GI2340@kib.kiev.ua> References: <499f05f4-4fab-9b31-5d37-83ecb554013c@yuripv.net> <20180829102727.GD2340@kib.kiev.ua> <20180829141914.GG2340@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Aug 2018 16:31:11 -0000 On Wed, Aug 29, 2018 at 07:17:07PM +0300, Yuri Pankov wrote: > Konstantin Belousov wrote: > > On Wed, Aug 29, 2018 at 09:12:37AM -0500, Kyle Evans wrote: > >> I guess this patch might do it: > >> https://people.freebsd.org/~kevans/efi-bootmap.diff > >> > >> Linux commit messages depict a tale in which they used to also only > >> map RUNTIME entries, but they were effectively forced to back down on > >> that because of buggy firmware that does exactly what you've described > >> and they later reintroduced the restrictive mapping for i386-only > >> where they'd not found such bugs. > > > > Orthogonal to the loader patch, please try the following. Even better, > > try this with the stock loader. > > > > You need to remove efirt from the kernel config for now, instead load > > efirt.ko, perhaps after the system booted into single user. I am interested > > if the panic goes away. You should see some interesting message from > > kernel about EFI realtime clock. > > > > If you have any binary modules like nvidia or vbox, do not load them > > with the patched kernel. > > Done, getting exactly the same fault without any new messages printed > (made sure I'm using the updated efirt using `nm | grep efirt_fault`). Can you show me exact fault messages ?