From: Pavel Machek <pavel@suse.cz>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: 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: Tue, 8 Aug 2006 13:37:37 +0200 [thread overview]
Message-ID: <20060808113737.GH4442@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0607131027200.6702-100000@iolanthe.rowland.org>
Hi!
> > > 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...?
>
> The key words here are "potentially", "should", and "may".
>
> BTW, what sort of overcurrents do you see during suspend/resume?
Okay, that was on X32, and I'm not using it for now, sorry about
that. "Overcurrent on port XY" was the message, IIRC, but...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2006-08-08 11:37 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 ` annoying frequent overcurrent messages 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 [this message]
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=20060808113737.GH4442@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=davej@redhat.com \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--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