linux-kernel - Why is kslowd accumulating so much CPU time?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <E1OMQ88-0002a1-Gb@closure.thunk.org>
Date:	Wed, 09 Jun 2010 14:36:00 -0400
From:	"Theodore Ts'o" <tytso@....edu>
To:	Dave Airlie <airlied@...hat.com>,
	David Howells <dhowells@...hat.com>
cc:	linux-kernel@...r.kernel.org
Subject: Why is kslowd accumulating so much CPU time?

My laptop is running 2.6.35-rc2 (plus a few patches) and after not quite
four hours of beeing booted (3:45 to be precise), top shows that kslowd
has accumulated as surprising amount of CPU time.  From top display:

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
 6173 root      15  -5     0    0    0 S    6  0.0  10:42.91 kslowd001
 1219 root      15  -5     0    0    0 S    5  0.0  11:00.68 kslowd000
 1765 root      15  -5     0    0    0 S    5  0.0  10:59.20 kslowd002
 6784 root      15  -5     0    0    0 S    4  0.0  10:34.37 kslowd003
 4946 root      20   0  144m  34m  17m S    3  0.9   2:24.62 Xorg

This came up because I was trying to figure out why mouse response was
being so jerky.  There aren't that many users of slow-work, and given
that I'm not using cifs, fscache, gfs2, my suspicions are falling on
drivers/gpu/drm/drm_crtc_helper.c (Would this be something that would be
in use on a Lenovo T400 laptop?)

Is there any way to easily see what is scheduling themselves to use the
slow workqueue?

Thanks,

						- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/