求解答：为何NMI中断里加打印，系统莫名其妙会重启 ？

Question

查看printk注释，其可以在任何上下文调用：
/*
* This is printk.  It can be called from any context.  We want it to work. *
* We try to grab the console_sem.  If we succeed, it's easy - we log the output and
* call the console drivers.  If we fail to get the semaphore we place the output
* into the log buffer and return.  The current holder of the console_sem will
* notice the new output in release_console_sem() and will send it to the
* consoles before releasing the semaphore.
*
* One effect of this deferred printing is that code which calls printk() and
* then changes console_loglevel may break. This is because console_loglevel
* is inspected when the actual printing occurs.
*/

那为何系统又会重启呢？
偶研究了NMI中断机制，查看了整个流程，百思不得其解

您知道么？

Answer 1

这句话有错误吧，printk是会引起调度的

Answer 2

“printk是会引起调度的”
不同意这句，应该不会引起调度的。

LZ看看代码吧，也许是其他地方的问题。

Answer 3

NMI时间过长 导致看门狗硬件启动系统？

Answer 4

NMI时间过长 导致看门狗硬件启动系统？
smalloc 发表于 2011-04-05 16:15

    这个解释倒似乎说的过去