RE: Weird: 30 sec delay during early boot

David Balazic
2004-07-05T07:22:51Z

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 already has a list of
"existing" drives.
Or maybe I'm flat out wrong ;-)

Regards,
David

> ----------
> From: Andries Brouwer[SMTP:aebr@win.tue.nl]
> Sent: 5. julij 2004 1:27
> To: Matt Domsch
> Cc: Jeff Garzik; Pavel Machek; Linux Kernel; Andi Kleen; Andrew Morton;
> David Balazic
> Subject: Re: Weird: 30 sec delay during early boot
>
> On Sun, Jul 04, 2004 at 03:52:51PM -0500, Matt Domsch wrote:
>
> > Only that it's now probing more than just the first disk, but the
> > first 16 possible BIOS disks. If the BIOS behaves badly to an int13
> > READ_SECTORS command, that'd be good to know...
>
> I recall text fragments like
>
> "Any device claiming compliance to ATA-3 or later as indicated in
> IDENTIFY DEVICE or IDENTIFY PACKET DEVICE data should properly
> release PDIAG- after a power-on or hardware reset upon receiving
> the first command or after 31 seconds have elapsed since the reset,
> whichever comes first."
>
> that seem to imply that probing a nonexistent device may take 31 sec
> before one is allowed to conclude that there is nothing there.
>
> Andries
>
>
> (ide_wait_hwif_ready() used to wait 35 seconds)
>