From: Adam Kropelin <akropel1@rochester.rr.com>
To: David Ford <david+hb@blue-labs.org>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: APCUPSD and HID spam
Date: Wed, 31 Dec 2003 09:14:06 -0500 [thread overview]
Message-ID: <20031231091406.A22231@mail.kroptech.com> (raw)
In-Reply-To: <3FF257A0.8070906@blue-labs.org>; from david+hb@blue-labs.org on Tue, Dec 30, 2003 at 11:59:12PM -0500
On Tue, Dec 30, 2003 at 11:59:12PM -0500, David Ford wrote:
> after starting apcupsd, my system is deluged with over three thousand of
> these messages per second; the control queue full messages. doesn't
> stop until apcupsd is stopped. i can't say if this is new or longtime,
> i just hooked it up after several months.
<snip>
> Dec 30 23:42:09 Huntington-Beach drivers/usb/input/hid-core.c: control
> queue full
Known bug. Upgrade apcupsd to 3.10.8 or the kernel to 2.6.1-rc1.
FYI, in the future you should direct inquiries regarding apcupsd to the
apcupsd-users list (apcupsd-users@lists.sourceforge.net) and search its
archive where bugs such as this tend to be well known.
--Adam
next prev parent reply other threads:[~2003-12-31 14:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-31 4:59 APCUPSD and HID spam David Ford
2003-12-31 14:14 ` Adam Kropelin [this message]
2003-12-31 14:41 ` David Ford
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=20031231091406.A22231@mail.kroptech.com \
--to=akropel1@rochester.rr.com \
--cc=david+hb@blue-labs.org \
--cc=linux-kernel@vger.kernel.org \
/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