Jump to content

On VM start server partially crashes


Recommended Posts

See logs below. 

When starting a Windows 10 VM with dedicated GPU (Nvidia 1050ti) the system seems to partly crash. It still works, but the VM’s tab won’t open. I have another GPU passed though for other server duties. After a restart it seems to all work again, but this is the second time it has happened so there is obviously something not quite right.

 

Anyone any ideas? 

 

Jul 1 19:56:22 Tower kernel: NVRM: Attempting to remove minor device 1 with non-zero usage count!
Jul 1 19:56:22 Tower kernel: ------------[ cut here ]------------
Jul 1 19:56:22 Tower kernel: WARNING: CPU: 13 PID: 6559 at /tmp/SBo/NVIDIA-Linux-x86_64-440.59/kernel/nvidia/nv-pci.c:577 nv_pci_remove+0xe9/0x2fc [nvidia]
Jul 1 19:56:22 Tower kernel: Modules linked in: sr_mod cdrom nvidia_uvm(O) xt_CHECKSUM ipt_REJECT ip6table_mangle ip6table_nat nf_nat_ipv6 iptable_mangle ip6table_filter ip6_tables xt_nat vhost_net tun vhost tap veth iptable_filter xfs md_mod i915 video backlight iosf_mbi intel_gtt i2c_algo_bit iptable_nat ipt_MASQUERADE nf_nat_ipv4 nf_nat ip_tables wireguard ip6_udp_tunnel udp_tunnel bonding nvidia_drm(PO) nvidia_modeset(PO) nvidia(PO) drm_kms_helper edac_mce_amd crc32_pclmul pcbc aesni_intel aes_x86_64 glue_helper crypto_simd ghash_clmulni_intel cryptd drm kvm_amd kvm r8169 syscopyarea sysfillrect sysimgblt fb_sys_fops realtek agpgart i2c_piix4 i2c_core wmi_bmof ahci ccp libahci crct10dif_pclmul crc32c_intel pcc_cpufreq wmi button acpi_cpufreq
Jul 1 19:56:22 Tower kernel: CPU: 13 PID: 6559 Comm: libvirtd Tainted: P O 4.19.107-Unraid #1
Jul 1 19:56:22 Tower kernel: Hardware name: Gigabyte Technology Co., Ltd. B450 AORUS M/B450 AORUS M, BIOS F50 11/27/2019
Jul 1 19:56:22 Tower kernel: RIP: 0010:nv_pci_remove+0xe9/0x2fc [nvidia]
Jul 1 19:56:22 Tower kernel: Code: aa 01 00 00 00 75 2c 8b 95 70 04 00 00 48 c7 c6 7b 35 98 a1 bf 04 00 00 00 e8 bd 7d 00 00 48 c7 c7 c2 35 98 a1 e8 31 a6 83 e0 <0f> 0b e8 c2 82 00 00 eb f9 4c 8d b5 50 04 00 00 4c 89 f7 e8 f7 42
Jul 1 19:56:22 Tower kernel: RSP: 0018:ffffc9000982bd50 EFLAGS: 00010246
Jul 1 19:56:22 Tower kernel: RAX: 0000000000000024 RBX: ffff888819a750a8 RCX: 0000000000000007
Jul 1 19:56:22 Tower kernel: RDX: 0000000000000000 RSI: 0000000000000002 RDI: ffff88881e9564f0
Jul 1 19:56:22 Tower kernel: RBP: ffff8888163a7000 R08: 0000000000000003 R09: 000000000001d500
Jul 1 19:56:22 Tower kernel: R10: 0000000000000000 R11: 0000000000000044 R12: ffff8882543c3008
Jul 1 19:56:22 Tower kernel: R13: ffff888819a75000 R14: 0000000000000060 R15: ffff888721433cc0
Jul 1 19:56:22 Tower kernel: FS: 00001517828e4700(0000) GS:ffff88881e940000(0000) knlGS:0000000000000000
Jul 1 19:56:22 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 1 19:56:22 Tower kernel: CR2: 00001517828e0378 CR3: 00000007c3fe6000 CR4: 0000000000340ee0
Jul 1 19:56:22 Tower kernel: Call Trace:
Jul 1 19:56:22 Tower kernel: pci_device_remove+0x36/0x8e
Jul 1 19:56:22 Tower kernel: device_release_driver_internal+0x144/0x225
Jul 1 19:56:22 Tower kernel: unbind_store+0x6b/0xae
Jul 1 19:56:22 Tower kernel: kernfs_fop_write+0xf3/0x135
Jul 1 19:56:22 Tower kernel: __vfs_write+0x32/0x13a
Jul 1 19:56:22 Tower kernel: vfs_write+0xc7/0x166
Jul 1 19:56:22 Tower kernel: ksys_write+0x60/0xb2
Jul 1 19:56:22 Tower kernel: do_syscall_64+0x57/0xf2
Jul 1 19:56:22 Tower kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Jul 1 19:56:22 Tower kernel: RIP: 0033:0x15178438348f
Jul 1 19:56:22 Tower kernel: Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 49 fd ff ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2d 44 89 c7 48 89 44 24 08 e8 7c fd ff ff 48
Jul 1 19:56:22 Tower kernel: RSP: 002b:00001517828e3530 EFLAGS: 00000293 ORIG_RAX: 0000000000000001
Jul 1 19:56:22 Tower kernel: RAX: ffffffffffffffda RBX: 000000000000000c RCX: 000015178438348f
Jul 1 19:56:22 Tower kernel: RDX: 000000000000000c RSI: 000015177c05f7e0 RDI: 000000000000001e
Jul 1 19:56:22 Tower kernel: RBP: 000015177c05f7e0 R08: 0000000000000000 R09: 0000000000000000
Jul 1 19:56:22 Tower kernel: R10: 0000000000000000 R11: 0000000000000293 R12: 000000000000001e
Jul 1 19:56:22 Tower kernel: R13: 000000000000001e R14: 0000000000000000 R15: 000015177c05ee70
Jul 1 19:56:22 Tower kernel: ---[ end trace e1e51175159f6869 ]---
Jul 1 20:01:20 Tower nginx: 2020/07/01 20:01:20 [error] 7772#7772: *165929 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.100.25, server: , request: "POST /webGui/include/DashboardApps.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.100.100", referrer: "http://192.168.100.100/Dashboard"
Jul 1 20:02:35 Tower webGUI: Successful login user root from 192.168.100.25

 

Link to comment

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...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...