Am Sa 17 Mai 2008 01:09:57 CEST schrieb Johannes Berg
<johannes@xxxxxxxxxxxxxxxx>:
> Can you try to find out what code this corresponds to?
From objdump with line numbers, it occurs at "for (i = 0; i <
bss->supp_rates_len; i++) {" in ieee80211_compatible_rates, which I think is
entered from ieee80211_send_assoc. It seems that bss is NULL. For testing, I
have placed a WARN_ON(!bss) statement just before the for loop.
That looks plausible. Helmut, any ideas how to avoid this? Skip the
compatible rates test completely and use all rates in this situation?
Yes, that's most likely the best solution for it. If we do not have a
bss at this point we cannot adjust the rates anyway. Should I prepare
a patch?
Helmut
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
