summaryrefslogtreecommitdiffstats
path: root/kernel/sched
diff options
context:
space:
mode:
authorDave Jones <davej@redhat.com>2011-12-22 16:39:30 -0500
committerIngo Molnar <mingo@elte.hu>2011-12-23 11:20:50 +0100
commit664dfa65e84429d0b68694483e1de7365c7c56fb (patch)
tree9c3b1ae83a5a139c0420184d5eece0059c086216 /kernel/sched
parent62af3783e4fd8ba9e28416e8e91cb3bdd9fb133e (diff)
downloadop-kernel-dev-664dfa65e84429d0b68694483e1de7365c7c56fb.zip
op-kernel-dev-664dfa65e84429d0b68694483e1de7365c7c56fb.tar.gz
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@redhat.com> Link: http://lkml.kernel.org/r/20111222213929.GA4722@redhat.com Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'kernel/sched')
-rw-r--r--kernel/sched/core.c3
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());
OpenPOWER on IntegriCloud