From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Grant Wilson <grant.wilson@zen.co.uk>, Ingo Molnar <mingo@elte.hu>
Cc: lkml <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: 2.6.24-rc1-gb4f5550 oops
Date: Thu, 8 Nov 2007 23:49:18 +0100 [thread overview]
Message-ID: <200711082349.19344.rjw@sisk.pl> (raw)
In-Reply-To: <20071108221951.71224bd8@worthy.swandive.local>
On Thursday, 8 of November 2007, Grant Wilson wrote:
> On Thu, 8 Nov 2007 22:42:21 +0100
> "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
>
> > On Thursday, 8 of November 2007, Grant Wilson wrote:
> > > On Thu, 8 Nov 2007 16:53:10 +0100
> > > "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> > >
> > > > On Thursday, 8 of November 2007, Grant Wilson wrote:
> > > > > On Thu, 8 Nov 2007 01:06:21 +0100
> > > > > "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> > > > >
> > > > > > On Monday, 5 of November 2007, Grant Wilson wrote:
> > > > > > > Hi,
> > > > > > > I got this oops on 2.6.24-rc1-641-gb4f5550:
> > > > > >
> > > > > > (1) Is this reproducible?
> > > > > > (2) Did it happen previously on your system?
> > > > > >
> > > > > > [18073.371126] Unable to handle kernel NULL pointer dereference at 0000000000000120 RIP:
> > > > > > [18073.371134] [<ffffffff8023572e>] check_preempt_wakeup+0x6e/0x110
> > > > >
> > > > > This has now happened twice - the second time was last night when
> > > > > running 2.6.24-rc2.
> > > > >
> > > > > Here's that second occurrence:
> > > > >
> > > [snip]
> > > >
> > > > Hmm.
> > > >
> > > > Please run "gdb vmlinux" and see what code corresponds to
> > > > check_preempt_wakeup+0x6e in your kernel.
> > >
> > >
> > > Dump of assembler code for function check_preempt_wakeup:
> >
> > Well, thanks, but I meant the source code. Please do "gdb vmlinux" and then
> > "l *check_preempt_wakeup+0x6e" in gdb.
>
> Here's the requested output:
>
> (gdb) l *check_preempt_wakeup+0x6e
> 0xffffffff802329ae is in check_preempt_wakeup (kernel/sched_fair.c:668).
> 663
> 664 /* Do the two (enqueued) entities belong to the same group ? */
> 665 static inline int
> 666 is_same_group(struct sched_entity *se, struct sched_entity *pse)
> 667 {
> 668 if (se->cfs_rq == pse->cfs_rq)
> 669 return 1;
> 670
> 671 return 0;
> 672 }
Well, it looks like either se or pse is NULL.
Ingo, can you please have a look?
Thanks,
Rafael
next prev parent reply other threads:[~2007-11-08 22:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 6:11 2.6.24-rc1-gb4f5550 oops Grant Wilson
2007-11-08 0:06 ` Rafael J. Wysocki
[not found] ` <20071108062250.02479c0c@worthy.swandive.local>
2007-11-08 15:53 ` Rafael J. Wysocki
2007-11-08 17:22 ` Grant Wilson
2007-11-08 21:42 ` Rafael J. Wysocki
2007-11-08 22:19 ` Grant Wilson
2007-11-08 22:49 ` Rafael J. Wysocki [this message]
2007-11-12 18:05 ` Peter Zijlstra
2007-11-12 18:28 ` Grant Wilson
-- strict thread matches above, loose matches on Subject: below --
2007-11-14 15:17 Oleg Nesterov
2007-11-14 15:29 ` Ingo Molnar
2007-11-14 15:50 ` Oleg Nesterov
2007-11-14 15:59 ` Ingo Molnar
2007-11-14 16:02 ` Ingo Molnar
2007-11-14 16:37 ` Srivatsa Vaddagiri
2007-11-14 17:48 ` Oleg Nesterov
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=200711082349.19344.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=grant.wilson@zen.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.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