From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 216630] config 1 has an invalid interface number: 2 but max is 1
Date: Thu, 27 Oct 2022 20:12:53 +0000 [thread overview]
Message-ID: <bug-216630-208809-bReOfAt1cP@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216630-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216630
--- Comment #2 from Artem S. Tashkinov (aros@gmx.com) ---
(In reply to Alan Stern from comment #1)
> These messages indicate that the device's firmware doesn't conform to the
> USB specification. You can see the problem in the lsusb output for Port 6
> Dev 3. The two entries say "If 0" and "If 2". But the USB spec says that
> interface numbers must be consecutive (starting at 0).
>
> It's a harmless error.
Thanks a lot for the explanation!
Since these messages can be seen at: dmesg -t --level=alert,crit,err,emerg,warn
is is it possible to decrease their level to e.g. notice or info?
I've google for it and there are literally hundreds of affected systems. I
don't think it's worth alerting the use to something they are unable to fix or
get fixed.
--
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:[~2022-10-27 20:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 9:28 [Bug 216630] New: config 1 has an invalid interface number: 2 but max is 1 bugzilla-daemon
2022-10-27 20:09 ` [Bug 216630] " bugzilla-daemon
2022-10-27 20:12 ` bugzilla-daemon [this message]
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-bReOfAt1cP@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.