Bug 786665
Summary: | Sandybridge laptop seeing lots of wakeups | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Amit Shah <amit.shah> | ||||||||||
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||||
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||
Priority: | unspecified | ||||||||||||
Version: | 16 | CC: | amit.shah, gansalmon, itamar, jforbes, jonathan, kernel-maint, madhu.chinakonda | ||||||||||
Target Milestone: | --- | ||||||||||||
Target Release: | --- | ||||||||||||
Hardware: | Unspecified | ||||||||||||
OS: | Unspecified | ||||||||||||
Whiteboard: | |||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2012-11-14 15:20:54 UTC | Type: | --- | ||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||
Documentation: | --- | CRM: | |||||||||||
Verified Versions: | Category: | --- | |||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
Embargoed: | |||||||||||||
Attachments: |
|
Description
Amit Shah
2012-02-02 05:06:52 UTC
10678 pkts/s Device nic:ppp0 so what happens when it isn't receiving packets ? This is with the 3G modem disconnected, and no network activity at all. Summary: 314.3 wakeups/second, 0.0 GPU ops/second and 0.0 VFS ops/sec Usage Events/s Category Description 4018 rpm Device Laptop fan 53.3% Device Display backlight 2.9 ms/s 6.2 Process gnome-shell --sm-client-id 1080b1eb1a6c16a69a 2.0 ms/s 49.9 Process /usr/lib64/firefox/firefox you're still not measuring an idle desktop, so these numbers are meaningless. idle means nothing running. especially things like firefox. Created attachment 561177 [details]
Powertop report on init 3
Created attachment 561178 [details]
powertop output on init 5 with new user account
Ow, sorry. I meant to also include stats from an X200 with a similar workload with much lesser number of wakeups. Can't get that info right away, so attaching two powertop-generated reports here.
I booted this laptop with 'init 3' and generated a powertop html report after optimising the tunables that were set to 'bad'. Wakeups are at below 30 per sec.
I then created a new user account, switched to init 5, opened a terminal and ran the same powertop command. Wakeups are now at 150+.
When I login to my user acct, with multiple apps restored after login, wakeups are back at 400+.
With the X200, init 3 has 8 wakeups/sec, init 5 has 25 wakeups (what the sandybridge laptop has in init 3 mode). The x200 laptop runs 3.1.5 instead of 3.2.5 of the sandybridge here, but I doubt that's going to change anything. I'm suspecting it's the GPU in the sandybridge that's causing this. Created attachment 562207 [details]
powertop report on x200, init 3
Created attachment 562208 [details]
x200 powertop report in init 5 mode, new user account
the only power related gpu thing for sandybridge is that rc6 is disabled by default. There's an i915_enable_rc6 option to i915.ko to turn it on. We can't turn it on by default because it makes some systems lock up. [mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update. [mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update. [mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update. Problem continues on 3.3.0 # Mass update to all open bugs. Kernel 3.6.2-1.fc16 has just been pushed to updates. This update is a significant rebase from the previous version. Please retest with this kernel, and let us know if your problem has been fixed. In the event that you have upgraded to a newer release and the bug you reported is still present, please change the version field to the newest release you have encountered the issue with. Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered. If you are not the original bug reporter and you still experience this bug, please file a new report, as it is possible that you may be seeing a different problem. (Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient). With no response, we are closing this bug under the assumption that it is no longer an issue. If you still experience this bug, please feel free to reopen the bug report. |