-- Logs begin at So 2016-02-14 00:19:34 CET, end at Mo 2016-02-15 14:31:17 CET. --
Feb 14 00:19:34 linux-ytaf systemd-journal[187]: Runtime journal is using 8.0M (max allowed 394.0M, trying to leave 591.0M free of 3.8G available → current limit 394.0M).
Feb 14 00:19:34 linux-ytaf systemd-journal[187]: Runtime journal is using 8.0M (max allowed 394.0M, trying to leave 591.0M free of 3.8G available → current limit 394.0M).
Feb 14 00:19:34 linux-ytaf kernel: microcode: CPU0 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 00:19:34 linux-ytaf kernel: Initializing cgroup subsys cpuset
Feb 14 00:19:34 linux-ytaf kernel: Initializing cgroup subsys cpu
Feb 14 00:19:34 linux-ytaf kernel: Initializing cgroup subsys cpuacct
Feb 14 00:19:34 linux-ytaf kernel: Linux version 4.1.15-8-default (geeko@buildhost) (gcc version 4.8.5 (SUSE Linux) ) #1 SMP PREEMPT Wed Jan 20 16:41:00 UTC 2016 (0e3b3ab)
Feb 14 00:19:34 linux-ytaf kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.1.15-8-default root=UUID=21024970-7a27-4114-8525-d8dd026f23b6 ro resume=/dev/sdb2 splash=silent quiet showopts
Feb 14 00:19:34 linux-ytaf kernel: e820: BIOS-provided physical RAM map:
Feb 14 00:19:34 linux-ytaf kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Feb 14 00:19:34 linux-ytaf kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
Feb 14 00:19:34 linux-ytaf kernel: BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable
Feb 14 00:19:34 linux-ytaf kernel: BIOS-e820: [mem 0x0000000020000000-0x00000000201fffff] reserved
Feb 14 00:19:34 linux-ytaf kernel: BIOS-e820: [mem 0x0000000020200000-0x000000003fffffff] usable
Feb 14 00:19:34 linux-ytaf kernel: BIOS-e820: [mem 0x0000000040000000-0x00000000401fffff] reserved
Feb 14 00:19:34 linux-ytaf kernel: BIOS-e820: [mem 0x0000000040200000-0x00000000ca38efff] usable
Feb 14 00:19:34 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ca38f000-0x00000000ca5f1fff] reserved
Feb 14 00:19:34 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ca5f2000-0x00000000ca679fff] ACPI NVS
Feb 14 00:19:34 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ca67a000-0x00000000ca93efff] reserved
Feb 14 00:19:34 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ca93f000-0x00000000cab83fff] ACPI NVS
Feb 14 00:19:34 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cab84000-0x00000000cab91fff] ACPI data
Feb 14 00:19:34 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cab92000-0x00000000cabbefff] ACPI NVS
Feb 14 00:19:34 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cabbf000-0x00000000cabc3fff] ACPI data
Feb 14 00:19:34 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cabc4000-0x00000000cac06fff] ACPI NVS
Feb 14 00:19:34 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cac07000-0x00000000caffffff] usable
Feb 14 00:19:34 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cb800000-0x00000000cf9fffff] reserved
Feb 14 00:19:34 linux-ytaf kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Feb 14 00:19:34 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Feb 14 00:19:34 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Feb 14 00:19:34 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Feb 14 00:19:34 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Feb 14 00:19:34 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Feb 14 00:19:34 linux-ytaf kernel: BIOS-e820: [mem 0x0000000100000000-0x000000022f5fffff] usable
Feb 14 00:19:34 linux-ytaf kernel: NX (Execute Disable) protection: active
Feb 14 00:19:34 linux-ytaf kernel: e820: update [mem 0x0c826018-0x0c835c57] usable ==> usable
Feb 14 00:19:34 linux-ytaf kernel: e820: update [mem 0x0c836018-0x0c846057] usable ==> usable
Feb 14 00:19:34 linux-ytaf kernel: e820: update [mem 0x0c847018-0x0c856857] usable ==> usable
Feb 14 00:19:34 linux-ytaf kernel: e820: update [mem 0x0c857018-0x0c85ae57] usable ==> usable
Feb 14 00:19:34 linux-ytaf kernel: extended physical RAM map:
Feb 14 00:19:34 linux-ytaf kernel: reserve setup_data: [mem 0x0000000000000000-0x000000000009efff] usable
Feb 14 00:19:34 linux-ytaf kernel: reserve setup_data: [mem 0x000000000009f000-0x000000000009ffff] reserved
Feb 14 00:19:34 linux-ytaf kernel: reserve setup_data: [mem 0x0000000000100000-0x000000000c826017] usable
Feb 14 00:19:34 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c826018-0x000000000c835c57] usable
Feb 14 00:19:34 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c835c58-0x000000000c836017] usable
Feb 14 00:19:34 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c836018-0x000000000c846057] usable
Feb 14 00:19:34 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c846058-0x000000000c847017] usable
Feb 14 00:19:34 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c847018-0x000000000c856857] usable
Feb 14 00:19:34 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c856858-0x000000000c857017] usable
Feb 14 00:19:34 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c857018-0x000000000c85ae57] usable
Feb 14 00:19:34 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c85ae58-0x000000001fffffff] usable
Feb 14 00:19:34 linux-ytaf kernel: reserve setup_data: [mem 0x0000000020000000-0x00000000201fffff] reserved
Feb 14 00:19:34 linux-ytaf kernel: reserve setup_data: [mem 0x0000000020200000-0x000000003fffffff] usable
Feb 14 00:19:34 linux-ytaf kernel: reserve setup_data: [mem 0x0000000040000000-0x00000000401fffff] reserved
Feb 14 00:19:34 linux-ytaf kernel: reserve setup_data: [mem 0x0000000040200000-0x00000000ca38efff] usable
Feb 14 00:19:34 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ca38f000-0x00000000ca5f1fff] reserved
Feb 14 00:19:34 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ca5f2000-0x00000000ca679fff] ACPI NVS
Feb 14 00:19:34 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ca67a000-0x00000000ca93efff] reserved
Feb 14 00:19:34 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ca93f000-0x00000000cab83fff] ACPI NVS
Feb 14 00:19:34 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cab84000-0x00000000cab91fff] ACPI data
Feb 14 00:19:34 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cab92000-0x00000000cabbefff] ACPI NVS
Feb 14 00:19:34 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cabbf000-0x00000000cabc3fff] ACPI data
Feb 14 00:19:34 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cabc4000-0x00000000cac06fff] ACPI NVS
Feb 14 00:19:34 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cac07000-0x00000000caffffff] usable
Feb 14 00:19:34 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cb800000-0x00000000cf9fffff] reserved
Feb 14 00:19:34 linux-ytaf kernel: reserve setup_data: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Feb 14 00:19:34 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Feb 14 00:19:34 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Feb 14 00:19:34 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Feb 14 00:19:34 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Feb 14 00:19:34 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Feb 14 00:19:34 linux-ytaf kernel: reserve setup_data: [mem 0x0000000100000000-0x000000022f5fffff] usable
Feb 14 00:19:34 linux-ytaf kernel: efi: EFI v2.31 by American Megatrends
Feb 14 00:19:34 linux-ytaf kernel: efi:  ACPI=0xcab84000  ACPI 2.0=0xcab84000  SMBIOS=0xca427e98  MPS=0xfc990 
Feb 14 00:19:34 linux-ytaf kernel: SMBIOS 2.6 present.
Feb 14 00:19:34 linux-ytaf kernel: DMI: System manufacturer System Product Name/MAXIMUS IV GENE-Z/GEN3, BIOS 3603 11/09/2012
Feb 14 00:19:34 linux-ytaf kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Feb 14 00:19:34 linux-ytaf kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Feb 14 00:19:34 linux-ytaf kernel: AGP: No AGP bridge found
Feb 14 00:19:34 linux-ytaf kernel: e820: last_pfn = 0x22f600 max_arch_pfn = 0x400000000
Feb 14 00:19:34 linux-ytaf kernel: MTRR default type: uncachable
Feb 14 00:19:34 linux-ytaf kernel: MTRR fixed ranges enabled:
Feb 14 00:19:34 linux-ytaf kernel:   00000-9FFFF write-back
Feb 14 00:19:34 linux-ytaf kernel:   A0000-BFFFF uncachable
Feb 14 00:19:34 linux-ytaf kernel:   C0000-D3FFF write-protect
Feb 14 00:19:34 linux-ytaf kernel:   D4000-DFFFF uncachable
Feb 14 00:19:34 linux-ytaf kernel:   E0000-E7FFF write-through
Feb 14 00:19:34 linux-ytaf kernel:   E8000-FFFFF write-protect
Feb 14 00:19:34 linux-ytaf kernel: MTRR variable ranges enabled:
Feb 14 00:19:34 linux-ytaf kernel:   0 base 000000000 mask E00000000 write-back
Feb 14 00:19:34 linux-ytaf kernel:   1 base 200000000 mask FE0000000 write-back
Feb 14 00:19:34 linux-ytaf kernel:   2 base 220000000 mask FF0000000 write-back
Feb 14 00:19:34 linux-ytaf kernel:   3 base 0E0000000 mask FE0000000 uncachable
Feb 14 00:19:34 linux-ytaf kernel:   4 base 0D0000000 mask FF0000000 uncachable
Feb 14 00:19:34 linux-ytaf kernel:   5 base 0CC000000 mask FFC000000 uncachable
Feb 14 00:19:34 linux-ytaf kernel:   6 base 0CB800000 mask FFF800000 uncachable
Feb 14 00:19:34 linux-ytaf kernel:   7 base 22F800000 mask FFF800000 uncachable
Feb 14 00:19:34 linux-ytaf kernel:   8 base 22F600000 mask FFFE00000 uncachable
Feb 14 00:19:34 linux-ytaf kernel:   9 disabled
Feb 14 00:19:34 linux-ytaf kernel: PAT configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- UC  
Feb 14 00:19:34 linux-ytaf kernel: e820: update [mem 0xcb800000-0xffffffff] usable ==> reserved
Feb 14 00:19:34 linux-ytaf kernel: e820: last_pfn = 0xcb000 max_arch_pfn = 0x400000000
Feb 14 00:19:34 linux-ytaf kernel: found SMP MP-table at [mem 0x000fcd30-0x000fcd3f] mapped at [ffff8800000fcd30]
Feb 14 00:19:34 linux-ytaf kernel: Scanning 1 areas for low memory corruption
Feb 14 00:19:34 linux-ytaf kernel: Base memory trampoline at [ffff880000097000] 97000 size 24576
Feb 14 00:19:34 linux-ytaf kernel: reserving inaccessible SNB gfx pages
Feb 14 00:19:34 linux-ytaf kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
Feb 14 00:19:34 linux-ytaf kernel:  [mem 0x00000000-0x000fffff] page 4k
Feb 14 00:19:34 linux-ytaf kernel: BRK [0x0e21a000, 0x0e21afff] PGTABLE
Feb 14 00:19:34 linux-ytaf kernel: BRK [0x0e21b000, 0x0e21bfff] PGTABLE
Feb 14 00:19:34 linux-ytaf kernel: BRK [0x0e21c000, 0x0e21cfff] PGTABLE
Feb 14 00:19:34 linux-ytaf kernel: init_memory_mapping: [mem 0x22f400000-0x22f5fffff]
Feb 14 00:19:34 linux-ytaf kernel:  [mem 0x22f400000-0x22f5fffff] page 2M
Feb 14 00:19:34 linux-ytaf kernel: BRK [0x0e21d000, 0x0e21dfff] PGTABLE
Feb 14 00:19:34 linux-ytaf kernel: init_memory_mapping: [mem 0x220000000-0x22f3fffff]
Feb 14 00:19:34 linux-ytaf kernel:  [mem 0x220000000-0x22f3fffff] page 2M
Feb 14 00:19:34 linux-ytaf kernel: init_memory_mapping: [mem 0x200000000-0x21fffffff]
Feb 14 00:19:34 linux-ytaf kernel:  [mem 0x200000000-0x21fffffff] page 2M
Feb 14 00:19:34 linux-ytaf kernel: init_memory_mapping: [mem 0x00100000-0x1fffffff]
Feb 14 00:19:34 linux-ytaf kernel:  [mem 0x00100000-0x001fffff] page 4k
Feb 14 00:19:34 linux-ytaf kernel:  [mem 0x00200000-0x1fffffff] page 2M
Feb 14 00:19:34 linux-ytaf kernel: init_memory_mapping: [mem 0x20200000-0x3fffffff]
Feb 14 00:19:34 linux-ytaf kernel:  [mem 0x20200000-0x3fffffff] page 2M
Feb 14 00:19:34 linux-ytaf kernel: init_memory_mapping: [mem 0x40200000-0xca38efff]
Feb 14 00:19:34 linux-ytaf kernel:  [mem 0x40200000-0xca1fffff] page 2M
Feb 14 00:19:34 linux-ytaf kernel:  [mem 0xca200000-0xca38efff] page 4k
Feb 14 00:19:34 linux-ytaf kernel: BRK [0x0e21e000, 0x0e21efff] PGTABLE
Feb 14 00:19:34 linux-ytaf kernel: BRK [0x0e21f000, 0x0e21ffff] PGTABLE
Feb 14 00:19:34 linux-ytaf kernel: init_memory_mapping: [mem 0xcac07000-0xcaffffff]
Feb 14 00:19:34 linux-ytaf kernel:  [mem 0xcac07000-0xcadfffff] page 4k
Feb 14 00:19:34 linux-ytaf kernel:  [mem 0xcae00000-0xcaffffff] page 2M
Feb 14 00:19:34 linux-ytaf kernel: init_memory_mapping: [mem 0x100000000-0x1ffffffff]
Feb 14 00:19:34 linux-ytaf kernel:  [mem 0x100000000-0x1ffffffff] page 2M
Feb 14 00:19:34 linux-ytaf kernel: RAMDISK: [mem 0x00457000-0x00ffafff]
Feb 14 00:19:34 linux-ytaf kernel: ACPI: Early table checksum verification disabled
Feb 14 00:19:34 linux-ytaf kernel: ACPI: RSDP 0x00000000CAB84000 000024 (v02 ALASKA)
Feb 14 00:19:34 linux-ytaf kernel: ACPI: XSDT 0x00000000CAB84078 000064 (v01 ALASKA A M I    01072009 AMI  00010013)
Feb 14 00:19:34 linux-ytaf kernel: ACPI: FACP 0x00000000CAB8FC78 0000F4 (v04 ALASKA A M I    01072009 AMI  00010013)
Feb 14 00:19:34 linux-ytaf kernel: ACPI: DSDT 0x00000000CAB84170 00BB02 (v02 ALASKA A M I    00000015 INTL 20051117)
Feb 14 00:19:34 linux-ytaf kernel: ACPI: FACS 0x00000000CABBDF80 000040
Feb 14 00:19:34 linux-ytaf kernel: ACPI: APIC 0x00000000CAB8FD70 000092 (v03 ALASKA A M I    01072009 AMI  00010013)
Feb 14 00:19:34 linux-ytaf kernel: ACPI: MCFG 0x00000000CAB8FE08 00003C (v01 ALASKA A M I    01072009 MSFT 00000097)
Feb 14 00:19:34 linux-ytaf kernel: ACPI: HPET 0x00000000CAB8FE48 000038 (v01 ALASKA A M I    01072009 AMI. 00000005)
Feb 14 00:19:34 linux-ytaf kernel: ACPI: SSDT 0x00000000CAB8FE80 00036D (v01 SataRe SataTabl 00001000 INTL 20091112)
Feb 14 00:19:34 linux-ytaf kernel: ACPI: SSDT 0x00000000CAB901F0 0009AA (v01 PmRef  Cpu0Ist  00003000 INTL 20051117)
Feb 14 00:19:34 linux-ytaf kernel: ACPI: SSDT 0x00000000CAB90BA0 000A92 (v01 PmRef  CpuPm    00003000 INTL 20051117)
Feb 14 00:19:34 linux-ytaf kernel: ACPI: BGRT 0x00000000CAB91690 000038 (v00 ALASKA A M I    01072009 AMI  00010013)
Feb 14 00:19:34 linux-ytaf kernel: ACPI: Local APIC address 0xfee00000
Feb 14 00:19:34 linux-ytaf kernel: No NUMA configuration found
Feb 14 00:19:34 linux-ytaf kernel: Faking a node at [mem 0x0000000000000000-0x000000022f5fffff]
Feb 14 00:19:34 linux-ytaf kernel: NODE_DATA(0) allocated [mem 0x22f5e5000-0x22f5f8fff]
Feb 14 00:19:34 linux-ytaf kernel:  [ffffea0000000000-ffffea0008bfffff] PMD -> [ffff880226c00000-ffff88022ebfffff] on node 0
Feb 14 00:19:34 linux-ytaf kernel: Zone ranges:
Feb 14 00:19:34 linux-ytaf kernel:   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
Feb 14 00:19:34 linux-ytaf kernel:   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
Feb 14 00:19:34 linux-ytaf kernel:   Normal   [mem 0x0000000100000000-0x000000022f5fffff]
Feb 14 00:19:34 linux-ytaf kernel: Movable zone start for each node
Feb 14 00:19:34 linux-ytaf kernel: Early memory node ranges
Feb 14 00:19:34 linux-ytaf kernel:   node   0: [mem 0x0000000000001000-0x000000000009efff]
Feb 14 00:19:34 linux-ytaf kernel:   node   0: [mem 0x0000000000100000-0x000000001fffffff]
Feb 14 00:19:34 linux-ytaf kernel:   node   0: [mem 0x0000000020200000-0x000000003fffffff]
Feb 14 00:19:34 linux-ytaf kernel:   node   0: [mem 0x0000000040200000-0x00000000ca38efff]
Feb 14 00:19:34 linux-ytaf kernel:   node   0: [mem 0x00000000cac07000-0x00000000caffffff]
Feb 14 00:19:34 linux-ytaf kernel:   node   0: [mem 0x0000000100000000-0x000000022f5fffff]
Feb 14 00:19:34 linux-ytaf kernel: Initmem setup node 0 [mem 0x0000000000001000-0x000000022f5fffff]
Feb 14 00:19:34 linux-ytaf kernel: On node 0 totalpages: 2070822
Feb 14 00:19:34 linux-ytaf kernel:   DMA zone: 64 pages used for memmap
Feb 14 00:19:34 linux-ytaf kernel:   DMA zone: 3138 pages reserved
Feb 14 00:19:34 linux-ytaf kernel:   DMA zone: 3998 pages, LIFO batch:0
Feb 14 00:19:34 linux-ytaf kernel:   DMA32 zone: 12879 pages used for memmap
Feb 14 00:19:34 linux-ytaf kernel:   DMA32 zone: 824200 pages, LIFO batch:31
Feb 14 00:19:34 linux-ytaf kernel:   Normal zone: 19416 pages used for memmap
Feb 14 00:19:34 linux-ytaf kernel:   Normal zone: 1242624 pages, LIFO batch:31
Feb 14 00:19:34 linux-ytaf kernel: tboot: non-0 tboot_addr but it is not of type E820_RESERVED
Feb 14 00:19:34 linux-ytaf kernel: ACPI: PM-Timer IO Port: 0x408
Feb 14 00:19:34 linux-ytaf kernel: ACPI: Local APIC address 0xfee00000
Feb 14 00:19:34 linux-ytaf kernel: ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
Feb 14 00:19:34 linux-ytaf kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
Feb 14 00:19:34 linux-ytaf kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Feb 14 00:19:34 linux-ytaf kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Feb 14 00:19:34 linux-ytaf kernel: ACPI: IRQ0 used by override.
Feb 14 00:19:34 linux-ytaf kernel: ACPI: IRQ9 used by override.
Feb 14 00:19:34 linux-ytaf kernel: Using ACPI (MADT) for SMP configuration information
Feb 14 00:19:34 linux-ytaf kernel: ACPI: HPET id: 0x8086a701 base: 0xfed00000
Feb 14 00:19:34 linux-ytaf kernel: smpboot: Allowing 8 CPUs, 0 hotplug CPUs
Feb 14 00:19:34 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
Feb 14 00:19:34 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Feb 14 00:19:34 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000fffff]
Feb 14 00:19:34 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c826000-0x0c826fff]
Feb 14 00:19:34 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c835000-0x0c835fff]
Feb 14 00:19:34 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c836000-0x0c836fff]
Feb 14 00:19:34 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c846000-0x0c846fff]
Feb 14 00:19:34 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c847000-0x0c847fff]
Feb 14 00:19:34 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c856000-0x0c856fff]
Feb 14 00:19:34 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c857000-0x0c857fff]
Feb 14 00:19:34 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c85a000-0x0c85afff]
Feb 14 00:19:34 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x20000000-0x201fffff]
Feb 14 00:19:34 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x40000000-0x401fffff]
Feb 14 00:19:34 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xca38f000-0xca5f1fff]
Feb 14 00:19:34 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xca5f2000-0xca679fff]
Feb 14 00:19:34 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xca67a000-0xca93efff]
Feb 14 00:19:34 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xca93f000-0xcab83fff]
Feb 14 00:19:34 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcab84000-0xcab91fff]
Feb 14 00:19:34 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcab92000-0xcabbefff]
Feb 14 00:19:34 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcabbf000-0xcabc3fff]
Feb 14 00:19:34 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcabc4000-0xcac06fff]
Feb 14 00:19:34 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcb000000-0xcb7fffff]
Feb 14 00:19:34 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcb800000-0xcf9fffff]
Feb 14 00:19:34 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcfa00000-0xf7ffffff]
Feb 14 00:19:34 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
Feb 14 00:19:34 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfc000000-0xfebfffff]
Feb 14 00:19:34 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
Feb 14 00:19:34 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfec01000-0xfecfffff]
Feb 14 00:19:34 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed00000-0xfed03fff]
Feb 14 00:19:34 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed04000-0xfed1bfff]
Feb 14 00:19:34 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Feb 14 00:19:34 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed20000-0xfedfffff]
Feb 14 00:19:34 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
Feb 14 00:19:34 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfee01000-0xfeffffff]
Feb 14 00:19:34 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Feb 14 00:19:34 linux-ytaf kernel: e820: [mem 0xcfa00000-0xf7ffffff] available for PCI devices
Feb 14 00:19:34 linux-ytaf kernel: Booting paravirtualized kernel on bare hardware
Feb 14 00:19:34 linux-ytaf kernel: clocksource refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
Feb 14 00:19:34 linux-ytaf kernel: setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:8 nr_node_ids:1
Feb 14 00:19:34 linux-ytaf kernel: PERCPU: Embedded 33 pages/cpu @ffff88022f200000 s97368 r8192 d29608 u262144
Feb 14 00:19:34 linux-ytaf kernel: pcpu-alloc: s97368 r8192 d29608 u262144 alloc=1*2097152
Feb 14 00:19:34 linux-ytaf kernel: pcpu-alloc: [0] 0 1 2 3 4 5 6 7 
Feb 14 00:19:34 linux-ytaf kernel: Built 1 zonelists in Node order, mobility grouping on.  Total pages: 2035325
Feb 14 00:19:34 linux-ytaf kernel: Policy zone: Normal
Feb 14 00:19:34 linux-ytaf kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.1.15-8-default root=UUID=21024970-7a27-4114-8525-d8dd026f23b6 ro resume=/dev/sdb2 splash=silent quiet showopts
Feb 14 00:19:34 linux-ytaf kernel: log_buf_len individual max cpu contribution: 32768 bytes
Feb 14 00:19:34 linux-ytaf kernel: log_buf_len total cpu_extra contributions: 229376 bytes
Feb 14 00:19:34 linux-ytaf kernel: log_buf_len min size: 262144 bytes
Feb 14 00:19:34 linux-ytaf kernel: log_buf_len: 524288 bytes
Feb 14 00:19:34 linux-ytaf kernel: early log buf free: 245492(93%)
Feb 14 00:19:34 linux-ytaf kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
Feb 14 00:19:34 linux-ytaf kernel: xsave: enabled xstate_bv 0x7, cntxt size 0x340 using standard form
Feb 14 00:19:34 linux-ytaf kernel: AGP: Checking aperture...
Feb 14 00:19:34 linux-ytaf kernel: AGP: No AGP bridge found
Feb 14 00:19:34 linux-ytaf kernel: Memory: 7863196K/8283288K available (6547K kernel code, 1084K rwdata, 4848K rodata, 1560K init, 1516K bss, 420092K reserved, 0K cma-reserved)
Feb 14 00:19:34 linux-ytaf kernel: Preemptible hierarchical RCU implementation.
Feb 14 00:19:34 linux-ytaf kernel:         RCU dyntick-idle grace-period acceleration is enabled.
Feb 14 00:19:34 linux-ytaf kernel:         RCU restricting CPUs from NR_CPUS=512 to nr_cpu_ids=8.
Feb 14 00:19:34 linux-ytaf kernel: RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
Feb 14 00:19:34 linux-ytaf kernel: NR_IRQS:33024 nr_irqs:488 16
Feb 14 00:19:34 linux-ytaf kernel:         Offload RCU callbacks from all CPUs
Feb 14 00:19:34 linux-ytaf kernel:         Offload RCU callbacks from CPUs: 0-7.
Feb 14 00:19:34 linux-ytaf kernel: Console: colour dummy device 80x25
Feb 14 00:19:34 linux-ytaf kernel: console [tty0] enabled
Feb 14 00:19:34 linux-ytaf kernel: clocksource hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484882848 ns
Feb 14 00:19:34 linux-ytaf kernel: hpet clockevent registered
Feb 14 00:19:34 linux-ytaf kernel: tsc: Fast TSC calibration using PIT
Feb 14 00:19:34 linux-ytaf kernel: tsc: Detected 3411.084 MHz processor
Feb 14 00:19:34 linux-ytaf kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 6822.16 BogoMIPS (lpj=13644336)
Feb 14 00:19:34 linux-ytaf kernel: pid_max: default: 32768 minimum: 301
Feb 14 00:19:34 linux-ytaf kernel: ACPI: Core revision 20150410
Feb 14 00:19:34 linux-ytaf kernel: ACPI: All ACPI Tables successfully acquired
Feb 14 00:19:34 linux-ytaf kernel: Security Framework initialized
Feb 14 00:19:34 linux-ytaf kernel: AppArmor: AppArmor initialized
Feb 14 00:19:34 linux-ytaf kernel: Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
Feb 14 00:19:34 linux-ytaf kernel: Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
Feb 14 00:19:34 linux-ytaf kernel: Mount-cache hash table entries: 16384 (order: 5, 131072 bytes)
Feb 14 00:19:34 linux-ytaf kernel: Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes)
Feb 14 00:19:34 linux-ytaf kernel: Initializing cgroup subsys blkio
Feb 14 00:19:34 linux-ytaf kernel: Initializing cgroup subsys memory
Feb 14 00:19:34 linux-ytaf kernel: Initializing cgroup subsys devices
Feb 14 00:19:34 linux-ytaf kernel: Initializing cgroup subsys freezer
Feb 14 00:19:34 linux-ytaf kernel: Initializing cgroup subsys net_cls
Feb 14 00:19:34 linux-ytaf kernel: Initializing cgroup subsys perf_event
Feb 14 00:19:34 linux-ytaf kernel: Initializing cgroup subsys net_prio
Feb 14 00:19:34 linux-ytaf kernel: Initializing cgroup subsys hugetlb
Feb 14 00:19:34 linux-ytaf kernel: CPU: Physical Processor ID: 0
Feb 14 00:19:34 linux-ytaf kernel: CPU: Processor Core ID: 0
Feb 14 00:19:34 linux-ytaf kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Feb 14 00:19:34 linux-ytaf kernel: ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Feb 14 00:19:34 linux-ytaf kernel: mce: CPU supports 9 MCE banks
Feb 14 00:19:34 linux-ytaf kernel: CPU0: Thermal monitoring enabled (TM1)
Feb 14 00:19:34 linux-ytaf kernel: process: using mwait in idle threads
Feb 14 00:19:34 linux-ytaf kernel: Last level iTLB entries: 4KB 512, 2MB 8, 4MB 8
Feb 14 00:19:34 linux-ytaf kernel: Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32, 1GB 0
Feb 14 00:19:34 linux-ytaf kernel: Freeing SMP alternatives memory: 24K (ffffffff82097000 - ffffffff8209d000)
Feb 14 00:19:34 linux-ytaf kernel: ftrace: allocating 25000 entries in 98 pages
Feb 14 00:19:34 linux-ytaf kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Feb 14 00:19:34 linux-ytaf kernel: TSC deadline timer enabled
Feb 14 00:19:34 linux-ytaf kernel: smpboot: CPU0: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz (fam: 06, model: 2a, stepping: 07)
Feb 14 00:19:34 linux-ytaf kernel: Performance Events: PEBS fmt1+, 16-deep LBR, SandyBridge events, full-width counters, Intel PMU driver.
Feb 14 00:19:34 linux-ytaf kernel: ... version:                3
Feb 14 00:19:34 linux-ytaf kernel: ... bit width:              48
Feb 14 00:19:34 linux-ytaf kernel: ... generic registers:      4
Feb 14 00:19:34 linux-ytaf kernel: ... value mask:             0000ffffffffffff
Feb 14 00:19:34 linux-ytaf kernel: ... max period:             0000ffffffffffff
Feb 14 00:19:34 linux-ytaf kernel: ... fixed-purpose events:   3
Feb 14 00:19:34 linux-ytaf kernel: ... event mask:             000000070000000f
Feb 14 00:19:34 linux-ytaf kernel: x86: Booting SMP configuration:
Feb 14 00:19:34 linux-ytaf kernel: .... node  #0, CPUs:      #1
Feb 14 00:19:34 linux-ytaf kernel: microcode: CPU1 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 00:19:34 linux-ytaf kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Feb 14 00:19:34 linux-ytaf kernel:  #2
Feb 14 00:19:34 linux-ytaf kernel: microcode: CPU2 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 00:19:34 linux-ytaf kernel:  #3
Feb 14 00:19:34 linux-ytaf kernel: microcode: CPU3 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 00:19:34 linux-ytaf kernel:  #4 #5 #6 #7
Feb 14 00:19:34 linux-ytaf kernel: x86: Booted up 1 node, 8 CPUs
Feb 14 00:19:34 linux-ytaf kernel: smpboot: Total of 8 processors activated (54577.34 BogoMIPS)
Feb 14 00:19:34 linux-ytaf kernel: devtmpfs: initialized
Feb 14 00:19:34 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xca5f2000-0xca679fff] (557056 bytes)
Feb 14 00:19:34 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xca93f000-0xcab83fff] (2379776 bytes)
Feb 14 00:19:34 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xcab92000-0xcabbefff] (184320 bytes)
Feb 14 00:19:34 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xcabc4000-0xcac06fff] (274432 bytes)
Feb 14 00:19:34 linux-ytaf kernel: clocksource jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
Feb 14 00:19:34 linux-ytaf kernel: pinctrl core: initialized pinctrl subsystem
Feb 14 00:19:34 linux-ytaf kernel: RTC time:  0:19:30, date: 02/14/16
Feb 14 00:19:34 linux-ytaf kernel: NET: Registered protocol family 16
Feb 14 00:19:34 linux-ytaf kernel: cpuidle: using governor ladder
Feb 14 00:19:34 linux-ytaf kernel: cpuidle: using governor menu
Feb 14 00:19:34 linux-ytaf kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
Feb 14 00:19:34 linux-ytaf kernel: ACPI: bus type PCI registered
Feb 14 00:19:34 linux-ytaf kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Feb 14 00:19:34 linux-ytaf kernel: PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
Feb 14 00:19:34 linux-ytaf kernel: PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
Feb 14 00:19:34 linux-ytaf kernel: PCI: Using configuration type 1 for base access
Feb 14 00:19:34 linux-ytaf kernel: perf_event_intel: PMU erratum BJ122, BV98, HSD29 worked around, HT is on
Feb 14 00:19:34 linux-ytaf kernel: ACPI: Added _OSI(Module Device)
Feb 14 00:19:34 linux-ytaf kernel: ACPI: Added _OSI(Processor Device)
Feb 14 00:19:34 linux-ytaf kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
Feb 14 00:19:34 linux-ytaf kernel: ACPI: Added _OSI(Processor Aggregator Device)
Feb 14 00:19:34 linux-ytaf kernel: ACPI: Executed 1 blocks of module-level executable AML code
Feb 14 00:19:34 linux-ytaf kernel: ACPI: Dynamic OEM Table Load:
Feb 14 00:19:34 linux-ytaf kernel: ACPI: SSDT 0xFFFF8802257C7000 00083B (v01 PmRef  Cpu0Cst  00003001 INTL 20051117)
Feb 14 00:19:34 linux-ytaf kernel: ACPI: Dynamic OEM Table Load:
Feb 14 00:19:34 linux-ytaf kernel: ACPI: SSDT 0xFFFF8802257C1400 000303 (v01 PmRef  ApIst    00003000 INTL 20051117)
Feb 14 00:19:34 linux-ytaf kernel: ACPI: Dynamic OEM Table Load:
Feb 14 00:19:34 linux-ytaf kernel: ACPI: SSDT 0xFFFF880225774600 000119 (v01 PmRef  ApCst    00003000 INTL 20051117)
Feb 14 00:19:34 linux-ytaf kernel: ACPI : EC: EC started
Feb 14 00:19:34 linux-ytaf kernel: ACPI: Interpreter enabled
Feb 14 00:19:34 linux-ytaf kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20150410/hwxface-580)
Feb 14 00:19:34 linux-ytaf kernel: ACPI: (supports S0 S1 S3 S4 S5)
Feb 14 00:19:34 linux-ytaf kernel: ACPI: Using IOAPIC for interrupt routing
Feb 14 00:19:34 linux-ytaf kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Feb 14 00:19:34 linux-ytaf kernel: ACPI: Power Resource [FN00] (off)
Feb 14 00:19:34 linux-ytaf kernel: ACPI: Power Resource [FN01] (off)
Feb 14 00:19:34 linux-ytaf kernel: ACPI: Power Resource [FN02] (off)
Feb 14 00:19:34 linux-ytaf kernel: ACPI: Power Resource [FN03] (off)
Feb 14 00:19:34 linux-ytaf kernel: ACPI: Power Resource [FN04] (off)
Feb 14 00:19:34 linux-ytaf kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
Feb 14 00:19:34 linux-ytaf kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Feb 14 00:19:34 linux-ytaf kernel: \_SB_.PCI0:_OSC invalid UUID
Feb 14 00:19:34 linux-ytaf kernel: _OSC request data:1 1f 0 
Feb 14 00:19:34 linux-ytaf kernel: acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
Feb 14 00:19:34 linux-ytaf kernel: PCI host bridge to bus 0000:00
Feb 14 00:19:34 linux-ytaf kernel: pci_bus 0000:00: root bus resource [bus 00-3e]
Feb 14 00:19:34 linux-ytaf kernel: pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
Feb 14 00:19:34 linux-ytaf kernel: pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
Feb 14 00:19:34 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
Feb 14 00:19:34 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff window]
Feb 14 00:19:34 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff window]
Feb 14 00:19:34 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff window]
Feb 14 00:19:34 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0xcfa00000-0xfeafffff window]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:00.0: [8086:0100] type 00 class 0x060000
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:01.0: [8086:0101] type 01 class 0x060400
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:01.0: System wakeup disabled by ACPI
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:01.1: [8086:0105] type 01 class 0x060400
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:01.1: PME# supported from D0 D3hot D3cold
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:01.1: System wakeup disabled by ACPI
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:02.0: [8086:0122] type 00 class 0x038000
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:02.0: reg 0x10: [mem 0xf7400000-0xf77fffff 64bit]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:02.0: reg 0x18: [mem 0xd0000000-0xdfffffff 64bit pref]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:02.0: reg 0x20: [io  0xf000-0xf03f]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:16.0: [8086:1c3a] type 00 class 0x078000
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:16.0: reg 0x10: [mem 0xf7b2c000-0xf7b2c00f 64bit]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:19.0: [8086:1503] type 00 class 0x020000
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:19.0: reg 0x10: [mem 0xf7b00000-0xf7b1ffff]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:19.0: reg 0x14: [mem 0xf7b29000-0xf7b29fff]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:19.0: reg 0x18: [io  0xf080-0xf09f]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:19.0: PME# supported from D0 D3hot D3cold
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:19.0: System wakeup disabled by ACPI
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1a.0: [8086:1c2d] type 00 class 0x0c0320
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1a.0: reg 0x10: [mem 0xf7b28000-0xf7b283ff]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1a.0: System wakeup disabled by ACPI
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1b.0: [8086:1c20] type 00 class 0x040300
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1b.0: reg 0x10: [mem 0xf7b20000-0xf7b23fff 64bit]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1b.0: System wakeup disabled by ACPI
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.0: [8086:1c10] type 01 class 0x060400
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.0: System wakeup disabled by ACPI
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.4: [8086:1c18] type 01 class 0x060400
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.4: System wakeup disabled by ACPI
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.5: [8086:1c1a] type 01 class 0x060400
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.5: System wakeup disabled by ACPI
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.6: [8086:1c1c] type 01 class 0x060400
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.6: PME# supported from D0 D3hot D3cold
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.6: System wakeup disabled by ACPI
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1d.0: [8086:1c26] type 00 class 0x0c0320
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1d.0: reg 0x10: [mem 0xf7b27000-0xf7b273ff]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1d.0: System wakeup disabled by ACPI
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1f.0: [8086:1c44] type 00 class 0x060100
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1f.2: [8086:1c02] type 00 class 0x010601
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x10: [io  0xf0d0-0xf0d7]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x14: [io  0xf0c0-0xf0c3]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x18: [io  0xf0b0-0xf0b7]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x1c: [io  0xf0a0-0xf0a3]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x20: [io  0xf060-0xf07f]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x24: [mem 0xf7b26000-0xf7b267ff]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1f.2: PME# supported from D3hot
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1f.3: [8086:1c22] type 00 class 0x0c0500
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1f.3: reg 0x10: [mem 0xf7b25000-0xf7b250ff 64bit]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1f.3: reg 0x20: [io  0x0580-0x059f]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:02:00.0: [10de:1183] type 00 class 0x030000
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:02:00.0: reg 0x10: [mem 0xf6000000-0xf6ffffff]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:02:00.0: reg 0x14: [mem 0xe0000000-0xe7ffffff 64bit pref]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:02:00.0: reg 0x1c: [mem 0xe8000000-0xe9ffffff 64bit pref]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:02:00.0: reg 0x24: [io  0xe000-0xe07f]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:02:00.0: reg 0x30: [mem 0xf7000000-0xf707ffff pref]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:02:00.1: [10de:0e0a] type 00 class 0x040300
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:02:00.1: reg 0x10: [mem 0xf7080000-0xf7083fff]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:01.1: PCI bridge to [bus 02]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [io  0xe000-0xefff]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xf6000000-0xf70fffff]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xe0000000-0xe9ffffff 64bit pref]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.0: PCI bridge to [bus 03]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:04:00.0: [1b21:1042] type 00 class 0x0c0330
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:04:00.0: reg 0x10: [mem 0xf7a00000-0xf7a07fff 64bit]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:04:00.0: PME# supported from D3hot D3cold
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:04:00.0: System wakeup disabled by ACPI
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.4: PCI bridge to [bus 04]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.4:   bridge window [mem 0xf7a00000-0xf7afffff]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:05:00.0: [1b21:1042] type 00 class 0x0c0330
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:05:00.0: reg 0x10: [mem 0xf7900000-0xf7907fff 64bit]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:05:00.0: PME# supported from D3hot D3cold
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:05:00.0: System wakeup disabled by ACPI
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.5: PCI bridge to [bus 05]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.5:   bridge window [mem 0xf7900000-0xf79fffff]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:06:00.0: [197b:2362] type 00 class 0x010185
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:06:00.0: reg 0x10: [io  0xd040-0xd047]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:06:00.0: reg 0x14: [io  0xd030-0xd033]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:06:00.0: reg 0x18: [io  0xd020-0xd027]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:06:00.0: reg 0x1c: [io  0xd010-0xd013]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:06:00.0: reg 0x20: [io  0xd000-0xd00f]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:06:00.0: reg 0x24: [mem 0xf7810000-0xf78101ff]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:06:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:06:00.0: PME# supported from D3hot
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:06:00.0: System wakeup disabled by ACPI
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.6: PCI bridge to [bus 06]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [io  0xd000-0xdfff]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [mem 0xf7800000-0xf78fffff]
Feb 14 00:19:34 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15)
Feb 14 00:19:34 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *10 11 12 14 15)
Feb 14 00:19:34 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Feb 14 00:19:34 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs *3 4 5 6 10 11 12 14 15)
Feb 14 00:19:34 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 *4 5 6 10 11 12 14 15)
Feb 14 00:19:34 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
Feb 14 00:19:34 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 *11 12 14 15)
Feb 14 00:19:34 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 *10 11 12 14 15)
Feb 14 00:19:34 linux-ytaf kernel: ACPI: Enabled 6 GPEs in block 00 to 3F
Feb 14 00:19:34 linux-ytaf kernel: ACPI : EC: GPE = 0x18, I/O: command/status = 0x66, data = 0x62
Feb 14 00:19:34 linux-ytaf kernel: vgaarb: setting as boot device: PCI:0000:02:00.0
Feb 14 00:19:34 linux-ytaf kernel: vgaarb: device added: PCI:0000:02:00.0,decodes=io+mem,owns=io+mem,locks=none
Feb 14 00:19:34 linux-ytaf kernel: vgaarb: loaded
Feb 14 00:19:34 linux-ytaf kernel: vgaarb: bridge control possible 0000:02:00.0
Feb 14 00:19:34 linux-ytaf kernel: SCSI subsystem initialized
Feb 14 00:19:34 linux-ytaf kernel: libata version 3.00 loaded.
Feb 14 00:19:34 linux-ytaf kernel: PCI: Using ACPI for IRQ routing
Feb 14 00:19:34 linux-ytaf kernel: PCI: pci_cache_line_size set to 64 bytes
Feb 14 00:19:34 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0009f000-0x0009ffff]
Feb 14 00:19:34 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c826018-0x0fffffff]
Feb 14 00:19:34 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c836018-0x0fffffff]
Feb 14 00:19:34 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c847018-0x0fffffff]
Feb 14 00:19:34 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c857018-0x0fffffff]
Feb 14 00:19:34 linux-ytaf kernel: e820: reserve RAM buffer [mem 0xca38f000-0xcbffffff]
Feb 14 00:19:34 linux-ytaf kernel: e820: reserve RAM buffer [mem 0xcb000000-0xcbffffff]
Feb 14 00:19:34 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x22f600000-0x22fffffff]
Feb 14 00:19:34 linux-ytaf kernel: NetLabel: Initializing
Feb 14 00:19:34 linux-ytaf kernel: NetLabel:  domain hash size = 128
Feb 14 00:19:34 linux-ytaf kernel: NetLabel:  protocols = UNLABELED CIPSOv4
Feb 14 00:19:34 linux-ytaf kernel: NetLabel:  unlabeled traffic allowed by default
Feb 14 00:19:34 linux-ytaf kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Feb 14 00:19:34 linux-ytaf kernel: hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Feb 14 00:19:34 linux-ytaf kernel: Switched to clocksource hpet
Feb 14 00:19:34 linux-ytaf kernel: AppArmor: AppArmor Filesystem Enabled
Feb 14 00:19:34 linux-ytaf kernel: pnp: PnP ACPI init
Feb 14 00:19:34 linux-ytaf kernel: system 00:00: [mem 0xfed40000-0xfed44fff] has been reserved
Feb 14 00:19:34 linux-ytaf kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
Feb 14 00:19:34 linux-ytaf kernel: system 00:01: [io  0x0680-0x069f] has been reserved
Feb 14 00:19:34 linux-ytaf kernel: system 00:01: [io  0x0200-0x020f] has been reserved
Feb 14 00:19:34 linux-ytaf kernel: system 00:01: [io  0xffff] has been reserved
Feb 14 00:19:34 linux-ytaf kernel: system 00:01: [io  0xffff] has been reserved
Feb 14 00:19:34 linux-ytaf kernel: system 00:01: [io  0x0400-0x0453] could not be reserved
Feb 14 00:19:34 linux-ytaf kernel: system 00:01: [io  0x0458-0x047f] has been reserved
Feb 14 00:19:34 linux-ytaf kernel: system 00:01: [io  0x0500-0x057f] has been reserved
Feb 14 00:19:34 linux-ytaf kernel: system 00:01: [io  0x164e-0x164f] has been reserved
Feb 14 00:19:34 linux-ytaf kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 00:19:34 linux-ytaf kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Feb 14 00:19:34 linux-ytaf kernel: system 00:03: [io  0x0454-0x0457] has been reserved
Feb 14 00:19:34 linux-ytaf kernel: system 00:03: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
Feb 14 00:19:34 linux-ytaf kernel: system 00:04: [io  0x0290-0x029f] has been reserved
Feb 14 00:19:34 linux-ytaf kernel: system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 00:19:34 linux-ytaf kernel: system 00:05: [io  0x04d0-0x04d1] has been reserved
Feb 14 00:19:34 linux-ytaf kernel: system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 00:19:34 linux-ytaf kernel: system 00:06: [mem 0xfed1c000-0xfed1ffff] has been reserved
Feb 14 00:19:34 linux-ytaf kernel: system 00:06: [mem 0xfed10000-0xfed17fff] has been reserved
Feb 14 00:19:34 linux-ytaf kernel: system 00:06: [mem 0xfed18000-0xfed18fff] has been reserved
Feb 14 00:19:34 linux-ytaf kernel: system 00:06: [mem 0xfed19000-0xfed19fff] has been reserved
Feb 14 00:19:34 linux-ytaf kernel: system 00:06: [mem 0xf8000000-0xfbffffff] has been reserved
Feb 14 00:19:34 linux-ytaf kernel: system 00:06: [mem 0xfed20000-0xfed3ffff] has been reserved
Feb 14 00:19:34 linux-ytaf kernel: system 00:06: [mem 0xfed90000-0xfed93fff] has been reserved
Feb 14 00:19:34 linux-ytaf kernel: system 00:06: [mem 0xfed45000-0xfed8ffff] has been reserved
Feb 14 00:19:34 linux-ytaf kernel: system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Feb 14 00:19:34 linux-ytaf kernel: system 00:06: [mem 0xfee00000-0xfeefffff] could not be reserved
Feb 14 00:19:34 linux-ytaf kernel: system 00:06: [mem 0xcfa00000-0xcfa00fff] has been reserved
Feb 14 00:19:34 linux-ytaf kernel: system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 00:19:34 linux-ytaf kernel: system 00:07: [mem 0x20000000-0x201fffff] has been reserved
Feb 14 00:19:34 linux-ytaf kernel: system 00:07: [mem 0x40000000-0x401fffff] has been reserved
Feb 14 00:19:34 linux-ytaf kernel: system 00:07: Plug and Play ACPI device, IDs PNP0c01 (active)
Feb 14 00:19:34 linux-ytaf kernel: pnp: PnP ACPI: found 8 devices
Feb 14 00:19:34 linux-ytaf kernel: clocksource acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.0: bridge window [io  0x1000-0x0fff] to [bus 03] add_size 1000
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 03] add_size 200000 add_align 100000
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff] to [bus 03] add_size 200000 add_align 100000
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.0: res[14]=[mem 0x00100000-0x000fffff] res_to_dev_res add_size 200000 min_align 100000
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.0: res[14]=[mem 0x00100000-0x002fffff] res_to_dev_res add_size 200000 min_align 100000
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x000fffff 64bit pref] res_to_dev_res add_size 200000 min_align 100000
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x002fffff 64bit pref] res_to_dev_res add_size 200000 min_align 100000
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.0: res[13]=[io  0x1000-0x0fff] res_to_dev_res add_size 1000 min_align 1000
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.0: res[13]=[io  0x1000-0x1fff] res_to_dev_res add_size 1000 min_align 1000
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.0: BAR 14: assigned [mem 0xcfb00000-0xcfcfffff]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.0: BAR 15: assigned [mem 0xcfd00000-0xcfefffff 64bit pref]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.0: BAR 13: assigned [io  0x2000-0x2fff]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:01.1: PCI bridge to [bus 02]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [io  0xe000-0xefff]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xf6000000-0xf70fffff]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xe0000000-0xe9ffffff 64bit pref]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.0: PCI bridge to [bus 03]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.0:   bridge window [io  0x2000-0x2fff]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.0:   bridge window [mem 0xcfb00000-0xcfcfffff]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.0:   bridge window [mem 0xcfd00000-0xcfefffff 64bit pref]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.4: PCI bridge to [bus 04]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.4:   bridge window [mem 0xf7a00000-0xf7afffff]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.5: PCI bridge to [bus 05]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.5:   bridge window [mem 0xf7900000-0xf79fffff]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:06:00.0: BAR 6: assigned [mem 0xf7800000-0xf780ffff pref]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.6: PCI bridge to [bus 06]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [io  0xd000-0xdfff]
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [mem 0xf7800000-0xf78fffff]
Feb 14 00:19:34 linux-ytaf kernel: pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
Feb 14 00:19:34 linux-ytaf kernel: pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
Feb 14 00:19:34 linux-ytaf kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
Feb 14 00:19:34 linux-ytaf kernel: pci_bus 0000:00: resource 7 [mem 0x000d4000-0x000d7fff window]
Feb 14 00:19:34 linux-ytaf kernel: pci_bus 0000:00: resource 8 [mem 0x000d8000-0x000dbfff window]
Feb 14 00:19:34 linux-ytaf kernel: pci_bus 0000:00: resource 9 [mem 0x000dc000-0x000dffff window]
Feb 14 00:19:34 linux-ytaf kernel: pci_bus 0000:00: resource 10 [mem 0xcfa00000-0xfeafffff window]
Feb 14 00:19:34 linux-ytaf kernel: pci_bus 0000:02: resource 0 [io  0xe000-0xefff]
Feb 14 00:19:34 linux-ytaf kernel: pci_bus 0000:02: resource 1 [mem 0xf6000000-0xf70fffff]
Feb 14 00:19:34 linux-ytaf kernel: pci_bus 0000:02: resource 2 [mem 0xe0000000-0xe9ffffff 64bit pref]
Feb 14 00:19:34 linux-ytaf kernel: pci_bus 0000:03: resource 0 [io  0x2000-0x2fff]
Feb 14 00:19:34 linux-ytaf kernel: pci_bus 0000:03: resource 1 [mem 0xcfb00000-0xcfcfffff]
Feb 14 00:19:34 linux-ytaf kernel: pci_bus 0000:03: resource 2 [mem 0xcfd00000-0xcfefffff 64bit pref]
Feb 14 00:19:34 linux-ytaf kernel: pci_bus 0000:04: resource 1 [mem 0xf7a00000-0xf7afffff]
Feb 14 00:19:34 linux-ytaf kernel: pci_bus 0000:05: resource 1 [mem 0xf7900000-0xf79fffff]
Feb 14 00:19:34 linux-ytaf kernel: pci_bus 0000:06: resource 0 [io  0xd000-0xdfff]
Feb 14 00:19:34 linux-ytaf kernel: pci_bus 0000:06: resource 1 [mem 0xf7800000-0xf78fffff]
Feb 14 00:19:34 linux-ytaf kernel: NET: Registered protocol family 2
Feb 14 00:19:34 linux-ytaf kernel: TCP established hash table entries: 65536 (order: 7, 524288 bytes)
Feb 14 00:19:34 linux-ytaf kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Feb 14 00:19:34 linux-ytaf kernel: TCP: Hash tables configured (established 65536 bind 65536)
Feb 14 00:19:34 linux-ytaf kernel: UDP hash table entries: 4096 (order: 5, 131072 bytes)
Feb 14 00:19:34 linux-ytaf kernel: UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
Feb 14 00:19:34 linux-ytaf kernel: NET: Registered protocol family 1
Feb 14 00:19:34 linux-ytaf kernel: pci 0000:02:00.0: Video device with shadowed ROM
Feb 14 00:19:34 linux-ytaf kernel: PCI: CLS 64 bytes, default 64
Feb 14 00:19:34 linux-ytaf kernel: Unpacking initramfs...
Feb 14 00:19:34 linux-ytaf kernel: Freeing initrd memory: 11920K (ffff880000457000 - ffff880000ffb000)
Feb 14 00:19:34 linux-ytaf kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Feb 14 00:19:34 linux-ytaf kernel: software IO TLB [mem 0xc638f000-0xca38f000] (64MB) mapped at [ffff8800c638f000-ffff8800ca38efff]
Feb 14 00:19:34 linux-ytaf kernel: RAPL PMU detected, API unit is 2^-32 Joules, 3 fixed counters 163840 ms ovfl timer
Feb 14 00:19:34 linux-ytaf kernel: hw unit of domain pp0-core 2^-16 Joules
Feb 14 00:19:34 linux-ytaf kernel: hw unit of domain package 2^-16 Joules
Feb 14 00:19:34 linux-ytaf kernel: hw unit of domain pp1-gpu 2^-16 Joules
Feb 14 00:19:34 linux-ytaf kernel: microcode: CPU0 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 00:19:34 linux-ytaf kernel: microcode: CPU1 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 00:19:34 linux-ytaf kernel: microcode: CPU2 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 00:19:34 linux-ytaf kernel: microcode: CPU3 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 00:19:34 linux-ytaf kernel: microcode: CPU4 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 00:19:34 linux-ytaf kernel: microcode: CPU5 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 00:19:34 linux-ytaf kernel: microcode: CPU6 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 00:19:34 linux-ytaf kernel: microcode: CPU7 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 00:19:34 linux-ytaf kernel: microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Feb 14 00:19:34 linux-ytaf kernel: Scanning for low memory corruption every 60 seconds
Feb 14 00:19:34 linux-ytaf kernel: futex hash table entries: 2048 (order: 5, 131072 bytes)
Feb 14 00:19:34 linux-ytaf kernel: audit: initializing netlink subsys (disabled)
Feb 14 00:19:34 linux-ytaf kernel: audit: type=2000 audit(1455409171.284:1): initialized
Feb 14 00:19:34 linux-ytaf kernel: HugeTLB registered 2 MB page size, pre-allocated 0 pages
Feb 14 00:19:34 linux-ytaf kernel: zpool: loaded
Feb 14 00:19:34 linux-ytaf kernel: zbud: loaded
Feb 14 00:19:34 linux-ytaf kernel: VFS: Disk quotas dquot_6.6.0
Feb 14 00:19:34 linux-ytaf kernel: VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Feb 14 00:19:34 linux-ytaf kernel: Key type big_key registered
Feb 14 00:19:34 linux-ytaf kernel: Key type asymmetric registered
Feb 14 00:19:34 linux-ytaf kernel: Asymmetric key parser 'x509' registered
Feb 14 00:19:34 linux-ytaf kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Feb 14 00:19:34 linux-ytaf kernel: io scheduler noop registered
Feb 14 00:19:34 linux-ytaf kernel: io scheduler deadline registered
Feb 14 00:19:34 linux-ytaf kernel: io scheduler cfq registered (default)
Feb 14 00:19:34 linux-ytaf kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Feb 14 00:19:34 linux-ytaf kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Feb 14 00:19:34 linux-ytaf kernel: efifb: probing for efifb
Feb 14 00:19:34 linux-ytaf kernel: efifb: framebuffer at 0xe9000000, mapped to 0xffffc90001000000, using 1876k, total 1875k
Feb 14 00:19:34 linux-ytaf kernel: efifb: mode is 800x600x32, linelength=3200, pages=1
Feb 14 00:19:34 linux-ytaf kernel: efifb: scrolling: redraw
Feb 14 00:19:34 linux-ytaf kernel: efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Feb 14 00:19:34 linux-ytaf kernel: Console: switching to colour frame buffer device 100x37
Feb 14 00:19:34 linux-ytaf kernel: fb0: EFI VGA frame buffer device
Feb 14 00:19:34 linux-ytaf kernel: intel_idle: MWAIT substates: 0x1120
Feb 14 00:19:34 linux-ytaf kernel: intel_idle: v0.4 model 0x2A
Feb 14 00:19:34 linux-ytaf kernel: intel_idle: lapic_timer_reliable_states 0xffffffff
Feb 14 00:19:34 linux-ytaf kernel: GHES: HEST is not enabled!
Feb 14 00:19:34 linux-ytaf kernel: Serial: 8250/16550 driver, 32 ports, IRQ sharing disabled
Feb 14 00:19:34 linux-ytaf kernel: Non-volatile memory driver v1.3
Feb 14 00:19:34 linux-ytaf kernel: Linux agpgart interface v0.103
Feb 14 00:19:34 linux-ytaf kernel: ahci 0000:00:1f.2: version 3.0
Feb 14 00:19:34 linux-ytaf kernel: ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x7 impl SATA mode
Feb 14 00:19:34 linux-ytaf kernel: ahci 0000:00:1f.2: flags: 64bit ncq led clo pio slum part ems apst 
Feb 14 00:19:34 linux-ytaf kernel: scsi host0: ahci
Feb 14 00:19:34 linux-ytaf kernel: scsi host1: ahci
Feb 14 00:19:34 linux-ytaf kernel: scsi host2: ahci
Feb 14 00:19:34 linux-ytaf kernel: scsi host3: ahci
Feb 14 00:19:34 linux-ytaf kernel: scsi host4: ahci
Feb 14 00:19:34 linux-ytaf kernel: scsi host5: ahci
Feb 14 00:19:34 linux-ytaf kernel: ata1: SATA max UDMA/133 abar m2048@0xf7b26000 port 0xf7b26100 irq 26
Feb 14 00:19:34 linux-ytaf kernel: ata2: SATA max UDMA/133 abar m2048@0xf7b26000 port 0xf7b26180 irq 26
Feb 14 00:19:34 linux-ytaf kernel: ata3: SATA max UDMA/133 abar m2048@0xf7b26000 port 0xf7b26200 irq 26
Feb 14 00:19:34 linux-ytaf kernel: ata4: DUMMY
Feb 14 00:19:34 linux-ytaf kernel: ata5: DUMMY
Feb 14 00:19:34 linux-ytaf kernel: ata6: DUMMY
Feb 14 00:19:34 linux-ytaf kernel: ahci 0000:06:00.0: AHCI 0001.0100 32 slots 2 ports 3 Gbps 0x3 impl SATA mode
Feb 14 00:19:34 linux-ytaf kernel: ahci 0000:06:00.0: flags: 64bit ncq pm led clo pmp pio slum part 
Feb 14 00:19:34 linux-ytaf kernel: scsi host6: ahci
Feb 14 00:19:34 linux-ytaf kernel: scsi host7: ahci
Feb 14 00:19:34 linux-ytaf kernel: ata7: SATA max UDMA/133 abar m512@0xf7810000 port 0xf7810100 irq 18
Feb 14 00:19:34 linux-ytaf kernel: ata8: SATA max UDMA/133 abar m512@0xf7810000 port 0xf7810180 irq 18
Feb 14 00:19:34 linux-ytaf kernel: i8042: PNP: No PS/2 controller found. Probing ports directly.
Feb 14 00:19:34 linux-ytaf kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Feb 14 00:19:34 linux-ytaf kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Feb 14 00:19:34 linux-ytaf kernel: mousedev: PS/2 mouse device common for all mice
Feb 14 00:19:34 linux-ytaf kernel: rtc_cmos 00:02: RTC can wake from S4
Feb 14 00:19:34 linux-ytaf kernel: rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Feb 14 00:19:34 linux-ytaf kernel: rtc_cmos 00:02: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
Feb 14 00:19:34 linux-ytaf kernel: Intel P-state driver initializing.
Feb 14 00:19:34 linux-ytaf kernel: ledtrig-cpu: registered to indicate activity on CPUs
Feb 14 00:19:34 linux-ytaf kernel: EFI Variables Facility v0.08 2004-May-17
Feb 14 00:19:34 linux-ytaf kernel: hidraw: raw HID events driver (C) Jiri Kosina
Feb 14 00:19:34 linux-ytaf kernel: NET: Registered protocol family 10
Feb 14 00:19:34 linux-ytaf kernel: registered taskstats version 1
Feb 14 00:19:34 linux-ytaf kernel: Key type encrypted registered
Feb 14 00:19:34 linux-ytaf kernel: AppArmor: AppArmor sha1 policy hashing enabled
Feb 14 00:19:34 linux-ytaf kernel:   Magic number: 4:294:304
Feb 14 00:19:34 linux-ytaf kernel: tty tty33: hash matches
Feb 14 00:19:34 linux-ytaf kernel: rtc_cmos 00:02: setting system clock to 2016-02-14 00:19:32 UTC (1455409172)
Feb 14 00:19:34 linux-ytaf kernel: PM: Checking hibernation image partition /dev/sdb2
Feb 14 00:19:34 linux-ytaf kernel: ata7: SATA link down (SStatus 0 SControl 300)
Feb 14 00:19:34 linux-ytaf kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 14 00:19:34 linux-ytaf kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Feb 14 00:19:34 linux-ytaf kernel: ata8: SATA link down (SStatus 0 SControl 300)
Feb 14 00:19:34 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 00:19:34 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff8802268b7dd8), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 00:19:34 linux-ytaf kernel: ata2.00: ATA-8: TOSHIBA HDWD110, MS2OA8J0, max UDMA/133
Feb 14 00:19:34 linux-ytaf kernel: ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Feb 14 00:19:34 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 00:19:34 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff8802268b7d60), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 00:19:34 linux-ytaf kernel: ata3.00: ATAPI: TSSTcorp CDDVDW SH-S223C, SB05, max MWDMA2
Feb 14 00:19:34 linux-ytaf kernel: ata3.00: applying bridge limits
Feb 14 00:19:34 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 00:19:34 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff8802268b7dd8), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 00:19:34 linux-ytaf kernel: ata2.00: configured for UDMA/133
Feb 14 00:19:34 linux-ytaf kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 14 00:19:34 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 00:19:34 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff8802268b7e50), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 00:19:34 linux-ytaf kernel: ata1.00: ATA-9: SAMSUNG SSD 830 Series, CXM03B1Q, max UDMA/133
Feb 14 00:19:34 linux-ytaf kernel: ata1.00: 500118192 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Feb 14 00:19:34 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 00:19:34 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff8802268b7e50), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 00:19:34 linux-ytaf kernel: ata1.00: configured for UDMA/133
Feb 14 00:19:34 linux-ytaf kernel: scsi 0:0:0:0: Direct-Access     ATA      SAMSUNG SSD 830  3B1Q PQ: 0 ANSI: 5
Feb 14 00:19:34 linux-ytaf kernel: sd 0:0:0:0: [sda] 500118192 512-byte logical blocks: (256 GB/238 GiB)
Feb 14 00:19:34 linux-ytaf kernel: sd 0:0:0:0: [sda] Write Protect is off
Feb 14 00:19:34 linux-ytaf kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 14 00:19:34 linux-ytaf kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 14 00:19:34 linux-ytaf kernel: scsi 1:0:0:0: Direct-Access     ATA      TOSHIBA HDWD110  A8J0 PQ: 0 ANSI: 5
Feb 14 00:19:34 linux-ytaf kernel: sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
Feb 14 00:19:34 linux-ytaf kernel: sd 1:0:0:0: [sdb] 4096-byte physical blocks
Feb 14 00:19:34 linux-ytaf kernel: sd 1:0:0:0: [sdb] Write Protect is off
Feb 14 00:19:34 linux-ytaf kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Feb 14 00:19:34 linux-ytaf kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 14 00:19:34 linux-ytaf kernel:  sda: sda1 sda2 sda3 sda4
Feb 14 00:19:34 linux-ytaf kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Feb 14 00:19:34 linux-ytaf kernel:  sdb: sdb1 sdb2 sdb3 sdb4
Feb 14 00:19:34 linux-ytaf kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
Feb 14 00:19:34 linux-ytaf kernel: tsc: Refined TSC clocksource calibration: 3411.128 MHz
Feb 14 00:19:34 linux-ytaf kernel: clocksource tsc: mask: 0xffffffffffffffff max_cycles: 0x312b5ecadef, max_idle_ns: 440795307361 ns
Feb 14 00:19:34 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 00:19:34 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff8802268b7d60), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 00:19:34 linux-ytaf kernel: ata3.00: configured for PIO4
Feb 14 00:19:34 linux-ytaf kernel: scsi 2:0:0:0: CD-ROM            TSSTcorp CDDVDW SH-S223C  SB05 PQ: 0 ANSI: 5
Feb 14 00:19:34 linux-ytaf kernel: PM: Hibernation image partition 8:18 present
Feb 14 00:19:34 linux-ytaf kernel: PM: Looking for hibernation image.
Feb 14 00:19:34 linux-ytaf kernel: Switched to clocksource tsc
Feb 14 00:19:34 linux-ytaf kernel: PM: Image not found (code -22)
Feb 14 00:19:34 linux-ytaf kernel: PM: Hibernation image not present or could not be loaded.
Feb 14 00:19:34 linux-ytaf kernel: Freeing unused kernel memory: 1560K (ffffffff81f11000 - ffffffff82097000)
Feb 14 00:19:34 linux-ytaf kernel: Write protecting the kernel read-only data: 14336k
Feb 14 00:19:34 linux-ytaf kernel: Freeing unused kernel memory: 1632K (ffff88000d668000 - ffff88000d800000)
Feb 14 00:19:34 linux-ytaf kernel: Freeing unused kernel memory: 1296K (ffff88000dcbc000 - ffff88000de00000)
Feb 14 00:19:34 linux-ytaf systemd[1]: RTC configured in localtime, applying delta of 60 minutes to system time.
Feb 14 00:19:34 linux-ytaf kernel: random: systemd urandom read with 22 bits of entropy available
Feb 14 00:19:34 linux-ytaf kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Feb 14 00:19:34 linux-ytaf kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0
Feb 14 00:19:34 linux-ytaf kernel: scsi 2:0:0:0: Attached scsi generic sg2 type 5
Feb 14 00:19:34 linux-ytaf systemd-journal[187]: Journal started
Feb 14 00:19:34 linux-ytaf dracut-cmdline[181]: dracut-42.1 dracut-037-68.1
Feb 14 00:19:34 linux-ytaf systemd-udevd[249]: Network interface NamePolicy= disabled on kernel commandline, ignoring.
Feb 14 00:19:34 linux-ytaf kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3
Feb 14 00:19:34 linux-ytaf kernel: ACPI: Power Button [PWRB]
Feb 14 00:19:34 linux-ytaf kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
Feb 14 00:19:34 linux-ytaf kernel: ACPI: Power Button [PWRF]
Feb 14 00:19:34 linux-ytaf kernel: ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
Feb 14 00:19:34 linux-ytaf kernel: acpi device:58: registered as cooling_device0
Feb 14 00:19:34 linux-ytaf kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5
Feb 14 00:19:34 linux-ytaf kernel: wmi: Mapper loaded
Feb 14 00:19:34 linux-ytaf kernel: ACPI: bus type USB registered
Feb 14 00:19:34 linux-ytaf kernel: usbcore: registered new interface driver usbfs
Feb 14 00:19:34 linux-ytaf kernel: usbcore: registered new interface driver hub
Feb 14 00:19:34 linux-ytaf kernel: usbcore: registered new device driver usb
Feb 14 00:19:34 linux-ytaf kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Feb 14 00:19:34 linux-ytaf kernel: ehci-pci: EHCI PCI platform driver
Feb 14 00:19:34 linux-ytaf kernel: ehci-pci 0000:00:1a.0: EHCI Host Controller
Feb 14 00:19:34 linux-ytaf kernel: ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Feb 14 00:19:34 linux-ytaf kernel: ehci-pci 0000:00:1a.0: debug port 2
Feb 14 00:19:34 linux-ytaf kernel: [drm] Initialized drm 1.1.0 20060810
Feb 14 00:19:34 linux-ytaf kernel: ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Feb 14 00:19:34 linux-ytaf kernel: ehci-pci 0000:00:1a.0: irq 16, io mem 0xf7b28000
Feb 14 00:19:34 linux-ytaf kernel: MXM: GUID detected in BIOS
Feb 14 00:19:34 linux-ytaf kernel: checking generic (e9000000 1d5000) vs hw (e0000000 8000000)
Feb 14 00:19:34 linux-ytaf kernel: checking generic (e9000000 1d5000) vs hw (e8000000 2000000)
Feb 14 00:19:34 linux-ytaf kernel: fb: switching to nouveaufb from EFI VGA
Feb 14 00:19:34 linux-ytaf kernel: Console: switching to colour dummy device 80x25
Feb 14 00:19:34 linux-ytaf kernel: nouveau  [  DEVICE][0000:02:00.0] BOOT0  : 0x0e4030a2
Feb 14 00:19:34 linux-ytaf kernel: nouveau  [  DEVICE][0000:02:00.0] Chipset: GK104 (NVE4)
Feb 14 00:19:34 linux-ytaf kernel: nouveau  [  DEVICE][0000:02:00.0] Family : NVE0
Feb 14 00:19:34 linux-ytaf kernel: ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Feb 14 00:19:34 linux-ytaf kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 00:19:34 linux-ytaf kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 00:19:34 linux-ytaf kernel: usb usb1: Product: EHCI Host Controller
Feb 14 00:19:34 linux-ytaf kernel: usb usb1: Manufacturer: Linux 4.1.15-8-default ehci_hcd
Feb 14 00:19:34 linux-ytaf kernel: usb usb1: SerialNumber: 0000:00:1a.0
Feb 14 00:19:34 linux-ytaf kernel: hub 1-0:1.0: USB hub found
Feb 14 00:19:34 linux-ytaf kernel: hub 1-0:1.0: 2 ports detected
Feb 14 00:19:34 linux-ytaf kernel: xhci_hcd 0000:04:00.0: xHCI Host Controller
Feb 14 00:19:34 linux-ytaf kernel: xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 2
Feb 14 00:19:34 linux-ytaf kernel: sr 2:0:0:0: [sr0] scsi3-mmc drive: 52x/52x writer dvd-ram cd/rw xa/form2 cdda tray
Feb 14 00:19:34 linux-ytaf kernel: cdrom: Uniform CD-ROM driver Revision: 3.20
Feb 14 00:19:34 linux-ytaf kernel: sr 2:0:0:0: Attached scsi CD-ROM sr0
Feb 14 00:19:34 linux-ytaf kernel: xhci_hcd 0000:04:00.0: hcc params 0x0200f180 hci version 0x96 quirks 0x00080000
Feb 14 00:19:34 linux-ytaf kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 00:19:34 linux-ytaf kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 00:19:34 linux-ytaf kernel: usb usb2: Product: xHCI Host Controller
Feb 14 00:19:34 linux-ytaf kernel: usb usb2: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 00:19:34 linux-ytaf kernel: usb usb2: SerialNumber: 0000:04:00.0
Feb 14 00:19:34 linux-ytaf kernel: hub 2-0:1.0: USB hub found
Feb 14 00:19:34 linux-ytaf kernel: hub 2-0:1.0: 2 ports detected
Feb 14 00:19:34 linux-ytaf kernel: xhci_hcd 0000:04:00.0: xHCI Host Controller
Feb 14 00:19:34 linux-ytaf kernel: xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 3
Feb 14 00:19:34 linux-ytaf kernel: ehci-pci 0000:00:1d.0: EHCI Host Controller
Feb 14 00:19:34 linux-ytaf kernel: usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
Feb 14 00:19:34 linux-ytaf kernel: usb usb3: New USB device found, idVendor=1d6b, idProduct=0003
Feb 14 00:19:34 linux-ytaf kernel: usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 00:19:34 linux-ytaf kernel: usb usb3: Product: xHCI Host Controller
Feb 14 00:19:34 linux-ytaf kernel: usb usb3: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 00:19:34 linux-ytaf kernel: usb usb3: SerialNumber: 0000:04:00.0
Feb 14 00:19:34 linux-ytaf kernel: hub 3-0:1.0: USB hub found
Feb 14 00:19:34 linux-ytaf kernel: hub 3-0:1.0: 2 ports detected
Feb 14 00:19:34 linux-ytaf kernel: ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 4
Feb 14 00:19:34 linux-ytaf kernel: ehci-pci 0000:00:1d.0: debug port 2
Feb 14 00:19:34 linux-ytaf kernel: ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Feb 14 00:19:34 linux-ytaf kernel: ehci-pci 0000:00:1d.0: irq 23, io mem 0xf7b27000
Feb 14 00:19:34 linux-ytaf kernel: ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Feb 14 00:19:34 linux-ytaf kernel: usb usb4: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 00:19:34 linux-ytaf kernel: usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 00:19:34 linux-ytaf kernel: usb usb4: Product: EHCI Host Controller
Feb 14 00:19:34 linux-ytaf kernel: usb usb4: Manufacturer: Linux 4.1.15-8-default ehci_hcd
Feb 14 00:19:34 linux-ytaf kernel: usb usb4: SerialNumber: 0000:00:1d.0
Feb 14 00:19:34 linux-ytaf kernel: hub 4-0:1.0: USB hub found
Feb 14 00:19:34 linux-ytaf kernel: hub 4-0:1.0: 2 ports detected
Feb 14 00:19:34 linux-ytaf kernel: xhci_hcd 0000:05:00.0: xHCI Host Controller
Feb 14 00:19:34 linux-ytaf kernel: xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 5
Feb 14 00:19:34 linux-ytaf kernel: i915 0000:00:02.0: enabling device (0006 -> 0007)
Feb 14 00:19:34 linux-ytaf kernel: xhci_hcd 0000:05:00.0: hcc params 0x0200f180 hci version 0x96 quirks 0x00080000
Feb 14 00:19:34 linux-ytaf kernel: usb usb5: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 00:19:34 linux-ytaf kernel: usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 00:19:34 linux-ytaf kernel: usb usb5: Product: xHCI Host Controller
Feb 14 00:19:34 linux-ytaf kernel: usb usb5: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 00:19:34 linux-ytaf kernel: usb usb5: SerialNumber: 0000:05:00.0
Feb 14 00:19:34 linux-ytaf kernel: hub 5-0:1.0: USB hub found
Feb 14 00:19:34 linux-ytaf kernel: hub 5-0:1.0: 2 ports detected
Feb 14 00:19:34 linux-ytaf kernel: xhci_hcd 0000:05:00.0: xHCI Host Controller
Feb 14 00:19:34 linux-ytaf kernel: xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 6
Feb 14 00:19:34 linux-ytaf kernel: usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
Feb 14 00:19:34 linux-ytaf kernel: usb usb6: New USB device found, idVendor=1d6b, idProduct=0003
Feb 14 00:19:34 linux-ytaf kernel: usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 00:19:34 linux-ytaf kernel: usb usb6: Product: xHCI Host Controller
Feb 14 00:19:34 linux-ytaf kernel: usb usb6: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 00:19:34 linux-ytaf kernel: usb usb6: SerialNumber: 0000:05:00.0
Feb 14 00:19:34 linux-ytaf kernel: hub 6-0:1.0: USB hub found
Feb 14 00:19:34 linux-ytaf kernel: hub 6-0:1.0: 2 ports detected
Feb 14 00:19:34 linux-ytaf kernel: nouveau  [   VBIOS][0000:02:00.0] using image from PROM
Feb 14 00:19:34 linux-ytaf kernel: nouveau  [   VBIOS][0000:02:00.0] BIT signature found
Feb 14 00:19:34 linux-ytaf kernel: nouveau  [   VBIOS][0000:02:00.0] version 80.04.4b.00.07
Feb 14 00:19:34 linux-ytaf kernel: nouveau  [     PMC][0000:02:00.0] MSI interrupts enabled
Feb 14 00:19:34 linux-ytaf kernel: nouveau  [     PFB][0000:02:00.0] RAM type: GDDR5
Feb 14 00:19:34 linux-ytaf kernel: nouveau  [     PFB][0000:02:00.0] RAM size: 2048 MiB
Feb 14 00:19:34 linux-ytaf kernel: nouveau  [     PFB][0000:02:00.0]    ZCOMP: 0 tags
Feb 14 00:19:34 linux-ytaf kernel: nouveau  [    VOLT][0000:02:00.0] GPU voltage: 987500uv
Feb 14 00:19:34 linux-ytaf kernel: nouveau  [  PTHERM][0000:02:00.0] FAN control: PWM
Feb 14 00:19:34 linux-ytaf kernel: nouveau  [  PTHERM][0000:02:00.0] fan management: automatic
Feb 14 00:19:34 linux-ytaf kernel: nouveau  [  PTHERM][0000:02:00.0] internal sensor: yes
Feb 14 00:19:34 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 07: core 324 MHz memory 648 MHz 
Feb 14 00:19:34 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 0a: core 324-862 MHz memory 1620 MHz 
Feb 14 00:19:34 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 0d: core 540-1202 MHz memory 6008 MHz 
Feb 14 00:19:34 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 0f: core 540-1202 MHz memory 6008 MHz 
Feb 14 00:19:34 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] --: core 324 MHz memory 648 MHz 
Feb 14 00:19:34 linux-ytaf kernel: raid6: sse2x1   gen() 11252 MB/s
Feb 14 00:19:34 linux-ytaf kernel: usb 1-1: new high-speed USB device number 2 using ehci-pci
Feb 14 00:19:34 linux-ytaf kernel: [TTM] Zone  kernel: Available graphics memory: 4034698 kiB
Feb 14 00:19:34 linux-ytaf kernel: [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
Feb 14 00:19:34 linux-ytaf kernel: [TTM] Initializing pool allocator
Feb 14 00:19:34 linux-ytaf kernel: [TTM] Initializing DMA pool allocator
Feb 14 00:19:34 linux-ytaf kernel: nouveau  [     DRM] VRAM: 2048 MiB
Feb 14 00:19:34 linux-ytaf kernel: nouveau  [     DRM] GART: 1048576 MiB
Feb 14 00:19:34 linux-ytaf kernel: nouveau  [     DRM] TMDS table version 2.0
Feb 14 00:19:34 linux-ytaf kernel: nouveau  [     DRM] DCB version 4.0
Feb 14 00:19:34 linux-ytaf kernel: nouveau  [     DRM] DCB outp 00: 01000f02 00020030
Feb 14 00:19:34 linux-ytaf kernel: nouveau  [     DRM] DCB outp 01: 02000f00 00000000
Feb 14 00:19:34 linux-ytaf kernel: nouveau  [     DRM] DCB outp 02: 08011f82 00020030
Feb 14 00:19:34 linux-ytaf kernel: nouveau  [     DRM] DCB outp 03: 02822f62 0f420010
Feb 14 00:19:34 linux-ytaf kernel: nouveau  [     DRM] DCB outp 05: 04833fb6 0f420010
Feb 14 00:19:34 linux-ytaf kernel: nouveau  [     DRM] DCB outp 06: 04033f72 00020010
Feb 14 00:19:34 linux-ytaf kernel: nouveau  [     DRM] DCB conn 00: 00001030
Feb 14 00:19:34 linux-ytaf kernel: nouveau  [     DRM] DCB conn 01: 00020131
Feb 14 00:19:34 linux-ytaf kernel: nouveau  [     DRM] DCB conn 02: 00002261
Feb 14 00:19:34 linux-ytaf kernel: nouveau  [     DRM] DCB conn 03: 00010346
Feb 14 00:19:34 linux-ytaf kernel: nouveau  [     DRM] DCB conn 04: 00000460
Feb 14 00:19:34 linux-ytaf kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Feb 14 00:19:34 linux-ytaf kernel: [drm] Driver supports precise vblank timestamp query.
Feb 14 00:19:34 linux-ytaf kernel: nouveau  [     DRM] MM: using COPY for buffer copies
Feb 14 00:19:34 linux-ytaf kernel: raid6: sse2x1   xor()  7495 MB/s
Feb 14 00:19:34 linux-ytaf kernel: usb 4-1: new high-speed USB device number 2 using ehci-pci
Feb 14 00:19:34 linux-ytaf kernel: raid6: sse2x2   gen() 14099 MB/s
Feb 14 00:19:34 linux-ytaf kernel: usb 1-1: New USB device found, idVendor=8087, idProduct=0024
Feb 14 00:19:34 linux-ytaf kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb 14 00:19:34 linux-ytaf kernel: hub 1-1:1.0: USB hub found
Feb 14 00:19:34 linux-ytaf kernel: hub 1-1:1.0: 6 ports detected
Feb 14 00:19:35 linux-ytaf kernel: raid6: sse2x2   xor() 10037 MB/s
Feb 14 00:19:35 linux-ytaf kernel: usb 5-2: new high-speed USB device number 2 using xhci_hcd
Feb 14 00:19:35 linux-ytaf kernel: usb 4-1: New USB device found, idVendor=8087, idProduct=0024
Feb 14 00:19:35 linux-ytaf kernel: usb 4-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb 14 00:19:35 linux-ytaf kernel: hub 4-1:1.0: USB hub found
Feb 14 00:19:35 linux-ytaf kernel: hub 4-1:1.0: 8 ports detected
Feb 14 00:19:35 linux-ytaf kernel: raid6: sse2x4   gen() 16267 MB/s
Feb 14 00:19:35 linux-ytaf kernel: raid6: sse2x4   xor() 12098 MB/s
Feb 14 00:19:35 linux-ytaf kernel: raid6: using algorithm sse2x4 gen() 16267 MB/s
Feb 14 00:19:35 linux-ytaf kernel: raid6: .... xor() 12098 MB/s, rmw enabled
Feb 14 00:19:35 linux-ytaf kernel: raid6: using ssse3x2 recovery algorithm
Feb 14 00:19:35 linux-ytaf kernel: xor: automatically using best checksumming function:
Feb 14 00:19:35 linux-ytaf kernel: nouveau  [     DRM] allocated 1920x1080 fb: 0x60000, bo ffff880222b7f800
Feb 14 00:19:35 linux-ytaf kernel: fbcon: nouveaufb (fb0) is primary device
Feb 14 00:19:35 linux-ytaf kernel:    avx       : 31206.000 MB/sec
Feb 14 00:19:35 linux-ytaf kernel: Btrfs loaded, assert=on
Feb 14 00:19:35 linux-ytaf kernel: BTRFS: device fsid 21024970-7a27-4114-8525-d8dd026f23b6 devid 1 transid 103 /dev/sdb3
Feb 14 00:19:35 linux-ytaf kernel: usb 5-2: New USB device found, idVendor=0930, idProduct=6545
Feb 14 00:19:35 linux-ytaf kernel: usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 14 00:19:35 linux-ytaf kernel: usb 5-2: Product: TransMemory
Feb 14 00:19:35 linux-ytaf kernel: usb 5-2: Manufacturer: TOSHIBA
Feb 14 00:19:35 linux-ytaf kernel: usb 5-2: SerialNumber: C89CDCBF6D59EF4140000065
Feb 14 00:19:35 linux-ytaf kernel: usb-storage 5-2:1.0: USB Mass Storage device detected
Feb 14 00:19:35 linux-ytaf kernel: scsi host8: usb-storage 5-2:1.0
Feb 14 00:19:35 linux-ytaf kernel: usbcore: registered new interface driver usb-storage
Feb 14 00:19:35 linux-ytaf kernel: usbcore: registered new interface driver uas
Feb 14 00:19:35 linux-ytaf kernel: usb 1-1.4: new full-speed USB device number 3 using ehci-pci
Feb 14 00:19:35 linux-ytaf kernel: usb 4-1.1: new full-speed USB device number 3 using ehci-pci
Feb 14 00:19:35 linux-ytaf kernel: usb 4-1.1: New USB device found, idVendor=1532, idProduct=0109
Feb 14 00:19:35 linux-ytaf kernel: usb 4-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 14 00:19:35 linux-ytaf kernel: usb 4-1.1: Product: Razer Lycosa
Feb 14 00:19:35 linux-ytaf kernel: usb 4-1.1: Manufacturer: Razer
Feb 14 00:19:35 linux-ytaf kernel: usbcore: registered new interface driver usbhid
Feb 14 00:19:35 linux-ytaf kernel: usbhid: USB HID core driver
Feb 14 00:19:35 linux-ytaf kernel: input: Razer Razer Lycosa as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1:1.0/0003:1532:0109.0001/input/input6
Feb 14 00:19:35 linux-ytaf kernel: usb 1-1.4: New USB device found, idVendor=06a3, idProduct=0ccb
Feb 14 00:19:35 linux-ytaf kernel: usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 14 00:19:35 linux-ytaf kernel: usb 1-1.4: Product: Cyborg R.A.T.7 Mouse
Feb 14 00:19:35 linux-ytaf kernel: usb 1-1.4: Manufacturer: Saitek
Feb 14 00:19:35 linux-ytaf kernel: hid-generic 0003:1532:0109.0001: input,hidraw0: USB HID v1.10 Keyboard [Razer Razer Lycosa] on usb-0000:00:1d.0-1.1/input0
Feb 14 00:19:35 linux-ytaf kernel: input: Razer Razer Lycosa as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1:1.1/0003:1532:0109.0002/input/input7
Feb 14 00:19:35 linux-ytaf kernel: hid-generic 0003:1532:0109.0002: input,hidraw1: USB HID v1.10 Device [Razer Razer Lycosa] on usb-0000:00:1d.0-1.1/input1
Feb 14 00:19:35 linux-ytaf kernel: Console: switching to colour frame buffer device 210x65
Feb 14 00:19:35 linux-ytaf kernel: nouveau 0000:02:00.0: fb0: nouveaufb frame buffer device
Feb 14 00:19:35 linux-ytaf kernel: nouveau 0000:02:00.0: registered panic notifier
Feb 14 00:19:35 linux-ytaf kernel: [drm] Initialized nouveau 1.2.2 20120801 for 0000:02:00.0 on minor 0
Feb 14 00:19:35 linux-ytaf kernel: [drm] Memory usable by graphics device = 2048M
Feb 14 00:19:35 linux-ytaf kernel: [drm] Replacing VGA console driver
Feb 14 00:19:35 linux-ytaf kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Feb 14 00:19:35 linux-ytaf kernel: [drm] Driver supports precise vblank timestamp query.
Feb 14 00:19:35 linux-ytaf kernel: vgaarb: device changed decodes: PCI:0000:02:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
Feb 14 00:19:35 linux-ytaf kernel: [drm] Initialized i915 1.6.0 20150327 for 0000:00:02.0 on minor 1
Feb 14 00:19:35 linux-ytaf kernel: [drm] GMBUS [i915 gmbus vga] timed out, falling back to bit banging on pin 2
Feb 14 00:19:35 linux-ytaf kernel: i915 0000:00:02.0: No connectors reported connected with modes
Feb 14 00:19:35 linux-ytaf kernel: [drm] Cannot find any crtc or sizes - going 1024x768
Feb 14 00:19:35 linux-ytaf kernel: i915 0000:00:02.0: fb1: inteldrmfb frame buffer device
Feb 14 00:19:35 linux-ytaf kernel: PM: Starting manual resume from disk
Feb 14 00:19:35 linux-ytaf kernel: PM: Hibernation image partition 8:18 present
Feb 14 00:19:35 linux-ytaf kernel: PM: Looking for hibernation image.
Feb 14 00:19:35 linux-ytaf kernel: PM: Image not found (code -22)
Feb 14 00:19:35 linux-ytaf kernel: PM: Hibernation image not present or could not be loaded.
Feb 14 00:19:35 linux-ytaf kernel: BTRFS info (device sdb3): disk space caching is enabled
Feb 14 00:19:35 linux-ytaf kernel: BTRFS: has skinny extents
Feb 14 00:19:35 linux-ytaf dracut-pre-pivot[416]: Converting /var/run to /run tmpfs
Feb 14 00:19:35 linux-ytaf dracut-pre-pivot[416]: TARGET SOURCE FSTYPE OPTIONS
Feb 14 00:19:35 linux-ytaf dracut-pre-pivot[416]: /sysroot /dev/sdb3[/@/.snapshots/1/snapshot] btrfs ro,relatime,space_cache,subvolid=259,subvol=/@/.snapshots/1/snapshot
Feb 14 00:19:35 linux-ytaf kernel: BTRFS info (device sdb3): disk space caching is enabled
Feb 14 00:19:35 linux-ytaf dracut-pre-pivot[416]: Converting /var/run to symlink
Feb 14 00:19:36 linux-ytaf kernel: BTRFS info (device sdb3): disk space caching is enabled
Feb 14 00:19:36 linux-ytaf kernel: scsi 8:0:0:0: Direct-Access     TOSHIBA  TransMemory      PMAP PQ: 0 ANSI: 6
Feb 14 00:19:36 linux-ytaf kernel: sd 8:0:0:0: Attached scsi generic sg3 type 0
Feb 14 00:19:36 linux-ytaf kernel: sd 8:0:0:0: [sdc] 30228480 512-byte logical blocks: (15.4 GB/14.4 GiB)
Feb 14 00:19:36 linux-ytaf kernel: sd 8:0:0:0: [sdc] Write Protect is off
Feb 14 00:19:36 linux-ytaf kernel: sd 8:0:0:0: [sdc] Mode Sense: 45 00 00 00
Feb 14 00:19:36 linux-ytaf kernel: sd 8:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Feb 14 00:19:36 linux-ytaf kernel: random: nonblocking pool is initialized
Feb 14 00:19:36 linux-ytaf [187]: Journal stopped
Feb 14 00:19:40 linux-ytaf systemd-journal[483]: Runtime journal is using 8.0M (max allowed 394.0M, trying to leave 591.0M free of 3.8G available → current limit 394.0M).
Feb 14 00:19:40 linux-ytaf systemd-journal[483]: Runtime journal is using 8.0M (max allowed 394.0M, trying to leave 591.0M free of 3.8G available → current limit 394.0M).
Feb 14 00:19:40 linux-ytaf kernel:  sdc: sdc1
Feb 14 00:19:40 linux-ytaf kernel: sd 8:0:0:0: [sdc] Attached SCSI removable disk
Feb 14 00:19:40 linux-ytaf systemd[1]: RTC configured in localtime, applying delta of 60 minutes to system time.
Feb 14 00:19:40 linux-ytaf kernel: BTRFS info (device sdb3): disk space caching is enabled
Feb 14 00:19:40 linux-ytaf kernel: thermal LNXTHERM:00: registered as thermal_zone0
Feb 14 00:19:40 linux-ytaf kernel: ACPI: Thermal Zone [TZ00] (28 C)
Feb 14 00:19:40 linux-ytaf kernel: thermal LNXTHERM:01: registered as thermal_zone1
Feb 14 00:19:40 linux-ytaf kernel: ACPI: Thermal Zone [TZ01] (30 C)
Feb 14 00:19:40 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000580-0x000000000000059F conflicts with OpRegion 0x0000000000000580-0x000000000000058F (\_SB_.PCI0.SBUS.SMBI) (20150410/utaddress-254)
Feb 14 00:19:40 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000580-0x000000000000059F conflicts with OpRegion 0x0000000000000580-0x000000000000059F (\_SB_.PCI0.SMB_.SMIO) (20150410/utaddress-254)
Feb 14 00:19:40 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 00:19:40 linux-ytaf kernel: input: PC Speaker as /devices/platform/pcspkr/input/input8
Feb 14 00:19:40 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20150410/utaddress-254)
Feb 14 00:19:40 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 00:19:40 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150410/utaddress-254)
Feb 14 00:19:40 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150410/utaddress-254)
Feb 14 00:19:40 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 00:19:40 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150410/utaddress-254)
Feb 14 00:19:40 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150410/utaddress-254)
Feb 14 00:19:40 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 00:19:40 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150410/utaddress-254)
Feb 14 00:19:40 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150410/utaddress-254)
Feb 14 00:19:40 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 00:19:40 linux-ytaf kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
Feb 14 00:19:40 linux-ytaf kernel: pps_core: LinuxPPS API ver. 1 registered
Feb 14 00:19:40 linux-ytaf kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
Feb 14 00:19:40 linux-ytaf kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Feb 14 00:19:40 linux-ytaf kernel: PTP clock support registered
Feb 14 00:19:40 linux-ytaf kernel: asus_wmi: ASUS WMI generic driver loaded
Feb 14 00:19:40 linux-ytaf kernel: iTCO_vendor_support: vendor-support=0
Feb 14 00:19:40 linux-ytaf kernel: iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
Feb 14 00:19:40 linux-ytaf kernel: iTCO_wdt: Found a Cougar Point TCO device (Version=2, TCOBASE=0x0460)
Feb 14 00:19:40 linux-ytaf kernel: iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
Feb 14 00:19:40 linux-ytaf kernel: asus_wmi: Initialization: 0x0
Feb 14 00:19:40 linux-ytaf kernel: asus_wmi: BIOS WMI version: 0.9
Feb 14 00:19:40 linux-ytaf kernel: asus_wmi: SFUN value: 0x0
Feb 14 00:19:40 linux-ytaf kernel: input: Eee PC WMI hotkeys as /devices/platform/eeepc-wmi/input/input9
Feb 14 00:19:40 linux-ytaf kernel: asus_wmi: Disabling ACPI video driver
Feb 14 00:19:40 linux-ytaf kernel: e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
Feb 14 00:19:40 linux-ytaf kernel: e1000e: Copyright(c) 1999 - 2014 Intel Corporation.
Feb 14 00:19:40 linux-ytaf kernel: e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
Feb 14 00:19:40 linux-ytaf kernel: AVX version of gcm_enc/dec engaged.
Feb 14 00:19:40 linux-ytaf kernel: AES CTR mode by8 optimization enabled
Feb 14 00:19:40 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: registered PHC clock
Feb 14 00:19:40 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) c8:60:00:09:38:76
Feb 14 00:19:40 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
Feb 14 00:19:40 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: FFFFFF-0FF
Feb 14 00:19:40 linux-ytaf kernel: snd_hda_intel 0000:00:1b.0: enabling device (0000 -> 0002)
Feb 14 00:19:40 linux-ytaf kernel: snd_hda_intel 0000:02:00.1: enabling device (0000 -> 0002)
Feb 14 00:19:40 linux-ytaf kernel: snd_hda_intel 0000:02:00.1: Disabling MSI
Feb 14 00:19:40 linux-ytaf kernel: snd_hda_intel 0000:02:00.1: Handle VGA-switcheroo audio client
Feb 14 00:19:40 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC889: line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line
Feb 14 00:19:40 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Feb 14 00:19:40 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
Feb 14 00:19:40 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
Feb 14 00:19:40 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    dig-out=0x11/0x1e
Feb 14 00:19:40 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    inputs:
Feb 14 00:19:40 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:      Front Mic=0x19
Feb 14 00:19:40 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:      Rear Mic=0x18
Feb 14 00:19:40 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:      Line=0x1a
Feb 14 00:19:40 linux-ytaf kernel: input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
Feb 14 00:19:40 linux-ytaf kernel: input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
Feb 14 00:19:40 linux-ytaf kernel: input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
Feb 14 00:19:40 linux-ytaf kernel: input: HDA Intel PCH Line Out Front as /devices/pci0000:00/0000:00:1b.0/sound/card0/input13
Feb 14 00:19:40 linux-ytaf kernel: input: HDA Intel PCH Line Out Surround as /devices/pci0000:00/0000:00:1b.0/sound/card0/input14
Feb 14 00:19:40 linux-ytaf kernel: input: HDA Intel PCH Line Out CLFE as /devices/pci0000:00/0000:00:1b.0/sound/card0/input15
Feb 14 00:19:40 linux-ytaf kernel: input: HDA Intel PCH Line Out Side as /devices/pci0000:00/0000:00:1b.0/sound/card0/input16
Feb 14 00:19:40 linux-ytaf kernel: input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input17
Feb 14 00:19:40 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input18
Feb 14 00:19:40 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input19
Feb 14 00:19:40 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input20
Feb 14 00:19:40 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input21
Feb 14 00:19:40 linux-ytaf kernel: Adding 2104316k swap on /dev/sdb2.  Priority:-1 extents:1 across:2104316k FS
Feb 14 00:19:40 linux-ytaf kernel: input: Saitek Cyborg R.A.T.7 Mouse as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/0003:06A3:0CCB.0003/input/input22
Feb 14 00:19:40 linux-ytaf kernel: saitek 0003:06A3:0CCB.0003: input,hidraw2: USB HID v1.11 Mouse [Saitek Cyborg R.A.T.7 Mouse] on usb-0000:00:1a.0-1.4/input0
Feb 14 00:19:40 linux-ytaf kernel: SGI XFS with ACLs, security attributes, realtime, no debug enabled
Feb 14 00:19:40 linux-ytaf kernel: XFS (sdb4): Mounting V5 Filesystem
Feb 14 00:19:40 linux-ytaf kernel: XFS (sdb4): Ending clean mount
Feb 14 00:19:40 linux-ytaf systemd-journal[483]: Journal started
Feb 14 00:19:39 linux-ytaf mtp-probe[668]: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4"
Feb 14 00:19:39 linux-ytaf mtp-probe[692]: checking bus 5, device 2: "/sys/devices/pci0000:00/0000:00:1c.5/0000:05:00.0/usb5/5-2"
Feb 14 00:19:39 linux-ytaf mtp-probe[671]: checking bus 4, device 3: "/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1"
Feb 14 00:19:39 linux-ytaf mtp-probe[668]: bus: 1, device: 3 was not an MTP device
Feb 14 00:19:39 linux-ytaf mtp-probe[692]: bus: 5, device: 2 was not an MTP device
Feb 14 00:19:39 linux-ytaf mtp-probe[671]: bus: 4, device: 3 was not an MTP device
Feb 14 00:19:38 linux-ytaf systemd-udevd[498]: Network interface NamePolicy= disabled on kernel commandline, ignoring.
Feb 14 00:19:38 linux-ytaf systemd-udevd[498]: invalid key/value pair in file /usr/lib/udev/rules.d/51-android.rules on line 115,starting at character 57 ('')
Feb 14 00:19:40 linux-ytaf systemd-fsck[766]: /sbin/fsck.xfs: XFS file system.
Feb 14 00:19:40 linux-ytaf auditd[825]: Started dispatcher: /sbin/audispd pid: 829
Feb 14 00:19:40 linux-ytaf kernel: audit: type=1305 audit(1455405580.369:2): audit_pid=825 old=0 auid=4294967295 ses=4294967295 res=1
Feb 14 00:19:40 linux-ytaf systemd-journal[483]: Permanent journal is using 11.5M (max allowed 4.0G, trying to leave 4.0G free of 33.0G available → current limit 4.0G).
Feb 14 00:19:40 linux-ytaf systemd-journal[483]: Time spent on flushing to /var is 32.759ms for 1037 entries.
Feb 14 00:19:40 linux-ytaf auditd[825]: Init complete, auditd 2.3.6 listening for events (startup state enable)
Feb 14 00:19:40 linux-ytaf audispd[829]: priority_boost_parser called with: 4
Feb 14 00:19:40 linux-ytaf audispd[829]: max_restarts_parser called with: 10
Feb 14 00:19:40 linux-ytaf audispd[829]: No plugins found, exiting
Feb 14 00:19:41 linux-ytaf auditctl[826]: No rules
Feb 14 00:19:41 linux-ytaf auditctl[826]: AUDIT_STATUS: enabled=1 flag=1 pid=825 rate_limit=0 backlog_limit=320 lost=0 backlog=1
Feb 14 00:19:43 linux-ytaf boot.apparmor[848]: Starting AppArmor ..done
Feb 14 00:19:43 linux-ytaf dbus-daemon[1010]: Unknown username "srvGeoClue" in message bus configuration file
Feb 14 00:19:44 linux-ytaf alsactl[1020]: /usr/sbin/alsactl: load_state:1683: Cannot open /var/lib/alsa/asound.state for reading: No such file or directory
Feb 14 00:19:44 linux-ytaf alsactl[1020]: Found hardware: "HDA-Intel" "Intel CougarPoint HDMI" "HDA:10ec0889,1043846b,00100004 HDA:80862805,80860101,00100000" "0x1043" "0x84dc"
Feb 14 00:19:44 linux-ytaf alsactl[1020]: Hardware is initialized using a generic method
Feb 14 00:19:44 linux-ytaf alsactl[1020]: Found hardware: "HDA-Intel" "Nvidia GPU 40 HDMI/DP" "HDA:10de0040,00000000,00100100" "0x0000" "0x0000"
Feb 14 00:19:44 linux-ytaf alsactl[1020]: Hardware is initialized using a generic method
Feb 14 00:19:44 linux-ytaf display-manager[1027]: /etc/vconsole.conf available
Feb 14 00:19:44 linux-ytaf display-manager[1027]: KEYMAP: de-latin1-nodeadkeys
Feb 14 00:19:44 linux-ytaf display-manager[1027]: Command: localectl set-keymap de-latin1-nodeadkeys
Feb 14 00:19:44 linux-ytaf dbus[1010]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service'
Feb 14 00:19:44 linux-ytaf dbus[1010]: [system] Successfully activated service 'org.freedesktop.locale1'
Feb 14 00:19:44 linux-ytaf display-manager[1027]: I: Using systemd /usr/share/systemd/kbd-model-map mapping
Feb 14 00:19:44 linux-ytaf smartd[1017]: smartd 6.2 2013-11-07 r3856 [x86_64-linux-4.1.15-8-default] (SUSE RPM)
Feb 14 00:19:44 linux-ytaf smartd[1017]: Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
Feb 14 00:19:44 linux-ytaf smartd[1017]: Opened configuration file /etc/smartd.conf
Feb 14 00:19:44 linux-ytaf smartd[1017]: Drive: DEVICESCAN, implied '-a' Directive on line 26 of file /etc/smartd.conf
Feb 14 00:19:44 linux-ytaf smartd[1017]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
Feb 14 00:19:44 linux-ytaf smartd[1017]: Device: /dev/sda, type changed from 'scsi' to 'sat'
Feb 14 00:19:44 linux-ytaf smartd[1017]: Device: /dev/sda [SAT], opened
Feb 14 00:19:44 linux-ytaf smartd[1017]: Device: /dev/sda [SAT], SAMSUNG SSD 830 Series, S/N:S0Z4NEAC906195, WWN:5-002538-043584d30, FW:CXM03B1Q, 256 GB
Feb 14 00:19:44 linux-ytaf smartd[1017]: Device: /dev/sda [SAT], found in smartd database: Samsung based SSDs
Feb 14 00:19:44 linux-ytaf avahi-daemon[1011]: Found user 'avahi' (UID 486) and group 'avahi' (GID 485).
Feb 14 00:19:44 linux-ytaf avahi-daemon[1011]: Successfully dropped root privileges.
Feb 14 00:19:44 linux-ytaf avahi-daemon[1011]: avahi-daemon 0.6.31 starting up.
Feb 14 00:19:44 linux-ytaf smartd[1017]: Device: /dev/sda [SAT], can't monitor Current_Pending_Sector count - no Attribute 197
Feb 14 00:19:44 linux-ytaf smartd[1017]: Device: /dev/sda [SAT], can't monitor Offline_Uncorrectable count - no Attribute 198
Feb 14 00:19:44 linux-ytaf smartd[1017]: Device: /dev/sda [SAT], is SMART capable. Adding to "monitor" list.
Feb 14 00:19:44 linux-ytaf avahi-daemon[1011]: Loading service file /etc/avahi/services/sftp-ssh.service.
Feb 14 00:19:44 linux-ytaf avahi-daemon[1011]: Loading service file /etc/avahi/services/ssh.service.
Feb 14 00:19:44 linux-ytaf avahi-daemon[1011]: Network interface enumeration completed.
Feb 14 00:19:44 linux-ytaf avahi-daemon[1011]: Registering HINFO record with values 'X86_64'/'LINUX'.
Feb 14 00:19:44 linux-ytaf avahi-daemon[1011]: Server startup complete. Host name is linux-ytaf.local. Local service cookie is 2059034429.
Feb 14 00:19:44 linux-ytaf avahi-daemon[1011]: Service "linux-ytaf" (/etc/avahi/services/ssh.service) successfully established.
Feb 14 00:19:44 linux-ytaf avahi-daemon[1011]: Service "linux-ytaf" (/etc/avahi/services/sftp-ssh.service) successfully established.
Feb 14 00:19:44 linux-ytaf smartd[1017]: Device: /dev/sdb, type changed from 'scsi' to 'sat'
Feb 14 00:19:44 linux-ytaf smartd[1017]: Device: /dev/sdb [SAT], opened
Feb 14 00:19:44 linux-ytaf smartd[1017]: Device: /dev/sdb [SAT], TOSHIBA HDWD110, S/N:Y5GDEMGFS, WWN:5-000039-fe7c5a79c, FW:MS2OA8J0, 1.00 TB
Feb 14 00:19:44 linux-ytaf smartd[1017]: Device: /dev/sdb [SAT], not found in smartd database.
Feb 14 00:19:46 linux-ytaf smartd[1017]: Device: /dev/sdb [SAT], is SMART capable. Adding to "monitor" list.
Feb 14 00:19:46 linux-ytaf smartd[1017]: Monitoring 2 ATA and 0 SCSI devices
Feb 14 00:19:46 linux-ytaf ModemManager[1013]: <info>  ModemManager (version 1.4.10) starting in system bus...
Feb 14 00:19:46 linux-ytaf dbus[1010]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Feb 14 00:19:47 linux-ytaf kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
Feb 14 00:19:47 linux-ytaf smartd[1017]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.SAMSUNG_SSD_830_Series-S0Z4NEAC906195.ata.state
Feb 14 00:19:47 linux-ytaf smartd[1017]: Device: /dev/sdb [SAT], state written to /var/lib/smartmontools/smartd.TOSHIBA_HDWD110-Y5GDEMGFS.ata.state
Feb 14 00:19:48 linux-ytaf kernel: nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
Feb 14 00:19:48 linux-ytaf polkitd[1097]: Started polkitd version 0.113
Feb 14 00:19:48 linux-ytaf polkitd[1097]: Loading rules from directory /etc/polkit-1/rules.d
Feb 14 00:19:48 linux-ytaf polkitd[1097]: Loading rules from directory /usr/share/polkit-1/rules.d
Feb 14 00:19:48 linux-ytaf polkitd[1097]: Finished loading, compiling and executing 3 rules
Feb 14 00:19:48 linux-ytaf dbus[1010]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Feb 14 00:19:48 linux-ytaf polkitd[1097]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
Feb 14 00:19:48 linux-ytaf kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Feb 14 00:19:48 linux-ytaf logger[1086]: /etc/init.d/xdm: No changes for /etc/X11/xdm/Xservers
Feb 14 00:19:48 linux-ytaf logger[1086]: /etc/init.d/xdm: No changes for /etc/X11/xdm/xdm-config
Feb 14 00:19:48 linux-ytaf sddm[1147]: Starting...
Feb 14 00:19:48 linux-ytaf sddm[1147]: Adding new display on vt 7 ...
Feb 14 00:19:48 linux-ytaf sddm[1147]: Display server starting...
Feb 14 00:19:48 linux-ytaf sddm[1147]: Running: /usr/bin/X -nolisten tcp -auth /run/sddm/{ca13106f-c3b6-4043-b5f2-ad33d711d0da} -background none -noreset -displayfd 17 vt7
Feb 14 00:19:48 linux-ytaf display-manager[1027]: Starting service sddm..done
Feb 14 00:19:49 linux-ytaf SuSEfirewall2[1176]: Firewall rules set to CLOSE.
Feb 14 00:19:49 linux-ytaf kernel: No iBFT detected.
Feb 14 00:19:50 linux-ytaf ModemManager[1013]: <info>  Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin
Feb 14 00:19:50 linux-ytaf kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Feb 14 00:19:51 linux-ytaf sddm[1147]: Display server started.
Feb 14 00:19:51 linux-ytaf sddm[1147]: Socket server starting...
Feb 14 00:19:51 linux-ytaf sddm[1147]: Socket server started.
Feb 14 00:19:51 linux-ytaf sddm[1147]: Greeter starting...
Feb 14 00:19:51 linux-ytaf sddm[1147]: Adding cookie to "/run/sddm/{ca13106f-c3b6-4043-b5f2-ad33d711d0da}"
Feb 14 00:19:51 linux-ytaf sddm-helper[1461]: [PAM] Starting...
Feb 14 00:19:51 linux-ytaf sddm-helper[1461]: [PAM] Authenticating...
Feb 14 00:19:51 linux-ytaf sddm-helper[1461]: [PAM] returning.
Feb 14 00:19:51 linux-ytaf sddm-helper[1461]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
Feb 14 00:19:51 linux-ytaf systemd[1463]: pam_unix(systemd-user:session): session opened for user sddm by (uid=0)
Feb 14 00:19:52 linux-ytaf sddm[1147]: Message received from greeter: Connect
Feb 14 00:19:53 linux-ytaf kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Feb 14 00:19:53 linux-ytaf kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Feb 14 00:19:53 linux-ytaf wickedd-dhcp4[1179]: eth0: Request to acquire DHCPv4 lease with UUID 16babf56-fa04-0300-a004-000005000000
Feb 14 00:19:53 linux-ytaf wickedd-dhcp6[1178]: eth0: Request to acquire DHCPv6 lease with UUID 16babf56-fa04-0300-a004-000006000000 in mode auto
Feb 14 00:19:53 linux-ytaf kernel: NET: Registered protocol family 17
Feb 14 00:19:54 linux-ytaf wickedd-dhcp4[1179]: eth0: Committed DHCPv4 lease with address 192.168.178.12 (lease time 864000 sec, renew in 432000 sec, rebind in 756000 sec)
Feb 14 00:19:54 linux-ytaf avahi-daemon[1011]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.178.12.
Feb 14 00:19:54 linux-ytaf avahi-daemon[1011]: New relevant interface eth0.IPv4 for mDNS.
Feb 14 00:19:54 linux-ytaf avahi-daemon[1011]: Registering new address record for 192.168.178.12 on eth0.IPv4.
Feb 14 00:19:54 linux-ytaf avahi-daemon[1011]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::ca60:ff:fe09:3876.
Feb 14 00:19:54 linux-ytaf avahi-daemon[1011]: New relevant interface eth0.IPv6 for mDNS.
Feb 14 00:19:54 linux-ytaf avahi-daemon[1011]: Registering new address record for fe80::ca60:ff:fe09:3876 on eth0.*.
Feb 14 00:19:54 linux-ytaf wickedd[1184]: eth0: Notified neighbours about IP address 192.168.178.12
Feb 14 00:19:55 MM-Home dbus[1010]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
Feb 14 00:19:55 MM-Home udisksd[1670]: udisks daemon version 2.1.6 starting
Feb 14 00:19:56 MM-Home udisksd[1670]: [86B blob data]
Feb 14 00:19:56 MM-Home udisksd[1670]: [86B blob data]
Feb 14 00:19:56 MM-Home dbus[1010]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Feb 14 00:19:56 MM-Home udisksd[1670]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Feb 14 00:19:56 MM-Home dbus[1010]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
Feb 14 00:19:57 MM-Home dbus[1010]: [system] Successfully activated service 'org.freedesktop.UPower'
Feb 14 00:20:06 MM-Home purge-kernels[1080]: /sbin/purge-kernels: Nothing to do.
Feb 14 00:20:08 MM-Home wicked[1186]: lo              up
Feb 14 00:20:08 MM-Home wicked[1186]: eth0            up
Feb 14 00:20:08 MM-Home echo[1709]: Starting mail service (Postfix)
Feb 14 00:20:08 MM-Home iscsiadm[1710]: iscsiadm: No records found
Feb 14 00:20:08 MM-Home SuSEfirewall2[1723]: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Feb 14 00:20:08 MM-Home SuSEfirewall2[1729]: using default zone 'ext' for interface eth0
Feb 14 00:20:08 MM-Home config_postfix[1717]: First configuration of postfix
Feb 14 00:20:08 MM-Home config_postfix[1717]: Reading /etc/sysconfig and updating the system...
Feb 14 00:20:08 MM-Home ntpd[1758]: ntpd 4.2.8p4@1.3265-o Thu Dec 17 05:32:52 UTC 2015 (1): Starting
Feb 14 00:20:08 MM-Home ntpd[1758]: Command line: /usr/sbin/ntpd -p /var/run/ntp/ntpd.pid -g -u ntp:ntp -c /etc/ntp.conf
Feb 14 00:20:09 MM-Home sntp[1812]: sntp 4.2.8p4@1.3265-o Thu Dec 17 05:32:29 UTC 2015 (1)
Feb 14 00:20:09 MM-Home sntp[1812]: kod_init_kod_db(): Cannot open KoD db file /var/db/ntp-kod: No such file or directory
Feb 14 00:20:09 MM-Home start-ntpd[1713]: Starting network time protocol daemon (NTPD)sntp 4.2.8p4@1.3265-o Thu Dec 17 05:32:29 UTC 2015 (1)
Feb 14 00:20:09 MM-Home start-ntpd[1713]: kod_init_kod_db(): Cannot open KoD db file /var/db/ntp-kod: No such file or directory
Feb 14 00:20:09 MM-Home sntp[1812]: 2016-02-14 00:20:09.096531 (-0100) -0.49828 +/- 0.393277 192.168.178.1 s3 no-leap
Feb 14 00:20:08 MM-Home start-ntpd[1713]: 2016-02-14 00:20:09.096531 (-0100) -0.49828 +/- 0.393277 192.168.178.1 s3 no-leap
Feb 14 00:20:08 MM-Home ntpd[1811]: proto: precision = 0.102 usec (-23)
Feb 14 00:20:08 MM-Home ntpd[1811]: switching logging to file /var/log/ntp
Feb 14 00:20:08 MM-Home SuSEfirewall2[1838]: Firewall rules successfully set
Feb 14 00:20:08 MM-Home /usr/sbin/start-ntpd[1840]: runtime configuration: server 192.168.178.1
Feb 14 00:20:09 MM-Home config_postfix[1717]: Setting up postfix local as MDA...
Feb 14 00:20:09 MM-Home config_postfix[1717]: Setting SPAM protection to "off"...
Feb 14 00:20:12 MM-Home sddm[1147]: Message received from greeter: Login
Feb 14 00:20:12 MM-Home sddm[1147]: Reading from "/usr/share/xsessions/plasma5.desktop"
Feb 14 00:20:12 MM-Home sddm[1147]: Session "/usr/share/xsessions/plasma5.desktop" selected, command: "/usr/bin/startkde"
Feb 14 00:20:12 MM-Home sddm-helper[1952]: [PAM] Starting...
Feb 14 00:20:12 MM-Home sddm-helper[1952]: [PAM] Authenticating...
Feb 14 00:20:12 MM-Home sddm-helper[1952]: [PAM] Preparing to converse...
Feb 14 00:20:12 MM-Home sddm-helper[1952]: [PAM] Conversation with 1 messages
Feb 14 00:20:12 MM-Home sddm-helper[1952]: [PAM] returning.
Feb 14 00:20:12 MM-Home sddm[1147]: Authenticated successfully
Feb 14 00:20:12 MM-Home sddm-helper[1952]: pam_unix(sddm:session): session opened for user marc by (uid=0)
Feb 14 00:20:12 MM-Home systemd[1953]: pam_unix(systemd-user:session): session opened for user marc by (uid=0)
Feb 14 00:20:12 MM-Home sddm-helper[1955]: Adding cookie to "/home/marc/.Xauthority"
Feb 14 00:20:12 MM-Home sddm[1147]: Session started
Feb 14 00:20:12 MM-Home sddm-helper[1461]: [PAM] Ended.
Feb 14 00:20:12 MM-Home sddm[1147]: Auth: sddm-helper exited successfully
Feb 14 00:20:12 MM-Home sddm[1147]: Greeter stopped.
Feb 14 00:20:12 MM-Home postfix/postfix-script[2011]: fatal: the Postfix mail system is not running
Feb 14 00:20:12 MM-Home postfix/postfix-script[2131]: starting the Postfix mail system
Feb 14 00:20:12 MM-Home postfix/master[2133]: daemon started -- version 2.11.6, configuration /etc/postfix
Feb 14 00:20:13 MM-Home cron[2150]: (CRON) INFO (RANDOM_DELAY will be scaled with factor 11% if used.)
Feb 14 00:20:13 MM-Home cron[2150]: (CRON) INFO (running with inotify support)
Feb 14 00:20:21 MM-Home dbus[1010]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Feb 14 00:20:21 MM-Home org.kde.powerdevil.backlighthelper[1010]: powerdevil: no kernel backlight interface found
Feb 14 00:20:21 MM-Home dbus[1010]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Feb 14 00:20:22 MM-Home polkitd[1097]: Registered Authentication Agent for unix-session:2 (system bus name :1.37 [/usr/lib64/libexec/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale de_DE.UTF-8)
Feb 14 00:20:22 MM-Home dbus[1010]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service'
Feb 14 00:20:23 MM-Home dbus[1010]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Feb 14 00:20:23 MM-Home rtkit-daemon[2252]: Successfully called chroot.
Feb 14 00:20:23 MM-Home rtkit-daemon[2252]: Successfully dropped privileges.
Feb 14 00:20:23 MM-Home rtkit-daemon[2252]: Successfully limited resources.
Feb 14 00:20:23 MM-Home rtkit-daemon[2252]: Running.
Feb 14 00:20:23 MM-Home rtkit-daemon[2252]: Canary thread running.
Feb 14 00:20:23 MM-Home rtkit-daemon[2252]: Watchdog thread running.
Feb 14 00:20:23 MM-Home rtkit-daemon[2252]: Successfully made thread 2251 of process 2251 (/usr/bin/pulseaudio) owned by 'marc' high priority at nice level -11.
Feb 14 00:20:23 MM-Home rtkit-daemon[2252]: Supervising 1 threads of 1 processes of 1 users.
Feb 14 00:20:26 MM-Home rtkit-daemon[2252]: Supervising 1 threads of 1 processes of 1 users.
Feb 14 00:20:26 MM-Home rtkit-daemon[2252]: Successfully made thread 2277 of process 2251 (/usr/bin/pulseaudio) owned by 'marc' RT at priority 5.
Feb 14 00:20:26 MM-Home rtkit-daemon[2252]: Supervising 2 threads of 1 processes of 1 users.
Feb 14 00:20:26 MM-Home rtkit-daemon[2252]: Supervising 2 threads of 1 processes of 1 users.
Feb 14 00:20:26 MM-Home rtkit-daemon[2252]: Successfully made thread 2278 of process 2251 (/usr/bin/pulseaudio) owned by 'marc' RT at priority 5.
Feb 14 00:20:26 MM-Home rtkit-daemon[2252]: Supervising 3 threads of 1 processes of 1 users.
Feb 14 00:20:26 MM-Home rtkit-daemon[2252]: Supervising 3 threads of 1 processes of 1 users.
Feb 14 00:20:26 MM-Home rtkit-daemon[2252]: Successfully made thread 2279 of process 2251 (/usr/bin/pulseaudio) owned by 'marc' RT at priority 5.
Feb 14 00:20:26 MM-Home rtkit-daemon[2252]: Supervising 4 threads of 1 processes of 1 users.
Feb 14 00:20:26 MM-Home dbus[1010]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Feb 14 00:20:26 MM-Home pulseaudio[2251]: [pulseaudio] authkey.c: Failed to open cookie file '/home/marc/.config/pulse/cookie': Datei oder Verzeichnis nicht gefunden
Feb 14 00:20:26 MM-Home pulseaudio[2251]: [pulseaudio] authkey.c: Failed to load authentication key '/home/marc/.config/pulse/cookie': Datei oder Verzeichnis nicht gefunden
Feb 14 00:20:26 MM-Home pulseaudio[2251]: [pulseaudio] authkey.c: Failed to open cookie file '/home/marc/.pulse-cookie': Datei oder Verzeichnis nicht gefunden
Feb 14 00:20:26 MM-Home pulseaudio[2251]: [pulseaudio] authkey.c: Failed to load authentication key '/home/marc/.pulse-cookie': Datei oder Verzeichnis nicht gefunden
Feb 14 00:20:27 MM-Home rtkit-daemon[2252]: Successfully made thread 2282 of process 2282 (/usr/bin/pulseaudio) owned by 'marc' high priority at nice level -11.
Feb 14 00:20:27 MM-Home rtkit-daemon[2252]: Supervising 5 threads of 2 processes of 1 users.
Feb 14 00:20:27 MM-Home pulseaudio[2282]: [pulseaudio] pid.c: Daemon already running.
Feb 14 00:20:27 MM-Home bluetoothd[2280]: Bluetooth daemon 5.35
Feb 14 00:20:27 MM-Home dbus[1010]: [system] Successfully activated service 'org.bluez'
Feb 14 00:20:27 MM-Home bluetoothd[2280]: Starting SDP server
Feb 14 00:20:27 MM-Home kernel: Bluetooth: Core ver 2.20
Feb 14 00:20:27 MM-Home kernel: NET: Registered protocol family 31
Feb 14 00:20:27 MM-Home kernel: Bluetooth: HCI device and connection manager initialized
Feb 14 00:20:27 MM-Home kernel: Bluetooth: HCI socket layer initialized
Feb 14 00:20:27 MM-Home kernel: Bluetooth: L2CAP socket layer initialized
Feb 14 00:20:27 MM-Home kernel: Bluetooth: SCO socket layer initialized
Feb 14 00:20:27 MM-Home dbus[1010]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Feb 14 00:20:27 MM-Home bluetoothd[2280]: Bluetooth management interface 1.9 initialized
Feb 14 00:20:27 MM-Home kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Feb 14 00:20:27 MM-Home kernel: Bluetooth: BNEP filters: protocol multicast
Feb 14 00:20:27 MM-Home kernel: Bluetooth: BNEP socket layer initialized
Feb 14 00:20:27 MM-Home dbus[1010]: [system] Successfully activated service 'org.freedesktop.hostname1'
Feb 14 00:20:28 MM-Home dbus[1010]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service'
Feb 14 00:20:28 MM-Home PackageKit[2296]: daemon start
Feb 14 00:20:28 MM-Home dbus[1010]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Feb 14 00:20:29 MM-Home PackageKit[2296]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 00:20:29 MM-Home PackageKit[2296]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 00:20:29 MM-Home PackageKit[2296]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 00:20:29 MM-Home PackageKit[2296]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 00:20:33 MM-Home PackageKit[2296]: refresh-cache transaction /1_adcaaeea from uid 1000 finished with success after 3932ms
Feb 14 00:20:33 MM-Home PackageKit[2296]: refresh-cache transaction /2_cbeacdac from uid 1000 finished with success after 282ms
Feb 14 00:20:35 MM-Home PackageKit[2296]: get-updates transaction /3_deccbeac from uid 1000 finished with success after 1447ms
Feb 14 00:20:36 MM-Home PackageKit[2296]: get-updates transaction /4_abcbaede from uid 1000 finished with success after 829ms
Feb 14 00:20:53 MM-Home PackageKit[2296]: daemon quit
Feb 14 00:20:53 MM-Home packagekitd[2296]: (packagekitd:2296): GLib-CRITICAL **: Source ID 6 was not found when attempting to remove it
Feb 14 00:22:24 MM-Home kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=fe80:0000:0000:0000:ca60:00ff:fe09:3876 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=94 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=54 
Feb 14 00:22:25 MM-Home kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=fe80:0000:0000:0000:ca60:00ff:fe09:3876 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=94 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=54 
Feb 14 00:22:27 MM-Home kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=fe80:0000:0000:0000:ca60:00ff:fe09:3876 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=94 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=54 
Feb 14 00:22:31 MM-Home kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=fe80:0000:0000:0000:ca60:00ff:fe09:3876 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=94 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=54 
Feb 14 00:22:39 MM-Home kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=fe80:0000:0000:0000:ca60:00ff:fe09:3876 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=94 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=54 
Feb 14 00:22:47 MM-Home kernel: nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
Feb 14 00:22:55 MM-Home kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=fe80:0000:0000:0000:ca60:00ff:fe09:3876 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=94 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=54 
Feb 14 00:23:27 MM-Home kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=fe80:0000:0000:0000:ca60:00ff:fe09:3876 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=94 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=54 
Feb 14 00:23:28 MM-Home kernel: fuse init (API version 7.23)
Feb 14 00:24:12 MM-Home org.kde.kwalletd5[2075]: kwalletd5 started
Feb 14 00:24:13 MM-Home org.kde.kwalletd5[2075]: Migration agent starting...
Feb 14 00:24:13 MM-Home org.kde.kwalletd5[2075]: kwalletd not started. Attempting start...
Feb 14 00:24:13 MM-Home org.kde.kwalletd5[2075]: The kwalletd service has been registered
Feb 14 00:24:13 MM-Home org.kde.kwalletd5[2075]: Old wallet is empty. No need to migrate.
Feb 14 00:24:13 MM-Home org.kde.kwalletd5[2075]: Migration agent stop.
Feb 14 00:24:31 MM-Home kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=fe80:0000:0000:0000:ca60:00ff:fe09:3876 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=94 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=54 
Feb 14 00:25:37 MM-Home dbus[1010]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service'
Feb 14 00:25:38 MM-Home accounts-daemon[2490]: started daemon version 0.6.40
Feb 14 00:25:38 MM-Home dbus[1010]: [system] Successfully activated service 'org.freedesktop.Accounts'
Feb 14 00:26:08 MM-Home polkitd[1097]: Operator of unix-session:2 successfully authenticated as unix-user:root to gain TEMPORARY authorization for action org.freedesktop.accounts.user-administration for system-bus-name::1.55 [/usr/bin/systemsettings5] (owned by unix-user:marc)
Feb 14 00:26:08 MM-Home accounts-daemon[2490]: request by system-bus-name::1.55 [/usr/bin/systemsettings5 pid:2392 uid:1000]: uncache user 'marc'
Feb 14 00:26:08 MM-Home accounts-daemon[2490]: request by system-bus-name::1.55 [/usr/bin/systemsettings5 pid:2392 uid:1000]: cache user 'marc'
Feb 14 00:26:08 MM-Home accounts-daemon[2490]: request by system-bus-name::1.55 [/usr/bin/systemsettings5 pid:2392 uid:1000]: change account type of user 'marc' (1000) to 1
Feb 14 00:26:08 MM-Home usermod[2496]: add 'marc' to group 'wheel'
Feb 14 00:26:08 MM-Home usermod[2496]: add 'marc' to group 'users'
Feb 14 00:26:08 MM-Home accounts-daemon[2490]: request by system-bus-name::1.55 [/usr/bin/systemsettings5 pid:2392 uid:1000]: disable automatic login for user 'marc' (1000)
Feb 14 00:26:39 MM-Home kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=fe80:0000:0000:0000:ca60:00ff:fe09:3876 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=94 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=54 
Feb 14 00:30:01 MM-Home cron[2688]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 00:30:01 MM-Home systemd[2689]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 00:30:28 MM-Home dbus[1010]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Feb 14 00:30:28 MM-Home dbus[1010]: [system] Successfully activated service 'org.opensuse.Snapper'
Feb 14 00:30:28 MM-Home kernel: BTRFS info (device sdb3): relocating block group 6471811072 flags 1
Feb 14 00:30:29 MM-Home kernel: BTRFS info (device sdb3): relocating block group 7545552896 flags 1
Feb 14 00:30:29 MM-Home kernel: BTRFS info (device sdb3): found 1 extents
Feb 14 00:30:30 MM-Home kernel: BTRFS info (device sdb3): found 1 extents
Feb 14 00:30:30 MM-Home kernel: BTRFS info (device sdb3): relocating block group 8619294720 flags 1
Feb 14 00:30:31 MM-Home kernel: BTRFS info (device sdb3): found 1 extents
Feb 14 00:30:31 MM-Home kernel: BTRFS info (device sdb3): found 1 extents
Feb 14 00:30:31 MM-Home kernel: BTRFS info (device sdb3): relocating block group 9693036544 flags 1
Feb 14 00:30:32 MM-Home kernel: BTRFS info (device sdb3): found 1 extents
Feb 14 00:30:32 MM-Home kernel: BTRFS info (device sdb3): found 1 extents
Feb 14 00:30:32 MM-Home kernel: BTRFS info (device sdb3): relocating block group 10766778368 flags 1
Feb 14 00:30:33 MM-Home kernel: BTRFS info (device sdb3): found 1 extents
Feb 14 00:30:33 MM-Home kernel: BTRFS info (device sdb3): found 1 extents
Feb 14 00:30:34 MM-Home kernel: BTRFS info (device sdb3): relocating block group 11840520192 flags 1
Feb 14 00:30:34 MM-Home kernel: BTRFS info (device sdb3): found 1 extents
Feb 14 00:30:34 MM-Home kernel: BTRFS info (device sdb3): found 1 extents
Feb 14 00:30:35 MM-Home kernel: BTRFS info (device sdb3): relocating block group 12914262016 flags 1
Feb 14 00:30:35 MM-Home kernel: BTRFS info (device sdb3): found 1 extents
Feb 14 00:30:35 MM-Home kernel: BTRFS info (device sdb3): found 1 extents
Feb 14 00:30:36 MM-Home kernel: BTRFS info (device sdb3): relocating block group 4194304 flags 4
Feb 14 00:30:36 MM-Home kernel: BTRFS info (device sdb3): relocating block group 0 flags 2
Feb 14 00:30:36 MM-Home kernel: BTRFS info (device sdb3): relocating block group 20971520 flags 34
Feb 14 00:30:36 MM-Home kernel: BTRFS info (device sdb3): relocating block group 15061745664 flags 34
Feb 14 00:30:37 MM-Home kernel: BTRFS info (device sdb3): relocating block group 15095300096 flags 34
Feb 14 00:30:37 MM-Home kernel: BTRFS info (device sdb3): relocating block group 15128854528 flags 34
Feb 14 00:30:37 MM-Home kernel: BTRFS info (device sdb3): relocating block group 15162408960 flags 34
Feb 14 00:30:55 MM-Home kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=fe80:0000:0000:0000:ca60:00ff:fe09:3876 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=94 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=54 
Feb 14 00:31:15 MM-Home CRON[2688]: pam_unix(crond:session): session closed for user root
Feb 14 00:31:15 MM-Home systemd[2690]: pam_unix(systemd-user:session): session closed for user root
Feb 14 00:35:56 MM-Home su[3167]: (to root) marc on pts/1
Feb 14 00:35:56 MM-Home su[3167]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 00:35:56 MM-Home su[3167]: pam_unix(su:session): session closed for user root
Feb 14 00:35:56 MM-Home su[3172]: (to root) marc on pts/1
Feb 14 00:35:56 MM-Home su[3172]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 00:36:22 MM-Home dbus[1010]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Feb 14 00:36:22 MM-Home dbus[1010]: [system] Successfully activated service 'org.opensuse.Snapper'
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PFIFO][0000:02:00.0] read fault at 0x0003341000 [PTE] from GR/GPC0/T1_0 on channel 0x007fa1a000 [X[1158]]
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PFIFO][0000:02:00.0] PGRAPH engine fault on channel 2, recovering...
Feb 14 00:36:23 MM-Home kernel: nouveau E[  PGRAPH][0000:02:00.0] TRAP ch 2 [0x007fa1a000 X[1158]]
Feb 14 00:36:23 MM-Home kernel: nouveau E[  PGRAPH][0000:02:00.0] GPC0/TPC0/TEX: 0x80000049
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] chid 1 mthd 0x0094 data 0xf0000000 0x00007094 0x00000000
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] chid 2 mthd 0x0094 data 0xf0000000 0x00007094 0x00000000
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] chid 1 mthd 0x00c0 data 0xffff00fe 0x100070c0 0x00000000
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] chid 2 mthd 0x00c0 data 0xffff00fe 0x100070c0 0x00000000
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] chid 0 mthd 0x048c data 0xf0000001 0x0000748c 0x00000000
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] chid 0 mthd 0x0080 data 0x00000000 0x10005080 0x00000021
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0080: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0084: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0088: 0xf0000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 0:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0180: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0184: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0188: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0190: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 1:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a0: 0x00000001              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a4: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a8: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01b0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 2:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c4: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c8: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01d0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 0:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0200: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0204: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0208: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0210: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 1:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0220: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0224: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0228: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0230: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 2:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0240: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0244: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0248: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0250: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 3:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0260: 0x00000102              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0264: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0268: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0270: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 4:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0280: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0284: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0288: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0290: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 5:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a4: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a8: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02b0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 6:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c4: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c8: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02d0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 7:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e4: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e8: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02f0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 0:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0300: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0304: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0308: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0310: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 1:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0320: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0324: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0328: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0330: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 2:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0340: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0344: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0348: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0350: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 3:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0360: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0364: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0368: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0370: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 0:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0400: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0404: 0x00000009              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0408: 0x31ec6000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x040c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0410: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0414: 0x044108c0              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0418: 0x000500af              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x041c: 0x002301c7              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0420: 0x043d0857              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0424: 0x00000001              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0428: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x042c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0430: 0xffffff00              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0434: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0438: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0440: 0x83000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0444: 0x00000410              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0448: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x044c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0450: 0x08c30ac0              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0454: 0x00200000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0458: 0x08c30ac0              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x045c: 0xf0000001              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0460: 0x000b2200              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0468: 0x04380e10              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x046c: 0x0000e104              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0470: 0x0000cf00              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0474: 0xffff00fe              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x047c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0480: 0x05000000 -> 0x85000000
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0484: 0x0002ecb0              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0488: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x048c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0490: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0494: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0498: 0x00040000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04a0: 0x00000002              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b0: 0x00000780              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b8: 0x041a0690              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04bc: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c0: 0x041a0690              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c4: 0x041a0690              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c8: 0x041a0690              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d0: 0x00000311              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d4: 0x00000100              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e4: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e8: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04ec: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f0: 0x00010000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f4: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f8: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04fc: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0500: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0504: 0x00010000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0508: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x050c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0510: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0514: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0518: 0x00010000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x051c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0520: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0524: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x052c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0530: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x054c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0550: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0554: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0558: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x055c: 0x00000002              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 1:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0700: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0704: 0x00000011              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0708: 0x33ec6000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x070c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0710: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0714: 0x04650898              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0718: 0x0004002b              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x071c: 0x002800bf              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0720: 0x0460083f              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0724: 0x00000001              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0728: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x072c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0730: 0xffffff00              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0734: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0738: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0740: 0x83000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0744: 0x00000430              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0748: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x074c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0750: 0x08d9ee20              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0754: 0x00200000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0758: 0x08d9ee20              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x075c: 0xf0000001              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0760: 0x000b2200              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0768: 0x04380e10              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x076c: 0x0000e104              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0770: 0x0000cf00              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0774: 0xffff00fe              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x077c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0780: 0x85000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0784: 0x0002ecf0              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0788: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x078c: 0xf0000001              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0790: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0794: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0798: 0x00040000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07a0: 0x00000002              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b8: 0x04380780              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07bc: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c0: 0x04380780              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c4: 0x04380780              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c8: 0x04380780              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d0: 0x00000311              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d4: 0x00000100              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e4: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e8: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07ec: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f0: 0x00010000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f4: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f8: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07fc: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0800: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0804: 0x00010000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0808: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x080c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0810: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0814: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0818: 0x00010000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x081c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0820: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0824: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x082c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0830: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x084c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0850: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0854: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0858: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x085c: 0x00000002              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 2:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a00: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a04: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a08: 0x21ec4000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a0c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a10: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a14: 0x00050008              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a18: 0x00000001              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a1c: 0x00010003              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a20: 0x00030004              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a24: 0x00000001              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a28: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a2c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a30: 0xffffff40              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a34: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a38: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a40: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a44: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a48: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a4c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a50: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a54: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a58: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a5c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a60: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a68: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a6c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a70: 0x0000e900              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a74: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a7c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a80: 0x05000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a84: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a88: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a8c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a90: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a94: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a98: 0x00040000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aa0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab8: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0abc: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac4: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac8: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad0: 0x00110300              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad4: 0x00001100              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae4: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae8: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aec: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af0: 0x00010000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af4: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af8: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0afc: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b00: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b04: 0x00010000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b08: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b0c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b10: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b14: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b18: 0x00010000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b1c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b20: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b24: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b2c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b30: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b4c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b50: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b54: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b58: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b5c: 0x00000001              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 3:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d00: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d04: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d08: 0x21ec4000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d0c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d10: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d14: 0x00050008              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d18: 0x00000001              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d1c: 0x00010003              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d20: 0x00030004              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d24: 0x00000001              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d28: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d2c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d30: 0xffffff40              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d34: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d38: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d40: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d44: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d48: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d4c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d50: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d54: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d58: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d5c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d60: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d68: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d6c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d70: 0x0000e900              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d74: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d7c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d80: 0x05000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d84: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d88: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d8c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d90: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d94: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d98: 0x00040000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0da0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db8: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dbc: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc4: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc8: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd0: 0x00110300              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd4: 0x00001100              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de4: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de8: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dec: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df0: 0x00010000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df4: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df8: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dfc: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e00: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e04: 0x00010000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e08: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e0c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e10: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e14: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e18: 0x00010000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e1c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e20: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e24: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e2c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e30: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e4c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e50: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e54: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e58: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e5c: 0x00000001              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] chid 0 mthd 0x0080 data 0x00000000 0x10005080 0x00000021
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0080: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0084: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0088: 0xf0000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 0:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0180: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0184: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0188: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0190: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 1:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a0: 0x00000001              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a4: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a8: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01b0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 2:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c4: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c8: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01d0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 0:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0200: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0204: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0208: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0210: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 1:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0220: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0224: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0228: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0230: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 2:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0240: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0244: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0248: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0250: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 3:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0260: 0x00000102              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0264: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0268: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0270: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 4:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0280: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0284: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0288: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0290: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 5:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a4: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a8: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02b0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 6:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c4: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c8: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02d0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 7:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e4: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e8: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02f0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 0:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0300: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0304: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0308: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0310: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 1:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0320: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0324: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0328: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0330: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 2:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0340: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0344: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0348: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0350: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 3:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0360: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0364: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0368: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0370: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 0:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0400: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0404: 0x00000009              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0408: 0x31ec6000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x040c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0410: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0414: 0x044108c0              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0418: 0x000500af              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x041c: 0x002301c7              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0420: 0x043d0857              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0424: 0x00000001              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0428: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x042c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0430: 0xffffff00              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0434: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0438: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0440: 0x83000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0444: 0x00000410              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0448: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x044c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0450: 0x08c30ac0              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0454: 0x00200000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0458: 0x08c30ac0              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x045c: 0xf0000001              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0460: 0x000b2200              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0468: 0x04380e10              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x046c: 0x0000e104              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0470: 0x0000cf00              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0474: 0xffff00fe              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x047c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0480: 0x05000000 -> 0x85000000
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0484: 0x0002ecb0              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0488: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x048c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0490: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0494: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0498: 0x00040000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04a0: 0x00000002              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b0: 0x00000780              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b8: 0x041a0690              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04bc: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c0: 0x041a0690              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c4: 0x041a0690              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c8: 0x041a0690              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d0: 0x00000311              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d4: 0x00000100              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e4: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e8: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04ec: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f0: 0x00010000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f4: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f8: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04fc: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0500: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0504: 0x00010000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0508: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x050c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0510: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0514: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0518: 0x00010000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x051c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0520: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0524: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x052c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0530: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x054c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0550: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0554: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0558: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x055c: 0x00000002              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 1:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0700: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0704: 0x00000011              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0708: 0x33ec6000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x070c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0710: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0714: 0x04650898              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0718: 0x0004002b              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x071c: 0x002800bf              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0720: 0x0460083f              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0724: 0x00000001              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0728: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x072c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0730: 0xffffff00              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0734: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0738: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0740: 0x83000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0744: 0x00000430              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0748: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x074c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0750: 0x08d9ee20              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0754: 0x00200000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0758: 0x08d9ee20              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x075c: 0xf0000001              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0760: 0x000b2200              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0768: 0x04380e10              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x076c: 0x0000e104              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0770: 0x0000cf00              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0774: 0xffff00fe              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x077c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0780: 0x85000000 -> 0x05000000
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0784: 0x0002ecf0              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0788: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x078c: 0xf0000001 -> 0x00000000
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0790: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0794: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0798: 0x00040000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07a0: 0x00000002              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b8: 0x04380780              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07bc: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c0: 0x04380780              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c4: 0x04380780              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c8: 0x04380780              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d0: 0x00000311              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d4: 0x00000100              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e4: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e8: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07ec: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f0: 0x00010000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f4: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f8: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07fc: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0800: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0804: 0x00010000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0808: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x080c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0810: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0814: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0818: 0x00010000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x081c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0820: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0824: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x082c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0830: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x084c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0850: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0854: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0858: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x085c: 0x00000002              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 2:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a00: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a04: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a08: 0x21ec4000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a0c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a10: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a14: 0x00050008              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a18: 0x00000001              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a1c: 0x00010003              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a20: 0x00030004              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a24: 0x00000001              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a28: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a2c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a30: 0xffffff40              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a34: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a38: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a40: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a44: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a48: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a4c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a50: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a54: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a58: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a5c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a60: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a68: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a6c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a70: 0x0000e900              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a74: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a7c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a80: 0x05000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a84: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a88: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a8c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a90: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a94: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a98: 0x00040000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aa0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab8: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0abc: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac4: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac8: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad0: 0x00110300              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad4: 0x00001100              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae4: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae8: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aec: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af0: 0x00010000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af4: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af8: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0afc: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b00: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b04: 0x00010000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b08: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b0c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b10: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b14: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b18: 0x00010000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b1c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b20: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b24: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b2c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b30: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b4c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b50: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b54: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b58: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b5c: 0x00000001              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 3:
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d00: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d04: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d08: 0x21ec4000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d0c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d10: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d14: 0x00050008              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d18: 0x00000001              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d1c: 0x00010003              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d20: 0x00030004              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d24: 0x00000001              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d28: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d2c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d30: 0xffffff40              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d34: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d38: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d40: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d44: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d48: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d4c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d50: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d54: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d58: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d5c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d60: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d68: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d6c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d70: 0x0000e900              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d74: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d7c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d80: 0x05000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d84: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d88: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d8c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d90: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d94: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d98: 0x00040000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0da0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db8: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dbc: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc4: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc8: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd0: 0x00110300              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd4: 0x00001100              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de0: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de4: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de8: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dec: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df0: 0x00010000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df4: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df8: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dfc: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e00: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e04: 0x00010000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e08: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e0c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e10: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e14: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e18: 0x00010000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e1c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e20: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e24: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e2c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e30: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e4c: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e50: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e54: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e58: 0x00000000              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e5c: 0x00000001              
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PFIFO][0000:02:00.0] PBDMA0: SIGNATURE
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PFIFO][0000:02:00.0] PBDMA0: ch 1 [DRM] subc 0 mthd 0x0000 data 0x00000000
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PFIFO][0000:02:00.0] PBDMA0: SIGNATURE
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PFIFO][0000:02:00.0] PBDMA0: ch 1 [DRM] subc 0 mthd 0x0000 data 0x00000000
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PFIFO][0000:02:00.0] PBDMA0: GPPTR PBENTRY SIGNATURE
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PFIFO][0000:02:00.0] PBDMA0: ch 1 [DRM] subc 0 mthd 0x0000 data 0x00000000
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PFIFO][0000:02:00.0] PBDMA0: GPPTR SIGNATURE
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PFIFO][0000:02:00.0] PBDMA0: ch 1 [DRM] subc 0 mthd 0x0000 data 0x00000000
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PFIFO][0000:02:00.0] PBDMA0: GPPTR SIGNATURE
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PFIFO][0000:02:00.0] PBDMA0: ch 1 [DRM] subc 0 mthd 0x0000 data 0x00000000
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PFIFO][0000:02:00.0] PBDMA0: GPPTR SIGNATURE
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PFIFO][0000:02:00.0] PBDMA0: ch 1 [DRM] subc 0 mthd 0x0000 data 0x00000000
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PFIFO][0000:02:00.0] PBDMA0: SIGNATURE
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PFIFO][0000:02:00.0] PBDMA0: ch 1 [DRM] subc 0 mthd 0x0000 data 0x00000000
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PFIFO][0000:02:00.0] PBDMA0: SIGNATURE
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PFIFO][0000:02:00.0] PBDMA0: ch 1 [DRM] subc 0 mthd 0x0000 data 0x00000000
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PFIFO][0000:02:00.0] PBDMA0: SIGNATURE
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PFIFO][0000:02:00.0] PBDMA0: ch 1 [DRM] subc 0 mthd 0x0000 data 0x00000000
Feb 14 00:36:23 MM-Home kernel: nouveau E[   PFIFO][0000:02:00.0] read fault at 0xf008787000 [VA_LIMIT_VIOLATION] from PBDMA0/HOST on channel 0x007fba2000 [unknown]
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] chid 0 mthd 0x078c data 0xf0000001 0x1000778c 0x00000000
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] chid 0 mthd 0x0080 data 0x00000000 0x10005080 0x00000021
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0080: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0084: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0088: 0xf0000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 0:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0180: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0184: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0188: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0190: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 1:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a0: 0x00000001              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a4: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a8: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01b0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 2:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c4: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c8: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01d0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 0:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0200: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0204: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0208: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0210: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 1:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0220: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0224: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0228: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0230: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 2:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0240: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0244: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0248: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0250: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 3:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0260: 0x00000102              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0264: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0268: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0270: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 4:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0280: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0284: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0288: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0290: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 5:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a4: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a8: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02b0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 6:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c4: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c8: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02d0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 7:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e4: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e8: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02f0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 0:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0300: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0304: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0308: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0310: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 1:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0320: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0324: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0328: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0330: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 2:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0340: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0344: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0348: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0350: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 3:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0360: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0364: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0368: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0370: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 0:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0400: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0404: 0x00000009              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0408: 0x31ec6000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x040c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0410: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0414: 0x044108c0              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0418: 0x000500af              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x041c: 0x002301c7              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0420: 0x043d0857              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0424: 0x00000001              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0428: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x042c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0430: 0xffffff00              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0434: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0438: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0440: 0x83000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0444: 0x00000410              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0448: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x044c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0450: 0x08c30ac0              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0454: 0x00200000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0458: 0x08c30ac0              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x045c: 0xf0000001              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0460: 0x000b2200              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0468: 0x04380e10              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x046c: 0x0000e104              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0470: 0x0000cf00              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0474: 0xffff00fe              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x047c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0480: 0x05000000 -> 0x85000000
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0484: 0x0002ecb0              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0488: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x048c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0490: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0494: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0498: 0x00040000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04a0: 0x00000002              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b0: 0x00000780              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b8: 0x041a0690              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04bc: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c0: 0x041a0690              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c4: 0x041a0690              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c8: 0x041a0690              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d0: 0x00000311              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d4: 0x00000100              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e4: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e8: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04ec: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f0: 0x00010000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f4: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f8: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04fc: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0500: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0504: 0x00010000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0508: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x050c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0510: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0514: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0518: 0x00010000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x051c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0520: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0524: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x052c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0530: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x054c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0550: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0554: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0558: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x055c: 0x00000002              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 1:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0700: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0704: 0x00000011              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0708: 0x33ec6000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x070c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0710: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0714: 0x04650898              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0718: 0x0004002b              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x071c: 0x002800bf              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0720: 0x0460083f              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0724: 0x00000001              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0728: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x072c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0730: 0xffffff00              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0734: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0738: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0740: 0x83000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0744: 0x00000430              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0748: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x074c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0750: 0x08d9ee20              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0754: 0x00200000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0758: 0x08d9ee20              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x075c: 0xf0000001              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0760: 0x000b2200              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0768: 0x04380e10              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x076c: 0x0000e104              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0770: 0x0000cf00              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0774: 0xffff00fe              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x077c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0780: 0x85000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0784: 0x0002ecf0              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0788: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x078c: 0xf0000001 -> 0x00000000
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0790: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0794: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0798: 0x00040000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07a0: 0x00000002              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b8: 0x04380780              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07bc: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c0: 0x04380780              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c4: 0x04380780              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c8: 0x04380780              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d0: 0x00000311              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d4: 0x00000100              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e4: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e8: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07ec: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f0: 0x00010000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f4: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f8: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07fc: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0800: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0804: 0x00010000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0808: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x080c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0810: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0814: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0818: 0x00010000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x081c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0820: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0824: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x082c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0830: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x084c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0850: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0854: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0858: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x085c: 0x00000002              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 2:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a00: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a04: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a08: 0x21ec4000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a0c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a10: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a14: 0x00050008              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a18: 0x00000001              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a1c: 0x00010003              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a20: 0x00030004              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a24: 0x00000001              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a28: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a2c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a30: 0xffffff40              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a34: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a38: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a40: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a44: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a48: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a4c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a50: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a54: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a58: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a5c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a60: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a68: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a6c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a70: 0x0000e900              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a74: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a7c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a80: 0x05000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a84: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a88: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a8c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a90: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a94: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a98: 0x00040000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aa0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab8: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0abc: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac4: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac8: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad0: 0x00110300              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad4: 0x00001100              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae4: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae8: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aec: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af0: 0x00010000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af4: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af8: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0afc: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b00: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b04: 0x00010000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b08: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b0c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b10: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b14: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b18: 0x00010000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b1c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b20: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b24: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b2c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b30: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b4c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b50: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b54: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b58: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b5c: 0x00000001              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 3:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d00: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d04: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d08: 0x21ec4000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d0c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d10: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d14: 0x00050008              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d18: 0x00000001              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d1c: 0x00010003              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d20: 0x00030004              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d24: 0x00000001              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d28: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d2c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d30: 0xffffff40              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d34: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d38: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d40: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d44: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d48: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d4c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d50: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d54: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d58: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d5c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d60: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d68: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d6c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d70: 0x0000e900              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d74: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d7c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d80: 0x05000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d84: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d88: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d8c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d90: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d94: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d98: 0x00040000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0da0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db8: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dbc: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc4: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc8: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd0: 0x00110300              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd4: 0x00001100              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de4: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de8: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dec: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df0: 0x00010000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df4: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df8: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dfc: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e00: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e04: 0x00010000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e08: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e0c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e10: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e14: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e18: 0x00010000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e1c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e20: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e24: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e2c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e30: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e4c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e50: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e54: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e58: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e5c: 0x00000001              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] chid 0 mthd 0x0080 data 0x00000000 0x10005080 0x00002021
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0080: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0084: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0088: 0xf0000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 0:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0180: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0184: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0188: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0190: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 1:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a0: 0x00000001              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a4: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a8: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01b0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 2:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c4: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c8: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01d0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 0:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0200: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0204: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0208: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0210: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 1:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0220: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0224: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0228: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0230: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 2:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0240: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0244: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0248: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0250: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 3:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0260: 0x00000102              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0264: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0268: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0270: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 4:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0280: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0284: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0288: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0290: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 5:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a4: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a8: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02b0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 6:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c4: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c8: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02d0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 7:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e4: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e8: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02f0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 0:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0300: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0304: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0308: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0310: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 1:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0320: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0324: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0328: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0330: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 2:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0340: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0344: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0348: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0350: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 3:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0360: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0364: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0368: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0370: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 0:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0400: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0404: 0x00000009              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0408: 0x31ec6000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x040c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0410: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0414: 0x044108c0              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0418: 0x000500af              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x041c: 0x002301c7              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0420: 0x043d0857              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0424: 0x00000001              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0428: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x042c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0430: 0xffffff00              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0434: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0438: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0440: 0x83000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0444: 0x00000410              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0448: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x044c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0450: 0x08c30ac0              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0454: 0x00200000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0458: 0x08c30ac0              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x045c: 0xf0000001              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0460: 0x000b2200              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0468: 0x04380e10              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x046c: 0x0000e104              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0470: 0x0000cf00              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0474: 0xffff00fe              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x047c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0480: 0x05000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0484: 0x0002ecb0              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0488: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x048c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0490: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0494: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0498: 0x00040000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04a0: 0x00000002              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b0: 0x00000780              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b8: 0x041a0690              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04bc: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c0: 0x041a0690              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c4: 0x041a0690              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c8: 0x041a0690              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d0: 0x00000311              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d4: 0x00000100              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e4: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e8: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04ec: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f0: 0x00010000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f4: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f8: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04fc: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0500: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0504: 0x00010000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0508: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x050c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0510: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0514: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0518: 0x00010000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x051c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0520: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0524: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x052c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0530: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x054c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0550: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0554: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0558: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x055c: 0x00000002              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 1:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0700: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0704: 0x00000011              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0708: 0x33ec6000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x070c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0710: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0714: 0x04650898              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0718: 0x0004002b              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x071c: 0x002800bf              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0720: 0x0460083f              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0724: 0x00000001              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0728: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x072c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0730: 0xffffff00              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0734: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0738: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0740: 0x83000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0744: 0x00000430              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0748: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x074c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0750: 0x08d9ee20              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0754: 0x00200000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0758: 0x08d9ee20              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x075c: 0xf0000001              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0760: 0x000b2200              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0768: 0x04380e10              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x076c: 0x0000e104              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0770: 0x0000cf00              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0774: 0xffff00fe              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x077c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0780: 0x85000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0784: 0x0002ecf0              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0788: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x078c: 0xf0000001 -> 0x00000000
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0790: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0794: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0798: 0x00040000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07a0: 0x00000002              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b8: 0x04380780              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07bc: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c0: 0x04380780              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c4: 0x04380780              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c8: 0x04380780              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d0: 0x00000311              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d4: 0x00000100              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e4: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e8: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07ec: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f0: 0x00010000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f4: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f8: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07fc: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0800: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0804: 0x00010000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0808: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x080c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0810: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0814: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0818: 0x00010000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x081c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0820: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0824: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x082c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0830: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x084c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0850: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0854: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0858: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x085c: 0x00000002              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 2:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a00: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a04: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a08: 0x21ec4000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a0c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a10: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a14: 0x00050008              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a18: 0x00000001              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a1c: 0x00010003              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a20: 0x00030004              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a24: 0x00000001              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a28: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a2c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a30: 0xffffff40              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a34: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a38: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a40: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a44: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a48: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a4c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a50: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a54: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a58: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a5c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a60: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a68: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a6c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a70: 0x0000e900              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a74: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a7c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a80: 0x05000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a84: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a88: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a8c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a90: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a94: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a98: 0x00040000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aa0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab8: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0abc: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac4: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac8: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad0: 0x00110300              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad4: 0x00001100              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae4: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae8: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aec: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af0: 0x00010000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af4: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af8: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0afc: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b00: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b04: 0x00010000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b08: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b0c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b10: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b14: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b18: 0x00010000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b1c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b20: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b24: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b2c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b30: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b4c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b50: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b54: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b58: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b5c: 0x00000001              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 3:
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d00: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d04: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d08: 0x21ec4000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d0c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d10: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d14: 0x00050008              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d18: 0x00000001              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d1c: 0x00010003              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d20: 0x00030004              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d24: 0x00000001              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d28: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d2c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d30: 0xffffff40              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d34: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d38: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d40: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d44: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d48: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d4c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d50: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d54: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d58: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d5c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d60: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d68: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d6c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d70: 0x0000e900              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d74: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d7c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d80: 0x05000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d84: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d88: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d8c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d90: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d94: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d98: 0x00040000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0da0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db8: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dbc: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc4: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc8: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd0: 0x00110300              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd4: 0x00001100              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de0: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de4: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de8: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dec: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df0: 0x00010000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df4: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df8: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dfc: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e00: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e04: 0x00010000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e08: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e0c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e10: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e14: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e18: 0x00010000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e1c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e20: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e24: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e2c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e30: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e4c: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e50: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e54: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e58: 0x00000000              
Feb 14 00:36:24 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e5c: 0x00000001              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] chid 0 mthd 0x048c data 0xf0000001 0x1000748c 0x00000000
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] chid 0 mthd 0x0080 data 0x00000000 0x10005080 0x00000021
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0080: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0084: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0088: 0xf0000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 0:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0180: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0184: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0188: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0190: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 1:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a0: 0x00000001              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a4: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a8: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01b0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 2:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c4: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c8: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01d0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 0:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0200: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0204: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0208: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0210: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 1:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0220: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0224: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0228: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0230: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 2:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0240: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0244: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0248: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0250: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 3:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0260: 0x00000102              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0264: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0268: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0270: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 4:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0280: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0284: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0288: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0290: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 5:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a4: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a8: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02b0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 6:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c4: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c8: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02d0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 7:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e4: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e8: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02f0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 0:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0300: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0304: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0308: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0310: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 1:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0320: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0324: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0328: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0330: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 2:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0340: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0344: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0348: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0350: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 3:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0360: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0364: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0368: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0370: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 0:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0400: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0404: 0x00000009              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0408: 0x31ec6000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x040c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0410: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0414: 0x044108c0              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0418: 0x000500af              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x041c: 0x002301c7              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0420: 0x043d0857              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0424: 0x00000001              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0428: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x042c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0430: 0xffffff00              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0434: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0438: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0440: 0x83000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0444: 0x00000410              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0448: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x044c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0450: 0x08c30ac0              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0454: 0x00200000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0458: 0x08c30ac0              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x045c: 0xf0000001              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0460: 0x000b2200              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0468: 0x04380e10              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x046c: 0x0000e104              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0470: 0x0000cf00              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0474: 0xffff00fe              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x047c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0480: 0x05000000 -> 0x85000000
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0484: 0x0002ecb0              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0488: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x048c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0490: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0494: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0498: 0x00040000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04a0: 0x00000002              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b0: 0x00000780              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b8: 0x041a0690              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04bc: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c0: 0x041a0690              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c4: 0x041a0690              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c8: 0x041a0690              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d0: 0x00000311              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d4: 0x00000100              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e4: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e8: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04ec: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f0: 0x00010000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f4: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f8: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04fc: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0500: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0504: 0x00010000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0508: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x050c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0510: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0514: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0518: 0x00010000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x051c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0520: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0524: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x052c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0530: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x054c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0550: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0554: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0558: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x055c: 0x00000002              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 1:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0700: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0704: 0x00000011              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0708: 0x33ec6000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x070c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0710: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0714: 0x04650898              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0718: 0x0004002b              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x071c: 0x002800bf              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0720: 0x0460083f              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0724: 0x00000001              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0728: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x072c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0730: 0xffffff00              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0734: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0738: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0740: 0x83000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0744: 0x00000430              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0748: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x074c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0750: 0x08d9ee20              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0754: 0x00200000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0758: 0x08d9ee20              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x075c: 0xf0000001              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0760: 0x000b2200              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0768: 0x04380e10              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x076c: 0x0000e104              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0770: 0x0000cf00              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0774: 0xffff00fe              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x077c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0780: 0x85000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0784: 0x0002ecf0              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0788: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x078c: 0xf0000001 -> 0x00000000
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0790: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0794: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0798: 0x00040000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07a0: 0x00000002              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b8: 0x04380780              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07bc: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c0: 0x04380780              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c4: 0x04380780              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c8: 0x04380780              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d0: 0x00000311              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d4: 0x00000100              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e4: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e8: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07ec: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f0: 0x00010000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f4: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f8: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07fc: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0800: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0804: 0x00010000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0808: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x080c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0810: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0814: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0818: 0x00010000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x081c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0820: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0824: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x082c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0830: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x084c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0850: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0854: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0858: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x085c: 0x00000002              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 2:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a00: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a04: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a08: 0x21ec4000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a0c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a10: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a14: 0x00050008              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a18: 0x00000001              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a1c: 0x00010003              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a20: 0x00030004              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a24: 0x00000001              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a28: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a2c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a30: 0xffffff40              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a34: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a38: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a40: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a44: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a48: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a4c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a50: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a54: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a58: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a5c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a60: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a68: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a6c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a70: 0x0000e900              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a74: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a7c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a80: 0x05000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a84: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a88: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a8c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a90: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a94: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a98: 0x00040000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aa0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab8: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0abc: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac4: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac8: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad0: 0x00110300              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad4: 0x00001100              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae4: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae8: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aec: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af0: 0x00010000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af4: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af8: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0afc: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b00: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b04: 0x00010000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b08: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b0c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b10: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b14: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b18: 0x00010000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b1c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b20: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b24: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b2c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b30: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b4c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b50: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b54: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b58: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b5c: 0x00000001              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 3:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d00: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d04: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d08: 0x21ec4000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d0c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d10: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d14: 0x00050008              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d18: 0x00000001              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d1c: 0x00010003              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d20: 0x00030004              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d24: 0x00000001              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d28: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d2c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d30: 0xffffff40              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d34: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d38: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d40: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d44: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d48: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d4c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d50: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d54: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d58: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d5c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d60: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d68: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d6c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d70: 0x0000e900              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d74: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d7c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d80: 0x05000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d84: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d88: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d8c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d90: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d94: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d98: 0x00040000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0da0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db8: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dbc: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc4: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc8: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd0: 0x00110300              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd4: 0x00001100              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de4: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de8: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dec: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df0: 0x00010000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df4: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df8: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dfc: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e00: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e04: 0x00010000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e08: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e0c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e10: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e14: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e18: 0x00010000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e1c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e20: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e24: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e2c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e30: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e4c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e50: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e54: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e58: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e5c: 0x00000001              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] chid 0 mthd 0x0080 data 0x00000000 0x10005080 0x00000021
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0080: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0084: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0088: 0xf0000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 0:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0180: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0184: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0188: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0190: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 1:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a0: 0x00000001              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a4: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a8: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01b0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 2:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c4: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c8: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01d0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 0:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0200: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0204: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0208: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0210: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 1:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0220: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0224: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0228: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0230: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 2:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0240: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0244: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0248: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0250: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 3:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0260: 0x00000102              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0264: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0268: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0270: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 4:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0280: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0284: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0288: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0290: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 5:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a4: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a8: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02b0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 6:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c4: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c8: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02d0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 7:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e4: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e8: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02f0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 0:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0300: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0304: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0308: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0310: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 1:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0320: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0324: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0328: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0330: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 2:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0340: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0344: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0348: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0350: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 3:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0360: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0364: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0368: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0370: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 0:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0400: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0404: 0x00000009              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0408: 0x31ec6000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x040c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0410: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0414: 0x044108c0              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0418: 0x000500af              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x041c: 0x002301c7              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0420: 0x043d0857              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0424: 0x00000001              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0428: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x042c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0430: 0xffffff00              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0434: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0438: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0440: 0x83000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0444: 0x00000410              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0448: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x044c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0450: 0x08c30ac0              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0454: 0x00200000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0458: 0x08c30ac0              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x045c: 0xf0000001              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0460: 0x000b2200              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0468: 0x04380e10              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x046c: 0x0000e104              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0470: 0x0000cf00              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0474: 0xffff00fe              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x047c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0480: 0x05000000 -> 0x85000000
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0484: 0x0002ecb0              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0488: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x048c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0490: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0494: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0498: 0x00040000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04a0: 0x00000002              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b0: 0x00000780              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b8: 0x041a0690              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04bc: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c0: 0x041a0690              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c4: 0x041a0690              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c8: 0x041a0690              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d0: 0x00000311              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d4: 0x00000100              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e4: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e8: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04ec: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f0: 0x00010000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f4: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f8: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04fc: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0500: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0504: 0x00010000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0508: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x050c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0510: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0514: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0518: 0x00010000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x051c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0520: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0524: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x052c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0530: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x054c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0550: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0554: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0558: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x055c: 0x00000002              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 1:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0700: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0704: 0x00000011              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0708: 0x33ec6000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x070c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0710: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0714: 0x04650898              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0718: 0x0004002b              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x071c: 0x002800bf              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0720: 0x0460083f              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0724: 0x00000001              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0728: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x072c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0730: 0xffffff00              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0734: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0738: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0740: 0x83000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0744: 0x00000430              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0748: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x074c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0750: 0x08d9ee20              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0754: 0x00200000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0758: 0x08d9ee20              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x075c: 0xf0000001              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0760: 0x000b2200              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0768: 0x04380e10              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x076c: 0x0000e104              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0770: 0x0000cf00              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0774: 0xffff00fe              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x077c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0780: 0x85000000 -> 0x05000000
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0784: 0x0002ecf0              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0788: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x078c: 0xf0000001 -> 0x00000000
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0790: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0794: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0798: 0x00040000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07a0: 0x00000002              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b8: 0x04380780              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07bc: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c0: 0x04380780              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c4: 0x04380780              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c8: 0x04380780              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d0: 0x00000311              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d4: 0x00000100              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e4: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e8: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07ec: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f0: 0x00010000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f4: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f8: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07fc: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0800: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0804: 0x00010000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0808: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x080c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0810: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0814: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0818: 0x00010000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x081c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0820: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0824: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x082c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0830: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x084c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0850: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0854: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0858: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x085c: 0x00000002              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 2:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a00: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a04: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a08: 0x21ec4000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a0c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a10: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a14: 0x00050008              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a18: 0x00000001              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a1c: 0x00010003              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a20: 0x00030004              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a24: 0x00000001              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a28: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a2c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a30: 0xffffff40              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a34: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a38: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a40: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a44: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a48: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a4c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a50: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a54: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a58: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a5c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a60: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a68: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a6c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a70: 0x0000e900              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a74: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a7c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a80: 0x05000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a84: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a88: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a8c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a90: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a94: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a98: 0x00040000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aa0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab8: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0abc: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac4: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac8: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad0: 0x00110300              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad4: 0x00001100              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae4: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae8: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aec: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af0: 0x00010000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af4: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af8: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0afc: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b00: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b04: 0x00010000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b08: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b0c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b10: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b14: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b18: 0x00010000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b1c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b20: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b24: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b2c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b30: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b4c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b50: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b54: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b58: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b5c: 0x00000001              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 3:
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d00: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d04: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d08: 0x21ec4000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d0c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d10: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d14: 0x00050008              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d18: 0x00000001              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d1c: 0x00010003              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d20: 0x00030004              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d24: 0x00000001              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d28: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d2c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d30: 0xffffff40              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d34: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d38: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d40: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d44: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d48: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d4c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d50: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d54: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d58: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d5c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d60: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d68: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d6c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d70: 0x0000e900              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d74: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d7c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d80: 0x05000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d84: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d88: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d8c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d90: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d94: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d98: 0x00040000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0da0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db8: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dbc: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc4: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc8: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd0: 0x00110300              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd4: 0x00001100              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de0: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de4: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de8: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dec: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df0: 0x00010000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df4: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df8: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dfc: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e00: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e04: 0x00010000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e08: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e0c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e10: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e14: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e18: 0x00010000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e1c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e20: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e24: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e2c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e30: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e4c: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e50: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e54: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e58: 0x00000000              
Feb 14 00:36:26 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e5c: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] chid 0 mthd 0x078c data 0xf0000001 0x1000778c 0x00000000
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] chid 0 mthd 0x0080 data 0x00000000 0x10005080 0x00000021
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0080: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0084: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0088: 0xf0000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 0:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0180: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0184: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0188: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0190: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 1:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a0: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01b0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 2:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01d0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 0:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0200: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0204: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0208: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0210: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 1:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0220: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0224: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0228: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0230: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 2:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0240: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0244: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0248: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0250: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 3:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0260: 0x00000102              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0264: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0268: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0270: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 4:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0280: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0284: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0288: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0290: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 5:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02b0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 6:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02d0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 7:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02f0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 0:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0300: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0304: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0308: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0310: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 1:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0320: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0324: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0328: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0330: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 2:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0340: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0344: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0348: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0350: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 3:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0360: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0364: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0368: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0370: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 0:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0400: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0404: 0x00000009              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0408: 0x31ec6000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x040c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0410: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0414: 0x044108c0              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0418: 0x000500af              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x041c: 0x002301c7              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0420: 0x043d0857              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0424: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0428: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x042c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0430: 0xffffff00              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0434: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0438: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0440: 0x83000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0444: 0x00000410              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0448: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x044c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0450: 0x08c30ac0              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0454: 0x00200000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0458: 0x08c30ac0              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x045c: 0xf0000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0460: 0x000b2200              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0468: 0x04380e10              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x046c: 0x0000e104              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0470: 0x0000cf00              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0474: 0xffff00fe              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x047c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0480: 0x05000000 -> 0x85000000
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0484: 0x0002ecb0              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0488: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x048c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0490: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0494: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0498: 0x00040000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04a0: 0x00000002              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b0: 0x00000780              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b8: 0x041a0690              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04bc: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c0: 0x041a0690              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c4: 0x041a0690              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c8: 0x041a0690              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d0: 0x00000311              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d4: 0x00000100              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04ec: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f0: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04fc: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0500: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0504: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0508: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x050c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0510: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0514: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0518: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x051c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0520: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0524: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x052c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0530: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x054c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0550: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0554: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0558: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x055c: 0x00000002              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 1:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0700: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0704: 0x00000011              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0708: 0x33ec6000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x070c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0710: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0714: 0x04650898              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0718: 0x0004002b              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x071c: 0x002800bf              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0720: 0x0460083f              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0724: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0728: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x072c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0730: 0xffffff00              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0734: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0738: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0740: 0x83000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0744: 0x00000430              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0748: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x074c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0750: 0x08d9ee20              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0754: 0x00200000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0758: 0x08d9ee20              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x075c: 0xf0000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0760: 0x000b2200              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0768: 0x04380e10              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x076c: 0x0000e104              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0770: 0x0000cf00              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0774: 0xffff00fe              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x077c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0780: 0x85000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0784: 0x0002ecf0              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0788: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x078c: 0xf0000001 -> 0x00000000
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0790: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0794: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0798: 0x00040000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07a0: 0x00000002              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b8: 0x04380780              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07bc: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c0: 0x04380780              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c4: 0x04380780              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c8: 0x04380780              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d0: 0x00000311              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d4: 0x00000100              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07ec: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f0: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07fc: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0800: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0804: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0808: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x080c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0810: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0814: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0818: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x081c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0820: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0824: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x082c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0830: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x084c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0850: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0854: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0858: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x085c: 0x00000002              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 2:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a00: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a04: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a08: 0x21ec4000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a0c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a10: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a14: 0x00050008              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a18: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a1c: 0x00010003              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a20: 0x00030004              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a24: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a28: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a2c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a30: 0xffffff40              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a34: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a38: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a40: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a44: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a48: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a4c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a50: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a54: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a58: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a5c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a60: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a68: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a6c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a70: 0x0000e900              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a74: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a7c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a80: 0x05000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a84: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a88: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a8c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a90: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a94: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a98: 0x00040000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aa0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0abc: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad0: 0x00110300              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad4: 0x00001100              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aec: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af0: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0afc: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b00: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b04: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b08: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b0c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b10: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b14: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b18: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b1c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b20: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b24: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b2c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b30: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b4c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b50: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b54: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b58: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b5c: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 3:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d00: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d04: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d08: 0x21ec4000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d0c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d10: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d14: 0x00050008              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d18: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d1c: 0x00010003              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d20: 0x00030004              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d24: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d28: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d2c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d30: 0xffffff40              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d34: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d38: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d40: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d44: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d48: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d4c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d50: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d54: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d58: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d5c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d60: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d68: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d6c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d70: 0x0000e900              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d74: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d7c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d80: 0x05000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d84: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d88: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d8c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d90: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d94: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d98: 0x00040000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0da0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dbc: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd0: 0x00110300              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd4: 0x00001100              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dec: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df0: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dfc: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e00: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e04: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e08: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e0c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e10: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e14: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e18: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e1c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e20: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e24: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e2c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e30: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e4c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e50: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e54: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e58: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e5c: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] chid 0 mthd 0x0080 data 0x00000000 0x10005080 0x00002021
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0080: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0084: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0088: 0xf0000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 0:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0180: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0184: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0188: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0190: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 1:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a0: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01b0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 2:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01d0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 0:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0200: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0204: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0208: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0210: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 1:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0220: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0224: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0228: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0230: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 2:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0240: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0244: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0248: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0250: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 3:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0260: 0x00000102              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0264: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0268: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0270: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 4:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0280: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0284: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0288: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0290: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 5:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02b0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 6:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02d0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 7:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02f0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 0:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0300: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0304: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0308: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0310: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 1:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0320: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0324: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0328: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0330: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 2:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0340: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0344: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0348: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0350: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 3:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0360: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0364: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0368: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0370: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 0:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0400: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0404: 0x00000009              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0408: 0x31ec6000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x040c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0410: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0414: 0x044108c0              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0418: 0x000500af              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x041c: 0x002301c7              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0420: 0x043d0857              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0424: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0428: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x042c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0430: 0xffffff00              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0434: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0438: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0440: 0x83000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0444: 0x00000410              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0448: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x044c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0450: 0x08c30ac0              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0454: 0x00200000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0458: 0x08c30ac0              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x045c: 0xf0000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0460: 0x000b2200              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0468: 0x04380e10              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x046c: 0x0000e104              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0470: 0x0000cf00              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0474: 0xffff00fe              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x047c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0480: 0x05000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0484: 0x0002ecb0              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0488: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x048c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0490: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0494: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0498: 0x00040000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04a0: 0x00000002              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b0: 0x00000780              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b8: 0x041a0690              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04bc: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c0: 0x041a0690              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c4: 0x041a0690              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c8: 0x041a0690              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d0: 0x00000311              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d4: 0x00000100              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04ec: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f0: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04fc: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0500: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0504: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0508: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x050c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0510: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0514: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0518: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x051c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0520: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0524: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x052c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0530: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x054c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0550: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0554: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0558: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x055c: 0x00000002              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 1:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0700: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0704: 0x00000011              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0708: 0x33ec6000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x070c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0710: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0714: 0x04650898              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0718: 0x0004002b              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x071c: 0x002800bf              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0720: 0x0460083f              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0724: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0728: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x072c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0730: 0xffffff00              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0734: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0738: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0740: 0x83000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0744: 0x00000430              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0748: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x074c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0750: 0x08d9ee20              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0754: 0x00200000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0758: 0x08d9ee20              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x075c: 0xf0000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0760: 0x000b2200              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0768: 0x04380e10              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x076c: 0x0000e104              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0770: 0x0000cf00              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0774: 0xffff00fe              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x077c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0780: 0x85000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0784: 0x0002ecf0              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0788: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x078c: 0xf0000001 -> 0x00000000
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0790: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0794: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0798: 0x00040000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07a0: 0x00000002              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b8: 0x04380780              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07bc: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c0: 0x04380780              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c4: 0x04380780              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c8: 0x04380780              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d0: 0x00000311              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d4: 0x00000100              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07ec: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f0: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07fc: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0800: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0804: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0808: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x080c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0810: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0814: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0818: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x081c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0820: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0824: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x082c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0830: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x084c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0850: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0854: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0858: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x085c: 0x00000002              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 2:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a00: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a04: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a08: 0x21ec4000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a0c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a10: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a14: 0x00050008              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a18: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a1c: 0x00010003              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a20: 0x00030004              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a24: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a28: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a2c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a30: 0xffffff40              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a34: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a38: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a40: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a44: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a48: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a4c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a50: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a54: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a58: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a5c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a60: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a68: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a6c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a70: 0x0000e900              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a74: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a7c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a80: 0x05000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a84: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a88: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a8c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a90: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a94: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a98: 0x00040000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aa0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0abc: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad0: 0x00110300              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad4: 0x00001100              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aec: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af0: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0afc: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b00: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b04: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b08: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b0c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b10: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b14: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b18: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b1c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b20: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b24: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b2c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b30: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b4c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b50: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b54: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b58: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b5c: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 3:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d00: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d04: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d08: 0x21ec4000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d0c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d10: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d14: 0x00050008              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d18: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d1c: 0x00010003              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d20: 0x00030004              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d24: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d28: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d2c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d30: 0xffffff40              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d34: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d38: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d40: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d44: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d48: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d4c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d50: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d54: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d58: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d5c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d60: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d68: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d6c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d70: 0x0000e900              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d74: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d7c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d80: 0x05000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d84: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d88: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d8c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d90: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d94: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d98: 0x00040000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0da0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dbc: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd0: 0x00110300              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd4: 0x00001100              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dec: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df0: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dfc: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e00: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e04: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e08: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e0c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e10: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e14: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e18: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e1c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e20: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e24: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e2c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e30: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e4c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e50: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e54: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e58: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e5c: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] chid 0 mthd 0x048c data 0xf0000001 0x1000748c 0x00000000
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] chid 0 mthd 0x0080 data 0x00000000 0x10005080 0x00000021
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0080: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0084: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0088: 0xf0000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 0:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0180: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0184: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0188: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0190: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 1:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a0: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01b0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 2:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01d0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 0:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0200: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0204: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0208: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0210: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 1:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0220: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0224: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0228: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0230: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 2:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0240: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0244: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0248: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0250: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 3:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0260: 0x00000102              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0264: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0268: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0270: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 4:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0280: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0284: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0288: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0290: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 5:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02b0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 6:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02d0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 7:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02f0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 0:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0300: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0304: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0308: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0310: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 1:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0320: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0324: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0328: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0330: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 2:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0340: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0344: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0348: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0350: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 3:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0360: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0364: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0368: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0370: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 0:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0400: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0404: 0x00000009              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0408: 0x31ec6000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x040c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0410: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0414: 0x044108c0              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0418: 0x000500af              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x041c: 0x002301c7              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0420: 0x043d0857              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0424: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0428: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x042c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0430: 0xffffff00              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0434: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0438: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0440: 0x83000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0444: 0x00000410              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0448: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x044c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0450: 0x08c30ac0              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0454: 0x00200000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0458: 0x08c30ac0              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x045c: 0xf0000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0460: 0x000b2200              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0468: 0x04380e10              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x046c: 0x0000e104              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0470: 0x0000cf00              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0474: 0xffff00fe              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x047c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0480: 0x05000000 -> 0x85000000
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0484: 0x0002ecb0              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0488: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x048c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0490: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0494: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0498: 0x00040000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04a0: 0x00000002              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b0: 0x00000780              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b8: 0x041a0690              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04bc: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c0: 0x041a0690              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c4: 0x041a0690              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c8: 0x041a0690              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d0: 0x00000311              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d4: 0x00000100              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04ec: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f0: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04fc: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0500: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0504: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0508: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x050c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0510: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0514: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0518: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x051c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0520: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0524: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x052c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0530: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x054c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0550: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0554: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0558: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x055c: 0x00000002              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 1:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0700: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0704: 0x00000011              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0708: 0x33ec6000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x070c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0710: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0714: 0x04650898              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0718: 0x0004002b              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x071c: 0x002800bf              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0720: 0x0460083f              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0724: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0728: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x072c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0730: 0xffffff00              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0734: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0738: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0740: 0x83000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0744: 0x00000430              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0748: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x074c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0750: 0x08d9ee20              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0754: 0x00200000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0758: 0x08d9ee20              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x075c: 0xf0000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0760: 0x000b2200              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0768: 0x04380e10              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x076c: 0x0000e104              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0770: 0x0000cf00              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0774: 0xffff00fe              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x077c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0780: 0x85000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0784: 0x0002ecf0              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0788: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x078c: 0xf0000001 -> 0x00000000
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0790: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0794: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0798: 0x00040000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07a0: 0x00000002              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b8: 0x04380780              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07bc: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c0: 0x04380780              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c4: 0x04380780              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c8: 0x04380780              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d0: 0x00000311              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d4: 0x00000100              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07ec: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f0: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07fc: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0800: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0804: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0808: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x080c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0810: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0814: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0818: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x081c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0820: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0824: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x082c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0830: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x084c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0850: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0854: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0858: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x085c: 0x00000002              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 2:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a00: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a04: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a08: 0x21ec4000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a0c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a10: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a14: 0x00050008              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a18: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a1c: 0x00010003              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a20: 0x00030004              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a24: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a28: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a2c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a30: 0xffffff40              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a34: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a38: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a40: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a44: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a48: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a4c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a50: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a54: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a58: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a5c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a60: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a68: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a6c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a70: 0x0000e900              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a74: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a7c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a80: 0x05000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a84: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a88: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a8c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a90: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a94: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a98: 0x00040000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aa0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0abc: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad0: 0x00110300              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad4: 0x00001100              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aec: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af0: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0afc: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b00: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b04: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b08: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b0c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b10: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b14: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b18: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b1c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b20: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b24: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b2c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b30: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b4c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b50: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b54: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b58: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b5c: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 3:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d00: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d04: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d08: 0x21ec4000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d0c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d10: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d14: 0x00050008              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d18: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d1c: 0x00010003              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d20: 0x00030004              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d24: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d28: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d2c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d30: 0xffffff40              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d34: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d38: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d40: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d44: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d48: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d4c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d50: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d54: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d58: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d5c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d60: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d68: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d6c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d70: 0x0000e900              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d74: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d7c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d80: 0x05000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d84: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d88: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d8c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d90: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d94: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d98: 0x00040000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0da0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dbc: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd0: 0x00110300              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd4: 0x00001100              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dec: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df0: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dfc: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e00: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e04: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e08: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e0c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e10: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e14: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e18: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e1c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e20: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e24: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e2c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e30: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e4c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e50: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e54: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e58: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e5c: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] chid 0 mthd 0x0080 data 0x00000000 0x10005080 0x00002021
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0080: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0084: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0088: 0xf0000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 0:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0180: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0184: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0188: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0190: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 1:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a0: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01b0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 2:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01d0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 0:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0200: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0204: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0208: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0210: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 1:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0220: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0224: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0228: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0230: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 2:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0240: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0244: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0248: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0250: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 3:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0260: 0x00000102              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0264: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0268: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0270: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 4:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0280: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0284: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0288: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0290: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 5:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02b0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 6:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02d0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 7:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02f0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 0:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0300: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0304: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0308: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0310: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 1:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0320: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0324: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0328: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0330: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 2:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0340: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0344: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0348: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0350: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 3:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0360: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0364: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0368: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0370: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 0:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0400: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0404: 0x00000009              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0408: 0x31ec6000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x040c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0410: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0414: 0x044108c0              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0418: 0x000500af              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x041c: 0x002301c7              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0420: 0x043d0857              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0424: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0428: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x042c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0430: 0xffffff00              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0434: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0438: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0440: 0x83000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0444: 0x00000410              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0448: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x044c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0450: 0x08c30ac0              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0454: 0x00200000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0458: 0x08c30ac0              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x045c: 0xf0000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0460: 0x000b2200              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0468: 0x04380e10              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x046c: 0x0000e104              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0470: 0x0000cf00              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0474: 0xffff00fe              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x047c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0480: 0x05000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0484: 0x0002ecb0              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0488: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x048c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0490: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0494: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0498: 0x00040000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04a0: 0x00000002              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b0: 0x00000780              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b8: 0x041a0690              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04bc: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c0: 0x041a0690              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c4: 0x041a0690              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c8: 0x041a0690              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d0: 0x00000311              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d4: 0x00000100              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04ec: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f0: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04fc: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0500: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0504: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0508: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x050c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0510: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0514: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0518: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x051c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0520: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0524: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x052c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0530: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x054c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0550: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0554: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0558: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x055c: 0x00000002              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 1:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0700: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0704: 0x00000011              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0708: 0x33ec6000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x070c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0710: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0714: 0x04650898              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0718: 0x0004002b              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x071c: 0x002800bf              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0720: 0x0460083f              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0724: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0728: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x072c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0730: 0xffffff00              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0734: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0738: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0740: 0x83000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0744: 0x00000430              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0748: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x074c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0750: 0x08d9ee20              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0754: 0x00200000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0758: 0x08d9ee20              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x075c: 0xf0000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0760: 0x000b2200              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0768: 0x04380e10              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x076c: 0x0000e104              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0770: 0x0000cf00              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0774: 0xffff00fe              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x077c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0780: 0x85000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0784: 0x0002ecf0              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0788: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x078c: 0xf0000001 -> 0x00000000
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0790: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0794: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0798: 0x00040000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07a0: 0x00000002              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b8: 0x04380780              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07bc: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c0: 0x04380780              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c4: 0x04380780              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c8: 0x04380780              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d0: 0x00000311              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d4: 0x00000100              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07ec: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f0: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07fc: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0800: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0804: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0808: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x080c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0810: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0814: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0818: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x081c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0820: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0824: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x082c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0830: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x084c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0850: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0854: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0858: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x085c: 0x00000002              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 2:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a00: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a04: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a08: 0x21ec4000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a0c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a10: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a14: 0x00050008              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a18: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a1c: 0x00010003              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a20: 0x00030004              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a24: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a28: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a2c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a30: 0xffffff40              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a34: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a38: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a40: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a44: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a48: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a4c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a50: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a54: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a58: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a5c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a60: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a68: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a6c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a70: 0x0000e900              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a74: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a7c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a80: 0x05000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a84: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a88: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a8c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a90: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a94: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a98: 0x00040000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aa0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0abc: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad0: 0x00110300              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad4: 0x00001100              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aec: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af0: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0afc: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b00: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b04: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b08: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b0c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b10: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b14: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b18: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b1c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b20: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b24: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b2c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b30: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b4c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b50: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b54: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b58: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b5c: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 3:
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d00: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d04: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d08: 0x21ec4000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d0c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d10: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d14: 0x00050008              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d18: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d1c: 0x00010003              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d20: 0x00030004              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d24: 0x00000001              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d28: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d2c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d30: 0xffffff40              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d34: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d38: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d40: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d44: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d48: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d4c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d50: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d54: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d58: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d5c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d60: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d68: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d6c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d70: 0x0000e900              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d74: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d7c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d80: 0x05000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d84: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d88: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d8c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d90: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d94: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d98: 0x00040000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0da0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dbc: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd0: 0x00110300              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd4: 0x00001100              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de0: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dec: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df0: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df4: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df8: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dfc: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e00: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e04: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e08: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e0c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e10: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e14: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e18: 0x00010000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e1c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e20: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e24: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e2c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e30: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e4c: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e50: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e54: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e58: 0x00000000              
Feb 14 00:36:27 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e5c: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] chid 0 mthd 0x048c data 0xf0000001 0x1000748c 0x00000000
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] chid 0 mthd 0x0080 data 0x00000000 0x10005080 0x00000021
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0080: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0084: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0088: 0xf0000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 0:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0180: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0184: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0188: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0190: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 1:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a0: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01b0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 2:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01d0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 0:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0200: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0204: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0208: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0210: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 1:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0220: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0224: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0228: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0230: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 2:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0240: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0244: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0248: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0250: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 3:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0260: 0x00000102              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0264: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0268: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0270: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 4:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0280: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0284: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0288: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0290: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 5:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02b0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 6:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02d0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 7:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02f0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 0:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0300: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0304: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0308: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0310: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 1:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0320: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0324: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0328: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0330: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 2:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0340: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0344: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0348: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0350: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 3:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0360: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0364: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0368: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0370: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 0:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0400: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0404: 0x00000009              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0408: 0x31ec6000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x040c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0410: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0414: 0x044108c0              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0418: 0x000500af              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x041c: 0x002301c7              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0420: 0x043d0857              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0424: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0428: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x042c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0430: 0xffffff00              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0434: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0438: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0440: 0x83000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0444: 0x00000410              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0448: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x044c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0450: 0x08c30ac0              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0454: 0x00200000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0458: 0x08c30ac0              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x045c: 0xf0000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0460: 0x000b2200              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0468: 0x04380e10              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x046c: 0x0000e104              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0470: 0x0000cf00              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0474: 0xffff00fe              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x047c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0480: 0x05000000 -> 0x85000000
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0484: 0x0002ecb0              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0488: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x048c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0490: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0494: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0498: 0x00040000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04a0: 0x00000002              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b0: 0x00000780              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b8: 0x041a0690              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04bc: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c0: 0x041a0690              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c4: 0x041a0690              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c8: 0x041a0690              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d0: 0x00000311              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d4: 0x00000100              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04ec: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f0: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04fc: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0500: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0504: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0508: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x050c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0510: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0514: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0518: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x051c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0520: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0524: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x052c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0530: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x054c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0550: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0554: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0558: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x055c: 0x00000002              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 1:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0700: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0704: 0x00000011              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0708: 0x33ec6000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x070c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0710: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0714: 0x04650898              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0718: 0x0004002b              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x071c: 0x002800bf              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0720: 0x0460083f              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0724: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0728: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x072c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0730: 0xffffff00              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0734: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0738: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0740: 0x83000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0744: 0x00000430              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0748: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x074c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0750: 0x08d9ee20              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0754: 0x00200000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0758: 0x08d9ee20              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x075c: 0xf0000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0760: 0x000b2200              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0768: 0x04380e10              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x076c: 0x0000e104              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0770: 0x0000cf00              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0774: 0xffff00fe              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x077c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0780: 0x85000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0784: 0x0002ecf0              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0788: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x078c: 0xf0000001 -> 0x00000000
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0790: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0794: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0798: 0x00040000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07a0: 0x00000002              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b8: 0x04380780              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07bc: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c0: 0x04380780              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c4: 0x04380780              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c8: 0x04380780              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d0: 0x00000311              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d4: 0x00000100              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07ec: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f0: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07fc: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0800: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0804: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0808: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x080c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0810: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0814: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0818: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x081c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0820: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0824: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x082c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0830: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x084c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0850: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0854: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0858: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x085c: 0x00000002              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 2:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a00: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a04: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a08: 0x21ec4000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a0c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a10: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a14: 0x00050008              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a18: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a1c: 0x00010003              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a20: 0x00030004              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a24: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a28: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a2c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a30: 0xffffff40              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a34: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a38: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a40: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a44: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a48: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a4c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a50: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a54: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a58: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a5c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a60: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a68: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a6c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a70: 0x0000e900              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a74: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a7c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a80: 0x05000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a84: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a88: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a8c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a90: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a94: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a98: 0x00040000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aa0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0abc: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad0: 0x00110300              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad4: 0x00001100              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aec: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af0: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0afc: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b00: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b04: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b08: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b0c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b10: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b14: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b18: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b1c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b20: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b24: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b2c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b30: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b4c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b50: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b54: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b58: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b5c: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 3:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d00: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d04: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d08: 0x21ec4000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d0c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d10: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d14: 0x00050008              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d18: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d1c: 0x00010003              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d20: 0x00030004              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d24: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d28: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d2c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d30: 0xffffff40              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d34: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d38: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d40: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d44: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d48: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d4c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d50: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d54: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d58: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d5c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d60: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d68: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d6c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d70: 0x0000e900              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d74: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d7c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d80: 0x05000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d84: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d88: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d8c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d90: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d94: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d98: 0x00040000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0da0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dbc: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd0: 0x00110300              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd4: 0x00001100              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dec: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df0: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dfc: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e00: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e04: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e08: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e0c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e10: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e14: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e18: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e1c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e20: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e24: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e2c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e30: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e4c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e50: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e54: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e58: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e5c: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] chid 0 mthd 0x0080 data 0x00000000 0x10005080 0x00000021
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0080: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0084: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0088: 0xf0000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 0:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0180: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0184: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0188: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0190: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 1:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a0: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01b0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 2:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01d0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 0:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0200: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0204: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0208: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0210: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 1:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0220: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0224: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0228: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0230: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 2:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0240: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0244: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0248: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0250: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 3:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0260: 0x00000102              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0264: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0268: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0270: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 4:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0280: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0284: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0288: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0290: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 5:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02b0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 6:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02d0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 7:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02f0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 0:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0300: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0304: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0308: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0310: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 1:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0320: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0324: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0328: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0330: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 2:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0340: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0344: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0348: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0350: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 3:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0360: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0364: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0368: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0370: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 0:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0400: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0404: 0x00000009              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0408: 0x31ec6000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x040c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0410: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0414: 0x044108c0              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0418: 0x000500af              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x041c: 0x002301c7              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0420: 0x043d0857              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0424: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0428: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x042c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0430: 0xffffff00              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0434: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0438: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0440: 0x83000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0444: 0x00000410              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0448: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x044c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0450: 0x08c30ac0              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0454: 0x00200000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0458: 0x08c30ac0              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x045c: 0xf0000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0460: 0x000b2200              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0468: 0x04380e10              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x046c: 0x0000e104              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0470: 0x0000cf00              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0474: 0xffff00fe              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x047c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0480: 0x05000000 -> 0x85000000
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0484: 0x0002ecb0              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0488: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x048c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0490: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0494: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0498: 0x00040000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04a0: 0x00000002              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b0: 0x00000780              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b8: 0x041a0690              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04bc: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c0: 0x041a0690              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c4: 0x041a0690              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c8: 0x041a0690              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d0: 0x00000311              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d4: 0x00000100              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04ec: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f0: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04fc: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0500: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0504: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0508: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x050c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0510: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0514: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0518: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x051c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0520: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0524: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x052c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0530: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x054c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0550: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0554: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0558: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x055c: 0x00000002              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 1:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0700: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0704: 0x00000011              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0708: 0x33ec6000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x070c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0710: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0714: 0x04650898              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0718: 0x0004002b              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x071c: 0x002800bf              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0720: 0x0460083f              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0724: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0728: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x072c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0730: 0xffffff00              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0734: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0738: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0740: 0x83000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0744: 0x00000430              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0748: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x074c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0750: 0x08d9ee20              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0754: 0x00200000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0758: 0x08d9ee20              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x075c: 0xf0000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0760: 0x000b2200              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0768: 0x04380e10              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x076c: 0x0000e104              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0770: 0x0000cf00              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0774: 0xffff00fe              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x077c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0780: 0x85000000 -> 0x05000000
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0784: 0x0002ecf0              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0788: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x078c: 0xf0000001 -> 0x00000000
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0790: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0794: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0798: 0x00040000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07a0: 0x00000002              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b8: 0x04380780              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07bc: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c0: 0x04380780              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c4: 0x04380780              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c8: 0x04380780              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d0: 0x00000311              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d4: 0x00000100              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07ec: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f0: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07fc: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0800: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0804: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0808: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x080c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0810: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0814: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0818: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x081c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0820: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0824: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x082c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0830: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x084c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0850: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0854: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0858: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x085c: 0x00000002              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 2:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a00: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a04: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a08: 0x21ec4000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a0c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a10: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a14: 0x00050008              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a18: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a1c: 0x00010003              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a20: 0x00030004              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a24: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a28: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a2c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a30: 0xffffff40              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a34: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a38: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a40: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a44: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a48: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a4c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a50: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a54: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a58: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a5c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a60: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a68: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a6c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a70: 0x0000e900              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a74: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a7c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a80: 0x05000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a84: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a88: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a8c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a90: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a94: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a98: 0x00040000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aa0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0abc: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad0: 0x00110300              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad4: 0x00001100              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aec: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af0: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0afc: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b00: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b04: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b08: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b0c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b10: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b14: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b18: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b1c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b20: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b24: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b2c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b30: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b4c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b50: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b54: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b58: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b5c: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 3:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d00: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d04: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d08: 0x21ec4000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d0c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d10: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d14: 0x00050008              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d18: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d1c: 0x00010003              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d20: 0x00030004              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d24: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d28: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d2c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d30: 0xffffff40              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d34: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d38: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d40: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d44: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d48: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d4c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d50: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d54: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d58: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d5c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d60: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d68: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d6c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d70: 0x0000e900              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d74: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d7c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d80: 0x05000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d84: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d88: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d8c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d90: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d94: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d98: 0x00040000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0da0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dbc: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd0: 0x00110300              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd4: 0x00001100              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dec: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df0: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dfc: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e00: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e04: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e08: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e0c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e10: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e14: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e18: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e1c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e20: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e24: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e2c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e30: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e4c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e50: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e54: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e58: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e5c: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] chid 0 mthd 0x078c data 0xf0000001 0x1000778c 0x00000000
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] chid 0 mthd 0x0080 data 0x00000000 0x10005080 0x00000021
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0080: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0084: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0088: 0xf0000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 0:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0180: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0184: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0188: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0190: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 1:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a0: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01b0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 2:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01d0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 0:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0200: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0204: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0208: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0210: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 1:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0220: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0224: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0228: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0230: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 2:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0240: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0244: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0248: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0250: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 3:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0260: 0x00000102              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0264: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0268: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0270: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 4:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0280: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0284: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0288: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0290: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 5:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02b0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 6:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02d0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 7:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02f0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 0:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0300: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0304: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0308: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0310: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 1:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0320: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0324: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0328: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0330: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 2:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0340: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0344: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0348: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0350: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 3:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0360: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0364: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0368: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0370: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 0:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0400: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0404: 0x00000009              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0408: 0x31ec6000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x040c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0410: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0414: 0x044108c0              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0418: 0x000500af              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x041c: 0x002301c7              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0420: 0x043d0857              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0424: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0428: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x042c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0430: 0xffffff00              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0434: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0438: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0440: 0x83000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0444: 0x00000410              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0448: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x044c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0450: 0x08c30ac0              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0454: 0x00200000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0458: 0x08c30ac0              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x045c: 0xf0000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0460: 0x000b2200              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0468: 0x04380e10              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x046c: 0x0000e104              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0470: 0x0000cf00              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0474: 0xffff00fe              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x047c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0480: 0x05000000 -> 0x85000000
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0484: 0x0002ecb0              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0488: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x048c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0490: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0494: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0498: 0x00040000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04a0: 0x00000002              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b0: 0x00000780              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b8: 0x041a0690              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04bc: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c0: 0x041a0690              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c4: 0x041a0690              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c8: 0x041a0690              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d0: 0x00000311              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d4: 0x00000100              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04ec: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f0: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04fc: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0500: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0504: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0508: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x050c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0510: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0514: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0518: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x051c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0520: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0524: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x052c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0530: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x054c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0550: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0554: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0558: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x055c: 0x00000002              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 1:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0700: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0704: 0x00000011              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0708: 0x33ec6000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x070c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0710: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0714: 0x04650898              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0718: 0x0004002b              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x071c: 0x002800bf              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0720: 0x0460083f              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0724: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0728: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x072c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0730: 0xffffff00              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0734: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0738: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0740: 0x83000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0744: 0x00000430              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0748: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x074c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0750: 0x08d9ee20              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0754: 0x00200000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0758: 0x08d9ee20              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x075c: 0xf0000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0760: 0x000b2200              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0768: 0x04380e10              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x076c: 0x0000e104              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0770: 0x0000cf00              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0774: 0xffff00fe              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x077c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0780: 0x85000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0784: 0x0002ecf0              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0788: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x078c: 0xf0000001 -> 0x00000000
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0790: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0794: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0798: 0x00040000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07a0: 0x00000002              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b8: 0x04380780              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07bc: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c0: 0x04380780              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c4: 0x04380780              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c8: 0x04380780              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d0: 0x00000311              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d4: 0x00000100              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07ec: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f0: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07fc: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0800: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0804: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0808: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x080c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0810: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0814: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0818: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x081c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0820: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0824: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x082c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0830: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x084c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0850: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0854: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0858: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x085c: 0x00000002              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 2:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a00: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a04: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a08: 0x21ec4000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a0c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a10: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a14: 0x00050008              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a18: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a1c: 0x00010003              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a20: 0x00030004              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a24: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a28: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a2c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a30: 0xffffff40              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a34: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a38: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a40: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a44: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a48: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a4c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a50: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a54: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a58: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a5c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a60: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a68: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a6c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a70: 0x0000e900              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a74: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a7c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a80: 0x05000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a84: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a88: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a8c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a90: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a94: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a98: 0x00040000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aa0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0abc: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad0: 0x00110300              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad4: 0x00001100              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aec: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af0: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0afc: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b00: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b04: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b08: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b0c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b10: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b14: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b18: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b1c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b20: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b24: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b2c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b30: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b4c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b50: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b54: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b58: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b5c: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 3:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d00: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d04: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d08: 0x21ec4000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d0c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d10: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d14: 0x00050008              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d18: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d1c: 0x00010003              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d20: 0x00030004              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d24: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d28: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d2c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d30: 0xffffff40              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d34: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d38: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d40: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d44: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d48: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d4c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d50: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d54: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d58: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d5c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d60: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d68: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d6c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d70: 0x0000e900              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d74: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d7c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d80: 0x05000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d84: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d88: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d8c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d90: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d94: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d98: 0x00040000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0da0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dbc: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd0: 0x00110300              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd4: 0x00001100              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dec: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df0: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dfc: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e00: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e04: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e08: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e0c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e10: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e14: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e18: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e1c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e20: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e24: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e2c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e30: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e4c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e50: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e54: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e58: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e5c: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] chid 0 mthd 0x0080 data 0x00000000 0x10005080 0x00002021
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0080: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0084: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0088: 0xf0000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 0:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0180: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0184: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0188: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0190: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 1:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a0: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01b0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 2:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01d0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 0:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0200: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0204: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0208: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0210: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 1:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0220: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0224: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0228: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0230: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 2:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0240: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0244: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0248: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0250: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 3:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0260: 0x00000102              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0264: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0268: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0270: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 4:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0280: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0284: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0288: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0290: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 5:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02b0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 6:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02d0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 7:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02f0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 0:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0300: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0304: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0308: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0310: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 1:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0320: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0324: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0328: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0330: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 2:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0340: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0344: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0348: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0350: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 3:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0360: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0364: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0368: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0370: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 0:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0400: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0404: 0x00000009              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0408: 0x31ec6000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x040c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0410: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0414: 0x044108c0              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0418: 0x000500af              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x041c: 0x002301c7              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0420: 0x043d0857              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0424: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0428: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x042c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0430: 0xffffff00              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0434: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0438: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0440: 0x83000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0444: 0x00000410              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0448: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x044c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0450: 0x08c30ac0              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0454: 0x00200000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0458: 0x08c30ac0              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x045c: 0xf0000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0460: 0x000b2200              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0468: 0x04380e10              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x046c: 0x0000e104              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0470: 0x0000cf00              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0474: 0xffff00fe              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x047c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0480: 0x05000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0484: 0x0002ecb0              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0488: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x048c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0490: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0494: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0498: 0x00040000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04a0: 0x00000002              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b0: 0x00000780              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b8: 0x041a0690              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04bc: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c0: 0x041a0690              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c4: 0x041a0690              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c8: 0x041a0690              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d0: 0x00000311              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d4: 0x00000100              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04ec: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f0: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04fc: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0500: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0504: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0508: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x050c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0510: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0514: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0518: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x051c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0520: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0524: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x052c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0530: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x054c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0550: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0554: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0558: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x055c: 0x00000002              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 1:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0700: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0704: 0x00000011              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0708: 0x33ec6000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x070c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0710: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0714: 0x04650898              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0718: 0x0004002b              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x071c: 0x002800bf              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0720: 0x0460083f              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0724: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0728: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x072c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0730: 0xffffff00              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0734: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0738: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0740: 0x83000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0744: 0x00000430              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0748: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x074c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0750: 0x08d9ee20              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0754: 0x00200000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0758: 0x08d9ee20              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x075c: 0xf0000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0760: 0x000b2200              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0768: 0x04380e10              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x076c: 0x0000e104              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0770: 0x0000cf00              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0774: 0xffff00fe              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x077c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0780: 0x85000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0784: 0x0002ecf0              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0788: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x078c: 0xf0000001 -> 0x00000000
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0790: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0794: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0798: 0x00040000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07a0: 0x00000002              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b8: 0x04380780              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07bc: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c0: 0x04380780              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c4: 0x04380780              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c8: 0x04380780              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d0: 0x00000311              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d4: 0x00000100              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07ec: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f0: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07fc: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0800: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0804: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0808: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x080c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0810: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0814: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0818: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x081c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0820: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0824: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x082c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0830: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x084c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0850: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0854: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0858: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x085c: 0x00000002              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 2:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a00: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a04: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a08: 0x21ec4000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a0c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a10: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a14: 0x00050008              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a18: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a1c: 0x00010003              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a20: 0x00030004              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a24: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a28: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a2c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a30: 0xffffff40              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a34: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a38: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a40: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a44: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a48: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a4c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a50: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a54: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a58: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a5c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a60: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a68: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a6c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a70: 0x0000e900              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a74: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a7c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a80: 0x05000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a84: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a88: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a8c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a90: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a94: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a98: 0x00040000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aa0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0abc: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad0: 0x00110300              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad4: 0x00001100              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aec: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af0: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0afc: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b00: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b04: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b08: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b0c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b10: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b14: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b18: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b1c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b20: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b24: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b2c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b30: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b4c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b50: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b54: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b58: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b5c: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 3:
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d00: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d04: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d08: 0x21ec4000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d0c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d10: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d14: 0x00050008              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d18: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d1c: 0x00010003              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d20: 0x00030004              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d24: 0x00000001              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d28: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d2c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d30: 0xffffff40              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d34: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d38: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d40: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d44: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d48: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d4c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d50: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d54: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d58: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d5c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d60: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d68: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d6c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d70: 0x0000e900              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d74: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d7c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d80: 0x05000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d84: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d88: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d8c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d90: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d94: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d98: 0x00040000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0da0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dbc: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd0: 0x00110300              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd4: 0x00001100              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de0: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dec: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df0: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df4: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df8: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dfc: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e00: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e04: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e08: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e0c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e10: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e14: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e18: 0x00010000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e1c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e20: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e24: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e2c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e30: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e4c: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e50: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e54: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e58: 0x00000000              
Feb 14 00:36:59 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e5c: 0x00000001              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] chid 0 mthd 0x048c data 0xf0000001 0x1000748c 0x00000000
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] chid 0 mthd 0x0080 data 0x00000000 0x10005080 0x00000021
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0080: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0084: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0088: 0xf0000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 0:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0180: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0184: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0188: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0190: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 1:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a0: 0x00000001              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a4: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a8: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01b0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 2:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c4: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c8: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01d0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 0:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0200: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0204: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0208: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0210: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 1:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0220: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0224: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0228: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0230: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 2:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0240: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0244: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0248: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0250: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 3:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0260: 0x00000102              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0264: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0268: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0270: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 4:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0280: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0284: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0288: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0290: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 5:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a4: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a8: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02b0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 6:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c4: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c8: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02d0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 7:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e4: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e8: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02f0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 0:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0300: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0304: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0308: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0310: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 1:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0320: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0324: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0328: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0330: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 2:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0340: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0344: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0348: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0350: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 3:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0360: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0364: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0368: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0370: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 0:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0400: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0404: 0x00000009              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0408: 0x31ec6000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x040c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0410: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0414: 0x044108c0              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0418: 0x000500af              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x041c: 0x002301c7              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0420: 0x043d0857              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0424: 0x00000001              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0428: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x042c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0430: 0xffffff00              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0434: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0438: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0440: 0x83000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0444: 0x00000410              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0448: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x044c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0450: 0x08c30ac0              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0454: 0x00200000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0458: 0x08c30ac0              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x045c: 0xf0000001              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0460: 0x000b2200              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0468: 0x04380e10              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x046c: 0x0000e104              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0470: 0x0000cf00              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0474: 0xffff00fe              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x047c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0480: 0x05000000 -> 0x85000000
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0484: 0x0002ecb0              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0488: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x048c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0490: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0494: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0498: 0x00040000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04a0: 0x00000002              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b0: 0x00000780              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b8: 0x041a0690              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04bc: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c0: 0x041a0690              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c4: 0x041a0690              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c8: 0x041a0690              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d0: 0x00000311              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d4: 0x00000100              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e4: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e8: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04ec: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f0: 0x00010000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f4: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f8: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04fc: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0500: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0504: 0x00010000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0508: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x050c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0510: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0514: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0518: 0x00010000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x051c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0520: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0524: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x052c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0530: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x054c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0550: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0554: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0558: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x055c: 0x00000002              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 1:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0700: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0704: 0x00000011              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0708: 0x33ec6000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x070c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0710: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0714: 0x04650898              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0718: 0x0004002b              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x071c: 0x002800bf              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0720: 0x0460083f              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0724: 0x00000001              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0728: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x072c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0730: 0xffffff00              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0734: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0738: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0740: 0x83000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0744: 0x00000430              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0748: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x074c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0750: 0x08d9ee20              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0754: 0x00200000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0758: 0x08d9ee20              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x075c: 0xf0000001              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0760: 0x000b2200              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0768: 0x04380e10              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x076c: 0x0000e104              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0770: 0x0000cf00              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0774: 0xffff00fe              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x077c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0780: 0x85000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0784: 0x0002ecf0              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0788: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x078c: 0xf0000001 -> 0x00000000
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0790: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0794: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0798: 0x00040000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07a0: 0x00000002              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b8: 0x04380780              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07bc: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c0: 0x04380780              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c4: 0x04380780              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c8: 0x04380780              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d0: 0x00000311              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d4: 0x00000100              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e4: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e8: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07ec: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f0: 0x00010000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f4: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f8: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07fc: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0800: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0804: 0x00010000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0808: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x080c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0810: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0814: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0818: 0x00010000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x081c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0820: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0824: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x082c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0830: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x084c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0850: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0854: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0858: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x085c: 0x00000002              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 2:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a00: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a04: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a08: 0x21ec4000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a0c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a10: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a14: 0x00050008              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a18: 0x00000001              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a1c: 0x00010003              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a20: 0x00030004              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a24: 0x00000001              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a28: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a2c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a30: 0xffffff40              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a34: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a38: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a40: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a44: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a48: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a4c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a50: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a54: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a58: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a5c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a60: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a68: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a6c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a70: 0x0000e900              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a74: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a7c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a80: 0x05000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a84: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a88: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a8c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a90: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a94: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a98: 0x00040000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aa0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab8: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0abc: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac4: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac8: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad0: 0x00110300              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad4: 0x00001100              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae4: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae8: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aec: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af0: 0x00010000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af4: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af8: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0afc: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b00: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b04: 0x00010000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b08: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b0c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b10: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b14: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b18: 0x00010000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b1c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b20: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b24: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b2c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b30: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b4c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b50: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b54: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b58: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b5c: 0x00000001              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 3:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d00: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d04: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d08: 0x21ec4000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d0c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d10: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d14: 0x00050008              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d18: 0x00000001              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d1c: 0x00010003              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d20: 0x00030004              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d24: 0x00000001              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d28: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d2c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d30: 0xffffff40              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d34: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d38: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d40: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d44: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d48: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d4c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d50: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d54: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d58: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d5c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d60: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d68: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d6c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d70: 0x0000e900              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d74: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d7c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d80: 0x05000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d84: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d88: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d8c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d90: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d94: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d98: 0x00040000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0da0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db8: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dbc: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc4: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc8: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd0: 0x00110300              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd4: 0x00001100              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de4: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de8: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dec: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df0: 0x00010000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df4: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df8: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dfc: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e00: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e04: 0x00010000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e08: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e0c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e10: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e14: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e18: 0x00010000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e1c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e20: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e24: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e2c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e30: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e4c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e50: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e54: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e58: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e5c: 0x00000001              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] chid 0 mthd 0x0080 data 0x00000000 0x10005080 0x00000021
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0080: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0084: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0088: 0xf0000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 0:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0180: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0184: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0188: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0190: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 1:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a0: 0x00000001              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a4: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a8: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01b0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 2:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c4: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c8: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01d0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 0:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0200: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0204: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0208: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0210: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 1:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0220: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0224: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0228: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0230: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 2:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0240: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0244: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0248: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0250: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 3:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0260: 0x00000102              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0264: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0268: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0270: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 4:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0280: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0284: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0288: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0290: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 5:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a4: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a8: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02b0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 6:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c4: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c8: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02d0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 7:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e4: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e8: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02f0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 0:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0300: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0304: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0308: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0310: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 1:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0320: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0324: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0328: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0330: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 2:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0340: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0344: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0348: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0350: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 3:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0360: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0364: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0368: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0370: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 0:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0400: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0404: 0x00000009              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0408: 0x31ec6000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x040c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0410: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0414: 0x044108c0              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0418: 0x000500af              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x041c: 0x002301c7              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0420: 0x043d0857              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0424: 0x00000001              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0428: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x042c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0430: 0xffffff00              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0434: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0438: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0440: 0x83000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0444: 0x00000410              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0448: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x044c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0450: 0x08c30ac0              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0454: 0x00200000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0458: 0x08c30ac0              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x045c: 0xf0000001              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0460: 0x000b2200              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0468: 0x04380e10              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x046c: 0x0000e104              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0470: 0x0000cf00              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0474: 0xffff00fe              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x047c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0480: 0x05000000 -> 0x85000000
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0484: 0x0002ecb0              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0488: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x048c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0490: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0494: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0498: 0x00040000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04a0: 0x00000002              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b0: 0x00000780              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b8: 0x041a0690              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04bc: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c0: 0x041a0690              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c4: 0x041a0690              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c8: 0x041a0690              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d0: 0x00000311              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d4: 0x00000100              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e4: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e8: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04ec: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f0: 0x00010000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f4: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f8: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04fc: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0500: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0504: 0x00010000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0508: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x050c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0510: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0514: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0518: 0x00010000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x051c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0520: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0524: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x052c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0530: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x054c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0550: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0554: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0558: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x055c: 0x00000002              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 1:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0700: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0704: 0x00000011              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0708: 0x33ec6000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x070c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0710: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0714: 0x04650898              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0718: 0x0004002b              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x071c: 0x002800bf              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0720: 0x0460083f              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0724: 0x00000001              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0728: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x072c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0730: 0xffffff00              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0734: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0738: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0740: 0x83000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0744: 0x00000430              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0748: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x074c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0750: 0x08d9ee20              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0754: 0x00200000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0758: 0x08d9ee20              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x075c: 0xf0000001              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0760: 0x000b2200              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0768: 0x04380e10              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x076c: 0x0000e104              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0770: 0x0000cf00              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0774: 0xffff00fe              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x077c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0780: 0x85000000 -> 0x05000000
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0784: 0x0002ecf0              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0788: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x078c: 0xf0000001 -> 0x00000000
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0790: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0794: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0798: 0x00040000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07a0: 0x00000002              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b8: 0x04380780              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07bc: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c0: 0x04380780              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c4: 0x04380780              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c8: 0x04380780              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d0: 0x00000311              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d4: 0x00000100              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e4: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e8: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07ec: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f0: 0x00010000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f4: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f8: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07fc: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0800: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0804: 0x00010000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0808: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x080c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0810: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0814: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0818: 0x00010000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x081c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0820: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0824: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x082c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0830: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x084c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0850: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0854: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0858: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x085c: 0x00000002              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 2:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a00: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a04: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a08: 0x21ec4000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a0c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a10: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a14: 0x00050008              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a18: 0x00000001              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a1c: 0x00010003              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a20: 0x00030004              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a24: 0x00000001              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a28: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a2c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a30: 0xffffff40              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a34: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a38: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a40: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a44: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a48: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a4c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a50: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a54: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a58: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a5c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a60: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a68: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a6c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a70: 0x0000e900              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a74: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a7c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a80: 0x05000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a84: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a88: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a8c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a90: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a94: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a98: 0x00040000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aa0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab8: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0abc: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac4: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac8: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad0: 0x00110300              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad4: 0x00001100              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae4: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae8: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aec: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af0: 0x00010000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af4: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af8: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0afc: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b00: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b04: 0x00010000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b08: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b0c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b10: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b14: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b18: 0x00010000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b1c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b20: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b24: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b2c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b30: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b4c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b50: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b54: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b58: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b5c: 0x00000001              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 3:
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d00: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d04: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d08: 0x21ec4000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d0c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d10: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d14: 0x00050008              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d18: 0x00000001              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d1c: 0x00010003              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d20: 0x00030004              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d24: 0x00000001              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d28: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d2c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d30: 0xffffff40              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d34: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d38: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d40: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d44: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d48: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d4c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d50: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d54: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d58: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d5c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d60: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d68: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d6c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d70: 0x0000e900              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d74: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d7c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d80: 0x05000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d84: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d88: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d8c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d90: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d94: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d98: 0x00040000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0da0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db8: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dbc: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc4: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc8: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd0: 0x00110300              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd4: 0x00001100              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de0: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de4: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de8: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dec: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df0: 0x00010000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df4: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df8: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dfc: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e00: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e04: 0x00010000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e08: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e0c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e10: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e14: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e18: 0x00010000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e1c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e20: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e24: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e2c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e30: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e4c: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e50: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e54: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e58: 0x00000000              
Feb 14 00:37:00 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e5c: 0x00000001              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] chid 0 mthd 0x078c data 0xf0000001 0x1000778c 0x00000000
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] chid 0 mthd 0x0080 data 0x00000000 0x10005080 0x00000021
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0080: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0084: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0088: 0xf0000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 0:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0180: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0184: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0188: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0190: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 1:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a0: 0x00000001              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a4: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a8: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01b0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 2:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c4: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c8: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01d0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 0:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0200: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0204: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0208: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0210: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 1:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0220: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0224: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0228: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0230: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 2:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0240: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0244: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0248: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0250: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 3:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0260: 0x00000102              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0264: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0268: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0270: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 4:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0280: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0284: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0288: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0290: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 5:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a4: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a8: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02b0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 6:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c4: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c8: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02d0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 7:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e4: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e8: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02f0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 0:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0300: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0304: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0308: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0310: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 1:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0320: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0324: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0328: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0330: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 2:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0340: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0344: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0348: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0350: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 3:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0360: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0364: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0368: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0370: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 0:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0400: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0404: 0x00000009              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0408: 0x31ec6000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x040c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0410: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0414: 0x044108c0              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0418: 0x000500af              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x041c: 0x002301c7              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0420: 0x043d0857              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0424: 0x00000001              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0428: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x042c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0430: 0xffffff00              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0434: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0438: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0440: 0x83000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0444: 0x00000410              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0448: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x044c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0450: 0x08c30ac0              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0454: 0x00200000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0458: 0x08c30ac0              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x045c: 0xf0000001              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0460: 0x000b2200              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0468: 0x04380e10              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x046c: 0x0000e104              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0470: 0x0000cf00              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0474: 0xffff00fe              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x047c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0480: 0x05000000 -> 0x85000000
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0484: 0x0002ecb0              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0488: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x048c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0490: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0494: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0498: 0x00040000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04a0: 0x00000002              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b0: 0x00000780              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b8: 0x041a0690              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04bc: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c0: 0x041a0690              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c4: 0x041a0690              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c8: 0x041a0690              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d0: 0x00000311              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d4: 0x00000100              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e4: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e8: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04ec: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f0: 0x00010000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f4: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f8: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04fc: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0500: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0504: 0x00010000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0508: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x050c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0510: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0514: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0518: 0x00010000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x051c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0520: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0524: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x052c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0530: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x054c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0550: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0554: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0558: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x055c: 0x00000002              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 1:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0700: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0704: 0x00000011              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0708: 0x33ec6000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x070c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0710: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0714: 0x04650898              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0718: 0x0004002b              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x071c: 0x002800bf              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0720: 0x0460083f              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0724: 0x00000001              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0728: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x072c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0730: 0xffffff00              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0734: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0738: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0740: 0x83000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0744: 0x00000430              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0748: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x074c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0750: 0x08d9ee20              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0754: 0x00200000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0758: 0x08d9ee20              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x075c: 0xf0000001              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0760: 0x000b2200              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0768: 0x04380e10              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x076c: 0x0000e104              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0770: 0x0000cf00              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0774: 0xffff00fe              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x077c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0780: 0x85000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0784: 0x0002ecf0              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0788: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x078c: 0xf0000001 -> 0x00000000
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0790: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0794: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0798: 0x00040000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07a0: 0x00000002              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b8: 0x04380780              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07bc: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c0: 0x04380780              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c4: 0x04380780              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c8: 0x04380780              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d0: 0x00000311              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d4: 0x00000100              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e4: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e8: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07ec: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f0: 0x00010000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f4: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f8: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07fc: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0800: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0804: 0x00010000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0808: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x080c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0810: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0814: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0818: 0x00010000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x081c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0820: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0824: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x082c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0830: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x084c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0850: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0854: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0858: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x085c: 0x00000002              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 2:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a00: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a04: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a08: 0x21ec4000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a0c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a10: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a14: 0x00050008              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a18: 0x00000001              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a1c: 0x00010003              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a20: 0x00030004              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a24: 0x00000001              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a28: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a2c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a30: 0xffffff40              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a34: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a38: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a40: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a44: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a48: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a4c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a50: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a54: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a58: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a5c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a60: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a68: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a6c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a70: 0x0000e900              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a74: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a7c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a80: 0x05000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a84: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a88: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a8c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a90: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a94: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a98: 0x00040000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aa0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab8: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0abc: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac4: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac8: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad0: 0x00110300              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad4: 0x00001100              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae4: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae8: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aec: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af0: 0x00010000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af4: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af8: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0afc: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b00: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b04: 0x00010000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b08: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b0c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b10: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b14: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b18: 0x00010000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b1c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b20: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b24: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b2c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b30: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b4c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b50: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b54: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b58: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b5c: 0x00000001              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 3:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d00: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d04: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d08: 0x21ec4000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d0c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d10: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d14: 0x00050008              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d18: 0x00000001              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d1c: 0x00010003              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d20: 0x00030004              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d24: 0x00000001              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d28: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d2c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d30: 0xffffff40              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d34: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d38: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d40: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d44: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d48: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d4c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d50: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d54: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d58: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d5c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d60: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d68: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d6c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d70: 0x0000e900              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d74: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d7c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d80: 0x05000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d84: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d88: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d8c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d90: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d94: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d98: 0x00040000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0da0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db8: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dbc: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc4: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc8: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd0: 0x00110300              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd4: 0x00001100              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de4: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de8: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dec: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df0: 0x00010000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df4: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df8: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dfc: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e00: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e04: 0x00010000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e08: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e0c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e10: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e14: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e18: 0x00010000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e1c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e20: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e24: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e2c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e30: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e4c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e50: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e54: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e58: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e5c: 0x00000001              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] chid 0 mthd 0x0080 data 0x00000000 0x10005080 0x00002021
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0080: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0084: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0088: 0xf0000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 0:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0180: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0184: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0188: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0190: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 1:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a0: 0x00000001              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a4: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01a8: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01b0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - DAC 2:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c4: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01c8: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x01d0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 0:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0200: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0204: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0208: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0210: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 1:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0220: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0224: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0228: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0230: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 2:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0240: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0244: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0248: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0250: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 3:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0260: 0x00000102              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0264: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0268: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0270: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 4:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0280: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0284: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0288: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0290: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 5:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a4: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02a8: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02b0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 6:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c4: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02c8: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02d0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - SOR 7:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e4: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02e8: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x02f0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 0:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0300: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0304: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0308: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0310: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 1:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0320: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0324: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0328: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0330: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 2:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0340: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0344: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0348: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0350: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - PIOR 3:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0360: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0364: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0368: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0370: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 0:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0400: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0404: 0x00000009              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0408: 0x31ec6000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x040c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0410: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0414: 0x044108c0              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0418: 0x000500af              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x041c: 0x002301c7              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0420: 0x043d0857              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0424: 0x00000001              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0428: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x042c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0430: 0xffffff00              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0434: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0438: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0440: 0x83000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0444: 0x00000410              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0448: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x044c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0450: 0x08c30ac0              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0454: 0x00200000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0458: 0x08c30ac0              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x045c: 0xf0000001              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0460: 0x000b2200              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0468: 0x04380e10              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x046c: 0x0000e104              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0470: 0x0000cf00              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0474: 0xffff00fe              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x047c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0480: 0x05000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0484: 0x0002ecb0              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0488: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x048c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0490: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0494: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0498: 0x00040000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04a0: 0x00000002              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b0: 0x00000780              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04b8: 0x041a0690              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04bc: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c0: 0x041a0690              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c4: 0x041a0690              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04c8: 0x041a0690              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d0: 0x00000311              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04d4: 0x00000100              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e4: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04e8: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04ec: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f0: 0x00010000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f4: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04f8: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x04fc: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0500: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0504: 0x00010000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0508: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x050c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0510: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0514: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0518: 0x00010000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x051c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0520: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0524: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x052c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0530: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x054c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0550: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0554: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0558: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x055c: 0x00000002              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 1:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0700: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0704: 0x00000011              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0708: 0x33ec6000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x070c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0710: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0714: 0x04650898              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0718: 0x0004002b              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x071c: 0x002800bf              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0720: 0x0460083f              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0724: 0x00000001              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0728: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x072c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0730: 0xffffff00              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0734: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0738: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0740: 0x83000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0744: 0x00000430              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0748: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x074c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0750: 0x08d9ee20              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0754: 0x00200000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0758: 0x08d9ee20              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x075c: 0xf0000001              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0760: 0x000b2200              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0768: 0x04380e10              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x076c: 0x0000e104              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0770: 0x0000cf00              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0774: 0xffff00fe              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x077c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0780: 0x85000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0784: 0x0002ecf0              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0788: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x078c: 0xf0000001 -> 0x00000000
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0790: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0794: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0798: 0x00040000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07a0: 0x00000002              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07b8: 0x04380780              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07bc: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c0: 0x04380780              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c4: 0x04380780              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07c8: 0x04380780              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d0: 0x00000311              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07d4: 0x00000100              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e4: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07e8: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07ec: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f0: 0x00010000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f4: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07f8: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x07fc: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0800: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0804: 0x00010000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0808: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x080c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0810: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0814: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0818: 0x00010000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x081c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0820: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0824: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x082c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0830: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x084c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0850: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0854: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0858: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x085c: 0x00000002              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 2:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a00: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a04: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a08: 0x21ec4000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a0c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a10: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a14: 0x00050008              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a18: 0x00000001              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a1c: 0x00010003              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a20: 0x00030004              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a24: 0x00000001              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a28: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a2c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a30: 0xffffff40              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a34: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a38: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a40: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a44: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a48: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a4c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a50: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a54: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a58: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a5c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a60: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a68: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a6c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a70: 0x0000e900              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a74: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a7c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a80: 0x05000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a84: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a88: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a8c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a90: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a94: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0a98: 0x00040000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aa0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ab8: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0abc: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac4: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ac8: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad0: 0x00110300              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ad4: 0x00001100              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae4: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0ae8: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0aec: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af0: 0x00010000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af4: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0af8: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0afc: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b00: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b04: 0x00010000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b08: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b0c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b10: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b14: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b18: 0x00010000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b1c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b20: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b24: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b2c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b30: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b4c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b50: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b54: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b58: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0b5c: 0x00000001              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0] Core - HEAD 3:
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d00: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d04: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d08: 0x21ec4000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d0c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d10: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d14: 0x00050008              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d18: 0x00000001              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d1c: 0x00010003              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d20: 0x00030004              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d24: 0x00000001              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d28: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d2c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d30: 0xffffff40              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d34: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d38: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d40: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d44: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d48: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d4c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d50: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d54: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d58: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d5c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d60: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d68: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d6c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d70: 0x0000e900              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d74: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d7c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d80: 0x05000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d84: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d88: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d8c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d90: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d94: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0d98: 0x00040000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0da0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0db8: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dbc: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc4: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dc8: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd0: 0x00110300              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dd4: 0x00001100              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de0: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de4: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0de8: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dec: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df0: 0x00010000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df4: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0df8: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0dfc: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e00: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e04: 0x00010000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e08: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e0c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e10: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e14: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e18: 0x00010000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e1c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e20: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e24: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e2c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e30: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e4c: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e50: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e54: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e58: 0x00000000              
Feb 14 00:37:01 MM-Home kernel: nouveau E[   PDISP][0000:02:00.0]         0x0e5c: 0x00000001              
-- Reboot --
Feb 14 11:49:11 linux-ytaf systemd-journal[187]: Runtime journal is using 8.0M (max allowed 394.0M, trying to leave 591.0M free of 3.8G available → current limit 394.0M).
Feb 14 11:49:11 linux-ytaf systemd-journal[187]: Runtime journal is using 8.0M (max allowed 394.0M, trying to leave 591.0M free of 3.8G available → current limit 394.0M).
Feb 14 11:49:11 linux-ytaf kernel: microcode: CPU0 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 11:49:11 linux-ytaf kernel: Initializing cgroup subsys cpuset
Feb 14 11:49:11 linux-ytaf kernel: Initializing cgroup subsys cpu
Feb 14 11:49:11 linux-ytaf kernel: Initializing cgroup subsys cpuacct
Feb 14 11:49:11 linux-ytaf kernel: Linux version 4.1.15-8-default (geeko@buildhost) (gcc version 4.8.5 (SUSE Linux) ) #1 SMP PREEMPT Wed Jan 20 16:41:00 UTC 2016 (0e3b3ab)
Feb 14 11:49:11 linux-ytaf kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.1.15-8-default root=UUID=21024970-7a27-4114-8525-d8dd026f23b6 ro resume=/dev/sdb2 splash=silent quiet showopts
Feb 14 11:49:11 linux-ytaf kernel: e820: BIOS-provided physical RAM map:
Feb 14 11:49:11 linux-ytaf kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Feb 14 11:49:11 linux-ytaf kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
Feb 14 11:49:11 linux-ytaf kernel: BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable
Feb 14 11:49:11 linux-ytaf kernel: BIOS-e820: [mem 0x0000000020000000-0x00000000201fffff] reserved
Feb 14 11:49:11 linux-ytaf kernel: BIOS-e820: [mem 0x0000000020200000-0x000000003fffffff] usable
Feb 14 11:49:11 linux-ytaf kernel: BIOS-e820: [mem 0x0000000040000000-0x00000000401fffff] reserved
Feb 14 11:49:11 linux-ytaf kernel: BIOS-e820: [mem 0x0000000040200000-0x00000000ca38efff] usable
Feb 14 11:49:11 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ca38f000-0x00000000ca5f1fff] reserved
Feb 14 11:49:11 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ca5f2000-0x00000000ca679fff] ACPI NVS
Feb 14 11:49:11 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ca67a000-0x00000000ca93efff] reserved
Feb 14 11:49:11 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ca93f000-0x00000000cab83fff] ACPI NVS
Feb 14 11:49:11 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cab84000-0x00000000cab91fff] ACPI data
Feb 14 11:49:11 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cab92000-0x00000000cabbefff] ACPI NVS
Feb 14 11:49:11 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cabbf000-0x00000000cabc3fff] ACPI data
Feb 14 11:49:11 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cabc4000-0x00000000cac06fff] ACPI NVS
Feb 14 11:49:11 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cac07000-0x00000000caffffff] usable
Feb 14 11:49:11 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cb800000-0x00000000cf9fffff] reserved
Feb 14 11:49:11 linux-ytaf kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Feb 14 11:49:11 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Feb 14 11:49:11 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Feb 14 11:49:11 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Feb 14 11:49:11 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Feb 14 11:49:11 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Feb 14 11:49:11 linux-ytaf kernel: BIOS-e820: [mem 0x0000000100000000-0x000000022f5fffff] usable
Feb 14 11:49:11 linux-ytaf kernel: NX (Execute Disable) protection: active
Feb 14 11:49:11 linux-ytaf kernel: e820: update [mem 0x0c826018-0x0c835c57] usable ==> usable
Feb 14 11:49:11 linux-ytaf kernel: e820: update [mem 0x0c836018-0x0c846057] usable ==> usable
Feb 14 11:49:11 linux-ytaf kernel: e820: update [mem 0x0c847018-0x0c856857] usable ==> usable
Feb 14 11:49:11 linux-ytaf kernel: e820: update [mem 0x0c857018-0x0c85ae57] usable ==> usable
Feb 14 11:49:11 linux-ytaf kernel: extended physical RAM map:
Feb 14 11:49:11 linux-ytaf kernel: reserve setup_data: [mem 0x0000000000000000-0x000000000009efff] usable
Feb 14 11:49:11 linux-ytaf kernel: reserve setup_data: [mem 0x000000000009f000-0x000000000009ffff] reserved
Feb 14 11:49:11 linux-ytaf kernel: reserve setup_data: [mem 0x0000000000100000-0x000000000c826017] usable
Feb 14 11:49:11 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c826018-0x000000000c835c57] usable
Feb 14 11:49:11 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c835c58-0x000000000c836017] usable
Feb 14 11:49:11 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c836018-0x000000000c846057] usable
Feb 14 11:49:11 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c846058-0x000000000c847017] usable
Feb 14 11:49:11 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c847018-0x000000000c856857] usable
Feb 14 11:49:11 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c856858-0x000000000c857017] usable
Feb 14 11:49:11 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c857018-0x000000000c85ae57] usable
Feb 14 11:49:11 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c85ae58-0x000000001fffffff] usable
Feb 14 11:49:11 linux-ytaf kernel: reserve setup_data: [mem 0x0000000020000000-0x00000000201fffff] reserved
Feb 14 11:49:11 linux-ytaf kernel: reserve setup_data: [mem 0x0000000020200000-0x000000003fffffff] usable
Feb 14 11:49:11 linux-ytaf kernel: reserve setup_data: [mem 0x0000000040000000-0x00000000401fffff] reserved
Feb 14 11:49:11 linux-ytaf kernel: reserve setup_data: [mem 0x0000000040200000-0x00000000ca38efff] usable
Feb 14 11:49:11 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ca38f000-0x00000000ca5f1fff] reserved
Feb 14 11:49:11 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ca5f2000-0x00000000ca679fff] ACPI NVS
Feb 14 11:49:11 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ca67a000-0x00000000ca93efff] reserved
Feb 14 11:49:11 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ca93f000-0x00000000cab83fff] ACPI NVS
Feb 14 11:49:11 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cab84000-0x00000000cab91fff] ACPI data
Feb 14 11:49:11 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cab92000-0x00000000cabbefff] ACPI NVS
Feb 14 11:49:11 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cabbf000-0x00000000cabc3fff] ACPI data
Feb 14 11:49:11 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cabc4000-0x00000000cac06fff] ACPI NVS
Feb 14 11:49:11 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cac07000-0x00000000caffffff] usable
Feb 14 11:49:11 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cb800000-0x00000000cf9fffff] reserved
Feb 14 11:49:11 linux-ytaf kernel: reserve setup_data: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Feb 14 11:49:11 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Feb 14 11:49:11 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Feb 14 11:49:11 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Feb 14 11:49:11 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Feb 14 11:49:11 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Feb 14 11:49:11 linux-ytaf kernel: reserve setup_data: [mem 0x0000000100000000-0x000000022f5fffff] usable
Feb 14 11:49:11 linux-ytaf kernel: efi: EFI v2.31 by American Megatrends
Feb 14 11:49:11 linux-ytaf kernel: efi:  ACPI=0xcab84000  ACPI 2.0=0xcab84000  SMBIOS=0xca427e98  MPS=0xfc990 
Feb 14 11:49:11 linux-ytaf kernel: SMBIOS 2.6 present.
Feb 14 11:49:11 linux-ytaf kernel: DMI: System manufacturer System Product Name/MAXIMUS IV GENE-Z/GEN3, BIOS 3603 11/09/2012
Feb 14 11:49:11 linux-ytaf kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Feb 14 11:49:11 linux-ytaf kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Feb 14 11:49:11 linux-ytaf kernel: AGP: No AGP bridge found
Feb 14 11:49:11 linux-ytaf kernel: e820: last_pfn = 0x22f600 max_arch_pfn = 0x400000000
Feb 14 11:49:11 linux-ytaf kernel: MTRR default type: uncachable
Feb 14 11:49:11 linux-ytaf kernel: MTRR fixed ranges enabled:
Feb 14 11:49:11 linux-ytaf kernel:   00000-9FFFF write-back
Feb 14 11:49:11 linux-ytaf kernel:   A0000-BFFFF uncachable
Feb 14 11:49:11 linux-ytaf kernel:   C0000-D3FFF write-protect
Feb 14 11:49:11 linux-ytaf kernel:   D4000-DFFFF uncachable
Feb 14 11:49:11 linux-ytaf kernel:   E0000-E7FFF write-through
Feb 14 11:49:11 linux-ytaf kernel:   E8000-FFFFF write-protect
Feb 14 11:49:11 linux-ytaf kernel: MTRR variable ranges enabled:
Feb 14 11:49:11 linux-ytaf kernel:   0 base 000000000 mask E00000000 write-back
Feb 14 11:49:11 linux-ytaf kernel:   1 base 200000000 mask FE0000000 write-back
Feb 14 11:49:11 linux-ytaf kernel:   2 base 220000000 mask FF0000000 write-back
Feb 14 11:49:11 linux-ytaf kernel:   3 base 0E0000000 mask FE0000000 uncachable
Feb 14 11:49:11 linux-ytaf kernel:   4 base 0D0000000 mask FF0000000 uncachable
Feb 14 11:49:11 linux-ytaf kernel:   5 base 0CC000000 mask FFC000000 uncachable
Feb 14 11:49:11 linux-ytaf kernel:   6 base 0CB800000 mask FFF800000 uncachable
Feb 14 11:49:11 linux-ytaf kernel:   7 base 22F800000 mask FFF800000 uncachable
Feb 14 11:49:11 linux-ytaf kernel:   8 base 22F600000 mask FFFE00000 uncachable
Feb 14 11:49:11 linux-ytaf kernel:   9 disabled
Feb 14 11:49:11 linux-ytaf kernel: PAT configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- UC  
Feb 14 11:49:11 linux-ytaf kernel: e820: update [mem 0xcb800000-0xffffffff] usable ==> reserved
Feb 14 11:49:11 linux-ytaf kernel: e820: last_pfn = 0xcb000 max_arch_pfn = 0x400000000
Feb 14 11:49:11 linux-ytaf kernel: found SMP MP-table at [mem 0x000fcd30-0x000fcd3f] mapped at [ffff8800000fcd30]
Feb 14 11:49:11 linux-ytaf kernel: Scanning 1 areas for low memory corruption
Feb 14 11:49:11 linux-ytaf kernel: Base memory trampoline at [ffff880000097000] 97000 size 24576
Feb 14 11:49:11 linux-ytaf kernel: reserving inaccessible SNB gfx pages
Feb 14 11:49:11 linux-ytaf kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
Feb 14 11:49:11 linux-ytaf kernel:  [mem 0x00000000-0x000fffff] page 4k
Feb 14 11:49:11 linux-ytaf kernel: BRK [0x0e21a000, 0x0e21afff] PGTABLE
Feb 14 11:49:11 linux-ytaf kernel: BRK [0x0e21b000, 0x0e21bfff] PGTABLE
Feb 14 11:49:11 linux-ytaf kernel: BRK [0x0e21c000, 0x0e21cfff] PGTABLE
Feb 14 11:49:11 linux-ytaf kernel: init_memory_mapping: [mem 0x22f400000-0x22f5fffff]
Feb 14 11:49:11 linux-ytaf kernel:  [mem 0x22f400000-0x22f5fffff] page 2M
Feb 14 11:49:11 linux-ytaf kernel: BRK [0x0e21d000, 0x0e21dfff] PGTABLE
Feb 14 11:49:11 linux-ytaf kernel: init_memory_mapping: [mem 0x220000000-0x22f3fffff]
Feb 14 11:49:11 linux-ytaf kernel:  [mem 0x220000000-0x22f3fffff] page 2M
Feb 14 11:49:11 linux-ytaf kernel: init_memory_mapping: [mem 0x200000000-0x21fffffff]
Feb 14 11:49:11 linux-ytaf kernel:  [mem 0x200000000-0x21fffffff] page 2M
Feb 14 11:49:11 linux-ytaf kernel: init_memory_mapping: [mem 0x00100000-0x1fffffff]
Feb 14 11:49:11 linux-ytaf kernel:  [mem 0x00100000-0x001fffff] page 4k
Feb 14 11:49:11 linux-ytaf kernel:  [mem 0x00200000-0x1fffffff] page 2M
Feb 14 11:49:11 linux-ytaf kernel: init_memory_mapping: [mem 0x20200000-0x3fffffff]
Feb 14 11:49:11 linux-ytaf kernel:  [mem 0x20200000-0x3fffffff] page 2M
Feb 14 11:49:11 linux-ytaf kernel: init_memory_mapping: [mem 0x40200000-0xca38efff]
Feb 14 11:49:11 linux-ytaf kernel:  [mem 0x40200000-0xca1fffff] page 2M
Feb 14 11:49:11 linux-ytaf kernel:  [mem 0xca200000-0xca38efff] page 4k
Feb 14 11:49:11 linux-ytaf kernel: BRK [0x0e21e000, 0x0e21efff] PGTABLE
Feb 14 11:49:11 linux-ytaf kernel: BRK [0x0e21f000, 0x0e21ffff] PGTABLE
Feb 14 11:49:11 linux-ytaf kernel: init_memory_mapping: [mem 0xcac07000-0xcaffffff]
Feb 14 11:49:11 linux-ytaf kernel:  [mem 0xcac07000-0xcadfffff] page 4k
Feb 14 11:49:11 linux-ytaf kernel:  [mem 0xcae00000-0xcaffffff] page 2M
Feb 14 11:49:11 linux-ytaf kernel: init_memory_mapping: [mem 0x100000000-0x1ffffffff]
Feb 14 11:49:11 linux-ytaf kernel:  [mem 0x100000000-0x1ffffffff] page 2M
Feb 14 11:49:11 linux-ytaf kernel: RAMDISK: [mem 0x00457000-0x00ffafff]
Feb 14 11:49:11 linux-ytaf kernel: ACPI: Early table checksum verification disabled
Feb 14 11:49:11 linux-ytaf kernel: ACPI: RSDP 0x00000000CAB84000 000024 (v02 ALASKA)
Feb 14 11:49:11 linux-ytaf kernel: ACPI: XSDT 0x00000000CAB84078 000064 (v01 ALASKA A M I    01072009 AMI  00010013)
Feb 14 11:49:11 linux-ytaf kernel: ACPI: FACP 0x00000000CAB8FC78 0000F4 (v04 ALASKA A M I    01072009 AMI  00010013)
Feb 14 11:49:11 linux-ytaf kernel: ACPI: DSDT 0x00000000CAB84170 00BB02 (v02 ALASKA A M I    00000015 INTL 20051117)
Feb 14 11:49:11 linux-ytaf kernel: ACPI: FACS 0x00000000CABBDF80 000040
Feb 14 11:49:11 linux-ytaf kernel: ACPI: APIC 0x00000000CAB8FD70 000092 (v03 ALASKA A M I    01072009 AMI  00010013)
Feb 14 11:49:11 linux-ytaf kernel: ACPI: MCFG 0x00000000CAB8FE08 00003C (v01 ALASKA A M I    01072009 MSFT 00000097)
Feb 14 11:49:11 linux-ytaf kernel: ACPI: HPET 0x00000000CAB8FE48 000038 (v01 ALASKA A M I    01072009 AMI. 00000005)
Feb 14 11:49:11 linux-ytaf kernel: ACPI: SSDT 0x00000000CAB8FE80 00036D (v01 SataRe SataTabl 00001000 INTL 20091112)
Feb 14 11:49:11 linux-ytaf kernel: ACPI: SSDT 0x00000000CAB901F0 0009AA (v01 PmRef  Cpu0Ist  00003000 INTL 20051117)
Feb 14 11:49:11 linux-ytaf kernel: ACPI: SSDT 0x00000000CAB90BA0 000A92 (v01 PmRef  CpuPm    00003000 INTL 20051117)
Feb 14 11:49:11 linux-ytaf kernel: ACPI: BGRT 0x00000000CAB91690 000038 (v00 ALASKA A M I    01072009 AMI  00010013)
Feb 14 11:49:11 linux-ytaf kernel: ACPI: Local APIC address 0xfee00000
Feb 14 11:49:11 linux-ytaf kernel: No NUMA configuration found
Feb 14 11:49:11 linux-ytaf kernel: Faking a node at [mem 0x0000000000000000-0x000000022f5fffff]
Feb 14 11:49:11 linux-ytaf kernel: NODE_DATA(0) allocated [mem 0x22f5e5000-0x22f5f8fff]
Feb 14 11:49:11 linux-ytaf kernel:  [ffffea0000000000-ffffea0008bfffff] PMD -> [ffff880226c00000-ffff88022ebfffff] on node 0
Feb 14 11:49:11 linux-ytaf kernel: Zone ranges:
Feb 14 11:49:11 linux-ytaf kernel:   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
Feb 14 11:49:11 linux-ytaf kernel:   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
Feb 14 11:49:11 linux-ytaf kernel:   Normal   [mem 0x0000000100000000-0x000000022f5fffff]
Feb 14 11:49:11 linux-ytaf kernel: Movable zone start for each node
Feb 14 11:49:11 linux-ytaf kernel: Early memory node ranges
Feb 14 11:49:11 linux-ytaf kernel:   node   0: [mem 0x0000000000001000-0x000000000009efff]
Feb 14 11:49:11 linux-ytaf kernel:   node   0: [mem 0x0000000000100000-0x000000001fffffff]
Feb 14 11:49:11 linux-ytaf kernel:   node   0: [mem 0x0000000020200000-0x000000003fffffff]
Feb 14 11:49:11 linux-ytaf kernel:   node   0: [mem 0x0000000040200000-0x00000000ca38efff]
Feb 14 11:49:11 linux-ytaf kernel:   node   0: [mem 0x00000000cac07000-0x00000000caffffff]
Feb 14 11:49:11 linux-ytaf kernel:   node   0: [mem 0x0000000100000000-0x000000022f5fffff]
Feb 14 11:49:11 linux-ytaf kernel: Initmem setup node 0 [mem 0x0000000000001000-0x000000022f5fffff]
Feb 14 11:49:11 linux-ytaf kernel: On node 0 totalpages: 2070822
Feb 14 11:49:11 linux-ytaf kernel:   DMA zone: 64 pages used for memmap
Feb 14 11:49:11 linux-ytaf kernel:   DMA zone: 3138 pages reserved
Feb 14 11:49:11 linux-ytaf kernel:   DMA zone: 3998 pages, LIFO batch:0
Feb 14 11:49:11 linux-ytaf kernel:   DMA32 zone: 12879 pages used for memmap
Feb 14 11:49:11 linux-ytaf kernel:   DMA32 zone: 824200 pages, LIFO batch:31
Feb 14 11:49:11 linux-ytaf kernel:   Normal zone: 19416 pages used for memmap
Feb 14 11:49:11 linux-ytaf kernel:   Normal zone: 1242624 pages, LIFO batch:31
Feb 14 11:49:11 linux-ytaf kernel: tboot: non-0 tboot_addr but it is not of type E820_RESERVED
Feb 14 11:49:11 linux-ytaf kernel: ACPI: PM-Timer IO Port: 0x408
Feb 14 11:49:11 linux-ytaf kernel: ACPI: Local APIC address 0xfee00000
Feb 14 11:49:11 linux-ytaf kernel: ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
Feb 14 11:49:11 linux-ytaf kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
Feb 14 11:49:11 linux-ytaf kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Feb 14 11:49:11 linux-ytaf kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Feb 14 11:49:11 linux-ytaf kernel: ACPI: IRQ0 used by override.
Feb 14 11:49:11 linux-ytaf kernel: ACPI: IRQ9 used by override.
Feb 14 11:49:11 linux-ytaf kernel: Using ACPI (MADT) for SMP configuration information
Feb 14 11:49:11 linux-ytaf kernel: ACPI: HPET id: 0x8086a701 base: 0xfed00000
Feb 14 11:49:11 linux-ytaf kernel: smpboot: Allowing 8 CPUs, 0 hotplug CPUs
Feb 14 11:49:11 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
Feb 14 11:49:11 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Feb 14 11:49:11 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000fffff]
Feb 14 11:49:11 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c826000-0x0c826fff]
Feb 14 11:49:11 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c835000-0x0c835fff]
Feb 14 11:49:11 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c836000-0x0c836fff]
Feb 14 11:49:11 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c846000-0x0c846fff]
Feb 14 11:49:11 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c847000-0x0c847fff]
Feb 14 11:49:11 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c856000-0x0c856fff]
Feb 14 11:49:11 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c857000-0x0c857fff]
Feb 14 11:49:11 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c85a000-0x0c85afff]
Feb 14 11:49:11 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x20000000-0x201fffff]
Feb 14 11:49:11 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x40000000-0x401fffff]
Feb 14 11:49:11 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xca38f000-0xca5f1fff]
Feb 14 11:49:11 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xca5f2000-0xca679fff]
Feb 14 11:49:11 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xca67a000-0xca93efff]
Feb 14 11:49:11 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xca93f000-0xcab83fff]
Feb 14 11:49:11 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcab84000-0xcab91fff]
Feb 14 11:49:11 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcab92000-0xcabbefff]
Feb 14 11:49:11 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcabbf000-0xcabc3fff]
Feb 14 11:49:11 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcabc4000-0xcac06fff]
Feb 14 11:49:11 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcb000000-0xcb7fffff]
Feb 14 11:49:11 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcb800000-0xcf9fffff]
Feb 14 11:49:11 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcfa00000-0xf7ffffff]
Feb 14 11:49:11 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
Feb 14 11:49:11 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfc000000-0xfebfffff]
Feb 14 11:49:11 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
Feb 14 11:49:11 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfec01000-0xfecfffff]
Feb 14 11:49:11 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed00000-0xfed03fff]
Feb 14 11:49:11 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed04000-0xfed1bfff]
Feb 14 11:49:11 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Feb 14 11:49:11 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed20000-0xfedfffff]
Feb 14 11:49:11 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
Feb 14 11:49:11 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfee01000-0xfeffffff]
Feb 14 11:49:11 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Feb 14 11:49:11 linux-ytaf kernel: e820: [mem 0xcfa00000-0xf7ffffff] available for PCI devices
Feb 14 11:49:11 linux-ytaf kernel: Booting paravirtualized kernel on bare hardware
Feb 14 11:49:11 linux-ytaf kernel: clocksource refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
Feb 14 11:49:11 linux-ytaf kernel: setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:8 nr_node_ids:1
Feb 14 11:49:11 linux-ytaf kernel: PERCPU: Embedded 33 pages/cpu @ffff88022f200000 s97368 r8192 d29608 u262144
Feb 14 11:49:11 linux-ytaf kernel: pcpu-alloc: s97368 r8192 d29608 u262144 alloc=1*2097152
Feb 14 11:49:11 linux-ytaf kernel: pcpu-alloc: [0] 0 1 2 3 4 5 6 7 
Feb 14 11:49:11 linux-ytaf kernel: Built 1 zonelists in Node order, mobility grouping on.  Total pages: 2035325
Feb 14 11:49:11 linux-ytaf kernel: Policy zone: Normal
Feb 14 11:49:11 linux-ytaf kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.1.15-8-default root=UUID=21024970-7a27-4114-8525-d8dd026f23b6 ro resume=/dev/sdb2 splash=silent quiet showopts
Feb 14 11:49:11 linux-ytaf kernel: log_buf_len individual max cpu contribution: 32768 bytes
Feb 14 11:49:11 linux-ytaf kernel: log_buf_len total cpu_extra contributions: 229376 bytes
Feb 14 11:49:11 linux-ytaf kernel: log_buf_len min size: 262144 bytes
Feb 14 11:49:11 linux-ytaf kernel: log_buf_len: 524288 bytes
Feb 14 11:49:11 linux-ytaf kernel: early log buf free: 245492(93%)
Feb 14 11:49:11 linux-ytaf kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
Feb 14 11:49:11 linux-ytaf kernel: xsave: enabled xstate_bv 0x7, cntxt size 0x340 using standard form
Feb 14 11:49:11 linux-ytaf kernel: AGP: Checking aperture...
Feb 14 11:49:11 linux-ytaf kernel: AGP: No AGP bridge found
Feb 14 11:49:11 linux-ytaf kernel: Memory: 7863196K/8283288K available (6547K kernel code, 1084K rwdata, 4848K rodata, 1560K init, 1516K bss, 420092K reserved, 0K cma-reserved)
Feb 14 11:49:11 linux-ytaf kernel: Preemptible hierarchical RCU implementation.
Feb 14 11:49:11 linux-ytaf kernel:         RCU dyntick-idle grace-period acceleration is enabled.
Feb 14 11:49:11 linux-ytaf kernel:         RCU restricting CPUs from NR_CPUS=512 to nr_cpu_ids=8.
Feb 14 11:49:11 linux-ytaf kernel: RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
Feb 14 11:49:11 linux-ytaf kernel: NR_IRQS:33024 nr_irqs:488 16
Feb 14 11:49:11 linux-ytaf kernel:         Offload RCU callbacks from all CPUs
Feb 14 11:49:11 linux-ytaf kernel:         Offload RCU callbacks from CPUs: 0-7.
Feb 14 11:49:11 linux-ytaf kernel: Console: colour dummy device 80x25
Feb 14 11:49:11 linux-ytaf kernel: console [tty0] enabled
Feb 14 11:49:11 linux-ytaf kernel: clocksource hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484882848 ns
Feb 14 11:49:11 linux-ytaf kernel: hpet clockevent registered
Feb 14 11:49:11 linux-ytaf kernel: tsc: Fast TSC calibration using PIT
Feb 14 11:49:11 linux-ytaf kernel: tsc: Detected 3411.164 MHz processor
Feb 14 11:49:11 linux-ytaf kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 6822.32 BogoMIPS (lpj=13644656)
Feb 14 11:49:11 linux-ytaf kernel: pid_max: default: 32768 minimum: 301
Feb 14 11:49:11 linux-ytaf kernel: ACPI: Core revision 20150410
Feb 14 11:49:11 linux-ytaf kernel: ACPI: All ACPI Tables successfully acquired
Feb 14 11:49:11 linux-ytaf kernel: Security Framework initialized
Feb 14 11:49:11 linux-ytaf kernel: AppArmor: AppArmor initialized
Feb 14 11:49:11 linux-ytaf kernel: Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
Feb 14 11:49:11 linux-ytaf kernel: Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
Feb 14 11:49:11 linux-ytaf kernel: Mount-cache hash table entries: 16384 (order: 5, 131072 bytes)
Feb 14 11:49:11 linux-ytaf kernel: Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes)
Feb 14 11:49:11 linux-ytaf kernel: Initializing cgroup subsys blkio
Feb 14 11:49:11 linux-ytaf kernel: Initializing cgroup subsys memory
Feb 14 11:49:11 linux-ytaf kernel: Initializing cgroup subsys devices
Feb 14 11:49:11 linux-ytaf kernel: Initializing cgroup subsys freezer
Feb 14 11:49:11 linux-ytaf kernel: Initializing cgroup subsys net_cls
Feb 14 11:49:11 linux-ytaf kernel: Initializing cgroup subsys perf_event
Feb 14 11:49:11 linux-ytaf kernel: Initializing cgroup subsys net_prio
Feb 14 11:49:11 linux-ytaf kernel: Initializing cgroup subsys hugetlb
Feb 14 11:49:11 linux-ytaf kernel: CPU: Physical Processor ID: 0
Feb 14 11:49:11 linux-ytaf kernel: CPU: Processor Core ID: 0
Feb 14 11:49:11 linux-ytaf kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Feb 14 11:49:11 linux-ytaf kernel: ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Feb 14 11:49:11 linux-ytaf kernel: mce: CPU supports 9 MCE banks
Feb 14 11:49:11 linux-ytaf kernel: CPU0: Thermal monitoring enabled (TM1)
Feb 14 11:49:11 linux-ytaf kernel: process: using mwait in idle threads
Feb 14 11:49:11 linux-ytaf kernel: Last level iTLB entries: 4KB 512, 2MB 8, 4MB 8
Feb 14 11:49:11 linux-ytaf kernel: Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32, 1GB 0
Feb 14 11:49:11 linux-ytaf kernel: Freeing SMP alternatives memory: 24K (ffffffff82097000 - ffffffff8209d000)
Feb 14 11:49:11 linux-ytaf kernel: ftrace: allocating 25000 entries in 98 pages
Feb 14 11:49:11 linux-ytaf kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Feb 14 11:49:11 linux-ytaf kernel: TSC deadline timer enabled
Feb 14 11:49:11 linux-ytaf kernel: smpboot: CPU0: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz (fam: 06, model: 2a, stepping: 07)
Feb 14 11:49:11 linux-ytaf kernel: Performance Events: PEBS fmt1+, 16-deep LBR, SandyBridge events, full-width counters, Intel PMU driver.
Feb 14 11:49:11 linux-ytaf kernel: ... version:                3
Feb 14 11:49:11 linux-ytaf kernel: ... bit width:              48
Feb 14 11:49:11 linux-ytaf kernel: ... generic registers:      4
Feb 14 11:49:11 linux-ytaf kernel: ... value mask:             0000ffffffffffff
Feb 14 11:49:11 linux-ytaf kernel: ... max period:             0000ffffffffffff
Feb 14 11:49:11 linux-ytaf kernel: ... fixed-purpose events:   3
Feb 14 11:49:11 linux-ytaf kernel: ... event mask:             000000070000000f
Feb 14 11:49:11 linux-ytaf kernel: x86: Booting SMP configuration:
Feb 14 11:49:11 linux-ytaf kernel: .... node  #0, CPUs:      #1
Feb 14 11:49:11 linux-ytaf kernel: microcode: CPU1 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 11:49:11 linux-ytaf kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Feb 14 11:49:11 linux-ytaf kernel:  #2
Feb 14 11:49:11 linux-ytaf kernel: microcode: CPU2 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 11:49:11 linux-ytaf kernel:  #3
Feb 14 11:49:11 linux-ytaf kernel: microcode: CPU3 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 11:49:11 linux-ytaf kernel:  #4 #5 #6 #7
Feb 14 11:49:11 linux-ytaf kernel: x86: Booted up 1 node, 8 CPUs
Feb 14 11:49:11 linux-ytaf kernel: smpboot: Total of 8 processors activated (54578.62 BogoMIPS)
Feb 14 11:49:11 linux-ytaf kernel: devtmpfs: initialized
Feb 14 11:49:11 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xca5f2000-0xca679fff] (557056 bytes)
Feb 14 11:49:11 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xca93f000-0xcab83fff] (2379776 bytes)
Feb 14 11:49:11 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xcab92000-0xcabbefff] (184320 bytes)
Feb 14 11:49:11 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xcabc4000-0xcac06fff] (274432 bytes)
Feb 14 11:49:11 linux-ytaf kernel: clocksource jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
Feb 14 11:49:11 linux-ytaf kernel: pinctrl core: initialized pinctrl subsystem
Feb 14 11:49:11 linux-ytaf kernel: RTC time: 11:49:08, date: 02/14/16
Feb 14 11:49:11 linux-ytaf kernel: NET: Registered protocol family 16
Feb 14 11:49:11 linux-ytaf kernel: cpuidle: using governor ladder
Feb 14 11:49:11 linux-ytaf kernel: cpuidle: using governor menu
Feb 14 11:49:11 linux-ytaf kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
Feb 14 11:49:11 linux-ytaf kernel: ACPI: bus type PCI registered
Feb 14 11:49:11 linux-ytaf kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Feb 14 11:49:11 linux-ytaf kernel: PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
Feb 14 11:49:11 linux-ytaf kernel: PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
Feb 14 11:49:11 linux-ytaf kernel: PCI: Using configuration type 1 for base access
Feb 14 11:49:11 linux-ytaf kernel: perf_event_intel: PMU erratum BJ122, BV98, HSD29 worked around, HT is on
Feb 14 11:49:11 linux-ytaf kernel: ACPI: Added _OSI(Module Device)
Feb 14 11:49:11 linux-ytaf kernel: ACPI: Added _OSI(Processor Device)
Feb 14 11:49:11 linux-ytaf kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
Feb 14 11:49:11 linux-ytaf kernel: ACPI: Added _OSI(Processor Aggregator Device)
Feb 14 11:49:11 linux-ytaf kernel: ACPI: Executed 1 blocks of module-level executable AML code
Feb 14 11:49:11 linux-ytaf kernel: ACPI: Dynamic OEM Table Load:
Feb 14 11:49:11 linux-ytaf kernel: ACPI: SSDT 0xFFFF8802257C9000 00083B (v01 PmRef  Cpu0Cst  00003001 INTL 20051117)
Feb 14 11:49:11 linux-ytaf kernel: ACPI: Dynamic OEM Table Load:
Feb 14 11:49:11 linux-ytaf kernel: ACPI: SSDT 0xFFFF8802257C3400 000303 (v01 PmRef  ApIst    00003000 INTL 20051117)
Feb 14 11:49:11 linux-ytaf kernel: ACPI: Dynamic OEM Table Load:
Feb 14 11:49:11 linux-ytaf kernel: ACPI: SSDT 0xFFFF880225776600 000119 (v01 PmRef  ApCst    00003000 INTL 20051117)
Feb 14 11:49:11 linux-ytaf kernel: ACPI : EC: EC started
Feb 14 11:49:11 linux-ytaf kernel: ACPI: Interpreter enabled
Feb 14 11:49:11 linux-ytaf kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20150410/hwxface-580)
Feb 14 11:49:11 linux-ytaf kernel: ACPI: (supports S0 S1 S3 S4 S5)
Feb 14 11:49:11 linux-ytaf kernel: ACPI: Using IOAPIC for interrupt routing
Feb 14 11:49:11 linux-ytaf kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Feb 14 11:49:11 linux-ytaf kernel: ACPI: Power Resource [FN00] (off)
Feb 14 11:49:11 linux-ytaf kernel: ACPI: Power Resource [FN01] (off)
Feb 14 11:49:11 linux-ytaf kernel: ACPI: Power Resource [FN02] (off)
Feb 14 11:49:11 linux-ytaf kernel: ACPI: Power Resource [FN03] (off)
Feb 14 11:49:11 linux-ytaf kernel: ACPI: Power Resource [FN04] (off)
Feb 14 11:49:11 linux-ytaf kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
Feb 14 11:49:11 linux-ytaf kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Feb 14 11:49:11 linux-ytaf kernel: \_SB_.PCI0:_OSC invalid UUID
Feb 14 11:49:11 linux-ytaf kernel: _OSC request data:1 1f 0 
Feb 14 11:49:11 linux-ytaf kernel: acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
Feb 14 11:49:11 linux-ytaf kernel: PCI host bridge to bus 0000:00
Feb 14 11:49:11 linux-ytaf kernel: pci_bus 0000:00: root bus resource [bus 00-3e]
Feb 14 11:49:11 linux-ytaf kernel: pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
Feb 14 11:49:11 linux-ytaf kernel: pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
Feb 14 11:49:11 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
Feb 14 11:49:11 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff window]
Feb 14 11:49:11 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff window]
Feb 14 11:49:11 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff window]
Feb 14 11:49:11 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0xcfa00000-0xfeafffff window]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:00.0: [8086:0100] type 00 class 0x060000
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:01.0: [8086:0101] type 01 class 0x060400
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:01.0: System wakeup disabled by ACPI
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:01.1: [8086:0105] type 01 class 0x060400
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:01.1: PME# supported from D0 D3hot D3cold
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:01.1: System wakeup disabled by ACPI
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:02.0: [8086:0122] type 00 class 0x038000
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:02.0: reg 0x10: [mem 0xf7400000-0xf77fffff 64bit]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:02.0: reg 0x18: [mem 0xd0000000-0xdfffffff 64bit pref]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:02.0: reg 0x20: [io  0xf000-0xf03f]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:16.0: [8086:1c3a] type 00 class 0x078000
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:16.0: reg 0x10: [mem 0xf7b2c000-0xf7b2c00f 64bit]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:19.0: [8086:1503] type 00 class 0x020000
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:19.0: reg 0x10: [mem 0xf7b00000-0xf7b1ffff]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:19.0: reg 0x14: [mem 0xf7b29000-0xf7b29fff]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:19.0: reg 0x18: [io  0xf080-0xf09f]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:19.0: PME# supported from D0 D3hot D3cold
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:19.0: System wakeup disabled by ACPI
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1a.0: [8086:1c2d] type 00 class 0x0c0320
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1a.0: reg 0x10: [mem 0xf7b28000-0xf7b283ff]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1a.0: System wakeup disabled by ACPI
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1b.0: [8086:1c20] type 00 class 0x040300
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1b.0: reg 0x10: [mem 0xf7b20000-0xf7b23fff 64bit]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1b.0: System wakeup disabled by ACPI
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.0: [8086:1c10] type 01 class 0x060400
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.0: System wakeup disabled by ACPI
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.4: [8086:1c18] type 01 class 0x060400
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.4: System wakeup disabled by ACPI
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.5: [8086:1c1a] type 01 class 0x060400
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.5: System wakeup disabled by ACPI
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.6: [8086:1c1c] type 01 class 0x060400
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.6: PME# supported from D0 D3hot D3cold
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.6: System wakeup disabled by ACPI
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1d.0: [8086:1c26] type 00 class 0x0c0320
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1d.0: reg 0x10: [mem 0xf7b27000-0xf7b273ff]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1d.0: System wakeup disabled by ACPI
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1f.0: [8086:1c44] type 00 class 0x060100
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1f.2: [8086:1c02] type 00 class 0x010601
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x10: [io  0xf0d0-0xf0d7]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x14: [io  0xf0c0-0xf0c3]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x18: [io  0xf0b0-0xf0b7]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x1c: [io  0xf0a0-0xf0a3]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x20: [io  0xf060-0xf07f]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x24: [mem 0xf7b26000-0xf7b267ff]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1f.2: PME# supported from D3hot
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1f.3: [8086:1c22] type 00 class 0x0c0500
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1f.3: reg 0x10: [mem 0xf7b25000-0xf7b250ff 64bit]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1f.3: reg 0x20: [io  0x0580-0x059f]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:02:00.0: [10de:1183] type 00 class 0x030000
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:02:00.0: reg 0x10: [mem 0xf6000000-0xf6ffffff]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:02:00.0: reg 0x14: [mem 0xe0000000-0xe7ffffff 64bit pref]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:02:00.0: reg 0x1c: [mem 0xe8000000-0xe9ffffff 64bit pref]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:02:00.0: reg 0x24: [io  0xe000-0xe07f]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:02:00.0: reg 0x30: [mem 0xf7000000-0xf707ffff pref]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:02:00.1: [10de:0e0a] type 00 class 0x040300
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:02:00.1: reg 0x10: [mem 0xf7080000-0xf7083fff]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:01.1: PCI bridge to [bus 02]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [io  0xe000-0xefff]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xf6000000-0xf70fffff]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xe0000000-0xe9ffffff 64bit pref]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.0: PCI bridge to [bus 03]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:04:00.0: [1b21:1042] type 00 class 0x0c0330
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:04:00.0: reg 0x10: [mem 0xf7a00000-0xf7a07fff 64bit]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:04:00.0: PME# supported from D3hot D3cold
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:04:00.0: System wakeup disabled by ACPI
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.4: PCI bridge to [bus 04]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.4:   bridge window [mem 0xf7a00000-0xf7afffff]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:05:00.0: [1b21:1042] type 00 class 0x0c0330
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:05:00.0: reg 0x10: [mem 0xf7900000-0xf7907fff 64bit]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:05:00.0: PME# supported from D3hot D3cold
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:05:00.0: System wakeup disabled by ACPI
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.5: PCI bridge to [bus 05]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.5:   bridge window [mem 0xf7900000-0xf79fffff]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:06:00.0: [197b:2362] type 00 class 0x010185
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:06:00.0: reg 0x10: [io  0xd040-0xd047]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:06:00.0: reg 0x14: [io  0xd030-0xd033]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:06:00.0: reg 0x18: [io  0xd020-0xd027]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:06:00.0: reg 0x1c: [io  0xd010-0xd013]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:06:00.0: reg 0x20: [io  0xd000-0xd00f]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:06:00.0: reg 0x24: [mem 0xf7810000-0xf78101ff]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:06:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:06:00.0: PME# supported from D3hot
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:06:00.0: System wakeup disabled by ACPI
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.6: PCI bridge to [bus 06]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [io  0xd000-0xdfff]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [mem 0xf7800000-0xf78fffff]
Feb 14 11:49:11 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15)
Feb 14 11:49:11 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *10 11 12 14 15)
Feb 14 11:49:11 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Feb 14 11:49:11 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs *3 4 5 6 10 11 12 14 15)
Feb 14 11:49:11 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 *4 5 6 10 11 12 14 15)
Feb 14 11:49:11 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
Feb 14 11:49:11 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 *11 12 14 15)
Feb 14 11:49:11 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 *10 11 12 14 15)
Feb 14 11:49:11 linux-ytaf kernel: ACPI: Enabled 6 GPEs in block 00 to 3F
Feb 14 11:49:11 linux-ytaf kernel: ACPI : EC: GPE = 0x18, I/O: command/status = 0x66, data = 0x62
Feb 14 11:49:11 linux-ytaf kernel: vgaarb: setting as boot device: PCI:0000:02:00.0
Feb 14 11:49:11 linux-ytaf kernel: vgaarb: device added: PCI:0000:02:00.0,decodes=io+mem,owns=io+mem,locks=none
Feb 14 11:49:11 linux-ytaf kernel: vgaarb: loaded
Feb 14 11:49:11 linux-ytaf kernel: vgaarb: bridge control possible 0000:02:00.0
Feb 14 11:49:11 linux-ytaf kernel: SCSI subsystem initialized
Feb 14 11:49:11 linux-ytaf kernel: libata version 3.00 loaded.
Feb 14 11:49:11 linux-ytaf kernel: PCI: Using ACPI for IRQ routing
Feb 14 11:49:11 linux-ytaf kernel: PCI: pci_cache_line_size set to 64 bytes
Feb 14 11:49:11 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0009f000-0x0009ffff]
Feb 14 11:49:11 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c826018-0x0fffffff]
Feb 14 11:49:11 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c836018-0x0fffffff]
Feb 14 11:49:11 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c847018-0x0fffffff]
Feb 14 11:49:11 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c857018-0x0fffffff]
Feb 14 11:49:11 linux-ytaf kernel: e820: reserve RAM buffer [mem 0xca38f000-0xcbffffff]
Feb 14 11:49:11 linux-ytaf kernel: e820: reserve RAM buffer [mem 0xcb000000-0xcbffffff]
Feb 14 11:49:11 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x22f600000-0x22fffffff]
Feb 14 11:49:11 linux-ytaf kernel: NetLabel: Initializing
Feb 14 11:49:11 linux-ytaf kernel: NetLabel:  domain hash size = 128
Feb 14 11:49:11 linux-ytaf kernel: NetLabel:  protocols = UNLABELED CIPSOv4
Feb 14 11:49:11 linux-ytaf kernel: NetLabel:  unlabeled traffic allowed by default
Feb 14 11:49:11 linux-ytaf kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Feb 14 11:49:11 linux-ytaf kernel: hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Feb 14 11:49:11 linux-ytaf kernel: Switched to clocksource hpet
Feb 14 11:49:11 linux-ytaf kernel: AppArmor: AppArmor Filesystem Enabled
Feb 14 11:49:11 linux-ytaf kernel: pnp: PnP ACPI init
Feb 14 11:49:11 linux-ytaf kernel: system 00:00: [mem 0xfed40000-0xfed44fff] has been reserved
Feb 14 11:49:11 linux-ytaf kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
Feb 14 11:49:11 linux-ytaf kernel: system 00:01: [io  0x0680-0x069f] has been reserved
Feb 14 11:49:11 linux-ytaf kernel: system 00:01: [io  0x0200-0x020f] has been reserved
Feb 14 11:49:11 linux-ytaf kernel: system 00:01: [io  0xffff] has been reserved
Feb 14 11:49:11 linux-ytaf kernel: system 00:01: [io  0xffff] has been reserved
Feb 14 11:49:11 linux-ytaf kernel: system 00:01: [io  0x0400-0x0453] could not be reserved
Feb 14 11:49:11 linux-ytaf kernel: system 00:01: [io  0x0458-0x047f] has been reserved
Feb 14 11:49:11 linux-ytaf kernel: system 00:01: [io  0x0500-0x057f] has been reserved
Feb 14 11:49:11 linux-ytaf kernel: system 00:01: [io  0x164e-0x164f] has been reserved
Feb 14 11:49:11 linux-ytaf kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 11:49:11 linux-ytaf kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Feb 14 11:49:11 linux-ytaf kernel: system 00:03: [io  0x0454-0x0457] has been reserved
Feb 14 11:49:11 linux-ytaf kernel: system 00:03: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
Feb 14 11:49:11 linux-ytaf kernel: system 00:04: [io  0x0290-0x029f] has been reserved
Feb 14 11:49:11 linux-ytaf kernel: system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 11:49:11 linux-ytaf kernel: system 00:05: [io  0x04d0-0x04d1] has been reserved
Feb 14 11:49:11 linux-ytaf kernel: system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 11:49:11 linux-ytaf kernel: system 00:06: [mem 0xfed1c000-0xfed1ffff] has been reserved
Feb 14 11:49:11 linux-ytaf kernel: system 00:06: [mem 0xfed10000-0xfed17fff] has been reserved
Feb 14 11:49:11 linux-ytaf kernel: system 00:06: [mem 0xfed18000-0xfed18fff] has been reserved
Feb 14 11:49:11 linux-ytaf kernel: system 00:06: [mem 0xfed19000-0xfed19fff] has been reserved
Feb 14 11:49:11 linux-ytaf kernel: system 00:06: [mem 0xf8000000-0xfbffffff] has been reserved
Feb 14 11:49:11 linux-ytaf kernel: system 00:06: [mem 0xfed20000-0xfed3ffff] has been reserved
Feb 14 11:49:11 linux-ytaf kernel: system 00:06: [mem 0xfed90000-0xfed93fff] has been reserved
Feb 14 11:49:11 linux-ytaf kernel: system 00:06: [mem 0xfed45000-0xfed8ffff] has been reserved
Feb 14 11:49:11 linux-ytaf kernel: system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Feb 14 11:49:11 linux-ytaf kernel: system 00:06: [mem 0xfee00000-0xfeefffff] could not be reserved
Feb 14 11:49:11 linux-ytaf kernel: system 00:06: [mem 0xcfa00000-0xcfa00fff] has been reserved
Feb 14 11:49:11 linux-ytaf kernel: system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 11:49:11 linux-ytaf kernel: system 00:07: [mem 0x20000000-0x201fffff] has been reserved
Feb 14 11:49:11 linux-ytaf kernel: system 00:07: [mem 0x40000000-0x401fffff] has been reserved
Feb 14 11:49:11 linux-ytaf kernel: system 00:07: Plug and Play ACPI device, IDs PNP0c01 (active)
Feb 14 11:49:11 linux-ytaf kernel: pnp: PnP ACPI: found 8 devices
Feb 14 11:49:11 linux-ytaf kernel: clocksource acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.0: bridge window [io  0x1000-0x0fff] to [bus 03] add_size 1000
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 03] add_size 200000 add_align 100000
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff] to [bus 03] add_size 200000 add_align 100000
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.0: res[14]=[mem 0x00100000-0x000fffff] res_to_dev_res add_size 200000 min_align 100000
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.0: res[14]=[mem 0x00100000-0x002fffff] res_to_dev_res add_size 200000 min_align 100000
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x000fffff 64bit pref] res_to_dev_res add_size 200000 min_align 100000
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x002fffff 64bit pref] res_to_dev_res add_size 200000 min_align 100000
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.0: res[13]=[io  0x1000-0x0fff] res_to_dev_res add_size 1000 min_align 1000
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.0: res[13]=[io  0x1000-0x1fff] res_to_dev_res add_size 1000 min_align 1000
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.0: BAR 14: assigned [mem 0xcfb00000-0xcfcfffff]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.0: BAR 15: assigned [mem 0xcfd00000-0xcfefffff 64bit pref]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.0: BAR 13: assigned [io  0x2000-0x2fff]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:01.1: PCI bridge to [bus 02]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [io  0xe000-0xefff]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xf6000000-0xf70fffff]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xe0000000-0xe9ffffff 64bit pref]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.0: PCI bridge to [bus 03]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.0:   bridge window [io  0x2000-0x2fff]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.0:   bridge window [mem 0xcfb00000-0xcfcfffff]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.0:   bridge window [mem 0xcfd00000-0xcfefffff 64bit pref]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.4: PCI bridge to [bus 04]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.4:   bridge window [mem 0xf7a00000-0xf7afffff]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.5: PCI bridge to [bus 05]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.5:   bridge window [mem 0xf7900000-0xf79fffff]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:06:00.0: BAR 6: assigned [mem 0xf7800000-0xf780ffff pref]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.6: PCI bridge to [bus 06]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [io  0xd000-0xdfff]
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [mem 0xf7800000-0xf78fffff]
Feb 14 11:49:11 linux-ytaf kernel: pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
Feb 14 11:49:11 linux-ytaf kernel: pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
Feb 14 11:49:11 linux-ytaf kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
Feb 14 11:49:11 linux-ytaf kernel: pci_bus 0000:00: resource 7 [mem 0x000d4000-0x000d7fff window]
Feb 14 11:49:11 linux-ytaf kernel: pci_bus 0000:00: resource 8 [mem 0x000d8000-0x000dbfff window]
Feb 14 11:49:11 linux-ytaf kernel: pci_bus 0000:00: resource 9 [mem 0x000dc000-0x000dffff window]
Feb 14 11:49:11 linux-ytaf kernel: pci_bus 0000:00: resource 10 [mem 0xcfa00000-0xfeafffff window]
Feb 14 11:49:11 linux-ytaf kernel: pci_bus 0000:02: resource 0 [io  0xe000-0xefff]
Feb 14 11:49:11 linux-ytaf kernel: pci_bus 0000:02: resource 1 [mem 0xf6000000-0xf70fffff]
Feb 14 11:49:11 linux-ytaf kernel: pci_bus 0000:02: resource 2 [mem 0xe0000000-0xe9ffffff 64bit pref]
Feb 14 11:49:11 linux-ytaf kernel: pci_bus 0000:03: resource 0 [io  0x2000-0x2fff]
Feb 14 11:49:11 linux-ytaf kernel: pci_bus 0000:03: resource 1 [mem 0xcfb00000-0xcfcfffff]
Feb 14 11:49:11 linux-ytaf kernel: pci_bus 0000:03: resource 2 [mem 0xcfd00000-0xcfefffff 64bit pref]
Feb 14 11:49:11 linux-ytaf kernel: pci_bus 0000:04: resource 1 [mem 0xf7a00000-0xf7afffff]
Feb 14 11:49:11 linux-ytaf kernel: pci_bus 0000:05: resource 1 [mem 0xf7900000-0xf79fffff]
Feb 14 11:49:11 linux-ytaf kernel: pci_bus 0000:06: resource 0 [io  0xd000-0xdfff]
Feb 14 11:49:11 linux-ytaf kernel: pci_bus 0000:06: resource 1 [mem 0xf7800000-0xf78fffff]
Feb 14 11:49:11 linux-ytaf kernel: NET: Registered protocol family 2
Feb 14 11:49:11 linux-ytaf kernel: TCP established hash table entries: 65536 (order: 7, 524288 bytes)
Feb 14 11:49:11 linux-ytaf kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Feb 14 11:49:11 linux-ytaf kernel: TCP: Hash tables configured (established 65536 bind 65536)
Feb 14 11:49:11 linux-ytaf kernel: UDP hash table entries: 4096 (order: 5, 131072 bytes)
Feb 14 11:49:11 linux-ytaf kernel: UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
Feb 14 11:49:11 linux-ytaf kernel: NET: Registered protocol family 1
Feb 14 11:49:11 linux-ytaf kernel: pci 0000:02:00.0: Video device with shadowed ROM
Feb 14 11:49:11 linux-ytaf kernel: PCI: CLS 64 bytes, default 64
Feb 14 11:49:11 linux-ytaf kernel: Unpacking initramfs...
Feb 14 11:49:11 linux-ytaf kernel: Freeing initrd memory: 11920K (ffff880000457000 - ffff880000ffb000)
Feb 14 11:49:11 linux-ytaf kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Feb 14 11:49:11 linux-ytaf kernel: software IO TLB [mem 0xc638f000-0xca38f000] (64MB) mapped at [ffff8800c638f000-ffff8800ca38efff]
Feb 14 11:49:11 linux-ytaf kernel: RAPL PMU detected, API unit is 2^-32 Joules, 3 fixed counters 163840 ms ovfl timer
Feb 14 11:49:11 linux-ytaf kernel: hw unit of domain pp0-core 2^-16 Joules
Feb 14 11:49:11 linux-ytaf kernel: hw unit of domain package 2^-16 Joules
Feb 14 11:49:11 linux-ytaf kernel: hw unit of domain pp1-gpu 2^-16 Joules
Feb 14 11:49:11 linux-ytaf kernel: microcode: CPU0 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 11:49:11 linux-ytaf kernel: microcode: CPU1 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 11:49:11 linux-ytaf kernel: microcode: CPU2 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 11:49:11 linux-ytaf kernel: microcode: CPU3 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 11:49:11 linux-ytaf kernel: microcode: CPU4 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 11:49:11 linux-ytaf kernel: microcode: CPU5 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 11:49:11 linux-ytaf kernel: microcode: CPU6 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 11:49:11 linux-ytaf kernel: microcode: CPU7 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 11:49:11 linux-ytaf kernel: microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Feb 14 11:49:11 linux-ytaf kernel: Scanning for low memory corruption every 60 seconds
Feb 14 11:49:11 linux-ytaf kernel: futex hash table entries: 2048 (order: 5, 131072 bytes)
Feb 14 11:49:11 linux-ytaf kernel: audit: initializing netlink subsys (disabled)
Feb 14 11:49:11 linux-ytaf kernel: audit: type=2000 audit(1455450549.280:1): initialized
Feb 14 11:49:11 linux-ytaf kernel: HugeTLB registered 2 MB page size, pre-allocated 0 pages
Feb 14 11:49:11 linux-ytaf kernel: zpool: loaded
Feb 14 11:49:11 linux-ytaf kernel: zbud: loaded
Feb 14 11:49:11 linux-ytaf kernel: VFS: Disk quotas dquot_6.6.0
Feb 14 11:49:11 linux-ytaf kernel: VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Feb 14 11:49:11 linux-ytaf kernel: Key type big_key registered
Feb 14 11:49:11 linux-ytaf kernel: Key type asymmetric registered
Feb 14 11:49:11 linux-ytaf kernel: Asymmetric key parser 'x509' registered
Feb 14 11:49:11 linux-ytaf kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Feb 14 11:49:11 linux-ytaf kernel: io scheduler noop registered
Feb 14 11:49:11 linux-ytaf kernel: io scheduler deadline registered
Feb 14 11:49:11 linux-ytaf kernel: io scheduler cfq registered (default)
Feb 14 11:49:11 linux-ytaf kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Feb 14 11:49:11 linux-ytaf kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Feb 14 11:49:11 linux-ytaf kernel: efifb: probing for efifb
Feb 14 11:49:11 linux-ytaf kernel: efifb: framebuffer at 0xe9000000, mapped to 0xffffc90001000000, using 1876k, total 1875k
Feb 14 11:49:11 linux-ytaf kernel: efifb: mode is 800x600x32, linelength=3200, pages=1
Feb 14 11:49:11 linux-ytaf kernel: efifb: scrolling: redraw
Feb 14 11:49:11 linux-ytaf kernel: efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Feb 14 11:49:11 linux-ytaf kernel: Console: switching to colour frame buffer device 100x37
Feb 14 11:49:11 linux-ytaf kernel: fb0: EFI VGA frame buffer device
Feb 14 11:49:11 linux-ytaf kernel: intel_idle: MWAIT substates: 0x1120
Feb 14 11:49:11 linux-ytaf kernel: intel_idle: v0.4 model 0x2A
Feb 14 11:49:11 linux-ytaf kernel: intel_idle: lapic_timer_reliable_states 0xffffffff
Feb 14 11:49:11 linux-ytaf kernel: GHES: HEST is not enabled!
Feb 14 11:49:11 linux-ytaf kernel: Serial: 8250/16550 driver, 32 ports, IRQ sharing disabled
Feb 14 11:49:11 linux-ytaf kernel: Non-volatile memory driver v1.3
Feb 14 11:49:11 linux-ytaf kernel: Linux agpgart interface v0.103
Feb 14 11:49:11 linux-ytaf kernel: ahci 0000:00:1f.2: version 3.0
Feb 14 11:49:11 linux-ytaf kernel: ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x7 impl SATA mode
Feb 14 11:49:11 linux-ytaf kernel: ahci 0000:00:1f.2: flags: 64bit ncq led clo pio slum part ems apst 
Feb 14 11:49:11 linux-ytaf kernel: scsi host0: ahci
Feb 14 11:49:11 linux-ytaf kernel: scsi host1: ahci
Feb 14 11:49:11 linux-ytaf kernel: scsi host2: ahci
Feb 14 11:49:11 linux-ytaf kernel: scsi host3: ahci
Feb 14 11:49:11 linux-ytaf kernel: scsi host4: ahci
Feb 14 11:49:11 linux-ytaf kernel: scsi host5: ahci
Feb 14 11:49:11 linux-ytaf kernel: ata1: SATA max UDMA/133 abar m2048@0xf7b26000 port 0xf7b26100 irq 26
Feb 14 11:49:11 linux-ytaf kernel: ata2: SATA max UDMA/133 abar m2048@0xf7b26000 port 0xf7b26180 irq 26
Feb 14 11:49:11 linux-ytaf kernel: ata3: SATA max UDMA/133 abar m2048@0xf7b26000 port 0xf7b26200 irq 26
Feb 14 11:49:11 linux-ytaf kernel: ata4: DUMMY
Feb 14 11:49:11 linux-ytaf kernel: ata5: DUMMY
Feb 14 11:49:11 linux-ytaf kernel: ata6: DUMMY
Feb 14 11:49:11 linux-ytaf kernel: ahci 0000:06:00.0: AHCI 0001.0100 32 slots 2 ports 3 Gbps 0x3 impl SATA mode
Feb 14 11:49:11 linux-ytaf kernel: ahci 0000:06:00.0: flags: 64bit ncq pm led clo pmp pio slum part 
Feb 14 11:49:11 linux-ytaf kernel: scsi host6: ahci
Feb 14 11:49:11 linux-ytaf kernel: scsi host7: ahci
Feb 14 11:49:11 linux-ytaf kernel: ata7: SATA max UDMA/133 abar m512@0xf7810000 port 0xf7810100 irq 18
Feb 14 11:49:11 linux-ytaf kernel: ata8: SATA max UDMA/133 abar m512@0xf7810000 port 0xf7810180 irq 18
Feb 14 11:49:11 linux-ytaf kernel: i8042: PNP: No PS/2 controller found. Probing ports directly.
Feb 14 11:49:11 linux-ytaf kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Feb 14 11:49:11 linux-ytaf kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Feb 14 11:49:11 linux-ytaf kernel: mousedev: PS/2 mouse device common for all mice
Feb 14 11:49:11 linux-ytaf kernel: rtc_cmos 00:02: RTC can wake from S4
Feb 14 11:49:11 linux-ytaf kernel: rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Feb 14 11:49:11 linux-ytaf kernel: rtc_cmos 00:02: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
Feb 14 11:49:11 linux-ytaf kernel: Intel P-state driver initializing.
Feb 14 11:49:11 linux-ytaf kernel: ledtrig-cpu: registered to indicate activity on CPUs
Feb 14 11:49:11 linux-ytaf kernel: EFI Variables Facility v0.08 2004-May-17
Feb 14 11:49:11 linux-ytaf kernel: hidraw: raw HID events driver (C) Jiri Kosina
Feb 14 11:49:11 linux-ytaf kernel: NET: Registered protocol family 10
Feb 14 11:49:11 linux-ytaf kernel: registered taskstats version 1
Feb 14 11:49:11 linux-ytaf kernel: Key type encrypted registered
Feb 14 11:49:11 linux-ytaf kernel: AppArmor: AppArmor sha1 policy hashing enabled
Feb 14 11:49:11 linux-ytaf kernel:   Magic number: 4:978:832
Feb 14 11:49:11 linux-ytaf kernel: rtc_cmos 00:02: setting system clock to 2016-02-14 11:49:09 UTC (1455450549)
Feb 14 11:49:11 linux-ytaf kernel: PM: Checking hibernation image partition /dev/sdb2
Feb 14 11:49:11 linux-ytaf kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 14 11:49:11 linux-ytaf kernel: ata8: SATA link down (SStatus 0 SControl 300)
Feb 14 11:49:11 linux-ytaf kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Feb 14 11:49:11 linux-ytaf kernel: ata7: SATA link down (SStatus 0 SControl 300)
Feb 14 11:49:11 linux-ytaf kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 14 11:49:11 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 11:49:11 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff8802268b7e50), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 11:49:11 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 11:49:11 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff8802268b7dd8), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 11:49:11 linux-ytaf kernel: ata1.00: ATA-9: SAMSUNG SSD 830 Series, CXM03B1Q, max UDMA/133
Feb 14 11:49:11 linux-ytaf kernel: ata1.00: 500118192 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Feb 14 11:49:11 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 11:49:11 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff8802268b7e50), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 11:49:11 linux-ytaf kernel: ata2.00: ATA-8: TOSHIBA HDWD110, MS2OA8J0, max UDMA/133
Feb 14 11:49:11 linux-ytaf kernel: ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Feb 14 11:49:11 linux-ytaf kernel: ata1.00: configured for UDMA/133
Feb 14 11:49:11 linux-ytaf kernel: scsi 0:0:0:0: Direct-Access     ATA      SAMSUNG SSD 830  3B1Q PQ: 0 ANSI: 5
Feb 14 11:49:11 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 11:49:11 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff8802268b7d60), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 11:49:11 linux-ytaf kernel: ata3.00: ATAPI: TSSTcorp CDDVDW SH-S223C, SB05, max UDMA/66
Feb 14 11:49:11 linux-ytaf kernel: ata3.00: applying bridge limits
Feb 14 11:49:11 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 11:49:11 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff8802268b7dd8), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 11:49:11 linux-ytaf kernel: sd 0:0:0:0: [sda] 500118192 512-byte logical blocks: (256 GB/238 GiB)
Feb 14 11:49:11 linux-ytaf kernel: ata2.00: configured for UDMA/133
Feb 14 11:49:11 linux-ytaf kernel: scsi 1:0:0:0: Direct-Access     ATA      TOSHIBA HDWD110  A8J0 PQ: 0 ANSI: 5
Feb 14 11:49:11 linux-ytaf kernel: sd 0:0:0:0: [sda] Write Protect is off
Feb 14 11:49:11 linux-ytaf kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 14 11:49:11 linux-ytaf kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 14 11:49:11 linux-ytaf kernel: sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
Feb 14 11:49:11 linux-ytaf kernel: sd 1:0:0:0: [sdb] 4096-byte physical blocks
Feb 14 11:49:11 linux-ytaf kernel: sd 1:0:0:0: [sdb] Write Protect is off
Feb 14 11:49:11 linux-ytaf kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Feb 14 11:49:11 linux-ytaf kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 14 11:49:11 linux-ytaf kernel:  sda: sda1 sda2 sda3 sda4
Feb 14 11:49:11 linux-ytaf kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Feb 14 11:49:11 linux-ytaf kernel:  sdb: sdb1 sdb2 sdb3 sdb4
Feb 14 11:49:11 linux-ytaf kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
Feb 14 11:49:11 linux-ytaf kernel: tsc: Refined TSC clocksource calibration: 3411.127 MHz
Feb 14 11:49:11 linux-ytaf kernel: clocksource tsc: mask: 0xffffffffffffffff max_cycles: 0x312b5e33c4e, max_idle_ns: 440795327319 ns
Feb 14 11:49:11 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 11:49:11 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff8802268b7d60), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 11:49:11 linux-ytaf kernel: ata3.00: configured for UDMA/66
Feb 14 11:49:11 linux-ytaf kernel: scsi 2:0:0:0: CD-ROM            TSSTcorp CDDVDW SH-S223C  SB05 PQ: 0 ANSI: 5
Feb 14 11:49:11 linux-ytaf kernel: PM: Hibernation image partition 8:18 present
Feb 14 11:49:11 linux-ytaf kernel: PM: Looking for hibernation image.
Feb 14 11:49:11 linux-ytaf kernel: Switched to clocksource tsc
Feb 14 11:49:11 linux-ytaf kernel: PM: Image not found (code -22)
Feb 14 11:49:11 linux-ytaf kernel: PM: Hibernation image not present or could not be loaded.
Feb 14 11:49:11 linux-ytaf kernel: Freeing unused kernel memory: 1560K (ffffffff81f11000 - ffffffff82097000)
Feb 14 11:49:11 linux-ytaf kernel: Write protecting the kernel read-only data: 14336k
Feb 14 11:49:11 linux-ytaf kernel: Freeing unused kernel memory: 1632K (ffff88000d668000 - ffff88000d800000)
Feb 14 11:49:11 linux-ytaf kernel: Freeing unused kernel memory: 1296K (ffff88000dcbc000 - ffff88000de00000)
Feb 14 11:49:11 linux-ytaf systemd[1]: RTC configured in localtime, applying delta of 60 minutes to system time.
Feb 14 11:49:11 linux-ytaf kernel: random: systemd urandom read with 21 bits of entropy available
Feb 14 11:49:11 linux-ytaf kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Feb 14 11:49:11 linux-ytaf kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0
Feb 14 11:49:11 linux-ytaf kernel: scsi 2:0:0:0: Attached scsi generic sg2 type 5
Feb 14 11:49:11 linux-ytaf systemd-journal[187]: Journal started
Feb 14 11:49:11 linux-ytaf dracut-cmdline[181]: dracut-42.1 dracut-037-68.1
Feb 14 11:49:11 linux-ytaf systemd-udevd[250]: Network interface NamePolicy= disabled on kernel commandline, ignoring.
Feb 14 11:49:11 linux-ytaf kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3
Feb 14 11:49:11 linux-ytaf kernel: ACPI: Power Button [PWRB]
Feb 14 11:49:11 linux-ytaf kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
Feb 14 11:49:11 linux-ytaf kernel: ACPI: Power Button [PWRF]
Feb 14 11:49:11 linux-ytaf kernel: ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
Feb 14 11:49:11 linux-ytaf kernel: acpi device:58: registered as cooling_device0
Feb 14 11:49:11 linux-ytaf kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5
Feb 14 11:49:11 linux-ytaf kernel: wmi: Mapper loaded
Feb 14 11:49:11 linux-ytaf kernel: [drm] Initialized drm 1.1.0 20060810
Feb 14 11:49:11 linux-ytaf kernel: ACPI: bus type USB registered
Feb 14 11:49:11 linux-ytaf kernel: usbcore: registered new interface driver usbfs
Feb 14 11:49:11 linux-ytaf kernel: usbcore: registered new interface driver hub
Feb 14 11:49:11 linux-ytaf kernel: usbcore: registered new device driver usb
Feb 14 11:49:11 linux-ytaf kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Feb 14 11:49:11 linux-ytaf kernel: ehci-pci: EHCI PCI platform driver
Feb 14 11:49:11 linux-ytaf kernel: ehci-pci 0000:00:1a.0: EHCI Host Controller
Feb 14 11:49:11 linux-ytaf kernel: ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Feb 14 11:49:11 linux-ytaf kernel: ehci-pci 0000:00:1a.0: debug port 2
Feb 14 11:49:11 linux-ytaf kernel: ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Feb 14 11:49:11 linux-ytaf kernel: ehci-pci 0000:00:1a.0: irq 16, io mem 0xf7b28000
Feb 14 11:49:11 linux-ytaf kernel: MXM: GUID detected in BIOS
Feb 14 11:49:11 linux-ytaf kernel: checking generic (e9000000 1d5000) vs hw (e0000000 8000000)
Feb 14 11:49:11 linux-ytaf kernel: checking generic (e9000000 1d5000) vs hw (e8000000 2000000)
Feb 14 11:49:11 linux-ytaf kernel: fb: switching to nouveaufb from EFI VGA
Feb 14 11:49:11 linux-ytaf kernel: Console: switching to colour dummy device 80x25
Feb 14 11:49:11 linux-ytaf kernel: nouveau  [  DEVICE][0000:02:00.0] BOOT0  : 0x0e4030a2
Feb 14 11:49:11 linux-ytaf kernel: nouveau  [  DEVICE][0000:02:00.0] Chipset: GK104 (NVE4)
Feb 14 11:49:11 linux-ytaf kernel: nouveau  [  DEVICE][0000:02:00.0] Family : NVE0
Feb 14 11:49:11 linux-ytaf kernel: ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Feb 14 11:49:11 linux-ytaf kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 11:49:11 linux-ytaf kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 11:49:11 linux-ytaf kernel: usb usb1: Product: EHCI Host Controller
Feb 14 11:49:11 linux-ytaf kernel: usb usb1: Manufacturer: Linux 4.1.15-8-default ehci_hcd
Feb 14 11:49:11 linux-ytaf kernel: usb usb1: SerialNumber: 0000:00:1a.0
Feb 14 11:49:11 linux-ytaf kernel: hub 1-0:1.0: USB hub found
Feb 14 11:49:11 linux-ytaf kernel: hub 1-0:1.0: 2 ports detected
Feb 14 11:49:11 linux-ytaf kernel: xhci_hcd 0000:04:00.0: xHCI Host Controller
Feb 14 11:49:11 linux-ytaf kernel: xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 2
Feb 14 11:49:11 linux-ytaf kernel: sr 2:0:0:0: [sr0] scsi3-mmc drive: 52x/52x writer dvd-ram cd/rw xa/form2 cdda tray
Feb 14 11:49:11 linux-ytaf kernel: cdrom: Uniform CD-ROM driver Revision: 3.20
Feb 14 11:49:11 linux-ytaf kernel: sr 2:0:0:0: Attached scsi CD-ROM sr0
Feb 14 11:49:11 linux-ytaf kernel: xhci_hcd 0000:04:00.0: hcc params 0x0200f180 hci version 0x96 quirks 0x00080000
Feb 14 11:49:11 linux-ytaf kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 11:49:11 linux-ytaf kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 11:49:11 linux-ytaf kernel: usb usb2: Product: xHCI Host Controller
Feb 14 11:49:11 linux-ytaf kernel: usb usb2: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 11:49:11 linux-ytaf kernel: usb usb2: SerialNumber: 0000:04:00.0
Feb 14 11:49:11 linux-ytaf kernel: hub 2-0:1.0: USB hub found
Feb 14 11:49:11 linux-ytaf kernel: hub 2-0:1.0: 2 ports detected
Feb 14 11:49:11 linux-ytaf kernel: xhci_hcd 0000:04:00.0: xHCI Host Controller
Feb 14 11:49:11 linux-ytaf kernel: xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 3
Feb 14 11:49:11 linux-ytaf kernel: ehci-pci 0000:00:1d.0: EHCI Host Controller
Feb 14 11:49:11 linux-ytaf kernel: ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 4
Feb 14 11:49:11 linux-ytaf kernel: usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
Feb 14 11:49:11 linux-ytaf kernel: usb usb3: New USB device found, idVendor=1d6b, idProduct=0003
Feb 14 11:49:11 linux-ytaf kernel: usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 11:49:11 linux-ytaf kernel: ehci-pci 0000:00:1d.0: debug port 2
Feb 14 11:49:11 linux-ytaf kernel: usb usb3: Product: xHCI Host Controller
Feb 14 11:49:11 linux-ytaf kernel: usb usb3: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 11:49:11 linux-ytaf kernel: usb usb3: SerialNumber: 0000:04:00.0
Feb 14 11:49:11 linux-ytaf kernel: hub 3-0:1.0: USB hub found
Feb 14 11:49:11 linux-ytaf kernel: hub 3-0:1.0: 2 ports detected
Feb 14 11:49:11 linux-ytaf kernel: ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Feb 14 11:49:11 linux-ytaf kernel: ehci-pci 0000:00:1d.0: irq 23, io mem 0xf7b27000
Feb 14 11:49:11 linux-ytaf kernel: ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Feb 14 11:49:11 linux-ytaf kernel: usb usb4: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 11:49:11 linux-ytaf kernel: usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 11:49:11 linux-ytaf kernel: usb usb4: Product: EHCI Host Controller
Feb 14 11:49:11 linux-ytaf kernel: usb usb4: Manufacturer: Linux 4.1.15-8-default ehci_hcd
Feb 14 11:49:11 linux-ytaf kernel: usb usb4: SerialNumber: 0000:00:1d.0
Feb 14 11:49:11 linux-ytaf kernel: hub 4-0:1.0: USB hub found
Feb 14 11:49:11 linux-ytaf kernel: hub 4-0:1.0: 2 ports detected
Feb 14 11:49:11 linux-ytaf kernel: xhci_hcd 0000:05:00.0: xHCI Host Controller
Feb 14 11:49:11 linux-ytaf kernel: i915 0000:00:02.0: enabling device (0006 -> 0007)
Feb 14 11:49:11 linux-ytaf kernel: xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 5
Feb 14 11:49:11 linux-ytaf kernel: xhci_hcd 0000:05:00.0: hcc params 0x0200f180 hci version 0x96 quirks 0x00080000
Feb 14 11:49:11 linux-ytaf kernel: usb usb5: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 11:49:11 linux-ytaf kernel: usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 11:49:11 linux-ytaf kernel: usb usb5: Product: xHCI Host Controller
Feb 14 11:49:11 linux-ytaf kernel: usb usb5: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 11:49:11 linux-ytaf kernel: usb usb5: SerialNumber: 0000:05:00.0
Feb 14 11:49:11 linux-ytaf kernel: hub 5-0:1.0: USB hub found
Feb 14 11:49:11 linux-ytaf kernel: hub 5-0:1.0: 2 ports detected
Feb 14 11:49:11 linux-ytaf kernel: xhci_hcd 0000:05:00.0: xHCI Host Controller
Feb 14 11:49:11 linux-ytaf kernel: xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 6
Feb 14 11:49:11 linux-ytaf kernel: usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
Feb 14 11:49:11 linux-ytaf kernel: usb usb6: New USB device found, idVendor=1d6b, idProduct=0003
Feb 14 11:49:11 linux-ytaf kernel: usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 11:49:11 linux-ytaf kernel: usb usb6: Product: xHCI Host Controller
Feb 14 11:49:11 linux-ytaf kernel: usb usb6: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 11:49:11 linux-ytaf kernel: usb usb6: SerialNumber: 0000:05:00.0
Feb 14 11:49:11 linux-ytaf kernel: hub 6-0:1.0: USB hub found
Feb 14 11:49:11 linux-ytaf kernel: hub 6-0:1.0: 2 ports detected
Feb 14 11:49:11 linux-ytaf kernel: nouveau  [   VBIOS][0000:02:00.0] using image from PROM
Feb 14 11:49:11 linux-ytaf kernel: nouveau  [   VBIOS][0000:02:00.0] BIT signature found
Feb 14 11:49:11 linux-ytaf kernel: nouveau  [   VBIOS][0000:02:00.0] version 80.04.4b.00.07
Feb 14 11:49:11 linux-ytaf kernel: nouveau  [     PMC][0000:02:00.0] MSI interrupts enabled
Feb 14 11:49:11 linux-ytaf kernel: nouveau  [     PFB][0000:02:00.0] RAM type: GDDR5
Feb 14 11:49:11 linux-ytaf kernel: nouveau  [     PFB][0000:02:00.0] RAM size: 2048 MiB
Feb 14 11:49:11 linux-ytaf kernel: nouveau  [     PFB][0000:02:00.0]    ZCOMP: 0 tags
Feb 14 11:49:11 linux-ytaf kernel: nouveau  [    VOLT][0000:02:00.0] GPU voltage: 987500uv
Feb 14 11:49:11 linux-ytaf kernel: nouveau  [  PTHERM][0000:02:00.0] FAN control: PWM
Feb 14 11:49:11 linux-ytaf kernel: nouveau  [  PTHERM][0000:02:00.0] fan management: automatic
Feb 14 11:49:11 linux-ytaf kernel: nouveau  [  PTHERM][0000:02:00.0] internal sensor: yes
Feb 14 11:49:11 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 07: core 324 MHz memory 648 MHz 
Feb 14 11:49:11 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 0a: core 324-862 MHz memory 1620 MHz 
Feb 14 11:49:11 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 0d: core 540-1202 MHz memory 6008 MHz 
Feb 14 11:49:11 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 0f: core 540-1202 MHz memory 6008 MHz 
Feb 14 11:49:11 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] --: core 324 MHz memory 648 MHz 
Feb 14 11:49:11 linux-ytaf kernel: raid6: sse2x1   gen()  8231 MB/s
Feb 14 11:49:11 linux-ytaf kernel: usb 1-1: new high-speed USB device number 2 using ehci-pci
Feb 14 11:49:11 linux-ytaf kernel: [TTM] Zone  kernel: Available graphics memory: 4034698 kiB
Feb 14 11:49:11 linux-ytaf kernel: [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
Feb 14 11:49:11 linux-ytaf kernel: [TTM] Initializing pool allocator
Feb 14 11:49:11 linux-ytaf kernel: [TTM] Initializing DMA pool allocator
Feb 14 11:49:11 linux-ytaf kernel: nouveau  [     DRM] VRAM: 2048 MiB
Feb 14 11:49:11 linux-ytaf kernel: nouveau  [     DRM] GART: 1048576 MiB
Feb 14 11:49:11 linux-ytaf kernel: nouveau  [     DRM] TMDS table version 2.0
Feb 14 11:49:11 linux-ytaf kernel: nouveau  [     DRM] DCB version 4.0
Feb 14 11:49:11 linux-ytaf kernel: nouveau  [     DRM] DCB outp 00: 01000f02 00020030
Feb 14 11:49:11 linux-ytaf kernel: nouveau  [     DRM] DCB outp 01: 02000f00 00000000
Feb 14 11:49:11 linux-ytaf kernel: nouveau  [     DRM] DCB outp 02: 08011f82 00020030
Feb 14 11:49:11 linux-ytaf kernel: nouveau  [     DRM] DCB outp 03: 02822f62 0f420010
Feb 14 11:49:11 linux-ytaf kernel: nouveau  [     DRM] DCB outp 05: 04833fb6 0f420010
Feb 14 11:49:11 linux-ytaf kernel: nouveau  [     DRM] DCB outp 06: 04033f72 00020010
Feb 14 11:49:11 linux-ytaf kernel: nouveau  [     DRM] DCB conn 00: 00001030
Feb 14 11:49:11 linux-ytaf kernel: nouveau  [     DRM] DCB conn 01: 00020131
Feb 14 11:49:11 linux-ytaf kernel: nouveau  [     DRM] DCB conn 02: 00002261
Feb 14 11:49:11 linux-ytaf kernel: nouveau  [     DRM] DCB conn 03: 00010346
Feb 14 11:49:11 linux-ytaf kernel: nouveau  [     DRM] DCB conn 04: 00000460
Feb 14 11:49:11 linux-ytaf kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Feb 14 11:49:11 linux-ytaf kernel: [drm] Driver supports precise vblank timestamp query.
Feb 14 11:49:11 linux-ytaf kernel: nouveau  [     DRM] MM: using COPY for buffer copies
Feb 14 11:49:11 linux-ytaf kernel: raid6: sse2x1   xor()  7793 MB/s
Feb 14 11:49:11 linux-ytaf kernel: usb 4-1: new high-speed USB device number 2 using ehci-pci
Feb 14 11:49:11 linux-ytaf kernel: raid6: sse2x2   gen() 14096 MB/s
Feb 14 11:49:11 linux-ytaf kernel: usb 1-1: New USB device found, idVendor=8087, idProduct=0024
Feb 14 11:49:11 linux-ytaf kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb 14 11:49:11 linux-ytaf kernel: hub 1-1:1.0: USB hub found
Feb 14 11:49:11 linux-ytaf kernel: hub 1-1:1.0: 6 ports detected
Feb 14 11:49:12 linux-ytaf kernel: usb 5-2: new high-speed USB device number 2 using xhci_hcd
Feb 14 11:49:12 linux-ytaf kernel: raid6: sse2x2   xor() 10056 MB/s
Feb 14 11:49:12 linux-ytaf kernel: usb 4-1: New USB device found, idVendor=8087, idProduct=0024
Feb 14 11:49:12 linux-ytaf kernel: usb 4-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb 14 11:49:12 linux-ytaf kernel: hub 4-1:1.0: USB hub found
Feb 14 11:49:12 linux-ytaf kernel: hub 4-1:1.0: 8 ports detected
Feb 14 11:49:12 linux-ytaf kernel: raid6: sse2x4   gen() 16274 MB/s
Feb 14 11:49:12 linux-ytaf kernel: raid6: sse2x4   xor() 12090 MB/s
Feb 14 11:49:12 linux-ytaf kernel: raid6: using algorithm sse2x4 gen() 16274 MB/s
Feb 14 11:49:12 linux-ytaf kernel: raid6: .... xor() 12090 MB/s, rmw enabled
Feb 14 11:49:12 linux-ytaf kernel: raid6: using ssse3x2 recovery algorithm
Feb 14 11:49:12 linux-ytaf kernel: xor: automatically using best checksumming function:
Feb 14 11:49:12 linux-ytaf kernel:    avx       : 31189.000 MB/sec
Feb 14 11:49:12 linux-ytaf kernel: Btrfs loaded, assert=on
Feb 14 11:49:12 linux-ytaf kernel: BTRFS: device fsid 21024970-7a27-4114-8525-d8dd026f23b6 devid 1 transid 241 /dev/sdb3
Feb 14 11:49:12 linux-ytaf kernel: usb 5-2: New USB device found, idVendor=0930, idProduct=6545
Feb 14 11:49:12 linux-ytaf kernel: usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 14 11:49:12 linux-ytaf kernel: usb 5-2: Product: TransMemory
Feb 14 11:49:12 linux-ytaf kernel: usb 5-2: Manufacturer: TOSHIBA
Feb 14 11:49:12 linux-ytaf kernel: usb 5-2: SerialNumber: C89CDCBF6D59EF4140000065
Feb 14 11:49:12 linux-ytaf kernel: usb-storage 5-2:1.0: USB Mass Storage device detected
Feb 14 11:49:12 linux-ytaf kernel: scsi host8: usb-storage 5-2:1.0
Feb 14 11:49:12 linux-ytaf kernel: usbcore: registered new interface driver usb-storage
Feb 14 11:49:12 linux-ytaf kernel: usbcore: registered new interface driver uas
Feb 14 11:49:12 linux-ytaf kernel: nouveau  [     DRM] allocated 1920x1080 fb: 0x60000, bo ffff88022282f800
Feb 14 11:49:12 linux-ytaf kernel: fbcon: nouveaufb (fb0) is primary device
Feb 14 11:49:12 linux-ytaf kernel: usb 1-1.4: new full-speed USB device number 3 using ehci-pci
Feb 14 11:49:12 linux-ytaf kernel: usb 4-1.1: new full-speed USB device number 3 using ehci-pci
Feb 14 11:49:12 linux-ytaf kernel: usb 4-1.1: New USB device found, idVendor=1532, idProduct=0109
Feb 14 11:49:12 linux-ytaf kernel: usb 4-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 14 11:49:12 linux-ytaf kernel: usb 4-1.1: Product: Razer Lycosa
Feb 14 11:49:12 linux-ytaf kernel: usb 4-1.1: Manufacturer: Razer
Feb 14 11:49:12 linux-ytaf kernel: usbcore: registered new interface driver usbhid
Feb 14 11:49:12 linux-ytaf kernel: usbhid: USB HID core driver
Feb 14 11:49:12 linux-ytaf kernel: input: Razer Razer Lycosa as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1:1.0/0003:1532:0109.0001/input/input6
Feb 14 11:49:12 linux-ytaf kernel: usb 1-1.4: New USB device found, idVendor=06a3, idProduct=0ccb
Feb 14 11:49:12 linux-ytaf kernel: usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 14 11:49:12 linux-ytaf kernel: usb 1-1.4: Product: Cyborg R.A.T.7 Mouse
Feb 14 11:49:12 linux-ytaf kernel: usb 1-1.4: Manufacturer: Saitek
Feb 14 11:49:12 linux-ytaf kernel: hid-generic 0003:1532:0109.0001: input,hidraw0: USB HID v1.10 Keyboard [Razer Razer Lycosa] on usb-0000:00:1d.0-1.1/input0
Feb 14 11:49:12 linux-ytaf kernel: input: Razer Razer Lycosa as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1:1.1/0003:1532:0109.0002/input/input7
Feb 14 11:49:12 linux-ytaf kernel: hid-generic 0003:1532:0109.0002: input,hidraw1: USB HID v1.10 Device [Razer Razer Lycosa] on usb-0000:00:1d.0-1.1/input1
Feb 14 11:49:12 linux-ytaf kernel: Console: switching to colour frame buffer device 210x65
Feb 14 11:49:12 linux-ytaf kernel: nouveau 0000:02:00.0: fb0: nouveaufb frame buffer device
Feb 14 11:49:12 linux-ytaf kernel: nouveau 0000:02:00.0: registered panic notifier
Feb 14 11:49:12 linux-ytaf kernel: [drm] Initialized nouveau 1.2.2 20120801 for 0000:02:00.0 on minor 0
Feb 14 11:49:12 linux-ytaf kernel: [drm] Memory usable by graphics device = 2048M
Feb 14 11:49:12 linux-ytaf kernel: [drm] Replacing VGA console driver
Feb 14 11:49:12 linux-ytaf kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Feb 14 11:49:12 linux-ytaf kernel: [drm] Driver supports precise vblank timestamp query.
Feb 14 11:49:12 linux-ytaf kernel: vgaarb: device changed decodes: PCI:0000:02:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
Feb 14 11:49:12 linux-ytaf kernel: [drm] Initialized i915 1.6.0 20150327 for 0000:00:02.0 on minor 1
Feb 14 11:49:12 linux-ytaf kernel: [drm] GMBUS [i915 gmbus vga] timed out, falling back to bit banging on pin 2
Feb 14 11:49:12 linux-ytaf kernel: i915 0000:00:02.0: No connectors reported connected with modes
Feb 14 11:49:12 linux-ytaf kernel: [drm] Cannot find any crtc or sizes - going 1024x768
Feb 14 11:49:12 linux-ytaf kernel: i915 0000:00:02.0: fb1: inteldrmfb frame buffer device
Feb 14 11:49:13 linux-ytaf kernel: scsi 8:0:0:0: Direct-Access     TOSHIBA  TransMemory      PMAP PQ: 0 ANSI: 6
Feb 14 11:49:13 linux-ytaf kernel: sd 8:0:0:0: Attached scsi generic sg3 type 0
Feb 14 11:49:13 linux-ytaf kernel: sd 8:0:0:0: [sdc] 30228480 512-byte logical blocks: (15.4 GB/14.4 GiB)
Feb 14 11:49:13 linux-ytaf kernel: sd 8:0:0:0: [sdc] Write Protect is off
Feb 14 11:49:13 linux-ytaf kernel: sd 8:0:0:0: [sdc] Mode Sense: 45 00 00 00
Feb 14 11:49:13 linux-ytaf kernel: sd 8:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Feb 14 11:49:13 linux-ytaf kernel:  sdc: sdc1
Feb 14 11:49:13 linux-ytaf kernel: sd 8:0:0:0: [sdc] Attached SCSI removable disk
Feb 14 11:49:13 linux-ytaf kernel: PM: Starting manual resume from disk
Feb 14 11:49:13 linux-ytaf kernel: PM: Hibernation image partition 8:18 present
Feb 14 11:49:13 linux-ytaf kernel: PM: Looking for hibernation image.
Feb 14 11:49:13 linux-ytaf kernel: PM: Image not found (code -22)
Feb 14 11:49:13 linux-ytaf kernel: PM: Hibernation image not present or could not be loaded.
Feb 14 11:49:13 linux-ytaf kernel: BTRFS info (device sdb3): disk space caching is enabled
Feb 14 11:49:13 linux-ytaf kernel: BTRFS: has skinny extents
Feb 14 11:49:13 linux-ytaf systemd-journal[187]: Journal stopped
Feb 14 11:49:15 linux-ytaf systemd-journal[477]: Runtime journal is using 8.0M (max allowed 394.0M, trying to leave 591.0M free of 3.8G available → current limit 394.0M).
Feb 14 11:49:15 linux-ytaf systemd-journal[477]: Runtime journal is using 8.0M (max allowed 394.0M, trying to leave 591.0M free of 3.8G available → current limit 394.0M).
Feb 14 11:49:15 linux-ytaf kernel: random: nonblocking pool is initialized
Feb 14 11:49:15 linux-ytaf systemd[1]: RTC configured in localtime, applying delta of 60 minutes to system time.
Feb 14 11:49:15 linux-ytaf systemd-journal[477]: Journal started
Feb 14 11:49:15 linux-ytaf systemd-udevd[494]: starting version 210
Feb 14 11:49:15 linux-ytaf systemd-udevd[494]: Network interface NamePolicy= disabled on kernel commandline, ignoring.
Feb 14 11:49:15 linux-ytaf systemd-udevd[494]: invalid key/value pair in file /usr/lib/udev/rules.d/51-android.rules on line 115,starting at character 57 ('')
Feb 14 11:49:16 linux-ytaf kernel: BTRFS info (device sdb3): disk space caching is enabled
Feb 14 11:49:16 linux-ytaf kernel: thermal LNXTHERM:00: registered as thermal_zone0
Feb 14 11:49:16 linux-ytaf kernel: ACPI: Thermal Zone [TZ00] (28 C)
Feb 14 11:49:16 linux-ytaf kernel: thermal LNXTHERM:01: registered as thermal_zone1
Feb 14 11:49:16 linux-ytaf kernel: ACPI: Thermal Zone [TZ01] (30 C)
Feb 14 11:49:16 linux-ytaf kernel: input: PC Speaker as /devices/platform/pcspkr/input/input8
Feb 14 11:49:16 linux-ytaf kernel: asus_wmi: ASUS WMI generic driver loaded
Feb 14 11:49:16 linux-ytaf kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Feb 14 11:49:16 linux-ytaf kernel: pps_core: LinuxPPS API ver. 1 registered
Feb 14 11:49:16 linux-ytaf kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
Feb 14 11:49:16 linux-ytaf kernel: PTP clock support registered
Feb 14 11:49:16 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20150410/utaddress-254)
Feb 14 11:49:16 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 11:49:16 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150410/utaddress-254)
Feb 14 11:49:16 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150410/utaddress-254)
Feb 14 11:49:16 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 11:49:16 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150410/utaddress-254)
Feb 14 11:49:16 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150410/utaddress-254)
Feb 14 11:49:16 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 11:49:16 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150410/utaddress-254)
Feb 14 11:49:16 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150410/utaddress-254)
Feb 14 11:49:16 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 11:49:16 linux-ytaf kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
Feb 14 11:49:16 linux-ytaf kernel: asus_wmi: Initialization: 0x0
Feb 14 11:49:16 linux-ytaf kernel: asus_wmi: BIOS WMI version: 0.9
Feb 14 11:49:16 linux-ytaf kernel: asus_wmi: SFUN value: 0x0
Feb 14 11:49:16 linux-ytaf kernel: input: Eee PC WMI hotkeys as /devices/platform/eeepc-wmi/input/input9
Feb 14 11:49:16 linux-ytaf kernel: asus_wmi: Disabling ACPI video driver
Feb 14 11:49:16 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000580-0x000000000000059F conflicts with OpRegion 0x0000000000000580-0x000000000000058F (\_SB_.PCI0.SBUS.SMBI) (20150410/utaddress-254)
Feb 14 11:49:16 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000580-0x000000000000059F conflicts with OpRegion 0x0000000000000580-0x000000000000059F (\_SB_.PCI0.SMB_.SMIO) (20150410/utaddress-254)
Feb 14 11:49:16 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 11:49:16 linux-ytaf kernel: iTCO_vendor_support: vendor-support=0
Feb 14 11:49:16 linux-ytaf kernel: e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
Feb 14 11:49:16 linux-ytaf kernel: e1000e: Copyright(c) 1999 - 2014 Intel Corporation.
Feb 14 11:49:16 linux-ytaf kernel: e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
Feb 14 11:49:16 linux-ytaf kernel: iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
Feb 14 11:49:16 linux-ytaf kernel: iTCO_wdt: Found a Cougar Point TCO device (Version=2, TCOBASE=0x0460)
Feb 14 11:49:16 linux-ytaf kernel: iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
Feb 14 11:49:16 linux-ytaf kernel: AVX version of gcm_enc/dec engaged.
Feb 14 11:49:16 linux-ytaf kernel: AES CTR mode by8 optimization enabled
Feb 14 11:49:16 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: registered PHC clock
Feb 14 11:49:16 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) c8:60:00:09:38:76
Feb 14 11:49:16 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
Feb 14 11:49:16 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: FFFFFF-0FF
Feb 14 11:49:17 linux-ytaf kernel: snd_hda_intel 0000:00:1b.0: enabling device (0000 -> 0002)
Feb 14 11:49:17 linux-ytaf kernel: snd_hda_intel 0000:02:00.1: enabling device (0000 -> 0002)
Feb 14 11:49:17 linux-ytaf kernel: snd_hda_intel 0000:02:00.1: Disabling MSI
Feb 14 11:49:17 linux-ytaf kernel: snd_hda_intel 0000:02:00.1: Handle VGA-switcheroo audio client
Feb 14 11:49:17 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC889: line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line
Feb 14 11:49:17 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Feb 14 11:49:17 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
Feb 14 11:49:17 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
Feb 14 11:49:17 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    dig-out=0x11/0x1e
Feb 14 11:49:17 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    inputs:
Feb 14 11:49:17 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:      Front Mic=0x19
Feb 14 11:49:17 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:      Rear Mic=0x18
Feb 14 11:49:17 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:      Line=0x1a
Feb 14 11:49:17 linux-ytaf mtp-probe[621]: checking bus 5, device 2: "/sys/devices/pci0000:00/0000:00:1c.5/0000:05:00.0/usb5/5-2"
Feb 14 11:49:17 linux-ytaf mtp-probe[619]: checking bus 4, device 3: "/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1"
Feb 14 11:49:17 linux-ytaf mtp-probe[618]: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4"
Feb 14 11:49:17 linux-ytaf mtp-probe[619]: bus: 4, device: 3 was not an MTP device
Feb 14 11:49:17 linux-ytaf mtp-probe[618]: bus: 1, device: 3 was not an MTP device
Feb 14 11:49:17 linux-ytaf mtp-probe[621]: bus: 5, device: 2 was not an MTP device
Feb 14 11:49:17 linux-ytaf kernel: input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
Feb 14 11:49:17 linux-ytaf kernel: input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
Feb 14 11:49:17 linux-ytaf kernel: input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
Feb 14 11:49:17 linux-ytaf kernel: input: HDA Intel PCH Line Out Front as /devices/pci0000:00/0000:00:1b.0/sound/card0/input13
Feb 14 11:49:17 linux-ytaf kernel: input: HDA Intel PCH Line Out Surround as /devices/pci0000:00/0000:00:1b.0/sound/card0/input14
Feb 14 11:49:17 linux-ytaf kernel: input: HDA Intel PCH Line Out CLFE as /devices/pci0000:00/0000:00:1b.0/sound/card0/input15
Feb 14 11:49:17 linux-ytaf kernel: input: HDA Intel PCH Line Out Side as /devices/pci0000:00/0000:00:1b.0/sound/card0/input16
Feb 14 11:49:17 linux-ytaf kernel: input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input17
Feb 14 11:49:17 linux-ytaf kernel: input: Saitek Cyborg R.A.T.7 Mouse as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/0003:06A3:0CCB.0003/input/input18
Feb 14 11:49:17 linux-ytaf kernel: saitek 0003:06A3:0CCB.0003: input,hidraw2: USB HID v1.11 Mouse [Saitek Cyborg R.A.T.7 Mouse] on usb-0000:00:1a.0-1.4/input0
Feb 14 11:49:17 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input19
Feb 14 11:49:17 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input20
Feb 14 11:49:17 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input21
Feb 14 11:49:17 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input22
Feb 14 11:49:17 linux-ytaf kernel: Adding 2104316k swap on /dev/sdb2.  Priority:-1 extents:1 across:2104316k FS
Feb 14 11:49:17 linux-ytaf kernel: FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Feb 14 11:49:17 linux-ytaf systemd-fsck[696]: /sbin/fsck.xfs: XFS file system.
Feb 14 11:49:17 linux-ytaf kernel: SGI XFS with ACLs, security attributes, realtime, no debug enabled
Feb 14 11:49:17 linux-ytaf kernel: XFS (sdb4): Mounting V5 Filesystem
Feb 14 11:49:18 linux-ytaf kernel: XFS (sdb4): Starting recovery (logdev: internal)
Feb 14 11:49:18 linux-ytaf kernel: XFS (sdb4): Ending recovery (logdev: internal)
Feb 14 11:49:19 linux-ytaf systemd-journal[477]: Permanent journal is using 41.1M (max allowed 4.0G, trying to leave 4.0G free of 32.9G available → current limit 4.0G).
Feb 14 11:49:19 linux-ytaf systemd-journal[477]: Time spent on flushing to /var is 32.944ms for 1031 entries.
Feb 14 11:49:19 linux-ytaf kernel: audit: type=1305 audit(1455446959.017:2): audit_pid=773 old=0 auid=4294967295 ses=4294967295 res=1
Feb 14 11:49:19 linux-ytaf auditd[773]: Started dispatcher: /sbin/audispd pid: 779
Feb 14 11:49:19 linux-ytaf audispd[779]: priority_boost_parser called with: 4
Feb 14 11:49:19 linux-ytaf audispd[779]: max_restarts_parser called with: 10
Feb 14 11:49:19 linux-ytaf audispd[779]: No plugins found, exiting
Feb 14 11:49:19 linux-ytaf auditd[773]: Init complete, auditd 2.3.6 listening for events (startup state enable)
Feb 14 11:49:19 linux-ytaf auditctl[774]: No rules
Feb 14 11:49:19 linux-ytaf auditctl[774]: AUDIT_STATUS: enabled=1 flag=1 pid=773 rate_limit=0 backlog_limit=320 lost=0 backlog=0
Feb 14 11:49:24 linux-ytaf boot.apparmor[780]: Starting AppArmor ..done
Feb 14 11:49:24 linux-ytaf dbus-daemon[949]: Unknown username "srvGeoClue" in message bus configuration file
Feb 14 11:49:24 linux-ytaf alsactl[960]: /usr/sbin/alsactl: load_state:1683: Cannot open /var/lib/alsa/asound.state for reading: No such file or directory
Feb 14 11:49:24 linux-ytaf alsactl[960]: Found hardware: "HDA-Intel" "Intel CougarPoint HDMI" "HDA:10ec0889,1043846b,00100004 HDA:80862805,80860101,00100000" "0x1043" "0x84dc"
Feb 14 11:49:24 linux-ytaf alsactl[960]: Hardware is initialized using a generic method
Feb 14 11:49:24 linux-ytaf alsactl[960]: Found hardware: "HDA-Intel" "Nvidia GPU 40 HDMI/DP" "HDA:10de0040,00000000,00100100" "0x0000" "0x0000"
Feb 14 11:49:24 linux-ytaf alsactl[960]: Hardware is initialized using a generic method
Feb 14 11:49:24 linux-ytaf avahi-daemon[950]: Found user 'avahi' (UID 486) and group 'avahi' (GID 485).
Feb 14 11:49:24 linux-ytaf avahi-daemon[950]: Successfully dropped root privileges.
Feb 14 11:49:24 linux-ytaf avahi-daemon[950]: avahi-daemon 0.6.31 starting up.
Feb 14 11:49:24 linux-ytaf avahi-daemon[950]: Loading service file /etc/avahi/services/sftp-ssh.service.
Feb 14 11:49:24 linux-ytaf avahi-daemon[950]: Loading service file /etc/avahi/services/ssh.service.
Feb 14 11:49:24 linux-ytaf avahi-daemon[950]: Network interface enumeration completed.
Feb 14 11:49:24 linux-ytaf avahi-daemon[950]: Registering HINFO record with values 'X86_64'/'LINUX'.
Feb 14 11:49:24 linux-ytaf avahi-daemon[950]: Server startup complete. Host name is linux-ytaf.local. Local service cookie is 378072868.
Feb 14 11:49:24 linux-ytaf avahi-daemon[950]: Service "linux-ytaf" (/etc/avahi/services/ssh.service) successfully established.
Feb 14 11:49:24 linux-ytaf avahi-daemon[950]: Service "linux-ytaf" (/etc/avahi/services/sftp-ssh.service) successfully established.
Feb 14 11:49:24 linux-ytaf display-manager[979]: /etc/vconsole.conf available
Feb 14 11:49:24 linux-ytaf display-manager[979]: KEYMAP: de-latin1-nodeadkeys
Feb 14 11:49:24 linux-ytaf display-manager[979]: Command: localectl set-keymap de-latin1-nodeadkeys
Feb 14 11:49:24 linux-ytaf smartd[956]: smartd 6.2 2013-11-07 r3856 [x86_64-linux-4.1.15-8-default] (SUSE RPM)
Feb 14 11:49:24 linux-ytaf smartd[956]: Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
Feb 14 11:49:24 linux-ytaf smartd[956]: Opened configuration file /etc/smartd.conf
Feb 14 11:49:24 linux-ytaf smartd[956]: Drive: DEVICESCAN, implied '-a' Directive on line 26 of file /etc/smartd.conf
Feb 14 11:49:24 linux-ytaf smartd[956]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
Feb 14 11:49:24 linux-ytaf smartd[956]: Device: /dev/sda, type changed from 'scsi' to 'sat'
Feb 14 11:49:24 linux-ytaf smartd[956]: Device: /dev/sda [SAT], opened
Feb 14 11:49:24 linux-ytaf smartd[956]: Device: /dev/sda [SAT], SAMSUNG SSD 830 Series, S/N:S0Z4NEAC906195, WWN:5-002538-043584d30, FW:CXM03B1Q, 256 GB
Feb 14 11:49:24 linux-ytaf display-manager[979]: I: Using systemd /usr/share/systemd/kbd-model-map mapping
Feb 14 11:49:24 linux-ytaf smartd[956]: Device: /dev/sda [SAT], found in smartd database: Samsung based SSDs
Feb 14 11:49:24 linux-ytaf dbus[949]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service'
Feb 14 11:49:24 linux-ytaf dbus[949]: [system] Successfully activated service 'org.freedesktop.locale1'
Feb 14 11:49:24 linux-ytaf smartd[956]: Device: /dev/sda [SAT], can't monitor Current_Pending_Sector count - no Attribute 197
Feb 14 11:49:24 linux-ytaf smartd[956]: Device: /dev/sda [SAT], can't monitor Offline_Uncorrectable count - no Attribute 198
Feb 14 11:49:24 linux-ytaf smartd[956]: Device: /dev/sda [SAT], is SMART capable. Adding to "monitor" list.
Feb 14 11:49:24 linux-ytaf smartd[956]: Device: /dev/sda [SAT], state read from /var/lib/smartmontools/smartd.SAMSUNG_SSD_830_Series-S0Z4NEAC906195.ata.state
Feb 14 11:49:24 linux-ytaf smartd[956]: Device: /dev/sdb, type changed from 'scsi' to 'sat'
Feb 14 11:49:24 linux-ytaf smartd[956]: Device: /dev/sdb [SAT], opened
Feb 14 11:49:24 linux-ytaf smartd[956]: Device: /dev/sdb [SAT], TOSHIBA HDWD110, S/N:Y5GDEMGFS, WWN:5-000039-fe7c5a79c, FW:MS2OA8J0, 1.00 TB
Feb 14 11:49:24 linux-ytaf smartd[956]: Device: /dev/sdb [SAT], not found in smartd database.
Feb 14 11:49:25 linux-ytaf kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
Feb 14 11:49:25 linux-ytaf kernel: nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
Feb 14 11:49:25 linux-ytaf kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Feb 14 11:49:25 linux-ytaf ModemManager[952]: <info>  ModemManager (version 1.4.10) starting in system bus...
Feb 14 11:49:25 linux-ytaf dbus[949]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Feb 14 11:49:25 linux-ytaf polkitd[1025]: Started polkitd version 0.113
Feb 14 11:49:26 linux-ytaf polkitd[1025]: Loading rules from directory /etc/polkit-1/rules.d
Feb 14 11:49:26 linux-ytaf polkitd[1025]: Loading rules from directory /usr/share/polkit-1/rules.d
Feb 14 11:49:26 linux-ytaf polkitd[1025]: Finished loading, compiling and executing 3 rules
Feb 14 11:49:26 linux-ytaf dbus[949]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Feb 14 11:49:26 linux-ytaf polkitd[1025]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
Feb 14 11:49:26 linux-ytaf SuSEfirewall2[1053]: Firewall rules set to CLOSE.
Feb 14 11:49:26 linux-ytaf kernel: No iBFT detected.
Feb 14 11:49:26 linux-ytaf smartd[956]: Device: /dev/sdb [SAT], is SMART capable. Adding to "monitor" list.
Feb 14 11:49:26 linux-ytaf smartd[956]: Device: /dev/sdb [SAT], state read from /var/lib/smartmontools/smartd.TOSHIBA_HDWD110-Y5GDEMGFS.ata.state
Feb 14 11:49:26 linux-ytaf smartd[956]: Monitoring 2 ATA and 0 SCSI devices
Feb 14 11:49:26 linux-ytaf smartd[956]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 76 to 77
Feb 14 11:49:26 linux-ytaf kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Feb 14 11:49:26 linux-ytaf smartd[956]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 222 to 253
Feb 14 11:49:27 linux-ytaf smartd[956]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.SAMSUNG_SSD_830_Series-S0Z4NEAC906195.ata.state
Feb 14 11:49:27 linux-ytaf smartd[956]: Device: /dev/sdb [SAT], state written to /var/lib/smartmontools/smartd.TOSHIBA_HDWD110-Y5GDEMGFS.ata.state
Feb 14 11:49:28 linux-ytaf ModemManager[952]: <info>  Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin
Feb 14 11:49:28 linux-ytaf logger[1059]: /etc/init.d/xdm: No changes for /etc/X11/xdm/Xservers
Feb 14 11:49:28 linux-ytaf logger[1059]: /etc/init.d/xdm: No changes for /etc/X11/xdm/xdm-config
Feb 14 11:49:28 linux-ytaf sddm[1225]: Starting...
Feb 14 11:49:28 linux-ytaf sddm[1225]: Adding new display on vt 7 ...
Feb 14 11:49:28 linux-ytaf sddm[1225]: Display server starting...
Feb 14 11:49:28 linux-ytaf sddm[1225]: Running: /usr/bin/X -nolisten tcp -auth /run/sddm/{af3e8e23-064b-4b51-97ef-02df70fb9e97} -background none -noreset -displayfd 17 vt7
Feb 14 11:49:28 linux-ytaf display-manager[979]: Starting service sddm..done
Feb 14 11:49:29 linux-ytaf kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Feb 14 11:49:29 linux-ytaf kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Feb 14 11:49:29 linux-ytaf wickedd-dhcp4[1061]: eth0: Request to acquire DHCPv4 lease with UUID b65bc056-1127-0700-2804-000005000000
Feb 14 11:49:29 linux-ytaf wickedd-dhcp6[1060]: eth0: Request to acquire DHCPv6 lease with UUID b65bc056-1127-0700-2804-000006000000 in mode auto
Feb 14 11:49:29 linux-ytaf kernel: NET: Registered protocol family 17
Feb 14 11:49:30 linux-ytaf sddm[1225]: Running display setup script  "/etc/X11/xdm/Xsetup"
Feb 14 11:49:30 linux-ytaf sddm[1225]: Socket server starting...
Feb 14 11:49:30 linux-ytaf sddm[1225]: Socket server started.
Feb 14 11:49:30 linux-ytaf sddm[1225]: Greeter starting...
Feb 14 11:49:30 linux-ytaf sddm[1225]: Adding cookie to "/run/sddm/{af3e8e23-064b-4b51-97ef-02df70fb9e97}"
Feb 14 11:49:30 linux-ytaf sddm-helper[1385]: [PAM] Starting...
Feb 14 11:49:30 linux-ytaf sddm-helper[1385]: [PAM] Authenticating...
Feb 14 11:49:30 linux-ytaf sddm-helper[1385]: [PAM] returning.
Feb 14 11:49:30 linux-ytaf sddm-helper[1385]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
Feb 14 11:49:30 linux-ytaf systemd[1387]: pam_unix(systemd-user:session): session opened for user sddm by (uid=0)
Feb 14 11:49:30 linux-ytaf avahi-daemon[950]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::ca60:ff:fe09:3876.
Feb 14 11:49:30 linux-ytaf avahi-daemon[950]: New relevant interface eth0.IPv6 for mDNS.
Feb 14 11:49:30 linux-ytaf avahi-daemon[950]: Registering new address record for fe80::ca60:ff:fe09:3876 on eth0.*.
Feb 14 11:49:33 linux-ytaf wickedd-dhcp4[1061]: eth0: Committed DHCPv4 lease with address 192.168.178.12 (lease time 864000 sec, renew in 432000 sec, rebind in 756000 sec)
Feb 14 11:49:33 linux-ytaf avahi-daemon[950]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.178.12.
Feb 14 11:49:33 linux-ytaf avahi-daemon[950]: New relevant interface eth0.IPv4 for mDNS.
Feb 14 11:49:33 linux-ytaf avahi-daemon[950]: Registering new address record for 192.168.178.12 on eth0.IPv4.
Feb 14 11:49:33 linux-ytaf wickedd[1064]: eth0: Notified neighbours about IP address 192.168.178.12
Feb 14 11:49:33 linux-ytaf dbus[949]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
Feb 14 11:49:34 linux-ytaf udisksd[1567]: udisks daemon version 2.1.6 starting
Feb 14 11:49:34 MM-Home udisksd[1567]: [103B blob data]
Feb 14 11:49:34 MM-Home udisksd[1567]: [103B blob data]
Feb 14 11:49:34 MM-Home dbus[949]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Feb 14 11:49:34 MM-Home udisksd[1567]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Feb 14 11:49:34 MM-Home dbus[949]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
Feb 14 11:49:34 MM-Home dbus[949]: [system] Successfully activated service 'org.freedesktop.UPower'
Feb 14 11:49:44 MM-Home wicked[1070]: lo              up
Feb 14 11:49:44 MM-Home wicked[1070]: eth0            up
Feb 14 11:49:44 MM-Home echo[1628]: Starting mail service (Postfix)
Feb 14 11:49:44 MM-Home iscsiadm[1629]: iscsiadm: No records found
Feb 14 11:49:44 MM-Home SuSEfirewall2[1662]: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Feb 14 11:49:44 MM-Home SuSEfirewall2[1670]: using default zone 'ext' for interface eth0
Feb 14 11:49:44 MM-Home ntpd[1646]: ntpd 4.2.8p4@1.3265-o Thu Dec 17 05:32:52 UTC 2015 (1): Starting
Feb 14 11:49:44 MM-Home ntpd[1646]: Command line: /usr/sbin/ntpd -p /var/run/ntp/ntpd.pid -g -u ntp:ntp -c /etc/ntp.conf
Feb 14 11:49:44 MM-Home sntp[1752]: sntp 4.2.8p4@1.3265-o Thu Dec 17 05:32:29 UTC 2015 (1)
Feb 14 11:49:44 MM-Home sntp[1752]: kod_init_kod_db(): Cannot open KoD db file /var/db/ntp-kod: No such file or directory
Feb 14 11:49:44 MM-Home ntpd[1751]: proto: precision = 0.110 usec (-23)
Feb 14 11:49:44 MM-Home ntpd[1751]: switching logging to file /var/log/ntp
Feb 14 11:49:44 MM-Home sntp[1752]: 2016-02-14 11:49:44.375121 (-0100) -0.32366 +/- 0.257274 192.168.178.1 s3 no-leap
Feb 14 11:49:44 MM-Home start-ntpd[1634]: Starting network time protocol daemon (NTPD)sntp 4.2.8p4@1.3265-o Thu Dec 17 05:32:29 UTC 2015 (1)
Feb 14 11:49:44 MM-Home start-ntpd[1634]: kod_init_kod_db(): Cannot open KoD db file /var/db/ntp-kod: No such file or directory
Feb 14 11:49:44 MM-Home start-ntpd[1634]: 2016-02-14 11:49:44.375121 (-0100) -0.32366 +/- 0.257274 192.168.178.1 s3 no-leap
Feb 14 11:49:44 MM-Home SuSEfirewall2[1776]: Firewall rules successfully set
Feb 14 11:49:44 MM-Home /usr/sbin/start-ntpd[1784]: runtime configuration: server 192.168.178.1
Feb 14 11:49:44 MM-Home postfix/postfix-script[1810]: starting the Postfix mail system
Feb 14 11:49:44 MM-Home postfix/master[1812]: daemon started -- version 2.11.6, configuration /etc/postfix
Feb 14 11:49:44 MM-Home cron[1829]: (CRON) INFO (RANDOM_DELAY will be scaled with factor 54% if used.)
Feb 14 11:49:44 MM-Home cron[1829]: (CRON) INFO (running with inotify support)
Feb 14 11:53:01 MM-Home kernel: nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
Feb 14 11:53:36 MM-Home sddm[1225]: Message received from greeter: Login
Feb 14 11:53:36 MM-Home sddm[1225]: Reading from "/usr/share/xsessions/plasma5.desktop"
Feb 14 11:53:36 MM-Home sddm-helper[1836]: [PAM] Starting...
Feb 14 11:53:36 MM-Home sddm-helper[1836]: [PAM] Authenticating...
Feb 14 11:53:36 MM-Home sddm-helper[1836]: [PAM] Preparing to converse...
Feb 14 11:53:36 MM-Home sddm-helper[1836]: [PAM] Conversation with 1 messages
Feb 14 11:53:36 MM-Home sddm-helper[1836]: [PAM] returning.
Feb 14 11:53:36 MM-Home sddm[1225]: Authenticated successfully
Feb 14 11:53:36 MM-Home sddm-helper[1836]: pam_unix(sddm:session): session opened for user marc by (uid=0)
Feb 14 11:53:37 MM-Home systemd[1837]: pam_unix(systemd-user:session): session opened for user marc by (uid=0)
Feb 14 11:53:37 MM-Home sddm[1225]: Auth: sddm-helper exited successfully
Feb 14 11:53:37 MM-Home sddm[1225]: Greeter stopped.
Feb 14 11:53:37 MM-Home sddm-helper[1836]: Starting: "/etc/X11/xdm/Xsession" "/usr/bin/startkde"
Feb 14 11:53:37 MM-Home sddm-helper[1839]: Adding cookie to "/home/marc/.Xauthority"
Feb 14 11:53:37 MM-Home sddm[1225]: Session started
Feb 14 11:53:38 MM-Home dbus[949]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Feb 14 11:53:38 MM-Home org.kde.powerdevil.backlighthelper[949]: powerdevil: no kernel backlight interface found
Feb 14 11:53:38 MM-Home dbus[949]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Feb 14 11:53:39 MM-Home polkitd[1025]: Registered Authentication Agent for unix-session:2 (system bus name :1.37 [/usr/lib64/libexec/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale de_DE.UTF-8)
Feb 14 11:53:39 MM-Home dbus[949]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service'
Feb 14 11:53:39 MM-Home dbus[949]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Feb 14 11:53:39 MM-Home rtkit-daemon[1993]: Successfully called chroot.
Feb 14 11:53:39 MM-Home rtkit-daemon[1993]: Successfully dropped privileges.
Feb 14 11:53:39 MM-Home rtkit-daemon[1993]: Successfully limited resources.
Feb 14 11:53:39 MM-Home rtkit-daemon[1993]: Running.
Feb 14 11:53:39 MM-Home rtkit-daemon[1993]: Canary thread running.
Feb 14 11:53:39 MM-Home rtkit-daemon[1993]: Watchdog thread running.
Feb 14 11:53:39 MM-Home rtkit-daemon[1993]: Successfully made thread 1992 of process 1992 (/usr/bin/pulseaudio) owned by 'marc' high priority at nice level -11.
Feb 14 11:53:39 MM-Home rtkit-daemon[1993]: Supervising 1 threads of 1 processes of 1 users.
Feb 14 11:53:41 MM-Home rtkit-daemon[1993]: Supervising 1 threads of 1 processes of 1 users.
Feb 14 11:53:41 MM-Home rtkit-daemon[1993]: Successfully made thread 2016 of process 1992 (/usr/bin/pulseaudio) owned by 'marc' RT at priority 5.
Feb 14 11:53:41 MM-Home rtkit-daemon[1993]: Supervising 2 threads of 1 processes of 1 users.
Feb 14 11:53:42 MM-Home rtkit-daemon[1993]: Supervising 2 threads of 1 processes of 1 users.
Feb 14 11:53:42 MM-Home rtkit-daemon[1993]: Successfully made thread 2019 of process 1992 (/usr/bin/pulseaudio) owned by 'marc' RT at priority 5.
Feb 14 11:53:42 MM-Home rtkit-daemon[1993]: Supervising 3 threads of 1 processes of 1 users.
Feb 14 11:53:42 MM-Home rtkit-daemon[1993]: Supervising 3 threads of 1 processes of 1 users.
Feb 14 11:53:42 MM-Home rtkit-daemon[1993]: Successfully made thread 2020 of process 1992 (/usr/bin/pulseaudio) owned by 'marc' RT at priority 5.
Feb 14 11:53:42 MM-Home rtkit-daemon[1993]: Supervising 4 threads of 1 processes of 1 users.
Feb 14 11:53:42 MM-Home dbus[949]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Feb 14 11:53:42 MM-Home bluetoothd[2021]: Bluetooth daemon 5.35
Feb 14 11:53:42 MM-Home dbus[949]: [system] Successfully activated service 'org.bluez'
Feb 14 11:53:42 MM-Home bluetoothd[2021]: Starting SDP server
Feb 14 11:53:42 MM-Home kernel: Bluetooth: Core ver 2.20
Feb 14 11:53:42 MM-Home kernel: NET: Registered protocol family 31
Feb 14 11:53:42 MM-Home kernel: Bluetooth: HCI device and connection manager initialized
Feb 14 11:53:42 MM-Home kernel: Bluetooth: HCI socket layer initialized
Feb 14 11:53:42 MM-Home kernel: Bluetooth: L2CAP socket layer initialized
Feb 14 11:53:42 MM-Home kernel: Bluetooth: SCO socket layer initialized
Feb 14 11:53:42 MM-Home kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Feb 14 11:53:42 MM-Home kernel: Bluetooth: BNEP filters: protocol multicast
Feb 14 11:53:42 MM-Home kernel: Bluetooth: BNEP socket layer initialized
Feb 14 11:53:42 MM-Home dbus[949]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Feb 14 11:53:42 MM-Home bluetoothd[2021]: Bluetooth management interface 1.9 initialized
Feb 14 11:53:42 MM-Home dbus[949]: [system] Successfully activated service 'org.freedesktop.hostname1'
Feb 14 11:53:42 MM-Home dbus[949]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service'
Feb 14 11:53:42 MM-Home PackageKit[2033]: daemon start
Feb 14 11:53:42 MM-Home dbus[949]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Feb 14 11:53:43 MM-Home PackageKit[2033]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 11:53:43 MM-Home PackageKit[2033]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 11:53:43 MM-Home PackageKit[2033]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 11:53:43 MM-Home PackageKit[2033]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 11:53:44 MM-Home PackageKit[2033]: refresh-cache transaction /1_ceecedaa from uid 1000 finished with failed after 893ms
Feb 14 11:53:44 MM-Home kernel: fuse init (API version 7.23)
Feb 14 11:53:44 MM-Home PackageKit[2033]: refresh-cache transaction /2_cbabbbaa from uid 1000 finished with failed after 305ms
Feb 14 11:54:02 MM-Home PackageKit[2033]: daemon quit
Feb 14 11:54:02 MM-Home packagekitd[2033]: (packagekitd:2033): GLib-CRITICAL **: Source ID 6 was not found when attempting to remove it
Feb 14 11:54:08 MM-Home dbus[949]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service'
Feb 14 11:54:08 MM-Home PackageKit[2084]: daemon start
Feb 14 11:54:08 MM-Home dbus[949]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Feb 14 11:54:08 MM-Home PackageKit[2084]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 11:54:08 MM-Home PackageKit[2084]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 11:54:08 MM-Home PackageKit[2084]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 11:54:08 MM-Home PackageKit[2084]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 11:54:08 MM-Home PackageKit[2084]: refresh-cache transaction /1_ebeccabd from uid 1000 finished with failed after 321ms
Feb 14 11:54:08 MM-Home PackageKit[2084]: refresh-cache transaction /2_cccbeaaa from uid 1000 finished with failed after 277ms
Feb 14 11:54:28 MM-Home PackageKit[2084]: daemon quit
Feb 14 11:54:28 MM-Home packagekitd[2084]: (packagekitd:2084): GLib-CRITICAL **: Source ID 6 was not found when attempting to remove it
Feb 14 11:55:23 MM-Home su[2126]: (to root) marc on pts/1
Feb 14 11:55:23 MM-Home su[2126]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 11:55:23 MM-Home su[2126]: pam_unix(su:session): session closed for user root
Feb 14 11:55:23 MM-Home su[2131]: (to root) marc on pts/1
Feb 14 11:55:23 MM-Home su[2131]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 11:56:35 MM-Home dbus[949]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Feb 14 11:56:35 MM-Home dbus[949]: [system] Successfully activated service 'org.opensuse.Snapper'
Feb 14 11:56:43 MM-Home kernel: st: Version 20101219, fixed bufsize 32768, s/g segs 256
Feb 14 11:56:43 MM-Home kernel: BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Feb 14 11:56:43 MM-Home kernel: EDD information not available.
Feb 14 11:56:50 MM-Home kernel: BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Feb 14 11:56:50 MM-Home kernel: EDD information not available.
Feb 14 11:56:55 MM-Home kernel: ppdev: user-space parallel port driver
Feb 14 11:56:55 MM-Home kernel: lp: driver loaded but no devices found
Feb 14 11:56:55 MM-Home kernel: lp: driver loaded but no devices found
Feb 14 11:56:56 MM-Home kernel: lp: driver loaded but no devices found
Feb 14 11:56:59 MM-Home kernel: BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Feb 14 11:56:59 MM-Home kernel: EDD information not available.
Feb 14 11:57:00 MM-Home kernel: BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Feb 14 11:57:00 MM-Home kernel: EDD information not available.
Feb 14 11:58:09 MM-Home dbus[949]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Feb 14 11:58:09 MM-Home dbus[949]: [system] Successfully activated service 'org.opensuse.Snapper'
Feb 14 11:59:03 MM-Home systemd-udevd[494]: Network interface NamePolicy= disabled on kernel commandline, ignoring.
Feb 14 11:59:04 MM-Home avahi-daemon[950]: Withdrawing address record for fe80::ca60:ff:fe09:3876 on eth0.
Feb 14 11:59:04 MM-Home avahi-daemon[950]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::ca60:ff:fe09:3876.
Feb 14 11:59:04 MM-Home avahi-daemon[950]: Interface eth0.IPv6 no longer relevant for mDNS.
Feb 14 11:59:04 MM-Home wickedd-dhcp4[1061]: eth0: Request to release DHCPv4 lease with UUID b65bc056-1127-0700-2804-000005000000
Feb 14 11:59:04 MM-Home avahi-daemon[950]: Withdrawing address record for 192.168.178.12 on eth0.
Feb 14 11:59:04 MM-Home avahi-daemon[950]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.178.12.
Feb 14 11:59:04 MM-Home avahi-daemon[950]: Interface eth0.IPv4 no longer relevant for mDNS.
Feb 14 11:59:04 MM-Home wickedd-dhcp6[1060]: eth0: no lease set
Feb 14 11:59:04 MM-Home kernel: e1000e: eth0 NIC Link is Down
Feb 14 11:59:07 MM-Home kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Feb 14 11:59:07 MM-Home wickedd-dhcp4[1061]: eth0: Request to acquire DHCPv4 lease with UUID b65bc056-1127-0700-2804-00000b000000
Feb 14 11:59:12 MM-Home wickedd-dhcp4[1061]: eth0: Committed DHCPv4 lease with address 192.168.178.12 (lease time 864000 sec, renew in 432000 sec, rebind in 756000 sec)
Feb 14 11:59:12 MM-Home avahi-daemon[950]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.178.12.
Feb 14 11:59:12 MM-Home avahi-daemon[950]: New relevant interface eth0.IPv4 for mDNS.
Feb 14 11:59:12 MM-Home avahi-daemon[950]: Registering new address record for 192.168.178.12 on eth0.IPv4.
Feb 14 11:59:12 MM-Home wickedd[1064]: eth0: Notified neighbours about IP address 192.168.178.12
Feb 14 11:59:17 MM-Home wicked[3105]: eth0            device-ready
Feb 14 11:59:17 MM-Home wicked[3105]: lo              up
Feb 14 11:59:17 MM-Home wicked[3105]: eth0            up
Feb 14 11:59:21 MM-Home postfix/postfix-script[3772]: refreshing the Postfix mail system
Feb 14 11:59:21 MM-Home postfix/master[1812]: reload -- version 2.11.6, configuration /etc/postfix
Feb 14 11:59:21 MM-Home postfix/master[1812]: warning: ignoring inet_protocols parameter value change
Feb 14 11:59:21 MM-Home postfix/master[1812]: warning: old value: "all", new value: "ipv4"
Feb 14 11:59:21 MM-Home postfix/master[1812]: warning: to change inet_protocols, stop and start Postfix
Feb 14 11:59:21 MM-Home dbus[949]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Feb 14 11:59:21 MM-Home dbus[949]: [system] Successfully activated service 'org.opensuse.Snapper'
Feb 14 12:00:01 MM-Home cron[3951]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 12:00:01 MM-Home systemd[3952]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 12:00:01 MM-Home CRON[3951]: pam_unix(crond:session): session closed for user root
Feb 14 12:00:01 MM-Home systemd[3953]: pam_unix(systemd-user:session): session closed for user root
Feb 14 12:00:49 MM-Home SuSEfirewall2[4273]: Firewall rules unloaded.
Feb 14 12:01:25 MM-Home SuSEfirewall2[4330]: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Feb 14 12:01:25 MM-Home SuSEfirewall2[4336]: using default zone 'ext' for interface eth0
Feb 14 12:01:25 MM-Home SuSEfirewall2[4392]: Firewall rules successfully set
Feb 14 12:01:36 MM-Home dbus[949]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Feb 14 12:01:36 MM-Home dbus[949]: [system] Successfully activated service 'org.opensuse.Snapper'
Feb 14 12:04:06 MM-Home dbus[949]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Feb 14 12:04:06 MM-Home dbus[949]: [system] Successfully activated service 'org.opensuse.Snapper'
Feb 14 12:06:15 MM-Home boot.apparmor[7176]: Restarting AppArmor ..done
Feb 14 12:06:16 MM-Home dbus[949]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Feb 14 12:06:16 MM-Home dbus[949]: [system] Successfully activated service 'org.opensuse.Snapper'
Feb 14 12:06:45 MM-Home systemd[1]: [/usr/lib/systemd/system/dm-event.socket:10] Unknown lvalue 'RemoveOnStop' in section 'Socket'
Feb 14 12:06:45 MM-Home SuSEfirewall2[8228]: Firewall rules unloaded.
Feb 14 12:06:46 MM-Home SuSEfirewall2[8250]: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Feb 14 12:06:46 MM-Home SuSEfirewall2[8256]: using default zone 'ext' for interface eth0
Feb 14 12:06:46 MM-Home SuSEfirewall2[8312]: Firewall rules successfully set
Feb 14 12:08:02 MM-Home systemd[1]: [/usr/lib/systemd/system/dm-event.socket:10] Unknown lvalue 'RemoveOnStop' in section 'Socket'
Feb 14 12:08:02 MM-Home SuSEfirewall2[8455]: Firewall rules unloaded.
Feb 14 12:08:02 MM-Home SuSEfirewall2[8476]: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Feb 14 12:08:02 MM-Home SuSEfirewall2[8482]: using default zone 'ext' for interface eth0
Feb 14 12:08:02 MM-Home SuSEfirewall2[8558]: Firewall rules successfully set
Feb 14 12:08:02 MM-Home dbus[949]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Feb 14 12:08:02 MM-Home dbus[949]: [system] Successfully activated service 'org.opensuse.Snapper'
-- Reboot --
Feb 14 12:11:43 linux-ytaf systemd-journal[187]: Runtime journal is using 8.0M (max allowed 394.0M, trying to leave 591.0M free of 3.8G available → current limit 394.0M).
Feb 14 12:11:43 linux-ytaf systemd-journal[187]: Runtime journal is using 8.0M (max allowed 394.0M, trying to leave 591.0M free of 3.8G available → current limit 394.0M).
Feb 14 12:11:43 linux-ytaf kernel: microcode: CPU0 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 12:11:43 linux-ytaf kernel: Initializing cgroup subsys cpuset
Feb 14 12:11:43 linux-ytaf kernel: Initializing cgroup subsys cpu
Feb 14 12:11:43 linux-ytaf kernel: Initializing cgroup subsys cpuacct
Feb 14 12:11:43 linux-ytaf kernel: Linux version 4.1.15-8-default (geeko@buildhost) (gcc version 4.8.5 (SUSE Linux) ) #1 SMP PREEMPT Wed Jan 20 16:41:00 UTC 2016 (0e3b3ab)
Feb 14 12:11:43 linux-ytaf kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.1.15-8-default root=UUID=21024970-7a27-4114-8525-d8dd026f23b6 ro resume=/dev/sdb2 splash=silent quiet showopts
Feb 14 12:11:43 linux-ytaf kernel: e820: BIOS-provided physical RAM map:
Feb 14 12:11:43 linux-ytaf kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Feb 14 12:11:43 linux-ytaf kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
Feb 14 12:11:43 linux-ytaf kernel: BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable
Feb 14 12:11:43 linux-ytaf kernel: BIOS-e820: [mem 0x0000000020000000-0x00000000201fffff] reserved
Feb 14 12:11:43 linux-ytaf kernel: BIOS-e820: [mem 0x0000000020200000-0x000000003fffffff] usable
Feb 14 12:11:43 linux-ytaf kernel: BIOS-e820: [mem 0x0000000040000000-0x00000000401fffff] reserved
Feb 14 12:11:43 linux-ytaf kernel: BIOS-e820: [mem 0x0000000040200000-0x00000000ca38efff] usable
Feb 14 12:11:43 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ca38f000-0x00000000ca5f1fff] reserved
Feb 14 12:11:43 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ca5f2000-0x00000000ca679fff] ACPI NVS
Feb 14 12:11:43 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ca67a000-0x00000000ca93efff] reserved
Feb 14 12:11:43 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ca93f000-0x00000000cab83fff] ACPI NVS
Feb 14 12:11:43 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cab84000-0x00000000cab91fff] ACPI data
Feb 14 12:11:43 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cab92000-0x00000000cabbefff] ACPI NVS
Feb 14 12:11:43 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cabbf000-0x00000000cabc3fff] ACPI data
Feb 14 12:11:43 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cabc4000-0x00000000cac06fff] ACPI NVS
Feb 14 12:11:43 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cac07000-0x00000000caffffff] usable
Feb 14 12:11:43 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cb800000-0x00000000cf9fffff] reserved
Feb 14 12:11:43 linux-ytaf kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Feb 14 12:11:43 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Feb 14 12:11:43 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Feb 14 12:11:43 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Feb 14 12:11:43 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Feb 14 12:11:43 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Feb 14 12:11:43 linux-ytaf kernel: BIOS-e820: [mem 0x0000000100000000-0x000000022f5fffff] usable
Feb 14 12:11:43 linux-ytaf kernel: NX (Execute Disable) protection: active
Feb 14 12:11:43 linux-ytaf kernel: e820: update [mem 0x0c826018-0x0c835c57] usable ==> usable
Feb 14 12:11:43 linux-ytaf kernel: e820: update [mem 0x0c836018-0x0c846057] usable ==> usable
Feb 14 12:11:43 linux-ytaf kernel: e820: update [mem 0x0c847018-0x0c856857] usable ==> usable
Feb 14 12:11:43 linux-ytaf kernel: e820: update [mem 0x0c857018-0x0c85ae57] usable ==> usable
Feb 14 12:11:43 linux-ytaf kernel: extended physical RAM map:
Feb 14 12:11:43 linux-ytaf kernel: reserve setup_data: [mem 0x0000000000000000-0x000000000009efff] usable
Feb 14 12:11:43 linux-ytaf kernel: reserve setup_data: [mem 0x000000000009f000-0x000000000009ffff] reserved
Feb 14 12:11:43 linux-ytaf kernel: reserve setup_data: [mem 0x0000000000100000-0x000000000c826017] usable
Feb 14 12:11:43 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c826018-0x000000000c835c57] usable
Feb 14 12:11:43 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c835c58-0x000000000c836017] usable
Feb 14 12:11:43 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c836018-0x000000000c846057] usable
Feb 14 12:11:43 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c846058-0x000000000c847017] usable
Feb 14 12:11:43 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c847018-0x000000000c856857] usable
Feb 14 12:11:43 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c856858-0x000000000c857017] usable
Feb 14 12:11:43 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c857018-0x000000000c85ae57] usable
Feb 14 12:11:43 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c85ae58-0x000000001fffffff] usable
Feb 14 12:11:43 linux-ytaf kernel: reserve setup_data: [mem 0x0000000020000000-0x00000000201fffff] reserved
Feb 14 12:11:43 linux-ytaf kernel: reserve setup_data: [mem 0x0000000020200000-0x000000003fffffff] usable
Feb 14 12:11:43 linux-ytaf kernel: reserve setup_data: [mem 0x0000000040000000-0x00000000401fffff] reserved
Feb 14 12:11:43 linux-ytaf kernel: reserve setup_data: [mem 0x0000000040200000-0x00000000ca38efff] usable
Feb 14 12:11:43 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ca38f000-0x00000000ca5f1fff] reserved
Feb 14 12:11:43 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ca5f2000-0x00000000ca679fff] ACPI NVS
Feb 14 12:11:43 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ca67a000-0x00000000ca93efff] reserved
Feb 14 12:11:43 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ca93f000-0x00000000cab83fff] ACPI NVS
Feb 14 12:11:43 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cab84000-0x00000000cab91fff] ACPI data
Feb 14 12:11:43 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cab92000-0x00000000cabbefff] ACPI NVS
Feb 14 12:11:43 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cabbf000-0x00000000cabc3fff] ACPI data
Feb 14 12:11:43 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cabc4000-0x00000000cac06fff] ACPI NVS
Feb 14 12:11:43 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cac07000-0x00000000caffffff] usable
Feb 14 12:11:43 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cb800000-0x00000000cf9fffff] reserved
Feb 14 12:11:43 linux-ytaf kernel: reserve setup_data: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Feb 14 12:11:43 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Feb 14 12:11:43 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Feb 14 12:11:43 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Feb 14 12:11:43 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Feb 14 12:11:43 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Feb 14 12:11:43 linux-ytaf kernel: reserve setup_data: [mem 0x0000000100000000-0x000000022f5fffff] usable
Feb 14 12:11:43 linux-ytaf kernel: efi: EFI v2.31 by American Megatrends
Feb 14 12:11:43 linux-ytaf kernel: efi:  ACPI=0xcab84000  ACPI 2.0=0xcab84000  SMBIOS=0xca427e98  MPS=0xfc990 
Feb 14 12:11:43 linux-ytaf kernel: SMBIOS 2.6 present.
Feb 14 12:11:43 linux-ytaf kernel: DMI: System manufacturer System Product Name/MAXIMUS IV GENE-Z/GEN3, BIOS 3603 11/09/2012
Feb 14 12:11:43 linux-ytaf kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Feb 14 12:11:43 linux-ytaf kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Feb 14 12:11:43 linux-ytaf kernel: AGP: No AGP bridge found
Feb 14 12:11:43 linux-ytaf kernel: e820: last_pfn = 0x22f600 max_arch_pfn = 0x400000000
Feb 14 12:11:43 linux-ytaf kernel: MTRR default type: uncachable
Feb 14 12:11:43 linux-ytaf kernel: MTRR fixed ranges enabled:
Feb 14 12:11:43 linux-ytaf kernel:   00000-9FFFF write-back
Feb 14 12:11:43 linux-ytaf kernel:   A0000-BFFFF uncachable
Feb 14 12:11:43 linux-ytaf kernel:   C0000-D3FFF write-protect
Feb 14 12:11:43 linux-ytaf kernel:   D4000-DFFFF uncachable
Feb 14 12:11:43 linux-ytaf kernel:   E0000-E7FFF write-through
Feb 14 12:11:43 linux-ytaf kernel:   E8000-FFFFF write-protect
Feb 14 12:11:43 linux-ytaf kernel: MTRR variable ranges enabled:
Feb 14 12:11:43 linux-ytaf kernel:   0 base 000000000 mask E00000000 write-back
Feb 14 12:11:43 linux-ytaf kernel:   1 base 200000000 mask FE0000000 write-back
Feb 14 12:11:43 linux-ytaf kernel:   2 base 220000000 mask FF0000000 write-back
Feb 14 12:11:43 linux-ytaf kernel:   3 base 0E0000000 mask FE0000000 uncachable
Feb 14 12:11:43 linux-ytaf kernel:   4 base 0D0000000 mask FF0000000 uncachable
Feb 14 12:11:43 linux-ytaf kernel:   5 base 0CC000000 mask FFC000000 uncachable
Feb 14 12:11:43 linux-ytaf kernel:   6 base 0CB800000 mask FFF800000 uncachable
Feb 14 12:11:43 linux-ytaf kernel:   7 base 22F800000 mask FFF800000 uncachable
Feb 14 12:11:43 linux-ytaf kernel:   8 base 22F600000 mask FFFE00000 uncachable
Feb 14 12:11:43 linux-ytaf kernel:   9 disabled
Feb 14 12:11:43 linux-ytaf kernel: PAT configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- UC  
Feb 14 12:11:43 linux-ytaf kernel: e820: update [mem 0xcb800000-0xffffffff] usable ==> reserved
Feb 14 12:11:43 linux-ytaf kernel: e820: last_pfn = 0xcb000 max_arch_pfn = 0x400000000
Feb 14 12:11:43 linux-ytaf kernel: found SMP MP-table at [mem 0x000fcd30-0x000fcd3f] mapped at [ffff8800000fcd30]
Feb 14 12:11:43 linux-ytaf kernel: Scanning 1 areas for low memory corruption
Feb 14 12:11:43 linux-ytaf kernel: Base memory trampoline at [ffff880000097000] 97000 size 24576
Feb 14 12:11:43 linux-ytaf kernel: reserving inaccessible SNB gfx pages
Feb 14 12:11:43 linux-ytaf kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
Feb 14 12:11:43 linux-ytaf kernel:  [mem 0x00000000-0x000fffff] page 4k
Feb 14 12:11:43 linux-ytaf kernel: BRK [0x0e21a000, 0x0e21afff] PGTABLE
Feb 14 12:11:43 linux-ytaf kernel: BRK [0x0e21b000, 0x0e21bfff] PGTABLE
Feb 14 12:11:43 linux-ytaf kernel: BRK [0x0e21c000, 0x0e21cfff] PGTABLE
Feb 14 12:11:43 linux-ytaf kernel: init_memory_mapping: [mem 0x22f400000-0x22f5fffff]
Feb 14 12:11:43 linux-ytaf kernel:  [mem 0x22f400000-0x22f5fffff] page 2M
Feb 14 12:11:43 linux-ytaf kernel: BRK [0x0e21d000, 0x0e21dfff] PGTABLE
Feb 14 12:11:43 linux-ytaf kernel: init_memory_mapping: [mem 0x220000000-0x22f3fffff]
Feb 14 12:11:43 linux-ytaf kernel:  [mem 0x220000000-0x22f3fffff] page 2M
Feb 14 12:11:43 linux-ytaf kernel: init_memory_mapping: [mem 0x200000000-0x21fffffff]
Feb 14 12:11:43 linux-ytaf kernel:  [mem 0x200000000-0x21fffffff] page 2M
Feb 14 12:11:43 linux-ytaf kernel: init_memory_mapping: [mem 0x00100000-0x1fffffff]
Feb 14 12:11:43 linux-ytaf kernel:  [mem 0x00100000-0x001fffff] page 4k
Feb 14 12:11:43 linux-ytaf kernel:  [mem 0x00200000-0x1fffffff] page 2M
Feb 14 12:11:43 linux-ytaf kernel: init_memory_mapping: [mem 0x20200000-0x3fffffff]
Feb 14 12:11:43 linux-ytaf kernel:  [mem 0x20200000-0x3fffffff] page 2M
Feb 14 12:11:43 linux-ytaf kernel: init_memory_mapping: [mem 0x40200000-0xca38efff]
Feb 14 12:11:43 linux-ytaf kernel:  [mem 0x40200000-0xca1fffff] page 2M
Feb 14 12:11:43 linux-ytaf kernel:  [mem 0xca200000-0xca38efff] page 4k
Feb 14 12:11:43 linux-ytaf kernel: BRK [0x0e21e000, 0x0e21efff] PGTABLE
Feb 14 12:11:43 linux-ytaf kernel: BRK [0x0e21f000, 0x0e21ffff] PGTABLE
Feb 14 12:11:43 linux-ytaf kernel: init_memory_mapping: [mem 0xcac07000-0xcaffffff]
Feb 14 12:11:43 linux-ytaf kernel:  [mem 0xcac07000-0xcadfffff] page 4k
Feb 14 12:11:43 linux-ytaf kernel:  [mem 0xcae00000-0xcaffffff] page 2M
Feb 14 12:11:43 linux-ytaf kernel: init_memory_mapping: [mem 0x100000000-0x1ffffffff]
Feb 14 12:11:43 linux-ytaf kernel:  [mem 0x100000000-0x1ffffffff] page 2M
Feb 14 12:11:43 linux-ytaf kernel: RAMDISK: [mem 0x00457000-0x00ffafff]
Feb 14 12:11:43 linux-ytaf kernel: ACPI: Early table checksum verification disabled
Feb 14 12:11:43 linux-ytaf kernel: ACPI: RSDP 0x00000000CAB84000 000024 (v02 ALASKA)
Feb 14 12:11:43 linux-ytaf kernel: ACPI: XSDT 0x00000000CAB84078 000064 (v01 ALASKA A M I    01072009 AMI  00010013)
Feb 14 12:11:43 linux-ytaf kernel: ACPI: FACP 0x00000000CAB8FC78 0000F4 (v04 ALASKA A M I    01072009 AMI  00010013)
Feb 14 12:11:43 linux-ytaf kernel: ACPI: DSDT 0x00000000CAB84170 00BB02 (v02 ALASKA A M I    00000015 INTL 20051117)
Feb 14 12:11:43 linux-ytaf kernel: ACPI: FACS 0x00000000CABBDF80 000040
Feb 14 12:11:43 linux-ytaf kernel: ACPI: APIC 0x00000000CAB8FD70 000092 (v03 ALASKA A M I    01072009 AMI  00010013)
Feb 14 12:11:43 linux-ytaf kernel: ACPI: MCFG 0x00000000CAB8FE08 00003C (v01 ALASKA A M I    01072009 MSFT 00000097)
Feb 14 12:11:43 linux-ytaf kernel: ACPI: HPET 0x00000000CAB8FE48 000038 (v01 ALASKA A M I    01072009 AMI. 00000005)
Feb 14 12:11:43 linux-ytaf kernel: ACPI: SSDT 0x00000000CAB8FE80 00036D (v01 SataRe SataTabl 00001000 INTL 20091112)
Feb 14 12:11:43 linux-ytaf kernel: ACPI: SSDT 0x00000000CAB901F0 0009AA (v01 PmRef  Cpu0Ist  00003000 INTL 20051117)
Feb 14 12:11:43 linux-ytaf kernel: ACPI: SSDT 0x00000000CAB90BA0 000A92 (v01 PmRef  CpuPm    00003000 INTL 20051117)
Feb 14 12:11:43 linux-ytaf kernel: ACPI: BGRT 0x00000000CAB91690 000038 (v00 ALASKA A M I    01072009 AMI  00010013)
Feb 14 12:11:43 linux-ytaf kernel: ACPI: Local APIC address 0xfee00000
Feb 14 12:11:43 linux-ytaf kernel: No NUMA configuration found
Feb 14 12:11:43 linux-ytaf kernel: Faking a node at [mem 0x0000000000000000-0x000000022f5fffff]
Feb 14 12:11:43 linux-ytaf kernel: NODE_DATA(0) allocated [mem 0x22f5e5000-0x22f5f8fff]
Feb 14 12:11:43 linux-ytaf kernel:  [ffffea0000000000-ffffea0008bfffff] PMD -> [ffff880226c00000-ffff88022ebfffff] on node 0
Feb 14 12:11:43 linux-ytaf kernel: Zone ranges:
Feb 14 12:11:43 linux-ytaf kernel:   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
Feb 14 12:11:43 linux-ytaf kernel:   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
Feb 14 12:11:43 linux-ytaf kernel:   Normal   [mem 0x0000000100000000-0x000000022f5fffff]
Feb 14 12:11:43 linux-ytaf kernel: Movable zone start for each node
Feb 14 12:11:43 linux-ytaf kernel: Early memory node ranges
Feb 14 12:11:43 linux-ytaf kernel:   node   0: [mem 0x0000000000001000-0x000000000009efff]
Feb 14 12:11:43 linux-ytaf kernel:   node   0: [mem 0x0000000000100000-0x000000001fffffff]
Feb 14 12:11:43 linux-ytaf kernel:   node   0: [mem 0x0000000020200000-0x000000003fffffff]
Feb 14 12:11:43 linux-ytaf kernel:   node   0: [mem 0x0000000040200000-0x00000000ca38efff]
Feb 14 12:11:43 linux-ytaf kernel:   node   0: [mem 0x00000000cac07000-0x00000000caffffff]
Feb 14 12:11:43 linux-ytaf kernel:   node   0: [mem 0x0000000100000000-0x000000022f5fffff]
Feb 14 12:11:43 linux-ytaf kernel: Initmem setup node 0 [mem 0x0000000000001000-0x000000022f5fffff]
Feb 14 12:11:43 linux-ytaf kernel: On node 0 totalpages: 2070822
Feb 14 12:11:43 linux-ytaf kernel:   DMA zone: 64 pages used for memmap
Feb 14 12:11:43 linux-ytaf kernel:   DMA zone: 3138 pages reserved
Feb 14 12:11:43 linux-ytaf kernel:   DMA zone: 3998 pages, LIFO batch:0
Feb 14 12:11:43 linux-ytaf kernel:   DMA32 zone: 12879 pages used for memmap
Feb 14 12:11:43 linux-ytaf kernel:   DMA32 zone: 824200 pages, LIFO batch:31
Feb 14 12:11:43 linux-ytaf kernel:   Normal zone: 19416 pages used for memmap
Feb 14 12:11:43 linux-ytaf kernel:   Normal zone: 1242624 pages, LIFO batch:31
Feb 14 12:11:43 linux-ytaf kernel: tboot: non-0 tboot_addr but it is not of type E820_RESERVED
Feb 14 12:11:43 linux-ytaf kernel: ACPI: PM-Timer IO Port: 0x408
Feb 14 12:11:43 linux-ytaf kernel: ACPI: Local APIC address 0xfee00000
Feb 14 12:11:43 linux-ytaf kernel: ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
Feb 14 12:11:43 linux-ytaf kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
Feb 14 12:11:43 linux-ytaf kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Feb 14 12:11:43 linux-ytaf kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Feb 14 12:11:43 linux-ytaf kernel: ACPI: IRQ0 used by override.
Feb 14 12:11:43 linux-ytaf kernel: ACPI: IRQ9 used by override.
Feb 14 12:11:43 linux-ytaf kernel: Using ACPI (MADT) for SMP configuration information
Feb 14 12:11:43 linux-ytaf kernel: ACPI: HPET id: 0x8086a701 base: 0xfed00000
Feb 14 12:11:43 linux-ytaf kernel: smpboot: Allowing 8 CPUs, 0 hotplug CPUs
Feb 14 12:11:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
Feb 14 12:11:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Feb 14 12:11:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000fffff]
Feb 14 12:11:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c826000-0x0c826fff]
Feb 14 12:11:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c835000-0x0c835fff]
Feb 14 12:11:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c836000-0x0c836fff]
Feb 14 12:11:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c846000-0x0c846fff]
Feb 14 12:11:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c847000-0x0c847fff]
Feb 14 12:11:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c856000-0x0c856fff]
Feb 14 12:11:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c857000-0x0c857fff]
Feb 14 12:11:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c85a000-0x0c85afff]
Feb 14 12:11:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x20000000-0x201fffff]
Feb 14 12:11:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x40000000-0x401fffff]
Feb 14 12:11:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xca38f000-0xca5f1fff]
Feb 14 12:11:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xca5f2000-0xca679fff]
Feb 14 12:11:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xca67a000-0xca93efff]
Feb 14 12:11:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xca93f000-0xcab83fff]
Feb 14 12:11:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcab84000-0xcab91fff]
Feb 14 12:11:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcab92000-0xcabbefff]
Feb 14 12:11:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcabbf000-0xcabc3fff]
Feb 14 12:11:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcabc4000-0xcac06fff]
Feb 14 12:11:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcb000000-0xcb7fffff]
Feb 14 12:11:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcb800000-0xcf9fffff]
Feb 14 12:11:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcfa00000-0xf7ffffff]
Feb 14 12:11:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
Feb 14 12:11:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfc000000-0xfebfffff]
Feb 14 12:11:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
Feb 14 12:11:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfec01000-0xfecfffff]
Feb 14 12:11:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed00000-0xfed03fff]
Feb 14 12:11:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed04000-0xfed1bfff]
Feb 14 12:11:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Feb 14 12:11:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed20000-0xfedfffff]
Feb 14 12:11:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
Feb 14 12:11:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfee01000-0xfeffffff]
Feb 14 12:11:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Feb 14 12:11:43 linux-ytaf kernel: e820: [mem 0xcfa00000-0xf7ffffff] available for PCI devices
Feb 14 12:11:43 linux-ytaf kernel: Booting paravirtualized kernel on bare hardware
Feb 14 12:11:43 linux-ytaf kernel: clocksource refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
Feb 14 12:11:43 linux-ytaf kernel: setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:8 nr_node_ids:1
Feb 14 12:11:43 linux-ytaf kernel: PERCPU: Embedded 33 pages/cpu @ffff88022f200000 s97368 r8192 d29608 u262144
Feb 14 12:11:43 linux-ytaf kernel: pcpu-alloc: s97368 r8192 d29608 u262144 alloc=1*2097152
Feb 14 12:11:43 linux-ytaf kernel: pcpu-alloc: [0] 0 1 2 3 4 5 6 7 
Feb 14 12:11:43 linux-ytaf kernel: Built 1 zonelists in Node order, mobility grouping on.  Total pages: 2035325
Feb 14 12:11:43 linux-ytaf kernel: Policy zone: Normal
Feb 14 12:11:43 linux-ytaf kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.1.15-8-default root=UUID=21024970-7a27-4114-8525-d8dd026f23b6 ro resume=/dev/sdb2 splash=silent quiet showopts
Feb 14 12:11:43 linux-ytaf kernel: log_buf_len individual max cpu contribution: 32768 bytes
Feb 14 12:11:43 linux-ytaf kernel: log_buf_len total cpu_extra contributions: 229376 bytes
Feb 14 12:11:43 linux-ytaf kernel: log_buf_len min size: 262144 bytes
Feb 14 12:11:43 linux-ytaf kernel: log_buf_len: 524288 bytes
Feb 14 12:11:43 linux-ytaf kernel: early log buf free: 245492(93%)
Feb 14 12:11:43 linux-ytaf kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
Feb 14 12:11:43 linux-ytaf kernel: xsave: enabled xstate_bv 0x7, cntxt size 0x340 using standard form
Feb 14 12:11:43 linux-ytaf kernel: AGP: Checking aperture...
Feb 14 12:11:43 linux-ytaf kernel: AGP: No AGP bridge found
Feb 14 12:11:43 linux-ytaf kernel: Memory: 7863196K/8283288K available (6547K kernel code, 1084K rwdata, 4848K rodata, 1560K init, 1516K bss, 420092K reserved, 0K cma-reserved)
Feb 14 12:11:43 linux-ytaf kernel: Preemptible hierarchical RCU implementation.
Feb 14 12:11:43 linux-ytaf kernel:         RCU dyntick-idle grace-period acceleration is enabled.
Feb 14 12:11:43 linux-ytaf kernel:         RCU restricting CPUs from NR_CPUS=512 to nr_cpu_ids=8.
Feb 14 12:11:43 linux-ytaf kernel: RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
Feb 14 12:11:43 linux-ytaf kernel: NR_IRQS:33024 nr_irqs:488 16
Feb 14 12:11:43 linux-ytaf kernel:         Offload RCU callbacks from all CPUs
Feb 14 12:11:43 linux-ytaf kernel:         Offload RCU callbacks from CPUs: 0-7.
Feb 14 12:11:43 linux-ytaf kernel: Console: colour dummy device 80x25
Feb 14 12:11:43 linux-ytaf kernel: console [tty0] enabled
Feb 14 12:11:43 linux-ytaf kernel: clocksource hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484882848 ns
Feb 14 12:11:43 linux-ytaf kernel: hpet clockevent registered
Feb 14 12:11:43 linux-ytaf kernel: tsc: Fast TSC calibration using PIT
Feb 14 12:11:43 linux-ytaf kernel: tsc: Detected 3411.116 MHz processor
Feb 14 12:11:43 linux-ytaf kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 6822.23 BogoMIPS (lpj=13644464)
Feb 14 12:11:43 linux-ytaf kernel: pid_max: default: 32768 minimum: 301
Feb 14 12:11:43 linux-ytaf kernel: ACPI: Core revision 20150410
Feb 14 12:11:43 linux-ytaf kernel: ACPI: All ACPI Tables successfully acquired
Feb 14 12:11:43 linux-ytaf kernel: Security Framework initialized
Feb 14 12:11:43 linux-ytaf kernel: AppArmor: AppArmor initialized
Feb 14 12:11:43 linux-ytaf kernel: Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
Feb 14 12:11:43 linux-ytaf kernel: Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
Feb 14 12:11:43 linux-ytaf kernel: Mount-cache hash table entries: 16384 (order: 5, 131072 bytes)
Feb 14 12:11:43 linux-ytaf kernel: Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes)
Feb 14 12:11:43 linux-ytaf kernel: Initializing cgroup subsys blkio
Feb 14 12:11:43 linux-ytaf kernel: Initializing cgroup subsys memory
Feb 14 12:11:43 linux-ytaf kernel: Initializing cgroup subsys devices
Feb 14 12:11:43 linux-ytaf kernel: Initializing cgroup subsys freezer
Feb 14 12:11:43 linux-ytaf kernel: Initializing cgroup subsys net_cls
Feb 14 12:11:43 linux-ytaf kernel: Initializing cgroup subsys perf_event
Feb 14 12:11:43 linux-ytaf kernel: Initializing cgroup subsys net_prio
Feb 14 12:11:43 linux-ytaf kernel: Initializing cgroup subsys hugetlb
Feb 14 12:11:43 linux-ytaf kernel: CPU: Physical Processor ID: 0
Feb 14 12:11:43 linux-ytaf kernel: CPU: Processor Core ID: 0
Feb 14 12:11:43 linux-ytaf kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Feb 14 12:11:43 linux-ytaf kernel: ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Feb 14 12:11:43 linux-ytaf kernel: mce: CPU supports 9 MCE banks
Feb 14 12:11:43 linux-ytaf kernel: CPU0: Thermal monitoring enabled (TM1)
Feb 14 12:11:43 linux-ytaf kernel: process: using mwait in idle threads
Feb 14 12:11:43 linux-ytaf kernel: Last level iTLB entries: 4KB 512, 2MB 8, 4MB 8
Feb 14 12:11:43 linux-ytaf kernel: Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32, 1GB 0
Feb 14 12:11:43 linux-ytaf kernel: Freeing SMP alternatives memory: 24K (ffffffff82097000 - ffffffff8209d000)
Feb 14 12:11:43 linux-ytaf kernel: ftrace: allocating 25000 entries in 98 pages
Feb 14 12:11:43 linux-ytaf kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Feb 14 12:11:43 linux-ytaf kernel: TSC deadline timer enabled
Feb 14 12:11:43 linux-ytaf kernel: smpboot: CPU0: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz (fam: 06, model: 2a, stepping: 07)
Feb 14 12:11:43 linux-ytaf kernel: Performance Events: PEBS fmt1+, 16-deep LBR, SandyBridge events, full-width counters, Intel PMU driver.
Feb 14 12:11:43 linux-ytaf kernel: ... version:                3
Feb 14 12:11:43 linux-ytaf kernel: ... bit width:              48
Feb 14 12:11:43 linux-ytaf kernel: ... generic registers:      4
Feb 14 12:11:43 linux-ytaf kernel: ... value mask:             0000ffffffffffff
Feb 14 12:11:43 linux-ytaf kernel: ... max period:             0000ffffffffffff
Feb 14 12:11:43 linux-ytaf kernel: ... fixed-purpose events:   3
Feb 14 12:11:43 linux-ytaf kernel: ... event mask:             000000070000000f
Feb 14 12:11:43 linux-ytaf kernel: x86: Booting SMP configuration:
Feb 14 12:11:43 linux-ytaf kernel: .... node  #0, CPUs:      #1
Feb 14 12:11:43 linux-ytaf kernel: microcode: CPU1 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 12:11:43 linux-ytaf kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Feb 14 12:11:43 linux-ytaf kernel:  #2
Feb 14 12:11:43 linux-ytaf kernel: microcode: CPU2 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 12:11:43 linux-ytaf kernel:  #3
Feb 14 12:11:43 linux-ytaf kernel: microcode: CPU3 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 12:11:43 linux-ytaf kernel:  #4 #5 #6 #7
Feb 14 12:11:43 linux-ytaf kernel: x86: Booted up 1 node, 8 CPUs
Feb 14 12:11:43 linux-ytaf kernel: smpboot: Total of 8 processors activated (54577.85 BogoMIPS)
Feb 14 12:11:43 linux-ytaf kernel: devtmpfs: initialized
Feb 14 12:11:43 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xca5f2000-0xca679fff] (557056 bytes)
Feb 14 12:11:43 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xca93f000-0xcab83fff] (2379776 bytes)
Feb 14 12:11:43 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xcab92000-0xcabbefff] (184320 bytes)
Feb 14 12:11:43 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xcabc4000-0xcac06fff] (274432 bytes)
Feb 14 12:11:43 linux-ytaf kernel: clocksource jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
Feb 14 12:11:43 linux-ytaf kernel: pinctrl core: initialized pinctrl subsystem
Feb 14 12:11:43 linux-ytaf kernel: RTC time: 12:11:40, date: 02/14/16
Feb 14 12:11:43 linux-ytaf kernel: NET: Registered protocol family 16
Feb 14 12:11:43 linux-ytaf kernel: cpuidle: using governor ladder
Feb 14 12:11:43 linux-ytaf kernel: cpuidle: using governor menu
Feb 14 12:11:43 linux-ytaf kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
Feb 14 12:11:43 linux-ytaf kernel: ACPI: bus type PCI registered
Feb 14 12:11:43 linux-ytaf kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Feb 14 12:11:43 linux-ytaf kernel: PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
Feb 14 12:11:43 linux-ytaf kernel: PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
Feb 14 12:11:43 linux-ytaf kernel: PCI: Using configuration type 1 for base access
Feb 14 12:11:43 linux-ytaf kernel: perf_event_intel: PMU erratum BJ122, BV98, HSD29 worked around, HT is on
Feb 14 12:11:43 linux-ytaf kernel: ACPI: Added _OSI(Module Device)
Feb 14 12:11:43 linux-ytaf kernel: ACPI: Added _OSI(Processor Device)
Feb 14 12:11:43 linux-ytaf kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
Feb 14 12:11:43 linux-ytaf kernel: ACPI: Added _OSI(Processor Aggregator Device)
Feb 14 12:11:43 linux-ytaf kernel: ACPI: Executed 1 blocks of module-level executable AML code
Feb 14 12:11:43 linux-ytaf kernel: ACPI: Dynamic OEM Table Load:
Feb 14 12:11:43 linux-ytaf kernel: ACPI: SSDT 0xFFFF8802257C9000 00083B (v01 PmRef  Cpu0Cst  00003001 INTL 20051117)
Feb 14 12:11:43 linux-ytaf kernel: ACPI: Dynamic OEM Table Load:
Feb 14 12:11:43 linux-ytaf kernel: ACPI: SSDT 0xFFFF8802257C3400 000303 (v01 PmRef  ApIst    00003000 INTL 20051117)
Feb 14 12:11:43 linux-ytaf kernel: ACPI: Dynamic OEM Table Load:
Feb 14 12:11:43 linux-ytaf kernel: ACPI: SSDT 0xFFFF880225776600 000119 (v01 PmRef  ApCst    00003000 INTL 20051117)
Feb 14 12:11:43 linux-ytaf kernel: ACPI : EC: EC started
Feb 14 12:11:43 linux-ytaf kernel: ACPI: Interpreter enabled
Feb 14 12:11:43 linux-ytaf kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20150410/hwxface-580)
Feb 14 12:11:43 linux-ytaf kernel: ACPI: (supports S0 S1 S3 S4 S5)
Feb 14 12:11:43 linux-ytaf kernel: ACPI: Using IOAPIC for interrupt routing
Feb 14 12:11:43 linux-ytaf kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Feb 14 12:11:43 linux-ytaf kernel: ACPI: Power Resource [FN00] (off)
Feb 14 12:11:43 linux-ytaf kernel: ACPI: Power Resource [FN01] (off)
Feb 14 12:11:43 linux-ytaf kernel: ACPI: Power Resource [FN02] (off)
Feb 14 12:11:43 linux-ytaf kernel: ACPI: Power Resource [FN03] (off)
Feb 14 12:11:43 linux-ytaf kernel: ACPI: Power Resource [FN04] (off)
Feb 14 12:11:43 linux-ytaf kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
Feb 14 12:11:43 linux-ytaf kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Feb 14 12:11:43 linux-ytaf kernel: \_SB_.PCI0:_OSC invalid UUID
Feb 14 12:11:43 linux-ytaf kernel: _OSC request data:1 1f 0 
Feb 14 12:11:43 linux-ytaf kernel: acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
Feb 14 12:11:43 linux-ytaf kernel: PCI host bridge to bus 0000:00
Feb 14 12:11:43 linux-ytaf kernel: pci_bus 0000:00: root bus resource [bus 00-3e]
Feb 14 12:11:43 linux-ytaf kernel: pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
Feb 14 12:11:43 linux-ytaf kernel: pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
Feb 14 12:11:43 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
Feb 14 12:11:43 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff window]
Feb 14 12:11:43 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff window]
Feb 14 12:11:43 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff window]
Feb 14 12:11:43 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0xcfa00000-0xfeafffff window]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:00.0: [8086:0100] type 00 class 0x060000
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:01.0: [8086:0101] type 01 class 0x060400
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:01.0: System wakeup disabled by ACPI
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:01.1: [8086:0105] type 01 class 0x060400
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:01.1: PME# supported from D0 D3hot D3cold
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:01.1: System wakeup disabled by ACPI
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:02.0: [8086:0122] type 00 class 0x038000
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:02.0: reg 0x10: [mem 0xf7400000-0xf77fffff 64bit]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:02.0: reg 0x18: [mem 0xd0000000-0xdfffffff 64bit pref]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:02.0: reg 0x20: [io  0xf000-0xf03f]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:16.0: [8086:1c3a] type 00 class 0x078000
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:16.0: reg 0x10: [mem 0xf7b2c000-0xf7b2c00f 64bit]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:19.0: [8086:1503] type 00 class 0x020000
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:19.0: reg 0x10: [mem 0xf7b00000-0xf7b1ffff]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:19.0: reg 0x14: [mem 0xf7b29000-0xf7b29fff]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:19.0: reg 0x18: [io  0xf080-0xf09f]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:19.0: PME# supported from D0 D3hot D3cold
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:19.0: System wakeup disabled by ACPI
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1a.0: [8086:1c2d] type 00 class 0x0c0320
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1a.0: reg 0x10: [mem 0xf7b28000-0xf7b283ff]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1a.0: System wakeup disabled by ACPI
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1b.0: [8086:1c20] type 00 class 0x040300
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1b.0: reg 0x10: [mem 0xf7b20000-0xf7b23fff 64bit]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1b.0: System wakeup disabled by ACPI
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.0: [8086:1c10] type 01 class 0x060400
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.0: System wakeup disabled by ACPI
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.4: [8086:1c18] type 01 class 0x060400
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.4: System wakeup disabled by ACPI
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.5: [8086:1c1a] type 01 class 0x060400
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.5: System wakeup disabled by ACPI
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.6: [8086:1c1c] type 01 class 0x060400
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.6: PME# supported from D0 D3hot D3cold
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.6: System wakeup disabled by ACPI
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1d.0: [8086:1c26] type 00 class 0x0c0320
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1d.0: reg 0x10: [mem 0xf7b27000-0xf7b273ff]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1d.0: System wakeup disabled by ACPI
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1f.0: [8086:1c44] type 00 class 0x060100
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1f.2: [8086:1c02] type 00 class 0x010601
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x10: [io  0xf0d0-0xf0d7]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x14: [io  0xf0c0-0xf0c3]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x18: [io  0xf0b0-0xf0b7]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x1c: [io  0xf0a0-0xf0a3]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x20: [io  0xf060-0xf07f]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x24: [mem 0xf7b26000-0xf7b267ff]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1f.2: PME# supported from D3hot
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1f.3: [8086:1c22] type 00 class 0x0c0500
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1f.3: reg 0x10: [mem 0xf7b25000-0xf7b250ff 64bit]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1f.3: reg 0x20: [io  0x0580-0x059f]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:02:00.0: [10de:1183] type 00 class 0x030000
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:02:00.0: reg 0x10: [mem 0xf6000000-0xf6ffffff]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:02:00.0: reg 0x14: [mem 0xe0000000-0xe7ffffff 64bit pref]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:02:00.0: reg 0x1c: [mem 0xe8000000-0xe9ffffff 64bit pref]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:02:00.0: reg 0x24: [io  0xe000-0xe07f]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:02:00.0: reg 0x30: [mem 0xf7000000-0xf707ffff pref]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:02:00.1: [10de:0e0a] type 00 class 0x040300
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:02:00.1: reg 0x10: [mem 0xf7080000-0xf7083fff]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:01.1: PCI bridge to [bus 02]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [io  0xe000-0xefff]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xf6000000-0xf70fffff]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xe0000000-0xe9ffffff 64bit pref]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.0: PCI bridge to [bus 03]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:04:00.0: [1b21:1042] type 00 class 0x0c0330
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:04:00.0: reg 0x10: [mem 0xf7a00000-0xf7a07fff 64bit]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:04:00.0: PME# supported from D3hot D3cold
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:04:00.0: System wakeup disabled by ACPI
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.4: PCI bridge to [bus 04]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.4:   bridge window [mem 0xf7a00000-0xf7afffff]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:05:00.0: [1b21:1042] type 00 class 0x0c0330
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:05:00.0: reg 0x10: [mem 0xf7900000-0xf7907fff 64bit]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:05:00.0: PME# supported from D3hot D3cold
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:05:00.0: System wakeup disabled by ACPI
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.5: PCI bridge to [bus 05]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.5:   bridge window [mem 0xf7900000-0xf79fffff]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:06:00.0: [197b:2362] type 00 class 0x010185
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:06:00.0: reg 0x10: [io  0xd040-0xd047]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:06:00.0: reg 0x14: [io  0xd030-0xd033]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:06:00.0: reg 0x18: [io  0xd020-0xd027]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:06:00.0: reg 0x1c: [io  0xd010-0xd013]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:06:00.0: reg 0x20: [io  0xd000-0xd00f]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:06:00.0: reg 0x24: [mem 0xf7810000-0xf78101ff]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:06:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:06:00.0: PME# supported from D3hot
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:06:00.0: System wakeup disabled by ACPI
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.6: PCI bridge to [bus 06]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [io  0xd000-0xdfff]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [mem 0xf7800000-0xf78fffff]
Feb 14 12:11:43 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15)
Feb 14 12:11:43 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *10 11 12 14 15)
Feb 14 12:11:43 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Feb 14 12:11:43 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs *3 4 5 6 10 11 12 14 15)
Feb 14 12:11:43 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 *4 5 6 10 11 12 14 15)
Feb 14 12:11:43 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
Feb 14 12:11:43 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 *11 12 14 15)
Feb 14 12:11:43 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 *10 11 12 14 15)
Feb 14 12:11:43 linux-ytaf kernel: ACPI: Enabled 6 GPEs in block 00 to 3F
Feb 14 12:11:43 linux-ytaf kernel: ACPI : EC: GPE = 0x18, I/O: command/status = 0x66, data = 0x62
Feb 14 12:11:43 linux-ytaf kernel: vgaarb: setting as boot device: PCI:0000:02:00.0
Feb 14 12:11:43 linux-ytaf kernel: vgaarb: device added: PCI:0000:02:00.0,decodes=io+mem,owns=io+mem,locks=none
Feb 14 12:11:43 linux-ytaf kernel: vgaarb: loaded
Feb 14 12:11:43 linux-ytaf kernel: vgaarb: bridge control possible 0000:02:00.0
Feb 14 12:11:43 linux-ytaf kernel: SCSI subsystem initialized
Feb 14 12:11:43 linux-ytaf kernel: libata version 3.00 loaded.
Feb 14 12:11:43 linux-ytaf kernel: PCI: Using ACPI for IRQ routing
Feb 14 12:11:43 linux-ytaf kernel: PCI: pci_cache_line_size set to 64 bytes
Feb 14 12:11:43 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0009f000-0x0009ffff]
Feb 14 12:11:43 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c826018-0x0fffffff]
Feb 14 12:11:43 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c836018-0x0fffffff]
Feb 14 12:11:43 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c847018-0x0fffffff]
Feb 14 12:11:43 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c857018-0x0fffffff]
Feb 14 12:11:43 linux-ytaf kernel: e820: reserve RAM buffer [mem 0xca38f000-0xcbffffff]
Feb 14 12:11:43 linux-ytaf kernel: e820: reserve RAM buffer [mem 0xcb000000-0xcbffffff]
Feb 14 12:11:43 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x22f600000-0x22fffffff]
Feb 14 12:11:43 linux-ytaf kernel: NetLabel: Initializing
Feb 14 12:11:43 linux-ytaf kernel: NetLabel:  domain hash size = 128
Feb 14 12:11:43 linux-ytaf kernel: NetLabel:  protocols = UNLABELED CIPSOv4
Feb 14 12:11:43 linux-ytaf kernel: NetLabel:  unlabeled traffic allowed by default
Feb 14 12:11:43 linux-ytaf kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Feb 14 12:11:43 linux-ytaf kernel: hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Feb 14 12:11:43 linux-ytaf kernel: Switched to clocksource hpet
Feb 14 12:11:43 linux-ytaf kernel: AppArmor: AppArmor Filesystem Enabled
Feb 14 12:11:43 linux-ytaf kernel: pnp: PnP ACPI init
Feb 14 12:11:43 linux-ytaf kernel: system 00:00: [mem 0xfed40000-0xfed44fff] has been reserved
Feb 14 12:11:43 linux-ytaf kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
Feb 14 12:11:43 linux-ytaf kernel: system 00:01: [io  0x0680-0x069f] has been reserved
Feb 14 12:11:43 linux-ytaf kernel: system 00:01: [io  0x0200-0x020f] has been reserved
Feb 14 12:11:43 linux-ytaf kernel: system 00:01: [io  0xffff] has been reserved
Feb 14 12:11:43 linux-ytaf kernel: system 00:01: [io  0xffff] has been reserved
Feb 14 12:11:43 linux-ytaf kernel: system 00:01: [io  0x0400-0x0453] could not be reserved
Feb 14 12:11:43 linux-ytaf kernel: system 00:01: [io  0x0458-0x047f] has been reserved
Feb 14 12:11:43 linux-ytaf kernel: system 00:01: [io  0x0500-0x057f] has been reserved
Feb 14 12:11:43 linux-ytaf kernel: system 00:01: [io  0x164e-0x164f] has been reserved
Feb 14 12:11:43 linux-ytaf kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 12:11:43 linux-ytaf kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Feb 14 12:11:43 linux-ytaf kernel: system 00:03: [io  0x0454-0x0457] has been reserved
Feb 14 12:11:43 linux-ytaf kernel: system 00:03: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
Feb 14 12:11:43 linux-ytaf kernel: system 00:04: [io  0x0290-0x029f] has been reserved
Feb 14 12:11:43 linux-ytaf kernel: system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 12:11:43 linux-ytaf kernel: system 00:05: [io  0x04d0-0x04d1] has been reserved
Feb 14 12:11:43 linux-ytaf kernel: system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 12:11:43 linux-ytaf kernel: system 00:06: [mem 0xfed1c000-0xfed1ffff] has been reserved
Feb 14 12:11:43 linux-ytaf kernel: system 00:06: [mem 0xfed10000-0xfed17fff] has been reserved
Feb 14 12:11:43 linux-ytaf kernel: system 00:06: [mem 0xfed18000-0xfed18fff] has been reserved
Feb 14 12:11:43 linux-ytaf kernel: system 00:06: [mem 0xfed19000-0xfed19fff] has been reserved
Feb 14 12:11:43 linux-ytaf kernel: system 00:06: [mem 0xf8000000-0xfbffffff] has been reserved
Feb 14 12:11:43 linux-ytaf kernel: system 00:06: [mem 0xfed20000-0xfed3ffff] has been reserved
Feb 14 12:11:43 linux-ytaf kernel: system 00:06: [mem 0xfed90000-0xfed93fff] has been reserved
Feb 14 12:11:43 linux-ytaf kernel: system 00:06: [mem 0xfed45000-0xfed8ffff] has been reserved
Feb 14 12:11:43 linux-ytaf kernel: system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Feb 14 12:11:43 linux-ytaf kernel: system 00:06: [mem 0xfee00000-0xfeefffff] could not be reserved
Feb 14 12:11:43 linux-ytaf kernel: system 00:06: [mem 0xcfa00000-0xcfa00fff] has been reserved
Feb 14 12:11:43 linux-ytaf kernel: system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 12:11:43 linux-ytaf kernel: system 00:07: [mem 0x20000000-0x201fffff] has been reserved
Feb 14 12:11:43 linux-ytaf kernel: system 00:07: [mem 0x40000000-0x401fffff] has been reserved
Feb 14 12:11:43 linux-ytaf kernel: system 00:07: Plug and Play ACPI device, IDs PNP0c01 (active)
Feb 14 12:11:43 linux-ytaf kernel: pnp: PnP ACPI: found 8 devices
Feb 14 12:11:43 linux-ytaf kernel: clocksource acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.0: bridge window [io  0x1000-0x0fff] to [bus 03] add_size 1000
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 03] add_size 200000 add_align 100000
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff] to [bus 03] add_size 200000 add_align 100000
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.0: res[14]=[mem 0x00100000-0x000fffff] res_to_dev_res add_size 200000 min_align 100000
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.0: res[14]=[mem 0x00100000-0x002fffff] res_to_dev_res add_size 200000 min_align 100000
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x000fffff 64bit pref] res_to_dev_res add_size 200000 min_align 100000
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x002fffff 64bit pref] res_to_dev_res add_size 200000 min_align 100000
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.0: res[13]=[io  0x1000-0x0fff] res_to_dev_res add_size 1000 min_align 1000
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.0: res[13]=[io  0x1000-0x1fff] res_to_dev_res add_size 1000 min_align 1000
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.0: BAR 14: assigned [mem 0xcfb00000-0xcfcfffff]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.0: BAR 15: assigned [mem 0xcfd00000-0xcfefffff 64bit pref]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.0: BAR 13: assigned [io  0x2000-0x2fff]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:01.1: PCI bridge to [bus 02]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [io  0xe000-0xefff]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xf6000000-0xf70fffff]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xe0000000-0xe9ffffff 64bit pref]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.0: PCI bridge to [bus 03]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.0:   bridge window [io  0x2000-0x2fff]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.0:   bridge window [mem 0xcfb00000-0xcfcfffff]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.0:   bridge window [mem 0xcfd00000-0xcfefffff 64bit pref]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.4: PCI bridge to [bus 04]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.4:   bridge window [mem 0xf7a00000-0xf7afffff]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.5: PCI bridge to [bus 05]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.5:   bridge window [mem 0xf7900000-0xf79fffff]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:06:00.0: BAR 6: assigned [mem 0xf7800000-0xf780ffff pref]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.6: PCI bridge to [bus 06]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [io  0xd000-0xdfff]
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [mem 0xf7800000-0xf78fffff]
Feb 14 12:11:43 linux-ytaf kernel: pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
Feb 14 12:11:43 linux-ytaf kernel: pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
Feb 14 12:11:43 linux-ytaf kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
Feb 14 12:11:43 linux-ytaf kernel: pci_bus 0000:00: resource 7 [mem 0x000d4000-0x000d7fff window]
Feb 14 12:11:43 linux-ytaf kernel: pci_bus 0000:00: resource 8 [mem 0x000d8000-0x000dbfff window]
Feb 14 12:11:43 linux-ytaf kernel: pci_bus 0000:00: resource 9 [mem 0x000dc000-0x000dffff window]
Feb 14 12:11:43 linux-ytaf kernel: pci_bus 0000:00: resource 10 [mem 0xcfa00000-0xfeafffff window]
Feb 14 12:11:43 linux-ytaf kernel: pci_bus 0000:02: resource 0 [io  0xe000-0xefff]
Feb 14 12:11:43 linux-ytaf kernel: pci_bus 0000:02: resource 1 [mem 0xf6000000-0xf70fffff]
Feb 14 12:11:43 linux-ytaf kernel: pci_bus 0000:02: resource 2 [mem 0xe0000000-0xe9ffffff 64bit pref]
Feb 14 12:11:43 linux-ytaf kernel: pci_bus 0000:03: resource 0 [io  0x2000-0x2fff]
Feb 14 12:11:43 linux-ytaf kernel: pci_bus 0000:03: resource 1 [mem 0xcfb00000-0xcfcfffff]
Feb 14 12:11:43 linux-ytaf kernel: pci_bus 0000:03: resource 2 [mem 0xcfd00000-0xcfefffff 64bit pref]
Feb 14 12:11:43 linux-ytaf kernel: pci_bus 0000:04: resource 1 [mem 0xf7a00000-0xf7afffff]
Feb 14 12:11:43 linux-ytaf kernel: pci_bus 0000:05: resource 1 [mem 0xf7900000-0xf79fffff]
Feb 14 12:11:43 linux-ytaf kernel: pci_bus 0000:06: resource 0 [io  0xd000-0xdfff]
Feb 14 12:11:43 linux-ytaf kernel: pci_bus 0000:06: resource 1 [mem 0xf7800000-0xf78fffff]
Feb 14 12:11:43 linux-ytaf kernel: NET: Registered protocol family 2
Feb 14 12:11:43 linux-ytaf kernel: TCP established hash table entries: 65536 (order: 7, 524288 bytes)
Feb 14 12:11:43 linux-ytaf kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Feb 14 12:11:43 linux-ytaf kernel: TCP: Hash tables configured (established 65536 bind 65536)
Feb 14 12:11:43 linux-ytaf kernel: UDP hash table entries: 4096 (order: 5, 131072 bytes)
Feb 14 12:11:43 linux-ytaf kernel: UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
Feb 14 12:11:43 linux-ytaf kernel: NET: Registered protocol family 1
Feb 14 12:11:43 linux-ytaf kernel: pci 0000:02:00.0: Video device with shadowed ROM
Feb 14 12:11:43 linux-ytaf kernel: PCI: CLS 64 bytes, default 64
Feb 14 12:11:43 linux-ytaf kernel: Unpacking initramfs...
Feb 14 12:11:43 linux-ytaf kernel: Freeing initrd memory: 11920K (ffff880000457000 - ffff880000ffb000)
Feb 14 12:11:43 linux-ytaf kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Feb 14 12:11:43 linux-ytaf kernel: software IO TLB [mem 0xc638f000-0xca38f000] (64MB) mapped at [ffff8800c638f000-ffff8800ca38efff]
Feb 14 12:11:43 linux-ytaf kernel: RAPL PMU detected, API unit is 2^-32 Joules, 3 fixed counters 163840 ms ovfl timer
Feb 14 12:11:43 linux-ytaf kernel: hw unit of domain pp0-core 2^-16 Joules
Feb 14 12:11:43 linux-ytaf kernel: hw unit of domain package 2^-16 Joules
Feb 14 12:11:43 linux-ytaf kernel: hw unit of domain pp1-gpu 2^-16 Joules
Feb 14 12:11:43 linux-ytaf kernel: microcode: CPU0 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 12:11:43 linux-ytaf kernel: microcode: CPU1 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 12:11:43 linux-ytaf kernel: microcode: CPU2 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 12:11:43 linux-ytaf kernel: microcode: CPU3 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 12:11:43 linux-ytaf kernel: microcode: CPU4 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 12:11:43 linux-ytaf kernel: microcode: CPU5 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 12:11:43 linux-ytaf kernel: microcode: CPU6 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 12:11:43 linux-ytaf kernel: microcode: CPU7 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 12:11:43 linux-ytaf kernel: microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Feb 14 12:11:43 linux-ytaf kernel: Scanning for low memory corruption every 60 seconds
Feb 14 12:11:43 linux-ytaf kernel: futex hash table entries: 2048 (order: 5, 131072 bytes)
Feb 14 12:11:43 linux-ytaf kernel: audit: initializing netlink subsys (disabled)
Feb 14 12:11:43 linux-ytaf kernel: audit: type=2000 audit(1455451900.284:1): initialized
Feb 14 12:11:43 linux-ytaf kernel: HugeTLB registered 2 MB page size, pre-allocated 0 pages
Feb 14 12:11:43 linux-ytaf kernel: zpool: loaded
Feb 14 12:11:43 linux-ytaf kernel: zbud: loaded
Feb 14 12:11:43 linux-ytaf kernel: VFS: Disk quotas dquot_6.6.0
Feb 14 12:11:43 linux-ytaf kernel: VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Feb 14 12:11:43 linux-ytaf kernel: Key type big_key registered
Feb 14 12:11:43 linux-ytaf kernel: Key type asymmetric registered
Feb 14 12:11:43 linux-ytaf kernel: Asymmetric key parser 'x509' registered
Feb 14 12:11:43 linux-ytaf kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Feb 14 12:11:43 linux-ytaf kernel: io scheduler noop registered
Feb 14 12:11:43 linux-ytaf kernel: io scheduler deadline registered
Feb 14 12:11:43 linux-ytaf kernel: io scheduler cfq registered (default)
Feb 14 12:11:43 linux-ytaf kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Feb 14 12:11:43 linux-ytaf kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Feb 14 12:11:43 linux-ytaf kernel: efifb: probing for efifb
Feb 14 12:11:43 linux-ytaf kernel: efifb: framebuffer at 0xe9000000, mapped to 0xffffc90001000000, using 1876k, total 1875k
Feb 14 12:11:43 linux-ytaf kernel: efifb: mode is 800x600x32, linelength=3200, pages=1
Feb 14 12:11:43 linux-ytaf kernel: efifb: scrolling: redraw
Feb 14 12:11:43 linux-ytaf kernel: efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Feb 14 12:11:43 linux-ytaf kernel: Console: switching to colour frame buffer device 100x37
Feb 14 12:11:43 linux-ytaf kernel: fb0: EFI VGA frame buffer device
Feb 14 12:11:43 linux-ytaf kernel: intel_idle: MWAIT substates: 0x1120
Feb 14 12:11:43 linux-ytaf kernel: intel_idle: v0.4 model 0x2A
Feb 14 12:11:43 linux-ytaf kernel: intel_idle: lapic_timer_reliable_states 0xffffffff
Feb 14 12:11:43 linux-ytaf kernel: GHES: HEST is not enabled!
Feb 14 12:11:43 linux-ytaf kernel: Serial: 8250/16550 driver, 32 ports, IRQ sharing disabled
Feb 14 12:11:43 linux-ytaf kernel: Non-volatile memory driver v1.3
Feb 14 12:11:43 linux-ytaf kernel: Linux agpgart interface v0.103
Feb 14 12:11:43 linux-ytaf kernel: ahci 0000:00:1f.2: version 3.0
Feb 14 12:11:43 linux-ytaf kernel: ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x7 impl SATA mode
Feb 14 12:11:43 linux-ytaf kernel: ahci 0000:00:1f.2: flags: 64bit ncq led clo pio slum part ems apst 
Feb 14 12:11:43 linux-ytaf kernel: scsi host0: ahci
Feb 14 12:11:43 linux-ytaf kernel: scsi host1: ahci
Feb 14 12:11:43 linux-ytaf kernel: scsi host2: ahci
Feb 14 12:11:43 linux-ytaf kernel: scsi host3: ahci
Feb 14 12:11:43 linux-ytaf kernel: scsi host4: ahci
Feb 14 12:11:43 linux-ytaf kernel: scsi host5: ahci
Feb 14 12:11:43 linux-ytaf kernel: ata1: SATA max UDMA/133 abar m2048@0xf7b26000 port 0xf7b26100 irq 26
Feb 14 12:11:43 linux-ytaf kernel: ata2: SATA max UDMA/133 abar m2048@0xf7b26000 port 0xf7b26180 irq 26
Feb 14 12:11:43 linux-ytaf kernel: ata3: SATA max UDMA/133 abar m2048@0xf7b26000 port 0xf7b26200 irq 26
Feb 14 12:11:43 linux-ytaf kernel: ata4: DUMMY
Feb 14 12:11:43 linux-ytaf kernel: ata5: DUMMY
Feb 14 12:11:43 linux-ytaf kernel: ata6: DUMMY
Feb 14 12:11:43 linux-ytaf kernel: ahci 0000:06:00.0: AHCI 0001.0100 32 slots 2 ports 3 Gbps 0x3 impl SATA mode
Feb 14 12:11:43 linux-ytaf kernel: ahci 0000:06:00.0: flags: 64bit ncq pm led clo pmp pio slum part 
Feb 14 12:11:43 linux-ytaf kernel: scsi host6: ahci
Feb 14 12:11:43 linux-ytaf kernel: scsi host7: ahci
Feb 14 12:11:43 linux-ytaf kernel: ata7: SATA max UDMA/133 abar m512@0xf7810000 port 0xf7810100 irq 18
Feb 14 12:11:43 linux-ytaf kernel: ata8: SATA max UDMA/133 abar m512@0xf7810000 port 0xf7810180 irq 18
Feb 14 12:11:43 linux-ytaf kernel: i8042: PNP: No PS/2 controller found. Probing ports directly.
Feb 14 12:11:43 linux-ytaf kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Feb 14 12:11:43 linux-ytaf kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Feb 14 12:11:43 linux-ytaf kernel: mousedev: PS/2 mouse device common for all mice
Feb 14 12:11:43 linux-ytaf kernel: rtc_cmos 00:02: RTC can wake from S4
Feb 14 12:11:43 linux-ytaf kernel: rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Feb 14 12:11:43 linux-ytaf kernel: rtc_cmos 00:02: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
Feb 14 12:11:43 linux-ytaf kernel: Intel P-state driver initializing.
Feb 14 12:11:43 linux-ytaf kernel: ledtrig-cpu: registered to indicate activity on CPUs
Feb 14 12:11:43 linux-ytaf kernel: EFI Variables Facility v0.08 2004-May-17
Feb 14 12:11:43 linux-ytaf kernel: hidraw: raw HID events driver (C) Jiri Kosina
Feb 14 12:11:43 linux-ytaf kernel: NET: Registered protocol family 10
Feb 14 12:11:43 linux-ytaf kernel: registered taskstats version 1
Feb 14 12:11:43 linux-ytaf kernel: Key type encrypted registered
Feb 14 12:11:43 linux-ytaf kernel: AppArmor: AppArmor sha1 policy hashing enabled
Feb 14 12:11:43 linux-ytaf kernel:   Magic number: 4:913:177
Feb 14 12:11:43 linux-ytaf kernel: acpi device:0d: hash matches
Feb 14 12:11:43 linux-ytaf kernel: rtc_cmos 00:02: setting system clock to 2016-02-14 12:11:41 UTC (1455451901)
Feb 14 12:11:43 linux-ytaf kernel: PM: Checking hibernation image partition /dev/sdb2
Feb 14 12:11:43 linux-ytaf kernel: ata8: SATA link down (SStatus 0 SControl 300)
Feb 14 12:11:43 linux-ytaf kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Feb 14 12:11:43 linux-ytaf kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 14 12:11:43 linux-ytaf kernel: ata7: SATA link down (SStatus 0 SControl 300)
Feb 14 12:11:43 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 12:11:43 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff8802268b7dd8), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 12:11:43 linux-ytaf kernel: ata2.00: ATA-8: TOSHIBA HDWD110, MS2OA8J0, max UDMA/133
Feb 14 12:11:43 linux-ytaf kernel: ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Feb 14 12:11:43 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 12:11:43 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff8802268b7d60), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 12:11:43 linux-ytaf kernel: ata3.00: ATAPI: TSSTcorp CDDVDW SH-S223C, SB05, max UDMA/66
Feb 14 12:11:43 linux-ytaf kernel: ata3.00: applying bridge limits
Feb 14 12:11:43 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 12:11:43 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff8802268b7dd8), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 12:11:43 linux-ytaf kernel: ata2.00: configured for UDMA/133
Feb 14 12:11:43 linux-ytaf kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 14 12:11:43 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 12:11:43 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff8802268b7e50), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 12:11:43 linux-ytaf kernel: ata1.00: ATA-9: SAMSUNG SSD 830 Series, CXM03B1Q, max UDMA/133
Feb 14 12:11:43 linux-ytaf kernel: ata1.00: 500118192 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Feb 14 12:11:43 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 12:11:43 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff8802268b7e50), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 12:11:43 linux-ytaf kernel: ata1.00: configured for UDMA/133
Feb 14 12:11:43 linux-ytaf kernel: scsi 0:0:0:0: Direct-Access     ATA      SAMSUNG SSD 830  3B1Q PQ: 0 ANSI: 5
Feb 14 12:11:43 linux-ytaf kernel: sd 0:0:0:0: [sda] 500118192 512-byte logical blocks: (256 GB/238 GiB)
Feb 14 12:11:43 linux-ytaf kernel: scsi 1:0:0:0: Direct-Access     ATA      TOSHIBA HDWD110  A8J0 PQ: 0 ANSI: 5
Feb 14 12:11:43 linux-ytaf kernel: sd 0:0:0:0: [sda] Write Protect is off
Feb 14 12:11:43 linux-ytaf kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 14 12:11:43 linux-ytaf kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 14 12:11:43 linux-ytaf kernel: sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
Feb 14 12:11:43 linux-ytaf kernel: sd 1:0:0:0: [sdb] 4096-byte physical blocks
Feb 14 12:11:43 linux-ytaf kernel: sd 1:0:0:0: [sdb] Write Protect is off
Feb 14 12:11:43 linux-ytaf kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Feb 14 12:11:43 linux-ytaf kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 14 12:11:43 linux-ytaf kernel:  sda: sda1 sda2 sda3 sda4
Feb 14 12:11:43 linux-ytaf kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Feb 14 12:11:43 linux-ytaf kernel:  sdb: sdb1 sdb2 sdb3 sdb4
Feb 14 12:11:43 linux-ytaf kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
Feb 14 12:11:43 linux-ytaf kernel: tsc: Refined TSC clocksource calibration: 3411.128 MHz
Feb 14 12:11:43 linux-ytaf kernel: clocksource tsc: mask: 0xffffffffffffffff max_cycles: 0x312b5ecadef, max_idle_ns: 440795307361 ns
Feb 14 12:11:43 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 12:11:43 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff8802268b7d60), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 12:11:43 linux-ytaf kernel: ata3.00: configured for UDMA/66
Feb 14 12:11:43 linux-ytaf kernel: scsi 2:0:0:0: CD-ROM            TSSTcorp CDDVDW SH-S223C  SB05 PQ: 0 ANSI: 5
Feb 14 12:11:43 linux-ytaf kernel: PM: Hibernation image partition 8:18 present
Feb 14 12:11:43 linux-ytaf kernel: PM: Looking for hibernation image.
Feb 14 12:11:43 linux-ytaf kernel: Switched to clocksource tsc
Feb 14 12:11:43 linux-ytaf kernel: PM: Image not found (code -22)
Feb 14 12:11:43 linux-ytaf kernel: PM: Hibernation image not present or could not be loaded.
Feb 14 12:11:43 linux-ytaf kernel: Freeing unused kernel memory: 1560K (ffffffff81f11000 - ffffffff82097000)
Feb 14 12:11:43 linux-ytaf kernel: Write protecting the kernel read-only data: 14336k
Feb 14 12:11:43 linux-ytaf kernel: Freeing unused kernel memory: 1632K (ffff88000d668000 - ffff88000d800000)
Feb 14 12:11:43 linux-ytaf kernel: Freeing unused kernel memory: 1296K (ffff88000dcbc000 - ffff88000de00000)
Feb 14 12:11:43 linux-ytaf systemd[1]: RTC configured in localtime, applying delta of 60 minutes to system time.
Feb 14 12:11:43 linux-ytaf kernel: random: systemd urandom read with 22 bits of entropy available
Feb 14 12:11:43 linux-ytaf kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Feb 14 12:11:43 linux-ytaf kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0
Feb 14 12:11:43 linux-ytaf kernel: scsi 2:0:0:0: Attached scsi generic sg2 type 5
Feb 14 12:11:43 linux-ytaf systemd-journal[187]: Journal started
Feb 14 12:11:43 linux-ytaf dracut-cmdline[181]: dracut-42.1 dracut-037-68.1
Feb 14 12:11:43 linux-ytaf systemd-udevd[250]: Network interface NamePolicy= disabled on kernel commandline, ignoring.
Feb 14 12:11:43 linux-ytaf kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3
Feb 14 12:11:43 linux-ytaf kernel: ACPI: Power Button [PWRB]
Feb 14 12:11:43 linux-ytaf kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
Feb 14 12:11:43 linux-ytaf kernel: ACPI: Power Button [PWRF]
Feb 14 12:11:43 linux-ytaf kernel: ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
Feb 14 12:11:43 linux-ytaf kernel: acpi device:58: registered as cooling_device0
Feb 14 12:11:43 linux-ytaf kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5
Feb 14 12:11:43 linux-ytaf kernel: wmi: Mapper loaded
Feb 14 12:11:43 linux-ytaf kernel: ACPI: bus type USB registered
Feb 14 12:11:43 linux-ytaf kernel: usbcore: registered new interface driver usbfs
Feb 14 12:11:43 linux-ytaf kernel: usbcore: registered new interface driver hub
Feb 14 12:11:43 linux-ytaf kernel: [drm] Initialized drm 1.1.0 20060810
Feb 14 12:11:43 linux-ytaf kernel: usbcore: registered new device driver usb
Feb 14 12:11:43 linux-ytaf kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Feb 14 12:11:43 linux-ytaf kernel: ehci-pci: EHCI PCI platform driver
Feb 14 12:11:43 linux-ytaf kernel: ehci-pci 0000:00:1a.0: EHCI Host Controller
Feb 14 12:11:43 linux-ytaf kernel: ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Feb 14 12:11:43 linux-ytaf kernel: ehci-pci 0000:00:1a.0: debug port 2
Feb 14 12:11:43 linux-ytaf kernel: ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Feb 14 12:11:43 linux-ytaf kernel: ehci-pci 0000:00:1a.0: irq 16, io mem 0xf7b28000
Feb 14 12:11:43 linux-ytaf kernel: MXM: GUID detected in BIOS
Feb 14 12:11:43 linux-ytaf kernel: checking generic (e9000000 1d5000) vs hw (e0000000 8000000)
Feb 14 12:11:43 linux-ytaf kernel: checking generic (e9000000 1d5000) vs hw (e8000000 2000000)
Feb 14 12:11:43 linux-ytaf kernel: fb: switching to nouveaufb from EFI VGA
Feb 14 12:11:43 linux-ytaf kernel: Console: switching to colour dummy device 80x25
Feb 14 12:11:43 linux-ytaf kernel: nouveau  [  DEVICE][0000:02:00.0] BOOT0  : 0x0e4030a2
Feb 14 12:11:43 linux-ytaf kernel: nouveau  [  DEVICE][0000:02:00.0] Chipset: GK104 (NVE4)
Feb 14 12:11:43 linux-ytaf kernel: nouveau  [  DEVICE][0000:02:00.0] Family : NVE0
Feb 14 12:11:43 linux-ytaf kernel: ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Feb 14 12:11:43 linux-ytaf kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 12:11:43 linux-ytaf kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 12:11:43 linux-ytaf kernel: usb usb1: Product: EHCI Host Controller
Feb 14 12:11:43 linux-ytaf kernel: usb usb1: Manufacturer: Linux 4.1.15-8-default ehci_hcd
Feb 14 12:11:43 linux-ytaf kernel: usb usb1: SerialNumber: 0000:00:1a.0
Feb 14 12:11:43 linux-ytaf kernel: sr 2:0:0:0: [sr0] scsi3-mmc drive: 52x/52x writer dvd-ram cd/rw xa/form2 cdda tray
Feb 14 12:11:43 linux-ytaf kernel: cdrom: Uniform CD-ROM driver Revision: 3.20
Feb 14 12:11:43 linux-ytaf kernel: sr 2:0:0:0: Attached scsi CD-ROM sr0
Feb 14 12:11:43 linux-ytaf kernel: hub 1-0:1.0: USB hub found
Feb 14 12:11:43 linux-ytaf kernel: hub 1-0:1.0: 2 ports detected
Feb 14 12:11:43 linux-ytaf kernel: xhci_hcd 0000:04:00.0: xHCI Host Controller
Feb 14 12:11:43 linux-ytaf kernel: xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 2
Feb 14 12:11:43 linux-ytaf kernel: xhci_hcd 0000:04:00.0: hcc params 0x0200f180 hci version 0x96 quirks 0x00080000
Feb 14 12:11:43 linux-ytaf kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 12:11:43 linux-ytaf kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 12:11:43 linux-ytaf kernel: usb usb2: Product: xHCI Host Controller
Feb 14 12:11:43 linux-ytaf kernel: usb usb2: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 12:11:43 linux-ytaf kernel: usb usb2: SerialNumber: 0000:04:00.0
Feb 14 12:11:43 linux-ytaf kernel: hub 2-0:1.0: USB hub found
Feb 14 12:11:43 linux-ytaf kernel: hub 2-0:1.0: 2 ports detected
Feb 14 12:11:43 linux-ytaf kernel: xhci_hcd 0000:04:00.0: xHCI Host Controller
Feb 14 12:11:43 linux-ytaf kernel: xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 3
Feb 14 12:11:43 linux-ytaf kernel: ehci-pci 0000:00:1d.0: EHCI Host Controller
Feb 14 12:11:43 linux-ytaf kernel: usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
Feb 14 12:11:43 linux-ytaf kernel: usb usb3: New USB device found, idVendor=1d6b, idProduct=0003
Feb 14 12:11:43 linux-ytaf kernel: usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 12:11:43 linux-ytaf kernel: usb usb3: Product: xHCI Host Controller
Feb 14 12:11:43 linux-ytaf kernel: usb usb3: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 12:11:43 linux-ytaf kernel: usb usb3: SerialNumber: 0000:04:00.0
Feb 14 12:11:43 linux-ytaf kernel: hub 3-0:1.0: USB hub found
Feb 14 12:11:43 linux-ytaf kernel: hub 3-0:1.0: 2 ports detected
Feb 14 12:11:43 linux-ytaf kernel: ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 4
Feb 14 12:11:43 linux-ytaf kernel: ehci-pci 0000:00:1d.0: debug port 2
Feb 14 12:11:43 linux-ytaf kernel: ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Feb 14 12:11:43 linux-ytaf kernel: ehci-pci 0000:00:1d.0: irq 23, io mem 0xf7b27000
Feb 14 12:11:43 linux-ytaf kernel: ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Feb 14 12:11:43 linux-ytaf kernel: usb usb4: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 12:11:43 linux-ytaf kernel: usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 12:11:43 linux-ytaf kernel: usb usb4: Product: EHCI Host Controller
Feb 14 12:11:43 linux-ytaf kernel: usb usb4: Manufacturer: Linux 4.1.15-8-default ehci_hcd
Feb 14 12:11:43 linux-ytaf kernel: usb usb4: SerialNumber: 0000:00:1d.0
Feb 14 12:11:43 linux-ytaf kernel: hub 4-0:1.0: USB hub found
Feb 14 12:11:43 linux-ytaf kernel: hub 4-0:1.0: 2 ports detected
Feb 14 12:11:43 linux-ytaf kernel: xhci_hcd 0000:05:00.0: xHCI Host Controller
Feb 14 12:11:43 linux-ytaf kernel: xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 5
Feb 14 12:11:43 linux-ytaf kernel: i915 0000:00:02.0: enabling device (0006 -> 0007)
Feb 14 12:11:43 linux-ytaf kernel: xhci_hcd 0000:05:00.0: hcc params 0x0200f180 hci version 0x96 quirks 0x00080000
Feb 14 12:11:43 linux-ytaf kernel: usb usb5: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 12:11:43 linux-ytaf kernel: usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 12:11:43 linux-ytaf kernel: usb usb5: Product: xHCI Host Controller
Feb 14 12:11:43 linux-ytaf kernel: usb usb5: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 12:11:43 linux-ytaf kernel: usb usb5: SerialNumber: 0000:05:00.0
Feb 14 12:11:43 linux-ytaf kernel: hub 5-0:1.0: USB hub found
Feb 14 12:11:43 linux-ytaf kernel: hub 5-0:1.0: 2 ports detected
Feb 14 12:11:43 linux-ytaf kernel: xhci_hcd 0000:05:00.0: xHCI Host Controller
Feb 14 12:11:43 linux-ytaf kernel: xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 6
Feb 14 12:11:43 linux-ytaf kernel: usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
Feb 14 12:11:43 linux-ytaf kernel: usb usb6: New USB device found, idVendor=1d6b, idProduct=0003
Feb 14 12:11:43 linux-ytaf kernel: usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 12:11:43 linux-ytaf kernel: usb usb6: Product: xHCI Host Controller
Feb 14 12:11:43 linux-ytaf kernel: usb usb6: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 12:11:43 linux-ytaf kernel: usb usb6: SerialNumber: 0000:05:00.0
Feb 14 12:11:43 linux-ytaf kernel: hub 6-0:1.0: USB hub found
Feb 14 12:11:43 linux-ytaf kernel: hub 6-0:1.0: 2 ports detected
Feb 14 12:11:43 linux-ytaf kernel: raid6: sse2x1   gen()  8786 MB/s
Feb 14 12:11:43 linux-ytaf kernel: nouveau  [   VBIOS][0000:02:00.0] using image from PROM
Feb 14 12:11:43 linux-ytaf kernel: nouveau  [   VBIOS][0000:02:00.0] BIT signature found
Feb 14 12:11:43 linux-ytaf kernel: nouveau  [   VBIOS][0000:02:00.0] version 80.04.4b.00.07
Feb 14 12:11:43 linux-ytaf kernel: nouveau  [     PMC][0000:02:00.0] MSI interrupts enabled
Feb 14 12:11:43 linux-ytaf kernel: nouveau  [     PFB][0000:02:00.0] RAM type: GDDR5
Feb 14 12:11:43 linux-ytaf kernel: nouveau  [     PFB][0000:02:00.0] RAM size: 2048 MiB
Feb 14 12:11:43 linux-ytaf kernel: nouveau  [     PFB][0000:02:00.0]    ZCOMP: 0 tags
Feb 14 12:11:43 linux-ytaf kernel: nouveau  [    VOLT][0000:02:00.0] GPU voltage: 987500uv
Feb 14 12:11:43 linux-ytaf kernel: nouveau  [  PTHERM][0000:02:00.0] FAN control: PWM
Feb 14 12:11:43 linux-ytaf kernel: nouveau  [  PTHERM][0000:02:00.0] fan management: automatic
Feb 14 12:11:43 linux-ytaf kernel: nouveau  [  PTHERM][0000:02:00.0] internal sensor: yes
Feb 14 12:11:43 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 07: core 324 MHz memory 648 MHz 
Feb 14 12:11:43 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 0a: core 324-862 MHz memory 1620 MHz 
Feb 14 12:11:43 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 0d: core 540-1202 MHz memory 6008 MHz 
Feb 14 12:11:43 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 0f: core 540-1202 MHz memory 6008 MHz 
Feb 14 12:11:43 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] --: core 324 MHz memory 648 MHz 
Feb 14 12:11:43 linux-ytaf kernel: raid6: sse2x1   xor()  8983 MB/s
Feb 14 12:11:43 linux-ytaf kernel: usb 1-1: new high-speed USB device number 2 using ehci-pci
Feb 14 12:11:43 linux-ytaf kernel: raid6: sse2x2   gen() 14104 MB/s
Feb 14 12:11:43 linux-ytaf kernel: [TTM] Zone  kernel: Available graphics memory: 4034698 kiB
Feb 14 12:11:43 linux-ytaf kernel: [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
Feb 14 12:11:43 linux-ytaf kernel: [TTM] Initializing pool allocator
Feb 14 12:11:43 linux-ytaf kernel: [TTM] Initializing DMA pool allocator
Feb 14 12:11:43 linux-ytaf kernel: nouveau  [     DRM] VRAM: 2048 MiB
Feb 14 12:11:43 linux-ytaf kernel: nouveau  [     DRM] GART: 1048576 MiB
Feb 14 12:11:43 linux-ytaf kernel: nouveau  [     DRM] TMDS table version 2.0
Feb 14 12:11:43 linux-ytaf kernel: nouveau  [     DRM] DCB version 4.0
Feb 14 12:11:43 linux-ytaf kernel: nouveau  [     DRM] DCB outp 00: 01000f02 00020030
Feb 14 12:11:43 linux-ytaf kernel: nouveau  [     DRM] DCB outp 01: 02000f00 00000000
Feb 14 12:11:43 linux-ytaf kernel: nouveau  [     DRM] DCB outp 02: 08011f82 00020030
Feb 14 12:11:43 linux-ytaf kernel: nouveau  [     DRM] DCB outp 03: 02822f62 0f420010
Feb 14 12:11:43 linux-ytaf kernel: nouveau  [     DRM] DCB outp 05: 04833fb6 0f420010
Feb 14 12:11:43 linux-ytaf kernel: nouveau  [     DRM] DCB outp 06: 04033f72 00020010
Feb 14 12:11:43 linux-ytaf kernel: nouveau  [     DRM] DCB conn 00: 00001030
Feb 14 12:11:43 linux-ytaf kernel: nouveau  [     DRM] DCB conn 01: 00020131
Feb 14 12:11:43 linux-ytaf kernel: nouveau  [     DRM] DCB conn 02: 00002261
Feb 14 12:11:43 linux-ytaf kernel: nouveau  [     DRM] DCB conn 03: 00010346
Feb 14 12:11:43 linux-ytaf kernel: nouveau  [     DRM] DCB conn 04: 00000460
Feb 14 12:11:43 linux-ytaf kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Feb 14 12:11:43 linux-ytaf kernel: [drm] Driver supports precise vblank timestamp query.
Feb 14 12:11:43 linux-ytaf kernel: nouveau  [     DRM] MM: using COPY for buffer copies
Feb 14 12:11:43 linux-ytaf kernel: raid6: sse2x2   xor() 10054 MB/s
Feb 14 12:11:43 linux-ytaf kernel: usb 4-1: new high-speed USB device number 2 using ehci-pci
Feb 14 12:11:44 linux-ytaf kernel: usb 1-1: New USB device found, idVendor=8087, idProduct=0024
Feb 14 12:11:44 linux-ytaf kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb 14 12:11:44 linux-ytaf kernel: hub 1-1:1.0: USB hub found
Feb 14 12:11:44 linux-ytaf kernel: hub 1-1:1.0: 6 ports detected
Feb 14 12:11:44 linux-ytaf kernel: raid6: sse2x4   gen() 16264 MB/s
Feb 14 12:11:44 linux-ytaf kernel: usb 5-2: new high-speed USB device number 2 using xhci_hcd
Feb 14 12:11:44 linux-ytaf kernel: raid6: sse2x4   xor() 12096 MB/s
Feb 14 12:11:44 linux-ytaf kernel: raid6: using algorithm sse2x4 gen() 16264 MB/s
Feb 14 12:11:44 linux-ytaf kernel: raid6: .... xor() 12096 MB/s, rmw enabled
Feb 14 12:11:44 linux-ytaf kernel: raid6: using ssse3x2 recovery algorithm
Feb 14 12:11:44 linux-ytaf kernel: xor: automatically using best checksumming function:
Feb 14 12:11:44 linux-ytaf kernel: usb 4-1: New USB device found, idVendor=8087, idProduct=0024
Feb 14 12:11:44 linux-ytaf kernel: usb 4-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb 14 12:11:44 linux-ytaf kernel: hub 4-1:1.0: USB hub found
Feb 14 12:11:44 linux-ytaf kernel: hub 4-1:1.0: 8 ports detected
Feb 14 12:11:44 linux-ytaf kernel:    avx       : 31206.000 MB/sec
Feb 14 12:11:44 linux-ytaf kernel: Btrfs loaded, assert=on
Feb 14 12:11:44 linux-ytaf kernel: BTRFS: device fsid 21024970-7a27-4114-8525-d8dd026f23b6 devid 1 transid 284 /dev/sdb3
Feb 14 12:11:44 linux-ytaf kernel: nouveau  [     DRM] allocated 1920x1080 fb: 0x60000, bo ffff88000b137000
Feb 14 12:11:44 linux-ytaf kernel: fbcon: nouveaufb (fb0) is primary device
Feb 14 12:11:44 linux-ytaf kernel: usb 5-2: New USB device found, idVendor=0930, idProduct=6545
Feb 14 12:11:44 linux-ytaf kernel: usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 14 12:11:44 linux-ytaf kernel: usb 5-2: Product: TransMemory
Feb 14 12:11:44 linux-ytaf kernel: usb 5-2: Manufacturer: TOSHIBA
Feb 14 12:11:44 linux-ytaf kernel: usb 5-2: SerialNumber: C89CDCBF6D59EF4140000065
Feb 14 12:11:44 linux-ytaf kernel: usb-storage 5-2:1.0: USB Mass Storage device detected
Feb 14 12:11:44 linux-ytaf kernel: scsi host8: usb-storage 5-2:1.0
Feb 14 12:11:44 linux-ytaf kernel: usbcore: registered new interface driver usb-storage
Feb 14 12:11:44 linux-ytaf kernel: usbcore: registered new interface driver uas
Feb 14 12:11:44 linux-ytaf kernel: usb 1-1.4: new full-speed USB device number 3 using ehci-pci
Feb 14 12:11:44 linux-ytaf kernel: usb 4-1.1: new full-speed USB device number 3 using ehci-pci
Feb 14 12:11:44 linux-ytaf kernel: usb 4-1.1: New USB device found, idVendor=1532, idProduct=0109
Feb 14 12:11:44 linux-ytaf kernel: usb 4-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 14 12:11:44 linux-ytaf kernel: usb 4-1.1: Product: Razer Lycosa
Feb 14 12:11:44 linux-ytaf kernel: usb 4-1.1: Manufacturer: Razer
Feb 14 12:11:44 linux-ytaf kernel: usbcore: registered new interface driver usbhid
Feb 14 12:11:44 linux-ytaf kernel: usbhid: USB HID core driver
Feb 14 12:11:44 linux-ytaf kernel: input: Razer Razer Lycosa as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1:1.0/0003:1532:0109.0001/input/input6
Feb 14 12:11:44 linux-ytaf kernel: usb 1-1.4: New USB device found, idVendor=06a3, idProduct=0ccb
Feb 14 12:11:44 linux-ytaf kernel: usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 14 12:11:44 linux-ytaf kernel: usb 1-1.4: Product: Cyborg R.A.T.7 Mouse
Feb 14 12:11:44 linux-ytaf kernel: usb 1-1.4: Manufacturer: Saitek
Feb 14 12:11:44 linux-ytaf kernel: hid-generic 0003:1532:0109.0001: input,hidraw0: USB HID v1.10 Keyboard [Razer Razer Lycosa] on usb-0000:00:1d.0-1.1/input0
Feb 14 12:11:44 linux-ytaf kernel: input: Razer Razer Lycosa as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1:1.1/0003:1532:0109.0002/input/input7
Feb 14 12:11:44 linux-ytaf kernel: hid-generic 0003:1532:0109.0002: input,hidraw1: USB HID v1.10 Device [Razer Razer Lycosa] on usb-0000:00:1d.0-1.1/input1
Feb 14 12:11:44 linux-ytaf kernel: Console: switching to colour frame buffer device 210x65
Feb 14 12:11:44 linux-ytaf kernel: nouveau 0000:02:00.0: fb0: nouveaufb frame buffer device
Feb 14 12:11:44 linux-ytaf kernel: nouveau 0000:02:00.0: registered panic notifier
Feb 14 12:11:44 linux-ytaf kernel: [drm] Initialized nouveau 1.2.2 20120801 for 0000:02:00.0 on minor 0
Feb 14 12:11:44 linux-ytaf kernel: [drm] Memory usable by graphics device = 2048M
Feb 14 12:11:44 linux-ytaf kernel: [drm] Replacing VGA console driver
Feb 14 12:11:44 linux-ytaf kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Feb 14 12:11:44 linux-ytaf kernel: [drm] Driver supports precise vblank timestamp query.
Feb 14 12:11:44 linux-ytaf kernel: vgaarb: device changed decodes: PCI:0000:02:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
Feb 14 12:11:44 linux-ytaf kernel: [drm] Initialized i915 1.6.0 20150327 for 0000:00:02.0 on minor 1
Feb 14 12:11:44 linux-ytaf kernel: [drm] GMBUS [i915 gmbus vga] timed out, falling back to bit banging on pin 2
Feb 14 12:11:44 linux-ytaf kernel: i915 0000:00:02.0: No connectors reported connected with modes
Feb 14 12:11:44 linux-ytaf kernel: [drm] Cannot find any crtc or sizes - going 1024x768
Feb 14 12:11:44 linux-ytaf kernel: i915 0000:00:02.0: fb1: inteldrmfb frame buffer device
Feb 14 12:11:45 linux-ytaf kernel: scsi 8:0:0:0: Direct-Access     TOSHIBA  TransMemory      PMAP PQ: 0 ANSI: 6
Feb 14 12:11:45 linux-ytaf kernel: sd 8:0:0:0: Attached scsi generic sg3 type 0
Feb 14 12:11:45 linux-ytaf kernel: sd 8:0:0:0: [sdc] 30228480 512-byte logical blocks: (15.4 GB/14.4 GiB)
Feb 14 12:11:45 linux-ytaf kernel: sd 8:0:0:0: [sdc] Write Protect is off
Feb 14 12:11:45 linux-ytaf kernel: sd 8:0:0:0: [sdc] Mode Sense: 45 00 00 00
Feb 14 12:11:45 linux-ytaf kernel: sd 8:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Feb 14 12:11:45 linux-ytaf kernel:  sdc: sdc1
Feb 14 12:11:45 linux-ytaf kernel: sd 8:0:0:0: [sdc] Attached SCSI removable disk
Feb 14 12:11:45 linux-ytaf kernel: PM: Starting manual resume from disk
Feb 14 12:11:45 linux-ytaf kernel: PM: Hibernation image partition 8:18 present
Feb 14 12:11:45 linux-ytaf kernel: PM: Looking for hibernation image.
Feb 14 12:11:45 linux-ytaf kernel: PM: Image not found (code -22)
Feb 14 12:11:45 linux-ytaf kernel: PM: Hibernation image not present or could not be loaded.
Feb 14 12:11:45 linux-ytaf kernel: BTRFS info (device sdb3): disk space caching is enabled
Feb 14 12:11:45 linux-ytaf kernel: BTRFS: has skinny extents
Feb 14 12:11:45 linux-ytaf systemd-journal[187]: Journal stopped
Feb 14 12:11:47 linux-ytaf systemd-journal[478]: Runtime journal is using 8.0M (max allowed 394.0M, trying to leave 591.0M free of 3.8G available → current limit 394.0M).
Feb 14 12:11:47 linux-ytaf systemd-journal[478]: Runtime journal is using 8.0M (max allowed 394.0M, trying to leave 591.0M free of 3.8G available → current limit 394.0M).
Feb 14 12:11:47 linux-ytaf kernel: random: nonblocking pool is initialized
Feb 14 12:11:47 linux-ytaf systemd[1]: RTC configured in localtime, applying delta of 60 minutes to system time.
Feb 14 12:11:47 linux-ytaf systemd-journal[478]: Journal started
Feb 14 12:11:47 linux-ytaf systemd-udevd[495]: starting version 210
Feb 14 12:11:47 linux-ytaf systemd-udevd[495]: Network interface NamePolicy= disabled on kernel commandline, ignoring.
Feb 14 12:11:47 linux-ytaf systemd-udevd[495]: invalid key/value pair in file /usr/lib/udev/rules.d/51-android.rules on line 115,starting at character 57 ('')
Feb 14 12:11:47 linux-ytaf kernel: BTRFS info (device sdb3): disk space caching is enabled
Feb 14 12:11:48 linux-ytaf kernel: thermal LNXTHERM:00: registered as thermal_zone0
Feb 14 12:11:48 linux-ytaf kernel: ACPI: Thermal Zone [TZ00] (28 C)
Feb 14 12:11:48 linux-ytaf kernel: thermal LNXTHERM:01: registered as thermal_zone1
Feb 14 12:11:48 linux-ytaf kernel: ACPI: Thermal Zone [TZ01] (30 C)
Feb 14 12:11:48 linux-ytaf kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Feb 14 12:11:48 linux-ytaf kernel: pps_core: LinuxPPS API ver. 1 registered
Feb 14 12:11:48 linux-ytaf kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
Feb 14 12:11:48 linux-ytaf kernel: PTP clock support registered
Feb 14 12:11:48 linux-ytaf kernel: input: PC Speaker as /devices/platform/pcspkr/input/input8
Feb 14 12:11:48 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20150410/utaddress-254)
Feb 14 12:11:48 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 12:11:48 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150410/utaddress-254)
Feb 14 12:11:48 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150410/utaddress-254)
Feb 14 12:11:48 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 12:11:48 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150410/utaddress-254)
Feb 14 12:11:48 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150410/utaddress-254)
Feb 14 12:11:48 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 12:11:48 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150410/utaddress-254)
Feb 14 12:11:48 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150410/utaddress-254)
Feb 14 12:11:48 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 12:11:48 linux-ytaf kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
Feb 14 12:11:48 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000580-0x000000000000059F conflicts with OpRegion 0x0000000000000580-0x000000000000058F (\_SB_.PCI0.SBUS.SMBI) (20150410/utaddress-254)
Feb 14 12:11:48 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000580-0x000000000000059F conflicts with OpRegion 0x0000000000000580-0x000000000000059F (\_SB_.PCI0.SMB_.SMIO) (20150410/utaddress-254)
Feb 14 12:11:48 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 12:11:48 linux-ytaf kernel: asus_wmi: ASUS WMI generic driver loaded
Feb 14 12:11:48 linux-ytaf kernel: asus_wmi: Initialization: 0x0
Feb 14 12:11:48 linux-ytaf kernel: asus_wmi: BIOS WMI version: 0.9
Feb 14 12:11:48 linux-ytaf kernel: asus_wmi: SFUN value: 0x0
Feb 14 12:11:48 linux-ytaf kernel: input: Eee PC WMI hotkeys as /devices/platform/eeepc-wmi/input/input9
Feb 14 12:11:48 linux-ytaf kernel: asus_wmi: Disabling ACPI video driver
Feb 14 12:11:48 linux-ytaf kernel: e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
Feb 14 12:11:48 linux-ytaf kernel: e1000e: Copyright(c) 1999 - 2014 Intel Corporation.
Feb 14 12:11:48 linux-ytaf kernel: e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
Feb 14 12:11:48 linux-ytaf kernel: iTCO_vendor_support: vendor-support=0
Feb 14 12:11:48 linux-ytaf mtp-probe[618]: checking bus 5, device 2: "/sys/devices/pci0000:00/0000:00:1c.5/0000:05:00.0/usb5/5-2"
Feb 14 12:11:48 linux-ytaf mtp-probe[615]: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4"
Feb 14 12:11:48 linux-ytaf mtp-probe[616]: checking bus 4, device 3: "/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1"
Feb 14 12:11:48 linux-ytaf mtp-probe[618]: bus: 5, device: 2 was not an MTP device
Feb 14 12:11:48 linux-ytaf mtp-probe[615]: bus: 1, device: 3 was not an MTP device
Feb 14 12:11:48 linux-ytaf mtp-probe[616]: bus: 4, device: 3 was not an MTP device
Feb 14 12:11:48 linux-ytaf kernel: iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
Feb 14 12:11:48 linux-ytaf kernel: iTCO_wdt: Found a Cougar Point TCO device (Version=2, TCOBASE=0x0460)
Feb 14 12:11:48 linux-ytaf kernel: iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
Feb 14 12:11:48 linux-ytaf kernel: input: Saitek Cyborg R.A.T.7 Mouse as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/0003:06A3:0CCB.0003/input/input10
Feb 14 12:11:48 linux-ytaf kernel: saitek 0003:06A3:0CCB.0003: input,hidraw2: USB HID v1.11 Mouse [Saitek Cyborg R.A.T.7 Mouse] on usb-0000:00:1a.0-1.4/input0
Feb 14 12:11:48 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: registered PHC clock
Feb 14 12:11:48 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) c8:60:00:09:38:76
Feb 14 12:11:48 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
Feb 14 12:11:48 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: FFFFFF-0FF
Feb 14 12:11:48 linux-ytaf kernel: snd_hda_intel 0000:00:1b.0: enabling device (0000 -> 0002)
Feb 14 12:11:48 linux-ytaf kernel: snd_hda_intel 0000:02:00.1: enabling device (0000 -> 0002)
Feb 14 12:11:48 linux-ytaf kernel: snd_hda_intel 0000:02:00.1: Disabling MSI
Feb 14 12:11:48 linux-ytaf kernel: snd_hda_intel 0000:02:00.1: Handle VGA-switcheroo audio client
Feb 14 12:11:48 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC889: line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line
Feb 14 12:11:48 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Feb 14 12:11:48 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
Feb 14 12:11:48 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
Feb 14 12:11:48 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    dig-out=0x11/0x1e
Feb 14 12:11:48 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    inputs:
Feb 14 12:11:48 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:      Front Mic=0x19
Feb 14 12:11:48 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:      Rear Mic=0x18
Feb 14 12:11:48 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:      Line=0x1a
Feb 14 12:11:49 linux-ytaf kernel: input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
Feb 14 12:11:49 linux-ytaf kernel: input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
Feb 14 12:11:49 linux-ytaf kernel: input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input13
Feb 14 12:11:49 linux-ytaf kernel: input: HDA Intel PCH Line Out Front as /devices/pci0000:00/0000:00:1b.0/sound/card0/input14
Feb 14 12:11:49 linux-ytaf kernel: input: HDA Intel PCH Line Out Surround as /devices/pci0000:00/0000:00:1b.0/sound/card0/input15
Feb 14 12:11:49 linux-ytaf kernel: input: HDA Intel PCH Line Out CLFE as /devices/pci0000:00/0000:00:1b.0/sound/card0/input16
Feb 14 12:11:49 linux-ytaf kernel: input: HDA Intel PCH Line Out Side as /devices/pci0000:00/0000:00:1b.0/sound/card0/input17
Feb 14 12:11:49 linux-ytaf kernel: input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input18
Feb 14 12:11:49 linux-ytaf kernel: AVX version of gcm_enc/dec engaged.
Feb 14 12:11:49 linux-ytaf kernel: AES CTR mode by8 optimization enabled
Feb 14 12:11:49 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input19
Feb 14 12:11:49 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input20
Feb 14 12:11:49 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input21
Feb 14 12:11:49 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input22
Feb 14 12:11:49 linux-ytaf kernel: Adding 2104316k swap on /dev/sdb2.  Priority:-1 extents:1 across:2104316k FS
Feb 14 12:11:49 linux-ytaf kernel: FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Feb 14 12:11:49 linux-ytaf systemd-fsck[689]: /sbin/fsck.xfs: XFS file system.
Feb 14 12:11:49 linux-ytaf kernel: SGI XFS with ACLs, security attributes, realtime, no debug enabled
Feb 14 12:11:50 linux-ytaf kernel: XFS (sdb4): Mounting V5 Filesystem
Feb 14 12:11:51 linux-ytaf kernel: XFS (sdb4): Starting recovery (logdev: internal)
Feb 14 12:11:51 linux-ytaf kernel: XFS (sdb4): Ending recovery (logdev: internal)
Feb 14 12:11:52 linux-ytaf systemd-journal[478]: Permanent journal is using 55.7M (max allowed 4.0G, trying to leave 4.0G free of 32.8G available → current limit 4.0G).
Feb 14 12:11:52 linux-ytaf systemd-journal[478]: Time spent on flushing to /var is 32.907ms for 1032 entries.
Feb 14 12:11:52 linux-ytaf kernel: audit: type=1305 audit(1455448312.057:2): audit_pid=773 old=0 auid=4294967295 ses=4294967295 res=1
Feb 14 12:11:52 linux-ytaf auditd[773]: Started dispatcher: /sbin/audispd pid: 784
Feb 14 12:11:52 linux-ytaf audispd[784]: priority_boost_parser called with: 4
Feb 14 12:11:52 linux-ytaf audispd[784]: max_restarts_parser called with: 10
Feb 14 12:11:52 linux-ytaf audispd[784]: No plugins found, exiting
Feb 14 12:11:52 linux-ytaf auditd[773]: Init complete, auditd 2.3.6 listening for events (startup state enable)
Feb 14 12:11:52 linux-ytaf auditctl[774]: No rules
Feb 14 12:11:52 linux-ytaf auditctl[774]: AUDIT_STATUS: enabled=0 flag=1 pid=0 rate_limit=0 backlog_limit=320 lost=0 backlog=0
Feb 14 12:11:53 linux-ytaf boot.apparmor[787]: Starting AppArmor ..done
Feb 14 12:11:54 linux-ytaf dbus-daemon[949]: Unknown username "srvGeoClue" in message bus configuration file
Feb 14 12:11:54 linux-ytaf alsactl[960]: /usr/sbin/alsactl: load_state:1683: Cannot open /var/lib/alsa/asound.state for reading: No such file or directory
Feb 14 12:11:54 linux-ytaf alsactl[960]: Found hardware: "HDA-Intel" "Intel CougarPoint HDMI" "HDA:10ec0889,1043846b,00100004 HDA:80862805,80860101,00100000" "0x1043" "0x84dc"
Feb 14 12:11:54 linux-ytaf alsactl[960]: Hardware is initialized using a generic method
Feb 14 12:11:54 linux-ytaf alsactl[960]: Found hardware: "HDA-Intel" "Nvidia GPU 40 HDMI/DP" "HDA:10de0040,00000000,00100100" "0x0000" "0x0000"
Feb 14 12:11:54 linux-ytaf alsactl[960]: Hardware is initialized using a generic method
Feb 14 12:11:54 linux-ytaf display-manager[979]: /etc/vconsole.conf available
Feb 14 12:11:54 linux-ytaf display-manager[979]: KEYMAP: de-latin1-nodeadkeys
Feb 14 12:11:54 linux-ytaf display-manager[979]: Command: localectl set-keymap de-latin1-nodeadkeys
Feb 14 12:11:54 linux-ytaf display-manager[979]: I: Using systemd /usr/share/systemd/kbd-model-map mapping
Feb 14 12:11:54 linux-ytaf dbus[949]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service'
Feb 14 12:11:54 linux-ytaf smartd[956]: smartd 6.2 2013-11-07 r3856 [x86_64-linux-4.1.15-8-default] (SUSE RPM)
Feb 14 12:11:54 linux-ytaf smartd[956]: Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
Feb 14 12:11:54 linux-ytaf smartd[956]: Opened configuration file /etc/smartd.conf
Feb 14 12:11:54 linux-ytaf smartd[956]: Drive: DEVICESCAN, implied '-a' Directive on line 26 of file /etc/smartd.conf
Feb 14 12:11:54 linux-ytaf smartd[956]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
Feb 14 12:11:54 linux-ytaf dbus[949]: [system] Successfully activated service 'org.freedesktop.locale1'
Feb 14 12:11:54 linux-ytaf smartd[956]: Device: /dev/sda, type changed from 'scsi' to 'sat'
Feb 14 12:11:54 linux-ytaf smartd[956]: Device: /dev/sda [SAT], opened
Feb 14 12:11:54 linux-ytaf smartd[956]: Device: /dev/sda [SAT], SAMSUNG SSD 830 Series, S/N:S0Z4NEAC906195, WWN:5-002538-043584d30, FW:CXM03B1Q, 256 GB
Feb 14 12:11:54 linux-ytaf smartd[956]: Device: /dev/sda [SAT], found in smartd database: Samsung based SSDs
Feb 14 12:11:54 linux-ytaf smartd[956]: Device: /dev/sda [SAT], can't monitor Current_Pending_Sector count - no Attribute 197
Feb 14 12:11:54 linux-ytaf smartd[956]: Device: /dev/sda [SAT], can't monitor Offline_Uncorrectable count - no Attribute 198
Feb 14 12:11:54 linux-ytaf smartd[956]: Device: /dev/sda [SAT], is SMART capable. Adding to "monitor" list.
Feb 14 12:11:54 linux-ytaf smartd[956]: Device: /dev/sda [SAT], state read from /var/lib/smartmontools/smartd.SAMSUNG_SSD_830_Series-S0Z4NEAC906195.ata.state
Feb 14 12:11:54 linux-ytaf avahi-daemon[950]: Found user 'avahi' (UID 486) and group 'avahi' (GID 485).
Feb 14 12:11:54 linux-ytaf avahi-daemon[950]: Successfully dropped root privileges.
Feb 14 12:11:54 linux-ytaf avahi-daemon[950]: avahi-daemon 0.6.31 starting up.
Feb 14 12:11:54 linux-ytaf avahi-daemon[950]: Loading service file /etc/avahi/services/sftp-ssh.service.
Feb 14 12:11:54 linux-ytaf avahi-daemon[950]: Loading service file /etc/avahi/services/ssh.service.
Feb 14 12:11:54 linux-ytaf avahi-daemon[950]: Network interface enumeration completed.
Feb 14 12:11:54 linux-ytaf avahi-daemon[950]: Registering HINFO record with values 'X86_64'/'LINUX'.
Feb 14 12:11:54 linux-ytaf avahi-daemon[950]: Server startup complete. Host name is linux-ytaf.local. Local service cookie is 1780147688.
Feb 14 12:11:54 linux-ytaf avahi-daemon[950]: Service "linux-ytaf" (/etc/avahi/services/ssh.service) successfully established.
Feb 14 12:11:54 linux-ytaf avahi-daemon[950]: Service "linux-ytaf" (/etc/avahi/services/sftp-ssh.service) successfully established.
Feb 14 12:11:54 linux-ytaf smartd[956]: Device: /dev/sdb, type changed from 'scsi' to 'sat'
Feb 14 12:11:54 linux-ytaf smartd[956]: Device: /dev/sdb [SAT], opened
Feb 14 12:11:54 linux-ytaf smartd[956]: Device: /dev/sdb [SAT], TOSHIBA HDWD110, S/N:Y5GDEMGFS, WWN:5-000039-fe7c5a79c, FW:MS2OA8J0, 1.00 TB
Feb 14 12:11:54 linux-ytaf ModemManager[952]: <info>  ModemManager (version 1.4.10) starting in system bus...
Feb 14 12:11:54 linux-ytaf kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
Feb 14 12:11:54 linux-ytaf kernel: nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
Feb 14 12:11:54 linux-ytaf kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Feb 14 12:11:54 linux-ytaf dbus[949]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Feb 14 12:11:54 linux-ytaf smartd[956]: Device: /dev/sdb [SAT], not found in smartd database.
Feb 14 12:11:54 linux-ytaf SuSEfirewall2[1046]: Firewall rules set to CLOSE.
Feb 14 12:11:54 linux-ytaf kernel: No iBFT detected.
Feb 14 12:11:55 linux-ytaf polkitd[1048]: Started polkitd version 0.113
Feb 14 12:11:55 linux-ytaf polkitd[1048]: Loading rules from directory /etc/polkit-1/rules.d
Feb 14 12:11:55 linux-ytaf polkitd[1048]: Loading rules from directory /usr/share/polkit-1/rules.d
Feb 14 12:11:55 linux-ytaf polkitd[1048]: Finished loading, compiling and executing 3 rules
Feb 14 12:11:55 linux-ytaf dbus[949]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Feb 14 12:11:55 linux-ytaf polkitd[1048]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
Feb 14 12:11:56 linux-ytaf smartd[956]: Device: /dev/sdb [SAT], is SMART capable. Adding to "monitor" list.
Feb 14 12:11:56 linux-ytaf smartd[956]: Device: /dev/sdb [SAT], state read from /var/lib/smartmontools/smartd.TOSHIBA_HDWD110-Y5GDEMGFS.ata.state
Feb 14 12:11:56 linux-ytaf smartd[956]: Monitoring 2 ATA and 0 SCSI devices
Feb 14 12:11:56 linux-ytaf smartd[956]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 77 to 76
Feb 14 12:11:56 linux-ytaf smartd[956]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 253 to 230
Feb 14 12:11:57 linux-ytaf ModemManager[952]: <info>  Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin
Feb 14 12:11:57 linux-ytaf smartd[956]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.SAMSUNG_SSD_830_Series-S0Z4NEAC906195.ata.state
Feb 14 12:11:57 linux-ytaf smartd[956]: Device: /dev/sdb [SAT], state written to /var/lib/smartmontools/smartd.TOSHIBA_HDWD110-Y5GDEMGFS.ata.state
Feb 14 12:11:57 linux-ytaf logger[1054]: /etc/init.d/xdm: No changes for /etc/X11/xdm/Xservers
Feb 14 12:11:57 linux-ytaf logger[1054]: /etc/init.d/xdm: No changes for /etc/X11/xdm/xdm-config
Feb 14 12:11:58 linux-ytaf sddm[1176]: Starting...
Feb 14 12:11:58 linux-ytaf sddm[1176]: Adding new display on vt 7 ...
Feb 14 12:11:58 linux-ytaf sddm[1176]: Display server starting...
Feb 14 12:11:58 linux-ytaf display-manager[979]: Starting service sddm..done
Feb 14 12:11:59 linux-ytaf kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Feb 14 12:11:59 linux-ytaf wickedd-dhcp4[1055]: eth0: Request to acquire DHCPv4 lease with UUID fc60c056-499c-0b00-2204-000004000000
Feb 14 12:11:59 linux-ytaf kernel: NET: Registered protocol family 17
Feb 14 12:12:00 linux-ytaf sddm[1176]: Display server started.
Feb 14 12:12:00 linux-ytaf sddm[1176]: Socket server starting...
Feb 14 12:12:00 linux-ytaf sddm[1176]: Socket server started.
Feb 14 12:12:00 linux-ytaf sddm[1176]: Greeter starting...
Feb 14 12:12:00 linux-ytaf sddm[1176]: Adding cookie to "/run/sddm/{20658caf-1c5c-4d4a-b835-124f2ac9ec5e}"
Feb 14 12:12:00 linux-ytaf sddm-helper[1246]: [PAM] Authenticating...
Feb 14 12:12:00 linux-ytaf sddm-helper[1246]: [PAM] returning.
Feb 14 12:12:00 linux-ytaf sddm-helper[1246]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
Feb 14 12:12:00 linux-ytaf systemd[1248]: pam_unix(systemd-user:session): session opened for user sddm by (uid=0)
Feb 14 12:12:00 linux-ytaf sddm[1176]: Message received from greeter: Connect
Feb 14 12:12:02 linux-ytaf dbus[949]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
Feb 14 12:12:02 linux-ytaf udisksd[1260]: udisks daemon version 2.1.6 starting
Feb 14 12:12:03 linux-ytaf dbus[949]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Feb 14 12:12:03 linux-ytaf udisksd[1260]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Feb 14 12:12:03 linux-ytaf dbus[949]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
Feb 14 12:12:03 linux-ytaf dbus[949]: [system] Successfully activated service 'org.freedesktop.UPower'
Feb 14 12:12:04 linux-ytaf wickedd-dhcp4[1055]: eth0: Committed DHCPv4 lease with address 192.168.178.12 (lease time 864000 sec, renew in 432000 sec, rebind in 756000 sec)
Feb 14 12:12:04 linux-ytaf avahi-daemon[950]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.178.12.
Feb 14 12:12:04 linux-ytaf avahi-daemon[950]: New relevant interface eth0.IPv4 for mDNS.
Feb 14 12:12:04 linux-ytaf avahi-daemon[950]: Registering new address record for 192.168.178.12 on eth0.IPv4.
Feb 14 12:12:04 linux-ytaf wickedd[1058]: eth0: Notified neighbours about IP address 192.168.178.12
Feb 14 12:12:04 MM-Home wicked[1060]: lo              up
Feb 14 12:12:04 MM-Home wicked[1060]: eth0            up
Feb 14 12:12:04 MM-Home echo[1468]: Starting mail service (Postfix)
Feb 14 12:12:04 MM-Home iscsiadm[1470]: iscsiadm: No records found
Feb 14 12:12:04 MM-Home SuSEfirewall2[1497]: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Feb 14 12:12:04 MM-Home SuSEfirewall2[1504]: using default zone 'ext' for interface eth0
Feb 14 12:12:04 MM-Home SuSEfirewall2[1634]: Firewall rules successfully set
Feb 14 12:12:04 MM-Home ntpd[1486]: ntpd 4.2.8p4@1.3265-o Thu Dec 17 05:32:52 UTC 2015 (1): Starting
Feb 14 12:12:04 MM-Home ntpd[1486]: Command line: /usr/sbin/ntpd -p /var/run/ntp/ntpd.pid -g -u ntp:ntp -c /etc/ntp.conf
Feb 14 12:12:04 MM-Home sntp[1662]: sntp 4.2.8p4@1.3265-o Thu Dec 17 05:32:29 UTC 2015 (1)
Feb 14 12:12:04 MM-Home sntp[1662]: kod_init_kod_db(): Cannot open KoD db file /var/db/ntp-kod: No such file or directory
Feb 14 12:12:04 MM-Home start-ntpd[1474]: Starting network time protocol daemon (NTPD)sntp 4.2.8p4@1.3265-o Thu Dec 17 05:32:29 UTC 2015 (1)
Feb 14 12:12:04 MM-Home start-ntpd[1474]: kod_init_kod_db(): Cannot open KoD db file /var/db/ntp-kod: No such file or directory
Feb 14 12:12:04 MM-Home ntpd[1661]: proto: precision = 0.050 usec (-24)
Feb 14 12:12:04 MM-Home sntp[1662]: 2016-02-14 12:12:04.890401 (-0100) +0.02684 +/- 0.062487 192.168.178.1 s3 no-leap
Feb 14 12:12:04 MM-Home ntpd[1661]: switching logging to file /var/log/ntp
Feb 14 12:12:04 MM-Home start-ntpd[1474]: 2016-02-14 12:12:04.890401 (-0100) +0.02684 +/- 0.062487 192.168.178.1 s3 no-leap
Feb 14 12:12:04 MM-Home postfix/postfix-script[1669]: starting the Postfix mail system
Feb 14 12:12:04 MM-Home /usr/sbin/start-ntpd[1670]: runtime configuration: server 192.168.178.1
Feb 14 12:12:04 MM-Home postfix/master[1672]: daemon started -- version 2.11.6, configuration /etc/postfix
Feb 14 12:12:04 MM-Home cron[1689]: (CRON) INFO (RANDOM_DELAY will be scaled with factor 76% if used.)
Feb 14 12:12:04 MM-Home cron[1689]: (CRON) INFO (running with inotify support)
Feb 14 12:13:19 MM-Home kernel: nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
Feb 14 12:15:01 MM-Home cron[1696]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 12:15:01 MM-Home systemd[1697]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 12:15:02 MM-Home CRON[1696]: pam_unix(crond:session): session closed for user root
Feb 14 12:15:02 MM-Home systemd[1698]: pam_unix(systemd-user:session): session closed for user root
Feb 14 12:23:18 MM-Home sddm[1176]: Message received from greeter: Login
Feb 14 12:23:18 MM-Home sddm[1176]: Reading from "/usr/share/xsessions/plasma5.desktop"
Feb 14 12:23:18 MM-Home sddm[1176]: Session "/usr/share/xsessions/plasma5.desktop" selected, command: "/usr/bin/startkde"
Feb 14 12:23:18 MM-Home sddm-helper[1735]: [PAM] Starting...
Feb 14 12:23:18 MM-Home sddm-helper[1735]: [PAM] Authenticating...
Feb 14 12:23:18 MM-Home sddm-helper[1735]: [PAM] Preparing to converse...
Feb 14 12:23:18 MM-Home sddm-helper[1735]: [PAM] Conversation with 1 messages
Feb 14 12:23:18 MM-Home sddm-helper[1735]: pam_unix(sddm:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=  user=marc
Feb 14 12:23:21 MM-Home sddm-helper[1735]: [PAM] authenticate: Authentication failure
Feb 14 12:23:21 MM-Home sddm-helper[1735]: [PAM] returning.
Feb 14 12:23:21 MM-Home sddm[1176]: Authentication error: "Authentication failure"
Feb 14 12:23:21 MM-Home sddm-helper[1735]: [PAM] Ended.
Feb 14 12:23:21 MM-Home sddm[1176]: Auth: sddm-helper exited with 1
Feb 14 12:30:01 MM-Home cron[1742]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 12:30:01 MM-Home systemd[1743]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 12:30:01 MM-Home CRON[1742]: pam_unix(crond:session): session closed for user root
Feb 14 12:30:01 MM-Home systemd[1744]: pam_unix(systemd-user:session): session closed for user root
Feb 14 12:45:01 MM-Home cron[1785]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 12:45:01 MM-Home systemd[1786]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 12:45:01 MM-Home CRON[1785]: pam_unix(crond:session): session closed for user root
Feb 14 12:45:01 MM-Home systemd[1787]: pam_unix(systemd-user:session): session closed for user root
Feb 14 12:48:28 MM-Home sddm[1176]: Message received from greeter: Login
Feb 14 12:48:28 MM-Home sddm[1176]: Reading from "/usr/share/xsessions/plasma5.desktop"
Feb 14 12:48:28 MM-Home sddm[1176]: Session "/usr/share/xsessions/plasma5.desktop" selected, command: "/usr/bin/startkde"
Feb 14 12:48:28 MM-Home sddm-helper[1829]: [PAM] Starting...
Feb 14 12:48:28 MM-Home sddm-helper[1829]: [PAM] Authenticating...
Feb 14 12:48:28 MM-Home sddm-helper[1829]: [PAM] Preparing to converse...
Feb 14 12:48:28 MM-Home sddm-helper[1829]: [PAM] Conversation with 1 messages
Feb 14 12:48:28 MM-Home sddm-helper[1829]: [PAM] returning.
Feb 14 12:48:28 MM-Home sddm[1176]: Authenticated successfully
Feb 14 12:48:28 MM-Home sddm-helper[1829]: pam_unix(sddm:session): session opened for user marc by (uid=0)
Feb 14 12:48:28 MM-Home systemd[1830]: pam_unix(systemd-user:session): session opened for user marc by (uid=0)
Feb 14 12:48:28 MM-Home sddm-helper[1829]: Starting: "/etc/X11/xdm/Xsession" "/usr/bin/startkde"
Feb 14 12:48:28 MM-Home sddm-helper[1832]: Adding cookie to "/home/marc/.Xauthority"
Feb 14 12:48:28 MM-Home sddm[1176]: Session started
Feb 14 12:48:28 MM-Home sddm-helper[1246]: [PAM] Ended.
Feb 14 12:48:28 MM-Home sddm[1176]: Auth: sddm-helper exited successfully
Feb 14 12:48:28 MM-Home sddm[1176]: Greeter stopped.
Feb 14 12:48:32 MM-Home dbus[949]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Feb 14 12:48:32 MM-Home org.kde.powerdevil.backlighthelper[949]: powerdevil: no kernel backlight interface found
Feb 14 12:48:32 MM-Home dbus[949]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Feb 14 12:48:33 MM-Home polkitd[1048]: Registered Authentication Agent for unix-session:5 (system bus name :1.42 [/usr/lib64/libexec/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale de_DE.UTF-8)
Feb 14 12:48:33 MM-Home dbus[949]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service'
Feb 14 12:48:34 MM-Home dbus[949]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Feb 14 12:48:34 MM-Home rtkit-daemon[1997]: Successfully called chroot.
Feb 14 12:48:34 MM-Home rtkit-daemon[1997]: Successfully dropped privileges.
Feb 14 12:48:34 MM-Home rtkit-daemon[1997]: Successfully limited resources.
Feb 14 12:48:34 MM-Home rtkit-daemon[1997]: Running.
Feb 14 12:48:34 MM-Home rtkit-daemon[1997]: Watchdog thread running.
Feb 14 12:48:34 MM-Home rtkit-daemon[1997]: Canary thread running.
Feb 14 12:48:34 MM-Home rtkit-daemon[1997]: Successfully made thread 1996 of process 1996 (/usr/bin/pulseaudio) owned by 'marc' high priority at nice level -11.
Feb 14 12:48:34 MM-Home rtkit-daemon[1997]: Supervising 1 threads of 1 processes of 1 users.
Feb 14 12:48:38 MM-Home rtkit-daemon[1997]: Supervising 1 threads of 1 processes of 1 users.
Feb 14 12:48:38 MM-Home rtkit-daemon[1997]: Successfully made thread 2010 of process 1996 (/usr/bin/pulseaudio) owned by 'marc' RT at priority 5.
Feb 14 12:48:38 MM-Home rtkit-daemon[1997]: Supervising 2 threads of 1 processes of 1 users.
Feb 14 12:48:38 MM-Home rtkit-daemon[1997]: Supervising 2 threads of 1 processes of 1 users.
Feb 14 12:48:38 MM-Home rtkit-daemon[1997]: Successfully made thread 2011 of process 1996 (/usr/bin/pulseaudio) owned by 'marc' RT at priority 5.
Feb 14 12:48:38 MM-Home rtkit-daemon[1997]: Supervising 3 threads of 1 processes of 1 users.
Feb 14 12:48:38 MM-Home rtkit-daemon[1997]: Supervising 3 threads of 1 processes of 1 users.
Feb 14 12:48:38 MM-Home rtkit-daemon[1997]: Successfully made thread 2012 of process 1996 (/usr/bin/pulseaudio) owned by 'marc' RT at priority 5.
Feb 14 12:48:38 MM-Home rtkit-daemon[1997]: Supervising 4 threads of 1 processes of 1 users.
Feb 14 12:48:38 MM-Home dbus[949]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Feb 14 12:48:38 MM-Home rtkit-daemon[1997]: Successfully made thread 2015 of process 2015 (/usr/bin/pulseaudio) owned by 'marc' high priority at nice level -11.
Feb 14 12:48:38 MM-Home rtkit-daemon[1997]: Supervising 5 threads of 2 processes of 1 users.
Feb 14 12:48:38 MM-Home pulseaudio[2015]: [pulseaudio] pid.c: Daemon already running.
Feb 14 12:48:38 MM-Home bluetoothd[2013]: Bluetooth daemon 5.35
Feb 14 12:48:38 MM-Home dbus[949]: [system] Successfully activated service 'org.bluez'
Feb 14 12:48:38 MM-Home bluetoothd[2013]: Starting SDP server
Feb 14 12:48:38 MM-Home kernel: Bluetooth: Core ver 2.20
Feb 14 12:48:38 MM-Home kernel: NET: Registered protocol family 31
Feb 14 12:48:38 MM-Home kernel: Bluetooth: HCI device and connection manager initialized
Feb 14 12:48:38 MM-Home kernel: Bluetooth: HCI socket layer initialized
Feb 14 12:48:38 MM-Home kernel: Bluetooth: L2CAP socket layer initialized
Feb 14 12:48:38 MM-Home kernel: Bluetooth: SCO socket layer initialized
Feb 14 12:48:38 MM-Home dbus[949]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Feb 14 12:48:38 MM-Home bluetoothd[2013]: Bluetooth management interface 1.9 initialized
Feb 14 12:48:38 MM-Home kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Feb 14 12:48:38 MM-Home kernel: Bluetooth: BNEP filters: protocol multicast
Feb 14 12:48:38 MM-Home kernel: Bluetooth: BNEP socket layer initialized
Feb 14 12:48:38 MM-Home dbus[949]: [system] Successfully activated service 'org.freedesktop.hostname1'
Feb 14 12:48:39 MM-Home dbus[949]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service'
Feb 14 12:48:39 MM-Home PackageKit[2029]: daemon start
Feb 14 12:48:40 MM-Home dbus[949]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Feb 14 12:48:41 MM-Home PackageKit[2029]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 12:48:41 MM-Home PackageKit[2029]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 12:48:41 MM-Home PackageKit[2029]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 12:48:41 MM-Home PackageKit[2029]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 12:48:42 MM-Home PackageKit[2029]: refresh-cache transaction /1_edcaddaa from uid 1000 finished with failed after 1290ms
Feb 14 12:48:42 MM-Home PackageKit[2029]: refresh-cache transaction /2_cebeebce from uid 1000 finished with failed after 282ms
Feb 14 12:49:00 MM-Home PackageKit[2029]: daemon quit
Feb 14 12:49:00 MM-Home packagekitd[2029]: (packagekitd:2029): GLib-CRITICAL **: Source ID 6 was not found when attempting to remove it
Feb 14 12:49:20 MM-Home dbus[949]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service'
Feb 14 12:49:20 MM-Home PackageKit[2066]: daemon start
Feb 14 12:49:20 MM-Home dbus[949]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Feb 14 12:49:20 MM-Home PackageKit[2066]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 12:49:20 MM-Home PackageKit[2066]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 12:49:20 MM-Home PackageKit[2066]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 12:49:20 MM-Home PackageKit[2066]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 12:49:21 MM-Home PackageKit[2066]: refresh-cache transaction /1_abbbeacc from uid 1000 finished with failed after 304ms
Feb 14 12:49:21 MM-Home PackageKit[2066]: refresh-cache transaction /2_ddabaadb from uid 1000 finished with failed after 313ms
Feb 14 12:49:41 MM-Home PackageKit[2066]: daemon quit
Feb 14 12:49:41 MM-Home packagekitd[2066]: (packagekitd:2066): GLib-CRITICAL **: Source ID 6 was not found when attempting to remove it
Feb 14 12:49:44 MM-Home dbus[949]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service'
Feb 14 12:49:44 MM-Home PackageKit[2093]: daemon start
Feb 14 12:49:44 MM-Home dbus[949]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Feb 14 12:49:45 MM-Home PackageKit[2093]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 12:49:45 MM-Home PackageKit[2093]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 12:49:45 MM-Home PackageKit[2093]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 12:49:45 MM-Home PackageKit[2093]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 12:49:45 MM-Home PackageKit[2093]: refresh-cache transaction /1_cadcbeee from uid 1000 finished with failed after 306ms
Feb 14 12:49:45 MM-Home PackageKit[2093]: refresh-cache transaction /2_bebbbaac from uid 1000 finished with failed after 286ms
Feb 14 12:50:03 MM-Home kernel: fuse init (API version 7.23)
Feb 14 12:50:05 MM-Home PackageKit[2093]: daemon quit
Feb 14 12:50:05 MM-Home packagekitd[2093]: (packagekitd:2093): GLib-CRITICAL **: Source ID 6 was not found when attempting to remove it
Feb 14 13:00:01 MM-Home cron[2358]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 13:00:01 MM-Home systemd[2359]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 13:00:01 MM-Home CRON[2358]: pam_unix(crond:session): session closed for user root
Feb 14 13:00:01 MM-Home systemd[2360]: pam_unix(systemd-user:session): session closed for user root
Feb 14 13:11:48 MM-Home su[2473]: (to root) marc on pts/1
Feb 14 13:11:48 MM-Home su[2473]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 13:11:48 MM-Home su[2473]: pam_unix(su:session): session closed for user root
Feb 14 13:11:48 MM-Home su[2478]: (to root) marc on pts/1
Feb 14 13:11:48 MM-Home su[2478]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 13:11:55 MM-Home dbus[949]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Feb 14 13:11:55 MM-Home dbus[949]: [system] Successfully activated service 'org.opensuse.Snapper'
Feb 14 13:12:05 MM-Home kernel: st: Version 20101219, fixed bufsize 32768, s/g segs 256
Feb 14 13:12:05 MM-Home kernel: BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Feb 14 13:12:05 MM-Home kernel: EDD information not available.
Feb 14 13:12:12 MM-Home kernel: BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Feb 14 13:12:12 MM-Home kernel: EDD information not available.
Feb 14 13:12:17 MM-Home kernel: ppdev: user-space parallel port driver
Feb 14 13:12:17 MM-Home kernel: lp: driver loaded but no devices found
Feb 14 13:12:17 MM-Home kernel: lp: driver loaded but no devices found
Feb 14 13:12:18 MM-Home kernel: lp: driver loaded but no devices found
Feb 14 13:12:20 MM-Home kernel: BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Feb 14 13:12:20 MM-Home kernel: EDD information not available.
Feb 14 13:12:21 MM-Home kernel: BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Feb 14 13:12:21 MM-Home kernel: EDD information not available.
Feb 14 13:15:01 MM-Home cron[3433]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 13:15:01 MM-Home systemd[3434]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 13:15:01 MM-Home CRON[3433]: pam_unix(crond:session): session closed for user root
Feb 14 13:15:01 MM-Home systemd[3435]: pam_unix(systemd-user:session): session closed for user root
Feb 14 13:16:41 MM-Home dbus[949]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Feb 14 13:16:41 MM-Home dbus[949]: [system] Successfully activated service 'org.opensuse.Snapper'
Feb 14 13:16:53 MM-Home kernel: device-mapper: uevent: version 1.0.3
Feb 14 13:16:53 MM-Home kernel: device-mapper: ioctl: 4.31.0-ioctl (2015-3-12) initialised: dm-devel@redhat.com
Feb 14 13:16:55 MM-Home kernel: BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Feb 14 13:16:55 MM-Home kernel: EDD information not available.
Feb 14 13:18:03 MM-Home su[2478]: pam_unix(su:session): session closed for user root
Feb 14 13:18:54 MM-Home kernel: nouveau E[   PFIFO][0000:02:00.0] read fault at 0x0003914000 [PTE] from GR/GPC2/T1_0 on channel 0x007fa1a000 [X[1226]]
Feb 14 13:18:54 MM-Home kernel: nouveau E[   PFIFO][0000:02:00.0] PGRAPH engine fault on channel 2, recovering...
Feb 14 13:18:54 MM-Home kernel: nouveau E[  PGRAPH][0000:02:00.0] TRAP ch 2 [0x007fa1a000 X[1226]]
Feb 14 13:18:54 MM-Home kernel: nouveau E[  PGRAPH][0000:02:00.0] GPC0/TPC0/TEX: 0x80000049
Feb 14 13:18:54 MM-Home kernel: nouveau E[  PGRAPH][0000:02:00.0] GPC1/TPC0/TEX: 0x80000049
Feb 14 13:18:54 MM-Home kernel: nouveau E[  PGRAPH][0000:02:00.0] GPC1/TPC1/TEX: 0x80000049
Feb 14 13:18:54 MM-Home kernel: nouveau E[  PGRAPH][0000:02:00.0] GPC2/TPC0/TEX: 0x80000049
Feb 14 13:18:54 MM-Home kernel: nouveau E[  PGRAPH][0000:02:00.0] GPC2/TPC1/TEX: 0x80000049
Feb 14 13:18:54 MM-Home kernel: nouveau E[  PGRAPH][0000:02:00.0] GPC3/TPC0/TEX: 0x80000049
Feb 14 13:18:54 MM-Home kernel: nouveau E[  PGRAPH][0000:02:00.0] GPC3/TPC1/TEX: 0x80000049
Feb 14 13:18:54 MM-Home kernel: nouveau E[   PFIFO][0000:02:00.0] read fault at 0x0000013000 [PDE] from PBDMA0/HOST_CPU on channel 0x007f5b5000 [unknown]
-- Reboot --
Feb 14 13:19:52 linux-ytaf systemd-journal[187]: Runtime journal is using 8.0M (max allowed 394.0M, trying to leave 591.0M free of 3.8G available → current limit 394.0M).
Feb 14 13:19:52 linux-ytaf systemd-journal[187]: Runtime journal is using 8.0M (max allowed 394.0M, trying to leave 591.0M free of 3.8G available → current limit 394.0M).
Feb 14 13:19:52 linux-ytaf kernel: microcode: CPU0 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 13:19:52 linux-ytaf kernel: Initializing cgroup subsys cpuset
Feb 14 13:19:52 linux-ytaf kernel: Initializing cgroup subsys cpu
Feb 14 13:19:52 linux-ytaf kernel: Initializing cgroup subsys cpuacct
Feb 14 13:19:52 linux-ytaf kernel: Linux version 4.1.15-8-default (geeko@buildhost) (gcc version 4.8.5 (SUSE Linux) ) #1 SMP PREEMPT Wed Jan 20 16:41:00 UTC 2016 (0e3b3ab)
Feb 14 13:19:52 linux-ytaf kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.1.15-8-default root=UUID=21024970-7a27-4114-8525-d8dd026f23b6 ro resume=/dev/sdb2 splash=silent quiet showopts
Feb 14 13:19:52 linux-ytaf kernel: e820: BIOS-provided physical RAM map:
Feb 14 13:19:52 linux-ytaf kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Feb 14 13:19:52 linux-ytaf kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
Feb 14 13:19:52 linux-ytaf kernel: BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable
Feb 14 13:19:52 linux-ytaf kernel: BIOS-e820: [mem 0x0000000020000000-0x00000000201fffff] reserved
Feb 14 13:19:52 linux-ytaf kernel: BIOS-e820: [mem 0x0000000020200000-0x000000003fffffff] usable
Feb 14 13:19:52 linux-ytaf kernel: BIOS-e820: [mem 0x0000000040000000-0x00000000401fffff] reserved
Feb 14 13:19:52 linux-ytaf kernel: BIOS-e820: [mem 0x0000000040200000-0x00000000ca38efff] usable
Feb 14 13:19:52 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ca38f000-0x00000000ca5f1fff] reserved
Feb 14 13:19:52 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ca5f2000-0x00000000ca679fff] ACPI NVS
Feb 14 13:19:52 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ca67a000-0x00000000ca93efff] reserved
Feb 14 13:19:52 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ca93f000-0x00000000cab83fff] ACPI NVS
Feb 14 13:19:52 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cab84000-0x00000000cab91fff] ACPI data
Feb 14 13:19:52 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cab92000-0x00000000cabbefff] ACPI NVS
Feb 14 13:19:52 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cabbf000-0x00000000cabc3fff] ACPI data
Feb 14 13:19:52 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cabc4000-0x00000000cac06fff] ACPI NVS
Feb 14 13:19:52 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cac07000-0x00000000caffffff] usable
Feb 14 13:19:52 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cb800000-0x00000000cf9fffff] reserved
Feb 14 13:19:52 linux-ytaf kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Feb 14 13:19:52 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Feb 14 13:19:52 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Feb 14 13:19:52 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Feb 14 13:19:52 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Feb 14 13:19:52 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Feb 14 13:19:52 linux-ytaf kernel: BIOS-e820: [mem 0x0000000100000000-0x000000022f5fffff] usable
Feb 14 13:19:52 linux-ytaf kernel: NX (Execute Disable) protection: active
Feb 14 13:19:52 linux-ytaf kernel: e820: update [mem 0x0c826018-0x0c835c57] usable ==> usable
Feb 14 13:19:52 linux-ytaf kernel: e820: update [mem 0x0c836018-0x0c846057] usable ==> usable
Feb 14 13:19:52 linux-ytaf kernel: e820: update [mem 0x0c847018-0x0c856857] usable ==> usable
Feb 14 13:19:52 linux-ytaf kernel: e820: update [mem 0x0c857018-0x0c85ae57] usable ==> usable
Feb 14 13:19:52 linux-ytaf kernel: extended physical RAM map:
Feb 14 13:19:52 linux-ytaf kernel: reserve setup_data: [mem 0x0000000000000000-0x000000000009efff] usable
Feb 14 13:19:52 linux-ytaf kernel: reserve setup_data: [mem 0x000000000009f000-0x000000000009ffff] reserved
Feb 14 13:19:52 linux-ytaf kernel: reserve setup_data: [mem 0x0000000000100000-0x000000000c826017] usable
Feb 14 13:19:52 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c826018-0x000000000c835c57] usable
Feb 14 13:19:52 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c835c58-0x000000000c836017] usable
Feb 14 13:19:52 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c836018-0x000000000c846057] usable
Feb 14 13:19:52 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c846058-0x000000000c847017] usable
Feb 14 13:19:52 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c847018-0x000000000c856857] usable
Feb 14 13:19:52 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c856858-0x000000000c857017] usable
Feb 14 13:19:52 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c857018-0x000000000c85ae57] usable
Feb 14 13:19:52 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c85ae58-0x000000001fffffff] usable
Feb 14 13:19:52 linux-ytaf kernel: reserve setup_data: [mem 0x0000000020000000-0x00000000201fffff] reserved
Feb 14 13:19:52 linux-ytaf kernel: reserve setup_data: [mem 0x0000000020200000-0x000000003fffffff] usable
Feb 14 13:19:52 linux-ytaf kernel: reserve setup_data: [mem 0x0000000040000000-0x00000000401fffff] reserved
Feb 14 13:19:52 linux-ytaf kernel: reserve setup_data: [mem 0x0000000040200000-0x00000000ca38efff] usable
Feb 14 13:19:52 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ca38f000-0x00000000ca5f1fff] reserved
Feb 14 13:19:52 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ca5f2000-0x00000000ca679fff] ACPI NVS
Feb 14 13:19:52 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ca67a000-0x00000000ca93efff] reserved
Feb 14 13:19:52 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ca93f000-0x00000000cab83fff] ACPI NVS
Feb 14 13:19:52 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cab84000-0x00000000cab91fff] ACPI data
Feb 14 13:19:52 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cab92000-0x00000000cabbefff] ACPI NVS
Feb 14 13:19:52 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cabbf000-0x00000000cabc3fff] ACPI data
Feb 14 13:19:52 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cabc4000-0x00000000cac06fff] ACPI NVS
Feb 14 13:19:52 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cac07000-0x00000000caffffff] usable
Feb 14 13:19:52 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cb800000-0x00000000cf9fffff] reserved
Feb 14 13:19:52 linux-ytaf kernel: reserve setup_data: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Feb 14 13:19:52 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Feb 14 13:19:52 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Feb 14 13:19:52 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Feb 14 13:19:52 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Feb 14 13:19:52 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Feb 14 13:19:52 linux-ytaf kernel: reserve setup_data: [mem 0x0000000100000000-0x000000022f5fffff] usable
Feb 14 13:19:52 linux-ytaf kernel: efi: EFI v2.31 by American Megatrends
Feb 14 13:19:52 linux-ytaf kernel: efi:  ACPI=0xcab84000  ACPI 2.0=0xcab84000  SMBIOS=0xca427e98  MPS=0xfc990 
Feb 14 13:19:52 linux-ytaf kernel: SMBIOS 2.6 present.
Feb 14 13:19:52 linux-ytaf kernel: DMI: System manufacturer System Product Name/MAXIMUS IV GENE-Z/GEN3, BIOS 3603 11/09/2012
Feb 14 13:19:52 linux-ytaf kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Feb 14 13:19:52 linux-ytaf kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Feb 14 13:19:52 linux-ytaf kernel: AGP: No AGP bridge found
Feb 14 13:19:52 linux-ytaf kernel: e820: last_pfn = 0x22f600 max_arch_pfn = 0x400000000
Feb 14 13:19:52 linux-ytaf kernel: MTRR default type: uncachable
Feb 14 13:19:52 linux-ytaf kernel: MTRR fixed ranges enabled:
Feb 14 13:19:52 linux-ytaf kernel:   00000-9FFFF write-back
Feb 14 13:19:52 linux-ytaf kernel:   A0000-BFFFF uncachable
Feb 14 13:19:52 linux-ytaf kernel:   C0000-D3FFF write-protect
Feb 14 13:19:52 linux-ytaf kernel:   D4000-DFFFF uncachable
Feb 14 13:19:52 linux-ytaf kernel:   E0000-E7FFF write-through
Feb 14 13:19:52 linux-ytaf kernel:   E8000-FFFFF write-protect
Feb 14 13:19:52 linux-ytaf kernel: MTRR variable ranges enabled:
Feb 14 13:19:52 linux-ytaf kernel:   0 base 000000000 mask E00000000 write-back
Feb 14 13:19:52 linux-ytaf kernel:   1 base 200000000 mask FE0000000 write-back
Feb 14 13:19:52 linux-ytaf kernel:   2 base 220000000 mask FF0000000 write-back
Feb 14 13:19:52 linux-ytaf kernel:   3 base 0E0000000 mask FE0000000 uncachable
Feb 14 13:19:52 linux-ytaf kernel:   4 base 0D0000000 mask FF0000000 uncachable
Feb 14 13:19:52 linux-ytaf kernel:   5 base 0CC000000 mask FFC000000 uncachable
Feb 14 13:19:52 linux-ytaf kernel:   6 base 0CB800000 mask FFF800000 uncachable
Feb 14 13:19:52 linux-ytaf kernel:   7 base 22F800000 mask FFF800000 uncachable
Feb 14 13:19:52 linux-ytaf kernel:   8 base 22F600000 mask FFFE00000 uncachable
Feb 14 13:19:52 linux-ytaf kernel:   9 disabled
Feb 14 13:19:52 linux-ytaf kernel: PAT configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- UC  
Feb 14 13:19:52 linux-ytaf kernel: e820: update [mem 0xcb800000-0xffffffff] usable ==> reserved
Feb 14 13:19:52 linux-ytaf kernel: e820: last_pfn = 0xcb000 max_arch_pfn = 0x400000000
Feb 14 13:19:52 linux-ytaf kernel: found SMP MP-table at [mem 0x000fcd30-0x000fcd3f] mapped at [ffff8800000fcd30]
Feb 14 13:19:52 linux-ytaf kernel: Scanning 1 areas for low memory corruption
Feb 14 13:19:52 linux-ytaf kernel: Base memory trampoline at [ffff880000097000] 97000 size 24576
Feb 14 13:19:52 linux-ytaf kernel: reserving inaccessible SNB gfx pages
Feb 14 13:19:52 linux-ytaf kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
Feb 14 13:19:52 linux-ytaf kernel:  [mem 0x00000000-0x000fffff] page 4k
Feb 14 13:19:52 linux-ytaf kernel: BRK [0x0e21a000, 0x0e21afff] PGTABLE
Feb 14 13:19:52 linux-ytaf kernel: BRK [0x0e21b000, 0x0e21bfff] PGTABLE
Feb 14 13:19:52 linux-ytaf kernel: BRK [0x0e21c000, 0x0e21cfff] PGTABLE
Feb 14 13:19:52 linux-ytaf kernel: init_memory_mapping: [mem 0x22f400000-0x22f5fffff]
Feb 14 13:19:52 linux-ytaf kernel:  [mem 0x22f400000-0x22f5fffff] page 2M
Feb 14 13:19:52 linux-ytaf kernel: BRK [0x0e21d000, 0x0e21dfff] PGTABLE
Feb 14 13:19:52 linux-ytaf kernel: init_memory_mapping: [mem 0x220000000-0x22f3fffff]
Feb 14 13:19:52 linux-ytaf kernel:  [mem 0x220000000-0x22f3fffff] page 2M
Feb 14 13:19:52 linux-ytaf kernel: init_memory_mapping: [mem 0x200000000-0x21fffffff]
Feb 14 13:19:52 linux-ytaf kernel:  [mem 0x200000000-0x21fffffff] page 2M
Feb 14 13:19:52 linux-ytaf kernel: init_memory_mapping: [mem 0x00100000-0x1fffffff]
Feb 14 13:19:52 linux-ytaf kernel:  [mem 0x00100000-0x001fffff] page 4k
Feb 14 13:19:52 linux-ytaf kernel:  [mem 0x00200000-0x1fffffff] page 2M
Feb 14 13:19:52 linux-ytaf kernel: init_memory_mapping: [mem 0x20200000-0x3fffffff]
Feb 14 13:19:52 linux-ytaf kernel:  [mem 0x20200000-0x3fffffff] page 2M
Feb 14 13:19:52 linux-ytaf kernel: init_memory_mapping: [mem 0x40200000-0xca38efff]
Feb 14 13:19:52 linux-ytaf kernel:  [mem 0x40200000-0xca1fffff] page 2M
Feb 14 13:19:52 linux-ytaf kernel:  [mem 0xca200000-0xca38efff] page 4k
Feb 14 13:19:52 linux-ytaf kernel: BRK [0x0e21e000, 0x0e21efff] PGTABLE
Feb 14 13:19:52 linux-ytaf kernel: BRK [0x0e21f000, 0x0e21ffff] PGTABLE
Feb 14 13:19:52 linux-ytaf kernel: init_memory_mapping: [mem 0xcac07000-0xcaffffff]
Feb 14 13:19:52 linux-ytaf kernel:  [mem 0xcac07000-0xcadfffff] page 4k
Feb 14 13:19:52 linux-ytaf kernel:  [mem 0xcae00000-0xcaffffff] page 2M
Feb 14 13:19:52 linux-ytaf kernel: init_memory_mapping: [mem 0x100000000-0x1ffffffff]
Feb 14 13:19:52 linux-ytaf kernel:  [mem 0x100000000-0x1ffffffff] page 2M
Feb 14 13:19:52 linux-ytaf kernel: RAMDISK: [mem 0x00457000-0x00ffafff]
Feb 14 13:19:52 linux-ytaf kernel: ACPI: Early table checksum verification disabled
Feb 14 13:19:52 linux-ytaf kernel: ACPI: RSDP 0x00000000CAB84000 000024 (v02 ALASKA)
Feb 14 13:19:52 linux-ytaf kernel: ACPI: XSDT 0x00000000CAB84078 000064 (v01 ALASKA A M I    01072009 AMI  00010013)
Feb 14 13:19:52 linux-ytaf kernel: ACPI: FACP 0x00000000CAB8FC78 0000F4 (v04 ALASKA A M I    01072009 AMI  00010013)
Feb 14 13:19:52 linux-ytaf kernel: ACPI: DSDT 0x00000000CAB84170 00BB02 (v02 ALASKA A M I    00000015 INTL 20051117)
Feb 14 13:19:52 linux-ytaf kernel: ACPI: FACS 0x00000000CABBDF80 000040
Feb 14 13:19:52 linux-ytaf kernel: ACPI: APIC 0x00000000CAB8FD70 000092 (v03 ALASKA A M I    01072009 AMI  00010013)
Feb 14 13:19:52 linux-ytaf kernel: ACPI: MCFG 0x00000000CAB8FE08 00003C (v01 ALASKA A M I    01072009 MSFT 00000097)
Feb 14 13:19:52 linux-ytaf kernel: ACPI: HPET 0x00000000CAB8FE48 000038 (v01 ALASKA A M I    01072009 AMI. 00000005)
Feb 14 13:19:52 linux-ytaf kernel: ACPI: SSDT 0x00000000CAB8FE80 00036D (v01 SataRe SataTabl 00001000 INTL 20091112)
Feb 14 13:19:52 linux-ytaf kernel: ACPI: SSDT 0x00000000CAB901F0 0009AA (v01 PmRef  Cpu0Ist  00003000 INTL 20051117)
Feb 14 13:19:52 linux-ytaf kernel: ACPI: SSDT 0x00000000CAB90BA0 000A92 (v01 PmRef  CpuPm    00003000 INTL 20051117)
Feb 14 13:19:52 linux-ytaf kernel: ACPI: BGRT 0x00000000CAB91690 000038 (v00 ALASKA A M I    01072009 AMI  00010013)
Feb 14 13:19:52 linux-ytaf kernel: ACPI: Local APIC address 0xfee00000
Feb 14 13:19:52 linux-ytaf kernel: No NUMA configuration found
Feb 14 13:19:52 linux-ytaf kernel: Faking a node at [mem 0x0000000000000000-0x000000022f5fffff]
Feb 14 13:19:52 linux-ytaf kernel: NODE_DATA(0) allocated [mem 0x22f5e5000-0x22f5f8fff]
Feb 14 13:19:52 linux-ytaf kernel:  [ffffea0000000000-ffffea0008bfffff] PMD -> [ffff880226c00000-ffff88022ebfffff] on node 0
Feb 14 13:19:52 linux-ytaf kernel: Zone ranges:
Feb 14 13:19:52 linux-ytaf kernel:   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
Feb 14 13:19:52 linux-ytaf kernel:   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
Feb 14 13:19:52 linux-ytaf kernel:   Normal   [mem 0x0000000100000000-0x000000022f5fffff]
Feb 14 13:19:52 linux-ytaf kernel: Movable zone start for each node
Feb 14 13:19:52 linux-ytaf kernel: Early memory node ranges
Feb 14 13:19:52 linux-ytaf kernel:   node   0: [mem 0x0000000000001000-0x000000000009efff]
Feb 14 13:19:52 linux-ytaf kernel:   node   0: [mem 0x0000000000100000-0x000000001fffffff]
Feb 14 13:19:52 linux-ytaf kernel:   node   0: [mem 0x0000000020200000-0x000000003fffffff]
Feb 14 13:19:52 linux-ytaf kernel:   node   0: [mem 0x0000000040200000-0x00000000ca38efff]
Feb 14 13:19:52 linux-ytaf kernel:   node   0: [mem 0x00000000cac07000-0x00000000caffffff]
Feb 14 13:19:52 linux-ytaf kernel:   node   0: [mem 0x0000000100000000-0x000000022f5fffff]
Feb 14 13:19:52 linux-ytaf kernel: Initmem setup node 0 [mem 0x0000000000001000-0x000000022f5fffff]
Feb 14 13:19:52 linux-ytaf kernel: On node 0 totalpages: 2070822
Feb 14 13:19:52 linux-ytaf kernel:   DMA zone: 64 pages used for memmap
Feb 14 13:19:52 linux-ytaf kernel:   DMA zone: 3138 pages reserved
Feb 14 13:19:52 linux-ytaf kernel:   DMA zone: 3998 pages, LIFO batch:0
Feb 14 13:19:52 linux-ytaf kernel:   DMA32 zone: 12879 pages used for memmap
Feb 14 13:19:52 linux-ytaf kernel:   DMA32 zone: 824200 pages, LIFO batch:31
Feb 14 13:19:52 linux-ytaf kernel:   Normal zone: 19416 pages used for memmap
Feb 14 13:19:52 linux-ytaf kernel:   Normal zone: 1242624 pages, LIFO batch:31
Feb 14 13:19:52 linux-ytaf kernel: tboot: non-0 tboot_addr but it is not of type E820_RESERVED
Feb 14 13:19:52 linux-ytaf kernel: ACPI: PM-Timer IO Port: 0x408
Feb 14 13:19:52 linux-ytaf kernel: ACPI: Local APIC address 0xfee00000
Feb 14 13:19:52 linux-ytaf kernel: ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
Feb 14 13:19:52 linux-ytaf kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
Feb 14 13:19:52 linux-ytaf kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Feb 14 13:19:52 linux-ytaf kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Feb 14 13:19:52 linux-ytaf kernel: ACPI: IRQ0 used by override.
Feb 14 13:19:52 linux-ytaf kernel: ACPI: IRQ9 used by override.
Feb 14 13:19:52 linux-ytaf kernel: Using ACPI (MADT) for SMP configuration information
Feb 14 13:19:52 linux-ytaf kernel: ACPI: HPET id: 0x8086a701 base: 0xfed00000
Feb 14 13:19:52 linux-ytaf kernel: smpboot: Allowing 8 CPUs, 0 hotplug CPUs
Feb 14 13:19:52 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
Feb 14 13:19:52 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Feb 14 13:19:52 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000fffff]
Feb 14 13:19:52 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c826000-0x0c826fff]
Feb 14 13:19:52 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c835000-0x0c835fff]
Feb 14 13:19:52 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c836000-0x0c836fff]
Feb 14 13:19:52 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c846000-0x0c846fff]
Feb 14 13:19:52 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c847000-0x0c847fff]
Feb 14 13:19:52 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c856000-0x0c856fff]
Feb 14 13:19:52 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c857000-0x0c857fff]
Feb 14 13:19:52 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c85a000-0x0c85afff]
Feb 14 13:19:52 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x20000000-0x201fffff]
Feb 14 13:19:52 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x40000000-0x401fffff]
Feb 14 13:19:52 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xca38f000-0xca5f1fff]
Feb 14 13:19:52 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xca5f2000-0xca679fff]
Feb 14 13:19:52 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xca67a000-0xca93efff]
Feb 14 13:19:52 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xca93f000-0xcab83fff]
Feb 14 13:19:52 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcab84000-0xcab91fff]
Feb 14 13:19:52 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcab92000-0xcabbefff]
Feb 14 13:19:52 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcabbf000-0xcabc3fff]
Feb 14 13:19:52 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcabc4000-0xcac06fff]
Feb 14 13:19:52 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcb000000-0xcb7fffff]
Feb 14 13:19:52 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcb800000-0xcf9fffff]
Feb 14 13:19:52 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcfa00000-0xf7ffffff]
Feb 14 13:19:52 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
Feb 14 13:19:52 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfc000000-0xfebfffff]
Feb 14 13:19:52 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
Feb 14 13:19:52 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfec01000-0xfecfffff]
Feb 14 13:19:52 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed00000-0xfed03fff]
Feb 14 13:19:52 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed04000-0xfed1bfff]
Feb 14 13:19:52 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Feb 14 13:19:52 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed20000-0xfedfffff]
Feb 14 13:19:52 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
Feb 14 13:19:52 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfee01000-0xfeffffff]
Feb 14 13:19:52 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Feb 14 13:19:52 linux-ytaf kernel: e820: [mem 0xcfa00000-0xf7ffffff] available for PCI devices
Feb 14 13:19:52 linux-ytaf kernel: Booting paravirtualized kernel on bare hardware
Feb 14 13:19:52 linux-ytaf kernel: clocksource refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
Feb 14 13:19:52 linux-ytaf kernel: setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:8 nr_node_ids:1
Feb 14 13:19:52 linux-ytaf kernel: PERCPU: Embedded 33 pages/cpu @ffff88022f200000 s97368 r8192 d29608 u262144
Feb 14 13:19:52 linux-ytaf kernel: pcpu-alloc: s97368 r8192 d29608 u262144 alloc=1*2097152
Feb 14 13:19:52 linux-ytaf kernel: pcpu-alloc: [0] 0 1 2 3 4 5 6 7 
Feb 14 13:19:52 linux-ytaf kernel: Built 1 zonelists in Node order, mobility grouping on.  Total pages: 2035325
Feb 14 13:19:52 linux-ytaf kernel: Policy zone: Normal
Feb 14 13:19:52 linux-ytaf kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.1.15-8-default root=UUID=21024970-7a27-4114-8525-d8dd026f23b6 ro resume=/dev/sdb2 splash=silent quiet showopts
Feb 14 13:19:52 linux-ytaf kernel: log_buf_len individual max cpu contribution: 32768 bytes
Feb 14 13:19:52 linux-ytaf kernel: log_buf_len total cpu_extra contributions: 229376 bytes
Feb 14 13:19:52 linux-ytaf kernel: log_buf_len min size: 262144 bytes
Feb 14 13:19:52 linux-ytaf kernel: log_buf_len: 524288 bytes
Feb 14 13:19:52 linux-ytaf kernel: early log buf free: 245492(93%)
Feb 14 13:19:52 linux-ytaf kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
Feb 14 13:19:52 linux-ytaf kernel: xsave: enabled xstate_bv 0x7, cntxt size 0x340 using standard form
Feb 14 13:19:52 linux-ytaf kernel: AGP: Checking aperture...
Feb 14 13:19:52 linux-ytaf kernel: AGP: No AGP bridge found
Feb 14 13:19:52 linux-ytaf kernel: Memory: 7863196K/8283288K available (6547K kernel code, 1084K rwdata, 4848K rodata, 1560K init, 1516K bss, 420092K reserved, 0K cma-reserved)
Feb 14 13:19:52 linux-ytaf kernel: Preemptible hierarchical RCU implementation.
Feb 14 13:19:52 linux-ytaf kernel:         RCU dyntick-idle grace-period acceleration is enabled.
Feb 14 13:19:52 linux-ytaf kernel:         RCU restricting CPUs from NR_CPUS=512 to nr_cpu_ids=8.
Feb 14 13:19:52 linux-ytaf kernel: RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
Feb 14 13:19:52 linux-ytaf kernel: NR_IRQS:33024 nr_irqs:488 16
Feb 14 13:19:52 linux-ytaf kernel:         Offload RCU callbacks from all CPUs
Feb 14 13:19:52 linux-ytaf kernel:         Offload RCU callbacks from CPUs: 0-7.
Feb 14 13:19:52 linux-ytaf kernel: Console: colour dummy device 80x25
Feb 14 13:19:52 linux-ytaf kernel: console [tty0] enabled
Feb 14 13:19:52 linux-ytaf kernel: clocksource hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484882848 ns
Feb 14 13:19:52 linux-ytaf kernel: hpet clockevent registered
Feb 14 13:19:52 linux-ytaf kernel: tsc: Fast TSC calibration using PIT
Feb 14 13:19:52 linux-ytaf kernel: tsc: Detected 3411.231 MHz processor
Feb 14 13:19:52 linux-ytaf kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 6822.46 BogoMIPS (lpj=13644924)
Feb 14 13:19:52 linux-ytaf kernel: pid_max: default: 32768 minimum: 301
Feb 14 13:19:52 linux-ytaf kernel: ACPI: Core revision 20150410
Feb 14 13:19:52 linux-ytaf kernel: ACPI: All ACPI Tables successfully acquired
Feb 14 13:19:52 linux-ytaf kernel: Security Framework initialized
Feb 14 13:19:52 linux-ytaf kernel: AppArmor: AppArmor initialized
Feb 14 13:19:52 linux-ytaf kernel: Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
Feb 14 13:19:52 linux-ytaf kernel: Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
Feb 14 13:19:52 linux-ytaf kernel: Mount-cache hash table entries: 16384 (order: 5, 131072 bytes)
Feb 14 13:19:52 linux-ytaf kernel: Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes)
Feb 14 13:19:52 linux-ytaf kernel: Initializing cgroup subsys blkio
Feb 14 13:19:52 linux-ytaf kernel: Initializing cgroup subsys memory
Feb 14 13:19:52 linux-ytaf kernel: Initializing cgroup subsys devices
Feb 14 13:19:52 linux-ytaf kernel: Initializing cgroup subsys freezer
Feb 14 13:19:52 linux-ytaf kernel: Initializing cgroup subsys net_cls
Feb 14 13:19:52 linux-ytaf kernel: Initializing cgroup subsys perf_event
Feb 14 13:19:52 linux-ytaf kernel: Initializing cgroup subsys net_prio
Feb 14 13:19:52 linux-ytaf kernel: Initializing cgroup subsys hugetlb
Feb 14 13:19:52 linux-ytaf kernel: CPU: Physical Processor ID: 0
Feb 14 13:19:52 linux-ytaf kernel: CPU: Processor Core ID: 0
Feb 14 13:19:52 linux-ytaf kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Feb 14 13:19:52 linux-ytaf kernel: ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Feb 14 13:19:52 linux-ytaf kernel: mce: CPU supports 9 MCE banks
Feb 14 13:19:52 linux-ytaf kernel: CPU0: Thermal monitoring enabled (TM1)
Feb 14 13:19:52 linux-ytaf kernel: process: using mwait in idle threads
Feb 14 13:19:52 linux-ytaf kernel: Last level iTLB entries: 4KB 512, 2MB 8, 4MB 8
Feb 14 13:19:52 linux-ytaf kernel: Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32, 1GB 0
Feb 14 13:19:52 linux-ytaf kernel: Freeing SMP alternatives memory: 24K (ffffffff82097000 - ffffffff8209d000)
Feb 14 13:19:52 linux-ytaf kernel: ftrace: allocating 25000 entries in 98 pages
Feb 14 13:19:52 linux-ytaf kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Feb 14 13:19:52 linux-ytaf kernel: TSC deadline timer enabled
Feb 14 13:19:52 linux-ytaf kernel: smpboot: CPU0: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz (fam: 06, model: 2a, stepping: 07)
Feb 14 13:19:52 linux-ytaf kernel: Performance Events: PEBS fmt1+, 16-deep LBR, SandyBridge events, full-width counters, Intel PMU driver.
Feb 14 13:19:52 linux-ytaf kernel: ... version:                3
Feb 14 13:19:52 linux-ytaf kernel: ... bit width:              48
Feb 14 13:19:52 linux-ytaf kernel: ... generic registers:      4
Feb 14 13:19:52 linux-ytaf kernel: ... value mask:             0000ffffffffffff
Feb 14 13:19:52 linux-ytaf kernel: ... max period:             0000ffffffffffff
Feb 14 13:19:52 linux-ytaf kernel: ... fixed-purpose events:   3
Feb 14 13:19:52 linux-ytaf kernel: ... event mask:             000000070000000f
Feb 14 13:19:52 linux-ytaf kernel: x86: Booting SMP configuration:
Feb 14 13:19:52 linux-ytaf kernel: .... node  #0, CPUs:      #1
Feb 14 13:19:52 linux-ytaf kernel: microcode: CPU1 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 13:19:52 linux-ytaf kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Feb 14 13:19:52 linux-ytaf kernel:  #2
Feb 14 13:19:52 linux-ytaf kernel: microcode: CPU2 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 13:19:52 linux-ytaf kernel:  #3
Feb 14 13:19:52 linux-ytaf kernel: microcode: CPU3 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 13:19:52 linux-ytaf kernel:  #4 #5 #6 #7
Feb 14 13:19:52 linux-ytaf kernel: x86: Booted up 1 node, 8 CPUs
Feb 14 13:19:52 linux-ytaf kernel: smpboot: Total of 8 processors activated (54579.69 BogoMIPS)
Feb 14 13:19:52 linux-ytaf kernel: devtmpfs: initialized
Feb 14 13:19:52 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xca5f2000-0xca679fff] (557056 bytes)
Feb 14 13:19:52 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xca93f000-0xcab83fff] (2379776 bytes)
Feb 14 13:19:52 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xcab92000-0xcabbefff] (184320 bytes)
Feb 14 13:19:52 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xcabc4000-0xcac06fff] (274432 bytes)
Feb 14 13:19:52 linux-ytaf kernel: clocksource jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
Feb 14 13:19:52 linux-ytaf kernel: pinctrl core: initialized pinctrl subsystem
Feb 14 13:19:52 linux-ytaf kernel: RTC time: 13:19:49, date: 02/14/16
Feb 14 13:19:52 linux-ytaf kernel: NET: Registered protocol family 16
Feb 14 13:19:52 linux-ytaf kernel: cpuidle: using governor ladder
Feb 14 13:19:52 linux-ytaf kernel: cpuidle: using governor menu
Feb 14 13:19:52 linux-ytaf kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
Feb 14 13:19:52 linux-ytaf kernel: ACPI: bus type PCI registered
Feb 14 13:19:52 linux-ytaf kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Feb 14 13:19:52 linux-ytaf kernel: PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
Feb 14 13:19:52 linux-ytaf kernel: PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
Feb 14 13:19:52 linux-ytaf kernel: PCI: Using configuration type 1 for base access
Feb 14 13:19:52 linux-ytaf kernel: perf_event_intel: PMU erratum BJ122, BV98, HSD29 worked around, HT is on
Feb 14 13:19:52 linux-ytaf kernel: ACPI: Added _OSI(Module Device)
Feb 14 13:19:52 linux-ytaf kernel: ACPI: Added _OSI(Processor Device)
Feb 14 13:19:52 linux-ytaf kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
Feb 14 13:19:52 linux-ytaf kernel: ACPI: Added _OSI(Processor Aggregator Device)
Feb 14 13:19:52 linux-ytaf kernel: ACPI: Executed 1 blocks of module-level executable AML code
Feb 14 13:19:52 linux-ytaf kernel: ACPI: Dynamic OEM Table Load:
Feb 14 13:19:52 linux-ytaf kernel: ACPI: SSDT 0xFFFF8802257C7000 00083B (v01 PmRef  Cpu0Cst  00003001 INTL 20051117)
Feb 14 13:19:52 linux-ytaf kernel: ACPI: Dynamic OEM Table Load:
Feb 14 13:19:52 linux-ytaf kernel: ACPI: SSDT 0xFFFF8802257C1400 000303 (v01 PmRef  ApIst    00003000 INTL 20051117)
Feb 14 13:19:52 linux-ytaf kernel: ACPI: Dynamic OEM Table Load:
Feb 14 13:19:52 linux-ytaf kernel: ACPI: SSDT 0xFFFF880225774600 000119 (v01 PmRef  ApCst    00003000 INTL 20051117)
Feb 14 13:19:52 linux-ytaf kernel: ACPI : EC: EC started
Feb 14 13:19:52 linux-ytaf kernel: ACPI: Interpreter enabled
Feb 14 13:19:52 linux-ytaf kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20150410/hwxface-580)
Feb 14 13:19:52 linux-ytaf kernel: ACPI: (supports S0 S1 S3 S4 S5)
Feb 14 13:19:52 linux-ytaf kernel: ACPI: Using IOAPIC for interrupt routing
Feb 14 13:19:52 linux-ytaf kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Feb 14 13:19:52 linux-ytaf kernel: ACPI: Power Resource [FN00] (off)
Feb 14 13:19:52 linux-ytaf kernel: ACPI: Power Resource [FN01] (off)
Feb 14 13:19:52 linux-ytaf kernel: ACPI: Power Resource [FN02] (off)
Feb 14 13:19:52 linux-ytaf kernel: ACPI: Power Resource [FN03] (off)
Feb 14 13:19:52 linux-ytaf kernel: ACPI: Power Resource [FN04] (off)
Feb 14 13:19:52 linux-ytaf kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
Feb 14 13:19:52 linux-ytaf kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Feb 14 13:19:52 linux-ytaf kernel: \_SB_.PCI0:_OSC invalid UUID
Feb 14 13:19:52 linux-ytaf kernel: _OSC request data:1 1f 0 
Feb 14 13:19:52 linux-ytaf kernel: acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
Feb 14 13:19:52 linux-ytaf kernel: PCI host bridge to bus 0000:00
Feb 14 13:19:52 linux-ytaf kernel: pci_bus 0000:00: root bus resource [bus 00-3e]
Feb 14 13:19:52 linux-ytaf kernel: pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
Feb 14 13:19:52 linux-ytaf kernel: pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
Feb 14 13:19:52 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
Feb 14 13:19:52 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff window]
Feb 14 13:19:52 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff window]
Feb 14 13:19:52 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff window]
Feb 14 13:19:52 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0xcfa00000-0xfeafffff window]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:00.0: [8086:0100] type 00 class 0x060000
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:01.0: [8086:0101] type 01 class 0x060400
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:01.0: System wakeup disabled by ACPI
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:01.1: [8086:0105] type 01 class 0x060400
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:01.1: PME# supported from D0 D3hot D3cold
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:01.1: System wakeup disabled by ACPI
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:02.0: [8086:0122] type 00 class 0x038000
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:02.0: reg 0x10: [mem 0xf7400000-0xf77fffff 64bit]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:02.0: reg 0x18: [mem 0xd0000000-0xdfffffff 64bit pref]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:02.0: reg 0x20: [io  0xf000-0xf03f]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:16.0: [8086:1c3a] type 00 class 0x078000
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:16.0: reg 0x10: [mem 0xf7b2c000-0xf7b2c00f 64bit]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:19.0: [8086:1503] type 00 class 0x020000
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:19.0: reg 0x10: [mem 0xf7b00000-0xf7b1ffff]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:19.0: reg 0x14: [mem 0xf7b29000-0xf7b29fff]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:19.0: reg 0x18: [io  0xf080-0xf09f]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:19.0: PME# supported from D0 D3hot D3cold
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:19.0: System wakeup disabled by ACPI
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1a.0: [8086:1c2d] type 00 class 0x0c0320
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1a.0: reg 0x10: [mem 0xf7b28000-0xf7b283ff]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1a.0: System wakeup disabled by ACPI
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1b.0: [8086:1c20] type 00 class 0x040300
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1b.0: reg 0x10: [mem 0xf7b20000-0xf7b23fff 64bit]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1b.0: System wakeup disabled by ACPI
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.0: [8086:1c10] type 01 class 0x060400
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.0: System wakeup disabled by ACPI
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.4: [8086:1c18] type 01 class 0x060400
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.4: System wakeup disabled by ACPI
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.5: [8086:1c1a] type 01 class 0x060400
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.5: System wakeup disabled by ACPI
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.6: [8086:1c1c] type 01 class 0x060400
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.6: PME# supported from D0 D3hot D3cold
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.6: System wakeup disabled by ACPI
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1d.0: [8086:1c26] type 00 class 0x0c0320
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1d.0: reg 0x10: [mem 0xf7b27000-0xf7b273ff]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1d.0: System wakeup disabled by ACPI
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1f.0: [8086:1c44] type 00 class 0x060100
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1f.2: [8086:1c02] type 00 class 0x010601
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x10: [io  0xf0d0-0xf0d7]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x14: [io  0xf0c0-0xf0c3]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x18: [io  0xf0b0-0xf0b7]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x1c: [io  0xf0a0-0xf0a3]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x20: [io  0xf060-0xf07f]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x24: [mem 0xf7b26000-0xf7b267ff]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1f.2: PME# supported from D3hot
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1f.3: [8086:1c22] type 00 class 0x0c0500
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1f.3: reg 0x10: [mem 0xf7b25000-0xf7b250ff 64bit]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1f.3: reg 0x20: [io  0x0580-0x059f]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:02:00.0: [10de:1183] type 00 class 0x030000
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:02:00.0: reg 0x10: [mem 0xf6000000-0xf6ffffff]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:02:00.0: reg 0x14: [mem 0xe0000000-0xe7ffffff 64bit pref]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:02:00.0: reg 0x1c: [mem 0xe8000000-0xe9ffffff 64bit pref]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:02:00.0: reg 0x24: [io  0xe000-0xe07f]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:02:00.0: reg 0x30: [mem 0xf7000000-0xf707ffff pref]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:02:00.1: [10de:0e0a] type 00 class 0x040300
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:02:00.1: reg 0x10: [mem 0xf7080000-0xf7083fff]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:01.1: PCI bridge to [bus 02]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [io  0xe000-0xefff]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xf6000000-0xf70fffff]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xe0000000-0xe9ffffff 64bit pref]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.0: PCI bridge to [bus 03]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:04:00.0: [1b21:1042] type 00 class 0x0c0330
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:04:00.0: reg 0x10: [mem 0xf7a00000-0xf7a07fff 64bit]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:04:00.0: PME# supported from D3hot D3cold
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:04:00.0: System wakeup disabled by ACPI
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.4: PCI bridge to [bus 04]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.4:   bridge window [mem 0xf7a00000-0xf7afffff]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:05:00.0: [1b21:1042] type 00 class 0x0c0330
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:05:00.0: reg 0x10: [mem 0xf7900000-0xf7907fff 64bit]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:05:00.0: PME# supported from D3hot D3cold
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:05:00.0: System wakeup disabled by ACPI
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.5: PCI bridge to [bus 05]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.5:   bridge window [mem 0xf7900000-0xf79fffff]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:06:00.0: [197b:2362] type 00 class 0x010185
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:06:00.0: reg 0x10: [io  0xd040-0xd047]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:06:00.0: reg 0x14: [io  0xd030-0xd033]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:06:00.0: reg 0x18: [io  0xd020-0xd027]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:06:00.0: reg 0x1c: [io  0xd010-0xd013]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:06:00.0: reg 0x20: [io  0xd000-0xd00f]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:06:00.0: reg 0x24: [mem 0xf7810000-0xf78101ff]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:06:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:06:00.0: PME# supported from D3hot
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:06:00.0: System wakeup disabled by ACPI
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.6: PCI bridge to [bus 06]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [io  0xd000-0xdfff]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [mem 0xf7800000-0xf78fffff]
Feb 14 13:19:52 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15)
Feb 14 13:19:52 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *10 11 12 14 15)
Feb 14 13:19:52 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Feb 14 13:19:52 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs *3 4 5 6 10 11 12 14 15)
Feb 14 13:19:52 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 *4 5 6 10 11 12 14 15)
Feb 14 13:19:52 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
Feb 14 13:19:52 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 *11 12 14 15)
Feb 14 13:19:52 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 *10 11 12 14 15)
Feb 14 13:19:52 linux-ytaf kernel: ACPI: Enabled 6 GPEs in block 00 to 3F
Feb 14 13:19:52 linux-ytaf kernel: ACPI : EC: GPE = 0x18, I/O: command/status = 0x66, data = 0x62
Feb 14 13:19:52 linux-ytaf kernel: vgaarb: setting as boot device: PCI:0000:02:00.0
Feb 14 13:19:52 linux-ytaf kernel: vgaarb: device added: PCI:0000:02:00.0,decodes=io+mem,owns=io+mem,locks=none
Feb 14 13:19:52 linux-ytaf kernel: vgaarb: loaded
Feb 14 13:19:52 linux-ytaf kernel: vgaarb: bridge control possible 0000:02:00.0
Feb 14 13:19:52 linux-ytaf kernel: SCSI subsystem initialized
Feb 14 13:19:52 linux-ytaf kernel: libata version 3.00 loaded.
Feb 14 13:19:52 linux-ytaf kernel: PCI: Using ACPI for IRQ routing
Feb 14 13:19:52 linux-ytaf kernel: PCI: pci_cache_line_size set to 64 bytes
Feb 14 13:19:52 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0009f000-0x0009ffff]
Feb 14 13:19:52 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c826018-0x0fffffff]
Feb 14 13:19:52 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c836018-0x0fffffff]
Feb 14 13:19:52 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c847018-0x0fffffff]
Feb 14 13:19:52 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c857018-0x0fffffff]
Feb 14 13:19:52 linux-ytaf kernel: e820: reserve RAM buffer [mem 0xca38f000-0xcbffffff]
Feb 14 13:19:52 linux-ytaf kernel: e820: reserve RAM buffer [mem 0xcb000000-0xcbffffff]
Feb 14 13:19:52 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x22f600000-0x22fffffff]
Feb 14 13:19:52 linux-ytaf kernel: NetLabel: Initializing
Feb 14 13:19:52 linux-ytaf kernel: NetLabel:  domain hash size = 128
Feb 14 13:19:52 linux-ytaf kernel: NetLabel:  protocols = UNLABELED CIPSOv4
Feb 14 13:19:52 linux-ytaf kernel: NetLabel:  unlabeled traffic allowed by default
Feb 14 13:19:52 linux-ytaf kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Feb 14 13:19:52 linux-ytaf kernel: hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Feb 14 13:19:52 linux-ytaf kernel: Switched to clocksource hpet
Feb 14 13:19:52 linux-ytaf kernel: AppArmor: AppArmor Filesystem Enabled
Feb 14 13:19:52 linux-ytaf kernel: pnp: PnP ACPI init
Feb 14 13:19:52 linux-ytaf kernel: system 00:00: [mem 0xfed40000-0xfed44fff] has been reserved
Feb 14 13:19:52 linux-ytaf kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
Feb 14 13:19:52 linux-ytaf kernel: system 00:01: [io  0x0680-0x069f] has been reserved
Feb 14 13:19:52 linux-ytaf kernel: system 00:01: [io  0x0200-0x020f] has been reserved
Feb 14 13:19:52 linux-ytaf kernel: system 00:01: [io  0xffff] has been reserved
Feb 14 13:19:52 linux-ytaf kernel: system 00:01: [io  0xffff] has been reserved
Feb 14 13:19:52 linux-ytaf kernel: system 00:01: [io  0x0400-0x0453] could not be reserved
Feb 14 13:19:52 linux-ytaf kernel: system 00:01: [io  0x0458-0x047f] has been reserved
Feb 14 13:19:52 linux-ytaf kernel: system 00:01: [io  0x0500-0x057f] has been reserved
Feb 14 13:19:52 linux-ytaf kernel: system 00:01: [io  0x164e-0x164f] has been reserved
Feb 14 13:19:52 linux-ytaf kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 13:19:52 linux-ytaf kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Feb 14 13:19:52 linux-ytaf kernel: system 00:03: [io  0x0454-0x0457] has been reserved
Feb 14 13:19:52 linux-ytaf kernel: system 00:03: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
Feb 14 13:19:52 linux-ytaf kernel: system 00:04: [io  0x0290-0x029f] has been reserved
Feb 14 13:19:52 linux-ytaf kernel: system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 13:19:52 linux-ytaf kernel: system 00:05: [io  0x04d0-0x04d1] has been reserved
Feb 14 13:19:52 linux-ytaf kernel: system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 13:19:52 linux-ytaf kernel: system 00:06: [mem 0xfed1c000-0xfed1ffff] has been reserved
Feb 14 13:19:52 linux-ytaf kernel: system 00:06: [mem 0xfed10000-0xfed17fff] has been reserved
Feb 14 13:19:52 linux-ytaf kernel: system 00:06: [mem 0xfed18000-0xfed18fff] has been reserved
Feb 14 13:19:52 linux-ytaf kernel: system 00:06: [mem 0xfed19000-0xfed19fff] has been reserved
Feb 14 13:19:52 linux-ytaf kernel: system 00:06: [mem 0xf8000000-0xfbffffff] has been reserved
Feb 14 13:19:52 linux-ytaf kernel: system 00:06: [mem 0xfed20000-0xfed3ffff] has been reserved
Feb 14 13:19:52 linux-ytaf kernel: system 00:06: [mem 0xfed90000-0xfed93fff] has been reserved
Feb 14 13:19:52 linux-ytaf kernel: system 00:06: [mem 0xfed45000-0xfed8ffff] has been reserved
Feb 14 13:19:52 linux-ytaf kernel: system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Feb 14 13:19:52 linux-ytaf kernel: system 00:06: [mem 0xfee00000-0xfeefffff] could not be reserved
Feb 14 13:19:52 linux-ytaf kernel: system 00:06: [mem 0xcfa00000-0xcfa00fff] has been reserved
Feb 14 13:19:52 linux-ytaf kernel: system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 13:19:52 linux-ytaf kernel: system 00:07: [mem 0x20000000-0x201fffff] has been reserved
Feb 14 13:19:52 linux-ytaf kernel: system 00:07: [mem 0x40000000-0x401fffff] has been reserved
Feb 14 13:19:52 linux-ytaf kernel: system 00:07: Plug and Play ACPI device, IDs PNP0c01 (active)
Feb 14 13:19:52 linux-ytaf kernel: pnp: PnP ACPI: found 8 devices
Feb 14 13:19:52 linux-ytaf kernel: clocksource acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.0: bridge window [io  0x1000-0x0fff] to [bus 03] add_size 1000
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 03] add_size 200000 add_align 100000
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff] to [bus 03] add_size 200000 add_align 100000
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.0: res[14]=[mem 0x00100000-0x000fffff] res_to_dev_res add_size 200000 min_align 100000
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.0: res[14]=[mem 0x00100000-0x002fffff] res_to_dev_res add_size 200000 min_align 100000
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x000fffff 64bit pref] res_to_dev_res add_size 200000 min_align 100000
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x002fffff 64bit pref] res_to_dev_res add_size 200000 min_align 100000
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.0: res[13]=[io  0x1000-0x0fff] res_to_dev_res add_size 1000 min_align 1000
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.0: res[13]=[io  0x1000-0x1fff] res_to_dev_res add_size 1000 min_align 1000
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.0: BAR 14: assigned [mem 0xcfb00000-0xcfcfffff]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.0: BAR 15: assigned [mem 0xcfd00000-0xcfefffff 64bit pref]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.0: BAR 13: assigned [io  0x2000-0x2fff]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:01.1: PCI bridge to [bus 02]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [io  0xe000-0xefff]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xf6000000-0xf70fffff]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xe0000000-0xe9ffffff 64bit pref]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.0: PCI bridge to [bus 03]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.0:   bridge window [io  0x2000-0x2fff]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.0:   bridge window [mem 0xcfb00000-0xcfcfffff]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.0:   bridge window [mem 0xcfd00000-0xcfefffff 64bit pref]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.4: PCI bridge to [bus 04]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.4:   bridge window [mem 0xf7a00000-0xf7afffff]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.5: PCI bridge to [bus 05]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.5:   bridge window [mem 0xf7900000-0xf79fffff]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:06:00.0: BAR 6: assigned [mem 0xf7800000-0xf780ffff pref]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.6: PCI bridge to [bus 06]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [io  0xd000-0xdfff]
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [mem 0xf7800000-0xf78fffff]
Feb 14 13:19:52 linux-ytaf kernel: pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
Feb 14 13:19:52 linux-ytaf kernel: pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
Feb 14 13:19:52 linux-ytaf kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
Feb 14 13:19:52 linux-ytaf kernel: pci_bus 0000:00: resource 7 [mem 0x000d4000-0x000d7fff window]
Feb 14 13:19:52 linux-ytaf kernel: pci_bus 0000:00: resource 8 [mem 0x000d8000-0x000dbfff window]
Feb 14 13:19:52 linux-ytaf kernel: pci_bus 0000:00: resource 9 [mem 0x000dc000-0x000dffff window]
Feb 14 13:19:52 linux-ytaf kernel: pci_bus 0000:00: resource 10 [mem 0xcfa00000-0xfeafffff window]
Feb 14 13:19:52 linux-ytaf kernel: pci_bus 0000:02: resource 0 [io  0xe000-0xefff]
Feb 14 13:19:52 linux-ytaf kernel: pci_bus 0000:02: resource 1 [mem 0xf6000000-0xf70fffff]
Feb 14 13:19:52 linux-ytaf kernel: pci_bus 0000:02: resource 2 [mem 0xe0000000-0xe9ffffff 64bit pref]
Feb 14 13:19:52 linux-ytaf kernel: pci_bus 0000:03: resource 0 [io  0x2000-0x2fff]
Feb 14 13:19:52 linux-ytaf kernel: pci_bus 0000:03: resource 1 [mem 0xcfb00000-0xcfcfffff]
Feb 14 13:19:52 linux-ytaf kernel: pci_bus 0000:03: resource 2 [mem 0xcfd00000-0xcfefffff 64bit pref]
Feb 14 13:19:52 linux-ytaf kernel: pci_bus 0000:04: resource 1 [mem 0xf7a00000-0xf7afffff]
Feb 14 13:19:52 linux-ytaf kernel: pci_bus 0000:05: resource 1 [mem 0xf7900000-0xf79fffff]
Feb 14 13:19:52 linux-ytaf kernel: pci_bus 0000:06: resource 0 [io  0xd000-0xdfff]
Feb 14 13:19:52 linux-ytaf kernel: pci_bus 0000:06: resource 1 [mem 0xf7800000-0xf78fffff]
Feb 14 13:19:52 linux-ytaf kernel: NET: Registered protocol family 2
Feb 14 13:19:52 linux-ytaf kernel: TCP established hash table entries: 65536 (order: 7, 524288 bytes)
Feb 14 13:19:52 linux-ytaf kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Feb 14 13:19:52 linux-ytaf kernel: TCP: Hash tables configured (established 65536 bind 65536)
Feb 14 13:19:52 linux-ytaf kernel: UDP hash table entries: 4096 (order: 5, 131072 bytes)
Feb 14 13:19:52 linux-ytaf kernel: UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
Feb 14 13:19:52 linux-ytaf kernel: NET: Registered protocol family 1
Feb 14 13:19:52 linux-ytaf kernel: pci 0000:02:00.0: Video device with shadowed ROM
Feb 14 13:19:52 linux-ytaf kernel: PCI: CLS 64 bytes, default 64
Feb 14 13:19:52 linux-ytaf kernel: Unpacking initramfs...
Feb 14 13:19:52 linux-ytaf kernel: Freeing initrd memory: 11920K (ffff880000457000 - ffff880000ffb000)
Feb 14 13:19:52 linux-ytaf kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Feb 14 13:19:52 linux-ytaf kernel: software IO TLB [mem 0xc638f000-0xca38f000] (64MB) mapped at [ffff8800c638f000-ffff8800ca38efff]
Feb 14 13:19:52 linux-ytaf kernel: RAPL PMU detected, API unit is 2^-32 Joules, 3 fixed counters 163840 ms ovfl timer
Feb 14 13:19:52 linux-ytaf kernel: hw unit of domain pp0-core 2^-16 Joules
Feb 14 13:19:52 linux-ytaf kernel: hw unit of domain package 2^-16 Joules
Feb 14 13:19:52 linux-ytaf kernel: hw unit of domain pp1-gpu 2^-16 Joules
Feb 14 13:19:52 linux-ytaf kernel: microcode: CPU0 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 13:19:52 linux-ytaf kernel: microcode: CPU1 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 13:19:52 linux-ytaf kernel: microcode: CPU2 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 13:19:52 linux-ytaf kernel: microcode: CPU3 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 13:19:52 linux-ytaf kernel: microcode: CPU4 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 13:19:52 linux-ytaf kernel: microcode: CPU5 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 13:19:52 linux-ytaf kernel: microcode: CPU6 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 13:19:52 linux-ytaf kernel: microcode: CPU7 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 13:19:52 linux-ytaf kernel: microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Feb 14 13:19:52 linux-ytaf kernel: Scanning for low memory corruption every 60 seconds
Feb 14 13:19:52 linux-ytaf kernel: futex hash table entries: 2048 (order: 5, 131072 bytes)
Feb 14 13:19:52 linux-ytaf kernel: audit: initializing netlink subsys (disabled)
Feb 14 13:19:52 linux-ytaf kernel: audit: type=2000 audit(1455455990.280:1): initialized
Feb 14 13:19:52 linux-ytaf kernel: HugeTLB registered 2 MB page size, pre-allocated 0 pages
Feb 14 13:19:52 linux-ytaf kernel: zpool: loaded
Feb 14 13:19:52 linux-ytaf kernel: zbud: loaded
Feb 14 13:19:52 linux-ytaf kernel: VFS: Disk quotas dquot_6.6.0
Feb 14 13:19:52 linux-ytaf kernel: VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Feb 14 13:19:52 linux-ytaf kernel: Key type big_key registered
Feb 14 13:19:52 linux-ytaf kernel: Key type asymmetric registered
Feb 14 13:19:52 linux-ytaf kernel: Asymmetric key parser 'x509' registered
Feb 14 13:19:52 linux-ytaf kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Feb 14 13:19:52 linux-ytaf kernel: io scheduler noop registered
Feb 14 13:19:52 linux-ytaf kernel: io scheduler deadline registered
Feb 14 13:19:52 linux-ytaf kernel: io scheduler cfq registered (default)
Feb 14 13:19:52 linux-ytaf kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Feb 14 13:19:52 linux-ytaf kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Feb 14 13:19:52 linux-ytaf kernel: efifb: probing for efifb
Feb 14 13:19:52 linux-ytaf kernel: efifb: framebuffer at 0xe9000000, mapped to 0xffffc90001000000, using 1876k, total 1875k
Feb 14 13:19:52 linux-ytaf kernel: efifb: mode is 800x600x32, linelength=3200, pages=1
Feb 14 13:19:52 linux-ytaf kernel: efifb: scrolling: redraw
Feb 14 13:19:52 linux-ytaf kernel: efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Feb 14 13:19:52 linux-ytaf kernel: Console: switching to colour frame buffer device 100x37
Feb 14 13:19:52 linux-ytaf kernel: fb0: EFI VGA frame buffer device
Feb 14 13:19:52 linux-ytaf kernel: intel_idle: MWAIT substates: 0x1120
Feb 14 13:19:52 linux-ytaf kernel: intel_idle: v0.4 model 0x2A
Feb 14 13:19:52 linux-ytaf kernel: intel_idle: lapic_timer_reliable_states 0xffffffff
Feb 14 13:19:52 linux-ytaf kernel: GHES: HEST is not enabled!
Feb 14 13:19:52 linux-ytaf kernel: Serial: 8250/16550 driver, 32 ports, IRQ sharing disabled
Feb 14 13:19:52 linux-ytaf kernel: Non-volatile memory driver v1.3
Feb 14 13:19:52 linux-ytaf kernel: Linux agpgart interface v0.103
Feb 14 13:19:52 linux-ytaf kernel: ahci 0000:00:1f.2: version 3.0
Feb 14 13:19:52 linux-ytaf kernel: ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x7 impl SATA mode
Feb 14 13:19:52 linux-ytaf kernel: ahci 0000:00:1f.2: flags: 64bit ncq led clo pio slum part ems apst 
Feb 14 13:19:52 linux-ytaf kernel: scsi host0: ahci
Feb 14 13:19:52 linux-ytaf kernel: scsi host1: ahci
Feb 14 13:19:52 linux-ytaf kernel: scsi host2: ahci
Feb 14 13:19:52 linux-ytaf kernel: scsi host3: ahci
Feb 14 13:19:52 linux-ytaf kernel: scsi host4: ahci
Feb 14 13:19:52 linux-ytaf kernel: scsi host5: ahci
Feb 14 13:19:52 linux-ytaf kernel: ata1: SATA max UDMA/133 abar m2048@0xf7b26000 port 0xf7b26100 irq 26
Feb 14 13:19:52 linux-ytaf kernel: ata2: SATA max UDMA/133 abar m2048@0xf7b26000 port 0xf7b26180 irq 26
Feb 14 13:19:52 linux-ytaf kernel: ata3: SATA max UDMA/133 abar m2048@0xf7b26000 port 0xf7b26200 irq 26
Feb 14 13:19:52 linux-ytaf kernel: ata4: DUMMY
Feb 14 13:19:52 linux-ytaf kernel: ata5: DUMMY
Feb 14 13:19:52 linux-ytaf kernel: ata6: DUMMY
Feb 14 13:19:52 linux-ytaf kernel: ahci 0000:06:00.0: AHCI 0001.0100 32 slots 2 ports 3 Gbps 0x3 impl SATA mode
Feb 14 13:19:52 linux-ytaf kernel: ahci 0000:06:00.0: flags: 64bit ncq pm led clo pmp pio slum part 
Feb 14 13:19:52 linux-ytaf kernel: scsi host6: ahci
Feb 14 13:19:52 linux-ytaf kernel: scsi host7: ahci
Feb 14 13:19:52 linux-ytaf kernel: ata7: SATA max UDMA/133 abar m512@0xf7810000 port 0xf7810100 irq 18
Feb 14 13:19:52 linux-ytaf kernel: ata8: SATA max UDMA/133 abar m512@0xf7810000 port 0xf7810180 irq 18
Feb 14 13:19:52 linux-ytaf kernel: i8042: PNP: No PS/2 controller found. Probing ports directly.
Feb 14 13:19:52 linux-ytaf kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Feb 14 13:19:52 linux-ytaf kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Feb 14 13:19:52 linux-ytaf kernel: mousedev: PS/2 mouse device common for all mice
Feb 14 13:19:52 linux-ytaf kernel: rtc_cmos 00:02: RTC can wake from S4
Feb 14 13:19:52 linux-ytaf kernel: rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Feb 14 13:19:52 linux-ytaf kernel: rtc_cmos 00:02: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
Feb 14 13:19:52 linux-ytaf kernel: Intel P-state driver initializing.
Feb 14 13:19:52 linux-ytaf kernel: ledtrig-cpu: registered to indicate activity on CPUs
Feb 14 13:19:52 linux-ytaf kernel: EFI Variables Facility v0.08 2004-May-17
Feb 14 13:19:52 linux-ytaf kernel: hidraw: raw HID events driver (C) Jiri Kosina
Feb 14 13:19:52 linux-ytaf kernel: NET: Registered protocol family 10
Feb 14 13:19:52 linux-ytaf kernel: registered taskstats version 1
Feb 14 13:19:52 linux-ytaf kernel: Key type encrypted registered
Feb 14 13:19:52 linux-ytaf kernel: AppArmor: AppArmor sha1 policy hashing enabled
Feb 14 13:19:52 linux-ytaf kernel:   Magic number: 4:675:331
Feb 14 13:19:52 linux-ytaf kernel: tty tty52: hash matches
Feb 14 13:19:52 linux-ytaf kernel: rtc_cmos 00:02: setting system clock to 2016-02-14 13:19:50 UTC (1455455990)
Feb 14 13:19:52 linux-ytaf kernel: PM: Checking hibernation image partition /dev/sdb2
Feb 14 13:19:52 linux-ytaf kernel: ata7: SATA link down (SStatus 0 SControl 300)
Feb 14 13:19:52 linux-ytaf kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 14 13:19:52 linux-ytaf kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 14 13:19:52 linux-ytaf kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Feb 14 13:19:52 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 13:19:52 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff8802268b7e50), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 13:19:52 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 13:19:52 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff8802268b7dd8), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 13:19:52 linux-ytaf kernel: ata1.00: ATA-9: SAMSUNG SSD 830 Series, CXM03B1Q, max UDMA/133
Feb 14 13:19:52 linux-ytaf kernel: ata1.00: 500118192 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Feb 14 13:19:52 linux-ytaf kernel: ata2.00: ATA-8: TOSHIBA HDWD110, MS2OA8J0, max UDMA/133
Feb 14 13:19:52 linux-ytaf kernel: ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Feb 14 13:19:52 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 13:19:52 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff8802268b7e50), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 13:19:52 linux-ytaf kernel: ata1.00: configured for UDMA/133
Feb 14 13:19:52 linux-ytaf kernel: scsi 0:0:0:0: Direct-Access     ATA      SAMSUNG SSD 830  3B1Q PQ: 0 ANSI: 5
Feb 14 13:19:52 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 13:19:52 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff8802268b7d60), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 13:19:52 linux-ytaf kernel: ata3.00: ATAPI: TSSTcorp CDDVDW SH-S223C, SB05, max UDMA/66
Feb 14 13:19:52 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 13:19:52 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff8802268b7dd8), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 13:19:52 linux-ytaf kernel: ata2.00: configured for UDMA/133
Feb 14 13:19:52 linux-ytaf kernel: sd 0:0:0:0: [sda] 500118192 512-byte logical blocks: (256 GB/238 GiB)
Feb 14 13:19:52 linux-ytaf kernel: scsi 1:0:0:0: Direct-Access     ATA      TOSHIBA HDWD110  A8J0 PQ: 0 ANSI: 5
Feb 14 13:19:52 linux-ytaf kernel: sd 0:0:0:0: [sda] Write Protect is off
Feb 14 13:19:52 linux-ytaf kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 14 13:19:52 linux-ytaf kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 14 13:19:52 linux-ytaf kernel: sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
Feb 14 13:19:52 linux-ytaf kernel: sd 1:0:0:0: [sdb] 4096-byte physical blocks
Feb 14 13:19:52 linux-ytaf kernel: sd 1:0:0:0: [sdb] Write Protect is off
Feb 14 13:19:52 linux-ytaf kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Feb 14 13:19:52 linux-ytaf kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 14 13:19:52 linux-ytaf kernel:  sda: sda1 sda2 sda3 sda4
Feb 14 13:19:52 linux-ytaf kernel: ata8: SATA link down (SStatus 0 SControl 300)
Feb 14 13:19:52 linux-ytaf kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Feb 14 13:19:52 linux-ytaf kernel:  sdb: sdb1 sdb2 sdb3 sdb4
Feb 14 13:19:52 linux-ytaf kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
Feb 14 13:19:52 linux-ytaf kernel: tsc: Refined TSC clocksource calibration: 3411.128 MHz
Feb 14 13:19:52 linux-ytaf kernel: clocksource tsc: mask: 0xffffffffffffffff max_cycles: 0x312b5ecadef, max_idle_ns: 440795307361 ns
Feb 14 13:19:52 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 13:19:52 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff8802268b7d60), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 13:19:52 linux-ytaf kernel: ata3.00: configured for UDMA/66
Feb 14 13:19:52 linux-ytaf kernel: scsi 2:0:0:0: CD-ROM            TSSTcorp CDDVDW SH-S223C  SB05 PQ: 0 ANSI: 5
Feb 14 13:19:52 linux-ytaf kernel: PM: Hibernation image partition 8:18 present
Feb 14 13:19:52 linux-ytaf kernel: PM: Looking for hibernation image.
Feb 14 13:19:52 linux-ytaf kernel: Switched to clocksource tsc
Feb 14 13:19:52 linux-ytaf kernel: PM: Image not found (code -22)
Feb 14 13:19:52 linux-ytaf kernel: PM: Hibernation image not present or could not be loaded.
Feb 14 13:19:52 linux-ytaf kernel: Freeing unused kernel memory: 1560K (ffffffff81f11000 - ffffffff82097000)
Feb 14 13:19:52 linux-ytaf kernel: Write protecting the kernel read-only data: 14336k
Feb 14 13:19:52 linux-ytaf kernel: Freeing unused kernel memory: 1632K (ffff88000d668000 - ffff88000d800000)
Feb 14 13:19:52 linux-ytaf kernel: Freeing unused kernel memory: 1296K (ffff88000dcbc000 - ffff88000de00000)
Feb 14 13:19:52 linux-ytaf systemd[1]: RTC configured in localtime, applying delta of 60 minutes to system time.
Feb 14 13:19:52 linux-ytaf kernel: random: systemd urandom read with 22 bits of entropy available
Feb 14 13:19:52 linux-ytaf kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Feb 14 13:19:52 linux-ytaf kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0
Feb 14 13:19:52 linux-ytaf kernel: scsi 2:0:0:0: Attached scsi generic sg2 type 5
Feb 14 13:19:52 linux-ytaf systemd-journal[187]: Journal started
Feb 14 13:19:52 linux-ytaf dracut-cmdline[181]: dracut-42.1 dracut-037-68.1
Feb 14 13:19:52 linux-ytaf systemd-udevd[250]: Network interface NamePolicy= disabled on kernel commandline, ignoring.
Feb 14 13:19:52 linux-ytaf kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3
Feb 14 13:19:52 linux-ytaf kernel: ACPI: Power Button [PWRB]
Feb 14 13:19:52 linux-ytaf kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
Feb 14 13:19:52 linux-ytaf kernel: ACPI: Power Button [PWRF]
Feb 14 13:19:52 linux-ytaf kernel: ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
Feb 14 13:19:52 linux-ytaf kernel: acpi device:58: registered as cooling_device0
Feb 14 13:19:52 linux-ytaf kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5
Feb 14 13:19:52 linux-ytaf kernel: wmi: Mapper loaded
Feb 14 13:19:52 linux-ytaf kernel: [drm] Initialized drm 1.1.0 20060810
Feb 14 13:19:52 linux-ytaf kernel: ACPI: bus type USB registered
Feb 14 13:19:52 linux-ytaf kernel: usbcore: registered new interface driver usbfs
Feb 14 13:19:52 linux-ytaf kernel: usbcore: registered new interface driver hub
Feb 14 13:19:52 linux-ytaf kernel: usbcore: registered new device driver usb
Feb 14 13:19:52 linux-ytaf kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Feb 14 13:19:52 linux-ytaf kernel: ehci-pci: EHCI PCI platform driver
Feb 14 13:19:52 linux-ytaf kernel: ehci-pci 0000:00:1a.0: EHCI Host Controller
Feb 14 13:19:52 linux-ytaf kernel: ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Feb 14 13:19:52 linux-ytaf kernel: ehci-pci 0000:00:1a.0: debug port 2
Feb 14 13:19:52 linux-ytaf kernel: ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Feb 14 13:19:52 linux-ytaf kernel: ehci-pci 0000:00:1a.0: irq 16, io mem 0xf7b28000
Feb 14 13:19:52 linux-ytaf kernel: MXM: GUID detected in BIOS
Feb 14 13:19:52 linux-ytaf kernel: checking generic (e9000000 1d5000) vs hw (e0000000 8000000)
Feb 14 13:19:52 linux-ytaf kernel: checking generic (e9000000 1d5000) vs hw (e8000000 2000000)
Feb 14 13:19:52 linux-ytaf kernel: fb: switching to nouveaufb from EFI VGA
Feb 14 13:19:52 linux-ytaf kernel: Console: switching to colour dummy device 80x25
Feb 14 13:19:52 linux-ytaf kernel: nouveau  [  DEVICE][0000:02:00.0] BOOT0  : 0x0e4030a2
Feb 14 13:19:52 linux-ytaf kernel: nouveau  [  DEVICE][0000:02:00.0] Chipset: GK104 (NVE4)
Feb 14 13:19:52 linux-ytaf kernel: nouveau  [  DEVICE][0000:02:00.0] Family : NVE0
Feb 14 13:19:52 linux-ytaf kernel: ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Feb 14 13:19:52 linux-ytaf kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 13:19:52 linux-ytaf kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 13:19:52 linux-ytaf kernel: usb usb1: Product: EHCI Host Controller
Feb 14 13:19:52 linux-ytaf kernel: usb usb1: Manufacturer: Linux 4.1.15-8-default ehci_hcd
Feb 14 13:19:52 linux-ytaf kernel: usb usb1: SerialNumber: 0000:00:1a.0
Feb 14 13:19:52 linux-ytaf kernel: hub 1-0:1.0: USB hub found
Feb 14 13:19:52 linux-ytaf kernel: hub 1-0:1.0: 2 ports detected
Feb 14 13:19:52 linux-ytaf kernel: xhci_hcd 0000:04:00.0: xHCI Host Controller
Feb 14 13:19:52 linux-ytaf kernel: xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 2
Feb 14 13:19:52 linux-ytaf kernel: sr 2:0:0:0: [sr0] scsi3-mmc drive: 52x/52x writer dvd-ram cd/rw xa/form2 cdda tray
Feb 14 13:19:52 linux-ytaf kernel: cdrom: Uniform CD-ROM driver Revision: 3.20
Feb 14 13:19:52 linux-ytaf kernel: sr 2:0:0:0: Attached scsi CD-ROM sr0
Feb 14 13:19:52 linux-ytaf kernel: xhci_hcd 0000:04:00.0: hcc params 0x0200f180 hci version 0x96 quirks 0x00080000
Feb 14 13:19:52 linux-ytaf kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 13:19:52 linux-ytaf kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 13:19:52 linux-ytaf kernel: usb usb2: Product: xHCI Host Controller
Feb 14 13:19:52 linux-ytaf kernel: usb usb2: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 13:19:52 linux-ytaf kernel: usb usb2: SerialNumber: 0000:04:00.0
Feb 14 13:19:52 linux-ytaf kernel: hub 2-0:1.0: USB hub found
Feb 14 13:19:52 linux-ytaf kernel: hub 2-0:1.0: 2 ports detected
Feb 14 13:19:52 linux-ytaf kernel: xhci_hcd 0000:04:00.0: xHCI Host Controller
Feb 14 13:19:52 linux-ytaf kernel: xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 3
Feb 14 13:19:52 linux-ytaf kernel: ehci-pci 0000:00:1d.0: EHCI Host Controller
Feb 14 13:19:52 linux-ytaf kernel: ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 4
Feb 14 13:19:52 linux-ytaf kernel: usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
Feb 14 13:19:52 linux-ytaf kernel: ehci-pci 0000:00:1d.0: debug port 2
Feb 14 13:19:52 linux-ytaf kernel: usb usb3: New USB device found, idVendor=1d6b, idProduct=0003
Feb 14 13:19:52 linux-ytaf kernel: usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 13:19:52 linux-ytaf kernel: usb usb3: Product: xHCI Host Controller
Feb 14 13:19:52 linux-ytaf kernel: usb usb3: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 13:19:52 linux-ytaf kernel: usb usb3: SerialNumber: 0000:04:00.0
Feb 14 13:19:52 linux-ytaf kernel: hub 3-0:1.0: USB hub found
Feb 14 13:19:52 linux-ytaf kernel: hub 3-0:1.0: 2 ports detected
Feb 14 13:19:52 linux-ytaf kernel: ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Feb 14 13:19:52 linux-ytaf kernel: ehci-pci 0000:00:1d.0: irq 23, io mem 0xf7b27000
Feb 14 13:19:52 linux-ytaf kernel: ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Feb 14 13:19:52 linux-ytaf kernel: usb usb4: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 13:19:52 linux-ytaf kernel: usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 13:19:52 linux-ytaf kernel: usb usb4: Product: EHCI Host Controller
Feb 14 13:19:52 linux-ytaf kernel: usb usb4: Manufacturer: Linux 4.1.15-8-default ehci_hcd
Feb 14 13:19:52 linux-ytaf kernel: usb usb4: SerialNumber: 0000:00:1d.0
Feb 14 13:19:52 linux-ytaf kernel: hub 4-0:1.0: USB hub found
Feb 14 13:19:52 linux-ytaf kernel: hub 4-0:1.0: 2 ports detected
Feb 14 13:19:52 linux-ytaf kernel: xhci_hcd 0000:05:00.0: xHCI Host Controller
Feb 14 13:19:52 linux-ytaf kernel: xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 5
Feb 14 13:19:52 linux-ytaf kernel: i915 0000:00:02.0: enabling device (0006 -> 0007)
Feb 14 13:19:52 linux-ytaf kernel: xhci_hcd 0000:05:00.0: hcc params 0x0200f180 hci version 0x96 quirks 0x00080000
Feb 14 13:19:52 linux-ytaf kernel: usb usb5: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 13:19:52 linux-ytaf kernel: usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 13:19:52 linux-ytaf kernel: usb usb5: Product: xHCI Host Controller
Feb 14 13:19:52 linux-ytaf kernel: usb usb5: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 13:19:52 linux-ytaf kernel: usb usb5: SerialNumber: 0000:05:00.0
Feb 14 13:19:52 linux-ytaf kernel: hub 5-0:1.0: USB hub found
Feb 14 13:19:52 linux-ytaf kernel: hub 5-0:1.0: 2 ports detected
Feb 14 13:19:52 linux-ytaf kernel: xhci_hcd 0000:05:00.0: xHCI Host Controller
Feb 14 13:19:52 linux-ytaf kernel: xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 6
Feb 14 13:19:52 linux-ytaf kernel: usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
Feb 14 13:19:52 linux-ytaf kernel: usb usb6: New USB device found, idVendor=1d6b, idProduct=0003
Feb 14 13:19:52 linux-ytaf kernel: usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 13:19:52 linux-ytaf kernel: usb usb6: Product: xHCI Host Controller
Feb 14 13:19:52 linux-ytaf kernel: usb usb6: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 13:19:52 linux-ytaf kernel: usb usb6: SerialNumber: 0000:05:00.0
Feb 14 13:19:52 linux-ytaf kernel: hub 6-0:1.0: USB hub found
Feb 14 13:19:52 linux-ytaf kernel: hub 6-0:1.0: 2 ports detected
Feb 14 13:19:52 linux-ytaf kernel: nouveau  [   VBIOS][0000:02:00.0] using image from PROM
Feb 14 13:19:52 linux-ytaf kernel: nouveau  [   VBIOS][0000:02:00.0] BIT signature found
Feb 14 13:19:52 linux-ytaf kernel: nouveau  [   VBIOS][0000:02:00.0] version 80.04.4b.00.07
Feb 14 13:19:52 linux-ytaf kernel: nouveau  [     PMC][0000:02:00.0] MSI interrupts enabled
Feb 14 13:19:52 linux-ytaf kernel: nouveau  [     PFB][0000:02:00.0] RAM type: GDDR5
Feb 14 13:19:52 linux-ytaf kernel: nouveau  [     PFB][0000:02:00.0] RAM size: 2048 MiB
Feb 14 13:19:52 linux-ytaf kernel: nouveau  [     PFB][0000:02:00.0]    ZCOMP: 0 tags
Feb 14 13:19:52 linux-ytaf kernel: nouveau  [    VOLT][0000:02:00.0] GPU voltage: 987500uv
Feb 14 13:19:52 linux-ytaf kernel: nouveau  [  PTHERM][0000:02:00.0] FAN control: PWM
Feb 14 13:19:52 linux-ytaf kernel: nouveau  [  PTHERM][0000:02:00.0] fan management: automatic
Feb 14 13:19:52 linux-ytaf kernel: nouveau  [  PTHERM][0000:02:00.0] internal sensor: yes
Feb 14 13:19:52 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 07: core 324 MHz memory 648 MHz 
Feb 14 13:19:52 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 0a: core 324-862 MHz memory 1620 MHz 
Feb 14 13:19:52 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 0d: core 540-1202 MHz memory 6008 MHz 
Feb 14 13:19:52 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 0f: core 540-1202 MHz memory 6008 MHz 
Feb 14 13:19:52 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] --: core 324 MHz memory 648 MHz 
Feb 14 13:19:52 linux-ytaf kernel: raid6: sse2x1   gen() 11233 MB/s
Feb 14 13:19:52 linux-ytaf kernel: usb 1-1: new high-speed USB device number 2 using ehci-pci
Feb 14 13:19:52 linux-ytaf kernel: raid6: sse2x1   xor()  9009 MB/s
Feb 14 13:19:52 linux-ytaf kernel: [TTM] Zone  kernel: Available graphics memory: 4034698 kiB
Feb 14 13:19:52 linux-ytaf kernel: [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
Feb 14 13:19:52 linux-ytaf kernel: [TTM] Initializing pool allocator
Feb 14 13:19:52 linux-ytaf kernel: [TTM] Initializing DMA pool allocator
Feb 14 13:19:52 linux-ytaf kernel: nouveau  [     DRM] VRAM: 2048 MiB
Feb 14 13:19:52 linux-ytaf kernel: nouveau  [     DRM] GART: 1048576 MiB
Feb 14 13:19:52 linux-ytaf kernel: nouveau  [     DRM] TMDS table version 2.0
Feb 14 13:19:52 linux-ytaf kernel: nouveau  [     DRM] DCB version 4.0
Feb 14 13:19:52 linux-ytaf kernel: nouveau  [     DRM] DCB outp 00: 01000f02 00020030
Feb 14 13:19:52 linux-ytaf kernel: nouveau  [     DRM] DCB outp 01: 02000f00 00000000
Feb 14 13:19:52 linux-ytaf kernel: nouveau  [     DRM] DCB outp 02: 08011f82 00020030
Feb 14 13:19:52 linux-ytaf kernel: nouveau  [     DRM] DCB outp 03: 02822f62 0f420010
Feb 14 13:19:52 linux-ytaf kernel: nouveau  [     DRM] DCB outp 05: 04833fb6 0f420010
Feb 14 13:19:52 linux-ytaf kernel: nouveau  [     DRM] DCB outp 06: 04033f72 00020010
Feb 14 13:19:52 linux-ytaf kernel: nouveau  [     DRM] DCB conn 00: 00001030
Feb 14 13:19:52 linux-ytaf kernel: nouveau  [     DRM] DCB conn 01: 00020131
Feb 14 13:19:52 linux-ytaf kernel: nouveau  [     DRM] DCB conn 02: 00002261
Feb 14 13:19:52 linux-ytaf kernel: nouveau  [     DRM] DCB conn 03: 00010346
Feb 14 13:19:52 linux-ytaf kernel: nouveau  [     DRM] DCB conn 04: 00000460
Feb 14 13:19:52 linux-ytaf kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Feb 14 13:19:52 linux-ytaf kernel: [drm] Driver supports precise vblank timestamp query.
Feb 14 13:19:52 linux-ytaf kernel: nouveau  [     DRM] MM: using COPY for buffer copies
Feb 14 13:19:52 linux-ytaf kernel: usb 4-1: new high-speed USB device number 2 using ehci-pci
Feb 14 13:19:52 linux-ytaf kernel: raid6: sse2x2   gen() 14109 MB/s
Feb 14 13:19:53 linux-ytaf kernel: usb 1-1: New USB device found, idVendor=8087, idProduct=0024
Feb 14 13:19:53 linux-ytaf kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb 14 13:19:53 linux-ytaf kernel: hub 1-1:1.0: USB hub found
Feb 14 13:19:53 linux-ytaf kernel: hub 1-1:1.0: 6 ports detected
Feb 14 13:19:53 linux-ytaf kernel: raid6: sse2x2   xor() 10040 MB/s
Feb 14 13:19:53 linux-ytaf kernel: usb 5-2: new high-speed USB device number 2 using xhci_hcd
Feb 14 13:19:53 linux-ytaf kernel: usb 4-1: New USB device found, idVendor=8087, idProduct=0024
Feb 14 13:19:53 linux-ytaf kernel: usb 4-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb 14 13:19:53 linux-ytaf kernel: hub 4-1:1.0: USB hub found
Feb 14 13:19:53 linux-ytaf kernel: hub 4-1:1.0: 8 ports detected
Feb 14 13:19:53 linux-ytaf kernel: raid6: sse2x4   gen() 16291 MB/s
Feb 14 13:19:53 linux-ytaf kernel: raid6: sse2x4   xor() 12098 MB/s
Feb 14 13:19:53 linux-ytaf kernel: raid6: using algorithm sse2x4 gen() 16291 MB/s
Feb 14 13:19:53 linux-ytaf kernel: raid6: .... xor() 12098 MB/s, rmw enabled
Feb 14 13:19:53 linux-ytaf kernel: raid6: using ssse3x2 recovery algorithm
Feb 14 13:19:53 linux-ytaf kernel: xor: automatically using best checksumming function:
Feb 14 13:19:53 linux-ytaf kernel:    avx       : 31207.000 MB/sec
Feb 14 13:19:53 linux-ytaf kernel: Btrfs loaded, assert=on
Feb 14 13:19:53 linux-ytaf kernel: BTRFS: device fsid 21024970-7a27-4114-8525-d8dd026f23b6 devid 1 transid 368 /dev/sdb3
Feb 14 13:19:53 linux-ytaf kernel: nouveau  [     DRM] allocated 1920x1080 fb: 0x60000, bo ffff880223230800
Feb 14 13:19:53 linux-ytaf kernel: fbcon: nouveaufb (fb0) is primary device
Feb 14 13:19:53 linux-ytaf kernel: usb 5-2: New USB device found, idVendor=0930, idProduct=6545
Feb 14 13:19:53 linux-ytaf kernel: usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 14 13:19:53 linux-ytaf kernel: usb 5-2: Product: TransMemory
Feb 14 13:19:53 linux-ytaf kernel: usb 5-2: Manufacturer: TOSHIBA
Feb 14 13:19:53 linux-ytaf kernel: usb 5-2: SerialNumber: C89CDCBF6D59EF4140000065
Feb 14 13:19:53 linux-ytaf kernel: usb-storage 5-2:1.0: USB Mass Storage device detected
Feb 14 13:19:53 linux-ytaf kernel: scsi host8: usb-storage 5-2:1.0
Feb 14 13:19:53 linux-ytaf kernel: usbcore: registered new interface driver usb-storage
Feb 14 13:19:53 linux-ytaf kernel: usbcore: registered new interface driver uas
Feb 14 13:19:53 linux-ytaf kernel: usb 1-1.4: new full-speed USB device number 3 using ehci-pci
Feb 14 13:19:53 linux-ytaf kernel: usb 4-1.1: new full-speed USB device number 3 using ehci-pci
Feb 14 13:19:53 linux-ytaf kernel: usb 4-1.1: New USB device found, idVendor=1532, idProduct=0109
Feb 14 13:19:53 linux-ytaf kernel: usb 4-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 14 13:19:53 linux-ytaf kernel: usb 4-1.1: Product: Razer Lycosa
Feb 14 13:19:53 linux-ytaf kernel: usb 4-1.1: Manufacturer: Razer
Feb 14 13:19:53 linux-ytaf kernel: usbcore: registered new interface driver usbhid
Feb 14 13:19:53 linux-ytaf kernel: usbhid: USB HID core driver
Feb 14 13:19:53 linux-ytaf kernel: input: Razer Razer Lycosa as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1:1.0/0003:1532:0109.0001/input/input6
Feb 14 13:19:53 linux-ytaf kernel: usb 1-1.4: New USB device found, idVendor=06a3, idProduct=0ccb
Feb 14 13:19:53 linux-ytaf kernel: usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 14 13:19:53 linux-ytaf kernel: usb 1-1.4: Product: Cyborg R.A.T.7 Mouse
Feb 14 13:19:53 linux-ytaf kernel: usb 1-1.4: Manufacturer: Saitek
Feb 14 13:19:53 linux-ytaf kernel: hid-generic 0003:1532:0109.0001: input,hidraw0: USB HID v1.10 Keyboard [Razer Razer Lycosa] on usb-0000:00:1d.0-1.1/input0
Feb 14 13:19:53 linux-ytaf kernel: input: Razer Razer Lycosa as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1:1.1/0003:1532:0109.0002/input/input7
Feb 14 13:19:53 linux-ytaf kernel: hid-generic 0003:1532:0109.0002: input,hidraw1: USB HID v1.10 Device [Razer Razer Lycosa] on usb-0000:00:1d.0-1.1/input1
Feb 14 13:19:53 linux-ytaf kernel: Console: switching to colour frame buffer device 210x65
Feb 14 13:19:53 linux-ytaf kernel: nouveau 0000:02:00.0: fb0: nouveaufb frame buffer device
Feb 14 13:19:53 linux-ytaf kernel: nouveau 0000:02:00.0: registered panic notifier
Feb 14 13:19:53 linux-ytaf kernel: [drm] Initialized nouveau 1.2.2 20120801 for 0000:02:00.0 on minor 0
Feb 14 13:19:53 linux-ytaf kernel: [drm] Memory usable by graphics device = 2048M
Feb 14 13:19:53 linux-ytaf kernel: [drm] Replacing VGA console driver
Feb 14 13:19:53 linux-ytaf kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Feb 14 13:19:53 linux-ytaf kernel: [drm] Driver supports precise vblank timestamp query.
Feb 14 13:19:53 linux-ytaf kernel: vgaarb: device changed decodes: PCI:0000:02:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
Feb 14 13:19:53 linux-ytaf kernel: [drm] Initialized i915 1.6.0 20150327 for 0000:00:02.0 on minor 1
Feb 14 13:19:53 linux-ytaf kernel: [drm] GMBUS [i915 gmbus vga] timed out, falling back to bit banging on pin 2
Feb 14 13:19:53 linux-ytaf kernel: i915 0000:00:02.0: No connectors reported connected with modes
Feb 14 13:19:53 linux-ytaf kernel: [drm] Cannot find any crtc or sizes - going 1024x768
Feb 14 13:19:53 linux-ytaf kernel: i915 0000:00:02.0: fb1: inteldrmfb frame buffer device
Feb 14 13:19:53 linux-ytaf kernel: PM: Starting manual resume from disk
Feb 14 13:19:53 linux-ytaf kernel: PM: Hibernation image partition 8:18 present
Feb 14 13:19:53 linux-ytaf kernel: PM: Looking for hibernation image.
Feb 14 13:19:53 linux-ytaf kernel: PM: Image not found (code -22)
Feb 14 13:19:53 linux-ytaf kernel: PM: Hibernation image not present or could not be loaded.
Feb 14 13:19:53 linux-ytaf kernel: BTRFS info (device sdb3): disk space caching is enabled
Feb 14 13:19:53 linux-ytaf kernel: BTRFS: has skinny extents
Feb 14 13:19:54 linux-ytaf kernel: scsi 8:0:0:0: Direct-Access     TOSHIBA  TransMemory      PMAP PQ: 0 ANSI: 6
Feb 14 13:19:54 linux-ytaf kernel: sd 8:0:0:0: Attached scsi generic sg3 type 0
Feb 14 13:19:54 linux-ytaf kernel: sd 8:0:0:0: [sdc] 30228480 512-byte logical blocks: (15.4 GB/14.4 GiB)
Feb 14 13:19:54 linux-ytaf kernel: sd 8:0:0:0: [sdc] Write Protect is off
Feb 14 13:19:54 linux-ytaf kernel: sd 8:0:0:0: [sdc] Mode Sense: 45 00 00 00
Feb 14 13:19:54 linux-ytaf kernel: sd 8:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Feb 14 13:19:54 linux-ytaf kernel:  sdc: sdc1
Feb 14 13:19:54 linux-ytaf kernel: sd 8:0:0:0: [sdc] Attached SCSI removable disk
Feb 14 13:19:54 linux-ytaf systemd-journal[187]: Journal stopped
Feb 14 13:19:56 linux-ytaf systemd-journal[479]: Runtime journal is using 8.0M (max allowed 394.0M, trying to leave 591.0M free of 3.8G available → current limit 394.0M).
Feb 14 13:19:56 linux-ytaf systemd-journal[479]: Runtime journal is using 8.0M (max allowed 394.0M, trying to leave 591.0M free of 3.8G available → current limit 394.0M).
Feb 14 13:19:56 linux-ytaf kernel: random: nonblocking pool is initialized
Feb 14 13:19:56 linux-ytaf systemd[1]: RTC configured in localtime, applying delta of 60 minutes to system time.
Feb 14 13:19:56 linux-ytaf systemd-journal[479]: Journal started
Feb 14 13:19:56 linux-ytaf systemd-udevd[498]: starting version 210
Feb 14 13:19:56 linux-ytaf systemd-udevd[498]: Network interface NamePolicy= disabled on kernel commandline, ignoring.
Feb 14 13:19:56 linux-ytaf systemd-udevd[498]: invalid key/value pair in file /usr/lib/udev/rules.d/51-android.rules on line 115,starting at character 57 ('')
Feb 14 13:19:56 linux-ytaf kernel: BTRFS info (device sdb3): disk space caching is enabled
Feb 14 13:19:56 linux-ytaf kernel: input: PC Speaker as /devices/platform/pcspkr/input/input8
Feb 14 13:19:56 linux-ytaf kernel: thermal LNXTHERM:00: registered as thermal_zone0
Feb 14 13:19:56 linux-ytaf kernel: ACPI: Thermal Zone [TZ00] (28 C)
Feb 14 13:19:56 linux-ytaf kernel: thermal LNXTHERM:01: registered as thermal_zone1
Feb 14 13:19:56 linux-ytaf kernel: ACPI: Thermal Zone [TZ01] (30 C)
Feb 14 13:19:56 linux-ytaf mtp-probe[646]: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4"
Feb 14 13:19:56 linux-ytaf mtp-probe[647]: checking bus 4, device 3: "/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1"
Feb 14 13:19:56 linux-ytaf mtp-probe[646]: bus: 1, device: 3 was not an MTP device
Feb 14 13:19:56 linux-ytaf mtp-probe[647]: bus: 4, device: 3 was not an MTP device
Feb 14 13:19:57 linux-ytaf kernel: AVX version of gcm_enc/dec engaged.
Feb 14 13:19:57 linux-ytaf kernel: AES CTR mode by8 optimization enabled
Feb 14 13:19:57 linux-ytaf kernel: input: Saitek Cyborg R.A.T.7 Mouse as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/0003:06A3:0CCB.0003/input/input9
Feb 14 13:19:57 linux-ytaf kernel: saitek 0003:06A3:0CCB.0003: input,hidraw2: USB HID v1.11 Mouse [Saitek Cyborg R.A.T.7 Mouse] on usb-0000:00:1a.0-1.4/input0
Feb 14 13:19:57 linux-ytaf kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Feb 14 13:19:57 linux-ytaf mtp-probe[680]: checking bus 5, device 2: "/sys/devices/pci0000:00/0000:00:1c.5/0000:05:00.0/usb5/5-2"
Feb 14 13:19:57 linux-ytaf mtp-probe[680]: bus: 5, device: 2 was not an MTP device
Feb 14 13:19:57 linux-ytaf kernel: snd_hda_intel 0000:00:1b.0: enabling device (0000 -> 0002)
Feb 14 13:19:57 linux-ytaf kernel: snd_hda_intel 0000:02:00.1: enabling device (0000 -> 0002)
Feb 14 13:19:57 linux-ytaf kernel: snd_hda_intel 0000:02:00.1: Disabling MSI
Feb 14 13:19:57 linux-ytaf kernel: snd_hda_intel 0000:02:00.1: Handle VGA-switcheroo audio client
Feb 14 13:19:57 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC889: line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line
Feb 14 13:19:57 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Feb 14 13:19:57 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
Feb 14 13:19:57 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
Feb 14 13:19:57 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    dig-out=0x11/0x1e
Feb 14 13:19:57 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    inputs:
Feb 14 13:19:57 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:      Front Mic=0x19
Feb 14 13:19:57 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:      Rear Mic=0x18
Feb 14 13:19:57 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:      Line=0x1a
Feb 14 13:19:57 linux-ytaf kernel: asus_wmi: ASUS WMI generic driver loaded
Feb 14 13:19:57 linux-ytaf kernel: asus_wmi: Initialization: 0x0
Feb 14 13:19:57 linux-ytaf kernel: asus_wmi: BIOS WMI version: 0.9
Feb 14 13:19:57 linux-ytaf kernel: asus_wmi: SFUN value: 0x0
Feb 14 13:19:57 linux-ytaf kernel: input: Eee PC WMI hotkeys as /devices/platform/eeepc-wmi/input/input11
Feb 14 13:19:57 linux-ytaf kernel: asus_wmi: Disabling ACPI video driver
Feb 14 13:19:57 linux-ytaf kernel: input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
Feb 14 13:19:57 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20150410/utaddress-254)
Feb 14 13:19:57 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 13:19:57 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150410/utaddress-254)
Feb 14 13:19:57 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150410/utaddress-254)
Feb 14 13:19:57 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 13:19:57 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150410/utaddress-254)
Feb 14 13:19:57 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150410/utaddress-254)
Feb 14 13:19:57 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 13:19:57 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150410/utaddress-254)
Feb 14 13:19:57 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150410/utaddress-254)
Feb 14 13:19:57 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 13:19:57 linux-ytaf kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
Feb 14 13:19:57 linux-ytaf kernel: pps_core: LinuxPPS API ver. 1 registered
Feb 14 13:19:57 linux-ytaf kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
Feb 14 13:19:57 linux-ytaf kernel: PTP clock support registered
Feb 14 13:19:57 linux-ytaf kernel: input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
Feb 14 13:19:57 linux-ytaf kernel: input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input13
Feb 14 13:19:57 linux-ytaf kernel: input: HDA Intel PCH Line Out Front as /devices/pci0000:00/0000:00:1b.0/sound/card0/input14
Feb 14 13:19:57 linux-ytaf kernel: input: HDA Intel PCH Line Out Surround as /devices/pci0000:00/0000:00:1b.0/sound/card0/input15
Feb 14 13:19:57 linux-ytaf kernel: input: HDA Intel PCH Line Out CLFE as /devices/pci0000:00/0000:00:1b.0/sound/card0/input16
Feb 14 13:19:57 linux-ytaf kernel: input: HDA Intel PCH Line Out Side as /devices/pci0000:00/0000:00:1b.0/sound/card0/input17
Feb 14 13:19:57 linux-ytaf kernel: input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input18
Feb 14 13:19:57 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000580-0x000000000000059F conflicts with OpRegion 0x0000000000000580-0x000000000000058F (\_SB_.PCI0.SBUS.SMBI) (20150410/utaddress-254)
Feb 14 13:19:57 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000580-0x000000000000059F conflicts with OpRegion 0x0000000000000580-0x000000000000059F (\_SB_.PCI0.SMB_.SMIO) (20150410/utaddress-254)
Feb 14 13:19:57 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 13:19:57 linux-ytaf kernel: e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
Feb 14 13:19:57 linux-ytaf kernel: e1000e: Copyright(c) 1999 - 2014 Intel Corporation.
Feb 14 13:19:57 linux-ytaf kernel: e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
Feb 14 13:19:57 linux-ytaf kernel: iTCO_vendor_support: vendor-support=0
Feb 14 13:19:57 linux-ytaf kernel: iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
Feb 14 13:19:57 linux-ytaf kernel: iTCO_wdt: Found a Cougar Point TCO device (Version=2, TCOBASE=0x0460)
Feb 14 13:19:57 linux-ytaf kernel: iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
Feb 14 13:19:57 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: registered PHC clock
Feb 14 13:19:57 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) c8:60:00:09:38:76
Feb 14 13:19:57 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
Feb 14 13:19:57 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: FFFFFF-0FF
Feb 14 13:19:57 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input19
Feb 14 13:19:57 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input20
Feb 14 13:19:57 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input21
Feb 14 13:19:57 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input22
Feb 14 13:19:57 linux-ytaf kernel: Adding 2104316k swap on /dev/sdb2.  Priority:-1 extents:1 across:2104316k FS
Feb 14 13:19:58 linux-ytaf kernel: FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Feb 14 13:19:58 linux-ytaf systemd-fsck[778]: /sbin/fsck.xfs: XFS file system.
Feb 14 13:19:58 linux-ytaf kernel: SGI XFS with ACLs, security attributes, realtime, no debug enabled
Feb 14 13:19:58 linux-ytaf kernel: XFS (sdb4): Mounting V5 Filesystem
Feb 14 13:19:59 linux-ytaf kernel: XFS (sdb4): Starting recovery (logdev: internal)
Feb 14 13:20:01 linux-ytaf kernel: XFS (sdb4): Ending recovery (logdev: internal)
Feb 14 13:20:02 linux-ytaf systemd-journal[479]: Permanent journal is using 64.0M (max allowed 4.0G, trying to leave 4.0G free of 32.8G available → current limit 4.0G).
Feb 14 13:20:02 linux-ytaf systemd-journal[479]: Time spent on flushing to /var is 32.809ms for 1031 entries.
Feb 14 13:20:02 linux-ytaf kernel: audit: type=1305 audit(1455452401.812:2): audit_pid=800 old=0 auid=4294967295 ses=4294967295 res=1
Feb 14 13:20:01 linux-ytaf auditd[800]: Started dispatcher: /sbin/audispd pid: 805
Feb 14 13:20:01 linux-ytaf audispd[805]: priority_boost_parser called with: 4
Feb 14 13:20:01 linux-ytaf audispd[805]: max_restarts_parser called with: 10
Feb 14 13:20:01 linux-ytaf audispd[805]: No plugins found, exiting
Feb 14 13:20:01 linux-ytaf auditd[800]: Init complete, auditd 2.3.6 listening for events (startup state enable)
Feb 14 13:20:03 linux-ytaf auditctl[801]: No rules
Feb 14 13:20:03 linux-ytaf auditctl[801]: AUDIT_STATUS: enabled=1 flag=1 pid=800 rate_limit=0 backlog_limit=320 lost=0 backlog=1
Feb 14 13:20:03 linux-ytaf boot.apparmor[809]: Starting AppArmor ..done
Feb 14 13:20:03 linux-ytaf dbus-daemon[976]: Unknown username "srvGeoClue" in message bus configuration file
Feb 14 13:20:03 linux-ytaf alsactl[987]: /usr/sbin/alsactl: load_state:1683: Cannot open /var/lib/alsa/asound.state for reading: No such file or directory
Feb 14 13:20:03 linux-ytaf alsactl[987]: Found hardware: "HDA-Intel" "Intel CougarPoint HDMI" "HDA:10ec0889,1043846b,00100004 HDA:80862805,80860101,00100000" "0x1043" "0x84dc"
Feb 14 13:20:03 linux-ytaf alsactl[987]: Hardware is initialized using a generic method
Feb 14 13:20:03 linux-ytaf alsactl[987]: Found hardware: "HDA-Intel" "Nvidia GPU 40 HDMI/DP" "HDA:10de0040,00000000,00100100" "0x0000" "0x0000"
Feb 14 13:20:03 linux-ytaf alsactl[987]: Hardware is initialized using a generic method
Feb 14 13:20:03 linux-ytaf avahi-daemon[977]: Found user 'avahi' (UID 486) and group 'avahi' (GID 485).
Feb 14 13:20:03 linux-ytaf avahi-daemon[977]: Successfully dropped root privileges.
Feb 14 13:20:03 linux-ytaf avahi-daemon[977]: avahi-daemon 0.6.31 starting up.
Feb 14 13:20:03 linux-ytaf avahi-daemon[977]: Loading service file /etc/avahi/services/sftp-ssh.service.
Feb 14 13:20:03 linux-ytaf avahi-daemon[977]: Loading service file /etc/avahi/services/ssh.service.
Feb 14 13:20:03 linux-ytaf avahi-daemon[977]: Network interface enumeration completed.
Feb 14 13:20:03 linux-ytaf avahi-daemon[977]: Registering HINFO record with values 'X86_64'/'LINUX'.
Feb 14 13:20:03 linux-ytaf avahi-daemon[977]: Server startup complete. Host name is linux-ytaf.local. Local service cookie is 2310764381.
Feb 14 13:20:03 linux-ytaf avahi-daemon[977]: Service "linux-ytaf" (/etc/avahi/services/ssh.service) successfully established.
Feb 14 13:20:03 linux-ytaf avahi-daemon[977]: Service "linux-ytaf" (/etc/avahi/services/sftp-ssh.service) successfully established.
Feb 14 13:20:03 linux-ytaf display-manager[1006]: /etc/vconsole.conf available
Feb 14 13:20:03 linux-ytaf display-manager[1006]: KEYMAP: de-latin1-nodeadkeys
Feb 14 13:20:03 linux-ytaf display-manager[1006]: Command: localectl set-keymap de-latin1-nodeadkeys
Feb 14 13:20:03 linux-ytaf display-manager[1006]: I: Using systemd /usr/share/systemd/kbd-model-map mapping
Feb 14 13:20:03 linux-ytaf dbus[976]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service'
Feb 14 13:20:03 linux-ytaf dbus[976]: [system] Successfully activated service 'org.freedesktop.locale1'
Feb 14 13:20:03 linux-ytaf smartd[983]: smartd 6.2 2013-11-07 r3856 [x86_64-linux-4.1.15-8-default] (SUSE RPM)
Feb 14 13:20:03 linux-ytaf smartd[983]: Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
Feb 14 13:20:03 linux-ytaf smartd[983]: Opened configuration file /etc/smartd.conf
Feb 14 13:20:03 linux-ytaf smartd[983]: Drive: DEVICESCAN, implied '-a' Directive on line 26 of file /etc/smartd.conf
Feb 14 13:20:03 linux-ytaf smartd[983]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
Feb 14 13:20:03 linux-ytaf smartd[983]: Device: /dev/sda, type changed from 'scsi' to 'sat'
Feb 14 13:20:03 linux-ytaf smartd[983]: Device: /dev/sda [SAT], opened
Feb 14 13:20:03 linux-ytaf smartd[983]: Device: /dev/sda [SAT], SAMSUNG SSD 830 Series, S/N:S0Z4NEAC906195, WWN:5-002538-043584d30, FW:CXM03B1Q, 256 GB
Feb 14 13:20:03 linux-ytaf smartd[983]: Device: /dev/sda [SAT], found in smartd database: Samsung based SSDs
Feb 14 13:20:03 linux-ytaf smartd[983]: Device: /dev/sda [SAT], can't monitor Current_Pending_Sector count - no Attribute 197
Feb 14 13:20:03 linux-ytaf smartd[983]: Device: /dev/sda [SAT], can't monitor Offline_Uncorrectable count - no Attribute 198
Feb 14 13:20:03 linux-ytaf smartd[983]: Device: /dev/sda [SAT], is SMART capable. Adding to "monitor" list.
Feb 14 13:20:03 linux-ytaf smartd[983]: Device: /dev/sda [SAT], state read from /var/lib/smartmontools/smartd.SAMSUNG_SSD_830_Series-S0Z4NEAC906195.ata.state
Feb 14 13:20:03 linux-ytaf kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
Feb 14 13:20:03 linux-ytaf ModemManager[979]: <info>  ModemManager (version 1.4.10) starting in system bus...
Feb 14 13:20:03 linux-ytaf kernel: nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
Feb 14 13:20:03 linux-ytaf dbus[976]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Feb 14 13:20:03 linux-ytaf SuSEfirewall2[1073]: Firewall rules set to CLOSE.
Feb 14 13:20:03 linux-ytaf smartd[983]: Device: /dev/sdb, type changed from 'scsi' to 'sat'
Feb 14 13:20:03 linux-ytaf smartd[983]: Device: /dev/sdb [SAT], opened
Feb 14 13:20:03 linux-ytaf smartd[983]: Device: /dev/sdb [SAT], TOSHIBA HDWD110, S/N:Y5GDEMGFS, WWN:5-000039-fe7c5a79c, FW:MS2OA8J0, 1.00 TB
Feb 14 13:20:03 linux-ytaf smartd[983]: Device: /dev/sdb [SAT], not found in smartd database.
Feb 14 13:20:03 linux-ytaf kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Feb 14 13:20:03 linux-ytaf kernel: No iBFT detected.
Feb 14 13:20:03 linux-ytaf polkitd[1075]: Started polkitd version 0.113
Feb 14 13:20:04 linux-ytaf polkitd[1075]: Loading rules from directory /etc/polkit-1/rules.d
Feb 14 13:20:04 linux-ytaf polkitd[1075]: Loading rules from directory /usr/share/polkit-1/rules.d
Feb 14 13:20:04 linux-ytaf polkitd[1075]: Finished loading, compiling and executing 3 rules
Feb 14 13:20:04 linux-ytaf dbus[976]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Feb 14 13:20:04 linux-ytaf polkitd[1075]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
Feb 14 13:20:05 linux-ytaf smartd[983]: Device: /dev/sdb [SAT], is SMART capable. Adding to "monitor" list.
Feb 14 13:20:05 linux-ytaf smartd[983]: Device: /dev/sdb [SAT], state read from /var/lib/smartmontools/smartd.TOSHIBA_HDWD110-Y5GDEMGFS.ata.state
Feb 14 13:20:05 linux-ytaf smartd[983]: Monitoring 2 ATA and 0 SCSI devices
Feb 14 13:20:06 linux-ytaf ModemManager[979]: <info>  Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin
Feb 14 13:20:06 linux-ytaf smartd[983]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.SAMSUNG_SSD_830_Series-S0Z4NEAC906195.ata.state
Feb 14 13:20:06 linux-ytaf smartd[983]: Device: /dev/sdb [SAT], state written to /var/lib/smartmontools/smartd.TOSHIBA_HDWD110-Y5GDEMGFS.ata.state
Feb 14 13:20:06 linux-ytaf logger[1080]: /etc/init.d/xdm: No changes for /etc/X11/xdm/Xservers
Feb 14 13:20:06 linux-ytaf logger[1080]: /etc/init.d/xdm: No changes for /etc/X11/xdm/xdm-config
Feb 14 13:20:07 linux-ytaf sddm[1252]: Starting...
Feb 14 13:20:07 linux-ytaf sddm[1252]: Display server starting...
Feb 14 13:20:07 linux-ytaf display-manager[1006]: Starting service sddm..done
Feb 14 13:20:09 linux-ytaf sddm[1252]: Display server started.
Feb 14 13:20:09 linux-ytaf sddm[1252]: Socket server starting...
Feb 14 13:20:09 linux-ytaf sddm[1252]: Greeter starting...
Feb 14 13:20:09 linux-ytaf sddm-helper[1271]: [PAM] Starting...
Feb 14 13:20:09 linux-ytaf sddm-helper[1271]: [PAM] Authenticating...
Feb 14 13:20:09 linux-ytaf sddm-helper[1271]: [PAM] returning.
Feb 14 13:20:09 linux-ytaf sddm-helper[1271]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
Feb 14 13:20:09 linux-ytaf systemd[1273]: pam_unix(systemd-user:session): session opened for user sddm by (uid=0)
Feb 14 13:20:09 linux-ytaf sddm[1252]: Greeter session started successfully
Feb 14 13:20:09 linux-ytaf kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Feb 14 13:20:09 linux-ytaf wickedd-dhcp4[1082]: eth0: Request to acquire DHCPv4 lease with UUID f570c056-8a30-0f00-3d04-000004000000
Feb 14 13:20:10 linux-ytaf kernel: NET: Registered protocol family 17
Feb 14 13:20:10 linux-ytaf wickedd-dhcp4[1082]: eth0: Committed DHCPv4 lease with address 192.168.178.12 (lease time 864000 sec, renew in 432000 sec, rebind in 756000 sec)
Feb 14 13:20:10 linux-ytaf avahi-daemon[977]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.178.12.
Feb 14 13:20:10 linux-ytaf avahi-daemon[977]: New relevant interface eth0.IPv4 for mDNS.
Feb 14 13:20:10 linux-ytaf avahi-daemon[977]: Registering new address record for 192.168.178.12 on eth0.IPv4.
Feb 14 13:20:10 linux-ytaf wickedd[1085]: eth0: Notified neighbours about IP address 192.168.178.12
Feb 14 13:20:10 MM-Home wicked[1087]: lo              up
Feb 14 13:20:10 MM-Home wicked[1087]: eth0            up
Feb 14 13:20:10 MM-Home echo[1461]: Starting mail service (Postfix)
Feb 14 13:20:10 MM-Home iscsiadm[1463]: iscsiadm: No records found
Feb 14 13:20:10 MM-Home SuSEfirewall2[1491]: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Feb 14 13:20:10 MM-Home SuSEfirewall2[1501]: using default zone 'ext' for interface eth0
Feb 14 13:20:10 MM-Home ntpd[1479]: ntpd 4.2.8p4@1.3265-o Thu Dec 17 05:32:52 UTC 2015 (1): Starting
Feb 14 13:20:10 MM-Home ntpd[1479]: Command line: /usr/sbin/ntpd -p /var/run/ntp/ntpd.pid -g -u ntp:ntp -c /etc/ntp.conf
Feb 14 13:20:10 MM-Home sntp[1631]: sntp 4.2.8p4@1.3265-o Thu Dec 17 05:32:29 UTC 2015 (1)
Feb 14 13:20:10 MM-Home sntp[1631]: kod_init_kod_db(): Cannot open KoD db file /var/db/ntp-kod: No such file or directory
Feb 14 13:20:10 MM-Home start-ntpd[1467]: Starting network time protocol daemon (NTPD)sntp 4.2.8p4@1.3265-o Thu Dec 17 05:32:29 UTC 2015 (1)
Feb 14 13:20:10 MM-Home start-ntpd[1467]: kod_init_kod_db(): Cannot open KoD db file /var/db/ntp-kod: No such file or directory
Feb 14 13:20:10 MM-Home sntp[1631]: 2016-02-14 13:20:10.939592 (-0100) +0.39306 +/- 0.306196 192.168.178.1 s3 no-leap
Feb 14 13:20:11 MM-Home ntpd[1629]: proto: precision = 0.042 usec (-24)
Feb 14 13:20:11 MM-Home start-ntpd[1467]: 2016-02-14 13:20:10.939592 (-0100) +0.39306 +/- 0.306196 192.168.178.1 s3 no-leap
Feb 14 13:20:11 MM-Home ntpd[1629]: switching logging to file /var/log/ntp
Feb 14 13:20:11 MM-Home /usr/sbin/start-ntpd[1652]: runtime configuration: server 192.168.178.1
Feb 14 13:20:11 MM-Home postfix/postfix-script[1660]: starting the Postfix mail system
Feb 14 13:20:11 MM-Home SuSEfirewall2[1661]: Firewall rules successfully set
Feb 14 13:20:11 MM-Home postfix/master[1663]: daemon started -- version 2.11.6, configuration /etc/postfix
Feb 14 13:20:11 MM-Home cron[1681]: (CRON) INFO (RANDOM_DELAY will be scaled with factor 88% if used.)
Feb 14 13:20:11 MM-Home cron[1681]: (CRON) INFO (running with inotify support)
Feb 14 13:20:11 MM-Home dbus[976]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
Feb 14 13:20:11 MM-Home udisksd[1685]: udisks daemon version 2.1.6 starting
Feb 14 13:20:12 MM-Home dbus[976]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Feb 14 13:20:12 MM-Home udisksd[1685]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Feb 14 13:20:12 MM-Home dbus[976]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
Feb 14 13:20:12 MM-Home dbus[976]: [system] Successfully activated service 'org.freedesktop.UPower'
Feb 14 13:20:19 MM-Home sddm[1252]: Message received from greeter: Login
Feb 14 13:20:19 MM-Home sddm[1252]: Reading from "/usr/share/xsessions/plasma5.desktop"
Feb 14 13:20:19 MM-Home sddm[1252]: Session "/usr/share/xsessions/plasma5.desktop" selected, command: "/usr/bin/startkde"
Feb 14 13:20:19 MM-Home sddm-helper[1718]: [PAM] Starting...
Feb 14 13:20:19 MM-Home sddm-helper[1718]: [PAM] Authenticating...
Feb 14 13:20:19 MM-Home sddm-helper[1718]: [PAM] Preparing to converse...
Feb 14 13:20:19 MM-Home sddm-helper[1718]: [PAM] Conversation with 1 messages
Feb 14 13:20:19 MM-Home sddm-helper[1718]: [PAM] returning.
Feb 14 13:20:19 MM-Home sddm[1252]: Authenticated successfully
Feb 14 13:20:19 MM-Home sddm-helper[1718]: pam_unix(sddm:session): session opened for user marc by (uid=0)
Feb 14 13:20:19 MM-Home systemd[1719]: pam_unix(systemd-user:session): session opened for user marc by (uid=0)
Feb 14 13:20:19 MM-Home sddm-helper[1721]: Adding cookie to "/home/marc/.Xauthority"
Feb 14 13:20:19 MM-Home sddm-helper[1271]: [PAM] Ended.
Feb 14 13:20:19 MM-Home sddm[1252]: Auth: sddm-helper exited successfully
Feb 14 13:20:19 MM-Home sddm[1252]: Greeter stopped.
Feb 14 13:20:19 MM-Home sddm[1252]: Session started
Feb 14 13:20:23 MM-Home polkitd[1075]: Registered Authentication Agent for unix-session:2 (system bus name :1.33 [/usr/lib64/libexec/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale de_DE.UTF-8)
Feb 14 13:20:23 MM-Home dbus[976]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service'
Feb 14 13:20:24 MM-Home dbus[976]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Feb 14 13:20:24 MM-Home rtkit-daemon[1875]: Successfully called chroot.
Feb 14 13:20:24 MM-Home rtkit-daemon[1875]: Successfully dropped privileges.
Feb 14 13:20:24 MM-Home rtkit-daemon[1875]: Successfully limited resources.
Feb 14 13:20:24 MM-Home rtkit-daemon[1875]: Running.
Feb 14 13:20:24 MM-Home rtkit-daemon[1875]: Watchdog thread running.
Feb 14 13:20:24 MM-Home rtkit-daemon[1875]: Canary thread running.
Feb 14 13:20:24 MM-Home rtkit-daemon[1875]: Successfully made thread 1874 of process 1874 (/usr/bin/pulseaudio) owned by 'marc' high priority at nice level -11.
Feb 14 13:20:24 MM-Home rtkit-daemon[1875]: Supervising 1 threads of 1 processes of 1 users.
Feb 14 13:20:24 MM-Home dbus[976]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Feb 14 13:20:24 MM-Home org.kde.powerdevil.backlighthelper[976]: powerdevil: no kernel backlight interface found
Feb 14 13:20:25 MM-Home dbus[976]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Feb 14 13:20:26 MM-Home rtkit-daemon[1875]: Supervising 1 threads of 1 processes of 1 users.
Feb 14 13:20:26 MM-Home rtkit-daemon[1875]: Successfully made thread 1898 of process 1874 (/usr/bin/pulseaudio) owned by 'marc' RT at priority 5.
Feb 14 13:20:26 MM-Home rtkit-daemon[1875]: Supervising 2 threads of 1 processes of 1 users.
Feb 14 13:20:27 MM-Home rtkit-daemon[1875]: Supervising 2 threads of 1 processes of 1 users.
Feb 14 13:20:27 MM-Home rtkit-daemon[1875]: Successfully made thread 1899 of process 1874 (/usr/bin/pulseaudio) owned by 'marc' RT at priority 5.
Feb 14 13:20:27 MM-Home rtkit-daemon[1875]: Supervising 3 threads of 1 processes of 1 users.
Feb 14 13:20:27 MM-Home rtkit-daemon[1875]: Supervising 3 threads of 1 processes of 1 users.
Feb 14 13:20:27 MM-Home rtkit-daemon[1875]: Successfully made thread 1900 of process 1874 (/usr/bin/pulseaudio) owned by 'marc' RT at priority 5.
Feb 14 13:20:27 MM-Home rtkit-daemon[1875]: Supervising 4 threads of 1 processes of 1 users.
Feb 14 13:20:27 MM-Home dbus[976]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Feb 14 13:20:27 MM-Home bluetoothd[1901]: Bluetooth daemon 5.35
Feb 14 13:20:27 MM-Home dbus[976]: [system] Successfully activated service 'org.bluez'
Feb 14 13:20:27 MM-Home bluetoothd[1901]: Starting SDP server
Feb 14 13:20:27 MM-Home kernel: Bluetooth: Core ver 2.20
Feb 14 13:20:27 MM-Home kernel: NET: Registered protocol family 31
Feb 14 13:20:27 MM-Home kernel: Bluetooth: HCI device and connection manager initialized
Feb 14 13:20:27 MM-Home kernel: Bluetooth: HCI socket layer initialized
Feb 14 13:20:27 MM-Home kernel: Bluetooth: L2CAP socket layer initialized
Feb 14 13:20:27 MM-Home kernel: Bluetooth: SCO socket layer initialized
Feb 14 13:20:27 MM-Home dbus[976]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Feb 14 13:20:27 MM-Home bluetoothd[1901]: Bluetooth management interface 1.9 initialized
Feb 14 13:20:27 MM-Home kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Feb 14 13:20:27 MM-Home kernel: Bluetooth: BNEP filters: protocol multicast
Feb 14 13:20:27 MM-Home kernel: Bluetooth: BNEP socket layer initialized
Feb 14 13:20:27 MM-Home dbus[976]: [system] Successfully activated service 'org.freedesktop.hostname1'
Feb 14 13:20:29 MM-Home dbus[976]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service'
Feb 14 13:20:29 MM-Home PackageKit[1915]: daemon start
Feb 14 13:20:29 MM-Home dbus[976]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Feb 14 13:20:30 MM-Home PackageKit[1915]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 13:20:30 MM-Home PackageKit[1915]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 13:20:30 MM-Home PackageKit[1915]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 13:20:30 MM-Home PackageKit[1915]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 13:20:31 MM-Home PackageKit[1915]: refresh-cache transaction /1_ecdabaca from uid 1000 finished with failed after 1317ms
Feb 14 13:20:32 MM-Home PackageKit[1915]: refresh-cache transaction /2_babbaede from uid 1000 finished with failed after 282ms
Feb 14 13:20:32 MM-Home kernel: fuse init (API version 7.23)
Feb 14 13:20:49 MM-Home PackageKit[1915]: daemon quit
Feb 14 13:20:49 MM-Home packagekitd[1915]: (packagekitd:1915): GLib-CRITICAL **: Source ID 6 was not found when attempting to remove it
Feb 14 13:24:17 MM-Home kernel: nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
Feb 14 13:30:01 MM-Home cron[2210]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 13:30:01 MM-Home systemd[2211]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 13:30:01 MM-Home CRON[2210]: pam_unix(crond:session): session closed for user root
Feb 14 13:30:01 MM-Home systemd[2212]: pam_unix(systemd-user:session): session closed for user root
Feb 14 13:39:30 MM-Home su[2291]: (to root) marc on pts/1
Feb 14 13:39:30 MM-Home su[2291]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 13:39:30 MM-Home su[2291]: pam_unix(su:session): session closed for user root
Feb 14 13:39:30 MM-Home su[2296]: (to root) marc on pts/1
Feb 14 13:39:30 MM-Home su[2296]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 13:39:37 MM-Home dbus[976]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Feb 14 13:39:37 MM-Home dbus[976]: [system] Successfully activated service 'org.opensuse.Snapper'
Feb 14 13:39:46 MM-Home kernel: st: Version 20101219, fixed bufsize 32768, s/g segs 256
Feb 14 13:39:46 MM-Home kernel: BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Feb 14 13:39:46 MM-Home kernel: EDD information not available.
Feb 14 13:39:53 MM-Home kernel: BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Feb 14 13:39:53 MM-Home kernel: EDD information not available.
Feb 14 13:39:58 MM-Home kernel: ppdev: user-space parallel port driver
Feb 14 13:39:58 MM-Home kernel: lp: driver loaded but no devices found
Feb 14 13:39:58 MM-Home kernel: lp: driver loaded but no devices found
Feb 14 13:39:59 MM-Home kernel: lp: driver loaded but no devices found
Feb 14 13:40:01 MM-Home kernel: BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Feb 14 13:40:01 MM-Home kernel: EDD information not available.
Feb 14 13:40:02 MM-Home kernel: BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Feb 14 13:40:02 MM-Home kernel: EDD information not available.
Feb 14 13:40:24 MM-Home kernel: lp: driver loaded but no devices found
Feb 14 13:40:25 MM-Home kernel: lp: driver loaded but no devices found
Feb 14 13:40:25 MM-Home kernel: BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Feb 14 13:40:25 MM-Home kernel: EDD information not available.
Feb 14 13:41:12 MM-Home su[2296]: pam_unix(su:session): session closed for user root
Feb 14 13:43:56 MM-Home su[4105]: (to root) marc on pts/2
Feb 14 13:43:56 MM-Home su[4105]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 13:43:56 MM-Home su[4105]: pam_unix(su:session): session closed for user root
Feb 14 13:43:56 MM-Home su[4110]: (to root) marc on pts/2
Feb 14 13:43:56 MM-Home su[4110]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 13:43:59 MM-Home dbus[976]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Feb 14 13:43:59 MM-Home dbus[976]: [system] Successfully activated service 'org.opensuse.Snapper'
Feb 14 13:44:07 MM-Home kernel: BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Feb 14 13:44:07 MM-Home kernel: EDD information not available.
Feb 14 13:44:14 MM-Home kernel: BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Feb 14 13:44:14 MM-Home kernel: EDD information not available.
Feb 14 13:44:19 MM-Home kernel: lp: driver loaded but no devices found
Feb 14 13:44:19 MM-Home kernel: lp: driver loaded but no devices found
Feb 14 13:44:20 MM-Home kernel: lp: driver loaded but no devices found
Feb 14 13:44:22 MM-Home kernel: BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Feb 14 13:44:22 MM-Home kernel: EDD information not available.
Feb 14 13:44:23 MM-Home kernel: BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Feb 14 13:44:23 MM-Home kernel: EDD information not available.
Feb 14 13:45:01 MM-Home cron[5247]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 13:45:01 MM-Home systemd[5248]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 13:45:01 MM-Home CRON[5247]: pam_unix(crond:session): session closed for user root
Feb 14 13:45:01 MM-Home systemd[5249]: pam_unix(systemd-user:session): session closed for user root
Feb 14 13:48:56 MM-Home dbus[976]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Feb 14 13:48:56 MM-Home dbus[976]: [system] Successfully activated service 'org.opensuse.Snapper'
Feb 14 13:49:02 MM-Home su[4110]: pam_unix(su:session): session closed for user root
Feb 14 13:49:13 MM-Home polkitd[1075]: Unregistered Authentication Agent for unix-session:2 (system bus name :1.33, object path /org/kde/PolicyKit1/AuthenticationAgent, locale de_DE.UTF-8)
Feb 14 13:49:13 MM-Home sddm[1252]: Auth: sddm-helper crashed (exit code 15)
Feb 14 13:49:13 MM-Home sddm[1252]: Authentication error: "Process crashed"
Feb 14 13:49:13 MM-Home sddm[1252]: Auth: sddm-helper exited with 15
Feb 14 13:49:13 MM-Home sddm[1252]: Socket server stopping...
Feb 14 13:49:13 MM-Home sddm[1252]: Socket server stopped.
Feb 14 13:49:13 MM-Home sddm[1252]: Display server stopping...
Feb 14 13:49:13 MM-Home avahi-daemon[977]: Got SIGTERM, quitting.
Feb 14 13:49:13 MM-Home avahi-daemon[977]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.178.12.
Feb 14 13:49:13 MM-Home avahi-daemon[977]: avahi-daemon 0.6.31 exiting.
Feb 14 13:49:13 MM-Home smartd[983]: smartd received signal 15: Terminated
Feb 14 13:49:13 MM-Home smartd[983]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.SAMSUNG_SSD_830_Series-S0Z4NEAC906195.ata.state
Feb 14 13:49:13 MM-Home smartd[983]: Device: /dev/sdb [SAT], state written to /var/lib/smartmontools/smartd.TOSHIBA_HDWD110-Y5GDEMGFS.ata.state
Feb 14 13:49:13 MM-Home smartd[983]: smartd is exiting (exit status 0)
Feb 14 13:49:13 MM-Home bluetoothd[1901]: Terminating
Feb 14 13:49:13 MM-Home bluetoothd[1901]: Stopping SDP server
Feb 14 13:49:13 MM-Home bluetoothd[1901]: Exit
Feb 14 13:49:13 MM-Home ModemManager[979]: <info>  Caught signal, shutting down...
Feb 14 13:49:13 MM-Home ModemManager[979]: <info>  ModemManager is shut down
Feb 14 13:49:13 MM-Home org.kde.kglobalaccel[1769]: The X11 connection broke: I/O error (code 1)
Feb 14 13:49:13 MM-Home org.kde.kglobalaccel[1769]: XIO:  fatal IO error 6 (Kein passendes Gerät bzw. keine passende Adresse gefunden) on X server ":0"
Feb 14 13:49:13 MM-Home org.kde.kglobalaccel[1769]: after 398 requests (396 known processed) with 0 events remaining.
Feb 14 13:49:13 MM-Home ca.desrt.dconf[1769]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
Feb 14 13:49:13 MM-Home iscsiadm[5949]: iscsiadm: No matching sessions found
Feb 14 13:49:13 MM-Home systemd[1274]: pam_unix(systemd-user:session): session closed for user sddm
Feb 14 13:49:13 MM-Home systemd[1720]: pam_unix(systemd-user:session): session closed for user marc
Feb 14 13:49:13 MM-Home SuSEfirewall2[6001]: Not unloading firewall rules at system shutdown
Feb 14 13:49:13 MM-Home swapoff[5944]: swapoff: /dev/disk/by-partlabel/primary: swapoff failed: Invalid argument
Feb 14 13:49:13 MM-Home postfix/postfix-script[6014]: stopping the Postfix mail system
Feb 14 13:49:13 MM-Home postfix/master[1663]: terminating on signal 15
Feb 14 13:49:13 MM-Home wickedd-dhcp4[1082]: eth0: Request to release DHCPv4 lease with UUID f570c056-8a30-0f00-3d04-000004000000
Feb 14 13:49:13 MM-Home kernel: e1000e: eth0 NIC Link is Down
Feb 14 13:49:13 MM-Home wicked[6031]: eth0            device-ready
Feb 14 13:49:14 MM-Home sddm[1252]: Running display stop script  "/usr/share/sddm/scripts/Xstop"
Feb 14 13:49:14 MM-Home sddm[1252]: Removing display ":0" ...
Feb 14 13:49:14 MM-Home sddm[1252]: Adding new display on vt 7 ...
Feb 14 13:49:14 MM-Home sddm[1252]: Display server starting...
Feb 14 13:49:14 MM-Home sddm[1252]: Running: /usr/bin/X -nolisten tcp -auth /run/sddm/{34fdc7af-d931-450b-9d07-9ec81755dc7a} -background none -noreset -displayfd 18 vt7
Feb 14 13:49:18 MM-Home display-manager[5978]: Shutting down service sddm..done
Feb 14 13:49:20 MM-Home sddm[1252]: Running display setup script  "/etc/X11/xdm/Xsetup"
Feb 14 13:49:20 MM-Home sddm[1252]: Display server started.
Feb 14 13:49:20 MM-Home sddm[1252]: Socket server starting...
Feb 14 13:49:20 MM-Home sddm[1252]: Socket server started.
Feb 14 13:49:20 MM-Home sddm[1252]: Greeter starting...
Feb 14 13:49:20 MM-Home sddm[1252]: Adding cookie to "/run/sddm/{34fdc7af-d931-450b-9d07-9ec81755dc7a}"
Feb 14 13:49:20 MM-Home sddm[1252]: Signal received: SIGTERM
Feb 14 13:49:20 MM-Home sddm[1252]: Socket server stopping...
Feb 14 13:49:20 MM-Home sddm[1252]: Socket server stopped.
Feb 14 13:49:20 MM-Home sddm[1252]: Display server stopping...
Feb 14 13:49:20 MM-Home sddm-helper[6191]: [PAM] Starting...
Feb 14 13:49:20 MM-Home sddm-helper[6191]: [PAM] Authenticating...
Feb 14 13:49:20 MM-Home sddm-helper[6191]: [PAM] returning.
Feb 14 13:49:20 MM-Home sddm[1252]: Display server stopped.
Feb 14 13:49:20 MM-Home sddm[1252]: Running display stop script  "/usr/share/sddm/scripts/Xstop"
Feb 14 13:49:20 MM-Home sddm[1252]: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.
Feb 14 13:49:20 MM-Home systemd-backlight[6199]: Failed to get backlight or LED device 'backlight:acpi_video0': No such file or directory
Feb 14 13:49:20 MM-Home boot.apparmor[6200]: Unloading AppArmor profiles  ..done
Feb 14 13:49:20 MM-Home auditd[800]: The audit daemon is exiting.
Feb 14 13:49:20 MM-Home kernel: audit: type=1305 audit(1455454160.672:252): audit_pid=0 old=800 auid=4294967295 ses=4294967295 res=1
Feb 14 13:49:20 MM-Home kernel: audit: type=1131 audit(1455454160.676:253): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=' comm="auditd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 14 13:49:20 MM-Home umount[6234]: umount: /var/log: target is busy
Feb 14 13:49:20 MM-Home umount[6234]: (In some cases useful info about processes that
Feb 14 13:49:20 MM-Home umount[6234]: use the device is found by lsof(8) or fuser(1).)
Feb 14 13:49:20 MM-Home kernel: audit: type=1130 audit(1455454160.696:254): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=' comm="plymouth-poweroff" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 14 13:49:20 MM-Home kernel: XFS (sdb4): Unmounting Filesystem
Feb 14 13:49:20 MM-Home kernel: audit: type=1131 audit(1455454160.848:255): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=' comm="systemd-remount-fs" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 14 13:49:20 MM-Home kernel: audit: type=1131 audit(1455454160.848:256): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=' comm="systemd-readahead-replay" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 14 13:49:20 MM-Home kernel: audit: type=1131 audit(1455454160.848:257): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=' comm="systemd-readahead-collect" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 14 13:49:20 MM-Home kernel: audit: type=1130 audit(1455454160.848:258): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=' comm="halt-local" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 14 13:49:20 MM-Home systemd-journal[479]: Journal stopped
-- Reboot --
Feb 14 14:50:04 linux-ytaf systemd-journal[187]: Runtime journal is using 8.0M (max allowed 394.0M, trying to leave 591.0M free of 3.8G available → current limit 394.0M).
Feb 14 14:50:04 linux-ytaf systemd-journal[187]: Runtime journal is using 8.0M (max allowed 394.0M, trying to leave 591.0M free of 3.8G available → current limit 394.0M).
Feb 14 14:50:04 linux-ytaf kernel: microcode: CPU0 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 14:50:04 linux-ytaf kernel: Initializing cgroup subsys cpuset
Feb 14 14:50:04 linux-ytaf kernel: Initializing cgroup subsys cpu
Feb 14 14:50:04 linux-ytaf kernel: Initializing cgroup subsys cpuacct
Feb 14 14:50:04 linux-ytaf kernel: Linux version 4.1.15-8-default (geeko@buildhost) (gcc version 4.8.5 (SUSE Linux) ) #1 SMP PREEMPT Wed Jan 20 16:41:00 UTC 2016 (0e3b3ab)
Feb 14 14:50:04 linux-ytaf kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.1.15-8-default root=UUID=21024970-7a27-4114-8525-d8dd026f23b6 ro resume=/dev/sdb2 splash=silent quiet showopts
Feb 14 14:50:04 linux-ytaf kernel: e820: BIOS-provided physical RAM map:
Feb 14 14:50:04 linux-ytaf kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Feb 14 14:50:04 linux-ytaf kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
Feb 14 14:50:04 linux-ytaf kernel: BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable
Feb 14 14:50:04 linux-ytaf kernel: BIOS-e820: [mem 0x0000000020000000-0x00000000201fffff] reserved
Feb 14 14:50:04 linux-ytaf kernel: BIOS-e820: [mem 0x0000000020200000-0x000000003fffffff] usable
Feb 14 14:50:04 linux-ytaf kernel: BIOS-e820: [mem 0x0000000040000000-0x00000000401fffff] reserved
Feb 14 14:50:04 linux-ytaf kernel: BIOS-e820: [mem 0x0000000040200000-0x00000000ca38efff] usable
Feb 14 14:50:04 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ca38f000-0x00000000ca5f1fff] reserved
Feb 14 14:50:04 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ca5f2000-0x00000000ca679fff] ACPI NVS
Feb 14 14:50:04 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ca67a000-0x00000000ca93efff] reserved
Feb 14 14:50:04 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ca93f000-0x00000000cab83fff] ACPI NVS
Feb 14 14:50:04 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cab84000-0x00000000cab91fff] ACPI data
Feb 14 14:50:04 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cab92000-0x00000000cabbefff] ACPI NVS
Feb 14 14:50:04 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cabbf000-0x00000000cabc3fff] ACPI data
Feb 14 14:50:04 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cabc4000-0x00000000cac06fff] ACPI NVS
Feb 14 14:50:04 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cac07000-0x00000000caffffff] usable
Feb 14 14:50:04 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cb800000-0x00000000cf9fffff] reserved
Feb 14 14:50:04 linux-ytaf kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Feb 14 14:50:04 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Feb 14 14:50:04 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Feb 14 14:50:04 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Feb 14 14:50:04 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Feb 14 14:50:04 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Feb 14 14:50:04 linux-ytaf kernel: BIOS-e820: [mem 0x0000000100000000-0x000000022f5fffff] usable
Feb 14 14:50:04 linux-ytaf kernel: NX (Execute Disable) protection: active
Feb 14 14:50:04 linux-ytaf kernel: e820: update [mem 0x0c826018-0x0c835c57] usable ==> usable
Feb 14 14:50:04 linux-ytaf kernel: e820: update [mem 0x0c836018-0x0c846057] usable ==> usable
Feb 14 14:50:04 linux-ytaf kernel: e820: update [mem 0x0c847018-0x0c856857] usable ==> usable
Feb 14 14:50:04 linux-ytaf kernel: e820: update [mem 0x0c857018-0x0c85ae57] usable ==> usable
Feb 14 14:50:04 linux-ytaf kernel: extended physical RAM map:
Feb 14 14:50:04 linux-ytaf kernel: reserve setup_data: [mem 0x0000000000000000-0x000000000009efff] usable
Feb 14 14:50:04 linux-ytaf kernel: reserve setup_data: [mem 0x000000000009f000-0x000000000009ffff] reserved
Feb 14 14:50:04 linux-ytaf kernel: reserve setup_data: [mem 0x0000000000100000-0x000000000c826017] usable
Feb 14 14:50:04 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c826018-0x000000000c835c57] usable
Feb 14 14:50:04 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c835c58-0x000000000c836017] usable
Feb 14 14:50:04 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c836018-0x000000000c846057] usable
Feb 14 14:50:04 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c846058-0x000000000c847017] usable
Feb 14 14:50:04 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c847018-0x000000000c856857] usable
Feb 14 14:50:04 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c856858-0x000000000c857017] usable
Feb 14 14:50:04 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c857018-0x000000000c85ae57] usable
Feb 14 14:50:04 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c85ae58-0x000000001fffffff] usable
Feb 14 14:50:04 linux-ytaf kernel: reserve setup_data: [mem 0x0000000020000000-0x00000000201fffff] reserved
Feb 14 14:50:04 linux-ytaf kernel: reserve setup_data: [mem 0x0000000020200000-0x000000003fffffff] usable
Feb 14 14:50:04 linux-ytaf kernel: reserve setup_data: [mem 0x0000000040000000-0x00000000401fffff] reserved
Feb 14 14:50:04 linux-ytaf kernel: reserve setup_data: [mem 0x0000000040200000-0x00000000ca38efff] usable
Feb 14 14:50:04 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ca38f000-0x00000000ca5f1fff] reserved
Feb 14 14:50:04 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ca5f2000-0x00000000ca679fff] ACPI NVS
Feb 14 14:50:04 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ca67a000-0x00000000ca93efff] reserved
Feb 14 14:50:04 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ca93f000-0x00000000cab83fff] ACPI NVS
Feb 14 14:50:04 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cab84000-0x00000000cab91fff] ACPI data
Feb 14 14:50:04 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cab92000-0x00000000cabbefff] ACPI NVS
Feb 14 14:50:04 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cabbf000-0x00000000cabc3fff] ACPI data
Feb 14 14:50:04 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cabc4000-0x00000000cac06fff] ACPI NVS
Feb 14 14:50:04 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cac07000-0x00000000caffffff] usable
Feb 14 14:50:04 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cb800000-0x00000000cf9fffff] reserved
Feb 14 14:50:04 linux-ytaf kernel: reserve setup_data: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Feb 14 14:50:04 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Feb 14 14:50:04 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Feb 14 14:50:04 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Feb 14 14:50:04 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Feb 14 14:50:04 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Feb 14 14:50:04 linux-ytaf kernel: reserve setup_data: [mem 0x0000000100000000-0x000000022f5fffff] usable
Feb 14 14:50:04 linux-ytaf kernel: efi: EFI v2.31 by American Megatrends
Feb 14 14:50:04 linux-ytaf kernel: efi:  ACPI=0xcab84000  ACPI 2.0=0xcab84000  SMBIOS=0xca427e98  MPS=0xfc990 
Feb 14 14:50:04 linux-ytaf kernel: SMBIOS 2.6 present.
Feb 14 14:50:04 linux-ytaf kernel: DMI: System manufacturer System Product Name/MAXIMUS IV GENE-Z/GEN3, BIOS 3603 11/09/2012
Feb 14 14:50:04 linux-ytaf kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Feb 14 14:50:04 linux-ytaf kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Feb 14 14:50:04 linux-ytaf kernel: AGP: No AGP bridge found
Feb 14 14:50:04 linux-ytaf kernel: e820: last_pfn = 0x22f600 max_arch_pfn = 0x400000000
Feb 14 14:50:04 linux-ytaf kernel: MTRR default type: uncachable
Feb 14 14:50:04 linux-ytaf kernel: MTRR fixed ranges enabled:
Feb 14 14:50:04 linux-ytaf kernel:   00000-9FFFF write-back
Feb 14 14:50:04 linux-ytaf kernel:   A0000-BFFFF uncachable
Feb 14 14:50:04 linux-ytaf kernel:   C0000-D3FFF write-protect
Feb 14 14:50:04 linux-ytaf kernel:   D4000-DFFFF uncachable
Feb 14 14:50:04 linux-ytaf kernel:   E0000-E7FFF write-through
Feb 14 14:50:04 linux-ytaf kernel:   E8000-FFFFF write-protect
Feb 14 14:50:04 linux-ytaf kernel: MTRR variable ranges enabled:
Feb 14 14:50:04 linux-ytaf kernel:   0 base 000000000 mask E00000000 write-back
Feb 14 14:50:04 linux-ytaf kernel:   1 base 200000000 mask FE0000000 write-back
Feb 14 14:50:04 linux-ytaf kernel:   2 base 220000000 mask FF0000000 write-back
Feb 14 14:50:04 linux-ytaf kernel:   3 base 0E0000000 mask FE0000000 uncachable
Feb 14 14:50:04 linux-ytaf kernel:   4 base 0D0000000 mask FF0000000 uncachable
Feb 14 14:50:04 linux-ytaf kernel:   5 base 0CC000000 mask FFC000000 uncachable
Feb 14 14:50:04 linux-ytaf kernel:   6 base 0CB800000 mask FFF800000 uncachable
Feb 14 14:50:04 linux-ytaf kernel:   7 base 22F800000 mask FFF800000 uncachable
Feb 14 14:50:04 linux-ytaf kernel:   8 base 22F600000 mask FFFE00000 uncachable
Feb 14 14:50:04 linux-ytaf kernel:   9 disabled
Feb 14 14:50:04 linux-ytaf kernel: PAT configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- UC  
Feb 14 14:50:04 linux-ytaf kernel: e820: update [mem 0xcb800000-0xffffffff] usable ==> reserved
Feb 14 14:50:04 linux-ytaf kernel: e820: last_pfn = 0xcb000 max_arch_pfn = 0x400000000
Feb 14 14:50:04 linux-ytaf kernel: found SMP MP-table at [mem 0x000fcd30-0x000fcd3f] mapped at [ffff8800000fcd30]
Feb 14 14:50:04 linux-ytaf kernel: Scanning 1 areas for low memory corruption
Feb 14 14:50:04 linux-ytaf kernel: Base memory trampoline at [ffff880000097000] 97000 size 24576
Feb 14 14:50:04 linux-ytaf kernel: reserving inaccessible SNB gfx pages
Feb 14 14:50:04 linux-ytaf kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
Feb 14 14:50:04 linux-ytaf kernel:  [mem 0x00000000-0x000fffff] page 4k
Feb 14 14:50:04 linux-ytaf kernel: BRK [0x0e21a000, 0x0e21afff] PGTABLE
Feb 14 14:50:04 linux-ytaf kernel: BRK [0x0e21b000, 0x0e21bfff] PGTABLE
Feb 14 14:50:04 linux-ytaf kernel: BRK [0x0e21c000, 0x0e21cfff] PGTABLE
Feb 14 14:50:04 linux-ytaf kernel: init_memory_mapping: [mem 0x22f400000-0x22f5fffff]
Feb 14 14:50:04 linux-ytaf kernel:  [mem 0x22f400000-0x22f5fffff] page 2M
Feb 14 14:50:04 linux-ytaf kernel: BRK [0x0e21d000, 0x0e21dfff] PGTABLE
Feb 14 14:50:04 linux-ytaf kernel: init_memory_mapping: [mem 0x220000000-0x22f3fffff]
Feb 14 14:50:04 linux-ytaf kernel:  [mem 0x220000000-0x22f3fffff] page 2M
Feb 14 14:50:04 linux-ytaf kernel: init_memory_mapping: [mem 0x200000000-0x21fffffff]
Feb 14 14:50:04 linux-ytaf kernel:  [mem 0x200000000-0x21fffffff] page 2M
Feb 14 14:50:04 linux-ytaf kernel: init_memory_mapping: [mem 0x00100000-0x1fffffff]
Feb 14 14:50:04 linux-ytaf kernel:  [mem 0x00100000-0x001fffff] page 4k
Feb 14 14:50:04 linux-ytaf kernel:  [mem 0x00200000-0x1fffffff] page 2M
Feb 14 14:50:04 linux-ytaf kernel: init_memory_mapping: [mem 0x20200000-0x3fffffff]
Feb 14 14:50:04 linux-ytaf kernel:  [mem 0x20200000-0x3fffffff] page 2M
Feb 14 14:50:04 linux-ytaf kernel: init_memory_mapping: [mem 0x40200000-0xca38efff]
Feb 14 14:50:04 linux-ytaf kernel:  [mem 0x40200000-0xca1fffff] page 2M
Feb 14 14:50:04 linux-ytaf kernel:  [mem 0xca200000-0xca38efff] page 4k
Feb 14 14:50:04 linux-ytaf kernel: BRK [0x0e21e000, 0x0e21efff] PGTABLE
Feb 14 14:50:04 linux-ytaf kernel: BRK [0x0e21f000, 0x0e21ffff] PGTABLE
Feb 14 14:50:04 linux-ytaf kernel: init_memory_mapping: [mem 0xcac07000-0xcaffffff]
Feb 14 14:50:04 linux-ytaf kernel:  [mem 0xcac07000-0xcadfffff] page 4k
Feb 14 14:50:04 linux-ytaf kernel:  [mem 0xcae00000-0xcaffffff] page 2M
Feb 14 14:50:04 linux-ytaf kernel: init_memory_mapping: [mem 0x100000000-0x1ffffffff]
Feb 14 14:50:04 linux-ytaf kernel:  [mem 0x100000000-0x1ffffffff] page 2M
Feb 14 14:50:04 linux-ytaf kernel: RAMDISK: [mem 0x00457000-0x00ffafff]
Feb 14 14:50:04 linux-ytaf kernel: ACPI: Early table checksum verification disabled
Feb 14 14:50:04 linux-ytaf kernel: ACPI: RSDP 0x00000000CAB84000 000024 (v02 ALASKA)
Feb 14 14:50:04 linux-ytaf kernel: ACPI: XSDT 0x00000000CAB84078 000064 (v01 ALASKA A M I    01072009 AMI  00010013)
Feb 14 14:50:04 linux-ytaf kernel: ACPI: FACP 0x00000000CAB8FC78 0000F4 (v04 ALASKA A M I    01072009 AMI  00010013)
Feb 14 14:50:04 linux-ytaf kernel: ACPI: DSDT 0x00000000CAB84170 00BB02 (v02 ALASKA A M I    00000015 INTL 20051117)
Feb 14 14:50:04 linux-ytaf kernel: ACPI: FACS 0x00000000CABBDF80 000040
Feb 14 14:50:04 linux-ytaf kernel: ACPI: APIC 0x00000000CAB8FD70 000092 (v03 ALASKA A M I    01072009 AMI  00010013)
Feb 14 14:50:04 linux-ytaf kernel: ACPI: MCFG 0x00000000CAB8FE08 00003C (v01 ALASKA A M I    01072009 MSFT 00000097)
Feb 14 14:50:04 linux-ytaf kernel: ACPI: HPET 0x00000000CAB8FE48 000038 (v01 ALASKA A M I    01072009 AMI. 00000005)
Feb 14 14:50:04 linux-ytaf kernel: ACPI: SSDT 0x00000000CAB8FE80 00036D (v01 SataRe SataTabl 00001000 INTL 20091112)
Feb 14 14:50:04 linux-ytaf kernel: ACPI: SSDT 0x00000000CAB901F0 0009AA (v01 PmRef  Cpu0Ist  00003000 INTL 20051117)
Feb 14 14:50:04 linux-ytaf kernel: ACPI: SSDT 0x00000000CAB90BA0 000A92 (v01 PmRef  CpuPm    00003000 INTL 20051117)
Feb 14 14:50:04 linux-ytaf kernel: ACPI: BGRT 0x00000000CAB91690 000038 (v00 ALASKA A M I    01072009 AMI  00010013)
Feb 14 14:50:04 linux-ytaf kernel: ACPI: Local APIC address 0xfee00000
Feb 14 14:50:04 linux-ytaf kernel: No NUMA configuration found
Feb 14 14:50:04 linux-ytaf kernel: Faking a node at [mem 0x0000000000000000-0x000000022f5fffff]
Feb 14 14:50:04 linux-ytaf kernel: NODE_DATA(0) allocated [mem 0x22f5e5000-0x22f5f8fff]
Feb 14 14:50:04 linux-ytaf kernel:  [ffffea0000000000-ffffea0008bfffff] PMD -> [ffff880226c00000-ffff88022ebfffff] on node 0
Feb 14 14:50:04 linux-ytaf kernel: Zone ranges:
Feb 14 14:50:04 linux-ytaf kernel:   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
Feb 14 14:50:04 linux-ytaf kernel:   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
Feb 14 14:50:04 linux-ytaf kernel:   Normal   [mem 0x0000000100000000-0x000000022f5fffff]
Feb 14 14:50:04 linux-ytaf kernel: Movable zone start for each node
Feb 14 14:50:04 linux-ytaf kernel: Early memory node ranges
Feb 14 14:50:04 linux-ytaf kernel:   node   0: [mem 0x0000000000001000-0x000000000009efff]
Feb 14 14:50:04 linux-ytaf kernel:   node   0: [mem 0x0000000000100000-0x000000001fffffff]
Feb 14 14:50:04 linux-ytaf kernel:   node   0: [mem 0x0000000020200000-0x000000003fffffff]
Feb 14 14:50:04 linux-ytaf kernel:   node   0: [mem 0x0000000040200000-0x00000000ca38efff]
Feb 14 14:50:04 linux-ytaf kernel:   node   0: [mem 0x00000000cac07000-0x00000000caffffff]
Feb 14 14:50:04 linux-ytaf kernel:   node   0: [mem 0x0000000100000000-0x000000022f5fffff]
Feb 14 14:50:04 linux-ytaf kernel: Initmem setup node 0 [mem 0x0000000000001000-0x000000022f5fffff]
Feb 14 14:50:04 linux-ytaf kernel: On node 0 totalpages: 2070822
Feb 14 14:50:04 linux-ytaf kernel:   DMA zone: 64 pages used for memmap
Feb 14 14:50:04 linux-ytaf kernel:   DMA zone: 3138 pages reserved
Feb 14 14:50:04 linux-ytaf kernel:   DMA zone: 3998 pages, LIFO batch:0
Feb 14 14:50:04 linux-ytaf kernel:   DMA32 zone: 12879 pages used for memmap
Feb 14 14:50:04 linux-ytaf kernel:   DMA32 zone: 824200 pages, LIFO batch:31
Feb 14 14:50:04 linux-ytaf kernel:   Normal zone: 19416 pages used for memmap
Feb 14 14:50:04 linux-ytaf kernel:   Normal zone: 1242624 pages, LIFO batch:31
Feb 14 14:50:04 linux-ytaf kernel: tboot: non-0 tboot_addr but it is not of type E820_RESERVED
Feb 14 14:50:04 linux-ytaf kernel: ACPI: PM-Timer IO Port: 0x408
Feb 14 14:50:04 linux-ytaf kernel: ACPI: Local APIC address 0xfee00000
Feb 14 14:50:04 linux-ytaf kernel: ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
Feb 14 14:50:04 linux-ytaf kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
Feb 14 14:50:04 linux-ytaf kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Feb 14 14:50:04 linux-ytaf kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Feb 14 14:50:04 linux-ytaf kernel: ACPI: IRQ0 used by override.
Feb 14 14:50:04 linux-ytaf kernel: ACPI: IRQ9 used by override.
Feb 14 14:50:04 linux-ytaf kernel: Using ACPI (MADT) for SMP configuration information
Feb 14 14:50:04 linux-ytaf kernel: ACPI: HPET id: 0x8086a701 base: 0xfed00000
Feb 14 14:50:04 linux-ytaf kernel: smpboot: Allowing 8 CPUs, 0 hotplug CPUs
Feb 14 14:50:04 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
Feb 14 14:50:04 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Feb 14 14:50:04 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000fffff]
Feb 14 14:50:04 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c826000-0x0c826fff]
Feb 14 14:50:04 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c835000-0x0c835fff]
Feb 14 14:50:04 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c836000-0x0c836fff]
Feb 14 14:50:04 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c846000-0x0c846fff]
Feb 14 14:50:04 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c847000-0x0c847fff]
Feb 14 14:50:04 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c856000-0x0c856fff]
Feb 14 14:50:04 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c857000-0x0c857fff]
Feb 14 14:50:04 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c85a000-0x0c85afff]
Feb 14 14:50:04 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x20000000-0x201fffff]
Feb 14 14:50:04 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x40000000-0x401fffff]
Feb 14 14:50:04 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xca38f000-0xca5f1fff]
Feb 14 14:50:04 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xca5f2000-0xca679fff]
Feb 14 14:50:04 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xca67a000-0xca93efff]
Feb 14 14:50:04 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xca93f000-0xcab83fff]
Feb 14 14:50:04 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcab84000-0xcab91fff]
Feb 14 14:50:04 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcab92000-0xcabbefff]
Feb 14 14:50:04 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcabbf000-0xcabc3fff]
Feb 14 14:50:04 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcabc4000-0xcac06fff]
Feb 14 14:50:04 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcb000000-0xcb7fffff]
Feb 14 14:50:04 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcb800000-0xcf9fffff]
Feb 14 14:50:04 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcfa00000-0xf7ffffff]
Feb 14 14:50:04 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
Feb 14 14:50:04 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfc000000-0xfebfffff]
Feb 14 14:50:04 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
Feb 14 14:50:04 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfec01000-0xfecfffff]
Feb 14 14:50:04 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed00000-0xfed03fff]
Feb 14 14:50:04 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed04000-0xfed1bfff]
Feb 14 14:50:04 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Feb 14 14:50:04 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed20000-0xfedfffff]
Feb 14 14:50:04 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
Feb 14 14:50:04 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfee01000-0xfeffffff]
Feb 14 14:50:04 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Feb 14 14:50:04 linux-ytaf kernel: e820: [mem 0xcfa00000-0xf7ffffff] available for PCI devices
Feb 14 14:50:04 linux-ytaf kernel: Booting paravirtualized kernel on bare hardware
Feb 14 14:50:04 linux-ytaf kernel: clocksource refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
Feb 14 14:50:04 linux-ytaf kernel: setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:8 nr_node_ids:1
Feb 14 14:50:04 linux-ytaf kernel: PERCPU: Embedded 33 pages/cpu @ffff88022f200000 s97368 r8192 d29608 u262144
Feb 14 14:50:04 linux-ytaf kernel: pcpu-alloc: s97368 r8192 d29608 u262144 alloc=1*2097152
Feb 14 14:50:04 linux-ytaf kernel: pcpu-alloc: [0] 0 1 2 3 4 5 6 7 
Feb 14 14:50:04 linux-ytaf kernel: Built 1 zonelists in Node order, mobility grouping on.  Total pages: 2035325
Feb 14 14:50:04 linux-ytaf kernel: Policy zone: Normal
Feb 14 14:50:04 linux-ytaf kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.1.15-8-default root=UUID=21024970-7a27-4114-8525-d8dd026f23b6 ro resume=/dev/sdb2 splash=silent quiet showopts
Feb 14 14:50:04 linux-ytaf kernel: log_buf_len individual max cpu contribution: 32768 bytes
Feb 14 14:50:04 linux-ytaf kernel: log_buf_len total cpu_extra contributions: 229376 bytes
Feb 14 14:50:04 linux-ytaf kernel: log_buf_len min size: 262144 bytes
Feb 14 14:50:04 linux-ytaf kernel: log_buf_len: 524288 bytes
Feb 14 14:50:04 linux-ytaf kernel: early log buf free: 245492(93%)
Feb 14 14:50:04 linux-ytaf kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
Feb 14 14:50:04 linux-ytaf kernel: xsave: enabled xstate_bv 0x7, cntxt size 0x340 using standard form
Feb 14 14:50:04 linux-ytaf kernel: AGP: Checking aperture...
Feb 14 14:50:04 linux-ytaf kernel: AGP: No AGP bridge found
Feb 14 14:50:04 linux-ytaf kernel: Memory: 7863196K/8283288K available (6547K kernel code, 1084K rwdata, 4848K rodata, 1560K init, 1516K bss, 420092K reserved, 0K cma-reserved)
Feb 14 14:50:04 linux-ytaf kernel: Preemptible hierarchical RCU implementation.
Feb 14 14:50:04 linux-ytaf kernel:         RCU dyntick-idle grace-period acceleration is enabled.
Feb 14 14:50:04 linux-ytaf kernel:         RCU restricting CPUs from NR_CPUS=512 to nr_cpu_ids=8.
Feb 14 14:50:04 linux-ytaf kernel: RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
Feb 14 14:50:04 linux-ytaf kernel: NR_IRQS:33024 nr_irqs:488 16
Feb 14 14:50:04 linux-ytaf kernel:         Offload RCU callbacks from all CPUs
Feb 14 14:50:04 linux-ytaf kernel:         Offload RCU callbacks from CPUs: 0-7.
Feb 14 14:50:04 linux-ytaf kernel: Console: colour dummy device 80x25
Feb 14 14:50:04 linux-ytaf kernel: console [tty0] enabled
Feb 14 14:50:04 linux-ytaf kernel: clocksource hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484882848 ns
Feb 14 14:50:04 linux-ytaf kernel: hpet clockevent registered
Feb 14 14:50:04 linux-ytaf kernel: tsc: Fast TSC calibration using PIT
Feb 14 14:50:04 linux-ytaf kernel: tsc: Detected 3411.197 MHz processor
Feb 14 14:50:04 linux-ytaf kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 6822.39 BogoMIPS (lpj=13644788)
Feb 14 14:50:04 linux-ytaf kernel: pid_max: default: 32768 minimum: 301
Feb 14 14:50:04 linux-ytaf kernel: ACPI: Core revision 20150410
Feb 14 14:50:04 linux-ytaf kernel: ACPI: All ACPI Tables successfully acquired
Feb 14 14:50:04 linux-ytaf kernel: Security Framework initialized
Feb 14 14:50:04 linux-ytaf kernel: AppArmor: AppArmor initialized
Feb 14 14:50:04 linux-ytaf kernel: Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
Feb 14 14:50:04 linux-ytaf kernel: Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
Feb 14 14:50:04 linux-ytaf kernel: Mount-cache hash table entries: 16384 (order: 5, 131072 bytes)
Feb 14 14:50:04 linux-ytaf kernel: Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes)
Feb 14 14:50:04 linux-ytaf kernel: Initializing cgroup subsys blkio
Feb 14 14:50:04 linux-ytaf kernel: Initializing cgroup subsys memory
Feb 14 14:50:04 linux-ytaf kernel: Initializing cgroup subsys devices
Feb 14 14:50:04 linux-ytaf kernel: Initializing cgroup subsys freezer
Feb 14 14:50:04 linux-ytaf kernel: Initializing cgroup subsys net_cls
Feb 14 14:50:04 linux-ytaf kernel: Initializing cgroup subsys perf_event
Feb 14 14:50:04 linux-ytaf kernel: Initializing cgroup subsys net_prio
Feb 14 14:50:04 linux-ytaf kernel: Initializing cgroup subsys hugetlb
Feb 14 14:50:04 linux-ytaf kernel: CPU: Physical Processor ID: 0
Feb 14 14:50:04 linux-ytaf kernel: CPU: Processor Core ID: 0
Feb 14 14:50:04 linux-ytaf kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Feb 14 14:50:04 linux-ytaf kernel: ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Feb 14 14:50:04 linux-ytaf kernel: mce: CPU supports 9 MCE banks
Feb 14 14:50:04 linux-ytaf kernel: CPU0: Thermal monitoring enabled (TM1)
Feb 14 14:50:04 linux-ytaf kernel: process: using mwait in idle threads
Feb 14 14:50:04 linux-ytaf kernel: Last level iTLB entries: 4KB 512, 2MB 8, 4MB 8
Feb 14 14:50:04 linux-ytaf kernel: Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32, 1GB 0
Feb 14 14:50:04 linux-ytaf kernel: Freeing SMP alternatives memory: 24K (ffffffff82097000 - ffffffff8209d000)
Feb 14 14:50:04 linux-ytaf kernel: ftrace: allocating 25000 entries in 98 pages
Feb 14 14:50:04 linux-ytaf kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Feb 14 14:50:04 linux-ytaf kernel: TSC deadline timer enabled
Feb 14 14:50:04 linux-ytaf kernel: smpboot: CPU0: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz (fam: 06, model: 2a, stepping: 07)
Feb 14 14:50:04 linux-ytaf kernel: Performance Events: PEBS fmt1+, 16-deep LBR, SandyBridge events, full-width counters, Intel PMU driver.
Feb 14 14:50:04 linux-ytaf kernel: ... version:                3
Feb 14 14:50:04 linux-ytaf kernel: ... bit width:              48
Feb 14 14:50:04 linux-ytaf kernel: ... generic registers:      4
Feb 14 14:50:04 linux-ytaf kernel: ... value mask:             0000ffffffffffff
Feb 14 14:50:04 linux-ytaf kernel: ... max period:             0000ffffffffffff
Feb 14 14:50:04 linux-ytaf kernel: ... fixed-purpose events:   3
Feb 14 14:50:04 linux-ytaf kernel: ... event mask:             000000070000000f
Feb 14 14:50:04 linux-ytaf kernel: x86: Booting SMP configuration:
Feb 14 14:50:04 linux-ytaf kernel: .... node  #0, CPUs:      #1
Feb 14 14:50:04 linux-ytaf kernel: microcode: CPU1 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 14:50:04 linux-ytaf kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Feb 14 14:50:04 linux-ytaf kernel:  #2
Feb 14 14:50:04 linux-ytaf kernel: microcode: CPU2 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 14:50:04 linux-ytaf kernel:  #3
Feb 14 14:50:04 linux-ytaf kernel: microcode: CPU3 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 14:50:04 linux-ytaf kernel:  #4 #5 #6 #7
Feb 14 14:50:04 linux-ytaf kernel: x86: Booted up 1 node, 8 CPUs
Feb 14 14:50:04 linux-ytaf kernel: smpboot: Total of 8 processors activated (54579.15 BogoMIPS)
Feb 14 14:50:04 linux-ytaf kernel: devtmpfs: initialized
Feb 14 14:50:04 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xca5f2000-0xca679fff] (557056 bytes)
Feb 14 14:50:04 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xca93f000-0xcab83fff] (2379776 bytes)
Feb 14 14:50:04 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xcab92000-0xcabbefff] (184320 bytes)
Feb 14 14:50:04 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xcabc4000-0xcac06fff] (274432 bytes)
Feb 14 14:50:04 linux-ytaf kernel: clocksource jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
Feb 14 14:50:04 linux-ytaf kernel: pinctrl core: initialized pinctrl subsystem
Feb 14 14:50:04 linux-ytaf kernel: RTC time: 14:50:00, date: 02/14/16
Feb 14 14:50:04 linux-ytaf kernel: NET: Registered protocol family 16
Feb 14 14:50:04 linux-ytaf kernel: cpuidle: using governor ladder
Feb 14 14:50:04 linux-ytaf kernel: cpuidle: using governor menu
Feb 14 14:50:04 linux-ytaf kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
Feb 14 14:50:04 linux-ytaf kernel: ACPI: bus type PCI registered
Feb 14 14:50:04 linux-ytaf kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Feb 14 14:50:04 linux-ytaf kernel: PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
Feb 14 14:50:04 linux-ytaf kernel: PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
Feb 14 14:50:04 linux-ytaf kernel: PCI: Using configuration type 1 for base access
Feb 14 14:50:04 linux-ytaf kernel: perf_event_intel: PMU erratum BJ122, BV98, HSD29 worked around, HT is on
Feb 14 14:50:04 linux-ytaf kernel: ACPI: Added _OSI(Module Device)
Feb 14 14:50:04 linux-ytaf kernel: ACPI: Added _OSI(Processor Device)
Feb 14 14:50:04 linux-ytaf kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
Feb 14 14:50:04 linux-ytaf kernel: ACPI: Added _OSI(Processor Aggregator Device)
Feb 14 14:50:04 linux-ytaf kernel: ACPI: Executed 1 blocks of module-level executable AML code
Feb 14 14:50:04 linux-ytaf kernel: ACPI: Dynamic OEM Table Load:
Feb 14 14:50:04 linux-ytaf kernel: ACPI: SSDT 0xFFFF8802257C7000 00083B (v01 PmRef  Cpu0Cst  00003001 INTL 20051117)
Feb 14 14:50:04 linux-ytaf kernel: ACPI: Dynamic OEM Table Load:
Feb 14 14:50:04 linux-ytaf kernel: ACPI: SSDT 0xFFFF8802257C1400 000303 (v01 PmRef  ApIst    00003000 INTL 20051117)
Feb 14 14:50:04 linux-ytaf kernel: ACPI: Dynamic OEM Table Load:
Feb 14 14:50:04 linux-ytaf kernel: ACPI: SSDT 0xFFFF880225774600 000119 (v01 PmRef  ApCst    00003000 INTL 20051117)
Feb 14 14:50:04 linux-ytaf kernel: ACPI : EC: EC started
Feb 14 14:50:04 linux-ytaf kernel: ACPI: Interpreter enabled
Feb 14 14:50:04 linux-ytaf kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20150410/hwxface-580)
Feb 14 14:50:04 linux-ytaf kernel: ACPI: (supports S0 S1 S3 S4 S5)
Feb 14 14:50:04 linux-ytaf kernel: ACPI: Using IOAPIC for interrupt routing
Feb 14 14:50:04 linux-ytaf kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Feb 14 14:50:04 linux-ytaf kernel: ACPI: Power Resource [FN00] (off)
Feb 14 14:50:04 linux-ytaf kernel: ACPI: Power Resource [FN01] (off)
Feb 14 14:50:04 linux-ytaf kernel: ACPI: Power Resource [FN02] (off)
Feb 14 14:50:04 linux-ytaf kernel: ACPI: Power Resource [FN03] (off)
Feb 14 14:50:04 linux-ytaf kernel: ACPI: Power Resource [FN04] (off)
Feb 14 14:50:04 linux-ytaf kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
Feb 14 14:50:04 linux-ytaf kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Feb 14 14:50:04 linux-ytaf kernel: \_SB_.PCI0:_OSC invalid UUID
Feb 14 14:50:04 linux-ytaf kernel: _OSC request data:1 1f 0 
Feb 14 14:50:04 linux-ytaf kernel: acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
Feb 14 14:50:04 linux-ytaf kernel: PCI host bridge to bus 0000:00
Feb 14 14:50:04 linux-ytaf kernel: pci_bus 0000:00: root bus resource [bus 00-3e]
Feb 14 14:50:04 linux-ytaf kernel: pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
Feb 14 14:50:04 linux-ytaf kernel: pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
Feb 14 14:50:04 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
Feb 14 14:50:04 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff window]
Feb 14 14:50:04 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff window]
Feb 14 14:50:04 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff window]
Feb 14 14:50:04 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0xcfa00000-0xfeafffff window]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:00.0: [8086:0100] type 00 class 0x060000
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:01.0: [8086:0101] type 01 class 0x060400
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:01.0: System wakeup disabled by ACPI
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:01.1: [8086:0105] type 01 class 0x060400
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:01.1: PME# supported from D0 D3hot D3cold
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:01.1: System wakeup disabled by ACPI
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:02.0: [8086:0122] type 00 class 0x038000
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:02.0: reg 0x10: [mem 0xf7400000-0xf77fffff 64bit]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:02.0: reg 0x18: [mem 0xd0000000-0xdfffffff 64bit pref]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:02.0: reg 0x20: [io  0xf000-0xf03f]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:16.0: [8086:1c3a] type 00 class 0x078000
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:16.0: reg 0x10: [mem 0xf7b2c000-0xf7b2c00f 64bit]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:19.0: [8086:1503] type 00 class 0x020000
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:19.0: reg 0x10: [mem 0xf7b00000-0xf7b1ffff]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:19.0: reg 0x14: [mem 0xf7b29000-0xf7b29fff]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:19.0: reg 0x18: [io  0xf080-0xf09f]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:19.0: PME# supported from D0 D3hot D3cold
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:19.0: System wakeup disabled by ACPI
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1a.0: [8086:1c2d] type 00 class 0x0c0320
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1a.0: reg 0x10: [mem 0xf7b28000-0xf7b283ff]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1a.0: System wakeup disabled by ACPI
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1b.0: [8086:1c20] type 00 class 0x040300
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1b.0: reg 0x10: [mem 0xf7b20000-0xf7b23fff 64bit]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1b.0: System wakeup disabled by ACPI
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.0: [8086:1c10] type 01 class 0x060400
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.0: System wakeup disabled by ACPI
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.4: [8086:1c18] type 01 class 0x060400
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.4: System wakeup disabled by ACPI
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.5: [8086:1c1a] type 01 class 0x060400
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.5: System wakeup disabled by ACPI
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.6: [8086:1c1c] type 01 class 0x060400
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.6: PME# supported from D0 D3hot D3cold
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.6: System wakeup disabled by ACPI
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1d.0: [8086:1c26] type 00 class 0x0c0320
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1d.0: reg 0x10: [mem 0xf7b27000-0xf7b273ff]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1d.0: System wakeup disabled by ACPI
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1f.0: [8086:1c44] type 00 class 0x060100
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1f.2: [8086:1c02] type 00 class 0x010601
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x10: [io  0xf0d0-0xf0d7]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x14: [io  0xf0c0-0xf0c3]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x18: [io  0xf0b0-0xf0b7]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x1c: [io  0xf0a0-0xf0a3]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x20: [io  0xf060-0xf07f]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x24: [mem 0xf7b26000-0xf7b267ff]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1f.2: PME# supported from D3hot
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1f.3: [8086:1c22] type 00 class 0x0c0500
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1f.3: reg 0x10: [mem 0xf7b25000-0xf7b250ff 64bit]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1f.3: reg 0x20: [io  0x0580-0x059f]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:02:00.0: [10de:1183] type 00 class 0x030000
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:02:00.0: reg 0x10: [mem 0xf6000000-0xf6ffffff]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:02:00.0: reg 0x14: [mem 0xe0000000-0xe7ffffff 64bit pref]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:02:00.0: reg 0x1c: [mem 0xe8000000-0xe9ffffff 64bit pref]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:02:00.0: reg 0x24: [io  0xe000-0xe07f]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:02:00.0: reg 0x30: [mem 0xf7000000-0xf707ffff pref]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:02:00.1: [10de:0e0a] type 00 class 0x040300
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:02:00.1: reg 0x10: [mem 0xf7080000-0xf7083fff]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:01.1: PCI bridge to [bus 02]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [io  0xe000-0xefff]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xf6000000-0xf70fffff]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xe0000000-0xe9ffffff 64bit pref]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.0: PCI bridge to [bus 03]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:04:00.0: [1b21:1042] type 00 class 0x0c0330
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:04:00.0: reg 0x10: [mem 0xf7a00000-0xf7a07fff 64bit]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:04:00.0: PME# supported from D3hot D3cold
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:04:00.0: System wakeup disabled by ACPI
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.4: PCI bridge to [bus 04]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.4:   bridge window [mem 0xf7a00000-0xf7afffff]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:05:00.0: [1b21:1042] type 00 class 0x0c0330
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:05:00.0: reg 0x10: [mem 0xf7900000-0xf7907fff 64bit]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:05:00.0: PME# supported from D3hot D3cold
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:05:00.0: System wakeup disabled by ACPI
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.5: PCI bridge to [bus 05]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.5:   bridge window [mem 0xf7900000-0xf79fffff]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:06:00.0: [197b:2362] type 00 class 0x010185
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:06:00.0: reg 0x10: [io  0xd040-0xd047]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:06:00.0: reg 0x14: [io  0xd030-0xd033]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:06:00.0: reg 0x18: [io  0xd020-0xd027]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:06:00.0: reg 0x1c: [io  0xd010-0xd013]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:06:00.0: reg 0x20: [io  0xd000-0xd00f]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:06:00.0: reg 0x24: [mem 0xf7810000-0xf78101ff]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:06:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:06:00.0: PME# supported from D3hot
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:06:00.0: System wakeup disabled by ACPI
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.6: PCI bridge to [bus 06]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [io  0xd000-0xdfff]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [mem 0xf7800000-0xf78fffff]
Feb 14 14:50:04 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15)
Feb 14 14:50:04 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *10 11 12 14 15)
Feb 14 14:50:04 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Feb 14 14:50:04 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs *3 4 5 6 10 11 12 14 15)
Feb 14 14:50:04 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 *4 5 6 10 11 12 14 15)
Feb 14 14:50:04 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
Feb 14 14:50:04 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 *11 12 14 15)
Feb 14 14:50:04 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 *10 11 12 14 15)
Feb 14 14:50:04 linux-ytaf kernel: ACPI: Enabled 6 GPEs in block 00 to 3F
Feb 14 14:50:04 linux-ytaf kernel: ACPI : EC: GPE = 0x18, I/O: command/status = 0x66, data = 0x62
Feb 14 14:50:04 linux-ytaf kernel: vgaarb: setting as boot device: PCI:0000:02:00.0
Feb 14 14:50:04 linux-ytaf kernel: vgaarb: device added: PCI:0000:02:00.0,decodes=io+mem,owns=io+mem,locks=none
Feb 14 14:50:04 linux-ytaf kernel: vgaarb: loaded
Feb 14 14:50:04 linux-ytaf kernel: vgaarb: bridge control possible 0000:02:00.0
Feb 14 14:50:04 linux-ytaf kernel: SCSI subsystem initialized
Feb 14 14:50:04 linux-ytaf kernel: libata version 3.00 loaded.
Feb 14 14:50:04 linux-ytaf kernel: PCI: Using ACPI for IRQ routing
Feb 14 14:50:04 linux-ytaf kernel: PCI: pci_cache_line_size set to 64 bytes
Feb 14 14:50:04 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0009f000-0x0009ffff]
Feb 14 14:50:04 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c826018-0x0fffffff]
Feb 14 14:50:04 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c836018-0x0fffffff]
Feb 14 14:50:04 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c847018-0x0fffffff]
Feb 14 14:50:04 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c857018-0x0fffffff]
Feb 14 14:50:04 linux-ytaf kernel: e820: reserve RAM buffer [mem 0xca38f000-0xcbffffff]
Feb 14 14:50:04 linux-ytaf kernel: e820: reserve RAM buffer [mem 0xcb000000-0xcbffffff]
Feb 14 14:50:04 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x22f600000-0x22fffffff]
Feb 14 14:50:04 linux-ytaf kernel: NetLabel: Initializing
Feb 14 14:50:04 linux-ytaf kernel: NetLabel:  domain hash size = 128
Feb 14 14:50:04 linux-ytaf kernel: NetLabel:  protocols = UNLABELED CIPSOv4
Feb 14 14:50:04 linux-ytaf kernel: NetLabel:  unlabeled traffic allowed by default
Feb 14 14:50:04 linux-ytaf kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Feb 14 14:50:04 linux-ytaf kernel: hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Feb 14 14:50:04 linux-ytaf kernel: Switched to clocksource hpet
Feb 14 14:50:04 linux-ytaf kernel: AppArmor: AppArmor Filesystem Enabled
Feb 14 14:50:04 linux-ytaf kernel: pnp: PnP ACPI init
Feb 14 14:50:04 linux-ytaf kernel: system 00:00: [mem 0xfed40000-0xfed44fff] has been reserved
Feb 14 14:50:04 linux-ytaf kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
Feb 14 14:50:04 linux-ytaf kernel: system 00:01: [io  0x0680-0x069f] has been reserved
Feb 14 14:50:04 linux-ytaf kernel: system 00:01: [io  0x0200-0x020f] has been reserved
Feb 14 14:50:04 linux-ytaf kernel: system 00:01: [io  0xffff] has been reserved
Feb 14 14:50:04 linux-ytaf kernel: system 00:01: [io  0xffff] has been reserved
Feb 14 14:50:04 linux-ytaf kernel: system 00:01: [io  0x0400-0x0453] could not be reserved
Feb 14 14:50:04 linux-ytaf kernel: system 00:01: [io  0x0458-0x047f] has been reserved
Feb 14 14:50:04 linux-ytaf kernel: system 00:01: [io  0x0500-0x057f] has been reserved
Feb 14 14:50:04 linux-ytaf kernel: system 00:01: [io  0x164e-0x164f] has been reserved
Feb 14 14:50:04 linux-ytaf kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 14:50:04 linux-ytaf kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Feb 14 14:50:04 linux-ytaf kernel: system 00:03: [io  0x0454-0x0457] has been reserved
Feb 14 14:50:04 linux-ytaf kernel: system 00:03: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
Feb 14 14:50:04 linux-ytaf kernel: system 00:04: [io  0x0290-0x029f] has been reserved
Feb 14 14:50:04 linux-ytaf kernel: system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 14:50:04 linux-ytaf kernel: system 00:05: [io  0x04d0-0x04d1] has been reserved
Feb 14 14:50:04 linux-ytaf kernel: system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 14:50:04 linux-ytaf kernel: system 00:06: [mem 0xfed1c000-0xfed1ffff] has been reserved
Feb 14 14:50:04 linux-ytaf kernel: system 00:06: [mem 0xfed10000-0xfed17fff] has been reserved
Feb 14 14:50:04 linux-ytaf kernel: system 00:06: [mem 0xfed18000-0xfed18fff] has been reserved
Feb 14 14:50:04 linux-ytaf kernel: system 00:06: [mem 0xfed19000-0xfed19fff] has been reserved
Feb 14 14:50:04 linux-ytaf kernel: system 00:06: [mem 0xf8000000-0xfbffffff] has been reserved
Feb 14 14:50:04 linux-ytaf kernel: system 00:06: [mem 0xfed20000-0xfed3ffff] has been reserved
Feb 14 14:50:04 linux-ytaf kernel: system 00:06: [mem 0xfed90000-0xfed93fff] has been reserved
Feb 14 14:50:04 linux-ytaf kernel: system 00:06: [mem 0xfed45000-0xfed8ffff] has been reserved
Feb 14 14:50:04 linux-ytaf kernel: system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Feb 14 14:50:04 linux-ytaf kernel: system 00:06: [mem 0xfee00000-0xfeefffff] could not be reserved
Feb 14 14:50:04 linux-ytaf kernel: system 00:06: [mem 0xcfa00000-0xcfa00fff] has been reserved
Feb 14 14:50:04 linux-ytaf kernel: system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 14:50:04 linux-ytaf kernel: system 00:07: [mem 0x20000000-0x201fffff] has been reserved
Feb 14 14:50:04 linux-ytaf kernel: system 00:07: [mem 0x40000000-0x401fffff] has been reserved
Feb 14 14:50:04 linux-ytaf kernel: system 00:07: Plug and Play ACPI device, IDs PNP0c01 (active)
Feb 14 14:50:04 linux-ytaf kernel: pnp: PnP ACPI: found 8 devices
Feb 14 14:50:04 linux-ytaf kernel: clocksource acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.0: bridge window [io  0x1000-0x0fff] to [bus 03] add_size 1000
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 03] add_size 200000 add_align 100000
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff] to [bus 03] add_size 200000 add_align 100000
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.0: res[14]=[mem 0x00100000-0x000fffff] res_to_dev_res add_size 200000 min_align 100000
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.0: res[14]=[mem 0x00100000-0x002fffff] res_to_dev_res add_size 200000 min_align 100000
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x000fffff 64bit pref] res_to_dev_res add_size 200000 min_align 100000
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x002fffff 64bit pref] res_to_dev_res add_size 200000 min_align 100000
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.0: res[13]=[io  0x1000-0x0fff] res_to_dev_res add_size 1000 min_align 1000
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.0: res[13]=[io  0x1000-0x1fff] res_to_dev_res add_size 1000 min_align 1000
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.0: BAR 14: assigned [mem 0xcfb00000-0xcfcfffff]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.0: BAR 15: assigned [mem 0xcfd00000-0xcfefffff 64bit pref]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.0: BAR 13: assigned [io  0x2000-0x2fff]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:01.1: PCI bridge to [bus 02]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [io  0xe000-0xefff]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xf6000000-0xf70fffff]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xe0000000-0xe9ffffff 64bit pref]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.0: PCI bridge to [bus 03]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.0:   bridge window [io  0x2000-0x2fff]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.0:   bridge window [mem 0xcfb00000-0xcfcfffff]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.0:   bridge window [mem 0xcfd00000-0xcfefffff 64bit pref]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.4: PCI bridge to [bus 04]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.4:   bridge window [mem 0xf7a00000-0xf7afffff]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.5: PCI bridge to [bus 05]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.5:   bridge window [mem 0xf7900000-0xf79fffff]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:06:00.0: BAR 6: assigned [mem 0xf7800000-0xf780ffff pref]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.6: PCI bridge to [bus 06]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [io  0xd000-0xdfff]
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [mem 0xf7800000-0xf78fffff]
Feb 14 14:50:04 linux-ytaf kernel: pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
Feb 14 14:50:04 linux-ytaf kernel: pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
Feb 14 14:50:04 linux-ytaf kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
Feb 14 14:50:04 linux-ytaf kernel: pci_bus 0000:00: resource 7 [mem 0x000d4000-0x000d7fff window]
Feb 14 14:50:04 linux-ytaf kernel: pci_bus 0000:00: resource 8 [mem 0x000d8000-0x000dbfff window]
Feb 14 14:50:04 linux-ytaf kernel: pci_bus 0000:00: resource 9 [mem 0x000dc000-0x000dffff window]
Feb 14 14:50:04 linux-ytaf kernel: pci_bus 0000:00: resource 10 [mem 0xcfa00000-0xfeafffff window]
Feb 14 14:50:04 linux-ytaf kernel: pci_bus 0000:02: resource 0 [io  0xe000-0xefff]
Feb 14 14:50:04 linux-ytaf kernel: pci_bus 0000:02: resource 1 [mem 0xf6000000-0xf70fffff]
Feb 14 14:50:04 linux-ytaf kernel: pci_bus 0000:02: resource 2 [mem 0xe0000000-0xe9ffffff 64bit pref]
Feb 14 14:50:04 linux-ytaf kernel: pci_bus 0000:03: resource 0 [io  0x2000-0x2fff]
Feb 14 14:50:04 linux-ytaf kernel: pci_bus 0000:03: resource 1 [mem 0xcfb00000-0xcfcfffff]
Feb 14 14:50:04 linux-ytaf kernel: pci_bus 0000:03: resource 2 [mem 0xcfd00000-0xcfefffff 64bit pref]
Feb 14 14:50:04 linux-ytaf kernel: pci_bus 0000:04: resource 1 [mem 0xf7a00000-0xf7afffff]
Feb 14 14:50:04 linux-ytaf kernel: pci_bus 0000:05: resource 1 [mem 0xf7900000-0xf79fffff]
Feb 14 14:50:04 linux-ytaf kernel: pci_bus 0000:06: resource 0 [io  0xd000-0xdfff]
Feb 14 14:50:04 linux-ytaf kernel: pci_bus 0000:06: resource 1 [mem 0xf7800000-0xf78fffff]
Feb 14 14:50:04 linux-ytaf kernel: NET: Registered protocol family 2
Feb 14 14:50:04 linux-ytaf kernel: TCP established hash table entries: 65536 (order: 7, 524288 bytes)
Feb 14 14:50:04 linux-ytaf kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Feb 14 14:50:04 linux-ytaf kernel: TCP: Hash tables configured (established 65536 bind 65536)
Feb 14 14:50:04 linux-ytaf kernel: UDP hash table entries: 4096 (order: 5, 131072 bytes)
Feb 14 14:50:04 linux-ytaf kernel: UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
Feb 14 14:50:04 linux-ytaf kernel: NET: Registered protocol family 1
Feb 14 14:50:04 linux-ytaf kernel: pci 0000:02:00.0: Video device with shadowed ROM
Feb 14 14:50:04 linux-ytaf kernel: PCI: CLS 64 bytes, default 64
Feb 14 14:50:04 linux-ytaf kernel: Unpacking initramfs...
Feb 14 14:50:04 linux-ytaf kernel: Freeing initrd memory: 11920K (ffff880000457000 - ffff880000ffb000)
Feb 14 14:50:04 linux-ytaf kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Feb 14 14:50:04 linux-ytaf kernel: software IO TLB [mem 0xc638f000-0xca38f000] (64MB) mapped at [ffff8800c638f000-ffff8800ca38efff]
Feb 14 14:50:04 linux-ytaf kernel: RAPL PMU detected, API unit is 2^-32 Joules, 3 fixed counters 163840 ms ovfl timer
Feb 14 14:50:04 linux-ytaf kernel: hw unit of domain pp0-core 2^-16 Joules
Feb 14 14:50:04 linux-ytaf kernel: hw unit of domain package 2^-16 Joules
Feb 14 14:50:04 linux-ytaf kernel: hw unit of domain pp1-gpu 2^-16 Joules
Feb 14 14:50:04 linux-ytaf kernel: microcode: CPU0 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 14:50:04 linux-ytaf kernel: microcode: CPU1 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 14:50:04 linux-ytaf kernel: microcode: CPU2 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 14:50:04 linux-ytaf kernel: microcode: CPU3 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 14:50:04 linux-ytaf kernel: microcode: CPU4 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 14:50:04 linux-ytaf kernel: microcode: CPU5 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 14:50:04 linux-ytaf kernel: microcode: CPU6 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 14:50:04 linux-ytaf kernel: microcode: CPU7 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 14:50:04 linux-ytaf kernel: microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Feb 14 14:50:04 linux-ytaf kernel: Scanning for low memory corruption every 60 seconds
Feb 14 14:50:04 linux-ytaf kernel: futex hash table entries: 2048 (order: 5, 131072 bytes)
Feb 14 14:50:04 linux-ytaf kernel: audit: initializing netlink subsys (disabled)
Feb 14 14:50:04 linux-ytaf kernel: audit: type=2000 audit(1455461401.280:1): initialized
Feb 14 14:50:04 linux-ytaf kernel: HugeTLB registered 2 MB page size, pre-allocated 0 pages
Feb 14 14:50:04 linux-ytaf kernel: zpool: loaded
Feb 14 14:50:04 linux-ytaf kernel: zbud: loaded
Feb 14 14:50:04 linux-ytaf kernel: VFS: Disk quotas dquot_6.6.0
Feb 14 14:50:04 linux-ytaf kernel: VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Feb 14 14:50:04 linux-ytaf kernel: Key type big_key registered
Feb 14 14:50:04 linux-ytaf kernel: Key type asymmetric registered
Feb 14 14:50:04 linux-ytaf kernel: Asymmetric key parser 'x509' registered
Feb 14 14:50:04 linux-ytaf kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Feb 14 14:50:04 linux-ytaf kernel: io scheduler noop registered
Feb 14 14:50:04 linux-ytaf kernel: io scheduler deadline registered
Feb 14 14:50:04 linux-ytaf kernel: io scheduler cfq registered (default)
Feb 14 14:50:04 linux-ytaf kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Feb 14 14:50:04 linux-ytaf kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Feb 14 14:50:04 linux-ytaf kernel: efifb: probing for efifb
Feb 14 14:50:04 linux-ytaf kernel: efifb: framebuffer at 0xe9000000, mapped to 0xffffc90001000000, using 1876k, total 1875k
Feb 14 14:50:04 linux-ytaf kernel: efifb: mode is 800x600x32, linelength=3200, pages=1
Feb 14 14:50:04 linux-ytaf kernel: efifb: scrolling: redraw
Feb 14 14:50:04 linux-ytaf kernel: efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Feb 14 14:50:04 linux-ytaf kernel: Console: switching to colour frame buffer device 100x37
Feb 14 14:50:04 linux-ytaf kernel: fb0: EFI VGA frame buffer device
Feb 14 14:50:04 linux-ytaf kernel: intel_idle: MWAIT substates: 0x1120
Feb 14 14:50:04 linux-ytaf kernel: intel_idle: v0.4 model 0x2A
Feb 14 14:50:04 linux-ytaf kernel: intel_idle: lapic_timer_reliable_states 0xffffffff
Feb 14 14:50:04 linux-ytaf kernel: GHES: HEST is not enabled!
Feb 14 14:50:04 linux-ytaf kernel: Serial: 8250/16550 driver, 32 ports, IRQ sharing disabled
Feb 14 14:50:04 linux-ytaf kernel: Non-volatile memory driver v1.3
Feb 14 14:50:04 linux-ytaf kernel: Linux agpgart interface v0.103
Feb 14 14:50:04 linux-ytaf kernel: ahci 0000:00:1f.2: version 3.0
Feb 14 14:50:04 linux-ytaf kernel: ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x7 impl SATA mode
Feb 14 14:50:04 linux-ytaf kernel: ahci 0000:00:1f.2: flags: 64bit ncq led clo pio slum part ems apst 
Feb 14 14:50:04 linux-ytaf kernel: scsi host0: ahci
Feb 14 14:50:04 linux-ytaf kernel: scsi host1: ahci
Feb 14 14:50:04 linux-ytaf kernel: scsi host2: ahci
Feb 14 14:50:04 linux-ytaf kernel: scsi host3: ahci
Feb 14 14:50:04 linux-ytaf kernel: scsi host4: ahci
Feb 14 14:50:04 linux-ytaf kernel: scsi host5: ahci
Feb 14 14:50:04 linux-ytaf kernel: ata1: SATA max UDMA/133 abar m2048@0xf7b26000 port 0xf7b26100 irq 26
Feb 14 14:50:04 linux-ytaf kernel: ata2: SATA max UDMA/133 abar m2048@0xf7b26000 port 0xf7b26180 irq 26
Feb 14 14:50:04 linux-ytaf kernel: ata3: SATA max UDMA/133 abar m2048@0xf7b26000 port 0xf7b26200 irq 26
Feb 14 14:50:04 linux-ytaf kernel: ata4: DUMMY
Feb 14 14:50:04 linux-ytaf kernel: ata5: DUMMY
Feb 14 14:50:04 linux-ytaf kernel: ata6: DUMMY
Feb 14 14:50:04 linux-ytaf kernel: ahci 0000:06:00.0: AHCI 0001.0100 32 slots 2 ports 3 Gbps 0x3 impl SATA mode
Feb 14 14:50:04 linux-ytaf kernel: ahci 0000:06:00.0: flags: 64bit ncq pm led clo pmp pio slum part 
Feb 14 14:50:04 linux-ytaf kernel: scsi host6: ahci
Feb 14 14:50:04 linux-ytaf kernel: scsi host7: ahci
Feb 14 14:50:04 linux-ytaf kernel: ata7: SATA max UDMA/133 abar m512@0xf7810000 port 0xf7810100 irq 18
Feb 14 14:50:04 linux-ytaf kernel: ata8: SATA max UDMA/133 abar m512@0xf7810000 port 0xf7810180 irq 18
Feb 14 14:50:04 linux-ytaf kernel: i8042: PNP: No PS/2 controller found. Probing ports directly.
Feb 14 14:50:04 linux-ytaf kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Feb 14 14:50:04 linux-ytaf kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Feb 14 14:50:04 linux-ytaf kernel: mousedev: PS/2 mouse device common for all mice
Feb 14 14:50:04 linux-ytaf kernel: rtc_cmos 00:02: RTC can wake from S4
Feb 14 14:50:04 linux-ytaf kernel: rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Feb 14 14:50:04 linux-ytaf kernel: rtc_cmos 00:02: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
Feb 14 14:50:04 linux-ytaf kernel: Intel P-state driver initializing.
Feb 14 14:50:04 linux-ytaf kernel: ledtrig-cpu: registered to indicate activity on CPUs
Feb 14 14:50:04 linux-ytaf kernel: EFI Variables Facility v0.08 2004-May-17
Feb 14 14:50:04 linux-ytaf kernel: hpet1: lost 2 rtc interrupts
Feb 14 14:50:04 linux-ytaf kernel: hidraw: raw HID events driver (C) Jiri Kosina
Feb 14 14:50:04 linux-ytaf kernel: NET: Registered protocol family 10
Feb 14 14:50:04 linux-ytaf kernel: registered taskstats version 1
Feb 14 14:50:04 linux-ytaf kernel: Key type encrypted registered
Feb 14 14:50:04 linux-ytaf kernel: AppArmor: AppArmor sha1 policy hashing enabled
Feb 14 14:50:04 linux-ytaf kernel:   Magic number: 4:299:839
Feb 14 14:50:04 linux-ytaf kernel: rtc_cmos 00:02: setting system clock to 2016-02-14 14:50:02 UTC (1455461402)
Feb 14 14:50:04 linux-ytaf kernel: PM: Checking hibernation image partition /dev/sdb2
Feb 14 14:50:04 linux-ytaf kernel: ata8: SATA link down (SStatus 0 SControl 300)
Feb 14 14:50:04 linux-ytaf kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 14 14:50:04 linux-ytaf kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Feb 14 14:50:04 linux-ytaf kernel: ata7: SATA link down (SStatus 0 SControl 300)
Feb 14 14:50:04 linux-ytaf kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 14 14:50:04 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 14:50:04 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff8802268b7e50), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 14:50:04 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 14:50:04 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff8802268b7dd8), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 14:50:04 linux-ytaf kernel: ata1.00: ATA-9: SAMSUNG SSD 830 Series, CXM03B1Q, max UDMA/133
Feb 14 14:50:04 linux-ytaf kernel: ata1.00: 500118192 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Feb 14 14:50:04 linux-ytaf kernel: ata2.00: ATA-8: TOSHIBA HDWD110, MS2OA8J0, max UDMA/133
Feb 14 14:50:04 linux-ytaf kernel: ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Feb 14 14:50:04 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 14:50:04 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff8802268b7e50), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 14:50:04 linux-ytaf kernel: ata1.00: configured for UDMA/133
Feb 14 14:50:04 linux-ytaf kernel: scsi 0:0:0:0: Direct-Access     ATA      SAMSUNG SSD 830  3B1Q PQ: 0 ANSI: 5
Feb 14 14:50:04 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 14:50:04 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff8802268b7dd8), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 14:50:04 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 14:50:04 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff8802268b7d60), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 14:50:04 linux-ytaf kernel: ata3.00: ATAPI: TSSTcorp CDDVDW SH-S223C, SB05, max UDMA/66
Feb 14 14:50:04 linux-ytaf kernel: ata3.00: applying bridge limits
Feb 14 14:50:04 linux-ytaf kernel: sd 0:0:0:0: [sda] 500118192 512-byte logical blocks: (256 GB/238 GiB)
Feb 14 14:50:04 linux-ytaf kernel: ata2.00: configured for UDMA/133
Feb 14 14:50:04 linux-ytaf kernel: scsi 1:0:0:0: Direct-Access     ATA      TOSHIBA HDWD110  A8J0 PQ: 0 ANSI: 5
Feb 14 14:50:04 linux-ytaf kernel: sd 0:0:0:0: [sda] Write Protect is off
Feb 14 14:50:04 linux-ytaf kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 14 14:50:04 linux-ytaf kernel: sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
Feb 14 14:50:04 linux-ytaf kernel: sd 1:0:0:0: [sdb] 4096-byte physical blocks
Feb 14 14:50:04 linux-ytaf kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 14 14:50:04 linux-ytaf kernel: sd 1:0:0:0: [sdb] Write Protect is off
Feb 14 14:50:04 linux-ytaf kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Feb 14 14:50:04 linux-ytaf kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 14 14:50:04 linux-ytaf kernel:  sda: sda1 sda2 sda3 sda4
Feb 14 14:50:04 linux-ytaf kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Feb 14 14:50:04 linux-ytaf kernel:  sdb: sdb1 sdb2 sdb3 sdb4
Feb 14 14:50:04 linux-ytaf kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
Feb 14 14:50:04 linux-ytaf kernel: tsc: Refined TSC clocksource calibration: 3411.128 MHz
Feb 14 14:50:04 linux-ytaf kernel: clocksource tsc: mask: 0xffffffffffffffff max_cycles: 0x312b5ecadef, max_idle_ns: 440795307361 ns
Feb 14 14:50:04 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 14:50:04 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff8802268b7d60), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 14:50:04 linux-ytaf kernel: ata3.00: configured for UDMA/66
Feb 14 14:50:04 linux-ytaf kernel: scsi 2:0:0:0: CD-ROM            TSSTcorp CDDVDW SH-S223C  SB05 PQ: 0 ANSI: 5
Feb 14 14:50:04 linux-ytaf kernel: PM: Hibernation image partition 8:18 present
Feb 14 14:50:04 linux-ytaf kernel: PM: Looking for hibernation image.
Feb 14 14:50:04 linux-ytaf kernel: Switched to clocksource tsc
Feb 14 14:50:04 linux-ytaf kernel: PM: Image not found (code -22)
Feb 14 14:50:04 linux-ytaf kernel: PM: Hibernation image not present or could not be loaded.
Feb 14 14:50:04 linux-ytaf kernel: Freeing unused kernel memory: 1560K (ffffffff81f11000 - ffffffff82097000)
Feb 14 14:50:04 linux-ytaf kernel: Write protecting the kernel read-only data: 14336k
Feb 14 14:50:04 linux-ytaf kernel: Freeing unused kernel memory: 1632K (ffff88000d668000 - ffff88000d800000)
Feb 14 14:50:04 linux-ytaf kernel: Freeing unused kernel memory: 1296K (ffff88000dcbc000 - ffff88000de00000)
Feb 14 14:50:04 linux-ytaf systemd[1]: RTC configured in localtime, applying delta of 60 minutes to system time.
Feb 14 14:50:04 linux-ytaf kernel: random: systemd urandom read with 22 bits of entropy available
Feb 14 14:50:04 linux-ytaf kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Feb 14 14:50:04 linux-ytaf kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0
Feb 14 14:50:04 linux-ytaf kernel: scsi 2:0:0:0: Attached scsi generic sg2 type 5
Feb 14 14:50:04 linux-ytaf systemd-journal[187]: Journal started
Feb 14 14:50:04 linux-ytaf dracut-cmdline[181]: dracut-42.1 dracut-037-68.1
Feb 14 14:50:04 linux-ytaf systemd-udevd[250]: Network interface NamePolicy= disabled on kernel commandline, ignoring.
Feb 14 14:50:04 linux-ytaf kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3
Feb 14 14:50:04 linux-ytaf kernel: ACPI: Power Button [PWRB]
Feb 14 14:50:04 linux-ytaf kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
Feb 14 14:50:04 linux-ytaf kernel: ACPI: Power Button [PWRF]
Feb 14 14:50:04 linux-ytaf kernel: wmi: Mapper loaded
Feb 14 14:50:04 linux-ytaf kernel: ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
Feb 14 14:50:04 linux-ytaf kernel: acpi device:58: registered as cooling_device0
Feb 14 14:50:04 linux-ytaf kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5
Feb 14 14:50:04 linux-ytaf kernel: [drm] Initialized drm 1.1.0 20060810
Feb 14 14:50:04 linux-ytaf kernel: ACPI: bus type USB registered
Feb 14 14:50:04 linux-ytaf kernel: usbcore: registered new interface driver usbfs
Feb 14 14:50:04 linux-ytaf kernel: usbcore: registered new interface driver hub
Feb 14 14:50:04 linux-ytaf kernel: usbcore: registered new device driver usb
Feb 14 14:50:04 linux-ytaf kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Feb 14 14:50:04 linux-ytaf kernel: ehci-pci: EHCI PCI platform driver
Feb 14 14:50:04 linux-ytaf kernel: ehci-pci 0000:00:1a.0: EHCI Host Controller
Feb 14 14:50:04 linux-ytaf kernel: ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Feb 14 14:50:04 linux-ytaf kernel: ehci-pci 0000:00:1a.0: debug port 2
Feb 14 14:50:04 linux-ytaf kernel: ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Feb 14 14:50:04 linux-ytaf kernel: ehci-pci 0000:00:1a.0: irq 16, io mem 0xf7b28000
Feb 14 14:50:04 linux-ytaf kernel: MXM: GUID detected in BIOS
Feb 14 14:50:04 linux-ytaf kernel: checking generic (e9000000 1d5000) vs hw (e0000000 8000000)
Feb 14 14:50:04 linux-ytaf kernel: checking generic (e9000000 1d5000) vs hw (e8000000 2000000)
Feb 14 14:50:04 linux-ytaf kernel: fb: switching to nouveaufb from EFI VGA
Feb 14 14:50:04 linux-ytaf kernel: Console: switching to colour dummy device 80x25
Feb 14 14:50:04 linux-ytaf kernel: sr 2:0:0:0: [sr0] scsi3-mmc drive: 52x/52x writer dvd-ram cd/rw xa/form2 cdda tray
Feb 14 14:50:04 linux-ytaf kernel: cdrom: Uniform CD-ROM driver Revision: 3.20
Feb 14 14:50:04 linux-ytaf kernel: sr 2:0:0:0: Attached scsi CD-ROM sr0
Feb 14 14:50:04 linux-ytaf kernel: ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Feb 14 14:50:04 linux-ytaf kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 14:50:04 linux-ytaf kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 14:50:04 linux-ytaf kernel: usb usb1: Product: EHCI Host Controller
Feb 14 14:50:04 linux-ytaf kernel: usb usb1: Manufacturer: Linux 4.1.15-8-default ehci_hcd
Feb 14 14:50:04 linux-ytaf kernel: usb usb1: SerialNumber: 0000:00:1a.0
Feb 14 14:50:04 linux-ytaf kernel: hub 1-0:1.0: USB hub found
Feb 14 14:50:04 linux-ytaf kernel: hub 1-0:1.0: 2 ports detected
Feb 14 14:50:04 linux-ytaf kernel: xhci_hcd 0000:04:00.0: xHCI Host Controller
Feb 14 14:50:04 linux-ytaf kernel: xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 2
Feb 14 14:50:04 linux-ytaf kernel: nouveau  [  DEVICE][0000:02:00.0] BOOT0  : 0x0e4030a2
Feb 14 14:50:04 linux-ytaf kernel: nouveau  [  DEVICE][0000:02:00.0] Chipset: GK104 (NVE4)
Feb 14 14:50:04 linux-ytaf kernel: nouveau  [  DEVICE][0000:02:00.0] Family : NVE0
Feb 14 14:50:04 linux-ytaf kernel: xhci_hcd 0000:04:00.0: hcc params 0x0200f180 hci version 0x96 quirks 0x00080000
Feb 14 14:50:04 linux-ytaf kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 14:50:04 linux-ytaf kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 14:50:04 linux-ytaf kernel: usb usb2: Product: xHCI Host Controller
Feb 14 14:50:04 linux-ytaf kernel: usb usb2: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 14:50:04 linux-ytaf kernel: usb usb2: SerialNumber: 0000:04:00.0
Feb 14 14:50:04 linux-ytaf kernel: hub 2-0:1.0: USB hub found
Feb 14 14:50:04 linux-ytaf kernel: hub 2-0:1.0: 2 ports detected
Feb 14 14:50:04 linux-ytaf kernel: xhci_hcd 0000:04:00.0: xHCI Host Controller
Feb 14 14:50:04 linux-ytaf kernel: xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 3
Feb 14 14:50:04 linux-ytaf kernel: ehci-pci 0000:00:1d.0: EHCI Host Controller
Feb 14 14:50:04 linux-ytaf kernel: ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 4
Feb 14 14:50:04 linux-ytaf kernel: usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
Feb 14 14:50:04 linux-ytaf kernel: usb usb3: New USB device found, idVendor=1d6b, idProduct=0003
Feb 14 14:50:04 linux-ytaf kernel: ehci-pci 0000:00:1d.0: debug port 2
Feb 14 14:50:04 linux-ytaf kernel: usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 14:50:04 linux-ytaf kernel: usb usb3: Product: xHCI Host Controller
Feb 14 14:50:04 linux-ytaf kernel: usb usb3: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 14:50:04 linux-ytaf kernel: usb usb3: SerialNumber: 0000:04:00.0
Feb 14 14:50:04 linux-ytaf kernel: hub 3-0:1.0: USB hub found
Feb 14 14:50:04 linux-ytaf kernel: hub 3-0:1.0: 2 ports detected
Feb 14 14:50:04 linux-ytaf kernel: ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Feb 14 14:50:04 linux-ytaf kernel: ehci-pci 0000:00:1d.0: irq 23, io mem 0xf7b27000
Feb 14 14:50:04 linux-ytaf kernel: ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Feb 14 14:50:04 linux-ytaf kernel: usb usb4: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 14:50:04 linux-ytaf kernel: usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 14:50:04 linux-ytaf kernel: usb usb4: Product: EHCI Host Controller
Feb 14 14:50:04 linux-ytaf kernel: usb usb4: Manufacturer: Linux 4.1.15-8-default ehci_hcd
Feb 14 14:50:04 linux-ytaf kernel: usb usb4: SerialNumber: 0000:00:1d.0
Feb 14 14:50:04 linux-ytaf kernel: hub 4-0:1.0: USB hub found
Feb 14 14:50:04 linux-ytaf kernel: hub 4-0:1.0: 2 ports detected
Feb 14 14:50:04 linux-ytaf kernel: xhci_hcd 0000:05:00.0: xHCI Host Controller
Feb 14 14:50:04 linux-ytaf kernel: i915 0000:00:02.0: enabling device (0006 -> 0007)
Feb 14 14:50:04 linux-ytaf kernel: xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 5
Feb 14 14:50:04 linux-ytaf kernel: xhci_hcd 0000:05:00.0: hcc params 0x0200f180 hci version 0x96 quirks 0x00080000
Feb 14 14:50:04 linux-ytaf kernel: usb usb5: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 14:50:04 linux-ytaf kernel: usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 14:50:04 linux-ytaf kernel: usb usb5: Product: xHCI Host Controller
Feb 14 14:50:04 linux-ytaf kernel: usb usb5: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 14:50:04 linux-ytaf kernel: usb usb5: SerialNumber: 0000:05:00.0
Feb 14 14:50:04 linux-ytaf kernel: hub 5-0:1.0: USB hub found
Feb 14 14:50:04 linux-ytaf kernel: hub 5-0:1.0: 2 ports detected
Feb 14 14:50:04 linux-ytaf kernel: xhci_hcd 0000:05:00.0: xHCI Host Controller
Feb 14 14:50:04 linux-ytaf kernel: xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 6
Feb 14 14:50:04 linux-ytaf kernel: usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
Feb 14 14:50:04 linux-ytaf kernel: usb usb6: New USB device found, idVendor=1d6b, idProduct=0003
Feb 14 14:50:04 linux-ytaf kernel: usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 14:50:04 linux-ytaf kernel: usb usb6: Product: xHCI Host Controller
Feb 14 14:50:04 linux-ytaf kernel: usb usb6: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 14:50:04 linux-ytaf kernel: usb usb6: SerialNumber: 0000:05:00.0
Feb 14 14:50:04 linux-ytaf kernel: hub 6-0:1.0: USB hub found
Feb 14 14:50:04 linux-ytaf kernel: hub 6-0:1.0: 2 ports detected
Feb 14 14:50:04 linux-ytaf kernel: nouveau  [   VBIOS][0000:02:00.0] using image from PROM
Feb 14 14:50:04 linux-ytaf kernel: nouveau  [   VBIOS][0000:02:00.0] BIT signature found
Feb 14 14:50:04 linux-ytaf kernel: nouveau  [   VBIOS][0000:02:00.0] version 80.04.4b.00.07
Feb 14 14:50:04 linux-ytaf kernel: nouveau  [     PMC][0000:02:00.0] MSI interrupts enabled
Feb 14 14:50:04 linux-ytaf kernel: nouveau  [     PFB][0000:02:00.0] RAM type: GDDR5
Feb 14 14:50:04 linux-ytaf kernel: nouveau  [     PFB][0000:02:00.0] RAM size: 2048 MiB
Feb 14 14:50:04 linux-ytaf kernel: nouveau  [     PFB][0000:02:00.0]    ZCOMP: 0 tags
Feb 14 14:50:04 linux-ytaf kernel: nouveau  [    VOLT][0000:02:00.0] GPU voltage: 987500uv
Feb 14 14:50:04 linux-ytaf kernel: nouveau  [  PTHERM][0000:02:00.0] FAN control: PWM
Feb 14 14:50:04 linux-ytaf kernel: nouveau  [  PTHERM][0000:02:00.0] fan management: automatic
Feb 14 14:50:04 linux-ytaf kernel: nouveau  [  PTHERM][0000:02:00.0] internal sensor: yes
Feb 14 14:50:04 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 07: core 324 MHz memory 648 MHz 
Feb 14 14:50:04 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 0a: core 324-862 MHz memory 1620 MHz 
Feb 14 14:50:04 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 0d: core 540-1202 MHz memory 6008 MHz 
Feb 14 14:50:04 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 0f: core 540-1202 MHz memory 6008 MHz 
Feb 14 14:50:04 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] --: core 324 MHz memory 648 MHz 
Feb 14 14:50:04 linux-ytaf kernel: usb 1-1: new high-speed USB device number 2 using ehci-pci
Feb 14 14:50:04 linux-ytaf kernel: raid6: sse2x1   gen() 11244 MB/s
Feb 14 14:50:04 linux-ytaf kernel: [TTM] Zone  kernel: Available graphics memory: 4034698 kiB
Feb 14 14:50:04 linux-ytaf kernel: [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
Feb 14 14:50:04 linux-ytaf kernel: [TTM] Initializing pool allocator
Feb 14 14:50:04 linux-ytaf kernel: [TTM] Initializing DMA pool allocator
Feb 14 14:50:04 linux-ytaf kernel: nouveau  [     DRM] VRAM: 2048 MiB
Feb 14 14:50:04 linux-ytaf kernel: nouveau  [     DRM] GART: 1048576 MiB
Feb 14 14:50:04 linux-ytaf kernel: nouveau  [     DRM] TMDS table version 2.0
Feb 14 14:50:04 linux-ytaf kernel: nouveau  [     DRM] DCB version 4.0
Feb 14 14:50:04 linux-ytaf kernel: nouveau  [     DRM] DCB outp 00: 01000f02 00020030
Feb 14 14:50:04 linux-ytaf kernel: nouveau  [     DRM] DCB outp 01: 02000f00 00000000
Feb 14 14:50:04 linux-ytaf kernel: nouveau  [     DRM] DCB outp 02: 08011f82 00020030
Feb 14 14:50:04 linux-ytaf kernel: nouveau  [     DRM] DCB outp 03: 02822f62 0f420010
Feb 14 14:50:04 linux-ytaf kernel: nouveau  [     DRM] DCB outp 05: 04833fb6 0f420010
Feb 14 14:50:04 linux-ytaf kernel: nouveau  [     DRM] DCB outp 06: 04033f72 00020010
Feb 14 14:50:04 linux-ytaf kernel: nouveau  [     DRM] DCB conn 00: 00001030
Feb 14 14:50:04 linux-ytaf kernel: nouveau  [     DRM] DCB conn 01: 00020131
Feb 14 14:50:04 linux-ytaf kernel: nouveau  [     DRM] DCB conn 02: 00002261
Feb 14 14:50:04 linux-ytaf kernel: nouveau  [     DRM] DCB conn 03: 00010346
Feb 14 14:50:04 linux-ytaf kernel: nouveau  [     DRM] DCB conn 04: 00000460
Feb 14 14:50:04 linux-ytaf kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Feb 14 14:50:04 linux-ytaf kernel: [drm] Driver supports precise vblank timestamp query.
Feb 14 14:50:04 linux-ytaf kernel: nouveau  [     DRM] MM: using COPY for buffer copies
Feb 14 14:50:04 linux-ytaf kernel: raid6: sse2x1   xor()  9012 MB/s
Feb 14 14:50:05 linux-ytaf kernel: usb 4-1: new high-speed USB device number 2 using ehci-pci
Feb 14 14:50:05 linux-ytaf kernel: usb 1-1: New USB device found, idVendor=8087, idProduct=0024
Feb 14 14:50:05 linux-ytaf kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb 14 14:50:05 linux-ytaf kernel: hub 1-1:1.0: USB hub found
Feb 14 14:50:05 linux-ytaf kernel: hub 1-1:1.0: 6 ports detected
Feb 14 14:50:05 linux-ytaf kernel: raid6: sse2x2   gen() 14101 MB/s
Feb 14 14:50:05 linux-ytaf kernel: usb 5-2: new high-speed USB device number 2 using xhci_hcd
Feb 14 14:50:05 linux-ytaf kernel: raid6: sse2x2   xor() 10030 MB/s
Feb 14 14:50:05 linux-ytaf kernel: usb 4-1: New USB device found, idVendor=8087, idProduct=0024
Feb 14 14:50:05 linux-ytaf kernel: usb 4-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb 14 14:50:05 linux-ytaf kernel: hub 4-1:1.0: USB hub found
Feb 14 14:50:05 linux-ytaf kernel: hub 4-1:1.0: 8 ports detected
Feb 14 14:50:05 linux-ytaf kernel: raid6: sse2x4   gen() 16200 MB/s
Feb 14 14:50:05 linux-ytaf kernel: nouveau  [     DRM] allocated 1920x1080 fb: 0x60000, bo ffff88000af18800
Feb 14 14:50:05 linux-ytaf kernel: fbcon: nouveaufb (fb0) is primary device
Feb 14 14:50:05 linux-ytaf kernel: raid6: sse2x4   xor() 12074 MB/s
Feb 14 14:50:05 linux-ytaf kernel: raid6: using algorithm sse2x4 gen() 16200 MB/s
Feb 14 14:50:05 linux-ytaf kernel: raid6: .... xor() 12074 MB/s, rmw enabled
Feb 14 14:50:05 linux-ytaf kernel: raid6: using ssse3x2 recovery algorithm
Feb 14 14:50:05 linux-ytaf kernel: xor: automatically using best checksumming function:
Feb 14 14:50:05 linux-ytaf kernel: usb 5-2: New USB device found, idVendor=0930, idProduct=6545
Feb 14 14:50:05 linux-ytaf kernel: usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 14 14:50:05 linux-ytaf kernel: usb 5-2: Product: TransMemory
Feb 14 14:50:05 linux-ytaf kernel: usb 5-2: Manufacturer: TOSHIBA
Feb 14 14:50:05 linux-ytaf kernel: usb 5-2: SerialNumber: C89CDCBF6D59EF4140000065
Feb 14 14:50:05 linux-ytaf kernel: usb-storage 5-2:1.0: USB Mass Storage device detected
Feb 14 14:50:05 linux-ytaf kernel: scsi host8: usb-storage 5-2:1.0
Feb 14 14:50:05 linux-ytaf kernel: usbcore: registered new interface driver usb-storage
Feb 14 14:50:05 linux-ytaf kernel: usbcore: registered new interface driver uas
Feb 14 14:50:05 linux-ytaf kernel:    avx       : 31199.000 MB/sec
Feb 14 14:50:05 linux-ytaf kernel: Btrfs loaded, assert=on
Feb 14 14:50:05 linux-ytaf kernel: BTRFS: device fsid 21024970-7a27-4114-8525-d8dd026f23b6 devid 1 transid 409 /dev/sdb3
Feb 14 14:50:05 linux-ytaf kernel: usb 1-1.4: new full-speed USB device number 3 using ehci-pci
Feb 14 14:50:05 linux-ytaf kernel: usb 4-1.1: new full-speed USB device number 3 using ehci-pci
Feb 14 14:50:05 linux-ytaf kernel: usb 1-1.4: New USB device found, idVendor=06a3, idProduct=0ccb
Feb 14 14:50:05 linux-ytaf kernel: usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 14 14:50:05 linux-ytaf kernel: usb 1-1.4: Product: Cyborg R.A.T.7 Mouse
Feb 14 14:50:05 linux-ytaf kernel: usb 1-1.4: Manufacturer: Saitek
Feb 14 14:50:05 linux-ytaf kernel: usbcore: registered new interface driver usbhid
Feb 14 14:50:05 linux-ytaf kernel: usbhid: USB HID core driver
Feb 14 14:50:05 linux-ytaf kernel: usb 4-1.1: New USB device found, idVendor=1532, idProduct=0109
Feb 14 14:50:05 linux-ytaf kernel: usb 4-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 14 14:50:05 linux-ytaf kernel: usb 4-1.1: Product: Razer Lycosa
Feb 14 14:50:05 linux-ytaf kernel: usb 4-1.1: Manufacturer: Razer
Feb 14 14:50:05 linux-ytaf kernel: input: Razer Razer Lycosa as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1:1.0/0003:1532:0109.0002/input/input6
Feb 14 14:50:05 linux-ytaf kernel: hid-generic 0003:1532:0109.0002: input,hidraw0: USB HID v1.10 Keyboard [Razer Razer Lycosa] on usb-0000:00:1d.0-1.1/input0
Feb 14 14:50:05 linux-ytaf kernel: input: Razer Razer Lycosa as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1:1.1/0003:1532:0109.0003/input/input7
Feb 14 14:50:05 linux-ytaf kernel: hid-generic 0003:1532:0109.0003: input,hidraw1: USB HID v1.10 Device [Razer Razer Lycosa] on usb-0000:00:1d.0-1.1/input1
Feb 14 14:50:05 linux-ytaf kernel: Console: switching to colour frame buffer device 210x65
Feb 14 14:50:05 linux-ytaf kernel: nouveau 0000:02:00.0: fb0: nouveaufb frame buffer device
Feb 14 14:50:05 linux-ytaf kernel: nouveau 0000:02:00.0: registered panic notifier
Feb 14 14:50:05 linux-ytaf kernel: [drm] Initialized nouveau 1.2.2 20120801 for 0000:02:00.0 on minor 0
Feb 14 14:50:05 linux-ytaf kernel: [drm] Memory usable by graphics device = 2048M
Feb 14 14:50:05 linux-ytaf kernel: [drm] Replacing VGA console driver
Feb 14 14:50:05 linux-ytaf kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Feb 14 14:50:05 linux-ytaf kernel: [drm] Driver supports precise vblank timestamp query.
Feb 14 14:50:05 linux-ytaf kernel: vgaarb: device changed decodes: PCI:0000:02:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
Feb 14 14:50:05 linux-ytaf kernel: [drm] Initialized i915 1.6.0 20150327 for 0000:00:02.0 on minor 1
Feb 14 14:50:05 linux-ytaf kernel: [drm] GMBUS [i915 gmbus vga] timed out, falling back to bit banging on pin 2
Feb 14 14:50:05 linux-ytaf kernel: i915 0000:00:02.0: No connectors reported connected with modes
Feb 14 14:50:05 linux-ytaf kernel: [drm] Cannot find any crtc or sizes - going 1024x768
Feb 14 14:50:05 linux-ytaf kernel: i915 0000:00:02.0: fb1: inteldrmfb frame buffer device
Feb 14 14:50:06 linux-ytaf kernel: scsi 8:0:0:0: Direct-Access     TOSHIBA  TransMemory      PMAP PQ: 0 ANSI: 6
Feb 14 14:50:06 linux-ytaf kernel: sd 8:0:0:0: Attached scsi generic sg3 type 0
Feb 14 14:50:06 linux-ytaf kernel: sd 8:0:0:0: [sdc] 30228480 512-byte logical blocks: (15.4 GB/14.4 GiB)
Feb 14 14:50:06 linux-ytaf kernel: sd 8:0:0:0: [sdc] Write Protect is off
Feb 14 14:50:06 linux-ytaf kernel: sd 8:0:0:0: [sdc] Mode Sense: 45 00 00 00
Feb 14 14:50:06 linux-ytaf kernel: sd 8:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Feb 14 14:50:06 linux-ytaf kernel:  sdc: sdc1
Feb 14 14:50:06 linux-ytaf kernel: sd 8:0:0:0: [sdc] Attached SCSI removable disk
Feb 14 14:50:06 linux-ytaf kernel: PM: Starting manual resume from disk
Feb 14 14:50:06 linux-ytaf kernel: PM: Hibernation image partition 8:18 present
Feb 14 14:50:06 linux-ytaf kernel: PM: Looking for hibernation image.
Feb 14 14:50:06 linux-ytaf kernel: PM: Image not found (code -22)
Feb 14 14:50:06 linux-ytaf kernel: PM: Hibernation image not present or could not be loaded.
Feb 14 14:50:06 linux-ytaf kernel: BTRFS info (device sdb3): disk space caching is enabled
Feb 14 14:50:06 linux-ytaf kernel: BTRFS: has skinny extents
Feb 14 14:50:06 linux-ytaf systemd-journal[187]: Journal stopped
Feb 14 14:50:08 linux-ytaf systemd-journal[495]: Runtime journal is using 8.0M (max allowed 394.0M, trying to leave 591.0M free of 3.8G available → current limit 394.0M).
Feb 14 14:50:08 linux-ytaf systemd-journal[495]: Runtime journal is using 8.0M (max allowed 394.0M, trying to leave 591.0M free of 3.8G available → current limit 394.0M).
Feb 14 14:50:08 linux-ytaf kernel: random: nonblocking pool is initialized
Feb 14 14:50:08 linux-ytaf systemd[1]: RTC configured in localtime, applying delta of 60 minutes to system time.
Feb 14 14:50:08 linux-ytaf kernel: BTRFS info (device sdb3): disk space caching is enabled
Feb 14 14:50:08 linux-ytaf systemd-journal[495]: Journal started
Feb 14 14:50:08 linux-ytaf systemd-udevd[509]: starting version 210
Feb 14 14:50:08 linux-ytaf systemd-udevd[509]: Network interface NamePolicy= disabled on kernel commandline, ignoring.
Feb 14 14:50:08 linux-ytaf systemd-udevd[509]: invalid key/value pair in file /usr/lib/udev/rules.d/51-android.rules on line 115,starting at character 57 ('')
Feb 14 14:50:09 linux-ytaf kernel: input: PC Speaker as /devices/platform/pcspkr/input/input8
Feb 14 14:50:09 linux-ytaf kernel: thermal LNXTHERM:00: registered as thermal_zone0
Feb 14 14:50:09 linux-ytaf kernel: ACPI: Thermal Zone [TZ00] (28 C)
Feb 14 14:50:09 linux-ytaf kernel: thermal LNXTHERM:01: registered as thermal_zone1
Feb 14 14:50:09 linux-ytaf kernel: ACPI: Thermal Zone [TZ01] (30 C)
Feb 14 14:50:09 linux-ytaf mtp-probe[659]: checking bus 4, device 3: "/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1"
Feb 14 14:50:09 linux-ytaf mtp-probe[660]: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4"
Feb 14 14:50:09 linux-ytaf mtp-probe[660]: bus: 1, device: 3 was not an MTP device
Feb 14 14:50:09 linux-ytaf mtp-probe[659]: bus: 4, device: 3 was not an MTP device
Feb 14 14:50:09 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000580-0x000000000000059F conflicts with OpRegion 0x0000000000000580-0x000000000000058F (\_SB_.PCI0.SBUS.SMBI) (20150410/utaddress-254)
Feb 14 14:50:09 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000580-0x000000000000059F conflicts with OpRegion 0x0000000000000580-0x000000000000059F (\_SB_.PCI0.SMB_.SMIO) (20150410/utaddress-254)
Feb 14 14:50:09 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 14:50:09 linux-ytaf kernel: input: Saitek Cyborg R.A.T.7 Mouse as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/0003:06A3:0CCB.0001/input/input9
Feb 14 14:50:09 linux-ytaf kernel: saitek 0003:06A3:0CCB.0001: input,hidraw2: USB HID v1.11 Mouse [Saitek Cyborg R.A.T.7 Mouse] on usb-0000:00:1a.0-1.4/input0
Feb 14 14:50:09 linux-ytaf kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Feb 14 14:50:09 linux-ytaf mtp-probe[673]: checking bus 5, device 2: "/sys/devices/pci0000:00/0000:00:1c.5/0000:05:00.0/usb5/5-2"
Feb 14 14:50:09 linux-ytaf mtp-probe[673]: bus: 5, device: 2 was not an MTP device
Feb 14 14:50:09 linux-ytaf kernel: pps_core: LinuxPPS API ver. 1 registered
Feb 14 14:50:09 linux-ytaf kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
Feb 14 14:50:09 linux-ytaf kernel: PTP clock support registered
Feb 14 14:50:09 linux-ytaf kernel: asus_wmi: ASUS WMI generic driver loaded
Feb 14 14:50:09 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20150410/utaddress-254)
Feb 14 14:50:09 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 14:50:09 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150410/utaddress-254)
Feb 14 14:50:09 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150410/utaddress-254)
Feb 14 14:50:09 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 14:50:09 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150410/utaddress-254)
Feb 14 14:50:09 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150410/utaddress-254)
Feb 14 14:50:09 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 14:50:09 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150410/utaddress-254)
Feb 14 14:50:09 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150410/utaddress-254)
Feb 14 14:50:09 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 14:50:09 linux-ytaf kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
Feb 14 14:50:09 linux-ytaf kernel: asus_wmi: Initialization: 0x0
Feb 14 14:50:09 linux-ytaf kernel: asus_wmi: BIOS WMI version: 0.9
Feb 14 14:50:09 linux-ytaf kernel: asus_wmi: SFUN value: 0x0
Feb 14 14:50:09 linux-ytaf kernel: input: Eee PC WMI hotkeys as /devices/platform/eeepc-wmi/input/input10
Feb 14 14:50:09 linux-ytaf kernel: asus_wmi: Disabling ACPI video driver
Feb 14 14:50:09 linux-ytaf kernel: iTCO_vendor_support: vendor-support=0
Feb 14 14:50:09 linux-ytaf kernel: AVX version of gcm_enc/dec engaged.
Feb 14 14:50:09 linux-ytaf kernel: AES CTR mode by8 optimization enabled
Feb 14 14:50:09 linux-ytaf kernel: snd_hda_intel 0000:00:1b.0: enabling device (0000 -> 0002)
Feb 14 14:50:09 linux-ytaf kernel: snd_hda_intel 0000:02:00.1: enabling device (0000 -> 0002)
Feb 14 14:50:09 linux-ytaf kernel: snd_hda_intel 0000:02:00.1: Disabling MSI
Feb 14 14:50:09 linux-ytaf kernel: snd_hda_intel 0000:02:00.1: Handle VGA-switcheroo audio client
Feb 14 14:50:09 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC889: line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line
Feb 14 14:50:09 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Feb 14 14:50:09 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
Feb 14 14:50:09 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
Feb 14 14:50:09 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    dig-out=0x11/0x1e
Feb 14 14:50:09 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    inputs:
Feb 14 14:50:09 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:      Front Mic=0x19
Feb 14 14:50:09 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:      Rear Mic=0x18
Feb 14 14:50:09 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:      Line=0x1a
Feb 14 14:50:09 linux-ytaf kernel: input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
Feb 14 14:50:09 linux-ytaf kernel: input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
Feb 14 14:50:09 linux-ytaf kernel: input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input13
Feb 14 14:50:09 linux-ytaf kernel: input: HDA Intel PCH Line Out Front as /devices/pci0000:00/0000:00:1b.0/sound/card0/input14
Feb 14 14:50:09 linux-ytaf kernel: input: HDA Intel PCH Line Out Surround as /devices/pci0000:00/0000:00:1b.0/sound/card0/input15
Feb 14 14:50:09 linux-ytaf kernel: input: HDA Intel PCH Line Out CLFE as /devices/pci0000:00/0000:00:1b.0/sound/card0/input16
Feb 14 14:50:09 linux-ytaf kernel: input: HDA Intel PCH Line Out Side as /devices/pci0000:00/0000:00:1b.0/sound/card0/input17
Feb 14 14:50:09 linux-ytaf kernel: input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input18
Feb 14 14:50:09 linux-ytaf kernel: e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
Feb 14 14:50:09 linux-ytaf kernel: e1000e: Copyright(c) 1999 - 2014 Intel Corporation.
Feb 14 14:50:09 linux-ytaf kernel: e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
Feb 14 14:50:09 linux-ytaf kernel: iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
Feb 14 14:50:09 linux-ytaf kernel: iTCO_wdt: Found a Cougar Point TCO device (Version=2, TCOBASE=0x0460)
Feb 14 14:50:09 linux-ytaf kernel: iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
Feb 14 14:50:09 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: registered PHC clock
Feb 14 14:50:09 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) c8:60:00:09:38:76
Feb 14 14:50:09 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
Feb 14 14:50:09 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: FFFFFF-0FF
Feb 14 14:50:10 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input19
Feb 14 14:50:10 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input20
Feb 14 14:50:10 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input21
Feb 14 14:50:10 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input22
Feb 14 14:50:10 linux-ytaf kernel: Adding 2104316k swap on /dev/sdb2.  Priority:-1 extents:1 across:2104316k FS
Feb 14 14:50:10 linux-ytaf kernel: FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Feb 14 14:50:10 linux-ytaf systemd-fsck[790]: /sbin/fsck.xfs: XFS file system.
Feb 14 14:50:10 linux-ytaf kernel: SGI XFS with ACLs, security attributes, realtime, no debug enabled
Feb 14 14:50:10 linux-ytaf kernel: XFS (sdb4): Mounting V5 Filesystem
Feb 14 14:50:11 linux-ytaf kernel: XFS (sdb4): Ending clean mount
Feb 14 14:50:11 linux-ytaf systemd-journal[495]: Permanent journal is using 64.0M (max allowed 4.0G, trying to leave 4.0G free of 32.8G available → current limit 4.0G).
Feb 14 14:50:11 linux-ytaf systemd-journal[495]: Time spent on flushing to /var is 117.682ms for 1031 entries.
Feb 14 14:50:12 linux-ytaf kernel: audit: type=1305 audit(1455457811.545:2): audit_pid=815 old=0 auid=4294967295 ses=4294967295 res=1
Feb 14 14:50:11 linux-ytaf auditd[815]: Started dispatcher: /sbin/audispd pid: 825
Feb 14 14:50:11 linux-ytaf audispd[825]: priority_boost_parser called with: 4
Feb 14 14:50:11 linux-ytaf audispd[825]: max_restarts_parser called with: 10
Feb 14 14:50:11 linux-ytaf audispd[825]: No plugins found, exiting
Feb 14 14:50:11 linux-ytaf auditd[815]: Init complete, auditd 2.3.6 listening for events (startup state enable)
Feb 14 14:50:12 linux-ytaf auditctl[816]: No rules
Feb 14 14:50:12 linux-ytaf auditctl[816]: AUDIT_STATUS: enabled=0 flag=1 pid=0 rate_limit=0 backlog_limit=320 lost=0 backlog=0
Feb 14 14:50:12 linux-ytaf boot.apparmor[829]: Starting AppArmor ..done
Feb 14 14:50:12 linux-ytaf dbus-daemon[991]: Unknown username "srvGeoClue" in message bus configuration file
Feb 14 14:50:12 linux-ytaf avahi-daemon[992]: Found user 'avahi' (UID 486) and group 'avahi' (GID 485).
Feb 14 14:50:12 linux-ytaf avahi-daemon[992]: Successfully dropped root privileges.
Feb 14 14:50:12 linux-ytaf avahi-daemon[992]: avahi-daemon 0.6.31 starting up.
Feb 14 14:50:12 linux-ytaf avahi-daemon[992]: Loading service file /etc/avahi/services/sftp-ssh.service.
Feb 14 14:50:12 linux-ytaf avahi-daemon[992]: Loading service file /etc/avahi/services/ssh.service.
Feb 14 14:50:12 linux-ytaf avahi-daemon[992]: Network interface enumeration completed.
Feb 14 14:50:12 linux-ytaf avahi-daemon[992]: Registering HINFO record with values 'X86_64'/'LINUX'.
Feb 14 14:50:12 linux-ytaf avahi-daemon[992]: Server startup complete. Host name is linux-ytaf.local. Local service cookie is 2099796113.
Feb 14 14:50:12 linux-ytaf avahi-daemon[992]: Service "linux-ytaf" (/etc/avahi/services/ssh.service) successfully established.
Feb 14 14:50:12 linux-ytaf avahi-daemon[992]: Service "linux-ytaf" (/etc/avahi/services/sftp-ssh.service) successfully established.
Feb 14 14:50:13 linux-ytaf display-manager[1024]: /etc/vconsole.conf available
Feb 14 14:50:13 linux-ytaf display-manager[1024]: KEYMAP: de-latin1-nodeadkeys
Feb 14 14:50:13 linux-ytaf display-manager[1024]: Command: localectl set-keymap de-latin1-nodeadkeys
Feb 14 14:50:13 linux-ytaf display-manager[1024]: I: Using systemd /usr/share/systemd/kbd-model-map mapping
Feb 14 14:50:13 linux-ytaf dbus[991]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service'
Feb 14 14:50:13 linux-ytaf dbus[991]: [system] Successfully activated service 'org.freedesktop.locale1'
Feb 14 14:50:13 linux-ytaf smartd[997]: smartd 6.2 2013-11-07 r3856 [x86_64-linux-4.1.15-8-default] (SUSE RPM)
Feb 14 14:50:13 linux-ytaf smartd[997]: Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
Feb 14 14:50:13 linux-ytaf smartd[997]: Opened configuration file /etc/smartd.conf
Feb 14 14:50:13 linux-ytaf smartd[997]: Drive: DEVICESCAN, implied '-a' Directive on line 26 of file /etc/smartd.conf
Feb 14 14:50:13 linux-ytaf smartd[997]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
Feb 14 14:50:13 linux-ytaf smartd[997]: Device: /dev/sda, type changed from 'scsi' to 'sat'
Feb 14 14:50:13 linux-ytaf smartd[997]: Device: /dev/sda [SAT], opened
Feb 14 14:50:13 linux-ytaf smartd[997]: Device: /dev/sda [SAT], SAMSUNG SSD 830 Series, S/N:S0Z4NEAC906195, WWN:5-002538-043584d30, FW:CXM03B1Q, 256 GB
Feb 14 14:50:13 linux-ytaf smartd[997]: Device: /dev/sda [SAT], found in smartd database: Samsung based SSDs
Feb 14 14:50:13 linux-ytaf smartd[997]: Device: /dev/sda [SAT], can't monitor Current_Pending_Sector count - no Attribute 197
Feb 14 14:50:13 linux-ytaf smartd[997]: Device: /dev/sda [SAT], can't monitor Offline_Uncorrectable count - no Attribute 198
Feb 14 14:50:13 linux-ytaf smartd[997]: Device: /dev/sda [SAT], is SMART capable. Adding to "monitor" list.
Feb 14 14:50:13 linux-ytaf smartd[997]: Device: /dev/sda [SAT], state read from /var/lib/smartmontools/smartd.SAMSUNG_SSD_830_Series-S0Z4NEAC906195.ata.state
Feb 14 14:50:13 linux-ytaf smartd[997]: Device: /dev/sdb, type changed from 'scsi' to 'sat'
Feb 14 14:50:13 linux-ytaf smartd[997]: Device: /dev/sdb [SAT], opened
Feb 14 14:50:13 linux-ytaf smartd[997]: Device: /dev/sdb [SAT], TOSHIBA HDWD110, S/N:Y5GDEMGFS, WWN:5-000039-fe7c5a79c, FW:MS2OA8J0, 1.00 TB
Feb 14 14:50:13 linux-ytaf smartd[997]: Device: /dev/sdb [SAT], not found in smartd database.
Feb 14 14:50:13 linux-ytaf ModemManager[994]: <info>  ModemManager (version 1.4.10) starting in system bus...
Feb 14 14:50:13 linux-ytaf dbus[991]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Feb 14 14:50:14 linux-ytaf polkitd[1061]: Started polkitd version 0.113
Feb 14 14:50:14 linux-ytaf smartd[997]: Device: /dev/sdb [SAT], is SMART capable. Adding to "monitor" list.
Feb 14 14:50:14 linux-ytaf smartd[997]: Device: /dev/sdb [SAT], state read from /var/lib/smartmontools/smartd.TOSHIBA_HDWD110-Y5GDEMGFS.ata.state
Feb 14 14:50:14 linux-ytaf smartd[997]: Monitoring 2 ATA and 0 SCSI devices
Feb 14 14:50:14 linux-ytaf kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
Feb 14 14:50:14 linux-ytaf kernel: nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
Feb 14 14:50:14 linux-ytaf kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Feb 14 14:50:14 linux-ytaf smartd[997]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 76 to 77
Feb 14 14:50:14 linux-ytaf SuSEfirewall2[1083]: Firewall rules set to CLOSE.
Feb 14 14:50:15 linux-ytaf smartd[997]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 230 to 253
Feb 14 14:50:16 linux-ytaf polkitd[1061]: Loading rules from directory /etc/polkit-1/rules.d
Feb 14 14:50:16 linux-ytaf polkitd[1061]: Loading rules from directory /usr/share/polkit-1/rules.d
Feb 14 14:50:16 linux-ytaf polkitd[1061]: Finished loading, compiling and executing 3 rules
Feb 14 14:50:16 linux-ytaf dbus[991]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Feb 14 14:50:16 linux-ytaf polkitd[1061]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
Feb 14 14:50:16 linux-ytaf smartd[997]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.SAMSUNG_SSD_830_Series-S0Z4NEAC906195.ata.state
Feb 14 14:50:16 linux-ytaf smartd[997]: Device: /dev/sdb [SAT], state written to /var/lib/smartmontools/smartd.TOSHIBA_HDWD110-Y5GDEMGFS.ata.state
Feb 14 14:50:16 linux-ytaf kernel: No iBFT detected.
Feb 14 14:50:16 linux-ytaf logger[1091]: /etc/init.d/xdm: No changes for /etc/X11/xdm/Xservers
Feb 14 14:50:16 linux-ytaf logger[1091]: /etc/init.d/xdm: No changes for /etc/X11/xdm/xdm-config
Feb 14 14:50:17 linux-ytaf sddm[1211]: Starting...
Feb 14 14:50:17 linux-ytaf sddm[1211]: Adding new display on vt 7 ...
Feb 14 14:50:17 linux-ytaf sddm[1211]: Running: /usr/bin/X -nolisten tcp -auth /run/sddm/{f131d9d2-bdfa-491e-a864-b69546351fd9} -background none -noreset -displayfd 17 vt7
Feb 14 14:50:17 linux-ytaf display-manager[1024]: Starting service sddm..done
Feb 14 14:50:18 linux-ytaf ModemManager[994]: <info>  Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin
Feb 14 14:50:18 linux-ytaf sddm[1211]: Running display setup script  "/etc/X11/xdm/Xsetup"
Feb 14 14:50:19 linux-ytaf sddm[1211]: Display server started.
Feb 14 14:50:19 linux-ytaf sddm[1211]: Socket server starting...
Feb 14 14:50:19 linux-ytaf sddm[1211]: Socket server started.
Feb 14 14:50:19 linux-ytaf sddm[1211]: Greeter starting...
Feb 14 14:50:19 linux-ytaf sddm[1211]: Adding cookie to "/run/sddm/{f131d9d2-bdfa-491e-a864-b69546351fd9}"
Feb 14 14:50:19 linux-ytaf sddm-helper[1279]: [PAM] Starting...
Feb 14 14:50:19 linux-ytaf sddm-helper[1279]: [PAM] Authenticating...
Feb 14 14:50:19 linux-ytaf sddm-helper[1279]: [PAM] returning.
Feb 14 14:50:19 linux-ytaf sddm-helper[1279]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
Feb 14 14:50:19 linux-ytaf systemd[1281]: pam_unix(systemd-user:session): session opened for user sddm by (uid=0)
Feb 14 14:50:19 linux-ytaf kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Feb 14 14:50:19 linux-ytaf wickedd-dhcp4[1088]: eth0: Request to acquire DHCPv4 lease with UUID 1886c056-0f8b-0800-4604-000004000000
Feb 14 14:50:19 linux-ytaf sddm[1211]: Message received from greeter: Connect
Feb 14 14:50:19 linux-ytaf kernel: NET: Registered protocol family 17
Feb 14 14:50:20 linux-ytaf wickedd-dhcp4[1088]: eth0: Committed DHCPv4 lease with address 192.168.178.12 (lease time 864000 sec, renew in 432000 sec, rebind in 756000 sec)
Feb 14 14:50:20 linux-ytaf avahi-daemon[992]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.178.12.
Feb 14 14:50:20 linux-ytaf avahi-daemon[992]: New relevant interface eth0.IPv4 for mDNS.
Feb 14 14:50:20 linux-ytaf avahi-daemon[992]: Registering new address record for 192.168.178.12 on eth0.IPv4.
Feb 14 14:50:20 linux-ytaf wickedd[1094]: eth0: Notified neighbours about IP address 192.168.178.12
Feb 14 14:50:20 MM-Home wicked[1105]: lo              up
Feb 14 14:50:20 MM-Home wicked[1105]: eth0            up
Feb 14 14:50:20 MM-Home echo[1468]: Starting mail service (Postfix)
Feb 14 14:50:20 MM-Home iscsiadm[1470]: iscsiadm: No records found
Feb 14 14:50:20 MM-Home SuSEfirewall2[1498]: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Feb 14 14:50:20 MM-Home SuSEfirewall2[1507]: using default zone 'ext' for interface eth0
Feb 14 14:50:21 MM-Home ntpd[1489]: ntpd 4.2.8p4@1.3265-o Thu Dec 17 05:32:52 UTC 2015 (1): Starting
Feb 14 14:50:21 MM-Home ntpd[1489]: Command line: /usr/sbin/ntpd -p /var/run/ntp/ntpd.pid -g -u ntp:ntp -c /etc/ntp.conf
Feb 14 14:50:21 MM-Home ntpd[1631]: proto: precision = 0.094 usec (-23)
Feb 14 14:50:21 MM-Home ntpd[1631]: switching logging to file /var/log/ntp
Feb 14 14:50:21 MM-Home sntp[1633]: sntp 4.2.8p4@1.3265-o Thu Dec 17 05:32:29 UTC 2015 (1)
Feb 14 14:50:21 MM-Home sntp[1633]: kod_init_kod_db(): Cannot open KoD db file /var/db/ntp-kod: No such file or directory
Feb 14 14:50:21 MM-Home start-ntpd[1473]: Starting network time protocol daemon (NTPD)sntp 4.2.8p4@1.3265-o Thu Dec 17 05:32:29 UTC 2015 (1)
Feb 14 14:50:21 MM-Home start-ntpd[1473]: kod_init_kod_db(): Cannot open KoD db file /var/db/ntp-kod: No such file or directory
Feb 14 14:50:21 MM-Home sntp[1633]: 2016-02-14 14:50:21.230556 (-0100) -0.45336 +/- 0.348790 192.168.178.1 s3 no-leap
Feb 14 14:50:20 MM-Home start-ntpd[1473]: 2016-02-14 14:50:21.230556 (-0100) -0.45336 +/- 0.348790 192.168.178.1 s3 no-leap
Feb 14 14:50:20 MM-Home /usr/sbin/start-ntpd[1639]: runtime configuration: server 192.168.178.1
Feb 14 14:50:21 MM-Home postfix/postfix-script[1647]: starting the Postfix mail system
Feb 14 14:50:21 MM-Home postfix/master[1653]: daemon started -- version 2.11.6, configuration /etc/postfix
Feb 14 14:50:21 MM-Home SuSEfirewall2[1676]: Firewall rules successfully set
Feb 14 14:50:21 MM-Home cron[1687]: (CRON) INFO (RANDOM_DELAY will be scaled with factor 48% if used.)
Feb 14 14:50:21 MM-Home cron[1687]: (CRON) INFO (running with inotify support)
Feb 14 14:50:22 MM-Home dbus[991]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
Feb 14 14:50:22 MM-Home udisksd[1691]: udisks daemon version 2.1.6 starting
Feb 14 14:50:23 MM-Home dbus[991]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Feb 14 14:50:23 MM-Home udisksd[1691]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Feb 14 14:50:23 MM-Home dbus[991]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
Feb 14 14:50:23 MM-Home dbus[991]: [system] Successfully activated service 'org.freedesktop.UPower'
Feb 14 14:50:31 MM-Home kernel: nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
Feb 14 14:51:01 MM-Home sddm[1211]: Message received from greeter: Login
Feb 14 14:51:01 MM-Home sddm[1211]: Reading from "/usr/share/xsessions/plasma5.desktop"
Feb 14 14:51:01 MM-Home sddm[1211]: Session "/usr/share/xsessions/plasma5.desktop" selected, command: "/usr/bin/startkde"
Feb 14 14:51:01 MM-Home sddm-helper[1729]: [PAM] Starting...
Feb 14 14:51:01 MM-Home sddm-helper[1729]: [PAM] Authenticating...
Feb 14 14:51:01 MM-Home sddm-helper[1729]: [PAM] Preparing to converse...
Feb 14 14:51:01 MM-Home sddm-helper[1729]: [PAM] Conversation with 1 messages
Feb 14 14:51:01 MM-Home sddm-helper[1729]: [PAM] returning.
Feb 14 14:51:01 MM-Home sddm[1211]: Authenticated successfully
Feb 14 14:51:01 MM-Home sddm-helper[1729]: pam_unix(sddm:session): session opened for user marc by (uid=0)
Feb 14 14:51:01 MM-Home systemd[1730]: pam_unix(systemd-user:session): session opened for user marc by (uid=0)
Feb 14 14:51:01 MM-Home sddm-helper[1732]: Adding cookie to "/home/marc/.Xauthority"
Feb 14 14:51:01 MM-Home sddm-helper[1279]: [PAM] Ended.
Feb 14 14:51:01 MM-Home sddm[1211]: Auth: sddm-helper exited successfully
Feb 14 14:51:01 MM-Home sddm[1211]: Session started
Feb 14 14:51:02 MM-Home dbus[991]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Feb 14 14:51:02 MM-Home org.kde.powerdevil.backlighthelper[991]: powerdevil: no kernel backlight interface found
Feb 14 14:51:02 MM-Home dbus[991]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Feb 14 14:51:03 MM-Home polkitd[1061]: Registered Authentication Agent for unix-session:2 (system bus name :1.35 [/usr/lib64/libexec/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale de_DE.UTF-8)
Feb 14 14:51:04 MM-Home dbus[991]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service'
Feb 14 14:51:04 MM-Home dbus[991]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Feb 14 14:51:04 MM-Home rtkit-daemon[1887]: Successfully called chroot.
Feb 14 14:51:04 MM-Home rtkit-daemon[1887]: Successfully dropped privileges.
Feb 14 14:51:04 MM-Home rtkit-daemon[1887]: Successfully limited resources.
Feb 14 14:51:04 MM-Home rtkit-daemon[1887]: Running.
Feb 14 14:51:04 MM-Home rtkit-daemon[1887]: Watchdog thread running.
Feb 14 14:51:04 MM-Home rtkit-daemon[1887]: Canary thread running.
Feb 14 14:51:04 MM-Home rtkit-daemon[1887]: Successfully made thread 1886 of process 1886 (/usr/bin/pulseaudio) owned by 'marc' high priority at nice level -11.
Feb 14 14:51:04 MM-Home rtkit-daemon[1887]: Supervising 1 threads of 1 processes of 1 users.
Feb 14 14:51:07 MM-Home rtkit-daemon[1887]: Supervising 1 threads of 1 processes of 1 users.
Feb 14 14:51:07 MM-Home rtkit-daemon[1887]: Successfully made thread 1915 of process 1886 (/usr/bin/pulseaudio) owned by 'marc' RT at priority 5.
Feb 14 14:51:07 MM-Home rtkit-daemon[1887]: Supervising 2 threads of 1 processes of 1 users.
Feb 14 14:51:07 MM-Home rtkit-daemon[1887]: Supervising 2 threads of 1 processes of 1 users.
Feb 14 14:51:07 MM-Home rtkit-daemon[1887]: Successfully made thread 1916 of process 1886 (/usr/bin/pulseaudio) owned by 'marc' RT at priority 5.
Feb 14 14:51:07 MM-Home rtkit-daemon[1887]: Supervising 3 threads of 1 processes of 1 users.
Feb 14 14:51:07 MM-Home rtkit-daemon[1887]: Supervising 3 threads of 1 processes of 1 users.
Feb 14 14:51:07 MM-Home rtkit-daemon[1887]: Successfully made thread 1917 of process 1886 (/usr/bin/pulseaudio) owned by 'marc' RT at priority 5.
Feb 14 14:51:07 MM-Home rtkit-daemon[1887]: Supervising 4 threads of 1 processes of 1 users.
Feb 14 14:51:07 MM-Home dbus[991]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Feb 14 14:51:07 MM-Home bluetoothd[1918]: Bluetooth daemon 5.35
Feb 14 14:51:07 MM-Home dbus[991]: [system] Successfully activated service 'org.bluez'
Feb 14 14:51:07 MM-Home bluetoothd[1918]: Starting SDP server
Feb 14 14:51:07 MM-Home kernel: Bluetooth: Core ver 2.20
Feb 14 14:51:07 MM-Home kernel: NET: Registered protocol family 31
Feb 14 14:51:07 MM-Home kernel: Bluetooth: HCI device and connection manager initialized
Feb 14 14:51:07 MM-Home kernel: Bluetooth: HCI socket layer initialized
Feb 14 14:51:07 MM-Home kernel: Bluetooth: L2CAP socket layer initialized
Feb 14 14:51:07 MM-Home kernel: Bluetooth: SCO socket layer initialized
Feb 14 14:51:07 MM-Home kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Feb 14 14:51:07 MM-Home kernel: Bluetooth: BNEP filters: protocol multicast
Feb 14 14:51:07 MM-Home kernel: Bluetooth: BNEP socket layer initialized
Feb 14 14:51:07 MM-Home dbus[991]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Feb 14 14:51:07 MM-Home bluetoothd[1918]: Bluetooth management interface 1.9 initialized
Feb 14 14:51:07 MM-Home dbus[991]: [system] Successfully activated service 'org.freedesktop.hostname1'
Feb 14 14:51:07 MM-Home rtkit-daemon[1887]: Successfully made thread 1927 of process 1927 (/usr/bin/pulseaudio) owned by 'marc' high priority at nice level -11.
Feb 14 14:51:07 MM-Home rtkit-daemon[1887]: Supervising 5 threads of 2 processes of 1 users.
Feb 14 14:51:07 MM-Home pulseaudio[1927]: [pulseaudio] pid.c: Daemon already running.
Feb 14 14:51:07 MM-Home rtkit-daemon[1887]: Successfully made thread 1929 of process 1929 (/usr/bin/pulseaudio) owned by 'marc' high priority at nice level -11.
Feb 14 14:51:07 MM-Home rtkit-daemon[1887]: Supervising 5 threads of 2 processes of 1 users.
Feb 14 14:51:07 MM-Home pulseaudio[1929]: [pulseaudio] pid.c: Daemon already running.
Feb 14 14:51:07 MM-Home dbus[991]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service'
Feb 14 14:51:07 MM-Home PackageKit[1933]: daemon start
Feb 14 14:51:08 MM-Home dbus[991]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Feb 14 14:51:09 MM-Home PackageKit[1933]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 14:51:09 MM-Home PackageKit[1933]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 14:51:09 MM-Home PackageKit[1933]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 14:51:09 MM-Home PackageKit[1933]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 14:51:09 MM-Home PackageKit[1933]: refresh-cache transaction /1_ebecebbc from uid 1000 finished with failed after 849ms
Feb 14 14:51:09 MM-Home kernel: fuse init (API version 7.23)
Feb 14 14:51:10 MM-Home PackageKit[1933]: refresh-cache transaction /2_ecbdabed from uid 1000 finished with failed after 297ms
Feb 14 14:51:28 MM-Home PackageKit[1933]: daemon quit
Feb 14 14:51:28 MM-Home packagekitd[1933]: (packagekitd:1933): GLib-CRITICAL **: Source ID 6 was not found when attempting to remove it
Feb 14 14:59:24 MM-Home org.kde.kuiserver[1780]: kuiserver: adding job contact for address:  ":1.18"  objectPath:  "/DataEngine/applicationjobs/JobView_1"
Feb 14 14:59:24 MM-Home org.kde.kuiserver[1780]: kuiserver: making async call of terminate for:  "/DataEngine/applicationjobs/JobView_1"
Feb 14 14:59:24 MM-Home org.kde.kuiserver[1780]: kuiserver: removing jobview from list, it finished
Feb 14 14:59:57 MM-Home org.kde.kuiserver[1780]: kuiserver: adding job contact for address:  ":1.18"  objectPath:  "/DataEngine/applicationjobs/JobView_2"
Feb 14 14:59:57 MM-Home org.kde.kuiserver[1780]: kuiserver: making async call of terminate for:  "/DataEngine/applicationjobs/JobView_2"
Feb 14 14:59:57 MM-Home org.kde.kuiserver[1780]: kuiserver: removing jobview from list, it finished
Feb 14 15:00:01 MM-Home cron[2195]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 15:00:01 MM-Home systemd[2196]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 15:00:01 MM-Home CRON[2195]: pam_unix(crond:session): session closed for user root
Feb 14 15:00:01 MM-Home systemd[2197]: pam_unix(systemd-user:session): session closed for user root
Feb 14 15:00:48 MM-Home org.kde.kuiserver[1780]: kuiserver: adding job contact for address:  ":1.18"  objectPath:  "/DataEngine/applicationjobs/JobView_3"
Feb 14 15:00:48 MM-Home org.kde.kuiserver[1780]: kuiserver: making async call of terminate for:  "/DataEngine/applicationjobs/JobView_3"
Feb 14 15:00:48 MM-Home org.kde.kuiserver[1780]: kuiserver: removing jobview from list, it finished
-- Reboot --
Feb 14 15:13:43 linux-ytaf systemd-journal[187]: Runtime journal is using 8.0M (max allowed 394.0M, trying to leave 591.0M free of 3.8G available → current limit 394.0M).
Feb 14 15:13:43 linux-ytaf systemd-journal[187]: Runtime journal is using 8.0M (max allowed 394.0M, trying to leave 591.0M free of 3.8G available → current limit 394.0M).
Feb 14 15:13:43 linux-ytaf kernel: microcode: CPU0 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 15:13:43 linux-ytaf kernel: Initializing cgroup subsys cpuset
Feb 14 15:13:43 linux-ytaf kernel: Initializing cgroup subsys cpu
Feb 14 15:13:43 linux-ytaf kernel: Initializing cgroup subsys cpuacct
Feb 14 15:13:43 linux-ytaf kernel: Linux version 4.1.15-8-default (geeko@buildhost) (gcc version 4.8.5 (SUSE Linux) ) #1 SMP PREEMPT Wed Jan 20 16:41:00 UTC 2016 (0e3b3ab)
Feb 14 15:13:43 linux-ytaf kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.1.15-8-default root=UUID=21024970-7a27-4114-8525-d8dd026f23b6 ro resume=/dev/sdb2 splash=silent quiet showopts
Feb 14 15:13:43 linux-ytaf kernel: e820: BIOS-provided physical RAM map:
Feb 14 15:13:43 linux-ytaf kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Feb 14 15:13:43 linux-ytaf kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
Feb 14 15:13:43 linux-ytaf kernel: BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable
Feb 14 15:13:43 linux-ytaf kernel: BIOS-e820: [mem 0x0000000020000000-0x00000000201fffff] reserved
Feb 14 15:13:43 linux-ytaf kernel: BIOS-e820: [mem 0x0000000020200000-0x000000003fffffff] usable
Feb 14 15:13:43 linux-ytaf kernel: BIOS-e820: [mem 0x0000000040000000-0x00000000401fffff] reserved
Feb 14 15:13:43 linux-ytaf kernel: BIOS-e820: [mem 0x0000000040200000-0x00000000ca38efff] usable
Feb 14 15:13:43 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ca38f000-0x00000000ca5f1fff] reserved
Feb 14 15:13:43 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ca5f2000-0x00000000ca679fff] ACPI NVS
Feb 14 15:13:43 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ca67a000-0x00000000ca93efff] reserved
Feb 14 15:13:43 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ca93f000-0x00000000cab83fff] ACPI NVS
Feb 14 15:13:43 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cab84000-0x00000000cab91fff] ACPI data
Feb 14 15:13:43 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cab92000-0x00000000cabbefff] ACPI NVS
Feb 14 15:13:43 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cabbf000-0x00000000cabc3fff] ACPI data
Feb 14 15:13:43 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cabc4000-0x00000000cac06fff] ACPI NVS
Feb 14 15:13:43 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cac07000-0x00000000caffffff] usable
Feb 14 15:13:43 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cb800000-0x00000000cf9fffff] reserved
Feb 14 15:13:43 linux-ytaf kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Feb 14 15:13:43 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Feb 14 15:13:43 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Feb 14 15:13:43 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Feb 14 15:13:43 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Feb 14 15:13:43 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Feb 14 15:13:43 linux-ytaf kernel: BIOS-e820: [mem 0x0000000100000000-0x000000022f5fffff] usable
Feb 14 15:13:43 linux-ytaf kernel: NX (Execute Disable) protection: active
Feb 14 15:13:43 linux-ytaf kernel: e820: update [mem 0x0c826018-0x0c835c57] usable ==> usable
Feb 14 15:13:43 linux-ytaf kernel: e820: update [mem 0x0c836018-0x0c846057] usable ==> usable
Feb 14 15:13:43 linux-ytaf kernel: e820: update [mem 0x0c847018-0x0c856857] usable ==> usable
Feb 14 15:13:43 linux-ytaf kernel: e820: update [mem 0x0c857018-0x0c85ae57] usable ==> usable
Feb 14 15:13:43 linux-ytaf kernel: extended physical RAM map:
Feb 14 15:13:43 linux-ytaf kernel: reserve setup_data: [mem 0x0000000000000000-0x000000000009efff] usable
Feb 14 15:13:43 linux-ytaf kernel: reserve setup_data: [mem 0x000000000009f000-0x000000000009ffff] reserved
Feb 14 15:13:43 linux-ytaf kernel: reserve setup_data: [mem 0x0000000000100000-0x000000000c826017] usable
Feb 14 15:13:43 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c826018-0x000000000c835c57] usable
Feb 14 15:13:43 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c835c58-0x000000000c836017] usable
Feb 14 15:13:43 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c836018-0x000000000c846057] usable
Feb 14 15:13:43 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c846058-0x000000000c847017] usable
Feb 14 15:13:43 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c847018-0x000000000c856857] usable
Feb 14 15:13:43 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c856858-0x000000000c857017] usable
Feb 14 15:13:43 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c857018-0x000000000c85ae57] usable
Feb 14 15:13:43 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c85ae58-0x000000001fffffff] usable
Feb 14 15:13:43 linux-ytaf kernel: reserve setup_data: [mem 0x0000000020000000-0x00000000201fffff] reserved
Feb 14 15:13:43 linux-ytaf kernel: reserve setup_data: [mem 0x0000000020200000-0x000000003fffffff] usable
Feb 14 15:13:43 linux-ytaf kernel: reserve setup_data: [mem 0x0000000040000000-0x00000000401fffff] reserved
Feb 14 15:13:43 linux-ytaf kernel: reserve setup_data: [mem 0x0000000040200000-0x00000000ca38efff] usable
Feb 14 15:13:43 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ca38f000-0x00000000ca5f1fff] reserved
Feb 14 15:13:43 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ca5f2000-0x00000000ca679fff] ACPI NVS
Feb 14 15:13:43 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ca67a000-0x00000000ca93efff] reserved
Feb 14 15:13:43 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ca93f000-0x00000000cab83fff] ACPI NVS
Feb 14 15:13:43 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cab84000-0x00000000cab91fff] ACPI data
Feb 14 15:13:43 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cab92000-0x00000000cabbefff] ACPI NVS
Feb 14 15:13:43 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cabbf000-0x00000000cabc3fff] ACPI data
Feb 14 15:13:43 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cabc4000-0x00000000cac06fff] ACPI NVS
Feb 14 15:13:43 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cac07000-0x00000000caffffff] usable
Feb 14 15:13:43 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cb800000-0x00000000cf9fffff] reserved
Feb 14 15:13:43 linux-ytaf kernel: reserve setup_data: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Feb 14 15:13:43 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Feb 14 15:13:43 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Feb 14 15:13:43 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Feb 14 15:13:43 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Feb 14 15:13:43 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Feb 14 15:13:43 linux-ytaf kernel: reserve setup_data: [mem 0x0000000100000000-0x000000022f5fffff] usable
Feb 14 15:13:43 linux-ytaf kernel: efi: EFI v2.31 by American Megatrends
Feb 14 15:13:43 linux-ytaf kernel: efi:  ACPI=0xcab84000  ACPI 2.0=0xcab84000  SMBIOS=0xca427e98  MPS=0xfc990 
Feb 14 15:13:43 linux-ytaf kernel: SMBIOS 2.6 present.
Feb 14 15:13:43 linux-ytaf kernel: DMI: System manufacturer System Product Name/MAXIMUS IV GENE-Z/GEN3, BIOS 3603 11/09/2012
Feb 14 15:13:43 linux-ytaf kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Feb 14 15:13:43 linux-ytaf kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Feb 14 15:13:43 linux-ytaf kernel: AGP: No AGP bridge found
Feb 14 15:13:43 linux-ytaf kernel: e820: last_pfn = 0x22f600 max_arch_pfn = 0x400000000
Feb 14 15:13:43 linux-ytaf kernel: MTRR default type: uncachable
Feb 14 15:13:43 linux-ytaf kernel: MTRR fixed ranges enabled:
Feb 14 15:13:43 linux-ytaf kernel:   00000-9FFFF write-back
Feb 14 15:13:43 linux-ytaf kernel:   A0000-BFFFF uncachable
Feb 14 15:13:43 linux-ytaf kernel:   C0000-D3FFF write-protect
Feb 14 15:13:43 linux-ytaf kernel:   D4000-DFFFF uncachable
Feb 14 15:13:43 linux-ytaf kernel:   E0000-E7FFF write-through
Feb 14 15:13:43 linux-ytaf kernel:   E8000-FFFFF write-protect
Feb 14 15:13:43 linux-ytaf kernel: MTRR variable ranges enabled:
Feb 14 15:13:43 linux-ytaf kernel:   0 base 000000000 mask E00000000 write-back
Feb 14 15:13:43 linux-ytaf kernel:   1 base 200000000 mask FE0000000 write-back
Feb 14 15:13:43 linux-ytaf kernel:   2 base 220000000 mask FF0000000 write-back
Feb 14 15:13:43 linux-ytaf kernel:   3 base 0E0000000 mask FE0000000 uncachable
Feb 14 15:13:43 linux-ytaf kernel:   4 base 0D0000000 mask FF0000000 uncachable
Feb 14 15:13:43 linux-ytaf kernel:   5 base 0CC000000 mask FFC000000 uncachable
Feb 14 15:13:43 linux-ytaf kernel:   6 base 0CB800000 mask FFF800000 uncachable
Feb 14 15:13:43 linux-ytaf kernel:   7 base 22F800000 mask FFF800000 uncachable
Feb 14 15:13:43 linux-ytaf kernel:   8 base 22F600000 mask FFFE00000 uncachable
Feb 14 15:13:43 linux-ytaf kernel:   9 disabled
Feb 14 15:13:43 linux-ytaf kernel: PAT configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- UC  
Feb 14 15:13:43 linux-ytaf kernel: e820: update [mem 0xcb800000-0xffffffff] usable ==> reserved
Feb 14 15:13:43 linux-ytaf kernel: e820: last_pfn = 0xcb000 max_arch_pfn = 0x400000000
Feb 14 15:13:43 linux-ytaf kernel: found SMP MP-table at [mem 0x000fcd30-0x000fcd3f] mapped at [ffff8800000fcd30]
Feb 14 15:13:43 linux-ytaf kernel: Scanning 1 areas for low memory corruption
Feb 14 15:13:43 linux-ytaf kernel: Base memory trampoline at [ffff880000097000] 97000 size 24576
Feb 14 15:13:43 linux-ytaf kernel: reserving inaccessible SNB gfx pages
Feb 14 15:13:43 linux-ytaf kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
Feb 14 15:13:43 linux-ytaf kernel:  [mem 0x00000000-0x000fffff] page 4k
Feb 14 15:13:43 linux-ytaf kernel: BRK [0x0e21a000, 0x0e21afff] PGTABLE
Feb 14 15:13:43 linux-ytaf kernel: BRK [0x0e21b000, 0x0e21bfff] PGTABLE
Feb 14 15:13:43 linux-ytaf kernel: BRK [0x0e21c000, 0x0e21cfff] PGTABLE
Feb 14 15:13:43 linux-ytaf kernel: init_memory_mapping: [mem 0x22f400000-0x22f5fffff]
Feb 14 15:13:43 linux-ytaf kernel:  [mem 0x22f400000-0x22f5fffff] page 2M
Feb 14 15:13:43 linux-ytaf kernel: BRK [0x0e21d000, 0x0e21dfff] PGTABLE
Feb 14 15:13:43 linux-ytaf kernel: init_memory_mapping: [mem 0x220000000-0x22f3fffff]
Feb 14 15:13:43 linux-ytaf kernel:  [mem 0x220000000-0x22f3fffff] page 2M
Feb 14 15:13:43 linux-ytaf kernel: init_memory_mapping: [mem 0x200000000-0x21fffffff]
Feb 14 15:13:43 linux-ytaf kernel:  [mem 0x200000000-0x21fffffff] page 2M
Feb 14 15:13:43 linux-ytaf kernel: init_memory_mapping: [mem 0x00100000-0x1fffffff]
Feb 14 15:13:43 linux-ytaf kernel:  [mem 0x00100000-0x001fffff] page 4k
Feb 14 15:13:43 linux-ytaf kernel:  [mem 0x00200000-0x1fffffff] page 2M
Feb 14 15:13:43 linux-ytaf kernel: init_memory_mapping: [mem 0x20200000-0x3fffffff]
Feb 14 15:13:43 linux-ytaf kernel:  [mem 0x20200000-0x3fffffff] page 2M
Feb 14 15:13:43 linux-ytaf kernel: init_memory_mapping: [mem 0x40200000-0xca38efff]
Feb 14 15:13:43 linux-ytaf kernel:  [mem 0x40200000-0xca1fffff] page 2M
Feb 14 15:13:43 linux-ytaf kernel:  [mem 0xca200000-0xca38efff] page 4k
Feb 14 15:13:43 linux-ytaf kernel: BRK [0x0e21e000, 0x0e21efff] PGTABLE
Feb 14 15:13:43 linux-ytaf kernel: BRK [0x0e21f000, 0x0e21ffff] PGTABLE
Feb 14 15:13:43 linux-ytaf kernel: init_memory_mapping: [mem 0xcac07000-0xcaffffff]
Feb 14 15:13:43 linux-ytaf kernel:  [mem 0xcac07000-0xcadfffff] page 4k
Feb 14 15:13:43 linux-ytaf kernel:  [mem 0xcae00000-0xcaffffff] page 2M
Feb 14 15:13:43 linux-ytaf kernel: init_memory_mapping: [mem 0x100000000-0x1ffffffff]
Feb 14 15:13:43 linux-ytaf kernel:  [mem 0x100000000-0x1ffffffff] page 2M
Feb 14 15:13:43 linux-ytaf kernel: RAMDISK: [mem 0x00457000-0x00ffafff]
Feb 14 15:13:43 linux-ytaf kernel: ACPI: Early table checksum verification disabled
Feb 14 15:13:43 linux-ytaf kernel: ACPI: RSDP 0x00000000CAB84000 000024 (v02 ALASKA)
Feb 14 15:13:43 linux-ytaf kernel: ACPI: XSDT 0x00000000CAB84078 000064 (v01 ALASKA A M I    01072009 AMI  00010013)
Feb 14 15:13:43 linux-ytaf kernel: ACPI: FACP 0x00000000CAB8FC78 0000F4 (v04 ALASKA A M I    01072009 AMI  00010013)
Feb 14 15:13:43 linux-ytaf kernel: ACPI: DSDT 0x00000000CAB84170 00BB02 (v02 ALASKA A M I    00000015 INTL 20051117)
Feb 14 15:13:43 linux-ytaf kernel: ACPI: FACS 0x00000000CABBDF80 000040
Feb 14 15:13:43 linux-ytaf kernel: ACPI: APIC 0x00000000CAB8FD70 000092 (v03 ALASKA A M I    01072009 AMI  00010013)
Feb 14 15:13:43 linux-ytaf kernel: ACPI: MCFG 0x00000000CAB8FE08 00003C (v01 ALASKA A M I    01072009 MSFT 00000097)
Feb 14 15:13:43 linux-ytaf kernel: ACPI: HPET 0x00000000CAB8FE48 000038 (v01 ALASKA A M I    01072009 AMI. 00000005)
Feb 14 15:13:43 linux-ytaf kernel: ACPI: SSDT 0x00000000CAB8FE80 00036D (v01 SataRe SataTabl 00001000 INTL 20091112)
Feb 14 15:13:43 linux-ytaf kernel: ACPI: SSDT 0x00000000CAB901F0 0009AA (v01 PmRef  Cpu0Ist  00003000 INTL 20051117)
Feb 14 15:13:43 linux-ytaf kernel: ACPI: SSDT 0x00000000CAB90BA0 000A92 (v01 PmRef  CpuPm    00003000 INTL 20051117)
Feb 14 15:13:43 linux-ytaf kernel: ACPI: BGRT 0x00000000CAB91690 000038 (v00 ALASKA A M I    01072009 AMI  00010013)
Feb 14 15:13:43 linux-ytaf kernel: ACPI: Local APIC address 0xfee00000
Feb 14 15:13:43 linux-ytaf kernel: No NUMA configuration found
Feb 14 15:13:43 linux-ytaf kernel: Faking a node at [mem 0x0000000000000000-0x000000022f5fffff]
Feb 14 15:13:43 linux-ytaf kernel: NODE_DATA(0) allocated [mem 0x22f5e5000-0x22f5f8fff]
Feb 14 15:13:43 linux-ytaf kernel:  [ffffea0000000000-ffffea0008bfffff] PMD -> [ffff880226c00000-ffff88022ebfffff] on node 0
Feb 14 15:13:43 linux-ytaf kernel: Zone ranges:
Feb 14 15:13:43 linux-ytaf kernel:   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
Feb 14 15:13:43 linux-ytaf kernel:   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
Feb 14 15:13:43 linux-ytaf kernel:   Normal   [mem 0x0000000100000000-0x000000022f5fffff]
Feb 14 15:13:43 linux-ytaf kernel: Movable zone start for each node
Feb 14 15:13:43 linux-ytaf kernel: Early memory node ranges
Feb 14 15:13:43 linux-ytaf kernel:   node   0: [mem 0x0000000000001000-0x000000000009efff]
Feb 14 15:13:43 linux-ytaf kernel:   node   0: [mem 0x0000000000100000-0x000000001fffffff]
Feb 14 15:13:43 linux-ytaf kernel:   node   0: [mem 0x0000000020200000-0x000000003fffffff]
Feb 14 15:13:43 linux-ytaf kernel:   node   0: [mem 0x0000000040200000-0x00000000ca38efff]
Feb 14 15:13:43 linux-ytaf kernel:   node   0: [mem 0x00000000cac07000-0x00000000caffffff]
Feb 14 15:13:43 linux-ytaf kernel:   node   0: [mem 0x0000000100000000-0x000000022f5fffff]
Feb 14 15:13:43 linux-ytaf kernel: Initmem setup node 0 [mem 0x0000000000001000-0x000000022f5fffff]
Feb 14 15:13:43 linux-ytaf kernel: On node 0 totalpages: 2070822
Feb 14 15:13:43 linux-ytaf kernel:   DMA zone: 64 pages used for memmap
Feb 14 15:13:43 linux-ytaf kernel:   DMA zone: 3138 pages reserved
Feb 14 15:13:43 linux-ytaf kernel:   DMA zone: 3998 pages, LIFO batch:0
Feb 14 15:13:43 linux-ytaf kernel:   DMA32 zone: 12879 pages used for memmap
Feb 14 15:13:43 linux-ytaf kernel:   DMA32 zone: 824200 pages, LIFO batch:31
Feb 14 15:13:43 linux-ytaf kernel:   Normal zone: 19416 pages used for memmap
Feb 14 15:13:43 linux-ytaf kernel:   Normal zone: 1242624 pages, LIFO batch:31
Feb 14 15:13:43 linux-ytaf kernel: tboot: non-0 tboot_addr but it is not of type E820_RESERVED
Feb 14 15:13:43 linux-ytaf kernel: ACPI: PM-Timer IO Port: 0x408
Feb 14 15:13:43 linux-ytaf kernel: ACPI: Local APIC address 0xfee00000
Feb 14 15:13:43 linux-ytaf kernel: ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
Feb 14 15:13:43 linux-ytaf kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
Feb 14 15:13:43 linux-ytaf kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Feb 14 15:13:43 linux-ytaf kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Feb 14 15:13:43 linux-ytaf kernel: ACPI: IRQ0 used by override.
Feb 14 15:13:43 linux-ytaf kernel: ACPI: IRQ9 used by override.
Feb 14 15:13:43 linux-ytaf kernel: Using ACPI (MADT) for SMP configuration information
Feb 14 15:13:43 linux-ytaf kernel: ACPI: HPET id: 0x8086a701 base: 0xfed00000
Feb 14 15:13:43 linux-ytaf kernel: smpboot: Allowing 8 CPUs, 0 hotplug CPUs
Feb 14 15:13:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
Feb 14 15:13:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Feb 14 15:13:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000fffff]
Feb 14 15:13:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c826000-0x0c826fff]
Feb 14 15:13:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c835000-0x0c835fff]
Feb 14 15:13:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c836000-0x0c836fff]
Feb 14 15:13:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c846000-0x0c846fff]
Feb 14 15:13:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c847000-0x0c847fff]
Feb 14 15:13:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c856000-0x0c856fff]
Feb 14 15:13:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c857000-0x0c857fff]
Feb 14 15:13:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c85a000-0x0c85afff]
Feb 14 15:13:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x20000000-0x201fffff]
Feb 14 15:13:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x40000000-0x401fffff]
Feb 14 15:13:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xca38f000-0xca5f1fff]
Feb 14 15:13:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xca5f2000-0xca679fff]
Feb 14 15:13:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xca67a000-0xca93efff]
Feb 14 15:13:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xca93f000-0xcab83fff]
Feb 14 15:13:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcab84000-0xcab91fff]
Feb 14 15:13:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcab92000-0xcabbefff]
Feb 14 15:13:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcabbf000-0xcabc3fff]
Feb 14 15:13:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcabc4000-0xcac06fff]
Feb 14 15:13:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcb000000-0xcb7fffff]
Feb 14 15:13:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcb800000-0xcf9fffff]
Feb 14 15:13:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcfa00000-0xf7ffffff]
Feb 14 15:13:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
Feb 14 15:13:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfc000000-0xfebfffff]
Feb 14 15:13:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
Feb 14 15:13:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfec01000-0xfecfffff]
Feb 14 15:13:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed00000-0xfed03fff]
Feb 14 15:13:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed04000-0xfed1bfff]
Feb 14 15:13:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Feb 14 15:13:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed20000-0xfedfffff]
Feb 14 15:13:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
Feb 14 15:13:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfee01000-0xfeffffff]
Feb 14 15:13:43 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Feb 14 15:13:43 linux-ytaf kernel: e820: [mem 0xcfa00000-0xf7ffffff] available for PCI devices
Feb 14 15:13:43 linux-ytaf kernel: Booting paravirtualized kernel on bare hardware
Feb 14 15:13:43 linux-ytaf kernel: clocksource refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
Feb 14 15:13:43 linux-ytaf kernel: setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:8 nr_node_ids:1
Feb 14 15:13:43 linux-ytaf kernel: PERCPU: Embedded 33 pages/cpu @ffff88022f200000 s97368 r8192 d29608 u262144
Feb 14 15:13:43 linux-ytaf kernel: pcpu-alloc: s97368 r8192 d29608 u262144 alloc=1*2097152
Feb 14 15:13:43 linux-ytaf kernel: pcpu-alloc: [0] 0 1 2 3 4 5 6 7 
Feb 14 15:13:43 linux-ytaf kernel: Built 1 zonelists in Node order, mobility grouping on.  Total pages: 2035325
Feb 14 15:13:43 linux-ytaf kernel: Policy zone: Normal
Feb 14 15:13:43 linux-ytaf kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.1.15-8-default root=UUID=21024970-7a27-4114-8525-d8dd026f23b6 ro resume=/dev/sdb2 splash=silent quiet showopts
Feb 14 15:13:43 linux-ytaf kernel: log_buf_len individual max cpu contribution: 32768 bytes
Feb 14 15:13:43 linux-ytaf kernel: log_buf_len total cpu_extra contributions: 229376 bytes
Feb 14 15:13:43 linux-ytaf kernel: log_buf_len min size: 262144 bytes
Feb 14 15:13:43 linux-ytaf kernel: log_buf_len: 524288 bytes
Feb 14 15:13:43 linux-ytaf kernel: early log buf free: 245492(93%)
Feb 14 15:13:43 linux-ytaf kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
Feb 14 15:13:43 linux-ytaf kernel: xsave: enabled xstate_bv 0x7, cntxt size 0x340 using standard form
Feb 14 15:13:43 linux-ytaf kernel: AGP: Checking aperture...
Feb 14 15:13:43 linux-ytaf kernel: AGP: No AGP bridge found
Feb 14 15:13:43 linux-ytaf kernel: Memory: 7863196K/8283288K available (6547K kernel code, 1084K rwdata, 4848K rodata, 1560K init, 1516K bss, 420092K reserved, 0K cma-reserved)
Feb 14 15:13:43 linux-ytaf kernel: Preemptible hierarchical RCU implementation.
Feb 14 15:13:43 linux-ytaf kernel:         RCU dyntick-idle grace-period acceleration is enabled.
Feb 14 15:13:43 linux-ytaf kernel:         RCU restricting CPUs from NR_CPUS=512 to nr_cpu_ids=8.
Feb 14 15:13:43 linux-ytaf kernel: RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
Feb 14 15:13:43 linux-ytaf kernel: NR_IRQS:33024 nr_irqs:488 16
Feb 14 15:13:43 linux-ytaf kernel:         Offload RCU callbacks from all CPUs
Feb 14 15:13:43 linux-ytaf kernel:         Offload RCU callbacks from CPUs: 0-7.
Feb 14 15:13:43 linux-ytaf kernel: Console: colour dummy device 80x25
Feb 14 15:13:43 linux-ytaf kernel: console [tty0] enabled
Feb 14 15:13:43 linux-ytaf kernel: clocksource hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484882848 ns
Feb 14 15:13:43 linux-ytaf kernel: hpet clockevent registered
Feb 14 15:13:43 linux-ytaf kernel: tsc: Fast TSC calibration using PIT
Feb 14 15:13:43 linux-ytaf kernel: tsc: Detected 3411.400 MHz processor
Feb 14 15:13:43 linux-ytaf kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 6822.80 BogoMIPS (lpj=13645600)
Feb 14 15:13:43 linux-ytaf kernel: pid_max: default: 32768 minimum: 301
Feb 14 15:13:43 linux-ytaf kernel: ACPI: Core revision 20150410
Feb 14 15:13:43 linux-ytaf kernel: ACPI: All ACPI Tables successfully acquired
Feb 14 15:13:43 linux-ytaf kernel: Security Framework initialized
Feb 14 15:13:43 linux-ytaf kernel: AppArmor: AppArmor initialized
Feb 14 15:13:43 linux-ytaf kernel: Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
Feb 14 15:13:43 linux-ytaf kernel: Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
Feb 14 15:13:43 linux-ytaf kernel: Mount-cache hash table entries: 16384 (order: 5, 131072 bytes)
Feb 14 15:13:43 linux-ytaf kernel: Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes)
Feb 14 15:13:43 linux-ytaf kernel: Initializing cgroup subsys blkio
Feb 14 15:13:43 linux-ytaf kernel: Initializing cgroup subsys memory
Feb 14 15:13:43 linux-ytaf kernel: Initializing cgroup subsys devices
Feb 14 15:13:43 linux-ytaf kernel: Initializing cgroup subsys freezer
Feb 14 15:13:43 linux-ytaf kernel: Initializing cgroup subsys net_cls
Feb 14 15:13:43 linux-ytaf kernel: Initializing cgroup subsys perf_event
Feb 14 15:13:43 linux-ytaf kernel: Initializing cgroup subsys net_prio
Feb 14 15:13:43 linux-ytaf kernel: Initializing cgroup subsys hugetlb
Feb 14 15:13:43 linux-ytaf kernel: CPU: Physical Processor ID: 0
Feb 14 15:13:43 linux-ytaf kernel: CPU: Processor Core ID: 0
Feb 14 15:13:43 linux-ytaf kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Feb 14 15:13:43 linux-ytaf kernel: ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Feb 14 15:13:43 linux-ytaf kernel: mce: CPU supports 9 MCE banks
Feb 14 15:13:43 linux-ytaf kernel: CPU0: Thermal monitoring enabled (TM1)
Feb 14 15:13:43 linux-ytaf kernel: process: using mwait in idle threads
Feb 14 15:13:43 linux-ytaf kernel: Last level iTLB entries: 4KB 512, 2MB 8, 4MB 8
Feb 14 15:13:43 linux-ytaf kernel: Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32, 1GB 0
Feb 14 15:13:43 linux-ytaf kernel: Freeing SMP alternatives memory: 24K (ffffffff82097000 - ffffffff8209d000)
Feb 14 15:13:43 linux-ytaf kernel: ftrace: allocating 25000 entries in 98 pages
Feb 14 15:13:43 linux-ytaf kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Feb 14 15:13:43 linux-ytaf kernel: TSC deadline timer enabled
Feb 14 15:13:43 linux-ytaf kernel: smpboot: CPU0: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz (fam: 06, model: 2a, stepping: 07)
Feb 14 15:13:43 linux-ytaf kernel: Performance Events: PEBS fmt1+, 16-deep LBR, SandyBridge events, full-width counters, Intel PMU driver.
Feb 14 15:13:43 linux-ytaf kernel: ... version:                3
Feb 14 15:13:43 linux-ytaf kernel: ... bit width:              48
Feb 14 15:13:43 linux-ytaf kernel: ... generic registers:      4
Feb 14 15:13:43 linux-ytaf kernel: ... value mask:             0000ffffffffffff
Feb 14 15:13:43 linux-ytaf kernel: ... max period:             0000ffffffffffff
Feb 14 15:13:43 linux-ytaf kernel: ... fixed-purpose events:   3
Feb 14 15:13:43 linux-ytaf kernel: ... event mask:             000000070000000f
Feb 14 15:13:43 linux-ytaf kernel: x86: Booting SMP configuration:
Feb 14 15:13:43 linux-ytaf kernel: .... node  #0, CPUs:      #1
Feb 14 15:13:43 linux-ytaf kernel: microcode: CPU1 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 15:13:43 linux-ytaf kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Feb 14 15:13:43 linux-ytaf kernel:  #2
Feb 14 15:13:43 linux-ytaf kernel: microcode: CPU2 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 15:13:43 linux-ytaf kernel:  #3
Feb 14 15:13:43 linux-ytaf kernel: microcode: CPU3 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 15:13:43 linux-ytaf kernel:  #4 #5 #6 #7
Feb 14 15:13:43 linux-ytaf kernel: x86: Booted up 1 node, 8 CPUs
Feb 14 15:13:43 linux-ytaf kernel: smpboot: Total of 8 processors activated (54582.40 BogoMIPS)
Feb 14 15:13:43 linux-ytaf kernel: devtmpfs: initialized
Feb 14 15:13:43 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xca5f2000-0xca679fff] (557056 bytes)
Feb 14 15:13:43 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xca93f000-0xcab83fff] (2379776 bytes)
Feb 14 15:13:43 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xcab92000-0xcabbefff] (184320 bytes)
Feb 14 15:13:43 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xcabc4000-0xcac06fff] (274432 bytes)
Feb 14 15:13:43 linux-ytaf kernel: clocksource jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
Feb 14 15:13:43 linux-ytaf kernel: pinctrl core: initialized pinctrl subsystem
Feb 14 15:13:43 linux-ytaf kernel: RTC time: 15:13:39, date: 02/14/16
Feb 14 15:13:43 linux-ytaf kernel: NET: Registered protocol family 16
Feb 14 15:13:43 linux-ytaf kernel: cpuidle: using governor ladder
Feb 14 15:13:43 linux-ytaf kernel: cpuidle: using governor menu
Feb 14 15:13:43 linux-ytaf kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
Feb 14 15:13:43 linux-ytaf kernel: ACPI: bus type PCI registered
Feb 14 15:13:43 linux-ytaf kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Feb 14 15:13:43 linux-ytaf kernel: PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
Feb 14 15:13:43 linux-ytaf kernel: PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
Feb 14 15:13:43 linux-ytaf kernel: PCI: Using configuration type 1 for base access
Feb 14 15:13:43 linux-ytaf kernel: perf_event_intel: PMU erratum BJ122, BV98, HSD29 worked around, HT is on
Feb 14 15:13:43 linux-ytaf kernel: ACPI: Added _OSI(Module Device)
Feb 14 15:13:43 linux-ytaf kernel: ACPI: Added _OSI(Processor Device)
Feb 14 15:13:43 linux-ytaf kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
Feb 14 15:13:43 linux-ytaf kernel: ACPI: Added _OSI(Processor Aggregator Device)
Feb 14 15:13:43 linux-ytaf kernel: ACPI: Executed 1 blocks of module-level executable AML code
Feb 14 15:13:43 linux-ytaf kernel: ACPI: Dynamic OEM Table Load:
Feb 14 15:13:43 linux-ytaf kernel: ACPI: SSDT 0xFFFF8802257C7000 00083B (v01 PmRef  Cpu0Cst  00003001 INTL 20051117)
Feb 14 15:13:43 linux-ytaf kernel: ACPI: Dynamic OEM Table Load:
Feb 14 15:13:43 linux-ytaf kernel: ACPI: SSDT 0xFFFF8802257C1400 000303 (v01 PmRef  ApIst    00003000 INTL 20051117)
Feb 14 15:13:43 linux-ytaf kernel: ACPI: Dynamic OEM Table Load:
Feb 14 15:13:43 linux-ytaf kernel: ACPI: SSDT 0xFFFF880225774600 000119 (v01 PmRef  ApCst    00003000 INTL 20051117)
Feb 14 15:13:43 linux-ytaf kernel: ACPI : EC: EC started
Feb 14 15:13:43 linux-ytaf kernel: ACPI: Interpreter enabled
Feb 14 15:13:43 linux-ytaf kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20150410/hwxface-580)
Feb 14 15:13:43 linux-ytaf kernel: ACPI: (supports S0 S1 S3 S4 S5)
Feb 14 15:13:43 linux-ytaf kernel: ACPI: Using IOAPIC for interrupt routing
Feb 14 15:13:43 linux-ytaf kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Feb 14 15:13:43 linux-ytaf kernel: ACPI: Power Resource [FN00] (off)
Feb 14 15:13:43 linux-ytaf kernel: ACPI: Power Resource [FN01] (off)
Feb 14 15:13:43 linux-ytaf kernel: ACPI: Power Resource [FN02] (off)
Feb 14 15:13:43 linux-ytaf kernel: ACPI: Power Resource [FN03] (off)
Feb 14 15:13:43 linux-ytaf kernel: ACPI: Power Resource [FN04] (off)
Feb 14 15:13:43 linux-ytaf kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
Feb 14 15:13:43 linux-ytaf kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Feb 14 15:13:43 linux-ytaf kernel: \_SB_.PCI0:_OSC invalid UUID
Feb 14 15:13:43 linux-ytaf kernel: _OSC request data:1 1f 0 
Feb 14 15:13:43 linux-ytaf kernel: acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
Feb 14 15:13:43 linux-ytaf kernel: PCI host bridge to bus 0000:00
Feb 14 15:13:43 linux-ytaf kernel: pci_bus 0000:00: root bus resource [bus 00-3e]
Feb 14 15:13:43 linux-ytaf kernel: pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
Feb 14 15:13:43 linux-ytaf kernel: pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
Feb 14 15:13:43 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
Feb 14 15:13:43 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff window]
Feb 14 15:13:43 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff window]
Feb 14 15:13:43 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff window]
Feb 14 15:13:43 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0xcfa00000-0xfeafffff window]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:00.0: [8086:0100] type 00 class 0x060000
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:01.0: [8086:0101] type 01 class 0x060400
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:01.0: System wakeup disabled by ACPI
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:01.1: [8086:0105] type 01 class 0x060400
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:01.1: PME# supported from D0 D3hot D3cold
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:01.1: System wakeup disabled by ACPI
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:02.0: [8086:0122] type 00 class 0x038000
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:02.0: reg 0x10: [mem 0xf7400000-0xf77fffff 64bit]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:02.0: reg 0x18: [mem 0xd0000000-0xdfffffff 64bit pref]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:02.0: reg 0x20: [io  0xf000-0xf03f]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:16.0: [8086:1c3a] type 00 class 0x078000
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:16.0: reg 0x10: [mem 0xf7b2c000-0xf7b2c00f 64bit]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:19.0: [8086:1503] type 00 class 0x020000
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:19.0: reg 0x10: [mem 0xf7b00000-0xf7b1ffff]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:19.0: reg 0x14: [mem 0xf7b29000-0xf7b29fff]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:19.0: reg 0x18: [io  0xf080-0xf09f]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:19.0: PME# supported from D0 D3hot D3cold
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:19.0: System wakeup disabled by ACPI
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1a.0: [8086:1c2d] type 00 class 0x0c0320
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1a.0: reg 0x10: [mem 0xf7b28000-0xf7b283ff]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1a.0: System wakeup disabled by ACPI
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1b.0: [8086:1c20] type 00 class 0x040300
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1b.0: reg 0x10: [mem 0xf7b20000-0xf7b23fff 64bit]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1b.0: System wakeup disabled by ACPI
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.0: [8086:1c10] type 01 class 0x060400
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.0: System wakeup disabled by ACPI
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.4: [8086:1c18] type 01 class 0x060400
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.4: System wakeup disabled by ACPI
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.5: [8086:1c1a] type 01 class 0x060400
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.5: System wakeup disabled by ACPI
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.6: [8086:1c1c] type 01 class 0x060400
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.6: PME# supported from D0 D3hot D3cold
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.6: System wakeup disabled by ACPI
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1d.0: [8086:1c26] type 00 class 0x0c0320
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1d.0: reg 0x10: [mem 0xf7b27000-0xf7b273ff]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1d.0: System wakeup disabled by ACPI
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1f.0: [8086:1c44] type 00 class 0x060100
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1f.2: [8086:1c02] type 00 class 0x010601
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x10: [io  0xf0d0-0xf0d7]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x14: [io  0xf0c0-0xf0c3]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x18: [io  0xf0b0-0xf0b7]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x1c: [io  0xf0a0-0xf0a3]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x20: [io  0xf060-0xf07f]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x24: [mem 0xf7b26000-0xf7b267ff]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1f.2: PME# supported from D3hot
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1f.3: [8086:1c22] type 00 class 0x0c0500
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1f.3: reg 0x10: [mem 0xf7b25000-0xf7b250ff 64bit]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1f.3: reg 0x20: [io  0x0580-0x059f]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:02:00.0: [10de:1183] type 00 class 0x030000
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:02:00.0: reg 0x10: [mem 0xf6000000-0xf6ffffff]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:02:00.0: reg 0x14: [mem 0xe0000000-0xe7ffffff 64bit pref]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:02:00.0: reg 0x1c: [mem 0xe8000000-0xe9ffffff 64bit pref]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:02:00.0: reg 0x24: [io  0xe000-0xe07f]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:02:00.0: reg 0x30: [mem 0xf7000000-0xf707ffff pref]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:02:00.1: [10de:0e0a] type 00 class 0x040300
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:02:00.1: reg 0x10: [mem 0xf7080000-0xf7083fff]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:01.1: PCI bridge to [bus 02]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [io  0xe000-0xefff]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xf6000000-0xf70fffff]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xe0000000-0xe9ffffff 64bit pref]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.0: PCI bridge to [bus 03]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:04:00.0: [1b21:1042] type 00 class 0x0c0330
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:04:00.0: reg 0x10: [mem 0xf7a00000-0xf7a07fff 64bit]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:04:00.0: PME# supported from D3hot D3cold
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:04:00.0: System wakeup disabled by ACPI
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.4: PCI bridge to [bus 04]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.4:   bridge window [mem 0xf7a00000-0xf7afffff]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:05:00.0: [1b21:1042] type 00 class 0x0c0330
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:05:00.0: reg 0x10: [mem 0xf7900000-0xf7907fff 64bit]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:05:00.0: PME# supported from D3hot D3cold
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:05:00.0: System wakeup disabled by ACPI
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.5: PCI bridge to [bus 05]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.5:   bridge window [mem 0xf7900000-0xf79fffff]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:06:00.0: [197b:2362] type 00 class 0x010185
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:06:00.0: reg 0x10: [io  0xd040-0xd047]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:06:00.0: reg 0x14: [io  0xd030-0xd033]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:06:00.0: reg 0x18: [io  0xd020-0xd027]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:06:00.0: reg 0x1c: [io  0xd010-0xd013]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:06:00.0: reg 0x20: [io  0xd000-0xd00f]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:06:00.0: reg 0x24: [mem 0xf7810000-0xf78101ff]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:06:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:06:00.0: PME# supported from D3hot
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:06:00.0: System wakeup disabled by ACPI
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.6: PCI bridge to [bus 06]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [io  0xd000-0xdfff]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [mem 0xf7800000-0xf78fffff]
Feb 14 15:13:43 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15)
Feb 14 15:13:43 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *10 11 12 14 15)
Feb 14 15:13:43 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Feb 14 15:13:43 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs *3 4 5 6 10 11 12 14 15)
Feb 14 15:13:43 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 *4 5 6 10 11 12 14 15)
Feb 14 15:13:43 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
Feb 14 15:13:43 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 *11 12 14 15)
Feb 14 15:13:43 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 *10 11 12 14 15)
Feb 14 15:13:43 linux-ytaf kernel: ACPI: Enabled 6 GPEs in block 00 to 3F
Feb 14 15:13:43 linux-ytaf kernel: ACPI : EC: GPE = 0x18, I/O: command/status = 0x66, data = 0x62
Feb 14 15:13:43 linux-ytaf kernel: vgaarb: setting as boot device: PCI:0000:02:00.0
Feb 14 15:13:43 linux-ytaf kernel: vgaarb: device added: PCI:0000:02:00.0,decodes=io+mem,owns=io+mem,locks=none
Feb 14 15:13:43 linux-ytaf kernel: vgaarb: loaded
Feb 14 15:13:43 linux-ytaf kernel: vgaarb: bridge control possible 0000:02:00.0
Feb 14 15:13:43 linux-ytaf kernel: SCSI subsystem initialized
Feb 14 15:13:43 linux-ytaf kernel: libata version 3.00 loaded.
Feb 14 15:13:43 linux-ytaf kernel: PCI: Using ACPI for IRQ routing
Feb 14 15:13:43 linux-ytaf kernel: PCI: pci_cache_line_size set to 64 bytes
Feb 14 15:13:43 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0009f000-0x0009ffff]
Feb 14 15:13:43 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c826018-0x0fffffff]
Feb 14 15:13:43 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c836018-0x0fffffff]
Feb 14 15:13:43 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c847018-0x0fffffff]
Feb 14 15:13:43 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c857018-0x0fffffff]
Feb 14 15:13:43 linux-ytaf kernel: e820: reserve RAM buffer [mem 0xca38f000-0xcbffffff]
Feb 14 15:13:43 linux-ytaf kernel: e820: reserve RAM buffer [mem 0xcb000000-0xcbffffff]
Feb 14 15:13:43 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x22f600000-0x22fffffff]
Feb 14 15:13:43 linux-ytaf kernel: NetLabel: Initializing
Feb 14 15:13:43 linux-ytaf kernel: NetLabel:  domain hash size = 128
Feb 14 15:13:43 linux-ytaf kernel: NetLabel:  protocols = UNLABELED CIPSOv4
Feb 14 15:13:43 linux-ytaf kernel: NetLabel:  unlabeled traffic allowed by default
Feb 14 15:13:43 linux-ytaf kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Feb 14 15:13:43 linux-ytaf kernel: hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Feb 14 15:13:43 linux-ytaf kernel: Switched to clocksource hpet
Feb 14 15:13:43 linux-ytaf kernel: AppArmor: AppArmor Filesystem Enabled
Feb 14 15:13:43 linux-ytaf kernel: pnp: PnP ACPI init
Feb 14 15:13:43 linux-ytaf kernel: system 00:00: [mem 0xfed40000-0xfed44fff] has been reserved
Feb 14 15:13:43 linux-ytaf kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
Feb 14 15:13:43 linux-ytaf kernel: system 00:01: [io  0x0680-0x069f] has been reserved
Feb 14 15:13:43 linux-ytaf kernel: system 00:01: [io  0x0200-0x020f] has been reserved
Feb 14 15:13:43 linux-ytaf kernel: system 00:01: [io  0xffff] has been reserved
Feb 14 15:13:43 linux-ytaf kernel: system 00:01: [io  0xffff] has been reserved
Feb 14 15:13:43 linux-ytaf kernel: system 00:01: [io  0x0400-0x0453] could not be reserved
Feb 14 15:13:43 linux-ytaf kernel: system 00:01: [io  0x0458-0x047f] has been reserved
Feb 14 15:13:43 linux-ytaf kernel: system 00:01: [io  0x0500-0x057f] has been reserved
Feb 14 15:13:43 linux-ytaf kernel: system 00:01: [io  0x164e-0x164f] has been reserved
Feb 14 15:13:43 linux-ytaf kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 15:13:43 linux-ytaf kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Feb 14 15:13:43 linux-ytaf kernel: system 00:03: [io  0x0454-0x0457] has been reserved
Feb 14 15:13:43 linux-ytaf kernel: system 00:03: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
Feb 14 15:13:43 linux-ytaf kernel: system 00:04: [io  0x0290-0x029f] has been reserved
Feb 14 15:13:43 linux-ytaf kernel: system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 15:13:43 linux-ytaf kernel: system 00:05: [io  0x04d0-0x04d1] has been reserved
Feb 14 15:13:43 linux-ytaf kernel: system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 15:13:43 linux-ytaf kernel: system 00:06: [mem 0xfed1c000-0xfed1ffff] has been reserved
Feb 14 15:13:43 linux-ytaf kernel: system 00:06: [mem 0xfed10000-0xfed17fff] has been reserved
Feb 14 15:13:43 linux-ytaf kernel: system 00:06: [mem 0xfed18000-0xfed18fff] has been reserved
Feb 14 15:13:43 linux-ytaf kernel: system 00:06: [mem 0xfed19000-0xfed19fff] has been reserved
Feb 14 15:13:43 linux-ytaf kernel: system 00:06: [mem 0xf8000000-0xfbffffff] has been reserved
Feb 14 15:13:43 linux-ytaf kernel: system 00:06: [mem 0xfed20000-0xfed3ffff] has been reserved
Feb 14 15:13:43 linux-ytaf kernel: system 00:06: [mem 0xfed90000-0xfed93fff] has been reserved
Feb 14 15:13:43 linux-ytaf kernel: system 00:06: [mem 0xfed45000-0xfed8ffff] has been reserved
Feb 14 15:13:43 linux-ytaf kernel: system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Feb 14 15:13:43 linux-ytaf kernel: system 00:06: [mem 0xfee00000-0xfeefffff] could not be reserved
Feb 14 15:13:43 linux-ytaf kernel: system 00:06: [mem 0xcfa00000-0xcfa00fff] has been reserved
Feb 14 15:13:43 linux-ytaf kernel: system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 15:13:43 linux-ytaf kernel: system 00:07: [mem 0x20000000-0x201fffff] has been reserved
Feb 14 15:13:43 linux-ytaf kernel: system 00:07: [mem 0x40000000-0x401fffff] has been reserved
Feb 14 15:13:43 linux-ytaf kernel: system 00:07: Plug and Play ACPI device, IDs PNP0c01 (active)
Feb 14 15:13:43 linux-ytaf kernel: pnp: PnP ACPI: found 8 devices
Feb 14 15:13:43 linux-ytaf kernel: clocksource acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.0: bridge window [io  0x1000-0x0fff] to [bus 03] add_size 1000
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 03] add_size 200000 add_align 100000
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff] to [bus 03] add_size 200000 add_align 100000
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.0: res[14]=[mem 0x00100000-0x000fffff] res_to_dev_res add_size 200000 min_align 100000
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.0: res[14]=[mem 0x00100000-0x002fffff] res_to_dev_res add_size 200000 min_align 100000
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x000fffff 64bit pref] res_to_dev_res add_size 200000 min_align 100000
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x002fffff 64bit pref] res_to_dev_res add_size 200000 min_align 100000
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.0: res[13]=[io  0x1000-0x0fff] res_to_dev_res add_size 1000 min_align 1000
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.0: res[13]=[io  0x1000-0x1fff] res_to_dev_res add_size 1000 min_align 1000
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.0: BAR 14: assigned [mem 0xcfb00000-0xcfcfffff]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.0: BAR 15: assigned [mem 0xcfd00000-0xcfefffff 64bit pref]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.0: BAR 13: assigned [io  0x2000-0x2fff]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:01.1: PCI bridge to [bus 02]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [io  0xe000-0xefff]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xf6000000-0xf70fffff]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xe0000000-0xe9ffffff 64bit pref]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.0: PCI bridge to [bus 03]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.0:   bridge window [io  0x2000-0x2fff]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.0:   bridge window [mem 0xcfb00000-0xcfcfffff]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.0:   bridge window [mem 0xcfd00000-0xcfefffff 64bit pref]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.4: PCI bridge to [bus 04]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.4:   bridge window [mem 0xf7a00000-0xf7afffff]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.5: PCI bridge to [bus 05]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.5:   bridge window [mem 0xf7900000-0xf79fffff]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:06:00.0: BAR 6: assigned [mem 0xf7800000-0xf780ffff pref]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.6: PCI bridge to [bus 06]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [io  0xd000-0xdfff]
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [mem 0xf7800000-0xf78fffff]
Feb 14 15:13:43 linux-ytaf kernel: pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
Feb 14 15:13:43 linux-ytaf kernel: pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
Feb 14 15:13:43 linux-ytaf kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
Feb 14 15:13:43 linux-ytaf kernel: pci_bus 0000:00: resource 7 [mem 0x000d4000-0x000d7fff window]
Feb 14 15:13:43 linux-ytaf kernel: pci_bus 0000:00: resource 8 [mem 0x000d8000-0x000dbfff window]
Feb 14 15:13:43 linux-ytaf kernel: pci_bus 0000:00: resource 9 [mem 0x000dc000-0x000dffff window]
Feb 14 15:13:43 linux-ytaf kernel: pci_bus 0000:00: resource 10 [mem 0xcfa00000-0xfeafffff window]
Feb 14 15:13:43 linux-ytaf kernel: pci_bus 0000:02: resource 0 [io  0xe000-0xefff]
Feb 14 15:13:43 linux-ytaf kernel: pci_bus 0000:02: resource 1 [mem 0xf6000000-0xf70fffff]
Feb 14 15:13:43 linux-ytaf kernel: pci_bus 0000:02: resource 2 [mem 0xe0000000-0xe9ffffff 64bit pref]
Feb 14 15:13:43 linux-ytaf kernel: pci_bus 0000:03: resource 0 [io  0x2000-0x2fff]
Feb 14 15:13:43 linux-ytaf kernel: pci_bus 0000:03: resource 1 [mem 0xcfb00000-0xcfcfffff]
Feb 14 15:13:43 linux-ytaf kernel: pci_bus 0000:03: resource 2 [mem 0xcfd00000-0xcfefffff 64bit pref]
Feb 14 15:13:43 linux-ytaf kernel: pci_bus 0000:04: resource 1 [mem 0xf7a00000-0xf7afffff]
Feb 14 15:13:43 linux-ytaf kernel: pci_bus 0000:05: resource 1 [mem 0xf7900000-0xf79fffff]
Feb 14 15:13:43 linux-ytaf kernel: pci_bus 0000:06: resource 0 [io  0xd000-0xdfff]
Feb 14 15:13:43 linux-ytaf kernel: pci_bus 0000:06: resource 1 [mem 0xf7800000-0xf78fffff]
Feb 14 15:13:43 linux-ytaf kernel: NET: Registered protocol family 2
Feb 14 15:13:43 linux-ytaf kernel: TCP established hash table entries: 65536 (order: 7, 524288 bytes)
Feb 14 15:13:43 linux-ytaf kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Feb 14 15:13:43 linux-ytaf kernel: TCP: Hash tables configured (established 65536 bind 65536)
Feb 14 15:13:43 linux-ytaf kernel: UDP hash table entries: 4096 (order: 5, 131072 bytes)
Feb 14 15:13:43 linux-ytaf kernel: UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
Feb 14 15:13:43 linux-ytaf kernel: NET: Registered protocol family 1
Feb 14 15:13:43 linux-ytaf kernel: pci 0000:02:00.0: Video device with shadowed ROM
Feb 14 15:13:43 linux-ytaf kernel: PCI: CLS 64 bytes, default 64
Feb 14 15:13:43 linux-ytaf kernel: Unpacking initramfs...
Feb 14 15:13:43 linux-ytaf kernel: Freeing initrd memory: 11920K (ffff880000457000 - ffff880000ffb000)
Feb 14 15:13:43 linux-ytaf kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Feb 14 15:13:43 linux-ytaf kernel: software IO TLB [mem 0xc638f000-0xca38f000] (64MB) mapped at [ffff8800c638f000-ffff8800ca38efff]
Feb 14 15:13:43 linux-ytaf kernel: RAPL PMU detected, API unit is 2^-32 Joules, 3 fixed counters 163840 ms ovfl timer
Feb 14 15:13:43 linux-ytaf kernel: hw unit of domain pp0-core 2^-16 Joules
Feb 14 15:13:43 linux-ytaf kernel: hw unit of domain package 2^-16 Joules
Feb 14 15:13:43 linux-ytaf kernel: hw unit of domain pp1-gpu 2^-16 Joules
Feb 14 15:13:43 linux-ytaf kernel: microcode: CPU0 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 15:13:43 linux-ytaf kernel: microcode: CPU1 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 15:13:43 linux-ytaf kernel: microcode: CPU2 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 15:13:43 linux-ytaf kernel: microcode: CPU3 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 15:13:43 linux-ytaf kernel: microcode: CPU4 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 15:13:43 linux-ytaf kernel: microcode: CPU5 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 15:13:43 linux-ytaf kernel: microcode: CPU6 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 15:13:43 linux-ytaf kernel: microcode: CPU7 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 15:13:43 linux-ytaf kernel: microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Feb 14 15:13:43 linux-ytaf kernel: Scanning for low memory corruption every 60 seconds
Feb 14 15:13:43 linux-ytaf kernel: futex hash table entries: 2048 (order: 5, 131072 bytes)
Feb 14 15:13:43 linux-ytaf kernel: audit: initializing netlink subsys (disabled)
Feb 14 15:13:43 linux-ytaf kernel: audit: type=2000 audit(1455462820.280:1): initialized
Feb 14 15:13:43 linux-ytaf kernel: HugeTLB registered 2 MB page size, pre-allocated 0 pages
Feb 14 15:13:43 linux-ytaf kernel: zpool: loaded
Feb 14 15:13:43 linux-ytaf kernel: zbud: loaded
Feb 14 15:13:43 linux-ytaf kernel: VFS: Disk quotas dquot_6.6.0
Feb 14 15:13:43 linux-ytaf kernel: VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Feb 14 15:13:43 linux-ytaf kernel: Key type big_key registered
Feb 14 15:13:43 linux-ytaf kernel: Key type asymmetric registered
Feb 14 15:13:43 linux-ytaf kernel: Asymmetric key parser 'x509' registered
Feb 14 15:13:43 linux-ytaf kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Feb 14 15:13:43 linux-ytaf kernel: io scheduler noop registered
Feb 14 15:13:43 linux-ytaf kernel: io scheduler deadline registered
Feb 14 15:13:43 linux-ytaf kernel: io scheduler cfq registered (default)
Feb 14 15:13:43 linux-ytaf kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Feb 14 15:13:43 linux-ytaf kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Feb 14 15:13:43 linux-ytaf kernel: efifb: probing for efifb
Feb 14 15:13:43 linux-ytaf kernel: efifb: framebuffer at 0xe9000000, mapped to 0xffffc90001000000, using 1876k, total 1875k
Feb 14 15:13:43 linux-ytaf kernel: efifb: mode is 800x600x32, linelength=3200, pages=1
Feb 14 15:13:43 linux-ytaf kernel: efifb: scrolling: redraw
Feb 14 15:13:43 linux-ytaf kernel: efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Feb 14 15:13:43 linux-ytaf kernel: Console: switching to colour frame buffer device 100x37
Feb 14 15:13:43 linux-ytaf kernel: fb0: EFI VGA frame buffer device
Feb 14 15:13:43 linux-ytaf kernel: intel_idle: MWAIT substates: 0x1120
Feb 14 15:13:43 linux-ytaf kernel: intel_idle: v0.4 model 0x2A
Feb 14 15:13:43 linux-ytaf kernel: intel_idle: lapic_timer_reliable_states 0xffffffff
Feb 14 15:13:43 linux-ytaf kernel: GHES: HEST is not enabled!
Feb 14 15:13:43 linux-ytaf kernel: Serial: 8250/16550 driver, 32 ports, IRQ sharing disabled
Feb 14 15:13:43 linux-ytaf kernel: Non-volatile memory driver v1.3
Feb 14 15:13:43 linux-ytaf kernel: Linux agpgart interface v0.103
Feb 14 15:13:43 linux-ytaf kernel: ahci 0000:00:1f.2: version 3.0
Feb 14 15:13:43 linux-ytaf kernel: ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x7 impl SATA mode
Feb 14 15:13:43 linux-ytaf kernel: ahci 0000:00:1f.2: flags: 64bit ncq led clo pio slum part ems apst 
Feb 14 15:13:43 linux-ytaf kernel: scsi host0: ahci
Feb 14 15:13:43 linux-ytaf kernel: scsi host1: ahci
Feb 14 15:13:43 linux-ytaf kernel: scsi host2: ahci
Feb 14 15:13:43 linux-ytaf kernel: scsi host3: ahci
Feb 14 15:13:43 linux-ytaf kernel: scsi host4: ahci
Feb 14 15:13:43 linux-ytaf kernel: scsi host5: ahci
Feb 14 15:13:43 linux-ytaf kernel: ata1: SATA max UDMA/133 abar m2048@0xf7b26000 port 0xf7b26100 irq 26
Feb 14 15:13:43 linux-ytaf kernel: ata2: SATA max UDMA/133 abar m2048@0xf7b26000 port 0xf7b26180 irq 26
Feb 14 15:13:43 linux-ytaf kernel: ata3: SATA max UDMA/133 abar m2048@0xf7b26000 port 0xf7b26200 irq 26
Feb 14 15:13:43 linux-ytaf kernel: ata4: DUMMY
Feb 14 15:13:43 linux-ytaf kernel: ata5: DUMMY
Feb 14 15:13:43 linux-ytaf kernel: ata6: DUMMY
Feb 14 15:13:43 linux-ytaf kernel: ahci 0000:06:00.0: AHCI 0001.0100 32 slots 2 ports 3 Gbps 0x3 impl SATA mode
Feb 14 15:13:43 linux-ytaf kernel: ahci 0000:06:00.0: flags: 64bit ncq pm led clo pmp pio slum part 
Feb 14 15:13:43 linux-ytaf kernel: scsi host6: ahci
Feb 14 15:13:43 linux-ytaf kernel: scsi host7: ahci
Feb 14 15:13:43 linux-ytaf kernel: ata7: SATA max UDMA/133 abar m512@0xf7810000 port 0xf7810100 irq 18
Feb 14 15:13:43 linux-ytaf kernel: ata8: SATA max UDMA/133 abar m512@0xf7810000 port 0xf7810180 irq 18
Feb 14 15:13:43 linux-ytaf kernel: i8042: PNP: No PS/2 controller found. Probing ports directly.
Feb 14 15:13:43 linux-ytaf kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Feb 14 15:13:43 linux-ytaf kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Feb 14 15:13:43 linux-ytaf kernel: mousedev: PS/2 mouse device common for all mice
Feb 14 15:13:43 linux-ytaf kernel: rtc_cmos 00:02: RTC can wake from S4
Feb 14 15:13:43 linux-ytaf kernel: rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Feb 14 15:13:43 linux-ytaf kernel: rtc_cmos 00:02: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
Feb 14 15:13:43 linux-ytaf kernel: Intel P-state driver initializing.
Feb 14 15:13:43 linux-ytaf kernel: ledtrig-cpu: registered to indicate activity on CPUs
Feb 14 15:13:43 linux-ytaf kernel: EFI Variables Facility v0.08 2004-May-17
Feb 14 15:13:43 linux-ytaf kernel: hidraw: raw HID events driver (C) Jiri Kosina
Feb 14 15:13:43 linux-ytaf kernel: NET: Registered protocol family 10
Feb 14 15:13:43 linux-ytaf kernel: registered taskstats version 1
Feb 14 15:13:43 linux-ytaf kernel: Key type encrypted registered
Feb 14 15:13:43 linux-ytaf kernel: AppArmor: AppArmor sha1 policy hashing enabled
Feb 14 15:13:43 linux-ytaf kernel:   Magic number: 4:784:234
Feb 14 15:13:43 linux-ytaf kernel: acpi device:4e: hash matches
Feb 14 15:13:43 linux-ytaf kernel: rtc_cmos 00:02: setting system clock to 2016-02-14 15:13:41 UTC (1455462821)
Feb 14 15:13:43 linux-ytaf kernel: PM: Checking hibernation image partition /dev/sdb2
Feb 14 15:13:43 linux-ytaf kernel: ata7: SATA link down (SStatus 0 SControl 300)
Feb 14 15:13:43 linux-ytaf kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 14 15:13:43 linux-ytaf kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 14 15:13:43 linux-ytaf kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Feb 14 15:13:43 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 15:13:43 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff8802268b7e50), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 15:13:43 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 15:13:43 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff8802268b7dd8), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 15:13:43 linux-ytaf kernel: ata1.00: ATA-9: SAMSUNG SSD 830 Series, CXM03B1Q, max UDMA/133
Feb 14 15:13:43 linux-ytaf kernel: ata1.00: 500118192 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Feb 14 15:13:43 linux-ytaf kernel: ata2.00: ATA-8: TOSHIBA HDWD110, MS2OA8J0, max UDMA/133
Feb 14 15:13:43 linux-ytaf kernel: ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Feb 14 15:13:43 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 15:13:43 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff8802268b7e50), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 15:13:43 linux-ytaf kernel: ata1.00: configured for UDMA/133
Feb 14 15:13:43 linux-ytaf kernel: scsi 0:0:0:0: Direct-Access     ATA      SAMSUNG SSD 830  3B1Q PQ: 0 ANSI: 5
Feb 14 15:13:43 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 15:13:43 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff8802268b7dd8), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 15:13:43 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 15:13:43 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff8802268b7d60), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 15:13:43 linux-ytaf kernel: ata3.00: ATAPI: TSSTcorp CDDVDW SH-S223C, SB05, max MWDMA2
Feb 14 15:13:43 linux-ytaf kernel: ata3.00: applying bridge limits
Feb 14 15:13:43 linux-ytaf kernel: sd 0:0:0:0: [sda] 500118192 512-byte logical blocks: (256 GB/238 GiB)
Feb 14 15:13:43 linux-ytaf kernel: sd 0:0:0:0: [sda] Write Protect is off
Feb 14 15:13:43 linux-ytaf kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 14 15:13:43 linux-ytaf kernel: ata2.00: configured for UDMA/133
Feb 14 15:13:43 linux-ytaf kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 14 15:13:43 linux-ytaf kernel: scsi 1:0:0:0: Direct-Access     ATA      TOSHIBA HDWD110  A8J0 PQ: 0 ANSI: 5
Feb 14 15:13:43 linux-ytaf kernel: sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
Feb 14 15:13:43 linux-ytaf kernel: sd 1:0:0:0: [sdb] 4096-byte physical blocks
Feb 14 15:13:43 linux-ytaf kernel: sd 1:0:0:0: [sdb] Write Protect is off
Feb 14 15:13:43 linux-ytaf kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Feb 14 15:13:43 linux-ytaf kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 14 15:13:43 linux-ytaf kernel:  sda: sda1 sda2 sda3 sda4
Feb 14 15:13:43 linux-ytaf kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Feb 14 15:13:43 linux-ytaf kernel: ata8: SATA link down (SStatus 0 SControl 300)
Feb 14 15:13:43 linux-ytaf kernel:  sdb: sdb1 sdb2 sdb3 sdb4
Feb 14 15:13:43 linux-ytaf kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
Feb 14 15:13:43 linux-ytaf kernel: tsc: Refined TSC clocksource calibration: 3411.128 MHz
Feb 14 15:13:43 linux-ytaf kernel: clocksource tsc: mask: 0xffffffffffffffff max_cycles: 0x312b5ecadef, max_idle_ns: 440795307361 ns
Feb 14 15:13:43 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 15:13:43 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff8802268b7d60), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 15:13:43 linux-ytaf kernel: ata3.00: configured for PIO4
Feb 14 15:13:43 linux-ytaf kernel: scsi 2:0:0:0: CD-ROM            TSSTcorp CDDVDW SH-S223C  SB05 PQ: 0 ANSI: 5
Feb 14 15:13:43 linux-ytaf kernel: PM: Hibernation image partition 8:18 present
Feb 14 15:13:43 linux-ytaf kernel: PM: Looking for hibernation image.
Feb 14 15:13:43 linux-ytaf kernel: Switched to clocksource tsc
Feb 14 15:13:43 linux-ytaf kernel: PM: Image not found (code -22)
Feb 14 15:13:43 linux-ytaf kernel: PM: Hibernation image not present or could not be loaded.
Feb 14 15:13:43 linux-ytaf kernel: Freeing unused kernel memory: 1560K (ffffffff81f11000 - ffffffff82097000)
Feb 14 15:13:43 linux-ytaf kernel: Write protecting the kernel read-only data: 14336k
Feb 14 15:13:43 linux-ytaf kernel: Freeing unused kernel memory: 1632K (ffff88000d668000 - ffff88000d800000)
Feb 14 15:13:43 linux-ytaf kernel: Freeing unused kernel memory: 1296K (ffff88000dcbc000 - ffff88000de00000)
Feb 14 15:13:43 linux-ytaf systemd[1]: RTC configured in localtime, applying delta of 60 minutes to system time.
Feb 14 15:13:43 linux-ytaf kernel: random: systemd urandom read with 22 bits of entropy available
Feb 14 15:13:43 linux-ytaf kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Feb 14 15:13:43 linux-ytaf kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0
Feb 14 15:13:43 linux-ytaf kernel: scsi 2:0:0:0: Attached scsi generic sg2 type 5
Feb 14 15:13:43 linux-ytaf systemd-journal[187]: Journal started
Feb 14 15:13:43 linux-ytaf dracut-cmdline[181]: dracut-42.1 dracut-037-68.1
Feb 14 15:13:43 linux-ytaf systemd-udevd[250]: Network interface NamePolicy= disabled on kernel commandline, ignoring.
Feb 14 15:13:43 linux-ytaf kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3
Feb 14 15:13:43 linux-ytaf kernel: ACPI: Power Button [PWRB]
Feb 14 15:13:43 linux-ytaf kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
Feb 14 15:13:43 linux-ytaf kernel: ACPI: Power Button [PWRF]
Feb 14 15:13:43 linux-ytaf kernel: ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
Feb 14 15:13:43 linux-ytaf kernel: acpi device:58: registered as cooling_device0
Feb 14 15:13:43 linux-ytaf kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5
Feb 14 15:13:43 linux-ytaf kernel: wmi: Mapper loaded
Feb 14 15:13:43 linux-ytaf kernel: ACPI: bus type USB registered
Feb 14 15:13:43 linux-ytaf kernel: usbcore: registered new interface driver usbfs
Feb 14 15:13:43 linux-ytaf kernel: usbcore: registered new interface driver hub
Feb 14 15:13:43 linux-ytaf kernel: usbcore: registered new device driver usb
Feb 14 15:13:43 linux-ytaf kernel: [drm] Initialized drm 1.1.0 20060810
Feb 14 15:13:43 linux-ytaf kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Feb 14 15:13:43 linux-ytaf kernel: ehci-pci: EHCI PCI platform driver
Feb 14 15:13:43 linux-ytaf kernel: ehci-pci 0000:00:1a.0: EHCI Host Controller
Feb 14 15:13:43 linux-ytaf kernel: ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Feb 14 15:13:43 linux-ytaf kernel: ehci-pci 0000:00:1a.0: debug port 2
Feb 14 15:13:43 linux-ytaf kernel: ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Feb 14 15:13:43 linux-ytaf kernel: ehci-pci 0000:00:1a.0: irq 16, io mem 0xf7b28000
Feb 14 15:13:43 linux-ytaf kernel: MXM: GUID detected in BIOS
Feb 14 15:13:43 linux-ytaf kernel: checking generic (e9000000 1d5000) vs hw (e0000000 8000000)
Feb 14 15:13:43 linux-ytaf kernel: checking generic (e9000000 1d5000) vs hw (e8000000 2000000)
Feb 14 15:13:43 linux-ytaf kernel: fb: switching to nouveaufb from EFI VGA
Feb 14 15:13:43 linux-ytaf kernel: Console: switching to colour dummy device 80x25
Feb 14 15:13:43 linux-ytaf kernel: nouveau  [  DEVICE][0000:02:00.0] BOOT0  : 0x0e4030a2
Feb 14 15:13:43 linux-ytaf kernel: nouveau  [  DEVICE][0000:02:00.0] Chipset: GK104 (NVE4)
Feb 14 15:13:43 linux-ytaf kernel: nouveau  [  DEVICE][0000:02:00.0] Family : NVE0
Feb 14 15:13:43 linux-ytaf kernel: sr 2:0:0:0: [sr0] scsi3-mmc drive: 52x/52x writer dvd-ram cd/rw xa/form2 cdda tray
Feb 14 15:13:43 linux-ytaf kernel: cdrom: Uniform CD-ROM driver Revision: 3.20
Feb 14 15:13:43 linux-ytaf kernel: sr 2:0:0:0: Attached scsi CD-ROM sr0
Feb 14 15:13:43 linux-ytaf kernel: ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Feb 14 15:13:43 linux-ytaf kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 15:13:43 linux-ytaf kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 15:13:43 linux-ytaf kernel: usb usb1: Product: EHCI Host Controller
Feb 14 15:13:43 linux-ytaf kernel: usb usb1: Manufacturer: Linux 4.1.15-8-default ehci_hcd
Feb 14 15:13:43 linux-ytaf kernel: usb usb1: SerialNumber: 0000:00:1a.0
Feb 14 15:13:43 linux-ytaf kernel: hub 1-0:1.0: USB hub found
Feb 14 15:13:43 linux-ytaf kernel: hub 1-0:1.0: 2 ports detected
Feb 14 15:13:43 linux-ytaf kernel: xhci_hcd 0000:04:00.0: xHCI Host Controller
Feb 14 15:13:43 linux-ytaf kernel: xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 2
Feb 14 15:13:43 linux-ytaf kernel: xhci_hcd 0000:04:00.0: hcc params 0x0200f180 hci version 0x96 quirks 0x00080000
Feb 14 15:13:43 linux-ytaf kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 15:13:43 linux-ytaf kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 15:13:43 linux-ytaf kernel: usb usb2: Product: xHCI Host Controller
Feb 14 15:13:43 linux-ytaf kernel: usb usb2: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 15:13:43 linux-ytaf kernel: usb usb2: SerialNumber: 0000:04:00.0
Feb 14 15:13:43 linux-ytaf kernel: hub 2-0:1.0: USB hub found
Feb 14 15:13:43 linux-ytaf kernel: hub 2-0:1.0: 2 ports detected
Feb 14 15:13:43 linux-ytaf kernel: xhci_hcd 0000:04:00.0: xHCI Host Controller
Feb 14 15:13:43 linux-ytaf kernel: xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 3
Feb 14 15:13:43 linux-ytaf kernel: ehci-pci 0000:00:1d.0: EHCI Host Controller
Feb 14 15:13:43 linux-ytaf kernel: usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
Feb 14 15:13:43 linux-ytaf kernel: usb usb3: New USB device found, idVendor=1d6b, idProduct=0003
Feb 14 15:13:43 linux-ytaf kernel: usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 15:13:43 linux-ytaf kernel: usb usb3: Product: xHCI Host Controller
Feb 14 15:13:43 linux-ytaf kernel: usb usb3: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 15:13:43 linux-ytaf kernel: usb usb3: SerialNumber: 0000:04:00.0
Feb 14 15:13:43 linux-ytaf kernel: hub 3-0:1.0: USB hub found
Feb 14 15:13:43 linux-ytaf kernel: hub 3-0:1.0: 2 ports detected
Feb 14 15:13:43 linux-ytaf kernel: ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 4
Feb 14 15:13:43 linux-ytaf kernel: ehci-pci 0000:00:1d.0: debug port 2
Feb 14 15:13:43 linux-ytaf kernel: ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Feb 14 15:13:43 linux-ytaf kernel: ehci-pci 0000:00:1d.0: irq 23, io mem 0xf7b27000
Feb 14 15:13:43 linux-ytaf kernel: ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Feb 14 15:13:43 linux-ytaf kernel: usb usb4: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 15:13:43 linux-ytaf kernel: usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 15:13:43 linux-ytaf kernel: usb usb4: Product: EHCI Host Controller
Feb 14 15:13:43 linux-ytaf kernel: usb usb4: Manufacturer: Linux 4.1.15-8-default ehci_hcd
Feb 14 15:13:43 linux-ytaf kernel: usb usb4: SerialNumber: 0000:00:1d.0
Feb 14 15:13:43 linux-ytaf kernel: hub 4-0:1.0: USB hub found
Feb 14 15:13:43 linux-ytaf kernel: hub 4-0:1.0: 2 ports detected
Feb 14 15:13:43 linux-ytaf kernel: xhci_hcd 0000:05:00.0: xHCI Host Controller
Feb 14 15:13:43 linux-ytaf kernel: xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 5
Feb 14 15:13:43 linux-ytaf kernel: i915 0000:00:02.0: enabling device (0006 -> 0007)
Feb 14 15:13:43 linux-ytaf kernel: nouveau  [   VBIOS][0000:02:00.0] using image from PROM
Feb 14 15:13:43 linux-ytaf kernel: nouveau  [   VBIOS][0000:02:00.0] BIT signature found
Feb 14 15:13:43 linux-ytaf kernel: nouveau  [   VBIOS][0000:02:00.0] version 80.04.4b.00.07
Feb 14 15:13:43 linux-ytaf kernel: nouveau  [     PMC][0000:02:00.0] MSI interrupts enabled
Feb 14 15:13:43 linux-ytaf kernel: nouveau  [     PFB][0000:02:00.0] RAM type: GDDR5
Feb 14 15:13:43 linux-ytaf kernel: nouveau  [     PFB][0000:02:00.0] RAM size: 2048 MiB
Feb 14 15:13:43 linux-ytaf kernel: nouveau  [     PFB][0000:02:00.0]    ZCOMP: 0 tags
Feb 14 15:13:43 linux-ytaf kernel: nouveau  [    VOLT][0000:02:00.0] GPU voltage: 987500uv
Feb 14 15:13:43 linux-ytaf kernel: xhci_hcd 0000:05:00.0: hcc params 0x0200f180 hci version 0x96 quirks 0x00080000
Feb 14 15:13:43 linux-ytaf kernel: usb usb5: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 15:13:43 linux-ytaf kernel: usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 15:13:43 linux-ytaf kernel: usb usb5: Product: xHCI Host Controller
Feb 14 15:13:43 linux-ytaf kernel: usb usb5: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 15:13:43 linux-ytaf kernel: usb usb5: SerialNumber: 0000:05:00.0
Feb 14 15:13:43 linux-ytaf kernel: hub 5-0:1.0: USB hub found
Feb 14 15:13:43 linux-ytaf kernel: hub 5-0:1.0: 2 ports detected
Feb 14 15:13:43 linux-ytaf kernel: xhci_hcd 0000:05:00.0: xHCI Host Controller
Feb 14 15:13:43 linux-ytaf kernel: xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 6
Feb 14 15:13:43 linux-ytaf kernel: usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
Feb 14 15:13:43 linux-ytaf kernel: usb usb6: New USB device found, idVendor=1d6b, idProduct=0003
Feb 14 15:13:43 linux-ytaf kernel: usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 15:13:43 linux-ytaf kernel: usb usb6: Product: xHCI Host Controller
Feb 14 15:13:43 linux-ytaf kernel: usb usb6: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 15:13:43 linux-ytaf kernel: usb usb6: SerialNumber: 0000:05:00.0
Feb 14 15:13:43 linux-ytaf kernel: hub 6-0:1.0: USB hub found
Feb 14 15:13:43 linux-ytaf kernel: hub 6-0:1.0: 2 ports detected
Feb 14 15:13:43 linux-ytaf kernel: nouveau  [  PTHERM][0000:02:00.0] FAN control: PWM
Feb 14 15:13:43 linux-ytaf kernel: nouveau  [  PTHERM][0000:02:00.0] fan management: automatic
Feb 14 15:13:43 linux-ytaf kernel: nouveau  [  PTHERM][0000:02:00.0] internal sensor: yes
Feb 14 15:13:43 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 07: core 324 MHz memory 648 MHz 
Feb 14 15:13:43 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 0a: core 324-862 MHz memory 1620 MHz 
Feb 14 15:13:43 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 0d: core 540-1202 MHz memory 6008 MHz 
Feb 14 15:13:43 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 0f: core 540-1202 MHz memory 6008 MHz 
Feb 14 15:13:43 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] --: core 324 MHz memory 648 MHz 
Feb 14 15:13:43 linux-ytaf kernel: raid6: sse2x1   gen() 11251 MB/s
Feb 14 15:13:43 linux-ytaf kernel: usb 1-1: new high-speed USB device number 2 using ehci-pci
Feb 14 15:13:43 linux-ytaf kernel: [TTM] Zone  kernel: Available graphics memory: 4034698 kiB
Feb 14 15:13:43 linux-ytaf kernel: [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
Feb 14 15:13:43 linux-ytaf kernel: [TTM] Initializing pool allocator
Feb 14 15:13:43 linux-ytaf kernel: [TTM] Initializing DMA pool allocator
Feb 14 15:13:43 linux-ytaf kernel: nouveau  [     DRM] VRAM: 2048 MiB
Feb 14 15:13:43 linux-ytaf kernel: nouveau  [     DRM] GART: 1048576 MiB
Feb 14 15:13:43 linux-ytaf kernel: nouveau  [     DRM] TMDS table version 2.0
Feb 14 15:13:43 linux-ytaf kernel: nouveau  [     DRM] DCB version 4.0
Feb 14 15:13:43 linux-ytaf kernel: nouveau  [     DRM] DCB outp 00: 01000f02 00020030
Feb 14 15:13:43 linux-ytaf kernel: nouveau  [     DRM] DCB outp 01: 02000f00 00000000
Feb 14 15:13:43 linux-ytaf kernel: nouveau  [     DRM] DCB outp 02: 08011f82 00020030
Feb 14 15:13:43 linux-ytaf kernel: nouveau  [     DRM] DCB outp 03: 02822f62 0f420010
Feb 14 15:13:43 linux-ytaf kernel: nouveau  [     DRM] DCB outp 05: 04833fb6 0f420010
Feb 14 15:13:43 linux-ytaf kernel: nouveau  [     DRM] DCB outp 06: 04033f72 00020010
Feb 14 15:13:43 linux-ytaf kernel: nouveau  [     DRM] DCB conn 00: 00001030
Feb 14 15:13:43 linux-ytaf kernel: nouveau  [     DRM] DCB conn 01: 00020131
Feb 14 15:13:43 linux-ytaf kernel: nouveau  [     DRM] DCB conn 02: 00002261
Feb 14 15:13:43 linux-ytaf kernel: nouveau  [     DRM] DCB conn 03: 00010346
Feb 14 15:13:43 linux-ytaf kernel: nouveau  [     DRM] DCB conn 04: 00000460
Feb 14 15:13:43 linux-ytaf kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Feb 14 15:13:43 linux-ytaf kernel: [drm] Driver supports precise vblank timestamp query.
Feb 14 15:13:43 linux-ytaf kernel: nouveau  [     DRM] MM: using COPY for buffer copies
Feb 14 15:13:43 linux-ytaf kernel: raid6: sse2x1   xor()  8961 MB/s
Feb 14 15:13:43 linux-ytaf kernel: usb 4-1: new high-speed USB device number 2 using ehci-pci
Feb 14 15:13:44 linux-ytaf kernel: raid6: sse2x2   gen() 14106 MB/s
Feb 14 15:13:44 linux-ytaf kernel: usb 1-1: New USB device found, idVendor=8087, idProduct=0024
Feb 14 15:13:44 linux-ytaf kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb 14 15:13:44 linux-ytaf kernel: hub 1-1:1.0: USB hub found
Feb 14 15:13:44 linux-ytaf kernel: hub 1-1:1.0: 6 ports detected
Feb 14 15:13:44 linux-ytaf kernel: raid6: sse2x2   xor() 10049 MB/s
Feb 14 15:13:44 linux-ytaf kernel: usb 5-2: new high-speed USB device number 2 using xhci_hcd
Feb 14 15:13:44 linux-ytaf kernel: usb 4-1: New USB device found, idVendor=8087, idProduct=0024
Feb 14 15:13:44 linux-ytaf kernel: usb 4-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb 14 15:13:44 linux-ytaf kernel: hub 4-1:1.0: USB hub found
Feb 14 15:13:44 linux-ytaf kernel: hub 4-1:1.0: 8 ports detected
Feb 14 15:13:44 linux-ytaf kernel: raid6: sse2x4   gen() 16289 MB/s
Feb 14 15:13:44 linux-ytaf kernel: raid6: sse2x4   xor() 12094 MB/s
Feb 14 15:13:44 linux-ytaf kernel: raid6: using algorithm sse2x4 gen() 16289 MB/s
Feb 14 15:13:44 linux-ytaf kernel: raid6: .... xor() 12094 MB/s, rmw enabled
Feb 14 15:13:44 linux-ytaf kernel: raid6: using ssse3x2 recovery algorithm
Feb 14 15:13:44 linux-ytaf kernel: xor: automatically using best checksumming function:
Feb 14 15:13:44 linux-ytaf kernel: nouveau  [     DRM] allocated 1920x1080 fb: 0x60000, bo ffff88000a8a0800
Feb 14 15:13:44 linux-ytaf kernel: fbcon: nouveaufb (fb0) is primary device
Feb 14 15:13:44 linux-ytaf kernel:    avx       : 31206.000 MB/sec
Feb 14 15:13:44 linux-ytaf kernel: Btrfs loaded, assert=on
Feb 14 15:13:44 linux-ytaf kernel: BTRFS: device fsid 21024970-7a27-4114-8525-d8dd026f23b6 devid 1 transid 437 /dev/sdb3
Feb 14 15:13:44 linux-ytaf kernel: usb 5-2: New USB device found, idVendor=0930, idProduct=6545
Feb 14 15:13:44 linux-ytaf kernel: usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 14 15:13:44 linux-ytaf kernel: usb 5-2: Product: TransMemory
Feb 14 15:13:44 linux-ytaf kernel: usb 5-2: Manufacturer: TOSHIBA
Feb 14 15:13:44 linux-ytaf kernel: usb 5-2: SerialNumber: C89CDCBF6D59EF4140000065
Feb 14 15:13:44 linux-ytaf kernel: usb-storage 5-2:1.0: USB Mass Storage device detected
Feb 14 15:13:44 linux-ytaf kernel: scsi host8: usb-storage 5-2:1.0
Feb 14 15:13:44 linux-ytaf kernel: usbcore: registered new interface driver usb-storage
Feb 14 15:13:44 linux-ytaf kernel: usbcore: registered new interface driver uas
Feb 14 15:13:44 linux-ytaf kernel: usb 1-1.4: new full-speed USB device number 3 using ehci-pci
Feb 14 15:13:44 linux-ytaf kernel: usb 4-1.1: new full-speed USB device number 3 using ehci-pci
Feb 14 15:13:44 linux-ytaf kernel: usb 4-1.1: New USB device found, idVendor=1532, idProduct=0109
Feb 14 15:13:44 linux-ytaf kernel: usb 4-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 14 15:13:44 linux-ytaf kernel: usb 4-1.1: Product: Razer Lycosa
Feb 14 15:13:44 linux-ytaf kernel: usb 4-1.1: Manufacturer: Razer
Feb 14 15:13:44 linux-ytaf kernel: usbcore: registered new interface driver usbhid
Feb 14 15:13:44 linux-ytaf kernel: usbhid: USB HID core driver
Feb 14 15:13:44 linux-ytaf kernel: input: Razer Razer Lycosa as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1:1.0/0003:1532:0109.0001/input/input6
Feb 14 15:13:44 linux-ytaf kernel: usb 1-1.4: New USB device found, idVendor=06a3, idProduct=0ccb
Feb 14 15:13:44 linux-ytaf kernel: usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 14 15:13:44 linux-ytaf kernel: usb 1-1.4: Product: Cyborg R.A.T.7 Mouse
Feb 14 15:13:44 linux-ytaf kernel: usb 1-1.4: Manufacturer: Saitek
Feb 14 15:13:44 linux-ytaf kernel: hid-generic 0003:1532:0109.0001: input,hidraw0: USB HID v1.10 Keyboard [Razer Razer Lycosa] on usb-0000:00:1d.0-1.1/input0
Feb 14 15:13:44 linux-ytaf kernel: input: Razer Razer Lycosa as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1:1.1/0003:1532:0109.0002/input/input7
Feb 14 15:13:44 linux-ytaf kernel: hid-generic 0003:1532:0109.0002: input,hidraw1: USB HID v1.10 Device [Razer Razer Lycosa] on usb-0000:00:1d.0-1.1/input1
Feb 14 15:13:44 linux-ytaf kernel: Console: switching to colour frame buffer device 210x65
Feb 14 15:13:44 linux-ytaf kernel: nouveau 0000:02:00.0: fb0: nouveaufb frame buffer device
Feb 14 15:13:44 linux-ytaf kernel: nouveau 0000:02:00.0: registered panic notifier
Feb 14 15:13:44 linux-ytaf kernel: [drm] Initialized nouveau 1.2.2 20120801 for 0000:02:00.0 on minor 0
Feb 14 15:13:44 linux-ytaf kernel: [drm] Memory usable by graphics device = 2048M
Feb 14 15:13:44 linux-ytaf kernel: [drm] Replacing VGA console driver
Feb 14 15:13:44 linux-ytaf kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Feb 14 15:13:44 linux-ytaf kernel: [drm] Driver supports precise vblank timestamp query.
Feb 14 15:13:44 linux-ytaf kernel: vgaarb: device changed decodes: PCI:0000:02:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
Feb 14 15:13:44 linux-ytaf kernel: [drm] Initialized i915 1.6.0 20150327 for 0000:00:02.0 on minor 1
Feb 14 15:13:44 linux-ytaf kernel: [drm] GMBUS [i915 gmbus vga] timed out, falling back to bit banging on pin 2
Feb 14 15:13:44 linux-ytaf kernel: i915 0000:00:02.0: No connectors reported connected with modes
Feb 14 15:13:44 linux-ytaf kernel: [drm] Cannot find any crtc or sizes - going 1024x768
Feb 14 15:13:44 linux-ytaf kernel: i915 0000:00:02.0: fb1: inteldrmfb frame buffer device
Feb 14 15:13:45 linux-ytaf kernel: scsi 8:0:0:0: Direct-Access     TOSHIBA  TransMemory      PMAP PQ: 0 ANSI: 6
Feb 14 15:13:45 linux-ytaf kernel: sd 8:0:0:0: Attached scsi generic sg3 type 0
Feb 14 15:13:45 linux-ytaf kernel: sd 8:0:0:0: [sdc] 30228480 512-byte logical blocks: (15.4 GB/14.4 GiB)
Feb 14 15:13:45 linux-ytaf kernel: sd 8:0:0:0: [sdc] Write Protect is off
Feb 14 15:13:45 linux-ytaf kernel: sd 8:0:0:0: [sdc] Mode Sense: 45 00 00 00
Feb 14 15:13:45 linux-ytaf kernel: sd 8:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Feb 14 15:13:45 linux-ytaf kernel:  sdc: sdc1
Feb 14 15:13:45 linux-ytaf kernel: sd 8:0:0:0: [sdc] Attached SCSI removable disk
Feb 14 15:13:45 linux-ytaf kernel: PM: Starting manual resume from disk
Feb 14 15:13:45 linux-ytaf kernel: PM: Hibernation image partition 8:18 present
Feb 14 15:13:45 linux-ytaf kernel: PM: Looking for hibernation image.
Feb 14 15:13:45 linux-ytaf kernel: PM: Image not found (code -22)
Feb 14 15:13:45 linux-ytaf kernel: PM: Hibernation image not present or could not be loaded.
Feb 14 15:13:45 linux-ytaf kernel: BTRFS info (device sdb3): disk space caching is enabled
Feb 14 15:13:45 linux-ytaf kernel: BTRFS: has skinny extents
Feb 14 15:13:45 linux-ytaf systemd-journal[187]: Journal stopped
Feb 14 15:13:48 linux-ytaf systemd-journal[476]: Runtime journal is using 8.0M (max allowed 394.0M, trying to leave 591.0M free of 3.8G available → current limit 394.0M).
Feb 14 15:13:48 linux-ytaf systemd-journal[476]: Runtime journal is using 8.0M (max allowed 394.0M, trying to leave 591.0M free of 3.8G available → current limit 394.0M).
Feb 14 15:13:48 linux-ytaf kernel: random: nonblocking pool is initialized
Feb 14 15:13:48 linux-ytaf systemd[1]: RTC configured in localtime, applying delta of 60 minutes to system time.
Feb 14 15:13:48 linux-ytaf kernel: thermal LNXTHERM:00: registered as thermal_zone0
Feb 14 15:13:48 linux-ytaf kernel: ACPI: Thermal Zone [TZ00] (28 C)
Feb 14 15:13:48 linux-ytaf kernel: thermal LNXTHERM:01: registered as thermal_zone1
Feb 14 15:13:48 linux-ytaf kernel: ACPI: Thermal Zone [TZ01] (30 C)
Feb 14 15:13:48 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20150410/utaddress-254)
Feb 14 15:13:48 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 15:13:48 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150410/utaddress-254)
Feb 14 15:13:48 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150410/utaddress-254)
Feb 14 15:13:48 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 15:13:48 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150410/utaddress-254)
Feb 14 15:13:48 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150410/utaddress-254)
Feb 14 15:13:48 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 15:13:48 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150410/utaddress-254)
Feb 14 15:13:48 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150410/utaddress-254)
Feb 14 15:13:48 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 15:13:48 linux-ytaf kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
Feb 14 15:13:48 linux-ytaf systemd-journal[476]: Journal started
Feb 14 15:13:47 linux-ytaf systemd-udevd[494]: starting version 210
Feb 14 15:13:47 linux-ytaf systemd-udevd[494]: Network interface NamePolicy= disabled on kernel commandline, ignoring.
Feb 14 15:13:47 linux-ytaf systemd-udevd[494]: invalid key/value pair in file /usr/lib/udev/rules.d/51-android.rules on line 115,starting at character 57 ('')
Feb 14 15:13:48 linux-ytaf kernel: BTRFS info (device sdb3): disk space caching is enabled
Feb 14 15:13:48 linux-ytaf kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Feb 14 15:13:48 linux-ytaf kernel: input: PC Speaker as /devices/platform/pcspkr/input/input8
Feb 14 15:13:48 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000580-0x000000000000059F conflicts with OpRegion 0x0000000000000580-0x000000000000058F (\_SB_.PCI0.SBUS.SMBI) (20150410/utaddress-254)
Feb 14 15:13:48 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000580-0x000000000000059F conflicts with OpRegion 0x0000000000000580-0x000000000000059F (\_SB_.PCI0.SMB_.SMIO) (20150410/utaddress-254)
Feb 14 15:13:48 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 15:13:48 linux-ytaf kernel: pps_core: LinuxPPS API ver. 1 registered
Feb 14 15:13:48 linux-ytaf kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
Feb 14 15:13:48 linux-ytaf kernel: iTCO_vendor_support: vendor-support=0
Feb 14 15:13:49 linux-ytaf kernel: PTP clock support registered
Feb 14 15:13:49 linux-ytaf kernel: e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
Feb 14 15:13:49 linux-ytaf kernel: e1000e: Copyright(c) 1999 - 2014 Intel Corporation.
Feb 14 15:13:49 linux-ytaf kernel: e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
Feb 14 15:13:49 linux-ytaf kernel: asus_wmi: ASUS WMI generic driver loaded
Feb 14 15:13:49 linux-ytaf kernel: asus_wmi: Initialization: 0x0
Feb 14 15:13:49 linux-ytaf kernel: asus_wmi: BIOS WMI version: 0.9
Feb 14 15:13:49 linux-ytaf kernel: asus_wmi: SFUN value: 0x0
Feb 14 15:13:49 linux-ytaf kernel: input: Eee PC WMI hotkeys as /devices/platform/eeepc-wmi/input/input9
Feb 14 15:13:49 linux-ytaf kernel: asus_wmi: Disabling ACPI video driver
Feb 14 15:13:49 linux-ytaf kernel: iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
Feb 14 15:13:49 linux-ytaf kernel: iTCO_wdt: Found a Cougar Point TCO device (Version=2, TCOBASE=0x0460)
Feb 14 15:13:49 linux-ytaf kernel: iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
Feb 14 15:13:49 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: registered PHC clock
Feb 14 15:13:49 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) c8:60:00:09:38:76
Feb 14 15:13:49 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
Feb 14 15:13:49 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: FFFFFF-0FF
Feb 14 15:13:49 linux-ytaf mtp-probe[641]: checking bus 4, device 3: "/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1"
Feb 14 15:13:49 linux-ytaf mtp-probe[653]: checking bus 5, device 2: "/sys/devices/pci0000:00/0000:00:1c.5/0000:05:00.0/usb5/5-2"
Feb 14 15:13:49 linux-ytaf mtp-probe[644]: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4"
Feb 14 15:13:49 linux-ytaf mtp-probe[644]: bus: 1, device: 3 was not an MTP device
Feb 14 15:13:49 linux-ytaf mtp-probe[653]: bus: 5, device: 2 was not an MTP device
Feb 14 15:13:49 linux-ytaf mtp-probe[641]: bus: 4, device: 3 was not an MTP device
Feb 14 15:13:49 linux-ytaf kernel: snd_hda_intel 0000:00:1b.0: enabling device (0000 -> 0002)
Feb 14 15:13:49 linux-ytaf kernel: snd_hda_intel 0000:02:00.1: enabling device (0000 -> 0002)
Feb 14 15:13:49 linux-ytaf kernel: snd_hda_intel 0000:02:00.1: Disabling MSI
Feb 14 15:13:49 linux-ytaf kernel: snd_hda_intel 0000:02:00.1: Handle VGA-switcheroo audio client
Feb 14 15:13:49 linux-ytaf kernel: AVX version of gcm_enc/dec engaged.
Feb 14 15:13:49 linux-ytaf kernel: AES CTR mode by8 optimization enabled
Feb 14 15:13:49 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC889: line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line
Feb 14 15:13:49 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Feb 14 15:13:49 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
Feb 14 15:13:49 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
Feb 14 15:13:49 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    dig-out=0x11/0x1e
Feb 14 15:13:49 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    inputs:
Feb 14 15:13:49 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:      Front Mic=0x19
Feb 14 15:13:49 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:      Rear Mic=0x18
Feb 14 15:13:49 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:      Line=0x1a
Feb 14 15:13:49 linux-ytaf kernel: input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
Feb 14 15:13:49 linux-ytaf kernel: input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
Feb 14 15:13:49 linux-ytaf kernel: input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
Feb 14 15:13:49 linux-ytaf kernel: input: HDA Intel PCH Line Out Front as /devices/pci0000:00/0000:00:1b.0/sound/card0/input13
Feb 14 15:13:49 linux-ytaf kernel: input: HDA Intel PCH Line Out Surround as /devices/pci0000:00/0000:00:1b.0/sound/card0/input14
Feb 14 15:13:49 linux-ytaf kernel: input: HDA Intel PCH Line Out CLFE as /devices/pci0000:00/0000:00:1b.0/sound/card0/input15
Feb 14 15:13:49 linux-ytaf kernel: input: HDA Intel PCH Line Out Side as /devices/pci0000:00/0000:00:1b.0/sound/card0/input16
Feb 14 15:13:49 linux-ytaf kernel: input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input17
Feb 14 15:13:49 linux-ytaf kernel: Adding 2104316k swap on /dev/sdb2.  Priority:-1 extents:1 across:2104316k FS
Feb 14 15:13:49 linux-ytaf kernel: input: Saitek Cyborg R.A.T.7 Mouse as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/0003:06A3:0CCB.0003/input/input18
Feb 14 15:13:49 linux-ytaf kernel: saitek 0003:06A3:0CCB.0003: input,hidraw2: USB HID v1.11 Mouse [Saitek Cyborg R.A.T.7 Mouse] on usb-0000:00:1a.0-1.4/input0
Feb 14 15:13:49 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input19
Feb 14 15:13:49 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input20
Feb 14 15:13:49 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input21
Feb 14 15:13:49 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input22
Feb 14 15:13:50 linux-ytaf kernel: FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Feb 14 15:13:50 linux-ytaf systemd-fsck[749]: /sbin/fsck.xfs: XFS file system.
Feb 14 15:13:50 linux-ytaf kernel: SGI XFS with ACLs, security attributes, realtime, no debug enabled
Feb 14 15:13:50 linux-ytaf kernel: XFS (sdb4): Mounting V5 Filesystem
Feb 14 15:13:50 linux-ytaf kernel: XFS (sdb4): Starting recovery (logdev: internal)
Feb 14 15:13:52 linux-ytaf kernel: XFS (sdb4): Ending recovery (logdev: internal)
Feb 14 15:13:53 linux-ytaf systemd-journal[476]: Permanent journal is using 83.2M (max allowed 4.0G, trying to leave 4.0G free of 32.8G available → current limit 4.0G).
Feb 14 15:13:53 linux-ytaf systemd-journal[476]: Time spent on flushing to /var is 33.707ms for 1032 entries.
Feb 14 15:13:53 linux-ytaf kernel: audit: type=1305 audit(1455459232.537:2): audit_pid=812 old=0 auid=4294967295 ses=4294967295 res=1
Feb 14 15:13:52 linux-ytaf auditd[812]: Started dispatcher: /sbin/audispd pid: 823
Feb 14 15:13:52 linux-ytaf audispd[823]: priority_boost_parser called with: 4
Feb 14 15:13:52 linux-ytaf audispd[823]: max_restarts_parser called with: 10
Feb 14 15:13:52 linux-ytaf audispd[823]: No plugins found, exiting
Feb 14 15:13:52 linux-ytaf auditd[812]: Init complete, auditd 2.3.6 listening for events (startup state enable)
Feb 14 15:13:53 linux-ytaf auditctl[813]: No rules
Feb 14 15:13:53 linux-ytaf auditctl[813]: AUDIT_STATUS: enabled=0 flag=1 pid=0 rate_limit=0 backlog_limit=320 lost=0 backlog=0
Feb 14 15:13:53 linux-ytaf boot.apparmor[826]: Starting AppArmor ..done
Feb 14 15:13:53 linux-ytaf dbus-daemon[988]: Unknown username "srvGeoClue" in message bus configuration file
Feb 14 15:13:54 linux-ytaf avahi-daemon[989]: Found user 'avahi' (UID 486) and group 'avahi' (GID 485).
Feb 14 15:13:54 linux-ytaf avahi-daemon[989]: Successfully dropped root privileges.
Feb 14 15:13:54 linux-ytaf avahi-daemon[989]: avahi-daemon 0.6.31 starting up.
Feb 14 15:13:54 linux-ytaf avahi-daemon[989]: Loading service file /etc/avahi/services/sftp-ssh.service.
Feb 14 15:13:54 linux-ytaf avahi-daemon[989]: Loading service file /etc/avahi/services/ssh.service.
Feb 14 15:13:54 linux-ytaf avahi-daemon[989]: Network interface enumeration completed.
Feb 14 15:13:54 linux-ytaf avahi-daemon[989]: Registering HINFO record with values 'X86_64'/'LINUX'.
Feb 14 15:13:54 linux-ytaf avahi-daemon[989]: Server startup complete. Host name is linux-ytaf.local. Local service cookie is 3074963766.
Feb 14 15:13:54 linux-ytaf avahi-daemon[989]: Service "linux-ytaf" (/etc/avahi/services/ssh.service) successfully established.
Feb 14 15:13:54 linux-ytaf avahi-daemon[989]: Service "linux-ytaf" (/etc/avahi/services/sftp-ssh.service) successfully established.
Feb 14 15:13:54 linux-ytaf display-manager[1018]: /etc/vconsole.conf available
Feb 14 15:13:54 linux-ytaf display-manager[1018]: KEYMAP: de-latin1-nodeadkeys
Feb 14 15:13:54 linux-ytaf display-manager[1018]: Command: localectl set-keymap de-latin1-nodeadkeys
Feb 14 15:13:54 linux-ytaf display-manager[1018]: I: Using systemd /usr/share/systemd/kbd-model-map mapping
Feb 14 15:13:54 linux-ytaf dbus[988]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service'
Feb 14 15:13:54 linux-ytaf dbus[988]: [system] Successfully activated service 'org.freedesktop.locale1'
Feb 14 15:13:54 linux-ytaf smartd[995]: smartd 6.2 2013-11-07 r3856 [x86_64-linux-4.1.15-8-default] (SUSE RPM)
Feb 14 15:13:54 linux-ytaf smartd[995]: Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
Feb 14 15:13:54 linux-ytaf smartd[995]: Opened configuration file /etc/smartd.conf
Feb 14 15:13:54 linux-ytaf smartd[995]: Drive: DEVICESCAN, implied '-a' Directive on line 26 of file /etc/smartd.conf
Feb 14 15:13:54 linux-ytaf smartd[995]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
Feb 14 15:13:54 linux-ytaf smartd[995]: Device: /dev/sda, type changed from 'scsi' to 'sat'
Feb 14 15:13:54 linux-ytaf smartd[995]: Device: /dev/sda [SAT], opened
Feb 14 15:13:54 linux-ytaf smartd[995]: Device: /dev/sda [SAT], SAMSUNG SSD 830 Series, S/N:S0Z4NEAC906195, WWN:5-002538-043584d30, FW:CXM03B1Q, 256 GB
Feb 14 15:13:54 linux-ytaf smartd[995]: Device: /dev/sda [SAT], found in smartd database: Samsung based SSDs
Feb 14 15:13:54 linux-ytaf smartd[995]: Device: /dev/sda [SAT], can't monitor Current_Pending_Sector count - no Attribute 197
Feb 14 15:13:54 linux-ytaf smartd[995]: Device: /dev/sda [SAT], can't monitor Offline_Uncorrectable count - no Attribute 198
Feb 14 15:13:54 linux-ytaf smartd[995]: Device: /dev/sda [SAT], is SMART capable. Adding to "monitor" list.
Feb 14 15:13:54 linux-ytaf smartd[995]: Device: /dev/sda [SAT], state read from /var/lib/smartmontools/smartd.SAMSUNG_SSD_830_Series-S0Z4NEAC906195.ata.state
Feb 14 15:13:54 linux-ytaf smartd[995]: Device: /dev/sdb, type changed from 'scsi' to 'sat'
Feb 14 15:13:54 linux-ytaf smartd[995]: Device: /dev/sdb [SAT], opened
Feb 14 15:13:54 linux-ytaf smartd[995]: Device: /dev/sdb [SAT], TOSHIBA HDWD110, S/N:Y5GDEMGFS, WWN:5-000039-fe7c5a79c, FW:MS2OA8J0, 1.00 TB
Feb 14 15:13:54 linux-ytaf smartd[995]: Device: /dev/sdb [SAT], not found in smartd database.
Feb 14 15:13:54 linux-ytaf ModemManager[991]: <info>  ModemManager (version 1.4.10) starting in system bus...
Feb 14 15:13:54 linux-ytaf dbus[988]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Feb 14 15:13:54 linux-ytaf SuSEfirewall2[1085]: Firewall rules set to CLOSE.
Feb 14 15:13:54 linux-ytaf kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
Feb 14 15:13:54 linux-ytaf kernel: nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
Feb 14 15:13:54 linux-ytaf kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Feb 14 15:13:54 linux-ytaf kernel: No iBFT detected.
Feb 14 15:13:54 linux-ytaf polkitd[1092]: Started polkitd version 0.113
Feb 14 15:13:54 linux-ytaf polkitd[1092]: Loading rules from directory /etc/polkit-1/rules.d
Feb 14 15:13:54 linux-ytaf polkitd[1092]: Loading rules from directory /usr/share/polkit-1/rules.d
Feb 14 15:13:54 linux-ytaf polkitd[1092]: Finished loading, compiling and executing 3 rules
Feb 14 15:13:54 linux-ytaf dbus[988]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Feb 14 15:13:54 linux-ytaf polkitd[1092]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
Feb 14 15:13:54 linux-ytaf logger[1091]: /etc/init.d/xdm: No changes for /etc/X11/xdm/Xservers
Feb 14 15:13:54 linux-ytaf logger[1091]: /etc/init.d/xdm: No changes for /etc/X11/xdm/xdm-config
Feb 14 15:13:55 linux-ytaf display-manager[1018]: Starting service sddm..done
Feb 14 15:13:55 linux-ytaf smartd[995]: Device: /dev/sdb [SAT], is SMART capable. Adding to "monitor" list.
Feb 14 15:13:55 linux-ytaf smartd[995]: Device: /dev/sdb [SAT], state read from /var/lib/smartmontools/smartd.TOSHIBA_HDWD110-Y5GDEMGFS.ata.state
Feb 14 15:13:55 linux-ytaf smartd[995]: Monitoring 2 ATA and 0 SCSI devices
Feb 14 15:13:55 linux-ytaf smartd[995]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 77 to 76
Feb 14 15:13:56 linux-ytaf smartd[995]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 253 to 230
Feb 14 15:13:56 linux-ytaf smartd[995]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.SAMSUNG_SSD_830_Series-S0Z4NEAC906195.ata.state
Feb 14 15:13:56 linux-ytaf smartd[995]: Device: /dev/sdb [SAT], state written to /var/lib/smartmontools/smartd.TOSHIBA_HDWD110-Y5GDEMGFS.ata.state
Feb 14 15:13:57 linux-ytaf sddm[1264]: Starting...
Feb 14 15:13:57 linux-ytaf sddm[1264]: Display server starting...
Feb 14 15:13:57 linux-ytaf sddm[1264]: Running: /usr/bin/X -nolisten tcp -auth /run/sddm/{22651807-cd87-42ec-9c6a-f3563ddf4bd4} -background none -noreset -displayfd 17 vt7
Feb 14 15:13:57 linux-ytaf ModemManager[991]: <info>  Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin
Feb 14 15:13:57 linux-ytaf kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Feb 14 15:13:57 linux-ytaf wickedd-dhcp4[1095]: eth0: Request to acquire DHCPv4 lease with UUID a28bc056-7aac-0800-4d04-000004000000
Feb 14 15:13:57 linux-ytaf kernel: NET: Registered protocol family 17
Feb 14 15:13:58 linux-ytaf wickedd-dhcp4[1095]: eth0: Committed DHCPv4 lease with address 192.168.178.12 (lease time 864000 sec, renew in 432000 sec, rebind in 756000 sec)
Feb 14 15:13:58 linux-ytaf avahi-daemon[989]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.178.12.
Feb 14 15:13:58 linux-ytaf avahi-daemon[989]: New relevant interface eth0.IPv4 for mDNS.
Feb 14 15:13:58 linux-ytaf avahi-daemon[989]: Registering new address record for 192.168.178.12 on eth0.IPv4.
Feb 14 15:13:58 linux-ytaf wickedd[1101]: eth0: Notified neighbours about IP address 192.168.178.12
Feb 14 15:13:58 linux-ytaf sddm[1264]: Socket server starting...
Feb 14 15:13:58 MM-Home wicked[1107]: lo              up
Feb 14 15:13:58 MM-Home wicked[1107]: eth0            up
Feb 14 15:13:58 MM-Home sddm[1264]: Greeter starting...
Feb 14 15:13:58 MM-Home sddm[1264]: Adding cookie to "/run/sddm/{22651807-cd87-42ec-9c6a-f3563ddf4bd4}"
Feb 14 15:13:59 MM-Home sddm-helper[1466]: [PAM] Starting...
Feb 14 15:13:59 MM-Home sddm-helper[1466]: [PAM] Authenticating...
Feb 14 15:13:59 MM-Home sddm-helper[1466]: [PAM] returning.
Feb 14 15:13:59 MM-Home sddm-helper[1466]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
Feb 14 15:13:59 MM-Home systemd[1470]: pam_unix(systemd-user:session): session opened for user sddm by (uid=0)
Feb 14 15:13:59 MM-Home SuSEfirewall2[1473]: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Feb 14 15:13:59 MM-Home echo[1458]: Starting mail service (Postfix)
Feb 14 15:13:59 MM-Home SuSEfirewall2[1483]: using default zone 'ext' for interface eth0
Feb 14 15:13:59 MM-Home iscsiadm[1459]: iscsiadm: No records found
Feb 14 15:13:59 MM-Home ntpd[1502]: ntpd 4.2.8p4@1.3265-o Thu Dec 17 05:32:52 UTC 2015 (1): Starting
Feb 14 15:13:59 MM-Home ntpd[1502]: Command line: /usr/sbin/ntpd -p /var/run/ntp/ntpd.pid -g -u ntp:ntp -c /etc/ntp.conf
Feb 14 15:13:59 MM-Home ntpd[1510]: proto: precision = 0.100 usec (-23)
Feb 14 15:13:59 MM-Home ntpd[1510]: switching logging to file /var/log/ntp
Feb 14 15:13:59 MM-Home sntp[1511]: sntp 4.2.8p4@1.3265-o Thu Dec 17 05:32:29 UTC 2015 (1)
Feb 14 15:13:59 MM-Home sntp[1511]: kod_init_kod_db(): Cannot open KoD db file /var/db/ntp-kod: No such file or directory
Feb 14 15:13:59 MM-Home start-ntpd[1462]: Starting network time protocol daemon (NTPD)sntp 4.2.8p4@1.3265-o Thu Dec 17 05:32:29 UTC 2015 (1)
Feb 14 15:13:59 MM-Home start-ntpd[1462]: kod_init_kod_db(): Cannot open KoD db file /var/db/ntp-kod: No such file or directory
Feb 14 15:13:59 MM-Home sntp[1511]: 2016-02-14 15:13:59.800419 (-0100) -0.48879 +/- 0.376271 192.168.178.1 s3 no-leap
Feb 14 15:13:59 MM-Home start-ntpd[1462]: 2016-02-14 15:13:59.800419 (-0100) -0.48879 +/- 0.376271 192.168.178.1 s3 no-leap
Feb 14 15:13:59 MM-Home sddm[1264]: Message received from greeter: Connect
Feb 14 15:13:59 MM-Home /usr/sbin/start-ntpd[1582]: runtime configuration: server 192.168.178.1
Feb 14 15:14:00 MM-Home SuSEfirewall2[1667]: Firewall rules successfully set
Feb 14 15:14:00 MM-Home postfix/postfix-script[1663]: starting the Postfix mail system
Feb 14 15:14:00 MM-Home postfix/master[1670]: daemon started -- version 2.11.6, configuration /etc/postfix
Feb 14 15:14:01 MM-Home cron[1688]: (CRON) INFO (RANDOM_DELAY will be scaled with factor 80% if used.)
Feb 14 15:14:01 MM-Home cron[1688]: (CRON) INFO (running with inotify support)
Feb 14 15:14:02 MM-Home dbus[988]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
Feb 14 15:14:02 MM-Home udisksd[1697]: udisks daemon version 2.1.6 starting
Feb 14 15:14:03 MM-Home dbus[988]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Feb 14 15:14:03 MM-Home udisksd[1697]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Feb 14 15:14:03 MM-Home dbus[988]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
Feb 14 15:14:03 MM-Home dbus[988]: [system] Successfully activated service 'org.freedesktop.UPower'
Feb 14 15:15:01 MM-Home cron[1734]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 15:15:01 MM-Home systemd[1735]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 15:15:01 MM-Home CRON[1734]: pam_unix(crond:session): session closed for user root
Feb 14 15:15:01 MM-Home systemd[1736]: pam_unix(systemd-user:session): session closed for user root
Feb 14 15:15:51 MM-Home kernel: nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
Feb 14 15:30:01 MM-Home cron[1778]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 15:30:01 MM-Home systemd[1779]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 15:30:01 MM-Home CRON[1778]: pam_unix(crond:session): session closed for user root
Feb 14 15:30:01 MM-Home systemd[1780]: pam_unix(systemd-user:session): session closed for user root
Feb 14 15:43:56 MM-Home smartd[995]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 76 to 77
Feb 14 15:43:56 MM-Home smartd[995]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 230 to 240
Feb 14 15:45:01 MM-Home cron[1823]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 15:45:01 MM-Home systemd[1824]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 15:45:01 MM-Home CRON[1823]: pam_unix(crond:session): session closed for user root
Feb 14 15:45:01 MM-Home systemd[1825]: pam_unix(systemd-user:session): session closed for user root
Feb 14 16:00:01 MM-Home cron[1865]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 16:00:01 MM-Home systemd[1866]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 16:00:01 MM-Home CRON[1865]: pam_unix(crond:session): session closed for user root
Feb 14 16:00:01 MM-Home systemd[1867]: pam_unix(systemd-user:session): session closed for user root
Feb 14 16:15:01 MM-Home cron[1918]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 16:15:01 MM-Home systemd[1919]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 16:15:02 MM-Home CRON[1918]: pam_unix(crond:session): session closed for user root
Feb 14 16:15:02 MM-Home systemd[1920]: pam_unix(systemd-user:session): session closed for user root
Feb 14 16:30:01 MM-Home cron[1962]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 16:30:01 MM-Home systemd[1963]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 16:30:01 MM-Home CRON[1962]: pam_unix(crond:session): session closed for user root
Feb 14 16:30:01 MM-Home systemd[1964]: pam_unix(systemd-user:session): session closed for user root
Feb 14 16:45:01 MM-Home cron[2007]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 16:45:01 MM-Home systemd[2008]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 16:45:01 MM-Home CRON[2007]: pam_unix(crond:session): session closed for user root
Feb 14 16:45:01 MM-Home systemd[2009]: pam_unix(systemd-user:session): session closed for user root
Feb 14 17:00:01 MM-Home cron[2052]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 17:00:01 MM-Home systemd[2053]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 17:00:01 MM-Home CRON[2052]: pam_unix(crond:session): session closed for user root
Feb 14 17:00:01 MM-Home systemd[2054]: pam_unix(systemd-user:session): session closed for user root
Feb 14 17:13:56 MM-Home smartd[995]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 77 to 76
Feb 14 17:13:56 MM-Home smartd[995]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 240 to 230
Feb 14 17:15:01 MM-Home cron[2108]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 17:15:01 MM-Home systemd[2109]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 17:15:01 MM-Home CRON[2108]: pam_unix(crond:session): session closed for user root
Feb 14 17:15:01 MM-Home systemd[2110]: pam_unix(systemd-user:session): session closed for user root
Feb 14 17:30:01 MM-Home cron[2149]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 17:30:01 MM-Home systemd[2150]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 17:30:01 MM-Home CRON[2149]: pam_unix(crond:session): session closed for user root
Feb 14 17:30:01 MM-Home systemd[2151]: pam_unix(systemd-user:session): session closed for user root
Feb 14 17:45:01 MM-Home cron[2194]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 17:45:01 MM-Home systemd[2195]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 17:45:01 MM-Home CRON[2194]: pam_unix(crond:session): session closed for user root
Feb 14 17:45:01 MM-Home systemd[2196]: pam_unix(systemd-user:session): session closed for user root
Feb 14 17:52:50 MM-Home sddm[1264]: Message received from greeter: Login
Feb 14 17:52:50 MM-Home sddm[1264]: Reading from "/usr/share/xsessions/plasma5.desktop"
Feb 14 17:52:50 MM-Home sddm[1264]: Session "/usr/share/xsessions/plasma5.desktop" selected, command: "/usr/bin/startkde"
Feb 14 17:52:50 MM-Home sddm-helper[2235]: [PAM] Starting...
Feb 14 17:52:50 MM-Home sddm-helper[2235]: [PAM] Authenticating...
Feb 14 17:52:50 MM-Home sddm-helper[2235]: [PAM] Preparing to converse...
Feb 14 17:52:50 MM-Home sddm-helper[2235]: [PAM] Conversation with 1 messages
Feb 14 17:52:50 MM-Home sddm-helper[2235]: [PAM] returning.
Feb 14 17:52:50 MM-Home sddm[1264]: Authenticated successfully
Feb 14 17:52:50 MM-Home sddm-helper[2235]: pam_unix(sddm:session): session opened for user marc by (uid=0)
Feb 14 17:52:50 MM-Home systemd[2236]: pam_unix(systemd-user:session): session opened for user marc by (uid=0)
Feb 14 17:52:50 MM-Home sddm-helper[2235]: Starting: "/etc/X11/xdm/Xsession" "/usr/bin/startkde"
Feb 14 17:52:50 MM-Home sddm-helper[2238]: Adding cookie to "/home/marc/.Xauthority"
Feb 14 17:52:50 MM-Home sddm-helper[1466]: [PAM] Ended.
Feb 14 17:52:50 MM-Home sddm[1264]: Auth: sddm-helper exited successfully
Feb 14 17:52:50 MM-Home sddm[1264]: Greeter stopped.
Feb 14 17:52:50 MM-Home sddm[1264]: Session started
Feb 14 17:52:54 MM-Home polkitd[1092]: Registered Authentication Agent for unix-session:13 (system bus name :1.55 [/usr/lib64/libexec/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale de_DE.UTF-8)
Feb 14 17:52:55 MM-Home dbus[988]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service'
Feb 14 17:52:55 MM-Home dbus[988]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Feb 14 17:52:55 MM-Home rtkit-daemon[2399]: Successfully called chroot.
Feb 14 17:52:55 MM-Home rtkit-daemon[2399]: Successfully dropped privileges.
Feb 14 17:52:55 MM-Home rtkit-daemon[2399]: Successfully limited resources.
Feb 14 17:52:55 MM-Home rtkit-daemon[2399]: Running.
Feb 14 17:52:55 MM-Home rtkit-daemon[2399]: Canary thread running.
Feb 14 17:52:55 MM-Home rtkit-daemon[2399]: Watchdog thread running.
Feb 14 17:52:55 MM-Home rtkit-daemon[2399]: Successfully made thread 2398 of process 2398 (/usr/bin/pulseaudio) owned by 'marc' high priority at nice level -11.
Feb 14 17:52:55 MM-Home rtkit-daemon[2399]: Supervising 1 threads of 1 processes of 1 users.
Feb 14 17:53:00 MM-Home rtkit-daemon[2399]: Supervising 1 threads of 1 processes of 1 users.
Feb 14 17:53:00 MM-Home rtkit-daemon[2399]: Successfully made thread 2403 of process 2398 (/usr/bin/pulseaudio) owned by 'marc' RT at priority 5.
Feb 14 17:53:00 MM-Home rtkit-daemon[2399]: Supervising 2 threads of 1 processes of 1 users.
Feb 14 17:53:01 MM-Home rtkit-daemon[2399]: Supervising 2 threads of 1 processes of 1 users.
Feb 14 17:53:01 MM-Home rtkit-daemon[2399]: Successfully made thread 2404 of process 2398 (/usr/bin/pulseaudio) owned by 'marc' RT at priority 5.
Feb 14 17:53:01 MM-Home rtkit-daemon[2399]: Supervising 3 threads of 1 processes of 1 users.
Feb 14 17:53:01 MM-Home rtkit-daemon[2399]: Supervising 3 threads of 1 processes of 1 users.
Feb 14 17:53:01 MM-Home rtkit-daemon[2399]: Successfully made thread 2405 of process 2398 (/usr/bin/pulseaudio) owned by 'marc' RT at priority 5.
Feb 14 17:53:01 MM-Home rtkit-daemon[2399]: Supervising 4 threads of 1 processes of 1 users.
Feb 14 17:53:01 MM-Home dbus[988]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Feb 14 17:53:01 MM-Home bluetoothd[2406]: Bluetooth daemon 5.35
Feb 14 17:53:01 MM-Home dbus[988]: [system] Successfully activated service 'org.bluez'
Feb 14 17:53:01 MM-Home bluetoothd[2406]: Starting SDP server
Feb 14 17:53:01 MM-Home kernel: Bluetooth: Core ver 2.20
Feb 14 17:53:01 MM-Home kernel: NET: Registered protocol family 31
Feb 14 17:53:01 MM-Home kernel: Bluetooth: HCI device and connection manager initialized
Feb 14 17:53:01 MM-Home kernel: Bluetooth: HCI socket layer initialized
Feb 14 17:53:01 MM-Home kernel: Bluetooth: L2CAP socket layer initialized
Feb 14 17:53:01 MM-Home kernel: Bluetooth: SCO socket layer initialized
Feb 14 17:53:01 MM-Home kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Feb 14 17:53:01 MM-Home kernel: Bluetooth: BNEP filters: protocol multicast
Feb 14 17:53:01 MM-Home kernel: Bluetooth: BNEP socket layer initialized
Feb 14 17:53:01 MM-Home dbus[988]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Feb 14 17:53:01 MM-Home bluetoothd[2406]: Bluetooth management interface 1.9 initialized
Feb 14 17:53:01 MM-Home dbus[988]: [system] Successfully activated service 'org.freedesktop.hostname1'
Feb 14 17:53:19 MM-Home dbus[988]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Feb 14 17:53:19 MM-Home org.kde.powerdevil.backlighthelper[988]: powerdevil: no kernel backlight interface found
Feb 14 17:53:19 MM-Home dbus[988]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Feb 14 17:53:24 MM-Home dbus[988]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service'
Feb 14 17:53:24 MM-Home PackageKit[2440]: daemon start
Feb 14 17:53:24 MM-Home dbus[988]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Feb 14 17:53:25 MM-Home PackageKit[2440]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 17:53:25 MM-Home PackageKit[2440]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 17:53:25 MM-Home PackageKit[2440]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 17:53:25 MM-Home PackageKit[2440]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 17:53:26 MM-Home PackageKit[2440]: refresh-cache transaction /1_aeadcced from uid 1000 finished with failed after 1415ms
Feb 14 17:53:27 MM-Home PackageKit[2440]: refresh-cache transaction /2_eecceaec from uid 1000 finished with failed after 286ms
Feb 14 17:53:27 MM-Home kernel: fuse init (API version 7.23)
Feb 14 17:53:44 MM-Home PackageKit[2440]: daemon quit
Feb 14 17:53:44 MM-Home packagekitd[2440]: (packagekitd:2440): GLib-CRITICAL **: Source ID 6 was not found when attempting to remove it
Feb 14 18:00:01 MM-Home cron[2666]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 18:00:01 MM-Home systemd[2667]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 18:00:01 MM-Home CRON[2666]: pam_unix(crond:session): session closed for user root
Feb 14 18:00:01 MM-Home systemd[2668]: pam_unix(systemd-user:session): session closed for user root
Feb 14 18:00:58 MM-Home polkitd[1092]: Unregistered Authentication Agent for unix-session:13 (system bus name :1.55, object path /org/kde/PolicyKit1/AuthenticationAgent, locale de_DE.UTF-8)
-- Reboot --
Feb 14 18:04:42 linux-ytaf systemd-journal[187]: Runtime journal is using 8.0M (max allowed 394.0M, trying to leave 591.0M free of 3.8G available → current limit 394.0M).
Feb 14 18:04:42 linux-ytaf systemd-journal[187]: Runtime journal is using 8.0M (max allowed 394.0M, trying to leave 591.0M free of 3.8G available → current limit 394.0M).
Feb 14 18:04:42 linux-ytaf kernel: microcode: CPU0 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 18:04:42 linux-ytaf kernel: Initializing cgroup subsys cpuset
Feb 14 18:04:42 linux-ytaf kernel: Initializing cgroup subsys cpu
Feb 14 18:04:42 linux-ytaf kernel: Initializing cgroup subsys cpuacct
Feb 14 18:04:42 linux-ytaf kernel: Linux version 4.1.15-8-default (geeko@buildhost) (gcc version 4.8.5 (SUSE Linux) ) #1 SMP PREEMPT Wed Jan 20 16:41:00 UTC 2016 (0e3b3ab)
Feb 14 18:04:42 linux-ytaf kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.1.15-8-default root=UUID=21024970-7a27-4114-8525-d8dd026f23b6 ro resume=/dev/sdb2 splash=silent quiet showopts
Feb 14 18:04:42 linux-ytaf kernel: e820: BIOS-provided physical RAM map:
Feb 14 18:04:42 linux-ytaf kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Feb 14 18:04:42 linux-ytaf kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
Feb 14 18:04:42 linux-ytaf kernel: BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable
Feb 14 18:04:42 linux-ytaf kernel: BIOS-e820: [mem 0x0000000020000000-0x00000000201fffff] reserved
Feb 14 18:04:42 linux-ytaf kernel: BIOS-e820: [mem 0x0000000020200000-0x000000003fffffff] usable
Feb 14 18:04:42 linux-ytaf kernel: BIOS-e820: [mem 0x0000000040000000-0x00000000401fffff] reserved
Feb 14 18:04:42 linux-ytaf kernel: BIOS-e820: [mem 0x0000000040200000-0x00000000ca38efff] usable
Feb 14 18:04:42 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ca38f000-0x00000000ca5f1fff] reserved
Feb 14 18:04:42 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ca5f2000-0x00000000ca679fff] ACPI NVS
Feb 14 18:04:42 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ca67a000-0x00000000ca93efff] reserved
Feb 14 18:04:42 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ca93f000-0x00000000cab83fff] ACPI NVS
Feb 14 18:04:42 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cab84000-0x00000000cab91fff] ACPI data
Feb 14 18:04:42 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cab92000-0x00000000cabbefff] ACPI NVS
Feb 14 18:04:42 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cabbf000-0x00000000cabc3fff] ACPI data
Feb 14 18:04:42 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cabc4000-0x00000000cac06fff] ACPI NVS
Feb 14 18:04:42 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cac07000-0x00000000caffffff] usable
Feb 14 18:04:42 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cb800000-0x00000000cf9fffff] reserved
Feb 14 18:04:42 linux-ytaf kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Feb 14 18:04:42 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Feb 14 18:04:42 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Feb 14 18:04:42 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Feb 14 18:04:42 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Feb 14 18:04:42 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Feb 14 18:04:42 linux-ytaf kernel: BIOS-e820: [mem 0x0000000100000000-0x000000022f5fffff] usable
Feb 14 18:04:42 linux-ytaf kernel: NX (Execute Disable) protection: active
Feb 14 18:04:42 linux-ytaf kernel: e820: update [mem 0x0c826018-0x0c835c57] usable ==> usable
Feb 14 18:04:42 linux-ytaf kernel: e820: update [mem 0x0c836018-0x0c846057] usable ==> usable
Feb 14 18:04:42 linux-ytaf kernel: e820: update [mem 0x0c847018-0x0c856857] usable ==> usable
Feb 14 18:04:42 linux-ytaf kernel: e820: update [mem 0x0c857018-0x0c85ae57] usable ==> usable
Feb 14 18:04:42 linux-ytaf kernel: extended physical RAM map:
Feb 14 18:04:42 linux-ytaf kernel: reserve setup_data: [mem 0x0000000000000000-0x000000000009efff] usable
Feb 14 18:04:42 linux-ytaf kernel: reserve setup_data: [mem 0x000000000009f000-0x000000000009ffff] reserved
Feb 14 18:04:42 linux-ytaf kernel: reserve setup_data: [mem 0x0000000000100000-0x000000000c826017] usable
Feb 14 18:04:42 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c826018-0x000000000c835c57] usable
Feb 14 18:04:42 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c835c58-0x000000000c836017] usable
Feb 14 18:04:42 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c836018-0x000000000c846057] usable
Feb 14 18:04:42 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c846058-0x000000000c847017] usable
Feb 14 18:04:42 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c847018-0x000000000c856857] usable
Feb 14 18:04:42 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c856858-0x000000000c857017] usable
Feb 14 18:04:42 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c857018-0x000000000c85ae57] usable
Feb 14 18:04:42 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c85ae58-0x000000001fffffff] usable
Feb 14 18:04:42 linux-ytaf kernel: reserve setup_data: [mem 0x0000000020000000-0x00000000201fffff] reserved
Feb 14 18:04:42 linux-ytaf kernel: reserve setup_data: [mem 0x0000000020200000-0x000000003fffffff] usable
Feb 14 18:04:42 linux-ytaf kernel: reserve setup_data: [mem 0x0000000040000000-0x00000000401fffff] reserved
Feb 14 18:04:42 linux-ytaf kernel: reserve setup_data: [mem 0x0000000040200000-0x00000000ca38efff] usable
Feb 14 18:04:42 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ca38f000-0x00000000ca5f1fff] reserved
Feb 14 18:04:42 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ca5f2000-0x00000000ca679fff] ACPI NVS
Feb 14 18:04:42 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ca67a000-0x00000000ca93efff] reserved
Feb 14 18:04:42 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ca93f000-0x00000000cab83fff] ACPI NVS
Feb 14 18:04:42 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cab84000-0x00000000cab91fff] ACPI data
Feb 14 18:04:42 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cab92000-0x00000000cabbefff] ACPI NVS
Feb 14 18:04:42 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cabbf000-0x00000000cabc3fff] ACPI data
Feb 14 18:04:42 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cabc4000-0x00000000cac06fff] ACPI NVS
Feb 14 18:04:42 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cac07000-0x00000000caffffff] usable
Feb 14 18:04:42 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cb800000-0x00000000cf9fffff] reserved
Feb 14 18:04:42 linux-ytaf kernel: reserve setup_data: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Feb 14 18:04:42 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Feb 14 18:04:42 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Feb 14 18:04:42 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Feb 14 18:04:42 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Feb 14 18:04:42 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Feb 14 18:04:42 linux-ytaf kernel: reserve setup_data: [mem 0x0000000100000000-0x000000022f5fffff] usable
Feb 14 18:04:42 linux-ytaf kernel: efi: EFI v2.31 by American Megatrends
Feb 14 18:04:42 linux-ytaf kernel: efi:  ACPI=0xcab84000  ACPI 2.0=0xcab84000  SMBIOS=0xca427e98  MPS=0xfc990 
Feb 14 18:04:42 linux-ytaf kernel: SMBIOS 2.6 present.
Feb 14 18:04:42 linux-ytaf kernel: DMI: System manufacturer System Product Name/MAXIMUS IV GENE-Z/GEN3, BIOS 3603 11/09/2012
Feb 14 18:04:42 linux-ytaf kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Feb 14 18:04:42 linux-ytaf kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Feb 14 18:04:42 linux-ytaf kernel: AGP: No AGP bridge found
Feb 14 18:04:42 linux-ytaf kernel: e820: last_pfn = 0x22f600 max_arch_pfn = 0x400000000
Feb 14 18:04:42 linux-ytaf kernel: MTRR default type: uncachable
Feb 14 18:04:42 linux-ytaf kernel: MTRR fixed ranges enabled:
Feb 14 18:04:42 linux-ytaf kernel:   00000-9FFFF write-back
Feb 14 18:04:42 linux-ytaf kernel:   A0000-BFFFF uncachable
Feb 14 18:04:42 linux-ytaf kernel:   C0000-D3FFF write-protect
Feb 14 18:04:42 linux-ytaf kernel:   D4000-DFFFF uncachable
Feb 14 18:04:42 linux-ytaf kernel:   E0000-E7FFF write-through
Feb 14 18:04:42 linux-ytaf kernel:   E8000-FFFFF write-protect
Feb 14 18:04:42 linux-ytaf kernel: MTRR variable ranges enabled:
Feb 14 18:04:42 linux-ytaf kernel:   0 base 000000000 mask E00000000 write-back
Feb 14 18:04:42 linux-ytaf kernel:   1 base 200000000 mask FE0000000 write-back
Feb 14 18:04:42 linux-ytaf kernel:   2 base 220000000 mask FF0000000 write-back
Feb 14 18:04:42 linux-ytaf kernel:   3 base 0E0000000 mask FE0000000 uncachable
Feb 14 18:04:42 linux-ytaf kernel:   4 base 0D0000000 mask FF0000000 uncachable
Feb 14 18:04:42 linux-ytaf kernel:   5 base 0CC000000 mask FFC000000 uncachable
Feb 14 18:04:42 linux-ytaf kernel:   6 base 0CB800000 mask FFF800000 uncachable
Feb 14 18:04:42 linux-ytaf kernel:   7 base 22F800000 mask FFF800000 uncachable
Feb 14 18:04:42 linux-ytaf kernel:   8 base 22F600000 mask FFFE00000 uncachable
Feb 14 18:04:42 linux-ytaf kernel:   9 disabled
Feb 14 18:04:42 linux-ytaf kernel: PAT configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- UC  
Feb 14 18:04:42 linux-ytaf kernel: e820: update [mem 0xcb800000-0xffffffff] usable ==> reserved
Feb 14 18:04:42 linux-ytaf kernel: e820: last_pfn = 0xcb000 max_arch_pfn = 0x400000000
Feb 14 18:04:42 linux-ytaf kernel: found SMP MP-table at [mem 0x000fcd30-0x000fcd3f] mapped at [ffff8800000fcd30]
Feb 14 18:04:42 linux-ytaf kernel: Scanning 1 areas for low memory corruption
Feb 14 18:04:42 linux-ytaf kernel: Base memory trampoline at [ffff880000097000] 97000 size 24576
Feb 14 18:04:42 linux-ytaf kernel: reserving inaccessible SNB gfx pages
Feb 14 18:04:42 linux-ytaf kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
Feb 14 18:04:42 linux-ytaf kernel:  [mem 0x00000000-0x000fffff] page 4k
Feb 14 18:04:42 linux-ytaf kernel: BRK [0x0e21a000, 0x0e21afff] PGTABLE
Feb 14 18:04:42 linux-ytaf kernel: BRK [0x0e21b000, 0x0e21bfff] PGTABLE
Feb 14 18:04:42 linux-ytaf kernel: BRK [0x0e21c000, 0x0e21cfff] PGTABLE
Feb 14 18:04:42 linux-ytaf kernel: init_memory_mapping: [mem 0x22f400000-0x22f5fffff]
Feb 14 18:04:42 linux-ytaf kernel:  [mem 0x22f400000-0x22f5fffff] page 2M
Feb 14 18:04:42 linux-ytaf kernel: BRK [0x0e21d000, 0x0e21dfff] PGTABLE
Feb 14 18:04:42 linux-ytaf kernel: init_memory_mapping: [mem 0x220000000-0x22f3fffff]
Feb 14 18:04:42 linux-ytaf kernel:  [mem 0x220000000-0x22f3fffff] page 2M
Feb 14 18:04:42 linux-ytaf kernel: init_memory_mapping: [mem 0x200000000-0x21fffffff]
Feb 14 18:04:42 linux-ytaf kernel:  [mem 0x200000000-0x21fffffff] page 2M
Feb 14 18:04:42 linux-ytaf kernel: init_memory_mapping: [mem 0x00100000-0x1fffffff]
Feb 14 18:04:42 linux-ytaf kernel:  [mem 0x00100000-0x001fffff] page 4k
Feb 14 18:04:42 linux-ytaf kernel:  [mem 0x00200000-0x1fffffff] page 2M
Feb 14 18:04:42 linux-ytaf kernel: init_memory_mapping: [mem 0x20200000-0x3fffffff]
Feb 14 18:04:42 linux-ytaf kernel:  [mem 0x20200000-0x3fffffff] page 2M
Feb 14 18:04:42 linux-ytaf kernel: init_memory_mapping: [mem 0x40200000-0xca38efff]
Feb 14 18:04:42 linux-ytaf kernel:  [mem 0x40200000-0xca1fffff] page 2M
Feb 14 18:04:42 linux-ytaf kernel:  [mem 0xca200000-0xca38efff] page 4k
Feb 14 18:04:42 linux-ytaf kernel: BRK [0x0e21e000, 0x0e21efff] PGTABLE
Feb 14 18:04:42 linux-ytaf kernel: BRK [0x0e21f000, 0x0e21ffff] PGTABLE
Feb 14 18:04:42 linux-ytaf kernel: init_memory_mapping: [mem 0xcac07000-0xcaffffff]
Feb 14 18:04:42 linux-ytaf kernel:  [mem 0xcac07000-0xcadfffff] page 4k
Feb 14 18:04:42 linux-ytaf kernel:  [mem 0xcae00000-0xcaffffff] page 2M
Feb 14 18:04:42 linux-ytaf kernel: init_memory_mapping: [mem 0x100000000-0x1ffffffff]
Feb 14 18:04:42 linux-ytaf kernel:  [mem 0x100000000-0x1ffffffff] page 2M
Feb 14 18:04:42 linux-ytaf kernel: RAMDISK: [mem 0x00457000-0x00ffafff]
Feb 14 18:04:42 linux-ytaf kernel: ACPI: Early table checksum verification disabled
Feb 14 18:04:42 linux-ytaf kernel: ACPI: RSDP 0x00000000CAB84000 000024 (v02 ALASKA)
Feb 14 18:04:42 linux-ytaf kernel: ACPI: XSDT 0x00000000CAB84078 000064 (v01 ALASKA A M I    01072009 AMI  00010013)
Feb 14 18:04:42 linux-ytaf kernel: ACPI: FACP 0x00000000CAB8FC78 0000F4 (v04 ALASKA A M I    01072009 AMI  00010013)
Feb 14 18:04:42 linux-ytaf kernel: ACPI: DSDT 0x00000000CAB84170 00BB02 (v02 ALASKA A M I    00000015 INTL 20051117)
Feb 14 18:04:42 linux-ytaf kernel: ACPI: FACS 0x00000000CABBDF80 000040
Feb 14 18:04:42 linux-ytaf kernel: ACPI: APIC 0x00000000CAB8FD70 000092 (v03 ALASKA A M I    01072009 AMI  00010013)
Feb 14 18:04:42 linux-ytaf kernel: ACPI: MCFG 0x00000000CAB8FE08 00003C (v01 ALASKA A M I    01072009 MSFT 00000097)
Feb 14 18:04:42 linux-ytaf kernel: ACPI: HPET 0x00000000CAB8FE48 000038 (v01 ALASKA A M I    01072009 AMI. 00000005)
Feb 14 18:04:42 linux-ytaf kernel: ACPI: SSDT 0x00000000CAB8FE80 00036D (v01 SataRe SataTabl 00001000 INTL 20091112)
Feb 14 18:04:42 linux-ytaf kernel: ACPI: SSDT 0x00000000CAB901F0 0009AA (v01 PmRef  Cpu0Ist  00003000 INTL 20051117)
Feb 14 18:04:42 linux-ytaf kernel: ACPI: SSDT 0x00000000CAB90BA0 000A92 (v01 PmRef  CpuPm    00003000 INTL 20051117)
Feb 14 18:04:42 linux-ytaf kernel: ACPI: BGRT 0x00000000CAB91690 000038 (v00 ALASKA A M I    01072009 AMI  00010013)
Feb 14 18:04:42 linux-ytaf kernel: ACPI: Local APIC address 0xfee00000
Feb 14 18:04:42 linux-ytaf kernel: No NUMA configuration found
Feb 14 18:04:42 linux-ytaf kernel: Faking a node at [mem 0x0000000000000000-0x000000022f5fffff]
Feb 14 18:04:42 linux-ytaf kernel: NODE_DATA(0) allocated [mem 0x22f5e5000-0x22f5f8fff]
Feb 14 18:04:42 linux-ytaf kernel:  [ffffea0000000000-ffffea0008bfffff] PMD -> [ffff880226c00000-ffff88022ebfffff] on node 0
Feb 14 18:04:42 linux-ytaf kernel: Zone ranges:
Feb 14 18:04:42 linux-ytaf kernel:   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
Feb 14 18:04:42 linux-ytaf kernel:   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
Feb 14 18:04:42 linux-ytaf kernel:   Normal   [mem 0x0000000100000000-0x000000022f5fffff]
Feb 14 18:04:42 linux-ytaf kernel: Movable zone start for each node
Feb 14 18:04:42 linux-ytaf kernel: Early memory node ranges
Feb 14 18:04:42 linux-ytaf kernel:   node   0: [mem 0x0000000000001000-0x000000000009efff]
Feb 14 18:04:42 linux-ytaf kernel:   node   0: [mem 0x0000000000100000-0x000000001fffffff]
Feb 14 18:04:42 linux-ytaf kernel:   node   0: [mem 0x0000000020200000-0x000000003fffffff]
Feb 14 18:04:42 linux-ytaf kernel:   node   0: [mem 0x0000000040200000-0x00000000ca38efff]
Feb 14 18:04:42 linux-ytaf kernel:   node   0: [mem 0x00000000cac07000-0x00000000caffffff]
Feb 14 18:04:42 linux-ytaf kernel:   node   0: [mem 0x0000000100000000-0x000000022f5fffff]
Feb 14 18:04:42 linux-ytaf kernel: Initmem setup node 0 [mem 0x0000000000001000-0x000000022f5fffff]
Feb 14 18:04:42 linux-ytaf kernel: On node 0 totalpages: 2070822
Feb 14 18:04:42 linux-ytaf kernel:   DMA zone: 64 pages used for memmap
Feb 14 18:04:42 linux-ytaf kernel:   DMA zone: 3138 pages reserved
Feb 14 18:04:42 linux-ytaf kernel:   DMA zone: 3998 pages, LIFO batch:0
Feb 14 18:04:42 linux-ytaf kernel:   DMA32 zone: 12879 pages used for memmap
Feb 14 18:04:42 linux-ytaf kernel:   DMA32 zone: 824200 pages, LIFO batch:31
Feb 14 18:04:42 linux-ytaf kernel:   Normal zone: 19416 pages used for memmap
Feb 14 18:04:42 linux-ytaf kernel:   Normal zone: 1242624 pages, LIFO batch:31
Feb 14 18:04:42 linux-ytaf kernel: tboot: non-0 tboot_addr but it is not of type E820_RESERVED
Feb 14 18:04:42 linux-ytaf kernel: ACPI: PM-Timer IO Port: 0x408
Feb 14 18:04:42 linux-ytaf kernel: ACPI: Local APIC address 0xfee00000
Feb 14 18:04:42 linux-ytaf kernel: ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
Feb 14 18:04:42 linux-ytaf kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
Feb 14 18:04:42 linux-ytaf kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Feb 14 18:04:42 linux-ytaf kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Feb 14 18:04:42 linux-ytaf kernel: ACPI: IRQ0 used by override.
Feb 14 18:04:42 linux-ytaf kernel: ACPI: IRQ9 used by override.
Feb 14 18:04:42 linux-ytaf kernel: Using ACPI (MADT) for SMP configuration information
Feb 14 18:04:42 linux-ytaf kernel: ACPI: HPET id: 0x8086a701 base: 0xfed00000
Feb 14 18:04:42 linux-ytaf kernel: smpboot: Allowing 8 CPUs, 0 hotplug CPUs
Feb 14 18:04:42 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
Feb 14 18:04:42 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Feb 14 18:04:42 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000fffff]
Feb 14 18:04:42 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c826000-0x0c826fff]
Feb 14 18:04:42 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c835000-0x0c835fff]
Feb 14 18:04:42 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c836000-0x0c836fff]
Feb 14 18:04:42 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c846000-0x0c846fff]
Feb 14 18:04:42 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c847000-0x0c847fff]
Feb 14 18:04:42 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c856000-0x0c856fff]
Feb 14 18:04:42 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c857000-0x0c857fff]
Feb 14 18:04:42 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c85a000-0x0c85afff]
Feb 14 18:04:42 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x20000000-0x201fffff]
Feb 14 18:04:42 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x40000000-0x401fffff]
Feb 14 18:04:42 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xca38f000-0xca5f1fff]
Feb 14 18:04:42 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xca5f2000-0xca679fff]
Feb 14 18:04:42 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xca67a000-0xca93efff]
Feb 14 18:04:42 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xca93f000-0xcab83fff]
Feb 14 18:04:42 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcab84000-0xcab91fff]
Feb 14 18:04:42 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcab92000-0xcabbefff]
Feb 14 18:04:42 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcabbf000-0xcabc3fff]
Feb 14 18:04:42 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcabc4000-0xcac06fff]
Feb 14 18:04:42 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcb000000-0xcb7fffff]
Feb 14 18:04:42 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcb800000-0xcf9fffff]
Feb 14 18:04:42 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcfa00000-0xf7ffffff]
Feb 14 18:04:42 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
Feb 14 18:04:42 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfc000000-0xfebfffff]
Feb 14 18:04:42 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
Feb 14 18:04:42 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfec01000-0xfecfffff]
Feb 14 18:04:42 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed00000-0xfed03fff]
Feb 14 18:04:42 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed04000-0xfed1bfff]
Feb 14 18:04:42 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Feb 14 18:04:42 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed20000-0xfedfffff]
Feb 14 18:04:42 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
Feb 14 18:04:42 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfee01000-0xfeffffff]
Feb 14 18:04:42 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Feb 14 18:04:42 linux-ytaf kernel: e820: [mem 0xcfa00000-0xf7ffffff] available for PCI devices
Feb 14 18:04:42 linux-ytaf kernel: Booting paravirtualized kernel on bare hardware
Feb 14 18:04:42 linux-ytaf kernel: clocksource refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
Feb 14 18:04:42 linux-ytaf kernel: setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:8 nr_node_ids:1
Feb 14 18:04:42 linux-ytaf kernel: PERCPU: Embedded 33 pages/cpu @ffff88022f200000 s97368 r8192 d29608 u262144
Feb 14 18:04:42 linux-ytaf kernel: pcpu-alloc: s97368 r8192 d29608 u262144 alloc=1*2097152
Feb 14 18:04:42 linux-ytaf kernel: pcpu-alloc: [0] 0 1 2 3 4 5 6 7 
Feb 14 18:04:42 linux-ytaf kernel: Built 1 zonelists in Node order, mobility grouping on.  Total pages: 2035325
Feb 14 18:04:42 linux-ytaf kernel: Policy zone: Normal
Feb 14 18:04:42 linux-ytaf kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.1.15-8-default root=UUID=21024970-7a27-4114-8525-d8dd026f23b6 ro resume=/dev/sdb2 splash=silent quiet showopts
Feb 14 18:04:42 linux-ytaf kernel: log_buf_len individual max cpu contribution: 32768 bytes
Feb 14 18:04:42 linux-ytaf kernel: log_buf_len total cpu_extra contributions: 229376 bytes
Feb 14 18:04:42 linux-ytaf kernel: log_buf_len min size: 262144 bytes
Feb 14 18:04:42 linux-ytaf kernel: log_buf_len: 524288 bytes
Feb 14 18:04:42 linux-ytaf kernel: early log buf free: 245492(93%)
Feb 14 18:04:42 linux-ytaf kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
Feb 14 18:04:42 linux-ytaf kernel: xsave: enabled xstate_bv 0x7, cntxt size 0x340 using standard form
Feb 14 18:04:42 linux-ytaf kernel: AGP: Checking aperture...
Feb 14 18:04:42 linux-ytaf kernel: AGP: No AGP bridge found
Feb 14 18:04:42 linux-ytaf kernel: Memory: 7863196K/8283288K available (6547K kernel code, 1084K rwdata, 4848K rodata, 1560K init, 1516K bss, 420092K reserved, 0K cma-reserved)
Feb 14 18:04:42 linux-ytaf kernel: Preemptible hierarchical RCU implementation.
Feb 14 18:04:42 linux-ytaf kernel:         RCU dyntick-idle grace-period acceleration is enabled.
Feb 14 18:04:42 linux-ytaf kernel:         RCU restricting CPUs from NR_CPUS=512 to nr_cpu_ids=8.
Feb 14 18:04:42 linux-ytaf kernel: RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
Feb 14 18:04:42 linux-ytaf kernel: NR_IRQS:33024 nr_irqs:488 16
Feb 14 18:04:42 linux-ytaf kernel:         Offload RCU callbacks from all CPUs
Feb 14 18:04:42 linux-ytaf kernel:         Offload RCU callbacks from CPUs: 0-7.
Feb 14 18:04:42 linux-ytaf kernel: Console: colour dummy device 80x25
Feb 14 18:04:42 linux-ytaf kernel: console [tty0] enabled
Feb 14 18:04:42 linux-ytaf kernel: clocksource hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484882848 ns
Feb 14 18:04:42 linux-ytaf kernel: hpet clockevent registered
Feb 14 18:04:42 linux-ytaf kernel: tsc: Fast TSC calibration using PIT
Feb 14 18:04:42 linux-ytaf kernel: tsc: Detected 3411.092 MHz processor
Feb 14 18:04:42 linux-ytaf kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 6822.18 BogoMIPS (lpj=13644368)
Feb 14 18:04:42 linux-ytaf kernel: pid_max: default: 32768 minimum: 301
Feb 14 18:04:42 linux-ytaf kernel: ACPI: Core revision 20150410
Feb 14 18:04:42 linux-ytaf kernel: ACPI: All ACPI Tables successfully acquired
Feb 14 18:04:42 linux-ytaf kernel: Security Framework initialized
Feb 14 18:04:42 linux-ytaf kernel: AppArmor: AppArmor initialized
Feb 14 18:04:42 linux-ytaf kernel: Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
Feb 14 18:04:42 linux-ytaf kernel: Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
Feb 14 18:04:42 linux-ytaf kernel: Mount-cache hash table entries: 16384 (order: 5, 131072 bytes)
Feb 14 18:04:42 linux-ytaf kernel: Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes)
Feb 14 18:04:42 linux-ytaf kernel: Initializing cgroup subsys blkio
Feb 14 18:04:42 linux-ytaf kernel: Initializing cgroup subsys memory
Feb 14 18:04:42 linux-ytaf kernel: Initializing cgroup subsys devices
Feb 14 18:04:42 linux-ytaf kernel: Initializing cgroup subsys freezer
Feb 14 18:04:42 linux-ytaf kernel: Initializing cgroup subsys net_cls
Feb 14 18:04:42 linux-ytaf kernel: Initializing cgroup subsys perf_event
Feb 14 18:04:42 linux-ytaf kernel: Initializing cgroup subsys net_prio
Feb 14 18:04:42 linux-ytaf kernel: Initializing cgroup subsys hugetlb
Feb 14 18:04:42 linux-ytaf kernel: CPU: Physical Processor ID: 0
Feb 14 18:04:42 linux-ytaf kernel: CPU: Processor Core ID: 0
Feb 14 18:04:42 linux-ytaf kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Feb 14 18:04:42 linux-ytaf kernel: ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Feb 14 18:04:42 linux-ytaf kernel: mce: CPU supports 9 MCE banks
Feb 14 18:04:42 linux-ytaf kernel: CPU0: Thermal monitoring enabled (TM1)
Feb 14 18:04:42 linux-ytaf kernel: process: using mwait in idle threads
Feb 14 18:04:42 linux-ytaf kernel: Last level iTLB entries: 4KB 512, 2MB 8, 4MB 8
Feb 14 18:04:42 linux-ytaf kernel: Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32, 1GB 0
Feb 14 18:04:42 linux-ytaf kernel: Freeing SMP alternatives memory: 24K (ffffffff82097000 - ffffffff8209d000)
Feb 14 18:04:42 linux-ytaf kernel: ftrace: allocating 25000 entries in 98 pages
Feb 14 18:04:42 linux-ytaf kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Feb 14 18:04:42 linux-ytaf kernel: TSC deadline timer enabled
Feb 14 18:04:42 linux-ytaf kernel: smpboot: CPU0: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz (fam: 06, model: 2a, stepping: 07)
Feb 14 18:04:42 linux-ytaf kernel: Performance Events: PEBS fmt1+, 16-deep LBR, SandyBridge events, full-width counters, Intel PMU driver.
Feb 14 18:04:42 linux-ytaf kernel: ... version:                3
Feb 14 18:04:42 linux-ytaf kernel: ... bit width:              48
Feb 14 18:04:42 linux-ytaf kernel: ... generic registers:      4
Feb 14 18:04:42 linux-ytaf kernel: ... value mask:             0000ffffffffffff
Feb 14 18:04:42 linux-ytaf kernel: ... max period:             0000ffffffffffff
Feb 14 18:04:42 linux-ytaf kernel: ... fixed-purpose events:   3
Feb 14 18:04:42 linux-ytaf kernel: ... event mask:             000000070000000f
Feb 14 18:04:42 linux-ytaf kernel: x86: Booting SMP configuration:
Feb 14 18:04:42 linux-ytaf kernel: .... node  #0, CPUs:      #1
Feb 14 18:04:42 linux-ytaf kernel: microcode: CPU1 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 18:04:42 linux-ytaf kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Feb 14 18:04:42 linux-ytaf kernel:  #2
Feb 14 18:04:42 linux-ytaf kernel: microcode: CPU2 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 18:04:42 linux-ytaf kernel:  #3
Feb 14 18:04:42 linux-ytaf kernel: microcode: CPU3 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 18:04:42 linux-ytaf kernel:  #4 #5 #6 #7
Feb 14 18:04:42 linux-ytaf kernel: x86: Booted up 1 node, 8 CPUs
Feb 14 18:04:42 linux-ytaf kernel: smpboot: Total of 8 processors activated (54577.47 BogoMIPS)
Feb 14 18:04:42 linux-ytaf kernel: devtmpfs: initialized
Feb 14 18:04:42 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xca5f2000-0xca679fff] (557056 bytes)
Feb 14 18:04:42 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xca93f000-0xcab83fff] (2379776 bytes)
Feb 14 18:04:42 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xcab92000-0xcabbefff] (184320 bytes)
Feb 14 18:04:42 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xcabc4000-0xcac06fff] (274432 bytes)
Feb 14 18:04:42 linux-ytaf kernel: clocksource jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
Feb 14 18:04:42 linux-ytaf kernel: pinctrl core: initialized pinctrl subsystem
Feb 14 18:04:42 linux-ytaf kernel: RTC time: 18:04:39, date: 02/14/16
Feb 14 18:04:42 linux-ytaf kernel: NET: Registered protocol family 16
Feb 14 18:04:42 linux-ytaf kernel: cpuidle: using governor ladder
Feb 14 18:04:42 linux-ytaf kernel: cpuidle: using governor menu
Feb 14 18:04:42 linux-ytaf kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
Feb 14 18:04:42 linux-ytaf kernel: ACPI: bus type PCI registered
Feb 14 18:04:42 linux-ytaf kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Feb 14 18:04:42 linux-ytaf kernel: PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
Feb 14 18:04:42 linux-ytaf kernel: PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
Feb 14 18:04:42 linux-ytaf kernel: PCI: Using configuration type 1 for base access
Feb 14 18:04:42 linux-ytaf kernel: perf_event_intel: PMU erratum BJ122, BV98, HSD29 worked around, HT is on
Feb 14 18:04:42 linux-ytaf kernel: ACPI: Added _OSI(Module Device)
Feb 14 18:04:42 linux-ytaf kernel: ACPI: Added _OSI(Processor Device)
Feb 14 18:04:42 linux-ytaf kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
Feb 14 18:04:42 linux-ytaf kernel: ACPI: Added _OSI(Processor Aggregator Device)
Feb 14 18:04:42 linux-ytaf kernel: ACPI: Executed 1 blocks of module-level executable AML code
Feb 14 18:04:42 linux-ytaf kernel: ACPI: Dynamic OEM Table Load:
Feb 14 18:04:42 linux-ytaf kernel: ACPI: SSDT 0xFFFF8802257C7000 00083B (v01 PmRef  Cpu0Cst  00003001 INTL 20051117)
Feb 14 18:04:42 linux-ytaf kernel: ACPI: Dynamic OEM Table Load:
Feb 14 18:04:42 linux-ytaf kernel: ACPI: SSDT 0xFFFF8802257C1400 000303 (v01 PmRef  ApIst    00003000 INTL 20051117)
Feb 14 18:04:42 linux-ytaf kernel: ACPI: Dynamic OEM Table Load:
Feb 14 18:04:42 linux-ytaf kernel: ACPI: SSDT 0xFFFF880225774600 000119 (v01 PmRef  ApCst    00003000 INTL 20051117)
Feb 14 18:04:42 linux-ytaf kernel: ACPI : EC: EC started
Feb 14 18:04:42 linux-ytaf kernel: ACPI: Interpreter enabled
Feb 14 18:04:42 linux-ytaf kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20150410/hwxface-580)
Feb 14 18:04:42 linux-ytaf kernel: ACPI: (supports S0 S1 S3 S4 S5)
Feb 14 18:04:42 linux-ytaf kernel: ACPI: Using IOAPIC for interrupt routing
Feb 14 18:04:42 linux-ytaf kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Feb 14 18:04:42 linux-ytaf kernel: ACPI: Power Resource [FN00] (off)
Feb 14 18:04:42 linux-ytaf kernel: ACPI: Power Resource [FN01] (off)
Feb 14 18:04:42 linux-ytaf kernel: ACPI: Power Resource [FN02] (off)
Feb 14 18:04:42 linux-ytaf kernel: ACPI: Power Resource [FN03] (off)
Feb 14 18:04:42 linux-ytaf kernel: ACPI: Power Resource [FN04] (off)
Feb 14 18:04:42 linux-ytaf kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
Feb 14 18:04:42 linux-ytaf kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Feb 14 18:04:42 linux-ytaf kernel: \_SB_.PCI0:_OSC invalid UUID
Feb 14 18:04:42 linux-ytaf kernel: _OSC request data:1 1f 0 
Feb 14 18:04:42 linux-ytaf kernel: acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
Feb 14 18:04:42 linux-ytaf kernel: PCI host bridge to bus 0000:00
Feb 14 18:04:42 linux-ytaf kernel: pci_bus 0000:00: root bus resource [bus 00-3e]
Feb 14 18:04:42 linux-ytaf kernel: pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
Feb 14 18:04:42 linux-ytaf kernel: pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
Feb 14 18:04:42 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
Feb 14 18:04:42 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff window]
Feb 14 18:04:42 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff window]
Feb 14 18:04:42 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff window]
Feb 14 18:04:42 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0xcfa00000-0xfeafffff window]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:00.0: [8086:0100] type 00 class 0x060000
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:01.0: [8086:0101] type 01 class 0x060400
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:01.0: System wakeup disabled by ACPI
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:01.1: [8086:0105] type 01 class 0x060400
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:01.1: PME# supported from D0 D3hot D3cold
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:01.1: System wakeup disabled by ACPI
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:02.0: [8086:0122] type 00 class 0x038000
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:02.0: reg 0x10: [mem 0xf7400000-0xf77fffff 64bit]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:02.0: reg 0x18: [mem 0xd0000000-0xdfffffff 64bit pref]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:02.0: reg 0x20: [io  0xf000-0xf03f]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:16.0: [8086:1c3a] type 00 class 0x078000
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:16.0: reg 0x10: [mem 0xf7b2c000-0xf7b2c00f 64bit]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:19.0: [8086:1503] type 00 class 0x020000
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:19.0: reg 0x10: [mem 0xf7b00000-0xf7b1ffff]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:19.0: reg 0x14: [mem 0xf7b29000-0xf7b29fff]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:19.0: reg 0x18: [io  0xf080-0xf09f]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:19.0: PME# supported from D0 D3hot D3cold
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:19.0: System wakeup disabled by ACPI
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1a.0: [8086:1c2d] type 00 class 0x0c0320
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1a.0: reg 0x10: [mem 0xf7b28000-0xf7b283ff]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1a.0: System wakeup disabled by ACPI
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1b.0: [8086:1c20] type 00 class 0x040300
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1b.0: reg 0x10: [mem 0xf7b20000-0xf7b23fff 64bit]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1b.0: System wakeup disabled by ACPI
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.0: [8086:1c10] type 01 class 0x060400
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.0: System wakeup disabled by ACPI
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.4: [8086:1c18] type 01 class 0x060400
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.4: System wakeup disabled by ACPI
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.5: [8086:1c1a] type 01 class 0x060400
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.5: System wakeup disabled by ACPI
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.6: [8086:1c1c] type 01 class 0x060400
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.6: PME# supported from D0 D3hot D3cold
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.6: System wakeup disabled by ACPI
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1d.0: [8086:1c26] type 00 class 0x0c0320
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1d.0: reg 0x10: [mem 0xf7b27000-0xf7b273ff]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1d.0: System wakeup disabled by ACPI
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1f.0: [8086:1c44] type 00 class 0x060100
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1f.2: [8086:1c02] type 00 class 0x010601
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x10: [io  0xf0d0-0xf0d7]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x14: [io  0xf0c0-0xf0c3]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x18: [io  0xf0b0-0xf0b7]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x1c: [io  0xf0a0-0xf0a3]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x20: [io  0xf060-0xf07f]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x24: [mem 0xf7b26000-0xf7b267ff]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1f.2: PME# supported from D3hot
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1f.3: [8086:1c22] type 00 class 0x0c0500
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1f.3: reg 0x10: [mem 0xf7b25000-0xf7b250ff 64bit]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1f.3: reg 0x20: [io  0x0580-0x059f]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:02:00.0: [10de:1183] type 00 class 0x030000
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:02:00.0: reg 0x10: [mem 0xf6000000-0xf6ffffff]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:02:00.0: reg 0x14: [mem 0xe0000000-0xe7ffffff 64bit pref]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:02:00.0: reg 0x1c: [mem 0xe8000000-0xe9ffffff 64bit pref]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:02:00.0: reg 0x24: [io  0xe000-0xe07f]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:02:00.0: reg 0x30: [mem 0xf7000000-0xf707ffff pref]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:02:00.1: [10de:0e0a] type 00 class 0x040300
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:02:00.1: reg 0x10: [mem 0xf7080000-0xf7083fff]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:01.1: PCI bridge to [bus 02]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [io  0xe000-0xefff]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xf6000000-0xf70fffff]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xe0000000-0xe9ffffff 64bit pref]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.0: PCI bridge to [bus 03]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:04:00.0: [1b21:1042] type 00 class 0x0c0330
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:04:00.0: reg 0x10: [mem 0xf7a00000-0xf7a07fff 64bit]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:04:00.0: PME# supported from D3hot D3cold
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:04:00.0: System wakeup disabled by ACPI
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.4: PCI bridge to [bus 04]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.4:   bridge window [mem 0xf7a00000-0xf7afffff]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:05:00.0: [1b21:1042] type 00 class 0x0c0330
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:05:00.0: reg 0x10: [mem 0xf7900000-0xf7907fff 64bit]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:05:00.0: PME# supported from D3hot D3cold
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:05:00.0: System wakeup disabled by ACPI
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.5: PCI bridge to [bus 05]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.5:   bridge window [mem 0xf7900000-0xf79fffff]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:06:00.0: [197b:2362] type 00 class 0x010185
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:06:00.0: reg 0x10: [io  0xd040-0xd047]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:06:00.0: reg 0x14: [io  0xd030-0xd033]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:06:00.0: reg 0x18: [io  0xd020-0xd027]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:06:00.0: reg 0x1c: [io  0xd010-0xd013]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:06:00.0: reg 0x20: [io  0xd000-0xd00f]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:06:00.0: reg 0x24: [mem 0xf7810000-0xf78101ff]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:06:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:06:00.0: PME# supported from D3hot
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:06:00.0: System wakeup disabled by ACPI
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.6: PCI bridge to [bus 06]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [io  0xd000-0xdfff]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [mem 0xf7800000-0xf78fffff]
Feb 14 18:04:42 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15)
Feb 14 18:04:42 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *10 11 12 14 15)
Feb 14 18:04:42 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Feb 14 18:04:42 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs *3 4 5 6 10 11 12 14 15)
Feb 14 18:04:42 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 *4 5 6 10 11 12 14 15)
Feb 14 18:04:42 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
Feb 14 18:04:42 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 *11 12 14 15)
Feb 14 18:04:42 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 *10 11 12 14 15)
Feb 14 18:04:42 linux-ytaf kernel: ACPI: Enabled 6 GPEs in block 00 to 3F
Feb 14 18:04:42 linux-ytaf kernel: ACPI : EC: GPE = 0x18, I/O: command/status = 0x66, data = 0x62
Feb 14 18:04:42 linux-ytaf kernel: vgaarb: setting as boot device: PCI:0000:02:00.0
Feb 14 18:04:42 linux-ytaf kernel: vgaarb: device added: PCI:0000:02:00.0,decodes=io+mem,owns=io+mem,locks=none
Feb 14 18:04:42 linux-ytaf kernel: vgaarb: loaded
Feb 14 18:04:42 linux-ytaf kernel: vgaarb: bridge control possible 0000:02:00.0
Feb 14 18:04:42 linux-ytaf kernel: SCSI subsystem initialized
Feb 14 18:04:42 linux-ytaf kernel: libata version 3.00 loaded.
Feb 14 18:04:42 linux-ytaf kernel: PCI: Using ACPI for IRQ routing
Feb 14 18:04:42 linux-ytaf kernel: PCI: pci_cache_line_size set to 64 bytes
Feb 14 18:04:42 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0009f000-0x0009ffff]
Feb 14 18:04:42 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c826018-0x0fffffff]
Feb 14 18:04:42 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c836018-0x0fffffff]
Feb 14 18:04:42 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c847018-0x0fffffff]
Feb 14 18:04:42 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c857018-0x0fffffff]
Feb 14 18:04:42 linux-ytaf kernel: e820: reserve RAM buffer [mem 0xca38f000-0xcbffffff]
Feb 14 18:04:42 linux-ytaf kernel: e820: reserve RAM buffer [mem 0xcb000000-0xcbffffff]
Feb 14 18:04:42 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x22f600000-0x22fffffff]
Feb 14 18:04:42 linux-ytaf kernel: NetLabel: Initializing
Feb 14 18:04:42 linux-ytaf kernel: NetLabel:  domain hash size = 128
Feb 14 18:04:42 linux-ytaf kernel: NetLabel:  protocols = UNLABELED CIPSOv4
Feb 14 18:04:42 linux-ytaf kernel: NetLabel:  unlabeled traffic allowed by default
Feb 14 18:04:42 linux-ytaf kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Feb 14 18:04:42 linux-ytaf kernel: hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Feb 14 18:04:42 linux-ytaf kernel: Switched to clocksource hpet
Feb 14 18:04:42 linux-ytaf kernel: AppArmor: AppArmor Filesystem Enabled
Feb 14 18:04:42 linux-ytaf kernel: pnp: PnP ACPI init
Feb 14 18:04:42 linux-ytaf kernel: system 00:00: [mem 0xfed40000-0xfed44fff] has been reserved
Feb 14 18:04:42 linux-ytaf kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
Feb 14 18:04:42 linux-ytaf kernel: system 00:01: [io  0x0680-0x069f] has been reserved
Feb 14 18:04:42 linux-ytaf kernel: system 00:01: [io  0x0200-0x020f] has been reserved
Feb 14 18:04:42 linux-ytaf kernel: system 00:01: [io  0xffff] has been reserved
Feb 14 18:04:42 linux-ytaf kernel: system 00:01: [io  0xffff] has been reserved
Feb 14 18:04:42 linux-ytaf kernel: system 00:01: [io  0x0400-0x0453] could not be reserved
Feb 14 18:04:42 linux-ytaf kernel: system 00:01: [io  0x0458-0x047f] has been reserved
Feb 14 18:04:42 linux-ytaf kernel: system 00:01: [io  0x0500-0x057f] has been reserved
Feb 14 18:04:42 linux-ytaf kernel: system 00:01: [io  0x164e-0x164f] has been reserved
Feb 14 18:04:42 linux-ytaf kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 18:04:42 linux-ytaf kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Feb 14 18:04:42 linux-ytaf kernel: system 00:03: [io  0x0454-0x0457] has been reserved
Feb 14 18:04:42 linux-ytaf kernel: system 00:03: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
Feb 14 18:04:42 linux-ytaf kernel: system 00:04: [io  0x0290-0x029f] has been reserved
Feb 14 18:04:42 linux-ytaf kernel: system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 18:04:42 linux-ytaf kernel: system 00:05: [io  0x04d0-0x04d1] has been reserved
Feb 14 18:04:42 linux-ytaf kernel: system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 18:04:42 linux-ytaf kernel: system 00:06: [mem 0xfed1c000-0xfed1ffff] has been reserved
Feb 14 18:04:42 linux-ytaf kernel: system 00:06: [mem 0xfed10000-0xfed17fff] has been reserved
Feb 14 18:04:42 linux-ytaf kernel: system 00:06: [mem 0xfed18000-0xfed18fff] has been reserved
Feb 14 18:04:42 linux-ytaf kernel: system 00:06: [mem 0xfed19000-0xfed19fff] has been reserved
Feb 14 18:04:42 linux-ytaf kernel: system 00:06: [mem 0xf8000000-0xfbffffff] has been reserved
Feb 14 18:04:42 linux-ytaf kernel: system 00:06: [mem 0xfed20000-0xfed3ffff] has been reserved
Feb 14 18:04:42 linux-ytaf kernel: system 00:06: [mem 0xfed90000-0xfed93fff] has been reserved
Feb 14 18:04:42 linux-ytaf kernel: system 00:06: [mem 0xfed45000-0xfed8ffff] has been reserved
Feb 14 18:04:42 linux-ytaf kernel: system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Feb 14 18:04:42 linux-ytaf kernel: system 00:06: [mem 0xfee00000-0xfeefffff] could not be reserved
Feb 14 18:04:42 linux-ytaf kernel: system 00:06: [mem 0xcfa00000-0xcfa00fff] has been reserved
Feb 14 18:04:42 linux-ytaf kernel: system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 18:04:42 linux-ytaf kernel: system 00:07: [mem 0x20000000-0x201fffff] has been reserved
Feb 14 18:04:42 linux-ytaf kernel: system 00:07: [mem 0x40000000-0x401fffff] has been reserved
Feb 14 18:04:42 linux-ytaf kernel: system 00:07: Plug and Play ACPI device, IDs PNP0c01 (active)
Feb 14 18:04:42 linux-ytaf kernel: pnp: PnP ACPI: found 8 devices
Feb 14 18:04:42 linux-ytaf kernel: clocksource acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.0: bridge window [io  0x1000-0x0fff] to [bus 03] add_size 1000
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 03] add_size 200000 add_align 100000
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff] to [bus 03] add_size 200000 add_align 100000
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.0: res[14]=[mem 0x00100000-0x000fffff] res_to_dev_res add_size 200000 min_align 100000
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.0: res[14]=[mem 0x00100000-0x002fffff] res_to_dev_res add_size 200000 min_align 100000
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x000fffff 64bit pref] res_to_dev_res add_size 200000 min_align 100000
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x002fffff 64bit pref] res_to_dev_res add_size 200000 min_align 100000
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.0: res[13]=[io  0x1000-0x0fff] res_to_dev_res add_size 1000 min_align 1000
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.0: res[13]=[io  0x1000-0x1fff] res_to_dev_res add_size 1000 min_align 1000
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.0: BAR 14: assigned [mem 0xcfb00000-0xcfcfffff]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.0: BAR 15: assigned [mem 0xcfd00000-0xcfefffff 64bit pref]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.0: BAR 13: assigned [io  0x2000-0x2fff]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:01.1: PCI bridge to [bus 02]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [io  0xe000-0xefff]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xf6000000-0xf70fffff]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xe0000000-0xe9ffffff 64bit pref]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.0: PCI bridge to [bus 03]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.0:   bridge window [io  0x2000-0x2fff]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.0:   bridge window [mem 0xcfb00000-0xcfcfffff]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.0:   bridge window [mem 0xcfd00000-0xcfefffff 64bit pref]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.4: PCI bridge to [bus 04]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.4:   bridge window [mem 0xf7a00000-0xf7afffff]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.5: PCI bridge to [bus 05]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.5:   bridge window [mem 0xf7900000-0xf79fffff]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:06:00.0: BAR 6: assigned [mem 0xf7800000-0xf780ffff pref]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.6: PCI bridge to [bus 06]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [io  0xd000-0xdfff]
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [mem 0xf7800000-0xf78fffff]
Feb 14 18:04:42 linux-ytaf kernel: pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
Feb 14 18:04:42 linux-ytaf kernel: pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
Feb 14 18:04:42 linux-ytaf kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
Feb 14 18:04:42 linux-ytaf kernel: pci_bus 0000:00: resource 7 [mem 0x000d4000-0x000d7fff window]
Feb 14 18:04:42 linux-ytaf kernel: pci_bus 0000:00: resource 8 [mem 0x000d8000-0x000dbfff window]
Feb 14 18:04:42 linux-ytaf kernel: pci_bus 0000:00: resource 9 [mem 0x000dc000-0x000dffff window]
Feb 14 18:04:42 linux-ytaf kernel: pci_bus 0000:00: resource 10 [mem 0xcfa00000-0xfeafffff window]
Feb 14 18:04:42 linux-ytaf kernel: pci_bus 0000:02: resource 0 [io  0xe000-0xefff]
Feb 14 18:04:42 linux-ytaf kernel: pci_bus 0000:02: resource 1 [mem 0xf6000000-0xf70fffff]
Feb 14 18:04:42 linux-ytaf kernel: pci_bus 0000:02: resource 2 [mem 0xe0000000-0xe9ffffff 64bit pref]
Feb 14 18:04:42 linux-ytaf kernel: pci_bus 0000:03: resource 0 [io  0x2000-0x2fff]
Feb 14 18:04:42 linux-ytaf kernel: pci_bus 0000:03: resource 1 [mem 0xcfb00000-0xcfcfffff]
Feb 14 18:04:42 linux-ytaf kernel: pci_bus 0000:03: resource 2 [mem 0xcfd00000-0xcfefffff 64bit pref]
Feb 14 18:04:42 linux-ytaf kernel: pci_bus 0000:04: resource 1 [mem 0xf7a00000-0xf7afffff]
Feb 14 18:04:42 linux-ytaf kernel: pci_bus 0000:05: resource 1 [mem 0xf7900000-0xf79fffff]
Feb 14 18:04:42 linux-ytaf kernel: pci_bus 0000:06: resource 0 [io  0xd000-0xdfff]
Feb 14 18:04:42 linux-ytaf kernel: pci_bus 0000:06: resource 1 [mem 0xf7800000-0xf78fffff]
Feb 14 18:04:42 linux-ytaf kernel: NET: Registered protocol family 2
Feb 14 18:04:42 linux-ytaf kernel: TCP established hash table entries: 65536 (order: 7, 524288 bytes)
Feb 14 18:04:42 linux-ytaf kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Feb 14 18:04:42 linux-ytaf kernel: TCP: Hash tables configured (established 65536 bind 65536)
Feb 14 18:04:42 linux-ytaf kernel: UDP hash table entries: 4096 (order: 5, 131072 bytes)
Feb 14 18:04:42 linux-ytaf kernel: UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
Feb 14 18:04:42 linux-ytaf kernel: NET: Registered protocol family 1
Feb 14 18:04:42 linux-ytaf kernel: pci 0000:02:00.0: Video device with shadowed ROM
Feb 14 18:04:42 linux-ytaf kernel: PCI: CLS 64 bytes, default 64
Feb 14 18:04:42 linux-ytaf kernel: Unpacking initramfs...
Feb 14 18:04:42 linux-ytaf kernel: Freeing initrd memory: 11920K (ffff880000457000 - ffff880000ffb000)
Feb 14 18:04:42 linux-ytaf kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Feb 14 18:04:42 linux-ytaf kernel: software IO TLB [mem 0xc638f000-0xca38f000] (64MB) mapped at [ffff8800c638f000-ffff8800ca38efff]
Feb 14 18:04:42 linux-ytaf kernel: RAPL PMU detected, API unit is 2^-32 Joules, 3 fixed counters 163840 ms ovfl timer
Feb 14 18:04:42 linux-ytaf kernel: hw unit of domain pp0-core 2^-16 Joules
Feb 14 18:04:42 linux-ytaf kernel: hw unit of domain package 2^-16 Joules
Feb 14 18:04:42 linux-ytaf kernel: hw unit of domain pp1-gpu 2^-16 Joules
Feb 14 18:04:42 linux-ytaf kernel: microcode: CPU0 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 18:04:42 linux-ytaf kernel: microcode: CPU1 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 18:04:42 linux-ytaf kernel: microcode: CPU2 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 18:04:42 linux-ytaf kernel: microcode: CPU3 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 18:04:42 linux-ytaf kernel: microcode: CPU4 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 18:04:42 linux-ytaf kernel: microcode: CPU5 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 18:04:42 linux-ytaf kernel: microcode: CPU6 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 18:04:42 linux-ytaf kernel: microcode: CPU7 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 18:04:42 linux-ytaf kernel: microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Feb 14 18:04:42 linux-ytaf kernel: Scanning for low memory corruption every 60 seconds
Feb 14 18:04:42 linux-ytaf kernel: futex hash table entries: 2048 (order: 5, 131072 bytes)
Feb 14 18:04:42 linux-ytaf kernel: audit: initializing netlink subsys (disabled)
Feb 14 18:04:42 linux-ytaf kernel: audit: type=2000 audit(1455473079.276:1): initialized
Feb 14 18:04:42 linux-ytaf kernel: HugeTLB registered 2 MB page size, pre-allocated 0 pages
Feb 14 18:04:42 linux-ytaf kernel: zpool: loaded
Feb 14 18:04:42 linux-ytaf kernel: zbud: loaded
Feb 14 18:04:42 linux-ytaf kernel: VFS: Disk quotas dquot_6.6.0
Feb 14 18:04:42 linux-ytaf kernel: VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Feb 14 18:04:42 linux-ytaf kernel: Key type big_key registered
Feb 14 18:04:42 linux-ytaf kernel: Key type asymmetric registered
Feb 14 18:04:42 linux-ytaf kernel: Asymmetric key parser 'x509' registered
Feb 14 18:04:42 linux-ytaf kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Feb 14 18:04:42 linux-ytaf kernel: io scheduler noop registered
Feb 14 18:04:42 linux-ytaf kernel: io scheduler deadline registered
Feb 14 18:04:42 linux-ytaf kernel: io scheduler cfq registered (default)
Feb 14 18:04:42 linux-ytaf kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Feb 14 18:04:42 linux-ytaf kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Feb 14 18:04:42 linux-ytaf kernel: efifb: probing for efifb
Feb 14 18:04:42 linux-ytaf kernel: efifb: framebuffer at 0xe9000000, mapped to 0xffffc90001000000, using 1876k, total 1875k
Feb 14 18:04:42 linux-ytaf kernel: efifb: mode is 800x600x32, linelength=3200, pages=1
Feb 14 18:04:42 linux-ytaf kernel: efifb: scrolling: redraw
Feb 14 18:04:42 linux-ytaf kernel: efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Feb 14 18:04:42 linux-ytaf kernel: Console: switching to colour frame buffer device 100x37
Feb 14 18:04:42 linux-ytaf kernel: fb0: EFI VGA frame buffer device
Feb 14 18:04:42 linux-ytaf kernel: intel_idle: MWAIT substates: 0x1120
Feb 14 18:04:42 linux-ytaf kernel: intel_idle: v0.4 model 0x2A
Feb 14 18:04:42 linux-ytaf kernel: intel_idle: lapic_timer_reliable_states 0xffffffff
Feb 14 18:04:42 linux-ytaf kernel: GHES: HEST is not enabled!
Feb 14 18:04:42 linux-ytaf kernel: Serial: 8250/16550 driver, 32 ports, IRQ sharing disabled
Feb 14 18:04:42 linux-ytaf kernel: Non-volatile memory driver v1.3
Feb 14 18:04:42 linux-ytaf kernel: Linux agpgart interface v0.103
Feb 14 18:04:42 linux-ytaf kernel: ahci 0000:00:1f.2: version 3.0
Feb 14 18:04:42 linux-ytaf kernel: ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x7 impl SATA mode
Feb 14 18:04:42 linux-ytaf kernel: ahci 0000:00:1f.2: flags: 64bit ncq led clo pio slum part ems apst 
Feb 14 18:04:42 linux-ytaf kernel: scsi host0: ahci
Feb 14 18:04:42 linux-ytaf kernel: scsi host1: ahci
Feb 14 18:04:42 linux-ytaf kernel: scsi host2: ahci
Feb 14 18:04:42 linux-ytaf kernel: scsi host3: ahci
Feb 14 18:04:42 linux-ytaf kernel: scsi host4: ahci
Feb 14 18:04:42 linux-ytaf kernel: scsi host5: ahci
Feb 14 18:04:42 linux-ytaf kernel: ata1: SATA max UDMA/133 abar m2048@0xf7b26000 port 0xf7b26100 irq 26
Feb 14 18:04:42 linux-ytaf kernel: ata2: SATA max UDMA/133 abar m2048@0xf7b26000 port 0xf7b26180 irq 26
Feb 14 18:04:42 linux-ytaf kernel: ata3: SATA max UDMA/133 abar m2048@0xf7b26000 port 0xf7b26200 irq 26
Feb 14 18:04:42 linux-ytaf kernel: ata4: DUMMY
Feb 14 18:04:42 linux-ytaf kernel: ata5: DUMMY
Feb 14 18:04:42 linux-ytaf kernel: ata6: DUMMY
Feb 14 18:04:42 linux-ytaf kernel: ahci 0000:06:00.0: AHCI 0001.0100 32 slots 2 ports 3 Gbps 0x3 impl SATA mode
Feb 14 18:04:42 linux-ytaf kernel: ahci 0000:06:00.0: flags: 64bit ncq pm led clo pmp pio slum part 
Feb 14 18:04:42 linux-ytaf kernel: scsi host6: ahci
Feb 14 18:04:42 linux-ytaf kernel: scsi host7: ahci
Feb 14 18:04:42 linux-ytaf kernel: ata7: SATA max UDMA/133 abar m512@0xf7810000 port 0xf7810100 irq 18
Feb 14 18:04:42 linux-ytaf kernel: ata8: SATA max UDMA/133 abar m512@0xf7810000 port 0xf7810180 irq 18
Feb 14 18:04:42 linux-ytaf kernel: i8042: PNP: No PS/2 controller found. Probing ports directly.
Feb 14 18:04:42 linux-ytaf kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Feb 14 18:04:42 linux-ytaf kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Feb 14 18:04:42 linux-ytaf kernel: mousedev: PS/2 mouse device common for all mice
Feb 14 18:04:42 linux-ytaf kernel: rtc_cmos 00:02: RTC can wake from S4
Feb 14 18:04:42 linux-ytaf kernel: rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Feb 14 18:04:42 linux-ytaf kernel: rtc_cmos 00:02: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
Feb 14 18:04:42 linux-ytaf kernel: Intel P-state driver initializing.
Feb 14 18:04:42 linux-ytaf kernel: ledtrig-cpu: registered to indicate activity on CPUs
Feb 14 18:04:42 linux-ytaf kernel: EFI Variables Facility v0.08 2004-May-17
Feb 14 18:04:42 linux-ytaf kernel: hidraw: raw HID events driver (C) Jiri Kosina
Feb 14 18:04:42 linux-ytaf kernel: NET: Registered protocol family 10
Feb 14 18:04:42 linux-ytaf kernel: registered taskstats version 1
Feb 14 18:04:42 linux-ytaf kernel: Key type encrypted registered
Feb 14 18:04:42 linux-ytaf kernel: AppArmor: AppArmor sha1 policy hashing enabled
Feb 14 18:04:42 linux-ytaf kernel:   Magic number: 4:449:89
Feb 14 18:04:42 linux-ytaf kernel: rtc_cmos 00:02: setting system clock to 2016-02-14 18:04:40 UTC (1455473080)
Feb 14 18:04:42 linux-ytaf kernel: PM: Checking hibernation image partition /dev/sdb2
Feb 14 18:04:42 linux-ytaf kernel: ata7: SATA link down (SStatus 0 SControl 300)
Feb 14 18:04:42 linux-ytaf kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Feb 14 18:04:42 linux-ytaf kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 14 18:04:42 linux-ytaf kernel: ata8: SATA link down (SStatus 0 SControl 300)
Feb 14 18:04:42 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 18:04:42 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff8802268b7dd8), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 18:04:42 linux-ytaf kernel: ata2.00: ATA-8: TOSHIBA HDWD110, MS2OA8J0, max UDMA/133
Feb 14 18:04:42 linux-ytaf kernel: ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Feb 14 18:04:42 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 18:04:42 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff8802268b7d60), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 18:04:42 linux-ytaf kernel: ata3.00: ATAPI: TSSTcorp CDDVDW SH-S223C, SB05, max MWDMA2
Feb 14 18:04:42 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 18:04:42 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff8802268b7dd8), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 18:04:42 linux-ytaf kernel: ata2.00: configured for UDMA/133
Feb 14 18:04:42 linux-ytaf kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 14 18:04:42 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 18:04:42 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff8802268b7e50), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 18:04:42 linux-ytaf kernel: ata1.00: ATA-9: SAMSUNG SSD 830 Series, CXM03B1Q, max UDMA/133
Feb 14 18:04:42 linux-ytaf kernel: ata1.00: 500118192 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Feb 14 18:04:42 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 18:04:42 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff8802268b7e50), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 18:04:42 linux-ytaf kernel: ata1.00: configured for UDMA/133
Feb 14 18:04:42 linux-ytaf kernel: scsi 0:0:0:0: Direct-Access     ATA      SAMSUNG SSD 830  3B1Q PQ: 0 ANSI: 5
Feb 14 18:04:42 linux-ytaf kernel: sd 0:0:0:0: [sda] 500118192 512-byte logical blocks: (256 GB/238 GiB)
Feb 14 18:04:42 linux-ytaf kernel: scsi 1:0:0:0: Direct-Access     ATA      TOSHIBA HDWD110  A8J0 PQ: 0 ANSI: 5
Feb 14 18:04:42 linux-ytaf kernel: sd 0:0:0:0: [sda] Write Protect is off
Feb 14 18:04:42 linux-ytaf kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 14 18:04:42 linux-ytaf kernel: sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
Feb 14 18:04:42 linux-ytaf kernel: sd 1:0:0:0: [sdb] 4096-byte physical blocks
Feb 14 18:04:42 linux-ytaf kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 14 18:04:42 linux-ytaf kernel: sd 1:0:0:0: [sdb] Write Protect is off
Feb 14 18:04:42 linux-ytaf kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Feb 14 18:04:42 linux-ytaf kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 14 18:04:42 linux-ytaf kernel:  sda: sda1 sda2 sda3 sda4
Feb 14 18:04:42 linux-ytaf kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Feb 14 18:04:42 linux-ytaf kernel:  sdb: sdb1 sdb2 sdb3 sdb4
Feb 14 18:04:42 linux-ytaf kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
Feb 14 18:04:42 linux-ytaf kernel: tsc: Refined TSC clocksource calibration: 3411.128 MHz
Feb 14 18:04:42 linux-ytaf kernel: clocksource tsc: mask: 0xffffffffffffffff max_cycles: 0x312b5ecadef, max_idle_ns: 440795307361 ns
Feb 14 18:04:42 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 18:04:42 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff8802268b7d60), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 18:04:42 linux-ytaf kernel: ata3.00: configured for PIO4
Feb 14 18:04:42 linux-ytaf kernel: scsi 2:0:0:0: CD-ROM            TSSTcorp CDDVDW SH-S223C  SB05 PQ: 0 ANSI: 5
Feb 14 18:04:42 linux-ytaf kernel: PM: Hibernation image partition 8:18 present
Feb 14 18:04:42 linux-ytaf kernel: PM: Looking for hibernation image.
Feb 14 18:04:42 linux-ytaf kernel: Switched to clocksource tsc
Feb 14 18:04:42 linux-ytaf kernel: PM: Image not found (code -22)
Feb 14 18:04:42 linux-ytaf kernel: PM: Hibernation image not present or could not be loaded.
Feb 14 18:04:42 linux-ytaf kernel: Freeing unused kernel memory: 1560K (ffffffff81f11000 - ffffffff82097000)
Feb 14 18:04:42 linux-ytaf kernel: Write protecting the kernel read-only data: 14336k
Feb 14 18:04:42 linux-ytaf kernel: Freeing unused kernel memory: 1632K (ffff88000d668000 - ffff88000d800000)
Feb 14 18:04:42 linux-ytaf kernel: Freeing unused kernel memory: 1296K (ffff88000dcbc000 - ffff88000de00000)
Feb 14 18:04:42 linux-ytaf systemd[1]: RTC configured in localtime, applying delta of 60 minutes to system time.
Feb 14 18:04:42 linux-ytaf kernel: random: systemd urandom read with 22 bits of entropy available
Feb 14 18:04:42 linux-ytaf kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Feb 14 18:04:42 linux-ytaf kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0
Feb 14 18:04:42 linux-ytaf kernel: scsi 2:0:0:0: Attached scsi generic sg2 type 5
Feb 14 18:04:42 linux-ytaf systemd-journal[187]: Journal started
Feb 14 18:04:42 linux-ytaf dracut-cmdline[181]: dracut-42.1 dracut-037-68.1
Feb 14 18:04:42 linux-ytaf systemd-udevd[250]: Network interface NamePolicy= disabled on kernel commandline, ignoring.
Feb 14 18:04:42 linux-ytaf kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3
Feb 14 18:04:42 linux-ytaf kernel: ACPI: Power Button [PWRB]
Feb 14 18:04:42 linux-ytaf kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
Feb 14 18:04:42 linux-ytaf kernel: ACPI: Power Button [PWRF]
Feb 14 18:04:42 linux-ytaf kernel: ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
Feb 14 18:04:42 linux-ytaf kernel: acpi device:58: registered as cooling_device0
Feb 14 18:04:42 linux-ytaf kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5
Feb 14 18:04:42 linux-ytaf kernel: wmi: Mapper loaded
Feb 14 18:04:42 linux-ytaf kernel: [drm] Initialized drm 1.1.0 20060810
Feb 14 18:04:42 linux-ytaf kernel: ACPI: bus type USB registered
Feb 14 18:04:42 linux-ytaf kernel: usbcore: registered new interface driver usbfs
Feb 14 18:04:42 linux-ytaf kernel: usbcore: registered new interface driver hub
Feb 14 18:04:42 linux-ytaf kernel: usbcore: registered new device driver usb
Feb 14 18:04:42 linux-ytaf kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Feb 14 18:04:42 linux-ytaf kernel: ehci-pci: EHCI PCI platform driver
Feb 14 18:04:42 linux-ytaf kernel: ehci-pci 0000:00:1a.0: EHCI Host Controller
Feb 14 18:04:42 linux-ytaf kernel: ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Feb 14 18:04:42 linux-ytaf kernel: ehci-pci 0000:00:1a.0: debug port 2
Feb 14 18:04:42 linux-ytaf kernel: ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Feb 14 18:04:42 linux-ytaf kernel: ehci-pci 0000:00:1a.0: irq 16, io mem 0xf7b28000
Feb 14 18:04:42 linux-ytaf kernel: sr 2:0:0:0: [sr0] scsi3-mmc drive: 52x/52x writer dvd-ram cd/rw xa/form2 cdda tray
Feb 14 18:04:42 linux-ytaf kernel: cdrom: Uniform CD-ROM driver Revision: 3.20
Feb 14 18:04:42 linux-ytaf kernel: sr 2:0:0:0: Attached scsi CD-ROM sr0
Feb 14 18:04:42 linux-ytaf kernel: ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Feb 14 18:04:42 linux-ytaf kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 18:04:42 linux-ytaf kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 18:04:42 linux-ytaf kernel: usb usb1: Product: EHCI Host Controller
Feb 14 18:04:42 linux-ytaf kernel: usb usb1: Manufacturer: Linux 4.1.15-8-default ehci_hcd
Feb 14 18:04:42 linux-ytaf kernel: usb usb1: SerialNumber: 0000:00:1a.0
Feb 14 18:04:42 linux-ytaf kernel: hub 1-0:1.0: USB hub found
Feb 14 18:04:42 linux-ytaf kernel: hub 1-0:1.0: 2 ports detected
Feb 14 18:04:42 linux-ytaf kernel: xhci_hcd 0000:04:00.0: xHCI Host Controller
Feb 14 18:04:42 linux-ytaf kernel: xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 2
Feb 14 18:04:42 linux-ytaf kernel: MXM: GUID detected in BIOS
Feb 14 18:04:42 linux-ytaf kernel: checking generic (e9000000 1d5000) vs hw (e0000000 8000000)
Feb 14 18:04:42 linux-ytaf kernel: checking generic (e9000000 1d5000) vs hw (e8000000 2000000)
Feb 14 18:04:42 linux-ytaf kernel: fb: switching to nouveaufb from EFI VGA
Feb 14 18:04:42 linux-ytaf kernel: Console: switching to colour dummy device 80x25
Feb 14 18:04:42 linux-ytaf kernel: nouveau  [  DEVICE][0000:02:00.0] BOOT0  : 0x0e4030a2
Feb 14 18:04:42 linux-ytaf kernel: nouveau  [  DEVICE][0000:02:00.0] Chipset: GK104 (NVE4)
Feb 14 18:04:42 linux-ytaf kernel: nouveau  [  DEVICE][0000:02:00.0] Family : NVE0
Feb 14 18:04:42 linux-ytaf kernel: xhci_hcd 0000:04:00.0: hcc params 0x0200f180 hci version 0x96 quirks 0x00080000
Feb 14 18:04:42 linux-ytaf kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 18:04:42 linux-ytaf kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 18:04:42 linux-ytaf kernel: usb usb2: Product: xHCI Host Controller
Feb 14 18:04:42 linux-ytaf kernel: usb usb2: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 18:04:42 linux-ytaf kernel: usb usb2: SerialNumber: 0000:04:00.0
Feb 14 18:04:42 linux-ytaf kernel: hub 2-0:1.0: USB hub found
Feb 14 18:04:42 linux-ytaf kernel: hub 2-0:1.0: 2 ports detected
Feb 14 18:04:42 linux-ytaf kernel: xhci_hcd 0000:04:00.0: xHCI Host Controller
Feb 14 18:04:42 linux-ytaf kernel: xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 3
Feb 14 18:04:42 linux-ytaf kernel: ehci-pci 0000:00:1d.0: EHCI Host Controller
Feb 14 18:04:42 linux-ytaf kernel: ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 4
Feb 14 18:04:42 linux-ytaf kernel: usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
Feb 14 18:04:42 linux-ytaf kernel: usb usb3: New USB device found, idVendor=1d6b, idProduct=0003
Feb 14 18:04:42 linux-ytaf kernel: usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 18:04:42 linux-ytaf kernel: ehci-pci 0000:00:1d.0: debug port 2
Feb 14 18:04:42 linux-ytaf kernel: usb usb3: Product: xHCI Host Controller
Feb 14 18:04:42 linux-ytaf kernel: usb usb3: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 18:04:42 linux-ytaf kernel: usb usb3: SerialNumber: 0000:04:00.0
Feb 14 18:04:42 linux-ytaf kernel: hub 3-0:1.0: USB hub found
Feb 14 18:04:42 linux-ytaf kernel: hub 3-0:1.0: 2 ports detected
Feb 14 18:04:42 linux-ytaf kernel: ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Feb 14 18:04:42 linux-ytaf kernel: ehci-pci 0000:00:1d.0: irq 23, io mem 0xf7b27000
Feb 14 18:04:42 linux-ytaf kernel: ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Feb 14 18:04:42 linux-ytaf kernel: usb usb4: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 18:04:42 linux-ytaf kernel: usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 18:04:42 linux-ytaf kernel: usb usb4: Product: EHCI Host Controller
Feb 14 18:04:42 linux-ytaf kernel: usb usb4: Manufacturer: Linux 4.1.15-8-default ehci_hcd
Feb 14 18:04:42 linux-ytaf kernel: usb usb4: SerialNumber: 0000:00:1d.0
Feb 14 18:04:42 linux-ytaf kernel: hub 4-0:1.0: USB hub found
Feb 14 18:04:42 linux-ytaf kernel: hub 4-0:1.0: 2 ports detected
Feb 14 18:04:42 linux-ytaf kernel: xhci_hcd 0000:05:00.0: xHCI Host Controller
Feb 14 18:04:42 linux-ytaf kernel: xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 5
Feb 14 18:04:42 linux-ytaf kernel: i915 0000:00:02.0: enabling device (0006 -> 0007)
Feb 14 18:04:42 linux-ytaf kernel: xhci_hcd 0000:05:00.0: hcc params 0x0200f180 hci version 0x96 quirks 0x00080000
Feb 14 18:04:42 linux-ytaf kernel: usb usb5: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 18:04:42 linux-ytaf kernel: usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 18:04:42 linux-ytaf kernel: usb usb5: Product: xHCI Host Controller
Feb 14 18:04:42 linux-ytaf kernel: usb usb5: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 18:04:42 linux-ytaf kernel: usb usb5: SerialNumber: 0000:05:00.0
Feb 14 18:04:42 linux-ytaf kernel: hub 5-0:1.0: USB hub found
Feb 14 18:04:42 linux-ytaf kernel: hub 5-0:1.0: 2 ports detected
Feb 14 18:04:42 linux-ytaf kernel: xhci_hcd 0000:05:00.0: xHCI Host Controller
Feb 14 18:04:42 linux-ytaf kernel: xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 6
Feb 14 18:04:42 linux-ytaf kernel: usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
Feb 14 18:04:42 linux-ytaf kernel: usb usb6: New USB device found, idVendor=1d6b, idProduct=0003
Feb 14 18:04:42 linux-ytaf kernel: usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 18:04:42 linux-ytaf kernel: usb usb6: Product: xHCI Host Controller
Feb 14 18:04:42 linux-ytaf kernel: usb usb6: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 18:04:42 linux-ytaf kernel: usb usb6: SerialNumber: 0000:05:00.0
Feb 14 18:04:42 linux-ytaf kernel: hub 6-0:1.0: USB hub found
Feb 14 18:04:42 linux-ytaf kernel: hub 6-0:1.0: 2 ports detected
Feb 14 18:04:42 linux-ytaf kernel: nouveau  [   VBIOS][0000:02:00.0] using image from PROM
Feb 14 18:04:42 linux-ytaf kernel: nouveau  [   VBIOS][0000:02:00.0] BIT signature found
Feb 14 18:04:42 linux-ytaf kernel: nouveau  [   VBIOS][0000:02:00.0] version 80.04.4b.00.07
Feb 14 18:04:42 linux-ytaf kernel: nouveau  [     PMC][0000:02:00.0] MSI interrupts enabled
Feb 14 18:04:42 linux-ytaf kernel: nouveau  [     PFB][0000:02:00.0] RAM type: GDDR5
Feb 14 18:04:42 linux-ytaf kernel: nouveau  [     PFB][0000:02:00.0] RAM size: 2048 MiB
Feb 14 18:04:42 linux-ytaf kernel: nouveau  [     PFB][0000:02:00.0]    ZCOMP: 0 tags
Feb 14 18:04:42 linux-ytaf kernel: nouveau  [    VOLT][0000:02:00.0] GPU voltage: 987500uv
Feb 14 18:04:42 linux-ytaf kernel: nouveau  [  PTHERM][0000:02:00.0] FAN control: PWM
Feb 14 18:04:42 linux-ytaf kernel: nouveau  [  PTHERM][0000:02:00.0] fan management: automatic
Feb 14 18:04:42 linux-ytaf kernel: nouveau  [  PTHERM][0000:02:00.0] internal sensor: yes
Feb 14 18:04:42 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 07: core 324 MHz memory 648 MHz 
Feb 14 18:04:42 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 0a: core 324-862 MHz memory 1620 MHz 
Feb 14 18:04:42 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 0d: core 540-1202 MHz memory 6008 MHz 
Feb 14 18:04:42 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 0f: core 540-1202 MHz memory 6008 MHz 
Feb 14 18:04:42 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] --: core 324 MHz memory 648 MHz 
Feb 14 18:04:42 linux-ytaf kernel: raid6: sse2x1   gen() 11034 MB/s
Feb 14 18:04:42 linux-ytaf kernel: usb 1-1: new high-speed USB device number 2 using ehci-pci
Feb 14 18:04:42 linux-ytaf kernel: raid6: sse2x1   xor()  8982 MB/s
Feb 14 18:04:42 linux-ytaf kernel: [TTM] Zone  kernel: Available graphics memory: 4034698 kiB
Feb 14 18:04:42 linux-ytaf kernel: [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
Feb 14 18:04:42 linux-ytaf kernel: [TTM] Initializing pool allocator
Feb 14 18:04:42 linux-ytaf kernel: [TTM] Initializing DMA pool allocator
Feb 14 18:04:42 linux-ytaf kernel: nouveau  [     DRM] VRAM: 2048 MiB
Feb 14 18:04:42 linux-ytaf kernel: nouveau  [     DRM] GART: 1048576 MiB
Feb 14 18:04:42 linux-ytaf kernel: nouveau  [     DRM] TMDS table version 2.0
Feb 14 18:04:42 linux-ytaf kernel: nouveau  [     DRM] DCB version 4.0
Feb 14 18:04:42 linux-ytaf kernel: nouveau  [     DRM] DCB outp 00: 01000f02 00020030
Feb 14 18:04:42 linux-ytaf kernel: nouveau  [     DRM] DCB outp 01: 02000f00 00000000
Feb 14 18:04:42 linux-ytaf kernel: nouveau  [     DRM] DCB outp 02: 08011f82 00020030
Feb 14 18:04:42 linux-ytaf kernel: nouveau  [     DRM] DCB outp 03: 02822f62 0f420010
Feb 14 18:04:42 linux-ytaf kernel: nouveau  [     DRM] DCB outp 05: 04833fb6 0f420010
Feb 14 18:04:42 linux-ytaf kernel: nouveau  [     DRM] DCB outp 06: 04033f72 00020010
Feb 14 18:04:42 linux-ytaf kernel: nouveau  [     DRM] DCB conn 00: 00001030
Feb 14 18:04:42 linux-ytaf kernel: nouveau  [     DRM] DCB conn 01: 00020131
Feb 14 18:04:42 linux-ytaf kernel: nouveau  [     DRM] DCB conn 02: 00002261
Feb 14 18:04:42 linux-ytaf kernel: nouveau  [     DRM] DCB conn 03: 00010346
Feb 14 18:04:42 linux-ytaf kernel: nouveau  [     DRM] DCB conn 04: 00000460
Feb 14 18:04:42 linux-ytaf kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Feb 14 18:04:42 linux-ytaf kernel: [drm] Driver supports precise vblank timestamp query.
Feb 14 18:04:42 linux-ytaf kernel: nouveau  [     DRM] MM: using COPY for buffer copies
Feb 14 18:04:42 linux-ytaf kernel: raid6: sse2x2   gen() 14083 MB/s
Feb 14 18:04:42 linux-ytaf kernel: usb 4-1: new high-speed USB device number 2 using ehci-pci
Feb 14 18:04:43 linux-ytaf kernel: usb 1-1: New USB device found, idVendor=8087, idProduct=0024
Feb 14 18:04:43 linux-ytaf kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb 14 18:04:43 linux-ytaf kernel: hub 1-1:1.0: USB hub found
Feb 14 18:04:43 linux-ytaf kernel: hub 1-1:1.0: 6 ports detected
Feb 14 18:04:43 linux-ytaf kernel: raid6: sse2x2   xor() 10018 MB/s
Feb 14 18:04:43 linux-ytaf kernel: usb 4-1: New USB device found, idVendor=8087, idProduct=0024
Feb 14 18:04:43 linux-ytaf kernel: usb 4-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb 14 18:04:43 linux-ytaf kernel: hub 4-1:1.0: USB hub found
Feb 14 18:04:43 linux-ytaf kernel: hub 4-1:1.0: 8 ports detected
Feb 14 18:04:43 linux-ytaf kernel: raid6: sse2x4   gen() 16256 MB/s
Feb 14 18:04:43 linux-ytaf kernel: usb 5-2: new high-speed USB device number 2 using xhci_hcd
Feb 14 18:04:43 linux-ytaf kernel: raid6: sse2x4   xor() 12078 MB/s
Feb 14 18:04:43 linux-ytaf kernel: raid6: using algorithm sse2x4 gen() 16256 MB/s
Feb 14 18:04:43 linux-ytaf kernel: raid6: .... xor() 12078 MB/s, rmw enabled
Feb 14 18:04:43 linux-ytaf kernel: raid6: using ssse3x2 recovery algorithm
Feb 14 18:04:43 linux-ytaf kernel: xor: automatically using best checksumming function:
Feb 14 18:04:43 linux-ytaf kernel:    avx       : 31208.000 MB/sec
Feb 14 18:04:43 linux-ytaf kernel: Btrfs loaded, assert=on
Feb 14 18:04:43 linux-ytaf kernel: BTRFS: device fsid 21024970-7a27-4114-8525-d8dd026f23b6 devid 1 transid 612 /dev/sdb3
Feb 14 18:04:43 linux-ytaf kernel: usb 1-1.4: new full-speed USB device number 3 using ehci-pci
Feb 14 18:04:43 linux-ytaf kernel: nouveau  [     DRM] allocated 1920x1080 fb: 0x60000, bo ffff8802220a6c00
Feb 14 18:04:43 linux-ytaf kernel: fbcon: nouveaufb (fb0) is primary device
Feb 14 18:04:43 linux-ytaf kernel: usb 5-2: New USB device found, idVendor=0930, idProduct=6545
Feb 14 18:04:43 linux-ytaf kernel: usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 14 18:04:43 linux-ytaf kernel: usb 5-2: Product: TransMemory
Feb 14 18:04:43 linux-ytaf kernel: usb 5-2: Manufacturer: TOSHIBA
Feb 14 18:04:43 linux-ytaf kernel: usb 5-2: SerialNumber: C89CDCBF6D59EF4140000065
Feb 14 18:04:43 linux-ytaf kernel: usb-storage 5-2:1.0: USB Mass Storage device detected
Feb 14 18:04:43 linux-ytaf kernel: scsi host8: usb-storage 5-2:1.0
Feb 14 18:04:43 linux-ytaf kernel: usbcore: registered new interface driver usb-storage
Feb 14 18:04:43 linux-ytaf kernel: usbcore: registered new interface driver uas
Feb 14 18:04:43 linux-ytaf kernel: usb 4-1.1: new full-speed USB device number 3 using ehci-pci
Feb 14 18:04:43 linux-ytaf kernel: usb 4-1.1: New USB device found, idVendor=1532, idProduct=0109
Feb 14 18:04:43 linux-ytaf kernel: usb 4-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 14 18:04:43 linux-ytaf kernel: usb 4-1.1: Product: Razer Lycosa
Feb 14 18:04:43 linux-ytaf kernel: usb 4-1.1: Manufacturer: Razer
Feb 14 18:04:43 linux-ytaf kernel: usbcore: registered new interface driver usbhid
Feb 14 18:04:43 linux-ytaf kernel: usbhid: USB HID core driver
Feb 14 18:04:43 linux-ytaf kernel: input: Razer Razer Lycosa as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1:1.0/0003:1532:0109.0001/input/input6
Feb 14 18:04:43 linux-ytaf kernel: usb 1-1.4: New USB device found, idVendor=06a3, idProduct=0ccb
Feb 14 18:04:43 linux-ytaf kernel: usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 14 18:04:43 linux-ytaf kernel: usb 1-1.4: Product: Cyborg R.A.T.7 Mouse
Feb 14 18:04:43 linux-ytaf kernel: usb 1-1.4: Manufacturer: Saitek
Feb 14 18:04:43 linux-ytaf kernel: hid-generic 0003:1532:0109.0001: input,hidraw0: USB HID v1.10 Keyboard [Razer Razer Lycosa] on usb-0000:00:1d.0-1.1/input0
Feb 14 18:04:43 linux-ytaf kernel: input: Razer Razer Lycosa as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1:1.1/0003:1532:0109.0002/input/input7
Feb 14 18:04:43 linux-ytaf kernel: hid-generic 0003:1532:0109.0002: input,hidraw1: USB HID v1.10 Device [Razer Razer Lycosa] on usb-0000:00:1d.0-1.1/input1
Feb 14 18:04:43 linux-ytaf kernel: Console: switching to colour frame buffer device 210x65
Feb 14 18:04:43 linux-ytaf kernel: nouveau 0000:02:00.0: fb0: nouveaufb frame buffer device
Feb 14 18:04:43 linux-ytaf kernel: nouveau 0000:02:00.0: registered panic notifier
Feb 14 18:04:43 linux-ytaf kernel: [drm] Initialized nouveau 1.2.2 20120801 for 0000:02:00.0 on minor 0
Feb 14 18:04:43 linux-ytaf kernel: [drm] Memory usable by graphics device = 2048M
Feb 14 18:04:43 linux-ytaf kernel: [drm] Replacing VGA console driver
Feb 14 18:04:43 linux-ytaf kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Feb 14 18:04:43 linux-ytaf kernel: [drm] Driver supports precise vblank timestamp query.
Feb 14 18:04:43 linux-ytaf kernel: vgaarb: device changed decodes: PCI:0000:02:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
Feb 14 18:04:43 linux-ytaf kernel: [drm] Initialized i915 1.6.0 20150327 for 0000:00:02.0 on minor 1
Feb 14 18:04:43 linux-ytaf kernel: [drm] GMBUS [i915 gmbus vga] timed out, falling back to bit banging on pin 2
Feb 14 18:04:43 linux-ytaf kernel: i915 0000:00:02.0: No connectors reported connected with modes
Feb 14 18:04:43 linux-ytaf kernel: [drm] Cannot find any crtc or sizes - going 1024x768
Feb 14 18:04:43 linux-ytaf kernel: i915 0000:00:02.0: fb1: inteldrmfb frame buffer device
Feb 14 18:04:44 linux-ytaf kernel: scsi 8:0:0:0: Direct-Access     TOSHIBA  TransMemory      PMAP PQ: 0 ANSI: 6
Feb 14 18:04:44 linux-ytaf kernel: sd 8:0:0:0: Attached scsi generic sg3 type 0
Feb 14 18:04:44 linux-ytaf kernel: sd 8:0:0:0: [sdc] 30228480 512-byte logical blocks: (15.4 GB/14.4 GiB)
Feb 14 18:04:44 linux-ytaf kernel: sd 8:0:0:0: [sdc] Write Protect is off
Feb 14 18:04:44 linux-ytaf kernel: sd 8:0:0:0: [sdc] Mode Sense: 45 00 00 00
Feb 14 18:04:44 linux-ytaf kernel: sd 8:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Feb 14 18:04:44 linux-ytaf kernel: PM: Starting manual resume from disk
Feb 14 18:04:44 linux-ytaf kernel: PM: Hibernation image partition 8:18 present
Feb 14 18:04:44 linux-ytaf kernel: PM: Looking for hibernation image.
Feb 14 18:04:44 linux-ytaf kernel: PM: Image not found (code -22)
Feb 14 18:04:44 linux-ytaf kernel: PM: Hibernation image not present or could not be loaded.
Feb 14 18:04:44 linux-ytaf kernel: BTRFS info (device sdb3): disk space caching is enabled
Feb 14 18:04:44 linux-ytaf kernel: BTRFS: has skinny extents
Feb 14 18:04:44 linux-ytaf kernel:  sdc: sdc1
Feb 14 18:04:44 linux-ytaf kernel: sd 8:0:0:0: [sdc] Attached SCSI removable disk
Feb 14 18:04:44 linux-ytaf systemd-journal[187]: Journal stopped
Feb 14 18:04:46 linux-ytaf systemd-journal[482]: Runtime journal is using 8.0M (max allowed 394.0M, trying to leave 591.0M free of 3.8G available → current limit 394.0M).
Feb 14 18:04:46 linux-ytaf systemd-journal[482]: Runtime journal is using 8.0M (max allowed 394.0M, trying to leave 591.0M free of 3.8G available → current limit 394.0M).
Feb 14 18:04:46 linux-ytaf kernel: random: nonblocking pool is initialized
Feb 14 18:04:46 linux-ytaf systemd[1]: RTC configured in localtime, applying delta of 60 minutes to system time.
Feb 14 18:04:46 linux-ytaf kernel: BTRFS info (device sdb3): disk space caching is enabled
Feb 14 18:04:46 linux-ytaf systemd-journal[482]: Journal started
Feb 14 18:04:46 linux-ytaf systemd-udevd[509]: starting version 210
Feb 14 18:04:46 linux-ytaf systemd-udevd[509]: Network interface NamePolicy= disabled on kernel commandline, ignoring.
Feb 14 18:04:46 linux-ytaf systemd-udevd[509]: invalid key/value pair in file /usr/lib/udev/rules.d/51-android.rules on line 115,starting at character 57 ('')
Feb 14 18:04:47 linux-ytaf kernel: thermal LNXTHERM:00: registered as thermal_zone0
Feb 14 18:04:47 linux-ytaf kernel: ACPI: Thermal Zone [TZ00] (28 C)
Feb 14 18:04:47 linux-ytaf kernel: thermal LNXTHERM:01: registered as thermal_zone1
Feb 14 18:04:47 linux-ytaf kernel: ACPI: Thermal Zone [TZ01] (30 C)
Feb 14 18:04:47 linux-ytaf kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Feb 14 18:04:47 linux-ytaf kernel: input: PC Speaker as /devices/platform/pcspkr/input/input8
Feb 14 18:04:47 linux-ytaf mtp-probe[623]: checking bus 5, device 2: "/sys/devices/pci0000:00/0000:00:1c.5/0000:05:00.0/usb5/5-2"
Feb 14 18:04:47 linux-ytaf mtp-probe[624]: checking bus 4, device 3: "/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1"
Feb 14 18:04:47 linux-ytaf mtp-probe[622]: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4"
Feb 14 18:04:47 linux-ytaf mtp-probe[623]: bus: 5, device: 2 was not an MTP device
Feb 14 18:04:47 linux-ytaf mtp-probe[622]: bus: 1, device: 3 was not an MTP device
Feb 14 18:04:47 linux-ytaf mtp-probe[624]: bus: 4, device: 3 was not an MTP device
Feb 14 18:04:47 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000580-0x000000000000059F conflicts with OpRegion 0x0000000000000580-0x000000000000058F (\_SB_.PCI0.SBUS.SMBI) (20150410/utaddress-254)
Feb 14 18:04:47 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000580-0x000000000000059F conflicts with OpRegion 0x0000000000000580-0x000000000000059F (\_SB_.PCI0.SMB_.SMIO) (20150410/utaddress-254)
Feb 14 18:04:47 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 18:04:47 linux-ytaf kernel: asus_wmi: ASUS WMI generic driver loaded
Feb 14 18:04:47 linux-ytaf kernel: pps_core: LinuxPPS API ver. 1 registered
Feb 14 18:04:47 linux-ytaf kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
Feb 14 18:04:47 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20150410/utaddress-254)
Feb 14 18:04:47 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 18:04:47 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150410/utaddress-254)
Feb 14 18:04:47 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150410/utaddress-254)
Feb 14 18:04:47 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 18:04:47 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150410/utaddress-254)
Feb 14 18:04:47 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150410/utaddress-254)
Feb 14 18:04:47 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 18:04:47 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150410/utaddress-254)
Feb 14 18:04:47 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150410/utaddress-254)
Feb 14 18:04:47 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 18:04:47 linux-ytaf kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
Feb 14 18:04:47 linux-ytaf kernel: PTP clock support registered
Feb 14 18:04:47 linux-ytaf kernel: asus_wmi: Initialization: 0x0
Feb 14 18:04:47 linux-ytaf kernel: asus_wmi: BIOS WMI version: 0.9
Feb 14 18:04:47 linux-ytaf kernel: asus_wmi: SFUN value: 0x0
Feb 14 18:04:47 linux-ytaf kernel: input: Eee PC WMI hotkeys as /devices/platform/eeepc-wmi/input/input9
Feb 14 18:04:47 linux-ytaf kernel: asus_wmi: Disabling ACPI video driver
Feb 14 18:04:47 linux-ytaf kernel: input: Saitek Cyborg R.A.T.7 Mouse as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/0003:06A3:0CCB.0003/input/input10
Feb 14 18:04:47 linux-ytaf kernel: saitek 0003:06A3:0CCB.0003: input,hidraw2: USB HID v1.11 Mouse [Saitek Cyborg R.A.T.7 Mouse] on usb-0000:00:1a.0-1.4/input0
Feb 14 18:04:47 linux-ytaf kernel: AVX version of gcm_enc/dec engaged.
Feb 14 18:04:47 linux-ytaf kernel: AES CTR mode by8 optimization enabled
Feb 14 18:04:47 linux-ytaf kernel: iTCO_vendor_support: vendor-support=0
Feb 14 18:04:47 linux-ytaf kernel: iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
Feb 14 18:04:47 linux-ytaf kernel: iTCO_wdt: Found a Cougar Point TCO device (Version=2, TCOBASE=0x0460)
Feb 14 18:04:47 linux-ytaf kernel: iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
Feb 14 18:04:47 linux-ytaf kernel: snd_hda_intel 0000:00:1b.0: enabling device (0000 -> 0002)
Feb 14 18:04:47 linux-ytaf kernel: snd_hda_intel 0000:02:00.1: enabling device (0000 -> 0002)
Feb 14 18:04:47 linux-ytaf kernel: snd_hda_intel 0000:02:00.1: Disabling MSI
Feb 14 18:04:47 linux-ytaf kernel: snd_hda_intel 0000:02:00.1: Handle VGA-switcheroo audio client
Feb 14 18:04:47 linux-ytaf kernel: e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
Feb 14 18:04:47 linux-ytaf kernel: e1000e: Copyright(c) 1999 - 2014 Intel Corporation.
Feb 14 18:04:47 linux-ytaf kernel: e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
Feb 14 18:04:47 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC889: line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line
Feb 14 18:04:47 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Feb 14 18:04:47 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
Feb 14 18:04:47 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
Feb 14 18:04:47 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    dig-out=0x11/0x1e
Feb 14 18:04:47 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    inputs:
Feb 14 18:04:47 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:      Front Mic=0x19
Feb 14 18:04:47 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:      Rear Mic=0x18
Feb 14 18:04:47 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:      Line=0x1a
Feb 14 18:04:48 linux-ytaf kernel: input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
Feb 14 18:04:48 linux-ytaf kernel: Adding 2104316k swap on /dev/sdb2.  Priority:-1 extents:1 across:2104316k FS
Feb 14 18:04:48 linux-ytaf kernel: input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
Feb 14 18:04:48 linux-ytaf kernel: input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input13
Feb 14 18:04:48 linux-ytaf kernel: input: HDA Intel PCH Line Out Front as /devices/pci0000:00/0000:00:1b.0/sound/card0/input14
Feb 14 18:04:48 linux-ytaf kernel: input: HDA Intel PCH Line Out Surround as /devices/pci0000:00/0000:00:1b.0/sound/card0/input15
Feb 14 18:04:48 linux-ytaf kernel: input: HDA Intel PCH Line Out CLFE as /devices/pci0000:00/0000:00:1b.0/sound/card0/input16
Feb 14 18:04:48 linux-ytaf kernel: input: HDA Intel PCH Line Out Side as /devices/pci0000:00/0000:00:1b.0/sound/card0/input17
Feb 14 18:04:48 linux-ytaf kernel: input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input18
Feb 14 18:04:48 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: registered PHC clock
Feb 14 18:04:48 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) c8:60:00:09:38:76
Feb 14 18:04:48 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
Feb 14 18:04:48 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: FFFFFF-0FF
Feb 14 18:04:48 linux-ytaf kernel: FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Feb 14 18:04:48 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input19
Feb 14 18:04:48 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input20
Feb 14 18:04:48 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input21
Feb 14 18:04:48 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input22
Feb 14 18:04:48 linux-ytaf systemd-fsck[719]: /sbin/fsck.xfs: XFS file system.
Feb 14 18:04:48 linux-ytaf kernel: SGI XFS with ACLs, security attributes, realtime, no debug enabled
Feb 14 18:04:48 linux-ytaf kernel: XFS (sdb4): Mounting V5 Filesystem
Feb 14 18:04:49 linux-ytaf kernel: XFS (sdb4): Starting recovery (logdev: internal)
Feb 14 18:04:53 linux-ytaf kernel: XFS (sdb4): Ending recovery (logdev: internal)
Feb 14 18:04:55 linux-ytaf systemd-journal[482]: Permanent journal is using 87.7M (max allowed 4.0G, trying to leave 4.0G free of 32.8G available → current limit 4.0G).
Feb 14 18:04:55 linux-ytaf systemd-journal[482]: Time spent on flushing to /var is 30.014ms for 1030 entries.
Feb 14 18:04:55 linux-ytaf kernel: audit: type=1305 audit(1455469493.480:2): audit_pid=782 old=0 auid=4294967295 ses=4294967295 res=1
Feb 14 18:04:55 linux-ytaf kernel: BTRFS warning (device sdb3): block group 29360128 has wrong amount of free space
Feb 14 18:04:55 linux-ytaf kernel: BTRFS warning (device sdb3): failed to load free space cache for block group 29360128, rebuild it now
Feb 14 18:04:53 linux-ytaf auditd[782]: Started dispatcher: /sbin/audispd pid: 792
Feb 14 18:04:53 linux-ytaf audispd[792]: priority_boost_parser called with: 4
Feb 14 18:04:53 linux-ytaf audispd[792]: max_restarts_parser called with: 10
Feb 14 18:04:53 linux-ytaf audispd[792]: No plugins found, exiting
Feb 14 18:04:53 linux-ytaf auditd[782]: Init complete, auditd 2.3.6 listening for events (startup state enable)
Feb 14 18:04:55 linux-ytaf auditctl[783]: No rules
Feb 14 18:04:55 linux-ytaf auditctl[783]: AUDIT_STATUS: enabled=0 flag=1 pid=0 rate_limit=0 backlog_limit=320 lost=0 backlog=0
Feb 14 18:04:55 linux-ytaf boot.apparmor[796]: Starting AppArmor ..done
Feb 14 18:04:55 linux-ytaf dbus-daemon[958]: Unknown username "srvGeoClue" in message bus configuration file
Feb 14 18:04:55 linux-ytaf avahi-daemon[959]: Found user 'avahi' (UID 486) and group 'avahi' (GID 485).
Feb 14 18:04:55 linux-ytaf avahi-daemon[959]: Successfully dropped root privileges.
Feb 14 18:04:55 linux-ytaf avahi-daemon[959]: avahi-daemon 0.6.31 starting up.
Feb 14 18:04:55 linux-ytaf avahi-daemon[959]: Loading service file /etc/avahi/services/sftp-ssh.service.
Feb 14 18:04:55 linux-ytaf avahi-daemon[959]: Loading service file /etc/avahi/services/ssh.service.
Feb 14 18:04:55 linux-ytaf avahi-daemon[959]: Network interface enumeration completed.
Feb 14 18:04:55 linux-ytaf avahi-daemon[959]: Registering HINFO record with values 'X86_64'/'LINUX'.
Feb 14 18:04:55 linux-ytaf avahi-daemon[959]: Server startup complete. Host name is linux-ytaf.local. Local service cookie is 2586741550.
Feb 14 18:04:55 linux-ytaf avahi-daemon[959]: Service "linux-ytaf" (/etc/avahi/services/ssh.service) successfully established.
Feb 14 18:04:55 linux-ytaf avahi-daemon[959]: Service "linux-ytaf" (/etc/avahi/services/sftp-ssh.service) successfully established.
Feb 14 18:04:55 linux-ytaf display-manager[988]: /etc/vconsole.conf available
Feb 14 18:04:55 linux-ytaf display-manager[988]: KEYMAP: de-latin1-nodeadkeys
Feb 14 18:04:55 linux-ytaf display-manager[988]: Command: localectl set-keymap de-latin1-nodeadkeys
Feb 14 18:04:55 linux-ytaf display-manager[988]: I: Using systemd /usr/share/systemd/kbd-model-map mapping
Feb 14 18:04:55 linux-ytaf smartd[965]: smartd 6.2 2013-11-07 r3856 [x86_64-linux-4.1.15-8-default] (SUSE RPM)
Feb 14 18:04:55 linux-ytaf smartd[965]: Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
Feb 14 18:04:55 linux-ytaf smartd[965]: Opened configuration file /etc/smartd.conf
Feb 14 18:04:55 linux-ytaf smartd[965]: Drive: DEVICESCAN, implied '-a' Directive on line 26 of file /etc/smartd.conf
Feb 14 18:04:55 linux-ytaf smartd[965]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
Feb 14 18:04:55 linux-ytaf smartd[965]: Device: /dev/sda, type changed from 'scsi' to 'sat'
Feb 14 18:04:55 linux-ytaf smartd[965]: Device: /dev/sda [SAT], opened
Feb 14 18:04:55 linux-ytaf smartd[965]: Device: /dev/sda [SAT], SAMSUNG SSD 830 Series, S/N:S0Z4NEAC906195, WWN:5-002538-043584d30, FW:CXM03B1Q, 256 GB
Feb 14 18:04:55 linux-ytaf smartd[965]: Device: /dev/sda [SAT], found in smartd database: Samsung based SSDs
Feb 14 18:04:55 linux-ytaf smartd[965]: Device: /dev/sda [SAT], can't monitor Current_Pending_Sector count - no Attribute 197
Feb 14 18:04:55 linux-ytaf smartd[965]: Device: /dev/sda [SAT], can't monitor Offline_Uncorrectable count - no Attribute 198
Feb 14 18:04:55 linux-ytaf smartd[965]: Device: /dev/sda [SAT], is SMART capable. Adding to "monitor" list.
Feb 14 18:04:55 linux-ytaf smartd[965]: Device: /dev/sda [SAT], state read from /var/lib/smartmontools/smartd.SAMSUNG_SSD_830_Series-S0Z4NEAC906195.ata.state
Feb 14 18:04:55 linux-ytaf dbus[958]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service'
Feb 14 18:04:55 linux-ytaf dbus[958]: [system] Successfully activated service 'org.freedesktop.locale1'
Feb 14 18:04:56 linux-ytaf smartd[965]: Device: /dev/sdb, type changed from 'scsi' to 'sat'
Feb 14 18:04:56 linux-ytaf smartd[965]: Device: /dev/sdb [SAT], opened
Feb 14 18:04:56 linux-ytaf smartd[965]: Device: /dev/sdb [SAT], TOSHIBA HDWD110, S/N:Y5GDEMGFS, WWN:5-000039-fe7c5a79c, FW:MS2OA8J0, 1.00 TB
Feb 14 18:04:56 linux-ytaf smartd[965]: Device: /dev/sdb [SAT], not found in smartd database.
Feb 14 18:04:56 linux-ytaf kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
Feb 14 18:04:56 linux-ytaf kernel: nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
Feb 14 18:04:56 linux-ytaf kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Feb 14 18:04:56 linux-ytaf SuSEfirewall2[1065]: Firewall rules set to CLOSE.
Feb 14 18:04:56 linux-ytaf ModemManager[961]: <info>  ModemManager (version 1.4.10) starting in system bus...
Feb 14 18:04:56 linux-ytaf dbus[958]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Feb 14 18:04:56 linux-ytaf kernel: No iBFT detected.
Feb 14 18:04:56 linux-ytaf logger[1019]: /etc/init.d/xdm: No changes for /etc/X11/xdm/Xservers
Feb 14 18:04:56 linux-ytaf logger[1019]: /etc/init.d/xdm: No changes for /etc/X11/xdm/xdm-config
Feb 14 18:04:56 linux-ytaf polkitd[1081]: Started polkitd version 0.113
Feb 14 18:04:57 linux-ytaf polkitd[1081]: Loading rules from directory /etc/polkit-1/rules.d
Feb 14 18:04:57 linux-ytaf polkitd[1081]: Loading rules from directory /usr/share/polkit-1/rules.d
Feb 14 18:04:57 linux-ytaf polkitd[1081]: Finished loading, compiling and executing 3 rules
Feb 14 18:04:57 linux-ytaf dbus[958]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Feb 14 18:04:57 linux-ytaf polkitd[1081]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
Feb 14 18:04:57 linux-ytaf display-manager[988]: Starting service sddm..done
Feb 14 18:04:57 linux-ytaf smartd[965]: Device: /dev/sdb [SAT], is SMART capable. Adding to "monitor" list.
Feb 14 18:04:57 linux-ytaf smartd[965]: Device: /dev/sdb [SAT], state read from /var/lib/smartmontools/smartd.TOSHIBA_HDWD110-Y5GDEMGFS.ata.state
Feb 14 18:04:57 linux-ytaf smartd[965]: Monitoring 2 ATA and 0 SCSI devices
Feb 14 18:04:57 linux-ytaf smartd[965]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 5 = 0
Feb 14 18:04:57 linux-ytaf smartd[965]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 9 = 0
Feb 14 18:04:57 linux-ytaf smartd[965]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 12 = 0
Feb 14 18:04:57 linux-ytaf smartd[965]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 177 = 0
Feb 14 18:04:57 linux-ytaf smartd[965]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 179 = 0
Feb 14 18:04:57 linux-ytaf smartd[965]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 181 = 0
Feb 14 18:04:57 linux-ytaf smartd[965]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 182 = 0
Feb 14 18:04:57 linux-ytaf smartd[965]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 183 = 0
Feb 14 18:04:57 linux-ytaf smartd[965]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 187 = 0
Feb 14 18:04:57 linux-ytaf smartd[965]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 190 = 0
Feb 14 18:04:57 linux-ytaf smartd[965]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 195 = 0
Feb 14 18:04:57 linux-ytaf smartd[965]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 199 = 0
Feb 14 18:04:57 linux-ytaf smartd[965]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 235 = 0
Feb 14 18:04:57 linux-ytaf smartd[965]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 241 = 0
Feb 14 18:04:58 linux-ytaf smartd[965]: Device: /dev/sdb [SAT], same Attribute has different ID numbers: 1 = 0
Feb 14 18:04:58 linux-ytaf smartd[965]: Device: /dev/sdb [SAT], same Attribute has different ID numbers: 2 = 0
Feb 14 18:04:58 linux-ytaf smartd[965]: Device: /dev/sdb [SAT], same Attribute has different ID numbers: 3 = 0
Feb 14 18:04:58 linux-ytaf smartd[965]: Device: /dev/sdb [SAT], same Attribute has different ID numbers: 4 = 0
Feb 14 18:04:58 linux-ytaf smartd[965]: Device: /dev/sdb [SAT], same Attribute has different ID numbers: 5 = 0
Feb 14 18:04:58 linux-ytaf smartd[965]: Device: /dev/sdb [SAT], same Attribute has different ID numbers: 7 = 0
Feb 14 18:04:58 linux-ytaf smartd[965]: Device: /dev/sdb [SAT], same Attribute has different ID numbers: 8 = 0
Feb 14 18:04:58 linux-ytaf smartd[965]: Device: /dev/sdb [SAT], same Attribute has different ID numbers: 9 = 0
Feb 14 18:04:58 linux-ytaf smartd[965]: Device: /dev/sdb [SAT], same Attribute has different ID numbers: 10 = 0
Feb 14 18:04:58 linux-ytaf smartd[965]: Device: /dev/sdb [SAT], same Attribute has different ID numbers: 12 = 0
Feb 14 18:04:58 linux-ytaf smartd[965]: Device: /dev/sdb [SAT], same Attribute has different ID numbers: 192 = 0
Feb 14 18:04:58 linux-ytaf smartd[965]: Device: /dev/sdb [SAT], same Attribute has different ID numbers: 193 = 0
Feb 14 18:04:58 linux-ytaf smartd[965]: Device: /dev/sdb [SAT], same Attribute has different ID numbers: 194 = 0
Feb 14 18:04:58 linux-ytaf smartd[965]: Device: /dev/sdb [SAT], same Attribute has different ID numbers: 196 = 0
Feb 14 18:04:58 linux-ytaf smartd[965]: Device: /dev/sdb [SAT], same Attribute has different ID numbers: 197 = 0
Feb 14 18:04:58 linux-ytaf smartd[965]: Device: /dev/sdb [SAT], same Attribute has different ID numbers: 198 = 0
Feb 14 18:04:58 linux-ytaf smartd[965]: Device: /dev/sdb [SAT], same Attribute has different ID numbers: 199 = 0
Feb 14 18:04:58 linux-ytaf smartd[965]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.SAMSUNG_SSD_830_Series-S0Z4NEAC906195.ata.state
Feb 14 18:04:58 linux-ytaf smartd[965]: Device: /dev/sdb [SAT], state written to /var/lib/smartmontools/smartd.TOSHIBA_HDWD110-Y5GDEMGFS.ata.state
Feb 14 18:04:58 linux-ytaf sddm[1111]: Initializing...
Feb 14 18:04:58 linux-ytaf sddm[1111]: Adding new display on vt 7 ...
Feb 14 18:04:58 linux-ytaf sddm[1111]: Running: /usr/bin/X -nolisten tcp -auth /run/sddm/{3a11f96b-a599-4dcd-a888-eccd48bd3416} -background none -noreset -displayfd 17 vt7
Feb 14 18:04:59 linux-ytaf ModemManager[961]: <info>  Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin
Feb 14 18:05:00 linux-ytaf kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Feb 14 18:05:00 linux-ytaf wickedd-dhcp4[1068]: eth0: Request to acquire DHCPv4 lease with UUID b8b3c056-00ef-0c00-3804-000004000000
Feb 14 18:05:00 linux-ytaf sddm[1111]: Display server started.
Feb 14 18:05:00 linux-ytaf sddm[1111]: Socket server starting...
Feb 14 18:05:00 linux-ytaf sddm[1111]: Greeter starting...
Feb 14 18:05:00 linux-ytaf sddm[1111]: Adding cookie to "/run/sddm/{3a11f96b-a599-4dcd-a888-eccd48bd3416}"
Feb 14 18:05:00 linux-ytaf sddm-helper[1246]: [PAM] Starting...
Feb 14 18:05:00 linux-ytaf sddm-helper[1246]: [PAM] Authenticating...
Feb 14 18:05:00 linux-ytaf sddm-helper[1246]: [PAM] returning.
Feb 14 18:05:00 linux-ytaf sddm-helper[1246]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
Feb 14 18:05:00 linux-ytaf systemd[1248]: pam_unix(systemd-user:session): session opened for user sddm by (uid=0)
Feb 14 18:05:00 linux-ytaf kernel: NET: Registered protocol family 17
Feb 14 18:05:00 linux-ytaf sddm[1111]: Message received from greeter: Connect
Feb 14 18:05:01 linux-ytaf wickedd-dhcp4[1068]: eth0: Committed DHCPv4 lease with address 192.168.178.12 (lease time 864000 sec, renew in 432000 sec, rebind in 756000 sec)
Feb 14 18:05:01 linux-ytaf avahi-daemon[959]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.178.12.
Feb 14 18:05:01 linux-ytaf avahi-daemon[959]: New relevant interface eth0.IPv4 for mDNS.
Feb 14 18:05:01 linux-ytaf avahi-daemon[959]: Registering new address record for 192.168.178.12 on eth0.IPv4.
Feb 14 18:05:01 linux-ytaf wickedd[1080]: eth0: Notified neighbours about IP address 192.168.178.12
Feb 14 18:05:01 MM-Home wicked[1083]: lo              up
Feb 14 18:05:01 MM-Home wicked[1083]: eth0            up
Feb 14 18:05:01 MM-Home echo[1437]: Starting mail service (Postfix)
Feb 14 18:05:01 MM-Home iscsiadm[1439]: iscsiadm: No records found
Feb 14 18:05:01 MM-Home SuSEfirewall2[1467]: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Feb 14 18:05:01 MM-Home SuSEfirewall2[1476]: using default zone 'ext' for interface eth0
Feb 14 18:05:01 MM-Home ntpd[1455]: ntpd 4.2.8p4@1.3265-o Thu Dec 17 05:32:52 UTC 2015 (1): Starting
Feb 14 18:05:01 MM-Home ntpd[1455]: Command line: /usr/sbin/ntpd -p /var/run/ntp/ntpd.pid -g -u ntp:ntp -c /etc/ntp.conf
Feb 14 18:05:01 MM-Home sntp[1624]: sntp 4.2.8p4@1.3265-o Thu Dec 17 05:32:29 UTC 2015 (1)
Feb 14 18:05:01 MM-Home sntp[1624]: kod_init_kod_db(): Cannot open KoD db file /var/db/ntp-kod: No such file or directory
Feb 14 18:05:01 MM-Home ntpd[1623]: proto: precision = 0.039 usec (-25)
Feb 14 18:05:01 MM-Home start-ntpd[1443]: Starting network time protocol daemon (NTPD)sntp 4.2.8p4@1.3265-o Thu Dec 17 05:32:29 UTC 2015 (1)
Feb 14 18:05:01 MM-Home start-ntpd[1443]: kod_init_kod_db(): Cannot open KoD db file /var/db/ntp-kod: No such file or directory
Feb 14 18:05:01 MM-Home ntpd[1623]: switching logging to file /var/log/ntp
Feb 14 18:05:01 MM-Home sntp[1624]: 2016-02-14 18:05:01.655819 (-0100) +0.07175 +/- 0.104641 192.168.178.1 s3 no-leap
Feb 14 18:05:01 MM-Home start-ntpd[1443]: 2016-02-14 18:05:01.655819 (-0100) +0.07175 +/- 0.104641 192.168.178.1 s3 no-leap
Feb 14 18:05:01 MM-Home SuSEfirewall2[1629]: Firewall rules successfully set
Feb 14 18:05:01 MM-Home /usr/sbin/start-ntpd[1634]: runtime configuration: server 192.168.178.1
Feb 14 18:05:01 MM-Home start-ntpd[1443]: /usr/sbin/ntpq: read: Connection refused
Feb 14 18:05:01 MM-Home postfix/postfix-script[1636]: starting the Postfix mail system
Feb 14 18:05:01 MM-Home postfix/master[1638]: daemon started -- version 2.11.6, configuration /etc/postfix
Feb 14 18:05:01 MM-Home cron[1656]: (CRON) INFO (RANDOM_DELAY will be scaled with factor 89% if used.)
Feb 14 18:05:01 MM-Home cron[1656]: (CRON) INFO (running with inotify support)
Feb 14 18:05:02 MM-Home dbus[958]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
Feb 14 18:05:02 MM-Home udisksd[1660]: udisks daemon version 2.1.6 starting
Feb 14 18:05:02 MM-Home dbus[958]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Feb 14 18:05:02 MM-Home udisksd[1660]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Feb 14 18:05:02 MM-Home dbus[958]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
Feb 14 18:05:02 MM-Home dbus[958]: [system] Successfully activated service 'org.freedesktop.UPower'
Feb 14 18:05:09 MM-Home sddm[1111]: Message received from greeter: Login
Feb 14 18:05:09 MM-Home sddm[1111]: Reading from "/usr/share/xsessions/plasma5.desktop"
Feb 14 18:05:09 MM-Home sddm[1111]: Session "/usr/share/xsessions/plasma5.desktop" selected, command: "/usr/bin/startkde"
Feb 14 18:05:09 MM-Home sddm-helper[1693]: [PAM] Starting...
Feb 14 18:05:09 MM-Home sddm-helper[1693]: [PAM] Authenticating...
Feb 14 18:05:09 MM-Home sddm-helper[1693]: [PAM] Preparing to converse...
Feb 14 18:05:09 MM-Home sddm-helper[1693]: [PAM] Conversation with 1 messages
Feb 14 18:05:09 MM-Home sddm-helper[1693]: [PAM] returning.
Feb 14 18:05:09 MM-Home sddm[1111]: Authenticated successfully
Feb 14 18:05:09 MM-Home sddm-helper[1693]: pam_unix(sddm:session): session opened for user marc by (uid=0)
Feb 14 18:05:09 MM-Home systemd[1694]: pam_unix(systemd-user:session): session opened for user marc by (uid=0)
Feb 14 18:05:09 MM-Home sddm-helper[1696]: Adding cookie to "/home/marc/.Xauthority"
Feb 14 18:05:09 MM-Home sddm-helper[1246]: [PAM] Ended.
Feb 14 18:05:09 MM-Home sddm[1111]: Auth: sddm-helper exited successfully
Feb 14 18:05:09 MM-Home sddm[1111]: Greeter stopped.
Feb 14 18:05:09 MM-Home sddm[1111]: Session started
Feb 14 18:05:13 MM-Home dbus[958]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Feb 14 18:05:13 MM-Home org.kde.powerdevil.backlighthelper[958]: powerdevil: no kernel backlight interface found
Feb 14 18:05:13 MM-Home dbus[958]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Feb 14 18:05:13 MM-Home polkitd[1081]: Registered Authentication Agent for unix-session:2 (system bus name :1.35 [/usr/lib64/libexec/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale de_DE.UTF-8)
Feb 14 18:05:14 MM-Home dbus[958]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service'
Feb 14 18:05:14 MM-Home dbus[958]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Feb 14 18:05:14 MM-Home rtkit-daemon[1849]: Successfully called chroot.
Feb 14 18:05:14 MM-Home rtkit-daemon[1849]: Successfully dropped privileges.
Feb 14 18:05:14 MM-Home rtkit-daemon[1849]: Successfully limited resources.
Feb 14 18:05:14 MM-Home rtkit-daemon[1849]: Running.
Feb 14 18:05:14 MM-Home rtkit-daemon[1849]: Canary thread running.
Feb 14 18:05:14 MM-Home rtkit-daemon[1849]: Watchdog thread running.
Feb 14 18:05:14 MM-Home rtkit-daemon[1849]: Successfully made thread 1848 of process 1848 (/usr/bin/pulseaudio) owned by 'marc' high priority at nice level -11.
Feb 14 18:05:14 MM-Home rtkit-daemon[1849]: Supervising 1 threads of 1 processes of 1 users.
Feb 14 18:05:17 MM-Home rtkit-daemon[1849]: Supervising 1 threads of 1 processes of 1 users.
Feb 14 18:05:17 MM-Home rtkit-daemon[1849]: Successfully made thread 1903 of process 1848 (/usr/bin/pulseaudio) owned by 'marc' RT at priority 5.
Feb 14 18:05:17 MM-Home rtkit-daemon[1849]: Supervising 2 threads of 1 processes of 1 users.
Feb 14 18:05:18 MM-Home rtkit-daemon[1849]: Supervising 2 threads of 1 processes of 1 users.
Feb 14 18:05:18 MM-Home rtkit-daemon[1849]: Successfully made thread 1908 of process 1848 (/usr/bin/pulseaudio) owned by 'marc' RT at priority 5.
Feb 14 18:05:18 MM-Home rtkit-daemon[1849]: Supervising 3 threads of 1 processes of 1 users.
Feb 14 18:05:18 MM-Home rtkit-daemon[1849]: Supervising 3 threads of 1 processes of 1 users.
Feb 14 18:05:18 MM-Home rtkit-daemon[1849]: Successfully made thread 1909 of process 1848 (/usr/bin/pulseaudio) owned by 'marc' RT at priority 5.
Feb 14 18:05:18 MM-Home rtkit-daemon[1849]: Supervising 4 threads of 1 processes of 1 users.
Feb 14 18:05:18 MM-Home dbus[958]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Feb 14 18:05:18 MM-Home rtkit-daemon[1849]: Successfully made thread 1912 of process 1912 (/usr/bin/pulseaudio) owned by 'marc' high priority at nice level -11.
Feb 14 18:05:18 MM-Home rtkit-daemon[1849]: Supervising 5 threads of 2 processes of 1 users.
Feb 14 18:05:18 MM-Home pulseaudio[1912]: [pulseaudio] pid.c: Daemon already running.
Feb 14 18:05:18 MM-Home bluetoothd[1910]: Bluetooth daemon 5.35
Feb 14 18:05:18 MM-Home dbus[958]: [system] Successfully activated service 'org.bluez'
Feb 14 18:05:19 MM-Home bluetoothd[1910]: Starting SDP server
Feb 14 18:05:19 MM-Home kernel: Bluetooth: Core ver 2.20
Feb 14 18:05:19 MM-Home kernel: NET: Registered protocol family 31
Feb 14 18:05:19 MM-Home kernel: Bluetooth: HCI device and connection manager initialized
Feb 14 18:05:19 MM-Home kernel: Bluetooth: HCI socket layer initialized
Feb 14 18:05:19 MM-Home kernel: Bluetooth: L2CAP socket layer initialized
Feb 14 18:05:19 MM-Home kernel: Bluetooth: SCO socket layer initialized
Feb 14 18:05:19 MM-Home dbus[958]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Feb 14 18:05:19 MM-Home bluetoothd[1910]: Bluetooth management interface 1.9 initialized
Feb 14 18:05:19 MM-Home kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Feb 14 18:05:19 MM-Home kernel: Bluetooth: BNEP filters: protocol multicast
Feb 14 18:05:19 MM-Home kernel: Bluetooth: BNEP socket layer initialized
Feb 14 18:05:19 MM-Home dbus[958]: [system] Successfully activated service 'org.freedesktop.hostname1'
Feb 14 18:05:20 MM-Home kernel: fuse init (API version 7.23)
Feb 14 18:05:21 MM-Home dbus[958]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service'
Feb 14 18:05:21 MM-Home PackageKit[1962]: daemon start
Feb 14 18:05:22 MM-Home dbus[958]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Feb 14 18:05:23 MM-Home PackageKit[1962]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 18:05:23 MM-Home PackageKit[1962]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 18:05:23 MM-Home PackageKit[1962]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 18:05:23 MM-Home PackageKit[1962]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 18:05:24 MM-Home PackageKit[1962]: refresh-cache transaction /1_ceccaaed from uid 1000 finished with failed after 1477ms
Feb 14 18:05:24 MM-Home PackageKit[1962]: refresh-cache transaction /2_ddeeecbc from uid 1000 finished with failed after 278ms
Feb 14 18:05:43 MM-Home PackageKit[1962]: daemon quit
Feb 14 18:05:43 MM-Home packagekitd[1962]: (packagekitd:1962): GLib-CRITICAL **: Source ID 6 was not found when attempting to remove it
Feb 14 18:08:15 MM-Home kernel: nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
Feb 14 18:09:05 MM-Home polkitd[1081]: Unregistered Authentication Agent for unix-session:2 (system bus name :1.35, object path /org/kde/PolicyKit1/AuthenticationAgent, locale de_DE.UTF-8)
Feb 14 18:09:05 MM-Home bluetoothd[1910]: Terminating
Feb 14 18:09:05 MM-Home bluetoothd[1910]: Stopping SDP server
Feb 14 18:09:05 MM-Home bluetoothd[1910]: Exit
Feb 14 18:09:05 MM-Home avahi-daemon[959]: Got SIGTERM, quitting.
Feb 14 18:09:05 MM-Home avahi-daemon[959]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.178.12.
Feb 14 18:09:05 MM-Home smartd[965]: smartd received signal 15: Terminated
Feb 14 18:09:05 MM-Home smartd[965]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.SAMSUNG_SSD_830_Series-S0Z4NEAC906195.ata.state
Feb 14 18:09:05 MM-Home smartd[965]: Device: /dev/sdb [SAT], state written to /var/lib/smartmontools/smartd.TOSHIBA_HDWD110-Y5GDEMGFS.ata.state
Feb 14 18:09:05 MM-Home smartd[965]: smartd is exiting (exit status 0)
Feb 14 18:09:05 MM-Home avahi-daemon[959]: avahi-daemon 0.6.31 exiting.
Feb 14 18:09:05 MM-Home ModemManager[961]: <info>  Caught signal, shutting down...
Feb 14 18:09:05 MM-Home ModemManager[961]: <info>  ModemManager is shut down
Feb 14 18:09:05 MM-Home SuSEfirewall2[2166]: Not unloading firewall rules at system shutdown
Feb 14 18:09:05 MM-Home postfix/postfix-script[2173]: stopping the Postfix mail system
Feb 14 18:09:05 MM-Home sddm[1111]: Authentication error: "Process crashed"
Feb 14 18:09:05 MM-Home sddm[1111]: Auth: sddm-helper crashed (exit code 15)
Feb 14 18:09:05 MM-Home sddm[1111]: Authentication error: "Process crashed"
Feb 14 18:09:05 MM-Home sddm[1111]: Auth: sddm-helper exited with 15
Feb 14 18:09:05 MM-Home sddm[1111]: Socket server stopping...
Feb 14 18:09:05 MM-Home sddm[1111]: Socket server stopped.
Feb 14 18:09:05 MM-Home sddm[1111]: Display server stopping...
Feb 14 18:09:05 MM-Home postfix/master[1638]: terminating on signal 15
Feb 14 18:09:05 MM-Home ca.desrt.dconf[1744]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
Feb 14 18:09:05 MM-Home org.kde.kglobalaccel[1744]: The X11 connection broke: I/O error (code 1)
Feb 14 18:09:05 MM-Home org.kde.kglobalaccel[1744]: XIO:  fatal IO error 6 (Kein passendes Gerät bzw. keine passende Adresse gefunden) on X server ":0"
Feb 14 18:09:05 MM-Home org.kde.kglobalaccel[1744]: after 398 requests (396 known processed) with 0 events remaining.
Feb 14 18:09:05 MM-Home iscsiadm[2127]: iscsiadm: No matching sessions found
Feb 14 18:09:05 MM-Home wickedd-dhcp4[1068]: eth0: Request to release DHCPv4 lease with UUID b8b3c056-00ef-0c00-3804-000004000000
Feb 14 18:09:05 MM-Home sddm[1111]: Running display stop script  "/usr/share/sddm/scripts/Xstop"
Feb 14 18:09:05 MM-Home sddm[1111]: Removing display ":0" ...
Feb 14 18:09:05 MM-Home sddm[1111]: Adding new display on vt 7 ...
Feb 14 18:09:05 MM-Home sddm[1111]: Display server starting...
Feb 14 18:09:05 MM-Home sddm[1111]: Running: /usr/bin/X -nolisten tcp -auth /run/sddm/{664ddaa6-ee87-4591-b42c-166403a90bce} -background none -noreset -displayfd 18 vt7
Feb 14 18:09:06 MM-Home kernel: e1000e: eth0 NIC Link is Down
Feb 14 18:09:06 MM-Home wicked[2197]: eth0            device-ready
Feb 14 18:09:06 MM-Home sddm[1111]: Running display setup script  "/etc/X11/xdm/Xsetup"
Feb 14 18:09:10 MM-Home display-manager[2141]: Shutting down service sddm..done
Feb 14 18:09:36 MM-Home sddm[1111]: Display server started.
Feb 14 18:09:36 MM-Home sddm[1111]: Socket server starting...
Feb 14 18:09:36 MM-Home sddm[1111]: Socket server started.
Feb 14 18:09:36 MM-Home sddm[1111]: Greeter starting...
Feb 14 18:09:36 MM-Home sddm[1111]: Adding cookie to "/run/sddm/{664ddaa6-ee87-4591-b42c-166403a90bce}"
Feb 14 18:09:36 MM-Home sddm[1111]: Signal received: SIGTERM
Feb 14 18:09:36 MM-Home sddm[1111]: Socket server stopping...
Feb 14 18:09:36 MM-Home sddm[1111]: Socket server stopped.
Feb 14 18:09:36 MM-Home sddm[1111]: Display server stopping...
Feb 14 18:09:36 MM-Home sddm-helper[2348]: [PAM] Starting...
Feb 14 18:09:36 MM-Home sddm-helper[2348]: [PAM] Authenticating...
Feb 14 18:09:36 MM-Home sddm-helper[2348]: [PAM] returning.
Feb 14 18:09:37 MM-Home sddm[1111]: Display server stopped.
Feb 14 18:09:37 MM-Home sddm[1111]: Running display stop script  "/usr/share/sddm/scripts/Xstop"
Feb 14 18:09:37 MM-Home sddm[1111]: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.
Feb 14 18:09:37 MM-Home boot.apparmor[2364]: Unloading AppArmor profiles  ..done
Feb 14 18:09:37 MM-Home auditd[782]: The audit daemon is exiting.
Feb 14 18:09:37 MM-Home kernel: audit: type=1305 audit(1455469777.114:205): audit_pid=0 old=782 auid=4294967295 ses=4294967295 res=1
Feb 14 18:09:37 MM-Home kernel: audit: type=1131 audit(1455469777.114:206): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=' comm="auditd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 14 18:09:37 MM-Home umount[2401]: umount: /var/log: target is busy
Feb 14 18:09:37 MM-Home umount[2401]: (In some cases useful info about processes that
Feb 14 18:09:37 MM-Home umount[2401]: use the device is found by lsof(8) or fuser(1).)
Feb 14 18:09:37 MM-Home kernel: XFS (sdb4): Unmounting Filesystem
Feb 14 18:09:37 MM-Home kernel: audit: type=1131 audit(1455469777.242:207): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=' comm="systemd-remount-fs" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 14 18:09:37 MM-Home kernel: audit: type=1131 audit(1455469777.242:208): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=' comm="systemd-readahead-replay" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 14 18:09:37 MM-Home kernel: audit: type=1131 audit(1455469777.242:209): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=' comm="systemd-readahead-collect" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 14 18:09:37 MM-Home kernel: audit: type=1130 audit(1455469777.246:210): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=' comm="halt-local" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 14 18:09:37 MM-Home systemd-journal[482]: Journal stopped
-- Reboot --
Feb 14 19:11:18 linux-ytaf systemd-journal[187]: Runtime journal is using 8.0M (max allowed 394.0M, trying to leave 591.0M free of 3.8G available → current limit 394.0M).
Feb 14 19:11:18 linux-ytaf systemd-journal[187]: Runtime journal is using 8.0M (max allowed 394.0M, trying to leave 591.0M free of 3.8G available → current limit 394.0M).
Feb 14 19:11:18 linux-ytaf kernel: microcode: CPU0 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 19:11:18 linux-ytaf kernel: Initializing cgroup subsys cpuset
Feb 14 19:11:18 linux-ytaf kernel: Initializing cgroup subsys cpu
Feb 14 19:11:18 linux-ytaf kernel: Initializing cgroup subsys cpuacct
Feb 14 19:11:18 linux-ytaf kernel: Linux version 4.1.15-8-default (geeko@buildhost) (gcc version 4.8.5 (SUSE Linux) ) #1 SMP PREEMPT Wed Jan 20 16:41:00 UTC 2016 (0e3b3ab)
Feb 14 19:11:18 linux-ytaf kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.1.15-8-default root=UUID=21024970-7a27-4114-8525-d8dd026f23b6 ro resume=/dev/sdb2 splash=silent quiet showopts
Feb 14 19:11:18 linux-ytaf kernel: e820: BIOS-provided physical RAM map:
Feb 14 19:11:18 linux-ytaf kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Feb 14 19:11:18 linux-ytaf kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
Feb 14 19:11:18 linux-ytaf kernel: BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable
Feb 14 19:11:18 linux-ytaf kernel: BIOS-e820: [mem 0x0000000020000000-0x00000000201fffff] reserved
Feb 14 19:11:18 linux-ytaf kernel: BIOS-e820: [mem 0x0000000020200000-0x000000003fffffff] usable
Feb 14 19:11:18 linux-ytaf kernel: BIOS-e820: [mem 0x0000000040000000-0x00000000401fffff] reserved
Feb 14 19:11:18 linux-ytaf kernel: BIOS-e820: [mem 0x0000000040200000-0x00000000ca38efff] usable
Feb 14 19:11:18 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ca38f000-0x00000000ca5f1fff] reserved
Feb 14 19:11:18 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ca5f2000-0x00000000ca679fff] ACPI NVS
Feb 14 19:11:18 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ca67a000-0x00000000ca93efff] reserved
Feb 14 19:11:18 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ca93f000-0x00000000cab83fff] ACPI NVS
Feb 14 19:11:18 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cab84000-0x00000000cab91fff] ACPI data
Feb 14 19:11:18 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cab92000-0x00000000cabbefff] ACPI NVS
Feb 14 19:11:18 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cabbf000-0x00000000cabc3fff] ACPI data
Feb 14 19:11:18 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cabc4000-0x00000000cac06fff] ACPI NVS
Feb 14 19:11:18 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cac07000-0x00000000caffffff] usable
Feb 14 19:11:18 linux-ytaf kernel: BIOS-e820: [mem 0x00000000cb800000-0x00000000cf9fffff] reserved
Feb 14 19:11:18 linux-ytaf kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Feb 14 19:11:18 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Feb 14 19:11:18 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Feb 14 19:11:18 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Feb 14 19:11:18 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Feb 14 19:11:18 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Feb 14 19:11:18 linux-ytaf kernel: BIOS-e820: [mem 0x0000000100000000-0x000000022f5fffff] usable
Feb 14 19:11:18 linux-ytaf kernel: NX (Execute Disable) protection: active
Feb 14 19:11:18 linux-ytaf kernel: e820: update [mem 0x0c826018-0x0c835c57] usable ==> usable
Feb 14 19:11:18 linux-ytaf kernel: e820: update [mem 0x0c836018-0x0c846057] usable ==> usable
Feb 14 19:11:18 linux-ytaf kernel: e820: update [mem 0x0c847018-0x0c856857] usable ==> usable
Feb 14 19:11:18 linux-ytaf kernel: e820: update [mem 0x0c857018-0x0c85ae57] usable ==> usable
Feb 14 19:11:18 linux-ytaf kernel: extended physical RAM map:
Feb 14 19:11:18 linux-ytaf kernel: reserve setup_data: [mem 0x0000000000000000-0x000000000009efff] usable
Feb 14 19:11:18 linux-ytaf kernel: reserve setup_data: [mem 0x000000000009f000-0x000000000009ffff] reserved
Feb 14 19:11:18 linux-ytaf kernel: reserve setup_data: [mem 0x0000000000100000-0x000000000c826017] usable
Feb 14 19:11:18 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c826018-0x000000000c835c57] usable
Feb 14 19:11:18 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c835c58-0x000000000c836017] usable
Feb 14 19:11:18 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c836018-0x000000000c846057] usable
Feb 14 19:11:18 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c846058-0x000000000c847017] usable
Feb 14 19:11:18 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c847018-0x000000000c856857] usable
Feb 14 19:11:18 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c856858-0x000000000c857017] usable
Feb 14 19:11:18 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c857018-0x000000000c85ae57] usable
Feb 14 19:11:18 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c85ae58-0x000000001fffffff] usable
Feb 14 19:11:18 linux-ytaf kernel: reserve setup_data: [mem 0x0000000020000000-0x00000000201fffff] reserved
Feb 14 19:11:18 linux-ytaf kernel: reserve setup_data: [mem 0x0000000020200000-0x000000003fffffff] usable
Feb 14 19:11:18 linux-ytaf kernel: reserve setup_data: [mem 0x0000000040000000-0x00000000401fffff] reserved
Feb 14 19:11:18 linux-ytaf kernel: reserve setup_data: [mem 0x0000000040200000-0x00000000ca38efff] usable
Feb 14 19:11:18 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ca38f000-0x00000000ca5f1fff] reserved
Feb 14 19:11:18 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ca5f2000-0x00000000ca679fff] ACPI NVS
Feb 14 19:11:18 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ca67a000-0x00000000ca93efff] reserved
Feb 14 19:11:18 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ca93f000-0x00000000cab83fff] ACPI NVS
Feb 14 19:11:18 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cab84000-0x00000000cab91fff] ACPI data
Feb 14 19:11:18 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cab92000-0x00000000cabbefff] ACPI NVS
Feb 14 19:11:18 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cabbf000-0x00000000cabc3fff] ACPI data
Feb 14 19:11:18 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cabc4000-0x00000000cac06fff] ACPI NVS
Feb 14 19:11:18 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cac07000-0x00000000caffffff] usable
Feb 14 19:11:18 linux-ytaf kernel: reserve setup_data: [mem 0x00000000cb800000-0x00000000cf9fffff] reserved
Feb 14 19:11:18 linux-ytaf kernel: reserve setup_data: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Feb 14 19:11:18 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Feb 14 19:11:18 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Feb 14 19:11:18 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Feb 14 19:11:18 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Feb 14 19:11:18 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Feb 14 19:11:18 linux-ytaf kernel: reserve setup_data: [mem 0x0000000100000000-0x000000022f5fffff] usable
Feb 14 19:11:18 linux-ytaf kernel: efi: EFI v2.31 by American Megatrends
Feb 14 19:11:18 linux-ytaf kernel: efi:  ACPI=0xcab84000  ACPI 2.0=0xcab84000  SMBIOS=0xca427e98  MPS=0xfc990 
Feb 14 19:11:18 linux-ytaf kernel: SMBIOS 2.6 present.
Feb 14 19:11:18 linux-ytaf kernel: DMI: System manufacturer System Product Name/MAXIMUS IV GENE-Z/GEN3, BIOS 3603 11/09/2012
Feb 14 19:11:18 linux-ytaf kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Feb 14 19:11:18 linux-ytaf kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Feb 14 19:11:18 linux-ytaf kernel: AGP: No AGP bridge found
Feb 14 19:11:18 linux-ytaf kernel: e820: last_pfn = 0x22f600 max_arch_pfn = 0x400000000
Feb 14 19:11:18 linux-ytaf kernel: MTRR default type: uncachable
Feb 14 19:11:18 linux-ytaf kernel: MTRR fixed ranges enabled:
Feb 14 19:11:18 linux-ytaf kernel:   00000-9FFFF write-back
Feb 14 19:11:18 linux-ytaf kernel:   A0000-BFFFF uncachable
Feb 14 19:11:18 linux-ytaf kernel:   C0000-D3FFF write-protect
Feb 14 19:11:18 linux-ytaf kernel:   D4000-DFFFF uncachable
Feb 14 19:11:18 linux-ytaf kernel:   E0000-E7FFF write-through
Feb 14 19:11:18 linux-ytaf kernel:   E8000-FFFFF write-protect
Feb 14 19:11:18 linux-ytaf kernel: MTRR variable ranges enabled:
Feb 14 19:11:18 linux-ytaf kernel:   0 base 000000000 mask E00000000 write-back
Feb 14 19:11:18 linux-ytaf kernel:   1 base 200000000 mask FE0000000 write-back
Feb 14 19:11:18 linux-ytaf kernel:   2 base 220000000 mask FF0000000 write-back
Feb 14 19:11:18 linux-ytaf kernel:   3 base 0E0000000 mask FE0000000 uncachable
Feb 14 19:11:18 linux-ytaf kernel:   4 base 0D0000000 mask FF0000000 uncachable
Feb 14 19:11:18 linux-ytaf kernel:   5 base 0CC000000 mask FFC000000 uncachable
Feb 14 19:11:18 linux-ytaf kernel:   6 base 0CB800000 mask FFF800000 uncachable
Feb 14 19:11:18 linux-ytaf kernel:   7 base 22F800000 mask FFF800000 uncachable
Feb 14 19:11:18 linux-ytaf kernel:   8 base 22F600000 mask FFFE00000 uncachable
Feb 14 19:11:18 linux-ytaf kernel:   9 disabled
Feb 14 19:11:18 linux-ytaf kernel: PAT configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- UC  
Feb 14 19:11:18 linux-ytaf kernel: e820: update [mem 0xcb800000-0xffffffff] usable ==> reserved
Feb 14 19:11:18 linux-ytaf kernel: e820: last_pfn = 0xcb000 max_arch_pfn = 0x400000000
Feb 14 19:11:18 linux-ytaf kernel: found SMP MP-table at [mem 0x000fcd30-0x000fcd3f] mapped at [ffff8800000fcd30]
Feb 14 19:11:18 linux-ytaf kernel: Scanning 1 areas for low memory corruption
Feb 14 19:11:18 linux-ytaf kernel: Base memory trampoline at [ffff880000097000] 97000 size 24576
Feb 14 19:11:18 linux-ytaf kernel: reserving inaccessible SNB gfx pages
Feb 14 19:11:18 linux-ytaf kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
Feb 14 19:11:18 linux-ytaf kernel:  [mem 0x00000000-0x000fffff] page 4k
Feb 14 19:11:18 linux-ytaf kernel: BRK [0x0e21a000, 0x0e21afff] PGTABLE
Feb 14 19:11:18 linux-ytaf kernel: BRK [0x0e21b000, 0x0e21bfff] PGTABLE
Feb 14 19:11:18 linux-ytaf kernel: BRK [0x0e21c000, 0x0e21cfff] PGTABLE
Feb 14 19:11:18 linux-ytaf kernel: init_memory_mapping: [mem 0x22f400000-0x22f5fffff]
Feb 14 19:11:18 linux-ytaf kernel:  [mem 0x22f400000-0x22f5fffff] page 2M
Feb 14 19:11:18 linux-ytaf kernel: BRK [0x0e21d000, 0x0e21dfff] PGTABLE
Feb 14 19:11:18 linux-ytaf kernel: init_memory_mapping: [mem 0x220000000-0x22f3fffff]
Feb 14 19:11:18 linux-ytaf kernel:  [mem 0x220000000-0x22f3fffff] page 2M
Feb 14 19:11:18 linux-ytaf kernel: init_memory_mapping: [mem 0x200000000-0x21fffffff]
Feb 14 19:11:18 linux-ytaf kernel:  [mem 0x200000000-0x21fffffff] page 2M
Feb 14 19:11:18 linux-ytaf kernel: init_memory_mapping: [mem 0x00100000-0x1fffffff]
Feb 14 19:11:18 linux-ytaf kernel:  [mem 0x00100000-0x001fffff] page 4k
Feb 14 19:11:18 linux-ytaf kernel:  [mem 0x00200000-0x1fffffff] page 2M
Feb 14 19:11:18 linux-ytaf kernel: init_memory_mapping: [mem 0x20200000-0x3fffffff]
Feb 14 19:11:18 linux-ytaf kernel:  [mem 0x20200000-0x3fffffff] page 2M
Feb 14 19:11:18 linux-ytaf kernel: init_memory_mapping: [mem 0x40200000-0xca38efff]
Feb 14 19:11:18 linux-ytaf kernel:  [mem 0x40200000-0xca1fffff] page 2M
Feb 14 19:11:18 linux-ytaf kernel:  [mem 0xca200000-0xca38efff] page 4k
Feb 14 19:11:18 linux-ytaf kernel: BRK [0x0e21e000, 0x0e21efff] PGTABLE
Feb 14 19:11:18 linux-ytaf kernel: BRK [0x0e21f000, 0x0e21ffff] PGTABLE
Feb 14 19:11:18 linux-ytaf kernel: init_memory_mapping: [mem 0xcac07000-0xcaffffff]
Feb 14 19:11:18 linux-ytaf kernel:  [mem 0xcac07000-0xcadfffff] page 4k
Feb 14 19:11:18 linux-ytaf kernel:  [mem 0xcae00000-0xcaffffff] page 2M
Feb 14 19:11:18 linux-ytaf kernel: init_memory_mapping: [mem 0x100000000-0x1ffffffff]
Feb 14 19:11:18 linux-ytaf kernel:  [mem 0x100000000-0x1ffffffff] page 2M
Feb 14 19:11:18 linux-ytaf kernel: RAMDISK: [mem 0x00457000-0x00ffafff]
Feb 14 19:11:18 linux-ytaf kernel: ACPI: Early table checksum verification disabled
Feb 14 19:11:18 linux-ytaf kernel: ACPI: RSDP 0x00000000CAB84000 000024 (v02 ALASKA)
Feb 14 19:11:18 linux-ytaf kernel: ACPI: XSDT 0x00000000CAB84078 000064 (v01 ALASKA A M I    01072009 AMI  00010013)
Feb 14 19:11:18 linux-ytaf kernel: ACPI: FACP 0x00000000CAB8FC78 0000F4 (v04 ALASKA A M I    01072009 AMI  00010013)
Feb 14 19:11:18 linux-ytaf kernel: ACPI: DSDT 0x00000000CAB84170 00BB02 (v02 ALASKA A M I    00000015 INTL 20051117)
Feb 14 19:11:18 linux-ytaf kernel: ACPI: FACS 0x00000000CABBDF80 000040
Feb 14 19:11:18 linux-ytaf kernel: ACPI: APIC 0x00000000CAB8FD70 000092 (v03 ALASKA A M I    01072009 AMI  00010013)
Feb 14 19:11:18 linux-ytaf kernel: ACPI: MCFG 0x00000000CAB8FE08 00003C (v01 ALASKA A M I    01072009 MSFT 00000097)
Feb 14 19:11:18 linux-ytaf kernel: ACPI: HPET 0x00000000CAB8FE48 000038 (v01 ALASKA A M I    01072009 AMI. 00000005)
Feb 14 19:11:18 linux-ytaf kernel: ACPI: SSDT 0x00000000CAB8FE80 00036D (v01 SataRe SataTabl 00001000 INTL 20091112)
Feb 14 19:11:18 linux-ytaf kernel: ACPI: SSDT 0x00000000CAB901F0 0009AA (v01 PmRef  Cpu0Ist  00003000 INTL 20051117)
Feb 14 19:11:18 linux-ytaf kernel: ACPI: SSDT 0x00000000CAB90BA0 000A92 (v01 PmRef  CpuPm    00003000 INTL 20051117)
Feb 14 19:11:18 linux-ytaf kernel: ACPI: BGRT 0x00000000CAB91690 000038 (v00 ALASKA A M I    01072009 AMI  00010013)
Feb 14 19:11:18 linux-ytaf kernel: ACPI: Local APIC address 0xfee00000
Feb 14 19:11:18 linux-ytaf kernel: No NUMA configuration found
Feb 14 19:11:18 linux-ytaf kernel: Faking a node at [mem 0x0000000000000000-0x000000022f5fffff]
Feb 14 19:11:18 linux-ytaf kernel: NODE_DATA(0) allocated [mem 0x22f5e5000-0x22f5f8fff]
Feb 14 19:11:18 linux-ytaf kernel:  [ffffea0000000000-ffffea0008bfffff] PMD -> [ffff880226c00000-ffff88022ebfffff] on node 0
Feb 14 19:11:18 linux-ytaf kernel: Zone ranges:
Feb 14 19:11:18 linux-ytaf kernel:   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
Feb 14 19:11:18 linux-ytaf kernel:   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
Feb 14 19:11:18 linux-ytaf kernel:   Normal   [mem 0x0000000100000000-0x000000022f5fffff]
Feb 14 19:11:18 linux-ytaf kernel: Movable zone start for each node
Feb 14 19:11:18 linux-ytaf kernel: Early memory node ranges
Feb 14 19:11:18 linux-ytaf kernel:   node   0: [mem 0x0000000000001000-0x000000000009efff]
Feb 14 19:11:18 linux-ytaf kernel:   node   0: [mem 0x0000000000100000-0x000000001fffffff]
Feb 14 19:11:18 linux-ytaf kernel:   node   0: [mem 0x0000000020200000-0x000000003fffffff]
Feb 14 19:11:18 linux-ytaf kernel:   node   0: [mem 0x0000000040200000-0x00000000ca38efff]
Feb 14 19:11:18 linux-ytaf kernel:   node   0: [mem 0x00000000cac07000-0x00000000caffffff]
Feb 14 19:11:18 linux-ytaf kernel:   node   0: [mem 0x0000000100000000-0x000000022f5fffff]
Feb 14 19:11:18 linux-ytaf kernel: Initmem setup node 0 [mem 0x0000000000001000-0x000000022f5fffff]
Feb 14 19:11:18 linux-ytaf kernel: On node 0 totalpages: 2070822
Feb 14 19:11:18 linux-ytaf kernel:   DMA zone: 64 pages used for memmap
Feb 14 19:11:18 linux-ytaf kernel:   DMA zone: 3138 pages reserved
Feb 14 19:11:18 linux-ytaf kernel:   DMA zone: 3998 pages, LIFO batch:0
Feb 14 19:11:18 linux-ytaf kernel:   DMA32 zone: 12879 pages used for memmap
Feb 14 19:11:18 linux-ytaf kernel:   DMA32 zone: 824200 pages, LIFO batch:31
Feb 14 19:11:18 linux-ytaf kernel:   Normal zone: 19416 pages used for memmap
Feb 14 19:11:18 linux-ytaf kernel:   Normal zone: 1242624 pages, LIFO batch:31
Feb 14 19:11:18 linux-ytaf kernel: tboot: non-0 tboot_addr but it is not of type E820_RESERVED
Feb 14 19:11:18 linux-ytaf kernel: ACPI: PM-Timer IO Port: 0x408
Feb 14 19:11:18 linux-ytaf kernel: ACPI: Local APIC address 0xfee00000
Feb 14 19:11:18 linux-ytaf kernel: ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
Feb 14 19:11:18 linux-ytaf kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
Feb 14 19:11:18 linux-ytaf kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Feb 14 19:11:18 linux-ytaf kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Feb 14 19:11:18 linux-ytaf kernel: ACPI: IRQ0 used by override.
Feb 14 19:11:18 linux-ytaf kernel: ACPI: IRQ9 used by override.
Feb 14 19:11:18 linux-ytaf kernel: Using ACPI (MADT) for SMP configuration information
Feb 14 19:11:18 linux-ytaf kernel: ACPI: HPET id: 0x8086a701 base: 0xfed00000
Feb 14 19:11:18 linux-ytaf kernel: smpboot: Allowing 8 CPUs, 0 hotplug CPUs
Feb 14 19:11:18 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
Feb 14 19:11:18 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Feb 14 19:11:18 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000fffff]
Feb 14 19:11:18 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c826000-0x0c826fff]
Feb 14 19:11:18 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c835000-0x0c835fff]
Feb 14 19:11:18 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c836000-0x0c836fff]
Feb 14 19:11:18 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c846000-0x0c846fff]
Feb 14 19:11:18 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c847000-0x0c847fff]
Feb 14 19:11:18 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c856000-0x0c856fff]
Feb 14 19:11:18 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c857000-0x0c857fff]
Feb 14 19:11:18 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c85a000-0x0c85afff]
Feb 14 19:11:18 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x20000000-0x201fffff]
Feb 14 19:11:18 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x40000000-0x401fffff]
Feb 14 19:11:18 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xca38f000-0xca5f1fff]
Feb 14 19:11:18 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xca5f2000-0xca679fff]
Feb 14 19:11:18 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xca67a000-0xca93efff]
Feb 14 19:11:18 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xca93f000-0xcab83fff]
Feb 14 19:11:18 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcab84000-0xcab91fff]
Feb 14 19:11:18 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcab92000-0xcabbefff]
Feb 14 19:11:18 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcabbf000-0xcabc3fff]
Feb 14 19:11:18 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcabc4000-0xcac06fff]
Feb 14 19:11:18 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcb000000-0xcb7fffff]
Feb 14 19:11:18 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcb800000-0xcf9fffff]
Feb 14 19:11:18 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xcfa00000-0xf7ffffff]
Feb 14 19:11:18 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
Feb 14 19:11:18 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfc000000-0xfebfffff]
Feb 14 19:11:18 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
Feb 14 19:11:18 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfec01000-0xfecfffff]
Feb 14 19:11:18 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed00000-0xfed03fff]
Feb 14 19:11:18 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed04000-0xfed1bfff]
Feb 14 19:11:18 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Feb 14 19:11:18 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed20000-0xfedfffff]
Feb 14 19:11:18 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
Feb 14 19:11:18 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfee01000-0xfeffffff]
Feb 14 19:11:18 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Feb 14 19:11:18 linux-ytaf kernel: e820: [mem 0xcfa00000-0xf7ffffff] available for PCI devices
Feb 14 19:11:18 linux-ytaf kernel: Booting paravirtualized kernel on bare hardware
Feb 14 19:11:18 linux-ytaf kernel: clocksource refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
Feb 14 19:11:18 linux-ytaf kernel: setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:8 nr_node_ids:1
Feb 14 19:11:18 linux-ytaf kernel: PERCPU: Embedded 33 pages/cpu @ffff88022f200000 s97368 r8192 d29608 u262144
Feb 14 19:11:18 linux-ytaf kernel: pcpu-alloc: s97368 r8192 d29608 u262144 alloc=1*2097152
Feb 14 19:11:18 linux-ytaf kernel: pcpu-alloc: [0] 0 1 2 3 4 5 6 7 
Feb 14 19:11:18 linux-ytaf kernel: Built 1 zonelists in Node order, mobility grouping on.  Total pages: 2035325
Feb 14 19:11:18 linux-ytaf kernel: Policy zone: Normal
Feb 14 19:11:18 linux-ytaf kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.1.15-8-default root=UUID=21024970-7a27-4114-8525-d8dd026f23b6 ro resume=/dev/sdb2 splash=silent quiet showopts
Feb 14 19:11:18 linux-ytaf kernel: log_buf_len individual max cpu contribution: 32768 bytes
Feb 14 19:11:18 linux-ytaf kernel: log_buf_len total cpu_extra contributions: 229376 bytes
Feb 14 19:11:18 linux-ytaf kernel: log_buf_len min size: 262144 bytes
Feb 14 19:11:18 linux-ytaf kernel: log_buf_len: 524288 bytes
Feb 14 19:11:18 linux-ytaf kernel: early log buf free: 245492(93%)
Feb 14 19:11:18 linux-ytaf kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
Feb 14 19:11:18 linux-ytaf kernel: xsave: enabled xstate_bv 0x7, cntxt size 0x340 using standard form
Feb 14 19:11:18 linux-ytaf kernel: AGP: Checking aperture...
Feb 14 19:11:18 linux-ytaf kernel: AGP: No AGP bridge found
Feb 14 19:11:18 linux-ytaf kernel: Memory: 7863196K/8283288K available (6547K kernel code, 1084K rwdata, 4848K rodata, 1560K init, 1516K bss, 420092K reserved, 0K cma-reserved)
Feb 14 19:11:18 linux-ytaf kernel: Preemptible hierarchical RCU implementation.
Feb 14 19:11:18 linux-ytaf kernel:         RCU dyntick-idle grace-period acceleration is enabled.
Feb 14 19:11:18 linux-ytaf kernel:         RCU restricting CPUs from NR_CPUS=512 to nr_cpu_ids=8.
Feb 14 19:11:18 linux-ytaf kernel: RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
Feb 14 19:11:18 linux-ytaf kernel: NR_IRQS:33024 nr_irqs:488 16
Feb 14 19:11:18 linux-ytaf kernel:         Offload RCU callbacks from all CPUs
Feb 14 19:11:18 linux-ytaf kernel:         Offload RCU callbacks from CPUs: 0-7.
Feb 14 19:11:18 linux-ytaf kernel: Console: colour dummy device 80x25
Feb 14 19:11:18 linux-ytaf kernel: console [tty0] enabled
Feb 14 19:11:18 linux-ytaf kernel: clocksource hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484882848 ns
Feb 14 19:11:18 linux-ytaf kernel: hpet clockevent registered
Feb 14 19:11:18 linux-ytaf kernel: tsc: Fast TSC calibration using PIT
Feb 14 19:11:18 linux-ytaf kernel: tsc: Detected 3411.095 MHz processor
Feb 14 19:11:18 linux-ytaf kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 6822.19 BogoMIPS (lpj=13644380)
Feb 14 19:11:18 linux-ytaf kernel: pid_max: default: 32768 minimum: 301
Feb 14 19:11:18 linux-ytaf kernel: ACPI: Core revision 20150410
Feb 14 19:11:18 linux-ytaf kernel: ACPI: All ACPI Tables successfully acquired
Feb 14 19:11:18 linux-ytaf kernel: Security Framework initialized
Feb 14 19:11:18 linux-ytaf kernel: AppArmor: AppArmor initialized
Feb 14 19:11:18 linux-ytaf kernel: Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
Feb 14 19:11:18 linux-ytaf kernel: Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
Feb 14 19:11:18 linux-ytaf kernel: Mount-cache hash table entries: 16384 (order: 5, 131072 bytes)
Feb 14 19:11:18 linux-ytaf kernel: Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes)
Feb 14 19:11:18 linux-ytaf kernel: Initializing cgroup subsys blkio
Feb 14 19:11:18 linux-ytaf kernel: Initializing cgroup subsys memory
Feb 14 19:11:18 linux-ytaf kernel: Initializing cgroup subsys devices
Feb 14 19:11:18 linux-ytaf kernel: Initializing cgroup subsys freezer
Feb 14 19:11:18 linux-ytaf kernel: Initializing cgroup subsys net_cls
Feb 14 19:11:18 linux-ytaf kernel: Initializing cgroup subsys perf_event
Feb 14 19:11:18 linux-ytaf kernel: Initializing cgroup subsys net_prio
Feb 14 19:11:18 linux-ytaf kernel: Initializing cgroup subsys hugetlb
Feb 14 19:11:18 linux-ytaf kernel: CPU: Physical Processor ID: 0
Feb 14 19:11:18 linux-ytaf kernel: CPU: Processor Core ID: 0
Feb 14 19:11:18 linux-ytaf kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Feb 14 19:11:18 linux-ytaf kernel: ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Feb 14 19:11:18 linux-ytaf kernel: mce: CPU supports 9 MCE banks
Feb 14 19:11:18 linux-ytaf kernel: CPU0: Thermal monitoring enabled (TM1)
Feb 14 19:11:18 linux-ytaf kernel: process: using mwait in idle threads
Feb 14 19:11:18 linux-ytaf kernel: Last level iTLB entries: 4KB 512, 2MB 8, 4MB 8
Feb 14 19:11:18 linux-ytaf kernel: Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32, 1GB 0
Feb 14 19:11:18 linux-ytaf kernel: Freeing SMP alternatives memory: 24K (ffffffff82097000 - ffffffff8209d000)
Feb 14 19:11:18 linux-ytaf kernel: ftrace: allocating 25000 entries in 98 pages
Feb 14 19:11:18 linux-ytaf kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Feb 14 19:11:18 linux-ytaf kernel: TSC deadline timer enabled
Feb 14 19:11:18 linux-ytaf kernel: smpboot: CPU0: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz (fam: 06, model: 2a, stepping: 07)
Feb 14 19:11:18 linux-ytaf kernel: Performance Events: PEBS fmt1+, 16-deep LBR, SandyBridge events, full-width counters, Intel PMU driver.
Feb 14 19:11:18 linux-ytaf kernel: ... version:                3
Feb 14 19:11:18 linux-ytaf kernel: ... bit width:              48
Feb 14 19:11:18 linux-ytaf kernel: ... generic registers:      4
Feb 14 19:11:18 linux-ytaf kernel: ... value mask:             0000ffffffffffff
Feb 14 19:11:18 linux-ytaf kernel: ... max period:             0000ffffffffffff
Feb 14 19:11:18 linux-ytaf kernel: ... fixed-purpose events:   3
Feb 14 19:11:18 linux-ytaf kernel: ... event mask:             000000070000000f
Feb 14 19:11:18 linux-ytaf kernel: x86: Booting SMP configuration:
Feb 14 19:11:18 linux-ytaf kernel: .... node  #0, CPUs:      #1
Feb 14 19:11:18 linux-ytaf kernel: microcode: CPU1 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 19:11:18 linux-ytaf kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Feb 14 19:11:18 linux-ytaf kernel:  #2
Feb 14 19:11:18 linux-ytaf kernel: microcode: CPU2 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 19:11:18 linux-ytaf kernel:  #3
Feb 14 19:11:18 linux-ytaf kernel: microcode: CPU3 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 19:11:18 linux-ytaf kernel:  #4 #5 #6 #7
Feb 14 19:11:18 linux-ytaf kernel: x86: Booted up 1 node, 8 CPUs
Feb 14 19:11:18 linux-ytaf kernel: smpboot: Total of 8 processors activated (54577.52 BogoMIPS)
Feb 14 19:11:18 linux-ytaf kernel: devtmpfs: initialized
Feb 14 19:11:18 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xca5f2000-0xca679fff] (557056 bytes)
Feb 14 19:11:18 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xca93f000-0xcab83fff] (2379776 bytes)
Feb 14 19:11:18 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xcab92000-0xcabbefff] (184320 bytes)
Feb 14 19:11:18 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xcabc4000-0xcac06fff] (274432 bytes)
Feb 14 19:11:18 linux-ytaf kernel: clocksource jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
Feb 14 19:11:18 linux-ytaf kernel: pinctrl core: initialized pinctrl subsystem
Feb 14 19:11:18 linux-ytaf kernel: RTC time: 19:11:14, date: 02/14/16
Feb 14 19:11:18 linux-ytaf kernel: NET: Registered protocol family 16
Feb 14 19:11:18 linux-ytaf kernel: cpuidle: using governor ladder
Feb 14 19:11:18 linux-ytaf kernel: cpuidle: using governor menu
Feb 14 19:11:18 linux-ytaf kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
Feb 14 19:11:18 linux-ytaf kernel: ACPI: bus type PCI registered
Feb 14 19:11:18 linux-ytaf kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Feb 14 19:11:18 linux-ytaf kernel: PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
Feb 14 19:11:18 linux-ytaf kernel: PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
Feb 14 19:11:18 linux-ytaf kernel: PCI: Using configuration type 1 for base access
Feb 14 19:11:18 linux-ytaf kernel: perf_event_intel: PMU erratum BJ122, BV98, HSD29 worked around, HT is on
Feb 14 19:11:18 linux-ytaf kernel: ACPI: Added _OSI(Module Device)
Feb 14 19:11:18 linux-ytaf kernel: ACPI: Added _OSI(Processor Device)
Feb 14 19:11:18 linux-ytaf kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
Feb 14 19:11:18 linux-ytaf kernel: ACPI: Added _OSI(Processor Aggregator Device)
Feb 14 19:11:18 linux-ytaf kernel: ACPI: Executed 1 blocks of module-level executable AML code
Feb 14 19:11:18 linux-ytaf kernel: ACPI: Dynamic OEM Table Load:
Feb 14 19:11:18 linux-ytaf kernel: ACPI: SSDT 0xFFFF8802257C7000 00083B (v01 PmRef  Cpu0Cst  00003001 INTL 20051117)
Feb 14 19:11:18 linux-ytaf kernel: ACPI: Dynamic OEM Table Load:
Feb 14 19:11:18 linux-ytaf kernel: ACPI: SSDT 0xFFFF8802257C1400 000303 (v01 PmRef  ApIst    00003000 INTL 20051117)
Feb 14 19:11:18 linux-ytaf kernel: ACPI: Dynamic OEM Table Load:
Feb 14 19:11:18 linux-ytaf kernel: ACPI: SSDT 0xFFFF880225774600 000119 (v01 PmRef  ApCst    00003000 INTL 20051117)
Feb 14 19:11:18 linux-ytaf kernel: ACPI : EC: EC started
Feb 14 19:11:18 linux-ytaf kernel: ACPI: Interpreter enabled
Feb 14 19:11:18 linux-ytaf kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20150410/hwxface-580)
Feb 14 19:11:18 linux-ytaf kernel: ACPI: (supports S0 S1 S3 S4 S5)
Feb 14 19:11:18 linux-ytaf kernel: ACPI: Using IOAPIC for interrupt routing
Feb 14 19:11:18 linux-ytaf kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Feb 14 19:11:18 linux-ytaf kernel: ACPI: Power Resource [FN00] (off)
Feb 14 19:11:18 linux-ytaf kernel: ACPI: Power Resource [FN01] (off)
Feb 14 19:11:18 linux-ytaf kernel: ACPI: Power Resource [FN02] (off)
Feb 14 19:11:18 linux-ytaf kernel: ACPI: Power Resource [FN03] (off)
Feb 14 19:11:18 linux-ytaf kernel: ACPI: Power Resource [FN04] (off)
Feb 14 19:11:18 linux-ytaf kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
Feb 14 19:11:18 linux-ytaf kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Feb 14 19:11:18 linux-ytaf kernel: \_SB_.PCI0:_OSC invalid UUID
Feb 14 19:11:18 linux-ytaf kernel: _OSC request data:1 1f 0 
Feb 14 19:11:18 linux-ytaf kernel: acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
Feb 14 19:11:18 linux-ytaf kernel: PCI host bridge to bus 0000:00
Feb 14 19:11:18 linux-ytaf kernel: pci_bus 0000:00: root bus resource [bus 00-3e]
Feb 14 19:11:18 linux-ytaf kernel: pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
Feb 14 19:11:18 linux-ytaf kernel: pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
Feb 14 19:11:18 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
Feb 14 19:11:18 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff window]
Feb 14 19:11:18 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff window]
Feb 14 19:11:18 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff window]
Feb 14 19:11:18 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0xcfa00000-0xfeafffff window]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:00.0: [8086:0100] type 00 class 0x060000
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:01.0: [8086:0101] type 01 class 0x060400
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:01.0: System wakeup disabled by ACPI
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:01.1: [8086:0105] type 01 class 0x060400
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:01.1: PME# supported from D0 D3hot D3cold
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:01.1: System wakeup disabled by ACPI
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:02.0: [8086:0122] type 00 class 0x038000
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:02.0: reg 0x10: [mem 0xf7400000-0xf77fffff 64bit]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:02.0: reg 0x18: [mem 0xd0000000-0xdfffffff 64bit pref]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:02.0: reg 0x20: [io  0xf000-0xf03f]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:16.0: [8086:1c3a] type 00 class 0x078000
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:16.0: reg 0x10: [mem 0xf7b2c000-0xf7b2c00f 64bit]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:19.0: [8086:1503] type 00 class 0x020000
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:19.0: reg 0x10: [mem 0xf7b00000-0xf7b1ffff]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:19.0: reg 0x14: [mem 0xf7b29000-0xf7b29fff]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:19.0: reg 0x18: [io  0xf080-0xf09f]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:19.0: PME# supported from D0 D3hot D3cold
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:19.0: System wakeup disabled by ACPI
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1a.0: [8086:1c2d] type 00 class 0x0c0320
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1a.0: reg 0x10: [mem 0xf7b28000-0xf7b283ff]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1a.0: System wakeup disabled by ACPI
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1b.0: [8086:1c20] type 00 class 0x040300
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1b.0: reg 0x10: [mem 0xf7b20000-0xf7b23fff 64bit]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1b.0: System wakeup disabled by ACPI
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.0: [8086:1c10] type 01 class 0x060400
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.0: System wakeup disabled by ACPI
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.4: [8086:1c18] type 01 class 0x060400
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.4: System wakeup disabled by ACPI
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.5: [8086:1c1a] type 01 class 0x060400
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.5: System wakeup disabled by ACPI
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.6: [8086:1c1c] type 01 class 0x060400
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.6: PME# supported from D0 D3hot D3cold
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.6: System wakeup disabled by ACPI
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1d.0: [8086:1c26] type 00 class 0x0c0320
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1d.0: reg 0x10: [mem 0xf7b27000-0xf7b273ff]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1d.0: System wakeup disabled by ACPI
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1f.0: [8086:1c44] type 00 class 0x060100
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1f.2: [8086:1c02] type 00 class 0x010601
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x10: [io  0xf0d0-0xf0d7]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x14: [io  0xf0c0-0xf0c3]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x18: [io  0xf0b0-0xf0b7]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x1c: [io  0xf0a0-0xf0a3]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x20: [io  0xf060-0xf07f]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x24: [mem 0xf7b26000-0xf7b267ff]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1f.2: PME# supported from D3hot
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1f.3: [8086:1c22] type 00 class 0x0c0500
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1f.3: reg 0x10: [mem 0xf7b25000-0xf7b250ff 64bit]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1f.3: reg 0x20: [io  0x0580-0x059f]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:02:00.0: [10de:1183] type 00 class 0x030000
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:02:00.0: reg 0x10: [mem 0xf6000000-0xf6ffffff]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:02:00.0: reg 0x14: [mem 0xe0000000-0xe7ffffff 64bit pref]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:02:00.0: reg 0x1c: [mem 0xe8000000-0xe9ffffff 64bit pref]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:02:00.0: reg 0x24: [io  0xe000-0xe07f]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:02:00.0: reg 0x30: [mem 0xf7000000-0xf707ffff pref]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:02:00.1: [10de:0e0a] type 00 class 0x040300
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:02:00.1: reg 0x10: [mem 0xf7080000-0xf7083fff]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:01.1: PCI bridge to [bus 02]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [io  0xe000-0xefff]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xf6000000-0xf70fffff]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xe0000000-0xe9ffffff 64bit pref]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.0: PCI bridge to [bus 03]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:04:00.0: [1b21:1042] type 00 class 0x0c0330
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:04:00.0: reg 0x10: [mem 0xf7a00000-0xf7a07fff 64bit]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:04:00.0: PME# supported from D3hot D3cold
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:04:00.0: System wakeup disabled by ACPI
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.4: PCI bridge to [bus 04]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.4:   bridge window [mem 0xf7a00000-0xf7afffff]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:05:00.0: [1b21:1042] type 00 class 0x0c0330
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:05:00.0: reg 0x10: [mem 0xf7900000-0xf7907fff 64bit]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:05:00.0: PME# supported from D3hot D3cold
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:05:00.0: System wakeup disabled by ACPI
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.5: PCI bridge to [bus 05]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.5:   bridge window [mem 0xf7900000-0xf79fffff]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:06:00.0: [197b:2362] type 00 class 0x010185
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:06:00.0: reg 0x10: [io  0xd040-0xd047]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:06:00.0: reg 0x14: [io  0xd030-0xd033]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:06:00.0: reg 0x18: [io  0xd020-0xd027]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:06:00.0: reg 0x1c: [io  0xd010-0xd013]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:06:00.0: reg 0x20: [io  0xd000-0xd00f]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:06:00.0: reg 0x24: [mem 0xf7810000-0xf78101ff]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:06:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:06:00.0: PME# supported from D3hot
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:06:00.0: System wakeup disabled by ACPI
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.6: PCI bridge to [bus 06]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [io  0xd000-0xdfff]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [mem 0xf7800000-0xf78fffff]
Feb 14 19:11:18 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15)
Feb 14 19:11:18 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *10 11 12 14 15)
Feb 14 19:11:18 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Feb 14 19:11:18 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs *3 4 5 6 10 11 12 14 15)
Feb 14 19:11:18 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 *4 5 6 10 11 12 14 15)
Feb 14 19:11:18 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
Feb 14 19:11:18 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 *11 12 14 15)
Feb 14 19:11:18 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 *10 11 12 14 15)
Feb 14 19:11:18 linux-ytaf kernel: ACPI: Enabled 6 GPEs in block 00 to 3F
Feb 14 19:11:18 linux-ytaf kernel: ACPI : EC: GPE = 0x18, I/O: command/status = 0x66, data = 0x62
Feb 14 19:11:18 linux-ytaf kernel: vgaarb: setting as boot device: PCI:0000:02:00.0
Feb 14 19:11:18 linux-ytaf kernel: vgaarb: device added: PCI:0000:02:00.0,decodes=io+mem,owns=io+mem,locks=none
Feb 14 19:11:18 linux-ytaf kernel: vgaarb: loaded
Feb 14 19:11:18 linux-ytaf kernel: vgaarb: bridge control possible 0000:02:00.0
Feb 14 19:11:18 linux-ytaf kernel: SCSI subsystem initialized
Feb 14 19:11:18 linux-ytaf kernel: libata version 3.00 loaded.
Feb 14 19:11:18 linux-ytaf kernel: PCI: Using ACPI for IRQ routing
Feb 14 19:11:18 linux-ytaf kernel: PCI: pci_cache_line_size set to 64 bytes
Feb 14 19:11:18 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0009f000-0x0009ffff]
Feb 14 19:11:18 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c826018-0x0fffffff]
Feb 14 19:11:18 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c836018-0x0fffffff]
Feb 14 19:11:18 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c847018-0x0fffffff]
Feb 14 19:11:18 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c857018-0x0fffffff]
Feb 14 19:11:18 linux-ytaf kernel: e820: reserve RAM buffer [mem 0xca38f000-0xcbffffff]
Feb 14 19:11:18 linux-ytaf kernel: e820: reserve RAM buffer [mem 0xcb000000-0xcbffffff]
Feb 14 19:11:18 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x22f600000-0x22fffffff]
Feb 14 19:11:18 linux-ytaf kernel: NetLabel: Initializing
Feb 14 19:11:18 linux-ytaf kernel: NetLabel:  domain hash size = 128
Feb 14 19:11:18 linux-ytaf kernel: NetLabel:  protocols = UNLABELED CIPSOv4
Feb 14 19:11:18 linux-ytaf kernel: NetLabel:  unlabeled traffic allowed by default
Feb 14 19:11:18 linux-ytaf kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Feb 14 19:11:18 linux-ytaf kernel: hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Feb 14 19:11:18 linux-ytaf kernel: Switched to clocksource hpet
Feb 14 19:11:18 linux-ytaf kernel: AppArmor: AppArmor Filesystem Enabled
Feb 14 19:11:18 linux-ytaf kernel: pnp: PnP ACPI init
Feb 14 19:11:18 linux-ytaf kernel: system 00:00: [mem 0xfed40000-0xfed44fff] has been reserved
Feb 14 19:11:18 linux-ytaf kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
Feb 14 19:11:18 linux-ytaf kernel: system 00:01: [io  0x0680-0x069f] has been reserved
Feb 14 19:11:18 linux-ytaf kernel: system 00:01: [io  0x0200-0x020f] has been reserved
Feb 14 19:11:18 linux-ytaf kernel: system 00:01: [io  0xffff] has been reserved
Feb 14 19:11:18 linux-ytaf kernel: system 00:01: [io  0xffff] has been reserved
Feb 14 19:11:18 linux-ytaf kernel: system 00:01: [io  0x0400-0x0453] could not be reserved
Feb 14 19:11:18 linux-ytaf kernel: system 00:01: [io  0x0458-0x047f] has been reserved
Feb 14 19:11:18 linux-ytaf kernel: system 00:01: [io  0x0500-0x057f] has been reserved
Feb 14 19:11:18 linux-ytaf kernel: system 00:01: [io  0x164e-0x164f] has been reserved
Feb 14 19:11:18 linux-ytaf kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 19:11:18 linux-ytaf kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Feb 14 19:11:18 linux-ytaf kernel: system 00:03: [io  0x0454-0x0457] has been reserved
Feb 14 19:11:18 linux-ytaf kernel: system 00:03: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
Feb 14 19:11:18 linux-ytaf kernel: system 00:04: [io  0x0290-0x029f] has been reserved
Feb 14 19:11:18 linux-ytaf kernel: system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 19:11:18 linux-ytaf kernel: system 00:05: [io  0x04d0-0x04d1] has been reserved
Feb 14 19:11:18 linux-ytaf kernel: system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 19:11:18 linux-ytaf kernel: system 00:06: [mem 0xfed1c000-0xfed1ffff] has been reserved
Feb 14 19:11:18 linux-ytaf kernel: system 00:06: [mem 0xfed10000-0xfed17fff] has been reserved
Feb 14 19:11:18 linux-ytaf kernel: system 00:06: [mem 0xfed18000-0xfed18fff] has been reserved
Feb 14 19:11:18 linux-ytaf kernel: system 00:06: [mem 0xfed19000-0xfed19fff] has been reserved
Feb 14 19:11:18 linux-ytaf kernel: system 00:06: [mem 0xf8000000-0xfbffffff] has been reserved
Feb 14 19:11:18 linux-ytaf kernel: system 00:06: [mem 0xfed20000-0xfed3ffff] has been reserved
Feb 14 19:11:18 linux-ytaf kernel: system 00:06: [mem 0xfed90000-0xfed93fff] has been reserved
Feb 14 19:11:18 linux-ytaf kernel: system 00:06: [mem 0xfed45000-0xfed8ffff] has been reserved
Feb 14 19:11:18 linux-ytaf kernel: system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Feb 14 19:11:18 linux-ytaf kernel: system 00:06: [mem 0xfee00000-0xfeefffff] could not be reserved
Feb 14 19:11:18 linux-ytaf kernel: system 00:06: [mem 0xcfa00000-0xcfa00fff] has been reserved
Feb 14 19:11:18 linux-ytaf kernel: system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 19:11:18 linux-ytaf kernel: system 00:07: [mem 0x20000000-0x201fffff] has been reserved
Feb 14 19:11:18 linux-ytaf kernel: system 00:07: [mem 0x40000000-0x401fffff] has been reserved
Feb 14 19:11:18 linux-ytaf kernel: system 00:07: Plug and Play ACPI device, IDs PNP0c01 (active)
Feb 14 19:11:18 linux-ytaf kernel: pnp: PnP ACPI: found 8 devices
Feb 14 19:11:18 linux-ytaf kernel: clocksource acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.0: bridge window [io  0x1000-0x0fff] to [bus 03] add_size 1000
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 03] add_size 200000 add_align 100000
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff] to [bus 03] add_size 200000 add_align 100000
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.0: res[14]=[mem 0x00100000-0x000fffff] res_to_dev_res add_size 200000 min_align 100000
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.0: res[14]=[mem 0x00100000-0x002fffff] res_to_dev_res add_size 200000 min_align 100000
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x000fffff 64bit pref] res_to_dev_res add_size 200000 min_align 100000
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x002fffff 64bit pref] res_to_dev_res add_size 200000 min_align 100000
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.0: res[13]=[io  0x1000-0x0fff] res_to_dev_res add_size 1000 min_align 1000
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.0: res[13]=[io  0x1000-0x1fff] res_to_dev_res add_size 1000 min_align 1000
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.0: BAR 14: assigned [mem 0xcfb00000-0xcfcfffff]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.0: BAR 15: assigned [mem 0xcfd00000-0xcfefffff 64bit pref]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.0: BAR 13: assigned [io  0x2000-0x2fff]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:01.1: PCI bridge to [bus 02]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [io  0xe000-0xefff]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xf6000000-0xf70fffff]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xe0000000-0xe9ffffff 64bit pref]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.0: PCI bridge to [bus 03]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.0:   bridge window [io  0x2000-0x2fff]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.0:   bridge window [mem 0xcfb00000-0xcfcfffff]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.0:   bridge window [mem 0xcfd00000-0xcfefffff 64bit pref]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.4: PCI bridge to [bus 04]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.4:   bridge window [mem 0xf7a00000-0xf7afffff]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.5: PCI bridge to [bus 05]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.5:   bridge window [mem 0xf7900000-0xf79fffff]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:06:00.0: BAR 6: assigned [mem 0xf7800000-0xf780ffff pref]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.6: PCI bridge to [bus 06]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [io  0xd000-0xdfff]
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [mem 0xf7800000-0xf78fffff]
Feb 14 19:11:18 linux-ytaf kernel: pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
Feb 14 19:11:18 linux-ytaf kernel: pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
Feb 14 19:11:18 linux-ytaf kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
Feb 14 19:11:18 linux-ytaf kernel: pci_bus 0000:00: resource 7 [mem 0x000d4000-0x000d7fff window]
Feb 14 19:11:18 linux-ytaf kernel: pci_bus 0000:00: resource 8 [mem 0x000d8000-0x000dbfff window]
Feb 14 19:11:18 linux-ytaf kernel: pci_bus 0000:00: resource 9 [mem 0x000dc000-0x000dffff window]
Feb 14 19:11:18 linux-ytaf kernel: pci_bus 0000:00: resource 10 [mem 0xcfa00000-0xfeafffff window]
Feb 14 19:11:18 linux-ytaf kernel: pci_bus 0000:02: resource 0 [io  0xe000-0xefff]
Feb 14 19:11:18 linux-ytaf kernel: pci_bus 0000:02: resource 1 [mem 0xf6000000-0xf70fffff]
Feb 14 19:11:18 linux-ytaf kernel: pci_bus 0000:02: resource 2 [mem 0xe0000000-0xe9ffffff 64bit pref]
Feb 14 19:11:18 linux-ytaf kernel: pci_bus 0000:03: resource 0 [io  0x2000-0x2fff]
Feb 14 19:11:18 linux-ytaf kernel: pci_bus 0000:03: resource 1 [mem 0xcfb00000-0xcfcfffff]
Feb 14 19:11:18 linux-ytaf kernel: pci_bus 0000:03: resource 2 [mem 0xcfd00000-0xcfefffff 64bit pref]
Feb 14 19:11:18 linux-ytaf kernel: pci_bus 0000:04: resource 1 [mem 0xf7a00000-0xf7afffff]
Feb 14 19:11:18 linux-ytaf kernel: pci_bus 0000:05: resource 1 [mem 0xf7900000-0xf79fffff]
Feb 14 19:11:18 linux-ytaf kernel: pci_bus 0000:06: resource 0 [io  0xd000-0xdfff]
Feb 14 19:11:18 linux-ytaf kernel: pci_bus 0000:06: resource 1 [mem 0xf7800000-0xf78fffff]
Feb 14 19:11:18 linux-ytaf kernel: NET: Registered protocol family 2
Feb 14 19:11:18 linux-ytaf kernel: TCP established hash table entries: 65536 (order: 7, 524288 bytes)
Feb 14 19:11:18 linux-ytaf kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Feb 14 19:11:18 linux-ytaf kernel: TCP: Hash tables configured (established 65536 bind 65536)
Feb 14 19:11:18 linux-ytaf kernel: UDP hash table entries: 4096 (order: 5, 131072 bytes)
Feb 14 19:11:18 linux-ytaf kernel: UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
Feb 14 19:11:18 linux-ytaf kernel: NET: Registered protocol family 1
Feb 14 19:11:18 linux-ytaf kernel: pci 0000:02:00.0: Video device with shadowed ROM
Feb 14 19:11:18 linux-ytaf kernel: PCI: CLS 64 bytes, default 64
Feb 14 19:11:18 linux-ytaf kernel: Unpacking initramfs...
Feb 14 19:11:18 linux-ytaf kernel: Freeing initrd memory: 11920K (ffff880000457000 - ffff880000ffb000)
Feb 14 19:11:18 linux-ytaf kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Feb 14 19:11:18 linux-ytaf kernel: software IO TLB [mem 0xc638f000-0xca38f000] (64MB) mapped at [ffff8800c638f000-ffff8800ca38efff]
Feb 14 19:11:18 linux-ytaf kernel: RAPL PMU detected, API unit is 2^-32 Joules, 3 fixed counters 163840 ms ovfl timer
Feb 14 19:11:18 linux-ytaf kernel: hw unit of domain pp0-core 2^-16 Joules
Feb 14 19:11:18 linux-ytaf kernel: hw unit of domain package 2^-16 Joules
Feb 14 19:11:18 linux-ytaf kernel: hw unit of domain pp1-gpu 2^-16 Joules
Feb 14 19:11:18 linux-ytaf kernel: microcode: CPU0 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 19:11:18 linux-ytaf kernel: microcode: CPU1 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 19:11:18 linux-ytaf kernel: microcode: CPU2 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 19:11:18 linux-ytaf kernel: microcode: CPU3 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 19:11:18 linux-ytaf kernel: microcode: CPU4 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 19:11:18 linux-ytaf kernel: microcode: CPU5 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 19:11:18 linux-ytaf kernel: microcode: CPU6 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 19:11:18 linux-ytaf kernel: microcode: CPU7 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 19:11:18 linux-ytaf kernel: microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Feb 14 19:11:18 linux-ytaf kernel: Scanning for low memory corruption every 60 seconds
Feb 14 19:11:18 linux-ytaf kernel: futex hash table entries: 2048 (order: 5, 131072 bytes)
Feb 14 19:11:18 linux-ytaf kernel: audit: initializing netlink subsys (disabled)
Feb 14 19:11:18 linux-ytaf kernel: audit: type=2000 audit(1455477075.280:1): initialized
Feb 14 19:11:18 linux-ytaf kernel: HugeTLB registered 2 MB page size, pre-allocated 0 pages
Feb 14 19:11:18 linux-ytaf kernel: zpool: loaded
Feb 14 19:11:18 linux-ytaf kernel: zbud: loaded
Feb 14 19:11:18 linux-ytaf kernel: VFS: Disk quotas dquot_6.6.0
Feb 14 19:11:18 linux-ytaf kernel: VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Feb 14 19:11:18 linux-ytaf kernel: Key type big_key registered
Feb 14 19:11:18 linux-ytaf kernel: Key type asymmetric registered
Feb 14 19:11:18 linux-ytaf kernel: Asymmetric key parser 'x509' registered
Feb 14 19:11:18 linux-ytaf kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Feb 14 19:11:18 linux-ytaf kernel: io scheduler noop registered
Feb 14 19:11:18 linux-ytaf kernel: io scheduler deadline registered
Feb 14 19:11:18 linux-ytaf kernel: io scheduler cfq registered (default)
Feb 14 19:11:18 linux-ytaf kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Feb 14 19:11:18 linux-ytaf kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Feb 14 19:11:18 linux-ytaf kernel: efifb: probing for efifb
Feb 14 19:11:18 linux-ytaf kernel: efifb: framebuffer at 0xe9000000, mapped to 0xffffc90001000000, using 1876k, total 1875k
Feb 14 19:11:18 linux-ytaf kernel: efifb: mode is 800x600x32, linelength=3200, pages=1
Feb 14 19:11:18 linux-ytaf kernel: efifb: scrolling: redraw
Feb 14 19:11:18 linux-ytaf kernel: efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Feb 14 19:11:18 linux-ytaf kernel: Console: switching to colour frame buffer device 100x37
Feb 14 19:11:18 linux-ytaf kernel: fb0: EFI VGA frame buffer device
Feb 14 19:11:18 linux-ytaf kernel: intel_idle: MWAIT substates: 0x1120
Feb 14 19:11:18 linux-ytaf kernel: intel_idle: v0.4 model 0x2A
Feb 14 19:11:18 linux-ytaf kernel: intel_idle: lapic_timer_reliable_states 0xffffffff
Feb 14 19:11:18 linux-ytaf kernel: GHES: HEST is not enabled!
Feb 14 19:11:18 linux-ytaf kernel: Serial: 8250/16550 driver, 32 ports, IRQ sharing disabled
Feb 14 19:11:18 linux-ytaf kernel: Non-volatile memory driver v1.3
Feb 14 19:11:18 linux-ytaf kernel: Linux agpgart interface v0.103
Feb 14 19:11:18 linux-ytaf kernel: ahci 0000:00:1f.2: version 3.0
Feb 14 19:11:18 linux-ytaf kernel: ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x7 impl SATA mode
Feb 14 19:11:18 linux-ytaf kernel: ahci 0000:00:1f.2: flags: 64bit ncq led clo pio slum part ems apst 
Feb 14 19:11:18 linux-ytaf kernel: scsi host0: ahci
Feb 14 19:11:18 linux-ytaf kernel: scsi host1: ahci
Feb 14 19:11:18 linux-ytaf kernel: scsi host2: ahci
Feb 14 19:11:18 linux-ytaf kernel: scsi host3: ahci
Feb 14 19:11:18 linux-ytaf kernel: scsi host4: ahci
Feb 14 19:11:18 linux-ytaf kernel: scsi host5: ahci
Feb 14 19:11:18 linux-ytaf kernel: ata1: SATA max UDMA/133 abar m2048@0xf7b26000 port 0xf7b26100 irq 26
Feb 14 19:11:18 linux-ytaf kernel: ata2: SATA max UDMA/133 abar m2048@0xf7b26000 port 0xf7b26180 irq 26
Feb 14 19:11:18 linux-ytaf kernel: ata3: SATA max UDMA/133 abar m2048@0xf7b26000 port 0xf7b26200 irq 26
Feb 14 19:11:18 linux-ytaf kernel: ata4: DUMMY
Feb 14 19:11:18 linux-ytaf kernel: ata5: DUMMY
Feb 14 19:11:18 linux-ytaf kernel: ata6: DUMMY
Feb 14 19:11:18 linux-ytaf kernel: ahci 0000:06:00.0: AHCI 0001.0100 32 slots 2 ports 3 Gbps 0x3 impl SATA mode
Feb 14 19:11:18 linux-ytaf kernel: ahci 0000:06:00.0: flags: 64bit ncq pm led clo pmp pio slum part 
Feb 14 19:11:18 linux-ytaf kernel: scsi host6: ahci
Feb 14 19:11:18 linux-ytaf kernel: scsi host7: ahci
Feb 14 19:11:18 linux-ytaf kernel: ata7: SATA max UDMA/133 abar m512@0xf7810000 port 0xf7810100 irq 18
Feb 14 19:11:18 linux-ytaf kernel: ata8: SATA max UDMA/133 abar m512@0xf7810000 port 0xf7810180 irq 18
Feb 14 19:11:18 linux-ytaf kernel: i8042: PNP: No PS/2 controller found. Probing ports directly.
Feb 14 19:11:18 linux-ytaf kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Feb 14 19:11:18 linux-ytaf kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Feb 14 19:11:18 linux-ytaf kernel: mousedev: PS/2 mouse device common for all mice
Feb 14 19:11:18 linux-ytaf kernel: rtc_cmos 00:02: RTC can wake from S4
Feb 14 19:11:18 linux-ytaf kernel: rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Feb 14 19:11:18 linux-ytaf kernel: rtc_cmos 00:02: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
Feb 14 19:11:18 linux-ytaf kernel: Intel P-state driver initializing.
Feb 14 19:11:18 linux-ytaf kernel: ledtrig-cpu: registered to indicate activity on CPUs
Feb 14 19:11:18 linux-ytaf kernel: EFI Variables Facility v0.08 2004-May-17
Feb 14 19:11:18 linux-ytaf kernel: hidraw: raw HID events driver (C) Jiri Kosina
Feb 14 19:11:18 linux-ytaf kernel: NET: Registered protocol family 10
Feb 14 19:11:18 linux-ytaf kernel: registered taskstats version 1
Feb 14 19:11:18 linux-ytaf kernel: Key type encrypted registered
Feb 14 19:11:18 linux-ytaf kernel: AppArmor: AppArmor sha1 policy hashing enabled
Feb 14 19:11:18 linux-ytaf kernel:   Magic number: 4:658:192
Feb 14 19:11:18 linux-ytaf kernel: acpi device:1e: hash matches
Feb 14 19:11:18 linux-ytaf kernel: rtc_cmos 00:02: setting system clock to 2016-02-14 19:11:16 UTC (1455477076)
Feb 14 19:11:18 linux-ytaf kernel: PM: Checking hibernation image partition /dev/sdb2
Feb 14 19:11:18 linux-ytaf kernel: ata8: SATA link down (SStatus 0 SControl 300)
Feb 14 19:11:18 linux-ytaf kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Feb 14 19:11:18 linux-ytaf kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 14 19:11:18 linux-ytaf kernel: ata7: SATA link down (SStatus 0 SControl 300)
Feb 14 19:11:18 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 19:11:18 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff8802268b7dd8), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 19:11:18 linux-ytaf kernel: ata2.00: ATA-8: TOSHIBA HDWD110, MS2OA8J0, max UDMA/133
Feb 14 19:11:18 linux-ytaf kernel: ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Feb 14 19:11:18 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 19:11:18 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff8802268b7d60), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 19:11:18 linux-ytaf kernel: ata3.00: ATAPI: TSSTcorp CDDVDW SH-S223C, SB05, max UDMA/66
Feb 14 19:11:18 linux-ytaf kernel: ata3.00: applying bridge limits
Feb 14 19:11:18 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 19:11:18 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff8802268b7dd8), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 19:11:18 linux-ytaf kernel: ata2.00: configured for UDMA/133
Feb 14 19:11:18 linux-ytaf kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 14 19:11:18 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 19:11:18 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff8802268b7e50), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 19:11:18 linux-ytaf kernel: ata1.00: ATA-9: SAMSUNG SSD 830 Series, CXM03B1Q, max UDMA/133
Feb 14 19:11:18 linux-ytaf kernel: ata1.00: 500118192 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Feb 14 19:11:18 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 19:11:18 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff8802268b7e50), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 19:11:18 linux-ytaf kernel: ata1.00: configured for UDMA/133
Feb 14 19:11:18 linux-ytaf kernel: scsi 0:0:0:0: Direct-Access     ATA      SAMSUNG SSD 830  3B1Q PQ: 0 ANSI: 5
Feb 14 19:11:18 linux-ytaf kernel: sd 0:0:0:0: [sda] 500118192 512-byte logical blocks: (256 GB/238 GiB)
Feb 14 19:11:18 linux-ytaf kernel: scsi 1:0:0:0: Direct-Access     ATA      TOSHIBA HDWD110  A8J0 PQ: 0 ANSI: 5
Feb 14 19:11:18 linux-ytaf kernel: sd 0:0:0:0: [sda] Write Protect is off
Feb 14 19:11:18 linux-ytaf kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 14 19:11:18 linux-ytaf kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 14 19:11:18 linux-ytaf kernel: sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
Feb 14 19:11:18 linux-ytaf kernel: sd 1:0:0:0: [sdb] 4096-byte physical blocks
Feb 14 19:11:18 linux-ytaf kernel: sd 1:0:0:0: [sdb] Write Protect is off
Feb 14 19:11:18 linux-ytaf kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Feb 14 19:11:18 linux-ytaf kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 14 19:11:18 linux-ytaf kernel:  sda: sda1 sda2 sda3 sda4
Feb 14 19:11:18 linux-ytaf kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Feb 14 19:11:18 linux-ytaf kernel:  sdb: sdb1 sdb2 sdb3 sdb4
Feb 14 19:11:18 linux-ytaf kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
Feb 14 19:11:18 linux-ytaf kernel: tsc: Refined TSC clocksource calibration: 3411.128 MHz
Feb 14 19:11:18 linux-ytaf kernel: clocksource tsc: mask: 0xffffffffffffffff max_cycles: 0x312b5ecadef, max_idle_ns: 440795307361 ns
Feb 14 19:11:18 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 19:11:18 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff8802268b7d60), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 19:11:18 linux-ytaf kernel: ata3.00: configured for UDMA/66
Feb 14 19:11:18 linux-ytaf kernel: scsi 2:0:0:0: CD-ROM            TSSTcorp CDDVDW SH-S223C  SB05 PQ: 0 ANSI: 5
Feb 14 19:11:18 linux-ytaf kernel: PM: Hibernation image partition 8:18 present
Feb 14 19:11:18 linux-ytaf kernel: PM: Looking for hibernation image.
Feb 14 19:11:18 linux-ytaf kernel: Switched to clocksource tsc
Feb 14 19:11:18 linux-ytaf kernel: PM: Image not found (code -22)
Feb 14 19:11:18 linux-ytaf kernel: PM: Hibernation image not present or could not be loaded.
Feb 14 19:11:18 linux-ytaf kernel: Freeing unused kernel memory: 1560K (ffffffff81f11000 - ffffffff82097000)
Feb 14 19:11:18 linux-ytaf kernel: Write protecting the kernel read-only data: 14336k
Feb 14 19:11:18 linux-ytaf kernel: Freeing unused kernel memory: 1632K (ffff88000d668000 - ffff88000d800000)
Feb 14 19:11:18 linux-ytaf kernel: Freeing unused kernel memory: 1296K (ffff88000dcbc000 - ffff88000de00000)
Feb 14 19:11:18 linux-ytaf systemd[1]: RTC configured in localtime, applying delta of 60 minutes to system time.
Feb 14 19:11:18 linux-ytaf kernel: random: systemd urandom read with 22 bits of entropy available
Feb 14 19:11:18 linux-ytaf kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Feb 14 19:11:18 linux-ytaf kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0
Feb 14 19:11:18 linux-ytaf kernel: scsi 2:0:0:0: Attached scsi generic sg2 type 5
Feb 14 19:11:18 linux-ytaf systemd-journal[187]: Journal started
Feb 14 19:11:18 linux-ytaf dracut-cmdline[181]: dracut-42.1 dracut-037-68.1
Feb 14 19:11:18 linux-ytaf systemd-udevd[250]: Network interface NamePolicy= disabled on kernel commandline, ignoring.
Feb 14 19:11:18 linux-ytaf kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3
Feb 14 19:11:18 linux-ytaf kernel: ACPI: Power Button [PWRB]
Feb 14 19:11:18 linux-ytaf kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
Feb 14 19:11:18 linux-ytaf kernel: ACPI: Power Button [PWRF]
Feb 14 19:11:18 linux-ytaf kernel: wmi: Mapper loaded
Feb 14 19:11:18 linux-ytaf kernel: ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
Feb 14 19:11:18 linux-ytaf kernel: acpi device:58: registered as cooling_device0
Feb 14 19:11:18 linux-ytaf kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5
Feb 14 19:11:18 linux-ytaf kernel: [drm] Initialized drm 1.1.0 20060810
Feb 14 19:11:18 linux-ytaf kernel: ACPI: bus type USB registered
Feb 14 19:11:18 linux-ytaf kernel: usbcore: registered new interface driver usbfs
Feb 14 19:11:18 linux-ytaf kernel: usbcore: registered new interface driver hub
Feb 14 19:11:18 linux-ytaf kernel: usbcore: registered new device driver usb
Feb 14 19:11:18 linux-ytaf kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Feb 14 19:11:18 linux-ytaf kernel: ehci-pci: EHCI PCI platform driver
Feb 14 19:11:18 linux-ytaf kernel: ehci-pci 0000:00:1a.0: EHCI Host Controller
Feb 14 19:11:18 linux-ytaf kernel: ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Feb 14 19:11:18 linux-ytaf kernel: ehci-pci 0000:00:1a.0: debug port 2
Feb 14 19:11:18 linux-ytaf kernel: ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Feb 14 19:11:18 linux-ytaf kernel: ehci-pci 0000:00:1a.0: irq 16, io mem 0xf7b28000
Feb 14 19:11:18 linux-ytaf kernel: MXM: GUID detected in BIOS
Feb 14 19:11:18 linux-ytaf kernel: checking generic (e9000000 1d5000) vs hw (e0000000 8000000)
Feb 14 19:11:18 linux-ytaf kernel: checking generic (e9000000 1d5000) vs hw (e8000000 2000000)
Feb 14 19:11:18 linux-ytaf kernel: fb: switching to nouveaufb from EFI VGA
Feb 14 19:11:18 linux-ytaf kernel: Console: switching to colour dummy device 80x25
Feb 14 19:11:18 linux-ytaf kernel: nouveau  [  DEVICE][0000:02:00.0] BOOT0  : 0x0e4030a2
Feb 14 19:11:18 linux-ytaf kernel: nouveau  [  DEVICE][0000:02:00.0] Chipset: GK104 (NVE4)
Feb 14 19:11:18 linux-ytaf kernel: nouveau  [  DEVICE][0000:02:00.0] Family : NVE0
Feb 14 19:11:18 linux-ytaf kernel: ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Feb 14 19:11:18 linux-ytaf kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 19:11:18 linux-ytaf kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 19:11:18 linux-ytaf kernel: usb usb1: Product: EHCI Host Controller
Feb 14 19:11:18 linux-ytaf kernel: usb usb1: Manufacturer: Linux 4.1.15-8-default ehci_hcd
Feb 14 19:11:18 linux-ytaf kernel: usb usb1: SerialNumber: 0000:00:1a.0
Feb 14 19:11:18 linux-ytaf kernel: hub 1-0:1.0: USB hub found
Feb 14 19:11:18 linux-ytaf kernel: hub 1-0:1.0: 2 ports detected
Feb 14 19:11:18 linux-ytaf kernel: xhci_hcd 0000:04:00.0: xHCI Host Controller
Feb 14 19:11:18 linux-ytaf kernel: xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 2
Feb 14 19:11:18 linux-ytaf kernel: sr 2:0:0:0: [sr0] scsi3-mmc drive: 52x/52x writer dvd-ram cd/rw xa/form2 cdda tray
Feb 14 19:11:18 linux-ytaf kernel: cdrom: Uniform CD-ROM driver Revision: 3.20
Feb 14 19:11:18 linux-ytaf kernel: sr 2:0:0:0: Attached scsi CD-ROM sr0
Feb 14 19:11:18 linux-ytaf kernel: xhci_hcd 0000:04:00.0: hcc params 0x0200f180 hci version 0x96 quirks 0x00080000
Feb 14 19:11:18 linux-ytaf kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 19:11:18 linux-ytaf kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 19:11:18 linux-ytaf kernel: usb usb2: Product: xHCI Host Controller
Feb 14 19:11:18 linux-ytaf kernel: usb usb2: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 19:11:18 linux-ytaf kernel: usb usb2: SerialNumber: 0000:04:00.0
Feb 14 19:11:18 linux-ytaf kernel: hub 2-0:1.0: USB hub found
Feb 14 19:11:18 linux-ytaf kernel: hub 2-0:1.0: 2 ports detected
Feb 14 19:11:18 linux-ytaf kernel: xhci_hcd 0000:04:00.0: xHCI Host Controller
Feb 14 19:11:18 linux-ytaf kernel: xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 3
Feb 14 19:11:18 linux-ytaf kernel: ehci-pci 0000:00:1d.0: EHCI Host Controller
Feb 14 19:11:18 linux-ytaf kernel: ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 4
Feb 14 19:11:18 linux-ytaf kernel: usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
Feb 14 19:11:18 linux-ytaf kernel: ehci-pci 0000:00:1d.0: debug port 2
Feb 14 19:11:18 linux-ytaf kernel: usb usb3: New USB device found, idVendor=1d6b, idProduct=0003
Feb 14 19:11:18 linux-ytaf kernel: usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 19:11:18 linux-ytaf kernel: usb usb3: Product: xHCI Host Controller
Feb 14 19:11:18 linux-ytaf kernel: usb usb3: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 19:11:18 linux-ytaf kernel: usb usb3: SerialNumber: 0000:04:00.0
Feb 14 19:11:18 linux-ytaf kernel: hub 3-0:1.0: USB hub found
Feb 14 19:11:18 linux-ytaf kernel: hub 3-0:1.0: 2 ports detected
Feb 14 19:11:18 linux-ytaf kernel: ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Feb 14 19:11:18 linux-ytaf kernel: ehci-pci 0000:00:1d.0: irq 23, io mem 0xf7b27000
Feb 14 19:11:18 linux-ytaf kernel: ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Feb 14 19:11:18 linux-ytaf kernel: usb usb4: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 19:11:18 linux-ytaf kernel: usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 19:11:18 linux-ytaf kernel: usb usb4: Product: EHCI Host Controller
Feb 14 19:11:18 linux-ytaf kernel: usb usb4: Manufacturer: Linux 4.1.15-8-default ehci_hcd
Feb 14 19:11:18 linux-ytaf kernel: usb usb4: SerialNumber: 0000:00:1d.0
Feb 14 19:11:18 linux-ytaf kernel: hub 4-0:1.0: USB hub found
Feb 14 19:11:18 linux-ytaf kernel: hub 4-0:1.0: 2 ports detected
Feb 14 19:11:18 linux-ytaf kernel: xhci_hcd 0000:05:00.0: xHCI Host Controller
Feb 14 19:11:18 linux-ytaf kernel: xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 5
Feb 14 19:11:18 linux-ytaf kernel: i915 0000:00:02.0: enabling device (0006 -> 0007)
Feb 14 19:11:18 linux-ytaf kernel: xhci_hcd 0000:05:00.0: hcc params 0x0200f180 hci version 0x96 quirks 0x00080000
Feb 14 19:11:18 linux-ytaf kernel: usb usb5: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 19:11:18 linux-ytaf kernel: usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 19:11:18 linux-ytaf kernel: usb usb5: Product: xHCI Host Controller
Feb 14 19:11:18 linux-ytaf kernel: usb usb5: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 19:11:18 linux-ytaf kernel: usb usb5: SerialNumber: 0000:05:00.0
Feb 14 19:11:18 linux-ytaf kernel: hub 5-0:1.0: USB hub found
Feb 14 19:11:18 linux-ytaf kernel: hub 5-0:1.0: 2 ports detected
Feb 14 19:11:18 linux-ytaf kernel: xhci_hcd 0000:05:00.0: xHCI Host Controller
Feb 14 19:11:18 linux-ytaf kernel: xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 6
Feb 14 19:11:18 linux-ytaf kernel: usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
Feb 14 19:11:18 linux-ytaf kernel: usb usb6: New USB device found, idVendor=1d6b, idProduct=0003
Feb 14 19:11:18 linux-ytaf kernel: usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 19:11:18 linux-ytaf kernel: usb usb6: Product: xHCI Host Controller
Feb 14 19:11:18 linux-ytaf kernel: usb usb6: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 19:11:18 linux-ytaf kernel: usb usb6: SerialNumber: 0000:05:00.0
Feb 14 19:11:18 linux-ytaf kernel: hub 6-0:1.0: USB hub found
Feb 14 19:11:18 linux-ytaf kernel: hub 6-0:1.0: 2 ports detected
Feb 14 19:11:18 linux-ytaf kernel: nouveau  [   VBIOS][0000:02:00.0] using image from PROM
Feb 14 19:11:18 linux-ytaf kernel: nouveau  [   VBIOS][0000:02:00.0] BIT signature found
Feb 14 19:11:18 linux-ytaf kernel: nouveau  [   VBIOS][0000:02:00.0] version 80.04.4b.00.07
Feb 14 19:11:18 linux-ytaf kernel: nouveau  [     PMC][0000:02:00.0] MSI interrupts enabled
Feb 14 19:11:18 linux-ytaf kernel: nouveau  [     PFB][0000:02:00.0] RAM type: GDDR5
Feb 14 19:11:18 linux-ytaf kernel: nouveau  [     PFB][0000:02:00.0] RAM size: 2048 MiB
Feb 14 19:11:18 linux-ytaf kernel: nouveau  [     PFB][0000:02:00.0]    ZCOMP: 0 tags
Feb 14 19:11:18 linux-ytaf kernel: nouveau  [    VOLT][0000:02:00.0] GPU voltage: 987500uv
Feb 14 19:11:18 linux-ytaf kernel: nouveau  [  PTHERM][0000:02:00.0] FAN control: PWM
Feb 14 19:11:18 linux-ytaf kernel: nouveau  [  PTHERM][0000:02:00.0] fan management: automatic
Feb 14 19:11:18 linux-ytaf kernel: nouveau  [  PTHERM][0000:02:00.0] internal sensor: yes
Feb 14 19:11:18 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 07: core 324 MHz memory 648 MHz 
Feb 14 19:11:18 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 0a: core 324-862 MHz memory 1620 MHz 
Feb 14 19:11:18 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 0d: core 540-1202 MHz memory 6008 MHz 
Feb 14 19:11:18 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 0f: core 540-1202 MHz memory 6008 MHz 
Feb 14 19:11:18 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] --: core 324 MHz memory 648 MHz 
Feb 14 19:11:18 linux-ytaf kernel: raid6: sse2x1   gen() 11024 MB/s
Feb 14 19:11:18 linux-ytaf kernel: [TTM] Zone  kernel: Available graphics memory: 4034698 kiB
Feb 14 19:11:18 linux-ytaf kernel: [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
Feb 14 19:11:18 linux-ytaf kernel: [TTM] Initializing pool allocator
Feb 14 19:11:18 linux-ytaf kernel: [TTM] Initializing DMA pool allocator
Feb 14 19:11:18 linux-ytaf kernel: nouveau  [     DRM] VRAM: 2048 MiB
Feb 14 19:11:18 linux-ytaf kernel: nouveau  [     DRM] GART: 1048576 MiB
Feb 14 19:11:18 linux-ytaf kernel: nouveau  [     DRM] TMDS table version 2.0
Feb 14 19:11:18 linux-ytaf kernel: nouveau  [     DRM] DCB version 4.0
Feb 14 19:11:18 linux-ytaf kernel: nouveau  [     DRM] DCB outp 00: 01000f02 00020030
Feb 14 19:11:18 linux-ytaf kernel: nouveau  [     DRM] DCB outp 01: 02000f00 00000000
Feb 14 19:11:18 linux-ytaf kernel: nouveau  [     DRM] DCB outp 02: 08011f82 00020030
Feb 14 19:11:18 linux-ytaf kernel: nouveau  [     DRM] DCB outp 03: 02822f62 0f420010
Feb 14 19:11:18 linux-ytaf kernel: nouveau  [     DRM] DCB outp 05: 04833fb6 0f420010
Feb 14 19:11:18 linux-ytaf kernel: nouveau  [     DRM] DCB outp 06: 04033f72 00020010
Feb 14 19:11:18 linux-ytaf kernel: nouveau  [     DRM] DCB conn 00: 00001030
Feb 14 19:11:18 linux-ytaf kernel: nouveau  [     DRM] DCB conn 01: 00020131
Feb 14 19:11:18 linux-ytaf kernel: nouveau  [     DRM] DCB conn 02: 00002261
Feb 14 19:11:18 linux-ytaf kernel: nouveau  [     DRM] DCB conn 03: 00010346
Feb 14 19:11:18 linux-ytaf kernel: nouveau  [     DRM] DCB conn 04: 00000460
Feb 14 19:11:18 linux-ytaf kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Feb 14 19:11:18 linux-ytaf kernel: [drm] Driver supports precise vblank timestamp query.
Feb 14 19:11:18 linux-ytaf kernel: nouveau  [     DRM] MM: using COPY for buffer copies
Feb 14 19:11:18 linux-ytaf kernel: usb 1-1: new high-speed USB device number 2 using ehci-pci
Feb 14 19:11:18 linux-ytaf kernel: raid6: sse2x1   xor()  7579 MB/s
Feb 14 19:11:19 linux-ytaf kernel: usb 4-1: new high-speed USB device number 2 using ehci-pci
Feb 14 19:11:19 linux-ytaf kernel: raid6: sse2x2   gen() 13876 MB/s
Feb 14 19:11:19 linux-ytaf kernel: raid6: sse2x2   xor() 10039 MB/s
Feb 14 19:11:19 linux-ytaf kernel: usb 5-2: new high-speed USB device number 2 using xhci_hcd
Feb 14 19:11:19 linux-ytaf kernel: usb 1-1: New USB device found, idVendor=8087, idProduct=0024
Feb 14 19:11:19 linux-ytaf kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb 14 19:11:19 linux-ytaf kernel: hub 1-1:1.0: USB hub found
Feb 14 19:11:19 linux-ytaf kernel: hub 1-1:1.0: 6 ports detected
Feb 14 19:11:19 linux-ytaf kernel: usb 4-1: New USB device found, idVendor=8087, idProduct=0024
Feb 14 19:11:19 linux-ytaf kernel: usb 4-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb 14 19:11:19 linux-ytaf kernel: hub 4-1:1.0: USB hub found
Feb 14 19:11:19 linux-ytaf kernel: hub 4-1:1.0: 8 ports detected
Feb 14 19:11:19 linux-ytaf kernel: raid6: sse2x4   gen() 16267 MB/s
Feb 14 19:11:19 linux-ytaf kernel: raid6: sse2x4   xor() 12125 MB/s
Feb 14 19:11:19 linux-ytaf kernel: raid6: using algorithm sse2x4 gen() 16267 MB/s
Feb 14 19:11:19 linux-ytaf kernel: raid6: .... xor() 12125 MB/s, rmw enabled
Feb 14 19:11:19 linux-ytaf kernel: raid6: using ssse3x2 recovery algorithm
Feb 14 19:11:19 linux-ytaf kernel: xor: automatically using best checksumming function:
Feb 14 19:11:19 linux-ytaf kernel:    avx       : 31206.000 MB/sec
Feb 14 19:11:19 linux-ytaf kernel: Btrfs loaded, assert=on
Feb 14 19:11:19 linux-ytaf kernel: BTRFS: device fsid 21024970-7a27-4114-8525-d8dd026f23b6 devid 1 transid 621 /dev/sdb3
Feb 14 19:11:19 linux-ytaf kernel: usb 5-2: New USB device found, idVendor=0930, idProduct=6545
Feb 14 19:11:19 linux-ytaf kernel: usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 14 19:11:19 linux-ytaf kernel: usb 5-2: Product: TransMemory
Feb 14 19:11:19 linux-ytaf kernel: usb 5-2: Manufacturer: TOSHIBA
Feb 14 19:11:19 linux-ytaf kernel: usb 5-2: SerialNumber: C89CDCBF6D59EF4140000065
Feb 14 19:11:19 linux-ytaf kernel: usb-storage 5-2:1.0: USB Mass Storage device detected
Feb 14 19:11:19 linux-ytaf kernel: scsi host8: usb-storage 5-2:1.0
Feb 14 19:11:19 linux-ytaf kernel: usbcore: registered new interface driver usb-storage
Feb 14 19:11:19 linux-ytaf kernel: nouveau  [     DRM] allocated 1920x1080 fb: 0x60000, bo ffff88000ae37000
Feb 14 19:11:19 linux-ytaf kernel: fbcon: nouveaufb (fb0) is primary device
Feb 14 19:11:19 linux-ytaf kernel: usbcore: registered new interface driver uas
Feb 14 19:11:19 linux-ytaf kernel: usb 1-1.4: new full-speed USB device number 3 using ehci-pci
Feb 14 19:11:19 linux-ytaf kernel: usb 4-1.1: new full-speed USB device number 3 using ehci-pci
Feb 14 19:11:19 linux-ytaf kernel: usb 4-1.1: New USB device found, idVendor=1532, idProduct=0109
Feb 14 19:11:19 linux-ytaf kernel: usb 4-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 14 19:11:19 linux-ytaf kernel: usb 4-1.1: Product: Razer Lycosa
Feb 14 19:11:19 linux-ytaf kernel: usb 4-1.1: Manufacturer: Razer
Feb 14 19:11:19 linux-ytaf kernel: usbcore: registered new interface driver usbhid
Feb 14 19:11:19 linux-ytaf kernel: usbhid: USB HID core driver
Feb 14 19:11:19 linux-ytaf kernel: input: Razer Razer Lycosa as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1:1.0/0003:1532:0109.0001/input/input6
Feb 14 19:11:19 linux-ytaf kernel: hid-generic 0003:1532:0109.0001: input,hidraw0: USB HID v1.10 Keyboard [Razer Razer Lycosa] on usb-0000:00:1d.0-1.1/input0
Feb 14 19:11:19 linux-ytaf kernel: input: Razer Razer Lycosa as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1:1.1/0003:1532:0109.0002/input/input7
Feb 14 19:11:19 linux-ytaf kernel: usb 1-1.4: New USB device found, idVendor=06a3, idProduct=0ccb
Feb 14 19:11:19 linux-ytaf kernel: usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 14 19:11:19 linux-ytaf kernel: usb 1-1.4: Product: Cyborg R.A.T.7 Mouse
Feb 14 19:11:19 linux-ytaf kernel: usb 1-1.4: Manufacturer: Saitek
Feb 14 19:11:19 linux-ytaf kernel: hid-generic 0003:1532:0109.0002: input,hidraw1: USB HID v1.10 Device [Razer Razer Lycosa] on usb-0000:00:1d.0-1.1/input1
Feb 14 19:11:19 linux-ytaf kernel: Console: switching to colour frame buffer device 210x65
Feb 14 19:11:19 linux-ytaf kernel: nouveau 0000:02:00.0: fb0: nouveaufb frame buffer device
Feb 14 19:11:19 linux-ytaf kernel: nouveau 0000:02:00.0: registered panic notifier
Feb 14 19:11:19 linux-ytaf kernel: [drm] Initialized nouveau 1.2.2 20120801 for 0000:02:00.0 on minor 0
Feb 14 19:11:19 linux-ytaf kernel: [drm] Memory usable by graphics device = 2048M
Feb 14 19:11:19 linux-ytaf kernel: [drm] Replacing VGA console driver
Feb 14 19:11:19 linux-ytaf kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Feb 14 19:11:19 linux-ytaf kernel: [drm] Driver supports precise vblank timestamp query.
Feb 14 19:11:19 linux-ytaf kernel: vgaarb: device changed decodes: PCI:0000:02:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
Feb 14 19:11:19 linux-ytaf kernel: [drm] Initialized i915 1.6.0 20150327 for 0000:00:02.0 on minor 1
Feb 14 19:11:19 linux-ytaf kernel: [drm] GMBUS [i915 gmbus vga] timed out, falling back to bit banging on pin 2
Feb 14 19:11:19 linux-ytaf kernel: i915 0000:00:02.0: No connectors reported connected with modes
Feb 14 19:11:19 linux-ytaf kernel: [drm] Cannot find any crtc or sizes - going 1024x768
Feb 14 19:11:19 linux-ytaf kernel: i915 0000:00:02.0: fb1: inteldrmfb frame buffer device
Feb 14 19:11:19 linux-ytaf kernel: PM: Starting manual resume from disk
Feb 14 19:11:19 linux-ytaf kernel: PM: Hibernation image partition 8:18 present
Feb 14 19:11:19 linux-ytaf kernel: PM: Looking for hibernation image.
Feb 14 19:11:19 linux-ytaf kernel: PM: Image not found (code -22)
Feb 14 19:11:19 linux-ytaf kernel: PM: Hibernation image not present or could not be loaded.
Feb 14 19:11:19 linux-ytaf kernel: BTRFS info (device sdb3): disk space caching is enabled
Feb 14 19:11:19 linux-ytaf kernel: BTRFS: has skinny extents
Feb 14 19:11:20 linux-ytaf kernel: scsi 8:0:0:0: Direct-Access     TOSHIBA  TransMemory      PMAP PQ: 0 ANSI: 6
Feb 14 19:11:20 linux-ytaf kernel: sd 8:0:0:0: Attached scsi generic sg3 type 0
Feb 14 19:11:20 linux-ytaf kernel: sd 8:0:0:0: [sdc] 30228480 512-byte logical blocks: (15.4 GB/14.4 GiB)
Feb 14 19:11:20 linux-ytaf kernel: sd 8:0:0:0: [sdc] Write Protect is off
Feb 14 19:11:20 linux-ytaf kernel: sd 8:0:0:0: [sdc] Mode Sense: 45 00 00 00
Feb 14 19:11:20 linux-ytaf kernel: sd 8:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Feb 14 19:11:20 linux-ytaf kernel:  sdc: sdc1
Feb 14 19:11:20 linux-ytaf kernel: sd 8:0:0:0: [sdc] Attached SCSI removable disk
Feb 14 19:11:20 linux-ytaf systemd-journal[187]: Journal stopped
Feb 14 19:11:22 linux-ytaf systemd-journal[474]: Runtime journal is using 8.0M (max allowed 394.0M, trying to leave 591.0M free of 3.8G available → current limit 394.0M).
Feb 14 19:11:22 linux-ytaf systemd-journal[474]: Runtime journal is using 8.0M (max allowed 394.0M, trying to leave 591.0M free of 3.8G available → current limit 394.0M).
Feb 14 19:11:22 linux-ytaf kernel: random: nonblocking pool is initialized
Feb 14 19:11:22 linux-ytaf systemd[1]: RTC configured in localtime, applying delta of 60 minutes to system time.
Feb 14 19:11:22 linux-ytaf kernel: BTRFS info (device sdb3): disk space caching is enabled
Feb 14 19:11:22 linux-ytaf systemd-journal[474]: Journal started
Feb 14 19:11:22 linux-ytaf systemd-udevd[492]: starting version 210
Feb 14 19:11:22 linux-ytaf systemd-udevd[492]: Network interface NamePolicy= disabled on kernel commandline, ignoring.
Feb 14 19:11:22 linux-ytaf systemd-udevd[492]: invalid key/value pair in file /usr/lib/udev/rules.d/51-android.rules on line 115,starting at character 57 ('')
Feb 14 19:11:22 linux-ytaf kernel: thermal LNXTHERM:00: registered as thermal_zone0
Feb 14 19:11:22 linux-ytaf kernel: ACPI: Thermal Zone [TZ00] (28 C)
Feb 14 19:11:22 linux-ytaf kernel: thermal LNXTHERM:01: registered as thermal_zone1
Feb 14 19:11:22 linux-ytaf kernel: ACPI: Thermal Zone [TZ01] (30 C)
Feb 14 19:11:23 linux-ytaf kernel: input: PC Speaker as /devices/platform/pcspkr/input/input8
Feb 14 19:11:23 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000580-0x000000000000059F conflicts with OpRegion 0x0000000000000580-0x000000000000058F (\_SB_.PCI0.SBUS.SMBI) (20150410/utaddress-254)
Feb 14 19:11:23 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000580-0x000000000000059F conflicts with OpRegion 0x0000000000000580-0x000000000000059F (\_SB_.PCI0.SMB_.SMIO) (20150410/utaddress-254)
Feb 14 19:11:23 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 19:11:23 linux-ytaf kernel: pps_core: LinuxPPS API ver. 1 registered
Feb 14 19:11:23 linux-ytaf kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
Feb 14 19:11:23 linux-ytaf kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Feb 14 19:11:23 linux-ytaf kernel: PTP clock support registered
Feb 14 19:11:23 linux-ytaf kernel: e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
Feb 14 19:11:23 linux-ytaf kernel: e1000e: Copyright(c) 1999 - 2014 Intel Corporation.
Feb 14 19:11:23 linux-ytaf kernel: e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
Feb 14 19:11:23 linux-ytaf kernel: asus_wmi: ASUS WMI generic driver loaded
Feb 14 19:11:23 linux-ytaf kernel: asus_wmi: Initialization: 0x0
Feb 14 19:11:23 linux-ytaf kernel: asus_wmi: BIOS WMI version: 0.9
Feb 14 19:11:23 linux-ytaf kernel: asus_wmi: SFUN value: 0x0
Feb 14 19:11:23 linux-ytaf kernel: input: Eee PC WMI hotkeys as /devices/platform/eeepc-wmi/input/input9
Feb 14 19:11:23 linux-ytaf kernel: asus_wmi: Disabling ACPI video driver
Feb 14 19:11:23 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: registered PHC clock
Feb 14 19:11:23 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) c8:60:00:09:38:76
Feb 14 19:11:23 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
Feb 14 19:11:23 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: FFFFFF-0FF
Feb 14 19:11:23 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20150410/utaddress-254)
Feb 14 19:11:23 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 19:11:23 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150410/utaddress-254)
Feb 14 19:11:23 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150410/utaddress-254)
Feb 14 19:11:23 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 19:11:23 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150410/utaddress-254)
Feb 14 19:11:23 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150410/utaddress-254)
Feb 14 19:11:23 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 19:11:23 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150410/utaddress-254)
Feb 14 19:11:23 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150410/utaddress-254)
Feb 14 19:11:23 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 19:11:23 linux-ytaf kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
Feb 14 19:11:23 linux-ytaf kernel: iTCO_vendor_support: vendor-support=0
Feb 14 19:11:23 linux-ytaf kernel: iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
Feb 14 19:11:23 linux-ytaf kernel: iTCO_wdt: Found a Cougar Point TCO device (Version=2, TCOBASE=0x0460)
Feb 14 19:11:23 linux-ytaf kernel: iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
Feb 14 19:11:23 linux-ytaf mtp-probe[595]: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4"
Feb 14 19:11:23 linux-ytaf mtp-probe[608]: checking bus 5, device 2: "/sys/devices/pci0000:00/0000:00:1c.5/0000:05:00.0/usb5/5-2"
Feb 14 19:11:23 linux-ytaf mtp-probe[594]: checking bus 4, device 3: "/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1"
Feb 14 19:11:23 linux-ytaf mtp-probe[595]: bus: 1, device: 3 was not an MTP device
Feb 14 19:11:23 linux-ytaf mtp-probe[594]: bus: 4, device: 3 was not an MTP device
Feb 14 19:11:23 linux-ytaf mtp-probe[608]: bus: 5, device: 2 was not an MTP device
Feb 14 19:11:23 linux-ytaf kernel: input: Saitek Cyborg R.A.T.7 Mouse as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/0003:06A3:0CCB.0003/input/input10
Feb 14 19:11:23 linux-ytaf kernel: saitek 0003:06A3:0CCB.0003: input,hidraw2: USB HID v1.11 Mouse [Saitek Cyborg R.A.T.7 Mouse] on usb-0000:00:1a.0-1.4/input0
Feb 14 19:11:23 linux-ytaf kernel: AVX version of gcm_enc/dec engaged.
Feb 14 19:11:23 linux-ytaf kernel: AES CTR mode by8 optimization enabled
Feb 14 19:11:23 linux-ytaf kernel: Adding 2104316k swap on /dev/sdb2.  Priority:-1 extents:1 across:2104316k FS
Feb 14 19:11:23 linux-ytaf kernel: snd_hda_intel 0000:00:1b.0: enabling device (0000 -> 0002)
Feb 14 19:11:23 linux-ytaf kernel: snd_hda_intel 0000:02:00.1: enabling device (0000 -> 0002)
Feb 14 19:11:23 linux-ytaf kernel: snd_hda_intel 0000:02:00.1: Disabling MSI
Feb 14 19:11:23 linux-ytaf kernel: snd_hda_intel 0000:02:00.1: Handle VGA-switcheroo audio client
Feb 14 19:11:24 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC889: line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line
Feb 14 19:11:24 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Feb 14 19:11:24 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
Feb 14 19:11:24 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
Feb 14 19:11:24 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    dig-out=0x11/0x1e
Feb 14 19:11:24 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    inputs:
Feb 14 19:11:24 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:      Front Mic=0x19
Feb 14 19:11:24 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:      Rear Mic=0x18
Feb 14 19:11:24 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:      Line=0x1a
Feb 14 19:11:24 linux-ytaf kernel: input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
Feb 14 19:11:24 linux-ytaf kernel: input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
Feb 14 19:11:24 linux-ytaf kernel: input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input13
Feb 14 19:11:24 linux-ytaf kernel: input: HDA Intel PCH Line Out Front as /devices/pci0000:00/0000:00:1b.0/sound/card0/input14
Feb 14 19:11:24 linux-ytaf kernel: input: HDA Intel PCH Line Out Surround as /devices/pci0000:00/0000:00:1b.0/sound/card0/input15
Feb 14 19:11:24 linux-ytaf kernel: input: HDA Intel PCH Line Out CLFE as /devices/pci0000:00/0000:00:1b.0/sound/card0/input16
Feb 14 19:11:24 linux-ytaf kernel: input: HDA Intel PCH Line Out Side as /devices/pci0000:00/0000:00:1b.0/sound/card0/input17
Feb 14 19:11:24 linux-ytaf kernel: input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input18
Feb 14 19:11:24 linux-ytaf kernel: FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Feb 14 19:11:24 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input19
Feb 14 19:11:24 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input20
Feb 14 19:11:24 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input21
Feb 14 19:11:24 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input22
Feb 14 19:11:24 linux-ytaf systemd-fsck[719]: /sbin/fsck.xfs: XFS file system.
Feb 14 19:11:24 linux-ytaf kernel: SGI XFS with ACLs, security attributes, realtime, no debug enabled
Feb 14 19:11:24 linux-ytaf kernel: XFS (sdb4): Mounting V5 Filesystem
Feb 14 19:11:25 linux-ytaf kernel: XFS (sdb4): Ending clean mount
Feb 14 19:11:25 linux-ytaf systemd-journal[474]: Permanent journal is using 80.0M (max allowed 4.0G, trying to leave 4.0G free of 32.8G available → current limit 4.0G).
Feb 14 19:11:25 linux-ytaf systemd-journal[474]: Time spent on flushing to /var is 154.007ms for 1031 entries.
Feb 14 19:11:26 linux-ytaf kernel: audit: type=1305 audit(1455473485.323:2): audit_pid=756 old=0 auid=4294967295 ses=4294967295 res=1
Feb 14 19:11:25 linux-ytaf auditd[756]: Started dispatcher: /sbin/audispd pid: 766
Feb 14 19:11:25 linux-ytaf audispd[766]: priority_boost_parser called with: 4
Feb 14 19:11:25 linux-ytaf audispd[766]: max_restarts_parser called with: 10
Feb 14 19:11:25 linux-ytaf audispd[766]: No plugins found, exiting
Feb 14 19:11:25 linux-ytaf auditd[756]: Init complete, auditd 2.3.6 listening for events (startup state enable)
Feb 14 19:11:26 linux-ytaf avahi-daemon[937]: Found user 'avahi' (UID 486) and group 'avahi' (GID 485).
Feb 14 19:11:26 linux-ytaf avahi-daemon[937]: Successfully dropped root privileges.
Feb 14 19:11:26 linux-ytaf avahi-daemon[937]: avahi-daemon 0.6.31 starting up.
Feb 14 19:11:26 linux-ytaf avahi-daemon[937]: Loading service file /etc/avahi/services/sftp-ssh.service.
Feb 14 19:11:26 linux-ytaf avahi-daemon[937]: Loading service file /etc/avahi/services/ssh.service.
Feb 14 19:11:26 linux-ytaf avahi-daemon[937]: Network interface enumeration completed.
Feb 14 19:11:26 linux-ytaf avahi-daemon[937]: Registering HINFO record with values 'X86_64'/'LINUX'.
Feb 14 19:11:26 linux-ytaf smartd[943]: smartd 6.2 2013-11-07 r3856 [x86_64-linux-4.1.15-8-default] (SUSE RPM)
Feb 14 19:11:26 linux-ytaf avahi-daemon[937]: Server startup complete. Host name is linux-ytaf.local. Local service cookie is 1609623050.
Feb 14 19:11:26 linux-ytaf smartd[943]: Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
Feb 14 19:11:26 linux-ytaf avahi-daemon[937]: Service "linux-ytaf" (/etc/avahi/services/ssh.service) successfully established.
Feb 14 19:11:26 linux-ytaf avahi-daemon[937]: Service "linux-ytaf" (/etc/avahi/services/sftp-ssh.service) successfully established.
Feb 14 19:11:26 linux-ytaf smartd[943]: Opened configuration file /etc/smartd.conf
Feb 14 19:11:26 linux-ytaf auditctl[757]: No rules
Feb 14 19:11:26 linux-ytaf auditctl[757]: AUDIT_STATUS: enabled=0 flag=1 pid=0 rate_limit=0 backlog_limit=320 lost=0 backlog=0
Feb 14 19:11:26 linux-ytaf boot.apparmor[774]: Starting AppArmor ..done
Feb 14 19:11:26 linux-ytaf dbus-daemon[936]: Unknown username "srvGeoClue" in message bus configuration file
Feb 14 19:11:26 linux-ytaf smartd[943]: Drive: DEVICESCAN, implied '-a' Directive on line 26 of file /etc/smartd.conf
Feb 14 19:11:26 linux-ytaf smartd[943]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
Feb 14 19:11:26 linux-ytaf smartd[943]: Device: /dev/sda, type changed from 'scsi' to 'sat'
Feb 14 19:11:26 linux-ytaf smartd[943]: Device: /dev/sda [SAT], opened
Feb 14 19:11:26 linux-ytaf smartd[943]: Device: /dev/sda [SAT], SAMSUNG SSD 830 Series, S/N:S0Z4NEAC906195, WWN:5-002538-043584d30, FW:CXM03B1Q, 256 GB
Feb 14 19:11:26 linux-ytaf smartd[943]: Device: /dev/sda [SAT], found in smartd database: Samsung based SSDs
Feb 14 19:11:26 linux-ytaf smartd[943]: Device: /dev/sda [SAT], can't monitor Current_Pending_Sector count - no Attribute 197
Feb 14 19:11:26 linux-ytaf smartd[943]: Device: /dev/sda [SAT], can't monitor Offline_Uncorrectable count - no Attribute 198
Feb 14 19:11:26 linux-ytaf smartd[943]: Device: /dev/sda [SAT], is SMART capable. Adding to "monitor" list.
Feb 14 19:11:26 linux-ytaf smartd[943]: Device: /dev/sda [SAT], state read from /var/lib/smartmontools/smartd.SAMSUNG_SSD_830_Series-S0Z4NEAC906195.ata.state
Feb 14 19:11:26 linux-ytaf smartd[943]: Device: /dev/sdb, type changed from 'scsi' to 'sat'
Feb 14 19:11:26 linux-ytaf smartd[943]: Device: /dev/sdb [SAT], opened
Feb 14 19:11:26 linux-ytaf smartd[943]: Device: /dev/sdb [SAT], TOSHIBA HDWD110, S/N:Y5GDEMGFS, WWN:5-000039-fe7c5a79c, FW:MS2OA8J0, 1.00 TB
Feb 14 19:11:26 linux-ytaf smartd[943]: Device: /dev/sdb [SAT], not found in smartd database.
Feb 14 19:11:27 linux-ytaf ModemManager[939]: <info>  ModemManager (version 1.4.10) starting in system bus...
Feb 14 19:11:27 linux-ytaf dbus[936]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Feb 14 19:11:28 linux-ytaf smartd[943]: Device: /dev/sdb [SAT], is SMART capable. Adding to "monitor" list.
Feb 14 19:11:28 linux-ytaf smartd[943]: Device: /dev/sdb [SAT], state read from /var/lib/smartmontools/smartd.TOSHIBA_HDWD110-Y5GDEMGFS.ata.state
Feb 14 19:11:28 linux-ytaf smartd[943]: Monitoring 2 ATA and 0 SCSI devices
Feb 14 19:11:28 linux-ytaf smartd[943]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 76 to 77
Feb 14 19:11:28 linux-ytaf display-manager[955]: /etc/vconsole.conf available
Feb 14 19:11:28 linux-ytaf display-manager[955]: KEYMAP: de-latin1-nodeadkeys
Feb 14 19:11:28 linux-ytaf display-manager[955]: Command: localectl set-keymap de-latin1-nodeadkeys
Feb 14 19:11:28 linux-ytaf smartd[943]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 230 to 250
Feb 14 19:11:28 linux-ytaf display-manager[955]: I: Using systemd /usr/share/systemd/kbd-model-map mapping
Feb 14 19:11:28 linux-ytaf dbus[936]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service'
Feb 14 19:11:28 linux-ytaf dbus[936]: [system] Successfully activated service 'org.freedesktop.locale1'
Feb 14 19:11:29 linux-ytaf smartd[943]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.SAMSUNG_SSD_830_Series-S0Z4NEAC906195.ata.state
Feb 14 19:11:29 linux-ytaf smartd[943]: Device: /dev/sdb [SAT], state written to /var/lib/smartmontools/smartd.TOSHIBA_HDWD110-Y5GDEMGFS.ata.state
Feb 14 19:11:29 linux-ytaf kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
Feb 14 19:11:29 linux-ytaf polkitd[979]: Started polkitd version 0.113
Feb 14 19:11:29 linux-ytaf kernel: nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
Feb 14 19:11:29 linux-ytaf kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Feb 14 19:11:29 linux-ytaf SuSEfirewall2[1050]: Firewall rules set to CLOSE.
Feb 14 19:11:29 linux-ytaf logger[996]: /etc/init.d/xdm: No changes for /etc/X11/xdm/Xservers
Feb 14 19:11:29 linux-ytaf logger[996]: /etc/init.d/xdm: No changes for /etc/X11/xdm/xdm-config
Feb 14 19:11:30 linux-ytaf polkitd[979]: Loading rules from directory /etc/polkit-1/rules.d
Feb 14 19:11:30 linux-ytaf polkitd[979]: Loading rules from directory /usr/share/polkit-1/rules.d
Feb 14 19:11:30 linux-ytaf kernel: No iBFT detected.
Feb 14 19:11:30 linux-ytaf polkitd[979]: Finished loading, compiling and executing 3 rules
Feb 14 19:11:30 linux-ytaf dbus[936]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Feb 14 19:11:30 linux-ytaf polkitd[979]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
Feb 14 19:11:30 linux-ytaf sddm[1087]: Adding new display on vt 7 ...
Feb 14 19:11:30 linux-ytaf sddm[1087]: Display server starting...
Feb 14 19:11:30 linux-ytaf sddm[1087]: Running: /usr/bin/X -nolisten tcp -auth /run/sddm/{59dc364d-7cfe-41d6-baf4-cdb8242ce8d4} -background none -noreset -displayfd 17 vt7
Feb 14 19:11:30 linux-ytaf display-manager[955]: Starting service sddm..done
Feb 14 19:11:32 linux-ytaf ModemManager[939]: <info>  Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin
Feb 14 19:11:33 linux-ytaf sddm[1087]: Socket server started.
Feb 14 19:11:33 linux-ytaf sddm[1087]: Greeter starting...
Feb 14 19:11:33 linux-ytaf sddm[1087]: Adding cookie to "/run/sddm/{59dc364d-7cfe-41d6-baf4-cdb8242ce8d4}"
Feb 14 19:11:33 linux-ytaf sddm-helper[1225]: [PAM] Starting...
Feb 14 19:11:33 linux-ytaf sddm-helper[1225]: [PAM] Authenticating...
Feb 14 19:11:33 linux-ytaf sddm-helper[1225]: [PAM] returning.
Feb 14 19:11:33 linux-ytaf sddm-helper[1225]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
Feb 14 19:11:33 linux-ytaf systemd[1227]: pam_unix(systemd-user:session): session opened for user sddm by (uid=0)
Feb 14 19:11:33 linux-ytaf sddm[1087]: Message received from greeter: Connect
Feb 14 19:11:33 linux-ytaf kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Feb 14 19:11:33 linux-ytaf wickedd-dhcp4[1053]: eth0: Request to acquire DHCPv4 lease with UUID 52c3c056-268a-0500-1f04-000004000000
Feb 14 19:11:33 linux-ytaf kernel: NET: Registered protocol family 17
Feb 14 19:11:34 linux-ytaf wickedd-dhcp4[1053]: eth0: Committed DHCPv4 lease with address 192.168.178.12 (lease time 864000 sec, renew in 432000 sec, rebind in 756000 sec)
Feb 14 19:11:34 linux-ytaf avahi-daemon[937]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.178.12.
Feb 14 19:11:34 linux-ytaf avahi-daemon[937]: New relevant interface eth0.IPv4 for mDNS.
Feb 14 19:11:34 linux-ytaf avahi-daemon[937]: Registering new address record for 192.168.178.12 on eth0.IPv4.
Feb 14 19:11:34 linux-ytaf wickedd[1055]: eth0: Notified neighbours about IP address 192.168.178.12
Feb 14 19:11:34 MM-Home wicked[1058]: lo              up
Feb 14 19:11:34 MM-Home wicked[1058]: eth0            up
Feb 14 19:11:34 MM-Home echo[1414]: Starting mail service (Postfix)
Feb 14 19:11:34 MM-Home iscsiadm[1416]: iscsiadm: No records found
Feb 14 19:11:34 MM-Home SuSEfirewall2[1447]: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Feb 14 19:11:34 MM-Home SuSEfirewall2[1455]: using default zone 'ext' for interface eth0
Feb 14 19:11:35 MM-Home SuSEfirewall2[1603]: Firewall rules successfully set
Feb 14 19:11:35 MM-Home ntpd[1435]: ntpd 4.2.8p4@1.3265-o Thu Dec 17 05:32:52 UTC 2015 (1): Starting
Feb 14 19:11:35 MM-Home ntpd[1435]: Command line: /usr/sbin/ntpd -p /var/run/ntp/ntpd.pid -g -u ntp:ntp -c /etc/ntp.conf
Feb 14 19:11:35 MM-Home sntp[1606]: sntp 4.2.8p4@1.3265-o Thu Dec 17 05:32:29 UTC 2015 (1)
Feb 14 19:11:35 MM-Home sntp[1606]: kod_init_kod_db(): Cannot open KoD db file /var/db/ntp-kod: No such file or directory
Feb 14 19:11:35 MM-Home ntpd[1605]: proto: precision = 0.085 usec (-23)
Feb 14 19:11:35 MM-Home start-ntpd[1419]: Starting network time protocol daemon (NTPD)sntp 4.2.8p4@1.3265-o Thu Dec 17 05:32:29 UTC 2015 (1)
Feb 14 19:11:35 MM-Home start-ntpd[1419]: kod_init_kod_db(): Cannot open KoD db file /var/db/ntp-kod: No such file or directory
Feb 14 19:11:35 MM-Home ntpd[1605]: switching logging to file /var/log/ntp
Feb 14 19:11:35 MM-Home sntp[1606]: 2016-02-14 19:11:35.323240 (-0100) -0.43881 +/- 0.345538 192.168.178.1 s3 no-leap
Feb 14 19:11:34 MM-Home start-ntpd[1419]: 2016-02-14 19:11:35.323240 (-0100) -0.43881 +/- 0.345538 192.168.178.1 s3 no-leap
Feb 14 19:11:34 MM-Home /usr/sbin/start-ntpd[1611]: runtime configuration: server 192.168.178.1
Feb 14 19:11:34 MM-Home start-ntpd[1419]: /usr/sbin/ntpq: read: Connection refused
Feb 14 19:11:35 MM-Home postfix/postfix-script[1613]: starting the Postfix mail system
Feb 14 19:11:35 MM-Home postfix/master[1615]: daemon started -- version 2.11.6, configuration /etc/postfix
Feb 14 19:11:35 MM-Home cron[1633]: (CRON) INFO (RANDOM_DELAY will be scaled with factor 67% if used.)
Feb 14 19:11:35 MM-Home cron[1633]: (CRON) INFO (running with inotify support)
Feb 14 19:11:36 MM-Home dbus[936]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
Feb 14 19:11:36 MM-Home udisksd[1637]: udisks daemon version 2.1.6 starting
Feb 14 19:11:36 MM-Home dbus[936]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Feb 14 19:11:36 MM-Home udisksd[1637]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Feb 14 19:11:36 MM-Home dbus[936]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
Feb 14 19:11:36 MM-Home dbus[936]: [system] Successfully activated service 'org.freedesktop.UPower'
Feb 14 19:14:11 MM-Home kernel: nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
Feb 14 19:15:01 MM-Home cron[1677]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 19:15:01 MM-Home systemd[1678]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 19:15:01 MM-Home CRON[1677]: pam_unix(crond:session): session closed for user root
Feb 14 19:15:01 MM-Home systemd[1679]: pam_unix(systemd-user:session): session closed for user root
Feb 14 19:16:08 MM-Home sddm[1087]: Message received from greeter: Login
Feb 14 19:16:08 MM-Home sddm[1087]: Session "/usr/share/xsessions/plasma5.desktop" selected, command: "/usr/bin/startkde"
Feb 14 19:16:08 MM-Home sddm-helper[1725]: [PAM] Starting...
Feb 14 19:16:08 MM-Home sddm-helper[1725]: [PAM] Authenticating...
Feb 14 19:16:08 MM-Home sddm-helper[1725]: [PAM] Preparing to converse...
Feb 14 19:16:08 MM-Home sddm-helper[1725]: [PAM] Conversation with 1 messages
Feb 14 19:16:08 MM-Home sddm-helper[1725]: [PAM] returning.
Feb 14 19:16:08 MM-Home sddm[1087]: Authenticated successfully
Feb 14 19:16:08 MM-Home sddm-helper[1725]: pam_unix(sddm:session): session opened for user marc by (uid=0)
Feb 14 19:16:08 MM-Home systemd[1726]: pam_unix(systemd-user:session): session opened for user marc by (uid=0)
Feb 14 19:16:08 MM-Home sddm-helper[1728]: Adding cookie to "/home/marc/.Xauthority"
Feb 14 19:16:08 MM-Home sddm-helper[1225]: [PAM] Ended.
Feb 14 19:16:08 MM-Home sddm[1087]: Auth: sddm-helper exited successfully
Feb 14 19:16:08 MM-Home sddm[1087]: Greeter stopped.
Feb 14 19:16:09 MM-Home dbus[936]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Feb 14 19:16:09 MM-Home org.kde.powerdevil.backlighthelper[936]: powerdevil: no kernel backlight interface found
Feb 14 19:16:09 MM-Home dbus[936]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Feb 14 19:16:09 MM-Home polkitd[979]: Registered Authentication Agent for unix-session:3 (system bus name :1.37 [/usr/lib64/libexec/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale de_DE.UTF-8)
Feb 14 19:16:09 MM-Home dbus[936]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service'
Feb 14 19:16:10 MM-Home dbus[936]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Feb 14 19:16:10 MM-Home rtkit-daemon[1880]: Successfully called chroot.
Feb 14 19:16:10 MM-Home rtkit-daemon[1880]: Successfully dropped privileges.
Feb 14 19:16:10 MM-Home rtkit-daemon[1880]: Successfully limited resources.
Feb 14 19:16:10 MM-Home rtkit-daemon[1880]: Running.
Feb 14 19:16:10 MM-Home rtkit-daemon[1880]: Canary thread running.
Feb 14 19:16:10 MM-Home rtkit-daemon[1880]: Watchdog thread running.
Feb 14 19:16:10 MM-Home rtkit-daemon[1880]: Successfully made thread 1879 of process 1879 (/usr/bin/pulseaudio) owned by 'marc' high priority at nice level -11.
Feb 14 19:16:10 MM-Home rtkit-daemon[1880]: Supervising 1 threads of 1 processes of 1 users.
Feb 14 19:16:12 MM-Home rtkit-daemon[1880]: Supervising 1 threads of 1 processes of 1 users.
Feb 14 19:16:12 MM-Home rtkit-daemon[1880]: Successfully made thread 1905 of process 1879 (/usr/bin/pulseaudio) owned by 'marc' RT at priority 5.
Feb 14 19:16:12 MM-Home rtkit-daemon[1880]: Supervising 2 threads of 1 processes of 1 users.
Feb 14 19:16:13 MM-Home rtkit-daemon[1880]: Supervising 2 threads of 1 processes of 1 users.
Feb 14 19:16:13 MM-Home rtkit-daemon[1880]: Successfully made thread 1913 of process 1879 (/usr/bin/pulseaudio) owned by 'marc' RT at priority 5.
Feb 14 19:16:13 MM-Home rtkit-daemon[1880]: Supervising 3 threads of 1 processes of 1 users.
Feb 14 19:16:13 MM-Home rtkit-daemon[1880]: Supervising 3 threads of 1 processes of 1 users.
Feb 14 19:16:13 MM-Home rtkit-daemon[1880]: Successfully made thread 1914 of process 1879 (/usr/bin/pulseaudio) owned by 'marc' RT at priority 5.
Feb 14 19:16:13 MM-Home rtkit-daemon[1880]: Supervising 4 threads of 1 processes of 1 users.
Feb 14 19:16:13 MM-Home dbus[936]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Feb 14 19:16:13 MM-Home bluetoothd[1915]: Bluetooth daemon 5.35
Feb 14 19:16:13 MM-Home dbus[936]: [system] Successfully activated service 'org.bluez'
Feb 14 19:16:13 MM-Home rtkit-daemon[1880]: Successfully made thread 1919 of process 1919 (/usr/bin/pulseaudio) owned by 'marc' high priority at nice level -11.
Feb 14 19:16:13 MM-Home bluetoothd[1915]: Starting SDP server
Feb 14 19:16:13 MM-Home rtkit-daemon[1880]: Supervising 5 threads of 2 processes of 1 users.
Feb 14 19:16:13 MM-Home pulseaudio[1919]: [pulseaudio] pid.c: Daemon already running.
Feb 14 19:16:13 MM-Home kernel: Bluetooth: Core ver 2.20
Feb 14 19:16:13 MM-Home kernel: NET: Registered protocol family 31
Feb 14 19:16:13 MM-Home kernel: Bluetooth: HCI device and connection manager initialized
Feb 14 19:16:13 MM-Home kernel: Bluetooth: HCI socket layer initialized
Feb 14 19:16:13 MM-Home kernel: Bluetooth: L2CAP socket layer initialized
Feb 14 19:16:13 MM-Home kernel: Bluetooth: SCO socket layer initialized
Feb 14 19:16:13 MM-Home kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Feb 14 19:16:13 MM-Home kernel: Bluetooth: BNEP filters: protocol multicast
Feb 14 19:16:13 MM-Home kernel: Bluetooth: BNEP socket layer initialized
Feb 14 19:16:13 MM-Home dbus[936]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Feb 14 19:16:13 MM-Home bluetoothd[1915]: Bluetooth management interface 1.9 initialized
Feb 14 19:16:13 MM-Home rtkit-daemon[1880]: Successfully made thread 1925 of process 1925 (/usr/bin/pulseaudio) owned by 'marc' high priority at nice level -11.
Feb 14 19:16:13 MM-Home rtkit-daemon[1880]: Supervising 5 threads of 2 processes of 1 users.
Feb 14 19:16:13 MM-Home pulseaudio[1925]: [pulseaudio] pid.c: Daemon already running.
Feb 14 19:16:13 MM-Home dbus[936]: [system] Successfully activated service 'org.freedesktop.hostname1'
Feb 14 19:16:14 MM-Home dbus[936]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service'
Feb 14 19:16:14 MM-Home PackageKit[1930]: daemon start
Feb 14 19:16:14 MM-Home dbus[936]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Feb 14 19:16:14 MM-Home PackageKit[1930]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 19:16:14 MM-Home PackageKit[1930]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 19:16:14 MM-Home PackageKit[1930]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 19:16:14 MM-Home PackageKit[1930]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 19:16:15 MM-Home PackageKit[1930]: refresh-cache transaction /1_edbccacd from uid 1000 finished with failed after 843ms
Feb 14 19:16:15 MM-Home kernel: fuse init (API version 7.23)
Feb 14 19:16:16 MM-Home PackageKit[1930]: refresh-cache transaction /2_bebacbdc from uid 1000 finished with failed after 302ms
Feb 14 19:16:34 MM-Home PackageKit[1930]: daemon quit
Feb 14 19:16:34 MM-Home packagekitd[1930]: (packagekitd:1930): GLib-CRITICAL **: Source ID 6 was not found when attempting to remove it
Feb 14 19:30:01 MM-Home cron[2217]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 19:30:01 MM-Home systemd[2218]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 19:30:01 MM-Home CRON[2217]: pam_unix(crond:session): session closed for user root
Feb 14 19:30:01 MM-Home systemd[2219]: pam_unix(systemd-user:session): session closed for user root
Feb 14 19:33:11 MM-Home polkitd[979]: Unregistered Authentication Agent for unix-session:3 (system bus name :1.37, object path /org/kde/PolicyKit1/AuthenticationAgent, locale de_DE.UTF-8)
Feb 14 19:33:11 MM-Home sddm[1087]: Auth: sddm-helper crashed (exit code 15)
Feb 14 19:33:11 MM-Home sddm[1087]: Authentication error: "Process crashed"
Feb 14 19:33:11 MM-Home sddm[1087]: Auth: sddm-helper exited with 15
Feb 14 19:33:11 MM-Home sddm[1087]: Socket server stopping...
-- Reboot --
Feb 14 19:40:48 linux-ytaf systemd-journal[187]: Runtime journal is using 8.0M (max allowed 397.5M, trying to leave 596.3M free of 3.8G available → current limit 397.5M).
Feb 14 19:40:48 linux-ytaf systemd-journal[187]: Runtime journal is using 8.0M (max allowed 397.5M, trying to leave 596.3M free of 3.8G available → current limit 397.5M).
Feb 14 19:40:48 linux-ytaf kernel: microcode: CPU0 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 19:40:48 linux-ytaf kernel: Initializing cgroup subsys cpuset
Feb 14 19:40:48 linux-ytaf kernel: Initializing cgroup subsys cpu
Feb 14 19:40:48 linux-ytaf kernel: Initializing cgroup subsys cpuacct
Feb 14 19:40:48 linux-ytaf kernel: Linux version 4.1.15-8-default (geeko@buildhost) (gcc version 4.8.5 (SUSE Linux) ) #1 SMP PREEMPT Wed Jan 20 16:41:00 UTC 2016 (0e3b3ab)
Feb 14 19:40:48 linux-ytaf kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.1.15-8-default root=UUID=21024970-7a27-4114-8525-d8dd026f23b6 ro resume=/dev/sdb2 splash=silent quiet showopts
Feb 14 19:40:48 linux-ytaf kernel: e820: BIOS-provided physical RAM map:
Feb 14 19:40:48 linux-ytaf kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Feb 14 19:40:48 linux-ytaf kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
Feb 14 19:40:48 linux-ytaf kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000deb8efff] usable
Feb 14 19:40:48 linux-ytaf kernel: BIOS-e820: [mem 0x00000000deb8f000-0x00000000dedf1fff] reserved
Feb 14 19:40:48 linux-ytaf kernel: BIOS-e820: [mem 0x00000000dedf2000-0x00000000dee79fff] ACPI NVS
Feb 14 19:40:48 linux-ytaf kernel: BIOS-e820: [mem 0x00000000dee7a000-0x00000000df13efff] reserved
Feb 14 19:40:48 linux-ytaf kernel: BIOS-e820: [mem 0x00000000df13f000-0x00000000df383fff] ACPI NVS
Feb 14 19:40:48 linux-ytaf kernel: BIOS-e820: [mem 0x00000000df384000-0x00000000df391fff] ACPI data
Feb 14 19:40:48 linux-ytaf kernel: BIOS-e820: [mem 0x00000000df392000-0x00000000df3befff] ACPI NVS
Feb 14 19:40:48 linux-ytaf kernel: BIOS-e820: [mem 0x00000000df3bf000-0x00000000df3c3fff] ACPI data
Feb 14 19:40:48 linux-ytaf kernel: BIOS-e820: [mem 0x00000000df3c4000-0x00000000df406fff] ACPI NVS
Feb 14 19:40:48 linux-ytaf kernel: BIOS-e820: [mem 0x00000000df407000-0x00000000df7fffff] usable
Feb 14 19:40:48 linux-ytaf kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Feb 14 19:40:48 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Feb 14 19:40:48 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Feb 14 19:40:48 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Feb 14 19:40:48 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Feb 14 19:40:48 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Feb 14 19:40:48 linux-ytaf kernel: BIOS-e820: [mem 0x0000000100000000-0x000000021effffff] usable
Feb 14 19:40:48 linux-ytaf kernel: NX (Execute Disable) protection: active
Feb 14 19:40:48 linux-ytaf kernel: e820: update [mem 0x0c81c018-0x0c82bc57] usable ==> usable
Feb 14 19:40:48 linux-ytaf kernel: e820: update [mem 0x0c82c018-0x0c83b857] usable ==> usable
Feb 14 19:40:48 linux-ytaf kernel: e820: update [mem 0x0c2f1018-0x0c2f4e57] usable ==> usable
Feb 14 19:40:48 linux-ytaf kernel: extended physical RAM map:
Feb 14 19:40:48 linux-ytaf kernel: reserve setup_data: [mem 0x0000000000000000-0x000000000009efff] usable
Feb 14 19:40:48 linux-ytaf kernel: reserve setup_data: [mem 0x000000000009f000-0x000000000009ffff] reserved
Feb 14 19:40:48 linux-ytaf kernel: reserve setup_data: [mem 0x0000000000100000-0x000000000c2f1017] usable
Feb 14 19:40:48 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c2f1018-0x000000000c2f4e57] usable
Feb 14 19:40:48 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c2f4e58-0x000000000c81c017] usable
Feb 14 19:40:48 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c81c018-0x000000000c82bc57] usable
Feb 14 19:40:48 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c82bc58-0x000000000c82c017] usable
Feb 14 19:40:48 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c82c018-0x000000000c83b857] usable
Feb 14 19:40:48 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c83b858-0x00000000deb8efff] usable
Feb 14 19:40:48 linux-ytaf kernel: reserve setup_data: [mem 0x00000000deb8f000-0x00000000dedf1fff] reserved
Feb 14 19:40:48 linux-ytaf kernel: reserve setup_data: [mem 0x00000000dedf2000-0x00000000dee79fff] ACPI NVS
Feb 14 19:40:48 linux-ytaf kernel: reserve setup_data: [mem 0x00000000dee7a000-0x00000000df13efff] reserved
Feb 14 19:40:48 linux-ytaf kernel: reserve setup_data: [mem 0x00000000df13f000-0x00000000df383fff] ACPI NVS
Feb 14 19:40:48 linux-ytaf kernel: reserve setup_data: [mem 0x00000000df384000-0x00000000df391fff] ACPI data
Feb 14 19:40:48 linux-ytaf kernel: reserve setup_data: [mem 0x00000000df392000-0x00000000df3befff] ACPI NVS
Feb 14 19:40:48 linux-ytaf kernel: reserve setup_data: [mem 0x00000000df3bf000-0x00000000df3c3fff] ACPI data
Feb 14 19:40:48 linux-ytaf kernel: reserve setup_data: [mem 0x00000000df3c4000-0x00000000df406fff] ACPI NVS
Feb 14 19:40:48 linux-ytaf kernel: reserve setup_data: [mem 0x00000000df407000-0x00000000df7fffff] usable
Feb 14 19:40:48 linux-ytaf kernel: reserve setup_data: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Feb 14 19:40:48 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Feb 14 19:40:48 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Feb 14 19:40:48 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Feb 14 19:40:48 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Feb 14 19:40:48 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Feb 14 19:40:48 linux-ytaf kernel: reserve setup_data: [mem 0x0000000100000000-0x000000021effffff] usable
Feb 14 19:40:48 linux-ytaf kernel: efi: EFI v2.31 by American Megatrends
Feb 14 19:40:48 linux-ytaf kernel: efi:  ACPI=0xdf384000  ACPI 2.0=0xdf384000  SMBIOS=0xdec27e98  MPS=0xfc990 
Feb 14 19:40:48 linux-ytaf kernel: SMBIOS 2.6 present.
Feb 14 19:40:48 linux-ytaf kernel: DMI: System manufacturer System Product Name/MAXIMUS IV GENE-Z/GEN3, BIOS 3603 11/09/2012
Feb 14 19:40:48 linux-ytaf kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Feb 14 19:40:48 linux-ytaf kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Feb 14 19:40:48 linux-ytaf kernel: AGP: No AGP bridge found
Feb 14 19:40:48 linux-ytaf kernel: e820: last_pfn = 0x21f000 max_arch_pfn = 0x400000000
Feb 14 19:40:48 linux-ytaf kernel: MTRR default type: uncachable
Feb 14 19:40:48 linux-ytaf kernel: MTRR fixed ranges enabled:
Feb 14 19:40:48 linux-ytaf kernel:   00000-9FFFF write-back
Feb 14 19:40:48 linux-ytaf kernel:   A0000-BFFFF uncachable
Feb 14 19:40:48 linux-ytaf kernel:   C0000-D3FFF write-protect
Feb 14 19:40:48 linux-ytaf kernel:   D4000-DFFFF uncachable
Feb 14 19:40:48 linux-ytaf kernel:   E0000-E7FFF write-through
Feb 14 19:40:48 linux-ytaf kernel:   E8000-FFFFF write-protect
Feb 14 19:40:48 linux-ytaf kernel: MTRR variable ranges enabled:
Feb 14 19:40:48 linux-ytaf kernel:   0 base 000000000 mask E00000000 write-back
Feb 14 19:40:48 linux-ytaf kernel:   1 base 200000000 mask FF0000000 write-back
Feb 14 19:40:48 linux-ytaf kernel:   2 base 210000000 mask FF8000000 write-back
Feb 14 19:40:48 linux-ytaf kernel:   3 base 218000000 mask FFC000000 write-back
Feb 14 19:40:48 linux-ytaf kernel:   4 base 21C000000 mask FFE000000 write-back
Feb 14 19:40:48 linux-ytaf kernel:   5 base 21E000000 mask FFF000000 write-back
Feb 14 19:40:48 linux-ytaf kernel:   6 base 0E0000000 mask FE0000000 uncachable
Feb 14 19:40:48 linux-ytaf kernel:   7 disabled
Feb 14 19:40:48 linux-ytaf kernel:   8 disabled
Feb 14 19:40:48 linux-ytaf kernel:   9 disabled
Feb 14 19:40:48 linux-ytaf kernel: PAT configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- UC  
Feb 14 19:40:48 linux-ytaf kernel: e820: update [mem 0xe0000000-0xffffffff] usable ==> reserved
Feb 14 19:40:48 linux-ytaf kernel: e820: last_pfn = 0xdf800 max_arch_pfn = 0x400000000
Feb 14 19:40:48 linux-ytaf kernel: found SMP MP-table at [mem 0x000fcd30-0x000fcd3f] mapped at [ffff8800000fcd30]
Feb 14 19:40:48 linux-ytaf kernel: Scanning 1 areas for low memory corruption
Feb 14 19:40:48 linux-ytaf kernel: Base memory trampoline at [ffff880000097000] 97000 size 24576
Feb 14 19:40:48 linux-ytaf kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
Feb 14 19:40:48 linux-ytaf kernel:  [mem 0x00000000-0x000fffff] page 4k
Feb 14 19:40:48 linux-ytaf kernel: BRK [0x0e21a000, 0x0e21afff] PGTABLE
Feb 14 19:40:48 linux-ytaf kernel: BRK [0x0e21b000, 0x0e21bfff] PGTABLE
Feb 14 19:40:48 linux-ytaf kernel: BRK [0x0e21c000, 0x0e21cfff] PGTABLE
Feb 14 19:40:48 linux-ytaf kernel: init_memory_mapping: [mem 0x21ee00000-0x21effffff]
Feb 14 19:40:48 linux-ytaf kernel:  [mem 0x21ee00000-0x21effffff] page 2M
Feb 14 19:40:48 linux-ytaf kernel: BRK [0x0e21d000, 0x0e21dfff] PGTABLE
Feb 14 19:40:48 linux-ytaf kernel: init_memory_mapping: [mem 0x200000000-0x21edfffff]
Feb 14 19:40:48 linux-ytaf kernel:  [mem 0x200000000-0x21edfffff] page 2M
Feb 14 19:40:48 linux-ytaf kernel: init_memory_mapping: [mem 0x1e0000000-0x1ffffffff]
Feb 14 19:40:48 linux-ytaf kernel:  [mem 0x1e0000000-0x1ffffffff] page 2M
Feb 14 19:40:48 linux-ytaf kernel: BRK [0x0e21e000, 0x0e21efff] PGTABLE
Feb 14 19:40:48 linux-ytaf kernel: init_memory_mapping: [mem 0x00100000-0xdeb8efff]
Feb 14 19:40:48 linux-ytaf kernel:  [mem 0x00100000-0x001fffff] page 4k
Feb 14 19:40:48 linux-ytaf kernel:  [mem 0x00200000-0xde9fffff] page 2M
Feb 14 19:40:48 linux-ytaf kernel:  [mem 0xdea00000-0xdeb8efff] page 4k
Feb 14 19:40:48 linux-ytaf kernel: init_memory_mapping: [mem 0xdf407000-0xdf7fffff]
Feb 14 19:40:48 linux-ytaf kernel:  [mem 0xdf407000-0xdf5fffff] page 4k
Feb 14 19:40:48 linux-ytaf kernel:  [mem 0xdf600000-0xdf7fffff] page 2M
Feb 14 19:40:48 linux-ytaf kernel: BRK [0x0e21f000, 0x0e21ffff] PGTABLE
Feb 14 19:40:48 linux-ytaf kernel: init_memory_mapping: [mem 0x100000000-0x1dfffffff]
Feb 14 19:40:48 linux-ytaf kernel:  [mem 0x100000000-0x1dfffffff] page 2M
Feb 14 19:40:48 linux-ytaf kernel: RAMDISK: [mem 0x00457000-0x00ffafff]
Feb 14 19:40:48 linux-ytaf kernel: ACPI: Early table checksum verification disabled
Feb 14 19:40:48 linux-ytaf kernel: ACPI: RSDP 0x00000000DF384000 000024 (v02 ALASKA)
Feb 14 19:40:48 linux-ytaf kernel: ACPI: XSDT 0x00000000DF384078 000064 (v01 ALASKA A M I    01072009 AMI  00010013)
Feb 14 19:40:48 linux-ytaf kernel: ACPI: FACP 0x00000000DF38FC78 0000F4 (v04 ALASKA A M I    01072009 AMI  00010013)
Feb 14 19:40:48 linux-ytaf kernel: ACPI: DSDT 0x00000000DF384170 00BB02 (v02 ALASKA A M I    00000015 INTL 20051117)
Feb 14 19:40:48 linux-ytaf kernel: ACPI: FACS 0x00000000DF3BDF80 000040
Feb 14 19:40:48 linux-ytaf kernel: ACPI: APIC 0x00000000DF38FD70 000092 (v03 ALASKA A M I    01072009 AMI  00010013)
Feb 14 19:40:48 linux-ytaf kernel: ACPI: MCFG 0x00000000DF38FE08 00003C (v01 ALASKA A M I    01072009 MSFT 00000097)
Feb 14 19:40:48 linux-ytaf kernel: ACPI: HPET 0x00000000DF38FE48 000038 (v01 ALASKA A M I    01072009 AMI. 00000005)
Feb 14 19:40:48 linux-ytaf kernel: ACPI: SSDT 0x00000000DF38FE80 00036D (v01 SataRe SataTabl 00001000 INTL 20091112)
Feb 14 19:40:48 linux-ytaf kernel: ACPI: SSDT 0x00000000DF3901F0 0009AA (v01 PmRef  Cpu0Ist  00003000 INTL 20051117)
Feb 14 19:40:48 linux-ytaf kernel: ACPI: SSDT 0x00000000DF390BA0 000A92 (v01 PmRef  CpuPm    00003000 INTL 20051117)
Feb 14 19:40:48 linux-ytaf kernel: ACPI: BGRT 0x00000000DF391690 000038 (v00 ALASKA A M I    01072009 AMI  00010013)
Feb 14 19:40:48 linux-ytaf kernel: ACPI: Local APIC address 0xfee00000
Feb 14 19:40:48 linux-ytaf kernel: No NUMA configuration found
Feb 14 19:40:48 linux-ytaf kernel: Faking a node at [mem 0x0000000000000000-0x000000021effffff]
Feb 14 19:40:48 linux-ytaf kernel: NODE_DATA(0) allocated [mem 0x21efe5000-0x21eff8fff]
Feb 14 19:40:48 linux-ytaf kernel:  [ffffea0000000000-ffffea00087fffff] PMD -> [ffff880216600000-ffff88021e5fffff] on node 0
Feb 14 19:40:48 linux-ytaf kernel: Zone ranges:
Feb 14 19:40:48 linux-ytaf kernel:   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
Feb 14 19:40:48 linux-ytaf kernel:   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
Feb 14 19:40:48 linux-ytaf kernel:   Normal   [mem 0x0000000100000000-0x000000021effffff]
Feb 14 19:40:48 linux-ytaf kernel: Movable zone start for each node
Feb 14 19:40:48 linux-ytaf kernel: Early memory node ranges
Feb 14 19:40:48 linux-ytaf kernel:   node   0: [mem 0x0000000000001000-0x000000000009efff]
Feb 14 19:40:48 linux-ytaf kernel:   node   0: [mem 0x0000000000100000-0x00000000deb8efff]
Feb 14 19:40:48 linux-ytaf kernel:   node   0: [mem 0x00000000df407000-0x00000000df7fffff]
Feb 14 19:40:48 linux-ytaf kernel:   node   0: [mem 0x0000000100000000-0x000000021effffff]
Feb 14 19:40:48 linux-ytaf kernel: Initmem setup node 0 [mem 0x0000000000001000-0x000000021effffff]
Feb 14 19:40:48 linux-ytaf kernel: On node 0 totalpages: 2088742
Feb 14 19:40:48 linux-ytaf kernel:   DMA zone: 64 pages used for memmap
Feb 14 19:40:48 linux-ytaf kernel:   DMA zone: 3021 pages reserved
Feb 14 19:40:48 linux-ytaf kernel:   DMA zone: 3998 pages, LIFO batch:0
Feb 14 19:40:48 linux-ytaf kernel:   DMA32 zone: 14207 pages used for memmap
Feb 14 19:40:48 linux-ytaf kernel:   DMA32 zone: 909192 pages, LIFO batch:31
Feb 14 19:40:48 linux-ytaf kernel:   Normal zone: 18368 pages used for memmap
Feb 14 19:40:48 linux-ytaf kernel:   Normal zone: 1175552 pages, LIFO batch:31
Feb 14 19:40:48 linux-ytaf kernel: tboot: non-0 tboot_addr but it is not of type E820_RESERVED
Feb 14 19:40:48 linux-ytaf kernel: ACPI: PM-Timer IO Port: 0x408
Feb 14 19:40:48 linux-ytaf kernel: ACPI: Local APIC address 0xfee00000
Feb 14 19:40:48 linux-ytaf kernel: ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
Feb 14 19:40:48 linux-ytaf kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
Feb 14 19:40:48 linux-ytaf kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Feb 14 19:40:48 linux-ytaf kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Feb 14 19:40:48 linux-ytaf kernel: ACPI: IRQ0 used by override.
Feb 14 19:40:48 linux-ytaf kernel: ACPI: IRQ9 used by override.
Feb 14 19:40:48 linux-ytaf kernel: Using ACPI (MADT) for SMP configuration information
Feb 14 19:40:48 linux-ytaf kernel: ACPI: HPET id: 0x8086a701 base: 0xfed00000
Feb 14 19:40:48 linux-ytaf kernel: smpboot: Allowing 8 CPUs, 0 hotplug CPUs
Feb 14 19:40:48 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
Feb 14 19:40:48 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Feb 14 19:40:48 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000fffff]
Feb 14 19:40:48 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c2f1000-0x0c2f1fff]
Feb 14 19:40:48 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c2f4000-0x0c2f4fff]
Feb 14 19:40:48 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c81c000-0x0c81cfff]
Feb 14 19:40:48 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c82b000-0x0c82bfff]
Feb 14 19:40:48 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c82c000-0x0c82cfff]
Feb 14 19:40:48 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c83b000-0x0c83bfff]
Feb 14 19:40:48 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xdeb8f000-0xdedf1fff]
Feb 14 19:40:48 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xdedf2000-0xdee79fff]
Feb 14 19:40:48 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xdee7a000-0xdf13efff]
Feb 14 19:40:48 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xdf13f000-0xdf383fff]
Feb 14 19:40:48 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xdf384000-0xdf391fff]
Feb 14 19:40:48 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xdf392000-0xdf3befff]
Feb 14 19:40:48 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xdf3bf000-0xdf3c3fff]
Feb 14 19:40:48 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xdf3c4000-0xdf406fff]
Feb 14 19:40:48 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xdf800000-0xf7ffffff]
Feb 14 19:40:48 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
Feb 14 19:40:48 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfc000000-0xfebfffff]
Feb 14 19:40:48 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
Feb 14 19:40:48 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfec01000-0xfecfffff]
Feb 14 19:40:48 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed00000-0xfed03fff]
Feb 14 19:40:48 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed04000-0xfed1bfff]
Feb 14 19:40:48 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Feb 14 19:40:48 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed20000-0xfedfffff]
Feb 14 19:40:48 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
Feb 14 19:40:48 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfee01000-0xfeffffff]
Feb 14 19:40:48 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Feb 14 19:40:48 linux-ytaf kernel: e820: [mem 0xdf800000-0xf7ffffff] available for PCI devices
Feb 14 19:40:48 linux-ytaf kernel: Booting paravirtualized kernel on bare hardware
Feb 14 19:40:48 linux-ytaf kernel: clocksource refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
Feb 14 19:40:48 linux-ytaf kernel: setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:8 nr_node_ids:1
Feb 14 19:40:48 linux-ytaf kernel: PERCPU: Embedded 33 pages/cpu @ffff88021ec00000 s97368 r8192 d29608 u262144
Feb 14 19:40:48 linux-ytaf kernel: pcpu-alloc: s97368 r8192 d29608 u262144 alloc=1*2097152
Feb 14 19:40:48 linux-ytaf kernel: pcpu-alloc: [0] 0 1 2 3 4 5 6 7 
Feb 14 19:40:48 linux-ytaf kernel: Built 1 zonelists in Node order, mobility grouping on.  Total pages: 2053082
Feb 14 19:40:48 linux-ytaf kernel: Policy zone: Normal
Feb 14 19:40:48 linux-ytaf kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.1.15-8-default root=UUID=21024970-7a27-4114-8525-d8dd026f23b6 ro resume=/dev/sdb2 splash=silent quiet showopts
Feb 14 19:40:48 linux-ytaf kernel: log_buf_len individual max cpu contribution: 32768 bytes
Feb 14 19:40:48 linux-ytaf kernel: log_buf_len total cpu_extra contributions: 229376 bytes
Feb 14 19:40:48 linux-ytaf kernel: log_buf_len min size: 262144 bytes
Feb 14 19:40:48 linux-ytaf kernel: log_buf_len: 524288 bytes
Feb 14 19:40:48 linux-ytaf kernel: early log buf free: 247532(94%)
Feb 14 19:40:48 linux-ytaf kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
Feb 14 19:40:48 linux-ytaf kernel: xsave: enabled xstate_bv 0x7, cntxt size 0x340 using standard form
Feb 14 19:40:48 linux-ytaf kernel: AGP: Checking aperture...
Feb 14 19:40:48 linux-ytaf kernel: AGP: No AGP bridge found
Feb 14 19:40:48 linux-ytaf kernel: Memory: 7935492K/8354968K available (6547K kernel code, 1084K rwdata, 4848K rodata, 1560K init, 1516K bss, 419476K reserved, 0K cma-reserved)
Feb 14 19:40:48 linux-ytaf kernel: Preemptible hierarchical RCU implementation.
Feb 14 19:40:48 linux-ytaf kernel:         RCU dyntick-idle grace-period acceleration is enabled.
Feb 14 19:40:48 linux-ytaf kernel:         RCU restricting CPUs from NR_CPUS=512 to nr_cpu_ids=8.
Feb 14 19:40:48 linux-ytaf kernel: RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
Feb 14 19:40:48 linux-ytaf kernel: NR_IRQS:33024 nr_irqs:488 16
Feb 14 19:40:48 linux-ytaf kernel:         Offload RCU callbacks from all CPUs
Feb 14 19:40:48 linux-ytaf kernel:         Offload RCU callbacks from CPUs: 0-7.
Feb 14 19:40:48 linux-ytaf kernel: Console: colour dummy device 80x25
Feb 14 19:40:48 linux-ytaf kernel: console [tty0] enabled
Feb 14 19:40:48 linux-ytaf kernel: clocksource hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484882848 ns
Feb 14 19:40:48 linux-ytaf kernel: hpet clockevent registered
Feb 14 19:40:48 linux-ytaf kernel: tsc: Fast TSC calibration using PIT
Feb 14 19:40:48 linux-ytaf kernel: tsc: Detected 3411.023 MHz processor
Feb 14 19:40:48 linux-ytaf kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 6822.04 BogoMIPS (lpj=13644092)
Feb 14 19:40:48 linux-ytaf kernel: pid_max: default: 32768 minimum: 301
Feb 14 19:40:48 linux-ytaf kernel: ACPI: Core revision 20150410
Feb 14 19:40:48 linux-ytaf kernel: ACPI: All ACPI Tables successfully acquired
Feb 14 19:40:48 linux-ytaf kernel: Security Framework initialized
Feb 14 19:40:48 linux-ytaf kernel: AppArmor: AppArmor initialized
Feb 14 19:40:48 linux-ytaf kernel: Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
Feb 14 19:40:48 linux-ytaf kernel: Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
Feb 14 19:40:48 linux-ytaf kernel: Mount-cache hash table entries: 16384 (order: 5, 131072 bytes)
Feb 14 19:40:48 linux-ytaf kernel: Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes)
Feb 14 19:40:48 linux-ytaf kernel: Initializing cgroup subsys blkio
Feb 14 19:40:48 linux-ytaf kernel: Initializing cgroup subsys memory
Feb 14 19:40:48 linux-ytaf kernel: Initializing cgroup subsys devices
Feb 14 19:40:48 linux-ytaf kernel: Initializing cgroup subsys freezer
Feb 14 19:40:48 linux-ytaf kernel: Initializing cgroup subsys net_cls
Feb 14 19:40:48 linux-ytaf kernel: Initializing cgroup subsys perf_event
Feb 14 19:40:48 linux-ytaf kernel: Initializing cgroup subsys net_prio
Feb 14 19:40:48 linux-ytaf kernel: Initializing cgroup subsys hugetlb
Feb 14 19:40:48 linux-ytaf kernel: CPU: Physical Processor ID: 0
Feb 14 19:40:48 linux-ytaf kernel: CPU: Processor Core ID: 0
Feb 14 19:40:48 linux-ytaf kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Feb 14 19:40:48 linux-ytaf kernel: ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Feb 14 19:40:48 linux-ytaf kernel: mce: CPU supports 9 MCE banks
Feb 14 19:40:48 linux-ytaf kernel: CPU0: Thermal monitoring enabled (TM1)
Feb 14 19:40:48 linux-ytaf kernel: process: using mwait in idle threads
Feb 14 19:40:48 linux-ytaf kernel: Last level iTLB entries: 4KB 512, 2MB 8, 4MB 8
Feb 14 19:40:48 linux-ytaf kernel: Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32, 1GB 0
Feb 14 19:40:48 linux-ytaf kernel: Freeing SMP alternatives memory: 24K (ffffffff82097000 - ffffffff8209d000)
Feb 14 19:40:48 linux-ytaf kernel: ftrace: allocating 25000 entries in 98 pages
Feb 14 19:40:48 linux-ytaf kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Feb 14 19:40:48 linux-ytaf kernel: TSC deadline timer enabled
Feb 14 19:40:48 linux-ytaf kernel: smpboot: CPU0: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz (fam: 06, model: 2a, stepping: 07)
Feb 14 19:40:48 linux-ytaf kernel: Performance Events: PEBS fmt1+, 16-deep LBR, SandyBridge events, full-width counters, Intel PMU driver.
Feb 14 19:40:48 linux-ytaf kernel: ... version:                3
Feb 14 19:40:48 linux-ytaf kernel: ... bit width:              48
Feb 14 19:40:48 linux-ytaf kernel: ... generic registers:      4
Feb 14 19:40:48 linux-ytaf kernel: ... value mask:             0000ffffffffffff
Feb 14 19:40:48 linux-ytaf kernel: ... max period:             0000ffffffffffff
Feb 14 19:40:48 linux-ytaf kernel: ... fixed-purpose events:   3
Feb 14 19:40:48 linux-ytaf kernel: ... event mask:             000000070000000f
Feb 14 19:40:48 linux-ytaf kernel: x86: Booting SMP configuration:
Feb 14 19:40:48 linux-ytaf kernel: .... node  #0, CPUs:      #1
Feb 14 19:40:48 linux-ytaf kernel: microcode: CPU1 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 19:40:48 linux-ytaf kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Feb 14 19:40:48 linux-ytaf kernel:  #2
Feb 14 19:40:48 linux-ytaf kernel: microcode: CPU2 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 19:40:48 linux-ytaf kernel:  #3
Feb 14 19:40:48 linux-ytaf kernel: microcode: CPU3 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 19:40:48 linux-ytaf kernel:  #4 #5 #6 #7
Feb 14 19:40:48 linux-ytaf kernel: x86: Booted up 1 node, 8 CPUs
Feb 14 19:40:48 linux-ytaf kernel: smpboot: Total of 8 processors activated (54576.36 BogoMIPS)
Feb 14 19:40:48 linux-ytaf kernel: devtmpfs: initialized
Feb 14 19:40:48 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xdedf2000-0xdee79fff] (557056 bytes)
Feb 14 19:40:48 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xdf13f000-0xdf383fff] (2379776 bytes)
Feb 14 19:40:48 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xdf392000-0xdf3befff] (184320 bytes)
Feb 14 19:40:48 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xdf3c4000-0xdf406fff] (274432 bytes)
Feb 14 19:40:48 linux-ytaf kernel: clocksource jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
Feb 14 19:40:48 linux-ytaf kernel: pinctrl core: initialized pinctrl subsystem
Feb 14 19:40:48 linux-ytaf kernel: RTC time: 19:40:44, date: 02/14/16
Feb 14 19:40:48 linux-ytaf kernel: NET: Registered protocol family 16
Feb 14 19:40:48 linux-ytaf kernel: cpuidle: using governor ladder
Feb 14 19:40:48 linux-ytaf kernel: cpuidle: using governor menu
Feb 14 19:40:48 linux-ytaf kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
Feb 14 19:40:48 linux-ytaf kernel: ACPI: bus type PCI registered
Feb 14 19:40:48 linux-ytaf kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Feb 14 19:40:48 linux-ytaf kernel: PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
Feb 14 19:40:48 linux-ytaf kernel: PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
Feb 14 19:40:48 linux-ytaf kernel: PCI: Using configuration type 1 for base access
Feb 14 19:40:48 linux-ytaf kernel: perf_event_intel: PMU erratum BJ122, BV98, HSD29 worked around, HT is on
Feb 14 19:40:48 linux-ytaf kernel: ACPI: Added _OSI(Module Device)
Feb 14 19:40:48 linux-ytaf kernel: ACPI: Added _OSI(Processor Device)
Feb 14 19:40:48 linux-ytaf kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
Feb 14 19:40:48 linux-ytaf kernel: ACPI: Added _OSI(Processor Aggregator Device)
Feb 14 19:40:48 linux-ytaf kernel: ACPI: Executed 1 blocks of module-level executable AML code
Feb 14 19:40:48 linux-ytaf kernel: ACPI: Dynamic OEM Table Load:
Feb 14 19:40:48 linux-ytaf kernel: ACPI: SSDT 0xFFFF880214FC9000 00083B (v01 PmRef  Cpu0Cst  00003001 INTL 20051117)
Feb 14 19:40:48 linux-ytaf kernel: ACPI: Dynamic OEM Table Load:
Feb 14 19:40:48 linux-ytaf kernel: ACPI: SSDT 0xFFFF880214FC3400 000303 (v01 PmRef  ApIst    00003000 INTL 20051117)
Feb 14 19:40:48 linux-ytaf kernel: ACPI: Dynamic OEM Table Load:
Feb 14 19:40:48 linux-ytaf kernel: ACPI: SSDT 0xFFFF880214F74600 000119 (v01 PmRef  ApCst    00003000 INTL 20051117)
Feb 14 19:40:48 linux-ytaf kernel: ACPI : EC: EC started
Feb 14 19:40:48 linux-ytaf kernel: ACPI: Interpreter enabled
Feb 14 19:40:48 linux-ytaf kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20150410/hwxface-580)
Feb 14 19:40:48 linux-ytaf kernel: ACPI: (supports S0 S1 S3 S4 S5)
Feb 14 19:40:48 linux-ytaf kernel: ACPI: Using IOAPIC for interrupt routing
Feb 14 19:40:48 linux-ytaf kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Feb 14 19:40:48 linux-ytaf kernel: ACPI: Power Resource [FN00] (off)
Feb 14 19:40:48 linux-ytaf kernel: ACPI: Power Resource [FN01] (off)
Feb 14 19:40:48 linux-ytaf kernel: ACPI: Power Resource [FN02] (off)
Feb 14 19:40:48 linux-ytaf kernel: ACPI: Power Resource [FN03] (off)
Feb 14 19:40:48 linux-ytaf kernel: ACPI: Power Resource [FN04] (off)
Feb 14 19:40:48 linux-ytaf kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
Feb 14 19:40:48 linux-ytaf kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Feb 14 19:40:48 linux-ytaf kernel: \_SB_.PCI0:_OSC invalid UUID
Feb 14 19:40:48 linux-ytaf kernel: _OSC request data:1 1f 0 
Feb 14 19:40:48 linux-ytaf kernel: acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
Feb 14 19:40:48 linux-ytaf kernel: PCI host bridge to bus 0000:00
Feb 14 19:40:48 linux-ytaf kernel: pci_bus 0000:00: root bus resource [bus 00-3e]
Feb 14 19:40:48 linux-ytaf kernel: pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
Feb 14 19:40:48 linux-ytaf kernel: pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
Feb 14 19:40:48 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
Feb 14 19:40:48 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff window]
Feb 14 19:40:48 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff window]
Feb 14 19:40:48 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff window]
Feb 14 19:40:48 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0xe0000000-0xfeafffff window]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:00.0: [8086:0100] type 00 class 0x060000
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:01.0: [8086:0101] type 01 class 0x060400
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:01.0: System wakeup disabled by ACPI
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:01.1: [8086:0105] type 01 class 0x060400
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:01.1: PME# supported from D0 D3hot D3cold
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:01.1: System wakeup disabled by ACPI
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:16.0: [8086:1c3a] type 00 class 0x078000
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:16.0: reg 0x10: [mem 0xf742c000-0xf742c00f 64bit]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:19.0: [8086:1503] type 00 class 0x020000
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:19.0: reg 0x10: [mem 0xf7400000-0xf741ffff]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:19.0: reg 0x14: [mem 0xf7429000-0xf7429fff]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:19.0: reg 0x18: [io  0xf040-0xf05f]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:19.0: PME# supported from D0 D3hot D3cold
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:19.0: System wakeup disabled by ACPI
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1a.0: [8086:1c2d] type 00 class 0x0c0320
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1a.0: reg 0x10: [mem 0xf7428000-0xf74283ff]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1a.0: System wakeup disabled by ACPI
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1b.0: [8086:1c20] type 00 class 0x040300
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1b.0: reg 0x10: [mem 0xf7420000-0xf7423fff 64bit]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1b.0: System wakeup disabled by ACPI
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.0: [8086:1c10] type 01 class 0x060400
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.0: System wakeup disabled by ACPI
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.4: [8086:1c18] type 01 class 0x060400
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.4: System wakeup disabled by ACPI
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.5: [8086:1c1a] type 01 class 0x060400
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.5: System wakeup disabled by ACPI
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.6: [8086:1c1c] type 01 class 0x060400
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.6: PME# supported from D0 D3hot D3cold
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.6: System wakeup disabled by ACPI
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1d.0: [8086:1c26] type 00 class 0x0c0320
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1d.0: reg 0x10: [mem 0xf7427000-0xf74273ff]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1d.0: System wakeup disabled by ACPI
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1f.0: [8086:1c44] type 00 class 0x060100
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1f.2: [8086:1c02] type 00 class 0x010601
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x10: [io  0xf090-0xf097]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x14: [io  0xf080-0xf083]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x18: [io  0xf070-0xf077]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x1c: [io  0xf060-0xf063]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x20: [io  0xf020-0xf03f]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x24: [mem 0xf7426000-0xf74267ff]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1f.2: PME# supported from D3hot
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1f.3: [8086:1c22] type 00 class 0x0c0500
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1f.3: reg 0x10: [mem 0xf7425000-0xf74250ff 64bit]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1f.3: reg 0x20: [io  0x0580-0x059f]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:02:00.0: [10de:1183] type 00 class 0x030000
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:02:00.0: reg 0x10: [mem 0xf6000000-0xf6ffffff]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:02:00.0: reg 0x14: [mem 0xe8000000-0xefffffff 64bit pref]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:02:00.0: reg 0x1c: [mem 0xf0000000-0xf1ffffff 64bit pref]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:02:00.0: reg 0x24: [io  0xe000-0xe07f]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:02:00.0: reg 0x30: [mem 0xf7000000-0xf707ffff pref]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:02:00.1: [10de:0e0a] type 00 class 0x040300
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:02:00.1: reg 0x10: [mem 0xf7080000-0xf7083fff]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:01.1: PCI bridge to [bus 02]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [io  0xe000-0xefff]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xf6000000-0xf70fffff]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xe8000000-0xf1ffffff 64bit pref]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.0: PCI bridge to [bus 03]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:04:00.0: [1b21:1042] type 00 class 0x0c0330
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:04:00.0: reg 0x10: [mem 0xf7300000-0xf7307fff 64bit]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:04:00.0: PME# supported from D3hot D3cold
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:04:00.0: System wakeup disabled by ACPI
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.4: PCI bridge to [bus 04]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.4:   bridge window [mem 0xf7300000-0xf73fffff]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:05:00.0: [1b21:1042] type 00 class 0x0c0330
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:05:00.0: reg 0x10: [mem 0xf7200000-0xf7207fff 64bit]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:05:00.0: PME# supported from D3hot D3cold
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:05:00.0: System wakeup disabled by ACPI
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.5: PCI bridge to [bus 05]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.5:   bridge window [mem 0xf7200000-0xf72fffff]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:06:00.0: [197b:2362] type 00 class 0x010185
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:06:00.0: reg 0x10: [io  0xd040-0xd047]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:06:00.0: reg 0x14: [io  0xd030-0xd033]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:06:00.0: reg 0x18: [io  0xd020-0xd027]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:06:00.0: reg 0x1c: [io  0xd010-0xd013]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:06:00.0: reg 0x20: [io  0xd000-0xd00f]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:06:00.0: reg 0x24: [mem 0xf7110000-0xf71101ff]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:06:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:06:00.0: PME# supported from D3hot
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:06:00.0: System wakeup disabled by ACPI
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.6: PCI bridge to [bus 06]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [io  0xd000-0xdfff]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [mem 0xf7100000-0xf71fffff]
Feb 14 19:40:48 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15)
Feb 14 19:40:48 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *10 11 12 14 15)
Feb 14 19:40:48 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Feb 14 19:40:48 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs *3 4 5 6 10 11 12 14 15)
Feb 14 19:40:48 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 *4 5 6 10 11 12 14 15)
Feb 14 19:40:48 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
Feb 14 19:40:48 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 *11 12 14 15)
Feb 14 19:40:48 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 *10 11 12 14 15)
Feb 14 19:40:48 linux-ytaf kernel: ACPI: Enabled 6 GPEs in block 00 to 3F
Feb 14 19:40:48 linux-ytaf kernel: ACPI : EC: GPE = 0x18, I/O: command/status = 0x66, data = 0x62
Feb 14 19:40:48 linux-ytaf kernel: vgaarb: setting as boot device: PCI:0000:02:00.0
Feb 14 19:40:48 linux-ytaf kernel: vgaarb: device added: PCI:0000:02:00.0,decodes=io+mem,owns=io+mem,locks=none
Feb 14 19:40:48 linux-ytaf kernel: vgaarb: loaded
Feb 14 19:40:48 linux-ytaf kernel: vgaarb: bridge control possible 0000:02:00.0
Feb 14 19:40:48 linux-ytaf kernel: SCSI subsystem initialized
Feb 14 19:40:48 linux-ytaf kernel: libata version 3.00 loaded.
Feb 14 19:40:48 linux-ytaf kernel: PCI: Using ACPI for IRQ routing
Feb 14 19:40:48 linux-ytaf kernel: PCI: pci_cache_line_size set to 64 bytes
Feb 14 19:40:48 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0009f000-0x0009ffff]
Feb 14 19:40:48 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c2f1018-0x0fffffff]
Feb 14 19:40:48 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c81c018-0x0fffffff]
Feb 14 19:40:48 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c82c018-0x0fffffff]
Feb 14 19:40:48 linux-ytaf kernel: e820: reserve RAM buffer [mem 0xdeb8f000-0xdfffffff]
Feb 14 19:40:48 linux-ytaf kernel: e820: reserve RAM buffer [mem 0xdf800000-0xdfffffff]
Feb 14 19:40:48 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x21f000000-0x21fffffff]
Feb 14 19:40:48 linux-ytaf kernel: NetLabel: Initializing
Feb 14 19:40:48 linux-ytaf kernel: NetLabel:  domain hash size = 128
Feb 14 19:40:48 linux-ytaf kernel: NetLabel:  protocols = UNLABELED CIPSOv4
Feb 14 19:40:48 linux-ytaf kernel: NetLabel:  unlabeled traffic allowed by default
Feb 14 19:40:48 linux-ytaf kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Feb 14 19:40:48 linux-ytaf kernel: hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Feb 14 19:40:48 linux-ytaf kernel: Switched to clocksource hpet
Feb 14 19:40:48 linux-ytaf kernel: AppArmor: AppArmor Filesystem Enabled
Feb 14 19:40:48 linux-ytaf kernel: pnp: PnP ACPI init
Feb 14 19:40:48 linux-ytaf kernel: system 00:00: [mem 0xfed40000-0xfed44fff] has been reserved
Feb 14 19:40:48 linux-ytaf kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
Feb 14 19:40:48 linux-ytaf kernel: system 00:01: [io  0x0680-0x069f] has been reserved
Feb 14 19:40:48 linux-ytaf kernel: system 00:01: [io  0x0200-0x020f] has been reserved
Feb 14 19:40:48 linux-ytaf kernel: system 00:01: [io  0xffff] has been reserved
Feb 14 19:40:48 linux-ytaf kernel: system 00:01: [io  0xffff] has been reserved
Feb 14 19:40:48 linux-ytaf kernel: system 00:01: [io  0x0400-0x0453] could not be reserved
Feb 14 19:40:48 linux-ytaf kernel: system 00:01: [io  0x0458-0x047f] has been reserved
Feb 14 19:40:48 linux-ytaf kernel: system 00:01: [io  0x0500-0x057f] has been reserved
Feb 14 19:40:48 linux-ytaf kernel: system 00:01: [io  0x164e-0x164f] has been reserved
Feb 14 19:40:48 linux-ytaf kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 19:40:48 linux-ytaf kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Feb 14 19:40:48 linux-ytaf kernel: system 00:03: [io  0x0454-0x0457] has been reserved
Feb 14 19:40:48 linux-ytaf kernel: system 00:03: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
Feb 14 19:40:48 linux-ytaf kernel: system 00:04: [io  0x0290-0x029f] has been reserved
Feb 14 19:40:48 linux-ytaf kernel: system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 19:40:48 linux-ytaf kernel: system 00:05: [io  0x04d0-0x04d1] has been reserved
Feb 14 19:40:48 linux-ytaf kernel: system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 19:40:48 linux-ytaf kernel: system 00:06: [mem 0xfed1c000-0xfed1ffff] has been reserved
Feb 14 19:40:48 linux-ytaf kernel: system 00:06: [mem 0xfed10000-0xfed17fff] has been reserved
Feb 14 19:40:48 linux-ytaf kernel: system 00:06: [mem 0xfed18000-0xfed18fff] has been reserved
Feb 14 19:40:48 linux-ytaf kernel: system 00:06: [mem 0xfed19000-0xfed19fff] has been reserved
Feb 14 19:40:48 linux-ytaf kernel: system 00:06: [mem 0xf8000000-0xfbffffff] has been reserved
Feb 14 19:40:48 linux-ytaf kernel: system 00:06: [mem 0xfed20000-0xfed3ffff] has been reserved
Feb 14 19:40:48 linux-ytaf kernel: system 00:06: [mem 0xfed90000-0xfed93fff] has been reserved
Feb 14 19:40:48 linux-ytaf kernel: system 00:06: [mem 0xfed45000-0xfed8ffff] has been reserved
Feb 14 19:40:48 linux-ytaf kernel: system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Feb 14 19:40:48 linux-ytaf kernel: system 00:06: [mem 0xfee00000-0xfeefffff] could not be reserved
Feb 14 19:40:48 linux-ytaf kernel: system 00:06: [mem 0xe0000000-0xe0000fff] has been reserved
Feb 14 19:40:48 linux-ytaf kernel: system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 19:40:48 linux-ytaf kernel: pnp: PnP ACPI: found 7 devices
Feb 14 19:40:48 linux-ytaf kernel: clocksource acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.0: bridge window [io  0x1000-0x0fff] to [bus 03] add_size 1000
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 03] add_size 200000 add_align 100000
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff] to [bus 03] add_size 200000 add_align 100000
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.0: res[14]=[mem 0x00100000-0x000fffff] res_to_dev_res add_size 200000 min_align 100000
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.0: res[14]=[mem 0x00100000-0x002fffff] res_to_dev_res add_size 200000 min_align 100000
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x000fffff 64bit pref] res_to_dev_res add_size 200000 min_align 100000
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x002fffff 64bit pref] res_to_dev_res add_size 200000 min_align 100000
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.0: res[13]=[io  0x1000-0x0fff] res_to_dev_res add_size 1000 min_align 1000
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.0: res[13]=[io  0x1000-0x1fff] res_to_dev_res add_size 1000 min_align 1000
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.0: BAR 14: assigned [mem 0xe0100000-0xe02fffff]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.0: BAR 15: assigned [mem 0xe0300000-0xe04fffff 64bit pref]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.0: BAR 13: assigned [io  0x2000-0x2fff]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:01.1: PCI bridge to [bus 02]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [io  0xe000-0xefff]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xf6000000-0xf70fffff]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xe8000000-0xf1ffffff 64bit pref]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.0: PCI bridge to [bus 03]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.0:   bridge window [io  0x2000-0x2fff]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.0:   bridge window [mem 0xe0100000-0xe02fffff]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.0:   bridge window [mem 0xe0300000-0xe04fffff 64bit pref]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.4: PCI bridge to [bus 04]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.4:   bridge window [mem 0xf7300000-0xf73fffff]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.5: PCI bridge to [bus 05]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.5:   bridge window [mem 0xf7200000-0xf72fffff]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:06:00.0: BAR 6: assigned [mem 0xf7100000-0xf710ffff pref]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.6: PCI bridge to [bus 06]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [io  0xd000-0xdfff]
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [mem 0xf7100000-0xf71fffff]
Feb 14 19:40:48 linux-ytaf kernel: pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
Feb 14 19:40:48 linux-ytaf kernel: pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
Feb 14 19:40:48 linux-ytaf kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
Feb 14 19:40:48 linux-ytaf kernel: pci_bus 0000:00: resource 7 [mem 0x000d4000-0x000d7fff window]
Feb 14 19:40:48 linux-ytaf kernel: pci_bus 0000:00: resource 8 [mem 0x000d8000-0x000dbfff window]
Feb 14 19:40:48 linux-ytaf kernel: pci_bus 0000:00: resource 9 [mem 0x000dc000-0x000dffff window]
Feb 14 19:40:48 linux-ytaf kernel: pci_bus 0000:00: resource 10 [mem 0xe0000000-0xfeafffff window]
Feb 14 19:40:48 linux-ytaf kernel: pci_bus 0000:02: resource 0 [io  0xe000-0xefff]
Feb 14 19:40:48 linux-ytaf kernel: pci_bus 0000:02: resource 1 [mem 0xf6000000-0xf70fffff]
Feb 14 19:40:48 linux-ytaf kernel: pci_bus 0000:02: resource 2 [mem 0xe8000000-0xf1ffffff 64bit pref]
Feb 14 19:40:48 linux-ytaf kernel: pci_bus 0000:03: resource 0 [io  0x2000-0x2fff]
Feb 14 19:40:48 linux-ytaf kernel: pci_bus 0000:03: resource 1 [mem 0xe0100000-0xe02fffff]
Feb 14 19:40:48 linux-ytaf kernel: pci_bus 0000:03: resource 2 [mem 0xe0300000-0xe04fffff 64bit pref]
Feb 14 19:40:48 linux-ytaf kernel: pci_bus 0000:04: resource 1 [mem 0xf7300000-0xf73fffff]
Feb 14 19:40:48 linux-ytaf kernel: pci_bus 0000:05: resource 1 [mem 0xf7200000-0xf72fffff]
Feb 14 19:40:48 linux-ytaf kernel: pci_bus 0000:06: resource 0 [io  0xd000-0xdfff]
Feb 14 19:40:48 linux-ytaf kernel: pci_bus 0000:06: resource 1 [mem 0xf7100000-0xf71fffff]
Feb 14 19:40:48 linux-ytaf kernel: NET: Registered protocol family 2
Feb 14 19:40:48 linux-ytaf kernel: TCP established hash table entries: 65536 (order: 7, 524288 bytes)
Feb 14 19:40:48 linux-ytaf kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Feb 14 19:40:48 linux-ytaf kernel: TCP: Hash tables configured (established 65536 bind 65536)
Feb 14 19:40:48 linux-ytaf kernel: UDP hash table entries: 4096 (order: 5, 131072 bytes)
Feb 14 19:40:48 linux-ytaf kernel: UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
Feb 14 19:40:48 linux-ytaf kernel: NET: Registered protocol family 1
Feb 14 19:40:48 linux-ytaf kernel: pci 0000:02:00.0: Video device with shadowed ROM
Feb 14 19:40:48 linux-ytaf kernel: PCI: CLS 64 bytes, default 64
Feb 14 19:40:48 linux-ytaf kernel: Unpacking initramfs...
Feb 14 19:40:48 linux-ytaf kernel: Freeing initrd memory: 11920K (ffff880000457000 - ffff880000ffb000)
Feb 14 19:40:48 linux-ytaf kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Feb 14 19:40:48 linux-ytaf kernel: software IO TLB [mem 0xdab8f000-0xdeb8f000] (64MB) mapped at [ffff8800dab8f000-ffff8800deb8efff]
Feb 14 19:40:48 linux-ytaf kernel: RAPL PMU detected, API unit is 2^-32 Joules, 3 fixed counters 163840 ms ovfl timer
Feb 14 19:40:48 linux-ytaf kernel: hw unit of domain pp0-core 2^-16 Joules
Feb 14 19:40:48 linux-ytaf kernel: hw unit of domain package 2^-16 Joules
Feb 14 19:40:48 linux-ytaf kernel: hw unit of domain pp1-gpu 2^-16 Joules
Feb 14 19:40:48 linux-ytaf kernel: microcode: CPU0 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 19:40:48 linux-ytaf kernel: microcode: CPU1 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 19:40:48 linux-ytaf kernel: microcode: CPU2 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 19:40:48 linux-ytaf kernel: microcode: CPU3 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 19:40:48 linux-ytaf kernel: microcode: CPU4 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 19:40:48 linux-ytaf kernel: microcode: CPU5 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 19:40:48 linux-ytaf kernel: microcode: CPU6 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 19:40:48 linux-ytaf kernel: microcode: CPU7 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 19:40:48 linux-ytaf kernel: microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Feb 14 19:40:48 linux-ytaf kernel: Scanning for low memory corruption every 60 seconds
Feb 14 19:40:48 linux-ytaf kernel: futex hash table entries: 2048 (order: 5, 131072 bytes)
Feb 14 19:40:48 linux-ytaf kernel: audit: initializing netlink subsys (disabled)
Feb 14 19:40:48 linux-ytaf kernel: audit: type=2000 audit(1455478845.284:1): initialized
Feb 14 19:40:48 linux-ytaf kernel: HugeTLB registered 2 MB page size, pre-allocated 0 pages
Feb 14 19:40:48 linux-ytaf kernel: zpool: loaded
Feb 14 19:40:48 linux-ytaf kernel: zbud: loaded
Feb 14 19:40:48 linux-ytaf kernel: VFS: Disk quotas dquot_6.6.0
Feb 14 19:40:48 linux-ytaf kernel: VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Feb 14 19:40:48 linux-ytaf kernel: Key type big_key registered
Feb 14 19:40:48 linux-ytaf kernel: Key type asymmetric registered
Feb 14 19:40:48 linux-ytaf kernel: Asymmetric key parser 'x509' registered
Feb 14 19:40:48 linux-ytaf kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Feb 14 19:40:48 linux-ytaf kernel: io scheduler noop registered
Feb 14 19:40:48 linux-ytaf kernel: io scheduler deadline registered
Feb 14 19:40:48 linux-ytaf kernel: io scheduler cfq registered (default)
Feb 14 19:40:48 linux-ytaf kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Feb 14 19:40:48 linux-ytaf kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Feb 14 19:40:48 linux-ytaf kernel: efifb: probing for efifb
Feb 14 19:40:48 linux-ytaf kernel: efifb: framebuffer at 0xf1000000, mapped to 0xffffc90001000000, using 1876k, total 1875k
Feb 14 19:40:48 linux-ytaf kernel: efifb: mode is 800x600x32, linelength=3200, pages=1
Feb 14 19:40:48 linux-ytaf kernel: efifb: scrolling: redraw
Feb 14 19:40:48 linux-ytaf kernel: efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Feb 14 19:40:48 linux-ytaf kernel: Console: switching to colour frame buffer device 100x37
Feb 14 19:40:48 linux-ytaf kernel: fb0: EFI VGA frame buffer device
Feb 14 19:40:48 linux-ytaf kernel: intel_idle: MWAIT substates: 0x1120
Feb 14 19:40:48 linux-ytaf kernel: intel_idle: v0.4 model 0x2A
Feb 14 19:40:48 linux-ytaf kernel: intel_idle: lapic_timer_reliable_states 0xffffffff
Feb 14 19:40:48 linux-ytaf kernel: GHES: HEST is not enabled!
Feb 14 19:40:48 linux-ytaf kernel: Serial: 8250/16550 driver, 32 ports, IRQ sharing disabled
Feb 14 19:40:48 linux-ytaf kernel: Non-volatile memory driver v1.3
Feb 14 19:40:48 linux-ytaf kernel: Linux agpgart interface v0.103
Feb 14 19:40:48 linux-ytaf kernel: ahci 0000:00:1f.2: version 3.0
Feb 14 19:40:48 linux-ytaf kernel: ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x7 impl SATA mode
Feb 14 19:40:48 linux-ytaf kernel: ahci 0000:00:1f.2: flags: 64bit ncq led clo pio slum part ems apst 
Feb 14 19:40:48 linux-ytaf kernel: scsi host0: ahci
Feb 14 19:40:48 linux-ytaf kernel: scsi host1: ahci
Feb 14 19:40:48 linux-ytaf kernel: scsi host2: ahci
Feb 14 19:40:48 linux-ytaf kernel: scsi host3: ahci
Feb 14 19:40:48 linux-ytaf kernel: scsi host4: ahci
Feb 14 19:40:48 linux-ytaf kernel: scsi host5: ahci
Feb 14 19:40:48 linux-ytaf kernel: ata1: SATA max UDMA/133 abar m2048@0xf7426000 port 0xf7426100 irq 26
Feb 14 19:40:48 linux-ytaf kernel: ata2: SATA max UDMA/133 abar m2048@0xf7426000 port 0xf7426180 irq 26
Feb 14 19:40:48 linux-ytaf kernel: ata3: SATA max UDMA/133 abar m2048@0xf7426000 port 0xf7426200 irq 26
Feb 14 19:40:48 linux-ytaf kernel: ata4: DUMMY
Feb 14 19:40:48 linux-ytaf kernel: ata5: DUMMY
Feb 14 19:40:48 linux-ytaf kernel: ata6: DUMMY
Feb 14 19:40:48 linux-ytaf kernel: ahci 0000:06:00.0: AHCI 0001.0100 32 slots 2 ports 3 Gbps 0x3 impl SATA mode
Feb 14 19:40:48 linux-ytaf kernel: ahci 0000:06:00.0: flags: 64bit ncq pm led clo pmp pio slum part 
Feb 14 19:40:48 linux-ytaf kernel: scsi host6: ahci
Feb 14 19:40:48 linux-ytaf kernel: scsi host7: ahci
Feb 14 19:40:48 linux-ytaf kernel: ata7: SATA max UDMA/133 abar m512@0xf7110000 port 0xf7110100 irq 18
Feb 14 19:40:48 linux-ytaf kernel: ata8: SATA max UDMA/133 abar m512@0xf7110000 port 0xf7110180 irq 18
Feb 14 19:40:48 linux-ytaf kernel: i8042: PNP: No PS/2 controller found. Probing ports directly.
Feb 14 19:40:48 linux-ytaf kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Feb 14 19:40:48 linux-ytaf kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Feb 14 19:40:48 linux-ytaf kernel: mousedev: PS/2 mouse device common for all mice
Feb 14 19:40:48 linux-ytaf kernel: rtc_cmos 00:02: RTC can wake from S4
Feb 14 19:40:48 linux-ytaf kernel: rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Feb 14 19:40:48 linux-ytaf kernel: rtc_cmos 00:02: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
Feb 14 19:40:48 linux-ytaf kernel: Intel P-state driver initializing.
Feb 14 19:40:48 linux-ytaf kernel: ledtrig-cpu: registered to indicate activity on CPUs
Feb 14 19:40:48 linux-ytaf kernel: EFI Variables Facility v0.08 2004-May-17
Feb 14 19:40:48 linux-ytaf kernel: hidraw: raw HID events driver (C) Jiri Kosina
Feb 14 19:40:48 linux-ytaf kernel: NET: Registered protocol family 10
Feb 14 19:40:48 linux-ytaf kernel: registered taskstats version 1
Feb 14 19:40:48 linux-ytaf kernel: Key type encrypted registered
Feb 14 19:40:48 linux-ytaf kernel: AppArmor: AppArmor sha1 policy hashing enabled
Feb 14 19:40:48 linux-ytaf kernel:   Magic number: 4:176:698
Feb 14 19:40:48 linux-ytaf kernel: rtc_cmos 00:02: setting system clock to 2016-02-14 19:40:46 UTC (1455478846)
Feb 14 19:40:48 linux-ytaf kernel: PM: Checking hibernation image partition /dev/sdb2
Feb 14 19:40:48 linux-ytaf kernel: ata7: SATA link down (SStatus 0 SControl 300)
Feb 14 19:40:48 linux-ytaf kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 14 19:40:48 linux-ytaf kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 14 19:40:48 linux-ytaf kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Feb 14 19:40:48 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 19:40:48 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff8802160b7dd8), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 19:40:48 linux-ytaf kernel: ata2.00: ATA-8: TOSHIBA HDWD110, MS2OA8J0, max UDMA/133
Feb 14 19:40:48 linux-ytaf kernel: ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Feb 14 19:40:48 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 19:40:48 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff8802160b7e50), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 19:40:48 linux-ytaf kernel: ata1.00: ATA-9: SAMSUNG SSD 830 Series, CXM03B1Q, max UDMA/133
Feb 14 19:40:48 linux-ytaf kernel: ata1.00: 500118192 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Feb 14 19:40:48 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 19:40:48 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff8802160b7d60), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 19:40:48 linux-ytaf kernel: ata3.00: ATAPI: TSSTcorp CDDVDW SH-S223C, SB05, max MWDMA2
Feb 14 19:40:48 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 19:40:48 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff8802160b7e50), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 19:40:48 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 19:40:48 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff8802160b7dd8), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 19:40:48 linux-ytaf kernel: ata1.00: configured for UDMA/133
Feb 14 19:40:48 linux-ytaf kernel: ata2.00: configured for UDMA/133
Feb 14 19:40:48 linux-ytaf kernel: scsi 0:0:0:0: Direct-Access     ATA      SAMSUNG SSD 830  3B1Q PQ: 0 ANSI: 5
Feb 14 19:40:48 linux-ytaf kernel: sd 0:0:0:0: [sda] 500118192 512-byte logical blocks: (256 GB/238 GiB)
Feb 14 19:40:48 linux-ytaf kernel: scsi 1:0:0:0: Direct-Access     ATA      TOSHIBA HDWD110  A8J0 PQ: 0 ANSI: 5
Feb 14 19:40:48 linux-ytaf kernel: sd 0:0:0:0: [sda] Write Protect is off
Feb 14 19:40:48 linux-ytaf kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 14 19:40:48 linux-ytaf kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 14 19:40:48 linux-ytaf kernel: sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
Feb 14 19:40:48 linux-ytaf kernel: sd 1:0:0:0: [sdb] 4096-byte physical blocks
Feb 14 19:40:48 linux-ytaf kernel: sd 1:0:0:0: [sdb] Write Protect is off
Feb 14 19:40:48 linux-ytaf kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Feb 14 19:40:48 linux-ytaf kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 14 19:40:48 linux-ytaf kernel: ata8: SATA link down (SStatus 0 SControl 300)
Feb 14 19:40:48 linux-ytaf kernel:  sda: sda1 sda2 sda3 sda4
Feb 14 19:40:48 linux-ytaf kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Feb 14 19:40:48 linux-ytaf kernel:  sdb: sdb1 sdb2 sdb3 sdb4
Feb 14 19:40:48 linux-ytaf kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
Feb 14 19:40:48 linux-ytaf kernel: tsc: Refined TSC clocksource calibration: 3411.128 MHz
Feb 14 19:40:48 linux-ytaf kernel: clocksource tsc: mask: 0xffffffffffffffff max_cycles: 0x312b5ecadef, max_idle_ns: 440795307361 ns
Feb 14 19:40:48 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 19:40:48 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff8802160b7d60), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 19:40:48 linux-ytaf kernel: ata3.00: configured for PIO4
Feb 14 19:40:48 linux-ytaf kernel: scsi 2:0:0:0: CD-ROM            TSSTcorp CDDVDW SH-S223C  SB05 PQ: 0 ANSI: 5
Feb 14 19:40:48 linux-ytaf kernel: PM: Hibernation image partition 8:18 present
Feb 14 19:40:48 linux-ytaf kernel: PM: Looking for hibernation image.
Feb 14 19:40:48 linux-ytaf kernel: Switched to clocksource tsc
Feb 14 19:40:48 linux-ytaf kernel: PM: Image not found (code -22)
Feb 14 19:40:48 linux-ytaf kernel: PM: Hibernation image not present or could not be loaded.
Feb 14 19:40:48 linux-ytaf kernel: Freeing unused kernel memory: 1560K (ffffffff81f11000 - ffffffff82097000)
Feb 14 19:40:48 linux-ytaf kernel: Write protecting the kernel read-only data: 14336k
Feb 14 19:40:48 linux-ytaf kernel: Freeing unused kernel memory: 1632K (ffff88000d668000 - ffff88000d800000)
Feb 14 19:40:48 linux-ytaf kernel: Freeing unused kernel memory: 1296K (ffff88000dcbc000 - ffff88000de00000)
Feb 14 19:40:48 linux-ytaf systemd[1]: RTC configured in localtime, applying delta of 60 minutes to system time.
Feb 14 19:40:48 linux-ytaf kernel: random: systemd urandom read with 22 bits of entropy available
Feb 14 19:40:48 linux-ytaf kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Feb 14 19:40:48 linux-ytaf kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0
Feb 14 19:40:48 linux-ytaf kernel: scsi 2:0:0:0: Attached scsi generic sg2 type 5
Feb 14 19:40:48 linux-ytaf systemd-journal[187]: Journal started
Feb 14 19:40:48 linux-ytaf dracut-cmdline[181]: dracut-42.1 dracut-037-68.1
Feb 14 19:40:48 linux-ytaf systemd-udevd[252]: Network interface NamePolicy= disabled on kernel commandline, ignoring.
Feb 14 19:40:48 linux-ytaf kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3
Feb 14 19:40:48 linux-ytaf kernel: ACPI: Power Button [PWRB]
Feb 14 19:40:48 linux-ytaf kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
Feb 14 19:40:48 linux-ytaf kernel: ACPI: Power Button [PWRF]
Feb 14 19:40:48 linux-ytaf kernel: wmi: Mapper loaded
Feb 14 19:40:48 linux-ytaf kernel: ACPI: bus type USB registered
Feb 14 19:40:48 linux-ytaf kernel: usbcore: registered new interface driver usbfs
Feb 14 19:40:48 linux-ytaf kernel: usbcore: registered new interface driver hub
Feb 14 19:40:48 linux-ytaf kernel: usbcore: registered new device driver usb
Feb 14 19:40:48 linux-ytaf kernel: [drm] Initialized drm 1.1.0 20060810
Feb 14 19:40:48 linux-ytaf kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Feb 14 19:40:48 linux-ytaf kernel: ehci-pci: EHCI PCI platform driver
Feb 14 19:40:48 linux-ytaf kernel: ehci-pci 0000:00:1a.0: EHCI Host Controller
Feb 14 19:40:48 linux-ytaf kernel: ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Feb 14 19:40:48 linux-ytaf kernel: ehci-pci 0000:00:1a.0: debug port 2
Feb 14 19:40:48 linux-ytaf kernel: ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Feb 14 19:40:48 linux-ytaf kernel: ehci-pci 0000:00:1a.0: irq 16, io mem 0xf7428000
Feb 14 19:40:48 linux-ytaf kernel: MXM: GUID detected in BIOS
Feb 14 19:40:48 linux-ytaf kernel: checking generic (f1000000 1d5000) vs hw (e8000000 8000000)
Feb 14 19:40:48 linux-ytaf kernel: checking generic (f1000000 1d5000) vs hw (f0000000 2000000)
Feb 14 19:40:48 linux-ytaf kernel: fb: switching to nouveaufb from EFI VGA
Feb 14 19:40:48 linux-ytaf kernel: Console: switching to colour dummy device 80x25
Feb 14 19:40:48 linux-ytaf kernel: nouveau  [  DEVICE][0000:02:00.0] BOOT0  : 0x0e4030a2
Feb 14 19:40:48 linux-ytaf kernel: nouveau  [  DEVICE][0000:02:00.0] Chipset: GK104 (NVE4)
Feb 14 19:40:48 linux-ytaf kernel: nouveau  [  DEVICE][0000:02:00.0] Family : NVE0
Feb 14 19:40:48 linux-ytaf kernel: sr 2:0:0:0: [sr0] scsi3-mmc drive: 52x/52x writer dvd-ram cd/rw xa/form2 cdda tray
Feb 14 19:40:48 linux-ytaf kernel: cdrom: Uniform CD-ROM driver Revision: 3.20
Feb 14 19:40:48 linux-ytaf kernel: sr 2:0:0:0: Attached scsi CD-ROM sr0
Feb 14 19:40:48 linux-ytaf kernel: ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Feb 14 19:40:48 linux-ytaf kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 19:40:48 linux-ytaf kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 19:40:48 linux-ytaf kernel: usb usb1: Product: EHCI Host Controller
Feb 14 19:40:48 linux-ytaf kernel: usb usb1: Manufacturer: Linux 4.1.15-8-default ehci_hcd
Feb 14 19:40:48 linux-ytaf kernel: usb usb1: SerialNumber: 0000:00:1a.0
Feb 14 19:40:48 linux-ytaf kernel: hub 1-0:1.0: USB hub found
Feb 14 19:40:48 linux-ytaf kernel: hub 1-0:1.0: 2 ports detected
Feb 14 19:40:48 linux-ytaf kernel: xhci_hcd 0000:04:00.0: xHCI Host Controller
Feb 14 19:40:48 linux-ytaf kernel: xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 2
Feb 14 19:40:48 linux-ytaf kernel: xhci_hcd 0000:04:00.0: hcc params 0x0200f180 hci version 0x96 quirks 0x00080000
Feb 14 19:40:48 linux-ytaf kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 19:40:48 linux-ytaf kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 19:40:48 linux-ytaf kernel: usb usb2: Product: xHCI Host Controller
Feb 14 19:40:48 linux-ytaf kernel: usb usb2: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 19:40:48 linux-ytaf kernel: usb usb2: SerialNumber: 0000:04:00.0
Feb 14 19:40:48 linux-ytaf kernel: hub 2-0:1.0: USB hub found
Feb 14 19:40:48 linux-ytaf kernel: hub 2-0:1.0: 2 ports detected
Feb 14 19:40:48 linux-ytaf kernel: xhci_hcd 0000:04:00.0: xHCI Host Controller
Feb 14 19:40:48 linux-ytaf kernel: xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 3
Feb 14 19:40:48 linux-ytaf kernel: ehci-pci 0000:00:1d.0: EHCI Host Controller
Feb 14 19:40:48 linux-ytaf kernel: ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 4
Feb 14 19:40:48 linux-ytaf kernel: usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
Feb 14 19:40:48 linux-ytaf kernel: ehci-pci 0000:00:1d.0: debug port 2
Feb 14 19:40:48 linux-ytaf kernel: usb usb3: New USB device found, idVendor=1d6b, idProduct=0003
Feb 14 19:40:48 linux-ytaf kernel: usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 19:40:48 linux-ytaf kernel: usb usb3: Product: xHCI Host Controller
Feb 14 19:40:48 linux-ytaf kernel: usb usb3: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 19:40:48 linux-ytaf kernel: usb usb3: SerialNumber: 0000:04:00.0
Feb 14 19:40:48 linux-ytaf kernel: hub 3-0:1.0: USB hub found
Feb 14 19:40:48 linux-ytaf kernel: hub 3-0:1.0: 2 ports detected
Feb 14 19:40:48 linux-ytaf kernel: ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Feb 14 19:40:48 linux-ytaf kernel: ehci-pci 0000:00:1d.0: irq 23, io mem 0xf7427000
Feb 14 19:40:48 linux-ytaf kernel: ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Feb 14 19:40:48 linux-ytaf kernel: usb usb4: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 19:40:48 linux-ytaf kernel: usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 19:40:48 linux-ytaf kernel: usb usb4: Product: EHCI Host Controller
Feb 14 19:40:48 linux-ytaf kernel: usb usb4: Manufacturer: Linux 4.1.15-8-default ehci_hcd
Feb 14 19:40:48 linux-ytaf kernel: usb usb4: SerialNumber: 0000:00:1d.0
Feb 14 19:40:48 linux-ytaf kernel: hub 4-0:1.0: USB hub found
Feb 14 19:40:48 linux-ytaf kernel: hub 4-0:1.0: 2 ports detected
Feb 14 19:40:48 linux-ytaf kernel: xhci_hcd 0000:05:00.0: xHCI Host Controller
Feb 14 19:40:48 linux-ytaf kernel: xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 5
Feb 14 19:40:48 linux-ytaf kernel: xhci_hcd 0000:05:00.0: hcc params 0x0200f180 hci version 0x96 quirks 0x00080000
Feb 14 19:40:48 linux-ytaf kernel: usb usb5: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 19:40:48 linux-ytaf kernel: usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 19:40:48 linux-ytaf kernel: usb usb5: Product: xHCI Host Controller
Feb 14 19:40:48 linux-ytaf kernel: usb usb5: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 19:40:48 linux-ytaf kernel: usb usb5: SerialNumber: 0000:05:00.0
Feb 14 19:40:48 linux-ytaf kernel: hub 5-0:1.0: USB hub found
Feb 14 19:40:48 linux-ytaf kernel: hub 5-0:1.0: 2 ports detected
Feb 14 19:40:48 linux-ytaf kernel: xhci_hcd 0000:05:00.0: xHCI Host Controller
Feb 14 19:40:48 linux-ytaf kernel: xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 6
Feb 14 19:40:48 linux-ytaf kernel: usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
Feb 14 19:40:48 linux-ytaf kernel: usb usb6: New USB device found, idVendor=1d6b, idProduct=0003
Feb 14 19:40:48 linux-ytaf kernel: usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 19:40:48 linux-ytaf kernel: usb usb6: Product: xHCI Host Controller
Feb 14 19:40:48 linux-ytaf kernel: usb usb6: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 19:40:48 linux-ytaf kernel: usb usb6: SerialNumber: 0000:05:00.0
Feb 14 19:40:48 linux-ytaf kernel: hub 6-0:1.0: USB hub found
Feb 14 19:40:48 linux-ytaf kernel: hub 6-0:1.0: 2 ports detected
Feb 14 19:40:48 linux-ytaf kernel: raid6: sse2x1   gen()  7890 MB/s
Feb 14 19:40:48 linux-ytaf kernel: nouveau  [   VBIOS][0000:02:00.0] using image from PROM
Feb 14 19:40:48 linux-ytaf kernel: nouveau  [   VBIOS][0000:02:00.0] BIT signature found
Feb 14 19:40:48 linux-ytaf kernel: nouveau  [   VBIOS][0000:02:00.0] version 80.04.4b.00.07
Feb 14 19:40:48 linux-ytaf kernel: nouveau  [     PMC][0000:02:00.0] MSI interrupts enabled
Feb 14 19:40:48 linux-ytaf kernel: nouveau  [     PFB][0000:02:00.0] RAM type: GDDR5
Feb 14 19:40:48 linux-ytaf kernel: nouveau  [     PFB][0000:02:00.0] RAM size: 2048 MiB
Feb 14 19:40:48 linux-ytaf kernel: nouveau  [     PFB][0000:02:00.0]    ZCOMP: 0 tags
Feb 14 19:40:48 linux-ytaf kernel: nouveau  [    VOLT][0000:02:00.0] GPU voltage: 987500uv
Feb 14 19:40:48 linux-ytaf kernel: nouveau  [  PTHERM][0000:02:00.0] FAN control: PWM
Feb 14 19:40:48 linux-ytaf kernel: nouveau  [  PTHERM][0000:02:00.0] fan management: automatic
Feb 14 19:40:48 linux-ytaf kernel: nouveau  [  PTHERM][0000:02:00.0] internal sensor: yes
Feb 14 19:40:48 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 07: core 324 MHz memory 648 MHz 
Feb 14 19:40:48 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 0a: core 324-862 MHz memory 1620 MHz 
Feb 14 19:40:48 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 0d: core 540-1202 MHz memory 6008 MHz 
Feb 14 19:40:48 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] 0f: core 540-1202 MHz memory 6008 MHz 
Feb 14 19:40:48 linux-ytaf kernel: nouveau  [     CLK][0000:02:00.0] --: core 324 MHz memory 648 MHz 
Feb 14 19:40:48 linux-ytaf kernel: raid6: sse2x1   xor()  9015 MB/s
Feb 14 19:40:48 linux-ytaf kernel: usb 1-1: new high-speed USB device number 2 using ehci-pci
Feb 14 19:40:48 linux-ytaf kernel: raid6: sse2x2   gen() 14106 MB/s
Feb 14 19:40:48 linux-ytaf kernel: [TTM] Zone  kernel: Available graphics memory: 4070810 kiB
Feb 14 19:40:48 linux-ytaf kernel: [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
Feb 14 19:40:48 linux-ytaf kernel: [TTM] Initializing pool allocator
Feb 14 19:40:48 linux-ytaf kernel: [TTM] Initializing DMA pool allocator
Feb 14 19:40:48 linux-ytaf kernel: nouveau  [     DRM] VRAM: 2048 MiB
Feb 14 19:40:48 linux-ytaf kernel: nouveau  [     DRM] GART: 1048576 MiB
Feb 14 19:40:48 linux-ytaf kernel: nouveau  [     DRM] TMDS table version 2.0
Feb 14 19:40:48 linux-ytaf kernel: nouveau  [     DRM] DCB version 4.0
Feb 14 19:40:48 linux-ytaf kernel: nouveau  [     DRM] DCB outp 00: 01000f02 00020030
Feb 14 19:40:48 linux-ytaf kernel: nouveau  [     DRM] DCB outp 01: 02000f00 00000000
Feb 14 19:40:48 linux-ytaf kernel: nouveau  [     DRM] DCB outp 02: 08011f82 00020030
Feb 14 19:40:48 linux-ytaf kernel: nouveau  [     DRM] DCB outp 03: 02822f62 0f420010
Feb 14 19:40:48 linux-ytaf kernel: nouveau  [     DRM] DCB outp 05: 04833fb6 0f420010
Feb 14 19:40:48 linux-ytaf kernel: nouveau  [     DRM] DCB outp 06: 04033f72 00020010
Feb 14 19:40:48 linux-ytaf kernel: nouveau  [     DRM] DCB conn 00: 00001030
Feb 14 19:40:48 linux-ytaf kernel: nouveau  [     DRM] DCB conn 01: 00020131
Feb 14 19:40:48 linux-ytaf kernel: nouveau  [     DRM] DCB conn 02: 00002261
Feb 14 19:40:48 linux-ytaf kernel: nouveau  [     DRM] DCB conn 03: 00010346
Feb 14 19:40:48 linux-ytaf kernel: nouveau  [     DRM] DCB conn 04: 00000460
Feb 14 19:40:48 linux-ytaf kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Feb 14 19:40:48 linux-ytaf kernel: [drm] Driver supports precise vblank timestamp query.
Feb 14 19:40:48 linux-ytaf kernel: nouveau  [     DRM] MM: using COPY for buffer copies
Feb 14 19:40:48 linux-ytaf kernel: raid6: sse2x2   xor()  7032 MB/s
Feb 14 19:40:48 linux-ytaf kernel: usb 4-1: new high-speed USB device number 2 using ehci-pci
Feb 14 19:40:49 linux-ytaf kernel: usb 1-1: New USB device found, idVendor=8087, idProduct=0024
Feb 14 19:40:49 linux-ytaf kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb 14 19:40:49 linux-ytaf kernel: hub 1-1:1.0: USB hub found
Feb 14 19:40:49 linux-ytaf kernel: hub 1-1:1.0: 6 ports detected
Feb 14 19:40:49 linux-ytaf kernel: raid6: sse2x4   gen() 14791 MB/s
Feb 14 19:40:49 linux-ytaf kernel: usb 5-2: new high-speed USB device number 2 using xhci_hcd
Feb 14 19:40:49 linux-ytaf kernel: raid6: sse2x4   xor() 12107 MB/s
Feb 14 19:40:49 linux-ytaf kernel: raid6: using algorithm sse2x4 gen() 14791 MB/s
Feb 14 19:40:49 linux-ytaf kernel: raid6: .... xor() 12107 MB/s, rmw enabled
Feb 14 19:40:49 linux-ytaf kernel: raid6: using ssse3x2 recovery algorithm
Feb 14 19:40:49 linux-ytaf kernel: xor: automatically using best checksumming function:
Feb 14 19:40:49 linux-ytaf kernel: usb 4-1: New USB device found, idVendor=8087, idProduct=0024
Feb 14 19:40:49 linux-ytaf kernel: usb 4-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb 14 19:40:49 linux-ytaf kernel: hub 4-1:1.0: USB hub found
Feb 14 19:40:49 linux-ytaf kernel: hub 4-1:1.0: 8 ports detected
Feb 14 19:40:49 linux-ytaf kernel:    avx       : 31206.000 MB/sec
Feb 14 19:40:49 linux-ytaf kernel: Btrfs loaded, assert=on
Feb 14 19:40:49 linux-ytaf kernel: BTRFS: device fsid 21024970-7a27-4114-8525-d8dd026f23b6 devid 1 transid 651 /dev/sdb3
Feb 14 19:40:49 linux-ytaf kernel: usb 5-2: New USB device found, idVendor=0930, idProduct=6545
Feb 14 19:40:49 linux-ytaf kernel: usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 14 19:40:49 linux-ytaf kernel: usb 5-2: Product: TransMemory
Feb 14 19:40:49 linux-ytaf kernel: usb 5-2: Manufacturer: TOSHIBA
Feb 14 19:40:49 linux-ytaf kernel: usb 5-2: SerialNumber: C89CDCBF6D59EF4140000065
Feb 14 19:40:49 linux-ytaf kernel: usb-storage 5-2:1.0: USB Mass Storage device detected
Feb 14 19:40:49 linux-ytaf kernel: scsi host8: usb-storage 5-2:1.0
Feb 14 19:40:49 linux-ytaf kernel: usbcore: registered new interface driver usb-storage
Feb 14 19:40:49 linux-ytaf kernel: usbcore: registered new interface driver uas
Feb 14 19:40:49 linux-ytaf kernel: nouveau  [     DRM] allocated 1920x1080 fb: 0x60000, bo ffff88000a8dc800
Feb 14 19:40:49 linux-ytaf kernel: fbcon: nouveaufb (fb0) is primary device
Feb 14 19:40:49 linux-ytaf kernel: usb 1-1.4: new full-speed USB device number 3 using ehci-pci
Feb 14 19:40:49 linux-ytaf kernel: usb 4-1.1: new full-speed USB device number 3 using ehci-pci
Feb 14 19:40:49 linux-ytaf kernel: usb 4-1.1: New USB device found, idVendor=1532, idProduct=0109
Feb 14 19:40:49 linux-ytaf kernel: usb 4-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 14 19:40:49 linux-ytaf kernel: usb 4-1.1: Product: Razer Lycosa
Feb 14 19:40:49 linux-ytaf kernel: usb 4-1.1: Manufacturer: Razer
Feb 14 19:40:49 linux-ytaf kernel: usbcore: registered new interface driver usbhid
Feb 14 19:40:49 linux-ytaf kernel: usbhid: USB HID core driver
Feb 14 19:40:49 linux-ytaf kernel: input: Razer Razer Lycosa as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1:1.0/0003:1532:0109.0001/input/input5
Feb 14 19:40:49 linux-ytaf kernel: usb 1-1.4: New USB device found, idVendor=06a3, idProduct=0ccb
Feb 14 19:40:49 linux-ytaf kernel: usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 14 19:40:49 linux-ytaf kernel: usb 1-1.4: Product: Cyborg R.A.T.7 Mouse
Feb 14 19:40:49 linux-ytaf kernel: usb 1-1.4: Manufacturer: Saitek
Feb 14 19:40:49 linux-ytaf kernel: hid-generic 0003:1532:0109.0001: input,hidraw0: USB HID v1.10 Keyboard [Razer Razer Lycosa] on usb-0000:00:1d.0-1.1/input0
Feb 14 19:40:49 linux-ytaf kernel: input: Razer Razer Lycosa as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1:1.1/0003:1532:0109.0002/input/input6
Feb 14 19:40:49 linux-ytaf kernel: hid-generic 0003:1532:0109.0002: input,hidraw1: USB HID v1.10 Device [Razer Razer Lycosa] on usb-0000:00:1d.0-1.1/input1
Feb 14 19:40:49 linux-ytaf kernel: Console: switching to colour frame buffer device 210x65
Feb 14 19:40:49 linux-ytaf kernel: nouveau 0000:02:00.0: fb0: nouveaufb frame buffer device
Feb 14 19:40:49 linux-ytaf kernel: nouveau 0000:02:00.0: registered panic notifier
Feb 14 19:40:49 linux-ytaf kernel: [drm] Initialized nouveau 1.2.2 20120801 for 0000:02:00.0 on minor 0
Feb 14 19:40:50 linux-ytaf kernel: scsi 8:0:0:0: Direct-Access     TOSHIBA  TransMemory      PMAP PQ: 0 ANSI: 6
Feb 14 19:40:50 linux-ytaf kernel: sd 8:0:0:0: Attached scsi generic sg3 type 0
Feb 14 19:40:50 linux-ytaf kernel: sd 8:0:0:0: [sdc] 30228480 512-byte logical blocks: (15.4 GB/14.4 GiB)
Feb 14 19:40:50 linux-ytaf kernel: sd 8:0:0:0: [sdc] Write Protect is off
Feb 14 19:40:50 linux-ytaf kernel: sd 8:0:0:0: [sdc] Mode Sense: 45 00 00 00
Feb 14 19:40:50 linux-ytaf kernel: sd 8:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Feb 14 19:40:50 linux-ytaf kernel:  sdc: sdc1
Feb 14 19:40:50 linux-ytaf kernel: sd 8:0:0:0: [sdc] Attached SCSI removable disk
Feb 14 19:40:50 linux-ytaf kernel: PM: Starting manual resume from disk
Feb 14 19:40:50 linux-ytaf kernel: PM: Hibernation image partition 8:18 present
Feb 14 19:40:50 linux-ytaf kernel: PM: Looking for hibernation image.
Feb 14 19:40:50 linux-ytaf kernel: PM: Image not found (code -22)
Feb 14 19:40:50 linux-ytaf kernel: PM: Hibernation image not present or could not be loaded.
Feb 14 19:40:50 linux-ytaf kernel: BTRFS info (device sdb3): disk space caching is enabled
Feb 14 19:40:50 linux-ytaf kernel: BTRFS: has skinny extents
Feb 14 19:40:50 linux-ytaf systemd-journal[187]: Journal stopped
Feb 14 19:40:52 linux-ytaf systemd-journal[473]: Runtime journal is using 8.0M (max allowed 397.5M, trying to leave 596.3M free of 3.8G available → current limit 397.5M).
Feb 14 19:40:52 linux-ytaf systemd-journal[473]: Runtime journal is using 8.0M (max allowed 397.5M, trying to leave 596.3M free of 3.8G available → current limit 397.5M).
Feb 14 19:40:52 linux-ytaf kernel: random: nonblocking pool is initialized
Feb 14 19:40:52 linux-ytaf systemd[1]: RTC configured in localtime, applying delta of 60 minutes to system time.
Feb 14 19:40:52 linux-ytaf systemd-journal[473]: Journal started
Feb 14 19:40:52 linux-ytaf systemd-udevd[492]: starting version 210
Feb 14 19:40:52 linux-ytaf systemd-udevd[492]: Network interface NamePolicy= disabled on kernel commandline, ignoring.
Feb 14 19:40:52 linux-ytaf kernel: BTRFS info (device sdb3): disk space caching is enabled
Feb 14 19:40:53 linux-ytaf kernel: thermal LNXTHERM:00: registered as thermal_zone0
Feb 14 19:40:53 linux-ytaf kernel: ACPI: Thermal Zone [TZ00] (28 C)
Feb 14 19:40:53 linux-ytaf kernel: thermal LNXTHERM:01: registered as thermal_zone1
Feb 14 19:40:53 linux-ytaf kernel: ACPI: Thermal Zone [TZ01] (30 C)
Feb 14 19:40:53 linux-ytaf kernel: input: PC Speaker as /devices/platform/pcspkr/input/input7
Feb 14 19:40:53 linux-ytaf kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Feb 14 19:40:53 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20150410/utaddress-254)
Feb 14 19:40:53 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 19:40:53 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150410/utaddress-254)
Feb 14 19:40:53 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150410/utaddress-254)
Feb 14 19:40:53 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 19:40:53 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150410/utaddress-254)
Feb 14 19:40:53 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150410/utaddress-254)
Feb 14 19:40:53 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 19:40:53 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150410/utaddress-254)
Feb 14 19:40:53 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150410/utaddress-254)
Feb 14 19:40:53 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 19:40:53 linux-ytaf kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
Feb 14 19:40:53 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000580-0x000000000000059F conflicts with OpRegion 0x0000000000000580-0x000000000000058F (\_SB_.PCI0.SBUS.SMBI) (20150410/utaddress-254)
Feb 14 19:40:53 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000580-0x000000000000059F conflicts with OpRegion 0x0000000000000580-0x000000000000059F (\_SB_.PCI0.SMB_.SMIO) (20150410/utaddress-254)
Feb 14 19:40:53 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 19:40:53 linux-ytaf kernel: iTCO_vendor_support: vendor-support=0
Feb 14 19:40:53 linux-ytaf kernel: iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
Feb 14 19:40:53 linux-ytaf kernel: iTCO_wdt: Found a Cougar Point TCO device (Version=2, TCOBASE=0x0460)
Feb 14 19:40:53 linux-ytaf kernel: iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
Feb 14 19:40:53 linux-ytaf kernel: pps_core: LinuxPPS API ver. 1 registered
Feb 14 19:40:53 linux-ytaf kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
Feb 14 19:40:53 linux-ytaf kernel: PTP clock support registered
Feb 14 19:40:53 linux-ytaf kernel: AVX version of gcm_enc/dec engaged.
Feb 14 19:40:53 linux-ytaf kernel: AES CTR mode by8 optimization enabled
Feb 14 19:40:53 linux-ytaf kernel: asus_wmi: ASUS WMI generic driver loaded
Feb 14 19:40:53 linux-ytaf kernel: asus_wmi: Initialization: 0x0
Feb 14 19:40:53 linux-ytaf kernel: asus_wmi: BIOS WMI version: 0.9
Feb 14 19:40:53 linux-ytaf kernel: asus_wmi: SFUN value: 0x0
Feb 14 19:40:53 linux-ytaf kernel: input: Eee PC WMI hotkeys as /devices/platform/eeepc-wmi/input/input8
Feb 14 19:40:53 linux-ytaf kernel: asus_wmi: Disabling ACPI video driver
Feb 14 19:40:53 linux-ytaf mtp-probe[596]: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4"
Feb 14 19:40:53 linux-ytaf mtp-probe[607]: checking bus 5, device 2: "/sys/devices/pci0000:00/0000:00:1c.5/0000:05:00.0/usb5/5-2"
Feb 14 19:40:53 linux-ytaf mtp-probe[595]: checking bus 4, device 3: "/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1"
Feb 14 19:40:53 linux-ytaf mtp-probe[596]: bus: 1, device: 3 was not an MTP device
Feb 14 19:40:53 linux-ytaf mtp-probe[607]: bus: 5, device: 2 was not an MTP device
Feb 14 19:40:53 linux-ytaf mtp-probe[595]: bus: 4, device: 3 was not an MTP device
Feb 14 19:40:53 linux-ytaf kernel: e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
Feb 14 19:40:53 linux-ytaf kernel: e1000e: Copyright(c) 1999 - 2014 Intel Corporation.
Feb 14 19:40:53 linux-ytaf kernel: e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
Feb 14 19:40:54 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: registered PHC clock
Feb 14 19:40:54 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) c8:60:00:09:38:76
Feb 14 19:40:54 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
Feb 14 19:40:54 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: FFFFFF-0FF
Feb 14 19:40:54 linux-ytaf kernel: input: Saitek Cyborg R.A.T.7 Mouse as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/0003:06A3:0CCB.0003/input/input9
Feb 14 19:40:54 linux-ytaf kernel: saitek 0003:06A3:0CCB.0003: input,hidraw2: USB HID v1.11 Mouse [Saitek Cyborg R.A.T.7 Mouse] on usb-0000:00:1a.0-1.4/input0
Feb 14 19:40:54 linux-ytaf kernel: snd_hda_intel 0000:00:1b.0: enabling device (0000 -> 0002)
Feb 14 19:40:54 linux-ytaf kernel: snd_hda_intel 0000:02:00.1: enabling device (0000 -> 0002)
Feb 14 19:40:54 linux-ytaf kernel: snd_hda_intel 0000:02:00.1: Disabling MSI
Feb 14 19:40:54 linux-ytaf kernel: snd_hda_intel 0000:02:00.1: Handle VGA-switcheroo audio client
Feb 14 19:40:54 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC889: line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line
Feb 14 19:40:54 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Feb 14 19:40:54 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
Feb 14 19:40:54 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
Feb 14 19:40:54 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    dig-out=0x11/0x1e
Feb 14 19:40:54 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    inputs:
Feb 14 19:40:54 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:      Front Mic=0x19
Feb 14 19:40:54 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:      Rear Mic=0x18
Feb 14 19:40:54 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:      Line=0x1a
Feb 14 19:40:54 linux-ytaf kernel: input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
Feb 14 19:40:54 linux-ytaf kernel: input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
Feb 14 19:40:54 linux-ytaf kernel: input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
Feb 14 19:40:54 linux-ytaf kernel: input: HDA Intel PCH Line Out Front as /devices/pci0000:00/0000:00:1b.0/sound/card0/input13
Feb 14 19:40:54 linux-ytaf kernel: input: HDA Intel PCH Line Out Surround as /devices/pci0000:00/0000:00:1b.0/sound/card0/input14
Feb 14 19:40:54 linux-ytaf kernel: input: HDA Intel PCH Line Out CLFE as /devices/pci0000:00/0000:00:1b.0/sound/card0/input15
Feb 14 19:40:54 linux-ytaf kernel: input: HDA Intel PCH Line Out Side as /devices/pci0000:00/0000:00:1b.0/sound/card0/input16
Feb 14 19:40:54 linux-ytaf systemd-fsck[687]: /sbin/fsck.xfs: XFS file system.
Feb 14 19:40:54 linux-ytaf kernel: Adding 2104316k swap on /dev/sdb2.  Priority:-1 extents:1 across:2104316k FS
Feb 14 19:40:54 linux-ytaf kernel: FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Feb 14 19:40:54 linux-ytaf kernel: SGI XFS with ACLs, security attributes, realtime, no debug enabled
Feb 14 19:40:54 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input17
Feb 14 19:40:54 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input18
Feb 14 19:40:54 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input19
Feb 14 19:40:54 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input20
Feb 14 19:40:54 linux-ytaf kernel: XFS (sdb4): Mounting V5 Filesystem
Feb 14 19:40:55 linux-ytaf kernel: XFS (sdb4): Starting recovery (logdev: internal)
Feb 14 19:40:55 linux-ytaf kernel: XFS (sdb4): Ending recovery (logdev: internal)
Feb 14 19:40:56 linux-ytaf systemd-journal[473]: Permanent journal is using 99.2M (max allowed 4.0G, trying to leave 4.0G free of 32.8G available → current limit 4.0G).
Feb 14 19:40:56 linux-ytaf systemd-journal[473]: Time spent on flushing to /var is 28.072ms for 980 entries.
Feb 14 19:40:57 linux-ytaf kernel: audit: type=1305 audit(1455475255.714:2): audit_pid=756 old=0 auid=4294967295 ses=4294967295 res=1
Feb 14 19:40:55 linux-ytaf auditd[756]: Started dispatcher: /sbin/audispd pid: 766
Feb 14 19:40:55 linux-ytaf audispd[766]: priority_boost_parser called with: 4
Feb 14 19:40:55 linux-ytaf audispd[766]: max_restarts_parser called with: 10
Feb 14 19:40:55 linux-ytaf audispd[766]: No plugins found, exiting
Feb 14 19:40:55 linux-ytaf auditd[756]: Init complete, auditd 2.3.6 listening for events (startup state enable)
Feb 14 19:40:56 linux-ytaf avahi-daemon[933]: Found user 'avahi' (UID 486) and group 'avahi' (GID 485).
Feb 14 19:40:56 linux-ytaf avahi-daemon[933]: Successfully dropped root privileges.
Feb 14 19:40:56 linux-ytaf avahi-daemon[933]: avahi-daemon 0.6.31 starting up.
Feb 14 19:40:56 linux-ytaf avahi-daemon[933]: Loading service file /etc/avahi/services/sftp-ssh.service.
Feb 14 19:40:56 linux-ytaf avahi-daemon[933]: Loading service file /etc/avahi/services/ssh.service.
Feb 14 19:40:56 linux-ytaf avahi-daemon[933]: Network interface enumeration completed.
Feb 14 19:40:57 linux-ytaf avahi-daemon[933]: Registering HINFO record with values 'X86_64'/'LINUX'.
Feb 14 19:40:57 linux-ytaf smartd[939]: smartd 6.2 2013-11-07 r3856 [x86_64-linux-4.1.15-8-default] (SUSE RPM)
Feb 14 19:40:57 linux-ytaf avahi-daemon[933]: Server startup complete. Host name is linux-ytaf.local. Local service cookie is 1285557709.
Feb 14 19:40:57 linux-ytaf smartd[939]: Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
Feb 14 19:40:57 linux-ytaf avahi-daemon[933]: Service "linux-ytaf" (/etc/avahi/services/ssh.service) successfully established.
Feb 14 19:40:57 linux-ytaf smartd[939]: Opened configuration file /etc/smartd.conf
Feb 14 19:40:57 linux-ytaf avahi-daemon[933]: Service "linux-ytaf" (/etc/avahi/services/sftp-ssh.service) successfully established.
Feb 14 19:40:57 linux-ytaf auditctl[757]: No rules
Feb 14 19:40:57 linux-ytaf auditctl[757]: AUDIT_STATUS: enabled=0 flag=1 pid=0 rate_limit=0 backlog_limit=320 lost=0 backlog=0
Feb 14 19:40:57 linux-ytaf boot.apparmor[770]: Starting AppArmor ..done
Feb 14 19:40:57 linux-ytaf dbus-daemon[932]: Unknown username "srvGeoClue" in message bus configuration file
Feb 14 19:40:57 linux-ytaf alsactl[943]: Found hardware: "HDA-Intel" "Realtek ALC889" "HDA:10ec0889,1043846b,00100004" "0x1043" "0x84dc"
Feb 14 19:40:57 linux-ytaf alsactl[943]: Hardware is initialized using a generic method
Feb 14 19:40:57 linux-ytaf alsactl[943]: /usr/sbin/alsactl: set_control:1325: failed to obtain info for control #31 (No such file or directory)
Feb 14 19:40:57 linux-ytaf alsactl[943]: /usr/sbin/alsactl: set_control:1325: failed to obtain info for control #32 (No such file or directory)
Feb 14 19:40:57 linux-ytaf alsactl[943]: /usr/sbin/alsactl: set_control:1325: failed to obtain info for control #33 (No such file or directory)
Feb 14 19:40:57 linux-ytaf alsactl[943]: /usr/sbin/alsactl: set_control:1325: failed to obtain info for control #34 (No such file or directory)
Feb 14 19:40:57 linux-ytaf alsactl[943]: /usr/sbin/alsactl: set_control:1325: failed to obtain info for control #55 (No such file or directory)
Feb 14 19:40:57 linux-ytaf alsactl[943]: /usr/sbin/alsactl: set_control:1325: failed to obtain info for control #60 (No such file or directory)
Feb 14 19:40:57 linux-ytaf alsactl[943]: /usr/sbin/alsactl: set_control:1325: failed to obtain info for control #61 (No such file or directory)
Feb 14 19:40:57 linux-ytaf display-manager[951]: /etc/vconsole.conf available
Feb 14 19:40:57 linux-ytaf display-manager[951]: KEYMAP: de-latin1-nodeadkeys
Feb 14 19:40:57 linux-ytaf display-manager[951]: Command: localectl set-keymap de-latin1-nodeadkeys
Feb 14 19:40:57 linux-ytaf display-manager[951]: I: Using systemd /usr/share/systemd/kbd-model-map mapping
Feb 14 19:40:57 linux-ytaf smartd[939]: Drive: DEVICESCAN, implied '-a' Directive on line 26 of file /etc/smartd.conf
Feb 14 19:40:57 linux-ytaf smartd[939]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
Feb 14 19:40:57 linux-ytaf smartd[939]: Device: /dev/sda, type changed from 'scsi' to 'sat'
Feb 14 19:40:57 linux-ytaf smartd[939]: Device: /dev/sda [SAT], opened
Feb 14 19:40:57 linux-ytaf smartd[939]: Device: /dev/sda [SAT], SAMSUNG SSD 830 Series, S/N:S0Z4NEAC906195, WWN:5-002538-043584d30, FW:CXM03B1Q, 256 GB
Feb 14 19:40:57 linux-ytaf smartd[939]: Device: /dev/sda [SAT], found in smartd database: Samsung based SSDs
Feb 14 19:40:57 linux-ytaf smartd[939]: Device: /dev/sda [SAT], can't monitor Current_Pending_Sector count - no Attribute 197
Feb 14 19:40:57 linux-ytaf smartd[939]: Device: /dev/sda [SAT], can't monitor Offline_Uncorrectable count - no Attribute 198
Feb 14 19:40:57 linux-ytaf smartd[939]: Device: /dev/sda [SAT], is SMART capable. Adding to "monitor" list.
Feb 14 19:40:57 linux-ytaf dbus[932]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service'
Feb 14 19:40:57 linux-ytaf smartd[939]: Device: /dev/sda [SAT], state read from /var/lib/smartmontools/smartd.SAMSUNG_SSD_830_Series-S0Z4NEAC906195.ata.state
Feb 14 19:40:57 linux-ytaf smartd[939]: Device: /dev/sdb, type changed from 'scsi' to 'sat'
Feb 14 19:40:57 linux-ytaf smartd[939]: Device: /dev/sdb [SAT], opened
Feb 14 19:40:57 linux-ytaf dbus[932]: [system] Successfully activated service 'org.freedesktop.locale1'
Feb 14 19:40:57 linux-ytaf smartd[939]: Device: /dev/sdb [SAT], TOSHIBA HDWD110, S/N:Y5GDEMGFS, WWN:5-000039-fe7c5a79c, FW:MS2OA8J0, 1.00 TB
Feb 14 19:40:57 linux-ytaf smartd[939]: Device: /dev/sdb [SAT], not found in smartd database.
Feb 14 19:40:57 linux-ytaf ModemManager[935]: <info>  ModemManager (version 1.4.10) starting in system bus...
Feb 14 19:40:57 linux-ytaf dbus[932]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Feb 14 19:40:58 linux-ytaf polkitd[987]: Started polkitd version 0.113
Feb 14 19:40:58 linux-ytaf kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
Feb 14 19:40:59 linux-ytaf smartd[939]: Device: /dev/sdb [SAT], is SMART capable. Adding to "monitor" list.
Feb 14 19:40:59 linux-ytaf smartd[939]: Device: /dev/sdb [SAT], state read from /var/lib/smartmontools/smartd.TOSHIBA_HDWD110-Y5GDEMGFS.ata.state
Feb 14 19:40:59 linux-ytaf smartd[939]: Monitoring 2 ATA and 0 SCSI devices
Feb 14 19:40:59 linux-ytaf smartd[939]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 5 = 0
Feb 14 19:40:59 linux-ytaf smartd[939]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 9 = 0
Feb 14 19:40:59 linux-ytaf smartd[939]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 12 = 0
Feb 14 19:40:59 linux-ytaf smartd[939]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 177 = 0
Feb 14 19:40:59 linux-ytaf smartd[939]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 179 = 0
Feb 14 19:40:59 linux-ytaf smartd[939]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 181 = 0
Feb 14 19:40:59 linux-ytaf smartd[939]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 182 = 0
Feb 14 19:40:59 linux-ytaf smartd[939]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 183 = 0
Feb 14 19:40:59 linux-ytaf smartd[939]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 187 = 0
Feb 14 19:40:59 linux-ytaf smartd[939]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 190 = 0
Feb 14 19:40:59 linux-ytaf smartd[939]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 195 = 0
Feb 14 19:40:59 linux-ytaf smartd[939]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 199 = 0
Feb 14 19:40:59 linux-ytaf smartd[939]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 235 = 0
Feb 14 19:40:59 linux-ytaf smartd[939]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 241 = 0
Feb 14 19:40:59 linux-ytaf smartd[939]: Device: /dev/sdb [SAT], same Attribute has different ID numbers: 1 = 0
Feb 14 19:40:59 linux-ytaf smartd[939]: Device: /dev/sdb [SAT], same Attribute has different ID numbers: 2 = 0
Feb 14 19:40:59 linux-ytaf smartd[939]: Device: /dev/sdb [SAT], same Attribute has different ID numbers: 3 = 0
Feb 14 19:40:59 linux-ytaf smartd[939]: Device: /dev/sdb [SAT], same Attribute has different ID numbers: 4 = 0
Feb 14 19:40:59 linux-ytaf smartd[939]: Device: /dev/sdb [SAT], same Attribute has different ID numbers: 5 = 0
Feb 14 19:40:59 linux-ytaf smartd[939]: Device: /dev/sdb [SAT], same Attribute has different ID numbers: 7 = 0
Feb 14 19:40:59 linux-ytaf smartd[939]: Device: /dev/sdb [SAT], same Attribute has different ID numbers: 8 = 0
Feb 14 19:40:59 linux-ytaf smartd[939]: Device: /dev/sdb [SAT], same Attribute has different ID numbers: 9 = 0
Feb 14 19:40:59 linux-ytaf smartd[939]: Device: /dev/sdb [SAT], same Attribute has different ID numbers: 10 = 0
Feb 14 19:40:59 linux-ytaf smartd[939]: Device: /dev/sdb [SAT], same Attribute has different ID numbers: 12 = 0
Feb 14 19:40:59 linux-ytaf smartd[939]: Device: /dev/sdb [SAT], same Attribute has different ID numbers: 192 = 0
Feb 14 19:40:59 linux-ytaf smartd[939]: Device: /dev/sdb [SAT], same Attribute has different ID numbers: 193 = 0
Feb 14 19:40:59 linux-ytaf smartd[939]: Device: /dev/sdb [SAT], same Attribute has different ID numbers: 194 = 0
Feb 14 19:40:59 linux-ytaf smartd[939]: Device: /dev/sdb [SAT], same Attribute has different ID numbers: 196 = 0
Feb 14 19:40:59 linux-ytaf smartd[939]: Device: /dev/sdb [SAT], same Attribute has different ID numbers: 197 = 0
Feb 14 19:40:59 linux-ytaf smartd[939]: Device: /dev/sdb [SAT], same Attribute has different ID numbers: 198 = 0
Feb 14 19:40:59 linux-ytaf smartd[939]: Device: /dev/sdb [SAT], same Attribute has different ID numbers: 199 = 0
Feb 14 19:41:00 linux-ytaf smartd[939]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.SAMSUNG_SSD_830_Series-S0Z4NEAC906195.ata.state
Feb 14 19:41:00 linux-ytaf smartd[939]: Device: /dev/sdb [SAT], state written to /var/lib/smartmontools/smartd.TOSHIBA_HDWD110-Y5GDEMGFS.ata.state
Feb 14 19:41:00 linux-ytaf kernel: nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
Feb 14 19:41:00 linux-ytaf kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Feb 14 19:41:00 linux-ytaf polkitd[987]: Loading rules from directory /etc/polkit-1/rules.d
Feb 14 19:41:00 linux-ytaf polkitd[987]: Loading rules from directory /usr/share/polkit-1/rules.d
Feb 14 19:41:00 linux-ytaf polkitd[987]: Finished loading, compiling and executing 3 rules
Feb 14 19:41:00 linux-ytaf dbus[932]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Feb 14 19:41:00 linux-ytaf polkitd[987]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
Feb 14 19:41:00 linux-ytaf SuSEfirewall2[1052]: Firewall rules set to CLOSE.
Feb 14 19:41:00 linux-ytaf logger[992]: /etc/init.d/xdm: No changes for /etc/X11/xdm/Xservers
Feb 14 19:41:00 linux-ytaf logger[992]: /etc/init.d/xdm: No changes for /etc/X11/xdm/xdm-config
Feb 14 19:41:00 linux-ytaf kernel: No iBFT detected.
Feb 14 19:41:01 linux-ytaf display-manager[951]: Starting service sddm..done
Feb 14 19:41:01 linux-ytaf sddm[1078]: Starting...
Feb 14 19:41:01 linux-ytaf sddm[1078]: Adding new display on vt 7 ...
Feb 14 19:41:01 linux-ytaf sddm[1078]: Display server starting...
Feb 14 19:41:01 linux-ytaf sddm[1078]: Running: /usr/bin/X -nolisten tcp -auth /run/sddm/{54df0300-91ee-4c2d-a24f-a7ebaf24ee15} -background none -noreset -displayfd 17 vt7
Feb 14 19:41:03 linux-ytaf ModemManager[935]: <info>  Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin
Feb 14 19:41:03 linux-ytaf sddm[1078]: Socket server started.
Feb 14 19:41:03 linux-ytaf sddm[1078]: Greeter starting...
Feb 14 19:41:03 linux-ytaf sddm[1078]: Adding cookie to "/run/sddm/{54df0300-91ee-4c2d-a24f-a7ebaf24ee15}"
Feb 14 19:41:03 linux-ytaf sddm-helper[1213]: [PAM] Starting...
Feb 14 19:41:03 linux-ytaf sddm-helper[1213]: [PAM] Authenticating...
Feb 14 19:41:03 linux-ytaf sddm-helper[1213]: [PAM] returning.
Feb 14 19:41:03 linux-ytaf sddm-helper[1213]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
Feb 14 19:41:03 linux-ytaf systemd[1215]: pam_unix(systemd-user:session): session opened for user sddm by (uid=0)
Feb 14 19:41:03 linux-ytaf sddm[1078]: Message received from greeter: Connect
Feb 14 19:41:04 linux-ytaf kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Feb 14 19:41:04 linux-ytaf wickedd-dhcp4[1055]: eth0: Request to acquire DHCPv4 lease with UUID 3dcac056-d302-0400-3304-000004000000
Feb 14 19:41:04 linux-ytaf kernel: NET: Registered protocol family 17
Feb 14 19:41:05 linux-ytaf wickedd-dhcp4[1055]: eth0: Committed DHCPv4 lease with address 192.168.178.12 (lease time 864000 sec, renew in 432000 sec, rebind in 756000 sec)
Feb 14 19:41:05 linux-ytaf avahi-daemon[933]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.178.12.
Feb 14 19:41:05 linux-ytaf avahi-daemon[933]: New relevant interface eth0.IPv4 for mDNS.
Feb 14 19:41:05 linux-ytaf avahi-daemon[933]: Registering new address record for 192.168.178.12 on eth0.IPv4.
Feb 14 19:41:05 linux-ytaf wickedd[1075]: eth0: Notified neighbours about IP address 192.168.178.12
Feb 14 19:41:05 MM-Home wicked[1077]: lo              up
Feb 14 19:41:05 MM-Home wicked[1077]: eth0            up
Feb 14 19:41:05 MM-Home echo[1402]: Starting mail service (Postfix)
Feb 14 19:41:05 MM-Home iscsiadm[1404]: iscsiadm: No records found
Feb 14 19:41:05 MM-Home SuSEfirewall2[1435]: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Feb 14 19:41:05 MM-Home SuSEfirewall2[1442]: using default zone 'ext' for interface eth0
Feb 14 19:41:06 MM-Home postfix/postfix-script[1592]: starting the Postfix mail system
Feb 14 19:41:06 MM-Home SuSEfirewall2[1593]: Firewall rules successfully set
Feb 14 19:41:06 MM-Home postfix/master[1595]: daemon started -- version 2.11.6, configuration /etc/postfix
Feb 14 19:41:06 MM-Home ntpd[1425]: ntpd 4.2.8p4@1.3265-o Thu Dec 17 05:32:52 UTC 2015 (1): Starting
Feb 14 19:41:06 MM-Home ntpd[1425]: Command line: /usr/sbin/ntpd -p /var/run/ntp/ntpd.pid -g -u ntp:ntp -c /etc/ntp.conf
Feb 14 19:41:06 MM-Home sntp[1609]: sntp 4.2.8p4@1.3265-o Thu Dec 17 05:32:29 UTC 2015 (1)
Feb 14 19:41:06 MM-Home sntp[1609]: kod_init_kod_db(): Cannot open KoD db file /var/db/ntp-kod: No such file or directory
Feb 14 19:41:06 MM-Home ntpd[1608]: proto: precision = 0.076 usec (-24)
Feb 14 19:41:06 MM-Home start-ntpd[1407]: Starting network time protocol daemon (NTPD)sntp 4.2.8p4@1.3265-o Thu Dec 17 05:32:29 UTC 2015 (1)
Feb 14 19:41:06 MM-Home start-ntpd[1407]: kod_init_kod_db(): Cannot open KoD db file /var/db/ntp-kod: No such file or directory
Feb 14 19:41:06 MM-Home ntpd[1608]: switching logging to file /var/log/ntp
Feb 14 19:41:06 MM-Home sntp[1609]: 2016-02-14 19:41:06.194081 (-0100) -0.43998 +/- 0.343999 192.168.178.1 s3 no-leap
Feb 14 19:41:05 MM-Home start-ntpd[1407]: 2016-02-14 19:41:06.194081 (-0100) -0.43998 +/- 0.343999 192.168.178.1 s3 no-leap
Feb 14 19:41:05 MM-Home /usr/sbin/start-ntpd[1618]: runtime configuration: server 192.168.178.1
Feb 14 19:41:05 MM-Home start-ntpd[1407]: /usr/sbin/ntpq: read: Connection refused
Feb 14 19:41:05 MM-Home cron[1617]: (CRON) INFO (RANDOM_DELAY will be scaled with factor 36% if used.)
Feb 14 19:41:05 MM-Home cron[1617]: (CRON) INFO (running with inotify support)
Feb 14 19:41:06 MM-Home dbus[932]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
Feb 14 19:41:06 MM-Home udisksd[1624]: udisks daemon version 2.1.6 starting
Feb 14 19:41:07 MM-Home dbus[932]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Feb 14 19:41:07 MM-Home udisksd[1624]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Feb 14 19:41:07 MM-Home dbus[932]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
Feb 14 19:41:07 MM-Home dbus[932]: [system] Successfully activated service 'org.freedesktop.UPower'
Feb 14 19:41:13 MM-Home sddm[1078]: Message received from greeter: Login
Feb 14 19:41:13 MM-Home sddm[1078]: Reading from "/usr/share/xsessions/plasma5.desktop"
Feb 14 19:41:13 MM-Home sddm[1078]: Session "/usr/share/xsessions/plasma5.desktop" selected, command: "/usr/bin/startkde"
Feb 14 19:41:13 MM-Home sddm-helper[1657]: [PAM] Starting...
Feb 14 19:41:13 MM-Home sddm-helper[1657]: [PAM] Authenticating...
Feb 14 19:41:13 MM-Home sddm-helper[1657]: [PAM] Preparing to converse...
Feb 14 19:41:13 MM-Home sddm-helper[1657]: [PAM] Conversation with 1 messages
Feb 14 19:41:13 MM-Home sddm-helper[1657]: [PAM] returning.
Feb 14 19:41:13 MM-Home sddm[1078]: Authenticated successfully
Feb 14 19:41:13 MM-Home sddm-helper[1657]: pam_unix(sddm:session): session opened for user marc by (uid=0)
Feb 14 19:41:13 MM-Home systemd[1658]: pam_unix(systemd-user:session): session opened for user marc by (uid=0)
Feb 14 19:41:13 MM-Home sddm-helper[1660]: Adding cookie to "/home/marc/.Xauthority"
Feb 14 19:41:13 MM-Home sddm-helper[1213]: [PAM] Ended.
Feb 14 19:41:13 MM-Home sddm[1078]: Auth: sddm-helper exited successfully
Feb 14 19:41:13 MM-Home sddm[1078]: Greeter stopped.
Feb 14 19:41:13 MM-Home sddm[1078]: Session started
Feb 14 19:41:17 MM-Home polkitd[987]: Registered Authentication Agent for unix-session:2 (system bus name :1.32 [/usr/lib64/libexec/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale de_DE.UTF-8)
Feb 14 19:41:18 MM-Home dbus[932]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service'
Feb 14 19:41:18 MM-Home dbus[932]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Feb 14 19:41:18 MM-Home rtkit-daemon[1822]: Successfully called chroot.
Feb 14 19:41:18 MM-Home rtkit-daemon[1822]: Successfully dropped privileges.
Feb 14 19:41:18 MM-Home rtkit-daemon[1822]: Successfully limited resources.
Feb 14 19:41:18 MM-Home rtkit-daemon[1822]: Running.
Feb 14 19:41:18 MM-Home rtkit-daemon[1822]: Canary thread running.
Feb 14 19:41:18 MM-Home rtkit-daemon[1822]: Watchdog thread running.
Feb 14 19:41:18 MM-Home rtkit-daemon[1822]: Successfully made thread 1821 of process 1821 (/usr/bin/pulseaudio) owned by 'marc' high priority at nice level -11.
Feb 14 19:41:18 MM-Home rtkit-daemon[1822]: Supervising 1 threads of 1 processes of 1 users.
Feb 14 19:41:18 MM-Home dbus[932]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Feb 14 19:41:19 MM-Home org.kde.powerdevil.backlighthelper[932]: powerdevil: no kernel backlight interface found
Feb 14 19:41:19 MM-Home dbus[932]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Feb 14 19:41:23 MM-Home rtkit-daemon[1822]: Supervising 1 threads of 1 processes of 1 users.
Feb 14 19:41:23 MM-Home rtkit-daemon[1822]: Successfully made thread 1871 of process 1821 (/usr/bin/pulseaudio) owned by 'marc' RT at priority 5.
Feb 14 19:41:23 MM-Home rtkit-daemon[1822]: Supervising 2 threads of 1 processes of 1 users.
Feb 14 19:41:23 MM-Home rtkit-daemon[1822]: Supervising 2 threads of 1 processes of 1 users.
Feb 14 19:41:23 MM-Home rtkit-daemon[1822]: Successfully made thread 1872 of process 1821 (/usr/bin/pulseaudio) owned by 'marc' RT at priority 5.
Feb 14 19:41:23 MM-Home rtkit-daemon[1822]: Supervising 3 threads of 1 processes of 1 users.
Feb 14 19:41:23 MM-Home rtkit-daemon[1822]: Supervising 3 threads of 1 processes of 1 users.
Feb 14 19:41:23 MM-Home rtkit-daemon[1822]: Successfully made thread 1873 of process 1821 (/usr/bin/pulseaudio) owned by 'marc' RT at priority 5.
Feb 14 19:41:23 MM-Home rtkit-daemon[1822]: Supervising 4 threads of 1 processes of 1 users.
Feb 14 19:41:23 MM-Home dbus[932]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Feb 14 19:41:23 MM-Home rtkit-daemon[1822]: Successfully made thread 1876 of process 1876 (/usr/bin/pulseaudio) owned by 'marc' high priority at nice level -11.
Feb 14 19:41:23 MM-Home rtkit-daemon[1822]: Supervising 5 threads of 2 processes of 1 users.
Feb 14 19:41:23 MM-Home pulseaudio[1876]: [pulseaudio] pid.c: Daemon already running.
Feb 14 19:41:24 MM-Home bluetoothd[1874]: Bluetooth daemon 5.35
Feb 14 19:41:24 MM-Home dbus[932]: [system] Successfully activated service 'org.bluez'
Feb 14 19:41:24 MM-Home kernel: Bluetooth: Core ver 2.20
Feb 14 19:41:24 MM-Home kernel: NET: Registered protocol family 31
Feb 14 19:41:24 MM-Home kernel: Bluetooth: HCI device and connection manager initialized
Feb 14 19:41:24 MM-Home kernel: Bluetooth: HCI socket layer initialized
Feb 14 19:41:24 MM-Home kernel: Bluetooth: L2CAP socket layer initialized
Feb 14 19:41:24 MM-Home kernel: Bluetooth: SCO socket layer initialized
Feb 14 19:41:24 MM-Home bluetoothd[1874]: Starting SDP server
Feb 14 19:41:24 MM-Home dbus[932]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Feb 14 19:41:24 MM-Home bluetoothd[1874]: Bluetooth management interface 1.9 initialized
Feb 14 19:41:24 MM-Home kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Feb 14 19:41:24 MM-Home kernel: Bluetooth: BNEP filters: protocol multicast
Feb 14 19:41:24 MM-Home kernel: Bluetooth: BNEP socket layer initialized
Feb 14 19:41:24 MM-Home dbus[932]: [system] Successfully activated service 'org.freedesktop.hostname1'
Feb 14 19:41:24 MM-Home kernel: fuse init (API version 7.23)
Feb 14 19:41:26 MM-Home dbus[932]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service'
Feb 14 19:41:26 MM-Home PackageKit[1942]: daemon start
Feb 14 19:41:29 MM-Home dbus[932]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Feb 14 19:41:29 MM-Home PackageKit[1942]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 19:41:29 MM-Home PackageKit[1942]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 19:41:29 MM-Home PackageKit[1942]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 19:41:29 MM-Home PackageKit[1942]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 19:41:31 MM-Home PackageKit[1942]: refresh-cache transaction /1_bedecebb from uid 1000 finished with failed after 1865ms
Feb 14 19:41:32 MM-Home PackageKit[1942]: refresh-cache transaction /2_cbdbdddd from uid 1000 finished with failed after 272ms
Feb 14 19:41:49 MM-Home PackageKit[1942]: daemon quit
Feb 14 19:41:49 MM-Home packagekitd[1942]: (packagekitd:1942): GLib-CRITICAL **: Source ID 6 was not found when attempting to remove it
Feb 14 19:42:44 MM-Home su[2066]: (to root) marc on pts/0
Feb 14 19:42:44 MM-Home su[2066]: pam_unix(su:session): session opened for user root by marc(uid=1000)
Feb 14 19:44:36 MM-Home kernel: nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
Feb 14 19:45:01 MM-Home cron[2173]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 19:45:01 MM-Home systemd[2174]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 19:45:01 MM-Home CRON[2173]: pam_unix(crond:session): session closed for user root
Feb 14 19:45:01 MM-Home systemd[2175]: pam_unix(systemd-user:session): session closed for user root
Feb 14 20:00:01 MM-Home cron[2283]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 20:00:01 MM-Home systemd[2284]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 20:00:02 MM-Home CRON[2283]: pam_unix(crond:session): session closed for user root
Feb 14 20:00:02 MM-Home systemd[2285]: pam_unix(systemd-user:session): session closed for user root
Feb 14 20:01:06 MM-Home dbus[932]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service'
Feb 14 20:01:06 MM-Home PackageKit[2326]: daemon start
Feb 14 20:01:06 MM-Home dbus[932]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Feb 14 20:01:06 MM-Home PackageKit[2326]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 20:01:06 MM-Home PackageKit[2326]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 20:01:06 MM-Home PackageKit[2326]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 20:01:06 MM-Home PackageKit[2326]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 20:01:09 MM-Home PackageKit[2326]: refresh-cache transaction /1_bbdadbca from uid 1000 finished with failed after 2466ms
Feb 14 20:01:09 MM-Home PackageKit[2326]: refresh-cache transaction /2_daeceaab from uid 1000 finished with failed after 281ms
Feb 14 20:01:26 MM-Home PackageKit[2326]: daemon quit
Feb 14 20:01:26 MM-Home packagekitd[2326]: (packagekitd:2326): GLib-CRITICAL **: Source ID 6 was not found when attempting to remove it
Feb 14 20:06:02 MM-Home su[2383]: (to root) marc on pts/2
Feb 14 20:06:02 MM-Home su[2383]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 20:06:02 MM-Home su[2383]: pam_unix(su:session): session closed for user root
Feb 14 20:06:02 MM-Home su[2388]: (to root) marc on pts/2
Feb 14 20:06:02 MM-Home su[2388]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 20:06:12 MM-Home dbus[932]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Feb 14 20:06:12 MM-Home dbus[932]: [system] Successfully activated service 'org.opensuse.Snapper'
Feb 14 20:07:44 MM-Home dbus[932]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Feb 14 20:07:44 MM-Home dbus[932]: [system] Successfully activated service 'org.opensuse.Snapper'
Feb 14 20:08:41 MM-Home dbus[932]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service'
Feb 14 20:08:41 MM-Home PackageKit[4527]: daemon start
Feb 14 20:08:42 MM-Home dbus[932]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Feb 14 20:08:42 MM-Home PackageKit[4527]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 20:08:42 MM-Home PackageKit[4527]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 20:08:42 MM-Home PackageKit[4527]: refresh-cache transaction /1_cabbcdae from uid 1000 finished with failed after 0ms
Feb 14 20:08:42 MM-Home PackageKit[4527]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 20:08:42 MM-Home PackageKit[4527]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 20:08:42 MM-Home PackageKit[4527]: refresh-cache transaction /2_bceacaea from uid 1000 finished with failed after 0ms
Feb 14 20:09:02 MM-Home PackageKit[4527]: daemon quit
Feb 14 20:09:02 MM-Home packagekitd[4527]: (packagekitd:4527): GLib-CRITICAL **: Source ID 6 was not found when attempting to remove it
Feb 14 20:11:41 MM-Home kernel: device-mapper: uevent: version 1.0.3
Feb 14 20:11:41 MM-Home kernel: device-mapper: ioctl: 4.31.0-ioctl (2015-3-12) initialised: dm-devel@redhat.com
Feb 14 20:11:41 MM-Home systemd-udevd[492]: Network interface NamePolicy= disabled on kernel commandline, ignoring.
Feb 14 20:11:44 MM-Home os-prober[17138]: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda1
Feb 14 20:11:44 MM-Home 50mounted-tests[17148]: debug: mounted using GRUB ntfs filesystem driver
Feb 14 20:11:44 MM-Home 50mounted-tests[17149]: debug: running subtest /usr/lib/os-probes/mounted/05efi
Feb 14 20:11:44 MM-Home 05efi[17152]: debug: /dev/sda1 is ntfs partition: exiting
Feb 14 20:11:44 MM-Home 50mounted-tests[17153]: debug: running subtest /usr/lib/os-probes/mounted/10freedos
Feb 14 20:11:44 MM-Home 10freedos[17156]: debug: /dev/sda1 is not a FAT partition: exiting
Feb 14 20:11:44 MM-Home 50mounted-tests[17157]: debug: running subtest /usr/lib/os-probes/mounted/10qnx
Feb 14 20:11:44 MM-Home 10qnx[17160]: debug: /dev/sda1 is not a QNX4 partition: exiting
Feb 14 20:11:44 MM-Home 50mounted-tests[17161]: debug: running subtest /usr/lib/os-probes/mounted/20macosx
Feb 14 20:11:44 MM-Home macosx-prober[17163]: debug: /dev/sda1 is not an HFS+ partition: exiting
Feb 14 20:11:44 MM-Home 50mounted-tests[17164]: debug: running subtest /usr/lib/os-probes/mounted/20microsoft
Feb 14 20:11:44 MM-Home 20microsoft[17167]: debug: Skipping legacy bootloaders on UEFI system
Feb 14 20:11:44 MM-Home 50mounted-tests[17168]: debug: running subtest /usr/lib/os-probes/mounted/30utility
Feb 14 20:11:44 MM-Home 30utility[17171]: debug: /dev/sda1 is not a FAT partition: exiting
Feb 14 20:11:44 MM-Home 50mounted-tests[17172]: debug: running subtest /usr/lib/os-probes/mounted/40lsb
Feb 14 20:11:44 MM-Home 50mounted-tests[17174]: debug: running subtest /usr/lib/os-probes/mounted/70hurd
Feb 14 20:11:44 MM-Home 50mounted-tests[17176]: debug: running subtest /usr/lib/os-probes/mounted/80minix
Feb 14 20:11:44 MM-Home 50mounted-tests[17178]: debug: running subtest /usr/lib/os-probes/mounted/83haiku
Feb 14 20:11:44 MM-Home 83haiku[17181]: debug: /dev/sda1 is not a BeFS partition: exiting
Feb 14 20:11:44 MM-Home 50mounted-tests[17182]: debug: running subtest /usr/lib/os-probes/mounted/90linux-distro
Feb 14 20:11:44 MM-Home 50mounted-tests[17188]: debug: running subtest /usr/lib/os-probes/mounted/90solaris
Feb 14 20:11:44 MM-Home 50mounted-tests[17190]: debug: running subtest /usr/lib/os-probes/mounted/efi
Feb 14 20:11:44 MM-Home os-prober[17200]: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda2
Feb 14 20:11:44 MM-Home 50mounted-tests[17210]: debug: mounted using GRUB fat filesystem driver
Feb 14 20:11:44 MM-Home 50mounted-tests[17211]: debug: running subtest /usr/lib/os-probes/mounted/05efi
Feb 14 20:11:44 MM-Home 05efi[17214]: debug: /dev/sda2 is a FAT partition (mounted by GRUB)
Feb 14 20:11:44 MM-Home 05efi[17219]: debug: /dev/sda2 container is ''
Feb 14 20:11:44 MM-Home 05efi[17223]: debug: /dev/sda2 partition scheme is gpt
Feb 14 20:11:44 MM-Home 05efi[17224]: debug: /dev/sda2 partition type is c12a7328-f81f-11d2-ba4b-00a0c93ec93b
Feb 14 20:11:44 MM-Home 05efi[17228]: debug: running subtest /usr/lib/os-probes/mounted/efi/10elilo
Feb 14 20:11:44 MM-Home 05efi[17231]: debug: running subtest /usr/lib/os-probes/mounted/efi/20microsoft
Feb 14 20:11:44 MM-Home 20microsoft[17250]: result: Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows
Feb 14 20:11:44 MM-Home 05efi[17251]: debug: bootloader Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows found by subtest /usr/lib/os-probes/mounted/efi/20microsoft
Feb 14 20:11:44 MM-Home 05efi[17252]: result: /dev/sda2@/efi/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi
Feb 14 20:11:44 MM-Home 50mounted-tests[17253]: debug: os found by subtest /usr/lib/os-probes/mounted/05efi
Feb 14 20:11:44 MM-Home os-prober[17256]: debug: os detected by /usr/lib/os-probes/50mounted-tests
Feb 14 20:11:44 MM-Home os-prober[17264]: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda3
Feb 14 20:11:44 MM-Home 50mounted-tests[17271]: debug: /dev/sda3 is a partition without file system; skipping
Feb 14 20:11:44 MM-Home os-prober[17272]: debug: os detected by /usr/lib/os-probes/50mounted-tests
Feb 14 20:11:44 MM-Home os-prober[17280]: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda4
Feb 14 20:11:44 MM-Home 50mounted-tests[17290]: debug: mounted using GRUB ntfs filesystem driver
Feb 14 20:11:44 MM-Home 50mounted-tests[17291]: debug: running subtest /usr/lib/os-probes/mounted/05efi
Feb 14 20:11:44 MM-Home 05efi[17294]: debug: /dev/sda4 is ntfs partition: exiting
Feb 14 20:11:44 MM-Home 50mounted-tests[17295]: debug: running subtest /usr/lib/os-probes/mounted/10freedos
Feb 14 20:11:45 MM-Home 10freedos[17298]: debug: /dev/sda4 is not a FAT partition: exiting
Feb 14 20:11:45 MM-Home 50mounted-tests[17299]: debug: running subtest /usr/lib/os-probes/mounted/10qnx
Feb 14 20:11:45 MM-Home 10qnx[17302]: debug: /dev/sda4 is not a QNX4 partition: exiting
Feb 14 20:11:45 MM-Home 50mounted-tests[17303]: debug: running subtest /usr/lib/os-probes/mounted/20macosx
Feb 14 20:11:45 MM-Home macosx-prober[17305]: debug: /dev/sda4 is not an HFS+ partition: exiting
Feb 14 20:11:45 MM-Home 50mounted-tests[17306]: debug: running subtest /usr/lib/os-probes/mounted/20microsoft
Feb 14 20:11:45 MM-Home 20microsoft[17309]: debug: Skipping legacy bootloaders on UEFI system
Feb 14 20:11:45 MM-Home 50mounted-tests[17310]: debug: running subtest /usr/lib/os-probes/mounted/30utility
Feb 14 20:11:45 MM-Home 30utility[17313]: debug: /dev/sda4 is not a FAT partition: exiting
Feb 14 20:11:45 MM-Home 50mounted-tests[17314]: debug: running subtest /usr/lib/os-probes/mounted/40lsb
Feb 14 20:11:45 MM-Home 50mounted-tests[17316]: debug: running subtest /usr/lib/os-probes/mounted/70hurd
Feb 14 20:11:45 MM-Home 50mounted-tests[17318]: debug: running subtest /usr/lib/os-probes/mounted/80minix
Feb 14 20:11:45 MM-Home 50mounted-tests[17320]: debug: running subtest /usr/lib/os-probes/mounted/83haiku
Feb 14 20:11:45 MM-Home 83haiku[17323]: debug: /dev/sda4 is not a BeFS partition: exiting
Feb 14 20:11:45 MM-Home 50mounted-tests[17324]: debug: running subtest /usr/lib/os-probes/mounted/90linux-distro
Feb 14 20:11:45 MM-Home 50mounted-tests[17330]: debug: running subtest /usr/lib/os-probes/mounted/90solaris
Feb 14 20:11:45 MM-Home 50mounted-tests[17332]: debug: running subtest /usr/lib/os-probes/mounted/efi
Feb 14 20:11:45 MM-Home os-prober[17353]: debug: running /usr/lib/os-probes/mounted/05efi on mounted /dev/sdb1
Feb 14 20:11:45 MM-Home 05efi[17356]: debug: /dev/sdb1 is a FAT32 partition
Feb 14 20:11:45 MM-Home 05efi[17361]: debug: /dev/sdb1 container is ''
Feb 14 20:11:45 MM-Home 05efi[17365]: debug: /dev/sdb1 partition scheme is gpt
Feb 14 20:11:45 MM-Home 05efi[17366]: debug: /dev/sdb1 partition type is c12a7328-f81f-11d2-ba4b-00a0c93ec93b
Feb 14 20:11:45 MM-Home 05efi[17370]: debug: running subtest /usr/lib/os-probes/mounted/efi/10elilo
Feb 14 20:11:45 MM-Home 05efi[17373]: debug: running subtest /usr/lib/os-probes/mounted/efi/20microsoft
Feb 14 20:11:45 MM-Home os-prober[17378]: debug: running /usr/lib/os-probes/mounted/10freedos on mounted /dev/sdb1
Feb 14 20:11:45 MM-Home 10freedos[17381]: debug: /dev/sdb1 is a FAT32 partition
Feb 14 20:11:45 MM-Home os-prober[17384]: debug: running /usr/lib/os-probes/mounted/10qnx on mounted /dev/sdb1
Feb 14 20:11:45 MM-Home 10qnx[17387]: debug: /dev/sdb1 is not a QNX4 partition: exiting
Feb 14 20:11:45 MM-Home os-prober[17388]: debug: running /usr/lib/os-probes/mounted/20macosx on mounted /dev/sdb1
Feb 14 20:11:45 MM-Home macosx-prober[17390]: debug: /dev/sdb1 is not an HFS+ partition: exiting
Feb 14 20:11:45 MM-Home os-prober[17391]: debug: running /usr/lib/os-probes/mounted/20microsoft on mounted /dev/sdb1
Feb 14 20:11:45 MM-Home 20microsoft[17394]: debug: Skipping legacy bootloaders on UEFI system
Feb 14 20:11:45 MM-Home os-prober[17395]: debug: running /usr/lib/os-probes/mounted/30utility on mounted /dev/sdb1
Feb 14 20:11:45 MM-Home 30utility[17398]: debug: /dev/sdb1 is a FAT32 partition
Feb 14 20:11:45 MM-Home os-prober[17403]: debug: running /usr/lib/os-probes/mounted/40lsb on mounted /dev/sdb1
Feb 14 20:11:45 MM-Home os-prober[17405]: debug: running /usr/lib/os-probes/mounted/70hurd on mounted /dev/sdb1
Feb 14 20:11:45 MM-Home os-prober[17407]: debug: running /usr/lib/os-probes/mounted/80minix on mounted /dev/sdb1
Feb 14 20:11:45 MM-Home os-prober[17409]: debug: running /usr/lib/os-probes/mounted/83haiku on mounted /dev/sdb1
Feb 14 20:11:45 MM-Home 83haiku[17412]: debug: /dev/sdb1 is not a BeFS partition: exiting
Feb 14 20:11:45 MM-Home os-prober[17413]: debug: running /usr/lib/os-probes/mounted/90linux-distro on mounted /dev/sdb1
Feb 14 20:11:45 MM-Home os-prober[17419]: debug: running /usr/lib/os-probes/mounted/90solaris on mounted /dev/sdb1
Feb 14 20:11:45 MM-Home os-prober[17425]: debug: /dev/sdb2: is active swap
Feb 14 20:11:45 MM-Home os-prober[17457]: debug: running /usr/lib/os-probes/mounted/05efi on mounted /dev/sdb4
Feb 14 20:11:45 MM-Home 05efi[17460]: debug: /dev/sdb4 is xfs partition: exiting
Feb 14 20:11:45 MM-Home os-prober[17461]: debug: running /usr/lib/os-probes/mounted/10freedos on mounted /dev/sdb4
Feb 14 20:11:45 MM-Home 10freedos[17464]: debug: /dev/sdb4 is not a FAT partition: exiting
Feb 14 20:11:45 MM-Home os-prober[17465]: debug: running /usr/lib/os-probes/mounted/10qnx on mounted /dev/sdb4
Feb 14 20:11:45 MM-Home 10qnx[17468]: debug: /dev/sdb4 is not a QNX4 partition: exiting
Feb 14 20:11:45 MM-Home os-prober[17469]: debug: running /usr/lib/os-probes/mounted/20macosx on mounted /dev/sdb4
Feb 14 20:11:45 MM-Home macosx-prober[17471]: debug: /dev/sdb4 is not an HFS+ partition: exiting
Feb 14 20:11:45 MM-Home os-prober[17472]: debug: running /usr/lib/os-probes/mounted/20microsoft on mounted /dev/sdb4
Feb 14 20:11:45 MM-Home 20microsoft[17475]: debug: Skipping legacy bootloaders on UEFI system
Feb 14 20:11:45 MM-Home os-prober[17476]: debug: running /usr/lib/os-probes/mounted/30utility on mounted /dev/sdb4
Feb 14 20:11:45 MM-Home 30utility[17479]: debug: /dev/sdb4 is not a FAT partition: exiting
Feb 14 20:11:45 MM-Home os-prober[17480]: debug: running /usr/lib/os-probes/mounted/40lsb on mounted /dev/sdb4
Feb 14 20:11:45 MM-Home os-prober[17482]: debug: running /usr/lib/os-probes/mounted/70hurd on mounted /dev/sdb4
Feb 14 20:11:45 MM-Home os-prober[17484]: debug: running /usr/lib/os-probes/mounted/80minix on mounted /dev/sdb4
Feb 14 20:11:45 MM-Home os-prober[17486]: debug: running /usr/lib/os-probes/mounted/83haiku on mounted /dev/sdb4
Feb 14 20:11:45 MM-Home 83haiku[17489]: debug: /dev/sdb4 is not a BeFS partition: exiting
Feb 14 20:11:45 MM-Home os-prober[17490]: debug: running /usr/lib/os-probes/mounted/90linux-distro on mounted /dev/sdb4
Feb 14 20:11:45 MM-Home os-prober[17496]: debug: running /usr/lib/os-probes/mounted/90solaris on mounted /dev/sdb4
Feb 14 20:11:45 MM-Home os-prober[17505]: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sdc1
Feb 14 20:11:45 MM-Home 50mounted-tests[17515]: debug: mounted using GRUB fat filesystem driver
Feb 14 20:11:45 MM-Home 50mounted-tests[17516]: debug: running subtest /usr/lib/os-probes/mounted/05efi
Feb 14 20:11:45 MM-Home 05efi[17519]: debug: /dev/sdc1 is a FAT partition (mounted by GRUB)
Feb 14 20:11:45 MM-Home 05efi[17524]: debug: /dev/sdc1 container is ''
Feb 14 20:11:45 MM-Home 05efi[17528]: debug: /dev/sdc1 partition scheme is dos
Feb 14 20:11:45 MM-Home 05efi[17529]: debug: /dev/sdc1 partition type is 0xc
Feb 14 20:11:45 MM-Home 05efi[17530]: debug: /dev/sdc1 is not a ESP partition: exiting
Feb 14 20:11:45 MM-Home 50mounted-tests[17531]: debug: running subtest /usr/lib/os-probes/mounted/10freedos
Feb 14 20:11:45 MM-Home 10freedos[17534]: debug: /dev/sdc1 is a FAT partition (mounted by GRUB)
Feb 14 20:11:45 MM-Home 50mounted-tests[17537]: debug: running subtest /usr/lib/os-probes/mounted/10qnx
Feb 14 20:11:45 MM-Home 10qnx[17540]: debug: /dev/sdc1 is not a QNX4 partition: exiting
Feb 14 20:11:45 MM-Home 50mounted-tests[17541]: debug: running subtest /usr/lib/os-probes/mounted/20macosx
Feb 14 20:11:45 MM-Home macosx-prober[17543]: debug: /dev/sdc1 is not an HFS+ partition: exiting
Feb 14 20:11:45 MM-Home 50mounted-tests[17544]: debug: running subtest /usr/lib/os-probes/mounted/20microsoft
Feb 14 20:11:45 MM-Home 20microsoft[17547]: debug: Skipping legacy bootloaders on UEFI system
Feb 14 20:11:45 MM-Home 50mounted-tests[17548]: debug: running subtest /usr/lib/os-probes/mounted/30utility
Feb 14 20:11:45 MM-Home 30utility[17551]: debug: /dev/sdc1 is a FAT partition (mounted by GRUB)
Feb 14 20:11:45 MM-Home 50mounted-tests[17556]: debug: running subtest /usr/lib/os-probes/mounted/40lsb
Feb 14 20:11:45 MM-Home 50mounted-tests[17558]: debug: running subtest /usr/lib/os-probes/mounted/70hurd
Feb 14 20:11:45 MM-Home 50mounted-tests[17560]: debug: running subtest /usr/lib/os-probes/mounted/80minix
Feb 14 20:11:45 MM-Home 50mounted-tests[17562]: debug: running subtest /usr/lib/os-probes/mounted/83haiku
Feb 14 20:11:45 MM-Home 83haiku[17565]: debug: /dev/sdc1 is not a BeFS partition: exiting
Feb 14 20:11:45 MM-Home 50mounted-tests[17566]: debug: running subtest /usr/lib/os-probes/mounted/90linux-distro
Feb 14 20:11:45 MM-Home 50mounted-tests[17572]: debug: running subtest /usr/lib/os-probes/mounted/90solaris
Feb 14 20:11:45 MM-Home 50mounted-tests[17574]: debug: running subtest /usr/lib/os-probes/mounted/efi
Feb 14 20:11:45 MM-Home os-prober[17584]: debug: running /usr/lib/os-probes/50mounted-tests on /dev/block/8
Feb 14 20:11:45 MM-Home 50mounted-tests[17590]: debug: /dev/block/8 type not recognised; skipping
Feb 14 20:11:45 MM-Home os-prober[17591]: debug: os detected by /usr/lib/os-probes/50mounted-tests
Feb 14 20:14:21 MM-Home su[2066]: pam_unix(su:session): session closed for user root
Feb 14 20:14:41 MM-Home polkitd[987]: Unregistered Authentication Agent for unix-session:2 (system bus name :1.32, object path /org/kde/PolicyKit1/AuthenticationAgent, locale de_DE.UTF-8)
Feb 14 20:14:56 MM-Home su[2388]: pam_unix(su:session): session closed for user root
Feb 14 20:14:56 MM-Home ca.desrt.dconf[1708]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
Feb 14 20:14:56 MM-Home sddm[1078]: Auth: sddm-helper crashed (exit code 15)
Feb 14 20:14:56 MM-Home sddm[1078]: Authentication error: "Process crashed"
Feb 14 20:14:56 MM-Home sddm[1078]: Auth: sddm-helper exited with 15
Feb 14 20:14:56 MM-Home sddm[1078]: Socket server stopping...
Feb 14 20:14:56 MM-Home sddm[1078]: Socket server stopped.
Feb 14 20:14:56 MM-Home sddm[1078]: Display server stopping...
Feb 14 20:14:56 MM-Home bluetoothd[1874]: Terminating
Feb 14 20:14:56 MM-Home bluetoothd[1874]: Stopping SDP server
Feb 14 20:14:56 MM-Home bluetoothd[1874]: Exit
Feb 14 20:14:56 MM-Home avahi-daemon[933]: Got SIGTERM, quitting.
Feb 14 20:14:56 MM-Home avahi-daemon[933]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.178.12.
Feb 14 20:14:56 MM-Home smartd[939]: smartd received signal 15: Terminated
Feb 14 20:14:56 MM-Home ModemManager[935]: <info>  Caught signal, shutting down...
Feb 14 20:14:56 MM-Home smartd[939]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.SAMSUNG_SSD_830_Series-S0Z4NEAC906195.ata.state
Feb 14 20:14:56 MM-Home smartd[939]: Device: /dev/sdb [SAT], state written to /var/lib/smartmontools/smartd.TOSHIBA_HDWD110-Y5GDEMGFS.ata.state
Feb 14 20:14:56 MM-Home smartd[939]: smartd is exiting (exit status 0)
Feb 14 20:14:56 MM-Home avahi-daemon[933]: avahi-daemon 0.6.31 exiting.
Feb 14 20:14:56 MM-Home ModemManager[935]: <info>  ModemManager is shut down
Feb 14 20:14:56 MM-Home iscsiadm[19102]: iscsiadm: No matching sessions found
Feb 14 20:14:56 MM-Home org.kde.kglobalaccel[1708]: The X11 connection broke: I/O error (code 1)
Feb 14 20:14:56 MM-Home org.kde.kglobalaccel[1708]: XIO:  fatal IO error 6 (Kein passendes Gerät bzw. keine passende Adresse gefunden) on X server ":0"
Feb 14 20:14:56 MM-Home org.kde.kglobalaccel[1708]: after 390 requests (388 known processed) with 0 events remaining.
Feb 14 20:14:56 MM-Home systemd[1659]: pam_unix(systemd-user:session): session closed for user marc
Feb 14 20:14:56 MM-Home SuSEfirewall2[19150]: Not unloading firewall rules at system shutdown
Feb 14 20:14:56 MM-Home postfix/postfix-script[19160]: stopping the Postfix mail system
Feb 14 20:14:56 MM-Home postfix/master[1595]: terminating on signal 15
Feb 14 20:14:56 MM-Home wickedd-dhcp4[1055]: eth0: Request to release DHCPv4 lease with UUID 3dcac056-d302-0400-3304-000004000000
Feb 14 20:14:57 MM-Home wicked[19176]: eth0            device-ready
Feb 14 20:14:57 MM-Home sddm[1078]: Running display stop script  "/usr/share/sddm/scripts/Xstop"
Feb 14 20:14:57 MM-Home kernel: e1000e: eth0 NIC Link is Down
Feb 14 20:14:57 MM-Home sddm[1078]: Removing display ":0" ...
Feb 14 20:14:57 MM-Home sddm[1078]: Display server starting...
Feb 14 20:14:57 MM-Home sddm[1078]: Running: /usr/bin/X -nolisten tcp -auth /run/sddm/{4730d862-9b76-4072-acb4-f52fe889c411} -background none -noreset -displayfd 18 vt7
Feb 14 20:14:58 MM-Home systemd-logind[962]: Failed to abandon session scope: Transport endpoint is not connected
Feb 14 20:15:01 MM-Home display-manager[19118]: Shutting down service sddm..done
Feb 14 20:15:02 MM-Home kernel: nvidia: module license 'NVIDIA' taints kernel.
Feb 14 20:15:02 MM-Home kernel: Disabling lock debugging due to kernel taint
Feb 14 20:15:02 MM-Home systemd-udevd[19366]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:02 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:02 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:02 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:02 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:02 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:02 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:02 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:02 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:02 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:02 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:02 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:02 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:02 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:02 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:02 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:02 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:02 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:02 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:02 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:02 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:02 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:02 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:02 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:02 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:02 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:02 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:02 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:02 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:02 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:02 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:02 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:02 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:02 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:02 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:02 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:02 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:02 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:02 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:02 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:02 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:02 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:02 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:02 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:02 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:02 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:02 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:03 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:03 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:03 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:03 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:03 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:03 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:03 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:03 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:03 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:03 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:03 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:03 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:03 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:03 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:03 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:03 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:03 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:03 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:03 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:03 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:03 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:03 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:03 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:03 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:03 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:03 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:03 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:03 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:03 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:03 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:03 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:03 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:03 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:03 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:03 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:03 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:03 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:03 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:03 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:03 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:03 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:03 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:03 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:03 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:03 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:03 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:03 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:03 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:03 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:03 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:03 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:03 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:03 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:03 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:03 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:03 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:03 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:03 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:03 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:03 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:03 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:03 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:03 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:03 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:03 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:03 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:03 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:03 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:03 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:03 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:03 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:03 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:03 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:03 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:03 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:03 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:03 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:03 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:03 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:03 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:03 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:03 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:03 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:03 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:03 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:03 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:03 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:03 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:03 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:03 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:03 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:03 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:03 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:03 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:03 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:03 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:03 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:03 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:03 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:03 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:03 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:03 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:03 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:03 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:03 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:03 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:03 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:03 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:03 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:03 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:03 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:03 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:03 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:03 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:03 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:03 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:03 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:03 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:03 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:03 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:03 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:03 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:03 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:03 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:03 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:03 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:03 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:03 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:03 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:03 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:03 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:03 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:03 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:03 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:03 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:03 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:03 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:03 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:03 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:03 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:03 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:03 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:03 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:03 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:03 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:04 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:04 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:04 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:04 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:04 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:04 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:04 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:04 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:04 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:04 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:04 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:04 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:04 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:04 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:04 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:04 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:04 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:04 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:04 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:04 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:04 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:04 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:04 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:04 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:04 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:04 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:04 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:04 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:04 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:04 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:04 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:04 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:04 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:04 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:04 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:04 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:04 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:04 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:04 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:04 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:04 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:04 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:04 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:04 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:04 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:04 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:04 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:04 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:04 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:04 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:04 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:04 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:04 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:04 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:04 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:04 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:04 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:04 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:04 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:04 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:04 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:04 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:04 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:04 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:04 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:04 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:04 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:04 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:04 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:04 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:04 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:04 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:04 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:04 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:04 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:04 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:04 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:04 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:04 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:04 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:04 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:04 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:04 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:04 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:04 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:04 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:04 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:04 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:04 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:04 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:04 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:04 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:04 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:04 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:04 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:04 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:04 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:04 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:04 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:04 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:04 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:04 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:04 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:04 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:04 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:04 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:04 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:04 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:04 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:04 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:04 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:04 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:04 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:04 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:04 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:04 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:04 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:04 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:04 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:04 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:04 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:04 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:04 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:04 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:04 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:04 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:04 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:04 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:04 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:04 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:04 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:04 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:04 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:04 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:04 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:04 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:04 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:04 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:04 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:05 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:05 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:05 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:05 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:05 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:05 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:05 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:05 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:05 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:05 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:05 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:05 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:05 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:05 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:05 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:05 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:05 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:05 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:05 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:05 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:05 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:05 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:05 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:05 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:05 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:05 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:05 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:05 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:05 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:05 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:05 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:05 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:05 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:05 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:05 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:05 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:05 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:05 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:05 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:05 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:05 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:05 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:05 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:05 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:05 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:05 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:05 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:05 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:05 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:05 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:05 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:05 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:05 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:05 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:05 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:05 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:05 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:05 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:05 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:05 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:05 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:05 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:05 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:05 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:05 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:05 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:05 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:05 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:05 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:05 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:05 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:05 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:05 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:05 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:05 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:05 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:05 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:05 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:05 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:05 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:05 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:05 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:05 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:05 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:05 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:05 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:05 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:05 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:05 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:05 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:05 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:05 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:05 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:05 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:05 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:05 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:05 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:05 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:05 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:05 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:05 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:05 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:05 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:05 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:05 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:05 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:05 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:05 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:05 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:05 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:05 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:05 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:05 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:05 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:05 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:05 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:05 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:05 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:05 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:05 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:05 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:05 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:05 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:05 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:05 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:05 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:05 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:05 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:05 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:05 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:05 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:05 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:05 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:05 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:05 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:05 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:05 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:05 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:05 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:06 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:06 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:06 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:06 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:06 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:06 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:06 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:06 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:06 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:06 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:06 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:06 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:06 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:06 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:06 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:06 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:06 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:06 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:06 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:06 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:06 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:06 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:06 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:06 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:06 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:06 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:06 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:06 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:06 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:06 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:06 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:06 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:06 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:06 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:06 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:06 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:06 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:06 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:06 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:06 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:06 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:06 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:06 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:06 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:06 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:06 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:06 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:06 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:06 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:06 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:06 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:06 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:06 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:06 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:06 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:06 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:06 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:06 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:06 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:06 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:06 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:06 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:06 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:06 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:06 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:06 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:06 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:06 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:06 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:06 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:06 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:06 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:06 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:06 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:06 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:06 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:06 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:06 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:06 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:06 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:06 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:06 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:06 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:06 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:06 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:06 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:06 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:06 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:06 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:06 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:06 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:06 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:06 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:06 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:06 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:06 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:06 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:06 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:06 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:06 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:06 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:06 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:06 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:06 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:06 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:06 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:06 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:06 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:06 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:06 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:06 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:06 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:06 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:06 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:06 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:06 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:06 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:06 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:06 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:06 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:06 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:06 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:06 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:06 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:06 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:06 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:06 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:06 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:06 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:06 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:06 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:06 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:06 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:06 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:06 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:06 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:06 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:06 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:06 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:06 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:06 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:06 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:06 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:06 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:06 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:07 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:07 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:07 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:07 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:07 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:07 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:07 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:07 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:07 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:07 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:07 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:07 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:07 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:07 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:07 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:07 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:07 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:07 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:07 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:07 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:07 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:07 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:07 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:07 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:07 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:07 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:07 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:07 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:07 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:07 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:07 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:07 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:07 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:07 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:07 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:07 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:07 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:07 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:07 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:07 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:07 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:07 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:07 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:07 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:07 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:07 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:07 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:07 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:07 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:07 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:07 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:07 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:07 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:07 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:07 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:07 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:07 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:07 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:07 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:07 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:07 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:07 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:07 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:07 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:07 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:07 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:07 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:07 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:07 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:07 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:07 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:07 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:07 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:07 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:07 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:07 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:07 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:07 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:07 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:07 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:07 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:07 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:07 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:07 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:07 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:07 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:07 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:07 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:07 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:07 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:07 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:07 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:07 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:07 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:07 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:07 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:07 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:07 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:07 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:07 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:07 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:07 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:07 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:07 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:07 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:07 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:07 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:07 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:07 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:07 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:07 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:07 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:07 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:07 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:07 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:07 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:07 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:07 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:07 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:07 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:07 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:07 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:07 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:07 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:07 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:07 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:07 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:07 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:07 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:07 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:07 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:07 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:07 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:07 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:07 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:07 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:07 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:07 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:07 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:07 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:07 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:07 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:07 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:07 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:07 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:08 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:08 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:08 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:08 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:08 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:08 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:08 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:08 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:08 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:08 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:08 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:08 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:08 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:08 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:08 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:08 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:08 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:08 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:08 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:08 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:08 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:08 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:08 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:08 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:08 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:08 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:08 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:08 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:08 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:08 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:08 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:08 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:08 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:08 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:08 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:08 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:08 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:08 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:08 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:08 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:08 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:08 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:08 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:08 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:08 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:08 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:08 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:08 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:08 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:08 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:08 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:08 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:08 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:08 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:08 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:08 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:08 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:08 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:08 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:08 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:08 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:08 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:08 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:08 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:08 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:08 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:08 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:08 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:08 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:08 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:08 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:08 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:08 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:08 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:08 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:08 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:08 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:08 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:08 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:08 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:08 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:08 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:08 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:08 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:08 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:08 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:08 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:08 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:08 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:08 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:08 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:08 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:08 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:08 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:08 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:08 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:08 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:08 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:08 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:08 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:08 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:08 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:08 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:08 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:08 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:08 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:08 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:08 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:08 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:08 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:08 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:08 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:08 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:08 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:08 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:08 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:08 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:08 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:08 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:08 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:08 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:08 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:08 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:08 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:08 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:08 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:08 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:08 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:08 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:08 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:08 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:08 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:08 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:09 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:09 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:09 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:09 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:09 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:09 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:09 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:09 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:09 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:09 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:09 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:09 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:09 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:09 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:09 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:09 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:09 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:09 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:09 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:09 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:09 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:09 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:09 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:09 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:09 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:09 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:09 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:09 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:09 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:09 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:09 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:09 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:09 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:09 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:09 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:09 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:09 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:09 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:09 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:09 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:09 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:09 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:09 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:09 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:09 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:09 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:09 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:09 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:09 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:09 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:09 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:09 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:09 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:09 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:09 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:09 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:09 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:09 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:09 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:09 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:09 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:09 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:09 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:09 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:09 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:09 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:09 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:09 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:09 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:09 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:09 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:09 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:09 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:09 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:09 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:09 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:09 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:09 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:09 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:09 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:09 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:09 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:09 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:09 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:09 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:09 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:09 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:09 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:09 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:09 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:09 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:09 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:09 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:09 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:09 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:09 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:09 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:09 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:09 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:09 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:09 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:09 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:09 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:09 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:09 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:09 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:09 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:09 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:09 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:09 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:09 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:09 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:09 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:09 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:09 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:09 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:09 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:09 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:09 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:09 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:09 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:09 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:09 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:09 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:09 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:09 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:09 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:09 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:09 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:09 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:09 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:09 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:09 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:09 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:09 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:09 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:09 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:09 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:09 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:10 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:10 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:10 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:10 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:10 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:10 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:10 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:10 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:10 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:10 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:10 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:10 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:10 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:10 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:10 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:10 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:10 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:10 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:10 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:10 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:10 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:10 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:10 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:10 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:10 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:10 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:10 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:10 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:10 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:10 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:10 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:10 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:10 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:10 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:10 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:10 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:10 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:10 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:10 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:10 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:10 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:10 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:10 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:10 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:10 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:10 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:10 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:10 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:10 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:10 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:10 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:10 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:10 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:10 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:10 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:10 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:10 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:10 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:10 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:10 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:10 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:10 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:10 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:10 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:10 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:10 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:10 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:10 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:10 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:10 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:10 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:10 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:10 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:10 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:10 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:10 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:10 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:10 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:10 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:10 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:10 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:10 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:10 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:10 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:10 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:10 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:10 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:10 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:10 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:10 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:10 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:10 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:10 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:10 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:10 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:10 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:10 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:10 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:10 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:10 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:10 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:10 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:10 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:10 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:10 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:10 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:10 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:10 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:10 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:10 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:10 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:10 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:10 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:10 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:10 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:10 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:10 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:10 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:10 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:10 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:10 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:10 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:10 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:10 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:10 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:10 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:10 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:10 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:10 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:10 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:10 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:10 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:10 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:10 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:10 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:10 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:10 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:10 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:10 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:10 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:10 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:10 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:10 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:10 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:10 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:10 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:10 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:10 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:10 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:10 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:10 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:10 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:10 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:10 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:10 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:10 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:10 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:11 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:11 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:11 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:11 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:11 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:11 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:11 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:11 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:11 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:11 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:11 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:11 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:11 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:11 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:11 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:11 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:11 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:11 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:11 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:11 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:11 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:11 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:11 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:11 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:11 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:11 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:11 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:11 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:11 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:11 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:11 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:11 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:11 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:11 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:11 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:11 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:11 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:11 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:11 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:11 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:11 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:11 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:11 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:11 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:11 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:11 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:11 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:11 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:11 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:11 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:11 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:11 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:11 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:11 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:11 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:11 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:11 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:11 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:11 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:11 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:11 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:11 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:11 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:11 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:11 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:11 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:11 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:11 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:11 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:11 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:11 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:11 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:11 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:11 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:11 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:11 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:11 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:11 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:11 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:11 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:11 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:11 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:11 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:11 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:11 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:11 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:11 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:11 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:11 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:11 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:11 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:11 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:11 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:11 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:11 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:11 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:11 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:11 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:11 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:11 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:11 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:11 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:11 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:11 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:11 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:11 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:11 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:11 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:11 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:11 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:11 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:11 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:11 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:11 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:11 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:11 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:11 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:11 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:11 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:11 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:11 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:11 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:11 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:11 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:11 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:11 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:11 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:11 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:11 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:11 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:11 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:11 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:11 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:11 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:11 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:11 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:11 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:11 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:11 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:11 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:11 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:11 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:11 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:11 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:11 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:12 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:12 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:12 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:12 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:12 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:12 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:12 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:12 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:12 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:12 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:12 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:12 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:12 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:12 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:12 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:12 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:12 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:12 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:12 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:12 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:12 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:12 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:12 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:12 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:12 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:12 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:12 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:12 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:12 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:12 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:12 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:12 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:12 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:12 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:12 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:12 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:12 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:12 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:12 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:12 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:12 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:12 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:12 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:12 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:12 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:12 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:12 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:12 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:12 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:12 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:12 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:12 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:12 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:12 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:12 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:12 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:12 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:12 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:12 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:12 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:12 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:12 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:12 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:12 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:12 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:12 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:12 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:12 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:12 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:12 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:12 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:12 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:12 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:12 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:12 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:12 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:12 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:12 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:12 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:12 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:12 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:12 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:12 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:12 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:12 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:12 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:12 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:12 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:12 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:12 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:12 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:12 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:12 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:12 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:12 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:12 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:12 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:12 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:12 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:12 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:12 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:12 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:12 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:12 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:12 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:12 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:12 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:12 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:12 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:12 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:12 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:12 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:12 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:12 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:12 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:12 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:12 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:12 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:12 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:12 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:12 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:12 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:12 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:12 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:12 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:12 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:12 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:12 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:12 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:12 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:12 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:12 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:12 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:12 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:12 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:12 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:12 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:12 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:12 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:12 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:12 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:12 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:12 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:12 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:12 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:12 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:12 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:12 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:12 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:12 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:12 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:12 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:12 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:12 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:12 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:12 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:12 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:13 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:13 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:13 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:13 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:13 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:13 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:13 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:13 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:13 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:13 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:13 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:13 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:13 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:13 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:13 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:13 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:13 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:13 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:13 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:13 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:13 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:13 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:13 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:13 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:13 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:13 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:13 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:13 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:13 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:13 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:13 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:13 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:13 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:13 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:13 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:13 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:13 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:13 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:13 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:13 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:13 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:13 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:13 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:13 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:13 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:13 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:13 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:13 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:13 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:13 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:13 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:13 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:13 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:13 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:13 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:13 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:13 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:13 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:13 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:13 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:13 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:13 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:13 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:13 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:13 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:13 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:13 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:13 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:13 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:13 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:13 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:13 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:13 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:13 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:13 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:13 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:13 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:13 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:13 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:13 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:13 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:13 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:13 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:13 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:13 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:13 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:13 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:13 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:13 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:13 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:13 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:13 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:13 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:13 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:13 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:13 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:13 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:13 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:13 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:13 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:13 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:13 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:13 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:13 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:13 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:13 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:13 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:13 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:13 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:13 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:13 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:13 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:13 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:13 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:13 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:13 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:13 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:13 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:13 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:13 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:13 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:13 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:13 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:13 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:13 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:13 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:13 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:13 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:13 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:13 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:13 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:13 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:13 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:13 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:13 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:13 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:13 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:13 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:13 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:13 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:13 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:13 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:13 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:13 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:13 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:13 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:13 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:13 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:13 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:13 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:13 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:13 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:13 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:13 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:13 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:13 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:13 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:13 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:13 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:13 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:13 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:13 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:13 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:13 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:13 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:13 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:13 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:13 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:13 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:13 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:13 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:13 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:13 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:13 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:13 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:14 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:14 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:14 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:14 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:14 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:14 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:14 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:14 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:14 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:14 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:14 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:14 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:14 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:14 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:14 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:14 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:14 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:14 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:14 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:14 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:14 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:14 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:14 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:14 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:14 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:14 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:14 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:14 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:14 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:14 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:14 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:14 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:14 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:14 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:14 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:14 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:14 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:14 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:14 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:14 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:14 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:14 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:14 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:14 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:14 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:14 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:14 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:14 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:14 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:14 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:14 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:14 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:14 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:14 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:14 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:14 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:14 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:14 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:14 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:14 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:14 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:14 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:14 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:14 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:14 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:14 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:14 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:14 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:14 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:14 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:14 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:14 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:14 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:14 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:14 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:14 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:14 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:14 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:14 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:14 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:14 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:14 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:14 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:14 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:14 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:14 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:14 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:14 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:14 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:14 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:14 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:14 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:14 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:14 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:14 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:14 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:14 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:14 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:14 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:14 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:14 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:14 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:14 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:14 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:14 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:14 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:14 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:14 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:14 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:14 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:14 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:14 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:14 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:14 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:14 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:14 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:14 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:14 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:14 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:14 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:14 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:14 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:14 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:14 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:14 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:14 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:14 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:14 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:14 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:14 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:14 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:14 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:14 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:14 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:14 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:14 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:14 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:14 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:14 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:14 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:14 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:14 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:14 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:14 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:14 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:15 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:15 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:15 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:15 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:15 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:15 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:15 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:15 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:15 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:15 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:15 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:15 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:15 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:15 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:15 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:15 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:15 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:15 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:15 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:15 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:15 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:15 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:15 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:15 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:15 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:15 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:15 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:15 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:15 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:15 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:15 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:15 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:15 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:15 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:15 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:15 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:15 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:15 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:15 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:15 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:15 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:15 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:15 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:15 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:15 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:15 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:15 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:15 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:15 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:15 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:15 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:15 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:15 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:15 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:15 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:15 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:15 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:15 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:15 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:15 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:15 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:15 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:15 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:15 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:15 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:15 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:15 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:15 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:15 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:15 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:15 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:15 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:15 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:15 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:15 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:15 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:15 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:15 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:15 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:15 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:15 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:15 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:15 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:15 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:15 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:15 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:15 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:15 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:15 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:15 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:15 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:15 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:15 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:15 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:15 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:15 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:15 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:15 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:15 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:15 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:15 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:15 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:15 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:15 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:15 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:15 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:15 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:15 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:15 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:15 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:15 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:15 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:15 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:15 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:15 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:15 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:15 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:15 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:15 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:15 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:15 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:15 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:15 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:15 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:15 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:15 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:15 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:15 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:15 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:15 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:15 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:15 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:15 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:15 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:15 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:15 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:15 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:15 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:15 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:15 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:15 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:15 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:15 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:15 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:15 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:15 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:15 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:15 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:15 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:15 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:15 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:15 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:15 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:15 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:15 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:15 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:15 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:16 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:16 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:16 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:16 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:16 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:16 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:16 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:16 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:16 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:16 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:16 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:16 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:16 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:16 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:16 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:16 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:16 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:16 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:16 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:16 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:16 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:16 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:16 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:16 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:16 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:16 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:16 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:16 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:16 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:16 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:16 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:16 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:16 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:16 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:16 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:16 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:16 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:16 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:16 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:16 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:16 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:16 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:16 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:16 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:16 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:16 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:16 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:16 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:16 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:16 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:16 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:16 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:16 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:16 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:16 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:16 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:16 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:16 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:16 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:16 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:16 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:16 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:16 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:16 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:16 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:16 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:16 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:16 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:16 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:16 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:16 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:16 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:16 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:16 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:16 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:16 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:16 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:16 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:16 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:16 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:16 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:16 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:16 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:16 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:16 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:16 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:16 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:16 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:16 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:16 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:16 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:16 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:16 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:16 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:16 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:16 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:16 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:16 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:16 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:16 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:16 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:16 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:16 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:16 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:16 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:16 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:16 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:16 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:16 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:16 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:16 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:16 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:16 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:16 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:16 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:16 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:16 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:16 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:16 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:16 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:16 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:16 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:16 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:16 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:16 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:16 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:16 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:16 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:16 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:16 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:16 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:16 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:16 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:16 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:16 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:16 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:16 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:16 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:16 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:16 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:16 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:16 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:16 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:16 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:16 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:17 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:17 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:17 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:17 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:17 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:17 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:17 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:17 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:17 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:17 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:17 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:17 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:17 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:17 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:17 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:17 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:17 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:17 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:17 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:17 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:17 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:17 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:17 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:17 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:17 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:17 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:17 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:17 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:17 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:17 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:17 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:17 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:17 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:17 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:17 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:17 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:17 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:17 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:17 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:17 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:17 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:17 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:17 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:17 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:17 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:17 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:17 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:17 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:17 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:17 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:17 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:17 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:17 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:17 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:17 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:17 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:17 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:17 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:17 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:17 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:17 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:17 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:17 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:17 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:17 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:17 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:17 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:17 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:17 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:17 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:17 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:17 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:17 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:17 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:17 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:17 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:17 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:17 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:17 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:17 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:17 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:17 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:17 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:17 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:17 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:17 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:17 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:17 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:17 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:17 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:17 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:17 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:17 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:17 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:17 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:17 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:17 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:17 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:17 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:17 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:17 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:17 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:17 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:17 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:17 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:17 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:17 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:17 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:17 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:17 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:17 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:17 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:17 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:17 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:17 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:17 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:17 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:17 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:17 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:17 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:17 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:17 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:17 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:17 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:17 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:17 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:17 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:17 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:17 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:17 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:17 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:17 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:17 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:17 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:17 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:17 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:17 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:17 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:17 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:17 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:17 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:17 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:17 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:17 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:17 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:17 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:17 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:17 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:17 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:17 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:17 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:17 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:17 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:17 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:17 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:17 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:17 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:18 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:18 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:18 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:18 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:18 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:18 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:18 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:18 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:18 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:18 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:18 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:18 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:18 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:18 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:18 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:18 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:18 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:18 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:18 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:18 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:18 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:18 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:18 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:18 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:18 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:18 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:18 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:18 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:18 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:18 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:18 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:18 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:18 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:18 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:18 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:18 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:18 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:18 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:18 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:18 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:18 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:18 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:18 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:18 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:18 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:18 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:18 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:18 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:18 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:18 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:18 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:18 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:18 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:18 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:18 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:18 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:18 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:18 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:18 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:18 MM-Home systemd-udevd[19366]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:18 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:18 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:18 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:18 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:18 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:18 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:18 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:18 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:18 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:18 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:18 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:18 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:18 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:18 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:18 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:18 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:18 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:18 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:18 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:18 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:18 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:18 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:18 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:18 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:18 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:18 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:18 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:18 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:18 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:18 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:18 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:18 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:18 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:18 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:18 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:18 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:18 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:18 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:18 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:18 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:18 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:18 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:18 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:18 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:18 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:18 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:18 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:18 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:18 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:18 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:18 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:18 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:18 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:18 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:18 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:18 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:18 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:18 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:18 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:18 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:18 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:18 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:18 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:18 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:18 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:18 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:18 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:18 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:18 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:18 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:18 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:18 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:18 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:18 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:18 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:18 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:18 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:18 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:18 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:18 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:18 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:18 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:18 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:18 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:18 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:18 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:18 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:18 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:18 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:18 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:18 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:19 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:19 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:19 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:19 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:19 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:19 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:19 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:19 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:19 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:19 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:19 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:19 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:19 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:19 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:19 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:19 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:19 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:19 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:19 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:19 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:19 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:19 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:19 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:19 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:19 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:19 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:19 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:19 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:19 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:19 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:19 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:19 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:19 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:19 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:19 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:19 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:19 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:19 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:19 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:19 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:19 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:19 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:19 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:19 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:19 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:19 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:19 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:19 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:19 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:19 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:19 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:19 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:19 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:19 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:19 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:19 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:19 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:19 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:19 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:19 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:19 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:19 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:19 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:19 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:19 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:19 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:19 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:19 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:19 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:19 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:19 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:19 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:19 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:19 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:19 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:19 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:19 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:19 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:19 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:19 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:19 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:19 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:19 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:19 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:19 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:19 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:19 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:19 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:19 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:19 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:19 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:19 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:19 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:19 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:19 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:19 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:19 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:19 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:19 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:19 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:19 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:19 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:19 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:19 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:19 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:19 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:19 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:19 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:19 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:19 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:19 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:19 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:19 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:19 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:19 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:19 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:19 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:19 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:19 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:19 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:19 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:19 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:19 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:19 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:19 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:19 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:19 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:19 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:19 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:19 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:19 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:19 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:19 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:19 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:19 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:19 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:19 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:19 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:19 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:19 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:19 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:19 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:19 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:19 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:19 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:19 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:19 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:19 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:19 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:19 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:19 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:19 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:19 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:19 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:19 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:19 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:19 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:20 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:20 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:20 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:20 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:20 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:20 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:20 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:20 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:20 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:20 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:20 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:20 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:20 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:20 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:20 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:20 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:20 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:20 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:20 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:20 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:20 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:20 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:20 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:20 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:20 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:20 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:20 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:20 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:20 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:20 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:20 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:20 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:20 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:20 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:20 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:20 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:20 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:20 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:20 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:20 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:20 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:20 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:20 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:20 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:20 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:20 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:20 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:20 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:20 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:20 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:20 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:20 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:20 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:20 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:20 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:20 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:20 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:20 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:20 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:20 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:20 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:20 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:20 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:20 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:20 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:20 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:20 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:20 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:20 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:20 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:20 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:20 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:20 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:20 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:20 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:20 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:20 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:20 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:20 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:20 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:20 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:20 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:20 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:20 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:20 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:20 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:20 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:20 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:20 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:20 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:20 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:20 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:20 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:20 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:20 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:20 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:20 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:20 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:20 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:20 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:20 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:20 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:20 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:20 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:20 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:20 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:20 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:20 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:20 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:20 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:20 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:20 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:20 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:20 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:20 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:20 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:20 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:20 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:20 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:20 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:20 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:20 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:20 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:20 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:20 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:20 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:20 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:20 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:20 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:20 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:20 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:20 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:20 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:20 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:20 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:20 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:20 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:20 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:20 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:20 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:20 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:20 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:20 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:20 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:20 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:20 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:20 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:20 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:20 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:20 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:20 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:20 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:20 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:20 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:20 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:20 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:20 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:21 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:21 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:21 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:21 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:21 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:21 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:21 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:21 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:21 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:21 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:21 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:21 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:21 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:21 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:21 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:21 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:21 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:21 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:21 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:21 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:21 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:21 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:21 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:21 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:21 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:21 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:21 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:21 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:21 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:21 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:21 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:21 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:21 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:21 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:21 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:21 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:21 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:21 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:21 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:21 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:21 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:21 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:21 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:21 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:21 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:21 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:21 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:21 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:21 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:21 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:21 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:21 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:21 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:21 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:21 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:21 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:21 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:21 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:21 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:21 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:21 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:21 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:21 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:21 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:21 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:21 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:21 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:21 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:21 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:21 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:21 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:21 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:21 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:21 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:21 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:21 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:21 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:21 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:21 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:21 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:21 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:21 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:21 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:21 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:21 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:21 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:21 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:21 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:21 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:21 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:21 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:21 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:21 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:21 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:21 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:21 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:21 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:21 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:21 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:21 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:21 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:21 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:21 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:21 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:21 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:21 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:21 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:21 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:21 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:21 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:21 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:21 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:21 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:21 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:21 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:21 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:21 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:21 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:21 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:21 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:21 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:21 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:21 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:21 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:21 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:21 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:21 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:21 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:21 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:21 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:21 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:21 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:21 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:21 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:21 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:21 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:21 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:21 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:21 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:21 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:21 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:21 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:21 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:21 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:21 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:21 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:21 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:21 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:21 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:21 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:21 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:21 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:21 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:21 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:21 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:21 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:21 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:21 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:21 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:21 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:21 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:21 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:21 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:22 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:22 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:22 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:22 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:22 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:22 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:22 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:22 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:22 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:22 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:22 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:22 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:22 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:22 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:22 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:22 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:22 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:22 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:22 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:22 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:22 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:22 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:22 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:22 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:22 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:22 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:22 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:22 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:22 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:22 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:22 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:22 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:22 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:22 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:22 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:22 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:22 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:22 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:22 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:22 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:22 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:22 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:22 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:22 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:22 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:22 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:22 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:22 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:22 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:22 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:22 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:22 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:22 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:22 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:22 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:22 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:22 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:22 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:22 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:22 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:22 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:22 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:22 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:22 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:22 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:22 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:22 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:22 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:22 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:22 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:22 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:22 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:22 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:22 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:22 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:22 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:22 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:22 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:22 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:22 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:22 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:22 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:22 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:22 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:22 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:22 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:22 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:22 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:22 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:22 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:22 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:22 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:22 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:22 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:22 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:22 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:22 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:22 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:22 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:22 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:22 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:22 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:22 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:22 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:22 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:22 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:22 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:22 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:22 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:22 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:22 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:22 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:22 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:22 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:22 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:22 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:22 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:22 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:22 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:22 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:22 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:22 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:22 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:22 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:22 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:22 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:22 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:22 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:22 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:22 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:22 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:22 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:22 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:22 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:22 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:22 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:22 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:22 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:22 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:22 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:22 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:22 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:22 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:22 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:22 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:22 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:22 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:22 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:22 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:22 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:22 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:22 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:22 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:22 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:22 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:22 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:22 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:23 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:23 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:23 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:23 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:23 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:23 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:23 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:23 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:23 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:23 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:23 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:23 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:23 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:23 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:23 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:23 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:23 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:23 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:23 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:23 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:23 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:23 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:23 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:23 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:23 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:23 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:23 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:23 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:23 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:23 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:23 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:23 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:23 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:23 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:23 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:23 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:23 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:23 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:23 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:23 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:23 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:23 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:23 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:23 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:23 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:23 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:23 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:23 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:23 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:23 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:23 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:23 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:23 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:23 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:23 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:23 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:23 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:23 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:23 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:23 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:23 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:23 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:23 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:23 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:23 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:23 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:23 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:23 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:23 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:23 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:23 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:23 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:23 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:23 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:23 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:23 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:23 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:23 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:23 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:23 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:23 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:23 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:23 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:23 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:23 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:23 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:23 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:23 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:23 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:23 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:23 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:23 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:23 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:23 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:23 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:23 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:23 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:23 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:23 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:23 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:23 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:23 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:23 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:23 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:23 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:23 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:23 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:23 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:23 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:23 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:23 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:23 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:23 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:23 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:23 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:23 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:23 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:23 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:23 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:23 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:23 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:23 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:23 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:23 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:23 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:23 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:23 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:23 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:23 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:23 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:23 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:23 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:23 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:23 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:23 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:23 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:23 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:23 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:23 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:24 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:24 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:24 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:24 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:24 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:24 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:24 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:24 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:24 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:24 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:24 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:24 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:24 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:24 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:24 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:24 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:24 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:24 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:24 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:24 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:24 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:24 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:24 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:24 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:24 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:24 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:24 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:24 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:24 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:24 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:24 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:24 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:24 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:24 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:24 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:24 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:24 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:24 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:24 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:24 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:24 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:24 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:24 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:24 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:24 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:24 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:24 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:24 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:24 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:24 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:24 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:24 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:24 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:24 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:24 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:24 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:24 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:24 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:24 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:24 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:24 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:24 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:24 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:24 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:24 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:24 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:24 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:24 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:24 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:24 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:24 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:24 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:24 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:24 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:24 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:24 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:24 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:24 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:24 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:24 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:24 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:24 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:24 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:24 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:24 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:24 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:24 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:24 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:24 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:24 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:24 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:24 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:24 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:24 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:24 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:24 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:24 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:24 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:24 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:24 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:24 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:24 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:24 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:24 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:24 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:24 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:24 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:24 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:24 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:24 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:24 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:24 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:24 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:24 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:24 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:24 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:24 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:24 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:24 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:24 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:24 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:24 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:24 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:24 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:24 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:24 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:24 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:24 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:24 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:24 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:24 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:24 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:24 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:24 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:24 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:24 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:24 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:24 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:24 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:24 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:24 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:24 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:24 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:24 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:24 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:24 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:24 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:24 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:24 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:24 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:24 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:24 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:24 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:24 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:24 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:24 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:24 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:25 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:25 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:25 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:25 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:25 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:25 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:25 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:25 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:25 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:25 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:25 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:25 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:25 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:25 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:25 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:25 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:25 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:25 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:25 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:25 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:25 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:25 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:25 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:25 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:25 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:25 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:25 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:25 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:25 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:25 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:25 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:25 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:25 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:25 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:25 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:25 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:25 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:25 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:25 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:25 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:25 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:25 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:25 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:25 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:25 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:25 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:25 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:25 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:25 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:25 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:25 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:25 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:25 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:25 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:25 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:25 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:25 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:25 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:25 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:25 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:25 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:25 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:25 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:25 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:25 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:25 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:25 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:25 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:25 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:25 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:25 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:25 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:25 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:25 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:25 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:25 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:25 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:25 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:25 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:25 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:25 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:25 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:25 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:25 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:25 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:25 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:25 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:25 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:25 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:25 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:25 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:25 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:25 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:25 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:25 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:25 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:25 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:25 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:25 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:25 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:25 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:25 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:25 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:25 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:25 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:25 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:25 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:25 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:25 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:25 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:25 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:25 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:25 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:25 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:25 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:25 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:25 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:25 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:25 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:25 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:25 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:25 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:25 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:25 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:25 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:25 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:25 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:25 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:25 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:25 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:25 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:25 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:25 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:25 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:25 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:25 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:25 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:25 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:25 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:26 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:26 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:26 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:26 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:26 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:26 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:26 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:26 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:26 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:26 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:26 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:26 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:26 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:26 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:26 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:26 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:26 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:26 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:26 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:26 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:26 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:26 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:26 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:26 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:26 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:26 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:26 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:26 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:26 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:26 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:26 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:26 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:26 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:26 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:26 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:26 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:26 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:26 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:26 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:26 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:26 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:26 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:26 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:26 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:26 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:26 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:26 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:26 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:26 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:26 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:26 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:26 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:26 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:26 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:26 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:26 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:26 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:26 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:26 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:26 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:26 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:26 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:26 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:26 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:26 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:26 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:26 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:26 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:26 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:26 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:26 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:26 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:26 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:26 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:26 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:26 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:26 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:26 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:26 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:26 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:26 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:26 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:26 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:26 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:26 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:26 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:26 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:26 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:26 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:26 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:26 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:26 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:26 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:26 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:26 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:26 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:26 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:26 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:26 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:26 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:26 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:26 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:26 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:26 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:26 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:26 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:26 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:26 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:26 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:26 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:26 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:26 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:26 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:26 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:26 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:26 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:26 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:26 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:26 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:26 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:26 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:26 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:26 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:26 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:26 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:26 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:26 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:26 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:26 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:26 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:26 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:26 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:26 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:26 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:26 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:26 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:26 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:26 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:26 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:27 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:27 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:27 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:27 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:27 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:27 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:27 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:27 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:27 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:27 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:27 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:27 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:27 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:27 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:27 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:27 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:27 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:27 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:27 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:27 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:27 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:27 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:27 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:27 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:27 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:27 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:27 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:27 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:27 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:27 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:27 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:27 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:27 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:27 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:27 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:27 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:27 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:27 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:27 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:27 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:27 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:27 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:27 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:27 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:27 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:27 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:27 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:27 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:27 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:27 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:27 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:27 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:27 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:27 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:27 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:27 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:27 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:27 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:27 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:27 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:27 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:27 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:27 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:27 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:27 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:27 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:27 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:27 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:27 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:27 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:27 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:27 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:27 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:27 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:27 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:27 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:27 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:27 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:27 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:27 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:27 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:27 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:27 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:27 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:27 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:27 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:27 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:27 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:27 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:27 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:27 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:27 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:27 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:27 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:27 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:27 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:27 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:27 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:27 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:27 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:27 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:27 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:27 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:27 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:27 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:27 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:27 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:27 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:27 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:27 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:27 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:27 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:27 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:27 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:27 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:27 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:27 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:27 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:27 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:27 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:27 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:27 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:27 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:27 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:27 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:27 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:27 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:27 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:27 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:27 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:27 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:27 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:27 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:27 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:27 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:27 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:27 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:27 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:27 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:27 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:27 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:27 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:27 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:27 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:27 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:27 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:27 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:27 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:27 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:27 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:27 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:27 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:27 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:27 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:27 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:27 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:27 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:27 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:27 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:27 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:27 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:27 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:27 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:28 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:28 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:28 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:28 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:28 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:28 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:28 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:28 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:28 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:28 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:28 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:28 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:28 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:28 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:28 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:28 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:28 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:28 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:28 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:28 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:28 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:28 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:28 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:28 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:28 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:28 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:28 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:28 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:28 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:28 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:28 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:28 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:28 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:28 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:28 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:28 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:28 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:28 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:28 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:28 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:28 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:28 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:28 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:28 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:28 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:28 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:28 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:28 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:28 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:28 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:28 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:28 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:28 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:28 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:28 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:28 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:28 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:28 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:28 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:28 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:28 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:28 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:28 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:28 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:28 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:28 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:28 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:28 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:28 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:28 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:28 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:28 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:28 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:28 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:28 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:28 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:28 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:28 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:28 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:28 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:28 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:28 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:28 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:28 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:28 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:28 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:28 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:28 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:28 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:28 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:28 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:28 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:28 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:28 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:28 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:28 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:28 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:28 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:28 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:28 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:28 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:28 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:28 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:28 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:28 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:28 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:28 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:28 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:28 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:28 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:28 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:28 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:28 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:28 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:28 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:28 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:28 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:28 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:28 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:28 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:28 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:28 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:28 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:28 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:28 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:28 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:28 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:28 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:28 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:28 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:28 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:28 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:28 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:28 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:28 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:28 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:28 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:28 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:28 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:28 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:28 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:28 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:28 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:28 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:28 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:29 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:29 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:29 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:29 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:29 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:29 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:29 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:29 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:29 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:29 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:29 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:29 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:29 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:29 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:29 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:29 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:29 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:29 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:29 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:29 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:29 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:29 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:29 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:29 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:29 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:29 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:29 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:29 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:29 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:29 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:29 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:29 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:29 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:29 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:29 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:29 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:29 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:29 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:29 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:29 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:29 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:29 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:29 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:29 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:29 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:29 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:29 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:29 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:29 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:29 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:29 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:29 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:29 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:29 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:29 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:29 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:29 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:29 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:29 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:29 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:29 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:29 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:29 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:29 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:29 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:29 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:29 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:29 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:29 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:29 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:29 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:29 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:29 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:29 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:29 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:29 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:29 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:29 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:29 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:29 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:29 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:29 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:29 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:29 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:29 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:29 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:29 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:29 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:29 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:29 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:29 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:29 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:29 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:29 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:29 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:29 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:29 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:29 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:29 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:29 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:29 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:29 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:29 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:29 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:29 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:29 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:29 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:29 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:29 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:29 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:29 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:29 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:29 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:29 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:29 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:29 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:29 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:29 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:29 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:29 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:29 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:29 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:29 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:29 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:29 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:29 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:29 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:29 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:29 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:29 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:29 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:29 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:29 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:29 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:29 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:29 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:29 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:29 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:29 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:29 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:29 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:29 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:29 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:29 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:29 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:29 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:29 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:29 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:29 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:29 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:29 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:29 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:29 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:29 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:29 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:29 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:29 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:30 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:30 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:30 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:30 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:30 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:30 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:30 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:30 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:30 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:30 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:30 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:30 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:30 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:30 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:30 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:30 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:30 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:30 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:30 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:30 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:30 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:30 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:30 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:30 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:30 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:30 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:30 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:30 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:30 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:30 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:30 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:30 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:30 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:30 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:30 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:30 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:30 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:30 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:30 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:30 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:30 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:30 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:30 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:30 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:30 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:30 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:30 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:30 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:30 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:30 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:30 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:30 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:30 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:30 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:30 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:30 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:30 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:30 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:30 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:30 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:30 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:30 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:30 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:30 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:30 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:30 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:30 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:30 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:30 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:30 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:30 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:30 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:30 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:30 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:30 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:30 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:30 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:30 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:30 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:30 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:30 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:30 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:30 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:30 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:30 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:30 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:30 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:30 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:30 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:30 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:30 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:30 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:30 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:30 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:30 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:30 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:30 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:30 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:30 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:30 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:30 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:30 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:30 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:30 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:30 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:30 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:30 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:30 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:30 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:30 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:30 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:30 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:30 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:30 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:30 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:30 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:30 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:30 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:30 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:30 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:30 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:30 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:30 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:30 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:30 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:30 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:30 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:30 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:30 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:30 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:30 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:30 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:30 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:30 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:30 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:30 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:30 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:30 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:30 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:30 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:30 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:30 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:30 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:30 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:30 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:30 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:30 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:30 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:30 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:30 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:30 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:30 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:30 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:30 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:30 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:30 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:30 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:31 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:31 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:31 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:31 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:31 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:31 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:31 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:31 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:31 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:31 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:31 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:31 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:31 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:31 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:31 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:31 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:31 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:31 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:31 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:31 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:31 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:31 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:31 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:31 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:31 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:31 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:31 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:31 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:31 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:31 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:31 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:31 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:31 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:31 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:31 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:31 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:31 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:31 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:31 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:31 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:31 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:31 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:31 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:31 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:31 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:31 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:31 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:31 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:31 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:31 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:31 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:31 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:31 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:31 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:31 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:31 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:31 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:31 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:31 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:31 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:31 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:31 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:31 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:31 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:31 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:31 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:31 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:31 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:31 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:31 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:31 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:31 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:31 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:31 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:31 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:31 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:31 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:31 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:31 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:31 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:31 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:31 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:31 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:31 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:31 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:31 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:31 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:31 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:31 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:31 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:31 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:31 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:31 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:31 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:31 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:31 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:31 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:31 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:31 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:31 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:31 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:31 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:31 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:31 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:31 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:31 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:31 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:31 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:31 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:31 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:31 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:31 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:31 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:31 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:31 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:31 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:31 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:31 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:31 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:31 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:31 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:31 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:31 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:31 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:31 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:31 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:31 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:31 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:31 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:31 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:31 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:31 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:31 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:31 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:31 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:31 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:31 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:31 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:31 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:31 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:31 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:31 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:31 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:31 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:31 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:31 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:31 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:31 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:31 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:31 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:31 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:31 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:31 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:31 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:31 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:31 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:31 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:32 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:32 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:32 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:32 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:32 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:32 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:32 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:32 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:32 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:32 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:32 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:32 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:32 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:32 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:32 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:32 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:32 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:32 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:32 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:32 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:32 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:32 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:32 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:32 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:32 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:32 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:32 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:32 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:32 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:32 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:32 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:32 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:32 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:32 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:32 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:32 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:32 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:32 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:32 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:32 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:32 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:32 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:32 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:32 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:32 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:32 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:32 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:32 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:32 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:32 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:32 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:32 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:32 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:32 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:32 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:32 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:32 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:32 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:32 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:32 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:32 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:32 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:32 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:32 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:32 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:32 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:32 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:32 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:32 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:32 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:32 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:32 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:32 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:32 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:32 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:32 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:32 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:32 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:32 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:32 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:32 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:32 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:32 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:32 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:32 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:32 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:32 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:32 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:32 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:32 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:32 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:32 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:32 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:32 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:32 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:32 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:32 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:32 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:32 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:32 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:32 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:32 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:32 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:32 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:32 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:32 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:32 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:32 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:32 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:32 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:32 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:32 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:32 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:32 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:32 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:32 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:32 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:32 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:32 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:32 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:32 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:32 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:32 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:32 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:32 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:32 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:32 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:32 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:32 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:32 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:32 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:32 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:32 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:32 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:32 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:32 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:32 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:32 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:32 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:32 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:32 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:32 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:32 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:32 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:32 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:33 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:33 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:33 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:33 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:33 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:33 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:33 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:33 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:33 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:33 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:33 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:33 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:33 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:33 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:33 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:33 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:33 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:33 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:33 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:33 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:33 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:33 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:33 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:33 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:33 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:33 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:33 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:33 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:33 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:33 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:33 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:33 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:33 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:33 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:33 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:33 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:33 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:33 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:33 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:33 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:33 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:33 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:33 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:33 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:33 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:33 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:33 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:33 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:33 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:33 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:33 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:33 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:33 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:33 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:33 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:33 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:33 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:33 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:33 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:33 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:33 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:33 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:33 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:33 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:33 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:33 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:33 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:33 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:33 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:33 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:33 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:33 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:33 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:33 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:33 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:33 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:33 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:33 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:33 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:33 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:33 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:33 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:33 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:33 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:33 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:33 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:33 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:33 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:33 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:33 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:33 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:33 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:33 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:33 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:33 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:33 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:33 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:33 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:33 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:33 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:33 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:33 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:33 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:33 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:33 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:33 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:33 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:33 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:33 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:33 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:33 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:33 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:33 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:33 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:33 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:33 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:33 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:33 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:33 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:33 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:33 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:33 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:33 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:33 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:33 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:33 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:33 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:33 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:33 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:33 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:33 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:33 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:33 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:33 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:33 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:33 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:33 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:33 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:33 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:33 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:33 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:33 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:33 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:33 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:33 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:33 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:33 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:33 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:33 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:33 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:33 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:33 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:33 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:33 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:33 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:33 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:33 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:34 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:34 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:34 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:34 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:34 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:34 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:34 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:34 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:34 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:34 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:34 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:34 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:34 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:34 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:34 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:34 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:34 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:34 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:34 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:34 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:34 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:34 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:34 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:34 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:34 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:34 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:34 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:34 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:34 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:34 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:34 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:34 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:34 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:34 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:34 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:34 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:34 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:34 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:34 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:34 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:34 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:34 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:34 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:34 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:34 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:34 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:34 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:34 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:34 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:34 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:34 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:34 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:34 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:34 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:34 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:34 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:34 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:34 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:34 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:34 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:34 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:34 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:34 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:34 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:34 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:34 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:34 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:34 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:34 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:34 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:34 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:34 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:34 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:34 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:34 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:34 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:34 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:34 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:34 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:34 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:34 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:34 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:34 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:34 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:34 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:34 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:34 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:34 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:34 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:34 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:34 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:34 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:34 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:34 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:34 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:34 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:34 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:34 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:34 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:34 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:34 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:34 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:34 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:34 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:34 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:34 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:34 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:34 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:34 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:34 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:34 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:34 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:34 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:34 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:34 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:34 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:34 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:34 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:34 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:34 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:34 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:34 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:34 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:34 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:34 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:34 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:34 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:34 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:34 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:34 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:34 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:34 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:34 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:34 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:34 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:34 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:34 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:34 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:34 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:34 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:34 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:34 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:34 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:34 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:34 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:35 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:35 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:35 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:35 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:35 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:35 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:35 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:35 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:35 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:35 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:35 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:35 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:35 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:35 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:35 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:35 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:35 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:35 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:35 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:35 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:35 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:35 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:35 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:35 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:35 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:35 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:35 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:35 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:35 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:35 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:35 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:35 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:35 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:35 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:35 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:35 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:35 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:35 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:35 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:35 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:35 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:35 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:35 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:35 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:35 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:35 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:35 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:35 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:35 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:35 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:35 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:35 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:35 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:35 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:35 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:35 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:35 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:35 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:35 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:35 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:35 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:35 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:35 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:35 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:35 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:35 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:35 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:35 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:35 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:35 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:35 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:35 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:35 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:35 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:35 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:35 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:35 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:35 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:35 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:35 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:35 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:35 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:35 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:35 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:35 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:35 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:35 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:35 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:35 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:35 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:35 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:35 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:35 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:35 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:35 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:35 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:35 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:35 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:35 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:35 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:35 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:35 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:35 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:35 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:35 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:35 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:35 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:35 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:35 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:35 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:35 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:35 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:35 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:35 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:35 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:35 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:35 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:35 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:35 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:35 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:35 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:35 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:35 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:35 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:35 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:35 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:35 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:35 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:35 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:35 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:35 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:35 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:35 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:35 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:35 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:35 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:35 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:35 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:35 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:35 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:35 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:35 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:35 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:35 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:35 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:36 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:36 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:36 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:36 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:36 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:36 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:36 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:36 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:36 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:36 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:36 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:36 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:36 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:36 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:36 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:36 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:36 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:36 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:36 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:36 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:36 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:36 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:36 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:36 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:36 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:36 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:36 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:36 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:36 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:36 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:36 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:36 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:36 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:36 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:36 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:36 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:36 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:36 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:36 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:36 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:36 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:36 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:36 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:36 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:36 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:36 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:36 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:36 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:36 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:36 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:36 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:36 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:36 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:36 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:36 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:36 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:36 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:36 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:36 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:36 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:36 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:36 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:36 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:36 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:36 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:36 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:36 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:36 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:36 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:36 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:36 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:36 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:36 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:36 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:36 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:36 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:36 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:36 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:36 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:36 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:36 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:36 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:36 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:36 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:36 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:36 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:36 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:36 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:36 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:36 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:36 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:36 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:36 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:36 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:36 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:36 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:36 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:36 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:36 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:36 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:36 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:36 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:36 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:36 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:36 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:36 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:36 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:36 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:36 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:36 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:36 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:36 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:36 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:36 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:36 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:36 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:36 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:36 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:36 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:36 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:36 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:36 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:36 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:36 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:36 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:36 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:36 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:36 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:36 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:36 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:36 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:36 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:36 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:36 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:36 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:36 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:36 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:36 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:36 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:36 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:36 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:36 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:36 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:36 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:36 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:36 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:36 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:36 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:36 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:36 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:36 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:37 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:37 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:37 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:37 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:37 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:37 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:37 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:37 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:37 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:37 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:37 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:37 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:37 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:37 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:37 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:37 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:37 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:37 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:37 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:37 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:37 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:37 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:37 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:37 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:37 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:37 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:37 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:37 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:37 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:37 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:37 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:37 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:37 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:37 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:37 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:37 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:37 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:37 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:37 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:37 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:37 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:37 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:37 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:37 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:37 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:37 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:37 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:37 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:37 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:37 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:37 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:37 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:37 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:37 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:37 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:37 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:37 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:37 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:37 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:37 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:37 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:37 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:37 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:37 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:37 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:37 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:37 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:37 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:37 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:37 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:37 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:37 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:37 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:37 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:37 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:37 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:37 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:37 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:37 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:37 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:37 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:37 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:37 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:37 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:37 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:37 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:37 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:37 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:37 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:37 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:37 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:37 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:37 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:37 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:37 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:37 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:37 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:37 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:37 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:37 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:37 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:37 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:37 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:37 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:37 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:37 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:37 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:37 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:37 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:37 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:37 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:37 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:37 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:37 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:37 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:37 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:37 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:37 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:37 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:37 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:37 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:37 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:37 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:37 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:37 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:37 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:37 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:37 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:37 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:37 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:37 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:37 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:37 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:37 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:37 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:37 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:37 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:37 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:37 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:37 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:37 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:37 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:37 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:37 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:37 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:37 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:37 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:37 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:37 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:37 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:37 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:37 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:37 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:37 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:37 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:37 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:37 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:37 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:37 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:37 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:37 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:37 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:37 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:38 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:38 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:38 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:38 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:38 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:38 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:38 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:38 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:38 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:38 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:38 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:38 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:38 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:38 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:38 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:38 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:38 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:38 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:38 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:38 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:38 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:38 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:38 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:38 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:38 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:38 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:38 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:38 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:38 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:38 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:38 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:38 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:38 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:38 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:38 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:38 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:38 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:38 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:38 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:38 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:38 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:38 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:38 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:38 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:38 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:38 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:38 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:38 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:38 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:38 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:38 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:38 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:38 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:38 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:38 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:38 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:38 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:38 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:38 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:38 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:38 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:38 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:38 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:38 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:38 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:38 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:38 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:38 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:38 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:38 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:38 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:38 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:38 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:38 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:38 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:38 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:38 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:38 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:38 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:38 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:38 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:38 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:38 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:38 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:38 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:38 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:38 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:38 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:38 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:38 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:38 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:38 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:38 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:38 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:38 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:38 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:38 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:38 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:38 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:38 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:38 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:38 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:38 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:38 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:38 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:38 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:38 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:38 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:38 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:38 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:38 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:38 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:38 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:38 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:38 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:38 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:38 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:38 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:38 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:38 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:38 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:38 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:38 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:38 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:38 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:38 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:38 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:38 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:38 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:38 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:38 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:38 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:38 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:38 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:38 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:38 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:38 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:38 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:38 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:38 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:38 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:38 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:38 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:38 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:38 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:38 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:39 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:39 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:39 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:39 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:39 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:39 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:39 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:39 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:39 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:39 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:39 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:39 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:39 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:39 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:39 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:39 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:39 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:39 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:39 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:39 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:39 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:39 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:39 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:39 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:39 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:39 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:39 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:39 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:39 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:39 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:39 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:39 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:39 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:39 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:39 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:39 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:39 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:39 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:39 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:39 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:39 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:39 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:39 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:39 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:39 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:39 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:39 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:39 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:39 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:39 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:39 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:39 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:39 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:39 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:39 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:39 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:39 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:39 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:39 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:39 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:39 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:39 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:39 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:39 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:39 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:39 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:39 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:39 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:39 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:39 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:39 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:39 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:39 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:39 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:39 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:39 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:39 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:39 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:39 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:39 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:39 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:39 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:39 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:39 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:39 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:39 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:39 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:39 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:39 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:39 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:39 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:39 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:39 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:39 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:39 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:39 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:39 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:39 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:39 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:39 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:39 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:39 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:39 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:39 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:39 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:39 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:39 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:39 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:39 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:39 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:39 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:39 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:39 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:39 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:39 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:39 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:39 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:39 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:39 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:39 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:39 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:39 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:39 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:39 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:39 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:39 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:39 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:39 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:39 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:39 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:39 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:39 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:39 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:39 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:39 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:39 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:39 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:39 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:39 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:39 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:39 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:39 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:39 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:39 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:39 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:39 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:39 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:39 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:39 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:39 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:39 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:39 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:39 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:39 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:39 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:39 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:40 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:40 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:40 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:40 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:40 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:40 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:40 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:40 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:40 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:40 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:40 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:40 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:40 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:40 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:40 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:40 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:40 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:40 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:40 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:40 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:40 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:40 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:40 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:40 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:40 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:40 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:40 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:40 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:40 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:40 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:40 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:40 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:40 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:40 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:40 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:40 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:40 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:40 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:40 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:40 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:40 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:40 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:40 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:40 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:40 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:40 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:40 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:40 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:40 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:40 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:40 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:40 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:40 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:40 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:40 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:40 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:40 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:40 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:40 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:40 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:40 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:40 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:40 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:40 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:40 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:40 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:40 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:40 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:40 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:40 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:40 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:40 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:40 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:40 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:40 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:40 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:40 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:40 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:40 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:40 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:40 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:40 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:40 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:40 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:40 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:40 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:40 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:40 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:40 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:40 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:40 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:40 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:40 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:40 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:40 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:40 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:40 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:40 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:40 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:40 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:40 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:40 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:40 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:40 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:40 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:40 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:40 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:40 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:40 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:40 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:40 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:40 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:40 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:40 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:40 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:40 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:40 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:40 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:40 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:40 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:40 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:40 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:40 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:40 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:40 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:40 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:40 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:40 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:40 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:40 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:40 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:40 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:40 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:40 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:40 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:40 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:40 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:40 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:40 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:40 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:40 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:40 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:40 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:40 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:40 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:40 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:40 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:40 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:40 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:40 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:40 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:41 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:41 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:41 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:41 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:41 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:41 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:41 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:41 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:41 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:41 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:41 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:41 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:41 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:41 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:41 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:41 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:41 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:41 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:41 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:41 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:41 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:41 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:41 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:41 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:41 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:41 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:41 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:41 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:41 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:41 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:41 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:41 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:41 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:41 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:41 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:41 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:41 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:41 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:41 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:41 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:41 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:41 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:41 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:41 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:41 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:41 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:41 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:41 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:41 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:41 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:41 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:41 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:41 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:41 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:41 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:41 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:41 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:41 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:41 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:41 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:41 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:41 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:41 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:41 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:41 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:41 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:41 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:41 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:41 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:41 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:41 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:41 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:41 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:41 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:41 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:41 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:41 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:41 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:41 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:41 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:41 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:41 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:41 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:41 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:41 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:41 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:41 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:41 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:41 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:41 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:41 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:41 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:41 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:41 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:41 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:41 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:41 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:41 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:41 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:41 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:41 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:41 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:41 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:41 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:41 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:41 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:41 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:41 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:41 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:41 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:41 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:41 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:41 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:41 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:41 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:41 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:41 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:41 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:41 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:41 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:41 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:41 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:41 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:41 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:41 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:41 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:41 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:41 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:41 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:41 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:41 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:41 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:41 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:41 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:41 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:41 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:41 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:41 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:41 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:41 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:41 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:41 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:41 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:41 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:41 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:41 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:41 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:41 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:41 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:41 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:41 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:41 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:41 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:41 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:41 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:41 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:41 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:42 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:42 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:42 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:42 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:42 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:42 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:42 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:42 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:42 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:42 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:42 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:42 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:42 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:42 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:42 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:42 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:42 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:42 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:42 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:42 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:42 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:42 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:42 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:42 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:42 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:42 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:42 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:42 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:42 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:42 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:42 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:42 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:42 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:42 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:42 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:42 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:42 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:42 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:42 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:42 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:42 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:42 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:42 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:42 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:42 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:42 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:42 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:42 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:42 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:42 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:42 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:42 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:42 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:42 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:42 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:42 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:42 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:42 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:42 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:42 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:42 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:42 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:42 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:42 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:42 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:42 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:42 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:42 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:42 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:42 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:42 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:42 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:42 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:42 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:42 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:42 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:42 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:42 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:42 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:42 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:42 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:42 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:42 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:42 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:42 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:42 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:42 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:42 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:42 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:42 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:42 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:42 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:42 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:42 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:42 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:42 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:42 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:42 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:42 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:42 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:42 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:42 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:42 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:42 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:42 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:42 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:42 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:42 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:42 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:42 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:42 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:42 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:42 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:42 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:42 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:42 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:42 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:42 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:42 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:42 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:42 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:42 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:42 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:42 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:42 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:42 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:42 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:42 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:42 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:42 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:42 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:42 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:42 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:42 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:42 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:42 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:42 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:42 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:42 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:42 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:42 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:42 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:42 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:42 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:42 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:42 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:42 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:42 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:42 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:42 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:42 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:43 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:43 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:43 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:43 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:43 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:43 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:43 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:43 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:43 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:43 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:43 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:43 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:43 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:43 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:43 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:43 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:43 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:43 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:43 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:43 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:43 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:43 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:43 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:43 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:43 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:43 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:43 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:43 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:43 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:43 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:43 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:43 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:43 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:43 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:43 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:43 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:43 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:43 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:43 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:43 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:43 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:43 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:43 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:43 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:43 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:43 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:43 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:43 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:43 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:43 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:43 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:43 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:43 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:43 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:43 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:43 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:43 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:43 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:43 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:43 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:43 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:43 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:43 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:43 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:43 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:43 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:43 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:43 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:43 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:43 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:43 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:43 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:43 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:43 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:43 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:43 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:43 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:43 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:43 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:43 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:43 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:43 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:43 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:43 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:43 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:43 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:43 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:43 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:43 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:43 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:43 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:43 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:43 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:43 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:43 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:43 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:43 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:43 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:43 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:43 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:43 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:43 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:43 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:43 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:43 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:43 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:43 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:43 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:43 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:43 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:43 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:43 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:43 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:43 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:43 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:43 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:43 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:43 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:43 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:43 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:43 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:43 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:43 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:43 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:43 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:43 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:43 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:43 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:43 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:43 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:43 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:43 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:43 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:44 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:44 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:44 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:44 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:44 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:44 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:44 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:44 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:44 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:44 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:44 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:44 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:44 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:44 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:44 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:44 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:44 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:44 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:44 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:44 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:44 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:44 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:44 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:44 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:44 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:44 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:44 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:44 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:44 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:44 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:44 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:44 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:44 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:44 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:44 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:44 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:44 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:44 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:44 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:44 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:44 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:44 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:44 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:44 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:44 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:44 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:44 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:44 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:44 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:44 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:44 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:44 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:44 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:44 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:44 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:44 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:44 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:44 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:44 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:44 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:44 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:44 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:44 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:44 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:44 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:44 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:44 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:44 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:44 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:44 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:44 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:44 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:44 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:44 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:44 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:44 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:44 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:44 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:44 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:44 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:44 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:44 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:44 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:44 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:44 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:44 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:44 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:44 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:44 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:44 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:44 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:44 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:44 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:44 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:44 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:44 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:44 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:44 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:44 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:44 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:44 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:44 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:44 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:44 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:44 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:44 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:44 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:44 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:44 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:44 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:44 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:44 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:44 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:44 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:44 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:44 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:44 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:44 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:44 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:44 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:44 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:44 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:44 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:44 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:44 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:44 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:44 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:44 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:44 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:44 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:44 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:44 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:44 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:44 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:44 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:44 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:44 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:44 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:44 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:44 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:44 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:44 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:44 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:44 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:44 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:44 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:44 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:44 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:44 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:44 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:44 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:44 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:44 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:44 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:44 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:44 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:44 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:44 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:44 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:44 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:44 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:44 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:44 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:45 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:45 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:45 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:45 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:45 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:45 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:45 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:45 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:45 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:45 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:45 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:45 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:45 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:45 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:45 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:45 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:45 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:45 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:45 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:45 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:45 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:45 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:45 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:45 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:45 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:45 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:45 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:45 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:45 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:45 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:45 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:45 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:45 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:45 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:45 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:45 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:45 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:45 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:45 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:45 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:45 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:45 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:45 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:45 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:45 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:45 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:45 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:45 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:45 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:45 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:45 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:45 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:45 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:45 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:45 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:45 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:45 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:45 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:45 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:45 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:45 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:45 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:45 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:45 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:45 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:45 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:45 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:45 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:45 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:45 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:45 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:45 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:45 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:45 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:45 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:45 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:45 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:45 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:45 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:45 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:45 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:45 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:45 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:45 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:45 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:45 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:45 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:45 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:45 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:45 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:45 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:45 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:45 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:45 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:45 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:45 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:45 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:45 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:45 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:45 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:45 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:45 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:45 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:45 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:45 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:45 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:45 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:45 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:45 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:45 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:45 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:45 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:45 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:45 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:45 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:45 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:45 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:45 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:45 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:45 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:45 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:45 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:45 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:45 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:45 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:45 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:45 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:45 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:45 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:45 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:45 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:45 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:45 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:45 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:45 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:45 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:45 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:45 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:45 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:46 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:46 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:46 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:46 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:46 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:46 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:46 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:46 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:46 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:46 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:46 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:46 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:46 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:46 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:46 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:46 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:46 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:46 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:46 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:46 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:46 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:46 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:46 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:46 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:46 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:46 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:46 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:46 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:46 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:46 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:46 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:46 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:46 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:46 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:46 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:46 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:46 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:46 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:46 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:46 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:46 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:46 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:46 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:46 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:46 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:46 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:46 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:46 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:46 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:46 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:46 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:46 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:46 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:46 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:46 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:46 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:46 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:46 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:46 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:46 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:46 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:46 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:46 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:46 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:46 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:46 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:46 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:46 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:46 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:46 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:46 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:46 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:46 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:46 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:46 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:46 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:46 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:46 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:46 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:46 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:46 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:46 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:46 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:46 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:46 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:46 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:46 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:46 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:46 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:15:46 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:46 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:46 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:46 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:46 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:46 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:46 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:46 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:15:46 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:15:46 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:15:46 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:15:46 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:15:46 MM-Home kernel: [drm] Module unloaded
Feb 14 20:15:46 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:15:46 MM-Home systemd-udevd[19367]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:16:32 MM-Home systemd[1]: display-manager.service stop-sigterm timed out. Killing.
Feb 14 20:16:32 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:16:32 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:16:32 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:16:32 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:16:32 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:16:32 MM-Home kernel: [drm] Module unloaded
Feb 14 20:16:32 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:16:32 MM-Home systemd-udevd[22644]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:16:32 MM-Home auditd[756]: The audit daemon is exiting.
Feb 14 20:16:32 MM-Home kernel: audit: type=1305 audit(1455477392.235:210): audit_pid=0 old=756 auid=4294967295 ses=4294967295 res=1
Feb 14 20:16:32 MM-Home kernel: audit: type=1131 audit(1455477392.235:211): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=' comm="auditd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 14 20:16:32 MM-Home kernel: audit: type=1400 audit(1455477392.235:212): apparmor="STATUS" operation="profile_remove" name="/usr/bin/lessopen.sh" pid=22666 comm="boot.apparmor"
Feb 14 20:16:32 MM-Home kernel: audit: type=1300 audit(1455477392.235:212): arch=c000003e syscall=1 success=yes exit=20 a0=1 a1=7f2d4f0bb000 a2=14 a3=ffffffec items=0 ppid=22642 pid=22666 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="boot.apparmor" exe="/bin/bash" key=(null)
Feb 14 20:16:32 MM-Home kernel: audit: type=1327 audit(1455477392.235:212): proctitle=2F62696E2F7368002F6574632F696E69742E642F626F6F742E61707061726D6F720073746F70
Feb 14 20:16:32 MM-Home kernel: audit: type=1400 audit(1455477392.235:213): apparmor="STATUS" operation="profile_remove" name="/usr/lib/apache2/mpm-prefork/apache2" pid=22666 comm="boot.apparmor"
Feb 14 20:16:32 MM-Home kernel: audit: type=1300 audit(1455477392.235:213): arch=c000003e syscall=1 success=yes exit=36 a0=1 a1=7f2d4f0bb000 a2=24 a3=6170612f6b726f66 items=0 ppid=22642 pid=22666 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="boot.apparmor" exe="/bin/bash" key=(null)
Feb 14 20:16:32 MM-Home kernel: audit: type=1327 audit(1455477392.235:213): proctitle=2F62696E2F7368002F6574632F696E69742E642F626F6F742E61707061726D6F720073746F70
Feb 14 20:16:32 MM-Home kernel: audit: type=1400 audit(1455477392.235:214): apparmor="STATUS" operation="profile_remove" name="/usr/lib/dovecot/anvil" pid=22666 comm="boot.apparmor"
Feb 14 20:16:32 MM-Home boot.apparmor[22642]: Unloading AppArmor profiles  ..done
Feb 14 20:16:32 MM-Home umount[22675]: umount: /var/log: target is busy
Feb 14 20:16:32 MM-Home umount[22675]: (In some cases useful info about processes that
Feb 14 20:16:32 MM-Home umount[22675]: use the device is found by lsof(8) or fuser(1).)
Feb 14 20:16:32 MM-Home umount[22685]: umount: /tmp: target is busy
Feb 14 20:16:32 MM-Home umount[22685]: (In some cases useful info about processes that
Feb 14 20:16:32 MM-Home umount[22685]: use the device is found by lsof(8) or fuser(1).)
Feb 14 20:16:32 MM-Home systemd[1]: Failed unmounting /tmp.
Feb 14 20:16:32 MM-Home kernel: XFS (sdb4): Unmounting Filesystem
Feb 14 20:16:32 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:16:32 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:16:32 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:16:32 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:16:32 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:16:32 MM-Home kernel: [drm] Module unloaded
Feb 14 20:16:32 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:16:32 MM-Home systemd-udevd[22647]: Failed to apply ACL on /dev/dri/card1: No such file or directory
Feb 14 20:16:32 MM-Home kernel: Error: Driver 'nvlink' is already registered, aborting...
Feb 14 20:16:32 MM-Home kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Feb 14 20:16:32 MM-Home kernel: NVRM: This can occur when a driver such as: 
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
                                NVRM: was loaded and obtained ownership of the NVIDIA device(s).
Feb 14 20:16:32 MM-Home kernel: NVRM: Try unloading the conflicting kernel module (and/or
                                NVRM: reconfigure your kernel without the conflicting
                                NVRM: driver(s)), then try loading the NVIDIA kernel module
                                NVRM: again.
Feb 14 20:16:32 MM-Home kernel: NVRM: No NVIDIA graphics adapter probed!
Feb 14 20:16:32 MM-Home kernel: [drm] Module unloaded
Feb 14 20:16:32 MM-Home kernel: NVRM: NVIDIA init module failed!
Feb 14 20:16:32 MM-Home systemd-journal[473]: Journal stopped
-- Reboot --
Feb 14 20:22:31 linux-ytaf systemd-journal[187]: Runtime journal is using 8.0M (max allowed 397.5M, trying to leave 596.3M free of 3.8G available → current limit 397.5M).
Feb 14 20:22:31 linux-ytaf systemd-journal[187]: Runtime journal is using 8.0M (max allowed 397.5M, trying to leave 596.3M free of 3.8G available → current limit 397.5M).
Feb 14 20:22:31 linux-ytaf kernel: microcode: CPU0 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 20:22:31 linux-ytaf kernel: Initializing cgroup subsys cpuset
Feb 14 20:22:31 linux-ytaf kernel: Initializing cgroup subsys cpu
Feb 14 20:22:31 linux-ytaf kernel: Initializing cgroup subsys cpuacct
Feb 14 20:22:31 linux-ytaf kernel: Linux version 4.1.15-8-default (geeko@buildhost) (gcc version 4.8.5 (SUSE Linux) ) #1 SMP PREEMPT Wed Jan 20 16:41:00 UTC 2016 (0e3b3ab)
Feb 14 20:22:31 linux-ytaf kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.1.15-8-default root=UUID=21024970-7a27-4114-8525-d8dd026f23b6 ro resume=/dev/sdb2 splash=silent quiet showopts
Feb 14 20:22:31 linux-ytaf kernel: e820: BIOS-provided physical RAM map:
Feb 14 20:22:31 linux-ytaf kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Feb 14 20:22:31 linux-ytaf kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
Feb 14 20:22:31 linux-ytaf kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000deb8efff] usable
Feb 14 20:22:31 linux-ytaf kernel: BIOS-e820: [mem 0x00000000deb8f000-0x00000000dedf1fff] reserved
Feb 14 20:22:31 linux-ytaf kernel: BIOS-e820: [mem 0x00000000dedf2000-0x00000000dee79fff] ACPI NVS
Feb 14 20:22:31 linux-ytaf kernel: BIOS-e820: [mem 0x00000000dee7a000-0x00000000df13efff] reserved
Feb 14 20:22:31 linux-ytaf kernel: BIOS-e820: [mem 0x00000000df13f000-0x00000000df383fff] ACPI NVS
Feb 14 20:22:31 linux-ytaf kernel: BIOS-e820: [mem 0x00000000df384000-0x00000000df391fff] ACPI data
Feb 14 20:22:31 linux-ytaf kernel: BIOS-e820: [mem 0x00000000df392000-0x00000000df3befff] ACPI NVS
Feb 14 20:22:31 linux-ytaf kernel: BIOS-e820: [mem 0x00000000df3bf000-0x00000000df3c3fff] ACPI data
Feb 14 20:22:31 linux-ytaf kernel: BIOS-e820: [mem 0x00000000df3c4000-0x00000000df406fff] ACPI NVS
Feb 14 20:22:31 linux-ytaf kernel: BIOS-e820: [mem 0x00000000df407000-0x00000000df7fffff] usable
Feb 14 20:22:31 linux-ytaf kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Feb 14 20:22:31 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Feb 14 20:22:31 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Feb 14 20:22:31 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Feb 14 20:22:31 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Feb 14 20:22:31 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Feb 14 20:22:31 linux-ytaf kernel: BIOS-e820: [mem 0x0000000100000000-0x000000021effffff] usable
Feb 14 20:22:31 linux-ytaf kernel: NX (Execute Disable) protection: active
Feb 14 20:22:31 linux-ytaf kernel: e820: update [mem 0x0c81c018-0x0c82bc57] usable ==> usable
Feb 14 20:22:31 linux-ytaf kernel: e820: update [mem 0x0c82c018-0x0c83b857] usable ==> usable
Feb 14 20:22:31 linux-ytaf kernel: e820: update [mem 0x0c2ef018-0x0c2f2e57] usable ==> usable
Feb 14 20:22:31 linux-ytaf kernel: extended physical RAM map:
Feb 14 20:22:31 linux-ytaf kernel: reserve setup_data: [mem 0x0000000000000000-0x000000000009efff] usable
Feb 14 20:22:31 linux-ytaf kernel: reserve setup_data: [mem 0x000000000009f000-0x000000000009ffff] reserved
Feb 14 20:22:31 linux-ytaf kernel: reserve setup_data: [mem 0x0000000000100000-0x000000000c2ef017] usable
Feb 14 20:22:31 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c2ef018-0x000000000c2f2e57] usable
Feb 14 20:22:31 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c2f2e58-0x000000000c81c017] usable
Feb 14 20:22:31 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c81c018-0x000000000c82bc57] usable
Feb 14 20:22:31 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c82bc58-0x000000000c82c017] usable
Feb 14 20:22:31 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c82c018-0x000000000c83b857] usable
Feb 14 20:22:31 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c83b858-0x00000000deb8efff] usable
Feb 14 20:22:31 linux-ytaf kernel: reserve setup_data: [mem 0x00000000deb8f000-0x00000000dedf1fff] reserved
Feb 14 20:22:31 linux-ytaf kernel: reserve setup_data: [mem 0x00000000dedf2000-0x00000000dee79fff] ACPI NVS
Feb 14 20:22:31 linux-ytaf kernel: reserve setup_data: [mem 0x00000000dee7a000-0x00000000df13efff] reserved
Feb 14 20:22:31 linux-ytaf kernel: reserve setup_data: [mem 0x00000000df13f000-0x00000000df383fff] ACPI NVS
Feb 14 20:22:31 linux-ytaf kernel: reserve setup_data: [mem 0x00000000df384000-0x00000000df391fff] ACPI data
Feb 14 20:22:31 linux-ytaf kernel: reserve setup_data: [mem 0x00000000df392000-0x00000000df3befff] ACPI NVS
Feb 14 20:22:31 linux-ytaf kernel: reserve setup_data: [mem 0x00000000df3bf000-0x00000000df3c3fff] ACPI data
Feb 14 20:22:31 linux-ytaf kernel: reserve setup_data: [mem 0x00000000df3c4000-0x00000000df406fff] ACPI NVS
Feb 14 20:22:31 linux-ytaf kernel: reserve setup_data: [mem 0x00000000df407000-0x00000000df7fffff] usable
Feb 14 20:22:31 linux-ytaf kernel: reserve setup_data: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Feb 14 20:22:31 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Feb 14 20:22:31 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Feb 14 20:22:31 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Feb 14 20:22:31 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Feb 14 20:22:31 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Feb 14 20:22:31 linux-ytaf kernel: reserve setup_data: [mem 0x0000000100000000-0x000000021effffff] usable
Feb 14 20:22:31 linux-ytaf kernel: efi: EFI v2.31 by American Megatrends
Feb 14 20:22:31 linux-ytaf kernel: efi:  ACPI=0xdf384000  ACPI 2.0=0xdf384000  SMBIOS=0xdec27e98  MPS=0xfc990 
Feb 14 20:22:31 linux-ytaf kernel: SMBIOS 2.6 present.
Feb 14 20:22:31 linux-ytaf kernel: DMI: System manufacturer System Product Name/MAXIMUS IV GENE-Z/GEN3, BIOS 3603 11/09/2012
Feb 14 20:22:31 linux-ytaf kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Feb 14 20:22:31 linux-ytaf kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Feb 14 20:22:31 linux-ytaf kernel: AGP: No AGP bridge found
Feb 14 20:22:31 linux-ytaf kernel: e820: last_pfn = 0x21f000 max_arch_pfn = 0x400000000
Feb 14 20:22:31 linux-ytaf kernel: MTRR default type: uncachable
Feb 14 20:22:31 linux-ytaf kernel: MTRR fixed ranges enabled:
Feb 14 20:22:31 linux-ytaf kernel:   00000-9FFFF write-back
Feb 14 20:22:31 linux-ytaf kernel:   A0000-BFFFF uncachable
Feb 14 20:22:31 linux-ytaf kernel:   C0000-D3FFF write-protect
Feb 14 20:22:31 linux-ytaf kernel:   D4000-DFFFF uncachable
Feb 14 20:22:31 linux-ytaf kernel:   E0000-E7FFF write-through
Feb 14 20:22:31 linux-ytaf kernel:   E8000-FFFFF write-protect
Feb 14 20:22:31 linux-ytaf kernel: MTRR variable ranges enabled:
Feb 14 20:22:31 linux-ytaf kernel:   0 base 000000000 mask E00000000 write-back
Feb 14 20:22:31 linux-ytaf kernel:   1 base 200000000 mask FF0000000 write-back
Feb 14 20:22:31 linux-ytaf kernel:   2 base 210000000 mask FF8000000 write-back
Feb 14 20:22:31 linux-ytaf kernel:   3 base 218000000 mask FFC000000 write-back
Feb 14 20:22:31 linux-ytaf kernel:   4 base 21C000000 mask FFE000000 write-back
Feb 14 20:22:31 linux-ytaf kernel:   5 base 21E000000 mask FFF000000 write-back
Feb 14 20:22:31 linux-ytaf kernel:   6 base 0E0000000 mask FE0000000 uncachable
Feb 14 20:22:31 linux-ytaf kernel:   7 disabled
Feb 14 20:22:31 linux-ytaf kernel:   8 disabled
Feb 14 20:22:31 linux-ytaf kernel:   9 disabled
Feb 14 20:22:31 linux-ytaf kernel: PAT configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- UC  
Feb 14 20:22:31 linux-ytaf kernel: e820: update [mem 0xe0000000-0xffffffff] usable ==> reserved
Feb 14 20:22:31 linux-ytaf kernel: e820: last_pfn = 0xdf800 max_arch_pfn = 0x400000000
Feb 14 20:22:31 linux-ytaf kernel: found SMP MP-table at [mem 0x000fcd30-0x000fcd3f] mapped at [ffff8800000fcd30]
Feb 14 20:22:31 linux-ytaf kernel: Scanning 1 areas for low memory corruption
Feb 14 20:22:31 linux-ytaf kernel: Base memory trampoline at [ffff880000097000] 97000 size 24576
Feb 14 20:22:31 linux-ytaf kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
Feb 14 20:22:31 linux-ytaf kernel:  [mem 0x00000000-0x000fffff] page 4k
Feb 14 20:22:31 linux-ytaf kernel: BRK [0x0e21a000, 0x0e21afff] PGTABLE
Feb 14 20:22:31 linux-ytaf kernel: BRK [0x0e21b000, 0x0e21bfff] PGTABLE
Feb 14 20:22:31 linux-ytaf kernel: BRK [0x0e21c000, 0x0e21cfff] PGTABLE
Feb 14 20:22:31 linux-ytaf kernel: init_memory_mapping: [mem 0x21ee00000-0x21effffff]
Feb 14 20:22:31 linux-ytaf kernel:  [mem 0x21ee00000-0x21effffff] page 2M
Feb 14 20:22:31 linux-ytaf kernel: BRK [0x0e21d000, 0x0e21dfff] PGTABLE
Feb 14 20:22:31 linux-ytaf kernel: init_memory_mapping: [mem 0x200000000-0x21edfffff]
Feb 14 20:22:31 linux-ytaf kernel:  [mem 0x200000000-0x21edfffff] page 2M
Feb 14 20:22:31 linux-ytaf kernel: init_memory_mapping: [mem 0x1e0000000-0x1ffffffff]
Feb 14 20:22:31 linux-ytaf kernel:  [mem 0x1e0000000-0x1ffffffff] page 2M
Feb 14 20:22:31 linux-ytaf kernel: BRK [0x0e21e000, 0x0e21efff] PGTABLE
Feb 14 20:22:31 linux-ytaf kernel: init_memory_mapping: [mem 0x00100000-0xdeb8efff]
Feb 14 20:22:31 linux-ytaf kernel:  [mem 0x00100000-0x001fffff] page 4k
Feb 14 20:22:31 linux-ytaf kernel:  [mem 0x00200000-0xde9fffff] page 2M
Feb 14 20:22:31 linux-ytaf kernel:  [mem 0xdea00000-0xdeb8efff] page 4k
Feb 14 20:22:31 linux-ytaf kernel: init_memory_mapping: [mem 0xdf407000-0xdf7fffff]
Feb 14 20:22:31 linux-ytaf kernel:  [mem 0xdf407000-0xdf5fffff] page 4k
Feb 14 20:22:31 linux-ytaf kernel:  [mem 0xdf600000-0xdf7fffff] page 2M
Feb 14 20:22:31 linux-ytaf kernel: BRK [0x0e21f000, 0x0e21ffff] PGTABLE
Feb 14 20:22:31 linux-ytaf kernel: init_memory_mapping: [mem 0x100000000-0x1dfffffff]
Feb 14 20:22:31 linux-ytaf kernel:  [mem 0x100000000-0x1dfffffff] page 2M
Feb 14 20:22:31 linux-ytaf kernel: RAMDISK: [mem 0x007e1000-0x00ffafff]
Feb 14 20:22:31 linux-ytaf kernel: ACPI: Early table checksum verification disabled
Feb 14 20:22:31 linux-ytaf kernel: ACPI: RSDP 0x00000000DF384000 000024 (v02 ALASKA)
Feb 14 20:22:31 linux-ytaf kernel: ACPI: XSDT 0x00000000DF384078 000064 (v01 ALASKA A M I    01072009 AMI  00010013)
Feb 14 20:22:31 linux-ytaf kernel: ACPI: FACP 0x00000000DF38FC78 0000F4 (v04 ALASKA A M I    01072009 AMI  00010013)
Feb 14 20:22:31 linux-ytaf kernel: ACPI: DSDT 0x00000000DF384170 00BB02 (v02 ALASKA A M I    00000015 INTL 20051117)
Feb 14 20:22:31 linux-ytaf kernel: ACPI: FACS 0x00000000DF3BDF80 000040
Feb 14 20:22:31 linux-ytaf kernel: ACPI: APIC 0x00000000DF38FD70 000092 (v03 ALASKA A M I    01072009 AMI  00010013)
Feb 14 20:22:31 linux-ytaf kernel: ACPI: MCFG 0x00000000DF38FE08 00003C (v01 ALASKA A M I    01072009 MSFT 00000097)
Feb 14 20:22:31 linux-ytaf kernel: ACPI: HPET 0x00000000DF38FE48 000038 (v01 ALASKA A M I    01072009 AMI. 00000005)
Feb 14 20:22:31 linux-ytaf kernel: ACPI: SSDT 0x00000000DF38FE80 00036D (v01 SataRe SataTabl 00001000 INTL 20091112)
Feb 14 20:22:31 linux-ytaf kernel: ACPI: SSDT 0x00000000DF3901F0 0009AA (v01 PmRef  Cpu0Ist  00003000 INTL 20051117)
Feb 14 20:22:31 linux-ytaf kernel: ACPI: SSDT 0x00000000DF390BA0 000A92 (v01 PmRef  CpuPm    00003000 INTL 20051117)
Feb 14 20:22:31 linux-ytaf kernel: ACPI: BGRT 0x00000000DF391690 000038 (v00 ALASKA A M I    01072009 AMI  00010013)
Feb 14 20:22:31 linux-ytaf kernel: ACPI: Local APIC address 0xfee00000
Feb 14 20:22:31 linux-ytaf kernel: No NUMA configuration found
Feb 14 20:22:31 linux-ytaf kernel: Faking a node at [mem 0x0000000000000000-0x000000021effffff]
Feb 14 20:22:31 linux-ytaf kernel: NODE_DATA(0) allocated [mem 0x21efe5000-0x21eff8fff]
Feb 14 20:22:31 linux-ytaf kernel:  [ffffea0000000000-ffffea00087fffff] PMD -> [ffff880216600000-ffff88021e5fffff] on node 0
Feb 14 20:22:31 linux-ytaf kernel: Zone ranges:
Feb 14 20:22:31 linux-ytaf kernel:   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
Feb 14 20:22:31 linux-ytaf kernel:   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
Feb 14 20:22:31 linux-ytaf kernel:   Normal   [mem 0x0000000100000000-0x000000021effffff]
Feb 14 20:22:31 linux-ytaf kernel: Movable zone start for each node
Feb 14 20:22:31 linux-ytaf kernel: Early memory node ranges
Feb 14 20:22:31 linux-ytaf kernel:   node   0: [mem 0x0000000000001000-0x000000000009efff]
Feb 14 20:22:31 linux-ytaf kernel:   node   0: [mem 0x0000000000100000-0x00000000deb8efff]
Feb 14 20:22:31 linux-ytaf kernel:   node   0: [mem 0x00000000df407000-0x00000000df7fffff]
Feb 14 20:22:31 linux-ytaf kernel:   node   0: [mem 0x0000000100000000-0x000000021effffff]
Feb 14 20:22:31 linux-ytaf kernel: Initmem setup node 0 [mem 0x0000000000001000-0x000000021effffff]
Feb 14 20:22:31 linux-ytaf kernel: On node 0 totalpages: 2088742
Feb 14 20:22:31 linux-ytaf kernel:   DMA zone: 64 pages used for memmap
Feb 14 20:22:31 linux-ytaf kernel:   DMA zone: 2115 pages reserved
Feb 14 20:22:31 linux-ytaf kernel:   DMA zone: 3998 pages, LIFO batch:0
Feb 14 20:22:31 linux-ytaf kernel:   DMA32 zone: 14207 pages used for memmap
Feb 14 20:22:31 linux-ytaf kernel:   DMA32 zone: 909192 pages, LIFO batch:31
Feb 14 20:22:31 linux-ytaf kernel:   Normal zone: 18368 pages used for memmap
Feb 14 20:22:31 linux-ytaf kernel:   Normal zone: 1175552 pages, LIFO batch:31
Feb 14 20:22:31 linux-ytaf kernel: tboot: non-0 tboot_addr but it is not of type E820_RESERVED
Feb 14 20:22:31 linux-ytaf kernel: ACPI: PM-Timer IO Port: 0x408
Feb 14 20:22:31 linux-ytaf kernel: ACPI: Local APIC address 0xfee00000
Feb 14 20:22:31 linux-ytaf kernel: ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
Feb 14 20:22:31 linux-ytaf kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
Feb 14 20:22:31 linux-ytaf kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Feb 14 20:22:31 linux-ytaf kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Feb 14 20:22:31 linux-ytaf kernel: ACPI: IRQ0 used by override.
Feb 14 20:22:31 linux-ytaf kernel: ACPI: IRQ9 used by override.
Feb 14 20:22:31 linux-ytaf kernel: Using ACPI (MADT) for SMP configuration information
Feb 14 20:22:31 linux-ytaf kernel: ACPI: HPET id: 0x8086a701 base: 0xfed00000
Feb 14 20:22:31 linux-ytaf kernel: smpboot: Allowing 8 CPUs, 0 hotplug CPUs
Feb 14 20:22:31 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
Feb 14 20:22:31 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Feb 14 20:22:31 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000fffff]
Feb 14 20:22:31 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c2ef000-0x0c2effff]
Feb 14 20:22:31 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c2f2000-0x0c2f2fff]
Feb 14 20:22:31 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c81c000-0x0c81cfff]
Feb 14 20:22:31 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c82b000-0x0c82bfff]
Feb 14 20:22:31 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c82c000-0x0c82cfff]
Feb 14 20:22:31 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c83b000-0x0c83bfff]
Feb 14 20:22:31 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xdeb8f000-0xdedf1fff]
Feb 14 20:22:31 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xdedf2000-0xdee79fff]
Feb 14 20:22:31 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xdee7a000-0xdf13efff]
Feb 14 20:22:31 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xdf13f000-0xdf383fff]
Feb 14 20:22:31 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xdf384000-0xdf391fff]
Feb 14 20:22:31 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xdf392000-0xdf3befff]
Feb 14 20:22:31 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xdf3bf000-0xdf3c3fff]
Feb 14 20:22:31 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xdf3c4000-0xdf406fff]
Feb 14 20:22:31 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xdf800000-0xf7ffffff]
Feb 14 20:22:31 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
Feb 14 20:22:31 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfc000000-0xfebfffff]
Feb 14 20:22:31 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
Feb 14 20:22:31 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfec01000-0xfecfffff]
Feb 14 20:22:31 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed00000-0xfed03fff]
Feb 14 20:22:31 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed04000-0xfed1bfff]
Feb 14 20:22:31 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Feb 14 20:22:31 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed20000-0xfedfffff]
Feb 14 20:22:31 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
Feb 14 20:22:31 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfee01000-0xfeffffff]
Feb 14 20:22:31 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Feb 14 20:22:31 linux-ytaf kernel: e820: [mem 0xdf800000-0xf7ffffff] available for PCI devices
Feb 14 20:22:31 linux-ytaf kernel: Booting paravirtualized kernel on bare hardware
Feb 14 20:22:31 linux-ytaf kernel: clocksource refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
Feb 14 20:22:31 linux-ytaf kernel: setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:8 nr_node_ids:1
Feb 14 20:22:31 linux-ytaf kernel: PERCPU: Embedded 33 pages/cpu @ffff88021ec00000 s97368 r8192 d29608 u262144
Feb 14 20:22:31 linux-ytaf kernel: pcpu-alloc: s97368 r8192 d29608 u262144 alloc=1*2097152
Feb 14 20:22:31 linux-ytaf kernel: pcpu-alloc: [0] 0 1 2 3 4 5 6 7 
Feb 14 20:22:31 linux-ytaf kernel: Built 1 zonelists in Node order, mobility grouping on.  Total pages: 2053988
Feb 14 20:22:31 linux-ytaf kernel: Policy zone: Normal
Feb 14 20:22:31 linux-ytaf kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.1.15-8-default root=UUID=21024970-7a27-4114-8525-d8dd026f23b6 ro resume=/dev/sdb2 splash=silent quiet showopts
Feb 14 20:22:31 linux-ytaf kernel: log_buf_len individual max cpu contribution: 32768 bytes
Feb 14 20:22:31 linux-ytaf kernel: log_buf_len total cpu_extra contributions: 229376 bytes
Feb 14 20:22:31 linux-ytaf kernel: log_buf_len min size: 262144 bytes
Feb 14 20:22:31 linux-ytaf kernel: log_buf_len: 524288 bytes
Feb 14 20:22:31 linux-ytaf kernel: early log buf free: 247532(94%)
Feb 14 20:22:31 linux-ytaf kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
Feb 14 20:22:31 linux-ytaf kernel: xsave: enabled xstate_bv 0x7, cntxt size 0x340 using standard form
Feb 14 20:22:31 linux-ytaf kernel: AGP: Checking aperture...
Feb 14 20:22:31 linux-ytaf kernel: AGP: No AGP bridge found
Feb 14 20:22:31 linux-ytaf kernel: Memory: 7939124K/8354968K available (6547K kernel code, 1084K rwdata, 4848K rodata, 1560K init, 1516K bss, 415844K reserved, 0K cma-reserved)
Feb 14 20:22:31 linux-ytaf kernel: Preemptible hierarchical RCU implementation.
Feb 14 20:22:31 linux-ytaf kernel:         RCU dyntick-idle grace-period acceleration is enabled.
Feb 14 20:22:31 linux-ytaf kernel:         RCU restricting CPUs from NR_CPUS=512 to nr_cpu_ids=8.
Feb 14 20:22:31 linux-ytaf kernel: RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
Feb 14 20:22:31 linux-ytaf kernel: NR_IRQS:33024 nr_irqs:488 16
Feb 14 20:22:31 linux-ytaf kernel:         Offload RCU callbacks from all CPUs
Feb 14 20:22:31 linux-ytaf kernel:         Offload RCU callbacks from CPUs: 0-7.
Feb 14 20:22:31 linux-ytaf kernel: Console: colour dummy device 80x25
Feb 14 20:22:31 linux-ytaf kernel: console [tty0] enabled
Feb 14 20:22:31 linux-ytaf kernel: clocksource hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484882848 ns
Feb 14 20:22:31 linux-ytaf kernel: hpet clockevent registered
Feb 14 20:22:31 linux-ytaf kernel: tsc: Fast TSC calibration using PIT
Feb 14 20:22:31 linux-ytaf kernel: tsc: Detected 3411.108 MHz processor
Feb 14 20:22:31 linux-ytaf kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 6822.21 BogoMIPS (lpj=13644432)
Feb 14 20:22:31 linux-ytaf kernel: pid_max: default: 32768 minimum: 301
Feb 14 20:22:31 linux-ytaf kernel: ACPI: Core revision 20150410
Feb 14 20:22:31 linux-ytaf kernel: ACPI: All ACPI Tables successfully acquired
Feb 14 20:22:31 linux-ytaf kernel: Security Framework initialized
Feb 14 20:22:31 linux-ytaf kernel: AppArmor: AppArmor initialized
Feb 14 20:22:31 linux-ytaf kernel: Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
Feb 14 20:22:31 linux-ytaf kernel: Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
Feb 14 20:22:31 linux-ytaf kernel: Mount-cache hash table entries: 16384 (order: 5, 131072 bytes)
Feb 14 20:22:31 linux-ytaf kernel: Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes)
Feb 14 20:22:31 linux-ytaf kernel: Initializing cgroup subsys blkio
Feb 14 20:22:31 linux-ytaf kernel: Initializing cgroup subsys memory
Feb 14 20:22:31 linux-ytaf kernel: Initializing cgroup subsys devices
Feb 14 20:22:31 linux-ytaf kernel: Initializing cgroup subsys freezer
Feb 14 20:22:31 linux-ytaf kernel: Initializing cgroup subsys net_cls
Feb 14 20:22:31 linux-ytaf kernel: Initializing cgroup subsys perf_event
Feb 14 20:22:31 linux-ytaf kernel: Initializing cgroup subsys net_prio
Feb 14 20:22:31 linux-ytaf kernel: Initializing cgroup subsys hugetlb
Feb 14 20:22:31 linux-ytaf kernel: CPU: Physical Processor ID: 0
Feb 14 20:22:31 linux-ytaf kernel: CPU: Processor Core ID: 0
Feb 14 20:22:31 linux-ytaf kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Feb 14 20:22:31 linux-ytaf kernel: ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Feb 14 20:22:31 linux-ytaf kernel: mce: CPU supports 9 MCE banks
Feb 14 20:22:31 linux-ytaf kernel: CPU0: Thermal monitoring enabled (TM1)
Feb 14 20:22:31 linux-ytaf kernel: process: using mwait in idle threads
Feb 14 20:22:31 linux-ytaf kernel: Last level iTLB entries: 4KB 512, 2MB 8, 4MB 8
Feb 14 20:22:31 linux-ytaf kernel: Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32, 1GB 0
Feb 14 20:22:31 linux-ytaf kernel: Freeing SMP alternatives memory: 24K (ffffffff82097000 - ffffffff8209d000)
Feb 14 20:22:31 linux-ytaf kernel: ftrace: allocating 25000 entries in 98 pages
Feb 14 20:22:31 linux-ytaf kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Feb 14 20:22:31 linux-ytaf kernel: TSC deadline timer enabled
Feb 14 20:22:31 linux-ytaf kernel: smpboot: CPU0: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz (fam: 06, model: 2a, stepping: 07)
Feb 14 20:22:31 linux-ytaf kernel: Performance Events: PEBS fmt1+, 16-deep LBR, SandyBridge events, full-width counters, Intel PMU driver.
Feb 14 20:22:31 linux-ytaf kernel: ... version:                3
Feb 14 20:22:31 linux-ytaf kernel: ... bit width:              48
Feb 14 20:22:31 linux-ytaf kernel: ... generic registers:      4
Feb 14 20:22:31 linux-ytaf kernel: ... value mask:             0000ffffffffffff
Feb 14 20:22:31 linux-ytaf kernel: ... max period:             0000ffffffffffff
Feb 14 20:22:31 linux-ytaf kernel: ... fixed-purpose events:   3
Feb 14 20:22:31 linux-ytaf kernel: ... event mask:             000000070000000f
Feb 14 20:22:31 linux-ytaf kernel: x86: Booting SMP configuration:
Feb 14 20:22:31 linux-ytaf kernel: .... node  #0, CPUs:      #1
Feb 14 20:22:31 linux-ytaf kernel: microcode: CPU1 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 20:22:31 linux-ytaf kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Feb 14 20:22:31 linux-ytaf kernel:  #2
Feb 14 20:22:31 linux-ytaf kernel: microcode: CPU2 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 20:22:31 linux-ytaf kernel:  #3
Feb 14 20:22:31 linux-ytaf kernel: microcode: CPU3 microcode updated early to revision 0x29, date = 2013-06-12
Feb 14 20:22:31 linux-ytaf kernel:  #4 #5 #6 #7
Feb 14 20:22:31 linux-ytaf kernel: x86: Booted up 1 node, 8 CPUs
Feb 14 20:22:31 linux-ytaf kernel: smpboot: Total of 8 processors activated (54577.72 BogoMIPS)
Feb 14 20:22:31 linux-ytaf kernel: devtmpfs: initialized
Feb 14 20:22:31 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xdedf2000-0xdee79fff] (557056 bytes)
Feb 14 20:22:31 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xdf13f000-0xdf383fff] (2379776 bytes)
Feb 14 20:22:31 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xdf392000-0xdf3befff] (184320 bytes)
Feb 14 20:22:31 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xdf3c4000-0xdf406fff] (274432 bytes)
Feb 14 20:22:31 linux-ytaf kernel: clocksource jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
Feb 14 20:22:31 linux-ytaf kernel: pinctrl core: initialized pinctrl subsystem
Feb 14 20:22:31 linux-ytaf kernel: RTC time: 20:22:28, date: 02/14/16
Feb 14 20:22:31 linux-ytaf kernel: NET: Registered protocol family 16
Feb 14 20:22:31 linux-ytaf kernel: cpuidle: using governor ladder
Feb 14 20:22:31 linux-ytaf kernel: cpuidle: using governor menu
Feb 14 20:22:31 linux-ytaf kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
Feb 14 20:22:31 linux-ytaf kernel: ACPI: bus type PCI registered
Feb 14 20:22:31 linux-ytaf kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Feb 14 20:22:31 linux-ytaf kernel: PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
Feb 14 20:22:31 linux-ytaf kernel: PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
Feb 14 20:22:31 linux-ytaf kernel: PCI: Using configuration type 1 for base access
Feb 14 20:22:31 linux-ytaf kernel: perf_event_intel: PMU erratum BJ122, BV98, HSD29 worked around, HT is on
Feb 14 20:22:31 linux-ytaf kernel: ACPI: Added _OSI(Module Device)
Feb 14 20:22:31 linux-ytaf kernel: ACPI: Added _OSI(Processor Device)
Feb 14 20:22:31 linux-ytaf kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
Feb 14 20:22:31 linux-ytaf kernel: ACPI: Added _OSI(Processor Aggregator Device)
Feb 14 20:22:31 linux-ytaf kernel: ACPI: Executed 1 blocks of module-level executable AML code
Feb 14 20:22:31 linux-ytaf kernel: ACPI: Dynamic OEM Table Load:
Feb 14 20:22:31 linux-ytaf kernel: ACPI: SSDT 0xFFFF880214FC7000 00083B (v01 PmRef  Cpu0Cst  00003001 INTL 20051117)
Feb 14 20:22:31 linux-ytaf kernel: ACPI: Dynamic OEM Table Load:
Feb 14 20:22:31 linux-ytaf kernel: ACPI: SSDT 0xFFFF880214FC1400 000303 (v01 PmRef  ApIst    00003000 INTL 20051117)
Feb 14 20:22:31 linux-ytaf kernel: ACPI: Dynamic OEM Table Load:
Feb 14 20:22:31 linux-ytaf kernel: ACPI: SSDT 0xFFFF880214F72600 000119 (v01 PmRef  ApCst    00003000 INTL 20051117)
Feb 14 20:22:31 linux-ytaf kernel: ACPI : EC: EC started
Feb 14 20:22:31 linux-ytaf kernel: ACPI: Interpreter enabled
Feb 14 20:22:31 linux-ytaf kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20150410/hwxface-580)
Feb 14 20:22:31 linux-ytaf kernel: ACPI: (supports S0 S1 S3 S4 S5)
Feb 14 20:22:31 linux-ytaf kernel: ACPI: Using IOAPIC for interrupt routing
Feb 14 20:22:31 linux-ytaf kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Feb 14 20:22:31 linux-ytaf kernel: ACPI: Power Resource [FN00] (off)
Feb 14 20:22:31 linux-ytaf kernel: ACPI: Power Resource [FN01] (off)
Feb 14 20:22:31 linux-ytaf kernel: ACPI: Power Resource [FN02] (off)
Feb 14 20:22:31 linux-ytaf kernel: ACPI: Power Resource [FN03] (off)
Feb 14 20:22:31 linux-ytaf kernel: ACPI: Power Resource [FN04] (off)
Feb 14 20:22:31 linux-ytaf kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
Feb 14 20:22:31 linux-ytaf kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Feb 14 20:22:31 linux-ytaf kernel: \_SB_.PCI0:_OSC invalid UUID
Feb 14 20:22:31 linux-ytaf kernel: _OSC request data:1 1f 0 
Feb 14 20:22:31 linux-ytaf kernel: acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
Feb 14 20:22:31 linux-ytaf kernel: PCI host bridge to bus 0000:00
Feb 14 20:22:31 linux-ytaf kernel: pci_bus 0000:00: root bus resource [bus 00-3e]
Feb 14 20:22:31 linux-ytaf kernel: pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
Feb 14 20:22:31 linux-ytaf kernel: pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
Feb 14 20:22:31 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
Feb 14 20:22:31 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff window]
Feb 14 20:22:31 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff window]
Feb 14 20:22:31 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff window]
Feb 14 20:22:31 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0xe0000000-0xfeafffff window]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:00.0: [8086:0100] type 00 class 0x060000
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:01.0: [8086:0101] type 01 class 0x060400
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:01.0: System wakeup disabled by ACPI
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:01.1: [8086:0105] type 01 class 0x060400
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:01.1: PME# supported from D0 D3hot D3cold
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:01.1: System wakeup disabled by ACPI
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:16.0: [8086:1c3a] type 00 class 0x078000
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:16.0: reg 0x10: [mem 0xf742c000-0xf742c00f 64bit]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:19.0: [8086:1503] type 00 class 0x020000
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:19.0: reg 0x10: [mem 0xf7400000-0xf741ffff]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:19.0: reg 0x14: [mem 0xf7429000-0xf7429fff]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:19.0: reg 0x18: [io  0xf040-0xf05f]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:19.0: PME# supported from D0 D3hot D3cold
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:19.0: System wakeup disabled by ACPI
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1a.0: [8086:1c2d] type 00 class 0x0c0320
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1a.0: reg 0x10: [mem 0xf7428000-0xf74283ff]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1a.0: System wakeup disabled by ACPI
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1b.0: [8086:1c20] type 00 class 0x040300
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1b.0: reg 0x10: [mem 0xf7420000-0xf7423fff 64bit]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1b.0: System wakeup disabled by ACPI
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.0: [8086:1c10] type 01 class 0x060400
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.0: System wakeup disabled by ACPI
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.4: [8086:1c18] type 01 class 0x060400
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.4: System wakeup disabled by ACPI
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.5: [8086:1c1a] type 01 class 0x060400
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.5: System wakeup disabled by ACPI
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.6: [8086:1c1c] type 01 class 0x060400
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.6: PME# supported from D0 D3hot D3cold
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.6: System wakeup disabled by ACPI
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1d.0: [8086:1c26] type 00 class 0x0c0320
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1d.0: reg 0x10: [mem 0xf7427000-0xf74273ff]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1d.0: System wakeup disabled by ACPI
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1f.0: [8086:1c44] type 00 class 0x060100
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1f.2: [8086:1c02] type 00 class 0x010601
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x10: [io  0xf090-0xf097]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x14: [io  0xf080-0xf083]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x18: [io  0xf070-0xf077]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x1c: [io  0xf060-0xf063]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x20: [io  0xf020-0xf03f]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x24: [mem 0xf7426000-0xf74267ff]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1f.2: PME# supported from D3hot
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1f.3: [8086:1c22] type 00 class 0x0c0500
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1f.3: reg 0x10: [mem 0xf7425000-0xf74250ff 64bit]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1f.3: reg 0x20: [io  0x0580-0x059f]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:02:00.0: [10de:1183] type 00 class 0x030000
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:02:00.0: reg 0x10: [mem 0xf6000000-0xf6ffffff]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:02:00.0: reg 0x14: [mem 0xe8000000-0xefffffff 64bit pref]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:02:00.0: reg 0x1c: [mem 0xf0000000-0xf1ffffff 64bit pref]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:02:00.0: reg 0x24: [io  0xe000-0xe07f]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:02:00.0: reg 0x30: [mem 0xf7000000-0xf707ffff pref]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:02:00.1: [10de:0e0a] type 00 class 0x040300
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:02:00.1: reg 0x10: [mem 0xf7080000-0xf7083fff]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:01.1: PCI bridge to [bus 02]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [io  0xe000-0xefff]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xf6000000-0xf70fffff]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xe8000000-0xf1ffffff 64bit pref]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.0: PCI bridge to [bus 03]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:04:00.0: [1b21:1042] type 00 class 0x0c0330
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:04:00.0: reg 0x10: [mem 0xf7300000-0xf7307fff 64bit]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:04:00.0: PME# supported from D3hot D3cold
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:04:00.0: System wakeup disabled by ACPI
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.4: PCI bridge to [bus 04]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.4:   bridge window [mem 0xf7300000-0xf73fffff]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:05:00.0: [1b21:1042] type 00 class 0x0c0330
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:05:00.0: reg 0x10: [mem 0xf7200000-0xf7207fff 64bit]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:05:00.0: PME# supported from D3hot D3cold
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:05:00.0: System wakeup disabled by ACPI
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.5: PCI bridge to [bus 05]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.5:   bridge window [mem 0xf7200000-0xf72fffff]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:06:00.0: [197b:2362] type 00 class 0x010185
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:06:00.0: reg 0x10: [io  0xd040-0xd047]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:06:00.0: reg 0x14: [io  0xd030-0xd033]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:06:00.0: reg 0x18: [io  0xd020-0xd027]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:06:00.0: reg 0x1c: [io  0xd010-0xd013]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:06:00.0: reg 0x20: [io  0xd000-0xd00f]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:06:00.0: reg 0x24: [mem 0xf7110000-0xf71101ff]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:06:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:06:00.0: PME# supported from D3hot
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:06:00.0: System wakeup disabled by ACPI
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.6: PCI bridge to [bus 06]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [io  0xd000-0xdfff]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [mem 0xf7100000-0xf71fffff]
Feb 14 20:22:31 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15)
Feb 14 20:22:31 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *10 11 12 14 15)
Feb 14 20:22:31 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Feb 14 20:22:31 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs *3 4 5 6 10 11 12 14 15)
Feb 14 20:22:31 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 *4 5 6 10 11 12 14 15)
Feb 14 20:22:31 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
Feb 14 20:22:31 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 *11 12 14 15)
Feb 14 20:22:31 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 *10 11 12 14 15)
Feb 14 20:22:31 linux-ytaf kernel: ACPI: Enabled 6 GPEs in block 00 to 3F
Feb 14 20:22:31 linux-ytaf kernel: ACPI : EC: GPE = 0x18, I/O: command/status = 0x66, data = 0x62
Feb 14 20:22:31 linux-ytaf kernel: vgaarb: setting as boot device: PCI:0000:02:00.0
Feb 14 20:22:31 linux-ytaf kernel: vgaarb: device added: PCI:0000:02:00.0,decodes=io+mem,owns=io+mem,locks=none
Feb 14 20:22:31 linux-ytaf kernel: vgaarb: loaded
Feb 14 20:22:31 linux-ytaf kernel: vgaarb: bridge control possible 0000:02:00.0
Feb 14 20:22:31 linux-ytaf kernel: SCSI subsystem initialized
Feb 14 20:22:31 linux-ytaf kernel: libata version 3.00 loaded.
Feb 14 20:22:31 linux-ytaf kernel: PCI: Using ACPI for IRQ routing
Feb 14 20:22:31 linux-ytaf kernel: PCI: pci_cache_line_size set to 64 bytes
Feb 14 20:22:31 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0009f000-0x0009ffff]
Feb 14 20:22:31 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c2ef018-0x0fffffff]
Feb 14 20:22:31 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c81c018-0x0fffffff]
Feb 14 20:22:31 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c82c018-0x0fffffff]
Feb 14 20:22:31 linux-ytaf kernel: e820: reserve RAM buffer [mem 0xdeb8f000-0xdfffffff]
Feb 14 20:22:31 linux-ytaf kernel: e820: reserve RAM buffer [mem 0xdf800000-0xdfffffff]
Feb 14 20:22:31 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x21f000000-0x21fffffff]
Feb 14 20:22:31 linux-ytaf kernel: NetLabel: Initializing
Feb 14 20:22:31 linux-ytaf kernel: NetLabel:  domain hash size = 128
Feb 14 20:22:31 linux-ytaf kernel: NetLabel:  protocols = UNLABELED CIPSOv4
Feb 14 20:22:31 linux-ytaf kernel: NetLabel:  unlabeled traffic allowed by default
Feb 14 20:22:31 linux-ytaf kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Feb 14 20:22:31 linux-ytaf kernel: hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Feb 14 20:22:31 linux-ytaf kernel: Switched to clocksource hpet
Feb 14 20:22:31 linux-ytaf kernel: AppArmor: AppArmor Filesystem Enabled
Feb 14 20:22:31 linux-ytaf kernel: pnp: PnP ACPI init
Feb 14 20:22:31 linux-ytaf kernel: system 00:00: [mem 0xfed40000-0xfed44fff] has been reserved
Feb 14 20:22:31 linux-ytaf kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
Feb 14 20:22:31 linux-ytaf kernel: system 00:01: [io  0x0680-0x069f] has been reserved
Feb 14 20:22:31 linux-ytaf kernel: system 00:01: [io  0x0200-0x020f] has been reserved
Feb 14 20:22:31 linux-ytaf kernel: system 00:01: [io  0xffff] has been reserved
Feb 14 20:22:31 linux-ytaf kernel: system 00:01: [io  0xffff] has been reserved
Feb 14 20:22:31 linux-ytaf kernel: system 00:01: [io  0x0400-0x0453] could not be reserved
Feb 14 20:22:31 linux-ytaf kernel: system 00:01: [io  0x0458-0x047f] has been reserved
Feb 14 20:22:31 linux-ytaf kernel: system 00:01: [io  0x0500-0x057f] has been reserved
Feb 14 20:22:31 linux-ytaf kernel: system 00:01: [io  0x164e-0x164f] has been reserved
Feb 14 20:22:31 linux-ytaf kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 20:22:31 linux-ytaf kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Feb 14 20:22:31 linux-ytaf kernel: system 00:03: [io  0x0454-0x0457] has been reserved
Feb 14 20:22:31 linux-ytaf kernel: system 00:03: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
Feb 14 20:22:31 linux-ytaf kernel: system 00:04: [io  0x0290-0x029f] has been reserved
Feb 14 20:22:31 linux-ytaf kernel: system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 20:22:31 linux-ytaf kernel: system 00:05: [io  0x04d0-0x04d1] has been reserved
Feb 14 20:22:31 linux-ytaf kernel: system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 20:22:31 linux-ytaf kernel: system 00:06: [mem 0xfed1c000-0xfed1ffff] has been reserved
Feb 14 20:22:31 linux-ytaf kernel: system 00:06: [mem 0xfed10000-0xfed17fff] has been reserved
Feb 14 20:22:31 linux-ytaf kernel: system 00:06: [mem 0xfed18000-0xfed18fff] has been reserved
Feb 14 20:22:31 linux-ytaf kernel: system 00:06: [mem 0xfed19000-0xfed19fff] has been reserved
Feb 14 20:22:31 linux-ytaf kernel: system 00:06: [mem 0xf8000000-0xfbffffff] has been reserved
Feb 14 20:22:31 linux-ytaf kernel: system 00:06: [mem 0xfed20000-0xfed3ffff] has been reserved
Feb 14 20:22:31 linux-ytaf kernel: system 00:06: [mem 0xfed90000-0xfed93fff] has been reserved
Feb 14 20:22:31 linux-ytaf kernel: system 00:06: [mem 0xfed45000-0xfed8ffff] has been reserved
Feb 14 20:22:31 linux-ytaf kernel: system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Feb 14 20:22:31 linux-ytaf kernel: system 00:06: [mem 0xfee00000-0xfeefffff] could not be reserved
Feb 14 20:22:31 linux-ytaf kernel: system 00:06: [mem 0xe0000000-0xe0000fff] has been reserved
Feb 14 20:22:31 linux-ytaf kernel: system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 14 20:22:31 linux-ytaf kernel: pnp: PnP ACPI: found 7 devices
Feb 14 20:22:31 linux-ytaf kernel: clocksource acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.0: bridge window [io  0x1000-0x0fff] to [bus 03] add_size 1000
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 03] add_size 200000 add_align 100000
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff] to [bus 03] add_size 200000 add_align 100000
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.0: res[14]=[mem 0x00100000-0x000fffff] res_to_dev_res add_size 200000 min_align 100000
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.0: res[14]=[mem 0x00100000-0x002fffff] res_to_dev_res add_size 200000 min_align 100000
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x000fffff 64bit pref] res_to_dev_res add_size 200000 min_align 100000
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x002fffff 64bit pref] res_to_dev_res add_size 200000 min_align 100000
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.0: res[13]=[io  0x1000-0x0fff] res_to_dev_res add_size 1000 min_align 1000
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.0: res[13]=[io  0x1000-0x1fff] res_to_dev_res add_size 1000 min_align 1000
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.0: BAR 14: assigned [mem 0xe0100000-0xe02fffff]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.0: BAR 15: assigned [mem 0xe0300000-0xe04fffff 64bit pref]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.0: BAR 13: assigned [io  0x2000-0x2fff]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:01.1: PCI bridge to [bus 02]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [io  0xe000-0xefff]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xf6000000-0xf70fffff]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xe8000000-0xf1ffffff 64bit pref]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.0: PCI bridge to [bus 03]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.0:   bridge window [io  0x2000-0x2fff]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.0:   bridge window [mem 0xe0100000-0xe02fffff]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.0:   bridge window [mem 0xe0300000-0xe04fffff 64bit pref]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.4: PCI bridge to [bus 04]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.4:   bridge window [mem 0xf7300000-0xf73fffff]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.5: PCI bridge to [bus 05]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.5:   bridge window [mem 0xf7200000-0xf72fffff]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:06:00.0: BAR 6: assigned [mem 0xf7100000-0xf710ffff pref]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.6: PCI bridge to [bus 06]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [io  0xd000-0xdfff]
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [mem 0xf7100000-0xf71fffff]
Feb 14 20:22:31 linux-ytaf kernel: pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
Feb 14 20:22:31 linux-ytaf kernel: pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
Feb 14 20:22:31 linux-ytaf kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
Feb 14 20:22:31 linux-ytaf kernel: pci_bus 0000:00: resource 7 [mem 0x000d4000-0x000d7fff window]
Feb 14 20:22:31 linux-ytaf kernel: pci_bus 0000:00: resource 8 [mem 0x000d8000-0x000dbfff window]
Feb 14 20:22:31 linux-ytaf kernel: pci_bus 0000:00: resource 9 [mem 0x000dc000-0x000dffff window]
Feb 14 20:22:31 linux-ytaf kernel: pci_bus 0000:00: resource 10 [mem 0xe0000000-0xfeafffff window]
Feb 14 20:22:31 linux-ytaf kernel: pci_bus 0000:02: resource 0 [io  0xe000-0xefff]
Feb 14 20:22:31 linux-ytaf kernel: pci_bus 0000:02: resource 1 [mem 0xf6000000-0xf70fffff]
Feb 14 20:22:31 linux-ytaf kernel: pci_bus 0000:02: resource 2 [mem 0xe8000000-0xf1ffffff 64bit pref]
Feb 14 20:22:31 linux-ytaf kernel: pci_bus 0000:03: resource 0 [io  0x2000-0x2fff]
Feb 14 20:22:31 linux-ytaf kernel: pci_bus 0000:03: resource 1 [mem 0xe0100000-0xe02fffff]
Feb 14 20:22:31 linux-ytaf kernel: pci_bus 0000:03: resource 2 [mem 0xe0300000-0xe04fffff 64bit pref]
Feb 14 20:22:31 linux-ytaf kernel: pci_bus 0000:04: resource 1 [mem 0xf7300000-0xf73fffff]
Feb 14 20:22:31 linux-ytaf kernel: pci_bus 0000:05: resource 1 [mem 0xf7200000-0xf72fffff]
Feb 14 20:22:31 linux-ytaf kernel: pci_bus 0000:06: resource 0 [io  0xd000-0xdfff]
Feb 14 20:22:31 linux-ytaf kernel: pci_bus 0000:06: resource 1 [mem 0xf7100000-0xf71fffff]
Feb 14 20:22:31 linux-ytaf kernel: NET: Registered protocol family 2
Feb 14 20:22:31 linux-ytaf kernel: TCP established hash table entries: 65536 (order: 7, 524288 bytes)
Feb 14 20:22:31 linux-ytaf kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Feb 14 20:22:31 linux-ytaf kernel: TCP: Hash tables configured (established 65536 bind 65536)
Feb 14 20:22:31 linux-ytaf kernel: UDP hash table entries: 4096 (order: 5, 131072 bytes)
Feb 14 20:22:31 linux-ytaf kernel: UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
Feb 14 20:22:31 linux-ytaf kernel: NET: Registered protocol family 1
Feb 14 20:22:31 linux-ytaf kernel: pci 0000:02:00.0: Video device with shadowed ROM
Feb 14 20:22:31 linux-ytaf kernel: PCI: CLS 64 bytes, default 64
Feb 14 20:22:31 linux-ytaf kernel: Unpacking initramfs...
Feb 14 20:22:31 linux-ytaf kernel: Freeing initrd memory: 8296K (ffff8800007e1000 - ffff880000ffb000)
Feb 14 20:22:31 linux-ytaf kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Feb 14 20:22:31 linux-ytaf kernel: software IO TLB [mem 0xdab8f000-0xdeb8f000] (64MB) mapped at [ffff8800dab8f000-ffff8800deb8efff]
Feb 14 20:22:31 linux-ytaf kernel: RAPL PMU detected, API unit is 2^-32 Joules, 3 fixed counters 163840 ms ovfl timer
Feb 14 20:22:31 linux-ytaf kernel: hw unit of domain pp0-core 2^-16 Joules
Feb 14 20:22:31 linux-ytaf kernel: hw unit of domain package 2^-16 Joules
Feb 14 20:22:31 linux-ytaf kernel: hw unit of domain pp1-gpu 2^-16 Joules
Feb 14 20:22:31 linux-ytaf kernel: microcode: CPU0 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 20:22:31 linux-ytaf kernel: microcode: CPU1 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 20:22:31 linux-ytaf kernel: microcode: CPU2 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 20:22:31 linux-ytaf kernel: microcode: CPU3 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 20:22:31 linux-ytaf kernel: microcode: CPU4 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 20:22:31 linux-ytaf kernel: microcode: CPU5 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 20:22:31 linux-ytaf kernel: microcode: CPU6 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 20:22:31 linux-ytaf kernel: microcode: CPU7 sig=0x206a7, pf=0x2, revision=0x29
Feb 14 20:22:31 linux-ytaf kernel: microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Feb 14 20:22:31 linux-ytaf kernel: Scanning for low memory corruption every 60 seconds
Feb 14 20:22:31 linux-ytaf kernel: futex hash table entries: 2048 (order: 5, 131072 bytes)
Feb 14 20:22:31 linux-ytaf kernel: audit: initializing netlink subsys (disabled)
Feb 14 20:22:31 linux-ytaf kernel: audit: type=2000 audit(1455481349.000:1): initialized
Feb 14 20:22:31 linux-ytaf kernel: HugeTLB registered 2 MB page size, pre-allocated 0 pages
Feb 14 20:22:31 linux-ytaf kernel: zpool: loaded
Feb 14 20:22:31 linux-ytaf kernel: zbud: loaded
Feb 14 20:22:31 linux-ytaf kernel: VFS: Disk quotas dquot_6.6.0
Feb 14 20:22:31 linux-ytaf kernel: VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Feb 14 20:22:31 linux-ytaf kernel: Key type big_key registered
Feb 14 20:22:31 linux-ytaf kernel: Key type asymmetric registered
Feb 14 20:22:31 linux-ytaf kernel: Asymmetric key parser 'x509' registered
Feb 14 20:22:31 linux-ytaf kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Feb 14 20:22:31 linux-ytaf kernel: io scheduler noop registered
Feb 14 20:22:31 linux-ytaf kernel: io scheduler deadline registered
Feb 14 20:22:31 linux-ytaf kernel: io scheduler cfq registered (default)
Feb 14 20:22:31 linux-ytaf kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Feb 14 20:22:31 linux-ytaf kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Feb 14 20:22:31 linux-ytaf kernel: efifb: probing for efifb
Feb 14 20:22:31 linux-ytaf kernel: efifb: framebuffer at 0xf1000000, mapped to 0xffffc90001000000, using 1876k, total 1875k
Feb 14 20:22:31 linux-ytaf kernel: efifb: mode is 800x600x32, linelength=3200, pages=1
Feb 14 20:22:31 linux-ytaf kernel: efifb: scrolling: redraw
Feb 14 20:22:31 linux-ytaf kernel: efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Feb 14 20:22:31 linux-ytaf kernel: Console: switching to colour frame buffer device 100x37
Feb 14 20:22:31 linux-ytaf kernel: fb0: EFI VGA frame buffer device
Feb 14 20:22:31 linux-ytaf kernel: intel_idle: MWAIT substates: 0x1120
Feb 14 20:22:31 linux-ytaf kernel: intel_idle: v0.4 model 0x2A
Feb 14 20:22:31 linux-ytaf kernel: intel_idle: lapic_timer_reliable_states 0xffffffff
Feb 14 20:22:31 linux-ytaf kernel: GHES: HEST is not enabled!
Feb 14 20:22:31 linux-ytaf kernel: Serial: 8250/16550 driver, 32 ports, IRQ sharing disabled
Feb 14 20:22:31 linux-ytaf kernel: Non-volatile memory driver v1.3
Feb 14 20:22:31 linux-ytaf kernel: Linux agpgart interface v0.103
Feb 14 20:22:31 linux-ytaf kernel: ahci 0000:00:1f.2: version 3.0
Feb 14 20:22:31 linux-ytaf kernel: ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x7 impl SATA mode
Feb 14 20:22:31 linux-ytaf kernel: ahci 0000:00:1f.2: flags: 64bit ncq led clo pio slum part ems apst 
Feb 14 20:22:31 linux-ytaf kernel: scsi host0: ahci
Feb 14 20:22:31 linux-ytaf kernel: scsi host1: ahci
Feb 14 20:22:31 linux-ytaf kernel: scsi host2: ahci
Feb 14 20:22:31 linux-ytaf kernel: scsi host3: ahci
Feb 14 20:22:31 linux-ytaf kernel: scsi host4: ahci
Feb 14 20:22:31 linux-ytaf kernel: scsi host5: ahci
Feb 14 20:22:31 linux-ytaf kernel: ata1: SATA max UDMA/133 abar m2048@0xf7426000 port 0xf7426100 irq 26
Feb 14 20:22:31 linux-ytaf kernel: ata2: SATA max UDMA/133 abar m2048@0xf7426000 port 0xf7426180 irq 26
Feb 14 20:22:31 linux-ytaf kernel: ata3: SATA max UDMA/133 abar m2048@0xf7426000 port 0xf7426200 irq 26
Feb 14 20:22:31 linux-ytaf kernel: ata4: DUMMY
Feb 14 20:22:31 linux-ytaf kernel: ata5: DUMMY
Feb 14 20:22:31 linux-ytaf kernel: ata6: DUMMY
Feb 14 20:22:31 linux-ytaf kernel: ahci 0000:06:00.0: AHCI 0001.0100 32 slots 2 ports 3 Gbps 0x3 impl SATA mode
Feb 14 20:22:31 linux-ytaf kernel: ahci 0000:06:00.0: flags: 64bit ncq pm led clo pmp pio slum part 
Feb 14 20:22:31 linux-ytaf kernel: scsi host6: ahci
Feb 14 20:22:31 linux-ytaf kernel: scsi host7: ahci
Feb 14 20:22:31 linux-ytaf kernel: ata7: SATA max UDMA/133 abar m512@0xf7110000 port 0xf7110100 irq 18
Feb 14 20:22:31 linux-ytaf kernel: ata8: SATA max UDMA/133 abar m512@0xf7110000 port 0xf7110180 irq 18
Feb 14 20:22:31 linux-ytaf kernel: i8042: PNP: No PS/2 controller found. Probing ports directly.
Feb 14 20:22:31 linux-ytaf kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Feb 14 20:22:31 linux-ytaf kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Feb 14 20:22:31 linux-ytaf kernel: mousedev: PS/2 mouse device common for all mice
Feb 14 20:22:31 linux-ytaf kernel: rtc_cmos 00:02: RTC can wake from S4
Feb 14 20:22:31 linux-ytaf kernel: rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Feb 14 20:22:31 linux-ytaf kernel: rtc_cmos 00:02: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
Feb 14 20:22:31 linux-ytaf kernel: Intel P-state driver initializing.
Feb 14 20:22:31 linux-ytaf kernel: ledtrig-cpu: registered to indicate activity on CPUs
Feb 14 20:22:31 linux-ytaf kernel: EFI Variables Facility v0.08 2004-May-17
Feb 14 20:22:31 linux-ytaf kernel: hidraw: raw HID events driver (C) Jiri Kosina
Feb 14 20:22:31 linux-ytaf kernel: NET: Registered protocol family 10
Feb 14 20:22:31 linux-ytaf kernel: registered taskstats version 1
Feb 14 20:22:31 linux-ytaf kernel: Key type encrypted registered
Feb 14 20:22:31 linux-ytaf kernel: AppArmor: AppArmor sha1 policy hashing enabled
Feb 14 20:22:31 linux-ytaf kernel:   Magic number: 4:970:396
Feb 14 20:22:31 linux-ytaf kernel: rtc_cmos 00:02: setting system clock to 2016-02-14 20:22:29 UTC (1455481349)
Feb 14 20:22:31 linux-ytaf kernel: PM: Checking hibernation image partition /dev/sdb2
Feb 14 20:22:31 linux-ytaf kernel: ata8: SATA link down (SStatus 0 SControl 300)
Feb 14 20:22:31 linux-ytaf kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 14 20:22:31 linux-ytaf kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Feb 14 20:22:31 linux-ytaf kernel: ata7: SATA link down (SStatus 0 SControl 300)
Feb 14 20:22:31 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 20:22:31 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff8802160b7e50), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 20:22:31 linux-ytaf kernel: ata1.00: ATA-9: SAMSUNG SSD 830 Series, CXM03B1Q, max UDMA/133
Feb 14 20:22:31 linux-ytaf kernel: ata1.00: 500118192 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Feb 14 20:22:31 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 20:22:31 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff8802160b7e50), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 20:22:31 linux-ytaf kernel: ata1.00: configured for UDMA/133
Feb 14 20:22:31 linux-ytaf kernel: scsi 0:0:0:0: Direct-Access     ATA      SAMSUNG SSD 830  3B1Q PQ: 0 ANSI: 5
Feb 14 20:22:31 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 20:22:31 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff8802160b7d60), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 20:22:31 linux-ytaf kernel: ata3.00: ATAPI: TSSTcorp CDDVDW SH-S223C, SB05, max UDMA/66
Feb 14 20:22:31 linux-ytaf kernel: ata3.00: applying bridge limits
Feb 14 20:22:31 linux-ytaf kernel: sd 0:0:0:0: [sda] 500118192 512-byte logical blocks: (256 GB/238 GiB)
Feb 14 20:22:31 linux-ytaf kernel: sd 0:0:0:0: [sda] Write Protect is off
Feb 14 20:22:31 linux-ytaf kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 14 20:22:31 linux-ytaf kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 14 20:22:31 linux-ytaf kernel:  sda: sda1 sda2 sda3 sda4
Feb 14 20:22:31 linux-ytaf kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Feb 14 20:22:31 linux-ytaf kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 14 20:22:31 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 20:22:31 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff8802160b7dd8), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 20:22:31 linux-ytaf kernel: ata2.00: ATA-8: TOSHIBA HDWD110, MS2OA8J0, max UDMA/133
Feb 14 20:22:31 linux-ytaf kernel: ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Feb 14 20:22:31 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 20:22:31 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff8802160b7dd8), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 20:22:31 linux-ytaf kernel: ata2.00: configured for UDMA/133
Feb 14 20:22:31 linux-ytaf kernel: scsi 1:0:0:0: Direct-Access     ATA      TOSHIBA HDWD110  A8J0 PQ: 0 ANSI: 5
Feb 14 20:22:31 linux-ytaf kernel: sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
Feb 14 20:22:31 linux-ytaf kernel: sd 1:0:0:0: [sdb] 4096-byte physical blocks
Feb 14 20:22:31 linux-ytaf kernel: sd 1:0:0:0: [sdb] Write Protect is off
Feb 14 20:22:31 linux-ytaf kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Feb 14 20:22:31 linux-ytaf kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 14 20:22:31 linux-ytaf kernel:  sdb: sdb1 sdb2 sdb3 sdb4
Feb 14 20:22:31 linux-ytaf kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
Feb 14 20:22:31 linux-ytaf kernel: tsc: Refined TSC clocksource calibration: 3411.127 MHz
Feb 14 20:22:31 linux-ytaf kernel: clocksource tsc: mask: 0xffffffffffffffff max_cycles: 0x312b5e33c4e, max_idle_ns: 440795327319 ns
Feb 14 20:22:31 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 14 20:22:31 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff8802160b7d60), AE_NOT_FOUND (20150410/psparse-536)
Feb 14 20:22:31 linux-ytaf kernel: ata3.00: configured for UDMA/66
Feb 14 20:22:31 linux-ytaf kernel: scsi 2:0:0:0: CD-ROM            TSSTcorp CDDVDW SH-S223C  SB05 PQ: 0 ANSI: 5
Feb 14 20:22:31 linux-ytaf kernel: PM: Hibernation image partition 8:18 present
Feb 14 20:22:31 linux-ytaf kernel: PM: Looking for hibernation image.
Feb 14 20:22:31 linux-ytaf kernel: Switched to clocksource tsc
Feb 14 20:22:31 linux-ytaf kernel: PM: Image not found (code -22)
Feb 14 20:22:31 linux-ytaf kernel: PM: Hibernation image not present or could not be loaded.
Feb 14 20:22:31 linux-ytaf kernel: Freeing unused kernel memory: 1560K (ffffffff81f11000 - ffffffff82097000)
Feb 14 20:22:31 linux-ytaf kernel: Write protecting the kernel read-only data: 14336k
Feb 14 20:22:31 linux-ytaf kernel: Freeing unused kernel memory: 1632K (ffff88000d668000 - ffff88000d800000)
Feb 14 20:22:31 linux-ytaf kernel: Freeing unused kernel memory: 1296K (ffff88000dcbc000 - ffff88000de00000)
Feb 14 20:22:31 linux-ytaf systemd[1]: RTC configured in localtime, applying delta of 60 minutes to system time.
Feb 14 20:22:31 linux-ytaf kernel: random: systemd urandom read with 22 bits of entropy available
Feb 14 20:22:31 linux-ytaf kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Feb 14 20:22:31 linux-ytaf kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0
Feb 14 20:22:31 linux-ytaf kernel: scsi 2:0:0:0: Attached scsi generic sg2 type 5
Feb 14 20:22:31 linux-ytaf systemd-journal[187]: Journal started
Feb 14 20:22:31 linux-ytaf dracut-cmdline[181]: dracut-42.1 dracut-037-68.1
Feb 14 20:22:31 linux-ytaf systemd-udevd[251]: Network interface NamePolicy= disabled on kernel commandline, ignoring.
Feb 14 20:22:31 linux-ytaf kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3
Feb 14 20:22:31 linux-ytaf kernel: ACPI: Power Button [PWRB]
Feb 14 20:22:31 linux-ytaf kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
Feb 14 20:22:31 linux-ytaf kernel: ACPI: Power Button [PWRF]
Feb 14 20:22:31 linux-ytaf kernel: wmi: Mapper loaded
Feb 14 20:22:31 linux-ytaf kernel: ACPI: bus type USB registered
Feb 14 20:22:31 linux-ytaf kernel: usbcore: registered new interface driver usbfs
Feb 14 20:22:31 linux-ytaf kernel: usbcore: registered new interface driver hub
Feb 14 20:22:31 linux-ytaf kernel: usbcore: registered new device driver usb
Feb 14 20:22:31 linux-ytaf kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Feb 14 20:22:31 linux-ytaf kernel: ehci-pci: EHCI PCI platform driver
Feb 14 20:22:31 linux-ytaf kernel: ehci-pci 0000:00:1a.0: EHCI Host Controller
Feb 14 20:22:31 linux-ytaf kernel: ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Feb 14 20:22:31 linux-ytaf kernel: ehci-pci 0000:00:1a.0: debug port 2
Feb 14 20:22:31 linux-ytaf kernel: ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Feb 14 20:22:31 linux-ytaf kernel: ehci-pci 0000:00:1a.0: irq 16, io mem 0xf7428000
Feb 14 20:22:31 linux-ytaf kernel: ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Feb 14 20:22:31 linux-ytaf kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 20:22:31 linux-ytaf kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 20:22:31 linux-ytaf kernel: usb usb1: Product: EHCI Host Controller
Feb 14 20:22:31 linux-ytaf kernel: usb usb1: Manufacturer: Linux 4.1.15-8-default ehci_hcd
Feb 14 20:22:31 linux-ytaf kernel: usb usb1: SerialNumber: 0000:00:1a.0
Feb 14 20:22:31 linux-ytaf kernel: hub 1-0:1.0: USB hub found
Feb 14 20:22:31 linux-ytaf kernel: hub 1-0:1.0: 2 ports detected
Feb 14 20:22:31 linux-ytaf kernel: xhci_hcd 0000:04:00.0: xHCI Host Controller
Feb 14 20:22:31 linux-ytaf kernel: xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 2
Feb 14 20:22:31 linux-ytaf kernel: sr 2:0:0:0: [sr0] scsi3-mmc drive: 52x/52x writer dvd-ram cd/rw xa/form2 cdda tray
Feb 14 20:22:31 linux-ytaf kernel: cdrom: Uniform CD-ROM driver Revision: 3.20
Feb 14 20:22:31 linux-ytaf kernel: sr 2:0:0:0: Attached scsi CD-ROM sr0
Feb 14 20:22:31 linux-ytaf kernel: xhci_hcd 0000:04:00.0: hcc params 0x0200f180 hci version 0x96 quirks 0x00080000
Feb 14 20:22:31 linux-ytaf kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 20:22:31 linux-ytaf kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 20:22:31 linux-ytaf kernel: usb usb2: Product: xHCI Host Controller
Feb 14 20:22:31 linux-ytaf kernel: usb usb2: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 20:22:31 linux-ytaf kernel: usb usb2: SerialNumber: 0000:04:00.0
Feb 14 20:22:31 linux-ytaf kernel: hub 2-0:1.0: USB hub found
Feb 14 20:22:31 linux-ytaf kernel: hub 2-0:1.0: 2 ports detected
Feb 14 20:22:31 linux-ytaf kernel: xhci_hcd 0000:04:00.0: xHCI Host Controller
Feb 14 20:22:31 linux-ytaf kernel: xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 3
Feb 14 20:22:31 linux-ytaf kernel: ehci-pci 0000:00:1d.0: EHCI Host Controller
Feb 14 20:22:31 linux-ytaf kernel: usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
Feb 14 20:22:31 linux-ytaf kernel: usb usb3: New USB device found, idVendor=1d6b, idProduct=0003
Feb 14 20:22:31 linux-ytaf kernel: usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 20:22:31 linux-ytaf kernel: usb usb3: Product: xHCI Host Controller
Feb 14 20:22:31 linux-ytaf kernel: usb usb3: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 20:22:31 linux-ytaf kernel: usb usb3: SerialNumber: 0000:04:00.0
Feb 14 20:22:31 linux-ytaf kernel: hub 3-0:1.0: USB hub found
Feb 14 20:22:31 linux-ytaf kernel: hub 3-0:1.0: 2 ports detected
Feb 14 20:22:31 linux-ytaf kernel: ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 4
Feb 14 20:22:31 linux-ytaf kernel: ehci-pci 0000:00:1d.0: debug port 2
Feb 14 20:22:31 linux-ytaf kernel: ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Feb 14 20:22:31 linux-ytaf kernel: ehci-pci 0000:00:1d.0: irq 23, io mem 0xf7427000
Feb 14 20:22:31 linux-ytaf kernel: ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Feb 14 20:22:31 linux-ytaf kernel: usb usb4: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 20:22:31 linux-ytaf kernel: usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 20:22:31 linux-ytaf kernel: usb usb4: Product: EHCI Host Controller
Feb 14 20:22:31 linux-ytaf kernel: usb usb4: Manufacturer: Linux 4.1.15-8-default ehci_hcd
Feb 14 20:22:31 linux-ytaf kernel: usb usb4: SerialNumber: 0000:00:1d.0
Feb 14 20:22:31 linux-ytaf kernel: hub 4-0:1.0: USB hub found
Feb 14 20:22:31 linux-ytaf kernel: hub 4-0:1.0: 2 ports detected
Feb 14 20:22:31 linux-ytaf kernel: xhci_hcd 0000:05:00.0: xHCI Host Controller
Feb 14 20:22:31 linux-ytaf kernel: xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 5
Feb 14 20:22:31 linux-ytaf kernel: xhci_hcd 0000:05:00.0: hcc params 0x0200f180 hci version 0x96 quirks 0x00080000
Feb 14 20:22:31 linux-ytaf kernel: usb usb5: New USB device found, idVendor=1d6b, idProduct=0002
Feb 14 20:22:31 linux-ytaf kernel: usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 20:22:31 linux-ytaf kernel: usb usb5: Product: xHCI Host Controller
Feb 14 20:22:31 linux-ytaf kernel: usb usb5: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 20:22:31 linux-ytaf kernel: usb usb5: SerialNumber: 0000:05:00.0
Feb 14 20:22:31 linux-ytaf kernel: hub 5-0:1.0: USB hub found
Feb 14 20:22:31 linux-ytaf kernel: hub 5-0:1.0: 2 ports detected
Feb 14 20:22:31 linux-ytaf kernel: xhci_hcd 0000:05:00.0: xHCI Host Controller
Feb 14 20:22:31 linux-ytaf kernel: xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 6
Feb 14 20:22:31 linux-ytaf kernel: usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
Feb 14 20:22:31 linux-ytaf kernel: usb usb6: New USB device found, idVendor=1d6b, idProduct=0003
Feb 14 20:22:31 linux-ytaf kernel: usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 14 20:22:31 linux-ytaf kernel: usb usb6: Product: xHCI Host Controller
Feb 14 20:22:31 linux-ytaf kernel: usb usb6: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 14 20:22:31 linux-ytaf kernel: usb usb6: SerialNumber: 0000:05:00.0
Feb 14 20:22:31 linux-ytaf kernel: hub 6-0:1.0: USB hub found
Feb 14 20:22:31 linux-ytaf kernel: hub 6-0:1.0: 2 ports detected
Feb 14 20:22:31 linux-ytaf kernel: raid6: sse2x1   gen() 11030 MB/s
Feb 14 20:22:31 linux-ytaf kernel: usb 1-1: new high-speed USB device number 2 using ehci-pci
Feb 14 20:22:31 linux-ytaf kernel: raid6: sse2x1   xor()  9018 MB/s
Feb 14 20:22:31 linux-ytaf kernel: usb 4-1: new high-speed USB device number 2 using ehci-pci
Feb 14 20:22:32 linux-ytaf kernel: raid6: sse2x2   gen() 14094 MB/s
Feb 14 20:22:32 linux-ytaf kernel: usb 1-1: New USB device found, idVendor=8087, idProduct=0024
Feb 14 20:22:32 linux-ytaf kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb 14 20:22:32 linux-ytaf kernel: hub 1-1:1.0: USB hub found
Feb 14 20:22:32 linux-ytaf kernel: hub 1-1:1.0: 6 ports detected
Feb 14 20:22:32 linux-ytaf kernel: raid6: sse2x2   xor() 10032 MB/s
Feb 14 20:22:32 linux-ytaf kernel: usb 5-2: new high-speed USB device number 2 using xhci_hcd
Feb 14 20:22:32 linux-ytaf kernel: usb 4-1: New USB device found, idVendor=8087, idProduct=0024
Feb 14 20:22:32 linux-ytaf kernel: usb 4-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb 14 20:22:32 linux-ytaf kernel: hub 4-1:1.0: USB hub found
Feb 14 20:22:32 linux-ytaf kernel: hub 4-1:1.0: 8 ports detected
Feb 14 20:22:32 linux-ytaf kernel: raid6: sse2x4   gen() 16264 MB/s
Feb 14 20:22:32 linux-ytaf kernel: raid6: sse2x4   xor() 12089 MB/s
Feb 14 20:22:32 linux-ytaf kernel: raid6: using algorithm sse2x4 gen() 16264 MB/s
Feb 14 20:22:32 linux-ytaf kernel: raid6: .... xor() 12089 MB/s, rmw enabled
Feb 14 20:22:32 linux-ytaf kernel: raid6: using ssse3x2 recovery algorithm
Feb 14 20:22:32 linux-ytaf kernel: xor: automatically using best checksumming function:
Feb 14 20:22:32 linux-ytaf kernel:    avx       : 31206.000 MB/sec
Feb 14 20:22:32 linux-ytaf kernel: Btrfs loaded, assert=on
Feb 14 20:22:32 linux-ytaf kernel: BTRFS: device fsid 21024970-7a27-4114-8525-d8dd026f23b6 devid 1 transid 703 /dev/sdb3
Feb 14 20:22:32 linux-ytaf kernel: usb 5-2: New USB device found, idVendor=0930, idProduct=6545
Feb 14 20:22:32 linux-ytaf kernel: usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 14 20:22:32 linux-ytaf kernel: usb 5-2: Product: TransMemory
Feb 14 20:22:32 linux-ytaf kernel: usb 5-2: Manufacturer: TOSHIBA
Feb 14 20:22:32 linux-ytaf kernel: usb 5-2: SerialNumber: C89CDCBF6D59EF4140000065
Feb 14 20:22:32 linux-ytaf kernel: usb-storage 5-2:1.0: USB Mass Storage device detected
Feb 14 20:22:32 linux-ytaf kernel: scsi host8: usb-storage 5-2:1.0
Feb 14 20:22:32 linux-ytaf kernel: usbcore: registered new interface driver usb-storage
Feb 14 20:22:32 linux-ytaf kernel: usbcore: registered new interface driver uas
Feb 14 20:22:32 linux-ytaf kernel: usb 1-1.4: new full-speed USB device number 3 using ehci-pci
Feb 14 20:22:32 linux-ytaf kernel: usb 4-1.1: new full-speed USB device number 3 using ehci-pci
Feb 14 20:22:32 linux-ytaf kernel: usb 4-1.1: New USB device found, idVendor=1532, idProduct=0109
Feb 14 20:22:32 linux-ytaf kernel: usb 4-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 14 20:22:32 linux-ytaf kernel: usb 4-1.1: Product: Razer Lycosa
Feb 14 20:22:32 linux-ytaf kernel: usb 4-1.1: Manufacturer: Razer
Feb 14 20:22:32 linux-ytaf kernel: usbcore: registered new interface driver usbhid
Feb 14 20:22:32 linux-ytaf kernel: usbhid: USB HID core driver
Feb 14 20:22:32 linux-ytaf kernel: input: Razer Razer Lycosa as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1:1.0/0003:1532:0109.0001/input/input5
Feb 14 20:22:32 linux-ytaf kernel: usb 1-1.4: New USB device found, idVendor=06a3, idProduct=0ccb
Feb 14 20:22:32 linux-ytaf kernel: usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 14 20:22:32 linux-ytaf kernel: usb 1-1.4: Product: Cyborg R.A.T.7 Mouse
Feb 14 20:22:32 linux-ytaf kernel: usb 1-1.4: Manufacturer: Saitek
Feb 14 20:22:32 linux-ytaf kernel: hid-generic 0003:1532:0109.0001: input,hidraw0: USB HID v1.10 Keyboard [Razer Razer Lycosa] on usb-0000:00:1d.0-1.1/input0
Feb 14 20:22:32 linux-ytaf kernel: input: Razer Razer Lycosa as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1:1.1/0003:1532:0109.0002/input/input6
Feb 14 20:22:32 linux-ytaf kernel: hid-generic 0003:1532:0109.0002: input,hidraw1: USB HID v1.10 Device [Razer Razer Lycosa] on usb-0000:00:1d.0-1.1/input1
Feb 14 20:22:33 linux-ytaf kernel: scsi 8:0:0:0: Direct-Access     TOSHIBA  TransMemory      PMAP PQ: 0 ANSI: 6
Feb 14 20:22:33 linux-ytaf kernel: sd 8:0:0:0: Attached scsi generic sg3 type 0
Feb 14 20:22:33 linux-ytaf kernel: sd 8:0:0:0: [sdc] 30228480 512-byte logical blocks: (15.4 GB/14.4 GiB)
Feb 14 20:22:33 linux-ytaf kernel: sd 8:0:0:0: [sdc] Write Protect is off
Feb 14 20:22:33 linux-ytaf kernel: sd 8:0:0:0: [sdc] Mode Sense: 45 00 00 00
Feb 14 20:22:33 linux-ytaf kernel: sd 8:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Feb 14 20:22:33 linux-ytaf kernel:  sdc: sdc1
Feb 14 20:22:33 linux-ytaf kernel: sd 8:0:0:0: [sdc] Attached SCSI removable disk
Feb 14 20:22:33 linux-ytaf kernel: PM: Starting manual resume from disk
Feb 14 20:22:33 linux-ytaf kernel: PM: Hibernation image partition 8:18 present
Feb 14 20:22:33 linux-ytaf kernel: PM: Looking for hibernation image.
Feb 14 20:22:33 linux-ytaf kernel: PM: Image not found (code -22)
Feb 14 20:22:33 linux-ytaf kernel: PM: Hibernation image not present or could not be loaded.
Feb 14 20:22:33 linux-ytaf kernel: BTRFS info (device sdb3): disk space caching is enabled
Feb 14 20:22:33 linux-ytaf kernel: BTRFS: has skinny extents
Feb 14 20:22:33 linux-ytaf systemd-journal[187]: Journal stopped
Feb 14 20:22:35 linux-ytaf systemd-journal[478]: Runtime journal is using 8.0M (max allowed 397.5M, trying to leave 596.3M free of 3.8G available → current limit 397.5M).
Feb 14 20:22:35 linux-ytaf systemd-journal[478]: Runtime journal is using 8.0M (max allowed 397.5M, trying to leave 596.3M free of 3.8G available → current limit 397.5M).
Feb 14 20:22:35 linux-ytaf kernel: random: nonblocking pool is initialized
Feb 14 20:22:35 linux-ytaf systemd[1]: RTC configured in localtime, applying delta of 60 minutes to system time.
Feb 14 20:22:35 linux-ytaf kernel: BTRFS info (device sdb3): disk space caching is enabled
Feb 14 20:22:35 linux-ytaf systemd-journal[478]: Journal started
Feb 14 20:22:34 linux-ytaf systemd[1]: Failed to configure loopback device: Permission denied
Feb 14 20:22:35 linux-ytaf systemd-udevd[506]: Network interface NamePolicy= disabled on kernel commandline, ignoring.
Feb 14 20:22:36 linux-ytaf kernel: thermal LNXTHERM:00: registered as thermal_zone0
Feb 14 20:22:36 linux-ytaf kernel: ACPI: Thermal Zone [TZ00] (28 C)
Feb 14 20:22:36 linux-ytaf kernel: thermal LNXTHERM:01: registered as thermal_zone1
Feb 14 20:22:36 linux-ytaf kernel: ACPI: Thermal Zone [TZ01] (30 C)
Feb 14 20:22:36 linux-ytaf kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Feb 14 20:22:36 linux-ytaf kernel: input: PC Speaker as /devices/platform/pcspkr/input/input7
Feb 14 20:22:36 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000580-0x000000000000059F conflicts with OpRegion 0x0000000000000580-0x000000000000058F (\_SB_.PCI0.SBUS.SMBI) (20150410/utaddress-254)
Feb 14 20:22:36 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000580-0x000000000000059F conflicts with OpRegion 0x0000000000000580-0x000000000000059F (\_SB_.PCI0.SMB_.SMIO) (20150410/utaddress-254)
Feb 14 20:22:36 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 20:22:36 linux-ytaf kernel: pps_core: LinuxPPS API ver. 1 registered
Feb 14 20:22:36 linux-ytaf kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
Feb 14 20:22:36 linux-ytaf kernel: PTP clock support registered
Feb 14 20:22:36 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20150410/utaddress-254)
Feb 14 20:22:36 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 20:22:36 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150410/utaddress-254)
Feb 14 20:22:36 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150410/utaddress-254)
Feb 14 20:22:36 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 20:22:36 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150410/utaddress-254)
Feb 14 20:22:36 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150410/utaddress-254)
Feb 14 20:22:36 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 20:22:36 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150410/utaddress-254)
Feb 14 20:22:36 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150410/utaddress-254)
Feb 14 20:22:36 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 14 20:22:36 linux-ytaf kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
Feb 14 20:22:36 linux-ytaf kernel: iTCO_vendor_support: vendor-support=0
Feb 14 20:22:36 linux-ytaf kernel: AVX version of gcm_enc/dec engaged.
Feb 14 20:22:36 linux-ytaf kernel: AES CTR mode by8 optimization enabled
Feb 14 20:22:36 linux-ytaf mtp-probe[644]: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4"
Feb 14 20:22:36 linux-ytaf mtp-probe[647]: checking bus 5, device 2: "/sys/devices/pci0000:00/0000:00:1c.5/0000:05:00.0/usb5/5-2"
Feb 14 20:22:36 linux-ytaf mtp-probe[642]: checking bus 4, device 3: "/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1"
Feb 14 20:22:36 linux-ytaf mtp-probe[644]: bus: 1, device: 3 was not an MTP device
Feb 14 20:22:36 linux-ytaf mtp-probe[647]: bus: 5, device: 2 was not an MTP device
Feb 14 20:22:36 linux-ytaf mtp-probe[642]: bus: 4, device: 3 was not an MTP device
Feb 14 20:22:36 linux-ytaf kernel: iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
Feb 14 20:22:36 linux-ytaf kernel: iTCO_wdt: Found a Cougar Point TCO device (Version=2, TCOBASE=0x0460)
Feb 14 20:22:36 linux-ytaf kernel: iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
Feb 14 20:22:36 linux-ytaf kernel: e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
Feb 14 20:22:36 linux-ytaf kernel: e1000e: Copyright(c) 1999 - 2014 Intel Corporation.
Feb 14 20:22:36 linux-ytaf kernel: e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
Feb 14 20:22:36 linux-ytaf kernel: input: Saitek Cyborg R.A.T.7 Mouse as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/0003:06A3:0CCB.0003/input/input8
Feb 14 20:22:36 linux-ytaf kernel: saitek 0003:06A3:0CCB.0003: input,hidraw2: USB HID v1.11 Mouse [Saitek Cyborg R.A.T.7 Mouse] on usb-0000:00:1a.0-1.4/input0
Feb 14 20:22:36 linux-ytaf kernel: [drm] Initialized drm 1.1.0 20060810
Feb 14 20:22:36 linux-ytaf kernel: asus_wmi: ASUS WMI generic driver loaded
Feb 14 20:22:36 linux-ytaf kernel: asus_wmi: Initialization: 0x0
Feb 14 20:22:36 linux-ytaf kernel: asus_wmi: BIOS WMI version: 0.9
Feb 14 20:22:36 linux-ytaf kernel: asus_wmi: SFUN value: 0x0
Feb 14 20:22:36 linux-ytaf kernel: input: Eee PC WMI hotkeys as /devices/platform/eeepc-wmi/input/input9
Feb 14 20:22:36 linux-ytaf kernel: asus_wmi: Disabling ACPI video driver
Feb 14 20:22:36 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: registered PHC clock
Feb 14 20:22:36 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) c8:60:00:09:38:76
Feb 14 20:22:36 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
Feb 14 20:22:36 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: FFFFFF-0FF
Feb 14 20:22:37 linux-ytaf kernel: nvidia: module license 'NVIDIA' taints kernel.
Feb 14 20:22:37 linux-ytaf kernel: Disabling lock debugging due to kernel taint
Feb 14 20:22:37 linux-ytaf kernel: vgaarb: device changed decodes: PCI:0000:02:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
Feb 14 20:22:37 linux-ytaf kernel: [drm] Initialized nvidia-drm 0.0.0 20150116 for 0000:02:00.0 on minor 0
Feb 14 20:22:37 linux-ytaf kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  352.79  Wed Jan 13 16:17:53 PST 2016
Feb 14 20:22:37 linux-ytaf kernel: snd_hda_intel 0000:00:1b.0: enabling device (0000 -> 0002)
Feb 14 20:22:37 linux-ytaf kernel: snd_hda_intel 0000:02:00.1: enabling device (0000 -> 0002)
Feb 14 20:22:37 linux-ytaf kernel: snd_hda_intel 0000:02:00.1: Disabling MSI
Feb 14 20:22:37 linux-ytaf kernel: snd_hda_intel 0000:02:00.1: Handle VGA-switcheroo audio client
Feb 14 20:22:37 linux-ytaf kernel: Adding 2104316k swap on /dev/sdb2.  Priority:-1 extents:1 across:2104316k FS
Feb 14 20:22:37 linux-ytaf kernel: nvidia_uvm: Loaded the UVM driver, major device number 247
Feb 14 20:22:37 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC889: line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line
Feb 14 20:22:37 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Feb 14 20:22:37 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
Feb 14 20:22:37 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
Feb 14 20:22:37 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    dig-out=0x11/0x1e
Feb 14 20:22:37 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    inputs:
Feb 14 20:22:37 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:      Front Mic=0x19
Feb 14 20:22:37 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:      Rear Mic=0x18
Feb 14 20:22:37 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:      Line=0x1a
Feb 14 20:22:37 linux-ytaf kernel: input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
Feb 14 20:22:37 linux-ytaf kernel: input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
Feb 14 20:22:37 linux-ytaf kernel: input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
Feb 14 20:22:37 linux-ytaf kernel: input: HDA Intel PCH Line Out Front as /devices/pci0000:00/0000:00:1b.0/sound/card0/input13
Feb 14 20:22:37 linux-ytaf kernel: input: HDA Intel PCH Line Out Surround as /devices/pci0000:00/0000:00:1b.0/sound/card0/input14
Feb 14 20:22:37 linux-ytaf kernel: input: HDA Intel PCH Line Out CLFE as /devices/pci0000:00/0000:00:1b.0/sound/card0/input15
Feb 14 20:22:37 linux-ytaf kernel: input: HDA Intel PCH Line Out Side as /devices/pci0000:00/0000:00:1b.0/sound/card0/input16
Feb 14 20:22:37 linux-ytaf kernel: FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Feb 14 20:22:38 linux-ytaf systemd-fsck[758]: /sbin/fsck.xfs: XFS file system.
Feb 14 20:22:38 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input17
Feb 14 20:22:38 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input18
Feb 14 20:22:38 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input19
Feb 14 20:22:38 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input20
Feb 14 20:22:38 linux-ytaf kernel: SGI XFS with ACLs, security attributes, realtime, no debug enabled
Feb 14 20:22:38 linux-ytaf kernel: XFS (sdb4): Mounting V5 Filesystem
Feb 14 20:22:38 linux-ytaf kernel: XFS (sdb4): Ending clean mount
Feb 14 20:22:39 linux-ytaf systemd-journal[478]: Permanent journal is using 96.0M (max allowed 4.0G, trying to leave 4.0G free of 32.1G available → current limit 4.0G).
Feb 14 20:22:39 linux-ytaf systemd-journal[478]: Time spent on flushing to /var is 406.219ms for 934 entries.
Feb 14 20:22:40 linux-ytaf kernel: audit: type=1305 audit(1455477758.783:2): audit_pid=848 old=0 auid=4294967295 ses=4294967295 res=1
Feb 14 20:22:38 linux-ytaf auditd[848]: Started dispatcher: /sbin/audispd pid: 858
Feb 14 20:22:38 linux-ytaf audispd[858]: priority_boost_parser called with: 4
Feb 14 20:22:38 linux-ytaf audispd[858]: max_restarts_parser called with: 10
Feb 14 20:22:38 linux-ytaf audispd[858]: No plugins found, exiting
Feb 14 20:22:38 linux-ytaf auditd[848]: Init complete, auditd 2.3.6 listening for events (startup state enable)
Feb 14 20:22:40 linux-ytaf auditctl[849]: No rules
Feb 14 20:22:40 linux-ytaf auditctl[849]: AUDIT_STATUS: enabled=0 flag=1 pid=0 rate_limit=0 backlog_limit=320 lost=0 backlog=0
Feb 14 20:22:40 linux-ytaf boot.apparmor[862]: Starting AppArmor ..done
Feb 14 20:22:40 linux-ytaf dbus-daemon[1030]: Unknown username "srvGeoClue" in message bus configuration file
Feb 14 20:22:40 linux-ytaf avahi-daemon[1031]: Found user 'avahi' (UID 486) and group 'avahi' (GID 485).
Feb 14 20:22:40 linux-ytaf avahi-daemon[1031]: Successfully dropped root privileges.
Feb 14 20:22:40 linux-ytaf avahi-daemon[1031]: avahi-daemon 0.6.31 starting up.
Feb 14 20:22:40 linux-ytaf avahi-daemon[1031]: Loading service file /etc/avahi/services/sftp-ssh.service.
Feb 14 20:22:40 linux-ytaf avahi-daemon[1031]: Loading service file /etc/avahi/services/ssh.service.
Feb 14 20:22:40 linux-ytaf avahi-daemon[1031]: Network interface enumeration completed.
Feb 14 20:22:40 linux-ytaf avahi-daemon[1031]: Registering HINFO record with values 'X86_64'/'LINUX'.
Feb 14 20:22:40 linux-ytaf avahi-daemon[1031]: Server startup complete. Host name is linux-ytaf.local. Local service cookie is 1051537151.
Feb 14 20:22:40 linux-ytaf avahi-daemon[1031]: Service "linux-ytaf" (/etc/avahi/services/ssh.service) successfully established.
Feb 14 20:22:40 linux-ytaf avahi-daemon[1031]: Service "linux-ytaf" (/etc/avahi/services/sftp-ssh.service) successfully established.
Feb 14 20:22:40 linux-ytaf smartd[1037]: smartd 6.2 2013-11-07 r3856 [x86_64-linux-4.1.15-8-default] (SUSE RPM)
Feb 14 20:22:40 linux-ytaf smartd[1037]: Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
Feb 14 20:22:40 linux-ytaf smartd[1037]: Opened configuration file /etc/smartd.conf
Feb 14 20:22:40 linux-ytaf smartd[1037]: Drive: DEVICESCAN, implied '-a' Directive on line 26 of file /etc/smartd.conf
Feb 14 20:22:40 linux-ytaf smartd[1037]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
Feb 14 20:22:40 linux-ytaf smartd[1037]: Device: /dev/sda, type changed from 'scsi' to 'sat'
Feb 14 20:22:40 linux-ytaf smartd[1037]: Device: /dev/sda [SAT], opened
Feb 14 20:22:40 linux-ytaf smartd[1037]: Device: /dev/sda [SAT], SAMSUNG SSD 830 Series, S/N:S0Z4NEAC906195, WWN:5-002538-043584d30, FW:CXM03B1Q, 256 GB
Feb 14 20:22:40 linux-ytaf smartd[1037]: Device: /dev/sda [SAT], found in smartd database: Samsung based SSDs
Feb 14 20:22:40 linux-ytaf smartd[1037]: Device: /dev/sda [SAT], can't monitor Current_Pending_Sector count - no Attribute 197
Feb 14 20:22:40 linux-ytaf smartd[1037]: Device: /dev/sda [SAT], can't monitor Offline_Uncorrectable count - no Attribute 198
Feb 14 20:22:40 linux-ytaf smartd[1037]: Device: /dev/sda [SAT], is SMART capable. Adding to "monitor" list.
Feb 14 20:22:40 linux-ytaf smartd[1037]: Device: /dev/sda [SAT], state read from /var/lib/smartmontools/smartd.SAMSUNG_SSD_830_Series-S0Z4NEAC906195.ata.state
Feb 14 20:22:40 linux-ytaf smartd[1037]: Device: /dev/sdb, type changed from 'scsi' to 'sat'
Feb 14 20:22:40 linux-ytaf smartd[1037]: Device: /dev/sdb [SAT], opened
Feb 14 20:22:40 linux-ytaf smartd[1037]: Device: /dev/sdb [SAT], TOSHIBA HDWD110, S/N:Y5GDEMGFS, WWN:5-000039-fe7c5a79c, FW:MS2OA8J0, 1.00 TB
Feb 14 20:22:40 linux-ytaf smartd[1037]: Device: /dev/sdb [SAT], not found in smartd database.
Feb 14 20:22:40 linux-ytaf display-manager[1049]: /etc/vconsole.conf available
Feb 14 20:22:40 linux-ytaf display-manager[1049]: KEYMAP: de-latin1-nodeadkeys
Feb 14 20:22:40 linux-ytaf display-manager[1049]: Command: localectl set-keymap de-latin1-nodeadkeys
Feb 14 20:22:41 linux-ytaf display-manager[1049]: I: Using systemd /usr/share/systemd/kbd-model-map mapping
Feb 14 20:22:41 linux-ytaf dbus[1030]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service'
Feb 14 20:22:41 linux-ytaf dbus[1030]: [system] Successfully activated service 'org.freedesktop.locale1'
Feb 14 20:22:42 linux-ytaf smartd[1037]: Device: /dev/sdb [SAT], is SMART capable. Adding to "monitor" list.
Feb 14 20:22:42 linux-ytaf smartd[1037]: Device: /dev/sdb [SAT], state read from /var/lib/smartmontools/smartd.TOSHIBA_HDWD110-Y5GDEMGFS.ata.state
Feb 14 20:22:42 linux-ytaf smartd[1037]: Monitoring 2 ATA and 0 SCSI devices
Feb 14 20:22:42 linux-ytaf ModemManager[1033]: <info>  ModemManager (version 1.4.10) starting in system bus...
Feb 14 20:22:42 linux-ytaf dbus[1030]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Feb 14 20:22:42 linux-ytaf smartd[1037]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 230 to 240
Feb 14 20:22:42 linux-ytaf polkitd[1091]: Started polkitd version 0.113
Feb 14 20:22:43 linux-ytaf smartd[1037]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.SAMSUNG_SSD_830_Series-S0Z4NEAC906195.ata.state
Feb 14 20:22:43 linux-ytaf smartd[1037]: Device: /dev/sdb [SAT], state written to /var/lib/smartmontools/smartd.TOSHIBA_HDWD110-Y5GDEMGFS.ata.state
Feb 14 20:22:43 linux-ytaf kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
Feb 14 20:22:43 linux-ytaf kernel: nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
Feb 14 20:22:43 linux-ytaf kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Feb 14 20:22:43 linux-ytaf polkitd[1091]: Loading rules from directory /etc/polkit-1/rules.d
Feb 14 20:22:43 linux-ytaf polkitd[1091]: Loading rules from directory /usr/share/polkit-1/rules.d
Feb 14 20:22:43 linux-ytaf polkitd[1091]: Finished loading, compiling and executing 3 rules
Feb 14 20:22:43 linux-ytaf dbus[1030]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Feb 14 20:22:43 linux-ytaf polkitd[1091]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
Feb 14 20:22:43 linux-ytaf logger[1087]: /etc/init.d/xdm: No changes for /etc/X11/xdm/Xservers
Feb 14 20:22:43 linux-ytaf logger[1087]: /etc/init.d/xdm: No changes for /etc/X11/xdm/xdm-config
Feb 14 20:22:43 linux-ytaf SuSEfirewall2[1168]: Firewall rules set to CLOSE.
Feb 14 20:22:44 linux-ytaf kernel: No iBFT detected.
Feb 14 20:22:44 linux-ytaf display-manager[1049]: Starting service sddm..done
Feb 14 20:22:44 linux-ytaf sddm[1173]: Starting...
Feb 14 20:22:44 linux-ytaf sddm[1173]: Adding new display on vt 7 ...
Feb 14 20:22:44 linux-ytaf sddm[1173]: Display server starting...
Feb 14 20:22:44 linux-ytaf sddm[1173]: Running: /usr/bin/X -nolisten tcp -auth /run/sddm/{2abaf585-238b-4b5a-b79b-f7f169dfda3d} -background none -noreset -displayfd 17 vt7
Feb 14 20:22:46 linux-ytaf ModemManager[1033]: <info>  Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin
Feb 14 20:22:46 linux-ytaf kernel: NVRM: Your system is not currently configured to drive a VGA console
Feb 14 20:22:46 linux-ytaf kernel: NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
Feb 14 20:22:46 linux-ytaf kernel: NVRM: requires the use of a text-mode VGA console. Use of other console
Feb 14 20:22:46 linux-ytaf kernel: NVRM: drivers including, but not limited to, vesafb, may result in
Feb 14 20:22:46 linux-ytaf kernel: NVRM: corruption and stability problems, and is not supported.
Feb 14 20:22:47 linux-ytaf kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Feb 14 20:22:47 linux-ytaf wickedd-dhcp4[1171]: eth0: Request to acquire DHCPv4 lease with UUID 04d4c056-2383-0600-9604-000004000000
Feb 14 20:22:47 linux-ytaf kernel: NET: Registered protocol family 17
Feb 14 20:22:48 linux-ytaf sddm[1173]: Display server started.
Feb 14 20:22:48 linux-ytaf sddm[1173]: Socket server starting...
Feb 14 20:22:48 linux-ytaf sddm[1173]: Socket server started.
Feb 14 20:22:48 linux-ytaf sddm[1173]: Greeter starting...
Feb 14 20:22:48 linux-ytaf sddm[1173]: Adding cookie to "/run/sddm/{2abaf585-238b-4b5a-b79b-f7f169dfda3d}"
Feb 14 20:22:48 linux-ytaf sddm-helper[1316]: [PAM] Starting...
Feb 14 20:22:48 linux-ytaf sddm-helper[1316]: [PAM] Authenticating...
Feb 14 20:22:48 linux-ytaf sddm-helper[1316]: [PAM] returning.
Feb 14 20:22:48 linux-ytaf sddm-helper[1316]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
Feb 14 20:22:48 linux-ytaf systemd[1318]: pam_unix(systemd-user:session): session opened for user sddm by (uid=0)
Feb 14 20:22:48 linux-ytaf wickedd-dhcp4[1171]: eth0: Committed DHCPv4 lease with address 192.168.178.12 (lease time 864000 sec, renew in 432000 sec, rebind in 756000 sec)
Feb 14 20:22:48 linux-ytaf avahi-daemon[1031]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.178.12.
Feb 14 20:22:48 linux-ytaf avahi-daemon[1031]: New relevant interface eth0.IPv4 for mDNS.
Feb 14 20:22:48 linux-ytaf avahi-daemon[1031]: Registering new address record for 192.168.178.12 on eth0.IPv4.
Feb 14 20:22:48 linux-ytaf wickedd[1174]: eth0: Notified neighbours about IP address 192.168.178.12
Feb 14 20:22:48 MM-Home wicked[1176]: lo              up
Feb 14 20:22:48 MM-Home wicked[1176]: eth0            up
Feb 14 20:22:48 MM-Home iscsiadm[1497]: iscsiadm: No records found
Feb 14 20:22:48 MM-Home SuSEfirewall2[1508]: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Feb 14 20:22:48 MM-Home SuSEfirewall2[1514]: using default zone 'ext' for interface eth0
Feb 14 20:22:48 MM-Home echo[1496]: Starting mail service (Postfix)
Feb 14 20:22:49 MM-Home ntpd[1528]: ntpd 4.2.8p4@1.3265-o Thu Dec 17 05:32:52 UTC 2015 (1): Starting
Feb 14 20:22:49 MM-Home ntpd[1528]: Command line: /usr/sbin/ntpd -p /var/run/ntp/ntpd.pid -g -u ntp:ntp -c /etc/ntp.conf
Feb 14 20:22:49 MM-Home sddm[1173]: Message received from greeter: Connect
Feb 14 20:22:49 MM-Home sntp[1627]: sntp 4.2.8p4@1.3265-o Thu Dec 17 05:32:29 UTC 2015 (1)
Feb 14 20:22:49 MM-Home sntp[1627]: kod_init_kod_db(): Cannot open KoD db file /var/db/ntp-kod: No such file or directory
Feb 14 20:22:49 MM-Home sntp[1627]: 2016-02-14 20:22:49.215934 (-0100) -0.13990 +/- 0.149054 192.168.178.1 s3 no-leap
Feb 14 20:22:49 MM-Home ntpd[1626]: proto: precision = 0.075 usec (-24)
Feb 14 20:22:49 MM-Home ntpd[1626]: switching logging to file /var/log/ntp
Feb 14 20:22:49 MM-Home /usr/sbin/start-ntpd[1681]: runtime configuration: server 192.168.178.1
Feb 14 20:22:49 MM-Home SuSEfirewall2[1696]: Firewall rules successfully set
Feb 14 20:22:49 MM-Home postfix/postfix-script[1680]: starting the Postfix mail system
Feb 14 20:22:49 MM-Home postfix/master[1699]: daemon started -- version 2.11.6, configuration /etc/postfix
Feb 14 20:22:49 MM-Home cron[1716]: (CRON) INFO (RANDOM_DELAY will be scaled with factor 54% if used.)
Feb 14 20:22:49 MM-Home cron[1716]: (CRON) INFO (running with inotify support)
Feb 14 20:22:49 MM-Home start-ntpd[1500]: Starting network time protocol daemon (NTPD)sntp 4.2.8p4@1.3265-o Thu Dec 17 05:32:29 UTC 2015 (1)
Feb 14 20:22:49 MM-Home start-ntpd[1500]: kod_init_kod_db(): Cannot open KoD db file /var/db/ntp-kod: No such file or directory
Feb 14 20:22:49 MM-Home start-ntpd[1500]: 2016-02-14 20:22:49.215934 (-0100) -0.13990 +/- 0.149054 192.168.178.1 s3 no-leap
Feb 14 20:22:52 MM-Home dbus[1030]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
Feb 14 20:22:52 MM-Home udisksd[1726]: udisks daemon version 2.1.6 starting
Feb 14 20:22:53 MM-Home dbus[1030]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Feb 14 20:22:53 MM-Home udisksd[1726]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Feb 14 20:22:53 MM-Home dbus[1030]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
Feb 14 20:22:53 MM-Home dbus[1030]: [system] Successfully activated service 'org.freedesktop.UPower'
Feb 14 20:23:04 MM-Home sddm[1173]: Message received from greeter: Login
Feb 14 20:23:04 MM-Home sddm[1173]: Session "/usr/share/xsessions/plasma5.desktop" selected, command: "/usr/bin/startkde"
Feb 14 20:23:04 MM-Home sddm-helper[1762]: [PAM] Authenticating...
Feb 14 20:23:04 MM-Home sddm-helper[1762]: [PAM] Conversation with 1 messages
Feb 14 20:23:04 MM-Home sddm[1173]: Authenticated successfully
Feb 14 20:23:04 MM-Home sddm-helper[1762]: pam_unix(sddm:session): session opened for user marc by (uid=0)
Feb 14 20:23:04 MM-Home systemd[1763]: pam_unix(systemd-user:session): session opened for user marc by (uid=0)
Feb 14 20:23:04 MM-Home sddm-helper[1765]: Adding cookie to "/home/marc/.Xauthority"
Feb 14 20:23:04 MM-Home sddm-helper[1316]: [PAM] Ended.
Feb 14 20:23:04 MM-Home sddm[1173]: Auth: sddm-helper exited successfully
Feb 14 20:23:04 MM-Home sddm[1173]: Greeter stopped.
Feb 14 20:23:04 MM-Home sddm[1173]: Session started
Feb 14 20:23:06 MM-Home dbus[1030]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Feb 14 20:23:06 MM-Home org.kde.powerdevil.backlighthelper[1030]: powerdevil: no kernel backlight interface found
Feb 14 20:23:06 MM-Home dbus[1030]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Feb 14 20:23:07 MM-Home polkitd[1091]: Registered Authentication Agent for unix-session:2 (system bus name :1.36 [/usr/lib64/libexec/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale de_DE.UTF-8)
Feb 14 20:23:07 MM-Home dbus[1030]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service'
Feb 14 20:23:07 MM-Home dbus[1030]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Feb 14 20:23:07 MM-Home rtkit-daemon[1922]: Successfully called chroot.
Feb 14 20:23:07 MM-Home rtkit-daemon[1922]: Successfully dropped privileges.
Feb 14 20:23:07 MM-Home rtkit-daemon[1922]: Successfully limited resources.
Feb 14 20:23:07 MM-Home rtkit-daemon[1922]: Running.
Feb 14 20:23:07 MM-Home rtkit-daemon[1922]: Canary thread running.
Feb 14 20:23:07 MM-Home rtkit-daemon[1922]: Watchdog thread running.
Feb 14 20:23:07 MM-Home rtkit-daemon[1922]: Successfully made thread 1921 of process 1921 (/usr/bin/pulseaudio) owned by 'marc' high priority at nice level -11.
Feb 14 20:23:07 MM-Home rtkit-daemon[1922]: Supervising 1 threads of 1 processes of 1 users.
Feb 14 20:23:10 MM-Home rtkit-daemon[1922]: Supervising 1 threads of 1 processes of 1 users.
Feb 14 20:23:10 MM-Home rtkit-daemon[1922]: Successfully made thread 1974 of process 1921 (/usr/bin/pulseaudio) owned by 'marc' RT at priority 5.
Feb 14 20:23:10 MM-Home rtkit-daemon[1922]: Supervising 2 threads of 1 processes of 1 users.
Feb 14 20:23:10 MM-Home rtkit-daemon[1922]: Supervising 2 threads of 1 processes of 1 users.
Feb 14 20:23:10 MM-Home rtkit-daemon[1922]: Successfully made thread 1978 of process 1921 (/usr/bin/pulseaudio) owned by 'marc' RT at priority 5.
Feb 14 20:23:10 MM-Home rtkit-daemon[1922]: Supervising 3 threads of 1 processes of 1 users.
Feb 14 20:23:10 MM-Home rtkit-daemon[1922]: Supervising 3 threads of 1 processes of 1 users.
Feb 14 20:23:10 MM-Home rtkit-daemon[1922]: Successfully made thread 1979 of process 1921 (/usr/bin/pulseaudio) owned by 'marc' RT at priority 5.
Feb 14 20:23:10 MM-Home rtkit-daemon[1922]: Supervising 4 threads of 1 processes of 1 users.
Feb 14 20:23:10 MM-Home dbus[1030]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Feb 14 20:23:10 MM-Home bluetoothd[1980]: Bluetooth daemon 5.35
Feb 14 20:23:10 MM-Home dbus[1030]: [system] Successfully activated service 'org.bluez'
Feb 14 20:23:10 MM-Home bluetoothd[1980]: Starting SDP server
Feb 14 20:23:10 MM-Home kernel: Bluetooth: Core ver 2.20
Feb 14 20:23:10 MM-Home kernel: NET: Registered protocol family 31
Feb 14 20:23:10 MM-Home kernel: Bluetooth: HCI device and connection manager initialized
Feb 14 20:23:10 MM-Home kernel: Bluetooth: HCI socket layer initialized
Feb 14 20:23:10 MM-Home kernel: Bluetooth: L2CAP socket layer initialized
Feb 14 20:23:10 MM-Home kernel: Bluetooth: SCO socket layer initialized
Feb 14 20:23:10 MM-Home kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Feb 14 20:23:10 MM-Home kernel: Bluetooth: BNEP filters: protocol multicast
Feb 14 20:23:10 MM-Home kernel: Bluetooth: BNEP socket layer initialized
Feb 14 20:23:10 MM-Home dbus[1030]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Feb 14 20:23:10 MM-Home bluetoothd[1980]: Bluetooth management interface 1.9 initialized
Feb 14 20:23:10 MM-Home dbus[1030]: [system] Successfully activated service 'org.freedesktop.hostname1'
Feb 14 20:23:11 MM-Home kernel: fuse init (API version 7.23)
Feb 14 20:23:11 MM-Home dbus[1030]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service'
Feb 14 20:23:11 MM-Home PackageKit[2032]: daemon start
Feb 14 20:23:11 MM-Home dbus[1030]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Feb 14 20:23:13 MM-Home PackageKit[2032]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 20:23:13 MM-Home PackageKit[2032]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 20:23:13 MM-Home PackageKit[2032]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 20:23:13 MM-Home PackageKit[2032]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 20:23:14 MM-Home PackageKit[2032]: refresh-cache transaction /1_cddccaaa from uid 1000 finished with success after 1117ms
Feb 14 20:23:14 MM-Home PackageKit[2032]: refresh-cache transaction /2_cadbebdc from uid 1000 finished with success after 7ms
Feb 14 20:23:15 MM-Home PackageKit[2032]: get-updates transaction /3_dcbbcaaa from uid 1000 finished with success after 1181ms
Feb 14 20:23:32 MM-Home PackageKit[2032]: daemon quit
Feb 14 20:23:32 MM-Home packagekitd[2032]: (packagekitd:2032): GLib-CRITICAL **: Source ID 6 was not found when attempting to remove it
Feb 14 20:24:22 MM-Home dbus[1030]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service'
Feb 14 20:24:22 MM-Home PackageKit[2111]: daemon start
Feb 14 20:24:22 MM-Home dbus[1030]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Feb 14 20:24:22 MM-Home PackageKit[2111]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 20:24:22 MM-Home PackageKit[2111]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 20:24:22 MM-Home PackageKit[2111]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 20:24:23 MM-Home PackageKit[2111]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 20:24:23 MM-Home PackageKit[2111]: refresh-cache transaction /1_eaebabbb from uid 1000 finished with success after 40ms
Feb 14 20:24:23 MM-Home PackageKit[2111]: refresh-cache transaction /2_eaddecbe from uid 1000 finished with success after 13ms
Feb 14 20:24:24 MM-Home PackageKit[2111]: get-updates transaction /3_eacebaaa from uid 1000 finished with success after 936ms
Feb 14 20:24:43 MM-Home PackageKit[2111]: daemon quit
Feb 14 20:24:43 MM-Home packagekitd[2111]: (packagekitd:2111): GLib-CRITICAL **: Source ID 6 was not found when attempting to remove it
Feb 14 20:25:06 MM-Home kernel: nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
Feb 14 20:30:01 MM-Home cron[2179]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 20:30:01 MM-Home systemd[2180]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 20:30:01 MM-Home CRON[2179]: pam_unix(crond:session): session closed for user root
Feb 14 20:30:01 MM-Home systemd[2181]: pam_unix(systemd-user:session): session closed for user root
Feb 14 20:41:49 MM-Home org.kde.kuiserver[1813]: kuiserver: adding job contact for address:  ":1.18"  objectPath:  "/DataEngine/applicationjobs/JobView_1"
Feb 14 20:41:49 MM-Home org.kde.kuiserver[1813]: kuiserver: making async call of terminate for:  "/DataEngine/applicationjobs/JobView_1"
Feb 14 20:41:49 MM-Home org.kde.kuiserver[1813]: kuiserver: removing jobview from list, it finished
Feb 14 20:45:01 MM-Home cron[2503]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 20:45:01 MM-Home systemd[2504]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 20:45:01 MM-Home CRON[2503]: pam_unix(crond:session): session closed for user root
Feb 14 20:45:01 MM-Home systemd[2505]: pam_unix(systemd-user:session): session closed for user root
Feb 14 20:52:43 MM-Home smartd[1037]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 240 to 230
Feb 14 21:00:01 MM-Home cron[2631]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 21:00:01 MM-Home systemd[2632]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 21:00:02 MM-Home CRON[2631]: pam_unix(crond:session): session closed for user root
Feb 14 21:00:02 MM-Home systemd[2633]: pam_unix(systemd-user:session): session closed for user root
Feb 14 21:05:30 MM-Home su[2744]: (to root) marc on pts/0
Feb 14 21:05:30 MM-Home su[2744]: pam_unix(su:session): session opened for user root by marc(uid=1000)
Feb 14 21:14:18 MM-Home su[2744]: pam_unix(su:session): session closed for user root
Feb 14 21:15:01 MM-Home cron[2823]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 21:15:01 MM-Home systemd[2824]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 21:15:01 MM-Home CRON[2823]: pam_unix(crond:session): session closed for user root
Feb 14 21:15:01 MM-Home systemd[2825]: pam_unix(systemd-user:session): session closed for user root
Feb 14 21:22:30 MM-Home org.kde.kwalletd5[1813]: kwalletd5 started
Feb 14 21:22:31 MM-Home org.kde.kwalletd5[1813]: Migration agent starting...
Feb 14 21:22:31 MM-Home org.kde.kwalletd5[1813]: old wallets were already migrated
Feb 14 21:22:31 MM-Home org.kde.kwalletd5[1813]: Migration agent stop.
Feb 14 21:22:43 MM-Home smartd[1037]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 230 to 240
Feb 14 21:23:27 MM-Home su[2921]: (to root) marc on pts/1
Feb 14 21:23:27 MM-Home su[2921]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 21:23:27 MM-Home su[2921]: pam_unix(su:session): session closed for user root
Feb 14 21:23:27 MM-Home su[2926]: (to root) marc on pts/1
Feb 14 21:23:27 MM-Home su[2926]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 21:23:35 MM-Home dbus[1030]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Feb 14 21:23:35 MM-Home dbus[1030]: [system] Successfully activated service 'org.opensuse.Snapper'
Feb 14 21:23:41 MM-Home kernel: device-mapper: uevent: version 1.0.3
Feb 14 21:23:41 MM-Home kernel: device-mapper: ioctl: 4.31.0-ioctl (2015-3-12) initialised: dm-devel@redhat.com
Feb 14 21:23:43 MM-Home kernel: st: Version 20101219, fixed bufsize 32768, s/g segs 256
Feb 14 21:23:43 MM-Home kernel: BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Feb 14 21:23:43 MM-Home kernel: EDD information not available.
Feb 14 21:24:23 MM-Home dbus[1030]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service'
Feb 14 21:24:23 MM-Home PackageKit[3949]: daemon start
Feb 14 21:24:23 MM-Home dbus[1030]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Feb 14 21:24:23 MM-Home PackageKit[3949]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 21:24:23 MM-Home PackageKit[3949]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 21:24:23 MM-Home PackageKit[3949]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 21:24:23 MM-Home PackageKit[3949]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 21:24:25 MM-Home PackageKit[3949]: refresh-cache transaction /1_ecbaeecd from uid 1000 finished with success after 2326ms
Feb 14 21:24:25 MM-Home PackageKit[3949]: refresh-cache transaction /2_becbaceb from uid 1000 finished with success after 18ms
Feb 14 21:24:26 MM-Home PackageKit[3949]: get-updates transaction /3_dadbaaad from uid 1000 finished with success after 924ms
Feb 14 21:24:43 MM-Home PackageKit[3949]: daemon quit
Feb 14 21:24:43 MM-Home packagekitd[3949]: (packagekitd:3949): GLib-CRITICAL **: Source ID 6 was not found when attempting to remove it
Feb 14 21:25:20 MM-Home su[2926]: pam_unix(su:session): session closed for user root
Feb 14 21:29:04 MM-Home org.a11y.Bus[1813]: Activating service name='org.a11y.atspi.Registry'
Feb 14 21:29:04 MM-Home org.a11y.Bus[1813]: Successfully activated service 'org.a11y.atspi.Registry'
Feb 14 21:29:04 MM-Home org.a11y.atspi.Registry[6530]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Feb 14 21:29:04 MM-Home org.a11y.atspi.Registry[6530]: Xlib:  extension "XEVIE" missing on display ":0".
Feb 14 21:29:05 MM-Home org.gtk.Private.AfcVolumeMonitor[1813]: Volume monitor alive
Feb 14 21:29:06 MM-Home org.gnome.OnlineAccounts[1813]: goa-daemon-Message: goa-daemon version 3.16.5 starting
Feb 14 21:29:06 MM-Home org.gnome.OnlineAccounts[1813]: (goa-daemon:6559): goa-daemon-CRITICAL **: Error preparing AM: The name org.freedesktop.Telepathy.AccountManager was not provided by any .service files
Feb 14 21:29:06 MM-Home dbus[1030]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Feb 14 21:29:06 MM-Home dbus[1030]: [system] Successfully activated service 'org.freedesktop.hostname1'
Feb 14 21:29:15 MM-Home polkitd[1091]: Operator of unix-session:2 successfully authenticated as unix-user:root to gain TEMPORARY authorization for action org.opensuse.cupspkhelper.mechanism.all-edit for unix-process:6528:399561 [/usr/bin/python3 /usr/share/system-config-printer/system-config-printer.py] (owned by unix-user:marc)
Feb 14 21:29:19 MM-Home dbus[1030]: [system] Activating service name='org.opensuse.CupsPkHelper.Mechanism' (using servicehelper)
Feb 14 21:29:19 MM-Home dbus[1030]: [system] Successfully activated service 'org.opensuse.CupsPkHelper.Mechanism'
Feb 14 21:29:19 MM-Home kernel: lp: driver loaded but no devices found
Feb 14 21:29:19 MM-Home kernel: ppdev: user-space parallel port driver
Feb 14 21:29:19 MM-Home kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=c8:60:00:09:38:76:64:51:06:1c:d0:c7:08:00 SRC=192.168.178.236 DST=192.168.178.12 LEN=99 TOS=0x00 PREC=0x00 TTL=64 ID=431 PROTO=UDP SPT=161 DPT=33124 LEN=79 
Feb 14 21:30:01 MM-Home cron[6624]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 21:30:01 MM-Home systemd[6625]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 21:30:01 MM-Home CRON[6624]: pam_unix(crond:session): session closed for user root
Feb 14 21:30:01 MM-Home systemd[6626]: pam_unix(systemd-user:session): session closed for user root
Feb 14 21:35:54 MM-Home dbus[1030]: [system] Activating service name='org.opensuse.CupsPkHelper.Mechanism' (using servicehelper)
Feb 14 21:35:54 MM-Home dbus[1030]: [system] Successfully activated service 'org.opensuse.CupsPkHelper.Mechanism'
Feb 14 21:36:01 MM-Home polkitd[1091]: Operator of unix-session:2 successfully authenticated as unix-user:root to gain TEMPORARY authorization for action org.opensuse.cupspkhelper.mechanism.printer-remote-edit for system-bus-name::1.84 [/usr/bin/python3 /usr/share/system-config-printer/system-config-printer.py] (owned by unix-user:marc)
Feb 14 21:36:20 MM-Home dbus[1030]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Feb 14 21:36:20 MM-Home dbus[1030]: [system] Successfully activated service 'org.freedesktop.hostname1'
Feb 14 21:38:49 MM-Home dbus[1030]: [system] Activating service name='org.opensuse.CupsPkHelper.Mechanism' (using servicehelper)
Feb 14 21:38:49 MM-Home dbus[1030]: [system] Successfully activated service 'org.opensuse.CupsPkHelper.Mechanism'
Feb 14 21:38:54 MM-Home polkitd[1091]: Operator of unix-session:2 successfully authenticated as unix-user:root to gain TEMPORARY authorization for action org.opensuse.cupspkhelper.mechanism.devices-get for system-bus-name::1.84 [/usr/bin/python3 /usr/share/system-config-printer/system-config-printer.py] (owned by unix-user:marc)
Feb 14 21:38:54 MM-Home kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=c8:60:00:09:38:76:64:51:06:1c:d0:c7:08:00 SRC=192.168.178.236 DST=192.168.178.12 LEN=99 TOS=0x00 PREC=0x00 TTL=64 ID=434 PROTO=UDP SPT=161 DPT=36291 LEN=79 
Feb 14 21:45:01 MM-Home cron[6807]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 21:45:01 MM-Home systemd[6808]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 21:45:01 MM-Home CRON[6807]: pam_unix(crond:session): session closed for user root
Feb 14 21:45:01 MM-Home systemd[6809]: pam_unix(systemd-user:session): session closed for user root
Feb 14 22:00:01 MM-Home cron[6876]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 22:00:01 MM-Home systemd[6877]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 22:00:01 MM-Home CRON[6876]: pam_unix(crond:session): session closed for user root
Feb 14 22:00:01 MM-Home systemd[6878]: pam_unix(systemd-user:session): session closed for user root
Feb 14 22:15:01 MM-Home cron[6931]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 22:15:01 MM-Home systemd[6932]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 22:15:01 MM-Home CRON[6931]: pam_unix(crond:session): session closed for user root
Feb 14 22:15:01 MM-Home systemd[6933]: pam_unix(systemd-user:session): session closed for user root
Feb 14 22:24:23 MM-Home dbus[1030]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service'
Feb 14 22:24:23 MM-Home PackageKit[6978]: daemon start
Feb 14 22:24:23 MM-Home dbus[1030]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Feb 14 22:24:23 MM-Home PackageKit[6978]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 22:24:23 MM-Home PackageKit[6978]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 22:24:23 MM-Home PackageKit[6978]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 22:24:23 MM-Home PackageKit[6978]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 22:24:24 MM-Home PackageKit[6978]: refresh-cache transaction /1_eadccded from uid 1000 finished with success after 1237ms
Feb 14 22:24:24 MM-Home PackageKit[6978]: refresh-cache transaction /2_ebbdabac from uid 1000 finished with success after 19ms
Feb 14 22:24:25 MM-Home PackageKit[6978]: get-updates transaction /3_edeccdcc from uid 1000 finished with success after 925ms
Feb 14 22:24:43 MM-Home PackageKit[6978]: daemon quit
Feb 14 22:24:43 MM-Home packagekitd[6978]: (packagekitd:6978): GLib-CRITICAL **: Source ID 6 was not found when attempting to remove it
Feb 14 22:30:01 MM-Home cron[7004]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 22:30:01 MM-Home systemd[7005]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 22:30:01 MM-Home CRON[7004]: pam_unix(crond:session): session closed for user root
Feb 14 22:30:01 MM-Home systemd[7006]: pam_unix(systemd-user:session): session closed for user root
Feb 14 22:45:01 MM-Home cron[7159]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 22:45:01 MM-Home systemd[7160]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 22:45:01 MM-Home CRON[7159]: pam_unix(crond:session): session closed for user root
Feb 14 22:45:01 MM-Home systemd[7161]: pam_unix(systemd-user:session): session closed for user root
Feb 14 23:00:01 MM-Home cron[7214]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 23:00:01 MM-Home systemd[7215]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 23:00:01 MM-Home CRON[7214]: pam_unix(crond:session): session closed for user root
Feb 14 23:00:01 MM-Home systemd[7216]: pam_unix(systemd-user:session): session closed for user root
Feb 14 23:15:01 MM-Home cron[7282]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 23:15:01 MM-Home systemd[7283]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 23:15:01 MM-Home CRON[7282]: pam_unix(crond:session): session closed for user root
Feb 14 23:15:01 MM-Home systemd[7284]: pam_unix(systemd-user:session): session closed for user root
Feb 14 23:17:30 MM-Home su[7384]: (to root) marc on pts/1
Feb 14 23:17:30 MM-Home su[7384]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:17:30 MM-Home su[7384]: pam_unix(su:session): session closed for user root
Feb 14 23:17:31 MM-Home su[7389]: (to root) marc on pts/1
Feb 14 23:17:31 MM-Home su[7389]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:17:35 MM-Home dbus[1030]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Feb 14 23:17:35 MM-Home dbus[1030]: [system] Successfully activated service 'org.opensuse.Snapper'
Feb 14 23:19:39 MM-Home kernel: BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Feb 14 23:19:39 MM-Home kernel: EDD information not available.
Feb 14 23:22:43 MM-Home smartd[1037]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 240 to 230
Feb 14 23:23:02 MM-Home dbus[1030]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Feb 14 23:23:02 MM-Home dbus[1030]: [system] Successfully activated service 'org.opensuse.Snapper'
Feb 14 23:24:23 MM-Home dbus[1030]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service'
Feb 14 23:24:23 MM-Home PackageKit[17611]: daemon start
Feb 14 23:24:23 MM-Home dbus[1030]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Feb 14 23:24:23 MM-Home PackageKit[17611]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 23:24:23 MM-Home PackageKit[17611]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 14 23:24:23 MM-Home PackageKit[17611]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 23:24:23 MM-Home PackageKit[17611]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 14 23:24:23 MM-Home PackageKit[17611]: refresh-cache transaction /1_aaabedae from uid 1000 finished with success after 38ms
Feb 14 23:24:23 MM-Home PackageKit[17611]: refresh-cache transaction /2_aeaeaebc from uid 1000 finished with success after 18ms
Feb 14 23:24:24 MM-Home PackageKit[17611]: get-updates transaction /3_bbddeace from uid 1000 finished with success after 930ms
Feb 14 23:24:43 MM-Home PackageKit[17611]: daemon quit
Feb 14 23:24:43 MM-Home packagekitd[17611]: (packagekitd:17611): GLib-CRITICAL **: Source ID 6 was not found when attempting to remove it
Feb 14 23:27:39 MM-Home su[17827]: (to root) marc on pts/3
Feb 14 23:27:39 MM-Home su[17827]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:27:39 MM-Home su[17827]: pam_unix(su:session): session closed for user root
Feb 14 23:28:21 MM-Home install.py[17753]: hplip-install[17753]: warning: Missing REQUIRED dependency: libusb (libusb - USB library)
Feb 14 23:28:21 MM-Home install.py[17753]: hplip-install[17753]: warning: Missing REQUIRED dependency: libtool (libtool - Library building support services)
Feb 14 23:28:21 MM-Home install.py[17753]: hplip-install[17753]: warning: Missing REQUIRED dependency: cups-image (CUPS image - CUPS image development files)
Feb 14 23:28:21 MM-Home install.py[17753]: hplip-install[17753]: warning: Missing REQUIRED dependency: gcc (gcc - GNU Project C and C++ Compiler)
Feb 14 23:28:21 MM-Home install.py[17753]: hplip-install[17753]: warning: Missing REQUIRED dependency: libjpeg (libjpeg - JPEG library)
Feb 14 23:28:21 MM-Home install.py[17753]: hplip-install[17753]: warning: Missing REQUIRED dependency: python-devel (Python devel - Python development files)
Feb 14 23:28:21 MM-Home install.py[17753]: hplip-install[17753]: warning: Missing REQUIRED dependency: cups-devel (CUPS devel- Common Unix Printing System development files)
Feb 14 23:28:21 MM-Home install.py[17753]: hplip-install[17753]: warning: Missing REQUIRED dependency: libcrypto (libcrypto - OpenSSL cryptographic library)
Feb 14 23:28:21 MM-Home install.py[17753]: hplip-install[17753]: warning: Missing REQUIRED dependency: libnetsnmp-devel (libnetsnmp-devel - SNMP networking library development files)
Feb 14 23:28:21 MM-Home install.py[17753]: hplip-install[17753]: warning: Missing REQUIRED dependency: pyqt4 (PyQt 4- Qt interface for Python (for Qt version 4.x))
Feb 14 23:28:21 MM-Home install.py[17753]: hplip-install[17753]: warning: Missing REQUIRED dependency: pyqt4-dbus (PyQt 4 DBus - DBus Support for PyQt4)
Feb 14 23:28:21 MM-Home install.py[17753]: hplip-install[17753]: warning: Missing REQUIRED dependency: dbus (DBus - Message bus system)
Feb 14 23:28:22 MM-Home install.py[17753]: hplip-install[17753]: warning: Missing REQUIRED dependency: sane-devel (SANE - Scanning library development files)
Feb 14 23:28:22 MM-Home install.py[17753]: hplip-install[17753]: warning: Missing OPTIONAL dependency for option 'base': cups-ddk (CUPS DDK - CUPS driver development kit)
Feb 14 23:28:22 MM-Home install.py[17753]: hplip-install[17753]: warning: Missing OPTIONAL dependency for option 'network': avahi-utils (avahi-utils)
Feb 14 23:28:22 MM-Home install.py[17753]: hplip-install[17753]: warning: Missing OPTIONAL dependency for option 'gui_qt4': python-notify (Python libnotify - Python bindings for the libnotify Desktop notifications)
Feb 14 23:28:22 MM-Home install.py[17753]: hplip-install[17753]: warning: Missing OPTIONAL dependency for option 'fax': reportlab (Reportlab - PDF library for Python)
Feb 14 23:28:22 MM-Home install.py[17753]: hplip-install[17753]: warning: This installer cannot install 'reportlab' for your distro/OS and/or version.
Feb 14 23:28:22 MM-Home install.py[17753]: hplip-install[17753]: warning: Missing OPTIONAL dependency for option 'scan': pil (PIL - Python Imaging Library (required for commandline scanning with hp-scan))
Feb 14 23:28:22 MM-Home install.py[17753]: hplip-install[17753]: warning: Missing OPTIONAL dependency for option 'scan': xsane (xsane - Graphical scanner frontend for SANE)
Feb 14 23:28:45 MM-Home su[7389]: pam_unix(su:session): session closed for user root
Feb 14 23:28:46 MM-Home dbus[1030]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Feb 14 23:28:46 MM-Home dbus[1030]: [system] Successfully activated service 'org.opensuse.Snapper'
Feb 14 23:28:54 MM-Home su[18983]: (to root) marc on pts/0
Feb 14 23:28:54 MM-Home su[18983]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:28:55 MM-Home su[18983]: pam_unix(su:session): session closed for user root
Feb 14 23:28:56 MM-Home su[18994]: (to root) marc on pts/0
Feb 14 23:28:56 MM-Home su[18994]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:29:05 MM-Home su[18994]: pam_unix(su:session): session closed for user root
Feb 14 23:29:06 MM-Home su[22291]: (to root) marc on pts/0
Feb 14 23:29:06 MM-Home su[22291]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:29:07 MM-Home su[22291]: pam_unix(su:session): session closed for user root
Feb 14 23:29:07 MM-Home su[22296]: (to root) marc on pts/0
Feb 14 23:29:07 MM-Home su[22296]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:29:19 MM-Home su[22296]: pam_unix(su:session): session closed for user root
Feb 14 23:29:20 MM-Home su[25738]: (to root) marc on pts/0
Feb 14 23:29:20 MM-Home su[25738]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:29:27 MM-Home su[25738]: pam_unix(su:session): session closed for user root
Feb 14 23:29:28 MM-Home su[29312]: (to root) marc on pts/0
Feb 14 23:29:28 MM-Home su[29312]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:29:34 MM-Home su[29312]: pam_unix(su:session): session closed for user root
Feb 14 23:29:34 MM-Home su[596]: (to root) marc on pts/0
Feb 14 23:29:34 MM-Home su[596]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:29:48 MM-Home su[596]: pam_unix(su:session): session closed for user root
Feb 14 23:29:49 MM-Home su[4741]: (to root) marc on pts/0
Feb 14 23:29:49 MM-Home su[4741]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:30:01 MM-Home su[4741]: pam_unix(su:session): session closed for user root
Feb 14 23:30:01 MM-Home su[8856]: (to root) marc on pts/0
Feb 14 23:30:01 MM-Home su[8856]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:30:01 MM-Home cron[8861]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 23:30:01 MM-Home systemd[8862]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 23:30:02 MM-Home CRON[8861]: pam_unix(crond:session): session closed for user root
Feb 14 23:30:02 MM-Home systemd[8863]: pam_unix(systemd-user:session): session closed for user root
Feb 14 23:30:12 MM-Home su[8856]: pam_unix(su:session): session closed for user root
Feb 14 23:30:12 MM-Home su[13058]: (to root) marc on pts/0
Feb 14 23:30:12 MM-Home su[13058]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:30:13 MM-Home su[13058]: pam_unix(su:session): session closed for user root
Feb 14 23:30:13 MM-Home su[13063]: (to root) marc on pts/0
Feb 14 23:30:13 MM-Home su[13063]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:30:14 MM-Home su[13063]: pam_unix(su:session): session closed for user root
Feb 14 23:30:14 MM-Home su[13068]: (to root) marc on pts/0
Feb 14 23:30:14 MM-Home su[13068]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:30:15 MM-Home su[13068]: pam_unix(su:session): session closed for user root
Feb 14 23:30:15 MM-Home su[13073]: (to root) marc on pts/0
Feb 14 23:30:15 MM-Home su[13073]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:30:21 MM-Home su[13073]: pam_unix(su:session): session closed for user root
Feb 14 23:30:21 MM-Home su[17369]: (to root) marc on pts/0
Feb 14 23:30:21 MM-Home su[17369]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:30:22 MM-Home su[17369]: pam_unix(su:session): session closed for user root
Feb 14 23:30:22 MM-Home su[17374]: (to root) marc on pts/0
Feb 14 23:30:22 MM-Home su[17374]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:30:39 MM-Home su[17374]: pam_unix(su:session): session closed for user root
Feb 14 23:30:39 MM-Home su[21873]: (to root) marc on pts/0
Feb 14 23:30:39 MM-Home su[21873]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:30:50 MM-Home su[21873]: pam_unix(su:session): session closed for user root
Feb 14 23:30:50 MM-Home su[26457]: (to root) marc on pts/0
Feb 14 23:30:50 MM-Home su[26457]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:30:56 MM-Home su[26457]: pam_unix(su:session): session closed for user root
Feb 14 23:30:56 MM-Home su[31183]: (to root) marc on pts/0
Feb 14 23:30:56 MM-Home su[31183]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:30:57 MM-Home su[31183]: pam_unix(su:session): session closed for user root
Feb 14 23:30:57 MM-Home su[31189]: (to root) marc on pts/0
Feb 14 23:30:57 MM-Home su[31189]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:30:58 MM-Home su[31189]: pam_unix(su:session): session closed for user root
Feb 14 23:30:58 MM-Home su[31194]: (to root) marc on pts/0
Feb 14 23:30:58 MM-Home su[31194]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:30:59 MM-Home su[31194]: pam_unix(su:session): session closed for user root
Feb 14 23:31:00 MM-Home su[31199]: (to root) marc on pts/0
Feb 14 23:31:00 MM-Home su[31199]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:31:04 MM-Home su[31199]: pam_unix(su:session): session closed for user root
Feb 14 23:31:05 MM-Home su[3906]: (to root) marc on pts/0
Feb 14 23:31:05 MM-Home su[3906]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:31:06 MM-Home su[3906]: pam_unix(su:session): session closed for user root
Feb 14 23:31:06 MM-Home su[3911]: (to root) marc on pts/0
Feb 14 23:31:06 MM-Home su[3911]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:31:12 MM-Home su[3911]: pam_unix(su:session): session closed for user root
Feb 14 23:31:12 MM-Home su[9038]: (to root) marc on pts/0
Feb 14 23:31:12 MM-Home su[9038]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:31:17 MM-Home su[9038]: pam_unix(su:session): session closed for user root
Feb 14 23:31:17 MM-Home su[14197]: (to root) marc on pts/0
Feb 14 23:31:17 MM-Home su[14197]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:31:25 MM-Home su[14197]: pam_unix(su:session): session closed for user root
Feb 14 23:31:25 MM-Home su[19520]: (to root) marc on pts/0
Feb 14 23:31:25 MM-Home su[19520]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:31:32 MM-Home su[19520]: pam_unix(su:session): session closed for user root
Feb 14 23:32:24 MM-Home su[25090]: (to root) marc on pts/0
Feb 14 23:32:24 MM-Home su[25090]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:25 MM-Home su[25090]: pam_unix(su:session): session closed for user root
Feb 14 23:32:25 MM-Home su[25095]: (to root) marc on pts/0
Feb 14 23:32:25 MM-Home su[25095]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:25 MM-Home su[25095]: pam_unix(su:session): session closed for user root
Feb 14 23:32:26 MM-Home su[25099]: (to root) marc on pts/0
Feb 14 23:32:26 MM-Home su[25099]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:26 MM-Home su[25099]: pam_unix(su:session): session closed for user root
Feb 14 23:32:26 MM-Home su[25103]: (to root) marc on pts/0
Feb 14 23:32:26 MM-Home su[25103]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:26 MM-Home su[25103]: pam_unix(su:session): session closed for user root
Feb 14 23:32:26 MM-Home su[25107]: (to root) marc on pts/0
Feb 14 23:32:26 MM-Home su[25107]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:26 MM-Home su[25107]: pam_unix(su:session): session closed for user root
Feb 14 23:32:26 MM-Home su[25111]: (to root) marc on pts/0
Feb 14 23:32:26 MM-Home su[25111]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:26 MM-Home su[25111]: pam_unix(su:session): session closed for user root
Feb 14 23:32:26 MM-Home su[25115]: (to root) marc on pts/0
Feb 14 23:32:26 MM-Home su[25115]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:26 MM-Home su[25115]: pam_unix(su:session): session closed for user root
Feb 14 23:32:27 MM-Home su[25119]: (to root) marc on pts/0
Feb 14 23:32:27 MM-Home su[25119]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:27 MM-Home su[25119]: pam_unix(su:session): session closed for user root
Feb 14 23:32:27 MM-Home su[25123]: (to root) marc on pts/0
Feb 14 23:32:27 MM-Home su[25123]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:27 MM-Home su[25123]: pam_unix(su:session): session closed for user root
Feb 14 23:32:27 MM-Home su[25127]: (to root) marc on pts/0
Feb 14 23:32:27 MM-Home su[25127]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:27 MM-Home su[25127]: pam_unix(su:session): session closed for user root
Feb 14 23:32:27 MM-Home su[25131]: (to root) marc on pts/0
Feb 14 23:32:27 MM-Home su[25131]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:27 MM-Home su[25131]: pam_unix(su:session): session closed for user root
Feb 14 23:32:28 MM-Home su[25135]: (to root) marc on pts/0
Feb 14 23:32:28 MM-Home su[25135]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:28 MM-Home su[25135]: pam_unix(su:session): session closed for user root
Feb 14 23:32:28 MM-Home su[25139]: (to root) marc on pts/0
Feb 14 23:32:28 MM-Home su[25139]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:28 MM-Home su[25139]: pam_unix(su:session): session closed for user root
Feb 14 23:32:28 MM-Home su[25143]: (to root) marc on pts/0
Feb 14 23:32:28 MM-Home su[25143]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:28 MM-Home su[25143]: pam_unix(su:session): session closed for user root
Feb 14 23:32:28 MM-Home su[25147]: (to root) marc on pts/0
Feb 14 23:32:28 MM-Home su[25147]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:28 MM-Home su[25147]: pam_unix(su:session): session closed for user root
Feb 14 23:32:29 MM-Home su[25151]: (to root) marc on pts/0
Feb 14 23:32:29 MM-Home su[25151]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:29 MM-Home su[25151]: pam_unix(su:session): session closed for user root
Feb 14 23:32:29 MM-Home su[25155]: (to root) marc on pts/0
Feb 14 23:32:29 MM-Home su[25155]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:29 MM-Home su[25155]: pam_unix(su:session): session closed for user root
Feb 14 23:32:29 MM-Home su[25159]: (to root) marc on pts/0
Feb 14 23:32:29 MM-Home su[25159]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:29 MM-Home su[25159]: pam_unix(su:session): session closed for user root
Feb 14 23:32:29 MM-Home su[25163]: (to root) marc on pts/0
Feb 14 23:32:29 MM-Home su[25163]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:29 MM-Home su[25163]: pam_unix(su:session): session closed for user root
Feb 14 23:32:30 MM-Home su[25167]: (to root) marc on pts/0
Feb 14 23:32:30 MM-Home su[25167]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:30 MM-Home su[25167]: pam_unix(su:session): session closed for user root
Feb 14 23:32:30 MM-Home su[25171]: (to root) marc on pts/0
Feb 14 23:32:30 MM-Home su[25171]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:30 MM-Home su[25171]: pam_unix(su:session): session closed for user root
Feb 14 23:32:30 MM-Home su[25175]: (to root) marc on pts/0
Feb 14 23:32:30 MM-Home su[25175]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:30 MM-Home su[25175]: pam_unix(su:session): session closed for user root
Feb 14 23:32:30 MM-Home su[25179]: (to root) marc on pts/0
Feb 14 23:32:30 MM-Home su[25179]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:30 MM-Home su[25179]: pam_unix(su:session): session closed for user root
Feb 14 23:32:30 MM-Home su[25183]: (to root) marc on pts/0
Feb 14 23:32:30 MM-Home su[25183]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:30 MM-Home su[25183]: pam_unix(su:session): session closed for user root
Feb 14 23:32:31 MM-Home su[25187]: (to root) marc on pts/0
Feb 14 23:32:31 MM-Home su[25187]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:31 MM-Home su[25187]: pam_unix(su:session): session closed for user root
Feb 14 23:32:31 MM-Home su[25191]: (to root) marc on pts/0
Feb 14 23:32:31 MM-Home su[25191]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:31 MM-Home su[25191]: pam_unix(su:session): session closed for user root
Feb 14 23:32:31 MM-Home su[25195]: (to root) marc on pts/0
Feb 14 23:32:31 MM-Home su[25195]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:31 MM-Home su[25195]: pam_unix(su:session): session closed for user root
Feb 14 23:32:31 MM-Home su[25199]: (to root) marc on pts/0
Feb 14 23:32:31 MM-Home su[25199]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:31 MM-Home su[25199]: pam_unix(su:session): session closed for user root
Feb 14 23:32:32 MM-Home su[25203]: (to root) marc on pts/0
Feb 14 23:32:32 MM-Home su[25203]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:32 MM-Home su[25203]: pam_unix(su:session): session closed for user root
Feb 14 23:32:32 MM-Home su[25207]: (to root) marc on pts/0
Feb 14 23:32:32 MM-Home su[25207]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:32 MM-Home su[25207]: pam_unix(su:session): session closed for user root
Feb 14 23:32:32 MM-Home su[25211]: (to root) marc on pts/0
Feb 14 23:32:32 MM-Home su[25211]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:32 MM-Home su[25211]: pam_unix(su:session): session closed for user root
Feb 14 23:32:32 MM-Home su[25215]: (to root) marc on pts/0
Feb 14 23:32:32 MM-Home su[25215]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:32 MM-Home su[25215]: pam_unix(su:session): session closed for user root
Feb 14 23:32:33 MM-Home su[25219]: (to root) marc on pts/0
Feb 14 23:32:33 MM-Home su[25219]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:33 MM-Home su[25219]: pam_unix(su:session): session closed for user root
Feb 14 23:32:33 MM-Home su[25223]: (to root) marc on pts/0
Feb 14 23:32:33 MM-Home su[25223]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:33 MM-Home su[25223]: pam_unix(su:session): session closed for user root
Feb 14 23:32:33 MM-Home su[25227]: (to root) marc on pts/0
Feb 14 23:32:33 MM-Home su[25227]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:33 MM-Home su[25227]: pam_unix(su:session): session closed for user root
Feb 14 23:32:33 MM-Home su[25231]: (to root) marc on pts/0
Feb 14 23:32:33 MM-Home su[25231]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:33 MM-Home su[25231]: pam_unix(su:session): session closed for user root
Feb 14 23:32:34 MM-Home su[25235]: (to root) marc on pts/0
Feb 14 23:32:34 MM-Home su[25235]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:34 MM-Home su[25235]: pam_unix(su:session): session closed for user root
Feb 14 23:32:34 MM-Home su[25239]: (to root) marc on pts/0
Feb 14 23:32:34 MM-Home su[25239]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:34 MM-Home su[25239]: pam_unix(su:session): session closed for user root
Feb 14 23:32:34 MM-Home su[25243]: (to root) marc on pts/0
Feb 14 23:32:34 MM-Home su[25243]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:34 MM-Home su[25243]: pam_unix(su:session): session closed for user root
Feb 14 23:32:34 MM-Home su[25247]: (to root) marc on pts/0
Feb 14 23:32:34 MM-Home su[25247]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:34 MM-Home su[25247]: pam_unix(su:session): session closed for user root
Feb 14 23:32:35 MM-Home su[25251]: (to root) marc on pts/0
Feb 14 23:32:35 MM-Home su[25251]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:35 MM-Home su[25251]: pam_unix(su:session): session closed for user root
Feb 14 23:32:35 MM-Home su[25255]: (to root) marc on pts/0
Feb 14 23:32:35 MM-Home su[25255]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:35 MM-Home su[25255]: pam_unix(su:session): session closed for user root
Feb 14 23:32:35 MM-Home su[25259]: (to root) marc on pts/0
Feb 14 23:32:35 MM-Home su[25259]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:35 MM-Home su[25259]: pam_unix(su:session): session closed for user root
Feb 14 23:32:35 MM-Home su[25263]: (to root) marc on pts/0
Feb 14 23:32:35 MM-Home su[25263]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:35 MM-Home su[25263]: pam_unix(su:session): session closed for user root
Feb 14 23:32:35 MM-Home su[25267]: (to root) marc on pts/0
Feb 14 23:32:35 MM-Home su[25267]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:35 MM-Home su[25267]: pam_unix(su:session): session closed for user root
Feb 14 23:32:36 MM-Home su[25271]: (to root) marc on pts/0
Feb 14 23:32:36 MM-Home su[25271]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:36 MM-Home su[25271]: pam_unix(su:session): session closed for user root
Feb 14 23:32:36 MM-Home su[25275]: (to root) marc on pts/0
Feb 14 23:32:36 MM-Home su[25275]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:36 MM-Home su[25275]: pam_unix(su:session): session closed for user root
Feb 14 23:32:36 MM-Home su[25279]: (to root) marc on pts/0
Feb 14 23:32:36 MM-Home su[25279]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:36 MM-Home su[25279]: pam_unix(su:session): session closed for user root
Feb 14 23:32:36 MM-Home su[25283]: (to root) marc on pts/0
Feb 14 23:32:36 MM-Home su[25283]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:36 MM-Home su[25283]: pam_unix(su:session): session closed for user root
Feb 14 23:32:37 MM-Home su[25287]: (to root) marc on pts/0
Feb 14 23:32:37 MM-Home su[25287]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:37 MM-Home su[25287]: pam_unix(su:session): session closed for user root
Feb 14 23:32:37 MM-Home su[25291]: (to root) marc on pts/0
Feb 14 23:32:37 MM-Home su[25291]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:37 MM-Home su[25291]: pam_unix(su:session): session closed for user root
Feb 14 23:32:37 MM-Home su[25295]: (to root) marc on pts/0
Feb 14 23:32:37 MM-Home su[25295]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:37 MM-Home su[25295]: pam_unix(su:session): session closed for user root
Feb 14 23:32:37 MM-Home su[25299]: (to root) marc on pts/0
Feb 14 23:32:37 MM-Home su[25299]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:37 MM-Home su[25299]: pam_unix(su:session): session closed for user root
Feb 14 23:32:38 MM-Home su[25303]: (to root) marc on pts/0
Feb 14 23:32:38 MM-Home su[25303]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:38 MM-Home su[25303]: pam_unix(su:session): session closed for user root
Feb 14 23:32:38 MM-Home su[25307]: (to root) marc on pts/0
Feb 14 23:32:38 MM-Home su[25307]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:38 MM-Home su[25307]: pam_unix(su:session): session closed for user root
Feb 14 23:32:38 MM-Home su[25311]: (to root) marc on pts/0
Feb 14 23:32:38 MM-Home su[25311]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:38 MM-Home su[25311]: pam_unix(su:session): session closed for user root
Feb 14 23:32:38 MM-Home su[25315]: (to root) marc on pts/0
Feb 14 23:32:38 MM-Home su[25315]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:38 MM-Home su[25315]: pam_unix(su:session): session closed for user root
Feb 14 23:32:39 MM-Home su[25319]: (to root) marc on pts/0
Feb 14 23:32:39 MM-Home su[25319]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:39 MM-Home su[25319]: pam_unix(su:session): session closed for user root
Feb 14 23:32:39 MM-Home su[25323]: (to root) marc on pts/0
Feb 14 23:32:39 MM-Home su[25323]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:39 MM-Home su[25323]: pam_unix(su:session): session closed for user root
Feb 14 23:32:39 MM-Home su[25327]: (to root) marc on pts/0
Feb 14 23:32:39 MM-Home su[25327]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:39 MM-Home su[25327]: pam_unix(su:session): session closed for user root
Feb 14 23:32:39 MM-Home su[25331]: (to root) marc on pts/0
Feb 14 23:32:39 MM-Home su[25331]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:39 MM-Home su[25331]: pam_unix(su:session): session closed for user root
Feb 14 23:32:40 MM-Home su[25335]: (to root) marc on pts/0
Feb 14 23:32:40 MM-Home su[25335]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:40 MM-Home su[25335]: pam_unix(su:session): session closed for user root
Feb 14 23:32:40 MM-Home su[25339]: (to root) marc on pts/0
Feb 14 23:32:40 MM-Home su[25339]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:40 MM-Home su[25339]: pam_unix(su:session): session closed for user root
Feb 14 23:32:40 MM-Home su[25343]: (to root) marc on pts/0
Feb 14 23:32:40 MM-Home su[25343]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:40 MM-Home su[25343]: pam_unix(su:session): session closed for user root
Feb 14 23:32:40 MM-Home su[25347]: (to root) marc on pts/0
Feb 14 23:32:40 MM-Home su[25347]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:40 MM-Home su[25347]: pam_unix(su:session): session closed for user root
Feb 14 23:32:41 MM-Home su[25351]: (to root) marc on pts/0
Feb 14 23:32:41 MM-Home su[25351]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:41 MM-Home su[25351]: pam_unix(su:session): session closed for user root
Feb 14 23:32:41 MM-Home su[25355]: (to root) marc on pts/0
Feb 14 23:32:41 MM-Home su[25355]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:41 MM-Home su[25355]: pam_unix(su:session): session closed for user root
Feb 14 23:32:41 MM-Home su[25360]: (to root) marc on pts/0
Feb 14 23:32:41 MM-Home su[25360]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:41 MM-Home su[25360]: pam_unix(su:session): session closed for user root
Feb 14 23:32:41 MM-Home su[25364]: (to root) marc on pts/0
Feb 14 23:32:41 MM-Home su[25364]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:41 MM-Home su[25364]: pam_unix(su:session): session closed for user root
Feb 14 23:32:41 MM-Home su[25368]: (to root) marc on pts/0
Feb 14 23:32:41 MM-Home su[25368]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:41 MM-Home su[25368]: pam_unix(su:session): session closed for user root
Feb 14 23:32:42 MM-Home su[25372]: (to root) marc on pts/0
Feb 14 23:32:42 MM-Home su[25372]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:42 MM-Home su[25372]: pam_unix(su:session): session closed for user root
Feb 14 23:32:42 MM-Home su[25376]: (to root) marc on pts/0
Feb 14 23:32:42 MM-Home su[25376]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:42 MM-Home su[25376]: pam_unix(su:session): session closed for user root
Feb 14 23:32:42 MM-Home su[25380]: (to root) marc on pts/0
Feb 14 23:32:42 MM-Home su[25380]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:42 MM-Home su[25380]: pam_unix(su:session): session closed for user root
Feb 14 23:32:42 MM-Home su[25384]: (to root) marc on pts/0
Feb 14 23:32:42 MM-Home su[25384]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:42 MM-Home su[25384]: pam_unix(su:session): session closed for user root
Feb 14 23:32:43 MM-Home su[25388]: (to root) marc on pts/0
Feb 14 23:32:43 MM-Home su[25388]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:43 MM-Home su[25388]: pam_unix(su:session): session closed for user root
Feb 14 23:32:43 MM-Home su[25392]: (to root) marc on pts/0
Feb 14 23:32:43 MM-Home su[25392]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:43 MM-Home su[25392]: pam_unix(su:session): session closed for user root
Feb 14 23:32:43 MM-Home su[25396]: (to root) marc on pts/0
Feb 14 23:32:43 MM-Home su[25396]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:43 MM-Home su[25396]: pam_unix(su:session): session closed for user root
Feb 14 23:32:43 MM-Home su[25400]: (to root) marc on pts/0
Feb 14 23:32:43 MM-Home su[25400]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:43 MM-Home su[25400]: pam_unix(su:session): session closed for user root
Feb 14 23:32:44 MM-Home su[25404]: (to root) marc on pts/0
Feb 14 23:32:44 MM-Home su[25404]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:44 MM-Home su[25404]: pam_unix(su:session): session closed for user root
Feb 14 23:32:44 MM-Home su[25408]: (to root) marc on pts/0
Feb 14 23:32:44 MM-Home su[25408]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:44 MM-Home su[25408]: pam_unix(su:session): session closed for user root
Feb 14 23:32:44 MM-Home su[25412]: (to root) marc on pts/0
Feb 14 23:32:44 MM-Home su[25412]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:44 MM-Home su[25412]: pam_unix(su:session): session closed for user root
Feb 14 23:32:44 MM-Home su[25416]: (to root) marc on pts/0
Feb 14 23:32:44 MM-Home su[25416]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:49 MM-Home su[25416]: pam_unix(su:session): session closed for user root
Feb 14 23:32:49 MM-Home su[25420]: (to root) marc on pts/0
Feb 14 23:32:49 MM-Home su[25420]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:49 MM-Home su[25420]: pam_unix(su:session): session closed for user root
Feb 14 23:32:49 MM-Home su[25424]: (to root) marc on pts/0
Feb 14 23:32:49 MM-Home su[25424]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:49 MM-Home su[25424]: pam_unix(su:session): session closed for user root
Feb 14 23:32:50 MM-Home su[25428]: (to root) marc on pts/0
Feb 14 23:32:50 MM-Home su[25428]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:50 MM-Home su[25428]: pam_unix(su:session): session closed for user root
Feb 14 23:32:50 MM-Home su[25432]: (to root) marc on pts/0
Feb 14 23:32:50 MM-Home su[25432]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:50 MM-Home su[25432]: pam_unix(su:session): session closed for user root
Feb 14 23:32:50 MM-Home su[25436]: (to root) marc on pts/0
Feb 14 23:32:50 MM-Home su[25436]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:50 MM-Home su[25436]: pam_unix(su:session): session closed for user root
Feb 14 23:32:50 MM-Home su[25440]: (to root) marc on pts/0
Feb 14 23:32:50 MM-Home su[25440]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:51 MM-Home su[25440]: pam_unix(su:session): session closed for user root
Feb 14 23:32:51 MM-Home su[25444]: (to root) marc on pts/0
Feb 14 23:32:51 MM-Home su[25444]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:51 MM-Home su[25444]: pam_unix(su:session): session closed for user root
Feb 14 23:32:51 MM-Home su[25448]: (to root) marc on pts/0
Feb 14 23:32:51 MM-Home su[25448]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:52 MM-Home su[25448]: pam_unix(su:session): session closed for user root
Feb 14 23:32:52 MM-Home su[25452]: (to root) marc on pts/0
Feb 14 23:32:52 MM-Home su[25452]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:52 MM-Home su[25452]: pam_unix(su:session): session closed for user root
Feb 14 23:32:52 MM-Home su[25456]: (to root) marc on pts/0
Feb 14 23:32:52 MM-Home su[25456]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:53 MM-Home su[25456]: pam_unix(su:session): session closed for user root
Feb 14 23:32:53 MM-Home su[25460]: (to root) marc on pts/0
Feb 14 23:32:53 MM-Home su[25460]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:53 MM-Home su[25460]: pam_unix(su:session): session closed for user root
Feb 14 23:32:54 MM-Home su[25464]: (to root) marc on pts/0
Feb 14 23:32:54 MM-Home su[25464]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:54 MM-Home su[25464]: pam_unix(su:session): session closed for user root
Feb 14 23:32:54 MM-Home su[25469]: (to root) marc on pts/0
Feb 14 23:32:54 MM-Home su[25469]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:55 MM-Home su[25469]: pam_unix(su:session): session closed for user root
Feb 14 23:32:55 MM-Home su[25473]: (to root) marc on pts/0
Feb 14 23:32:55 MM-Home su[25473]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:55 MM-Home su[25473]: pam_unix(su:session): session closed for user root
Feb 14 23:32:55 MM-Home su[25477]: (to root) marc on pts/0
Feb 14 23:32:55 MM-Home su[25477]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:55 MM-Home su[25477]: pam_unix(su:session): session closed for user root
Feb 14 23:32:55 MM-Home su[25481]: (to root) marc on pts/0
Feb 14 23:32:55 MM-Home su[25481]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:55 MM-Home su[25481]: pam_unix(su:session): session closed for user root
Feb 14 23:32:55 MM-Home su[25485]: (to root) marc on pts/0
Feb 14 23:32:55 MM-Home su[25485]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:55 MM-Home su[25485]: pam_unix(su:session): session closed for user root
Feb 14 23:32:56 MM-Home su[25489]: (to root) marc on pts/0
Feb 14 23:32:56 MM-Home su[25489]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:56 MM-Home su[25489]: pam_unix(su:session): session closed for user root
Feb 14 23:32:56 MM-Home su[25493]: (to root) marc on pts/0
Feb 14 23:32:56 MM-Home su[25493]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:56 MM-Home su[25493]: pam_unix(su:session): session closed for user root
Feb 14 23:32:56 MM-Home su[25497]: (to root) marc on pts/0
Feb 14 23:32:56 MM-Home su[25497]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:32:57 MM-Home dbus[1030]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Feb 14 23:32:57 MM-Home dbus[1030]: [system] Successfully activated service 'org.opensuse.Snapper'
Feb 14 23:33:04 MM-Home su[25497]: pam_unix(su:session): session closed for user root
Feb 14 23:33:05 MM-Home su[31092]: (to root) marc on pts/0
Feb 14 23:33:05 MM-Home su[31092]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:33:05 MM-Home su[31092]: pam_unix(su:session): session closed for user root
Feb 14 23:33:07 MM-Home install.py[17753]: hplip-install[17753]: warning: An optional dependency 'reportlab (Reportlab - PDF library for Python)' is still missing.
Feb 14 23:33:07 MM-Home install.py[17753]: hplip-install[17753]: warning: Some features may not function as expected.
Feb 14 23:33:43 MM-Home su[9964]: (to root) marc on pts/0
Feb 14 23:33:43 MM-Home su[9964]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 23:33:45 MM-Home su[9964]: pam_unix(su:session): session closed for user root
Feb 14 23:39:01 MM-Home kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=c8:60:00:09:38:76:64:51:06:1c:d0:c7:08:00 SRC=192.168.178.236 DST=192.168.178.12 LEN=679 TOS=0x00 PREC=0x00 TTL=64 ID=2 PROTO=UDP SPT=427 DPT=43911 LEN=659 
Feb 14 23:39:05 MM-Home hp-setup[11094]: hp-setup[11094]: error: No devices found on bus: net
Feb 14 23:39:05 MM-Home hp-setup[11094]: hp-setup[11094]: warning:  HPLIP cannot detect printers in your network.  This may be due to existing firewall settings blocking the required ports.
                                                         When you are in a trusted network environment, you may open the ports for network services like mdns and slp in the firewall. For detailed steps follow the link.
                                                          http://hplipopensource.com/node/375
Feb 14 23:45:01 MM-Home cron[11153]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 23:45:01 MM-Home systemd[11154]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 14 23:45:01 MM-Home CRON[11153]: pam_unix(crond:session): session closed for user root
Feb 14 23:45:01 MM-Home systemd[11155]: pam_unix(systemd-user:session): session closed for user root
Feb 14 23:46:42 MM-Home kernel: usb 5-1: new high-speed USB device number 3 using xhci_hcd
Feb 14 23:46:43 MM-Home kernel: usb 5-1: New USB device found, idVendor=03f0, idProduct=5d12
Feb 14 23:46:43 MM-Home kernel: usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 14 23:46:43 MM-Home kernel: usb 5-1: Product: Officejet 6600
Feb 14 23:46:43 MM-Home kernel: usb 5-1: Manufacturer: HP
Feb 14 23:46:43 MM-Home kernel: usb 5-1: SerialNumber: CN4849R23505RN
Feb 14 23:46:43 MM-Home systemd-udevd[506]: Network interface NamePolicy= disabled on kernel commandline, ignoring.
Feb 14 23:46:43 MM-Home logger[11203]: loading HP Device 005 003
Feb 14 23:46:43 MM-Home python[11204]: io/hpmud/musb.c 2179: [11204] hpmud_make_usb_uri() bus=005 dev=003
Feb 14 23:46:43 MM-Home python[11204]: io/hpmud/musb.c 2276: hpmud_make_usb_uri() uri=hp:/usb/Officejet_6600?serial=CN4849R23505RN bytes_read=44
Feb 14 23:46:43 MM-Home kernel: usblp 5-1:1.1: usblp0: USB Bidirectional printer dev 3 if 1 alt 0 proto 2 vid 0x03F0 pid 0x5D12
Feb 14 23:46:43 MM-Home kernel: usblp 5-1:1.2: usblp1: USB Bidirectional printer dev 3 if 2 alt 0 proto 2 vid 0x03F0 pid 0x5D12
Feb 14 23:46:43 MM-Home kernel: usbcore: registered new interface driver usblp
Feb 14 23:47:06 MM-Home hp-setup[11094]: io/hpmud/musb.c 427: Found interface conf=0, iface=1, altset=0, index=1
Feb 14 23:47:06 MM-Home hp-setup[11094]: io/hpmud/musb.c 389: Active kernel driver on interface=1 ret=1
Feb 14 23:47:06 MM-Home hp-setup[11094]: io/hpmud/musb.c 393: Detaching kernel driver on interface=1 ret=0
Feb 14 23:47:06 MM-Home hp-setup[11094]: io/hpmud/musb.c 535: claimed 7/1/2 interface
Feb 14 23:47:06 MM-Home hp-setup[11094]: io/hpmud/musb.c 779: read actual device_id successfully fd=1 len=504
Feb 14 23:47:06 MM-Home hp-setup[11094]: io/hpmud/musb.c 561: released 7/1/2 interface
Feb 14 23:47:06 MM-Home hp-setup[11094]: io/hpmud/musb.c 427: Found interface conf=0, iface=1, altset=0, index=1
Feb 14 23:47:06 MM-Home hp-setup[11094]: io/hpmud/musb.c 389: Active kernel driver on interface=1 ret=0
Feb 14 23:47:06 MM-Home hp-setup[11094]: io/hpmud/musb.c 535: claimed 7/1/2 interface
Feb 14 23:47:06 MM-Home hp-setup[11094]: io/hpmud/musb.c 779: read actual device_id successfully fd=1 len=504
Feb 14 23:47:06 MM-Home hp-setup[11094]: io/hpmud/musb.c 561: released 7/1/2 interface
Feb 14 23:47:06 MM-Home hp-setup[11094]: io/hpmud/musb.c 959: new HP-LEDM-SCAN channel=24 clientCnt=1 channelCnt=1
Feb 14 23:47:06 MM-Home hp-setup[11094]: io/hpmud/musb.c 427: Found interface conf=0, iface=0, altset=0, index=11
Feb 14 23:47:06 MM-Home hp-setup[11094]: io/hpmud/musb.c 389: Active kernel driver on interface=0 ret=0
Feb 14 23:47:06 MM-Home hp-setup[11094]: io/hpmud/musb.c 535: claimed ff/cc/0 interface
Feb 14 23:47:06 MM-Home kernel: usblp0: removed
Feb 14 23:47:06 MM-Home kernel: Did not find alt setting 1 for intf 0, config 1
Feb 14 23:47:06 MM-Home kernel: Did not find alt setting 1 for intf 0, config 1
Feb 14 23:47:25 MM-Home hp-setup[11094]: io/hpmud/musb.c 561: released ff/cc/0 interface
Feb 14 23:47:25 MM-Home hp-setup[11094]: io/hpmud/musb.c 974: removed HP-LEDM-SCAN channel=24 clientCnt=0 channelCnt=0
Feb 14 23:49:48 MM-Home kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=c8:60:00:09:38:76:08:96:d7:82:8c:d3:08:00 SRC=192.168.178.1 DST=192.168.178.12 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=27556 DF PROTO=TCP SPT=53454 DPT=14013 WINDOW=5840 RES=0x00 SYN URGP=0 OPT (020405B40402080A201F7D500000000001030302) 
Feb 14 23:49:50 MM-Home kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=c8:60:00:09:38:76:08:96:d7:82:8c:d3:08:00 SRC=192.168.178.1 DST=192.168.178.12 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=59288 DF PROTO=TCP SPT=39385 DPT=80 WINDOW=5840 RES=0x00 SYN URGP=0 OPT (020405B40402080A201F7EA40000000001030302) 
Feb 14 23:49:51 MM-Home kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=c8:60:00:09:38:76:08:96:d7:82:8c:d3:08:00 SRC=192.168.178.1 DST=192.168.178.12 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=27557 DF PROTO=TCP SPT=53454 DPT=14013 WINDOW=5840 RES=0x00 SYN URGP=0 OPT (020405B40402080A201F803E0000000001030302) 
Feb 14 23:49:53 MM-Home kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=c8:60:00:09:38:76:08:96:d7:82:8c:d3:08:00 SRC=192.168.178.1 DST=192.168.178.12 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=59289 DF PROTO=TCP SPT=39385 DPT=80 WINDOW=5840 RES=0x00 SYN URGP=0 OPT (020405B40402080A201F81920000000001030302) 
Feb 14 23:49:57 MM-Home kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=c8:60:00:09:38:76:08:96:d7:82:8c:d3:08:00 SRC=192.168.178.1 DST=192.168.178.12 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=27558 DF PROTO=TCP SPT=53454 DPT=14013 WINDOW=5840 RES=0x00 SYN URGP=0 OPT (020405B40402080A201F861A0000000001030302) 
Feb 14 23:50:15 MM-Home hp-setup[11094]: io/hpmud/musb.c 427: Found interface conf=0, iface=1, altset=0, index=1
Feb 14 23:50:15 MM-Home hp-setup[11094]: io/hpmud/musb.c 389: Active kernel driver on interface=1 ret=0
Feb 14 23:50:15 MM-Home hp-setup[11094]: io/hpmud/musb.c 535: claimed 7/1/2 interface
Feb 14 23:50:15 MM-Home hp-setup[11094]: io/hpmud/musb.c 779: read actual device_id successfully fd=1 len=504
Feb 14 23:50:15 MM-Home hp-setup[11094]: io/hpmud/musb.c 561: released 7/1/2 interface
Feb 14 23:50:15 MM-Home hp-setup[11094]: io/hpmud/musb.c 427: Found interface conf=0, iface=1, altset=0, index=1
Feb 14 23:50:15 MM-Home hp-setup[11094]: io/hpmud/musb.c 389: Active kernel driver on interface=1 ret=0
Feb 14 23:50:15 MM-Home hp-setup[11094]: io/hpmud/musb.c 535: claimed 7/1/2 interface
Feb 14 23:50:15 MM-Home hp-setup[11094]: io/hpmud/musb.c 779: read actual device_id successfully fd=1 len=504
Feb 14 23:50:15 MM-Home hp-setup[11094]: io/hpmud/musb.c 561: released 7/1/2 interface
Feb 14 23:50:15 MM-Home hp-setup[11094]: io/hpmud/musb.c 959: new HP-LEDM-SCAN channel=24 clientCnt=1 channelCnt=1
Feb 14 23:50:15 MM-Home hp-setup[11094]: io/hpmud/musb.c 427: Found interface conf=0, iface=0, altset=0, index=11
Feb 14 23:50:15 MM-Home hp-setup[11094]: io/hpmud/musb.c 389: Active kernel driver on interface=0 ret=0
Feb 14 23:50:15 MM-Home hp-setup[11094]: io/hpmud/musb.c 535: claimed ff/cc/0 interface
Feb 14 23:50:15 MM-Home kernel: Did not find alt setting 1 for intf 0, config 1
Feb 14 23:50:15 MM-Home kernel: Did not find alt setting 1 for intf 0, config 1
Feb 14 23:50:53 MM-Home hp-setup[11094]: io/hpmud/musb.c 561: released ff/cc/0 interface
Feb 14 23:50:53 MM-Home hp-setup[11094]: io/hpmud/musb.c 974: removed HP-LEDM-SCAN channel=24 clientCnt=0 channelCnt=0
Feb 14 23:51:29 MM-Home hp-systray[11279]: hp-systray[11279]: error: Unable to lock /home/marc/.hplip/hp-systray.lock. Is hp-systray already running?
Feb 14 23:51:50 MM-Home kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=c8:60:00:09:38:76:08:96:d7:82:8c:d3:08:00 SRC=192.168.178.1 DST=192.168.178.12 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=22394 DF PROTO=TCP SPT=39519 DPT=80 WINDOW=5840 RES=0x00 SYN URGP=0 OPT (020405B40402080A201FF4030000000001030302) 
Feb 14 23:51:53 MM-Home kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=c8:60:00:09:38:76:08:96:d7:82:8c:d3:08:00 SRC=192.168.178.1 DST=192.168.178.12 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=22395 DF PROTO=TCP SPT=39519 DPT=80 WINDOW=5840 RES=0x00 SYN URGP=0 OPT (020405B40402080A201FF6F10000000001030302) 
Feb 14 23:51:59 MM-Home kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=c8:60:00:09:38:76:08:96:d7:82:8c:d3:08:00 SRC=192.168.178.1 DST=192.168.178.12 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=22396 DF PROTO=TCP SPT=39519 DPT=80 WINDOW=5840 RES=0x00 SYN URGP=0 OPT (020405B40402080A201FFCCD0000000001030302) 
Feb 14 23:52:52 MM-Home hp-setup[11284]: hp-setup[11284]: error:  Printer queue setup failed.   Error : successful-ok-ignored-or-substituted-attributes
Feb 14 23:52:56 MM-Home hp-setup[11284]: [11284]: error: Print command failed with exit code 256!
Feb 14 23:52:56 MM-Home hp-setup[11284]: hp-setup[11284]: error:  Fax queue setup failed.  Error : successful-ok-ignored-or-substituted-attributes
Feb 14 23:54:47 MM-Home python[11303]: io/hpmud/jd.c 678: timeout read_channel sec=5 hpfax:/net/Officejet_6600?ip=192.168.178.236
Feb 14 23:54:52 MM-Home python[11303]: io/hpmud/jd.c 678: timeout read_channel sec=5 hpfax:/net/Officejet_6600?ip=192.168.178.236
Feb 14 23:55:24 MM-Home org.freedesktop.secrets[1813]: gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used
Feb 14 23:55:24 MM-Home gnome-keyring-daemon[11367]: couldn't access control socket: /run/user/1000/keyring/control: Datei oder Verzeichnis nicht gefunden
Feb 14 23:55:24 MM-Home org.freedesktop.secrets[1813]: ** Message: couldn't access control socket: /run/user/1000/keyring/control: Datei oder Verzeichnis nicht gefunden
Feb 14 23:55:42 MM-Home dbus[1030]: [system] Rejected send message, 9 matched rules; type="method_return", sender=":1.1" (uid=486 pid=1031 comm="avahi-daemon: starting up ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.338" (uid=1000 pid=6438 comm="/usr/lib64/firefox/firefox http://localhost:631/ ")
Feb 14 23:55:42 MM-Home dbus[1030]: [system] Rejected send message, 9 matched rules; type="method_return", sender=":1.1" (uid=486 pid=1031 comm="avahi-daemon: starting up ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.338" (uid=1000 pid=6438 comm="/usr/lib64/firefox/firefox http://localhost:631/ ")
Feb 14 23:56:10 MM-Home dbus[1030]: [system] Rejected send message, 9 matched rules; type="method_return", sender=":1.1" (uid=486 pid=1031 comm="avahi-daemon: starting up ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.338" (uid=1000 pid=6438 comm="/usr/lib64/firefox/firefox http://localhost:631/ ")
Feb 14 23:56:10 MM-Home dbus[1030]: [system] Rejected send message, 9 matched rules; type="method_return", sender=":1.1" (uid=486 pid=1031 comm="avahi-daemon: starting up ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.338" (uid=1000 pid=6438 comm="/usr/lib64/firefox/firefox http://localhost:631/ ")
Feb 14 23:56:24 MM-Home dbus[1030]: [system] Rejected send message, 9 matched rules; type="method_return", sender=":1.1" (uid=486 pid=1031 comm="avahi-daemon: starting up ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.338" (uid=1000 pid=6438 comm="/usr/lib64/firefox/firefox http://localhost:631/ ")
Feb 14 23:56:24 MM-Home dbus[1030]: [system] Rejected send message, 9 matched rules; type="method_return", sender=":1.1" (uid=486 pid=1031 comm="avahi-daemon: starting up ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.338" (uid=1000 pid=6438 comm="/usr/lib64/firefox/firefox http://localhost:631/ ")
Feb 15 00:00:01 MM-Home cron[11432]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 15 00:00:01 MM-Home systemd[11433]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 15 00:00:01 MM-Home CRON[11432]: pam_unix(crond:session): session closed for user root
Feb 15 00:00:01 MM-Home systemd[11434]: pam_unix(systemd-user:session): session closed for user root
Feb 15 00:09:51 MM-Home dbus[1030]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Feb 15 00:09:51 MM-Home dbus[1030]: [system] Successfully activated service 'org.opensuse.Snapper'
Feb 15 00:10:57 MM-Home su[11655]: The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyring/control
Feb 15 00:10:57 MM-Home su[11655]: gkr-pam: couldn't unlock the login keyring.
Feb 15 00:10:57 MM-Home su[11655]: (to root) marc on pts/1
Feb 15 00:10:57 MM-Home su[11655]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 15 00:10:57 MM-Home su[11655]: pam_unix(su:session): session closed for user root
Feb 15 00:10:57 MM-Home su[11660]: The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyring/control
Feb 15 00:10:57 MM-Home su[11660]: gkr-pam: couldn't unlock the login keyring.
Feb 15 00:10:57 MM-Home su[11660]: (to root) marc on pts/1
Feb 15 00:10:57 MM-Home su[11660]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 15 00:10:57 MM-Home dbus[1030]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Feb 15 00:10:57 MM-Home dbus[1030]: [system] Successfully activated service 'org.opensuse.Snapper'
Feb 15 00:11:34 MM-Home su[11660]: pam_unix(su:session): session closed for user root
Feb 15 00:12:53 MM-Home kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=c8:60:00:09:38:76:08:96:d7:82:8c:d3:08:00 SRC=192.168.178.1 DST=192.168.178.12 LEN=345 TOS=0x00 PREC=0x00 TTL=64 ID=12224 PROTO=UDP SPT=1900 DPT=46452 LEN=325 
Feb 15 00:12:53 MM-Home kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=c8:60:00:09:38:76:08:96:d7:82:8c:d3:08:00 SRC=192.168.178.1 DST=192.168.178.12 LEN=345 TOS=0x00 PREC=0x00 TTL=64 ID=12225 PROTO=UDP SPT=1900 DPT=46452 LEN=325 
Feb 15 00:15:01 MM-Home cron[21534]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 15 00:15:01 MM-Home systemd[21535]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 15 00:15:01 MM-Home CRON[21534]: pam_unix(crond:session): session closed for user root
Feb 15 00:15:01 MM-Home systemd[21536]: pam_unix(systemd-user:session): session closed for user root
Feb 15 00:18:32 MM-Home dbus[1030]: [system] Rejected send message, 9 matched rules; type="method_return", sender=":1.1" (uid=486 pid=1031 comm="avahi-daemon: starting up ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.338" (uid=1000 pid=6438 comm="/usr/lib64/firefox/firefox http://localhost:631/ ")
Feb 15 00:18:32 MM-Home dbus[1030]: [system] Rejected send message, 9 matched rules; type="method_return", sender=":1.1" (uid=486 pid=1031 comm="avahi-daemon: starting up ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.338" (uid=1000 pid=6438 comm="/usr/lib64/firefox/firefox http://localhost:631/ ")
Feb 15 00:21:18 MM-Home dbus[1030]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Feb 15 00:21:18 MM-Home dbus[1030]: [system] Successfully activated service 'org.opensuse.Snapper'
Feb 15 00:21:57 MM-Home su[21683]: The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyring/control
Feb 15 00:21:57 MM-Home su[21683]: gkr-pam: couldn't unlock the login keyring.
Feb 15 00:21:57 MM-Home su[21683]: (to root) marc on pts/1
Feb 15 00:21:57 MM-Home su[21683]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 15 00:21:57 MM-Home su[21683]: pam_unix(su:session): session closed for user root
Feb 15 00:21:57 MM-Home su[21688]: The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyring/control
Feb 15 00:21:57 MM-Home su[21688]: gkr-pam: couldn't unlock the login keyring.
Feb 15 00:21:57 MM-Home su[21688]: (to root) marc on pts/1
Feb 15 00:21:57 MM-Home su[21688]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 15 00:22:43 MM-Home smartd[1037]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 230 to 240
Feb 15 00:24:00 MM-Home su[21688]: pam_unix(su:session): session closed for user root
Feb 15 00:24:23 MM-Home dbus[1030]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service'
Feb 15 00:24:23 MM-Home PackageKit[32314]: daemon start
Feb 15 00:24:23 MM-Home dbus[1030]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Feb 15 00:24:23 MM-Home PackageKit[32314]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 15 00:24:23 MM-Home PackageKit[32314]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 15 00:24:23 MM-Home PackageKit[32314]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 15 00:24:23 MM-Home PackageKit[32314]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 15 00:24:23 MM-Home PackageKit[32314]: refresh-cache transaction /1_dedeadea from uid 1000 finished with success after 35ms
Feb 15 00:24:23 MM-Home PackageKit[32314]: refresh-cache transaction /2_addebded from uid 1000 finished with success after 12ms
Feb 15 00:24:24 MM-Home PackageKit[32314]: get-updates transaction /3_dcdadbdb from uid 1000 finished with success after 945ms
Feb 15 00:24:43 MM-Home PackageKit[32314]: daemon quit
Feb 15 00:24:43 MM-Home packagekitd[32314]: (packagekitd:32314): GLib-CRITICAL **: Source ID 6 was not found when attempting to remove it
Feb 15 00:30:01 MM-Home cron[32352]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 15 00:30:01 MM-Home systemd[32353]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 15 00:30:15 MM-Home dbus[1030]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Feb 15 00:30:15 MM-Home dbus[1030]: [system] Successfully activated service 'org.opensuse.Snapper'
Feb 15 00:31:28 MM-Home CRON[32352]: pam_unix(crond:session): session closed for user root
Feb 15 00:31:28 MM-Home systemd[32354]: pam_unix(systemd-user:session): session closed for user root
Feb 15 00:31:49 MM-Home polkitd[1091]: Operator of unix-session:2 FAILED to authenticate to gain authorization for action org.freedesktop.udisks2.filesystem-mount-system for system-bus-name::1.386 [/usr/bin/dolphin] (owned by unix-user:marc)
Feb 15 00:31:52 MM-Home udisksd[1726]: Mounted /dev/sdc1 at /run/media/marc/OPENSUSE-LE on behalf of uid 1000
Feb 15 00:31:52 MM-Home org.gtk.Private.UDisks2VolumeMonitor[1813]: disc.c:332: error opening file BDMV/index.bdmv
Feb 15 00:31:52 MM-Home org.gtk.Private.UDisks2VolumeMonitor[1813]: disc.c:332: error opening file BDMV/BACKUP/index.bdmv
Feb 15 00:33:01 MM-Home org.kde.kuiserver[1813]: kuiserver: adding job contact for address:  ":1.18"  objectPath:  "/DataEngine/applicationjobs/JobView_2"
Feb 15 00:33:01 MM-Home org.kde.kuiserver[1813]: kuiserver: making async call of terminate for:  "/DataEngine/applicationjobs/JobView_2"
Feb 15 00:33:01 MM-Home org.kde.kuiserver[1813]: kuiserver: removing jobview from list, it finished
Feb 15 00:33:13 MM-Home org.kde.kuiserver[1813]: kuiserver: adding job contact for address:  ":1.18"  objectPath:  "/DataEngine/applicationjobs/JobView_3"
Feb 15 00:33:13 MM-Home org.kde.kuiserver[1813]: kuiserver: making async call of terminate for:  "/DataEngine/applicationjobs/JobView_3"
Feb 15 00:33:13 MM-Home org.kde.kuiserver[1813]: kuiserver: removing jobview from list, it finished
Feb 15 00:34:01 MM-Home org.kde.kuiserver[1813]: kuiserver: adding job contact for address:  ":1.18"  objectPath:  "/DataEngine/applicationjobs/JobView_4"
Feb 15 00:34:02 MM-Home org.kde.kiod5[1813]: org.kde.kio.kpasswdserver: User = "marc" , WindowId = 130023428
Feb 15 00:34:04 MM-Home org.kde.kuiserver[1813]: kuiserver: making async call of terminate for:  "/DataEngine/applicationjobs/JobView_4"
Feb 15 00:34:04 MM-Home org.kde.kuiserver[1813]: kuiserver: removing jobview from list, it finished
Feb 15 00:34:12 MM-Home org.kde.kuiserver[1813]: kuiserver: adding job contact for address:  ":1.18"  objectPath:  "/DataEngine/applicationjobs/JobView_5"
Feb 15 00:34:12 MM-Home org.kde.kuiserver[1813]: kuiserver: making async call of terminate for:  "/DataEngine/applicationjobs/JobView_5"
Feb 15 00:34:12 MM-Home org.kde.kuiserver[1813]: kuiserver: removing jobview from list, it finished
Feb 15 00:34:12 MM-Home org.kde.kuiserver[1813]: kuiserver: making async call of terminate for:  "/DataEngine/applicationjobs/JobView_5"
Feb 15 00:34:12 MM-Home org.kde.kuiserver[1813]: kuiserver: removing jobview from list, it finished
Feb 15 00:34:12 MM-Home org.kde.kuiserver[1813]: kuiserver: making async call of terminate for:  "/DataEngine/applicationjobs/JobView_4"
Feb 15 00:34:12 MM-Home org.kde.kuiserver[1813]: kuiserver: removing jobview from list, it finished
Feb 15 00:34:27 MM-Home org.kde.kiod5[1813]: org.kde.kio.kpasswdserver: User = "marc" , WindowId = 0
Feb 15 00:39:54 MM-Home org.kde.kuiserver[1813]: kuiserver: making async call of terminate for:  "/DataEngine/applicationjobs/JobView_3"
Feb 15 00:39:55 MM-Home org.kde.kuiserver[1813]: kuiserver: removing jobview from list, it finished
Feb 15 00:39:55 MM-Home org.kde.kuiserver[1813]: kuiserver: making async call of terminate for:  "/DataEngine/applicationjobs/JobView_2"
Feb 15 00:39:55 MM-Home org.kde.kuiserver[1813]: kuiserver: removing jobview from list, it finished
Feb 15 00:41:41 MM-Home kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=c8:60:00:09:38:76:08:96:d7:82:8c:d3:08:00 SRC=192.168.178.1 DST=192.168.178.12 LEN=345 TOS=0x00 PREC=0x00 TTL=64 ID=13209 PROTO=UDP SPT=1900 DPT=38371 LEN=325 
Feb 15 00:41:42 MM-Home kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=c8:60:00:09:38:76:08:96:d7:82:8c:d3:08:00 SRC=192.168.178.1 DST=192.168.178.12 LEN=345 TOS=0x00 PREC=0x00 TTL=64 ID=13210 PROTO=UDP SPT=1900 DPT=38371 LEN=325 
Feb 15 00:41:42 MM-Home kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=c8:60:00:09:38:76:08:96:d7:82:8c:d3:08:00 SRC=192.168.178.1 DST=192.168.178.12 LEN=345 TOS=0x00 PREC=0x00 TTL=64 ID=13211 PROTO=UDP SPT=1900 DPT=59029 LEN=325 
Feb 15 00:41:42 MM-Home kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=c8:60:00:09:38:76:08:96:d7:82:8c:d3:08:00 SRC=192.168.178.1 DST=192.168.178.12 LEN=345 TOS=0x00 PREC=0x00 TTL=64 ID=13212 PROTO=UDP SPT=1900 DPT=59029 LEN=325 
Feb 15 00:42:17 MM-Home kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=c8:60:00:09:38:76:08:96:d7:82:8c:d3:08:00 SRC=192.168.178.1 DST=192.168.178.12 LEN=345 TOS=0x00 PREC=0x00 TTL=64 ID=13251 PROTO=UDP SPT=1900 DPT=48359 LEN=325 
Feb 15 00:42:17 MM-Home kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=c8:60:00:09:38:76:08:96:d7:82:8c:d3:08:00 SRC=192.168.178.1 DST=192.168.178.12 LEN=345 TOS=0x00 PREC=0x00 TTL=64 ID=13252 PROTO=UDP SPT=1900 DPT=48359 LEN=325 
Feb 15 00:44:52 MM-Home kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=c8:60:00:09:38:76:08:96:d7:82:8c:d3:08:00 SRC=192.168.178.1 DST=192.168.178.12 LEN=345 TOS=0x00 PREC=0x00 TTL=64 ID=13349 PROTO=UDP SPT=1900 DPT=37047 LEN=325 
Feb 15 00:44:52 MM-Home kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=c8:60:00:09:38:76:08:96:d7:82:8c:d3:08:00 SRC=192.168.178.1 DST=192.168.178.12 LEN=345 TOS=0x00 PREC=0x00 TTL=64 ID=13350 PROTO=UDP SPT=1900 DPT=37047 LEN=325 
Feb 15 00:44:52 MM-Home kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=c8:60:00:09:38:76:08:96:d7:82:8c:d3:08:00 SRC=192.168.178.1 DST=192.168.178.12 LEN=345 TOS=0x00 PREC=0x00 TTL=64 ID=13351 PROTO=UDP SPT=1900 DPT=55035 LEN=325 
Feb 15 00:44:52 MM-Home kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=c8:60:00:09:38:76:08:96:d7:82:8c:d3:08:00 SRC=192.168.178.1 DST=192.168.178.12 LEN=345 TOS=0x00 PREC=0x00 TTL=64 ID=13352 PROTO=UDP SPT=1900 DPT=55035 LEN=325 
Feb 15 00:45:01 MM-Home cron[25009]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 15 00:45:01 MM-Home systemd[25010]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 15 00:45:01 MM-Home CRON[25009]: pam_unix(crond:session): session closed for user root
Feb 15 00:45:01 MM-Home systemd[25011]: pam_unix(systemd-user:session): session closed for user root
Feb 15 00:55:40 MM-Home kcheckpass[25083]: gkr-pam: unlocked login keyring
Feb 15 00:59:14 MM-Home su[25103]: The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyring/control
Feb 15 00:59:14 MM-Home su[25103]: gkr-pam: couldn't unlock the login keyring.
Feb 15 00:59:14 MM-Home su[25103]: (to root) marc on pts/1
Feb 15 00:59:14 MM-Home su[25103]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 15 00:59:14 MM-Home su[25103]: pam_unix(su:session): session closed for user root
Feb 15 00:59:14 MM-Home su[25108]: The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyring/control
Feb 15 00:59:14 MM-Home su[25108]: gkr-pam: couldn't unlock the login keyring.
Feb 15 00:59:14 MM-Home su[25108]: (to root) marc on pts/1
Feb 15 00:59:14 MM-Home su[25108]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 15 00:59:26 MM-Home dbus[1030]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Feb 15 00:59:26 MM-Home dbus[1030]: [system] Successfully activated service 'org.opensuse.Snapper'
Feb 15 01:00:01 MM-Home cron[27439]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 15 01:00:01 MM-Home systemd[27440]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 15 01:00:01 MM-Home CRON[27439]: pam_unix(crond:session): session closed for user root
Feb 15 01:00:01 MM-Home systemd[27441]: pam_unix(systemd-user:session): session closed for user root
Feb 15 01:15:01 MM-Home cron[28641]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 15 01:15:01 MM-Home systemd[28642]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 15 01:15:01 MM-Home CRON[28641]: pam_unix(crond:session): session closed for user root
Feb 15 01:15:01 MM-Home systemd[28643]: pam_unix(systemd-user:session): session closed for user root
Feb 15 01:24:23 MM-Home dbus[1030]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service'
Feb 15 01:24:23 MM-Home PackageKit[28703]: daemon start
Feb 15 01:24:23 MM-Home dbus[1030]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Feb 15 01:24:23 MM-Home PackageKit[28703]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 15 01:24:23 MM-Home PackageKit[28703]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 15 01:24:23 MM-Home PackageKit[28703]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 15 01:24:23 MM-Home PackageKit[28703]: refresh-cache transaction /1_bbcccbbc from uid 1000 finished with failed after 1ms
Feb 15 01:24:23 MM-Home PackageKit[28703]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 15 01:24:23 MM-Home PackageKit[28703]: refresh-cache transaction /2_dabdbaee from uid 1000 finished with failed after 0ms
Feb 15 01:24:43 MM-Home PackageKit[28703]: daemon quit
Feb 15 01:24:43 MM-Home packagekitd[28703]: (packagekitd:28703): GLib-CRITICAL **: Source ID 6 was not found when attempting to remove it
Feb 15 01:27:51 MM-Home dbus[1030]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Feb 15 01:27:51 MM-Home dbus[1030]: [system] Successfully activated service 'org.opensuse.Snapper'
Feb 15 01:30:01 MM-Home cron[31213]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 15 01:30:01 MM-Home systemd[31214]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 15 01:30:02 MM-Home CRON[31213]: pam_unix(crond:session): session closed for user root
Feb 15 01:30:02 MM-Home systemd[31215]: pam_unix(systemd-user:session): session closed for user root
Feb 15 01:41:50 MM-Home su[25108]: pam_unix(su:session): session closed for user root
Feb 15 01:45:01 MM-Home cron[31382]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 15 01:45:01 MM-Home systemd[31383]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 15 01:45:01 MM-Home CRON[31382]: pam_unix(crond:session): session closed for user root
Feb 15 01:45:01 MM-Home systemd[31384]: pam_unix(systemd-user:session): session closed for user root
Feb 15 01:45:40 MM-Home su[31442]: The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyring/control
Feb 15 01:45:40 MM-Home su[31442]: gkr-pam: couldn't unlock the login keyring.
Feb 15 01:45:40 MM-Home su[31442]: (to root) marc on pts/1
Feb 15 01:45:40 MM-Home su[31442]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 15 01:45:40 MM-Home su[31442]: pam_unix(su:session): session closed for user root
Feb 15 01:45:40 MM-Home su[31447]: The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyring/control
Feb 15 01:45:40 MM-Home su[31447]: gkr-pam: couldn't unlock the login keyring.
Feb 15 01:45:40 MM-Home su[31447]: (to root) marc on pts/1
Feb 15 01:45:40 MM-Home su[31447]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 15 01:45:48 MM-Home dbus[1030]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Feb 15 01:45:48 MM-Home dbus[1030]: [system] Successfully activated service 'org.opensuse.Snapper'
Feb 15 01:46:49 MM-Home su[31447]: pam_unix(su:session): session closed for user root
Feb 15 01:49:14 MM-Home kernel: usb 1-1.4: USB disconnect, device number 3
Feb 15 01:49:16 MM-Home kernel: usb 1-1.5: new full-speed USB device number 4 using ehci-pci
Feb 15 01:49:16 MM-Home mtp-probe[401]: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5"
Feb 15 01:49:16 MM-Home mtp-probe[401]: bus: 1, device: 4 was not an MTP device
Feb 15 01:49:16 MM-Home kernel: usb 1-1.5: New USB device found, idVendor=06a3, idProduct=0ccb
Feb 15 01:49:16 MM-Home kernel: usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 15 01:49:16 MM-Home kernel: usb 1-1.5: Product: Cyborg R.A.T.7 Mouse
Feb 15 01:49:16 MM-Home kernel: usb 1-1.5: Manufacturer: Saitek
Feb 15 01:49:16 MM-Home kernel: input: Saitek Cyborg R.A.T.7 Mouse as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0/0003:06A3:0CCB.0004/input/input21
Feb 15 01:49:16 MM-Home kernel: saitek 0003:06A3:0CCB.0004: input,hidraw2: USB HID v1.11 Mouse [Saitek Cyborg R.A.T.7 Mouse] on usb-0000:00:1a.0-1.5/input0
-- Reboot --
Feb 15 12:45:29 linux-ytaf systemd-journal[187]: Runtime journal is using 8.0M (max allowed 397.5M, trying to leave 596.3M free of 3.8G available → current limit 397.5M).
Feb 15 12:45:29 linux-ytaf systemd-journal[187]: Runtime journal is using 8.0M (max allowed 397.5M, trying to leave 596.3M free of 3.8G available → current limit 397.5M).
Feb 15 12:45:29 linux-ytaf kernel: microcode: CPU0 microcode updated early to revision 0x29, date = 2013-06-12
Feb 15 12:45:29 linux-ytaf kernel: Initializing cgroup subsys cpuset
Feb 15 12:45:29 linux-ytaf kernel: Initializing cgroup subsys cpu
Feb 15 12:45:29 linux-ytaf kernel: Initializing cgroup subsys cpuacct
Feb 15 12:45:29 linux-ytaf kernel: Linux version 4.1.15-8-default (geeko@buildhost) (gcc version 4.8.5 (SUSE Linux) ) #1 SMP PREEMPT Wed Jan 20 16:41:00 UTC 2016 (0e3b3ab)
Feb 15 12:45:29 linux-ytaf kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.1.15-8-default root=UUID=21024970-7a27-4114-8525-d8dd026f23b6 ro resume=/dev/sdb2 splash=silent quiet showopts
Feb 15 12:45:29 linux-ytaf kernel: e820: BIOS-provided physical RAM map:
Feb 15 12:45:29 linux-ytaf kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Feb 15 12:45:29 linux-ytaf kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
Feb 15 12:45:29 linux-ytaf kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000deb8efff] usable
Feb 15 12:45:29 linux-ytaf kernel: BIOS-e820: [mem 0x00000000deb8f000-0x00000000dedf1fff] reserved
Feb 15 12:45:29 linux-ytaf kernel: BIOS-e820: [mem 0x00000000dedf2000-0x00000000dee79fff] ACPI NVS
Feb 15 12:45:29 linux-ytaf kernel: BIOS-e820: [mem 0x00000000dee7a000-0x00000000df13efff] reserved
Feb 15 12:45:29 linux-ytaf kernel: BIOS-e820: [mem 0x00000000df13f000-0x00000000df383fff] ACPI NVS
Feb 15 12:45:29 linux-ytaf kernel: BIOS-e820: [mem 0x00000000df384000-0x00000000df391fff] ACPI data
Feb 15 12:45:29 linux-ytaf kernel: BIOS-e820: [mem 0x00000000df392000-0x00000000df3befff] ACPI NVS
Feb 15 12:45:29 linux-ytaf kernel: BIOS-e820: [mem 0x00000000df3bf000-0x00000000df3c3fff] ACPI data
Feb 15 12:45:29 linux-ytaf kernel: BIOS-e820: [mem 0x00000000df3c4000-0x00000000df406fff] ACPI NVS
Feb 15 12:45:29 linux-ytaf kernel: BIOS-e820: [mem 0x00000000df407000-0x00000000df7fffff] usable
Feb 15 12:45:29 linux-ytaf kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Feb 15 12:45:29 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Feb 15 12:45:29 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Feb 15 12:45:29 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Feb 15 12:45:29 linux-ytaf kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Feb 15 12:45:29 linux-ytaf kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Feb 15 12:45:29 linux-ytaf kernel: BIOS-e820: [mem 0x0000000100000000-0x000000021effffff] usable
Feb 15 12:45:29 linux-ytaf kernel: NX (Execute Disable) protection: active
Feb 15 12:45:29 linux-ytaf kernel: e820: update [mem 0x0c81c018-0x0c82bc57] usable ==> usable
Feb 15 12:45:29 linux-ytaf kernel: e820: update [mem 0x0c82c018-0x0c83b857] usable ==> usable
Feb 15 12:45:29 linux-ytaf kernel: e820: update [mem 0x0c2f1018-0x0c2f4e57] usable ==> usable
Feb 15 12:45:29 linux-ytaf kernel: extended physical RAM map:
Feb 15 12:45:29 linux-ytaf kernel: reserve setup_data: [mem 0x0000000000000000-0x000000000009efff] usable
Feb 15 12:45:29 linux-ytaf kernel: reserve setup_data: [mem 0x000000000009f000-0x000000000009ffff] reserved
Feb 15 12:45:29 linux-ytaf kernel: reserve setup_data: [mem 0x0000000000100000-0x000000000c2f1017] usable
Feb 15 12:45:29 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c2f1018-0x000000000c2f4e57] usable
Feb 15 12:45:29 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c2f4e58-0x000000000c81c017] usable
Feb 15 12:45:29 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c81c018-0x000000000c82bc57] usable
Feb 15 12:45:29 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c82bc58-0x000000000c82c017] usable
Feb 15 12:45:29 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c82c018-0x000000000c83b857] usable
Feb 15 12:45:29 linux-ytaf kernel: reserve setup_data: [mem 0x000000000c83b858-0x00000000deb8efff] usable
Feb 15 12:45:29 linux-ytaf kernel: reserve setup_data: [mem 0x00000000deb8f000-0x00000000dedf1fff] reserved
Feb 15 12:45:29 linux-ytaf kernel: reserve setup_data: [mem 0x00000000dedf2000-0x00000000dee79fff] ACPI NVS
Feb 15 12:45:29 linux-ytaf kernel: reserve setup_data: [mem 0x00000000dee7a000-0x00000000df13efff] reserved
Feb 15 12:45:29 linux-ytaf kernel: reserve setup_data: [mem 0x00000000df13f000-0x00000000df383fff] ACPI NVS
Feb 15 12:45:29 linux-ytaf kernel: reserve setup_data: [mem 0x00000000df384000-0x00000000df391fff] ACPI data
Feb 15 12:45:29 linux-ytaf kernel: reserve setup_data: [mem 0x00000000df392000-0x00000000df3befff] ACPI NVS
Feb 15 12:45:29 linux-ytaf kernel: reserve setup_data: [mem 0x00000000df3bf000-0x00000000df3c3fff] ACPI data
Feb 15 12:45:29 linux-ytaf kernel: reserve setup_data: [mem 0x00000000df3c4000-0x00000000df406fff] ACPI NVS
Feb 15 12:45:29 linux-ytaf kernel: reserve setup_data: [mem 0x00000000df407000-0x00000000df7fffff] usable
Feb 15 12:45:29 linux-ytaf kernel: reserve setup_data: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Feb 15 12:45:29 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Feb 15 12:45:29 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Feb 15 12:45:29 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Feb 15 12:45:29 linux-ytaf kernel: reserve setup_data: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Feb 15 12:45:29 linux-ytaf kernel: reserve setup_data: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Feb 15 12:45:29 linux-ytaf kernel: reserve setup_data: [mem 0x0000000100000000-0x000000021effffff] usable
Feb 15 12:45:29 linux-ytaf kernel: efi: EFI v2.31 by American Megatrends
Feb 15 12:45:29 linux-ytaf kernel: efi:  ACPI=0xdf384000  ACPI 2.0=0xdf384000  SMBIOS=0xdec27e98  MPS=0xfc990 
Feb 15 12:45:29 linux-ytaf kernel: SMBIOS 2.6 present.
Feb 15 12:45:29 linux-ytaf kernel: DMI: System manufacturer System Product Name/MAXIMUS IV GENE-Z/GEN3, BIOS 3603 11/09/2012
Feb 15 12:45:29 linux-ytaf kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Feb 15 12:45:29 linux-ytaf kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Feb 15 12:45:29 linux-ytaf kernel: AGP: No AGP bridge found
Feb 15 12:45:29 linux-ytaf kernel: e820: last_pfn = 0x21f000 max_arch_pfn = 0x400000000
Feb 15 12:45:29 linux-ytaf kernel: MTRR default type: uncachable
Feb 15 12:45:29 linux-ytaf kernel: MTRR fixed ranges enabled:
Feb 15 12:45:29 linux-ytaf kernel:   00000-9FFFF write-back
Feb 15 12:45:29 linux-ytaf kernel:   A0000-BFFFF uncachable
Feb 15 12:45:29 linux-ytaf kernel:   C0000-D3FFF write-protect
Feb 15 12:45:29 linux-ytaf kernel:   D4000-DFFFF uncachable
Feb 15 12:45:29 linux-ytaf kernel:   E0000-E7FFF write-through
Feb 15 12:45:29 linux-ytaf kernel:   E8000-FFFFF write-protect
Feb 15 12:45:29 linux-ytaf kernel: MTRR variable ranges enabled:
Feb 15 12:45:29 linux-ytaf kernel:   0 base 000000000 mask E00000000 write-back
Feb 15 12:45:29 linux-ytaf kernel:   1 base 200000000 mask FF0000000 write-back
Feb 15 12:45:29 linux-ytaf kernel:   2 base 210000000 mask FF8000000 write-back
Feb 15 12:45:29 linux-ytaf kernel:   3 base 218000000 mask FFC000000 write-back
Feb 15 12:45:29 linux-ytaf kernel:   4 base 21C000000 mask FFE000000 write-back
Feb 15 12:45:29 linux-ytaf kernel:   5 base 21E000000 mask FFF000000 write-back
Feb 15 12:45:29 linux-ytaf kernel:   6 base 0E0000000 mask FE0000000 uncachable
Feb 15 12:45:29 linux-ytaf kernel:   7 disabled
Feb 15 12:45:29 linux-ytaf kernel:   8 disabled
Feb 15 12:45:29 linux-ytaf kernel:   9 disabled
Feb 15 12:45:29 linux-ytaf kernel: PAT configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- UC  
Feb 15 12:45:29 linux-ytaf kernel: e820: update [mem 0xe0000000-0xffffffff] usable ==> reserved
Feb 15 12:45:29 linux-ytaf kernel: e820: last_pfn = 0xdf800 max_arch_pfn = 0x400000000
Feb 15 12:45:29 linux-ytaf kernel: found SMP MP-table at [mem 0x000fcd30-0x000fcd3f] mapped at [ffff8800000fcd30]
Feb 15 12:45:29 linux-ytaf kernel: Scanning 1 areas for low memory corruption
Feb 15 12:45:29 linux-ytaf kernel: Base memory trampoline at [ffff880000097000] 97000 size 24576
Feb 15 12:45:29 linux-ytaf kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
Feb 15 12:45:29 linux-ytaf kernel:  [mem 0x00000000-0x000fffff] page 4k
Feb 15 12:45:29 linux-ytaf kernel: BRK [0x0e21a000, 0x0e21afff] PGTABLE
Feb 15 12:45:29 linux-ytaf kernel: BRK [0x0e21b000, 0x0e21bfff] PGTABLE
Feb 15 12:45:29 linux-ytaf kernel: BRK [0x0e21c000, 0x0e21cfff] PGTABLE
Feb 15 12:45:29 linux-ytaf kernel: init_memory_mapping: [mem 0x21ee00000-0x21effffff]
Feb 15 12:45:29 linux-ytaf kernel:  [mem 0x21ee00000-0x21effffff] page 2M
Feb 15 12:45:29 linux-ytaf kernel: BRK [0x0e21d000, 0x0e21dfff] PGTABLE
Feb 15 12:45:29 linux-ytaf kernel: init_memory_mapping: [mem 0x200000000-0x21edfffff]
Feb 15 12:45:29 linux-ytaf kernel:  [mem 0x200000000-0x21edfffff] page 2M
Feb 15 12:45:29 linux-ytaf kernel: init_memory_mapping: [mem 0x1e0000000-0x1ffffffff]
Feb 15 12:45:29 linux-ytaf kernel:  [mem 0x1e0000000-0x1ffffffff] page 2M
Feb 15 12:45:29 linux-ytaf kernel: BRK [0x0e21e000, 0x0e21efff] PGTABLE
Feb 15 12:45:29 linux-ytaf kernel: init_memory_mapping: [mem 0x00100000-0xdeb8efff]
Feb 15 12:45:29 linux-ytaf kernel:  [mem 0x00100000-0x001fffff] page 4k
Feb 15 12:45:29 linux-ytaf kernel:  [mem 0x00200000-0xde9fffff] page 2M
Feb 15 12:45:29 linux-ytaf kernel:  [mem 0xdea00000-0xdeb8efff] page 4k
Feb 15 12:45:29 linux-ytaf kernel: init_memory_mapping: [mem 0xdf407000-0xdf7fffff]
Feb 15 12:45:29 linux-ytaf kernel:  [mem 0xdf407000-0xdf5fffff] page 4k
Feb 15 12:45:29 linux-ytaf kernel:  [mem 0xdf600000-0xdf7fffff] page 2M
Feb 15 12:45:29 linux-ytaf kernel: BRK [0x0e21f000, 0x0e21ffff] PGTABLE
Feb 15 12:45:29 linux-ytaf kernel: init_memory_mapping: [mem 0x100000000-0x1dfffffff]
Feb 15 12:45:29 linux-ytaf kernel:  [mem 0x100000000-0x1dfffffff] page 2M
Feb 15 12:45:29 linux-ytaf kernel: RAMDISK: [mem 0x007e1000-0x00ffafff]
Feb 15 12:45:29 linux-ytaf kernel: ACPI: Early table checksum verification disabled
Feb 15 12:45:29 linux-ytaf kernel: ACPI: RSDP 0x00000000DF384000 000024 (v02 ALASKA)
Feb 15 12:45:29 linux-ytaf kernel: ACPI: XSDT 0x00000000DF384078 000064 (v01 ALASKA A M I    01072009 AMI  00010013)
Feb 15 12:45:29 linux-ytaf kernel: ACPI: FACP 0x00000000DF38FC78 0000F4 (v04 ALASKA A M I    01072009 AMI  00010013)
Feb 15 12:45:29 linux-ytaf kernel: ACPI: DSDT 0x00000000DF384170 00BB02 (v02 ALASKA A M I    00000015 INTL 20051117)
Feb 15 12:45:29 linux-ytaf kernel: ACPI: FACS 0x00000000DF3BDF80 000040
Feb 15 12:45:29 linux-ytaf kernel: ACPI: APIC 0x00000000DF38FD70 000092 (v03 ALASKA A M I    01072009 AMI  00010013)
Feb 15 12:45:29 linux-ytaf kernel: ACPI: MCFG 0x00000000DF38FE08 00003C (v01 ALASKA A M I    01072009 MSFT 00000097)
Feb 15 12:45:29 linux-ytaf kernel: ACPI: HPET 0x00000000DF38FE48 000038 (v01 ALASKA A M I    01072009 AMI. 00000005)
Feb 15 12:45:29 linux-ytaf kernel: ACPI: SSDT 0x00000000DF38FE80 00036D (v01 SataRe SataTabl 00001000 INTL 20091112)
Feb 15 12:45:29 linux-ytaf kernel: ACPI: SSDT 0x00000000DF3901F0 0009AA (v01 PmRef  Cpu0Ist  00003000 INTL 20051117)
Feb 15 12:45:29 linux-ytaf kernel: ACPI: SSDT 0x00000000DF390BA0 000A92 (v01 PmRef  CpuPm    00003000 INTL 20051117)
Feb 15 12:45:29 linux-ytaf kernel: ACPI: BGRT 0x00000000DF391690 000038 (v00 ALASKA A M I    01072009 AMI  00010013)
Feb 15 12:45:29 linux-ytaf kernel: ACPI: Local APIC address 0xfee00000
Feb 15 12:45:29 linux-ytaf kernel: No NUMA configuration found
Feb 15 12:45:29 linux-ytaf kernel: Faking a node at [mem 0x0000000000000000-0x000000021effffff]
Feb 15 12:45:29 linux-ytaf kernel: NODE_DATA(0) allocated [mem 0x21efe5000-0x21eff8fff]
Feb 15 12:45:29 linux-ytaf kernel:  [ffffea0000000000-ffffea00087fffff] PMD -> [ffff880216600000-ffff88021e5fffff] on node 0
Feb 15 12:45:29 linux-ytaf kernel: Zone ranges:
Feb 15 12:45:29 linux-ytaf kernel:   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
Feb 15 12:45:29 linux-ytaf kernel:   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
Feb 15 12:45:29 linux-ytaf kernel:   Normal   [mem 0x0000000100000000-0x000000021effffff]
Feb 15 12:45:29 linux-ytaf kernel: Movable zone start for each node
Feb 15 12:45:29 linux-ytaf kernel: Early memory node ranges
Feb 15 12:45:29 linux-ytaf kernel:   node   0: [mem 0x0000000000001000-0x000000000009efff]
Feb 15 12:45:29 linux-ytaf kernel:   node   0: [mem 0x0000000000100000-0x00000000deb8efff]
Feb 15 12:45:29 linux-ytaf kernel:   node   0: [mem 0x00000000df407000-0x00000000df7fffff]
Feb 15 12:45:29 linux-ytaf kernel:   node   0: [mem 0x0000000100000000-0x000000021effffff]
Feb 15 12:45:29 linux-ytaf kernel: Initmem setup node 0 [mem 0x0000000000001000-0x000000021effffff]
Feb 15 12:45:29 linux-ytaf kernel: On node 0 totalpages: 2088742
Feb 15 12:45:29 linux-ytaf kernel:   DMA zone: 64 pages used for memmap
Feb 15 12:45:29 linux-ytaf kernel:   DMA zone: 2115 pages reserved
Feb 15 12:45:29 linux-ytaf kernel:   DMA zone: 3998 pages, LIFO batch:0
Feb 15 12:45:29 linux-ytaf kernel:   DMA32 zone: 14207 pages used for memmap
Feb 15 12:45:29 linux-ytaf kernel:   DMA32 zone: 909192 pages, LIFO batch:31
Feb 15 12:45:29 linux-ytaf kernel:   Normal zone: 18368 pages used for memmap
Feb 15 12:45:29 linux-ytaf kernel:   Normal zone: 1175552 pages, LIFO batch:31
Feb 15 12:45:29 linux-ytaf kernel: tboot: non-0 tboot_addr but it is not of type E820_RESERVED
Feb 15 12:45:29 linux-ytaf kernel: ACPI: PM-Timer IO Port: 0x408
Feb 15 12:45:29 linux-ytaf kernel: ACPI: Local APIC address 0xfee00000
Feb 15 12:45:29 linux-ytaf kernel: ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
Feb 15 12:45:29 linux-ytaf kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
Feb 15 12:45:29 linux-ytaf kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Feb 15 12:45:29 linux-ytaf kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Feb 15 12:45:29 linux-ytaf kernel: ACPI: IRQ0 used by override.
Feb 15 12:45:29 linux-ytaf kernel: ACPI: IRQ9 used by override.
Feb 15 12:45:29 linux-ytaf kernel: Using ACPI (MADT) for SMP configuration information
Feb 15 12:45:29 linux-ytaf kernel: ACPI: HPET id: 0x8086a701 base: 0xfed00000
Feb 15 12:45:29 linux-ytaf kernel: smpboot: Allowing 8 CPUs, 0 hotplug CPUs
Feb 15 12:45:29 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
Feb 15 12:45:29 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Feb 15 12:45:29 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000fffff]
Feb 15 12:45:29 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c2f1000-0x0c2f1fff]
Feb 15 12:45:29 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c2f4000-0x0c2f4fff]
Feb 15 12:45:29 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c81c000-0x0c81cfff]
Feb 15 12:45:29 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c82b000-0x0c82bfff]
Feb 15 12:45:29 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c82c000-0x0c82cfff]
Feb 15 12:45:29 linux-ytaf kernel: PM: Registered nosave memory: [mem 0x0c83b000-0x0c83bfff]
Feb 15 12:45:29 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xdeb8f000-0xdedf1fff]
Feb 15 12:45:29 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xdedf2000-0xdee79fff]
Feb 15 12:45:29 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xdee7a000-0xdf13efff]
Feb 15 12:45:29 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xdf13f000-0xdf383fff]
Feb 15 12:45:29 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xdf384000-0xdf391fff]
Feb 15 12:45:29 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xdf392000-0xdf3befff]
Feb 15 12:45:29 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xdf3bf000-0xdf3c3fff]
Feb 15 12:45:29 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xdf3c4000-0xdf406fff]
Feb 15 12:45:29 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xdf800000-0xf7ffffff]
Feb 15 12:45:29 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
Feb 15 12:45:29 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfc000000-0xfebfffff]
Feb 15 12:45:29 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
Feb 15 12:45:29 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfec01000-0xfecfffff]
Feb 15 12:45:29 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed00000-0xfed03fff]
Feb 15 12:45:29 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed04000-0xfed1bfff]
Feb 15 12:45:29 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Feb 15 12:45:29 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfed20000-0xfedfffff]
Feb 15 12:45:29 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
Feb 15 12:45:29 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xfee01000-0xfeffffff]
Feb 15 12:45:29 linux-ytaf kernel: PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Feb 15 12:45:29 linux-ytaf kernel: e820: [mem 0xdf800000-0xf7ffffff] available for PCI devices
Feb 15 12:45:29 linux-ytaf kernel: Booting paravirtualized kernel on bare hardware
Feb 15 12:45:29 linux-ytaf kernel: clocksource refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
Feb 15 12:45:29 linux-ytaf kernel: setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:8 nr_node_ids:1
Feb 15 12:45:29 linux-ytaf kernel: PERCPU: Embedded 33 pages/cpu @ffff88021ec00000 s97368 r8192 d29608 u262144
Feb 15 12:45:29 linux-ytaf kernel: pcpu-alloc: s97368 r8192 d29608 u262144 alloc=1*2097152
Feb 15 12:45:29 linux-ytaf kernel: pcpu-alloc: [0] 0 1 2 3 4 5 6 7 
Feb 15 12:45:29 linux-ytaf kernel: Built 1 zonelists in Node order, mobility grouping on.  Total pages: 2053988
Feb 15 12:45:29 linux-ytaf kernel: Policy zone: Normal
Feb 15 12:45:29 linux-ytaf kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.1.15-8-default root=UUID=21024970-7a27-4114-8525-d8dd026f23b6 ro resume=/dev/sdb2 splash=silent quiet showopts
Feb 15 12:45:29 linux-ytaf kernel: log_buf_len individual max cpu contribution: 32768 bytes
Feb 15 12:45:29 linux-ytaf kernel: log_buf_len total cpu_extra contributions: 229376 bytes
Feb 15 12:45:29 linux-ytaf kernel: log_buf_len min size: 262144 bytes
Feb 15 12:45:29 linux-ytaf kernel: log_buf_len: 524288 bytes
Feb 15 12:45:29 linux-ytaf kernel: early log buf free: 247532(94%)
Feb 15 12:45:29 linux-ytaf kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
Feb 15 12:45:29 linux-ytaf kernel: xsave: enabled xstate_bv 0x7, cntxt size 0x340 using standard form
Feb 15 12:45:29 linux-ytaf kernel: AGP: Checking aperture...
Feb 15 12:45:29 linux-ytaf kernel: AGP: No AGP bridge found
Feb 15 12:45:29 linux-ytaf kernel: Memory: 7939116K/8354968K available (6547K kernel code, 1084K rwdata, 4848K rodata, 1560K init, 1516K bss, 415852K reserved, 0K cma-reserved)
Feb 15 12:45:29 linux-ytaf kernel: Preemptible hierarchical RCU implementation.
Feb 15 12:45:29 linux-ytaf kernel:         RCU dyntick-idle grace-period acceleration is enabled.
Feb 15 12:45:29 linux-ytaf kernel:         RCU restricting CPUs from NR_CPUS=512 to nr_cpu_ids=8.
Feb 15 12:45:29 linux-ytaf kernel: RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
Feb 15 12:45:29 linux-ytaf kernel: NR_IRQS:33024 nr_irqs:488 16
Feb 15 12:45:29 linux-ytaf kernel:         Offload RCU callbacks from all CPUs
Feb 15 12:45:29 linux-ytaf kernel:         Offload RCU callbacks from CPUs: 0-7.
Feb 15 12:45:29 linux-ytaf kernel: Console: colour dummy device 80x25
Feb 15 12:45:29 linux-ytaf kernel: console [tty0] enabled
Feb 15 12:45:29 linux-ytaf kernel: clocksource hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484882848 ns
Feb 15 12:45:29 linux-ytaf kernel: hpet clockevent registered
Feb 15 12:45:29 linux-ytaf kernel: tsc: Fast TSC calibration using PIT
Feb 15 12:45:29 linux-ytaf kernel: tsc: Detected 3411.250 MHz processor
Feb 15 12:45:29 linux-ytaf kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 6822.50 BogoMIPS (lpj=13645000)
Feb 15 12:45:29 linux-ytaf kernel: pid_max: default: 32768 minimum: 301
Feb 15 12:45:29 linux-ytaf kernel: ACPI: Core revision 20150410
Feb 15 12:45:29 linux-ytaf kernel: ACPI: All ACPI Tables successfully acquired
Feb 15 12:45:29 linux-ytaf kernel: Security Framework initialized
Feb 15 12:45:29 linux-ytaf kernel: AppArmor: AppArmor initialized
Feb 15 12:45:29 linux-ytaf kernel: Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
Feb 15 12:45:29 linux-ytaf kernel: Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
Feb 15 12:45:29 linux-ytaf kernel: Mount-cache hash table entries: 16384 (order: 5, 131072 bytes)
Feb 15 12:45:29 linux-ytaf kernel: Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes)
Feb 15 12:45:29 linux-ytaf kernel: Initializing cgroup subsys blkio
Feb 15 12:45:29 linux-ytaf kernel: Initializing cgroup subsys memory
Feb 15 12:45:29 linux-ytaf kernel: Initializing cgroup subsys devices
Feb 15 12:45:29 linux-ytaf kernel: Initializing cgroup subsys freezer
Feb 15 12:45:29 linux-ytaf kernel: Initializing cgroup subsys net_cls
Feb 15 12:45:29 linux-ytaf kernel: Initializing cgroup subsys perf_event
Feb 15 12:45:29 linux-ytaf kernel: Initializing cgroup subsys net_prio
Feb 15 12:45:29 linux-ytaf kernel: Initializing cgroup subsys hugetlb
Feb 15 12:45:29 linux-ytaf kernel: CPU: Physical Processor ID: 0
Feb 15 12:45:29 linux-ytaf kernel: CPU: Processor Core ID: 0
Feb 15 12:45:29 linux-ytaf kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Feb 15 12:45:29 linux-ytaf kernel: ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Feb 15 12:45:29 linux-ytaf kernel: mce: CPU supports 9 MCE banks
Feb 15 12:45:29 linux-ytaf kernel: CPU0: Thermal monitoring enabled (TM1)
Feb 15 12:45:29 linux-ytaf kernel: process: using mwait in idle threads
Feb 15 12:45:29 linux-ytaf kernel: Last level iTLB entries: 4KB 512, 2MB 8, 4MB 8
Feb 15 12:45:29 linux-ytaf kernel: Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32, 1GB 0
Feb 15 12:45:29 linux-ytaf kernel: Freeing SMP alternatives memory: 24K (ffffffff82097000 - ffffffff8209d000)
Feb 15 12:45:29 linux-ytaf kernel: ftrace: allocating 25000 entries in 98 pages
Feb 15 12:45:29 linux-ytaf kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Feb 15 12:45:29 linux-ytaf kernel: TSC deadline timer enabled
Feb 15 12:45:29 linux-ytaf kernel: smpboot: CPU0: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz (fam: 06, model: 2a, stepping: 07)
Feb 15 12:45:29 linux-ytaf kernel: Performance Events: PEBS fmt1+, 16-deep LBR, SandyBridge events, full-width counters, Intel PMU driver.
Feb 15 12:45:29 linux-ytaf kernel: ... version:                3
Feb 15 12:45:29 linux-ytaf kernel: ... bit width:              48
Feb 15 12:45:29 linux-ytaf kernel: ... generic registers:      4
Feb 15 12:45:29 linux-ytaf kernel: ... value mask:             0000ffffffffffff
Feb 15 12:45:29 linux-ytaf kernel: ... max period:             0000ffffffffffff
Feb 15 12:45:29 linux-ytaf kernel: ... fixed-purpose events:   3
Feb 15 12:45:29 linux-ytaf kernel: ... event mask:             000000070000000f
Feb 15 12:45:29 linux-ytaf kernel: x86: Booting SMP configuration:
Feb 15 12:45:29 linux-ytaf kernel: .... node  #0, CPUs:      #1
Feb 15 12:45:29 linux-ytaf kernel: microcode: CPU1 microcode updated early to revision 0x29, date = 2013-06-12
Feb 15 12:45:29 linux-ytaf kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Feb 15 12:45:29 linux-ytaf kernel:  #2
Feb 15 12:45:29 linux-ytaf kernel: microcode: CPU2 microcode updated early to revision 0x29, date = 2013-06-12
Feb 15 12:45:29 linux-ytaf kernel:  #3
Feb 15 12:45:29 linux-ytaf kernel: microcode: CPU3 microcode updated early to revision 0x29, date = 2013-06-12
Feb 15 12:45:29 linux-ytaf kernel:  #4 #5 #6 #7
Feb 15 12:45:29 linux-ytaf kernel: x86: Booted up 1 node, 8 CPUs
Feb 15 12:45:29 linux-ytaf kernel: smpboot: Total of 8 processors activated (54580.00 BogoMIPS)
Feb 15 12:45:29 linux-ytaf kernel: devtmpfs: initialized
Feb 15 12:45:29 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xdedf2000-0xdee79fff] (557056 bytes)
Feb 15 12:45:29 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xdf13f000-0xdf383fff] (2379776 bytes)
Feb 15 12:45:29 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xdf392000-0xdf3befff] (184320 bytes)
Feb 15 12:45:29 linux-ytaf kernel: PM: Registering ACPI NVS region [mem 0xdf3c4000-0xdf406fff] (274432 bytes)
Feb 15 12:45:29 linux-ytaf kernel: clocksource jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
Feb 15 12:45:29 linux-ytaf kernel: pinctrl core: initialized pinctrl subsystem
Feb 15 12:45:29 linux-ytaf kernel: RTC time: 12:45:26, date: 02/15/16
Feb 15 12:45:29 linux-ytaf kernel: NET: Registered protocol family 16
Feb 15 12:45:29 linux-ytaf kernel: cpuidle: using governor ladder
Feb 15 12:45:29 linux-ytaf kernel: cpuidle: using governor menu
Feb 15 12:45:29 linux-ytaf kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
Feb 15 12:45:29 linux-ytaf kernel: ACPI: bus type PCI registered
Feb 15 12:45:29 linux-ytaf kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Feb 15 12:45:29 linux-ytaf kernel: PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
Feb 15 12:45:29 linux-ytaf kernel: PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
Feb 15 12:45:29 linux-ytaf kernel: PCI: Using configuration type 1 for base access
Feb 15 12:45:29 linux-ytaf kernel: perf_event_intel: PMU erratum BJ122, BV98, HSD29 worked around, HT is on
Feb 15 12:45:29 linux-ytaf kernel: ACPI: Added _OSI(Module Device)
Feb 15 12:45:29 linux-ytaf kernel: ACPI: Added _OSI(Processor Device)
Feb 15 12:45:29 linux-ytaf kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
Feb 15 12:45:29 linux-ytaf kernel: ACPI: Added _OSI(Processor Aggregator Device)
Feb 15 12:45:29 linux-ytaf kernel: ACPI: Executed 1 blocks of module-level executable AML code
Feb 15 12:45:29 linux-ytaf kernel: ACPI: Dynamic OEM Table Load:
Feb 15 12:45:29 linux-ytaf kernel: ACPI: SSDT 0xFFFF880214FC7000 00083B (v01 PmRef  Cpu0Cst  00003001 INTL 20051117)
Feb 15 12:45:29 linux-ytaf kernel: ACPI: Dynamic OEM Table Load:
Feb 15 12:45:29 linux-ytaf kernel: ACPI: SSDT 0xFFFF880214FC1400 000303 (v01 PmRef  ApIst    00003000 INTL 20051117)
Feb 15 12:45:29 linux-ytaf kernel: ACPI: Dynamic OEM Table Load:
Feb 15 12:45:29 linux-ytaf kernel: ACPI: SSDT 0xFFFF880214F72600 000119 (v01 PmRef  ApCst    00003000 INTL 20051117)
Feb 15 12:45:29 linux-ytaf kernel: ACPI : EC: EC started
Feb 15 12:45:29 linux-ytaf kernel: ACPI: Interpreter enabled
Feb 15 12:45:29 linux-ytaf kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20150410/hwxface-580)
Feb 15 12:45:29 linux-ytaf kernel: ACPI: (supports S0 S1 S3 S4 S5)
Feb 15 12:45:29 linux-ytaf kernel: ACPI: Using IOAPIC for interrupt routing
Feb 15 12:45:29 linux-ytaf kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Feb 15 12:45:29 linux-ytaf kernel: ACPI: Power Resource [FN00] (off)
Feb 15 12:45:29 linux-ytaf kernel: ACPI: Power Resource [FN01] (off)
Feb 15 12:45:29 linux-ytaf kernel: ACPI: Power Resource [FN02] (off)
Feb 15 12:45:29 linux-ytaf kernel: ACPI: Power Resource [FN03] (off)
Feb 15 12:45:29 linux-ytaf kernel: ACPI: Power Resource [FN04] (off)
Feb 15 12:45:29 linux-ytaf kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
Feb 15 12:45:29 linux-ytaf kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Feb 15 12:45:29 linux-ytaf kernel: \_SB_.PCI0:_OSC invalid UUID
Feb 15 12:45:29 linux-ytaf kernel: _OSC request data:1 1f 0 
Feb 15 12:45:29 linux-ytaf kernel: acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
Feb 15 12:45:29 linux-ytaf kernel: PCI host bridge to bus 0000:00
Feb 15 12:45:29 linux-ytaf kernel: pci_bus 0000:00: root bus resource [bus 00-3e]
Feb 15 12:45:29 linux-ytaf kernel: pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
Feb 15 12:45:29 linux-ytaf kernel: pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
Feb 15 12:45:29 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
Feb 15 12:45:29 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff window]
Feb 15 12:45:29 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff window]
Feb 15 12:45:29 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff window]
Feb 15 12:45:29 linux-ytaf kernel: pci_bus 0000:00: root bus resource [mem 0xe0000000-0xfeafffff window]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:00.0: [8086:0100] type 00 class 0x060000
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:01.0: [8086:0101] type 01 class 0x060400
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:01.0: System wakeup disabled by ACPI
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:01.1: [8086:0105] type 01 class 0x060400
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:01.1: PME# supported from D0 D3hot D3cold
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:01.1: System wakeup disabled by ACPI
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:16.0: [8086:1c3a] type 00 class 0x078000
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:16.0: reg 0x10: [mem 0xf742c000-0xf742c00f 64bit]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:19.0: [8086:1503] type 00 class 0x020000
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:19.0: reg 0x10: [mem 0xf7400000-0xf741ffff]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:19.0: reg 0x14: [mem 0xf7429000-0xf7429fff]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:19.0: reg 0x18: [io  0xf040-0xf05f]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:19.0: PME# supported from D0 D3hot D3cold
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:19.0: System wakeup disabled by ACPI
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1a.0: [8086:1c2d] type 00 class 0x0c0320
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1a.0: reg 0x10: [mem 0xf7428000-0xf74283ff]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1a.0: System wakeup disabled by ACPI
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1b.0: [8086:1c20] type 00 class 0x040300
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1b.0: reg 0x10: [mem 0xf7420000-0xf7423fff 64bit]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1b.0: System wakeup disabled by ACPI
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.0: [8086:1c10] type 01 class 0x060400
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.0: System wakeup disabled by ACPI
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.4: [8086:1c18] type 01 class 0x060400
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.4: System wakeup disabled by ACPI
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.5: [8086:1c1a] type 01 class 0x060400
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.5: System wakeup disabled by ACPI
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.6: [8086:1c1c] type 01 class 0x060400
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.6: PME# supported from D0 D3hot D3cold
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.6: System wakeup disabled by ACPI
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1d.0: [8086:1c26] type 00 class 0x0c0320
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1d.0: reg 0x10: [mem 0xf7427000-0xf74273ff]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1d.0: System wakeup disabled by ACPI
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1f.0: [8086:1c44] type 00 class 0x060100
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1f.2: [8086:1c02] type 00 class 0x010601
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x10: [io  0xf090-0xf097]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x14: [io  0xf080-0xf083]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x18: [io  0xf070-0xf077]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x1c: [io  0xf060-0xf063]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x20: [io  0xf020-0xf03f]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1f.2: reg 0x24: [mem 0xf7426000-0xf74267ff]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1f.2: PME# supported from D3hot
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1f.3: [8086:1c22] type 00 class 0x0c0500
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1f.3: reg 0x10: [mem 0xf7425000-0xf74250ff 64bit]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1f.3: reg 0x20: [io  0x0580-0x059f]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:02:00.0: [10de:1183] type 00 class 0x030000
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:02:00.0: reg 0x10: [mem 0xf6000000-0xf6ffffff]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:02:00.0: reg 0x14: [mem 0xe8000000-0xefffffff 64bit pref]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:02:00.0: reg 0x1c: [mem 0xf0000000-0xf1ffffff 64bit pref]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:02:00.0: reg 0x24: [io  0xe000-0xe07f]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:02:00.0: reg 0x30: [mem 0xf7000000-0xf707ffff pref]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:02:00.1: [10de:0e0a] type 00 class 0x040300
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:02:00.1: reg 0x10: [mem 0xf7080000-0xf7083fff]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:01.1: PCI bridge to [bus 02]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [io  0xe000-0xefff]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xf6000000-0xf70fffff]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xe8000000-0xf1ffffff 64bit pref]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.0: PCI bridge to [bus 03]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:04:00.0: [1b21:1042] type 00 class 0x0c0330
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:04:00.0: reg 0x10: [mem 0xf7300000-0xf7307fff 64bit]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:04:00.0: PME# supported from D3hot D3cold
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:04:00.0: System wakeup disabled by ACPI
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.4: PCI bridge to [bus 04]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.4:   bridge window [mem 0xf7300000-0xf73fffff]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:05:00.0: [1b21:1042] type 00 class 0x0c0330
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:05:00.0: reg 0x10: [mem 0xf7200000-0xf7207fff 64bit]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:05:00.0: PME# supported from D3hot D3cold
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:05:00.0: System wakeup disabled by ACPI
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.5: PCI bridge to [bus 05]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.5:   bridge window [mem 0xf7200000-0xf72fffff]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:06:00.0: [197b:2362] type 00 class 0x010185
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:06:00.0: reg 0x10: [io  0xd040-0xd047]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:06:00.0: reg 0x14: [io  0xd030-0xd033]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:06:00.0: reg 0x18: [io  0xd020-0xd027]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:06:00.0: reg 0x1c: [io  0xd010-0xd013]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:06:00.0: reg 0x20: [io  0xd000-0xd00f]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:06:00.0: reg 0x24: [mem 0xf7110000-0xf71101ff]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:06:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:06:00.0: PME# supported from D3hot
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:06:00.0: System wakeup disabled by ACPI
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.6: PCI bridge to [bus 06]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [io  0xd000-0xdfff]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [mem 0xf7100000-0xf71fffff]
Feb 15 12:45:29 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15)
Feb 15 12:45:29 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *10 11 12 14 15)
Feb 15 12:45:29 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Feb 15 12:45:29 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs *3 4 5 6 10 11 12 14 15)
Feb 15 12:45:29 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 *4 5 6 10 11 12 14 15)
Feb 15 12:45:29 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
Feb 15 12:45:29 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 *11 12 14 15)
Feb 15 12:45:29 linux-ytaf kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 *10 11 12 14 15)
Feb 15 12:45:29 linux-ytaf kernel: ACPI: Enabled 6 GPEs in block 00 to 3F
Feb 15 12:45:29 linux-ytaf kernel: ACPI : EC: GPE = 0x18, I/O: command/status = 0x66, data = 0x62
Feb 15 12:45:29 linux-ytaf kernel: vgaarb: setting as boot device: PCI:0000:02:00.0
Feb 15 12:45:29 linux-ytaf kernel: vgaarb: device added: PCI:0000:02:00.0,decodes=io+mem,owns=io+mem,locks=none
Feb 15 12:45:29 linux-ytaf kernel: vgaarb: loaded
Feb 15 12:45:29 linux-ytaf kernel: vgaarb: bridge control possible 0000:02:00.0
Feb 15 12:45:29 linux-ytaf kernel: SCSI subsystem initialized
Feb 15 12:45:29 linux-ytaf kernel: libata version 3.00 loaded.
Feb 15 12:45:29 linux-ytaf kernel: PCI: Using ACPI for IRQ routing
Feb 15 12:45:29 linux-ytaf kernel: PCI: pci_cache_line_size set to 64 bytes
Feb 15 12:45:29 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0009f000-0x0009ffff]
Feb 15 12:45:29 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c2f1018-0x0fffffff]
Feb 15 12:45:29 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c81c018-0x0fffffff]
Feb 15 12:45:29 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x0c82c018-0x0fffffff]
Feb 15 12:45:29 linux-ytaf kernel: e820: reserve RAM buffer [mem 0xdeb8f000-0xdfffffff]
Feb 15 12:45:29 linux-ytaf kernel: e820: reserve RAM buffer [mem 0xdf800000-0xdfffffff]
Feb 15 12:45:29 linux-ytaf kernel: e820: reserve RAM buffer [mem 0x21f000000-0x21fffffff]
Feb 15 12:45:29 linux-ytaf kernel: NetLabel: Initializing
Feb 15 12:45:29 linux-ytaf kernel: NetLabel:  domain hash size = 128
Feb 15 12:45:29 linux-ytaf kernel: NetLabel:  protocols = UNLABELED CIPSOv4
Feb 15 12:45:29 linux-ytaf kernel: NetLabel:  unlabeled traffic allowed by default
Feb 15 12:45:29 linux-ytaf kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Feb 15 12:45:29 linux-ytaf kernel: hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Feb 15 12:45:29 linux-ytaf kernel: Switched to clocksource hpet
Feb 15 12:45:29 linux-ytaf kernel: AppArmor: AppArmor Filesystem Enabled
Feb 15 12:45:29 linux-ytaf kernel: pnp: PnP ACPI init
Feb 15 12:45:29 linux-ytaf kernel: system 00:00: [mem 0xfed40000-0xfed44fff] has been reserved
Feb 15 12:45:29 linux-ytaf kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
Feb 15 12:45:29 linux-ytaf kernel: system 00:01: [io  0x0680-0x069f] has been reserved
Feb 15 12:45:29 linux-ytaf kernel: system 00:01: [io  0x0200-0x020f] has been reserved
Feb 15 12:45:29 linux-ytaf kernel: system 00:01: [io  0xffff] has been reserved
Feb 15 12:45:29 linux-ytaf kernel: system 00:01: [io  0xffff] has been reserved
Feb 15 12:45:29 linux-ytaf kernel: system 00:01: [io  0x0400-0x0453] could not be reserved
Feb 15 12:45:29 linux-ytaf kernel: system 00:01: [io  0x0458-0x047f] has been reserved
Feb 15 12:45:29 linux-ytaf kernel: system 00:01: [io  0x0500-0x057f] has been reserved
Feb 15 12:45:29 linux-ytaf kernel: system 00:01: [io  0x164e-0x164f] has been reserved
Feb 15 12:45:29 linux-ytaf kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 15 12:45:29 linux-ytaf kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Feb 15 12:45:29 linux-ytaf kernel: system 00:03: [io  0x0454-0x0457] has been reserved
Feb 15 12:45:29 linux-ytaf kernel: system 00:03: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
Feb 15 12:45:29 linux-ytaf kernel: system 00:04: [io  0x0290-0x029f] has been reserved
Feb 15 12:45:29 linux-ytaf kernel: system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 15 12:45:29 linux-ytaf kernel: system 00:05: [io  0x04d0-0x04d1] has been reserved
Feb 15 12:45:29 linux-ytaf kernel: system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 15 12:45:29 linux-ytaf kernel: system 00:06: [mem 0xfed1c000-0xfed1ffff] has been reserved
Feb 15 12:45:29 linux-ytaf kernel: system 00:06: [mem 0xfed10000-0xfed17fff] has been reserved
Feb 15 12:45:29 linux-ytaf kernel: system 00:06: [mem 0xfed18000-0xfed18fff] has been reserved
Feb 15 12:45:29 linux-ytaf kernel: system 00:06: [mem 0xfed19000-0xfed19fff] has been reserved
Feb 15 12:45:29 linux-ytaf kernel: system 00:06: [mem 0xf8000000-0xfbffffff] has been reserved
Feb 15 12:45:29 linux-ytaf kernel: system 00:06: [mem 0xfed20000-0xfed3ffff] has been reserved
Feb 15 12:45:29 linux-ytaf kernel: system 00:06: [mem 0xfed90000-0xfed93fff] has been reserved
Feb 15 12:45:29 linux-ytaf kernel: system 00:06: [mem 0xfed45000-0xfed8ffff] has been reserved
Feb 15 12:45:29 linux-ytaf kernel: system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Feb 15 12:45:29 linux-ytaf kernel: system 00:06: [mem 0xfee00000-0xfeefffff] could not be reserved
Feb 15 12:45:29 linux-ytaf kernel: system 00:06: [mem 0xe0000000-0xe0000fff] has been reserved
Feb 15 12:45:29 linux-ytaf kernel: system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 15 12:45:29 linux-ytaf kernel: pnp: PnP ACPI: found 7 devices
Feb 15 12:45:29 linux-ytaf kernel: clocksource acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.0: bridge window [io  0x1000-0x0fff] to [bus 03] add_size 1000
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 03] add_size 200000 add_align 100000
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff] to [bus 03] add_size 200000 add_align 100000
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.0: res[14]=[mem 0x00100000-0x000fffff] res_to_dev_res add_size 200000 min_align 100000
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.0: res[14]=[mem 0x00100000-0x002fffff] res_to_dev_res add_size 200000 min_align 100000
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x000fffff 64bit pref] res_to_dev_res add_size 200000 min_align 100000
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x002fffff 64bit pref] res_to_dev_res add_size 200000 min_align 100000
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.0: res[13]=[io  0x1000-0x0fff] res_to_dev_res add_size 1000 min_align 1000
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.0: res[13]=[io  0x1000-0x1fff] res_to_dev_res add_size 1000 min_align 1000
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.0: BAR 14: assigned [mem 0xe0100000-0xe02fffff]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.0: BAR 15: assigned [mem 0xe0300000-0xe04fffff 64bit pref]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.0: BAR 13: assigned [io  0x2000-0x2fff]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:01.1: PCI bridge to [bus 02]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [io  0xe000-0xefff]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xf6000000-0xf70fffff]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:01.1:   bridge window [mem 0xe8000000-0xf1ffffff 64bit pref]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.0: PCI bridge to [bus 03]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.0:   bridge window [io  0x2000-0x2fff]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.0:   bridge window [mem 0xe0100000-0xe02fffff]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.0:   bridge window [mem 0xe0300000-0xe04fffff 64bit pref]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.4: PCI bridge to [bus 04]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.4:   bridge window [mem 0xf7300000-0xf73fffff]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.5: PCI bridge to [bus 05]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.5:   bridge window [mem 0xf7200000-0xf72fffff]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:06:00.0: BAR 6: assigned [mem 0xf7100000-0xf710ffff pref]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.6: PCI bridge to [bus 06]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [io  0xd000-0xdfff]
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:00:1c.6:   bridge window [mem 0xf7100000-0xf71fffff]
Feb 15 12:45:29 linux-ytaf kernel: pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
Feb 15 12:45:29 linux-ytaf kernel: pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
Feb 15 12:45:29 linux-ytaf kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
Feb 15 12:45:29 linux-ytaf kernel: pci_bus 0000:00: resource 7 [mem 0x000d4000-0x000d7fff window]
Feb 15 12:45:29 linux-ytaf kernel: pci_bus 0000:00: resource 8 [mem 0x000d8000-0x000dbfff window]
Feb 15 12:45:29 linux-ytaf kernel: pci_bus 0000:00: resource 9 [mem 0x000dc000-0x000dffff window]
Feb 15 12:45:29 linux-ytaf kernel: pci_bus 0000:00: resource 10 [mem 0xe0000000-0xfeafffff window]
Feb 15 12:45:29 linux-ytaf kernel: pci_bus 0000:02: resource 0 [io  0xe000-0xefff]
Feb 15 12:45:29 linux-ytaf kernel: pci_bus 0000:02: resource 1 [mem 0xf6000000-0xf70fffff]
Feb 15 12:45:29 linux-ytaf kernel: pci_bus 0000:02: resource 2 [mem 0xe8000000-0xf1ffffff 64bit pref]
Feb 15 12:45:29 linux-ytaf kernel: pci_bus 0000:03: resource 0 [io  0x2000-0x2fff]
Feb 15 12:45:29 linux-ytaf kernel: pci_bus 0000:03: resource 1 [mem 0xe0100000-0xe02fffff]
Feb 15 12:45:29 linux-ytaf kernel: pci_bus 0000:03: resource 2 [mem 0xe0300000-0xe04fffff 64bit pref]
Feb 15 12:45:29 linux-ytaf kernel: pci_bus 0000:04: resource 1 [mem 0xf7300000-0xf73fffff]
Feb 15 12:45:29 linux-ytaf kernel: pci_bus 0000:05: resource 1 [mem 0xf7200000-0xf72fffff]
Feb 15 12:45:29 linux-ytaf kernel: pci_bus 0000:06: resource 0 [io  0xd000-0xdfff]
Feb 15 12:45:29 linux-ytaf kernel: pci_bus 0000:06: resource 1 [mem 0xf7100000-0xf71fffff]
Feb 15 12:45:29 linux-ytaf kernel: NET: Registered protocol family 2
Feb 15 12:45:29 linux-ytaf kernel: TCP established hash table entries: 65536 (order: 7, 524288 bytes)
Feb 15 12:45:29 linux-ytaf kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Feb 15 12:45:29 linux-ytaf kernel: TCP: Hash tables configured (established 65536 bind 65536)
Feb 15 12:45:29 linux-ytaf kernel: UDP hash table entries: 4096 (order: 5, 131072 bytes)
Feb 15 12:45:29 linux-ytaf kernel: UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
Feb 15 12:45:29 linux-ytaf kernel: NET: Registered protocol family 1
Feb 15 12:45:29 linux-ytaf kernel: pci 0000:02:00.0: Video device with shadowed ROM
Feb 15 12:45:29 linux-ytaf kernel: PCI: CLS 64 bytes, default 64
Feb 15 12:45:29 linux-ytaf kernel: Unpacking initramfs...
Feb 15 12:45:29 linux-ytaf kernel: Freeing initrd memory: 8296K (ffff8800007e1000 - ffff880000ffb000)
Feb 15 12:45:29 linux-ytaf kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Feb 15 12:45:29 linux-ytaf kernel: software IO TLB [mem 0xdab8f000-0xdeb8f000] (64MB) mapped at [ffff8800dab8f000-ffff8800deb8efff]
Feb 15 12:45:29 linux-ytaf kernel: RAPL PMU detected, API unit is 2^-32 Joules, 3 fixed counters 163840 ms ovfl timer
Feb 15 12:45:29 linux-ytaf kernel: hw unit of domain pp0-core 2^-16 Joules
Feb 15 12:45:29 linux-ytaf kernel: hw unit of domain package 2^-16 Joules
Feb 15 12:45:29 linux-ytaf kernel: hw unit of domain pp1-gpu 2^-16 Joules
Feb 15 12:45:29 linux-ytaf kernel: microcode: CPU0 sig=0x206a7, pf=0x2, revision=0x29
Feb 15 12:45:29 linux-ytaf kernel: microcode: CPU1 sig=0x206a7, pf=0x2, revision=0x29
Feb 15 12:45:29 linux-ytaf kernel: microcode: CPU2 sig=0x206a7, pf=0x2, revision=0x29
Feb 15 12:45:29 linux-ytaf kernel: microcode: CPU3 sig=0x206a7, pf=0x2, revision=0x29
Feb 15 12:45:29 linux-ytaf kernel: microcode: CPU4 sig=0x206a7, pf=0x2, revision=0x29
Feb 15 12:45:29 linux-ytaf kernel: microcode: CPU5 sig=0x206a7, pf=0x2, revision=0x29
Feb 15 12:45:29 linux-ytaf kernel: microcode: CPU6 sig=0x206a7, pf=0x2, revision=0x29
Feb 15 12:45:29 linux-ytaf kernel: microcode: CPU7 sig=0x206a7, pf=0x2, revision=0x29
Feb 15 12:45:29 linux-ytaf kernel: microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Feb 15 12:45:29 linux-ytaf kernel: Scanning for low memory corruption every 60 seconds
Feb 15 12:45:29 linux-ytaf kernel: futex hash table entries: 2048 (order: 5, 131072 bytes)
Feb 15 12:45:29 linux-ytaf kernel: audit: initializing netlink subsys (disabled)
Feb 15 12:45:29 linux-ytaf kernel: audit: type=2000 audit(1455540327.000:1): initialized
Feb 15 12:45:29 linux-ytaf kernel: HugeTLB registered 2 MB page size, pre-allocated 0 pages
Feb 15 12:45:29 linux-ytaf kernel: zpool: loaded
Feb 15 12:45:29 linux-ytaf kernel: zbud: loaded
Feb 15 12:45:29 linux-ytaf kernel: VFS: Disk quotas dquot_6.6.0
Feb 15 12:45:29 linux-ytaf kernel: VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Feb 15 12:45:29 linux-ytaf kernel: Key type big_key registered
Feb 15 12:45:29 linux-ytaf kernel: Key type asymmetric registered
Feb 15 12:45:29 linux-ytaf kernel: Asymmetric key parser 'x509' registered
Feb 15 12:45:29 linux-ytaf kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Feb 15 12:45:29 linux-ytaf kernel: io scheduler noop registered
Feb 15 12:45:29 linux-ytaf kernel: io scheduler deadline registered
Feb 15 12:45:29 linux-ytaf kernel: io scheduler cfq registered (default)
Feb 15 12:45:29 linux-ytaf kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Feb 15 12:45:29 linux-ytaf kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Feb 15 12:45:29 linux-ytaf kernel: efifb: probing for efifb
Feb 15 12:45:29 linux-ytaf kernel: efifb: framebuffer at 0xf1000000, mapped to 0xffffc90001000000, using 1876k, total 1875k
Feb 15 12:45:29 linux-ytaf kernel: efifb: mode is 800x600x32, linelength=3200, pages=1
Feb 15 12:45:29 linux-ytaf kernel: efifb: scrolling: redraw
Feb 15 12:45:29 linux-ytaf kernel: efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Feb 15 12:45:29 linux-ytaf kernel: Console: switching to colour frame buffer device 100x37
Feb 15 12:45:29 linux-ytaf kernel: fb0: EFI VGA frame buffer device
Feb 15 12:45:29 linux-ytaf kernel: intel_idle: MWAIT substates: 0x1120
Feb 15 12:45:29 linux-ytaf kernel: intel_idle: v0.4 model 0x2A
Feb 15 12:45:29 linux-ytaf kernel: intel_idle: lapic_timer_reliable_states 0xffffffff
Feb 15 12:45:29 linux-ytaf kernel: GHES: HEST is not enabled!
Feb 15 12:45:29 linux-ytaf kernel: Serial: 8250/16550 driver, 32 ports, IRQ sharing disabled
Feb 15 12:45:29 linux-ytaf kernel: Non-volatile memory driver v1.3
Feb 15 12:45:29 linux-ytaf kernel: Linux agpgart interface v0.103
Feb 15 12:45:29 linux-ytaf kernel: ahci 0000:00:1f.2: version 3.0
Feb 15 12:45:29 linux-ytaf kernel: ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x7 impl SATA mode
Feb 15 12:45:29 linux-ytaf kernel: ahci 0000:00:1f.2: flags: 64bit ncq led clo pio slum part ems apst 
Feb 15 12:45:29 linux-ytaf kernel: scsi host0: ahci
Feb 15 12:45:29 linux-ytaf kernel: scsi host1: ahci
Feb 15 12:45:29 linux-ytaf kernel: scsi host2: ahci
Feb 15 12:45:29 linux-ytaf kernel: scsi host3: ahci
Feb 15 12:45:29 linux-ytaf kernel: scsi host4: ahci
Feb 15 12:45:29 linux-ytaf kernel: scsi host5: ahci
Feb 15 12:45:29 linux-ytaf kernel: ata1: SATA max UDMA/133 abar m2048@0xf7426000 port 0xf7426100 irq 26
Feb 15 12:45:29 linux-ytaf kernel: ata2: SATA max UDMA/133 abar m2048@0xf7426000 port 0xf7426180 irq 26
Feb 15 12:45:29 linux-ytaf kernel: ata3: SATA max UDMA/133 abar m2048@0xf7426000 port 0xf7426200 irq 26
Feb 15 12:45:29 linux-ytaf kernel: ata4: DUMMY
Feb 15 12:45:29 linux-ytaf kernel: ata5: DUMMY
Feb 15 12:45:29 linux-ytaf kernel: ata6: DUMMY
Feb 15 12:45:29 linux-ytaf kernel: ahci 0000:06:00.0: AHCI 0001.0100 32 slots 2 ports 3 Gbps 0x3 impl SATA mode
Feb 15 12:45:29 linux-ytaf kernel: ahci 0000:06:00.0: flags: 64bit ncq pm led clo pmp pio slum part 
Feb 15 12:45:29 linux-ytaf kernel: scsi host6: ahci
Feb 15 12:45:29 linux-ytaf kernel: scsi host7: ahci
Feb 15 12:45:29 linux-ytaf kernel: ata7: SATA max UDMA/133 abar m512@0xf7110000 port 0xf7110100 irq 18
Feb 15 12:45:29 linux-ytaf kernel: ata8: SATA max UDMA/133 abar m512@0xf7110000 port 0xf7110180 irq 18
Feb 15 12:45:29 linux-ytaf kernel: i8042: PNP: No PS/2 controller found. Probing ports directly.
Feb 15 12:45:29 linux-ytaf kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Feb 15 12:45:29 linux-ytaf kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Feb 15 12:45:29 linux-ytaf kernel: mousedev: PS/2 mouse device common for all mice
Feb 15 12:45:29 linux-ytaf kernel: rtc_cmos 00:02: RTC can wake from S4
Feb 15 12:45:29 linux-ytaf kernel: rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Feb 15 12:45:29 linux-ytaf kernel: rtc_cmos 00:02: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
Feb 15 12:45:29 linux-ytaf kernel: Intel P-state driver initializing.
Feb 15 12:45:29 linux-ytaf kernel: ledtrig-cpu: registered to indicate activity on CPUs
Feb 15 12:45:29 linux-ytaf kernel: EFI Variables Facility v0.08 2004-May-17
Feb 15 12:45:29 linux-ytaf kernel: hidraw: raw HID events driver (C) Jiri Kosina
Feb 15 12:45:29 linux-ytaf kernel: NET: Registered protocol family 10
Feb 15 12:45:29 linux-ytaf kernel: registered taskstats version 1
Feb 15 12:45:29 linux-ytaf kernel: Key type encrypted registered
Feb 15 12:45:29 linux-ytaf kernel: AppArmor: AppArmor sha1 policy hashing enabled
Feb 15 12:45:29 linux-ytaf kernel:   Magic number: 4:609:784
Feb 15 12:45:29 linux-ytaf kernel: rtc_cmos 00:02: setting system clock to 2016-02-15 12:45:27 UTC (1455540327)
Feb 15 12:45:29 linux-ytaf kernel: PM: Checking hibernation image partition /dev/sdb2
Feb 15 12:45:29 linux-ytaf kernel: ata7: SATA link down (SStatus 0 SControl 300)
Feb 15 12:45:29 linux-ytaf kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 15 12:45:29 linux-ytaf kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Feb 15 12:45:29 linux-ytaf kernel: ata8: SATA link down (SStatus 0 SControl 300)
Feb 15 12:45:29 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 15 12:45:29 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff8802160b7dd8), AE_NOT_FOUND (20150410/psparse-536)
Feb 15 12:45:29 linux-ytaf kernel: ata2.00: ATA-8: TOSHIBA HDWD110, MS2OA8J0, max UDMA/133
Feb 15 12:45:29 linux-ytaf kernel: ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Feb 15 12:45:29 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 15 12:45:29 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff8802160b7dd8), AE_NOT_FOUND (20150410/psparse-536)
Feb 15 12:45:29 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 15 12:45:29 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff8802160b7d60), AE_NOT_FOUND (20150410/psparse-536)
Feb 15 12:45:29 linux-ytaf kernel: ata3.00: ATAPI: TSSTcorp CDDVDW SH-S223C, SB05, max UDMA/66
Feb 15 12:45:29 linux-ytaf kernel: ata3.00: applying bridge limits
Feb 15 12:45:29 linux-ytaf kernel: ata2.00: configured for UDMA/133
Feb 15 12:45:29 linux-ytaf kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 15 12:45:29 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 15 12:45:29 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff8802160b7e50), AE_NOT_FOUND (20150410/psparse-536)
Feb 15 12:45:29 linux-ytaf kernel: ata1.00: ATA-9: SAMSUNG SSD 830 Series, CXM03B1Q, max UDMA/133
Feb 15 12:45:29 linux-ytaf kernel: ata1.00: 500118192 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Feb 15 12:45:29 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 15 12:45:29 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff8802160b7e50), AE_NOT_FOUND (20150410/psparse-536)
Feb 15 12:45:29 linux-ytaf kernel: ata1.00: configured for UDMA/133
Feb 15 12:45:29 linux-ytaf kernel: scsi 0:0:0:0: Direct-Access     ATA      SAMSUNG SSD 830  3B1Q PQ: 0 ANSI: 5
Feb 15 12:45:29 linux-ytaf kernel: sd 0:0:0:0: [sda] 500118192 512-byte logical blocks: (256 GB/238 GiB)
Feb 15 12:45:29 linux-ytaf kernel: sd 0:0:0:0: [sda] Write Protect is off
Feb 15 12:45:29 linux-ytaf kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 15 12:45:29 linux-ytaf kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 15 12:45:29 linux-ytaf kernel: scsi 1:0:0:0: Direct-Access     ATA      TOSHIBA HDWD110  A8J0 PQ: 0 ANSI: 5
Feb 15 12:45:29 linux-ytaf kernel: sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
Feb 15 12:45:29 linux-ytaf kernel: sd 1:0:0:0: [sdb] 4096-byte physical blocks
Feb 15 12:45:29 linux-ytaf kernel: sd 1:0:0:0: [sdb] Write Protect is off
Feb 15 12:45:29 linux-ytaf kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Feb 15 12:45:29 linux-ytaf kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 15 12:45:29 linux-ytaf kernel:  sda: sda1 sda2 sda3 sda4
Feb 15 12:45:29 linux-ytaf kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Feb 15 12:45:29 linux-ytaf kernel:  sdb: sdb1 sdb2 sdb3 sdb4
Feb 15 12:45:29 linux-ytaf kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
Feb 15 12:45:29 linux-ytaf kernel: tsc: Refined TSC clocksource calibration: 3411.127 MHz
Feb 15 12:45:29 linux-ytaf kernel: clocksource tsc: mask: 0xffffffffffffffff max_cycles: 0x312b5e33c4e, max_idle_ns: 440795327319 ns
Feb 15 12:45:29 linux-ytaf kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
Feb 15 12:45:29 linux-ytaf kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node ffff8802160b7d60), AE_NOT_FOUND (20150410/psparse-536)
Feb 15 12:45:29 linux-ytaf kernel: ata3.00: configured for UDMA/66
Feb 15 12:45:29 linux-ytaf kernel: scsi 2:0:0:0: CD-ROM            TSSTcorp CDDVDW SH-S223C  SB05 PQ: 0 ANSI: 5
Feb 15 12:45:29 linux-ytaf kernel: PM: Hibernation image partition 8:18 present
Feb 15 12:45:29 linux-ytaf kernel: PM: Looking for hibernation image.
Feb 15 12:45:29 linux-ytaf kernel: Switched to clocksource tsc
Feb 15 12:45:29 linux-ytaf kernel: PM: Image not found (code -22)
Feb 15 12:45:29 linux-ytaf kernel: PM: Hibernation image not present or could not be loaded.
Feb 15 12:45:29 linux-ytaf kernel: Freeing unused kernel memory: 1560K (ffffffff81f11000 - ffffffff82097000)
Feb 15 12:45:29 linux-ytaf kernel: Write protecting the kernel read-only data: 14336k
Feb 15 12:45:29 linux-ytaf kernel: Freeing unused kernel memory: 1632K (ffff88000d668000 - ffff88000d800000)
Feb 15 12:45:29 linux-ytaf kernel: Freeing unused kernel memory: 1296K (ffff88000dcbc000 - ffff88000de00000)
Feb 15 12:45:29 linux-ytaf systemd[1]: RTC configured in localtime, applying delta of 60 minutes to system time.
Feb 15 12:45:29 linux-ytaf kernel: random: systemd urandom read with 22 bits of entropy available
Feb 15 12:45:29 linux-ytaf kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Feb 15 12:45:29 linux-ytaf kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0
Feb 15 12:45:29 linux-ytaf kernel: scsi 2:0:0:0: Attached scsi generic sg2 type 5
Feb 15 12:45:29 linux-ytaf systemd-journal[187]: Journal started
Feb 15 12:45:29 linux-ytaf dracut-cmdline[181]: dracut-42.1 dracut-037-68.1
Feb 15 12:45:29 linux-ytaf systemd-udevd[251]: Network interface NamePolicy= disabled on kernel commandline, ignoring.
Feb 15 12:45:29 linux-ytaf kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3
Feb 15 12:45:29 linux-ytaf kernel: ACPI: Power Button [PWRB]
Feb 15 12:45:29 linux-ytaf kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
Feb 15 12:45:29 linux-ytaf kernel: ACPI: Power Button [PWRF]
Feb 15 12:45:29 linux-ytaf kernel: wmi: Mapper loaded
Feb 15 12:45:29 linux-ytaf kernel: ACPI: bus type USB registered
Feb 15 12:45:29 linux-ytaf kernel: usbcore: registered new interface driver usbfs
Feb 15 12:45:29 linux-ytaf kernel: usbcore: registered new interface driver hub
Feb 15 12:45:29 linux-ytaf kernel: usbcore: registered new device driver usb
Feb 15 12:45:29 linux-ytaf kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Feb 15 12:45:29 linux-ytaf kernel: ehci-pci: EHCI PCI platform driver
Feb 15 12:45:29 linux-ytaf kernel: ehci-pci 0000:00:1a.0: EHCI Host Controller
Feb 15 12:45:29 linux-ytaf kernel: ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Feb 15 12:45:29 linux-ytaf kernel: ehci-pci 0000:00:1a.0: debug port 2
Feb 15 12:45:29 linux-ytaf kernel: ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Feb 15 12:45:29 linux-ytaf kernel: ehci-pci 0000:00:1a.0: irq 16, io mem 0xf7428000
Feb 15 12:45:29 linux-ytaf kernel: sr 2:0:0:0: [sr0] scsi3-mmc drive: 52x/52x writer dvd-ram cd/rw xa/form2 cdda tray
Feb 15 12:45:29 linux-ytaf kernel: cdrom: Uniform CD-ROM driver Revision: 3.20
Feb 15 12:45:29 linux-ytaf kernel: sr 2:0:0:0: Attached scsi CD-ROM sr0
Feb 15 12:45:29 linux-ytaf kernel: ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Feb 15 12:45:29 linux-ytaf kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Feb 15 12:45:29 linux-ytaf kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 15 12:45:29 linux-ytaf kernel: usb usb1: Product: EHCI Host Controller
Feb 15 12:45:29 linux-ytaf kernel: usb usb1: Manufacturer: Linux 4.1.15-8-default ehci_hcd
Feb 15 12:45:29 linux-ytaf kernel: usb usb1: SerialNumber: 0000:00:1a.0
Feb 15 12:45:29 linux-ytaf kernel: hub 1-0:1.0: USB hub found
Feb 15 12:45:29 linux-ytaf kernel: hub 1-0:1.0: 2 ports detected
Feb 15 12:45:29 linux-ytaf kernel: xhci_hcd 0000:04:00.0: xHCI Host Controller
Feb 15 12:45:29 linux-ytaf kernel: xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 2
Feb 15 12:45:29 linux-ytaf kernel: xhci_hcd 0000:04:00.0: hcc params 0x0200f180 hci version 0x96 quirks 0x00080000
Feb 15 12:45:29 linux-ytaf kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Feb 15 12:45:29 linux-ytaf kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 15 12:45:29 linux-ytaf kernel: usb usb2: Product: xHCI Host Controller
Feb 15 12:45:29 linux-ytaf kernel: usb usb2: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 15 12:45:29 linux-ytaf kernel: usb usb2: SerialNumber: 0000:04:00.0
Feb 15 12:45:29 linux-ytaf kernel: hub 2-0:1.0: USB hub found
Feb 15 12:45:29 linux-ytaf kernel: hub 2-0:1.0: 2 ports detected
Feb 15 12:45:29 linux-ytaf kernel: xhci_hcd 0000:04:00.0: xHCI Host Controller
Feb 15 12:45:29 linux-ytaf kernel: xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 3
Feb 15 12:45:29 linux-ytaf kernel: ehci-pci 0000:00:1d.0: EHCI Host Controller
Feb 15 12:45:29 linux-ytaf kernel: ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 4
Feb 15 12:45:29 linux-ytaf kernel: ehci-pci 0000:00:1d.0: debug port 2
Feb 15 12:45:29 linux-ytaf kernel: usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
Feb 15 12:45:29 linux-ytaf kernel: usb usb3: New USB device found, idVendor=1d6b, idProduct=0003
Feb 15 12:45:29 linux-ytaf kernel: usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 15 12:45:29 linux-ytaf kernel: usb usb3: Product: xHCI Host Controller
Feb 15 12:45:29 linux-ytaf kernel: usb usb3: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 15 12:45:29 linux-ytaf kernel: usb usb3: SerialNumber: 0000:04:00.0
Feb 15 12:45:29 linux-ytaf kernel: hub 3-0:1.0: USB hub found
Feb 15 12:45:29 linux-ytaf kernel: hub 3-0:1.0: 2 ports detected
Feb 15 12:45:29 linux-ytaf kernel: ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Feb 15 12:45:29 linux-ytaf kernel: ehci-pci 0000:00:1d.0: irq 23, io mem 0xf7427000
Feb 15 12:45:29 linux-ytaf kernel: ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Feb 15 12:45:29 linux-ytaf kernel: usb usb4: New USB device found, idVendor=1d6b, idProduct=0002
Feb 15 12:45:29 linux-ytaf kernel: usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 15 12:45:29 linux-ytaf kernel: usb usb4: Product: EHCI Host Controller
Feb 15 12:45:29 linux-ytaf kernel: usb usb4: Manufacturer: Linux 4.1.15-8-default ehci_hcd
Feb 15 12:45:29 linux-ytaf kernel: usb usb4: SerialNumber: 0000:00:1d.0
Feb 15 12:45:29 linux-ytaf kernel: hub 4-0:1.0: USB hub found
Feb 15 12:45:29 linux-ytaf kernel: hub 4-0:1.0: 2 ports detected
Feb 15 12:45:29 linux-ytaf kernel: xhci_hcd 0000:05:00.0: xHCI Host Controller
Feb 15 12:45:29 linux-ytaf kernel: xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 5
Feb 15 12:45:29 linux-ytaf kernel: xhci_hcd 0000:05:00.0: hcc params 0x0200f180 hci version 0x96 quirks 0x00080000
Feb 15 12:45:29 linux-ytaf kernel: usb usb5: New USB device found, idVendor=1d6b, idProduct=0002
Feb 15 12:45:29 linux-ytaf kernel: usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 15 12:45:29 linux-ytaf kernel: usb usb5: Product: xHCI Host Controller
Feb 15 12:45:29 linux-ytaf kernel: usb usb5: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 15 12:45:29 linux-ytaf kernel: usb usb5: SerialNumber: 0000:05:00.0
Feb 15 12:45:29 linux-ytaf kernel: hub 5-0:1.0: USB hub found
Feb 15 12:45:29 linux-ytaf kernel: hub 5-0:1.0: 2 ports detected
Feb 15 12:45:29 linux-ytaf kernel: xhci_hcd 0000:05:00.0: xHCI Host Controller
Feb 15 12:45:29 linux-ytaf kernel: xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 6
Feb 15 12:45:29 linux-ytaf kernel: usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
Feb 15 12:45:29 linux-ytaf kernel: usb usb6: New USB device found, idVendor=1d6b, idProduct=0003
Feb 15 12:45:29 linux-ytaf kernel: usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 15 12:45:29 linux-ytaf kernel: usb usb6: Product: xHCI Host Controller
Feb 15 12:45:29 linux-ytaf kernel: usb usb6: Manufacturer: Linux 4.1.15-8-default xhci-hcd
Feb 15 12:45:29 linux-ytaf kernel: usb usb6: SerialNumber: 0000:05:00.0
Feb 15 12:45:29 linux-ytaf kernel: hub 6-0:1.0: USB hub found
Feb 15 12:45:29 linux-ytaf kernel: hub 6-0:1.0: 2 ports detected
Feb 15 12:45:29 linux-ytaf kernel: raid6: sse2x1   gen() 11240 MB/s
Feb 15 12:45:29 linux-ytaf kernel: usb 1-1: new high-speed USB device number 2 using ehci-pci
Feb 15 12:45:29 linux-ytaf kernel: raid6: sse2x1   xor()  9007 MB/s
Feb 15 12:45:29 linux-ytaf kernel: raid6: sse2x2   gen() 14097 MB/s
Feb 15 12:45:30 linux-ytaf kernel: usb 4-1: new high-speed USB device number 2 using ehci-pci
Feb 15 12:45:30 linux-ytaf kernel: raid6: sse2x2   xor() 10038 MB/s
Feb 15 12:45:30 linux-ytaf kernel: usb 1-1: New USB device found, idVendor=8087, idProduct=0024
Feb 15 12:45:30 linux-ytaf kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb 15 12:45:30 linux-ytaf kernel: hub 1-1:1.0: USB hub found
Feb 15 12:45:30 linux-ytaf kernel: hub 1-1:1.0: 6 ports detected
Feb 15 12:45:30 linux-ytaf kernel: usb 5-1: new high-speed USB device number 2 using xhci_hcd
Feb 15 12:45:30 linux-ytaf kernel: raid6: sse2x4   gen() 16266 MB/s
Feb 15 12:45:30 linux-ytaf kernel: raid6: sse2x4   xor() 12105 MB/s
Feb 15 12:45:30 linux-ytaf kernel: raid6: using algorithm sse2x4 gen() 16266 MB/s
Feb 15 12:45:30 linux-ytaf kernel: raid6: .... xor() 12105 MB/s, rmw enabled
Feb 15 12:45:30 linux-ytaf kernel: raid6: using ssse3x2 recovery algorithm
Feb 15 12:45:30 linux-ytaf kernel: xor: automatically using best checksumming function:
Feb 15 12:45:30 linux-ytaf kernel: usb 4-1: New USB device found, idVendor=8087, idProduct=0024
Feb 15 12:45:30 linux-ytaf kernel: usb 4-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb 15 12:45:30 linux-ytaf kernel: hub 4-1:1.0: USB hub found
Feb 15 12:45:30 linux-ytaf kernel: hub 4-1:1.0: 8 ports detected
Feb 15 12:45:30 linux-ytaf kernel:    avx       : 31208.000 MB/sec
Feb 15 12:45:30 linux-ytaf kernel: Btrfs loaded, assert=on
Feb 15 12:45:30 linux-ytaf kernel: BTRFS: device fsid 21024970-7a27-4114-8525-d8dd026f23b6 devid 1 transid 1200 /dev/sdb3
Feb 15 12:45:30 linux-ytaf kernel: usb 5-1: New USB device found, idVendor=03f0, idProduct=5d12
Feb 15 12:45:30 linux-ytaf kernel: usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 15 12:45:30 linux-ytaf kernel: usb 5-1: Product: Officejet 6600
Feb 15 12:45:30 linux-ytaf kernel: usb 5-1: Manufacturer: HP
Feb 15 12:45:30 linux-ytaf kernel: usb 5-1: SerialNumber: CN4849R23505RN
Feb 15 12:45:30 linux-ytaf kernel: usb 1-1.5: new full-speed USB device number 3 using ehci-pci
Feb 15 12:45:30 linux-ytaf kernel: usb 4-1.1: new full-speed USB device number 3 using ehci-pci
Feb 15 12:45:30 linux-ytaf kernel: usb 5-2: new high-speed USB device number 3 using xhci_hcd
Feb 15 12:45:30 linux-ytaf kernel: usb 1-1.5: New USB device found, idVendor=06a3, idProduct=0ccb
Feb 15 12:45:30 linux-ytaf kernel: usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 15 12:45:30 linux-ytaf kernel: usb 1-1.5: Product: Cyborg R.A.T.7 Mouse
Feb 15 12:45:30 linux-ytaf kernel: usb 1-1.5: Manufacturer: Saitek
Feb 15 12:45:30 linux-ytaf kernel: usbcore: registered new interface driver usbhid
Feb 15 12:45:30 linux-ytaf kernel: usbhid: USB HID core driver
Feb 15 12:45:30 linux-ytaf kernel: usb 4-1.1: New USB device found, idVendor=1532, idProduct=0109
Feb 15 12:45:30 linux-ytaf kernel: usb 4-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 15 12:45:30 linux-ytaf kernel: usb 4-1.1: Product: Razer Lycosa
Feb 15 12:45:30 linux-ytaf kernel: usb 4-1.1: Manufacturer: Razer
Feb 15 12:45:30 linux-ytaf kernel: input: Razer Razer Lycosa as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1:1.0/0003:1532:0109.0002/input/input5
Feb 15 12:45:30 linux-ytaf kernel: hid-generic 0003:1532:0109.0002: input,hidraw0: USB HID v1.10 Keyboard [Razer Razer Lycosa] on usb-0000:00:1d.0-1.1/input0
Feb 15 12:45:30 linux-ytaf kernel: input: Razer Razer Lycosa as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1:1.1/0003:1532:0109.0003/input/input6
Feb 15 12:45:30 linux-ytaf kernel: usb 5-2: New USB device found, idVendor=0930, idProduct=6545
Feb 15 12:45:30 linux-ytaf kernel: usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 15 12:45:30 linux-ytaf kernel: usb 5-2: Product: TransMemory
Feb 15 12:45:30 linux-ytaf kernel: usb 5-2: Manufacturer: TOSHIBA
Feb 15 12:45:30 linux-ytaf kernel: usb 5-2: SerialNumber: C89CDCBF6D59EF4140000065
Feb 15 12:45:30 linux-ytaf kernel: usb-storage 5-2:1.0: USB Mass Storage device detected
Feb 15 12:45:30 linux-ytaf kernel: scsi host8: usb-storage 5-2:1.0
Feb 15 12:45:30 linux-ytaf kernel: usbcore: registered new interface driver usb-storage
Feb 15 12:45:30 linux-ytaf kernel: usbcore: registered new interface driver uas
Feb 15 12:45:30 linux-ytaf kernel: hid-generic 0003:1532:0109.0003: input,hidraw1: USB HID v1.10 Device [Razer Razer Lycosa] on usb-0000:00:1d.0-1.1/input1
Feb 15 12:45:31 linux-ytaf kernel: PM: Starting manual resume from disk
Feb 15 12:45:31 linux-ytaf kernel: PM: Hibernation image partition 8:18 present
Feb 15 12:45:31 linux-ytaf kernel: PM: Looking for hibernation image.
Feb 15 12:45:31 linux-ytaf kernel: PM: Image not found (code -22)
Feb 15 12:45:31 linux-ytaf kernel: PM: Hibernation image not present or could not be loaded.
Feb 15 12:45:31 linux-ytaf kernel: BTRFS info (device sdb3): disk space caching is enabled
Feb 15 12:45:31 linux-ytaf kernel: BTRFS: has skinny extents
Feb 15 12:45:31 linux-ytaf kernel: scsi 8:0:0:0: Direct-Access     TOSHIBA  TransMemory      PMAP PQ: 0 ANSI: 6
Feb 15 12:45:31 linux-ytaf kernel: sd 8:0:0:0: Attached scsi generic sg3 type 0
Feb 15 12:45:31 linux-ytaf kernel: sd 8:0:0:0: [sdc] 30228480 512-byte logical blocks: (15.4 GB/14.4 GiB)
Feb 15 12:45:31 linux-ytaf kernel: sd 8:0:0:0: [sdc] Write Protect is off
Feb 15 12:45:31 linux-ytaf kernel: sd 8:0:0:0: [sdc] Mode Sense: 45 00 00 00
Feb 15 12:45:31 linux-ytaf kernel: sd 8:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Feb 15 12:45:31 linux-ytaf kernel:  sdc: sdc1
Feb 15 12:45:31 linux-ytaf kernel: sd 8:0:0:0: [sdc] Attached SCSI removable disk
Feb 15 12:45:31 linux-ytaf kernel: random: nonblocking pool is initialized
Feb 15 12:45:32 linux-ytaf systemd-journal[187]: Journal stopped
Feb 15 12:45:34 linux-ytaf systemd-journal[480]: Runtime journal is using 8.0M (max allowed 397.5M, trying to leave 596.3M free of 3.8G available → current limit 397.5M).
Feb 15 12:45:34 linux-ytaf systemd-journal[480]: Runtime journal is using 8.0M (max allowed 397.5M, trying to leave 596.3M free of 3.8G available → current limit 397.5M).
Feb 15 12:45:34 linux-ytaf systemd[1]: RTC configured in localtime, applying delta of 60 minutes to system time.
Feb 15 12:45:34 linux-ytaf systemd-journal[480]: Journal started
Feb 15 12:45:33 linux-ytaf systemd[1]: Failed to configure loopback device: Permission denied
Feb 15 12:45:34 linux-ytaf kernel: BTRFS info (device sdb3): disk space caching is enabled
Feb 15 12:45:34 linux-ytaf systemd-udevd[500]: Network interface NamePolicy= disabled on kernel commandline, ignoring.
Feb 15 12:45:34 linux-ytaf systemd-udevd[500]: invalid key/value pair in file /usr/lib/udev/rules.d/51-android.rules on line 115,starting at character 57 ('')
Feb 15 12:45:35 linux-ytaf kernel: thermal LNXTHERM:00: registered as thermal_zone0
Feb 15 12:45:35 linux-ytaf kernel: ACPI: Thermal Zone [TZ00] (28 C)
Feb 15 12:45:35 linux-ytaf kernel: thermal LNXTHERM:01: registered as thermal_zone1
Feb 15 12:45:35 linux-ytaf kernel: ACPI: Thermal Zone [TZ01] (30 C)
Feb 15 12:45:35 linux-ytaf kernel: input: PC Speaker as /devices/platform/pcspkr/input/input7
Feb 15 12:45:35 linux-ytaf kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Feb 15 12:45:35 linux-ytaf kernel: pps_core: LinuxPPS API ver. 1 registered
Feb 15 12:45:35 linux-ytaf kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
Feb 15 12:45:35 linux-ytaf mtp-probe[627]: checking bus 5, device 3: "/sys/devices/pci0000:00/0000:00:1c.5/0000:05:00.0/usb5/5-2"
Feb 15 12:45:35 linux-ytaf mtp-probe[620]: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5"
Feb 15 12:45:35 linux-ytaf mtp-probe[619]: checking bus 4, device 3: "/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1"
Feb 15 12:45:35 linux-ytaf mtp-probe[627]: bus: 5, device: 3 was not an MTP device
Feb 15 12:45:35 linux-ytaf mtp-probe[620]: bus: 1, device: 3 was not an MTP device
Feb 15 12:45:35 linux-ytaf mtp-probe[619]: bus: 4, device: 3 was not an MTP device
Feb 15 12:45:35 linux-ytaf kernel: AVX version of gcm_enc/dec engaged.
Feb 15 12:45:35 linux-ytaf kernel: AES CTR mode by8 optimization enabled
Feb 15 12:45:35 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000580-0x000000000000059F conflicts with OpRegion 0x0000000000000580-0x000000000000058F (\_SB_.PCI0.SBUS.SMBI) (20150410/utaddress-254)
Feb 15 12:45:35 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000580-0x000000000000059F conflicts with OpRegion 0x0000000000000580-0x000000000000059F (\_SB_.PCI0.SMB_.SMIO) (20150410/utaddress-254)
Feb 15 12:45:35 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 15 12:45:35 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20150410/utaddress-254)
Feb 15 12:45:35 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 15 12:45:35 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150410/utaddress-254)
Feb 15 12:45:35 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150410/utaddress-254)
Feb 15 12:45:35 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 15 12:45:35 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150410/utaddress-254)
Feb 15 12:45:35 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150410/utaddress-254)
Feb 15 12:45:35 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 15 12:45:35 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150410/utaddress-254)
Feb 15 12:45:35 linux-ytaf kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150410/utaddress-254)
Feb 15 12:45:35 linux-ytaf kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 15 12:45:35 linux-ytaf kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
Feb 15 12:45:35 linux-ytaf kernel: PTP clock support registered
Feb 15 12:45:35 linux-ytaf kernel: [drm] Initialized drm 1.1.0 20060810
Feb 15 12:45:35 linux-ytaf kernel: input: Saitek Cyborg R.A.T.7 Mouse as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0/0003:06A3:0CCB.0001/input/input8
Feb 15 12:45:35 linux-ytaf kernel: saitek 0003:06A3:0CCB.0001: input,hidraw2: USB HID v1.11 Mouse [Saitek Cyborg R.A.T.7 Mouse] on usb-0000:00:1a.0-1.5/input0
Feb 15 12:45:36 linux-ytaf kernel: e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
Feb 15 12:45:36 linux-ytaf kernel: e1000e: Copyright(c) 1999 - 2014 Intel Corporation.
Feb 15 12:45:36 linux-ytaf kernel: e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
Feb 15 12:45:36 linux-ytaf kernel: nvidia: module license 'NVIDIA' taints kernel.
Feb 15 12:45:36 linux-ytaf kernel: Disabling lock debugging due to kernel taint
Feb 15 12:45:36 linux-ytaf kernel: vgaarb: device changed decodes: PCI:0000:02:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
Feb 15 12:45:36 linux-ytaf kernel: [drm] Initialized nvidia-drm 0.0.0 20150116 for 0000:02:00.0 on minor 0
Feb 15 12:45:36 linux-ytaf kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  352.79  Wed Jan 13 16:17:53 PST 2016
Feb 15 12:45:36 linux-ytaf kernel: nvidia_uvm: Loaded the UVM driver, major device number 247
Feb 15 12:45:36 linux-ytaf logger[626]: loading HP Device 005 002
Feb 15 12:45:36 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: registered PHC clock
Feb 15 12:45:36 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) c8:60:00:09:38:76
Feb 15 12:45:36 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
Feb 15 12:45:36 linux-ytaf kernel: e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: FFFFFF-0FF
Feb 15 12:45:37 linux-ytaf kernel: iTCO_vendor_support: vendor-support=0
Feb 15 12:45:37 linux-ytaf kernel: iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
Feb 15 12:45:37 linux-ytaf kernel: iTCO_wdt: Found a Cougar Point TCO device (Version=2, TCOBASE=0x0460)
Feb 15 12:45:37 linux-ytaf kernel: iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
Feb 15 12:45:38 linux-ytaf kernel: asus_wmi: ASUS WMI generic driver loaded
Feb 15 12:45:38 linux-ytaf kernel: asus_wmi: Initialization: 0x0
Feb 15 12:45:38 linux-ytaf kernel: asus_wmi: BIOS WMI version: 0.9
Feb 15 12:45:38 linux-ytaf kernel: asus_wmi: SFUN value: 0x0
Feb 15 12:45:38 linux-ytaf kernel: input: Eee PC WMI hotkeys as /devices/platform/eeepc-wmi/input/input9
Feb 15 12:45:38 linux-ytaf kernel: asus_wmi: Disabling ACPI video driver
Feb 15 12:45:38 linux-ytaf kernel: snd_hda_intel 0000:00:1b.0: enabling device (0000 -> 0002)
Feb 15 12:45:38 linux-ytaf kernel: snd_hda_intel 0000:02:00.1: enabling device (0000 -> 0002)
Feb 15 12:45:38 linux-ytaf kernel: snd_hda_intel 0000:02:00.1: Disabling MSI
Feb 15 12:45:38 linux-ytaf kernel: snd_hda_intel 0000:02:00.1: Handle VGA-switcheroo audio client
Feb 15 12:45:39 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC889: line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line
Feb 15 12:45:39 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Feb 15 12:45:39 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
Feb 15 12:45:39 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
Feb 15 12:45:39 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    dig-out=0x11/0x1e
Feb 15 12:45:39 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:    inputs:
Feb 15 12:45:39 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:      Front Mic=0x19
Feb 15 12:45:39 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:      Rear Mic=0x18
Feb 15 12:45:39 linux-ytaf kernel: snd_hda_codec_realtek hdaudioC0D0:      Line=0x1a
Feb 15 12:45:39 linux-ytaf kernel: input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
Feb 15 12:45:39 linux-ytaf kernel: input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
Feb 15 12:45:39 linux-ytaf kernel: input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
Feb 15 12:45:39 linux-ytaf kernel: input: HDA Intel PCH Line Out Front as /devices/pci0000:00/0000:00:1b.0/sound/card0/input13
Feb 15 12:45:39 linux-ytaf kernel: input: HDA Intel PCH Line Out Surround as /devices/pci0000:00/0000:00:1b.0/sound/card0/input14
Feb 15 12:45:39 linux-ytaf kernel: input: HDA Intel PCH Line Out CLFE as /devices/pci0000:00/0000:00:1b.0/sound/card0/input15
Feb 15 12:45:39 linux-ytaf kernel: input: HDA Intel PCH Line Out Side as /devices/pci0000:00/0000:00:1b.0/sound/card0/input16
Feb 15 12:45:39 linux-ytaf kernel: Adding 2104316k swap on /dev/sdb2.  Priority:-1 extents:1 across:2104316k FS
Feb 15 12:45:39 linux-ytaf kernel: FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Feb 15 12:45:39 linux-ytaf systemd-fsck[716]: /sbin/fsck.xfs: XFS file system.
Feb 15 12:45:39 linux-ytaf kernel: SGI XFS with ACLs, security attributes, realtime, no debug enabled
Feb 15 12:45:39 linux-ytaf kernel: XFS (sdb4): Mounting V5 Filesystem
Feb 15 12:45:39 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input17
Feb 15 12:45:39 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input18
Feb 15 12:45:39 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input19
Feb 15 12:45:39 linux-ytaf kernel: input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.1/0000:02:00.1/sound/card1/input20
Feb 15 12:45:40 linux-ytaf python[692]: io/hpmud/musb.c 2179: [692] hpmud_make_usb_uri() bus=005 dev=002
Feb 15 12:45:40 linux-ytaf python[692]: io/hpmud/musb.c 2276: hpmud_make_usb_uri() uri=hp:/usb/Officejet_6600?serial=CN4849R23505RN bytes_read=44
Feb 15 12:45:40 linux-ytaf kernel: usblp 5-1:1.1: usblp0: USB Bidirectional printer dev 2 if 1 alt 0 proto 2 vid 0x03F0 pid 0x5D12
Feb 15 12:45:40 linux-ytaf kernel: usblp 5-1:1.2: usblp1: USB Bidirectional printer dev 2 if 2 alt 0 proto 2 vid 0x03F0 pid 0x5D12
Feb 15 12:45:40 linux-ytaf kernel: usbcore: registered new interface driver usblp
Feb 15 12:45:41 linux-ytaf kernel: XFS (sdb4): Starting recovery (logdev: internal)
Feb 15 12:45:42 linux-ytaf kernel: XFS (sdb4): Ending recovery (logdev: internal)
Feb 15 12:45:42 linux-ytaf systemd-journal[480]: Permanent journal is using 96.0M (max allowed 4.0G, trying to leave 4.0G free of 30.8G available → current limit 4.0G).
Feb 15 12:45:43 linux-ytaf systemd-journal[480]: Time spent on flushing to /var is 344.663ms for 948 entries.
Feb 15 12:45:44 linux-ytaf kernel: audit: type=1305 audit(1455536742.419:2): audit_pid=848 old=0 auid=4294967295 ses=4294967295 res=1
Feb 15 12:45:42 linux-ytaf auditd[848]: Started dispatcher: /sbin/audispd pid: 857
Feb 15 12:45:42 linux-ytaf audispd[857]: priority_boost_parser called with: 4
Feb 15 12:45:42 linux-ytaf audispd[857]: max_restarts_parser called with: 10
Feb 15 12:45:42 linux-ytaf audispd[857]: No plugins found, exiting
Feb 15 12:45:42 linux-ytaf auditd[848]: Init complete, auditd 2.3.6 listening for events (startup state enable)
Feb 15 12:45:44 linux-ytaf auditctl[849]: No rules
Feb 15 12:45:44 linux-ytaf auditctl[849]: AUDIT_STATUS: enabled=0 flag=1 pid=0 rate_limit=0 backlog_limit=320 lost=0 backlog=0
Feb 15 12:45:44 linux-ytaf boot.apparmor[862]: Starting AppArmor ..done
Feb 15 12:45:45 linux-ytaf dbus-daemon[1029]: Unknown username "srvGeoClue" in message bus configuration file
Feb 15 12:45:45 linux-ytaf avahi-daemon[1030]: Found user 'avahi' (UID 486) and group 'avahi' (GID 485).
Feb 15 12:45:45 linux-ytaf avahi-daemon[1030]: Successfully dropped root privileges.
Feb 15 12:45:45 linux-ytaf avahi-daemon[1030]: avahi-daemon 0.6.31 starting up.
Feb 15 12:45:45 linux-ytaf avahi-daemon[1030]: Loading service file /etc/avahi/services/sftp-ssh.service.
Feb 15 12:45:45 linux-ytaf avahi-daemon[1030]: Loading service file /etc/avahi/services/ssh.service.
Feb 15 12:45:45 linux-ytaf avahi-daemon[1030]: Network interface enumeration completed.
Feb 15 12:45:45 linux-ytaf avahi-daemon[1030]: Registering HINFO record with values 'X86_64'/'LINUX'.
Feb 15 12:45:45 linux-ytaf avahi-daemon[1030]: Server startup complete. Host name is linux-ytaf.local. Local service cookie is 674995437.
Feb 15 12:45:45 linux-ytaf avahi-daemon[1030]: Service "linux-ytaf" (/etc/avahi/services/ssh.service) successfully established.
Feb 15 12:45:45 linux-ytaf avahi-daemon[1030]: Service "linux-ytaf" (/etc/avahi/services/sftp-ssh.service) successfully established.
Feb 15 12:45:45 linux-ytaf smartd[1036]: smartd 6.2 2013-11-07 r3856 [x86_64-linux-4.1.15-8-default] (SUSE RPM)
Feb 15 12:45:45 linux-ytaf smartd[1036]: Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
Feb 15 12:45:45 linux-ytaf smartd[1036]: Opened configuration file /etc/smartd.conf
Feb 15 12:45:45 linux-ytaf smartd[1036]: Drive: DEVICESCAN, implied '-a' Directive on line 26 of file /etc/smartd.conf
Feb 15 12:45:45 linux-ytaf smartd[1036]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
Feb 15 12:45:45 linux-ytaf smartd[1036]: Device: /dev/sda, type changed from 'scsi' to 'sat'
Feb 15 12:45:45 linux-ytaf smartd[1036]: Device: /dev/sda [SAT], opened
Feb 15 12:45:45 linux-ytaf smartd[1036]: Device: /dev/sda [SAT], SAMSUNG SSD 830 Series, S/N:S0Z4NEAC906195, WWN:5-002538-043584d30, FW:CXM03B1Q, 256 GB
Feb 15 12:45:45 linux-ytaf smartd[1036]: Device: /dev/sda [SAT], found in smartd database: Samsung based SSDs
Feb 15 12:45:45 linux-ytaf smartd[1036]: Device: /dev/sda [SAT], can't monitor Current_Pending_Sector count - no Attribute 197
Feb 15 12:45:45 linux-ytaf smartd[1036]: Device: /dev/sda [SAT], can't monitor Offline_Uncorrectable count - no Attribute 198
Feb 15 12:45:45 linux-ytaf smartd[1036]: Device: /dev/sda [SAT], is SMART capable. Adding to "monitor" list.
Feb 15 12:45:45 linux-ytaf smartd[1036]: Device: /dev/sda [SAT], state read from /var/lib/smartmontools/smartd.SAMSUNG_SSD_830_Series-S0Z4NEAC906195.ata.state
Feb 15 12:45:45 linux-ytaf display-manager[1059]: /etc/vconsole.conf available
Feb 15 12:45:45 linux-ytaf display-manager[1059]: KEYMAP: de-latin1-nodeadkeys
Feb 15 12:45:45 linux-ytaf display-manager[1059]: Command: localectl set-keymap de-latin1-nodeadkeys
Feb 15 12:45:45 linux-ytaf display-manager[1059]: I: Using systemd /usr/share/systemd/kbd-model-map mapping
Feb 15 12:45:45 linux-ytaf dbus[1029]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service'
Feb 15 12:45:45 linux-ytaf smartd[1036]: Device: /dev/sdb, type changed from 'scsi' to 'sat'
Feb 15 12:45:45 linux-ytaf smartd[1036]: Device: /dev/sdb [SAT], opened
Feb 15 12:45:45 linux-ytaf dbus[1029]: [system] Successfully activated service 'org.freedesktop.locale1'
Feb 15 12:45:45 linux-ytaf smartd[1036]: Device: /dev/sdb [SAT], TOSHIBA HDWD110, S/N:Y5GDEMGFS, WWN:5-000039-fe7c5a79c, FW:MS2OA8J0, 1.00 TB
Feb 15 12:45:45 linux-ytaf smartd[1036]: Device: /dev/sdb [SAT], not found in smartd database.
Feb 15 12:45:45 linux-ytaf ModemManager[1032]: <info>  ModemManager (version 1.4.10) starting in system bus...
Feb 15 12:45:45 linux-ytaf dbus[1029]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Feb 15 12:45:46 linux-ytaf polkitd[1088]: Started polkitd version 0.113
Feb 15 12:45:46 linux-ytaf kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
Feb 15 12:45:46 linux-ytaf polkitd[1088]: Loading rules from directory /etc/polkit-1/rules.d
Feb 15 12:45:47 linux-ytaf smartd[1036]: Device: /dev/sdb [SAT], is SMART capable. Adding to "monitor" list.
Feb 15 12:45:47 linux-ytaf polkitd[1088]: Loading rules from directory /usr/share/polkit-1/rules.d
Feb 15 12:45:47 linux-ytaf smartd[1036]: Device: /dev/sdb [SAT], state read from /var/lib/smartmontools/smartd.TOSHIBA_HDWD110-Y5GDEMGFS.ata.state
Feb 15 12:45:47 linux-ytaf smartd[1036]: Monitoring 2 ATA and 0 SCSI devices
Feb 15 12:45:47 linux-ytaf smartd[1036]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 77 to 78
Feb 15 12:45:47 linux-ytaf smartd[1036]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 240 to 253
Feb 15 12:45:48 linux-ytaf kernel: nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
Feb 15 12:45:48 linux-ytaf polkitd[1088]: Finished loading, compiling and executing 3 rules
Feb 15 12:45:48 linux-ytaf dbus[1029]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Feb 15 12:45:48 linux-ytaf polkitd[1088]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
Feb 15 12:45:48 linux-ytaf smartd[1036]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.SAMSUNG_SSD_830_Series-S0Z4NEAC906195.ata.state
Feb 15 12:45:48 linux-ytaf smartd[1036]: Device: /dev/sdb [SAT], state written to /var/lib/smartmontools/smartd.TOSHIBA_HDWD110-Y5GDEMGFS.ata.state
Feb 15 12:45:48 linux-ytaf kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Feb 15 12:45:48 linux-ytaf SuSEfirewall2[1146]: Firewall rules set to CLOSE.
Feb 15 12:45:48 linux-ytaf kernel: No iBFT detected.
Feb 15 12:45:49 linux-ytaf logger[1094]: /etc/init.d/xdm: No changes for /etc/X11/xdm/Xservers
Feb 15 12:45:49 linux-ytaf logger[1094]: /etc/init.d/xdm: No changes for /etc/X11/xdm/xdm-config
Feb 15 12:45:49 linux-ytaf sddm[1259]: Adding new display on vt 7 ...
Feb 15 12:45:49 linux-ytaf sddm[1259]: Display server starting...
Feb 15 12:45:49 linux-ytaf sddm[1259]: Running: /usr/bin/X -nolisten tcp -auth /run/sddm/{2627b447-d62c-4925-b775-cf33f7e483cd} -background none -noreset -displayfd 17 vt7
Feb 15 12:45:49 linux-ytaf display-manager[1059]: Starting service sddm..done
Feb 15 12:45:50 linux-ytaf ModemManager[1032]: <info>  Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin
Feb 15 12:45:51 linux-ytaf kernel: NVRM: Your system is not currently configured to drive a VGA console
Feb 15 12:45:51 linux-ytaf kernel: NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
Feb 15 12:45:51 linux-ytaf kernel: NVRM: requires the use of a text-mode VGA console. Use of other console
Feb 15 12:45:51 linux-ytaf kernel: NVRM: drivers including, but not limited to, vesafb, may result in
Feb 15 12:45:51 linux-ytaf kernel: NVRM: corruption and stability problems, and is not supported.
Feb 15 12:45:51 linux-ytaf kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Feb 15 12:45:51 linux-ytaf wickedd-dhcp4[1149]: eth0: Request to acquire DHCPv4 lease with UUID 6dbac156-47ca-0200-7f04-000004000000
Feb 15 12:45:52 linux-ytaf sddm[1259]: Socket server started.
Feb 15 12:45:52 linux-ytaf sddm[1259]: Greeter starting...
Feb 15 12:45:52 linux-ytaf sddm[1259]: Adding cookie to "/run/sddm/{2627b447-d62c-4925-b775-cf33f7e483cd}"
Feb 15 12:45:52 linux-ytaf sddm-helper[1321]: [PAM] Starting...
Feb 15 12:45:52 linux-ytaf sddm-helper[1321]: [PAM] Authenticating...
Feb 15 12:45:52 linux-ytaf sddm-helper[1321]: [PAM] returning.
Feb 15 12:45:52 linux-ytaf sddm-helper[1321]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
Feb 15 12:45:52 linux-ytaf systemd[1323]: pam_unix(systemd-user:session): session opened for user sddm by (uid=0)
Feb 15 12:45:52 linux-ytaf kernel: NET: Registered protocol family 17
Feb 15 12:45:52 linux-ytaf sddm[1259]: Message received from greeter: Connect
Feb 15 12:45:54 linux-ytaf dbus[1029]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
Feb 15 12:45:54 linux-ytaf udisksd[1335]: udisks daemon version 2.1.6 starting
Feb 15 12:45:55 linux-ytaf dbus[1029]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Feb 15 12:45:55 linux-ytaf udisksd[1335]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Feb 15 12:45:55 linux-ytaf dbus[1029]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
Feb 15 12:45:55 linux-ytaf dbus[1029]: [system] Successfully activated service 'org.freedesktop.UPower'
Feb 15 12:45:56 linux-ytaf wickedd-dhcp4[1149]: eth0: Committed DHCPv4 lease with address 192.168.178.12 (lease time 864000 sec, renew in 432000 sec, rebind in 756000 sec)
Feb 15 12:45:56 linux-ytaf avahi-daemon[1030]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.178.12.
Feb 15 12:45:56 linux-ytaf avahi-daemon[1030]: New relevant interface eth0.IPv4 for mDNS.
Feb 15 12:45:56 linux-ytaf avahi-daemon[1030]: Registering new address record for 192.168.178.12 on eth0.IPv4.
Feb 15 12:45:56 linux-ytaf wickedd[1151]: eth0: Notified neighbours about IP address 192.168.178.12
Feb 15 12:45:57 MM-Home wicked[1153]: lo              up
Feb 15 12:45:57 MM-Home wicked[1153]: eth0            up
Feb 15 12:45:57 MM-Home echo[1550]: Starting mail service (Postfix)
Feb 15 12:45:57 MM-Home iscsiadm[1551]: iscsiadm: No records found
Feb 15 12:45:57 MM-Home SuSEfirewall2[1580]: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Feb 15 12:45:57 MM-Home SuSEfirewall2[1586]: using default zone 'ext' for interface eth0
Feb 15 12:45:57 MM-Home ntpd[1569]: ntpd 4.2.8p4@1.3265-o Thu Dec 17 05:32:52 UTC 2015 (1): Starting
Feb 15 12:45:57 MM-Home ntpd[1569]: Command line: /usr/sbin/ntpd -p /var/run/ntp/ntpd.pid -g -u ntp:ntp -c /etc/ntp.conf
Feb 15 12:45:57 MM-Home sntp[1653]: sntp 4.2.8p4@1.3265-o Thu Dec 17 05:32:29 UTC 2015 (1)
Feb 15 12:45:57 MM-Home sntp[1653]: kod_init_kod_db(): Cannot open KoD db file /var/db/ntp-kod: No such file or directory
Feb 15 12:45:57 MM-Home start-ntpd[1556]: Starting network time protocol daemon (NTPD)sntp 4.2.8p4@1.3265-o Thu Dec 17 05:32:29 UTC 2015 (1)
Feb 15 12:45:57 MM-Home start-ntpd[1556]: kod_init_kod_db(): Cannot open KoD db file /var/db/ntp-kod: No such file or directory
Feb 15 12:45:57 MM-Home ntpd[1652]: proto: precision = 0.095 usec (-23)
Feb 15 12:45:57 MM-Home sntp[1653]: 2016-02-15 12:45:57.545083 (-0100) -0.65884 +/- 0.484377 192.168.178.1 s3 no-leap
Feb 15 12:45:56 MM-Home start-ntpd[1556]: 2016-02-15 12:45:57.545083 (-0100) -0.65884 +/- 0.484377 192.168.178.1 s3 no-leap
Feb 15 12:45:56 MM-Home ntpd[1652]: switching logging to file /var/log/ntp
Feb 15 12:45:56 MM-Home /usr/sbin/start-ntpd[1658]: runtime configuration: server 192.168.178.1
Feb 15 12:45:56 MM-Home start-ntpd[1556]: /usr/sbin/ntpq: read: Connection refused
Feb 15 12:45:57 MM-Home SuSEfirewall2[1703]: Firewall rules successfully set
Feb 15 12:45:57 MM-Home postfix/postfix-script[1752]: starting the Postfix mail system
Feb 15 12:45:57 MM-Home postfix/master[1754]: daemon started -- version 2.11.6, configuration /etc/postfix
Feb 15 12:45:57 MM-Home cron[1771]: (CRON) INFO (RANDOM_DELAY will be scaled with factor 35% if used.)
Feb 15 12:45:57 MM-Home cron[1771]: (CRON) INFO (running with inotify support)
Feb 15 12:47:19 MM-Home sddm[1259]: Message received from greeter: Login
Feb 15 12:47:19 MM-Home sddm[1259]: Reading from "/usr/share/xsessions/plasma5.desktop"
Feb 15 12:47:19 MM-Home sddm-helper[1788]: [PAM] Starting...
Feb 15 12:47:19 MM-Home sddm-helper[1788]: [PAM] Authenticating...
Feb 15 12:47:19 MM-Home sddm-helper[1788]: [PAM] Preparing to converse...
Feb 15 12:47:19 MM-Home sddm-helper[1788]: [PAM] Conversation with 1 messages
Feb 15 12:47:19 MM-Home sddm-helper[1788]: [PAM] returning.
Feb 15 12:47:19 MM-Home sddm[1259]: Authenticated successfully
Feb 15 12:47:19 MM-Home sddm-helper[1788]: pam_unix(sddm:session): session opened for user marc by (uid=0)
Feb 15 12:47:19 MM-Home systemd[1789]: pam_unix(systemd-user:session): session opened for user marc by (uid=0)
Feb 15 12:47:20 MM-Home sddm-helper[1791]: Adding cookie to "/home/marc/.Xauthority"
Feb 15 12:47:20 MM-Home sddm[1259]: Auth: sddm-helper exited successfully
Feb 15 12:47:20 MM-Home sddm[1259]: Greeter stopped.
Feb 15 12:47:20 MM-Home sddm[1259]: Session started
Feb 15 12:47:22 MM-Home dbus[1029]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Feb 15 12:47:22 MM-Home org.kde.powerdevil.backlighthelper[1029]: powerdevil: no kernel backlight interface found
Feb 15 12:47:22 MM-Home dbus[1029]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Feb 15 12:47:22 MM-Home kernel: QSGRenderThread[1881]: segfault at 98 ip 00007fb4384f18f5 sp 00007fb418d12710 error 4 in libnvidia-glcore.so.352.79[7fb436e33000+19fe000]
Feb 15 12:47:23 MM-Home polkitd[1088]: Registered Authentication Agent for unix-session:2 (system bus name :1.38 [/usr/lib64/libexec/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale de_DE.UTF-8)
Feb 15 12:47:23 MM-Home dbus[1029]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service'
Feb 15 12:47:23 MM-Home dbus[1029]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Feb 15 12:47:23 MM-Home rtkit-daemon[1954]: Successfully called chroot.
Feb 15 12:47:23 MM-Home rtkit-daemon[1954]: Successfully dropped privileges.
Feb 15 12:47:23 MM-Home rtkit-daemon[1954]: Successfully limited resources.
Feb 15 12:47:23 MM-Home rtkit-daemon[1954]: Running.
Feb 15 12:47:23 MM-Home rtkit-daemon[1954]: Canary thread running.
Feb 15 12:47:23 MM-Home rtkit-daemon[1954]: Watchdog thread running.
Feb 15 12:47:23 MM-Home rtkit-daemon[1954]: Successfully made thread 1953 of process 1953 (/usr/bin/pulseaudio) owned by 'marc' high priority at nice level -11.
Feb 15 12:47:23 MM-Home rtkit-daemon[1954]: Supervising 1 threads of 1 processes of 1 users.
Feb 15 12:47:27 MM-Home rtkit-daemon[1954]: Supervising 1 threads of 1 processes of 1 users.
Feb 15 12:47:27 MM-Home rtkit-daemon[1954]: Successfully made thread 2011 of process 1953 (/usr/bin/pulseaudio) owned by 'marc' RT at priority 5.
Feb 15 12:47:27 MM-Home rtkit-daemon[1954]: Supervising 2 threads of 1 processes of 1 users.
Feb 15 12:47:27 MM-Home kernel: fuse init (API version 7.23)
Feb 15 12:47:28 MM-Home rtkit-daemon[1954]: Supervising 2 threads of 1 processes of 1 users.
Feb 15 12:47:28 MM-Home rtkit-daemon[1954]: Successfully made thread 2068 of process 1953 (/usr/bin/pulseaudio) owned by 'marc' RT at priority 5.
Feb 15 12:47:28 MM-Home rtkit-daemon[1954]: Supervising 3 threads of 1 processes of 1 users.
Feb 15 12:47:28 MM-Home rtkit-daemon[1954]: Supervising 3 threads of 1 processes of 1 users.
Feb 15 12:47:28 MM-Home rtkit-daemon[1954]: Successfully made thread 2069 of process 1953 (/usr/bin/pulseaudio) owned by 'marc' RT at priority 5.
Feb 15 12:47:28 MM-Home rtkit-daemon[1954]: Supervising 4 threads of 1 processes of 1 users.
Feb 15 12:47:28 MM-Home dbus[1029]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Feb 15 12:47:28 MM-Home bluetoothd[2070]: Bluetooth daemon 5.35
Feb 15 12:47:28 MM-Home dbus[1029]: [system] Successfully activated service 'org.bluez'
Feb 15 12:47:28 MM-Home bluetoothd[2070]: Starting SDP server
Feb 15 12:47:28 MM-Home dbus[1029]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Feb 15 12:47:28 MM-Home bluetoothd[2070]: Bluetooth management interface 1.9 initialized
Feb 15 12:47:28 MM-Home kernel: Bluetooth: Core ver 2.20
Feb 15 12:47:28 MM-Home kernel: NET: Registered protocol family 31
Feb 15 12:47:28 MM-Home kernel: Bluetooth: HCI device and connection manager initialized
Feb 15 12:47:28 MM-Home kernel: Bluetooth: HCI socket layer initialized
Feb 15 12:47:28 MM-Home kernel: Bluetooth: L2CAP socket layer initialized
Feb 15 12:47:28 MM-Home kernel: Bluetooth: SCO socket layer initialized
Feb 15 12:47:28 MM-Home kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Feb 15 12:47:28 MM-Home kernel: Bluetooth: BNEP filters: protocol multicast
Feb 15 12:47:28 MM-Home kernel: Bluetooth: BNEP socket layer initialized
Feb 15 12:47:28 MM-Home dbus[1029]: [system] Successfully activated service 'org.freedesktop.hostname1'
Feb 15 12:47:28 MM-Home rtkit-daemon[1954]: Successfully made thread 2077 of process 2077 (/usr/bin/pulseaudio) owned by 'marc' high priority at nice level -11.
Feb 15 12:47:28 MM-Home rtkit-daemon[1954]: Supervising 5 threads of 2 processes of 1 users.
Feb 15 12:47:28 MM-Home pulseaudio[2077]: [pulseaudio] pid.c: Daemon already running.
Feb 15 12:47:29 MM-Home dbus[1029]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service'
Feb 15 12:47:29 MM-Home PackageKit[2107]: daemon start
Feb 15 12:47:30 MM-Home dbus[1029]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Feb 15 12:47:31 MM-Home PackageKit[2107]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 15 12:47:31 MM-Home PackageKit[2107]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 15 12:47:31 MM-Home PackageKit[2107]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 15 12:47:31 MM-Home PackageKit[2107]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 15 12:47:38 MM-Home PackageKit[2107]: refresh-cache transaction /1_addaaabe from uid 1000 finished with success after 7306ms
Feb 15 12:47:38 MM-Home PackageKit[2107]: refresh-cache transaction /2_bcbdacad from uid 1000 finished with success after 20ms
Feb 15 12:47:39 MM-Home PackageKit[2107]: get-updates transaction /3_abcebdea from uid 1000 finished with success after 870ms
Feb 15 12:47:55 MM-Home PackageKit[2107]: daemon quit
Feb 15 12:47:55 MM-Home packagekitd[2107]: (packagekitd:2107): GLib-CRITICAL **: Source ID 6 was not found when attempting to remove it
Feb 15 12:48:44 MM-Home kernel: nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
Feb 15 12:54:42 MM-Home org.kde.kiod5[1840]: org.kde.kio.kpasswdserver: User = "marc" , WindowId = 0
Feb 15 12:54:42 MM-Home org.kde.kiod5[1840]: The kwalletd service has been registered
Feb 15 12:54:42 MM-Home org.kde.kwalletd5[1840]: kwalletd5 started
Feb 15 12:54:42 MM-Home org.kde.kiod5[1840]: org.kde.kio.kpasswdserver: User = "marc" , WindowId = 0
Feb 15 12:54:42 MM-Home org.kde.kwalletd5[1840]: Migration agent starting...
Feb 15 12:54:42 MM-Home org.kde.kwalletd5[1840]: old wallets were already migrated
Feb 15 12:54:42 MM-Home org.kde.kwalletd5[1840]: Migration agent stop.
Feb 15 12:56:19 MM-Home org.kde.kuiserver[1840]: kuiserver: adding job contact for address:  ":1.18"  objectPath:  "/DataEngine/applicationjobs/JobView_1"
Feb 15 12:56:19 MM-Home org.kde.kuiserver[1840]: kuiserver: making async call of terminate for:  "/DataEngine/applicationjobs/JobView_1"
Feb 15 12:56:19 MM-Home org.kde.kuiserver[1840]: kuiserver: removing jobview from list, it finished
Feb 15 12:57:04 MM-Home org.kde.kuiserver[1840]: kuiserver: adding job contact for address:  ":1.18"  objectPath:  "/DataEngine/applicationjobs/JobView_2"
Feb 15 12:57:04 MM-Home org.kde.kiod5[1840]: org.kde.kio.kpasswdserver: User = "marc" , WindowId = 23068676
Feb 15 12:57:31 MM-Home org.kde.kuiserver[1840]: kuiserver: making async call of terminate for:  "/DataEngine/applicationjobs/JobView_2"
Feb 15 12:57:31 MM-Home org.kde.kuiserver[1840]: kuiserver: removing jobview from list, it finished
Feb 15 12:57:42 MM-Home org.kde.kuiserver[1840]: kuiserver: adding job contact for address:  ":1.18"  objectPath:  "/DataEngine/applicationjobs/JobView_3"
Feb 15 12:57:42 MM-Home org.kde.kuiserver[1840]: kuiserver: making async call of terminate for:  "/DataEngine/applicationjobs/JobView_3"
Feb 15 12:57:42 MM-Home org.kde.kuiserver[1840]: kuiserver: removing jobview from list, it finished
Feb 15 12:57:42 MM-Home org.kde.kuiserver[1840]: kuiserver: making async call of terminate for:  "/DataEngine/applicationjobs/JobView_3"
Feb 15 12:57:42 MM-Home org.kde.kuiserver[1840]: kuiserver: removing jobview from list, it finished
Feb 15 12:57:42 MM-Home org.kde.kuiserver[1840]: kuiserver: making async call of terminate for:  "/DataEngine/applicationjobs/JobView_2"
Feb 15 12:57:42 MM-Home org.kde.kuiserver[1840]: kuiserver: removing jobview from list, it finished
Feb 15 12:58:33 MM-Home org.kde.kuiserver[1840]: kuiserver: adding job contact for address:  ":1.18"  objectPath:  "/DataEngine/applicationjobs/JobView_4"
Feb 15 12:58:33 MM-Home org.kde.kuiserver[1840]: kuiserver: making async call of terminate for:  "/DataEngine/applicationjobs/JobView_4"
Feb 15 12:58:33 MM-Home org.kde.kuiserver[1840]: kuiserver: removing jobview from list, it finished
Feb 15 12:58:48 MM-Home org.kde.kuiserver[1840]: kuiserver: adding job contact for address:  ":1.18"  objectPath:  "/DataEngine/applicationjobs/JobView_5"
Feb 15 12:58:49 MM-Home org.kde.kuiserver[1840]: kuiserver: making async call of terminate for:  "/DataEngine/applicationjobs/JobView_5"
Feb 15 12:58:49 MM-Home org.kde.kuiserver[1840]: kuiserver: removing jobview from list, it finished
Feb 15 12:59:14 MM-Home org.kde.kuiserver[1840]: kuiserver: adding job contact for address:  ":1.18"  objectPath:  "/DataEngine/applicationjobs/JobView_6"
Feb 15 12:59:14 MM-Home org.kde.kuiserver[1840]: kuiserver: making async call of terminate for:  "/DataEngine/applicationjobs/JobView_6"
Feb 15 12:59:14 MM-Home org.kde.kuiserver[1840]: kuiserver: removing jobview from list, it finished
Feb 15 13:00:01 MM-Home cron[2436]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 15 13:00:01 MM-Home systemd[2437]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 15 13:00:01 MM-Home CRON[2436]: pam_unix(crond:session): session closed for user root
Feb 15 13:00:01 MM-Home systemd[2438]: pam_unix(systemd-user:session): session closed for user root
Feb 15 13:05:33 MM-Home org.kde.kuiserver[1840]: kuiserver: adding job contact for address:  ":1.18"  objectPath:  "/DataEngine/applicationjobs/JobView_7"
Feb 15 13:05:33 MM-Home org.kde.kuiserver[1840]: kuiserver: making async call of terminate for:  "/DataEngine/applicationjobs/JobView_7"
Feb 15 13:05:33 MM-Home org.kde.kuiserver[1840]: kuiserver: removing jobview from list, it finished
Feb 15 13:07:52 MM-Home org.kde.kuiserver[1840]: kuiserver: adding job contact for address:  ":1.18"  objectPath:  "/DataEngine/applicationjobs/JobView_8"
Feb 15 13:07:52 MM-Home org.kde.kuiserver[1840]: kuiserver: making async call of terminate for:  "/DataEngine/applicationjobs/JobView_8"
Feb 15 13:07:52 MM-Home org.kde.kuiserver[1840]: kuiserver: removing jobview from list, it finished
Feb 15 13:15:01 MM-Home cron[2546]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 15 13:15:01 MM-Home systemd[2547]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 15 13:15:01 MM-Home CRON[2546]: pam_unix(crond:session): session closed for user root
Feb 15 13:15:01 MM-Home systemd[2548]: pam_unix(systemd-user:session): session closed for user root
Feb 15 13:15:48 MM-Home smartd[1036]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 78 to 77
Feb 15 13:15:49 MM-Home smartd[1036]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 253 to 230
Feb 15 13:15:54 MM-Home org.kde.kuiserver[1840]: kuiserver: making async call of terminate for:  "/DataEngine/applicationjobs/JobView_8"
Feb 15 13:15:54 MM-Home org.kde.kuiserver[1840]: kuiserver: removing jobview from list, it finished
Feb 15 13:15:54 MM-Home org.kde.kuiserver[1840]: kuiserver: making async call of terminate for:  "/DataEngine/applicationjobs/JobView_7"
Feb 15 13:15:54 MM-Home org.kde.kuiserver[1840]: kuiserver: removing jobview from list, it finished
Feb 15 13:15:54 MM-Home org.kde.kuiserver[1840]: kuiserver: making async call of terminate for:  "/DataEngine/applicationjobs/JobView_6"
Feb 15 13:15:54 MM-Home org.kde.kuiserver[1840]: kuiserver: removing jobview from list, it finished
Feb 15 13:15:54 MM-Home org.kde.kuiserver[1840]: kuiserver: making async call of terminate for:  "/DataEngine/applicationjobs/JobView_5"
Feb 15 13:15:54 MM-Home org.kde.kuiserver[1840]: kuiserver: removing jobview from list, it finished
Feb 15 13:15:54 MM-Home org.kde.kuiserver[1840]: kuiserver: making async call of terminate for:  "/DataEngine/applicationjobs/JobView_4"
Feb 15 13:15:54 MM-Home org.kde.kuiserver[1840]: kuiserver: removing jobview from list, it finished
Feb 15 13:15:54 MM-Home org.kde.kuiserver[1840]: kuiserver: making async call of terminate for:  "/DataEngine/applicationjobs/JobView_1"
Feb 15 13:15:54 MM-Home org.kde.kuiserver[1840]: kuiserver: removing jobview from list, it finished
Feb 15 13:30:01 MM-Home cron[4476]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 15 13:30:01 MM-Home systemd[4477]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 15 13:30:01 MM-Home CRON[4476]: pam_unix(crond:session): session closed for user root
Feb 15 13:30:01 MM-Home systemd[4478]: pam_unix(systemd-user:session): session closed for user root
Feb 15 13:45:01 MM-Home cron[4553]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 15 13:45:01 MM-Home systemd[4554]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 15 13:45:01 MM-Home CRON[4553]: pam_unix(crond:session): session closed for user root
Feb 15 13:45:01 MM-Home systemd[4555]: pam_unix(systemd-user:session): session closed for user root
Feb 15 13:45:48 MM-Home smartd[1036]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 77 to 76
Feb 15 13:47:30 MM-Home dbus[1029]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service'
Feb 15 13:47:30 MM-Home PackageKit[4602]: daemon start
Feb 15 13:47:30 MM-Home dbus[1029]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Feb 15 13:47:30 MM-Home PackageKit[4602]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 15 13:47:30 MM-Home PackageKit[4602]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 15 13:47:30 MM-Home PackageKit[4602]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 15 13:47:30 MM-Home PackageKit[4602]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 15 13:47:31 MM-Home PackageKit[4602]: refresh-cache transaction /1_ebbcacaa from uid 1000 finished with success after 921ms
Feb 15 13:47:31 MM-Home PackageKit[4602]: refresh-cache transaction /2_aaabeeea from uid 1000 finished with success after 21ms
Feb 15 13:47:32 MM-Home PackageKit[4602]: get-updates transaction /3_bbccaebc from uid 1000 finished with success after 940ms
Feb 15 13:47:50 MM-Home PackageKit[4602]: daemon quit
Feb 15 13:47:50 MM-Home packagekitd[4602]: (packagekitd:4602): GLib-CRITICAL **: Source ID 6 was not found when attempting to remove it
Feb 15 14:00:01 MM-Home cron[4640]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 15 14:00:01 MM-Home systemd[4641]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 15 14:00:02 MM-Home CRON[4640]: pam_unix(crond:session): session closed for user root
Feb 15 14:00:02 MM-Home systemd[4642]: pam_unix(systemd-user:session): session closed for user root
Feb 15 14:15:01 MM-Home cron[4708]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 15 14:15:01 MM-Home systemd[4709]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 15 14:15:01 MM-Home CRON[4708]: pam_unix(crond:session): session closed for user root
Feb 15 14:15:01 MM-Home systemd[4710]: pam_unix(systemd-user:session): session closed for user root
Feb 15 14:30:01 MM-Home cron[4843]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 15 14:30:01 MM-Home systemd[4844]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 15 14:30:01 MM-Home CRON[4843]: pam_unix(crond:session): session closed for user root
Feb 15 14:30:01 MM-Home systemd[4845]: pam_unix(systemd-user:session): session closed for user root
Feb 15 14:30:57 MM-Home polkitd[1088]: Operator of unix-session:2 FAILED to authenticate to gain authorization for action org.freedesktop.udisks2.filesystem-mount-system for system-bus-name::1.66 [/usr/bin/dolphin] (owned by unix-user:marc)
Feb 15 14:31:07 MM-Home polkitd[1088]: Operator of unix-session:2 successfully authenticated as unix-user:root to gain TEMPORARY authorization for action org.freedesktop.udisks2.filesystem-mount-system for system-bus-name::1.66 [/usr/bin/dolphin] (owned by unix-user:marc)
Feb 15 14:31:07 MM-Home ntfs-3g[4910]: Version 2013.1.13 external FUSE 29
Feb 15 14:31:07 MM-Home ntfs-3g[4910]: Mounted /dev/sda4 (Read-Write, label "", NTFS 3.1)
Feb 15 14:31:07 MM-Home ntfs-3g[4910]: Cmdline options: rw,nodev,nosuid,uid=1000,gid=100,uhelper=udisks2
Feb 15 14:31:07 MM-Home ntfs-3g[4910]: Mount options: rw,nodev,nosuid,uhelper=udisks2,allow_other,nonempty,relatime,default_permissions,fsname=/dev/sda4,blkdev,blksize=4096
Feb 15 14:31:07 MM-Home ntfs-3g[4910]: Global ownership and permissions enforced, configuration type 1
Feb 15 14:31:07 MM-Home udisksd[1335]: Mounted /dev/sda4 at /run/media/marc/3452CBB252CB76E0 on behalf of uid 1000
Feb 15 14:31:17 MM-Home kernel: FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Feb 15 14:31:17 MM-Home udisksd[1335]: Mounted /dev/sdc1 at /run/media/marc/OPENSUSE-LE on behalf of uid 1000
