From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Houghton Date: Tue, 7 Jun 2011 21:54:28 +0100 Subject: [ath9k-devel] ath9k causes lockups since kernel 2.6.35 In-Reply-To: References: <20110310131950.61580121@toddler> <20110314162721.1c3e1429@toddler> <20110606205400.6840a9b8@realh.co.uk> <20110607011748.48f797e8@toddler> Message-ID: <20110607215428.1dabdbe8@toddler> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org On Tue, 7 Jun 2011 09:21:51 +0800 Adrian Chadd wrote: > Ok, checking out a previous version of the wireless-testing tree (@ > 53bc7aa08b48e5cd745f986731cc7dc24eef2a9f) shows that > ath9k_hw_configpcipowersave() is different in that version to later > versions. > > So moral of the story tony - please checkout a tree before that commit > and test. :-) There's significant differences between ath9k back then > and now to make comparison non-trivial. My bisect log showed the last "good" commit was d5cdfacb35ed886271d1ccfffbded98d3447da17 and the first "bad" 53bc7aa08b48e5cd745f986731cc7dc24eef2a9f. I tested those again and it seemed to confirm the initial finding. With the "good" one I suspended/resumed at least twice, did rmmod ath9k at least twice, and disabled wireless with NetworkManager, all without incident. The "bad" one crashed the first time I tried rmmod ath9k.