drm-next-kmod panic

[Jakob Alvermark]

On 08/31/17 19:09, Pete Wright wrote:
>
>
> On 08/31/2017 01:29, Jakob Alvermark wrote:
>> Hello,
>>
>> Excited about the new graphics/drm-next-kmod port I naturally wanted 
>> to try it.
>>
>> I have tested it on two machines. First, my daily driver, a ThinkPad 
>> Yoga 12 (Broadwell)
>>
>> It is an Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz
>>
>> Running -CURRENT r322999
>>
>> I installed drm-next-kmod-g20170829 and when kldloading 
>> /boot/modules/drm.ko and then /boot/modules/i915kms.ko
>>
>> The screen goes blank and system is unresposive (probably panics?), 
>> only a power cycle gets it running again.
>>
>
> if there is no core in /var/crash you can try adding this sysctl knob 
> which may increase the probability of capturing a core for analysis:
>
> dev.drm.skip_ddb=1
>
> one other question - are you able to ssh in to this system after it 
> has crashed?

There is no core in /var/crash, dev.drm.skip_ddb=1 does not make any 
difference.

An ssh session established before loading i915kms.ko hangs.

On the other machine (the Acer) I do get into the debugger, so I might 
be able to provide some useful information.

Thanks,

Jakob