Return-path: Received: from serv04.lahn.de ([213.239.197.57]:48781 "EHLO serv04.lahn.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753051Ab2DIK0W (ORCPT ); Mon, 9 Apr 2012 06:26:22 -0400 Date: Mon, 9 Apr 2012 12:25:49 +0200 From: Michael Leun To: Mohammed Shafi Cc: Ben Greear , casteyde.christian@free.fr, Kelly Anderson , "ath9k-devel@lists.ath9k.org" , Linux Kernel Mailing List , Felix Fietkau , linux-wireless Mailing List , Sergio Correia Subject: Re: 3.4-rc ath9k regression (Re: [ath9k-devel] 3.3.1 ath9k regression) Message-ID: <20120409122549.7469543a@xenia.leun.net> (sfid-20120409_122639_178997_F0BA567E) In-Reply-To: References: <4F7A8EB7.4060200@silka.with-linux.com> <4F7A923D.5000002@candelatech.com> <4F7A9D5C.8040402@silka.with-linux.com> <4F7AAAD9.2040307@silka.with-linux.com> <4F7AB6FE.3080009@silka.with-linux.com> <20120403200306.0afbb48b@xenia.leun.net> <20120404235104.682cfad3@xenia.leun.net> <4F7DE3A4.1040705@candelatech.com> <4F7F52BD.7060906@candelatech.com> <20120409010816.36244f17@xenia.leun.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-wireless-owner@vger.kernel.org List-ID: On Mon, 9 Apr 2012 11:58:06 +0530 Mohammed Shafi wrote: > On Mon, Apr 9, 2012 at 4:38 AM, Michael Leun > 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 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. Yes, this patch helps with the issue I see in 3.4-rc2 described above. But I agree with Ben and Sergio that it does NOT help with the issue in 3.3.1 we all see. -- MfG, Michael Leun