Re: [U-Boot-Users] debug linux kernel hangs

Hi Denk: I am sorry for pre unreadable mail. Hi All:
My box is MPC8247 I use u-boot 1.1.1 to boot linux kernel 2.4.22, the bd_info are same in u-boot.h, and IMMR address also same at 0xf0000000. but after input bootm command the linux kernel hangs: ==================================== => setenv ipaddr 192.168.0.33 => setenv serverip 192.168.0.222 => tftp 0x100000 uImage Using FCC1 ETHERNET device TFTP from server 192.168.0.222; our IP address is 192.168.0.33 Filename "uImage". Load address: 0x100000 Loading: ################################################################# ################################################################# ##################################### done Bytes transferred = 853098 (d046a hex) => bootm 0x100000 ## Booting image at 00100000 ... Image Name: Linux Kernel Image Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 853034 Bytes = 833 kB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK =============================================
and under the ppc_6xx-gdb : ========================== (gdb) 620 ppc_md.setup_arch(); (gdb) n
<<<<< long time wait and then press ctl + c.
ò Program received signal SIGSTOP, Stopped (signal). 0xc0007e4c in __delay () at time.c:427 427 } (gdb) where #0 0xc0007e4c in __delay () at time.c:427 #1 0xc0015ae4 in panic (fmt=0x2bbbd "\001") at delay.h:42 (gdb) ========================= It seems kernel breaken down at ppc_md.setup_arch() and panic a message to me, isn't it?
Any hints will be appreciated!
BRG Alexander

Hello,
in message 021a01c57785$fc451a30$4500a8c0@baniantealex you wrote:
My box is MPC8247 I use u-boot 1.1.1 to boot linux kernel 2.4.22, the bd_info are same in
Both the versions of U-Boot and Linux kernel are very, very old. I strongly recommend to use more current versions of the software.
620 ppc_md.setup_arch(); (gdb) n
<<<<< long time wait and then press ctl + c.
...
#0 0xc0007e4c in __delay () at time.c:427 #1 0xc0015ae4 in panic (fmt=0x2bbbd "\001") at delay.h:42
So your kernel has paniced.
and panic a message to me, isn't it?
Indeed. And what was the panic message? What was the contents of the log_buf area?
I'm afraid you will have to type the commands to display the contents of the log buffer yourself - you did not give instructions how to log in on your system.
See also http://www.denx.de/twiki/bin/view/DULG/LinuxPostMortemAnalysis
And by the way: this is a Linux problem, so all of this is completely off topic on this list.
Best regards,
Wolfgang Denk

Hi Denk:
Thanks your help. Just because the serial console can not work on my board, so I step into kernel to trace. I think maybe the kernel init sequence can not arrive the console_init(), so I can not get any message after run "bootm". It just told me "Uncompressing Kernel Image ... OK", then it hangs. Bye the way, I only the u-boot 1.1.1 and linux kernel 2.4.22 in hand, where I can find the lastest code?
Thanks again! BRG
----- Original Message ----- From: "Wolfgang Denk" wd@denx.de To: "Alex shi" alex.shi@tom.com Cc: u-boot-users@lists.sourceforge.net Sent: Thursday, June 23, 2005 8:11 AM Subject: Re: [U-Boot-Users] debug linux kernel hangs
Hello,
in message 021a01c57785$fc451a30$4500a8c0@baniantealex you wrote:
My box is MPC8247 I use u-boot 1.1.1 to boot linux kernel 2.4.22, the bd_info are same in
Both the versions of U-Boot and Linux kernel are very, very old. I strongly recommend to use more current versions of the software.
620 ppc_md.setup_arch(); (gdb) n
<<<<< long time wait and then press ctl + c.
...
#0 0xc0007e4c in __delay () at time.c:427 #1 0xc0015ae4 in panic (fmt=0x2bbbd "\001") at delay.h:42
So your kernel has paniced.
and panic a message to me, isn't it?
Indeed. And what was the panic message? What was the contents of the log_buf area?
I'm afraid you will have to type the commands to display the contents of the log buffer yourself - you did not give instructions how to log in on your system.
See also http://www.denx.de/twiki/bin/view/DULG/LinuxPostMortemAnalysis
And by the way: this is a Linux problem, so all of this is completely off topic on this list.
Best regards,
Wolfgang Denk
-- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de "'Tis true, 'tis pity, and pity 'tis 'tis true."
- Poloniouius, in Willie the Shake's _Hamlet, Prince of Darkness_

Hi Alex
I had the same problem but only with Xilinx Evaluation Board. What I have made. I used static variables to debug the kerenel startup sequence. In the System.map I could see if there are set or not. Then I could find out where the kernel hangs and I comment out this functions. After that the kernel runs. Further a put this function in the Kernel again and the kernel runs too. But atention: There are a function, in kernel boot sequence, where kernel takes parameters from u-boot. If there the Linux hangs than you must see your u-boot arguments.
I hope I could help you!
best regards
"Alex shi" alex.shi@tom.com Gesendet von: An u-boot-users-admin@list "Wolfgang Denk" wd@denx.de s.sourceforge.net Kopie u-boot-users@lists.sourceforge.net Thema 23.06.2005 02:32 Re: [U-Boot-Users] debug linux kernel hangs
Hi Denk:
Thanks your help. Just because the serial console can not work on my board, so I step into kernel to trace. I think maybe the kernel init sequence can not arrive the console_init(), so I can not get any message after run "bootm". It just told me "Uncompressing Kernel Image ... OK", then it hangs. Bye the way, I only the u-boot 1.1.1 and linux kernel 2.4.22 in hand, where I can find the lastest code?
Thanks again! BRG
----- Original Message ----- From: "Wolfgang Denk" wd@denx.de To: "Alex shi" alex.shi@tom.com Cc: u-boot-users@lists.sourceforge.net Sent: Thursday, June 23, 2005 8:11 AM Subject: Re: [U-Boot-Users] debug linux kernel hangs
Hello,
in message 021a01c57785$fc451a30$4500a8c0@baniantealex you wrote:
My box is MPC8247 I use u-boot 1.1.1 to boot linux kernel 2.4.22, the bd_info are same in
Both the versions of U-Boot and Linux kernel are very, very old. I strongly recommend to use more current versions of the software.
620 ppc_md.setup_arch(); (gdb) n
<<<<< long time wait and then press ctl + c.
...
#0 0xc0007e4c in __delay () at time.c:427 #1 0xc0015ae4 in panic (fmt=0x2bbbd "\001") at delay.h:42
So your kernel has paniced.
and panic a message to me, isn't it?
Indeed. And what was the panic message? What was the contents of the log_buf area?
I'm afraid you will have to type the commands to display the contents of the log buffer yourself - you did not give instructions how to log in on your system.
See also http://www.denx.de/twiki/bin/view/DULG/LinuxPostMortemAnalysis
And by the way: this is a Linux problem, so all of this is completely off topic on this list.
Best regards,
Wolfgang Denk
-- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de "'Tis true, 'tis pity, and pity 'tis 'tis true."
- Poloniouius, in Willie the Shake's _Hamlet, Prince of Darkness_
------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
participants (3)
-
Alex shi
-
andreas_schmidt@ifm-electronic.com
-
Wolfgang Denk