From: Graeme Russ <graeme.russ@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: x86 - Boot hangs at Calibrating delay loop on AMD SC520
Date: Wed, 17 Mar 2010 23:42:51 +1100 [thread overview]
Message-ID: <4BA0CE4B.90508@gmail.com> (raw)
I now have U-Boot booting 2.6.33 (abandoned 32-bit Boot Protocol and got a
pseudo BIOS working)
During boot I was getting a warning at arch/x86/kernel/rtc.c:125 and the
kernel hung at Calibrating delay loop... Also, all boot messages have a
zero time-stamp.
I have tried a 2.4.37.9 kernel and get the same freeze calibrating the
delay loop.
I have tried with and without the AMD Elan Extended (non-PC) x86 platform
I first assumed that the RTC is not working - I wasn't initially doing
anything relating to the SC520 RTC in U-Boot. I have added initialisation
code (as per the ÉlanTMSC520 Microcontroller User’s Manual Order #22004B)
and confirmed that the RTC is working in the SC520.
If traced back how the delay loop is performed and that has led me to
arch/x86/lib/delay.c where I promptly got very lost.
Any ideas?
next reply other threads:[~2010-03-17 12:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 12:42 Graeme Russ [this message]
2010-03-20 1:22 ` [Fixed] x86 - Boot hangs at Calibrating delay loop on AMD SC520 Graeme Russ
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=4BA0CE4B.90508@gmail.com \
--to=graeme.russ@gmail.com \
--cc=linux-kernel@vger.kernel.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