This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug testsuite/13332] New: skipped.exp testcase can freeze processes/system
- From: "mjw at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Sat, 22 Oct 2011 19:52:39 +0000
- Subject: [Bug testsuite/13332] New: skipped.exp testcase can freeze processes/system
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=13332
Bug #: 13332
Summary: skipped.exp testcase can freeze processes/system
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: testsuite
AssignedTo: systemtap@sourceware.org
ReportedBy: mjw@redhat.com
Classification: Unclassified
When running skipped.exp (sudo make installcheck RUNTESTFLAGS=skipped.exp) my
machine sometimes acts up (frozen processes) and dmesg will show:
hrtimer: interrupt took 30006338 ns
Sometimes, though not often, the skipped.exp testcase itself will timeout.
This seem to be caused by this (guru) script:
global f
probe timer.profile { f++; snooze() }
function snooze() %{ udelay(10000); %}
It is run with:
stap -e $script -DMAXTRYLOCK=0 -DSTP_NO_OVERLOAD -tug
The purpose of the test seems to be to see whether global locks timeout.
Is there a better way to test this that doesn't cause such long interrupts
resulting in system/process freezes?
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.