From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sithglan@stud.informatik.uni-erlangen.de>
Received: from faui03.informatik.uni-erlangen.de
	(faui03.informatik.uni-erlangen.de [131.188.30.103])
	by ozlabs.org (Postfix) with ESMTP id 09EE8DDDEB
	for <linuxppc-embedded@ozlabs.org>;
	Fri, 22 Jun 2007 01:15:55 +1000 (EST)
Date: Thu, 21 Jun 2007 17:15:54 +0200
From: Thomas Glanzmann <thomas@glanzmann.de>
To: linuxppc-embedded@ozlabs.org
Subject: Virtex4FX12LC hangs in calibrating delay loop
Message-ID: <20070621151554.GA22663@cip.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
List-Id: Linux on Embedded PowerPC Developers Mail List
	<linuxppc-embedded.ozlabs.org>
List-Unsubscribe: <https://ozlabs.org/mailman/listinfo/linuxppc-embedded>,
	<mailto:linuxppc-embedded-request@ozlabs.org?subject=unsubscribe>
List-Archive: <http://ozlabs.org/pipermail/linuxppc-embedded>
List-Post: <mailto:linuxppc-embedded@ozlabs.org>
List-Help: <mailto:linuxppc-embedded-request@ozlabs.org?subject=help>
List-Subscribe: <https://ozlabs.org/mailman/listinfo/linuxppc-embedded>,
	<mailto:linuxppc-embedded-request@ozlabs.org?subject=subscribe>

Hello,
I used the HEAD secretlabs kernel and used ml403 defconfig. I still see
no serial output from the _kernel_ on the serial console. But I do see
output from the in kernel embedded boot loader "load_kernel". I typed in
stop in xmd and got an instruction pointer which points to:

        c00045a0 <__delay>:
        c00045a0:       2c 03 00 00     cmpwi   r3,0
        c00045a4:       7c 69 03 a6     mtctr   r3
        c00045a8:       4d 82 00 20     beqlr
        c00045ac:       42 00 00 00     bdnz-   c00045ac <__delay+0xc>       <<<<<<<<
        c00045b0:       4e 80 00 20     blr

So I guess it is the calibrating delay loop and I am not sure. I can reproduce
this. It is always in this function. Now I wonder is my board missing
timer interrupts? What could be the reason for this. And of course one
much more important question:

        - Is the serial console initialized before or after the
          calibrating delay loop?

Is there a way to get a backtrace out of this? If that is the case what
do I have to do? Recompile the Kernel with frame pointers and attach
gdb?

        Thomas