On Thu, 11 Jan 2007, Jon Smirl wrote: > In this log I booted with it plugged in and let the usbhid drivers load. > I then successively modprobe/rmmod them. > > There were only two ways I could get the device working once it went > into suspend: > rmmod/modprobe uhci_hcd;modprobe usbhid > usbreset the audio device
That makes sense. When you modprobe uhci_hcd, all the devices on the bus get reset, including the audio device. > If the device was working I can do: > rmmod usbhid;modprobe usbhid - works > rmmod usbhid;sleep 5; modprobe usbhid fails. Again, this makes sense. The first sequence doesn't cause an autosuspend and the second does. It certainly looks as though your device doesn't want to resume when it's plugged into a root port. Have you got a different computer to try this on? > Next time I will turn on printk times. > I never hit the error -19 this time. I noticed that too. The hardware resume bug never occurred. That's how it was with me; sometimes it would crop up several times in a row and then it would just disappear... Makes debugging rather difficult. Alan Stern ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
