From: Dave Jones <davej@redhat.com>
To: David Balazic <david.balazic@hermes.si>
Cc: Matt Domsch <Matt_Domsch@dell.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: Mon, 5 Jul 2004 12:25:21 +0100 [thread overview]
Message-ID: <20040705112521.GA18201@redhat.com> (raw)
In-Reply-To: <600B91D5E4B8D211A58C00902724252C035F1CB0@piramida.hermes.si>
On Mon, Jul 05, 2004 at 09:21:34AM +0200, David Balazic wrote:
> Wouldn't the BIOS immediatelly respond with a "no such disk" error if int13
> would
> try to access a non-existing disk ?
> This is BIOS land, not hardware land.
The BIOS guys get their stash from a different dealer to the hardware guys.
Screwups happen. It could just be yet another 'interesting' interpretation
of specifications.
Dave
next prev parent reply other threads:[~2004-07-05 11:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-05 7:21 Weird: 30 sec delay during early boot David Balazic
2004-07-05 11:25 ` Dave Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-30 12:52 David Balazic
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
[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=20040705112521.GA18201@redhat.com \
--to=davej@redhat.com \
--cc=Matt_Domsch@dell.com \
--cc=aebr@win.tue.nl \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--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.