From: Greg KH <greg@kroah.com>
To: "Sebastian Dröge" <sebastian.droege@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.5.5-dj2] USB keyboard strangeness and ALSA error
Date: Mon, 4 Mar 2002 14:35:31 -0800 [thread overview]
Message-ID: <20020304223530.GA5280@kroah.com> (raw)
In-Reply-To: <20020304211949.26f188ac.sebastian.droege@gmx.de>
In-Reply-To: <20020304211949.26f188ac.sebastian.droege@gmx.de>
On Mon, Mar 04, 2002 at 09:19:49PM +0100, Sebastian Dröge wrote:
> Hi,
> I've following problems with 2.5.5-dj2:
> If I try to enable numlock I get this message: hid-core.c: control queue full
> and the numlock LED doesn't shine but numlock is enabled
> This is on a USB keyboard (Cherry xyz... the one with included USB hub)
> While booting I get this message: hid-core.c: ctrl urb status -32 received
Can you please try 2.5.6-pre2 and let us know if you still have the USB
problem with that kernel?
thanks,
greg k-h
next prev parent reply other threads:[~2002-03-04 22:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-04 20:19 [2.5.5-dj2] USB keyboard strangeness and ALSA error Sebastian Dröge
2002-03-04 22:35 ` Greg KH [this message]
2002-03-05 0:16 ` Dave Jones
2002-03-06 18:32 ` Sebastian Droege
2002-03-06 19:26 ` Sebastian Droege
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=20020304223530.GA5280@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sebastian.droege@gmx.de \
/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