Re: drm2, i915kms cause instant lock-up

From: Steve Kargl <sgk_at_troutmask.apl.washington.edu>
Date: Mon, 20 Feb 2017 21:26:58 -0800
On Tue, Feb 21, 2017 at 01:50:30AM +0100, Mateusz Guzik wrote:
> On Mon, Feb 20, 2017 at 04:43:40PM -0800, Steve Kargl wrote:
> > On Tue, Feb 21, 2017 at 12:58:07AM +0100, Mateusz Guzik wrote:
> > > On Mon, Feb 20, 2017 at 03:52:24PM -0800, Steve Kargl wrote:
> > > > With a kernel and world from r313943 sources (circa
> > > > Feb 19, 2017), kldload of either drm2.ko or i915kms.ko
> > > > will lock up the system.  There is no keyboard response,
> > > > screen output, or panic.  Just a locked up system.
> > > > 
> > > > A kernel from r313027 and its modules boots fine.
> > > > 'kldload drm2.ko' yields the following in /var/log/messages:
> > > > 
> > > 
> > > There were quite a few invasive changes in this timeframe. Can you
> > > please:
> > > 
> > > 1. switch to 313254 and ensure it works
> > > 2. apply https://people.freebsd.org/~mjg/patches/complete-locks.diff and
> > > check if it breaks
> > > 
> > > If it does not break, revert the patch and bisect the kernel please.
> > > Otherwise I'll devise smaller diffs to narrow this down.
> > > 
> > 
> > With 1. and 2. the system boots and I can kldload both drm2
> > and i915kms.  I revert the patch and start bisecting the kernel.
> > Thanks for the quick response.
> > 
> 
> Thanks for testing. Note you may encounter some turbulences along the
> road as there were fixups and fixups to fixups to the combined above
> patch.
> 

Well, the good news seems to be that r313254 and older are 'ok'.
So, something between r313943 and r313254 is triggering a the
problem.  I'm still bisecting, but it might take a day or two.

-- 
Steve
20161221 https://www.youtube.com/watch?v=IbCHE-hONow
Received on Tue Feb 21 2017 - 04:27:00 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:10 UTC