From: Steven Rostedt <rostedt@goodmis.org>
To: habanero@linux.vnet.ibm.com
Cc: Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org,
paulmck <paulmck@linux.vnet.ibm.com>
Subject: Re: BUG on 3.0-rc on commit d72bce0e67e8afc6eb959f656013cbb577426f1e
Date: Mon, 13 Jun 2011 11:14:26 -0400 [thread overview]
Message-ID: <1307978066.9218.71.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <1307977614.17297.12.camel@atheurer-w510>
On Mon, 2011-06-13 at 10:06 -0500, Andrew Theurer wrote:
> On Fri, 2011-06-10 at 18:27 +0200, Peter Zijlstra wrote:
> > On Fri, 2011-06-10 at 10:34 -0500, Andrew Theurer wrote:
> > > RIP: 0010:[<ffffffff8104e8c1>] [<ffffffff8104e8c1>] find_lowest_rq+0xa1/0x150
> >
> > If you've still got the vmlinux around, could you find out where in
> > find_lowest_rq that RIP is?
>
> Does this help?
A little, but could you also do the following: (if you had DEBUG_INFO
compiled in)
$ gdb vmlinux
gdb> li *0xffffffff8104e8c1
And give the output of that?
Thanks,
-- Steve
next prev parent reply other threads:[~2011-06-13 15:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 13:17 Andrew Theurer
2011-06-10 14:11 ` Peter Zijlstra
2011-06-10 14:45 ` Peter Zijlstra
2011-06-10 14:52 ` Steven Rostedt
2011-06-10 14:59 ` Peter Zijlstra
2011-06-10 15:34 ` Andrew Theurer
2011-06-10 15:45 ` Andrew Theurer
2011-06-10 16:27 ` Peter Zijlstra
2011-06-13 15:06 ` Andrew Theurer
2011-06-13 15:14 ` Steven Rostedt [this message]
2011-06-13 15:33 ` Steven Rostedt
2011-06-14 0:05 ` Andrew Theurer
2011-06-14 0:35 ` Steven Rostedt
2011-06-14 0:52 ` Andrew Theurer
2011-06-14 1:24 ` Steven Rostedt
2011-06-14 2:29 ` Andrew Theurer
2011-06-14 11:02 ` Peter Zijlstra
2011-06-14 12:25 ` Steven Rostedt
2011-06-10 15:13 ` Andrew Theurer
2011-06-10 16:09 ` Peter Zijlstra
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=1307978066.9218.71.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=habanero@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®