From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107001] New: Radeon HDMI audio lost after resuming from suspend
Date: Sun, 01 Nov 2015 10:52:46 +0000 [thread overview]
Message-ID: <bug-107001-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=107001
Bug ID: 107001
Summary: Radeon HDMI audio lost after resuming from suspend
Product: Drivers
Version: 2.5
Kernel Version: 4.2.0
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: timo.valtoaho@gmail.com
Regression: No
Created attachment 191781
--> https://bugzilla.kernel.org/attachment.cgi?id=191781&action=edit
output of scripts/ver_linux
After switching to 4.2 series, I noticed that audio through HDMI was gone after
first suspend/resume cycle (systemctl suspend). I can get audio back with some
simple operations, like executing xrand, lanching gnome-control-center or
swithcing to a virtual terminal (ctrl+alt+F1). All of these operations will
restore audio.
I have tested this out, and it was 4.2-rc2 that introduced this issue, and is
still present in 4.3-rc7. Also, it doesn't matter whether radeon driver is a
module or compiled in with required firmware.
System is Debian Jessie (8.2), Gnome
Output of scripts/ver_linux:
Attached files:
output of scripts/ver_linux
output of lspci -vvv
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2015-11-01 10:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-01 10:52 bugzilla-daemon [this message]
2015-11-01 10:53 ` [Bug 107001] Radeon HDMI audio lost after resuming from suspend bugzilla-daemon
2015-11-15 8:52 ` bugzilla-daemon
2016-03-31 18:44 ` bugzilla-daemon
2016-10-03 16:54 ` bugzilla-daemon
2016-12-20 19:14 ` bugzilla-daemon
2016-12-22 21:54 ` 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-107001-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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.