From: Waldemar Brodkorb <wbx@openadk.org>
To: linux-kernel@vger.kernel.org
Subject: xhci: Not enough bandwidth for new device state
Date: Wed, 28 Feb 2018 21:54:44 +0100 [thread overview]
Message-ID: <20180228205444.GX12535@waldemar-brodkorb.de> (raw)
Hi,
I am getting these messages from a Debian 9.3 system using
Linux 4.9.x:
[ 547.352746] usb 3-5.2: 3:1: usb_set_interface failed (-28)
[ 548.352865] usb 3-5.3: Not enough bandwidth for new device state.
[ 548.352868] usb 3-5.3: Not enough bandwidth for altsetting 1
I have connected a 7-Port USB 3.0 Hub to my machine.
I have 6 different Headsets and USB Soundcards connected to the HUB.
As soon as I start a C++ application which opens all ALSA devices
I get these errors and the USB stopps working correctly.
I think the maximum count of USB sound devices, which behave stable
is three or four.
Is this some miscalculation of the Linux kernel regarding the USB
bandwidth usage? How I can determine how much bandwidth the USB
sound card driver preallocates?
Or are five USB soundcards really too much for an USB 3.0 bus?
Thanks in advance for any advise,
best regards
Waldemar
next reply other threads:[~2018-02-28 21:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 20:54 Waldemar Brodkorb [this message]
2018-03-01 7:10 ` Waldemar Brodkorb
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=20180228205444.GX12535@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®