All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Hugh Dickins <hugh@veritas.com>, kay.sievers@vrfy.org
Cc: Miles Lane <miles.lane@gmail.com>, Andrew Morton <akpm@osdl.org>,
	LKML <linux-kernel@vger.kernel.org>,
	yi.zhu@intel.com
Subject: Re: 2.6.20-rc2-mm1 -- INFO: possible recursive locking detected
Date: Thu, 4 Jan 2007 15:57:58 -0800	[thread overview]
Message-ID: <20070104235758.GA32132@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0701042339080.4441@blonde.wat.veritas.com>

On Thu, Jan 04, 2007 at 11:50:02PM +0000, Hugh Dickins wrote:
> On Thu, 4 Jan 2007, Greg KH wrote:
> > On Sat, Dec 30, 2006 at 02:47:20AM -0800, Miles Lane wrote:
> > > Sorry Andrew, I am not sure which maintainer to contact about this.  I
> > > CCed gregkh for sysfs and Yi for ipw2200.  Hopefully this is helpful.
> > > BTW, I also found that none of my network drivers were recognized by
> > > hal (lshal did not show their "net" entries) unless I set
> > > CONFIG_SYSFS_DEPRECATED=y.  I am running Ubuntu development (Feisty
> > > Fawn), so it seems like I ought to be running pretty current hal
> > > utilities:   hal-device-manager       0.5.8.1-4ubuntu1.  After
> > > reenabling CONFIG_SYSFS_DEPRECATED, I am able to use my IPW2200
> > > driver, in spite of this recursive locking message, so this INFO
> > > message may not indicate a problem.
> > 
> > Does this show up on the 2.6.20-rc3 kernel too?
> 
> Yes.  Well, I can't speak for Miles on Ubuntu, but I have ipw2200
> on openSUSE 10.2 (using ifplugd if that matters), and have to build
> my 2.6.20-rc3 with CONFIG_SYSFS_DEPRECATED=y in order to get an IP
> address (no idea whether it's a hald issue in my case).  Likewise
> needed CONFIG_SYSFS_DEPRECATED=y with 2.6.19-rc-mm on SuSE 10.1.

I was referring to the locking traceback :)

But anyway, Kay, I thought that 10.2 would work with
CONFIG_SYSFS_DEPRECATED=y?

And yes, 10.1 I know will not work that way, but as it's not supported
anymore, that's not a big deal :)

> --- 2.6.20-rc3/init/Kconfig	2007-01-01 10:30:46.000000000 +0000
> +++ linux/init/Kconfig	2007-01-04 23:36:40.000000000 +0000
> @@ -266,7 +266,7 @@ config SYSFS_DEPRECATED
>  	  that belong to a class, back into the /sys/class heirachy, in
>  	  order to support older versions of udev.
>  
> -	  If you are using a distro that was released in 2006 or later,
> +	  If you are using a distro that was released in 2008 or later,
>  	  it should be safe to say N here.

Well, I'm using a distro released in 2006 that works just fine (Gentoo
unstable, Debian unstable should also work.  I think even Gentoo stable
works too, but haven't tried that out...)

thanks,

greg k-h

  reply	other threads:[~2007-01-04 23:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-30 10:47 2.6.20-rc2-mm1 -- INFO: possible recursive locking detected Miles Lane
2007-01-04 21:47 ` Greg KH
2007-01-04 23:50   ` Hugh Dickins
2007-01-04 23:57     ` Greg KH [this message]
2007-01-05 11:34       ` Kay Sievers
2007-01-05 12:43         ` Hugh Dickins

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=20070104235758.GA32132@suse.de \
    --to=gregkh@suse.de \
    --cc=akpm@osdl.org \
    --cc=hugh@veritas.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miles.lane@gmail.com \
    --cc=yi.zhu@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.