[lkml]   [2012]   [Jul]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: long boot delays caused by 070ad7e7 floppy change
    On Tue, Jul 3, 2012 at 10:50 AM, Linus Torvalds
    <> wrote:
    > It looks like the code meant for -1 to mean "regular delay"
    > (current_reqD), and -2 to mean MAXTIMEOUT. For some reason the "-1"
    > logic has gotten screwed.

    So it looks like current_reqD still exists, and sets the drive to
    "current_drive". Which *should* be 0, as far as I can tell. In fact,
    since "current_drive" is printed out by DPRINTK(), we *know* it's 0
    (it's the "0" in the "floppy0:" message).

    But how the heck does it pick that bogus 20 second delay then? The -1
    should have been caught by

    if (drive == current_reqD)
    drive = current_drive;

    and then we should have used the regular delay for drive 0.

    Jiri, any ideas?


     \ /
      Last update: 2012-07-03 20:41    [W:0.021 / U:0.060 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site