Re: [lkp] [fs] df4c0e36f1: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:1]

2015-11-02 Thread Andrey Ryabinin
2015-11-02 23:07 GMT+03:00 Dave Hansen : > On 11/02/2015 11:34 AM, Andrey Ryabinin wrote: >> >> [1.159450] augmented rbtree testing -> 23675 cycles >> [1.864996] >> It took less than a second, meanwhile in your case it didn't finish in >> 22 seconds. >> >>

Re: [lkp] [fs] df4c0e36f1: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:1]

2015-11-02 Thread Dave Hansen
On 11/02/2015 11:34 AM, Andrey Ryabinin wrote: >>> >> >>> >> [1.159450] augmented rbtree testing -> 23675 cycles >>> >> [1.864996] >>> >> It took less than a second, meanwhile in your case it didn't finish in >>> >> 22 seconds. >>> >> >>> >> This makes me think that your host is overloaded

Re: [lkp] [fs] df4c0e36f1: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:1]

2015-11-02 Thread Andrey Ryabinin
2015-11-02 20:39 GMT+03:00 Dave Hansen : > On 11/02/2015 01:32 AM, Andrey Ryabinin wrote: >> And the major factor here is number 2. >> >> In your dmesg: >> [ 67.891156] rbtree testing -> 570841 cycles >> [ 88.609636] augmented rbtree testing >> [ 116.546697] NMI watchdog: BUG: soft lockup - CP

Re: [lkp] [fs] df4c0e36f1: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:1]

2015-11-02 Thread Dave Hansen
On 11/02/2015 01:32 AM, Andrey Ryabinin wrote: > And the major factor here is number 2. > > In your dmesg: > [ 67.891156] rbtree testing -> 570841 cycles > [ 88.609636] augmented rbtree testing > [ 116.546697] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! > [swapper/0:1] > > > I've

Re: [lkp] [fs] df4c0e36f1: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:1]

2015-11-02 Thread Andrey Ryabinin
2015-11-02 11:06 GMT+03:00 kernel test robot : > FYI, we noticed the below changes on > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master > commit df4c0e36f1b1782b0611a77c52cc240e5c4752dd ("fs: dcache: manually > unpoison dname after allocation to shut up kasan's reports"

Re: [lkp] [fs] df4c0e36f1: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:1]

2015-11-02 Thread Dmitry Vyukov
Hi Ying, Does testing happen with CONFIG_KASAN=y? If not, this is probably a flake caused by something else. On Mon, Nov 2, 2015 at 9:06 AM, kernel test robot wrote: > FYI, we noticed the below changes on > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master > commit df4

[lkp] [fs] df4c0e36f1: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:1]

2015-11-02 Thread kernel test robot
FYI, we noticed the below changes on https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit df4c0e36f1b1782b0611a77c52cc240e5c4752dd ("fs: dcache: manually unpoison dname after allocation to shut up kasan's reports") The commit fixed a KASan bug, but introduced or reve