Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 30 Apr 2013 08:41:12 -0700
From:      Adrian Chadd <adrian@freebsd.org>
To:        lev@freebsd.org
Cc:        freebsd-wireless@freebsd.org
Subject:   Re: New hardware, old problem: stuck beacon when here is WiFi traffic
Message-ID:  <CAJ-VmonQXyB_Aik-ApSmgRqT3yhD5Bqrx3zj%2BKM%2BitVmZhY0TQ@mail.gmail.com>
In-Reply-To: <124956607.20130430122459@serebryakov.spb.ru>
References:  <2810538978.20130423164137@serebryakov.spb.ru> <CAJ-Vmom4UDoz7EgdnVeQ%2BALuFFXkH9t_Uj7=FwL77S5rKfUD1g@mail.gmail.com> <1813905823.20130423184528@serebryakov.spb.ru> <CAJ-VmomhRaKODxis09MjAhUbAUOw%2B6jWBY48JpZR_JgfZZLKcQ@mail.gmail.com> <184105677.20130424002002@serebryakov.spb.ru> <CAJ-VmokVmHDXwE7S5koSqtFjPXQ_VUPhj8gfMruDM2k-DyUMPw@mail.gmail.com> <1936997795.20130424003555@serebryakov.spb.ru> <CAJ-Vmokx2QhcjcsgA-_kqjX63Vu4CLk7HkuyALautbnzp61ywQ@mail.gmail.com> <886711115.20130424004702@serebryakov.spb.ru> <CAJ-VmoksSTBC7jmC-_hvBeJFSD0k28HoZodaWdHm0AF0d1yZJg@mail.gmail.com> <6010292503.20130426001447@serebryakov.spb.ru> <CAJ-VmomUsPgHTVGaKHZ_YE%2Bu1ZOjGqrVfh2uYmvOs6gKmhnxOw@mail.gmail.com> <CAJ-VmokZBbmHbruKJV-8kvTyOTsiq5_XHnfqUYo3vO68872Q=w@mail.gmail.com> <99510815.20130426122508@serebryakov.spb.ru> <CAJ-VmoktRPbnDRbRuwA4i8w50kExs2pwD4yBawL6iOz7F4Bknw@mail.gmail.com> <CAJ-VmonCao99MOrm97tQS_f1xS9tieQfg-nQUB4APWVmdJJUBg@mail.gmail.com> <CAJ-VmokLKdwckXjzH64P=mYm9pZQzkCkJhDV4iojzJehXmJLLA@mail.gmail.com> <725880393.20130429004352@serebryakov.spb.ru> <CAJ-Vmokz=0rZM-nHtt9S%2Ba-SxRLuyP%2ByDhSAbLpr0xFS%2BpO3vA@mail.gmail.com> <187241224.20130429113623@serebryakov.spb.ru> <CAJ-Vmo=MzeJsKHfVoipPQqCRmkOHWk6p-iZNaXDwye6oG%2B76xg@mail.gmail.com> <CAJ-Vmo=b-kBDWKz=Y709kYEsYQt3ZRczCN0wG9zDRk=sR60%2Btg@mail.gmail.com> <124956607.20130430122459@serebryakov.spb.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
On 30 April 2013 01:24, Lev Serebryakov <lev@freebsd.org> 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmonQXyB_Aik-ApSmgRqT3yhD5Bqrx3zj%2BKM%2BitVmZhY0TQ>