From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/20279] New: in parallel testsuite mode, we're getting SIGABORTs
Date: Mon, 20 Jun 2016 21:30:00 -0000 [thread overview]
Message-ID: <bug-20279-6586@http.sourceware.org/bugzilla/> (raw)
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.
next reply other threads:[~2016-06-20 21:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 21:30 dsmith at redhat dot com [this message]
2016-06-20 21:40 ` [Bug runtime/20279] " dsmith at redhat dot com
2016-06-21 0:11 ` jistone at redhat dot com
2016-06-21 13:38 ` [Bug runtime/20279] in parallel testsuite mode, we're getting SIGSEGVs dsmith at redhat dot com
2016-06-21 17:32 ` jistone 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-20279-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).