From: Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>
To: linux-kernel@vger.kernel.org
Subject: Re: keyboard - was: Re: Linux 2.6.0-test4
Date: Tue, 2 Sep 2003 13:18:03 +0200 [thread overview]
Message-ID: <20030902111756.GL14380@charite.de> (raw)
In-Reply-To: <20030902124717.B1221@pclin040.win.tue.nl>
* Andries Brouwer <aebr@win.tue.nl>:
> On Tue, Sep 02, 2003 at 10:07:33AM +0200, Ralf Hildebrandt wrote:
>
> > I got some more events, and today I even was able to reproduc the
> > "CTRL-is-stuck" problem.
> >
> > I was able to get the key unstuck by switching back and forth between
> > dirrerent FB consoles and by pushing and releaseing CTRL in them...
>
> Yesterday's data sufficed, and I suppose the patch I gave solves
> this problem. Now that you send this, we can verify that each time
> there is a problem we have had a double release just before, and
> that release was an e0 xx combination.
Excellent. I rebuild my kernel including your patch; I shall reboot
soon :)
> This bug is understood.
I'll get back to you once I verify that the problem doesn't occur
anymore.
--
Ralf Hildebrandt (Im Auftrag des Referat V a) Ralf.Hildebrandt@charite.de
Charite Campus Mitte Tel. +49 (0)30-450 570-155
Referat V a - Kommunikationsnetze - Fax. +49 (0)30-450 570-916
AIM: ralfpostfix
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
* Andries Brouwer <aebr@win.tue.nl>:
> On Tue, Sep 02, 2003 at 10:07:33AM +0200, Ralf Hildebrandt wrote:
>
> > I got some more events, and today I even was able to reproduc the
> > "CTRL-is-stuck" problem.
> >
> > I was able to get the key unstuck by switching back and forth between
> > dirrerent FB consoles and by pushing and releaseing CTRL in them...
>
> Yesterday's data sufficed, and I suppose the patch I gave solves
> this problem. Now that you send this, we can verify that each time
> there is a problem we have had a double release just before, and
> that release was an e0 xx combination.
Excellent. I rebuild my kernel including your patch; I shall reboot
soon :)
> This bug is understood.
I'll get back to you once I verify that the problem doesn't occur
anymore.
--
Ralf Hildebrandt (Im Auftrag des Referat V a) Ralf.Hildebrandt@charite.de
Charite Campus Mitte Tel. +49 (0)30-450 570-155
Referat V a - Kommunikationsnetze - Fax. +49 (0)30-450 570-916
AIM: ralfpostfix
next prev parent reply other threads:[~2003-09-02 11:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-31 16:22 Re:Re: Linux 2.6.0-test4 Chris Heath
2003-09-01 16:01 ` Ralf Hildebrandt
2003-09-02 0:16 ` [PATCH] keyboard - was: " Andries Brouwer
2003-09-02 5:39 ` Ralf Hildebrandt
2003-09-02 8:07 ` Ralf Hildebrandt
2003-09-02 10:47 ` keyboard - was: " Andries Brouwer
2003-09-02 11:18 ` Ralf Hildebrandt [this message]
2003-09-02 12:32 ` Ralf Hildebrandt
2003-09-02 21:41 ` Andries Brouwer
2003-09-03 7:45 ` Ralf Hildebrandt
2003-09-03 13:25 ` Ralf Hildebrandt
-- strict thread matches above, loose matches on Subject: below --
2003-09-04 4:09 Chris Heath
2003-09-04 20:48 ` Jamie Lokier
2003-09-04 22:34 ` Andries Brouwer
2003-09-04 23:00 ` Jamie Lokier
2003-09-05 0:19 ` Andries Brouwer
2003-09-05 3:41 ` Chris Heath
2003-09-05 10:08 ` Andries Brouwer
2003-09-05 13:46 Norman Diamond
2003-09-05 14:57 John Bradford
2003-09-05 23:45 ` Andries Brouwer
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=20030902111756.GL14380@charite.de \
--to=ralf.hildebrandt@charite.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.