Date: Wed, 29 Aug 2018 19:17:07 +0300 From: Yuri Pankov <yuripv@yuripv.net> To: Konstantin Belousov <kostikbel@gmail.com>, Kyle Evans <kevans@freebsd.org> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: r336921 broke booting on MBP 2017, EFIRT related Message-ID: <ef9482c4-9bee-3e05-2b6e-46462a424c25@yuripv.net> In-Reply-To: <20180829141914.GG2340@kib.kiev.ua> References: <499f05f4-4fab-9b31-5d37-83ecb554013c@yuripv.net> <20180829102727.GD2340@kib.kiev.ua> <b767f852-6e1a-1c02-11eb-5548aea26afe@yuripv.net> <a8611843-8fbc-c5d2-2246-1853fa4ca1b7@yuripv.net> <CACNAnaFvSGLs9XwQYZ%2BGVfmXwDD-Bh%2BgVvnkmOipKUHNOGS2DA@mail.gmail.com> <20180829141914.GG2340@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
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`).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ef9482c4-9bee-3e05-2b6e-46462a424c25>