UNRAID 6.4.0 Call Trace Issues, I need some help.

[Scott St. Jean]

New to Unraid.  Setup server yesterday, upgraded to 6.4.0 a few hours ago after parity drive finished.  'Fix Common Problems' plug in notified me that I had call trace details in the system log.  Bit rusty, need some help interpreting before I start copying over to the Array.  Have attached the diagnostics package as well.  Other then create some empty shares and install some plug-ins, I haven't done anything else yet.

 

Jan 13 19:48:00 Tower kernel: Call Trace:
Jan 13 19:48:00 Tower kernel: dmar_validate_one_drhd+0x89/0x99
Jan 13 19:48:00 Tower kernel: dmar_walk_remapping_entries+0xd6/0x109
Jan 13 19:48:00 Tower kernel: detect_intel_iommu+0x51/0xc5
Jan 13 19:48:00 Tower kernel: ? xen_swiotlb_init+0x3d3/0x3d3
Jan 13 19:48:00 Tower kernel: pci_iommu_alloc+0x4c/0x67
Jan 13 19:48:00 Tower kernel: mem_init+0x11/0x93
Jan 13 19:48:00 Tower kernel: start_kernel+0x1ed/0x3e9
Jan 13 19:48:00 Tower kernel: secondary_startup_64+0xa5/0xb0
Jan 13 19:48:00 Tower kernel: Code: 01 00 00 00 48 89 04 24 e8 51 46 0d 00 4c 8b 4c 24 08 48 89 ea 48 89 de 4c 8b 04 24 48 89 c1 48 c7 c7 80 1d b6 81 e8 3b b3 cd ff <0f> ff 48 83 c4 10 5b 5d c3 c3 41 57 b8 01 00 00 00 49 89 ff 41 
Jan 13 19:48:00 Tower kernel: ---[ end trace dd4750b0e88f4d3b ]---

tower-diagnostics-20180113-2019.zip

[Squid]

Try looking for a BIOS update

Jan 13 19:48:00 Tower kernel: Your BIOS is broken; DMAR reported at address 0!

But if you don't see any adverse affects, ignore it.