From owner-freebsd-wireless@FreeBSD.ORG Mon Aug 13 01:00:11 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 6C4E2106566B for ; Mon, 13 Aug 2012 01:00:11 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 3927E8FC17 for ; Mon, 13 Aug 2012 01:00:10 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so6712888pbb.13 for ; Sun, 12 Aug 2012 18:00:10 -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=6ytHWmZLRdrdfZcJTXfXa1AYUns6a57bvkmgXgYskCE=; b=1FgRusc8H8zgenlCa+ABLJBlh6RPJxvNso3NX4cVWoaQXdumjhRw2Z9qyFOMbLGzR3 0xQJ2izDlUEY6wyYQMFQLdU18vo0FfggXyzf/PfA5LsOJhu1X8zoYi38dvWN5d6q+8Fi 9sX7sRlGZzcdktdgBjeYCCl3/T/tOlQSfdVuL31sLNIYfSJ3X1g1SiDTz6WgXvzZpSK3 RlacNnAhWe5e9uTKyn2KUgjxaqMna6mIPn6NJykKL7a8i5wFXn2cPj0kCPkIMdSrkHjq I2WjGfJjqClbE5N1wm+9Kh2CzyMdajPGwa/J9VRLAd0+WAADLYP/kpFoRaG0hrHLD3Io kjGg== MIME-Version: 1.0 Received: by 10.66.75.195 with SMTP id e3mr14491802paw.32.1344819610430; Sun, 12 Aug 2012 18:00:10 -0700 (PDT) Received: by 10.68.43.169 with HTTP; Sun, 12 Aug 2012 18:00:10 -0700 (PDT) In-Reply-To: References: Date: Sun, 12 Aug 2012 18:00:10 -0700 Message-ID: From: Adrian Chadd To: Kim Culhan 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:00:11 -0000 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. Adrian