Re: killall -9 does not work !?

From: Chris Faherty (rallymonkey@bellsouth.net)
Date: Wed May 24 2000 - 13:20:29 EDT

  • Next message: Damir Cosic: "Re: Possible bug in 2.2.14 IP code"

    On 24-May-2000 Alan Cox wrote:

    > If it hung in state 'd' then its a kernel bug. Try an unpatched kernel. If
    > you can get 2.2.15 wedging stuff in D state then I'd like to know

    I've gotten stuck processes pretty often ever since the first mandrake
    release -- i.e. never had them before except with driver problems. It was
    always xterms via rlogin that caused the xterms to hang and so it might have
    been some funky X stuff. That was happening each day but I no longer use
    this method so I can't say if the problem is still there.

    However with every kernel since that setup I still get processes that say DW
    maybe twice a week on my current system. This is a Stormix running
    2.2.16pre3. Right now I have a stuck bash that says:

    12621 ? DW 0:00 (bash)

    This is bash 2.01.1(1)-release from the 2.01.1-4.1 Debian package.

    Let me know if I can debug this somehow or give any useful information.

    /* Chris Faherty <rallymonkey@bellsouth.net> */
    /* Your Stock has crashed - you must now restart your system */

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.rutgers.edu
    Please read the FAQ at http://www.tux.org/lkml/



    This archive was generated by hypermail 2b29 : Wed May 24 2000 - 13:31:28 EDT