linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Soeren Sonnenburg <sonne@debian.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Greg KH <greg@kroah.com>, "Rafael J. Wysocki" <rjw@sisk.pl>,
	linux-input@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Kernel Testers List <kernel-testers@vger.kernel.org>
Subject: Re: [Bug #14626] oops on boot starting udev
Date: Tue, 17 Nov 2009 03:59:03 +0100	[thread overview]
Message-ID: <1258426743.9883.53.camel@no> (raw)
In-Reply-To: <20091117020451.GA27967@core.coreip.homeip.net>

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?).

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

  reply	other threads:[~2009-11-17  2:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <GUZt44bIwCE.A.vLF.pSdALB@chimera>
     [not found] ` <xXQGFmujPl.A.fpF.zSdALB@chimera>
2009-11-17  1:14   ` [Bug #14626] oops on boot starting udev Greg KH
2009-11-17  2:04     ` Dmitry Torokhov
2009-11-17  2:59       ` Soeren Sonnenburg [this message]
2009-11-17  4:01         ` Dmitry Torokhov
     [not found]           ` <20091117040104.GA5792-WlK9ik9hQGAhIp7JRqBPierSzoNAToWh@public.gmane.org>
2009-11-17  4:06             ` Soeren Sonnenburg
2009-11-19  2:59               ` Dmitry Torokhov
2009-11-21  6:21                 ` Soeren Sonnenburg
2009-11-21  8:56                 ` Soeren Sonnenburg
2009-11-21  9:30                   ` Justin P. Mattock
2009-11-21  9:35                   ` [SOLVED] kernel module loading does not work with binutils-gold (was Re: [Bug #14626] oops on boot starting udev) Soeren Sonnenburg
2009-11-21  9:58                     ` Justin P. Mattock
     [not found]                       ` <4B07B9BA.2070607-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-11-21 10:08                         ` Soeren Sonnenburg
2009-11-21 10:29                           ` Justin P. Mattock

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1258426743.9883.53.camel@no \
    --to=sonne@debian.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=greg@kroah.com \
    --cc=kernel-testers@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).