From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 86351] HDMI audio garbled output on Radeon R9 280X
Date: Tue, 13 Jan 2015 16:41:52 +0000 [thread overview]
Message-ID: <bug-86351-2300-0NZTeyylpN@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-86351-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=86351
--- Comment #8 from Andy Furniss <adf.lists@gmail.com> ---
(In reply to Alex Deucher from comment #7)
> If you are using CPU governor, does forcing the CPU power state to a stable
> state help?
No, I've tried many things as recorded in the FDO bug I linked.
It's certainly a strange one, but the only way to get working sound I've found
is to have enough CPU load across all my CPUs (just maxing one won't do).
By luck for me my only real use case is HDTV and decoding in s/w is enough
load.
When there is no load it's like just one chunk of buffer gets repeated and this
may initially contain old sound from a previous loaded run.
Doing not much will advance the buffer. With more, but not enough, load the
sound is almost OK, but there is a bit of crackle.
This does seem to need purely CPU load, as I said in the other bug I can
reproduce from fbcon without X and temporarily "fix" the sound my compiling
something with make -j5.
My CPU is AMD Phenom II x4 965be, but IIRC others have seen this with intel.
Whether working or not interrupt counters rise at the same rate.
Previous card = HD4890 didn't have the issue in the same box with the same TV
with almost the same s/w.
--
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 prev parent reply other threads:[~2015-01-13 16:41 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 19:22 [Bug 86351] New: HDMI audio garbled output on Radeon R9 280X bugzilla-daemon
2014-10-15 19:22 ` [Bug 86351] " 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 [this message]
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-0NZTeyylpN@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.