Pavel Machek wrote:
> On Thu 13-07-06 23:50:55, Al Boldi wrote:
> > On Thu, 2006-07-13 at 14:08 +0200, Pavel Machek wrote:
> > > > > 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...?
> >
> > I don't want to sound alarming here, but I just had a USBFlashStick
> > fried by a machine, while in suspend-to-ram running 2.6.17.
>
> Well, I have one usb sticdk fried by regular use under linux (like --
> 5 minutes of regular use!) and another fried by my dad on windows. So
> these beasts are crap.
>
> > I am blaming hw, but does anybody know how I can get my data back?
>
> Probably not easily. Specialized shop might desolder flash chip and
> read it directly... or you may try swapping flash chip into
> 'not-yet-fried' stick...
Or there is (should be) a fuse?
Thanks!
--
Al
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
