To close the loop on this, the root cause ended up being a mistake on
my end. This system had a rather convoluted boot process, and as a
result of that was loading a nullfs.ko built for a months-old kernel.
This setup accidentally worked for some time, but I guess some recent
change to struct
Sorry for the late reply. Panicking this system is a bit painful, but
I found some time to do it today.
Strangely, it's actually cred that is NULL, not cred->cr_prison:
(kgdb) p cred
$7 = (struct ucred *) 0x0
(kgdb) disassemble
Dump of assembler code for function prison_allow:
On Sun, Feb 11, 2018 at 11:50:43PM -0500, Ryan Stone wrote:
> I'm getting a persistent panic on boot in prison_allow(). The first
> case that I hit is this:
>
> Fatal trap 12: page fault while in kernel mode
> cpuid = 10; apic id = 22
> fault virtual address = 0x30
> fault code =
I'm getting a persistent panic on boot in prison_allow(). The first
case that I hit is this:
Fatal trap 12: page fault while in kernel mode
cpuid = 10; apic id = 22
fault virtual address = 0x30
fault code = supervisor read data, page not present
instruction pointer =
