From: Michael Leun Date: Mon, 9 Apr 2012 01:08:16 +0200 Subject: [ath9k-devel] 3.4-rc ath9k regression (Re: 3.3.1 ath9k regression) In-Reply-To: <4F7F52BD.7060906@candelatech.com> 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> Message-ID: <20120409010816.36244f17@xenia.leun.net> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org 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. 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