Messages in this thread | | | From | "Nick Warne" <> | Date | Thu, 19 Feb 2004 20:04:27 -0000 | Subject | Re: 2.6.3 RT8139too NIC problems |
| |
> So, corrected (and as the kernel was built): > > # CONFIG_8139CP is not set > CONFIG_8139TOO=y > # CONFIG_8139TOO_PIO is not set > # CONFIG_8139TOO_TUNE_TWISTER is not set > # CONFIG_8139TOO_8129 is not set > # CONFIG_8139_OLD_RX_RESET is not set > CONFIG_8139_RXBUF_IDX=2
OK, I think there _is_ a problem here. I was suspecting my NFS setup maybe causing the NIC (eth0) to timeout and get reset, as I mount files from an old 486 -> 2.6.3 box.
But after messing about a bit, I checked the logs on my 2.4.24 box via SSH (AND eth1). It hung as issued #> pico /var/log/messages for about 3 seconds.. then came to life. So...
... in the logs on 2.6.3 box straight after:
Feb 19 19:33:13 Linux233 kernel: NETDEV WATCHDOG: eth1: transmit timed out Feb 19 19:33:13 Linux233 kernel: eth1: link up, 10Mbps, half-duplex, lpa 0x0000
Nick
-- "I am not Spock", said Leonard Nimoy. "And it is highly illogical of humans to assume so."
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |