From: Jani Nikula <jani.nikula@linux.intel.com>
To: James Courtier-Dutton <james.dutton@gmail.com>,
Intel-gfx@lists.freedesktop.org
Subject: Re: Regression: Backlight not coming on after resume.
Date: Thu, 28 Feb 2013 17:33:56 +0200 [thread overview]
Message-ID: <87lia8mp0b.fsf@intel.com> (raw)
In-Reply-To: <CAAMvbhG461HNV4-VaLDDwP5Z-FU4VttZO+ct2MogXSaQ8Cm6jg@mail.gmail.com>
On Thu, 28 Feb 2013, James Courtier-Dutton <james.dutton@gmail.com> wrote:
> Bisect done on tree:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
> Worked on 3.7.
> Broken on 3.8
>
> Problem: "Backlight not coming on after resume."
> git finally bisected for my Samsung Serial 7 Laptop.
> Bisecting: 0 revisions left to test after this (roughly 0 steps)
> [cf0a6584aa6d382f802f2c3cacac23ccbccde0cd] drm/i915: write backlight
> harder <- This is the problem commit. Seems that fixing some
> machines breaks others, based on the existing comments on that patch.
The backlight haunts us again. Could you post the dmesg with
drm.debug=0xe module parameter, first running vanilla 3.8, and then with
the bad commit reverted, please?
Might not be a bad idea to file a bug on Product=DRI,
Component=DRM/Intel at https://bugs.freedesktop.org (see
https://01.org/linuxgraphics/documentation/how-report-bugs-0 for
details) and attach your bisect results and the dmesgs there.
Thanks,
Jani.
next prev parent reply other threads:[~2013-02-28 15:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 14:56 Regression: Backlight not coming on after resume James Courtier-Dutton
2013-02-28 15:33 ` Jani Nikula [this message]
2013-02-28 17:20 ` Takashi Iwai
2013-03-01 8:45 ` James Courtier-Dutton
2013-03-01 14:47 ` Jani Nikula
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=87lia8mp0b.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=james.dutton@gmail.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 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.