This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/20279] New: in parallel testsuite mode, we're getting SIGABORTs
- From: "dsmith at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Mon, 20 Jun 2016 21:30:37 +0000
- Subject: [Bug runtime/20279] New: in parallel testsuite mode, we're getting SIGABORTs
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=20279
Bug ID: 20279
Summary: in parallel testsuite mode, we're getting SIGABORTs
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
Assignee: systemtap at sourceware dot org
Reporter: dsmith at redhat dot com
Target Milestone: ---
When running the testsuite in parallel mode, I see several of the following
messages on the console:
[ 5619.908020] rm[61446]: unhandled signal 11 at 00003fffdc83ff90 nip
00003fffa8a51f38 lr 00003fffa8a34008 code 30001
[ 6611.824811] bz5274[54850]: unhandled signal 11 at 0000000000000000 nip
0000000000000000 lr 0000000000000000 code 30001
On RHEL7 ppc64, I see around 7 of these during a full testsuite run. I don't
see these errors when the testsuite is run in non-parallel mode.
I'm not 100% sure it is related, but the testsuite also got hung at the end of
this run, waiting on a 'loop' process (from unprivileged_probes.exp) to be
killed.
--
You are receiving this mail because:
You are the assignee for the bug.