archive mirror
 help / color / mirror / Atom feed
Subject: 2.6.0 USB/HID problems.
Date: Sun, 07 Dec 2003 23:04:34 -0700	[thread overview]
Message-ID: <> (raw)

I am posting this here since I dont seem to be able to post to
either of the USB lists.

In working with the code apcupsd, I have found two problems that appeare
in the 2.6.0-testX kernels that did not appear in the 2.4.x series of kernels.

    (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.

    (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?

                 reply	other threads:[~2003-12-08  6:04 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).