From: Abbas Dadabhoy <a.dadabhoy@aristoslogic.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Walnut405 PPC hang prob at linux startup
Date: Thu, 15 Jan 2004 09:44:51 -0800 [thread overview]
Message-ID: <4006D193.CAFA2B38@aristoslogic.com> (raw)
Hi
I am using u-boot 1.0.0, and am loading linux kernel at 400000, it
appears to hang after printing message
- "Warning: real time clock seems stuck!"
My linux kernel version is 2.4.18
I have put additional kprint in main.c and am able to track it down to
between the lines
. . .
kmem_cache_init();
sti();
. .
I have tried to set clocks_in_mhz to 1 through the setenv command and it
did not help.
I have already checked time.c and it is 1.35 11/28/01, and has the
following code
if (ppc_md.get_rtc_time) {
stamp = get_native_tbl();
sec = ppc_md.get_rtc_time();
elapsed = 0;
do {
old_stamp = stamp;
old_sec = sec;
stamp = get_native_tbl();
if (__USE_RTC() && stamp < old_stamp) old_stamp -=
1000000000;
elapsed += stamp - old_stamp;
sec = ppc_md.get_rtc_time();
} while ( sec == old_sec && elapsed < 2*HZ*tb_ticks_per_jiffy);
if (sec==old_sec) {
printk("Warning: real time clock seems stuck!\n");
}
write_lock_irqsave(&xtime_lock, flags);
xtime.tv_sec = sec;
last_jiffy_stamp(0) = tb_last_stamp = stamp;
xtime.tv_usec = 0;
/* No update now, we just read the time from the RTC ! */
last_rtc_update = xtime.tv_sec;
write_unlock_irqrestore(&xtime_lock, flags);
} else {
stamp = get_native_tbl();
last_jiffy_stamp(0) = tb_last_stamp = stamp;
}
I will appreciate any helpregarding this.
Thanks
A. Dadabhoy
next reply other threads:[~2004-01-15 17:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 17:44 Abbas Dadabhoy [this message]
2004-01-15 18:08 ` [U-Boot-Users] Walnut405 PPC hang prob at linux startup Wolfgang Denk
2004-01-15 18:21 ` Abbas Dadabhoy
-- strict thread matches above, loose matches on Subject: below --
2004-01-15 18:43 Rune Torgersen
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=4006D193.CAFA2B38@aristoslogic.com \
--to=a.dadabhoy@aristoslogic.com \
--cc=u-boot@lists.denx.de \
/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