From: Jeff Garzik <jgarzik@pobox.com>
To: Pavel Machek <pavel@suse.cz>, Matt Domsch <Matt_Domsch@dell.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Andi Kleen <ak@suse.de>, Andrew Morton <akpm@osdl.org>
Subject: Re: Weird: 30 sec delay during early boot
Date: Sun, 04 Jul 2004 13:33:07 -0400 [thread overview]
Message-ID: <40E83F53.3050006@pobox.com> (raw)
In-Reply-To: <20040704063321.GB5054@openzaurus.ucw.cz>
Pavel Machek wrote:
> Hi!
>
>
>>This appeared in -bk-latest in the past day or two.
>>
>>BK-current on x86-64 (config/dmesg/lspci attached) will pause for 30
>>wall-clock seconds immediately after being loaded by the bootloader,
>>then will proceed to boot successfully and function correctly. This
>>is reproducible on every boot.
>>
>>So, 30 seconds with no printk output, then boots normally.
>>
>
>
> Search archives, there was something similar seen before.
> It was related to EDD, or some similar BIOS feature, IIRC.
Thank you for the hint!
I verified that changing CONFIG_EDD=y to '# CONFIG_EDD is not set'
removed the 30-second pause at boot.
This 30-second pause only appeared recently on my x86-64 box (VIA-based
Athlon64), so I'll bsearch changesets when I get a free moment (sometime
this week).
I wonder, even, if it is related to the bootsetup.h fix from Matt that I
forwarded recently.
Jeff
next prev parent reply other threads:[~2004-07-04 17:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-04 2:34 Weird: 30 sec delay during early boot Jeff Garzik
2004-07-04 6:33 ` Pavel Machek
2004-07-04 17:33 ` Jeff Garzik [this message]
2004-07-04 20:52 ` Matt Domsch
2004-07-04 23:27 ` Andries Brouwer
2004-07-05 13:31 ` Matt Domsch
2004-07-05 18:04 ` EDD results (was Re: Weird: 30 sec delay during early boot) Jeff Garzik
2004-07-05 18:06 ` Jeff Garzik
[not found] <2e55c-392-7@gated-at.bofh.it>
2004-07-04 2:47 ` Weird: 30 sec delay during early boot Andi Kleen
2004-07-04 2:52 ` Jeff Garzik
2004-07-04 3:23 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2004-07-05 7:21 David Balazic
2004-07-05 11:25 ` Dave Jones
2004-07-05 11:30 David Balazic
2004-07-13 22:16 ` Matt Domsch
2004-07-13 22:35 ` Jeff Garzik
2004-07-14 2:32 ` Matt Domsch
2004-07-14 3:03 ` Matt Domsch
2004-07-14 3:18 ` Jeff Garzik
2004-07-28 12:16 David Balazic
2004-07-28 12:40 ` Matt Domsch
2004-07-29 13:05 David Balazic
2004-07-29 16:02 ` Matt Domsch
2004-07-30 12:52 David Balazic
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=40E83F53.3050006@pobox.com \
--to=jgarzik@pobox.com \
--cc=Matt_Domsch@dell.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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.