Am Mittwoch, 25. Januar 2017, 16:08:52 CET schrieb Takashi Iwai:
OK, and at this moment, do you see any kernel messages showing warning or such? Check the output of dmesg.
dmesg includes those lines after wakeup: [22470.597775] [drm] GPU HANG: ecode 8:0:0xba399353, in Xorg [1652], reason: Hang on render ring, action: reset [22470.597778] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [22470.597780] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [22470.597781] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [22470.597782] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [22470.597784] [drm] GPU crash dump saved to /sys/class/drm/card0/error [22470.597865] drm/i915: Resetting chip after gpu hang [22479.589147] drm/i915: Resetting chip after gpu hang [22480.078992] Uhhuh. NMI received for unknown reason 3c on CPU 0. [22480.078995] Do you have a strange power saving mode enabled? [22480.078997] Dazed and confused, but trying to continue [22491.589009] drm/i915: Resetting chip after gpu hang [22503.620918] drm/i915: Resetting chip after gpu hang [22515.588830] drm/i915: Resetting chip after gpu hang [22527.588757] drm/i915: Resetting chip after gpu hang [22539.588682] drm/i915: Resetting chip after gpu hang [22551.588603] drm/i915: Resetting chip after gpu hang [22562.596511] drm/i915: Resetting chip after gpu hang [22573.604415] drm/i915: Resetting chip after gpu hang [22584.580419] drm/i915: Resetting chip after gpu hang [22595.620296] drm/i915: Resetting chip after gpu hang [22607.588250] drm/i915: Resetting chip after gpu hang [22617.604150] drm/i915: Resetting chip after gpu hang [22629.604064] drm/i915: Resetting chip after gpu hang [22641.603976] drm/i915: Resetting chip after gpu hang [22651.619902] drm/i915: Resetting chip after gpu hang [22662.627872] drm/i915: Resetting chip after gpu hang [22675.587746] drm/i915: Resetting chip after gpu hang ============================================ dmesg | grep "error" [ 9.446992] tpm tpm0: A TPM error (6) occurred attempting to read a pcr value [ 9.453848] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-7265D-26.ucode failed with error -2 [ 9.453861] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-7265D-25.ucode failed with error -2 [ 9.453869] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-7265D-24.ucode failed with error -2 [ 9.453876] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-7265D-23.ucode failed with error -2 [21923.165360] tpm tpm0: A TPM error (6) occurred attempting to read a pcr value [22456.293200] tpm tpm0: A TPM error (6) occurred attempting to read a pcr value [22470.597784] [drm] GPU crash dump saved to /sys/class/drm/card0/error linux-k2bd:/home/AW # dmesg | grep "*ERROR*" [21923.880843] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training [21923.965787] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to start channel equalization [21930.417303] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun
You can test my backup kernel repo, OBS home:tiwai:kernel:4.8: http://download.opensuse.org/repositories/home:/tiwai:/kernel:/4.8/
But, before trying that: which kernels did you test? Did it start breaking from 4.9.0? Or later version of 4.9.x?
I'm not sure, but I guess, with 4.9.3. Loading your 4.8. kernel... -- Alexander -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org