From: Harshal Vora <harshal@amideeptech.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Adhoc mode and chip reset issue with tp link wn721n/ath9k_htc drivers
Date: Mon, 31 Mar 2014 11:11:38 +0530 [thread overview]
Message-ID: <53390012.2050307@amideeptech.com> (raw)
In-Reply-To: <5337C85D.2060002@rempel-privat.de>
Hi Oleksij,
Is there any constraint on the kernel version with the new firmware, as
in a minimum kernel version for atheros drivers that are compatible with
the latest firmware?
Thanks,
Regards,
On 03/30/2014 01:01 PM, Oleksij Rempel wrote:
> Am 29.03.2014 11:17, schrieb Harshal Vora:
>> Hi,
>>
>> We are running tp link wn721n usb wifi adapter with atheros 9271 chipset
>> on raspberry pi using kernel version 3.6.11
>> We run the physical interface wlan0 in adhoc mode and also create a
>> virtual interface wlan0-mon0 from wlan0 which runs in monitor mode.
>> The USB chipset suddenly hangs or shuts down after running for sometime.
>> Sometimes it runs for few minutes, sometimes for hours before this happens.
>> Sometimes this happens when a new node enters the adhoc network.
>> We are using babel on top of ad-hoc network to create a mesh like
>> functionality.
>>
>> Below are the logs from one of the device. Also when I try to unload the
>> driver using modprobe -r, it looks like panic mode.
>> We are not using power save mode.
>>
>>
>> Mar 28 15:45:45 localhost kernel: [18268.650000] ath: phy0: Unable to
>> reset channel (2452 Mhz) reset status -22
>> Mar 28 15:45:45 localhost kernel: [18268.670000] ath: phy0: Unable to
>> set channel
>> Mar 28 15:45:46 localhost kernel: [18269.180000] ath: phy0: timeout
>> (100000 us) on reg 0x7000: 0xfffffffb & 0x00000003 != 0x00000000
>> Mar 28 15:45:46 localhost kernel: [18269.180000] ath: phy0: Chip reset
>> failed
>> Mar 28 15:45:46 localhost kernel: [18269.190000] ath: phy0: Unable to
>> reset channel (2457 Mhz) reset status -22
>> Mar 28 15:45:46 localhost kernel: [18269.210000] ath: phy0: Unable to
>> set channel
>> Mar 28 15:45:46 localhost kernel: [18269.720000] ath: phy0: timeout
>> (100000 us) on reg 0x7000: 0xfffffffb & 0x00000003 != 0x00000000
>> Mar 28 15:45:46 localhost kernel: [18269.720000] ath: phy0: Chip reset
>> failed
>> Mar 28 15:45:46 localhost kernel: [18269.730000] ath: phy0: Unable to
>> reset channel (2462 Mhz) reset status -22
>> Mar 28 15:45:46 localhost kernel: [18269.750000] ath: phy0: Unable to
>> set channel
>> Mar 28 15:45:47 localhost kernel: [18270.250000] ath: phy0: timeout
>> (100000 us) on reg 0x7000: 0xfffffffb & 0x00000003 != 0x00000000
>> Mar 28 15:45:47 localhost kernel: [18270.260000] ath: phy0: Chip reset
>> failed
>> Mar 28 15:45:47 localhost kernel: [18270.270000] ath: phy0: Unable to
>> reset channel (2467 Mhz) reset status -22
>> Mar 28 15:45:47 localhost kernel: [18270.280000] ath: phy0: Unable to
>> set channel
>> Mar 28 15:45:47 localhost kernel: [18270.790000] ath: phy0: timeout
>> (100000 us) on reg 0x7000: 0xfffffffb & 0x00000003 != 0x00000000
>> Mar 28 15:45:47 localhost kernel: [18270.800000] ath: phy0: Chip reset
>> failed
>> Mar 28 15:45:48 localhost kernel: [18270.810000] ath: phy0: Unable to
>> reset channel (2472 Mhz) reset status -22
>> Mar 28 15:45:48 localhost kernel: [18270.820000] ath: phy0: Unable to
>> set channel
>> Mar 28 15:45:48 localhost kernel: [18271.330000] ath: phy0: timeout
>> (100000 us) on reg 0x7000: 0xfffffffb & 0x00000003 != 0x00000000
>> Mar 28 15:45:48 localhost kernel: [18271.340000] ath: phy0: Chip reset
>> failed
>> Mar 28 15:45:48 localhost kernel: [18271.350000] ath: phy0: Unable to
>> reset channel (2484 Mhz) reset status -22
>> Mar 28 15:45:48 localhost kernel: [18271.360000] ath: phy0: Unable to
>> set channel
>> Mar 28 15:45:49 localhost kernel: [18271.870000] ath: phy0: timeout
>> (100000 us) on reg 0x7000: 0xfffffffb & 0x00000003 != 0x00000000
>> Mar 28 15:45:49 localhost kernel: [18271.880000] ath: phy0: Chip reset
>> failed
>> Mar 28 15:45:49 localhost kernel: [18271.890000] ath: phy0: Unable to
>> reset channel (2412 Mhz) reset status -22
>> Mar 28 15:45:49 localhost kernel: [18271.900000] ath: phy0: Unable to
>> set channel
>> Mar 28 15:45:49 localhost kernel: [18272.080000] wlan1: expiring
>> inactive STA c0:4a:00:18:db:79
>> Mar 28 15:45:49 localhost kernel: [18272.080000] wlan1: moving STA
>> c0:4a:00:18:db:79 to state 3
>> Mar 28 15:45:49 localhost kernel: [18272.090000] wlan1: moving STA
>> c0:4a:00:18:db:79 to state 2
>> Mar 28 15:45:49 localhost kernel: [18272.090000] ath: phy0: Unable to
>> remove station entry for: c0:4a:00:18:db:79
>> Mar 28 15:45:49 localhost kernel: [18272.110000] wlan1: moving STA
>> c0:4a:00:18:db:79 to state 1
>> Mar 28 15:45:49 localhost kernel: [18272.110000] ieee80211 phy0: Removed
>> STA c0:4a:00:18:db:79
>> Mar 28 15:45:49 localhost kernel: [18272.120000] ieee80211 phy0:
>> Destroyed STA c0:4a:00:18:db:79
>> Mar 28 15:45:49 localhost kernel: [18272.120000] wlan1: expiring
>> inactive STA 10:fe:ed:13:f2:10
>> Mar 28 15:45:49 localhost kernel: [18272.130000] wlan1: moving STA
>> 10:fe:ed:13:f2:10 to state 3
>> Mar 28 15:45:49 localhost kernel: [18272.130000] wlan1: moving STA
>> 10:fe:ed:13:f2:10 to state 2
>> Mar 28 15:45:49 localhost kernel: [18272.140000] ath: phy0: Unable to
>> remove station entry for: 10:fe:ed:13:f2:10
>> Mar 28 15:45:49 localhost kernel: [18272.150000] wlan1: moving STA
>> 10:fe:ed:13:f2:10 to state 1
>> Mar 28 15:45:49 localhost kernel: [18272.160000] ieee80211 phy0: Removed
>> STA 10:fe:ed:13:f2:10
>> Mar 28 15:45:49 localhost kernel: [18272.160000] ieee80211 phy0:
>> Destroyed STA 10:fe:ed:13:f2:10
>> Mar 28 15:45:49 localhost kernel: [18272.170000] wlan1: expiring
>> inactive STA 64:66:b3:18:c9:79
>> Mar 28 15:45:49 localhost kernel: [18272.170000] wlan1: moving STA
>> 64:66:b3:18:c9:79 to state 3
>> Mar 28 15:45:49 localhost kernel: [18272.180000] wlan1: moving STA
>> 64:66:b3:18:c9:79 to state 2
>> Mar 28 15:45:49 localhost kernel: [18272.180000] ath: phy0: Unable to
>> remove station entry for: 64:66:b3:18:c9:79
>> Mar 28 15:45:49 localhost kernel: [18272.200000] wlan1: moving STA
>> 64:66:b3:18:c9:79 to state 1
>> Mar 28 15:45:49 localhost kernel: [18272.200000] ieee80211 phy0: Removed
>> STA 64:66:b3:18:c9:79
>> Mar 28 15:45:49 localhost kernel: [18272.210000] ieee80211 phy0:
>> Destroyed STA 64:66:b3:18:c9:79
>> Mar 28 15:45:49 localhost kernel: [18272.210000] wlan1: expiring
>> inactive STA 00:1f:3c:0b:f0:5c
>> Mar 28 15:45:49 localhost kernel: [18272.220000] wlan1: moving STA
>> 00:1f:3c:0b:f0:5c to state 3
>> Mar 28 15:45:49 localhost kernel: [18272.220000] wlan1: moving STA
>> 00:1f:3c:0b:f0:5c to state 2
>> Mar 28 15:45:49 localhost kernel: [18272.230000] ath: phy0: Unable to
>> remove station entry for: 00:1f:3c:0b:f0:5c
>> Mar 28 15:45:49 localhost kernel: [18272.240000] wlan1: moving STA
>> 00:1f:3c:0b:f0:5c to state 1
>> Mar 28 15:45:49 localhost kernel: [18272.250000] ieee80211 phy0: Removed
>> STA 00:1f:3c:0b:f0:5c
>> Mar 28 15:45:49 localhost kernel: [18272.250000] ieee80211 phy0:
>> Destroyed STA 00:1f:3c:0b:f0:5c
>> Mar 28 15:45:49 localhost kernel: [18272.260000] wlan1: expiring
>> inactive STA 10:fe:ed:14:d5:c4
>> Mar 28 15:45:49 localhost kernel: [18272.260000] wlan1: moving STA
>> 10:fe:ed:14:d5:c4 to state 3
>> Mar 28 15:45:49 localhost kernel: [18272.270000] wlan1: moving STA
>> 10:fe:ed:14:d5:c4 to state 2
>> Mar 28 15:45:49 localhost kernel: [18272.270000] ath: phy0: Unable to
>> remove station entry for: 10:fe:ed:14:d5:c4
>> Mar 28 15:45:49 localhost kernel: [18272.280000] wlan1: moving STA
>> 10:fe:ed:14:d5:c4 to state 1
>> Mar 28 15:45:49 localhost kernel: [18272.290000] ieee80211 phy0: Removed
>> STA 10:fe:ed:14:d5:c4
>> Mar 28 15:45:49 localhost kernel: [18272.290000] ieee80211 phy0:
>> Destroyed STA 10:fe:ed:14:d5:c4
>>
>>
>> Mar 28 15:46:19 localhost kernel: [18302.080000] wlan1: No active IBSS
>> STAs - trying to scan for other IBSS networks with same SSID (merge)
>> Mar 28 15:46:19 localhost kernel: [18302.770000] ath: phy0: timeout
>> (100000 us) on reg 0x7000: 0xfffffffb & 0x00000003 != 0x00000000
>> Mar 28 15:46:19 localhost kernel: [18302.780000] ath: phy0: Chip reset
>> failed
>> Mar 28 15:46:19 localhost kernel: [18302.780000] ath: phy0: Unable to
>> reset channel (2412 Mhz) reset status -22
>> Mar 28 15:46:19 localhost kernel: [18302.800000] ath: phy0: Unable to
>> set channel
>> Mar 28 15:46:20 localhost kernel: [18303.310000] ath: phy0: timeout
>> (100000 us) on reg 0x7000: 0xfffffffb & 0x00000003 != 0x00000000
>> Mar 28 15:46:20 localhost kernel: [18303.310000] ath: phy0: Chip reset
>> failed
>> Mar 28 15:46:20 localhost kernel: [18303.320000] ath: phy0: Unable to
>> reset channel (2417 Mhz) reset status -22
>> Mar 28 15:46:20 localhost kernel: [18303.330000] ath: phy0: Unable to
>> set channel
>> Mar 28 15:46:20 localhost ntpdate[12205]: adjust time server
>> 199.102.46.73 offset -0.001353 sec
>> Mar 28 15:46:21 localhost kernel: [18303.850000] ath: phy0: timeout
>> (100000 us) on reg 0x7000: 0xfffffffb & 0x00000003 != 0x00000000
>> Mar 28 15:46:21 localhost kernel: [18303.860000] ath: phy0: Chip reset
>> failed
>> Mar 28 15:46:21 localhost kernel: [18303.870000] ath: phy0: Unable to
>> reset channel (2422 Mhz) reset status -22
>> Mar 28 15:46:21 localhost kernel: [18303.880000] ath: phy0: Unable to
>> set channel
>> Mar 28 15:46:21 localhost kernel: [18304.390000] ath: phy0: timeout
>> (100000 us) on reg 0x7000: 0xfffffffb & 0x00000003 != 0x00000000
>> Mar 28 15:46:21 localhost kernel: [18304.400000] ath: phy0: Chip reset
>> failed
> Hi Harshal,
>
> please, use latest wireless-testing.git and this firmware branch:
> https://github.com/olerem/open-ath9k-htc-firmware/tree/testing
>
> Latest kernel git has lots of changes in ath9k_htc code. And it is able
> to catch oops pattern from firmware.
> Latest firmware branch, is able to restart on some crashes.
> If you still have this issue, i'll suggest you to investigate it. You
> will need to attach UART to ar9271, to get more info.
> https://wikidevi.com/wiki/AR9271
next prev parent reply other threads:[~2014-03-31 5:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-29 10:17 [ath9k-devel] Adhoc mode and chip reset issue with tp link wn721n/ath9k_htc drivers Harshal Vora
2014-03-30 7:31 ` Oleksij Rempel
2014-03-31 5:41 ` Harshal Vora [this message]
2014-03-31 7:19 ` Oleksij Rempel
2014-03-31 8:06 ` Harshal Vora
2014-03-31 8:22 ` Oleksij Rempel
2014-03-31 9:10 ` Harshal Vora
2014-04-04 12:37 ` Harshal Vora
2014-04-04 12:59 ` Oleksij Rempel
2014-04-19 11:49 ` Harshal Vora
2014-04-19 19:42 ` Oleksij Rempel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53390012.2050307@amideeptech.com \
--to=harshal@amideeptech.com \
--cc=ath9k-devel@lists.ath9k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.