Booting with 3.14.* results in unexpected shutdown

Problem description: Computer boots normally up until the moment before NVIDIA splash and entering login screen (quiet disabled shows no errors), but upon trying to do so suffers abrupt shutdown.
Some cases the computer screen goes blank, followed by a short period of nothing until the fans start running at max.
Adding "acpi=off"  to GRUB stops both above-mentioned events, instead the boot processs is simply halted at the same point with screen not being cleared and nothing else happening.
The computer is an ASUS G55VW laptop, Intel i7 CPU, NVIDIA GTX660M (without Optimus).
I'm running the stock kernel and the problem has persisted with all core versions of 3.14.* Downgrading NVIDIA from 337.* to 334.* has had no effect (337 depends on >3.14)
Relevant journalctl (which tells me nothing): (Alternatively, pastebin link)
-- Logs begin at Wed 2014-03-05 03:33:14 CET, end at Sun 2014-05-04 17:12:33 CEST. --
May 01 16:01:14 arch systemd-journal[177]: Runtime journal is using 8.0M (max allowed 397.1M, trying to leave 595.7M free of 3.8G available → current limit 397.1M).
May 01 16:01:14 arch systemd-journal[177]: Runtime journal is using 8.0M (max allowed 397.1M, trying to leave 595.7M free of 3.8G available → current limit 397.1M).
May 01 16:01:14 arch kernel: Initializing cgroup subsys cpuset
May 01 16:01:14 arch kernel: Initializing cgroup subsys cpu
May 01 16:01:14 arch kernel: Initializing cgroup subsys cpuacct
May 01 16:01:14 arch kernel: Linux version 3.14.2-1-ARCH (nobody@var-lib-archbuild-testing-x86_64-tobias) (gcc version 4.9.0 (GCC) ) #1 SMP PREEMPT Sun Apr 27 11:28:44 CEST 2014
May 01 16:01:14 arch kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=7919229d-db26-4075-ac4b-97d2fa5fc984 rw quiet
May 01 16:01:14 arch kernel: e820: BIOS-provided physical RAM map:
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000dd6f5fff] usable
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000dd6f6000-0x00000000dd6f7fff] reserved
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000dd6f8000-0x00000000dd704fff] usable
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000dd705000-0x00000000ddd05fff] ACPI NVS
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddd06000-0x00000000ddd08fff] reserved
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddd09000-0x00000000ddd1ffff] usable
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddd20000-0x00000000ddd25fff] reserved
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddd26000-0x00000000ddd27fff] usable
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddd28000-0x00000000ddd31fff] reserved
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddd32000-0x00000000ddec4fff] usable
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddec5000-0x00000000ddec8fff] reserved
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddec9000-0x00000000ddf12fff] usable
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf13000-0x00000000ddf37fff] reserved
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf38000-0x00000000ddf3afff] usable
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf3b000-0x00000000ddf3cfff] reserved
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf3d000-0x00000000ddf53fff] usable
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf54000-0x00000000ddf59fff] reserved
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf5a000-0x00000000ddf61fff] usable
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf62000-0x00000000ddf62fff] reserved
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf63000-0x00000000ddf71fff] usable
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf72000-0x00000000ddf72fff] reserved
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf73000-0x00000000ddf7dfff] usable
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf7e000-0x00000000ddf82fff] reserved
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf83000-0x00000000ddfaefff] usable
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddfaf000-0x00000000ddfaffff] reserved
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddfb0000-0x00000000ddfbffff] usable
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddfc0000-0x00000000ddfe7fff] reserved
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddfe8000-0x00000000ddffbfff] usable
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddffc000-0x00000000ddffcfff] reserved
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddffd000-0x00000000ddffdfff] usable
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddffe000-0x00000000ddffffff] reserved
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000de000000-0x00000000de001fff] usable
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000de002000-0x00000000de006fff] reserved
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000de007000-0x00000000de01afff] usable
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000de01b000-0x00000000de5e2fff] reserved
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000de5e3000-0x00000000de862fff] ACPI NVS
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000de863000-0x00000000de867fff] ACPI data
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000de868000-0x00000000de868fff] usable
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000de869000-0x00000000de8abfff] ACPI NVS
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000de8ac000-0x00000000decbefff] usable
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000decbf000-0x00000000deff3fff] reserved
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000deff4000-0x00000000deffffff] usable
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x0000000100000000-0x000000021f3fffff] usable
May 01 16:01:14 arch kernel: NX (Execute Disable) protection: active
May 01 16:01:14 arch kernel: efi: EFI v2.31 by American Megatrends
May 01 16:01:14 arch kernel: efi: ACPI=0xde839000 ACPI 2.0=0xde839000 SMBIOS=0xf04c0 MPS=0xfd4d0
May 01 16:01:14 arch kernel: efi: mem00: type=3, attr=0xf, range=[0x0000000000000000-0x0000000000008000) (0MB)
May 01 16:01:14 arch kernel: efi: mem01: type=7, attr=0xf, range=[0x0000000000008000-0x000000000005d000) (0MB)
May 01 16:01:14 arch kernel: efi: mem02: type=4, attr=0xf, range=[0x000000000005d000-0x0000000000060000) (0MB)
May 01 16:01:14 arch kernel: efi: mem03: type=3, attr=0xf, range=[0x0000000000060000-0x000000000009f000) (0MB)
May 01 16:01:14 arch kernel: efi: mem04: type=6, attr=0x800000000000000f, range=[0x000000000009f000-0x00000000000a0000) (0MB)
May 01 16:01:14 arch kernel: efi: mem05: type=7, attr=0xf, range=[0x0000000000100000-0x0000000001000000) (15MB)
May 01 16:01:14 arch kernel: efi: mem06: type=2, attr=0xf, range=[0x0000000001000000-0x000000000205b000) (16MB)
May 01 16:01:14 arch kernel: efi: mem07: type=7, attr=0xf, range=[0x000000000205b000-0x00000000379d4000) (857MB)
May 01 16:01:14 arch kernel: efi: mem08: type=2, attr=0xf, range=[0x00000000379d4000-0x0000000037ce2000) (3MB)
May 01 16:01:14 arch kernel: efi: mem09: type=7, attr=0xf, range=[0x0000000037ce2000-0x000000009dbfb000) (1631MB)
May 01 16:01:14 arch kernel: efi: mem10: type=2, attr=0xf, range=[0x000000009dbfb000-0x00000000d2732000) (843MB)
May 01 16:01:14 arch kernel: efi: mem11: type=1, attr=0xf, range=[0x00000000d2732000-0x00000000d274f000) (0MB)
May 01 16:01:14 arch kernel: efi: mem12: type=7, attr=0xf, range=[0x00000000d274f000-0x00000000d276c000) (0MB)
May 01 16:01:14 arch kernel: efi: mem13: type=4, attr=0xf, range=[0x00000000d276c000-0x00000000d293d000) (1MB)
May 01 16:01:14 arch kernel: efi: mem14: type=7, attr=0xf, range=[0x00000000d293d000-0x00000000d2949000) (0MB)
May 01 16:01:14 arch kernel: efi: mem15: type=4, attr=0xf, range=[0x00000000d2949000-0x00000000d29a2000) (0MB)
May 01 16:01:14 arch kernel: efi: mem16: type=7, attr=0xf, range=[0x00000000d29a2000-0x00000000d2ac9000) (1MB)
May 01 16:01:14 arch kernel: efi: mem17: type=4, attr=0xf, range=[0x00000000d2ac9000-0x00000000dc390000) (152MB)
May 01 16:01:14 arch kernel: efi: mem18: type=7, attr=0xf, range=[0x00000000dc390000-0x00000000dc393000) (0MB)
May 01 16:01:14 arch kernel: efi: mem19: type=4, attr=0xf, range=[0x00000000dc393000-0x00000000dc3cd000) (0MB)
May 01 16:01:14 arch kernel: efi: mem20: type=7, attr=0xf, range=[0x00000000dc3cd000-0x00000000dc3ce000) (0MB)
May 01 16:01:14 arch kernel: efi: mem21: type=4, attr=0xf, range=[0x00000000dc3ce000-0x00000000dd07f000) (12MB)
May 01 16:01:14 arch kernel: efi: mem22: type=7, attr=0xf, range=[0x00000000dd07f000-0x00000000dd6d1000) (6MB)
May 01 16:01:14 arch kernel: efi: mem23: type=2, attr=0xf, range=[0x00000000dd6d1000-0x00000000dd6dd000) (0MB)
May 01 16:01:14 arch kernel: efi: mem24: type=3, attr=0xf, range=[0x00000000dd6dd000-0x00000000dd6f6000) (0MB)
May 01 16:01:14 arch kernel: efi: mem25: type=6, attr=0x800000000000000f, range=[0x00000000dd6f6000-0x00000000dd6f8000) (0MB)
May 01 16:01:14 arch kernel: efi: mem26: type=3, attr=0xf, range=[0x00000000dd6f8000-0x00000000dd705000) (0MB)
May 01 16:01:14 arch kernel: efi: mem27: type=10, attr=0xf, range=[0x00000000dd705000-0x00000000ddd06000) (6MB)
May 01 16:01:14 arch kernel: efi: mem28: type=5, attr=0x800000000000000f, range=[0x00000000ddd06000-0x00000000ddd09000) (0MB)
May 01 16:01:14 arch kernel: efi: mem29: type=3, attr=0xf, range=[0x00000000ddd09000-0x00000000ddd20000) (0MB)
May 01 16:01:14 arch kernel: efi: mem30: type=5, attr=0x800000000000000f, range=[0x00000000ddd20000-0x00000000ddd26000) (0MB)
May 01 16:01:14 arch kernel: efi: mem31: type=3, attr=0xf, range=[0x00000000ddd26000-0x00000000ddd28000) (0MB)
May 01 16:01:14 arch kernel: efi: mem32: type=5, attr=0x800000000000000f, range=[0x00000000ddd28000-0x00000000ddd32000) (0MB)
May 01 16:01:14 arch kernel: efi: mem33: type=3, attr=0xf, range=[0x00000000ddd32000-0x00000000ddec5000) (1MB)
May 01 16:01:14 arch kernel: efi: mem34: type=5, attr=0x800000000000000f, range=[0x00000000ddec5000-0x00000000ddec9000) (0MB)
May 01 16:01:14 arch kernel: efi: mem35: type=3, attr=0xf, range=[0x00000000ddec9000-0x00000000ddf13000) (0MB)
May 01 16:01:14 arch kernel: efi: mem36: type=5, attr=0x800000000000000f, range=[0x00000000ddf13000-0x00000000ddf1a000) (0MB)
May 01 16:01:14 arch kernel: efi: mem37: type=6, attr=0x800000000000000f, range=[0x00000000ddf1a000-0x00000000ddf27000) (0MB)
May 01 16:01:14 arch kernel: efi: mem38: type=5, attr=0x800000000000000f, range=[0x00000000ddf27000-0x00000000ddf38000) (0MB)
May 01 16:01:14 arch kernel: efi: mem39: type=3, attr=0xf, range=[0x00000000ddf38000-0x00000000ddf3b000) (0MB)
May 01 16:01:14 arch kernel: efi: mem40: type=5, attr=0x800000000000000f, range=[0x00000000ddf3b000-0x00000000ddf3d000) (0MB)
May 01 16:01:14 arch kernel: efi: mem41: type=3, attr=0xf, range=[0x00000000ddf3d000-0x00000000ddf54000) (0MB)
May 01 16:01:14 arch kernel: efi: mem42: type=5, attr=0x800000000000000f, range=[0x00000000ddf54000-0x00000000ddf5a000) (0MB)
May 01 16:01:14 arch kernel: efi: mem43: type=3, attr=0xf, range=[0x00000000ddf5a000-0x00000000ddf62000) (0MB)
May 01 16:01:14 arch kernel: efi: mem44: type=5, attr=0x800000000000000f, range=[0x00000000ddf62000-0x00000000ddf63000) (0MB)
May 01 16:01:14 arch kernel: efi: mem45: type=3, attr=0xf, range=[0x00000000ddf63000-0x00000000ddf72000) (0MB)
May 01 16:01:14 arch kernel: efi: mem46: type=5, attr=0x800000000000000f, range=[0x00000000ddf72000-0x00000000ddf73000) (0MB)
May 01 16:01:14 arch kernel: efi: mem47: type=3, attr=0xf, range=[0x00000000ddf73000-0x00000000ddf7e000) (0MB)
May 01 16:01:14 arch kernel: efi: mem48: type=5, attr=0x800000000000000f, range=[0x00000000ddf7e000-0x00000000ddf83000) (0MB)
May 01 16:01:14 arch kernel: efi: mem49: type=3, attr=0xf, range=[0x00000000ddf83000-0x00000000ddfaf000) (0MB)
May 01 16:01:14 arch kernel: efi: mem50: type=5, attr=0x800000000000000f, range=[0x00000000ddfaf000-0x00000000ddfb0000) (0MB)
May 01 16:01:14 arch kernel: efi: mem51: type=3, attr=0xf, range=[0x00000000ddfb0000-0x00000000ddfc0000) (0MB)
May 01 16:01:14 arch kernel: efi: mem52: type=5, attr=0x800000000000000f, range=[0x00000000ddfc0000-0x00000000ddfe8000) (0MB)
May 01 16:01:14 arch kernel: efi: mem53: type=3, attr=0xf, range=[0x00000000ddfe8000-0x00000000ddffc000) (0MB)
May 01 16:01:14 arch kernel: efi: mem54: type=5, attr=0x800000000000000f, range=[0x00000000ddffc000-0x00000000ddffd000) (0MB)
May 01 16:01:14 arch kernel: efi: mem55: type=3, attr=0xf, range=[0x00000000ddffd000-0x00000000ddffe000) (0MB)
May 01 16:01:14 arch kernel: efi: mem56: type=5, attr=0x800000000000000f, range=[0x00000000ddffe000-0x00000000de000000) (0MB)
May 01 16:01:14 arch kernel: efi: mem57: type=3, attr=0xf, range=[0x00000000de000000-0x00000000de002000) (0MB)
May 01 16:01:14 arch kernel: efi: mem58: type=5, attr=0x800000000000000f, range=[0x00000000de002000-0x00000000de007000) (0MB)
May 01 16:01:14 arch kernel: efi: mem59: type=3, attr=0xf, range=[0x00000000de007000-0x00000000de01b000) (0MB)
May 01 16:01:14 arch kernel: efi: mem60: type=6, attr=0x800000000000000f, range=[0x00000000de01b000-0x00000000de09c000) (0MB)
May 01 16:01:14 arch kernel: efi: mem61: type=5, attr=0x800000000000000f, range=[0x00000000de09c000-0x00000000de0b9000) (0MB)
May 01 16:01:14 arch kernel: efi: mem62: type=6, attr=0x800000000000000f, range=[0x00000000de0b9000-0x00000000de0bf000) (0MB)
May 01 16:01:14 arch kernel: efi: mem63: type=6, attr=0x800000000000000f, range=[0x00000000de0bf000-0x00000000de0c1000) (0MB)
May 01 16:01:14 arch kernel: efi: mem64: type=6, attr=0x800000000000000f, range=[0x00000000de0c1000-0x00000000de0e3000) (0MB)
May 01 16:01:14 arch kernel: efi: mem65: type=0, attr=0xf, range=[0x00000000de0e3000-0x00000000de437000) (3MB)
May 01 16:01:14 arch kernel: efi: mem66: type=0, attr=0xf, range=[0x00000000de437000-0x00000000de578000) (1MB)
May 01 16:01:14 arch kernel: efi: mem67: type=0, attr=0xf, range=[0x00000000de578000-0x00000000de57e000) (0MB)
May 01 16:01:14 arch kernel: efi: mem68: type=0, attr=0xf, range=[0x00000000de57e000-0x00000000de5e3000) (0MB)
May 01 16:01:14 arch kernel: efi: mem69: type=10, attr=0xf, range=[0x00000000de5e3000-0x00000000de699000) (0MB)
May 01 16:01:14 arch kernel: efi: mem70: type=10, attr=0xf, range=[0x00000000de699000-0x00000000de863000) (1MB)
May 01 16:01:14 arch kernel: efi: mem71: type=9, attr=0xf, range=[0x00000000de863000-0x00000000de868000) (0MB)
May 01 16:01:14 arch kernel: efi: mem72: type=4, attr=0xf, range=[0x00000000de868000-0x00000000de869000) (0MB)
May 01 16:01:14 arch kernel: efi: mem73: type=10, attr=0xf, range=[0x00000000de869000-0x00000000de8ac000) (0MB)
May 01 16:01:14 arch kernel: efi: mem74: type=4, attr=0xf, range=[0x00000000de8ac000-0x00000000de9fa000) (1MB)
May 01 16:01:14 arch kernel: efi: mem75: type=3, attr=0xf, range=[0x00000000de9fa000-0x00000000dec96000) (2MB)
May 01 16:01:14 arch kernel: efi: mem76: type=4, attr=0xf, range=[0x00000000dec96000-0x00000000deca6000) (0MB)
May 01 16:01:14 arch kernel: efi: mem77: type=3, attr=0xf, range=[0x00000000deca6000-0x00000000decb8000) (0MB)
May 01 16:01:14 arch kernel: efi: mem78: type=4, attr=0xf, range=[0x00000000decb8000-0x00000000decbf000) (0MB)
May 01 16:01:14 arch kernel: efi: mem79: type=6, attr=0x800000000000000f, range=[0x00000000decbf000-0x00000000deff4000) (3MB)
May 01 16:01:14 arch kernel: efi: mem80: type=4, attr=0xf, range=[0x00000000deff4000-0x00000000df000000) (0MB)
May 01 16:01:14 arch kernel: efi: mem81: type=7, attr=0xf, range=[0x0000000100000000-0x000000021f400000) (4596MB)
May 01 16:01:14 arch kernel: efi: mem82: type=11, attr=0x8000000000000001, range=[0x00000000f8000000-0x00000000fc000000) (64MB)
May 01 16:01:14 arch kernel: efi: mem83: type=11, attr=0x8000000000000001, range=[0x00000000fec00000-0x00000000fec01000) (0MB)
May 01 16:01:14 arch kernel: efi: mem84: type=11, attr=0x8000000000000001, range=[0x00000000fed00000-0x00000000fed04000) (0MB)
May 01 16:01:14 arch kernel: efi: mem85: type=11, attr=0x8000000000000001, range=[0x00000000fed1c000-0x00000000fed20000) (0MB)
May 01 16:01:14 arch kernel: efi: mem86: type=11, attr=0x8000000000000001, range=[0x00000000fee00000-0x00000000fee01000) (0MB)
May 01 16:01:14 arch kernel: efi: mem87: type=11, attr=0x8000000000000001, range=[0x00000000ff000000-0x0000000100000000) (16MB)
May 01 16:01:14 arch kernel: SMBIOS 2.7 present.
May 01 16:01:14 arch kernel: DMI: ASUSTeK COMPUTER INC. G55VW/G55VW, BIOS G55VW.217 11/05/2012
May 01 16:01:14 arch kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
May 01 16:01:14 arch kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
May 01 16:01:14 arch kernel: No AGP bridge found
May 01 16:01:14 arch kernel: e820: last_pfn = 0x21f400 max_arch_pfn = 0x400000000
May 01 16:01:14 arch kernel: MTRR default type: uncachable
May 01 16:01:14 arch kernel: MTRR fixed ranges enabled:
May 01 16:01:14 arch kernel: 00000-9FFFF write-back
May 01 16:01:14 arch kernel: A0000-BFFFF uncachable
May 01 16:01:14 arch kernel: C0000-CFFFF write-protect
May 01 16:01:14 arch kernel: D0000-DFFFF uncachable
May 01 16:01:14 arch kernel: E0000-FFFFF write-protect
May 01 16:01:14 arch kernel: MTRR variable ranges enabled:
May 01 16:01:14 arch kernel: 0 base 000000000 mask E00000000 write-back
May 01 16:01:14 arch kernel: 1 base 200000000 mask FF0000000 write-back
May 01 16:01:14 arch kernel: 2 base 210000000 mask FF8000000 write-back
May 01 16:01:14 arch kernel: 3 base 218000000 mask FFC000000 write-back
May 01 16:01:14 arch kernel: 4 base 21C000000 mask FFE000000 write-back
May 01 16:01:14 arch kernel: 5 base 21E000000 mask FFF000000 write-back
May 01 16:01:14 arch kernel: 6 base 21F000000 mask FFFC00000 write-back
May 01 16:01:14 arch kernel: 7 base 0E0000000 mask FE0000000 uncachable
May 01 16:01:14 arch kernel: 8 base 0DFC00000 mask FFFC00000 uncachable
May 01 16:01:14 arch kernel: 9 disabled
May 01 16:01:14 arch kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
May 01 16:01:14 arch kernel: e820: update [mem 0xdfc00000-0xffffffff] usable ==> reserved
May 01 16:01:14 arch kernel: e820: last_pfn = 0xdf000 max_arch_pfn = 0x400000000
May 01 16:01:14 arch kernel: found SMP MP-table at [mem 0x000fd830-0x000fd83f] mapped at [ffff8800000fd830]
May 01 16:01:14 arch kernel: Scanning 1 areas for low memory corruption
May 01 16:01:14 arch kernel: Base memory trampoline at [ffff880000097000] 97000 size 24576
May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
May 01 16:01:14 arch kernel: [mem 0x00000000-0x000fffff] page 4k
May 01 16:01:14 arch kernel: BRK [0x01b39000, 0x01b39fff] PGTABLE
May 01 16:01:14 arch kernel: BRK [0x01b3a000, 0x01b3afff] PGTABLE
May 01 16:01:14 arch kernel: BRK [0x01b3b000, 0x01b3bfff] PGTABLE
May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0x21f200000-0x21f3fffff]
May 01 16:01:14 arch kernel: [mem 0x21f200000-0x21f3fffff] page 2M
May 01 16:01:14 arch kernel: BRK [0x01b3c000, 0x01b3cfff] PGTABLE
May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0x21c000000-0x21f1fffff]
May 01 16:01:14 arch kernel: [mem 0x21c000000-0x21f1fffff] page 2M
May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0x200000000-0x21bffffff]
May 01 16:01:14 arch kernel: [mem 0x200000000-0x21bffffff] page 2M
May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0x00100000-0xdd6f5fff]
May 01 16:01:14 arch kernel: [mem 0x00100000-0x001fffff] page 4k
May 01 16:01:14 arch kernel: [mem 0x00200000-0xdd5fffff] page 2M
May 01 16:01:14 arch kernel: [mem 0xdd600000-0xdd6f5fff] page 4k
May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xdd6f8000-0xdd704fff]
May 01 16:01:14 arch kernel: [mem 0xdd6f8000-0xdd704fff] page 4k
May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddd09000-0xddd1ffff]
May 01 16:01:14 arch kernel: [mem 0xddd09000-0xddd1ffff] page 4k
May 01 16:01:14 arch kernel: BRK [0x01b3d000, 0x01b3dfff] PGTABLE
May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddd26000-0xddd27fff]
May 01 16:01:14 arch kernel: [mem 0xddd26000-0xddd27fff] page 4k
May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddd32000-0xddec4fff]
May 01 16:01:14 arch kernel: [mem 0xddd32000-0xddec4fff] page 4k
May 01 16:01:14 arch kernel: BRK [0x01b3e000, 0x01b3efff] PGTABLE
May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddec9000-0xddf12fff]
May 01 16:01:14 arch kernel: [mem 0xddec9000-0xddf12fff] page 4k
May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddf38000-0xddf3afff]
May 01 16:01:14 arch kernel: [mem 0xddf38000-0xddf3afff] page 4k
May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddf3d000-0xddf53fff]
May 01 16:01:14 arch kernel: [mem 0xddf3d000-0xddf53fff] page 4k
May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddf5a000-0xddf61fff]
May 01 16:01:14 arch kernel: [mem 0xddf5a000-0xddf61fff] page 4k
May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddf63000-0xddf71fff]
May 01 16:01:14 arch kernel: [mem 0xddf63000-0xddf71fff] page 4k
May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddf73000-0xddf7dfff]
May 01 16:01:14 arch kernel: [mem 0xddf73000-0xddf7dfff] page 4k
May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddf83000-0xddfaefff]
May 01 16:01:14 arch kernel: [mem 0xddf83000-0xddfaefff] page 4k
May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddfb0000-0xddfbffff]
May 01 16:01:14 arch kernel: [mem 0xddfb0000-0xddfbffff] page 4k
May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddfe8000-0xddffbfff]
May 01 16:01:14 arch kernel: [mem 0xddfe8000-0xddffbfff] page 4k
May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddffd000-0xddffdfff]
May 01 16:01:14 arch kernel: [mem 0xddffd000-0xddffdfff] page 4k
May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xde000000-0xde001fff]
May 01 16:01:14 arch kernel: [mem 0xde000000-0xde001fff] page 4k
May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xde007000-0xde01afff]
May 01 16:01:14 arch kernel: [mem 0xde007000-0xde01afff] page 4k
May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xde868000-0xde868fff]
May 01 16:01:14 arch kernel: [mem 0xde868000-0xde868fff] page 4k
May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xde8ac000-0xdecbefff]
May 01 16:01:14 arch kernel: [mem 0xde8ac000-0xde9fffff] page 4k
May 01 16:01:14 arch kernel: [mem 0xdea00000-0xdebfffff] page 2M
May 01 16:01:14 arch kernel: [mem 0xdec00000-0xdecbefff] page 4k
May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xdeff4000-0xdeffffff]
May 01 16:01:14 arch kernel: [mem 0xdeff4000-0xdeffffff] page 4k
May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0x100000000-0x1ffffffff]
May 01 16:01:14 arch kernel: [mem 0x100000000-0x1ffffffff] page 2M
May 01 16:01:14 arch kernel: RAMDISK: [mem 0x379d4000-0x37ce1fff]
May 01 16:01:14 arch kernel: ACPI: RSDP 00000000de839000 000024 (v02 _ASUS_)
May 01 16:01:14 arch kernel: ACPI: XSDT 00000000de839080 00007C (v01 _ASUS_ Notebook 01072009 AMI 00010013)
May 01 16:01:14 arch kernel: ACPI: FACP 00000000de849e28 00010C (v05 _ASUS_ Notebook 01072009 AMI 00010013)
May 01 16:01:14 arch kernel: ACPI: DSDT 00000000de839190 010C93 (v02 _ASUS_ Notebook 00000013 INTL 20091112)
May 01 16:01:14 arch kernel: ACPI: FACS 00000000de860080 000040
May 01 16:01:14 arch kernel: ACPI: APIC 00000000de849f38 000092 (v03 _ASUS_ Notebook 01072009 AMI 00010013)
May 01 16:01:14 arch kernel: ACPI: FPDT 00000000de849fd0 000044 (v01 _ASUS_ Notebook 01072009 AMI 00010013)
May 01 16:01:14 arch kernel: ACPI: ECDT 00000000de84a018 0000C1 (v01 _ASUS_ Notebook 01072009 AMI. 00000005)
May 01 16:01:14 arch kernel: ACPI: MCFG 00000000de84a0e0 00003C (v01 _ASUS_ Notebook 01072009 MSFT 00000097)
May 01 16:01:14 arch kernel: ACPI: SLIC 00000000de84a120 000176 (v01 _ASUS_ Notebook 01072009 ASUS 00000001)
May 01 16:01:14 arch kernel: ACPI: HPET 00000000de84a298 000038 (v01 _ASUS_ Notebook 01072009 AMI. 00000005)
May 01 16:01:14 arch kernel: ACPI: SSDT 00000000de84a2d0 00066E (v01 AhciR1 AhciTab1 00001000 INTL 20091112)
May 01 16:01:14 arch kernel: ACPI: SSDT 00000000de84a940 00049E (v01 AhciR2 AhciTab2 00001000 INTL 20091112)
May 01 16:01:14 arch kernel: ACPI: SSDT 00000000de84ade0 00090A (v01 PmRef Cpu0Ist 00003000 INTL 20051117)
May 01 16:01:14 arch kernel: ACPI: SSDT 00000000de84b6f0 000A92 (v01 PmRef CpuPm 00003000 INTL 20051117)
May 01 16:01:14 arch kernel: ACPI: Local APIC address 0xfee00000
May 01 16:01:14 arch kernel: No NUMA configuration found
May 01 16:01:14 arch kernel: Faking a node at [mem 0x0000000000000000-0x000000021f3fffff]
May 01 16:01:14 arch kernel: Initmem setup node 0 [mem 0x00000000-0x21f3fffff]
May 01 16:01:14 arch kernel: NODE_DATA [mem 0x21f3ef000-0x21f3f3fff]
May 01 16:01:14 arch kernel: [ffffea0000000000-ffffea00087fffff] PMD -> [ffff880216a00000-ffff88021e9fffff] on node 0
May 01 16:01:14 arch kernel: Zone ranges:
May 01 16:01:14 arch kernel: DMA [mem 0x00001000-0x00ffffff]
May 01 16:01:14 arch kernel: DMA32 [mem 0x01000000-0xffffffff]
May 01 16:01:14 arch kernel: Normal [mem 0x100000000-0x21f3fffff]
May 01 16:01:14 arch kernel: Movable zone start for each node
May 01 16:01:14 arch kernel: Early memory node ranges
May 01 16:01:14 arch kernel: node 0: [mem 0x00001000-0x0009efff]
May 01 16:01:14 arch kernel: node 0: [mem 0x00100000-0xdd6f5fff]
May 01 16:01:14 arch kernel: node 0: [mem 0xdd6f8000-0xdd704fff]
May 01 16:01:14 arch kernel: node 0: [mem 0xddd09000-0xddd1ffff]
May 01 16:01:14 arch kernel: node 0: [mem 0xddd26000-0xddd27fff]
May 01 16:01:14 arch kernel: node 0: [mem 0xddd32000-0xddec4fff]
May 01 16:01:14 arch kernel: node 0: [mem 0xddec9000-0xddf12fff]
May 01 16:01:14 arch kernel: node 0: [mem 0xddf38000-0xddf3afff]
May 01 16:01:14 arch kernel: node 0: [mem 0xddf3d000-0xddf53fff]
May 01 16:01:14 arch kernel: node 0: [mem 0xddf5a000-0xddf61fff]
May 01 16:01:14 arch kernel: node 0: [mem 0xddf63000-0xddf71fff]
May 01 16:01:14 arch kernel: node 0: [mem 0xddf73000-0xddf7dfff]
May 01 16:01:14 arch kernel: node 0: [mem 0xddf83000-0xddfaefff]
May 01 16:01:14 arch kernel: node 0: [mem 0xddfb0000-0xddfbffff]
May 01 16:01:14 arch kernel: node 0: [mem 0xddfe8000-0xddffbfff]
May 01 16:01:14 arch kernel: node 0: [mem 0xddffd000-0xddffdfff]
May 01 16:01:14 arch kernel: node 0: [mem 0xde000000-0xde001fff]
May 01 16:01:14 arch kernel: node 0: [mem 0xde007000-0xde01afff]
May 01 16:01:14 arch kernel: node 0: [mem 0xde868000-0xde868fff]
May 01 16:01:14 arch kernel: node 0: [mem 0xde8ac000-0xdecbefff]
May 01 16:01:14 arch kernel: node 0: [mem 0xdeff4000-0xdeffffff]
May 01 16:01:14 arch kernel: node 0: [mem 0x100000000-0x21f3fffff]
May 01 16:01:14 arch kernel: On node 0 totalpages: 2085210
May 01 16:01:14 arch kernel: DMA zone: 64 pages used for memmap
May 01 16:01:14 arch kernel: DMA zone: 28 pages reserved
May 01 16:01:14 arch kernel: DMA zone: 3998 pages, LIFO batch:0
May 01 16:01:14 arch kernel: DMA32 zone: 14135 pages used for memmap
May 01 16:01:14 arch kernel: DMA32 zone: 904636 pages, LIFO batch:31
May 01 16:01:14 arch kernel: Normal zone: 18384 pages used for memmap
May 01 16:01:14 arch kernel: Normal zone: 1176576 pages, LIFO batch:31
May 01 16:01:14 arch kernel: ACPI: PM-Timer IO Port: 0x408
May 01 16:01:14 arch kernel: ACPI: Local APIC address 0xfee00000
May 01 16:01:14 arch kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
May 01 16:01:14 arch kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
May 01 16:01:14 arch kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
May 01 16:01:14 arch kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)
May 01 16:01:14 arch kernel: ACPI: LAPIC (acpi_id[0x05] lapic_id[0x01] enabled)
May 01 16:01:14 arch kernel: ACPI: LAPIC (acpi_id[0x06] lapic_id[0x03] enabled)
May 01 16:01:14 arch kernel: ACPI: LAPIC (acpi_id[0x07] lapic_id[0x05] enabled)
May 01 16:01:14 arch kernel: ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] enabled)
May 01 16:01:14 arch kernel: ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
May 01 16:01:14 arch kernel: ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
May 01 16:01:14 arch kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
May 01 16:01:14 arch kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
May 01 16:01:14 arch kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
May 01 16:01:14 arch kernel: ACPI: IRQ0 used by override.
May 01 16:01:14 arch kernel: ACPI: IRQ2 used by override.
May 01 16:01:14 arch kernel: ACPI: IRQ9 used by override.
May 01 16:01:14 arch kernel: Using ACPI (MADT) for SMP configuration information
May 01 16:01:14 arch kernel: ACPI: HPET id: 0x8086a701 base: 0xfed00000
May 01 16:01:14 arch kernel: smpboot: Allowing 8 CPUs, 0 hotplug CPUs
May 01 16:01:14 arch kernel: nr_irqs_gsi: 40
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000fffff]
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xdd6f6000-0xdd6f7fff]
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xdd705000-0xddd05fff]
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddd06000-0xddd08fff]
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddd20000-0xddd25fff]
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddd28000-0xddd31fff]
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddec5000-0xddec8fff]
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddf13000-0xddf37fff]
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddf3b000-0xddf3cfff]
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddf54000-0xddf59fff]
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddf62000-0xddf62fff]
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddf72000-0xddf72fff]
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddf7e000-0xddf82fff]
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddfaf000-0xddfaffff]
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddfc0000-0xddfe7fff]
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddffc000-0xddffcfff]
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddffe000-0xddffffff]
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xde002000-0xde006fff]
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xde01b000-0xde5e2fff]
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xde5e3000-0xde862fff]
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xde863000-0xde867fff]
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xde869000-0xde8abfff]
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xdecbf000-0xdeff3fff]
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xdf000000-0xf7ffffff]
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xfc000000-0xfebfffff]
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xfec01000-0xfecfffff]
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xfed00000-0xfed03fff]
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xfed04000-0xfed1bfff]
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xfed20000-0xfedfffff]
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xfee01000-0xfeffffff]
May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
May 01 16:01:14 arch kernel: e820: [mem 0xdf000000-0xf7ffffff] available for PCI devices
May 01 16:01:14 arch kernel: Booting paravirtualized kernel on bare hardware
May 01 16:01:14 arch kernel: setup_percpu: NR_CPUS:128 nr_cpumask_bits:128 nr_cpu_ids:8 nr_node_ids:1
May 01 16:01:14 arch kernel: PERCPU: Embedded 29 pages/cpu @ffff88021f000000 s87040 r8192 d23552 u262144
May 01 16:01:14 arch kernel: pcpu-alloc: s87040 r8192 d23552 u262144 alloc=1*2097152
May 01 16:01:14 arch kernel: pcpu-alloc: [0] 0 1 2 3 4 5 6 7
May 01 16:01:14 arch kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 2052599
May 01 16:01:14 arch kernel: Policy zone: Normal
May 01 16:01:14 arch kernel: Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=7919229d-db26-4075-ac4b-97d2fa5fc984 rw quiet
May 01 16:01:14 arch kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
May 01 16:01:14 arch kernel: xsave: enabled xstate_bv 0x7, cntxt size 0x340
May 01 16:01:14 arch kernel: Checking aperture...
May 01 16:01:14 arch kernel: No AGP bridge found
May 01 16:01:14 arch kernel: Calgary: detecting Calgary via BIOS EBDA area
May 01 16:01:14 arch kernel: Calgary: Unable to locate Rio Grande table in EBDA - bailing!
May 01 16:01:14 arch kernel: Memory: 7948780K/8340840K available (5229K kernel code, 857K rwdata, 1632K rodata, 1120K init, 1288K bss, 392060K reserved)
May 01 16:01:14 arch kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
May 01 16:01:14 arch kernel: Preemptible hierarchical RCU implementation.
May 01 16:01:14 arch kernel: RCU dyntick-idle grace-period acceleration is enabled.
May 01 16:01:14 arch kernel: Dump stacks of tasks blocking RCU-preempt GP.
May 01 16:01:14 arch kernel: RCU restricting CPUs from NR_CPUS=128 to nr_cpu_ids=8.
May 01 16:01:14 arch kernel: RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
May 01 16:01:14 arch kernel: NR_IRQS:8448 nr_irqs:744 16
May 01 16:01:14 arch kernel: Console: colour dummy device 80x25
May 01 16:01:14 arch kernel: console [tty0] enabled
May 01 16:01:14 arch kernel: allocated 33554432 bytes of page_cgroup
May 01 16:01:14 arch kernel: please try 'cgroup_disable=memory' option if you don't want memory cgroups
May 01 16:01:14 arch kernel: hpet clockevent registered
May 01 16:01:14 arch kernel: tsc: Fast TSC calibration using PIT
May 01 16:01:14 arch kernel: tsc: Detected 2294.759 MHz processor
May 01 16:01:14 arch kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 4591.74 BogoMIPS (lpj=7649196)
May 01 16:01:14 arch kernel: pid_max: default: 32768 minimum: 301
May 01 16:01:14 arch kernel: ACPI: Core revision 20131218
May 01 16:01:14 arch kernel: ACPI: All ACPI Tables successfully acquired
May 01 16:01:14 arch kernel: Security Framework initialized
May 01 16:01:14 arch kernel: Yama: becoming mindful.
May 01 16:01:14 arch kernel: Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
May 01 16:01:14 arch kernel: Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
May 01 16:01:14 arch kernel: Mount-cache hash table entries: 16384 (order: 5, 131072 bytes)
May 01 16:01:14 arch kernel: Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes)
May 01 16:01:14 arch kernel: Initializing cgroup subsys memory
May 01 16:01:14 arch kernel: Initializing cgroup subsys devices
May 01 16:01:14 arch kernel: Initializing cgroup subsys freezer
May 01 16:01:14 arch kernel: Initializing cgroup subsys net_cls
May 01 16:01:14 arch kernel: Initializing cgroup subsys blkio
May 01 16:01:14 arch kernel: CPU: Physical Processor ID: 0
May 01 16:01:14 arch kernel: CPU: Processor Core ID: 0
May 01 16:01:14 arch kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
May 01 16:01:14 arch kernel: mce: CPU supports 9 MCE banks
May 01 16:01:14 arch kernel: CPU0: Thermal monitoring enabled (TM1)
May 01 16:01:14 arch kernel: Last level iTLB entries: 4KB 512, 2MB 8, 4MB 8
Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32, 1GB 0
tlb_flushall_shift: 2
May 01 16:01:14 arch kernel: Freeing SMP alternatives memory: 20K (ffffffff819f0000 - ffffffff819f5000)
May 01 16:01:14 arch kernel: ftrace: allocating 20026 entries in 79 pages
May 01 16:01:14 arch kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
May 01 16:01:14 arch kernel: smpboot: CPU0: Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz (fam: 06, model: 3a, stepping: 09)
May 01 16:01:14 arch kernel: TSC deadline timer enabled
May 01 16:01:14 arch kernel: Performance Events: PEBS fmt1+, 16-deep LBR, IvyBridge events, full-width counters, Intel PMU driver.
May 01 16:01:14 arch kernel: ... version: 3
May 01 16:01:14 arch kernel: ... bit width: 48
May 01 16:01:14 arch kernel: ... generic registers: 4
May 01 16:01:14 arch kernel: ... value mask: 0000ffffffffffff
May 01 16:01:14 arch kernel: ... max period: 0000ffffffffffff
May 01 16:01:14 arch kernel: ... fixed-purpose events: 3
May 01 16:01:14 arch kernel: ... event mask: 000000070000000f
May 01 16:01:14 arch kernel: x86: Booting SMP configuration:
May 01 16:01:14 arch kernel: .... node #0, CPUs: #1
May 01 16:01:14 arch kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
May 01 16:01:14 arch kernel: #2 #3 #4 #5 #6 #7
May 01 16:01:14 arch kernel: x86: Booted up 1 node, 8 CPUs
May 01 16:01:14 arch kernel: smpboot: Total of 8 processors activated (36730.98 BogoMIPS)
May 01 16:01:14 arch kernel: devtmpfs: initialized
May 01 16:01:14 arch kernel: PM: Registering ACPI NVS region [mem 0xdd705000-0xddd05fff] (6295552 bytes)
May 01 16:01:14 arch kernel: PM: Registering ACPI NVS region [mem 0xde5e3000-0xde862fff] (2621440 bytes)
May 01 16:01:14 arch kernel: PM: Registering ACPI NVS region [mem 0xde869000-0xde8abfff] (274432 bytes)
May 01 16:01:14 arch kernel: pinctrl core: initialized pinctrl subsystem
May 01 16:01:14 arch kernel: RTC time: 14:01:11, date: 05/01/14
May 01 16:01:14 arch kernel: NET: Registered protocol family 16
May 01 16:01:14 arch kernel: cpuidle: using governor ladder
May 01 16:01:14 arch kernel: cpuidle: using governor menu
May 01 16:01:14 arch kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
May 01 16:01:14 arch kernel: ACPI: bus type PCI registered
May 01 16:01:14 arch kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
May 01 16:01:14 arch kernel: PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
May 01 16:01:14 arch kernel: PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
May 01 16:01:14 arch kernel: PCI: Using configuration type 1 for base access
May 01 16:01:14 arch kernel: bio: create slab <bio-0> at 0
May 01 16:01:14 arch kernel: ACPI: Added _OSI(Module Device)
May 01 16:01:14 arch kernel: ACPI: Added _OSI(Processor Device)
May 01 16:01:14 arch kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
May 01 16:01:14 arch kernel: ACPI: Added _OSI(Processor Aggregator Device)
May 01 16:01:14 arch kernel: ACPI : EC: EC description table is found, configuring boot EC
May 01 16:01:14 arch kernel: ACPI: Executed 1 blocks of module-level executable AML code
May 01 16:01:14 arch kernel: [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
May 01 16:01:14 arch kernel: ACPI: SSDT 00000000de590018 000853 (v01 PmRef Cpu0Cst 00003001 INTL 20051117)
May 01 16:01:14 arch kernel: ACPI: Dynamic OEM Table Load:
May 01 16:01:14 arch kernel: ACPI: SSDT (null) 000853 (v01 PmRef Cpu0Cst 00003001 INTL 20051117)
May 01 16:01:14 arch kernel: ACPI: SSDT 00000000de591a98 000303 (v01 PmRef ApIst 00003000 INTL 20051117)
May 01 16:01:14 arch kernel: ACPI: Dynamic OEM Table Load:
May 01 16:01:14 arch kernel: ACPI: SSDT (null) 000303 (v01 PmRef ApIst 00003000 INTL 20051117)
May 01 16:01:14 arch kernel: ACPI: SSDT 00000000de592c18 000119 (v01 PmRef ApCst 00003000 INTL 20051117)
May 01 16:01:14 arch kernel: ACPI: Dynamic OEM Table Load:
May 01 16:01:14 arch kernel: ACPI: SSDT (null) 000119 (v01 PmRef ApCst 00003000 INTL 20051117)
May 01 16:01:14 arch kernel: ACPI: Interpreter enabled
May 01 16:01:14 arch kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131218/hwxface-580)
May 01 16:01:14 arch kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131218/hwxface-580)
May 01 16:01:14 arch kernel: ACPI: (supports S0 S3 S4 S5)
May 01 16:01:14 arch kernel: ACPI: Using IOAPIC for interrupt routing
May 01 16:01:14 arch kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
May 01 16:01:14 arch kernel: ACPI: No dock devices found.
May 01 16:01:14 arch kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
May 01 16:01:14 arch kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
May 01 16:01:14 arch kernel: acpi PNP0A08:00: _OSC: platform does not support [PCIeHotplug PME]
May 01 16:01:14 arch kernel: acpi PNP0A08:00: _OSC: OS now controls [AER PCIeCapability]
May 01 16:01:14 arch kernel: PCI host bridge to bus 0000:00
May 01 16:01:14 arch kernel: pci_bus 0000:00: root bus resource [bus 00-3e]
May 01 16:01:14 arch kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
May 01 16:01:14 arch kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
May 01 16:01:14 arch kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
May 01 16:01:14 arch kernel: pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d3fff]
May 01 16:01:14 arch kernel: pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff]
May 01 16:01:14 arch kernel: pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff]
May 01 16:01:14 arch kernel: pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff]
May 01 16:01:14 arch kernel: pci_bus 0000:00: root bus resource [mem 0xdfc00000-0xfeafffff]
May 01 16:01:14 arch kernel: pci 0000:00:00.0: [8086:0154] type 00 class 0x060000
May 01 16:01:14 arch kernel: pci 0000:00:01.0: [8086:0151] type 01 class 0x060400
May 01 16:01:14 arch kernel: pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
May 01 16:01:14 arch kernel: pci 0000:00:01.0: System wakeup disabled by ACPI
May 01 16:01:14 arch kernel: pci 0000:00:14.0: [8086:1e31] type 00 class 0x0c0330
May 01 16:01:14 arch kernel: pci 0000:00:14.0: reg 0x10: [mem 0xf7300000-0xf730ffff 64bit]
May 01 16:01:14 arch kernel: pci 0000:00:14.0: PME# supported from D3hot D3cold
May 01 16:01:14 arch kernel: pci 0000:00:14.0: System wakeup disabled by ACPI
May 01 16:01:14 arch kernel: pci 0000:00:16.0: [8086:1e3a] type 00 class 0x078000
May 01 16:01:14 arch kernel: pci 0000:00:16.0: reg 0x10: [mem 0xf731b000-0xf731b00f 64bit]
May 01 16:01:14 arch kernel: pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
May 01 16:01:14 arch kernel: pci 0000:00:1a.0: [8086:1e2d] type 00 class 0x0c0320
May 01 16:01:14 arch kernel: pci 0000:00:1a.0: reg 0x10: [mem 0xf7318000-0xf73183ff]
May 01 16:01:14 arch kernel: pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
May 01 16:01:14 arch kernel: pci 0000:00:1a.0: System wakeup disabled by ACPI
May 01 16:01:14 arch kernel: pci 0000:00:1b.0: [8086:1e20] type 00 class 0x040300
May 01 16:01:14 arch kernel: pci 0000:00:1b.0: reg 0x10: [mem 0xf7310000-0xf7313fff 64bit]
May 01 16:01:14 arch kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
May 01 16:01:14 arch kernel: pci 0000:00:1b.0: System wakeup disabled by ACPI
May 01 16:01:14 arch kernel: pci 0000:00:1c.0: [8086:1e10] type 01 class 0x060400
May 01 16:01:14 arch kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
May 01 16:01:14 arch kernel: pci 0000:00:1c.0: System wakeup disabled by ACPI
May 01 16:01:14 arch kernel: pci 0000:00:1c.1: [8086:1e12] type 01 class 0x060400
May 01 16:01:14 arch kernel: pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
May 01 16:01:14 arch kernel: pci 0000:00:1c.3: [8086:1e16] type 01 class 0x060400
May 01 16:01:14 arch kernel: pci 0000:00:1c.3: PME# supported from D0 D3hot D3cold
May 01 16:01:14 arch kernel: pci 0000:00:1c.3: System wakeup disabled by ACPI
May 01 16:01:14 arch kernel: pci 0000:00:1c.4: [8086:1e18] type 01 class 0x060400
May 01 16:01:14 arch kernel: pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
May 01 16:01:14 arch kernel: pci 0000:00:1c.4: System wakeup disabled by ACPI
May 01 16:01:14 arch kernel: pci 0000:00:1d.0: [8086:1e26] type 00 class 0x0c0320
May 01 16:01:14 arch kernel: pci 0000:00:1d.0: reg 0x10: [mem 0xf7317000-0xf73173ff]
May 01 16:01:14 arch kernel: pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
May 01 16:01:14 arch kernel: pci 0000:00:1d.0: System wakeup disabled by ACPI
May 01 16:01:14 arch kernel: pci 0000:00:1f.0: [8086:1e57] type 00 class 0x060100
May 01 16:01:14 arch kernel: pci 0000:00:1f.2: [8086:1e03] type 00 class 0x010601
May 01 16:01:14 arch kernel: pci 0000:00:1f.2: reg 0x10: [io 0xf070-0xf077]
May 01 16:01:14 arch kernel: pci 0000:00:1f.2: reg 0x14: [io 0xf060-0xf063]
May 01 16:01:14 arch kernel: pci 0000:00:1f.2: reg 0x18: [io 0xf050-0xf057]
May 01 16:01:14 arch kernel: pci 0000:00:1f.2: reg 0x1c: [io 0xf040-0xf043]
May 01 16:01:14 arch kernel: pci 0000:00:1f.2: reg 0x20: [io 0xf020-0xf03f]
May 01 16:01:14 arch kernel: pci 0000:00:1f.2: reg 0x24: [mem 0xf7316000-0xf73167ff]
May 01 16:01:14 arch kernel: pci 0000:00:1f.2: PME# supported from D3hot
May 01 16:01:14 arch kernel: pci 0000:00:1f.3: [8086:1e22] type 00 class 0x0c0500
May 01 16:01:14 arch kernel: pci 0000:00:1f.3: reg 0x10: [mem 0xf7315000-0xf73150ff 64bit]
May 01 16:01:14 arch kernel: pci 0000:00:1f.3: reg 0x20: [io 0xf000-0xf01f]
May 01 16:01:14 arch kernel: pci 0000:01:00.0: [10de:0fd4] type 00 class 0x030000
May 01 16:01:14 arch kernel: pci 0000:01:00.0: reg 0x10: [mem 0xf6000000-0xf6ffffff]
May 01 16:01:14 arch kernel: pci 0000:01:00.0: reg 0x14: [mem 0xe0000000-0xefffffff 64bit pref]
May 01 16:01:14 arch kernel: pci 0000:01:00.0: reg 0x1c: [mem 0xf0000000-0xf1ffffff 64bit pref]
May 01 16:01:14 arch kernel: pci 0000:01:00.0: reg 0x24: [io 0xe000-0xe07f]
May 01 16:01:14 arch kernel: pci 0000:01:00.0: reg 0x30: [mem 0xf7000000-0xf707ffff pref]
May 01 16:01:14 arch kernel: pci 0000:01:00.1: [10de:0e1b] type 00 class 0x040300
May 01 16:01:14 arch kernel: pci 0000:01:00.1: reg 0x10: [mem 0xf7080000-0xf7083fff]
May 01 16:01:14 arch kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
May 01 16:01:14 arch kernel: pci 0000:00:01.0: bridge window [io 0xe000-0xefff]
May 01 16:01:14 arch kernel: pci 0000:00:01.0: bridge window [mem 0xf6000000-0xf70fffff]
May 01 16:01:14 arch kernel: pci 0000:00:01.0: bridge window [mem 0xe0000000-0xf1ffffff 64bit pref]
May 01 16:01:14 arch kernel: pci 0000:00:1c.0: PCI bridge to [bus 02]
May 01 16:01:14 arch kernel: pci 0000:03:00.0: [168c:0032] type 00 class 0x028000
May 01 16:01:14 arch kernel: pci 0000:03:00.0: reg 0x10: [mem 0xf7200000-0xf727ffff 64bit]
May 01 16:01:14 arch kernel: pci 0000:03:00.0: reg 0x30: [mem 0xf7280000-0xf728ffff pref]
May 01 16:01:14 arch kernel: pci 0000:03:00.0: supports D1 D2
May 01 16:01:14 arch kernel: pci 0000:03:00.0: PME# supported from D0 D1 D2 D3hot D3cold
May 01 16:01:14 arch kernel: pci 0000:03:00.0: System wakeup disabled by ACPI
May 01 16:01:14 arch kernel: pci 0000:00:1c.1: PCI bridge to [bus 03]
May 01 16:01:14 arch kernel: pci 0000:00:1c.1: bridge window [mem 0xf7200000-0xf72fffff]
May 01 16:01:14 arch kernel: pci 0000:04:00.0: [1969:1083] type 00 class 0x020000
May 01 16:01:14 arch kernel: pci 0000:04:00.0: reg 0x10: [mem 0xf7100000-0xf713ffff 64bit]
May 01 16:01:14 arch kernel: pci 0000:04:00.0: reg 0x18: [io 0xd000-0xd07f]
May 01 16:01:14 arch kernel: pci 0000:04:00.0: PME# supported from D0 D1 D2 D3hot D3cold
May 01 16:01:14 arch kernel: pci 0000:04:00.0: System wakeup disabled by ACPI
May 01 16:01:14 arch kernel: pci 0000:00:1c.3: PCI bridge to [bus 04]
May 01 16:01:14 arch kernel: pci 0000:00:1c.3: bridge window [io 0xd000-0xdfff]
May 01 16:01:14 arch kernel: pci 0000:00:1c.3: bridge window [mem 0xf7100000-0xf71fffff]
May 01 16:01:14 arch kernel: acpiphp: Slot [1] registered
May 01 16:01:14 arch kernel: pci 0000:00:1c.4: PCI bridge to [bus 05]
May 01 16:01:14 arch kernel: acpi PNP0A08:00: Disabling ASPM (FADT indicates it is unsupported)
May 01 16:01:14 arch kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12)
May 01 16:01:14 arch kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 12)
May 01 16:01:14 arch kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs *3 4 5 6 7 10 12)
May 01 16:01:14 arch kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 7 10 12)
May 01 16:01:14 arch kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 12) *0, disabled.
May 01 16:01:14 arch kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 12) *0, disabled.
May 01 16:01:14 arch kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 *4 5 6 7 10 12)
May 01 16:01:14 arch kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 *10 12)
May 01 16:01:14 arch kernel: ACPI: Enabled 3 GPEs in block 00 to 3F
May 01 16:01:14 arch kernel: ACPI : EC: GPE = 0x19, I/O: command/status = 0x66, data = 0x62
May 01 16:01:14 arch kernel: vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
May 01 16:01:14 arch kernel: vgaarb: loaded
May 01 16:01:14 arch kernel: vgaarb: bridge control possible 0000:01:00.0
May 01 16:01:14 arch kernel: PCI: Using ACPI for IRQ routing
May 01 16:01:14 arch kernel: PCI: pci_cache_line_size set to 64 bytes
May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0x0009f000-0x0009ffff]
May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xdd6f6000-0xdfffffff]
May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xdd705000-0xdfffffff]
May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddd20000-0xdfffffff]
May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddd28000-0xdfffffff]
May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddec5000-0xdfffffff]
May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddf13000-0xdfffffff]
May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddf3b000-0xdfffffff]
May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddf54000-0xdfffffff]
May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddf62000-0xdfffffff]
May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddf72000-0xdfffffff]
May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddf7e000-0xdfffffff]
May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddfaf000-0xdfffffff]
May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddfc0000-0xdfffffff]
May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddffc000-0xdfffffff]
May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddffe000-0xdfffffff]
May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xde002000-0xdfffffff]
May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xde01b000-0xdfffffff]
May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xde869000-0xdfffffff]
May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xdecbf000-0xdfffffff]
May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xdf000000-0xdfffffff]
May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0x21f400000-0x21fffffff]
May 01 16:01:14 arch kernel: NetLabel: Initializing
May 01 16:01:14 arch kernel: NetLabel: domain hash size = 128
May 01 16:01:14 arch kernel: NetLabel: protocols = UNLABELED CIPSOv4
May 01 16:01:14 arch kernel: NetLabel: unlabeled traffic allowed by default
May 01 16:01:14 arch kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
May 01 16:01:14 arch kernel: hpet0: 8 comparators, 64-bit 14.318180 MHz counter
May 01 16:01:14 arch kernel: Switched to clocksource hpet
May 01 16:01:14 arch kernel: pnp: PnP ACPI init
May 01 16:01:14 arch kernel: ACPI: bus type PNP registered
May 01 16:01:14 arch kernel: system 00:00: [mem 0xfed40000-0xfed44fff] has been reserved
May 01 16:01:14 arch kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
May 01 16:01:14 arch kernel: pnp 00:01: [dma 4]
May 01 16:01:14 arch kernel: pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
May 01 16:01:14 arch kernel: pnp 00:02: Plug and Play ACPI device, IDs INT0800 (active)
May 01 16:01:14 arch kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active)
May 01 16:01:14 arch kernel: system 00:04: [io 0x0680-0x069f] has been reserved
May 01 16:01:14 arch kernel: system 00:04: [io 0x1000-0x100f] has been reserved
May 01 16:01:14 arch kernel: system 00:04: [io 0xffff] has been reserved
May 01 16:01:14 arch kernel: system 00:04: [io 0xffff] has been reserved
May 01 16:01:14 arch kernel: system 00:04: [io 0x0400-0x0453] could not be reserved
May 01 16:01:14 arch kernel: system 00:04: [io 0x0458-0x047f] has been reserved
May 01 16:01:14 arch kernel: system 00:04: [io 0x0500-0x057f] has been reserved
May 01 16:01:14 arch kernel: system 00:04: [io 0x164e-0x164f] has been reserved
May 01 16:01:14 arch kernel: system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
May 01 16:01:14 arch kernel: pnp 00:05: Plug and Play ACPI device, IDs PNP0b00 (active)
May 01 16:01:14 arch kernel: system 00:06: [io 0x0454-0x0457] has been reserved
May 01 16:01:14 arch kernel: system 00:06: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
May 01 16:01:14 arch kernel: system 00:07: [io 0x04d0-0x04d1] has been reserved
May 01 16:01:14 arch kernel: system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
May 01 16:01:14 arch kernel: pnp 00:08: Plug and Play ACPI device, IDs PNP0c04 (active)
May 01 16:01:14 arch kernel: system 00:09: [io 0x0240-0x0259] has been reserved
May 01 16:01:14 arch kernel: system 00:09: Plug and Play ACPI device, IDs PNP0c02 (active)
May 01 16:01:14 arch kernel: pnp 00:0a: Plug and Play ACPI device, IDs ETD0101 SYN0a00 SYN0002 PNP0f03 PNP0f13 PNP0f12 (active)
May 01 16:01:14 arch kernel: pnp 00:0b: Plug and Play ACPI device, IDs ATK3001 PNP030b (active)
May 01 16:01:14 arch kernel: system 00:0c: [mem 0xfed1c000-0xfed1ffff] has been reserved
May 01 16:01:14 arch kernel: system 00:0c: [mem 0xfed10000-0xfed17fff] has been reserved
May 01 16:01:14 arch kernel: system 00:0c: [mem 0xfed18000-0xfed18fff] has been reserved
May 01 16:01:14 arch kernel: system 00:0c: [mem 0xfed19000-0xfed19fff] has been reserved
May 01 16:01:14 arch kernel: system 00:0c: [mem 0xf8000000-0xfbffffff] has been reserved
May 01 16:01:14 arch kernel: system 00:0c: [mem 0xfed20000-0xfed3ffff] has been reserved
May 01 16:01:14 arch kernel: system 00:0c: [mem 0xfed90000-0xfed93fff] has been reserved
May 01 16:01:14 arch kernel: system 00:0c: [mem 0xfed45000-0xfed8ffff] has been reserved
May 01 16:01:14 arch kernel: system 00:0c: [mem 0xff000000-0xffffffff] has been reserved
May 01 16:01:14 arch kernel: system 00:0c: [mem 0xfee00000-0xfeefffff] could not be reserved
May 01 16:01:14 arch kernel: system 00:0c: Plug and Play ACPI device, IDs PNP0c02 (active)
May 01 16:01:14 arch kernel: pnp: PnP ACPI: found 13 devices
May 01 16:01:14 arch kernel: ACPI: bus type PNP unregistered
May 01 16:01:14 arch kernel: pci 0000:00:1c.4: bridge window [io 0x1000-0x0fff] to [bus 05] add_size 1000
May 01 16:01:14 arch kernel: pci 0000:00:1c.4: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 05] add_size 200000
May 01 16:01:14 arch kernel: pci 0000:00:1c.4: bridge window [mem 0x00100000-0x000fffff] to [bus 05] add_size 200000
May 01 16:01:14 arch kernel: pci 0000:00:1c.4: res[14]=[mem 0x00100000-0x000fffff] get_res_add_size add_size 200000
May 01 16:01:14 arch kernel: pci 0000:00:1c.4: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_size add_size 200000
May 01 16:01:14 arch kernel: pci 0000:00:1c.4: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
May 01 16:01:14 arch kernel: pci 0000:00:1c.4: BAR 14: assigned [mem 0xdfc00000-0xdfdfffff]
May 01 16:01:14 arch kernel: pci 0000:00:1c.4: BAR 15: assigned [mem 0xdfe00000-0xdfffffff 64bit pref]
May 01 16:01:14 arch kernel: pci 0000:00:1c.4: BAR 13: assigned [io 0x2000-0x2fff]
May 01 16:01:14 arch kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
May 01 16:01:14 arch kernel: pci 0000:00:01.0: bridge window [io 0xe000-0xefff]
May 01 16:01:14 arch kernel: pci 0000:00:01.0: bridge window [mem 0xf6000000-0xf70fffff]
May 01 16:01:14 arch kernel: pci 0000:00:01.0: bridge window [mem 0xe0000000-0xf1ffffff 64bit pref]
May 01 16:01:14 arch kernel: pci 0000:00:1c.0: PCI bridge to [bus 02]
May 01 16:01:14 arch kernel: pci 0000:00:1c.1: PCI bridge to [bus 03]
May 01 16:01:14 arch kernel: pci 0000:00:1c.1: bridge window [mem 0xf7200000-0xf72fffff]
May 01 16:01:14 arch kernel: pci 0000:00:1c.3: PCI bridge to [bus 04]
May 01 16:01:14 arch kernel: pci 0000:00:1c.3: bridge window [io 0xd000-0xdfff]
May 01 16:01:14 arch kernel: pci 0000:00:1c.3: bridge window [mem 0xf7100000-0xf71fffff]
May 01 16:01:14 arch kernel: pci 0000:00:1c.4: PCI bridge to [bus 05]
May 01 16:01:14 arch kernel: pci 0000:00:1c.4: bridge window [io 0x2000-0x2fff]
May 01 16:01:14 arch kernel: pci 0000:00:1c.4: bridge window [mem 0xdfc00000-0xdfdfffff]
May 01 16:01:14 arch kernel: pci 0000:00:1c.4: bridge window [mem 0xdfe00000-0xdfffffff 64bit pref]
May 01 16:01:14 arch kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
May 01 16:01:14 arch kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
May 01 16:01:14 arch kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
May 01 16:01:14 arch kernel: pci_bus 0000:00: resource 7 [mem 0x000d0000-0x000d3fff]
May 01 16:01:14 arch kernel: pci_bus 0000:00: resource 8 [mem 0x000d4000-0x000d7fff]
May 01 16:01:14 arch kernel: pci_bus 0000:00: resource 9 [mem 0x000d8000-0x000dbfff]
May 01 16:01:14 arch kernel: pci_bus 0000:00: resource 10 [mem 0x000dc000-0x000dffff]
May 01 16:01:14 arch kernel: pci_bus 0000:00: resource 11 [mem 0xdfc00000-0xfeafffff]
May 01 16:01:14 arch kernel: pci_bus 0000:01: resource 0 [io 0xe000-0xefff]
May 01 16:01:14 arch kernel: pci_bus 0000:01: resource 1 [mem 0xf6000000-0xf70fffff]
May 01 16:01:14 arch kernel: pci_bus 0000:01: resource 2 [mem 0xe0000000-0xf1ffffff 64bit pref]
May 01 16:01:14 arch kernel: pci_bus 0000:03: resource 1 [mem 0xf7200000-0xf72fffff]
May 01 16:01:14 arch kernel: pci_bus 0000:04: resource 0 [io 0xd000-0xdfff]
May 01 16:01:14 arch kernel: pci_bus 0000:04: resource 1 [mem 0xf7100000-0xf71fffff]
May 01 16:01:14 arch kernel: pci_bus 0000:05: resource 0 [io 0x2000-0x2fff]
May 01 16:01:14 arch kernel: pci_bus 0000:05: resource 1 [mem 0xdfc00000-0xdfdfffff]
May 01 16:01:14 arch kernel: pci_bus 0000:05: resource 2 [mem 0xdfe00000-0xdfffffff 64bit pref]
May 01 16:01:14 arch kernel: NET: Registered protocol family 2
May 01 16:01:14 arch kernel: TCP established hash table entries: 65536 (order: 7, 524288 bytes)
May 01 16:01:14 arch kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
May 01 16:01:14 arch kernel: TCP: Hash tables configured (established 65536 bind 65536)
May 01 16:01:14 arch kernel: TCP: reno registered
May 01 16:01:14 arch kernel: UDP hash table entries: 4096 (order: 5, 131072 bytes)
May 01 16:01:14 arch kernel: UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
May 01 16:01:14 arch kernel: NET: Registered protocol family 1
May 01 16:01:14 arch kernel: pci 0000:01:00.0: Boot video device
May 01 16:01:14 arch kernel: PCI: CLS 64 bytes, default 64
May 01 16:01:14 arch kernel: Unpacking initramfs...
May 01 16:01:14 arch kernel: Freeing initrd memory: 3128K (ffff8800379d4000 - ffff880037ce2000)
May 01 16:01:14 arch kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
May 01 16:01:14 arch kernel: software IO TLB [mem 0xce76c000-0xd276c000] (64MB) mapped at [ffff8800ce76c000-ffff8800d276bfff]
May 01 16:01:14 arch kernel: RAPL PMU detected, hw unit 2^-16 Joules, API unit is 2^-32 Joules, 3 fixed counters 163840 ms ovfl timer
May 01 16:01:14 arch kernel: Scanning for low memory corruption every 60 seconds
May 01 16:01:14 arch kernel: futex hash table entries: 2048 (order: 5, 131072 bytes)
May 01 16:01:14 arch kernel: HugeTLB registered 2 MB page size, pre-allocated 0 pages
May 01 16:01:14 arch kernel: zbud: loaded
May 01 16:01:14 arch kernel: VFS: Disk quotas dquot_6.5.2
May 01 16:01:14 arch kernel: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
May 01 16:01:14 arch kernel: msgmni has been set to 15880
May 01 16:01:14 arch kernel: Key type big_key registered
May 01 16:01:14 arch kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
May 01 16:01:14 arch kernel: io scheduler noop registered
May 01 16:01:14 arch kernel: io scheduler deadline registered
May 01 16:01:14 arch kernel: io scheduler cfq registered (default)
May 01 16:01:14 arch kernel: pcieport 0000:00:01.0: irq 40 for MSI/MSI-X
May 01 16:01:14 arch kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
May 01 16:01:14 arch kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
May 01 16:01:14 arch kernel: efifb: probing for efifb
May 01 16:01:14 arch kernel: efifb: framebuffer at 0xf1000000, mapped to 0xffffc90004e80000, using 1920k, total 1920k
May 01 16:01:14 arch kernel: efifb: mode is 800x600x32, linelength=3200, pages=1
May 01 16:01:14 arch kernel: efifb: scrolling: redraw
May 01 16:01:14 arch kernel: efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
May 01 16:01:14 arch kernel: Console: switching to colour frame buffer device 100x37
May 01 16:01:14 arch kernel: fb0: EFI VGA frame buffer device
May 01 16:01:14 arch kernel: intel_idle: MWAIT substates: 0x21120
May 01 16:01:14 arch kernel: intel_idle: v0.4 model 0x3A
May 01 16:01:14 arch kernel: intel_idle: lapic_timer_reliable_states 0xffffffff
May 01 16:01:14 arch kernel: GHES: HEST is not enabled!
May 01 16:01:14 arch kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
May 01 16:01:14 arch kernel: Linux agpgart interface v0.103
May 01 16:01:14 arch kernel: rtc_cmos 00:05: RTC can wake from S4
May 01 16:01:14 arch kernel: rtc_cmos 00:05: rtc core: registered rtc_cmos as rtc0
May 01 16:01:14 arch kernel: rtc_cmos 00:05: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
May 01 16:01:14 arch kernel: Intel P-state driver initializing.
May 01 16:01:14 arch kernel: Intel pstate controlling: cpu 0
May 01 16:01:14 arch kernel: Intel pstate controlling: cpu 1
May 01 16:01:14 arch kernel: Intel pstate controlling: cpu 2
May 01 16:01:14 arch kernel: Intel pstate controlling: cpu 3
May 01 16:01:14 arch kernel: Intel pstate controlling: cpu 4
May 01 16:01:14 arch kernel: Intel pstate controlling: cpu 5
May 01 16:01:14 arch kernel: Intel pstate controlling: cpu 6
May 01 16:01:14 arch kernel: Intel pstate controlling: cpu 7
May 01 16:01:14 arch kernel: ledtrig-cpu: registered to indicate activity on CPUs
May 01 16:01:14 arch kernel: TCP: cubic registered
May 01 16:01:14 arch kernel: NET: Registered protocol family 10
May 01 16:01:14 arch kernel: NET: Registered protocol family 17
May 01 16:01:14 arch kernel: registered taskstats version 1
May 01 16:01:14 arch kernel: Magic number: 14:512:29
May 01 16:01:14 arch kernel: rtc_cmos 00:05: setting system clock to 2014-05-01 14:01:11 UTC (1398952871)
May 01 16:01:14 arch kernel: PM: Hibernation image not present or could not be loaded.
May 01 16:01:14 arch kernel: Freeing unused kernel memory: 1120K (ffffffff818d8000 - ffffffff819f0000)
May 01 16:01:14 arch kernel: Write protecting the kernel read-only data: 8192k
May 01 16:01:14 arch kernel: Freeing unused kernel memory: 904K (ffff88000151e000 - ffff880001600000)
May 01 16:01:14 arch kernel: Freeing unused kernel memory: 416K (ffff880001798000 - ffff880001800000)
May 01 16:01:14 arch kernel: random: systemd-tmpfile urandom read with 1 bits of entropy available
May 01 16:01:14 arch systemd-udevd[77]: starting version 212
May 01 16:01:14 arch kernel: i8042: PNP: PS/2 Controller [PNP030b:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
May 01 16:01:14 arch kernel: ACPI: bus type USB registered
May 01 16:01:14 arch kernel: usbcore: registered new interface driver usbfs
May 01 16:01:14 arch kernel: usbcore: registered new interface driver hub
May 01 16:01:14 arch kernel: usbcore: registered new device driver usb
May 01 16:01:14 arch kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controlle

There are actually a couple of other topics about this issue. If you are looking for an answer as to what the problem is, then nobody seem to be able to provide an answer. Nvidia claim it is a bug in the kernel acpi calls, but have not been forthcoming to explain that further. There is a lengthy topic on nvidia forums.
However, for a way to get things working again, read this topic: https://bbs.archlinux.org/viewtopic.php?id=180085

Similar Messages

  • I have big problems with mountain lion. you can not have a boot disk system I resulted in the need to re-download the os from scratch impiegandoci 8 hours, it is outrageous even with windows 95.

    I have big problems with mountain lion. you can not have a boot disk system I resulted in the need to re-download the os from scratch impiegandoci 8 hours, it is outrageous even with windows 95.
    at least that the operator has confirmed to me that he called me. I also have problems with either the start of the mac with the power off. I can not understand if it crashes or is just very very slow.
    Finally, I have a problem with the external hard disck. I often said to have been ejected incorrectly (not true) and I start to restore the startup recovery disk because disk utility is ineffective from the normal operating system .. is a shocking thing, but how you reduced. in four years it had never happened. seem to have windows or worse. Wake up.
    I am an Italian, alas, and then I would like an answer to my language because my € are the same as German French or English.

    You are on Windows 2000, you do not have a "Firefox" button, and should consider yourself to be fortunate in that you still have menus and don't have to do anything to get the menus back instead of the "Firefox" button. (The same applies to Windows XP users).
    Use the "File" menu to get to Import. You are not on Windows 7 or Vista, and don't have to put up with the nonsense added for Aero.
    If you want the "Firefox" button you can get it with View -> toolbars -> (uncheck) Menu Bar. The menu bar and the "Firefox" button were supposed to be mutually exclusive (which is impossible in some cases without being incompatible).
    Once you are using the "Firefox" button ...
    Use the "Alt" key to view the menu bar (temporarily) containing File, Edit, View, History, Bookmarks, Tools, and Help. On Windows 7 and Vista, the menu bar was hidden by default in Firefox 4 and above. These menu items are more or less available under the "Firefox" button which has the most used of the built-in Firefox menu items available in a different format.
    To get back to having menus again. "Firefox" button -> Options (second column) -> (check) Menu Bar
    You can make '''Firefox 7.0.1''' look like Firefox 3.6.*, see numbered '''items 1-10''' in the following topic [http://dmcritchie.mvps.org/firefox/firefox-problems.htm#fx4interface Fix Firefox 4.0 toolbar user interface, problems (Make Firefox 4.0 thru 8.0, look like 3.6)]. ''Whether or not you make changes, you should be aware of what has changed and what you have to do to use changed or missing features.''
    * http://dmcritchie.mvps.org/firefox/firefox-problems.htm#fx4interface

  • Image creation with MDT task sequence- "Windows has recovered from an unexpected shutdown"

    I'm using MDT 2012 U1 to build and capture a Windows 7 x86 image for deployment with ConfigMgr 2012 SP1.  I'm using the standard client task sequence in MDT.
    The MDT task sequence consistently fails after the reboot in the "Postinstall" group.  The install OS, Copy Scripts, Configure, Inject Drivers, Next Phase, and Restart Computer tasks all execute successfully, then the MDT-initiated reboot
    completes successfully.  There is nothing else helpful in the SMSTS.LOG, these are the last entries in the log:
    Successfully complete the action (Restart Computer) with the exit win32 code 0
    Sending status message
    Executing in non SMS standalone mode.  Ignoring send a task execution status message request
    Set a global environment variable _SMSTSLastActionRetCode=0
    Set a global environment variable _SMSTSLastActionSucceeded=true
    Expand a string %_SMSTSMDataPath%\Logs
    Deleting file without retrying
    The error message on the reference computer says, "Windows has recovered from an unexpected shutdown" along with "An existing in-progress deployment was found but is not in an expected state.  Would you like to ignore this in-progress
    deployment and start a new one?"
    I have found one post that suggested modifying customsettings.ini with  HideShell=Yes, which I tried.  It didn't help.
    I am not sure why MDT thinks the reboot was unexpected?  Has anybody run into this?  What steps can I take to narrow down the problem?
    Any help/suggestions are appreciated.
    Thanks,
    FP

    Thanks for your reply Phil.
    Setuperr.log is empty, zero bytes.  Setupact.log looks good to me, it has these entries at the end:
    OrchestrateUpdateImageState: Updating image state from [IMAGE_STATE_UNDEPLOYABLE] --> [Image_State_Complete]
    OOBELdr.exe exiting with code [0x0]...
    Process exited with exit code [0x0]
    c:\windows\panther\SetupInfo succeeded.
    c:\windows\panther\setupinfo.
    Windeploy.exe exiting with code [0x0]
    SetupSQM Started
    Panther path is C:\windows\Panther
    SQM not opted in
    SetupSQM is finished
    Our image environment was created during an MCS Engagement, so we have the solution pack and there are many variables in customsettings.ini.  I will need to find out how to narrow this down but I'm not finding a log file that tells me where it's choking... 
    Any suggestions are appreciated.
    Thanks,
    FP

  • The operation of my computer (Mac OS X 10.6.8) has been frequently interrupted by an unexpected shutdown. How to solve the problem?

    Dear Sirs, owners and managers
    Apple Support:
    I appreciate the opportunity given to request either always valuable assistance of masters.
    It happens that I have been supporting, for some time, inopportune and unexpected shutdowns
    of my Mac, with losses mounting and haul what I write in TextEdit.
    I ask, in this situation indigestible, a help of you to resolve this anomaly and thus be able to
    take back a firm and smooth operation of the MAC.
    Sincerely,
    Ricardo Cutolo

    Given your problem statement:
    inopportune and unexpected shutdowns of my Mac
    Unexpected hard shutdowns are usually either severe operating system corruptions, or they're triggered by hardware errors.   Bad memory, bad processors, bad power, bad disk, bad main board, etc.
    A likely first step is to archive (back up) your data onto an external disk.  Get a good backup. 
    After that (and possibly a second, verified, external-disk backup), check your system log for any potential clues that might be logged there.   If there is nothing obvious, then ensure that all external devices (other than a keyboard and mouse) are disconnected, and see if the problems persist. 
    If you continue to have problems, then you'll likely have to boot the DVD installer dis and use Disk Utility to wipe the disk, and reinstall Mac OS X Snow Leopard onto the disk, and migrate your archive back in as part of the installation. 
    If the problems persist after the reinstallation, then it's probably a hardware error with whichever Mac is involved here.  If this is a new Mac or under support, call Apple support and see what they have to say.  If you have a local Apple store, you'll check with the folks at the Genius Bar for assistance.

  • Re: Windows Server 2008 R2 guest unexpected shutdown

    Hi,
    I originally attempted to hijack an old abandoned forum thread to ask my question. I wasn't contributing to the original poster's issue but have a concern of my own.
    That thread from 2011 was:
    Windows Server 2008 R2 guest unexpected shutdown
    and my post has been split away from the hijacked thread to let it stand on its own.
    My question is ...
    Any update on this? I'm having this issue using the Intel Driver. I was told by Oracle support to use the PV Drivers and once I install the drivers, the window server does a Blue Screen. Please Help.
    Thank you
    Devon
    Here is an example of the vm,cfg.
    acpi = 1
    apic = 1
    boot = 'd'
    builder = 'hvm'
    device_model = '/usr/lib/xen/bin/qemu-dm'
    disk = ['phy:/dev/mapper/mpath11,hda,w',
    'file:/var/ovs/mount/B8B69E5B1F134F67869CEF8FF85AFEF9/iso_pool/win2008r2/win2008R2sp1.iso,hdc:cdrom,r',
    kernel = '/usr/lib/xen/boot/hvmloader'
    keymap = 'en-us'
    memory = '16000'
    name = 'xxxxxxx'
    on_crash = 'restart'
    on_reboot = 'restart'
    os_variant = 'vista'
    pae = 1
    serial = 'pty'
    timer_mode = 1
    usbdevice = 'tablet'
    uuid = '26447494-7950-8ef1-f6cd-c0327bb62e06'
    vcpus = 8
    cpus = '16-23'
    vif = ['mac=00:16:3E:78:6F:4D, bridge=xenbr0']
    vnc = 1
    vncconsole = 1
    vnclisten = '0.0.0.0'
    vncpasswd = ''
    vncunused = 1

    user10413801 wrote:
    do you have any other suggestions, is this normal, is this a bug, have others complained about this?I'm not an expert on Windows guests, as I don't run any myself. It's not normal, but others have not complained about it and we do not have any open bugs. However, I don't know how to troubleshoot crashing Windows guests like you can with crashing Linux guests. Your best bet is to open an SR with Oracle Support, and perhaps also Microsoft support, so you can track down why the guest is crashing.

  • IPhoto unexpected shutdown - successful downloaded pictures now gone

    Picture download was successful, but within a minute of the download iPhoto unexpectedly shutdown. When I relaunched iPhoto, the pictures I downloaded were gone. The originals on the camera were deleted after the download. Is there any way of getting those pictures back?

    Try these in order - from best option on down...
    1. Do you have an up-to-date back up? If so, try copy the library6.iphoto file from the back up to the iPhoto Library (Right Click -> Show Package Contents) allowing it to overwrite the damaged file.
    2. Download iPhoto Library Manager and use its rebuild function. This will create a new library based on data in the albumdata.xml file. Not everything will be brought over - no slideshows, books or calendars, for instance - but it should get all your albums and keywords back.
    Because this process creates an entirely new library and leaves your old one untouched, it is non-destructive, and if you're not happy with the results you can simply return to your old one.
    3. If neither of these work then you'll need to create and populate a new library.
    To create and populate a new *iPhoto 08* library:
    Note this will give you a working library with the same Events and pictures as before, however, you will lose your albums, keywords, modified versions, books, calendars etc.
    In the iPhoto Preferences -> Events Uncheck the box at 'Imported Items from the Finder'
    Move the iPhoto Library to the desktop
    Launch iPhoto. It will ask if you wish to create a new Library. Say Yes.
    Go into the iPhoto Library (Right Click -> Show Package Contents) on your desktop and find the Originals folder. From the Originals folder drag the individual Event Folders to the iPhoto Window and it will recreate them in the new library.
    When you're sure all is well you can delete the iPhoto Library on your desktop.
    In the future, in addition to your usual back up routine, you might like to make a copy of the library6.iPhoto file whenever you have made changes to the library as protection against database corruption.
    Regards
    TD

  • SOLVED: K9A2 Platinuim= Unexpected shutdowns on medium load.

    Hello guys!
    This is my first message, I'm from argentina, and I regret this first is a cry for help.
    I've unexpected shutdowns on my system, (specs on the signature), and it happens when I use heavy open GL apps, like SecondLife (at maximum quality settings), Quake 4 (idem).
    It works wonderfully for a while and then BANG! shutdown, so so down, I've to actully turn off the PSU switch and then on again to be able to boot.
    At first I thought it was a temperature issue, but no, my system rarely go more than 50C even with the CPU at it's very full capacity (try a render on blender) for a long time.
    This is also strange, because I can have my CPU at 100% on each core for 5 hours and everything's peachy, BUT I play Quake 4 and 30 minutes or so later the computer shuts down.
    I read in the forum it could be also a weak PSU, and according to my numbers mine is extremely weak, so that explanation could be consistent with the demand of extra power the GPU needs on games.
    I visit the Nvidia forum and the only post remotely similar to my problem talks about the mother (k9a2).
    So the question is: Besides the obvious need of a better PSU... do I need to check something else?
    Oh!! one additional fact: playing games my Graphics board never climb to more than 60C
    Yes it's hot, but the default threshold for slowing the GPU down is 100C so I guess it's ok.
    Any ideas?
    Thank you very much in advance and excuse my crappy english 
    Edit: Issue solved see below.

    "So the question is: Besides the obvious need of a better PSU... do I need to check something else?"
    No, its the PSU for sure
    "Any ideas?"
    Go for normal, modern and better PSU
    For Good PSU suggestions and more info:
    https://forum-en.msi.com/index.php?topic=112039.msg836246#msg836246
    Some of those will be great choose:
    CORSAIR 450VX: http://www.newegg.com/Product/Product.aspx?Item=N82E16817139003
    CORSAIR 550VX: http://www.newegg.com/Product/Product.aspx?Item=N82E16817139004
    Corsair 650TX: http://www.newegg.com/Product/Product.aspx?Item=N82E16817139005
    Corsair 750TX: http://www.newegg.com/Product/Product.aspx?Item=N82E16817139006
    Add on to read:
    >>> PSU's---2 x 12v---The Dual Rail Myth <<<
    >>> Is your problem caused by your PSU? <<<

  • Unexpected shutdown

    Hi!  i have unexpected shutdown problem on my macbook pro.
    It happens every time, no matter wich software (programs) iam using at that moment, unexpectedly:
    display becoming black, but keyboard still have backlight (caps lock button does not work - lamp does not light), all buttons not working, indicator on the front edge (on the right side) is lit and not flashing. i can only push power button off.
    more simptoms
    unexpected shutdown happens:
    when i am using spase button for preview folders and files
    when i am using photoshop
    when i am using Spaces
    when i am opening Time Machine
    when i am reinstalling MacOS and trying set Time Zone
    when i am using/not using battery...
    after mac boot up or 10-30 min later - whatever, when i am using graphic effects - unexpected shutdown happens
    as example you can view my video on youtube: https://www.youtube.com/watch?v=Dyswi5McQ-U
    What i am already done:
    Reinstalled MacOS
    Changed hard drive
    Changed memory cards
    Resetted SMC
    Launched Diagnostic tools (no errors)
    Changed power adapter
    ... and unexpected shutdown still happening
    I think, all that because i have problems with my videocard(s). And I think that this is a manufacturing defect.
    How i can fix this problem? Can I fix it myself ?
    MacBook Pro 6,2 (15 inch, middle 2010)
    Intel Core i7 2.66
    DDR3 4GBx2 1067
    Video   NVIDIA GeForce GT 330M
               Intel HD
    EFI Boot ROM MBP61.0057.B0C
    SMC 1.58f17
    My Story:
    in late 2010 I bought my macbook pro in official shop (Beijing, China). I did not buy an extended warranty. After several month using, I came to the official service (Beijing, China), because I had some problems with usb. Genius man took my computer, and told me that Apple can repair the computer during a few days for free. It was necessary to replace the motherboard. Unfortunately, I did not have a few days those time, cause I had to go to another country. Therefore, I was given a receipt on which I can restore my computer the next time, when I have time. Then I flew to another country. For several years, I have not had the opportunity to come to the Apple store. During all this time, I had a problem with unexpected shutdown. After I came back to China, in 2014, i came to the oficcial service center again. Told my story. They told me that they knew that I appealed about this issue before, but they can not help me because my warranty is over. And i was offered to replace the motherboard for about 5,000 yuan. This is terrible. This repair cost more expensive than buying a new computer with a much more powerful specifications (other computer brands). I am very sad that I bought a new computer, for a long time, to work on it and was unable to use it several years. Now my laptop simply stored in a drawer. When I bought the computer from Apple company, I was hoping to get a quality assistant in my work and life. But I was deceived. I want you to understand me. I am the system administrator. I am working with computers every day. For my clients i always advising to buy Apple computers for the quality and usability. "Shoemaker without shoes" - I would say. I am disappointed with the quality and support. There is nothing worse that when your favorite company denies you.
    I know that Apple company launched "MacBook Pro Repair Extension Program for Video Issues", but only for MacBook Pro systems were sold between February 2011 and December 2013. Maybe this is a problem not only for computers released in 2011, but for 2010 too?

    Hello Durr, 
    Welcome to the forums. 
    In this case we can try to reload the software on the BlackBerry® smartphone to make sure it is running the latest version and there are no issues with the OS.
    Here is how to backup your BlackBerry smartphone http://bbry.lv/oPVWXc
    Once you have backed up your BlackBerry smartphone please follow the link below to complete a clean reload of the BlackBerry smartphone software.
    Link: http://www.blackberry.com/btsc/KB03621
    Once completed test it and proceed with a selective restore, here is how to restore http://bbry.lv/qgQxLo
    -SR
    Come follow your BlackBerry Technical Team on twitter! @BlackBerryHelp
    Be sure to click Kudos! for those who have helped you.Click Solution? for posts that have solved your issue(s)!

  • No Boot with AGP Card in Slot - 865 PE Neo2

    I have tried absolutely everything.
    My system will not power up when I have an AGP card in the AGP Slot.  I have tried 3 different AGP 8x video cards.  All with the same result -- the system fails to power up at all.
    When I take the card out of the AGP slot and just power up -- everything seems to go smoothly. (not that I would know since i can't see anything)  However, atleast it powers up.
    This Mobo doesn't have built in video.
    And I've never had one successful "power up" with a card in the AGP slot.
    Any suggestions or help?
    I'd greatly appreciate it.
    Justin

    Hmmm...I've posted my own message but...after reading this...I'm having the EXACT same problem. I cannot get the system to boot with any VGA card installed. If I take the card out, it boots but beeps 8 times when it gets to the video card part of the boot phase. Then it stops at some later phase (I believe the keyboard section). System specs are as follows...
    Intel P4 Northwood 1.8Ghz
    Gainward Powerpack Ultra 760TV/DVI (GeforceFX 5600 8X AGP)
    765PE Neo2 (like this guy above) MB
    PSU is a "DURO 400W Max"
    I don't know how to obtain other information you have asked for, such as "combined wattage". I can give you the amp ratings for the various voltages listed on the PSU...
    +3.3V 28A
    +5V   30A
    +12V  11A
    -5V   .5A
    -12V  .8A
    +5VSB  3A
    This was in a generic case we just got becuase the PSU was bad in the old one and my roommate seemed to think the button on the front of the old case could have been causing me trouble (?). Now if you are going to tell me the PSU is junk then you need to do a few things. First explain why. Tell me how to obtain the "combined watts" information and how knowing it is useful, and what it needs to be to support a system like this. Give your recommendations on reasonably priced PSUs that would provide enough power to run this system.
    If a PSU can have so much to do with preventing a system from starting, why don't MOBO and VGA Card makers list more specific requirements for PSUs than "System needs at least a 300W PSU"?
    I've been having problems getting a system running for months now, every since my original system shutdown one day and never started again. Since then I've been through  MOBOs 2 CPUs and 2 PSUs. This is the closest I've gotten, with the system starting but the bracket lights freezing at Video Card Initalizing.

  • T450s Docking Station Problems: Unexpected Shutdowns

    I recently got a T450s and I've been having issues docking/undocking the PC.  Generally, the issue is with undocking. I put it to sleep, wait for the "sleeping" red LED on the lid, then undock; upon opening the laptop a few minutes later (and pressing power), the PC is having a fresh boot.  Windows logs confirm this was an unexpected shutdown. In another instance - one off and potentially unrelated - the sleeping laptop was docked, and upon pressing power, I was greeted by a BIOS message asking me to check date/time.  I did - BIOS settings were wiped - date was 1/1/2001.  I noticed I had some static charge on me (not much though, summer time in Seattle) when I docked.  This particular issue has me wondering if also an ESD bug; I know certain T-series or W-series ThinkPads had issues 5-7 years ago docking station ESD issues. Regardless, this is big problem for me.  I can't reliably leave any documents open when undocking.  I updated to the latest BIOS and it still had the unexpected shutdown.  I am running W8.1. This is the log from the BIOS update:
    [2015/6/23 16:48:58]
    OS = Windows 8 64bit
    Driver Loading....Done
    System BIOS Version -> JBET48WW
    Applying BIOS Version -> JBET49WW
    System EC Version -> JBHT13WW
    Applying EC Version -> JBHT13WW
    AC adapter/Battery check....OK. Any help would be greatly appreciated!

    Hi Hemanth,Thanks for the suggestion.  I ran the utility and the only thing available for the ThinkPad Pro Dock (65 W) was a firmware update utility.  I ran the utility and it appears I have newer firmware than what's posted on the site.  See utility output below:CHIP ID: VMM2322
    CHIP version: A3
    Firmware version: 2.22.000Update to version: ver2.17.000!!! As such I did not run the update. That revision appears dated 2014 - is there something newer posted elsewhere? Thanks for the suggestion!David

  • Blue screen error "windows has recovered from a unexpected shutdown"

    Hi guys
    I am using laptop & everyday it will unexpectedly shutdown and shows Blue screen error "windows has recovered from a unexpected shutdown"...Pls help me to resolve this issue.
    Problem signature:
      Problem Event Name: BlueScreen
      OS Version: 6.1.7600.2.0.0.256.48
      Locale ID: 1033
    Additional information about the problem:
      BCCode: d1
      BCP1: 00000030
      BCP2: 00000002
      BCP3: 00000000
      BCP4: 8F2DA8A5
      OS Version: 6_1_7600
      Service Pack: 0_0
      Product: 256_1
    Files that help describe the problem:
      C:\Windows\Minidump\062614-23836-01.dmp
      C:\Users\Venkateshwara swamy\AppData\Local\Temp\WER-74552-0.sysdata.xml
    Read our privacy statement online:
      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
    If the online privacy statement is not available, please read our privacy statement offline:
      C:\Windows\system32\en-US\erofflps.txt

    It could be some driver compatibility issues.
    http://msdn.microsoft.com/en-us/library/windows/hardware/ff560244(v=vs.85).aspx
     http://blogs.technet.com/b/askcore/archive/2008/11/01/how-to-debug-kernel-mode-blue-screen-crashes-for-beginners.aspx
    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]
    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

  • Yosemite System Crashes on Boot with Dell U2713HM

    Previously under Mavericks I had no issue with a Dell U2713HM monitor and my 'non-stock' NVidia card.  (The reason I'm using the video card I am is because the stock ATI card (ATI Radeon HD 2600 XT) is known do fry itself which I discovered after replacing it with an identical card and having the 2nd one fry itself after a year.  I did a lot of research and settle don the card I now have because others had reported success with it.  It worked fine for nearly a year until updating to Yosemite.)
    After upgrading to Yosemite my system went into an infinite reboot loop on startup.  On a hunch, I swapped out my U2713HM for an old 17" monitor and was able to boot.  I can't even have the U2713HM plugged in/turned off using the second port on the card without the system crashing.  If I get the system booted using the 17", I can then plug in/turn on the U2713HM and set the resolution - at that point I can (sometimes) boot but it will then crash on shutdown triggering an automatic restart.
    Is anyone having any success with a U2713HM, and especially with an NVidia card?  The only option I haven't tried is a completely fresh, clean install.  Once the system boots, I get the dialog that it was restarted because of an issue and can view part of the dump info that will be sent to Apple -> that clearly indicates the issue is with the kernel/NVidia driver somewhere.
    System specs:  Mac Pro (Early 2008) with an NVidia GeForce GTX 650 1024MB card installed running Yosemite (OS X 10.10)

    My mac mini (late 2012, Yosemite installed) doesn't start with Dell U2713HM if the USB cable of the monitor is connected.
    No problems if I connect the usb-cable after successful startup. Also the usb-hub of the Dell is working fine then.

  • Biege G3 won't boot with OS 9.2

    I purchased a biege G3 MT with OS 8.6 on eBay. Unfortunately, the OS is in French. I upgraded that to OS 9.2 and now it won't boot. No chime and it stops after the first icon during startup. It won't boot with extensions off nor with the CD. I tried resetting pram, etc. without any luck. Loaded it with 8.5 and it works. Took another HD with 10.2 from another biege G3 and it works. It just doesn't like 9.2, but I have 9.2 running in another biege G3. Are there G3 that won't work with 9.2? Please help.
    biege g3   Mac OS 9.2.x  

    Hi elpro,
    Here's a bunch of stock responses you'll hear on the G3 forum.
    Is the 9.2 CD a universal installer (gold color), or a gray machine-specific CD, and if it is gray, is it the right one for your machine? Apple made gold CDs for general retail to work with all machines, and gray ones that were usually distributed with a machine with the components just for that machine. Unless you have a universal installer CD, the version of OS 9 you are trying to install may not have the right components for your system unless you happen to have one that matches your type of G3. If the 8.5 CD is the right one, and the OS X you say is from an identical machine then that may explain why they boot up but not your OS 9.
    If you post your problem on the G3 forum you'll almost be sure to get this question. How old is the battery in this machine? G3s exhibit all kinds of weird and unexpected symptoms when the batteries are weak, and they go through them pretty quickly, especially if they have been unplugged for a long time. The battery helps preserve basic machine configuration information between bootups so if you're having problems with your monitor it might even be related to the battery. If in doubt, replace the battery.
    The PRAM reset and extensions off are the other stock replies but you've tried those.
    Brian

  • KT4AV will not boot with SATA card installed and no SATA drive

    I put a Promise brand SATA II card in a KT4AV motherboard. There is an IDE drive and a DVD drive hooked up to the IDE1 port on the motherboard. That IDE drive has Windows XP Pro SP2 loaded on it.
    If I have a SATA drive plugged into the card, the machine works fine. If I remove the STAT drive and leave the card in, I cannot boot to Windows. If I remove the card, it works fine. The only time there is a problem is when the SATA card is plugged in and there is no drive on the SATA card.
    As one possible solution, I tried to boot to a Windows CD to reload Windows. It will not even allow me to reload from the CD, it says there is a file missing from the CD. If the SATA drive is hooked up, it will work fine on the CD. Also, I tried multiple CDs and they all give the same message. Because it makes a difference whether the SATA drive is connected or not, I do not believe the CD is the problem.
    I have tried looking on Promise's web site for a FAQ or an updated BIOS or for other information about this problem and I found nothing. I have e-mailed them and they did not reply yet.
    There is no reason to think this is the fault of the motherboard, but I wanted to see if anyone had any ideas about this problem. Because of the symptoms, I believe it also cannot be the CPU, memory, PSU, video card, etc. Sorry if that makes this post off topic.

    Quote from: HenryW on 16-March-07, 02:56:44
    Have you tried to disable card in Device Manager when you don't use it? What is the model number of the card you are using?
    It is a SATA 300 TX2, which means that it has two SATA ports and one IDE port. I have never used the IDE port, only one SATA.
    I have never tried to disable it, but I could try, just to see what it did. It sure would be a lot more work to disable and enable it so that isn't a good long term solution. Among other things, it would mean that I would have to boot up in order to remove the SATA drive. Since it won't boot with the drive removed, it will require more planning.
    Will post the results once I have tried. Still no reply from Promise :-(

  • Won't boot with external display connected

    My MacBook Pro (circa 1997) won't boot with the external display connected. I can connect the external display (20in flat planel) after it has started, and it works just fine.
    I have tried two different DVI cables (one of which I think is a DVI-A cable) and the DVI-to-VGA cable. The result is the same.
    During the boot phase I get the tone, the apple logo and the progress wheel. After 30 seconds to one minute those disappear to be replaced by an empty blue screen.

    In case anyone wonders, my "solution" was to change to a WB Elements Desktop 3TB (only USB 2.0 is currently available for this model). I miss the speed of USB 3.0, but it's much nicer to not have to remember to unplug and plug in the hard drive each time I boot.
    Still hoping to see a proper solution to this (since I don't have the WB My Book anymore, I can't test adaher's suggestion).

Maybe you are looking for