[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200711082242.21869.rjw@sisk.pl>
Date: Thu, 8 Nov 2007 22:42:21 +0100
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Grant Wilson <grant.wilson@....co.uk>
Cc: lkml <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
netdev <netdev@...r.kernel.org>
Subject: Re: 2.6.24-rc1-gb4f5550 oops
On Thursday, 8 of November 2007, Grant Wilson wrote:
> On Thu, 8 Nov 2007 16:53:10 +0100
> "Rafael J. Wysocki" <rjw@...k.pl> wrote:
>
> > On Thursday, 8 of November 2007, Grant Wilson wrote:
> > > On Thu, 8 Nov 2007 01:06:21 +0100
> > > "Rafael J. Wysocki" <rjw@...k.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.
Thanks,
Rafael
-
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