Solaris 10 09/10 fails to start X with NVidia card

Hi folks,
I've just set up a new workstation for Solaris 10 x86, but I can't seem to get X to start.
I've got two NVidia 6200 cards on PCI (as the board doesn't have PCIe yet) which should be fairly mainstream.
However, on startup I get in the syslog "[ID 702911] nvidia: nv_intr_setup_fixed: ddi_intr_enable failed. nv_setup_intr failed."
and then X throws me an error into /var/dt/Xerrors that it can't find any suitable device.
This makes me wonder, as there is also an ATI Rage2 onboard graphics chip which works fine with X when I remove the NVidias.
However, it is dead slow so I'd prefer to disable it again, or use it only for console, and X on the nvidias.
Has anyone got Solaris 10 running on that nv6200 or can enlighten me on what I may have misconfigured?
Other OSes (e.g. win2k3) run fine on all cards, so I can rule out a hardware defect.

First of all check the HCL to see if that card is supported. If it is then you have a complaint. If not, go to nvidia's site and look for a Solaris driver package for your card. They have tons of drivers and I got something working that didn't originally work in Solaris by using nvidia's driver package.

Similar Messages

  • Power Mac G5 fails to start up with Airport Extreme card in.

    Hello.
    I just received a 'new' Airport Extreme card for my Power Mac G5 1.8 (900fsb). I just installed it and it failed to start up with it in. The mac started up but without my Apple LCD and any USB devices. I did a PMU reset on the logic board and took out the Crucial 3rd party 512mb RAM and tried again but it won't start up. When I take the card out it's business as usual.
    Is it the card or the mac that's at fault? Has anyone had this problem too?
    Your help will be greatly appreciated.

    This problem can happen if:
    - the card has not been fully seated into its socket (doing that can take a firm push) or if you installed the card upside down
    - the card is defective
    - the card socket in the PowerMac G5 has broken or bent contact pins
    Check the installation you did with:
    http://www.info.apple.com/usen/cip/pdf/g5/apec_c.pdf
    If you are sure the card has been properly installed, you are gong to have to either (a) try a different Airport Extreme card or (b) let an Apple dealer or service center take a look at your PowerMac G5.

  • Errors Pku2ulog failed to start 0xC--35, Negolog failed to start, IDListenLog failed to start, P2PLog failed to start and HomegroupLog failed to start, all with the same failure code 0xC-- 35.

    Hi There,
    I'm getting the errors below and but I have not got any BSOD.
    The errors I'm getting in eventviewer are Pku2ulog failed to start 0xC--35, Negolog failed to start, IDListenLog failed to start, P2PLog failed to start and HomegroupLog failed to start, all with the same failure code 0xC-- 35.
    This is what the logs files says about each error.
    Pku2ulog:
    Unknown( 10): GUID=c36a26fb-03a9-d591-3984-dc17e4a48527 (No Format Information found).
    p2plog:
    Unknown( 89): GUID=fc9d5ca5-e6c8-627c-be74-e6e0a98bbf57 (No Format Information found).
    negolog:
    Unknown( 37): GUID=2553184f-6f2a-3198-ddb7-93ab1ad2d125 (No Format Information found).
    idlistenlog:
    Unknown( 10): GUID=418a567f-b393-1423-26aa-123149ef8882 (No Format Information found).
    homegrouplog:
    Unknown( 12): GUID=96f7a94a-4343-6ede-ff2b-dd1dafeed500 (No Format Information found).
    However, the 'Unknown(xx)' number changes times to times.
    Could you help me please?
    Thank you very much for your attention.
    Best Regards.

    Hi,
    If you have Home group set up, please go to Control Panel – Network and Sharing Center. Choose homegroup and sharing options and click “Leave the homegroup”.
    Juke Chou
    TechNet Community Support

  • Admin Server 4 fails to start up with new Internet Protocol (IP) address

    By default, the Netscape Admin Server 4.x uses the Internet Protocol (IP)
    address that was entered in its configuration at the time the server was
    installed. However, if a system administrator decides to change the IP address,
    the server will fail to start.<BR>
    <P>
    The following is an example of the error message:<BR>
    <P>
    # ./start-admin
    Info: Cache expiration set to 600 seconds
    Netscape-Administrator/4.0 B99.035.2034
    startup failure: could not bind to port 4050, IP address 208.12.45.56 (Invalid
    Argument)
    The error log will show:<BR>
    [29/Oct/1999:11:32:58] info: successful server startup
    [29/Oct/1999:11:32:58] info: Netscape-Administrator/4.0 B99.035.2034
    [29/Oct/1999:11:32:58] failure: startup failure: could not bind to port 4050,
    IP address 208.12.45.56 (Cannot assign requested address)
    <P>
    In addition, if the system administrator manually clears the IP address for the Admin
    Server in Console (by clicking the Configuration tab, clicking the Network tab,
    selecting Process Settings, and then selecting IP Address), the server will
    also fail to start. The following are examples of the error message and error
    log entries.
    <BR>
    # ./start-admin
    Info: Cache expiration set to 600 seconds
    Netscape-Administrator/4.0 B99.165.2023
    startup failure: could not bind to port 4100, IP address
    (Directory open error)
    The error log will show:<BR>
    [03/Dec/1999:09:32:43] info: successful server startup
    [03/Dec/1999:09:32:43] info: Netscape-Administrator/4.0 B99.165.2023
    [03/Dec/1999:09:32:43] failure: startup failure: could not bind to port 4100,
    IP address (Error 0)
    <P>
    These problems affect both Admin Server 4.0 and 4.1.
    <P>
    (See attachment)

    Hi Laurent,
    although I was given the advice earlier that I should simply take the machine back to the shop, or call the help centre, I ended up just praying that it would be OK.  A couple of days after I posted the message I think there was an update to download and install, just a regular one from Apple from the Software Update option for the operating system or it may have been one for Final Cut Pro X, and once it installed I never had the problem again, so my prayers were answered.
    It was pretty scary at the time because I thought it must be some hardware malfunction, but because it was resolved through an update it suggested it was a software issue.  Hopefully it is the same with you.
    I'm now running 10.7.2 and have had no recurrence of the problem in many months, thankfully.
    It might have nothing to do with it, but the only other two things that may have somehow caused errors in the system startup (and I doubt these will be "unrelated" to people who know how computers work better than I do, but I feel I should mention them just in case), but I also updated Final Cut Pro X from a glitchy version to version 10.0.2 around the same time, and I also had an application installed which didn't function correctly in OS10.7 called PowerController (a simple app that can start up the computer at a set time and play music from iTunes as an alarm clock) and it was in the group of apps that were set to start at the starting up of the computer.
    Anyway, I hope your problem is resolved as easily.  Pray about it too!

  • Solaris 10 x86 Installation Fails to Start

    I am trying to install Solaris 10 x86 05/08 on a Sony PCG-K115S laptop. The issue I am having is that the installation hangs after printing the copyright information and does not go any further. I get no error message or status as to what the installation is doing.
    I downloaded the dvd iso from sun website and verified the md5 checksum before burning the dvd more than once but the issue occurred in both dvds.
    The laptop currently has XP installed but there is 30GB of free unallocated/partitioned space on the disk.
    Are there any options I can active to debug the installation and see where and why it is stalling.
    Thank you,
    F.
    Edit 1:
    After some forum reading I activated the Kernel Debugger and verbose mode:
    The installation hangs after this line is printed out:
    echi0 is /pci@0,0/pci104d,8175@c,2
    loaded modules: [uppc neti ufs unix krtld uhci hook genunix ip usba specfs pcplusmp cpu.generic sctp arp]
    Does this strike a cord with anybody??
    Edit 2:
    After some more reading and investigation, I read that this could be caused by my USB controller not being recognoized or some USB 2.0 issues with Solaris 10.
    I have tried to deactive the usb system with the options "-B acpi_user_options=2" and "-B acpi_user_options=8" but with no luck. (I got about these on some some forum, not sure if they are correct).
    Any help is appreciated!!
    Thank you,
    F.
    Edited by: Fergus on Jul 6, 2008 2:22 AM
    Edited by: Fergus on Jul 7, 2008 9:12 PM

    OK, got a little further. I entered the incorrect value for the acpi-user-options, the number should have been in hex.
    So with options "-k -v -B acpi-user-options=0x8 -B install_media=cdrom" I get the install menu
    1. Interactive
    On selecting "1" for interactive, the install begins be halts quickly with an error:
    NOTICE: rtls0 -- link down
    ERROR: Unable to configure network interface
       Exiting to shell.Is there any way to disable the configuration of the network interfaces?? I don't need them for installation...
    Thank you for any help,
    F.

  • Windows 7 OSD failing at Starting Services with unexpected reboot

    Hello. My environment is SCCM 2012 R2. I have a Windows 7 task sequence that deploys a custom Windows 7 WIM file. The task sequence has been used for a number
    of years and the Windows 7 WIM file was updated with the latest security update but has been deployed out to many machines without issue since. I have a difficult problem that I am trying to figure out. Recently the build process started failing on a specific
    model of machine (Dell Optiplex 7020). See the attachment for the error message. The problem is it is only happening at one location. Other locations have not reported the problem. Also, some 7020s built at the problem location do successfully complete but
    when someone tries to use a USB device on the machine, it becomes unresponsive for up to 20 minutes.
    My assumption was that the driver package on the distribution point is corrupt. However, I have removed it and successfully added it back. I also noticed that
    is a memory dump file. I examined it and it points to the USB drivers. The problem is that I have compared the Windows 7 setup logs with a working 7020 from another location. There are no differences other than the location the drivers are pulled from. There
    are no errors in the setup logs or SCCM logs. The only items I can found to point to the cause of the failure is the dump file.
    Any recommendations on what I should look at next?

    The attachment didnt come across, can you post the smsts.log or upload it to OneDrive, etc?
    Daniel Ratliff | http://www.PotentEngineer.com |
    @PotentEngineer

  • Failing to start app with HCP runtime version 2.30

    Hello,
    This morning I have been unable to deploy and start an instance of my web app under newly released version 2.30 of the HANA Cloud Platform runtime.  Whilst the application appeared to be in status Started in the cockpit, trying to access it returned the "Service Unavailable" page.  I could not see any errors in the logs.  I tried deploying again, this time requesting runtime version 2.29 and everything was fine again.
    Likewise, simply trying to restart another instance, that was running fine yesterday under version 2.29, failed this morning under version 2.30.  Once again I resolved this by re-deploying the same WAR requesting version 2.29.
    Looks like there may be some issue with version 2.30.
    Cheers,
    Scott

    Hi Scott,
    Currently the latest runtime version is 2.34 - do you still face issues?
    If yes, please share logs as requested by Nikolai; if not, please take care to update this thread and eventually close it.
    Cheers,
    --Vlado (Moderator)

  • [Solved] kdm.service fails to start X with systemd 185-4

    Hello
    After updating systemd yesterday to 185-4 and booting my pc in the morning I found out that either the boot stops in the middle giving me just black screen or it would throw me to console prompt after some time.
    systemctl status kdm.service shows two errors
    Jul 1 11:20:57 pc kdm[285]: X server startup timeout, terminating
    Jul 1 11:21:08 pc kdm[285]: X server for display :0 cannot be started, session disabled
    The same can be observed in logs. However, there are no errors in Xorg.0.log.
    Moreover when I do
    systemctl stop kdm.service
    systemctl start kdm.service
    kdm loads fine and I can login to kde.
    I have temporarily reverted to 185-3 and the problem seems to be gone.
    Does anybody experience a similar issue?
    thanks
    Last edited by aya (2012-07-02 14:05:53)

    ~ $ ls -l /etc/systemd/system/graphical.target.wants/kdm.service
    lrwxrwxrwx 1 root root 35 мая 31 20:33 /etc/systemd/system/graphical.target.wants/kdm.service -> /usr/lib/systemd/system/kdm.service
    ~ $ cat /usr/lib/systemd/system/kdm.service
    cat: /usr/lib/systemd/system/kdm.service: No such file or directory.
    Also read - https://projects.archlinux.org/svntogit … 833ee7a0c8

  • Xorg fails to start, blackscreen with immovable mouse

    Since the last xorg-server update this happened, though I downgraded the package and it didn't fix it.

    AdrenalineJunky wrote:i've had the same problem once or twice - i booted to console and re-installed catalyst and all was well.
    Was it necessary to reinstall catalyst? That package just contains the license and the kernel module. I thought it's just catalyst-utils that needs reinstalling after Xorg updates due to some lib??? stuff getting overwritten?

  • 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

  • VM failed to start with Event ID 12140, 12010, 12030

    We are running VMs on Windows 2008. When trying to start one of VMs, we get the failed to start message with Event ID 12140, 12010 and 12030
    Log Name:      Microsoft-Windows-Hyper-V-Worker-Admin
    Source:        Microsoft-Windows-Hyper-V-Worker
    Event ID:      12140
    Task Category: None
    Level:         Error
    Description:
    The description for Event ID 12140 from source Microsoft-Windows-Hyper-V-Worker cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on
    the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    AutoDesk
    808419FF-6855-4DB9-8DD4-DBB30567B6E9
    E:
    %%2147942432
    0x80070020
    IDE/ATAPI
     1/0
    The locale specific resource for the desired message is not present
    Log Name:      Microsoft-Windows-Hyper-V-Worker-Admin
    Source:        Microsoft-Windows-Hyper-V-Worker
    Date:          9/12/2011 1:47:37 PM
    Event ID:      12010
    Task Category: None
    Level:         Error
    Description:
    The description for Event ID 12010 from source Microsoft-Windows-Hyper-V-Worker cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on
    the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    AutoDesk
    808419FF-6855-4DB9-8DD4-DBB30567B6E9
    Microsoft Emulated IDE Controller
    %%2147942432
    0x80070020
    {83F8638B-8DCA-4152-9EDA-2CA8B33039B4}
    The locale specific resource for the desired message is not present
    Log Name:      Microsoft-Windows-Hyper-V-Worker-Admin
    Source:        Microsoft-Windows-Hyper-V-Worker
    Date:          9/12/2011 1:50:42 PM
    Event ID:      12030
    Task Category: None
    Level:         Error
    Description:
    'AutoDesk' failed to start. (Virtual machine 808419FF-6855-4DB9-8DD4-DBB30567B6E9)
    Any help?
    Bob Lin, MVP, MCSE & CNE Networking, Internet, Routing, VPN Troubleshooting on
    http://www.ChicagoTech.net
    How to Setup Windows, Network, VPN & Remote Access on
    http://www.howtonetworking.com

    Hi,
    In order to perform the further research, please help me to collect the following information:
    1. What’s the operating system within the problematic VM?
    2. How many CPU and memory did you assign to this VM?
    3. Did you have any anti-virus software installed on the Hyper-V host machine?
    By the way, you can check the following link to see whether you can resolve the issue.
    http://www.chicagotech.net/netforums/viewtopic.php?f=3&t=5699
    Important Note: This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to
    you. Microsoft does not control these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there.
    There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet.
    Best Regards,
    Vincent Hu

  • Intel(r) Management Engine Interface fails to start

    HP G62 Notebook PC running 8 Gig of Memory and Windows 7 Professional 64 bit.
    Get message in Device Manager of this device failing to start.   with code 0000000A.  Have done Bios upgrade and checked for latest driver and the system tells me I have it already, yet this error still persists.

    Hi,
    It seems your machine has motherboard with Intel chips. And this problem occurs if you install a driver via Windows Update. You could try to upgrade the latest version driver from Intel, then this problem would be solved. Here is some information about Intel
    Management Engine:
    http://www.intel.com/en_US/Assets/PDF/general/ug_Intel_MEBX.pdf
    Notice: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this.
    “Also getting update failure on Microsoft SQL Server 2005 Service Pack 4 (KB2463332).”
    This is a Service Pack for SQL server. Since this is a SQL server related issue, I suggest you could post this problem to Microsoft SQL Server forum.
    http://social.technet.microsoft.com/Forums/en-US/category/sqlserver/
    The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us.
    William Tan
    TechNet Community Support

  • Solaris 10: BIND 9 Chroot Service fails to start with SVCADM but works when

    I recently upgraded with Solaris patches and after the reboot my Bind Named services (DNS) go into maintenance mode.
    bash-3.2# svcs -xv
    svc:/network/dns/server:chroot (?)
    State: maintenance since Thu Nov 01 00:22:19 2012
    Reason: Start method failed repeatedly, last exited with status 1.
    See: http://sun.com/msg/SMF-8000-KS
    See: man -M /usr/man -s 1M named
    See: /var/svc/log/network-dns-server:chroot.log
    Impact: This service is not running.
    Output from var/svc/log/network-dns-server:chroot.log below
    [ Nov 1 00:22:19 Executing start method ("/lib/svc/method/dns-server start chroot") ] dns-server: Executing: named -t /var/named/chroot/named -c /etc/named.conf /lib/svc/method/dns-server: named: cannot execute dns-server : start failed! Check syslog for further information. [ Nov 1 00:22:19 Method "start" exited with status 1 ]
    I can run named -t /var/named/chroot/named -c /etc/named.conf manually from as root from the command line the named process starts and DNS works.
    I thought this had something to do with permissions/file ownership or something like that. I have tried changing (chown/chgrp)the /var/named/chroot/named directory to root root and named root. I also did the same with the /var/named/chroot/named/named binary. I also tried the same types of things with the /etc/named.conf file. So far no luck.
    Any suggestions on how to figure this out would be greatly appreciated.

    Just read the mentioned thread because the answer is in it and duplicating that seems useless. Don't make it seem like you want the answer to be presented on a silver plate

  • Misconfigured rcap on Solaris 10 with zones - SMF fails to start rcap

    Hi,
    I have just installed Solaris 10 on a brand new T5220 server (Niagara processor, 16GB of RAM). After creating first non-global zone with capped memory and cpu, SMF fails to start rcap service:
    +root@bs10 [~]$ svcs -xv+
    svc:/system/rcap:default (resource capping daemon)
    State: maintenance since Mon Nov 03 10:28:53 2008
    Reason: Start method exited with $SMF_EXIT_ERR_CONFIG.
    See: http://sun.com/msg/SMF-8000-KS
    See: man -M /usr/share/man -s 1M rcapd
    See: man -M /usr/share/man -s 1M rcapstat
    See: man -M /usr/share/man -s 1M rcapadm
    See: /var/svc/log/system-rcap:default.log
    Impact: This service is not running.
    Content of service's log:
    +root@bs10 [~]$ tail /var/svc/log/system-rcap:default.log+
    +[ Nov  3 09:36:21 Method "start" exited with status 96 ]+
    +[ Nov  3 10:25:37 Leaving maintenance because clear requested. ]+
    +[ Nov  3 10:25:37 Enabled. ]+
    +[ Nov  3 10:25:37 Executing start method ("/usr/lib/rcap/rcapd") ]+
    +[ Nov  3 10:25:37 Method "start" exited with status 0 ]+
    +[ Nov  3 10:26:59 Stopping because service disabled. ]+
    +[ Nov  3 10:27:00 Executing stop method (:kill) ]+
    +[ Nov  3 10:28:53 Executing start method ("/usr/lib/rcap/rcapd") ]+
    svc.startd could not set context for method: chdir: No such file or directory
    +[ Nov  3 10:28:53 Method "start" exited with status 96 ]+
    Clearing service status helps, but this error is reported after every system restart. FSS is set as the default system's scheduling class.
    Zone configuration:
    zonecfg:bs10z1> info
    zonename: bs10z1
    zonepath: /zones/bs10z1
    brand: native
    autoboot: true
    bootargs:
    pool:
    limitpriv:
    scheduling-class: FSS
    ip-type: exclusive
    inherit-pkg-dir:
    dir: /platform
    inherit-pkg-dir:
    dir: /install
    fs:
    dir: /opt/mirror1/oracle
    special: /dev/md/dsk/d105
    raw: /dev/md/rdsk/d105
    type: ufs
    +options: [rw]+
    net:
    address not specified
    physical: e1000g1
    capped-cpu:
    +[ncpus: 10.00]+
    capped-memory:
    physical: 6G
    +[swap: 6G]+
    +[locked: 4G]+
    rctl:
    name: zone.cpu-cap
    value: (priv=privileged,limit=1000,action=deny)
    rctl:
    name: zone.max-swap
    value: (priv=privileged,limit=6442450944,action=deny)
    rctl:
    name: zone.max-locked-memory
    value: (priv=privileged,limit=4294967296,action=deny)
    What have I missed?
    Edited by: Maciejos on Nov 3, 2008 2:29 AM

    The reason of this behave: the root's home directory was located on the filesystem different than root filesystem. After moving it everything works fine.

  • Solaris 10 Guest OS in VirtualBox: X-server fails to start

    I couldn't find a VirtualBox users/admins forum, so this seemed to be the next best place to post.
    I installed VBox (2.1.2) on Solaris 10 x86, and then created a Solaris 10 guest. After installing the guest additions package to the Solaris guest the X-server fails to start.
    I see the following message on the VBox console for the guest:
    The X-server can not be started on display :0...
    See file /var/dt/Xerror for details.The /var/dt/Xerrors file shows these messages.
    Server for display :0 terminated unexpectedly 1
    Server for display :0 can't be startedI found that removing (or renaming) the /etc/X11/xorg.conf file clears this problem up.
    Since this guest OS is going to be my SunRay server I don't know if removing the xorg.conf file is going to cause some other problems later on.
    Has anybody else seen this problem?
    And/or
    Does anybody know the xorg.conf file well enough to know how to fix this without completely removing the file?

    By default Solaris does not create an xorg.conf file. It probes for the values and uses what it finds. You can find several books on X Windows and one of those should be able to step you through the xorg.conf file.
    You can probably find an online version at some Linux Vendors documentation web site.
    alan

Maybe you are looking for