[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1258426743.9883.53.camel@no>
Date: Tue, 17 Nov 2009 03:59:03 +0100
From: Soeren Sonnenburg <sonne@...ian.org>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: Greg KH <greg@...ah.com>, "Rafael J\. Wysocki" <rjw@...k.pl>,
linux-input@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Kernel Testers List <kernel-testers@...r.kernel.org>
Subject: Re: [Bug #14626] oops on boot starting udev
On Mon, 2009-11-16 at 18:04 -0800, Dmitry Torokhov wrote:
> On Mon, Nov 16, 2009 at 05:14:55PM -0800, Greg KH wrote:
> > On Mon, Nov 16, 2009 at 11:37:48PM +0100, Rafael J. Wysocki wrote:
> > > This message has been generated automatically as a part of a report
> > > of recent regressions.
> > >
> > > The following bug entry is on the current list of known regressions
> > > from 2.6.31. Please verify if it still should be listed and let me know
> > > (either way).
> > >
> > >
> > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14626
> > > Subject : oops on boot starting udev
> > > Submitter : Soeren Sonnenburg <sonne@...ian.org>
> > > Date : 2009-11-14 10:16 (3 days old)
> > > References : http://marc.info/?l=linux-kernel&m=125819380206800&w=4
> >
> > This looks like an input core problem, as the evdev module was just
> > loaded and died.
> >
> > Any input developers have any ideas?
> >
>
>
> Hmm, evdev does:
>
> dev_set_name(&evdev->dev, "event%d", minor);
>
> Not sure how it can go wrong...
Anything I should/could do to narrow it down a bit (apart from
bisecting?).
Soeren
--
For the one fact about the future of which we can be certain is that it
will be utterly fantastic. -- Arthur C. Clarke, 1962
--
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