From owner-freebsd-wireless@FreeBSD.ORG Fri Apr 26 08:51:19 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 6E9136AB; Fri, 26 Apr 2013 08:51:19 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com [IPv6:2a00:1450:400c:c03::22e]) by mx1.freebsd.org (Postfix) with ESMTP id D0BA418BE; Fri, 26 Apr 2013 08:51:18 +0000 (UTC) Received: by mail-we0-f174.google.com with SMTP id t9so2876746wey.5 for ; Fri, 26 Apr 2013 01:51:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=ejG2qhn9AnEtP5JT05AMPgZXZroD1NZM12GNz20a9Xk=; b=kLlbKYNhfHu4rcPw/u2+uVGUlAp1qGIiDyYW02+8ghgNI9cbO+FoAOnXMXKrCc5TT+ 4zxXEI0ak/NXc8qpJgWZ4B4GRRu4ogoThQnDqUimpIIQXWbHjna+ebLxnBYkVaUXypc9 bJXZBvQgfANLvPRhHyLroyKO9mC6S/I/tYp8RYCECjGWBnbxwFhzZMzcaZncZ0BePGKJ s8uHPtoqQSmOr2e78i7OrK2XrzKYrDIGzjDeQ54ipGPOIM98JX8+zUxABXaD8JqpXz4n pqkTcBG1JboH/Bt8pBqo6LNrG9rMLxIwY0NhBMonB/RCAkMkWVzAOYG9Q6vE6s66tAFw kzNQ== MIME-Version: 1.0 X-Received: by 10.194.93.133 with SMTP id cu5mr80862719wjb.56.1366966277230; Fri, 26 Apr 2013 01:51:17 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Fri, 26 Apr 2013 01:51:17 -0700 (PDT) In-Reply-To: References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> Date: Fri, 26 Apr 2013 01:51:17 -0700 X-Google-Sender-Auth: vEj8OwfsUe8CFMNFg_OuBZJoepY Message-ID: Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic From: Adrian Chadd To: lev@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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: Fri, 26 Apr 2013 08:51:19 -0000 On 26 April 2013 01:45, Adrian Chadd wrote: > Hi, > > Wait. sysctl dev.ath.0.forcebstuck=1 didn't fix it? So the descriptors are mostly completed. I really need to hack the reset path to continue printing everything in the queue, not just the frames that were completed. But the TXQ[1] head pointer is pointing to the wrong descriptor. It's pointing to a descriptor that's finished, whose next descriptor is also finished. That makes no sense. I'll have to add some more debugging to -HEAD so to dump out the full set of TX descriptors in the queue. That hopefully will shed some light here. Adrian