public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexey Starikovskiy <astarikovskiy@suse.de>
To: Zhao Yakui <yakui.zhao@intel.com>
Cc: lenb@kernel.org, linux-acpi@vger.kernel.org
Subject: Re: The regression about EC GPE storm on the latest linus git tree
Date: Thu, 13 Nov 2008 11:32:57 +0300	[thread overview]
Message-ID: <491BE639.6070407@suse.de> (raw)
In-Reply-To: <1226539214.4006.70.camel@yakui_zhao.sh.intel.com>

Hi Yakui,

Does your latest kernel include yesterday pool of patches? 

Thanks,
Alex.
Zhao Yakui wrote:
> Hi, Alexey
>     I do some tests on the latest kernel and find that there exists the
> EC GPE storm on the three laptops. And then EC will work in polling
> mode. One is Asus EEEPC 1000. The other are HP laptops. 
>     
>     I do the similar test on the previous kernel(for example:
> 2.6.27-rc6, 2.6.27.4) and there is no EC GPE storm on the three laptops.
> The EC works in EC GPE interrupt mode. 
>     After the EC debug is used on the 2.6.27-rc6 kernel, I find that at
> most 8 EC interrupts are triggered in each EC transaction(This includes
> the effective EC GPE interrupts). In such case it should not be regarded
> as EC GPE storm.
>        
>     The attached are the dmesg info on the Asus EEEPC 1000. (One is
> based on the latest git tree. One is based on 2.6.27-rc6 kernel).
>     If you need to investigate the root cause about the EC GPE storm,
> please tell me what I should do. I will try my best to test the patch
> from you and give response.
> 
> Thanks.
>    Yakui
>  
> 


       reply	other threads:[~2008-11-13  8:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1226539214.4006.70.camel@yakui_zhao.sh.intel.com>
2008-11-13  8:32 ` Alexey Starikovskiy [this message]
2008-11-13  9:00 ` [PATCH] ACPI: EC: count interrupts only if called from interrupt handler Alexey Starikovskiy
2008-11-14  1:21   ` Zhao Yakui
2008-11-26 22:16   ` Len Brown

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=491BE639.6070407@suse.de \
    --to=astarikovskiy@suse.de \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=yakui.zhao@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