From: Steven Newbury <steve@snewbury.org.uk>
To: Matthew Garrett <matthew.garrett@nebula.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
James Hogan <james@albanarts.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kamal Mostafa <kamal@canonical.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: Linux 3.11-rc2
Date: Tue, 23 Jul 2013 22:10:38 +0100 [thread overview]
Message-ID: <1374613838.5355.5.camel@artifact> (raw)
In-Reply-To: <1374609113.2641.2.camel@x230>
On Tue, 2013-07-23 at 19:51 +0000, Matthew Garrett wrote:
> On Tue, 2013-07-23 at 18:47 +0100, Steven Newbury wrote:
>
> > In the code as was present in the linux-pm/bleeding-edge tree I would
> > encounter a hard lockup on keyboard brightness trigger. This also occurred with
> > the code as it initially hit mainline, but a later commit fixed the crash*, but
> > resulted in no backlight controls being available at all.
> > /sys/class/backlight is empty.
>
> This is an Intel system using the i915 driver?
>
Yes, IVB i7-3840QM. CLEVO W270EUQ.
next prev parent reply other threads:[~2013-07-23 21:10 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-21 19:53 Linux 3.11-rc2 Linus Torvalds
2013-07-21 21:07 ` Tobias Klausmann
2013-07-22 13:08 ` Rafael J. Wysocki
2013-07-22 15:43 ` Tobias Klausmann
2013-07-21 23:08 ` James Hogan
2013-07-22 13:02 ` Rafael J. Wysocki
2013-07-22 13:15 ` Martin Steigerwald
2013-07-22 13:37 ` Rafael J. Wysocki
2013-07-22 18:46 ` Martin Steigerwald
2013-07-22 19:57 ` Rafael J. Wysocki
2013-07-24 5:10 ` Kalle Valo
2013-07-22 13:21 ` James Hogan
2013-07-22 18:11 ` Linus Torvalds
2013-07-22 19:54 ` Rafael J. Wysocki
2013-07-23 18:46 ` Linux 3.11-rc2 (acpi backlight) Kamal Mostafa
2013-07-24 0:05 ` Rafael J. Wysocki
2013-07-24 4:54 ` Steven Newbury
2013-07-24 6:49 ` James Hogan
2013-07-24 7:14 ` Mike Galbraith
2013-07-24 7:19 ` Igor Gnatenko
2013-07-24 12:06 ` Rafael J. Wysocki
2013-07-24 11:45 ` Jörg Otte
2013-07-25 13:00 ` Linux 3.11-rc2 (acpi backlight, revert) Rafael J. Wysocki
2013-07-25 14:43 ` Kamal Mostafa
2013-07-25 14:46 ` Daniel Vetter
2013-07-25 14:59 ` Kamal Mostafa
2013-07-25 14:52 ` Jörg Otte
2013-07-25 15:52 ` Jörg Otte
2013-07-25 19:14 ` James Hogan
2013-07-25 19:47 ` Rafael J. Wysocki
2013-07-26 4:23 ` Joerg Platte
2013-07-26 11:22 ` Igor Gnatenko
2013-07-26 7:43 ` Steven Newbury
2013-07-26 12:09 ` Martin Steigerwald
2013-07-26 12:40 ` Rafael J. Wysocki
2013-08-04 19:33 ` Martin Steigerwald
2013-08-04 22:15 ` Rafael J. Wysocki
2013-07-27 5:34 ` Kalle Valo
2013-07-27 12:18 ` Rafael J. Wysocki
2013-07-22 18:16 ` Linux 3.11-rc2 Matthew Garrett
2013-07-22 19:56 ` Rafael J. Wysocki
2013-07-23 17:47 ` Steven Newbury
2013-07-23 19:51 ` Matthew Garrett
2013-07-23 21:10 ` Steven Newbury [this message]
2013-07-23 21:24 ` Rafael J. Wysocki
2013-07-23 22:49 ` Steven Newbury
2013-07-22 1:25 ` Dave Chinner
2013-07-22 4:06 ` Al Viro
2013-07-24 3:22 ` Dave Chinner
2013-07-23 1:04 ` rydberg
2013-07-23 1:17 ` Myklebust, Trond
2013-07-23 18:31 ` Myklebust, Trond
2013-07-23 19:08 ` rydberg
2013-07-23 20:42 ` Linus Torvalds
2013-07-23 20:52 ` Myklebust, Trond
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=1374613838.5355.5.camel@artifact \
--to=steve@snewbury.org.uk \
--cc=james@albanarts.com \
--cc=kamal@canonical.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.garrett@nebula.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@sisk.pl \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).