https://bugs.kde.org/show_bug.cgi?id=364818
Nate Graham changed:
What|Removed |Added
CC||pointedst...@zoho.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=364818
David Edmundson changed:
What|Removed |Added
Resolution|--- |WONTFIX
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=364818
--- Comment #5 from vindica...@live.com ---
At long last, I've got something to show. It's been a problem for a long time,
but either I didn't have the instructions in my notes at the time or I just
didn't have time or want to deal with it.
When I ran "
https://bugs.kde.org/show_bug.cgi?id=364818
--- Comment #4 from vindica...@live.com ---
Whoa, looking further down that thread, it gets a lot more detailed. I was
simply looking at what was marked as "Answer".
I think I'll be able to use stuff mentioned in the other answers.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=364818
--- Comment #3 from vindica...@live.com ---
Kai, can you be more specific regarding "debugging the kworker"? Does that
involve using gdb, "syscall profiling tools" or simply trial-and-error by
unplugging devices, shutting down services...?
--
You are r
https://bugs.kde.org/show_bug.cgi?id=364818
Kai Uwe Broulik changed:
What|Removed |Added
CC||k...@privat.broulik.de
--- Comment #2 from Ka
https://bugs.kde.org/show_bug.cgi?id=364818
--- Comment #1 from vindica...@live.com ---
Adding that the KDE system stat widgets also freeze with that network loss.
Also, "kworker/2:1H" (whatever that is) is the one item making one of the cpu
cores run at 100%.
Now I'm thinking that NFS may be a b
