Bug 111879 - GPU reset during hibernation
Summary: GPU reset during hibernation
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/AMDgpu (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: not set normal
Assignee: Default DRI bug account
QA Contact:
Depends on:
Reported: 2019-10-01 19:11 UTC by Yuxuan Shui
Modified: 2019-11-19 09:57 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

relevant bits of dmesg (18.60 KB, text/plain)
2019-10-01 19:11 UTC, Yuxuan Shui
no flags Details
possible fix (1.93 KB, patch)
2019-10-01 21:47 UTC, Alex Deucher
no flags Details | Splinter Review

Description Yuxuan Shui 2019-10-01 19:11:44 UTC
Created attachment 145606 [details]
relevant bits of dmesg

After resuming from hibernation, the screen freezes (flickers between two frames), and "Failed to initialize parser -125!" is printed repeatedly in dmesg.
Comment 1 Yuxuan Shui 2019-10-01 19:17:11 UTC
Looks like a GPU reset was triggered during hibernation and that's what's causing the "Failed to initialize parser" error.
Comment 2 Alex Deucher 2019-10-01 21:38:55 UTC
What chip is this?  Please attach your full dmesg output.
Comment 3 Alex Deucher 2019-10-01 21:47:19 UTC
Created attachment 145608 [details] [review]
possible fix

Does this patch fix the issue?
Comment 4 Yuxuan Shui 2019-10-02 01:14:44 UTC
(In reply to Alex Deucher from comment #3)
> Created attachment 145608 [details] [review] [review]
> possible fix
> Does this patch fix the issue?

I hiberate/resumed with this patch a couple of times, the problem hasn't occurred so far. Looks like this fixes the problem.

Comment 5 Martin Peres 2019-11-19 09:57:00 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/928.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.