[lkml]   [2004]   [Jul]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: Weird: 30 sec delay during early boot
    On Mon, 5 Jul 2004, Andries Brouwer wrote:

    > 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.

    I wonder if, for our purposes, we could first issue the int13 fn41 (check
    extensions present) as we do before calling fn48 later. This doesn't read
    the disk itself, and hopefully can return immediately with a failure on
    the nonexistant device, thus we can stop before reading the MBR. No one
    has indicated that the fn41 or fn48 code causes any delay, only the fn02
    (read sectors)...

    Matt Domsch
    Sr. Software Engineer, Lead Engineer
    Dell Linux Solutions &
    Linux on Dell mailing lists @

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 14:04    [W:0.019 / U:0.260 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site