From: Linus Torvalds <torvalds@linux-foundation.org>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Dave Airlie <airlied@linux.ie>,
Chris Wilson <chris@chris-wilson.co.uk>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Paulo Zanoni <paulo.r.zanoni@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
DRI mailing list <dri-devel@lists.freedesktop.org>,
"Beauchesne, Gwenole" <gwenole.beauchesne@intel.com>,
Sean V Kelley <sean.v.kelley@intel.com>
Subject: Re: [git pull] drm tree for 3.12-rc1
Date: Thu, 5 Sep 2013 17:56:44 -0700 [thread overview]
Message-ID: <CA+55aFyy_pKt07MgB9PzKg-LLKj1PH0q1t8y2Zu42srCyw-W4w@mail.gmail.com> (raw)
In-Reply-To: <CA+55aFwOme_LD6qqmzdEQ6AXiK8My7PWU1y5VV2tLgkO1HU7xg@mail.gmail.com>
On Thu, Sep 5, 2013 at 4:19 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> So I've decided I'm going to try to bisect this after all. I've done
> enough pulls for today anyway, I guess. Let's see if I can bisect it
> by just trying to boot many times each try.
Ok, it's not the recent drm pull at all. I can't find a good kernel in
the bunch - they all fail eventually.
It may have been going in for as long as I've had this Haswell
machine, and I was just lucky (and not rebooting a lot until in the
merge window - and 4/5 boots work fine).
It may also be user-space and have come in with the mesa update I got
through yum yesterday. So there might be multiple reasons why I saw it
today after the drm pull for the first time.
The black screen - when it happens - happens after the fedora logo has
flashed, and gdm is supposed to start up. I tried reproducing it by
logging out and back in again (to restart X), but that doesn't do it.
Maybe timing-related with boot or just demand-loading of binaries the
first time, whatever.. Or mayby it's something special that gdm does
at startup?
Linus
next prev parent reply other threads:[~2013-09-06 0:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 10:41 [git pull] drm tree for 3.12-rc1 Dave Airlie
2013-09-05 19:18 ` Linus Torvalds
2013-09-05 22:02 ` Dave Airlie
2013-09-05 22:32 ` Jesse Barnes
2013-09-05 22:51 ` Linus Torvalds
2013-09-05 23:01 ` Linus Torvalds
2013-09-05 23:19 ` Linus Torvalds
2013-09-06 0:56 ` Linus Torvalds [this message]
2013-09-10 8:16 ` Benjamin Tissoires
2013-09-10 6:25 ` Sean V Kelley
2013-09-10 15:49 ` Linus Torvalds
2013-09-10 16:06 ` Mike Lothian
2013-09-10 20:50 ` Sean V Kelley
2013-09-10 23:18 ` Sean V Kelley
2013-09-10 23:23 ` Dave Airlie
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=CA+55aFyy_pKt07MgB9PzKg-LLKj1PH0q1t8y2Zu42srCyw-W4w@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=airlied@linux.ie \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gwenole.beauchesne@intel.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulo.r.zanoni@intel.com \
--cc=sean.v.kelley@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).