This does look like an events/0 runaway - It can flatten a full battery in little more than anhour when it really gets going :(
Its apparently fixed in latest kernels, but thats not an option for me at least - though with 2008.12, it happens a lot less. BillK On Wed, 2009-01-28 at 18:08 +0100, Christ van Willegen wrote: > On Wed, Jan 28, 2009 at 4:40 PM, Andy Green <a...@openmoko.com> wrote: > > Somebody in the thread at some point said: > > > > |> It's hard to guess where the power is going if you can't ssh into it. > > | I'll go home and check if I can still SSH into it from Ubuntu. > > > > If you can, look at the /sys for bq27000 idea of temperature and current. > > When I got back to the phone, it was dead... > > I hooked it up to my computer, but was unsure if it was already > correctly enumerated. Apparently it wasn't, and 100mA is certainly not > enough to remain warm! > > Post-mortem is not possible, I guess... > > Here's the current info, and boy, was it empty... > /sys/devices/platform/bq27000-battery.0/power_supply/bat# cat uevent > POWER_SUPPLY_NAME=bat > POWER_SUPPLY_TYPE=Battery > POWER_SUPPLY_STATUS=Charging > POWER_SUPPLY_VOLTAGE_NOW=3530000 > POWER_SUPPLY_CURRENT_NOW=-274125 > POWER_SUPPLY_CHARGE_FULL=1093134 > POWER_SUPPLY_TEMP=226 > POWER_SUPPLY_TECHNOLOGY=Li-ion > POWER_SUPPLY_PRESENT=1 > POWER_SUPPLY_TIME_TO_EMPTY_NOW=3932100 > POWER_SUPPLY_TIME_TO_FULL_NOW=22560 > POWER_SUPPLY_CAPACITY=0 > POWER_SUPPLY_ONLINE=1 > > /sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073# cat charger_type > host/500mA usb mode 500mA > # cat charger_adc > 42 > # cat dump_regs > 13 84 80 00 00 00 00 80 00 00 00 00 00 d3 aa 4a > 15 47 ff 01 00 07 00 00 02 08 6b 01 00 0a 1b 02 > 00 22 2f 01 00 22 00 00 3f 01 05 20 11 18 02 18 > 02 00 00 00 00 15 00 15 01 12 01 00 00 ff 3f 00 > 00 17 63 e7 28 19 ff ff 00 01 00 23 23 52 19 00 > 00 08 00 00 7e 0a 00 f2 00 26 04 17 00 28 00 09 > 7f 7f 3f 07 3f 1f ff 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 8d a2 59 0a 18 85 09 a0 08 > 11 90 03 06 00 03 00 03 e5 0e b9 5e 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > > Anything else that might have been of value :-) ? > > I'll try to reproduce tomorrow (Wifi ON, GPS ON) and check if I can > get these values out... > > > |> WLAN or GSM side would be reasonable guesses. > > | > > | How can I check what's going on to any reasonable detail that may > > | track this down for you? > > > > I can't see an easy way. > Too bad. > > > WLAN can't be disconnected from power, and the device won't stay up > > without a battery typically. > Nope, it's a V6 (AFAIK), so it doesn't stay up without a battery. > > > What I would suggest is update to something using the newer kernel and > > see if it still happens. One of the changes in the newer kernels is > > overhaul of the WLAN driver. > I've seen lots of stuff come by on the mailing list. > > > In git anyway the packaging config for the kernel has WLAN stuff as > > modules, and when you rmmod the module it should take the device down to > > its lowest power state. So that should give a way to try to point the > > finger anyway. > > OM2008.12 doesn't support a newer kernel, does it? > > I'm not against installing Qi and a 'stable' or 'tracking' kernel, > since I don't use it for 'daily use' yet... > > So, are there any steps to take to reproduce this, and/or check if it > still happens with newer kernels? > > Christ van Willegen -- William Kenworthy <bi...@iinet.net.au> Home in Perth! _______________________________________________ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
