From: Matt Domsch <Matt_Domsch@dell.com>
To: David Balazic <david.balazic@hermes.si>
Cc: Dave Jones <davej@redhat.com>, Andries Brouwer <aebr@win.tue.nl>,
Jeff Garzik <jgarzik@pobox.com>, Pavel Machek <pavel@suse.cz>,
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: Thu, 29 Jul 2004 11:02:18 -0500 [thread overview]
Message-ID: <20040729160218.GA20901@lists.us.dell.com> (raw)
In-Reply-To: <B1ECE240295BB146BAF3A94E00F2DBFF090202@piramida.hermes.si>
[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]
On Thu, Jul 29, 2004 at 03:05:10PM +0200, David Balazic wrote:
> > David, you had said before that by downgrading your BIOS you no longer
> > saw the delay. Is this not still true?
> >
> Still true, downgrading removes the delay.
OK, then I'm inclined to believe it's a BIOS bug really...
> > You also mentioned that Grub made different calls. I'll check that
> > out too.
> >
> Can you make a patch, that only accesses hd0 and hd1 ?
Reduce the value of
#define EDD_MBR_SIG_MAX 16
in include/linux/edd.h to whatever value you like, e.g. 2.
> Or one which prints what is it doing, on each step ?
> ( I tried this one myself, but it did not work :blush: , IA32 assembler
> is not my strong side )
That's more PITA - it's in real mode, before anything's ever been
printed. I'd prefer not to have to figure that out if I can avoid it.
Thanks,
Matt
--
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-07-29 16:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-29 13:05 Weird: 30 sec delay during early boot David Balazic
2004-07-29 16:02 ` Matt Domsch [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-30 12:52 David Balazic
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
[not found] <2e55c-392-7@gated-at.bofh.it>
2004-07-04 2:47 ` Andi Kleen
2004-07-04 2:52 ` Jeff Garzik
2004-07-04 3:23 ` Andi Kleen
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=20040729160218.GA20901@lists.us.dell.com \
--to=matt_domsch@dell.com \
--cc=aebr@win.tue.nl \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=david.balazic@hermes.si \
--cc=jgarzik@pobox.com \
--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.