linux-kernel - kworker thread eating CPU time in 3.3-rc1

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 for Android: free password hash cracker in your pocket

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

Date:	Fri, 20 Jan 2012 13:33:24 +0900
From:	Norbert Preining <preining@...ic.at>
To:	linux-kernel@...r.kernel.org
Subject: kworker thread eating CPU time in 3.3-rc1

Dear all,

(please cc)

today I switched from 3.2 to 3.3-rc1 and now I have permanently
2 kworker threads each eating up 10-20% CPU time, which seems a bit
exaggerated, comparted to all the rest at below or around 1%.
There is nothing really crazy running, just a gnome3 desktop, firefox,
nothing fancy.

Any idea where this might come from?

Please let me know if you need more information.

Best wishes

Norbert
------------------------------------------------------------------------
Norbert Preining            preining@...ist.ac.jp, logic.at, debian.org}
JAIST, Japan                                 TeX Live & Debian Developer
DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
------------------------------------------------------------------------
HASSOP (n.)
The pocket down the back of an armchair used for storing two-shilling
bits and pieces of Lego.
			--- Douglas Adams, The Meaning of Liff
--
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/