From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Cork <kernel@box.qzdev.se>
Cc: linux-acpi@vger.kernel.org, Aaron Lu <aaron.lu@intel.com>
Subject: Re: Sys backlight is empty since landing of "ACPI / PCI: Make PCI root driver use struct acpi_scan_handler"
Date: Thu, 27 Jun 2013 00:08:14 +0200 [thread overview]
Message-ID: <2662547.VNNgPCsUL0@vostro.rjw.lan> (raw)
In-Reply-To: <450286594.1598749.1372279129153.JavaMail.root@qzdev.se>
On Wednesday, June 26, 2013 08:38:49 PM Cork wrote:
> // Cork
OK, thanks.
The initialization ordering obviously changed in 3.9 and the ACPI video
driver fails to find your backlight device.
Can you please tell me what the output of
$ find /sys/devices/ -name LNXVIDEO\*
is on your system in 3.9 and 3.8?
Rafael
>
> ----- Original Message -----
> > From: "Rafael J. Wysocki" <rjw@sisk.pl>
> > To: "Cork" <kernel@box.qzdev.se>
> > Cc: linux-acpi@vger.kernel.org, "Aaron Lu" <aaron.lu@intel.com>
> > Sent: Wednesday, 26 June, 2013 10:05:38 PM
> > Subject: Re: Sys backlight is empty since landing of "ACPI / PCI: Make PCI root driver use struct acpi_scan_handler"
> >
> > On Wednesday, June 26, 2013 09:52:46 PM Rafael J. Wysocki wrote:
> > > On Wednesday, June 26, 2013 07:31:00 PM Cork wrote:
> > > > Hello. This is my first time sending a report like this, so
> > > > please excuse me if I'm missing some vital information.
> > > >
> > > > From updating the kernel in Arch linux to 3.9 the brightness
> > > > controls stopped working on my Clevo P0150HM. I have tried the
> > > > acpi_backlight=vendor boot parameter but it makes no difference.
> > > >
> > > > While researching this problem I've found that
> > > > /sys/class/backlight is empty in the versions where the buttons
> > > > isn't working. Bisecting points to
> > > > 00c43b9682507dc622c03172fde1032e2a216e9d [1] as the first commit
> > > > showing the symptoms.
> > > >
> > > > Attached is the output from journalctl -b _TRANSFORM=kernel for
> > > > the two versions. Not sure what other useful information I can
> > > > provide apart from that, so please direct me if there is
> > > > something missing.
> > > >
> > > > [1]
> > > > https://github.com/torvalds/linux/commit/00c43b9682507dc622c03172fde1032e2a216e9d
> > >
> > > Interesting.
> > >
> > > Please send the output of acpidump from your machine.
> >
> > Also please put initcall_debug into the kernel command line and send
> > dmesg from
> > the working and not working kernels with that.
> >
> > Thanks,
> > Rafael
> >
> >
> > --
> > I speak only for myself.
> > Rafael J. Wysocki, Intel Open Source Technology Center.
> >
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2013-06-26 21:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <117469492.1598370.1372275060043.JavaMail.root@qzdev.se>
2013-06-26 19:52 ` Sys backlight is empty since landing of "ACPI / PCI: Make PCI root driver use struct acpi_scan_handler" Rafael J. Wysocki
2013-06-26 20:05 ` Rafael J. Wysocki
[not found] ` <450286594.1598749.1372279129153.JavaMail.root@qzdev.se>
2013-06-26 22:08 ` Rafael J. Wysocki [this message]
2013-06-27 1:38 ` Aaron Lu
2013-06-27 5:40 ` Cork
2013-06-27 12:18 ` Rafael J. Wysocki
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=2662547.VNNgPCsUL0@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=aaron.lu@intel.com \
--cc=kernel@box.qzdev.se \
--cc=linux-acpi@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