[Bug runtime/24416] Tests stuck in uprobes_onthefly.exp

["wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>]

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

--- Comment #2 from William Cohen <wcohen at redhat dot com> ---
The particular test where the RCU warnings start occurring appears to be the
last one in uprobes_onthefly.exp:

run_subtest_stress "otf_stress_max_iter_5000" 1 5000 max \
   -D STP_ON_THE_FLY_INTERVAL=100000

According to comment below for make_script a lot of tracepoint will be used. 
It is possible that variation in the trace

# Returns a script with some variables replaced.
#     SUBTEST    name of subtest
#     ENABLED    set to 1 to start the target probe as enabled, 0 as disabled
#     MAXTOGGLES number of times we toggle the target probe condition
#     TIMER      if a number, then it's the period of the timer probe which
#                toggles the target probes, if set to 'profile' then instead a
#                timer.profile probe is used to toggle the target probe, if set
#                to 'hardcore' then both a timer.profile probe and a
#                kernel.trace("*") probe is used for toggling, if set to 'max'
#                then a lot of various probe points are used for toggling

It looks like the x86_64 might be running into a problem similar to the one
addressed in PR17270 by:

commit e6f437adfe6d0f48562ce3204c0fa4dd184b43c9
Author: David Smith <dsmith@redhat.com>
Date:   Wed Dec 17 11:38:45 2014 -0600

    Fixed PR17270 by updating "on the fly" tests for ppc64.

    * translate.cxx (c_unparser::emit_module_refresh): Don't print debug
      message in STAP_SESSION_STOPPING state.
    * testsuite/systemtap.onthefly/hrtimer_onthefly.exp: On ppc64, don't probe
      kernel tracepoints causing a crash.
    * testsuite/systemtap.onthefly/kprobes_onthefly.exp: Ditto.
    * testsuite/systemtap.onthefly/uprobes_onthefly.exp: Ditto.

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