Hi Vince,
On Thu, Sep 3, 2015 at 11:04 PM, Vince Weaver <vincent.wea...@maine.edu> wrote:
>
> Hello
>
> running a fresh copy of current git and I can still crash my Haswell test
> machine using the perf_fuzzer.
>
> It looks like the pebs issue still, it triggered the new warning, and
> was stuck looping with these messages until I rebooted the system.
>
I do not have access to my Haswell Desktop machine right. I will run
the test case once I get
access to it again.
>
> [ 1800.285152] ------------[ cut here ]------------
> [ 1800.290757] WARNING: CPU: 0 PID: 0 at
> arch/x86/kernel/cpu/perf_event_intel_ds.c:1210
> intel_pmu_drain_pebs_nhm+0x305/0x320()
> [ 1800.303301] PEBS record without PEBS event! status=2 pebs_enabled=1
> active_mask=200000000
> [ 1800.311916] Modules linked in: binfmt_misc intel_rapl iosf_mbi
> x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul
> crc32_pclmul ghash_clmulni_intel snd_hda_codec_hdmi hmac drbg ansi_cprng i915
> aesni_intel aes_x86_64 snd_hda_codec_realtek snd_hda_codec_generic lrw
> snd_hda_intel snd_hda_codec iTCO_wdt gf128mul drm_kms_helper snd_hda_core
> ppdev iTCO_vendor_support evdev glue_helper ablk_helper cryptd parport_pc
> snd_hwdep snd_pcm snd_timer psmouse tpm_tis tpm drm i2c_algo_bit sg parport
> snd pcspkr video serio_raw processor soundcore mei_me lpc_ich mfd_core mei
> i2c_i801 wmi button battery sr_mod sd_mod cdrom ehci_pci ehci_hcd xhci_pci
> xhci_hcd ahci libahci libata e1000e ptp usbcore crc32c_intel scsi_mod
> pps_core usb_common fan thermal
> [ 1800.390813] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G W 4.2.0+
> #173
> [ 1800.399488] Hardware name: LENOVO 10AM000AUS/SHARKBAY, BIOS FBKT72AUS
> 01/26/2014
> [ 1800.408243] ffffffff81a0d828 ffff88011ea03aa8 ffffffff8169da0c
> ffff88011ea03af0
> [ 1800.417089] ffff88011ea03ae0 ffffffff8106e812 0000000000000001
> ffff880119000000
> [ 1800.426024] ffff88011ea0c120 ffff88011900ffc0 ffff880119000000
> ffff88011ea03b40
> [ 1800.434946] Call Trace:
> [ 1800.438453] <IRQ> [<ffffffff8169da0c>] dump_stack+0x44/0x55
> [ 1800.445504] [<ffffffff8106e812>] warn_slowpath_common+0x82/0xc0
> [ 1800.452832] [<ffffffff8106e89c>] warn_slowpath_fmt+0x4c/0x50
> [ 1800.459879] [<ffffffff8102f7d5>] intel_pmu_drain_pebs_nhm+0x305/0x320
> [ 1800.467725] [<ffffffff810b6b69>] ? __lock_acquire.isra.31+0x349/0xfc0
> [ 1800.475613] [<ffffffff8102ec38>] intel_pmu_drain_pebs_buffer+0x18/0x20
What would help here is if you could get the source line number. You can do that
with gdb:
gdb vmlinux
(gdb) info line *0xffffffff8102ec38
>
> [ 1800.483550] [<ffffffff810b6b69>] ? __lock_acquire.isra.31+0x349/0xfc0
> [ 1800.491334] [<ffffffff81156f2f>] ? perf_event_update_userpage+0xff/0x170
> [ 1800.499471] [<ffffffff814025e4>] ? debug_object_activate+0xe4/0x1c0
> [ 1800.507184] [<ffffffff8103076a>] ? intel_stop_scheduling+0x4a/0x70
> [ 1800.514756] [<ffffffff810289ea>] ? perf_assign_events+0x14a/0x2a0
> [ 1800.522238] [<ffffffff81030373>] intel_pmu_pebs_disable+0xf3/0x110
> [ 1800.529812] [<ffffffff8103108b>] intel_pmu_disable_event+0x11b/0x120
> [ 1800.537551] [<ffffffff810291f9>] x86_pmu_stop+0x69/0xc0
> [ 1800.544106] [<ffffffff8102a36f>] x86_pmu_enable+0x9f/0x2f0
> [ 1800.550894] [<ffffffff811522b7>] perf_pmu_enable.part.78+0x7/0x10
> [ 1800.558425] [<ffffffff81156601>] perf_pmu_enable+0x21/0x30
> [ 1800.565250] [<ffffffff81028c38>] x86_pmu_commit_txn+0x78/0xa0
> [ 1800.572352] [<ffffffff8140258e>] ? debug_object_activate+0x8e/0x1c0
> [ 1800.580035] [<ffffffff810b6b69>] ? __lock_acquire.isra.31+0x349/0xfc0
> [ 1800.587892] [<ffffffff810dc40c>] ? hrtimer_start_range_ns+0x1bc/0x3b0
> [ 1800.595692] [<ffffffff811524f0>] ? event_sched_in.isra.84+0xf0/0x310
> [ 1800.603470] [<ffffffff81154c42>] group_sched_in+0x1a2/0x1c0
> [ 1800.610424] [<ffffffff811558aa>] __perf_event_enable+0x25a/0x290
> [ 1800.617823] [<ffffffff81151d90>] ? cpu_clock_event_start+0x30/0x30
> [ 1800.625417] [<ffffffff81151dca>] remote_function+0x3a/0x40
> [ 1800.632238] [<ffffffff810efcef>] flush_smp_call_function_queue+0x7f/0x160
> [ 1800.640448] [<ffffffff810f06b3>]
> generic_smp_call_function_single_interrupt+0x13/0x60
> [ 1800.649816] [<ffffffff810494a4>]
> smp_trace_call_function_single_interrupt+0x34/0xb0
> [ 1800.658950] [<ffffffff816a6332>]
> trace_call_function_single_interrupt+0x82/0x90
> [ 1800.667678] <EOI> [<ffffffff81541890>] ? cpuidle_enter_state+0x130/0x270
> [ 1800.676002] [<ffffffff8154186b>] ? cpuidle_enter_state+0x10b/0x270
> [ 1800.683645] [<ffffffff81541a07>] cpuidle_enter+0x17/0x20
> [ 1800.690274] [<ffffffff810afec2>] call_cpuidle+0x32/0x60
> [ 1800.696781] [<ffffffff815419e3>] ? cpuidle_select+0x13/0x20
> [ 1800.703655] [<ffffffff810b0106>] cpu_startup_entry+0x216/0x2d0
> [ 1800.710809] [<ffffffff81693798>] rest_init+0xb8/0xc0
> [ 1800.716949] [<ffffffff81d41f74>] start_kernel+0x447/0x454
> [ 1800.723593] [<ffffffff81d41120>] ? early_idt_handler_array+0x120/0x120
> [ 1800.731414] [<ffffffff81d41339>] x86_64_start_reservations+0x2a/0x2c
> [ 1800.739055] [<ffffffff81d41476>] x86_64_start_kernel+0x13b/0x14a
> [ 1800.746311] ---[ end trace 852faffdf2d3f87f ]---
> [ 1800.751912] ------------[ cut here ]------------
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
