Date: Fri, 1 Sep 2017 10:52:38 +0200 From: Jakob Alvermark <jakob@alvermark.net> To: Pete Wright <pete@nomadlogic.org>, x11@freebsd.org Subject: Re: drm-next-kmod panic Message-ID: <bb8f3409-d013-ed55-11cd-82dfe9c0b411@alvermark.net> In-Reply-To: <69456e0e-8b97-51fd-8a65-023ecb093cfd@nomadlogic.org> References: <cf88383f-5f7a-9904-996e-b26d1d49bc65@alvermark.net> <69456e0e-8b97-51fd-8a65-023ecb093cfd@nomadlogic.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bb8f3409-d013-ed55-11cd-82dfe9c0b411>