linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gautham R Shenoy <ego@in.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Sachin Sant <sachinp@in.ibm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
	Mike Galbraith <efault@gmx.de>
Subject: Re: -next: Nov 12 - kernel BUG at kernel/sched.c:7359!
Date: Fri, 13 Nov 2009 15:28:01 +0530	[thread overview]
Message-ID: <20091113095801.GA29977@in.ibm.com> (raw)
In-Reply-To: <1258045831.4039.736.camel@laptop>

On Thu, Nov 12, 2009 at 06:10:31PM +0100, Peter Zijlstra wrote:
> 
> diff --git a/kernel/sched.c b/kernel/sched.c
> index 1f2e99d..62df61c 100644
> --- a/kernel/sched.c
> +++ b/kernel/sched.c
> @@ -2377,6 +2377,9 @@ static int try_to_wake_up(struct task_struct *p, unsigned int state,
>  	task_rq_unlock(rq, &flags);
> 

How about this ?

again:
  	cpu = p->sched_class->select_task_rq(p, SD_BALANCE_WAKE, wake_flags);
 	if (!cpu_online(cpu))
 		cpu = cpumask_any_and(&p->cpus_allowed, cpu_active_mask);
	if (!cpu) {
		set_task_affinity(); 
		goto again;
	}
> +
>  	if (cpu != orig_cpu) {
>  		local_irq_save(flags);
>  		rq = cpu_rq(cpu);

Will it help further narrow down the window ?
> 
> 
> Something I think Mike also tried and didn't deadlock for him..
> 
> Sachin, Mike, could you try the above snippet and verify if it does
> indeed solve your respective issues?
> 
> /me prays it does, because otherwise I'm fresh out of clue...

-- 
Thanks and Regards
gautham

  parent reply	other threads:[~2009-11-13  9:57 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-12  8:51 linux-next: Tree for November 12 Stephen Rothwell
2009-11-12 11:53 ` -next: Nov 12 - kernel BUG at kernel/sched.c:7359! Sachin Sant
2009-11-12 12:10   ` Peter Zijlstra
2009-11-12 12:23     ` Sachin Sant
2009-11-12 12:27       ` Peter Zijlstra
2009-11-12 17:10         ` Peter Zijlstra
2009-11-13  9:00           ` Sachin Sant
2009-11-13  9:06             ` Peter Zijlstra
2009-11-13  9:58           ` Gautham R Shenoy [this message]
2009-11-13 10:16             ` Peter Zijlstra
2009-11-13 10:31               ` Peter Zijlstra
2009-11-13 10:49                 ` Peter Zijlstra
2009-11-13 11:44                 ` Sachin Sant
2009-11-13 16:12                 ` Mike Galbraith
2009-11-23  9:53                 ` Sachin Sant
2009-11-25 13:42                   ` Peter Zijlstra
2009-11-26  4:39                     ` Sachin Sant
2009-12-04 12:06                     ` Sachin Sant
2009-12-04 12:16                       ` Peter Zijlstra
2009-12-07  6:16                         ` Sachin Sant
2009-12-12  7:09                     ` Max Krasnyansky
2009-11-12 17:40 ` linux-next: Tree for November 12 (acpi/processor.h) Randy Dunlap
2009-11-12 18:09   ` linux-next: Tree for November 12 (acpi_processor_get_bios_limit) Randy Dunlap
2009-11-12 23:46 ` [PATCH -next] staging/line6: fix printk formats Randy Dunlap

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=20091113095801.GA29977@in.ibm.com \
    --to=ego@in.ibm.com \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=sachinp@in.ibm.com \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).