← Back to team overview

kernel-packages team mailing list archive

[Bug 1308628] Re: xhci-hda does not support isochronous streaming on usb 2.0 devices


Forest, thank you for reporting this and helping make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 1308628
When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

** Project changed: ubuntustudio => linux (Ubuntu)

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

** Changed in: linux (Ubuntu)
   Importance: Undecided => Low

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  xhci-hda does not support isochronous streaming on usb 2.0 devices

Status in linux package in Ubuntu:

Bug description:
  I have a Presonus AudioBox 1818VSL (usb audio interface,) which was
  working flawlessly for about 2 years on ubuntu 12.04. I bought a new
  computer with usb 3 ports and installed 14.04, and suddenly the audio
  is popping and crackling. The computer is loading the 1818vsl as a usb
  3 device using xchi-hda even though it's a usb 2 device and should use
  ehci-hda. From what I understand on this thread, this is a problem
  that affects other usb audio interfaces as well:


  I found other users in the forums having this problem. Since xchi-hda
  is prebaked into the kernel, the only workarounds are

  1. Disable usb 3 in BIOS or
  2. If you don't have that option in BIOS, compile a new kernel with xchi-hda and ehci-hda enabled as modules and then blacklist xhci-hda.

  These shouldn't be the only options for Ubuntu users!

  My proposal is build xhci-hda as a module in the default Ubuntu kernel
  so that the affected users can blacklist it without having to compile
  an entirely new kernel. There are very few usb 3 devices at the moment
  anyways, and this should have very little effect on performance for
  other users.

To manage notifications about this bug go to: