[arch-general] Help diagnosing kworker 'bug'
ngoonee.talk at gmail.com
Tue Aug 5 19:37:16 EDT 2014
Yesterday night I noticed (just before performing an update my conky
showing high continuous writing to root. iotop -Pa shows this:-
Total DISK READ : 0.00 B/s | Total DISK WRITE : 8.93 M/s
Actual DISK READ: 0.00 B/s | Actual DISK WRITE: 11.06 M/s
PID PRIO USER DISK READ DISK WRITE SWAPIN IO> COMMAND
112 be/4 root 0.00 B 64.91 M 0.00 % 24.34 % [kworker/u16:3]
11936 be/4 root 0.00 B 0.00 B 0.00 % 0.06 % [kworker/1:1]
28794 be/4 root 0.00 B 36.00 K 0.00 % 0.00 % [kworker/u16:1]
This is after roughly 6-7 seconds, and 65 MB has already been written
by that kworker thread.
As I said, this was already happening before an upgrade. I ran the
upgrade anyway, which upgraded linux to 3.16-2, and still got the same
thing. Yes, I'm using [testing].
Any ideas on how to proceed? Next thing I'm going to try is
downgrading linux to 3.15, but I thought I'd post this here first in
case I don't make it back.
More information about the arch-general