2.6.24-rc1 / powertop-svn: See which USB devices causes wakeups?

[Peter Ganzhorn]

Here you go, I can't see anything else related to USB...but maybe you 
can read something out of this:

31.2% ( 20.0)     <kernel core> : usb_hcd_poll_rh_status (rh_timer_func)
  18.7% ( 12.0)       <interrupt> : iwl4965
  15.6% ( 10.0)     <kernel core> : ehci_work (ehci_watchdog)
   9.8% (  6.3)      <kernel IPI> : Rescheduling interrupts
   3.9% (  2.5)              Xorg : do_setitimer (it_real_fn)
   3.1% (  2.0)           xfsbufd : schedule_timeout (process_timeout)
   2.5% (  1.6)    wpa_supplicant : schedule_timeout (process_timeout)
   2.4% (  1.5)           fluxbox : schedule_timeout (process_timeout)
   1.6% (  1.0)              Xorg : schedule_timeout (process_timeout)
   1.6% (  1.0)               mpd : schedule_timeout (process_timeout)
   1.0% (  0.7)       firefox-bin : futex_wait (hrtimer_wakeup)
   0.7% (  0.5)       <interrupt> : libata
   0.7% (  0.5)      <kernel IPI> : function call interrupts
   0.7% (  0.5)           iwl4965 : ieee80211_sta_work (ieee80211_sta_timer)
   0.7% (  0.5)             conky : schedule_timeout (process_timeout)
   0.7% (  0.5)             conky : futex_wait (hrtimer_wakeup)
   0.7% (  0.5)             conky : sk_reset_timer (tcp_delack_timer)
   0.7% (  0.5)               mpd : sk_reset_timer (tcp_delack_timer)
   0.7% (  0.5)             conky : sk_reset_timer (tcp_write_timer)

Thanks!
Peter


Arjan van de Ven wrote:
> Peter Ganzhorn wrote:
>> Hi,
>>
>> with 2.6.24-rc1 and powertop from svn (2007-10-28) I still can't see 
>> which USB devices keeps producing wakeups:
>>
>> 49.3% ( 20.0)     <kernel core> : usb_hcd_poll_rh_status (rh_timer_func)
>>
>> I think Arjan said that with newest powertop and 2.6.24-rc* this 
>> should be possible because some patch to add this functionality was 
>> merged into 2.6.24.
>> So why can't I see which USB device is causing the wakeups or what am 
>> I doing wrong???
>>
>
> can you give like the top 10? Maybe it's there anyway
> the cause of USB stuff is listed separately, and only for devices, not 
> for the controller..
>