Linux kernel 内核死机-不同步：看门狗检测到硬锁定

谁能帮帮我，为什么我会撞车

[2324956.184374] Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 1
[2324956.184374] Pid: 0, comm: kworker/0:0 Tainted: P            3.1.10-gb20-default #1
[2324956.184374] Call Trace:
[2324956.184374]  [<ffffffff81003add>] dump_trace+0x98/0x223
[2324956.184374]  [<ffffffff813dc659>] dump_stack+0x69/0x6f
[2324956.184374]  [<ffffffff813def08>] panic+0xa4/0x1b4
[2324956.184374]  [<ffffffff81094b48>] watchdog_overflow_callback+0x79/0x9e
[2324956.184374]  [<ffffffff810b66b5>] __perf_event_overflow+0xf9/0x185
[2324956.184374]  [<ffffffff81010a2c>] intel_pmu_handle_irq+0x15d/0x1be
[2324956.184374]  [<ffffffff813f375b>] perf_event_nmi_handler+0x3e/0x87
[2324956.184374]  [<ffffffff813f4c0f>] notifier_call_chain+0x2e/0x5b
[2324956.184374]  [<ffffffff813f4c76>] __atomic_notifier_call_chain+0x3a/0x4d
[2324956.184374]  [<ffffffff813f4cc1>] notify_die+0x2d/0x32
[2324956.184374]  [<ffffffff813f2bbb>] default_do_nmi+0x29/0x1b5
[2324956.184374]  [<ffffffff813f2eb7>] do_nmi+0x47/0x6f
[2324956.184374]  [<ffffffff813f2a30>] nmi+0x20/0x30
[2324956.184374]  [<ffffffff8106b725>] arch_local_irq_save+0x1/0x17
[2324956.184374]  [<ffffffff813f1e9b>] _raw_spin_lock_irqsave+0xf/0x39
[2324956.184374]  [<ffffffff8105d9b7>] down_trylock+0xb/0x29
[2324956.184374]  [<ffffffff810409c2>] console_trylock+0xf/0x47
[2324956.184374]  [<ffffffff81040dc9>] console_unlock+0x100/0x129
[2324956.184374]  [<ffffffff8104120b>] vprintk+0x348/0x394
[2324956.184374]  [<ffffffff813df06b>] printk+0x53/0x58
[2324956.184374]  [<ffffffff81359902>] ip_handle_martian_source+0x6d/0xf6
[2324956.184374]  [<ffffffff8135b980>] ip_route_input_slow+0x45d/0x462
[2324956.184374]  [<ffffffff8135c02f>] ip_route_input_common+0x217/0x231
[2324956.184374]  [<ffffffff8137e995>] arp_process+0x181/0x4ac
[2324956.184374]  [<ffffffff81337bf5>] __netif_receive_skb+0x317/0x36b
[2324956.184374]  [<ffffffff81337b44>] __netif_receive_skb+0x266/0x36b
[2324956.184374]  [<ffffffff81339722>] netif_receive_skb+0x7e/0x84
[2324956.184374]  [<ffffffff8133979e>] napi_skb_finish+0x1c/0x31
[2324956.184374]  [<ffffffffa02e1dee>] igb_clean_rx_irq+0x30d/0x39e [igb]
[2324956.184374]  [<ffffffffa02e1ecd>] igb_poll+0x4e/0x74 [igb]
[2324956.184374]  [<ffffffff81339c88>] net_rx_action+0x65/0x178
[2324956.184374]  [<ffffffff81045c73>] __do_softirq+0xb2/0x19d
[2324956.184374]  [<ffffffff813f9aac>] call_softirq+0x1c/0x30
[2324956.184374]  [<ffffffff81003931>] do_softirq+0x3c/0x7b
[2324956.184374]  [<ffffffff81045f98>] irq_exit+0x3c/0xac
[2324956.184374]  [<ffffffff81003655>] do_IRQ+0x82/0x98
[2324956.184374]  [<ffffffff813f24ee>] common_interrupt+0x6e/0x6e
[2324956.184374]  [<ffffffff8123f91d>] intel_idle+0xdd/0x104
[2324956.184374]  [<ffffffff8130b76b>] cpuidle_idle_call+0xdf/0x181
[2324956.184374]  [<ffffffff81001201>] cpu_idle+0x56/0xa9

[2324956.184374]内核死机-不同步：看门狗检测到cpu 1上的硬锁定
[2324956.184374]Pid:0，comm:kworker/0:0受污染：p3.1.10-gb20-default#1
[2324956.184374]呼叫跟踪：
[2324956.184374][]转储跟踪+0x98/0x223
[2324956.184374][]转储堆栈+0x69/0x6f
[2324956.184374][]死机+0xa4/0x1b4
[2324956.184374][]看门狗溢出回调+0x79/0x9e
[2324956.184374][]性能事件溢出+0xf9/0x185
[2324956.184374][]英特尔pmu句柄irq+0x15d/0x1be
[2324956.184374][]性能事件nmi处理程序+0x3e/0x87
[2324956.184374][]通知程序调用链+0x2e/0x5b
[2324956.184374][]原子通知程序调用链+0x3a/0x4d
[2324956.184374][]通知模具+0x2d/0x32
[2324956.184374][]默认的nmi+0x29/0x1b5
[2324956.184374][]不使用nmi+0x47/0x6f
[2324956.184374][]nmi+0x20/0x30
[2324956.184374][]局部irq保存+0x1/0x17
[2324956.184374][]原始旋转锁定irqsave+0xf/0x39
[2324956.184374][]向下锁定+0xb/0x29
[2324956.184374][]控制台锁定+0xf/0x47
[2324956.184374][]控制台解锁+0x100/0x129
[2324956.184374][]vprintk+0x348/0x394
[2324956.184374][]打印K+0x53/0x58
[2324956.184374][]ip_句柄_火星_源+0x6d/0xf6
[2324956.184374][]ip路由输入慢+0x45d/0x462
[2324956.184374][]ip路由输入公共+0x217/0x231
[2324956.184374][]arp_进程+0x181/0x4ac
[2324956.184374][]网络接收skb+0x317/0x36b
[2324956.184374][]网络接收skb+0x266/0x36b
[2324956.184374][]网络接收skb+0x7e/0x84
[2324956.184374][]napi_skb_饰面+0x1c/0x31
[2324956.184374][]igb_清洁_接收_irq+0x30d/0x39e[igb]
[2324956.184374][]igb_poll+0x4e/0x74[igb]
[2324956.184374][]净接收动作+0x65/0x178
[2324956.184374][]软件IRQ+0xb2/0x19d
[2324956.184374][]呼叫软件IRQ+0x1c/0x30
[2324956.184374][]不使用软件Q+0x3c/0x7b
[2324956.184374][]irq_出口+0x3c/0xac
[2324956.184374][]do_IRQ+0x82/0x98
[2324956.184374][]公共中断+0x6e/0x6e
[2324956.184374][]英特尔空闲+0xdd/0x104
[2324956.184374][]cpuidle_idle_call+0xdf/0x181
[2324956.184374][]cpu_空闲+0x56/0xa9

只知道调用堆栈就调试问题？我们不是魔术师。在任何情况下，我们都不会调试3d party产品的服务。罪魁祸首可能是网卡的驱动程序，但这只是一个猜测。您看到的最有可能是硬锁症状-正如您在内核中的watchdog_overflow_回调实现（以及堆栈中的任何其他函数）中看到的，当igb想要写入一些日志时，cpu被阻塞（很可能是因为设置了CONFIG\u IP\u ROUTE\u VERBOSE）。这并不意味着这个特定的调用堆栈向您显示了一个罪魁祸首，而是一个症状-您需要知道在其他内核线程中发生了什么。@RyszardGrzesica谢谢，但问题是由于最长的ISR而发生的。console_unlock（）函数正在从ISR调用，强烈建议不要使用ISR的任何阻塞函数。这个困难的查找问题是因为火星源的洪水泛滥。