Re: annoying frequent overcurrent messages.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 7/12/06, Alan Stern <[email protected]> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux