From: Daniel Vetter <daniel@ffwll.ch>
To: linux-kernel@vger.kernel.org
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
airlied@linux.ie, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Subject: Re: [Regression] 3.18 black screen after boot (bisected)
Date: Mon, 15 Dec 2014 08:57:34 +0100 [thread overview]
Message-ID: <20141215075734.GR27182@phenom.ffwll.local> (raw)
In-Reply-To: <20141214115831.GA1634@fritha.org>
On Sun, Dec 14, 2014 at 12:58:31PM +0100, Heinz Diehl wrote:
> Hi,
>
> since kernel 3.18 I'm no longer able to run X on my machine. While
> 3.17.6 is fine, 3.18 leaves me with a black screen when starting
> X. Booting into runlevel 1/3 is fine.
>
> I did a "git bisect", and the offending commit is this one:
>
> [root@kiera linux-git]# git bisect bad
> 83f45fc360c8e16a330474860ebda872d1384c8c is the first bad commit
> commit 83f45fc360c8e16a330474860ebda872d1384c8c
> Author: Daniel Vetter <daniel.vetter@ffwll.ch>
> Date: Wed Aug 6 09:10:18 2014 +0200
>
> drm: Don't grab an fb reference for the idr
>
> [....]
>
> I double-checked, and 3.18 is fine with this commit reverted.
>
> My machine is an Asus U45JC laptop, and the CPU is an Intel i450M
> (Ironlake). Please contact me if I can help in any way (I'm subscribed
> to lkml, but not to other X or kernel related lists).
Can you please boot with drm.debug=0xf on both good and bad kernels and
then grab dmesg from each?
To make sure we don't forget this please file the above summary plus dmesg
files as a new bug against dri -> drm(intel) on bugs.freedesktop.org.
Please add "[ilk bisected]" to the bug summary so it shows up in all the
right searches for us.
Thanks, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-12-15 7:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-14 11:58 [Regression] 3.18 black screen after boot (bisected) Heinz Diehl
2014-12-15 7:57 ` Daniel Vetter [this message]
2014-12-15 12:51 ` Heinz Diehl
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=20141215075734.GR27182@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@linux.ie \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
/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