Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964930AbVKHEoX (ORCPT ); Mon, 7 Nov 2005 23:44:23 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964933AbVKHEoX (ORCPT ); Mon, 7 Nov 2005 23:44:23 -0500 Received: from mail.kroah.org ([69.55.234.183]:38814 "EHLO perch.kroah.org") by vger.kernel.org with ESMTP id S964930AbVKHEoW (ORCPT ); Mon, 7 Nov 2005 23:44:22 -0500 Date: Mon, 7 Nov 2005 20:43:49 -0800 From: Greg KH To: "Theodore Ts'o" , linux-kernel@vger.kernel.org Subject: Re: udev on 2.6.14 fails to create /dev/input/event2 on T40 Thinkpad Message-ID: <20051108044348.GB5516@kroah.com> References: <20051106203421.GB2527@kroah.com> <20051107053648.GA7521@thunk.org> <20051107155243.GA14658@kroah.com> <20051107181706.GB8374@thunk.org> <20051107182434.GC18861@kroah.com> <20051108033019.GA6129@thunk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051108033019.GA6129@thunk.org> User-Agent: Mutt/1.5.11 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1672 Lines: 40 On Mon, Nov 07, 2005 at 10:30:19PM -0500, Theodore Ts'o wrote: > On Mon, Nov 07, 2005 at 10:24:34AM -0800, Greg KH wrote: > > > from Debian with a post 2.6.14 kernel, and it wasn't working for me. > > > > I see that 073 is in unstable, which fixed a lot of problems with 071, > > 072 and 073 due to Debian configuration issues. I suggest you try that. > > I've just tried udev 073 from Debian unstable, with a freshly pulled > kernel 2.6.14 from earlier in the evening on 11/7. Same failure: > > /dev/input only has /dev/input/event3, and is missing the event0, event1, > and event2 files that is present if I boot 2.6.14. > > So is this a Debian bug, a kernel bug, or a udev bug? Debian bug, as this version of udev, and kernel, running on a different distro, works just fine for me here :) > What is going on? I don't know enough about recent changes to udev > and/or the events sent to udev to start debugging this, but this is > something that works in 2.6.14 and fails post-2.6.14.... The input subsystem moved to handle nested class devices, so udev had to change to handle this properly. I bet however Debian does the initial population of the /dev tree is messed up somehow, as that is what it looks like is happening (event3 I bet is from a USB device that is added after init starts?) > So this is what I believe Andrew would call "a regression". :-) I call it a "Debian mess"... Good luck, greg k-h - 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/