public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 220238] Blue Yeti microphone doesn't consistently work after unplugging and plugging back in or reboot.
Date: Fri, 26 Dec 2025 14:09:01 +0000	[thread overview]
Message-ID: <bug-220238-208809-wBy8oXDUJM@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220238-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=220238

kernel.exact088@passmail.net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kernel.exact088@passmail.ne
                   |                            |t

--- Comment #14 from kernel.exact088@passmail.net ---
I'm experiencing the same issue with the Blue Yeti (046d:0ab7) on kernel
6.17.12-300.fc43.x86_64 (Framework Laptop 16, AMD Ryzen 9 7940HS).
In my case, the mic works fine until suspend/resume. After resume:

Device enumerates correctly (no errors in dmesg)
ALSA can open the device
Recording fails with: arecord: pcm_read:2279: read error: Input/output error
sox shows 0 samples read, amplitude 0.000000

Physical replug restores functionality. USB unbind/rebind, usbreset, and
USB_QUIRK_RESET_RESUME do not fix it.
This appears related to Bug 215219 which reports the same device ID with
similar symptoms.
Attaching diagnostic data (dmesg, lsusb -v, sox analysis of working vs broken
state).

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2025-12-26 14:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-16  8:45 [Bug 220238] New: Blue Yeti microphone doesn't consistently work after unplugging and plugging back in or reboot bugzilla-daemon
2025-06-17  5:32 ` [Bug 220238] " bugzilla-daemon
2025-06-23  9:07 ` bugzilla-daemon
2025-06-23  9:29 ` bugzilla-daemon
2025-06-23  9:36 ` bugzilla-daemon
2025-06-23  9:42 ` bugzilla-daemon
2025-06-23 10:03 ` bugzilla-daemon
2025-06-23 10:40   ` Oliver Neukum
2025-06-23 10:40 ` bugzilla-daemon
2025-06-23 11:23 ` bugzilla-daemon
2025-06-23 11:24 ` bugzilla-daemon
2025-07-02  3:39 ` bugzilla-daemon
2025-07-21  8:39 ` bugzilla-daemon
2025-07-21 16:32 ` bugzilla-daemon
2025-07-26 23:17 ` bugzilla-daemon
2025-12-26 14:09 ` bugzilla-daemon [this message]
2025-12-26 14:09 ` bugzilla-daemon
2026-01-09 23:35 ` 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-220238-208809-wBy8oXDUJM@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