Re: [OpenWrt-Devel] kernel panic on p54pci insertion on mipsel
Chr schrieb: (...) >> Code; c0071828 >> <_PC>: >> Code; c0071828 >>0: 8ca40150 lw a0,336(a1) >> Code; c007182c >>4: 24020001 li v0,1 >> Code; c0071830 >>8: afa20010 sw v0,16(sp) >> Code; c0071834<= >>c: 8c820078 lw v0,120(a0) <= >> Code; c0071838 >> 10: 00a08021 moves0,a1 >> Code; c007183c >> 14: 30420200 andiv0,v0,0x200 >> Code; c0071840 >> 18: 1440009f bnezv0,298 <_PC+0x298> >> Code; c0071844 >> 1c: 8cb10160 lw s1,352(a1) >> Code; c0071848 >> 20: 8c820010 lw v0,16(a0) >> >> Kernel panic - not syncing: Fatal exception in interrupt >> > > Ouch?! Are you sure your hardware isn't damaged? > Can you please try another wifi card in your mips, > or "test" the wifi card in a x86? I took it from a IXP (arm) router, where it worked. I'll verify if it works on x86, though. -- Tomasz Chmielewski http://wpkg.org ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] kernel panic on p54pci insertion on mipsel
Michael Buesch schrieb: > On Wednesday 06 August 2008 22:28:32 Tomasz Chmielewski wrote: >> Johannes Berg schrieb: Call Trace:[<8018405c>][<8001d2bc>][<8004cc30>][<8004e0dc>][<80002ca4>][<8001c310>][<80001e54>][<80002ca4>][<80125850>][][][] Code: 8ca40150 24020001 afa20010 <8c820078> 00a08021 30420200 1440009f 8cb10160 8c820010 Kernel panic - not syncing: Fatal exception in interrupt >>> Please remove me from the CC list, at least until you've discovered >>> ksymoops. >> Sorry for that. Is this one more helpful? > > No, you seem to be using the wrong System.map and/or vmlinux image. > Read the manpage, please. Why do you think they are wrong? Both files (System.map and vmlinux image) come from the kernel which panicked. It could be I compiled the kernel by adding one module (no compiled-in the kernel changes) to its .config - without flashing the kernel. Would it make a difference to System.map and/or vmlinux image and ksymoops? If so, here is one more try, where everything should be proper. This panic was made by simply doing the below ~50 times in a loop, and is reproducible: rmmod prism54 modprobe prism54 ifconfig eth2 up If it's still totally wrong, please take my apologies, but I've no idea what I may be doing wrong. # ksymoops -K -v vmlinux-2.6.25.12 < oops2 ksymoops 2.4.11 on mips 2.6.25.12. Options used -v vmlinux-2.6.25.12 (specified) -K (specified) -l /proc/modules (default) -o /lib/modules/2.6.25.12/ (default) -m /boot/System.map-2.6.25.12 (default) No modules in ksyms, skipping objects No ksyms, skipping lsmod Data bus error, epc == c0084834, ra == 8004cc30 Cpu 0 $ 0 : 10009800 0001 0001 $ 4 : c0054000 81df0b60 $ 8 : 1000d800 101f 802e 802f $12 : 802e 0005 802e4588 81c3d950 $16 : 81dea280 0080 0001 0006 $20 : c0054078 0001 7fd019e8 $24 : 0001 2abb4fb0 $28 : 80ec 80ec1c50 7fd0199c 8004cc30 Hi: 00020200 Lo: 05858000 epc : c0084834 Not tainted Using defaults from ksymoops -t elf32-tradlittlemips -a mips:3000 Cause : 0080401c 0001 8004cc30 802a1a90 0006 81df0b60 81df0800 802a1a90 0006 81df0b60 81df0800 8004e0dc 0005 802e4588 81c3d950 802e4df4 4000 c0054000 80001e54 8914 0400 c881 802a 80002ca4 0001 7fd019e8 80125850 80023de8 802e4df4 Call Trace:[<8018405c>][<8004cc30>][<8001d2bc>][<8004cc30>][<8004e0dc>][<80001e54>][<80002ca4>][<80125850>][<80023de8>][][][<80001e54>] Code: 8ca40150 24020001 afa20010 <8c820078> 00a08021 30420200 1440009f 8cb10160 8c820010 >>RA; 8004cc30 >>$12; 802e >>$14; 802e4588 >>$31; 8004cc30 >>PC; c0084834<= Trace; 8018405c Trace; 8004cc30 Trace; 8001d2bc Trace; 8004cc30 Trace; 8004e0dc Trace; 80001e54 Trace; 80002ca4 Trace; 80125850 Trace; 80023de8 Trace; c0083c00 Trace; c0083c98 Trace; 80001e54 Code; c0084828 <_PC>: Code; c0084828 0: 8ca40150 lw a0,336(a1) Code; c008482c 4: 24020001 li v0,1 Code; c0084830 8: afa20010 sw v0,16(sp) Code; c0084834<= c: 8c820078 lw v0,120(a0) <= Code; c0084838 10: 00a08021 moves0,a1 Code; c008483c 14: 30420200 andiv0,v0,0x200 Code; c0084840 18: 1440009f bnezv0,298 <_PC+0x298> Code; c0084844 1c: 8cb10160 lw s1,352(a1) Code; c0084848 20: 8c820010 lw v0,16(a0) Kernel panic - not syncing: Fatal exception in interrupt -- Tomasz Chmielewski http://wpkg.org ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] kernel panic on p54pci insertion on mipsel
On Wednesday 06 August 2008 22:28:32 Tomasz Chmielewski wrote: > Johannes Berg schrieb: > >> Call > >> Trace:[<8018405c>][<8001d2bc>][<8004cc30>][<8004e0dc>][<80002ca4>][<8001c310>][<80001e54>][<80002ca4>][<80125850>][][][] > >> > >> Code: 8ca40150 24020001 afa20010 <8c820078> 00a08021 30420200 1440009f > >> 8cb10160 8c820010 > >> Kernel panic - not syncing: Fatal exception in interrupt > > > > Please remove me from the CC list, at least until you've discovered > > ksymoops. > > Sorry for that. Is this one more helpful? No, you seem to be using the wrong System.map and/or vmlinux image. Read the manpage, please. -- Greetings Michael. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] kernel panic on p54pci insertion on mipsel
Johannes Berg schrieb: >> Call >> Trace:[<8018405c>][<8001d2bc>][<8004cc30>][<8004e0dc>][<80002ca4>][<8001c310>][<80001e54>][<80002ca4>][<80125850>][][][] >> >> Code: 8ca40150 24020001 afa20010 <8c820078> 00a08021 30420200 1440009f >> 8cb10160 8c820010 >> Kernel panic - not syncing: Fatal exception in interrupt > > Please remove me from the CC list, at least until you've discovered > ksymoops. Sorry for that. Is this one more helpful? # ksymoops -v vmlinux-2.6.25.12 < oops ksymoops 2.4.11 on mips 2.6.25.12. Options used -v vmlinux-2.6.25.12 (specified) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.6.25.12/ (default) -m /boot/System.map-2.6.25.12 (default) Error (regular_file): read_ksyms stat /proc/ksyms failed ksymoops: No such file or directory No modules in ksyms, skipping objects No ksyms, skipping lsmod Data bus error, epc == c0071834, ra == 8004cc30 Cpu 0 $ 0 : 10009800 0001 0001 $ 4 : c0054000 80de8b60 $ 8 : 1000d800 101f 802e 802f $12 : 802e 0006 802e4588 81c3d508 $16 : 81d69880 0080 0001 0006 $20 : c0054078 0001 7fc25828 $24 : 0001 2abb4fb0 $28 : 80de 80de1c50 7fc258bc 8004cc30 Hi: 00020200 Lo: 05858000 epc : c0071834 Not tainted Using defaults from ksymoops -t elf32-tradlittlemips -a mips:3000 Cause : 0080401c 0001 8004cc30 802a1a90 0006 80de8b60 80de8800 802a1a90 0006 80de8b60 80de8800 8004e0dc 80002ca4 81d17e00 10009801 8001c310 4000 c0054000 80001e54 1000d800 0400 468c 802a 80002ca4 0001 7fc25828 80125850 0006 802e4df4 Call Trace:[<8018405c>][<8001d2bc>][<8004cc30>][<8004e0dc>][<80002ca4>][<8001c310>][<80001e54>][<80002ca4>][<80125850>][][][] Code: 8ca40150 24020001 afa20010 <8c820078> 00a08021 30420200 1440009f 8cb10160 8c820010 >>RA; 8004cc30 >>$12; 802e >>$14; 802e4588 >>$31; 8004cc30 >>PC; c0071834<= Trace; 8018405c Trace; 8001d2bc Trace; 8004cc30 Trace; 8004e0dc Trace; 80002ca4 Trace; 8001c310 <__wake_up_common+54/bc> Trace; 80001e54 Trace; 80002ca4 Trace; 80125850 Trace; c0070c00 Trace; c0070c98 Trace; c007118c Code; c0071828 <_PC>: Code; c0071828 0: 8ca40150 lw a0,336(a1) Code; c007182c 4: 24020001 li v0,1 Code; c0071830 8: afa20010 sw v0,16(sp) Code; c0071834<= c: 8c820078 lw v0,120(a0) <= Code; c0071838 10: 00a08021 moves0,a1 Code; c007183c 14: 30420200 andiv0,v0,0x200 Code; c0071840 18: 1440009f bnezv0,298 <_PC+0x298> Code; c0071844 1c: 8cb10160 lw s1,352(a1) Code; c0071848 20: 8c820010 lw v0,16(a0) Kernel panic - not syncing: Fatal exception in interrupt 1 error issued. Results may not be reliable. -- Tomasz Chmielewski http://wpkg.org ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] kernel panic on p54pci insertion on mipsel
Johannes Berg schrieb: >> Call >> Trace:[<8018405c>][<8001d2bc>][<8004cc30>][<8004e0dc>][<80002ca4>][<8001c310>][<80001e54>][<80002ca4>][<80125850>][][][] >> >> Code: 8ca40150 24020001 afa20010 <8c820078> 00a08021 30420200 1440009f >> 8cb10160 8c820010 >> Kernel panic - not syncing: Fatal exception in interrupt > > Please remove me from the CC list, at least until you've discovered > ksymoops. Sorry for that. Is this one more helpful? # ksymoops -v vmlinux-2.6.25.12 < oops ksymoops 2.4.11 on mips 2.6.25.12. Options used -v vmlinux-2.6.25.12 (specified) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.6.25.12/ (default) -m /boot/System.map-2.6.25.12 (default) Error (regular_file): read_ksyms stat /proc/ksyms failed ksymoops: No such file or directory No modules in ksyms, skipping objects No ksyms, skipping lsmod Data bus error, epc == c0071834, ra == 8004cc30 Cpu 0 $ 0 : 10009800 0001 0001 $ 4 : c0054000 80de8b60 $ 8 : 1000d800 101f 802e 802f $12 : 802e 0006 802e4588 81c3d508 $16 : 81d69880 0080 0001 0006 $20 : c0054078 0001 7fc25828 $24 : 0001 2abb4fb0 $28 : 80de 80de1c50 7fc258bc 8004cc30 Hi: 00020200 Lo: 05858000 epc : c0071834 Not tainted Using defaults from ksymoops -t elf32-tradlittlemips -a mips:3000 Cause : 0080401c 0001 8004cc30 802a1a90 0006 80de8b60 80de8800 802a1a90 0006 80de8b60 80de8800 8004e0dc 80002ca4 81d17e00 10009801 8001c310 4000 c0054000 80001e54 1000d800 0400 468c 802a 80002ca4 0001 7fc25828 80125850 0006 802e4df4 Call Trace:[<8018405c>][<8001d2bc>][<8004cc30>][<8004e0dc>][<80002ca4>][<8001c310>][<80001e54>][<80002ca4>][<80125850>][][][] Code: 8ca40150 24020001 afa20010 <8c820078> 00a08021 30420200 1440009f 8cb10160 8c820010 >>RA; 8004cc30 >>$12; 802e >>$14; 802e4588 >>$31; 8004cc30 >>PC; c0071834<= Trace; 8018405c Trace; 8001d2bc Trace; 8004cc30 Trace; 8004e0dc Trace; 80002ca4 Trace; 8001c310 <__wake_up_common+54/bc> Trace; 80001e54 Trace; 80002ca4 Trace; 80125850 Trace; c0070c00 Trace; c0070c98 Trace; c007118c Code; c0071828 <_PC>: Code; c0071828 0: 8ca40150 lw a0,336(a1) Code; c007182c 4: 24020001 li v0,1 Code; c0071830 8: afa20010 sw v0,16(sp) Code; c0071834<= c: 8c820078 lw v0,120(a0) <= Code; c0071838 10: 00a08021 moves0,a1 Code; c007183c 14: 30420200 andiv0,v0,0x200 Code; c0071840 18: 1440009f bnezv0,298 <_PC+0x298> Code; c0071844 1c: 8cb10160 lw s1,352(a1) Code; c0071848 20: 8c820010 lw v0,16(a0) Kernel panic - not syncing: Fatal exception in interrupt 1 error issued. Results may not be reliable. -- Tomasz Chmielewski http://wpkg.org ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] kernel panic on p54pci insertion on mipsel
Chr schrieb: > On Wednesday 06 August 2008 21:02:24 Tomasz Chmielewski wrote: >> Luis R. Rodriguez schrieb: >> >> (...) >> - doesn't work with prism54.ko module (similar messages to http://marc.info/?l=linux-wireless&m=120250829717134&w=2) >>> We need more details, or do you get *exactly* the same error messages? >>> >>> "Out of memory, cannot handle oid" comes up after a failed kmalloc() >>> while trying to handle an interrupt and management frame (not 802.11 >>> frame) from the firmware. From that archived mailing list though the >>> oid 0x080002ff is mentioned and... well prism54 doesn't know what that >>> is. I wonder if the firmware is triggering random interrupts with >>> bogus oids. >>> >>> If you can provide a complete log it can help. Also in your previous >>> posts I see you mentioned you were working with different firmwares. >>> 1.0.4.3.arm should *only* be used with prism54. You may also want to >>> try an older firmware version than 1.0.4.3.arm, this one came from >>> 3com cards. >> Is older firmware available anywhere online? > you can get lots of fullmac & softmac firmwares right here: > http://daemonizer.de/prism54/prism54-fw/ I get "Out of memory, cannot handle oid" with all 1.x.x.x firmware and prism54 module. I was renaming 1.x.x.x to isl3890, loading module, ifconfig up, removing module - from the highest 1.x.x.x version down to 0.8.0.0, which made the kernel panic after these series of rmmods, modprobes and ifconfigs. The panic can be reproduced if you do these ifconfig up series several times in a row. # ifconfig eth2 up Data bus error, epc == c0071834, ra == 8004cc30 Oops[#1]: Cpu 0 $ 0 : 10009800 0001 0001 $ 4 : c0054000 80de8b60 $ 8 : 1000d800 101f 802e 802f $12 : 802e 0006 802e4588 81c3d508 $16 : 81d69880 0080 0001 0006 $20 : c0054078 0001 7fc25828 $24 : 0001 2abb4fb0 $28 : 80de 80de1c50 7fc258bc 8004cc30 Hi: 00020200 Lo: 05858000 epc : c0071834 Not tainted ra: 8004cc30 Status: 10009803KERNEL EXL IE Cause : 0080401c PrId : 00029006 (Broadcom BCM3302) Modules linked in: prism54 [last unloaded: prism54] Process ifconfig (pid: 1329, threadinfo=80de, task=81edb998) Stack : 8018405c 81c02805 0001 802e4558 0001 8001d2bc 81d69880 0080 0001 8004cc30 802a1a90 0006 80de8b60 80de8800 802a1a90 0006 80de8b60 80de8800 8004e0dc 80002ca4 81d17e00 10009801 8001c310 4000 c0054000 80001e54 1000d800 0400 468c 802a 80002ca4 0001 7fc25828 80125850 0006 802e4df4 ... Call Trace:[<8018405c>][<8001d2bc>][<8004cc30>][<8004e0dc>][<80002ca4>][<8001c310>][<80001e54>][<80002ca4>][<80125850>][][][] Code: 8ca40150 24020001 afa20010 <8c820078> 00a08021 30420200 1440009f 8cb10160 8c820010 Kernel panic - not syncing: Fatal exception in interrupt -- Tomasz Chmielewski http://wpkg.org ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Etrax support
> Manually disable ide support on make menuconfig fix the problem. > When a compile error arise post/read tail of "make V=99" It's not enabled by default, anyway i'm trying to get the trunk again...but openwrt.org is down atm ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Etrax support
1) openwrt down a.t.m., anyway 2) Should your patch be renamed in "987something.patch"? and placed where EXACTLY? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] kernel panic on p54pci insertion on mipsel
Luis R. Rodriguez schrieb: (...) >> - doesn't work with prism54.ko module (similar messages to >> http://marc.info/?l=linux-wireless&m=120250829717134&w=2) > > We need more details, or do you get *exactly* the same error messages? > > "Out of memory, cannot handle oid" comes up after a failed kmalloc() > while trying to handle an interrupt and management frame (not 802.11 > frame) from the firmware. From that archived mailing list though the > oid 0x080002ff is mentioned and... well prism54 doesn't know what that > is. I wonder if the firmware is triggering random interrupts with > bogus oids. > > If you can provide a complete log it can help. Also in your previous > posts I see you mentioned you were working with different firmwares. > 1.0.4.3.arm should *only* be used with prism54. You may also want to > try an older firmware version than 1.0.4.3.arm, this one came from > 3com cards. Is older firmware available anywhere online? This is a complete log (kernel outputs pasted below each command, kernel used is 2.6.25.12 with OpenWRT patches), firmware used is 1.0.4.3.arm - messages are essentially the same as the last time I tried with 2.6.23.x: # modprobe prism54 Loaded prism54 driver, version 1.2 PCI: Fixing up device :00:02.0 # dmesg -c Loaded prism54 driver, version 1.2 PCI: Fixing up device :00:02.0 # ifconfig eth2 up eth2: Out of memory, cannot handle oid 0x030002ff eth2: timeout waiting for mgmt response eth2: mgt_commit_list: failure. oid=1002 err=-145 eth2: Out of memory, cannot handle oid 0x0012 eth2: timeout waiting for mgmt response eth2: mgt_commit_list: failure. oid=1205 err=-145 eth2: Out of memory, cannot handle oid 0x0712 eth2: timeout waiting for mgmt response eth2: mgt_commit_list: failure. oid=ff020003 err=-145 eth2: interface reset failure prism54: Your card/socket may be faulty, or IRQ line too busy :( SIOCSIFFLAGS: Connection timed out # dmesg -c eth2: resetting device... eth2: uploading firmware... eth2: firmware version: 1.0.4.3 eth2: firmware upload complete eth2: Out of memory, cannot handle oid 0x030002ff eth2: timeout waiting for mgmt response 250, triggering device eth2: timeout waiting for mgmt response 225, triggering device eth2: timeout waiting for mgmt response 200, triggering device eth2: timeout waiting for mgmt response 175, triggering device eth2: timeout waiting for mgmt response 150, triggering device eth2: timeout waiting for mgmt response 125, triggering device eth2: timeout waiting for mgmt response 100, triggering device eth2: timeout waiting for mgmt response 75, triggering device eth2: timeout waiting for mgmt response 50, triggering device eth2: timeout waiting for mgmt response 25, triggering device eth2: timeout waiting for mgmt response eth2: mgt_commit_list: failure. oid=1002 err=-145 eth2: Out of memory, cannot handle oid 0x0012 eth2: timeout waiting for mgmt response 250, triggering device eth2: timeout waiting for mgmt response 225, triggering device eth2: timeout waiting for mgmt response 200, triggering device eth2: timeout waiting for mgmt response 175, triggering device eth2: timeout waiting for mgmt response 150, triggering device eth2: timeout waiting for mgmt response 125, triggering device eth2: timeout waiting for mgmt response 100, triggering device eth2: timeout waiting for mgmt response 75, triggering device eth2: timeout waiting for mgmt response 50, triggering device eth2: timeout waiting for mgmt response 25, triggering device eth2: timeout waiting for mgmt response eth2: mgt_commit_list: failure. oid=1205 err=-145 eth2: Out of memory, cannot handle oid 0x0712 eth2: timeout waiting for mgmt response 250, triggering device eth2: timeout waiting for mgmt response 225, triggering device eth2: timeout waiting for mgmt response 200, triggering device eth2: timeout waiting for mgmt response 175, triggering device eth2: timeout waiting for mgmt response 150, triggering device eth2: timeout waiting for mgmt response 125, triggering device eth2: timeout waiting for mgmt response 100, triggering device eth2: timeout waiting for mgmt response 75, triggering device eth2: timeout waiting for mgmt response 50, triggering device eth2: timeout waiting for mgmt response 25, triggering device eth2: timeout waiting for mgmt response eth2: mgt_commit_list: failure. oid=ff020003 err=-145 eth2: mgt_commit: failure eth2: interface reset failure prism54: Your card/socket may be faulty, or IRQ line too busy :( -- Tomasz Chmielewski http://wpkg.org ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] R: Re: Linking problem while building package
Hi Roberto,In the makefile.linux you could replace $(CC) with $(CXX). Presently the build configuration of openwrt(CC=uclibc-gcc) is overriding mgen (CC=g++). As per rules.mk the build flag CXX is uclibc-g++ which might resolve the issue you are facing.I am really a newbie to this forum, please pardon me for the choice of adjectives :) . As per my analysis of your issue , I deduced the solution could be as simple as substituting the CC with CXX in makefile.linux in MGEN source.Following is the file and specific lines which gives that info:trunk/rules.mk:84: CC=$(TARGET_CC) \trunk/rules.mk:86: CXX=$(TARGET_CROSS)g++ \Regards,Karthik Venkateswaran[EMAIL PROTECTED] wrote: -To: OpenWrt Development List From: Roberto Riggio <[EMAIL PROTECTED]>Sent by: [EMAIL PROTECTED]Date: 08/06/2008 11:00AMcc: OpenWrt Development List Subject: [OpenWrt-Devel] R: Re: Linking problem while building package- "Karthik Venkateswaran" <[EMAIL PROTECTED]> ha scritto:> A simple solution is to use $(CXX) instead of $(CC) in MGEN source > Makefile.Sorry for the very simple question, but how do I tell kamikaze to use g++in the package Makefile. The mgen makefile already spacifies g++ but it is ignored by kamikaze. > Karthik VenkateswaranR.___openwrt-devel mailing listopenwrt-devel@lists.openwrt.orghttp://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel__ This email may contain confidential or privileged information for the intended recipient(s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system. Thanks __ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] fix for ipkg-utils (using wrong 'find' on FreeBSD)
ipkg-build calls 'find' directly irrespective of the platform,
this causes failure in case gnu-find specific options are used
(such as "-uid +99").
The attached diff, which creates tools/ipkg-utils/patches/160-find.patch,
fixes the problem by using gfind is available. Again, this is similar
to what is done in include/host.mk
--- /dev/null 2008-08-06 15:11:00.0 +0200
+++ openwrt/tools/ipkg-utils/patches/160-find.patch 2008-08-06
15:08:55.0 +0200
@@ -0,0 +1,39 @@
+--- /tmp/ipkg-build2008-08-01 09:36:41.0 +0200
ipkg-utils-1.7/ipkg-build 2008-08-06 15:04:52.0 +0200
+@@ -10,7 +10,8 @@
+ set -e
+
+ version=1.0
+-
++FIND="$(which gfind)"
++FIND="${FIND:-$(which find)}"
+ TAR="${TAR:-$(which tar)}"
+
+ ipkg_extract_value() {
+@@ -49,7 +50,7 @@
+
+ PKG_ERROR=0
+
+- cvs_dirs=`find . -name 'CVS'`
++ cvs_dirs=`$FIND . -name 'CVS'`
+ if [ -n "$cvs_dirs" ]; then
+ if [ "$noclean" = "1" ]; then
+ echo "*** Warning: The following CVS directories where found.
+@@ -62,7 +63,7 @@
+ fi
+ fi
+
+- tilde_files=`find . -name '*~'`
++ tilde_files=`$FIND . -name '*~'`
+ if [ -n "$tilde_files" ]; then
+ if [ "$noclean" = "1" ]; then
+ echo "*** Warning: The following files have names ending in '~'.
+@@ -75,7 +76,7 @@
+ fi
+ fi
+
+- large_uid_files=`find . -uid +99 || true`
++ large_uid_files=`$FIND . -uid +99 || true`
+
+ if [ "$ogargs" = "" ] && [ -n "$large_uid_files" ]; then
+ echo "*** Warning: The following files have a UID greater than
99.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] fix for scripts/feeds on FreeBSD
Description:
scripts/feeds calls 'make' irrespective of the platform it is
running on. The attached patch changes the code to use gmake
if available (which should cover non-linux platforms, and is
the same logic used to adapt other programs in include/host.mk)
cheers
luigi
Index: scripts/feeds
===
--- scripts/feeds (revision 12201)
+++ scripts/feeds (working copy)
@@ -11,6 +11,10 @@
chdir "$FindBin::Bin/..";
$ENV{TOPDIR}=getcwd();
+my $mk=`which gmake`; # select the right 'make' program
+chomp($mk);# trim trailing newline
+$mk or $mk = "make"; # default to 'make'
+
my @feeds;
my %build_packages;
my %installed;
@@ -48,8 +52,8 @@
-d "./feeds/$name.tmp" or mkdir "./feeds/$name.tmp" or return 1;
-d "./feeds/$name.tmp/info" or mkdir "./feeds/$name.tmp/info" or return
1;
- system("make -s prepare-mk TMP_DIR=\"$ENV{TOPDIR}/feeds/$name.tmp\"");
- system("make -s -f include/scan.mk IS_TTY=1 SCAN_TARGET=\"packageinfo\"
SCAN_DIR=\"feeds/$name\" SCAN_NAME=\"package\"
SCAN_DEPS=\"$ENV{TOPDIR}/include/package*.mk\" SCAN_DEPTH=4 SCAN_EXTRA=\"\"
TMP_DIR=\"$ENV{TOPDIR}/feeds/$name.tmp\"");
+ system("$mk -s prepare-mk TMP_DIR=\"$ENV{TOPDIR}/feeds/$name.tmp\"");
+ system("$mk -s -f include/scan.mk IS_TTY=1 SCAN_TARGET=\"packageinfo\"
SCAN_DIR=\"feeds/$name\" SCAN_NAME=\"package\"
SCAN_DEPS=\"$ENV{TOPDIR}/include/package*.mk\" SCAN_DEPTH=4 SCAN_EXTRA=\"\"
TMP_DIR=\"$ENV{TOPDIR}/feeds/$name.tmp\"");
system("ln -sf $name.tmp/.packageinfo ./feeds/$name.index");
return 0;
@@ -117,7 +121,7 @@
}
sub get_installed() {
- system("make -s prepare-tmpinfo");
+ system("$mk -s prepare-tmpinfo");
clear_packages();
parse_package_metadata("./tmp/.packageinfo");
%installed = %package;
@@ -299,9 +303,9 @@
# refresh the config
if ($default) {
- system("make oldconfig CONFDEFAULT=\"$default\" Config.in
>/dev/null 2>/dev/null");
+ system("$mk oldconfig CONFDEFAULT=\"$default\" Config.in
>/dev/null 2>/dev/null");
} else {
- system("make defconfig Config.in >/dev/null 2>/dev/null");
+ system("$mk defconfig Config.in >/dev/null 2>/dev/null");
}
}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Etrax support
Claudio wrote: >>> Can someone test? >> Works for me, except for kernel compilation I had to apply this patch.. > @Hinko Kocevar > Why you remove these LD/OBJCOPYFLAG option? The reason is because otherwise ld fails with unknown option 'criself'.. > Is board now flashable and bootable with this patch? Yes it is bootable. I use similar arch/cris/arch-v10/Makefile for our products. Regards Hinko -- ČETRTA POT, d.o.o., Kranj Planina 3 4000 Kranj Slovenia, Europe Tel. +386 (0) 4 280 66 03 E-mail: [EMAIL PROTECTED] Http: www.cetrtapot.si ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Etrax support
Hi 2008/8/6, Hinko Kocevar <[EMAIL PROTECTED]>: > MichelinoK wrote: >> I've just downloaded the latest svn trunk...and etrax target cannot be >> compiled anymore... @MichelinoK: Manually disable ide support on make menuconfig fix the problem. When a compile error arise post/read tail of "make V=99" >> Can someone test? > > Works for me, except for kernel compilation I had to apply this patch.. @Hinko Kocevar Why you remove these LD/OBJCOPYFLAG option? Is board now flashable and bootable with this patch? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] kernel panic on p54pci insertion on mipsel
> > As it is unclear to me which firmware I should use (lspci outputs both > ISL3890 and ISL3886 for this device; http://prism54.org/fullmac.html tells > that these two cards should use different firmware), I also tried 1.0.4.3.arm > firmware - this time, it oopses, with no kernel panic: hi, there are the "old" kernel module called prism54.ko (in openwrt it is the kmod-net-prism54 module) and a newer one ( kmod-p54-common and kmod-p54-pci) which requires mac80211. both need a firmware to run, but not while loading the kernel module, but if the device will be up (ifconfig eth1 up) the firmware request start looking for the firmware file in /lib/firmware. the chip 3880 is hardmac, so you will need 1.0.4.3 and rename it to isl3890. the chips 3886 and 3887 are softmac, so you need a 2.x firmware (for ex. 2.7.0.0). more infos: hardmac docu, as you know is under prism54.org und softmac docu is under http://islsm.org/wiki/ ia far as i remember the new driver was not working on kernels >2.6.19 but only prism54. now with kernel >2.6.24 the old driver prism54 is not working anymore but the new one. tested on soekris (x86). i will test later on to build a new openwrt image for mtx-1 (mips) so long ulf ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Etrax support
MichelinoK wrote: > I've just downloaded the latest svn trunk...and etrax target cannot be > compiled anymore... > Can someone test? Works for me, except for kernel compilation I had to apply this patch.. HTH, Hinko -- ČETRTA POT, d.o.o., Kranj Planina 3 4000 Kranj Slovenia, Europe Tel. +386 (0) 4 280 66 03 E-mail: [EMAIL PROTECTED] Http: www.cetrtapot.si --- linux-2.6.25.12/arch/cris/arch-v10/boot/compressed/Makefile.orig 2008-08-06 12:07:38.0 +0200 +++ linux-2.6.25.12/arch/cris/arch-v10/boot/compressed/Makefile 2008-08-06 12:07:47.0 +0200 @@ -3,10 +3,8 @@ # ccflags-y += -O2 -LD = $(CROSS_COMPILE)ld -m criself ldflags-y += -T $(obj)/decompress.ld OBJECTS = $(obj)/head.o $(obj)/misc.o -OBJCOPYFLAGS = -O binary --remove-section=.bss quiet_cmd_image = BUILD $@ cmd_image = cat $(obj)/decompress.bin $(obj)/piggy.gz > $@ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] update acx-mac80211
Still crashes on my 1350 (Speedport W701V) but might help others Signed-off-by: Jan Willies <[EMAIL PROTECTED]> --- package/acx-mac80211/Makefile |9 +-- package/acx-mac80211/patches/001-build_module.diff | 22 ++-- 2 files changed, 17 insertions(+), 14 deletions(-) diff --git a/package/acx-mac80211/Makefile b/package/acx-mac80211/Makefile index 10865ab..2fcf3a6 100644 --- a/package/acx-mac80211/Makefile +++ b/package/acx-mac80211/Makefile @@ -10,12 +10,15 @@ include $(TOPDIR)/rules.mk include $(INCLUDE_DIR)/kernel.mk PKG_NAME:=acx-mac80211 -PKG_VERSION:=20080210 +PKG_REV:=11edba2 +PKG_VERSION:=20080805 PKG_RELEASE:=1 PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2 -PKG_SOURCE_URL:[EMAIL PROTECTED]/acx100 -PKG_MD5SUM:=d1c38b3ff24ce9162eb678298763ec88 +PKG_SOURCE_URL:=git://gitorious.org/acx-mac80211/mainline.git +PKG_SOURCE_PROTO:=git +PKG_SOURCE_SUBDIR:=$(PKG_NAME)-$(PKG_VERSION) +PKG_SOURCE_VERSION:=$(PKG_REV) PKG_FW_C16_NAME:=tiacx111c16 PKG_FW_C16_URL:=http://teknoraver.net/software/acx-mac80211/ diff --git a/package/acx-mac80211/patches/001-build_module.diff b/package/acx-mac80211/patches/001-build_module.diff index 3c1fcda..38dd590 100644 --- a/package/acx-mac80211/patches/001-build_module.diff +++ b/package/acx-mac80211/patches/001-build_module.diff @@ -1,11 +1,11 @@ acx-mac80211-20070610/Makefile 2007-06-10 20:23:27.0 +0200 -+++ acx-mac80211-20070610//Makefile2007-07-23 17:00:34.0 +0200 -@@ -4,7 +4,7 @@ - acx-mac80211-obj-$(CONFIG_ACX_MAC80211_USB) += usb.o - - #acx-mac80211-objs := wlan.o conv.o ioctl.o common.o $(acx-mac80211-obj-y) --acx-mac80211-objs := common.o $(acx-mac80211-obj-y) -+acx-mac80211-objs := common.o $(acx-mac80211-obj-m) - - # Use this if you have proper Kconfig integration: - +--- acx-mac80211-20080802/Makefile 2008-08-02 17:34:09.0 +0200 acx-mac80211-20080802-b/Makefile 2008-08-04 22:24:25.0 +0200 +@@ -28,7 +28,7 @@ + obj-$(CONFIG_ACX_MAC80211) += acx-mac80211.o + acx-mac80211-obj-$(CONFIG_ACX_MAC80211_PCI) += pci.o + acx-mac80211-obj-$(CONFIG_ACX_MAC80211_USB) += usb.o +- acx-mac80211-objs := common.o $(acx-mac80211-obj-y) ++ acx-mac80211-objs := common.o $(acx-mac80211-obj-m) + else + # Otherwise we were called directly from the command line: the the kernel build + # system must be explicitly invoked. -- 1.5.6.4 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] fix for building iproute2 on FreeBSD
package iproute2 has problems building on recent BSD-derived platforms because some programs to be run on the host use malloc.h in an incompatible way. package/iproute2/patches/004-darwin_fixes.patch has a fix for Darwin, however the fix can be made to work on other BSD platforms by changing the patch as below. I think a similar approach should work for other BSD-derived platforms, replacing the #ifndef __APPLE__ with #if !defined(__APPLE__) && !defined(__FreeBSD__) && !defined(...) or perhaps even with just #ifdef __linux__ if the set of platforms where malloc.h is ok is small or restricted to just linux In any case, the patch is below. cheers luigi Index: package/iproute2/patches/004-darwin_fixes.patch === --- package/iproute2/patches/004-darwin_fixes.patch (revision 12201) +++ package/iproute2/patches/004-darwin_fixes.patch (working copy) @@ -6,7 +6,7 @@ #include #include #include -+#ifndef __APPLE__ ++#if !defined(__APPLE__) && !defined(__FreeBSD__) #include +#endif #include @@ -20,7 +20,7 @@ #include #include -+#ifndef __APPLE__ ++#if !defined(__APPLE__) && !defined(__FreeBSD__) #include #include +#else @@ -37,7 +37,7 @@ #include #include -+#ifndef __APPLE__ ++#if !defined(__APPLE__) && !defined(__FreeBSD__) #include #include +#else @@ -54,7 +54,7 @@ #include #include #include -+#ifndef __APPLE__ ++#if !defined(__APPLE__) && !defined(__FreeBSD__) #include - #include ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] kernel panic on p54pci insertion on mipsel
Luis R. Rodriguez schrieb: > On Tue, Aug 5, 2008 at 2:54 PM, Tomasz Chmielewski <[EMAIL PROTECTED]> wrote: >> Johannes Berg schrieb: Call Trace:[][] >>> My magic crystal ball says that this is not inside p54 at all, and >>> indeed a problem in your kernel patches. :P >> An amazingly advanced crystal ball you have ;) >> >> So, a final update: ASUS WL-500gP (v1) running with OpenWRT patches and a >> prism54 mini-pci card: >> >> - panics / oopses with p54pci.ko > > Can't help you there, and what Johannes was trying to say is the call > trace doesn't help us as its just hex values to us. We would need the > mapped culprit routines. Is there a link anywhere explaining how to get these to help debugging? >> - doesn't work with prism54.ko module (similar messages to >> http://marc.info/?l=linux-wireless&m=120250829717134&w=2) > > We need more details, or do you get *exactly* the same error messages? > > "Out of memory, cannot handle oid" comes up after a failed kmalloc() > while trying to handle an interrupt and management frame (not 802.11 > frame) from the firmware. From that archived mailing list though the > oid 0x080002ff is mentioned and... well prism54 doesn't know what that > is. I wonder if the firmware is triggering random interrupts with > bogus oids. > > If you can provide a complete log it can help. I'll try to post it later today in the evening. -- Tomasz Chmielewski http://wpkg.org ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
