Bug 100109

Summary: Graphics Lockup if monitor disconnected and then set into standby
Product: DRI Reporter: Kieran Grant <kierangrant>
Component: DRM/AMDgpu-proAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: medium    
Version: XOrg git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Various log files none

Description Kieran Grant 2017-03-08 10:19:22 UTC
Created attachment 130119 [details]
Various log files

I got a Kernel Oops from with AMDGPU-PRO for Ubuntu 16.04.2 LTS x86-64 version 16.60 after unplugging and plugging in my HDMI display...

Computer was left on overnight to do some long IO operation... before I left it, I turned monitor off... at the time my MATE display settings was to put monitor to sleep after 30 minutes... so I guess it tried that after 30 minutes...

Next day... I got no graphics response... after trying various F-n combos... I eventually tried some SysRq keys to force text console... but stock Ubuntu SysRq limit was in effect *doh*...

That is when as a last resort thought to unplug and re-plug in monitor... in hopes that would magically do something... it did something alright...

I got Kernel OOPS at that moment... it was early morning for me :|

Attached is a snippet of my syslog plus various ls* outputs...

I have a MSI Radeon RX480 8GB

I will see if I can manually reproduce the bug to get a Xorg.log file... I forgot that one and old one is now gone :/
Comment 1 Kieran Grant 2017-03-08 10:25:58 UTC
I just tried to quickly reproduce the problem using timer delayed xset usage and turning off monitor and unplugging it... but no oops and no graphics stack corruption... (Well... at least *that* is good news)

So it will take some better testing to reproduce it...
Hopefully I won't have to resort to leaving my computer on overnight again with original setup of sleep after 30 minutes and monitor turned off...
Comment 2 Martin Peres 2019-11-19 07:58:22 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/12.

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.