From: Maxim Levitsky <maximlevitsky@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
Linux PM <linux-pm@lists.linux-foundation.org>,
"Moore, Robert" <robert.moore@intel.com>,
len.brown@intel.com
Subject: Re: commit 'ACPICA: Minimize the differences between linux GPE code and ACPICA code base' breaks EC GPE on my system
Date: Fri, 11 Jun 2010 22:59:06 +0300 [thread overview]
Message-ID: <1276286346.30124.4.camel@maxim-laptop> (raw)
In-Reply-To: <201006112150.43743.rjw@sisk.pl>
On Fri, 2010-06-11 at 21:50 +0200, Rafael J. Wysocki wrote:
> On Friday, June 11, 2010, Maxim Levitsky wrote:
> > On Fri, 2010-06-11 at 21:23 +0200, Rafael J. Wysocki wrote:
> > > On Friday, June 11, 2010, Maxim Levitsky wrote:
> > > > Just bisected it.
> > > >
> > > > I also tried linux-acpi-next/test, and no change.
> > > >
> > > > The sympthoms are that EC does't sent any GPEs, and therefore battery
> > > > insert/removal events don't show up.
> > > >
> > > > It can be see by doing 'grep . /sys/firmware/acpi/interrupts/*'
> > > > With regression the line is shown like this:
> > > >
> > > >
> > > > /sys/firmware/acpi/interrupts/gpe1C: 1 enabled
> > > >
> > > > Without regression it is
> > > >
> > > > /sys/firmware/acpi/interrupts/gpe1C: 22889 enabled
> > > >
> > > > and steadily increasing.
> > > >
> > > > After suspend/resume, regression disappears.
> > >
> > > Hmm.
> > >
> > > Can you please apply the following patches:
> > >
> > > https://patchwork.kernel.org/patch/104903/
> > > https://patchwork.kernel.org/patch/104912/
> > > https://patchwork.kernel.org/patch/104909/
> > > https://patchwork.kernel.org/patch/104911/
> > > https://patchwork.kernel.org/patch/104910/
> > >
> > > on top of current -git and see if the problem is still there?
> > >
> > > Rafael
> >
> > These patch don't apply nether on top of linus tree nor on top of
> > acpi-test tree (which includes these?)
>
> Yes, acpi-test contains them, so you can test that tree. I'm not sure why
> they don't apply on top of the Linus' tree, though.
I was using acpi-next all the time, so these patches don't help.
I partially reverted the guilty commit, and compile the kernel.
Best regards,
Maxim Levitsky
next prev parent reply other threads:[~2010-06-11 19:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1276256839.4251.7.camel@maxim-laptop>
[not found] ` <201006112123.17706.rjw@sisk.pl>
2010-06-11 19:43 ` commit 'ACPICA: Minimize the differences between linux GPE code and ACPICA code base' breaks EC GPE on my system Rafael J. Wysocki
[not found] ` <1276285623.30124.1.camel@maxim-laptop>
2010-06-11 19:50 ` Rafael J. Wysocki
[not found] ` <201006112150.43743.rjw@sisk.pl>
2010-06-11 19:59 ` Maxim Levitsky [this message]
[not found] ` <201006112143.54654.rjw@sisk.pl>
2010-06-11 20:32 ` Maxim Levitsky
[not found] ` <1276288322.2651.4.camel@maxim-laptop>
2010-06-11 20:34 ` Rafael J. Wysocki
[not found] ` <201006112234.39747.rjw@sisk.pl>
2010-06-11 20:59 ` Rafael J. Wysocki
[not found] ` <201006112259.33602.rjw@sisk.pl>
2010-06-11 21:43 ` Maxim Levitsky
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=1276286346.30124.4.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=rjw@sisk.pl \
--cc=robert.moore@intel.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