#429: Kernel panic after playing with VAP modes and txpower
---------------------------------+------------------------------------------
Reporter: Mister_X | Owner:
Type: defect | Status: new
Priority: major | Milestone: version 0.9.0 - move to new
codebase
Component: madwifi: other | Version: trunk
Resolution: | Keywords:
Patch_attached: 0 |
---------------------------------+------------------------------------------
Comment (by sph <[EMAIL PROTECTED]>):
I encountered very similar problem, but hadn't yet traced which of the
commands in the configuration script did it after destroying and
recreating VAP. In general, oops seems to happen after VAP is destroyed
and recreated the second time. When I comment txpower setting out there's
no oops.
Here's ksymoops dump from my embedded PPC board with kernel 2.4.31 and
madwifi r1454:
{{{
>>EIP; c90faf80 <[wlan]ieee80211_add_xr_param+f0/14c> <=====
>>GPR1; c7fcde50 <_end+7e1145c/8ee666c>
>>GPR2; c7fcc000 <_end+7e0f60c/8ee666c>
>>GPR3; c7cff0b1 <_end+7b426bd/8ee666c>
>>GPR4; c6784180 <_end+65c778c/8ee666c>
>>GPR6; c7cff078 <_end+7b42684/8ee666c>
>>GPR8; c7cff0a1 <_end+7b426ad/8ee666c>
>>GPR9; c60e817b <_end+5f2b787/8ee666c>
>>GPR21; c03bd8e8 <_end+200ef4/8ee666c>
>>GPR22; c60e8000 <_end+5f2b60c/8ee666c>
>>GPR23; c03bc180 <_end+1ff78c/8ee666c>
>>GPR25; c03bc02c <_end+1ff638/8ee666c>
>>GPR26; c60e81b5 <_end+5f2b7c1/8ee666c>
>>GPR27; c6784180 <_end+65c778c/8ee666c>
>>GPR28; c6784858 <_end+65c7e64/8ee666c>
>>GPR29; c7cff046 <_end+7b42652/8ee666c>
>>GPR30; c03bc180 <_end+1ff78c/8ee666c>
>>GPR31; c7cff0a1 <_end+7b426ad/8ee666c>
Trace; c90ed8f0 <[wlan]ieee80211_beacon_init+238/3ac>
Trace; c90edb04 <[wlan]ieee80211_beacon_alloc+a0/1d0>
Trace; c9119874 <[ath_pci]ath_beacon_alloc+5c/1fc>
Trace; c91202c8 <[ath_pci]ath_newstate+440/6e0>
Trace; c90fe42c <[wlan]ieee80211_new_state+30/74>
Trace; c90f5e14 <[wlan]ieee80211_sta_join1_tasklet+20/40>
Trace; c001a510 <tasklet_action+94/e0>
Trace; c001a2b4 <do_softirq+104/108>
Trace; c001a938 <ksoftirqd+90/b4>
Trace; c000838c <arch_kernel_thread+2c/38>
}}}
As a wild idea based on this dump, I tried to add "iwpriv wlan0 xr 0" (xr
was otherwise unset, shouldn't it already default to 0?) to the start
script and behold, no oops...
--
Ticket URL: <http://madwifi.org/ticket/429>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
