public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: arnaud.quette@mgeups.com
To: reg@dwf.com
Cc: Greg KH <greg@kroah.com>, Paul Stewart <stewart@wetlogic.net>,
	Vojtech Pavlik <vojtech@suse.cz>,
	linux-kernel@vger.kernel.org,
	linux-usb-users@lists.sourceforge.net, opensource@mgeups.com,
	"Charles Lepple" <clepple@ghz.cc>,
	reg@orion.dwf.com
Subject: Réf. : [Linux-usb-users] Re: USB/HID UPS issue (was Re: USB scanner issue)
Date: Wed, 10 Dec 2003 10:54:24 +0100	[thread overview]
Message-ID: <C1256DF8.003624D1.00@gin123.ftgin.com> (raw)




Hi Reg,

> I havent anything to add to your comments, except to make sure you saw
> my comments about USB/HID problems that I have encountered with a UPS.
>
> Since the message was short, I reproduce it here:

Fine as I seem to have missed it.

---

>...
>    (1) When doing a read to get hiddev_event structures, 2.4 only
>    gave the 'real' events from the device that one expected.
>    Under 2.6.0-testx there are several ZERO event structures/sec
>    where the entire structure is ZERO, both hid and value.
>
>    For the current code there may be a 'real' event every few
>    seconds, and 5-10 of these zero events/sec.  I have no
>    idea where they are coming from.
>

I have logged this in bugzilla for some times, but didn't had
time to go deeper (http://bugzilla.kernel.org/show_bug.cgi?id=795)
Eric Penner also added: http://bugzilla.kernel.org/show_bug.cgi?id=1048

>    (2) In one thread the code does a select, followed by a read if
>    data is available.  If one just 'falls thru' to the read with
>    the few lines of code it takes to do the checking, one gets
>    up to 45000 messages/minute (750/sec) reading:
>
>        kernel: drivers/usb/input/hid-core.c: control queue full
>
>    If one puts a 1/10sec sleep between these two commands, the
>    error messages go away.
>
>Anyone know anything about either of these errors?
>Or how to report them to the USB people if you cant post to the USB lists?

About the "control queue full", Vojtech once made a patch  (I should still have
it somewhere. If you want to test it, tell me so...)

Lastly, the best way to report is still to mail to usd-users and usb-devel
lists. Otherwise, the above mentionned Linux' bugzilla is a good way too.

Arnaud



                 reply	other threads:[~2003-12-10  9:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=C1256DF8.003624D1.00@gin123.ftgin.com \
    --to=arnaud.quette@mgeups.com \
    --cc=clepple@ghz.cc \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-users@lists.sourceforge.net \
    --cc=opensource@mgeups.com \
    --cc=reg@dwf.com \
    --cc=reg@orion.dwf.com \
    --cc=stewart@wetlogic.net \
    --cc=vojtech@suse.cz \
    /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