[<prev] [next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.11.1505121449540.15999@vincent-weaver-1.umelst.maine.edu>
Date: Tue, 12 May 2015 14:59:14 -0400 (EDT)
From: Vince Weaver <vincent.weaver@...ne.edu>
To: LKML <linux-kernel@...r.kernel.org>
cc: Stephane Eranian <eranian@...gle.com>,
Peter Zijlstra <peterz@...radead.org>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Jiri Olsa <jolsa@...hat.com>, Ingo Molnar <mingo@...hat.com>,
Paul Mackerras <paulus@...ba.org>
Subject: perf: warning in x86_pmu_start triggered by perf_fuzzer
Hello
I've managed to trigger this one multiple times on my Haswell box running
4.1-rc2. It's not easily reproducible though.
The WARNING in question is
if (WARN_ON_ONCE(!(event->hw.state & PERF_HES_STOPPED)))
return;
These problems I'm seeing now all seem to be weird race conditions, I
should try applying the one mutex locking patch to see if that helps.
[116917.487333] WARNING: CPU: 1 PID: 25348 at arch/x86/kernel/cpu/perf_event.c:1151 x86_pmu_start+0xb2/0x120()
[116917.498346] Modules linked in: fuse snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi x86_pkg_temp_thermal intel_powerclamp snd_hda_intel intel_rapl iosf_mbi snd_hda_controller snd_hda_codec coretemp kvm crct10dif_pclmul crc32_pclmul snd_hda_core ghash_clmulni_intel aesni_intel snd_hwdep aes_x86_64 lrw i915 evdev ppdev psmouse drm_kms_helper iTCO_wdt iTCO_vendor_support snd_pcm gf128mul snd_timer glue_helper ablk_helper snd pcspkr serio_raw soundcore drm cryptd mei_me mei tpm_tis xhci_pci parport_pc i2c_algo_bit button video processor battery i2c_i801 xhci_hcd tpm parport lpc_ich wmi mfd_core sg sr_mod cdrom sd_mod ahci libahci libata ehci_pci ehci_hcd e1000e ptp usbcore scsi_mod crc32c_intel usb_common pps_core thermal fan thermal_sys
[116917.573757] CPU: 1 PID: 25348 Comm: perf_fuzzer Tainted: G W 4.1.0-rc2+ #142
[116917.583317] Hardware name: LENOVO 10AM000AUS/SHARKBAY, BIOS FBKT72AUS 01/26/2014
[116917.592002] ffffffff81a08c08 ffff8800c5c03da8 ffffffff816d51d3 0000000000000000
[116917.600844] 0000000000000000 ffff8800c5c03de8 ffffffff81072dfa 00000001ca10e000
[116917.609672] ffff88011ea4bd80 ffff8801176d9000 0000000000000000 ffff88011eb5ed78
[116917.618465] Call Trace:
[116917.621906] [<ffffffff816d51d3>] dump_stack+0x45/0x57
[116917.628212] [<ffffffff81072dfa>] warn_slowpath_common+0x8a/0xc0
[116917.635426] [<ffffffff81072eea>] warn_slowpath_null+0x1a/0x20
[116917.642471] [<ffffffff8102b762>] x86_pmu_start+0xb2/0x120
[116917.649131] [<ffffffff811663ec>] perf_ioctl+0x48c/0x4d0
[116917.655640] [<ffffffff81062fd9>] ? __do_page_fault+0x159/0x460
[116917.662794] [<ffffffff81201ea0>] do_vfs_ioctl+0x2e0/0x4e0
[116917.669482] [<ffffffff810bb593>] ? up_read+0x23/0x40
[116917.675728] [<ffffffff81063051>] ? __do_page_fault+0x1d1/0x460
[116917.682858] [<ffffffff81202121>] SyS_ioctl+0x81/0xa0
[116917.689077] [<ffffffff816dd1b2>] system_call_fastpath+0x16/0x7a
[116917.696314] ---[ end trace 1f7cf34f6e082bd8 ]---
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists