Scheduling whilst Atomic on ifconfig wlan0 up with rt2500usb

Live forum:


16-01-2008 00:00:36

Hi all,

When I bring my rt2500usb card up on rt2x00 git revision 940ca25e, I get the following

[code1ys9f10t]phy0 -> rt2500usb_init_bbp: Debug - Start initialization from EEPROM...
phy0 -> rt2500usb_init_bbp: Debug - BBP: 0x11, value: 0x2f.
phy0 -> rt2500usb_init_bbp: Debug - BBP: 0x15, value: 0x18.
phy0 -> rt2500usb_init_bbp: Debug - BBP: 0x16, value: 0x18.
phy0 -> rt2500usb_init_bbp: Debug - BBP: 0x3e, value: 0x00.
phy0 -> rt2500usb_init_bbp: Debug - ...End initialization from EEPROM.
BUG: scheduling while atomic: ifconfig/13497/0x00000002
Pid: 13497, comm: ifconfig Not tainted 2.6.24-rc5-g940ca25e #11
[<c0337cc6>] schedule+0x246/0x300
[<c03381f3>] schedule_timeout+0x43/0xb0
[<c0112dd2>] finish_task_switch+0x22/0x70
[<c011ed72>] lock_timer_base+0x22/0x60
[<c011f1a0>] process_timeout+0x0/0x10
[<c03381ee>] schedule_timeout+0x3e/0xb0
[<c0337fad>] wait_for_common+0x7d/0x150
[<c01134c0>] default_wake_function+0x0/0x10
[<c722aaa0>] usb_start_wait_urb+0x80/0xa0 [usbcore]
[<c722acb1>] usb_control_msg+0xc1/0xe0 [usbcore]
[<c735e42e>] rt2x00usb_vendor_request+0xae/0x130 [rt2x00usb]
[<c735e5d9>] rt2x00usb_vendor_req_buff_lock+0x129/0x140 [rt2x00usb]
[<c735e64f>] rt2x00usb_vendor_request_buff+0x5f/0x80 [rt2x00usb]
[<c7338c4d>] rt2500usb_config_bssid+0x2d/0x40 [rt2500usb]
[<c73b2587>] rt2x00lib_config_bssid+0x37/0x40 [rt2x00lib]
[<c73b2079>] rt2x00mac_config_interface+0x49/0xa0 [rt2x00lib]
[<c72ca1cf>] __ieee80211_if_config+0x7f/0xf0 [mac80211]
[<c72cbde0>] ieee80211_open+0x3e0/0x470 [mac80211]
[<c02a857c>] dev_open+0x4c/0x80
[<c02a7695>] dev_change_flags+0x75/0x180
[<c02a62d3>] __dev_get_by_name+0x73/0x90
[<c02e611e>] devinet_ioctl+0x51e/0x670
[<c02a93ed>] dev_ioctl+0x2bd/0x520
[<c029b1c4>] sock_ioctl+0xb4/0x1f0
[<c029b110>] sock_ioctl+0x0/0x1f0
[<c016b71f>] do_ioctl+0x1f/0x70
[<c016b94b>] vfs_ioctl+0x1db/0x2a0
[<c016ba43>] sys_ioctl+0x33/0x50
[<c0104262>] syscall_call+0x7/0xb
ADDRCONF(NETDEV_UP): wlan0: link is not ready[/code1ys9f10t]

My distro is Debian Testing as of this morning.

Is this a known issue, and is there a fix forthcoming?

I am going to try this with git 75ee748 tonight to see if this is still happening.


Julian Calaby


17-02-2008 14:32:40

This should be fixed in latest git version.