From: Alexey Starikovskiy <aystarik@gmail.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: linux-acpi@vger.kernel.org
Subject: Re: Battery info bogus on Lenovo 3000 N100
Date: Sat, 23 Feb 2008 01:02:36 +0300 [thread overview]
Message-ID: <47BF467C.9070801@gmail.com> (raw)
In-Reply-To: <alpine.LNX.1.00.0802221232450.19024@iabervon.org>
Please open bug report at bugzilla.kernel.org against ACPI/battery.
Please attach dmesg and acpidump to that bug.
Please also attach actual /proc/acpi/battery/*/* files.
Thanks,
Alex.
Daniel Barkalow wrote:
> I'm having problems with the battery reporting on my laptop. In
> particular, the LEDs suggest that the battery isn't working at all, but
> /proc/acpi/battery/BAT1/state says it's fine. Furthermore, one time when I
> actually removed the battery entirely, /proc/acpi/.../info said (from
> memory, may be slightly off):
>
> present: yes
> design capacity: 4000 mAh
> last full capacity: 4000 mAh
> battery technology: rechargeable
> design voltage: 11100 mV
> design capacity warning: 420 mAh
> design capacity low: 156 mAh
> capacity granularity 1: 264 mAh
> capacity granularity 2: 3780 mAh
> model number: PABAS024
> serial number: 3658Q
> battery type: LION
> OEM info: COMPAL
>
> I've also been noticing for a while that the "remaining capacity" updates
> irregularly and isn't generally current, and it reports the design
> capacity when the state is "charged", even if discharging it at all
> indicates that it's actually a lot lower. I've noticed this from 2.6.17
> (the first kernel I had on this computer) to 2.6.22, the latest I've tried
> here.
>
> CONFIG_ACPI_DEBUG doesn't seem to be showing me anything particularly
> informative (When I remove or insert the battery, I get:
> [ACPI Debug] String: [0x12] "=====QUERY_25=====")
>
> There seem to be BIOS updates available, but nothing looks related.
>
> What information can I collect on this problem?
>
> -Daniel
> *This .sig left intentionally blank*
> -
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2008-02-22 22:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 17:55 Battery info bogus on Lenovo 3000 N100 Daniel Barkalow
2008-02-22 22:02 ` Alexey Starikovskiy [this message]
2008-02-25 6:18 ` Daniel Barkalow
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=47BF467C.9070801@gmail.com \
--to=aystarik@gmail.com \
--cc=barkalow@iabervon.org \
--cc=linux-acpi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox