Comment 274 for bug 85488

It didn't seem to me that my device (canoscan lide 25, plustek) was crashing. Being able to run scanimage multiple times in sequence suggests that suspend works fine as long as the device is resumed properly. If I'm wrong about that I'd like to know in more detail what's really happening. The reason I'm pressing the issue is that, as I stated earlier, blacklisting specific scanners means that new scanners won't be blacklisted until someone runs into this issue, reports it, and in the case of Ubuntu waits 6 months to 1 year for their device to be added to the blacklist.

Blacklisting is not a forward-looking solution. Perhaps there is some way to probe the device to see if it supports suspend. Maybe by trying to suspend it, resume it, and see if it works. Or active a workaround whenever a device exhibits this behavior. A check of some kind to see if the device did actually resume and force it to wake up somehow if it didn't (by a reset and then a flag to say don't suspend it again).

Whatever the solution is it should work for devices that don't exist yet. Otherwise USB suspend is simply not safe and must not be used.