From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 6039233D4FF for ; Sun, 8 Mar 2026 17:56:05 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772992565; cv=none; b=TTn9+5cIv6l0/ZNaQTlADqpIi5dYkQMR3R0tppu90bFUTOb6EXk7rnvhCiIwe+0KnZ8GD8Or12iNtyjcPp8iQH2WQB0Ni3YauRzEBJqEx8TpjKpfjplqf2MkuJyxTY5O/sDIxd6YAIZOTh3cgSmbjerAuLOicBvtqcPmms4Fyow= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772992565; c=relaxed/simple; bh=Tazz66W0uB8xKME9ef/M9auzneenawq7+FcolqGIgt4=; h=From:To:Subject:Date:Message-ID:In-Reply-To:References: Content-Type:MIME-Version; b=sGRQOxUZkDVLKQVk0xBBQa7lAH0nRYQSxkSyzj0vZ0UaBykdflMNba7qoOeJ6ngRJ1ronKYBalqlN9WjWHfOWfXMQx1tJaY7frNipICAz9ADDrJCaofrfpI80bXQiiSg8R6kYavWqRwtefBRl1RDP7Cq91BvwARFCIXMBGRgWWs= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=I+kC/dI/; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="I+kC/dI/" Received: by smtp.kernel.org (Postfix) with ESMTPS id 26736C2BCB2 for ; Sun, 8 Mar 2026 17:56:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1772992565; bh=Tazz66W0uB8xKME9ef/M9auzneenawq7+FcolqGIgt4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=I+kC/dI/qfhZS6xE3gcXXb8XBdFTpiZzQ+4pPFZvZfSbNthGLRhCWzoy4wI6V/NVQ nplUARbOoAgiJicTxG/PLIDWM0aYuS7NUSg5nKMX8z8G9UXENUGgcRgfHA9IyJpnNY v6aMQZNWE3fOw8hA7WckcuLxxML9fpzf8pvRGLWPOKQBi2nlqnvImrOyRuIjAAN3+k +mU3EG3gWmHoo9/9ToZ7Uls8TRrliov7xLq3xdBCZRpTa5rbUZaFQRpw3R0NmpP3Hm 5u5JKK4TkXN1mfqmwMgB68uKMNNQ2norMT10f5ZadSlKf4VCxisWhACYdJ+RTocX1Q Z8nweoTEy0d8Q== Received: by aws-us-west-2-korg-bugzilla-1.web.codeaurora.org (Postfix, from userid 48) id 1DCFBC4160E; Sun, 8 Mar 2026 17:56:05 +0000 (UTC) From: bugzilla-daemon@kernel.org To: linux-usb@vger.kernel.org Subject: [Bug 221103] xhci_hcd: System lockup under CPU load during usbfs polling of USB devices on AMD platforms Date: Sun, 08 Mar 2026 17:56:04 +0000 X-Bugzilla-Reason: None X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: AssignedTo drivers_usb@kernel-bugs.kernel.org X-Bugzilla-Product: Drivers X-Bugzilla-Component: USB X-Bugzilla-Version: 2.5 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: gtschemer@gmail.com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: drivers_usb@kernel-bugs.kernel.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugzilla.kernel.org/ Auto-Submitted: auto-generated Precedence: bulk X-Mailing-List: linux-usb@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 https://bugzilla.kernel.org/show_bug.cgi?id=3D221103 S. Davar (gtschemer@gmail.com) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gtschemer@gmail.com --- Comment #25 from S. Davar (gtschemer@gmail.com) --- I have been supporting users on an atomic distribution, so no one has tried= the test patch. However, 4+ users who had this freeze behavior on ASUS motherboards with Ry= zen 5 / 7 / 9 CPUs seem to have 100% success manually setting all the xHCI controllers to "on" instead of "auto". All of those users froze very quickly with the usb_poll test, and never fro= ze after changing the xHCI power control behavior. Most have a B650M or simil= ar motherboard. Was anyone with the freeze able to try the test patch? Also, are there any concerns that a small delay might still be unreliable, e.g. long enough in = some cases but not long enough in others? Could it potentially cause a performa= nce hit in some cases, or is it expected to be called rarely enough that it doe= sn't matter? --=20 You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.=