From owner-freebsd-stable@FreeBSD.ORG Thu Jul 20 19:25:19 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F1D1016A4DD for ; Thu, 20 Jul 2006 19:25:19 +0000 (UTC) (envelope-from vsemionov@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3568343D45 for ; Thu, 20 Jul 2006 19:25:18 +0000 (GMT) (envelope-from vsemionov@gmail.com) Received: by ug-out-1314.google.com with SMTP id m2so994965uge for ; Thu, 20 Jul 2006 12:25:17 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:user-agent:references:in-reply-to:cc:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=K6HIVaN6N/rKrh3CdYXuc+Hbma2Lywznc69BqaE2DD6qeXbZd8b6tYRNxjd2je4qu7KFAdQJqeqUrOwzS8DARfp/cVJ/i2KpYASTypSiK2WQH64CFVp6isQqpQ09q8IlwGbGsd51xUw54dwgSivwxHhTg70IIm0zYx014E16xs4= Received: by 10.67.89.5 with SMTP id r5mr2248043ugl; Thu, 20 Jul 2006 12:18:07 -0700 (PDT) Received: from neon.devian.bg ( [83.148.125.201]) by mx.gmail.com with ESMTP id e1sm759426ugf.2006.07.20.12.18.06; Thu, 20 Jul 2006 12:18:06 -0700 (PDT) From: Victor Semionov To: freebsd-stable@freebsd.org Date: Thu, 20 Jul 2006 22:08:35 +0300 User-Agent: KMail/1.9.3 References: <44BFA45C.5050108@errno.com> In-Reply-To: <44BFA45C.5050108@errno.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607202208.35435.vsemionov@gmail.com> Cc: Subject: Re: ath driver transmits frames only after a low watermark is filled X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jul 2006 19:25:20 -0000 > The original posting didn't provide any basic info so there's little > anyone can provide except wild guesses. There are debugging mechanisms > for tracing what's going on at the net80211 layer and in the driver that > have been referenced countless times in this forum. Sorry, didn't know it could be hardware-related. What info do you need?