From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Dave Jones <davej@redhat.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
ray-gmail@madrabbit.org,
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 19:26:25 +0100 [thread overview]
Message-ID: <1152728785.22943.88.camel@localhost.localdomain> (raw)
In-Reply-To: <20060712175124.GF14453@redhat.com>
Ar Mer, 2006-07-12 am 13:51 -0400, ysgrifennodd Dave Jones:
> Defective it may be, I'm not arguing that. But spewing hundreds of
> these an hour isn't going to make the user fix the problem (if they even can)
> any faster.
>
> *grumbles and goes to edit modprobe.conf*
dmidecode
pci svid/subdevice
submit patch
I agree entirely with the other Alan here, overcurrent is a serious item
with a potential severity not that far below "your cpu fan seems to have
stopped going round [Ok]"
If its a dodgy board it should be possible to id and blacklist its UHCI
controller
next prev parent reply other threads:[~2006-07-12 18: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 ` 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 [this message]
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=1152728785.22943.88.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--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