Skip to contentSkip to conversation

2.6.13-rc5 - ACPI regression

DISCUSSION Lukas Hejtmanek 4 participants 6 messages Aug 2, 2005

lore
Share & tools
lore
#0 lore raw

Hello,

newly with 2.6.13-rc5 (previous -rc1 was quite ok)

$ time cat /proc/acpi/battery/BAT0/info  
present:                 yes
design capacity:         6000 mAh
last full capacity:      6000 mAh
battery technology:      rechargeable
design voltage:          14800 mV
design capacity warning: 600 mAh
design capacity low:     300 mAh
capacity granularity 1:  60 mAh
capacity granularity 2:  60 mAh
model number:            M6A
serial number:            
battery type:            LIon
OEM info:                ASUSTEK
real    0m32.521s
user    0m0.001s
sys     0m0.015s
Signature · 1 line
Lukáš Hejtmánek
#1 lore raw
Quoted 19 lines · Lukas Hejtmanek

Hello,

newly with 2.6.13-rc5 (previous -rc1 was quite ok)

$ time cat /proc/acpi/battery/BAT0/info
present:                 yes
design capacity:         6000 mAh
last full capacity:      6000 mAh
battery technology:      rechargeable
design voltage:          14800 mV
design capacity warning: 600 mAh
design capacity low:     300 mAh
capacity granularity 1:  60 mAh
capacity granularity 2:  60 mAh
model number:            M6A
serial number:
battery type:            LIon
OEM info:                ASUSTEK
Quoted 3 lines
real    0m32.521s
user    0m0.001s
sys     0m0.015s

Different data point, in case this might be useful...

Dell Latitude C640, uptodate FC4, kernel built with stock GCC 4.0.1:

time cat /proc/acpi/battery/BAT0/info

present:                 yes
design capacity:         65120 mWh
last full capacity:      45300 mWh
battery technology:      rechargeable
design voltage:          14800 mV
design capacity warning: 3000 mWh
design capacity low:     1000 mWh
capacity granularity 1:  200 mWh
capacity granularity 2:  200 mWh
model number:            LIP8120DLP
serial number:           363
battery type:            LION
OEM info:                Sony Corp.
real    0m1.372s
user    0m0.000s
sys     0m1.340s

--alessandro

"Nothing's hard as getting free from places I've already been"

(Wallflowers - "I've Been Delivered")

#2 lore raw
Quoted 29 lines · Alessandro Suardi
Quoted 19 lines · Lukas Hejtmanek

Hello,

newly with 2.6.13-rc5 (previous -rc1 was quite ok)

$ time cat /proc/acpi/battery/BAT0/info
present:                 yes
design capacity:         6000 mAh
last full capacity:      6000 mAh
battery technology:      rechargeable
design voltage:          14800 mV
design capacity warning: 600 mAh
design capacity low:     300 mAh
capacity granularity 1:  60 mAh
capacity granularity 2:  60 mAh
model number:            M6A
serial number:
battery type:            LIon
OEM info:                ASUSTEK
Quoted 3 lines
real    0m32.521s
user    0m0.001s
sys     0m0.015s

Different data point, in case this might be useful...

Dell Latitude C640, uptodate FC4, kernel built with stock GCC 4.0.1:

time cat /proc/acpi/battery/BAT0/info

Quoted 13 lines
present:                 yes
design capacity:         65120 mWh
last full capacity:      45300 mWh
battery technology:      rechargeable
design voltage:          14800 mV
design capacity warning: 3000 mWh
design capacity low:     1000 mWh
capacity granularity 1:  200 mWh
capacity granularity 2:  200 mWh
model number:            LIP8120DLP
serial number:           363
battery type:            LION
OEM info:                Sony Corp.

I did not notice before, but my values (capacity and so on) are completely wrong. It should contain values in mWh instead of mAh.

Signature · 1 line
Lukáš Hejtmánek
#3 lore raw
Quoted 44 lines · Lukas Hejtmanek
Quoted 29 lines · Alessandro Suardi
Quoted 19 lines · Lukas Hejtmanek

Hello,

newly with 2.6.13-rc5 (previous -rc1 was quite ok)

$ time cat /proc/acpi/battery/BAT0/info
present:                 yes
design capacity:         6000 mAh
last full capacity:      6000 mAh
battery technology:      rechargeable
design voltage:          14800 mV
design capacity warning: 600 mAh
design capacity low:     300 mAh
capacity granularity 1:  60 mAh
capacity granularity 2:  60 mAh
model number:            M6A
serial number:
battery type:            LIon
OEM info:                ASUSTEK
Quoted 3 lines
real    0m32.521s
user    0m0.001s
sys     0m0.015s

Different data point, in case this might be useful...

Dell Latitude C640, uptodate FC4, kernel built with stock GCC 4.0.1:

time cat /proc/acpi/battery/BAT0/info

Quoted 13 lines
present:                 yes
design capacity:         65120 mWh
last full capacity:      45300 mWh
battery technology:      rechargeable
design voltage:          14800 mV
design capacity warning: 3000 mWh
design capacity low:     1000 mWh
capacity granularity 1:  200 mWh
capacity granularity 2:  200 mWh
model number:            LIP8120DLP
serial number:           363
battery type:            LION
OEM info:                Sony Corp.
Quoted 2 lines

I did not notice before, but my values (capacity and so on) are completely wrong. It should contain values in mWh instead of mAh.

There's a new kernel boot oprion ec_polling that you may want to try.

Greets,
Rafael

Signature · 3 lines
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
		-- Lewis Carroll "Alice's Adventures in Wonderland"
#4 lore raw
Quoted 4 lines · Rafael J. Wysocki
Quoted 2 lines

I did not notice before, but my values (capacity and so on) are completely wrong. It should contain values in mWh instead of mAh.

There's a new kernel boot oprion ec_polling that you may want to try.

Now it's ok except asus_acpi module does not work any more.

It complains about generic hot key driver even when I do not have compiled generic hot key driver in.

Signature · 1 line
Lukáš Hejtmánek
#5 lore raw
In reply to Lukas Hejtmanek

On Tuesday 02 Aug 2005 20:05, Lukas Hejtmanek wrote:
[snip]

Quoted 3 lines

I did not notice before, but my values (capacity and so on) are completely wrong. It should contain values in mWh instead of mAh.

mWh is mAh x operational voltage. They're not "completely wrong", probably just whatever unit your machine's ACPI uses.

The units are not the problem, it sounds like some other ACPI bug.

Signature · 6 lines
Cheers,
Alistair.

'No sense being pessimistic, it probably wouldn't work anyway.'
Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.