Created attachment 742758 [details] messages and panic backtrace Description of problem: kernel panic at enter_hwbkpt_probe+0x152 while running systemtap Version-Release number of selected component (if applicable): 3.8.9-200.fc18.i686 How reproducible: This problem can be reproduced 100% if I run following systemtap script. Steps to Reproduce: (1) # echo 1 > /proc/sys/kernel/panic_on_oops (2) run following systemtap script #! /usr/bin/env stap probe kernel.data("vm_dirty_ratio").rw { print_backtrace(); } Actual results: Following kernel panic happened. [ 34.688695] cgroup: libvirtd (1250) created nested cgroup for controller "memory" which has incomplete hierarchy support. Nested cgroups may change behavior in the future. [ 34.688988] cgroup: "memory" requires setting use_hierarchy to 1 on the root. [ 34.689571] cgroup: libvirtd (1250) created nested cgroup for controller "devices" which has incomplete hierarchy support. Nested cgroups may change behavior in the future. [ 34.690464] cgroup: libvirtd (1250) created nested cgroup for controller "blkio" which has incomplete hierarchy support. Nested cgroups may change behavior in the future. [ 502.918555] stap_f57c962d222057f5feb8d3523dbda31_7992: systemtap: 2.1/0.155, base: f9381000, memory: 21data/32text/2ctx/2058net/16alloc kb, probes: 1 [ 504.328204] BUG: unable to handle kernel NULL pointer dereference at 00000034 [ 504.329085] IP: [<f9387382>] enter_hwbkpt_probe+0x152/0x350 [stap_f57c962d222057f5feb8d3523dbda31_7992] [ 504.329085] *pde = 00000000 [ 504.329085] Oops: 0000 [#1] SMP [ 504.329085] Modules linked in: stap_f57c962d222057f5feb8d3523dbda31_7992(OF) ebtable_nat michael_mic arc4 ipt_MASQUERADE nf_conntrack_netbios_ns nf_conntrack_broadcast ip6table_mangle ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 iptable_nat nf_nat_ipv4 nf_nat bnep iptable_mangle bluetooth nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ebtable_filter ebtables ip6table_filter ip6_tables be2iscsi iscsi_boot_sysfs bnx2i cnic uio cxgb4i cxgb4 cxgb3i cxgb3 mdio libcxgbi ib_iser rdma_cm ib_addr iw_cm ib_cm ib_sa ib_mad ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi iTCO_wdt iTCO_vendor_support hp_wmi sparse_keymap snd_hda_codec_analog uvcvideo snd_hda_intel coretemp videobuf2_vmalloc snd_hda_codec videobuf2_memops snd_hwdep snd_seq videobuf2_core videodev snd_seq_device microcode [ 504.329085] lib80211_crypt_tkip media snd_pcm wl(POF) snd_page_alloc serio_raw snd_timer lpc_ich cfg80211 snd soundcore sky2 rfkill lib80211 hp_accel lis3lv02d input_polldev uinput i915 i2c_algo_bit drm_kms_helper drm i2c_core wmi video [ 504.329085] Pid: 458, comm: flush-253:0 Tainted: PF O 3.8.9-200.fc18.i686 #1 Hewlett-Packard HP Mini 5101/3632 [ 504.329085] EIP: 0060:[<f9387382>] EFLAGS: 00010046 CPU: 1 [ 504.329085] EIP is at enter_hwbkpt_probe+0x152/0x350 [stap_f57c962d222057f5feb8d3523dbda31_7992] [ 504.329085] EAX: f4646800 EBX: d8dce9aa ECX: 00000000 EDX: 00000000 [ 504.329085] ESI: 00000000 EDI: 00000000 EBP: f47b3cbc ESP: f47b3c90 [ 504.329085] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 504.329085] CR0: 8005003b CR2: 00000034 CR3: 00ce4000 CR4: 000007c0 [ 504.329085] DR0: c0bdd868 DR1: 00000000 DR2: 00000000 DR3: 00000000 [ 504.329085] DR6: ffff0ff0 DR7: 00000400 [ 504.329085] Process flush-253:0 (pid: 458, ti=f47b2000 task=f6917230 task.ti=f47b2000) [ 504.329085] Stack: [ 504.329085] f4c5d9a0 f47b3d10 f4c5d970 00000000 00000001 00000001 0000028e f4646800 [ 504.329085] f9387230 f20ae800 00000000 f47b3d04 c04f4036 00000000 00000001 00000000 [ 504.329085] 00000000 f47b3d54 f47b3e40 f47b3d58 f47b3d64 c047940b ffffffff ffffffff [ 504.329085] Call Trace: [ 504.329085] [<f9387230>] ? _stp_error+0x40/0x40 [stap_f57c962d222057f5feb8d3523dbda31_7992] [ 504.329085] [<c04f4036>] __perf_event_overflow+0xa6/0x270 [ 504.329085] [<c047940b>] ? find_busiest_group+0x2b/0x420 [ 504.329085] [<c04f43bf>] perf_swevent_overflow+0x4f/0xa0 [ 504.329085] [<c04f4516>] perf_swevent_event+0x106/0x110 [ 504.329085] [<c04f4e70>] perf_bp_event+0xa0/0xb0 [ 504.329085] [<c04757a4>] ? dequeue_entity+0x154/0x620 [ 504.329085] [<c0980c96>] hw_breakpoint_exceptions_notify+0x106/0x130 [ 504.329085] [<c047610e>] ? dequeue_task_fair+0x36e/0x6d0 [ 504.329085] [<c0982a53>] notifier_call_chain+0x43/0x60 [ 504.329085] [<c0982a91>] __atomic_notifier_call_chain+0x21/0x30 [ 504.329085] [<c0982abf>] atomic_notifier_call_chain+0x1f/0x30 [ 504.329085] [<c0982afd>] notify_die+0x2d/0x30 [ 504.329085] [<c09800cc>] do_debug+0x8c/0x170 [ 504.329085] [<c097fb8f>] debug_stack_correct+0x30/0x35 [ 504.329085] [<c05000d8>] ? __build_all_zonelists+0x78/0x90 [ 504.329085] [<c0504d4a>] ? global_dirty_limits+0x3a/0x110 [ 504.329085] [<c056ae03>] over_bground_thresh+0x23/0xb0 [ 504.329085] [<c056e3d2>] wb_do_writeback+0x112/0x1c0 [ 504.329085] [<c044c670>] ? __internal_add_timer+0xc0/0xc0 [ 504.329085] [<c056e4f1>] bdi_writeback_thread+0x71/0x1d0 [ 504.329085] [<c056e480>] ? wb_do_writeback+0x1c0/0x1c0 [ 504.329085] [<c045e254>] kthread+0x94/0xa0 [ 504.329085] [<c09863b7>] ret_from_kernel_thread+0x1b/0x28 [ 504.329085] [<c045e1c0>] ? kthread_create_on_node+0xc0/0xc0 [ 504.329085] Code: 00 00 00 00 00 00 c7 80 30 01 00 00 00 00 00 00 c7 40 10 10 27 00 00 c7 80 44 01 00 00 00 00 00 00 c7 80 9c 01 00 00 00 00 00 00 <8b> 4e 34 83 e1 03 83 f9 03 0f 84 23 01 00 00 8b 55 08 89 90 20 [ 504.329085] EIP: [<f9387382>] enter_hwbkpt_probe+0x152/0x350 [stap_f57c962d222057f5feb8d3523dbda31_7992] SS:ESP 0068:f47b3c90 [ 504.329085] CR2: 0000000000000034 ~ Expected results: No panic with any systemtap script. Additional info: vmcore file (23MB) is available, if required.
The same systemtap script didn't panic the system on Fedora 19(Alpha), with kernel 3.9.0-301.fc19.x86_64.
The same systemtap script DID panic the system on Fedora 19(Alpha), with kernel 3.9.0-301.fc19.i686. In other word, I can reproduce this symptom on 32bit system with latest kernel.
The same systemtap script DID oops the system on Fedora 18, with 3.8.11-200.fc18.i686.
crash> dis -r enter_hwbkpt_probe+0x152 0xf855a230 <enter_hwbkpt_probe>: push %ebp 0xf855a231 <enter_hwbkpt_probe+1>: mov %esp,%ebp 0xf855a233 <enter_hwbkpt_probe+3>: push %edi 0xf855a234 <enter_hwbkpt_probe+4>: push %esi (snip) 0xf855a34a <enter_hwbkpt_probe+282>: and $0xfffffffc,%edx 0xf855a34d <enter_hwbkpt_probe+285>: mov %dl,0xc(%eax) 0xf855a350 <enter_hwbkpt_probe+288>: mov 0x8(%ebp),%esi 0xf855a353 <enter_hwbkpt_probe+291>: movl $0x0,0x12c(%eax) 0xf855a35d <enter_hwbkpt_probe+301>: movl $0x0,0x130(%eax) 0xf855a367 <enter_hwbkpt_probe+311>: movl $0x2710,0x10(%eax) 0xf855a36e <enter_hwbkpt_probe+318>: movl $0x0,0x144(%eax) 0xf855a378 <enter_hwbkpt_probe+328>: movl $0x0,0x19c(%eax) 0xf855a382 <enter_hwbkpt_probe+338>: mov 0x34(%esi),%ecx crash> [37718.571019] EIP is at enter_hwbkpt_probe+0x152/0x350 [stap_8783a7847bf638210f944fa0120bf5_30065] [37718.571019] EAX: e2b52800 EBX: e7113568 ECX: 00000000 EDX: 00000000 [37718.571019] ESI: 00000082 EDI: 00000000 EBP: e9329c94 ESP: e9329c68 [37718.571019] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [37718.571019] CR0: 8005003b CR2: 000000b6 CR3: 2c5f7000 CR4: 000007c0 [37718.571019] DR0: c0bdd868 DR1: 00000000 DR2: 00000000 DR3: 00000000 [37718.571019] DR6: ffff0ff0 DR7: 00000400 ECX=00000000
systemtap-runtime-2.1-3.fc18.i686 systemtap-devel-2.1-3.fc18.i686 systemtap-client-2.1-3.fc18.i686 systemtap-sdt-devel-2.1-3.fc18.i686 systemtap-2.1-3.fc18.i686
Filed & fixed as http://sourceware.org/bugzilla/show_bug.cgi?id=15445. Thank you for reporting this problem. The fix is in git systemtap and should be in the next release.
Download git repository and compile latest systemtap. $ /home/iida/systemtap/bin/stap --version Systemtap translator/driver (version 2.2/0.155, commit release-2.1-218-g173a35a) Copyright (C) 2005-2013 Red Hat, Inc. and others This is free software; see the source for copying conditions. enabled features: TR1_UNORDERED_MAP NLS I have confirmed latest systemtap works as expected on F18(i686). No more oops. Thank you.
Thanks a lot for checking!
I know systemtap-2.2 is ready on update-testing. So I have enabled it and tried to install. My original RPMS are systemtap-runtime-2.1-3.fc18.i686 systemtap-2.1-3.fc18.i686 systemtap-devel-2.1-3.fc18.i686 systemtap-debuginfo-2.1-3.fc18.i686 systemtap-client-2.1-3.fc18.i686 systemtap-sdt-devel-2.1-3.fc18.i686 Then I exected # yum update systemtap Then yum selected following files. Updating: systemtap i686 2.2.1-1.fc18 updates-testing 23 k Updating for dependencies: systemtap-client i686 2.2.1-1.fc18 updates-testing 3.4 M systemtap-devel i686 2.2.1-1.fc18 updates-testing 1.4 M systemtap-runtime i686 2.2.1-1.fc18 updates-testing 229 k As you see sytemtap-sdt-devel-2.2.1-1 was NOT on this list. First time, I didn't notice it and type "y" to install these RPMs. But I got following errors. Transaction Check Error: file /usr/share/locale/en/LC_MESSAGES/systemtap.mo from install of systemtap-devel-2.2.1-1.fc18.i686 conflicts with file from package systemtap-sdt-devel-2.1-3.fc18.i686 file /usr/share/locale/fr/LC_MESSAGES/systemtap.mo from install of systemtap-devel-2.2.1-1.fc18.i686 conflicts with file from package systemtap-sdt-devel-2.1-3.fc18.i686 file /usr/share/locale/pl/LC_MESSAGES/systemtap.mo from install of systemtap-devel-2.2.1-1.fc18.i686 conflicts with file from package systemtap-sdt-devel-2.1-3.fc18.i686 file /usr/share/locale/en/LC_MESSAGES/systemtap.mo from install of systemtap-runtime-2.2.1-1.fc18.i686 conflicts with file from package systemtap-sdt-devel-2.1-3.fc18.i686 file /usr/share/locale/fr/LC_MESSAGES/systemtap.mo from install of systemtap-runtime-2.2.1-1.fc18.i686 conflicts with file from package systemtap-sdt-devel-2.1-3.fc18.i686 file /usr/share/locale/pl/LC_MESSAGES/systemtap.mo from install of systemtap-runtime-2.2.1-1.fc18.i686 conflicts with file from package systemtap-sdt-devel-2.1-3.fc18.i686 file /usr/share/locale/en/LC_MESSAGES/systemtap.mo from install of systemtap-client-2.2.1-1.fc18.i686 conflicts with file from package systemtap-sdt-devel-2.1-3.fc18.i686 file /usr/share/locale/fr/LC_MESSAGES/systemtap.mo from install of systemtap-client-2.2.1-1.fc18.i686 conflicts with file from package systemtap-sdt-devel-2.1-3.fc18.i686 file /usr/share/locale/pl/LC_MESSAGES/systemtap.mo from install of systemtap-client-2.2.1-1.fc18.i686 conflicts with file from package systemtap-sdt-devel-2.1-3.fc18.i686 file /usr/share/locale/en/LC_MESSAGES/systemtap.mo from install of systemtap-2.2.1-1.fc18.i686 conflicts with file from package systemtap-sdt-devel-2.1-3.fc18.i686 file /usr/share/locale/fr/LC_MESSAGES/systemtap.mo from install of systemtap-2.2.1-1.fc18.i686 conflicts with file from package systemtap-sdt-devel-2.1-3.fc18.i686 file /usr/share/locale/pl/LC_MESSAGES/systemtap.mo from install of systemtap-2.2.1-1.fc18.i686 conflicts with file from package systemtap-sdt-devel-2.1-3.fc18.i686 It is because the YUM didn't select systemtap-sdt-devel-2.2 as dependency, so systemtap-sdt-devel 2.1 still remain in HD, but rest of the RPMS were going to be 2.2. So it made conflicts. I removed systemtap-sdt-devel-2.1,and I run yum update systemtap again... This time, the update succeeded. I am not sure if it is good idea to set systemtap-sdt-devel as dependency of systemtap RPM. (Not everyone may need it.)
(In reply to masanari iida from comment #9) > It is because the YUM didn't select systemtap-sdt-devel-2.2 as dependency, > so systemtap-sdt-devel 2.1 still remain in HD, but rest of the RPMS were > going to be 2.2. So it made conflicts. This has been fixed for bug 915247. We can't do anything about the old sdt-devel, but the new package won't include the translation files (and doesn't need them), so it won't conflict if the rest of systemtap is a different release.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.