Red Hat Bugzilla – Bug 185809
USB audio driver produces kernel errors in log when connected through USB hub
Last modified: 2007-11-30 17:11:27 EST
Description of problem:
Using USB audio headset with ekiga produces kernel error messages
Mar 18 19:59:18 localhost kernel: cannot submit datapipe for urb 0, err = -28
Mar 18 19:59:49 localhost last message repeated 2086 times
Mar 18 20:04:59 localhost last message repeated 998 times
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.install fedora cor5test3
2.update kernel, ekiga, udev
3.call using USB headset
get error messages, but the audio works.
audio work, no error messages
These errors are only displayed when USB headset is connected through usb hub
D-Link DUB-H4. When plugged directly, it works OK.
seems like nearly the same bug as #34002 in ubuntu
It's a wontfix material. This problem needs serious work with the scheduling
of ISOs in EHCI. I think more of it started to get to light now that TT is
enabled in high-speed hubs. I suppose one option is to use an old 1.1 hub,
but even then scheduling is not optimal. For example, INTs and ISOs step
on each other. David Brownell tackled this in the past, maybe he can be
Yes, actually audio even when plugged directly, is not ideal. Others complain
that they do not hear me someitmes, I hear some clicks everytime.
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.
Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.
This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.
Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.
In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed. See bug 207474 for further details.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.
I checked against kernel-2.6.20-1.2307.fc5, it is working OK