All of lore.kernel.org
 help / color / mirror / Atom feed
From: swamydp <swamydp@gmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: RE: linux 2.6 hangs at __delay function on Viretx 4 board
Date: Fri, 16 May 2008 07:56:50 -0700 (PDT)	[thread overview]
Message-ID: <17276753.post@talk.nabble.com> (raw)
In-Reply-To: <20080514150139.E258D8D006F@mail70-va3.bigfish.com>


John

Thanks for your suggestions.

 I looked up the virtual address for __log_buf in System.map and subtracted
0xc0000000 to get the physical address. I then reset the processor from XMD
and dump contents of the physical address of __log_buf using 'mrd' command
from XMD. All I see is bunch of zeros in those locations.

I am debugging but do not have much clue.

Swamy



John Linn wrote:
> 
> Hi Swamy,
> 
> I have seen this sometime before I think, but don't remember why.
> 
> I see that udelay depends on loops_per_jiffy, have you looked to see
> what value it is? Maybe it's garbage and some large value?
> 
> Have you tried dumping the __log_buf to understand how far it got thru
> booting the kernel before it got hung?
> 
> I assume you must be using xmd to load the image, you can also use it to
> dump the buffer.
> 
> On another processor I have seen it get hung in the calibrate_delay call
> from the kernel if the interrupts or timer aren't working, but haven't
> ever seen that on the Powerpc.
> 
> Thanks,
> John
> 
> 
> -----Original Message-----
> From: linuxppc-embedded-bounces+john.linn=xilinx.com@ozlabs.org
> [mailto:linuxppc-embedded-bounces+john.linn=xilinx.com@ozlabs.org] On
> Behalf Of swamydp
> Sent: Tuesday, May 13, 2008 9:29 PM
> To: linuxppc-embedded@ozlabs.org
> Subject: linux 2.6 hangs at __delay function on Viretx 4 board
> 
> 
> 
> I am trying to boot linux 2.6 on HITECH virtex 4(fx60) board. Linux
> hangs at
> address 0xc00045ec which is in the __udelay function. I am using EDK
> 9.2i
> and gcc version 4.0.2 for compiling the kernel. The following is the
> boot
> message from the bootloader. 
> 
> loaded at:     00400000 0054E19C
> board data at: 0054C120 0054C19C
> relocated to:  00404064 004040E0
> zimage at:     00404E55 0054B5B4
> avail ram:     0054F000 02000000
> 
> Linux/PPC load: console=ttyS0,9600 console=tty0 root=/dev/sda2
> Uncompressing Linux...done.
> Now booting the kernel
> 
> Any help is greatly appreciated. I have run out of ideas to fix this.
> 
> Thanks
> swamy
> 
> -- 
> View this message in context:
> http://www.nabble.com/linux-2.6-hangs-at-__delay-function-on-Viretx-4-bo
> ard-tp17222725p17222725.html
> Sent from the linuxppc-embedded mailing list archive at Nabble.com.
> 
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> 
> 
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> 
> 

-- 
View this message in context: http://www.nabble.com/linux-2.6-hangs-at-__delay-function-on-Viretx-4-board-tp17222725p17276753.html
Sent from the linuxppc-embedded mailing list archive at Nabble.com.

  reply	other threads:[~2008-05-16 14:56 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 [this message]
2008-05-16 16:28     ` John Linn
2008-05-25  5:35       ` swamydp
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=17276753.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 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.