obideuce Posted April 19, 2017 Share Posted April 19, 2017 Fix common problems shows call traces. Diagnostics attached. Any advice is appreciated. unraid-diagnostics-20170418-2100.zip Quote Link to comment
Squid Posted April 19, 2017 Share Posted April 19, 2017 Apr 7 20:03:33 unraid kernel: WARNING: CPU: 0 PID: 1 at drivers/iommu/intel-iommu.c:5477 intel_iommu_init+0xb99/0x1107 Apr 7 20:03:33 unraid kernel: Your BIOS is broken; DMA routed to ISOCH DMAR unit but no TLB space. . . . Apr 7 20:03:33 unraid kernel: WARNING: CPU: 0 PID: 1 at drivers/iommu/intel-iommu.c:2653 domain_prepare_identity_map+0xb9/0x15a Apr 7 20:03:33 unraid kernel: Your BIOS is broken; RMRR ends before it starts! I'm not the real expert here, but the traces all all about RMRR (whatever that is) and IOMMU, and a broken BIOS. - If utilizing hardware passthrough, check for a BIOS update - If not utilizing hardware passthrough, disable IOMMU in the BIOS Quote Link to comment
obideuce Posted April 19, 2017 Author Share Posted April 19, 2017 (edited) There aren't any BIOS updates. Does disabling IOMMU (VT-d) have any impact on Docker applications, or is it purely for redirected hardware on VMs? Edited April 19, 2017 by obideuce Quote Link to comment
JonathanM Posted April 19, 2017 Share Posted April 19, 2017 10 minutes ago, obideuce said: Does disabling IOMMU (VT-d) have any impact on Docker applications, or is it purely for redirected hardware on VMs? Just hardware passthrough. 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.