Realtek RTL8111/8168B death
Hi all, after about 3 weeks into a new machine the network card started dying
pretty regularly with these oopses:
Aug 21 23:03:49 fire kernel: [ 2656.192450] ------------[ cut here ]------------
Aug 21 23:03:49 fire kernel: [ 2656.192457] WARNING: at /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/net/sched/sch_generic.c:255 dev_watchdog+0xe9/0x148()
Aug 21 23:03:49 fire kernel: [ 2656.192459] Hardware name: H61M-DS2
Aug 21 23:03:49 fire kernel: [ 2656.192460] NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
Aug 21 23:03:49 fire kernel: [ 2656.192461] Modules linked in: ipt_MASQUERADE xt_state iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_tcpudp iptable_filter ip_tables x_tables nf_conntrack_ftp nf_conntrack binfmt_misc nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc loop snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc i915 snd_seq snd_seq_device coretemp snd_timer crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 snd acpi_cpufreq video aes_generic drm_kms_helper soundcore parport_pc drm i2c_algo_bit serio_raw mperf parport cryptd evdev joydev pcspkr iTCO_wdt i2c_i801 i2c_core iTCO_vendor_support processor button thermal_sys ext4 crc16 jbd2 mbcache dm_mod raid1 md_mod sd_mod sr_mod cdrom crc_t10dif usbhid hid ahci libahci atl1c libata r8169 scsi_mod mii ehci_hcd usbcore usb_common [last unloaded: scsi_wait_scan]
Aug 21 23:03:49 fire kernel: [ 2656.192503] Pid: 0, comm: swapper/0 Not tainted 3.2.0-3-amd64 #1
Aug 21 23:03:49 fire kernel: [ 2656.192505] Call Trace:
Aug 21 23:03:49 fire kernel: [ 2656.192506] <IRQ> [<ffffffff81046901>] ? warn_slowpath_common+0x78/0x8c
Aug 21 23:03:49 fire kernel: [ 2656.192512] [<ffffffff810469ad>] ? warn_slowpath_fmt+0x45/0x4a
Aug 21 23:03:49 fire kernel: [ 2656.192514] [<ffffffff812a3559>] ? netif_tx_lock+0x40/0x72
Aug 21 23:03:49 fire kernel: [ 2656.192518] [<ffffffff812a36ba>] ? dev_watchdog+0xe9/0x148
Aug 21 23:03:49 fire kernel: [ 2656.192520] [<ffffffff81051f74>] ? run_timer_softirq+0x19a/0x261
Aug 21 23:03:49 fire kernel: [ 2656.192522] [<ffffffff812a35d1>] ? netif_tx_unlock+0x46/0x46
Aug 21 23:03:49 fire kernel: [ 2656.192526] [<ffffffff81065ad7>] ? timekeeping_get_ns+0xd/0x2a
Aug 21 23:03:49 fire kernel: [ 2656.192528] [<ffffffff8104bee8>] ? __do_softirq+0xb9/0x177
Aug 21 23:03:49 fire kernel: [ 2656.192532] [<ffffffff81351eec>] ? call_softirq+0x1c/0x30
Aug 21 23:03:49 fire kernel: [ 2656.192535] [<ffffffff8100f8e5>] ? do_softirq+0x3c/0x7b
Aug 21 23:03:49 fire kernel: [ 2656.192537] [<ffffffff8104c150>] ? irq_exit+0x3c/0x9a
Aug 21 23:03:49 fire kernel: [ 2656.192541] [<ffffffff81024208>] ? smp_apic_timer_interrupt+0x74/0x82
Aug 21 23:03:49 fire kernel: [ 2656.192543] [<ffffffff8135075e>] ? apic_timer_interrupt+0x6e/0x80
Aug 21 23:03:49 fire kernel: [ 2656.192544] <EOI> [<ffffffff81023ed0>] ? lapic_next_event+0xe/0x13
Aug 21 23:03:49 fire kernel: [ 2656.192549] [<ffffffff811ec633>] ? intel_idle+0xea/0x118
Aug 21 23:03:49 fire kernel: [ 2656.192551] [<ffffffff811ec612>] ? intel_idle+0xc9/0x118
Aug 21 23:03:49 fire kernel: [ 2656.192555] [<ffffffff8126cbff>] ? cpuidle_idle_call+0xec/0x179
Aug 21 23:03:49 fire kernel: [ 2656.192557] [<ffffffff8100d248>] ? cpu_idle+0xa5/0xf2
Aug 21 23:03:49 fire kernel: [ 2656.192560] [<ffffffff816aab33>] ? start_kernel+0x3b3/0x3be
Aug 21 23:03:49 fire kernel: [ 2656.192562] [<ffffffff816aa140>] ? early_idt_handlers+0x140/0x140
Aug 21 23:03:49 fire kernel: [ 2656.192564] [<ffffffff816aa3c4>] ? x86_64_start_kernel+0x104/0x111
Aug 21 23:03:49 fire kernel: [ 2656.192565] ---[ end trace 52c65d93a2f98318 ]---
$ lspci -knn | grep -B2 r8169
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 01)
Subsystem: Realtek Semiconductor Co., Ltd. TEG-ECTX Gigabit PCI-E Adapter [Trendnet] [10ec:8168]
Kernel driver in use: r8169
$ cat /etc/issue
Debian GNU/Linux wheezy/sid \n \l
$ uname -a
Linux fire 3.2.0-3-amd64 #1 SMP Mon Jul 23 02:45:17 UTC 2012 x86_64 GNU/Linux
It doesn't seem to be related to the amount of traffic through it beforehand.
I've noticed people posting similar reports over a few years so I'm not sure
if this is a new bug to report? Could it be hardware or should I be using
Realtek's own drivers?
Reply to: