Realterminator

Hello everyone, I had a kernel panic today. Some setting on the network card does not seem to be ok. Have any of you seen this or even managed to solve it? 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) Subsystem: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 54 IOMMU group: 10 ... Kernel driver in use: r8168 Kernel modules: r8169, r8168 root@Storage:~# ethtool -i eth0 driver: r8168 version: 8.052.01-NAPI firmware-version: expansion-rom-version: bus-info: 0000:01:00.0 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: yes supports-priv-flags: no root@Storage:~# modinfo r8168 filename: /lib/modules/6.1.64-Unraid/kernel/drivers/net/ethernet/realtek/r8168.ko.xz version: 8.052.01-NAPI license: GPL description: RealTek RTL-8168 Gigabit Ethernet driver author: Realtek and the Linux r8168 crew <[email protected]> [Thu Feb 8 13:00:16 2024] r8168: loading out-of-tree module taints kernel. [Thu Feb 8 13:00:16 2024] r8168 Gigabit Ethernet driver 8.052.01-NAPI loaded [Thu Feb 8 13:00:16 2024] r8168 0000:01:00.0: enabling device (0000 -> 0003) [Thu Feb 8 13:00:16 2024] r8168: This product is covered by one or more of the following patents: US6,570,884, US6,115,776, and US6,327,625. [Thu Feb 8 13:00:16 2024] r8168 Copyright (C) 2023 Realtek NIC software team <[email protected]> [Thu Feb 8 13:00:16 2024] r8168 Gigabit Ethernet driver 8.052.01-NAPI loaded [Thu Feb 8 13:00:16 2024] r8168 0000:02:00.0: enabling device (0000 -> 0003) [Thu Feb 8 13:00:16 2024] r8168: This product is covered by one or more of the following patents: US6,570,884, US6,115,776, and US6,327,625. [Thu Feb 8 13:00:16 2024] r8168 Copyright (C) 2023 Realtek NIC software team <[email protected]> [Thu Feb 8 13:00:18 2024] r8168 Gigabit Ethernet driver 8.052.01-NAPI loaded [Thu Feb 8 13:00:18 2024] r8168: This product is covered by one or more of the following patents: US6,570,884, US6,115,776, and US6,327,625. [Thu Feb 8 13:00:18 2024] r8168 Copyright (C) 2023 Realtek NIC software team <[email protected]> [Thu Feb 8 13:00:18 2024] r8168 Gigabit Ethernet driver 8.052.01-NAPI loaded [Thu Feb 8 13:00:18 2024] r8168: This product is covered by one or more of the following patents: US6,570,884, US6,115,776, and US6,327,625. [Thu Feb 8 13:00:18 2024] r8168 Copyright (C) 2023 Realtek NIC software team <[email protected]> [Thu Feb 8 13:06:31 2024] r8168: eth0: link up [Thu Feb 8 13:06:35 2024] r8168: eth1: link up [Thu Feb 8 13:26:11 2024] r8168: eth0: link up [Thu Feb 8 13:31:07 2024] r8168: eth1: link up [Thu Feb 8 13:41:47 2024] r8168: eth0: link up [Thu Feb 8 23:14:11 2024] r8168: eth1: link up ... [Sat Feb 10 00:46:12 2024] r8168: eth1: link up [Sat Feb 10 01:35:56 2024] r8168: eth1: link up [Sat Feb 10 01:43:00 2024] r8168: eth1: link up [Sat Feb 10 01:48:23 2024] r8168 0000:01:00.0 eth0: test_phy_ocp ResetPhyType = 0x02 [Sat Feb 10 01:48:30 2024] WARNING: CPU: 11 PID: 16114 at /usr/src/unraid-r8125-r8152-driver/r8168/src/r8168_n.c:8418 rtl8168_wait_phy_state_ready.isra.0+0x50/0x64 [r8168] [Sat Feb 10 01:48:30 2024] Modules linked in: macvlan udp_diag cdc_acm xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype br_netfilter xfs md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) tcp_diag inet_diag corefreqk(O) ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs bridge stp llc r8168(O) amdgpu edac_mce_amd edac_core intel_rapl_msr intel_rapl_common iosf_mbi kvm_amd kvm gpu_sched drm_buddy i2c_algo_bit drm_ttm_helper ttm drm_display_helper crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 wmi_bmof aesni_intel drm_kms_helper crypto_simd ahci cryptd drm rapl libahci k10temp i2c_piix4 nvme amd_sfh agpgart nvme_core i2c_core syscopyarea ccp sysfillrect [Sat Feb 10 01:48:30 2024] sysimgblt fb_sys_fops tpm_crb video tpm_tis tpm_tis_core wmi tpm backlight acpi_cpufreq button unix [last unloaded: r8168(O)] [Sat Feb 10 01:48:30 2024] Workqueue: events rtl8168_esd_task [r8168] [Sat Feb 10 01:48:30 2024] RIP: 0010:rtl8168_wait_phy_state_ready.isra.0+0x50/0x64 [r8168] [Sat Feb 10 01:48:30 2024] ? rtl8168_wait_phy_state_ready.isra.0+0x50/0x64 [r8168] [Sat Feb 10 01:48:30 2024] ? rtl8168_wait_phy_state_ready.isra.0+0x50/0x64 [r8168] [Sat Feb 10 01:48:30 2024] rtl8168_esd_task+0x6e0/0xc0e [r8168] [Sat Feb 10 01:48:31 2024] WARNING: CPU: 11 PID: 16114 at /usr/src/unraid-r8125-r8152-driver/r8168/src/r8168_n.c:8654 rtl8168_wait_phy_ups_resume+0x4a/0x57 [r8168] [Sat Feb 10 01:48:31 2024] Modules linked in: macvlan udp_diag cdc_acm xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype br_netfilter xfs md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) tcp_diag inet_diag corefreqk(O) ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs bridge stp llc r8168(O) amdgpu edac_mce_amd edac_core intel_rapl_msr intel_rapl_common iosf_mbi kvm_amd kvm gpu_sched drm_buddy i2c_algo_bit drm_ttm_helper ttm drm_display_helper crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 wmi_bmof aesni_intel drm_kms_helper crypto_simd ahci cryptd drm rapl libahci k10temp i2c_piix4 nvme amd_sfh agpgart nvme_core i2c_core syscopyarea ccp sysfillrect [Sat Feb 10 01:48:31 2024] sysimgblt fb_sys_fops tpm_crb video tpm_tis tpm_tis_core wmi tpm backlight acpi_cpufreq button unix [last unloaded: r8168(O)] [Sat Feb 10 01:48:31 2024] Workqueue: events rtl8168_esd_task [r8168] [Sat Feb 10 01:48:31 2024] RIP: 0010:rtl8168_wait_phy_ups_resume+0x4a/0x57 [r8168] [Sat Feb 10 01:48:31 2024] ? rtl8168_wait_phy_ups_resume+0x4a/0x57 [r8168] [Sat Feb 10 01:48:31 2024] ? rtl8168_wait_phy_ups_resume+0x4a/0x57 [r8168] [Sat Feb 10 01:48:31 2024] ? rtl8168_wait_phy_ups_resume+0x37/0x57 [r8168] [Sat Feb 10 01:48:31 2024] rtl8168_esd_task+0xb99/0xc0e [r8168] [Sat Feb 10 01:49:04 2024] r8168: eth0: link up [Sat Feb 10 02:02:59 2024] r8168: eth1: link up [Sat Feb 10 02:11:24 2024] r8168: eth0: link up

<interface type='direct'> <mac address='52:54:00:66:be:a8'/> <source dev='eth0.20' mode='bridge'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface>

I have eth0 as mgmt interface Vlan interface eth0.10 an eth0.20 For Docker I can select eth0.20 without problems. But how can I connect a VM to interface eth0.20? Only virbr0 can I select from Gui. I think I have to insert the network card directly in the xml, the question is only what exactlyTahnks This is not working <interface type='bridge'> <mac address='52:54:00:66:be:a8'/> <source bridge='eth0.20'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> Thanks for the help

Fix is: add device to container USBDEVICES is only that permissions set to device inside the container

Have approximately the same question: ----- Debugging information ----- ----- ----- ----- System ----- ----- arch: x86_64 ----- ----- ----- ----- Versions ----- ----- image: v5.1.0 ----- ----- node: v12.21.0 ----- ----- npm: 6.14.11 ----- ----- ----- ----- ENV ----- ----- SETGID: 100 ----- ----- SETUID: 99 ----- ----- USBDEVICES: /dev/ttyACM0 ----- ------------------------------------------------------------ ----- Step 4 of 5: Applying special settings ----- ------------------------------------------------------------ Some adapters have special requirements/ settings which can be activated by the use of environment variables. For more information take a look at readme.md on Github! Usb-device-support is activated by ENV. Setting permissions for /dev/ttyACM0... chown: Zugriff auf '/dev/ttyACM0' nicht möglich: Datei oder Verzeichnis nicht gefunden chmod: Zugriff auf '/dev/ttyACM0' nicht möglich: Datei oder Verzeichnis nicht gefunden On Unraid root@Storage:/dev/serial/by-id# ls -al /dev/ttyACM0 crw-rw-rw- 1 root dialout 166, 0 Mar 2 17:39 /dev/ttyACM0 Can anyone help me with this?

I have installed and configured Unraid. Now I want to do the configuration from scratch, but without rebuilding the array. The idea is to rewrite the USB stick and then reload the Liezense. And after that to mount the existing array again. How can I mount an existing array in a "new" unraid? Thanks a lot

This problem occurs with Unraid 6.8.2 6.8.3 and 6.9-rc2 Binding... 0000:08:00.0 already bound to vfio-pci /usr/local/sbin/vfio-pci: line 169: /sys/bus/pci/devices/0000:08:00.1/iommu_group/devices/0000:08:00.1/driver/unbind: Permission denied Unbound 0000:08:00.1 from igb Successfully bound the device 8086:10d6 at 0000:08:00.1 to vfio-pci cat /boot/config/vfio-pci.cfg BIND=0000:07:00.0|8086:10d6 0000:07:00.1|8086:10d6 0000:08:00.0|8086:10d6 0000:08:00.1|8086:10d6 07:00.0 Ethernet controller [0200]: Intel Corporation 82575GB Gigabit Network Connection [8086:10d6] (rev 02) Subsystem: Intel Corporation Gigabit VT Quad Port Server Adapter [8086:145a] Kernel driver in use: vfio-pci Kernel modules: igb 07:00.1 Ethernet controller [0200]: Intel Corporation 82575GB Gigabit Network Connection [8086:10d6] (rev 02) Subsystem: Intel Corporation Gigabit VT Quad Port Server Adapter [8086:145a] Kernel driver in use: vfio-pci Kernel modules: igb 08:00.0 Ethernet controller [0200]: Intel Corporation 82575GB Gigabit Network Connection [8086:10d6] (rev 02) Subsystem: Intel Corporation Gigabit VT Quad Port Server Adapter [8086:145a] Kernel driver in use: vfio-pci Kernel modules: igb 08:00.1 Ethernet controller [0200]: Intel Corporation 82575GB Gigabit Network Connection [8086:10d6] (rev 02) Subsystem: Intel Corporation Gigabit VT Quad Port Server Adapter [8086:145a] Kernel modules: igb VIFO-PCI log: Loading config from /boot/config/vfio-pci.cfg BIND=0000:07:00.0|8086:10d6 0000:07:00.1|8086:10d6 0000:08:00.0|8086:10d6 0000:08:00.1|8086:10d6 --- Processing 0000:07:00.0 8086:10d6 Vendor:Device 8086:10d6 found at 0000:07:00.0 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:07:00.0/iommu_group/devices/0000:07:00.0 /sys/bus/pci/devices/0000:07:00.0/iommu_group/devices/0000:07:00.1 Binding... Successfully bound the device 8086:10d6 at 0000:07:00.0 to vfio-pci --- Processing 0000:07:00.1 8086:10d6 Vendor:Device 8086:10d6 found at 0000:07:00.1 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:07:00.1/iommu_group/devices/0000:07:00.0 /sys/bus/pci/devices/0000:07:00.1/iommu_group/devices/0000:07:00.1 Binding... 0000:07:00.0 already bound to vfio-pci 0000:07:00.1 already bound to vfio-pci Successfully bound the device 8086:10d6 at 0000:07:00.1 to vfio-pci --- Processing 0000:08:00.0 8086:10d6 Vendor:Device 8086:10d6 found at 0000:08:00.0 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:08:00.0/iommu_group/devices/0000:08:00.0 /sys/bus/pci/devices/0000:08:00.0/iommu_group/devices/0000:08:00.1 Binding... /usr/local/sbin/vfio-pci: line 169: /sys/bus/pci/devices/0000:08:00.0/iommu_group/devices/0000:08:00.1/driver/unbind: Permission denied Unbound 0000:08:00.1 from igb Successfully bound the device 8086:10d6 at 0000:08:00.0 to vfio-pci --- Processing 0000:08:00.1 8086:10d6 Vendor:Device 8086:10d6 found at 0000:08:00.1 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:08:00.1/iommu_group/devices/0000:08:00.0 /sys/bus/pci/devices/0000:08:00.1/iommu_group/devices/0000:08:00.1 Binding... 0000:08:00.0 already bound to vfio-pci /usr/local/sbin/vfio-pci: line 169: /sys/bus/pci/devices/0000:08:00.1/iommu_group/devices/0000:08:00.1/driver/unbind: Permission denied Unbound 0000:08:00.1 from igb Successfully bound the device 8086:10d6 at 0000:08:00.1 to vfio-pci --- vfio-pci binding complete Devices listed in /sys/bus/pci/drivers/vfio-pci: lrwxrwxrwx 1 root root 0 Feb 16 02:56 0000:07:00.0 -> ../../../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:02.0/0000:05:00.0/0000:06:02.0/0000:07:00.0 lrwxrwxrwx 1 root root 0 Feb 16 02:56 0000:07:00.1 -> ../../../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:02.0/0000:05:00.0/0000:06:02.0/0000:07:00.1 lrwxrwxrwx 1 root root 0 Feb 16 02:56 0000:08:00.0 -> ../../../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:02.0/0000:05:00.0/0000:06:04.0/0000:08:00.0 ls -l /dev/vfio/ total 0 crw------- 1 root root 249, 0 Feb 16 02:56 24 crw------- 1 root root 249, 1 Feb 16 02:56 25 crw-rw-rw- 1 root root 10, 196 Feb 16 02:56 vfio