[opensuse-factory] X locks up periodically after TW 20180116

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Ever since I upgraded to TW 20180116 (currently on 20180122), at some point during the day my laptop will stop responding. I can still move the mouse, but can't click on anything, the mouse doesn't change shape as I move over different parts of the display, etc. About 30 seconds later, X restarts and I'm back at the login screen, and is fine for the rest of my day. (Note that the whole computer doesn't lock up/restart, it just seems to be X itself.) The rotated Xorg.0.log.old file doesn't really contain anything about the crash: [ 58.669] (II) modeset(0): Modeline "1440x900"x0.0 136.75 1440 1536 1688 1936 900 903 909 942 -hsync +vsync (70.6 kHz e) [ 19116.762] (II) event10 - (II) Logitech USB Optical Mouse: (II) SYN_DROPPED event - some input events have been lost. nor does the new log: [ 19703.840] (--) Log file renamed from "/var/log/Xorg.pid-28831.log" to "/var/log/Xorg.0.log" [ 19703.841] X.Org X Server 1.19.6 Release Date: 2017-12-20 [ 19703.841] X Protocol Version 11, Revision 0 [ 19703.841] Build Operating System: openSUSE SUSE LINUX [ 19703.841] Current Operating System: Linux caradhras.millikin.edu 4.14.14-1-default #1 SMP PREEMPT Wed Jan 17 09:26:10 UTC 2018 (eef6178) x86_64 [ 19703.841] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.14.14-1- default root=UUID=f84d219d-a7de-4de5-a3bb-62dd9d55232e resume=/dev/nvme0n1p1 quiet showopts [ 19703.841] Build Date: 20 January 2018 01:51:08PM [ 19703.841] [ 19703.841] Current version of pixman: 0.34.0 [ 19703.841] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [.....] Is there any way to tell what's causing this? This is a Lenovo T570. I'm not using any custom display drivers; the "Hardware Information" thing in YaST lists it as using the i915 driver. Chris -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEE7GM/Dul8WSWn72odQ1nEo4DFCIUFAlpo4j8ACgkQQ1nEo4DF CIWtEwf/ddm8kzazvVyGyrIwwPu6B/vnk5IbY/4qQW4S/e6QHKfVmROGx/uUyRdF 8SyFMj0zylnOw6eFIziobI41Awm0pEeMQjRkwln3Wnpip1iP4nzMkrpho0sQ2nKM KXrjJ2ePIa+v1fAAP+IXTEs79PKfP3BbTT8J1ClYEqtpUtYbdkqOTGBpoo6DR1Sv B5Xeu6uvsyzFBKU6yCmEqSjuwC3nssWa7v8T2JQnOzTOMedkuGN8CQCBi/BR16pw YQ1qVnYyei5B6I0TVVbAPccsjtEWgPj9I11WMeEqHwrBjbhmgY6ehYbe8t4jAM8i 3pUrgB72Pj0oyruAQqmP4f3MyHGxUg== =yb8T -----END PGP SIGNATURE----- N�����r��y隊Z)z{.���r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���r�+��0�����Ǩ�

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On Thu, 2018-01-25 at 09:35 +0100, Michal Srb wrote:
Just happened about 10 minutes ago this morning, great way to start the day... It looks like there are messages when I do "dmesg"; that "card0/error" file mentioned is zero bytes. Looks like there may be several bug reports for it possibly? https://bugs.freedesktop.org/buglist.cgi?quick search=0x85dffffb [ 509.814831] [drm] GPU HANG: ecode 9:0:0x85dffffb, in X [2928], reason: Hang on rcs0, action: reset [ 509.814835] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 509.814837] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 509.814838] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 509.814840] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 509.814842] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 509.814855] i915 0000:00:02.0: Resetting rcs0 after gpu hang [ 517.824153] i915 0000:00:02.0: Resetting rcs0 after gpu hang [ 525.824168] i915 0000:00:02.0: Resetting rcs0 after gpu hang [ 533.824167] i915 0000:00:02.0: Resetting rcs0 after gpu hang [ 542.816187] i915 0000:00:02.0: Resetting rcs0 after gpu hang -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEE7GM/Dul8WSWn72odQ1nEo4DFCIUFAlpp4uQACgkQQ1nEo4DF CIVWuAf/bHmE9rf4r+rBbweWv+rMbcbTjebLHhcxPKrlWEN0on1TDXZY+UwIZs54 RgFFPHP+AIDoTnCqL1ZE9kvN1RyqxfFumf8LTJ5AHTJfjEsuiIbxNymNfdyJhgkE YJO5pMRK3B11k8zA6y80ab/DdFpaXahytYtQGgV45nOFmWT+F6rzQdiT6Y16uMNC H7L+7mSDtD5d09ICgFVs57nHv1upt5oyW82vyu5nGJXv+RvDNploQVv7ked70KnF Dhpu5DS1fqQXoZwGsc6OoGwHrjiJUuL15ifwQcfSFeou/n9ACrtVdm8VQM53uYBs TLI8Mf5Qn9wkCvKgNxmbOwyG3BXjJw== =PYPw -----END PGP SIGNATURE-----

Christopher Myers wrote:
I can sort of confirm it, though I have so far only seen it once - but exactly those symptoms. laptop with skylake/HD530 (also i915 driver) Will try to catch logs should it happen again. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On Thu, 2018-01-25 at 11:56 +0100, nicholas cunliffe wrote:
Out of curiosity, what packages did you uninstall, and did you need to install any replacement ones? -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEE7GM/Dul8WSWn72odQ1nEo4DFCIUFAlpp7NUACgkQQ1nEo4DF CIV0ZQf/ULGBRcb79Ff9tD3PbOfwMLV48pF7bwln+vIH8Qg3LvnS0L4Yl7YPrnRy d+F8sy08f4KSu3ooWkAcwnWCq1MxOI9OxcpGPX1NxiHMoN62j/7CUDI+0C17lEdO iGNKmTiY/bdjWAVfKy6AdI4WwmC49czR3xu2w4JjogM/MFzMuMp8ylPUHvR6BD3W 1rCtM/UqGflQD8ByPQ3UcXL11Swk7Wpots23qsvrIp0kqH4jfpYCEHiSdzoRja6C rQziU1w4v+0eZw9hap7GzpklNwVQcdxl25B9WBUud1XCmbyZkUAKGWAqrgo59ya8 9Y8ObgjWERkXO8BH4xGj7nwD7h+PNA== =YFSr -----END PGP SIGNATURE----- N�����r��y隊Z)z{.���r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���r�+��0�����Ǩ�

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On Thu, 2018-01-25 at 16:29 +0100, nicholas cunliffe wrote:
Awesome, thanks very much! It's done it twice this morning already :/ -----BEGIN PGP SIGNATURE----- iQEyBAEBCgAdFiEE7GM/Dul8WSWn72odQ1nEo4DFCIUFAlpp+rAACgkQQ1nEo4DF CIWXfQf3QrR3FgSm2k+DITn/Tb+VZjhCoDnDYOArnMEnXE9cJdDGmvnPnC9sNCcQ wronep4tYXfkxRU9TvP0fC5u0wbZtDpihtfydTipgomTod/Ktvcl8rBMD/biLkkx kh+I+aiZqo4G1f97usX1Oy/14p+YeUeW93ATTUV6LagGWv6/g8YeIWMLYJRJk3bJ KO60OT3Bqyy+NIzwbqvRGfHMcoQS+O5jFMJPGvJ+odQiTNpK/dsTj7EUaoAzvj/P AygsNg3TcFFMt8Mm3WETukqiSQ6NcjFR5FIR5wa+Fpl3ipshIYRLrCvB6/58Tg7f 2LOivJM8mcz5V62KLLEMRL4vaauA =TCF8 -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On Thu, 2018-01-25 at 09:35 +0100, Michal Srb wrote:
Just happened about 10 minutes ago this morning, great way to start the day... It looks like there are messages when I do "dmesg"; that "card0/error" file mentioned is zero bytes. Looks like there may be several bug reports for it possibly? https://bugs.freedesktop.org/buglist.cgi?quick search=0x85dffffb [ 509.814831] [drm] GPU HANG: ecode 9:0:0x85dffffb, in X [2928], reason: Hang on rcs0, action: reset [ 509.814835] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 509.814837] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 509.814838] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 509.814840] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 509.814842] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 509.814855] i915 0000:00:02.0: Resetting rcs0 after gpu hang [ 517.824153] i915 0000:00:02.0: Resetting rcs0 after gpu hang [ 525.824168] i915 0000:00:02.0: Resetting rcs0 after gpu hang [ 533.824167] i915 0000:00:02.0: Resetting rcs0 after gpu hang [ 542.816187] i915 0000:00:02.0: Resetting rcs0 after gpu hang -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEE7GM/Dul8WSWn72odQ1nEo4DFCIUFAlpp4uQACgkQQ1nEo4DF CIVWuAf/bHmE9rf4r+rBbweWv+rMbcbTjebLHhcxPKrlWEN0on1TDXZY+UwIZs54 RgFFPHP+AIDoTnCqL1ZE9kvN1RyqxfFumf8LTJ5AHTJfjEsuiIbxNymNfdyJhgkE YJO5pMRK3B11k8zA6y80ab/DdFpaXahytYtQGgV45nOFmWT+F6rzQdiT6Y16uMNC H7L+7mSDtD5d09ICgFVs57nHv1upt5oyW82vyu5nGJXv+RvDNploQVv7ked70KnF Dhpu5DS1fqQXoZwGsc6OoGwHrjiJUuL15ifwQcfSFeou/n9ACrtVdm8VQM53uYBs TLI8Mf5Qn9wkCvKgNxmbOwyG3BXjJw== =PYPw -----END PGP SIGNATURE-----

Christopher Myers wrote:
I can sort of confirm it, though I have so far only seen it once - but exactly those symptoms. laptop with skylake/HD530 (also i915 driver) Will try to catch logs should it happen again. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On Thu, 2018-01-25 at 11:56 +0100, nicholas cunliffe wrote:
Out of curiosity, what packages did you uninstall, and did you need to install any replacement ones? -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEE7GM/Dul8WSWn72odQ1nEo4DFCIUFAlpp7NUACgkQQ1nEo4DF CIV0ZQf/ULGBRcb79Ff9tD3PbOfwMLV48pF7bwln+vIH8Qg3LvnS0L4Yl7YPrnRy d+F8sy08f4KSu3ooWkAcwnWCq1MxOI9OxcpGPX1NxiHMoN62j/7CUDI+0C17lEdO iGNKmTiY/bdjWAVfKy6AdI4WwmC49czR3xu2w4JjogM/MFzMuMp8ylPUHvR6BD3W 1rCtM/UqGflQD8ByPQ3UcXL11Swk7Wpots23qsvrIp0kqH4jfpYCEHiSdzoRja6C rQziU1w4v+0eZw9hap7GzpklNwVQcdxl25B9WBUud1XCmbyZkUAKGWAqrgo59ya8 9Y8ObgjWERkXO8BH4xGj7nwD7h+PNA== =YFSr -----END PGP SIGNATURE----- N�����r��y隊Z)z{.���r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���r�+��0�����Ǩ�
participants (4)
-
Christopher Myers
-
Michal Srb
-
nicholas cunliffe
-
Peter Suetterlin