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 ? _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
