[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <tip-664dfa65e84429d0b68694483e1de7365c7c56fb@git.kernel.org>
Date: Fri, 23 Dec 2011 05:18:29 -0800
From: tip-bot for Dave Jones <davej@...hat.com>
To: linux-tip-commits@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, hpa@...or.com, mingo@...hat.com,
davej@...hat.com, tglx@...utronix.de, mingo@...e.hu
Subject: [tip:sched/core] sched: Disable scheduler warnings during oopses
Commit-ID: 664dfa65e84429d0b68694483e1de7365c7c56fb
Gitweb: http://git.kernel.org/tip/664dfa65e84429d0b68694483e1de7365c7c56fb
Author: Dave Jones <davej@...hat.com>
AuthorDate: Thu, 22 Dec 2011 16:39:30 -0500
Committer: Ingo Molnar <mingo@...e.hu>
CommitDate: Fri, 23 Dec 2011 11:20:50 +0100
sched: Disable scheduler warnings during oopses
The panic-on-framebuffer code seems to cause a schedule
to occur during an oops. This causes a bunch of extra
spew as can be seen in:
https://bugzilla.redhat.com/attachment.cgi?id=549230
Don't do scheduler debug checks when we are oopsing already.
Signed-off-by: Dave Jones <davej@...hat.com>
Link: http://lkml.kernel.org/r/20111222213929.GA4722@redhat.com
Signed-off-by: Ingo Molnar <mingo@...e.hu>
---
kernel/sched/core.c | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index 081ece2..8ffe523 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -3077,6 +3077,9 @@ static noinline void __schedule_bug(struct task_struct *prev)
{
struct pt_regs *regs = get_irq_regs();
+ if (oops_in_progress)
+ return;
+
printk(KERN_ERR "BUG: scheduling while atomic: %s/%d/0x%08x\n",
prev->comm, prev->pid, preempt_count());
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists