Comment 14 for bug 435352

I have a MSI Wind U100 rebrand (Advent 4211), and I get this too. Mine has a (0c45:62c0) Microdia Sonix USB 2.0 Camera though. Confirming it's also happening with the new 2.6.31-12 kernel.

And +1 to raising importance. If the camera is enabled during boot (and there is no led to signal whether it is), the system is pretty much borked with no inclination as to why. Already connected usb devices seem to work, but it doesn't react when connecting any new ones (no dmesg messages at all).

One workaround is to "deauthorize" the usb hub (by piping 0 to /sys/bus/usb/devices/usb1/authorized) and then authorizing it again after a few seconds. USB devices gets enumerated, and even the camera works. But if you start toggling the camera it breaks down again. It's more of a recovery method if you accidentally booted with the camera enabled.