From: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: john stultz <johnstul@us.ibm.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
LKML <linux-kernel@vger.kernel.org>,
Oleg Nesterov <oleg@redhat.com>
Subject: Re: rcu stalls seen with numasched_v2 patches applied.
Date: Thu, 16 Aug 2012 22:46:09 +0530 [thread overview]
Message-ID: <20120816171609.GA25338@linux.vnet.ibm.com> (raw)
In-Reply-To: <1344845488.31459.10.camel@twins>
* Peter Zijlstra <peterz@infradead.org> [2012-08-13 10:11:28]:
> On Mon, 2012-08-13 at 09:51 +0200, Peter Zijlstra wrote:
> > On Fri, 2012-08-10 at 21:54 +0530, Srikar Dronamraju wrote:
> >
> > > This change worked well on the 2 node machine
> > > but on the 8 node machine it hangs with repeated messages
> > >
> > > Pid: 60935, comm: numa01 Tainted: G W 3.5.0-numasched_v2_020812+ #4
> > > Call Trace:
> > > <IRQ> [<ffffffff810d32e2>] ? rcu_check_callback s+0x632/0x650
> > > [<ffffffff81061bb8>] ? update_process_times+0x48/0x90
> > > [<ffffffff810a2a4e>] ? tick_sched_timer+0x6e/0xe0
> > > [<ffffffff81079c85>] ? __run_hrtimer+0x75/0x1a0
> > > [<ffffffff810a29e0>] ? tick_setup_sched_timer+0x100/0x100
> > > [<ffffffff8107a036>] ? hrtimer_interrupt+0xf6/0x250
> > > [<ffffffff814f1379>] ? smp_apic_timer_interrupt+0x69/0x99
> > > [<ffffffff814f034a>] ? apic_timer_interrupt+0x6a/0x70
> > > <EOI> [<ffffffff811082e3>] ? wait_on_page_bit+0x73/0x80
> > > [<ffffffff814e7992>] ? _raw_spin_lock+0x22/0x30
> > > [<ffffffff81131bf3>] ? handle_pte_fault+0x1b3/0xca0
> > > [<ffffffff814e64f7>] ? __schedule+0x2e7/0x710
> > > [<ffffffff8107a9a8>] ? up_read+0x18/0x30
> > > [<ffffffff814eb2be>] ? do_page_fault+0x13e/0x460
> > > [<ffffffff810137ba>] ? __switch_to+0x1aa/0x460
> > > [<ffffffff814e64f7>] ? __schedule+0x2e7/0x710
> > > [<ffffffff814e7de5>] ? page_fault+0x25/0x30
> > > { 3} (t=62998 jiffies)
> > >
> >
> > If you run a -tip kernel without the numa patches, does that work?
>
>
> n/m, I found a total brain-fart in there.. does the below sort it?
>
> ---
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -917,7 +917,7 @@ void task_numa_work(struct callback_head
> t = p;
> do {
> sched_setnode(t, node);
> - } while ((t = next_thread(p)) != p);
> + } while ((t = next_thread(t)) != p);
> rcu_read_unlock();
> }
>
>
I tried this fix, but doesnt seem to help.
will try on -tip and revert.
--
thanks and regards
srikar
next prev parent reply other threads:[~2012-08-16 17:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 12:33 rcu stalls seen with numasched_v2 patches applied Srikar Dronamraju
2012-08-07 13:52 ` Peter Zijlstra
2012-08-07 17:19 ` Srikar Dronamraju
2012-08-08 19:58 ` Peter Zijlstra
2012-08-10 16:24 ` Srikar Dronamraju
2012-08-13 7:51 ` Peter Zijlstra
2012-08-13 8:11 ` Peter Zijlstra
2012-08-16 17:16 ` Srikar Dronamraju [this message]
2012-08-17 5:23 ` Srikar Dronamraju
2012-08-07 17:08 ` John Stultz
2012-08-07 16:59 ` Srikar Dronamraju
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120816171609.GA25338@linux.vnet.ibm.com \
--to=srikar@linux.vnet.ibm.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox