On Tue, Jul 30, 2013 at 10:57:18AM -0700, Paul E. McKenney wrote:
> On Fri, Jul 19, 2013 at 08:32:12PM -0400, Dave Jones wrote:
> > On Fri, Jul 19, 2013 at 03:15:39PM -0700, Paul E. McKenney wrote:
> > > On Fri, Jul 19, 2013 at 10:53:23AM -0400, Dave Jones wrote:
> > > > My fuzz tester keeps
On Fri, Jul 19, 2013 at 08:32:12PM -0400, Dave Jones wrote:
> On Fri, Jul 19, 2013 at 03:15:39PM -0700, Paul E. McKenney wrote:
> > On Fri, Jul 19, 2013 at 10:53:23AM -0400, Dave Jones wrote:
> > > My fuzz tester keeps hitting this. Every instance shows the non-irq stack
> > > came in from mlock
On Fri, Jul 19, 2013 at 08:32:12PM -0400, Dave Jones wrote:
> On Fri, Jul 19, 2013 at 03:15:39PM -0700, Paul E. McKenney wrote:
> > On Fri, Jul 19, 2013 at 10:53:23AM -0400, Dave Jones wrote:
> > > My fuzz tester keeps hitting this. Every instance shows the non-irq stack
> > > came in from mlock
On Fri, Jul 19, 2013 at 03:15:39PM -0700, Paul E. McKenney wrote:
> On Fri, Jul 19, 2013 at 10:53:23AM -0400, Dave Jones wrote:
> > My fuzz tester keeps hitting this. Every instance shows the non-irq stack
> > came in from mlockall. I'm only seeing this on one box, but that has more
> > ram (8
On Fri, Jul 19, 2013 at 10:53:23AM -0400, Dave Jones wrote:
> My fuzz tester keeps hitting this. Every instance shows the non-irq stack
> came in from mlockall. I'm only seeing this on one box, but that has more
> ram (8gb) than my other machines, which might explain it.
Are you building CONFIG_P
My fuzz tester keeps hitting this. Every instance shows the non-irq stack
came in from mlockall. I'm only seeing this on one box, but that has more
ram (8gb) than my other machines, which might explain it.
Dave
INFO: rcu_preempt self-detected stall on CPU { 3} (t=6500 jiffies g=470344
6 matches
Mail list logo