From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 73060] New: RV630 HDMI audio lost after suspend resume
Date: Fri, 27 Dec 2013 08:35:23 +0000 [thread overview]
Message-ID: <bug-73060-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 950 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=73060
Priority: medium
Bug ID: 73060
Assignee: dri-devel@lists.freedesktop.org
Summary: RV630 HDMI audio lost after suspend resume
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: karzisss@hotmail.com
Hardware: x86 (IA32)
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
HDMI audio is lost when resuming from system suspend. Can't test RCs because
audio is not working at all (mouse, wlan and gpu acceleration too).
Last working kernel version: 3.4.X
First version bug appeared: 3.5
Last version bug appeared: still not resolved (3.13-RC5)
Hardware:
Gigabyte GA-MA790X-DS4 (BIOS F9)
AMD X2 3600+
Radeon 2600 PRO 512mb (ASUS)
Launchpad: Bug #1237105
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2248 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
next reply other threads:[~2013-12-27 8:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-27 8:35 bugzilla-daemon [this message]
2013-12-27 8:48 ` [Bug 73060] RV630 HDMI audio lost after suspend resume bugzilla-daemon
2013-12-31 1:03 ` bugzilla-daemon
2014-01-12 2:10 ` [Bug 73060] RV630 HDMI audio lost after system suspend bugzilla-daemon
2014-01-17 22:54 ` bugzilla-daemon
2014-01-17 22:54 ` bugzilla-daemon
2019-11-19 8:41 ` 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-73060-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;
as well as URLs for NNTP newsgroup(s).