From owner-freebsd-wireless@FreeBSD.ORG Thu Feb 2 21:46:58 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 9148E1065678 for ; Thu, 2 Feb 2012 21:46:58 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 4C4B18FC20 for ; Thu, 2 Feb 2012 21:46:58 +0000 (UTC) Received: by vbbfa15 with SMTP id fa15so3227404vbb.13 for ; Thu, 02 Feb 2012 13:46:57 -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=8DNkJRu55+QdeQTWOkyNRs7wmB8aVC6LmTqU50asPzA=; b=vBKSrvLWCW+hLwsFMyZkKv46j2Mut4kkaqwTqSXHlPo6uXt6vKo6pihIx0yiO477FQ 7ObLQBcRei8ZKX7MiYn4hoyGZEssVHbe/SbgPJhyp/uDVGuE56ZGeNlkPTYbup6XNIyi AQQcHh6ER6nEtzIsjaRIHMeGpazxULZKq9qSI= MIME-Version: 1.0 Received: by 10.52.26.199 with SMTP id n7mr2184607vdg.17.1328219217672; Thu, 02 Feb 2012 13:46:57 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.172.37 with HTTP; Thu, 2 Feb 2012 13:46:57 -0800 (PST) In-Reply-To: <208667374.20120203002726@serebryakov.spb.ru> References: <743722267.20120202195757@serebryakov.spb.ru> <1292923023.20120202232810@serebryakov.spb.ru> <208667374.20120203002726@serebryakov.spb.ru> Date: Thu, 2 Feb 2012 13:46:57 -0800 X-Google-Sender-Auth: v3YWimJrXPK1c7-9UkniYx9C6BU 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 21:46:58 -0000 Hi, The lack of TX buffers in that list (they're all RX buffers) means that the TX queue is empty. So, the "device timeout" is incorrect - the device didn't timeout, we just didn't queue any frames to the device but somehow the TX watchdog was set. Or, the watchdog wasn't cleared upon TX queue processing. I wonder why this is occuring. ;-) Adrian