On Tue, 2013-07-23 at 23:24 +0200, Rafael J. Wysocki wrote: > On Tuesday, July 23, 2013 06:47:55 PM Steven Newbury wrote: > > On Mon, 2013-07-22 at 21:56 +0200, Rafael J. Wysocki wrote: > > > On Monday, July 22, 2013 06:16:20 PM Matthew Garrett wrote: > > > > On Mon, 2013-07-22 at 15:02 +0200, Rafael J. Wysocki wrote: > > > > > > > > > In the meantime I received a report from Steven Newbury that these changes > > > > > broke things for him too, so we need to revert commits 8c5bd7a and efaa14c. > > > > > The other two commits in the series should be benign. > > > > > > > > Could you let me know the details of this problem? > > > > > > Steven, can you please describe the problem you're seeing to Matthew and > > > the other people on the list? > > > > > > Rafael > > > > > > > Before the changes backlight was working fine using the ACPI method: > > /sys/class/backlight/acpi_video0/ is present and the keyboard function keys > > control brightness with notifications working in GNOME. > > > > 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. > > > > *not actually sure if /sys/class/backlight contained anything before this > > Hmm. Which commit fixed the crash for you? > > Rafael > I'll see if I can build a broken kernel tomorrow, after backing up! ;-) -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
