public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bruno Ducrot <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
To: Adam Kessel <adam-/J5p37YCQWYytDrLOV7HaA@public.gmane.org>
Cc: Nate Lawson <nate-Y6VGUYTwhu0@public.gmane.org>,
	acpi-devel-TtF/mJH4Jtrk1uMJSBkQmQ@public.gmane.org
Subject: Re: Handler for [EmbeddedControl] returned AE_TIME in 2.6.1/20040116
Date: Thu, 5 Feb 2004 10:38:05 +0100	[thread overview]
Message-ID: <20040205093805.GO882@poupinou.org> (raw)
In-Reply-To: <20040204204055.GA8434-H/G4Yv+sbq78nmnftgJBZjK0Oss5Xsdo@public.gmane.org>

On Wed, Feb 04, 2004 at 03:40:55PM -0500, Adam Kessel wrote:
> On Wed, Feb 04, 2004 at 11:32:26AM +0100, Bruno Ducrot wrote:
> > > > We moved to a 100 ms timeout on EC requests for FreeBSD because some
> > > > devices just couldn't respond quicker.  But I think there's a larger issue
> > #define ACPI_EC_UDELAY_COUNT	10000
> 
> I tried this patch, and it does prevent the AE_TIME error. 
> 
> The battery charge indicator now seems unreliable, however, after
> switching from AC to battery and back.  For example, it will drop from
> 70%-80% down to 2% fairly quickly, but I can still run the machine for
> quite a while at 2%.  It also has jumped from 80% up to 100% in a couple
> of minutes, much faster than it could actually charge.
> 
> I'm not sure if any of this is related to the AE_TIME problem, but I'm
> putting it out here to see if there are any ideas.

I see 3 possibilities:

1- the EC firmware is somehow broken.  Nobody here then can help you
other than to tell you to go to EOM support, since most EC's are
microcontrollers, requiring a firmware for themself (those firmware
may contain bug, like any other software), and get the latest BIOS (this
EC's firmware may be downloaded at boot time on the chip by the bios),

2- the battery is dying and need to be replaced,

3- or, there is some bug in the current implementation under linux.

Cheers,

-- 
Bruno Ducrot

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

      parent reply	other threads:[~2004-02-05  9:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-03 17:24 Handler for [EmbeddedControl] returned AE_TIME in 2.6.1/20040116 Adam Kessel
     [not found] ` <20040203172413.GA1299-H/G4Yv+sbq78nmnftgJBZjK0Oss5Xsdo@public.gmane.org>
2004-02-03 22:40   ` Nate Lawson
     [not found]     ` <20040203143906.B33512-Y6VGUYTwhu0@public.gmane.org>
2004-02-03 23:41       ` Adam Kessel
     [not found]         ` <20040203234141.GA8327-/J5p37YCQWYytDrLOV7HaA@public.gmane.org>
2004-02-04 10:32           ` Bruno Ducrot
     [not found]             ` <20040204103226.GI882-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-02-04 20:40               ` Adam Kessel
     [not found]                 ` <20040204204055.GA8434-H/G4Yv+sbq78nmnftgJBZjK0Oss5Xsdo@public.gmane.org>
2004-02-05  9:38                   ` Bruno Ducrot [this message]

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=20040205093805.GO882@poupinou.org \
    --to=ducrot-kk6yzipjem5g9huczpvpmw@public.gmane.org \
    --cc=acpi-devel-TtF/mJH4Jtrk1uMJSBkQmQ@public.gmane.org \
    --cc=adam-/J5p37YCQWYytDrLOV7HaA@public.gmane.org \
    --cc=nate-Y6VGUYTwhu0@public.gmane.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