From: "Dmitry Adamushko" <dmitry.adamushko@gmail.com>
To: "Vegard Nossum" <vegard.nossum@gmail.com>
Cc: Yanmin <yanmin_zhang@linux.intel.com>,
"Rusty Russell" <rusty@rustcorp.com.au>,
"Ingo Molnar" <mingo@elte.hu>,
"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
"Dhaval Giani" <dhaval@linux.vnet.ibm.com>,
"Gautham R Shenoy" <ego@in.ibm.com>,
"Heiko Carstens" <heiko.carstens@de.ibm.com>,
miaox@cn.fujitsu.com, "Lai Jiangshan" <laijs@cn.fujitsu.com>,
"Avi Kivity" <avi@qumranet.com>,
linux-kernel@vger.kernel.org
Subject: Re: v2.6.26-rc9: kernel BUG at kernel/sched.c:5858!
Date: Fri, 11 Jul 2008 11:02:25 +0200 [thread overview]
Message-ID: <b647ffbd0807110202o10ca65c7yf93d8b2146a05e33@mail.gmail.com> (raw)
In-Reply-To: <19f34abd0807102249t6b2e9e97l97bc5b22cc7709ef@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 511 bytes --]
Vegard,
regarding the first crash. Would you please run your test with the
following debugging patch and let me know its output?
The apperance of " * [ pid ] comm (name), orig_cpu() ... " means we
hit a problematic case (with Miao Xie's patch it shouldn't crash).
I see that you have CONFIG_SCHED_DEBUG=y so I'm also interested in
messages from sched_domain_debug() - "CPU# attaching ...". IOW, all
the kernel messages appearing while a cpu is going down and up.
TIA,
--
Best regards,
Dmitry Adamushko
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: hotplug-debug.patch --]
[-- Type: text/x-patch; name=hotplug-debug.patch, Size: 1368 bytes --]
--- kernel/sched-orig.c 2008-07-10 15:08:01.000000000 +0200
+++ kernel/sched.c 2008-07-11 10:52:48.000000000 +0200
@@ -2081,6 +2081,7 @@ static int try_to_wake_up(struct task_st
unsigned long flags;
long old_state;
struct rq *rq;
+ int oops = 0;
if (!sched_feat(SYNC_WAKEUPS))
sync = 0;
@@ -2103,6 +2104,11 @@ static int try_to_wake_up(struct task_st
goto out_activate;
cpu = p->sched_class->select_task_rq(p, sync);
+ if (unlikely(cpu_is_offline(cpu))) {
+ cpu = orig_cpu;
+ oops = 1;
+ }
+
if (cpu != orig_cpu) {
set_task_cpu(p, cpu);
task_rq_unlock(rq, &flags);
@@ -2159,6 +2165,10 @@ out_running:
out:
task_rq_unlock(rq, &flags);
+ if (oops)
+ printk(KERN_ERR " * [ %d ] comm (%s), orig_cpu (%d), dst_cpu (%d), cpu (%d)\n",
+ p->pid, p->comm, orig_cpu, cpu, task_cpu(p));
+
return success;
}
@@ -5712,6 +5722,10 @@ static int __migrate_task_irq(struct tas
local_irq_disable();
ret = __migrate_task(p, src_cpu, dest_cpu);
local_irq_enable();
+
+ printk(KERN_ERR "__migrate(%d -- %s) -> cpu (%d) == ret (%d)\n",
+ p->pid, p->comm, dest_cpu, ret);
+
return ret;
}
@@ -5868,6 +5882,7 @@ static void migrate_dead(unsigned int de
* fine.
*/
spin_unlock_irq(&rq->lock);
+ printk(KERN_ERR "---> migrate_dead(%d -- %s)\n", p->pid, p->comm);
move_task_off_dead_cpu(dead_cpu, p);
spin_lock_irq(&rq->lock);
next prev parent reply other threads:[~2008-07-11 9:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 11:59 Vegard Nossum
2008-07-10 12:12 ` Vegard Nossum
2008-07-10 12:50 ` Dmitry Adamushko
2008-07-10 13:04 ` Vegard Nossum
2008-07-10 13:17 ` Vegard Nossum
2008-07-10 13:33 ` Vegard Nossum
2008-07-10 13:43 ` Vegard Nossum
2008-07-10 14:03 ` Dmitry Adamushko
2008-07-10 14:16 ` Vegard Nossum
2008-07-10 15:06 ` Vegard Nossum
2008-07-10 19:49 ` Vegard Nossum
2008-07-10 20:16 ` Dmitry Adamushko
2008-07-11 5:49 ` Vegard Nossum
2008-07-11 9:02 ` Dmitry Adamushko [this message]
2008-07-11 11:04 ` Vegard Nossum
2008-07-11 11:46 ` Dmitry Adamushko
2008-07-11 17:51 ` Vegard Nossum
2008-07-11 18:00 ` Vegard Nossum
2008-07-11 23:42 ` Dmitry Adamushko
2008-07-10 20:20 ` Rafael J. Wysocki
2008-07-11 5:23 ` Vegard Nossum
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=b647ffbd0807110202o10ca65c7yf93d8b2146a05e33@mail.gmail.com \
--to=dmitry.adamushko@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=avi@qumranet.com \
--cc=dhaval@linux.vnet.ibm.com \
--cc=ego@in.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miaox@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=vegard.nossum@gmail.com \
--cc=yanmin_zhang@linux.intel.com \
/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
Powered by JetHome