Comment 10 for bug 1589379

Revision history for this message
bastien (bastien-bernard) wrote :

My mistake, I did not go until the end of the bissect, one step was remaining.
So I now have the following bad commit:

4474b85771139f2da8f8f4f443e6fad08081e99e is the first bad commit
commit 4474b85771139f2da8f8f4f443e6fad08081e99e
Author: Alex Deucher <email address hidden>
Date: Tue Feb 2 16:24:20 2016 -0500

    drm/amdgpu: remove exp hardware support from iceland

If I test one commit back ([b8b1ad305f8de05b241a57707d5b3de3692dbdfa] drm/amdgpu: don't load MEC2 on topaz), I do not reproduce the problem.

I did another bisect to see from which commit I can boot into the OS and really see the problem of freeze after resume. The result is:

 commit 53e609099daa023ad7771ec8351202f2a7bee1c1
Author: Alex Deucher <email address hidden>
Date: Mon Mar 7 18:40:45 2016 -0500

    drm/amdgpu: fix topaz/tonga gmc assignment in 4.4 stable

So to sum-up:
- before commit 4474b85771139f2da8f8f4f443e6fad08081e99e, resume was working 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 the problem of system frozen on resume (this bug report)(version 4.4.5 and above).