On Wed, 4 Nov 2009, Oliver Neukum wrote: > This has a tendency for an ugly cycle. > > Defective SD card -> error handler resets -> reader disconnected > -> udev switches mode -> SD reader scanned -> defective SD card -> ... > > I think we need a quirk for such devices. I think it is cleaner to have > it add usbcore's level as we cannot be sure this is always limited > to the storage driver. Comments? Bear in mind that we already have the potential for similar ugly cycles. Pretty much any device that disconnects itself when an error or reset occurs and then reconnects will cause one. For example, there have been reports of this sort of thing happening during enumeration of the built-in Bluetooth interface in some laptops. People complain about their system logs getting flooded with error and disconnect messages. This is nothing new, and it's not directly related to mode-switching. The way to fix it is to have the hub driver look out for devices that reconnect too much and too often. 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
