Bug 40935

Summary: radeon lockup on resume
Product: DRI Reporter: Michal Suchanek <hramrach>
Component: DRM/RadeonAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Bug Depends on:    
Bug Blocks: 42373    
Attachments:
Description Flags
dmesg none

Description Michal Suchanek 2011-09-16 04:46:21 UTC 
The card locked up after resume from suspend.

The resume probably happened because suspend failed and  the system did not shut down at all meaning  the card was not reset to text mode.

Initializing radeon from anything but text mode fails but normally does not lock up the card completely.
Comment 1 Michal Suchanek 2011-09-16 08:23:57 UTC 
Created attachment 51264 [details]
dmesg
Comment 2 Alex Deucher 2011-09-16 09:19:23 UTC 
What card is this?  Can you attach your boot up dmesg?  Is this a regression?  If so when did it last work and can you bisect?
Comment 3 Michel Dänzer 2011-09-16 10:18:01 UTC 
I don't understand how you can get "GPU lockup" messages from radeon_fence_wait(), but none from r100_gpu_cp_is_lockup()... Do you have dev_err() output disabled somehow?
Comment 4 Michal Suchanek 2011-09-19 04:21:10 UTC 
It's a redwood.

The bootup dmesg is below the locup messages.

I am not sure what dev_err() would be.

And now I rebooted and tried to kill Xorg with suspend and it would not lock up the card, only keep resetting it.
Comment 5 Michal Suchanek 2011-11-18 07:36:11 UTC 
hmm, I it looks like the driver resets the card quite a few  times over some hours until it locks up permanently (or at least long enough for the next reset to fail) or the driver gives up and the screen stays blank.
Comment 6 Michal Suchanek 2012-06-18 04:30:27 UTC 
this is AFAIK an issue since introduction of KMS on r300, not a regression.
Comment 7 Jerome Glisse 2012-06-18 07:38:21 UTC 
All my r300 works fine with KMS (and i have a lot of them), you just an unlucky user. Not all r300 are affected, it's most likely the combination of your gpu with your motherboard.
Comment 8 Martin Peres 2019-11-19 08:20:37 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/211.

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.