From: Pavel Machek <pavel@ucw.cz>
To: Al Boldi <a1426z@gawab.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: annoying frequent overcurrent messages.
Date: Fri, 14 Jul 2006 20:44:46 +0000 [thread overview]
Message-ID: <20060714204445.GC8731@ucw.cz> (raw)
In-Reply-To: <200607132350.55978.a1426z@gawab.com>
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...
--
Thanks for all the (sleeping) penguins.
next prev parent reply other threads:[~2006-07-14 20:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 20:50 annoying frequent overcurrent messages Al Boldi
2006-07-14 20:44 ` Pavel Machek [this message]
2006-07-15 3:54 ` Al Boldi
[not found] <200607111747.13529.david-b@pacbell.net>
2006-07-12 14:19 ` Alan Stern
2006-07-12 16:56 ` Dave Jones
2006-07-12 17:09 ` Ray Lee
2006-07-12 17:19 ` Alan Stern
2006-07-12 17:34 ` Ray Lee
2006-07-12 17:45 ` Alan Stern
2006-07-12 18:06 ` Ray Lee
2006-07-12 17:51 ` Dave Jones
2006-07-12 18:07 ` Alan Stern
2006-07-12 18:26 ` Alan Cox
2006-07-13 12:08 ` Pavel Machek
2006-07-13 12:14 ` Arjan van de Ven
2006-07-13 14:29 ` Alan Stern
2006-08-08 11:37 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2006-07-12 0:37 Dave Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060714204445.GC8731@ucw.cz \
--to=pavel@ucw.cz \
--cc=a1426z@gawab.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox