public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/12947] New: Use of hardware watchpoint causing oops
Date: Tue, 28 Jun 2011 21:03:00 -0000	[thread overview]
Message-ID: <bug-12947-6586@http.sourceware.org/bugzilla/> (raw)

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

           Summary: Use of hardware watchpoint causing oops
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
        AssignedTo: systemtap@sourceware.org
        ReportedBy: wcohen@redhat.com


Created attachment 5825
  --> http://sourceware.org/bugzilla/attachment.cgi?id=5825
Serial console of the run with the oops

I was experimenting to the hardware watchpoints.

I had one script that would give me an address of the place going to probe and
then had another another script to initialize the hardware watchpoint and
record backtraces when the memory location was accessed.

Find the address with:

[wcohen@montague tmp]$ stap -g find_free_ram_addr.stp
&global_page_state(NR_FREE_PAGES) = 0xffffffffc0bb0eb0

Then set monitoring with:

[wcohen@montague tmp]$ stap -g track_free_ram.stp 0xc0bb0eb0

Attached is log of the run.

This was using

kernel-2.6.38.8-32.fc15.i686
systemtap-1.5-1.fc15.i686

It seems like that the hw watch points should be better behaved.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2011-06-28 21:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-28 21:03 wcohen at redhat dot com [this message]
2011-06-28 21:04 ` [Bug runtime/12947] " wcohen at redhat dot com
2011-06-28 21:05 ` wcohen at redhat dot com
2011-06-29 15:57 ` wcohen at redhat dot com
2011-07-05 15:46 ` wcohen at redhat dot com
2011-07-05 16:01 ` wcohen at redhat dot com
2011-07-27 18:23 ` wcohen 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=bug-12947-6586@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --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).