Re: RE: acpi-20031203-2.6.0.diff brokes the battery status readings with 2.6.0 in DELL Inspiron 8500

Re: RE: acpi-20031203-2.6.0.diff brokes the battery status readings with 2.6.0 in DELL Inspiron 8500

[Nate Lawson]

[-- 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

RE: RE: acpi-20031203-2.6.0.diff brokes the battery status readings with 2.6.0 in DELL Inspiron 8500

[Yu, Luming]

>>      -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.

Please try patch filed at  http://bugme.osdl.org/show_bug.cgi?id=1766



-------------------------------------------------------
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

Re: RE: acpi-20031203-2.6.0.diff brokes the battery status readings with 2.6.0 in DELL Inspiron 8500

[Mark M.]

Success! I used the patch below and things seem to be working again. 
Actually, I manually edited my (2.6.0-mm) 
/usr/src/linux/drivers/acpi/dispatcher/dsmthdat.c
because i don't think the paths in the patch would have worked. I just 
recompiled the kernel and rebooted.

As a side note, I didn't include the before last line of the patch 
"new_obj_desc;", because it wasn't in my version of the file.

Here is the proof:

maalox-2T+B9ReNDUQ@public.gmane.org maalox $ uname -a
Linux laptop 2.6.0-mm1 #4 Wed Dec 31 13:53:35 EST 2003 i686 Mobile 
Intel(R) Pentium(R) 4     CPU 3.06GHz GenuineIntel GNU/Linux

maalox-2T+B9ReNDUQ@public.gmane.org maalox $ cat /proc/acpi/thermal_zone/THM/temperature
temperature:             50 C

maalox-2T+B9ReNDUQ@public.gmane.org maalox $ cat /proc/acpi/battery/BAT0/
alarm  info   state
maalox-2T+B9ReNDUQ@public.gmane.org maalox $ cat /proc/acpi/battery/BAT0/alarm
alarm:                   626 mAh

maalox-2T+B9ReNDUQ@public.gmane.org maalox $ cat /proc/acpi/battery/BAT0/info
present:                 yes
design capacity:         6450 mAh
last full capacity:      6263 mAh
battery technology:      rechargeable
design voltage:          14800 mV
design capacity warning: 626 mAh
design capacity low:     189 mAh
capacity granularity 1:  5 mAh
capacity granularity 2:  5 mAh
model number:            DELL 0009Y
serial number:           10421
battery type:            LION
OEM info:                Sony

maalox-2T+B9ReNDUQ@public.gmane.org maalox $ cat /proc/acpi/battery/BAT0/state
present:                 yes
capacity state:          ok
charging state:          unknown
present rate:            unknown
remaining capacity:      6450 mAh
present voltage:         16355 mV

Obviously, the KDE battery monitor is working again, as is the gkrellm 
stuff.

Thanks,
Mark

P.S. Does anyone know why the temparature reading from acpi is always 1 
degree higher than the one reported by the i8k module for dells? I see 
both readings side by side in gkrellm.

Yu, Luming wrote:
>>>     -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.
> 
> 
> Please try patch filed at  http://bugme.osdl.org/show_bug.cgi?id=1766
> 
> 
> 
> -------------------------------------------------------
> 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
> _______________________________________________
> Acpi-devel mailing list
> Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/acpi-devel
> 




-------------------------------------------------------
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=1278&alloc_id=3371&op=click

Re: RE: acpi-20031203-2.6.0.diff brokes the battery status readings with 2.6.0 in DELL Inspiron 8500

[Nate Lawson]

I can confirm success for one FreeBSD user with a broken Inspiron also.
Thanks for your work and I hope you can come up with a proper fix and
import it soon!

On Wed, 31 Dec 2003, Mark M. wrote:
> Success! I used the patch below and things seem to be working again.
> Actually, I manually edited my (2.6.0-mm)
> /usr/src/linux/drivers/acpi/dispatcher/dsmthdat.c
> because i don't think the paths in the patch would have worked. I just
> recompiled the kernel and rebooted.
>
> As a side note, I didn't include the before last line of the patch
> "new_obj_desc;", because it wasn't in my version of the file.

We removed that line from FreeBSD since it appears to be a typo.  Patch
was submitted back to Intel.

-Nate


-------------------------------------------------------
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=1278&alloc_id=3371&op=click

RE: RE: acpi-20031203-2.6.0.diff brokes the battery status readings with 2.6.0 in DELL Inspiron 8500

[Yu, Luming]

Please try patches:

http://bugzilla.kernel.org/show_bug.cgi?id=1766
http://bugzilla.kernel.org/show_bug.cgi?id=1791



-------------------------------------------------------
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