Attachment 125363 Details for Bug 97104 – IVB-drv_missed_irq-kern.log

IVB-drv_missed_irq-kern.log

IVB-drv_missed_irq-kern.log (text/plain), 278.09 KB, created by cprigent on 2016-07-28 09:44:02 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: cprigent

Created: 2016-07-28 09:44:02 UTC

Size: 278.09 KB

patch

obsolete

>Jul 29 06:33:18 IVB102 kernel: [    0.000000] Linux version 4.7.0-rc7-nightly+ (jenkins@vanaheimr) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #1 SMP Tue Jul 26 02:02:06 CEST 2016
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.7.0-rc7-nightly+ root=UUID=923347ab-d83e-43a7-88a3-ad3eb8d86663 ro drm.debug=0xe initcall_debug crashkernel=384M-:128M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] KERNEL supported cpus:
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]   Intel GenuineIntel
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]   AMD AuthenticAMD
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]   Centaur CentaurHauls
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] x86/fpu: Using 'eager' FPU context switches.
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009d7ff] usable
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009d800-0x000000000009ffff] reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] BIOS-e820: [mem 0x0000000020000000-0x00000000201fffff] reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] BIOS-e820: [mem 0x0000000020200000-0x0000000040003fff] usable
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] BIOS-e820: [mem 0x0000000040004000-0x0000000040004fff] reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] BIOS-e820: [mem 0x0000000040005000-0x00000000d9cadfff] usable
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] BIOS-e820: [mem 0x00000000d9cae000-0x00000000da2a5fff] reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] BIOS-e820: [mem 0x00000000da2a6000-0x00000000da2b5fff] ACPI data
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] BIOS-e820: [mem 0x00000000da2b6000-0x00000000da3c5fff] ACPI NVS
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] BIOS-e820: [mem 0x00000000da3c6000-0x00000000da69bfff] reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] BIOS-e820: [mem 0x00000000da69c000-0x00000000da69cfff] usable
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] BIOS-e820: [mem 0x00000000da69d000-0x00000000da6dffff] ACPI NVS
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] BIOS-e820: [mem 0x00000000da6e0000-0x00000000daffffff] usable
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] BIOS-e820: [mem 0x00000000db800000-0x00000000df9fffff] reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000081f5fffff] usable
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] NX (Execute Disable) protection: active
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] SMBIOS 2.7 present.
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] DMI:                  /DH77EB, BIOS EBH7710H.86A.0096.2012.1012.1645 10/12/2012
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] e820: last_pfn = 0x81f600 max_arch_pfn = 0x400000000
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] MTRR default type: uncachable
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] MTRR fixed ranges enabled:
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]   00000-9FFFF write-back
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]   A0000-BFFFF uncachable
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]   C0000-CFFFF write-protect
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]   D0000-E7FFF uncachable
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]   E8000-FFFFF write-protect
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] MTRR variable ranges enabled:
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]   0 base 000000000 mask 800000000 write-back
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]   1 base 800000000 mask FE0000000 write-back
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]   2 base 0E0000000 mask FE0000000 uncachable
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]   3 base 0DC000000 mask FFC000000 uncachable
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]   4 base 0DB800000 mask FFF800000 uncachable
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]   5 base 81F800000 mask FFF800000 uncachable
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]   6 base 81F600000 mask FFFE00000 uncachable
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]   7 disabled
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]   8 disabled
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]   9 disabled
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- WT  
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] total RAM covered: 32686M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 64K 	chunk_size: 64K 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 64K 	chunk_size: 128K 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 64K 	chunk_size: 256K 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 64K 	chunk_size: 512K 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 64K 	chunk_size: 1M 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 64K 	chunk_size: 2M 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 64K 	chunk_size: 4M 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 64K 	chunk_size: 8M 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 64K 	chunk_size: 16M 	num_reg: 10  	lose cover RAM: -10M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 64K 	chunk_size: 32M 	num_reg: 10  	lose cover RAM: -10M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 64K 	chunk_size: 64M 	num_reg: 10  	lose cover RAM: -10M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 64K 	chunk_size: 128M 	num_reg: 10  	lose cover RAM: -8M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 64K 	chunk_size: 256M 	num_reg: 10  	lose cover RAM: -8M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 64K 	chunk_size: 512M 	num_reg: 10  	lose cover RAM: -8M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 64K 	chunk_size: 1G 	num_reg: 10  	lose cover RAM: -512M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 64K 	chunk_size: 2G 	num_reg: 10  	lose cover RAM: -1536M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 128K 	chunk_size: 128K 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 128K 	chunk_size: 256K 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 128K 	chunk_size: 512K 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 128K 	chunk_size: 1M 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 128K 	chunk_size: 2M 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 128K 	chunk_size: 4M 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 128K 	chunk_size: 8M 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 128K 	chunk_size: 16M 	num_reg: 10  	lose cover RAM: -10M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 128K 	chunk_size: 32M 	num_reg: 10  	lose cover RAM: -10M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 128K 	chunk_size: 64M 	num_reg: 10  	lose cover RAM: -10M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 128K 	chunk_size: 128M 	num_reg: 10  	lose cover RAM: -8M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 128K 	chunk_size: 256M 	num_reg: 10  	lose cover RAM: -8M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 128K 	chunk_size: 512M 	num_reg: 10  	lose cover RAM: -8M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 128K 	chunk_size: 1G 	num_reg: 10  	lose cover RAM: -512M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 128K 	chunk_size: 2G 	num_reg: 10  	lose cover RAM: -1536M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 256K 	chunk_size: 256K 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 256K 	chunk_size: 512K 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 256K 	chunk_size: 1M 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 256K 	chunk_size: 2M 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 256K 	chunk_size: 4M 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 256K 	chunk_size: 8M 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 256K 	chunk_size: 16M 	num_reg: 10  	lose cover RAM: -10M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 256K 	chunk_size: 32M 	num_reg: 10  	lose cover RAM: -10M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 256K 	chunk_size: 64M 	num_reg: 10  	lose cover RAM: -10M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 256K 	chunk_size: 128M 	num_reg: 10  	lose cover RAM: -8M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 256K 	chunk_size: 256M 	num_reg: 10  	lose cover RAM: -8M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 256K 	chunk_size: 512M 	num_reg: 10  	lose cover RAM: -8M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 256K 	chunk_size: 1G 	num_reg: 10  	lose cover RAM: -512M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 256K 	chunk_size: 2G 	num_reg: 10  	lose cover RAM: -1536M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 512K 	chunk_size: 512K 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 512K 	chunk_size: 1M 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 512K 	chunk_size: 2M 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 512K 	chunk_size: 4M 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 512K 	chunk_size: 8M 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 512K 	chunk_size: 16M 	num_reg: 10  	lose cover RAM: -10M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 512K 	chunk_size: 32M 	num_reg: 10  	lose cover RAM: -10M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 512K 	chunk_size: 64M 	num_reg: 10  	lose cover RAM: -10M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 512K 	chunk_size: 128M 	num_reg: 10  	lose cover RAM: -8M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 512K 	chunk_size: 256M 	num_reg: 10  	lose cover RAM: -8M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 512K 	chunk_size: 512M 	num_reg: 10  	lose cover RAM: -8M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 512K 	chunk_size: 1G 	num_reg: 10  	lose cover RAM: -512M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 512K 	chunk_size: 2G 	num_reg: 10  	lose cover RAM: -1536M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 1M 	chunk_size: 1M 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 1M 	chunk_size: 2M 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 1M 	chunk_size: 4M 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 1M 	chunk_size: 8M 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 1M 	chunk_size: 16M 	num_reg: 10  	lose cover RAM: -10M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 1M 	chunk_size: 32M 	num_reg: 10  	lose cover RAM: -10M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 1M 	chunk_size: 64M 	num_reg: 10  	lose cover RAM: -10M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 1M 	chunk_size: 128M 	num_reg: 10  	lose cover RAM: -8M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 1M 	chunk_size: 256M 	num_reg: 10  	lose cover RAM: -8M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 1M 	chunk_size: 512M 	num_reg: 10  	lose cover RAM: -8M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 1M 	chunk_size: 1G 	num_reg: 10  	lose cover RAM: -512M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 1M 	chunk_size: 2G 	num_reg: 10  	lose cover RAM: -1536M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 2M 	chunk_size: 2M 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 2M 	chunk_size: 4M 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 2M 	chunk_size: 8M 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 2M 	chunk_size: 16M 	num_reg: 10  	lose cover RAM: -10M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 2M 	chunk_size: 32M 	num_reg: 10  	lose cover RAM: -10M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 2M 	chunk_size: 64M 	num_reg: 10  	lose cover RAM: -10M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 2M 	chunk_size: 128M 	num_reg: 10  	lose cover RAM: -8M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 2M 	chunk_size: 256M 	num_reg: 10  	lose cover RAM: -8M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 2M 	chunk_size: 512M 	num_reg: 10  	lose cover RAM: -8M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 2M 	chunk_size: 1G 	num_reg: 10  	lose cover RAM: -512M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 2M 	chunk_size: 2G 	num_reg: 10  	lose cover RAM: -1536M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 4M 	chunk_size: 4M 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 4M 	chunk_size: 8M 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 4M 	chunk_size: 16M 	num_reg: 10  	lose cover RAM: -10M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 4M 	chunk_size: 32M 	num_reg: 10  	lose cover RAM: -10M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 4M 	chunk_size: 64M 	num_reg: 10  	lose cover RAM: -10M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 4M 	chunk_size: 128M 	num_reg: 10  	lose cover RAM: -6M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 4M 	chunk_size: 256M 	num_reg: 10  	lose cover RAM: -6M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 4M 	chunk_size: 512M 	num_reg: 10  	lose cover RAM: -6M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 4M 	chunk_size: 1G 	num_reg: 10  	lose cover RAM: -510M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 4M 	chunk_size: 2G 	num_reg: 10  	lose cover RAM: -1534M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 8M 	chunk_size: 8M 	num_reg: 10  	lose cover RAM: 502M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 8M 	chunk_size: 16M 	num_reg: 10  	lose cover RAM: 246M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 8M 	chunk_size: 32M 	num_reg: 10  	lose cover RAM: -10M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 8M 	chunk_size: 64M 	num_reg: 10  	lose cover RAM: -10M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 8M 	chunk_size: 128M 	num_reg: 10  	lose cover RAM: 6M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 8M 	chunk_size: 256M 	num_reg: 10  	lose cover RAM: 6M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 8M 	chunk_size: 512M 	num_reg: 10  	lose cover RAM: 6M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 8M 	chunk_size: 1G 	num_reg: 10  	lose cover RAM: 6M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 8M 	chunk_size: 2G 	num_reg: 10  	lose cover RAM: -1018M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 16M 	chunk_size: 16M 	num_reg: 10  	lose cover RAM: 254M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 16M 	chunk_size: 32M 	num_reg: 10  	lose cover RAM: -2M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 16M 	chunk_size: 64M 	num_reg: 10  	lose cover RAM: -2M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 16M 	chunk_size: 128M 	num_reg: 10  	lose cover RAM: 14M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 16M 	chunk_size: 256M 	num_reg: 10  	lose cover RAM: 14M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 16M 	chunk_size: 512M 	num_reg: 10  	lose cover RAM: 14M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 16M 	chunk_size: 1G 	num_reg: 10  	lose cover RAM: 14M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 16M 	chunk_size: 2G 	num_reg: 10  	lose cover RAM: -1010M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 32M 	chunk_size: 32M 	num_reg: 10  	lose cover RAM: 142M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 32M 	chunk_size: 64M 	num_reg: 10  	lose cover RAM: 14M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 32M 	chunk_size: 128M 	num_reg: 10  	lose cover RAM: 46M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 32M 	chunk_size: 256M 	num_reg: 10  	lose cover RAM: 46M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 32M 	chunk_size: 512M 	num_reg: 10  	lose cover RAM: 46M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 32M 	chunk_size: 1G 	num_reg: 10  	lose cover RAM: 46M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] *BAD*gran_size: 32M 	chunk_size: 2G 	num_reg: 10  	lose cover RAM: -978M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 64M 	chunk_size: 64M 	num_reg: 10  	lose cover RAM: 110M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 64M 	chunk_size: 128M 	num_reg: 9  	lose cover RAM: 110M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 64M 	chunk_size: 256M 	num_reg: 9  	lose cover RAM: 110M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 64M 	chunk_size: 512M 	num_reg: 9  	lose cover RAM: 110M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 64M 	chunk_size: 1G 	num_reg: 9  	lose cover RAM: 110M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 64M 	chunk_size: 2G 	num_reg: 10  	lose cover RAM: 110M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 128M 	chunk_size: 128M 	num_reg: 9  	lose cover RAM: 174M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 128M 	chunk_size: 256M 	num_reg: 9  	lose cover RAM: 174M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 128M 	chunk_size: 512M 	num_reg: 9  	lose cover RAM: 174M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 128M 	chunk_size: 1G 	num_reg: 9  	lose cover RAM: 174M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 128M 	chunk_size: 2G 	num_reg: 10  	lose cover RAM: 174M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 256M 	chunk_size: 256M 	num_reg: 7  	lose cover RAM: 430M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 256M 	chunk_size: 512M 	num_reg: 9  	lose cover RAM: 430M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 256M 	chunk_size: 1G 	num_reg: 9  	lose cover RAM: 430M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 256M 	chunk_size: 2G 	num_reg: 10  	lose cover RAM: 430M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 512M 	chunk_size: 512M 	num_reg: 5  	lose cover RAM: 942M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 512M 	chunk_size: 1G 	num_reg: 5  	lose cover RAM: 942M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 512M 	chunk_size: 2G 	num_reg: 5  	lose cover RAM: 942M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 1G 	chunk_size: 1G 	num_reg: 5  	lose cover RAM: 942M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 1G 	chunk_size: 2G 	num_reg: 5  	lose cover RAM: 942M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]  gran_size: 2G 	chunk_size: 2G 	num_reg: 4  	lose cover RAM: 1966M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] mtrr_cleanup: can not find optimal value
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] please specify mtrr_gran_size/mtrr_chunk_size
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] e820: update [mem 0xdb800000-0xffffffff] usable ==> reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] e820: last_pfn = 0xdb000 max_arch_pfn = 0x400000000
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd730-0x000fd73f] mapped at [ffff8800000fd730]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] Scanning 1 areas for low memory corruption
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] Base memory trampoline at [ffff880000097000] 97000 size 24576
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] BRK [0x02014000, 0x02014fff] PGTABLE
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] BRK [0x02015000, 0x02015fff] PGTABLE
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] BRK [0x02016000, 0x02016fff] PGTABLE
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] BRK [0x02017000, 0x02017fff] PGTABLE
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] BRK [0x02018000, 0x02018fff] PGTABLE
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] BRK [0x02019000, 0x02019fff] PGTABLE
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] RAMDISK: [mem 0x3372a000-0x35b8cfff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] ACPI: Early table checksum verification disabled
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] ACPI: RSDP 0x00000000000F0490 000024 (v02 INTEL )
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] ACPI: XSDT 0x00000000DA2AA070 000064 (v01 INTEL  DH77EB   00000060 AMI  00010013)
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] ACPI: FACP 0x00000000DA2B4158 00010C (v05 INTEL  DH77EB   00000060 AMI  00010013)
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] ACPI: DSDT 0x00000000DA2AA168 009FE9 (v02 INTEL  DH77EB   00000096 INTL 20051117)
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] ACPI: FACS 0x00000000DA3C4080 000040
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] ACPI: APIC 0x00000000DA2B4268 000092 (v03 INTEL  DH77EB   00000060 AMI  00010013)
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] ACPI: FPDT 0x00000000DA2B4300 000044 (v01 INTEL  DH77EB   00000060 AMI  00010013)
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] ACPI: MCFG 0x00000000DA2B4348 00003C (v01 INTEL  DH77EB   00000060 MSFT 00000097)
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] ACPI: HPET 0x00000000DA2B4388 000038 (v01 INTEL  DH77EB   00000060 AMI. 00000005)
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] ACPI: SSDT 0x00000000DA2B43C0 00036D (v01 SataRe SataTabl 00001000 INTL 20091112)
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] ACPI: SSDT 0x00000000DA2B4730 0009AA (v01 PmRef  Cpu0Ist  00003000 INTL 20051117)
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] ACPI: SSDT 0x00000000DA2B50E0 000A92 (v01 PmRef  CpuPm    00003000 INTL 20051117)
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] No NUMA configuration found
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] Faking a node at [mem 0x0000000000000000-0x000000081f5fffff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] NODE_DATA(0) allocated [mem 0x81f5dc000-0x81f5dffff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] Reserving 128MB of memory at 688MB for crashkernel (System RAM: 32665MB)
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] Zone ranges:
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]   Normal   [mem 0x0000000100000000-0x000000081f5fffff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] Movable zone start for each node
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] Early memory node ranges
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]   node   0: [mem 0x0000000000001000-0x000000000009cfff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]   node   0: [mem 0x0000000000100000-0x000000001fffffff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]   node   0: [mem 0x0000000020200000-0x0000000040003fff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]   node   0: [mem 0x0000000040005000-0x00000000d9cadfff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]   node   0: [mem 0x00000000da69c000-0x00000000da69cfff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]   node   0: [mem 0x00000000da6e0000-0x00000000daffffff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]   node   0: [mem 0x0000000100000000-0x000000081f5fffff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] Initmem setup node 0 [mem 0x0000000000001000-0x000000081f5fffff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] On node 0 totalpages: 8362346
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]   DMA zone: 21 pages reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]   DMA zone: 3996 pages, LIFO batch:0
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]   DMA32 zone: 13904 pages used for memmap
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]   DMA32 zone: 889806 pages, LIFO batch:31
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]   Normal zone: 116696 pages used for memmap
>Jul 29 06:33:18 IVB102 kernel: [    0.000000]   Normal zone: 7468544 pages, LIFO batch:31
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] Reserving Intel graphics memory at 0x00000000dba00000-0x00000000df9fffff
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] ACPI: IRQ0 used by override.
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] ACPI: IRQ9 used by override.
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] smpboot: Allowing 8 CPUs, 0 hotplug CPUs
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009d000-0x0009dfff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009ffff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x20000000-0x201fffff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x40004000-0x40004fff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xd9cae000-0xda2a5fff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xda2a6000-0xda2b5fff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xda2b6000-0xda3c5fff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xda3c6000-0xda69bfff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xda69d000-0xda6dffff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xdb000000-0xdb7fffff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xdb800000-0xdf9fffff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xdfa00000-0xf7ffffff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfc000000-0xfebfffff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfec01000-0xfecfffff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed00000-0xfed03fff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed04000-0xfed1bfff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfedfffff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfee01000-0xfeffffff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] e820: [mem 0xdfa00000-0xf7ffffff] available for PCI devices
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:8 nr_node_ids:1
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] percpu: Embedded 35 pages/cpu @ffff88081f200000 s102744 r8192 d32424 u262144
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] pcpu-alloc: s102744 r8192 d32424 u262144 alloc=1*2097152
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] pcpu-alloc: [0] 0 1 2 3 4 5 6 7 
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] Built 1 zonelists in Node order, mobility grouping on.  Total pages: 8231661
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] Policy zone: Normal
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.7.0-rc7-nightly+ root=UUID=923347ab-d83e-43a7-88a3-ad3eb8d86663 ro drm.debug=0xe initcall_debug crashkernel=384M-:128M
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] Memory: 32672616K/33449384K available (7841K kernel code, 1312K rwdata, 3624K rodata, 1508K init, 1308K bss, 776768K reserved, 0K cma-reserved)
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] Hierarchical RCU implementation.
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] 	Build-time adjustment of leaf fanout to 64.
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=8.
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=8
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:488 16
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-7.
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] Console: colour VGA+ 80x25
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] console [tty0] enabled
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484882848 ns
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] hpet clockevent registered
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
>Jul 29 06:33:18 IVB102 kernel: [    0.000000] tsc: Detected 3500.172 MHz processor
>Jul 29 06:33:18 IVB102 kernel: [    0.000017] Calibrating delay loop (skipped), value calculated using timer frequency.. 7000.34 BogoMIPS (lpj=14000688)
>Jul 29 06:33:18 IVB102 kernel: [    0.000084] pid_max: default: 32768 minimum: 301
>Jul 29 06:33:18 IVB102 kernel: [    0.000119] ACPI: Core revision 20160422
>Jul 29 06:33:18 IVB102 kernel: [    0.004593] ACPI: 4 ACPI AML tables successfully acquired and loaded
>Jul 29 06:33:18 IVB102 kernel: [    0.004645] 
>Jul 29 06:33:18 IVB102 kernel: [    0.004686] Security Framework initialized
>Jul 29 06:33:18 IVB102 kernel: [    0.004719] Yama: becoming mindful.
>Jul 29 06:33:18 IVB102 kernel: [    0.004753] AppArmor: AppArmor initialized
>Jul 29 06:33:18 IVB102 kernel: [    0.005967] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
>Jul 29 06:33:18 IVB102 kernel: [    0.011500] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
>Jul 29 06:33:18 IVB102 kernel: [    0.014032] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
>Jul 29 06:33:18 IVB102 kernel: [    0.014091] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
>Jul 29 06:33:18 IVB102 kernel: [    0.014400] CPU: Physical Processor ID: 0
>Jul 29 06:33:18 IVB102 kernel: [    0.014433] CPU: Processor Core ID: 0
>Jul 29 06:33:18 IVB102 kernel: [    0.014466] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
>Jul 29 06:33:18 IVB102 kernel: [    0.014499] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
>Jul 29 06:33:18 IVB102 kernel: [    0.014536] mce: CPU supports 9 MCE banks
>Jul 29 06:33:18 IVB102 kernel: [    0.014573] CPU0: Thermal monitoring enabled (TM1)
>Jul 29 06:33:18 IVB102 kernel: [    0.014611] process: using mwait in idle threads
>Jul 29 06:33:18 IVB102 kernel: [    0.014647] Last level iTLB entries: 4KB 512, 2MB 8, 4MB 8
>Jul 29 06:33:18 IVB102 kernel: [    0.014679] Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32, 1GB 0
>Jul 29 06:33:18 IVB102 kernel: [    0.015042] Freeing SMP alternatives memory: 32K (ffffffff81ec3000 - ffffffff81ecb000)
>Jul 29 06:33:18 IVB102 kernel: [    0.017763] ftrace: allocating 31374 entries in 123 pages
>Jul 29 06:33:18 IVB102 kernel: [    0.028430] smpboot: Max logical packages: 2
>Jul 29 06:33:18 IVB102 kernel: [    0.028463] smpboot: APIC(0) Converting physical 0 to logical package 0
>Jul 29 06:33:18 IVB102 kernel: [    0.028915] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
>Jul 29 06:33:18 IVB102 kernel: [    0.068637] TSC deadline timer enabled
>Jul 29 06:33:18 IVB102 kernel: [    0.068640] smpboot: CPU0: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz (family: 0x6, model: 0x3a, stepping: 0x9)
>Jul 29 06:33:18 IVB102 kernel: [    0.068734] calling  trace_init_flags_sys_exit+0x0/0xf @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.068735] initcall trace_init_flags_sys_exit+0x0/0xf returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.068736] calling  trace_init_flags_sys_enter+0x0/0xf @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.068738] initcall trace_init_flags_sys_enter+0x0/0xf returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.068739] calling  init_hw_perf_events+0x0/0x50e @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.068740] Performance Events: PEBS fmt1+, 16-deep LBR, IvyBridge events, full-width counters, Intel PMU driver.
>Jul 29 06:33:18 IVB102 kernel: [    0.068877] ... version:                3
>Jul 29 06:33:18 IVB102 kernel: [    0.068910] ... bit width:              48
>Jul 29 06:33:18 IVB102 kernel: [    0.068940] ... generic registers:      4
>Jul 29 06:33:18 IVB102 kernel: [    0.068970] ... value mask:             0000ffffffffffff
>Jul 29 06:33:18 IVB102 kernel: [    0.069003] ... max period:             0000ffffffffffff
>Jul 29 06:33:18 IVB102 kernel: [    0.069035] ... fixed-purpose events:   3
>Jul 29 06:33:18 IVB102 kernel: [    0.069065] ... event mask:             000000070000000f
>Jul 29 06:33:18 IVB102 kernel: [    0.069105] initcall init_hw_perf_events+0x0/0x50e returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.069107] calling  xen_init_spinlocks_jump+0x0/0x29 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.069109] initcall xen_init_spinlocks_jump+0x0/0x29 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.069110] calling  set_real_mode_permissions+0x0/0x9a @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.069115] initcall set_real_mode_permissions+0x0/0x9a returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.069116] calling  trace_init_perf_perm_irq_work_exit+0x0/0x13 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.069118] initcall trace_init_perf_perm_irq_work_exit+0x0/0x13 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.069119] calling  register_trigger_all_cpu_backtrace+0x0/0x16 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.069121] initcall register_trigger_all_cpu_backtrace+0x0/0x16 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.069122] calling  numachip_system_init+0x0/0x67 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.069123] initcall numachip_system_init+0x0/0x67 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.069124] calling  kvm_spinlock_init_jump+0x0/0x34 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.069125] initcall kvm_spinlock_init_jump+0x0/0x34 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.069127] calling  early_efi_map_fb+0x0/0x32 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.069129] initcall early_efi_map_fb+0x0/0x32 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.069130] calling  spawn_ksoftirqd+0x0/0x2d @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.069142] initcall spawn_ksoftirqd+0x0/0x2d returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.069144] calling  init_workqueues+0x0/0x547 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.069186] initcall init_workqueues+0x0/0x547 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.069188] calling  migration_init+0x0/0x3e @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.069189] initcall migration_init+0x0/0x3e returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.069191] calling  check_cpu_stall_init+0x0/0x1b @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.069192] initcall check_cpu_stall_init+0x0/0x1b returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.069193] calling  rcu_spawn_gp_kthread+0x0/0x137 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.069216] initcall rcu_spawn_gp_kthread+0x0/0x137 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.069217] calling  cpu_stop_init+0x0/0x9b @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.069226] initcall cpu_stop_init+0x0/0x9b returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.069227] calling  relay_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.069230] initcall relay_init+0x0/0x14 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.069232] calling  init_events+0x0/0x60 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.069237] initcall init_events+0x0/0x60 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.069238] calling  init_trace_printk+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.069240] initcall init_trace_printk+0x0/0x12 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.069241] calling  event_trace_enable_again+0x0/0x24 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.069243] initcall event_trace_enable_again+0x0/0x24 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.069245] calling  jump_label_init_module+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.069247] initcall jump_label_init_module+0x0/0x12 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.069248] calling  lru_init+0x0/0x4e @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.069256] initcall lru_init+0x0/0x4e returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.069258] calling  dynamic_debug_init+0x0/0x272 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.069585] initcall dynamic_debug_init+0x0/0x272 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.069588] calling  rand_initialize+0x0/0x40 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.069606] initcall rand_initialize+0x0/0x40 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.069702] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
>Jul 29 06:33:18 IVB102 kernel: [    0.069818] x86: Booting SMP configuration:
>Jul 29 06:33:18 IVB102 kernel: [    0.069849] .... node  #0, CPUs:      #1 #2 #3 #4 #5 #6 #7
>Jul 29 06:33:18 IVB102 kernel: [    0.630819] x86: Booted up 1 node, 8 CPUs
>Jul 29 06:33:18 IVB102 kernel: [    0.630881] smpboot: Total of 8 processors activated (56010.54 BogoMIPS)
>Jul 29 06:33:18 IVB102 kernel: [    0.637615] devtmpfs: initialized
>Jul 29 06:33:18 IVB102 kernel: [    0.637690] x86/mm: Memory block size: 128MB
>Jul 29 06:33:18 IVB102 kernel: [    0.641059] calling  ipc_ns_init+0x0/0x48 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641061] initcall ipc_ns_init+0x0/0x48 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641062] calling  init_mmap_min_addr+0x0/0x16 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641064] initcall init_mmap_min_addr+0x0/0x16 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641066] calling  evm_display_config+0x0/0x2d @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641066] evm: security.selinux
>Jul 29 06:33:18 IVB102 kernel: [    0.641096] evm: security.SMACK64
>Jul 29 06:33:18 IVB102 kernel: [    0.641126] evm: security.ima
>Jul 29 06:33:18 IVB102 kernel: [    0.641155] evm: security.capability
>Jul 29 06:33:18 IVB102 kernel: [    0.641183] initcall evm_display_config+0x0/0x2d returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641186] calling  init_cpufreq_transition_notifier_list+0x0/0x1b @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641188] initcall init_cpufreq_transition_notifier_list+0x0/0x1b returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641189] calling  net_ns_init+0x0/0x139 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641214] initcall net_ns_init+0x0/0x139 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641230] calling  e820_mark_nvs_memory+0x0/0x3b @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641231] PM: Registering ACPI NVS region [mem 0xda2b6000-0xda3c5fff] (1114112 bytes)
>Jul 29 06:33:18 IVB102 kernel: [    0.641288] PM: Registering ACPI NVS region [mem 0xda69d000-0xda6dffff] (274432 bytes)
>Jul 29 06:33:18 IVB102 kernel: [    0.641337] initcall e820_mark_nvs_memory+0x0/0x3b returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641338] calling  cpufreq_register_tsc_scaling+0x0/0x33 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641339] initcall cpufreq_register_tsc_scaling+0x0/0x33 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641341] calling  init_cpu_syscore+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641342] initcall init_cpu_syscore+0x0/0x14 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641344] calling  reboot_init+0x0/0x37 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641347] initcall reboot_init+0x0/0x37 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641349] calling  init_lapic_sysfs+0x0/0x23 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641351] initcall init_lapic_sysfs+0x0/0x23 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641352] calling  cpu_hotplug_pm_sync_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641354] initcall cpu_hotplug_pm_sync_init+0x0/0x14 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641355] calling  alloc_frozen_cpus+0x0/0x8 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641357] initcall alloc_frozen_cpus+0x0/0x8 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641358] calling  wq_sysfs_init+0x0/0x2b @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641369] initcall wq_sysfs_init+0x0/0x2b returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641371] calling  ksysfs_init+0x0/0x93 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641377] initcall ksysfs_init+0x0/0x93 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641378] calling  pm_init+0x0/0x76 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641398] initcall pm_init+0x0/0x76 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641399] calling  pm_disk_init+0x0/0x19 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641401] initcall pm_disk_init+0x0/0x19 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641403] calling  swsusp_header_init+0x0/0x40 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641405] initcall swsusp_header_init+0x0/0x40 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641406] calling  init_jiffies_clocksource+0x0/0x19 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641407] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
>Jul 29 06:33:18 IVB102 kernel: [    0.641459] initcall init_jiffies_clocksource+0x0/0x19 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641461] calling  cgroup_wq_init+0x0/0x58 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641472] initcall cgroup_wq_init+0x0/0x58 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641474] calling  ftrace_mod_cmd_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641476] initcall ftrace_mod_cmd_init+0x0/0x12 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641477] calling  init_function_trace+0x0/0x92 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641480] initcall init_function_trace+0x0/0x92 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641482] calling  init_wakeup_tracer+0x0/0x32 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641484] initcall init_wakeup_tracer+0x0/0x32 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641485] calling  init_graph_trace+0x0/0x68 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641489] initcall init_graph_trace+0x0/0x68 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641491] calling  init_per_zone_wmark_min+0x0/0x6a @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641494] initcall init_per_zone_wmark_min+0x0/0x6a returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641496] calling  init_zero_pfn+0x0/0x39 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641497] initcall init_zero_pfn+0x0/0x39 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641499] calling  memory_failure_init+0x0/0xa4 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641501] initcall memory_failure_init+0x0/0xa4 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641502] calling  cma_init_reserved_areas+0x0/0x1d4 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641504] initcall cma_init_reserved_areas+0x0/0x1d4 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641505] calling  fsnotify_init+0x0/0x26 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641507] initcall fsnotify_init+0x0/0x26 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641509] calling  filelock_init+0x0/0x9f @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641513] initcall filelock_init+0x0/0x9f returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641514] calling  init_script_binfmt+0x0/0x16 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641516] initcall init_script_binfmt+0x0/0x16 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641517] calling  init_elf_binfmt+0x0/0x16 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641519] initcall init_elf_binfmt+0x0/0x16 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641521] calling  init_compat_elf_binfmt+0x0/0x16 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641522] initcall init_compat_elf_binfmt+0x0/0x16 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641523] calling  debugfs_init+0x0/0x50 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641526] initcall debugfs_init+0x0/0x50 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641527] calling  tracefs_init+0x0/0x3b @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641529] initcall tracefs_init+0x0/0x3b returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641530] calling  securityfs_init+0x0/0x47 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641532] initcall securityfs_init+0x0/0x47 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641533] calling  prandom_init+0x0/0xe4 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641537] initcall prandom_init+0x0/0xe4 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641538] calling  pinctrl_init+0x0/0xb2 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641539] pinctrl core: initialized pinctrl subsystem
>Jul 29 06:33:18 IVB102 kernel: [    0.641580] initcall pinctrl_init+0x0/0xb2 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641581] calling  gpiolib_dev_init+0x0/0xd4 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641587] initcall gpiolib_dev_init+0x0/0xd4 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641590] calling  sfi_sysfs_init+0x0/0xd9 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641591] initcall sfi_sysfs_init+0x0/0xd9 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641593] calling  virtio_init+0x0/0x30 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641598] initcall virtio_init+0x0/0x30 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641599] calling  regulator_init+0x0/0x8c @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641639] initcall regulator_init+0x0/0x8c returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641640] calling  iommu_init+0x0/0x56 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641642] initcall iommu_init+0x0/0x56 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641645] calling  early_resume_init+0x0/0x230 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641670] RTC time:  4:33:04, date: 07/29/16
>Jul 29 06:33:18 IVB102 kernel: [    0.641702] initcall early_resume_init+0x0/0x230 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641703] calling  cpufreq_core_init+0x0/0x4c @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641705] initcall cpufreq_core_init+0x0/0x4c returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641707] calling  cpuidle_init+0x0/0x3d @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641710] initcall cpuidle_init+0x0/0x3d returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641711] calling  capsule_reboot_register+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641713] initcall capsule_reboot_register+0x0/0x12 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641714] calling  bsp_pm_check_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641716] initcall bsp_pm_check_init+0x0/0x14 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641718] calling  sock_init+0x0/0x8f @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641758] initcall sock_init+0x0/0x8f returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641759] calling  net_inuse_init+0x0/0x26 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641762] initcall net_inuse_init+0x0/0x26 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641763] calling  netpoll_init+0x0/0x31 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641764] initcall netpoll_init+0x0/0x31 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641765] calling  netlink_proto_init+0x0/0x15b @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641795] NET: Registered protocol family 16
>Jul 29 06:33:18 IVB102 kernel: [    0.641832] initcall netlink_proto_init+0x0/0x15b returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641834] calling  __gnttab_init+0x0/0x30 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641836] initcall __gnttab_init+0x0/0x30 returned -19 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641851] calling  bdi_class_init+0x0/0x49 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641855] initcall bdi_class_init+0x0/0x49 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641856] calling  mm_sysfs_init+0x0/0x29 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641858] initcall mm_sysfs_init+0x0/0x29 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641859] calling  kobject_uevent_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641861] initcall kobject_uevent_init+0x0/0x12 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641862] calling  pcibus_class_init+0x0/0x19 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641864] initcall pcibus_class_init+0x0/0x19 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641866] calling  pci_driver_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641871] initcall pci_driver_init+0x0/0x12 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641872] calling  rio_bus_init+0x0/0x40 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641878] initcall rio_bus_init+0x0/0x40 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641880] calling  backlight_class_init+0x0/0xaa @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641883] initcall backlight_class_init+0x0/0xaa returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641884] calling  xenbus_init+0x0/0x29c @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641885] initcall xenbus_init+0x0/0x29c returned -19 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641886] calling  tty_class_init+0x0/0x34 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641888] initcall tty_class_init+0x0/0x34 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641889] calling  vtconsole_class_init+0x0/0xc3 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641899] initcall vtconsole_class_init+0x0/0xc3 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641901] calling  iommu_dev_init+0x0/0x19 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641903] initcall iommu_dev_init+0x0/0x19 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641905] calling  mipi_dsi_bus_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641910] initcall mipi_dsi_bus_init+0x0/0x12 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641911] calling  wakeup_sources_debugfs_init+0x0/0x2b @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641914] initcall wakeup_sources_debugfs_init+0x0/0x2b returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641915] calling  register_node_type+0x0/0x2f @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641926] initcall register_node_type+0x0/0x2f returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641927] calling  regmap_initcall+0x0/0xd @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641930] initcall regmap_initcall+0x0/0xd returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641931] calling  sram_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641936] initcall sram_init+0x0/0x14 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641937] calling  syscon_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641943] initcall syscon_init+0x0/0x14 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641944] calling  spi_init+0x0/0x84 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641951] initcall spi_init+0x0/0x84 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641952] calling  i2c_init+0x0/0xaa @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.641959] initcall i2c_init+0x0/0xaa returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.641960] calling  init_ladder+0x0/0x25 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.644973] cpuidle: using governor ladder
>Jul 29 06:33:18 IVB102 kernel: [    0.645021] initcall init_ladder+0x0/0x25 returned 0 after 3906 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.645023] calling  init_menu+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.648969] cpuidle: using governor menu
>Jul 29 06:33:18 IVB102 kernel: [    0.649023] initcall init_menu+0x0/0x12 returned 0 after 3906 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.649025] calling  amd_postcore_init+0x0/0x141 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.649026] initcall amd_postcore_init+0x0/0x141 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.649042] calling  bts_init+0x0/0xaa @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.649045] initcall bts_init+0x0/0xaa returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.649046] calling  pt_init+0x0/0x367 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.649047] initcall pt_init+0x0/0x367 returned -19 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.649048] calling  boot_params_ksysfs_init+0x0/0x226 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.649051] initcall boot_params_ksysfs_init+0x0/0x226 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.649052] calling  sbf_init+0x0/0xf5 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.649053] initcall sbf_init+0x0/0xf5 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.649054] calling  arch_kdebugfs_init+0x0/0x24 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.649057] initcall arch_kdebugfs_init+0x0/0x24 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.649058] calling  mtrr_if_init+0x0/0x65 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.649060] initcall mtrr_if_init+0x0/0x65 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.649062] calling  ffh_cstate_init+0x0/0x2b @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.649063] initcall ffh_cstate_init+0x0/0x2b returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.649065] calling  activate_jump_labels+0x0/0x35 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.649066] initcall activate_jump_labels+0x0/0x35 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.649067] calling  gigantic_pages_init+0x0/0x33 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.649069] initcall gigantic_pages_init+0x0/0x33 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.649070] calling  kcmp_cookies_init+0x0/0x36 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.649077] initcall kcmp_cookies_init+0x0/0x36 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.649078] calling  acpi_pci_init+0x0/0x66 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.649079] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
>Jul 29 06:33:18 IVB102 kernel: [    0.649126] ACPI: bus type PCI registered
>Jul 29 06:33:18 IVB102 kernel: [    0.649158] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
>Jul 29 06:33:18 IVB102 kernel: [    0.649191] initcall acpi_pci_init+0x0/0x66 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.649192] calling  dma_bus_init+0x0/0xc2 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.649200] initcall dma_bus_init+0x0/0xc2 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.649202] calling  dma_channel_table_init+0x0/0xcf @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.649205] initcall dma_channel_table_init+0x0/0xcf returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.649206] calling  setup_vcpu_hotplug_event+0x0/0x22 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.649207] initcall setup_vcpu_hotplug_event+0x0/0x22 returned -19 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.649208] calling  register_xen_pci_notifier+0x0/0x36 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.649209] initcall register_xen_pci_notifier+0x0/0x36 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.649210] calling  xen_pcpu_init+0x0/0xc9 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.649211] initcall xen_pcpu_init+0x0/0xc9 returned -19 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.649213] calling  dmi_id_init+0x0/0x30f @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.649233] initcall dmi_id_init+0x0/0x30f returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.649234] calling  numachip_timer_init+0x0/0x52 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.649236] initcall numachip_timer_init+0x0/0x52 returned -19 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.649237] calling  pci_arch_init+0x0/0x68 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.649250] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
>Jul 29 06:33:18 IVB102 kernel: [    0.649296] PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
>Jul 29 06:33:18 IVB102 kernel: [    0.649335] pmd_set_huge: Cannot satisfy [mem 0xf8000000-0xf8200000] with a huge-page mapping due to MTRR override.
>Jul 29 06:33:18 IVB102 kernel: [    0.649433] PCI: Using configuration type 1 for base access
>Jul 29 06:33:18 IVB102 kernel: [    0.649470] initcall pci_arch_init+0x0/0x68 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.649485] calling  init_vdso+0x0/0x49 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.649494] initcall init_vdso+0x0/0x49 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.649495] calling  sysenter_setup+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.649497] initcall sysenter_setup+0x0/0x14 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.649498] calling  fixup_ht_bug+0x0/0xf2 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.649499] core: PMU erratum BJ122, BV98, HSD29 worked around, HT is on
>Jul 29 06:33:18 IVB102 kernel: [    0.649535] initcall fixup_ht_bug+0x0/0xf2 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.649536] calling  topology_init+0x0/0x89 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.649904] initcall topology_init+0x0/0x89 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.649905] calling  mtrr_init_finialize+0x0/0x3f @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.649907] initcall mtrr_init_finialize+0x0/0x3f returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.649908] calling  uid_cache_init+0x0/0x95 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.649910] initcall uid_cache_init+0x0/0x95 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.649912] calling  param_sysfs_init+0x0/0x1b2 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.650492] initcall param_sysfs_init+0x0/0x1b2 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.650493] calling  proc_schedstat_init+0x0/0x22 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.650495] initcall proc_schedstat_init+0x0/0x22 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.650496] calling  pm_sysrq_init+0x0/0x19 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.652976] initcall pm_sysrq_init+0x0/0x19 returned 0 after 3906 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.652981] calling  create_proc_profile+0x0/0x2a0 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.652984] initcall create_proc_profile+0x0/0x2a0 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.652987] calling  crash_save_vmcoreinfo_init+0x0/0x5d3 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653017] initcall crash_save_vmcoreinfo_init+0x0/0x5d3 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653018] calling  crash_notes_memory_init+0x0/0x37 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653021] initcall crash_notes_memory_init+0x0/0x37 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653022] calling  cgroup_namespaces_init+0x0/0x8 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653023] initcall cgroup_namespaces_init+0x0/0x8 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653024] calling  user_namespaces_init+0x0/0x2d @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653028] initcall user_namespaces_init+0x0/0x2d returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653029] calling  hung_task_init+0x0/0x51 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653040] initcall hung_task_init+0x0/0x51 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653042] calling  oom_init+0x0/0x6a @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653050] initcall oom_init+0x0/0x6a returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653051] calling  default_bdi_init+0x0/0x3f @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653074] initcall default_bdi_init+0x0/0x3f returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653075] calling  percpu_enable_async+0x0/0xf @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653076] initcall percpu_enable_async+0x0/0xf returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653078] calling  kcompactd_init+0x0/0x69 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653088] initcall kcompactd_init+0x0/0x69 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653089] calling  init_reserve_notifier+0x0/0x26 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653091] initcall init_reserve_notifier+0x0/0x26 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653093] calling  init_admin_reserve+0x0/0x40 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653094] initcall init_admin_reserve+0x0/0x40 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653095] calling  init_user_reserve+0x0/0x40 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653097] initcall init_user_reserve+0x0/0x40 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653098] calling  hugetlb_init+0x0/0x499 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653100] HugeTLB registered 2 MB page size, pre-allocated 0 pages
>Jul 29 06:33:18 IVB102 kernel: [    0.653147] initcall hugetlb_init+0x0/0x499 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653148] calling  mmu_notifier_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653150] initcall mmu_notifier_init+0x0/0x12 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653151] calling  ksm_init+0x0/0x15b @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653170] initcall ksm_init+0x0/0x15b returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653172] calling  hugepage_init+0x0/0x18f @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653192] initcall hugepage_init+0x0/0x18f returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653195] calling  mem_cgroup_swap_init+0x0/0x73 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653197] initcall mem_cgroup_swap_init+0x0/0x73 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653198] calling  mem_cgroup_init+0x0/0x148 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653201] initcall mem_cgroup_init+0x0/0x148 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653203] calling  crypto_wq_init+0x0/0x33 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653223] initcall crypto_wq_init+0x0/0x33 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653224] calling  cryptomgr_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653226] initcall cryptomgr_init+0x0/0x12 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653227] calling  init_bio+0x0/0xd1 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653262] initcall init_bio+0x0/0xd1 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653264] calling  blk_settings_init+0x0/0x2a @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653265] initcall blk_settings_init+0x0/0x2a returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653266] calling  blk_ioc_init+0x0/0x2a @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653270] initcall blk_ioc_init+0x0/0x2a returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653271] calling  blk_softirq_init+0x0/0x6a @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653272] initcall blk_softirq_init+0x0/0x6a returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653273] calling  blk_mq_init+0x0/0x19 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653274] initcall blk_mq_init+0x0/0x19 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653275] calling  genhd_device_init+0x0/0x76 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653298] initcall genhd_device_init+0x0/0x76 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653299] calling  irq_poll_setup+0x0/0x6a @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653301] initcall irq_poll_setup+0x0/0x6a returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653302] calling  byt_gpio_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653307] initcall byt_gpio_init+0x0/0x14 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653308] calling  gpiolib_debugfs_init+0x0/0x24 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653314] initcall gpiolib_debugfs_init+0x0/0x24 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653316] calling  lp_gpio_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653320] initcall lp_gpio_init+0x0/0x14 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653321] calling  rc5t583_gpio_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653324] initcall rc5t583_gpio_init+0x0/0x14 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653325] calling  sx150x_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653329] initcall sx150x_init+0x0/0x14 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653330] calling  palmas_gpio_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653334] initcall palmas_gpio_init+0x0/0x14 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653335] calling  tps6586x_gpio_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653338] initcall tps6586x_gpio_init+0x0/0x14 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653339] calling  tps65910_gpio_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653343] initcall tps65910_gpio_init+0x0/0x14 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653344] calling  pwm_debugfs_init+0x0/0x24 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653346] initcall pwm_debugfs_init+0x0/0x24 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653347] calling  pwm_sysfs_init+0x0/0x19 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653349] initcall pwm_sysfs_init+0x0/0x19 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653352] calling  pci_slot_init+0x0/0x50 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653354] initcall pci_slot_init+0x0/0x50 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653355] calling  fbmem_init+0x0/0xd7 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653359] initcall fbmem_init+0x0/0xd7 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.653360] calling  acpi_init+0x0/0x2a3 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.653376] ACPI: Added _OSI(Module Device)
>Jul 29 06:33:18 IVB102 kernel: [    0.653411] ACPI: Added _OSI(Processor Device)
>Jul 29 06:33:18 IVB102 kernel: [    0.653442] ACPI: Added _OSI(3.0 _SCP Extensions)
>Jul 29 06:33:18 IVB102 kernel: [    0.653474] ACPI: Added _OSI(Processor Aggregator Device)
>Jul 29 06:33:18 IVB102 kernel: [    0.653645] ACPI: Executed 1 blocks of module-level executable AML code
>Jul 29 06:33:18 IVB102 kernel: [    0.656117] ACPI: Dynamic OEM Table Load:
>Jul 29 06:33:18 IVB102 kernel: [    0.656181] ACPI: SSDT 0xFFFF8807FADED000 00083B (v01 PmRef  Cpu0Cst  00003001 INTL 20051117)
>Jul 29 06:33:18 IVB102 kernel: [    0.656592] ACPI: Dynamic OEM Table Load:
>Jul 29 06:33:18 IVB102 kernel: [    0.656656] ACPI: SSDT 0xFFFF8807FAE11C00 000303 (v01 PmRef  ApIst    00003000 INTL 20051117)
>Jul 29 06:33:18 IVB102 kernel: [    0.657027] ACPI: Dynamic OEM Table Load:
>Jul 29 06:33:18 IVB102 kernel: [    0.657090] ACPI: SSDT 0xFFFF8807FADDD800 000119 (v01 PmRef  ApCst    00003000 INTL 20051117)
>Jul 29 06:33:18 IVB102 kernel: [    0.658253] ACPI: Interpreter enabled
>Jul 29 06:33:18 IVB102 kernel: [    0.658295] ACPI: (supports S0 S3 S4 S5)
>Jul 29 06:33:18 IVB102 kernel: [    0.658327] ACPI: Using IOAPIC for interrupt routing
>Jul 29 06:33:18 IVB102 kernel: [    0.658374] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
>Jul 29 06:33:18 IVB102 kernel: [    0.662737] ACPI: Power Resource [FN00] (off)
>Jul 29 06:33:18 IVB102 kernel: [    0.662822] ACPI: Power Resource [FN01] (off)
>Jul 29 06:33:18 IVB102 kernel: [    0.662907] ACPI: Power Resource [FN02] (off)
>Jul 29 06:33:18 IVB102 kernel: [    0.662990] ACPI: Power Resource [FN03] (off)
>Jul 29 06:33:18 IVB102 kernel: [    0.663072] ACPI: Power Resource [FN04] (off)
>Jul 29 06:33:18 IVB102 kernel: [    0.663443] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
>Jul 29 06:33:18 IVB102 kernel: [    0.663481] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
>Jul 29 06:33:18 IVB102 kernel: [    0.663673] acpi PNP0A08:00: _OSC: platform does not support [PCIeHotplug PME]
>Jul 29 06:33:18 IVB102 kernel: [    0.663799] acpi PNP0A08:00: _OSC: OS now controls [AER PCIeCapability]
>Jul 29 06:33:18 IVB102 kernel: [    0.663837] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration
>Jul 29 06:33:18 IVB102 kernel: [    0.664173] PCI host bridge to bus 0000:00
>Jul 29 06:33:18 IVB102 kernel: [    0.664207] pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
>Jul 29 06:33:18 IVB102 kernel: [    0.664242] pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
>Jul 29 06:33:18 IVB102 kernel: [    0.664277] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
>Jul 29 06:33:18 IVB102 kernel: [    0.664321] pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d3fff window]
>Jul 29 06:33:18 IVB102 kernel: [    0.664365] pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff window]
>Jul 29 06:33:18 IVB102 kernel: [    0.664409] pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff window]
>Jul 29 06:33:18 IVB102 kernel: [    0.664453] pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff window]
>Jul 29 06:33:18 IVB102 kernel: [    0.664496] pci_bus 0000:00: root bus resource [mem 0x000e0000-0x000e3fff window]
>Jul 29 06:33:18 IVB102 kernel: [    0.664540] pci_bus 0000:00: root bus resource [mem 0x000e4000-0x000e7fff window]
>Jul 29 06:33:18 IVB102 kernel: [    0.664585] pci_bus 0000:00: root bus resource [mem 0xdfa00000-0xfeafffff window]
>Jul 29 06:33:18 IVB102 kernel: [    0.664628] pci_bus 0000:00: root bus resource [bus 00-3e]
>Jul 29 06:33:18 IVB102 kernel: [    0.664666] pci 0000:00:00.0: [8086:0150] type 00 class 0x060000
>Jul 29 06:33:18 IVB102 kernel: [    0.664733] pci 0000:00:02.0: [8086:0162] type 00 class 0x030000
>Jul 29 06:33:18 IVB102 kernel: [    0.664740] pci 0000:00:02.0: reg 0x10: [mem 0xf7800000-0xf7bfffff 64bit]
>Jul 29 06:33:18 IVB102 kernel: [    0.664744] pci 0000:00:02.0: reg 0x18: [mem 0xe0000000-0xefffffff 64bit pref]
>Jul 29 06:33:18 IVB102 kernel: [    0.664747] pci 0000:00:02.0: reg 0x20: [io  0xf000-0xf03f]
>Jul 29 06:33:18 IVB102 kernel: [    0.664835] pci 0000:00:14.0: [8086:1e31] type 00 class 0x0c0330
>Jul 29 06:33:18 IVB102 kernel: [    0.664853] pci 0000:00:14.0: reg 0x10: [mem 0xf7d20000-0xf7d2ffff 64bit]
>Jul 29 06:33:18 IVB102 kernel: [    0.664917] pci 0000:00:14.0: PME# supported from D3hot D3cold
>Jul 29 06:33:18 IVB102 kernel: [    0.664949] pci 0000:00:14.0: System wakeup disabled by ACPI
>Jul 29 06:33:18 IVB102 kernel: [    0.665018] pci 0000:00:16.0: [8086:1e3a] type 00 class 0x078000
>Jul 29 06:33:18 IVB102 kernel: [    0.665037] pci 0000:00:16.0: reg 0x10: [mem 0xf7d3b000-0xf7d3b00f 64bit]
>Jul 29 06:33:18 IVB102 kernel: [    0.665106] pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
>Jul 29 06:33:18 IVB102 kernel: [    0.665169] pci 0000:00:19.0: [8086:1503] type 00 class 0x020000
>Jul 29 06:33:18 IVB102 kernel: [    0.665184] pci 0000:00:19.0: reg 0x10: [mem 0xf7d00000-0xf7d1ffff]
>Jul 29 06:33:18 IVB102 kernel: [    0.665191] pci 0000:00:19.0: reg 0x14: [mem 0xf7d39000-0xf7d39fff]
>Jul 29 06:33:18 IVB102 kernel: [    0.665199] pci 0000:00:19.0: reg 0x18: [io  0xf080-0xf09f]
>Jul 29 06:33:18 IVB102 kernel: [    0.665253] pci 0000:00:19.0: PME# supported from D0 D3hot D3cold
>Jul 29 06:33:18 IVB102 kernel: [    0.665284] pci 0000:00:19.0: System wakeup disabled by ACPI
>Jul 29 06:33:18 IVB102 kernel: [    0.665346] pci 0000:00:1a.0: [8086:1e2d] type 00 class 0x0c0320
>Jul 29 06:33:18 IVB102 kernel: [    0.665361] pci 0000:00:1a.0: reg 0x10: [mem 0xf7d38000-0xf7d383ff]
>Jul 29 06:33:18 IVB102 kernel: [    0.665437] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
>Jul 29 06:33:18 IVB102 kernel: [    0.665481] pci 0000:00:1a.0: System wakeup disabled by ACPI
>Jul 29 06:33:18 IVB102 kernel: [    0.665541] pci 0000:00:1b.0: [8086:1e20] type 00 class 0x040300
>Jul 29 06:33:18 IVB102 kernel: [    0.665556] pci 0000:00:1b.0: reg 0x10: [mem 0xf7d30000-0xf7d33fff 64bit]
>Jul 29 06:33:18 IVB102 kernel: [    0.665621] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
>Jul 29 06:33:18 IVB102 kernel: [    0.665656] pci 0000:00:1b.0: System wakeup disabled by ACPI
>Jul 29 06:33:18 IVB102 kernel: [    0.666327] pci 0000:00:1c.0: [8086:1e10] type 01 class 0x060400
>Jul 29 06:33:18 IVB102 kernel: [    0.666451] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
>Jul 29 06:33:18 IVB102 kernel: [    0.666494] pci 0000:00:1c.0: System wakeup disabled by ACPI
>Jul 29 06:33:18 IVB102 kernel: [    0.666563] pci 0000:00:1c.5: [8086:1e1a] type 01 class 0x060400
>Jul 29 06:33:18 IVB102 kernel: [    0.666685] pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
>Jul 29 06:33:18 IVB102 kernel: [    0.666727] pci 0000:00:1c.5: System wakeup disabled by ACPI
>Jul 29 06:33:18 IVB102 kernel: [    0.666789] pci 0000:00:1d.0: [8086:1e26] type 00 class 0x0c0320
>Jul 29 06:33:18 IVB102 kernel: [    0.666805] pci 0000:00:1d.0: reg 0x10: [mem 0xf7d37000-0xf7d373ff]
>Jul 29 06:33:18 IVB102 kernel: [    0.666882] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
>Jul 29 06:33:18 IVB102 kernel: [    0.666922] pci 0000:00:1d.0: System wakeup disabled by ACPI
>Jul 29 06:33:18 IVB102 kernel: [    0.666984] pci 0000:00:1f.0: [8086:1e4a] type 00 class 0x060100
>Jul 29 06:33:18 IVB102 kernel: [    0.667130] pci 0000:00:1f.2: [8086:1e02] type 00 class 0x010601
>Jul 29 06:33:18 IVB102 kernel: [    0.667143] pci 0000:00:1f.2: reg 0x10: [io  0xf0d0-0xf0d7]
>Jul 29 06:33:18 IVB102 kernel: [    0.667150] pci 0000:00:1f.2: reg 0x14: [io  0xf0c0-0xf0c3]
>Jul 29 06:33:18 IVB102 kernel: [    0.667157] pci 0000:00:1f.2: reg 0x18: [io  0xf0b0-0xf0b7]
>Jul 29 06:33:18 IVB102 kernel: [    0.667163] pci 0000:00:1f.2: reg 0x1c: [io  0xf0a0-0xf0a3]
>Jul 29 06:33:18 IVB102 kernel: [    0.667171] pci 0000:00:1f.2: reg 0x20: [io  0xf060-0xf07f]
>Jul 29 06:33:18 IVB102 kernel: [    0.667178] pci 0000:00:1f.2: reg 0x24: [mem 0xf7d36000-0xf7d367ff]
>Jul 29 06:33:18 IVB102 kernel: [    0.667214] pci 0000:00:1f.2: PME# supported from D3hot
>Jul 29 06:33:18 IVB102 kernel: [    0.667267] pci 0000:00:1f.3: [8086:1e22] type 00 class 0x0c0500
>Jul 29 06:33:18 IVB102 kernel: [    0.667281] pci 0000:00:1f.3: reg 0x10: [mem 0xf7d35000-0xf7d350ff 64bit]
>Jul 29 06:33:18 IVB102 kernel: [    0.667298] pci 0000:00:1f.3: reg 0x20: [io  0xf040-0xf05f]
>Jul 29 06:33:18 IVB102 kernel: [    0.667422] pci 0000:00:1c.0: PCI bridge to [bus 01]
>Jul 29 06:33:18 IVB102 kernel: [    0.667673] pci 0000:02:00.0: [8086:008a] type 00 class 0x028000
>Jul 29 06:33:18 IVB102 kernel: [    0.667832] pci 0000:02:00.0: reg 0x10: [mem 0xf7c00000-0xf7c01fff 64bit]
>Jul 29 06:33:18 IVB102 kernel: [    0.668551] pci 0000:02:00.0: PME# supported from D0 D3hot D3cold
>Jul 29 06:33:18 IVB102 kernel: [    0.668710] pci 0000:02:00.0: System wakeup disabled by ACPI
>Jul 29 06:33:18 IVB102 kernel: [    0.673085] pci 0000:00:1c.5: PCI bridge to [bus 02]
>Jul 29 06:33:18 IVB102 kernel: [    0.673124] pci 0000:00:1c.5:   bridge window [mem 0xf7c00000-0xf7cfffff]
>Jul 29 06:33:18 IVB102 kernel: [    0.673595] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15)
>Jul 29 06:33:18 IVB102 kernel: [    0.673829] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *10 11 12 14 15)
>Jul 29 06:33:18 IVB102 kernel: [    0.674061] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 10 *11 12 14 15)
>Jul 29 06:33:18 IVB102 kernel: [    0.674292] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 *10 11 12 14 15)
>Jul 29 06:33:18 IVB102 kernel: [    0.674522] ACPI: PCI Interrupt Link [LNKE] (IRQs *3 4 5 6 10 11 12 14 15)
>Jul 29 06:33:18 IVB102 kernel: [    0.674751] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
>Jul 29 06:33:18 IVB102 kernel: [    0.675020] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 *11 12 14 15)
>Jul 29 06:33:18 IVB102 kernel: [    0.675250] ACPI: PCI Interrupt Link [LNKH] (IRQs *3 4 5 6 10 11 12 14 15)
>Jul 29 06:33:18 IVB102 kernel: [    0.675594] ACPI: Enabled 4 GPEs in block 00 to 3F
>Jul 29 06:33:18 IVB102 kernel: [    0.675670] initcall acpi_init+0x0/0x2a3 returned 0 after 19531 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.675672] calling  pnp_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.675678] initcall pnp_init+0x0/0x12 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.675679] calling  balloon_init+0x0/0x1ad @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.675681] initcall balloon_init+0x0/0x1ad returned -19 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.675682] calling  xen_setup_shutdown_event+0x0/0x40 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.675684] initcall xen_setup_shutdown_event+0x0/0x40 returned -19 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.675685] calling  xenbus_probe_backend_init+0x0/0x52 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.675689] initcall xenbus_probe_backend_init+0x0/0x52 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.675690] calling  xenbus_probe_frontend_init+0x0/0x9b @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.675694] initcall xenbus_probe_frontend_init+0x0/0x9b returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.675695] calling  xen_acpi_pad_init+0x0/0x4d @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.675696] initcall xen_acpi_pad_init+0x0/0x4d returned -19 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.675697] calling  balloon_init+0x0/0x8a @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.675698] initcall balloon_init+0x0/0x8a returned -19 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.675700] calling  pm8607_regulator_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.675704] initcall pm8607_regulator_init+0x0/0x14 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.675705] calling  lp8788_buck_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.675709] initcall lp8788_buck_init+0x0/0x14 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.675710] calling  lp8788_ldo_init+0x0/0x19 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.675716] initcall lp8788_ldo_init+0x0/0x19 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.675718] calling  misc_init+0x0/0xc4 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.675721] initcall misc_init+0x0/0xc4 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.675722] calling  tpm_init+0x0/0x7e @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.675725] initcall tpm_init+0x0/0x7e returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.675727] calling  vga_arb_device_init+0x0/0x1b7 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.675751] vgaarb: setting as boot device: PCI:0000:00:02.0
>Jul 29 06:33:18 IVB102 kernel: [    0.675787] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
>Jul 29 06:33:18 IVB102 kernel: [    0.675832] vgaarb: loaded
>Jul 29 06:33:18 IVB102 kernel: [    0.675861] vgaarb: bridge control possible 0000:00:02.0
>Jul 29 06:33:18 IVB102 kernel: [    0.675894] initcall vga_arb_device_init+0x0/0x1b7 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.675897] calling  cn_init+0x0/0xc0 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.675903] initcall cn_init+0x0/0xc0 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.675905] calling  pm860x_i2c_init+0x0/0x2e @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.675909] initcall pm860x_i2c_init+0x0/0x2e returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.675911] calling  wm8400_module_init+0x0/0x2e @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.675914] initcall wm8400_module_init+0x0/0x2e returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.675916] calling  wm831x_i2c_init+0x0/0x2e @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.675919] initcall wm831x_i2c_init+0x0/0x2e returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.675921] calling  wm831x_spi_init+0x0/0x2a @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.675924] initcall wm831x_spi_init+0x0/0x2a returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.675925] calling  wm8350_i2c_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.675930] initcall wm8350_i2c_init+0x0/0x14 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.675931] calling  tps65910_i2c_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.675935] initcall tps65910_i2c_init+0x0/0x14 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.675936] calling  tps80031_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.675939] initcall tps80031_init+0x0/0x14 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.675941] calling  ezx_pcap_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.675944] initcall ezx_pcap_init+0x0/0x14 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.675946] calling  da903x_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.675950] initcall da903x_init+0x0/0x14 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.675951] calling  da9052_spi_init+0x0/0x2e @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.675955] initcall da9052_spi_init+0x0/0x2e returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.675956] calling  da9052_i2c_init+0x0/0x2e @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.675959] initcall da9052_i2c_init+0x0/0x2e returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.675961] calling  lp8788_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.675964] initcall lp8788_init+0x0/0x14 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.675965] calling  da9055_i2c_init+0x0/0x2e @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.675969] initcall da9055_i2c_init+0x0/0x2e returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.675970] calling  max8925_i2c_init+0x0/0x2e @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.675975] initcall max8925_i2c_init+0x0/0x2e returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.675976] calling  max8997_i2c_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.675980] initcall max8997_i2c_init+0x0/0x14 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.675981] calling  max8998_i2c_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.675984] initcall max8998_i2c_init+0x0/0x14 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.675986] calling  ab3100_i2c_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.675989] initcall ab3100_i2c_init+0x0/0x14 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.675991] calling  tps6586x_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.675994] initcall tps6586x_init+0x0/0x14 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.675996] calling  tps65090_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.675999] initcall tps65090_init+0x0/0x14 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.676000] calling  aat2870_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.676004] initcall aat2870_init+0x0/0x14 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.676005] calling  palmas_i2c_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.676009] initcall palmas_i2c_init+0x0/0x14 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.676010] calling  rc5t583_i2c_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.676014] initcall rc5t583_i2c_init+0x0/0x14 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.676016] calling  sec_pmic_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.676019] initcall sec_pmic_init+0x0/0x14 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.676021] calling  as3711_i2c_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.676025] initcall as3711_i2c_init+0x0/0x14 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.676026] calling  dma_buf_init+0x0/0xaf @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.676029] initcall dma_buf_init+0x0/0xaf returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.676031] calling  init_scsi+0x0/0x9d @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.676056] SCSI subsystem initialized
>Jul 29 06:33:18 IVB102 kernel: [    0.676090] initcall init_scsi+0x0/0x9d returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.676092] calling  ata_init+0x0/0x409 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.676115] libata version 3.00 loaded.
>Jul 29 06:33:18 IVB102 kernel: [    0.676116] initcall ata_init+0x0/0x409 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.676117] calling  phy_init+0x0/0x32 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.676129] initcall phy_init+0x0/0x32 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.676130] calling  usb_init+0x0/0x166 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.676132] ACPI: bus type USB registered
>Jul 29 06:33:18 IVB102 kernel: [    0.676174] usbcore: registered new interface driver usbfs
>Jul 29 06:33:18 IVB102 kernel: [    0.676214] usbcore: registered new interface driver hub
>Jul 29 06:33:18 IVB102 kernel: [    0.676259] usbcore: registered new device driver usb
>Jul 29 06:33:18 IVB102 kernel: [    0.676294] initcall usb_init+0x0/0x166 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.676295] calling  usb_phy_generic_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.676299] initcall usb_phy_generic_init+0x0/0x14 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.676300] calling  serio_init+0x0/0x2c @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.676305] initcall serio_init+0x0/0x2c returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.676306] calling  input_init+0x0/0x10a @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.676309] initcall input_init+0x0/0x10a returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.676310] calling  rtc_init+0x0/0x4f @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.676314] initcall rtc_init+0x0/0x4f returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.676315] calling  power_supply_class_init+0x0/0x40 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.676318] initcall power_supply_class_init+0x0/0x40 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.676319] calling  hwmon_init+0x0/0xdd @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.676322] initcall hwmon_init+0x0/0xdd returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.676323] calling  md_init+0x0/0x165 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.676345] initcall md_init+0x0/0x165 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.676346] calling  mmc_init+0x0/0x3f @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.676355] initcall mmc_init+0x0/0x3f returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.676356] calling  leds_init+0x0/0x3c @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.676358] initcall leds_init+0x0/0x3c returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.676359] calling  dmi_init+0x0/0x11c @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.676363] initcall dmi_init+0x0/0x11c returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.676364] calling  efisubsys_init+0x0/0x14d @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.676365] initcall efisubsys_init+0x0/0x14d returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.676367] calling  devfreq_init+0x0/0xa9 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.676380] initcall devfreq_init+0x0/0xa9 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.676381] calling  devfreq_simple_ondemand_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.676383] initcall devfreq_simple_ondemand_init+0x0/0x12 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.676385] calling  devfreq_performance_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.676386] initcall devfreq_performance_init+0x0/0x12 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.676388] calling  devfreq_powersave_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.676389] initcall devfreq_powersave_init+0x0/0x12 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.676390] calling  devfreq_userspace_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.676392] initcall devfreq_userspace_init+0x0/0x12 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.676393] calling  ras_init+0x0/0x10 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.676396] initcall ras_init+0x0/0x10 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.676398] calling  pci_subsys_init+0x0/0x48 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.676398] PCI: Using ACPI for IRQ routing
>Jul 29 06:33:18 IVB102 kernel: [    0.677843] PCI: pci_cache_line_size set to 64 bytes
>Jul 29 06:33:18 IVB102 kernel: [    0.677930] e820: reserve RAM buffer [mem 0x0009d800-0x0009ffff]
>Jul 29 06:33:18 IVB102 kernel: [    0.677931] e820: reserve RAM buffer [mem 0x40004000-0x43ffffff]
>Jul 29 06:33:18 IVB102 kernel: [    0.677932] e820: reserve RAM buffer [mem 0xd9cae000-0xdbffffff]
>Jul 29 06:33:18 IVB102 kernel: [    0.677933] e820: reserve RAM buffer [mem 0xda69d000-0xdbffffff]
>Jul 29 06:33:18 IVB102 kernel: [    0.677934] e820: reserve RAM buffer [mem 0xdb000000-0xdbffffff]
>Jul 29 06:33:18 IVB102 kernel: [    0.677935] e820: reserve RAM buffer [mem 0x81f600000-0x81fffffff]
>Jul 29 06:33:18 IVB102 kernel: [    0.677937] initcall pci_subsys_init+0x0/0x48 returned 0 after 3906 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.677939] calling  proto_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.677941] initcall proto_init+0x0/0x12 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.677942] calling  net_dev_init+0x0/0x1bd @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.677997] initcall net_dev_init+0x0/0x1bd returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.677998] calling  neigh_init+0x0/0x80 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.677999] initcall neigh_init+0x0/0x80 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.678000] calling  fib_rules_init+0x0/0xa8 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.678002] initcall fib_rules_init+0x0/0xa8 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.678003] calling  pktsched_init+0x0/0x113 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.678005] initcall pktsched_init+0x0/0x113 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.678006] calling  tc_filter_init+0x0/0x55 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.678007] initcall tc_filter_init+0x0/0x55 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.678008] calling  tc_action_init+0x0/0x55 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.678009] initcall tc_action_init+0x0/0x55 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.678010] calling  genl_init+0x0/0x87 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.678013] initcall genl_init+0x0/0x87 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.678015] calling  ipv4_netfilter_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.678016] initcall ipv4_netfilter_init+0x0/0x12 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.678017] calling  cipso_v4_init+0x0/0x6a @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.678019] initcall cipso_v4_init+0x0/0x6a returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.678020] calling  wireless_nlevent_init+0x0/0x39 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.678022] initcall wireless_nlevent_init+0x0/0x39 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.678023] calling  netlbl_init+0x0/0x83 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.678024] NetLabel: Initializing
>Jul 29 06:33:18 IVB102 kernel: [    0.678056] NetLabel:  domain hash size = 128
>Jul 29 06:33:18 IVB102 kernel: [    0.678084] NetLabel:  protocols = UNLABELED CIPSOv4
>Jul 29 06:33:18 IVB102 kernel: [    0.678124] NetLabel:  unlabeled traffic allowed by default
>Jul 29 06:33:18 IVB102 kernel: [    0.678160] initcall netlbl_init+0x0/0x83 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.678161] calling  rfkill_init+0x0/0x85 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.678181] initcall rfkill_init+0x0/0x85 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.678182] calling  xen_mcfg_late+0x0/0xd1 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.678183] initcall xen_mcfg_late+0x0/0xd1 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.678184] calling  watchdog_init+0x0/0x77 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.678204] initcall watchdog_init+0x0/0x77 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.678221] calling  nmi_warning_debugfs+0x0/0x27 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.678223] initcall nmi_warning_debugfs+0x0/0x27 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.678225] calling  hpet_late_init+0x0/0xee @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.678234] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
>Jul 29 06:33:18 IVB102 kernel: [    0.678399] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
>Jul 29 06:33:18 IVB102 kernel: [    0.680436] initcall hpet_late_init+0x0/0xee returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.680437] calling  init_amd_nbs+0x0/0xc4 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.680440] amd_nb: Cannot enumerate AMD northbridges
>Jul 29 06:33:18 IVB102 kernel: [    0.680474] initcall init_amd_nbs+0x0/0xc4 returned -19 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.680475] calling  clocksource_done_booting+0x0/0x42 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.680488] clocksource: Switched to clocksource hpet
>Jul 29 06:33:18 IVB102 kernel: [    0.680525] initcall clocksource_done_booting+0x0/0x42 returned 0 after 37 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.680527] calling  ftrace_init_tracefs+0x0/0x1d0 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.680553] initcall ftrace_init_tracefs+0x0/0x1d0 returned 0 after 22 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.680554] calling  tracer_init_tracefs+0x0/0x1a4 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.681235] initcall tracer_init_tracefs+0x0/0x1a4 returned 0 after 662 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.681237] calling  init_trace_printk_function_export+0x0/0x32 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.681244] initcall init_trace_printk_function_export+0x0/0x32 returned 0 after 3 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.681245] calling  init_graph_tracefs+0x0/0x32 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.681249] initcall init_graph_tracefs+0x0/0x32 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.681250] calling  event_trace_init+0x0/0x2df @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684588] initcall event_trace_init+0x0/0x2df returned 0 after 3256 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684591] calling  init_kprobe_trace+0x0/0x96 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684598] initcall init_kprobe_trace+0x0/0x96 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684600] calling  init_uprobe_trace+0x0/0x54 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684605] initcall init_uprobe_trace+0x0/0x54 returned 0 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684607] calling  init_pipe_fs+0x0/0x47 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684618] initcall init_pipe_fs+0x0/0x47 returned 0 after 8 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684620] calling  cgroup_writeback_init+0x0/0x2d @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684639] initcall cgroup_writeback_init+0x0/0x2d returned 0 after 15 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684641] calling  inotify_user_setup+0x0/0x4b @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684648] initcall inotify_user_setup+0x0/0x4b returned 0 after 3 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684649] calling  eventpoll_init+0x0/0xda @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684654] initcall eventpoll_init+0x0/0xda returned 0 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684656] calling  anon_inode_init+0x0/0x5f @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684663] initcall anon_inode_init+0x0/0x5f returned 0 after 4 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684664] calling  proc_locks_init+0x0/0x22 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684668] initcall proc_locks_init+0x0/0x22 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684669] calling  dquot_init+0x0/0x120 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684671] VFS: Disk quotas dquot_6.6.0
>Jul 29 06:33:18 IVB102 kernel: [    0.684712] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
>Jul 29 06:33:18 IVB102 kernel: [    0.684750] initcall dquot_init+0x0/0x120 returned 0 after 76 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684752] calling  quota_init+0x0/0x31 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684759] initcall quota_init+0x0/0x31 returned 0 after 4 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684760] calling  proc_cmdline_init+0x0/0x22 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684765] initcall proc_cmdline_init+0x0/0x22 returned 0 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684766] calling  proc_consoles_init+0x0/0x22 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684769] initcall proc_consoles_init+0x0/0x22 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684770] calling  proc_cpuinfo_init+0x0/0x22 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684774] initcall proc_cpuinfo_init+0x0/0x22 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684775] calling  proc_devices_init+0x0/0x22 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684778] initcall proc_devices_init+0x0/0x22 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684779] calling  proc_interrupts_init+0x0/0x22 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684782] initcall proc_interrupts_init+0x0/0x22 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684783] calling  proc_loadavg_init+0x0/0x22 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684786] initcall proc_loadavg_init+0x0/0x22 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684787] calling  proc_meminfo_init+0x0/0x22 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684790] initcall proc_meminfo_init+0x0/0x22 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684791] calling  proc_stat_init+0x0/0x22 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684794] initcall proc_stat_init+0x0/0x22 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684794] calling  proc_uptime_init+0x0/0x22 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684798] initcall proc_uptime_init+0x0/0x22 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684799] calling  proc_version_init+0x0/0x22 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684802] initcall proc_version_init+0x0/0x22 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684803] calling  proc_softirqs_init+0x0/0x22 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684806] initcall proc_softirqs_init+0x0/0x22 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684807] calling  proc_kcore_init+0x0/0x182 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684813] initcall proc_kcore_init+0x0/0x182 returned 0 after 3 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684814] calling  vmcore_init+0x0/0x56a @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684817] initcall vmcore_init+0x0/0x56a returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684818] calling  proc_kmsg_init+0x0/0x25 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684822] initcall proc_kmsg_init+0x0/0x25 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684823] calling  proc_page_init+0x0/0x5f @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684827] initcall proc_page_init+0x0/0x5f returned 0 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684829] calling  init_ramfs_fs+0x0/0x20 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684832] initcall init_ramfs_fs+0x0/0x20 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684833] calling  init_hugetlbfs_fs+0x0/0x160 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684849] initcall init_hugetlbfs_fs+0x0/0x160 returned 0 after 12 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684851] calling  tomoyo_initerface_init+0x0/0x17b @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684854] initcall tomoyo_initerface_init+0x0/0x17b returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684855] calling  aa_create_aafs+0x0/0xc1 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684873] AppArmor: AppArmor Filesystem Enabled
>Jul 29 06:33:18 IVB102 kernel: [    0.684909] initcall aa_create_aafs+0x0/0xc1 returned 0 after 49 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684910] calling  blk_scsi_ioctl_init+0x0/0x2c5 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684913] initcall blk_scsi_ioctl_init+0x0/0x2c5 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684914] calling  dynamic_debug_init_debugfs+0x0/0x69 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684918] initcall dynamic_debug_init_debugfs+0x0/0x69 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684919] calling  fb_console_init+0x0/0x116 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684940] initcall fb_console_init+0x0/0x116 returned 0 after 18 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684941] calling  simplefb_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684949] initcall simplefb_init+0x0/0x14 returned 0 after 5 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684951] calling  acpi_event_init+0x0/0x3d @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684958] initcall acpi_event_init+0x0/0x3d returned 0 after 3 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684959] calling  pnp_system_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684966] initcall pnp_system_init+0x0/0x12 returned 0 after 3 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.684967] calling  pnpacpi_init+0x0/0x74 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.684968] pnp: PnP ACPI init
>Jul 29 06:33:18 IVB102 kernel: [    0.685049] system 00:00: [mem 0xfed40000-0xfed44fff] has been reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.685087] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
>Jul 29 06:33:18 IVB102 kernel: [    0.685134] system 00:01: [io  0x0680-0x069f] has been reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.685168] system 00:01: [io  0x1000-0x100f] has been reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.685202] system 00:01: [io  0xffff] has been reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.685235] system 00:01: [io  0xffff] has been reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.685268] system 00:01: [io  0x0400-0x0453] has been reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.685298] system 00:01: [io  0x0458-0x047f] has been reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.685332] system 00:01: [io  0x0500-0x057f] has been reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.685366] system 00:01: [io  0x164e-0x164f] has been reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.685400] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
>Jul 29 06:33:18 IVB102 kernel: [    0.685415] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
>Jul 29 06:33:18 IVB102 kernel: [    0.685446] system 00:03: [io  0x0454-0x0457] has been reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.685483] system 00:03: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
>Jul 29 06:33:18 IVB102 kernel: [    0.685529] system 00:04: [io  0x0a00-0x0a0f] has been reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.685566] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
>Jul 29 06:33:18 IVB102 kernel: [    0.685767] pnp 00:05: [dma 0 disabled]
>Jul 29 06:33:18 IVB102 kernel: [    0.685841] pnp 00:05: Plug and Play ACPI device, IDs PNP0400 (active)
>Jul 29 06:33:18 IVB102 kernel: [    0.685983] pnp 00:06: [dma 0 disabled]
>Jul 29 06:33:18 IVB102 kernel: [    0.686013] pnp 00:06: Plug and Play ACPI device, IDs PNP0501 (active)
>Jul 29 06:33:18 IVB102 kernel: [    0.686043] system 00:07: [io  0x04d0-0x04d1] has been reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.686077] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
>Jul 29 06:33:18 IVB102 kernel: [    0.686248] system 00:08: [mem 0xfed1c000-0xfed1ffff] has been reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.686285] system 00:08: [mem 0xfed10000-0xfed17fff] has been reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.686319] system 00:08: [mem 0xfed18000-0xfed18fff] has been reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.686354] system 00:08: [mem 0xfed19000-0xfed19fff] has been reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.686389] system 00:08: [mem 0xf8000000-0xfbffffff] has been reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.686420] system 00:08: [mem 0xfed20000-0xfed3ffff] has been reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.686455] system 00:08: [mem 0xfed90000-0xfed93fff] has been reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.686487] system 00:08: [mem 0xfed45000-0xfed8ffff] has been reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.686521] system 00:08: [mem 0xff000000-0xffffffff] has been reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.686554] system 00:08: [mem 0xfee00000-0xfeefffff] could not be reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.686590] system 00:08: [mem 0xdfa00000-0xdfa00fff] has been reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.686624] system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
>Jul 29 06:33:18 IVB102 kernel: [    0.686731] system 00:09: [mem 0x20000000-0x201fffff] has been reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.686768] system 00:09: [mem 0x40004000-0x40004fff] has been reserved
>Jul 29 06:33:18 IVB102 kernel: [    0.686800] system 00:09: Plug and Play ACPI device, IDs PNP0c01 (active)
>Jul 29 06:33:18 IVB102 kernel: [    0.686811] pnp: PnP ACPI: found 10 devices
>Jul 29 06:33:18 IVB102 kernel: [    0.686845] initcall pnpacpi_init+0x0/0x74 returned 0 after 1832 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.686847] calling  chr_dev_init+0x0/0xad @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.688454] initcall chr_dev_init+0x0/0xad returned 0 after 1566 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.688456] calling  firmware_class_init+0x0/0xec @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.688462] initcall firmware_class_init+0x0/0xec returned 0 after 3 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.688464] calling  thermal_init+0x0/0xd2 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.688474] initcall thermal_init+0x0/0xd2 returned 0 after 8 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.688476] calling  cpufreq_gov_performance_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.688479] initcall cpufreq_gov_performance_init+0x0/0x12 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.688480] calling  init_acpi_pm_clocksource+0x0/0xd7 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.692988] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
>Jul 29 06:33:18 IVB102 kernel: [    0.693036] initcall init_acpi_pm_clocksource+0x0/0xd7 returned 0 after 4446 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.693038] calling  pcibios_assign_resources+0x0/0xb4 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.693065] pci 0000:00:1c.0: PCI bridge to [bus 01]
>Jul 29 06:33:18 IVB102 kernel: [    0.693114] pci 0000:00:1c.5: PCI bridge to [bus 02]
>Jul 29 06:33:18 IVB102 kernel: [    0.693151] pci 0000:00:1c.5:   bridge window [mem 0xf7c00000-0xf7cfffff]
>Jul 29 06:33:18 IVB102 kernel: [    0.693196] pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
>Jul 29 06:33:18 IVB102 kernel: [    0.693197] pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
>Jul 29 06:33:18 IVB102 kernel: [    0.693198] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
>Jul 29 06:33:18 IVB102 kernel: [    0.693199] pci_bus 0000:00: resource 7 [mem 0x000d0000-0x000d3fff window]
>Jul 29 06:33:18 IVB102 kernel: [    0.693200] pci_bus 0000:00: resource 8 [mem 0x000d4000-0x000d7fff window]
>Jul 29 06:33:18 IVB102 kernel: [    0.693201] pci_bus 0000:00: resource 9 [mem 0x000d8000-0x000dbfff window]
>Jul 29 06:33:18 IVB102 kernel: [    0.693202] pci_bus 0000:00: resource 10 [mem 0x000dc000-0x000dffff window]
>Jul 29 06:33:18 IVB102 kernel: [    0.693203] pci_bus 0000:00: resource 11 [mem 0x000e0000-0x000e3fff window]
>Jul 29 06:33:18 IVB102 kernel: [    0.693204] pci_bus 0000:00: resource 12 [mem 0x000e4000-0x000e7fff window]
>Jul 29 06:33:18 IVB102 kernel: [    0.693205] pci_bus 0000:00: resource 13 [mem 0xdfa00000-0xfeafffff window]
>Jul 29 06:33:18 IVB102 kernel: [    0.693207] pci_bus 0000:02: resource 1 [mem 0xf7c00000-0xf7cfffff]
>Jul 29 06:33:18 IVB102 kernel: [    0.693212] initcall pcibios_assign_resources+0x0/0xb4 returned 0 after 167 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.693213] calling  sysctl_core_init+0x0/0x2c @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.693227] initcall sysctl_core_init+0x0/0x2c returned 0 after 12 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.693228] calling  eth_offload_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.693231] initcall eth_offload_init+0x0/0x14 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.693232] calling  inet_init+0x0/0x28a @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.693242] NET: Registered protocol family 2
>Jul 29 06:33:18 IVB102 kernel: [    0.693413] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
>Jul 29 06:33:18 IVB102 kernel: [    0.693712] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
>Jul 29 06:33:18 IVB102 kernel: [    0.693854] TCP: Hash tables configured (established 262144 bind 65536)
>Jul 29 06:33:18 IVB102 kernel: [    0.693914] UDP hash table entries: 16384 (order: 7, 524288 bytes)
>Jul 29 06:33:18 IVB102 kernel: [    0.694012] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
>Jul 29 06:33:18 IVB102 kernel: [    0.694129] initcall inet_init+0x0/0x28a returned 0 after 873 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.694131] calling  ipv4_offload_init+0x0/0x61 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.694134] initcall ipv4_offload_init+0x0/0x61 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.694135] calling  af_unix_init+0x0/0x50 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.694138] NET: Registered protocol family 1
>Jul 29 06:33:18 IVB102 kernel: [    0.694172] initcall af_unix_init+0x0/0x50 returned 0 after 33 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.694173] calling  ipv6_offload_init+0x0/0x83 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.694177] initcall ipv6_offload_init+0x0/0x83 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.694178] calling  pci_apply_final_quirks+0x0/0x103 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.694186] pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
>Jul 29 06:33:18 IVB102 kernel: [    0.732604] PCI: CLS mismatch (64 != 32), using 64 bytes
>Jul 29 06:33:18 IVB102 kernel: [    0.732607] initcall pci_apply_final_quirks+0x0/0x103 returned 0 after 37527 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.732609] calling  acpi_reserve_resources+0x0/0xeb @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.732614] initcall acpi_reserve_resources+0x0/0xeb returned 0 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    0.732616] calling  populate_rootfs+0x0/0x104 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    0.732647] Trying to unpack rootfs image as initramfs...
>Jul 29 06:33:18 IVB102 kernel: [    1.122784] Freeing initrd memory: 37260K (ffff88003372a000 - ffff880035b8d000)
>Jul 29 06:33:18 IVB102 kernel: [    1.122838] initcall populate_rootfs+0x0/0x104 returned 0 after 381087 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.122840] calling  pci_iommu_init+0x0/0x3c @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.122843] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
>Jul 29 06:33:18 IVB102 kernel: [    1.122876] software IO TLB [mem 0xd5cae000-0xd9cae000] (64MB) mapped at [ffff8800d5cae000-ffff8800d9cadfff]
>Jul 29 06:33:18 IVB102 kernel: [    1.122924] initcall pci_iommu_init+0x0/0x3c returned 0 after 78 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.122926] calling  calgary_fixup_tce_spaces+0x0/0xf2 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.122929] initcall calgary_fixup_tce_spaces+0x0/0xf2 returned -19 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.122932] calling  ir_dev_scope_init+0x0/0x34 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.122935] initcall ir_dev_scope_init+0x0/0x34 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.122953] calling  ia32_binfmt_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.122979] initcall ia32_binfmt_init+0x0/0x14 returned 0 after 19 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.122980] calling  amd_uncore_init+0x0/0x239 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.122983] initcall amd_uncore_init+0x0/0x239 returned -19 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.122984] calling  amd_ibs_init+0x0/0x1bc @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.122987] initcall amd_ibs_init+0x0/0x1bc returned -19 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.122988] calling  msr_init+0x0/0xc4 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.122995] initcall msr_init+0x0/0xc4 returned 0 after 4 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.122996] calling  amd_iommu_pc_init+0x0/0x151 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123000] initcall amd_iommu_pc_init+0x0/0x151 returned -19 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123001] calling  intel_cqm_init+0x0/0x4ba @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123004] initcall intel_cqm_init+0x0/0x4ba returned -19 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123005] calling  rapl_pmu_init+0x0/0x285 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123012] RAPL PMU: API unit is 2^-32 Joules, 3 fixed counters, 163840 ms ovfl timer
>Jul 29 06:33:18 IVB102 kernel: [    1.123058] RAPL PMU: hw unit of domain pp0-core 2^-16 Joules
>Jul 29 06:33:18 IVB102 kernel: [    1.123091] RAPL PMU: hw unit of domain package 2^-16 Joules
>Jul 29 06:33:18 IVB102 kernel: [    1.123124] RAPL PMU: hw unit of domain pp1-gpu 2^-16 Joules
>Jul 29 06:33:18 IVB102 kernel: [    1.123158] initcall rapl_pmu_init+0x0/0x285 returned 0 after 146 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123159] calling  intel_uncore_init+0x0/0x2db @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123223] initcall intel_uncore_init+0x0/0x2db returned 0 after 59 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123224] calling  cstate_pmu_init+0x0/0x167 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123237] initcall cstate_pmu_init+0x0/0x167 returned 0 after 10 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123240] calling  register_kernel_offset_dumper+0x0/0x1b @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123243] initcall register_kernel_offset_dumper+0x0/0x1b returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123245] calling  i8259A_init_ops+0x0/0x24 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123248] initcall i8259A_init_ops+0x0/0x24 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123250] calling  init_tsc_clocksource+0x0/0xb7 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123254] initcall init_tsc_clocksource+0x0/0xb7 returned 0 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123255] calling  add_rtc_cmos+0x0/0xaa @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123260] initcall add_rtc_cmos+0x0/0xaa returned 0 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123261] calling  i8237A_init_ops+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123269] initcall i8237A_init_ops+0x0/0x14 returned 0 after 4 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123270] calling  thermal_throttle_init_device+0x0/0x82 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123291] initcall thermal_throttle_init_device+0x0/0x82 returned 0 after 17 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123292] calling  ioapic_init_ops+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123295] initcall ioapic_init_ops+0x0/0x14 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123296] calling  add_pcspkr+0x0/0x40 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123321] initcall add_pcspkr+0x0/0x40 returned 0 after 21 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123324] calling  start_periodic_check_for_corruption+0x0/0x60 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123328] Scanning for low memory corruption every 60 seconds
>Jul 29 06:33:18 IVB102 kernel: [    1.123365] initcall start_periodic_check_for_corruption+0x0/0x60 returned 0 after 36 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123366] calling  sysfb_init+0x0/0x6f @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123395] initcall sysfb_init+0x0/0x6f returned 0 after 25 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123396] calling  audit_classes_init+0x0/0xaf @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123401] initcall audit_classes_init+0x0/0xaf returned 0 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123403] calling  crc32c_intel_mod_init+0x0/0x69 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123445] initcall crc32c_intel_mod_init+0x0/0x69 returned 0 after 39 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123447] calling  pmc_atom_init+0x0/0x1c3 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123453] initcall pmc_atom_init+0x0/0x1c3 returned -19 after 4 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123454] calling  iosf_mbi_init+0x0/0x1b @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123469] initcall iosf_mbi_init+0x0/0x1b returned 0 after 11 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123470] calling  proc_execdomains_init+0x0/0x22 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123476] initcall proc_execdomains_init+0x0/0x22 returned 0 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123478] calling  cpuhp_sysfs_init+0x0/0x6a @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123494] initcall cpuhp_sysfs_init+0x0/0x6a returned 0 after 13 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123495] calling  ioresources_init+0x0/0x3c @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123500] initcall ioresources_init+0x0/0x3c returned 0 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123502] calling  init_sched_debug_procfs+0x0/0x2c @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123506] initcall init_sched_debug_procfs+0x0/0x2c returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123507] calling  snapshot_device_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123549] initcall snapshot_device_init+0x0/0x12 returned 0 after 38 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123551] calling  irq_gc_init_ops+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123554] initcall irq_gc_init_ops+0x0/0x14 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123555] calling  irq_pm_init_ops+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123558] initcall irq_pm_init_ops+0x0/0x14 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123559] calling  init_posix_timers+0x0/0x243 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123573] initcall init_posix_timers+0x0/0x243 returned 0 after 10 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123574] calling  init_posix_cpu_timers+0x0/0x96 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123577] initcall init_posix_cpu_timers+0x0/0x96 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123578] calling  timekeeping_init_ops+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123581] initcall timekeeping_init_ops+0x0/0x14 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123582] calling  init_clocksource_sysfs+0x0/0x69 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123607] initcall init_clocksource_sysfs+0x0/0x69 returned 0 after 21 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123608] calling  init_timer_list_procfs+0x0/0x2c @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123613] initcall init_timer_list_procfs+0x0/0x2c returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123614] calling  alarmtimer_init+0x0/0x168 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123641] initcall alarmtimer_init+0x0/0x168 returned 0 after 24 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123643] calling  clockevents_init_sysfs+0x0/0xcb @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123716] initcall clockevents_init_sysfs+0x0/0xcb returned 0 after 69 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123717] calling  init_tstats_procfs+0x0/0x2c @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123721] initcall init_tstats_procfs+0x0/0x2c returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123722] calling  futex_init+0x0/0xee @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123729] futex hash table entries: 2048 (order: 5, 131072 bytes)
>Jul 29 06:33:18 IVB102 kernel: [    1.123779] initcall futex_init+0x0/0xee returned 0 after 54 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123781] calling  proc_dma_init+0x0/0x22 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123786] initcall proc_dma_init+0x0/0x22 returned 0 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123787] calling  proc_modules_init+0x0/0x22 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123791] initcall proc_modules_init+0x0/0x22 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123792] calling  kallsyms_init+0x0/0x25 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123796] initcall kallsyms_init+0x0/0x25 returned 0 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123798] calling  pid_namespaces_init+0x0/0x40 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123808] initcall pid_namespaces_init+0x0/0x40 returned 0 after 5 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123809] calling  audit_init+0x0/0xf7 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123811] audit: initializing netlink subsys (disabled)
>Jul 29 06:33:18 IVB102 kernel: [    1.123854] audit: type=2000 audit(1469766785.116:1): initialized
>Jul 29 06:33:18 IVB102 kernel: [    1.123892] initcall audit_init+0x0/0xf7 returned 0 after 78 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123893] calling  audit_watch_init+0x0/0x3a @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123897] initcall audit_watch_init+0x0/0x3a returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123898] calling  audit_fsnotify_init+0x0/0x3a @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123901] initcall audit_fsnotify_init+0x0/0x3a returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123902] calling  audit_tree_init+0x0/0x49 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.123905] initcall audit_tree_init+0x0/0x49 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.123907] calling  init_kprobes+0x0/0x1b5 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.124043] initcall init_kprobes+0x0/0x1b5 returned 0 after 130 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.124044] calling  utsname_sysctl_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.124052] initcall utsname_sysctl_init+0x0/0x14 returned 0 after 4 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.124053] calling  init_tracepoints+0x0/0x2a @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.124056] initcall init_tracepoints+0x0/0x2a returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.124058] calling  init_lstats_procfs+0x0/0x25 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.124062] initcall init_lstats_procfs+0x0/0x25 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.124063] calling  stack_trace_init+0x0/0xb0 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.124071] initcall stack_trace_init+0x0/0xb0 returned 0 after 4 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.124072] calling  init_mmio_trace+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.124078] initcall init_mmio_trace+0x0/0x12 returned 0 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.124079] calling  init_blk_tracer+0x0/0x58 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.124085] initcall init_blk_tracer+0x0/0x58 returned 0 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.124087] calling  perf_event_sysfs_init+0x0/0x93 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.124238] initcall perf_event_sysfs_init+0x0/0x93 returned 0 after 144 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.124240] calling  init_uprobes+0x0/0x63 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.124245] initcall init_uprobes+0x0/0x63 returned 0 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.124246] calling  system_trusted_keyring_init+0x0/0x74 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.124249] Initialise system trusted keyrings
>Jul 29 06:33:18 IVB102 kernel: [    1.124286] initcall system_trusted_keyring_init+0x0/0x74 returned 0 after 35 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.124287] calling  kswapd_init+0x0/0x6e @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.124315] initcall kswapd_init+0x0/0x6e returned 0 after 25 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.124317] calling  extfrag_debug_init+0x0/0x7a @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.124324] initcall extfrag_debug_init+0x0/0x7a returned 0 after 4 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.124326] calling  setup_vmstat+0x0/0x19a @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.124386] initcall setup_vmstat+0x0/0x19a returned 0 after 56 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.124387] calling  mm_compute_batch_init+0x0/0x19 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.124391] initcall mm_compute_batch_init+0x0/0x19 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.124392] calling  slab_proc_init+0x0/0x25 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.124397] initcall slab_proc_init+0x0/0x25 returned 0 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.124399] calling  workingset_init+0x0/0x87 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.124401] workingset: timestamp_bits=38 max_order=23 bucket_order=0
>Jul 29 06:33:18 IVB102 kernel: [    1.124438] initcall workingset_init+0x0/0x87 returned 0 after 35 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.124439] calling  proc_vmalloc_init+0x0/0x25 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.124443] initcall proc_vmalloc_init+0x0/0x25 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.124444] calling  procswaps_init+0x0/0x22 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.124449] initcall procswaps_init+0x0/0x22 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.124450] calling  init_frontswap+0x0/0x93 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.124458] initcall init_frontswap+0x0/0x93 returned 0 after 4 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.124460] calling  slab_sysfs_init+0x0/0xf6 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.125435] initcall slab_sysfs_init+0x0/0xf6 returned 0 after 949 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.125437] calling  init_cleancache+0x0/0x93 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.125451] initcall init_cleancache+0x0/0x93 returned 0 after 10 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.125452] calling  zs_init+0x0/0x88 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.125458] initcall zs_init+0x0/0x88 returned 0 after 3 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.125460] calling  fcntl_init+0x0/0x2a @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.125466] initcall fcntl_init+0x0/0x2a returned 0 after 3 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.125468] calling  proc_filesystems_init+0x0/0x22 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.125473] initcall proc_filesystems_init+0x0/0x22 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.125474] calling  start_dirtytime_writeback+0x0/0x2a @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.125478] initcall start_dirtytime_writeback+0x0/0x2a returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.125480] calling  dio_init+0x0/0x2d @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.125485] initcall dio_init+0x0/0x2d returned 0 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.125487] calling  dnotify_init+0x0/0x7b @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.125493] initcall dnotify_init+0x0/0x7b returned 0 after 3 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.125494] calling  fanotify_user_setup+0x0/0x77 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.125502] initcall fanotify_user_setup+0x0/0x77 returned 0 after 4 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.125503] calling  aio_setup+0x0/0xa7 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.125517] initcall aio_setup+0x0/0xa7 returned 0 after 10 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.125518] calling  init_sys32_ioctl+0x0/0x28 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.125578] initcall init_sys32_ioctl+0x0/0x28 returned 0 after 55 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.125579] calling  mbcache_init+0x0/0x31 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.125598] initcall mbcache_init+0x0/0x31 returned 0 after 15 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.125599] calling  init_devpts_fs+0x0/0x28 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.125610] initcall init_devpts_fs+0x0/0x28 returned 0 after 6 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.125611] calling  ext4_init_fs+0x0/0x19f @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.125678] initcall ext4_init_fs+0x0/0x19f returned 0 after 63 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.125680] calling  journal_init+0x0/0x104 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.125740] initcall journal_init+0x0/0x104 returned 0 after 55 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.125741] calling  init_fat_fs+0x0/0x4a @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.125772] initcall init_fat_fs+0x0/0x4a returned 0 after 27 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.125773] calling  init_vfat_fs+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.125777] initcall init_vfat_fs+0x0/0x12 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.125778] calling  ecryptfs_init+0x0/0x1ba @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.125896] initcall ecryptfs_init+0x0/0x1ba returned 0 after 111 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.125897] calling  init_nls_cp437+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.125901] initcall init_nls_cp437+0x0/0x14 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.125902] calling  fuse_init+0x0/0x1ad @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.125904] fuse init (API version 7.25)
>Jul 29 06:33:18 IVB102 kernel: [    1.125988] initcall fuse_init+0x0/0x1ad returned 0 after 81 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.125990] calling  init_pstore_fs+0x0/0x47 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.125994] initcall init_pstore_fs+0x0/0x47 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.125996] calling  efivarfs_init+0x0/0x34 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.125999] initcall efivarfs_init+0x0/0x34 returned -19 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126000] calling  ipc_init+0x0/0x17 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126006] initcall ipc_init+0x0/0x17 returned 0 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126007] calling  ipc_sysctl_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126018] initcall ipc_sysctl_init+0x0/0x14 returned 0 after 8 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126020] calling  init_mqueue_fs+0x0/0xa1 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126052] initcall init_mqueue_fs+0x0/0xa1 returned 0 after 29 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126054] calling  key_proc_init+0x0/0x5e @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126059] initcall key_proc_init+0x0/0x5e returned 0 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126060] calling  big_key_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126063] Key type big_key registered
>Jul 29 06:33:18 IVB102 kernel: [    1.126095] initcall big_key_init+0x0/0x12 returned 0 after 31 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126096] calling  selinux_nf_ip_init+0x0/0x47 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126099] initcall selinux_nf_ip_init+0x0/0x47 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126101] calling  init_sel_fs+0x0/0x9a @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126104] initcall init_sel_fs+0x0/0x9a returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126105] calling  selnl_init+0x0/0x56 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126112] initcall selnl_init+0x0/0x56 returned 0 after 3 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126113] calling  sel_netif_init+0x0/0x3a @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126116] initcall sel_netif_init+0x0/0x3a returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126117] calling  sel_netnode_init+0x0/0x32 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126121] initcall sel_netnode_init+0x0/0x32 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126122] calling  sel_netport_init+0x0/0x32 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126126] initcall sel_netport_init+0x0/0x32 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126127] calling  aurule_init+0x0/0x2d @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126130] initcall aurule_init+0x0/0x2d returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126132] calling  init_smk_fs+0x0/0x128 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126135] initcall init_smk_fs+0x0/0x128 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126136] calling  crypto_algapi_init+0x0/0xd @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126140] initcall crypto_algapi_init+0x0/0xd returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126142] calling  chainiv_module_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126146] initcall chainiv_module_init+0x0/0x12 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126147] calling  eseqiv_module_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126151] initcall eseqiv_module_init+0x0/0x12 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126153] calling  rsa_init+0x0/0x50 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126181] initcall rsa_init+0x0/0x50 returned 0 after 24 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126183] calling  hmac_module_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126187] initcall hmac_module_init+0x0/0x12 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126188] calling  crypto_null_mod_init+0x0/0x44 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126305] initcall crypto_null_mod_init+0x0/0x44 returned 0 after 110 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126307] calling  md5_mod_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126336] initcall md5_mod_init+0x0/0x12 returned 0 after 25 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126337] calling  sha1_generic_mod_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126362] initcall sha1_generic_mod_init+0x0/0x12 returned 0 after 20 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126364] calling  sha256_generic_mod_init+0x0/0x17 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126424] initcall sha256_generic_mod_init+0x0/0x17 returned 0 after 55 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126426] calling  sha512_generic_mod_init+0x0/0x17 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126475] initcall sha512_generic_mod_init+0x0/0x17 returned 0 after 44 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126476] calling  crypto_ecb_module_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126480] initcall crypto_ecb_module_init+0x0/0x12 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126481] calling  crypto_cbc_module_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126485] initcall crypto_cbc_module_init+0x0/0x12 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126486] calling  aes_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126511] initcall aes_init+0x0/0x12 returned 0 after 21 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126513] calling  crc32c_mod_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126538] initcall crc32c_mod_init+0x0/0x12 returned 0 after 22 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126540] calling  crct10dif_mod_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126568] initcall crct10dif_mod_init+0x0/0x12 returned 0 after 24 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126569] calling  lzo_mod_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126608] initcall lzo_mod_init+0x0/0x12 returned 0 after 35 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126610] calling  asymmetric_key_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126612] Key type asymmetric registered
>Jul 29 06:33:18 IVB102 kernel: [    1.126645] initcall asymmetric_key_init+0x0/0x12 returned 0 after 31 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126646] calling  x509_key_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126648] Asymmetric key parser 'x509' registered
>Jul 29 06:33:18 IVB102 kernel: [    1.126682] initcall x509_key_init+0x0/0x12 returned 0 after 32 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126683] calling  proc_genhd_init+0x0/0x3c @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126688] initcall proc_genhd_init+0x0/0x3c returned 0 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126689] calling  bsg_init+0x0/0x12a @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126710] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
>Jul 29 06:33:18 IVB102 kernel: [    1.126756] initcall bsg_init+0x0/0x12a returned 0 after 63 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126757] calling  throtl_init+0x0/0x44 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126794] initcall throtl_init+0x0/0x44 returned 0 after 33 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126795] calling  noop_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126796] io scheduler noop registered
>Jul 29 06:33:18 IVB102 kernel: [    1.126828] initcall noop_init+0x0/0x12 returned 0 after 31 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126829] calling  deadline_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126831] io scheduler deadline registered (default)
>Jul 29 06:33:18 IVB102 kernel: [    1.126864] initcall deadline_init+0x0/0x12 returned 0 after 32 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126865] calling  cfq_init+0x0/0xb7 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126884] io scheduler cfq registered
>Jul 29 06:33:18 IVB102 kernel: [    1.126918] initcall cfq_init+0x0/0xb7 returned 0 after 49 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126919] calling  btree_module_init+0x0/0x2a @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126924] initcall btree_module_init+0x0/0x2a returned 0 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126925] calling  crc_t10dif_mod_init+0x0/0x3e @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126930] initcall crc_t10dif_mod_init+0x0/0x3e returned 0 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126931] calling  percpu_counter_startup+0x0/0x19 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126936] initcall percpu_counter_startup+0x0/0x19 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126937] calling  digsig_init+0x0/0x3d @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126940] initcall digsig_init+0x0/0x3d returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126941] calling  sg_pool_init+0x0/0xcc @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126952] initcall sg_pool_init+0x0/0xcc returned 0 after 8 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126953] calling  phy_core_init+0x0/0x4d @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126959] initcall phy_core_init+0x0/0x4d returned 0 after 3 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126960] calling  intel_gpio_init+0x0/0x1b @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126972] initcall intel_gpio_init+0x0/0x1b returned 0 after 8 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126973] calling  pci_proc_init+0x0/0x65 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.126990] initcall pci_proc_init+0x0/0x65 returned 0 after 14 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.126992] calling  pcie_portdrv_init+0x0/0x77 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.127270] initcall pcie_portdrv_init+0x0/0x77 returned 0 after 269 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.127272] calling  aer_service_init+0x0/0x3e @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.127278] initcall aer_service_init+0x0/0x3e returned 0 after 3 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.127280] calling  pcie_pme_service_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.127286] initcall pcie_pme_service_init+0x0/0x12 returned 0 after 3 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.127287] calling  pci_hotplug_init+0x0/0x4a @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.127289] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
>Jul 29 06:33:18 IVB102 kernel: [    1.127323] initcall pci_hotplug_init+0x0/0x4a returned 0 after 32 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.127324] calling  pcied_init+0x0/0x6f @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.127328] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
>Jul 29 06:33:18 IVB102 kernel: [    1.127364] initcall pcied_init+0x0/0x6f returned 0 after 36 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.127365] calling  imsttfb_init+0x0/0xf6 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.127376] initcall imsttfb_init+0x0/0xf6 returned 0 after 8 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.127378] calling  asiliantfb_init+0x0/0x34 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.127386] initcall asiliantfb_init+0x0/0x34 returned 0 after 5 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.127387] calling  vesafb_driver_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.127398] initcall vesafb_driver_init+0x0/0x14 returned 0 after 8 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.127399] calling  efifb_driver_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.127406] initcall efifb_driver_init+0x0/0x14 returned 0 after 4 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.127408] calling  intel_idle_init+0x0/0x66e @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.127410] intel_idle: MWAIT substates: 0x1120
>Jul 29 06:33:18 IVB102 kernel: [    1.127411] intel_idle: v0.4.1 model 0x3A
>Jul 29 06:33:18 IVB102 kernel: [    1.127581] intel_idle: lapic_timer_reliable_states 0xffffffff
>Jul 29 06:33:18 IVB102 kernel: [    1.127583] initcall intel_idle_init+0x0/0x66e returned 0 after 169 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.127585] calling  ipmi_init_msghandler_mod+0x0/0xd @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.127591] ipmi message handler version 39.2
>Jul 29 06:33:18 IVB102 kernel: [    1.127627] initcall ipmi_init_msghandler_mod+0x0/0xd returned 0 after 38 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.127629] calling  acpi_ac_init+0x0/0x2e @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.127651] initcall acpi_ac_init+0x0/0x2e returned 0 after 19 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.127653] calling  acpi_button_driver_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.127690] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
>Jul 29 06:33:18 IVB102 kernel: [    1.127740] ACPI: Power Button [PWRB]
>Jul 29 06:33:18 IVB102 kernel: [    1.127794] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
>Jul 29 06:33:18 IVB102 kernel: [    1.127840] ACPI: Power Button [PWRF]
>Jul 29 06:33:18 IVB102 kernel: [    1.127882] initcall acpi_button_driver_init+0x0/0x12 returned 0 after 220 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.127883] calling  acpi_fan_driver_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.128056] initcall acpi_fan_driver_init+0x0/0x14 returned 0 after 165 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.128057] calling  acpi_processor_driver_init+0x0/0x44 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.128160] initcall acpi_processor_driver_init+0x0/0x44 returned 0 after 97 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.128162] calling  acpi_thermal_init+0x0/0x80 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.128433] thermal LNXTHERM:00: registered as thermal_zone0
>Jul 29 06:33:18 IVB102 kernel: [    1.128476] ACPI: Thermal Zone [TZ00] (28 C)
>Jul 29 06:33:18 IVB102 kernel: [    1.128657] thermal LNXTHERM:01: registered as thermal_zone1
>Jul 29 06:33:18 IVB102 kernel: [    1.128692] ACPI: Thermal Zone [TZ01] (30 C)
>Jul 29 06:33:18 IVB102 kernel: [    1.128729] initcall acpi_thermal_init+0x0/0x80 returned 0 after 550 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.128730] calling  acpi_battery_init+0x0/0x2c @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.128737] initcall acpi_battery_init+0x0/0x2c returned 0 after 3 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.128738] calling  acpi_hed_driver_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.128769] initcall acpi_hed_driver_init+0x0/0x12 returned 0 after 27 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.128770] calling  bgrt_init+0x0/0x7a @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.128774] initcall bgrt_init+0x0/0x7a returned -19 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.128775] calling  erst_init+0x0/0x2d9 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.128779] initcall erst_init+0x0/0x2d9 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.128780] calling  ghes_init+0x0/0x194 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.128782] GHES: HEST is not enabled!
>Jul 29 06:33:18 IVB102 kernel: [    1.128815] initcall ghes_init+0x0/0x194 returned -22 after 31 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.128816] calling  virtio_mmio_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.128823] initcall virtio_mmio_init+0x0/0x14 returned 0 after 5 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.128824] calling  virtio_pci_driver_init+0x0/0x1b @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.128838] initcall virtio_pci_driver_init+0x0/0x1b returned 0 after 11 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.128839] calling  virtio_balloon_driver_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.128846] initcall virtio_balloon_driver_init+0x0/0x12 returned 0 after 3 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.128847] calling  xenbus_probe_initcall+0x0/0x50 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.128850] initcall xenbus_probe_initcall+0x0/0x50 returned -19 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.128851] calling  xenbus_init+0x0/0x3b @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.128853] initcall xenbus_init+0x0/0x3b returned -19 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.128854] calling  xenbus_backend_init+0x0/0x4d @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.128857] initcall xenbus_backend_init+0x0/0x4d returned -19 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.128858] calling  hypervisor_subsys_init+0x0/0x27 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.128861] initcall hypervisor_subsys_init+0x0/0x27 returned -19 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.128862] calling  hyper_sysfs_init+0x0/0x158 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.128865] initcall hyper_sysfs_init+0x0/0x158 returned -19 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.128866] calling  platform_pci_init+0x0/0x1b @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.128876] initcall platform_pci_init+0x0/0x1b returned 0 after 5 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.128877] calling  xen_late_init_mcelog+0x0/0x54 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.128881] initcall xen_late_init_mcelog+0x0/0x54 returned -19 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.128882] calling  xen_acpi_processor_init+0x0/0x205 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.128884] initcall xen_acpi_processor_init+0x0/0x205 returned -19 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.128885] calling  lp872x_driver_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.128895] initcall lp872x_driver_init+0x0/0x14 returned 0 after 5 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.128896] calling  pty_init+0x0/0x3a2 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.128934] initcall pty_init+0x0/0x3a2 returned 0 after 34 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.128935] calling  sysrq_init+0x0/0x78 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.128941] initcall sysrq_init+0x0/0x78 returned 0 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.128942] calling  xen_hvc_init+0x0/0x23f @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.128945] initcall xen_hvc_init+0x0/0x23f returned -19 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.128946] calling  serial8250_init+0x0/0x157 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.128948] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
>Jul 29 06:33:18 IVB102 kernel: [    1.149414] 00:06: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
>Jul 29 06:33:18 IVB102 kernel: [    1.150519] initcall serial8250_init+0x0/0x157 returned 0 after 21065 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.150521] calling  serial_pci_driver_init+0x0/0x1b @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.150540] initcall serial_pci_driver_init+0x0/0x1b returned 0 after 16 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.150541] calling  max310x_uart_driver_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.150548] initcall max310x_uart_driver_init+0x0/0x14 returned 0 after 3 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.150549] calling  sccnxp_uart_driver_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.150556] initcall sccnxp_uart_driver_init+0x0/0x14 returned 0 after 4 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.150557] calling  init_kgdboc+0x0/0x16 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.150562] initcall init_kgdboc+0x0/0x16 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.150563] calling  ttyprintk_init+0x0/0xff @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.150594] initcall ttyprintk_init+0x0/0xff returned 0 after 27 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.150595] calling  init+0x0/0x104 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.150611] initcall init+0x0/0x104 returned 0 after 12 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.150612] calling  hpet_init+0x0/0x65 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.150707] initcall hpet_init+0x0/0x65 returned 0 after 90 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.150709] calling  hwrng_modinit+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.150739] initcall hwrng_modinit+0x0/0x12 returned 0 after 27 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.150741] calling  agp_init+0x0/0x29 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.150743] Linux agpgart interface v0.103
>Jul 29 06:33:18 IVB102 kernel: [    1.150773] initcall agp_init+0x0/0x29 returned 0 after 29 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.150774] calling  agp_amd64_mod_init+0x0/0x21 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.150793] initcall agp_amd64_mod_init+0x0/0x21 returned -19 after 15 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.150794] calling  agp_intel_init+0x0/0x2a @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.150805] initcall agp_intel_init+0x0/0x2a returned 0 after 6 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.150806] calling  agp_via_init+0x0/0x2a @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.150817] initcall agp_via_init+0x0/0x2a returned 0 after 8 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.150818] calling  init_tis+0x0/0xcf @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.150839] initcall init_tis+0x0/0xcf returned 0 after 18 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.150841] calling  cn_proc_init+0x0/0x38 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.150845] initcall cn_proc_init+0x0/0x38 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.150847] calling  topology_sysfs_init+0x0/0x80 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.150873] initcall topology_sysfs_init+0x0/0x80 returned 0 after 23 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.150875] calling  cacheinfo_sysfs_init+0x0/0x8a @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.151222] initcall cacheinfo_sysfs_init+0x0/0x8a returned 0 after 335 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.151223] calling  devcoredump_init+0x0/0x19 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.151230] initcall devcoredump_init+0x0/0x19 returned 0 after 3 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.151231] calling  brd_init+0x0/0x15a @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.153255] brd: module loaded
>Jul 29 06:33:18 IVB102 kernel: [    1.153291] initcall brd_init+0x0/0x15a returned 0 after 2008 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.153293] calling  loop_init+0x0/0x14d @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154302] loop: module loaded
>Jul 29 06:33:18 IVB102 kernel: [    1.154337] initcall loop_init+0x0/0x14d returned 0 after 1016 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154338] calling  init+0x0/0x80 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154361] initcall init+0x0/0x80 returned 0 after 19 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154363] calling  xlblk_init+0x0/0xdf @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154366] initcall xlblk_init+0x0/0xdf returned -19 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154368] calling  htcpld_core_init+0x0/0x2d @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154385] initcall htcpld_core_init+0x0/0x2d returned -19 after 14 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154387] calling  wm8994_i2c_driver_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154394] initcall wm8994_i2c_driver_init+0x0/0x14 returned 0 after 3 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154395] calling  tps65912_i2c_driver_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154402] initcall tps65912_i2c_driver_init+0x0/0x14 returned 0 after 3 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154403] calling  tps65912_spi_driver_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154410] initcall tps65912_spi_driver_init+0x0/0x14 returned 0 after 3 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154412] calling  twl6040_driver_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154422] initcall twl6040_driver_init+0x0/0x14 returned 0 after 5 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154424] calling  smsc_i2c_driver_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154430] initcall smsc_i2c_driver_init+0x0/0x14 returned 0 after 3 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154432] calling  da9063_i2c_driver_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154439] initcall da9063_i2c_driver_init+0x0/0x14 returned 0 after 3 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154440] calling  max77693_i2c_driver_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154447] initcall max77693_i2c_driver_init+0x0/0x14 returned 0 after 3 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154448] calling  adp5520_driver_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154455] initcall adp5520_driver_init+0x0/0x14 returned 0 after 3 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154456] calling  intel_soc_pmic_i2c_driver_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154463] initcall intel_soc_pmic_i2c_driver_init+0x0/0x14 returned 0 after 3 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154465] calling  spi_transport_init+0x0/0x76 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154473] initcall spi_transport_init+0x0/0x76 returned 0 after 5 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154474] calling  init_sd+0x0/0x173 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154489] initcall init_sd+0x0/0x173 returned 0 after 11 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154490] calling  init_sr+0x0/0x43 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154497] initcall init_sr+0x0/0x43 returned 0 after 4 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154499] calling  init_sg+0x0/0x122 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154508] initcall init_sg+0x0/0x122 returned 0 after 6 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154510] calling  piix_init+0x0/0x29 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154525] initcall piix_init+0x0/0x29 returned 0 after 12 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154527] calling  sis_pci_driver_init+0x0/0x1b @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154537] initcall sis_pci_driver_init+0x0/0x1b returned 0 after 6 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154539] calling  ata_generic_pci_driver_init+0x0/0x1b @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154550] initcall ata_generic_pci_driver_init+0x0/0x1b returned 0 after 8 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154551] calling  net_olddevs_init+0x0/0x5b @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154557] initcall net_olddevs_init+0x0/0x5b returned 0 after 3 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154558] calling  phy_module_init+0x0/0x19 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154593] initcall phy_module_init+0x0/0x19 returned 0 after 32 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154594] calling  phy_module_init+0x0/0x19 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154609] initcall phy_module_init+0x0/0x19 returned 0 after 12 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154610] calling  phy_module_init+0x0/0x19 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154620] initcall phy_module_init+0x0/0x19 returned 0 after 5 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154621] calling  phy_module_init+0x0/0x19 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154635] initcall phy_module_init+0x0/0x19 returned 0 after 11 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154636] calling  phy_module_init+0x0/0x19 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154642] initcall phy_module_init+0x0/0x19 returned 0 after 3 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154643] calling  phy_module_init+0x0/0x19 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154663] initcall phy_module_init+0x0/0x19 returned 0 after 17 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154664] calling  phy_module_init+0x0/0x19 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154687] initcall phy_module_init+0x0/0x19 returned 0 after 20 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154688] calling  phy_module_init+0x0/0x19 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154721] initcall phy_module_init+0x0/0x19 returned 0 after 30 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154722] calling  phy_module_init+0x0/0x19 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154731] initcall phy_module_init+0x0/0x19 returned 0 after 5 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154732] calling  phy_module_init+0x0/0x19 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154746] initcall phy_module_init+0x0/0x19 returned 0 after 11 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154747] calling  phy_module_init+0x0/0x19 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154764] initcall phy_module_init+0x0/0x19 returned 0 after 14 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154765] calling  phy_module_init+0x0/0x19 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154772] initcall phy_module_init+0x0/0x19 returned 0 after 4 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154773] calling  fixed_mdio_bus_init+0x0/0xc4 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154797] libphy: Fixed MDIO Bus: probed
>Jul 29 06:33:18 IVB102 kernel: [    1.154831] initcall fixed_mdio_bus_init+0x0/0xc4 returned 0 after 54 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154832] calling  mdio_gpio_driver_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154840] initcall mdio_gpio_driver_init+0x0/0x14 returned 0 after 5 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154841] calling  phy_module_init+0x0/0x19 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154847] initcall phy_module_init+0x0/0x19 returned 0 after 3 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154848] calling  phy_module_init+0x0/0x19 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154858] initcall phy_module_init+0x0/0x19 returned 0 after 5 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154859] calling  phy_module_init+0x0/0x19 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154896] initcall phy_module_init+0x0/0x19 returned 0 after 34 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154897] calling  phy_module_init+0x0/0x19 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154911] initcall phy_module_init+0x0/0x19 returned 0 after 12 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154912] calling  phy_module_init+0x0/0x19 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154919] initcall phy_module_init+0x0/0x19 returned 0 after 3 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.154920] calling  tun_init+0x0/0x90 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.154922] tun: Universal TUN/TAP device driver, 1.6
>Jul 29 06:33:18 IVB102 kernel: [    1.154954] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
>Jul 29 06:33:18 IVB102 kernel: [    1.155017] initcall tun_init+0x0/0x90 returned 0 after 92 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.155018] calling  virtio_net_driver_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.155026] initcall virtio_net_driver_init+0x0/0x12 returned 0 after 4 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.155027] calling  ppp_init+0x0/0x115 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.155029] PPP generic driver version 2.4.2
>Jul 29 06:33:18 IVB102 kernel: [    1.155086] initcall ppp_init+0x0/0x115 returned 0 after 55 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.155087] calling  netif_init+0x0/0x68 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.155090] initcall netif_init+0x0/0x68 returned -19 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.155091] calling  cdrom_init+0x0/0x19 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.155097] initcall cdrom_init+0x0/0x19 returned 0 after 3 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.155098] calling  dwc2_platform_driver_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.155106] initcall dwc2_platform_driver_init+0x0/0x14 returned 0 after 4 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.155107] calling  dwc2_pci_driver_init+0x0/0x1b @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.155117] initcall dwc2_pci_driver_init+0x0/0x1b returned 0 after 5 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.155118] calling  ohci_hcd_mod_init+0x0/0x95 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.155120] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
>Jul 29 06:33:18 IVB102 kernel: [    1.155156] initcall ohci_hcd_mod_init+0x0/0x95 returned 0 after 35 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.155157] calling  ohci_pci_init+0x0/0x69 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.155159] ohci-pci: OHCI PCI platform driver
>Jul 29 06:33:18 IVB102 kernel: [    1.155198] initcall ohci_pci_init+0x0/0x69 returned 0 after 37 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.155199] calling  ohci_platform_init+0x0/0x4c @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.155201] ohci-platform: OHCI generic platform driver
>Jul 29 06:33:18 IVB102 kernel: [    1.155239] initcall ohci_platform_init+0x0/0x4c returned 0 after 35 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.155240] calling  uhci_hcd_init+0x0/0x11d @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.155242] uhci_hcd: USB Universal Host Controller Interface driver
>Jul 29 06:33:18 IVB102 kernel: [    1.155286] initcall uhci_hcd_init+0x0/0x11d returned 0 after 43 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.155287] calling  kgdbdbgp_start_thread+0x0/0x52 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.155290] initcall kgdbdbgp_start_thread+0x0/0x52 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    1.155291] calling  i8042_init+0x0/0x413 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    1.155308] i8042: PNP: No PS/2 controller found. Probing ports directly.
>Jul 29 06:33:18 IVB102 kernel: [    2.120483] tsc: Refined TSC clocksource calibration: 3500.025 MHz
>Jul 29 06:33:18 IVB102 kernel: [    2.120521] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x327368780e0, max_idle_ns: 440795231913 ns
>Jul 29 06:33:18 IVB102 kernel: [    2.251369] i8042: No controller found
>Jul 29 06:33:18 IVB102 kernel: [    2.251401] initcall i8042_init+0x0/0x413 returned -19 after 1070462 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.251402] calling  input_leds_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.251407] initcall input_leds_init+0x0/0x12 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.251408] calling  mousedev_init+0x0/0x85 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.251519] mousedev: PS/2 mouse device common for all mice
>Jul 29 06:33:18 IVB102 kernel: [    2.251553] initcall mousedev_init+0x0/0x85 returned 0 after 139 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.251554] calling  evdev_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.251662] initcall evdev_init+0x0/0x12 returned 0 after 102 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.251663] calling  atkbd_init+0x0/0x27 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.251673] initcall atkbd_init+0x0/0x27 returned 0 after 7 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.251675] calling  uinput_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.251737] initcall uinput_init+0x0/0x12 returned 0 after 57 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.251739] calling  cmos_init+0x0/0x73 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.251761] rtc_cmos 00:02: RTC can wake from S4
>Jul 29 06:33:18 IVB102 kernel: [    2.251942] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
>Jul 29 06:33:18 IVB102 kernel: [    2.252001] rtc_cmos 00:02: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
>Jul 29 06:33:18 IVB102 kernel: [    2.252052] initcall cmos_init+0x0/0x73 returned 0 after 303 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.252054] calling  dm_init+0x0/0x46 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.252077] device-mapper: uevent: version 1.0.3
>Jul 29 06:33:18 IVB102 kernel: [    2.252185] device-mapper: ioctl: 4.34.0-ioctl (2015-10-28) initialised: dm-devel@redhat.com
>Jul 29 06:33:18 IVB102 kernel: [    2.252232] initcall dm_init+0x0/0x46 returned 0 after 172 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.252234] calling  cpufreq_stats_init+0x0/0xcb @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.252238] initcall cpufreq_stats_init+0x0/0xcb returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.252239] calling  cpufreq_gov_powersave_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.252243] initcall cpufreq_gov_powersave_init+0x0/0x12 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.252244] calling  cpufreq_gov_userspace_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.252247] initcall cpufreq_gov_userspace_init+0x0/0x12 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.252248] calling  cpufreq_gov_dbs_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.252252] initcall cpufreq_gov_dbs_init+0x0/0x12 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.252253] calling  cpufreq_gov_dbs_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.252256] initcall cpufreq_gov_dbs_init+0x0/0x12 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.252257] calling  intel_pstate_init+0x0/0x4d6 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.252262] intel_pstate: Intel P-state driver initializing
>Jul 29 06:33:18 IVB102 kernel: [    2.252546] initcall intel_pstate_init+0x0/0x4d6 returned 0 after 278 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.252550] calling  ledtrig_cpu_init+0x0/0x99 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.252560] ledtrig-cpu: registered to indicate activity on CPUs
>Jul 29 06:33:18 IVB102 kernel: [    2.252607] initcall ledtrig_cpu_init+0x0/0x99 returned 0 after 49 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.252611] calling  efivars_sysfs_init+0x0/0x230 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.252618] initcall efivars_sysfs_init+0x0/0x230 returned -19 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.252621] calling  esrt_sysfs_init+0x0/0x343 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.252627] initcall esrt_sysfs_init+0x0/0x343 returned -38 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.252630] calling  gpio_clk_driver_init+0x0/0x14 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.252650] initcall gpio_clk_driver_init+0x0/0x14 returned 0 after 15 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.252653] calling  extcon_class_init+0x0/0x17 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.252666] initcall extcon_class_init+0x0/0x17 returned 0 after 5 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.252669] calling  powercap_init+0x0/0x289 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.252720] initcall powercap_init+0x0/0x289 returned 0 after 43 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.252724] calling  pm_check_save_msr+0x0/0x20 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.252731] initcall pm_check_save_msr+0x0/0x20 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.252734] calling  sock_diag_init+0x0/0x37 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.252769] initcall sock_diag_init+0x0/0x37 returned 0 after 28 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.252775] calling  blackhole_init+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.252782] initcall blackhole_init+0x0/0x12 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.252785] calling  gre_offload_init+0x0/0x47 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.252791] initcall gre_offload_init+0x0/0x47 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.252794] calling  sysctl_ipv4_init+0x0/0x4e @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.252859] initcall sysctl_ipv4_init+0x0/0x4e returned 0 after 59 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.252862] calling  cubictcp_register+0x0/0x59 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.252868] initcall cubictcp_register+0x0/0x59 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.252871] calling  inet6_init+0x0/0x323 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.253022] NET: Registered protocol family 10
>Jul 29 06:33:18 IVB102 kernel: [    2.253351] initcall inet6_init+0x0/0x323 returned 0 after 463 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.253354] calling  packet_init+0x0/0x42 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.253378] NET: Registered protocol family 17
>Jul 29 06:33:18 IVB102 kernel: [    2.253428] initcall packet_init+0x0/0x42 returned 0 after 65 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.253431] calling  dcbnl_init+0x0/0x4d @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.253438] initcall dcbnl_init+0x0/0x4d returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.253441] calling  init_dns_resolver+0x0/0xe7 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.253451] Key type dns_resolver registered
>Jul 29 06:33:18 IVB102 kernel: [    2.253496] initcall init_dns_resolver+0x0/0xe7 returned 0 after 50 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.253500] calling  mcheck_init_device+0x0/0x17b @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.253841] initcall mcheck_init_device+0x0/0x17b returned 0 after 326 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.253879] calling  tboot_late_init+0x0/0x29b @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.253886] initcall tboot_late_init+0x0/0x29b returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.253889] calling  mcheck_late_init+0x0/0x34 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.253901] initcall mcheck_late_init+0x0/0x34 returned 0 after 6 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.253904] calling  severities_debugfs_init+0x0/0x3d @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.253912] initcall severities_debugfs_init+0x0/0x3d returned 0 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.253915] calling  threshold_init_device+0x0/0x45 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.253924] initcall threshold_init_device+0x0/0x45 returned 0 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.253927] calling  microcode_init+0x0/0x1b8 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.253972] microcode: CPU0 sig=0x306a9, pf=0x2, revision=0x15
>Jul 29 06:33:18 IVB102 kernel: [    2.254056] microcode: CPU1 sig=0x306a9, pf=0x2, revision=0x15
>Jul 29 06:33:18 IVB102 kernel: [    2.254131] microcode: CPU2 sig=0x306a9, pf=0x2, revision=0x15
>Jul 29 06:33:18 IVB102 kernel: [    2.254220] microcode: CPU3 sig=0x306a9, pf=0x2, revision=0x15
>Jul 29 06:33:18 IVB102 kernel: [    2.254277] microcode: CPU4 sig=0x306a9, pf=0x2, revision=0x15
>Jul 29 06:33:18 IVB102 kernel: [    2.254365] microcode: CPU5 sig=0x306a9, pf=0x2, revision=0x15
>Jul 29 06:33:18 IVB102 kernel: [    2.254438] microcode: CPU6 sig=0x306a9, pf=0x2, revision=0x15
>Jul 29 06:33:18 IVB102 kernel: [    2.254529] microcode: CPU7 sig=0x306a9, pf=0x2, revision=0x15
>Jul 29 06:33:18 IVB102 kernel: [    2.254679] microcode: Microcode Update Driver: v2.01 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
>Jul 29 06:33:18 IVB102 kernel: [    2.254748] initcall microcode_init+0x0/0x1b8 returned 0 after 793 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.254752] calling  hpet_insert_resource+0x0/0x24 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.254762] initcall hpet_insert_resource+0x0/0x24 returned 0 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.254765] calling  update_mp_table+0x0/0x43d @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.254773] initcall update_mp_table+0x0/0x43d returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.254777] calling  lapic_insert_resource+0x0/0x3f @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.254786] initcall lapic_insert_resource+0x0/0x3f returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.254788] calling  print_ICs+0x0/0x1b4 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.254794] initcall print_ICs+0x0/0x1b4 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.254797] calling  pat_memtype_list_init+0x0/0x35 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.254818] initcall pat_memtype_list_init+0x0/0x35 returned 0 after 13 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.254821] calling  create_tlb_single_page_flush_ceiling+0x0/0x29 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.254828] initcall create_tlb_single_page_flush_ceiling+0x0/0x29 returned 0 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.254831] calling  init_oops_id+0x0/0x40 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.254841] initcall init_oops_id+0x0/0x40 returned 0 after 3 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.254843] calling  sched_init_debug+0x0/0x24 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.254850] initcall sched_init_debug+0x0/0x24 returned 0 after 4 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.254852] calling  pm_qos_power_init+0x0/0xb7 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.255099] initcall pm_qos_power_init+0x0/0xb7 returned 0 after 236 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.255101] calling  pm_debugfs_init+0x0/0x24 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.255109] initcall pm_debugfs_init+0x0/0x24 returned 0 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.255112] calling  printk_late_init+0x0/0x75 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.255119] initcall printk_late_init+0x0/0x75 returned 0 after 3 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.255121] calling  tk_debug_sleep_time_init+0x0/0x3c @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.255128] initcall tk_debug_sleep_time_init+0x0/0x3c returned 0 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.255131] calling  debugfs_kprobe_init+0x0/0xa7 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.255141] initcall debugfs_kprobe_init+0x0/0xa7 returned 0 after 4 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.255144] calling  taskstats_init+0x0/0x6e @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.255155] registered taskstats version 1
>Jul 29 06:33:18 IVB102 kernel: [    2.255199] initcall taskstats_init+0x0/0x6e returned 0 after 47 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.255202] calling  clear_boot_tracer+0x0/0x30 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.255210] initcall clear_boot_tracer+0x0/0x30 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.255214] calling  kdb_ftrace_register+0x0/0x32 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.255223] initcall kdb_ftrace_register+0x0/0x32 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.255227] calling  load_system_certificate_list+0x0/0x101 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.255232] Loading compiled-in X.509 certificates
>Jul 29 06:33:18 IVB102 kernel: [    2.259504] Loaded X.509 cert 'Build time autogenerated kernel key: 20102992874ed87c21bc46b9c2e67587bef9558a'
>Jul 29 06:33:18 IVB102 kernel: [    2.259579] initcall load_system_certificate_list+0x0/0x101 returned 0 after 4240 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.259583] calling  fault_around_debugfs+0x0/0x35 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.259595] initcall fault_around_debugfs+0x0/0x35 returned 0 after 5 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.259598] calling  max_swapfiles_check+0x0/0x8 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.259604] initcall max_swapfiles_check+0x0/0x8 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.259607] calling  split_huge_pages_debugfs+0x0/0x35 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.259616] initcall split_huge_pages_debugfs+0x0/0x35 returned 0 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.259619] calling  check_early_ioremap_leak+0x0/0x42 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.259624] initcall check_early_ioremap_leak+0x0/0x42 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.259627] calling  init_root_keyring+0x0/0xb @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.259657] initcall init_root_keyring+0x0/0xb returned 0 after 22 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.259660] calling  big_key_crypto_init+0x0/0xa1 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.262190] initcall big_key_crypto_init+0x0/0xa1 returned -14 after 2458 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.262195] calling  init_trusted+0x0/0xba @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.265120] Key type trusted registered
>Jul 29 06:33:18 IVB102 kernel: [    2.265172] initcall init_trusted+0x0/0xba returned 0 after 2898 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.265176] calling  init_encrypted+0x0/0x11b @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.270370] Key type encrypted registered
>Jul 29 06:33:18 IVB102 kernel: [    2.270423] initcall init_encrypted+0x0/0x11b returned 0 after 5114 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.270427] calling  init_profile_hash+0x0/0x7d @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.270434] AppArmor: AppArmor sha1 policy hashing enabled
>Jul 29 06:33:18 IVB102 kernel: [    2.270479] initcall init_profile_hash+0x0/0x7d returned 0 after 43 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.270482] calling  init_ima+0x0/0x31 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.270487] ima: No TPM chip found, activating TPM-bypass!
>Jul 29 06:33:18 IVB102 kernel: [    2.270556] initcall init_ima+0x0/0x31 returned 0 after 67 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.270560] calling  init_evm+0x0/0x55 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.270565] evm: HMAC attrs: 0x1
>Jul 29 06:33:18 IVB102 kernel: [    2.270610] initcall init_evm+0x0/0x55 returned 0 after 41 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.270612] calling  prandom_reseed+0x0/0x40 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.270643] initcall prandom_reseed+0x0/0x40 returned 0 after 24 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.270646] calling  pci_resource_alignment_sysfs_init+0x0/0x22 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.270657] initcall pci_resource_alignment_sysfs_init+0x0/0x22 returned 0 after 4 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.270659] calling  pci_sysfs_init+0x0/0x49 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.270947] initcall pci_sysfs_init+0x0/0x49 returned 0 after 275 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.270949] calling  boot_wait_for_devices+0x0/0x29 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.270956] initcall boot_wait_for_devices+0x0/0x29 returned -19 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.270959] calling  dmar_free_unused_resources+0x0/0xb5 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.270964] initcall dmar_free_unused_resources+0x0/0xb5 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.270969] calling  deferred_probe_initcall+0x0/0x70 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.271144] initcall deferred_probe_initcall+0x0/0x70 returned 0 after 165 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.271146] calling  late_resume_init+0x0/0x1a0 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.271148]   Magic number: 8:636:566
>Jul 29 06:33:18 IVB102 kernel: [    2.271240] initcall late_resume_init+0x0/0x1a0 returned 0 after 89 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.271241] calling  rtc_hctosys+0x0/0xe7 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.271312] rtc_cmos 00:02: setting system clock to 2016-07-29 04:33:06 UTC (1469766786)
>Jul 29 06:33:18 IVB102 kernel: [    2.271365] initcall rtc_hctosys+0x0/0xe7 returned 0 after 119 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.271366] calling  charger_manager_init+0x0/0x9b @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.271466] initcall charger_manager_init+0x0/0x9b returned 0 after 94 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.271467] calling  acpi_cpufreq_init+0x0/0x27d @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.271470] initcall acpi_cpufreq_init+0x0/0x27d returned -17 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.271482] calling  powernowk8_init+0x0/0x180 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.271487] initcall powernowk8_init+0x0/0x180 returned -19 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.271488] calling  pcc_cpufreq_init+0x0/0x4b3 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.271492] initcall pcc_cpufreq_init+0x0/0x4b3 returned -19 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.271493] calling  centrino_init+0x0/0x2a @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.271497] initcall centrino_init+0x0/0x2a returned -19 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.271498] calling  edd_init+0x0/0x2e5 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.271500] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
>Jul 29 06:33:18 IVB102 kernel: [    2.271545] EDD information not available.
>Jul 29 06:33:18 IVB102 kernel: [    2.271576] initcall edd_init+0x0/0x2e5 returned -19 after 74 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.271577] calling  firmware_memmap_init+0x0/0x33 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.271625] initcall firmware_memmap_init+0x0/0x33 returned 0 after 43 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.271626] calling  efi_shutdown_init+0x0/0x33 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.271629] initcall efi_shutdown_init+0x0/0x33 returned -19 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.271630] calling  clk_debug_init+0x0/0x137 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.271638] initcall clk_debug_init+0x0/0x137 returned 0 after 4 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.271639] calling  pci_mmcfg_late_insert_resources+0x0/0x4b @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.271644] initcall pci_mmcfg_late_insert_resources+0x0/0x4b returned 0 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.271645] calling  register_sk_filter_ops+0x0/0x8 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.271648] initcall register_sk_filter_ops+0x0/0x8 returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.271649] calling  tcp_congestion_default+0x0/0x12 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.271652] initcall tcp_congestion_default+0x0/0x12 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.271653] calling  ip_auto_config+0x0/0xee4 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.271658] initcall ip_auto_config+0x0/0xee4 returned 0 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.271661] calling  software_resume+0x0/0x370 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.271663] PM: Hibernation image not present or could not be loaded.
>Jul 29 06:33:18 IVB102 kernel: [    2.271666] initcall software_resume+0x0/0x370 returned -2 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.271667] calling  regulator_init_complete+0x0/0x1f @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.271671] initcall regulator_init_complete+0x0/0x1f returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.271674] calling  clk_disable_unused+0x0/0x100 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.271678] initcall clk_disable_unused+0x0/0x100 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.271678] calling  init_default_flow_dissectors+0x0/0x50 @ 1
>Jul 29 06:33:18 IVB102 kernel: [    2.271682] initcall init_default_flow_dissectors+0x0/0x50 returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.272276] Freeing unused kernel memory: 1508K (ffffffff81d4a000 - ffffffff81ec3000)
>Jul 29 06:33:18 IVB102 kernel: [    2.272323] Write protecting the kernel read-only data: 12288k
>Jul 29 06:33:18 IVB102 kernel: [    2.272582] Freeing unused kernel memory: 336K (ffff8800017ac000 - ffff880001800000)
>Jul 29 06:33:18 IVB102 kernel: [    2.273955] Freeing unused kernel memory: 472K (ffff880001b8a000 - ffff880001c00000)
>Jul 29 06:33:18 IVB102 kernel: [    2.281639] random: systemd-udevd urandom read with 2 bits of entropy available
>Jul 29 06:33:18 IVB102 kernel: [    2.306145] calling  acpi_wmi_init+0x0/0x1000 [wmi] @ 193
>Jul 29 06:33:18 IVB102 kernel: [    2.306230] wmi: Mapper loaded
>Jul 29 06:33:18 IVB102 kernel: [    2.306269] initcall acpi_wmi_init+0x0/0x1000 [wmi] returned 0 after 114 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.306946] calling  acpi_video_init+0x0/0x1000 [video] @ 190
>Jul 29 06:33:18 IVB102 kernel: [    2.306962] initcall acpi_video_init+0x0/0x1000 [video] returned 0 after 8 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.321282] calling  pps_init+0x0/0x1000 [pps_core] @ 190
>Jul 29 06:33:18 IVB102 kernel: [    2.321295] pps_core: LinuxPPS API ver. 1 registered
>Jul 29 06:33:18 IVB102 kernel: [    2.321336] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
>Jul 29 06:33:18 IVB102 kernel: [    2.321387] initcall pps_init+0x0/0x1000 [pps_core] returned 0 after 93 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.322433] calling  ptp_init+0x0/0x1000 [ptp] @ 190
>Jul 29 06:33:18 IVB102 kernel: [    2.322441] calling  xhci_hcd_init+0x0/0x15 [xhci_hcd] @ 184
>Jul 29 06:33:18 IVB102 kernel: [    2.322449] initcall xhci_hcd_init+0x0/0x15 [xhci_hcd] returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.322449] PTP clock support registered
>Jul 29 06:33:18 IVB102 kernel: [    2.322455] initcall ptp_init+0x0/0x1000 [ptp] returned 0 after 7 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.323445] calling  xhci_pci_init+0x0/0x1000 [xhci_pci] @ 184
>Jul 29 06:33:18 IVB102 kernel: [    2.323750] xhci_hcd 0000:00:14.0: xHCI Host Controller
>Jul 29 06:33:18 IVB102 kernel: [    2.323805] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1
>Jul 29 06:33:18 IVB102 kernel: [    2.324417] calling  ehci_hcd_init+0x0/0x1000 [ehci_hcd] @ 220
>Jul 29 06:33:18 IVB102 kernel: [    2.324438] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
>Jul 29 06:33:18 IVB102 kernel: [    2.324478] Warning! ehci_hcd should always be loaded before uhci_hcd and ohci_hcd, not after
>Jul 29 06:33:18 IVB102 kernel: [    2.324542] initcall ehci_hcd_init+0x0/0x1000 [ehci_hcd] returned 0 after 99 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.324949] xhci_hcd 0000:00:14.0: hcc params 0x20007181 hci version 0x100 quirks 0x0000b930
>Jul 29 06:33:18 IVB102 kernel: [    2.325004] xhci_hcd 0000:00:14.0: cache line size of 64 is not supported
>Jul 29 06:33:18 IVB102 kernel: [    2.325083] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
>Jul 29 06:33:18 IVB102 kernel: [    2.325122] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
>Jul 29 06:33:18 IVB102 kernel: [    2.325176] usb usb1: Product: xHCI Host Controller
>Jul 29 06:33:18 IVB102 kernel: [    2.325212] usb usb1: Manufacturer: Linux 4.7.0-rc7-nightly+ xhci-hcd
>Jul 29 06:33:18 IVB102 kernel: [    2.325255] usb usb1: SerialNumber: 0000:00:14.0
>Jul 29 06:33:18 IVB102 kernel: [    2.325399] hub 1-0:1.0: USB hub found
>Jul 29 06:33:18 IVB102 kernel: [    2.325441] hub 1-0:1.0: 4 ports detected
>Jul 29 06:33:18 IVB102 kernel: [    2.325671] calling  ehci_pci_init+0x0/0x1000 [ehci_pci] @ 220
>Jul 29 06:33:18 IVB102 kernel: [    2.325675] ehci-pci: EHCI PCI platform driver
>Jul 29 06:33:18 IVB102 kernel: [    2.325799] xhci_hcd 0000:00:14.0: xHCI Host Controller
>Jul 29 06:33:18 IVB102 kernel: [    2.325834] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
>Jul 29 06:33:18 IVB102 kernel: [    2.325920] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
>Jul 29 06:33:18 IVB102 kernel: [    2.325964] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
>Jul 29 06:33:18 IVB102 kernel: [    2.326017] usb usb2: Product: xHCI Host Controller
>Jul 29 06:33:18 IVB102 kernel: [    2.326056] usb usb2: Manufacturer: Linux 4.7.0-rc7-nightly+ xhci-hcd
>Jul 29 06:33:18 IVB102 kernel: [    2.326097] usb usb2: SerialNumber: 0000:00:14.0
>Jul 29 06:33:18 IVB102 kernel: [    2.326239] hub 2-0:1.0: USB hub found
>Jul 29 06:33:18 IVB102 kernel: [    2.326288] hub 2-0:1.0: 4 ports detected
>Jul 29 06:33:18 IVB102 kernel: [    2.326677] calling  ahci_pci_driver_init+0x0/0x1000 [ahci] @ 222
>Jul 29 06:33:18 IVB102 kernel: [    2.326732] ehci-pci 0000:00:1a.0: EHCI Host Controller
>Jul 29 06:33:18 IVB102 kernel: [    2.326771] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 3
>Jul 29 06:33:18 IVB102 kernel: [    2.326834] ehci-pci 0000:00:1a.0: debug port 2
>Jul 29 06:33:18 IVB102 kernel: [    2.327099] calling  e1000_init_module+0x0/0x1000 [e1000e] @ 190
>Jul 29 06:33:18 IVB102 kernel: [    2.327102] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
>Jul 29 06:33:18 IVB102 kernel: [    2.327163] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
>Jul 29 06:33:18 IVB102 kernel: [    2.330765] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
>Jul 29 06:33:18 IVB102 kernel: [    2.330781] ehci-pci 0000:00:1a.0: irq 16, io mem 0xf7d38000
>Jul 29 06:33:18 IVB102 kernel: [    2.330862] initcall xhci_pci_init+0x0/0x1000 [xhci_pci] returned 0 after 7234 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.331297] calling  drm_core_init+0x0/0xf3 [drm] @ 193
>Jul 29 06:33:18 IVB102 kernel: [    2.331314] [drm] Initialized drm 1.1.0 20060810
>Jul 29 06:33:18 IVB102 kernel: [    2.331361] initcall drm_core_init+0x0/0xf3 [drm] returned 0 after 45 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.338746] calling  drm_kms_helper_init+0x0/0x14 [drm_kms_helper] @ 193
>Jul 29 06:33:18 IVB102 kernel: [    2.338760] initcall drm_kms_helper_init+0x0/0x14 [drm_kms_helper] returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.340442] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
>Jul 29 06:33:18 IVB102 kernel: [    2.340531] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
>Jul 29 06:33:18 IVB102 kernel: [    2.340577] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
>Jul 29 06:33:18 IVB102 kernel: [    2.340623] usb usb3: Product: EHCI Host Controller
>Jul 29 06:33:18 IVB102 kernel: [    2.340657] usb usb3: Manufacturer: Linux 4.7.0-rc7-nightly+ ehci_hcd
>Jul 29 06:33:18 IVB102 kernel: [    2.340699] usb usb3: SerialNumber: 0000:00:1a.0
>Jul 29 06:33:18 IVB102 kernel: [    2.340924] hub 3-0:1.0: USB hub found
>Jul 29 06:33:18 IVB102 kernel: [    2.340960] hub 3-0:1.0: 2 ports detected
>Jul 29 06:33:18 IVB102 kernel: [    2.341268] ehci-pci 0000:00:1d.0: EHCI Host Controller
>Jul 29 06:33:18 IVB102 kernel: [    2.341314] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 4
>Jul 29 06:33:18 IVB102 kernel: [    2.341375] ehci-pci 0000:00:1d.0: debug port 2
>Jul 29 06:33:18 IVB102 kernel: [    2.345320] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
>Jul 29 06:33:18 IVB102 kernel: [    2.345335] ehci-pci 0000:00:1d.0: irq 23, io mem 0xf7d37000
>Jul 29 06:33:18 IVB102 kernel: [    2.356444] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
>Jul 29 06:33:18 IVB102 kernel: [    2.356537] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002
>Jul 29 06:33:18 IVB102 kernel: [    2.356573] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
>Jul 29 06:33:18 IVB102 kernel: [    2.356634] usb usb4: Product: EHCI Host Controller
>Jul 29 06:33:18 IVB102 kernel: [    2.356675] usb usb4: Manufacturer: Linux 4.7.0-rc7-nightly+ ehci_hcd
>Jul 29 06:33:18 IVB102 kernel: [    2.356719] usb usb4: SerialNumber: 0000:00:1d.0
>Jul 29 06:33:18 IVB102 kernel: [    2.356882] hub 4-0:1.0: USB hub found
>Jul 29 06:33:18 IVB102 kernel: [    2.356924] hub 4-0:1.0: 2 ports detected
>Jul 29 06:33:18 IVB102 kernel: [    2.357135] initcall ehci_pci_init+0x0/0x1000 [ehci_pci] returned 0 after 30720 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.357191] ahci 0000:00:1f.2: version 3.0
>Jul 29 06:33:18 IVB102 kernel: [    2.357341] ahci 0000:00:1f.2: SSS flag set, parallel bus scan disabled
>Jul 29 06:33:18 IVB102 kernel: [    2.358491] calling  i915_init+0x0/0x64 [i915] @ 193
>Jul 29 06:33:18 IVB102 kernel: [    2.367473] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x21 impl SATA mode
>Jul 29 06:33:18 IVB102 kernel: [    2.367527] ahci 0000:00:1f.2: flags: 64bit ncq stag pm led clo pio slum part ems sxs apst 
>Jul 29 06:33:18 IVB102 kernel: [    2.373090] scsi host0: ahci
>Jul 29 06:33:18 IVB102 kernel: [    2.373237] scsi host1: ahci
>Jul 29 06:33:18 IVB102 kernel: [    2.373363] scsi host2: ahci
>Jul 29 06:33:18 IVB102 kernel: [    2.373485] scsi host3: ahci
>Jul 29 06:33:18 IVB102 kernel: [    2.373625] scsi host4: ahci
>Jul 29 06:33:18 IVB102 kernel: [    2.373760] scsi host5: ahci
>Jul 29 06:33:18 IVB102 kernel: [    2.373845] ata1: SATA max UDMA/133 abar m2048@0xf7d36000 port 0xf7d36100 irq 25
>Jul 29 06:33:18 IVB102 kernel: [    2.373906] ata2: DUMMY
>Jul 29 06:33:18 IVB102 kernel: [    2.373941] ata3: DUMMY
>Jul 29 06:33:18 IVB102 kernel: [    2.373975] ata4: DUMMY
>Jul 29 06:33:18 IVB102 kernel: [    2.374009] ata5: DUMMY
>Jul 29 06:33:18 IVB102 kernel: [    2.374039] ata6: SATA max UDMA/133 abar m2048@0xf7d36000 port 0xf7d36380 irq 25
>Jul 29 06:33:18 IVB102 kernel: [    2.374121] initcall ahci_pci_driver_init+0x0/0x1000 [ahci] returned 0 after 46322 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.374241] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
>Jul 29 06:33:18 IVB102 kernel: [    2.518243] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): registered PHC clock
>Jul 29 06:33:18 IVB102 kernel: [    2.643390] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 00:22:4d:80:0b:44
>Jul 29 06:33:18 IVB102 kernel: [    2.643459] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
>Jul 29 06:33:18 IVB102 kernel: [    2.643546] e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: FFFFFF-0FF
>Jul 29 06:33:18 IVB102 kernel: [    2.643620] initcall e1000_init_module+0x0/0x1000 [e1000e] returned 0 after 309093 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.643815] [drm:intel_detect_pch] Found PantherPoint PCH
>Jul 29 06:33:18 IVB102 kernel: [    2.643817] [drm:get_allowed_dc_mask] Allowed DC state mask 00
>Jul 29 06:33:18 IVB102 kernel: [    2.643834] [drm:intel_device_info_dump] i915 device info: gen=7, pciid=0x0162 rev=0x09 flags=need_gfx_hws,is_ivybridge,has_fbc,has_hotplug,has_llc,
>Jul 29 06:33:18 IVB102 kernel: [    2.644084] [drm:intel_device_info_runtime_init] slice total: 0
>Jul 29 06:33:18 IVB102 kernel: [    2.644085] [drm:intel_device_info_runtime_init] subslice total: 0
>Jul 29 06:33:18 IVB102 kernel: [    2.644086] [drm:intel_device_info_runtime_init] subslice per slice: 0
>Jul 29 06:33:18 IVB102 kernel: [    2.644087] [drm:intel_device_info_runtime_init] EU total: 0
>Jul 29 06:33:18 IVB102 kernel: [    2.644087] [drm:intel_device_info_runtime_init] EU per subslice: 0
>Jul 29 06:33:18 IVB102 kernel: [    2.644088] [drm:intel_device_info_runtime_init] has slice power gating: n
>Jul 29 06:33:18 IVB102 kernel: [    2.644089] [drm:intel_device_info_runtime_init] has subslice power gating: n
>Jul 29 06:33:18 IVB102 kernel: [    2.644089] [drm:intel_device_info_runtime_init] has EU power gating: n
>Jul 29 06:33:18 IVB102 kernel: [    2.644090] [drm:intel_sanitize_options] ppgtt mode: 1
>Jul 29 06:33:18 IVB102 kernel: [    2.644091] [drm:intel_sanitize_options] use GPU sempahores? yes
>Jul 29 06:33:18 IVB102 kernel: [    2.644133] [drm:i915_gem_init_stolen] Memory reserved for graphics device: 65536K, usable: 64512K
>Jul 29 06:33:18 IVB102 kernel: [    2.644134] [drm] Memory usable by graphics device = 2048M
>Jul 29 06:33:18 IVB102 kernel: [    2.644182] [drm:i915_ggtt_init_hw] GMADR size = 256M
>Jul 29 06:33:18 IVB102 kernel: [    2.644195] [drm:i915_ggtt_init_hw] GTT stolen size = 64M
>Jul 29 06:33:18 IVB102 kernel: [    2.644196] [drm] Replacing VGA console driver
>Jul 29 06:33:18 IVB102 kernel: [    2.644851] Console: switching to colour dummy device 80x25
>Jul 29 06:33:18 IVB102 kernel: [    2.645127] [drm:intel_opregion_setup] graphic opregion physical addr: 0xda3c0018
>Jul 29 06:33:18 IVB102 kernel: [    2.645131] [drm:intel_opregion_setup] SWSCI supported
>Jul 29 06:33:18 IVB102 kernel: [    2.645153] e1000e 0000:00:19.0 eno1: renamed from eth0
>Jul 29 06:33:18 IVB102 kernel: [    2.651226] [drm:swsci_setup] SWSCI GBDA callbacks 00000cf3, SBCB callbacks 00000241
>Jul 29 06:33:18 IVB102 kernel: [    2.651231] [drm:intel_opregion_setup] Found valid VBT in ACPI OpRegion (Mailbox #4)
>Jul 29 06:33:18 IVB102 kernel: [    2.651270] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
>Jul 29 06:33:18 IVB102 kernel: [    2.651273] [drm] Driver supports precise vblank timestamp query.
>Jul 29 06:33:18 IVB102 kernel: [    2.651276] [drm:init_vbt_defaults] Set default to SSC at 120000 kHz
>Jul 29 06:33:18 IVB102 kernel: [    2.651277] [drm:intel_bios_init] VBT signature "$VBT SNB/IVB-DESKTOP", BDB version 166
>Jul 29 06:33:18 IVB102 kernel: [    2.651278] [drm:parse_general_features] BDB_GENERAL_FEATURES int_tv_support 0 int_crt_support 1 lvds_use_ssc 0 lvds_ssc_freq 120000 display_clock_mode 0 fdi_rx_polarity_inverted 0
>Jul 29 06:33:18 IVB102 kernel: [    2.651279] [drm:parse_general_definitions] crt_ddc_bus_pin: 5
>Jul 29 06:33:18 IVB102 kernel: [    2.653312] [drm:parse_lfp_panel_data] Panel type: 0 (OpRegion)
>Jul 29 06:33:18 IVB102 kernel: [    2.653316] [drm:parse_lfp_panel_data] DRRS supported mode is static
>Jul 29 06:33:18 IVB102 kernel: [    2.653320] [drm:parse_lfp_panel_data] Found panel mode in BIOS VBT tables:
>Jul 29 06:33:18 IVB102 kernel: [    2.653324] [drm:drm_mode_debug_printmodeline] Modeline 0:"640x480" 0 25180 640 648 744 784 480 482 484 509 0x8 0xa
>Jul 29 06:33:18 IVB102 kernel: [    2.653325] [drm:parse_lfp_panel_data] VBT initial LVDS value 300
>Jul 29 06:33:18 IVB102 kernel: [    2.653328] [drm:parse_lfp_backlight] VBT backlight PWM modulation frequency 10000 Hz, active high, min brightness 0, level 255
>Jul 29 06:33:18 IVB102 kernel: [    2.653331] [drm:parse_sdvo_panel_data] Found SDVO panel mode in BIOS VBT tables:
>Jul 29 06:33:18 IVB102 kernel: [    2.653342] [drm:drm_mode_debug_printmodeline] Modeline 0:"1600x1200" 0 162000 1600 1664 1856 2160 1200 1201 1204 1250 0x8 0xa
>Jul 29 06:33:18 IVB102 kernel: [    2.653343] [drm:parse_sdvo_device_mapping] No SDVO device info is found in VBT
>Jul 29 06:33:18 IVB102 kernel: [    2.653345] [drm:parse_driver_features] DRRS State Enabled:1
>Jul 29 06:33:18 IVB102 kernel: [    2.653365] [drm:intel_dsm_pci_probe] no _DSM method for intel device
>Jul 29 06:33:18 IVB102 kernel: [    2.653372] [drm:intel_update_rawclk] rawclk rate: 125000 kHz
>Jul 29 06:33:18 IVB102 kernel: [    2.653373] [drm:intel_power_well_enable] enabling always-on
>Jul 29 06:33:18 IVB102 kernel: [    2.653582] [drm:intel_fbc_init] Sanitized enable_fbc value: 0
>Jul 29 06:33:18 IVB102 kernel: [    2.653585] [drm:intel_print_wm_latency] Primary WM0 latency 12 (1.2 usec)
>Jul 29 06:33:18 IVB102 kernel: [    2.653586] [drm:intel_print_wm_latency] Primary WM1 latency 4 (2.0 usec)
>Jul 29 06:33:18 IVB102 kernel: [    2.653587] [drm:intel_print_wm_latency] Primary WM2 latency 16 (8.0 usec)
>Jul 29 06:33:18 IVB102 kernel: [    2.653589] [drm:intel_print_wm_latency] Primary WM3 latency 32 (16.0 usec)
>Jul 29 06:33:18 IVB102 kernel: [    2.653590] [drm:intel_print_wm_latency] Sprite WM0 latency 12 (1.2 usec)
>Jul 29 06:33:18 IVB102 kernel: [    2.653595] [drm:intel_print_wm_latency] Sprite WM1 latency 4 (2.0 usec)
>Jul 29 06:33:18 IVB102 kernel: [    2.653596] [drm:intel_print_wm_latency] Sprite WM2 latency 16 (8.0 usec)
>Jul 29 06:33:18 IVB102 kernel: [    2.653597] [drm:intel_print_wm_latency] Sprite WM3 latency 32 (16.0 usec)
>Jul 29 06:33:18 IVB102 kernel: [    2.653598] [drm:intel_print_wm_latency] Cursor WM0 latency 12 (1.2 usec)
>Jul 29 06:33:18 IVB102 kernel: [    2.653599] [drm:intel_print_wm_latency] Cursor WM1 latency 4 (2.0 usec)
>Jul 29 06:33:18 IVB102 kernel: [    2.653600] [drm:intel_print_wm_latency] Cursor WM2 latency 16 (8.0 usec)
>Jul 29 06:33:18 IVB102 kernel: [    2.653601] [drm:intel_print_wm_latency] Cursor WM3 latency 64 (32.0 usec)
>Jul 29 06:33:18 IVB102 kernel: [    2.653604] [drm:intel_modeset_init] 3 display pipes available.
>Jul 29 06:33:18 IVB102 kernel: [    2.653617] [drm:intel_update_cdclk] Current CD clock rate: 400000 kHz
>Jul 29 06:33:18 IVB102 kernel: [    2.653620] [drm:intel_update_max_cdclk] Max CD clock rate: 400000 kHz
>Jul 29 06:33:18 IVB102 kernel: [    2.653621] [drm:intel_update_max_cdclk] Max dotclock rate: 360000 kHz
>Jul 29 06:33:18 IVB102 kernel: [    2.653623] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
>Jul 29 06:33:18 IVB102 kernel: [    2.653954] [drm:intel_crt_reset] crt adpa set to 0xf40000
>Jul 29 06:33:18 IVB102 kernel: [    2.653958] [drm:intel_gmbus_force_bit] enabling bit-banging on i915 gmbus dpb. force bit now 1
>Jul 29 06:33:18 IVB102 kernel: [    2.654798] [drm:intel_sdvo_read_byte] i2c transfer returned -6
>Jul 29 06:33:18 IVB102 kernel: [    2.654799] [drm:intel_sdvo_init] No SDVO device found on SDVOB
>Jul 29 06:33:18 IVB102 kernel: [    2.654816] [drm:intel_gmbus_force_bit] disabling bit-banging on i915 gmbus dpb. force bit now 0
>Jul 29 06:33:18 IVB102 kernel: [    2.654820] [drm:intel_hdmi_init_connector] Adding HDMI connector on port B
>Jul 29 06:33:18 IVB102 kernel: [    2.654837] [drm:intel_dp_init_connector] Adding DP connector on port B
>Jul 29 06:33:18 IVB102 kernel: [    2.654849] [drm:intel_hdmi_init_connector] Adding HDMI connector on port C
>Jul 29 06:33:18 IVB102 kernel: [    2.654856] [drm:intel_hdmi_init_connector] Adding HDMI connector on port D
>Jul 29 06:33:18 IVB102 kernel: [    2.654867] [drm:intel_dp_init_connector] Adding DP connector on port C
>Jul 29 06:33:18 IVB102 kernel: [    2.654875] [drm:intel_dp_init_connector] Adding DP connector on port D
>Jul 29 06:33:18 IVB102 kernel: [    2.654881] [drm:ironlake_init_pch_refclk] has_panel 0 has_lvds 0 has_ck505 0 using_ssc_source 0
>Jul 29 06:33:18 IVB102 kernel: [    2.654895] [drm:intel_modeset_readout_hw_state] [CRTC:26:pipe A] hw state readout: enabled
>Jul 29 06:33:18 IVB102 kernel: [    2.654896] [drm:intel_modeset_readout_hw_state] [CRTC:30:pipe B] hw state readout: disabled
>Jul 29 06:33:18 IVB102 kernel: [    2.654897] [drm:intel_modeset_readout_hw_state] [CRTC:34:pipe C] hw state readout: disabled
>Jul 29 06:33:18 IVB102 kernel: [    2.654903] [drm:intel_modeset_readout_hw_state] PCH DPLL A hw state readout: crtc_mask 0x00000001, on 1
>Jul 29 06:33:18 IVB102 kernel: [    2.654907] [drm:intel_modeset_readout_hw_state] PCH DPLL B hw state readout: crtc_mask 0x00000000, on 0
>Jul 29 06:33:18 IVB102 kernel: [    2.654909] [drm:intel_modeset_readout_hw_state] [ENCODER:37:CRT] hw state readout: disabled, pipe A
>Jul 29 06:33:18 IVB102 kernel: [    2.654912] [drm:intel_modeset_readout_hw_state] [ENCODER:38:HDMI B] hw state readout: disabled, pipe A
>Jul 29 06:33:18 IVB102 kernel: [    2.654915] [drm:intel_modeset_readout_hw_state] [ENCODER:43:DP B] hw state readout: disabled, pipe A
>Jul 29 06:33:18 IVB102 kernel: [    2.654917] [drm:intel_modeset_readout_hw_state] [ENCODER:45:HDMI C] hw state readout: disabled, pipe A
>Jul 29 06:33:18 IVB102 kernel: [    2.654919] [drm:intel_modeset_readout_hw_state] [ENCODER:47:HDMI D] hw state readout: disabled, pipe A
>Jul 29 06:33:18 IVB102 kernel: [    2.654926] [drm:intel_modeset_readout_hw_state] [ENCODER:49:DP C] hw state readout: enabled, pipe A
>Jul 29 06:33:18 IVB102 kernel: [    2.654929] [drm:intel_modeset_readout_hw_state] [ENCODER:51:DP D] hw state readout: disabled, pipe A
>Jul 29 06:33:18 IVB102 kernel: [    2.654931] [drm:intel_modeset_readout_hw_state] [CONNECTOR:36:VGA-1] hw state readout: disabled
>Jul 29 06:33:18 IVB102 kernel: [    2.654933] [drm:intel_modeset_readout_hw_state] [CONNECTOR:39:HDMI-A-1] hw state readout: disabled
>Jul 29 06:33:18 IVB102 kernel: [    2.654936] [drm:intel_modeset_readout_hw_state] [CONNECTOR:44:DP-1] hw state readout: disabled
>Jul 29 06:33:18 IVB102 kernel: [    2.654937] [drm:intel_modeset_readout_hw_state] [CONNECTOR:46:HDMI-A-2] hw state readout: disabled
>Jul 29 06:33:18 IVB102 kernel: [    2.654939] [drm:intel_modeset_readout_hw_state] [CONNECTOR:48:HDMI-A-3] hw state readout: disabled
>Jul 29 06:33:18 IVB102 kernel: [    2.654941] [drm:intel_modeset_readout_hw_state] [CONNECTOR:50:DP-2] hw state readout: enabled
>Jul 29 06:33:18 IVB102 kernel: [    2.654944] [drm:intel_modeset_readout_hw_state] [CONNECTOR:52:DP-3] hw state readout: disabled
>Jul 29 06:33:18 IVB102 kernel: [    2.654952] [drm:intel_dump_pipe_config] [CRTC:26:pipe A][setup_hw_state] config ffff8807f4234800 for pipe A
>Jul 29 06:33:18 IVB102 kernel: [    2.654953] [drm:intel_dump_pipe_config] cpu_transcoder: A
>Jul 29 06:33:18 IVB102 kernel: [    2.654954] [drm:intel_dump_pipe_config] pipe bpp: 24, dithering: 0
>Jul 29 06:33:18 IVB102 kernel: [    2.654955] [drm:intel_dump_pipe_config] fdi/pch: 1, lanes: 1, gmch_m: 2346946, gmch_n: 8388608, link_m: 48894, link_n: 524288, tu: 64
>Jul 29 06:33:18 IVB102 kernel: [    2.654956] [drm:intel_dump_pipe_config] dp: 1, lanes: 4, gmch_m: 586736, gmch_n: 8388608, link_m: 48894, link_n: 524288, tu: 64
>Jul 29 06:33:18 IVB102 kernel: [    2.654957] [drm:intel_dump_pipe_config] dp: 1, lanes: 4, gmch_m2: 0, gmch_n2: 0, link_m2: 0, link_n2: 0, tu2: 0
>Jul 29 06:33:18 IVB102 kernel: [    2.654957] [drm:intel_dump_pipe_config] audio: 0, infoframes: 0
>Jul 29 06:33:18 IVB102 kernel: [    2.654958] [drm:intel_dump_pipe_config] requested mode:
>Jul 29 06:33:18 IVB102 kernel: [    2.654959] [drm:drm_mode_debug_printmodeline] Modeline 0:"640x480" 60 25179 640 656 752 800 480 490 492 525 0x40 0x5
>Jul 29 06:33:18 IVB102 kernel: [    2.654960] [drm:intel_dump_pipe_config] adjusted mode:
>Jul 29 06:33:18 IVB102 kernel: [    2.654961] [drm:drm_mode_debug_printmodeline] Modeline 0:"640x480" 60 25179 640 656 752 800 480 490 492 525 0x40 0x5
>Jul 29 06:33:18 IVB102 kernel: [    2.654962] [drm:intel_dump_crtc_timings] crtc timings: 25179 640 656 752 800 480 490 492 525, type: 0x40 flags: 0x5
>Jul 29 06:33:18 IVB102 kernel: [    2.654963] [drm:intel_dump_pipe_config] port clock: 270000
>Jul 29 06:33:18 IVB102 kernel: [    2.654963] [drm:intel_dump_pipe_config] pipe src size: 720x400
>Jul 29 06:33:18 IVB102 kernel: [    2.654964] [drm:intel_dump_pipe_config] num_scalers: 0, scaler_users: 0x0, scaler_id: 0
>Jul 29 06:33:18 IVB102 kernel: [    2.654965] [drm:intel_dump_pipe_config] gmch pfit: control: 0x00000000, ratios: 0x00000000, lvds border: 0x00000000
>Jul 29 06:33:18 IVB102 kernel: [    2.654966] [drm:intel_dump_pipe_config] pch pfit: pos: 0x00000000, size: 0x028001e0, enabled
>Jul 29 06:33:18 IVB102 kernel: [    2.654966] [drm:intel_dump_pipe_config] ips: 0
>Jul 29 06:33:18 IVB102 kernel: [    2.654967] [drm:intel_dump_pipe_config] double wide: 0
>Jul 29 06:33:18 IVB102 kernel: [    2.654968] [drm:intel_dump_pipe_config] dpll_hw_state: dpll: 0xc4010001, dpll_md: 0x0, fp0: 0x20e08, fp1: 0x30d07
>Jul 29 06:33:18 IVB102 kernel: [    2.654968] [drm:intel_dump_pipe_config] planes on this crtc
>Jul 29 06:33:18 IVB102 kernel: [    2.654969] [drm:intel_dump_pipe_config] [PLANE:23:primary A] disabled, scaler_id = 0
>Jul 29 06:33:18 IVB102 kernel: [    2.654970] [drm:intel_dump_pipe_config] [PLANE:25:cursor A] disabled, scaler_id = 0
>Jul 29 06:33:18 IVB102 kernel: [    2.654971] [drm:intel_dump_pipe_config] [PLANE:27:sprite A] disabled, scaler_id = 0
>Jul 29 06:33:18 IVB102 kernel: [    2.654972] [drm:intel_dump_pipe_config] [CRTC:30:pipe B][setup_hw_state] config ffff8807f4235800 for pipe B
>Jul 29 06:33:18 IVB102 kernel: [    2.654972] [drm:intel_dump_pipe_config] cpu_transcoder: B
>Jul 29 06:33:18 IVB102 kernel: [    2.654973] [drm:intel_dump_pipe_config] pipe bpp: 0, dithering: 0
>Jul 29 06:33:18 IVB102 kernel: [    2.654974] [drm:intel_dump_pipe_config] fdi/pch: 0, lanes: 0, gmch_m: 0, gmch_n: 0, link_m: 0, link_n: 0, tu: 0
>Jul 29 06:33:18 IVB102 kernel: [    2.654975] [drm:intel_dump_pipe_config] dp: 0, lanes: 0, gmch_m: 0, gmch_n: 0, link_m: 0, link_n: 0, tu: 0
>Jul 29 06:33:18 IVB102 kernel: [    2.654976] [drm:intel_dump_pipe_config] dp: 0, lanes: 0, gmch_m2: 0, gmch_n2: 0, link_m2: 0, link_n2: 0, tu2: 0
>Jul 29 06:33:18 IVB102 kernel: [    2.654977] [drm:intel_dump_pipe_config] audio: 0, infoframes: 0
>Jul 29 06:33:18 IVB102 kernel: [    2.654977] [drm:intel_dump_pipe_config] requested mode:
>Jul 29 06:33:18 IVB102 kernel: [    2.654978] [drm:drm_mode_debug_printmodeline] Modeline 0:"" 0 0 0 0 0 0 0 0 0 0 0x0 0x0
>Jul 29 06:33:18 IVB102 kernel: [    2.654979] [drm:intel_dump_pipe_config] adjusted mode:
>Jul 29 06:33:18 IVB102 kernel: [    2.654980] [drm:drm_mode_debug_printmodeline] Modeline 0:"" 0 0 0 0 0 0 0 0 0 0 0x0 0x0
>Jul 29 06:33:18 IVB102 kernel: [    2.654981] [drm:intel_dump_crtc_timings] crtc timings: 0 0 0 0 0 0 0 0 0, type: 0x0 flags: 0x0
>Jul 29 06:33:18 IVB102 kernel: [    2.654982] [drm:intel_dump_pipe_config] port clock: 0
>Jul 29 06:33:18 IVB102 kernel: [    2.654982] [drm:intel_dump_pipe_config] pipe src size: 0x0
>Jul 29 06:33:18 IVB102 kernel: [    2.654983] [drm:intel_dump_pipe_config] num_scalers: 0, scaler_users: 0x0, scaler_id: 0
>Jul 29 06:33:18 IVB102 kernel: [    2.654984] [drm:intel_dump_pipe_config] gmch pfit: control: 0x00000000, ratios: 0x00000000, lvds border: 0x00000000
>Jul 29 06:33:18 IVB102 kernel: [    2.654984] [drm:intel_dump_pipe_config] pch pfit: pos: 0x00000000, size: 0x00000000, disabled
>Jul 29 06:33:18 IVB102 kernel: [    2.654985] [drm:intel_dump_pipe_config] ips: 0
>Jul 29 06:33:18 IVB102 kernel: [    2.654986] [drm:intel_dump_pipe_config] double wide: 0
>Jul 29 06:33:18 IVB102 kernel: [    2.654986] [drm:intel_dump_pipe_config] dpll_hw_state: dpll: 0x0, dpll_md: 0x0, fp0: 0x0, fp1: 0x0
>Jul 29 06:33:18 IVB102 kernel: [    2.654987] [drm:intel_dump_pipe_config] planes on this crtc
>Jul 29 06:33:18 IVB102 kernel: [    2.654988] [drm:intel_dump_pipe_config] [PLANE:28:primary B] disabled, scaler_id = 0
>Jul 29 06:33:18 IVB102 kernel: [    2.654988] [drm:intel_dump_pipe_config] [PLANE:29:cursor B] disabled, scaler_id = 0
>Jul 29 06:33:18 IVB102 kernel: [    2.654989] [drm:intel_dump_pipe_config] [PLANE:31:sprite B] disabled, scaler_id = 0
>Jul 29 06:33:18 IVB102 kernel: [    2.654990] [drm:intel_dump_pipe_config] [CRTC:34:pipe C][setup_hw_state] config ffff8807f4236800 for pipe C
>Jul 29 06:33:18 IVB102 kernel: [    2.654991] [drm:intel_dump_pipe_config] cpu_transcoder: C
>Jul 29 06:33:18 IVB102 kernel: [    2.654991] [drm:intel_dump_pipe_config] pipe bpp: 0, dithering: 0
>Jul 29 06:33:18 IVB102 kernel: [    2.654992] [drm:intel_dump_pipe_config] fdi/pch: 0, lanes: 0, gmch_m: 0, gmch_n: 0, link_m: 0, link_n: 0, tu: 0
>Jul 29 06:33:18 IVB102 kernel: [    2.654993] [drm:intel_dump_pipe_config] dp: 0, lanes: 0, gmch_m: 0, gmch_n: 0, link_m: 0, link_n: 0, tu: 0
>Jul 29 06:33:18 IVB102 kernel: [    2.654994] [drm:intel_dump_pipe_config] dp: 0, lanes: 0, gmch_m2: 0, gmch_n2: 0, link_m2: 0, link_n2: 0, tu2: 0
>Jul 29 06:33:18 IVB102 kernel: [    2.654995] [drm:intel_dump_pipe_config] audio: 0, infoframes: 0
>Jul 29 06:33:18 IVB102 kernel: [    2.654995] [drm:intel_dump_pipe_config] requested mode:
>Jul 29 06:33:18 IVB102 kernel: [    2.654996] [drm:drm_mode_debug_printmodeline] Modeline 0:"" 0 0 0 0 0 0 0 0 0 0 0x0 0x0
>Jul 29 06:33:18 IVB102 kernel: [    2.654997] [drm:intel_dump_pipe_config] adjusted mode:
>Jul 29 06:33:18 IVB102 kernel: [    2.654998] [drm:drm_mode_debug_printmodeline] Modeline 0:"" 0 0 0 0 0 0 0 0 0 0 0x0 0x0
>Jul 29 06:33:18 IVB102 kernel: [    2.654999] [drm:intel_dump_crtc_timings] crtc timings: 0 0 0 0 0 0 0 0 0, type: 0x0 flags: 0x0
>Jul 29 06:33:18 IVB102 kernel: [    2.654999] [drm:intel_dump_pipe_config] port clock: 0
>Jul 29 06:33:18 IVB102 kernel: [    2.655000] [drm:intel_dump_pipe_config] pipe src size: 0x0
>Jul 29 06:33:18 IVB102 kernel: [    2.655001] [drm:intel_dump_pipe_config] num_scalers: 0, scaler_users: 0x0, scaler_id: 0
>Jul 29 06:33:18 IVB102 kernel: [    2.655002] [drm:intel_dump_pipe_config] gmch pfit: control: 0x00000000, ratios: 0x00000000, lvds border: 0x00000000
>Jul 29 06:33:18 IVB102 kernel: [    2.655002] [drm:intel_dump_pipe_config] pch pfit: pos: 0x00000000, size: 0x00000000, disabled
>Jul 29 06:33:18 IVB102 kernel: [    2.655003] [drm:intel_dump_pipe_config] ips: 0
>Jul 29 06:33:18 IVB102 kernel: [    2.655003] [drm:intel_dump_pipe_config] double wide: 0
>Jul 29 06:33:18 IVB102 kernel: [    2.655004] [drm:intel_dump_pipe_config] dpll_hw_state: dpll: 0x0, dpll_md: 0x0, fp0: 0x0, fp1: 0x0
>Jul 29 06:33:18 IVB102 kernel: [    2.655005] [drm:intel_dump_pipe_config] planes on this crtc
>Jul 29 06:33:18 IVB102 kernel: [    2.655005] [drm:intel_dump_pipe_config] [PLANE:32:primary C] disabled, scaler_id = 0
>Jul 29 06:33:18 IVB102 kernel: [    2.655006] [drm:intel_dump_pipe_config] [PLANE:33:cursor C] disabled, scaler_id = 0
>Jul 29 06:33:18 IVB102 kernel: [    2.655007] [drm:intel_dump_pipe_config] [PLANE:35:sprite C] disabled, scaler_id = 0
>Jul 29 06:33:18 IVB102 kernel: [    2.655214] [drm:i915_gem_setup_global_gtt] clearing unused GTT space: [0, 7ffff000]
>Jul 29 06:33:18 IVB102 kernel: [    2.656417] usb 3-1: new high-speed USB device number 2 using ehci-pci
>Jul 29 06:33:18 IVB102 kernel: [    2.656492] [drm:gen6_ppgtt_init] Allocated pde space (2M) at GTT entry: 7fdf0
>Jul 29 06:33:18 IVB102 kernel: [    2.657050] [drm:i915_gem_context_init] HW context support initialized
>Jul 29 06:33:18 IVB102 kernel: [    2.657229] [drm:init_status_page] render ring hws offset: 0x7fff2000
>Jul 29 06:33:18 IVB102 kernel: [    2.657251] [drm:i915_gem_object_create_stolen] creating stolen object: size=1000
>Jul 29 06:33:18 IVB102 kernel: [    2.657253] [drm:i915_pages_create_for_stolen] offset=0x0, size=4096
>Jul 29 06:33:18 IVB102 kernel: [    2.657254] [drm:intel_init_pipe_control] render ring pipe control offset: 0x00000000
>Jul 29 06:33:18 IVB102 kernel: [    2.657402] [drm:init_status_page] blitter ring hws offset: 0x00021000
>Jul 29 06:33:18 IVB102 kernel: [    2.657506] [drm:init_status_page] bsd ring hws offset: 0x00042000
>Jul 29 06:33:18 IVB102 kernel: [    2.657563] [drm:intel_guc_setup] GuC fw status: path (null), fetch NONE, load NONE
>Jul 29 06:33:18 IVB102 kernel: [    2.657571] [drm:intel_init_gt_powersave] Overclocking supported, max: 1150MHz, overclock: 1150MHz
>Jul 29 06:33:18 IVB102 kernel: [    2.657572] [drm:intel_update_cdclk] Current CD clock rate: 400000 kHz
>Jul 29 06:33:18 IVB102 kernel: [    2.657590] [drm:intel_fbdev_init_bios] pipe A not active or no fb, skipping
>Jul 29 06:33:18 IVB102 kernel: [    2.657591] [drm:intel_fbdev_init_bios] pipe B not active or no fb, skipping
>Jul 29 06:33:18 IVB102 kernel: [    2.657591] [drm:intel_fbdev_init_bios] pipe C not active or no fb, skipping
>Jul 29 06:33:18 IVB102 kernel: [    2.657592] [drm:intel_fbdev_init_bios] no active fbs found, not using BIOS config
>Jul 29 06:33:18 IVB102 kernel: [    2.657605] [drm:intel_crt_detect] [CONNECTOR:36:VGA-1] force=0
>Jul 29 06:33:18 IVB102 kernel: [    2.657608] [drm:intel_ironlake_crt_detect_hotplug] trigger hotplug detect cycle: adpa=0xf40000
>Jul 29 06:33:18 IVB102 kernel: [    2.667546] [drm:intel_ironlake_crt_detect_hotplug] ironlake hotplug adpa=0xf40000, result 0
>Jul 29 06:33:18 IVB102 kernel: [    2.667550] [drm:intel_crt_detect] CRT not detected via hotplug
>Jul 29 06:33:18 IVB102 kernel: [    2.667781] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpb] NAK for addr: 0050 w(1)
>Jul 29 06:33:18 IVB102 kernel: [    2.667784] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpb] NAK on first message, retry
>Jul 29 06:33:18 IVB102 kernel: [    2.668043] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpb] NAK for addr: 0050 w(1)
>Jul 29 06:33:18 IVB102 kernel: [    2.668045] [drm:drm_do_probe_ddc_edid] drm: skipping non-existent adapter i915 gmbus dpb
>Jul 29 06:33:18 IVB102 kernel: [    2.668046] [drm:intel_crt_get_edid] CRT GMBUS EDID read failed, retry using GPIO bit-banging
>Jul 29 06:33:18 IVB102 kernel: [    2.668047] [drm:intel_gmbus_force_bit] enabling bit-banging on i915 gmbus dpb. force bit now 1
>Jul 29 06:33:18 IVB102 kernel: [    2.668832] [drm:drm_do_probe_ddc_edid] drm: skipping non-existent adapter i915 gmbus dpb
>Jul 29 06:33:18 IVB102 kernel: [    2.668833] [drm:intel_gmbus_force_bit] disabling bit-banging on i915 gmbus dpb. force bit now 0
>Jul 29 06:33:18 IVB102 kernel: [    2.668833] [drm:intel_crt_detect_ddc] CRT not detected via DDC:0x50 [no valid EDID found]
>Jul 29 06:33:18 IVB102 kernel: [    2.668835] [drm:drm_helper_hpd_irq_event] [CONNECTOR:36:VGA-1] status updated from unknown to disconnected
>Jul 29 06:33:18 IVB102 kernel: [    2.668836] [drm:intel_hdmi_detect] [CONNECTOR:39:HDMI-A-1]
>Jul 29 06:33:18 IVB102 kernel: [    2.672433] usb 4-1: new high-speed USB device number 2 using ehci-pci
>Jul 29 06:33:18 IVB102 kernel: [    2.682995] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
>Jul 29 06:33:18 IVB102 kernel: [    2.684437] ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
>Jul 29 06:33:18 IVB102 kernel: [    2.684442] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
>Jul 29 06:33:18 IVB102 kernel: [    2.684453] ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
>Jul 29 06:33:18 IVB102 kernel: [    2.685796] ata1.00: ATA-8: ST250DM000-1BD141, KC45, max UDMA/133
>Jul 29 06:33:18 IVB102 kernel: [    2.685805] ata1.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 31/32)
>Jul 29 06:33:18 IVB102 kernel: [    2.687488] ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
>Jul 29 06:33:18 IVB102 kernel: [    2.687493] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
>Jul 29 06:33:18 IVB102 kernel: [    2.687504] ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
>Jul 29 06:33:18 IVB102 kernel: [    2.688799] ata1.00: configured for UDMA/133
>Jul 29 06:33:18 IVB102 kernel: [    2.689100] scsi 0:0:0:0: Direct-Access     ATA      ST250DM000-1BD14 KC45 PQ: 0 ANSI: 5
>Jul 29 06:33:18 IVB102 kernel: [    2.704707] sd 0:0:0:0: [sda] 488397168 512-byte logical blocks: (250 GB/233 GiB)
>Jul 29 06:33:18 IVB102 kernel: [    2.704709] sd 0:0:0:0: Attached scsi generic sg0 type 0
>Jul 29 06:33:18 IVB102 kernel: [    2.704714] sd 0:0:0:0: [sda] 4096-byte physical blocks
>Jul 29 06:33:18 IVB102 kernel: [    2.704832] sd 0:0:0:0: [sda] Write Protect is off
>Jul 29 06:33:18 IVB102 kernel: [    2.704839] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
>Jul 29 06:33:18 IVB102 kernel: [    2.704880] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
>Jul 29 06:33:18 IVB102 kernel: [    2.720549]  sda: sda1 sda2 sda3
>Jul 29 06:33:18 IVB102 kernel: [    2.721357] sd 0:0:0:0: [sda] Attached SCSI disk
>Jul 29 06:33:18 IVB102 kernel: [    2.788749] usb 3-1: New USB device found, idVendor=8087, idProduct=0024
>Jul 29 06:33:18 IVB102 kernel: [    2.788758] usb 3-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
>Jul 29 06:33:18 IVB102 kernel: [    2.789030] hub 3-1:1.0: USB hub found
>Jul 29 06:33:18 IVB102 kernel: [    2.789116] hub 3-1:1.0: 6 ports detected
>Jul 29 06:33:18 IVB102 kernel: [    2.796441] [drm:intel_hdmi_detect] HDMI live status down
>Jul 29 06:33:18 IVB102 kernel: [    2.796665] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpb] NAK for addr: 0050 w(1)
>Jul 29 06:33:18 IVB102 kernel: [    2.796667] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpb] NAK on first message, retry
>Jul 29 06:33:18 IVB102 kernel: [    2.796929] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpb] NAK for addr: 0050 w(1)
>Jul 29 06:33:18 IVB102 kernel: [    2.796931] [drm:drm_do_probe_ddc_edid] drm: skipping non-existent adapter i915 gmbus dpb
>Jul 29 06:33:18 IVB102 kernel: [    2.797189] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpb] NAK for addr: 0040 w(1)
>Jul 29 06:33:18 IVB102 kernel: [    2.797190] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpb] NAK on first message, retry
>Jul 29 06:33:18 IVB102 kernel: [    2.797428] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpb] NAK for addr: 0040 w(1)
>Jul 29 06:33:18 IVB102 kernel: [    2.797430] [drm:drm_helper_hpd_irq_event] [CONNECTOR:39:HDMI-A-1] status updated from unknown to disconnected
>Jul 29 06:33:18 IVB102 kernel: [    2.797431] [drm:intel_dp_detect] [CONNECTOR:44:DP-1]
>Jul 29 06:33:18 IVB102 kernel: [    2.797435] [drm:drm_helper_hpd_irq_event] [CONNECTOR:44:DP-1] status updated from unknown to disconnected
>Jul 29 06:33:18 IVB102 kernel: [    2.797435] [drm:intel_hdmi_detect] [CONNECTOR:46:HDMI-A-2]
>Jul 29 06:33:18 IVB102 kernel: [    2.797697] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpc] NAK for addr: 0050 w(1)
>Jul 29 06:33:18 IVB102 kernel: [    2.797698] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpc] NAK on first message, retry
>Jul 29 06:33:18 IVB102 kernel: [    2.797959] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpc] NAK for addr: 0050 w(1)
>Jul 29 06:33:18 IVB102 kernel: [    2.797961] [drm:drm_do_probe_ddc_edid] drm: skipping non-existent adapter i915 gmbus dpc
>Jul 29 06:33:18 IVB102 kernel: [    2.798224] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpc] NAK for addr: 0040 w(1)
>Jul 29 06:33:18 IVB102 kernel: [    2.798226] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpc] NAK on first message, retry
>Jul 29 06:33:18 IVB102 kernel: [    2.798391] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpc] NAK for addr: 0040 w(1)
>Jul 29 06:33:18 IVB102 kernel: [    2.798395] [drm:drm_helper_hpd_irq_event] [CONNECTOR:46:HDMI-A-2] status updated from unknown to disconnected
>Jul 29 06:33:18 IVB102 kernel: [    2.798397] [drm:intel_hdmi_detect] [CONNECTOR:48:HDMI-A-3]
>Jul 29 06:33:18 IVB102 kernel: [    2.804750] usb 4-1: New USB device found, idVendor=8087, idProduct=0024
>Jul 29 06:33:18 IVB102 kernel: [    2.804759] usb 4-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
>Jul 29 06:33:18 IVB102 kernel: [    2.805029] hub 4-1:1.0: USB hub found
>Jul 29 06:33:18 IVB102 kernel: [    2.805119] hub 4-1:1.0: 8 ports detected
>Jul 29 06:33:18 IVB102 kernel: [    2.924437] [drm:intel_hdmi_detect] HDMI live status down
>Jul 29 06:33:18 IVB102 kernel: [    2.924713] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpd] NAK for addr: 0050 w(1)
>Jul 29 06:33:18 IVB102 kernel: [    2.924715] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpd] NAK on first message, retry
>Jul 29 06:33:18 IVB102 kernel: [    2.924984] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpd] NAK for addr: 0050 w(1)
>Jul 29 06:33:18 IVB102 kernel: [    2.924986] [drm:drm_do_probe_ddc_edid] drm: skipping non-existent adapter i915 gmbus dpd
>Jul 29 06:33:18 IVB102 kernel: [    2.925249] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpd] NAK for addr: 0040 w(1)
>Jul 29 06:33:18 IVB102 kernel: [    2.925250] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpd] NAK on first message, retry
>Jul 29 06:33:18 IVB102 kernel: [    2.925523] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpd] NAK for addr: 0040 w(1)
>Jul 29 06:33:18 IVB102 kernel: [    2.925525] [drm:drm_helper_hpd_irq_event] [CONNECTOR:48:HDMI-A-3] status updated from unknown to disconnected
>Jul 29 06:33:18 IVB102 kernel: [    2.925526] [drm:intel_dp_detect] [CONNECTOR:50:DP-2]
>Jul 29 06:33:18 IVB102 kernel: [    2.925978] [drm:intel_dp_get_dpcd] DPCD: 11 0a 84 01 01 00 01 01 02 00 00 00 00 00 00
>Jul 29 06:33:18 IVB102 kernel: [    2.926303] [drm:intel_dp_get_dpcd] Display Port TPS3 support: source no, sink no
>Jul 29 06:33:18 IVB102 kernel: [    2.926307] [drm:intel_dp_print_rates] source rates: 162000, 270000
>Jul 29 06:33:18 IVB102 kernel: [    2.926308] [drm:intel_dp_print_rates] sink rates: 162000, 270000
>Jul 29 06:33:18 IVB102 kernel: [    2.926309] [drm:intel_dp_print_rates] common rates: 162000, 270000
>Jul 29 06:33:18 IVB102 kernel: [    2.932071] [drm:drm_helper_hpd_irq_event] [CONNECTOR:50:DP-2] status updated from unknown to connected
>Jul 29 06:33:18 IVB102 kernel: [    2.932075] [drm:intel_dp_detect] [CONNECTOR:52:DP-3]
>Jul 29 06:33:18 IVB102 kernel: [    2.932082] [drm:drm_helper_hpd_irq_event] [CONNECTOR:52:DP-3] status updated from unknown to disconnected
>Jul 29 06:33:18 IVB102 kernel: [    2.932342] [drm:intel_dp_connector_register] registering DPDDC-B bus for card0-DP-1
>Jul 29 06:33:18 IVB102 kernel: [    2.932433] [drm:intel_dp_connector_register] registering DPDDC-C bus for card0-DP-2
>Jul 29 06:33:18 IVB102 kernel: [    2.932460] [drm:intel_dp_connector_register] registering DPDDC-D bus for card0-DP-3
>Jul 29 06:33:18 IVB102 kernel: [    2.932745] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
>Jul 29 06:33:18 IVB102 kernel: [    2.932887] acpi device:49: registered as cooling_device13
>Jul 29 06:33:18 IVB102 kernel: [    2.932929] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input2
>Jul 29 06:33:18 IVB102 kernel: [    2.932981] [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:36:VGA-1]
>Jul 29 06:33:18 IVB102 kernel: [    2.932993] [drm:intel_crt_detect] [CONNECTOR:36:VGA-1] force=1
>Jul 29 06:33:18 IVB102 kernel: [    2.932997] [drm:intel_ironlake_crt_detect_hotplug] ironlake hotplug adpa=0xf40000, result 0
>Jul 29 06:33:18 IVB102 kernel: [    2.933026] initcall i915_init+0x0/0x64 [i915] returned 0 after 561061 usecs
>Jul 29 06:33:18 IVB102 kernel: [    2.933028] [drm:intel_crt_detect] CRT not detected via hotplug
>Jul 29 06:33:18 IVB102 kernel: [    2.933192] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpb] NAK for addr: 0050 w(1)
>Jul 29 06:33:18 IVB102 kernel: [    2.933194] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpb] NAK on first message, retry
>Jul 29 06:33:18 IVB102 kernel: [    2.933352] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpb] NAK for addr: 0050 w(1)
>Jul 29 06:33:18 IVB102 kernel: [    2.933353] [drm:drm_do_probe_ddc_edid] drm: skipping non-existent adapter i915 gmbus dpb
>Jul 29 06:33:18 IVB102 kernel: [    2.933355] [drm:intel_crt_get_edid] CRT GMBUS EDID read failed, retry using GPIO bit-banging
>Jul 29 06:33:18 IVB102 kernel: [    2.933356] [drm:intel_gmbus_force_bit] enabling bit-banging on i915 gmbus dpb. force bit now 1
>Jul 29 06:33:18 IVB102 kernel: [    2.934180] [drm:drm_do_probe_ddc_edid] drm: skipping non-existent adapter i915 gmbus dpb
>Jul 29 06:33:18 IVB102 kernel: [    2.934182] [drm:intel_gmbus_force_bit] disabling bit-banging on i915 gmbus dpb. force bit now 0
>Jul 29 06:33:18 IVB102 kernel: [    2.934182] [drm:intel_crt_detect_ddc] CRT not detected via DDC:0x50 [no valid EDID found]
>Jul 29 06:33:18 IVB102 kernel: [    2.934184] [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:36:VGA-1] disconnected
>Jul 29 06:33:18 IVB102 kernel: [    2.934185] [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:39:HDMI-A-1]
>Jul 29 06:33:18 IVB102 kernel: [    2.934186] [drm:intel_hdmi_detect] [CONNECTOR:39:HDMI-A-1]
>Jul 29 06:33:18 IVB102 kernel: [    3.015105] ata6: SATA link down (SStatus 0 SControl 300)
>Jul 29 06:33:18 IVB102 kernel: [    3.060429] [drm:intel_hdmi_detect] HDMI live status down
>Jul 29 06:33:18 IVB102 kernel: [    3.060667] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpb] NAK for addr: 0050 w(1)
>Jul 29 06:33:18 IVB102 kernel: [    3.060671] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpb] NAK on first message, retry
>Jul 29 06:33:18 IVB102 kernel: [    3.060877] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpb] NAK for addr: 0050 w(1)
>Jul 29 06:33:18 IVB102 kernel: [    3.060882] [drm:drm_do_probe_ddc_edid] drm: skipping non-existent adapter i915 gmbus dpb
>Jul 29 06:33:18 IVB102 kernel: [    3.061121] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpb] NAK for addr: 0040 w(1)
>Jul 29 06:33:18 IVB102 kernel: [    3.061125] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpb] NAK on first message, retry
>Jul 29 06:33:18 IVB102 kernel: [    3.061333] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpb] NAK for addr: 0040 w(1)
>Jul 29 06:33:18 IVB102 kernel: [    3.061339] [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:39:HDMI-A-1] disconnected
>Jul 29 06:33:18 IVB102 kernel: [    3.061341] [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:44:DP-1]
>Jul 29 06:33:18 IVB102 kernel: [    3.061352] [drm:intel_dp_detect] [CONNECTOR:44:DP-1]
>Jul 29 06:33:18 IVB102 kernel: [    3.061357] [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:44:DP-1] disconnected
>Jul 29 06:33:18 IVB102 kernel: [    3.061358] [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:46:HDMI-A-2]
>Jul 29 06:33:18 IVB102 kernel: [    3.061359] [drm:intel_hdmi_detect] [CONNECTOR:46:HDMI-A-2]
>Jul 29 06:33:18 IVB102 kernel: [    3.061587] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpc] NAK for addr: 0050 w(1)
>Jul 29 06:33:18 IVB102 kernel: [    3.061591] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpc] NAK on first message, retry
>Jul 29 06:33:18 IVB102 kernel: [    3.061826] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpc] NAK for addr: 0050 w(1)
>Jul 29 06:33:18 IVB102 kernel: [    3.061831] [drm:drm_do_probe_ddc_edid] drm: skipping non-existent adapter i915 gmbus dpc
>Jul 29 06:33:18 IVB102 kernel: [    3.062001] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpc] NAK for addr: 0040 w(1)
>Jul 29 06:33:18 IVB102 kernel: [    3.062003] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpc] NAK on first message, retry
>Jul 29 06:33:18 IVB102 kernel: [    3.062162] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpc] NAK for addr: 0040 w(1)
>Jul 29 06:33:18 IVB102 kernel: [    3.062165] [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:46:HDMI-A-2] disconnected
>Jul 29 06:33:18 IVB102 kernel: [    3.062167] [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:48:HDMI-A-3]
>Jul 29 06:33:18 IVB102 kernel: [    3.062169] [drm:intel_hdmi_detect] [CONNECTOR:48:HDMI-A-3]
>Jul 29 06:33:18 IVB102 kernel: [    3.120634] clocksource: Switched to clocksource tsc
>Jul 29 06:33:18 IVB102 kernel: [    3.188412] [drm:intel_hdmi_detect] HDMI live status down
>Jul 29 06:33:18 IVB102 kernel: [    3.188624] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpd] NAK for addr: 0050 w(1)
>Jul 29 06:33:18 IVB102 kernel: [    3.188627] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpd] NAK on first message, retry
>Jul 29 06:33:18 IVB102 kernel: [    3.188832] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpd] NAK for addr: 0050 w(1)
>Jul 29 06:33:18 IVB102 kernel: [    3.188837] [drm:drm_do_probe_ddc_edid] drm: skipping non-existent adapter i915 gmbus dpd
>Jul 29 06:33:18 IVB102 kernel: [    3.189076] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpd] NAK for addr: 0040 w(1)
>Jul 29 06:33:18 IVB102 kernel: [    3.189080] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpd] NAK on first message, retry
>Jul 29 06:33:18 IVB102 kernel: [    3.189304] [drm:do_gmbus_xfer] GMBUS [i915 gmbus dpd] NAK for addr: 0040 w(1)
>Jul 29 06:33:18 IVB102 kernel: [    3.189310] [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:48:HDMI-A-3] disconnected
>Jul 29 06:33:18 IVB102 kernel: [    3.189313] [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:50:DP-2]
>Jul 29 06:33:18 IVB102 kernel: [    3.189324] [drm:intel_dp_detect] [CONNECTOR:50:DP-2]
>Jul 29 06:33:18 IVB102 kernel: [    3.189756] [drm:intel_dp_get_dpcd] DPCD: 11 0a 84 01 01 00 01 01 02 00 00 00 00 00 00
>Jul 29 06:33:18 IVB102 kernel: [    3.190068] [drm:intel_dp_get_dpcd] Display Port TPS3 support: source no, sink no
>Jul 29 06:33:18 IVB102 kernel: [    3.190069] [drm:intel_dp_print_rates] source rates: 162000, 270000
>Jul 29 06:33:18 IVB102 kernel: [    3.190070] [drm:intel_dp_print_rates] sink rates: 162000, 270000
>Jul 29 06:33:18 IVB102 kernel: [    3.190071] [drm:intel_dp_print_rates] common rates: 162000, 270000
>Jul 29 06:33:18 IVB102 kernel: [    3.190432] [drm:drm_edid_to_eld] ELD: no CEA Extension found
>Jul 29 06:33:18 IVB102 kernel: [    3.190436] [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:50:DP-2] probed modes :
>Jul 29 06:33:18 IVB102 kernel: [    3.190446] [drm:drm_mode_debug_printmodeline] Modeline 55:"1920x1080" 60 148500 1920 2008 2052 2200 1080 1084 1089 1125 0x48 0x5
>Jul 29 06:33:18 IVB102 kernel: [    3.190448] [drm:drm_mode_debug_printmodeline] Modeline 62:"1280x1024" 75 135000 1280 1296 1440 1688 1024 1025 1028 1066 0x40 0x5
>Jul 29 06:33:18 IVB102 kernel: [    3.190449] [drm:drm_mode_debug_printmodeline] Modeline 57:"1280x1024" 60 108000 1280 1328 1440 1688 1024 1025 1028 1066 0x40 0x5
>Jul 29 06:33:18 IVB102 kernel: [    3.190450] [drm:drm_mode_debug_printmodeline] Modeline 56:"1152x864" 75 108000 1152 1216 1344 1600 864 865 868 900 0x40 0x5
>Jul 29 06:33:18 IVB102 kernel: [    3.190451] [drm:drm_mode_debug_printmodeline] Modeline 63:"1024x768" 75 78750 1024 1040 1136 1312 768 769 772 800 0x40 0x5
>Jul 29 06:33:18 IVB102 kernel: [    3.190453] [drm:drm_mode_debug_printmodeline] Modeline 64:"1024x768" 60 65000 1024 1048 1184 1344 768 771 777 806 0x40 0xa
>Jul 29 06:33:18 IVB102 kernel: [    3.190454] [drm:drm_mode_debug_printmodeline] Modeline 65:"800x600" 75 49500 800 816 896 1056 600 601 604 625 0x40 0x5
>Jul 29 06:33:18 IVB102 kernel: [    3.190455] [drm:drm_mode_debug_printmodeline] Modeline 58:"800x600" 60 40000 800 840 968 1056 600 601 605 628 0x40 0x5
>Jul 29 06:33:18 IVB102 kernel: [    3.190456] [drm:drm_mode_debug_printmodeline] Modeline 59:"640x480" 75 31500 640 656 720 840 480 481 484 500 0x40 0xa
>Jul 29 06:33:18 IVB102 kernel: [    3.190457] [drm:drm_mode_debug_printmodeline] Modeline 60:"640x480" 60 25175 640 656 752 800 480 490 492 525 0x40 0xa
>Jul 29 06:33:18 IVB102 kernel: [    3.190458] [drm:drm_mode_debug_printmodeline] Modeline 61:"720x400" 70 28320 720 738 846 900 400 412 414 449 0x40 0x6
>Jul 29 06:33:18 IVB102 kernel: [    3.190459] [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:52:DP-3]
>Jul 29 06:33:18 IVB102 kernel: [    3.190460] [drm:intel_dp_detect] [CONNECTOR:52:DP-3]
>Jul 29 06:33:18 IVB102 kernel: [    3.190464] [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:52:DP-3] disconnected
>Jul 29 06:33:18 IVB102 kernel: [    3.190466] [drm:drm_setup_crtcs] 
>Jul 29 06:33:18 IVB102 kernel: [    3.190467] [drm:drm_enable_connectors] connector 36 enabled? no
>Jul 29 06:33:18 IVB102 kernel: [    3.190467] [drm:drm_enable_connectors] connector 39 enabled? no
>Jul 29 06:33:18 IVB102 kernel: [    3.190468] [drm:drm_enable_connectors] connector 44 enabled? no
>Jul 29 06:33:18 IVB102 kernel: [    3.190469] [drm:drm_enable_connectors] connector 46 enabled? no
>Jul 29 06:33:18 IVB102 kernel: [    3.190469] [drm:drm_enable_connectors] connector 48 enabled? no
>Jul 29 06:33:18 IVB102 kernel: [    3.190470] [drm:drm_enable_connectors] connector 50 enabled? yes
>Jul 29 06:33:18 IVB102 kernel: [    3.190470] [drm:drm_enable_connectors] connector 52 enabled? no
>Jul 29 06:33:18 IVB102 kernel: [    3.190472] [drm:intel_fb_initial_config] connector VGA-1 not enabled, skipping
>Jul 29 06:33:18 IVB102 kernel: [    3.190472] [drm:intel_fb_initial_config] connector HDMI-A-1 not enabled, skipping
>Jul 29 06:33:18 IVB102 kernel: [    3.190473] [drm:intel_fb_initial_config] connector DP-1 not enabled, skipping
>Jul 29 06:33:18 IVB102 kernel: [    3.190474] [drm:intel_fb_initial_config] connector HDMI-A-2 not enabled, skipping
>Jul 29 06:33:18 IVB102 kernel: [    3.190474] [drm:intel_fb_initial_config] connector HDMI-A-3 not enabled, skipping
>Jul 29 06:33:18 IVB102 kernel: [    3.190475] [drm:intel_fb_initial_config] looking for cmdline mode on connector DP-2
>Jul 29 06:33:18 IVB102 kernel: [    3.190476] [drm:intel_fb_initial_config] looking for preferred mode on connector DP-2 0
>Jul 29 06:33:18 IVB102 kernel: [    3.190478] [drm:intel_fb_initial_config] connector DP-2 on [CRTC:26:pipe A]: 1920x1080
>Jul 29 06:33:18 IVB102 kernel: [    3.190478] [drm:intel_fb_initial_config] connector DP-3 not enabled, skipping
>Jul 29 06:33:18 IVB102 kernel: [    3.190479] [drm:drm_setup_crtcs] desired mode 1920x1080 set on crtc 26 (0,0)
>Jul 29 06:33:18 IVB102 kernel: [    3.190481] [drm:intelfb_create] no BIOS fb, allocating a new one
>Jul 29 06:33:18 IVB102 kernel: [    3.190482] [drm:i915_gem_object_create_stolen] creating stolen object: size=7e9000
>Jul 29 06:33:18 IVB102 kernel: [    3.190485] [drm:i915_pages_create_for_stolen] offset=0x1000, size=8294400
>Jul 29 06:33:18 IVB102 kernel: [    3.191252] [drm:intelfb_create] allocated 1920x1080 fb: 0x00063000, bo ffff8807f3cfc000
>Jul 29 06:33:18 IVB102 kernel: [    3.191334] fbcon: inteldrmfb (fb0) is primary device
>Jul 29 06:33:18 IVB102 kernel: [    3.191391] [drm:connected_sink_compute_bpp] [CONNECTOR:50:DP-2] checking for sink bpp constrains
>Jul 29 06:33:18 IVB102 kernel: [    3.191391] [drm:connected_sink_compute_bpp] clamping display bpp (was 36) to EDID reported max of 24
>Jul 29 06:33:18 IVB102 kernel: [    3.191393] [drm:intel_dp_compute_config] DP link computation with max lane count 4 max bw 270000 pixel clock 148500KHz
>Jul 29 06:33:18 IVB102 kernel: [    3.191394] [drm:intel_dp_compute_config] DP link bw 06 rate select 00 lane count 4 clock 162000 bpp 24
>Jul 29 06:33:18 IVB102 kernel: [    3.191394] [drm:intel_dp_compute_config] DP link bw required 356400 available 518400
>Jul 29 06:33:18 IVB102 kernel: [    3.191396] [drm:ironlake_check_fdi_lanes] checking fdi config on pipe A, lanes 2
>Jul 29 06:33:18 IVB102 kernel: [    3.191396] [drm:intel_modeset_pipe_config] hw max bpp: 36, pipe bpp: 24, dithering: 0
>Jul 29 06:33:18 IVB102 kernel: [    3.191397] [drm:intel_dump_pipe_config] [CRTC:26:pipe A][modeset] config ffff8807f2d15000 for pipe A
>Jul 29 06:33:18 IVB102 kernel: [    3.191398] [drm:intel_dump_pipe_config] cpu_transcoder: A
>Jul 29 06:33:18 IVB102 kernel: [    3.191398] [drm:intel_dump_pipe_config] pipe bpp: 24, dithering: 0
>Jul 29 06:33:18 IVB102 kernel: [    3.191399] [drm:intel_dump_pipe_config] fdi/pch: 1, lanes: 2, gmch_m: 6920601, gmch_n: 8388608, link_m: 288358, link_n: 524288, tu: 64
>Jul 29 06:33:18 IVB102 kernel: [    3.191399] [drm:intel_dump_pipe_config] dp: 1, lanes: 4, gmch_m: 5767168, gmch_n: 8388608, link_m: 240298, link_n: 262144, tu: 64
>Jul 29 06:33:18 IVB102 kernel: [    3.191400] [drm:intel_dump_pipe_config] dp: 1, lanes: 4, gmch_m2: 0, gmch_n2: 0, link_m2: 0, link_n2: 0, tu2: 0
>Jul 29 06:33:18 IVB102 kernel: [    3.191400] [drm:intel_dump_pipe_config] audio: 0, infoframes: 0
>Jul 29 06:33:18 IVB102 kernel: [    3.191401] [drm:intel_dump_pipe_config] requested mode:
>Jul 29 06:33:18 IVB102 kernel: [    3.191402] [drm:drm_mode_debug_printmodeline] Modeline 0:"1920x1080" 60 148500 1920 2008 2052 2200 1080 1084 1089 1125 0x48 0x5
>Jul 29 06:33:18 IVB102 kernel: [    3.191402] [drm:intel_dump_pipe_config] adjusted mode:
>Jul 29 06:33:18 IVB102 kernel: [    3.191403] [drm:drm_mode_debug_printmodeline] Modeline 0:"1920x1080" 60 148500 1920 2008 2052 2200 1080 1084 1089 1125 0x48 0x5
>Jul 29 06:33:18 IVB102 kernel: [    3.191404] [drm:intel_dump_crtc_timings] crtc timings: 148500 1920 2008 2052 2200 1080 1084 1089 1125, type: 0x48 flags: 0x5
>Jul 29 06:33:18 IVB102 kernel: [    3.191404] [drm:intel_dump_pipe_config] port clock: 162000
>Jul 29 06:33:18 IVB102 kernel: [    3.191405] [drm:intel_dump_pipe_config] pipe src size: 1920x1080
>Jul 29 06:33:18 IVB102 kernel: [    3.191405] [drm:intel_dump_pipe_config] num_scalers: 0, scaler_users: 0x0, scaler_id: 0
>Jul 29 06:33:18 IVB102 kernel: [    3.191405] [drm:intel_dump_pipe_config] gmch pfit: control: 0x00000000, ratios: 0x00000000, lvds border: 0x00000000
>Jul 29 06:33:18 IVB102 kernel: [    3.191406] [drm:intel_dump_pipe_config] pch pfit: pos: 0x00000000, size: 0x00000000, disabled
>Jul 29 06:33:18 IVB102 kernel: [    3.191406] [drm:intel_dump_pipe_config] ips: 0
>Jul 29 06:33:18 IVB102 kernel: [    3.191407] [drm:intel_dump_pipe_config] double wide: 0
>Jul 29 06:33:18 IVB102 kernel: [    3.191407] [drm:intel_dump_pipe_config] dpll_hw_state: dpll: 0xc4010001, dpll_md: 0x0, fp0: 0x20e08, fp1: 0x30d07
>Jul 29 06:33:18 IVB102 kernel: [    3.191407] [drm:intel_dump_pipe_config] planes on this crtc
>Jul 29 06:33:18 IVB102 kernel: [    3.191408] [drm:intel_dump_pipe_config] [PLANE:23:primary A] disabled, scaler_id = 0
>Jul 29 06:33:18 IVB102 kernel: [    3.191408] [drm:intel_dump_pipe_config] [PLANE:25:cursor A] disabled, scaler_id = 0
>Jul 29 06:33:18 IVB102 kernel: [    3.191409] [drm:intel_dump_pipe_config] [PLANE:27:sprite A] disabled, scaler_id = 0
>Jul 29 06:33:18 IVB102 kernel: [    3.191414] [drm:intel_find_shared_dpll] [CRTC:26:pipe A] allocated PCH DPLL A
>Jul 29 06:33:18 IVB102 kernel: [    3.191414] [drm:intel_reference_shared_dpll] using PCH DPLL A for pipe A
>Jul 29 06:33:18 IVB102 kernel: [    3.191603] [drm:intel_disable_pipe] disabling pipe A
>Jul 29 06:33:18 IVB102 kernel: [    3.203919] [drm:intel_dp_link_down] 
>Jul 29 06:33:18 IVB102 kernel: [    3.220814] [drm:intel_disable_shared_dpll] disable PCH DPLL A (active 1, on? 1) for crtc 26
>Jul 29 06:33:18 IVB102 kernel: [    3.220819] [drm:intel_disable_shared_dpll] disabling PCH DPLL A
>Jul 29 06:33:18 IVB102 kernel: [    3.221029] [drm:verify_encoder_state] [ENCODER:37:CRT]
>Jul 29 06:33:18 IVB102 kernel: [    3.221031] [drm:verify_encoder_state] [ENCODER:38:HDMI B]
>Jul 29 06:33:18 IVB102 kernel: [    3.221032] [drm:verify_encoder_state] [ENCODER:43:DP B]
>Jul 29 06:33:18 IVB102 kernel: [    3.221034] [drm:verify_encoder_state] [ENCODER:45:HDMI C]
>Jul 29 06:33:18 IVB102 kernel: [    3.221035] [drm:verify_encoder_state] [ENCODER:47:HDMI D]
>Jul 29 06:33:18 IVB102 kernel: [    3.221037] [drm:verify_encoder_state] [ENCODER:49:DP C]
>Jul 29 06:33:18 IVB102 kernel: [    3.221038] [drm:verify_encoder_state] [ENCODER:51:DP D]
>Jul 29 06:33:18 IVB102 kernel: [    3.221039] [drm:intel_connector_verify_state] [CONNECTOR:36:VGA-1]
>Jul 29 06:33:18 IVB102 kernel: [    3.221041] [drm:intel_connector_verify_state] [CONNECTOR:39:HDMI-A-1]
>Jul 29 06:33:18 IVB102 kernel: [    3.221042] [drm:intel_connector_verify_state] [CONNECTOR:44:DP-1]
>Jul 29 06:33:18 IVB102 kernel: [    3.221043] [drm:intel_connector_verify_state] [CONNECTOR:46:HDMI-A-2]
>Jul 29 06:33:18 IVB102 kernel: [    3.221045] [drm:intel_connector_verify_state] [CONNECTOR:48:HDMI-A-3]
>Jul 29 06:33:18 IVB102 kernel: [    3.221046] [drm:intel_connector_verify_state] [CONNECTOR:52:DP-3]
>Jul 29 06:33:18 IVB102 kernel: [    3.221048] [drm:verify_single_dpll_state] PCH DPLL A
>Jul 29 06:33:18 IVB102 kernel: [    3.221052] [drm:verify_single_dpll_state] PCH DPLL B
>Jul 29 06:33:18 IVB102 kernel: [    3.221060] [drm:intel_prepare_shared_dpll] setting up PCH DPLL A
>Jul 29 06:33:18 IVB102 kernel: [    3.221599] [drm:intel_enable_pipe] enabling pipe A
>Jul 29 06:33:18 IVB102 kernel: [    3.221761] [drm:ivb_manual_fdi_link_train] FDI_RX_IIR before link train 0x700
>Jul 29 06:33:18 IVB102 kernel: [    3.221768] [drm:ivb_manual_fdi_link_train] FDI_RX_IIR 0x700
>Jul 29 06:33:18 IVB102 kernel: [    3.221769] [drm:ivb_manual_fdi_link_train] FDI train 1 done, level 0.
>Jul 29 06:33:18 IVB102 kernel: [    3.221776] [drm:ivb_manual_fdi_link_train] FDI_RX_IIR 0x600
>Jul 29 06:33:18 IVB102 kernel: [    3.221777] [drm:ivb_manual_fdi_link_train] FDI train 2 done, level 0.
>Jul 29 06:33:18 IVB102 kernel: [    3.221777] [drm:ivb_manual_fdi_link_train] FDI train done.
>Jul 29 06:33:18 IVB102 kernel: [    3.221780] [drm:intel_enable_shared_dpll] enable PCH DPLL A (active 1, on? 0) for crtc 26
>Jul 29 06:33:18 IVB102 kernel: [    3.221781] [drm:intel_enable_shared_dpll] enabling PCH DPLL A
>Jul 29 06:33:18 IVB102 kernel: [    3.224725] [drm:intel_dp_set_signal_levels] Using signal levels 00000000
>Jul 29 06:33:18 IVB102 kernel: [    3.224727] [drm:intel_dp_set_signal_levels] Using vswing level 0
>Jul 29 06:33:18 IVB102 kernel: [    3.224727] [drm:intel_dp_set_signal_levels] Using pre-emphasis level 0
>Jul 29 06:33:18 IVB102 kernel: [    3.226227] [drm:intel_dp_link_training_clock_recovery] clock recovery OK
>Jul 29 06:33:18 IVB102 kernel: [    3.227596] [drm:intel_dp_set_signal_levels] Using signal levels 00400000
>Jul 29 06:33:18 IVB102 kernel: [    3.227596] [drm:intel_dp_set_signal_levels] Using vswing level 0
>Jul 29 06:33:18 IVB102 kernel: [    3.227597] [drm:intel_dp_set_signal_levels] Using pre-emphasis level 1
>Jul 29 06:33:18 IVB102 kernel: [    3.228527] [drm:intel_dp_link_training_channel_equalization] Channel EQ done. DP Training successful
>Jul 29 06:33:18 IVB102 kernel: [    3.261987] [drm:intel_connector_verify_state] [CONNECTOR:50:DP-2]
>Jul 29 06:33:18 IVB102 kernel: [    3.261995] [drm:verify_crtc_state] [CRTC:26:pipe A]
>Jul 29 06:33:18 IVB102 kernel: [    3.262024] [drm:verify_single_dpll_state] PCH DPLL A
>Jul 29 06:33:18 IVB102 kernel: [    3.262034] Console: switching to colour frame buffer device 240x67
>Jul 29 06:33:18 IVB102 kernel: [    3.281435] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
>Jul 29 06:33:18 IVB102 kernel: [    3.737319] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
>Jul 29 06:33:18 IVB102 kernel: [    3.784677] [drm:intel_print_rc6_info] Enabling RC6 states: RC6 on RC6p on RC6pp off
>Jul 29 06:33:18 IVB102 kernel: [    4.422463] calling  init_autofs4_fs+0x0/0x27 [autofs4] @ 1
>Jul 29 06:33:18 IVB102 kernel: [    4.422500] initcall init_autofs4_fs+0x0/0x27 [autofs4] returned 0 after 33 usecs
>Jul 29 06:33:18 IVB102 kernel: [    5.035458] random: nonblocking pool is initialized
>Jul 29 06:33:18 IVB102 kernel: [    6.645681] calling  parport_default_proc_register+0x0/0x1000 [parport] @ 1108
>Jul 29 06:33:18 IVB102 kernel: [    6.645694] initcall parport_default_proc_register+0x0/0x1000 [parport] returned 0 after 9 usecs
>Jul 29 06:33:18 IVB102 kernel: [    6.740188] calling  lp_init_module+0x0/0x1000 [lp] @ 1108
>Jul 29 06:33:18 IVB102 kernel: [    6.807884] lp: driver loaded but no devices found
>Jul 29 06:33:18 IVB102 kernel: [    6.808850] initcall lp_init_module+0x0/0x1000 [lp] returned 0 after 67052 usecs
>Jul 29 06:33:18 IVB102 kernel: [    6.836321] calling  ppdev_init+0x0/0x1000 [ppdev] @ 1108
>Jul 29 06:33:18 IVB102 kernel: [    6.836841] ppdev: user-space parallel port driver
>Jul 29 06:33:18 IVB102 kernel: [    6.837798] initcall ppdev_init+0x0/0x1000 [ppdev] returned 0 after 1439 usecs
>Jul 29 06:33:18 IVB102 kernel: [    6.907249] calling  parport_pc_init+0x0/0xf44 [parport_pc] @ 1108
>Jul 29 06:33:18 IVB102 kernel: [    6.907277] parport_pc 00:05: reported by Plug and Play ACPI
>Jul 29 06:33:18 IVB102 kernel: [    6.908305] parport0: PC-style at 0x378, irq 5 [PCSPP]
>Jul 29 06:33:18 IVB102 kernel: [    7.004286] lp0: using parport0 (interrupt-driven).
>Jul 29 06:33:18 IVB102 kernel: [    7.005391] initcall parport_pc_init+0x0/0xf44 [parport_pc] returned 0 after 95842 usecs
>Jul 29 06:33:18 IVB102 kernel: [    7.410496] EXT4-fs (sda3): re-mounted. Opts: errors=remount-ro
>Jul 29 06:33:18 IVB102 kernel: [    7.625197] calling  mac_hid_init+0x0/0x1000 [mac_hid] @ 1198
>Jul 29 06:33:18 IVB102 kernel: [    7.625203] initcall mac_hid_init+0x0/0x1000 [mac_hid] returned 0 after 3 usecs
>Jul 29 06:33:18 IVB102 kernel: [    7.667378] calling  rc_core_init+0x0/0x1000 [rc_core] @ 1186
>Jul 29 06:33:18 IVB102 kernel: [    7.667387] initcall rc_core_init+0x0/0x1000 [rc_core] returned 0 after 4 usecs
>Jul 29 06:33:18 IVB102 kernel: [    7.688237] calling  nvt_driver_init+0x0/0x1000 [nuvoton_cir] @ 1186
>Jul 29 06:33:18 IVB102 kernel: [    7.688248] initcall nvt_driver_init+0x0/0x1000 [nuvoton_cir] returned 0 after 8 usecs
>Jul 29 06:33:18 IVB102 kernel: [    7.772270] calling  edac_init+0x0/0xf77 [edac_core] @ 1237
>Jul 29 06:33:18 IVB102 kernel: [    7.772272] EDAC MC: Ver: 3.0.0
>Jul 29 06:33:18 IVB102 kernel: [    7.772398] initcall edac_init+0x0/0xf77 [edac_core] returned 0 after 118 usecs
>Jul 29 06:33:18 IVB102 kernel: [    7.788489] calling  lpc_ich_driver_init+0x0/0x1000 [lpc_ich] @ 1241
>Jul 29 06:33:18 IVB102 kernel: [    7.788568] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20160422/utaddress-255)
>Jul 29 06:33:18 IVB102 kernel: [    7.788573] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
>Jul 29 06:33:18 IVB102 kernel: [    7.788579] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20160422/utaddress-255)
>Jul 29 06:33:18 IVB102 kernel: [    7.788583] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
>Jul 29 06:33:18 IVB102 kernel: [    7.788584] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20160422/utaddress-255)
>Jul 29 06:33:18 IVB102 kernel: [    7.788587] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
>Jul 29 06:33:18 IVB102 kernel: [    7.788588] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20160422/utaddress-255)
>Jul 29 06:33:18 IVB102 kernel: [    7.788592] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x000000000000050F-0x000000000000050F (\_SB.PCI0.RLED.DBG0) (20160422/utaddress-255)
>Jul 29 06:33:18 IVB102 kernel: [    7.788595] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
>Jul 29 06:33:18 IVB102 kernel: [    7.788596] lpc_ich: Resource conflict(s) found affecting gpio_ich
>Jul 29 06:33:18 IVB102 kernel: [    7.788620] initcall lpc_ich_driver_init+0x0/0x1000 [lpc_ich] returned 0 after 122 usecs
>Jul 29 06:33:18 IVB102 kernel: [    7.796180] calling  cryptd_init+0x0/0x1000 [cryptd] @ 1236
>Jul 29 06:33:18 IVB102 kernel: [    7.796188] initcall cryptd_init+0x0/0x1000 [cryptd] returned 0 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    7.869293] calling  init_soundcore+0x0/0x1000 [soundcore] @ 1196
>Jul 29 06:33:18 IVB102 kernel: [    7.869302] initcall init_soundcore+0x0/0x1000 [soundcore] returned 0 after 4 usecs
>Jul 29 06:33:18 IVB102 kernel: [    7.905526] calling  alsa_sound_init+0x0/0x84 [snd] @ 2269
>Jul 29 06:33:18 IVB102 kernel: [    7.905537] initcall alsa_sound_init+0x0/0x84 [snd] returned 0 after 5 usecs
>Jul 29 06:33:18 IVB102 kernel: [    7.941242] calling  ie31200_init+0x0/0x1000 [ie31200_edac] @ 1237
>Jul 29 06:33:18 IVB102 kernel: [    7.941259] initcall ie31200_init+0x0/0x1000 [ie31200_edac] returned 0 after 13 usecs
>Jul 29 06:33:18 IVB102 kernel: [    7.962641] calling  crypto_module_init+0x0/0x1000 [lrw] @ 1206
>Jul 29 06:33:18 IVB102 kernel: [    7.962644] initcall crypto_module_init+0x0/0x1000 [lrw] returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    7.966600] calling  alsa_timer_init+0x0/0x1000 [snd_timer] @ 2379
>Jul 29 06:33:18 IVB102 kernel: [    7.966631] initcall alsa_timer_init+0x0/0x1000 [snd_timer] returned 0 after 27 usecs
>Jul 29 06:33:18 IVB102 kernel: [    7.971667] calling  aes_init+0x0/0x1000 [aes_x86_64] @ 1187
>Jul 29 06:33:18 IVB102 kernel: [    7.971691] initcall aes_init+0x0/0x1000 [aes_x86_64] returned 0 after 20 usecs
>Jul 29 06:33:18 IVB102 kernel: [    7.991794] calling  aesni_init+0x0/0x13e [aesni_intel] @ 1187
>Jul 29 06:33:18 IVB102 kernel: [    7.991796] AVX version of gcm_enc/dec engaged.
>Jul 29 06:33:18 IVB102 kernel: [    7.991796] AES CTR mode by8 optimization enabled
>Jul 29 06:33:18 IVB102 kernel: [    7.992208] initcall aesni_init+0x0/0x13e [aesni_intel] returned 0 after 397 usecs
>Jul 29 06:33:18 IVB102 kernel: [    8.075354] calling  alsa_seq_device_init+0x0/0x1000 [snd_seq_device] @ 2379
>Jul 29 06:33:18 IVB102 kernel: [    8.075371] initcall alsa_seq_device_init+0x0/0x1000 [snd_seq_device] returned 0 after 6 usecs
>Jul 29 06:33:18 IVB102 kernel: [    8.112086] calling  ghash_pclmulqdqni_mod_init+0x0/0x1000 [ghash_clmulni_intel] @ 1210
>Jul 29 06:33:18 IVB102 kernel: [    8.112123] initcall ghash_pclmulqdqni_mod_init+0x0/0x1000 [ghash_clmulni_intel] returned 0 after 33 usecs
>Jul 29 06:33:18 IVB102 kernel: [    8.119610] calling  alsa_seq_init+0x0/0x48 [snd_seq] @ 2452
>Jul 29 06:33:18 IVB102 kernel: [    8.119645] initcall alsa_seq_init+0x0/0x48 [snd_seq] returned 0 after 30 usecs
>Jul 29 06:33:18 IVB102 kernel: [    8.135797] calling  mei_init+0x0/0xae [mei] @ 1212
>Jul 29 06:33:18 IVB102 kernel: [    8.135809] initcall mei_init+0x0/0xae [mei] returned 0 after 8 usecs
>Jul 29 06:33:18 IVB102 kernel: [    8.153613] calling  alsa_rawmidi_init+0x0/0x1000 [snd_rawmidi] @ 2481
>Jul 29 06:33:18 IVB102 kernel: [    8.153616] initcall alsa_rawmidi_init+0x0/0x1000 [snd_rawmidi] returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    8.155621] calling  alsa_seq_midi_event_init+0x0/0x1000 [snd_seq_midi_event] @ 2485
>Jul 29 06:33:18 IVB102 kernel: [    8.155625] initcall alsa_seq_midi_event_init+0x0/0x1000 [snd_seq_midi_event] returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [    8.156569] calling  seq_midisynth_driver_init+0x0/0x1000 [snd_seq_midi] @ 2485
>Jul 29 06:33:18 IVB102 kernel: [    8.156583] initcall seq_midisynth_driver_init+0x0/0x1000 [snd_seq_midi] returned 0 after 10 usecs
>Jul 29 06:33:18 IVB102 kernel: [    8.165958] calling  shpcd_init+0x0/0x1000 [shpchp] @ 1189
>Jul 29 06:33:18 IVB102 kernel: [    8.165972] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
>Jul 29 06:33:18 IVB102 kernel: [    8.165974] initcall shpcd_init+0x0/0x1000 [shpchp] returned 0 after 13 usecs
>Jul 29 06:33:18 IVB102 kernel: [    8.176570] calling  mei_me_driver_init+0x0/0x1000 [mei_me] @ 1212
>Jul 29 06:33:18 IVB102 kernel: [    8.180149] initcall mei_me_driver_init+0x0/0x1000 [mei_me] returned 0 after 3491 usecs
>Jul 29 06:33:18 IVB102 kernel: [    8.196421] calling  alsa_pcm_init+0x0/0x6c [snd_pcm] @ 2493
>Jul 29 06:33:18 IVB102 kernel: [    8.196428] initcall alsa_pcm_init+0x0/0x6c [snd_pcm] returned 0 after 2 usecs
>Jul 29 06:33:18 IVB102 kernel: [    8.198122] calling  alsa_hwdep_init+0x0/0x1000 [snd_hwdep] @ 1196
>Jul 29 06:33:18 IVB102 kernel: [    8.198126] initcall alsa_hwdep_init+0x0/0x1000 [snd_hwdep] returned 0 after 1 usecs
>Jul 29 06:33:18 IVB102 kernel: [    8.202030] calling  crc32_pclmul_mod_init+0x0/0x1000 [crc32_pclmul] @ 1199
>Jul 29 06:33:18 IVB102 kernel: [    8.202058] initcall crc32_pclmul_mod_init+0x0/0x1000 [crc32_pclmul] returned 0 after 23 usecs
>Jul 29 06:33:18 IVB102 kernel: [    8.226441] calling  hda_bus_init+0x0/0x12 [snd_hda_core] @ 1196
>Jul 29 06:33:18 IVB102 kernel: [    8.226451] initcall hda_bus_init+0x0/0x12 [snd_hda_core] returned 0 after 5 usecs
>Jul 29 06:33:18 IVB102 kernel: [    8.272052] calling  crct10dif_intel_mod_init+0x0/0x1000 [crct10dif_pclmul] @ 1238
>Jul 29 06:33:18 IVB102 kernel: [    8.272495] initcall crct10dif_intel_mod_init+0x0/0x1000 [crct10dif_pclmul] returned 0 after 428 usecs
>Jul 29 06:33:18 IVB102 kernel: [    8.369767] calling  azx_driver_init+0x0/0xfce [snd_hda_intel] @ 1196
>Jul 29 06:33:18 IVB102 kernel: [    8.369964] initcall azx_driver_init+0x0/0xfce [snd_hda_intel] returned 0 after 188 usecs
>Jul 29 06:33:18 IVB102 kernel: [    8.382452] calling  generic_driver_init+0x0/0x1000 [snd_hda_codec_generic] @ 2525
>Jul 29 06:33:18 IVB102 kernel: [    8.382467] initcall generic_driver_init+0x0/0x1000 [snd_hda_codec_generic] returned 0 after 9 usecs
>Jul 29 06:33:18 IVB102 kernel: [    8.491767] calling  realtek_driver_init+0x0/0x1000 [snd_hda_codec_realtek] @ 1212
>Jul 29 06:33:18 IVB102 kernel: [    8.492471] snd_hda_codec_realtek hdaudioC0D2: autoconfig for ALC892: line_outs=3 (0x14/0x15/0x16/0x0/0x0) type:line
>Jul 29 06:33:18 IVB102 kernel: [    8.492473] snd_hda_codec_realtek hdaudioC0D2:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
>Jul 29 06:33:18 IVB102 kernel: [    8.492474] snd_hda_codec_realtek hdaudioC0D2:    hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
>Jul 29 06:33:18 IVB102 kernel: [    8.492475] snd_hda_codec_realtek hdaudioC0D2:    mono: mono_out=0x0
>Jul 29 06:33:18 IVB102 kernel: [    8.492476] snd_hda_codec_realtek hdaudioC0D2:    dig-out=0x11/0x1e
>Jul 29 06:33:18 IVB102 kernel: [    8.492476] snd_hda_codec_realtek hdaudioC0D2:    inputs:
>Jul 29 06:33:18 IVB102 kernel: [    8.492478] snd_hda_codec_realtek hdaudioC0D2:      Front Mic=0x19
>Jul 29 06:33:18 IVB102 kernel: [    8.492479] snd_hda_codec_realtek hdaudioC0D2:      Rear Mic=0x18
>Jul 29 06:33:18 IVB102 kernel: [    8.492480] snd_hda_codec_realtek hdaudioC0D2:      Line=0x1a
>Jul 29 06:33:18 IVB102 kernel: [    8.503774] initcall realtek_driver_init+0x0/0x1000 [snd_hda_codec_realtek] returned 0 after 11719 usecs
>Jul 29 06:33:18 IVB102 kernel: [    8.506152] calling  hdmi_driver_init+0x0/0x1000 [snd_hda_codec_hdmi] @ 1212
>Jul 29 06:33:18 IVB102 kernel: [    8.506200] snd_hda_intel 0000:00:1b.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
>Jul 29 06:33:18 IVB102 kernel: [    8.542451] calling  cfg80211_init+0x0/0xdb [cfg80211] @ 1200
>Jul 29 06:33:18 IVB102 kernel: [    8.546012] initcall cfg80211_init+0x0/0xdb [cfg80211] returned 0 after 3453 usecs
>Jul 29 06:33:18 IVB102 kernel: [    8.577722] calling  vmx_init+0x0/0x370 [kvm_intel] @ 1264
>Jul 29 06:33:18 IVB102 kernel: [    8.578211] initcall vmx_init+0x0/0x370 [kvm_intel] returned 0 after 470 usecs
>Jul 29 06:33:18 IVB102 kernel: [    8.633965] calling  coretemp_init+0x0/0x1000 [coretemp] @ 1236
>Jul 29 06:33:18 IVB102 kernel: [    8.634051] initcall coretemp_init+0x0/0x1000 [coretemp] returned 0 after 80 usecs
>Jul 29 06:33:18 IVB102 kernel: [    8.659252] calling  powerclamp_init+0x0/0x1000 [intel_powerclamp] @ 1264
>Jul 29 06:33:18 IVB102 kernel: [    8.659290] initcall powerclamp_init+0x0/0x1000 [intel_powerclamp] returned 0 after 32 usecs
>Jul 29 06:33:18 IVB102 kernel: [    8.666988] calling  pkg_temp_thermal_init+0x0/0x1000 [x86_pkg_temp_thermal] @ 1264
>Jul 29 06:33:18 IVB102 kernel: [    8.667033] initcall pkg_temp_thermal_init+0x0/0x1000 [x86_pkg_temp_thermal] returned 0 after 39 usecs
>Jul 29 06:33:18 IVB102 kernel: [    8.756123] calling  iwl_drv_init+0x0/0x8e [iwlwifi] @ 1200
>Jul 29 06:33:18 IVB102 kernel: [    8.756125] Intel(R) Wireless WiFi driver for Linux
>Jul 29 06:33:18 IVB102 kernel: [    8.756125] Copyright(c) 2003- 2015 Intel Corporation
>Jul 29 06:33:18 IVB102 kernel: [    8.756334] iwlwifi 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control
>Jul 29 06:33:18 IVB102 kernel: [    8.756748] initcall iwl_drv_init+0x0/0x8e [iwlwifi] returned 0 after 599 usecs
>Jul 29 06:33:18 IVB102 kernel: [    8.784848] Adding 1952764k swap on /dev/sda2.  Priority:-1 extents:1 across:1952764k FS
>Jul 29 06:33:18 IVB102 kernel: [    8.877430] initcall hdmi_driver_init+0x0/0x1000 [snd_hda_codec_hdmi] returned 0 after 362586 usecs
>Jul 29 06:33:18 IVB102 kernel: [    8.878072] input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input3
>Jul 29 06:33:18 IVB102 kernel: [    8.878131] input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input4
>Jul 29 06:33:18 IVB102 kernel: [    8.878182] input: HDA Intel PCH Line Out Front as /devices/pci0000:00/0000:00:1b.0/sound/card0/input5
>Jul 29 06:33:18 IVB102 kernel: [    8.878234] input: HDA Intel PCH Line Out Surround as /devices/pci0000:00/0000:00:1b.0/sound/card0/input6
>Jul 29 06:33:18 IVB102 kernel: [    8.878283] input: HDA Intel PCH Line Out CLFE as /devices/pci0000:00/0000:00:1b.0/sound/card0/input7
>Jul 29 06:33:18 IVB102 kernel: [    8.878334] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input8
>Jul 29 06:33:18 IVB102 kernel: [    8.878384] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
>Jul 29 06:33:18 IVB102 kernel: [    8.884237] calling  rapl_init+0x0/0x1000 [intel_rapl] @ 1192
>Jul 29 06:33:18 IVB102 kernel: [    8.884242] intel_rapl: Found RAPL domain package
>Jul 29 06:33:18 IVB102 kernel: [    8.884244] intel_rapl: Found RAPL domain core
>Jul 29 06:33:18 IVB102 kernel: [    8.884246] intel_rapl: Found RAPL domain uncore
>Jul 29 06:33:18 IVB102 kernel: [    8.884393] initcall rapl_init+0x0/0x1000 [intel_rapl] returned 0 after 147 usecs
>Jul 29 06:33:18 IVB102 kernel: [    9.230876] iwlwifi 0000:02:00.0: loaded firmware version 18.168.6.1 op_mode iwldvm
>Jul 29 06:33:18 IVB102 kernel: [    9.481227] calling  ieee80211_init+0x0/0x3f [mac80211] @ 2600
>Jul 29 06:33:18 IVB102 kernel: [    9.481242] initcall ieee80211_init+0x0/0x3f [mac80211] returned 0 after 3 usecs
>Jul 29 06:33:18 IVB102 kernel: [    9.610785] calling  iwl_init+0x0/0x1000 [iwldvm] @ 2600
>Jul 29 06:33:18 IVB102 kernel: [    9.610803] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEBUG disabled
>Jul 29 06:33:18 IVB102 kernel: [    9.610804] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEBUGFS enabled
>Jul 29 06:33:18 IVB102 kernel: [    9.610805] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEVICE_TRACING enabled
>Jul 29 06:33:18 IVB102 kernel: [    9.610806] iwlwifi 0000:02:00.0: Detected Intel(R) Centrino(R) Wireless-N 1030 BGN, REV=0xB0
>Jul 29 06:33:18 IVB102 kernel: [    9.612216] iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
>Jul 29 06:33:18 IVB102 kernel: [    9.670045] calling  arc4_init+0x0/0x1000 [arc4] @ 2604
>Jul 29 06:33:18 IVB102 kernel: [    9.670085] initcall arc4_init+0x0/0x1000 [arc4] returned 0 after 36 usecs
>Jul 29 06:33:18 IVB102 kernel: [    9.670702] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
>Jul 29 06:33:18 IVB102 kernel: [    9.670928] initcall iwl_init+0x0/0x1000 [iwldvm] returned 0 after 58727 usecs
>Jul 29 06:33:18 IVB102 kernel: [    9.706818] iwlwifi 0000:02:00.0 wlp2s0: renamed from wlan0
>Jul 29 06:33:18 IVB102 kernel: [    9.920205] calling  init_nls_iso8859_1+0x0/0x1000 [nls_iso8859_1] @ 2630
>Jul 29 06:33:18 IVB102 kernel: [    9.920208] initcall init_nls_iso8859_1+0x0/0x1000 [nls_iso8859_1] returned 0 after 0 usecs
>Jul 29 06:33:18 IVB102 kernel: [   11.811729] audit: type=1400 audit(1469766796.033:2): apparmor="STATUS" operation="profile_load" name="/usr/sbin/ippusbxd" pid=2765 comm="apparmor_parser"
>Jul 29 06:33:18 IVB102 kernel: [   11.849484] audit: type=1400 audit(1469766796.073:3): apparmor="STATUS" operation="profile_load" name="/sbin/dhclient" pid=2758 comm="apparmor_parser"
>Jul 29 06:33:18 IVB102 kernel: [   11.849497] audit: type=1400 audit(1469766796.073:4): apparmor="STATUS" operation="profile_load" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2758 comm="apparmor_parser"
>Jul 29 06:33:18 IVB102 kernel: [   11.849499] audit: type=1400 audit(1469766796.073:5): apparmor="STATUS" operation="profile_load" name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=2758 comm="apparmor_parser"
>Jul 29 06:33:18 IVB102 kernel: [   11.849501] audit: type=1400 audit(1469766796.073:6): apparmor="STATUS" operation="profile_load" name="/usr/lib/connman/scripts/dhclient-script" pid=2758 comm="apparmor_parser"
>Jul 29 06:33:18 IVB102 kernel: [   11.851861] audit: type=1400 audit(1469766796.073:7): apparmor="STATUS" operation="profile_load" name="/usr/sbin/tcpdump" pid=2767 comm="apparmor_parser"
>Jul 29 06:33:18 IVB102 kernel: [   11.852496] audit: type=1400 audit(1469766796.077:8): apparmor="STATUS" operation="profile_load" name="/usr/sbin/cups-browsed" pid=2763 comm="apparmor_parser"
>Jul 29 06:33:18 IVB102 kernel: [   11.854977] audit: type=1400 audit(1469766796.077:9): apparmor="STATUS" operation="profile_load" name="/usr/lib/lightdm/lightdm-guest-session" pid=2757 comm="apparmor_parser"
>Jul 29 06:33:18 IVB102 kernel: [   11.854980] audit: type=1400 audit(1469766796.077:10): apparmor="STATUS" operation="profile_load" name="chromium" pid=2757 comm="apparmor_parser"
>Jul 29 06:33:18 IVB102 kernel: [   11.869789] audit: type=1400 audit(1469766796.093:11): apparmor="STATUS" operation="profile_load" name="/usr/bin/ubuntu-core-launcher" pid=2761 comm="apparmor_parser"
>Jul 29 06:33:18 IVB102 NetworkManager[2824]: <info>  [1469766798.6784] NetworkManager (version 1.2.0) is starting...
>Jul 29 06:33:18 IVB102 NetworkManager[2824]: <info>  [1469766798.6790] Read config: /etc/NetworkManager/NetworkManager.conf (etc: default-wifi-powersave-on.conf)
>Jul 29 06:33:18 IVB102 NetworkManager[2824]: <info>  [1469766798.7085] manager[0x21c81a0]: monitoring kernel firmware directory '/lib/firmware'.
>Jul 29 06:33:18 IVB102 NetworkManager[2824]: <info>  [1469766798.7085] monitoring ifupdown state file '/run/network/ifstate'.
>Jul 29 06:33:18 IVB102 NetworkManager[2824]: <info>  [1469766798.7333] dns-mgr[0x21da0b0]: set resolv-conf-mode: dnsmasq, plugin="dnsmasq"
>Jul 29 06:33:18 IVB102 NetworkManager[2824]: <info>  [1469766798.7333] dns-mgr[0x21da0b0]: using resolv.conf manager 'resolvconf'
>Jul 29 06:33:18 IVB102 NetworkManager[2824]: <info>  [1469766798.7574] rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.5/0000:02:00.0/ieee80211/phy0/rfkill0) (driver iwlwifi)
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.0751] init!
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.0753] management mode: unmanaged
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.0756] devices added (path: /sys/devices/pci0000:00/0000:00:19.0/net/eno1, iface: eno1)
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.0756] device added (path: /sys/devices/pci0000:00/0000:00:19.0/net/eno1, iface: eno1): no ifupdown configuration found.
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.0756] devices added (path: /sys/devices/pci0000:00/0000:00:1c.5/0000:02:00.0/net/wlp2s0, iface: wlp2s0)
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.0756] device added (path: /sys/devices/pci0000:00/0000:00:1c.5/0000:02:00.0/net/wlp2s0, iface: wlp2s0): no ifupdown configuration found.
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.0757] devices added (path: /sys/devices/virtual/net/lo, iface: lo)
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.0757] device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found.
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.0757] end _init.
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.0757] settings: loaded plugin ifupdown: (C) 2008 Canonical Ltd.  To report bugs please use the NetworkManager mailing list. (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-settings-plugin-ifupdown.so)
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.0757] settings: loaded plugin keyfile: (c) 2007 - 2015 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.0915] SettingsPlugin-Ofono: init!
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <warn>  [1469766799.0915] SettingsPlugin-Ofono: file doesn't exist: /var/lib/ofono
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.0915] SettingsPlugin-Ofono: end _init.
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.0915] settings: loaded plugin ofono: (C) 2013-2016 Canonical Ltd.  To report bugs please use the NetworkManager mailing list. (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-settings-plugin-ofono.so)
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.0915] (35578704) ... get_connections.
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.0915] (35578704) ... get_connections (managed=false): return empty list.
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.1029] SettingsPlugin-Ofono: (35578928) ... get_connections.
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.1029] SettingsPlugin-Ofono: (35578928) connections count: 0
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.1029] get unmanaged devices count: 0
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.3181] settings: hostname: using hostnamed
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.3181] settings: hostname changed from (none) to "IVB102"
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.3183] Using DHCP client 'dhclient'
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.3183] manager: WiFi enabled by radio killswitch; enabled by state file
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.3184] manager: WWAN enabled by radio killswitch; enabled by state file
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.3184] manager: Networking is enabled by state file
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.3185] Loaded device plugin: NMVxlanFactory (internal)
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.3185] Loaded device plugin: NMVlanFactory (internal)
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.3185] Loaded device plugin: NMVethFactory (internal)
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.3185] Loaded device plugin: NMTunFactory (internal)
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.3186] Loaded device plugin: NMMacvlanFactory (internal)
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.3186] Loaded device plugin: NMIPTunnelFactory (internal)
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.3186] Loaded device plugin: NMInfinibandFactory (internal)
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.3186] Loaded device plugin: NMEthernetFactory (internal)
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.3187] Loaded device plugin: NMBridgeFactory (internal)
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.3187] Loaded device plugin: NMBondFactory (internal)
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.3533] Loaded device plugin: NMWifiFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wifi.so)
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.4359] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wwan.so)
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.4683] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.4824] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-adsl.so)
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.4832] (wlp2s0): using nl80211 for WiFi device control
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.4928] device (wlp2s0): driver supports Access Point (AP) mode
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.5012] manager: (wlp2s0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/0)
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.5020] device (wlp2s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
>Jul 29 06:33:19 IVB102 kernel: [   15.272920] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
>Jul 29 06:33:19 IVB102 kernel: [   15.275140] iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
>Jul 29 06:33:19 IVB102 kernel: [   15.282049] iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
>Jul 29 06:33:19 IVB102 kernel: [   15.282148] iwlwifi 0000:02:00.0: Radio type=0x2-0x0-0x1
>Jul 29 06:33:19 IVB102 kernel: [   15.384211] iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
>Jul 29 06:33:19 IVB102 kernel: [   15.391123] iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
>Jul 29 06:33:19 IVB102 kernel: [   15.391222] iwlwifi 0000:02:00.0: Radio type=0x2-0x0-0x1
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.7081] manager: (eno1): new Ethernet device (/org/freedesktop/NetworkManager/Devices/1)
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.7088] keyfile: add connection in-memory (dea3bae1-11f9-4fbb-aee0-1418c87e2ad7,"Wired connection 1")
>Jul 29 06:33:19 IVB102 kernel: [   15.477663] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.7180] settings: (eno1): created default wired connection 'Wired connection 1'
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.7185] device (eno1): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
>Jul 29 06:33:19 IVB102 kernel: [   15.489385] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.9698] device (lo): link connected
>Jul 29 06:33:19 IVB102 NetworkManager[2824]: <info>  [1469766799.9702] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/2)
>Jul 29 06:33:19 IVB102 kernel: [   15.740032] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
>Jul 29 06:33:20 IVB102 NetworkManager[2824]: <info>  [1469766800.0090] urfkill disappeared from the bus
>Jul 29 06:33:20 IVB102 NetworkManager[2824]: <info>  [1469766800.0100] ofono is now available
>Jul 29 06:33:20 IVB102 NetworkManager[2824]: <warn>  [1469766800.0103] failed to enumerate oFono devices: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files
>Jul 29 06:33:20 IVB102 NetworkManager[2824]: <info>  [1469766800.0107] ModemManager available in the bus
>Jul 29 06:33:20 IVB102 NetworkManager[2824]: <info>  [1469766800.1063] supplicant: wpa_supplicant running
>Jul 29 06:33:20 IVB102 NetworkManager[2824]: <info>  [1469766800.1063] device (wlp2s0): supplicant interface state: init -> starting
>Jul 29 06:33:20 IVB102 NetworkManager[2824]: <info>  [1469766800.1411] device (wlp2s0): supplicant interface state: starting -> ready
>Jul 29 06:33:20 IVB102 NetworkManager[2824]: <info>  [1469766800.1411] device (wlp2s0): state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
>Jul 29 06:33:20 IVB102 kernel: [   15.911979] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
>Jul 29 06:33:20 IVB102 NetworkManager[2824]: <info>  [1469766800.5296] device (wlp2s0): supplicant interface state: ready -> inactive
>Jul 29 06:33:22 IVB102 NetworkManager[2824]: <info>  [1469766802.7475] device (eno1): link connected
>Jul 29 06:33:22 IVB102 NetworkManager[2824]: <info>  [1469766802.7478] device (eno1): state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
>Jul 29 06:33:22 IVB102 NetworkManager[2824]: <info>  [1469766802.7483] policy: auto-activating connection 'Wired connection 1'
>Jul 29 06:33:22 IVB102 NetworkManager[2824]: <info>  [1469766802.7489] device (eno1): Activation: starting connection 'Wired connection 1' (dea3bae1-11f9-4fbb-aee0-1418c87e2ad7)
>Jul 29 06:33:22 IVB102 NetworkManager[2824]: <info>  [1469766802.7490] device (eno1): state change: disconnected -> prepare (reason 'none') [30 40 0]
>Jul 29 06:33:22 IVB102 kernel: [   18.517905] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
>Jul 29 06:33:22 IVB102 kernel: [   18.517938] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
>Jul 29 06:33:22 IVB102 NetworkManager[2824]: <info>  [1469766802.7491] manager: NetworkManager state is now CONNECTING
>Jul 29 06:33:22 IVB102 NetworkManager[2824]: <info>  [1469766802.7495] device (eno1): state change: prepare -> config (reason 'none') [40 50 0]
>Jul 29 06:33:22 IVB102 NetworkManager[2824]: <info>  [1469766802.7497] device (eno1): state change: config -> ip-config (reason 'none') [50 70 0]
>Jul 29 06:33:22 IVB102 NetworkManager[2824]: <info>  [1469766802.7614] dhcp4 (eno1): activation: beginning transaction (timeout in 45 seconds)
>Jul 29 06:33:22 IVB102 NetworkManager[2824]: <info>  [1469766802.8335] dhcp4 (eno1): dhclient started with pid 3036
>Jul 29 06:33:23 IVB102 NetworkManager[2824]: <info>  [1469766803.0260]   address 10.102.161.176
>Jul 29 06:33:23 IVB102 NetworkManager[2824]: <info>  [1469766803.0260]   plen 22 (255.255.252.0)
>Jul 29 06:33:23 IVB102 NetworkManager[2824]: <info>  [1469766803.0260]   gateway 10.102.160.1
>Jul 29 06:33:23 IVB102 NetworkManager[2824]: <info>  [1469766803.0260]   server identifier 10.216.46.196
>Jul 29 06:33:23 IVB102 NetworkManager[2824]: <info>  [1469766803.0260]   lease time 43200
>Jul 29 06:33:23 IVB102 NetworkManager[2824]: <info>  [1469766803.0260]   nameserver '10.248.2.1'
>Jul 29 06:33:23 IVB102 NetworkManager[2824]: <info>  [1469766803.0261]   nameserver '10.216.46.196'
>Jul 29 06:33:23 IVB102 NetworkManager[2824]: <info>  [1469766803.0261]   nameserver '163.33.253.68'
>Jul 29 06:33:23 IVB102 NetworkManager[2824]: <info>  [1469766803.0261]   domain name 'tl.intel.com'
>Jul 29 06:33:23 IVB102 NetworkManager[2824]: <info>  [1469766803.0261]   wins '143.185.63.31'
>Jul 29 06:33:23 IVB102 NetworkManager[2824]: <info>  [1469766803.0261]   wins '163.33.7.86'
>Jul 29 06:33:23 IVB102 NetworkManager[2824]: <info>  [1469766803.0261] dhcp4 (eno1): state changed unknown -> bound
>Jul 29 06:33:23 IVB102 NetworkManager[2824]: <info>  [1469766803.0268] device (eno1): state change: ip-config -> ip-check (reason 'none') [70 80 0]
>Jul 29 06:33:23 IVB102 NetworkManager[2824]: <info>  [1469766803.0272] device (eno1): state change: ip-check -> secondaries (reason 'none') [80 90 0]
>Jul 29 06:33:23 IVB102 NetworkManager[2824]: <info>  [1469766803.0274] device (eno1): state change: secondaries -> activated (reason 'none') [90 100 0]
>Jul 29 06:33:23 IVB102 NetworkManager[2824]: <info>  [1469766803.0275] manager: NetworkManager state is now CONNECTED_LOCAL
>Jul 29 06:33:23 IVB102 NetworkManager[2824]: <info>  [1469766803.1002] manager: NetworkManager state is now CONNECTED_GLOBAL
>Jul 29 06:33:23 IVB102 NetworkManager[2824]: <info>  [1469766803.1003] policy: set 'Wired connection 1' (eno1) as default for IPv4 routing and DNS
>Jul 29 06:33:23 IVB102 NetworkManager[2824]: <info>  [1469766803.1011] DNS: starting dnsmasq...
>Jul 29 06:33:23 IVB102 NetworkManager[2824]: <warn>  [1469766803.1191] dnsmasq[0x21d5840]: dnsmasq not found on the bus. The nameserver update will be sent when dnsmasq appears
>Jul 29 06:33:23 IVB102 NetworkManager[2824]: <info>  [1469766803.1192] dns-mgr: Writing DNS information to /sbin/resolvconf
>Jul 29 06:33:23 IVB102 NetworkManager[2824]: <info>  [1469766803.3976] device (eno1): Activation: successful, device activated.
>Jul 29 06:33:23 IVB102 NetworkManager[2824]: <info>  [1469766803.3989] dnsmasq[0x21d5840]: dnsmasq appeared as :1.35
>Jul 29 06:33:23 IVB102 NetworkManager[2824]: <info>  [1469766803.3990] dns-mgr: Writing DNS information to /sbin/resolvconf
>Jul 29 06:33:28 IVB102 NetworkManager[2824]: <info>  [1469766808.2377] manager: startup complete
>Jul 29 06:33:29 IVB102 NetworkManager[2824]: <info>  [1469766809.2351] WiFi hardware radio set enabled
>Jul 29 06:33:29 IVB102 NetworkManager[2824]: <info>  [1469766809.2351] WWAN hardware radio set enabled
>Jul 29 06:36:00 IVB102 kernel: [  176.471632] [drm:i915_gem_open] 
>Jul 29 06:36:00 IVB102 kernel: [  176.472121] [drm:i915_gem_open] 
>Jul 29 06:36:00 IVB102 kernel: [  176.472163] [drm:i915_ring_test_irq_set] Masking interrupts on rings 0x00000007
>Jul 29 06:36:02 IVB102 kernel: [  177.877083] [drm:i915_gem_idle_work_handler] kicked stuck waiters (1)...missed irq?
>Jul 29 06:36:03 IVB102 kernel: [  178.913040] [drm:i915_gem_idle_work_handler] kicked stuck waiters (4)...missed irq?
>Jul 29 06:36:05 IVB102 kernel: [  180.900957] [drm:i915_gem_idle_work_handler] kicked stuck waiters (4)...missed irq?
>Jul 29 06:36:06 IVB102 kernel: [  181.908915] [drm:i915_gem_idle_work_handler] kicked stuck waiters (4)...missed irq?
>Jul 29 06:36:08 IVB102 kernel: [  183.912838] [drm:i915_gem_idle_work_handler] kicked stuck waiters (2)...missed irq?
>Jul 29 06:36:08 IVB102 kernel: [  183.913551] [drm:i915_ring_test_irq_set] Masking interrupts on rings 0x00000000

Actions: View

Attachments on bug 97104: 125363 | 125520 | 125521 | 125522

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.