From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 215561] snd-usb-audio:reset_resume error -22 after suspend
Date: Thu, 10 Feb 2022 01:33:39 +0000 [thread overview]
Message-ID: <bug-215561-208809-OXpyW0pBpD@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215561-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215561
--- Comment #4 from Mark Blakeney (mark.blakeney@bullet-systems.net) ---
@Takashi, I can't really try that. Note that when this fault occurs my machine
becomes unusable and also will not reboot. I have to hard reset it via the
power switch. I see this with my dock but I just removed that and replicated it
with nothing plugged in to my XPS 13 laptop except a direct USB headset. Set
sound output to that and then suspend. When resuming, sound will lock up. Still
fails on 5.16.8, works fine on all of 5.15 -> 5.15.22 and before.
--
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 prev parent reply other threads:[~2022-02-10 1:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 11:08 [Bug 215561] New: snd-usb-audio:reset_resume error -22 after suspend bugzilla-daemon
2022-02-02 11:50 ` [Bug 215561] " bugzilla-daemon
2022-02-07 22:10 ` bugzilla-daemon
2022-02-08 13:42 ` bugzilla-daemon
2022-02-10 1:33 ` bugzilla-daemon [this message]
2022-02-10 8:01 ` bugzilla-daemon
2022-02-10 10:11 ` bugzilla-daemon
2022-02-13 22:07 ` bugzilla-daemon
2022-02-14 8:49 ` bugzilla-daemon
2022-02-14 8:53 ` bugzilla-daemon
2022-02-14 10:37 ` bugzilla-daemon
2022-02-14 10:41 ` bugzilla-daemon
2022-02-14 10:42 ` bugzilla-daemon
2022-02-14 11:00 ` bugzilla-daemon
2022-02-14 12:47 ` bugzilla-daemon
2022-02-14 13:09 ` bugzilla-daemon
2022-02-19 22:43 ` 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-215561-208809-OXpyW0pBpD@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 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.