From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754879Ab2ALSEq (ORCPT ); Thu, 12 Jan 2012 13:04:46 -0500 Received: from h118.nextmail.ru ([194.67.36.118]:50128 "EHLO h118.nextmail.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751142Ab2ALSEo (ORCPT ); Thu, 12 Jan 2012 13:04:44 -0500 To: =?koi8-r?B?TW9oYW1tZWQgU2hhZmk=?= From: =?koi8-r?B?TVI=?= CC: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org, "=?koi8-r?B?UmFqa3VtYXIgTWFub2hhcmFu?=" Subject: =?koi8-r?B?UmU6IGF0aDlrIGNyYXNoIDMuMi1yYzc=?= Date: Thu, 12 Jan 2012 22:04:41 +0400 X-Mailer: NextMail.Ru X-RemoteAddr: 195.91.224.225 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > 2012/1/11 MR : > >> does roaming seems to trigger this issue consistently ? > >> . please provide the logs > >> sudo modprobe -v ath9k debug=0xffffffff > >> http://linuxwireless.org/en/users/Drivers/ath9k/debug > > > > As I need to rebuild for CONFIG_ATH_DEBUG: should I check the allegedely > > proper fix or wide-angle code removal first? > > please check with the proper fix Turned out I got lucky previous time. This time I went to the other AP, spent some time under it, roamed back and WiFi didn't disappear. I didn't even lose XMPP connections in the process. Maybe debug printing (which prints a lot) managed to introduce some extra delays into some race condition. I hope I will have time to test this more on Monday. Tomorrow I will be using WiFi less than usual.