Bug#883935: linux-image-4.9.0-4-amd64: i915 GPU hang after every suspend or hibernate (Hang on render ring)

2017-12-27 Thread Ferdinand Rau
FYI, the bug is not resolved in the latest kernel package (update 12/23/2017):

> $ uname -a
> Linux N360-11 4.9.0-4-amd64 #1 SMP Debian 4.9.65-3+deb9u1 (2017-12-23) x86_64 
> GNU/Linux

After hibernate/resume:
> $ dmesg | tail -n 9
> [ 1686.964009] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
> [ 1687.868696] [drm] GPU HANG: ecode 8:0:0x5fa3bf07, in Xorg [650], reason: 
> Hang on render ring, action: reset
> [ 1687.868704] [drm] GPU hangs can indicate a bug anywhere in the entire gfx 
> stack, including userspace.
> [ 1687.868708] [drm] Please file a _new_ bug report on bugs.freedesktop.org 
> against DRI -> DRM/Intel
> [ 1687.868712] [drm] drm/i915 developers can then reassign to the right 
> component if it's not a kernel issue.
> [ 1687.868716] [drm] The gpu crash dump is required to analyze gpu hangs, so 
> please always attach it.
> [ 1687.868720] [drm] GPU crash dump saved to /sys/class/drm/card0/error
> [ 1687.868949] drm/i915: Resetting chip after gpu hang
> [ 1697.849509] drm/i915: Resetting chip after gpu hang



Bug#883935: linux-image-4.9.0-4-amd64: i915 GPU hang after every suspend or hibernate (Hang on render ring)

2017-12-10 Thread Christoph Wiedemann
Package: src:linux
Version: 4.9.65-3
Followup-For: Bug #883935

Dear Maintainer,

I have the same issue, and I find it very annoying. As a workaround I use 
kernel linux-image-4.12.0-1-amd64, which mostly
manages to wake correctly from hibernation. But honestly, I'm a bit 
overstrained in using a testing kernel on an otherwise
stable system. I was hoping that the recent update of 4.9.0 kernel maybe fixed 
the issue, but unfortunately not. It would
be very nice if this could be fixed with a future update.

Thank you in advance!
Christoph


-- Package-specific info:
** Version:
Linux version 4.9.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 
20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.65-3 (2017-12-03)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.9.0-4-amd64 
root=UUID=39cb1350-d7bf-43e6-9a89-f1821f0ae9b9 ro quiet 
i915.preliminary_hw_support=1

** Tainted: PUO (4161)
 * Proprietary module has been loaded.
 * Userspace-defined naughtiness.
 * Out-of-tree module has been loaded.

** Kernel log:
[  167.358244] ata1.00: supports DRM functions and may not be fully accessible
[  167.358695] ata1.00: configured for UDMA/133
[  167.383405] usb 1-4: reset high-speed USB device number 2 using xhci_hcd
[  167.643093] usb 1-7: reset full-speed USB device number 5 using xhci_hcd
[  167.903455] usb 1-6: reset full-speed USB device number 3 using xhci_hcd
[  167.910793] psmouse serio1: synaptics: queried max coordinates: x [..5676], 
y [..4758]
[  167.946771] psmouse serio1: synaptics: queried min coordinates: x [1266..], 
y [1096..]
[  168.163211] usb 1-9: reset full-speed USB device number 8 using xhci_hcd
[  168.422910] usb 1-8: reset high-speed USB device number 7 using xhci_hcd
[  168.830965] usb 1-4.2: reset low-speed USB device number 6 using xhci_hcd
[  169.387447] usb 1-4.1: reset low-speed USB device number 4 using xhci_hcd
[  169.720828] PM: restore of devices complete after 2684.862 msecs
[  169.721308] usb 1-7:1.0: rebind failed: -517
[  169.721313] usb 1-7:1.1: rebind failed: -517
[  169.721665] PM: Image restored successfully.
[  169.721774] PM: Basic memory bitmaps freed
[  169.721780] Restarting tasks ... done.
[  169.731277] thermal thermal_zone2: failed to read out thermal zone (-5)
[  169.739769] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
[  169.746776] Bluetooth: hci0: Device revision is 5
[  169.746777] Bluetooth: hci0: Secure boot is enabled
[  169.746778] Bluetooth: hci0: OTP lock is enabled
[  169.746779] Bluetooth: hci0: API lock is enabled
[  169.746779] Bluetooth: hci0: Debug lock is disabled
[  169.746780] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[  169.751150] bluetooth hci0: firmware: direct-loading firmware 
intel/ibt-11-5.sfi
[  169.751153] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[  169.865935] e1000e: eth1 NIC Link is Down
[  169.867438] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[  170.075048] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[  170.075720] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[  170.079558] iwlwifi :03:00.0: L1 Enabled - LTR Enabled
[  170.082036] iwlwifi :03:00.0: L1 Enabled - LTR Enabled
[  170.212136] iwlwifi :03:00.0: L1 Enabled - LTR Enabled
[  170.212626] iwlwifi :03:00.0: L1 Enabled - LTR Enabled
[  170.309080] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[  170.321546] iwlwifi :03:00.0: L1 Enabled - LTR Enabled
[  170.323628] iwlwifi :03:00.0: L1 Enabled - LTR Enabled
[  170.458950] iwlwifi :03:00.0: L1 Enabled - LTR Enabled
[  170.459265] iwlwifi :03:00.0: L1 Enabled - LTR Enabled
[  170.491370] [drm] RC6 on
[  170.553392] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[  170.603365] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[  170.629381] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, 
buttons: 3/3
[  170.825772] input: TPPS/2 IBM TrackPoint as 
/devices/platform/i8042/serio1/serio2/input/input23
[  171.338681] Bluetooth: hci0: Waiting for firmware download to complete
[  171.338772] Bluetooth: hci0: Firmware loaded in 1562047 usecs
[  171.338958] Bluetooth: hci0: Waiting for device to boot
[  171.349737] Bluetooth: hci0: Device booted in 10636 usecs
[  171.349930] bluetooth hci0: firmware: direct-loading firmware 
intel/ibt-11-5.ddc
[  171.349932] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
[  171.353746] Bluetooth: hci0: Applying Intel DDC parameters completed
[  174.173465] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[  182.459087] [drm] GPU HANG: ecode 9:0:0x81ba3c75, in Xorg [709], reason: 
Hang on render ring, action: reset
[  182.459089] [drm] GPU hangs can indicate a bug anywhere in the entire gfx 
stack, including userspace.
[  182.459090] [drm] Please file a _new_ bug report on bugs.freedesktop.org 
against DRI -> DRM/Intel
[  182.459091] [drm] drm/i915 developers can then reassign to the right 
component if it's not a kernel issue.
[  182.459092] [drm] The