This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/19186] New: getting a 'BUG: sleeping fujnction called from invalid context' error on rawhide
- From: "dsmith at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Thu, 29 Oct 2015 18:19:17 +0000
- Subject: [Bug runtime/19186] New: getting a 'BUG: sleeping fujnction called from invalid context' error on rawhide
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=19186
Bug ID: 19186
Summary: getting a 'BUG: sleeping fujnction called from invalid
context' error on rawhide
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 slowvfs.stp example script on a rawhide kernel
(4.3.0-0.rc7.git1.1.fc24.x86_64), I get the following kernel backtrace:
====
[ 2849.293562] stap_88e4cea26e1c41bc9512e34dc8172103_17592: systemtap:
3.0/0.164, base: ffffffffa0495000, memory:
172data/48text/191ctx/2058net/380alloc kb, probes: 3
[ 2849.395584] BUG: sleeping fujnction called from invalid context at
kernel/locking/mutex.c:616
[ 2849.404038] in_atomic(): 1, irqs_disabled(): 0, pid: 17600, name: modprobe
[ 2849.410930] no locks held by modprobe/17600.
[ 2849.415223] CPU: 7 PID: 17600 Comm: modprobe Tainted: G OE
4.3.0-0.rc7.git1.1.fc24.x86_64 #1
[ 2849.424703] Hardware name: Intel MP Server/S5000VSA , BIOS
S5000.86B.02.00.0054.061520062205 06/15/2006
[ 2849.434193] 0000000000000000 000000005f15d42a ffff8801341f3be8
ffffffff8141be59
[ 2849.441713] ffff880159680000 ffff8801341f3c10 ffffffff810d72b9
ffffffff81c8b280
[ 2849.449234] 0000000000000268 0000000000000000 ffff8801341f3c38
ffffffff810d73b9
[ 2849.456762] Call Trace:
[ 2849.459238] [<ffffffff8141be59>] dump_stack+0x4b/0x72
[ 2849.464391] [<ffffffff810d72b9>] ___might_sleep+0x179/0x230
[ 2849.470068] [<ffffffff810d73b9>] __might_sleep+0x49/0x80
[ 2849.475484] [<ffffffff81860da3>] mutex_lock_nested+0x43/0x400
[ 2849.481328] [<ffffffff81104fa9>] ? trace_hardirqs_on_caller+0x129/0x1b0
[ 2849.488050] [<ffffffffa049aaeb>] systemtap_module_refresh+0x1b/0x180
[stap_88e4cea26e1c41bc9512e34dc8172103_17592]
[ 2849.498502] [<ffffffffa049acae>] _stp_module_notifier+0x3e/0x190
[stap_88e4cea26e1c41bc9512e34dc8172103_17592]
[ 2849.508600] [<ffffffffa049ae38>] _stp_module_load_tp+0x18/0x20
[stap_88e4cea26e1c41bc9512e34dc8172103_17592]
[ 2849.518533] [<ffffffff8114e843>] load_module+0x2163/0x27d0
[ 2849.524125] [<ffffffff8114a980>] ? __symbol_put+0x70/0x70
[ 2849.529628] [<ffffffff810e451a>] ? sched_clock_cpu+0x8a/0xb0
[ 2849.535391] [<ffffffff81212c0d>] ? __might_fault+0x4d/0xa0
[ 2849.540982] [<ffffffff8114f022>] SyS_init_module+0x172/0x1b0
[ 2849.546743] [<ffffffff81864bb2>] entry_SYSCALL_64_fastpath+0x12/0x76
====
Note that this doesn't seem to be happening 100% of the time.
--
You are receiving this mail because:
You are the assignee for the bug.