public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shaun Jackman <sjackman@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: lkml <linux-kernel@vger.kernel.org>, Tejun Heo <htejun@gmail.com>,
	Jeff Garzik <jgarzik@pobox.com>,
	Jan Engelhardt <jengelh@linux01.gwdg.de>
Subject: Re: Trouble shooting a ten minute boot delay (SiI3112)
Date: Mon, 15 Aug 2005 15:34:04 -0700	[thread overview]
Message-ID: <7f45d939050815153448a44e0f@mail.gmail.com> (raw)
In-Reply-To: <1123901740.5296.100.camel@localhost.localdomain>

2005/8/12, Steven Rostedt <rostedt@goodmis.org>:
> Is the keyboard ever set up then? This is all happening before
> console_init (since that's when the prints start) and the early printk
> won't show anything before it parses the options.  For other
> architectures, I use to write out to the serial really early, just an
> 'x'. If you know how to do that, you could give it a try. Start at
> start_kernel in main hopefully you see the 'x'. If you do, keep moving
> it until you find where it's delaying.  Of course, this could be before
> start_kernel, then you're really screwed, unless you're good at doing
> the same in assembly (which I've done for MIPS, PPC and ARM, but never
> for x86).

Since each reboot takes ten minutes, this would be a tedious process.
Thanks for the suggestion though.

> > I compiled a vanilla 2.6.12.4 kernel, enabled EARLY_PRINTK and
> > rebooted with earlyprintk=vga. The kernel didn't display any extra
> > information before the delay.
> 
> Do you see grub saying "uncompressing kernel..." or whatever that says?

Grub says...

root (hd2,2)
  Filesystem type is ext2fs, partition type 0x83
kernel /boot/vmlinuz-2.6.12.4 root=/dev/md0 ro nodma
   [Linux-bzImage, setup=0x1e00, size=0x1302ff]

I suspect this second message is where grub decompresses the kernel.
The last message grub displays is simply...

boot

Cheers,
Shaun

  reply	other threads:[~2005-08-15 22:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-09 23:31 Trouble shooting a ten minute boot delay (SiI3112) Shaun Jackman
2005-08-12  2:47 ` Tejun Heo
2005-08-12  8:00   ` Shaun Jackman
2005-08-12  8:03     ` Jeff Garzik
2005-08-12 17:44       ` Shaun Jackman
2005-08-12 18:39         ` Jan Engelhardt
2005-08-12 19:08           ` Shaun Jackman
2005-08-12 19:14             ` Jan Engelhardt
2005-08-13  1:39               ` Shaun Jackman
2005-08-13  2:55                 ` Steven Rostedt
2005-08-15 22:34                   ` Shaun Jackman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-08-16 12:37 Etienne Lorrain

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=7f45d939050815153448a44e0f@mail.gmail.com \
    --to=sjackman@gmail.com \
    --cc=htejun@gmail.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.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