On Mar 28, 2012, at 11:56 AM, Ben Greear wrote: > On 03/07/2012 11:45 AM, Bryan Phillippe wrote: >> >> Yes, it's a known problem. It's very reproducible for me on a non-hacked 3.3-rc1 as well: changing from AP to client mode, or setting up multiple APs, or changing from 2.4Ghz to 5Ghz all seem to trigger this warning with various stack traces. > > I'm still seeing this and related warnings on 3.3.0. At least some > of them comes from calls the 'hostapd' process makes (I printed > current->comm in the warning). > > I am not having luck writing a simple script that reproduce this, > but my application that creates a VAP and bunch of virtual station > hits it every time on startup. > > Bryan: Do you have a simple script that reproduces this problem? Hi Ben. I apologize for the delay in responding; I was out of town for a week. No, I do not. Which is frustrating, because it was happening pretty reliably for me before, but it's much more difficult to force to happen now. In the past, it was switching back and forth between AP and client mode (kill hostapd, start wpa_supplicant, for example). Or restarting hostapd frequently in different radio modes. > Johannes: Any ideas on likely causes of this problem? Might help > me zero in on the problem quicker... If I've been following the thread accurately, it looks like some headway has been made on this and some fixes checked in? I'd like to retest, if that is the case. I'm using compat-wireless trees downloaded as tarballs - do you have a version you recommend I test with? Thanks, -- -bp -- 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
