[lwlan-user] [non-subscriber] WLAN is busy sleeping in interrupt context

[David Cook]

It DOES makes sense to me that you might want to upgrade
kernel FROM 2.4.18.

But, it does NOT make much sense to me why you chose
2.5.<anything>.  I've always thought that when the second
digit is ODD (like 5), that means that the kernel is
experimental, right?

So, unless you have a specific REASON for choosing 2.5.<x>, I'd
suggest you consider going to 2.4.20 or 2.4.21, which are latest
'non-experimental' kernels.  (I'm just concerned that this
busy-sleeping in interrupt context [or other issues] might
get mixed in with any wireless-lan issues, and we won't know
how to distinguish the problems.)

Please correct me if I'm incorrect about the meaning of
kernel version numbers.

Cheers...

		Dave


-----Original Message-----
From: linux-wlan-user-admin@lists.linux-wlan.com
[mailto:linux-wlan-user-admin@lists.linux-wlan.com]On Behalf Of
tempnet.net -
Sent: July 06, 2003 09:54
To: linux-wlan-user@lists.linux-wlan.com
Cc: matthew@tempnet.net
Subject: [lwlan-user] [non-subscriber] WLAN is busy sleeping in
interrupt context


I am running a 2.5.21 kernel and a MN-510 prism2_usb NIC.

I had multiple problems with it on 2.4.18 so I upgraded the kernel and
finally it configured and compiled easy. But now when I run the wlanctl-ng
lnxreq_autojoin ssid="my id" authtype=opensystem
I get the string like its working untill the very end.

It says:

*** WLAN is busy-sleeping in interrupt context!

three times.

Now I am still able to ifconfig wlan0 up and down but I can never get a
network connection out of it. We're using an airport basestation and it even
reads the signal as being top noch. But I just cant get the thing to hit the
accesspoint.
Cant ping it or anything else. Any ideas?

-Matthew
_______________________________________________
Linux-wlan-user mailing list
Linux-wlan-user@lists.linux-wlan.com
http://lists.linux-wlan.com/mailman/listinfo/linux-wlan-user