On Wed, 26 Oct 2011, Anton Alekseev wrote: > Hello. I've sent this message to <linux-kernel@xxxxxxxxxxxxxxx> but there's > no such recipient, so forwarding it to you. You should always post messages like this to the appropriate mailing list. In this case, that's the linux-usb list. (And <linux-kernel@xxxxxxxxxxxxxxx> is a perfectly valid recipient; I send email messages there quite often. However it doesn't like HTML-formatted mail.) > ---------- Forwarded message ---------- > From: Anton Alekseev <nullakilla@xxxxxxxxx> > Date: 2011/10/24 > Subject: EHCI driver problem > To: linux-kernel@xxxxxxxxxxxxxxx > > > Hello! > > I have M-Audio Fast Track Ultra soundcard that is USB Audio Device Class > compliant device. > It works fine in kernel < 2.6.38.x, but in kernel 3.0 and higher when I try > to initialize this device for BUFFER=128 samples and FREQUENCY=48000 ALSA > fails to initialize. > > The only reason for me to use kernel >= 3.0 is that there's no MIXER support > for this soundcard in earlier kernels. > > But problem NOT in ALSA, I think, but in EHCI driver because I've tried this > on Ubuntu and Fedora different releases and on different hardware. > > alsa-info.sh output: > http://www.alsa-project.org/db/?f=c3f2296dbeb507cb9c15f22c11e44b6a5305deaa > > I've posted stuff about this problem here on > ubuntuforums<http://ubuntuforums.org/showthread.php?t=1867974> > . You should have included more information in the bug report. It looks like the real problem is this: [ 1810.546888] ehci_hcd 0000:00:12.2: force halt; handshake ffffc9000031e024 00004000 00000000 -> -110 [ 1810.546894] ehci_hcd 0000:00:12.2: HC died; cleaning up Is that right? It means the kernel told your EHCI controller to turn off its periodic schedule, but the controller didn't do it. There's a workaround in the kernel which may fix this, but it wasn't enabled (currently it is used only for Intel controllers). What is the output from "lspci -n"? Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
