* ath9k_htc works poorly in 3.9
@ 2013-05-08 3:52 Corey Richardson
2013-05-08 5:31 ` [ath9k-devel] " Oleksij Rempel
0 siblings, 1 reply; 4+ messages in thread
From: Corey Richardson @ 2013-05-08 3:52 UTC (permalink / raw)
To: linux-wireless, ath9k-devel
Initially, I can associate and everything works fine, but after an
hour or maybe a few, I get deauthenticated, with:
[ 3115.047842] cfg80211: Calling CRDA for country: US
[ 3116.383330] wlan0: authenticate with 00:14:c2:ae:e1:c0
[ 3116.480597] wlan0: send auth to 00:14:c2:ae:e1:c0 (try 1/3)
[ 3119.526272] wlan0: send auth to 00:14:c2:ae:e1:c0 (try 2/3)
[ 3121.485530] wlan0: deauthenticating from 00:14:c2:ae:e1:c0 by local
choice (reason=3)
[ 3123.386841] wlan0: authenticate with 00:14:c2:ae:e1:c0
[ 3123.483019] wlan0: send auth to 00:14:c2:ae:e1:c0 (try 1/3)
[ 3126.528663] wlan0: send auth to 00:14:c2:ae:e1:c0 (try 2/3)
[ 3128.486335] wlan0: deauthenticating from 00:14:c2:ae:e1:c0 by local
choice (reason=3)
[ 3130.879429] wlan0: authenticate with 00:14:c2:ae:e1:c0
[ 3130.976309] wlan0: send auth to 00:14:c2:ae:e1:c0 (try 1/3)
[ 3130.976512] wlan0: deauthenticating from 00:14:c2:ae:e1:c0 by local
choice (reason=3)
in dmesg and
May 07 23:32:57 roger NetworkManager[317]: <warn> Connection
disconnected (reason -4)
May 07 23:32:57 roger NetworkManager[317]: <info> (wlan0): supplicant
interface state: completed -> disconnected
May 07 23:32:58 roger NetworkManager[317]: <info> (wlan0): supplicant
interface state: disconnected -> scanning
May 07 23:32:59 roger NetworkManager[317]: <info> (wlan0): supplicant
interface state: scanning -> authenticating
May 07 23:32:59 roger NetworkManager[317]: <info> (wlan0): roamed from
BSSID 00:14:C2:AE:E1:C0 (home1) to (none) ((none))
May 07 23:33:04 roger NetworkManager[317]: <info> (wlan0): supplicant
interface state: authenticating -> disconnected
May 07 23:33:04 roger NetworkManager[317]: <warn> Connection
disconnected (reason -3)
May 07 23:33:05 roger NetworkManager[317]: <info> (wlan0): supplicant
interface state: disconnected -> scanning
May 07 23:33:06 roger NetworkManager[317]: <info> (wlan0): supplicant
interface state: scanning -> authenticating
May 07 23:33:11 roger NetworkManager[317]: <info> (wlan0): supplicant
interface state: authenticating -> disconnected
May 07 23:33:11 roger NetworkManager[317]: <warn> Connection
disconnected (reason -3)
May 07 23:33:12 roger NetworkManager[317]: <info> (wlan0): supplicant
interface state: disconnected -> scanning
May 07 23:33:13 roger NetworkManager[317]: <warn> (wlan0): link timed out.
May 07 23:33:13 roger NetworkManager[317]: <info> (wlan0): device
state change: activated -> failed (reason 'SSID not found') [100 120
53]
May 07 23:33:13 roger NetworkManager[317]: <warn> Activation (wlan0)
failed for connection 'home1'
May 07 23:33:13 roger NetworkManager[317]: <info> (wlan0): device
state change: failed -> disconnected (reason 'none') [120 30 0]
May 07 23:33:13 roger NetworkManager[317]: <info> (wlan0):
deactivating device (reason 'none') [0]
May 07 23:33:13 roger NetworkManager[317]: <info> (wlan0): canceled
DHCP transaction, DHCP client pid 527
May 07 23:33:14 roger NetworkManager[317]: <info> (wlan0): supplicant
interface state: scanning -> authenticating
May 07 23:33:14 roger NetworkManager[317]: <warn> Connection
disconnected (reason -3)
May 07 23:33:14 roger NetworkManager[317]: <info> (wlan0): supplicant
interface state: authenticating -> disconnected
May 07 23:33:14 roger NetworkManager[317]: <warn> Connection
disconnected (reason -3)
in the journal.
Removing and reinserting the USB stick allows me to reassociate about
50% of the time; others need a reboot.
This is a regression from 3.8. It was present in the earlier 3.9 RC's
after Johannes' fix for idle sequence handling, but not before the
changes that broke ath9k_htc, so I think something between the patch
that broke the driver and the patch that fixed it is to blame.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [ath9k-devel] ath9k_htc works poorly in 3.9
2013-05-08 3:52 ath9k_htc works poorly in 3.9 Corey Richardson
@ 2013-05-08 5:31 ` Oleksij Rempel
2013-05-15 17:31 ` Corey Richardson
0 siblings, 1 reply; 4+ messages in thread
From: Oleksij Rempel @ 2013-05-08 5:31 UTC (permalink / raw)
To: Corey Richardson; +Cc: linux-wireless, ath9k-devel
Am 08.05.2013 05:52, schrieb Corey Richardson:
> Initially, I can associate and everything works fine, but after an
> hour or maybe a few, I get deauthenticated, with:
>
> [ 3115.047842] cfg80211: Calling CRDA for country: US
> [ 3116.383330] wlan0: authenticate with 00:14:c2:ae:e1:c0
> [ 3116.480597] wlan0: send auth to 00:14:c2:ae:e1:c0 (try 1/3)
> [ 3119.526272] wlan0: send auth to 00:14:c2:ae:e1:c0 (try 2/3)
> [ 3121.485530] wlan0: deauthenticating from 00:14:c2:ae:e1:c0 by local
> choice (reason=3)
> [ 3123.386841] wlan0: authenticate with 00:14:c2:ae:e1:c0
> [ 3123.483019] wlan0: send auth to 00:14:c2:ae:e1:c0 (try 1/3)
> [ 3126.528663] wlan0: send auth to 00:14:c2:ae:e1:c0 (try 2/3)
> [ 3128.486335] wlan0: deauthenticating from 00:14:c2:ae:e1:c0 by local
> choice (reason=3)
> [ 3130.879429] wlan0: authenticate with 00:14:c2:ae:e1:c0
> [ 3130.976309] wlan0: send auth to 00:14:c2:ae:e1:c0 (try 1/3)
> [ 3130.976512] wlan0: deauthenticating from 00:14:c2:ae:e1:c0 by local
> choice (reason=3)
>
> in dmesg and
>
> May 07 23:32:57 roger NetworkManager[317]: <warn> Connection
> disconnected (reason -4)
> May 07 23:32:57 roger NetworkManager[317]: <info> (wlan0): supplicant
> interface state: completed -> disconnected
> May 07 23:32:58 roger NetworkManager[317]: <info> (wlan0): supplicant
> interface state: disconnected -> scanning
> May 07 23:32:59 roger NetworkManager[317]: <info> (wlan0): supplicant
> interface state: scanning -> authenticating
> May 07 23:32:59 roger NetworkManager[317]: <info> (wlan0): roamed from
> BSSID 00:14:C2:AE:E1:C0 (home1) to (none) ((none))
> May 07 23:33:04 roger NetworkManager[317]: <info> (wlan0): supplicant
> interface state: authenticating -> disconnected
> May 07 23:33:04 roger NetworkManager[317]: <warn> Connection
> disconnected (reason -3)
> May 07 23:33:05 roger NetworkManager[317]: <info> (wlan0): supplicant
> interface state: disconnected -> scanning
> May 07 23:33:06 roger NetworkManager[317]: <info> (wlan0): supplicant
> interface state: scanning -> authenticating
> May 07 23:33:11 roger NetworkManager[317]: <info> (wlan0): supplicant
> interface state: authenticating -> disconnected
> May 07 23:33:11 roger NetworkManager[317]: <warn> Connection
> disconnected (reason -3)
> May 07 23:33:12 roger NetworkManager[317]: <info> (wlan0): supplicant
> interface state: disconnected -> scanning
> May 07 23:33:13 roger NetworkManager[317]: <warn> (wlan0): link timed out.
> May 07 23:33:13 roger NetworkManager[317]: <info> (wlan0): device
> state change: activated -> failed (reason 'SSID not found') [100 120
> 53]
> May 07 23:33:13 roger NetworkManager[317]: <warn> Activation (wlan0)
> failed for connection 'home1'
> May 07 23:33:13 roger NetworkManager[317]: <info> (wlan0): device
> state change: failed -> disconnected (reason 'none') [120 30 0]
> May 07 23:33:13 roger NetworkManager[317]: <info> (wlan0):
> deactivating device (reason 'none') [0]
> May 07 23:33:13 roger NetworkManager[317]: <info> (wlan0): canceled
> DHCP transaction, DHCP client pid 527
> May 07 23:33:14 roger NetworkManager[317]: <info> (wlan0): supplicant
> interface state: scanning -> authenticating
> May 07 23:33:14 roger NetworkManager[317]: <warn> Connection
> disconnected (reason -3)
> May 07 23:33:14 roger NetworkManager[317]: <info> (wlan0): supplicant
> interface state: authenticating -> disconnected
> May 07 23:33:14 roger NetworkManager[317]: <warn> Connection
> disconnected (reason -3)
>
>
> in the journal.
>
> Removing and reinserting the USB stick allows me to reassociate about
> 50% of the time; others need a reboot.
>
> This is a regression from 3.8. It was present in the earlier 3.9 RC's
> after Johannes' fix for idle sequence handling, but not before the
> changes that broke ath9k_htc, so I think something between the patch
> that broke the driver and the patch that fixed it is to blame.
Hi Corey,
only person who can help to fix it is you ;)
Currently I'm trying to reproduce other bug with this driver/firmware
without luck. Yesterday i started my test, i streamed some hundred
gigabytes over the air and my system is still working.
My kernel is 3.9.0-wl-00003-g4125f14
If it is an regression, can you please do "git bisect". If you can
locate the patch which introduced this regression, it will be great.
--
Regards,
Oleksij
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [ath9k-devel] ath9k_htc works poorly in 3.9
2013-05-08 5:31 ` [ath9k-devel] " Oleksij Rempel
@ 2013-05-15 17:31 ` Corey Richardson
2013-05-15 17:33 ` Ben Greear
0 siblings, 1 reply; 4+ messages in thread
From: Corey Richardson @ 2013-05-15 17:31 UTC (permalink / raw)
To: Oleksij Rempel; +Cc: linux-wireless, ath9k-devel
On Wed, May 8, 2013 at 1:31 AM, Oleksij Rempel <linux@rempel-privat.de> wrote:
> If it is an regression, can you please do "git bisect". If you can locate
> the patch which introduced this regression, it will be great.
>
It seems to have been an intermittent problem with my WAP as well; the
PoE wasn't consistent so it kept dropping out, also taking down the
adapter with it. It does seem to be a regression, but it's so hard to
reproduce that I don't think it's worth pursuing.
Thanks!
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [ath9k-devel] ath9k_htc works poorly in 3.9
2013-05-15 17:31 ` Corey Richardson
@ 2013-05-15 17:33 ` Ben Greear
0 siblings, 0 replies; 4+ messages in thread
From: Ben Greear @ 2013-05-15 17:33 UTC (permalink / raw)
To: Corey Richardson; +Cc: Oleksij Rempel, ath9k-devel, linux-wireless
On 05/15/2013 10:31 AM, Corey Richardson wrote:
> On Wed, May 8, 2013 at 1:31 AM, Oleksij Rempel <linux@rempel-privat.de> wrote:
>> If it is an regression, can you please do "git bisect". If you can locate
>> the patch which introduced this regression, it will be great.
>>
>
> It seems to have been an intermittent problem with my WAP as well; the
> PoE wasn't consistent so it kept dropping out, also taking down the
> adapter with it. It does seem to be a regression, but it's so hard to
> reproduce that I don't think it's worth pursuing.
Sometimes I see the NIC fail to boot up on reboot of the OS.
I've only tested 3.9 kernels with these NICs, as I haven't used
them previously.
The kernel message was something about not being able to upload
firmware to the adapter...I'll grab some logs next
time I see it.
Thanks,
Ben
>
> Thanks!
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel@lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2013-05-15 17:33 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-05-08 3:52 ath9k_htc works poorly in 3.9 Corey Richardson
2013-05-08 5:31 ` [ath9k-devel] " Oleksij Rempel
2013-05-15 17:31 ` Corey Richardson
2013-05-15 17:33 ` Ben Greear
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).