From: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
To: fche at redhat dot com <sourceware-bugzilla@sourceware.org>
Cc: systemtap@sources.redhat.com
Subject: Re: [Bug kprobes/2453] kernel panic when probe elv_dequeue_request
Date: Tue, 14 Mar 2006 04:27:00 -0000 [thread overview]
Message-ID: <20060314042707.GB2339@in.ibm.com> (raw)
In-Reply-To: <20060313144919.15380.qmail@sourceware.org>
On Mon, Mar 13, 2006 at 02:49:19PM -0000, fche at redhat dot com wrote:
>
> ------- Additional Comments From fche at redhat dot com 2006-03-13 14:49 -------
> To my powerpc-inexperienced eyes, it looks like the kprobe breakpoint ended up
> on top of a tdnei (conditional trap) instruction.
Well, that tdnei is what BUG() uses internally to cause a trap. Methinks,
we have hit a (possibly legitimate) BUG() while using the testcase.
Ananth
next prev parent reply other threads:[~2006-03-14 4:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 8:34 [Bug kprobes/2453] New: " guanglei at cn dot ibm dot com
2006-03-13 14:49 ` [Bug kprobes/2453] " fche at redhat dot com
2006-03-14 4:27 ` Ananth N Mavinakayanahalli [this message]
2006-03-14 4:27 ` ananth at in dot ibm dot com
2006-03-16 0:30 ` jkenisto at us dot ibm dot com
2006-03-16 3:18 ` Michael Ellerman
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=20060314042707.GB2339@in.ibm.com \
--to=ananth@in.ibm.com \
--cc=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).