On 2019-09-18 10:15, Masachika ISHIZUKA wrote:
Can you please use absolute paths to i915kms.ko anyway, just to test?
The same hang up occure with kld_list="/boot/modules/i915kms.ko"
in /etc/rc.conf.
Even after applying the patch I suggested?
Yes.
kld_list="/boot/modules/drm.ko /boot/modules/i915kms.ko"
will hang as well.
/boot/modules/{drm,i915kms}.ko is patched modules.
# /boot/kernel.r352239/{drm,i915kms}.ko is not patched.
Are you able to collect a kernel dump? If so, remove the kld_list
setting and set debug.debugger_on_panic=0 and dev.drm.skip_ddb=1. Then
manually kldload /boot/modules/i915kms.ko. If you are running an
INVARIANTS kernel you might be hitting an assertion failure; having the
vmcore would help us debug.
Thank you for mail.
As I'm busy now, I'll try to get kernel dump about 1 day after.
I'm very sorry.
The patch you suggested is work fine.
The reason why it didn't work was because the patch was applied
to the wrong file.
Now, drm-current-kmod is working fine on r352467 by your patch.
Hi!
I just updated the port with the fix I suggested earlier, hopefully it
works. It will take some time before it shows up as packages, but there
is no problems building drm-current-kmod from ports even if packages are
used for the rest of the system.
Regards
--
Niclas Zeising
_______________________________________________
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"
