Alan Jenkins wrote: > On 17/12/2007, Tomas Carnecky <[EMAIL PROTECTED]> wrote: >> Oliver Neukum wrote: >>> Am Montag, 17. Dezember 2007 14:44:04 schrieb Tomas Carnecky: >>>> There is was no external usb device connected to the laptop, but the >>>> built-in fingerprint reader was, if that matters. I don't see any way to >>>> disable it, in case that causes the wakeups. >>> That matters. Find the fingerprint reader's directory in sysfs and echo >>> "auto" into power/level >>> >> That does indeed matter! Thanks. Not only did the usb rh poll function >> disappear, but I now also get 99% C3 state with an average residency of >> 100ms (or 200ms if X is running). >> >> I'm wondering why 'auto' isn't default... >> >> That leaves me with: >> - fbcon_add_cursor_timer which is called only when X is not running. >> That creates an interesting situation where with X running I get less >> wakeups per second than without X (the fbcon function fires five times >> per second, and X only adds ~2 wakeups/s). >> - xfsbufd is still there, accounting for two wakeups per second. >> - clocksource_register sometimes appears after a fresh boot, and >> disappears later, accounting for two wakeups/s. It wasn't listed before >> because I haven't rebooted the laptop, and after a few minutes that >> function disappears (or after I start something, I'm not sure). >> >> I'll look into increasing the fbcon timer and getting rid of the >> clocksource function to see if that improves my power consumption. >> Thanks so far. > > The clocksource one sounds familiar. (No-one responded to my queries > about it). My problem was caused by TSC consistency checks, which I > believe could be safely avoided. IIRC my wakeups didn't go away after > a while, so maybe your issue is different. > > Does yours default to the TSC? What happens if you change
Default is hpet. > clocksources? Does switching back to TSC cause it to start again? It's unpredictable. Now I booted the laptop and clocksource_register wasn't listed in powertop. After I echoed 'tsc' to current_clocksource, the system shortly after locked up (hard). I also tried 'jiffies' and the system locked up, too, albeit only softly, `date` stopped increasing the time, and trying to revert it back to hpet didn't work (cat current_cl.. still shows 'jiffies'). Seems like my system doesn't like me changing the clocksource. I tried rebooting a few times now, no luck getting clocksource_register back into powertop. Btw, that function is executed at a fixed HZ/2 rate if 'watchdog_list' is non-empty. And it seems that every clocksource that can be used as a clocksource watchdog is added to that list. That's about how I understand the code. So why the function is listed only sometimes in powertop is a mystery to me. tom _______________________________________________ Discuss mailing list [email protected] http://mail.lesswatts.org/mailman/listinfo/discuss
