the state of SMP workingness?
James Harper
james.harper
Fri Dec 5 02:03:53 PST 2003
I'm still having problems on my SMP machine, I get messages like this...
Dec 2 19:08:01 portal kernel: wifi0: 00:50:8b:46:57:d5 auth_cb - alg=0
trans#=2 status=0 - STA authenticated
Dec 2 19:08:02 portal kernel: wifi0: 00:50:8b:46:57:d5 assoc_cb - STA
associated
Dec 2 19:08:03 portal kernel: wifi0: 00:50:8b:46:57:d5 auth_cb - alg=0
trans#=2 status=0 - STA authenticated
Dec 2 19:08:03 portal kernel: wifi0: 00:50:8b:46:57:d5 assoc_cb - STA
associated
Dec 2 19:08:38 portal kernel: wifi0: 00:50:8b:46:57:d5 auth_cb - alg=0
trans#=2 status=0 - STA authenticated
Dec 2 19:08:38 portal kernel: wifi0: 00:50:8b:46:57:d5 assoc_cb - STA
associated
Dec 2 21:09:07 portal kernel: wifi0: 00:20:e0:d0:af:8d auth_cb - alg=0
trans#=2 status=0 - STA authenticated
Dec 2 21:09:07 portal kernel: wifi0: 00:20:e0:d0:af:8d assoc_cb - STA
associated
Dec 2 21:09:23 portal kernel: handle_ap_item -
addr3(BSSID)=96:25:c1:e3:79:d5 not own MAC
Dec 2 21:14:19 portal kernel: wifi0: STA 00:20:e0:d0:af:8d did not ACK
activity poll frame
Dec 2 21:14:20 portal kernel: wifi0: sending disassociation info to STA
00:20:e0:d0:af:8d(last=7193164, jiffies=7494165)
Dec 2 21:14:21 portal kernel: wifi0: sending deauthentication info to
STA 00:20:e0:d0:af:8d(last=7193164, jiffies=7495166)
Dec 2 21:14:21 portal kernel: wifi0: Could not find STA
00:20:e0:d0:af:8d for this TX error (@7495175)
Dec 2 21:39:52 portal kernel: wifi0: detected fid change (try=0,
reg=0044): 0000 0127 0127
Dec 2 21:47:20 portal kernel: wifi0: detected fid change (try=0,
reg=0044): 0151 0151 e800
Dec 2 21:51:40 portal kernel: wifi0: hfa384x_setup_bap - timeout after
Dec 2 21:51:40 portal kernel: wifi0: prism2_tx_80211 - to BAP0 failed
Dec 2 21:51:40 portal kernel: wifi0: scheduled card reset
Dec 2 21:51:40 portal kernel: hostap_pci: wifi0: resetting card
Dec 2 21:51:40 portal kernel: wifi0: prism2_tx_80211: hw not ready -
skipping
Dec 2 21:51:40 portal last message repeated 3 times
Dec 2 21:51:40 portal kernel: prism2_hw_init: initialized in 202 ms
Dec 2 21:51:40 portal kernel: wifi0: trying to read PDA from 0x007f0000: OK
Dec 2 21:51:56 portal kernel: wifi0: detected fid change (try=0,
reg=0044): 0000 01ba 01ba
Dec 2 21:55:51 portal kernel: wifi0: detected fid change (try=0,
reg=0040): 0000 03ab 03ab
Dec 2 21:56:23 portal kernel: wifi0: detected fid change (try=0,
reg=0040): 0000 0163 0163
... on high usage. I use ssh on my laptop (XPsp1) and that's fine, but
once I start trying to copy a file or play some streaming media, the
laptop wireless card starts blinking and the server gets messages like
the above. That's on transmit from the hostap enabled device. It seems
that sending bulk data from the laptop doesn't cause so much of a problem.
00:20:e0:d0:af:8d is my laptop. no idea where the 00:20:e0:d0:af:8d
comes from, but i suspect it's a bogus address caused by corruption.
I've got firewall rules in place to detect and block unknown mac
addresses. I know that mac addresses can be spoofed but I'd still see
someone trying it on, and i'm in a rural area anyway.
It's running 2.6.0-test11 with a cvs check out a few days after
2.6.0-test11 came out. I'm thinking maybe it's not an smp problem and
that I should look elsewhere. The wireless card is bridged to the lan
via the linux bridging code, if that makes any difference.
Can anyone comment on how their smp box is performing, or where else I
should be looking? When I get some time, and if i remember, i'll do some
testing to boot in uniprocessor mode.
tia.
james
More information about the Hostap
mailing list