mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ray Lee" <madrabbit@gmail.com>
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: Wed, 12 Jul 2006 10:09:05 -0700	[thread overview]
Message-ID: <2c0942db0607121009l1fc00764ye0b98d686700a74c@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0607121012570.6607-100000@iolanthe.rowland.org>

On 7/12/06, Alan Stern <stern@rowland.harvard.edu> wrote:
> Dave Jones 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.
>
> Since you're not using the UHCI controller on that computer, you could
> simply rmmod uhci-hcd (or modify /etc/modprobe.conf to prevent it from
> being loaded in the first place).  That would stop the constant interrupts
> and the syslog spamming.

For the syslog spamming, you could jus emit the message once when the
state is first noticed, then emit a everything good message when it
clears up. There's no need to log it repeatedly during the problem
period.

Ray

  parent reply	other threads:[~2006-07-12 17:09 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 [this message]
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
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=2c0942db0607121009l1fc00764ye0b98d686700a74c@mail.gmail.com \
    --to=madrabbit@gmail.com \
    --cc=davej@redhat.com \
    --cc=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ray-gmail@madrabbit.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

Powered by JetHome