ath lor

[Adrian Chadd]

On 3 August 2012 22:11, PseudoCylon <moonlightakkiy at yahoo.ca> wrote:

> I have added if_printf(), so we can track down the driver to blame.
> https://gitorious.org/ieee80211/net80211/commit/4dbc79c5f832b4cdffe9966dbbeba9b1b8fd24da

Cool.

> I also added functions to revert changes when overflow (maybe too much).
> https://gitorious.org/ieee80211/net80211/commit/dc1aa81ea1a9eeb7cf1a3a1c2b8a5a8cd85e687d
>
>
>> Does it fix some/all of the LORs for you?
>>
>
> So far, node/driver LOR in iv_key_delete() seems to be gone.

This is a bit odd. I've not seen that, but you're testing with USB, right?

I just saw a LOR between a node lock and a tcpinp lock. i was doing
some iperf to an AR5416 802.11n AP running iperf locally. I've not
seen this before as I've not run a NIC in AP mode with local traffic
termination; I've only had APs do bridging.

Thanks for chasing this down. Let me know if you see the node/power or
node/scan LORs?



Adrian