Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #90921 > unrolled thread

Bug#1126149: linux: usb enumeration fails with error -32 for Krom Kreator keyboard

Started byVicboom <fglezjuarez@gmail.com>
First post2026-01-22 13:50 +0100
Last post2026-02-08 08:50 +0100
Articles 7 — 3 participants

Back to article view | Back to linux.debian.kernel

Contents

  Bug#1126149: linux: usb enumeration fails with error -32 for Krom Kreator keyboard Vicboom <fglezjuarez@gmail.com> - 2026-01-22 13:50 +0100
    Processed: Re: Bug#1126149: linux: usb enumeration fails with  error -32 for Krom Kreator keyboard "Debian Bug Tracking System" <owner@bugs.debian.org> - 2026-01-24 21:00 +0100
    Bug#1126149: linux: usb enumeration fails with error -32 for Krom Kreator keyboard Salvatore Bonaccorso <carnil@debian.org> - 2026-01-24 21:00 +0100
    Bug#1126149: linux: usb enumeration fails with error -32 for Krom Kreator keyboard Salvatore Bonaccorso <carnil@debian.org> - 2026-01-27 06:00 +0100
    Bug#1126149: linux: usb enumeration fails with error -32 for Krom Kreator keyboard Salvatore Bonaccorso <carnil@debian.org> - 2026-02-07 12:10 +0100
    Processed: Re: Bug#1126149: linux: usb enumeration fails with  error -32 for Krom Kreator keyboard "Debian Bug Tracking System" <owner@bugs.debian.org> - 2026-02-08 08:50 +0100
    Bug#1126149: linux: usb enumeration fails with error -32 for Krom Kreator keyboard Salvatore Bonaccorso <carnil@debian.org> - 2026-02-08 08:50 +0100

#90921 — Bug#1126149: linux: usb enumeration fails with error -32 for Krom Kreator keyboard

FromVicboom <fglezjuarez@gmail.com>
Date2026-01-22 13:50 +0100
SubjectBug#1126149: linux: usb enumeration fails with error -32 for Krom Kreator keyboard
Message-ID<Mg2il-cr0p-1@gated-at.bofh.it>
Source: linux
Severity: important
Tags: upstream
X-Debbugs-Cc: debian-amd64@lists.debian.org, fglezjuarez@gmail.com
User: debian-amd64@lists.debian.org
Usertags: amd64

Dear Maintainer,

   * What led up to the situation?
Connecting a Krom Kreator keyboard to any USB port on the system
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
- Tried different USB ports (USB 2.0, USB 3.0, front panel, rear I/O)
- Tried through USB hubs (powered and unpowered)
- Tried different USB quirks via kernel parameters
   * What was the outcome of this action?
Same problem persists: "usb *: unable to read config index 0 descriptor/start: -32"
The keyboard fails to enumerate and is unusable in Linux.
Previously it showed error -71 but after some update it changed to -32
   * What outcome did you expect instead?
Keyboard should enumerate and work normally as it does in BIOS and Windows.

=== dmesg output when keyboard connected ===
[10832.805157] usb 5-1.2: new full-speed USB device number 16 using xhci_hcd
[10838.070073] usb 5-1.2: unable to read config index 0 descriptor/start: -32
[10838.070082] usb 5-1.2: chopping to 0 config(s)
[10838.070086] usb 5-1.2: can't read configurations, error -32
[10838.165080] usb 5-1.2: new full-speed USB device number 17 using xhci_hcd
[10843.445780] usb 5-1.2: unable to read config index 0 descriptor/start: -32
[10843.445790] usb 5-1.2: chopping to 0 config(s)
[10843.445794] usb 5-1.2: can't read configurations, error -32
[10843.446086] usb 5-1-port2: attempt power cycle
[10844.029144] usb 5-1.2: new full-speed USB device number 18 using xhci_hcd
[10849.077690] usb 5-1.2: unable to read config index 0 descriptor/start: -32
[10849.077698] usb 5-1.2: chopping to 0 config(s)
[10849.077701] usb 5-1.2: can't read configurations, error -32
[10849.149121] usb 5-1.2: new full-speed USB device number 19 using xhci_hcd
[10854.197667] usb 5-1.2: unable to read config index 0 descriptor/start: -32
[10854.197675] usb 5-1.2: chopping to 0 config(s)
[10854.197678] usb 5-1.2: can't read configurations, error -32
[10854.197837] usb 5-1-port2: unable to enumerate USB device

=== lsusb -t output ===
/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/10p, 480M
    |__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 001: Dev 002, If 1, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 002: Dev 003, If 0, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 002: Dev 003, If 1, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 003: Dev 004, If 0, Class=Mass Storage, Driver=usb-storage, 480M
    |__ Port 005: Dev 005, If 0, Class=Vendor Specific Class, Driver=[none], 12M
    |__ Port 005: Dev 005, If 2, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 006: Dev 006, If 0, Class=Audio, Driver=snd-usb-audio, 480M
    |__ Port 006: Dev 006, If 1, Class=Audio, Driver=snd-usb-audio, 480M
    |__ Port 006: Dev 006, If 2, Class=Audio, Driver=snd-usb-audio, 480M
    |__ Port 006: Dev 006, If 3, Class=Application Specific Interface, Driver=[none], 480M
    |__ Port 008: Dev 007, If 0, Class=Vendor Specific Class, Driver=xpad, 12M
/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M
/:  Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 480M
/:  Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M
/:  Bus 005.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M
    |__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/5p, 480M
        |__ Port 004: Dev 003, If 0, Class=Hub, Driver=hub/4p, 480M
            |__ Port 003: Dev 005, If 0, Class=Communications, Driver=cdc_ether, 480M
            |__ Port 003: Dev 005, If 1, Class=CDC Data, Driver=cdc_ether, 480M
            |__ Port 004: Dev 006, If 0, Class=Hub, Driver=hub/4p, 480M
                |__ Port 003: Dev 007, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 005: Dev 004, If 0, Class=Billboard, Driver=[none], 480M
/:  Bus 006.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M
/:  Bus 007.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 10000M
/:  Bus 008.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M
/:  Bus 009.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 10000M

=== Additional information ===
-The keyboard works perfectly in BIOS/UEFI and Windows 10/11
-Keyboard does not work in this specific system, probably due to an xhci_hcd issue on the A620 chipset

-- System Information:
Debian Release: 13.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

-- Hardware:
Motherboard: Asus A620AM-K
CPU: AMD Ryzen 5 8400F
USB controllers visible in lspci:
05:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:43ed]
08:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:15b9]
08:00.4 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:15ba]
0a:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:15c0]
0a:00.4 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:15c1]
Other USB devices working:
-Mars Gaming MM55
-Mars Gaming MKMINI
-M-Audio M-Track 2x2
-RedDragon Saturn G807
-Huion HS611
-GameSir-Z1

Kernel: Linux 6.17.13+deb13-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

[toc] | [next] | [standalone]

#90955 — Processed: Re: Bug#1126149: linux: usb enumeration fails with error -32 for Krom Kreator keyboard

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2026-01-24 21:00 +0100
SubjectProcessed: Re: Bug#1126149: linux: usb enumeration fails with error -32 for Krom Kreator keyboard
Message-ID<MgRXz-d3k5-1@gated-at.bofh.it>
In reply to#90921
Processing control commands:

> tags -1 + moreinfo
Bug #1126149 [src:linux] linux: usb enumeration fails with error -32 for Krom Kreator keyboard
Added tag(s) moreinfo.

-- 
1126149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1126149
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#90956

FromSalvatore Bonaccorso <carnil@debian.org>
Date2026-01-24 21:00 +0100
Message-ID<MgRXz-d3k5-3@gated-at.bofh.it>
In reply to#90921
Control: tags -1 + moreinfo

Hi,

On Thu, Jan 22, 2026 at 01:39:29PM +0100, Vicboom wrote:
> Source: linux
> Severity: important
> Tags: upstream
> X-Debbugs-Cc: debian-amd64@lists.debian.org, fglezjuarez@gmail.com
> User: debian-amd64@lists.debian.org
> Usertags: amd64
> 
> Dear Maintainer,
> 
>    * What led up to the situation?
> Connecting a Krom Kreator keyboard to any USB port on the system
>    * What exactly did you do (or not do) that was effective (or
>      ineffective)?
> - Tried different USB ports (USB 2.0, USB 3.0, front panel, rear I/O)
> - Tried through USB hubs (powered and unpowered)
> - Tried different USB quirks via kernel parameters
>    * What was the outcome of this action?
> Same problem persists: "usb *: unable to read config index 0 descriptor/start: -32"
> The keyboard fails to enumerate and is unusable in Linux.
> Previously it showed error -71 but after some update it changed to -32
>    * What outcome did you expect instead?
> Keyboard should enumerate and work normally as it does in BIOS and Windows.
> 
> === dmesg output when keyboard connected ===
> [10832.805157] usb 5-1.2: new full-speed USB device number 16 using xhci_hcd
> [10838.070073] usb 5-1.2: unable to read config index 0 descriptor/start: -32
> [10838.070082] usb 5-1.2: chopping to 0 config(s)
> [10838.070086] usb 5-1.2: can't read configurations, error -32
> [10838.165080] usb 5-1.2: new full-speed USB device number 17 using xhci_hcd
> [10843.445780] usb 5-1.2: unable to read config index 0 descriptor/start: -32
> [10843.445790] usb 5-1.2: chopping to 0 config(s)
> [10843.445794] usb 5-1.2: can't read configurations, error -32
> [10843.446086] usb 5-1-port2: attempt power cycle
> [10844.029144] usb 5-1.2: new full-speed USB device number 18 using xhci_hcd
> [10849.077690] usb 5-1.2: unable to read config index 0 descriptor/start: -32
> [10849.077698] usb 5-1.2: chopping to 0 config(s)
> [10849.077701] usb 5-1.2: can't read configurations, error -32
> [10849.149121] usb 5-1.2: new full-speed USB device number 19 using xhci_hcd
> [10854.197667] usb 5-1.2: unable to read config index 0 descriptor/start: -32
> [10854.197675] usb 5-1.2: chopping to 0 config(s)
> [10854.197678] usb 5-1.2: can't read configurations, error -32
> [10854.197837] usb 5-1-port2: unable to enumerate USB device
> 
> === lsusb -t output ===
> /:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/10p, 480M
>     |__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M
>     |__ Port 001: Dev 002, If 1, Class=Human Interface Device, Driver=usbhid, 12M
>     |__ Port 002: Dev 003, If 0, Class=Human Interface Device, Driver=usbhid, 12M
>     |__ Port 002: Dev 003, If 1, Class=Human Interface Device, Driver=usbhid, 12M
>     |__ Port 003: Dev 004, If 0, Class=Mass Storage, Driver=usb-storage, 480M
>     |__ Port 005: Dev 005, If 0, Class=Vendor Specific Class, Driver=[none], 12M
>     |__ Port 005: Dev 005, If 2, Class=Human Interface Device, Driver=usbhid, 12M
>     |__ Port 006: Dev 006, If 0, Class=Audio, Driver=snd-usb-audio, 480M
>     |__ Port 006: Dev 006, If 1, Class=Audio, Driver=snd-usb-audio, 480M
>     |__ Port 006: Dev 006, If 2, Class=Audio, Driver=snd-usb-audio, 480M
>     |__ Port 006: Dev 006, If 3, Class=Application Specific Interface, Driver=[none], 480M
>     |__ Port 008: Dev 007, If 0, Class=Vendor Specific Class, Driver=xpad, 12M
> /:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M
> /:  Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 480M
> /:  Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M
> /:  Bus 005.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M
>     |__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/5p, 480M
>         |__ Port 004: Dev 003, If 0, Class=Hub, Driver=hub/4p, 480M
>             |__ Port 003: Dev 005, If 0, Class=Communications, Driver=cdc_ether, 480M
>             |__ Port 003: Dev 005, If 1, Class=CDC Data, Driver=cdc_ether, 480M
>             |__ Port 004: Dev 006, If 0, Class=Hub, Driver=hub/4p, 480M
>                 |__ Port 003: Dev 007, If 0, Class=Human Interface Device, Driver=usbhid, 12M
>         |__ Port 005: Dev 004, If 0, Class=Billboard, Driver=[none], 480M
> /:  Bus 006.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M
> /:  Bus 007.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 10000M
> /:  Bus 008.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M
> /:  Bus 009.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 10000M
> 
> === Additional information ===
> -The keyboard works perfectly in BIOS/UEFI and Windows 10/11
> -Keyboard does not work in this specific system, probably due to an xhci_hcd issue on the A620 chipset
> 
> -- System Information:
> Debian Release: 13.3
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> -- Hardware:
> Motherboard: Asus A620AM-K
> CPU: AMD Ryzen 5 8400F
> USB controllers visible in lspci:
> 05:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:43ed]
> 08:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:15b9]
> 08:00.4 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:15ba]
> 0a:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:15c0]
> 0a:00.4 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:15c1]
> Other USB devices working:
> -Mars Gaming MM55
> -Mars Gaming MKMINI
> -M-Audio M-Track 2x2
> -RedDragon Saturn G807
> -Huion HS611
> -GameSir-Z1

Can you please attach the keyboard and the provide the *full* kernel
log, I'm interested to see the idVendor, and idProduct.

Please do as well provide a verbose output of lsusb for the device in
a moment it is seen.

If you do several plugging/unpuggling cycles, does it sometimes work
correctly?

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#90984

FromSalvatore Bonaccorso <carnil@debian.org>
Date2026-01-27 06:00 +0100
Message-ID<MhJlf-dD7y-3@gated-at.bofh.it>
In reply to#90921
Hi

[Please include the Debian bug address as well as we want to keep
track of the pgorgress and information on the bug]

On Tue, Jan 27, 2026 at 12:16:07AM +0000, Vicboom18 wrote:
> I used a Gigabyte G5 KC that also has Debian Trixie, the 2 *bad.log files
> are what's shown in the PC where the keyboard doesn't work while the
> *working.log files are what's shown in the laptop, in both cases the full
> dmesg log since the keyboard is connected and the lsusb executed after the
> dmesg.
> For what I could find the idVendor is 0x5566 ZXWMicroChip and the idProduct
> is 0x0008 ZXW-Keyboard.
> Plugging and unplugging several times does not work.

The full boot log would show more on the surrounding system so if you
can provide if for both the non working system and the working laptop
system can you please provide it still. I'm confused if they both run
trixie but work on one but not the other.

Can you please try the following testing patch please on the non
working system:

diff --git a/drivers/usb/core/quirks.c b/drivers/usb/core/quirks.c
index c4d85089d19b..7e6de2a27416 100644
--- a/drivers/usb/core/quirks.c
+++ b/drivers/usb/core/quirks.c
@@ -581,6 +581,9 @@ static const struct usb_device_id usb_quirk_list[] = {
        /* VCOM device */
        { USB_DEVICE(0x4296, 0x7570), .driver_info = USB_QUIRK_CONFIG_INTF_STRINGS },

+       /* ZXWMicroChip ZXW-Keyboard */
+       { USB_DEVICE(0x5566, 0x0008), .driver_info = USB_QUIRK_NO_LPM },
+
        /* INTEL VALUE SSD */
        { USB_DEVICE(0x8086, 0xf1a5), .driver_info = USB_QUIRK_RESET_RESUME },

As the issue looks somehow similar to 181135bb20dc ("usb: add NO_LPM
quirk for Realforce 87U Keyboard").

To build and test a kernel with a patch applied on top see:
https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#id-1.6.6.4

If you struggle at any step with the above please let us know so we
might try to outline it smoother.

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#91098

FromSalvatore Bonaccorso <carnil@debian.org>
Date2026-02-07 12:10 +0100
Message-ID<MlOml-gnRl-3@gated-at.bofh.it>
In reply to#90921
Hi,

On Sat, Feb 07, 2026 at 11:35:03AM +0100, Salvatore Bonaccorso wrote:
> Hi,
> 
> On Fri, Feb 06, 2026 at 09:48:34PM +0000, Vicboom18 wrote:
> > This bug has also been reported to Debian. You can track it here:
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1126149 (Debian Bug
> > #1126149).
> 
> Well yes, I know it is reported there in Debian.
> 
> let me phrase it differently. I won't provide private support, that is
> please *always* include the Debian BTS email address as well in the
> replies, so others in the team are aware as well of the progress.
> 
> > Both boot logs have attached, in both cases the computer were turned on
> > with the keyboard connected, then it was disconnected and connected again.
> > 
> > As it can bee seen in PC_boot.log I also went back to the 6.12 LTS kernel,
> > as the 6.17 was installed in order to try to fix the issue on my own (with
> > no success)
> 
> Thank you. So I see in the one variant it seems to recocnize correctly
> the keyboard. So we should still try to quirk before forwarding your
> report to upstream.
> 
> > When trying the official guide (from point 4.5.1 up to 4.5.2, skipping
> > 4.5.1.1)  it seems to fail in the $ debian/bin/test-patches command.
> 
> I need here the full context. As
> 
> set +e; QUILT_PC=.pc quilt unapplied --quiltrc - >/dev/null && echo 'Patch series not fully applied'; test $? -eq 1
> Patch series not fully applied
> 
> 
> I think you need to massage a bit the patch yet for context in
> 6.12.63. I will see if I can provide you a test kernel to test it more
> reasily.

here we go, can you please test it with the (unofficial!) kernel
provided in
https://people.debian.org/~carnil/tmp/linux/1126149/
and report back if that resolves the issue?

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#91108 — Processed: Re: Bug#1126149: linux: usb enumeration fails with error -32 for Krom Kreator keyboard

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2026-02-08 08:50 +0100
SubjectProcessed: Re: Bug#1126149: linux: usb enumeration fails with error -32 for Krom Kreator keyboard
Message-ID<Mm7Im-gAsp-17@gated-at.bofh.it>
In reply to#90921
Processing control commands:

> tags -1 - moreinfo patch
Bug #1126149 [src:linux] linux: usb enumeration fails with error -32 for Krom Kreator keyboard
Removed tag(s) patch and moreinfo.

-- 
1126149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1126149
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#91109

FromSalvatore Bonaccorso <carnil@debian.org>
Date2026-02-08 08:50 +0100
Message-ID<Mm7Il-gAsp-9@gated-at.bofh.it>
In reply to#90921

[Multipart message — attachments visible in raw view] — view raw

Control: tags -1 - moreinfo patch

Hi,

[adding back the BTS bug]

On Sat, Feb 07, 2026 at 09:19:38PM +0000, Vicboom18 wrote:
> debian-amd64@lists.debian.org
> 
> It still doesn't work. The log attached was made turning on the PC with the
> keyboard connected, then plugging it off and then on again as done prior

Thanks for reporting back.

Regards,
Salvatore

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web