Re: 2.6.19-rc5 nasty ACPI regression, AE_TIME errors

[David Brownell <david-b@pacbell.net>]

On Tuesday 14 November 2006 11:48 pm, Len Brown wrote:
> On Wednesday 15 November 2006 02:03, David Brownell wrote:
> > dmesg reports to me stuff like
> > 
> > ACPI Exception (evregion-0424): AE_TIME, Returned by Handler for [EmbeddedControl] [20060707]
> > ACPI Exception (dswexec-0458): AE_TIME, While resolving operands for [OpcodeName unavailable] [20060707]
> > ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.LPC0.BAT1._BIF] (Node ffff8100020368d0), AE_TIME
> > ACPI Exception (acpi_battery-0148): AE_TIME, Evaluating _BIF [20060707]
> > ACPI: read EC, IB not empty
> > ACPI Exception (evregion-0424): AE_TIME, Returned by Handler for [EmbeddedControl] [20060707]
> > ACPI Exception (dswexec-0458): AE_TIME, While resolving operands for [OpcodeName unavailable] [20060707]
> > ACPI Error (psparse-0537): Method parse/execution failed [\_TZ_.THRM._TMP] (Node ffff810002032d10), AE_TIME
> 
> AE_TIME is generally used for timeout situations -- ie didn't get a semaphore within a certain period.
> 
> Any change if you boot with "ec_intr=0"?

That does seem to get rid of the AE_TIME messages; thanks!

Next I'll try that "ec1.patch" from Alex, without overriding ec_intr.

- Dave


> 
> thanks,
> -Len
> 
> > It never used to complain at all.  This is an amd64 laptop, and related symptoms
> > include
> > 
> >  - kpowersave not being able to monitor the batter or AC adapter correctly;
> >    leading to catastrophes like laptop powering itself off with no warning,
> >    loss of work, filesystem needing log recovery, and so forth.
> > 
> >  - Serious fan action.  Recent kernels seemed to finally be doing sane things
> >    so that e.g. just editing text kept the CPU cool ... but now it's on almost
> >    all the time, CPU is very hot.
> > 
> > What's an AE_TIME?
> > 
> > I'm not quite sure where these problems crept in, but I never saw such stuff with
> > 2.6.18 at all.
> > 
> > - Dave
> > 
> >