From: swamydp <swamydp@gmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: RE: linux 2.6 hangs at __delay function on Viretx 4 board
Date: Sat, 24 May 2008 22:35:22 -0700 (PDT) [thread overview]
Message-ID: <17454696.post@talk.nabble.com> (raw)
In-Reply-To: <20080516162807.2132E181804D@mail89-sin.bigfish.com>
Hi John
Sorry for getting back late.
I have been debugging further using the UART to send output directly to
serial post. Now I see that just after entering start_kernel, a ITLB miss
exception occurs and linux hangs at that point.
Looks like the kernel is probably not running at all yet, may stuck in
early initialization.
>> Yes
1. Has the kernel ever ran on this board or is this development to get
it running?
>> No. This is a new board and I am trying to build a simple EDK system with
>> only
PPC, UART, PIC as the devices.
2. Not sure on the tools you are using to build it. You mention the
EDK, but you must not be using it's compiler as it's not configured in
the EDK to build Linux.
>> EDK 9.2 version, XMD for debug. Kernel 2.6 version is built in linux
>> machine and zImage.elf is downloaded
to the board.
Thanks for the UART suggestion, works well. Any suggestions as to what might
be wrong in start_kernel function ? I will continue debugging meanwhile.
Thanks
swamy
--
View this message in context: http://www.nabble.com/linux-2.6-hangs-at-__delay-function-on-Viretx-4-board-tp17222725p17454696.html
Sent from the linuxppc-embedded mailing list archive at Nabble.com.
next prev parent reply other threads:[~2008-05-25 5:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 3:29 linux 2.6 hangs at __delay function on Viretx 4 board swamydp
2008-05-14 15:01 ` John Linn
2008-05-16 14:56 ` swamydp
2008-05-16 16:28 ` John Linn
2008-05-25 5:35 ` swamydp [this message]
2008-05-27 4:11 ` swamydp
2008-05-28 14:07 ` John Linn
2008-06-04 3:00 ` swamydp
2008-06-04 8:55 ` Peter Korsgaard
2008-06-04 21:22 ` John Linn
2008-06-04 21:31 ` Peter Korsgaard
2008-06-04 21:44 ` Howard, Marc
2008-06-04 23:18 ` Stephen Neuendorffer
2008-06-19 16:33 ` swamydp
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=17454696.post@talk.nabble.com \
--to=swamydp@gmail.com \
--cc=linuxppc-embedded@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).