* [U-Boot-Users] debug linux kernel hangs
@ 2005-06-22 19:30 Alex shi
0 siblings, 0 replies; 5+ messages in thread
From: Alex shi @ 2005-06-22 19:30 UTC (permalink / raw)
To: u-boot
Hi all:
My platform is MPC8247, u-boot verison is 1.1.1 and linux kernel version is 2.4.22
in the serial console I load the linux kernel and want to boot it under u-boot:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
=> setenv ethaddr 00:01:02:03:04:05
=> 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
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
but after print the "Uncompressing Kernel Image ... OK" msg, the kernel hangs.
I use the same u-boot.h file under linux kernel and u-boot, and sure the bd_info in them are same.
IMMR address also are same at 0xf0000000.
My bdi2000 run and print below:
++++++++++++++++++++++++++++++++++
8272>i
Target CPU : MPC8280/8220/5200 (Zeppo)
Target state : debug mode
Debug entry cause : COP freeze (startup)
Current PC : 0xfff00100
Current CR : 0x00000000
Current MSR : 0x00001042
Current LR : 0x00000000
8272>g
8272>h
Target CPU : MPC8280/8220/5200 (Zeppo)
Target state : debug mode
Debug entry cause : COP halt
Current PC : 0x07fe94c8
Current CR : 0x84002024
Current MSR : 0x0000b002
Current LR : 0x07fda464
8272>bi 0xc01554c8 (which is the start_kernel_address)
Breakpoint identification is 1
8272>g
- TARGET: stopped
8272>i
Target CPU : MPC8280/8220/5200 (Zeppo)
Target state : debug mode
Debug entry cause : <reserved 0>
Current PC : 0x001cbde4
Current CR : 0x24008084
Current MSR : 0x00003002
Current LR : 0x00000028
+++++++++++++++++++++++++++++++++++++++++++
Why the Current PC can not get the start_kernel address? How can i to debug the linux kernel?
Any hits will be very appreciated!
BRG
Alexander
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20050623/19a36956/attachment.htm
^ permalink raw reply [flat|nested] 5+ messages in thread
* [U-Boot-Users] debug linux kernel hangs
[not found] <20050622195228.ED924C1510@atlas.denx.de>
@ 2005-06-22 22:30 ` Alex shi
0 siblings, 0 replies; 5+ messages in thread
From: Alex shi @ 2005-06-22 22:30 UTC (permalink / raw)
To: u-boot
Hi Denk: Sorry, I did not notice it.Hi all:
My platform is MPC8247, u-boot verison is 1.1.1 and linux kernel version is 2.4.22
in the serial console I load the linux kernel and want to boot it under u-boot:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
=> setenv ethaddr 00:01:02:03:04:05
=> 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
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
but after print the "Uncompressing Kernel Image ... OK" msg, the kernel hangs.
I use the same u-boot.h file under linux kernel and u-boot, and sure the bd_info in them
are same.
IMMR address also are same at 0xf0000000.
My bdi2000 run and print below:
++++++++++++++++++++++++++++++++++
8272>i
Target CPU : MPC8280/8220/5200 (Zeppo)
Target state : debug mode
Debug entry cause : COP freeze (startup)
Current PC : 0xfff00100
Current CR : 0x00000000
Current MSR : 0x00001042
Current LR : 0x00000000
8272>g
8272>h
Target CPU : MPC8280/8220/5200 (Zeppo)
Target state : debug mode
Debug entry cause : COP halt
Current PC : 0x07fe94c8
Current CR : 0x84002024
Current MSR : 0x0000b002
Current LR : 0x07fda464
8272>bi 0xc01554c8 (which is the start_kernel_address)
Breakpoint identification is 1
8272>g
- TARGET: stopped
8272>i
Target CPU : MPC8280/8220/5200 (Zeppo)
Target state : debug mode
Debug entry cause : <reserved 0>
Current PC : 0x001cbde4
Current CR : 0x24008084
Current MSR : 0x00003002
Current LR : 0x00000028
+++++++++++++++++++++++++++++++++++++++++++
Why the Current PC can not get the start_kernel address? How can i to debug the linux
kernel?
Any hits will be very appreciated!
BRG
Alexander
^ permalink raw reply [flat|nested] 5+ messages in thread
* [U-Boot-Users] debug linux kernel hangs
[not found] <20050622225017.94069C1510@atlas.denx.de>
@ 2005-06-22 23:56 ` Alex shi
2005-06-23 0:11 ` Wolfgang Denk
0 siblings, 1 reply; 5+ messages in thread
From: Alex shi @ 2005-06-22 23:56 UTC (permalink / raw)
To: u-boot
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@ppc_md.setup_arch()
and panic a message to me, isn't it?
Any hints will be appreciated!
BRG
Alexander
^ permalink raw reply [flat|nested] 5+ messages in thread
* [U-Boot-Users] debug linux kernel hangs
2005-06-22 23:56 ` Alex shi
@ 2005-06-23 0:11 ` Wolfgang Denk
2005-06-23 0:32 ` Alex shi
0 siblings, 1 reply; 5+ messages in thread
From: Wolfgang Denk @ 2005-06-23 0:11 UTC (permalink / raw)
To: u-boot
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 at denx.de
"'Tis true, 'tis pity, and pity 'tis 'tis true."
- Poloniouius, in Willie the Shake's _Hamlet, Prince of Darkness_
^ permalink raw reply [flat|nested] 5+ messages in thread
* [U-Boot-Users] debug linux kernel hangs
2005-06-23 0:11 ` Wolfgang Denk
@ 2005-06-23 0:32 ` Alex shi
0 siblings, 0 replies; 5+ messages in thread
From: Alex shi @ 2005-06-23 0:32 UTC (permalink / raw)
To: u-boot
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 at denx.de
> "'Tis true, 'tis pity, and pity 'tis 'tis true."
> - Poloniouius, in Willie the Shake's _Hamlet, Prince of Darkness_
>
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2005-06-23 0:32 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20050622195228.ED924C1510@atlas.denx.de>
2005-06-22 22:30 ` [U-Boot-Users] debug linux kernel hangs Alex shi
[not found] <20050622225017.94069C1510@atlas.denx.de>
2005-06-22 23:56 ` Alex shi
2005-06-23 0:11 ` Wolfgang Denk
2005-06-23 0:32 ` Alex shi
2005-06-22 19:30 Alex shi
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox