eth1 (realtek) timeouts

[ssamartzis]

Hello,
I have setup a new untangle 8.1.1 installation(32bit) in a compaq eu100 sff box. It has an internal pci-e ethernet controller (realtek) and I bought an additional one (realtek based) so I can make this box a router. Everything is the setup went fine and the box is live. Unfortunatelly looking at the log files I see that there are timeouts in the eth1 interface(internal 1GB link).
The message is (with cat/var/log/messages) :
---
May 29 17:27:34 apexwall kernel: [109661.715189] r8169: eth1: link up
May 29 17:38:22 apexwall kernel: [110446.458770] NETDEV WATCHDOG: eth1: transmit
timed out
May 29 17:38:22 apexwall kernel: [110446.701037] r8169: eth1: link up
May 29 17:38:34 apexwall kernel: [110460.858779] NETDEV WATCHDOG: eth1: transmit
timed out
May 29 17:38:34 apexwall kernel: [110461.152057] r8169: eth1: link up
May 29 17:38:46 apexwall kernel: [110474.832413] NETDEV WATCHDOG: eth1: transmit
timed out
May 29 17:38:46 apexwall kernel: [110475.105670] r8169: eth1: link up
---

in kern.log there is an error logged as:
May 28 20:26:33 apexwall kernel: [13221.352015] NETDEV WATCHDOG: eth1: transmit timed out
May 28 20:26:33 apexwall kernel: [13221.352031] ------------[ cut here ]------------
May 28 20:26:33 apexwall kernel: [13221.352036] WARNING: at net/sched/sch_generic.c:222 dev_watchdog+0x92/0xe3()
May 28 20:26:33 apexwall kernel: [13221.352041] Modules linked in: ipt_ULOG ipt_set ip_set_iphash ip_set ipt_addrtype xt_NFQUEUE xt_NOTRACK iptable_raw ipt_REDIRECT tun nfnetlink_queue dummy nf_nat_tftp nf_nat_sip nf_nat_pptp nf_nat_h323 nf_nat_amanda nf_nat_snmp_basic nf_nat_proto_gre nf_nat_irc nf_nat_ftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_irc nf_conntrack_ftp nf_conntrack_proto_sctp nf_conntrack_netlink nfnetlink ts_kmp nf_conntrack_amanda nf_conntrack_tftp nf_conntrack_proto_gre nf_conntrack_netbios_ns nf_conntrack_h323 xt_physdev xt_IMQ iptable_tune xt_multiport ipt_MASQUERADE xt_state ipt_REJECT xt_mark iptable_filter xt_connmark xt_conntrack iptable_nat nf_nat xt_CONNMARK xt_MARK iptable_mangle ip_tables n22xxed igb dca loop evdev button serio_raw psmouse i2c_i801 i2c_core pcspkr snd_hda_intel snd_pcm snd_timer snd soundcore snd_page_alloc ext3 jbd mbcache sg sd_mod sr_mod cdrom usb_storage ide_pci_generic ide_core ata_generic ata_piix ehci_hcd uhci_hcd libata usbcore scsi_mod dock r8169 therma
May 28 20:26:33 apexwall kernel: l processor fan thermal_sys [last unloaded: scsi_wait_scan]
May 28 20:26:33 apexwall kernel: [13221.352171] Pid: 0, comm: swapper Not tainted 2.6.26-2-untangle-686 #1
May 28 20:26:33 apexwall kernel: [13221.352208] [<c012461f>] warn_on_slowpath+0x41/0x6b
May 28 20:26:33 apexwall kernel: [13221.352297] [<c0138468>] ? sched_clock_cpu+0x10b/0x11a
May 28 20:26:33 apexwall kernel: [13221.352329] [<c013788a>] ? up+0x2b/0x2f
May 28 20:26:33 apexwall kernel: [13221.352358] [<c0124b0f>] ? release_console_sem+0x182/0x18a
May 28 20:26:33 apexwall kernel: [13221.352435] [<c012bf39>] ? lock_timer_base+0x1f/0x3e
May 28 20:26:33 apexwall kernel: [13221.352478] [<c012c05b>] ? __mod_timer+0x9c/0xa7
May 28 20:26:33 apexwall kernel: [13221.352530] [<c0131df4>] ? queue_delayed_work_on+0xa1/0xae
May 28 20:26:33 apexwall kernel: [13221.352573] [<c0131e2f>] ? queue_delayed_work+0x1b/0x1e
May 28 20:26:33 apexwall kernel: [13221.352598] [<c0131e43>] ? schedule_delayed_work+0x11/0x13
May 28 20:26:33 apexwall kernel: [13221.352622] [<f8828102>] ? rtl8169_schedule_work+0x1e/0x20 [r8169]
May 28 20:26:33 apexwall kernel: [13221.352657] [<f8828168>] ? rtl8169_tx_timeout+0x1f/0x22 [r8169]
May 28 20:26:33 apexwall kernel: [13221.352702] [<c027e7d2>] dev_watchdog+0x92/0xe3
May 28 20:26:33 apexwall kernel: [13221.352731] [<c012baac>] run_timer_softirq+0x124/0x18c
May 28 20:26:33 apexwall kernel: [13221.352739] [<c027e740>] ? dev_watchdog+0x0/0xe3
May 28 20:26:33 apexwall kernel: [13221.352764] [<c027e740>] ? dev_watchdog+0x0/0xe3
May 28 20:26:33 apexwall kernel: [13221.352811] [<c012881d>] __do_softirq+0x6d/0xdf
May 28 20:26:33 apexwall kernel: [13221.352851] [<c01288d7>] do_softirq+0x48/0x57
May 28 20:26:33 apexwall kernel: [13221.352874] [<c0128bac>] irq_exit+0x38/0x6d
May 28 20:26:33 apexwall kernel: [13221.352890] [<c0110b5a>] smp_apic_timer_interrupt+0x6e/0x7c
May 28 20:26:33 apexwall kernel: [13221.352899] [<c0108ef0>] ? mwait_idle+0x0/0x40
May 28 20:26:33 apexwall kernel: [13221.352923] [<c0104478>] apic_timer_interrupt+0x28/0x30
May 28 20:26:33 apexwall kernel: [13221.352931] [<c0108ef0>] ? mwait_idle+0x0/0x40
May 28 20:26:33 apexwall kernel: [13221.353001] [<c0108f22>] ? mwait_idle+0x32/0x40
May 28 20:26:33 apexwall kernel: [13221.353009] [<c0102607>] cpu_idle+0xb3/0xd3
May 28 20:26:33 apexwall kernel: [13221.353009] [<c02d5052>] start_secondary+0x175/0x17a
May 28 20:26:33 apexwall kernel: [13221.353009] =======================
May 28 20:26:33 apexwall kernel: [13221.353009] ---[ end trace 24aa9bce81f621da ]---

Here some info anout the machine and nics:
# uname -a
Linux apexwall.teletrans.local 2.6.26-2-untangle-686 #1 SMP Fri Nov 26 13:36:11
PST 2010 i686 GNU/Linux

# lspci -v
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E P
CI Express Fast Ethernet controller (rev 02)
Subsystem: Hewlett-Packard Company Device 2ab0
Flags: bus master, fast devsel, latency 0, IRQ 220
I/O ports at d800 [size=256]
Memory at fdeef000 (64-bit, prefetchable) [size=4K]
Memory at fdef0000 (64-bit, prefetchable) [size=64K]
Expansion ROM at feae0000 [disabled] [size=128K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 01
Capabilities: [ac] MSI-X: Enable- Count=2 Masked-
Capabilities: [cc] Vital Product Data
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Virtual Channel
Capabilities: [160] Device Serial Number 01-00-00-00-00-00-00-00
Kernel driver in use: r8169
Kernel modules: r8169

03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI E
xpress Gigabit Ethernet controller (rev 03)
Subsystem: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gig
abit Ethernet controller
Flags: fast devsel, IRQ 219
I/O ports at e800 [disabled] [size=256]
Memory at febdf000 (64-bit, non-prefetchable) [disabled] [size=4K]
Memory at fdffc000 (64-bit, prefetchable) [disabled] [size=16K]
[virtual] Expansion ROM at febe0000 [disabled] [size=128K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 01
Capabilities: [ac] MSI-X: Enable- Count=4 Masked-
Capabilities: [cc] Vital Product Data
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Virtual Channel
Capabilities: [160] Device Serial Number dc-02-00-00-68-4c-e0-00
Kernel driver in use: r8169
Kernel modules: r8169

---
# ifconfig

dummy0 Link encap:Ethernet HWaddr 46:d7:d9:52:2e:b3
inet addr:192.0.2.42 Bcast:192.0.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

eth0 Link encap:Ethernet HWaddr 78:e7:d1:d4:00:70
inet addr:192.168.99.250 Bcast:192.168.99.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:404382 errors:0 dropped:0 overruns:0 frame:0
TX packets:300795 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:332808063 (317.3 MiB) TX bytes:123602776 (117.8 MiB)
Interrupt:220

eth1 Link encap:Ethernet HWaddr 00:0a:cd:1b:2e:a0
inet addr:192.168.0.254 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:154890 errors:0 dropped:0 overruns:0 frame:0
TX packets:232316 errors:0 dropped:1932 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:24655100 (23.5 MiB) TX bytes:255879646 (244.0 MiB)
Interrupt:219 Base address:0x2000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1440517 errors:0 dropped:0 overruns:0 frame:0
TX packets:1440517 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:220076929 (209.8 MiB) TX bytes:220076929 (209.8 MiB)

tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
-00
inet addr:172.16.0.1 P-t-P:172.16.0.2 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:164252 errors:0 dropped:0 overruns:0 frame:0
TX packets:149654 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:60409618 (57.6 MiB) TX bytes:82021356 (78.2 MiB)

utun Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
-00
inet addr:192.0.2.43 P-t-P:192.0.2.43 Mask:255.255.255.0
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:352 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:17520 (17.1 KiB) TX bytes:0 (0.0 B)
---
Is there a patch or a fix for that?
Best,
Spyros Samartzis

[sky-knight]

There is no fix for this, this is one of the many reasons why I yell and scream, GO INTEL OR GO HOME!

Despite some members of this forum, and a few Untangle devs opinions. The quality variations of realtek technology is such that you'll be troubleshooting those interfaces until Doomsday and still not make them work consistently.

You could have a PCI bus issue, or a defective card. There are any number of 1000 reasons why that card isn't lighting up. Yet, I'm willing to bet if you tossed in a pair of Intel cards, it would pop online and run without further complaint.

It is possible a BIOS update for your mainboard can be the culprit too!

The second card is the RTL8111 chipset, which Jim and I have had no end of issues with. Some variants work, others just don't.

[dwasserman]

This demostrate how 1 simple post finish with a 72 post´s thread, or real life theorem
http://forums.untangle.com/hardware/...-vs-intel.html

[ssamartzis]

Hello and thanks for your reply.
Actually eth1 timeouts which is not the onboard card but the extra pci-e.
Anyway, I have connected it to a 100Mbit port and the timeout went away.
I understand that this is not a solution but since I did not know these issues before I setup my first untangle box I have to live with it.

[sky-knight]

The "issue" hasn't been really quantified. If you're up for some experimenting you may find it. I tell people to use Intel interfaces to avoid this situation, but the reality is I don't know what causes that situation. It would be nice to solve it, then these interfaces would be usable.

[hescominsoon]

unless you need gigabit can't go wrong with the intel dual port cards an Untangle employee is selling for cheap:

http://forums.untangle.com/hardware/...ased-nics.html

[sky-knight]

Those are Dell branded Intel manufactured PCI boards, and they work really well for many applications. I've purchased a small pile for myself just because.