annoying frequent overcurrent messages.
Quoted 12 lines · Pavel Machek
Quoted 12 lines
Quoted 6 lines
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...
Quoted 3 lines
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.
Quoted 8 lines
Quoted 2 lines
Well, overcurrent is a potentially dangerous situation. That's why it gets reported with
dev_errpriority.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.
I am blaming hw, but does anybody know how I can get my data back?
Thanks!
--
Al
Quoted 16 lines · Al Boldi
Quoted 15 lines · Pavel Machek
Quoted 14 lines
Quoted 6 lines
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...
Quoted 3 lines
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_errpriority.
Quoted 8 lines
Quoted 5 lines
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.
Quoted 1 line
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...
Signature · 1 line
Thanks for all the (sleeping) penguins.
Quoted 31 lines · Pavel Machek
Quoted 17 lines · Al Boldi
Quoted 16 lines · Pavel Machek
Quoted 15 lines
Quoted 6 lines
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...
Quoted 3 lines
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_errpriority.Quoted 8 lines
Quoted 5 lines
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.
Quoted 5 lines
Quoted 1 line
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