From: sivaji <rameshmrm@gmail.com>
To: linuxppc-dev@ozlabs.org
Subject: Re: 2.6.23-rc3 boot hang on MPC8641D
Date: Wed, 12 Sep 2007 21:47:28 -0700 (PDT) [thread overview]
Message-ID: <12648671.post@talk.nabble.com> (raw)
In-Reply-To: <85940BCC-C5A7-4461-B49C-A5C1879708C3@kernel.crashing.org>
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
Kumar Gala-3 wrote:
>
>
> On Sep 12, 2007, at 11:18 PM, sivaji wrote:
>
>>
>> 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
>
> how are you connecting gdb to the board?
>
> do you have a JTAG debugger connected to the board?
>
> - k
>
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
>
>
--
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.
next prev parent reply other threads:[~2007-09-13 4:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-13 4:18 2.6.23-rc3 boot hang on MPC8641D sivaji
2007-09-13 4:25 ` Kumar Gala
2007-09-13 4:47 ` sivaji [this message]
2007-09-13 5:13 ` Kumar Gala
2007-09-13 5:59 ` Michael Ellerman
2007-09-13 4:38 ` Zhang Wei-r63237
2007-09-13 4:52 ` sivaji
2007-09-13 5:11 ` Kumar Gala
2007-09-13 5:19 ` Zhang Wei-r63237
2007-09-13 5:32 ` sivaji
2007-09-13 6:46 ` Zhang Wei-r63237
2007-09-14 14:25 ` sivaji
2007-09-13 5:24 ` sivaji
2007-09-13 5:29 ` David Gibson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=12648671.post@talk.nabble.com \
--to=rameshmrm@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.