From owner-freebsd-wireless@FreeBSD.ORG Tue Mar 26 22:34:40 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 66D3351F for ; Tue, 26 Mar 2013 22:34:40 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-ia0-x235.google.com (mail-ia0-x235.google.com [IPv6:2607:f8b0:4001:c02::235]) by mx1.freebsd.org (Postfix) with ESMTP id 3ABD889C for ; Tue, 26 Mar 2013 22:34:40 +0000 (UTC) Received: by mail-ia0-f181.google.com with SMTP id o25so6723556iad.40 for ; Tue, 26 Mar 2013 15:34:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=lgcFGtkt4BXgOcld2GKXyKSY/oD33qW7W76auBGis4I=; b=yWonE3/DosbmZRAha51VH005WAX35Sw4Vn53ArNQ/PFrE+CrHs9BnhaN5lf1QahVWM BoiYIlhC2zrSkaXaDKPxKYF9+F7/X0Ll/evjMRFgcsvbPG5o89UNV3bHH4EFkUlL3zC/ QGp//yIsBA2VfIXYYtGlrpMeoQdGgU9bXIG+QMtTGGB92wWJLmhOQi1Phvu/cEntvkQb lnngV9++tsqj7l5WFg8N7aE0UvxIPDvNTTgm4dgu0e9yUZaaJU/b82F7nXhkMlukm06w tDcWv91eTvL10rSm9eZjUyljZR1B5Ny+P/ERXP8pGKwSwjSToJdrXEk6QfEo4sBwbeFc 1txg== X-Received: by 10.50.153.165 with SMTP id vh5mr2684900igb.48.1364337279183; Tue, 26 Mar 2013 15:34:39 -0700 (PDT) Received: from [192.168.1.44] (c-98-212-197-211.hsd1.il.comcast.net. [98.212.197.211]) by mx.google.com with ESMTPS id wx2sm4530251igb.4.2013.03.26.15.34.37 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 26 Mar 2013 15:34:38 -0700 (PDT) Message-ID: <51522277.6040107@gmail.com> Date: Tue, 26 Mar 2013 17:34:31 -0500 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: freebsd-wireless@freebsd.org Subject: Re: [wip] ar9300 hostap support References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: Tue, 26 Mar 2013 22:34:40 -0000 I know it'll sound bad, but I've had two hours of uptime without a panic and while keeping network. It seems you'ved fixed the network connectivity problem, which could have been because of a weak signal, and the panics. My dmesg is getting occasional "ath0: ath_edma_recv_proc_queue: handled npkts 0" but not nearly as often as before. On 3/26/2013 3:10 PM, Adrian Chadd wrote: > .. and it's all now in -HEAD. > > Please update to -HEAD before you test out the AR9380 support. > > Joshua - I've also put in a work around to stop things crashing on an > empty tx queue. It'll just log a warning. > > I'm going to add some further debugging code to ensure that frames > going into a TXQ actually _have_ the right queue ID set in the > descriptor. It's quite possible that I've screwed this up somewhere. > > Thanks, > > > Adrian >