Re: wl1271: ERROR watchdog interrupt received! starting recovery.

["Martin Hundebøll" <m.hundeboll@gmail.com>]

On 2012-01-20 10:52, Martin Hundebøll wrote:
> I'm running an ad-hoc network with two pandaboards using the following commands to setup the network:
>
> root@panda0 # ip link set dev wlan0 address 7e:78:47:8c:26:52
> root@panda0 # iw dev wlan0 set type ibss
> root@panda0 # ip link set dev wlan0 up
> root@panda0 # iw dev wlan0 ibss join panda-mesh 2412 02:72:CF:28:19:1A
> root@panda0 # iw phy phy0 set rts 100
> root@panda0 # ip addr add 10.10.10.52/24 dev wlan0
>
> and
>
> root@panda1 # ip link set dev wlan0 address 7e:78:47:8c:26:53
> root@panda1 # iw dev wlan0 set type ibss
> root@panda1 # ip link set dev wlan0 up
> root@panda1 # iw dev wlan0 ibss join panda-mesh 2412 02:72:CF:28:19:1A
> root@panda1 # iw phy phy0 set rts 100
> root@panda1 # ip addr add 10.10.10.53/24 dev wlan0
>
> After this, the nodes list each other in a station dump. I then run ping:
>
> root@panda0 # ping 10.10.10.53
>
> but only two requests are transmitted before the devices restart as seen in the attached dmesg logs. The tcpdump from panda1 is attached in tcpdump.txt. I have attached the kernel config and here is some additional info:
>
I have investigated the issue further and it seems to be related to the rts-setting in the commands listed above. Since my last mail I have update to kernel v3.2.1 and now the watchdog interrupts continuously if I configure the RTS threshold to 62 bytes or less. Changing the threshold to 63 bytes or more stops the watchdog interrupt from occuring.

Kind regards,
Martin Hundebøll