From: Tim Gardner <tim.gardner@canonical.com>
To: Ben Skeggs <skeggsb@gmail.com>
Cc: bskeggs@redhat.com, Seth Forshee <seth.forshee@canonical.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: 3.4-rc7 backlight regression on Dell XPS M1710
Date: Thu, 17 May 2012 08:41:34 -0600 [thread overview]
Message-ID: <4FB50E1E.8020202@canonical.com> (raw)
In-Reply-To: <CACAvsv551Q2Wb=bj6piizN88-+k-wCJS0FgT5j5KiK5N3Se=Gw@mail.gmail.com>
On 05/17/2012 12:20 AM, Ben Skeggs wrote:
> On Thu, May 17, 2012 at 10:30 AM, Ben Skeggs<bskeggs@redhat.com> wrote:
>> Am Mittwoch, den 16.05.2012, 12:17 -0600 schrieb Tim Gardner:
>>> commit b99da31ed8521eb78d5d6930f3128f8ecdb75fae causes the backlight in
>>> my Dell XPS M1710 to stop working. Symptoms are dim display and won't
>>> respond to key brightness events. I bisected and confirmed that
>>> reverting this single patch on top of 3.4-rc7 fixes the problem.
>> That commit is correct, it may have uncovered a bug elsewhere though.
> It's been pointed out I should probably be a bit more verbose about
> what I'm after here... Apologies :)
>
> The commit that causes the original regression is
> a0b25635515ef5049f93b032a1e37f18b16e0f6f. Did your backlight work
> correctly before this?
>
> Thanks,
> Ben.
>
I just checked that brightness controls worked with the original 2.6.32
kernel. The original regression commit
a0b25635515ef5049f93b032a1e37f18b16e0f6f went into 3.3, but the
backlight for this laptop has continued to function until commit
b99da31ed8521eb78d5d6930f3128f8ecdb75fae (3.4-rc6).
rtg@m1710:~$ uname -r
2.6.32-41-generic
rtg@m1710:~$ lsmod|egrep ^n
nouveau 515227 2
rtg
--
Tim Gardner tim.gardner@canonical.com
prev parent reply other threads:[~2012-05-17 14:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 18:17 3.4-rc7 backlight regression on Dell XPS M1710 Tim Gardner
2012-05-17 0:30 ` Ben Skeggs
2012-05-17 6:20 ` Ben Skeggs
2012-05-17 14:41 ` Tim Gardner [this message]
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=4FB50E1E.8020202@canonical.com \
--to=tim.gardner@canonical.com \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seth.forshee@canonical.com \
--cc=skeggsb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox