From: Ricardo Ribalda <ribalda@chromium.org>
To: JP Hein <jp@jphein.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Hans de Goede <hansg@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-media@vger.kernel.org, linux-usb@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH 0/3] USB/UVC: Add quirks to prevent Razer Kiyo Pro xHCI cascade failure
Date: Mon, 23 Mar 2026 10:56:01 +0100 [thread overview]
Message-ID: <CANiDSCsZf0QWzCQdgFC=hj+V4ChCynwjRNAz6u-F3Y8vzZXXDw@mail.gmail.com> (raw)
In-Reply-To: <20260321223713.1219297-1-jp@jphein.com>
Hi JP
On Sat, 21 Mar 2026 at 23:38, JP Hein <jp@jphein.com> wrote:
>
> The Razer Kiyo Pro (1532:0e05) is a USB 3.0 webcam whose firmware has a
> well-documented failure mode that cascades into complete xHCI host
> controller death, disconnecting every USB device on the bus — including
> keyboards and mice, requiring a hard reboot.
Have you tried reaching out to Razer in case they have a new firmware
that fixes your issues?
>
> The device has two crash triggers:
>
> 1. LPM/autosuspend resume: Device enters LPM or autosuspend, fails to
> reinitialize on resume, producing EPIPE (-32) on UVC SET_CUR. The
> stalled endpoint triggers an xHCI stop-endpoint timeout, and the
> kernel declares the host controller dead.
>
> 2. Rapid control transfers: ~25 rapid consecutive UVC SET_CUR
> operations overwhelm the firmware. The standard error-code query
> (GET_CUR on UVC_VC_REQUEST_ERROR_CODE_CONTROL) amplifies the
> failure by sending a second transfer to the already-stalling device,
> pushing it into a full lockup and xHCI controller death.
>
> This has been reported as Ubuntu Launchpad Bug #2061177 and affects
> multiple kernel versions (tested on 6.5.x through 6.8.x). There are
> currently no device-specific quirks for this webcam in either the USB
> core quirks table or the UVC driver device table.
>
> This series adds three patches:
>
> Patch 1: USB core — USB_QUIRK_NO_LPM to prevent Link Power Management
> transitions that destabilize the device firmware.
>
> Patch 2: UVC driver — introduce UVC_QUIRK_CTRL_THROTTLE to rate-limit
> SET_CUR control transfers (50ms minimum interval) and skip the
> error-code query after EPIPE errors on affected devices.
>
> Patch 3: UVC driver — add Razer Kiyo Pro device table entry with
> UVC_QUIRK_CTRL_THROTTLE, UVC_QUIRK_DISABLE_AUTOSUSPEND, and
> UVC_QUIRK_NO_RESET_RESUME to address both crash triggers.
>
> Together, these keep the device in a stable active state, prevent rapid
> control transfer crashes, and avoid the power management transitions
> that trigger the firmware bug.
>
> Tested on:
> - Kernel: 6.8.0-106-generic (Ubuntu 24.04)
> - Hardware: Intel Cannon Lake PCH xHCI (8086:a36d)
> - Device: Razer Kiyo Pro (1532:0e05), firmware 8.21
> - Stress test: 50 rounds of rapid UVC control changes, 0 failures
>
> JP Hein (3):
> USB: core: add NO_LPM quirk for Razer Kiyo Pro webcam
> media: uvcvideo: add UVC_QUIRK_CTRL_THROTTLE for fragile firmware
> media: uvcvideo: add quirks for Razer Kiyo Pro webcam
>
> drivers/media/usb/uvc/uvc_driver.c | 16 ++++++++++++++++
> drivers/media/usb/uvc/uvc_video.c | 33 +++++++++++++++++++++++++++++++++
> drivers/media/usb/uvc/uvcvideo.h | 3 +++
> drivers/usb/core/quirks.c | 2 ++
> 4 files changed, 54 insertions(+)
>
--
Ricardo Ribalda
next prev parent reply other threads:[~2026-03-23 9:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-21 22:37 [PATCH 0/3] USB/UVC: Add quirks to prevent Razer Kiyo Pro xHCI cascade failure JP Hein
2026-03-21 22:37 ` [PATCH 1/3] USB: core: add NO_LPM quirk for Razer Kiyo Pro webcam JP Hein
2026-03-21 22:37 ` [PATCH 2/3] media: uvcvideo: add UVC_QUIRK_CTRL_THROTTLE for fragile firmware JP Hein
2026-03-21 22:37 ` [PATCH 3/3] media: uvcvideo: add quirks for Razer Kiyo Pro webcam JP Hein
2026-03-22 2:15 ` [PATCH 0/3] USB/UVC: Add quirks to prevent Razer Kiyo Pro xHCI cascade failure Alan Stern
2026-03-22 4:53 ` Michal Pecio
2026-03-22 22:10 ` Jeffrey Hein
2026-03-23 7:58 ` Michal Pecio
2026-03-23 9:56 ` Ricardo Ribalda [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-22 3:40 JP Hein
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='CANiDSCsZf0QWzCQdgFC=hj+V4ChCynwjRNAz6u-F3Y8vzZXXDw@mail.gmail.com' \
--to=ribalda@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=hansg@kernel.org \
--cc=jp@jphein.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stable@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