From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 220016] USB devices plugged into USB hubs on 6.14.2-300.fc42.x86_64 do not work
Date: Fri, 25 Apr 2025 16:05:38 +0000 [thread overview]
Message-ID: <bug-220016-208809-zmtzjn2Nuu@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220016-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220016
--- Comment #24 from Ilpo Järvinen (ilpo.jarvinen@linux.intel.com) ---
Created attachment 308020
--> https://bugzilla.kernel.org/attachment.cgi?id=308020&action=edit
Add min_bridge_window cmdline parameter
It seems the FW left zero extra tail room in the root iomem windows which makes
it a bit hard for pci=realloc to work. It doesn't work well with the default
sizing algorithm that is greedy and tries to reserves more space than is really
required.
Maybe the attached patch helps more devices to assign their resources:
So please test with pci=realloc,min_bridge_window
It could still leads to a failure or some failures because it seems there
simply is not enough space to fit everything even without pci=realloc reserving
that extra empty space.
Please also add dyndbg="file drivers/pci/*.c +p" on kernel cmdline to get a bit
more information.
--
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:[~2025-04-25 16:05 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 0:25 [Bug 220016] New: USB devices plugged into USB hubs on 6.14.2-300.fc42.x86_64 do not work bugzilla-daemon
2025-04-16 0:26 ` [Bug 220016] " bugzilla-daemon
2025-04-16 7:21 ` bugzilla-daemon
2025-04-16 8:53 ` bugzilla-daemon
2025-04-16 17:20 ` bugzilla-daemon
2025-04-16 17:43 ` bugzilla-daemon
2025-04-16 17:43 ` bugzilla-daemon
2025-04-16 17:51 ` bugzilla-daemon
2025-04-16 21:38 ` bugzilla-daemon
2025-04-16 22:19 ` bugzilla-daemon
2025-04-17 13:22 ` bugzilla-daemon
2025-04-18 16:25 ` bugzilla-daemon
2025-04-18 17:37 ` bugzilla-daemon
2025-04-18 17:38 ` bugzilla-daemon
2025-04-18 17:38 ` bugzilla-daemon
2025-04-18 17:39 ` bugzilla-daemon
2025-04-18 17:45 ` bugzilla-daemon
2025-04-18 17:53 ` bugzilla-daemon
2025-04-18 18:05 ` bugzilla-daemon
2025-04-18 18:05 ` bugzilla-daemon
2025-04-18 18:06 ` bugzilla-daemon
2025-04-18 18:06 ` bugzilla-daemon
2025-04-18 18:09 ` bugzilla-daemon
2025-04-21 17:35 ` bugzilla-daemon
2025-04-25 16:05 ` bugzilla-daemon [this message]
2025-04-25 19:34 ` bugzilla-daemon
2025-04-25 19:35 ` bugzilla-daemon
2025-04-28 17:06 ` bugzilla-daemon
2025-04-28 19:00 ` bugzilla-daemon
2025-04-30 10:39 ` bugzilla-daemon
2025-04-30 10:44 ` bugzilla-daemon
2025-04-30 14:46 ` bugzilla-daemon
2025-04-30 14:46 ` 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-220016-208809-zmtzjn2Nuu@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