On Fri, Aug 3, 2018 at 10:10 PM, Eitan Adler <li...@eitanadler.com> wrote: > Hi all, > > After installing the latest current kernel I get the following panic: > > panic: mutex pmap not owned at ... efirt_machdep.c:255 > cpuid =3 > time = 1 > ... > mtx_assert() > efi_arch_enter() > efirt_modevents() > module_register_init() > mi_startup() > btext() >
This seems odd- pmap lock is acquired at [1], then asserted shortly later at [2]... I avoid some of this stuff as well as I can, but is it actually possible for PCPU_GET(...) acquired curpmap to not match curthread->td_proc->p_vmspace->vm_pmap in this context? [1] https://svnweb.freebsd.org/base/head/sys/dev/efidev/efirt.c?view=markup#l260 [2] https://svnweb.freebsd.org/base/head/sys/amd64/amd64/efirt_machdep.c?view=markup#l254 _______________________________________________ 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"
