search for: nmi_handler

...| 20 | | | INFO:rcu_sched_self-detected_stall_on_CPU(t=jiffies_g=c=q=) | 0 | 0 | 1 | | INFO:task_blocked_for_more_than_seconds | 0 | 0 | 2 | | INFO:NMI_handler(arch_trigger_all_cpu_backtrace_handler)took_too_long_to_run:msecs | 0 | 0 | 1 | | Kernel_panic-not_syncing:hung_task:blocked_tasks | 0 | 0 | 1 | | BUG:kernel_test_crashed...

...| 20 | | | INFO:rcu_sched_self-detected_stall_on_CPU(t=jiffies_g=c=q=) | 0 | 0 | 1 | | INFO:task_blocked_for_more_than_seconds | 0 | 0 | 2 | | INFO:NMI_handler(arch_trigger_all_cpu_backtrace_handler)took_too_long_to_run:msecs | 0 | 0 | 1 | | Kernel_panic-not_syncing:hung_task:blocked_tasks | 0 | 0 | 1 | | BUG:kernel_test_crashed...

...| | > | INFO:rcu_sched_self-detected_stall_on_CPU(t=jiffies_g=c=q=) | 0 | 0 | 1 | > | INFO:task_blocked_for_more_than_seconds | 0 | 0 | 2 | > | INFO:NMI_handler(arch_trigger_all_cpu_backtrace_handler)took_too_long_to_run:msecs | 0 | 0 | 1 | > | Kernel_panic-not_syncing:hung_task:blocked_tasks | 0 | 0 | 1 | > | BUG:kernel_test_crashed...

...low+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...

...4: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...

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)

...l 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...

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

...| 30 | | | INFO:rcu_sched_detected_stalls_on_CPUs/tasks:(detected_by,t=jiffies,g=,c=,q=) | 15 | | | INFO:rcu_sched_self-detected_stall_on_CPU(t=jiffies_g=c=q=) | 7 | | | INFO:NMI_handler(arch_trigger_all_cpu_backtrace_handler)took_too_long_to_run:msecs | 7 | | | BUG:kernel_early_hang_without_any_printk_output | 1 | | | page_allocation_failure:order:,mode...

...| 30 | | | INFO:rcu_sched_detected_stalls_on_CPUs/tasks:(detected_by,t=jiffies,g=,c=,q=) | 15 | | | INFO:rcu_sched_self-detected_stall_on_CPU(t=jiffies_g=c=q=) | 7 | | | INFO:NMI_handler(arch_trigger_all_cpu_backtrace_handler)took_too_long_to_run:msecs | 7 | | | BUG:kernel_early_hang_without_any_printk_output | 1 | | | page_allocation_failure:order:,mode...

Greetings, I got the below dmesg and the first bad commit is commit 3ab098df35f8b98b6553edc2e40234af512ba877 Author: Jason Wang <jasowang at redhat.com> Date: Tue Oct 15 11:18:58 2013 +0800 virtio-net: don't respond to cpu hotplug notifier if we're not ready We're trying to re-configure the affinity unconditionally in cpu hotplug callback. This may lead the

Greetings, I got the below dmesg and the first bad commit is commit 3ab098df35f8b98b6553edc2e40234af512ba877 Author: Jason Wang <jasowang at redhat.com> Date: Tue Oct 15 11:18:58 2013 +0800 virtio-net: don't respond to cpu hotplug notifier if we're not ready We're trying to re-configure the affinity unconditionally in cpu hotplug callback. This may lead the