From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753643Ab1A0DS6 (ORCPT ); Wed, 26 Jan 2011 22:18:58 -0500 Received: from ironport2-out.teksavvy.com ([206.248.154.183]:10624 "EHLO ironport2-out.pppoe.ca" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751671Ab1A0DS5 (ORCPT ); Wed, 26 Jan 2011 22:18:57 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApIBALZyQE1Ld/sX/2dsb2JhbAAMhAbNCpBogSODOHQEhRc X-IronPort-AV: E=Sophos;i="4.60,383,1291611600"; d="scan'208";a="89376868" Message-ID: <4D40E41D.2030003@teksavvy.com> Date: Wed, 26 Jan 2011 22:18:53 -0500 From: Mark Lord User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: Dmitry Torokhov CC: Mauro Carvalho Chehab , Linus Torvalds , Linux Kernel , linux-input@vger.kernel.org, linux-media@vger.kernel.org Subject: Re: 2.6.36/2.6.37: broken compatibility with userspace input-utils ? References: <20110125164803.GA19701@core.coreip.homeip.net> <20110125205453.GA19896@core.coreip.homeip.net> <4D3F4804.6070508@redhat.com> <4D3F4D11.9040302@teksavvy.com> <20110125232914.GA20130@core.coreip.homeip.net> <20110126020003.GA23085@core.coreip.homeip.net> <4D403855.4050706@teksavvy.com> <4D40C3D7.90608@teksavvy.com> <4D40C551.4020907@teksavvy.com> <20110127021227.GA29709@core.coreip.homeip.net> In-Reply-To: <20110127021227.GA29709@core.coreip.homeip.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11-01-26 09:12 PM, Dmitry Torokhov wrote: > On Wed, Jan 26, 2011 at 08:07:29PM -0500, Mark Lord wrote: >> 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 > > Does it die when you try to invoke the command by hand? Can you see where? No, it does not seem to segfault when I unload/reload ir-kbd-i2c and then invoke it by hand with the same parameters. Quite possibly the environment is different when udev invokes it, and my strace attempt with udev killed the system, so no info there. It does NOT segfault on the stock 2.6.37 kernel, without the patch. -ml