eribre Posted December 8, 2023 Share Posted December 8, 2023 Hi, seems like this blacklist fix with the newest driver version (for RTL8156) does not work for the 8153 (in satechi usb-c to rj45 1gbe) in unraid 6.12.5+ Setup (network) Intel 2.5gig from NAS to PC Realtek 1gig from NAS to router/lan The usb nic works if it is in eth1 using active backup. But as soon as it's moved to eth0, since I want that to be the internet access point, it stops working. Using the GUI boot I can see that the MAC address does not show up for eth0. Also, when the 8153 usb nic is moved to eth0 Unraid starts to hang for a minute or 2 during boot (triggering udev events... dont recall exact words). This is only after 6.12.5. Rolling back to .4 fixes it. tower-diagnostics-20231208-1417.zip Quote Link to comment
JorgeB Posted December 9, 2023 Share Posted December 9, 2023 9 hours ago, eribre said: This is only after 6.12.5. Rolling back to .4 fixes it. Try v6.12.6 again but without the plugin, rtl8152 since v6.12.5 now works with or without the plugin, not sure about that one. 1 Quote Link to comment
ich777 Posted December 9, 2023 Share Posted December 9, 2023 10 hours ago, eribre said: Hi, seems like this blacklist fix with the newest driver version (for RTL8156) does not work for the 8153 (in satechi usb-c to rj45 1gbe) in unraid 6.12.5+ It seems that in your case another driver is used, can you please try to do the following with the plugin installed: echo "blacklist cdc_ether" > /boot/config/modprobe.d/cdc_ether.conf It seems like that your NIC is using another driver. However as @JorgeB said it might be possible that you even don't need the R8152 anymore. Can you please also test what removing the R8152 does after a reboot and if everything is working as expected (of course you have to remove the file /boot/config/modprobe.d/cdc_ether.conf first <- otherwise you won't have network!)? 1 Quote Link to comment
jinlife Posted December 9, 2023 Author Share Posted December 9, 2023 @ich777 @eribre It seems cdc driver is quite complex, I would suggest to blacklist all 3 of them to completely remove its impact. cdc_mbim cdc_ncm cdc_ether Quote Link to comment
eribre Posted December 9, 2023 Share Posted December 9, 2023 @ich777 @JorgeB Already tried without driver first. Ended up on this thread trying to figure out what's wrong and tried the driver and the new version of the driver when that came out about a day after that. Then I asked you guys. Thanks for the quick response btw, testing the new blacklist now @jinlife Quote Link to comment
eribre Posted December 9, 2023 Share Posted December 9, 2023 So, with the blocklist and with driver. no go. With this one I spotted "modprobe FATAL: module r8152 is in use" during boot. With the blocklist (minus ether) and without driver. Doesn't work either. The modprobe message was spotted again. Diagnostics from the attempt with parts of the blocklist (minus ether) and without the driver included. tower-diagnostics-20231209-1043.zip Quote Link to comment
ich777 Posted December 9, 2023 Share Posted December 9, 2023 3 hours ago, eribre said: with the blocklist and with driver Yes, that what I was saying above, you can‘t blacklist the built in driver when you uninstall the plugin becuase that means that you would have no available driver to use. 3 hours ago, eribre said: With the blocklist (minus ether) and without driver About what blacklist are you talking exactly? When the driver is not installed there should be no blacklist file in place. Just for clarification, have you copy pasted my command from above in a Terminal from Unraid and after that rebooted with the driver plugin from @jinlife already installed? After installing the plugin you manually have to copy/paste the command from above and reboot. Quote Link to comment
eribre Posted December 9, 2023 Share Posted December 9, 2023 Sry, did the test runs in a bit of a rush, but I forgot to mention that I tried a clean install of 6.12.6 without the old config, just to check. I had disconnected the intel nic's cable and unraid autoconfigured itself to use the usb nic as a active backup. That worked fine, but as soon as I tried to move the usb nic to eth0 connection was lost and the behavior mentioned earlier (pause during boot etc,) happened. Just tried installing the driver, checked that it autocreated the one modprobe.d file, then ran the command you wrote. Seeing the same issue still. Also tried mbim block earlier, same result. But below is the diagnostics for a test run with the driver installed and with the default ncm file and the ether file. Sorry if my writing wasn't clear btw. tower-diagnostics-20231209-1526.zip Quote Link to comment
JorgeB Posted December 10, 2023 Share Posted December 10, 2023 11 hours ago, eribre said: Just tried installing the driver, checked that it autocreated the one modprobe.d file, then ran the command you wrote. With the driver still installed also blacklist this one 22 hours ago, jinlife said: cdc_mbim Then reboot Quote Link to comment
ich777 Posted December 10, 2023 Share Posted December 10, 2023 11 hours ago, eribre said: Just tried installing the driver, checked that it autocreated the one modprobe.d file, then ran the command you wrote. Seeing the same issue still. Also tried mbim block earlier, same result. But below is the diagnostics for a test run with the driver installed and with the default ncm file and the ether file. Sorry if my writing wasn't clear btw. I've gone through the source and your specific Vendor/Device ID is supported by the RTL8152 plugin but it failed to install as you can see here: Dec 9 15:24:59 Tower root: -----------------------Downloading RTL8152 package!------------------------- Dec 9 15:24:59 Tower root: --------This could take some time, please don't close this window!---------- Dec 9 15:24:59 Tower root: Dec 9 15:24:59 Tower root: -----------------------Can't download RTL8152 package----------------------- Dec 9 15:24:59 Tower root: plugin: run failed: '/bin/bash' returned 1 Are you sure that the plugin is correctly installed? Please check if the plugin is in the "Plugin Error" tab on the Plugin page, uninstall it and try to reinstall it while your Intel NIC is connected and make sure that the plugin actually says that it is installed and the Done button appeared in the plugin installation popup. Make sure you have the cdc_ether.conf still in place and after that reboot your server and please pull new Diagnostics and post them here if the NIC doesn't work after that. Quote Link to comment
eribre Posted December 10, 2023 Share Posted December 10, 2023 Reinstalled, and no error tab in the plugin page (on 6.12.4 that is). Added cdc_ether (and mbim as requested by @JorgeB). Then I reboot without updating to .6. No issues with either nics. No plugin error tab. Shares mount on my pc, etc. Diagnostics (-1603.zip) included. Then I go to update to .6 using the tool in the tools page. I wait until that is finished, then unraid asks for me to wait until certain background tasks are finished. Which I do. I notice it mentions updating/downloading the driver again. Checked the plugin page, no error still. Go to reboot, and from there on, the errors start. Modprobe FATAL.. as mentioned earlier, stuck for a minute or 2. Diagnostics from that (-1701.zip) included. Hope this helps clear up things. tower-diagnostics-20231210-1603.zip tower-diagnostics-20231210-1701.zip Quote Link to comment
ich777 Posted December 10, 2023 Share Posted December 10, 2023 15 minutes ago, eribre said: Added cdc_ether (and mbim as requested by @JorgeB). I think you mean cdc_mbim? Can you remove that? 17 minutes ago, eribre said: Then I reboot without updating to .6. No issues with either nics. No plugin error tab. Shares mount on my pc, etc. From what version? From the Diagnostics I see 6.12.4? 19 minutes ago, eribre said: Go to reboot, and from there on, the errors start. Modprobe FATAL.. as mentioned earlier, stuck for a minute or 2. Where does it say that? Did you type in a command? 22 minutes ago, eribre said: Hope this helps clear up things. Please execute this command once and reboot and make sure the plugin is installed and see if that fixes the error: echo "blacklist r8153_ecm" > /boot/config/modprobe.d/r8153_ecm.conf (leave the other three files in place) Quote Link to comment
eribre Posted December 10, 2023 Share Posted December 10, 2023 Yes, cdc_mbim, just shortened it in writing here... Removing it now. From version 6.12.4 to 6.12.6. I realise that was not the clearest way of writing that. The first diagnostics file was from after installing the driver to show that things were installed correctly, the second file is after the upgrade to 6.12.6. The modprobe thing, is what I mentioned earlier of seeing the message "modprobe FATAL: module r8152 is in use" during bootup of the unraid server. Followed shortly by the 2 minute stop at the udev portion of boot (forget the exact words). Figured it was worth mentioning. I did not type in a command that you guys did tell me to, just to be clear. Im no linux guru, but this isn't my first time with a CLI. Ran the command blacklisting r8153_ecm. Rebooted, things were fine, and then ran the upgrade tool for Unraid 6.12.6. And it seems the r8153_ecm blacklist did it! Everything booted as it should, and I can remotely access the server! Thanks you so much for the help! Sorry if I wasn't super clear. Anyhow, I included the diagnostics of the confirmed working configuration in case you guys wanted to pick it apart a bit more. tower-diagnostics-20231210-1948.zip 1 Quote Link to comment
ich777 Posted December 10, 2023 Share Posted December 10, 2023 I've pushed an update to the plugin so that it blacklist all cdc drivers. 1 Quote Link to comment
eribre Posted December 10, 2023 Share Posted December 10, 2023 (edited) Including r8153_ecm? If not, perhaps a note for those who have similar issues maybe? Edited December 10, 2023 by eribre Quote Link to comment
ich777 Posted December 10, 2023 Share Posted December 10, 2023 32 minutes ago, eribre said: Including r8153_ecm? Yes, why not? This update should be a solution so that the plugin is workig again for all users. I just waited for your confirmation since your posts where a bit confusing. Quote Link to comment
eribre Posted December 10, 2023 Share Posted December 10, 2023 Sorry, again. Was just asking if r8153_ecm was included and if it was not included I just wrote a suggestion. Everythin is fine now! 1 1 Quote Link to comment
Aviv Posted December 13, 2023 Share Posted December 13, 2023 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03) should i upgrade the unraid version? Quote Link to comment
ich777 Posted December 13, 2023 Share Posted December 13, 2023 2 hours ago, Aviv said: should i upgrade the unraid version? Yes, please make sure that your plugin is also up to date! Quote Link to comment
cardo Posted December 13, 2023 Share Posted December 13, 2023 Hi All, For the last several days I've had my unRAID lock up/go offline. Because of the lockup, I wasn't able to capture the syslog data, but I did notice that there were some no response type errors in eth0. Today while I was performing some file activity I lost my connection to the share, so I went to the syslog and captured a diagnostic. I do see a lot of errors. I'm not certain they are related to my RealTek device, but I thought I'd start here since the eth0 errors. I'm running 6.12.6 with the latest RealTek plugin and before 6.12.5 released, my system had been rock solid for years. Any help would be really appreciated. diagnostics-20231213-0649.zip Quote Link to comment
ich777 Posted December 13, 2023 Share Posted December 13, 2023 5 hours ago, cardo said: Hi All, You have a macvlan trace in your syslog: Dec 12 22:17:53 MojoRyzen kernel: ------------[ cut here ]------------ Dec 12 22:17:53 MojoRyzen kernel: NETDEV WATCHDOG: eth0 (r8152): transmit queue 0 timed out Dec 12 22:17:53 MojoRyzen kernel: WARNING: CPU: 20 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x14e/0x1c0 Dec 12 22:17:53 MojoRyzen kernel: Modules linked in: xt_connmark xt_comment iptable_raw wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha xt_mark tcp_diag udp_diag inet_diag veth macvlan xt_nat nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 vhost_net tun vhost vhost_iotlb tap nvidia_uvm(PO) xfs nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc bonding tls r8152(O) igb i2c_algo_bit nvidia_drm(PO) nvidia_modeset(PO) edac_mce_amd edac_core intel_rapl_msr intel_rapl_common iosf_mbi kvm_amd nvidia(PO) kvm crct10dif_pclmul crc32_pclmul crc32c_intel video Dec 12 22:17:53 MojoRyzen kernel: ghash_clmulni_intel sha512_ssse3 sha256_ssse3 btusb sha1_ssse3 drm_kms_helper btrtl aesni_intel btbcm btintel input_leds crypto_simd wmi_bmof mxm_wmi cryptd drm bluetooth mpt3sas rapl nvme backlight syscopyarea k10temp raid_class hid_apple sysfillrect ahci sysimgblt ccp i2c_piix4 ecdh_generic scsi_transport_sas fb_sys_fops nvme_core ecc led_class libahci i2c_core tpm_crb tpm_tis tpm_tis_core tpm wmi button acpi_cpufreq unix [last unloaded: r8152(O)] Dec 12 22:17:53 MojoRyzen kernel: CPU: 20 PID: 0 Comm: swapper/20 Tainted: P O 6.1.64-Unraid #1 Dec 12 22:17:53 MojoRyzen kernel: Hardware name: To Be Filled By O.E.M. X570 Taichi/X570 Taichi, BIOS P5.00 10/19/2022 Dec 12 22:17:53 MojoRyzen kernel: RIP: 0010:dev_watchdog+0x14e/0x1c0 Dec 12 22:17:53 MojoRyzen kernel: Code: a4 c5 00 00 75 26 48 89 ef c6 05 a8 a4 c5 00 01 e8 59 23 fc ff 44 89 f1 48 89 ee 48 c7 c7 58 80 15 82 48 89 c2 e8 ab 73 93 ff <0f> 0b 48 89 ef e8 32 fb ff ff 48 8b 83 88 fc ff ff 48 89 ef 44 89 Dec 12 22:17:53 MojoRyzen kernel: RSP: 0018:ffffc90000670ea8 EFLAGS: 00010282 Dec 12 22:17:53 MojoRyzen kernel: RAX: 0000000000000000 RBX: ffff888106075448 RCX: 0000000000000003 Dec 12 22:17:53 MojoRyzen kernel: RDX: 0000000000000104 RSI: 0000000000000003 RDI: 00000000ffffffff Dec 12 22:17:53 MojoRyzen kernel: RBP: ffff888106075000 R08: 0000000000000000 R09: ffffffff829513f0 Dec 12 22:17:53 MojoRyzen kernel: R10: 00003fffffffffff R11: 2074696d736e6172 R12: 0000000000000000 Dec 12 22:17:53 MojoRyzen kernel: R13: ffff88810607539c R14: 0000000000000000 R15: 0000000000000001 Dec 12 22:17:53 MojoRyzen kernel: FS: 0000000000000000(0000) GS:ffff888ffed00000(0000) knlGS:0000000000000000 Dec 12 22:17:53 MojoRyzen kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 12 22:17:53 MojoRyzen kernel: CR2: 0000000000452b98 CR3: 0000000103894000 CR4: 0000000000350ee0 Dec 12 22:17:53 MojoRyzen kernel: Call Trace: Dec 12 22:17:53 MojoRyzen kernel: <IRQ> Dec 12 22:17:53 MojoRyzen kernel: ? __warn+0xab/0x122 Dec 12 22:17:53 MojoRyzen kernel: ? report_bug+0x109/0x17e Dec 12 22:17:53 MojoRyzen kernel: ? dev_watchdog+0x14e/0x1c0 Dec 12 22:17:53 MojoRyzen kernel: ? handle_bug+0x41/0x6f Dec 12 22:17:53 MojoRyzen kernel: ? exc_invalid_op+0x13/0x60 Dec 12 22:17:53 MojoRyzen kernel: ? asm_exc_invalid_op+0x16/0x20 Dec 12 22:17:53 MojoRyzen kernel: ? dev_watchdog+0x14e/0x1c0 ### [PREVIOUS LINE REPEATED 1 TIMES] ### Dec 12 22:17:53 MojoRyzen kernel: ? psched_ppscfg_precompute+0x57/0x57 ### [PREVIOUS LINE REPEATED 1 TIMES] ### Dec 12 22:17:53 MojoRyzen kernel: call_timer_fn+0x6f/0x10d Dec 12 22:17:53 MojoRyzen kernel: __run_timers+0x144/0x184 Dec 12 22:17:53 MojoRyzen kernel: ? tick_init_jiffy_update+0x7c/0x7c Dec 12 22:17:53 MojoRyzen kernel: ? update_process_times+0x7a/0x81 Dec 12 22:17:53 MojoRyzen kernel: ? tick_sched_timer+0x43/0x71 Dec 12 22:17:53 MojoRyzen kernel: ? __hrtimer_next_event_base+0x27/0x81 Dec 12 22:17:53 MojoRyzen kernel: run_timer_softirq+0x2b/0x43 Dec 12 22:17:53 MojoRyzen kernel: __do_softirq+0x129/0x288 Dec 12 22:17:53 MojoRyzen kernel: __irq_exit_rcu+0x5e/0xb8 Dec 12 22:17:53 MojoRyzen kernel: sysvec_apic_timer_interrupt+0x85/0xa6 Dec 12 22:17:53 MojoRyzen kernel: </IRQ> Dec 12 22:17:53 MojoRyzen kernel: <TASK> Dec 12 22:17:53 MojoRyzen kernel: asm_sysvec_apic_timer_interrupt+0x16/0x20 Dec 12 22:17:53 MojoRyzen kernel: RIP: 0010:cpuidle_enter_state+0x11d/0x202 Dec 12 22:17:53 MojoRyzen kernel: Code: 2b ff 9f ff 45 84 ff 74 1b 9c 58 0f 1f 40 00 0f ba e0 09 73 08 0f 0b fa 0f 1f 44 00 00 31 ff e8 a3 c0 a4 ff fb 0f 1f 44 00 00 <45> 85 e4 0f 88 ba 00 00 00 48 8b 04 24 49 63 cc 48 6b d1 68 49 29 Dec 12 22:17:53 MojoRyzen kernel: RSP: 0018:ffffc900001f7e98 EFLAGS: 00000246 Dec 12 22:17:53 MojoRyzen kernel: RAX: ffff888ffed00000 RBX: ffff888109157000 RCX: 0000000000000000 Dec 12 22:17:53 MojoRyzen kernel: RDX: 000009412b09c6cd RSI: ffffffff820d7e01 RDI: ffffffff820d830a Dec 12 22:17:53 MojoRyzen kernel: RBP: 0000000000000001 R08: 0000000000000002 R09: 0000000000000002 Dec 12 22:17:53 MojoRyzen kernel: R10: 0000000000000020 R11: 000000000000afc8 R12: 0000000000000001 Dec 12 22:17:53 MojoRyzen kernel: R13: ffffffff823237a0 R14: 000009412b09c6cd R15: 0000000000000000 Dec 12 22:17:53 MojoRyzen kernel: ? cpuidle_enter_state+0xf7/0x202 Dec 12 22:17:53 MojoRyzen kernel: cpuidle_enter+0x2a/0x38 Dec 12 22:17:53 MojoRyzen kernel: do_idle+0x18d/0x1fb Dec 12 22:17:53 MojoRyzen kernel: cpu_startup_entry+0x2a/0x2c Dec 12 22:17:53 MojoRyzen kernel: start_secondary+0x101/0x101 Dec 12 22:17:53 MojoRyzen kernel: secondary_startup_64_no_verify+0xce/0xdb Dec 12 22:17:53 MojoRyzen kernel: </TASK> Dec 12 22:17:53 MojoRyzen kernel: ---[ end trace 0000000000000000 ]--- If you are using macvlan in your Docker settings please disable the Bridge in your Network settings, if you need the Bridge then please change to ipvlan in your Docker settings. Quote Link to comment
cardo Posted December 13, 2023 Share Posted December 13, 2023 29 minutes ago, ich777 said: You have a macvlan trace in your syslog: Dec 12 22:17:53 MojoRyzen kernel: ------------[ cut here ]------------ Dec 12 22:17:53 MojoRyzen kernel: NETDEV WATCHDOG: eth0 (r8152): transmit queue 0 timed out Dec 12 22:17:53 MojoRyzen kernel: WARNING: CPU: 20 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x14e/0x1c0 Dec 12 22:17:53 MojoRyzen kernel: Modules linked in: xt_connmark xt_comment iptable_raw wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha xt_mark tcp_diag udp_diag inet_diag veth macvlan xt_nat nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 vhost_net tun vhost vhost_iotlb tap nvidia_uvm(PO) xfs nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc bonding tls r8152(O) igb i2c_algo_bit nvidia_drm(PO) nvidia_modeset(PO) edac_mce_amd edac_core intel_rapl_msr intel_rapl_common iosf_mbi kvm_amd nvidia(PO) kvm crct10dif_pclmul crc32_pclmul crc32c_intel video Dec 12 22:17:53 MojoRyzen kernel: ghash_clmulni_intel sha512_ssse3 sha256_ssse3 btusb sha1_ssse3 drm_kms_helper btrtl aesni_intel btbcm btintel input_leds crypto_simd wmi_bmof mxm_wmi cryptd drm bluetooth mpt3sas rapl nvme backlight syscopyarea k10temp raid_class hid_apple sysfillrect ahci sysimgblt ccp i2c_piix4 ecdh_generic scsi_transport_sas fb_sys_fops nvme_core ecc led_class libahci i2c_core tpm_crb tpm_tis tpm_tis_core tpm wmi button acpi_cpufreq unix [last unloaded: r8152(O)] Dec 12 22:17:53 MojoRyzen kernel: CPU: 20 PID: 0 Comm: swapper/20 Tainted: P O 6.1.64-Unraid #1 Dec 12 22:17:53 MojoRyzen kernel: Hardware name: To Be Filled By O.E.M. X570 Taichi/X570 Taichi, BIOS P5.00 10/19/2022 Dec 12 22:17:53 MojoRyzen kernel: RIP: 0010:dev_watchdog+0x14e/0x1c0 Dec 12 22:17:53 MojoRyzen kernel: Code: a4 c5 00 00 75 26 48 89 ef c6 05 a8 a4 c5 00 01 e8 59 23 fc ff 44 89 f1 48 89 ee 48 c7 c7 58 80 15 82 48 89 c2 e8 ab 73 93 ff <0f> 0b 48 89 ef e8 32 fb ff ff 48 8b 83 88 fc ff ff 48 89 ef 44 89 Dec 12 22:17:53 MojoRyzen kernel: RSP: 0018:ffffc90000670ea8 EFLAGS: 00010282 Dec 12 22:17:53 MojoRyzen kernel: RAX: 0000000000000000 RBX: ffff888106075448 RCX: 0000000000000003 Dec 12 22:17:53 MojoRyzen kernel: RDX: 0000000000000104 RSI: 0000000000000003 RDI: 00000000ffffffff Dec 12 22:17:53 MojoRyzen kernel: RBP: ffff888106075000 R08: 0000000000000000 R09: ffffffff829513f0 Dec 12 22:17:53 MojoRyzen kernel: R10: 00003fffffffffff R11: 2074696d736e6172 R12: 0000000000000000 Dec 12 22:17:53 MojoRyzen kernel: R13: ffff88810607539c R14: 0000000000000000 R15: 0000000000000001 Dec 12 22:17:53 MojoRyzen kernel: FS: 0000000000000000(0000) GS:ffff888ffed00000(0000) knlGS:0000000000000000 Dec 12 22:17:53 MojoRyzen kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 12 22:17:53 MojoRyzen kernel: CR2: 0000000000452b98 CR3: 0000000103894000 CR4: 0000000000350ee0 Dec 12 22:17:53 MojoRyzen kernel: Call Trace: Dec 12 22:17:53 MojoRyzen kernel: <IRQ> Dec 12 22:17:53 MojoRyzen kernel: ? __warn+0xab/0x122 Dec 12 22:17:53 MojoRyzen kernel: ? report_bug+0x109/0x17e Dec 12 22:17:53 MojoRyzen kernel: ? dev_watchdog+0x14e/0x1c0 Dec 12 22:17:53 MojoRyzen kernel: ? handle_bug+0x41/0x6f Dec 12 22:17:53 MojoRyzen kernel: ? exc_invalid_op+0x13/0x60 Dec 12 22:17:53 MojoRyzen kernel: ? asm_exc_invalid_op+0x16/0x20 Dec 12 22:17:53 MojoRyzen kernel: ? dev_watchdog+0x14e/0x1c0 ### [PREVIOUS LINE REPEATED 1 TIMES] ### Dec 12 22:17:53 MojoRyzen kernel: ? psched_ppscfg_precompute+0x57/0x57 ### [PREVIOUS LINE REPEATED 1 TIMES] ### Dec 12 22:17:53 MojoRyzen kernel: call_timer_fn+0x6f/0x10d Dec 12 22:17:53 MojoRyzen kernel: __run_timers+0x144/0x184 Dec 12 22:17:53 MojoRyzen kernel: ? tick_init_jiffy_update+0x7c/0x7c Dec 12 22:17:53 MojoRyzen kernel: ? update_process_times+0x7a/0x81 Dec 12 22:17:53 MojoRyzen kernel: ? tick_sched_timer+0x43/0x71 Dec 12 22:17:53 MojoRyzen kernel: ? __hrtimer_next_event_base+0x27/0x81 Dec 12 22:17:53 MojoRyzen kernel: run_timer_softirq+0x2b/0x43 Dec 12 22:17:53 MojoRyzen kernel: __do_softirq+0x129/0x288 Dec 12 22:17:53 MojoRyzen kernel: __irq_exit_rcu+0x5e/0xb8 Dec 12 22:17:53 MojoRyzen kernel: sysvec_apic_timer_interrupt+0x85/0xa6 Dec 12 22:17:53 MojoRyzen kernel: </IRQ> Dec 12 22:17:53 MojoRyzen kernel: <TASK> Dec 12 22:17:53 MojoRyzen kernel: asm_sysvec_apic_timer_interrupt+0x16/0x20 Dec 12 22:17:53 MojoRyzen kernel: RIP: 0010:cpuidle_enter_state+0x11d/0x202 Dec 12 22:17:53 MojoRyzen kernel: Code: 2b ff 9f ff 45 84 ff 74 1b 9c 58 0f 1f 40 00 0f ba e0 09 73 08 0f 0b fa 0f 1f 44 00 00 31 ff e8 a3 c0 a4 ff fb 0f 1f 44 00 00 <45> 85 e4 0f 88 ba 00 00 00 48 8b 04 24 49 63 cc 48 6b d1 68 49 29 Dec 12 22:17:53 MojoRyzen kernel: RSP: 0018:ffffc900001f7e98 EFLAGS: 00000246 Dec 12 22:17:53 MojoRyzen kernel: RAX: ffff888ffed00000 RBX: ffff888109157000 RCX: 0000000000000000 Dec 12 22:17:53 MojoRyzen kernel: RDX: 000009412b09c6cd RSI: ffffffff820d7e01 RDI: ffffffff820d830a Dec 12 22:17:53 MojoRyzen kernel: RBP: 0000000000000001 R08: 0000000000000002 R09: 0000000000000002 Dec 12 22:17:53 MojoRyzen kernel: R10: 0000000000000020 R11: 000000000000afc8 R12: 0000000000000001 Dec 12 22:17:53 MojoRyzen kernel: R13: ffffffff823237a0 R14: 000009412b09c6cd R15: 0000000000000000 Dec 12 22:17:53 MojoRyzen kernel: ? cpuidle_enter_state+0xf7/0x202 Dec 12 22:17:53 MojoRyzen kernel: cpuidle_enter+0x2a/0x38 Dec 12 22:17:53 MojoRyzen kernel: do_idle+0x18d/0x1fb Dec 12 22:17:53 MojoRyzen kernel: cpu_startup_entry+0x2a/0x2c Dec 12 22:17:53 MojoRyzen kernel: start_secondary+0x101/0x101 Dec 12 22:17:53 MojoRyzen kernel: secondary_startup_64_no_verify+0xce/0xdb Dec 12 22:17:53 MojoRyzen kernel: </TASK> Dec 12 22:17:53 MojoRyzen kernel: ---[ end trace 0000000000000000 ]--- If you are using macvlan in your Docker settings please disable the Bridge in your Network settings, if you need the Bridge then please change to ipvlan in your Docker settings. Hi @ich777, Thank you for the quick response. I will admit I'm not entirely sure what the issue is here. I've been running this exact configuration for several years without issue. Was there a change in 6.12.5 or .6 that made my configuration an issue? Also, I currently swapped back to using my on board gigabit card and am not seeing any issues at all so far. I'm trying to figure out what I need to change. Thanks! Quote Link to comment
ich777 Posted December 13, 2023 Share Posted December 13, 2023 9 minutes ago, cardo said: I'm trying to figure out what I need to change. See here: https://docs.unraid.net/unraid-os/release-notes/6.12.4/#fix-for-macvlan-call-traces 1 Quote Link to comment
cardo Posted December 13, 2023 Share Posted December 13, 2023 1 hour ago, ich777 said: See here: https://docs.unraid.net/unraid-os/release-notes/6.12.4/#fix-for-macvlan-call-traces I just made the change. I'll report back if I have another system lockup. It generally happens within 24 hours. Thanks again! 1 Quote Link to comment
cardo Posted December 21, 2023 Share Posted December 21, 2023 (edited) On 12/13/2023 at 2:50 PM, cardo said: I just made the change. I'll report back if I have another system lockup. It generally happens within 24 hours. Thanks again! System just hard locked again. I have to power it down when this occurs. Just before it locked up I did see some some warning and errors related to the USB NIC about timeouts, etc. I stream music videos once a week from unRAID to my desktop PC. Both have 2.5Gbps cards. The desktop PC has an onboard NIC and unRAID has the RealTek external USB. The last time this occurred was also when I did 12+ hours of streaming. The issue started after 6.12.5, but I am not necessarily blaming unRAID or the NIC drivers it could very well be that the external NIC isn't good. Does anyone know of an external USB 2.5Gbps NIC that has built in unRAID support? I'm tired of fighting with the RealTek. Edited December 21, 2023 by cardo Quote Link to comment
Recommended Posts
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.