https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239351

--- Comment #3 from Evilham <cont...@evilham.com> ---
Created attachment 206031
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=206031&action=edit
coredump_nowg_onboot_net_up

Actually, I meant to update this bug report yesterday but didn't manage to.

I have seen this kernel panic again without WireGuard, though it does happen
way more often with it and I can produce the panic with it but can't reliably
(ehem) panic the system without it.

It actually happened once while booting, but after network was initialised, so
network could still be at fault.

Now I'm quite inclined to believe that this is related to #231760 and booting
with hw.pci.mcfg=0 (the only way to boot atm); but my knowledge of FreeBSD's
inners is not up to the task to fully pin-point it.

I have two more dumps, please note that even if drm-kmod is present and
somewhat verbose, it was not present on the system at the time of the first
dump; so it'd be misleading to think it's caused by it.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Reply via email to