search for: x8dt3

...ion cards installed except for the dual-port gigabit > NICs. We're using the onboard SATA controller for only the local Dom0 > OS, and iSCSI and NFS for managing storage for VMs and images. > We've got some other motherboards as well, I think this list is exhaustive: Supermicro X8DT3 Supermicro X8DT6 Supermicro X9DRD-iF/LF Supermicro X9DRT Supermicro X9SCL/X9SCM These are -F variants which means they include a BMC chip with a separate NIC. A few of the X8DT3 are the LN4 variant, which has 4 onboard NICs and therefore we did not use an expansion NIC. -- Kevin Stange Chief Te...

...<http://wiki.xensource.com/xenwiki/VTdHowTo>page, I am a little puzzled with the fact that only Intel Core2Duo (with VT-x), Core2Quad, i7 and Core i5 (vPro Brand) CPU''s are supported while motherboards with the i55x0 chipset are supported (for example the Supermicro server mainboard: X8DT3-F<http://www.supermicro.com/products/motherboard/QPI/5500/X8DT3-F.cfm> ). The irony in all this it that above this list of supported CPU''s and motherboards is the statement "Note that in addition to the motherboard chipset and BIOS also your CPU must have support for IOMMU IO v...

On 03/16/2017 04:22 PM, Kevin Stange wrote: >> I still can't rest assured the NIC issue is fixed, but no 4.4 or 4.9 >> server has yet had a NIC issue, with some being up almost a full month. >> It looks promising! (I'm knocking on all the wood everywhere, though.) > > I'm ready to call this conclusive. The problems I was having across the > board seemed to

...ues are unrecoverable and require a hard boot to resolve. All have Intel NICs. Often the systems will remain stable for days or weeks, then suddenly encounter one of these issues. I have yet to tie the error to any specific action on the systems and can't reproduce it reliably. - Supermicro X8DT3, Dual Xeon E5620, 2x 82575EB NICs, 2x 82576 NICs Kernel messages upon failure: pcieport 0000:00:03.0: AER: Multiple Corrected error received: id=0018 pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, type=Transaction Layer, id=0018(Receiver ID) pcieport 0000:00:03.0: device [8086:340a]...

...o work. I know that they installed the last BIOS version. I have other identical servers that works well with KVM. I tried to disable all i saw for virtualization support in BIOS, result is the same. I did memtest86 tests without problem. Here are the specs: Supermicro 6026T-3RF (mainboard X8DT3-S) BIOS 03/17/12 15:50:21 Ver 2.1 Xeon E5520 Kingston 12 Gig RAM (Triple Channel) LSI 9240-8i What should i do to debug this? Any pointers, URL, etc would be greatly appreciated! Thanks all. Guy Boisvert, ing. IngTegration inc. http://www.ingtegration.com

...ues are unrecoverable and require a hard boot to resolve. All have Intel NICs. Often the systems will remain stable for days or weeks, then suddenly encounter one of these issues. I have yet to tie the error to any specific action on the systems and can't reproduce it reliably. - Supermicro X8DT3, Dual Xeon E5620, 2x 82575EB NICs, 2x 82576 NICs Kernel messages upon failure: pcieport 0000:00:03.0: AER: Multiple Corrected error received: id=0018 pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, type=Transaction Layer, id=0018(Receiver ID) pcieport 0000:00:03.0: device [8086:340a]...

...> hard boot to resolve. All have Intel NICs. > > Often the systems will remain stable for days or weeks, then suddenly > encounter one of these issues. I have yet to tie the error to any > specific action on the systems and can't reproduce it reliably. > > - Supermicro X8DT3, Dual Xeon E5620, 2x 82575EB NICs, 2x 82576 NICs > > Kernel messages upon failure: > > pcieport 0000:00:03.0: AER: Multiple Corrected error received: id=0018 > pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, > type=Transaction Layer, id=0018(Receiver ID) > pcieport...

...olve. All have Intel NICs. >> >> Often the systems will remain stable for days or weeks, then suddenly >> encounter one of these issues. I have yet to tie the error to any >> specific action on the systems and can't reproduce it reliably. >> >> - Supermicro X8DT3, Dual Xeon E5620, 2x 82575EB NICs, 2x 82576 NICs >> >> Kernel messages upon failure: >> >> pcieport 0000:00:03.0: AER: Multiple Corrected error received: id=0018 >> pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, >> type=Transaction Layer, id=0018(Rece...

...hard boot > to resolve. All have Intel NICs. > > Often the systems will remain stable for days or weeks, then suddenly > encounter one of these issues. I have yet to tie the error to any specific > action on the systems and can't reproduce it reliably. > > - Supermicro X8DT3, Dual Xeon E5620, 2x 82575EB NICs, 2x 82576 NICs > > Kernel messages upon failure: > > pcieport 0000:00:03.0: AER: Multiple Corrected error received: id=0018 > pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, type=Transaction > Layer, id=0018(Receiver ID) > pcieport...

Good news/bad news testing the new kernel on CentOS7 with my now notoriously finicky machines: Good news: 4.9.23-26.el7 (grabbed today via yum update) isn't any worse than 4.9.13-22 was on my xen hosts (as far as I can tell so far at least) Bad news: It isn't any better than 4.9.13 was for me either, if I don't set vcpu limit in the grub/xen config, it still panics like so: [

...lanes and drives and the problem happens on every single Silicon Mechanics system we have, so at this point I''m really doubting it''s a hardware issue :) Hardware details are as follows: Silicon Mechanics Storform iServ R518 (Based on SuperMicro SC847E16-R1400 chassis) SuperMicro X8DT3 motherboard w/ onboard LSI1068 controller. - One LSI port goes to the front backplane (where the bulk of the SATA drives are, the two SSD''s used as ZIL/OS) - The other LSI port goes to the rear backplane where the two L2ARC drives are along with a couple SATA''s...