2.6.3 RT8139too NIC problems
Hello all,
Due to traffic restraints, I am not on the lkml - please CC replies.
Yesterday I built 2.6.3. Clean build, and system runs nice.
I have two NIC's in the box, both rt8139.
But I noticed I am getting this in syslogs:
Linux233 kernel: NETDEV WATCHDOG: eth1: transmit timed out Linux233 kernel: eth1: link up, 10Mbps, half-duplex, lpa 0x0000 Linux233 kernel: nfs: server 486Linux not responding, still trying Linux233 kernel: nfs: server 486Linux not responding, still trying Linux233 kernel: NETDEV WATCHDOG: eth0: transmit timed out Linux233 kernel: nfs: server 486Linux OK
Linux233 kernel: nfs: server 486Linux OK
Linux233 kernel: nfs: server 486Linux not responding, still trying Linux233 kernel: NETDEV WATCHDOG: eth0: transmit timed out Linux233 kernel: nfs: server 486Linux OK
This happens about once every 3 hours.
Quoted 1 line
From my config file:
# CONFIG_8139CP is not setCONFIG_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= is not set
No other NIC drivers are used.
I am also stuck as to what the new RXBUF_IDX is for. It appears the new build needs it, as I cannot remove.
These cards have worked fine under all 2.4.x and 2.6.1/2.6.2 kernels.
Ideas?
TIA,
Nick
Signature · 2 lines
"I am not Spock", said Leonard Nimoy. "And it is highly illogical of humans to assume so."
Quoted 10 lines · Nick Warne
Quoted 1 line
From my config file:
#
CONFIG_8139CPis not setCONFIG_8139TOO=y
#CONFIG_8139TOO_PIOis not set
#CONFIG_8139TOO_TUNE_TWISTERis not set
#CONFIG_8139TOO_8129is not set
#CONFIG_8139_OLD_RX_RESETis not set
#CONFIG_8139_RXBUF_IDX=is not set
Quoted 5 lines
No other NIC drivers are used.
I am also stuck as to what the new
RXBUF_IDXis for. It appears the new build needs it, as I cannot remove.
So read the help entry in Kconfig. Before this change went in, pretty much everyone defaulted to a 32k receive ring size, which is also the current default. If you had used the default value of 2 instead of trying to hack around it, you might get better behavior from your driver..
Quoted 14 lines · Nick Warne
Quoted 12 lines
Quoted 1 line
From my config file:
#
CONFIG_8139CPis not setCONFIG_8139TOO=y
#CONFIG_8139TOO_PIOis not set
#CONFIG_8139TOO_TUNE_TWISTERis not set
#CONFIG_8139TOO_8129is not set
#CONFIG_8139_OLD_RX_RESETis not set
#CONFIG_8139_RXBUF_IDX=is not setNo other NIC drivers are used.
Quoted 7 lines
Quoted 3 lines
I am also stuck as to what the new
RXBUF_IDXis for. It appears the new build needs it, as I cannot remove.So read the help entry in
Kconfig. Before this change went in, pretty much everyone defaulted to a 32k receive ring size, which is also the current default. If you had used the default value of 2 instead of trying to hack around it, you might get better behavior from your driver..
Hi Paul,
My bad...
I did use the default 2... unfortunately that snippet I copied here was what I tried to do to rebuild kernel with out it, but make just adds the line back in CONFIG and asks what option I what.
So it is set to 2 as per the default.
So, corrected (and as the kernel was built):
# CONFIG_8139CP is not setCONFIG_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 setCONFIG_8139_RXBUF_IDX=2
Nick
Signature · 2 lines
"I am not Spock", said Leonard Nimoy. "And it is highly illogical of humans to assume so."
Quoted 10 lines · Nick Warne
Hello all,
Due to traffic restraints, I am not on the lkml - please CC replies.
Yesterday I built 2.6.3. Clean build, and system runs nice.
I have two NIC's in the box, both rt8139.
But I noticed I am getting this in syslogs:
Quoted 10 lines
Linux233 kernel: NETDEV WATCHDOG: eth1: transmit timed out Linux233 kernel: eth1: link up, 10Mbps, half-duplex, lpa
0x0000Linux233 kernel: nfs: server 486Linux not responding, still trying Linux233 kernel: nfs: server 486Linux not responding, still trying Linux233 kernel: NETDEV WATCHDOG: eth0: transmit timed out Linux233 kernel: nfs: server 486Linux OK
Linux233 kernel: nfs: server 486Linux OK
Linux233 kernel: nfs: server 486Linux not responding, still trying Linux233 kernel: NETDEV WATCHDOG: eth0: transmit timed out Linux233 kernel: nfs: server 486Linux OK
This is usually irq routing related... Try booting with 'noapic' or similar.
Jeff
Quoted 12 lines
Quoted 10 lines
Linux233 kernel: NETDEV WATCHDOG: eth1: transmit timed out Linux233 kernel: eth1: link up, 10Mbps, half-duplex, lpa
0x0000Linux233 kernel: nfs: server 486Linux not responding, still trying Linux233 kernel: nfs: server 486Linux not responding, still trying Linux233 kernel: NETDEV WATCHDOG: eth0: transmit timed out Linux233 kernel: nfs: server 486Linux OK
Linux233 kernel: nfs: server 486Linux OK
Linux233 kernel: nfs: server 486Linux not responding, still trying Linux233 kernel: NETDEV WATCHDOG: eth0: transmit timed out Linux233 kernel: nfs: server 486Linux OK
Quoted 2 lines
This is usually irq routing related... Try booting with 'noapic' or similar.
I don't have apic built in the kernel. This has only started to happen on 2.6.3. As I said, on all other kernels, 2.4.x, 2.6.0, 2.6.1, 2.6.2 these NIC are OK.
With 2.6.3 my logs are now riddled with these messages (and the period is totally random - sometimes 10 times in an hour), and I lose connectivity during these periods.
I will be booting back into 2.6.2 tonight until I can resolve this.
Nick
Signature · 2 lines
"I am not Spock", said Leonard Nimoy. "And it is highly illogical of humans to assume so."