On Mon, 9 Nov 2020 12:48:07 -0800 Dan Youngquist via tde-users <users@xxxxxxxxxxxxxxxxxx> wrote: > On 11/09/2020 12:23 PM, Slávek Banko via tde-users wrote: > > kworker, although due to the 'k' at the beginning may give the impression > > that it is related to TDE, it is a thread in the kernel. That's why it > > runs there, even if you login into XFCE. > > Just to clarify, it does not start if the system boots into XFCE. It's seen > with XFCE only if TDE was running before XFCE. It starts with TDE, whether > booted directly to TDE, or booted to XFCE and then switched to TDE. So it's > something that TDE is starting. > > > The only thing where TDE could be directly related to the kernel is if you > > have SAK turned on. In this case, a special 'event' device for capturing > > the keyboard is created there. > > I did have SAK enabled. I disabled it, rebooted, and the problem remains. https://askubuntu.com/questions/33640/kworker-what-is-it-and-why-is-it-hogging-so-much-cpu suggests that the perf tool ( https://perf.wiki.kernel.org/index.php/Main_Page ) may be able to help you diagnose this. Possibly TDE is starting some kind of timer or the like that isn't canceled when you leave, or something's being simulated in software that newer CPUs can do in hardware. E. Liddell ____________________________________________________ tde-users mailing list -- users@xxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxx Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@xxxxxxxxxxxxxxxxxx
