From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben Greear Date: Fri, 07 Jan 2011 09:24:58 -0800 Subject: [ath9k-devel] ath9k deadbeef In-Reply-To: References: Message-ID: <4D274C6A.8010602@candelatech.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org On 01/07/2011 08:55 AM, Senthilkumar Balasubramanian wrote: > On Fri, Jan 7, 2011 at 10:04 PM, Brian Prodoehl wrote: >> What's the story on reading a register in ath9k and getting >> 0xDEADBEEF? I know this has come up before, and whatever the symptom > > If you are seeing DEADBEEF then the chip is in SLEEP state and i believe > there is some race condition still where we need to handle > sleep/wakeup properly. > > Can you please provide us the steps to reproduce this issue consistently? > > I assume you are using the latest wireless testing, please confirm. For me: Create 60 stations, bring them up, rmmod ath9k modules. Watch DMA fail to stop and very often DEADBEEF register reads. Probably a lot less stations would do the same, but it happens very often with 60. Doesn't seem to do any lasting harm, however... The failure to stop DMA *might* be the cause of the rmmod corruption crash I reported yesterday, but not certain. I am using latest wireless-testing, but have seen this same general problem for months. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com