[lkml]   [2003]   [Jun]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: Linux 2.4.21-rc7
    > Now I really hope its the last one, all this
    > rc's are making me mad.

    We still have ide problems, and I don't see any
    potential fixes for that in the changelog between -rc6 and -rc7.

    I tried -rc6 on a whim and had hda report
    a timeout (dma, I think, but the message went by kind of quick), then the big freeze with the
    disk light stuck on, Never happened
    in 6 months on the same hardware running
    2.4.19-rc2 (with glibc-2.2.5, gcc-2.95.3,
    binutils-, all ext2 filesystems).

    I recompiled with all kernel debugging options
    enabled and disabled partition statistics, since that was the one thing that was obviously new about the enabled ide options (I didn't select
    any other new options, but of course the kernel code underneath is probably different, so one could not conclude anything from suck meager
    testing). It ran for about 8 hours without freezing, with that drive doing a lot more
    work than it was doing when it livelocked.

    e2fsck reported errors on the next reboot, though,
    and it's been rebooted into 2.4.19-rc2 to get some
    other work done with it since then (caching the source for an upgrade of a 2.2.x box, different libc, yada yada, needs to be reliable until
    that is finished).

    SiS530/5513, k6-II/450, udma33 Maxtor drive that 2.4.19-rc2 has no problems with.

    You can release a 2.4.21 anyway, of course, but without finding out where the ide livelock (and other big freezes, thinking of the report on the all-scsi system already posted) originates, calling it "stable" would be a bit fanciful.

    (2.4.19-rc2 has its own quirks, of course, but
    not "single-threaded ide livelock with this
    chipset and ide drive". I can reliably kill it with 32 threads depth-first scanning different directory trees on that same disk in parallel, unfortunately without an oops to show for it.
    It is not running out of memory (no ENOMEM reports), merely some mundane race condition or missing lock or whatever. Change it to 32 forks running in parallel, and they finish normally, though of course not all that quickly while seek-thrashing one and the same disk between them.)

    Not what you wanted to hear, right? Oh well.

    (Better to find out sooner than release
    2.4.21-stable and watch 52 different bug reports on it arrive at the list the next day.)


    Clayton Weaver

    Sign-up for your own FREE Personalized E-mail at

    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 13:36    [W:0.022 / U:5.940 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site