Re: [arch-general] Help diagnosing kworker 'bug'

2014-08-24 Thread Oon-Ee Ng
On Sat, Aug 9, 2014 at 11:18 AM, Anatol Pomozov wrote: > Hi > > Another way to get more information about this problem is to use > kernel traces. Let's enable block and writeback events: > > sudo su > cd /sys/kernel/debug/tracing > echo 1 > events/writeback/enable > echo 1 > events/block/enable >

Re: [arch-general] Help diagnosing kworker 'bug'

2014-08-08 Thread Anatol Pomozov
Hi On Fri, Aug 8, 2014 at 6:58 PM, Oon-Ee Ng wrote: > On Wed, Aug 6, 2014 at 3:43 PM, Oon-Ee Ng wrote: >> On Wed, Aug 6, 2014 at 10:40 AM, Anatol Pomozov >> wrote: >>> 'perf' is a great and very powerful tool that allow to debug problems >>> like this. Run '# perf top -g -p $PID' and it will sh

Re: [arch-general] Help diagnosing kworker 'bug'

2014-08-08 Thread Oon-Ee Ng
On Wed, Aug 6, 2014 at 3:43 PM, Oon-Ee Ng wrote: > On Wed, Aug 6, 2014 at 10:40 AM, Anatol Pomozov > wrote: >> 'perf' is a great and very powerful tool that allow to debug problems >> like this. Run '# perf top -g -p $PID' and it will show where the >> process spends *cpu cycles*. It should be en

Re: [arch-general] Help diagnosing kworker 'bug'

2014-08-06 Thread Oon-Ee Ng
On Wed, Aug 6, 2014 at 10:40 AM, Anatol Pomozov wrote: > Hi > > On Tue, Aug 5, 2014 at 4:37 PM, Oon-Ee Ng wrote: >> This is after roughly 6-7 seconds, and 65 MB has already been written >> by that kworker thread. > > How long this IO activity takes? Could it be some kind of automatic > defragment

Re: [arch-general] Help diagnosing kworker 'bug'

2014-08-05 Thread Anatol Pomozov
Hi On Tue, Aug 5, 2014 at 4:37 PM, Oon-Ee Ng wrote: > 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

Re: [arch-general] Help diagnosing kworker 'bug'

2014-08-05 Thread Oon-Ee Ng
On Wed, Aug 6, 2014 at 7:37 AM, Oon-Ee Ng wrote: > 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. And I made it back alive. 3.15.8-1 does not have the same problem. Also downgraded bbs

[arch-general] Help diagnosing kworker 'bug'

2014-08-05 Thread Oon-Ee Ng
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