From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 222071] [Bisected] [Regression] xhci_hcd: Resuming from hibernation fails with "Not enough host resources"
Date: Tue, 29 Sep 2026 20:26:52 +0000 [thread overview]
Message-ID: <bug-222071-208809-VgNQl99x9B@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-222071-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=222071
Michał Pecio (michal.pecio@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |michal.pecio@gmail.com
--- Comment #7 from Michał Pecio (michal.pecio@gmail.com) ---
Some old Intel chipsets can't calculate bandwidth allocation themselves and
need babysitting by the driver. You seem to have one of those. The bug(s) can
likely be reproduced on any hardware by specifying xhci_hcd.quirks=0x120.
With quirks=0x1a0 one may not even need hibernation, only suspend.
The other controller is ASM1042, one of the oldest and buggiest. Mine does the
same, even with zero connected devices. Maybe they just don't support this.
--
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:[~2026-09-29 20:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 8:10 [Bug 222071] New: [Bisected] [Regression] xhci_hcd: Resuming from hibernation fails with "Not enough host resources" bugzilla-daemon
2026-09-29 8:19 ` [Bug 222071] " bugzilla-daemon
2026-09-29 10:47 ` bugzilla-daemon
2026-09-29 17:17 ` bugzilla-daemon
2026-09-29 17:19 ` bugzilla-daemon
2026-09-29 18:44 ` bugzilla-daemon
2026-09-29 18:46 ` bugzilla-daemon
2026-09-29 20:26 ` bugzilla-daemon [this message]
2026-09-30 6:45 ` bugzilla-daemon
2026-09-30 7:49 ` bugzilla-daemon
2026-09-30 9:25 ` bugzilla-daemon
2026-10-01 13:25 ` bugzilla-daemon
2026-10-01 23:29 ` bugzilla-daemon
2026-10-06 10:19 ` bugzilla-daemon
2026-10-06 12:14 ` 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-222071-208809-VgNQl99x9B@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