Re: ath0 issue
- From: JoaoBR <joao@xxxxxxxxxxxx>
- Date: Sun, 12 Nov 2006 18:42:19 -0200
On Sunday 12 November 2006 17:32, Lamont Granquist wrote:
i saw the same behavior where tx packets would tend to
spool up and buffer. here's the output of one second
where a bunch of spooled up packets were sent alont with
the previous second and following second and with a note
on how long it had been before any ath*tx* routine had
been called. hopefully this is useful for debugging --
i've got copious amounts of debugging logs, so let me
know if i've guessed wrongly about what is relevant...
yes and when you then look at athstats you probably see the
tx buffer is filled up until the interface stops
transmitting sooner or later
It seems to me that the tx buffer never becomes empty
anymore when the interface raised once "tx stopped because
out of txbuffer" until it then completly stops tx, if you
are present when it happens you can get it back with
ifconfig down/up but when you are late you need to reset it
or reboot. It does not matter how high you set the
ath.txbuf
it seems the problem comes up later when setting higher
values for dev.ath.0.acktimeout and dev.ath.0.ctstimeout
but I am still testing
--
João
A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura.
Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br
_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"
- References:
- ath0 issue
- From: Lamont Granquist
- Re: ath0 issue
- From: Lamont Granquist
- ath0 issue
- Prev by Date: Re: sio driver sucks
- Next by Date: Re: ath0 issue
- Previous by thread: Re: ath0 issue
- Next by thread: Re: ath0 issue
- Index(es):
Relevant Pages
|