From: bugzilla-daemon@bugzilla.kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 211117] dma_mmap_coherent() - garbage sound output with mem_encrypt on Ryzen platform
Date: Wed, 20 Jan 2021 12:47:01 +0000 [thread overview]
Message-ID: <bug-211117-215701-j7bZfmo4HI@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-211117-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=211117
--- Comment #18 from Triton Circonflexe (triton+enkelr@kumal.info) ---
Tested with iommu=pt (and no mem_encrypt option, so "on" by default): still
white noise.
Regarding the encryption, I don't really have a _need_ for that. If I use it,
it's in part because Virtualbox seems to require it in some use cases (not even
entirely sure about that) and mostly because it's activated by default (and I
like default settings to work correctly).
I checked the BIOS anyway but did not find any TSME or similar option (thanks
for the information, though).
Right now, I'm working with mem_encrypt=off and I can do everything I need for
now (no vbox for the moment).
I will continue to follow this bug because I can reproduce the problem easily
and do tests if required.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2021-01-20 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-211117-215701@https.bugzilla.kernel.org/>
2021-01-18 14:27 ` [Bug 211117] [oxygen] [virtuoso] route, dmix and other alsa plugins produce garbage output with mem_encrypt on Ryzen platform bugzilla-daemon
2021-01-18 14:28 ` [Bug 211117] dma_mmap_coherent() - garbage sound " bugzilla-daemon
2021-01-18 14:36 ` bugzilla-daemon
2021-01-19 19:33 ` bugzilla-daemon
2021-01-20 12:47 ` 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-211117-215701-j7bZfmo4HI@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=platform-driver-x86@vger.kernel.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.