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.

Network drops after 15-20 days uptime

Featured Replies

Since a couple of month ago my server started to drop the network after around 15-20 days uptime. The server works like a charm while it is up, and is no big issue when im at home, since a restart solves the problem for another 15-20 days.

 

Still it is a frustrating issue..

 

I have googled the problem and havent found a good solution, i know the network controller is the onboard sky2 and that might be the problem. I have 2 ports and have tried both, bonded and not bonded.

 

I have also tried to see if there is something else that can cause the problem, i did a reconfigure of the network, and changed a couple of devices (switch + router), but the problem still exist.

 

I havent bought a new network card (yet) because i'm not 100% sure thats the problem.

 

Here is the log when the network problem occurs (diagnostics file attached aswell):

 

Jan 12 07:57:59 Unraid kernel: br0: port 2(vnet0) entered blocking state
Jan 12 07:57:59 Unraid kernel: br0: port 2(vnet0) entered forwarding state
Jan 12 09:13:56 Unraid kernel: DMAR: DRHD: handling fault status reg 2
Jan 12 09:13:56 Unraid kernel: DMAR: [DMA Read] Request device [07:00.0] PASID ffffffff fault addr f718f000 [fault reason 06] PTE Read access is not set
Jan 12 09:13:56 Unraid kernel: sky2 0000:07:00.0: error interrupt status=0x80000000
Jan 12 09:13:56 Unraid kernel: sky2 0000:07:00.0: PCI hardware error (0x2010)
Jan 12 09:14:01 Unraid kernel: ------------[ cut here ]------------
Jan 12 09:14:01 Unraid kernel: NETDEV WATCHDOG: eth0 (sky2): transmit queue 0 timed out
Jan 12 09:14:01 Unraid kernel: WARNING: CPU: 7 PID: 6342 at net/sched/sch_generic.c:442 dev_watchdog+0xcf/0x12b
Jan 12 09:14:01 Unraid kernel: Modules linked in: macvlan nvidia_uvm(PO) xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle nf_tables vhost_net tun vhost vhost_iotlb tap veth xt_nat xt_tcpudp xt_conntrack nf_conntrack_netlink nfnetlink xt_addrtype br_netfilter xfs md_mod nvidia_drm(PO) nvidia_modeset(PO) drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops nvidia(PO) drm backlight agpgart hwmon_vid iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libblake2s blake2s_x86_64 libblake2s_generic libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables sky2 intel_powerclamp coretemp mxm_wmi kvm_intel kvm crc32c_intel intel_cstate intel_uncore mpt3sas ahci libahci i2c_i801 i7core_edac i2c_smbus i2c_core raid_class input_leds i5500_temp wmi led_class asus_atk0110 scsi_transport_sas button acpi_cpufreq
Jan 12 09:14:01 Unraid kernel: [last unloaded: sky2]
Jan 12 09:14:01 Unraid kernel: CPU: 7 PID: 6342 Comm: mono Tainted: P        W IO      5.10.28-Unraid #1
Jan 12 09:14:01 Unraid kernel: Hardware name: System manufacturer System Product Name/P6X58D PREMIUM, BIOS 1501    05/10/2011
Jan 12 09:14:01 Unraid kernel: RIP: 0010:dev_watchdog+0xcf/0x12b
Jan 12 09:14:01 Unraid kernel: Code: 79 b7 00 00 75 38 48 89 ef c6 05 63 79 b7 00 01 e8 79 dd fc ff 44 89 e1 48 89 ee 48 c7 c7 ef 7f de 81 48 89 c2 e8 50 16 10 00 <0f> 0b eb 10 41 ff c4 48 05 40 01 00 00 41 39 f4 75 9d eb 16 48 8b
Jan 12 09:14:01 Unraid kernel: RSP: 0018:ffffc90000228ed8 EFLAGS: 00010286
Jan 12 09:14:01 Unraid kernel: RAX: 0000000000000000 RBX: ffff88810143e438 RCX: 0000000000000027
Jan 12 09:14:01 Unraid kernel: RDX: 00000000ffffefff RSI: 0000000000000001 RDI: ffff888a17bd8920
Jan 12 09:14:01 Unraid kernel: RBP: ffff88810143e000 R08: 0000000000000000 R09: 00000000ffffefff
Jan 12 09:14:01 Unraid kernel: R10: ffffc90000228d08 R11: ffffc90000228d00 R12: 0000000000000000
Jan 12 09:14:01 Unraid kernel: R13: ffffc90000228f10 R14: ffffc90000228f10 R15: ffffffff820060c8
Jan 12 09:14:01 Unraid kernel: FS:  00001458058fe700(0000) GS:ffff888a17bc0000(0000) knlGS:0000000000000000
Jan 12 09:14:01 Unraid kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 12 09:14:01 Unraid kernel: CR2: 000001755284f000 CR3: 00000001283be000 CR4: 00000000000026e0
Jan 12 09:14:01 Unraid kernel: Call Trace:
Jan 12 09:14:01 Unraid kernel: <IRQ>
Jan 12 09:14:01 Unraid kernel: call_timer_fn.isra.0+0x12/0x6f
Jan 12 09:14:01 Unraid kernel: ? netif_tx_lock+0x7a/0x7a
Jan 12 09:14:01 Unraid kernel: __run_timers.part.0+0x144/0x185
Jan 12 09:14:01 Unraid kernel: ? update_process_times+0x68/0x6e
Jan 12 09:14:01 Unraid kernel: ? hrtimer_forward+0x73/0x7b
Jan 12 09:14:01 Unraid kernel: ? tick_sched_timer+0x5a/0x64
Jan 12 09:14:01 Unraid kernel: ? timerqueue_add+0x62/0x68
Jan 12 09:14:01 Unraid kernel: ? recalibrate_cpu_khz+0x1/0x1
Jan 12 09:14:01 Unraid kernel: run_timer_softirq+0x21/0x43
Jan 12 09:14:01 Unraid kernel: __do_softirq+0xc4/0x1c2
Jan 12 09:14:01 Unraid kernel: asm_call_irq_on_stack+0x12/0x20
Jan 12 09:14:01 Unraid kernel: </IRQ>
Jan 12 09:14:01 Unraid kernel: do_softirq_own_stack+0x2c/0x39
Jan 12 09:14:01 Unraid kernel: __irq_exit_rcu+0x45/0x80
Jan 12 09:14:01 Unraid kernel: sysvec_apic_timer_interrupt+0x87/0x95
Jan 12 09:14:01 Unraid kernel: asm_sysvec_apic_timer_interrupt+0x12/0x20
Jan 12 09:14:01 Unraid kernel: RIP: 0010:arch_local_irq_enable+0x4/0x8
Jan 12 09:14:01 Unraid kernel: Code: 68 48 8b 7f 70 e9 1a ff ff ff 8b 77 58 48 8b 7f 28 e9 0e ff ff ff 9c 58 66 66 90 66 90 c3 fa 66 66 90 66 66 90 c3 fb 66 66 90 <66> 66 90 c3 48 8b 05 82 01 fb 00 e9 d5 1b 99 00 c6 07 00 66 66 66
Jan 12 09:14:01 Unraid kernel: RSP: 0018:ffffc90001e5bb00 EFLAGS: 00000246
Jan 12 09:14:01 Unraid kernel: RAX: ffff8881000fd940 RBX: 0000000000000000 RCX: 0000000000000000
Jan 12 09:14:01 Unraid kernel: RDX: 0000000000000000 RSI: 0000000000000006 RDI: ffff888a17be2380
Jan 12 09:14:01 Unraid kernel: RBP: ffffc90001e5bb38 R08: 0000000000000000 R09: 0000000000000019
Jan 12 09:14:01 Unraid kernel: R10: ffff888a17be2380 R11: ffff888270e7e200 R12: ffff8881000fd940
Jan 12 09:14:01 Unraid kernel: R13: ffff8882884c4400 R14: ffff888a17be2380 R15: ffff88811bc41980
Jan 12 09:14:01 Unraid kernel: __raw_spin_unlock_irq+0xa/0xb
Jan 12 09:14:01 Unraid kernel: finish_task_switch+0x125/0x1ee
Jan 12 09:14:01 Unraid kernel: __schedule+0x466/0x4a4
Jan 12 09:14:01 Unraid kernel: schedule+0x73/0x99
Jan 12 09:14:01 Unraid kernel: request_wait_answer+0x7b/0x1e7
Jan 12 09:14:01 Unraid kernel: ? init_wait_entry+0x24/0x24
Jan 12 09:14:01 Unraid kernel: fuse_simple_request+0x1b5/0x1f0
Jan 12 09:14:01 Unraid kernel: fuse_perform_write+0x324/0x45e
Jan 12 09:14:01 Unraid kernel: fuse_file_write_iter+0x1c1/0x2f0
Jan 12 09:14:01 Unraid kernel: ? ___bpf_prog_run+0x82f/0x12eb
Jan 12 09:14:01 Unraid kernel: ? __bpf_prog_run32+0x35/0x51
Jan 12 09:14:01 Unraid kernel: ? xfs_iunlock+0x2d/0x76 [xfs]
Jan 12 09:14:01 Unraid kernel: new_sync_write+0x7a/0xb2
Jan 12 09:14:01 Unraid kernel: vfs_write+0xd7/0x121
Jan 12 09:14:01 Unraid kernel: ksys_write+0x71/0xba
Jan 12 09:14:01 Unraid kernel: do_syscall_64+0x5d/0x6a
Jan 12 09:14:01 Unraid kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Jan 12 09:14:01 Unraid kernel: RIP: 0033:0x14582069c3a7
Jan 12 09:14:01 Unraid kernel: Code: 44 00 00 41 54 55 49 89 d4 53 48 89 f5 89 fb 48 83 ec 10 e8 5b fd ff ff 4c 89 e2 41 89 c0 48 89 ee 89 df b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 48 89 44 24 08 e8 94 fd ff ff 48
Jan 12 09:14:01 Unraid kernel: RSP: 002b:00001458058fc4a0 EFLAGS: 00000293 ORIG_RAX: 0000000000000001
Jan 12 09:14:01 Unraid kernel: RAX: ffffffffffffffda RBX: 0000000000000015 RCX: 000014582069c3a7
Jan 12 09:14:01 Unraid kernel: RDX: 0000000000002000 RSI: 00001457f12223d0 RDI: 0000000000000015
Jan 12 09:14:01 Unraid kernel: RBP: 00001457f12223d0 R08: 0000000000000000 R09: 0000000000000000
Jan 12 09:14:01 Unraid kernel: R10: 00001457f00008d0 R11: 0000000000000293 R12: 0000000000002000
Jan 12 09:14:01 Unraid kernel: R13: 000055bcb494f998 R14: 00001457f0000b20 R15: 0000000000002000
Jan 12 09:14:01 Unraid kernel: ---[ end trace 86f7356cc5d7e87e ]---
Jan 12 09:14:01 Unraid kernel: sky2 0000:07:00.0 eth0: tx timeout
Jan 12 09:14:01 Unraid kernel: sky2 0000:07:00.0 eth0: transmit ring 118 .. 15 report=118 done=118
Jan 12 09:14:01 Unraid kernel: br0: port 1(eth0) entered disabled state
Jan 12 09:14:05 Unraid kernel: sky2 0000:07:00.0 eth0: Link is up at 1000 Mbps, full duplex, flow control both
Jan 12 09:14:05 Unraid kernel: br0: port 1(eth0) entered blocking state
Jan 12 09:14:05 Unraid kernel: br0: port 1(eth0) entered forwarding state
Jan 12 09:14:10 Unraid kernel: sky2 0000:07:00.0 eth0: tx timeout
Jan 12 09:14:10 Unraid kernel: sky2 0000:07:00.0 eth0: transmit ring 3 .. 25 report=3 done=3
Jan 12 09:14:10 Unraid kernel: br0: port 1(eth0) entered disabled state
Jan 12 09:14:13 Unraid kernel: sky2 0000:07:00.0 eth0: Link is up at 1000 Mbps, full duplex, flow control both
Jan 12 09:14:13 Unraid kernel: br0: port 1(eth0) entered blocking state
Jan 12 09:14:13 Unraid kernel: br0: port 1(eth0) entered forwarding state
Jan 12 09:14:17 Unraid kernel: TCP: request_sock_TCP: Possible SYN flooding on port 25410. Sending cookies.  Check SNMP counters.
Jan 12 09:14:19 Unraid kernel: sky2 0000:07:00.0 eth0: tx timeout
Jan 12 09:14:19 Unraid kernel: sky2 0000:07:00.0 eth0: transmit ring 2 .. 26 report=2 done=2
Jan 12 09:14:19 Unraid kernel: br0: port 1(eth0) entered disabled state
Jan 12 09:14:23 Unraid kernel: sky2 0000:07:00.0 eth0: Link is up at 1000 Mbps, full duplex, flow control both
Jan 12 09:14:23 Unraid kernel: br0: port 1(eth0) entered blocking state
Jan 12 09:14:23 Unraid kernel: br0: port 1(eth0) entered forwarding state
Jan 12 09:14:28 Unraid kernel: sky2 0000:07:00.0 eth0: tx timeout

 

 

 

unraid-diagnostics-20220112-0931.zip

Solved by LtJaeger

  • 5 months later...
  • Author
  • Solution

Solved with new network card.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

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.