linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Valerio Passini <valerio.passini@unicam.it>
To: linux-wireless@vger.kernel.org
Subject: Stability connection problems in ath9k kernel 4.7
Date: Wed, 07 Sep 2016 09:49:42 +0200	[thread overview]
Message-ID: <1798564.U2X6r5Zons@automatix> (raw)

Hello,

I have found some connection problems since 4.7 release using ath9k that turn 
the wifi pretty useless, I think it might be something in the power management 
because the signal seems really low. Previously, up to kernel 4.6.7 everything 
worked very well.
This is a sample of dmesg in kernel 4.7.2:
 239.898935] wlp4s0: authenticate with XX:XX:XX:XX:XX:XX 
[  239.919995] wlp4s0: send auth to XX:XX:XX:XX:XX:XX  (try 1/3) 
[  239.931877] wlp4s0: authenticated 
[  239.932357] wlp4s0: associate with XX:XX:XX:XX:XX:XX  (try 1/3) 
[  239.942171] wlp4s0: RX AssocResp from XX:XX:XX:XX:XX:XX  (capab=0x431 
status=0 aid=2) 
[  239.942301] wlp4s0: associated 
[  244.802853] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 
AR_DIAG_SW=0x02000020 DMADBG_7=0x0000
6100                                                                                                         
[  245.931832] wlp4s0: authenticate with XX:XX:XX:XX:XX:XX  
[  245.953028] wlp4s0: send auth to XX:XX:XX:XX:XX:XX  (try 1/3) 
[  245.958702] wlp4s0: authenticated 
[  245.960386] wlp4s0: associate withXX:XX:XX:XX:XX:XX  (try 1/3) 
[  245.980543] wlp4s0: RX AssocResp from XX:XX:XX:XX:XX:XX  (capab=0x431 
status=0 aid=2)

lspci on 4.6.7 kernel:
04:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter 
(rev 01)
        Subsystem: AzureWave AR9485 Wireless Network Adapter
        Flags: bus master, fast devsel, latency 0, IRQ 18
        Memory at f7900000 (64-bit, non-prefetchable) [size=512K]
        Expansion ROM at f7980000 [disabled] [size=64K]
        Capabilities: [40] Power Management version 2
        Capabilities: [50] MSI: Enable- Count=1/4 Maskable+ 64bit+
        Capabilities: [70] Express Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Virtual Channel
        Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00
        Kernel driver in use: ath9k
        Kernel modules: ath9k

Probably you need some debugging output, but before recompiling the kernel I 
would like to know if you are interested in any kind of help from me and what 
steps I should take (I'm able to help in testing patches but I'm not familiar 
with git). Thank you

Valerio

             reply	other threads:[~2016-09-07  7:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-07  7:49 Valerio Passini [this message]
2016-09-07  8:32 ` Stability connection problems in ath9k kernel 4.7 Kalle Valo
2016-09-08 14:11   ` Valerio Passini
2016-09-08 14:20     ` Valerio Passini
2016-09-08 17:25     ` Kalle Valo
     [not found]       ` <CAC6K2=_Hdkgc_6igoC59J_Cn9=bdye827zbEK7PWtZY6ebh-6Q@mail.gmail.com>
2016-09-09  8:38         ` Joerg Roedel
2016-09-09 14:32           ` Valerio Passini

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=1798564.U2X6r5Zons@automatix \
    --to=valerio.passini@unicam.it \
    --cc=linux-wireless@vger.kernel.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 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).