From: Nate Lawson <nate-Y6VGUYTwhu0@public.gmane.org>
To: "Mark M." <maalox-XzQKRVe1yT0V+D8aMU/kSg@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: RE: acpi-20031203-2.6.0.diff brokes the battery status readings with 2.6.0 in DELL Inspiron 8500
Date: Tue, 30 Dec 2003 09:59:05 -0800 (PST) [thread overview]
Message-ID: <20031230094935.E98403@root.org> (raw)
In-Reply-To: <3FECC541.10001-XzQKRVe1yT0V+D8aMU/kSg@public.gmane.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=X-UNKNOWN, Size: 3198 bytes --]
Your dmesg shows that this is the same thing we found broken for Dells:
> -0091: *** Error: ut_allocate: Attempt to allocate zero bytes
> -0091: *** Error: ut_allocate: Attempt to allocate zero bytes
> -0091: *** Error: ut_allocate: Attempt to allocate zero bytes
> -0091: *** Error: ut_allocate: Attempt to allocate zero bytes
Here is the bug info. Note that Luming's patch does NOT fix the problem
but just silences the warnings. If you use the ASL patch I have attached
that adds RefOf/DerefOf (credit Mark Santcroos), the problems are fixed.
You can also revert dsmthdat.c back to what it was pre-0619 and that also
fixes the problem.
http://bugme.osdl.org/show_bug.cgi?id=1728
The issue is, ACPI-CA is still not getting its argument-passing right
after moving away from "always copy" semantics.
-Nate
On Fri, 26 Dec 2003, Mark M. wrote:
> I have the same problem with my Dell Inspiron 5150. Battery status AND
> temperature reading stopped working when I upgraded from 2.6.0-test11-mm
> to 2.6.0-mm1. I noticed it because klaptop stopped showing the battery
> charge status, and gkrellm2 stopped showing the battery and temperature
> status (stuck at 25C). Actually, the only thing that still works with
> the battery is wether the AC is plugged in or not. Here is my /proc and
> dmesg from 2.6.0-mm1. I can reboot and show you the working test11-mm
> stuff as well, if needed.
> ...
> root-2T+B9ReNDUQ@public.gmane.org maalox # cat /proc/acpi/battery/BAT0/state
> present: yes
> capacity state: ok
> charging state: unknown
> present rate: 0 mW
> remaining capacity: 0 mWh
> present voltage: 0 mV
>
> All the 0 readings have actual numbers with test11-mm, as well as model
> number, serial number, ...
>
> From: Brown, Len <len-lUQJ9CVx3tM@public.gmane.org>
> RE: acpi-20031203-2.6.0.diff brokes the battery status readings with
> 2.6.0 in DELL Inspiron 8500
> 2003-12-19 08:11
>
> dmesg from before and after would help, plus the info under
> /proc/acpi/battery.
>
> Thanks,
> -Len
>
> > -----Original Message-----
> > From: acpi-devel-admin-I+uqrFQUvWk@public.gmane.org
> > [mailto:acpi-devel-admin-I+uqrFQUvWk@public.gmane.org] On Behalf Of
> > Pere Castañer
> > Sent: Thursday, December 18, 2003 7:00 PM
> > To: acpi-devel
> > Subject: [ACPI] acpi-20031203-2.6.0.diff brokes the battery
> > status readings with 2.6.0 in DELL Inspiron 8500
> >
> >
> > I've just aplyied last patch into 2.6.0 stable release and it
> > brokes the battery monitor from acpi in
> > /proc/acpi/battery/BAT0/status...because of this
> > gnome-battery applet don't shows any information.
> >
> > Do you need more information?
> >
> > PS:with acpi included on 2.6.0 all works fine.
>
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&op=click
next prev parent reply other threads:[~2003-12-30 17:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Aa16k-00089f-Ft@sc8-sf-list2.sourceforge.net>
[not found] ` <E1Aa16k-00089f-Ft-ek0oC1U1TqqnvZpeIfgr/KQD96bmaF075NbjCUgZEJk@public.gmane.org>
2003-12-26 23:33 ` acpi-20031203-2.6.0.diff brokes the battery status readings with 2.6.0 in DELL Inspiron 8500 Mark M.
[not found] ` <3FECC541.10001-XzQKRVe1yT0V+D8aMU/kSg@public.gmane.org>
2003-12-30 17:59 ` Nate Lawson [this message]
2003-12-31 10:31 Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401720C69-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2003-12-31 19:12 ` Mark M.
[not found] ` <3FF31FB6.7040306-XzQKRVe1yT0V+D8aMU/kSg@public.gmane.org>
2004-01-01 1:43 ` Nate Lawson
-- strict thread matches above, loose matches on Subject: below --
2004-01-18 7:01 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=20031230094935.E98403@root.org \
--to=nate-y6vguytwhu0@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=maalox-XzQKRVe1yT0V+D8aMU/kSg@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