search for: perf_event_nmi_handler

...veau 0000:04:00.0: timeout at /home/pmoreau/projects/nouveau/nouveau/drm/nouveau/nvkm/subdev/bar/g84.c:38/g84_bar_flush()! [ 559.852907] nouveau 0000:04:00.0: fifo: intr 04800000 [ 563.418621] INFO: NMI handler (ghes_notify_nmi) took too long to run: 48.172 msecs [ 563.563141] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 48.172 msecs [ 563.659490] perf: interrupt took too long (376349 > 2500), lowering kernel.perf_event_max_sample_rate to 300 [ 578.942906] NMI watchdog: Watchdog detected hard LOCKUP on cpu 0 [ 578.942909] Modules linked in: netconsole snd_hda_codec_hdmi ipmi_ssif snd_hd...

...event_overflow+0x8c/0x2a0 [ 9227.509797] [<ffffffff8102b9ba>] ? x86_perf_event_set_period+0xca/0x170 [ 9227.509798] [<ffffffff8116b2b4>] perf_event_overflow+0x14/0x20 [ 9227.509800] [<ffffffff81032fda>] intel_pmu_handle_irq+0x1ba/0x3a0 [ 9227.509802] [<ffffffff8102a6db>] perf_event_nmi_handler+0x2b/0x50 [ 9227.509804] [<ffffffff810184c0>] nmi_handle+0x80/0x120 [ 9227.509805] [<ffffffff81018a6a>] default_do_nmi+0x4a/0x140 [ 9227.509806] [<ffffffff81018be8>] do_nmi+0x88/0xd0 [ 9227.509808] [<ffffffff817b3ae1>] end_repeat_nmi+0x1e/0x2e [ 9227.509810] [<ffffff...

...t;] vprintk+0x1c3/0x470 Sep 17 15:26:18 box6 kernel: [ 1948.826078] [<ffffffffa00e7385>] ? vga16fb_imageblit+0x25/0x30 [vga16fb] Sep 17 15:26:18 box6 kernel: [ 1948.826084] [<ffffffff81557efa>] printk +0x41/0x47 Sep 17 15:26:18 box6 kernel: [ 1948.826088] [<ffffffff8155c0ae>] ? perf_event_nmi_handler+0xe/0x60 Sep 17 15:26:18 box6 kernel: [ 1948.826091] [<ffffffff8155bb08>] __die +0x48/0xf0 Sep 17 15:26:18 box6 kernel: [ 1948.826095] [<ffffffff81017108>] die +0x48/0x90 Sep 17 15:26:18 box6 kernel: [ 1948.826098] [<ffffffff8155b7e2>] do_general_protection+0x152/0x160 Sep 17 1...

https://bugs.freedesktop.org/show_bug.cgi?id=70927 Priority: medium Bug ID: 70927 Assignee: nouveau at lists.freedesktop.org Summary: nv50_instobj_wr32 kernel panic Severity: normal Classification: Unclassified OS: Linux (All) Reporter: antoniovazquezblanco at gmail.com Hardware: x86-64 (AMD64)

...rflow+0xa7/0x240 Feb 16 06:07:01 [<ffffffff81119e14>] ? perf_event_update_userpage+0x24/0x110 Feb 16 06:07:01 [<ffffffff81121454>] ? perf_event_overflow+0x14/0x20 Feb 16 06:07:01 [<ffffffff8101e3fb>] ? x86_pmu_handle_irq+0x1eb/0x250 Feb 16 06:07:01 [<ffffffff81535ed9>] ? perf_event_nmi_handler+0x39/0xb0 Feb 16 06:07:01 [<ffffffff81537995>] ? notifier_call_chain+0x55/0x80 Feb 16 06:07:01 [<ffffffff815379fa>] ? atomic_notifier_call_chain+0x1a/0x20 Feb 16 06:07:01 [<ffffffff810a4ede>] ? notify_die+0x2e/0x30 Feb 16 06:07:01 [<ffffffff8153565b>] ? do_nmi+0x1bb/0x34...

NOTE: this is happening on Centos 6 x86_64, 2.6.32-504.3.3.el6.x86_64 not Centos 5 Dell PowerEdge 2970, Seagate SATA drive, non-raid. I have this server which has been dying randomly, with no logs. I had a tail -f over ssh for a week, when this just happened. Feb 8 00:10:21 thirteen-230 kernel: mptscsih: ioc0: attempting task abort! (sc=ffff880057a0a080) Feb 8 00:10:21 thirteen-230 kernel:

...d9/0x160 Jul 21 10:11:42 dioo-XPS kernel: [ 2185.090401] [<ffffffff81177e64>] perf_event_overflow+0x14/0x20 Jul 21 10:11:42 dioo-XPS kernel: [ 2185.090403] [<ffffffff81034d2a>] intel_pmu_handle_irq+0x1da/0x450 Jul 21 10:11:42 dioo-XPS kernel: [ 2185.090406] [<ffffffff8102b60b>] perf_event_nmi_handler+0x2b/0x50 Jul 21 10:11:42 dioo-XPS kernel: [ 2185.090408] [<ffffffff810191d8>] nmi_handle+0x88/0x120 Jul 21 10:11:42 dioo-XPS kernel: [ 2185.090410] [<ffffffff8101974a>] default_do_nmi+0x4a/0x140 Jul 21 10:11:42 dioo-XPS kernel: [ 2185.090411] [<ffffffff810198c8>] do_nmi+0x88/0...

....93: registering with nfnetlink. > > [ 57.780880] ipt_CLUSTERIP: ClusterIP Version 0.8 loaded successfully > > [ 60.506072] u32 classifier > > [ 60.506077] Performance counters on > > [ 60.506078] Actions configured > > [ 118.338005] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 2.220 msecs > > [ 118.338016] perf interrupt took too long (19624 > 2500), lowering kernel.perf_event_max_sample_rate to 50000 > > [ 180.970220] perf interrupt took too long (19751 > 5000), lowering kernel.perf_event_max_sample_rate to 25000 > > &g...

...57.201413] ctnetlink v0.93: registering with nfnetlink. > [ 57.780880] ipt_CLUSTERIP: ClusterIP Version 0.8 loaded successfully > [ 60.506072] u32 classifier > [ 60.506077] Performance counters on > [ 60.506078] Actions configured > [ 118.338005] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 2.220 msecs > [ 118.338016] perf interrupt took too long (19624 > 2500), lowering kernel.perf_event_max_sample_rate to 50000 > [ 180.970220] perf interrupt took too long (19751 > 5000), lowering kernel.perf_event_max_sample_rate to 25000 -Thomas

...57.201413] ctnetlink v0.93: registering with nfnetlink. > [ 57.780880] ipt_CLUSTERIP: ClusterIP Version 0.8 loaded successfully > [ 60.506072] u32 classifier > [ 60.506077] Performance counters on > [ 60.506078] Actions configured > [ 118.338005] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 2.220 msecs > [ 118.338016] perf interrupt took too long (19624 > 2500), lowering kernel.perf_event_max_sample_rate to 50000 > [ 180.970220] perf interrupt took too long (19751 > 5000), lowering kernel.perf_event_max_sample_rate to 25000 -Thomas

Currently the blacklist is maintained by hand in kprobes.c which is separated from the function definition and is hard to catch up the kernel update. To solve this issue, I've tried to implement new NOKPROBE_SYMBOL() macro for making kprobe blacklist at build time. Since the NOKPROBE_SYMBOL() macros can be placed right after the function is defined, it is easy to maintain. This series

Currently the blacklist is maintained by hand in kprobes.c which is separated from the function definition and is hard to catch up the kernel update. To solve this issue, I've tried to implement new NOKPROBE_SYMBOL() macro for making kprobe blacklist at build time. Since the NOKPROBE_SYMBOL() macros can be placed right after the function is defined, it is easy to maintain. This series

Hi, Here is the version 3 of NOKPORBE_SYMBOL series. Currently the blacklist is maintained by hand in kprobes.c which is separated from the function definition and is hard to catch up the kernel update. To solve this issue, I've introduced NOKPROBE_SYMBOL() macro for making kprobe blacklist at build time. Since the NOKPROBE_SYMBOL() macros can be placed right after the function is defined

Hi, Here is the version 3 of NOKPORBE_SYMBOL series. Currently the blacklist is maintained by hand in kprobes.c which is separated from the function definition and is hard to catch up the kernel update. To solve this issue, I've introduced NOKPROBE_SYMBOL() macro for making kprobe blacklist at build time. Since the NOKPROBE_SYMBOL() macros can be placed right after the function is defined