public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Mike Galbraith <efault@gmx.de>
Cc: Ingo Molnar <mingo@elte.hu>, Frans Pop <elendil@planet.nl>,
	torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
	akpm@linux-foundation.org,
	Richard Jonsson <richie@coderworld.net>,
	"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [git pull] scheduler changes for v2.6.26
Date: Wed, 23 Apr 2008 13:21:55 +0200	[thread overview]
Message-ID: <1208949715.7115.334.camel@twins> (raw)
In-Reply-To: <1208946604.4803.9.camel@marge.simson.net>

On Wed, 2008-04-23 at 12:30 +0200, Mike Galbraith wrote:
> On Wed, 2008-04-23 at 10:11 +0200, Mike Galbraith wrote:
> 
> > I dug my old p3/500 out and hooked it up since I still can't get minicom
> > functional plugging P4->Q6600, but no joy.  Whatever the heck is going
> > wrong in sched-devel is so catastrophic that not one character hits the
> > console when it locks, and nmi_watchdog=1 does nada.
> 
> I built x86/latest to see if it locked, and while testing to see if
> minicom was really really working properly on p3/500, I created an
> explosion.  I see in the log that clockevents griped during boot, and
> when I later poked SysRq-W, box blew to pieces.

> [  604.923629] BUG: unable to handle kernel NULL pointer dereference at 0000000000000018
> [  604.923629] IP: [<ffffffff802a93ac>] seq_printf+0x2e/0xa7

Sorry about that :-/

this should fix it:

---
Subject: sched: fix oops

sched_debug uses SEQ_printf to use printk when the seqfile 'm' is NULL.
Instead of doing that here too; choose to not output the weight tree
to cut back on output.

Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
---
diff --git a/kernel/sched_fair.c b/kernel/sched_fair.c
index 89fa32b..353a481 100644
--- a/kernel/sched_fair.c
+++ b/kernel/sched_fair.c
@@ -1643,8 +1643,10 @@ static void print_cfs_stats(struct seq_file *m, int cpu)
 	for_each_leaf_cfs_rq(cpu_rq(cpu), cfs_rq)
 		print_cfs_rq(m, cpu, cfs_rq);
 
-	seq_printf(m, "\nWeight tree:\n");
-	print_cfs_rq_tasks(m, &cpu_rq(cpu)->cfs, 1);
+	if (m) {
+		seq_printf(m, "\nWeight tree:\n");
+		print_cfs_rq_tasks(m, &cpu_rq(cpu)->cfs, 1);
+	}
 	rcu_read_unlock();
 }
 #endif



  reply	other threads:[~2008-04-23 11:22 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-19 18:13 [git pull] scheduler changes for v2.6.26 Ingo Molnar
2008-04-19 18:47 ` Guillaume Chazarain
2008-04-19 18:49   ` Ingo Molnar
2008-04-19 18:54     ` Peter Zijlstra
2008-04-19 19:47 ` Frans Pop
2008-04-21 12:39   ` Ingo Molnar
2008-04-21 16:31     ` Frans Pop
2008-04-21 19:43       ` Ingo Molnar
2008-04-22  8:51         ` Mike Galbraith
2008-04-22  8:59           ` Ingo Molnar
2008-04-22  9:59             ` Peter Zijlstra
2008-04-22 12:25             ` Mike Galbraith
2008-04-23  8:11               ` Mike Galbraith
2008-04-23 10:30                 ` Mike Galbraith
2008-04-23 11:21                   ` Peter Zijlstra [this message]
2008-04-23 13:27                     ` Mike Galbraith
2008-04-22  9:41         ` Kevin Winchester
2008-04-22 10:49           ` David Miller
2008-04-22 11:10             ` Peter Zijlstra
2008-04-23  9:36         ` Frans Pop
2008-04-23  9:42           ` Peter Zijlstra
2008-04-23  9:46           ` Ingo Molnar
2008-04-23 13:36             ` Frans Pop
2008-04-29 12:29               ` Ingo Molnar
2008-04-29 15:28                 ` Steven Rostedt
2008-04-23 16:23             ` Frans Pop

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=1208949715.7115.334.camel@twins \
    --to=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=efault@gmx.de \
    --cc=elendil@planet.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=richie@coderworld.net \
    --cc=rjw@sisk.pl \
    --cc=torvalds@linux-foundation.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