FX5600 TD128 sets monitor into standby

Hi all
I searched the existing threads and found some similiar issues but nothing that was exactly the same.
I formatted my drive and installed Xp with SP1a. Tried to install det. 53 from Nvidia and the monitor went into standby and didn't come on again. Installed 44 which came with the MSI FX5600 TD128 which worked. Then I installed 53 and XP was happy. Loaded Q3 and when I tried to run it the monitor went into standby.
Found a link on the net about disabling Enable Write Combining in driver properties and this sorted out the Q3 problems. Then this past weekend I was surfing the net and the monitor switched off. I then tried UT2004 demo and the game loaded but the minute I click on the settings menu the monitor hung again.
I got fedup and installed 2000 again. Q3, UT2004 and COD all run fine and my monitor isn't hanging.
What could be causing the vga/monitor problem in XP? Here are my system specs( at work at the moment so can't supply the PSU voltage):
AMD 900 Thunderbird
Asus A7V Pro KT133
512Mb PC133
20Gb Fujitsu 7200rpm
SBLive 5.1 DE
Accton 10/100
56K Modem
MSI FX5600 TD128
Viewsonic E70 17"
Sparkle 300w PSU
Thanks

I appear to have a similar problem with a FX5600 VTDR128  .  I have the latest updates to XP, main board bios and NVIDIA drivers loaded  (the problem was not any worse under the previous versions of the drivers).
Periodically, the screen goes blank. The blanking occurs in 3 forms, (1) things go blank for 2-3 seconds and then comes back, (2) the screen looses the signal entirely and the system continues to run but I have to reset and reboot; and (3) occasionally the whole system appears to be taken down by this process and reboots.
Thinking that it could be a power supply issue, I installed an ANTEC 550 true power supply (which is great  ) but it did not solve the problem.  I have also tried a number of voltage settings for both video and memory but they did not seem to change things either.
Any further suggestions would be appreciated  

Similar Messages

  • Putting the second Monitor into Standby IMac i7 Mid 2011

    Hello...
    Im trying to get my Eizo FlexScan 2431S into Standby... but its not working...
    The Imac Display shuts off, but the Eizo just (lightning) Black...
    Imac i7 3,4GHz mid2011, seems to be the "DDC" Signals...
    Any suggestions?
    cheers
    Einar

    sorry i missspelled...
    Eizo FlexScan S2431W

  • X11 won't start (sets monitor to standby) with nVidia card

    Hello everyone!
    I'm having some trouble getting my computer to work properly. Yesterday it was working perfectly, but today it would't start again. After some troubleshooting I've determined that the problem lies with X11 and the graphics driver. The bootloader, grub, and arch itself, boots perfectly in runlevel 3, but the moment you run "startx" it would appear to be loading for a while and finally the screen goes to standby mode and there is no way out of that other than reseting the computer using the reset button. I've tried uninstalling the nvidia drivers and installing nouveau drivers, but it still won't start X, this time arround, it would just hang up with a white screen.
    I've also tried removing xorg.conf and also using nvidia utility to generate a new one, but neither seems to work.
    /var/log/Xorg.0.log doesn't report any errors, it just gives different info from the configuration and the graphics card and just ends there.
    I've tried booting with a debian live USB but it would't boot either (the computer would just restart). I've also tried a Kubuntu live USB, this time arround, it would start to boot but the graphics appeared to be corrupted (strange colored noise all over the screen) and eventually it would just hang up. Using nomodeset Kubuntu finally booted (using vesa I guess?), but the same didn't work in Arch (I'm guessing because I have the nvidia drivers installed instead of nouveau).
    In conclussion, something appears to be wrong with the graphics card, I dont't know if it's a software problem or a hardware problem, as it started from one day to the other, without any upgrades in between, and it just doesn't work in any of the 3 distributions I've tested.
    Any suggestions in what to do to troubleshoot this?
    Thanks in advance,
    Santiago.-

    Xorg.0.log
    [ 35.560]
    X.Org X Server 1.14.4
    Release Date: 2013-10-31
    [ 35.560] X Protocol Version 11, Revision 0
    [ 35.560] Build Operating System: Linux 3.11.6-1-ARCH x86_64
    [ 35.561] Current Operating System: Linux arch 3.11.6-1-ARCH #1 SMP PREEMPT Fri Oct 18 23:22:36 CEST 2013 x86_64
    [ 35.561] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=17d019be-e01f-4c1c-ac50-69e1f3dc0592 rw quiet 3
    [ 35.562] Build Date: 01 November 2013 05:10:48PM
    [ 35.562]
    [ 35.562] Current version of pixman: 0.30.2
    [ 35.562] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 35.562] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 35.564] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Nov 4 21:35:07 2013
    [ 35.576] (==) Using config file: "/etc/X11/xorg.conf"
    [ 35.576] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 35.577] (==) ServerLayout "Layout0"
    [ 35.577] (**) |-->Screen "Screen0" (0)
    [ 35.577] (**) | |-->Monitor "Monitor0"
    [ 35.577] (**) | |-->Device "Device0"
    [ 35.577] (**) |-->Input Device "Keyboard0"
    [ 35.577] (**) |-->Input Device "Mouse0"
    [ 35.577] (==) Automatically adding devices
    [ 35.577] (==) Automatically enabling devices
    [ 35.577] (==) Automatically adding GPU devices
    [ 35.603] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 35.603] Entry deleted from font path.
    [ 35.603] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
    [ 35.603] Entry deleted from font path.
    [ 35.603] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 35.603] Entry deleted from font path.
    [ 35.603] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 35.604] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 35.604] Entry deleted from font path.
    [ 35.604] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 35.604] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/
    [ 35.604] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 35.604] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
    [ 35.604] (WW) Disabling Keyboard0
    [ 35.604] (WW) Disabling Mouse0
    [ 35.604] (II) Loader magic: 0x7fdc20
    [ 35.604] (II) Module ABI versions:
    [ 35.604] X.Org ANSI C Emulation: 0.4
    [ 35.604] X.Org Video Driver: 14.1
    [ 35.604] X.Org XInput driver : 19.1
    [ 35.604] X.Org Server Extension : 7.0
    [ 35.604] (II) xfree86: Adding drm device (/dev/dri/card0)
    [ 35.605] (--) PCI:*(0:1:0:0) 10de:0421:1682:2353 rev 161, Mem @ 0xfa000000/16777216, 0xd0000000/268435456, 0xf8000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/131072
    [ 35.606] Initializing built-in extension Generic Event Extension
    [ 35.606] Initializing built-in extension SHAPE
    [ 35.606] Initializing built-in extension MIT-SHM
    [ 35.606] Initializing built-in extension XInputExtension
    [ 35.606] Initializing built-in extension XTEST
    [ 35.607] Initializing built-in extension BIG-REQUESTS
    [ 35.607] Initializing built-in extension SYNC
    [ 35.607] Initializing built-in extension XKEYBOARD
    [ 35.607] Initializing built-in extension XC-MISC
    [ 35.608] Initializing built-in extension SECURITY
    [ 35.608] Initializing built-in extension XINERAMA
    [ 35.608] Initializing built-in extension XFIXES
    [ 35.608] Initializing built-in extension RENDER
    [ 35.608] Initializing built-in extension RANDR
    [ 35.609] Initializing built-in extension COMPOSITE
    [ 35.609] Initializing built-in extension DAMAGE
    [ 35.609] Initializing built-in extension MIT-SCREEN-SAVER
    [ 35.609] Initializing built-in extension DOUBLE-BUFFER
    [ 35.619] Initializing built-in extension RECORD
    [ 35.629] Initializing built-in extension DPMS
    [ 35.638] Initializing built-in extension X-Resource
    [ 35.647] Initializing built-in extension XVideo
    [ 35.656] Initializing built-in extension XVideo-MotionCompensation
    [ 35.665] Initializing built-in extension XFree86-VidModeExtension
    [ 35.673] Initializing built-in extension XFree86-DGA
    [ 35.682] Initializing built-in extension XFree86-DRI
    [ 35.690] Initializing built-in extension DRI2
    [ 35.690] (II) LoadModule: "glx"
    [ 35.757] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 36.111] (II) Module glx: vendor="NVIDIA Corporation"
    [ 36.111] compiled for 4.0.2, module version = 1.0.0
    [ 36.111] Module class: X.Org Server Extension
    [ 36.111] (II) NVIDIA GLX Module 325.15 Wed Jul 31 18:12:00 PDT 2013
    [ 36.126] Loading extension GLX
    [ 36.126] (II) LoadModule: "nvidia"
    [ 36.136] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
    [ 36.195] (II) Module nvidia: vendor="NVIDIA Corporation"
    [ 36.195] compiled for 4.0.2, module version = 1.0.0
    [ 36.195] Module class: X.Org Video Driver
    [ 36.197] (II) NVIDIA dlloader X Driver 325.15 Wed Jul 31 17:50:57 PDT 2013
    [ 36.197] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    [ 36.197] (--) using VT number 2
    [ 36.248] (II) Loading sub module "fb"
    [ 36.248] (II) LoadModule: "fb"
    [ 36.259] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 36.270] (II) Module fb: vendor="X.Org Foundation"
    [ 36.270] compiled for 1.14.4, module version = 1.0.0
    [ 36.270] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 36.270] (WW) Unresolved symbol: fbGetGCPrivateKey
    [ 36.270] (II) Loading sub module "wfb"
    [ 36.270] (II) LoadModule: "wfb"
    [ 36.270] (II) Loading /usr/lib/xorg/modules/libwfb.so
    [ 36.271] (II) Module wfb: vendor="X.Org Foundation"
    [ 36.271] compiled for 1.14.4, module version = 1.0.0
    [ 36.271] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 36.271] (II) Loading sub module "shadow"
    [ 36.271] (II) LoadModule: "shadow"
    [ 36.271] (II) Loading /usr/lib/xorg/modules/libshadow.so
    [ 36.272] (II) Module shadow: vendor="X.Org Foundation"
    [ 36.272] compiled for 1.14.4, module version = 1.1.0
    [ 36.272] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 36.272] (II) Loading sub module "ramdac"
    [ 36.272] (II) LoadModule: "ramdac"
    [ 36.272] (II) Module "ramdac" already built-in
    [ 36.274] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
    [ 36.274] (==) NVIDIA(0): RGB weight 888
    [ 36.274] (==) NVIDIA(0): Default visual is TrueColor
    [ 36.274] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
    [ 36.274] (**) NVIDIA(0): Option "UseEdidDpi" "False"
    [ 36.274] (**) NVIDIA(0): Option "DPI" "96 x 96"
    [ 36.274] (**) NVIDIA(0): Enabling 2D acceleration
    [ 50.151] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20130102)
    [ 50.256] (II) NVIDIA(GPU-0): Display (Samsung SMB2330H (CRT-0)) does not support NVIDIA 3D
    [ 50.256] (II) NVIDIA(GPU-0): Vision stereo.
    [ 50.256] (II) NVIDIA(0): NVIDIA GPU GeForce 8500 GT (G86) at PCI:1:0:0 (GPU-0)
    [ 50.256] (--) NVIDIA(0): Memory: 1048576 kBytes
    [ 50.256] (--) NVIDIA(0): VideoBIOS: 60.86.41.00.85
    [ 50.256] (II) NVIDIA(0): Detected PCI Express Link width: 16X
    journalctl -xb
    -- Logs begin at Sat 2013-08-17 21:55:41 ART, end at Mon 2013-11-04 22:01:35 ART. --
    Nov 04 21:59:09 arch systemd-journal[120]: Runtime journal is using 364.0K (max 100.1M, leaving 150.2M of free 1001.3M, current limit 100.1M).
    Nov 04 21:59:09 arch systemd-journal[120]: Runtime journal is using 368.0K (max 100.1M, leaving 150.2M of free 1001.3M, current limit 100.1M).
    Nov 04 21:59:09 arch kernel: Initializing cgroup subsys cpuset
    Nov 04 21:59:09 arch kernel: Initializing cgroup subsys cpu
    Nov 04 21:59:09 arch kernel: Initializing cgroup subsys cpuacct
    Nov 04 21:59:09 arch kernel: Linux version 3.11.6-1-ARCH (nobody@var-lib-archbuild-extra-x86_64-thomas) (gcc version 4.8.1 20130725 (prerelease) (GCC) ) #1 SMP PREEMPT Fri Oct 18 23:22:36 CEST 2013
    Nov 04 21:59:09 arch kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=17d019be-e01f-4c1c-ac50-69e1f3dc0592 rw quiet 3
    Nov 04 21:59:09 arch kernel: e820: BIOS-provided physical RAM map:
    Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
    Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
    Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
    Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x0000000000100000-0x000000007fbb4fff] usable
    Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x000000007fbb5000-0x000000007fbf7fff] ACPI NVS
    Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x000000007fbf8000-0x000000007fd4bfff] reserved
    Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x000000007fd4c000-0x000000007fd51fff] ACPI data
    Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x000000007fd52000-0x000000007fd52fff] ACPI NVS
    Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x000000007fd53000-0x000000007fd54fff] ACPI data
    Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x000000007fd55000-0x000000007fd56fff] ACPI NVS
    Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x000000007fd57000-0x000000007fd57fff] reserved
    Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x000000007fd58000-0x000000007fd5bfff] ACPI NVS
    Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x000000007fd5c000-0x000000007fd6afff] reserved
    Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x000000007fd6b000-0x000000007fefffff] usable
    Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
    Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x00000000ffa00000-0x00000000ffbfffff] reserved
    Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x00000000ffe00000-0x00000000ffffffff] reserved
    Nov 04 21:59:09 arch kernel: NX (Execute Disable) protection: active
    Nov 04 21:59:09 arch kernel: SMBIOS 2.4 present.
    Nov 04 21:59:09 arch kernel: DMI: /DG31PR, BIOS PRG3110H.86A.0071.2010.0318.1704 03/18/2010
    Nov 04 21:59:09 arch kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
    Nov 04 21:59:09 arch kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
    Nov 04 21:59:09 arch kernel: No AGP bridge found
    Nov 04 21:59:09 arch kernel: e820: last_pfn = 0x7ff00 max_arch_pfn = 0x400000000
    Nov 04 21:59:09 arch kernel: MTRR default type: uncachable
    Nov 04 21:59:09 arch kernel: MTRR fixed ranges enabled:
    Nov 04 21:59:09 arch kernel: 00000-9FFFF write-back
    Nov 04 21:59:09 arch kernel: A0000-E7FFF uncachable
    Nov 04 21:59:09 arch kernel: E8000-FFFFF write-protect
    Nov 04 21:59:09 arch kernel: MTRR variable ranges enabled:
    Nov 04 21:59:09 arch kernel: 0 base 000000000 mask F80000000 write-back
    Nov 04 21:59:09 arch kernel: 1 base 07FF00000 mask FFFF00000 uncachable
    Nov 04 21:59:09 arch kernel: 2 disabled
    Nov 04 21:59:09 arch kernel: 3 disabled
    Nov 04 21:59:09 arch kernel: 4 disabled
    Nov 04 21:59:09 arch kernel: 5 disabled
    Nov 04 21:59:09 arch kernel: 6 disabled
    Nov 04 21:59:09 arch kernel: 7 disabled
    Nov 04 21:59:09 arch kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    Nov 04 21:59:09 arch kernel: found SMP MP-table at [mem 0x000fc620-0x000fc62f] mapped at [ffff8800000fc620]
    Nov 04 21:59:09 arch kernel: Scanning 1 areas for low memory corruption
    Nov 04 21:59:09 arch kernel: Base memory trampoline at [ffff880000099000] 99000 size 24576
    Nov 04 21:59:09 arch kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
    Nov 04 21:59:09 arch kernel: [mem 0x00000000-0x000fffff] page 4k
    Nov 04 21:59:09 arch kernel: BRK [0x01b2f000, 0x01b2ffff] PGTABLE
    Nov 04 21:59:09 arch kernel: BRK [0x01b30000, 0x01b30fff] PGTABLE
    Nov 04 21:59:09 arch kernel: BRK [0x01b31000, 0x01b31fff] PGTABLE
    Nov 04 21:59:09 arch kernel: init_memory_mapping: [mem 0x7f800000-0x7f9fffff]
    Nov 04 21:59:09 arch kernel: [mem 0x7f800000-0x7f9fffff] page 2M
    Nov 04 21:59:09 arch kernel: BRK [0x01b32000, 0x01b32fff] PGTABLE
    Nov 04 21:59:09 arch kernel: init_memory_mapping: [mem 0x7c000000-0x7f7fffff]
    Nov 04 21:59:09 arch kernel: [mem 0x7c000000-0x7f7fffff] page 2M
    Nov 04 21:59:09 arch kernel: init_memory_mapping: [mem 0x00100000-0x7bffffff]
    Nov 04 21:59:09 arch kernel: [mem 0x00100000-0x001fffff] page 4k
    Nov 04 21:59:09 arch kernel: [mem 0x00200000-0x7bffffff] page 2M
    Nov 04 21:59:09 arch kernel: init_memory_mapping: [mem 0x7fa00000-0x7fbb4fff]
    Nov 04 21:59:09 arch kernel: [mem 0x7fa00000-0x7fbb4fff] page 4k
    Nov 04 21:59:09 arch kernel: BRK [0x01b33000, 0x01b33fff] PGTABLE
    Nov 04 21:59:09 arch kernel: init_memory_mapping: [mem 0x7fd6b000-0x7fefffff]
    Nov 04 21:59:09 arch kernel: [mem 0x7fd6b000-0x7fefffff] page 4k
    Nov 04 21:59:09 arch kernel: BRK [0x01b34000, 0x01b34fff] PGTABLE
    Nov 04 21:59:09 arch kernel: RAMDISK: [mem 0x37a14000-0x37d01fff]
    Nov 04 21:59:09 arch kernel: ACPI: RSDP 00000000000f03f0 00024 (v02 INTEL)
    Nov 04 21:59:09 arch kernel: ACPI: XSDT 000000007fd53f10 00044 (v01 INTEL DG31PR 06222004 MSFT 00010013)
    Nov 04 21:59:09 arch kernel: ACPI: FACP 000000007fd51d90 000F4 (v04 INTEL DG31PR 06222004 MSFT 00010013)
    Nov 04 21:59:09 arch kernel: ACPI Warning: 32/64 FACS address mismatch in FADT - two FACS tables! (20130517/tbfadt-395)
    Nov 04 21:59:09 arch kernel: ACPI BIOS Warning (bug): 32/64X FACS address mismatch in FADT - 0x7FD56F40/0x000000007FD52F40, using 32 (20130517/tbfadt-522)
    Nov 04 21:59:09 arch kernel: ACPI: DSDT 000000007fd4c010 04BE9 (v01 INTEL DG31PR 00000000 INTL 20051117)
    Nov 04 21:59:09 arch kernel: ACPI: FACS 000000007fd56f40 00040
    Nov 04 21:59:09 arch kernel: ACPI: APIC 000000007fd51f10 0006C (v02 INTEL DG31PR 06222004 MSFT 00010013)
    Nov 04 21:59:09 arch kernel: ACPI: HPET 000000007fd5ad10 00038 (v01 INTEL ICH7HPET 06222004 AMI. 00000001)
    Nov 04 21:59:09 arch kernel: ACPI: MCFG 000000007fd5ac10 0003C (v01 INTEL DG31PR 06222004 MSFT 00000097)
    Nov 04 21:59:09 arch kernel: ACPI: Local APIC address 0xfee00000
    Nov 04 21:59:09 arch kernel: No NUMA configuration found
    Nov 04 21:59:09 arch kernel: Faking a node at [mem 0x0000000000000000-0x000000007fefffff]
    Nov 04 21:59:09 arch kernel: Initmem setup node 0 [mem 0x00000000-0x7fefffff]
    Nov 04 21:59:09 arch kernel: NODE_DATA [mem 0x7fefb000-0x7fefffff]
    Nov 04 21:59:09 arch kernel: [ffffea0000000000-ffffea0001ffffff] PMD -> [ffff88007d200000-ffff88007f1fffff] on node 0
    Nov 04 21:59:09 arch kernel: Zone ranges:
    Nov 04 21:59:09 arch kernel: DMA [mem 0x00001000-0x00ffffff]
    Nov 04 21:59:09 arch kernel: DMA32 [mem 0x01000000-0xffffffff]
    Nov 04 21:59:09 arch kernel: Normal empty
    Nov 04 21:59:09 arch kernel: Movable zone start for each node
    Nov 04 21:59:09 arch kernel: Early memory node ranges
    Nov 04 21:59:09 arch kernel: node 0: [mem 0x00001000-0x0009efff]
    Nov 04 21:59:09 arch kernel: node 0: [mem 0x00100000-0x7fbb4fff]
    Nov 04 21:59:09 arch kernel: node 0: [mem 0x7fd6b000-0x7fefffff]
    Nov 04 21:59:09 arch kernel: On node 0 totalpages: 523496
    Nov 04 21:59:09 arch kernel: DMA zone: 64 pages used for memmap
    Nov 04 21:59:09 arch kernel: DMA zone: 21 pages reserved
    Nov 04 21:59:09 arch kernel: DMA zone: 3998 pages, LIFO batch:0
    Nov 04 21:59:09 arch kernel: DMA32 zone: 8124 pages used for memmap
    Nov 04 21:59:09 arch kernel: DMA32 zone: 519498 pages, LIFO batch:31
    Nov 04 21:59:09 arch kernel: ACPI: PM-Timer IO Port: 0x408
    Nov 04 21:59:09 arch kernel: ACPI: Local APIC address 0xfee00000
    Nov 04 21:59:09 arch kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
    Nov 04 21:59:09 arch kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
    Nov 04 21:59:09 arch kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
    Nov 04 21:59:09 arch kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
    Nov 04 21:59:09 arch kernel: ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
    Nov 04 21:59:09 arch kernel: IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
    Nov 04 21:59:09 arch kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    Nov 04 21:59:09 arch kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    Nov 04 21:59:09 arch kernel: ACPI: IRQ0 used by override.
    Nov 04 21:59:09 arch kernel: ACPI: IRQ2 used by override.
    Nov 04 21:59:09 arch kernel: ACPI: IRQ9 used by override.
    Nov 04 21:59:09 arch kernel: Using ACPI (MADT) for SMP configuration information
    Nov 04 21:59:09 arch kernel: ACPI: HPET id: 0x8086a201 base: 0xfed00000
    Nov 04 21:59:09 arch kernel: smpboot: Allowing 4 CPUs, 0 hotplug CPUs
    Nov 04 21:59:09 arch kernel: nr_irqs_gsi: 40
    Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
    Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
    Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
    Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x7fbb5000-0x7fbf7fff]
    Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x7fbf8000-0x7fd4bfff]
    Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x7fd4c000-0x7fd51fff]
    Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x7fd52000-0x7fd52fff]
    Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x7fd53000-0x7fd54fff]
    Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x7fd55000-0x7fd56fff]
    Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x7fd57000-0x7fd57fff]
    Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x7fd58000-0x7fd5bfff]
    Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x7fd5c000-0x7fd6afff]
    Nov 04 21:59:09 arch kernel: e820: [mem 0x7ff00000-0xfed1bfff] available for PCI devices
    Nov 04 21:59:09 arch kernel: Booting paravirtualized kernel on bare hardware
    Nov 04 21:59:09 arch kernel: setup_percpu: NR_CPUS:128 nr_cpumask_bits:128 nr_cpu_ids:4 nr_node_ids:1
    Nov 04 21:59:09 arch kernel: PERCPU: Embedded 29 pages/cpu @ffff88007f800000 s86528 r8192 d24064 u524288
    Nov 04 21:59:09 arch kernel: pcpu-alloc: s86528 r8192 d24064 u524288 alloc=1*2097152
    Nov 04 21:59:09 arch kernel: pcpu-alloc: [0] 0 1 2 3
    Nov 04 21:59:09 arch kernel: Built 1 zonelists in Node order, mobility grouping on. Total pages: 515287
    Nov 04 21:59:09 arch kernel: Policy zone: DMA32
    Nov 04 21:59:09 arch kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=17d019be-e01f-4c1c-ac50-69e1f3dc0592 rw quiet 3
    Nov 04 21:59:09 arch kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
    Nov 04 21:59:09 arch kernel: Checking aperture...
    Nov 04 21:59:09 arch kernel: No AGP bridge found
    Nov 04 21:59:09 arch kernel: Calgary: detecting Calgary via BIOS EBDA area
    Nov 04 21:59:09 arch kernel: Calgary: Unable to locate Rio Grande table in EBDA - bailing!
    Nov 04 21:59:09 arch kernel: Memory: 2045916K/2093984K available (5050K kernel code, 799K rwdata, 1696K rodata, 1140K init, 1288K bss, 48068K reserved)
    Nov 04 21:59:09 arch kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
    Nov 04 21:59:09 arch kernel: Preemptible hierarchical RCU implementation.
    Nov 04 21:59:09 arch kernel: RCU dyntick-idle grace-period acceleration is enabled.
    Nov 04 21:59:09 arch kernel: Dump stacks of tasks blocking RCU-preempt GP.
    Nov 04 21:59:09 arch kernel: RCU restricting CPUs from NR_CPUS=128 to nr_cpu_ids=4.
    Nov 04 21:59:09 arch kernel: NR_IRQS:8448 nr_irqs:712 16
    Nov 04 21:59:09 arch kernel: Console: colour dummy device 80x25
    Nov 04 21:59:09 arch kernel: console [tty0] enabled
    Nov 04 21:59:09 arch kernel: allocated 8388608 bytes of page_cgroup
    Nov 04 21:59:09 arch kernel: please try 'cgroup_disable=memory' option if you don't want memory cgroups
    Nov 04 21:59:09 arch kernel: hpet clockevent registered
    Nov 04 21:59:09 arch kernel: tsc: Fast TSC calibration using PIT
    Nov 04 21:59:09 arch kernel: tsc: Detected 2399.803 MHz processor
    Nov 04 21:59:09 arch kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 4801.58 BogoMIPS (lpj=7999343)
    Nov 04 21:59:09 arch kernel: pid_max: default: 32768 minimum: 301
    Nov 04 21:59:09 arch kernel: Security Framework initialized
    Nov 04 21:59:09 arch kernel: AppArmor: AppArmor disabled by boot time parameter
    Nov 04 21:59:09 arch kernel: Yama: becoming mindful.
    Nov 04 21:59:09 arch kernel: Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
    Nov 04 21:59:09 arch kernel: Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
    Nov 04 21:59:09 arch kernel: Mount-cache hash table entries: 256
    Nov 04 21:59:09 arch kernel: Initializing cgroup subsys memory
    Nov 04 21:59:09 arch kernel: Initializing cgroup subsys devices
    Nov 04 21:59:09 arch kernel: Initializing cgroup subsys freezer
    Nov 04 21:59:09 arch kernel: Initializing cgroup subsys net_cls
    Nov 04 21:59:09 arch kernel: Initializing cgroup subsys blkio
    Nov 04 21:59:09 arch kernel: CPU: Physical Processor ID: 0
    Nov 04 21:59:09 arch kernel: CPU: Processor Core ID: 0
    Nov 04 21:59:09 arch kernel: mce: CPU supports 6 MCE banks
    Nov 04 21:59:09 arch kernel: CPU0: Thermal monitoring enabled (TM2)
    Nov 04 21:59:09 arch kernel: Last level iTLB entries: 4KB 128, 2MB 4, 4MB 4
    Last level dTLB entries: 4KB 256, 2MB 0, 4MB 32
    tlb_flushall_shift: -1
    Nov 04 21:59:09 arch kernel: Freeing SMP alternatives memory: 20K (ffffffff819e6000 - ffffffff819eb000)
    Nov 04 21:59:09 arch kernel: ACPI: Core revision 20130517
    Nov 04 21:59:09 arch kernel: ACPI: All ACPI Tables successfully acquired
    Nov 04 21:59:09 arch kernel: ftrace: allocating 20100 entries in 79 pages
    Nov 04 21:59:09 arch kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    Nov 04 21:59:09 arch kernel: smpboot: CPU0: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (fam: 06, model: 0f, stepping: 0b)
    Nov 04 21:59:09 arch kernel: Performance Events: PEBS fmt0+, 4-deep LBR, Core2 events, Intel PMU driver.
    Nov 04 21:59:09 arch kernel: perf_event_intel: PEBS disabled due to CPU errata
    Nov 04 21:59:09 arch kernel: ... version: 2
    Nov 04 21:59:09 arch kernel: ... bit width: 40
    Nov 04 21:59:09 arch kernel: ... generic registers: 2
    Nov 04 21:59:09 arch kernel: ... value mask: 000000ffffffffff
    Nov 04 21:59:09 arch kernel: ... max period: 000000007fffffff
    Nov 04 21:59:09 arch kernel: ... fixed-purpose events: 3
    Nov 04 21:59:09 arch kernel: ... event mask: 0000000700000003
    Nov 04 21:59:09 arch kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
    Nov 04 21:59:09 arch kernel: smpboot: Booting Node 0, Processors #1 #2 #3 OK
    Nov 04 21:59:09 arch kernel: Brought up 4 CPUs
    Nov 04 21:59:09 arch kernel: smpboot: Total of 4 processors activated (19206.35 BogoMIPS)
    Nov 04 21:59:09 arch kernel: devtmpfs: initialized
    Nov 04 21:59:09 arch kernel: PM: Registering ACPI NVS region [mem 0x7fbb5000-0x7fbf7fff] (274432 bytes)
    Nov 04 21:59:09 arch kernel: PM: Registering ACPI NVS region [mem 0x7fd52000-0x7fd52fff] (4096 bytes)
    Nov 04 21:59:09 arch kernel: PM: Registering ACPI NVS region [mem 0x7fd55000-0x7fd56fff] (8192 bytes)
    Nov 04 21:59:09 arch kernel: PM: Registering ACPI NVS region [mem 0x7fd58000-0x7fd5bfff] (16384 bytes)
    Nov 04 21:59:09 arch kernel: RTC time: 0:59:05, date: 11/05/13
    Nov 04 21:59:09 arch kernel: NET: Registered protocol family 16
    Nov 04 21:59:09 arch kernel: ACPI: bus type PCI registered
    Nov 04 21:59:09 arch kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
    Nov 04 21:59:09 arch kernel: PCI: MMCONFIG for domain 0000 [bus 00-40] at [mem 0xe0000000-0xe40fffff] (base 0xe0000000)
    Nov 04 21:59:09 arch kernel: PCI: not using MMCONFIG
    Nov 04 21:59:09 arch kernel: PCI: Using configuration type 1 for base access
    Nov 04 21:59:09 arch kernel: mtrr: your CPUs had inconsistent fixed MTRR settings
    Nov 04 21:59:09 arch kernel: mtrr: your CPUs had inconsistent variable MTRR settings
    Nov 04 21:59:09 arch kernel: mtrr: probably your BIOS does not setup all CPUs.
    Nov 04 21:59:09 arch kernel: mtrr: corrected configuration.
    Nov 04 21:59:09 arch kernel: bio: create slab <bio-0> at 0
    Nov 04 21:59:09 arch kernel: ACPI: Added _OSI(Module Device)
    Nov 04 21:59:09 arch kernel: ACPI: Added _OSI(Processor Device)
    Nov 04 21:59:09 arch kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
    Nov 04 21:59:09 arch kernel: ACPI: Added _OSI(Processor Aggregator Device)
    Nov 04 21:59:09 arch kernel: ACPI: EC: Look up EC in DSDT
    Nov 04 21:59:09 arch kernel: ACPI: Executed 1 blocks of module-level executable AML code
    Nov 04 21:59:09 arch kernel: ACPI: SSDT 000000007fd56c10 002CC (v01 AMI IST 00000001 MSFT 03000001)
    Nov 04 21:59:09 arch kernel: ACPI: Dynamic OEM Table Load:
    Nov 04 21:59:09 arch kernel: ACPI: SSDT (null) 002CC (v01 AMI IST 00000001 MSFT 03000001)
    Nov 04 21:59:09 arch kernel: ACPI: Interpreter enabled
    Nov 04 21:59:09 arch kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20130517/hwxface-571)
    Nov 04 21:59:09 arch kernel: ACPI: (supports S0 S1 S3 S4 S5)
    Nov 04 21:59:09 arch kernel: ACPI: Using IOAPIC for interrupt routing
    Nov 04 21:59:09 arch kernel: PCI: MMCONFIG for domain 0000 [bus 00-40] at [mem 0xe0000000-0xe40fffff] (base 0xe0000000)
    Nov 04 21:59:09 arch kernel: PCI: MMCONFIG at [mem 0xe0000000-0xe40fffff] reserved in ACPI motherboard resources
    Nov 04 21:59:09 arch kernel: PCI: MMCONFIG for 0000 [bus00-1f] at [mem 0xe0000000-0xe1ffffff] (base 0xe0000000) (size reduced!)
    Nov 04 21:59:09 arch kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
    Nov 04 21:59:09 arch kernel: ACPI: No dock devices found.
    Nov 04 21:59:09 arch kernel: [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
    Nov 04 21:59:09 arch kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
    Nov 04 21:59:09 arch kernel: acpi PNP0A08:00: Requesting ACPI _OSC control (0x1d)
    Nov 04 21:59:09 arch kernel: acpi PNP0A08:00: ACPI _OSC control (0x1d) granted
    Nov 04 21:59:09 arch kernel: acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-1f] only partially covers this bridge
    Nov 04 21:59:09 arch kernel: PCI host bridge to bus 0000:00
    Nov 04 21:59:09 arch kernel: pci_bus 0000:00: root bus resource [bus 00-ff]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:00: root bus resource [mem 0x80000000-0xffffffff]
    Nov 04 21:59:09 arch kernel: pci 0000:00:00.0: [8086:29c0] type 00 class 0x060000
    Nov 04 21:59:09 arch kernel: pci 0000:00:01.0: [8086:29c1] type 01 class 0x060400
    Nov 04 21:59:09 arch kernel: pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
    Nov 04 21:59:09 arch kernel: pci 0000:00:01.0: System wakeup disabled by ACPI
    Nov 04 21:59:09 arch kernel: pci 0000:00:1b.0: [8086:27d8] type 00 class 0x040300
    Nov 04 21:59:09 arch kernel: pci 0000:00:1b.0: reg 0x10: [mem 0xfb200000-0xfb203fff 64bit]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: [8086:27d0] type 01 class 0x060400
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: System wakeup disabled by ACPI
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: [8086:27d2] type 01 class 0x060400
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: System wakeup disabled by ACPI
    Nov 04 21:59:09 arch kernel: pci 0000:00:1d.0: [8086:27c8] type 00 class 0x0c0300
    Nov 04 21:59:09 arch kernel: pci 0000:00:1d.0: reg 0x20: [io 0xf080-0xf09f]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1d.0: System wakeup disabled by ACPI
    Nov 04 21:59:09 arch kernel: pci 0000:00:1d.1: [8086:27c9] type 00 class 0x0c0300
    Nov 04 21:59:09 arch kernel: pci 0000:00:1d.1: reg 0x20: [io 0xf060-0xf07f]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1d.1: System wakeup disabled by ACPI
    Nov 04 21:59:09 arch kernel: pci 0000:00:1d.2: [8086:27ca] type 00 class 0x0c0300
    Nov 04 21:59:09 arch kernel: pci 0000:00:1d.2: reg 0x20: [io 0xf040-0xf05f]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1d.2: System wakeup disabled by ACPI
    Nov 04 21:59:09 arch kernel: pci 0000:00:1d.3: [8086:27cb] type 00 class 0x0c0300
    Nov 04 21:59:09 arch kernel: pci 0000:00:1d.3: reg 0x20: [io 0xf020-0xf03f]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1d.3: System wakeup disabled by ACPI
    Nov 04 21:59:09 arch kernel: pci 0000:00:1d.7: [8086:27cc] type 00 class 0x0c0320
    Nov 04 21:59:09 arch kernel: pci 0000:00:1d.7: reg 0x10: [mem 0xfb204000-0xfb2043ff]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
    Nov 04 21:59:09 arch kernel: pci 0000:00:1d.7: System wakeup disabled by ACPI
    Nov 04 21:59:09 arch kernel: pci 0000:00:1e.0: [8086:244e] type 01 class 0x060401
    Nov 04 21:59:09 arch kernel: pci 0000:00:1e.0: System wakeup disabled by ACPI
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.0: [8086:27b8] type 00 class 0x060100
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.0: address space collision: [io 0x0400-0x047f] conflicts with ACPI CPU throttle [??? 0x00000410-0x00000415 flags 0x80000000]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.0: quirk: [io 0x0500-0x053f] claimed by ICH6 GPIO
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0290 (mask 00ff)
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.1: [8086:27df] type 00 class 0x01018a
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.1: reg 0x10: [io 0xf130-0xf137]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.1: reg 0x14: [io 0xf120-0xf123]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.1: reg 0x18: [io 0xf110-0xf117]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.1: reg 0x1c: [io 0xf100-0xf103]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.1: reg 0x20: [io 0xf0f0-0xf0ff]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.2: [8086:27c0] type 00 class 0x01018f
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.2: reg 0x10: [io 0xf0e0-0xf0e7]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.2: reg 0x14: [io 0xf0d0-0xf0d3]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.2: reg 0x18: [io 0xf0c0-0xf0c7]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.2: reg 0x1c: [io 0xf0b0-0xf0b3]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.2: reg 0x20: [io 0xf0a0-0xf0af]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.2: PME# supported from D3hot
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.3: [8086:27da] type 00 class 0x0c0500
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.3: reg 0x20: [io 0xf000-0xf01f]
    Nov 04 21:59:09 arch kernel: pci 0000:01:00.0: [10de:0421] type 00 class 0x030000
    Nov 04 21:59:09 arch kernel: pci 0000:01:00.0: reg 0x10: [mem 0xfa000000-0xfaffffff]
    Nov 04 21:59:09 arch kernel: pci 0000:01:00.0: reg 0x14: [mem 0xd0000000-0xdfffffff 64bit pref]
    Nov 04 21:59:09 arch kernel: pci 0000:01:00.0: reg 0x1c: [mem 0xf8000000-0xf9ffffff 64bit]
    Nov 04 21:59:09 arch kernel: pci 0000:01:00.0: reg 0x24: [io 0xe000-0xe07f]
    Nov 04 21:59:09 arch kernel: pci 0000:01:00.0: reg 0x30: [mem 0xfb000000-0xfb01ffff pref]
    Nov 04 21:59:09 arch kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
    Nov 04 21:59:09 arch kernel: pci 0000:00:01.0: bridge window [io 0xe000-0xefff]
    Nov 04 21:59:09 arch kernel: pci 0000:00:01.0: bridge window [mem 0xf8000000-0xfb0fffff]
    Nov 04 21:59:09 arch kernel: pci 0000:00:01.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: PCI bridge to [bus 02]
    Nov 04 21:59:09 arch kernel: pci 0000:03:00.0: [10ec:8168] type 00 class 0x020000
    Nov 04 21:59:09 arch kernel: pci 0000:03:00.0: reg 0x10: [io 0xd000-0xd0ff]
    Nov 04 21:59:09 arch kernel: pci 0000:03:00.0: reg 0x18: [mem 0xfb120000-0xfb120fff 64bit]
    Nov 04 21:59:09 arch kernel: pci 0000:03:00.0: reg 0x30: [mem 0xfb100000-0xfb11ffff pref]
    Nov 04 21:59:09 arch kernel: pci 0000:03:00.0: supports D1 D2
    Nov 04 21:59:09 arch kernel: pci 0000:03:00.0: PME# supported from D1 D2 D3hot D3cold
    Nov 04 21:59:09 arch kernel: pci 0000:03:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: PCI bridge to [bus 03]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: bridge window [io 0xd000-0xdfff]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: bridge window [mem 0xfb100000-0xfb1fffff]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1e.0: PCI bridge to [bus 04] (subtractive decode)
    Nov 04 21:59:09 arch kernel: pci 0000:00:1e.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
    Nov 04 21:59:09 arch kernel: pci 0000:00:1e.0: bridge window [io 0x0d00-0xffff] (subtractive decode)
    Nov 04 21:59:09 arch kernel: pci 0000:00:1e.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
    Nov 04 21:59:09 arch kernel: pci 0000:00:1e.0: bridge window [mem 0x80000000-0xffffffff] (subtractive decode)
    Nov 04 21:59:09 arch kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
    Nov 04 21:59:09 arch kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
    Nov 04 21:59:09 arch kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 *7 10 11 12 14 15)
    Nov 04 21:59:09 arch kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs *3 4 5 6 10 11 12 14 15)
    Nov 04 21:59:09 arch kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0
    Nov 04 21:59:09 arch kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0
    Nov 04 21:59:09 arch kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0
    Nov 04 21:59:09 arch kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 *5 6 7 10 11 12 14 15)
    Nov 04 21:59:09 arch kernel: ACPI: Enabled 3 GPEs in block 00 to 1F
    Nov 04 21:59:09 arch kernel: ACPI: \_SB_.PCI0: notify handler is installed
    Nov 04 21:59:09 arch kernel: Found 1 acpi root devices
    Nov 04 21:59:09 arch kernel: vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
    Nov 04 21:59:09 arch kernel: vgaarb: loaded
    Nov 04 21:59:09 arch kernel: vgaarb: bridge control possible 0000:01:00.0
    Nov 04 21:59:09 arch kernel: PCI: Using ACPI for IRQ routing
    Nov 04 21:59:09 arch kernel: PCI: pci_cache_line_size set to 64 bytes
    Nov 04 21:59:09 arch kernel: e820: reserve RAM buffer [mem 0x0009fc00-0x0009ffff]
    Nov 04 21:59:09 arch kernel: e820: reserve RAM buffer [mem 0x7fbb5000-0x7fffffff]
    Nov 04 21:59:09 arch kernel: e820: reserve RAM buffer [mem 0x7ff00000-0x7fffffff]
    Nov 04 21:59:09 arch kernel: NetLabel: Initializing
    Nov 04 21:59:09 arch kernel: NetLabel: domain hash size = 128
    Nov 04 21:59:09 arch kernel: NetLabel: protocols = UNLABELED CIPSOv4
    Nov 04 21:59:09 arch kernel: NetLabel: unlabeled traffic allowed by default
    Nov 04 21:59:09 arch kernel: HPET: 3 timers in total, 0 timers will be used for per-cpu timer
    Nov 04 21:59:09 arch kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
    Nov 04 21:59:09 arch kernel: hpet0: 3 comparators, 64-bit 14.318180 MHz counter
    Nov 04 21:59:09 arch kernel: Switched to clocksource hpet
    Nov 04 21:59:09 arch kernel: pnp: PnP ACPI init
    Nov 04 21:59:09 arch kernel: ACPI: bus type PNP registered
    Nov 04 21:59:09 arch kernel: system 00:00: [mem 0xfed14000-0xfed19fff] has been reserved
    Nov 04 21:59:09 arch kernel: system 00:00: [mem 0xe0000000-0xe3ffffff] has been reserved
    Nov 04 21:59:09 arch kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
    Nov 04 21:59:09 arch kernel: system 00:01: [io 0x0400-0x047f] could not be reserved
    Nov 04 21:59:09 arch kernel: system 00:01: [io 0x1180-0x119f] has been reserved
    Nov 04 21:59:09 arch kernel: system 00:01: [io 0x0500-0x053f] has been reserved
    Nov 04 21:59:09 arch kernel: system 00:01: [mem 0xfec00000-0xfecfffff] could not be reserved
    Nov 04 21:59:09 arch kernel: system 00:01: [mem 0xfee00000-0xfee0ffff] has been reserved
    Nov 04 21:59:09 arch kernel: system 00:01: [mem 0xfed1c000-0xfed1ffff] has been reserved
    Nov 04 21:59:09 arch kernel: system 00:01: [mem 0xffb00000-0xffcfffff] could not be reserved
    Nov 04 21:59:09 arch kernel: system 00:01: [mem 0xfc800000-0xfc800fff] has been reserved
    Nov 04 21:59:09 arch kernel: system 00:01: [mem 0xfed20000-0xfed7ffff] has been reserved
    Nov 04 21:59:09 arch kernel: system 00:01: [mem 0xffe00000-0xffffffff] has been reserved
    Nov 04 21:59:09 arch kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c01 (active)
    Nov 04 21:59:09 arch kernel: system 00:02: [io 0x0290-0x029f] has been reserved
    Nov 04 21:59:09 arch kernel: system 00:02: Plug and Play ACPI device, IDs PNP0c02 (active)
    Nov 04 21:59:09 arch kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0f03 PNP0f13 (active)
    Nov 04 21:59:09 arch kernel: pnp 00:04: [dma 2]
    Nov 04 21:59:09 arch kernel: pnp 00:04: Plug and Play ACPI device, IDs PNP0700 (active)
    Nov 04 21:59:09 arch kernel: pnp 00:05: [dma 0 disabled]
    Nov 04 21:59:09 arch kernel: pnp 00:05: Plug and Play ACPI device, IDs PNP0501 (active)
    Nov 04 21:59:09 arch kernel: pnp 00:06: [dma 4]
    Nov 04 21:59:09 arch kernel: pnp 00:06: Plug and Play ACPI device, IDs PNP0200 (active)
    Nov 04 21:59:09 arch kernel: pnp 00:07: Plug and Play ACPI device, IDs PNP0b00 (active)
    Nov 04 21:59:09 arch kernel: pnp 00:08: Plug and Play ACPI device, IDs PNP0800 (active)
    Nov 04 21:59:09 arch kernel: system 00:09: [io 0x04d0-0x04d1] has been reserved
    Nov 04 21:59:09 arch kernel: system 00:09: Plug and Play ACPI device, IDs PNP0c02 (active)
    Nov 04 21:59:09 arch kernel: pnp 00:0a: Plug and Play ACPI device, IDs PNP0c04 (active)
    Nov 04 21:59:09 arch kernel: pnp 00:0b: Plug and Play ACPI device, IDs PNP0103 (active)
    Nov 04 21:59:09 arch kernel: pnp: PnP ACPI: found 12 devices
    Nov 04 21:59:09 arch kernel: ACPI: bus type PNP unregistered
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: bridge window [io 0x1000-0x0fff] to [bus 02] add_size 1000
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 02] add_size 200000
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff] to [bus 02] add_size 200000
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 03] add_size 200000
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.0: BAR 13: [io 0x0400-0x047f] has bogus alignment
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: res[14]=[mem 0x00100000-0x000fffff] get_res_add_size add_size 200000
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_size add_size 200000
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_size add_size 200000
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: BAR 14: assigned [mem 0x80000000-0x801fffff]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: BAR 15: assigned [mem 0x80200000-0x803fffff 64bit pref]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: BAR 15: assigned [mem 0x80400000-0x805fffff 64bit pref]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: BAR 13: assigned [io 0x2000-0x2fff]
    Nov 04 21:59:09 arch kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
    Nov 04 21:59:09 arch kernel: pci 0000:00:01.0: bridge window [io 0xe000-0xefff]
    Nov 04 21:59:09 arch kernel: pci 0000:00:01.0: bridge window [mem 0xf8000000-0xfb0fffff]
    Nov 04 21:59:09 arch kernel: pci 0000:00:01.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: PCI bridge to [bus 02]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: bridge window [io 0x2000-0x2fff]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: bridge window [mem 0x80000000-0x801fffff]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: bridge window [mem 0x80200000-0x803fffff 64bit pref]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: PCI bridge to [bus 03]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: bridge window [io 0xd000-0xdfff]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: bridge window [mem 0xfb100000-0xfb1fffff]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: bridge window [mem 0x80400000-0x805fffff 64bit pref]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1e.0: PCI bridge to [bus 04]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1e.0: setting latency timer to 64
    Nov 04 21:59:09 arch kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:00: resource 7 [mem 0x80000000-0xffffffff]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:01: resource 0 [io 0xe000-0xefff]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:01: resource 1 [mem 0xf8000000-0xfb0fffff]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:01: resource 2 [mem 0xd0000000-0xdfffffff 64bit pref]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:02: resource 0 [io 0x2000-0x2fff]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:02: resource 1 [mem 0x80000000-0x801fffff]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:02: resource 2 [mem 0x80200000-0x803fffff 64bit pref]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:03: resource 0 [io 0xd000-0xdfff]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:03: resource 1 [mem 0xfb100000-0xfb1fffff]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:03: resource 2 [mem 0x80400000-0x805fffff 64bit pref]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:04: resource 4 [io 0x0000-0x0cf7]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:04: resource 5 [io 0x0d00-0xffff]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:04: resource 6 [mem 0x000a0000-0x000bffff]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:04: resource 7 [mem 0x80000000-0xffffffff]
    Nov 04 21:59:09 arch kernel: NET: Registered protocol family 2
    Nov 04 21:59:09 arch kernel: TCP established hash table entries: 16384 (order: 6, 262144 bytes)
    Nov 04 21:59:09 arch kernel: TCP bind hash table entries: 16384 (order: 6, 262144 bytes)
    Nov 04 21:59:09 arch kernel: TCP: Hash tables configured (established 16384 bind 16384)
    Nov 04 21:59:09 arch kernel: TCP: reno registered
    Nov 04 21:59:09 arch kernel: UDP hash table entries: 1024 (order: 3, 32768 bytes)
    Nov 04 21:59:09 arch kernel: UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes)
    Nov 04 21:59:09 arch kernel: NET: Registered protocol family 1
    Nov 04 21:59:09 arch kernel: pci 0000:00:1d.7: EHCI: BIOS handoff failed (BIOS bug?) 01010001
    Nov 04 21:59:09 arch kernel: pci 0000:01:00.0: Boot video device
    Nov 04 21:59:09 arch kernel: PCI: CLS 64 bytes, default 64
    Nov 04 21:59:09 arch kernel: Unpacking initramfs...
    Nov 04 21:59:09 arch kernel: Freeing initrd memory: 3000K (ffff880037a14000 - ffff880037d02000)
    Nov 04 21:59:09 arch kernel: Scanning for low memory corruption every 60 seconds
    Nov 04 21:59:09 arch kernel: audit: initializing netlink socket (disabled)
    Nov 04 21:59:09 arch kernel: type=2000 audit(1383613146.559:1): initialized
    Nov 04 21:59:09 arch kernel: HugeTLB registered 2 MB page size, pre-allocated 0 pages
    Nov 04 21:59:09 arch kernel: zbud: loaded
    Nov 04 21:59:09 arch kernel: VFS: Disk quotas dquot_6.5.2
    Nov 04 21:59:09 arch kernel: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
    Nov 04 21:59:09 arch kernel: msgmni has been set to 4001
    Nov 04 21:59:09 arch kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
    Nov 04 21:59:09 arch kernel: io scheduler noop registered
    Nov 04 21:59:09 arch kernel: io scheduler deadline registered
    Nov 04 21:59:09 arch kernel: io scheduler cfq registered (default)
    Nov 04 21:59:09 arch kernel: pcieport 0000:00:01.0: irq 40 for MSI/MSI-X
    Nov 04 21:59:09 arch kernel: pcieport 0000:00:1c.0: irq 41 for MSI/MSI-X
    Nov 04 21:59:09 arch kernel: pcieport 0000:00:1c.1: irq 42 for MSI/MSI-X
    Nov 04 21:59:09 arch kernel: pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
    Nov 04 21:59:09 arch kernel: pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
    Nov 04 21:59:09 arch kernel: pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
    Nov 04 21:59:09 arch kernel: pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
    Nov 04 21:59:09 arch kernel: pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
    Nov 04 21:59:09 arch kernel: pcieport 0000:00:1c.1: Signaling PME through PCIe PME interrupt
    Nov 04 21:59:09 arch kernel: pci 0000:03:00.0: Signaling PME through PCIe PME interrupt
    Nov 04 21:59:09 arch kernel: pcie_pme 0000:00:1c.1:pcie01: service driver pcie_pme loaded
    Nov 04 21:59:09 arch kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    Nov 04 21:59:09 arch kernel: pciehp 0000:00:1c.0:pcie04: HPC vendor_id 8086 device_id 27d0 ss_vid 8086 ss_did 27d0
    Nov 04 21:59:09 arch kernel: pciehp 0000:00:1c.0:pcie04: service driver pciehp loaded
    Nov 04 21:59:09 arch kernel: pciehp 0000:00:1c.1:pcie04: HPC vendor_id 8086 device_id 27d2 ss_vid 8086 ss_did 27d2
    Nov 04 21:59:09 arch kernel: pciehp 0000:00:1c.1:pcie04: service driver pciehp loaded
    Nov 04 21:59:09 arch kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
    Nov 04 21:59:09 arch kernel: vesafb: mode is 640x480x32, linelength=2560, pages=0
    Nov 04 21:59:09 arch kernel: vesafb: scrolling: redraw
    Nov 04 21:59:09 arch kernel: vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
    Nov 04 21:59:09 arch kernel: vesafb: framebuffer at 0xf9000000, mapped to 0xffffc90002400000, using 1216k, total 1216k
    Nov 04 21:59:09 arch kernel: Console: switching to colour frame buffer device 80x30
    Nov 04 21:59:09 arch kernel: fb0: VESA VGA frame buffer device
    Nov 04 21:59:09 arch kernel: intel_idle: does not run on family 6 model 15
    Nov 04 21:59:09 arch kernel: GHES: HEST is not enabled!
    Nov 04 21:59:09 arch kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    Nov 04 21:59:09 arch kernel: 00:05: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
    Nov 04 21:59:09 arch kernel: Linux agpgart interface v0.103
    Nov 04 21:59:09 arch kernel: i8042: PNP: PS/2 Controller [PNP0f03:PS2M] at 0x60,0x64 irq 12
    Nov 04 21:59:09 arch kernel: i8042: PNP: PS/2 controller doesn't have KBD irq; using default 1
    Nov 04 21:59:09 arch kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
    Nov 04 21:59:09 arch kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
    Nov 04 21:59:09 arch kernel: mousedev: PS/2 mouse device common for all mice
    Nov 04 21:59:09 arch kernel: rtc_cmos 00:07: RTC can wake from S4
    Nov 04 21:59:09 arch kernel: rtc_cmos 00:07: rtc core: registered rtc_cmos as rtc0
    Nov 04 21:59:09 arch kernel: rtc_cmos 00:07: alarms up to one year, y3k, 114 bytes nvram, hpet irqs
    Nov 04 21:59:09 arch kernel: cpuidle: using governor ladder
    Nov 04 21:59:09 arch kernel: cpuidle: using governor menu
    Nov 04 21:59:09 arch kernel: drop_monitor: Initializing network drop monitor service
    Nov 04 21:59:09 arch kernel: TCP: cubic registered
    Nov 04 21:59:09 arch kernel: NET: Registered protocol family 10
    Nov 04 21:59:09 arch kernel: NET: Registered protocol family 17
    Nov 04 21:59:09 arch kernel: Key type dns_resolver registered
    Nov 04 21:59:09 arch kernel: PM: Hibernation image not present or could not be loaded.
    Nov 04 21:59:09 arch kernel: registered taskstats version 1
    Nov 04 21:59:09 arch kernel: Magic number: 5:843:960
    Nov 04 21:59:09 arch kernel: memory memory11: hash matches
    Nov 04 21:59:09 arch kernel: rtc_cmos 00:07: setting system clock to 2013-11-05 00:59:07 UTC (1383613147)
    Nov 04 21:59:09 arch kernel: Freeing unused kernel memory: 1140K (ffffffff818c9000 - ffffffff819e6000)
    Nov 04 21:59:09 arch kernel: Write protecting the kernel read-only data: 8192k
    Nov 04 21:59:09 arch kernel: Freeing unused kernel memory: 1084K (ffff8800014f1000 - ffff880001600000)
    Nov 04 21:59:09 arch kernel: Freeing unused kernel memory: 352K (ffff8800017a8000 - ffff880001800000)
    Nov 04 21:59:09 arch systemd-udevd[58]: starting version 208
    Nov 04 21:59:09 arch kernel: Floppy drive(s): fd0 is 1.44M
    Nov 04 21:59:09 arch kernel: SCSI subsystem initialized
    Nov 04 21:59:09 arch kernel: ACPI: bus type USB registered
    Nov 04 21:59:09 arch kernel: usbcore: registered new interface driver usbfs
    Nov 04 21:59:09 arch kernel: usbcore: registered new interface driver hub
    Nov 04 21:59:09 arch kernel: usbcore: registered new device driver usb
    Nov 04 21:59:09 arch kernel: ACPI: bus type ATA registered
    Nov 04 21:59:09 arch kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    Nov 04 21:59:09 arch kernel: uhci_hcd: USB Universal Host Controller Interface driver
    Nov 04 21:59:09 arch kernel: libata version 3.00 loaded.
    Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.0: setting latency timer to 64
    Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.0: UHCI Host Controller
    Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
    Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.0: irq 23, io base 0x0000f080
    Nov 04 21:59:09 arch kernel: ehci-pci: EHCI PCI platform driver
    Nov 04 21:59:09 arch kernel: hub 1-0:1.0: USB hub found
    Nov 04 21:59:09 arch kernel: hub 1-0:1.0: 2 ports detected
    Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.1: setting latency timer to 64
    Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.1: UHCI Host Controller
    Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
    Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000f060
    Nov 04 21:59:09 arch kernel: hub 2-0:1.0: USB hub found
    Nov 04 21:59:09 arch kernel: hub 2-0:1.0: 2 ports detected
    Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.2: setting latency timer to 64
    Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.2: UHCI Host Controller
    Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
    Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000f040
    Nov 04 21:59:09 arch kernel: FDC 0 is a post-1991 82077
    Nov 04 21:59:09 arch kernel: hub 3-0:1.0: USB hub found
    Nov 04 21:59:09 arch kernel: hub 3-0:1.0: 2 ports detected
    Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.3: setting latency timer to 64
    Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.3: UHCI Host Controller
    Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4
    Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.3: irq 16, io base 0x0000f020
    Nov 04 21:59:09 arch kernel: hub 4-0:1.0: USB hub found
    Nov 04 21:59:09 arch kernel: hub 4-0:1.0: 2 ports detected
    Nov 04 21:59:09 arch kernel: ata_piix 0000:00:1f.1: version 2.13
    Nov 04 21:59:09 arch kernel: ata_piix 0000:00:1f.1: setting latency timer to 64
    Nov 04 21:59:09 arch kernel: scsi0 : ata_piix
    Nov 04 21:59:09 arch kernel: scsi1 : ata_piix
    Nov 04 21:59:09 arch kernel: ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xf0f0 irq 14
    Nov 04 21:59:09 arch kernel: ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xf0f8 irq 15
    Nov 04 21:59:09 arch kernel: ata_piix 0000:00:1f.2: MAP [
    Nov 04 21:59:09 arch kernel: P0 P2 P1 P3 ]
    Nov 04 21:59:09 arch kernel: ata_piix 0000:00:1f.2: setting latency timer to 64
    Nov 04 21:59:09 arch kernel: ata2: port disabled--ignoring
    Nov 04 21:59:09 arch kernel: scsi2 : ata_piix
    Nov 04 21:59:09 arch kernel: scsi3 : ata_piix
    Nov 04 21:59:09 arch kernel: ata3: SATA max UDMA/133 cmd 0xf0e0 ctl 0xf0d0 bmdma 0xf0a0 irq 19
    Nov 04 21:59:09 arch kernel: ata4: SATA max UDMA/133 cmd 0xf0c0 ctl 0xf0b0 bmdma 0xf0a8 irq 19
    Nov 04 21:59:09 arch kernel: ehci-pci 0000:00:1d.7: setting latency timer to 64
    Nov 04 21:59:09 arch kernel: ehci-pci 0000:00:1d.7: EHCI Host Controller
    Nov 04 21:59:09 arch kernel: ehci-pci 0000:00:1d.7: new USB bus registered, assigned bus number 5
    Nov 04 21:59:09 arch kernel: ehci-pci 0000:00:1d.7: debug port 1
    Nov 04 21:59:09 arch kernel: ehci-pci 0000:00:1d.7: cache line size of 64 is not supported
    Nov 04 21:59:09 arch kernel: ehci-pci 0000:00:1d.7: irq 23, io mem 0xfb204000
    Nov 04 21:59:09 arch kernel: ehci-pci 0000:00:1d.7: USB 2.0 started, EHCI 1.00
    Nov 04 21:59:09 arch kernel: hub 5-0:1.0: USB hub found
    Nov 04 21:59:09 arch kernel: hub 5-0:1.0: 8 ports detected
    Nov 04 21:59:09 arch kernel: hub 1-0:1.0: USB hub found
    Nov 04 21:59:09 arch kernel: hub 1-0:1.0: 2 ports detected
    Nov 04 21:59:09 arch kernel: hub 2-0:1.0: USB hub found
    Nov 04 21:59:09 arch kernel: hub 2-0:1.0: 2 ports detected
    Nov 04 21:59:09 arch kernel: hub 3-0:1.0: USB hub found
    Nov 04 21:59:09 arch kernel: hub 3-0:1.0: 2 ports detected
    Nov 04 21:59:09 arch kernel: hub 4-0:1.0: USB hub found
    Nov 04 21:59:09 arch kernel: hub 4-0:1.0: 2 ports detected
    Nov 04 21:59:09 arch kernel: ata4.00: ATA-8: WDC WD10EZEX-00RKKA0, 80.00A80, max UDMA/133
    Nov 04 21:59:09 arch kernel: ata4.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32)
    Nov 04 21:59:09 arch kernel: ata4.00: configured for UDMA/133
    Nov 04 21:59:09 arch kernel: scsi 3:0:0:0: Direct-Access ATA WDC WD10EZEX-00R 80.0 PQ: 0 ANSI: 5
    Nov 04 21:59:09 arch kernel: sd 3:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
    Nov 04 21:59:09 arch kernel: sd 3:0:0:0: [sda] 4096-byte physical blocks
    Nov 04 21:59:09 arch kernel: sd 3:0:0:0: [sda] Write Protect is off
    Nov 04 21:59:09 arch kernel: sd 3:0:0:0: [sda] Mode Sense: 00 3a 00 00
    Nov 04 21:59:09 arch kernel: sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    Nov 04 21:59:09 arch kernel: sda: sda1 sda2 sda3 sda4 sda5
    Nov 04 21:59:09 arch kernel: sd 3:0:0:0: [sda] Attached SCSI disk
    Nov 04 21:59:09 arch kernel: usb 3-2: new full-speed USB device number 2 using uhci_hcd
    Nov 04 21:59:09 arch kernel: tsc: Refined TSC clocksource calibration: 2399.950 MHz
    Nov 04 21:59:09 arch kernel: EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
    Nov 04 21:59:09 arch systemd[1]: systemd 208 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)
    Nov 04 21:59:09 arch systemd[1]: Set hostname to <arch>.
    Nov 04 21:59:09 arch kernel: Switched to clocksource tsc
    Nov 04 21:59:09 arch systemd[1]: Failed to load default target: No such file or directory
    Nov 04 21:59:09 arch systemd[1]: Trying to load rescue target...
    Nov 04 21:59:09 arch systemd[1]: Starting Encrypted Volumes.
    Nov 04 21:59:09 arch systemd[1]: Reached target Encrypted Volumes.
    Nov 04 21:59:09 arch systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
    Nov 04 21:59:09 arch systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
    Nov 04 21:59:09 arch systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
    Nov 04 21:59:09 arch systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
    Nov 04 21:59:09 arch systemd[1]: Starting Journal Socket.
    Nov 04 21:59:09 arch systemd[1]: Listening on Journal Socket.
    Nov 04 21:59:09 arch systemd[1]: Starting Setup Virtual Console...
    Nov 04 21:59:09 arch systemd[1]: Starting Apply Kernel Variables...
    Nov 04 21:59:09 arch systemd[1]: Started Set Up Additional Binary Formats.
    Nov 04 21:59:09 arch systemd[1]: Started Load Kernel Modules.
    Nov 04 21:59:09 arch systemd[1]: Mounted FUSE Control File System.
    Nov 04 21:59:09 arch systemd[1]: Mounting POSIX Message Queue File System...
    Nov 04 21:59:09 arch systemd[1]: Mounting Huge Pages File System...
    Nov 04 21:59:09 arch systemd[1]: Mounting Configuration File System...
    Nov 04 21:59:09 arch systemd[1]: Starting Journal Service...
    Nov 04 21:59:09 arch systemd[1]: Started Journal Service.
    Nov 04 21:59:09 arch systemd-journal[120]: Journal started
    -- Subject: The Journal has been started
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- The system journal process has been starting up, opened the journal
    -- files for writing and is now ready to process requests.
    Nov 04 21:59:09 arch systemd[1]: Starting Create list of required static device nodes for the current kernel...
    -- Subject: Unit kmod-static-nodes.service has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit kmod-static-nodes.service has begun starting up.
    Nov 04 21:59:09 arch systemd[1]: Starting udev Kernel Socket.
    -- Subject: Unit systemd-udevd-kernel.socket has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-udevd-kernel.socket has begun starting up.
    Nov 04 21:59:09 arch systemd[1]: Listening on udev Kernel Socket.
    -- Subject: Unit systemd-udevd-kernel.socket has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-udevd-kernel.socket has finished starting up.
    -- The start-up result is done.
    Nov 04 21:59:09 arch systemd[1]: Starting udev Control Socket.
    -- Subject: Unit systemd-udevd-control.socket has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-udevd-control.socket has begun starting up.
    Nov 04 21:59:09 arch systemd[1]: Listening on udev Control Socket.
    -- Subject: Unit systemd-udevd-control.socket has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-udevd-control.socket has finished starting up.
    -- The start-up result is done.
    Nov 04 21:59:09 arch systemd[1]: Starting udev Coldplug all Devices...
    -- Subject: Unit systemd-udev-trigger.service has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-udev-trigger.service has begun starting up.
    Nov 04 21:59:09 arch systemd[1]: Mounting Debug File System...
    -- Subject: Unit sys-kernel-debug.mount has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit sys-kernel-debug.mount has begun starting up.
    Nov 04 21:59:09 arch systemd[1]: Expecting device dev-sda4.device...
    -- Subject: Unit dev-sda4.device has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit dev-sda4.device has begun starting up.
    Nov 04 21:59:09 arch systemd[1]: Expecting device dev-disk-by\x2duuid-32d1daa9\x2daa59\x2d4ac1\x2da592\x2d23aa1ae655c5.device...
    -- Subject: Unit dev-disk-by\x2duuid-32d1daa9\x2daa59\x2d4ac1\x2da592\x2d23aa1ae655c5.device has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit dev-disk-by\x2duuid-32d1daa9\x2daa59\x2d4ac1\x2da592\x2d23aa1ae655c5.device has begun starting up.
    Nov 04 21:59:09 arch systemd[1]: Mounting Temporary Directory...
    -- Subject: Unit tmp.mount has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit tmp.mount has begun starting up.
    Nov 04 21:59:09 arch systemd[1]: Started File System Check on Root Device.
    -- Subject: Unit systemd-fsck-root.service has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-fsck-root.service has finished starting up.
    -- The start-up result is done.
    Nov 04 21:59:09 arch systemd[1]: Starting Remount Root and Kernel File Systems...
    -- Subject: Unit systemd-remount-fs.service has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-remount-fs.service has begun starting up.
    Nov 04 21:59:09 arch systemd[1]: Starting Root Slice.
    -- Subject: Unit -.slice has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit -.slice has begun starting up.
    Nov 04 21:59:09 arch systemd[1]: Created slice Root Slice.
    -- Subject: Unit -.slice has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit -.slice has finished starting up.
    -- The start-up result is done.
    Nov 04 21:59:09 arch systemd[1]: Starting System Slice.
    -- Subject: Unit system.slice has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit system.slice has begun starting up.
    Nov 04 21:59:09 arch systemd[1]: Created slice System Slice.
    -- Subject: Unit system.slice has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit system.slice has finished starting up.
    -- The start-up result is done.
    Nov 04 21:59:09 arch systemd[1]: Expecting device dev-disk-by\x2duuid-bdf255b1\x2d60c6\x2d4714\x2d8dc8\x2d5bd057b49aaa.device...
    -- Subject: Unit dev-disk-by\x2duuid-bdf255b1\x2d60c6\x2d4714\x2d8dc8\x2d5bd057b49aaa.device has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit dev-disk-by\x2duuid-bdf255b1\x2d60c6\x2d4714\x2d8dc8\x2d5bd057b49aaa.device has begun starting up.
    Nov 04 21:59:09 arch systemd[1]: Started Apply Kernel Variables.
    -- Subject: Unit systemd-sysctl.service has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-sysctl.service has finished starting up.
    -- The start-up result is done.
    Nov 04 21:59:09 arch systemd[1]: Mounted POSIX Message Queue File System.
    -- Subject: Unit dev-mqueue.mount has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit dev-mqueue.mount has finished starting up.
    -- The start-up result is done.
    Nov 04 21:59:09 arch systemd[1]: Mounted Huge Pages File System.
    -- Subject: Unit dev-hugepages.mount has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit dev-hugepages.mount has finished starting up.
    -- The start-up result is done.
    Nov 04 21:59:09 arch systemd[1]: Mounted Configuration File System.
    -- Subject: Unit sys-kernel-config.mount has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit sys-kernel-config.mount has finished starting up.
    -- The start-up result is done.
    Nov 04 21:59:09 arch systemd[1]: Mounted Debug File System.
    -- Subject: Unit sys-kernel-debug.mount has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit sys-kernel-debug.mount has finished starting up.
    -- The start-up result is done.
    Nov 04 21:59:09 arch systemd[1]: Mounted Temporary Directory.
    -- Subject: Unit tmp.mount has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit tmp.mount has finished starting up.
    -- The start-up result is done.
    Nov 04 21:59:09 arch systemd[1]: Started Create list of required static device nodes for the current kernel.
    -- Subject: Unit kmod-static-nodes.service has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit kmod-static-nodes.service has finished starting up.
    -- The start-up result is done.
    Nov 04 21:59:09 arch systemd[1]: Started udev Coldplug all Devices.
    -- Subject: Unit systemd-udev-trigger.service has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-udev-trigger.service has finished starting up.
    -- The start-up result is done.
    Nov 04 21:59:09 arch systemd[1]: Starting Create static device nodes in /dev...
    -- Subject: Unit systemd-tmpfiles-setup-dev.service has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-tmpfiles-setup-dev.service has begun starting up.
    Nov 04 21:59:09 arch systemd[1]: Started Remount Root and Kernel File Systems.
    -- Subject: Unit systemd-remount-fs.service has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-remount-fs.service has finished starting up.
    -- The start-up result is done.
    Nov 04 21:59:09 arch systemd[1]: Starting Load/Save Random Seed...
    -- Subject: Unit systemd-random-seed.service has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-random-seed.service has begun starting up.
    Nov 04 21:59:09 arch kernel: EXT4-fs (sda1): re-mounted. Opts: data=ordered
    Nov 04 21:59:09 arch systemd[1]: Started Load/Save Random Seed.
    -- Subject: Unit systemd-random-seed.service has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-random-seed.service has finished starting up.
    -- The start-up result is done.
    Nov 04 21:59:09 arch systemd[1]: Started Create static device nodes in /dev.
    -- Subject: Unit systemd-tmpfiles-setup-dev.service has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mail

  • Help, MBP 2,2 won't turn into Standby after upgrade to 10.7.2

    Recently I've upgraded from 10.7.1 to 10.7.2 via the Software-update utility, however now my MBP model 2,2 won't turn into standby mode when it is connected to the power adapter. Not when I close the lid, or when I select Standby via Apple -> Standby.
    On the other hand, when my MBP is running on battery there is no problem with going into Standby mode, so I thing it has something to do with the settings that are suddenly changed...
    Does anyone now if the settings have changed somehow? Or where I can change the settings?
    Thanks in advance!

    Hello Bastiaan,
    The first two days after installation of 10.7.2 and the Aperture update my laptop also refused to go to sleep, but that behaviour stopped recently all by its own. When I looked at the Activity monitor I saw the mac was indexing spotlight and rebuilding libraries, so probably it did not want to go to sleep while there still was critical work to be done to migrate properly to iCloud.
    I do not know of any other preference settings that might prevent sleep.
    So perhaps you should look at the Activity Monitor, if some high priority process is running, that might prevent sleep.
    If closing the lid does not work, that might be a hardware problem, but it seems to be unlikely, since it works when on battery power. Does your computer go to sleep when on power adapter, if you set the computer sleep interval to a very short time?
    Regards
    Léonie

  • My new macbook pro retina randomly goes into standby mode

    My new macbook pro retina randomly goes into standby mode. I have to close the screen and wait a few seconds and re-open it in order for it to come back on.
    Sometimes it immediately goes back into standby mode again after closing and reopening the screen. I have checked the battery level everytime, and it has never been below 40% when this occurs. Is this a Mountain Lion issue?

    Well I fixed my problem.
    I took it into the Apple store. Even without the other two monitors they were able to recreate the problem. One symptom (I had) was that one of the Hot Corners was set to Disable screen saver. If you then put your cursor there, you'd go into screen saver mode. Change the setting to another corner and the problem follows you there.
    The Apple person at the Genius bar logged out as me and back in as test and same problem. He tried some stuff and finally said I needed to wipe the drive and reinstall the OS (Lion). I'd only had the machine for 12 hours and had just migrated my data to it, so I didn't mind doing that. I did it at home.
    Problem solved.
    BUT... then I reinstalled the driver for my EVGA UV Plus 19 (most current drivers) and bingo problem back. Uninstall. Problem gone. I'm now using mini display port to DVI for one monitor and HDMI for the other I think the machine is a bit warmer this way (versus using a USB to the EVGA device) but at least it's not sleeping all the time. Someone might say "it (the heat) is your imagination" or something else. Or someone might say "use the other thunderbolt port for another mini-display port to DVI" but I need that for the LAN... c'est la vie.
    Maybe I'll write to evga and see what they say. Maybe they'll fix their driver and/or Apple will fix it.

  • Hard drive wakes up immediately after being put into standby

    I have an IDE disk which, till now, I used to keep in standby mode (it makes an audible humming noise when it's working which annoys me a lot :<). Today I noticed that after running `hdparm -y' on it, it would spin down but then it would immediately spin up again. I'm certain that the disk isn't being used and doesn't have any partitions mounted anywhere on the filesystem. Still, I'm unable to pinpoint the reason it's waking up.
    Any ideas on why this is happening?
    Edit: It appears that the disk gets into standby by itself after 10 minutes. I wish I knew where this value is coming from. O.o
    Edit2: Those 10 minutes must be coming from `hdparm -S1 /dev/sdb'; maybe the hard drive has a lower limit in regard to this setting. :3
    (I'm not sure what kind of information would be useful in order to troubleshoot this issue, but below are some bits I believe are relevant)
    Failed attempt to put the drive into standby:
    [root@foutboxd ~]# hdparm -y /dev/sdb; hdparm -C /dev/sdb; sleep 1; hdparm -C /dev/sdb
    /dev/sdb:
    issuing standby command
    /dev/sdb:
    drive state is: standby
    /dev/sdb:
    drive state is: active/idle
    hdparm -I:
    [root@foutboxd ~]# hdparm -I /dev/sdb
    /dev/sdb:
    ATA device, with non-removable media
    Model Number: WDC WD2500SB-01KBC0
    Serial Number: WD-WCAL77403899
    Firmware Revision: 08.02D08
    Standards:
    Supported: 6 5 4
    Likely used: 8
    Configuration:
    Logical max current
    cylinders 16383 16383
    heads 16 16
    sectors/track 63 63
    CHS current addressable sectors: 16514064
    LBA user addressable sectors: 268435455
    LBA48 user addressable sectors: 488397168
    Logical/Physical Sector size: 512 bytes
    device size with M = 1024*1024: 238475 MBytes
    device size with M = 1000*1000: 250059 MBytes (250 GB)
    cache/buffer size = 8192 KBytes (type=DualPortCache)
    Capabilities:
    LBA, IORDY(can be disabled)
    Standby timer values: spec'd by Standard, with device specific minimum
    R/W multiple sector transfer: Max = 16 Current = 16
    Recommended acoustic management value: 128, current value: 254
    DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
    Cycle time: min=120ns recommended=120ns
    PIO: pio0 pio1 pio2 pio3 pio4
    Cycle time: no flow control=120ns IORDY flow control=120ns
    Commands/features:
    Enabled Supported:
    * SMART feature set
    Security Mode feature set
    * Power Management feature set
    * Write cache
    * Look-ahead
    * Host Protected Area feature set
    * WRITE_BUFFER command
    * READ_BUFFER command
    * DOWNLOAD_MICROCODE
    Power-Up In Standby feature set
    * SET_FEATURES required to spinup after power up
    SET_MAX security extension
    * Automatic Acoustic Management feature set
    * 48-bit Address feature set
    * Device Configuration Overlay feature set
    * Mandatory FLUSH_CACHE
    * FLUSH_CACHE_EXT
    * SMART error logging
    * SMART self-test
    * SMART Command Transport (SCT) feature set
    * SCT Long Sector Access (AC1)
    * SCT LBA Segment Access (AC2)
    * SCT Error Recovery Control (AC3)
    * SCT Features Control (AC4)
    * SCT Data Tables (AC5)
    Security:
    Master password revision code = 65534
    supported
    not enabled
    not locked
    not frozen
    not expired: security count
    not supported: enhanced erase
    HW reset results:
    CBLID- above Vih
    Device num = 0 determined by the jumper
    Checksum: correct
    smartctl --all:
    [root@foutboxd ~]# smartctl --all /dev/sdb
    smartctl version 5.38 [x86_64-unknown-linux-gnu] Copyright (C) 2002-8 Bruce Allen
    Home page is http://smartmontools.sourceforge.net/
    === START OF INFORMATION SECTION ===
    Model Family: Western Digital Caviar RE EIDE family
    Device Model: WDC WD2500SB-01KBC0
    Serial Number: WD-WCAL77403899
    Firmware Version: 08.02D08
    User Capacity: 250,059,350,016 bytes
    Device is: In smartctl database [for details use: -P show]
    ATA Version is: 6
    ATA Standard is: Exact ATA specification draft version not indicated
    Local Time is: Wed Mar 11 21:47:50 2009 EET
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled
    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: PASSED
    General SMART Values:
    Offline data collection status: (0x84) Offline data collection activity
    was suspended by an interrupting command from host.
    Auto Offline Data Collection: Enabled.
    Self-test execution status: ( 0) The previous self-test routine completed
    without error or no self-test has ever
    been run.
    Total time to complete Offline
    data collection: (6951) seconds.
    Offline data collection
    capabilities: (0x7b) SMART execute Offline immediate.
    Auto Offline data collection on/off support.
    Suspend Offline collection upon new
    command.
    Offline surface scan supported.
    Self-test supported.
    Conveyance Self-test supported.
    Selective Self-test supported.
    SMART capabilities: (0x0003) Saves SMART data before entering
    power-saving mode.
    Supports SMART auto save timer.
    Error logging capability: (0x01) Error logging supported.
    No General Purpose Logging support.
    Short self-test routine
    recommended polling time: ( 2) minutes.
    Extended self-test routine
    recommended polling time: ( 88) minutes.
    Conveyance self-test routine
    recommended polling time: ( 5) minutes.
    SCT capabilities: (0x003f) SCT Status supported.
    SCT Feature Control supported.
    SCT Data Table supported.
    SMART Attributes Data Structure revision number: 16
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
    1 Raw_Read_Error_Rate 0x000b 200 200 051 Pre-fail Always - 0
    3 Spin_Up_Time 0x0007 236 124 021 Pre-fail Always - 708
    4 Start_Stop_Count 0x0032 098 098 040 Old_age Always - 2680
    5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
    7 Seek_Error_Rate 0x000b 200 200 051 Pre-fail Always - 0
    9 Power_On_Hours 0x0032 081 081 000 Old_age Always - 14289
    10 Spin_Retry_Count 0x0013 100 100 051 Pre-fail Always - 0
    11 Calibration_Retry_Count 0x0013 100 100 051 Pre-fail Always - 0
    12 Power_Cycle_Count 0x0032 098 098 000 Old_age Always - 2365
    194 Temperature_Celsius 0x0022 123 092 000 Old_age Always - 27
    196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
    197 Current_Pending_Sector 0x0012 200 200 000 Old_age Always - 0
    198 Offline_Uncorrectable 0x0012 200 200 000 Old_age Always - 0
    199 UDMA_CRC_Error_Count 0x000a 200 253 000 Old_age Always - 0
    200 Multi_Zone_Error_Rate 0x0009 200 200 051 Pre-fail Offline - 0
    SMART Error Log Version: 1
    No Errors Logged
    SMART Self-test log structure revision number 1
    No self-tests have been logged. [To run self-tests, use: smartctl -t]
    SMART Selective self-test log data structure revision number 1
    SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
    1 0 0 Not_testing
    2 0 0 Not_testing
    3 0 0 Not_testing
    4 0 0 Not_testing
    5 0 0 Not_testing
    Selective self-test flags (0x0):
    After scanning selected spans, do NOT read-scan remainder of disk.
    If Selective self-test is pending on power-up, resume after 0 minute delay
    Last edited by foutrelis (2009-03-12 10:18:25)

    Here is what i get when i try that command.:
    $ sudo hdparm -B 254 /dev/sdc
    /dev/sdc:
    setting Advanced Power Management level to 0xfe (254)
    HDIO_DRIVE_CMD failed: Input/output error
    APM_level = not supported
    I tried other values also and its always the same error.
    I just did another try with -y and the drive stayed in standby during ±40 minutes this time. The most annoying part is that is something that was not happening before I am pretty sure that it would stay in standby for days.
    I also included my results for hdparm -I.:
    $ sudo hdparm -I /dev/sdc
    /dev/sdc:
    ATA device, with non-removable media
    Model Number: WDC WD800JB-00JJC0
    Serial Number: WD-WCAM9N730552
    Firmware Revision: 05.01C05
    Standards:
    Supported: 6 5 4
    Likely used: 8
    Configuration:
    Logical max current
    cylinders 16383 16383
    heads 16 16
    sectors/track 63 63
    CHS current addressable sectors: 16514064
    LBA user addressable sectors: 156299375
    Logical/Physical Sector size: 512 bytes
    device size with M = 1024*1024: 76318 MBytes
    device size with M = 1000*1000: 80025 MBytes (80 GB)
    cache/buffer size = 8192 KBytes
    Capabilities:
    LBA, IORDY(can be disabled)
    Standby timer values: spec'd by Standard, with device specific minimum
    R/W multiple sector transfer: Max = 16 Current = 1
    Recommended acoustic management value: 128, current value: 254
    DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
    Cycle time: min=120ns recommended=120ns
    PIO: pio0 pio1 pio2 pio3 pio4
    Cycle time: no flow control=120ns IORDY flow control=120ns
    Commands/features:
    Enabled Supported:
    * SMART feature set
    Security Mode feature set
    * Power Management feature set
    * Write cache
    * Look-ahead
    * Host Protected Area feature set
    * WRITE_BUFFER command
    * READ_BUFFER command
    * DOWNLOAD_MICROCODE
    SET_MAX security extension
    * Automatic Acoustic Management feature set
    * Device Configuration Overlay feature set
    * Mandatory FLUSH_CACHE
    * SMART error logging
    * SMART self-test
    * SMART Command Transport (SCT) feature set
    * SCT Long Sector Access (AC1)
    * SCT LBA Segment Access (AC2)
    * SCT Error Recovery Control (AC3)
    * SCT Features Control (AC4)
    * SCT Data Tables (AC5)
    Security:
    Master password revision code = 65534
    supported
    not enabled
    not locked
    frozen
    not expired: security count
    not supported: enhanced erase
    HW reset results:
    CBLID- above Vih
    Device num = 0 determined by the jumper
    Checksum: correct

  • External screen doesn't go into standby when putting MacBook Pro into sleep

    I'm using a new MacBook Pro with an external monitor (DELL P2411H) through a Mini Displayport to DVI adapter.
    When putting the Macbook into sleepmode, the external screen goes into standby but immediately wakes up, then goes back into standby and wakes up ... this cycle doesn't stop. The only option is to manually push the powerbutton on the display.
    I'm having this issue too when using a MacBook Pro 13", so it's not a single issue.

    I got similar Problem, my external monitor will go to standby mode and then switch on immediately, and the go to sleep , and the monitor will show no signal detect

  • My 3050 J610 printer goes into standby or sleep mode and then I cannot print docs to it wirelessly

    Everytime I do not print something for a few hours, my printer goes into standby or sleep mode.  When it does this, it cannot be used to print from my laptop or android to it.  Is there a way to set this up so that it doesn't "go to sleep" and it is always available to me to print with.  I like the printer, but it seems kind of off that you cannot print on it wirelessly and it is considered a WIRELESS printer.  That's the only reason I bought it and now I can't even use it without walking downstairs and turning the printer back on again.  If I wanted to do that every time I would just print from my main computer!
    Thanks,
    Ashley
    This question was solved.
    View Solution.

    Ok, I know this thread is a little old, but it would not allow me to start a new one, since I am new. I am having the same issues with my 3050 J610 as everyone else. It makes you think there is a wireless connection problem, but that is not the case. The printer goes into a standby mode and there is no way to bring it out of it, unless you cycle the printer. The panel buttons will still work, you just lose the ability to print wirelessly.
    I have had my 3050 J610 in two different rooms, master bedroom and basement office. Both areas work well when it is connected and awake. After a while of inactivity, it goes into standby mode and cannot print wirelessly. Here are steps I have taken so far:
    When the printer goes into standby and will not print wirelessly, I have check to make sure there is still a connection between the router and the printer - There is
    I have set a static Id for the printer at .210
    Cycling the printer brings the connection back instantly.
    The front panel buttons work just fine when it does not have connectivity
    In the basement, the machine has excellent signal and connection.
    I have checked the recommendations in this thread, and like others, there are no options under the advanced tab of the maintenance page. The problem is a standby or sleep issue. When this arises, it has connection to the router, but the wireless computer does not have connection to the machine. I know when it was in the bedroom, the light would blink 3 or 4 times now and then throughout the night. We need a way to turn off the standby, or bring the machine out of standby mode. It is not an issue of the router, channel, interference, or software. It is the sole issue of standby or sleep modes. I have been pulling my hair out for almost two years over this issue. I swore I would not buy another HP product after the problems I had with a printer and laptop. But I thought I would give HP another chance.

  • Computer does not automaticatly go into Standby when iTunes 9 running

    Hi
    I have Windows XP computer and have installed iTunes on it for my iPod.
    I have set on the 'power options properties' panel 'Power Schemes' tab for the computer to go into standby automatically if idle after 5 mins. This works well with any programs running EXCEPT iTunes. I had the same problem on my last computer - the problem is specifically with iTunes.
    I have chosen iTunes settings that do not share the library or search for remote speakers etc but nothing works.
    Any ideas welcome?
    Thanks
    Tim

    What OS is PC running?
    Is your device connected to the PC while going into standby mode?
    Click here to Backup the data on your BlackBerry Device! It's important, and FREE!
    Click "Accept as Solution" if your problem is solved. To give thanks, click thumbs up
    Click to search the Knowledge Base at BTSC and click to Read The Fabulous Manuals
    BESAdmin's, please make a signature with your BES environment info.
    SIM Free BlackBerry Unlocking FAQ
    Follow me on Twitter @knottyrope
    Want to thank me? Buy my KnottyRope App here
    BES 12 and BES 5.0.4 with Exchange 2010 and SQL 2012 Hyper V

  • Unable to paste clips from source monitor into the timeline with buttons

    hi,
    working with the newest version of premiere pro cc 2014.
    I'am unable to paste clips from the source monitor into the timeline by neither using the buttons below the source monitor nor hitting the shortcut "," .
    dragging the clip in the timeline still works... is there a hidden setting to enable this functions again or is it a bug?
    thanks in advance
    yannick

    Thanks a lot!
    Further Information: Adobe Premiere Pro Help | Source patching and track targeting

  • Manually set Monitor Profile

    Instead of Photoshop, et al using my Win7 x64 ICC monitor profile, I would like to set it manually, as I'm able to do in other applications.  Is this possible? 
    The reason why is that I have a Dell U3014 and using the software that comes with it, I want to use its sRGB mode (and an associated sRGB profile from my Spyder 4 set as my Windows default) for all of my regular apps, and AdobeRGB mode (and profile) for my CS and other color-aware apps. My other apps DxO, PhotoMechanic, Canon SLR apps, etc. let me choose the profile.

    I would think that your calibration software would create a color profile for your display and set it into its device drivers color management configuration and set something up to load the Video Adapter LUT when the system boots up using the values stored in you displays color profile.  I think the software changes your systems displays color management configuration default profile. If not I think you should.
    When you edit images in Photoshop you should be editing them in a standard color space like sRGB, Adobe RGB or ProPhotoRGB.  When ever Photoshop renders an image for you it will use the document color profile and your displays color profile to display the best colors you display is capable of displaying for the image.  You don't set your displays profile for Photoshop. Photoshop retrieves your displays profile from your system configuration.

  • Satellite P10 automatically goes into Standby after 15 minutes

    My Satellite P10 automatically goes into Standby after 15 minutes. This is a setting that is controlled by the Toshiba Power Management settings, or the Toshiba Console.
    When I change the settings there the system still goes into Standby after 15 minutes. When I go to Control Panel/Performance and Maintenance/Power Options, it tells me to go to the Toshiba Power Management to change the settings, but I can still see the settings in grey stating 15 minutes standby time.
    But in the Toshiba Power Management I can't seem to be able to ajust Standby settings so that they actually work. There must be a trick to it..
    Can anyone help me figure it out?
    Thanks a lot,
    Lerak

    Thank you for your replies. As I now understand it there are 3 power management utilities fighting for control of the power management settings:
    1) The windows OS power options("Power Option Properties, from the control panel/performance and maintenance/power options);
    this utility is overridden by:
    2) Toshiba Power management;
    and
    3) the "power save modes", activated by pressing the Function key and the F2 key, which in turn can override the Toshiba Power management.
    If this last Function/F2 combination is used to change the power save modes, the windows OS power settings (which are shown in grey and cannot be changed because this is overridden by the Toshiba Power management) DO actually change.
    Hold down the Function key (Fn) and press F2, holding down the Fn key. Each time you then press the F2 key again you scroll down the different "Power Schemes". The last mode is called: Toshiba Power Management. One would think that by choosing this setting the Toshiba Power management utility would effectively take over control of the power settings. Unfortunately this does not seem to be the case..
    At least using this last option provides a workaround. Some of the "Power Schemes" disable the standby options.

  • Have to unwire computer everytime laptop goes into standby

    My laptop has an automatic setting to go into standby mode every thirty minutes or so. I come back turn it back on and my wireless connection is lost. So I connect the laptop to the back of my WRT54GS router and run unwire this computer again and again. Is there a way that it will stay connected?

    is your laptop running on windows xp or vista?
    automatically a laptop should save the network that it tried to connect to, so when you boot up your computer it should automatically connect to the chosen network right. how about adding your network in the system or manually adding up your network to your saved networks and removing all the other networks that you don't use...

  • [svn] 3493: Fix bug setting focus into an A. 2 application that is in a dialog.

    Revision: 3493
    Author: [email protected]
    Date: 2008-10-06 13:40:22 -0700 (Mon, 06 Oct 2008)
    Log Message:
    Fix bug setting focus into an A.2 application that is in a dialog.
    QE: YES
    Doc:
    Checkintests: Marshall Plan mustella tests
    Reviewer: Carol
    Bugs: SDK-17177
    SystemManager.as
    On mouse down, change the test from "the click was in a bridged application", to "the click is in a bridged application and it has the same focus manager as the document". A bridged application that is in a dialog will have a different focus manager than the document.
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-17177
    Modified Paths:
    flex/sdk/branches/3.0.x/frameworks/projects/framework/src/mx/managers/SystemManager.as

    Thanks Jutapa.
    When I ran the DPC Latency Checker, there were no significant hiccups, and nothing abnormal at all when the skips occurred. The PCI Latency Tool had no effect on the issue, either (I tried many different latency options, between 0 and 248). But maybe they'll help other people with this or similar problems!
    Besides that, I tried logging huge amounts of data with the performance monitor and there's no consistent abnormalities at the times the skips occur as far as CPU usage or any other measurable variables go.
    I'll check out http://musicxp.net! I'd tried fresh installs and disabling all unnecessary system services and startup programs before and it also had absolutely no effect, but that's probably not what MusicXP.net advises, so I'll take a look. Thanks!

  • Putting it into standby before switching off

    I'm using ATV without a monitor and controlled through Remote app.
    At present I do not have a way to put it into standby before switching it off.
    It does not seem to spin down unless put into standby.
    Does anyone know if I could program a 3rd party remote to switch the ATV into standby?
    Failing that should I just wait for the nice people at "Remote" or iTunes to program a button for that.

    I'm just lazy and don't close down applications as often as I should.
    More honestly (although I don't close applications often enough when I've finished with them) it's more because I do a lot of video editing.

Maybe you are looking for