Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #59775
| From | Ferdinand Rau <rauferd@web.de> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| Subject | Bug#883935: linux-image-4.9.0-4-amd64: i915 GPU hang after every suspend or hibernate (Hang on render ring) |
| Date | 2017-12-27 11:30 +0100 |
| Message-ID | <v1h8d-am-1@gated-at.bofh.it> (permalink) |
| References | <uV7Oh-6XP-5@gated-at.bofh.it> <v1h8d-am-3@gated-at.bofh.it> <uV7Oh-6XP-5@gated-at.bofh.it> <v1h8d-am-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
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
Back to linux.debian.kernel | Previous | Next | Find similar | Unroll thread
Bug#883935: linux-image-4.9.0-4-amd64: i915 GPU hang after every suspend or hibernate (Hang on render ring) Ferdinand Rau <rauferd@web.de> - 2017-12-27 11:30 +0100
csiph-web