From mboxrd@z Thu Jan 1 00:00:00 1970 From: Udi Finkelstein Date: Mon, 26 May 2003 11:59:21 +0300 Subject: [U-Boot-Users] Doubt on Kernel Linking In-Reply-To: <002101c323cd$788955c0$6706a8c0@SPLENDOR> References: <20030523135616.99CA5C6162@atlas.denx.de> <001201c323b6$08c05bb0$6706a8c0@SPLENDOR> <3ED1B935.5010409@udif.com> <002101c323cd$788955c0$6706a8c0@SPLENDOR> Message-ID: <3ED1D769.6070901@udif.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Please see: http://www.penguinppc.org/dev/kernel.shtml Not that I look at it again, I probably got the source using rsync, not CVS. You can also look at http://source.mvista.com if you don't mind using the Bitkeeper client. Udi Rupesh S wrote: > Hi, > Is there any http or ftp server in www.penguinppc.org from where I can > download the linuxppc kernel ( > 2.4.18) > > ----- Original Message ----- > From: "Udi Finkelstein" > To: "Rupesh S" > Cc: "Wolfgang Denk" ; > Sent: Sunday, May 25, 2003 11:50 PM > Subject: Re: [U-Boot-Users] Doubt on Kernel Linking > > > >>I had the same problem as you in the past (8xx board locked up in linux >>with sig11 messages in log_buf). Since log_buf is cyclic (it assums that >>the latest messages are the most important), The buffer is overwritten >>with the sig 11 messages. >> >>I've modified the debug code that writes to log_buf (kernel/printk.c) >>and instead of wrapping around, it stopped writing at the end of the >>buffer (sorry, no patch - its quite simply, and I didn't keep it). >>This way you can see >>You can also control the size of the log buf by changing LOG_BUF_LEN in >>the same file. >> >>BTW, I've never managed to run the ELDK kernel (I was aware of >>clocks_in_mhz - changing it didn't help). I ended up using 2.4.20 from >>the linuxppc_2_4 CVS tree in www.penguinppc.org , which worked for me. >>OTOH, the ELDK kernel works for other people. >> >>I'm now trying to integrate some parts of the ELDK kernel such as the >>8xx LCD code in the latest kernel. >> >>Udi >> >>n.b. Wolfgang, did you get the u-boot patch I sent you? (RBC823 config + >>8xx LCD patches) >> >>Rupesh S wrote: >> >>>I also enabled the DEBUG printfs in u-boot. >>>Below attached is the log of messages I got after displaying memory of >>>"log_buf". >>>It gives a few "OOPS". >>>The kernel mesages must be happening before the kernel gets hold of > > serial > >>>console as well, because I don't see these on my console. >>> >>>:>bootm 100000 >>>## Booting image at 00100000 ... >>> Image Name: Rupesh's Kernel Image >>> Image Type: PowerPC Linux Kernel Image (gzip compressed) >>> Data Size: 489707 Bytes = 478.2 kB >>> Load Address: 00000000 >>> Entry Point: 00000000 >>> Verifying Checksum ... OK >>> Uncompressing Kernel Image ... OK >>>## Current stack ends at 0x0075FC18 => set upper limit to 0x0075F410 >>>## cmdline at 0x0075F310 ... 0x0075F310 >>>bd address = 0x0075FFC4 >>>memstart = 0x00000000 >>>memsize = 0x00800000 >>>flashstart = 0x02800000 >>>flashsize = 0x00200000 >>>flashoffset = 0x00080000 >>>sramstart = 0x00000000 >>>sramsize = 0x00000000 >>>immr_base = 0xFF000000 >>>bootflags = 0x00000001 >>>intfreq = 40 MHz >>>busfreq = 40 MHz >>>ethaddr = 08:00:22:50:70:63 >>>IP addr = 192.168.6.227 >>>baudrate = 19200 bps >>>No initrd >>>## Transferring control to Linux (at address 00000000) ... >>> >>>/****************** Here It Hanged !!! *****************/ >>>/***************** Below messages after RESET ************************/ >>> >>> >>>U-Boot 0.3.1 (May 26 2003 - 11:20:21) >>> >>>CPU: PPC823ZTnnA at 40 MHz: 2 kB I-Cache 1 kB D-Cache >>> *** Warning: CPU Core has Silicon Bugs -- Check the Errata *** >>>Board: FADS with db MPC823 rev ENG or PILOT >>>DRAM: (4 MB SDRAM) 8 MB >>>Top of RAM usable for U-Boot at: 00800000 >>>Reserving 512k for U-Boot at: 00780000 >>>Reserving 128k for malloc() at: 00760000 >>>Reserving 60 Bytes for Board Info at: 0075ffc4 >>>Reserving 44 Bytes for Global Data at: 0075ff98 >>>Stack Pointer at: 0075ff78 >>>New Stack Pointer is: 0075ff78 >>>Now running in RAM - U-Boot at: 00780000 >>>FLASH: 2 MB >>>In: serial >>>Out: serial >>>Err: serial >>>U-Boot relocated to 00780000 >>>Net: SCC ETHERNET >>>### main_loop entered: bootdelay=0 >>> >>>### main_loop: bootcmd="" >>> >>>/********************* The location of "log_buf" >>>*****************************************/ >>>:>md 12eee8 >>>0012eee8: 63657373 206f6620 62616420 61726561 cess of bad area >>>0012eef8: 2c207369 673a2031 310a4f6f 70733a20 , sig: 11.Oops: >>>0012ef08: 6b65726e 656c2061 63636573 73206f66 kernel access of >>>0012ef18: 20626164 20617265 612c2073 69673a20 bad area, sig: >>>0012ef28: 31310a4f 6f70733a 206b6572 6e656c20 11.Oops: kernel >>>0012ef38: 61636365 7373206f 66206261 64206172 access of bad ar >>>0012ef48: 65612c20 7369673a 2031310a 3c323e4b ea, sig: 11.<2>K >>>0012ef58: 65726e65 6c207374 61636b20 6f766572 ernel stack over >>>0012ef68: 666c6f77 20696e20 70726f63 65737320 flow in process >>>0012ef78: 63303131 37303230 2c207231 3d633031 c0117020, r1=c01 >>>0012ef88: 31373262 300a4f6f 70733a20 6b65726e 172b0.Oops: kern >>>0012ef98: 656c2061 63636573 73206f66 20626164 el access of bad >>>0012efa8: 20617265 612c2073 69673a20 31310a4f area, sig: 11.O >>>0012efb8: 6f70733a 206b6572 6e656c20 61636365 ops: kernel acce >>>0012efc8: 7373206f 66206261 64206172 65612c20 ss of bad area, >>>0012efd8: 7369673a 2031310a 4f6f7073 3a206b65 sig: 11.Oops: ke >>>:> >>> >>>What could be wrong ?? >>>Please advice.. >>>Rupesh >>> >>>----- Original Message ----- >>>From: "Wolfgang Denk" >>>To: "Rupesh S" >>>Cc: >>>Sent: Friday, May 23, 2003 6:56 AM >>>Subject: Re: [U-Boot-Users] Doubt on Kernel Linking >>> >>> >>> >>> >>>>In message <00a901c3219b$59d821d0$6706a8c0@SPLENDOR> you wrote: >>>> >>>> >>>>>I kept the link address back at 0xc0000000. >>>>>Doing mkimage , I did load address and entry address as 0x0. >>>>> >>>>>On my FADS823 board, I do a download to 0x100000. >>>>>And gave a bootm 0x100000. >>>>> >>>>>But the system hangs after Uncompressing Kernel Image... >>>>>Note: I have compared the bd_info stricture of linux and u-boot . It is >>> >>>the >>> >>> >>>>>same . Also the IMMR address. >>>>>I do mkimage on gzipped binary image of vmlinux. >>>>> >>>>>Please advice. >>>> >>>>Attach a debugger (BDI2000 recommended). >>>> >>>>Or reset the board and check the contents of the "log_buf" buffer >>>>(post mortem dump) - grep the address from the System.map file, and >>>>subtract 0xC0000000 to convert from virtual to physical address; the >>>>use U-Boot's "md" command. >>>> >>>>Best regards, >>>> >>>>Wolfgang Denk >>>> >>>>-- >>>>Software Engineering: Embedded and Realtime Systems, Embedded Linux >>>>Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de >>>>If all economists were laid end to end, they would not reach a con- >>>>clusion. >>> >>> >>> >>> >>>------------------------------------------------------- >>>This SF.net email is sponsored by: ObjectStore. >>>If flattening out C++ or Java code to make your application fit in a >>>relational database is painful, don't do it! Check out ObjectStore. >>>Now part of Progress Software. http://www.objectstore.net/sourceforge >>>_______________________________________________ >>>U-Boot-Users mailing list >>>U-Boot-Users at lists.sourceforge.net >>>https://lists.sourceforge.net/lists/listinfo/u-boot-users >>> >> >> > >