From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 86351] HDMI audio garbled output on Radeon R9 280X
Date: Sat, 23 Mar 2019 19:20:59 +0000 [thread overview]
Message-ID: <bug-86351-2300-eUnmBbb6E2@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 #35 from Christian Birchinger (joker@netswarm.net) ---
After a success report in the previous comment i've installed a 5.0.3 kernel
on my system.
The audio seems good so far. I'm trying to keep the load low in the background
to make sure this time it's not just fine because there's also a video playing.
It's been playing for 10 minutes without dropouts so far, i'm cautiously
optimistic at this point (again).
If you have this problem and the possibility to test with a 5.0 kernel (or
maybe 4.20 from the previous comment) give it a try please.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2019-03-23 19:21 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
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 [this message]
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-eUnmBbb6E2@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 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).