Re: [slab] a1fd55538c: WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2601 trace_hardirqs_on_caller()

2016-03-01 Thread Andrew Morton
On Thu, 28 Jan 2016 22:52:55 +0800 kernel test robot wrote: > Greetings, > > 0day kernel testing robot got the below dmesg and the first bad commit is > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master > > commit

Re: [slab] a1fd55538c: WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2601 trace_hardirqs_on_caller()

2016-03-01 Thread Andrew Morton
On Thu, 28 Jan 2016 22:52:55 +0800 kernel test robot wrote: > Greetings, > > 0day kernel testing robot got the below dmesg and the first bad commit is > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master > > commit a1fd55538cae9f411059c9b067a3d48c41aa876b > Author:

[slab] a1fd55538c: WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2601 trace_hardirqs_on_caller()

2016-03-01 Thread kernel test robot
This is a multi-part message in MIME format. Greetings, 0day kernel testing robot got the below dmesg and the first bad commit is https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master commit a1fd55538cae9f411059c9b067a3d48c41aa876b Author: Jesper Dangaard Brouer

[slab] a1fd55538c: WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2601 trace_hardirqs_on_caller()

2016-03-01 Thread kernel test robot
This is a multi-part message in MIME format. Greetings, 0day kernel testing robot got the below dmesg and the first bad commit is https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master commit a1fd55538cae9f411059c9b067a3d48c41aa876b Author: Jesper Dangaard Brouer

[slab] a1fd55538c: WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2601 trace_hardirqs_on_caller()

2016-02-23 Thread kernel test robot
This is a multi-part message in MIME format. Greetings, 0day kernel testing robot got the below dmesg and the first bad commit is https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master commit a1fd55538cae9f411059c9b067a3d48c41aa876b Author: Jesper Dangaard Brouer

[slab] a1fd55538c: WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2601 trace_hardirqs_on_caller()

2016-02-23 Thread kernel test robot
This is a multi-part message in MIME format. Greetings, 0day kernel testing robot got the below dmesg and the first bad commit is https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master commit a1fd55538cae9f411059c9b067a3d48c41aa876b Author: Jesper Dangaard Brouer

Re: [slab] a1fd55538c: WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2601 trace_hardirqs_on_caller()

2016-02-02 Thread Valdis . Kletnieks
On Mon, 01 Feb 2016 07:34:22 +1100, Stephen Rothwell said: > Hi Jesper, > > [PATCH] mm: temporary fix for SLAB in linux-next > > > > From: Jesper Dangaard Brouer > > > > This is only for linux-next, until AKPM pickup fixes two patches: > > base url: http://ozlabs.org/~akpm/mmots/broken-out/ > >

Re: [slab] a1fd55538c: WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2601 trace_hardirqs_on_caller()

2016-02-02 Thread Valdis . Kletnieks
On Mon, 01 Feb 2016 07:34:22 +1100, Stephen Rothwell said: > Hi Jesper, > > [PATCH] mm: temporary fix for SLAB in linux-next > > > > From: Jesper Dangaard Brouer > > > > This is only for linux-next, until AKPM pickup fixes two patches: > > base url:

Re: [slab] a1fd55538c: WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2601 trace_hardirqs_on_caller()

2016-01-31 Thread Stephen Rothwell
Hi Jesper, On Sun, 31 Jan 2016 19:40:48 +0100 Jesper Dangaard Brouer wrote: > > On Sun, 31 Jan 2016 13:15:06 +1100 > Stephen Rothwell wrote: > > > On Sat, 30 Jan 2016 18:46:46 +0100 Jesper Dangaard Brouer > > wrote: > > > > > > Let me know, if the linux-next tree need's an explicit fix?

Re: [slab] a1fd55538c: WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2601 trace_hardirqs_on_caller()

2016-01-31 Thread Jesper Dangaard Brouer
On Sun, 31 Jan 2016 13:15:06 +1100 Stephen Rothwell wrote: > Hi Jesper, > > On Sat, 30 Jan 2016 18:46:46 +0100 Jesper Dangaard Brouer > wrote: > > > > Let me know, if the linux-next tree need's an explicit fix? > > It would be a good idea if you could send a fix against linux-next to > me

Re: [slab] a1fd55538c: WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2601 trace_hardirqs_on_caller()

2016-01-31 Thread Stephen Rothwell
Hi Jesper, On Sun, 31 Jan 2016 19:40:48 +0100 Jesper Dangaard Brouer wrote: > > On Sun, 31 Jan 2016 13:15:06 +1100 > Stephen Rothwell wrote: > > > On Sat, 30 Jan 2016 18:46:46 +0100 Jesper Dangaard Brouer > > wrote: > > > > > >

Re: [slab] a1fd55538c: WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2601 trace_hardirqs_on_caller()

2016-01-31 Thread Jesper Dangaard Brouer
On Sun, 31 Jan 2016 13:15:06 +1100 Stephen Rothwell wrote: > Hi Jesper, > > On Sat, 30 Jan 2016 18:46:46 +0100 Jesper Dangaard Brouer > wrote: > > > > Let me know, if the linux-next tree need's an explicit fix? > > It would be a good idea if you

Re: [slab] a1fd55538c: WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2601 trace_hardirqs_on_caller()

2016-01-30 Thread Stephen Rothwell
Hi Jesper, On Sat, 30 Jan 2016 18:46:46 +0100 Jesper Dangaard Brouer wrote: > > Let me know, if the linux-next tree need's an explicit fix? It would be a good idea if you could send a fix against linux-next to me as Andrew is currently travelling. -- Cheers, Stephen Rothwell

Re: [slab] a1fd55538c: WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2601 trace_hardirqs_on_caller()

2016-01-30 Thread Jesper Dangaard Brouer
On Sat, 30 Jan 2016 02:09:30 -0500 valdis.kletni...@vt.edu wrote: > On Thu, 28 Jan 2016 18:47:49 +0100, Jesper Dangaard Brouer said: > > I cannot reproduce below problem... have enabled all kind of debugging > > and also lockdep. > > > > Can I get a version of the .config file used? > > I'm

Re: [slab] a1fd55538c: WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2601 trace_hardirqs_on_caller()

2016-01-30 Thread Jesper Dangaard Brouer
On Sat, 30 Jan 2016 02:09:30 -0500 valdis.kletni...@vt.edu wrote: > On Thu, 28 Jan 2016 18:47:49 +0100, Jesper Dangaard Brouer said: > > I cannot reproduce below problem... have enabled all kind of debugging > > and also lockdep. > > > > Can I get a version of the .config file used? > > I'm

Re: [slab] a1fd55538c: WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2601 trace_hardirqs_on_caller()

2016-01-30 Thread Stephen Rothwell
Hi Jesper, On Sat, 30 Jan 2016 18:46:46 +0100 Jesper Dangaard Brouer wrote: > > Let me know, if the linux-next tree need's an explicit fix? It would be a good idea if you could send a fix against linux-next to me as Andrew is currently travelling. -- Cheers, Stephen

Re: [slab] a1fd55538c: WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2601 trace_hardirqs_on_caller()

2016-01-29 Thread Valdis . Kletnieks
On Thu, 28 Jan 2016 18:47:49 +0100, Jesper Dangaard Brouer said: > I cannot reproduce below problem... have enabled all kind of debugging > and also lockdep. > > Can I get a version of the .config file used? I'm not the 0day bot, but my laptop hits the same issue at boot. .config follows.. # #

Re: [slab] a1fd55538c: WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2601 trace_hardirqs_on_caller()

2016-01-29 Thread Valdis . Kletnieks
On Thu, 28 Jan 2016 18:47:49 +0100, Jesper Dangaard Brouer said: > I cannot reproduce below problem... have enabled all kind of debugging > and also lockdep. > > Can I get a version of the .config file used? I'm not the 0day bot, but my laptop hits the same issue at boot. .config follows.. # #

Re: [slab] a1fd55538c: WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2601 trace_hardirqs_on_caller()

2016-01-28 Thread Jesper Dangaard Brouer
Hi, I cannot reproduce below problem... have enabled all kind of debugging and also lockdep. Can I get a version of the .config file used? --Jesper On Thu, 28 Jan 2016 22:52:55 +0800 kernel test robot wrote: > Greetings, > > 0day kernel testing robot got the below dmesg and the first bad

[slab] a1fd55538c: WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2601 trace_hardirqs_on_caller()

2016-01-28 Thread kernel test robot
This is a multi-part message in MIME format. Greetings, 0day kernel testing robot got the below dmesg and the first bad commit is https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master commit a1fd55538cae9f411059c9b067a3d48c41aa876b Author: Jesper Dangaard Brouer

Re: [slab] a1fd55538c: WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2601 trace_hardirqs_on_caller()

2016-01-28 Thread Jesper Dangaard Brouer
Hi, I cannot reproduce below problem... have enabled all kind of debugging and also lockdep. Can I get a version of the .config file used? --Jesper On Thu, 28 Jan 2016 22:52:55 +0800 kernel test robot wrote: > Greetings, > > 0day kernel testing robot got the below

[slab] a1fd55538c: WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2601 trace_hardirqs_on_caller()

2016-01-28 Thread kernel test robot
This is a multi-part message in MIME format. Greetings, 0day kernel testing robot got the below dmesg and the first bad commit is https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master commit a1fd55538cae9f411059c9b067a3d48c41aa876b Author: Jesper Dangaard Brouer