2008/5/5 张轶 <[EMAIL PROTECTED]>: > > The kernel I am using is 2.6.24,gcc 4.1.0,glibc 2.3.6,and the board Xilinx > XUPV2P > > It compiles successfully with some warnings like below: > MODPOST vmlinux.o > WARNING: vmlinux.o(.text+0x223c): Section mismatch: reference to > .init.text:early_init (between 'start_here' and 'initial_mmu') > WARNING: vmlinux.o(.text+0x2254): Section mismatch: reference to > .init.text:machine_init (between 'start_here' and 'initial_mmu') > WARNING: vmlinux.o(.text+0x2258): Section mismatch: reference to > .init.text:MMU_init (between 'start_here' and 'initial_mmu') > WARNING: vmlinux.o(.text+0x22b2): Section mismatch: reference to > .init.text:start_kernel (between 'start_here' and 'initial_mmu') > WARNING: vmlinux.o(.text+0x22b6): Section mismatch: reference to > .init.text:start_kernel (between 'start_here' and 'initial_mmu') > LD vmlinux > > The system is created as ACE file and booted from CF Card > > After uncompressing the kernel,the system hangs.The information is like > below: > > loaded at: 00400000 0056619C > board data at: 00000000 0000007C > relocated to: 00404068 004040E4 > zimage at: 00404E51 00563BF4 > avail ram: 00567000 7C9E2370 > > Linux/PPC load: console=ttyS0,9600 root=/dev/xsysace/disc0/part3 rw > Uncompressing Linux...done. > Now booting the kernel > I wonder if it is the upper WARNINGs that causes the hang of the system, and > how can I fix it.
The warnings most likely are not related to your problem. Most likely you just haven't set console correctly. Are you using a uartlite? If so, use 'console=ttyUL0' on the kernel parameters line. If you can halt the CPU and look at memory, your should also look at __log_buf (see System.map to find the address of __log_buf) to see how far the kernel is booting. Cheers, g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
