april 21 09:04:31 monster kernel: Initializing cgroup subsys cpuset april 21 09:04:31 monster kernel: Initializing cgroup subsys cpu april 21 09:04:31 monster kernel: Initializing cgroup subsys cpuacct april 21 09:04:31 monster kernel: Linux version 3.19.0-15-generic (buildd@komainu) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ) #15-Ubuntu SMP Thu Apr 16 23:32:37 UTC 2015 (Ubuntu 3.19.0-15.15-generic 3.19.3) april 21 09:04:31 monster kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=f99b1ed0-5a42-4536-9899-d3e982f1c048 ro april 21 09:04:31 monster kernel: KERNEL supported cpus: april 21 09:04:31 monster kernel: Intel GenuineIntel april 21 09:04:31 monster kernel: AMD AuthenticAMD april 21 09:04:31 monster kernel: Centaur CentaurHauls april 21 09:04:31 monster kernel: tseg: 0000000000 april 21 09:04:31 monster kernel: e820: BIOS-provided physical RAM map: april 21 09:04:31 monster kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009abff] usable april 21 09:04:31 monster kernel: BIOS-e820: [mem 0x000000000009ac00-0x000000000009ffff] reserved april 21 09:04:31 monster kernel: BIOS-e820: [mem 0x00000000000e2000-0x00000000000fffff] reserved april 21 09:04:31 monster kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000cfe8ffff] usable april 21 09:04:31 monster kernel: BIOS-e820: [mem 0x00000000cfe90000-0x00000000cfea7fff] ACPI data april 21 09:04:31 monster kernel: BIOS-e820: [mem 0x00000000cfea8000-0x00000000cfecffff] ACPI NVS april 21 09:04:31 monster kernel: BIOS-e820: [mem 0x00000000cfed0000-0x00000000cfefffff] reserved april 21 09:04:31 monster kernel: BIOS-e820: [mem 0x00000000ffe00000-0x00000000ffffffff] reserved april 21 09:04:31 monster kernel: BIOS-e820: [mem 0x0000000100000000-0x000000042fffffff] usable april 21 09:04:31 monster kernel: NX (Execute Disable) protection: active april 21 09:04:31 monster kernel: SMBIOS 2.6 present. april 21 09:04:31 monster kernel: DMI: System manufacturer System Product Name/Crosshair IV Extreme, BIOS 2002 04/01/2011 april 21 09:04:31 monster kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved april 21 09:04:31 monster kernel: e820: remove [mem 0x000a0000-0x000fffff] usable april 21 09:04:31 monster kernel: AGP: No AGP bridge found april 21 09:04:31 monster kernel: e820: last_pfn = 0x430000 max_arch_pfn = 0x400000000 april 21 09:04:31 monster kernel: MTRR default type: uncachable april 21 09:04:31 monster kernel: MTRR fixed ranges enabled: april 21 09:04:31 monster kernel: 00000-9FFFF write-back april 21 09:04:31 monster kernel: A0000-EFFFF uncachable april 21 09:04:31 monster kernel: F0000-FFFFF write-protect april 21 09:04:31 monster kernel: MTRR variable ranges enabled: april 21 09:04:31 monster kernel: 0 base 000000000000 mask FFFF80000000 write-back april 21 09:04:31 monster kernel: 1 base 000080000000 mask FFFFC0000000 write-back april 21 09:04:31 monster kernel: 2 base 0000C0000000 mask FFFFF0000000 write-back april 21 09:04:31 monster kernel: 3 disabled april 21 09:04:31 monster kernel: 4 disabled april 21 09:04:31 monster kernel: 5 disabled april 21 09:04:31 monster kernel: 6 disabled april 21 09:04:31 monster kernel: 7 disabled april 21 09:04:31 monster kernel: TOM2: 0000000430000000 aka 17152M april 21 09:04:31 monster kernel: PAT configuration [0-7]: WB WC UC- UC WB WC UC- UC april 21 09:04:31 monster kernel: e820: update [mem 0xd0000000-0xffffffff] usable ==> reserved april 21 09:04:31 monster kernel: e820: last_pfn = 0xcfe90 max_arch_pfn = 0x400000000 april 21 09:04:31 monster kernel: found SMP MP-table at [mem 0x000ff780-0x000ff78f] mapped at [ffff8800000ff780] april 21 09:04:31 monster kernel: Scanning 1 areas for low memory corruption april 21 09:04:31 monster kernel: Base memory trampoline at [ffff880000094000] 94000 size 24576 april 21 09:04:31 monster kernel: Using GB pages for direct mapping april 21 09:04:31 monster kernel: init_memory_mapping: [mem 0x00000000-0x000fffff] april 21 09:04:31 monster kernel: [mem 0x00000000-0x000fffff] page 4k april 21 09:04:31 monster kernel: BRK [0x01fe5000, 0x01fe5fff] PGTABLE april 21 09:04:31 monster kernel: BRK [0x01fe6000, 0x01fe6fff] PGTABLE april 21 09:04:31 monster kernel: BRK [0x01fe7000, 0x01fe7fff] PGTABLE april 21 09:04:31 monster kernel: init_memory_mapping: [mem 0x42fe00000-0x42fffffff] april 21 09:04:31 monster kernel: [mem 0x42fe00000-0x42fffffff] page 2M april 21 09:04:31 monster kernel: BRK [0x01fe8000, 0x01fe8fff] PGTABLE april 21 09:04:31 monster kernel: init_memory_mapping: [mem 0x420000000-0x42fdfffff] april 21 09:04:31 monster kernel: [mem 0x420000000-0x42fdfffff] page 2M april 21 09:04:31 monster kernel: init_memory_mapping: [mem 0x400000000-0x41fffffff] april 21 09:04:31 monster kernel: [mem 0x400000000-0x41fffffff] page 2M april 21 09:04:31 monster kernel: init_memory_mapping: [mem 0x00100000-0xcfe8ffff] april 21 09:04:31 monster kernel: [mem 0x00100000-0x001fffff] page 4k april 21 09:04:31 monster kernel: [mem 0x00200000-0x3fffffff] page 2M april 21 09:04:31 monster kernel: [mem 0x40000000-0xbfffffff] page 1G april 21 09:04:31 monster kernel: [mem 0xc0000000-0xcfdfffff] page 2M april 21 09:04:31 monster kernel: [mem 0xcfe00000-0xcfe8ffff] page 4k april 21 09:04:31 monster kernel: init_memory_mapping: [mem 0x100000000-0x3ffffffff] april 21 09:04:31 monster kernel: [mem 0x100000000-0x3ffffffff] page 1G april 21 09:04:31 monster kernel: RAMDISK: [mem 0x34218000-0x36103fff] april 21 09:04:31 monster kernel: ACPI: Early table checksum verification disabled april 21 09:04:31 monster kernel: ACPI: RSDP 0x00000000000FBE90 000024 (v02 ACPIAM) april 21 09:04:31 monster kernel: ACPI: XSDT 0x00000000CFE90100 000064 (v01 040111 XSDT2024 20110401 MSFT 00000097) april 21 09:04:31 monster kernel: ACPI: FACP 0x00000000CFE90290 0000F4 (v03 040111 FACP2024 20110401 MSFT 00000097) april 21 09:04:31 monster kernel: ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Gpe0Block: 64/32 (20141107/tbfadt-618) april 21 09:04:31 monster kernel: ACPI: DSDT 0x00000000CFE90460 00DEDD (v01 A1546 A1546000 00000000 INTL 20060113) april 21 09:04:31 monster kernel: ACPI: FACS 0x00000000CFEA8000 000040 april 21 09:04:31 monster kernel: ACPI: APIC 0x00000000CFE90390 000088 (v01 040111 APIC2024 20110401 MSFT 00000097) april 21 09:04:31 monster kernel: ACPI: MCFG 0x00000000CFE90420 00003C (v01 040111 OEMMCFG 20110401 MSFT 00000097) april 21 09:04:31 monster kernel: ACPI: OEMB 0x00000000CFEA8040 000072 (v01 040111 OEMB2024 20110401 MSFT 00000097) april 21 09:04:31 monster kernel: ACPI: SRAT 0x00000000CFE9F8B0 0000E8 (v01 AMD FAM_F_10 00000002 AMD 00000001) april 21 09:04:31 monster kernel: ACPI: HPET 0x00000000CFE9F9A0 000038 (v01 040111 OEMHPET 20110401 MSFT 00000097) april 21 09:04:31 monster kernel: ACPI: IVRS 0x00000000CFE9F9E0 0000D0 (v01 AMD RD890S 00202031 AMD 00000000) april 21 09:04:31 monster kernel: ACPI: SSDT 0x00000000CFE9FAB0 00088C (v01 A M I POWERNOW 00000001 AMD 00000001) april 21 09:04:31 monster kernel: ACPI: Local APIC address 0xfee00000 april 21 09:04:31 monster kernel: SRAT: PXM 0 -> APIC 0x00 -> Node 0 april 21 09:04:31 monster kernel: SRAT: PXM 0 -> APIC 0x01 -> Node 0 april 21 09:04:31 monster kernel: SRAT: PXM 0 -> APIC 0x02 -> Node 0 april 21 09:04:31 monster kernel: SRAT: PXM 0 -> APIC 0x03 -> Node 0 april 21 09:04:31 monster kernel: SRAT: Node 0 PXM 0 [mem 0x00000000-0x0009ffff] april 21 09:04:31 monster kernel: SRAT: Node 0 PXM 0 [mem 0x00100000-0xcfffffff] april 21 09:04:31 monster kernel: SRAT: Node 0 PXM 0 [mem 0x100000000-0x42fffffff] april 21 09:04:31 monster kernel: NUMA: Node 0 [mem 0x00000000-0x0009ffff] + [mem 0x00100000-0xcfffffff] -> [mem 0x00000000-0xcfffffff] april 21 09:04:31 monster kernel: NUMA: Node 0 [mem 0x00000000-0xcfffffff] + [mem 0x100000000-0x42fffffff] -> [mem 0x00000000-0x42fffffff] april 21 09:04:31 monster kernel: NODE_DATA(0) allocated [mem 0x42fff9000-0x42fffdfff] april 21 09:04:31 monster kernel: [ffffea0000000000-ffffea0010bfffff] PMD -> [ffff88041f600000-ffff88042f5fffff] on node 0 april 21 09:04:31 monster kernel: Zone ranges: april 21 09:04:31 monster kernel: DMA [mem 0x00001000-0x00ffffff] april 21 09:04:31 monster kernel: DMA32 [mem 0x01000000-0xffffffff] april 21 09:04:31 monster kernel: Normal [mem 0x100000000-0x42fffffff] april 21 09:04:31 monster kernel: Movable zone start for each node april 21 09:04:31 monster kernel: Early memory node ranges april 21 09:04:31 monster kernel: node 0: [mem 0x00001000-0x00099fff] april 21 09:04:31 monster kernel: node 0: [mem 0x00100000-0xcfe8ffff] april 21 09:04:31 monster kernel: node 0: [mem 0x100000000-0x42fffffff] april 21 09:04:31 monster kernel: Initmem setup node 0 [mem 0x00001000-0x42fffffff] april 21 09:04:31 monster kernel: On node 0 totalpages: 4193833 april 21 09:04:31 monster kernel: DMA zone: 64 pages used for memmap april 21 09:04:31 monster kernel: DMA zone: 21 pages reserved april 21 09:04:31 monster kernel: DMA zone: 3993 pages, LIFO batch:0 april 21 09:04:31 monster kernel: DMA32 zone: 13243 pages used for memmap april 21 09:04:31 monster kernel: DMA32 zone: 847504 pages, LIFO batch:31 april 21 09:04:31 monster kernel: Normal zone: 52224 pages used for memmap april 21 09:04:31 monster kernel: Normal zone: 3342336 pages, LIFO batch:31 april 21 09:04:31 monster kernel: ACPI: PM-Timer IO Port: 0x808 april 21 09:04:31 monster kernel: ACPI: Local APIC address 0xfee00000 april 21 09:04:31 monster kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) april 21 09:04:31 monster kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) april 21 09:04:31 monster kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled) april 21 09:04:31 monster kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled) april 21 09:04:31 monster kernel: ACPI: LAPIC (acpi_id[0x05] lapic_id[0x84] disabled) april 21 09:04:31 monster kernel: ACPI: LAPIC (acpi_id[0x06] lapic_id[0x85] disabled) april 21 09:04:31 monster kernel: ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0]) april 21 09:04:31 monster kernel: IOAPIC[0]: apic_id 4, version 33, address 0xfec00000, GSI 0-23 april 21 09:04:31 monster kernel: ACPI: IOAPIC (id[0x05] address[0xfec20000] gsi_base[24]) april 21 09:04:31 monster kernel: IOAPIC[1]: apic_id 5, version 33, address 0xfec20000, GSI 24-55 april 21 09:04:31 monster kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) april 21 09:04:31 monster kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) april 21 09:04:31 monster kernel: ACPI: IRQ0 used by override. april 21 09:04:31 monster kernel: ACPI: IRQ9 used by override. april 21 09:04:31 monster kernel: Using ACPI (MADT) for SMP configuration information april 21 09:04:31 monster kernel: ACPI: HPET id: 0x8300 base: 0xfed00000 april 21 09:04:31 monster kernel: smpboot: Allowing 6 CPUs, 2 hotplug CPUs april 21 09:04:31 monster kernel: PM: Registered nosave memory: [mem 0x00000000-0x00000fff] april 21 09:04:31 monster kernel: PM: Registered nosave memory: [mem 0x0009a000-0x0009afff] april 21 09:04:31 monster kernel: PM: Registered nosave memory: [mem 0x0009b000-0x0009ffff] april 21 09:04:31 monster kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000e1fff] april 21 09:04:31 monster kernel: PM: Registered nosave memory: [mem 0x000e2000-0x000fffff] april 21 09:04:31 monster kernel: PM: Registered nosave memory: [mem 0xcfe90000-0xcfea7fff] april 21 09:04:31 monster kernel: PM: Registered nosave memory: [mem 0xcfea8000-0xcfecffff] april 21 09:04:31 monster kernel: PM: Registered nosave memory: [mem 0xcfed0000-0xcfefffff] april 21 09:04:31 monster kernel: PM: Registered nosave memory: [mem 0xcff00000-0xffdfffff] april 21 09:04:31 monster kernel: PM: Registered nosave memory: [mem 0xffe00000-0xffffffff] april 21 09:04:31 monster kernel: e820: [mem 0xcff00000-0xffdfffff] available for PCI devices april 21 09:04:31 monster kernel: Booting paravirtualized kernel on bare hardware april 21 09:04:31 monster kernel: setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:6 nr_node_ids:1 april 21 09:04:31 monster kernel: PERCPU: Embedded 31 pages/cpu @ffff88042fc00000 s87040 r8192 d31744 u262144 april 21 09:04:31 monster kernel: pcpu-alloc: s87040 r8192 d31744 u262144 alloc=1*2097152 april 21 09:04:31 monster kernel: pcpu-alloc: [0] 0 1 2 3 4 5 - - april 21 09:04:31 monster kernel: Built 1 zonelists in Node order, mobility grouping on. Total pages: 4128281 april 21 09:04:31 monster kernel: Policy zone: Normal april 21 09:04:31 monster kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=f99b1ed0-5a42-4536-9899-d3e982f1c048 ro april 21 09:04:31 monster kernel: PID hash table entries: 4096 (order: 3, 32768 bytes) april 21 09:04:31 monster kernel: AGP: Checking aperture... april 21 09:04:31 monster kernel: AGP: No AGP bridge found april 21 09:04:31 monster kernel: AGP: Node 0: aperture [bus addr 0xc4000000-0xc5ffffff] (32MB) april 21 09:04:31 monster kernel: Aperture pointing to e820 RAM. Ignoring. april 21 09:04:31 monster kernel: AGP: Your BIOS doesn't leave a aperture memory hole april 21 09:04:31 monster kernel: AGP: Please enable the IOMMU option in the BIOS setup april 21 09:04:31 monster kernel: AGP: This costs you 64MB of RAM april 21 09:04:31 monster kernel: AGP: Mapping aperture over RAM [mem 0xc4000000-0xc7ffffff] (65536KB) april 21 09:04:31 monster kernel: PM: Registered nosave memory: [mem 0xc4000000-0xc7ffffff] april 21 09:04:31 monster kernel: Memory: 16332532K/16775332K available (7993K kernel code, 1232K rwdata, 3752K rodata, 1408K init, 1300K bss, 442800K reserved, 0K cma-reserved) april 21 09:04:31 monster kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=6, Nodes=1 april 21 09:04:31 monster kernel: Hierarchical RCU implementation. april 21 09:04:31 monster kernel: RCU dyntick-idle grace-period acceleration is enabled. april 21 09:04:31 monster kernel: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=6. april 21 09:04:31 monster kernel: RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=6 april 21 09:04:31 monster kernel: NR_IRQS:16640 nr_irqs:1016 16 april 21 09:04:31 monster kernel: Offload RCU callbacks from all CPUs april 21 09:04:31 monster kernel: Offload RCU callbacks from CPUs: 0-5. april 21 09:04:31 monster kernel: spurious 8259A interrupt: IRQ7. april 21 09:04:31 monster kernel: Console: colour dummy device 80x25 april 21 09:04:31 monster kernel: console [tty0] enabled april 21 09:04:31 monster kernel: hpet clockevent registered april 21 09:04:31 monster kernel: tsc: Fast TSC calibration using PIT april 21 09:04:31 monster kernel: tsc: Detected 3411.241 MHz processor april 21 09:04:31 monster kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 6822.48 BogoMIPS (lpj=13644964) april 21 09:04:31 monster kernel: pid_max: default: 32768 minimum: 301 april 21 09:04:31 monster kernel: ACPI: Core revision 20141107 april 21 09:04:31 monster kernel: ACPI: All ACPI Tables successfully acquired april 21 09:04:31 monster kernel: Security Framework initialized april 21 09:04:31 monster kernel: AppArmor: AppArmor initialized april 21 09:04:31 monster kernel: Yama: becoming mindful. april 21 09:04:31 monster kernel: Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes) april 21 09:04:31 monster kernel: Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes) april 21 09:04:31 monster kernel: Mount-cache hash table entries: 32768 (order: 6, 262144 bytes) april 21 09:04:31 monster kernel: Mountpoint-cache hash table entries: 32768 (order: 6, 262144 bytes) april 21 09:04:31 monster kernel: Initializing cgroup subsys memory april 21 09:04:31 monster kernel: Initializing cgroup subsys devices april 21 09:04:31 monster kernel: Initializing cgroup subsys freezer april 21 09:04:31 monster kernel: Initializing cgroup subsys net_cls april 21 09:04:31 monster kernel: Initializing cgroup subsys blkio april 21 09:04:31 monster kernel: Initializing cgroup subsys perf_event april 21 09:04:31 monster kernel: Initializing cgroup subsys net_prio april 21 09:04:31 monster kernel: Initializing cgroup subsys hugetlb april 21 09:04:31 monster kernel: CPU: Physical Processor ID: 0 april 21 09:04:31 monster kernel: CPU: Processor Core ID: 0 april 21 09:04:31 monster kernel: mce: CPU supports 6 MCE banks april 21 09:04:31 monster kernel: LVT offset 0 assigned for vector 0xf9 april 21 09:04:31 monster kernel: process: using AMD E400 aware idle routine april 21 09:04:31 monster kernel: Last level iTLB entries: 4KB 512, 2MB 16, 4MB 8 april 21 09:04:31 monster kernel: Freeing SMP alternatives memory: 32K (ffffffff81e96000 - ffffffff81e9e000) april 21 09:04:31 monster kernel: ftrace: allocating 30078 entries in 118 pages april 21 09:04:31 monster kernel: [Firmware Bug]: AMD-Vi: IOAPIC[4] not in IVRS table april 21 09:04:31 monster kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found april 21 09:04:31 monster kernel: AMD-Vi: Disabling interrupt remapping april 21 09:04:31 monster kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 april 21 09:04:31 monster kernel: smpboot: CPU0: AMD Phenom(tm) II X4 965 Processor (fam: 10, model: 04, stepping: 03) april 21 09:04:31 monster kernel: Performance Events: AMD PMU driver. april 21 09:04:31 monster kernel: ... version: 0 april 21 09:04:31 monster kernel: ... bit width: 48 april 21 09:04:31 monster kernel: ... generic registers: 4 april 21 09:04:31 monster kernel: ... value mask: 0000ffffffffffff april 21 09:04:31 monster kernel: ... max period: 00007fffffffffff april 21 09:04:31 monster kernel: ... fixed-purpose events: 0 april 21 09:04:31 monster kernel: ... event mask: 000000000000000f april 21 09:04:31 monster kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter. april 21 09:04:31 monster kernel: x86: Booting SMP configuration: april 21 09:04:31 monster kernel: .... node #0, CPUs: #1 april 21 09:04:31 monster kernel: process: System has AMD C1E enabled april 21 09:04:31 monster kernel: process: Switch to broadcast mode on CPU1 april 21 09:04:31 monster kernel: #2 april 21 09:04:31 monster kernel: process: Switch to broadcast mode on CPU2 april 21 09:04:31 monster kernel: #3 april 21 09:04:31 monster kernel: x86: Booted up 1 node, 4 CPUs april 21 09:04:31 monster kernel: smpboot: Total of 4 processors activated (27289.92 BogoMIPS) april 21 09:04:31 monster kernel: process: Switch to broadcast mode on CPU3 april 21 09:04:31 monster kernel: process: Switch to broadcast mode on CPU0 april 21 09:04:31 monster kernel: devtmpfs: initialized april 21 09:04:31 monster kernel: evm: security.selinux april 21 09:04:31 monster kernel: evm: security.SMACK64 april 21 09:04:31 monster kernel: evm: security.SMACK64EXEC april 21 09:04:31 monster kernel: evm: security.SMACK64TRANSMUTE april 21 09:04:31 monster kernel: evm: security.SMACK64MMAP april 21 09:04:31 monster kernel: evm: security.ima april 21 09:04:31 monster kernel: evm: security.capability april 21 09:04:31 monster kernel: PM: Registering ACPI NVS region [mem 0xcfea8000-0xcfecffff] (163840 bytes) april 21 09:04:31 monster kernel: pinctrl core: initialized pinctrl subsystem april 21 09:04:31 monster kernel: RTC time: 7:04:26, date: 04/21/15 april 21 09:04:31 monster kernel: NET: Registered protocol family 16 april 21 09:04:31 monster kernel: cpuidle: using governor ladder april 21 09:04:31 monster kernel: cpuidle: using governor menu april 21 09:04:31 monster kernel: node 0 link 0: io port [1000, ffffff] april 21 09:04:31 monster kernel: TOM: 00000000d0000000 aka 3328M april 21 09:04:31 monster kernel: Fam 10h mmconf [mem 0xe0000000-0xefffffff] april 21 09:04:31 monster kernel: node 0 link 0: mmio [e0000000, efffffff] ==> none april 21 09:04:31 monster kernel: node 0 link 0: mmio [f0000000, ffffffff] april 21 09:04:31 monster kernel: node 0 link 0: mmio [a0000, bffff] april 21 09:04:31 monster kernel: node 0 link 0: mmio [d0000000, dfffffff] april 21 09:04:31 monster kernel: TOM2: 0000000430000000 aka 17152M april 21 09:04:31 monster kernel: bus: [bus 00-07] on node 0 link 0 april 21 09:04:31 monster kernel: bus: 00 [io 0x0000-0xffff] april 21 09:04:31 monster kernel: bus: 00 [mem 0xf0000000-0xffffffff] april 21 09:04:31 monster kernel: bus: 00 [mem 0x000a0000-0x000bffff] april 21 09:04:31 monster kernel: bus: 00 [mem 0xd0000000-0xdfffffff] april 21 09:04:31 monster kernel: bus: 00 [mem 0x430000000-0xfcffffffff] april 21 09:04:31 monster kernel: ACPI: bus type PCI registered april 21 09:04:31 monster kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 april 21 09:04:31 monster kernel: PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000) april 21 09:04:31 monster kernel: PCI: not using MMCONFIG april 21 09:04:31 monster kernel: PCI: Using configuration type 1 for base access april 21 09:04:31 monster kernel: PCI: Using configuration type 1 for extended access april 21 09:04:31 monster kernel: mtrr: your CPUs had inconsistent variable MTRR settings april 21 09:04:31 monster kernel: mtrr: probably your BIOS does not setup all CPUs. april 21 09:04:31 monster kernel: mtrr: corrected configuration. april 21 09:04:31 monster kernel: ACPI: Added _OSI(Module Device) april 21 09:04:31 monster kernel: ACPI: Added _OSI(Processor Device) april 21 09:04:31 monster kernel: ACPI: Added _OSI(3.0 _SCP Extensions) april 21 09:04:31 monster kernel: ACPI: Added _OSI(Processor Aggregator Device) april 21 09:04:31 monster kernel: ACPI: Executed 3 blocks of module-level executable AML code april 21 09:04:31 monster kernel: ACPI: Interpreter enabled april 21 09:04:31 monster kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20141107/hwxface-580) april 21 09:04:31 monster kernel: ACPI: (supports S0 S1 S3 S4 S5) april 21 09:04:31 monster kernel: ACPI: Using IOAPIC for interrupt routing april 21 09:04:31 monster kernel: PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000) april 21 09:04:31 monster kernel: PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in ACPI motherboard resources april 21 09:04:31 monster kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug april 21 09:04:31 monster kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff]) april 21 09:04:31 monster kernel: acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] april 21 09:04:31 monster kernel: acpi PNP0A03:00: _OSC: platform does not support [PCIeHotplug] april 21 09:04:31 monster kernel: acpi PNP0A03:00: _OSC: OS now controls [PME AER PCIeCapability] april 21 09:04:31 monster kernel: PCI host bridge to bus 0000:00 april 21 09:04:31 monster kernel: pci_bus 0000:00: root bus resource [bus 00-ff] april 21 09:04:31 monster kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7] april 21 09:04:31 monster kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff] april 21 09:04:31 monster kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff] april 21 09:04:31 monster kernel: pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000dffff] april 21 09:04:31 monster kernel: pci_bus 0000:00: root bus resource [mem 0xcff00000-0xdfffffff] april 21 09:04:31 monster kernel: pci_bus 0000:00: root bus resource [mem 0xf0000000-0xfebfffff] april 21 09:04:31 monster kernel: pci 0000:00:00.0: [1002:5a11] type 00 class 0x060000 april 21 09:04:31 monster kernel: pci 0000:00:00.2: [1002:5a23] type 00 class 0x080600 april 21 09:04:31 monster kernel: pci 0000:00:02.0: [1002:5a16] type 01 class 0x060400 april 21 09:04:31 monster kernel: pci 0000:00:02.0: PME# supported from D0 D3hot D3cold april 21 09:04:31 monster kernel: pci 0000:00:02.0: System wakeup disabled by ACPI april 21 09:04:31 monster kernel: pci 0000:00:05.0: [1002:5a19] type 01 class 0x060400 april 21 09:04:31 monster kernel: pci 0000:00:05.0: PME# supported from D0 D3hot D3cold april 21 09:04:31 monster kernel: pci 0000:00:05.0: System wakeup disabled by ACPI april 21 09:04:31 monster kernel: pci 0000:00:06.0: [1002:5a1a] type 01 class 0x060400 april 21 09:04:31 monster kernel: pci 0000:00:06.0: PME# supported from D0 D3hot D3cold april 21 09:04:31 monster kernel: pci 0000:00:06.0: System wakeup disabled by ACPI april 21 09:04:31 monster kernel: pci 0000:00:0a.0: [1002:5a1d] type 01 class 0x060400 april 21 09:04:31 monster kernel: pci 0000:00:0a.0: PME# supported from D0 D3hot D3cold april 21 09:04:31 monster kernel: pci 0000:00:0a.0: System wakeup disabled by ACPI april 21 09:04:31 monster kernel: pci 0000:00:11.0: [1002:4391] type 00 class 0x010601 april 21 09:04:31 monster kernel: pci 0000:00:11.0: reg 0x10: [io 0x9000-0x9007] april 21 09:04:31 monster kernel: pci 0000:00:11.0: reg 0x14: [io 0x8000-0x8003] april 21 09:04:31 monster kernel: pci 0000:00:11.0: reg 0x18: [io 0x7000-0x7007] april 21 09:04:31 monster kernel: pci 0000:00:11.0: reg 0x1c: [io 0x6000-0x6003] april 21 09:04:31 monster kernel: pci 0000:00:11.0: reg 0x20: [io 0x5000-0x500f] april 21 09:04:31 monster kernel: pci 0000:00:11.0: reg 0x24: [mem 0xfe3ffc00-0xfe3fffff] april 21 09:04:31 monster kernel: pci 0000:00:12.0: [1002:4397] type 00 class 0x0c0310 april 21 09:04:31 monster kernel: pci 0000:00:12.0: reg 0x10: [mem 0xfe3fe000-0xfe3fefff] april 21 09:04:31 monster kernel: pci 0000:00:12.0: System wakeup disabled by ACPI april 21 09:04:31 monster kernel: pci 0000:00:12.2: [1002:4396] type 00 class 0x0c0320 april 21 09:04:31 monster kernel: pci 0000:00:12.2: reg 0x10: [mem 0xfe3ff800-0xfe3ff8ff] april 21 09:04:31 monster kernel: pci 0000:00:12.2: supports D1 D2 april 21 09:04:31 monster kernel: pci 0000:00:12.2: PME# supported from D0 D1 D2 D3hot april 21 09:04:31 monster kernel: pci 0000:00:12.2: System wakeup disabled by ACPI april 21 09:04:31 monster kernel: pci 0000:00:13.0: [1002:4397] type 00 class 0x0c0310 april 21 09:04:31 monster kernel: pci 0000:00:13.0: reg 0x10: [mem 0xfe3fd000-0xfe3fdfff] april 21 09:04:31 monster kernel: pci 0000:00:13.0: System wakeup disabled by ACPI april 21 09:04:31 monster kernel: pci 0000:00:13.2: [1002:4396] type 00 class 0x0c0320 april 21 09:04:31 monster kernel: pci 0000:00:13.2: reg 0x10: [mem 0xfe3ff400-0xfe3ff4ff] april 21 09:04:31 monster kernel: pci 0000:00:13.2: supports D1 D2 april 21 09:04:31 monster kernel: pci 0000:00:13.2: PME# supported from D0 D1 D2 D3hot april 21 09:04:31 monster kernel: pci 0000:00:13.2: System wakeup disabled by ACPI april 21 09:04:31 monster kernel: pci 0000:00:14.0: [1002:4385] type 00 class 0x0c0500 april 21 09:04:31 monster kernel: pci 0000:00:14.2: [1002:4383] type 00 class 0x040300 april 21 09:04:31 monster kernel: pci 0000:00:14.2: reg 0x10: [mem 0xfe3f4000-0xfe3f7fff 64bit] april 21 09:04:31 monster kernel: pci 0000:00:14.2: PME# supported from D0 D3hot D3cold april 21 09:04:31 monster kernel: pci 0000:00:14.2: System wakeup disabled by ACPI april 21 09:04:31 monster kernel: pci 0000:00:14.3: [1002:439d] type 00 class 0x060100 april 21 09:04:31 monster kernel: pci 0000:00:14.4: [1002:4384] type 01 class 0x060401 april 21 09:04:31 monster kernel: pci 0000:00:14.4: System wakeup disabled by ACPI april 21 09:04:31 monster kernel: pci 0000:00:14.5: [1002:4399] type 00 class 0x0c0310 april 21 09:04:31 monster kernel: pci 0000:00:14.5: reg 0x10: [mem 0xfe3fc000-0xfe3fcfff] april 21 09:04:31 monster kernel: pci 0000:00:14.5: System wakeup disabled by ACPI april 21 09:04:31 monster kernel: pci 0000:00:15.0: [1002:43a0] type 01 class 0x060400 april 21 09:04:31 monster kernel: pci 0000:00:15.0: supports D1 D2 april 21 09:04:31 monster kernel: pci 0000:00:15.0: System wakeup disabled by ACPI april 21 09:04:31 monster kernel: pci 0000:00:15.1: [1002:43a1] type 01 class 0x060400 april 21 09:04:31 monster kernel: pci 0000:00:15.1: supports D1 D2 april 21 09:04:31 monster kernel: pci 0000:00:15.1: System wakeup disabled by ACPI april 21 09:04:31 monster kernel: pci 0000:00:16.0: [1002:4397] type 00 class 0x0c0310 april 21 09:04:31 monster kernel: pci 0000:00:16.0: reg 0x10: [mem 0xfe3f3000-0xfe3f3fff] april 21 09:04:31 monster kernel: pci 0000:00:16.0: System wakeup disabled by ACPI april 21 09:04:31 monster kernel: pci 0000:00:16.2: [1002:4396] type 00 class 0x0c0320 april 21 09:04:31 monster kernel: pci 0000:00:16.2: reg 0x10: [mem 0xfe3ff000-0xfe3ff0ff] april 21 09:04:31 monster kernel: pci 0000:00:16.2: supports D1 D2 april 21 09:04:31 monster kernel: pci 0000:00:16.2: PME# supported from D0 D1 D2 D3hot april 21 09:04:31 monster kernel: pci 0000:00:16.2: System wakeup disabled by ACPI april 21 09:04:31 monster kernel: pci 0000:00:18.0: [1022:1200] type 00 class 0x060000 april 21 09:04:31 monster kernel: pci 0000:00:18.1: [1022:1201] type 00 class 0x060000 april 21 09:04:31 monster kernel: pci 0000:00:18.2: [1022:1202] type 00 class 0x060000 april 21 09:04:31 monster kernel: pci 0000:00:18.3: [1022:1203] type 00 class 0x060000 april 21 09:04:31 monster kernel: pci 0000:00:18.4: [1022:1204] type 00 class 0x060000 april 21 09:04:31 monster kernel: pci 0000:01:00.0: [1002:68f9] type 00 class 0x030000 april 21 09:04:31 monster kernel: pci 0000:01:00.0: reg 0x10: [mem 0xd0000000-0xdfffffff 64bit pref] april 21 09:04:31 monster kernel: pci 0000:01:00.0: reg 0x18: [mem 0xfe4e0000-0xfe4fffff 64bit] april 21 09:04:31 monster kernel: pci 0000:01:00.0: reg 0x20: [io 0xa000-0xa0ff] april 21 09:04:31 monster kernel: pci 0000:01:00.0: reg 0x30: [mem 0xfe4c0000-0xfe4dffff pref] april 21 09:04:31 monster kernel: pci 0000:01:00.0: supports D1 D2 april 21 09:04:31 monster kernel: pci 0000:01:00.1: [1002:aa68] type 00 class 0x040300 april 21 09:04:31 monster kernel: pci 0000:01:00.1: reg 0x10: [mem 0xfe4bc000-0xfe4bffff 64bit] april 21 09:04:31 monster kernel: pci 0000:01:00.1: supports D1 D2 april 21 09:04:31 monster kernel: pci 0000:00:02.0: PCI bridge to [bus 01] april 21 09:04:31 monster kernel: pci 0000:00:02.0: bridge window [io 0xa000-0xafff] april 21 09:04:31 monster kernel: pci 0000:00:02.0: bridge window [mem 0xfe400000-0xfe4fffff] april 21 09:04:31 monster kernel: pci 0000:00:02.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref] april 21 09:04:31 monster kernel: pci 0000:02:00.0: [197b:2363] type 00 class 0x010185 april 21 09:04:31 monster kernel: pci 0000:02:00.0: reg 0x24: [mem 0xfe5fe000-0xfe5fffff] april 21 09:04:31 monster kernel: pci 0000:02:00.0: PME# supported from D3hot april 21 09:04:31 monster kernel: pci 0000:02:00.1: [197b:2363] type 00 class 0x010185 april 21 09:04:31 monster kernel: pci 0000:02:00.1: reg 0x10: [io 0xbc00-0xbc07] april 21 09:04:31 monster kernel: pci 0000:02:00.1: reg 0x14: [io 0xb880-0xb883] april 21 09:04:31 monster kernel: pci 0000:02:00.1: reg 0x18: [io 0xb800-0xb807] april 21 09:04:31 monster kernel: pci 0000:02:00.1: reg 0x1c: [io 0xb480-0xb483] april 21 09:04:31 monster kernel: pci 0000:02:00.1: reg 0x20: [io 0xb400-0xb40f] april 21 09:04:31 monster kernel: pci 0000:02:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force' april 21 09:04:31 monster kernel: pci 0000:00:05.0: PCI bridge to [bus 02] april 21 09:04:31 monster kernel: pci 0000:00:05.0: bridge window [io 0xb000-0xbfff] april 21 09:04:31 monster kernel: pci 0000:00:05.0: bridge window [mem 0xfe500000-0xfe5fffff] april 21 09:04:31 monster kernel: pci 0000:03:00.0: [197b:2363] type 00 class 0x010185 april 21 09:04:31 monster kernel: pci 0000:03:00.0: reg 0x24: [mem 0xfe6fe000-0xfe6fffff] april 21 09:04:31 monster kernel: pci 0000:03:00.0: PME# supported from D3hot april 21 09:04:31 monster kernel: pci 0000:03:00.1: [197b:2363] type 00 class 0x010185 april 21 09:04:31 monster kernel: pci 0000:03:00.1: reg 0x10: [io 0xcc00-0xcc07] april 21 09:04:31 monster kernel: pci 0000:03:00.1: reg 0x14: [io 0xc880-0xc883] april 21 09:04:31 monster kernel: pci 0000:03:00.1: reg 0x18: [io 0xc800-0xc807] april 21 09:04:31 monster kernel: pci 0000:03:00.1: reg 0x1c: [io 0xc480-0xc483] april 21 09:04:31 monster kernel: pci 0000:03:00.1: reg 0x20: [io 0xc400-0xc40f] april 21 09:04:31 monster kernel: pci 0000:03:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force' april 21 09:04:31 monster kernel: pci 0000:00:06.0: PCI bridge to [bus 03] april 21 09:04:31 monster kernel: pci 0000:00:06.0: bridge window [io 0xc000-0xcfff] april 21 09:04:31 monster kernel: pci 0000:00:06.0: bridge window [mem 0xfe600000-0xfe6fffff] april 21 09:04:31 monster kernel: pci 0000:04:00.0: [1033:0194] type 00 class 0x0c0330 april 21 09:04:31 monster kernel: pci 0000:04:00.0: reg 0x10: [mem 0xfe7fe000-0xfe7fffff 64bit] april 21 09:04:31 monster kernel: pci 0000:04:00.0: PME# supported from D0 D3hot D3cold april 21 09:04:31 monster kernel: pci 0000:00:0a.0: PCI bridge to [bus 04] april 21 09:04:31 monster kernel: pci 0000:00:0a.0: bridge window [mem 0xfe700000-0xfe7fffff] april 21 09:04:31 monster kernel: pci 0000:00:14.4: PCI bridge to [bus 05] (subtractive decode) april 21 09:04:31 monster kernel: pci 0000:00:14.4: bridge window [io 0x0000-0x0cf7] (subtractive decode) april 21 09:04:31 monster kernel: pci 0000:00:14.4: bridge window [io 0x0d00-0xffff] (subtractive decode) april 21 09:04:31 monster kernel: pci 0000:00:14.4: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode) april 21 09:04:31 monster kernel: pci 0000:00:14.4: bridge window [mem 0x000d0000-0x000dffff] (subtractive decode) april 21 09:04:31 monster kernel: pci 0000:00:14.4: bridge window [mem 0xcff00000-0xdfffffff] (subtractive decode) april 21 09:04:31 monster kernel: pci 0000:00:14.4: bridge window [mem 0xf0000000-0xfebfffff] (subtractive decode) april 21 09:04:31 monster kernel: pci 0000:06:00.0: [1106:3403] type 00 class 0x0c0010 april 21 09:04:31 monster kernel: pci 0000:06:00.0: reg 0x10: [mem 0xfe8ff800-0xfe8fffff 64bit] april 21 09:04:31 monster kernel: pci 0000:06:00.0: reg 0x18: [io 0xd800-0xd8ff] april 21 09:04:31 monster kernel: pci 0000:06:00.0: supports D2 april 21 09:04:31 monster kernel: pci 0000:06:00.0: PME# supported from D2 D3hot D3cold april 21 09:04:31 monster kernel: pci 0000:00:15.0: PCI bridge to [bus 06] april 21 09:04:31 monster kernel: pci 0000:00:15.0: bridge window [io 0xd000-0xdfff] april 21 09:04:31 monster kernel: pci 0000:00:15.0: bridge window [mem 0xfe800000-0xfe8fffff] april 21 09:04:31 monster kernel: pci 0000:07:00.0: [8086:150c] type 00 class 0x020000 april 21 09:04:31 monster kernel: pci 0000:07:00.0: reg 0x10: [mem 0xfe9e0000-0xfe9fffff] april 21 09:04:31 monster kernel: pci 0000:07:00.0: reg 0x18: [io 0xec00-0xec1f] april 21 09:04:31 monster kernel: pci 0000:07:00.0: reg 0x1c: [mem 0xfe9dc000-0xfe9dffff] april 21 09:04:31 monster kernel: pci 0000:07:00.0: PME# supported from D0 D3hot D3cold april 21 09:04:31 monster kernel: pci 0000:00:15.1: PCI bridge to [bus 07] april 21 09:04:31 monster kernel: pci 0000:00:15.1: bridge window [io 0xe000-0xefff] april 21 09:04:31 monster kernel: pci 0000:00:15.1: bridge window [mem 0xfe900000-0xfe9fffff] april 21 09:04:31 monster kernel: pci_bus 0000:00: on NUMA node 0 april 21 09:04:31 monster kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs *4 7 10 11 14 15) april 21 09:04:31 monster kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 4 7 10 *11 14 15) april 21 09:04:31 monster kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 4 7 *10 11 14 15) april 21 09:04:31 monster kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 4 7 *10 11 14 15) april 21 09:04:31 monster kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 4 7 *10 11 14 15) april 21 09:04:31 monster kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 4 7 10 *11 14 15) april 21 09:04:31 monster kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 4 *7 10 11 14 15) april 21 09:04:31 monster kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 4 7 *10 11 14 15) april 21 09:04:31 monster kernel: ACPI : EC: GPE = 0xa, I/O: command/status = 0x66, data = 0x62 april 21 09:04:31 monster kernel: vgaarb: setting as boot device: PCI:0000:01:00.0 april 21 09:04:31 monster kernel: vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none april 21 09:04:31 monster kernel: vgaarb: loaded april 21 09:04:31 monster kernel: vgaarb: bridge control possible 0000:01:00.0 april 21 09:04:31 monster kernel: SCSI subsystem initialized april 21 09:04:31 monster kernel: libata version 3.00 loaded. april 21 09:04:31 monster kernel: ACPI: bus type USB registered april 21 09:04:31 monster kernel: usbcore: registered new interface driver usbfs april 21 09:04:31 monster kernel: usbcore: registered new interface driver hub april 21 09:04:31 monster kernel: usbcore: registered new device driver usb april 21 09:04:31 monster kernel: PCI: Using ACPI for IRQ routing april 21 09:04:31 monster kernel: PCI: pci_cache_line_size set to 64 bytes april 21 09:04:31 monster kernel: e820: reserve RAM buffer [mem 0x0009ac00-0x0009ffff] april 21 09:04:31 monster kernel: e820: reserve RAM buffer [mem 0xcfe90000-0xcfffffff] april 21 09:04:31 monster kernel: NetLabel: Initializing april 21 09:04:31 monster kernel: NetLabel: domain hash size = 128 april 21 09:04:31 monster kernel: NetLabel: protocols = UNLABELED CIPSOv4 april 21 09:04:31 monster kernel: NetLabel: unlabeled traffic allowed by default april 21 09:04:31 monster kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0 april 21 09:04:31 monster kernel: hpet0: 3 comparators, 32-bit 14.318180 MHz counter april 21 09:04:31 monster kernel: Switched to clocksource hpet april 21 09:04:31 monster kernel: AppArmor: AppArmor Filesystem Enabled april 21 09:04:31 monster kernel: pnp: PnP ACPI init april 21 09:04:31 monster kernel: system 00:00: [mem 0xfec20000-0xfec200ff] could not be reserved april 21 09:04:31 monster kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active) april 21 09:04:31 monster kernel: system 00:01: [mem 0xf6000000-0xf6003fff] could not be reserved april 21 09:04:31 monster kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active) april 21 09:04:31 monster kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active) april 21 09:04:31 monster kernel: system 00:03: [mem 0xfec00000-0xfec00fff] could not be reserved april 21 09:04:31 monster kernel: system 00:03: [mem 0xfee00000-0xfee00fff] has been reserved april 21 09:04:31 monster kernel: system 00:03: Plug and Play ACPI device, IDs PNP0c02 (active) april 21 09:04:31 monster kernel: system 00:04: [io 0x04d0-0x04d1] has been reserved april 21 09:04:31 monster kernel: system 00:04: [io 0x040b] has been reserved april 21 09:04:31 monster kernel: system 00:04: [io 0x04d6] has been reserved april 21 09:04:31 monster kernel: system 00:04: [io 0x0c00-0x0c01] has been reserved april 21 09:04:31 monster kernel: system 00:04: [io 0x0c14] has been reserved april 21 09:04:31 monster kernel: system 00:04: [io 0x0c50-0x0c51] has been reserved april 21 09:04:31 monster kernel: system 00:04: [io 0x0c52] has been reserved april 21 09:04:31 monster kernel: system 00:04: [io 0x0c6c] has been reserved april 21 09:04:31 monster kernel: system 00:04: [io 0x0c6f] has been reserved april 21 09:04:31 monster kernel: system 00:04: [io 0x0cd0-0x0cd1] has been reserved april 21 09:04:31 monster kernel: system 00:04: [io 0x0cd2-0x0cd3] has been reserved april 21 09:04:31 monster kernel: system 00:04: [io 0x0cd4-0x0cd5] has been reserved april 21 09:04:31 monster kernel: system 00:04: [io 0x0cd6-0x0cd7] has been reserved april 21 09:04:31 monster kernel: system 00:04: [io 0x0cd8-0x0cdf] has been reserved april 21 09:04:31 monster kernel: system 00:04: [io 0x0800-0x089f] could not be reserved april 21 09:04:31 monster kernel: system 00:04: [io 0x0b00-0x0b1f] has been reserved april 21 09:04:31 monster kernel: system 00:04: [io 0x0b20-0x0b3f] has been reserved april 21 09:04:31 monster kernel: system 00:04: [io 0x0900-0x090f] has been reserved april 21 09:04:31 monster kernel: system 00:04: [io 0x0910-0x091f] has been reserved april 21 09:04:31 monster kernel: system 00:04: [io 0xfe00-0xfefe] has been reserved april 21 09:04:31 monster kernel: system 00:04: [mem 0xcff00000-0xcfffffff] has been reserved april 21 09:04:31 monster kernel: system 00:04: [mem 0xffb80000-0xffbfffff] has been reserved april 21 09:04:31 monster kernel: system 00:04: [mem 0xfec10000-0xfec1001f] has been reserved april 21 09:04:31 monster kernel: system 00:04: [mem 0xfed80000-0xfed80fff] has been reserved april 21 09:04:31 monster kernel: system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active) april 21 09:04:31 monster kernel: system 00:05: [io 0x0230-0x023f] has been reserved april 21 09:04:31 monster kernel: system 00:05: [io 0x0290-0x029f] has been reserved april 21 09:04:31 monster kernel: system 00:05: [io 0x0f40-0x0f4f] has been reserved april 21 09:04:31 monster kernel: system 00:05: [io 0x0a30-0x0a3f] has been reserved april 21 09:04:31 monster kernel: system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active) april 21 09:04:31 monster kernel: system 00:06: [mem 0xe0000000-0xefffffff] has been reserved april 21 09:04:31 monster kernel: system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active) april 21 09:04:31 monster kernel: system 00:07: [mem 0x00000000-0x0009ffff] could not be reserved april 21 09:04:31 monster kernel: system 00:07: [mem 0x000c0000-0x000cffff] could not be reserved april 21 09:04:31 monster kernel: system 00:07: [mem 0x000e0000-0x000fffff] could not be reserved april 21 09:04:31 monster kernel: system 00:07: [mem 0x00100000-0xcfefffff] could not be reserved april 21 09:04:31 monster kernel: system 00:07: [mem 0xfec00000-0xffffffff] could not be reserved april 21 09:04:31 monster kernel: system 00:07: Plug and Play ACPI device, IDs PNP0c01 (active) april 21 09:04:31 monster kernel: pnp: PnP ACPI: found 8 devices april 21 09:04:31 monster kernel: pci 0000:00:02.0: PCI bridge to [bus 01] april 21 09:04:31 monster kernel: pci 0000:00:02.0: bridge window [io 0xa000-0xafff] april 21 09:04:31 monster kernel: pci 0000:00:02.0: bridge window [mem 0xfe400000-0xfe4fffff] april 21 09:04:31 monster kernel: pci 0000:00:02.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref] april 21 09:04:31 monster kernel: pci 0000:00:05.0: PCI bridge to [bus 02] april 21 09:04:31 monster kernel: pci 0000:00:05.0: bridge window [io 0xb000-0xbfff] april 21 09:04:31 monster kernel: pci 0000:00:05.0: bridge window [mem 0xfe500000-0xfe5fffff] april 21 09:04:31 monster kernel: pci 0000:00:06.0: PCI bridge to [bus 03] april 21 09:04:31 monster kernel: pci 0000:00:06.0: bridge window [io 0xc000-0xcfff] april 21 09:04:31 monster kernel: pci 0000:00:06.0: bridge window [mem 0xfe600000-0xfe6fffff] april 21 09:04:31 monster kernel: pci 0000:00:0a.0: PCI bridge to [bus 04] april 21 09:04:31 monster kernel: pci 0000:00:0a.0: bridge window [mem 0xfe700000-0xfe7fffff] april 21 09:04:31 monster kernel: pci 0000:00:14.4: PCI bridge to [bus 05] april 21 09:04:31 monster kernel: pci 0000:00:15.0: PCI bridge to [bus 06] april 21 09:04:31 monster kernel: pci 0000:00:15.0: bridge window [io 0xd000-0xdfff] april 21 09:04:31 monster kernel: pci 0000:00:15.0: bridge window [mem 0xfe800000-0xfe8fffff] april 21 09:04:31 monster kernel: pci 0000:00:15.1: PCI bridge to [bus 07] april 21 09:04:31 monster kernel: pci 0000:00:15.1: bridge window [io 0xe000-0xefff] april 21 09:04:31 monster kernel: pci 0000:00:15.1: bridge window [mem 0xfe900000-0xfe9fffff] april 21 09:04:31 monster kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7] april 21 09:04:31 monster kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff] april 21 09:04:31 monster kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff] april 21 09:04:31 monster kernel: pci_bus 0000:00: resource 7 [mem 0x000d0000-0x000dffff] april 21 09:04:31 monster kernel: pci_bus 0000:00: resource 8 [mem 0xcff00000-0xdfffffff] april 21 09:04:31 monster kernel: pci_bus 0000:00: resource 9 [mem 0xf0000000-0xfebfffff] april 21 09:04:31 monster kernel: pci_bus 0000:01: resource 0 [io 0xa000-0xafff] april 21 09:04:31 monster kernel: pci_bus 0000:01: resource 1 [mem 0xfe400000-0xfe4fffff] april 21 09:04:31 monster kernel: pci_bus 0000:01: resource 2 [mem 0xd0000000-0xdfffffff 64bit pref] april 21 09:04:31 monster kernel: pci_bus 0000:02: resource 0 [io 0xb000-0xbfff] april 21 09:04:31 monster kernel: pci_bus 0000:02: resource 1 [mem 0xfe500000-0xfe5fffff] april 21 09:04:31 monster kernel: pci_bus 0000:03: resource 0 [io 0xc000-0xcfff] april 21 09:04:31 monster kernel: pci_bus 0000:03: resource 1 [mem 0xfe600000-0xfe6fffff] april 21 09:04:31 monster kernel: pci_bus 0000:04: resource 1 [mem 0xfe700000-0xfe7fffff] april 21 09:04:31 monster kernel: pci_bus 0000:05: resource 4 [io 0x0000-0x0cf7] april 21 09:04:31 monster kernel: pci_bus 0000:05: resource 5 [io 0x0d00-0xffff] april 21 09:04:31 monster kernel: pci_bus 0000:05: resource 6 [mem 0x000a0000-0x000bffff] april 21 09:04:31 monster kernel: pci_bus 0000:05: resource 7 [mem 0x000d0000-0x000dffff] april 21 09:04:31 monster kernel: pci_bus 0000:05: resource 8 [mem 0xcff00000-0xdfffffff] april 21 09:04:31 monster kernel: pci_bus 0000:05: resource 9 [mem 0xf0000000-0xfebfffff] april 21 09:04:31 monster kernel: pci_bus 0000:06: resource 0 [io 0xd000-0xdfff] april 21 09:04:31 monster kernel: pci_bus 0000:06: resource 1 [mem 0xfe800000-0xfe8fffff] april 21 09:04:31 monster kernel: pci_bus 0000:07: resource 0 [io 0xe000-0xefff] april 21 09:04:31 monster kernel: pci_bus 0000:07: resource 1 [mem 0xfe900000-0xfe9fffff] april 21 09:04:31 monster kernel: NET: Registered protocol family 2 april 21 09:04:31 monster kernel: TCP established hash table entries: 131072 (order: 8, 1048576 bytes) april 21 09:04:31 monster kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) april 21 09:04:31 monster kernel: TCP: Hash tables configured (established 131072 bind 65536) april 21 09:04:31 monster kernel: TCP: reno registered april 21 09:04:31 monster kernel: UDP hash table entries: 8192 (order: 6, 262144 bytes) april 21 09:04:31 monster kernel: UDP-Lite hash table entries: 8192 (order: 6, 262144 bytes) april 21 09:04:31 monster kernel: NET: Registered protocol family 1 april 21 09:04:31 monster kernel: pci 0000:01:00.0: Video device with shadowed ROM april 21 09:04:31 monster kernel: PCI: CLS 64 bytes, default 64 april 21 09:04:31 monster kernel: Trying to unpack rootfs image as initramfs... april 21 09:04:31 monster kernel: Freeing initrd memory: 31664K (ffff880034218000 - ffff880036104000) april 21 09:04:31 monster kernel: AMD-Vi: Found IOMMU at 0000:00:00.2 cap 0x40 april 21 09:04:31 monster kernel: AMD-Vi: Lazy IO/TLB flushing enabled april 21 09:04:31 monster kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB) april 21 09:04:31 monster kernel: software IO TLB [mem 0xcbe90000-0xcfe90000] (64MB) mapped at [ffff8800cbe90000-ffff8800cfe8ffff] april 21 09:04:31 monster kernel: microcode: CPU0: patch_level=0x010000c8 april 21 09:04:31 monster kernel: microcode: CPU1: patch_level=0x010000c8 april 21 09:04:31 monster kernel: microcode: CPU2: patch_level=0x010000c8 april 21 09:04:31 monster kernel: microcode: CPU3: patch_level=0x010000c8 april 21 09:04:31 monster kernel: microcode: Microcode Update Driver: v2.00 , Peter Oruba april 21 09:04:31 monster kernel: LVT offset 1 assigned for vector 0x400 april 21 09:04:31 monster kernel: IBS: LVT offset 1 assigned april 21 09:04:31 monster kernel: perf: AMD IBS detected (0x0000001f) april 21 09:04:31 monster kernel: Scanning for low memory corruption every 60 seconds april 21 09:04:31 monster kernel: futex hash table entries: 2048 (order: 5, 131072 bytes) april 21 09:04:31 monster kernel: Initialise system trusted keyring april 21 09:04:31 monster kernel: audit: initializing netlink subsys (disabled) april 21 09:04:31 monster kernel: audit: type=2000 audit(1429599868.104:1): initialized april 21 09:04:31 monster kernel: HugeTLB registered 2 MB page size, pre-allocated 0 pages april 21 09:04:31 monster kernel: zpool: loaded april 21 09:04:31 monster kernel: zbud: loaded april 21 09:04:31 monster kernel: VFS: Disk quotas dquot_6.5.2 april 21 09:04:31 monster kernel: VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) april 21 09:04:31 monster kernel: fuse init (API version 7.23) april 21 09:04:31 monster kernel: Key type big_key registered april 21 09:04:31 monster kernel: Key type asymmetric registered april 21 09:04:31 monster kernel: Asymmetric key parser 'x509' registered april 21 09:04:31 monster kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252) april 21 09:04:31 monster kernel: io scheduler noop registered april 21 09:04:31 monster kernel: io scheduler deadline registered (default) april 21 09:04:31 monster kernel: io scheduler cfq registered april 21 09:04:31 monster kernel: pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt april 21 09:04:31 monster kernel: pci 0000:01:00.0: Signaling PME through PCIe PME interrupt april 21 09:04:31 monster kernel: pci 0000:01:00.1: Signaling PME through PCIe PME interrupt april 21 09:04:31 monster kernel: pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded april 21 09:04:31 monster kernel: pcieport 0000:00:05.0: Signaling PME through PCIe PME interrupt april 21 09:04:31 monster kernel: pci 0000:02:00.0: Signaling PME through PCIe PME interrupt april 21 09:04:31 monster kernel: pci 0000:02:00.1: Signaling PME through PCIe PME interrupt april 21 09:04:31 monster kernel: pcie_pme 0000:00:05.0:pcie01: service driver pcie_pme loaded april 21 09:04:31 monster kernel: pcieport 0000:00:06.0: Signaling PME through PCIe PME interrupt april 21 09:04:31 monster kernel: pci 0000:03:00.0: Signaling PME through PCIe PME interrupt april 21 09:04:31 monster kernel: pci 0000:03:00.1: Signaling PME through PCIe PME interrupt april 21 09:04:31 monster kernel: pcie_pme 0000:00:06.0:pcie01: service driver pcie_pme loaded april 21 09:04:31 monster kernel: pcieport 0000:00:0a.0: Signaling PME through PCIe PME interrupt april 21 09:04:31 monster kernel: pci 0000:04:00.0: Signaling PME through PCIe PME interrupt april 21 09:04:31 monster kernel: pcie_pme 0000:00:0a.0:pcie01: service driver pcie_pme loaded april 21 09:04:31 monster kernel: pcieport 0000:00:15.0: Signaling PME through PCIe PME interrupt april 21 09:04:31 monster kernel: pci 0000:06:00.0: Signaling PME through PCIe PME interrupt april 21 09:04:31 monster kernel: pcie_pme 0000:00:15.0:pcie01: service driver pcie_pme loaded april 21 09:04:31 monster kernel: pcieport 0000:00:15.1: Signaling PME through PCIe PME interrupt april 21 09:04:31 monster kernel: pci 0000:07:00.0: Signaling PME through PCIe PME interrupt april 21 09:04:31 monster kernel: pcie_pme 0000:00:15.1:pcie01: service driver pcie_pme loaded april 21 09:04:31 monster kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5 april 21 09:04:31 monster kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4 april 21 09:04:31 monster kernel: vesafb: mode is 1400x1050x32, linelength=5632, pages=0 april 21 09:04:31 monster kernel: vesafb: scrolling: redraw april 21 09:04:31 monster kernel: vesafb: Truecolor: size=0:8:8:8, shift=0:16:8:0 april 21 09:04:31 monster kernel: vesafb: framebuffer at 0xd0000000, mapped to 0xffffc90011b80000, using 5824k, total 5824k april 21 09:04:31 monster kernel: Console: switching to colour frame buffer device 175x65 april 21 09:04:31 monster kernel: fb0: VESA VGA frame buffer device april 21 09:04:31 monster kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0 april 21 09:04:31 monster kernel: ACPI: Power Button [PWRB] april 21 09:04:31 monster kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1 april 21 09:04:31 monster kernel: ACPI: Power Button [PWRF] april 21 09:04:31 monster kernel: ACPI: processor limited to max C-state 1 april 21 09:04:31 monster kernel: GHES: HEST is not enabled! april 21 09:04:31 monster kernel: Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled april 21 09:04:31 monster kernel: Linux agpgart interface v0.103 april 21 09:04:31 monster kernel: brd: module loaded april 21 09:04:31 monster kernel: loop: module loaded april 21 09:04:31 monster kernel: libphy: Fixed MDIO Bus: probed april 21 09:04:31 monster kernel: tun: Universal TUN/TAP device driver, 1.6 april 21 09:04:31 monster kernel: tun: (C) 1999-2004 Max Krasnyansky april 21 09:04:31 monster kernel: PPP generic driver version 2.4.2 april 21 09:04:31 monster kernel: QUIRK: Enable AMD PLL fix april 21 09:04:31 monster kernel: xhci_hcd 0000:04:00.0: xHCI Host Controller april 21 09:04:31 monster kernel: xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 1 april 21 09:04:31 monster kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 april 21 09:04:31 monster kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 april 21 09:04:31 monster kernel: usb usb1: Product: xHCI Host Controller april 21 09:04:31 monster kernel: usb usb1: Manufacturer: Linux 3.19.0-15-generic xhci-hcd april 21 09:04:31 monster kernel: usb usb1: SerialNumber: 0000:04:00.0 april 21 09:04:31 monster kernel: hub 1-0:1.0: USB hub found april 21 09:04:31 monster kernel: hub 1-0:1.0: 2 ports detected april 21 09:04:31 monster kernel: xhci_hcd 0000:04:00.0: xHCI Host Controller april 21 09:04:31 monster kernel: xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 2 april 21 09:04:31 monster kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0003 april 21 09:04:31 monster kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 april 21 09:04:31 monster kernel: usb usb2: Product: xHCI Host Controller april 21 09:04:31 monster kernel: usb usb2: Manufacturer: Linux 3.19.0-15-generic xhci-hcd april 21 09:04:31 monster kernel: usb usb2: SerialNumber: 0000:04:00.0 april 21 09:04:31 monster kernel: hub 2-0:1.0: USB hub found april 21 09:04:31 monster kernel: hub 2-0:1.0: 2 ports detected april 21 09:04:31 monster kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver april 21 09:04:31 monster kernel: ehci-pci: EHCI PCI platform driver april 21 09:04:31 monster kernel: ehci-pci 0000:00:12.2: EHCI Host Controller april 21 09:04:31 monster kernel: ehci-pci 0000:00:12.2: new USB bus registered, assigned bus number 3 april 21 09:04:31 monster kernel: ehci-pci 0000:00:12.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround april 21 09:04:31 monster kernel: ehci-pci 0000:00:12.2: debug port 1 april 21 09:04:31 monster kernel: ehci-pci 0000:00:12.2: irq 17, io mem 0xfe3ff800 april 21 09:04:31 monster kernel: ehci-pci 0000:00:12.2: USB 2.0 started, EHCI 1.00 april 21 09:04:31 monster kernel: usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 april 21 09:04:31 monster kernel: usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 april 21 09:04:31 monster kernel: usb usb3: Product: EHCI Host Controller april 21 09:04:31 monster kernel: usb usb3: Manufacturer: Linux 3.19.0-15-generic ehci_hcd april 21 09:04:31 monster kernel: usb usb3: SerialNumber: 0000:00:12.2 april 21 09:04:31 monster kernel: hub 3-0:1.0: USB hub found april 21 09:04:31 monster kernel: hub 3-0:1.0: 5 ports detected april 21 09:04:31 monster kernel: ehci-pci 0000:00:13.2: EHCI Host Controller april 21 09:04:31 monster kernel: ehci-pci 0000:00:13.2: new USB bus registered, assigned bus number 4 april 21 09:04:31 monster kernel: ehci-pci 0000:00:13.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround april 21 09:04:31 monster kernel: ehci-pci 0000:00:13.2: debug port 1 april 21 09:04:31 monster kernel: ehci-pci 0000:00:13.2: irq 17, io mem 0xfe3ff400 april 21 09:04:31 monster kernel: ehci-pci 0000:00:13.2: USB 2.0 started, EHCI 1.00 april 21 09:04:31 monster kernel: usb usb4: New USB device found, idVendor=1d6b, idProduct=0002 april 21 09:04:31 monster kernel: usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 april 21 09:04:31 monster kernel: usb usb4: Product: EHCI Host Controller april 21 09:04:31 monster kernel: usb usb4: Manufacturer: Linux 3.19.0-15-generic ehci_hcd april 21 09:04:31 monster kernel: usb usb4: SerialNumber: 0000:00:13.2 april 21 09:04:31 monster kernel: hub 4-0:1.0: USB hub found april 21 09:04:31 monster kernel: hub 4-0:1.0: 5 ports detected april 21 09:04:31 monster kernel: ehci-pci 0000:00:16.2: EHCI Host Controller april 21 09:04:31 monster kernel: ehci-pci 0000:00:16.2: new USB bus registered, assigned bus number 5 april 21 09:04:31 monster kernel: ehci-pci 0000:00:16.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround april 21 09:04:31 monster kernel: ehci-pci 0000:00:16.2: debug port 1 april 21 09:04:31 monster kernel: ehci-pci 0000:00:16.2: irq 17, io mem 0xfe3ff000 april 21 09:04:31 monster kernel: ehci-pci 0000:00:16.2: USB 2.0 started, EHCI 1.00 april 21 09:04:31 monster kernel: usb usb5: New USB device found, idVendor=1d6b, idProduct=0002 april 21 09:04:31 monster kernel: usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 april 21 09:04:31 monster kernel: usb usb5: Product: EHCI Host Controller april 21 09:04:31 monster kernel: usb usb5: Manufacturer: Linux 3.19.0-15-generic ehci_hcd april 21 09:04:31 monster kernel: usb usb5: SerialNumber: 0000:00:16.2 april 21 09:04:31 monster kernel: hub 5-0:1.0: USB hub found april 21 09:04:31 monster kernel: hub 5-0:1.0: 4 ports detected april 21 09:04:31 monster kernel: ehci-platform: EHCI generic platform driver april 21 09:04:31 monster kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver april 21 09:04:31 monster kernel: ohci-pci: OHCI PCI platform driver april 21 09:04:31 monster kernel: ohci-pci 0000:00:12.0: OHCI PCI host controller april 21 09:04:31 monster kernel: ohci-pci 0000:00:12.0: new USB bus registered, assigned bus number 6 april 21 09:04:31 monster kernel: ohci-pci 0000:00:12.0: irq 18, io mem 0xfe3fe000 april 21 09:04:31 monster kernel: usb usb6: New USB device found, idVendor=1d6b, idProduct=0001 april 21 09:04:31 monster kernel: usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1 april 21 09:04:31 monster kernel: usb usb6: Product: OHCI PCI host controller april 21 09:04:31 monster kernel: usb usb6: Manufacturer: Linux 3.19.0-15-generic ohci_hcd april 21 09:04:31 monster kernel: usb usb6: SerialNumber: 0000:00:12.0 april 21 09:04:31 monster kernel: hub 6-0:1.0: USB hub found april 21 09:04:31 monster kernel: hub 6-0:1.0: 5 ports detected april 21 09:04:31 monster kernel: ohci-pci 0000:00:13.0: OHCI PCI host controller april 21 09:04:31 monster kernel: ohci-pci 0000:00:13.0: new USB bus registered, assigned bus number 7 april 21 09:04:31 monster kernel: ohci-pci 0000:00:13.0: irq 18, io mem 0xfe3fd000 april 21 09:04:31 monster kernel: usb usb7: New USB device found, idVendor=1d6b, idProduct=0001 april 21 09:04:31 monster kernel: usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1 april 21 09:04:31 monster kernel: usb usb7: Product: OHCI PCI host controller april 21 09:04:31 monster kernel: usb usb7: Manufacturer: Linux 3.19.0-15-generic ohci_hcd april 21 09:04:31 monster kernel: usb usb7: SerialNumber: 0000:00:13.0 april 21 09:04:31 monster kernel: hub 7-0:1.0: USB hub found april 21 09:04:31 monster kernel: hub 7-0:1.0: 5 ports detected april 21 09:04:31 monster kernel: ohci-pci 0000:00:14.5: OHCI PCI host controller april 21 09:04:31 monster kernel: ohci-pci 0000:00:14.5: new USB bus registered, assigned bus number 8 april 21 09:04:31 monster kernel: ohci-pci 0000:00:14.5: irq 18, io mem 0xfe3fc000 april 21 09:04:31 monster kernel: usb usb8: New USB device found, idVendor=1d6b, idProduct=0001 april 21 09:04:31 monster kernel: usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1 april 21 09:04:31 monster kernel: usb usb8: Product: OHCI PCI host controller april 21 09:04:31 monster kernel: usb usb8: Manufacturer: Linux 3.19.0-15-generic ohci_hcd april 21 09:04:31 monster kernel: usb usb8: SerialNumber: 0000:00:14.5 april 21 09:04:31 monster kernel: hub 8-0:1.0: USB hub found april 21 09:04:31 monster kernel: hub 8-0:1.0: 2 ports detected april 21 09:04:31 monster kernel: ohci-pci 0000:00:16.0: OHCI PCI host controller april 21 09:04:31 monster kernel: ohci-pci 0000:00:16.0: new USB bus registered, assigned bus number 9 april 21 09:04:31 monster kernel: ohci-pci 0000:00:16.0: irq 18, io mem 0xfe3f3000 april 21 09:04:31 monster kernel: usb 5-4: new high-speed USB device number 2 using ehci-pci april 21 09:04:31 monster kernel: usb usb9: New USB device found, idVendor=1d6b, idProduct=0001 april 21 09:04:31 monster kernel: usb usb9: New USB device strings: Mfr=3, Product=2, SerialNumber=1 april 21 09:04:31 monster kernel: usb usb9: Product: OHCI PCI host controller april 21 09:04:31 monster kernel: usb usb9: Manufacturer: Linux 3.19.0-15-generic ohci_hcd april 21 09:04:31 monster kernel: usb usb9: SerialNumber: 0000:00:16.0 april 21 09:04:31 monster kernel: hub 9-0:1.0: USB hub found april 21 09:04:31 monster kernel: hub 9-0:1.0: 4 ports detected april 21 09:04:31 monster kernel: ohci-platform: OHCI generic platform driver april 21 09:04:31 monster kernel: uhci_hcd: USB Universal Host Controller Interface driver april 21 09:04:31 monster kernel: i8042: PNP: No PS/2 controller found. Probing ports directly. april 21 09:04:31 monster kernel: serio: i8042 KBD port at 0x60,0x64 irq 1 april 21 09:04:31 monster kernel: serio: i8042 AUX port at 0x60,0x64 irq 12 april 21 09:04:31 monster kernel: mousedev: PS/2 mouse device common for all mice april 21 09:04:31 monster kernel: rtc_cmos 00:02: RTC can wake from S4 april 21 09:04:31 monster kernel: rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0 april 21 09:04:31 monster kernel: rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs april 21 09:04:31 monster kernel: i2c /dev entries driver april 21 09:04:31 monster kernel: device-mapper: uevent: version 1.0.3 april 21 09:04:31 monster kernel: device-mapper: ioctl: 4.29.0-ioctl (2014-10-28) initialised: dm-devel@redhat.com april 21 09:04:31 monster kernel: usb 6-1: new full-speed USB device number 2 using ohci-pci april 21 09:04:31 monster kernel: ledtrig-cpu: registered to indicate activity on CPUs april 21 09:04:31 monster kernel: PCCT header not found. april 21 09:04:31 monster kernel: usb 5-4: New USB device found, idVendor=0781, idProduct=5567 april 21 09:04:31 monster kernel: usb 5-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 april 21 09:04:31 monster kernel: usb 5-4: Product: Cruzer Blade april 21 09:04:31 monster kernel: usb 5-4: Manufacturer: SanDisk april 21 09:04:31 monster kernel: usb 5-4: SerialNumber: 20042103310C61A11712 april 21 09:04:31 monster kernel: ACPI PCC probe failed. april 21 09:04:31 monster kernel: TCP: cubic registered april 21 09:04:31 monster kernel: NET: Registered protocol family 10 april 21 09:04:31 monster kernel: NET: Registered protocol family 17 april 21 09:04:31 monster kernel: Key type dns_resolver registered april 21 09:04:31 monster kernel: Loading compiled-in X.509 certificates april 21 09:04:31 monster kernel: Loaded X.509 cert 'Magrathea: Glacier signing key: 9e64807092f3a6a8f66f3b7ea4cb3767fdfae08a' april 21 09:04:31 monster kernel: registered taskstats version 1 april 21 09:04:31 monster kernel: Key type trusted registered april 21 09:04:31 monster kernel: Key type encrypted registered april 21 09:04:31 monster kernel: AppArmor: AppArmor sha1 policy hashing enabled april 21 09:04:31 monster kernel: ima: No TPM chip found, activating TPM-bypass! april 21 09:04:31 monster kernel: evm: HMAC attrs: 0x1 april 21 09:04:31 monster kernel: usb 7-2: new full-speed USB device number 2 using ohci-pci april 21 09:04:31 monster kernel: Magic number: 11:817:66 april 21 09:04:31 monster kernel: memory memory94: hash matches april 21 09:04:31 monster kernel: rtc_cmos 00:02: setting system clock to 2015-04-21 07:04:29 UTC (1429599869) april 21 09:04:31 monster kernel: acpi-cpufreq: overriding BIOS provided _PSD data april 21 09:04:31 monster kernel: BIOS EDD facility v0.16 2004-Jun-25, 0 devices found april 21 09:04:31 monster kernel: EDD information not available. april 21 09:04:31 monster kernel: PM: Hibernation image not present or could not be loaded. april 21 09:04:31 monster kernel: Freeing unused kernel memory: 1408K (ffffffff81d36000 - ffffffff81e96000) april 21 09:04:31 monster kernel: Write protecting the kernel read-only data: 12288k april 21 09:04:31 monster kernel: Freeing unused kernel memory: 188K (ffff8800017d1000 - ffff880001800000) april 21 09:04:31 monster kernel: Freeing unused kernel memory: 344K (ffff880001baa000 - ffff880001c00000) april 21 09:04:31 monster kernel: random: systemd-udevd urandom read with 9 bits of entropy available april 21 09:04:31 monster kernel: wmi: Mapper loaded april 21 09:04:31 monster kernel: pata_jmicron 0000:02:00.1: enabling device (0000 -> 0001) april 21 09:04:31 monster kernel: scsi host0: pata_jmicron april 21 09:04:31 monster kernel: scsi host1: pata_jmicron april 21 09:04:31 monster kernel: ahci 0000:00:11.0: version 3.0 april 21 09:04:31 monster kernel: ahci 0000:00:11.0: AHCI 0001.0200 32 slots 6 ports 6 Gbps 0x3f impl SATA mode april 21 09:04:31 monster kernel: ahci 0000:00:11.0: flags: 64bit ncq sntf ilck pm led clo pmp pio slum part april 21 09:04:31 monster kernel: scsi host2: ahci april 21 09:04:31 monster kernel: scsi host3: ahci april 21 09:04:31 monster kernel: scsi host4: ahci april 21 09:04:31 monster kernel: scsi host5: ahci april 21 09:04:31 monster kernel: scsi host6: ahci april 21 09:04:31 monster kernel: scsi host7: ahci april 21 09:04:31 monster kernel: ata3: SATA max UDMA/133 abar m1024@0xfe3ffc00 port 0xfe3ffd00 irq 41 april 21 09:04:31 monster kernel: ata4: SATA max UDMA/133 abar m1024@0xfe3ffc00 port 0xfe3ffd80 irq 41 april 21 09:04:31 monster kernel: ata5: SATA max UDMA/133 abar m1024@0xfe3ffc00 port 0xfe3ffe00 irq 41 april 21 09:04:31 monster kernel: ata6: SATA max UDMA/133 abar m1024@0xfe3ffc00 port 0xfe3ffe80 irq 41 april 21 09:04:31 monster kernel: ata7: SATA max UDMA/133 abar m1024@0xfe3ffc00 port 0xfe3fff00 irq 41 april 21 09:04:31 monster kernel: ata8: SATA max UDMA/133 abar m1024@0xfe3ffc00 port 0xfe3fff80 irq 41 april 21 09:04:31 monster kernel: [drm] Initialized drm 1.1.0 20060810 april 21 09:04:31 monster kernel: usb-storage 5-4:1.0: USB Mass Storage device detected april 21 09:04:31 monster kernel: scsi host8: usb-storage 5-4:1.0 april 21 09:04:31 monster kernel: usbcore: registered new interface driver usb-storage april 21 09:04:31 monster kernel: pps_core: LinuxPPS API ver. 1 registered april 21 09:04:31 monster kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti april 21 09:04:31 monster kernel: usb 6-1: New USB device found, idVendor=0a12, idProduct=0001 april 21 09:04:31 monster kernel: usb 6-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 april 21 09:04:31 monster kernel: ata1: PATA max UDMA/100 cmd 0xbc00 ctl 0xb880 bmdma 0xb400 irq 35 april 21 09:04:31 monster kernel: usbcore: registered new interface driver uas april 21 09:04:31 monster kernel: ata2: PATA max UDMA/100 cmd 0xb800 ctl 0xb480 bmdma 0xb408 irq 35 april 21 09:04:31 monster kernel: pata_jmicron 0000:03:00.1: enabling device (0000 -> 0001) april 21 09:04:31 monster kernel: scsi host9: pata_jmicron april 21 09:04:31 monster kernel: PTP clock support registered april 21 09:04:31 monster kernel: scsi host10: pata_jmicron april 21 09:04:31 monster kernel: ata9: PATA max UDMA/100 cmd 0xcc00 ctl 0xc880 bmdma 0xc400 irq 43 april 21 09:04:31 monster kernel: ata10: PATA max UDMA/100 cmd 0xc800 ctl 0xc480 bmdma 0xc408 irq 43 april 21 09:04:31 monster kernel: ahci 0000:02:00.0: AHCI 0001.0000 32 slots 2 ports 3 Gbps 0x3 impl SATA mode april 21 09:04:31 monster kernel: ahci 0000:02:00.0: flags: 64bit ncq pm led clo pmp pio slum part april 21 09:04:31 monster kernel: scsi host11: ahci april 21 09:04:31 monster kernel: scsi host12: ahci april 21 09:04:31 monster kernel: ata11: SATA max UDMA/133 abar m8192@0xfe5fe000 port 0xfe5fe100 irq 42 april 21 09:04:31 monster kernel: ata12: SATA max UDMA/133 abar m8192@0xfe5fe000 port 0xfe5fe180 irq 42 april 21 09:04:31 monster kernel: ahci 0000:03:00.0: AHCI 0001.0000 32 slots 2 ports 3 Gbps 0x3 impl SATA mode april 21 09:04:31 monster kernel: ahci 0000:03:00.0: flags: 64bit ncq pm led clo pmp pio slum part april 21 09:04:31 monster kernel: scsi host13: ahci april 21 09:04:31 monster kernel: scsi host14: ahci april 21 09:04:31 monster kernel: ata13: SATA max UDMA/133 abar m8192@0xfe6fe000 port 0xfe6fe100 irq 44 april 21 09:04:31 monster kernel: ata14: SATA max UDMA/133 abar m8192@0xfe6fe000 port 0xfe6fe180 irq 44 april 21 09:04:31 monster kernel: tsc: Refined TSC clocksource calibration: 3411.317 MHz april 21 09:04:31 monster kernel: [drm] radeon kernel modesetting enabled. april 21 09:04:31 monster kernel: firewire_ohci 0000:06:00.0: added OHCI v1.10 device as card 0, 4 IR + 8 IT contexts, quirks 0x10 april 21 09:04:31 monster kernel: e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k april 21 09:04:31 monster kernel: e1000e: Copyright(c) 1999 - 2014 Intel Corporation. april 21 09:04:31 monster kernel: AMD IOMMUv2 driver by Joerg Roedel april 21 09:04:31 monster kernel: e1000e 0000:07:00.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode april 21 09:04:31 monster kernel: usb 7-2: New USB device found, idVendor=062a, idProduct=4101 april 21 09:04:31 monster kernel: usb 7-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 april 21 09:04:31 monster kernel: usb 7-2: Product: 2.4G Keyboard Mouse april 21 09:04:31 monster kernel: usb 7-2: Manufacturer: MOSART Semi. april 21 09:04:31 monster kernel: AMD IOMMUv2 functionality not available on this system april 21 09:04:31 monster kernel: CRAT table not found april 21 09:04:31 monster kernel: Finished initializing topology ret=0 april 21 09:04:31 monster kernel: kfd kfd: Initialized module april 21 09:04:31 monster kernel: checking generic (d0000000 5b0000) vs hw (d0000000 10000000) april 21 09:04:31 monster kernel: fb: switching to radeondrmfb from VESA VGA april 21 09:04:31 monster kernel: Console: switching to colour dummy device 80x25 april 21 09:04:31 monster kernel: [drm] initializing kernel modesetting (CEDAR 0x1002:0x68F9 0x1043:0x0374). april 21 09:04:31 monster kernel: [drm] register mmio base: 0xFE4E0000 april 21 09:04:31 monster kernel: [drm] register mmio size: 131072 april 21 09:04:31 monster kernel: ATOM BIOS: 68F9.12.19.0.2.AS02 april 21 09:04:31 monster kernel: radeon 0000:01:00.0: VRAM: 512M 0x0000000000000000 - 0x000000001FFFFFFF (512M used) april 21 09:04:31 monster kernel: radeon 0000:01:00.0: GTT: 1024M 0x0000000020000000 - 0x000000005FFFFFFF april 21 09:04:31 monster kernel: [drm] Detected VRAM RAM=512M, BAR=256M april 21 09:04:31 monster kernel: [drm] RAM width 64bits DDR april 21 09:04:31 monster kernel: [TTM] Zone kernel: Available graphics memory: 8183084 kiB april 21 09:04:31 monster kernel: [TTM] Zone dma32: Available graphics memory: 2097152 kiB april 21 09:04:31 monster kernel: [TTM] Initializing pool allocator april 21 09:04:31 monster kernel: [TTM] Initializing DMA pool allocator april 21 09:04:31 monster kernel: [drm] radeon: 512M of VRAM memory ready april 21 09:04:31 monster kernel: [drm] radeon: 1024M of GTT memory ready. april 21 09:04:31 monster kernel: [drm] Loading CEDAR Microcode april 21 09:04:31 monster kernel: [drm] Internal thermal controller without fan control april 21 09:04:31 monster kernel: [drm] radeon: dpm initialized april 21 09:04:31 monster kernel: [drm] GART: num cpu pages 262144, num gpu pages 262144 april 21 09:04:31 monster kernel: [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 april 21 09:04:31 monster kernel: [drm] PCIE GART of 1024M enabled (table at 0x000000000025E000). april 21 09:04:31 monster kernel: radeon 0000:01:00.0: WB enabled april 21 09:04:31 monster kernel: radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000020000c00 and cpu addr 0xffff88041769cc00 april 21 09:04:31 monster kernel: radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000020000c0c and cpu addr 0xffff88041769cc0c april 21 09:04:31 monster kernel: radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x000000000005c418 and cpu addr 0xffffc9001229c418 april 21 09:04:31 monster kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). april 21 09:04:31 monster kernel: [drm] Driver supports precise vblank timestamp query. april 21 09:04:31 monster kernel: radeon 0000:01:00.0: radeon: MSI limited to 32-bit april 21 09:04:31 monster kernel: radeon 0000:01:00.0: radeon: using MSI. april 21 09:04:31 monster kernel: [drm] radeon: irq initialized. april 21 09:04:31 monster kernel: [drm] ring test on 0 succeeded in 1 usecs april 21 09:04:31 monster kernel: [drm] ring test on 3 succeeded in 3 usecs april 21 09:04:31 monster kernel: e1000e 0000:07:00.0 eth0: registered PHC clock april 21 09:04:31 monster kernel: e1000e 0000:07:00.0 eth0: (PCI Express:2.5GT/s:Width x1) bc:ae:c5:04:b6:f8 april 21 09:04:31 monster kernel: e1000e 0000:07:00.0 eth0: Intel(R) PRO/1000 Network Connection april 21 09:04:31 monster kernel: e1000e 0000:07:00.0 eth0: MAC: 4, PHY: 8, PBA No: FFFFFF-0FF april 21 09:04:31 monster kernel: ata8: SATA link down (SStatus 0 SControl 300) april 21 09:04:31 monster kernel: ata6: SATA link down (SStatus 0 SControl 300) april 21 09:04:31 monster kernel: ata11: SATA link down (SStatus 0 SControl 300) april 21 09:04:31 monster kernel: ata12: SATA link down (SStatus 0 SControl 300) april 21 09:04:31 monster kernel: usb 7-3: new full-speed USB device number 3 using ohci-pci april 21 09:04:31 monster kernel: [drm] ring test on 5 succeeded in 1 usecs april 21 09:04:31 monster kernel: [drm] UVD initialized successfully. april 21 09:04:31 monster kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) april 21 09:04:31 monster kernel: [drm] ib test on ring 0 succeeded in 0 usecs april 21 09:04:31 monster kernel: [drm] ib test on ring 3 succeeded in 0 usecs april 21 09:04:31 monster kernel: ata3.00: ATA-7: SAMSUNG SP2504C, VT100-41, max UDMA7 april 21 09:04:31 monster kernel: ata3.00: 488397168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA april 21 09:04:31 monster kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) april 21 09:04:31 monster kernel: ata3.00: configured for UDMA/133 april 21 09:04:31 monster kernel: scsi 2:0:0:0: Direct-Access ATA SAMSUNG SP2504C 0-41 PQ: 0 ANSI: 5 april 21 09:04:31 monster kernel: sd 2:0:0:0: Attached scsi generic sg0 type 0 april 21 09:04:31 monster kernel: sd 2:0:0:0: [sda] 488397168 512-byte logical blocks: (250 GB/232 GiB) april 21 09:04:31 monster kernel: sd 2:0:0:0: [sda] Write Protect is off april 21 09:04:31 monster kernel: sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00 april 21 09:04:31 monster kernel: sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA april 21 09:04:31 monster kernel: sda: sda1 april 21 09:04:31 monster kernel: sd 2:0:0:0: [sda] Attached SCSI disk april 21 09:04:31 monster kernel: ata4.00: ATA-8: KINGSTON SV300S37A120G, 541ABBF0, max UDMA/133 april 21 09:04:31 monster kernel: ata4.00: 234441648 sectors, multi 1: LBA48 NCQ (depth 31/32), AA april 21 09:04:31 monster kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300) april 21 09:04:31 monster kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) april 21 09:04:31 monster kernel: ata4.00: configured for UDMA/133 april 21 09:04:31 monster kernel: scsi 3:0:0:0: Direct-Access ATA KINGSTON SV300S3 BBF0 PQ: 0 ANSI: 5 april 21 09:04:31 monster kernel: sd 3:0:0:0: Attached scsi generic sg1 type 0 april 21 09:04:31 monster kernel: sd 3:0:0:0: [sdb] 234441648 512-byte logical blocks: (120 GB/111 GiB) april 21 09:04:31 monster kernel: sd 3:0:0:0: [sdb] Write Protect is off april 21 09:04:31 monster kernel: sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00 april 21 09:04:31 monster kernel: sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA april 21 09:04:31 monster kernel: sdb: sdb1 sdb2 april 21 09:04:31 monster kernel: sd 3:0:0:0: [sdb] Attached SCSI disk april 21 09:04:31 monster kernel: ata7.00: ATA-7: SAMSUNG HD753LJ, 1AA01113, max UDMA7 april 21 09:04:31 monster kernel: ata7.00: 1465149168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA april 21 09:04:31 monster kernel: ata7.00: configured for UDMA/133 april 21 09:04:31 monster kernel: ata5.00: ATA-8: KINGSTON SV300S37A120G, 525ABBF0, max UDMA/133 april 21 09:04:31 monster kernel: ata5.00: 234441648 sectors, multi 1: LBA48 NCQ (depth 31/32), AA april 21 09:04:31 monster kernel: ata5.00: configured for UDMA/133 april 21 09:04:31 monster kernel: scsi 4:0:0:0: Direct-Access ATA KINGSTON SV300S3 BBF0 PQ: 0 ANSI: 5 april 21 09:04:31 monster kernel: sd 4:0:0:0: Attached scsi generic sg2 type 0 april 21 09:04:31 monster kernel: sd 4:0:0:0: [sdc] 234441648 512-byte logical blocks: (120 GB/111 GiB) april 21 09:04:31 monster kernel: sd 4:0:0:0: [sdc] Write Protect is off april 21 09:04:31 monster kernel: sd 4:0:0:0: [sdc] Mode Sense: 00 3a 00 00 april 21 09:04:31 monster kernel: sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA april 21 09:04:31 monster kernel: scsi 6:0:0:0: Direct-Access ATA SAMSUNG HD753LJ 1113 PQ: 0 ANSI: 5 april 21 09:04:31 monster kernel: sd 6:0:0:0: [sdd] 1465149168 512-byte logical blocks: (750 GB/698 GiB) april 21 09:04:31 monster kernel: sd 6:0:0:0: Attached scsi generic sg3 type 0 april 21 09:04:31 monster kernel: sd 6:0:0:0: [sdd] Write Protect is off april 21 09:04:31 monster kernel: sd 6:0:0:0: [sdd] Mode Sense: 00 3a 00 00 april 21 09:04:31 monster kernel: sd 6:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA april 21 09:04:31 monster kernel: sdc: sdc1 sdc2 april 21 09:04:31 monster kernel: sd 4:0:0:0: [sdc] Attached SCSI disk april 21 09:04:31 monster kernel: sdd: sdd1 april 21 09:04:31 monster kernel: sd 6:0:0:0: [sdd] Attached SCSI disk april 21 09:04:31 monster kernel: ata13: SATA link up 1.5 Gbps (SStatus 113 SControl 300) april 21 09:04:31 monster kernel: ata14: SATA link up 1.5 Gbps (SStatus 113 SControl 300) april 21 09:04:31 monster kernel: ata14.00: ATAPI: Optiarc DVD RW AD-7260S, 1.03, max UDMA/100 april 21 09:04:31 monster kernel: ata13.00: ATAPI: ATAPI iHBS212 2, 5L01, max UDMA/100 april 21 09:04:31 monster kernel: ata14.00: configured for UDMA/100 april 21 09:04:31 monster kernel: ata13.00: configured for UDMA/100 april 21 09:04:31 monster kernel: usb 7-3: New USB device found, idVendor=1532, idProduct=011b april 21 09:04:31 monster kernel: usb 7-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 april 21 09:04:31 monster kernel: usb 7-3: Product: Razer BlackWidow april 21 09:04:31 monster kernel: usb 7-3: Manufacturer: Razer april 21 09:04:31 monster kernel: hidraw: raw HID events driver (C) Jiri Kosina april 21 09:04:31 monster kernel: usbcore: registered new interface driver usbhid april 21 09:04:31 monster kernel: usbhid: USB HID core driver april 21 09:04:31 monster kernel: input: MOSART Semi. 2.4G Keyboard Mouse as /devices/pci0000:00/0000:00:13.0/usb7/7-2/7-2:1.0/0003:062A:4101.0001/input/input5 april 21 09:04:31 monster kernel: firewire_core 0000:06:00.0: created device fw0: GUID 001fc6000005eddc, S400 april 21 09:04:31 monster kernel: hid-generic 0003:062A:4101.0001: input,hidraw0: USB HID v1.10 Keyboard [MOSART Semi. 2.4G Keyboard Mouse] on usb-0000:00:13.0-2/input0 april 21 09:04:31 monster kernel: input: MOSART Semi. 2.4G Keyboard Mouse as /devices/pci0000:00/0000:00:13.0/usb7/7-2/7-2:1.1/0003:062A:4101.0002/input/input6 april 21 09:04:31 monster kernel: hid-generic 0003:062A:4101.0002: input,hiddev0,hidraw1: USB HID v1.10 Mouse [MOSART Semi. 2.4G Keyboard Mouse] on usb-0000:00:13.0-2/input1 april 21 09:04:31 monster kernel: input: Razer Razer BlackWidow as /devices/pci0000:00/0000:00:13.0/usb7/7-3/7-3:1.0/0003:1532:011B.0003/input/input7 april 21 09:04:31 monster kernel: hid-generic 0003:1532:011B.0003: input,hidraw2: USB HID v1.11 Keyboard [Razer Razer BlackWidow] on usb-0000:00:13.0-3/input0 april 21 09:04:31 monster kernel: input: Razer Razer BlackWidow as /devices/pci0000:00/0000:00:13.0/usb7/7-3/7-3:1.1/0003:1532:011B.0004/input/input8 april 21 09:04:31 monster kernel: hid-generic 0003:1532:011B.0004: input,hidraw3: USB HID v1.11 Keyboard [Razer Razer BlackWidow] on usb-0000:00:13.0-3/input1 april 21 09:04:31 monster kernel: scsi 13:0:0:0: CD-ROM ATAPI iHBS212 2 5L01 PQ: 0 ANSI: 5 april 21 09:04:31 monster kernel: input: Razer Razer BlackWidow as /devices/pci0000:00/0000:00:13.0/usb7/7-3/7-3:1.2/0003:1532:011B.0005/input/input9 april 21 09:04:31 monster kernel: hid-generic 0003:1532:011B.0005: input,hidraw4: USB HID v1.11 Mouse [Razer Razer BlackWidow] on usb-0000:00:13.0-3/input2 april 21 09:04:31 monster kernel: sr 13:0:0:0: [sr0] scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray april 21 09:04:31 monster kernel: cdrom: Uniform CD-ROM driver Revision: 3.20 april 21 09:04:31 monster kernel: sr 13:0:0:0: Attached scsi CD-ROM sr0 april 21 09:04:31 monster kernel: sr 13:0:0:0: Attached scsi generic sg4 type 5 april 21 09:04:31 monster kernel: scsi 14:0:0:0: CD-ROM Optiarc DVD RW AD-7260S 1.03 PQ: 0 ANSI: 5 april 21 09:04:31 monster kernel: sr 14:0:0:0: [sr1] scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray april 21 09:04:31 monster kernel: sr 14:0:0:0: Attached scsi CD-ROM sr1 april 21 09:04:31 monster kernel: sr 14:0:0:0: Attached scsi generic sg5 type 5 april 21 09:04:31 monster kernel: scsi 8:0:0:0: Direct-Access SanDisk Cruzer Blade 1.27 PQ: 0 ANSI: 6 april 21 09:04:31 monster kernel: sd 8:0:0:0: Attached scsi generic sg6 type 0 april 21 09:04:31 monster kernel: sd 8:0:0:0: [sde] 15633408 512-byte logical blocks: (8.00 GB/7.45 GiB) april 21 09:04:31 monster kernel: sd 8:0:0:0: [sde] Write Protect is off april 21 09:04:31 monster kernel: sd 8:0:0:0: [sde] Mode Sense: 43 00 00 00 april 21 09:04:31 monster kernel: sd 8:0:0:0: [sde] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA april 21 09:04:31 monster kernel: sde: sde1 april 21 09:04:31 monster kernel: sd 8:0:0:0: [sde] Attached SCSI removable disk april 21 09:04:31 monster kernel: random: nonblocking pool is initialized april 21 09:04:31 monster kernel: [drm] ib test on ring 5 succeeded april 21 09:04:31 monster kernel: [drm] Radeon Display Connectors april 21 09:04:31 monster kernel: [drm] Connector 0: april 21 09:04:31 monster kernel: [drm] HDMI-A-1 april 21 09:04:31 monster kernel: [drm] HPD1 april 21 09:04:31 monster kernel: [drm] DDC: 0x6440 0x6440 0x6444 0x6444 0x6448 0x6448 0x644c 0x644c april 21 09:04:31 monster kernel: [drm] Encoders: april 21 09:04:31 monster kernel: [drm] DFP1: INTERNAL_UNIPHY1 april 21 09:04:31 monster kernel: [drm] Connector 1: april 21 09:04:31 monster kernel: [drm] DVI-I-1 april 21 09:04:31 monster kernel: [drm] HPD4 april 21 09:04:31 monster kernel: [drm] DDC: 0x6460 0x6460 0x6464 0x6464 0x6468 0x6468 0x646c 0x646c april 21 09:04:31 monster kernel: [drm] Encoders: april 21 09:04:31 monster kernel: [drm] DFP2: INTERNAL_UNIPHY april 21 09:04:31 monster kernel: [drm] CRT1: INTERNAL_KLDSCP_DAC1 april 21 09:04:31 monster kernel: [drm] Connector 2: april 21 09:04:31 monster kernel: [drm] VGA-1 april 21 09:04:31 monster kernel: [drm] DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 0x643c 0x643c april 21 09:04:31 monster kernel: [drm] Encoders: april 21 09:04:31 monster kernel: [drm] CRT2: INTERNAL_KLDSCP_DAC2 april 21 09:04:31 monster kernel: Switched to clocksource tsc april 21 09:04:31 monster kernel: [drm] fb mappable at 0xD045F000 april 21 09:04:31 monster kernel: [drm] vram apper at 0xD0000000 april 21 09:04:31 monster kernel: [drm] size 8294400 april 21 09:04:31 monster kernel: [drm] fb depth is 24 april 21 09:04:31 monster kernel: [drm] pitch is 7680 april 21 09:04:31 monster kernel: fbcon: radeondrmfb (fb0) is primary device april 21 09:04:31 monster kernel: Console: switching to colour frame buffer device 240x67 april 21 09:04:31 monster kernel: radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device april 21 09:04:31 monster kernel: radeon 0000:01:00.0: registered panic notifier april 21 09:04:31 monster kernel: [drm] Initialized radeon 2.40.0 20080528 for 0000:01:00.0 on minor 0 april 21 09:04:31 monster kernel: raid6: sse2x1 4712 MB/s april 21 09:04:31 monster kernel: raid6: sse2x2 6993 MB/s april 21 09:04:31 monster kernel: raid6: sse2x4 8128 MB/s april 21 09:04:31 monster kernel: raid6: using algorithm sse2x4 (8128 MB/s) april 21 09:04:31 monster kernel: raid6: using intx1 recovery algorithm april 21 09:04:31 monster kernel: xor: measuring software checksum speed april 21 09:04:31 monster kernel: prefetch64-sse: 13521.000 MB/sec april 21 09:04:31 monster kernel: generic_sse: 13042.000 MB/sec april 21 09:04:31 monster kernel: xor: using function: prefetch64-sse (13521.000 MB/sec) april 21 09:04:31 monster kernel: Btrfs loaded april 21 09:04:31 monster kernel: EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null) april 21 09:04:31 monster kernel: RPC: Registered named UNIX socket transport module. april 21 09:04:31 monster kernel: RPC: Registered udp transport module. april 21 09:04:31 monster kernel: RPC: Registered tcp transport module. april 21 09:04:31 monster kernel: RPC: Registered tcp NFSv4.1 backchannel transport module. april 21 09:04:31 monster kernel: lp: driver loaded but no devices found april 21 09:04:31 monster kernel: ppdev: user-space parallel port driver april 21 09:04:32 monster kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 april 21 09:04:32 monster kernel: ATK0110 ATK0110:00: EC enabled april 21 09:04:32 monster kernel: ACPI Warning: SystemIO range 0x0000000000000b00-0x0000000000000b07 conflicts with OpRegion 0x0000000000000b00-0x0000000000000b2f (\_SB_.PCI0.SBRG.ASOC.SMRG) (20141107/utaddress-258) april 21 09:04:32 monster kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver april 21 09:04:32 monster kernel: snd_hda_intel 0000:01:00.1: Handle VGA-switcheroo audio client april 21 09:04:32 monster kernel: MCE: In-kernel MCE decoding enabled. april 21 09:04:32 monster kernel: EDAC MC: Ver: 3.0.0 april 21 09:04:32 monster kernel: AMD64 EDAC driver v3.4.0 april 21 09:04:32 monster kernel: EDAC amd64: DRAM ECC disabled. april 21 09:04:32 monster kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. april 21 09:04:32 monster kernel: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:02.0/0000:01:00.1/sound/card1/input10 april 21 09:04:32 monster kernel: sound hdaudioC0D0: autoconfig: line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line april 21 09:04:32 monster kernel: sound hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) april 21 09:04:32 monster kernel: sound hdaudioC0D0: hp_outs=1 (0x1b/0x0/0x0/0x0/0x0) april 21 09:04:32 monster kernel: sound hdaudioC0D0: mono: mono_out=0x0 april 21 09:04:32 monster kernel: sound hdaudioC0D0: dig-out=0x11/0x1e april 21 09:04:32 monster kernel: sound hdaudioC0D0: inputs: april 21 09:04:32 monster kernel: sound hdaudioC0D0: Front Mic=0x19 april 21 09:04:32 monster kernel: sound hdaudioC0D0: Rear Mic=0x18 april 21 09:04:32 monster kernel: sound hdaudioC0D0: Line=0x1a april 21 09:04:32 monster kernel: input: HDA ATI SB Front Mic as /devices/pci0000:00/0000:00:14.2/sound/card0/input11 april 21 09:04:32 monster kernel: input: HDA ATI SB Rear Mic as /devices/pci0000:00/0000:00:14.2/sound/card0/input12 april 21 09:04:32 monster kernel: input: HDA ATI SB Line as /devices/pci0000:00/0000:00:14.2/sound/card0/input13 april 21 09:04:32 monster kernel: input: HDA ATI SB Line Out Front as /devices/pci0000:00/0000:00:14.2/sound/card0/input14 april 21 09:04:32 monster kernel: input: HDA ATI SB Line Out Surround as /devices/pci0000:00/0000:00:14.2/sound/card0/input15 april 21 09:04:32 monster kernel: input: HDA ATI SB Line Out CLFE as /devices/pci0000:00/0000:00:14.2/sound/card0/input16 april 21 09:04:32 monster kernel: input: HDA ATI SB Line Out Side as /devices/pci0000:00/0000:00:14.2/sound/card0/input17 april 21 09:04:32 monster kernel: input: HDA ATI SB Front Headphone as /devices/pci0000:00/0000:00:14.2/sound/card0/input18 april 21 09:04:32 monster kernel: kvm: Nested Virtualization enabled april 21 09:04:32 monster kernel: kvm: Nested Paging enabled april 21 09:04:32 monster kernel: Bluetooth: Core ver 2.20 april 21 09:04:32 monster kernel: NET: Registered protocol family 31 april 21 09:04:32 monster kernel: Bluetooth: HCI device and connection manager initialized april 21 09:04:32 monster kernel: Bluetooth: HCI socket layer initialized april 21 09:04:32 monster kernel: Bluetooth: L2CAP socket layer initialized april 21 09:04:32 monster kernel: Bluetooth: SCO socket layer initialized april 21 09:04:32 monster kernel: usbcore: registered new interface driver btusb april 21 09:04:33 monster kernel: EXT4-fs (sdc1): re-mounted. Opts: errors=remount-ro april 21 09:04:33 monster kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) april 21 09:04:33 monster kernel: EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null) april 21 09:04:33 monster kernel: Adding 4095484k swap on /dev/mapper/cryptswap1. Priority:-1 extents:1 across:4095484k SSFS april 21 09:04:33 monster kernel: audit: type=1400 audit(1429599873.339:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/lightdm/lightdm-guest-session" pid=781 comm="apparmor_parser" april 21 09:04:33 monster kernel: audit: type=1400 audit(1429599873.339:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="chromium" pid=781 comm="apparmor_parser" april 21 09:04:33 monster kernel: audit: type=1400 audit(1429599873.339:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=781 comm="apparmor_parser" april 21 09:04:33 monster kernel: audit: type=1400 audit(1429599873.339:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=781 comm="apparmor_parser" april 21 09:04:33 monster kernel: audit: type=1400 audit(1429599873.339:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=781 comm="apparmor_parser" april 21 09:04:33 monster kernel: audit: type=1400 audit(1429599873.339:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=781 comm="apparmor_parser" april 21 09:04:33 monster kernel: Adding 4881916k swap on /dev/mapper/cryptswap2. Priority:-2 extents:1 across:4881916k SSFS april 21 09:04:33 monster kernel: audit: type=1400 audit(1429599873.355:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/evince" pid=781 comm="apparmor_parser" april 21 09:04:33 monster kernel: audit: type=1400 audit(1429599873.355:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="sanitized_helper" pid=781 comm="apparmor_parser" april 21 09:04:33 monster kernel: audit: type=1400 audit(1429599873.355:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/evince-previewer" pid=781 comm="apparmor_parser" april 21 09:04:33 monster kernel: vboxdrv: module verification failed: signature and/or required key missing - tainting kernel april 21 09:04:33 monster kernel: vboxdrv: Found 4 processor cores. april 21 09:04:33 monster kernel: vboxdrv: fAsync=0 offMin=0x46d offMax=0x1b80 april 21 09:04:33 monster kernel: vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'. april 21 09:04:33 monster kernel: vboxdrv: Successfully loaded version 4.3.26 (interface 0x001a000a). april 21 09:04:33 monster NetworkManager[938]: NetworkManager (version 0.9.10.0) is starting... april 21 09:04:33 monster NetworkManager[938]: Read config: /etc/NetworkManager/NetworkManager.conf april 21 09:04:33 monster NetworkManager[938]: WEXT support is enabled april 21 09:04:33 monster kernel: cfg80211: Calling CRDA to update world regulatory domain april 21 09:04:33 monster kernel: cfg80211: World regulatory domain updated: april 21 09:04:33 monster kernel: cfg80211: DFS Master region: unset april 21 09:04:33 monster kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) april 21 09:04:33 monster kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A) april 21 09:04:33 monster kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A) april 21 09:04:33 monster kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm), (N/A) april 21 09:04:33 monster kernel: cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A) april 21 09:04:33 monster kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A) april 21 09:04:33 monster kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 april 21 09:04:33 monster kernel: Bluetooth: BNEP filters: protocol multicast april 21 09:04:33 monster kernel: Bluetooth: BNEP socket layer initialized april 21 09:04:33 monster NetworkManager[938]: VPN: loaded org.freedesktop.NetworkManager.pptp april 21 09:04:33 monster NetworkManager[938]: DNS: loaded plugin dnsmasq april 21 09:04:33 monster kernel: Bluetooth: RFCOMM TTY layer initialized april 21 09:04:33 monster kernel: Bluetooth: RFCOMM socket layer initialized april 21 09:04:33 monster kernel: Bluetooth: RFCOMM ver 1.11 april 21 09:04:33 monster NetworkManager[938]: init! april 21 09:04:33 monster NetworkManager[938]: update_system_hostname april 21 09:04:33 monster NetworkManager[938]: interface-parser: parsing file /etc/network/interfaces april 21 09:04:33 monster NetworkManager[938]: interface-parser: finished parsing file /etc/network/interfaces april 21 09:04:33 monster NetworkManager[938]: management mode: unmanaged april 21 09:04:33 monster NetworkManager[938]: devices added (path: /sys/devices/pci0000:00/0000:00:15.1/0000:07:00.0/net/eth0, iface: eth0) april 21 09:04:33 monster NetworkManager[938]: device added (path: /sys/devices/pci0000:00/0000:00:15.1/0000:07:00.0/net/eth0, iface: eth0): no ifupdown configuration found. april 21 09:04:33 monster NetworkManager[938]: devices added (path: /sys/devices/virtual/net/lo, iface: lo) april 21 09:04:33 monster NetworkManager[938]: device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found. april 21 09:04:33 monster NetworkManager[938]: end _init. april 21 09:04:33 monster NetworkManager[938]: Loaded plugin ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the NetworkManager mailing list. april 21 09:04:33 monster NetworkManager[938]: Loaded plugin keyfile: (c) 2007 - 2013 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. april 21 09:04:33 monster NetworkManager[938]: SCPlugin-Ofono: Acquired D-Bus service com.canonical.NMOfono april 21 09:04:33 monster NetworkManager[938]: SCPlugin-Ofono: init! april 21 09:04:33 monster NetworkManager[938]: SCPlugin-Ofono: end _init. april 21 09:04:33 monster NetworkManager[938]: Loaded plugin ofono: (C) 2013 Canonical Ltd. To report bugs please use the NetworkManager mailing list. april 21 09:04:33 monster NetworkManager[938]: (9797984) ... get_connections. april 21 09:04:33 monster NetworkManager[938]: (9797984) ... get_connections (managed=false): return empty list. april 21 09:04:33 monster NetworkManager[938]: new connection /etc/NetworkManager/system-connections/virbr0-nic april 21 09:04:33 monster NetworkManager[938]: new connection /etc/NetworkManager/system-connections/vnet0 april 21 09:04:33 monster NetworkManager[938]: new connection /etc/NetworkManager/system-connections/Wired connection 1 april 21 09:04:33 monster NetworkManager[938]: SCPlugin-Ofono: (9610768) ... get_connections. april 21 09:04:33 monster NetworkManager[938]: SCPlugin-Ofono: (9610768) connections count: 0 april 21 09:04:33 monster NetworkManager[938]: get unmanaged devices count: 0 april 21 09:04:33 monster kernel: vboxpci: IOMMU found april 21 09:04:33 monster NetworkManager[938]: monitoring kernel firmware directory '/lib/firmware'. april 21 09:04:33 monster NetworkManager[938]: monitoring ifupdown state file '/run/network/ifstate'. april 21 09:04:33 monster NetworkManager[938]: Loaded device plugin: /usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so april 21 09:04:33 monster NetworkManager[938]: Loaded device plugin: /usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wifi.so april 21 09:04:33 monster NetworkManager[938]: ofono is now available april 21 09:04:33 monster NetworkManager[938]: Loaded device plugin: /usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wwan.so april 21 09:04:33 monster NetworkManager[938]: Loaded device plugin: /usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-adsl.so april 21 09:04:33 monster NetworkManager[938]: WiFi enabled by radio killswitch; enabled by state file april 21 09:04:33 monster NetworkManager[938]: WWAN enabled by radio killswitch; enabled by state file april 21 09:04:33 monster NetworkManager[938]: WiMAX enabled by radio killswitch; enabled by state file april 21 09:04:33 monster NetworkManager[938]: Networking is enabled by state file april 21 09:04:33 monster NetworkManager[938]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed april 21 09:04:33 monster NetworkManager[938]: (lo): link connected april 21 09:04:33 monster NetworkManager[938]: (lo): carrier is ON april 21 09:04:33 monster NetworkManager[938]: (lo): new Generic device (driver: 'unknown' ifindex: 1) april 21 09:04:33 monster NetworkManager[938]: (lo): exported as /org/freedesktop/NetworkManager/Devices/0 april 21 09:04:33 monster NetworkManager[938]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed april 21 09:04:33 monster NetworkManager[938]: (eth0): carrier is OFF april 21 09:04:33 monster NetworkManager[938]: (eth0): new Ethernet device (driver: 'e1000e' ifindex: 2) april 21 09:04:33 monster NetworkManager[938]: (eth0): exported as /org/freedesktop/NetworkManager/Devices/1 april 21 09:04:33 monster NetworkManager[938]: (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] april 21 09:04:34 monster NetworkManager[938]: (eth0): preparing device april 21 09:04:34 monster NetworkManager[938]: urfkill disappeared from the bus april 21 09:04:34 monster NetworkManager[938]: ofono is now available april 21 09:04:34 monster NetworkManager[938]: use BlueZ version 4 april 21 09:04:36 monster kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx april 21 09:04:39 monster NetworkManager[938]: could not mark modem as powered: org.ofono.Error.Failed Operation failed april 21 09:04:39 monster NetworkManager[938]: (hfp/001060D1E09F_980D2EB43501): failed to look up interface index april 21 09:04:39 monster NetworkManager[938]: (hfp/001060D1E09F_980D2EB43501): new Broadband device (driver: 'unknown' ifindex: 0) april 21 09:04:39 monster NetworkManager[938]: (hfp/001060D1E09F_980D2EB43501): exported as /org/freedesktop/NetworkManager/Devices/2 april 21 09:04:39 monster NetworkManager[938]: (hfp/001060D1E09F_980D2EB43501): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] april 21 09:04:39 monster NetworkManager[938]: [1429599879.193004] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 21 09:04:39 monster NetworkManager[938]: [1429599879.193034] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 21 09:04:39 monster NetworkManager[938]: [1429599879.193047] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 21 09:04:39 monster NetworkManager[938]: [1429599879.193058] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 21 09:04:39 monster NetworkManager[938]: [1429599879.193069] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 21 09:04:39 monster NetworkManager[938]: [1429599879.193081] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 21 09:04:39 monster NetworkManager[938]: [1429599879.193092] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 21 09:04:39 monster NetworkManager[938]: [1429599879.193103] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 21 09:04:39 monster NetworkManager[938]: [1429599879.193112] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 21 09:04:39 monster NetworkManager[938]: [1429599879.193121] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 21 09:04:39 monster NetworkManager[938]: [1429599879.193129] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 21 09:04:39 monster NetworkManager[938]: [1429599879.193223] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 21 09:04:39 monster NetworkManager[938]: (hfp/001060D1E09F_980D2EB43501): preparing device april 21 09:04:39 monster NetworkManager[938]: [1429599879.194917] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 21 09:04:39 monster NetworkManager[938]: [1429599879.194935] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 21 09:04:39 monster NetworkManager[938]: [1429599879.194945] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 21 09:04:39 monster NetworkManager[938]: (hfp/001060D1E09F_980D2EB43501): modem state 'initializing' april 21 09:04:39 monster NetworkManager[938]: (eth0): link connected april 21 09:04:44 monster NetworkManager[938]: could not mark modem as powered: org.ofono.Error.Failed Operation failed april 21 09:04:44 monster NetworkManager[938]: modem with path /hfp/001060D1E09F_980D2EB43501 already exists, ignoring april 21 09:04:44 monster NetworkManager[938]: WiFi hardware radio set enabled april 21 09:04:44 monster NetworkManager[938]: WWAN hardware radio set enabled april 21 09:04:44 monster NetworkManager[938]: (/hfp/001060D1E09F_980D2EB43501) modem is now Offline april 21 09:04:44 monster NetworkManager[938]: (/hfp/001060D1E09F_980D2EB43501) updated available interfaces april 21 09:04:44 monster NetworkManager[938]: (eth0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40] april 21 09:04:44 monster NetworkManager[938]: Auto-activating connection 'Wired connection 1'. april 21 09:04:44 monster NetworkManager[938]: Activation (eth0) starting connection 'Wired connection 1' april 21 09:04:44 monster NetworkManager[938]: Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... april 21 09:04:44 monster NetworkManager[938]: Activation (eth0) Stage 1 of 5 (Device Prepare) started... april 21 09:04:44 monster NetworkManager[938]: (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0] april 21 09:04:44 monster NetworkManager[938]: NetworkManager state is now CONNECTING april 21 09:04:44 monster NetworkManager[938]: Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... april 21 09:04:44 monster NetworkManager[938]: Activation (eth0) Stage 1 of 5 (Device Prepare) complete. april 21 09:04:44 monster NetworkManager[938]: Activation (eth0) Stage 2 of 5 (Device Configure) starting... april 21 09:04:44 monster NetworkManager[938]: (eth0): device state change: prepare -> config (reason 'none') [40 50 0] april 21 09:04:44 monster NetworkManager[938]: Activation (eth0) Stage 2 of 5 (Device Configure) successful. april 21 09:04:44 monster NetworkManager[938]: Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. april 21 09:04:44 monster NetworkManager[938]: Activation (eth0) Stage 2 of 5 (Device Configure) complete. april 21 09:04:44 monster NetworkManager[938]: Activation (eth0) Stage 3 of 5 (IP Configure Start) started... april 21 09:04:44 monster NetworkManager[938]: (eth0): device state change: config -> ip-config (reason 'none') [50 70 0] april 21 09:04:44 monster NetworkManager[938]: Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds) april 21 09:04:44 monster NetworkManager[938]: dhclient started with pid 1113 april 21 09:04:44 monster NetworkManager[938]: Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. april 21 09:04:44 monster NetworkManager[938]: BT device HTC Desire 500 (98:0D:2E:B4:35:01) added (NAP) april 21 09:04:44 monster NetworkManager[938]: (98:0D:2E:B4:35:01): new Bluetooth device (driver: 'bluez' ifindex: 0) april 21 09:04:44 monster NetworkManager[938]: (98:0D:2E:B4:35:01): exported as /org/freedesktop/NetworkManager/Devices/3 april 21 09:04:44 monster NetworkManager[938]: (98:0D:2E:B4:35:01): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] april 21 09:04:44 monster NetworkManager[938]: (98:0D:2E:B4:35:01): preparing device april 21 09:04:44 monster NetworkManager[938]: ModemManager available in the bus april 21 09:04:44 monster NetworkManager[938]: (98:0D:2E:B4:35:01): device state change: unavailable -> disconnected (reason 'none') [20 30 0] april 21 09:04:44 monster NetworkManager[938]: (eth0): DHCPv4 state changed nbi -> preinit april 21 09:04:44 monster dhclient[1113]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 (xid=0x41c900b9) april 21 09:04:44 monster dhclient[1113]: DHCPREQUEST of 192.168.0.105 on eth0 to 255.255.255.255 port 67 (xid=0x41c900b9) april 21 09:04:44 monster dhclient[1113]: DHCPOFFER of 192.168.0.105 from 192.168.0.1 april 21 09:04:44 monster dhclient[1113]: DHCPACK of 192.168.0.105 from 192.168.0.1 april 21 09:04:44 monster NetworkManager[938]: (eth0): DHCPv4 state changed preinit -> bound april 21 09:04:44 monster NetworkManager[938]: address 192.168.0.105 april 21 09:04:44 monster NetworkManager[938]: plen 24 (255.255.255.0) april 21 09:04:44 monster NetworkManager[938]: gateway 192.168.0.1 april 21 09:04:44 monster NetworkManager[938]: server identifier 192.168.0.1 april 21 09:04:44 monster NetworkManager[938]: lease time 43200 april 21 09:04:44 monster NetworkManager[938]: hostname 'monster' april 21 09:04:44 monster NetworkManager[938]: nameserver '192.168.0.1' april 21 09:04:44 monster NetworkManager[938]: domain name 'lan' april 21 09:04:44 monster NetworkManager[938]: Activation (eth0) Stage 5 of 5 (IPv4 Configure Commit) scheduled... april 21 09:04:44 monster NetworkManager[938]: Activation (eth0) Stage 5 of 5 (IPv4 Commit) started... april 21 09:04:44 monster NetworkManager[938]: (eth0): device state change: ip-config -> ip-check (reason 'none') [70 80 0] april 21 09:04:44 monster NetworkManager[938]: Activation (eth0) Stage 5 of 5 (IPv4 Commit) complete. april 21 09:04:44 monster NetworkManager[938]: (eth0): device state change: ip-check -> secondaries (reason 'none') [80 90 0] april 21 09:04:44 monster NetworkManager[938]: (eth0): device state change: secondaries -> activated (reason 'none') [90 100 0] april 21 09:04:44 monster NetworkManager[938]: NetworkManager state is now CONNECTED_LOCAL april 21 09:04:44 monster dhclient[1113]: bound to 192.168.0.105 -- renewal in 16203 seconds. april 21 09:04:44 monster NetworkManager[938]: NetworkManager state is now CONNECTED_GLOBAL april 21 09:04:44 monster NetworkManager[938]: Policy set 'Wired connection 1' (eth0) as default for IPv4 routing and DNS. april 21 09:04:44 monster NetworkManager[938]: DNS: starting dnsmasq... april 21 09:04:44 monster NetworkManager[938]: dnsmasq not available on the bus, can't update servers. april 21 09:04:44 monster NetworkManager[938]: [1429599884.428635] [dns-manager/nm-dns-dnsmasq.c:398] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name april 21 09:04:44 monster NetworkManager[938]: DNS: plugin dnsmasq update failed april 21 09:04:44 monster NetworkManager[938]: Writing DNS information to /sbin/resolvconf april 21 09:04:44 monster NetworkManager[938]: Activation (eth0) successful, device activated. april 21 09:04:44 monster NetworkManager[938]: dnsmasq appeared on DBus: :1.20 april 21 09:04:44 monster NetworkManager[938]: Writing DNS information to /sbin/resolvconf april 21 09:04:49 monster NetworkManager[938]: startup complete april 21 09:04:49 monster kernel: FS-Cache: Loaded april 21 09:04:49 monster kernel: FS-Cache: Netfs 'nfs' registered for caching april 21 09:04:49 monster kernel: NFS: Registering the id_resolver key type april 21 09:04:49 monster kernel: Key type id_resolver registered april 21 09:04:49 monster kernel: Key type id_legacy registered april 21 09:04:50 monster kernel: ip_tables: (C) 2000-2006 Netfilter Core Team april 21 09:04:50 monster kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team april 21 09:04:50 monster kernel: Ebtables v2.0 registered april 21 09:04:50 monster kernel: Netfilter messages via NETLINK v0.30. april 21 09:04:50 monster kernel: device eth0 entered promiscuous mode april 21 09:04:50 monster NetworkManager[938]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed april 21 09:04:50 monster NetworkManager[938]: (virbr0): ignoring bridge not created by NetworkManager april 21 09:04:50 monster kernel: bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this. april 21 09:04:50 monster NetworkManager[938]: devices added (path: /sys/devices/virtual/net/virbr0, iface: virbr0) april 21 09:04:50 monster NetworkManager[938]: device added (path: /sys/devices/virtual/net/virbr0, iface: virbr0): no ifupdown configuration found. april 21 09:04:50 monster NetworkManager[938]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed april 21 09:04:50 monster NetworkManager[938]: (virbr0-nic): carrier is OFF april 21 09:04:50 monster NetworkManager[938]: (virbr0-nic): new Tun device (driver: 'unknown' ifindex: 4) april 21 09:04:50 monster NetworkManager[938]: (virbr0-nic): exported as /org/freedesktop/NetworkManager/Devices/4 april 21 09:04:50 monster NetworkManager[938]: devices added (path: /sys/devices/virtual/net/virbr0-nic, iface: virbr0-nic) april 21 09:04:50 monster NetworkManager[938]: device added (path: /sys/devices/virtual/net/virbr0-nic, iface: virbr0-nic): no ifupdown configuration found. april 21 09:04:50 monster NetworkManager[938]: (virbr0-nic): enslaved to unknown device 3 virbr0 april 21 09:04:50 monster kernel: device virbr0-nic entered promiscuous mode april 21 09:04:50 monster NetworkManager[938]: (virbr0-nic): enslaved to unknown device 3 virbr0 april 21 09:04:50 monster NetworkManager[938]: (virbr0-nic): link connected april 21 09:04:50 monster kernel: nf_conntrack version 0.5.0 (16384 buckets, 65536 max) april 21 09:04:51 monster kernel: virbr0: port 1(virbr0-nic) entered listening state april 21 09:04:51 monster kernel: virbr0: port 1(virbr0-nic) entered listening state april 21 09:04:51 monster NetworkManager[938]: (virbr0-nic): enslaved to unknown device 3 virbr0 april 21 09:04:51 monster NetworkManager[938]: (virbr0-nic): link disconnected april 21 09:04:51 monster kernel: virbr0: port 1(virbr0-nic) entered disabled state april 21 09:05:37 monster ureadahead[349]: ureadahead:kernel: Ignored relative path april 21 09:05:37 monster ureadahead[349]: ureadahead:kernel: Ignored relative path april 21 09:05:37 monster ureadahead[349]: ureadahead:kernel: Ignored relative path april 21 09:14:47 monster NetworkManager[938]: Auto-activating connection 'virbr0-nic'. april 21 09:14:47 monster NetworkManager[938]: Failed to activate 'virbr0-nic': Master connection not found or invalid april 21 09:16:58 monster kernel: usb 9-3: new full-speed USB device number 2 using ohci-pci april 21 09:16:58 monster kernel: usb 9-3: New USB device found, idVendor=046d, idProduct=c52b april 21 09:16:58 monster kernel: usb 9-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 april 21 09:16:58 monster kernel: usb 9-3: Product: USB Receiver april 21 09:16:58 monster kernel: usb 9-3: Manufacturer: Logitech april 21 09:16:58 monster kernel: logitech-djreceiver 0003:046D:C52B.0008: hiddev0,hidraw5: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:16.0-3/input2 april 21 09:16:59 monster kernel: input: Logitech M705 as /devices/pci0000:00/0000:00:16.0/usb9/9-3/9-3:1.2/0003:046D:C52B.0008/0003:046D:101B.0009/input/input19 april 21 09:16:59 monster kernel: logitech-hidpp-device 0003:046D:101B.0009: input,hidraw6: USB HID v1.11 Mouse [Logitech M705] on usb-0000:00:16.0-3:1 april 21 13:34:47 monster dhclient[1113]: DHCPREQUEST of 192.168.0.105 on eth0 to 192.168.0.1 port 67 (xid=0x41c900b9) april 21 13:34:47 monster dhclient[1113]: DHCPACK of 192.168.0.105 from 192.168.0.1 april 21 13:34:47 monster NetworkManager[938]: (eth0): DHCPv4 state changed bound -> renew april 21 13:34:47 monster NetworkManager[938]: address 192.168.0.105 april 21 13:34:47 monster NetworkManager[938]: plen 24 (255.255.255.0) april 21 13:34:47 monster NetworkManager[938]: gateway 192.168.0.1 april 21 13:34:47 monster NetworkManager[938]: server identifier 192.168.0.1 april 21 13:34:47 monster NetworkManager[938]: lease time 43200 april 21 13:34:47 monster NetworkManager[938]: hostname 'monster' april 21 13:34:47 monster NetworkManager[938]: nameserver '192.168.0.1' april 21 13:34:47 monster NetworkManager[938]: domain name 'nillabs.com' april 21 13:34:47 monster NetworkManager[938]: Writing DNS information to /sbin/resolvconf april 21 13:34:47 monster dhclient[1113]: bound to 192.168.0.105 -- renewal in 17269 seconds. april 21 14:24:20 monster kernel: sde: sde1 april 21 18:22:36 monster dhclient[1113]: DHCPREQUEST of 192.168.0.105 on eth0 to 192.168.0.1 port 67 (xid=0x41c900b9) april 21 18:22:36 monster dhclient[1113]: DHCPACK of 192.168.0.105 from 192.168.0.1 april 21 18:22:36 monster NetworkManager[938]: (eth0): DHCPv4 state changed renew -> renew april 21 18:22:36 monster NetworkManager[938]: address 192.168.0.105 april 21 18:22:36 monster NetworkManager[938]: plen 24 (255.255.255.0) april 21 18:22:36 monster NetworkManager[938]: gateway 192.168.0.1 april 21 18:22:36 monster NetworkManager[938]: server identifier 192.168.0.1 april 21 18:22:36 monster NetworkManager[938]: lease time 43200 april 21 18:22:36 monster NetworkManager[938]: hostname 'monster' april 21 18:22:36 monster NetworkManager[938]: nameserver '192.168.0.1' april 21 18:22:36 monster NetworkManager[938]: domain name 'nillabs.com' april 21 18:22:36 monster dhclient[1113]: bound to 192.168.0.105 -- renewal in 16049 seconds. april 21 18:45:37 monster kernel: show_signal_msg: 54 callbacks suppressed april 21 18:45:37 monster kernel: kactivitymanage[3319]: segfault at 7f192f979cd0 ip 00007f191b994031 sp 00007fffbb8dcf48 error 4 in libQt5Sql.so.5.4.1[7f191b980000+3f000] april 21 18:45:51 monster NetworkManager[938]: Auto-activating connection 'virbr0-nic'. april 21 18:45:51 monster NetworkManager[938]: Failed to activate 'virbr0-nic': Master connection not found or invalid april 21 22:50:05 monster dhclient[1113]: DHCPREQUEST of 192.168.0.105 on eth0 to 192.168.0.1 port 67 (xid=0x41c900b9) april 21 22:50:05 monster dhclient[1113]: DHCPACK of 192.168.0.105 from 192.168.0.1 april 21 22:50:05 monster NetworkManager[938]: (eth0): DHCPv4 state changed renew -> renew april 21 22:50:05 monster NetworkManager[938]: address 192.168.0.105 april 21 22:50:05 monster NetworkManager[938]: plen 24 (255.255.255.0) april 21 22:50:05 monster NetworkManager[938]: gateway 192.168.0.1 april 21 22:50:05 monster NetworkManager[938]: server identifier 192.168.0.1 april 21 22:50:05 monster NetworkManager[938]: lease time 43200 april 21 22:50:05 monster NetworkManager[938]: hostname 'monster' april 21 22:50:05 monster NetworkManager[938]: nameserver '192.168.0.1' april 21 22:50:05 monster NetworkManager[938]: domain name 'nillabs.com' april 21 22:50:05 monster dhclient[1113]: bound to 192.168.0.105 -- renewal in 15723 seconds. april 22 00:39:14 monster kernel: sde: sde1 april 22 03:12:08 monster dhclient[1113]: DHCPREQUEST of 192.168.0.105 on eth0 to 192.168.0.1 port 67 (xid=0x41c900b9) april 22 03:12:08 monster dhclient[1113]: DHCPACK of 192.168.0.105 from 192.168.0.1 april 22 03:12:08 monster NetworkManager[938]: (eth0): DHCPv4 state changed renew -> renew april 22 03:12:08 monster NetworkManager[938]: address 192.168.0.105 april 22 03:12:08 monster NetworkManager[938]: plen 24 (255.255.255.0) april 22 03:12:08 monster NetworkManager[938]: gateway 192.168.0.1 april 22 03:12:08 monster NetworkManager[938]: server identifier 192.168.0.1 april 22 03:12:08 monster NetworkManager[938]: lease time 43200 april 22 03:12:08 monster NetworkManager[938]: hostname 'monster' april 22 03:12:08 monster NetworkManager[938]: nameserver '192.168.0.1' april 22 03:12:08 monster NetworkManager[938]: domain name 'nillabs.com' april 22 03:12:08 monster dhclient[1113]: bound to 192.168.0.105 -- renewal in 18379 seconds. april 22 08:16:52 monster kernel: kactivitymanage[28449]: segfault at 7f0b4010bcd0 ip 00007f0b34a1c031 sp 00007fffbbe3b888 error 4 in libQt5Sql.so.5.4.1[7f0b34a08000+3f000] april 22 08:17:05 monster NetworkManager[938]: Auto-activating connection 'virbr0-nic'. april 22 08:17:05 monster NetworkManager[938]: Failed to activate 'virbr0-nic': Master connection not found or invalid april 22 08:18:27 monster dhclient[1113]: DHCPREQUEST of 192.168.0.105 on eth0 to 192.168.0.1 port 67 (xid=0x41c900b9) april 22 08:18:27 monster dhclient[1113]: DHCPACK of 192.168.0.105 from 192.168.0.1 april 22 08:18:27 monster NetworkManager[938]: (eth0): DHCPv4 state changed renew -> renew april 22 08:18:27 monster NetworkManager[938]: address 192.168.0.105 april 22 08:18:27 monster NetworkManager[938]: plen 24 (255.255.255.0) april 22 08:18:27 monster NetworkManager[938]: gateway 192.168.0.1 april 22 08:18:27 monster NetworkManager[938]: server identifier 192.168.0.1 april 22 08:18:27 monster NetworkManager[938]: lease time 43200 april 22 08:18:27 monster NetworkManager[938]: hostname 'monster' april 22 08:18:27 monster NetworkManager[938]: nameserver '192.168.0.1' april 22 08:18:27 monster NetworkManager[938]: domain name 'nillabs.com' april 22 08:18:27 monster dhclient[1113]: bound to 192.168.0.105 -- renewal in 18695 seconds. april 22 08:19:53 monster NetworkManager[938]: ModemManager disappeared from bus april 22 08:19:53 monster NetworkManager[938]: (hfp/001060D1E09F_980D2EB43501): device state change: unavailable -> unmanaged (reason 'removed') [20 10 36] april 22 08:19:53 monster NetworkManager[938]: (98:0D:2E:B4:35:01): device state change: disconnected -> unmanaged (reason 'removed') [30 10 36] april 22 08:19:53 monster NetworkManager[938]: ModemManager disappeared from bus april 22 08:19:54 monster kernel: device eth0 left promiscuous mode april 22 08:19:54 monster kernel: device eth0 entered promiscuous mode april 22 08:19:58 monster NetworkManager[938]: could not mark modem as powered: (null) Message did not receive a reply (timeout by message bus) april 22 08:19:58 monster NetworkManager[938]: (hfp/001060D1E09F_980D2EB43501): failed to look up interface index april 22 08:19:58 monster NetworkManager[938]: ** (NetworkManager:938): CRITICAL **: dbus_g_error_get_name: assertion 'error->code == DBUS_GERROR_REMOTE_EXCEPTION' failed april 22 08:19:58 monster NetworkManager[938]: (hfp/001060D1E09F_980D2EB43501): new Broadband device (driver: 'unknown' ifindex: 0) april 22 08:19:58 monster NetworkManager[938]: (hfp/001060D1E09F_980D2EB43501): exported as /org/freedesktop/NetworkManager/Devices/5 april 22 08:19:58 monster NetworkManager[938]: (hfp/001060D1E09F_980D2EB43501): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] april 22 08:19:58 monster NetworkManager[938]: [1429683598.627573] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 22 08:19:58 monster NetworkManager[938]: [1429683598.627614] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 22 08:19:58 monster NetworkManager[938]: [1429683598.627631] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 22 08:19:58 monster NetworkManager[938]: [1429683598.627646] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 22 08:19:58 monster NetworkManager[938]: [1429683598.627662] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 22 08:19:58 monster NetworkManager[938]: [1429683598.627677] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 22 08:19:58 monster NetworkManager[938]: [1429683598.627691] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 22 08:19:58 monster NetworkManager[938]: [1429683598.627704] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 22 08:19:58 monster NetworkManager[938]: [1429683598.627715] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 22 08:19:58 monster NetworkManager[938]: [1429683598.627726] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 22 08:19:58 monster NetworkManager[938]: [1429683598.627737] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 22 08:19:58 monster NetworkManager[938]: [1429683598.627813] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 22 08:19:58 monster NetworkManager[938]: (hfp/001060D1E09F_980D2EB43501): preparing device april 22 08:19:58 monster NetworkManager[938]: [1429683598.632733] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 22 08:19:58 monster NetworkManager[938]: [1429683598.632759] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 22 08:19:58 monster NetworkManager[938]: [1429683598.632772] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 22 08:19:58 monster NetworkManager[938]: (hfp/001060D1E09F_980D2EB43501): modem state 'initializing' april 22 08:19:58 monster NetworkManager[938]: could not mark modem as powered: org.freedesktop.DBus.Error.UnknownObject Method "SetProperty" with signature "sv" on interface "org.ofono.Modem" doesn't exist april 22 08:19:58 monster NetworkManager[938]: modem with path /hfp/001060D1E09F_980D2EB43501 already exists, ignoring april 22 08:19:58 monster NetworkManager[938]: ModemManager available in the bus april 22 08:19:58 monster NetworkManager[938]: (hfp/001060D1E09F_980D2EB43501): device state change: unavailable -> unmanaged (reason 'removed') [20 10 36] april 22 08:19:58 monster NetworkManager[938]: ofono disappeared april 22 08:19:58 monster NetworkManager[938]: ofono is now available april 22 08:20:03 monster NetworkManager[938]: could not mark modem as powered: org.ofono.Error.Failed Operation failed april 22 08:20:03 monster NetworkManager[938]: (hfp/001060D1E09F_980D2EB43501): failed to look up interface index april 22 08:20:03 monster NetworkManager[938]: (hfp/001060D1E09F_980D2EB43501): new Broadband device (driver: 'unknown' ifindex: 0) april 22 08:20:03 monster NetworkManager[938]: (hfp/001060D1E09F_980D2EB43501): exported as /org/freedesktop/NetworkManager/Devices/6 april 22 08:20:03 monster NetworkManager[938]: (hfp/001060D1E09F_980D2EB43501): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] april 22 08:20:03 monster NetworkManager[938]: [1429683603.808026] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 22 08:20:03 monster NetworkManager[938]: [1429683603.808070] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 22 08:20:03 monster NetworkManager[938]: [1429683603.808090] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 22 08:20:03 monster NetworkManager[938]: [1429683603.808106] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 22 08:20:03 monster NetworkManager[938]: [1429683603.808122] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 22 08:20:03 monster NetworkManager[938]: [1429683603.808137] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 22 08:20:03 monster NetworkManager[938]: [1429683603.808153] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 22 08:20:03 monster NetworkManager[938]: [1429683603.808168] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 22 08:20:03 monster NetworkManager[938]: [1429683603.808183] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 22 08:20:03 monster NetworkManager[938]: [1429683603.808196] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 22 08:20:03 monster NetworkManager[938]: [1429683603.808581] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 22 08:20:03 monster NetworkManager[938]: [1429683603.809036] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 22 08:20:03 monster NetworkManager[938]: (hfp/001060D1E09F_980D2EB43501): preparing device april 22 08:20:03 monster NetworkManager[938]: [1429683603.813715] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 22 08:20:03 monster NetworkManager[938]: [1429683603.813742] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 22 08:20:03 monster NetworkManager[938]: [1429683603.813757] [NetworkManagerUtils.c:1258] ASSERT_VALID_PATH_COMPONENT(): Failed asserting path component: NULL april 22 08:20:03 monster NetworkManager[938]: (hfp/001060D1E09F_980D2EB43501): modem state 'initializing' april 22 08:20:08 monster NetworkManager[938]: could not mark modem as powered: org.ofono.Error.Failed Operation failed april 22 08:20:08 monster NetworkManager[938]: modem with path /hfp/001060D1E09F_980D2EB43501 already exists, ignoring april 22 08:20:14 monster NetworkManager[938]: could not mark modem as powered: org.ofono.Error.Failed Operation failed april 22 08:20:14 monster NetworkManager[938]: modem with path /hfp/001060D1E09F_980D2EB43501 already exists, ignoring april 22 08:20:19 monster NetworkManager[938]: could not mark modem as powered: org.ofono.Error.Failed Operation failed april 22 08:20:19 monster NetworkManager[938]: modem with path /hfp/001060D1E09F_980D2EB43501 already exists, ignoring april 22 08:20:19 monster NetworkManager[938]: (/hfp/001060D1E09F_980D2EB43501) modem is now Offline april 22 08:20:19 monster NetworkManager[938]: (/hfp/001060D1E09F_980D2EB43501) updated available interfaces april 22 08:20:19 monster NetworkManager[938]: BT device HTC Desire 500 (98:0D:2E:B4:35:01) added (NAP) april 22 08:20:19 monster NetworkManager[938]: (98:0D:2E:B4:35:01): new Bluetooth device (driver: 'bluez' ifindex: 0) april 22 08:20:19 monster NetworkManager[938]: (98:0D:2E:B4:35:01): exported as /org/freedesktop/NetworkManager/Devices/7 april 22 08:20:19 monster NetworkManager[938]: (98:0D:2E:B4:35:01): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] april 22 08:20:19 monster NetworkManager[938]: (98:0D:2E:B4:35:01): preparing device april 22 08:20:19 monster NetworkManager[938]: Auto-activating connection 'virbr0-nic'. april 22 08:20:19 monster NetworkManager[938]: (98:0D:2E:B4:35:01): device state change: unavailable -> disconnected (reason 'none') [20 30 0] april 22 08:20:19 monster NetworkManager[938]: Failed to activate 'virbr0-nic': Master connection not found or invalid april 22 08:25:37 monster kernel: sde: sde1 april 22 09:37:21 monster kernel: sde: sde1 april 22 10:32:26 monster kernel: usb 5-4: USB disconnect, device number 2 april 22 10:32:43 monster kernel: usb 5-4: new high-speed USB device number 4 using ehci-pci april 22 10:32:43 monster kernel: usb 5-4: New USB device found, idVendor=0bb4, idProduct=0f91 april 22 10:32:43 monster kernel: usb 5-4: New USB device strings: Mfr=2, Product=3, SerialNumber=4 april 22 10:32:43 monster kernel: usb 5-4: Product: Android Phone april 22 10:32:43 monster kernel: usb 5-4: Manufacturer: HTC april 22 10:32:43 monster kernel: usb 5-4: SerialNumber: SH39SWE02490 april 22 10:32:43 monster kernel: usb-storage 5-4:1.1: USB Mass Storage device detected april 22 10:32:43 monster kernel: scsi host15: usb-storage 5-4:1.1 april 22 10:32:43 monster kernel: usb 5-4: USB disconnect, device number 4 april 22 10:32:44 monster kernel: usb 5-4: new high-speed USB device number 5 using ehci-pci april 22 10:32:44 monster kernel: usb 5-4: New USB device found, idVendor=0bb4, idProduct=0f91 april 22 10:32:44 monster kernel: usb 5-4: New USB device strings: Mfr=2, Product=3, SerialNumber=4 april 22 10:32:44 monster kernel: usb 5-4: Product: Android Phone april 22 10:32:44 monster kernel: usb 5-4: Manufacturer: HTC april 22 10:32:44 monster kernel: usb 5-4: SerialNumber: SH39SWE02490 april 22 10:36:25 monster kernel: usb 5-4: USB disconnect, device number 5 april 22 13:30:03 monster dhclient[1113]: DHCPREQUEST of 192.168.0.105 on eth0 to 192.168.0.1 port 67 (xid=0x41c900b9) april 22 13:30:03 monster dhclient[1113]: DHCPACK of 192.168.0.105 from 192.168.0.1 april 22 13:30:03 monster NetworkManager[938]: (eth0): DHCPv4 state changed renew -> renew april 22 13:30:03 monster NetworkManager[938]: address 192.168.0.105 april 22 13:30:03 monster NetworkManager[938]: plen 24 (255.255.255.0) april 22 13:30:03 monster NetworkManager[938]: gateway 192.168.0.1 april 22 13:30:03 monster NetworkManager[938]: server identifier 192.168.0.1 april 22 13:30:03 monster NetworkManager[938]: lease time 43200 april 22 13:30:03 monster NetworkManager[938]: hostname 'monster' april 22 13:30:03 monster NetworkManager[938]: nameserver '192.168.0.1' april 22 13:30:03 monster NetworkManager[938]: domain name 'nillabs.com' april 22 13:30:03 monster dhclient[1113]: bound to 192.168.0.105 -- renewal in 17992 seconds. april 22 13:59:25 monster kernel: kactivitymanage[893]: segfault at 7fd2b5ae0cd0 ip 00007fd2ae623031 sp 00007ffc1dd1e1c8 error 4 in libQt5Sql.so.5.4.1[7fd2ae60f000+3f000] april 22 13:59:39 monster NetworkManager[938]: Auto-activating connection 'virbr0-nic'. april 22 13:59:39 monster NetworkManager[938]: Failed to activate 'virbr0-nic': Master connection not found or invalid april 22 17:44:21 monster kernel: input: Razer Razer BlackWidow as /devices/pci0000:00/0000:00:13.0/usb7/7-3/7-3:1.2/0003:1532:011B.000A/input/input20 april 22 17:44:21 monster kernel: hid-generic 0003:1532:011B.000A: input,hidraw4: USB HID v1.11 Mouse [Razer Razer BlackWidow] on usb-0000:00:13.0-3/input2 april 22 18:29:55 monster dhclient[1113]: DHCPREQUEST of 192.168.0.105 on eth0 to 192.168.0.1 port 67 (xid=0x41c900b9) april 22 18:29:55 monster dhclient[1113]: DHCPACK of 192.168.0.105 from 192.168.0.1 april 22 18:29:55 monster NetworkManager[938]: (eth0): DHCPv4 state changed renew -> renew april 22 18:29:55 monster NetworkManager[938]: address 192.168.0.105 april 22 18:29:55 monster NetworkManager[938]: plen 24 (255.255.255.0) april 22 18:29:55 monster NetworkManager[938]: gateway 192.168.0.1 april 22 18:29:55 monster NetworkManager[938]: server identifier 192.168.0.1 april 22 18:29:55 monster NetworkManager[938]: lease time 43200 april 22 18:29:55 monster NetworkManager[938]: hostname 'monster' april 22 18:29:55 monster NetworkManager[938]: nameserver '192.168.0.1' april 22 18:29:55 monster NetworkManager[938]: domain name 'nillabs.com' april 22 18:29:55 monster dhclient[1113]: bound to 192.168.0.105 -- renewal in 16387 seconds. april 22 23:03:02 monster dhclient[1113]: DHCPREQUEST of 192.168.0.105 on eth0 to 192.168.0.1 port 67 (xid=0x41c900b9) april 22 23:03:02 monster dhclient[1113]: DHCPACK of 192.168.0.105 from 192.168.0.1 april 22 23:03:02 monster NetworkManager[938]: (eth0): DHCPv4 state changed renew -> renew april 22 23:03:02 monster NetworkManager[938]: address 192.168.0.105 april 22 23:03:02 monster NetworkManager[938]: plen 24 (255.255.255.0) april 22 23:03:02 monster NetworkManager[938]: gateway 192.168.0.1 april 22 23:03:02 monster NetworkManager[938]: server identifier 192.168.0.1 april 22 23:03:02 monster NetworkManager[938]: lease time 43200 april 22 23:03:02 monster NetworkManager[938]: hostname 'monster' april 22 23:03:02 monster NetworkManager[938]: nameserver '192.168.0.1' april 22 23:03:02 monster NetworkManager[938]: domain name 'nillabs.com' april 22 23:03:02 monster dhclient[1113]: bound to 192.168.0.105 -- renewal in 15661 seconds. april 23 03:24:03 monster dhclient[1113]: DHCPREQUEST of 192.168.0.105 on eth0 to 192.168.0.1 port 67 (xid=0x41c900b9) april 23 03:24:03 monster dhclient[1113]: DHCPACK of 192.168.0.105 from 192.168.0.1 april 23 03:24:03 monster NetworkManager[938]: (eth0): DHCPv4 state changed renew -> renew april 23 03:24:03 monster NetworkManager[938]: address 192.168.0.105 april 23 03:24:03 monster NetworkManager[938]: plen 24 (255.255.255.0) april 23 03:24:03 monster NetworkManager[938]: gateway 192.168.0.1 april 23 03:24:03 monster NetworkManager[938]: server identifier 192.168.0.1 april 23 03:24:03 monster NetworkManager[938]: lease time 43200 april 23 03:24:03 monster NetworkManager[938]: hostname 'monster' april 23 03:24:03 monster NetworkManager[938]: nameserver '192.168.0.1' april 23 03:24:03 monster NetworkManager[938]: domain name 'nillabs.com' april 23 03:24:03 monster dhclient[1113]: bound to 192.168.0.105 -- renewal in 18108 seconds. april 23 08:17:08 monster kernel: audit: type=1400 audit(1429769828.020:29): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=3274 comm="apparmor_parser" april 23 08:17:08 monster kernel: audit: type=1400 audit(1429769828.020:30): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=3274 comm="apparmor_parser" april 23 08:17:08 monster kernel: audit: type=1400 audit(1429769828.024:31): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=3274 comm="apparmor_parser" april 23 08:17:08 monster kernel: audit: type=1400 audit(1429769828.024:32): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=3274 comm="apparmor_parser" april 23 08:25:51 monster dhclient[1113]: DHCPREQUEST of 192.168.0.105 on eth0 to 192.168.0.1 port 67 (xid=0x41c900b9) april 23 08:25:51 monster dhclient[1113]: DHCPACK of 192.168.0.105 from 192.168.0.1 april 23 08:25:51 monster NetworkManager[938]: (eth0): DHCPv4 state changed renew -> renew april 23 08:25:51 monster NetworkManager[938]: address 192.168.0.105 april 23 08:25:51 monster NetworkManager[938]: plen 24 (255.255.255.0) april 23 08:25:51 monster NetworkManager[938]: gateway 192.168.0.1 april 23 08:25:51 monster NetworkManager[938]: server identifier 192.168.0.1 april 23 08:25:51 monster NetworkManager[938]: lease time 43200 april 23 08:25:51 monster NetworkManager[938]: hostname 'monster' april 23 08:25:51 monster NetworkManager[938]: nameserver '192.168.0.1' april 23 08:25:51 monster NetworkManager[938]: domain name 'nillabs.com' april 23 08:25:51 monster dhclient[1113]: bound to 192.168.0.105 -- renewal in 18464 seconds. april 23 11:21:05 monster kernel: usb 5-4: new high-speed USB device number 6 using ehci-pci april 23 11:21:05 monster kernel: usb 5-4: New USB device found, idVendor=0bb4, idProduct=0f91 april 23 11:21:05 monster kernel: usb 5-4: New USB device strings: Mfr=2, Product=3, SerialNumber=4 april 23 11:21:05 monster kernel: usb 5-4: Product: Android Phone april 23 11:21:05 monster kernel: usb 5-4: Manufacturer: HTC april 23 11:21:05 monster kernel: usb 5-4: SerialNumber: SH39SWE02490 april 23 11:21:05 monster kernel: usb-storage 5-4:1.1: USB Mass Storage device detected april 23 11:21:05 monster kernel: scsi host16: usb-storage 5-4:1.1 april 23 11:21:05 monster kernel: usb 5-4: USB disconnect, device number 6 april 23 11:21:06 monster kernel: usb 5-4: new high-speed USB device number 7 using ehci-pci april 23 11:21:06 monster kernel: usb 5-4: New USB device found, idVendor=0bb4, idProduct=0f91 april 23 11:21:06 monster kernel: usb 5-4: New USB device strings: Mfr=2, Product=3, SerialNumber=4 april 23 11:21:06 monster kernel: usb 5-4: Product: Android Phone april 23 11:21:06 monster kernel: usb 5-4: Manufacturer: HTC april 23 11:21:06 monster kernel: usb 5-4: SerialNumber: SH39SWE02490 april 23 11:33:58 monster kernel: SGI XFS with ACLs, security attributes, realtime, no debug enabled april 23 11:33:58 monster kernel: JFS: nTxBlock = 8192, nTxLock = 65536 april 23 11:33:58 monster kernel: ntfs: driver 2.1.31 [Flags: R/O MODULE]. april 23 11:33:58 monster kernel: QNX4 filesystem 0.2.3 registered. april 23 11:34:00 monster kernel: EXT4-fs (dm-2): VFS: Can't find ext4 filesystem april 23 11:34:00 monster kernel: EXT4-fs (dm-2): VFS: Can't find ext4 filesystem april 23 11:34:00 monster kernel: EXT4-fs (dm-2): VFS: Can't find ext4 filesystem april 23 11:34:00 monster kernel: FAT-fs (dm-2): invalid media value (0x00) april 23 11:34:00 monster kernel: FAT-fs (dm-2): Can't find a valid FAT filesystem april 23 11:34:00 monster kernel: XFS (dm-2): Invalid superblock magic number april 23 11:34:00 monster kernel: FAT-fs (dm-2): invalid media value (0x00) april 23 11:34:00 monster kernel: FAT-fs (dm-2): Can't find a valid FAT filesystem april 23 11:34:00 monster kernel: VFS: Can't find a Minix filesystem V1 | V2 | V3 on device dm-2. april 23 11:34:00 monster kernel: hfsplus: unable to find HFS+ superblock april 23 11:34:00 monster kernel: qnx4: no qnx4 filesystem (no root dir). april 23 11:34:00 monster kernel: ufs: You didn't specify the type of your ufs filesystem april 23 11:34:00 monster kernel: ufs: ufs_fill_super(): bad magic number april 23 11:34:00 monster kernel: hfs: can't find a HFS filesystem on dev dm-2