Subject: Re: wi performance hack
To: NetBSD Current <current-users@NetBSD.ORG>
From: Holger Weiss <email@example.com>
Date: 07/19/2004 23:13:16
* Charles M. Hannum <firstname.lastname@example.org> [2004-07-19 19:56]:
> On Monday 19 July 2004 18:52, Holger Weiss wrote:
> > * Charles M. Hannum <email@example.com> [2004-07-19 16:49]:
> > > Here's a new patch that adds some more diagnostics. Give it a whirl and
> > > let me know what it outputs...
> > wi0: bad alloc 1f7 != 1f9, alloc 2 queue 1 start 1 queued 0 started 2
> > wi0: bad alloc 1f8 != 1f9, alloc 2 queue 2 start 2 queued 0 started 3
> > wi0: bad alloc 1f9 != 1f7, alloc 0 queue 0 start 0 queued 0 started 3
> Hm, I have the suspicion that the card is simply not transmitting packets in
> the order we told it to. What happens with the following patch instead?
Lots of 'bad alloc' errors, but nonetheless scp'ing data to another
local machine seems to work fine now.
> Also, are you using an AP, adhoc mode, or what?
I'm using an AP.
> What does "ifconfig wi0" say?
wi0: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ssid zion nwkey *****
bssid 00:80:c8:38:58:72 chan 4
media: IEEE802.11 autoselect (DS11)
inet 192.168.0.3 netmask 0xffffff00 broadcast 192.168.0.255
inet6 fe80::202:2dff:fe9d:f080%wi0 prefixlen 64 scopeid 0x8
PGP fingerprint: F1F0 9071 8084 A426 DD59 9839 59D3 F3A1 B8B5 D3DE