From: Andrew Morton <akpm@linux-foundation.org>
To: "Arun Thomas" <arun.thomas@gmail.com>
Cc: 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 01:53:15 -0800 [thread overview]
Message-ID: <20071214015315.09829a99.akpm@linux-foundation.org> (raw)
In-Reply-To: <9a8cbed90712140110l156a34e3x38533b7710544cf8@mail.gmail.com>
On Fri, 14 Dec 2007 04:10:31 -0500 "Arun Thomas" <arun.thomas@gmail.com> wrote:
> My Dell Vostro desktop w/ an Intel E6850 dual-core 3GHz CPU has an 8+
> minute delay during boot. The machine seems to run fine after it
> boots. The problem occurs on the Ubuntu gutsy 2.6.22-14 kernel,
> 2.6.23.9, and 2.6.24-rc5. I have upgraded to the most recent Dell BIOS
> version (1.0.8). I am running an SMP kernel currently, but the problem
> presents itself in uniprocessor mode (nosmp) also. I'm running the
> machine in 32-bit mode w/hyperthreading configured.
>
> Here are a few interesting things in the dmesg output for the
> 2.6.24-rc5 kernel (smp). The full dmesg is also included farther down.
>
> [ 20.101501] CPU: After generic identify, caps: bfebfbff 20100000
> 00000000 00000000 0000e3fd 00000000 00000001 00000000
> [ 20.101505] monitor/mwait feature present.
> [ 20.101506] using mwait in idle threads.
> [ 20.101508] CPU: L1 I cache: 32K, L1 D cache: 32K
> [ 20.101509] CPU: L2 cache: 4096K
> [ 20.101511] CPU: Physical Processor ID: 0
> [ 20.101511] CPU: Processor Core ID: 0
> [ 20.101513] CPU: After all inits, caps: bfebfbff 20100000 00000000
> 00003940 0000e3fd 00000000 00000001 00000000
> [ 20.101517] Compat vDSO mapped to ffffe000.
> [ 20.101525] Checking 'hlt' instruction... OK.
> [ 20.117651] SMP alternatives: switching to UP code
> [ 20.118574] ACPI: Core revision 20070126
> [ 20.175154] CPU0: Intel(R) Core(TM)2 Duo CPU E6850 @ 3.00GHz stepping 0b
> [ 20.175163] SMP alternatives: switching to SMP code
> [ 20.175437] Booting processor 1/1 eip 3000
> [ 20.185881] Initializing CPU#1
> [ 527.926587] Calibrating delay using timer specific routine..
> 200566.59 BogoMIPS (lpj=401133185)
> [ 527.926592] CPU: After generic identify, caps: bfebfbff 20100000
> 00000000 00000000 0000e3fd 00000000 00000001 00000000
> [ 527.926595] monitor/mwait feature present.
> [ 527.926596] CPU: L1 I cache: 32K, L1 D cache: 32K
> [ 527.926597] CPU: L2 cache: 4096K
> [ 527.926599] CPU: Physical Processor ID: 0
Silly question: is that delay actually observeable by a human,
or is it just a leap in the printk timestamping?
next prev parent reply other threads:[~2007-12-14 9:53 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 [this message]
2007-12-14 10:01 ` Arun Thomas
2007-12-14 10:18 ` Jiri Slaby
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=20071214015315.09829a99.akpm@linux-foundation.org \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox