[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4D40C551.4020907@teksavvy.com>
Date: Wed, 26 Jan 2011 20:07:29 -0500
From: Mark Lord <kernel@...savvy.com>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
CC: Mauro Carvalho Chehab <mchehab@...hat.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Linux Kernel <linux-kernel@...r.kernel.org>,
linux-input@...r.kernel.org, linux-media@...r.kernel.org
Subject: Re: 2.6.36/2.6.37: broken compatibility with userspace input-utils
?
On 11-01-26 08:01 PM, Mark Lord wrote:
> On 11-01-26 10:05 AM, Mark Lord wrote:
>> On 11-01-25 09:00 PM, Dmitry Torokhov wrote:
> ..
>>> I wonder if the patch below is all that is needed...
>>
>> Nope. Does not work here:
>>
>> $ lsinput
>> protocol version mismatch (expected 65536, got 65537)
>>
>
> Heh.. I just noticed something *new* in the bootlogs on my system:
>
> kernel: Registered IR keymap rc-rc5-tv
> udevd-event[6438]: run_program: '/usr/bin/ir-keytable' abnormal exit
> kernel: input: i2c IR (Hauppauge) as /devices/virtual/rc/rc0/input7
> kernel: ir-keytable[6439]: segfault at 8 ip 00000000004012d2 sp 00007fff6d43ca60
> error 4 in ir-keytable[400000+7000]
> kernel: rc0: i2c IR (Hauppauge) as /devices/virtual/rc/rc0
> kernel: ir-kbd-i2c: i2c IR (Hauppauge) detected at i2c-0/0-0018/ir0 [ivtv i2c
> driver #0]
>
> That's udev invoking ir-keyboard when the ir-kbd-i2c kernel module is loaded,
> and that is also ir-keyboard (userspace) segfaulting when run.
Note: I tried to capture an strace of ir-keyboard segfaulting during boot
(as above), but doing so kills the system (hangs on boot).
The command from udev was: /usr/bin/ir-keytable -a /etc/rc_maps.cfg -s rc0
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists