Date: Tue, 17 Sep 2019 23:59:30 +0900 (JST) From: Masachika ISHIZUKA <ish@amail.plala.or.jp> To: freebsd-current@freebsd.org Subject: Re: hang up with r352239 and r352386 with i5-7500 Message-ID: <20190917.235930.528406816270492485.ish@amail.plala.or.jp> In-Reply-To: <20190917140912.GC35245@raichu> References: <746a0593-3dad-e3f5-53db-994c9a058233@freebsd.org> <20190917.072041.480458056274937279.ish@amail.plala.or.jp> <20190917140912.GC35245@raichu>
next in thread | previous in thread | raw e-mail | index | archive | help
>> >>> 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.
--
Masachika ISHIZUKA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190917.235930.528406816270492485.ish>