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.
[ INFO: possible recursive locking detected ]
2.6.20-rc2-mm1 #21
---------------------------------------------
modprobe/1779 is trying to acquire lock:
(&sysfs_inode_imutex_key){--..}, at: [<c02db236>] mutex_lock+0x1c/0x1f
but task is already holding lock:
(&sysfs_inode_imutex_key){--..}, at: [<c02db236>] mutex_lock+0x1c/0x1f
other info that might help us debug this:
3 locks held by modprobe/1779:
#0: (rtnl_mutex){--..}, at: [<c02db236>] mutex_lock+0x1c/0x1f
#1: (&priv->mutex){--..}, at: [<c02db236>] mutex_lock+0x1c/0x1f
#2: (&sysfs_inode_imutex_key){--..}, at: [<c02db236>] mutex_lock+0x1c/0x1f
stack backtrace:
[<c0104eab>] show_trace_log_lvl+0x1a/0x2f
[<c010558b>] show_trace+0x12/0x14
[<c010563d>] dump_stack+0x16/0x18
[<c0132147>] __lock_acquire+0x12e/0xb75
[<c0132bf6>] lock_acquire+0x68/0x82
[<c02db094>] __mutex_lock_slowpath+0xdc/0x262
[<c02db236>] mutex_lock+0x1c/0x1f
[<c019bca3>] sysfs_drop_dentry+0xb7/0x12b
[<c019d331>] sysfs_remove_dir+0x6f/0x10b
[<c01dcf9d>] kobject_del+0xb/0x15
[<c0243701>] device_del+0x1b0/0x1c4
[<c0243720>] device_unregister+0xb/0x15
[<f90dc384>] _request_firmware+0x2e0/0x300 [firmware_class]
[<f90dc43c>] request_firmware+0x12/0x14 [firmware_class]
[<f9212d05>] ipw_load+0x5b/0x1690 [ipw2200]
[<f92143ca>] ipw_up+0x90/0x7d7 [ipw2200]
[<f921b6e1>] ipw_net_init+0x1f/0x3e [ipw2200]
[<c028b612>] register_netdevice+0xa9/0x2e5
[<c028c9b3>] register_netdev+0x40/0x4d
[<f921da23>] ipw_pci_probe+0x78b/0x833 [ipw2200]
[<c01f65c9>] pci_device_probe+0x39/0x5b
[<c0245505>] driver_probe_device+0xaa/0x123
[<c0245675>] __driver_attach+0x6a/0xa1
[<c0244b0a>] bus_for_each_dev+0x36/0x5b
[<c024538c>] driver_attach+0x19/0x1b
[<c0244dfa>] bus_add_driver+0x6a/0x170
[<c0245954>] driver_register+0x79/0x7e
[<c01f671e>] __pci_register_driver+0x53/0x80
[<f90d502e>] ipw_init+0x2e/0x73 [ipw2200]
[<c0138cc9>] sys_init_module+0x131a/0x1469
[<c0103ed6>] sysenter_past_esp+0x5f/0x99
PM: Adding info for No Bus:eth1
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?
thanks,
greg k-h
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.
Hugh
--- 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.
config RELAY
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
On Thu, 2007-01-04 at 15:57 -0800, Greg KH wrote:
> 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?
Yes, HAL, udev, NetworkManager, ... from 10.2 works fine here, without
that option set.
Kay
On Fri, 5 Jan 2007, Kay Sievers wrote:
> >
> > But anyway, Kay, I thought that 10.2 would work with
> > CONFIG_SYSFS_DEPRECATED=y?
>
> Yes, HAL, udev, NetworkManager, ... from 10.2 works fine here, without
> that option set.
I'm using ifplugd rather than NetworkManager: would that affect it?
Hugh