All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 92086] AMD Trinity No screen at HDMI after S3 wakeup
Date: Wed, 23 Sep 2015 08:17:11 +0000	[thread overview]
Message-ID: <bug-92086-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 92086
           Summary: AMD Trinity No screen at HDMI after S3 wakeup
           Product: DRI
           Version: XOrg git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: DRM/Radeon
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: vinibali@freemail.hu

Created attachment 118407
  --> https://bugs.freedesktop.org/attachment.cgi?id=118407&action=edit
trinity_wakeup.log

Dear Devs,
ive got this really annoying issue with multiple boards:
- ASRock FM2A75 Pro4
- ASRock A88M-HD+
- ASUS A78M-E
The simptome is the same in every board, but just with A8-7800K Trinity(ARUBA).
I've also tested with A10-7700K Kaveri(GCN1.1), but there was no problems at
all. So I put the PC to S3 sleep, than wake it up. The monitor which uses DVI
connector, works perfectly, but the HDMI one is mostly black,stays at sleep,
doesnt displays information(out of range, etc), but sometimes a really
flickering screen comes in for a few momements than disappears.
I hope its still a non-listed bug, I've checked multiple reports, but doesnt
find thisone. Look at the attachments, dmesg log added.
Thanks

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

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

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

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

             reply	other threads:[~2015-09-23  8:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-23  8:17 bugzilla-daemon [this message]
2015-09-23 13:15 ` [Bug 92086] AMD Trinity No screen at HDMI after S3 wakeup bugzilla-daemon
2015-09-23 13:42 ` bugzilla-daemon
2015-09-23 14:15 ` bugzilla-daemon
2015-09-23 14:15 ` bugzilla-daemon
2015-09-23 14:15 ` bugzilla-daemon
2015-09-23 14:16 ` bugzilla-daemon
2015-10-07  6:45 ` bugzilla-daemon
2015-10-07  6:45 ` bugzilla-daemon
2015-10-07  6:46 ` bugzilla-daemon
2015-10-14 14:45 ` bugzilla-daemon
2015-10-14 15:05 ` bugzilla-daemon
2015-11-04 19:16 ` bugzilla-daemon
2015-11-04 19:17 ` bugzilla-daemon
2015-11-04 19:17 ` bugzilla-daemon
2015-12-29 11:39 ` bugzilla-daemon
2016-05-01 16:35 ` bugzilla-daemon
2016-05-27 19:59 ` bugzilla-daemon
2019-11-19  9:08 ` 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-92086-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.