February 7, 20179 yr Community Expert "Call Traces found on your server" from Fix Common Errors plugin after upgrade to 6.3.0 (from relatively new 6.2.4 install), but extended test finds no faults. Nothing to worry about or are there deeper tests to conduct? edit: syslog shows Feb 7 20:15:52 fortytwo emhttp: error: changeSlots: missing csrf_token Initially though this may be related to unassigned devices, but best leave it to the pros here Diagnostics attached fortytwo-diagnostics-20170207-2026.zip
February 7, 20179 yr Feb 7 20:14:40 fortytwo kernel: WARNING: CPU: 8 PID: 1 at drivers/iommu/intel-iommu.c:5476 intel_iommu_init+0xd8e/0x10fd Feb 7 20:14:40 fortytwo kernel: Your BIOS is broken; DMA routed to ISOCH DMAR unit but no TLB space. Feb 7 20:14:40 fortytwo kernel: BIOS vendor: American Megatrends Inc.; Ver: 1003 ; Product Version: System Version Feb 7 20:14:40 fortytwo kernel: Modules linked in: Feb 7 20:14:40 fortytwo kernel: CPU: 8 PID: 1 Comm: swapper/0 Tainted: G I 4.9.7-unRAID #1 Feb 7 20:14:40 fortytwo kernel: Hardware name: System manufacturer System Product Name/Rampage III GENE, BIOS 1003 09/20/2011 You might look for a newer BIOS or try disabling IOMMU if you're not using it. The csrf_token is a new security measure introduced in 6.3.0 and discussed in the release thread. Make sure all plugins are up to date.
February 7, 20179 yr Author Community Expert Thanks. Everything is up to date, BIOS is also latest available. Was aware of a potential issue with DMAR tables (common with asus x58), but hadn't tried any VMs with pass through to confirm, only dockers so far. I'll go trawl through that thread to find the fix, if any.
Archived
This topic is now archived and is closed to further replies.