All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heinz Diehl <htd+ml@fritha.org>
To: linux-kernel@vger.kernel.org, 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 13:51:27 +0100	[thread overview]
Message-ID: <20141215125127.GA1886@fritha.org> (raw)
In-Reply-To: <20141215075734.GR27182@phenom.ffwll.local>

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

On 15.12.2014, Daniel Vetter wrote: 

> Can you please boot with drm.debug=0xf on both good and bad kernels and
> then grab dmesg from each?

The output is attached. The dmesg log stops after runlevel 3 for the
3.18 kernel, because I'm not able to do anything in runlevel 5 with a
black screen.

> 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.

Will do.


[-- Attachment #2: dmesg-3.17.6.good.txt.xz --]
[-- Type: application/octet-stream, Size: 36192 bytes --]

[-- Attachment #3: dmesg-3.18.bad.txt.xz --]
[-- Type: application/octet-stream, Size: 19708 bytes --]

[-- Attachment #4: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: Heinz Diehl <htd+ml@fritha.org>
To: linux-kernel@vger.kernel.org, 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 13:51:27 +0100	[thread overview]
Message-ID: <20141215125127.GA1886@fritha.org> (raw)
In-Reply-To: <20141215075734.GR27182@phenom.ffwll.local>

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

On 15.12.2014, Daniel Vetter wrote: 

> Can you please boot with drm.debug=0xf on both good and bad kernels and
> then grab dmesg from each?

The output is attached. The dmesg log stops after runlevel 3 for the
3.18 kernel, because I'm not able to do anything in runlevel 5 with a
black screen.

> 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.

Will do.


[-- Attachment #2: dmesg-3.17.6.good.txt.xz --]
[-- Type: application/octet-stream, Size: 36192 bytes --]

[-- Attachment #3: dmesg-3.18.bad.txt.xz --]
[-- Type: application/octet-stream, Size: 19708 bytes --]

  reply	other threads:[~2014-12-15 12:51 UTC|newest]

Thread overview: 5+ 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
2014-12-15  7:57   ` Daniel Vetter
2014-12-15 12:51   ` Heinz Diehl [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=20141215125127.GA1886@fritha.org \
    --to=htd+ml@fritha.org \
    --cc=airlied@linux.ie \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.