Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

NIC Issues w/ Realtek r8169

Featured Replies

  • Community Expert

I'm seeing the following trace, which would indicate a kernel bug or more likely flaky hardware. Specifically with the Realtek r8169 NIC. Researching online would suggest bag hardware.

 

------------[ cut here ]------------
WARNING: CPU: 5 PID: 0 at net/sched/sch_generic.c:303 dev_watchdog+0x194/0x1fa()
NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
Modules linked in: xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables kvm_amd kvm vhost_net vhost macvtap macvlan tun xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod hid_logitech_hidpp fam15h_power k10temp pata_atiixp hid_logitech_dj r8169 mii e1000 i2c_piix4 ahci mpt2sas libahci raid_class scsi_transport_sas acpi_cpufreq
CPU: 5 PID: 0 Comm: swapper/5 Not tainted 4.1.1-unRAID #2
Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./970 Extreme4, BIOS P2.60 11/11/2013
0000000000000009 ffff88033ed43dc8 ffffffff8160fb4b 0000000000008328
ffff88033ed43e18 ffff88033ed43e08 ffffffff8104772b ffff88033ed55740
ffffffff81548d86 ffff88032de40000 ffff8800b9238e00 ffff88032de403a0
Call Trace:
<IRQ>  [<ffffffff8160fb4b>] dump_stack+0x4c/0x6e
[<ffffffff8104772b>] warn_slowpath_common+0x97/0xb1
[<ffffffff81548d86>] ? dev_watchdog+0x194/0x1fa
[<ffffffff81047786>] warn_slowpath_fmt+0x41/0x43
[<ffffffff81548d86>] dev_watchdog+0x194/0x1fa
[<ffffffff81057535>] ? cancel_delayed_work+0x68/0x68
[<ffffffff81548bf2>] ? dev_graft_qdisc+0x69/0x69
[<ffffffff81548bf2>] ? dev_graft_qdisc+0x69/0x69
[<ffffffff810829f4>] call_timer_fn.isra.27+0x17/0x6d
[<ffffffff810832f5>] run_timer_softirq+0x1b1/0x1d9
[<ffffffff8104a529>] __do_softirq+0xc9/0x1be
[<ffffffff8104a7af>] irq_exit+0x3d/0x82
[<ffffffff81033ec9>] smp_apic_timer_interrupt+0x3f/0x4b
[<ffffffff8161601e>] apic_timer_interrupt+0x6e/0x80
<EOI>  [<ffffffff814fd46a>] ? cpuidle_enter_state+0xb6/0x114
[<ffffffff814fd403>] ? cpuidle_enter_state+0x4f/0x114
[<ffffffff814fd4ea>] cpuidle_enter+0x12/0x14
[<ffffffff810727f8>] cpu_startup_entry+0x1e2/0x2b2
[<ffffffff810324e4>] start_secondary+0x10e/0x12c
---[ end trace 9b9572771cef3a40 ]---

 

I'm running with 6.1-rc2, however, I'm encountering erratic NIC behaviour on boot up, first with the r8169 onboard LAN and now my dual e1000 NIC.

 

Here's a pastebin: http://pastebin.com/urdg9DXa

 

Occassionally it would boot up with no network connectivity despite me logging on via console and seeing an IP address.

 

Board: ASRock 970 Extreme4

 

Found this: http://lime-technology.com/forum/index.php?topic=12192.0

 

Which pointed to adding the boot parameter:

 

  append initrd=/bzroot pcie_aspm=off 

but that didn't help. Would appear that I'm stuck here.

  • Author
  • Community Expert

Tools->Diagnostics. Attach file.

 

Also, neglected to mention:

 

AMD iommu enabled in the bios, disabled audio/1394/serial and hardware as per signature (2nd build).

tower-diagnostics-20150811-1034.zip

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.