From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 30 15:41:14 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 7A03FBDA; Tue, 30 Apr 2013 15:41:14 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) by mx1.freebsd.org (Postfix) with ESMTP id DE8561AC3; Tue, 30 Apr 2013 15:41:13 +0000 (UTC) Received: by mail-wi0-f170.google.com with SMTP id l13so4346927wie.3 for ; Tue, 30 Apr 2013 08:41:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=22p+eIyAk+tlrPhVnr5OxKZk6sf3FfmZmX7hilTCfXM=; b=c58gPqGA3CXUcAmVjNNK1fXV0VoO9Q6E0CrLWS6DEffl5xyusGMdNjWNtQ5MP0u+xG BV6feeeULQP6VQiXgAdjpSPuhQPGR95z9xQRfdNWH2e7Y798sv/8m+z7GZQys0l1Ayv4 XTxxSigTSZmehXSoRtVzYIek/2pjTJH7prqqO7hkkdYaYkmm5csl2V8/7ec43fwp7lMS 6UUko07taWMdNSd8NqlXLqrkCpsDL+2ixIhvqbdVOXJtusVNmTKR/B+Rlape8z/nddN+ bUtmWlweocMlqwYPJpU1E6QXkBF6JMJ7Q3AIg7n30JFzT0BvL2T7v2BWpIaksOkyHC41 Cdyg== MIME-Version: 1.0 X-Received: by 10.194.119.33 with SMTP id kr1mr23665300wjb.36.1367336473086; Tue, 30 Apr 2013 08:41:13 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Tue, 30 Apr 2013 08:41:12 -0700 (PDT) In-Reply-To: <124956607.20130430122459@serebryakov.spb.ru> References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <725880393.20130429004352@serebryakov.spb.ru> <187241224.20130429113623@serebryakov.spb.ru> <124956607.20130430122459@serebryakov.spb.ru> Date: Tue, 30 Apr 2013 08:41:12 -0700 X-Google-Sender-Auth: rmSIB_VV2mJrAE5C5a6qfBRmRr0 Message-ID: Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic From: Adrian Chadd To: lev@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org 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, 30 Apr 2013 15:41:14 -0000 On 30 April 2013 01:24, Lev Serebryakov wrote: > Hello, Adrian. > You wrote 30 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2013 =D0=B3., 8:53:00: > > AC> Any follow-up with the latest stuff in -HEAD? I'd like to see if the > AC> hardware queue is behaving how I think it is. > Sorry, was busy yesterday. > Sources: r250041, TDMA is enabled in kernel config. Ok. > Warm-up: 120 seconds of TCP, throughput osculate between 50 and > 100Mbit/, several BAR resets, no hangs. Ok. But did it negotiate A-MPDU? > Test: 600 seconds of UDP. Throughput is 20Mbit/s. Hang on ~327s. > traffic generator stopped, single "forced bstuck" helps. > > Log attached. > > > Please, note: low throughput for UDP on these revisions. It was not > so on older revisions, before all this additional debug stuff was > added, latest good I tried was something like r249333, and I don't > remember about r249767 (but I could try, firmware image is not > removed, and I don't have images between r249333 and r249333). It's fine. We'll worry about aggregation later. So here we go: Apr 30 12:21:26 gateway kernel: ath0: ath_stoptxdma: tx queue [9] 0xd8c3000, link 0 Apr 30 12:21:26 gateway kernel: ath0: ath_tx_stopdma: tx queue [0] 0, active=3D0, hwpending=3D0, flags 0x00000000, link 0 Apr 30 12:21:26 gateway kernel: ath0: ath_tx_stopdma: tx queue [1] 0xc720ed00, active=3D0, hwpending=3D0, flags 0x00000000, link 0 Apr 30 12:21:26 gateway kernel: ath0: ath_tx_stopdma: tx queue [2] 0, active=3D0, hwpending=3D0, flags 0x00000000, link 0 Apr 30 12:21:26 gateway kernel: ath0: ath_tx_stopdma: tx queue [3] 0xd8bec00, active=3D0, hwpending=3D0, flags 0x00000000, link 0 Apr 30 12:21:26 gateway kernel: ath0: ath_tx_stopdma: tx queue [8] 0xc720d2c0, active=3D0, hwpending=3D0, flags 0x00000000, link 0 Notice how the hardware queue isn't active at all. There's frames in the TXQ and the hardware points to the next frame to transmit (but you didn't provide the whole list of frames that were in the TXQ, so I'm going on what it said before.) Hm.. Adrian