며칠 전부터 갑자기 가끔 발생하는 이상한 문제에 직면하기 시작했습니다. 비디오를 스트리밍하거나 브라우저(Chrome 또는 Firefox)에서 음성 통화를 하는 경우 가끔 시스템이 완전히 정지되고 오디오의 마지막 0.5초 정도가 반복해서 재생됩니다. 전원 버튼을 길게 눌러 강제 종료해야 합니다. 지난번에 이런 일이 발생했을 때 나는 이 문제 바로 앞에 있는 syslog 항목을 발견했습니다.
May 12 15:15:22 Machine gnome-shell[12407]: [19904:20:0512/151522.107395:ERROR:webrtc_video_engine.cc(3350)] Absent receive stream; ignoring clearing encoded frame sink for ssrc 0
May 12 15:15:44 Machine gnome-shell[12407]: [19904:20:0512/151544.534097:ERROR:webrtc_video_engine.cc(3350)] Absent receive stream; ignoring clearing encoded frame sink for ssrc 0
May 12 15:16:08 Machine gnome-shell[2103]: ../clutter/clutter/clutter-actor.c:10558: The clutter_actor_set_allocation() function can only be called from within the implementation of the ClutterActor::allocate() virtual function.
May 12 15:16:29 Machine gnome-shell[2103]: ../clutter/clutter/clutter-actor.c:10558: The clutter_actor_set_allocation() function can only be called from within the implementation of the ClutterActor::allocate() virtual function.
May 12 15:17:01 Machine CRON[20644]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 12 15:17:34 Machine gnome-shell[12407]: [19904:20:0512/151734.483733:ERROR:webrtc_video_engine.cc(3350)] Absent receive stream; ignoring clearing encoded frame sink for ssrc 0
May 12 15:19:21 Machine gnome-shell[12407]: [19904:20:0512/151921.527291:ERROR:webrtc_video_engine.cc(3350)] Absent receive stream; ignoring clearing encoded frame sink for ssrc 0
May 12 15:20:08 Machine gnome-shell[12407]: [19904:20:0512/152008.433602:ERROR:webrtc_video_engine.cc(3350)] Absent receive stream; ignoring clearing encoded frame sink for ssrc 0
May 12 15:20:55 Machine gnome-shell[2103]: ../clutter/clutter/clutter-actor.c:10558: The clutter_actor_set_allocation() function can only be called from within the implementation of the ClutterActor::allocate() virtual function.
May 12 15:24:32 Machine kernel: [12112.697501] perf: interrupt took too long (3145 > 3126), lowering kernel.perf_event_max_sample_rate to 63500
May 12 15:26:18 Machine gnome-shell[2103]: message repeated 3 times: [ ../clutter/clutter/clutter-actor.c:10558: The clutter_actor_set_allocation() function can only be called from within the implementation of the ClutterActor::allocate() virtual function.]
May 12 15:30:01 Machine CRON[20950]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
관련이 있는지는 확실하지 않지만 뚜껑을 닫을 때 가끔 시스템이 정지되기도 합니다. 그리고 제가 겪은 문제는 이전의 문제와 매우 유사합니다.이 게시물. 또한 통합 Intel GPU 외에 전용 AMD Radeon GPU가 있는데 WiFi에 문제가 발생한 적도 있습니다. 저는 syslog 파일이 그렇게 커지지 않도록 문제를 해결하기 전에 엄청난 시스템 로그 문제에 직면했습니다. 하지만 유일한 문제는 시스템이 완전히 정지되기 때문에 RAM과 스왑이 완전히 채워졌는지 확인할 기회가 없다는 것입니다. 그리고 주어진 해결책은 나에게 적용되지 않습니다.
관련이 있는 경우 최근에 직면했습니다.이것잘못된 5.8.0-50 커널 업그레이드로 인한 문제. 이 문제는 5.8.0-43 커널로 돌아가서 해결되었습니다.
업데이트: 아직 해결책이 없으며 가끔 시스템 정지 현상이 계속 발생합니다. 아무것도 스트리밍되지 않는데도 가끔 발생하는 현상이 있어서 흔한 현상은 찾을 수 없습니다. Firefox가 실행 중일 때 세 번, Chrome이 실행 중일 때 한 번 발생했습니다. 또한 GNOME과 함께 KDE Plasma가 있는데 KDE Plasma에서 문제가 더 자주 발생하는 것 같습니다. 그리고 아마도 정지 후 하드 재부팅을 수행한 후 WiFi가 작동하지 않는 일이 두 번 발생했기 때문에 아마도 내 WiFi와 약간의 연결이 있을 것입니다. 이중 부팅이 있고 Windows로 부팅한 다음 Ubuntu로 다시 부팅하면 WiFi가 수정됩니다.
업데이트: 직감적으로 이전 커널로 돌아가기로 결정했고 하루나 이틀 동안은 괜찮았지만 문제는 사라지지 않았습니다. 이 문제는 여전히 발생하며 비디오가 재생되지 않는 한 거의 발생하지 않기 때문에 비디오를 실행하는 것은 분명히 그것과 관련이 있습니다. 시스템 로그에 문제를 나타내는 zilch가 있습니다.
업데이트: 짧은 시간 동안 여러 번의 충돌이 발생했습니다. 그 중 하나 직전에 WiFi가 세션 중간에 작동을 멈췄습니다(이번에는 시스템이 자체적으로 재부팅되었습니다). 로그는 다음과 같습니다.
May 28 13:13:04 Machine wpa_supplicant[1103]: wlp8s0: CTRL-EVENT-BEACON-LOSS
May 28 13:13:05 Machine kernel: [ 382.206213] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:05 Machine wpa_supplicant[1103]: wlp8s0: CTRL-EVENT-DISCONNECTED bssid=d8:32:14:ac:c3:51 reason=4 locally_generated=1
May 28 13:13:05 Machine NetworkManager[1080]: <warn> [1622187785.4714] sup-iface[0x5643f88e0120,wlp8s0]: connection disconnected (reason -4)
May 28 13:13:05 Machine kernel: [ 382.386690] ath: phy0: Chip reset failed
May 28 13:13:05 Machine kernel: [ 382.386692] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:05 Machine wpa_supplicant[1103]: wlp8s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
May 28 13:13:05 Machine NetworkManager[1080]: <info> [1622187785.5013] device (wlp8s0): supplicant interface state: completed -> disconnected
May 28 13:13:05 Machine NetworkManager[1080]: <info> [1622187785.5014] device (p2p-dev-wlp8s0): supplicant management interface state: completed -> disconnected
May 28 13:13:05 Machine kernel: [ 382.499354] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:05 Machine NetworkManager[1080]: <info> [1622187785.7671] device (wlp8s0): supplicant interface state: disconnected -> scanning
May 28 13:13:05 Machine NetworkManager[1080]: <info> [1622187785.7671] device (p2p-dev-wlp8s0): supplicant management interface state: disconnected -> scanning
May 28 13:13:05 Machine kernel: [ 382.682440] ath: phy0: Chip reset failed
May 28 13:13:05 Machine kernel: [ 382.682444] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:05 Machine kernel: [ 382.694287] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:05 Machine kernel: [ 382.875265] ath: phy0: Chip reset failed
May 28 13:13:05 Machine kernel: [ 382.875269] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:05 Machine kernel: [ 382.886876] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:06 Machine kernel: [ 383.067340] ath: phy0: Chip reset failed
May 28 13:13:06 Machine kernel: [ 383.067343] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:06 Machine kernel: [ 383.078891] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:06 Machine kernel: [ 383.259781] ath: phy0: Chip reset failed
May 28 13:13:06 Machine kernel: [ 383.259786] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:06 Machine kernel: [ 383.271428] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:06 Machine kernel: [ 383.452775] ath: phy0: Chip reset failed
May 28 13:13:06 Machine kernel: [ 383.452779] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:06 Machine kernel: [ 383.464488] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:06 Machine gnome-shell[2785]: [2778:2903:0528/131306.670523:ERROR:connection_factory_impl.cc(429 )] Failed to connect to MCS endpoint with error -106
May 28 13:13:06 Machine kernel: [ 383.645343] ath: phy0: Chip reset failed
May 28 13:13:06 Machine kernel: [ 383.645349] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:06 Machine kernel: [ 383.656982] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:06 Machine kernel: [ 383.837653] ath: phy0: Chip reset failed
May 28 13:13:06 Machine kernel: [ 383.837655] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:06 Machine kernel: [ 383.849256] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:07 Machine kernel: [ 384.029730] ath: phy0: Chip reset failed
May 28 13:13:07 Machine kernel: [ 384.029732] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:07 Machine kernel: [ 384.041264] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:07 Machine kernel: [ 384.221517] ath: phy0: Chip reset failed
May 28 13:13:07 Machine kernel: [ 384.221520] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:07 Machine kernel: [ 384.233066] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:07 Machine kernel: [ 384.413455] ath: phy0: Chip reset failed
May 28 13:13:07 Machine kernel: [ 384.413457] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:07 Machine kernel: [ 384.425027] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:07 Machine kernel: [ 384.606230] ath: phy0: Chip reset failed
May 28 13:13:07 Machine kernel: [ 384.606234] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:07 Machine kernel: [ 384.617913] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:07 Machine kernel: [ 384.827768] ath: phy0: Chip reset failed
May 28 13:13:07 Machine kernel: [ 384.827772] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:07 Machine kernel: [ 384.839466] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:08 Machine kernel: [ 385.021760] ath: phy0: Chip reset failed
May 28 13:13:08 Machine kernel: [ 385.021764] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:08 Machine kernel: [ 385.033343] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:08 Machine kernel: [ 385.214743] ath: phy0: Chip reset failed
May 28 13:13:08 Machine kernel: [ 385.214748] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:08 Machine kernel: [ 385.226332] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:08 Machine kernel: [ 385.408193] ath: phy0: Chip reset failed
May 28 13:13:08 Machine kernel: [ 385.408198] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:08 Machine kernel: [ 385.419929] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:08 Machine kernel: [ 385.602564] ath: phy0: Chip reset failed
May 28 13:13:08 Machine kernel: [ 385.602568] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:08 Machine kernel: [ 385.614334] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:08 Machine kernel: [ 385.796999] ath: phy0: Chip reset failed
May 28 13:13:08 Machine kernel: [ 385.797003] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:08 Machine kernel: [ 385.808712] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:09 Machine kernel: [ 385.989881] ath: phy0: Chip reset failed
May 28 13:13:09 Machine kernel: [ 385.989885] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:09 Machine kernel: [ 386.001417] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:09 Machine kernel: [ 386.181595] ath: phy0: Chip reset failed
May 28 13:13:09 Machine kernel: [ 386.181598] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:09 Machine kernel: [ 386.193159] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:09 Machine kernel: [ 386.373430] ath: phy0: Chip reset failed
May 28 13:13:09 Machine kernel: [ 386.373433] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:09 Machine kernel: [ 386.385040] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:09 Machine kernel: [ 386.566223] ath: phy0: Chip reset failed
May 28 13:13:09 Machine kernel: [ 386.566227] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:09 Machine kernel: [ 386.577874] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:09 Machine kernel: [ 386.759163] ath: phy0: Chip reset failed
May 28 13:13:09 Machine kernel: [ 386.759167] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:09 Machine kernel: [ 386.770887] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:10 Machine kernel: [ 386.953264] ath: phy0: Chip reset failed
May 28 13:13:10 Machine kernel: [ 386.953268] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:10 Machine kernel: [ 386.965018] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:10 Machine kernel: [ 387.146871] ath: phy0: Chip reset failed
May 28 13:13:10 Machine kernel: [ 387.146875] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:10 Machine kernel: [ 387.158537] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:10 Machine kernel: [ 387.366195] ath: phy0: Chip reset failed
May 28 13:13:10 Machine kernel: [ 387.366199] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:10 Machine kernel: [ 387.377851] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:10 Machine kernel: [ 387.560208] ath: phy0: Chip reset failed
May 28 13:13:10 Machine kernel: [ 387.560213] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:10 Machine kernel: [ 387.571827] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:10 Machine kernel: [ 387.753678] ath: phy0: Chip reset failed
May 28 13:13:10 Machine kernel: [ 387.753682] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:10 Machine kernel: [ 387.765389] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:11 Machine kernel: [ 387.947248] ath: phy0: Chip reset failed
May 28 13:13:11 Machine kernel: [ 387.947252] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:11 Machine kernel: [ 387.958835] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:11 Machine kernel: [ 388.139488] ath: phy0: Chip reset failed
May 28 13:13:11 Machine kernel: [ 388.139492] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:11 Machine kernel: [ 388.151087] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:11 Machine kernel: [ 388.331842] ath: phy0: Chip reset failed
May 28 13:13:11 Machine kernel: [ 388.331847] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:11 Machine kernel: [ 388.343403] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:11 Machine kernel: [ 388.524071] ath: phy0: Chip reset failed
May 28 13:13:11 Machine kernel: [ 388.524076] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:11 Machine kernel: [ 388.535694] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:11 Machine kernel: [ 388.716655] ath: phy0: Chip reset failed
May 28 13:13:11 Machine kernel: [ 388.716660] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:11 Machine kernel: [ 388.728373] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:11 Machine kernel: [ 388.909853] ath: phy0: Chip reset failed
May 28 13:13:11 Machine kernel: [ 388.909857] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:12 Machine kernel: [ 388.921631] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:12 Machine kernel: [ 389.103311] ath: phy0: Chip reset failed
May 28 13:13:12 Machine kernel: [ 389.103315] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:12 Machine kernel: [ 389.114925] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:12 Machine kernel: [ 389.296130] ath: phy0: Chip reset failed
May 28 13:13:12 Machine kernel: [ 389.296134] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:12 Machine kernel: [ 389.307803] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:12 Machine kernel: [ 389.488445] ath: phy0: Chip reset failed
May 28 13:13:12 Machine kernel: [ 389.488449] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:12 Machine kernel: [ 389.500061] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:12 Machine kernel: [ 389.681076] ath: phy0: Chip reset failed
May 28 13:13:12 Machine kernel: [ 389.681080] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:12 Machine kernel: [ 389.692809] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:12 Machine kernel: [ 389.874830] ath: phy0: Chip reset failed
May 28 13:13:12 Machine kernel: [ 389.874844] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:12 Machine kernel: [ 389.886718] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:13 Machine kernel: [ 390.068907] ath: phy0: Chip reset failed
May 28 13:13:13 Machine kernel: [ 390.068912] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:13 Machine kernel: [ 390.080601] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:13 Machine kernel: [ 390.262758] ath: phy0: Chip reset failed
May 28 13:13:13 Machine kernel: [ 390.262762] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:13 Machine kernel: [ 390.274446] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
마지막 문제는 내가 로그인했을 때 발생했기 때문에(데스크톱 화면이 로드되지도 않았음) 시스템 과열이 그것과 관련이 있는 것으로 의심됩니다. 노트북을 20분 동안 꺼두었다가 다시 시작했는데 지금까지 충돌이 발생하지 않았습니다. 소스를 찾아내는 데 도움이 될 경우를 대비해 충돌이 발생하기 전의 또 다른 로그 항목은 다음과 같습니다.
May 28 13:20:17 Machine gnome-shell[3664]: libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
May 28 13:20:18 Machine gnome-shell[3664]: [3704:3704:0528/132018.336942:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
그로부터 몇 분 후의 내용은 다음과 같습니다.
May 28 13:27:04 Machine systemd[1]: Starting Manage, Install and Generate Color Profiles...
May 28 13:27:04 Machine gnome-session-binary[1482]: Entering running state
May 28 13:27:04 Machine gsd-media-keys[1852]: Failed to grab accelerator for keybinding settingslayback-repeat
May 28 13:27:04 Machine gsd-media-keys[1852]: Failed to grab accelerator for keybinding settings:rfkill
May 28 13:27:04 Machine gsd-media-keys[1852]: Failed to grab accelerator for keybinding settings:hibernate
May 28 13:27:04 Machine gsd-media-keys[1852]: Failed to grab accelerator for keybinding settingslayback-random
May 28 13:27:04 Machine dbus-daemon[1100]: [system] Successfully activated service 'org.freedesktop.ColorManager'
May 28 13:27:04 Machine systemd[1]: Started Manage, Install and Generate Color Profiles.
May 28 13:27:04 Machine xbrlapi.desktop[2027]: openConnection: connect: No such file or directory
May 28 13:27:04 Machine xbrlapi.desktop[2027]: cannot connect to braille devices daemon brltty at :0
May 28 13:27:05 Machine org.gnome.Shell.desktop[2034]: The XKEYBOARD keymap compiler (xkbcomp) reports:
May 28 13:27:05 Machine org.gnome.Shell.desktop[2034]: > Warning: Unsupported maximum keycode 569, clipping.
May 28 13:27:05 Machine org.gnome.Shell.desktop[2034]: > X11 cannot support keycodes above 255.
May 28 13:27:05 Machine org.gnome.Shell.desktop[2034]: > Internal error: Could not resolve keysym Invalid
May 28 13:27:05 Machine org.gnome.Shell.desktop[2034]: Errors from xkbcomp are not fatal to the X server
May 28 13:27:07 Machine gnome-shell[1542]: Warning: Failed to start gsd-xsettings
May 28 13:27:08 Machine org.gnome.Shell.desktop[1542]: libinput error: client bug: timer event5 keyboard: scheduled expiry is in the past (-74ms), your system is too slow
May 28 13:27:08 Machine gnome-shell[1542]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 24]: reference to undefined property "MetaWindowXwayland"
업데이트: Ubuntu 20.04(커널을 5.8.0-53으로 업그레이드)를 다시 설치해도 이 문제가 지속됩니다. 어제 재설치했는데 오늘 노트북 덮개를 열고 Chrome에서 탭 몇 개를 연 후 첫 번째 시스템이 정지되었습니다(브라우저는 이미 열려 있었습니다). 도대체 무슨 일이 일어나고 있는지, 왜 도움을 줄 수 없는지 모르겠습니다.
업데이트: 얼마 전에 저는 노트북 덮개를 닫았습니다(그런 일이 발생하면 시스템이 일시 중지되도록 설정되지 않았습니다). 열어보니 자체적으로 다시 시작되는 것 같습니다. 그 무렵에 다음과 같은 로그 항목을 발견했습니다.
Jun 2 18:15:49 Machine thermald[849]: sensor id 4 : No temp sysfs for reading raw tempJun 2 18:23:11 Machine kernel: [ 51.336014] Freezing user space processes ... (elapsed 0.110 seconds) done.
Jun 2 18:23:11 Machine kernel: [ 51.446664] OOM killer disabled.
Jun 2 18:23:11 Machine kernel: [ 51.446667] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Jun 2 18:23:11 Machine kernel: [ 51.448174] printk: Suspending console(s) (use no_console_suspend to debug)
Jun 2 18:23:11 Machine kernel: [ 51.599021] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 2 18:23:11 Machine kernel: [ 51.685897] sd 0:0:0:0: [sda] Stopping disk
Jun 2 18:23:11 Machine kernel: [ 51.930059] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0
Jun 2 18:23:11 Machine kernel: [ 51.959324] [drm] PCIE GART of 2048M enabled (table at 0x00000000001D6000).
또 다른 항목은 다음과 같습니다.
Jun 2 18:23:13 Machine thermald[849]: I/O warning : failed to load external entity "/etc/thermald/thermal-conf.xml"
Jun 2 18:23:13 Machine thermald[849]: error: could not parse file /etc/thermald/thermal-conf.xml
Jun 2 18:23:13 Machine thermald[849]: I/O warning : failed to load external entity "/etc/thermald/thermal-conf.xml"
Jun 2 18:23:13 Machine thermald[849]: error: could not parse file /etc/thermald/thermal-conf.xml
Jun 2 18:23:13 Machine thermald[849]: I/O warning : failed to load external entity "/etc/thermald/thermal-conf.xml"
Jun 2 18:23:13 Machine thermald[849]: error: could not parse file /etc/thermald/thermal-conf.xml
이 열 오류를 찾아봤지만 구현할 수 있는 명확한 해결책을 찾지 못했습니다.
Gnome과 KDE Plasma를 모두 설치하면 이 문제가 발생할 가능성이 있습니까? 특히 sddm이 아닌 gdm3을 디스플레이 관리자로 설정했기 때문에?
업데이트: 아직 이에 대한 해결책이 없으며 문제가 사라지지 않았습니다. 더 무거운 웹사이트가 포함된 약 5~6개의 Chrome 탭(이전에도 사용했던)이 있을 때 메모리가 90% 이상 꽉 차서 시스템이 불안해지는 것을 몇 번이나 발견했습니다. 그러나 이것이 근본 원인인지는 여전히 확신할 수 없습니다(syslog에서 이에 대해 아무 것도 언급하지 않는 이유는 무엇입니까?). 또한 내가 가지고 있는 4GB RAM으로 Windows 설치가 괜찮은지 이해가 안 되지만 Ubuntu는 그렇지 않습니다. 가장 최근 충돌 이후의 또 다른 로그 항목은 다음과 같습니다.
Jul 4 14:25:48 Machine google-chrome.desktop[26653]: libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
Jul 4 14:25:48 Machine google-chrome.desktop[26653]: [26685:26685:0704/142548.700456:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
Jul 4 14:25:53 Machine google-chrome.desktop[26653]: [26646:26666:0704/142553.812893:ERROR:gcm_store_impl.cc(652)] LevelDB remove failed: NotFound:
Jul 4 14:25:53 Machine google-chrome.desktop[26653]: [26646:26669:0704/142553.813045:ERROR:mcs_client.cc(526)] GCM Update failed!
Jul 4 14:27:18 Machine PackageKit: daemon quit
Jul 4 14:27:18 Machine systemd[1]: packagekit.service: Succeeded.
Jul 4 14:27:56 Machine google-chrome.desktop[26653]: [26687:26690:0704/142756.708204:ERROR:ssl_client_socket_impl.cc(980)] handshake failed; returned -1, SSL error code 1, net_error -100
Jul 4 14:27:56 Machine google-chrome.desktop[26653]: [26687:26690:0704/142756.796603:ERROR:ssl_client_socket_impl.cc(980)] handshake failed; returned -1, SSL error code 1, net_error -100
Jul 4 14:27:56 Machine google-chrome.desktop[26653]: [26687:26690:0704/142756.852918:ERROR:ssl_client_socket_impl.cc(980)] handshake failed; returned -1, SSL error code 1, net_error -100
Jul 4 14:28:03 Machine google-chrome.desktop[26653]: [26687:26690:0704/142803.997212:ERROR:ssl_client_socket_impl.cc(980)] handshake failed; returned -1, SSL error code 1, net_error -100
Jul 4 14:28:04 Machine google-chrome.desktop[26653]: [26687:26690:0704/142804.080933:ERROR:ssl_client_socket_impl.cc(980)] handshake failed; returned -1, SSL error code 1, net_error -100
Jul 4 14:28:04 Machine google-chrome.desktop[26653]: [26687:26690:0704/142804.141079:ERROR:ssl_client_socket_impl.cc(980)] handshake failed; returned -1, SSL error code 1, net_error -100
Jul 4 14:28:14 Machine google-chrome.desktop[26653]: [26687:26690:0704/142814.603884:ERROR:ssl_client_socket_impl.cc(980)] handshake failed; returned -1, SSL error code 1, net_error -100
Jul 4 14:28:14 Machine google-chrome.desktop[26653]: [26687:26690:0704/142814.668010:ERROR:ssl_client_socket_impl.cc(980)] handshake failed; returned -1, SSL error code 1, net_error -100
Jul 4 14:28:14 Machine google-chrome.desktop[26653]: [26687:26690:0704/142814.780805:ERROR:ssl_client_socket_impl.cc(980)] handshake failed; returned -1, SSL error code 1, net_error -100
Jul 4 14:28:14 Machine google-chrome.desktop[26653]: [26687:26690:0704/142814.860787:ERROR:ssl_client_socket_impl.cc(980)] handshake failed; returned -1, SSL error code 1, net_error -100
Jul 4 14:28:17 Machine google-chrome.desktop[26653]: (transmission-gtk:27230): GLib-CRITICAL **: 14:28:17.210: g_file_test: assertion 'filename != NULL' failed
Jul 4 14:28:17 Machine dbus-daemon[852]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.212' (uid=1000 pid=27230 comm="transmission-gtk magnet:?xt=urn:btih:1EF2D24F1ECFF" label="unconfined")
Jul 4 14:28:17 Machine systemd[1]: Starting Hostname Service...
Jul 4 14:28:18 Machine dbus-daemon[852]: [system] Successfully activated service 'org.freedesktop.hostname1'
Jul 4 14:28:18 Machine systemd[1]: Started Hostname Service.
Jul 4 14:28:21 Machine google-chrome.desktop[26653]: [26687:26690:0704/142821.884753:ERROR:ssl_client_socket_impl.cc(980)] handshake failed; returned -1, SSL error code 1, net_error -100
Jul 4 14:28:21 Machine google-chrome.desktop[26653]: [26687:26690:0704/142821.964205:ERROR:ssl_client_socket_impl.cc(980)] handshake failed; returned -1, SSL error code 1, net_error -100
Jul 4 14:28:22 Machine google-chrome.desktop[26653]: [26687:26690:0704/142822.068246:ERROR:ssl_client_socket_impl.cc(980)] handshake failed; returned -1, SSL error code 1, net_error -100
Jul 4 14:28:22 Machine google-chrome.desktop[26653]: [26687:26690:0704/142822.140346:ERROR:ssl_client_socket_impl.cc(980)] handshake failed; returned -1, SSL error code 1, net_error -100
Jul 4 14:28:32 Machine google-chrome.desktop[26653]: [26685:26685:0704/142832.102447:ERROR:gl_utils.cc(314)] [.RendererMainThread-0x2c11bcb84700] GL_INVALID_FRAMEBUFFER_OPERATION: Draw framebuffer is incomplete
Jul 4 14:28:48 Machine systemd[1]: systemd-hostnamed.service: Succeeded.
솔직히 이렇게 많은 정보를 제공했음에도 불구하고 이에 대해 아무도 답을 제시하지 못하는 것이 이상하다고 생각합니다.
답변1
tlp또는 을 사용하는 경우 slimbook-battery제거하세요.