Fri May 22 02:40:01 2020 kern.info kernel: [ 20.024000] potentially unexpected fatal signal 11.
Fri May 22 02:40:01 2020 kern.warn kernel: [ 20.036000] CPU: 0 PID: 1142 Comm: check_forver Tainted: G O 3.10.14 #10
Fri May 22 02:40:01 2020 kern.warn kernel: [ 20.048000] task: 83f8b9e8 ti: 8310a000 task.ti: 8310a000
Fri May 22 02:40:01 2020 kern.warn kernel: [ 20.060000] $ 0 : 00000000 77967570 00412060 00414000
Fri May 22 02:40:01 2020 kern.warn kernel: [ 20.072000] $ 4 : 00000001 00001fa0 fffffffc 00000049
Fri May 22 02:40:01 2020 kern.warn kernel: [ 20.080000] $ 8 : 00000000 00000fa6 800a0ee8 fffffff0
Fri May 22 02:40:01 2020 kern.warn kernel: [ 20.092000] $12 : 00000000 00000002 00000000 00410000
Fri May 22 02:40:01 2020 kern.warn kernel: [ 20.104000] $16 : 779a7fec 00412068 7f8109c8 ffffffff
Fri May 22 02:40:01 2020 kern.warn kernel: [ 20.112000] $20 : 77a633
potentially unexpected fatal signal 11( call fclose(fd) twice)
最新推荐文章于 2024-06-18 08:55:58 发布
这篇博客记录了一次Linux系统出现'potentially unexpected fatal signal 11'的问题,详细日志显示在kernel.warn和kernel.info级别。问题可能由check_forver进程中重复调用fclose(fd)导致。分析了可能的段错误原因,并提出了相应的解决方案。
摘要由CSDN通过智能技术生成