From owner-freebsd-wireless@FreeBSD.ORG Thu Feb 2 19:32:18 2012 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 56EA21065672 for ; Thu, 2 Feb 2012 19:32:18 +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 107ED8FC08 for ; Thu, 2 Feb 2012 19:32:17 +0000 (UTC) Received: by vcmm1 with SMTP id m1so3178047vcm.13 for ; Thu, 02 Feb 2012 11:32:17 -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=0P2sXeU2BMGzjsXiE1xJYuQeNcnsqwDaIhleQtb4pN8=; b=O15JAGVkRs8FmHsBTcKPrPsSvrfbyXay9JQuO01OtxhIwbAXaoOcc6c7IxVf6qh+gi 7Os5vTkusuIZjbG8TdSAh2EJthTUb7RlmecNWRASj8AgSShLSqKY60KdGmBo2I4VfiKX pADiCndsp8DQkaunJIqNA1R566qnj3vHFq46c= MIME-Version: 1.0 Received: by 10.220.156.201 with SMTP id y9mr2333358vcw.22.1328211137332; Thu, 02 Feb 2012 11:32:17 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.172.37 with HTTP; Thu, 2 Feb 2012 11:32:17 -0800 (PST) In-Reply-To: <1292923023.20120202232810@serebryakov.spb.ru> References: <743722267.20120202195757@serebryakov.spb.ru> <1292923023.20120202232810@serebryakov.spb.ru> Date: Thu, 2 Feb 2012 11:32:17 -0800 X-Google-Sender-Auth: A6MdF5YiKAjHq2UTaN723gxJ9Cw Message-ID: From: Adrian Chadd To: Lev Serebryakov Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: Re: "ath0: device timeout" when environment is clear 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: Thu, 02 Feb 2012 19:32:18 -0000 Please file a bug so I don't forget. What you can do is flip on reset debugging in the driver (look at if_ath_debug.h for ATH_DEBUG_RESET) - not the HAL debugging, just the reset debugging) - that should make ath_draintxq() print out the contents of the TX queue before its drained. I'd like to see if there's anything in the TX queue when the NIC is reset. Chances are there are; I'd like to see what it is and whether it's completed or not. Adrian