April 2018 - iGVT-g - Ml01.01.Org

Setting up KVMGT for use with upstream QEMU 2.12

by Gizmo Chicken

If I’m not mistaken, the most current guide provided by Intel for setting up GVTg for KVM (KVMGT) is found here: https://github.com/intel/gvt-linux/wiki/GVTg_Setup_Guide The above referenced guide discusses setting up KVMGT for use with a custom version of QEMU that seems to be based on QEMU 2.9. When applying the guide to setting up KVMGT for use with upstream QEMU 2.12, what steps (if any) should be changed? NOTE: If the changes are significant, please don't feel any need to provide a full explanation of the changes here in the mailing list. But I do hope that someone will please update the above referenced guide with the changes as soon as feasible. Regards, GizmoChicken

2 years, 10 months

4
13
0 / 0

Will GVT-g support basic VGA mode (for guest setup) in the future?

by Gizmo Chicken

User "m132" posted in the Phoronix forums some helpful comments regarding GVT-g, including the need to install the Windows guest with QXL graphics first, and then install the Intel driver before switching to GVT-g. See [1]. Upon reading those comments, I was reminded that, when I first tried to get GVT-g working, although implied here [2] and here [3] in the GVT-g Setup Guide, the need for first using QXL graphics wasn't initially apparent to me. It seems strange to me that GVT-g can support the Intel driver, but can’t support basic VGA mode, which would be helpful during setup. QUESTION: Do you foresee GVT-g ever supporting basic VGA mode? Regards, GizmoChicken [1] https://www.phoronix.com/forums/forum/phoronix/latest-phoronix-articles/1... [2] https://github.com/intel/gvt-linux/wiki/GVTg_Setup_Guide#42-windows-guest... [3] https://github.com/intel/gvt-linux/wiki/GVTg_Setup_Guide#561-create-kvmgt-vm

2 years, 10 months

4
3
0 / 0

[ANNOUNCE] Intel GVT-g ISO for 2018-Q1 Release

by Xu, Terrence

Hi all, We are pleased to release the Intel GVT-g ISO which contains all the 2018-Q1 updates for both KVMGT and XenGT. The setup guide is embedded in ISO, please refer to README file for more details. Platform Support - Server platforms: Intel(r) Xeon(r) E3_v4, E3_v5 and E3_v6 with Intel Graphics processor - Client platforms: Intel(r) Core(tm) 5th generation (code name: Broadwell), 6th generation (code name: Skylake) and 7th generation (code name: Kabylake) Guest Operation System Validated - Windows7 32-bit, Window7 64-bit, Windows8.1 64-bit, Windows10 64-bit - Ubuntu 16.04 64-bit Major Changes from Q3'2017 Release - This update is based on kernel version 4.14 and Qemu version 2.10 and Xen 4.10. - Improve stability of Live Migration feature with internal stress test passed. - Implement dmabuf-based Guest VM framebuffer sharing for KVMGT. With adding GTK and Spice dmabuf support in Qemu (to be in Qemu 2.12), local and remote display use cases are preliminarily enabled. - Improve GVT health on IOMMU enabled platform by fixing high DMA setup overhead issue for KVMGT. - More bug fixing, code refinement and debugging interface enhancement, please refer to git log. Refer to Q1'18 KVMGT and XenGT release notes for more details. ISO download link: https://download.01.org/GVT-g/2018Q1/ Official GVT-g portal: https://01.org/igvt-g If you have any questions, please subscribe to join the mailing list: https://lists.01.org/mailman/listinfo/igvt-g Please subscribe to join the mailing list if you want to learn more about GVT-g project: https://lists.01.org/mailman/listinfo/igvt-g Please subscribe to join the mailing list if you want to contribute/review latest GVT-g upstream patches: https://lists.freedesktop.org/mailman/listinfo/intel-gvt-dev Note: The KVMGT and XenGT project should be considered a work in progress. As such it is not a complete product nor should it be considered one. Extra care should be taken when testing and configuring a system to use the KVMGT and XenGT project. Thanks Terrence Tel: +86-21-6116 5390 MP: +86-1356 4367 024 Mail: terrence.xu(a)intel.com<mailto:terrence.xu@intel.com> _______________________________________________ GVT-g mailing list iGVT-g(a)lists.01.org<mailto:iGVT-g@lists.01.org> https://lists.01.org/mailman/listinfo/igvt-g

2 years, 10 months

1
0
0 / 0

GVTg and hybrid graphics (Optimus) setups in Windows guests

by Jack Coulter

Over the last few months, myself and a few others have been working to try and get VM assignment of laptop Nvidia dGPUs working with KVM. This ended up involving a (very hacky) OVMF patch [1] to load the dGPU's VBIOS via the ACPI _ROM method; this works for now, but if we're able to get things working properly, it could be cleaned up into something a bit more maintainable. Things generally work without much struggle with Linux guests; the Nvidia GPU can be used to run guest applications both via the Bumblebee project's optirun/primusrun, and via DRI PRIME. As far as Windows guests are concerned, we've made significant progress, to the point where the Nvidia card initialises correctly and applications that explicitly make use of cross-adapter resources [2] can successfully use the dGPU and render at near native performance levels. Unfortunately, under Windows, the vast majority of applications seem to require a valid [3] hybrid graphics setup for the guest's Direct3D runtime to select the dGPU to render on. This has lead us down the path to attempting to get GVT-g working in the hopes that a VM with both a GVT-g iGPU and a Nvidia dGPU assigned would finally result in a working set up. After quite a bit of experimentation and and another OVMF patch [4], we finally got GVT-g display output working with a UEFI + Windows guest. This resulted in both the GVT-g iGPU and the Nvidia dGPU initialising correctly, and showing up in Windows Task Manager's performance tab. Sadly, the majority of applications will only render on the iGPU, again the only applications making use of the Nvidia dGPU being those that explicitly look for cross-adapter resources (in my testing, this is limited to Unreal Engine 4 games). After some scrutiny of the Microsoft documentation [3]: > When the system boots, one of the display adapters is marked as the current POST adapter. If this POST adapter supports Windows Display Driver Model (WDDM) 1.3 and has an integrated display panel, it's considered an /integrated hybrid/ adapter. I suspect we're getting caught up on the "has an integrated display panel" (identified by a _DXGK_INTEGRATED_DISPLAY_CHILD [5] child in the iGPU's _DXGK_CHILD_DESCRIPTOR [6] array populated by the DXGKDDI_QUERY_CHILD_RELATIONS method) part, as the virtual display emulated by a GVT-g device is a non-embedded DisplayPort display [8][9]. Assuming that this is the sole issue preventing this setup from working, then we have several options available but I'm not familiar enough with this area to accurately gauge the viability of each approach: 1. Amend gvt/display.c in the host kernel such that the virtual display used by the Intel VGPU is identified as an integrated display panel. 2. See if UPT assignment of the iGPU with x-igd-opregion=on results in the host's eDP panel being exposed to the guest. I have not been able to get UPT with x-igd-opregion to show any displays in the guest however, even though the Windows Intel driver appears to be working properly. 3. See if legacy iGPU assignment results in the host's eDP panel being exposed to the guest. This would most likely necessitate the use of a SeaBIOS VM rather than OVMF, as no UEFI-compatible Intel VBIOS exists to my knowledge. This would also require us to patch SeaBIOS for ACPI ROM loading for the Nvidia dGPU as in [1]. I've also not been able to get legacy assignment working on my machine at all - starting the VM immediately hangs the host (network connectivity is lost and SSH sessions to the host are dropped) 4. Do this without GVT entirely; upgrade qxl-wddm-dod [10] to WDDM 1.3 (it's currently 1.2 [11]) and amend it such that the emulated monitor is exposed as an integrated display panel. This is probably the cleanest approach, if it's technically feasible. At this point, I'm not really sure how to proceed any further with this effort. I'm posting this to both the igvt-g and vfio-users lists in the hopes that the wider audience will lead to someone more knowledgeable on all this than myself being able to provide some direction/advice as to how to best advance things. Cheers, Jack [1] https://github.com/jscinoz/optimus-vfio-docs/issues/2 [2] https://docs.microsoft.com/en-us/windows-hardware/drivers/display/renderi... [3] https://docs.microsoft.com/en-us/windows-hardware/drivers/display/validat... [4] https://bugzilla.tianocore.org/show_bug.cgi?id=935 [5] https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/content/dis... [6] https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/content/dis... [7] https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/content/dis... [8] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/d... [9] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/d... [10] https://gitlab.com/spice/qxl-wddm-dod [11] https://gitlab.com/spice/qxl-wddm-dod/blob/master/qxldod/QxlDod.cpp#L523

2 years, 10 months

1
0
0 / 0

Windows Intel driver crashing with GVT-g

by Sri Ramanujam

Hi all, I'm trying to use GVT-g on KVM with Windows Server 2016 guests on an i7-7700 processor. Whenever I try to install the latest Intel windows driver 15.65.5.4982 into the guests, it immediately crashes. Other drivers install without crashing, but fail to perform properly at all. In fact, it seems like the only driver that is completely stable is 15.45.19.4678, which is the driver version mentioned in the GVT-g wiki article. However, this driver does not show the console framebuffer in virt-manager VNC. Is there a known validated Windows driver version that provides stability, performance and console framebuffer? For debugging purposes, here is a memory dump taken from a Server 2016 guest with the 4982 crash:https://sri.dattodrive.com/index.php/s/3ztJuSiBEkGRwST Thank you! -- *Sri Ramanujam* Software Engineer Datto, Inc. www.datto.com <http://datto.com/datto-signature/> Join the conversation! [image: Facebook] <http://www.facebook.com/dattoinc> [image: Twitter] <https://twitter.com/dattobackup> [image: LinkedIn] <http://www.linkedin.com/company/1477873?trk=tyah> [image: pinterest] <http://pinterest.com/dattobackup/> [image: Blog RSS] <http://blog.dattobackup.com/blog> [image: YouTube] <http://www.youtube.com/user/DattoInc/featured> [image: Google Plus Page] <https://plus.google.com/u/0/108292366419623632143/posts>

2 years, 10 months

7
21
0 / 0

[Intel-gfx] [GVT-g] [ANNOUNCE] 2018-Q1 release of XenGT (Intel GVT-g for Xen)

by Xu, Terrence

Hi all, We are pleased to announce an update of Intel GVT-g for Xen. Intel GVT-g is a full GPU virtualization solution with mediated pass-through, starting from 4th generation Intel Core(TM) processors with Intel processor graphics. A virtual GPU instance is maintained for each VM, with part of performance critical resources directly assigned. The capability of running native graphics driver inside a VM, without hypervisor intervention in performance critical paths, achieves a good balance among performance, feature, and sharing capability. GVT-g for Xen hypervisor is XenGT. Repositories - Xen : https://github.com/01org/igvtg-xen (tag: 2018-q1-xengt-stable-4.10) - Kernel: https://github.com/01org/gvt-linux (tag: 2018-q1-gvt-stable-4.14) - Qemu: https://github.com/01org/igvtg-qemu (tag: 2018-q1-stable-2.10.0) Platform Support - Server platforms: Intel(r) Xeon(r) E3_v4, E3_v5 and E3_v6 with Intel Graphics processor - Client platforms: Intel(r) Core(tm) 5th generation (code name: Broadwell), 6th generation (code name: Skylake) and 7th generation (code name: Kabylake) Guest Operation System Validated - Windows7 32-bit, Window7 64-bit, Windows8.1 64-bit, Windows10 64-bit - Ubuntu 16.04 64-bit Major Changes from Q3'2017 Release - This update is based on kernel version 4.14 and Qemu version 2.10 and Xen 4.10. - Improve stability of Live Migration feature with internal stress test passed. - More bug fixing, code refinement and debugging interface enhancement, please refer to git log. Limitation or known issues: - Due to graphics hardware resource limitation, the maximum number of Windows VM is 7. - The pre-defined type vgt_low_gm_sz=128/256/512 of option into HVM file must be created for VM to install Windows 7 32-bit. vGPU type 8 is not allocated to have enough graphics resource to support Windows 7 32-bit. - If the default 1024x768 vm screen resolution couldn't satisfy your need, please add vgt_log_gm_sz=128/256/512 option into HVM file. - Due to one known regression issue in latest Intel Windows Graphics driver, Intel Windows Graphics driver version 15.45 is preferred to install in Windows VM and please don't enable Windows auto-update mechanism to update the driver to later version. Some 3rd party applications like 3DMark rely on DirectX12 features. DirectX12 is not supported in Intel Windows Graphics driver 15.45 or earlier versions. So the applications will not run well in Windows VM with these drivers. - There's corner case that Guest Windows 7 32bit VM may be killed automatically by Xen when Guest VM runs into TDR. This issues happens only on Broadwell platform. The workaround is to disable part of viridian feature in Guest VM hvm file by adding viridian=["all", "!apic_assist"]. Useful links: - Setup guide: https://github.com/01org/gvt-linux/wiki/GVTg_Setup_Guide - New upstream architecture design introduction: https://01.org/igvt-g/documentation/intel-gvt-g-new-architecture-introduc... - Please subscribe to join the mailing list if you want to learn more about GVT-g project: https://lists.01.org/mailman/listinfo/igvt-g - Please subscribe to join the mailing list if you want to contribute/review latest GVT-g upstream patches: https://lists.freedesktop.org/mailman/listinfo/intel-gvt-dev - Official GVT-g portal: https://01.org/igvt-g - More information about background, architecture and others about Intel GVT-g, can be found at: https://01.org/igvt-g https://www.usenix.org/conference/atc14/technical-sessions/presentation/tian http://events.linuxfoundation.org/sites/events/files/slides/XenGT-Xen%20S... http://events.linuxfoundation.org/sites/events/files/slides/XenGT-Xen%20S... https://01.org/xen/blogs/srclarkx/2013/graphics-virtualization-xengt Important Note: The XenGT project should be considered a work in progress. As such it is not a complete product nor should it be considered one. Extra care should be taken when testing and configuring a system to use the XenGT project. Thanks Terrence Tel: +86-21-6116 5390 MP: +86-1356 4367 024 Mail: terrence.xu(a)intel.com<mailto:terrence.xu@intel.com> _______________________________________________ GVT-g mailing list iGVT-g(a)lists.01.org<mailto:iGVT-g@lists.01.org> https://lists.01.org/mailman/listinfo/igvt-g

2 years, 10 months

1
0
0 / 0

[Intel-gfx] [GVT-g] [ANNOUNCE] 2018-Q1 release of KVMGT (Intel GVT-g for KVM)

by Xu, Terrence

Hi all, We are pleased to announce an update of Intel GVT-g for KVM. Intel GVT-g for KVM (a.k.a. KVMGT) is a full GPU virtualization solution with mediated pass-through, starting from 5th generation Intel Core(TM) processors with Intel processor graphics. A virtual GPU instance is maintained for each VM, with part of performance critical resources directly assigned. The capability of running native graphics driver inside a VM, without hypervisor intervention in performance critical paths, achieves a good balance among performance, feature, and sharing capability. Repositories: - Kernel: https://github.com/01org/gvt-linux (tag: 2018-q1-gvt-stable-4.14) - Qemu: https://github.com/01org/igvtg-qemu (tag: 2018-q1-stable-2.10.0) Platform Support: - Server platforms: Intel(r) Xeon(r) E3_v4, E3_v5 and E3_v6 with Intel Graphics processor - Client platforms: Intel(r) Core(tm) 5th generation (code name: Broadwell), 6th generation (code name: Skylake) and 7th generation (code name: Kabylake) Guest Operation System Validated: - Windows7 32-bit, Window7 64-bit, Windows8.1 64-bit, Windows10 64-bit - Ubuntu 16.04 64-bit Major Changes from Q3'2017 Release: - This update is based on kernel version 4.14 and Qemu version 2.10. - Improve stability of Live Migration feature with internal stress test passed. - Implement dmabuf-based Guest VM framebuffer sharing. With adding GTK and Spice dmabuf support in Qemu (to be in Qemu 2.12), local and remote display use cases are preliminarily enabled. - Improve GVT health on IOMMU enabled platform by fixing high DMA setup overhead issue. - More bug fixing, code refinement and debugging interface enhancement, please refer to git log. Limitation or known issues: - Due to graphics hardware resource limitation, the maximum number of Windows VM is 7. - The pre-defined type 1, 2 or 4 of vGPU must be created for VM to install Windows 7 32-bit. vGPU type 8 is not allocated to have enough graphics resource to support Windows 7 32-bit. - Some 3rd party applications/tools like GPU_Z, Passmark 9.0 running in Windows VM may meet BSOD error. This happens when these applications try to access some un-emulated Model Specific Registers in KVM. The workaround is to add "kvm.ignore_msrs=1" in host kernel's command line to avoid this. - Due to one known regression issue in latest Intel Windows Graphics driver, Intel Windows Graphics driver version 15.45 is preferred to install in Windows VM and please don't enable Windows auto-update mechanism to update the driver to later version. Some 3rd party applications like 3DMark rely on DirectX12 features. DirectX12 is not supported in Intel Windows Graphics driver 15.45 or earlier versions. So the applications will not run well in Windows VM with these drivers. - There's case about Guest VM stability while the IOMMU feature is enabled. The issues happens on a few Broadwell and Kabylake platforms. There are still instability issues seen on a few Broadwell and Kabylake machines when IOMMU is enabled in Host. The workaround is to turn off IOMMU on Intel graphics device by adding "intel_iommu=igfx_off" in Host kernel's command line. Useful links: - Setup guide: https://github.com/01org/gvt-linux/wiki/GVTg_Setup_Guide - New upstream architecture design introduction: https://01.org/igvt-g/documentation/intel-gvt-g-new-architecture-introduc... - Please subscribe to join the mailing list if you want to learn more about GVT-g project: https://lists.01.org/mailman/listinfo/igvt-g - Please subscribe to join the mailing list if you want to contribute/review latest GVT-g upstream patches: https://lists.freedesktop.org/mailman/listinfo/intel-gvt-dev - Official GVT-g portal: https://01.org/igvt-g - More information about background, architecture and others about Intel GVT-g, can be found at: http://www.linux-kvm.org/images/f/f3/01x08b-KVMGT-a.pdf https://www.usenix.org/conference/atc14/technical-sessions/presentation/tian Important Note: The KVMGT project should be considered a work in progress. As such it is not a complete product nor should it be considered one. Extra care should be taken when testing and configuring a system to use the KVMGT project. Thanks Terrence Tel: +86-21-6116 5390 MP: +86-1356 4367 024 Mail: terrence.xu(a)intel.com<mailto:terrence.xu@intel.com> _______________________________________________ GVT-g mailing list iGVT-g(a)lists.01.org<mailto:iGVT-g@lists.01.org> https://lists.01.org/mailman/listinfo/igvt-g

2 years, 10 months

1
0
0 / 0

Hardware Support Question

by Richard Walter

Hi list, Is it possible to use gvt-g with Intel NUC 7i5DNH? I followed the gvt-g setup guide on github. The guide worked well on a ASUS P9X79 Pro with Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz under Debian Strech. But with Intel NUC 7i5DNH and Ubuntu 16.04.4 the command ll /sys/bus/pci/devices/0000:00:02.0/mdev_supported_types/ failed with directory not found. cat /proc/cpuinfo | grep "model name" model name : Intel(R) Core(TM) i5-7300U CPU @ 2.60GHz lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 02) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model Is this hardware supported by igvt-g? Thanks Richard

2 years, 10 months

5
12
0 / 0

Re: [iGVT-g] Hardware Support Question

by Richard Walter

# cat /sys/bus/pci/devices/0000:00:02.0/mdev_supported_types/i915-GVTg_V5_1/description low_gm_size: 512MB high_gm_size: 2048MB fence: 4 resolution: 1920x1200 weight: 16 Best regards, Richard 2018-04-16 11:11 GMT+02:00 Oliver Rath <oliver(a)greenunit.de>: > Hi Richard, for my personal research: What is the content of your file > > i915-GVTg_V5_1/description > > ? > > Tfh! > > Oliver > > On 16.04.2018 10:47, Richard Walter wrote: > > Now it works. > > # ll /sys/bus/pci/devices/0000:00:02.0/mdev_supported_types/ > insgesamt 0 > drwxr-xr-x 6 root root 0 Apr 16 10:42 ./ > drwxr-xr-x 10 root root 0 Apr 16 10:42 ../ > drwxr-xr-x 3 root root 0 Apr 16 10:42 i915-GVTg_V5_1/ > drwxr-xr-x 3 root root 0 Apr 16 10:42 i915-GVTg_V5_2/ > drwxr-xr-x 3 root root 0 Apr 16 10:42 i915-GVTg_V5_4/ > drwxr-xr-x 3 root root 0 Apr 16 10:42 i915-GVTg_V5_8/ > > Thank you very much. > > Rchard > > 2018-04-16 10:25 GMT+02:00 Zhang, Xiong Y <xiong.y.zhang(a)intel.com>: > >> Please remove “nomodeset” from grub. >> >> >> >> thanks >> >> *From:* iGVT-g [mailto:igvt-g-bounces@lists.01.org] *On Behalf Of *Richard >> Walter >> *Sent:* Monday, April 16, 2018 4:23 PM >> *To:* Yuan, Hang <hang.yuan(a)intel.com>; iGVT-g(a)lists.01.org >> *Subject:* Re: [iGVT-g] Hardware Support Question >> >> >> >> [ 0.000000] Linux version 4.16.0-rc5+ (root@vmserver11) (gcc version >> 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)) #1 SMP Tue Mar 20 16:18:37 >> CET 2018 >> >> [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.16.0-rc5+ >> root=UUID=406fbf0e-4b09-467d-8a8d-7c00e430dd16 ro net.ifnames=0 >> biosdevname=0 ignore_loglevel log_buf_len=128M console=ttyS0,115200,8n1 >> i915.enable_gvt=1 kvm.ignore_msrs=1 intel_iommu=on drm.debug=0 quiet >> nomodeset >> >> [ 0.000000] KERNEL supported cpus: >> >> [ 0.000000] Intel GenuineIntel >> >> [ 0.000000] AMD AuthenticAMD >> >> [ 0.000000] Centaur CentaurHauls >> >> [ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating >> point registers' >> >> [ 0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' >> >> [ 0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' >> >> [ 0.000000] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds >> registers' >> >> [ 0.000000] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR' >> >> [ 0.000000] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 >> >> [ 0.000000] x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64 >> >> [ 0.000000] x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64 >> >> [ 0.000000] x86/fpu: Enabled xstate features 0x1f, context size is 960 >> bytes, using 'compacted' format. >> >> [ 0.000000] e820: BIOS-provided physical RAM map: >> >> [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] >> usable >> >> [ 0.000000] BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] >> reserved >> >> [ 0.000000] BIOS-e820: [mem 0x0000000000059000-0x000000000009dfff] >> usable >> >> [ 0.000000] BIOS-e820: [mem 0x000000000009e000-0x00000000000fffff] >> reserved >> >> [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x0000000089e5efff] >> usable >> >> [ 0.000000] BIOS-e820: [mem 0x0000000089e5f000-0x0000000089e5ffff] >> ACPI NVS >> >> [ 0.000000] BIOS-e820: [mem 0x0000000089e60000-0x0000000089e60fff] >> reserved >> >> [ 0.000000] BIOS-e820: [mem 0x0000000089e61000-0x000000008f58cfff] >> usable >> >> [ 0.000000] BIOS-e820: [mem 0x000000008f58d000-0x000000008fa1cfff] >> reserved >> >> [ 0.000000] BIOS-e820: [mem 0x000000008fa1d000-0x000000008fa64fff] >> ACPI data >> >> [ 0.000000] BIOS-e820: [mem 0x000000008fa65000-0x000000008fac4fff] >> ACPI NVS >> >> [ 0.000000] BIOS-e820: [mem 0x000000008fac5000-0x000000008ff2cfff] >> reserved >> >> [ 0.000000] BIOS-e820: [mem 0x000000008ff2d000-0x000000008fffefff] >> type 20 >> >> [ 0.000000] BIOS-e820: [mem 0x000000008ffff000-0x000000008fffffff] >> usable >> >> [ 0.000000] BIOS-e820: [mem 0x0000000090000000-0x000000009cffffff] >> reserved >> >> [ 0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] >> reserved >> >> [ 0.000000] BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] >> reserved >> >> [ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] >> reserved >> >> [ 0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] >> reserved >> >> [ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] >> reserved >> >> [ 0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] >> reserved >> >> [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x0000000860ffffff] >> usable >> >> [ 0.000000] debug: ignoring loglevel setting. >> >> [ 0.000000] NX (Execute Disable) protection: active >> >> [ 0.000000] efi: EFI v2.60 by American Megatrends >> >> [ 0.000000] efi: ACPI 2.0=0x8fa2b000 ACPI=0x8fa2b000 >> SMBIOS=0x8fe89000 SMBIOS 3.0=0x8fe88000 ESRT=0x8fe85418 >> MEMATTR=0x8d79a018 >> >> [ 0.000000] random: fast init done >> >> [ 0.000000] SMBIOS 3.0.0 present. >> >> [ 0.000000] DMI: Intel Corporation NUC7i5DNHE/NUC7i5DNB, BIOS >> DNKBLi5v.86A.0026.2017.0915.2016 09/15/2017 >> >> [ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> >> reserved >> >> [ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable >> >> [ 0.000000] e820: last_pfn = 0x861000 max_arch_pfn = 0x400000000 >> >> [ 0.000000] MTRR default type: write-back >> >> [ 0.000000] MTRR fixed ranges enabled: >> >> [ 0.000000] 00000-9FFFF write-back >> >> [ 0.000000] A0000-BFFFF uncachable >> >> [ 0.000000] C0000-FFFFF write-protect >> >> [ 0.000000] MTRR variable ranges enabled: >> >> [ 0.000000] 0 base 00C0000000 mask 7FC0000000 uncachable >> >> [ 0.000000] 1 base 00A0000000 mask 7FE0000000 uncachable >> >> [ 0.000000] 2 base 009C000000 mask 7FFC000000 uncachable >> >> [ 0.000000] 3 base 009A000000 mask 7FFE000000 uncachable >> >> [ 0.000000] 4 base 0099000000 mask 7FFF000000 uncachable >> >> [ 0.000000] 5 base 0098800000 mask 7FFF800000 uncachable >> >> [ 0.000000] 6 base 2000000000 mask 7000000000 uncachable >> >> [ 0.000000] 7 disabled >> >> [ 0.000000] 8 disabled >> >> [ 0.000000] 9 disabled >> >> [ 0.000000] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- >> WT >> >> [ 0.000000] e820: last_pfn = 0x90000 max_arch_pfn = 0x400000000 >> >> [ 0.000000] esrt: Reserving ESRT space from 0x000000008fe85418 to >> 0x000000008fe85450. >> >> [ 0.000000] Scanning 1 areas for low memory corruption >> >> [ 0.000000] Base memory trampoline at [ (ptrval)] 98000 size >> 24576 >> >> [ 0.000000] Using GB pages for direct mapping >> >> [ 0.000000] BRK [0x4c9ee000, 0x4c9eefff] PGTABLE >> >> [ 0.000000] BRK [0x4c9ef000, 0x4c9effff] PGTABLE >> >> [ 0.000000] BRK [0x4c9f0000, 0x4c9f0fff] PGTABLE >> >> [ 0.000000] BRK [0x4c9f1000, 0x4c9f1fff] PGTABLE >> >> [ 0.000000] BRK [0x4c9f2000, 0x4c9f2fff] PGTABLE >> >> [ 0.000000] BRK [0x4c9f3000, 0x4c9f3fff] PGTABLE >> >> [ 0.000000] BRK [0x4c9f4000, 0x4c9f4fff] PGTABLE >> >> [ 0.000000] log_buf_len: 134217728 bytes >> >> [ 0.000000] early log buf free: 256736(97%) >> >> [ 0.000000] Secure boot could not be determined >> >> [ 0.000000] RAMDISK: [mem 0x329de000-0x354e6fff] >> >> [ 0.000000] ACPI: Early table checksum verification disabled >> >> [ 0.000000] ACPI: RSDP 0x000000008FA2B000 000024 (v02 INTEL ) >> >> [ 0.000000] ACPI: XSDT 0x000000008FA2B0C0 000104 (v01 INTEL NUC7i5DN >> 0000001A AMI 00010013) >> >> [ 0.000000] ACPI: FACP 0x000000008FA54A88 000114 (v06 INTEL NUC7i5DN >> 0000001A AMI 00010013) >> >> [ 0.000000] ACPI: DSDT 0x000000008FA2B258 02982F (v02 INTEL NUC7i5DN >> 0000001A INTL 20160422) >> >> [ 0.000000] ACPI: FACS 0x000000008FA94F00 000040 >> >> [ 0.000000] ACPI: APIC 0x000000008FA54BA0 000084 (v03 INTEL NUC7i5DN >> 0000001A AMI 00010013) >> >> [ 0.000000] ACPI: FPDT 0x000000008FA54C28 000044 (v01 INTEL NUC7i5DN >> 0000001A AMI 00010013) >> >> [ 0.000000] ACPI: FIDT 0x000000008FA54C70 00009C (v01 INTEL NUC7i5DN >> 0000001A AMI 00010013) >> >> [ 0.000000] ACPI: MCFG 0x000000008FA54D10 00003C (v01 INTEL NUC7i5DN >> 0000001A MSFT 00000097) >> >> [ 0.000000] ACPI: SSDT 0x000000008FA54D50 000359 (v01 INTEL NUC7i5DN >> 0000001A INTL 20160422) >> >> [ 0.000000] ACPI: WDAT 0x000000008FA550B0 000194 (v01 INTEL NUC7i5DN >> 0000001A MSFT 00010013) >> >> [ 0.000000] ACPI: SSDT 0x000000008FA55248 003156 (v02 INTEL NUC7i5DN >> 0000001A INTL 20160422) >> >> [ 0.000000] ACPI: HPET 0x000000008FA583A0 000038 (v01 INTEL NUC7i5DN >> 0000001A MSFT 0000005F) >> >> [ 0.000000] ACPI: SSDT 0x000000008FA583D8 000024 (v02 INTEL NUC7i5DN >> 0000001A INTL 20160422) >> >> [ 0.000000] ACPI: SSDT 0x000000008FA58400 00475C (v02 INTEL NUC7i5DN >> 0000001A INTL 20160422) >> >> [ 0.000000] ACPI: SSDT 0x000000008FA5CB60 0011A2 (v02 INTEL NUC7i5DN >> 0000001A INTL 20160422) >> >> [ 0.000000] ACPI: SSDT 0x000000008FA5DD08 000728 (v02 INTEL NUC7i5DN >> 0000001A INTL 20160422) >> >> [ 0.000000] ACPI: UEFI 0x000000008FA5E430 000042 (v01 INTEL NUC7i5DN >> 0000001A 01000013) >> >> [ 0.000000] ACPI: SSDT 0x000000008FA5E478 0017AE (v02 INTEL NUC7i5DN >> 0000001A INTL 20160422) >> >> [ 0.000000] ACPI: LPIT 0x000000008FA5FC28 000094 (v01 INTEL NUC7i5DN >> 0000001A MSFT 0000005F) >> >> [ 0.000000] ACPI: SSDT 0x000000008FA5FCC0 000141 (v02 INTEL NUC7i5DN >> 0000001A INTL 20160422) >> >> [ 0.000000] ACPI: SSDT 0x000000008FA5FE08 00029F (v02 INTEL NUC7i5DN >> 0000001A INTL 20160422) >> >> [ 0.000000] ACPI: SSDT 0x000000008FA600A8 003002 (v02 INTEL NUC7i5DN >> 0000001A INTL 20160422) >> >> [ 0.000000] ACPI: SSDT 0x000000008FA630B0 000517 (v02 INTEL NUC7i5DN >> 0000001A INTL 20160422) >> >> [ 0.000000] ACPI: DBGP 0x000000008FA635C8 000034 (v01 INTEL NUC7i5DN >> 0000001A MSFT 0000005F) >> >> [ 0.000000] ACPI: DBG2 0x000000008FA63600 000054 (v00 INTEL NUC7i5DN >> 0000001A MSFT 0000005F) >> >> [ 0.000000] ACPI: SSDT 0x000000008FA63658 0012E6 (v02 INTEL NUC7i5DN >> 0000001A INTL 20160422) >> >> [ 0.000000] ACPI: DMAR 0x000000008FA64940 0000F0 (v01 INTEL NUC7i5DN >> 0000001A INTL 00000001) >> >> [ 0.000000] ACPI: BGRT 0x000000008FA64A30 000038 (v01 INTEL NUC7i5DN >> 0000001A AMI 00010013) >> >> [ 0.000000] ACPI: TPM2 0x000000008FA64A68 000034 (v03 INTEL NUC7i5DN >> 0000001A AMI 00000000) >> >> [ 0.000000] ACPI: ASF! 0x000000008FA64AA0 0000A0 (v32 INTEL NUC7i5DN >> 0000001A TFSM 000F4240) >> >> [ 0.000000] ACPI: WSMT 0x000000008FA64B40 000028 (v01 INTEL NUC7i5DN >> 0000001A AMI 00010013) >> >> [ 0.000000] ACPI: Local APIC address 0xfee00000 >> >> [ 0.000000] No NUMA configuration found >> >> [ 0.000000] Faking a node at [mem 0x0000000000000000-0x000000086 >> 0ffffff] >> >> [ 0.000000] NODE_DATA(0) allocated [mem 0x858ff9000-0x858ffdfff] >> >> [ 0.000000] Zone ranges: >> >> [ 0.000000] DMA [mem 0x0000000000001000-0x0000000000ffffff] >> >> [ 0.000000] DMA32 [mem 0x0000000001000000-0x00000000ffffffff] >> >> [ 0.000000] Normal [mem 0x0000000100000000-0x0000000860ffffff] >> >> [ 0.000000] Device empty >> >> [ 0.000000] Movable zone start for each node >> >> [ 0.000000] Early memory node ranges >> >> [ 0.000000] node 0: [mem 0x0000000000001000-0x0000000000057fff] >> >> [ 0.000000] node 0: [mem 0x0000000000059000-0x000000000009dfff] >> >> [ 0.000000] node 0: [mem 0x0000000000100000-0x0000000089e5efff] >> >> [ 0.000000] node 0: [mem 0x0000000089e61000-0x000000008f58cfff] >> >> [ 0.000000] node 0: [mem 0x000000008ffff000-0x000000008fffffff] >> >> [ 0.000000] node 0: [mem 0x0000000100000000-0x0000000860ffffff] >> >> [ 0.000000] Initmem setup node 0 [mem 0x0000000000001000-0x000000086 >> 0ffffff] >> >> [ 0.000000] On node 0 totalpages: 8324392 >> >> [ 0.000000] DMA zone: 64 pages used for memmap >> >> [ 0.000000] DMA zone: 22 pages reserved >> >> [ 0.000000] DMA zone: 3996 pages, LIFO batch:0 >> >> [ 0.000000] DMA32 zone: 9111 pages used for memmap >> >> [ 0.000000] DMA32 zone: 583052 pages, LIFO batch:31 >> >> [ 0.000000] Normal zone: 120896 pages used for memmap >> >> [ 0.000000] Normal zone: 7737344 pages, LIFO batch:31 >> >> [ 0.000000] Reserved but unavailable: 99 pages >> >> [ 0.000000] Reserving Intel graphics memory at [mem >> 0x99000000-0x9cffffff] >> >> [ 0.000000] ACPI: PM-Timer IO Port: 0x1808 >> >> [ 0.000000] ACPI: Local APIC address 0xfee00000 >> >> [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) >> >> [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) >> >> [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) >> >> [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) >> >> [ 0.000000] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI >> 0-119 >> >> [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) >> >> [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) >> >> [ 0.000000] ACPI: IRQ0 used by override. >> >> [ 0.000000] ACPI: IRQ9 used by override. >> >> [ 0.000000] Using ACPI (MADT) for SMP configuration information >> >> [ 0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000 >> >> [ 0.000000] smpboot: Allowing 4 CPUs, 0 hotplug CPUs >> >> [ 0.000000] PM: Registered nosave memory: [mem 0x00000000-0x00000fff] >> >> [ 0.000000] PM: Registered nosave memory: [mem 0x00058000-0x00058fff] >> >> [ 0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x000fffff] >> >> [ 0.000000] PM: Registered nosave memory: [mem 0x89e5f000-0x89e5ffff] >> >> [ 0.000000] PM: Registered nosave memory: [mem 0x89e60000-0x89e60fff] >> >> [ 0.000000] PM: Registered nosave memory: [mem 0x8f58d000-0x8fa1cfff] >> >> [ 0.000000] PM: Registered nosave memory: [mem 0x8fa1d000-0x8fa64fff] >> >> [ 0.000000] PM: Registered nosave memory: [mem 0x8fa65000-0x8fac4fff] >> >> [ 0.000000] PM: Registered nosave memory: [mem 0x8fac5000-0x8ff2cfff] >> >> [ 0.000000] PM: Registered nosave memory: [mem 0x8ff2d000-0x8fffefff] >> >> [ 0.000000] PM: Registered nosave memory: [mem 0x90000000-0x9cffffff] >> >> [ 0.000000] PM: Registered nosave memory: [mem 0x9d000000-0xdfffffff] >> >> [ 0.000000] PM: Registered nosave memory: [mem 0xe0000000-0xefffffff] >> >> [ 0.000000] PM: Registered nosave memory: [mem 0xf0000000-0xfdffffff] >> >> [ 0.000000] PM: Registered nosave memory: [mem 0xfe000000-0xfe010fff] >> >> [ 0.000000] PM: Registered nosave memory: [mem 0xfe011000-0xfebfffff] >> >> [ 0.000000] PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff] >> >> [ 0.000000] PM: Registered nosave memory: [mem 0xfec01000-0xfecfffff] >> >> [ 0.000000] PM: Registered nosave memory: [mem 0xfed00000-0xfed00fff] >> >> [ 0.000000] PM: Registered nosave memory: [mem 0xfed01000-0xfedfffff] >> >> [ 0.000000] PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff] >> >> [ 0.000000] PM: Registered nosave memory: [mem 0xfee01000-0xfeffffff] >> >> [ 0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff] >> >> [ 0.000000] e820: [mem 0x9d000000-0xdfffffff] available for PCI devices >> >> [ 0.000000] Booting paravirtualized kernel on bare hardware >> >> [ 0.000000] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: >> 0xffffffff, max_idle_ns: 7645519600211568 ns >> >> [ 0.000000] setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:4 >> nr_node_ids:1 >> >> [ 0.000000] percpu: Embedded 45 pages/cpu @ (ptrval) s146520 >> r8192 d29608 u524288 >> >> [ 0.000000] pcpu-alloc: s146520 r8192 d29608 u524288 alloc=1*2097152 >> >> [ 0.000000] pcpu-alloc: [0] 0 1 2 3 >> >> [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: >> 8194299 >> >> [ 0.000000] Policy zone: Normal >> >> [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.16.0-rc5+ >> root=UUID=406fbf0e-4b09-467d-8a8d-7c00e430dd16 ro net.ifnames=0 >> biosdevname=0 ignore_loglevel log_buf_len=128M console=ttyS0,115200,8n1 >> i915.enable_gvt=1 kvm.ignore_msrs=1 intel_iommu=on drm.debug=0 quiet >> nomodeset >> >> [ 0.000000] DMAR: IOMMU enabled >> >> [ 0.000000] Calgary: detecting Calgary via BIOS EBDA area >> >> [ 0.000000] Calgary: Unable to locate Rio Grande table in EBDA - >> bailing! >> >> [ 0.000000] Memory: 32461532K/33297568K available (12300K kernel code, >> 1554K rwdata, 3928K rodata, 1692K init, 1184K bss, 836036K reserved, 0K >> cma-reserved) >> >> [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 >> >> [ 0.000000] Kernel/User page tables isolation: enabled >> >> [ 0.000000] ftrace: allocating 38245 entries in 150 pages >> >> [ 0.000000] Hierarchical RCU implementation. >> >> [ 0.000000] RCU restricting CPUs from NR_CPUS=512 to nr_cpu_ids=4. >> >> [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, >> nr_cpu_ids=4 >> >> [ 0.000000] NR_IRQS: 33024, nr_irqs: 1024, preallocated irqs: 16 >> >> [ 0.000000] Console: colour dummy device 80x25 >> >> [ 0.000000] console [ttyS0] enabled >> >> [ 0.000000] ACPI: Core revision 20180105 >> >> [ 0.000000] ACPI: 13 ACPI AML tables successfully acquired and loaded >> >> [ 0.000000] clocksource: hpet: mask: 0xffffffff max_cycles: >> 0xffffffff, max_idle_ns: 79635855245 ns >> >> [ 0.000000] hpet clockevent registered >> >> [ 0.004000] APIC: Switch to symmetric I/O mode setup >> >> [ 0.008000] DMAR: Host address width 39 >> >> [ 0.012000] DMAR: DRHD base: 0x000000fed90000 flags: 0x0 >> >> [ 0.016000] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap >> 1c0000c40660462 ecap 19e2ff0505e >> >> [ 0.020000] DMAR: DRHD base: 0x000000fed91000 flags: 0x1 >> >> [ 0.024000] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap >> d2008c40660462 ecap f050da >> >> [ 0.028000] DMAR: RMRR base: 0x0000008f99e000 end: 0x0000008f9bdfff >> >> [ 0.032000] DMAR: RMRR base: 0x00000098800000 end: 0x0000009cffffff >> >> [ 0.036000] DMAR: ANDD device: 1 name: \_SB.PCI0.I2C0 >> >> [ 0.040000] DMAR: ANDD device: 2 name: \_SB.PCI0.I2C1 >> >> [ 0.044000] DMAR-IR: IOAPIC id 2 under DRHD base 0xfed91000 IOMMU 1 >> >> [ 0.048000] DMAR-IR: HPET id 0 under DRHD base 0xfed91000 >> >> [ 0.052000] DMAR-IR: Queued invalidation will be enabled to support >> x2apic and Intr-remapping. >> >> [ 0.060000] DMAR-IR: Enabled IRQ remapping in x2apic mode >> >> [ 0.060000] x2apic enabled >> >> [ 0.064000] Switched APIC routing to cluster x2apic. >> >> [ 0.072000] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 >> >> [ 0.092000] tsc: Detected 2700.000 MHz processor >> >> [ 0.096000] tsc: Detected 2712.000 MHz TSC >> >> [ 0.096000] clocksource: tsc-early: mask: 0xffffffffffffffff >> max_cycles: 0x2717868ea45, max_idle_ns: 440795316085 ns >> >> [ 0.104002] Calibrating delay loop (skipped), value calculated using >> timer frequency.. 5424.00 BogoMIPS (lpj=10848000) >> >> [ 0.108001] pid_max: default: 32768 minimum: 301 >> >> [ 0.112705] Security Framework initialized >> >> [ 0.116001] Yama: becoming mindful. >> >> [ 0.120012] AppArmor: AppArmor initialized >> >> [ 0.131364] Dentry cache hash table entries: 4194304 (order: 13, >> 33554432 bytes) >> >> [ 0.136883] Inode-cache hash table entries: 2097152 (order: 12, >> 16777216 bytes) >> >> [ 0.140068] Mount-cache hash table entries: 65536 (order: 7, 524288 >> bytes) >> >> [ 0.144065] Mountpoint-cache hash table entries: 65536 (order: 7, >> 524288 bytes) >> >> [ 0.148172] CPU: Physical Processor ID: 0 >> >> [ 0.152004] CPU: Processor Core ID: 0 >> >> [ 0.156005] ENERGY_PERF_BIAS: Set to 'normal', was 'performance' >> >> [ 0.160000] ENERGY_PERF_BIAS: View and update with >> x86_energy_perf_policy(8) >> >> [ 0.164006] mce: CPU supports 8 MCE banks >> >> [ 0.168009] CPU0: Thermal monitoring enabled (TM1) >> >> [ 0.172015] process: using mwait in idle threads >> >> [ 0.176002] Last level iTLB entries: 4KB 64, 2MB 8, 4MB 8 >> >> [ 0.180000] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0, 1GB 4 >> >> [ 0.184001] Spectre V2 : Mitigation: Full generic retpoline >> >> [ 0.188000] Spectre V2 : Spectre v2 mitigation: Filling RSB on context >> switch >> >> [ 0.192257] Freeing SMP alternatives memory: 36K >> >> [ 0.200287] TSC deadline timer enabled >> >> [ 0.204000] smpboot: CPU0: Intel(R) Core(TM) i5-7300U CPU @ 2.60GHz >> (family: 0x6, model: 0x8e, stepping: 0x9) >> >> [ 0.204054] Performance Events: PEBS fmt3+, Skylake events, 32-deep >> LBR, full-width counters, Intel PMU driver. >> >> [ 0.208005] ... version: 4 >> >> [ 0.212001] ... bit width: 48 >> >> [ 0.216001] ... generic registers: 4 >> >> [ 0.220001] ... value mask: 0000ffffffffffff >> >> [ 0.224001] ... max period: 00007fffffffffff >> >> [ 0.228001] ... fixed-purpose events: 3 >> >> [ 0.232001] ... event mask: 000000070000000f >> >> [ 0.236033] Hierarchical SRCU implementation. >> >> [ 0.240850] NMI watchdog: Enabled. Permanently consumes one hw-PMU >> counter. >> >> [ 0.244009] smp: Bringing up secondary CPUs ... >> >> [ 0.248077] x86: Booting SMP configuration: >> >> [ 0.252003] .... node #0, CPUs: #1 #2 #3 >> >> [ 0.252453] smp: Brought up 1 node, 4 CPUs >> >> [ 0.260001] smpboot: Max logical packages: 1 >> >> [ 0.264001] smpboot: Total of 4 processors activated (21696.00 >> BogoMIPS) >> >> [ 0.272184] devtmpfs: initialized >> >> [ 0.272184] x86/mm: Memory block size: 128MB >> >> [ 0.277842] evm: security.selinux >> >> [ 0.284001] evm: security.SMACK64 >> >> [ 0.287329] evm: security.SMACK64EXEC >> >> [ 0.292001] evm: security.SMACK64TRANSMUTE >> >> [ 0.296001] evm: security.SMACK64MMAP >> >> [ 0.299679] evm: security.apparmor >> >> [ 0.300001] evm: security.ima >> >> [ 0.302983] evm: security.capability >> >> [ 0.308067] PM: Registering ACPI NVS region [mem >> 0x89e5f000-0x89e5ffff] (4096 bytes) >> >> [ 0.316002] PM: Registering ACPI NVS region [mem >> 0x8fa65000-0x8fac4fff] (393216 bytes) >> >> [ 0.324040] clocksource: jiffies: mask: 0xffffffff max_cycles: >> 0xffffffff, max_idle_ns: 7645041785100000 ns >> >> [ 0.332009] futex hash table entries: 1024 (order: 4, 65536 bytes) >> >> [ 0.340048] pinctrl core: initialized pinctrl subsystem >> >> [ 0.344150] RTC time: 11:18:33, date: 04/06/18 >> >> [ 0.349023] NET: Registered protocol family 16 >> >> [ 0.356115] audit: initializing netlink subsys (disabled) >> >> [ 0.360007] audit: type=2000 audit(1523013511.360:1): >> state=initialized audit_enabled=0 res=1 >> >> [ 0.368002] cpuidle: using governor ladder >> >> [ 0.372011] cpuidle: using governor menu >> >> [ 0.376085] KVM setup pv remote TLB flush >> >> [ 0.380005] ACPI FADT declares the system doesn't support PCIe ASPM, >> so disable it >> >> [ 0.388001] ACPI: bus type PCI registered >> >> [ 0.392001] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 >> >> [ 0.400055] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem >> 0xe0000000-0xefffffff] (base 0xe0000000) >> >> [ 0.408003] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in >> E820 >> >> [ 0.416011] PCI: Using configuration type 1 for base access >> >> [ 0.424017] HugeTLB registered 1.00 GiB page size, pre-allocated 0 >> pages >> >> [ 0.428002] HugeTLB registered 2.00 MiB page size, pre-allocated 0 >> pages >> >> [ 0.436075] ACPI: Added _OSI(Module Device) >> >> [ 0.440002] ACPI: Added _OSI(Processor Device) >> >> [ 0.444001] ACPI: Added _OSI(3.0 _SCP Extensions) >> >> [ 0.448001] ACPI: Added _OSI(Processor Aggregator Device) >> >> [ 0.456924] ACPI BIOS Error (bug): Failure looking up >> [\_SB.PCI0.RP04.PXSX._SB.PCI0.RP05.PXSX], AE_NOT_FOUND >> (20180105/dswload2-194) >> >> [ 0.468002] ACPI Error: AE_NOT_FOUND, During name lookup/catalog >> (20180105/psobject-252) >> >> [ 0.476001] ACPI Error: Method parse/execution failed >> \_SB.PCI0.RP04.PXSX, AE_NOT_FOUND (20180105/psparse-550) >> >> [ 0.488295] ACPI BIOS Error (bug): Failure looking up >> [\_SB.PCI0.RP08.PXSX._SB.PCI0.RP09.PXSX], AE_NOT_FOUND >> (20180105/dswload2-194) >> >> [ 0.500001] ACPI Error: AE_NOT_FOUND, During name lookup/catalog >> (20180105/psobject-252) >> >> [ 0.508001] ACPI Error: Method parse/execution failed >> \_SB.PCI0.RP08.PXSX, AE_NOT_FOUND (20180105/psparse-550) >> >> [ 0.517260] ACPI Error: Could not find/resolve named package element: >> V0PR (20180105/dspkginit-384) >> >> [ 0.528021] ACPI Error: Could not find/resolve named package element: >> V0PR (20180105/dspkginit-384) >> >> [ 0.536027] ACPI Error: Could not find/resolve named package element: >> V1PR (20180105/dspkginit-384) >> >> [ 0.548019] ACPI Error: Could not find/resolve named package element: >> V1PR (20180105/dspkginit-384) >> >> [ 0.556027] ACPI Error: Could not find/resolve named package element: >> V2PR (20180105/dspkginit-384) >> >> [ 0.564019] ACPI Error: Could not find/resolve named package element: >> V2PR (20180105/dspkginit-384) >> >> [ 0.572169] ACPI: Executed 57 blocks of module-level executable AML >> code >> >> [ 0.590966] ACPI: Dynamic OEM Table Load: >> >> [ 0.596007] ACPI: SSDT 0xFFFF9CD3B4FF2800 0006B4 (v02 PmRef Cpu0Ist >> 00003000 INTL 20160422) >> >> [ 0.604201] ACPI: Executed 1 blocks of module-level executable AML code >> >> [ 0.612069] ACPI: \_PR_.PR00: _OSC native thermal LVT Acked >> >> [ 0.617111] ACPI: Dynamic OEM Table Load: >> >> [ 0.620005] ACPI: SSDT 0xFFFF9CD3B4A9D000 0003FF (v02 PmRef Cpu0Cst >> 00003001 INTL 20160422) >> >> [ 0.632188] ACPI: Executed 1 blocks of module-level executable AML code >> >> [ 0.636136] ACPI: Dynamic OEM Table Load: >> >> [ 0.640004] ACPI: SSDT 0xFFFF9CD3B4AB03C0 0000BA (v02 PmRef Cpu0Hwp >> 00003000 INTL 20160422) >> >> [ 0.648165] ACPI: Executed 1 blocks of module-level executable AML code >> >> [ 0.656099] ACPI: Dynamic OEM Table Load: >> >> [ 0.660004] ACPI: SSDT 0xFFFF9CD3B4FF3000 000628 (v02 PmRef HwpLvt >> 00003000 INTL 20160422) >> >> [ 0.668161] ACPI: Executed 1 blocks of module-level executable AML code >> >> [ 0.676385] ACPI: Dynamic OEM Table Load: >> >> [ 0.680007] ACPI: SSDT 0xFFFF9CD3B49F0000 000D14 (v02 PmRef ApIst >> 00003000 INTL 20160422) >> >> [ 0.688622] ACPI: Executed 1 blocks of module-level executable AML code >> >> [ 0.696138] ACPI: Dynamic OEM Table Load: >> >> [ 0.700004] ACPI: SSDT 0xFFFF9CD3B4A9D800 000317 (v02 PmRef ApHwp >> 00003000 INTL 20160422) >> >> [ 0.708216] ACPI: Executed 1 blocks of module-level executable AML code >> >> [ 0.716144] ACPI: Dynamic OEM Table Load: >> >> [ 0.720004] ACPI: SSDT 0xFFFF9CD3B4A9DC00 00030A (v02 PmRef ApCst >> 00003000 INTL 20160422) >> >> [ 0.728214] ACPI: Executed 1 blocks of module-level executable AML code >> >> [ 0.737417] ACPI: EC: EC started >> >> [ 0.740001] ACPI: EC: interrupt blocked >> >> [ 0.743874] ACPI: \_SB_.PCI0.LPCB.H_EC: Used as first EC >> >> [ 0.748002] ACPI: \_SB_.PCI0.LPCB.H_EC: GPE=0x20, EC_CMD/EC_SC=0x66, >> EC_DATA=0x62 >> >> [ 0.756002] ACPI: \_SB_.PCI0.LPCB.H_EC: Used as boot DSDT EC to handle >> transactions >> >> [ 0.764001] ACPI: Interpreter enabled >> >> [ 0.767714] ACPI: (supports S0 S3 S4 S5) >> >> [ 0.772001] ACPI: Using IOAPIC for interrupt routing >> >> [ 0.776034] PCI: Using host bridge windows from ACPI; if necessary, >> use "pci=nocrs" and report a bug >> >> [ 0.788809] ACPI: Enabled 7 GPEs in block 00 to 7F >> >> [ 0.796202] ACPI: Power Resource [PXP] (off) >> >> [ 0.802193] ACPI: Power Resource [PXP] (off) >> >> [ 0.809854] ACPI: Power Resource [PXP] (off) >> >> [ 0.817042] ACPI: Power Resource [USBC] (on) >> >> [ 0.824155] ACPI: Power Resource [PAUD] (on) >> >> [ 0.828459] ACPI: Power Resource [V0PR] (on) >> >> [ 0.832047] ACPI: Power Resource [V1PR] (on) >> >> [ 0.836044] ACPI: Power Resource [V2PR] (on) >> >> [ 0.842676] ACPI: Power Resource [PXTC] (off) >> >> [ 0.854435] ACPI: Power Resource [FN00] (off) >> >> [ 0.856086] ACPI: Power Resource [FN01] (off) >> >> [ 0.864077] ACPI: Power Resource [FN02] (off) >> >> [ 0.868077] ACPI: Power Resource [FN03] (off) >> >> [ 0.872075] ACPI: Power Resource [FN04] (off) >> >> [ 0.877116] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-fe]) >> >> [ 0.884006] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM >> ClockPM Segments MSI] >> >> [ 0.892155] acpi PNP0A08:00: _OSC: platform does not support >> [PCIeHotplug PME] >> >> [ 0.900145] acpi PNP0A08:00: _OSC: OS now controls [AER PCIeCapability] >> >> [ 0.904002] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using >> BIOS configuration >> >> [ 0.912635] PCI host bridge to bus 0000:00 >> >> [ 0.920003] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7 >> window] >> >> [ 0.924002] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff >> window] >> >> [ 0.932002] pci_bus 0000:00: root bus resource [mem >> 0x000a0000-0x000bffff window] >> >> [ 0.940001] pci_bus 0000:00: root bus resource [mem >> 0x000c0000-0x000c3fff window] >> >> [ 0.948001] pci_bus 0000:00: root bus resource [mem >> 0x000c4000-0x000c7fff window] >> >> [ 0.956001] pci_bus 0000:00: root bus resource [mem >> 0x000c8000-0x000cbfff window] >> >> [ 0.964002] pci_bus 0000:00: root bus resource [mem >> 0x000cc000-0x000cffff window] >> >> [ 0.968001] pci_bus 0000:00: root bus resource [mem >> 0x000d0000-0x000d3fff window] >> >> [ 0.976001] pci_bus 0000:00: root bus resource [mem >> 0x000d4000-0x000d7fff window] >> >> [ 0.984002] pci_bus 0000:00: root bus resource [mem >> 0x000d8000-0x000dbfff window] >> >> [ 0.992001] pci_bus 0000:00: root bus resource [mem >> 0x000dc000-0x000dffff window] >> >> [ 1.000001] pci_bus 0000:00: root bus resource [mem >> 0x000e0000-0x000e3fff window] >> >> [ 1.008001] pci_bus 0000:00: root bus resource [mem >> 0x000e4000-0x000e7fff window] >> >> [ 1.016001] pci_bus 0000:00: root bus resource [mem >> 0x000e8000-0x000ebfff window] >> >> [ 1.024001] pci_bus 0000:00: root bus resource [mem >> 0x000ec000-0x000effff window] >> >> [ 1.028001] pci_bus 0000:00: root bus resource [mem >> 0x9d000000-0xdfffffff window] >> >> [ 1.036001] pci_bus 0000:00: root bus resource [mem >> 0x2000000000-0x2fffffffff window] >> >> [ 1.044001] pci_bus 0000:00: root bus resource [mem >> 0xfd000000-0xfe7fffff window] >> >> [ 1.052002] pci_bus 0000:00: root bus resource [bus 00-fe] >> >> [ 1.056009] pci 0000:00:00.0: [8086:5904] type 00 class 0x060000 >> >> [ 1.064303] pci 0000:00:02.0: [8086:5916] type 00 class 0x030000 >> >> [ 1.072013] pci 0000:00:02.0: reg 0x10: [mem 0x2ffe000000-0x2ffeffffff >> 64bit] >> >> [ 1.076007] pci 0000:00:02.0: reg 0x18: [mem 0x2e00000000-0x2effffffff >> 64bit pref] >> >> [ 1.084005] pci 0000:00:02.0: reg 0x20: [io 0xf000-0xf03f] >> >> [ 1.092161] pci 0000:00:08.0: [8086:1911] type 00 class 0x088000 >> >> [ 1.096015] pci 0000:00:08.0: reg 0x10: [mem 0x2fff027000-0x2fff027fff >> 64bit] >> >> [ 1.104156] pci 0000:00:14.0: [8086:9d2f] type 00 class 0x0c0330 >> >> [ 1.112025] pci 0000:00:14.0: reg 0x10: [mem 0x2fff010000-0x2fff01ffff >> 64bit] >> >> [ 1.116073] pci 0000:00:14.0: PME# supported from D3hot D3cold >> >> [ 1.124187] pci 0000:00:14.2: [8086:9d31] type 00 class 0x118000 >> >> [ 1.128024] pci 0000:00:14.2: reg 0x10: [mem 0x2fff026000-0x2fff026fff >> 64bit] >> >> [ 1.136255] pci 0000:00:15.0: [8086:9d60] type 00 class 0x118000 >> >> [ 1.144263] pci 0000:00:15.0: reg 0x10: [mem 0xdff2a000-0xdff2afff >> 64bit] >> >> [ 1.152962] pci 0000:00:15.1: [8086:9d61] type 00 class 0x118000 >> >> [ 1.156262] pci 0000:00:15.1: reg 0x10: [mem 0xdff29000-0xdff29fff >> 64bit] >> >> [ 1.164897] pci 0000:00:16.0: [8086:9d3a] type 00 class 0x078000 >> >> [ 1.172029] pci 0000:00:16.0: reg 0x10: [mem 0x2fff025000-0x2fff025fff >> 64bit] >> >> [ 1.180079] pci 0000:00:16.0: PME# supported from D3hot >> >> [ 1.184162] pci 0000:00:16.3: [8086:9d3d] type 00 class 0x070002 >> >> [ 1.188018] pci 0000:00:16.3: reg 0x10: [io 0xf0a0-0xf0a7] >> >> [ 1.196007] pci 0000:00:16.3: reg 0x14: [mem 0xdff28000-0xdff28fff] >> >> [ 1.200159] pci 0000:00:17.0: [8086:9d03] type 00 class 0x010601 >> >> [ 1.208020] pci 0000:00:17.0: reg 0x10: [mem 0xdff24000-0xdff25fff] >> >> [ 1.216009] pci 0000:00:17.0: reg 0x14: [mem 0xdff27000-0xdff270ff] >> >> [ 1.220009] pci 0000:00:17.0: reg 0x18: [io 0xf090-0xf097] >> >> [ 1.224008] pci 0000:00:17.0: reg 0x1c: [io 0xf080-0xf083] >> >> [ 1.232008] pci 0000:00:17.0: reg 0x20: [io 0xf060-0xf07f] >> >> [ 1.236008] pci 0000:00:17.0: reg 0x24: [mem 0xdff26000-0xdff267ff] >> >> [ 1.244044] pci 0000:00:17.0: PME# supported from D3hot >> >> [ 1.248157] pci 0000:00:1d.0: [8086:9d18] type 01 class 0x060400 >> >> [ 1.256078] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold >> >> [ 1.260187] pci 0000:00:1f.0: [8086:9d4e] type 00 class 0x060100 >> >> [ 1.268235] pci 0000:00:1f.2: [8086:9d21] type 00 class 0x058000 >> >> [ 1.272016] pci 0000:00:1f.2: reg 0x10: [mem 0xdff20000-0xdff23fff] >> >> [ 1.280165] pci 0000:00:1f.3: [8086:9d71] type 00 class 0x040300 >> >> [ 1.288028] pci 0000:00:1f.3: reg 0x10: [mem 0x2fff020000-0x2fff023fff >> 64bit] >> >> [ 1.292027] pci 0000:00:1f.3: reg 0x20: [mem 0x2fff000000-0x2fff00ffff >> 64bit] >> >> [ 1.300050] pci 0000:00:1f.3: PME# supported from D3hot D3cold >> >> [ 1.308211] pci 0000:00:1f.4: [8086:9d23] type 00 class 0x0c0500 >> >> [ 1.312061] pci 0000:00:1f.4: reg 0x10: [mem 0x2fff024000-0x2fff0240ff >> 64bit] >> >> [ 1.320070] pci 0000:00:1f.4: reg 0x20: [io 0xf040-0xf05f] >> >> [ 1.324196] pci 0000:00:1f.6: [8086:156f] type 00 class 0x020000 >> >> [ 1.332027] pci 0000:00:1f.6: reg 0x10: [mem 0xdff00000-0xdff1ffff] >> >> [ 1.336104] pci 0000:00:1f.6: PME# supported from D0 D3hot D3cold >> >> [ 1.344200] pci 0000:01:00.0: [144d:a804] type 00 class 0x010802 >> >> [ 1.352032] pci 0000:01:00.0: reg 0x10: [mem 0xdfe00000-0xdfe03fff >> 64bit] >> >> [ 1.368069] pci 0000:00:1d.0: PCI bridge to [bus 01] >> >> [ 1.376005] pci 0000:00:1d.0: bridge window [mem >> 0xdfe00000-0xdfefffff] >> >> [ 1.382042] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 >> 15) >> >> [ 1.392046] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *10 11 12 14 >> 15) >> >> [ 1.396043] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 10 *11 12 14 >> 15) >> >> [ 1.404043] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 >> 15) >> >> [ 1.412043] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 10 *11 12 14 >> 15) >> >> [ 1.416043] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 *11 12 14 >> 15) >> >> [ 1.424043] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 *11 12 14 >> 15) >> >> [ 1.432042] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 10 *11 12 14 >> 15) >> >> [ 1.440638] ACPI: EC: interrupt unblocked >> >> [ 1.444015] ACPI: EC: event unblocked >> >> [ 1.447705] ACPI: \_SB_.PCI0.LPCB.H_EC: GPE=0x20, EC_CMD/EC_SC=0x66, >> EC_DATA=0x62 >> >> [ 1.456002] ACPI: \_SB_.PCI0.LPCB.H_EC: Used as boot DSDT EC to handle >> transactions and events >> >> [ 1.464063] pci 0000:00:02.0: vgaarb: setting as boot VGA device >> >> [ 1.468000] pci 0000:00:02.0: vgaarb: VGA device added: >> decodes=io+mem,owns=io+mem,locks=none >> >> [ 1.476003] pci 0000:00:02.0: vgaarb: bridge control possible >> >> [ 1.484001] vgaarb: loaded >> >> [ 1.486847] SCSI subsystem initialized >> >> [ 1.492015] libata version 3.00 loaded. >> >> [ 1.495872] ACPI: bus type USB registered >> >> [ 1.500012] usbcore: registered new interface driver usbfs >> >> [ 1.504006] usbcore: registered new interface driver hub >> >> [ 1.508012] usbcore: registered new device driver usb >> >> [ 1.512019] pps_core: LinuxPPS API ver. 1 registered >> >> [ 1.520001] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 >> Rodolfo Giometti <giometti(a)linux.it> >> >> [ 1.528003] PTP clock support registered >> >> [ 1.532010] EDAC MC: Ver: 3.0.0 >> >> [ 1.536112] Registered efivars operations >> >> [ 1.558075] PCI: Using ACPI for IRQ routing >> >> [ 1.588180] PCI: pci_cache_line_size set to 64 bytes >> >> [ 1.596098] e820: reserve RAM buffer [mem 0x00058000-0x0005ffff] >> >> [ 1.600001] e820: reserve RAM buffer [mem 0x0009e000-0x0009ffff] >> >> [ 1.608001] e820: reserve RAM buffer [mem 0x89e5f000-0x8bffffff] >> >> [ 1.612001] e820: reserve RAM buffer [mem 0x8f58d000-0x8fffffff] >> >> [ 1.620002] e820: reserve RAM buffer [mem 0x861000000-0x863ffffff] >> >> [ 1.624074] NetLabel: Initializing >> >> [ 1.627490] NetLabel: domain hash size = 128 >> >> [ 1.632001] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO >> >> [ 1.640012] NetLabel: unlabeled traffic allowed by default >> >> [ 1.644125] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0 >> >> [ 1.648002] hpet0: 8 comparators, 64-bit 24.000000 MHz counter >> >> [ 1.654038] clocksource: Switched to clocksource tsc-early >> >> [ 1.665041] VFS: Disk quotas dquot_6.6.0 >> >> [ 1.668995] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 >> bytes) >> >> [ 1.675968] AppArmor: AppArmor Filesystem Enabled >> >> [ 1.680711] pnp: PnP ACPI init >> >> [ 1.684088] system 00:00: [io 0x0a00-0x0a1f] has been reserved >> >> [ 1.690032] system 00:00: [io 0x0a20-0x0a2f] has been reserved >> >> [ 1.695974] system 00:00: [io 0x0a30-0x0a3f] has been reserved >> >> [ 1.701918] system 00:00: [io 0x0a40-0x0a4f] has been reserved >> >> [ 1.707862] system 00:00: [io 0x0a50-0x0a5f] has been reserved >> >> [ 1.713803] system 00:00: [io 0x0a60-0x0a6f] has been reserved >> >> [ 1.719749] system 00:00: Plug and Play ACPI device, IDs PNP0c02 >> (active) >> >> [ 1.726768] pnp 00:01: [dma 0 disabled] >> >> [ 1.730664] pnp 00:01: Plug and Play ACPI device, IDs PNP0501 (active) >> >> [ 1.737338] system 00:02: [io 0x0680-0x069f] has been reserved >> >> [ 1.743283] system 00:02: [io 0xffff] has been reserved >> >> [ 1.748617] system 00:02: [io 0xffff] has been reserved >> >> [ 1.753949] system 00:02: [io 0xffff] has been reserved >> >> [ 1.759284] system 00:02: [io 0x1800-0x18fe] has been reserved >> >> [ 1.765228] system 00:02: [io 0x164e-0x164f] has been reserved >> >> [ 1.771177] system 00:02: Plug and Play ACPI device, IDs PNP0c02 >> (active) >> >> [ 1.778074] pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active) >> >> [ 1.784656] system 00:04: [io 0x1854-0x1857] has been reserved >> >> [ 1.790603] system 00:04: Plug and Play ACPI device, IDs INT3f0d >> PNP0c02 (active) >> >> [ 1.798326] system 00:05: [mem 0xfed10000-0xfed17fff] has been reserved >> >> [ 1.804969] system 00:05: [mem 0xfed18000-0xfed18fff] has been reserved >> >> [ 1.811610] system 00:05: [mem 0xfed19000-0xfed19fff] has been reserved >> >> [ 1.818249] system 00:05: [mem 0xe0000000-0xefffffff] has been reserved >> >> [ 1.824895] system 00:05: [mem 0xfed20000-0xfed3ffff] has been reserved >> >> [ 1.831547] system 00:05: [mem 0xfed90000-0xfed93fff] could not be >> reserved >> >> [ 1.838535] system 00:05: [mem 0xfed45000-0xfed8ffff] has been reserved >> >> [ 1.845176] system 00:05: [mem 0xff000000-0xffffffff] has been reserved >> >> [ 1.851813] system 00:05: [mem 0xfee00000-0xfeefffff] could not be >> reserved >> >> [ 1.858802] system 00:05: [mem 0xdffe0000-0xdfffffff] has been reserved >> >> [ 1.865443] system 00:05: Plug and Play ACPI device, IDs PNP0c02 >> (active) >> >> [ 1.872294] system 00:06: [mem 0xfd000000-0xfdabffff] has been reserved >> >> [ 1.878935] system 00:06: [mem 0xfdad0000-0xfdadffff] has been reserved >> >> [ 1.885573] system 00:06: [mem 0xfdb00000-0xfdffffff] has been reserved >> >> [ 1.892211] system 00:06: [mem 0xfe000000-0xfe01ffff] could not be >> reserved >> >> [ 1.899201] system 00:06: [mem 0xfe036000-0xfe03bfff] has been reserved >> >> [ 1.905840] system 00:06: [mem 0xfe03d000-0xfe3fffff] has been reserved >> >> [ 1.912478] system 00:06: [mem 0xfe410000-0xfe7fffff] has been reserved >> >> [ 1.919118] system 00:06: Plug and Play ACPI device, IDs PNP0c02 >> (active) >> >> [ 1.926183] system 00:07: [io 0xff00-0xfffe] has been reserved >> >> [ 1.932128] system 00:07: Plug and Play ACPI device, IDs PNP0c02 >> (active) >> >> [ 1.939850] system 00:08: [mem 0xfe029000-0xfe029fff] has been reserved >> >> [ 1.946491] system 00:08: [mem 0xfe028000-0xfe028fff] has been reserved >> >> [ 1.953132] system 00:08: Plug and Play ACPI device, IDs PNP0c02 >> (active) >> >> [ 1.960793] pnp: PnP ACPI: found 9 devices >> >> [ 1.970405] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, >> max_idle_ns: 2085701024 ns >> >> [ 1.979319] pci 0000:00:1d.0: PCI bridge to [bus 01] >> >> [ 1.984308] pci 0000:00:1d.0: bridge window [mem >> 0xdfe00000-0xdfefffff] >> >> [ 1.991127] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7 window] >> >> [ 1.997331] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff window] >> >> [ 2.003536] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff >> window] >> >> [ 2.010437] pci_bus 0000:00: resource 7 [mem 0x000c0000-0x000c3fff >> window] >> >> [ 2.017339] pci_bus 0000:00: resource 8 [mem 0x000c4000-0x000c7fff >> window] >> >> [ 2.024240] pci_bus 0000:00: resource 9 [mem 0x000c8000-0x000cbfff >> window] >> >> [ 2.031142] pci_bus 0000:00: resource 10 [mem 0x000cc000-0x000cffff >> window] >> >> [ 2.038127] pci_bus 0000:00: resource 11 [mem 0x000d0000-0x000d3fff >> window] >> >> [ 2.045116] pci_bus 0000:00: resource 12 [mem 0x000d4000-0x000d7fff >> window] >> >> [ 2.052104] pci_bus 0000:00: resource 13 [mem 0x000d8000-0x000dbfff >> window] >> >> [ 2.059089] pci_bus 0000:00: resource 14 [mem 0x000dc000-0x000dffff >> window] >> >> [ 2.066074] pci_bus 0000:00: resource 15 [mem 0x000e0000-0x000e3fff >> window] >> >> [ 2.073060] pci_bus 0000:00: resource 16 [mem 0x000e4000-0x000e7fff >> window] >> >> [ 2.080048] pci_bus 0000:00: resource 17 [mem 0x000e8000-0x000ebfff >> window] >> >> [ 2.087035] pci_bus 0000:00: resource 18 [mem 0x000ec000-0x000effff >> window] >> >> [ 2.094022] pci_bus 0000:00: resource 19 [mem 0x9d000000-0xdfffffff >> window] >> >> [ 2.101011] pci_bus 0000:00: resource 20 [mem >> 0x2000000000-0x2fffffffff window] >> >> [ 2.108348] pci_bus 0000:00: resource 21 [mem 0xfd000000-0xfe7fffff >> window] >> >> [ 2.115337] pci_bus 0000:01: resource 1 [mem 0xdfe00000-0xdfefffff] >> >> [ 2.121743] NET: Registered protocol family 2 >> >> [ 2.126248] tcp_listen_portaddr_hash hash table entries: 16384 (order: >> 6, 262144 bytes) >> >> [ 2.134368] TCP established hash table entries: 262144 (order: 9, >> 2097152 bytes) >> >> [ 2.142100] TCP bind hash table entries: 65536 (order: 8, 1048576 >> bytes) >> >> [ 2.148938] TCP: Hash tables configured (established 262144 bind 65536) >> >> [ 2.155612] UDP hash table entries: 16384 (order: 7, 524288 bytes) >> >> [ 2.161891] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes) >> >> [ 2.168614] NET: Registered protocol family 1 >> >> [ 2.173016] pci 0000:00:02.0: Video device with shadowed ROM at [mem >> 0x000c0000-0x000dffff] >> >> [ 2.181659] PCI: CLS 64 bytes, default 64 >> >> [ 2.185716] Unpacking initramfs... >> >> [ 2.869487] Freeing initrd memory: 44068K >> >> [ 2.873575] DMAR: ACPI device "device:71" under DMAR at fed91000 as >> 00:15.0 >> >> [ 2.880566] DMAR: ACPI device "device:72" under DMAR at fed91000 as >> 00:15.1 >> >> [ 2.887585] DMAR: No ATSR found >> >> [ 2.890774] DMAR: dmar0: Using Queued invalidation >> >> [ 2.895667] dmar0: Allocated order 8 PASID table. >> >> [ 2.900470] DMAR: dmar1: Using Queued invalidation >> >> [ 2.905403] DMAR: Setting RMRR: >> >> [ 2.908597] DMAR: Setting identity map for device 0000:00:02.0 >> [0x98800000 - 0x9cffffff] >> >> [ 2.916767] DMAR: Setting identity map for device 0000:00:14.0 >> [0x8f99e000 - 0x8f9bdfff] >> >> [ 2.924896] DMAR: Prepare 0-16MiB unity mapping for LPC >> >> [ 2.930173] DMAR: Setting identity map for device 0000:00:1f.0 [0x0 - >> 0xffffff] >> >> [ 2.937703] DMAR: Intel(R) Virtualization Technology for Directed I/O >> >> [ 2.944208] iommu: Adding device 0000:00:00.0 to group 0 >> >> [ 2.949548] iommu: Adding device 0000:00:02.0 to group 1 >> >> [ 2.954888] iommu: Adding device 0000:00:08.0 to group 2 >> >> [ 2.960229] iommu: Adding device 0000:00:14.0 to group 3 >> >> [ 2.965568] iommu: Adding device 0000:00:14.2 to group 3 >> >> [ 2.970910] iommu: Adding device 0000:00:15.0 to group 4 >> >> [ 2.976246] iommu: Adding device 0000:00:15.1 to group 4 >> >> [ 2.981588] iommu: Adding device 0000:00:16.0 to group 5 >> >> [ 2.986924] iommu: Adding device 0000:00:16.3 to group 5 >> >> [ 2.992260] iommu: Adding device 0000:00:17.0 to group 6 >> >> [ 2.997607] iommu: Adding device 0000:00:1d.0 to group 7 >> >> [ 3.002957] iommu: Adding device 0000:00:1f.0 to group 8 >> >> [ 3.008295] iommu: Adding device 0000:00:1f.2 to group 8 >> >> [ 3.013633] iommu: Adding device 0000:00:1f.3 to group 8 >> >> [ 3.018971] iommu: Adding device 0000:00:1f.4 to group 8 >> >> [ 3.024307] iommu: Adding device 0000:00:1f.6 to group 8 >> >> [ 3.029646] iommu: Adding device 0000:01:00.0 to group 7 >> >> [ 3.036286] RAPL PMU: API unit is 2^-32 Joules, 5 fixed counters, >> 655360 ms ovfl timer >> >> [ 3.044233] RAPL PMU: hw unit of domain pp0-core 2^-14 Joules >> >> [ 3.050001] RAPL PMU: hw unit of domain package 2^-14 Joules >> >> [ 3.055684] RAPL PMU: hw unit of domain dram 2^-14 Joules >> >> [ 3.061104] RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules >> >> [ 3.066787] RAPL PMU: hw unit of domain psys 2^-14 Joules >> >> [ 3.072263] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: >> 0x2717868ea45, max_idle_ns: 440795316085 ns >> >> [ 3.082307] clocksource: Switched to clocksource tsc >> >> [ 3.087343] Scanning for low memory corruption every 60 seconds >> >> [ 3.093844] Initialise system trusted keyrings >> >> [ 3.098314] Key type blacklist registered >> >> [ 3.102365] workingset: timestamp_bits=40 max_order=23 bucket_order=0 >> >> [ 3.109749] zbud: loaded >> >> [ 3.112701] squashfs: version 4.0 (2009/01/31) Phillip Lougher >> >> [ 3.118667] fuse init (API version 7.26) >> >> [ 3.122950] Key type asymmetric registered >> >> [ 3.127069] Asymmetric key parser 'x509' registered >> >> [ 3.131999] Block layer SCSI generic (bsg) driver version 0.4 loaded >> (major 245) >> >> [ 3.139446] io scheduler noop registered >> >> [ 3.143389] io scheduler deadline registered (default) >> >> [ 3.148580] io scheduler cfq registered >> >> [ 3.152433] io scheduler mq-deadline registered (default) >> >> [ 3.157855] io scheduler kyber registered >> >> [ 3.162183] pcieport 0000:00:1d.0: AER enabled with IRQ 123 >> >> [ 3.167810] efifb: invalid framebuffer address >> >> [ 3.172278] intel_idle: MWAIT substates: 0x11142120 >> >> [ 3.177178] intel_idle: v0.4.1 model 0x8E >> >> [ 3.181342] intel_idle: lapic_timer_reliable_states 0xffffffff >> >> [ 3.187317] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS: >> 00/PNP0C0E:00/input/input0 >> >> [ 3.195705] ACPI: Sleep Button [SLPB] >> >> [ 3.199411] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS: >> 00/PNP0C0C:00/input/input1 >> >> [ 3.207797] ACPI: Power Button [PWRB] >> >> [ 3.211505] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN: >> 00/input/input2 >> >> [ 3.218973] ACPI: Power Button [PWRF] >> >> [ 3.340286] thermal LNXTHERM:00: registered as thermal_zone0 >> >> [ 3.345973] ACPI: Thermal Zone [TZ00] (28 C) >> >> [ 3.350413] thermal LNXTHERM:01: registered as thermal_zone1 >> >> [ 3.356098] ACPI: Thermal Zone [TZ01] (30 C) >> >> [ 3.360557] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled >> >> [ 3.387952] 00:01: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is >> a 16550A >> >> [ 3.396070] serial 0000:00:16.3: enabling device (0000 -> 0003) >> >> [ 3.422353] 0000:00:16.3: ttyS4 at I/O 0xf0a0 (irq = 19, base_baud = >> 115200) is a 16550A >> >> [ 3.430694] Linux agpgart interface v0.103 >> >> [ 3.444239] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0x1A, rev-id 16) >> >> [ 3.502589] loop: module loaded >> >> [ 3.506133] nvme nvme0: pci function 0000:01:00.0 >> >> [ 3.510934] libphy: Fixed MDIO Bus: probed >> >> [ 3.515052] tun: Universal TUN/TAP device driver, 1.6 >> >> [ 3.520210] PPP generic driver version 2.4.2 >> >> [ 3.524544] VFIO - User Level meta-driver version: 0.3 >> >> [ 3.529757] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver >> >> [ 3.536313] ehci-pci: EHCI PCI platform driver >> >> [ 3.540782] ehci-platform: EHCI generic platform driver >> >> [ 3.546035] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver >> >> [ 3.552242] ohci-pci: OHCI PCI platform driver >> >> [ 3.556709] ohci-platform: OHCI generic platform driver >> >> [ 3.561958] uhci_hcd: USB Universal Host Controller Interface driver >> >> [ 3.568475] xhci_hcd 0000:00:14.0: xHCI Host Controller >> >> [ 3.573725] xhci_hcd 0000:00:14.0: new USB bus registered, assigned >> bus number 1 >> >> [ 3.582238] xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version >> 0x100 quirks 0x00109810 >> >> [ 3.590710] xhci_hcd 0000:00:14.0: cache line size of 64 is not >> supported >> >> [ 3.597639] usb usb1: New USB device found, idVendor=1d6b, >> idProduct=0002 >> >> [ 3.604456] usb usb1: New USB device strings: Mfr=3, Product=2, >> SerialNumber=1 >> >> [ 3.611705] usb usb1: Product: xHCI Host Controller >> >> [ 3.616602] usb usb1: Manufacturer: Linux 4.16.0-rc5+ xhci-hcd >> >> [ 3.622456] usb usb1: SerialNumber: 0000:00:14.0 >> >> [ 3.627187] hub 1-0:1.0: USB hub found >> >> [ 3.630968] hub 1-0:1.0: 12 ports detected >> >> [ 3.635867] xhci_hcd 0000:00:14.0: xHCI Host Controller >> >> [ 3.641119] xhci_hcd 0000:00:14.0: new USB bus registered, assigned >> bus number 2 >> >> [ 3.648566] usb usb2: New USB device found, idVendor=1d6b, >> idProduct=0003 >> >> [ 3.655382] usb usb2: New USB device strings: Mfr=3, Product=2, >> SerialNumber=1 >> >> [ 3.662630] usb usb2: Product: xHCI Host Controller >> >> [ 3.667529] usb usb2: Manufacturer: Linux 4.16.0-rc5+ xhci-hcd >> >> [ 3.673384] usb usb2: SerialNumber: 0000:00:14.0 >> >> [ 3.678089] hub 2-0:1.0: USB hub found >> >> [ 3.681867] hub 2-0:1.0: 6 ports detected >> >> [ 3.686466] i8042: PNP: No PS/2 controller found. >> >> [ 3.691194] i8042: Probing ports directly. >> >> [ 4.778246] i8042: No controller found >> >> [ 4.782071] mousedev: PS/2 mouse device common for all mice >> >> [ 4.787786] rtc_cmos 00:03: RTC can wake from S4 >> >> [ 4.792883] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0 >> >> [ 4.799092] rtc_cmos 00:03: alarms up to one month, y3k, 242 bytes >> nvram, hpet irqs >> >> [ 4.806784] i2c /dev entries driver >> >> [ 4.810334] device-mapper: uevent: version 1.0.3 >> >> [ 4.814692] nvme0n1: p1 p2 p3 >> >> [ 4.815085] device-mapper: ioctl: 4.37.0-ioctl (2017-09-20) >> initialised: dm-devel(a)redhat.com >> >> [ 4.826525] intel_pstate: Intel P-state driver initializing >> >> [ 4.832331] intel_pstate: HWP enabled >> >> [ 4.836119] ledtrig-cpu: registered to indicate activity on CPUs >> >> [ 4.842149] EFI Variables Facility v0.08 2004-May-17 >> >> [ 4.867685] NET: Registered protocol family 10 >> >> [ 4.872270] Segment Routing with IPv6 >> >> [ 4.875956] NET: Registered protocol family 17 >> >> [ 4.880428] Key type dns_resolver registered >> >> [ 4.884950] microcode: sig=0x806e9, pf=0x80, revision=0x62 >> >> [ 4.890563] microcode: Microcode Update Driver: v2.2. >> >> [ 4.890570] sched_clock: Marking stable (4890559906, 0)->(4874287121, >> 16272785) >> >> [ 4.903132] registered taskstats version 1 >> >> [ 4.907253] Loading compiled-in X.509 certificates >> >> [ 4.913982] Loaded X.509 cert 'Build time autogenerated kernel key: >> 306c974dc2e293db635f47bb5075af350f660b5a' >> >> [ 4.923964] zswap: loaded using pool lzo/zbud >> >> [ 4.929286] Key type trusted registered >> >> [ 4.934030] Key type encrypted registered >> >> [ 4.938063] AppArmor: AppArmor sha1 policy hashing enabled >> >> [ 5.060408] evm: HMAC attrs: 0x1 >> >> [ 5.064632] Magic number: 14:872:326 >> >> [ 5.068627] rtc_cmos 00:03: setting system clock to 2018-04-06 >> 11:18:38 UTC (1523013518) >> >> [ 5.076855] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found >> >> [ 5.082892] EDD information not available. >> >> [ 5.088312] Freeing unused kernel memory: 1692K >> >> [ 5.092870] Write protecting the kernel read-only data: 18432k >> >> [ 5.099046] Freeing unused kernel memory: 2008K >> >> [ 5.103806] Freeing unused kernel memory: 168K >> >> [ 5.169033] ahci 0000:00:17.0: version 3.0 >> >> [ 5.173672] ahci 0000:00:17.0: AHCI 0001.0301 32 slots 1 ports 6 Gbps >> 0x1 impl SATA mode >> >> [ 5.181807] ahci 0000:00:17.0: flags: 64bit ncq pm led clo only pio >> slum part deso sadm sds apst >> >> [ 5.191100] scsi host0: ahci >> >> [ 5.194075] ata1: SATA max UDMA/133 abar m2048@0xdff26000 port >> 0xdff26100 irq 129 >> >> [ 5.202467] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k >> >> [ 5.208338] e1000e: Copyright(c) 1999 - 2015 Intel Corporation. >> >> [ 5.214569] e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) >> set to dynamic conservative mode >> >> [ 5.223965] cryptd: max_cpu_qlen set to 1000 >> >> [ 5.234053] AVX2 version of gcm_enc/dec engaged. >> >> [ 5.238694] AES CTR mode by8 optimization enabled >> >> [ 5.313813] e1000e 0000:00:1f.6 0000:00:1f.6 (uninitialized): >> registered PHC clock >> >> [ 5.406173] e1000e 0000:00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) >> d4:5d:df:00:e4:6e >> >> [ 5.414131] e1000e 0000:00:1f.6 eth0: Intel(R) PRO/1000 Network >> Connection >> >> [ 5.421094] e1000e 0000:00:1f.6 eth0: MAC: 12, PHY: 12, PBA No: >> FFFFFF-0FF >> >> [ 5.518897] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) >> >> [ 5.525929] ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) >> succeeded >> >> [ 5.532929] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE >> LOCK) filtered out >> >> [ 5.540877] ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE >> CONFIGURATION OVERLAY) filtered out >> >> [ 5.549876] ata1.00: supports DRM functions and may not be fully >> accessible >> >> [ 5.558029] ata1.00: ATA-10: Crucial_CT2050MX300SSD1, M0CR060, max >> UDMA/133 >> >> [ 5.565115] ata1.00: 4004704368 sectors, multi 16: LBA48 NCQ (depth >> 31/32), AA >> >> [ 5.575799] ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) >> succeeded >> >> [ 5.582802] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE >> LOCK) filtered out >> >> [ 5.590751] ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE >> CONFIGURATION OVERLAY) filtered out >> >> [ 5.599747] ata1.00: supports DRM functions and may not be fully >> accessible >> >> [ 5.610328] ata1.00: configured for UDMA/133 >> >> [ 5.614818] scsi 0:0:0:0: Direct-Access ATA Crucial_CT2050MX >> R060 PQ: 0 ANSI: 5 >> >> [ 5.623075] ata1.00: Enabling discard_zeroes_data >> >> [ 5.623076] sd 0:0:0:0: Attached scsi generic sg0 type 0 >> >> [ 5.633165] sd 0:0:0:0: [sda] 4004704368 512-byte logical blocks: >> (2.05 TB/1.86 TiB) >> >> [ 5.640945] sd 0:0:0:0: [sda] Write Protect is off >> >> [ 5.645758] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 >> >> [ 5.650836] sd 0:0:0:0: [sda] Write cache: enabled, read cache: >> enabled, doesn't support DPO or FUA >> >> [ 5.659975] ata1.00: Enabling discard_zeroes_data >> >> [ 5.666049] sda: sda1 >> >> [ 5.668535] ata1.00: Enabling discard_zeroes_data >> >> [ 5.673304] sd 0:0:0:0: [sda] Attached SCSI disk >> >> [ 6.844033] raid6: sse2x1 gen() 12408 MB/s >> >> [ 6.916034] raid6: sse2x1 xor() 9219 MB/s >> >> [ 6.988035] raid6: sse2x2 gen() 15298 MB/s >> >> [ 7.060033] raid6: sse2x2 xor() 10535 MB/s >> >> [ 7.132032] raid6: sse2x4 gen() 17434 MB/s >> >> [ 7.204035] raid6: sse2x4 xor() 11644 MB/s >> >> [ 7.276032] raid6: avx2x1 gen() 24357 MB/s >> >> [ 7.348037] raid6: avx2x1 xor() 17455 MB/s >> >> [ 7.420034] raid6: avx2x2 gen() 27740 MB/s >> >> [ 7.492032] raid6: avx2x2 xor() 19095 MB/s >> >> [ 7.564033] raid6: avx2x4 gen() 30826 MB/s >> >> [ 7.636032] raid6: avx2x4 xor() 21767 MB/s >> >> [ 7.640328] raid6: using algorithm avx2x4 gen() 30826 MB/s >> >> [ 7.645836] raid6: .... xor() 21767 MB/s, rmw enabled >> >> [ 7.650908] raid6: using avx2x2 recovery algorithm >> >> [ 7.656536] xor: automatically using best checksumming function avx >> >> [ 7.664303] async_tx: api initialized (async) >> >> [ 7.717139] Btrfs loaded, crc32c=crc32c-intel >> >> [ 7.769710] EXT4-fs (nvme0n1p2): mounted filesystem with ordered data >> mode. Opts: (null) >> >> [ 7.893926] systemd[1]: systemd 229 running in system mode. (+PAM >> +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP >> +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN) >> >> [ 7.932118] systemd[1]: Detected architecture x86-64. >> >> [ 7.937304] systemd[1]: Set hostname to <vmserver11>. >> >> [ 7.980269] systemd[1]: Listening on Device-mapper event daemon FIFOs. >> >> [ 7.986895] systemd[1]: Listening on udev Kernel Socket. >> >> [ 7.992255] systemd[1]: Listening on /dev/initctl Compatibility Named >> Pipe. >> >> [ 7.999800] systemd[1]: Created slice System Slice. >> >> [ 8.004735] systemd[1]: Started Trigger resolvconf update for networkd >> DNS. >> >> [ 8.011877] systemd[1]: Set up automount Arbitrary Executable File >> Formats File System Automount Point. >> >> [ 8.021329] systemd[1]: Listening on Syslog Socket. >> >> [ 8.040248] EXT4-fs (nvme0n1p2): re-mounted. Opts: >> discard,errors=remount-ro >> >> [ 8.048183] Loading iSCSI transport class v2.0-870. >> >> [ 8.062070] iscsi: registered transport (tcp) >> >> [ 8.082269] systemd-journald[393]: Received request to flush runtime >> journal from PID 1 >> >> [ 8.103947] iscsi: registered transport (iser) >> >> [ 8.196755] shpchp: Standard Hot Plug PCI Controller Driver version: >> 0.4 >> >> [ 8.206281] intel-lpss 0000:00:15.0: enabling device (0000 -> 0002) >> >> [ 8.230810] idma64 idma64.0: Found Intel integrated DMA 64-bit >> >> [ 8.241725] mei_me 0000:00:16.0: enabling device (0000 -> 0002) >> >> [ 8.253115] bridge: filtering via arp/ip/ip6tables is no longer >> available by default. Update your scripts to load br_netfilter if you need >> this. >> >> [ 8.266904] intel-lpss 0000:00:15.1: enabling device (0000 -> 0002) >> >> [ 8.273693] idma64 idma64.1: Found Intel integrated DMA 64-bit >> >> [ 8.285221] intel_rapl: Found RAPL domain package >> >> [ 8.289984] intel_rapl: Found RAPL domain core >> >> [ 8.292478] br0: port 1(eth0) entered blocking state >> >> [ 8.294465] intel_rapl: Found RAPL domain uncore >> >> [ 8.299472] br0: port 1(eth0) entered disabled state >> >> [ 8.304111] intel_rapl: Found RAPL domain dram >> >> [ 8.314589] device eth0 entered promiscuous mode >> >> [ 8.346320] snd_hda_intel 0000:00:1f.3: enabling device (0000 -> 0002) >> >> [ 8.357356] snd_hda_intel 0000:00:1f.3: failed to add i915 component >> master (-19) >> >> [ 8.376236] snd_hda_codec_hdmi hdaudioC0D2: No i915 binding for Intel >> HDMI/DP codec >> >> [ 8.386330] snd_hda_codec_hdmi hdaudioC0D2: No i915 binding for Intel >> HDMI/DP codec >> >> [ 8.394139] Adding 33297404k swap on /dev/nvme0n1p3. Priority:-2 >> extents:1 across:33297404k SSFS >> >> [ 8.404801] input: HDA Intel PCH HDMI/DP,pcm=3 as >> /devices/pci0000:00/0000:00:1f.3/sound/card0/input3 >> >> [ 8.484496] FAT-fs (nvme0n1p1): Volume was not properly unmounted. >> Some data may be corrupt. Please run fsck. >> >> [ 8.524979] EXT4-fs (sda1): mounted filesystem with ordered data mode. >> Opts: discard >> >> [ 8.590918] audit: type=1400 audit(1523013522.015:2): >> apparmor="STATUS" operation="profile_load" profile="unconfined" >> name="/usr/bin/lxc-start" pid=885 comm="apparmor_parser" >> >> [ 8.606562] audit: type=1400 audit(1523013522.015:3): >> apparmor="STATUS" operation="profile_load" profile="unconfined" >> name="lxc-container-default" pid=883 comm="apparmor_parser" >> >> [ 8.623085] audit: type=1400 audit(1523013522.015:4): >> apparmor="STATUS" operation="profile_load" profile="unconfined" >> name="lxc-container-default-cgns" pid=883 comm="apparmor_parser" >> >> [ 8.627479] new mount options do not match the existing superblock, >> will be ignored >> >> [ 8.639400] audit: type=1400 audit(1523013522.015:5): >> apparmor="STATUS" operation="profile_load" profile="unconfined" >> name="lxc-container-default-with-mounting" pid=883 comm="apparmor_parser" >> >> [ 8.639402] audit: type=1400 audit(1523013522.015:6): >> apparmor="STATUS" operation="profile_load" profile="unconfined" >> name="lxc-container-default-with-nesting" pid=883 comm="apparmor_parser" >> >> [ 8.639405] audit: type=1400 audit(1523013522.015:7): >> apparmor="STATUS" operation="profile_load" profile="unconfined" >> name="/usr/lib/snapd/snap-confine" pid=887 comm="apparmor_parser" >> >> [ 8.697617] audit: type=1400 audit(1523013522.015:8): >> apparmor="STATUS" operation="profile_load" profile="unconfined" >> name="/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" >> pid=887 comm="apparmor_parser" >> >> [ 8.716824] audit: type=1400 audit(1523013522.015:9): >> apparmor="STATUS" operation="profile_load" profile="unconfined" >> name="/usr/lib/snapd/snap-confine//snap_update_ns" pid=887 >> comm="apparmor_parser" >> >> [ 8.734627] audit: type=1400 audit(1523013522.035:10): >> apparmor="STATUS" operation="profile_load" profile="unconfined" >> name="/usr/lib/lxd/lxd-bridge-proxy" pid=886 comm="apparmor_parser" >> >> [ 8.751302] audit: type=1400 audit(1523013522.035:11): >> apparmor="STATUS" operation="profile_load" profile="unconfined" >> name="/sbin/dhclient" pid=884 comm="apparmor_parser" >> >> [ 11.462360] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow >> Control: None >> >> [ 11.469929] br0: port 1(eth0) entered blocking state >> >> [ 11.474920] br0: port 1(eth0) entered forwarding state >> >> [ 14.044340] random: crng init done >> >> [ 39.987781] e1000e: eth0 NIC Link is Down >> >> [ 39.991838] br0: port 1(eth0) entered disabled state >> >> [ 43.697800] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow >> Control: None >> >> [ 43.705372] br0: port 1(eth0) entered blocking state >> >> [ 43.710365] br0: port 1(eth0) entered forwarding state >> >> [ 2829.742626] br0: port 2(tap850) entered blocking state >> >> [ 2829.747818] br0: port 2(tap850) entered disabled state >> >> [ 2829.753083] device tap850 entered promiscuous mode >> >> [ 2829.757981] br0: port 2(tap850) entered blocking state >> >> [ 2829.763160] br0: port 2(tap850) entered forwarding state >> >> [ 2829.772486] device tap850 left promiscuous mode >> >> [ 2829.777087] br0: port 2(tap850) entered disabled state >> >> [ 2851.982792] br0: port 2(tap850) entered blocking state >> >> [ 2851.987982] br0: port 2(tap850) entered disabled state >> >> [ 2851.993244] device tap850 entered promiscuous mode >> >> [ 2851.998114] br0: port 2(tap850) entered blocking state >> >> [ 2852.003291] br0: port 2(tap850) entered forwarding state >> >> [ 2852.012381] device tap850 left promiscuous mode >> >> [ 2852.016959] br0: port 2(tap850) entered disabled state >> >> [11225.984501] br0: port 2(tap850) entered blocking state >> >> [11225.989703] br0: port 2(tap850) entered disabled state >> >> [11225.994959] device tap850 entered promiscuous mode >> >> [11225.999830] br0: port 2(tap850) entered blocking state >> >> [11226.005003] br0: port 2(tap850) entered forwarding state >> >> [11226.014104] device tap850 left promiscuous mode >> >> [11226.018683] br0: port 2(tap850) entered disabled state >> >> [11248.330194] br0: port 2(tap850) entered blocking state >> >> [11248.335383] br0: port 2(tap850) entered disabled state >> >> [11248.340627] device tap850 entered promiscuous mode >> >> [11248.345554] br0: port 2(tap850) entered blocking state >> >> [11248.350740] br0: port 2(tap850) entered forwarding state >> >> [13357.191080] device tap850 left promiscuous mode >> >> [13357.195682] br0: port 2(tap850) entered disabled state >> >> [21234.285539] br0: port 2(tap860) entered blocking state >> >> [21234.290738] br0: port 2(tap860) entered disabled state >> >> [21234.296145] device tap860 entered promiscuous mode >> >> [21234.301063] br0: port 2(tap860) entered blocking state >> >> [21234.306255] br0: port 2(tap860) entered forwarding state >> >> [21588.418184] device tap860 left promiscuous mode >> >> [21588.422774] br0: port 2(tap860) entered disabled state >> >> [21916.954733] br0: port 2(tap860) entered blocking state >> >> [21916.959928] br0: port 2(tap860) entered disabled state >> >> [21916.965167] device tap860 entered promiscuous mode >> >> [21916.970059] br0: port 2(tap860) entered blocking state >> >> [21916.975242] br0: port 2(tap860) entered forwarding state >> >> [22574.131714] device tap860 left promiscuous mode >> >> [22574.136294] br0: port 2(tap860) entered disabled state >> >> [22612.095231] br0: port 2(tap860) entered blocking state >> >> [22612.100414] br0: port 2(tap860) entered disabled state >> >> [22612.105654] device tap860 entered promiscuous mode >> >> [22612.110544] br0: port 2(tap860) entered blocking state >> >> [22612.115732] br0: port 2(tap860) entered forwarding state >> >> [22618.748283] perf: interrupt took too long (2511 > 2500), lowering >> kernel.perf_event_max_sample_rate to 79500 >> >> [22797.340399] device tap860 left promiscuous mode >> >> [22797.344977] br0: port 2(tap860) entered disabled state >> >> [22979.672216] br0: port 2(tap860) entered blocking state >> >> [22979.677403] br0: port 2(tap860) entered disabled state >> >> [22979.682701] device tap860 entered promiscuous mode >> >> [22979.687604] br0: port 2(tap860) entered blocking state >> >> [22979.692782] br0: port 2(tap860) entered forwarding state >> >> [23224.628283] device tap860 left promiscuous mode >> >> [23224.632867] br0: port 2(tap860) entered disabled state >> >> [42855.170194] perf: interrupt took too long (3209 > 3138), lowering >> kernel.perf_event_max_sample_rate to 62250 >> >> [116275.181870] perf: interrupt took too long (4048 > 4011), lowering >> kernel.perf_event_max_sample_rate to 49250 >> >> [269613.044329] br0: port 2(tap860) entered blocking state >> >> [269613.049605] br0: port 2(tap860) entered disabled state >> >> [269613.054982] device tap860 entered promiscuous mode >> >> [269613.059987] br0: port 2(tap860) entered blocking state >> >> [269613.065256] br0: port 2(tap860) entered forwarding state >> >> [269936.795013] device tap860 left promiscuous mode >> >> [269936.799706] br0: port 2(tap860) entered disabled state >> >> [270031.079090] br0: port 2(tap860) entered blocking state >> >> [270031.084362] br0: port 2(tap860) entered disabled state >> >> [270031.090121] device tap860 entered promiscuous mode >> >> [270031.095101] br0: port 2(tap860) entered blocking state >> >> [270031.100371] br0: port 2(tap860) entered forwarding state >> >> [270136.913644] device tap860 left promiscuous mode >> >> [270136.918336] br0: port 2(tap860) entered disabled state >> >> [270149.057394] br0: port 2(tap860) entered blocking state >> >> [270149.062667] br0: port 2(tap860) entered disabled state >> >> [270149.068038] device tap860 entered promiscuous mode >> >> [270149.073016] br0: port 2(tap860) entered blocking state >> >> [270149.078283] br0: port 2(tap860) entered forwarding state >> >> [270149.087679] device tap860 left promiscuous mode >> >> [270149.092344] br0: port 2(tap860) entered disabled state >> >> [270168.986861] br0: port 2(tap860) entered blocking state >> >> [270168.992145] br0: port 2(tap860) entered disabled state >> >> [270168.997797] device tap860 entered promiscuous mode >> >> [270169.002780] br0: port 2(tap860) entered blocking state >> >> [270169.008050] br0: port 2(tap860) entered forwarding state >> >> [270261.521461] device tap860 left promiscuous mode >> >> [270261.526158] br0: port 2(tap860) entered disabled state >> >> [270337.305890] br0: port 2(tap860) entered blocking state >> >> [270337.311204] br0: port 2(tap860) entered disabled state >> >> [270337.316590] device tap860 entered promiscuous mode >> >> [270337.321590] br0: port 2(tap860) entered blocking state >> >> [270337.326854] br0: port 2(tap860) entered forwarding state >> >> [271285.081912] device tap860 left promiscuous mode >> >> [271285.086577] br0: port 2(tap860) entered disabled state >> >> [271335.803402] br0: port 2(tap870) entered blocking state >> >> [271335.808753] br0: port 2(tap870) entered disabled state >> >> [271335.814173] device tap870 entered promiscuous mode >> >> [271335.819169] br0: port 2(tap870) entered blocking state >> >> [271335.824445] br0: port 2(tap870) entered forwarding state >> >> [272918.159848] device tap870 left promiscuous mode >> >> [272918.164544] br0: port 2(tap870) entered disabled state >> >> [273424.674490] br0: port 2(tap850) entered blocking state >> >> [273424.679796] br0: port 2(tap850) entered disabled state >> >> [273424.685218] device tap850 entered promiscuous mode >> >> [273424.690212] br0: port 2(tap850) entered blocking state >> >> [273424.695497] br0: port 2(tap850) entered forwarding state >> >> [286852.645616] perf: interrupt took too long (5085 > 5060), lowering >> kernel.perf_event_max_sample_rate to 39250 >> >> [314025.991424] perf: interrupt took too long (6361 > 6356), lowering >> kernel.perf_event_max_sample_rate to 31250 >> >> [351901.019424] br0: port 3(tap860) entered blocking state >> >> [351901.024697] br0: port 3(tap860) entered disabled state >> >> [351901.030385] device tap860 entered promiscuous mode >> >> [351901.035363] br0: port 3(tap860) entered blocking state >> >> [351901.040638] br0: port 3(tap860) entered forwarding state >> >> [354572.376171] br0: port 4(tap870) entered blocking state >> >> [354572.381450] br0: port 4(tap870) entered disabled state >> >> [354572.386779] device tap870 entered promiscuous mode >> >> [354572.391731] br0: port 4(tap870) entered blocking state >> >> [354572.396997] br0: port 4(tap870) entered forwarding state >> >> [398257.417036] perf: interrupt took too long (7955 > 7951), lowering >> kernel.perf_event_max_sample_rate to 25000 >> >> >> >> >> >> Thanks, >> >> Richard >> >> >> >> 2018-04-16 10:16 GMT+02:00 Yuan, Hang <hang.yuan(a)intel.com>: >> >> Id “8086:5916” is a supported device. Could you also copy dmesg log here? >> Need to check if any errors in gvt init procedure. >> >> >> >> Thanks, >> >> Henry >> >> >> >> *From:* Richard Walter [mailto:rw@allgaeudsl.de] >> *Sent:* Monday, April 16, 2018 4:10 PM >> *To:* Yuan, Hang <hang.yuan(a)intel.com>; iGVT-g(a)lists.01.org >> *Subject:* Re: [iGVT-g] Hardware Support Question >> >> >> >> Hi Henry >> >> >> >> lspci -n >> >> >> >> # lspci -n >> >> 00:00.0 0600: 8086:5904 (rev 02) >> >> 00:02.0 0300: 8086:5916 (rev 02) >> >> 00:08.0 0880: 8086:1911 >> >> 00:14.0 0c03: 8086:9d2f (rev 21) >> >> 00:14.2 1180: 8086:9d31 (rev 21) >> >> 00:15.0 1180: 8086:9d60 (rev 21) >> >> 00:15.1 1180: 8086:9d61 (rev 21) >> >> 00:16.0 0780: 8086:9d3a (rev 21) >> >> 00:16.3 0700: 8086:9d3d (rev 21) >> >> 00:17.0 0106: 8086:9d03 (rev 21) >> >> 00:1d.0 0604: 8086:9d18 (rev f1) >> >> 00:1f.0 0601: 8086:9d4e (rev 21) >> >> 00:1f.2 0580: 8086:9d21 (rev 21) >> >> 00:1f.3 0403: 8086:9d71 (rev 21) >> >> 00:1f.4 0c05: 8086:9d23 (rev 21) >> >> 00:1f.6 0200: 8086:156f (rev 21) >> >> 01:00.0 0108: 144d:a804 >> >> >> >> Thanks >> >> Richard >> >> >> >> >> >> 2018-04-16 9:44 GMT+02:00 Yuan, Hang <hang.yuan(a)intel.com>: >> >> What’s the output of ‘lspci -n'? >> >> >> >> Regards, >> >> Henry >> >> >> >> *From:* iGVT-g [mailto:igvt-g-bounces@lists.01.org] *On Behalf Of *Richard >> Walter >> *Sent:* Monday, April 16, 2018 3:09 PM >> *To:* iGVT-g(a)lists.01.org >> *Subject:* [iGVT-g] Hardware Support Question >> >> >> >> Hi list, >> >> >> >> Is it possible to use gvt-g with Intel NUC 7i5DNH? >> >> I followed the gvt-g setup guide on github. >> >> >> >> The guide worked well on a ASUS P9X79 Pro with Intel(R) Core(TM) i7-4930K >> CPU @ 3.40GHz under Debian Strech. >> >> >> >> But with Intel NUC 7i5DNH and Ubuntu 16.04.4 >> >> the command >> >> ll /sys/bus/pci/devices/0000:00:02.0/mdev_supported_types/ >> >> failed with directory not found. >> >> >> >> >> >> cat /proc/cpuinfo | grep "model name" >> >> >> >> model name : Intel(R) Core(TM) i5-7300U CPU @ 2.60GHz >> >> >> >> >> >> lspci >> >> >> >> 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core >> Processor Host Bridge/DRAM Registers (rev 02) >> >> 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev >> 02) >> >> 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 >> v5 / 6th/7th Gen Core Processor Gaussian Mixture Model >> >> >> >> >> >> Is this hardware supported by igvt-g? >> >> >> >> Thanks >> >> >> >> Richard >> >> >> >> >> > > > > _______________________________________________ > iGVT-g mailing listiGVT-g@lists.01.orghttps://lists.01.org/mailman/listinfo/igvt-g > > >

2 years, 10 months

1
0
0 / 0

Hardware support question

by Oliver Rath

Hi list, Im trying to get run gvt-g on a platform which should be supported, but Im not sure. In the documentation https://github.com/intel/gvt-linux/wiki/GVTg_Setup_Guide#22-hardware-requ... I will find: "..on server platforms , E3_v4, E3_v5 or E3_v6 Xeon Processor Graphics is required..". If I now look at my Computer with lspci: 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) There is a Xeon .. v3/4th Gen. On VGA I read "..4th Gen". For me it sounds, E3_v4 (which supports igvt-g) is the 4th Gen of Xeon, but on the bridge stands ..*v3*/4th .. Is this Computer supported by igvt-g? loading mdev and kvmgt gets no result in the sys-path of vga. Tfh! Oliver

2 years, 10 months

2
3
0 / 0

2021

2020

2019

2018

2017

2016

2015

iGVT-g April 2018