Thread: Re: [Madwifi-devel] trunk version may cause kernel panic when only one open-auth wep
Status: Beta
Brought to you by:
otaku
From: Xiangyong C. <cc...@ms...> - 2007-07-30 07:25:54
|
Hello, =20 It seems that the bug has been fixed in trunk-version 2625. It happened in = trunk-version 2621.=20 My kernel is 2.4.20. I can try to use oops if still need to catch the scre= en. No this type of kernel panic in trunk-2625 now. Shawn > Date: Mon, 30 Jul 2007 06:54:34 +0200> Subject: Re: [Madwifi-devel] trunk= version may cause kernel panic when only one open-auth wep> From: mrenzman= n...@ma...> To: cc...@ms...> CC: mad...@li...>= > Hi.> > > Does anyone meet same scene as me?> > Probably, but it's hard t= o tell as you left out the most interesting part> (the kernel oops message)= . You might want to check the existing tickets on> madwifi.org to see wheth= er someone else already reported about a similar> problem.> > > 1, create a= th0 on dev wifi0> ...> > You should provide the exact chain of commands you= use rather than> explaining what they do.> > > And Kernel panic after 2-3 = seconds. Display"..0x..Kernel> > panic....Alee....". I think you can get th= at on your screen if do so.> > Probably, probably not. For that reason you = should also provide us with a> full dump of the resulting decoded oops mess= age.> http://madwifi.org/wiki/DevDocs/KernelOops might help here.> > Furthe= r information about your environment (such as the kernel version you> use) = would be interesting, too.> > Bye, Mike _________________________________________________________________ See what you=92re getting into=85before you go there. http://newlivehotmail.com= |
From: Xiangyong C. <cc...@ms...> - 2007-07-30 10:55:29
|
Hello, =20 Firstly, it does not appear in madwifi-ng-r2625-20070729 and only appears i= n madwifi-ng-r2621-20070728. I think it has been fixed up. =20 Secondly, I also don't think it is 2.4.20's fault. And I guess 2.4.23 could= be the same(not proved). My job is adding Atheros chip to a device which b= ased on 2.4.20 kernel. I use 2.4.20 just because the supplier has not give = me version on another kernel. But 2.4.20 has worked well with madwifi 0.9.0= , 0.9.2 and 0.9.3.1 for several months by many users. =20 Lastly, I will show what I have done at below. I am not familiar with kerne= l OOPs. I don't known how to print the panic screen and OOPs-test-module's = screen. I write down the last panic screen words and /proc/ooops screen wor= ds onto paper. Then type them here. I'll try to write clearly. =20 Thanks for your patience and help. =20 Shawn. ----------------------------------------------- insmod oops-test-0.1.0.o (not sure this filename) =20 insmod wlan.oinsmod wlan_acl.oinsmod wlan_scan_ap.oinsmod wlan_scan_sta.oin= smod wlan_wep.oinsmod wlan_xauth.oinsmod wlan_tkip.oinsmod wlan_ccmp.oinsmo= d ../ath_hal/ath_hal.oinsmod ../ath_rate/sample/ath_rate_sample.oinsmod ../= ath_rate/onoe/ath_rate_onoe.oinsmod ../ath/ath_pci.o =20 ifconfig br0 downbrctl delbr br0brctl addbr br0 =20 wlanconfig ath0 destroywlanconfig ath0 create wlandev wifi0 wlanmode ap iwc= onfig ath0 essid "ath0"iwpriv ath0 bintval 100iwconfig ath0 channel 9iwpriv= ath0 rsncaps 0iwpriv ath0 wpa 0iwpriv ath0 uapsd 0 iwpriv ath0 authmode 1 iwpriv ath0 keymgtalgs 1 iwconfig ath0 key [1] 0000000000iwconfig ath0 key [1]iwconfig ath0 key on ifconfig ath0 upifconfig ath0 0.0.0.0brctl addif br0 $1 ifconfig br0 upbrct= l show br0 =20 brctl addif br0 eth0ifconfig br0 192.168.3.20 upbrctl show br0 =20 wait for 3 seconds, then kernel panic. -------------------------------- This is panic screen. [<f888ffe4>] ieee80211_recv_mgmt[wlan] 0x2bf0(0xc033fcc0)) [<c01b8eac>] ata_output_data[kernel] 0xbc(0xc033fda4)) [<c01b8eac>] ata_output_data[kernel] 0xbc(0xc033fdb4)) [<f8943646>] ath_recv_mgmt[ath_pci] 0x5e(0xc033fdec)) [<f8889995>] ieee80211_input[wlan] 0x575(0xc033fe24)) [<c01ea7b4>] pskb_expand_head[kernel] 0xdc(0xc033fe60)) [<f888aa63>] ieee80211_iinput_all[wlan] 0x77(0xc033fea8)) [<f894c2bd>] __func__.47[ath_pci] 0x0(0xc033fec0)) [<f8943dc5>] ath_rx_tasklet[ath_pci] 0x605(0xc033fee8)) [<c01209b6>] tasklet_action[kernel] 0x46(0xc033ff44)) [<c0120885>] do_softirq[kernel] 0x95(0xc033ff50)) [<c010a9ae>] do_irq[kernel] 0xb2(0xc033ff68)) [<c010d3e8>] call_do_IRQ[kernel] 0x5(0xc033ff88)) [<c0106443>] default_idle[kernel] 0x23(0xc033ffb4)) [<c011513c>] apm_cpu_idle[kernel] 0x23(0xc033ffc0)) [<c0115098>] apm_cpu_idle[kernel] 0xa4(0xc033ffc4)) [<c0106fd0>] default_idle[kernel] 0x0(0xc033ffd0)) [<c0107072>] cpu_idle[kernel] 0x46(0xc033ffd4)) [<c0105000>] stext[kernel] 0x0(0xc033ffe0)) Code 8b 9c 90 90 00 00 00 85 db 74 20 8d b4 26 00 00 00 00 fc 8b <0> Kernel Panic: Aiee, killing interrupt handler! In interrupt handler-not syncing. -------------------------------------------------- After reboot,=20 'insmod oops-test-0.1.0'.=20 'cat /proc/oops'.=20 I am not sure the oops-test-module should be used in this way. This is the screen. =20 <5> Generation Oops... Unable to handle kernel NULL pointer dereference at address 00000000 printing eip: f88810af *pde=3D00000000 Oops:0002 oopstest nls_iso8859_1 nls_cp437 vfat fat parport_pc lp parport autofs wlan= _scan_sta ath_rate_sample ath_pci wlan ath_hal ipt_REJECT iptable_filter ip= _tables CPU:0 EIP:0060:[<f88810af>]Tainted:p EFlags:00010286 EIP is at oopstest_handle_proc[oopstest] 0x10(2.4.20-8) eax:00000016 ebx:f601d1c0 ecx:c0360d24 edx :f6273f7c esi:00000c00 edi:f2ba20000 ebp:f24bbf50 esp:f24bbf38 ds:0068 es:0068 ss:0068 Process cat(pid:3122,stack page=3Df24bb000) Stack:f8881108 c02ffa80 00000000 f2906ac0 ffffffea 00001000 00001000 c01671e4 f2ba2000 f24bbf80 00000000 00000c00 f24bbf7c 00000000 f24ba00 f601d1c0 00000000 00000000 00000000 00000000 f2906ac0 ffffffea 00001000 c0143bd7 Call Trace:[<f8881108>].rodata.str1.1 [oopstest] 0x5(0xf24bbf38)) [<c01671e4>]proc_file_read[kernel] 0xcc(0xf24bbf54)) [<c0143bd7>]sys_read[kernel] 0xa3(0xf24bbf94)) [<c01093b3>]system_call[kernel] 0x33(0xf24bbfc0)) Code: c7 05 00 00 00 00 00 00 00 00 b8 00 00 00 00 c9 c3 55 89 e5 Segmentation fault =20 _________________________________________________________________ Local listings, incredible imagery, and driving directions - all in one pla= ce! Find it! http://maps.live.com/?wip=3D69&FORM=3DMGAC01= |
From: Matthew \mentor\ B. <me...@ma...> - 2007-07-30 16:10:57
|
Xiangyong Chen wrote: > Hello, Hi, > > Firstly, it does not appear in madwifi-ng-r2625-20070729 and only > appears in madwifi-ng-r2621-20070728. I think it has been fixed up. What architecture are you running? The kernel oops you are encountering doens't really look related to any of the changesets between r2621 and r2625... <snip> mentor |
From: Michael R. <mre...@ma...> - 2007-07-30 08:16:09
|
Hi. > My kernel is 2.4.20. MadWifi does not support 2.4.x kernels before 2.4.23 (INSTALL still states that 2.4.22 or later work, but even that wouldn't match your situation). Bye, Mike |