[Bug 12788] After suspend/resume, processor spends more time in C0 state, C3 hardly used

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

 



http://bugzilla.kernel.org/show_bug.cgi?id=12788





------- Comment #9 from theholyettlz@xxxxxxxxxxxxxx  2009-03-05 14:50 -------
I see a steady flow of interrupt 16 before and after suspend/resume, about
15/sec in both cases. I can't see anything else producing interrupts en-masse.

 16:         40       3707   IO-APIC-fasteoi   uhci_hcd:usb3, mmc0, mmc1,
iwlagn, i915@pci:0000:00:02.0

Unplugging/disabling all USB devices does not appear to solve the problem.
(Haven't tried reloading uhci driver, it's built into the kernel.)

Here's another screenshot following suspend/resume:

     PowerTOP version 1.10      (C) 2007 Intel Corporation

Cn                Avg residency       P-states (frequencies)
C0 (cpu running)        (55.1%)         2.11 Ghz     0.2%
C0                0.0ms ( 0.0%)         2.10 Ghz     0.0%
C1                0.0ms ( 0.0%)         1.60 Ghz     0.5%
C2                0.0ms (44.1%)          800 Mhz    99.3%
C3                0.0ms ( 0.7%)

Wakeups-from-idle per second : 39692.4  interval: 10.0s
no ACPI power usage estimate available

Top causes for wakeups:
  30.3% ( 38.0)       <interrupt> : acpi 
  12.6% ( 15.8)      <kernel IPI> : Rescheduling interrupts 
  12.3% ( 15.4)       <interrupt> : uhci_hcd:usb3, mmc0, mmc1,
i915@pci:0000:00:
  11.0% ( 13.8)       <interrupt> : extra timer interrupt 
   8.0% ( 10.0)           gkrellm : schedule_hrtimeout_range (hrtimer_wakeup) 
   6.7% (  8.4)       <interrupt> : ata_piix

I don't understand this at all --- it would appear to show no significant
difference in the sources of wakeups than from the first screenshot I posed in
Comment #3 --- yet claims around 200 times more wakeups in total. ...So where
are they coming from? I can't see any process hogging CPU...


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--
To unsubscribe from this list: send the line "unsubscribe cpufreq" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Devel]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Forum]     [Linux SCSI]

  Powered by Linux