Messages in this thread | | | Subject | Re: annoying frequent overcurrent messages. | From | Arjan van de Ven <> | Date | Thu, 13 Jul 2006 14:14:38 +0200 |
| |
On Thu, 2006-07-13 at 14:08 +0200, Pavel Machek wrote: > Hi! > > > > I have a box that's having its dmesg flooded with.. > > > > > > hub 1-0:1.0: over-current change on port 1 > > > hub 1-0:1.0: over-current change on port 2 > > > hub 1-0:1.0: over-current change on port 1 > > > hub 1-0:1.0: over-current change on port 2 > > ... > > > > > over and over again.. > > > The thing is, this box doesn't even have any USB devices connected to it, > > > so there's absolutely nothing I can do to remedy this. > > > > Well, overcurrent is a potentially dangerous situation. That's why it > > gets reported with dev_err priority. > > Well, I see overcurrents all the time while doing suspend/resume... > > Why is it dangerous? USB should survive plugging something that > connects +5V and ground. It may turn your machine off, but that should > be it...?
it's fun if your main storage resides near it on the same hub... like your suspend device (now ok suspend-to-usb-disk is silly I suppose, but I can think of some really cool usage models that that allows in an office-less office)
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |