All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Arun Thomas <arun.thomas@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: PROBLEM: E6850 has an 8+ minute delay during boot
Date: Fri, 14 Dec 2007 11:18:23 +0100	[thread overview]
Message-ID: <4762586F.8090603@gmail.com> (raw)
In-Reply-To: <9a8cbed90712140201r6cb287d9w99cc1210c68e8e60@mail.gmail.com>

On 12/14/2007 11:01 AM, Arun Thomas wrote:
> On Dec 14, 2007 4:53 AM, Andrew Morton <akpm@linux-foundation.org> wrote:
>> On Fri, 14 Dec 2007 04:10:31 -0500 "Arun Thomas" <arun.thomas@gmail.com> wrote:
>>

some time before:
[   20.101392] Calibrating delay using timer specific routine..
5989.01 BogoMIPS (lpj=11978034)

>>> [   20.185881] Initializing CPU#1
>>> [  527.926587] Calibrating delay using timer specific routine..
>>> 200566.59 BogoMIPS (lpj=401133185)
>> Silly question: is that delay actually observeable by a human,
>> or is it just a leap in the printk timestamping?
> 
> Good question. Yes, it's human-observable. The kernel "hangs" for  8
> mins by my wall clock, and then it continues to boot up.

By the way, the same processor here, but
Calibrating delay using timer specific routine.. 5984.76 BogoMIPS (lpj=11969527)
for the second core.

The calibration is some kind of weird there.

If any info needed from me, feel free to ask (x86_64 here). No problems with it
here AFAIK.

  reply	other threads:[~2007-12-14 10:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-14  9:10 PROBLEM: E6850 has an 8+ minute delay during boot Arun Thomas
2007-12-14  9:53 ` Andrew Morton
2007-12-14 10:01   ` Arun Thomas
2007-12-14 10:18     ` Jiri Slaby [this message]
2007-12-14 10:43       ` Thomas Gleixner
2007-12-14 11:15         ` Arun Thomas
2007-12-14 14:44         ` Mark Lord
2007-12-14 19:01         ` H. Peter Anvin
2007-12-15  0:00           ` Arun Thomas
2007-12-15  0:38             ` H. Peter Anvin
2007-12-14 14:38 ` Mark Lord
2007-12-15  6:07 ` Len Brown
2007-12-16  5:38   ` Arun Thomas

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=4762586F.8090603@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=arun.thomas@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.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 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.