From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Guillaume Chazarain <guichaz@gmail.com>
Cc: ajax@redhat.com, LKML <linux-kernel@vger.kernel.org>,
linux-input@vger.kernel.org
Subject: Re: evdev regression on macbook with 2.6.33-rc5
Date: Sun, 24 Jan 2010 01:30:55 -0800 [thread overview]
Message-ID: <20100124093055.GA17607@core.coreip.homeip.net> (raw)
In-Reply-To: <3d8471ca1001231053k512011dcnfab50052ce3667fa@mail.gmail.com>
Hi Guillaume,
On Sat, Jan 23, 2010 at 07:53:58PM +0100, Guillaume Chazarain wrote:
> Hi,
>
> Since 2.6.33-rc5, the keyboard on my MacBookPro 3,1 stopped working
> when using X.
> It works fine in console mode, but in X, pressing keys does not have
> any effect until I hit the touchpad or an USB mouse and then all the
> keystrokes are delivered.
> I'm using the nvidia proprietary drivers on Ubuntu 9.10 x86_64
> (config.gz and dmesg.gz attached).
>
> A git bisection found this commit as the culprit and reverting it
> indeed fixes the problem:
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=30a589fde0162aa4dac7c69803aeee8fbe8d1b82
>
> commit 30a589fde0162aa4dac7c69803aeee8fbe8d1b82
> Author: Adam Jackson <ajax@redhat.com>
> Date: Tue Jan 5 17:56:04 2010 -0800
>
> Input: evdev - be less aggressive about sending SIGIO notifies
>
> Thanks.
>
DOes the same behavior happens when you try using 'evtest' utility while
in console? Also, do you have external USB keyboard by any chance and if
you do does it exibit the same problem?
Thanks.
--
Dmitry
next prev parent reply other threads:[~2010-01-24 9:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-23 18:53 evdev regression on macbook with 2.6.33-rc5 Guillaume Chazarain
2010-01-24 9:30 ` Dmitry Torokhov [this message]
2010-01-25 22:49 ` Guillaume Chazarain
2010-01-25 23:25 ` Dmitry Torokhov
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=20100124093055.GA17607@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=ajax@redhat.com \
--cc=guichaz@gmail.com \
--cc=linux-input@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).