Created attachment 26507 [details] dmesg with multiple p54spi failures After I stop an interface (either client or monitor), p54spi seems to get into a bad state where it yields kernel WARNINGs and fails until I rmmod and modprobe it again. I am testing this on my Nokia N810 with the current work-in-progress patchset to get it semi-usable, however the p54 driver is unmodified in logic from mainline 2.6.33.2. If the specific branch is needed for testing, please see http://gitorious.org/~Luke-Jr/linux-omap/n8x0/trees/3c6b1aff00d56b63cf52536bbb3b8c0949e7d22a
(I hope you reported that ?rndis? crash already) [ 528.930816] ------------[ cut here ]------------ [ 528.982971] WARNING: at net/wireless/mlme.c:276 ieee80211_mgd_deauth+0xc8/0x138 [mac80211]() [ 529.000488] Modules linked in: snd_pcm_oss snd_mixer_oss snd_soc_n810(+) snd_soc_omap snd_soc_omap_mcbsp snd_soc_tlv320aic3x snd_soc_core snd_pcm snd_timer snd snd_page_alloc p54spi p54common mac80211 cfg80211 [ 529.055084] [<c0032d74>] (unwind_backtrace+0x0/0xdc) from [<c0056dac>] (warn_slowpath_common+0x4c/0x80) [ 529.094268] [<c0056dac>] (warn_slowpath_common+0x4c/0x80) from [<bf02f840>] (ieee80211_mgd_deauth+0xc8/0x138 [mac80211]) [ 529.141296] [<bf02f840>] (ieee80211_mgd_deauth+0xc8/0x138 [mac80211]) from [<bf00f024>] (__cfg80211_mlme_deauth+0x110/0x11c [cfg80211]) [ 529.180328] [<bf00f024>] (__cfg80211_mlme_deauth+0x110/0x11c [cfg80211]) from [<bf01147c>] (cfg80211_conn_do_work+0x19c/0x1e0 [cfg80211]) [ 529.219726] [<bf01147c>] (cfg80211_conn_do_work+0x19c/0x1e0 [cfg80211]) from [<bf012808>] (cfg80211_conn_work+0x94/0x128 [cfg80211]) [ 529.257507] [<bf012808>] (cfg80211_conn_work+0x94/0x128 [cfg80211]) from [<c0068ef4>] (worker_thread+0x170/0x21c) [ 529.278259] [<c0068ef4>] (worker_thread+0x170/0x21c) from [<c006c528>] (kthread+0x78/0x80) [ 529.289337] [<c006c528>] (kthread+0x78/0x80) from [<c002df90>] (kernel_thread_exit+0x0/0x8) [ 529.300750] ---[ end trace a6b3be8a596fdb6a ]--- Is this the warning you are talking about? This looks more like a problem in the mac80211-stack. Do you think you can get compat-wireless working on your Nokia? compat-wireless is stack and driver backport release, which allows most users to try bleeding-edge features & fixes without migrating to a new kernel. Tarballs can be downloaded from wireless.kernel.org. If you need more help then visit our irc channel #linux-wireless @ freenode. Regards, Chr
So perhaps the warning is unrelated to the failures, dunno... Will compat-wireless help debug this problem, or are you just offering it as a "solution to use p54spi"? I want to get 2.6.33 working for ramzswap as well... (No idea what rndis is, or what's up with the crash. The log suggests it's USB-related, which is NOT vanilla)
> So perhaps the warning is unrelated to the failures, dunno... do you talk about this "failures"? [ 610.661468] wlan0: deauthenticating from 00:18:84:80:5b:8d by local choice (reason=3) means that the connection was dropped by the N810 . Are you connecting to a WPA secured network, through wpa_supplicant? If so, what wpa_supplicant back-end are available, and which one is used (and, if possible switch to nl80211)? Are any other wpa_supplicants available or can you reproduce the problem with different AP settings or a different AP? > Will compat-wireless help debug this problem, or are you just offering it as > a > "solution to use p54spi"? I want to get 2.6.33 working for ramzswap as > well... Well, I don't know if it works "now" or is still broken. But, if you can reproduce the problem with compat-wireless you should think about contacting the linux-wireless ML: linux-wireless@vger.kernel.org and report your findings. If it turns out to be fixed, then you *can* try to huntdown the chance and notify greg & linville. But that's your decision. >(No idea what rndis is, or what's up with the crash. The log suggests it's >USB-related, which is NOT vanilla) well, granted: the Oops has only limited value. Most ksyms are missing and the litte that remains could be a coincidence? [ 41.746520] PC is at pty_init+0x1fc/0x2c8 [ 41.753845] LR is at rndis_bind+0x1f4/0x48c Do you have an broadcom wlan solution connected to your n810? Maybe the syms are misinterpreted and its oopsing in mac80211/p54.
The failure I refer to is that after I manually disconnect from my AP, I cannot use the wireless anymore until I rmmod+modprobe p54spi. I use a simple WEP with basic Gentoo networking init scripts. I would imagine if this problem were general to the whole mac80211 stack, it'd be a much bigger deal and would be reported and fixed by now for one of the more common drivers. Therefore I'm inclined to conclude it must be specific to p54spi, which apparently has never been tested (it names itself "cx3110x" while the only board file using it, N8x0, expects it to be named "p54spi"). My N810's USB is connected to my development machine as an Ethernet gadget. No Broadcom is involved at all (the AP runs Atheros).
Closing as obsolete, if this is still seen with modern kernels please re-open and update