Re: Network is blocked till ping is issued
On 8/30/07, DI BACCO ANTONIO - technolabs [EMAIL PROTECTED] wrote: sounds to me like it could be a classical ARP problem. Have you checked the ARP cache on the non-Linux machine? But if Linux received the SYN packet of TCP connection, shouldn't the Linux machine reply to the source mac address of SYN packet with a SYN,ACK packet? No. You are confusing Ethernet frames and IP packets a little bit. If a Linux machine receives a SYN from a remote host (not on the same network) then the Linux machine needs to ARP for the router that is listed as the default route in the routing table. If no such default route exists, you will not be able to reach the remote host. If the router doesn't reply to your ARP request, you will not be able to reach the remote host. Check to make sure you are not having either one of these problems. ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: BUG: NETDEV WATCHDOG - Badness in gianfar driver?
On 4/26/07, Clemens Koller [EMAIL PROTECTED] wrote: Hi There! I am currently using Linux ecam.anagramm.de 2.6.21-rc5-g9a5ee4cc #4 Mon Apr 2 21:31:53 CEST 2007 ppc e500 GNU/Linux on an mpc8540 embedded powerpc system. The system was running fine for many days and weeks without any problems. However, just a few minutes ago I noticed a single clicking sound of the harddisk (like a head recalibration), so I checked the system. I couldn't connect to it via ssh anymore, but via a serial console I got at least endless messages as shown below... After a reboot, everything looks fine again but the kernel log grew up to several MBytes. I pasted the hopefully interesting part below. Any ideas of what could be wrong there? I think there could be a problem in the gianfar network driver. Or is there a physical problem with the PHY (a Marvell MV88E)? Any recommendations of how to debug that thingy? There were some workarounds in the e1000 driver to address some issues with some Marvell 88E parts, so you might want to check those out. - 8 - cut here Jan 1 01:00:38 ecam kernel: PHY: 0:00 - Link is Up - 100/Full Jan 1 01:00:35 ecam network: Bringing up loopback interface: succeeded Jan 1 01:00:47 ecam mount: mount: RPC: Remote system error - No route to host Jan 1 01:00:47 ecam netfs: Mounting NFS filesystems: failed Jan 1 01:00:47 ecam netfs: Mounting other filesystems: succeeded Jan 1 01:00:47 ecam xinetd[665]: xinetd Version 2.3.11 started with libwrap options compiled in. Jan 1 01:00:47 ecam xinetd[665]: Started working: 1 available service Jan 1 01:00:50 ecam xinetd: xinetd startup succeeded Jan 1 01:00:50 ecam rc: Starting sshd: succeeded Jan 1 01:00:51 ecam rc: Starting samba: succeeded Jan 1 03:43:23 ecam kernel: NETDEV WATCHDOG: eth0: transmit timed out Jan 1 03:43:23 ecam kernel: [ cut here ] Jan 1 03:43:23 ecam kernel: Badness at c003d3d8 [verbose debug info unavailable] Jan 1 03:43:23 ecam kernel: Call Trace: Jan 1 03:43:23 ecam kernel: [C0355C70] [C0008FE0] show_stack+0x3c/0x194 (unreliable) Jan 1 03:43:23 ecam kernel: [C0355CA0] [C0135594] report_bug+0xa4/0xac Jan 1 03:43:23 ecam kernel: [C0355CB0] [C0003784] program_check_exception+0x2b8/0x460 Jan 1 03:43:23 ecam kernel: [C0355CD0] [C0002908] ret_from_except_full+0x0/0x4c Jan 1 03:43:23 ecam kernel: [C0355D90] [C017B3CC] marvell_ack_interrupt+0x14/0x38 Jan 1 03:43:23 ecam kernel: [C0355DB0] [C01764A8] stop_gfar+0x54/0xd0 Jan 1 03:43:23 ecam kernel: [C0355DD0] [C01773D0] gfar_timeout+0x5c/0x68 Jan 1 03:43:23 ecam kernel: [C0355DE0] [C020A060] dev_watchdog+0x110/0x118 Jan 1 03:43:23 ecam kernel: [C0355E00] [C0024228] run_timer_softirq+0x148/0x1a8 Jan 1 03:43:23 ecam kernel: [C0355E40] [C002006C] __do_softirq+0x78/0xe4 Jan 1 03:43:23 ecam kernel: [C0355E70] [C0007054] do_softirq+0x54/0x58 Jan 1 03:43:23 ecam kernel: [C0355E80] [C001FE4C] irq_exit+0x48/0x58 Jan 1 03:43:23 ecam kernel: [C0355E90] [C0004000] timer_interrupt+0x17c/0x224 Jan 1 03:43:23 ecam kernel: [C0355ED0] [C0002954] ret_from_except+0x0/0x18 Jan 1 03:43:23 ecam kernel: [C0355F90] [C0009FB8] cpu_idle+0xc0/0xd0 Jan 1 03:43:23 ecam kernel: [C0355FB0] [C0001A7C] rest_init+0x28/0x38 Jan 1 03:43:23 ecam kernel: [C0355FC0] [C03568E4] start_kernel+0x220/0x29c Jan 1 03:43:23 ecam kernel: [C0355FF0] [C388] skpinv+0x2b8/0x2f4 Jan 1 03:43:23 ecam kernel: [ cut here ] Jan 1 03:43:23 ecam kernel: Badness at c003d3d8 [verbose debug info unavailable] Jan 1 03:43:23 ecam kernel: Call Trace: Jan 1 03:43:23 ecam kernel: [C0355C70] [C0008FE0] show_stack+0x3c/0x194 (unreliable) [...repeating forever...] - 8 - cut here The system time is wrong, because the I2C realtime clock cannot be read on this system due to some kernel misconfiguration which I didn't care about. Thank you in advance, -- Clemens Koller __ RD Imaging Devices Anagramm GmbH Rupert-Mayer-Straße 45/1 Linhof Werksgelände D-81379 München Tel.089-741518-50 Fax 089-741518-19 http://www.anagramm-technology.com ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: MPC8245 Broadcom BMW board
I would recommend u-boot. You can probably boot CFE if you want, but I found u-boot to be better. I've used that board quite a bit in the past and mostly booted u-boot/linux using the 2MB flash instead of the 512MB one. You will want to make sure you have some kind of flash programmer before you start wiping out what is on there, but once you get that working you should be fine. On 4/9/07, Ashish Ranjan Dash [EMAIL PROTECTED] wrote: Hi, I need some help in booting linux on broadcom bmw( MPC8245 - KAHLUA2)board. The board has the vxWork boot loader, can i boot linux with this boot loader? Should I go for CFE provided by Broacom. or Should I go for u-boot as it supports my board. Please tell me about shadow flasing so that I can have a headstart. Thanks and Regards, Aashis ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: JTAG debugger for MPC82xx/MPC83xx
On 9/19/06, Steven Hein [EMAIL PROTECTED] wrote: Hi, My group is starting a new project includes a custom board with an MPC8258E processor on it. I'm in the process of evaluating the state of the Linux kernel, toolchains, etc. for the MPC8258E/MPC8360E, as well as selecting a JTAG debugger for our project. I've been researching the available JTAG debuggers that support the MPC82xx/MPC83xx family, and I've found these choices so far: * Abatron BDI-2000 * Green Hills Probe * Freescale's PowerTAP PRO for PowerPC * Lauterbach TRACE32-ICD * WindRiver ICE * Embedded Toolsmiths Guardian-SE (BUT...this is no longer being sold, according to an email response I received from Embedded Toolsmiths) We will definitely want one with a network connection, and will will run the debugger software from a Linux host. Ideally, we would also like one that provides a library to allow us to write apps to function the debugger. Can anyone comment on what JTAG debugger they are using, and how have your experiences been? Are there any other good options besides the ones mentioned above. I'd appreciate any input. Thanks! Steve -- Steve Hein ([EMAIL PROTECTED]) Engineering Diagnostics/Software Silicon Graphics, Inc. 1168 Industrial Blvd. Phone: (715) 726-8410 Chippewa Falls, WI 54729 Fax: (715) 726-6715 ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded I've used the BDI on 82xx, 85xx, 83xx, and othersfor custom board bringup and I liked it. Some may not like the command line interface, but I found it quite easy to use. I was able to use remote gdb to debug u-boot, the Linux kernel, and with some trickery userspace apps. I can't comment specifically on the others (though I have seen some WR and Lauterbach debuggers and didn't like the user interface), but I would still recommend the BDI. ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
execve of /sbin/init fails
You could also try compiling init statically. I've had success with that in the past until I figured out what the actual problem was. On 5/30/06, Anantharaman Chetan-W16155 Chetan.S.Anantharaman at motorola.com wrote: Hi, I am trying to bring up a custom board with a PPC405 processor running Linux 2.4.20 (MontaVista Release) and am having problems with the call to execve(/sbin/init, argv_init, envp_init) not returning in the file main.c. The processor just hangs and there is no output on the terminal. I have tried to see if I can run bin/sh and even this execve call does not return. Some things about the board are, the networking option has been disabled in the Linux .config file. I am running U-Boot 1.1.1 as the bootloader and am downloading the uImage (compressed kernel) and the initrd.boot (filesystem) into RAM and accessing the filesystem in RAM. Any help as to what could be causing this to happen or how to debug this issue would be appreciated. Also, I've tried to capture the return value of the execve call but since the call does not return, this has not helped any. Thanks, Chetan Anantharaman ___ Linuxppc-embedded mailing list Linuxppc-embedded at ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
execve of /sbin/init fails
On 5/30/06, Steve Iribarne (GMail) netstv at gmail.com wrote: On 5/30/06, Anantharaman Chetan-W16155 Chetan.S.Anantharaman at motorola.com wrote: Hi, I am trying to bring up a custom board with a PPC405 processor running Linux 2.4.20 (MontaVista Release) and am having problems with the call to execve(/sbin/init, argv_init, envp_init) not returning in the file main.c. Hmm.. Ok.. so I've read the other suggestions all good, but I think we are missing some info. Are you running Busybox? If you are using Busybox, what version? Also, what init are you using? Are you using busyboxes? The ramdisk suggestion was a good one. First off, check what is in your ramdisk. Also check the rights of the files in the ramdisk. Make sure you have the execute bit set. I've seen exactly what you are seeing when my rights on the file init were messed up. Also I think I've seen a hang with an older version of Busybox using their version of init. I just got sysinit and that seemed to fix it, (Although I had to reconfig Busybox to not use their version of init) I guess I totally assumed busybox was being used, so good suggestion. I too saw this with an older version of busybox (0.60 maybe?) and I ended up editing the config to contain only init and then compiled it statically and placed it on the rootfs. It turned out to be just the right size and functionality for my needs. I think I later updated to a 1.0 or 1.1-series and didn't have to use the same hack. The processor just hangs and there is no output on the terminal. When you say the process just hangs, where are you in the boot cycle? Is it before you see the linux kernel starting to load? Or do you see any kernel messages start to spew out? Hope this helps a little. -stv ___ Linuxppc-embedded mailing list Linuxppc-embedded at ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Moving from 2.4 to 2.6 kernel
On 5/4/06, Grant Likely grant.likely at secretlab.ca wrote: On 5/4/06, Chris Dumoulin cdumoulin at ics-ltd.com wrote: I am trying to take a working embedded linux system from kernel 2.4 to 2.6. The hardware is a custom board using a Virtex II Pro with PPC405 processor. The working system uses u-boot 1.1.1 with linux kernel 2.4.18. I am using the same u-boot and I am trying to port linux kernel 2.6.15 to our platform. Using the stuff from the working 2.4 kernel port and other PPC4xx platforms in the 2.6.15 code as examples, I believe I have done everything required to get the kernel booting. However, the kernel seems to hang after being uncompressed. Here is what I see after running bootm from u-boot: The V2pro is already supported in the 2.6 kernel. Are you using that code; or starting from scratch? V2Pro (ML300) and V4FX (ML403) are both supported in the latest 2.6 kernel. I had similar problems when I was porting to the V4FX. Do you have a JTAG debugger (Like a BDI-2000)? I think your best bet is to get in there with a debugger to find out where it goes off into Lala land. Cheers, g. -- Grant Likely, B.Sc. P.Eng. Secret Lab Technologies Ltd. (403) 399-0195 ___ Linuxppc-embedded mailing list Linuxppc-embedded at ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded You could also try enabling early printksometimes that helps tell you how far you did or didn't get.
How to make mudules on linux-ppc2.6.12
Johnson, See: http://lwn.net/Articles/21817/ I found this article to be helpful in the past. -andy On 10/20/05, JohnsonCheng JohnsonCheng at qnap.com.tw wrote: Dear All, I just write a hello world module code, but I can't compile it for ppc2.6.12. My Makefile is list as following: obj-m := test.o all: make ARCH=ppc CROSS_COMPILE=powerpc-linux- -C /root/linux-2.6.12.3 SUBDIR=. modules When I run make, no error message output, but I find no test.ko modules. The output message is list as following: make ARCH=ppc CROSS_COMPILE=powerpc-linux- -C /root/linux-2.6.1 2.3 SUBDIR=. modules make[1]: Entering directory `/root/linux-2.6.12.3' CHK include/linux/version.h make[2]: `arch/ppc/kernel/asm-offsets.s' is up to date. Building modules, stage 2. MODPOST make[1]: Leaving directory `/root/linux-2.6.12.3' Do anyone can give me some help ? Thanks, Johnson Cheng ___ Linuxppc-embedded mailing list Linuxppc-embedded at ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
