On Sun, 9 Sep 2012, Florian Wöhrl wrote: > Hi Alan, Oliver, > > Am 08.09.2012 18:04, schrieb Alan Stern: > > If you're certain that the problem is associated with the kernel > > version, you could try using git bisect to pinpoint exactly what > > change to the kernel caused the problem to start. > Never used git bisect before, but will give it a try. There might be a > lot of changes to relevant modules between 2.6 and 3.2 - don't you > think? what modules could be relevant in your opinion? It's hard to say. Certainly things under drivers/usb are relevant. Other parts of the kernel are less likely to be involved, but you never know. > # uname -a > Linux desktop01 3.2.0-29-generic #46-Ubuntu SMP Fri Jul 27 17:03:23 UTC > 2012 x86_64 x86_64 x86_64 GNU/Linux > > # dmesg > [20012.271332] usb 1-1.2: new full-speed USB device number 3 using ehci_hcd > [20017.357551] usb 1-1.2: unable to read config index 0 > descriptor/start: -32 > [20017.357557] usb 1-1.2: chopping to 0 config(s) > [20017.359046] usb 1-1.2: string descriptor 0 read error: -32 > [20017.359207] usb 1-1.2: no configuration chosen from 0 choices I didn't notice this before: The usbmon trace showed -2 and -71 errors but not -32. So why does the log say -32? > > Also, to make sure that nothing important has been omitted, please > > resend the earlier trace without any "grep" filtering. And do the same > > with the new trace. > Ok, will try that. On the RPI there was a lot of traffic going on in > that trace as there's an internal USB hub and a USB GPIO onboard. That's > why I used grep. Filtering out the GPIO traffic probably won't hurt. But leave everything else in. 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
