VM won't start, unable to mount VHD file

Hello,
Last night I powered off my Windows 8.1 Pro machine running Hyper-V and one of the virtual machines may have gotten forced down hard.  This morning when I tried to start it I am getting:
BOOTMGR is missing
Press Ctrl+Alt+Del to restart
My first suspicion was that the .VHD was corrupted and needed repairing.  In the VMware world I would mount the disk to another VM and use various tools on it (chkdsk, etc) I believe Windows actually makes this a little easier by allowing mounding of
a .VHD within disk manger.  I mount the disk and see the following image:
Although the size is correct the disk comes up as RAW (Which seems odd to this hyper-V newbie).  I am unable to explore the contents of the drive, I get the error "F:\ is not accessible.  The file or directory is corrupted and unreadable."
I have a crazy suspicion that the drive is still locked by Hyper-V as if it is still running.  Naturally I have confirmed the virtual machine appears offline.  Is it possible that some kind of lock was not fully released when the machine was powered
off?  Any other troubleshooting tips I could try?

Hi,
I don’t found the similar issue, if you have the backup of this vm, you can try to recovery it ,then try to start it again, or you can try the following method for the further
troubleshooting:
Method 1:
Backup this guest vm, use the VHD tool to fix that VHD.
Method 2:
Merge this vm checkpoint then try to start it again.
The VHD Tools download:
VHD tool
http://archive.msdn.microsoft.com/vhdtool
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

  • My laptop won't start without battery mounted

    Hello! I have a Compaq CQ61-200sq laptop and recently my battery just got "old". So for the time untill i will buy a new one a just took it out and try to use the laptop without battery, just with the AC adaptor pluged in. But, just i said it won't start if i don't mount the battery. If i took the battery out while it's on there is no problem.
    So, my question, beside what could be the problem, is if the problem will disapear with a new battery. I don't want to buy a new battery and still have problems.
    Thank you! 

    I updated it about two to three times and would still experience the same problem.
    Why update 3 times?!? If you run an update, and it installs normally, that it - done!
    There's a world of difference between running BatteryUpdate 1.2 and installing a new battery. In fact, if you read the linked page above, it states that the after you run battery update if you experience any of the listed problems you should contact AppleCare. Their first step will be to replace the battery. Could it be a logic board problem? Sure. Is that the first thing they'll do? No. By that reasoning, the first thing to try if your car fails to start on a cold morning is to put in a new engine...
    So, to the OP, contact Apple - or better yet, if it's convenient, go in to an Apple Store. Get a new battery. If the problem persists, go from there. The advantage of taking it into a Store is that they'll test it on the spot.

  • Toshiba M45-s269 Windows won't start-miss​ing or corrupt file

    Toshiba M45-s269 Windows xp sp3
    Recently got the message upon a restart that "Windows cannot start because a file is missing or corrupt" then names the file "<Windows root>\system32\ntoskrnl.exe."
    Screen show options to restart windows normally, in last known good config, safe mode, safe mode with command prompt or with networking.  All options only have the result of a 2-minute freeze-up and returning to the same screen after showing the Toshiba splash screen.
    I was able to F12 at splash screen which gives the option of what to reboot from: Multiple discs, single disc, floppy or networked.  Otherwise all options have same looped result notifying cannot start due to missing/corrupt file.....
    Having the factory recovery disc, I was able to select the single disc option with F12 at splash and try running a recovery from D:/.
    The disc, however, says it will reload Windows 98 (the computer came with  XP Home) and wants to re-format which will blow out EVERYTHING I have on the hard drive which is NOT an option for me!
    A while ago I was given a disc from a friend that has XP Professional. I have been trying to restore from that with less than expected results. Have gotten to a DOS promt and tried to COPY the file from XP Pro disc but being told cannot find the file. I'm most likely not doing something right. Don't know what destination to send it IF I'm able to copy the file anyway.
    Tried to load XP Pro on hard drive but computer sees the Home version and gives the message that loading 2 OS's is not recommended. Was hoping that XP Pro would simply over-write Home.
    Any help appreciated.  Thanks in advance,
    Rob

    Hi
    Setup CD is not delivered with your notebook, just recovery CD and recovery CD does not offer repair option.
    Try to obtain Microsoft Installations CD. Talk with your friends. I am pretty sure someone has this WXP installations CD. Check if you can do something using R option.
    Check also what Microsoft wrote about this issue:
    http://support.microsoft.com/?kbid=307545
    http://support.microsoft.com/kb/269075/en-us
    Good luck!

  • [solved] xfce4 won't start, "unable to load failsafe session"

    Hello, after a recent upgrade (i guess), I restarted xfce4 and I am now receiving this error message:
    Unable to load failsafe session
    Unable to determine a failsafe session name. Possible causes:
    xfconfd isn't running (D-Bus setup problem);
    environment variable $XDG_CONFIG_DIRS is set incorrectly (must include "/etc"),
    or xfce4-session is installed incorrectly
    While trying to restart xfce4 again.
    I'm using the radeon driver for an ati card btw.
    I have dbus and hal installed. I am using openbox just fine at this very moment, except that it won't logout without a ctrl-alt-backspace. So something is wrong. I wish to have xfce4 running again though.
    I have a very minimal xorg.conf, with no errors in my Xorg.0.log.
    Did this happen to anyone else? I searched the forum and people fixed this same error message by installing dbus, but I have dbus installed... so it's weird.
    Last edited by efourseven (2009-05-08 04:38:01)

    Do you run Arch64?
    If so, then
    # pacman -Sy dbus
    This thing will install "dbus *permissive-1" which, suprisingly enough, is not a dependency of xfce4. I don't know if it's built like that on purpose, or it's just a blunder... but it would make more sense to me if XFCE4 depended on that package.
    After installing that and restarting hal (which wouldn't run properly, anyway) your XFCE4 should start.
    I discovered that just recently on a virtual machine (normally I run 32-bit, and there is no such issue there).
    Last edited by scarecrow (2009-05-18 18:37:16)

  • Word won't start when 'double-clicking' .doc file

    I installed Microsoft Office X, (and removed the trial version that came with the machine). It runs fine if I start up the application and then open a file. However, if the application isn't running, and I double-click on a .doc file, I get an error message and Word doesn't start up.
    (By the way, when I first installed it, the same operation would start up the 'trial version'...so I used the microsoft remove program to eliminate it.)

    go to the .doc file.. get info in it.
    go to "Open with" select the new Microsoft Office, then click on the "Change All..." button.
    now all .doc files will be associated with the new install of Office.

  • Unable to mount iso file: mountpoint doesn't seem to exist?

    When I issue the command: sudo mount -o loop -t iso9660 /path/to/iso /mnt/point
    It always says that /mnt/point doesn't exist. I've tried using /mnt/iso (that I made) or /media or a directory in my home directory.
    If it makes a difference, I'm using systemd and KDE.

    pogeymanz wrote:
    I did, in fact create the directories I tried with mkdir /mnt/point
    Hmm. By having a loop device available, do you mean that /dev should have loop in it? Because it doesn't. I guess I need to recompile my kernel and make sure to enable loop devices?
    If I do ls /dev | grep loop, I just see 'loop-control', whatever that is.
    /dev/loop-control is a device that creates loop devices on demand. On first access, the kernel will reach into userspace and modprobe the loop module (if needed). If the module hasn't been loaded yet and you upgraded your kernel (deleting all your modules), you'll get the behavior you see.

  • [Solved] unable to mount harddisk partition or flash drive

    After recent updates to gnome 3.4.2,i am unable to mount  harddisk partition or flash drive .I have 2 year old arch installation with gnome.
    When i click on partitions in nautilus,it says "Unable to mount program files \n Not authorized to perform operation"
    Problem is not only while mounting partitions.
    Wherever we need authorization .Like changing date and time ,changing user accounts using gnome UI etc.The unlock button is greyed out permanently.
    even i am not able to shutdown using gnome menus. it just log me out only ,do not restart or shutdown.Though i can shutdown using shutdown command on commandline.
    i run gnome using daemon method. not through xinitrc .
    https://bugs.archlinux.org/task/25031?p … ekit#close
    I found a similar discussion in this bug. But since, i do not use xinitrc, it is unlikely they will help me.
    Can someone be kind enough to help me on this?
    Thanks in advance.
    Last edited by piyushbhatt (2012-09-11 05:48:57)

    maybe changes in udev or any other package
    you have polkit polkit-gnome
    and you user is in optical, disks and wheel groups?
    for me those above work in every sitation

  • My Premiere Elements 9 won´t start, it stars loading and then it stops.

    After replacing two drivers (as Adobe told me to because wasn´t showing the preview of vids, just sound) my premiere elements won´t start. I replaced the files and didn´t start. Then I replaced those files with the originals that I saved just in case, but the same issue. Does anyone know how to start the program again?
    Thank you.

    More information needed for someone to help... please click below and provide the requested information
    -Premiere Elements FAQ http://forums.adobe.com/thread/1042180
    This is a user to user forum, not Adobe support... so nobody here knows what Adobe told you to do... you need to provide details
    What is your exact brand/model graphics adapter (ATI or nVidia or ???)
    What is your exact graphics adapter driver version?
    Have you gone to the vendor web site to check for a newer driver?
    -If Windows, do NOT rely on Windows Update to have current driver information
    -you need to go direct to the vendor web site and check updates for yourself
    ATI Driver Autodetect http://support.amd.com/en-us/download/auto-detect-tool
    nVidia Driver Downloads http://www.nvidia.com/Download/index.aspx?lang=en-us

  • 10.4.4: Can't mount .dmg files or access iDisk

    Shortly after updating to 10.4.4 I noticed that my daily automated backups (using Backup 3) weren't working any more. I also found that I couldn't access the iDisk via the Finder icon, or via the Go > iDisk > My iDisk option in Finder. I can still upload to my iDisk using iWeb.
    I'm now also unable to mount .dmg files. When I open them in Finder or try to mount them using Disk Utility I get an error message saying that there are 'no child processes'.
    What can I do about these issues? Help would be greatly appreciated. Thanks in advance!

    Solved , by installing the 10.4.4 combo update!

  • Tiger won't start up, no volume to mount to?

    Hi everyone,
    I was doing some permissions repair and disk cleanup, when my power went out. Now Tiger won't start up! I get a full-screen shell with the following text:
    disk0s3: I/O error.
    disk0s3: I/O error.
    /etc/master.password: Input/output error
    disk0s3: I/O error.
    -sh: /etc/profile: Input/output error
    -sh-2.05b#
    If I leave the Mac on, the fans start spinning up slowly and keep building to a roar. I've left it on for about 1 minute, then shut it down.
    Starting up by holding the Command key down after the startup ding gets me a screen with a folder icon (?), which proceeds to turn into a smiley face and then the bootup sequence starts. It then goes back to the full-screen shell.
    I put in my Tiger (10.4) install disk, and the Disk Utility shows the Hard Drive, but the Macintosh HD volume is greyed out and won't / can't mount, be verified, or repaired.
    Trying to install so that I can archive / install yields no HDs that I can install to. Luckily I keep my PC around for just such an occurance
    So the question is, what is going on here? Thanks in advance,
    -Gary

    You are going to have to reformat the drive. If there is a chance of data recovery it would be best if you stop using the drive altogether. Find another Mac with Firewire. Connect the two by Firewire cable. Boot the "bad" computer into Target Disk Mode, then boot the "good" computer normally. The "bad" computer's disk drive should appear on the other computer's Desktop. If the drive is still accessible, then you may be able to recover your data.
    When you reformat the drive use the following procedure:
    1. Boot from your Tiger DVD. After the installer loads select Disk Utility from the Utilities menu.
    2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Click on the Partition tab in the DU main window.
    3. Set the number of partitions from the dropdown menu (use 1 partition unless you wish to make more.) Set the format type to Mac OS Extended (Journaled, if supported.) Click on the Partition button and wait until the volume(s) mount on the Desktop.
    4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
    5. Set the format type to Mac OS Extended (Journaled, if supported.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
    6. Click on the Erase button. The format process will take 30 minutes to an hour or more depending upon the drive size.

  • My iMac won't start. I have to press T and mount it to an old G4.

    My iMac won't start. I have to press T and mount it to an old G4 then eject then boot but slow and lots of beech balls. First aid says it has a 'Invalid key length' in 1 volume and can't be repaired. Will an upgrade to Mountain lion from Snow Leopard help or Disk Warrior as my files won't install.

    Thanks PATRICKMELE for your response, however I'm not sure if my Time Machine backup is trustworthy. I had a problem with that about 2 weeks ago and I took to an Apple Genius who ended up wiping my Time Machine backups. The new backup took 9 days and now looking at Time Machine Preferences it shows 1.59 GB of 3TB available; Oldest backup: None; Latest backup: None?
    I'm taking your advice and calling Apple Support as soon as possible. Thanks for your help

  • Password service won't start

    Following an unplanned hard restart of our server (Mac OS X 10.9.5, Server 3.2.2), the password service won't start, so our staff can't log into mail, calendars or file sharing.
    When I launch Open Directory, the main window has the message "Unable to load replica list", then it switches itself off after a minute or so.
    I've looked at the certificates in Server and they have the green tick so presumably are OK.
    DNS is working OK and running the command "sudo changeip -checkhostname" reports success.
    Here's the section of log that repeats every few seconds as PasswordService repeatedly starts up and exits:
    13/03/2015 20:55:00.617 com.apple.launchd[1]: (com.apple.PasswordService[5890]) Exited with code: 1
    13/03/2015 20:55:00.617 com.apple.launchd[1]: (com.apple.PasswordService) Throttling respawn: Will start in 10 seconds
    13/03/2015 20:55:02.540 xscertd[249]: Failed sending LookupCRLByCARecordName command to com.apple.xscertd.helper: The operation couldn’t be completed. (com.apple.certificateserver error 42005.)
    13/03/2015 20:55:08.708 com.apple.launchd[1]: (org.openldap.slapd[5894]) Exited with code: 1
    13/03/2015 20:55:08.708 com.apple.launchd[1]: (org.openldap.slapd) Throttling respawn: Will start in 7 seconds
    13/03/2015 20:55:10.206 xscertd-helper[5897]: ldap_search_ext_s returned -1 - Can't contact LDAP server when searching for bdb suffix, exiting
    13/03/2015 20:55:10.207 com.apple.launchd[1]: (com.apple.xscertd-helper[5897]) Exited with code: 1
    13/03/2015 20:55:10.207 com.apple.launchd[1]: (com.apple.xscertd-helper) Throttling respawn: Will start in 10 seconds
    13/03/2015 20:55:10.639 PasswordService[5901]: -[PasswordServerPrefsObject getSearchBase]: Unable to locate search base: -1 Can't contact LDAP server
    13/03/2015 20:55:10.639 PasswordService[5901]: -[PasswordServerPrefsObject loadXMLData]: Unable to locate passwordserver config record's plist attribute: -1 Can't contact LDAP server
    13/03/2015 20:55:10.640 PasswordService[5901]: -[PasswordServerPrefsObject getSearchBase]: Unable to locate search base: -1 Can't contact LDAP server
    13/03/2015 20:55:10.640 PasswordService[5901]: -[PasswordServerPrefsObject saveXMLData]: ldap_modify_ext_s of the passwordserver config record's plist attribute: -1 Can't contact LDAP server
    13/03/2015 20:55:10.684 PasswordService[5901]: int pwsf_GetPublicKey(char *): ldap_search_ext_s cn=authdata for Public Key returned -1
    13/03/2015 20:55:10.687 com.apple.launchd[1]: (com.apple.PasswordService[5901]) Exited with code: 1
    I have backups (both Time Machine and clones of the hard drive) that I could use to restore the corrupted bit of the configuration, if necessary, but I don't know what to restore.

    Many Open Directory problems can be resolved by taking the following steps. Test after each one, and back up all data before making any changes.
    1. The OD master must have a static IP address on the local network, not a dynamic address. It must not be connected to the same network with more than one interface; e.g., Ethernet and Wi-Fi.
    2. You must have a working DNS service, and the server's hostname must match its fully-qualified domain name. To confirm, select the server by name in the sidebar of the Server application window, then select the Overview tab. Click the Edit button on the Host Name line. On the Accessing your Server sheet, Domain Name should be selected. Change the Host Name, if necessary. The server must have at least a three-level name (e.g. "server.yourdomain.com"), and the name must not be in the ".local" top-level domain, which is reserved for Bonjour.
    3. The primary DNS server used by the server must be itself, unless you're using another server for internal DNS. The only DNS server set on the clients should be the internal one, which they should get from DHCP if applicable.
    4. If you have accounts with network home directories, make sure the URL's are correct in the user settings. A return status of 45 from the authorizationhost daemon in the log may mean that the URL for mounting the home directory was not updated after a change in the hostname.
    5. Only if you're still running Mavericks server, follow these instructions to rebuild the Kerberos configuration on the server.
    6. If you use authenticated binding, check the validity of the master's certificate. The common name must match the hostname and domain name. Deselecting and then reselecting the certificate in Server.app has been reported to have an effect in some cases. Otherwise delete all certificates and create new ones.
    7. Unbind and then rebind the clients in the Users & Groups preference pane. Use the fully-qualified domain name of the master.
    8. Reboot the master and the clients.
    9. Don't log in to the server with a network user's account.
    10. Disable any internal firewalls in use, including third-party "security" software.
    11. If you've created any replica servers, delete them.
    12. If OD has only recently stopped working when it was working before, you may be able to restore it from the automatic backup in /var/db/backups, or from a Time Machine snapshot of that backup.
    13. As a last resort, export all OD users. In the Open Directory pane of Server, delete the OD server. Then recreate it and import the users. Ensure that the UID's are in the 1001+ range.
    If you get this far without solving the problem, then you'll need to examine the logs in the Open Directory section of the log list in the Server app, and also the system log on the clients.

  • 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

  • My MacBook Pro won't start! HELP!

    I've been away for two weeks and haven't used my MacBook Pro.
    When I was about to start it again yesterday it won't start!
    I get the start sound and then it freezes on the first picture with the Apple and the wheel.
    I tried several times and I waited for almost an hour but nothing happened.
    The computer is about 3 years old.
    Can anybody help me?

    Will my hard drive be erased when I do the recovery?
    Merely booting into Recovery won't change anything. Depending on what you do next, your data might be affected, so you have to back up first if you haven't already done so.
    There are several ways to back up a Mac that is unable to fully boot. You need an external hard drive to hold the backup data.
    1. Boot into Recovery (command-R at startup; 10.7 or later), from a local Time Machine backup volume (option key at startup; 10.7.2 or later), or from your installation disc (C key at startup; 10.6.8 or earlier.) Launch Disk Utility and follow the instructions in the support article linked below, under “Instructions for backing up to an external hard disk via Disk Utility.”
    How to back up and restore your files
    2. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, boot the non-working Mac in target disk mode by holding down the key combination command-T at the startup chime. Connect the two Macs with a FireWire or Thunderbolt cable. The internal drive of the machine running in target mode will mount as an external drive on the other machine. Copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
    How to use and troubleshoot FireWire target disk mode
    3. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.

  • [Solved] Fresh install; HAL won't start?

    So I just finished a fresh installation and now I can't start X because HAL won't start up at all.
    I haven't messed around with anything except for installing everything and fixing up my config files.
    Seems like HAL is crashing because of permissions but I even checked the paths and they seem to be fine:
    hald --daemon=no --verbose=yes
    01:08:41.090 [i] hald.c:673: hal 0.5.14
    01:08:41.090 [i] hald.c:674: using child timeout 250s
    01:08:41.090 [i] hald.c:739: Will not daemonize
    01:08:41.090 [i] hald_dbus.c:5444: local server is listening at unix:abstract=/var/run/hald/dbus-uBDySnOMjt,guid=33e68e9ab5cc00ac1ce4ba92000008c1
    01:08:41.091 [i] hald_runner.c:304: Runner has pid 1695
    Runner started - allowed paths are '/usr/lib/hal:/usr/lib/hal/scripts:/usr/bin'
    01:08:41.093 [i] hald_runner.c:184: runner connection is 0x17da830
    01:08:41.097 [W] osspec.c:393: Unable to open /proc/mdstat: No such file or directory
    ** (process:1694): WARNING **: Failed to add monitor on '/usr/share/hal/fdi/preprobe': Permission denied
    ** (process:1694): WARNING **: Failed to add monitor on '/etc/hal/fdi/preprobe': Permission denied
    ** (process:1694): WARNING **: Failed to add monitor on '/usr/share/hal/fdi/information': Permission denied
    ** (process:1694): WARNING **: Failed to add monitor on '/etc/hal/fdi/information': Permission denied
    ** (process:1694): WARNING **: Failed to add monitor on '/usr/share/hal/fdi/policy': Permission denied
    ** (process:1694): WARNING **: Failed to add monitor on '/etc/hal/fdi/policy': Permission denied
    22:08:41.098 [i] mmap_cache.c:126: Regenerating fdi cache..
    Could not get password database information for UID of current process: User "???" unknown or no memory to allocate password entry
    Could not get password database information for UID of current process: User "???" unknown or no memory to allocate password entry
    22:08:41.099 [E] hald_runner.c:888: Error running 'hald-generate-fdi-cache': org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
    22:08:41.099 [i] mmap_cache.c:104: In regen_cache_cb exit_type=2, return_code=0
    22:08:41.099 [E] mmap_cache.c:153: fdi cache regeneration failed!
    22:08:41.099 [i] mmap_cache.c:156: fdi cache generation done
    22:08:41.099 [i] mmap_cache.c:278: cache mtime is 0
    *** [DIE] osspec.c:osspec_init():449 : Unable to read /proc/mounts
    Can't find anything worthwhile in logs etc., and I can't think of anything that could be causing this?
    I checked that the HAL user exists and has been added to the default groups, but that "???"-part is alarming.
    DBus starts up normally.
    Networking and "lo" seem to be working fine as well, and I don't have iptables up.
    Last edited by initbox (2011-07-05 16:59:36)

    tomk wrote:Update your system - xorg does not depend on hal anymore. hal is obsolete.
    Ah, haven't been up to date on all the changes, it seems...
    In the past I've had problems with the nvidia driver + Xorg without HAL, I think?
    Anyhow, contrary to the Xorg page, I had no 20-nvidia.conf. I created that and now I'm able to startx without HAL but KDM doesn't work, the screen flickers when it attempts to start Xorg but then it crashes. Strange. Nothing in the Xorg logs either.
    I'll have to see about that next, but it's nice to be able to get rid of HAL at least.

Maybe you are looking for

  • Cash Management - Bank Statement Open Interface

    Bank Statement Open Interface (The tables are ce_statement_headers_int_all and ce_statement_lines_interface) I am trying to load the bank statements with Journal Lines and trying to reconcile them using Autoreconcilation but I am getting error. ( I a

  • Create an Excel and send it as an email

    Hi All, I have an ALV block list which has 4 internal tables appened.. I have displayed the data but i wanted to create an excel and mail it to the users who are intersted. as there are 4 internal tables displayed in the output how to send all of the

  • Cfmail "from name" and "from email address"

    I have been using a cf newsletter app with a <cfmail> function, and the syntax like this for the from and to addresses <cfmail from="#from_name# <#from_email_address#>" to="#first_name# #last_name# <#email_address#>" subject="#form.message_subject#">

  • Text inside the portlet is cutting off

    I have a process portlets and the text inside the portlet is cutting off. For example, instead of displaying the name of the process "Certificate of good standing" I get "Certificate of Goo..." How can I make the text wrap or show the full project na

  • What happened to user_domains in WLS7.0 GA?

    when I installed WLS7.0 GA I didn't see any clean domain like user_domains or mydomain to build our domain.... Am I missing something?? -Praveen