Hi,
I've been testing zd1211rw (not the mac80211 version) a bit on my
powermac because I wanted to test AP mode for bcm43xx and use my zd1211
device as a client... Thing is, I have a few problems with it already...
For one, I get lots of warnings like this (when running in monitor mode)
[ 3354.472204] drivers/net/wireless/zd1211rw/zd_chip.c:1467 ASSERT r >= 0 VIOLATED!
[ 3354.472212] Call Trace:
[ 3354.472222] [C000000001BCF6D0] [C00000000000F330] .show_stack+0x68/0x1b0 (unreliable)
[ 3354.472247] [C000000001BCF770] [D000000000444F04] .zd_rx_qual_percent+0x164/0x200 [zd1211rw]
[ 3354.472281] [C000000001BCF7F0] [D0000000004470CC] .do_rx+0x198/0x5c0 [zd1211rw]
[ 3354.472307] [C000000001BCF8D0] [C000000000049978] .tasklet_action+0xd0/0x188
[ 3354.472323] [C000000001BCF970] [C0000000000495C4] .__do_softirq+0xa8/0x164
Secondly, also in monitor mode, I see a huge number of invalid packets.
I can't believe there's that much noise here, and even then I shouldn't
be seeing these packets. And I mean a HUGE number, in just 10 seconds I
captured around 3700 packets! I'm pretty sure that the CRC and/or PLCP
check isn't enabled since I'm seeing things like
Beacon frame,SN=2219,FN=0,BI=100, SSID: "p\025Echel"
while the AP is actually named "puschel" (don't ask me, just someone in
my vicinity). I hope it doesn't happen in a normal (managed) mode.
johannes
On Tue, 2007-03-06 at 09:15 -0800, Maxime Austruy wrote:
> fyi, this looks like:
> http://bugzilla.kernel.org/show_bug.cgi?id=7752
Yeah, looks like. Do you want me to open another bug report for the
filter-not -working issue?
johannes
On Tue, Mar 06, 2007 at 02:01:46AM +0100, Johannes Berg wrote:
> Hi,
>
> I've been testing zd1211rw (not the mac80211 version) a bit on my
> powermac because I wanted to test AP mode for bcm43xx and use my zd1211
> device as a client... Thing is, I have a few problems with it already...
>
> For one, I get lots of warnings like this (when running in monitor mode)
>
> [ 3354.472204] drivers/net/wireless/zd1211rw/zd_chip.c:1467 ASSERT r >= 0 VIOLATED!
> [ 3354.472212] Call Trace:
> [ 3354.472222] [C000000001BCF6D0] [C00000000000F330] .show_stack+0x68/0x1b0 (unreliable)
> [ 3354.472247] [C000000001BCF770] [D000000000444F04] .zd_rx_qual_percent+0x164/0x200 [zd1211rw]
> [ 3354.472281] [C000000001BCF7F0] [D0000000004470CC] .do_rx+0x198/0x5c0 [zd1211rw]
> [ 3354.472307] [C000000001BCF8D0] [C000000000049978] .tasklet_action+0xd0/0x188
> [ 3354.472323] [C000000001BCF970] [C0000000000495C4] .__do_softirq+0xa8/0x164
Johannes,
fyi, this looks like:
http://bugzilla.kernel.org/show_bug.cgi?id=7752
Thanks,
Max
On Thu, 2007-03-08 at 10:58 -0500, Daniel Drake wrote:
> >> fyi, this looks like:
> >> http://bugzilla.kernel.org/show_bug.cgi?id=7752
>
> It would be useful if someone could post results from the patch there. I
> do not see the issue on any of my devices.
Oh, I hadn't seen the patch before. I don't think I'll get to it soon
though.
johannes
Johannes Berg wrote:
> On Tue, 2007-03-06 at 09:15 -0800, Maxime Austruy wrote:
>
>> fyi, this looks like:
>> http://bugzilla.kernel.org/show_bug.cgi?id=7752
It would be useful if someone could post results from the patch there. I
do not see the issue on any of my devices.
> Yeah, looks like. Do you want me to open another bug report for the
> filter-not -working issue?
Yes please.
Daniel