From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 216630] New: config 1 has an invalid interface number: 2 but max is 1
Date: Thu, 27 Oct 2022 09:28:55 +0000 [thread overview]
Message-ID: <bug-216630-208809@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=216630
Bug ID: 216630
Summary: config 1 has an invalid interface number: 2 but max is
1
Product: Drivers
Version: 2.5
Kernel Version: 6.0.5
Hardware: AMD
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: USB
Assignee: drivers_usb@kernel-bugs.kernel.org
Reporter: aros@gmx.com
Regression: No
I'm getting these messages on boot and I wonder if they are superficial,
there's a bug in the kernel or my HW is not working properly:
usb 3-6: config 1 has an invalid interface number: 2 but max is 1
usb 3-6: config 1 has no interface number 1
lsusb -tv
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
|__ Port 5: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter
|__ Port 5: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter
|__ Port 6: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
ID 0b05:18f3 ASUSTek Computer, Inc.
|__ Port 6: Dev 3, If 2, Class=Human Interface Device, Driver=usbhid, 12M
ID 0b05:18f3 ASUSTek Computer, Inc.
--
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 reply other threads:[~2022-10-27 9:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 9:28 bugzilla-daemon [this message]
2022-10-27 20:09 ` [Bug 216630] config 1 has an invalid interface number: 2 but max is 1 bugzilla-daemon
2022-10-27 20:12 ` bugzilla-daemon
2022-10-27 20:52 ` bugzilla-daemon
2022-10-27 20:53 ` bugzilla-daemon
2022-11-09 11:35 ` 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-216630-208809@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.