Re: [Bug #14626] oops on boot starting udev

[Soeren Sonnenburg <sonne@debian.org>]

On Wed, 2009-11-18 at 18:59 -0800, Dmitry Torokhov wrote:
> On Tue, Nov 17, 2009 at 05:06:47AM +0100, Soeren Sonnenburg wrote:
> > On Mon, 2009-11-16 at 20:01 -0800, Dmitry Torokhov wrote:
> > > On Tue, Nov 17, 2009 at 03:59:03AM +0100, Soeren Sonnenburg wrote:
> > > > 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@debian.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?).
> > > > 
> > > 
> > > Umm, I looked through the changes between -rc6 and 7 but nothing jumped
> > > out at me... You don't happen to have any local changes in your tree?
> > 
> > Well only the mouse button #1 emulation - though I don't see what could
> > go wrong there.
> > 
> 
> I have been looking through the changes and I really don't see anything
> suspicious. I am also not hittign this oops on any of my boxes. Any
> chance you could bisect?

I cannot promise whether I find the time to do this :/ One thing I
noticed is that applesmc seems to freak out every now and then on boot
(after the oopses). Only on this macbook pro.

Soeren

PS: I don't have this oops on a desktop machine either.
-- 
For the one fact about the future of which we can be certain is that it
will be utterly fantastic. -- Arthur C. Clarke, 1962