From: "David H. Durgee" <dhdurgee@verizon.net>
To: linux-kernel@vger.kernel.org
Subject: Request for assistance - excessive kworker CPU wakeups
Date: Fri, 09 Dec 2011 16:27:04 -0500 [thread overview]
Message-ID: <4EE27D28.4040909@verizon.net> (raw)
I recently purchased a Lenovo IdeaPad Z560, model 09143YU, and as I am
not a Windows fan I installed Linux Mint 11 Katya x64 to use instead of
the supplied W7. I was encountering a known hang and had to upgrade to
a later kernel, so I am now using the 2.6.38-11-generic #50-Ubuntu SMP
Mon Sep 12 21:17:25 UTC 2011 x86_64 kernel.
I had my first occasion to use the laptop for an extended period for the
first time over the Thanksgiving holiday and I found it needed to be
tuned. I downloaded powertop and used it to discover where my problems
were. After addressing excessive i915 interrupts due to DRI the next
most frequent cause of CPU wakeups is a kworker on the system. A search
lead to a post by Tejun, indicating the need to trace such issues.
Running the trace showed that 1933 of 2748 events were of the form:
<idle>-0 [000] 22005.355346: workqueue_queue_work: work
struct=ffff8800bb411188 function=do_dbs_timer workqueue=ffff88012b5d2c00
req_cpu=0 cpu=0
Tejun indicated that this is a workitem used by cpufreq and likely
caused by something else hitting the CPU frequently. So how do I
diagnose this further and isolate the cause for correction?
If you would like a summary of this, download this spreadsheet:
http://home.comcast.net/%7Eddurgee/Tracelog.ods
If you would like to inspect the trace log itself:
http://home.comcast.net/%7Eddurgee/tracelog.zip
Dave
next reply other threads:[~2011-12-09 21:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 21:27 David H. Durgee [this message]
2012-01-25 17:44 ` Mandeep Singh Baines
2012-01-25 18:56 ` David H. Durgee
2012-01-25 23:44 ` Mandeep Singh Baines
2012-01-26 0:31 ` David H. Durgee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EE27D28.4040909@verizon.net \
--to=dhdurgee@verizon.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome