Linked by Thom Holwerda on Fri 23rd Aug 2013 08:37 UTC

Pretty much for my entire career in Linux USB (eight years now?), we've been complaining about how USB device power management just sucks. We enable auto-suspend for a USB device driver, and find dozens of different USB devices that simply disconnect from the bus when auto-suspend is enabled.

For years, we've blamed those devices for being cheap, crappy, and broken. We talked about blacklists in the kernel, and ripped those out when they got too big. We've talked about whitelists in userspace, but not many distros have time to cultivate such lists.

It turns out it's not always the device's fault.

Fascinating bug.

Permalink for comment 570419
To read all comments associated with this story, please click here.
Member since:

This snarky Windows Developer DID read through the entire post, and the comments. That is where he read about all the problems this is causing for users, how someone solved the problem by using a Mac where USB "just works" and where someone posts that in the Windows driver a timeout of 10ms works just fine.

This snarky Windows Developer also read about all the workarounds that have been discussed and deployed to fix this problem previously (blacklists that grew out of proportions, whitelists that wouldn't be maintained)

I did enjoy the schadenfreude although I don't know why. Mostly I am happy this will (soon, hopefully) solve the problems of many endusers

P.S. I am just a developer that uses .NET. I am not "developing Windows". I do have to defend Windows as a closed platform because I keep hearing "x is open source so everyone can look at the code and fix things but they cannot fix this because it is closed" which irritates me a lot

Reply Parent Score: 2