From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 218656] New: Regression: Update from 6.8.1 to 6.8.2 breaks E50 DAC
Date: Fri, 29 Mar 2024 01:20:03 +0000 [thread overview]
Message-ID: <bug-218656-208809@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=218656
Bug ID: 218656
Summary: Regression: Update from 6.8.1 to 6.8.2 breaks E50 DAC
Product: Drivers
Version: 2.5
Hardware: AMD
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: USB
Assignee: drivers_usb@kernel-bugs.kernel.org
Reporter: vaxerskiofficial@gmail.com
Regression: No
Created attachment 306056
--> https://bugzilla.kernel.org/attachment.cgi?id=306056&action=edit
sudo journalctl -b -1 | grep E50 -A 10 -B 50
Hello,
after upgrading to 6.8.2, my DAC no longer receives any signal, thus audio
can't work.
I have ran `sudo journalctl -b -1 | grep E50 -A 10 -B 50` and it seems pw/alsa
is having a hard time communicating. Logs attached.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2024-03-29 1:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 1:20 bugzilla-daemon [this message]
2024-03-29 1:58 ` [Bug 218656] Regression: Update from 6.8.1 to 6.8.2 breaks E50 DAC 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-218656-208809@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-usb@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 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).