LKML Archive on
help / color / mirror / Atom feed
From: Greg KH <>
To: Miles Lane <>
Cc: Andrew Morton <>,
	LKML <>,
Subject: Re: 2.6.20-rc2-mm1 -- INFO: possible recursive locking detected
Date: Thu, 4 Jan 2007 13:47:47 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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


greg k-h

  reply	other threads:[~2007-01-04 22:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-30 10:47 Miles Lane
2007-01-04 21:47 ` Greg KH [this message]
2007-01-04 23:50   ` Hugh Dickins
2007-01-04 23:57     ` Greg KH
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:

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

  git send-email \ \ \ \ \ \ \
    --subject='Re: 2.6.20-rc2-mm1 -- INFO: possible recursive locking detected' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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