epic100 && >=2.3.99pre7 && ping -f == reproducible lockup

From: dart@iowaone.net
Date: Sat May 27 2000 - 01:35:55 EDT

  • Next message: H. Peter Anvin: "Re: any chance we could dump the 64k subdirectory limit before 2.4 ships?"

    2.3.99pre6 works fine, >= pre7 is broken
    2.4.0-test1 is current kernel

    Eth is generally broken, no communication with other hosts whatsoever.
    The hosts are on local lan with 192.168.1.xxx ip's. A ping -f to another
    host results in a hard lockup with the reset button the only option.
    I've tried "debug" on the boot command line and gdb with no joy. Strace
    will fail in poll([{fd=3, events=POLLIN|POLLERR}], 1, 10) = 0 with just
    "poll(" when it freezes. Both my hub and the remote host show no
    activity during the ping flood.

    Dmesg:
    epic100.c:v1.09+LK1.1.2 4/28/2000 Written by Donald Becker
    <becker@scyld.com>
            http://www.scyld.com/network/epic100.html
    eth0: SMSC EPIC/100 83c170 at 0xc901c000, IRQ 11, 00:e0:29:22:4f:18.
    eth0: MII transceiver #3 control 3000 status 7809.
    eth0: Autonegotiation advertising 01e1 link partner 0001.

    Any suggestion on how to get a better trace....? Standing ready to crash
    my machine repeatedly with extreme prejudice...

    -
    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 : Sat May 27 2000 - 01:24:53 EDT