iamcagn
-
Posts
6 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by iamcagn
-
-
I do use static IP addresses on basically all my dockers, but never ran into this issue before. Would disabling the onboard NICs in the BIOS help? I'd like to keep everything on the same subnet for now.
-
Hi there,
Recently I've been seeing errors similar to:
Aug 4 09:18:14 iamserver kernel: rcu: INFO: rcu_sched self-detected stall on CPU Aug 4 09:18:14 iamserver kernel: rcu: 0-....: (779698 ticks this GP) idle=08a/1/0x4000000000000002 softirq=90781609/90781610 fqs=184365 Aug 4 09:18:14 iamserver kernel: rcu: (t=780014 jiffies g=223095361 q=211077) Aug 4 09:18:14 iamserver kernel: NMI backtrace for cpu 0 Aug 4 09:18:14 iamserver kernel: CPU: 0 PID: 31451 Comm: containerd Tainted: P D W O 4.19.107-Unraid #1 Aug 4 09:18:14 iamserver kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X470 Taichi Ultimate, BIOS P3.90 01/10/2020 Aug 4 09:18:14 iamserver kernel: Call Trace: Aug 4 09:18:14 iamserver kernel: <IRQ> Aug 4 09:18:14 iamserver kernel: dump_stack+0x67/0x83 Aug 4 09:18:14 iamserver kernel: nmi_cpu_backtrace+0x71/0x83 Aug 4 09:18:14 iamserver kernel: ? lapic_can_unplug_cpu+0x97/0x97 Aug 4 09:18:14 iamserver kernel: nmi_trigger_cpumask_backtrace+0x57/0xd4 Aug 4 09:18:14 iamserver kernel: rcu_dump_cpu_stacks+0x8b/0xb4 Aug 4 09:18:14 iamserver kernel: rcu_check_callbacks+0x296/0x5a0 Aug 4 09:18:14 iamserver kernel: update_process_times+0x24/0x47 Aug 4 09:18:14 iamserver kernel: tick_sched_timer+0x36/0x64 Aug 4 09:18:14 iamserver kernel: __hrtimer_run_queues+0xb7/0x10b Aug 4 09:18:14 iamserver kernel: ? tick_sched_handle.isra.0+0x2f/0x2f Aug 4 09:18:14 iamserver kernel: hrtimer_interrupt+0xf4/0x20e Aug 4 09:18:14 iamserver kernel: smp_apic_timer_interrupt+0x7b/0x93 Aug 4 09:18:14 iamserver kernel: apic_timer_interrupt+0xf/0x20 Aug 4 09:18:14 iamserver kernel: </IRQ> Aug 4 09:18:14 iamserver kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x67/0x171 Aug 4 09:18:14 iamserver kernel: Code: 01 00 00 0f 42 f0 8b 07 30 e4 09 c6 f7 c6 00 ff ff ff 74 0e 81 e6 00 ff 00 00 75 1a c6 47 01 00 eb 14 85 f6 74 0a 8b 07 84 c0 <74> 04 f3 90 eb f6 66 c7 07 01 00 c3 48 c7 c2 40 07 02 00 65 48 03 Aug 4 09:18:14 iamserver kernel: RSP: 0018:ffffc9000a48bd78 EFLAGS: 00000202 ORIG_RAX: ffffffffffffff13 Aug 4 09:18:14 iamserver kernel: RAX: 0000000000000101 RBX: ffffc900035bc948 RCX: 000000009b3fabc7 Aug 4 09:18:14 iamserver kernel: RDX: 0000000000000001 RSI: 0000000000000001 RDI: ffffc900035bc944 Aug 4 09:18:14 iamserver kernel: RBP: ffffc900035bc944 R08: 000000000270ac88 R09: 0000000000000000 Aug 4 09:18:14 iamserver kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 Aug 4 09:18:14 iamserver kernel: R13: 00000000ffffffff R14: 0000000000000001 R15: 0000000000000001 Aug 4 09:18:14 iamserver kernel: _raw_spin_lock+0x16/0x19 Aug 4 09:18:14 iamserver kernel: futex_wake+0x91/0x147 Aug 4 09:18:14 iamserver kernel: do_futex+0x20e/0x9dc Aug 4 09:18:14 iamserver kernel: ? wake_up_q+0x2d/0x48 Aug 4 09:18:14 iamserver kernel: ? rwsem_wake+0x9b/0xbe Aug 4 09:18:14 iamserver kernel: __se_sys_futex+0x131/0x156 Aug 4 09:18:14 iamserver kernel: ? __do_page_fault+0x36d/0x3ff Aug 4 09:18:14 iamserver kernel: do_syscall_64+0x57/0xf2 Aug 4 09:18:14 iamserver kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Aug 4 09:18:14 iamserver kernel: RIP: 0033:0x45f623 Aug 4 09:18:14 iamserver kernel: Code: 24 20 c3 cc cc cc cc 48 8b 7c 24 08 8b 74 24 10 8b 54 24 14 4c 8b 54 24 18 4c 8b 44 24 20 44 8b 4c 24 28 b8 ca 00 00 00 0f 05 <89> 44 24 30 c3 cc cc cc cc cc cc cc cc 8b 7c 24 08 48 8b 74 24 10 Aug 4 09:18:14 iamserver kernel: RSP: 002b:000014e0d5f7ab98 EFLAGS: 00000206 ORIG_RAX: 00000000000000ca Aug 4 09:18:14 iamserver kernel: RAX: ffffffffffffffda RBX: 000000c0004b9000 RCX: 000000000045f623 Aug 4 09:18:14 iamserver kernel: RDX: 0000000000000001 RSI: 0000000000000081 RDI: 000000000270ac88 Aug 4 09:18:14 iamserver kernel: RBP: 000014e0d5f7abe8 R08: 0000000000000000 R09: 0000000000000000 Aug 4 09:18:14 iamserver kernel: R10: 0000000000000000 R11: 0000000000000206 R12: ffffffffffffffff Aug 4 09:18:14 iamserver kernel: R13: 0000000000000002 R14: 0000000000000001 R15: 0000000000000200 Aug 4 09:18:19 iamserver kernel: rcu: INFO: rcu_bh self-detected stall on CPU Aug 4 09:18:19 iamserver kernel: rcu: 0-....: (795572 ticks this GP) idle=08a/1/0x4000000000000002 softirq=90776120/90781610 fqs=186292 Aug 4 09:18:19 iamserver kernel: rcu: (t=780014 jiffies g=21013 q=2) Aug 4 09:18:19 iamserver kernel: NMI backtrace for cpu 0 Aug 4 09:18:19 iamserver kernel: CPU: 0 PID: 31451 Comm: containerd Tainted: P D W O 4.19.107-Unraid #1 Aug 4 09:18:19 iamserver kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X470 Taichi Ultimate, BIOS P3.90 01/10/2020 Aug 4 09:18:19 iamserver kernel: Call Trace: Aug 4 09:18:19 iamserver kernel: <IRQ> Aug 4 09:18:19 iamserver kernel: dump_stack+0x67/0x83 Aug 4 09:18:19 iamserver kernel: nmi_cpu_backtrace+0x71/0x83 Aug 4 09:18:19 iamserver kernel: ? lapic_can_unplug_cpu+0x97/0x97 Aug 4 09:18:19 iamserver kernel: nmi_trigger_cpumask_backtrace+0x57/0xd4 Aug 4 09:18:19 iamserver kernel: rcu_dump_cpu_stacks+0x8b/0xb4 Aug 4 09:18:19 iamserver kernel: rcu_check_callbacks+0x296/0x5a0 Aug 4 09:18:19 iamserver kernel: update_process_times+0x24/0x47 Aug 4 09:18:19 iamserver kernel: tick_sched_timer+0x36/0x64 Aug 4 09:18:19 iamserver kernel: __hrtimer_run_queues+0xb7/0x10b Aug 4 09:18:19 iamserver kernel: ? tick_sched_handle.isra.0+0x2f/0x2f Aug 4 09:18:19 iamserver kernel: hrtimer_interrupt+0xf4/0x20e Aug 4 09:18:19 iamserver kernel: smp_apic_timer_interrupt+0x7b/0x93 Aug 4 09:18:19 iamserver kernel: apic_timer_interrupt+0xf/0x20 Aug 4 09:18:19 iamserver kernel: </IRQ> Aug 4 09:18:19 iamserver kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x67/0x171 Aug 4 09:18:19 iamserver kernel: Code: 01 00 00 0f 42 f0 8b 07 30 e4 09 c6 f7 c6 00 ff ff ff 74 0e 81 e6 00 ff 00 00 75 1a c6 47 01 00 eb 14 85 f6 74 0a 8b 07 84 c0 <74> 04 f3 90 eb f6 66 c7 07 01 00 c3 48 c7 c2 40 07 02 00 65 48 03 Aug 4 09:18:19 iamserver kernel: RSP: 0018:ffffc9000a48bd78 EFLAGS: 00000202 ORIG_RAX: ffffffffffffff13 Aug 4 09:18:19 iamserver kernel: RAX: 0000000000000101 RBX: ffffc900035bc948 RCX: 000000009b3fabc7 Aug 4 09:18:19 iamserver kernel: RDX: 0000000000000001 RSI: 0000000000000001 RDI: ffffc900035bc944 Aug 4 09:18:19 iamserver kernel: RBP: ffffc900035bc944 R08: 000000000270ac88 R09: 0000000000000000 Aug 4 09:18:19 iamserver kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 Aug 4 09:18:19 iamserver kernel: R13: 00000000ffffffff R14: 0000000000000001 R15: 0000000000000001 Aug 4 09:18:19 iamserver kernel: _raw_spin_lock+0x16/0x19 Aug 4 09:18:19 iamserver kernel: futex_wake+0x91/0x147 Aug 4 09:18:19 iamserver kernel: do_futex+0x20e/0x9dc Aug 4 09:18:19 iamserver kernel: ? wake_up_q+0x2d/0x48 Aug 4 09:18:19 iamserver kernel: ? rwsem_wake+0x9b/0xbe Aug 4 09:18:19 iamserver kernel: __se_sys_futex+0x131/0x156 Aug 4 09:18:19 iamserver kernel: ? __do_page_fault+0x36d/0x3ff Aug 4 09:18:19 iamserver kernel: do_syscall_64+0x57/0xf2 Aug 4 09:18:19 iamserver kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Aug 4 09:18:19 iamserver kernel: RIP: 0033:0x45f623 Aug 4 09:18:19 iamserver kernel: Code: 24 20 c3 cc cc cc cc 48 8b 7c 24 08 8b 74 24 10 8b 54 24 14 4c 8b 54 24 18 4c 8b 44 24 20 44 8b 4c 24 28 b8 ca 00 00 00 0f 05 <89> 44 24 30 c3 cc cc cc cc cc cc cc cc 8b 7c 24 08 48 8b 74 24 10 Aug 4 09:18:19 iamserver kernel: RSP: 002b:000014e0d5f7ab98 EFLAGS: 00000206 ORIG_RAX: 00000000000000ca Aug 4 09:18:19 iamserver kernel: RAX: ffffffffffffffda RBX: 000000c0004b9000 RCX: 000000000045f623 Aug 4 09:18:19 iamserver kernel: RDX: 0000000000000001 RSI: 0000000000000081 RDI: 000000000270ac88 Aug 4 09:18:19 iamserver kernel: RBP: 000014e0d5f7abe8 R08: 0000000000000000 R09: 0000000000000000 Aug 4 09:18:19 iamserver kernel: R10: 0000000000000000 R11: 0000000000000206 R12: ffffffffffffffff Aug 4 09:18:19 iamserver kernel: R13: 0000000000000002 R14: 0000000000000001 R15: 0000000000000200
I started seeing them after installing this this Dell H310 6Gbps SAS HBA card, or after I started to use the 10GB port on my mobo
My server was a Ryzen 2700x in a ASRock x470 Tarichi Ultimate, but I decided to swap it with my desktop, a 6700k in a Gigabyte Gaming 7 x170 and popped in a SuperMicro X540-AT2 AOC-STG-I2T 10GB Ethernet card. Since then, I started to see:
Aug 8 15:43:44 iamserver kernel: ------------[ cut here ]------------ Aug 8 15:43:44 iamserver kernel: WARNING: CPU: 6 PID: 5707 at net/netfilter/nf_nat_core.c:420 nf_nat_setup_info+0x94/0x666 [nf_nat] Aug 8 15:43:44 iamserver kernel: Modules linked in: veth nvidia_uvm(O) arc4 ecb md4 sha512_ssse3 sha512_generic cmac cifs ccm xt_nat macvlan ipt_MASQUERADE iptable_filter iptable_nat nf_nat_ipv4 nf_nat ip_tables xfs md_mod e1000e ixgbe(O) alx mdio nvidia_drm(PO) nvidia_modeset(PO) nvidia(PO) crc32_pclmul intel_rapl_perf intel_uncore pcbc aesni_intel aes_x86_64 glue_helper crypto_simd ghash_clmulni_intel cryptd hid_logitech_hidpp kvm_intel intel_wmi_thunderbolt mxm_wmi kvm drm_kms_helper intel_cstate drm coretemp mpt3sas crct10dif_pclmul intel_powerclamp syscopyarea sysfillrect ahci crc32c_intel sysimgblt fb_sys_fops libahci raid_class x86_pkg_temp_thermal agpgart wmi hid_logitech_dj video scsi_transport_sas i2c_i801 i2c_core pcc_cpufreq backlight thermal button acpi_pad fan [last unloaded: e1000e] Aug 8 15:43:44 iamserver kernel: CPU: 6 PID: 5707 Comm: kworker/6:0 Tainted: P O 4.19.107-Unraid #1 Aug 8 15:43:44 iamserver kernel: Hardware name: Gigabyte Technology Co., Ltd. Z170X-Gaming 7/Z170X-Gaming 7, BIOS F22m 03/09/2018 Aug 8 15:43:44 iamserver kernel: Workqueue: events macvlan_process_broadcast [macvlan] Aug 8 15:43:44 iamserver kernel: RIP: 0010:nf_nat_setup_info+0x94/0x666 [nf_nat] Aug 8 15:43:44 iamserver kernel: Code: 0d 8b 87 80 00 00 00 25 80 00 00 00 eb 0c 41 8b 86 80 00 00 00 25 00 01 00 00 85 c0 74 13 48 c7 c7 cc 51 0f a0 e8 8b a9 f9 e0 <0f> 0b e9 49 01 00 00 4c 8d 6c 24 30 49 8d 76 58 4c 89 ef e8 bd 10 Aug 8 15:43:44 iamserver kernel: RSP: 0018:ffff88883eb83c50 EFLAGS: 00010246 Aug 8 15:43:44 iamserver kernel: RAX: 0000000000000024 RBX: ffff88883eb83df0 RCX: 0000000000000000 Aug 8 15:43:44 iamserver kernel: RDX: 0000000000000000 RSI: ffff88883eb964f8 RDI: ffff88883eb964f8 Aug 8 15:43:44 iamserver kernel: RBP: ffff88883eb83d28 R08: 0000000000000003 R09: 000000000001fa00 Aug 8 15:43:44 iamserver kernel: R10: 0000000000000000 R11: 0000000000000044 R12: 0000000000000000 Aug 8 15:43:44 iamserver kernel: R13: 0000000000000000 R14: ffff88814dc18500 R15: ffff88883eb83d3c Aug 8 15:43:44 iamserver kernel: FS: 0000000000000000(0000) GS:ffff88883eb80000(0000) knlGS:0000000000000000 Aug 8 15:43:44 iamserver kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Aug 8 15:43:44 iamserver kernel: CR2: 00001551bf8f0000 CR3: 0000000001e0a002 CR4: 00000000003606e0 Aug 8 15:43:44 iamserver kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Aug 8 15:43:44 iamserver kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Aug 8 15:43:44 iamserver kernel: Call Trace: Aug 8 15:43:44 iamserver kernel: <IRQ> Aug 8 15:43:44 iamserver kernel: nf_nat_alloc_null_binding+0x71/0x88 [nf_nat] Aug 8 15:43:44 iamserver kernel: nf_nat_inet_fn+0x9f/0x1b9 [nf_nat] Aug 8 15:43:44 iamserver kernel: nf_hook_slow+0x3a/0x90 Aug 8 15:43:44 iamserver kernel: ip_local_deliver+0xad/0xdc Aug 8 15:43:44 iamserver kernel: ? ip_sublist_rcv_finish+0x54/0x54 Aug 8 15:43:44 iamserver kernel: ip_sabotage_in+0x38/0x3e Aug 8 15:43:44 iamserver kernel: nf_hook_slow+0x3a/0x90 Aug 8 15:43:44 iamserver kernel: ip_rcv+0x8e/0xbe Aug 8 15:43:44 iamserver kernel: ? ip_rcv_finish_core.isra.0+0x2e1/0x2e1 Aug 8 15:43:44 iamserver kernel: __netif_receive_skb_one_core+0x53/0x6f Aug 8 15:43:44 iamserver kernel: process_backlog+0x77/0x10e Aug 8 15:43:44 iamserver kernel: net_rx_action+0x107/0x26c Aug 8 15:43:44 iamserver kernel: __do_softirq+0xc9/0x1d7 Aug 8 15:43:44 iamserver kernel: do_softirq_own_stack+0x2a/0x40 Aug 8 15:43:44 iamserver kernel: </IRQ> Aug 8 15:43:44 iamserver kernel: do_softirq+0x4d/0x5a Aug 8 15:43:44 iamserver kernel: netif_rx_ni+0x1c/0x22 Aug 8 15:43:44 iamserver kernel: macvlan_broadcast+0x111/0x156 [macvlan] Aug 8 15:43:44 iamserver kernel: ? __switch_to_asm+0x41/0x70 Aug 8 15:43:44 iamserver kernel: macvlan_process_broadcast+0xea/0x128 [macvlan] Aug 8 15:43:44 iamserver kernel: process_one_work+0x16e/0x24f Aug 8 15:43:44 iamserver kernel: worker_thread+0x1e2/0x2b8 Aug 8 15:43:44 iamserver kernel: ? rescuer_thread+0x2a7/0x2a7 Aug 8 15:43:44 iamserver kernel: kthread+0x10c/0x114 Aug 8 15:43:44 iamserver kernel: ? kthread_park+0x89/0x89 Aug 8 15:43:44 iamserver kernel: ret_from_fork+0x35/0x40 Aug 8 15:43:44 iamserver kernel: ---[ end trace db298b547ca99952 ]---
Should I be concerned about these errors?
-
Oh my god, you're right! The slot the card is in was previously occupied by a GPU that I was passing through to a VM.
So many hours of troubleshooting wasted, I should've just posted here first.
Thank you so much!
-
1
-
-
Hey there, hoping someone can help.
I recently purchased a Dell H310 off eBay (https://www.ebay.com.au/itm/Dell-H310-6Gbps-SAS-HBA-LSI-9211-8i-FW-P20-IT-Mode-for-ZFS-FreeNAS-unRAID-AU/133159382201?ssPageName=STRK%3AMEBIDX%3AIT&_trksid=p2057872.m2749.l2649) and cables from Amazon (https://www.ebay.com.au/itm/Dell-H310-6Gbps-SAS-HBA-LSI-9211-8i-FW-P20-IT-Mode-for-ZFS-FreeNAS-unRAID-AU/133159382201?ssPageName=STRK%3AMEBIDX%3AIT&_trksid=p2057872.m2749.l2649) which was reportedly already flashed to IT mode. After installing the card and connecting the drives, I couldn't get them to detect in Unraid.
A few flashes later, I've got the card with a BIOS and the drives are appearing in it's report during POST and if I use the boards boot menu, I can see the drives listed there as well. As soon as I get to Unraid, I get the alerts that all my array drives cannot be detected, the cache drives are still connected to the onboard SATA and appears as expected. I've tried both the Dell IT and LSI IT firmware (as per https://forums.unraid.net/topic/12114-lsi-controller-fw-updates-irit-modes/page/24/?tab=comments#comment-255573).
When the card arrived it was showing the controller as SAS2008(??), after reflashing it with LSI P20 it's showing as SAS2008(B2).
Since the drives are appearing in the controllers POST, I am assuming that they are communicating as expected, at least to the card.
The system is a Ryzen 2700x/ASRock X470 Taichi Ultimate with the controller in the second PCI-E slot. I've tried Unraid in both UEFI and Legacy modes, with the Storage OpROM on the same settings as the boot type, still no luck. Attached are my diagnostic logs. I am running the Linuxserver Nvidia version, which again I am unsure if that would be contributing to the issue.
The drives are all 10TB, and a mix of Ironwolfs and EXOS drives, with one WD white label in the mix.
Any help/advice you can give will be greatly apricated. If there is more information you need from me, please let me know.
I'm about to try again with the Dell IT firmware now I've confirmed the drives are appearing to the controller, and will see how that goes.
Edit: No dice with the Dell IT firmware, or upgrading it to LSI either.
-
On 6/12/2019 at 9:41 AM, CHBMB said:
TEST BUILDS FOR NVIDIA/DVB COMBINED
People have asked if I'll produce a combined Nvidia/DVB build. Here's the thing, I have no intention of producing separate and combined builds, the workload is just too much for something I have no need of. It would need 8 builds on top of the Nvidia build to do so. I will however produce a combined build, depending on two conditions.
1. People don't mind an increased download size.
2. It works reliably.
However I no longer have any DVB hardware so I can't test. So I've produced some combination builds for people to try out. I am only doing this for v6.7.1rc2, so if nobody tests each build then it's not going to happen. So if you want it, YOU need to test it.
HOW TO USE
1. Download the Nvidia build of v6.7.1rc2 (Important - Do not use any other version)
2. Once the build has downloaded and the window indicating the copying to flash has happened and before you reboot, download one of the attached zip files depending on which DVB build you use, unpack it and copy across the bzmodules and bzfirmware files to your flash disk.
3. Reboot
I know that the Nvidia Plugin will not report the correct version number, that's an easy fix in the future if this works. Once you've rebooted I need to know two things for each build.
1. Does the Nvidia hardware encoding work with Plex/Emby/Jellyfin?
2. Does the DVB hardware work?
libreelec-nvidia-v6.7.1rc2.zip 22.81 MB · 8 downloads tbs-os-nvidia-v6.7.1rc2.zip 18.35 MB · 0 downloads tbs-crazycat-nvidia-v6.7.1rc2.zip 18.51 MB · 0 downloads dd-nvidia-v6.7.1rc2.zip 17.47 MB · 3 downloads
Hi CHBMB,
I'm very interested in having both nVidia and DVB drivers in the same build, but with 6.7.2 released I'm hesitant to revert back to an older version of Unraid.
What I do have though is a spare WinTV-HVR-2200-DVB-T, MULTI-PAL 89619 LF (rev. D3F2) that I would be happy to ship to you and for you to keep. They are PAL, so if you're in a NTSC region they will be usless, but I'm happy to send them to anyone for testing this project.
Intermittent IRQ errors in logs
in General Support
Posted
By downing the ports on the other interfaces I was able to eliminate the macvlan interrupts, but I just had the server lock up.
The following is repeated within my server logs, so it was still operating enough to log the errors, but I couldn't access the server and it wouldn't respond to a keyboard either.