From owner-freebsd-wireless@FreeBSD.ORG Mon Aug 13 01:10:20 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 38DB6106564A for ; Mon, 13 Aug 2012 01:10:20 +0000 (UTC) (envelope-from w8hdkim@gmail.com) Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id D50E78FC1A for ; Mon, 13 Aug 2012 01:10:19 +0000 (UTC) Received: by vcbgb22 with SMTP id gb22so3912694vcb.13 for ; Sun, 12 Aug 2012 18:10:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Ms+Ffu8DfZVUJhYPMywnluHLuy7vHUJ1/YdhFJ4rq9Q=; b=vrn/NpDjZpxBOymDLMw07XXQ8/SigH0T/SKQW1syRMLULveOk0LXCW/b49czPQm/VT RczAHF+9GylCw4xaxRyvDGyiacFC+KmdSOd8d5TqnktukTc0WJPccS0SEY1Q6mhRNja5 m5gpzFXuZE6RpuHKcvxWfP/Jdq6UyYHJXp/xBAaH3VmpnMOFKbm0eVfQkUmSk5WKjbHe 0R3DtNbcqGxQHPPUxjoXTjcy7jFhBr5jfcLHL/fsMA82/5CnOHXqmiKahJrZ/CKm4Gub eSDxb+KdntuVi8b6VThql0sPKhcHQt6zVmubMfQVmwi5HPLL7HDBdGZrsWAXPqGKoR9Z N14g== MIME-Version: 1.0 Received: by 10.221.9.142 with SMTP id ow14mr4164674vcb.33.1344820218583; Sun, 12 Aug 2012 18:10:18 -0700 (PDT) Received: by 10.58.200.101 with HTTP; Sun, 12 Aug 2012 18:10:18 -0700 (PDT) In-Reply-To: References: Date: Sun, 12 Aug 2012 21:10:18 -0400 Message-ID: From: Kim Culhan To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org, moonlightakkiy@yahoo.ca Subject: Re: (ANother) stall fixed, please update to HEAD 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, 13 Aug 2012 01:10:20 -0000 On Sun, Aug 12, 2012 at 9:00 PM, Adrian Chadd wrote: > Cool, thanks. > > I think this particular bug (kern/170513) is different to what you've > been seeing. > > Those descriptors don't look like they actually _have_ the aggregate > bit set. It's almost like what I'm queueing to the hardware is broken. > > Please update to -HEAD and retest. If it's still broken (read: my > recent fixes to the restart DMA code didn't fix it) then I'll have to > start digging into things to see how it is there's only one buffer in > the aggregate list but bf_state.bfs_nframes > 1. > > Thanks! Let's try to nail this one down quickly so I can shift onto > trying to design a working power save management framework and > filtered frames support so we can finally advertise 11n support by > default. Updated to revision 239222 and building now. thanks -kim