From: Daniel Vetter <daniel@ffwll.ch>
To: Emmanuel Benisty <benisty.e@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Dave Airlie <airlied@linux.ie>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [Regression] 83f45fc turns machine's screen off
Date: Mon, 15 Dec 2014 08:31:56 +0100 [thread overview]
Message-ID: <20141215073156.GK27182@phenom.ffwll.local> (raw)
In-Reply-To: <CA+i8gKJPPPUXrxY5q+81xZG91azygoUb27R_Wid3GTpb3-1-rw@mail.gmail.com>
On Sun, Dec 14, 2014 at 02:07:19AM +0100, Emmanuel Benisty wrote:
> Hi Daniel,
>
> > On Mon, Nov 10, 2014 at 10:19 PM, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> >> Adding relevant mailing lists.
> >>
> >>
> >> On Sat, Nov 8, 2014 at 7:34 PM, Emmanuel Benisty <benisty.e@gmail.com> wrote:
> >>> Hi,
> >>>
> >>> The following commit permanently turns my screen off when x server is
> >>> started (i3 330M Ironlake):
> >>>
> >>> [83f45fc360c8e16a330474860ebda872d1384c8c] drm: Don't grab an fb
> >>> reference for the idr
> >>>
> >>> Reverting this commit fixed the issue.
> >>
> >> This is definitely unexpected. I think we need a bit more data to
> >> figure out what's going on here:
> >> - Please boot with drm.debug=0xe added to your kernel cmdline and grab
> >> the dmesg right after boot-up for both a working or broken kernel.
> >
> > Please see attached files.
> >
> >> - Are you using any special i915 cmdline options?
> >
> > Nope.
>
> Is there anything else I could provide to help fixing this issue? It's
> still in Linus' tree.
Sorry for the delay. Absolutely no difference in the relevant parts of the
log. There could be the chance that something is hidden somewhere, so can
please grab a new set of logs but this time with drm.debug=0xe?
-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:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+i8gKK0sj55s-Gk8Y36KM4yBFLvLotffbSodjH5Gsd_yxd5Sg@mail.gmail.com>
2014-11-10 21:19 ` [Regression] 83f45fc turns machine's screen off Daniel Vetter
2014-11-13 21:37 ` Emmanuel Benisty
2014-12-14 1:07 ` Emmanuel Benisty
2014-12-15 7:31 ` Daniel Vetter [this message]
2014-12-15 11:46 ` Emmanuel Benisty
2014-12-15 13:48 ` Daniel Vetter
2014-12-16 6:42 ` Heinz Diehl
2014-11-08 18:36 Emmanuel Benisty
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=20141215073156.GK27182@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@linux.ie \
--cc=benisty.e@gmail.com \
--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