public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shaun Jackman <sjackman@gmail.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Tejun Heo <htejun@gmail.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: Trouble shooting a ten minute boot delay (SiI3112)
Date: Fri, 12 Aug 2005 10:44:53 -0700	[thread overview]
Message-ID: <7f45d93905081210441e209e31@mail.gmail.com> (raw)
In-Reply-To: <42FC57EC.2060204@pobox.com>

2005/8/12, Jeff Garzik <jgarzik@pobox.com>:
> > At this point there is a nine minute, fifteen second delay. As soon as
> > the kernel starts printing messages it goes by quite fast, so I can't
> > be certain what it's printing, but the first message according to
> > dmesg is...
> > Linux version 2.6.11-1-k7 (dannf@firetheft) (gcc version 3.3.6 (Debian 1:3.3.6-6
> > )) #1 Mon Jun 20 21:26:23 MDT 2005
> > BIOS-provided physical RAM map:
> 
> It's doing something BIOS-related at that point.
> 
> Try booting with 'edd=off' or disabling CONFIG_EDD.

Thanks for the hint. I tried edd=off but sadly the boot delay
persists. It looks as though edd was already disabled, as my .config
contains CONFIG_EDD=m and the edd module is not loaded. If it helps
troubleshooting I can post my .config here.

Cheers,
Shaun

  reply	other threads:[~2005-08-12 17:45 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 [this message]
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
  -- 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=7f45d93905081210441e209e31@mail.gmail.com \
    --to=sjackman@gmail.com \
    --cc=htejun@gmail.com \
    --cc=jgarzik@pobox.com \
    --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