Hi everyone,

During a few tests with madwifi-hal-testing and madwifi-free branches, I've
noticed strange packet loss at the sender.

I'm using iperf to send small (100 bytes long) UDP packets to a unicast
destination (in ad-hoc mode, without any protection) and ask purposefully for
a sending rate of 54 Mbps, just to see how fast the card is able to transmit
in that very environment.

Sometimes these packets get lost before they even have a chance to get sent by
the hardware. Iperf happily shows...

Okay, I agree with that. But first, in the case of my measurements, we can
say that the kernel should consider the "cable" as plugged, since the
destination MAC address *is* reachable. And second, how come changing the
debug flags (athdebug +xmit) changes anything at all in the way the kernel
would consider the "cable" as plugged or not?

I would like to understand what kind of side-effects are caused by the
activation of the debug flag. Note that it seems only the xmit flag causes
this change,...

Core duo (first generation) T2400 clocked at 1.83GHz on a macbook pro (also
first generation), right at this time.

Maybe I should check whether simply commenting out the DPRINTFs regarding
ATH_DEBUG_XMIT still makes the xmit debug flag change anything. I was also
wondering whether the setting of vap->iv_debug in ath_vap_create does
anything, but I doubt that function is called upon change of the debug flags
(and I'm always setting the xmit flag *after* setting the interface up).

--
If y...