On Sat, 26 Jan 2013, Udo van den Heuvel wrote: > On 2013-01-26 15:56, Alan Stern wrote: > > That SF bit in the intrstatus register is the one causing the problem, > > I think. It is not set in the intrenable register, so the controller > > shouldn't issue any IRQs. But it does, nonetheless. Turning off SF > > apparently doesn't help -- the controller turns it on again a > > millisecond later anyway. > > > > So it looks like there's nothing we can do about this. It's just bad > > hardware. Sorry. > > So why was this problem introduced on my old hardware after running for > years without this issue? > This new hardware is just 2-3 months old or so should not have grown > extra 'features'. > Please explain. I can't. I don't know what's going on with your systems. But nobody else seems to be experiencing this problem. You can always try installing an earlier version of the kernel to see if that makes the problem go away. 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
