Skip to contentSkip to conversation

2.6.23-rc3 boot hang on MPC8641D

DISCUSSION sivaji 5 participants 14 messages Sep 13, 2007 – Sep 14, 2007

lore
Share & tools
lore

sivaji

author
#0 lore raw

Hi,
I am try to boot the 2.6.23-rc3 kernel to my custom board based on
8641D Processor. After uncompressing the kernel it was hang. I got the following messages.

Uncompressing Kernel Image ... OK
Booting using flat device tree at 0x600000.

Then i tried to debug with GDB. In my source path i given the command
${CROSS_COMPILE}gdb vmlinux, I got GDB Prompt after i tried to set the breakpoint at start_kernel. I got follwing messages

gdb) b start_kernel
Cannot access memory at address 0xc02b44ec

Processor Information:
8641D processor and the silicon revision is 2.0.

Part : MPC8641D
Revision:  2.0
e600 Core Revision:  2.2
DeviceMarking:  B
Processor Version Register Value: 0x8004_0202
System Version Register Value:   0x8090_0120

I don't know how to proceed. Please tell the way how to start kernel
debug in this situation.

By
Sivaji

Signature · 2 lines
View this message in context: http://www.nabble.com/2.6.23-rc3-boot-hang-on-MPC8641D-tf4433508.html#a12648489
Sent from the linuxppc-dev mailing list archive at Nabble.com.
#1 lore raw
Quoted 10 lines · sivaji

Hi,
I am try to boot the 2.6.23-rc3 kernel to my custom board
based on
8641D Processor. After uncompressing the kernel it was hang. I got the following messages.

Uncompressing Kernel Image ... OK
Booting using flat device tree at 0x600000.

Quoted 7 lines

Then i tried to debug with GDB. In my source path i given
the command
${CROSS_COMPILE}gdb vmlinux, I got GDB Prompt after i tried to set the breakpoint at start_kernel. I got follwing messages

gdb) b start_kernel
Cannot access memory at address 0xc02b44ec

how are you connecting gdb to the board?

do you have a JTAG debugger connected to the board?

- k

author
#2 lore raw

Hi,
I have JTAG Debugger connected to the board. I was given the
following commands in the root path of the kernel source

1. ${CROSS_COMPILE}gdb vmlinux
2. I got th GDB prompt after that i give

          target remote 172.29.38.213:2001 i got following results
         (gdb) target remote 172.29.38.213:2001

Remote debugging using 172.29.38.213:2001
Remote packet too long:
deadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbe 0000000000605200000000000060520000000000006052000000000000605200000000000060520000000000006052000000000000605200000000000060520000000000006052000000000000605200000000000060520000000000006052000000000000605200000000000060520000000000006052000000000000605200000000000060520000000000006052000000000000605200000000000060520000000000006052000000000000605200000000000060520000000000006052000000000000605200000000000060520000000000006052000000000000605200000000000060520000000000006052000000000000605200000000fff00100deadbee Ignoring packet error, continuing...
0xdeadbeef in ?? ()
3.(gdb) b start_kernel
Cannot access memory at address 0xc02b44ec

by
sivaji

Quoted 35 lines · Kumar Gala-3 wrote:
Quoted 10 lines · sivaji

Hi,
I am try to boot the 2.6.23-rc3 kernel to my custom board
based on
8641D Processor. After uncompressing the kernel it was hang. I got the following messages.

Uncompressing Kernel Image ... OK
Booting using flat device tree at 0x600000.

Quoted 7 lines

Then i tried to debug with GDB. In my source path i given
the command
${CROSS_COMPILE}gdb vmlinux, I got GDB Prompt after i tried to set the breakpoint at start_kernel. I got follwing messages

gdb) b start_kernel
Cannot access memory at address 0xc02b44ec

how are you connecting gdb to the board?

do you have a JTAG debugger connected to the board?

- k

_______________________________________________
Linuxppc-dev mailing list
[email protected]
https://ozlabs.org/mailman/listinfo/linuxppc-dev

Signature · 2 lines
View this message in context: http://www.nabble.com/2.6.23-rc3-boot-hang-on-MPC8641D-tf4433508.html#a12648671
Sent from the linuxppc-dev mailing list archive at Nabble.com.
#3 lore raw
Quoted 5 lines · sivaji

Hi,
I have JTAG Debugger connected to the board. I was given the
following commands in the root path of the kernel source

If you can dump memory w/o connecting GDB, I suggest the following.

Look in your kernel build for System.map and grep for log_buf you should get something like:

c040b04c d log_buf
c043b1a4 b __log_buf

then dump the memory @ these addresses. I can't remember which one is the correct one. You'll want to subtract c000_0000 from the address to get a physical address that you can dump. This should help provide some possible insight into what's going on.

- k

#4 lore raw
Quoted 13 lines · Kumar Gala
Quoted 5 lines · sivaji

Hi,
I have JTAG Debugger connected to the board. I was given the
following commands in the root path of the kernel source

If you can dump memory w/o connecting GDB, I suggest the following.

Look in your kernel build for System.map and grep for log_buf you should get something like:

Quoted 7 lines

c040b04c d log_buf
c043b1a4 b __log_buf

then dump the memory @ these addresses. I can't remember which one is the correct one. You'll want to subtract c000_0000 from the address to get a physical address that you can dump. This should help provide some possible insight into what's going on.

__log_buf is the actual buffer, log_buf points to the current insertion point IIRC. It should be pretty obvious that you're looking at a dmesg buffer though, unless there's nothing in there for some reason.

cheers

Signature · 8 lines
Michael Ellerman
OzLabs, IBM Australia Development Lab

wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)

We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
#5 lore raw
In reply to sivaji

Hi,=20

Your flat device tree address seems too low. Try to move the dtb to higher address such as 0x2000000.

And which version of your u-boot?

Cheers!
- zw

Quoted 52 lines

-----Original Message-----
From: [email protected]=20 [mailto:[email protected] g] On Behalf Of sivaji
Sent: Thursday, September 13, 2007 12:18 PM
To: [email protected]
Subject: 2.6.23-rc3 boot hang on MPC8641D
=20
=20
Hi,
I am try to boot the 2.6.23-rc3 kernel to my custom=20
board based on
8641D Processor. After uncompressing the kernel it was hang. I got the following messages.
=20
Uncompressing Kernel Image ... OK
Booting using flat device tree at 0x600000.=20
=20
Then i tried to debug with GDB. In my source path i=20
given the command
${CROSS_COMPILE}gdb vmlinux, I got GDB Prompt after i tried to set the breakpoint at start_kernel. I got follwing messages
=20
gdb) b start_kernel
Cannot access memory at address 0xc02b44ec
=20
Processor Information:
8641D processor and the silicon revision is 2.0.

Part : MPC8641D
Revision:  2.0
e600 Core Revision:  2.2
DeviceMarking:  B
Processor Version Register Value: 0x8004_0202
System Version Register Value:   0x8090_0120

=20
I don't know how to proceed. Please tell the way how to=20
start kernel
debug in this situation.
=20
By
Sivaji
--=20
View this message in context:=20
http://www.nabble.com/2.6.23-rc3-boot-hang-on-MPC8641D-tf44335
08.html#a12648489
Sent from the linuxppc-dev mailing list archive at Nabble.com. =20
_______________________________________________
Linuxppc-dev mailing list
[email protected]
https://ozlabs.org/mailman/listinfo/linuxppc-dev
=20

author
#6 lore raw

Hi,

          I tired to move the dtb to 0x2000000, but the result was same.

uboot version is 1.1.6

by
Sivaji

Quoted 69 lines · Zhang Wei-r63237 wrote:

Hi,

Your flat device tree address seems too low. Try to move the dtb to higher address such as 0x2000000.

And which version of your u-boot?

Cheers!
- zw

Quoted 35 lines

-----Original Message-----
From: [email protected] [mailto:[email protected] g] On Behalf Of sivaji
Sent: Thursday, September 13, 2007 12:18 PM
To: [email protected]
Subject: 2.6.23-rc3 boot hang on MPC8641D

Hi,
I am try to boot the 2.6.23-rc3 kernel to my custom
board based on
8641D Processor. After uncompressing the kernel it was hang. I got the following messages.

Uncompressing Kernel Image ... OK
Booting using flat device tree at 0x600000.

Then i tried to debug with GDB. In my source path i
given the command
${CROSS_COMPILE}gdb vmlinux, I got GDB Prompt after i tried to set the breakpoint at start_kernel. I got follwing messages

gdb) b start_kernel
Cannot access memory at address 0xc02b44ec

Processor Information:
8641D processor and the silicon revision is 2.0.

Part : MPC8641D
Revision:  2.0
e600 Core Revision:  2.2
DeviceMarking:  B
Processor Version Register Value: 0x8004_0202
System Version Register Value:   0x8090_0120
Quoted 17 lines

I don't know how to proceed. Please tell the way how to
start kernel
debug in this situation.

By
Sivaji

Signature · 9 lines
View this message in context: 
http://www.nabble.com/2.6.23-rc3-boot-hang-on-MPC8641D-tf44335
08.html#a12648489
Sent from the linuxppc-dev mailing list archive at Nabble.com.

_______________________________________________
Linuxppc-dev mailing list
[email protected]
https://ozlabs.org/mailman/listinfo/linuxppc-dev

_______________________________________________
Linuxppc-dev mailing list
[email protected]
https://ozlabs.org/mailman/listinfo/linuxppc-dev

Signature · 2 lines
View this message in context: http://www.nabble.com/2.6.23-rc3-boot-hang-on-MPC8641D-tf4433508.html#a12648696
Sent from the linuxppc-dev mailing list archive at Nabble.com.
#7 lore raw
Quoted 6 lines · sivaji

Hi,

          I tired to move the dtb to 0x2000000, but the result was  

same.
uboot version is 1.1.6

seems like a pretty old u-boot. Willing to try a 1.3.0-rc1?

- k

#8 lore raw

Yes, It's too old. Maybe not fully supports FDT. You can try the version of Kumar said or in the BSP of Freescale released.

- zw

Quoted 27 lines

-----Original Message-----
From: [email protected]=20 [mailto:[email protected] g] On Behalf Of Kumar Gala
Sent: Thursday, September 13, 2007 1:11 PM
To: sivaji
Cc: [email protected]
Subject: Re: 2.6.23-rc3 boot hang on MPC8641D
=20
=20
On Sep 12, 2007, at 11:52 PM, sivaji wrote:
=20

Quoted 6 lines

Hi,

          I tired to move the dtb to 0x2000000, but the result was =20

same.
uboot version is 1.1.6

=20
seems like a pretty old u-boot. Willing to try a 1.3.0-rc1? =20
- k
_______________________________________________
Linuxppc-dev mailing list
[email protected]
https://ozlabs.org/mailman/listinfo/linuxppc-dev
=20

author
#9 lore raw

Hi,
Sorry i specify the wrong version, we r using 1.2.0. This uboot
was taken from the BSP which was released by Freescale. Previously we tested linux 2.6.21 kernel, we got linux prompt. For this we are using the same uboot(1.2.0).
In that version we face some issues in the pci express, at that time kumar suggest to upgrade the kernel verison 2.6.23-rc3.
Zhang did u suspect the problem is related to uboot?.
by
sivaji

Quoted 39 lines · Zhang Wei-r63237 wrote:

Yes, It's too old. Maybe not fully supports FDT. You can try the version of Kumar said or in the BSP of Freescale released.

- zw

Quoted 19 lines

-----Original Message-----
From: [email protected] [mailto:[email protected] g] On Behalf Of Kumar Gala
Sent: Thursday, September 13, 2007 1:11 PM
To: sivaji
Cc: [email protected]
Subject: Re: 2.6.23-rc3 boot hang on MPC8641D

Quoted 6 lines · sivaji

Hi,

          I tired to move the dtb to 0x2000000, but the result was  

same.
uboot version is 1.1.6

Quoted 8 lines

seems like a pretty old u-boot. Willing to try a 1.3.0-rc1?

- k
_______________________________________________
Linuxppc-dev mailing list
[email protected]
https://ozlabs.org/mailman/listinfo/linuxppc-dev

_______________________________________________
Linuxppc-dev mailing list
[email protected]
https://ozlabs.org/mailman/listinfo/linuxppc-dev

Signature · 2 lines
View this message in context: http://www.nabble.com/2.6.23-rc3-boot-hang-on-MPC8641D-tf4433508.html#a12648963
Sent from the linuxppc-dev mailing list archive at Nabble.com.
#10 lore raw

Hi, Sivaji,

I've tested the newest git tree of Paul's, which is aleady updated to 2.6.23-rc4. The kernel is no problem with the u-boot of our released BSP (Jun, 2007) on MPC8641HPCN board.

Maybe you could update to the newest kernel git tree and try again.

Cheers!
-zw

Quoted 79 lines

-----Original Message-----
From: [email protected]=20 [mailto:[email protected] g] On Behalf Of sivaji
Sent: Thursday, September 13, 2007 1:32 PM
To: [email protected]
Subject: RE: 2.6.23-rc3 boot hang on MPC8641D
=20
=20
Hi,
Sorry i specify the wrong version, we r using=20
1.2.0. This uboot
was taken from the BSP which was released by Freescale.=20 Previously we tested
linux 2.6.21 kernel, we got linux prompt. For this we are=20 using the same
uboot(1.2.0).
In that version we face some issues in the pci express, at=20 that time kumar
suggest to upgrade the kernel verison 2.6.23-rc3.
Zhang did u suspect the problem is related to uboot?. by
sivaji
=20
=20

Quoted 2 lines · Zhang Wei-r63237 wrote:

=20
Yes, It's too old. Maybe not fully supports FDT. You can=20

try the version

Quoted 20 lines

of Kumar said or in the BSP of Freescale released. =20
- zw
=20

Quoted 16 lines

-----Original Message-----
From: [email protected]=20 [mailto:[email protected] g] On Behalf Of Kumar Gala
Sent: Thursday, September 13, 2007 1:11 PM
To: sivaji
Cc: [email protected]
Subject: Re: 2.6.23-rc3 boot hang on MPC8641D
=20
=20
On Sep 12, 2007, at 11:52 PM, sivaji wrote:
=20

Quoted 4 lines

Hi,

          I tired to move the dtb to 0x2000000, but the=20

result was =20

Quoted 11 lines
Quoted 11 lines
Quoted 2 lines

same.
uboot version is 1.1.6

=20
seems like a pretty old u-boot. Willing to try a 1.3.0-rc1? =20
- k
_______________________________________________
Linuxppc-dev mailing list
[email protected]
https://ozlabs.org/mailman/listinfo/linuxppc-dev
=20

Quoted 6 lines

_______________________________________________
Linuxppc-dev mailing list
[email protected]
https://ozlabs.org/mailman/listinfo/linuxppc-dev
=20
=20

=20
--=20
View this message in context:=20
http://www.nabble.com/2.6.23-rc3-boot-hang-on-MPC8641D-tf44335
08.html#a12648963
Sent from the linuxppc-dev mailing list archive at Nabble.com. =20
_______________________________________________
Linuxppc-dev mailing list
[email protected]
https://ozlabs.org/mailman/listinfo/linuxppc-dev
=20

author
#11 lore raw

Hi Zhang,
Asper ur idea, i downloaded latest BSP(Jun,2007) and the
kernel (2.6.23-rc4) from the Paul's Git tree.
Uboot(1.2.0) was taken from the latest BSP. I portted the new uboot to my custom board, i got uboot prompt.

When i compiling the kernel i got following warning messages
WARNING: vmlinux.o(.text+0x169f6): Section mismatch: reference to .init.data:boot_command_line (between 'note_bootable_part' and 'pmac_restart')
WARNING: vmlinux.o(.text+0x16a02): Section mismatch: reference to .init.data:boot_command_line (between 'note_bootable_part' and 'pmac_restart')
WARNING: vmlinux.o(.text+0x16a12): Section mismatch: reference to .init.data:boot_command_line (between 'note_bootable_part' and 'pmac_restart')

When i try to boot the kernel, I got following messages

Booting image at 00200000 ...

   Image Name:   Linux-2.6.23-rc4-g5326152f-dirty
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    1842307 Bytes =  1.8 MB

Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Booting using flat device tree at 0x600000

I can't know whether the problem is related to uboot or
kernel. But i tested the board with the 2.6.21 kernel, it was up.In that kernel we face some issues on PCI Express so we plan to upgrade the kernel. But the latest kernel was not up.
Please advice me.

By
Sivaji

Quoted 97 lines · Zhang Wei-r63237 wrote:

Hi, Sivaji,

I've tested the newest git tree of Paul's, which is aleady updated to 2.6.23-rc4. The kernel is no problem with the u-boot of our released BSP (Jun, 2007) on MPC8641HPCN board.

Maybe you could update to the newest kernel git tree and try again.

Cheers!
-zw

Quoted 61 lines

-----Original Message-----
From: [email protected] [mailto:[email protected] g] On Behalf Of sivaji
Sent: Thursday, September 13, 2007 1:32 PM
To: [email protected]
Subject: RE: 2.6.23-rc3 boot hang on MPC8641D

Hi,
Sorry i specify the wrong version, we r using
1.2.0. This uboot
was taken from the BSP which was released by Freescale. Previously we tested
linux 2.6.21 kernel, we got linux prompt. For this we are using the same
uboot(1.2.0).
In that version we face some issues in the pci express, at that time kumar
suggest to upgrade the kernel verison 2.6.23-rc3. Zhang did u suspect the problem is related to uboot?. by
sivaji

Quoted 2 lines · Zhang Wei-r63237 wrote:

Yes, It's too old. Maybe not fully supports FDT. You can

try the version

Quoted 20 lines

of Kumar said or in the BSP of Freescale released.

- zw

Quoted 16 lines

-----Original Message-----
From: [email protected] [mailto:[email protected] g] On Behalf Of Kumar Gala
Sent: Thursday, September 13, 2007 1:11 PM
To: sivaji
Cc: [email protected]
Subject: Re: 2.6.23-rc3 boot hang on MPC8641D

Quoted 4 lines · sivaji

Hi,

          I tired to move the dtb to 0x2000000, but the 

result was

Quoted 11 lines
Quoted 11 lines
Quoted 2 lines

same.
uboot version is 1.1.6

seems like a pretty old u-boot. Willing to try a 1.3.0-rc1?

- k
_______________________________________________
Linuxppc-dev mailing list
[email protected]
https://ozlabs.org/mailman/listinfo/linuxppc-dev

Quoted 18 lines
Quoted 6 lines

_______________________________________________
Linuxppc-dev mailing list
[email protected]
https://ozlabs.org/mailman/listinfo/linuxppc-dev

Signature · 9 lines
View this message in context: 
http://www.nabble.com/2.6.23-rc3-boot-hang-on-MPC8641D-tf44335
08.html#a12648963
Sent from the linuxppc-dev mailing list archive at Nabble.com.

_______________________________________________
Linuxppc-dev mailing list
[email protected]
https://ozlabs.org/mailman/listinfo/linuxppc-dev

_______________________________________________
Linuxppc-dev mailing list
[email protected]
https://ozlabs.org/mailman/listinfo/linuxppc-dev

Signature · 2 lines
View this message in context: http://www.nabble.com/2.6.23-rc3-boot-hang-on-MPC8641D-tf4433508.html#a12676464
Sent from the linuxppc-dev mailing list archive at Nabble.com.
author
#12 lore raw
In reply to Kumar Gala

Hi,
I am not willing to upgrade the uboot. Becuase it takes some time to
port the new uboot for my custom boad.
whether the current problem is related to uboot ? One more point, previously i tried 2.6.21 with the same uboot(1.1.6) we got linux prompt but we face some issue in the pci express in that version. so we plan to upgrade the kernel version.
by
Sivaji

Quoted 20 lines · Kumar Gala-3 wrote:
Quoted 6 lines · sivaji

Hi,

          I tired to move the dtb to 0x2000000, but the result was  

same.
uboot version is 1.1.6

seems like a pretty old u-boot. Willing to try a 1.3.0-rc1?

- k
_______________________________________________
Linuxppc-dev mailing list
[email protected]
https://ozlabs.org/mailman/listinfo/linuxppc-dev

Signature · 2 lines
View this message in context: http://www.nabble.com/2.6.23-rc3-boot-hang-on-MPC8641D-tf4433508.html#a12648913
Sent from the linuxppc-dev mailing list archive at Nabble.com.
#13 lore raw
Quoted 9 lines · sivaji

Hi,
I am not willing to upgrade the uboot. Becuase it takes some time to
port the new uboot for my custom boad.
whether the current problem is related to uboot ? One more point, previously i tried 2.6.21 with the same uboot(1.1.6) we got linux prompt but we face some issue in the pci express in that version. so we plan to upgrade the kernel version.

I thought u-boot < 1.3 didn't understand the flat tree at all. In which case you'll need a cuboot zImage.

Signature · 4 lines
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson