All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Starikovskiy <alexey.y.starikovskiy@linux.intel.com>
To: David Brownell <david-b@pacbell.net>
Cc: Len Brown <lenb@kernel.org>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	linux-acpi@vger.kernel.org
Subject: Re: 2.6.19-rc5 nasty ACPI regression, AE_TIME errors
Date: Thu, 16 Nov 2006 19:23:22 +0300	[thread overview]
Message-ID: <455C907A.8080600@linux.intel.com> (raw)
In-Reply-To: <200611160803.04152.david-b@pacbell.net>

David Brownell wrote:
> On Thursday 16 November 2006 7:41 am, Alexey Starikovskiy wrote:
>   
>> Looks like either EC GPE or whole ACPI irq got disabled... Could you 
>> check that ACPI interrupts still arrive after
>> you notice AE_TIME?
>>     
>
> If I unplug AC, /proc/interrrupts reports 2 IRQs going to ACPI.
> Then on replug, it reports 10-12 IRQs going to ACPI.
>   
What is the state of kacpid and kacpid_notify ?
>
>   
>> Also, may be attached patch will help?
>>     
>
> I'l give it a try next time I can reboot (presumably by this PM).
>
> - Dave
>
>
>   
>> Regards,
>>     Alex.
>>
>> David Brownell wrote:
>>     
>>> On Wednesday 15 November 2006 1:56 pm, David Brownell wrote:
>>>   
>>>       
>>>> On Wednesday 15 November 2006 6:48 am, Alexey Starikovskiy wrote:
>>>>     
>>>>         
>>>>> ec1.patch
>>>>>
>>>>>
>>>>> Always enable GPE after return from notify handler.
>>>>>
>>>>> From:  Alexey Starikovskiy <alexey.y.starikovskiy@linux.intel.com>
>>>>>
>>>>>
>>>>> ---
>>>>>       
>>>>>           
>>>> Yes, this seems to resolve the regression as well as Len's ec_intr=0 boot param.
>>>>     
>>>>         
>>> Whoops, I spoke too soon.  It does get rid of SOME of the AE_TIME errors.  But
>>> the system is still confused about whether or not the AC is connected, and
>>> whether the battery is charging or not; and the CPU is still relatively hot.
>>> Even with this patch I later got:
>>>
>>> ACPI Exception (evregion-0424): AE_TIME, Returned by Handler for [EmbeddedControl] [20060707]
>>> ACPI Exception (dswexec-0458): AE_TIME, While resolving operands for [OpcodeName unavailable] [2006070
>>> 7]
>>> ACPI Error (psparse-0537): Method parse/execution failed [\_TZ_.THRM._TMP] (Node ffff810002032d10), AE
>>> _TIME
>>>
>>> In short, better but evidently not yet good enough...
>>>
>>> - Dave
>>>
>>>
>>>
>>>   
>>>       
>>>> IMO this should get merged into 2.6.19 ASAP ...
>>>>
>>>>
>>>>     
>>>>         
>>>>>  drivers/acpi/ec.c |    2 --
>>>>>  1 files changed, 0 insertions(+), 2 deletions(-)
>>>>>
>>>>> diff --git a/drivers/acpi/ec.c b/drivers/acpi/ec.c
>>>>> index e6d4b08..937eafc 100644
>>>>> --- a/drivers/acpi/ec.c
>>>>> +++ b/drivers/acpi/ec.c
>>>>> @@ -465,8 +465,6 @@ static u32 acpi_ec_gpe_handler(void *dat
>>>>>  
>>>>>         if (value & ACPI_EC_FLAG_SCI) {
>>>>>                 status = acpi_os_execute(OSL_EC_BURST_HANDLER, acpi_ec_gpe_query, ec);
>>>>> -               return status == AE_OK ?
>>>>> -                   ACPI_INTERRUPT_HANDLED : ACPI_INTERRUPT_NOT_HANDLED;
>>>>>         }
>>>>>         acpi_enable_gpe(NULL, ec->gpe_bit, ACPI_ISR);
>>>>>         return status == AE_OK ?
>>>>>       
>>>>>           
>>     

  reply	other threads:[~2006-11-16 16:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-15  7:03 2.6.19-rc5 nasty ACPI regression, AE_TIME errors David Brownell
2006-11-15  7:48 ` Len Brown
2006-11-15 14:48   ` Alexey Starikovskiy
2006-11-15 21:56     ` David Brownell
2006-11-15 21:56       ` David Brownell
2006-11-16  1:10       ` David Brownell
2006-11-16  1:10         ` David Brownell
2006-11-16 15:41         ` Alexey Starikovskiy
2006-11-16 16:03           ` David Brownell
2006-11-16 16:23             ` Alexey Starikovskiy [this message]
2006-11-16 16:53               ` David Brownell
2006-11-16 21:56                 ` Alexey Starikovskiy
2006-11-17 21:45                   ` [Bulk] " David Brownell
2006-11-17  6:22           ` David Brownell
2006-11-17  6:22             ` David Brownell
2006-11-17 21:04             ` David Brownell
2006-11-18 16:18               ` Alexey Starikovskiy
2006-11-15 18:46   ` David Brownell
2006-11-21 14:47   ` Janosch Machowinski

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=455C907A.8080600@linux.intel.com \
    --to=alexey.y.starikovskiy@linux.intel.com \
    --cc=david-b@pacbell.net \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.