[Bug 241697] i915kms: Kernel panic loading module on custom kernel w/ MAXCPU < 256 (Invalid CPU in callout 256)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241697 Mark Linimon changed: What|Removed |Added Flags|mfc-stable12?, | |mfc-stable11? | CC|hsela...@freebsd.org| --- Comment #7 from Mark Linimon --- ^Triage: clear stale flags. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 241697] i915kms: Kernel panic loading module on custom kernel w/ MAXCPU < 256 (Invalid CPU in callout 256)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241697 Mark Linimon changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu ||gzilla/show_bug.cgi?id=2792 ||24 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 241697] i915kms: Kernel panic loading module on custom kernel w/ MAXCPU < 256 (Invalid CPU in callout 256)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241697 Ed Maste changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu ||gzilla/show_bug.cgi?id=2695 ||72 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 241697] i915kms: Kernel panic loading module on custom kernel w/ MAXCPU < 256 (Invalid CPU in callout 256)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241697 --- Comment #6 from Hans Petter Selasky --- At work we simply dump: sysctl kern.conftxt and run configure on that to get all the options correct. --HPS -- You are receiving this mail because: You are the assignee for the bug.
[Bug 241697] i915kms: Kernel panic loading module on custom kernel w/ MAXCPU < 256 (Invalid CPU in callout 256)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241697 --- Comment #5 from Ed Maste --- There is a broad issue with out-of-tree kernel modules not picking up kernel configuration options; we need to develop a holistic solution for this. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 241697] i915kms: Kernel panic loading module on custom kernel w/ MAXCPU < 256 (Invalid CPU in callout 256)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241697 Andre Albsmeier changed: What|Removed |Added CC||m...@fbsd2.e4m.org --- Comment #4 from Andre Albsmeier --- FWIW, it took me half a day to realise I was bitten by the same thing on 12.2-STABLE as of today. What works is to compile drm-fbsd12.0-kmod with the same value for MAXCPU as the kernel. A smaller value for the kmod does not help either. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 241697] i915kms: Kernel panic loading module on custom kernel w/ MAXCPU < 256 (Invalid CPU in callout 256)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241697 Mark Linimon changed: What|Removed |Added Keywords||i915 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 241697] i915kms: Kernel panic loading module on custom kernel w/ MAXCPU < 256 (Invalid CPU in callout 256)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241697 --- Comment #3 from Hans Petter Selasky --- I suspect the drm-kms modules need default values for some kernel parameters, because when building these we don't use the config file used by the kernel. This might be possible to fix, by generating the needed kernel options from the current kernel config file. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 241697] i915kms: Kernel panic loading module on custom kernel w/ MAXCPU < 256 (Invalid CPU in callout 256)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241697 --- Comment #2 from Joshua Kinard --- 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. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 241697] i915kms: Kernel panic loading module on custom kernel w/ MAXCPU < 256 (Invalid CPU in callout 256)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241697 Joshua Kinard changed: What|Removed |Added Summary|i915kms: Kernel panic |i915kms: Kernel panic |loading module on ustom |loading module on custom |kernel w/ MAXCPU < 256 |kernel w/ MAXCPU < 256 |(Invalid CPU in callout |(Invalid CPU in callout |256)|256) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
