On Fri, Mar 20, 2015 at 10:46:33AM -0400, Sasha Levin wrote:
> On 03/20/2015 10:29 AM, Paul E. McKenney wrote:
> > On Fri, Mar 20, 2015 at 10:15:34AM -0400, Sasha Levin wrote:
> >> On 03/15/2015 08:02 PM, Paul E. McKenney wrote:
> >>> On Sun, Mar 15, 2015 at 07:32:32PM -0400, Sasha Levin wrote:
> >
On 03/20/2015 10:29 AM, Paul E. McKenney wrote:
> On Fri, Mar 20, 2015 at 10:15:34AM -0400, Sasha Levin wrote:
>> On 03/15/2015 08:02 PM, Paul E. McKenney wrote:
>>> On Sun, Mar 15, 2015 at 07:32:32PM -0400, Sasha Levin wrote:
> On 03/15/2015 04:43 PM, Paul E. McKenney wrote:
>>> But I did
On Fri, Mar 20, 2015 at 10:15:34AM -0400, Sasha Levin wrote:
> On 03/15/2015 08:02 PM, Paul E. McKenney wrote:
> > On Sun, Mar 15, 2015 at 07:32:32PM -0400, Sasha Levin wrote:
> >> > On 03/15/2015 04:43 PM, Paul E. McKenney wrote:
> >>> > > But I did find a bug that would result in the other warnin
On 03/15/2015 08:02 PM, Paul E. McKenney wrote:
> On Sun, Mar 15, 2015 at 07:32:32PM -0400, Sasha Levin wrote:
>> > On 03/15/2015 04:43 PM, Paul E. McKenney wrote:
>>> > > But I did find a bug that would result in the other warnings, and could
>>> > > also result in too-short grace periods, which c
On Sun, Mar 15, 2015 at 07:32:32PM -0400, Sasha Levin wrote:
> On 03/15/2015 04:43 PM, Paul E. McKenney wrote:
> > But I did find a bug that would result in the other warnings, and could
> > also result in too-short grace periods, which could in turn result in
> > arbitrarily arbitrary misbehavior.
On 03/15/2015 04:43 PM, Paul E. McKenney wrote:
> But I did find a bug that would result in the other warnings, and could
> also result in too-short grace periods, which could in turn result in
> arbitrarily arbitrary misbehavior. The patch below, which is also on
> its way into -next, should fix
On Fri, Mar 13, 2015 at 10:39:43AM -0700, Paul E. McKenney wrote:
> On Thu, Mar 12, 2015 at 07:07:49AM -0700, Paul E. McKenney wrote:
> > On Thu, Mar 12, 2015 at 08:32:05AM -0400, Sasha Levin wrote:
> > > On 03/12/2015 08:28 AM, Sasha Levin wrote:
> > > > On 03/11/2015 07:16 PM, Paul E. McKenney wr
On Thu, Mar 12, 2015 at 07:07:49AM -0700, Paul E. McKenney wrote:
> On Thu, Mar 12, 2015 at 08:32:05AM -0400, Sasha Levin wrote:
> > On 03/12/2015 08:28 AM, Sasha Levin wrote:
> > > On 03/11/2015 07:16 PM, Paul E. McKenney wrote:
> > >> > On Wed, Mar 11, 2015 at 07:06:40PM -0400, Sasha Levin wrote:
On Thu, Mar 12, 2015 at 08:32:05AM -0400, Sasha Levin wrote:
> On 03/12/2015 08:28 AM, Sasha Levin wrote:
> > On 03/11/2015 07:16 PM, Paul E. McKenney wrote:
> >> > On Wed, Mar 11, 2015 at 07:06:40PM -0400, Sasha Levin wrote:
> >> > On 03/11/2015 07:01 PM, Paul E. McKenney wrote:
> >>
On 03/12/2015 08:28 AM, Sasha Levin wrote:
> On 03/11/2015 07:16 PM, Paul E. McKenney wrote:
>> > On Wed, Mar 11, 2015 at 07:06:40PM -0400, Sasha Levin wrote:
>> > On 03/11/2015 07:01 PM, Paul E. McKenney wrote:
> >> With the commit I didn't hit it yet, but I do see 4
>
On 03/11/2015 07:16 PM, Paul E. McKenney wrote:
> On Wed, Mar 11, 2015 at 07:06:40PM -0400, Sasha Levin wrote:
>> > On 03/11/2015 07:01 PM, Paul E. McKenney wrote:
> >> With the commit I didn't hit it yet, but I do see 4 different
> >> WARNings:
>>> > > I wish that I could say that I am
On Wed, Mar 11, 2015 at 07:06:40PM -0400, Sasha Levin wrote:
> On 03/11/2015 07:01 PM, Paul E. McKenney wrote:
> >> With the commit I didn't hit it yet, but I do see 4 different WARNings:
> > I wish that I could say that I am surprised, but the sad fact is that
> > I am still shaking the bugs out.
On 03/11/2015 07:01 PM, Paul E. McKenney wrote:
>> With the commit I didn't hit it yet, but I do see 4 different WARNings:
> I wish that I could say that I am surprised, but the sad fact is that
> I am still shaking the bugs out.
I have one more to add:
[ 93.330539] WARNING: CPU: 1 PID: 8 at
On Wed, Mar 11, 2015 at 06:18:57PM -0400, Sasha Levin wrote:
> On 03/11/2015 04:41 PM, Paul E. McKenney wrote:
> > Aha, I forgot to update rcu/next. I have now updated it, so it should
> > make it there today or tomorrow. In the meantime, does the following
> > commit help?
> >
> > Also, how qui
On 03/11/2015 04:41 PM, Paul E. McKenney wrote:
> Aha, I forgot to update rcu/next. I have now updated it, so it should
> make it there today or tomorrow. In the meantime, does the following
> commit help?
>
> Also, how quickly does your test setup reproduce this?
I usually hit it within an hou
On Wed, Mar 11, 2015 at 04:18:49PM -0400, Sasha Levin wrote:
> On 03/11/2015 04:17 PM, Paul E. McKenney wrote:
> > On Wed, Mar 11, 2015 at 03:57:32PM -0400, Sasha Levin wrote:
> >> Hi all,
> >>
> >> I've started seeing the following hang pretty often during my fuzzing. The
> >> system proceeds to l
On 03/11/2015 04:17 PM, Paul E. McKenney wrote:
> On Wed, Mar 11, 2015 at 03:57:32PM -0400, Sasha Levin wrote:
>> Hi all,
>>
>> I've started seeing the following hang pretty often during my fuzzing. The
>> system proceeds to lock up after that.
>>
>> [ 3209.655703] INFO: rcu_preempt detected stalls
On Wed, Mar 11, 2015 at 03:57:32PM -0400, Sasha Levin wrote:
> Hi all,
>
> I've started seeing the following hang pretty often during my fuzzing. The
> system proceeds to lock up after that.
>
> [ 3209.655703] INFO: rcu_preempt detected stalls on CPUs/tasks:
> [ 3209.655703]Tasks blocked
Hi all,
I've started seeing the following hang pretty often during my fuzzing. The
system proceeds to lock up after that.
[ 3209.655703] INFO: rcu_preempt detected stalls on CPUs/tasks:
[ 3209.655703] Tasks blocked on level-1 rcu_node (CPUs 16-31):
[ 3209.655703] (detected by 0, t=30502 jiffies
19 matches
Mail list logo
