From: Arjan van de Ven <arjan@infradead.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Dave Jones <davej@redhat.com>,
Kernel development list <linux-kernel@vger.kernel.org>,
David Brownell <david-b@pacbell.net>
Subject: Re: annoying frequent overcurrent messages.
Date: Thu, 13 Jul 2006 14:14:38 +0200 [thread overview]
Message-ID: <1152792878.3024.41.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20060713120815.GA5727@elf.ucw.cz>
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)
next prev parent reply other threads:[~2006-07-13 12:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2006-07-13 14:29 ` Alan Stern
2006-08-08 11:37 ` Pavel Machek
2006-07-13 20:50 Al Boldi
2006-07-14 20:44 ` Pavel Machek
2006-07-15 3:54 ` Al Boldi
-- 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=1152792878.3024.41.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=davej@redhat.com \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=stern@rowland.harvard.edu \
/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
all inboxes | Powered by JetHome®