From: Gerhard Schrenk <deb.gschrenk@gmx.de>
To: "Yu, Luming" <luming.yu@intel.com>
Cc: "Brown, Len" <len.brown@intel.com>, linux-kernel@vger.kernel.org
Subject: Re: EC interrupt mode by default breaks power button and lid button
Date: Fri, 10 Feb 2006 06:14:52 +0100 [thread overview]
Message-ID: <20060210051451.GA4351@mailhub.uni-konstanz.de> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F840AE28A07@pdsmsx403>
* Yu, Luming <luming.yu@intel.com> [2006-02-10 00:37]:
> It's interesting. Could you file a bug in ACPI category on
> bugzilla.kernel.org?
http://bugzilla.kernel.org/show_bug.cgi?id=6049
BTW with ec_initr=1 I cannot toggle the hardware based rf_kill (for ipw2200).
But with ec_initr=0 I can toggle it. This is reflected by the blue "WLAN" led and
/sys/devices/pci0000:00/0000:00:1e.0/0000:01:09.0/rf_kill
> BTW, does battery work?
Mmmh. I see interrupt 9 "IO-APIC-edge acpi" in /proc/interrupts
increase for ec_intr=0. But it seems to increase all the time so I'm not
sure if it's triggered by battery (un)plug events.
However I cannot see any acpid-events in /var/log/acpid with ec_initr=0 when
(un)plugging the battery. (battery was present and correctly detected on boot.)
For ec_intr=1 interrupt 9 "IO-APIC-edge acpi in /proc/interrupts is
definitely always constant to 1. No acpid-events, too.
Interestingly the following battery problem is independant of ec_intr:
/proc/acpi/battery/BAT1/{info,state} shows only sensible battery data, if the
battery was **present at boot time**. When unplugging the battery it still says
"present: yes" and /proc/acpi/battery/BAT1/info does not change at all.
/proc/acpi/battery/BAT1/state does change like this:
--- ec1-plugged-state 2006-02-10 04:40:54.000000000 +0100
+++ ec1-unplugged-state 2006-02-10 04:42:31.000000000 +0100
@@ -1,6 +1,6 @@
present: yes
capacity state: ok
-charging state: charging
-present rate: 1930 mA
-remaining capacity: 2433 mAh
-present voltage: 16202 mV
+charging state: charged
+present rate: unknown
+remaining capacity: unknown
+present voltage: 10000 mV
If the battery was **not present at boot time** and is plugged in *after* booting
the system, it will never be detected by /proc/acpi/battery/BAT1/{info,state}.
It always says "present: no". With Kernel v2.6.15 compiling the acpi drivers as modules, i.e.
CONFIG_ACPI_BATTERY=m and same fo other acpi drivers helps. But I have to
$ rmmod battery
$ modprobe battery
first. No chance with statically compiled acpi-drivers. :(
-- Gerhard
next prev parent reply other threads:[~2006-02-10 5:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 1:29 Yu, Luming
2006-02-10 5:14 ` Gerhard Schrenk [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-07 6:52 Yu, Luming
2006-02-07 14:08 ` Gerhard Schrenk
2006-02-06 7:37 Yu, Luming
2006-02-06 7:37 ` Jiri Slaby
2006-02-06 13:34 ` Gerhard Schrenk
2006-02-05 18:04 Gerhard Schrenk
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=20060210051451.GA4351@mailhub.uni-konstanz.de \
--to=deb.gschrenk@gmx.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luming.yu@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
all inboxes | Powered by JetHome®