June 26, 20206 yr 15 hours ago, saarg said: That looks correct. What doesn't look correct is your transcode bind mount. You have mapped /config/transcode on unraid, which is not a user share in unraid so it gets created in ram. Dopu should fix that. You can also tr to add a new variable for NVIDIA_DRIVER_CAPABILITIES and set it to all and see if that changes anything. Wherever I set it I get this: what(): Codecs: Initialize: 'boost::filesystem::temp_directory_path: Not a directory: "/mnt/cache/plextrans"' I've tried my appdata folder and my media folder where tv and movies are. Both say the above error. What is "Dopu?" Thanks again for helping me.
June 26, 20206 yr 10 hours ago, waymon said: Wherever I set it I get this: what(): Codecs: Initialize: 'boost::filesystem::temp_directory_path: Not a directory: "/mnt/cache/plextrans"' I've tried my appdata folder and my media folder where tv and movies are. Both say the above error. What is "Dopu?" Thanks again for helping me. Isn't dopu self explanatory? 😂 It should have been saying you. We can't read your mind, so you need to post the docker run command and also what you do and where the error message pops up.
June 27, 20206 yr FIXED it i have no idea how just the old reset everything and try again hi i have just upgraded to a ryzen for my system and i am unable to get the nvidia driver to see the p400 card i get the following error "NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running." quick system overview b450 mortherboard pci slot 1 p400 pci slot 2 lis card pci slot 3 quadro nvs 295 slot three is set to primary video device and it give an out put on video the cards are both showing in the device list [1022:43c7] 02:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01) [8086:1539] 03:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) [1000:0072] 05:00.0 RAID bus controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03) [10de:06fd] 07:00.0 VGA compatible controller: NVIDIA Corporation G98 [Quadro NVS 295] (rev a1) IOMMU group 1:[1022:1482] 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 2:[1022:1482] 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1483] 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [10de:1cb3] 08:00.0 VGA compatible controller: NVIDIA Corporation GP107GL [Quadro P400] (rev a1) [10de:0fb9] 08:00.1 Audio device: NVIDIA Corporation GP107GL High Definition Audio Controller (rev a1) i have removed the driver and reinstalled it same error i tried with just the p400 in same error i changed the slot of the p400 same error anybody got any ideas Edited June 27, 20206 yr by andy harris
June 28, 20206 yr I installed a new GPU recently into my unraid server, and I have been getting hundreds of these errors in the system log: NVRM: GPU - RmInitAdapter failed! NVRM: GPU - rm_init_adapter failed, device minor number 0 NVRM: GPU - Failed to copy vbios to system memory New GPU is a GTX 1660Ti Running Nvidia UnRaid 6.8.3 with Nvidia 440.59 drivers I was not having any of these errors with my previous GPU, and I do not have any issues with my new GPU in another two machines when I tested From what I have been able to see during troubleshooting, is the GPU keeps going online and offline, and as per the video it seems to be when the cached memory in unraid gets all used up, due to file transfers happening. Perhaps there is a tunable of some sort to prevent all the memory from getting used? I did a screen capture when it was happening, its boring AF but it does show the device going offline and online when the cached memory goes up and down. Keep an eye on the memory usage and the green available sliver at the top. There seems to be a number of other posts about this, but can't really see that its been resolved. Any help or suggestions would be appreciated
June 28, 20206 yr Hi, Is there someway of completely uninstalling this? ever since I've installed it I can't seem to get any of my GPU Passthrough VM's to work. They just crash the VM tab and I have to force stop from the dashboard page. Thanks
June 28, 20206 yr 30 minutes ago, Thompson8 said: Hi, Is there someway of completely uninstalling this? ever since I've installed it I can't seem to get any of my GPU Passthrough VM's to work. They just crash the VM tab and I have to force stop from the dashboard page. Thanks Load back up the plugin and select to install the stock OS build.
June 28, 20206 yr On 6/26/2020 at 4:40 AM, saarg said: Isn't dopu self explanatory? 😂 It should have been saying you. We can't read your mind, so you need to post the docker run command and also what you do and where the error message pops up. root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='plex' --net='host' -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e 'VERSION'='docker' -e 'NVIDIA_VISIBLE_DEVICES'='all' -e 'NVIDIA_DRIVER_CAPABILITIES'='all' -e 'TCP_PORT_32400'='32400' -e 'TCP_PORT_3005'='3005' -e 'TCP_PORT_8324'='8324' -e 'TCP_PORT_32469'='32469' -e 'UDP_PORT_1900'='1900' -e 'UDP_PORT_32410'='32410' -e 'UDP_PORT_32412'='32412' -e 'UDP_PORT_32413'='32413' -e 'UDP_PORT_32414'='32414' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/user/media/Movies/':'/movies':'rw' -v '/mnt/user/media/TV Shows/':'/tv':'rw' -v '':'/music':'rw' -v '/mnt/cache/plextrans':'/transcode':'rw' -v '/mnt/user/media/Comedy/':'/comedy/':'rw' -v '/mnt/user/appdata/plex':'/config':'rw' --runtime=nvidia 'linuxserver/plex' 97e7392d31c195872fe8f672ee5e4c187cb7ac4a63868458b9a5418f96e75cdb The command finished successfully! 😞 Edited June 28, 20206 yr by waymon
June 28, 20206 yr 8 minutes ago, waymon said: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='plex' --net='host' -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e 'VERSION'='docker' -e 'NVIDIA_VISIBLE_DEVICES'='all' -e 'NVIDIA_DRIVER_CAPABILITIES'='all' -e 'TCP_PORT_32400'='32400' -e 'TCP_PORT_3005'='3005' -e 'TCP_PORT_8324'='8324' -e 'TCP_PORT_32469'='32469' -e 'UDP_PORT_1900'='1900' -e 'UDP_PORT_32410'='32410' -e 'UDP_PORT_32412'='32412' -e 'UDP_PORT_32413'='32413' -e 'UDP_PORT_32414'='32414' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/user/media/Movies/':'/movies':'rw' -v '/mnt/user/media/TV Shows/':'/tv':'rw' -v '':'/music':'rw' -v '/mnt/cache/plextrans':'/transcode':'rw' -v '/mnt/user/media/Comedy/':'/comedy/':'rw' -v '/mnt/user/appdata/plex':'/config':'rw' --runtime=nvidia 'linuxserver/plex' 97e7392d31c195872fe8f672ee5e4c187cb7ac4a63868458b9a5418f96e75cdb The command finished successfully! 😞 You have the variable NVIDIA_VISIBLE_DEVICES set incorrectly. It should be the GPU UUID and NOT set to all read #3 in the How to Utilise the GPU in LinuxServer.io Emby, Jellyfin or Plex Docker Containers section of the following post
June 28, 20206 yr Also in plex settings make sure Use hardware acceleration when available is checked
June 28, 20206 yr Thanks guys ❤️ Using the official Repo + double checking all the steps and finally adding this NVIDIA_DRIVER_CAPABILITIES. Did the trick. Again, thanks for holding my hand. Edited June 28, 20206 yr by waymon
June 29, 20206 yr Not sure if this has been requested already, but could the driver version be updated to 450.36.06? There is a bug with Plex where the GPU stays in power state P0 after transcoded streams are terminated and this is supposed to be fixed in the new Nvidia driver. https://forums.plex.tv/t/stuck-in-p-state-p0-after-transcode-finished-on-nvidia/387685/101
June 29, 20206 yr 1 hour ago, DavidSpek said: Not sure if this has been requested already, but could the driver version be updated to 450.36.06? There is a bug with Plex where the GPU stays in power state P0 after transcoded streams are terminated and this is supposed to be fixed in the new Nvidia driver. https://forums.plex.tv/t/stuck-in-p-state-p0-after-transcode-finished-on-nvidia/387685/101 440.100 is the latest driver for linux. Current unraid, 6.8.3, is using 440.59 and the driver version will not be bumped until next build. The 6.9.0 beta release might have 440.100. We use the slackbuild drivers, so even though nvidia release a driver, it might not be the latest one for slackware.
June 29, 20206 yr 10 minutes ago, saarg said: 440.100 is the latest driver for linux. Current unraid, 6.8.3, is using 440.59 and the driver version will not be bumped until next build. The 6.9.0 beta release might have 440.100. We use the slackbuild drivers, so even though nvidia release a driver, it might not be the latest one for slackware. Given the power management fixes in the new 450.36.06 driver (and assuming also newer ones once they are released), would it be possible to add this driver once it is available through SlackBuild? I know the usual procedure it to have one release for each unraid build unless there is a critical bug, but given the fact that many use their GPU's for Plex transcoding and power usage in P8 is ~30% of the power usage in P0 wit a P2000 I think it is debatable if this should be considered critical. Reading through the thread I linked earlier the issue with Plex and power management was actually something Nvidia needed to fix in their driver and was not caused by an issue in Plex (even though Emby and Jellyfin don't seem to have this issue), which also supports the notion that this is a bug in the driver.
July 1, 20206 yr GTX 1060 not working for 4K HEVC My GeForce GTX 1060 3GB installed fine with these instructions. NVidia driver 440.59, unRAID 6.8.3 Most everything works. But I cannot transcode an HEVC 4K video. It just hangs. I confirmed that the video is H.265 (HEVC) 4:2:0, so it should work according to https://developer.nvidia.com/video-encode-decode-gpu-support-matrix My questions. 1. Is there a fix? 2. If not, how can I prevent it from using hardware transcoding for HEVC 4K videos (and only those)? Thanks.
July 1, 20206 yr 1 hour ago, Pducharme said: I have a GTX 1060 6GB and it seems to work... strange yours doesn't. Very strange. I just upgraded to 6.9.0-beta22 with the upgraded NVidia drivers, and it still doesn't work. I hope I can troubleshoot it.
July 1, 20206 yr On 5/19/2020 at 12:58 PM, saarg said: Nvidia doesn't support it in Linux since 2016. according to there driver comparability it shows the m2000
July 1, 20206 yr 4 hours ago, cjjermont said: according to there driver comparability it shows the m2000 No idea how I came to that conclusion then. Post a screenhot of the Nvidia plugin page and the output of lspci -k Edited July 1, 20206 yr by saarg
July 1, 20206 yr 2 hours ago, saarg said: No idea how I came to that conclusion then. Post a screenhot of the Nvidia plugin page and the output of lspci -k i get two different warnings.. if i put it in vfio i get a different warning..last is just for system stats so you know
July 1, 20206 yr 7 minutes ago, cjjermont said: i get two different warnings.. if i put it in vfio i get a different warning..last is just for system stats so you know other warning Edited July 1, 20206 yr by cjjermont
July 1, 20206 yr I tried installing this yesterday and after the reboot, my OS does not start all the way. I am unable able to log in with ssh, but not through the GUI. I see these logs in syslog and if I reboot per the message it is the same. It does start all the way in safe mode. Jun 30 20:13:20 Tower root: plugin: installing: /boot/config/plugins/Unraid-Nvidia.plg Jun 30 20:13:20 Tower root: plugin: running: anonymous Jun 30 20:13:20 Tower root: Jun 30 20:13:20 Tower root: Jun 30 20:13:20 Tower root: Jun 30 20:13:20 Tower root: Jun 30 20:13:20 Tower root: plugin: running: anonymous Jun 30 20:13:20 Tower root: plugin: skipping: /boot/config/plugins/Unraid-Nvidia/Unraid-Nvidia-2019.06.23.txz already exists Jun 30 20:13:20 Tower root: plugin: running: /boot/config/plugins/Unraid-Nvidia/Unraid-Nvidia-2019.06.23.txz Jun 30 20:13:20 Tower root: Jun 30 20:13:20 Tower root: +============================================================================== Jun 30 20:13:20 Tower root: | Installing new package /boot/config/plugins/Unraid-Nvidia/Unraid-Nvidia-2019.06.23.txz Jun 30 20:13:20 Tower root: +============================================================================== Jun 30 20:13:20 Tower root: Jun 30 20:13:20 Tower root: Verifying package Unraid-Nvidia-2019.06.23.txz. Jun 30 20:13:20 Tower root: Installing package Unraid-Nvidia-2019.06.23.txz: Jun 30 20:13:20 Tower root: PACKAGE DESCRIPTION: Jun 30 20:13:20 Tower root: Package Unraid-Nvidia-2019.06.23.txz installed. Jun 30 20:13:20 Tower root: plugin: running: anonymous Jun 30 20:13:21 Tower kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000 Jun 30 20:13:21 Tower kernel: #PF: supervisor write access in kernel mode Jun 30 20:13:21 Tower kernel: #PF: error_code(0x0002) - not-present page Jun 30 20:13:21 Tower kernel: PGD 80000013f5291067 P4D 80000013f5291067 PUD 1426ff2067 PMD 0 Jun 30 20:13:21 Tower kernel: Oops: 0002 [#1] SMP PTI Jun 30 20:13:21 Tower kernel: CPU: 20 PID: 5398 Comm: nvidia-smi Tainted: P O 5.7.2-Unraid #1 Jun 30 20:13:21 Tower kernel: Hardware name: Cisco Systems Inc UCSC-C220-M4S/UCSC-C220-M4S, BIOS C220M4.3.0.4g.0.1113190807 11/13/2019 Jun 30 20:13:21 Tower kernel: RIP: 0010:_nv025250rm+0x8/0x40 [nvidia] Jun 30 20:13:21 Tower kernel: Code: 1f 00 41 8b 4d 08 41 39 0a 4c 89 d6 0f 82 5b fe ff ff e9 69 fe ff ff 90 66 2e 0f 1f 84 00 00 00 00 00 48 83 ec 08 48 8b 42 48 <83> 00 01 c6 42 10 01 e8 5c f4 ff ff 85 c0 74 13 89 c2 be 00 10 57 Jun 30 20:13:21 Tower kernel: RSP: 0018:ffffc90020e97a28 EFLAGS: 00010296 Jun 30 20:13:21 Tower kernel: RAX: 0000000000000000 RBX: 000000000000001c RCX: ffff8893eed22e48 Jun 30 20:13:21 Tower kernel: RDX: ffff8893f6963408 RSI: ffff8893e809e008 RDI: ffff8893eed64008 Jun 30 20:13:21 Tower kernel: RBP: ffff8893eed22e40 R08: ffffffffa0a60930 R09: ffff8893eed229ec Jun 30 20:13:21 Tower kernel: R10: 0000000000001516 R11: 0000000000000000 R12: ffff8893eed64008 Jun 30 20:13:21 Tower kernel: R13: ffff8893f68d4008 R14: ffff8893eed64008 R15: ffff8893f33e0008 Jun 30 20:13:21 Tower kernel: FS: 000014bad9eb3b80(0000) GS:ffff88942fd00000(0000) knlGS:0000000000000000 Jun 30 20:13:21 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 30 20:13:21 Tower kernel: CR2: 0000000000000000 CR3: 00000013f536c001 CR4: 00000000003606e0 Jun 30 20:13:21 Tower kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Jun 30 20:13:21 Tower kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Jun 30 20:13:21 Tower kernel: Call Trace: Jun 30 20:13:21 Tower kernel: ? _nv025251rm+0x260/0x260 [nvidia] Jun 30 20:13:21 Tower kernel: ? _nv031459rm+0x7a/0xb0 [nvidia] Jun 30 20:13:21 Tower kernel: ? _nv031799rm+0x6ec/0x2440 [nvidia] Jun 30 20:13:21 Tower kernel: ? _nv021294rm+0xbb/0x1a0 [nvidia] Jun 30 20:13:21 Tower kernel: ? _nv021542rm+0x27/0x50 [nvidia] Jun 30 20:13:21 Tower kernel: ? _raw_spin_unlock_irqrestore+0xd/0xe Jun 30 20:13:21 Tower kernel: ? _nv000901rm+0x1200/0x1cc0 [nvidia] Jun 30 20:13:21 Tower kernel: ? rm_init_adapter+0xd5/0xe0 [nvidia] Jun 30 20:13:21 Tower kernel: ? nv_open_device+0x434/0x648 [nvidia] Jun 30 20:13:21 Tower kernel: ? nvidia_open+0x2a1/0x41a [nvidia] Jun 30 20:13:21 Tower kernel: ? nvidia_frontend_open+0x62/0x8d [nvidia] Jun 30 20:13:21 Tower kernel: ? chrdev_open+0x150/0x187 Jun 30 20:13:21 Tower kernel: ? cdev_put+0x19/0x19 Jun 30 20:13:21 Tower kernel: ? do_dentry_open+0x181/0x296 Jun 30 20:13:21 Tower kernel: ? path_openat+0x85a/0x933 Jun 30 20:13:21 Tower kernel: ? do_filp_open+0x4c/0xa9 Jun 30 20:13:21 Tower kernel: ? up_write+0x17/0x24 Jun 30 20:13:21 Tower kernel: ? chown_common.isra.0+0xec/0x14d Jun 30 20:13:21 Tower kernel: ? _cond_resched+0x1b/0x1e Jun 30 20:13:21 Tower kernel: ? slab_pre_alloc_hook+0x2c/0x53 Jun 30 20:13:21 Tower kernel: ? do_sys_openat2+0x6d/0xd9 Jun 30 20:13:21 Tower kernel: ? do_sys_open+0x35/0x4f Jun 30 20:13:21 Tower kernel: ? do_syscall_64+0x7a/0x87 Jun 30 20:13:21 Tower kernel: ? entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 30 20:13:21 Tower kernel: Modules linked in: iptable_nat xt_MASQUERADE nf_nat ip_tables wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 libchacha poly1305_x86_64 ip6_udp_tunnel udp_tunnel libblake2s blake2s_x86_64 libblake2s_generic bonding ixgbe mdio igb i2c_algo_bit nvidia_drm(PO) nvidia_modeset(PO) nvidia(PO) crc32_pclmul intel_rapl_perf intel_uncore aesni_intel glue_helper crypto_simd ghash_clmulni_intel cryptd kvm_intel kvm drm_kms_helper intel_cstate coretemp mxm_wmi drm crct10dif_pclmul intel_powerclamp crc32c_intel sb_edac backlight syscopyarea sysfillrect sysimgblt fb_sys_fops x86_pkg_temp_thermal agpgart ipmi_si ahci input_leds megaraid_sas libahci ipmi_ssif i2c_core led_class wmi acpi_power_meter button acpi_pad [last unloaded: mdio] Jun 30 20:13:21 Tower kernel: CR2: 0000000000000000 Jun 30 20:13:21 Tower kernel: ---[ end trace 2ead729f5369cb81 ]--- Jun 30 20:13:21 Tower kernel: RIP: 0010:_nv025250rm+0x8/0x40 [nvidia] Jun 30 20:13:21 Tower kernel: Code: 1f 00 41 8b 4d 08 41 39 0a 4c 89 d6 0f 82 5b fe ff ff e9 69 fe ff ff 90 66 2e 0f 1f 84 00 00 00 00 00 48 83 ec 08 48 8b 42 48 <83> 00 01 c6 42 10 01 e8 5c f4 ff ff 85 c0 74 13 89 c2 be 00 10 57 Jun 30 20:13:21 Tower kernel: RSP: 0018:ffffc90020e97a28 EFLAGS: 00010296 Jun 30 20:13:21 Tower kernel: RAX: 0000000000000000 RBX: 000000000000001c RCX: ffff8893eed22e48 Jun 30 20:13:21 Tower kernel: RDX: ffff8893f6963408 RSI: ffff8893e809e008 RDI: ffff8893eed64008 Jun 30 20:13:21 Tower kernel: RBP: ffff8893eed22e40 R08: ffffffffa0a60930 R09: ffff8893eed229ec Jun 30 20:13:21 Tower kernel: R10: 0000000000001516 R11: 0000000000000000 R12: ffff8893eed64008 Jun 30 20:13:21 Tower kernel: R13: ffff8893f68d4008 R14: ffff8893eed64008 R15: ffff8893f33e0008 Jun 30 20:13:21 Tower kernel: FS: 000014bad9eb3b80(0000) GS:ffff88942fd00000(0000) knlGS:0000000000000000 Jun 30 20:13:21 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 30 20:13:21 Tower kernel: CR2: 0000000000000000 CR3: 00000013f536c001 CR4: 00000000003606e0 Jun 30 20:13:21 Tower kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Jun 30 20:13:21 Tower kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Jun 30 20:13:21 Tower kernel: general protection fault, probably for non-canonical address 0x61ad8614c5ac1b00: 0000 [#2] SMP PTI Jun 30 20:13:21 Tower kernel: CPU: 20 PID: 5398 Comm: nvidia-smi Tainted: P D O 5.7.2-Unraid #1 Jun 30 20:13:21 Tower kernel: Hardware name: Cisco Systems Inc UCSC-C220-M4S/UCSC-C220-M4S, BIOS C220M4.3.0.4g.0.1113190807 11/13/2019 Jun 30 20:13:21 Tower kernel: RIP: 0010:_nv007414rm+0x2c/0x330 [nvidia] Jun 30 20:13:21 Tower kernel: Code: 48 85 d2 74 07 48 63 47 08 48 01 d0 48 8b 17 48 85 d2 75 16 e9 9d 02 00 00 0f 1f 44 00 00 48 8b 4a 10 48 85 c9 74 17 48 89 ca <48> 39 32 77 ef 0f 83 29 02 00 00 48 8b 4a 18 48 85 c9 75 e9 48 89 Jun 30 20:13:21 Tower kernel: RSP: 0018:ffffc90020e97d40 EFLAGS: 00010006 Jun 30 20:13:21 Tower kernel: RAX: ffffc90020e97dc8 RBX: ffffc90020e97d70 RCX: 61ad8614c5ac1b00 Jun 30 20:13:21 Tower kernel: RDX: 61ad8614c5ac1b00 RSI: 0000000000001516 RDI: ffffffffa177a3d8 Jun 30 20:13:21 Tower kernel: RBP: ffff8893f2c22ff0 R08: 0000000000000001 R09: ffffffffa0588903 Jun 30 20:13:21 Tower kernel: R10: ffff889428430a00 R11: ffff889428430a00 R12: 675f65736e6f7073 Jun 30 20:13:21 Tower kernel: R13: ffff889428433000 R14: ffffffffa1778c20 R15: ffff889428433000 Jun 30 20:13:21 Tower kernel: FS: 0000000000000000(0000) GS:ffff88942fd00000(0000) knlGS:0000000000000000 Jun 30 20:13:21 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 30 20:13:21 Tower kernel: CR2: 0000000000000000 CR3: 000000000200a002 CR4: 00000000003606e0 Jun 30 20:13:21 Tower kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Jun 30 20:13:21 Tower kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Jun 30 20:13:21 Tower kernel: Call Trace: Jun 30 20:13:21 Tower kernel: ? _nv036791rm+0xf1/0x1d0 [nvidia] Jun 30 20:13:21 Tower kernel: ? rm_free_unused_clients+0x41/0xe0 [nvidia] Jun 30 20:13:21 Tower kernel: ? _raw_spin_lock_irqsave+0x3a/0x66 Jun 30 20:13:21 Tower kernel: ? nvidia_close+0xf3/0x25b [nvidia] Jun 30 20:13:21 Tower kernel: ? nvidia_frontend_close+0x2c/0x3e [nvidia] Jun 30 20:13:21 Tower kernel: ? __fput+0x107/0x1d0 Jun 30 20:13:21 Tower kernel: ? task_work_run+0x70/0x81 Jun 30 20:13:21 Tower kernel: ? do_exit+0x3f8/0x8f3 Jun 30 20:13:21 Tower kernel: ? rewind_stack_do_exit+0x17/0x20 Jun 30 20:13:21 Tower kernel: Modules linked in: iptable_nat xt_MASQUERADE nf_nat ip_tables wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 libchacha poly1305_x86_64 ip6_udp_tunnel udp_tunnel libblake2s blake2s_x86_64 libblake2s_generic bonding ixgbe mdio igb i2c_algo_bit nvidia_drm(PO) nvidia_modeset(PO) nvidia(PO) crc32_pclmul intel_rapl_perf intel_uncore aesni_intel glue_helper crypto_simd ghash_clmulni_intel cryptd kvm_intel kvm drm_kms_helper intel_cstate coretemp mxm_wmi drm crct10dif_pclmul intel_powerclamp crc32c_intel sb_edac backlight syscopyarea sysfillrect sysimgblt fb_sys_fops x86_pkg_temp_thermal agpgart ipmi_si ahci input_leds megaraid_sas libahci ipmi_ssif i2c_core led_class wmi acpi_power_meter button acpi_pad [last unloaded: mdio] Jun 30 20:13:21 Tower kernel: ---[ end trace 2ead729f5369cb82 ]--- Jun 30 20:13:21 Tower kernel: RIP: 0010:_nv025250rm+0x8/0x40 [nvidia] Jun 30 20:13:21 Tower kernel: Code: 1f 00 41 8b 4d 08 41 39 0a 4c 89 d6 0f 82 5b fe ff ff e9 69 fe ff ff 90 66 2e 0f 1f 84 00 00 00 00 00 48 83 ec 08 48 8b 42 48 <83> 00 01 c6 42 10 01 e8 5c f4 ff ff 85 c0 74 13 89 c2 be 00 10 57 Jun 30 20:13:21 Tower kernel: RSP: 0018:ffffc90020e97a28 EFLAGS: 00010296 Jun 30 20:13:21 Tower kernel: RAX: 0000000000000000 RBX: 000000000000001c RCX: ffff8893eed22e48 Jun 30 20:13:21 Tower kernel: RDX: ffff8893f6963408 RSI: ffff8893e809e008 RDI: ffff8893eed64008 Jun 30 20:13:21 Tower kernel: RBP: ffff8893eed22e40 R08: ffffffffa0a60930 R09: ffff8893eed229ec Jun 30 20:13:21 Tower kernel: R10: 0000000000001516 R11: 0000000000000000 R12: ffff8893eed64008 Jun 30 20:13:21 Tower kernel: R13: ffff8893f68d4008 R14: ffff8893eed64008 R15: ffff8893f33e0008 Jun 30 20:13:21 Tower kernel: FS: 0000000000000000(0000) GS:ffff88942fd00000(0000) knlGS:0000000000000000 Jun 30 20:13:21 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 30 20:13:21 Tower kernel: CR2: 0000000000000000 CR3: 000000000200a002 CR4: 00000000003606e0 Jun 30 20:13:21 Tower kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Jun 30 20:13:21 Tower kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Jun 30 20:13:21 Tower kernel: Fixing recursive fault but reboot is needed! Jun 30 20:13:42 Tower rsyslogd: action 'action-3-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.2002.0 try https://www.rsyslog.com/e/2359 ] root@Tower:~# lspci -v | grep VGA 07:00.0 VGA compatible controller: NVIDIA Corporation GK106GL [Quadro K4000] (rev a1) (prog-if 00 [VGA controller]) Wondering if anyone has any suggestions on where to start looking for an answer? I have tried my best google-fu and failed before posting here. Edited July 1, 20206 yr by jwiener3
July 1, 20206 yr 11 minutes ago, jwiener3 said: unable to log in with ssh, but not through the GUI. Unable for one way BUT not for the other way. I suspect you meant one of these was working since you said BUT. Did you mean to say you are able to use ssh?
Archived
This topic is now archived and is closed to further replies.