This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/21876] New: on rhel6 i686, running the testsuite crashes the kernel
- From: "dsmith at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Tue, 01 Aug 2017 17:25:51 +0000
- Subject: [Bug runtime/21876] New: on rhel6 i686, running the testsuite crashes the kernel
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=21876
Bug ID: 21876
Summary: on rhel6 i686, running the testsuite crashes the
kernel
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: ---
With HEAD systemtap on RHEL6 (2.6.32-696.6.3.el6.i686), when running the
testsuite I see the following on the console:
====
Systemtap Error at _stp_mempool_init:50 Memory allocation failed.
Systemtap Error at _stp_register_ctl_channel:738 Error creating systemtap
control channel.
BUG: unable to handle kernel NULL pointer dereference at (null)
IP: [<fcfc168b>] probe_3607+0x1b/0x620
[stap_efbcdc9d6c2e0a81b0f875b34455f92e_7703]
*pdpt = 0000000031087001 *pde = 00000003fcf21067
Oops: 0000 [#1] SMP
last sysfs file: /sys/module/uprobes/sections/__ksymtab_strings
Modules linked in: stap_efbcdc9d6c2e0a81b0f875b34455f92e_7703(U) uprobes(U)
cpufreq_ondemand acpi_cpufreq mperf ib_ipoib rdma_ucm ib_ucm ib_uverbs ib_umad
rdma_cm ib_cm iw_cm ib_sa ib_mad ib_core ib_addr ipv6 ipmi_si ipmi_msghandler
microcode iTCO_wdt iTCO_vendor_support sg i2c_i801 i2c_core lpc_ich mfd_core
e1000e ptp pps_core ext4 jbd2 mbcache sr_mod cdrom sd_mod crc_t10dif pata_acpi
ata_generic ata_piix dm_mirror dm_region_hash dm_log dm_mod [last unloaded:
stap_efca01cac043d68e8cee73b3a480fe78_7395]
Pid: 7704, comm: towers.x Not tainted 2.6.32-696.6.3.el6.i686 #1 NEC
Express5800/T110b [N8100-1589]/6FXSV00R-MB
EIP: 0060:[<fcfc168b>] EFLAGS: 00210282 CPU: 2
EIP is at probe_3607+0x1b/0x620 [stap_efbcdc9d6c2e0a81b0f875b34455f92e_7703]
EAX: 00000000 EBX: fd1e014c ECX: fcfc5180 EDX: fd1e0000
ESI: bffd5011 EDI: f114dfb4 EBP: fcfc9040 ESP: f114dd84
DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Process towers.x (pid: 7704, ti=f114c000 task=f1142aa0 task.ti=f114c000)
Stack:
1dcd6500 00000000 c0514337 00000000 fd1e0000 c051a80d d1689b60 1dcd6500
<0> d1689b60 f3135d40 bffd5011 f114dfb4 fcfc9040 fcfc5353 00000000 f114ddec
<0> c0ab7a80 48c6a6f2 fd1e0000 f11d0dc0 f114dfb4 f3135d40 c1f45e00 fef8e47e
Call Trace:
[<c0514337>] ? kunmap_high+0x17/0xa0
[<c051a80d>] ? __access_remote_vm+0x15d/0x170
[<fcfc5353>] ? enter_uretprobe_probe+0x1d3/0x3a0
[stap_efbcdc9d6c2e0a81b0f875b34455f92e_7703]
[<fef8e47e>] ? uprobe_report_signal+0x62e/0xa00 [uprobes]
[<c0479a2f>] ? __dequeue_signal+0xdf/0x180
[<c04777e5>] ? recalc_sigpending+0x95/0xb0
[<c0488dc0>] ? run_posix_cpu_timers+0x3a0/0x8f0
[<fef8de50>] ? uprobe_report_signal+0x0/0xa00 [uprobes]
[<c04b88c7>] ? utrace_get_signal+0x257/0x6b0
[<c047a1a3>] ? get_signal_to_deliver+0x2d3/0x460
[<c0409083>] ? do_signal+0x93/0xa90
[<c044c0d2>] ? task_rq_lock+0x42/0x80
[<c0477650>] ? signal_wake_up+0x20/0x40
[<c0478479>] ? __send_signal+0x199/0x300
[<c0469b3e>] ? __do_softirq+0xce/0x1f0
[<c0478616>] ? send_signal+0x36/0x70
[<c04795bb>] ? force_sig_info+0x7b/0xd0
[<c0409af7>] ? do_notify_resume+0x77/0xa0
[<c087e7bc>] ? work_notifysig+0x13/0x1b
Code: fc fc eb c1 c7 83 1c 01 00 00 51 93 fc fc eb b5 55 89 c2 57 56 53 89 c3
83 ec 24 81 c3 4c 01 00 00 89 44 24 10 8b 80 48 01 00 00 <8b> 00 89 c1 c1 f9 1f
89 82 4c 01 00 00 b8 e8 8f fc fc 89 8a 50
EIP: [<fcfc168b>] probe_3607+0x1b/0x620
[stap_efbcdc9d6c2e0a81b0f875b34455f92e_7703] SS:ESP 0068:f114dd84
CR2: 0000000000000000
====
I'm unsure about which test triggers this BUG.
--
You are receiving this mail because:
You are the assignee for the bug.