From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 16265] Why is kslowd accumulating so much CPU time?
Date: Fri, 13 Aug 2010 19:51:20 GMT [thread overview]
Message-ID: <201008131951.o7DJpKMi025669@demeter.kernel.org> (raw)
In-Reply-To: <bug-16265-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=16265
alfonso.pola@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alfonso.pola@gmail.com
Chris Wilson <chris@chris-wilson.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |chris@chris-wilson.co.uk
--- Comment #3 from alfonso.pola@gmail.com 2010-08-12 00:15:51 ---
I'm having this problem with kernel 2.6.35.1 in archlinux. I'm willing to
provide debugging information, I just don't know what should I post. I have a
lenovo sl300 laptop with intel integrated graphics (HD4500 I believe).
--- Comment #4 from Chris Wilson <chris@chris-wilson.co.uk> 2010-08-13 08:13:45 ---
Ok, we understand what's going on here now. Every 10s the non-hotplug capable
outputs are polled for connection/disconnection events. For a certain class of
analog device on some hardware this is very slow and CPU intensive.
See also https://bugs.freedesktop.org/show_bug?id=29536
The first workaround proposed is just to disable polling via a module
parameter. The eventual solution will likely be a mix of finer grained locking
and cheaper, non-destructive polling.
--- Comment #5 from alfonso.pola@gmail.com 2010-08-13 19:51:15 ---
ok, cool.
PS: The link is http://bugs.freedesktop.org/show_bug.cgi?id=29536
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
--
next prev parent reply other threads:[~2010-08-13 19:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 19:04 [Bug 16265] New: Why is kslowd accumulating so much CPU time? bugzilla-daemon
2010-07-23 20:03 ` [Bug 16265] " bugzilla-daemon
2010-07-23 20:03 ` bugzilla-daemon
2010-07-24 13:19 ` bugzilla-daemon
2010-08-01 13:29 ` bugzilla-daemon
2010-08-01 13:29 ` bugzilla-daemon
2010-08-13 19:51 ` bugzilla-daemon [this message]
2010-09-07 6:38 ` bugzilla-daemon
2010-09-22 11:58 ` bugzilla-daemon
2011-01-12 10:48 ` bugzilla-daemon
2011-01-12 11:21 ` bugzilla-daemon
2011-01-12 11:38 ` bugzilla-daemon
2011-01-12 11:38 ` bugzilla-daemon
2011-01-15 20:43 ` bugzilla-daemon
2011-01-15 22:35 ` bugzilla-daemon
2011-01-16 9:04 ` bugzilla-daemon
2011-01-16 12:47 ` bugzilla-daemon
2011-01-16 19:46 ` bugzilla-daemon
2011-01-16 22:46 ` bugzilla-daemon
2011-01-18 18:18 ` bugzilla-daemon
2011-01-18 18:19 ` bugzilla-daemon
2011-04-09 16:48 ` bugzilla-daemon
2011-04-09 16:51 ` bugzilla-daemon
2011-04-09 17:02 ` bugzilla-daemon
2011-04-09 17:46 ` bugzilla-daemon
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=201008131951.o7DJpKMi025669@demeter.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.sourceforge.net \
/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