mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: kernel list <linux-kernel@vger.kernel.org>,
	jani.nikula@linux.intel.com, joonas.lahtinen@linux.intel.com,
	rodrigo.vivi@intel.com, intel-gfx@lists.freedesktop.org,
	airlied@redhat.com
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de, hpa@zytor.com
Subject: 5.7-rc0: regression caused by drm tree, hangs while attempting to run X
Date: Fri, 3 Apr 2020 11:41:10 +0200	[thread overview]
Message-ID: <20200403092634.GA3610@duo.ucw.cz> (raw)
In-Reply-To: <20200403091430.GA3845@duo.ucw.cz>

[-- Attachment #1: Type: text/plain, Size: 1691 bytes --]

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@linux-foundation.org>
> > 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@linux-foundation.org>
> 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@redhat.com>
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 #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  parent reply	other threads:[~2020-04-03  9:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-02 21:32 5.6-rc6: Xorg hangs Pavel Machek
2020-04-02 21:35 ` 5.6-rc7: Xorg hangs, too Pavel Machek
2020-04-02 21:55   ` Chris Wilson
2020-04-03  7:37   ` 5.7-rc0: hangs while attempting to run X Pavel Machek
2020-04-03  9:14     ` Pavel Machek
2020-04-03  9:16       ` [Intel-gfx] " Chris Wilson
2020-04-03  9:41       ` Pavel Machek [this message]
2020-04-03 10:29         ` 5.7-rc0: regression caused by drm tree, " Pavel Machek
2020-04-03 12:30           ` [bisected] " Pavel Machek
2020-04-03 13:00             ` [bisected] Re: 7dc8f11437: regression in 5.7-rc0, " Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200403092634.GA3610@duo.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=airlied@redhat.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®