Send users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://rt2x00.serialmonkey.com/mailman/listinfo/users_rt2x00.serialmonkey.com
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of users digest..."
Today's Topics:
1. Re: rt2800 usb crash with hostapd (Teika Kazura)
2. Re: rt2800 usb crash with hostapd (Olivier Gandit)
3. Re: rt2800 usb crash with hostapd (Gertjan van Wingerde)
----------------------------------------------------------------------
Message: 1
Date: Wed, 19 Oct 2011 16:54:17 +0900 (JST)
From: Teika Kazura <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: Re: [rt2x00-users] rt2800 usb crash with hostapd
Message-ID: <[email protected]>
Content-Type: Text/Plain; charset=us-ascii
Hi, Olivier.
(I'm not a dev.) In general, you have to clarify your device,
probably with lsusb when you ask a device question.
Since this area is rapidly moving, you have to try the latest driver.
(Developers are not idle. =) Install "compat-wireless" (if your distro
doesn't provide it, search for that word.) It's drivers included in
the kernel, but developers distribute it independently so that you
don't have to use the latest kernel. Try 3.0.x, and if it's
problematic, ask again.
Regards,
Teika (Teika kazura)
------------------------------
Message: 2
Date: Wed, 19 Oct 2011 10:44:48 +0200
From: Olivier Gandit <[email protected]>
To: [email protected]
Subject: Re: [rt2x00-users] rt2800 usb crash with hostapd
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi Teika,
thank you for your answer.
2011/10/19 Teika Kazura <[email protected]>:
> Hi, Olivier.
>
> (I'm not a dev.) In general, you have to clarify your device,
> probably with lsusb when you ask a device question.
Bus 002 Device 010: ID 148f:3070 Ralink Technology, Corp.
RT2870/RT3070 Wireless Adapter
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x148f Ralink Technology, Corp.
idProduct 0x3070 RT2870/RT3070 Wireless Adapter
bcdDevice 1.01
iManufacturer 1 Ralink
iProduct 2 802.11 n WLAN
iSerial 3 1.0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 67
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 450mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 7
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 5 1.0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x05 EP 5 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x06 EP 6 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)
>
> Since this area is rapidly moving, you have to try the latest driver.
> (Developers are not idle. =) Install "compat-wireless" (if your distro
> doesn't provide it, search for that word.) It's drivers included in
> the kernel, but developers distribute it independently so that you
> don't have to use the latest kernel. Try 3.0.x, and if it's
> problematic, ask again.
I've tested it with compat-wireless 3.0.2, same result.
Since it's a custom ARM platform with kernel v 2.6.35.5, I've had to
build the drivers from the source code.
I have noticed the issue is non-blocking, clients can connect with no
problem. Still I can't explain this issue.
>
> Regards,
> Teika (Teika kazura)
Best regards,
Olivier Gandit
>
>
------------------------------
Message: 3
Date: Wed, 19 Oct 2011 11:43:55 +0200
From: Gertjan van Wingerde <[email protected]>
To: Olivier Gandit <[email protected]>
Cc: [email protected]
Subject: Re: [rt2x00-users] rt2800 usb crash with hostapd
Message-ID:
<cal1gcdmfg-pb_vmtrpcd40vucv_6cgtb9-dfwmrmf92ygfz...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Hi Olivier,
On Wed, Oct 12, 2011 at 6:07 PM, Olivier Gandit
<[email protected]> wrote:
> Hi rt2x00 users,
>
> I have built the stable release of the rt2x00 drivers for use with
> hostapd on an ARM system with kernel version 2.6.35.5 and a rt2800 usb
> chipset.
>
> Everything starts fine but when a client tries to connect to the
> access point, it fails with the following message:
>
> BUG: scheduling while atomic: hostapd/1089/0x00000002
> Modules linked in: rt2800usb rt2800lib rt2x00usb rt2x00lib mac80211
> cfg80211 kfifo(P) compat lib80211_crypt_wep lib80211_crypt_tkip
> lib80211_crypt_ccmp ppp_async ppp_generic slhc
> [<c002872c>] (unwind_backtrace+0x0/0xf4) from [<c02a95b0>]
> (schedule+0x274/0x34c)
> [<c02a95b0>] (schedule+0x274/0x34c) from [<c02a9dc8>]
> (schedule_timeout+0x13c/0x1d8)
> [<c02a9dc8>] (schedule_timeout+0x13c/0x1d8) from [<c02a9af4>]
> (wait_for_common+0xe8/0x1c4)
> [<c02a9af4>] (wait_for_common+0xe8/0x1c4) from [<c01d6240>]
> (usb_start_wait_urb+0x9c/0xc4)
> [<c01d6240>] (usb_start_wait_urb+0x9c/0xc4) from [<c01d6450>]
> (usb_control_msg+0xd4/0xf8)
> [<c01d6450>] (usb_control_msg+0xd4/0xf8) from [<bf138de0>]
> (rt2x00usb_vendor_request+0xa8/0x130 [rt2x00usb])
> [<bf138de0>] (rt2x00usb_vendor_request+0xa8/0x130 [rt2x00usb]) from
> [<bf138f08>] (rt2x00usb_vendor_req_buff_lock+0x68/0x114 [rt2x00usb])
> [<bf138f08>] (rt2x00usb_vendor_req_buff_lock+0x68/0x114 [rt2x00usb])
> from [<bf13911c>] (rt2x00usb_vendor_request_buff+0x68/0xbc
> [rt2x00usb])
> [<bf13911c>] (rt2x00usb_vendor_request_buff+0x68/0xbc [rt2x00usb])
> from [<bf151534>] (rt2x00usb_register_multiread+0x44/0x4c [rt2800usb])
> [<bf151534>] (rt2x00usb_register_multiread+0x44/0x4c [rt2800usb]) from
> [<bf141148>] (rt2800_get_tkip_seq+0x34/0x4c [rt2800lib])
> [<bf141148>] (rt2800_get_tkip_seq+0x34/0x4c [rt2800lib]) from
> [<bf0f5c74>] (ieee80211_get_key+0x198/0x1e8 [mac80211])
> [<bf0f5c74>] (ieee80211_get_key+0x198/0x1e8 [mac80211]) from
> [<bf0bb79c>] (nl80211_get_key+0x284/0x328 [cfg80211])
> [<bf0bb79c>] (nl80211_get_key+0x284/0x328 [cfg80211]) from
> [<bf0a37ec>] (nl_doit_wrapper+0x130/0x158 [compat])
> [<bf0a37ec>] (nl_doit_wrapper+0x130/0x158 [compat]) from [<c023754c>]
> (genl_rcv_msg+0x1e8/0x210)
> [<c023754c>] (genl_rcv_msg+0x1e8/0x210) from [<c0235bb8>]
> (netlink_rcv_skb+0xbc/0xd8)
> [<c0235bb8>] (netlink_rcv_skb+0xbc/0xd8) from [<c0237358>]
> (genl_rcv+0x18/0x24)
> [<c0237358>] (genl_rcv+0x18/0x24) from [<c023579c>]
> (netlink_unicast+0x2d0/0x32c)
> [<c023579c>] (netlink_unicast+0x2d0/0x32c) from [<c02360dc>]
> (netlink_sendmsg+0x190/0x270)
> [<c02360dc>] (netlink_sendmsg+0x190/0x270) from [<c021073c>]
> (sock_sendmsg+0x8c/0xb0)
> [<c021073c>] (sock_sendmsg+0x8c/0xb0) from [<c0210c8c>]
> (sys_sendmsg+0x130/0x254)
> [<c0210c8c>] (sys_sendmsg+0x130/0x254) from [<c0022ee0>]
> (ret_fast_syscall+0x0/0x2c)
>
> Does anyone has already seen this?
> Do you know any solution?
>
Am I right in my understanding that you are trying to use TKIP keys?
Can you check what happens if you use CCMP or AES keys?
Regardless it would still be an issue that needs to be fixed, but it
would allow us to get closer to the issue,
and would allow you run without these warnings being generated.
---
Gertjan
------------------------------
_______________________________________________
users mailing list
[email protected]
http://rt2x00.serialmonkey.com/mailman/listinfo/users_rt2x00.serialmonkey.com
End of users Digest, Vol 32, Issue 9
************************************
