public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: David Smith <dsmith@redhat.com>
To: maynardj@us.ibm.com
Cc: Roland McGrath <roland@redhat.com>,
	systemtap@sourceware.org,
	        "Frank Ch. Eigler" <fche@redhat.com>
Subject: Re: Backward compatibility for insn probe point
Date: Thu, 14 May 2009 19:44:00 -0000	[thread overview]
Message-ID: <4A0C7482.3010103@redhat.com> (raw)
In-Reply-To: <4A0C6A90.6070306@us.ibm.com>

Maynard Johnson wrote:
>> David Smith wrote:
>> One last thing.  I thought I'd try block stepping, so I got access to an
>> ia64 machine.  Unfortunately, using systemtap insn probes (either single
>> or block step) lock up the system with a spinlock lockup.  Sigh.
>
> Does anyone know who maintains ia64/utrace?  David, was the above error
> on "old" utrace or "new"?

The error is on "old" utrace.  I'm trying to look into the ia64 utrace
problem now.

-- 
David Smith
dsmith@redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)

  reply	other threads:[~2009-05-14 19:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-01 21:59 Maynard Johnson
2009-04-27 21:01 ` David Smith
2009-04-29 13:56   ` Maynard Johnson
2009-04-29 21:08   ` Maynard Johnson
2009-04-30 18:00     ` David Smith
2009-04-30 20:48       ` Roland McGrath
2009-05-12 16:06         ` David Smith
2009-05-12 18:20           ` Roland McGrath
2009-05-13 15:04             ` David Smith
2009-05-13 18:24               ` Roland McGrath
2009-05-14 15:11                 ` David Smith
2009-05-14 18:41                   ` Roland McGrath
2009-05-14 19:01                   ` Maynard Johnson
2009-05-14 19:44                     ` David Smith [this message]
2009-05-14 21:36                       ` David Smith
2009-05-15 13:52                         ` ia64 hang when using itrace (was Re: Backward compatibility for insn probe point) David Smith

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=4A0C7482.3010103@redhat.com \
    --to=dsmith@redhat.com \
    --cc=fche@redhat.com \
    --cc=maynardj@us.ibm.com \
    --cc=roland@redhat.com \
    --cc=systemtap@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).