| Bug ID | 96866 |
|---|---|
| Summary | System frozen after resume, on Ubuntu 16.04 kernel 4.4.0-22 |
| Product | DRI |
| Version | XOrg git |
| Hardware | x86-64 (AMD64) |
| OS | Linux (All) |
| Status | NEW |
| Severity | critical |
| Priority | medium |
| Component | DRM/AMDgpu |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | bastien.bernard@gmx.fr |
| CC | alexdeucher@gmail.com |
Problem on HP probook 450, with Radeon R7 M260/M265. Please see: ht= tps://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589379 To sum-up: - before commit 4474b85771139f2da8f8f4f443e6fad08081e99e, resume was workin= g OK (version 4.4.3) - from commit 4474b85771139f2da8f8f4f443e6fad08081e99e (drm/amdgpu: remove = exp hardware support from iceland), I cannot boot on the OS (version 4.4.4) - from commit 53e609099daa023ad7771ec8351202f2a7bee1c1 (drm/amdgpu: fix topaz/tonga gmc assignment in 4.4 stable), I can boot into the OS and see t= he problem of system frozen on resume (this bug report)(version 4.4.5 and abov= e).
| What | Removed | Added |
|---|---|---|
| Summary | System frozen after resume, on Ubuntu 16.04 kernel 4.4.0-22 | REGRESSION System frozen after resume |
| Severity | critical | normal |
1) Edited title as not a Ubuntu bug, but an upstream one as pe= r original reporter (reproducible in mainline 4.7-rc6 and a regression). 2) Issue after suspend isn't Critical.
I have the same problem with Linux kernel 4.4.8 on my fresh (b= ought 4 days ago) HP notebook 17-y011nc, with AMD/ATI Topaz XT [Radeon R7 M260/M265]. The interesting thing is, that originally I had the 4.4.0 kernel from Ubuntu 16.04.1 LTS but it sometimes got frozen during suspending. Not everytime, j= ust sometimes. However, it was a way too often, so it was pretty annoying. Then I have found somewhere in forums, that this bug was resolved in newer kernels, so I switched from 4.4.0 to 4.4.8. And it surely was resolved, how= ever after resume from suspend, it ALWAYS got frozen, so my problem in fact got = much worse with the kernel upgrade 4.4.0 =3D> 4.4.8.
You can set amdgpu.runpm=3D0 on the kernel command line in gru= b or try the latest drm-next kernel code.
I've encountered the same issue on Fedora 24 with kernel-4.7.2= -201.fc24. Tried booting with amdgpu.runpm=3D0 but that still didn't solve the problem. Any ideas besides recompiling drm-next branch?
Good news, this seems corrected on the last upstream kernel 4.9.0-040900rc6-generic.
| What | Removed | Added |
|---|---|---|
| Status | NEW | RESOLVED |
| Resolution | --- | FIXED |