From: Pete Zaitcev <zaitcev@redhat.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.8-ac2 USB keyboard capslock hang
Date: Mon, 13 Aug 2001 17:36:04 -0400 [thread overview]
Message-ID: <200108132136.f7DLa4l13034@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.997731905.31689.linux-kernel2news@redhat.com>
In-Reply-To: <E15WM1P-0007uJ-00@the-village.bc.nu> <mailman.997731905.31689.linux-kernel2news@redhat.com>
The bug that I fixed was that CapsLock submitted URB while
in a callback (it was a LED control URB).
If you have to hit CapsLock _twice_ to trigger the bug,
then I think it's something different.
-- Pete
> this bug has been around since 2.4.3-ac *at least*, and the linux-usb
> folks are aware of it [but can't get a repro]. i've had repros since
> 2.4.3-ac.
>
> this is the first time afaik that this bug has been reported on a non
> ms-natural-pro keyboard tho.
>
> Alan Cox wrote:
>
> >>On Mon, Aug 13, 2001 at 06:56:48PM +0100, Alan Cox wrote:
> >>
> >>>Roswell is the Red Hat 7.2 beta, so its probably another bug that was fixed
> >>>in the USB and input updates in -ac
> >>>
> >>It hangs on 2.4.8-ac2, so was this bug fix lost perhaps?
> >>
> >
> >It would be useful to know if 2.4.7ac3 say works and if so which one after
> >that it broke at
next prev parent reply other threads:[~2001-08-13 21:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-13 16:15 2.4.8-ac2 USB keyboard capslock hang Peter J. Braam
2001-08-13 17:11 ` Johannes Erdfelt
2001-08-13 17:33 ` Ignacio Vazquez-Abrams
2001-08-13 17:56 ` Alan Cox
2001-08-13 17:55 ` Peter J. Braam
2001-08-13 18:01 ` Alan Cox
2001-08-13 19:40 ` Joseph Cheek
2001-08-13 20:56 ` [Linux-usb-users] " Peter J. Braam
2001-08-13 23:11 ` Joseph Cheek
2001-08-15 0:18 ` Peter J. Braam
2001-08-15 0:33 ` Joseph Cheek
2001-08-15 7:50 ` Brad Hards
[not found] ` <mailman.997731905.31689.linux-kernel2news@redhat.com>
2001-08-13 21:36 ` Pete Zaitcev [this message]
2001-08-13 19:52 ` Ignacio Vazquez-Abrams
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=200108132136.f7DLa4l13034@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--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