[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD2nsn3-C8ZLmUpTDeA6HuPr-+=V5KkPJb6h5e7ZJsGi4v9p0g@mail.gmail.com>
Date: Mon, 9 Apr 2012 11:58:06 +0530
From: Mohammed Shafi <shafi.wireless@...il.com>
To: Michael Leun <lkml20120218@...ton.leun.net>
Cc: Ben Greear <greearb@...delatech.com>, casteyde.christian@...e.fr,
Kelly Anderson <kelly@...ka.with-linux.com>,
"ath9k-devel@...ts.ath9k.org" <ath9k-devel@...ema.h4ckr.net>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Felix Fietkau <nbd@...nwrt.org>,
linux-wireless Mailing List <linux-wireless@...r.kernel.org>
Subject: Re: 3.4-rc ath9k regression (Re: [ath9k-devel] 3.3.1 ath9k regression)
On Mon, Apr 9, 2012 at 4:38 AM, Michael Leun
<lkml20120218@...ton.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.
>
> 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
View attachment "test.patch" of type "text/x-diff" (641 bytes)
Powered by blists - more mailing lists