From: Alexander Wilhelm <alexander.wilhelm@westermo.com>
To: Mathias Nyman <mathias.nyman@intel.com>,
Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: usb: Error while assigning device slot ID
Date: Thu, 4 Dec 2025 12:09:11 +0100 [thread overview]
Message-ID: <aTFr17xKxnWGG3vU@FUE-ALEWI-WINX> (raw)
Hello USB developers,
I’m using an NXP LS1046A SoC with the integrated DWC3 USB controller in
host mode. On Linux v5.5.167 my USB flash drive was detected and mountable.
After upgrading to Linux v6.6.110 the USB flash drive is no longer
recognized. If it is already plugged in during boot phase I get the
following errors:
xhci-hcd xhci-hcd.2.auto: Error while assigning device slot ID: Command Aborted
xhci-hcd xhci-hcd.2.auto: Max number of devices this xHCI host supports is 127
And here is the kernel debug output:
user@host:~# cat /sys/kernel/debug/usb/xhci/xhci-hcd.3.auto/ports/port01/portsc
Powered Connected Disabled Link:Polling PortSpeed:1 Change: Wake: WDE WOE
I’ve also found that the function `xhci_alloc_dev` shows the error message.
I printed the `command` member variables and see that the `status` is
`COMP_COMMAND_ABORTED` and `slot_id` remains `0`. I have already seen
similar error patterns in some forums, but the suggested solutions didn’t
help me. Between these releases Kconfig has changed significantly; I may be
missing a config option, but I haven’t found one. Does anyone else see this
error pattern? Or maybe someone has a hint for me on how to proceed?
Best regards
Alexander Wilhelm
next reply other threads:[~2025-12-04 11:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 11:09 Alexander Wilhelm [this message]
2025-12-04 15:35 ` usb: Error while assigning device slot ID Mathias Nyman
2025-12-05 8:22 ` Alexander Wilhelm
2025-12-09 14:53 ` Mathias Nyman
2025-12-10 8:31 ` Alexander Wilhelm
2025-12-15 11:40 ` Mathias Nyman
2026-01-19 7:16 ` Alexander Wilhelm
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=aTFr17xKxnWGG3vU@FUE-ALEWI-WINX \
--to=alexander.wilhelm@westermo.com \
--cc=Thinh.Nguyen@synopsys.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
/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