public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug runtime/3911] Compilation of systemtap causes the system to crash on p570 system.
Date: Thu, 25 Jan 2007 20:27:00 -0000	[thread overview]
Message-ID: <20070125202733.17559.qmail@sourceware.org> (raw)
In-Reply-To: <20070124094941.3911.srinivasa@in.ibm.com>


------- Additional Comments From fche at redhat dot com  2007-01-25 20:27 -------
(In reply to comment #0)
> I was compiling latest systemtap source on  rhel5(2.6.18-1.2961.el5) kernel and
> system dropped to xmon.

Not really just compiling: you were running test cases.

> What xmon shows 
> =============================
> Unable to handle kernel paging request for data at address 0x420000000007f
> 5:mon> e
> cpu 0x5: Vector: 300 (Data Access) at [c000000028a6b310]
>     pc: c000000000349f40: ._spin_lock+0x20/0x88

This resembles a memory corruption that may even precede this systemtap module.
It is certainly *before* any probes are even registered, let alone run.  The
runtime is the only part more or less running by this time.


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=3911

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

  parent reply	other threads:[~2007-01-25 20:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-24  9:50 [Bug runtime/3911] New: " srinivasa at in dot ibm dot com
2007-01-24 15:13 ` [Bug runtime/3911] " mmlnx at us dot ibm dot com
2007-01-25 20:27 ` fche at redhat dot com [this message]
2007-01-29  8:31 ` srinivasa at in dot ibm dot com
2007-01-30  7:17 ` srinivasa at in dot ibm dot com
2007-01-30 12:16 ` fche at redhat dot com
2007-01-30 14:37 ` hunt at redhat dot com
2007-01-30 14:38 ` hunt at redhat dot com

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=20070125202733.17559.qmail@sourceware.org \
    --to=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).