Ken R. Posted September 3, 2017 Share Posted September 3, 2017 Sep 3 10:11:20 kingsnake kernel: Call Trace: Sep 3 10:11:20 kingsnake kernel: ? free_reserved_area+0xe5/0xf5 Sep 3 10:11:20 kingsnake kernel: ? set_debug_rodata+0x12/0x12 Sep 3 10:11:20 kingsnake kernel: pci_iommu_init+0x12/0x3c Sep 3 10:11:20 kingsnake kernel: ? load_default_modules+0x9/0xb Sep 3 10:11:20 kingsnake kernel: ? pci_iommu_init+0x12/0x3c Sep 3 10:11:20 kingsnake kernel: ? e820__memblock_setup+0x5f/0x5f Sep 3 10:11:20 kingsnake kernel: do_one_initcall+0x8b/0x127 Sep 3 10:11:20 kingsnake kernel: kernel_init_freeable+0x182/0x20b Sep 3 10:11:20 kingsnake kernel: ? rest_init+0x82/0x82 Sep 3 10:11:20 kingsnake kernel: kernel_init+0x9/0xf0 Sep 3 10:11:20 kingsnake kernel: ret_from_fork+0x25/0x30 Sep 3 10:11:20 kingsnake kernel: Code: 00 49 89 c4 e8 1b 34 b5 ff bf 01 00 00 00 48 89 c3 e8 0e 34 b5 ff 4c 89 e1 48 89 da 48 c7 c7 d2 cb 74 81 48 89 c6 e8 5c c0 7b ff <0f> ff 83 0d de ee 11 00 04 eb 0c 48 c7 c7 46 cc 74 81 e8 45 c0 Sep 3 10:11:20 kingsnake kernel: ---[ end trace 52606231966f7598 ]--- Anybody understand this? I have not been able to get pass through working (sound or video) in a VM - is this call trace related? Thanks Quote Link to comment
Squid Posted September 3, 2017 Share Posted September 3, 2017 Snippets are very rarely useful (especially since your's didn't include the header). Post the diagnostics instead. Quote Link to comment
Ken R. Posted September 3, 2017 Author Share Posted September 3, 2017 Attached. There are quite a few Call Traces in there all of a sudden. kingsnake-diagnostics-20170903-1129.zip Quote Link to comment
Squid Posted September 3, 2017 Share Posted September 3, 2017 Sep 3 10:51:23 kingsnake kernel: Your BIOS is broken; RMRR ends before it starts! Sep 3 10:51:23 kingsnake kernel: BIOS vendor: American Megatrends Inc.; Ver: 1501 ; Product Version: System Version Sep 3 10:51:23 kingsnake kernel: ------------[ cut here ]------------ Sep 3 10:51:23 kingsnake kernel: WARNING: CPU: 6 PID: 1 at drivers/iommu/intel-iommu.c:2662 domain_prepare_identity_map+0xa7/0x13e Look for BIOS updates. Since they're all apparently IOMMU related, and you're not running any VM's with passthrough, you can safely disable IOMMU / VT-D within your BIOS. 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.