lkml.org 
[lkml]   [2012]   [Apr]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    Date
    SubjectRe: 3.4-rc ath9k regression (Re: [ath9k-devel] 3.3.1 ath9k regression)
    Hello Mohammed,

    On Mon, Apr 9, 2012 at 2:28 AM, Mohammed Shafi <shafi.wireless@gmail.com> wrote:
    > On Mon, Apr 9, 2012 at 4:38 AM, Michael Leun
    > <lkml20120218@newton.leun.net> wrote:
    >> After an suspend to disk / resume cycle (in kernel suspend to disk,
    >> openSuSE) with 3.4-rc2 my ath9k wireless does not ping
    >> anymore.
    >>
    >> Output of iwconfig wlan0 looks just as usual (associated to AP).
    >>
    >> iwconfig wlan0 essid <myssid> fixes this (causes an
    >> deauthenticate/authenticate with AP) - then connectivity is there again.
    >>
    >> Guess what: "Of course" does not happen when reverting
    >> c1afdaff90538ef085b756454f12b29575411214 ath9k: fix going to full-sleep
    >> on PS idle.
    >>
    >> So, in my opinion it should be seriously considered to revert that patch
    >> until it is fully understood what is going on and why.
    >
    > please try with the attached patch to see if it helps.
    >

    with your patch applied on a 3.3 kernel, nothing seems to change here
    (AR9285 PCI express): if the card goes through the suspend/resume
    cycle, or if I disable/re-enabled the wireless networking on the
    network manager, I get the following messages:

    [ 62.931045] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 65.770425] wlan0: authenticate with 00:26:44:68:e0:6f (try 1)
    [ 65.967949] wlan0: authenticate with 00:26:44:68:e0:6f (try 2)
    [ 66.167722] wlan0: authenticate with 00:26:44:68:e0:6f (try 3)
    [ 66.367504] wlan0: authentication with 00:26:44:68:e0:6f timed out

    if I unload/reload the ath9k module, it works again, though:

    [ 88.657560] ath9k: Driver unloaded
    [ 88.714713] ath: EEPROM regdomain: 0x60
    [ 88.714715] ath: EEPROM indicates we should expect a direct regpair map
    [ 88.714718] ath: Country alpha2 being used: 00
    [ 88.714720] ath: Regpair used: 0x60
    [ 88.716415] ieee80211 phy1: Selected rate control algorithm
    'ath9k_rate_control'
    [ 88.716933] Registered led device: ath9k-phy1
    [ 88.716948] ieee80211 phy1: Atheros AR9285 Rev:2
    mem=0xffffc90005960000, irq=17
    [ 88.735253] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 91.568727] wlan0: authenticate with 00:26:44:68:e0:6f (try 1)
    [ 91.572181] wlan0: authenticated
    [ 91.593796] wlan0: associate with 00:26:44:68:e0:6f (try 1)
    [ 91.598115] wlan0: RX AssocResp from 00:26:44:68:e0:6f (capab=0x411
    status=0 aid=2)
    [ 91.598119] wlan0: associated
    [ 91.598122] wlan0: moving STA 00:26:44:68:e0:6f to state 1
    [ 91.598124] wlan0: moving STA 00:26:44:68:e0:6f to state 2
    [ 91.598775] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 91.611432] wlan0: moving STA 00:26:44:68:e0:6f to state 3
    thanks,
    sergio

    >>
    >> It may look theoretically correct (I've no knowledge that would enable
    >> me assess that), but it seems to have caused 3 more or less different
    >> problems to various people.
    >>
    >> --
    >> MfG,
    >>
    >> Michael Leun
    >>
    >
    >
    >
    > --
    > thanks,
    > shafi


    \
     
     \ /
      Last update: 2012-04-09 10:47    [from the cache]
    ©2003-2011 Jasper Spaans