system is too hot

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

system is too hot

760件の閲覧回数
gravity_one
Contributor III

 

Hi, NXP

pls help me analyze or solve it.

out :

Timeout for IPC response!

System is too hot. GPU3D will work at 1/64 clock.

[  790.966992] ------------[ cut here ]------------
[  790.971656] WARNING: CPU: 0 PID: 28060 at /usr/src/kernel/net/wireless/sme.c:981 __cfg80211_disconnected+0x1d8/0x1e8
[  790.982186] Modules linked in: ieee1609dot3(PO) ieee1609dot4(PO) ieee1609gnl(PO) cw_os(O) cw_llc(O) bcmdhd ip6table_mangle ip6_tables iptable_mangle crc32_ce crct10dif_ce galcore(O) [last unloaded: csdio1]
[  791.000500] CPU: 0 PID: 28060 Comm: kworker/u8:0 Tainted: P        W  O    4.14.98+g5b72df0 #1
[  791.009119] Hardware name: Freescale i.MX8QXP MEK (DT)
[  791.014272] Workqueue: cfg80211 cfg80211_event_work
[  791.019153] task: ffff80007835b600 task.stack: ffff0000146a0000
[  791.025081] PC is at __cfg80211_disconnected+0x1d8/0x1e8
[  791.030398] LR is at cfg80211_process_wdev_events+0x110/0x180
[  791.036146] pc : [<ffff000008d705a0>] lr : [<ffff000008d4b090>] pstate: 80000145
[  791.043547] sp : ffff0000146a3ce0
[  791.046863] x29: ffff0000146a3ce0 x28: 0000000000000000
[  791.052182] x27: ffff8000691c0000 x26: ffff000009222080
[  791.057496] x25: 0000000000000000 x24: dead000000000200
[  791.062813] x23: ffff80006e87d0d8 x22: ffff8000691c0300
[  791.068130] x21: ffff80006e87d0e8 x20: ffff80006e87d000
[  791.073449] x19: ffff8000688b5000 x18: 0000ffffe08e6adf
[  791.078763] x17: 0000ffff86bebe68 x16: ffff000008b9f6c0
[  791.081985] Timeout for IPC response!
[  791.084080] x15: 000000000000000a x14: 0000000000000000
[  791.093054] x13: 0000000000000000 x12: 0000000000000001
[  791.098373] x11: 0000000000000000 x10: 000000000000d080
[  791.103690] x9 : 0000000000000000 x8 : ffff800078d3e500
[  791.109005] x7 : ffff800078008020 x6 : 0000000000000000
[  791.114321] x5 : ffff800078d3e560 x4 : 0000000000000001
[  791.119638] x3 : 0000000000000003 x2 : 0000000000000000
[  791.124957] x1 : ffff8000688b5088 x0 : ffff800075f02000
[  791.130274] Call trace:
[  791.132727] Exception stack(0xffff0000146a3ba0 to 0xffff0000146a3ce0)
[  791.139175] 3ba0: ffff800075f02000 ffff8000688b5088 0000000000000000 0000000000000003
[  791.147009] 3bc0: 0000000000000001 ffff800078d3e560 0000000000000000 ffff800078008020
[  791.154846] 3be0: ffff800078d3e500 0000000000000000 000000000000d080 0000000000000000
[  791.162681] 3c00: 0000000000000001 0000000000000000 0000000000000000 000000000000000a
[  791.170521] 3c20: ffff000008b9f6c0 0000ffff86bebe68 0000ffffe08e6adf ffff8000688b5000
[  791.178353] 3c40: ffff80006e87d000 ffff80006e87d0e8 ffff8000691c0300 ffff80006e87d0d8
[  791.186190] 3c60: dead000000000200 0000000000000000 ffff000009222080 ffff8000691c0000
[  791.194027] 3c80: 0000000000000000 ffff0000146a3ce0 ffff000008d4b090 ffff0000146a3ce0
[  791.201863] 3ca0: ffff000008d705a0 0000000080000145 ffff8000691c0418 ffff000009506000
[  791.209699] 3cc0: ffffffffffffffff ffff8000691c01a8 ffff0000146a3ce0 ffff000008d705a0
[  791.213985] Timeout for IPC response!
[  791.217543] [<ffff000008d705a0>] __cfg80211_disconnected+0x1d8/0x1e8
[  791.227555] [<ffff000008d4b090>] cfg80211_process_wdev_events+0x110/0x180
[  791.234346] [<ffff000008d4b134>] cfg80211_process_rdev_events+0x34/0x70
[  791.240965] [<ffff000008d45c04>] cfg80211_event_work+0x1c/0x30
[  791.246805] [<ffff0000080e7564>] process_one_work+0x1d4/0x348
[  791.252553] [<ffff0000080e7720>] worker_thread+0x48/0x470
[  791.257959] [<ffff0000080eda24>] kthread+0x12c/0x130
[  791.262928] [<ffff000008084ed8>] ret_from_fork+0x10/0x18
[  791.268241] ---[ end trace 403ae0236cda365c ]---
[  791.274689] System is too hot. GPU3D will work at 1/64 clock.
[  792.214603] Dot4_WaveDataTx: 28 callbacks suppressed
[  792.214610] Dot4_WaveDataTx: WAVE data PTP not available > kernel 4.8.0
[  792.741996] NET: Unregistered protocol family 22
Sep 18 07:48:16 ctx0800-c0 systemd[1]: Stopping Load Cohda 1609 stack...
Sep 18 07:48:17 ctx0800-c0 systemd[1]: Stopped Load Cohda 1609 stack.
Sep 18 07:48:18 ctx0800-c0 systemd[1]: Stopping Boot SAF5400 and Setup LLC...
Sep 18 07:48:18 ctx0800-c0 saf5400_stop[7725]:
Sep 18 07:48:18 ctx0800-c0 saf5400_stop[7725]: Removing LLC module
Sep 18 07:48:18 ctx0800-c0 saf5400_stop[7725]: put llc down
Sep 18 07:48:18 ctx0800-c0 saf5400_stop[7725]: remove llc
Sep 18 07:48:18 ctx0800-c0 saf5400_stop[7725]: Module                  Size  Used by
Sep 18 07:48:18 ctx0800-c0 saf5400_stop[7725]: cw_llc                385024  0
Sep 18 07:48:18 ctx0800-c0 saf5400_stop[7725]: bcmdhd               2322432  0
Sep 18 07:48:18 ctx0800-c0 saf5400_stop[7725]: ip6table_mangle        16384  1
Sep 18 07:48:18 ctx0800-c0 saf5400_stop[7725]: ip6_tables             28672  1 ip6table_mangle
Sep 18 07:48:18 ctx0800-c0 saf5400_stop[7725]: iptable_mangle         16384  1
Sep 18 07:48:18 ctx0800-c0 saf5400_stop[7725]: crc32_ce               16384  1
Sep 18 07:48:18 ctx0800-c0 saf5400_stop[7725]: crct10dif_ce           16384  0
Sep 18 07:48:18 ctx0800-c0 saf5400_stop[7725]: galcore               434176  10

root@ctx0800-c0:~#

 

ラベル(1)
0 件の賞賛
返信
1 返信

751件の閲覧回数
Bio_TICFSL
NXP TechSupport
NXP TechSupport

Hello gravity,

This is because that powering down by thermal or sysrq-trigger is directly from kernel space, the Trusty vio services are still alive, then when the callback function is triggered in this power down process, it will fail to remove the vio connection, then the power down process will fail.

The callback function is added for another case at that time, we can remove it to fix this issue without any side effect. In our latest L5.10.35, we don't have this call back function.

Thank you.

0 件の賞賛
返信