[Bug 241697] i915kms: Kernel panic loading module on custom kernel w/ MAXCPU < 256 (Invalid CPU in callout 256)
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Mon Nov 4 04:44:59 UTC 2019
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241697
--- Comment #2 from Joshua Kinard <kumba at gentoo.org> ---
I believe it is. When I initially tested on 12.1-RC2, I followed this mailing
list thread here, thinking this thread highlighted my problem:
https://www.mail-archive.com/freebsd-stable@freebsd.org/msg138326.html
So I built drm-fbsd12.0-kmod-4.16.g20191024 via ports as a package (as well as
gpu-firmware-kmod-g20191015), then installed that package to get it working on
12.1-RC2 (needed because I'm building a Kodi box and need EVDEV for working
bluetooth mouse/keyboard via a mini keyboard device). Before I rebuilt my
kernel w/o MAXCPU, it'd crash virtually the exact same way. Just a slight
difference in the stack trace where after the call to
"intel_dp_init_connector", there's a call to "intel_edp_panel_vdd_sanitize",
then the call to "linux_queue_delayed_work_on", which goes on to trigger the
panic.
After rebuilding the 12.1-RC2 kernel and commenting out MAXCPU, it works fine
w/ i915kms.ko from the rebuilt drm-fbsd12.0-kmod package. Even got Kodi up and
working (just working on sound output now).
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list