From: Sebastian Droege <sebastian.droege@gmx.de>
To: Dave Jones <davej@suse.de>,
linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>
Cc: vojtech@suse.cz
Subject: Re: [2.5.5-dj2] USB keyboard strangeness and ALSA error
Date: Wed, 6 Mar 2002 19:32:18 +0100 [thread overview]
Message-ID: <20020306193218.4bec28ca.sebastian.droege@gmx.de> (raw)
In-Reply-To: <20020305011604.G23524@suse.de>
In-Reply-To: <20020304211949.26f188ac.sebastian.droege@gmx.de> <20020304223530.GA5280@kroah.com> <20020305011604.G23524@suse.de>
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
On Tue, 5 Mar 2002 01:16:04 +0100
Dave Jones <davej@suse.de> wrote:
> On Mon, Mar 04, 2002 at 02:35:31PM -0800, Greg KH wrote:
> > > 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?
>
> My money is on it being ok. -dj has vojtech's various new input layer
> trickery, which I'm suspecting is the real cause of the problem.
Yes right... 2.5.6-pre2 doesn't compile properly but 2.5.5 doesn't have this problem
If it's really important to test it with 2.5.6-pre2 I'll try it again this evening or tomorrow
Bye
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2002-03-06 18:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-04 20:19 Sebastian Dröge
2002-03-04 22:35 ` Greg KH
2002-03-05 0:16 ` Dave Jones
2002-03-06 19:26 ` Sebastian Droege
2002-03-06 18:32 ` Sebastian Droege [this message]
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=20020306193218.4bec28ca.sebastian.droege@gmx.de \
--to=sebastian.droege@gmx.de \
--cc=davej@suse.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®