linux-kernel - usb: Error while assigning device slot ID

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <aTFr17xKxnWGG3vU@FUE-ALEWI-WINX>
Date: Thu, 4 Dec 2025 12:09:11 +0100
From: Alexander Wilhelm <alexander.wilhelm@...termo.com>
To: Mathias Nyman <mathias.nyman@...el.com>,
        Thinh Nguyen <Thinh.Nguyen@...opsys.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: usb: Error while assigning device slot ID

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@...t:~# 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