From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@bugzilla.kernel.org Subject: [Bug 16265] Why is kslowd accumulating so much CPU time? Date: Fri, 13 Aug 2010 19:51:20 GMT Message-ID: <201008131951.o7DJpKMi025669@demeter.kernel.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.sourceforge.net To: dri-devel@lists.sourceforge.net List-Id: dri-devel@lists.freedesktop.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 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 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 --