On Mon, 2 Jul 2012, Sadasivan Shaiju wrote: > On Mon, Jul 2, 2012 at 9:08 AM, shaiju shaiju <shshaiju@xxxxxxxxx> wrote: > > Hi Peter, > > > > I have attached the dmesg for a working case and a non working > > case with CONFIG_USB_DEBUG option set . > > > > Looks like here is what is happening in the case of error . It > > try to use OHCI/UHCI driver instead of EHCI driver and try to > > set the port to fullspeed, instead of high speed . Right. As Peter said, this is caused by a hardware problem. > This happens only some times . Say after 30 reboots the problem > occurs . If it is a hardware problem how it is working in other > cases . Because it is intermittent. Actually that doesn't explain anything; it just means that sometimes the problem occurs and sometimes it goes away. But hardware problems can be like that, whereas software problems tend not to be. In this case, the problem seems to be that some part of the hardware is marginally out of spec. Most of the time it works but sometimes it doesn't. > We have a rate matching hub embedded in the PCH . The hardware used > is Ibex Peak/Jasper Forest . > This is an eUSB . I am not sure how I can try the above . It may be that the electrical connections between the EHCI controller and the rate-matching hub are marginally bad. 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
