From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 86351] New: HDMI audio garbled output on Radeon R9 280X
Date: Wed, 15 Oct 2014 19:22:21 +0000 [thread overview]
Message-ID: <bug-86351-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=86351
Bug ID: 86351
Summary: HDMI audio garbled output on Radeon R9 280X
Product: Drivers
Version: 2.5
Kernel Version: 3.17
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: joker@netswarm.net
Regression: No
Created attachment 153891
--> https://bugzilla.kernel.org/attachment.cgi?id=153891&action=edit
dmesg output
Any sound played back over HDMI results in garbled audio output.
When playing audio at 24000hz or below (19200Hz also tested) playback
starts to work normaly without the constant choppyness.
What also works is 44100Hz in Mono.
It behaves like a data bandwith issue that kicks in above 24000hz Stereo
or 44100Hz Mono.
All test are done directly talking to the alsa device.
This means no pulseaudio or dmix or similar processing.
"plughw" had to be used because the hardware does not
allow low rates like 24000.
During all Test a perfectly fine and stable 1080p image is displayed
over HDMI. (No dropouts at all).
This hardware setup has also be successfully tested using Windows.
(Incl. Multi channel PCM 6.0 for lot's of audio bandwidth)
Working Audio Tests:
--------------------
speaker-test -r 24000 -c2
speaker-test -r 24000 -c6 (multi channel PCM works too)
mpg123 -r 24000 <file>
mpg123 -m -r 44100 <file>
The peer format detection is pcm 2.0 44100 or 48000 here.
It appears the format link doesn't matter, only the actual
data bandwidth that's being used)
Garbled Audio Tests:
--------------------
speaker-test -r 48000 -c2
speaker-test -r 48000 -c6
mpg123 -r 44100 <file>
All passthru formats (dts, dolby d, pcm multi channel) get detected
my the destination, but after a short period it loses the link and
tries to resync.
What previously also worked is a HD5570 in the same system which i
no longer have access to though. Not sure about the kernel used back
then.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2014-10-15 19:22 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 19:22 bugzilla-daemon [this message]
2014-10-15 19:22 ` [Bug 86351] HDMI audio garbled output on Radeon R9 280X bugzilla-daemon
2014-10-15 19:23 ` bugzilla-daemon
2015-01-11 11:53 ` bugzilla-daemon
2015-01-11 12:20 ` bugzilla-daemon
2015-01-12 21:51 ` bugzilla-daemon
2015-01-13 16:18 ` bugzilla-daemon
2015-01-13 16:23 ` bugzilla-daemon
2015-01-13 16:41 ` bugzilla-daemon
2015-01-13 17:42 ` bugzilla-daemon
2015-07-04 22:31 ` bugzilla-daemon
2015-07-04 22:31 ` bugzilla-daemon
2015-07-06 2:58 ` bugzilla-daemon
2015-07-06 5:29 ` bugzilla-daemon
2015-07-10 22:10 ` bugzilla-daemon
2015-07-13 5:47 ` bugzilla-daemon
2015-08-26 19:19 ` bugzilla-daemon
2015-08-26 22:00 ` bugzilla-daemon
2015-09-15 15:19 ` bugzilla-daemon
2015-11-21 11:08 ` bugzilla-daemon
2016-01-30 22:31 ` bugzilla-daemon
2016-03-23 19:17 ` bugzilla-daemon
2016-03-23 19:58 ` bugzilla-daemon
2016-03-23 22:18 ` bugzilla-daemon
2016-03-28 21:36 ` bugzilla-daemon
2016-04-27 18:45 ` bugzilla-daemon
2017-03-24 0:56 ` bugzilla-daemon
2017-03-24 10:37 ` bugzilla-daemon
2017-03-24 11:22 ` bugzilla-daemon
2017-03-25 13:22 ` bugzilla-daemon
2018-01-23 18:05 ` bugzilla-daemon
2018-05-18 18:16 ` bugzilla-daemon
2018-05-31 7:09 ` bugzilla-daemon
2018-05-31 17:31 ` bugzilla-daemon
2019-03-23 8:27 ` bugzilla-daemon
2019-03-23 19:20 ` 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-86351-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.