我有一堆桌面客户端，自从将内核从 更新到 以来，它们似乎会定期3.10.0-327挂起3.10.0-514（10.2，21.1和21.2）
我得到的唯一“确凿”证据是偶尔会看到本地记录的事件：
May 19 09:55:10 desktop-132 acpid: 1 client rule loaded
May 19 09:55:20 desktop-132 kernel: lockd: server nfserver not responding, still trying
May 19 09:55:23 desktop-132 kernel: lockd: server nfserver OK
May 19 09:55:23 desktop-132 gnome-session: (gnome-settings-daemon:3367): GLib-GIO-WARNING **: gdbusobjectmanagerclient.c:1586: Processing InterfaceRemoved signal for path /org/gnome/Mutter/IdleMonitor/Device6 but no object proxy exists
May 19 09:55:23 desktop-132 gnome-session: (gnome-settings-daemon:3367): GLib-GIO-WARNING **: gdbusobjectmanagerclient.c:1586: Processing InterfaceRemoved signal for path /org/gnome/Mutter/IdleMonitor/Device7 but no object proxy exists
May 19 09:55:23 desktop-132 gnome-session: (gnome-settings-daemon:3367): GLib-GIO-WARNING **: gdbusobjectmanagerclient.c:1586: Processing InterfaceRemoved signal for path /org/gnome/Mutter/IdleMonitor/Device8 but no object proxy exists
May 19 09:55:23 desktop-132 gnome-session: (gnome-settings-daemon:3367): GLib-GIO-WARNING **: gdbusobjectmanagerclient.c:1586: Processing InterfaceRemoved signal for path /org/gnome/Mutter/IdleMonitor/Device9 but no object proxy exists
May 19 09:55:23 desktop-132 gnome-session: (gnome-settings-daemon:3367): GLib-GIO-WARNING **: gdbusobjectmanagerclient.c:1586: Processing InterfaceRemoved signal for path /org/gnome/Mutter/IdleMonitor/Device10 but no object proxy exists
May 19 09:55:23 desktop-132 gnome-session: Window manager warning: last_user_time (946497320) is greater than comparison timestamp (946495968). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around...
May 19 09:55:23 desktop-132 gnome-session: Window manager warning: 0x2000007 (user@d) appears to be one of the offending windows with a timestamp of 946497320. Working around...
我很确定这个问题只在这个内核版本上出现——只有更新过的东西才会出现这个问题，而且降级再次升级到 3.10.0-327 问题便会消失。
当然，这没有帮助，因为我们是为了修复安全问题而进行更新。
几天前发布的当前内核版本似乎仍然存在该问题。
但我有点不知所措——我没有记录任何内容，只有我试图跟踪的“死机”。所以我甚至还没有开始提交错误报告所需的基本信息。