> First, run tulip with debug 2. If it is a module, insmod tulip debug=2.
> If builtin, compile with -DTULIP_DEBUG=2.
> When it hangs, what does the tulip-diag program report? Run as
> tulip-diag -fame -p 0xb800.
> http://cesdis.gsfc.nasa.gov/linux/diag/tulip-diag.c.
I'm waiting for one of the machines that I've configured with DEBUG=2 to
drop off the network. I'll get this information as soon as that happens.
> Instead of ifconfig down/up, does
> ifconfig eth0 promisc
> ifconfig eth0 -promisc
> fix the problem? If so, I probably have a fix for you.
I tried this on another machine that dropped off the network (but I hadn't
installed tulip-diag nor had I configured DEBUG=2 on that one). Didn't
help--only ifconfig down/up helped.
Brian
-
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/