https://bugs.freedesktop.org/show_bug.cgi?id=40935
Summary: radeon lockup on resume Product: DRI Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel@lists.freedesktop.org ReportedBy: hramrach@gmail.com
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.
https://bugs.freedesktop.org/show_bug.cgi?id=40935
--- Comment #1 from Michal Suchanek hramrach@gmail.com 2011-09-16 08:23:57 PDT --- Created an attachment (id=51264) --> (https://bugs.freedesktop.org/attachment.cgi?id=51264) dmesg
https://bugs.freedesktop.org/show_bug.cgi?id=40935
Michal Suchanek hramrach@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #51264|application/octet-stream |text/plain mime type| |
https://bugs.freedesktop.org/show_bug.cgi?id=40935
--- Comment #2 from Alex Deucher agd5f@yahoo.com 2011-09-16 09:19:23 PDT --- 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?
https://bugs.freedesktop.org/show_bug.cgi?id=40935
--- Comment #3 from Michel Dänzer michel@daenzer.net 2011-09-16 10:18:01 PDT --- 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?
https://bugs.freedesktop.org/show_bug.cgi?id=40935
--- Comment #4 from Michal Suchanek hramrach@gmail.com 2011-09-19 04:21:10 PDT --- 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.
https://bugs.freedesktop.org/show_bug.cgi?id=40935
Kunal kunal.gangakhedkar@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Blocks| |42373
https://bugs.freedesktop.org/show_bug.cgi?id=40935
--- Comment #5 from Michal Suchanek hramrach@gmail.com 2011-11-18 07:36:11 PST --- 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.
https://bugs.freedesktop.org/show_bug.cgi?id=40935
--- Comment #6 from Michal Suchanek hramrach@gmail.com 2012-06-18 04:30:27 PDT --- this is AFAIK an issue since introduction of KMS on r300, not a regression.
https://bugs.freedesktop.org/show_bug.cgi?id=40935
--- Comment #7 from Jerome Glisse glisse@freedesktop.org 2012-06-18 07:38:21 PDT --- 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.
https://bugs.freedesktop.org/show_bug.cgi?id=40935
Martin Peres martin.peres@free.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |MOVED Status|NEW |RESOLVED
--- Comment #8 from Martin Peres martin.peres@free.fr --- -- 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.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org