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/15908] On ARM fc19 hw_watch_addr.stp example causes kernel  hang and "BUG: scheduling while atomic:" and lock up
Date: Thu, 29 Aug 2013 19:42:00 -0000	[thread overview]
Message-ID: <bug-15908-6586-76D4y7zt2w@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15908-6586@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=15908

--- Comment #1 from William Cohen <wcohen at redhat dot com> ---
The testsuite/systemtap.log has the following output which seems to indicate
that it should fail because "OUT WARNING" says no hardware watchpoints are
available:

meta taglines 'test_support: perf stat --event=mem:0xc000000 /bin/true' tag
'test_support' value 'perf stat --event=mem:0xc000000 /bin/true'
TEST
PWD=/mnt/badlands/home/wcohen/systemtap_write/systemtap/testsuite/systemtap.examples/memory
attempting command perf stat --event=mem:0xc000000 /bin/true
OUT 
 Performance counter stats for '/bin/true':

                 0 mem:0xc000000                                               

       0.012679596 seconds time elapsed

RC 0
PASS: ./systemtap.examples/memory/hw_watch_addr support
meta taglines 'test_check: stap --all-modules -p4 hw_watch_addr.stp 0x`grep
"vm_dirty_ratio" /proc/kallsyms`' tag 'test_check' value 'stap --all-modules
-p4 hw_watch_addr.stp 0x`grep "vm_dirty_ratio" /proc/kallsyms`'
attempting command stap --all-modules -p4 hw_watch_addr.stp 0x`grep
"vm_dirty_ratio" /proc/kallsyms`
OUT WARNING: Too many hardware breakpoint probes requested for arm (1 vs. 0)
/mnt/badlands/home/wcohen/systemtap_write/systemtap/testsuite/.systemtap-root/cache/1e/stap_1ecd6f7036b3c87d801be07b2476bfa4_2556.ko
RC 0
PASS: ./systemtap.examples/memory/hw_watch_addr build
meta taglines 'test_installcheck: stap --all-modules hw_watch_addr.stp 0x`grep
"vm_dirty_ratio" /proc/kallsyms` -c "sleep 5"' tag 'test_installcheck' value
'stap --all-modules hw_watch_addr.stp 0x`grep "vm_dirty_ratio" /proc/kallsyms`
-c "sleep 5"'
attempting command stap --all-modules hw_watch_addr.stp 0x`grep
"vm_dirty_ratio" /proc/kallsyms` -c "sleep 5"

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

  reply	other threads:[~2013-08-29 19:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-29 19:33 [Bug runtime/15908] New: " wcohen at redhat dot com
2013-08-29 19:42 ` wcohen at redhat dot com [this message]
2013-08-29 22:21 ` [Bug runtime/15908] " 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-15908-6586-76D4y7zt2w@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).