> With the new networking changes, a bad assumption about the xcvr will not
> lead one into that "sanity-checking" timeout loop, since
> "test_bit(LINK_STATE_XOFF, &dev->state)" happily stays at 0 and that code
> is never executed. Explicitly setting the xcvr to 1 as a module option
> was the fix! And while at it, one may as well set the "io=" option
> explicitly as well... :)
You found a bug in the 3c503 driver yes. The softnet stuff has broken the
transceiver changing stuff
-
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 Feb 23 2000 - 21:00:19 EST