public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Fred Labrosse <ffl-4CLdheC3Iye1Qrn1Bg8BZw@public.gmane.org>
To: "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>,
	hgfelger-9nAOAgdJVo4b1SvskN2V4Q@public.gmane.org,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: 2.6.9 battery status  regression ? [was RE: Battery status wrong from 2.6.7 when running on batteries]
Date: Wed, 17 Nov 2004 10:06:12 +0000	[thread overview]
Message-ID: <16795.8852.83376.901018@aber.ac.uk> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F84041AC079@pdsmsx403>

Yu, Luming wrote:
 > I just find out the changes that could affect this area. And has
 > attached
 > at bug 3678. I hope you guys can verify if it is a regression.

I can't find it.

However, I think there's been some misunderstanding somewhere.  What is a
regression in 2.6.9 is the shutdown problem, reported in bug 3669 (and it
seems it's been solved).

Bug 3678 is about wrong battery and temperature (and maybe others) status
reported soon after running on batteries, but never when running on AC.
The problem remains after plugging back the AC.  THIS IS A REGRESSION OF
2.6.7.

Hope this helps.

Fred



-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8

  reply	other threads:[~2004-11-17 10:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-16  9:20 2.6.9 battery status regression ? [was RE: Battery status wrong from 2.6.7 when running on batteries] Yu, Luming
2004-11-17 10:06 ` Fred Labrosse [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-11-17 11:30 Yu, Luming
2004-11-29  7:09 Yu, Luming
2004-11-29  8:23 Yu, Luming

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=16795.8852.83376.901018@aber.ac.uk \
    --to=ffl-4cldhec3iye1qrn1bg8bzw@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=hgfelger-9nAOAgdJVo4b1SvskN2V4Q@public.gmane.org \
    --cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=sziwan-DETuoxkZsSqrDJvtcaxF/A@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