On Sun, Nov 04, 2012 at 03:07:35PM -0500, Alan Stern wrote: [...] > The first thing you should do is test a 3.6 kernel with > CONFIG_USB_DEBUG enabled and post the dmesg log showing the problem. > That will help indicate what is going wrong. I guess this is a compile time option. Is it any run-time possibility to achieve a similar result? > If that doesn't suggest a solution, the next thing you should do is use > git bisect to find which change to the kernel is responsible for the > errors. For this to work, you have to be able to tell reliably whether > the problem is present or not with a particular kernel, but it sounds > like that should be easy enough. This seems a bit out of reach, for several reasons. I'll have to use a Fedora kernel, which might have its own patches and I suspect things will become complicated beyond my capability to manage them. I might try on a different PC, with a vanilla kernel, not sure... I was hoping someone had in mind what could be the hotspot and the possibility to check it quickly. bye, -- piergiorgio -- 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
