From owner-freebsd-wireless@FreeBSD.ORG Mon Nov 21 22:56:12 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 00AF6106564A; Mon, 21 Nov 2011 22:56:12 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 95DBF8FC15; Mon, 21 Nov 2011 22:56:11 +0000 (UTC) Received: by vcbfl10 with SMTP id fl10so3383165vcb.13 for ; Mon, 21 Nov 2011 14:56:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=3ZQDP7gRlOaZBG2vQ4HnHft9pSrszTuuyZmE5ZDEjbo=; b=Ew7Uk9/SV5oRV0P/Xak3HFFTJ3g3tbas8iyFFGeonY1YRLLoB3c0hkF7IcZRE82FtH WGyS/plDAs6Rsa4AuMCa9gl6+NxfWxx85R1Icz2eBygQIgyNPft7s9AQAOoIMOs55pV8 RajxbMbVDUT7Nv8pyCCfZU1LSUcIxbmVCuI50= MIME-Version: 1.0 Received: by 10.52.34.78 with SMTP id x14mr17271721vdi.122.1321916170433; Mon, 21 Nov 2011 14:56:10 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.29.198 with HTTP; Mon, 21 Nov 2011 14:56:10 -0800 (PST) In-Reply-To: <20111121225343.GA19155@freebsd.org> References: <20111121131730.GA3599@freebsd.org> <20111121152054.GA22220@freebsd.org> <20111121221224.GA11508@freebsd.org> <20111121225343.GA19155@freebsd.org> Date: Tue, 22 Nov 2011 06:56:10 +0800 X-Google-Sender-Auth: MdlJ46Z_RwiBFqwbRgkEPRlKwh4 Message-ID: From: Adrian Chadd To: Alexander Best Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: issues with the recent ath commits (r227740, r227651, ...) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Nov 2011 22:56:12 -0000 On 22 November 2011 06:53, Alexander Best wrote: > ok. after > 45 minutes uptime i can confirm that the patch fixes the issues i > experienced beforehand. unless i didn't get a boot-up-panic, my system locked > up after < 5 minutes. Sweet, I'll commit that to -HEAD now. > however using your patch i noticed the following console output: > > ath0: ath_start: sc_inreset_cnt > 0; bailing > > ... only once, however. i don't believe i've seen this one ever beforehand. That's intentional. That means that a frame was queued for TX whilst the hardware was busy being reset. It may be because I'm now processing the frames on an interface reset, rather than just deleting them. But on SMP machines it's quite plausible that a reset on one thread would run in parallel with if_start on another thread, causing these to interfere. My eventual aim is to have TX/RX properly suspended before a reset occurs, so these messages will go away (and their appearance will only be when there's a real problem.) But that's going to take time. Thanks for getting back to me about this issue! Adrian