[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Battery status not correctly seen - how to fix?



On 10/08/2004 07:11 PM, Julien BLACHE wrote:
> "Kevin B. McCarty" <kmccarty@Princeton.EDU> wrote:
> 
> 
>>A little more info about this:  the battery level seen just dropped from
>>99% to 0% while running on battery, causing a shutdown before I could
>>plug in the power cable.  The result of "cat /proc/apm" is currently
>>
>>0.5 1.1 0x00 0x01 0x03 0x08 0% -1 min
> 
> 
> What are the reported values in /proc/pmu/* ? These are the ones you
> should trust.
> 
> JB.
> 

Forgot to CC the following to the list; doing so now:

sorry for the delay in responding; I've been on an airplane for the past
n hours.

/proc/pmu/battery_0:
flags      : 00000013
charge     : 0
max_charge : 3544
current    : 900
voltage    : 20424
time rem.  : 14176

info:
PMU driver version     : 2
PMU firmware version   : 0c
AC Power               : 1
Battery count          : 1

interrupts:
  0:          0 (Total CB1 triggered events)
  1:     282111 (Total GPIO1 triggered events)
  2:          0 (PC-Card eject button)
  3:          0 (Sound/Brightness button)
  4:     260571 (ADB message)
  5:          0 (Battery state change)
  6:      21466 (Environment interrupt)
  7:          0 (Tick timer)
  8:          0 (Ghost interrupt (zero len))
  9:         83 (Empty interrupt (empty mask))
 10:          1 (Max irqs in a row)

options:
lid_wakeup=1
server_mode=0


hmm, charge in "battery_0" is reported as zero, which suggests either a
kernel issue or a battery problem.

regards,

-- 
Kevin B. McCarty <kmccarty@princeton.edu>   Physics Department
WWW: http://www.princeton.edu/~kmccarty/    Princeton University
GPG public key ID: 4F83C751                 Princeton, NJ 08544



Reply to: