-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, A curiosity. I had to shuffle around some power cables on my home-server/media-center, and instead of powering it down, I hibernated it. I power it back, and I continue doing things on it remotely via ssh. Then I notice that while my tmux session on it responded to create a new tab or switch tabs, the tabs themselves did not refresh. Then I noticed that the X display on the server had frozen, did not respond to mouse or keyboard, not even to ctrl-alt-backspace. The reason was this: 0.6> 2018-07-18T23:40:09.851253+02:00 Isengard kernel - - - [2630591.596304] [drm] GPU HANG: ecode 8:0:0xfffffffe, in X [2292], reason: Hang on render ring, action: reset <0.6> 2018-07-18T23:40:09.851284+02:00 Isengard kernel - - - [2630591.596312] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. <0.6> 2018-07-18T23:40:09.851287+02:00 Isengard kernel - - - [2630591.596312] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel <0.6> 2018-07-18T23:40:09.851289+02:00 Isengard kernel - - - [2630591.596313] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. <0.6> 2018-07-18T23:40:09.851290+02:00 Isengard kernel - - - [2630591.596313] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. <0.6> 2018-07-18T23:40:09.851292+02:00 Isengard kernel - - - [2630591.596314] [drm] GPU crash dump saved to /sys/class/drm/card0/error <0.5> 2018-07-18T23:40:09.851293+02:00 Isengard kernel - - - [2630591.596492] drm/i915: Resetting chip after gpu hang <0.6> 2018-07-18T23:40:14.564978+02:00 Isengard kernel - - - [2630596.312747] tracker-store[5136]: segfault at 28b ip 00007f1d84ce0dea sp 00007ffe2971b8d0 error 4 in libglib-2.0.so.0.4800.2[7f1d84c7a000+10e000] <3.6> 2018-07-18T23:40:14.586453+02:00 Isengard systemd-coredump 28748 - - Core Dumping has been disabled for process 5136 (tracker-store). <0.2> 2018-07-18T23:40:14.606757+02:00 Isengard systemd-coredump 28748 - - Process 5136 (tracker-store) of user 1000 dumped core. <0.5> 2018-07-18T23:40:18.844004+02:00 Isengard kernel - - - [2630600.589381] drm/i915: Resetting chip after gpu hang <0.5> 2018-07-18T23:40:27.855999+02:00 Isengard kernel - - - [2630609.601866] drm/i915: Resetting chip after gpu hang <0.5> 2018-07-18T23:40:37.855999+02:00 Isengard kernel - - - [2630619.602401] drm/i915: Resetting chip after gpu hang I will not report it, because I took the chance to run yast update, which included a kernel update. And I forgot to capture to file the crash dump. However, what surprised me is that "tmux" did not respond. The contents of the "tabs" froze. The X graphical session had one terminal with tmux running, and tmux could not update its contents on the frozen display... I wonder if next time I can do something to disconnect tmux from the frozen display and regain control of my important tasks running inside :-? - -- Cheers Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAltP2F0ACgkQtTMYHG2NR9X4JgCfdA+mDCOBgWO+vGGDKgyJrDd7 ATMAn0gFzpoQSWAzaYxqLXkVFvW5wOMU =KvqJ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org