On Thursday 17 August 2006 19:00, Larry Finger wrote:
The last ping before I took this output took 333 ms.
Larry
larrylap:~ # cat /debug/bcm43xx/eth1/tx_status
Last 100 logged xmitstatus blobs (Latest first):
0x00: cookie: 0xb182, flags: 0x01, cnt1: 0x00, cnt2: 0x01, seq:
On Friday 18 August 2006 13:52, Michael Buesch wrote:
Hm, I don't see anything special.
There's only one packet retried once, but even that succeed after the retry.
I would say that's normal noise.
So, what's going on there? Did you try with another card and driver, but with
the
same AP?
Michael Buesch wrote:
On Friday 18 August 2006 13:52, Michael Buesch wrote:
Hm, I don't see anything special.
There's only one packet retried once, but even that succeed after the retry.
I would say that's normal noise.
So, what's going on there? Did you try with another card and driver, but
On Friday 18 August 2006 22:05, Larry Finger wrote:
I will set up a configuration that lets me capture packets in monitor mode
using kismet and send you the capture file. The host I will be using is
for the capture is rather low powered, so it doesn't have X, but it makes a
good file server.
I am having severe performance problems with bcm43xx-softmac.
When I ping my AP (only a wireless round trip), The following
times are typical. Note the instance when it takes nearly
1/2 second! In addition, I have seen times of 10 seconds, or more.
larrylap:~ # ping -c 10 192.168.1.1
PING
On Thursday 17 August 2006 17:48, Larry Finger wrote:
I am having severe performance problems with bcm43xx-softmac.
When I ping my AP (only a wireless round trip), The following
times are typical. Note the instance when it takes nearly
1/2 second! In addition, I have seen times of 10 seconds
Michael Buesch wrote:
Can you post a dump of /debug/bcm43xx/ethX/tx_status
directly after you produced such a long delay?
The last ping before I took this output took 333 ms.
Larry
larrylap:~ # cat /debug/bcm43xx/eth1/tx_status
Last 100 logged xmitstatus blobs (Latest first):
0x00:
