* [Bug runtime/20516] New: "BUG: spinlock recursion on CPU#0" crash on s390x
@ 2016-08-25 16:03 dsmith at redhat dot com
2016-08-25 16:14 ` [Bug runtime/20516] " fche at redhat dot com
2017-10-06 15:37 ` dsmith at redhat dot com
0 siblings, 2 replies; 3+ messages in thread
From: dsmith at redhat dot com @ 2016-08-25 16:03 UTC (permalink / raw)
To: systemtap
https://sourceware.org/bugzilla/show_bug.cgi?id=20516
Bug ID: 20516
Summary: "BUG: spinlock recursion on CPU#0" crash on s390x
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: ---
Host: s390x
On the RHEL7 debug kernel (3.10.0-327.el7.s390x.debug), I'm seeing a crash when
running the following command:
# make -j3 installcheck-parallel TESTS='*/buildok-interactive.exp
*/parse-semok.exp */uprobes_onthefly.exp'
I just got the following backtrace:
====
[ 663.318409] BUG: spinlock recursion on CPU#0, stap/17029
[ 663.318424] lock: 0x2697888, .magic: dead4ead, .owner: stap/17029,
.owner_cp
u: 0
[ 663.318429] CPU: 0 PID: 17029 Comm: stap Tainted: G OE
-----------
- 3.10.0-327.el7.s390x.debug #1
[ 663.318433] 000000000001b848 000000000001b858 0000000000000002
0000000
000000000
000000000001b8e8 000000000001b860 000000000001b860 0000000000112f78
0000000000000000 00000000007fbf1e 00000000007de39c 000000000000000b
000000000001b8a8 000000000001b848 0000000000000000 0000000000000000
00000000006a0c80 0000000000112f78 000000000001b848 000000000001b8a8
[ 663.318473] Call Trace:
[ 663.318477] ([<0000000000112ebc>] show_trace+0x144/0x148)
[ 663.318487] [<0000000000112f2c>] show_stack+0x6c/0xe8
[ 663.318493] [<0000000000410ffa>] do_raw_spin_lock+0x14a/0x160
[ 663.318501] [<000000000065348c>] _raw_spin_lock+0x84/0x98
[ 663.318510] [<0000000000188b76>] account_system_time+0xce/0x1d0
[ 663.318518] [<00000000001049d0>] vtime_account_irq_enter+0xc0/0x140
[ 663.318650] [<0000000000143640>] irq_enter+0x58/0xa8
[ 663.318655] [<000000000010ccf0>] do_extint+0x58/0x310
[ 663.318659] [<000000000065557e>] ext_skip+0x40/0x46
[ 663.318663] [<0000000000654ce0>] vtime_stop_cpu+0x50/0xa8
[ 663.318666] ([<0000000000654cc6>] vtime_stop_cpu+0x36/0xa8)
[ 663.318670] [<000000000040399e>] __udelay_disabled+0x8e/0xd0
[ 663.318716] [<0000000000403a8c>] __udelay+0xac/0x110
[ 663.318720] [<000003ff807c92fe>] stp_lock_probe+0xe6/0x110
[stap_d119207e065
a4a09629eafc3026ded3d__17023]
[ 663.318768] [<000003ff807d52ca>] probe_2809+0x32/0x210
[stap_d119207e065a4a0
9629eafc3026ded3d__17023]
[ 663.318796] [<000003ff80850196>] enter_real_tracepoint_probe_887+0xce/0x230
[stap_d119207e065a4a09629eafc3026ded3d__17023]
[ 663.318819] [<00000000001bd336>] lock_release+0xfe/0x2c8
[ 663.318826] [<00000000006538c4>] _raw_spin_unlock+0x34/0x58
[ 663.318833] [<0000000000188b90>] account_system_time+0xe8/0x1d0
[ 663.318840] [<00000000001049d0>]
(zcon 15:13:21) [-- MARK --]
(zcon 15:28:22) [-- MARK --]
[ 663.318840] [<00000000001049d0>] vtime_account_irq_enter+0xc0/0x140
[ 663.318896] [<0000000000143640>] irq_enter+0x58/0xa8
[ 663.318899] [<000000000010ccf0>] do_extint+0x58/0x310
[ 663.318908] [<000000000065557e>] ext_skip+0x40/0x46
[ 663.318928] [<000003fffd60fb66>] 0x3fffd60fb66
[ 663.318934] INFO: lockdep is turned off.
[ 2489.906739] BUG: spinlock lockup suspected on CPU#0, stap/17029
[ 2489.906776] lock: 0x2697888, .magic: dead4ead, .owner: stap/17029,
.owner_cp
u: 0
[ 2489.906781] CPU: 0 PID: 17029 Comm: stap Tainted: G OE
-----------
- 3.10.0-327.el7.s390x.debug #1
[ 2489.906785] 000000000001b848 000000000001b858 0000000000000002
0000000
000000000
000000000001b8e8 000000000001b860 000000000001b860 0000000000112f78
0000000000000000 00000000007fbf1e 00000000007de39c 000000000000000b
000000000001b8a8 000000000001b848 0000000000000000 0000000000000000
00000000006a0c80 0000000000112f78 000000000001b848 000000000001b8a8
[ 2489.907127] Call Trace:
[ 2489.907132] ([<0000000000112ebc>]
====
That's actually the first backtrace I've seen for this problem. Typically the
machine crashed immediately to the s390x monitor with nothing printed on the
console.
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug runtime/20516] "BUG: spinlock recursion on CPU#0" crash on s390x
2016-08-25 16:03 [Bug runtime/20516] New: "BUG: spinlock recursion on CPU#0" crash on s390x dsmith at redhat dot com
@ 2016-08-25 16:14 ` fche at redhat dot com
2017-10-06 15:37 ` dsmith at redhat dot com
1 sibling, 0 replies; 3+ messages in thread
From: fche at redhat dot com @ 2016-08-25 16:14 UTC (permalink / raw)
To: systemtap
https://sourceware.org/bugzilla/show_bug.cgi?id=20516
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fche at redhat dot com
--- Comment #1 from Frank Ch. Eigler <fche at redhat dot com> ---
likely s390 kernel problem: see also
https://bugzilla.redhat.com/show_bug.cgi?id=1319085
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug runtime/20516] "BUG: spinlock recursion on CPU#0" crash on s390x
2016-08-25 16:03 [Bug runtime/20516] New: "BUG: spinlock recursion on CPU#0" crash on s390x dsmith at redhat dot com
2016-08-25 16:14 ` [Bug runtime/20516] " fche at redhat dot com
@ 2017-10-06 15:37 ` dsmith at redhat dot com
1 sibling, 0 replies; 3+ messages in thread
From: dsmith at redhat dot com @ 2017-10-06 15:37 UTC (permalink / raw)
To: systemtap
https://sourceware.org/bugzilla/show_bug.cgi?id=20516
David Smith <dsmith at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from David Smith <dsmith at redhat dot com> ---
Added a workaround in commit 54c6b53ee. This workaround uses
kallsyms_lookup_symbol() to find the address of udelay_simple(). The real fix
for this problem is for the RHEL7 kernel to export udelay_simple().
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-10-06 15:37 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-08-25 16:03 [Bug runtime/20516] New: "BUG: spinlock recursion on CPU#0" crash on s390x dsmith at redhat dot com
2016-08-25 16:14 ` [Bug runtime/20516] " fche at redhat dot com
2017-10-06 15:37 ` dsmith at redhat dot com
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).