On Thursday 22 March 2007 12:54 pm, Tino Keitel wrote: > On Thu, Mar 22, 2007 at 15:40:40 -0400, Alan Stern wrote: > > _Something_ is generating those overcurrent > > warnings, and it sure looks like a hardware malfunction. > > But it works with 2.6.20.
So can you bisect to find what caused the problem? We've been afflicted with such strange overcurrent messages off and on for some time. Some hardware triggers them, while most doesn't, and the USB developers don't have any of the hardware that triggers it (that almost goes without saying). It's been clear to me that _something_ the software does is making that more likely to happen. One thing we've been lacking is anything like a usable clue as to what kind of changes would have that failure mode ... and thus, what kind of changes could remove it. - Dave ------------------------------------------------------------------------- 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 _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
