Mic*_*zuk 7 google-chrome freeze 19.04
我已经为此搜索了 Askubuntu 和其他网站，但没有发现任何实质性的内容，所以我希望它不是太多重复。
无论如何，我最近遇到了随机冻结 - 系统完全锁定，我的键盘和鼠标没有响应，PC 也从活动的网络客户端中消失（通过使用来自不同 PC 的 nmap 扫描我的网络）所以我假设它完全死亡，而不仅仅是失去输入。升级到 19.04 后，它最近开始发生。
我一直无法查明问题，唯一的共同点似乎是 Chrome。然而，即便如此，仍然存在巨大的变化窗口，因为我可以做任何事情，从观看 YT 到仅阅读 Latex 格式提示，从高负载到低负载。我关闭了 GPU 加速和其他实验性好东西，所以我不认为是这样 - 此外，我在 19.04 之前从未遇到过这样的问题。
在冻结之前 /var/log/syslog 中出现以下内容：
Sep 25 12:31:08 meeshbox systemd[1]: Started Run anacron jobs.
Sep 25 12:31:08 meeshbox anacron[11822]: Anacron 2.3 started on 2019-09-25
Sep 25 12:31:08 meeshbox anacron[11822]: Normal exit (0 jobs run)
Sep 25 12:31:08 meeshbox systemd[1]: anacron.service: Succeeded.
Sep 25 12:31:32 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x3802c74 sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 214748364
7; this doesn't make much sense.
Sep 25 12:31:32 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x3802c74 sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 214748364
7; this doesn't make much sense.
Sep 25 12:36:28 meeshbox org.gnome.Shell.desktop[1329]: [1:1:0925/123628.789445:ERROR:child_process_sandbox_support_impl_linux.cc(81)] FontService unique font name matching request did not receive a respo
nse.
Sep 25 12:36:28 meeshbox org.gnome.Shell.desktop[1329]: [1:1:0925/123628.791155:ERROR:child_process_sandbox_support_impl_linux.cc(81)] FontService unique font name matching request did not receive a respo
nse.
Sep 25 12:36:45 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x38039d7 sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 214748364
7; this doesn't make much sense.
Sep 25 12:36:45 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x38039d7 sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 214748364
7; this doesn't make much sense.
Sep 25 12:38:08 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x3803b5a sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 214748364
7; this doesn't make much sense.
Sep 25 12:38:08 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x3803b5a sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense.
Sep 25 12:38:26 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x3803bc3 sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense.
Sep 25 12:38:26 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x3803bc3 sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense.
Sep 25 12:38:40 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x3803c21 sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense.
Sep 25 12:38:40 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x3803c21 sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense.
Sep 25 12:38:41 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x3803c35 sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense.
Sep 25 12:38:41 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x3803c35 sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense.
Sep 25 12:38:42 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x3803c49 sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense.
Sep 25 12:38:42 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x3803c49 sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense.
Sep 25 12:38:51 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x3803ca1 sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense.
Sep 25 12:38:51 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x3803ca1 sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense.
Sep 25 12:39:02 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x3803d01 sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense.
Sep 25 12:39:02 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x3803d01 sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense.
Sep 25 12:40:09 meeshbox smartd[910]: Device: /dev/sdb [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 68 to 67
Sep 25 12:40:09 meeshbox smartd[910]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 32 to 33
Sep 25 12:41:14 meeshbox systemd-resolved[803]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
在 kern.log 中没有任何兴趣。18.04 从来没有这个问题。这不是很常见，但一旦发生就很烦人——例如，现在，我丢失了我正在编写的大量代码，因为我愚蠢到没有保存它。它也从未发生过，例如，在玩游戏时，即使在后台有其他东西。我真的无法正确定位它。但是，从上周的日志中搜索冻结发生时的日志，我发现这样的行：
[1:1:0925/123628.789445:ERROR:child_process_sandbox_support_impl_linux.cc(81)] FontService unique font name matching request did not receive a response.
经常在冻结前不久看到 - 但不是在冻结前不久，更像是 3-4 分钟。
还有哪些其他日志需要检查？
最好的解决方案是启用多次启动消息日志记录，然后显示上次启动的最后消息：
$ journalctl -xe -b-1
Nov 11 23:12:07 alien systemd[1]: Reached target Shutdown.
-- Subject: Unit shutdown.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit shutdown.target has finished starting up.
--
-- The start-up result is done.
Nov 11 23:12:07 alien systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition
Nov 11 23:13:37 alien systemd[1]: dev-disk-by\x2duuid-b4512bc6\x2d0ec8\x2d4b17\x2d9edd\x2d8
Nov 11 23:13:37 alien systemd[1]: Deactivated swap /dev/disk/by-uuid/b4512bc6-0ec8-4b17-9ed
-- Subject: Unit dev-disk-by\x2duuid-b4512bc6\x2d0ec8\x2d4b17\x2d9edd\x2d88db0f031332.swap
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit dev-disk-by\x2duuid-b4512bc6\x2d0ec8\x2d4b17\x2d9edd\x2d88db0f031332.swap has finis
Nov 11 23:13:37 alien systemd[1]: dev-disk-by\x2duuid-b4512bc6\x2d0ec8\x2d4b17\x2d9edd\x2d8
在您的情况下，消息不会显示正常关闭，而是显示系统崩溃之前最后记录的消息。
第一个错误消息在这里解决：
解决方案是使用：
看来我的系统有旧的配置，导致两个服务之间发生冲突：
resolvconf和systemd-resolved。符号链接
/etc/resolv.conf 指向../run/resolvconf/resolv.conf将其更改为指向
/run/systemd/resolve/resolv.conf由 systemd 管理的位置，为我修复了它。
第二条错误消息是由 nvidia 生成的：
发布的答案仅对软件开发人员有帮助，对最终用户没有帮助。对于运行 Chrome 的最终用户，存在其他解决方案：
小智 2
众所周知，系统锁定很难诊断，特别是当系统日志中没有显示任何内容时。您可以按照其他答案中的建议检查journalctl，但我的猜测是它不会显示任何更多信息。
如果您能够找到一种可靠地触发冻结的方法，那么dmesg --follow --human在窗口中运行可能会显示一些有用的信息。然而，大多数情况下，冻结发生得很突然，实际上没有任何记录。很多时候，这些“随机冻结”很难缩小到任何特定原因。
系统冻结可能是由硬件本身的问题（例如内存故障、电源过载……）、BIOS 缺陷或内核或其硬件驱动程序（尤其是 GPU 驱动程序）中的错误引起的。有时，首先尝试升级/降级内核，然后查看是否有可用的 BIOS 更新，如果有，则进行更新，然后进行一些硬件诊断和/或更换，这是最节省时间的方法。
GPU 锁定是一种常见的系统冻结类型。对于 Intel 显卡，有一些工具可以在冻结后从显卡本身获取转储（请参阅 intel-gpu-tools 的文档），但它可能会偶然获得足够有用的信息。通常最好的情况是不断更新您的 BIOS、内核和/或硬件，直到问题消失。
| 归档时间： |
|
| 查看次数： |
1663 次 |
| 最近记录： |