5.7-rc0: regression caused by drm tree, hangs while attempting to run X

From: Pavel Machek
Date: Fri Apr 03 2020 - 05:41:31 EST


Hi!

> > > > Hardware is thinkpad x220. I had this crash few days ago. And today I
> > > > have similar-looking one, with slightly newer kernel. (Will post
> > > > as a follow-up).
> >
> > As part of quest for working system, I tried 5.7-rc0, based on
> >
> > Merge: 50a5de895dbe b4d8ddf8356d
> > Author: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
> > Date: Wed Apr 1 18:18:18 2020 -0700
> >
> > It hangs in userspace, at a time when X should be starting, and I'm
> > looking at blinking cursor.
> >
> > 5.6-rcs worked, I'll test 5.6-final.
>
> 5.6-final works.
>
> Hmm...
>
> commit f365ab31efacb70bed1e821f7435626e0b2528a6
> Merge: 4646de87d325 59e7a8cc2dcf
> Author: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
> Date: Wed Apr 1 15:24:20 2020 -0700
>
> Merge tag 'drm-next-2020-04-01' of git://anongit.freedesktop.org/drm/drm
>
> Let me test 4646de87d32526ee87b46c2e0130413367fb5362...that one works.
>
> Ok, so obviously... I should
> test... f365ab31efacb70bed1e821f7435626e0b2528a6

f365ab31efacb70bed1e821f7435626e0b2528a6 is broken, and it is the
first broken merge. next-0403 is also broken.

Any ideas, besides the b-word?

Would c0ca be good commit for testing?

commit 700d6ab987f3b5e28b13b5993e5a9a975c5604e2
Merge: c0ca5437c509 2bdd4c28baff
Author: Dave Airlie <airlied@xxxxxxxxxx>
Date: Mon Mar 30 15:56:03 2020 +1000

Merge tag 'drm-intel-next-fixes-2020-03-27' of git://anongit.freedesktop.org
/drm/drm-intel into drm-next

Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Attachment: signature.asc
Description: PGP signature