dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100109] Graphics Lockup if monitor disconnected and then set into standby
Date: Wed, 08 Mar 2017 10:19:22 +0000	[thread overview]
Message-ID: <bug-100109-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1729 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=100109

            Bug ID: 100109
           Summary: Graphics Lockup if monitor disconnected and then set
                    into standby
           Product: DRI
           Version: XOrg git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu-pro
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: kierangrant@linux.com

Created attachment 130119
  --> https://bugs.freedesktop.org/attachment.cgi?id=130119&action=edit
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 :/

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3147 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2017-03-08 10:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-08 10:19 bugzilla-daemon [this message]
2017-03-08 10:25 ` [Bug 100109] Graphics Lockup if monitor disconnected and then set into standby bugzilla-daemon
2019-11-19  7:58 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-100109-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox