public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "joshua dot i dot stone at intel dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug kprobes/2294] New: current.stp causes NX protection fault on i686 SMP
Date: Tue, 07 Feb 2006 21:20:00 -0000	[thread overview]
Message-ID: <20060207212024.2294.joshua.i.stone@intel.com> (raw)

It has been reported in two cases that current.stp causes an NX protection fault.

http://sources.redhat.com/ml/systemtap/2006-q1/msg00157.html
http://sources.redhat.com/ml/systemtap/2006-q1/msg00397.html

The two kernels reported to crash are 2.6.14-1.1656_FC4smp.i686 and
2.6.9-30.ELsmp.i686.  Both reports had a similar stack trace as well, starting with:

  kretprobe_trampoline
  do_timer
  timer_interrupt
  kretprobe_trampoline

Several other kernels and a different architecture (x86_64) were tested and did
not experience this crash.

-- 
           Summary: current.stp causes NX protection fault on i686 SMP
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: kprobes
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: joshua dot i dot stone at intel dot com


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

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

             reply	other threads:[~2006-02-07 21:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-07 21:20 joshua dot i dot stone at intel dot com [this message]
2006-02-09  3:22 ` [Bug kprobes/2294] " bibo dot mao at intel 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=20060207212024.2294.joshua.i.stone@intel.com \
    --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).