From: Jeff Garzik <jgarzik@pobox.com>
To: Andi Kleen <ak@muc.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Weird: 30 sec delay during early boot
Date: Sat, 03 Jul 2004 22:52:58 -0400 [thread overview]
Message-ID: <40E7710A.4020601@pobox.com> (raw)
In-Reply-To: <m3hdsoebe8.fsf@averell.firstfloor.org>
Andi Kleen wrote:
> Jeff Garzik <jgarzik@pobox.com> writes:
>
>
>>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.
>
>
> Boot with earlyprintk=serial,ttySx,baud or earlyprintk=vga
> That should enable printk from the beginning and may give
> some clues.
would early printk show something that dmesg(8) would not?
Jeff
next prev parent reply other threads:[~2004-07-04 2:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2004-07-04 3:23 ` Andi Kleen
2004-07-30 12:52 David Balazic
-- strict thread matches above, loose matches on Subject: below --
2004-07-29 13:05 David Balazic
2004-07-29 16:02 ` Matt Domsch
2004-07-28 12:16 David Balazic
2004-07-28 12:40 ` Matt Domsch
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-05 7:21 David Balazic
2004-07-05 11:25 ` Dave Jones
2004-07-04 2:34 Jeff Garzik
2004-07-04 6:33 ` Pavel Machek
2004-07-04 17:33 ` Jeff Garzik
2004-07-04 20:52 ` Matt Domsch
2004-07-04 23:27 ` Andries Brouwer
2004-07-05 13:31 ` Matt Domsch
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=40E7710A.4020601@pobox.com \
--to=jgarzik@pobox.com \
--cc=ak@muc.de \
--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