From owner-freebsd-wireless@FreeBSD.ORG Tue Oct 4 05:04:07 2011 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 3FC65106566B; Tue, 4 Oct 2011 05:04:07 +0000 (UTC) (envelope-from bogorodskiy@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id DBB168FC12; Tue, 4 Oct 2011 05:04:06 +0000 (UTC) Received: by yxk36 with SMTP id 36so142690yxk.13 for ; Mon, 03 Oct 2011 22:04:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=Oc+oSWRfV1GX58+C8hTHSa4bzNFVbzYBEeCJfEwq8XE=; b=bnPVOm6d7dgEc7o3cE1pqrkd7sPkz7uP+eqAaejmBciNz/uusJNqQ+tUsvvoJCmTGo LKeXsSLqK3xSSH2cYekAGfacreScu2LkmZnpKRQNLb/e1S1s7AAwt1i7VVxHk4+nIVYl H3jq/JFc50vGD93uOHWugzo7xlt35P1zoUoPw= Received: by 10.236.181.135 with SMTP id l7mr4003694yhm.85.1317704646080; Mon, 03 Oct 2011 22:04:06 -0700 (PDT) Received: from reemsky ([12.204.99.163]) by mx.google.com with ESMTPS id r12sm8590060anm.13.2011.10.03.22.04.01 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 03 Oct 2011 22:04:05 -0700 (PDT) Sender: Roman Bogorodskiy Date: Mon, 3 Oct 2011 22:03:33 -0700 From: Roman Bogorodskiy To: Adrian Chadd Message-ID: <20111004050331.GA2276@reemsky> References: <20111002232848.GA1943@reemsky> <20111003024406.GC1943@reemsky> <20111003044350.GD1943@reemsky> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BXVAT5kNtrzKuDFl" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-wireless@freebsd.org Subject: Re: bwn + BETA3/ppc = very unstable 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: Tue, 04 Oct 2011 05:04:07 -0000 --BXVAT5kNtrzKuDFl Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Adrian Chadd wrote: > On 3 October 2011 12:43, Roman Bogorodskiy wrote: > > =A0Roman Bogorodskiy wrote: >=20 > > Hm, I have applied a fix similar to this one: > > > > http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/ic/bwi.c.diff?r1=3D1.= 88;r2=3D1.89 > > > > I'm not sure if it's a coincidence or not, but I had no panics since > > then. Packet loss rate are still very high - first packets go through > > without losses, but eventually loss rate goes up. >=20 > It sounds like a calibration issue. >=20 > > Now uptime is 1 hour and loss rate is about 80-85%. > > > > Any directions how can I debug this? >=20 > Well, firstly, can you please do up a patch against -HEAD? I'll commit > it to FreeBSD-HEAD ASAP and then include it in the list of things I > want to backmerge into -9. >=20 > Debugging this - I'd first isolate it to whether it is: >=20 > * TX issues; > * RX issues; > * or both TX and RX issues. >=20 > I suggest liberal use of iperf in UDP mode to TX things. It's a bit > difficult as TX'ing a one way UDP stream also involves RX'ing an ACK > from the remote end, so it isn't a 100% guaranteed way of debugging > it. But it hopefully will show it's either TX or RX related. Experimented with iperf today. The setup is the following: laptop A: G4 with bwi laptop B: i386 with ath Both connected to the same ssid. Started iperf on B in a server mode and connected from g4 -- nothing is displayed on the server side. Started iperf on A in a server mode and connected from B, got that: [ 3] Server Report: [ 3] 0.0-10.0 sec 1.15 MBytes 967 Kbits/sec 2.224 ms 71/ 893 (8%) 8% packets loss is probably not that bad. So it looks like the problem is mostly with outgoing traffic. > I'd also enable BWI_DEBUG and then flip on the relevant bits that let > you debug the attach and configuration bits (BWI_DBG_RF, > BWI_DBG_TXPOWER, BWI_DBG_ATTACH). > In fact, enable both BWI_DEBUG and BWI_DEBUG_VERBOSE in your kernel > config and rebuild. >=20 > The BWI_DBG bits are defined in if_bwivar.h. Done, here's the output of `dmesg|grep bwi0`: http://people.freebsd.org/~novel/misc/bwi_debug.txt (22K) Does it say something to you? Roman Bogorodskiy --BXVAT5kNtrzKuDFl Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iQEcBAEBAgAGBQJOipOjAAoJEMltX/4IwiJqQ3wH/2RqWZtS7pWVVDn0Wbv9QuBS HNmoYrQN6FJLOncB54r0G+8qs1WrVzlG3Z2jjWBBlGrKzMm6+Zf7pFIZBp5+AdI1 QbplhzjBLPTht7oB1moUw0KG5/oW9jD/mULKTlY7rVqe/UckSvdWkR4LL80EDcfB dn7BSB1Tni4XDq8tAfck8TchjBTBs43VX7cRtv3HIuIT3r2L0Qro/L1+4bAy1dL/ bPjTuig4eZECDMt3pnmSjczx433yzo+LjitVhpDxU+zLvY5aCyK9hwbaXmGk+YSq EdM6hiQYvMe4F/fD4maaT645BB00aeFHhR7hpXgqOYazJy7xpmH6pq25sLd96S0= =qzSq -----END PGP SIGNATURE----- --BXVAT5kNtrzKuDFl--