<pat-lkml@...> writes: > On my system, it doesnt' fail until > something actively scans and we receive the probe. I thinks its the same here. That would explain the following behavior. If I started the hostapd deamon in the cellar, where I can access the console server to capture the trace, I was able to start the service and the panic appeared when I stopped the hostap deamon. When I start it at the upper flor where the AP can receive many WLAN stations the kernel panic appears instantly after the start of the deamon. -- 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
