February 21, 20179 yr Hi, Could I get assistance in deciphering the following Call Trace? Also what are some resources to help figure out future errors because google search was not the most helpful? Below is the Call Trace and attached is my system log. Thanks! Feb 20 18:10:45 Hiveserver kernel: CPU: 0 PID: 0 Comm: swapper Not tainted 4.9.10-unRAID #1 Feb 20 18:10:45 Hiveserver kernel: Hardware name: System manufacturer System Product Name/P7H55-M LE, BIOS 0801 09/07/2012 Feb 20 18:10:45 Hiveserver kernel: ffffffff81c03d60 ffffffff813a353e ffffffff81c03db0 ffffffff81988e30 Feb 20 18:10:45 Hiveserver kernel: ffffffff81c03da0 ffffffff8104d00c 0000034c81c03e18 ffffffff81e2801c Feb 20 18:10:45 Hiveserver kernel: ffffffff81e28058 0000000000000000 0000000000000000 0000000000014140 Feb 20 18:10:45 Hiveserver kernel: Call Trace: Feb 20 18:10:45 Hiveserver kernel: [] dump_stack+0x61/0x7e Feb 20 18:10:45 Hiveserver kernel: [] __warn+0xb8/0xd3 Feb 20 18:10:45 Hiveserver kernel: [] warn_slowpath_fmt_taint+0x3f/0x47 Feb 20 18:10:45 Hiveserver kernel: [] ? __early_ioremap+0x13e/0x1b7 Feb 20 18:10:45 Hiveserver kernel: [] warn_invalid_dmar+0x70/0x7d Feb 20 18:10:45 Hiveserver kernel: [] dmar_validate_one_drhd+0x8e/0xa0 Feb 20 18:10:45 Hiveserver kernel: [] dmar_walk_remapping_entries+0xe6/0x113 Feb 20 18:10:45 Hiveserver kernel: [] detect_intel_iommu+0x54/0xd1 Feb 20 18:10:45 Hiveserver kernel: [] ? xen_swiotlb_init+0x3ab/0x3ab Feb 20 18:10:45 Hiveserver kernel: [] pci_iommu_alloc+0x50/0x6c Feb 20 18:10:45 Hiveserver kernel: [] mem_init+0x17/0x9d Feb 20 18:10:45 Hiveserver kernel: [] start_kernel+0x1d9/0x3dc Feb 20 18:10:45 Hiveserver kernel: [] ? early_idt_handler_array+0x120/0x120 Feb 20 18:10:45 Hiveserver kernel: [] x86_64_start_reservations+0x2a/0x2c Feb 20 18:10:45 Hiveserver kernel: [] x86_64_start_kernel+0xe6/0xf3 Feb 20 18:10:45 Hiveserver kernel: ---[ end trace 0000000000000000 ]--- Febhttp://cloud.tapatalk.com/s/58abd4fa9a286/hiveserver-syslog-20170220-1911.ziphttp://cloud.tapatalk.com/s/58abd56172957/syslog.txt
February 21, 20179 yr Post your full diagnostics zip. Tools -> Diagnostics. The syslog snippet you pasted into your post is unreadable.
February 21, 20179 yr Author 5 hours ago, John_M said: Post your full diagnostics zip. Tools -> Diagnostics. The syslog snippet you pasted into your post is unreadable. Sorry about that. Here you go. hiveserver-diagnostics-20170221-1022.zip Edited February 21, 20179 yr by khronos247
February 21, 20179 yr Author HTTP Error 503 on that tapatalk link.Just uploaded it directly to the forum. Thanks! Sent from my Nexus 6P using Tapatalk
February 21, 20179 yr From right at the very beginning of your syslog: Quote Feb 21 10:20:04 Hiveserver kernel: Your BIOS is broken; DMAR reported at address fed91000 returns all ones! Feb 21 10:20:04 Hiveserver kernel: BIOS vendor: American Megatrends Inc.; Ver: 0801 ; Product Version: System Version Since it dates from 2012, I'd look for a newer version.
February 21, 20179 yr Author Unfortunately 2012 is the most recent revision. Should I get a new board?
February 21, 20179 yr I try turning off any virtualization options in the BIOS first. I see your Westmere Core i3 has VTx but not VTd. It looks as though you're not going to be able to run any VMs so you might want to consider a hardware upgrade.
February 24, 20179 yr Author I try turning off any virtualization options in the BIOS first. I see your Westmere Core i3 has VTx but not VTd. It looks as though you're not going to be able to run any VMs so you might want to consider a hardware upgrade.Disabling virtualization VTd resolved the issue. Thanks! Sent from my Nexus 6P using Tapatalk
February 24, 20179 yr Good. You were able to fix the problem without having to lose anything just by switching off a feature that wasn't supported anyway. Useful to know.
Archived
This topic is now archived and is closed to further replies.