No login available on ttys (systemd)

Hello,
I can no longer login to ttys (ctrl + alt + F1 - this is called a "tty" right?).
If I switch to one of the ttys I can still read some bootup messages I think.
The last one says
[OK] listening on delayed shutdown socket
No login prompt or blinking cursor at all. all ttys (tty1 - tty6) look that way. If it may help understanding my problem I can type all of that messages into a post...
There is no problem switching back to X  waiting on tty7. This makes me believe I do not have broken keyboard config or stuff.
Has anyone a hint, were i can look for some log output what i going wrong when I hit ctrl + alt + f[0-6]?
some research:
ben # systemctl list-units | egrep -i "tty|login"
sys-devi...tty-ttyS0.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS0
sys-devi...tty-ttyS1.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS1
sys-devi...tty-ttyS2.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS2
sys-devi...tty-ttyS3.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS3
[email protected] loaded active running Getty on tty1
[email protected] loaded active running Getty on tty2
[email protected] loaded active running Getty on tty3
[email protected] loaded active running Getty on tty4
[email protected] loaded active running Getty on tty5
[email protected] loaded active running Getty on tty6
systemd-logind.service loaded active running Login Service
getty.target loaded active active Login Prompts
ben # ps au | grep tty
root 365 0.0 0.0 9848 804 tty1 Ss+ 18:34 0:00 /sbin/agetty --noclear tty1 38400 linux
root 379 1.5 0.7 212552 123820 tty7 Rs+ 18:34 0:36 /usr/bin/X :0 vt7 -nolisten tcp -auth /var/run/xauth/A:0-BKoSkc
root 482 0.0 0.0 9848 796 tty3 Ss+ 18:35 0:00 /sbin/agetty --noclear tty3 38400 linux
root 483 0.0 0.0 9848 792 tty4 Ss+ 18:35 0:00 /sbin/agetty --noclear tty4 38400 linux
root 484 0.0 0.0 9848 800 tty5 Ss+ 18:35 0:00 /sbin/agetty --noclear tty5 38400 linux
root 485 0.0 0.0 9848 800 tty6 Ss+ 18:35 0:00 /sbin/agetty --noclear tty6 38400 linux
root 6130 0.0 0.0 9848 804 tty2 Ss+ 18:52 0:00 /sbin/agetty --noclear tty2 38400 linux
root 9777 0.0 0.0 14692 1128 pts/0 S+ 19:14 0:00 grep --colour=auto tty
ben # cat /etc/systemd/logind.conf | grep -v "^#"
[Login]
NAutoVTs=6
ReserveVT=6
ben # systemctl status systemd-logind
systemd-logind.service - Login Service
Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static)
Active: active (running) since Di 2013-08-20 18:34:55 CEST; 41min ago
Docs: man:systemd-logind.service(8)
man:logind.conf(5)
[url]http://www.freedesktop.org/wiki/Software/systemd/multiseat[/url]
Main PID: 360 (systemd-logind)
CGroup: name=systemd:/system/systemd-logind.service
└─360 /usr/lib/systemd/systemd-logind
Aug 20 18:35:06 bendude systemd-logind[360]: New session 1 of user ben.
Aug 20 18:35:06 bendude systemd-logind[360]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display.
And general system info
ben # uname -a
Linux ben 3.10.7-1-ARCH #1 SMP PREEMPT Thu Aug 15 11:55:34 CEST 2013 x86_64 GNU/Linux
ben # pacman -Qsi systemd
local/initscripts 2012.10.1-1
System initialization/bootup scripts
local/lib32-systemd 204-1
system and service manager (32-bit)
local/systemd 204-3
system and service manager
local/systemd-sysvcompat 204-3 (base)
sysvinit compat for systemd
Thanks in advance,
Ben

Well, all ttys display the Welcome to Arch linux screen with the last message being
[ OK ] Listening on LVM2 metadata daemon socket.
[james@arch ~]$ systemctl list-units | egrep -i "tty|login"
sys-devi...tty-ttyS1.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS1
sys-devi...tty-ttyS2.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS2
sys-devi...tty-ttyS3.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS3
sys-devi...tty-ttyS0.device loaded active plugged /sys/devices/pnp0/00:0a/tty/ttyS0
[email protected] loaded active running Getty on tty1
[email protected] loaded active running Getty on tty2
[email protected] loaded active running Getty on tty5
systemd-logind.service loaded active running Login Service
getty.target loaded active active Login Prompts
with each getty@tty service being loaded when I try to access them
[james@arch ~]$ ps au | grep tty
root 264 0.0 0.0 7904 800 tty1 Ss+ 09:53 0:00 /sbin/agetty --noclear tty1 38400 linux
root 273 12.9 2.1 502284 176900 tty7 Ss+ 09:53 0:58 /usr/sbin/X :0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
root 947 0.0 0.0 7904 792 tty5 Ss+ 09:55 0:00 /sbin/agetty --noclear tty5 38400 linux
root 1104 0.0 0.0 7904 796 tty2 Ss+ 09:58 0:00 /sbin/agetty --noclear tty2 38400 linux
james 1145 0.0 0.0 10684 1072 pts/0 S+ 10:00 0:00 grep tty
nothing set in logind.conf
[james@arch ~]$ systemctl status systemd-logind
systemd-logind.service - Login Service
Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static)
Active: active (running) since Fri 2013-08-23 09:53:18 NZST; 11min ago
Docs: man:systemd-logind.service(8)
man:logind.conf(5)
http://www.freedesktop.org/wiki/Software/systemd/multiseat
Main PID: 257 (systemd-logind)
CGroup: name=systemd:/system/systemd-logind.service
└─257 /usr/lib/systemd/systemd-logind
[james@arch ~]$ uname -a
Linux arch 3.10.7-1-ARCH #1 SMP PREEMPT Thu Aug 15 11:55:34 CEST 2013 x86_64 GNU/Linux
[james@arch ~]$ pacman -Qsi systemd
local/lib32-systemd 204-1
system and service manager (32-bit)
local/netctl 1.3-1 (base)
Profile based systemd network management
local/systemd 204-3
system and service manager
local/systemd-sysvcompat 204-3 (base)
sysvinit compat for systemd
What other info can I give you?

Similar Messages

  • LXC Container login on host tty

    I want create a full system lxc container with a gui and log in to it on one of the host's tty (using CTRL+ALT+Fn). I have set up lxc as per the wiki and I can login into container (its debian sid) and ssh into it and install software. What I'm having trouble doing is getting it to present a login at the host tty. I'm trying to set this up for F7 since that is not used by systemd. Has anybody been able to do this?
    My config file:
    # Template used to create this container: /usr/share/lxc/templates/lxc-debian
    # Parameters passed to the template:
    # For additional config options, please look at lxc.container.conf(5)
    # lxc.network.type = empty
    lxc.rootfs = /var/lib/lxc/Mycont/rootfs
    # Common configuration
    lxc.include = /usr/share/lxc/config/debian.common.conf
    # Container specific configuration
    lxc.utsname = Mycont
    lxc.arch = amd64
    lxc.tty = 3
    lxc.cap.drop = mknod
    lxc.pts = 1024
    lxc.kmsg = 0
    lxc.autodev = 1
    #networking
    lxc.network.type=veth
    lxc.network.link=br0
    lxc.network.ipv4=10.0.0.100
    lxc.network.ipv4.gateway=10.0.0.1
    lxc.network.flags=up
    lxc.network.name=enp3s0
    lxc.network.mtu=1500
    #cgroups
    lxc.cgroup.devices.deny = a # Deny all access to devices
    lxc.cgroup.devices.allow = c 1:3 rwm # dev/null
    lxc.cgroup.devices.allow = c 1:5 rwm # dev/zero
    lxc.cgroup.devices.allow = c 5:1 rwm # dev/console
    lxc.cgroup.devices.allow = c 5:0 rwm # dev/tty
    #lxc.cgroup.devices.allow = c 4:0 rwm # dev/tty0
    lxc.cgroup.devices.allow = c 4:7 rwm # dev/tty7
    lxc.cgroup.devices.allow = c 1:9 rwm # dev/urandom
    lxc.cgroup.devices.allow = c 1:8 rwm # dev/random
    lxc.cgroup.devices.allow = c 136:* rwm # dev/pts/*
    lxc.cgroup.devices.allow = c 5:2 rwm # dev/pts/ptmx
    tty setup in the container's rootfs/dev/
    crw-rw-rw- 1 root tty 5, 0 Jan 14 01:03 tty
    crw------- 1 root tty 4, 0 Jan 14 01:03 tty0
    crw-r--r-- 1 root root 4, 1 Mar 2 14:26 tty1
    crw-r--r-- 1 root root 4, 2 Mar 2 14:26 tty2
    crw-r--r-- 1 root root 4, 3 Mar 2 14:26 tty3
    crw-r--r-- 1 root root 4, 4 Mar 2 14:26 tty4
    crw-r--r-- 1 root root 4, 7 Mar 3 15:34 tty7
    tty setp in the container /dev when its running:
    crw-rw-rw- 1 root root 5, 0 Mar 4 18:52 tty
    crw--w---- 1 root tty 136, 0 Mar 4 18:52 tty1
    crw--w---- 1 root tty 136, 1 Mar 4 18:52 tty2
    crw--w---- 1 root tty 136, 2 Mar 4 18:52 tty3
    crw-rw-rw- 1 root root 1, 9 Mar 4 18:52 urandom
    note that tty7 is not created in the running container's /dev even though it is in the container's rootfs/dev
    thanks

    Hi yjdabear,  Thank you for your replies. I do have logging history set to level 4.  I am still not seeing traps generated even using the 'syslog method' for the login failures.  here is a snipit of my logging
    Syslog logging: enabled (0 messages dropped, 1102 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)
    Console logging: level debugging, 277317 messages logged, xml disabled,
    filtering disabled
    Monitor logging: level debugging, 139 messages logged, xml disabled,
    filtering disabled
    Buffer logging: level debugging, 278418 messages logged, xml disabled,
    filtering disabled
    Exception Logging: size (8192 bytes)
    Count and timestamp logging messages: disabled
    Trap logging: level debugging, 278388 message lines logged
    Logging to , 278388 message lines logged, xml disabled,
    filtering disabled
    switch#show logging history
    Syslog History Table:1 maximum table entries,
    saving level warnings or higher
    4417 messages ignored, 0 dropped, 0 recursion drops
    273892 table entries flushed
    SNMP notifications enabled, 52 notifications sent
    entry number 273893 : LINK-3-UPDOWN
    Interface GigabitEthernet7/19, changed state to up
    timestamp: 883868674

  • No login available in Business Catalyst extension panel in Dreamweaver CS5.

    I am not getting the login form in the Business Catalyst Extension panel in Dreamweaver CS5.
    I have added the extension and restarted Dreamweaver, but the panel still shows two buttons: Get Started ( taking me to download the extension) and Learn More ( taking me to a page that does not exist anymore).
    Does anyone know how to make the login form appear so that I can get Business Catalyst integrated with Dreamweaver CS5?
    Evan

    Try to restore the Dreamweaver Preferences as given in the link below, and see if that helps
    http://helpx.adobe.com/dreamweaver/kb/restore-preferences-dreamweaver-cs4-cs5.html

  • Intermittent very long delay before login available

    Windows 7 64 - SP1 fully updated.
    I have a few remaining Windows 7 desktops in my Domain.  Ocassionally (have not found a pattern) the user will boot up the computer or come back from lunch and try to unlock their computer.  The computer will go to a blank blue screen but no username
    or password field will display.  The mouse is responsive.   After a very long delay the credential fields will display and the user can log in.  This delay can be 20 mins or more.   This seems to happen to the same computers but
    only occasionally.  Sometimes a forced reboot is required.  After reboot the system usually works as expected.
    When searching for this issue and resolutions to it, I don't seem to find this exact issue - or I am not wording it correctly in a search.
    If this happened consistently, I would probably repair, or wipe and restore the system.   I am not seeing anything in the event log that would be related.
    I look forward to your advice.
    Fred Zilz

    Hi Fred,
    Since the delay occurred before your input the credential. It's not related with domain.
    Let's aim at the Windows 7 computer itself. Generally, it should be the winlogon process cannot load successfully.
    Did you use Aero theme?
    If yes, try disabling the Aero theme and use the Windows 7 Basic layout.
    Meanwhile, logon with the local administrator and perform a clean boot to see if there is some other service conflict:
    How to perform a clean boot in Windows
    http://support.microsoft.com/kb/929135
    Also disconnect all network and all external hardware to check if it occurs again.
    Karen Hu
    TechNet Community Support

  • Systemd logind.service reports an error: Failed to start login service

    Hello,
    I found this error in /var/log/errors.log and /var/log/daemon.log although my system functions normally.
    It's been written there every 90 seconds!!!!:
    Dec 19 23:52:59 localhost systemd[1]: Failed to start Login Service.
    Dec 19 23:54:29 localhost systemd[1]: Failed to start Login Service.
    Dec 19 23:55:59 localhost systemd[1]: Failed to start Login Service.
    Dec 19 23:57:29 localhost systemd[1]: Failed to start Login Service.
    Dec 19 23:58:59 localhost systemd[1]: Failed to start Login Service.
    the process: systemd-logind.service seems to be working fine:
    [xxx@archbox ~]$ sudo systemctl status systemd-logind.service
    [sudo] password for xxx:
    systemd-logind.service - Login Service
    Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static)
    Active: activating (start) since Wed, 2012-12-19 23:49:59 CET; 49s ago
    Docs: man:systemd-logind.service(8)
    man:logind.conf(5)
    http://www.freedesktop.org/wiki/Software/systemd/multiseat
    Main PID: 11822 (systemd-logind)
    CGroup: name=systemd:/system/systemd-logind.service
    └─11822 /usr/lib/systemd/systemd-logind
    Dec 19 23:49:59 archbox systemd[1]: Starting Login Service...
    Dec 19 23:49:59 archbox systemd-logind[11822]: New seat seat0.
    Dec 19 23:49:59 archbox systemd-logind[11822]: Watching system buttons on /dev/input/event6 (P...on)
    Dec 19 23:49:59 archbox systemd-logind[11822]: Watching system buttons on /dev/input/event7 (V...us)
    Dec 19 23:49:59 archbox systemd-logind[11822]: Watching system buttons on /dev/input/event4 (L...ch)
    Dec 19 23:49:59 archbox systemd-logind[11822]: Watching system buttons on /dev/input/event5 (S...on)
    Dec 19 23:49:59 archbox systemd-logind[11822]: Watching system buttons on /dev/input/event3 (T...ns)
    Dec 19 23:49:59 archbox systemd-logind[11822]: New session 1 of user xxx.
    Dec 19 23:49:59 archbox systemd-logind[11822]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-...ay.
    and journalctl _PID=11822 returns:
    Dec 19 23:38:01 archbox sudo[21335]: xxx : TTY=pts/1 ; PWD=/home/xxx ; USER=root ; COMMAND=/usr/bin/
    Dec 19 23:38:01 archbox sudo[21335]: pam_unix(sudo:session): session opened for user root by xxx(uid
    Dec 19 23:38:01 archbox sudo[21335]: pam_unix(sudo:session): session closed for user root
    Dec 19 23:38:44 archbox sudo[22682]: xxx : TTY=pts/1 ; PWD=/home/xxx ; USER=root ; COMMAND=/usr/bin/
    Dec 19 23:38:44 archbox sudo[22682]: pam_unix(sudo:session): session opened for user root by xxx(uid
    Dec 19 23:38:44 archbox sudo[22682]: pam_unix(sudo:session): session closed for user root
    Dec 19 23:39:10 archbox sudo[23516]: xxx : TTY=pts/1 ; PWD=/home/xxx ; USER=root ; COMMAND=/usr/bin/
    Dec 19 23:39:10 archbox sudo[23516]: pam_unix(sudo:session): session opened for user root by xxx(uid
    Dec 19 23:39:29 archbox systemd[1]: systemd-logind.service operation timed out. Terminating.
    Dec 19 23:39:29 archbox systemd[1]: Failed to start Login Service.
    Dec 19 23:39:29 archbox systemd[1]: Unit systemd-logind.service entered failed state
    Dec 19 23:39:29 archbox systemd[1]: systemd-logind.service holdoff time over, scheduling restart.
    Dec 19 23:39:29 archbox systemd[1]: Stopping Login Service...
    Dec 19 23:39:29 archbox systemd[1]: Starting Login Service...
    Dec 19 23:39:29 archbox systemd-logind[24096]: New seat seat0.
    Dec 19 23:39:29 archbox systemd-logind[24096]: Watching system buttons on /dev/input/event6 (Power B
    Dec 19 23:39:29 archbox systemd-logind[24096]: Watching system buttons on /dev/input/event7 (Video B
    Dec 19 23:39:29 archbox systemd-logind[24096]: Watching system buttons on /dev/input/event4 (Lid Swi
    Dec 19 23:39:29 archbox systemd-logind[24096]: Watching system buttons on /dev/input/event5 (Sleep B
    Dec 19 23:39:29 archbox systemd-logind[24096]: Watching system buttons on /dev/input/event3 (ThinkPa
    Dec 19 23:39:29 archbox systemd-logind[24096]: New session 1 of user xxx.
    Dec 19 23:39:29 archbox systemd-logind[24096]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-displa
    Dec 19 23:39:30 archbox sudo[23516]: pam_unix(sudo:session): session closed for user root
    Dec 19 23:40:08 archbox sudo[25314]: xxx : TTY=pts/1 ; PWD=/home/xxx ; USER=root ; COMMAND=/usr/bin/
    Dec 19 23:40:08 archbox sudo[25314]: pam_unix(sudo:session): session opened for user root by xxx(uid
    Dec 19 23:40:09 archbox sudo[25314]: pam_unix(sudo:session): session closed for user root
    Dec 19 23:40:43 archbox slim[641]: error 8: BadMatch (invalid parameter attributes) request 142 mino
    Dec 19 23:40:43 archbox slim[641]: error 9: BadDrawable (invalid Pixmap or Window parameter) request
    Dec 19 23:40:43 archbox slim[641]: error 4: BadPixmap (invalid Pixmap parameter) request 54 minor 0
    Dec 19 23:40:56 archbox sudo[26739]: xxx : TTY=pts/0 ; PWD=/home/xxx ; USER=root ; COMMAND=/usr/bin/
    Dec 19 23:40:56 archbox sudo[26739]: pam_unix(sudo:session): session opened for user root by xxx(uid
    Dec 19 23:40:59 archbox systemd[1]: systemd-logind.service operation timed out. Terminating.
    Dec 19 23:40:59 archbox systemd[1]: Failed to start Login Service.
    Dec 19 23:40:59 archbox systemd[1]: Unit systemd-logind.service entered failed state
    Dec 19 23:40:59 archbox systemd[1]: systemd-logind.service holdoff time over, scheduling restart.
    Dec 19 23:40:59 archbox systemd[1]: Stopping Login Service...
    Dec 19 23:40:59 archbox systemd[1]: Starting Login Service...
    Dec 19 23:40:59 archbox systemd-logind[26935]: New seat seat0.
    Dec 19 23:40:59 archbox systemd-logind[26935]: Watching system buttons on /dev/input/event6 (Power B
    Dec 19 23:40:59 archbox systemd-logind[26935]: Watching system buttons on /dev/input/event7 (Video B
    Dec 19 23:40:59 archbox systemd-logind[26935]: Watching system buttons on /dev/input/event4 (Lid Swi
    Dec 19 23:40:59 archbox systemd-logind[26935]: Watching system buttons on /dev/input/event5 (Sleep B
    Dec 19 23:40:59 archbox systemd-logind[26935]: Watching system buttons on /dev/input/event3 (ThinkPa
    Dec 19 23:40:59 archbox systemd-logind[26935]: New session 1 of user xxx.
    Dec 19 23:40:59 archbox systemd-logind[26935]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-displa
    Updating system with pacman didn't solve it.
    Did I miss something out while migrating to systemd, is it a problem with SLiM or user session maybe ? Do you guys have any ideas where to start ? Thanks.
    Last edited by nastycino (2012-12-30 17:46:43)

    My /etc/systemd/logind.conf:
    # This file is part of systemd.
    # systemd is free software; you can redistribute it and/or modify it
    # under the terms of the GNU Lesser General Public License as published by
    # the Free Software Foundation; either version 2.1 of the License, or
    # (at your option) any later version.
    # See logind.conf(5) for details
    [Login]
    #NAutoVTs=6
    #ReserveVT=6
    #KillUserProcesses=no
    #KillOnlyUsers=
    #KillExcludeUsers=root
    #Controllers=
    #ResetControllers=cpu
    #InhibitDelayMaxSec=5
    HandlePowerKey=poweroff
    HandleSuspendKey=suspend
    HandleHibernateKey=hibernate
    HandleLidSwitch=suspend
    #PowerKeyIgnoreInhibited=no
    #SuspendKeyIgnoreInhibited=no
    #HibernateKeyIgnoreInhibited=no
    #LidSwitchIgnoreInhibited=yes
    Is there any way of reinstalling parts of systemd like logind.service?

  • [Solved]Login delay of up to 12 seconds even on TTY

    TL;DR
    Installed Qingy a while back, NVIDIA driver didn't like it, so I uninstalled it.
    Since have long login delay on my account, new accounts are fine.
    If I'm already logged in, this account is fine.
    Full details:
    Let's start from the top- My system was running great, and is still, as far as I can tell, running great.
    On login, I have a 8-12 second delay on my Rojikku account.
    This started happening after I attempted to install quingy (That was hell.)
    I did all sorts of stuff attempting to get the qingy gui to work, and I never did.
    I eventually undid everything, at least I believe I did, and uninstalled quingy.
    I started the whole qingy search because I heard slim was abandoned, and qingy sounded cool.
    I have since been using lightdm, which I thought was the problem.
    In the process of going to fix this problem, I logged out completely and went to login to the tty, when I discovered I have the issue.
    This issue WILL NOT happen if I am already logged in with my xsession started.
    For example, I am on tty2 with this i3 session open. If I switch to tty3, my login will be instant.
    If I close out of tty2, and login on any tty, it will take ten seconds or so.
    If I attempt to login on a new account I just made, the login is instant.
    I use the zsh shell. I assume everything outside of my shell is fairly irrelevant, though I have a couple user systemd processes.
    I couldn't find the issue on Google, though I have a basic understanding of "Something that needs to see I'm logged in isn't seeing it until it reloads after about ten seconds". That could be completely wrong.
    In case you're wondering, no, I didn't make any other major changes just before this started happening.
    I run the nvidia driver, which wasn't very compatible with qingy.
    My kernel is at 3.18.6-1-ARCH
    I'm running off an SSD, 30GB partition, and I have 16GB of RAM.
    My processor averages less than 20% load even when I'm doing a lot of stuff much more intensive than logging into a tty session.
    I use the i3 window manager, for those curious, and have xinit setup to allow me to choose between it and xfce4. I have xfce4 installed so that I am not missing any major dependencies- or at least am less likely to be, as far as I can tell.
    Last edited by Rojikku (2015-03-13 06:01:30)

    set -x was certainly interesting.
    There's, by my timing, around a five or six second delay, before a rainbow falls from the sky. Then it becomes a shell. The fact that a rainbow of text flew in out of nowhere slightly distracted my ability to count time. Is there some way I can log this output so I can analyze it?
    It's slightly too fast for me to see. By slightly, I mean a lot.
    As for log/journal, I have no idea how to access that... I tried a few things, not getting anything.

  • [SOLVED] TTY terminal font not displaying correctly

    Solved, see Edit 2 for solution.
    Begin original post:
    Hi everyone,
    When I login to any TTY console on my system (i.e. by pressing Ctrl+Alt+F2 and loging with my user name and password), the [user@hostname ~]$ is all gibberish; it looks something like this:
    ┌─[\[\e[31;1m\]\u@\[\e[32;1m\]\H\[\033[1;37m\]] \n\[\033[1;37m\]└─[\[\033[0;36m\]\w\[\033[1;37m\]]> \[\e[0m\]
    Note: The user name and password prompts display correctly, as well as any commands that I enter (such as pacman -Syu), just the text preceding where I enter commands in messed up. Also, graphical terminal emulators such as xfce4-terminal do not have this issue.
    I have researched this for a while, and I found a Post that outlines the same issue I am having. Unfortunately, the solution is for init.d and rc scripts, so it obviously will not work with Systemd.
    Also, no other distro has this problem on my system, even a clean install of Arch works properly. This leads me to believe that a config file is messed up somewhere.
    Does anybody know how to translate the above fix to a Systemd solution so I do not have to deal with wonky virtual consoles?
    Thanks
      -venividivici24
    Edit: I just tried logging in as root, and it worked fine, everything was normal, so maybe it is some configuration file for my user specifically.
    Edit 2: I fixed it. The problem happened to be in my ~/.profile config file. A while ago, I had bashish installed, but have since removed it. It left some settings in .profile that caused the console to act the way described above.
    All I did to fix this was to change this:
    # Termcap is outdated, old, and crusty, kill it.
    unset TERMCAP
    # Man is much better than us at figuring this out
    unset MANPATH
    BASHISHDIR="/usr/local/share/bashish" ## line added by bashish
    TTY=`tty 2>/dev/null` && if test "x$BASHISHDIR" != x;then ## line added by bashish
    test "$BASHISH_OLDPATH"||BASHISH_OLDPATH="$PATH" ## line added by bashish
    PATH="$HOME/.bashish/launcher:$BASHISHDIR/lib:$BASHISH_OLDPATH" ## line added by bashish
    BASHSISH_CP=437 ## line added by bashish
    EST_TERM="$TERM" _bashish_utfcheck && BASHISH_CP=utf8 ## line added by bashish
    ENV="$HOME/.profile" ## line added by bashish
    export BASHISH_CP BASHISH_OLDPATH TTY ENV ## line added by bashish
    . "$BASHISHDIR/main/prompt/sh/init" ## line added by bashish
    fi ## line added by bashish
    to this (I commented out the commands):
    # Termcap is outdated, old, and crusty, kill it.
    #unset TERMCAP
    # Man is much better than us at figuring this out
    #unset MANPATH
    #BASHISHDIR="/usr/local/share/bashish" ## line added by bashish
    #TTY=`tty 2>/dev/null` && if test "x$BASHISHDIR" != x;then ## line added by bashish
    #test "$BASHISH_OLDPATH"||BASHISH_OLDPATH="$PATH" ## line added by bashish
    #PATH="$HOME/.bashish/launcher:$BASHISHDIR/lib:$BASHISH_OLDPATH" ## line added by bashish
    #BASHSISH_CP=437 ## line added by bashish
    #EST_TERM="$TERM" _bashish_utfcheck && BASHISH_CP=utf8 ## line added by bashish
    #ENV="$HOME/.profile" ## line added by bashish
    #export BASHISH_CP BASHISH_OLDPATH TTY ENV ## line added by bashish
    #. "$BASHISHDIR/main/prompt/sh/init" ## line added by bashish
    #fi ## line added by bashish
    I hope that this helps anyone who has this issue
    Last edited by venividivici24 (2014-12-01 00:41:23)

    It says:
    LANG=en_US.UTF-8
    LC_CTYPE="en_US.UTF-8"
    LC_NUMERIC="en_US.UTF-8"
    LC_TIME="en_US.UTF-8"
    LC_COLLATE="en_US.UTF-8"
    LC_MONETARY="en_US.UTF-8"
    LC_MESSAGES="en_US.UTF-8"
    LC_PAPER="en_US.UTF-8"
    LC_NAME="en_US.UTF-8"
    LC_ADDRESS="en_US.UTF-8"
    LC_TELEPHONE="en_US.UTF-8"
    LC_MEASUREMENT="en_US.UTF-8"
    LC_IDENTIFICATION="en_US.UTF-8"
    LC_ALL=
    This is my bashrc, but I do not see anything in here that would warrant such odd behavior.
    alias aurup='yaourt -Sua'
    alias pacup='sudo pacman -Syu'
    alias update='sudo pacman -Syu && yaourt -Sua'
    export EDITOR="nano"
    complete -cf sudo
    Last edited by venividivici24 (2014-12-01 00:32:05)

  • Systemd-logind - no session created

    I had no problems switching to systemd on my machine, but on another with a similar setup there is the following problem.
    After logining in, there is no systemd-logind session, meaning no permissions for automounting etc.  Env. variables XDG_SESSION_ID and XDG_VTNR are empty, loginctl does not show session 1.
    $ journalctl -b | grep -i login
    systemd[1]: Starting Login Service...
    systemd-logind[855]: New seat seat0.
    systemd[1]: Started Login Service.
    systemd[1]: Starting Login Prompts.
    systemd[1]: Reached target Login Prompts.
    login[975]: pam_unix(login:session): session opened for user joe by LOGIN(uid=0)
    login[975]: LOGIN ON tty1 BY joe
    systemd-logind[855]: New session 2 of user sawyer.
    In the above, the last line is from my ssh session, but I am missing a similar one for session 1 after the login from tty.
    $ loginctl
    SESSION UID USER SEAT
    2 1000 sawyer
    1 sessions listed.
    Note that the user was still logged in when the above was ran.
    Any ideas on how to tackle the problem? I followed the wiki to transition to systemd, and as mentioned did the same on my computer before and everything works for me.

    Same kind of problem here ...
    Setup:
    /etc/systemd/system/
    ├── dbus-org.freedesktop.Avahi.service -> /usr/lib/systemd/system/avahi-daemon.service
    ├── default.target -> /usr/lib/systemd/system/multi-user.target
    ├── getty.target.wants
    │   └── [email protected] -> /usr/lib/systemd/system/[email protected]
    ├── graphical.target.wants
    ├── multi-user.target.wants
    │   ├── avahi-daemon.service -> /usr/lib/systemd/system/avahi-daemon.service
    │   ├── netcfg.service -> /usr/lib/systemd/system/netcfg.service
    │   ├── remote-fs.target -> /usr/lib/systemd/system/remote-fs.target
    │   ├── sshd.service -> /usr/lib/systemd/system/sshd.service
    │   └── sshdgenkeys.service -> /usr/lib/systemd/system/sshdgenkeys.service
    └── sockets.target.wants
    └── avahi-daemon.socket -> /usr/lib/systemd/system/avahi-daemon.socket
    When I log from tty1, logintcl shows noting, but when I log from ssh I do get a
    session in loginctl.
    I've re-installed arch on a vm just to check what's going on
    On the vm, I do get a login session, and the logs say:
    $ journalct -b | grep login
    Mar 16 13:40:32 arch systemd-logind[164]: Watching system buttons on /dev/input/event3 (Power Button)
    Mar 16 13:40:32 arch systemd-logind[164]: Watching system buttons on /dev/input/event4 (Sleep Button)
    Mar 16 13:40:32 arch systemd-logind[164]: New seat seat0.
    Mar 16 13:40:32 arch systemd-logind[164]: Watching system buttons on /dev/input/event3 (Power Button)
    Mar 16 13:40:32 arch systemd-logind[164]: Watching system buttons on /dev/input/event4 (Sleep Button)
    Mar 16 13:40:43 arch login[166]: pam_unix(login:session): session opened for user yannick by LOGIN(uid=0)
    Mar 16 13:40:43 arch systemd-logind[164]: New session 1 of user yannick.
    On my box the logs say:
    Mar 16 15:26:49 bermudes systemd-logind[975]: Watching system buttons on /dev/input/event3 (Power Button)
    Mar 16 15:26:49 bermudes systemd-logind[975]: Watching system buttons on /dev/input/event5 (Video Bus)
    Mar 16 15:26:49 bermudes systemd-logind[975]: Watching system buttons on /dev/input/event0 (Power Button)
    Mar 16 15:26:49 bermudes systemd-logind[975]: Watching system buttons on /dev/input/event1 (Lid Switch)
    Mar 16 15:26:49 bermudes systemd-logind[975]: Watching system buttons on /dev/input/event2 (Sleep Button)
    So for some reason on my box the seat does not even get created ...
    edit: solved for me    Turned out I changed /etc/pam.d/login back in 2011 and never merged in with /etc/pam.d/login.pacnew.
    For reference, here's the /etc/pam.d/login that did the trick
    auth required pam_securetty.so
    auth requisite pam_nologin.so
    auth include system-local-login
    account include system-local-login
    session include system-local-login
    @sawyer: maybe you should look at your .pacnew files too, or ask for help on #systemd irc channel
    Last edited by Yannick_LM (2013-03-16 14:26:04)

  • Systemd Emergency Mode on Boot

    I am sorry if this is in the wrong forum section.
    When I boot my Archlinux computer, I am taken to an "emergency mode" screen. It is clearly part of systemd, and I cannot start my regular graphical environment. I have been using Arch for a few months, and I have had minor systemd troubles but nothing as serious as this. I am currently in a Linux Mint Live CD so I can post this.
    I researched the problem, and found that the systemd may have failed to mount critical drives. I looked at my /etc/fstab file, and it seems to be kind of wonky (my boot partition is after my root partition, UUIDs seem to be wrong). I do not know how to fix this emergency mode problem.
    Please help; any help is appreciated.

    By now, I didn't do something that solve the problem. Sorry by my side.
    Idea's goal: try to login in a tty using rescue.target. And from there launch systemd's multi-user.target to see what fails. I don't know if it'll used for something (I'm saying something like "press all keys to see what's up").
    For boot in rescue.target. You can use a kernel parameter:
    https://wiki.archlinux.org/index.php/Sy … ent_target
    or another way (if kernel parameter points to default.target): change symbolic link from default.target to rescue.target
    ln -sf /usr/lib/systemd/system/rescue.target /etc/systemd/system/default.target
    If you get a login try to change current run level.
    Edit:
    but, maybe it is the same that grub's fallback mode.
    emergency.target???
    Last edited by Alber (2013-12-15 12:23:22)

  • Systemd: Slim fails to start automatically after boot

    Hi, after some update a couple of weeks ago (I don't remember exactly), slim fails to start after boot. I use systemd and just had enabled the slim.service file that is included in the package. After boot, I can login on the tty and then restart the slim.service, and everything works.
    In the slim.log file it says:
    Fatal server error:
    no screens found
    Giving up.
    slim: unable to connect to X server
    /usr/bin/xauth: file /var/run/slim.auth does not exist
    It seems like slim is started before X, since everything works when I restart the service manually. What is causing this problem and how can I solve it?
    Best regards and thanks,
    Jan Oliver

    oliarch ~ sudo systemd-analyze blame
    2460ms net-auto-wireless.service
    243ms rsyslog.service
    239ms sshd.service
    183ms console-kit-log-system-start.service
    136ms systemd-logind.service
    124ms console-kit-daemon.service
    119ms systemd-udev-trigger.service
    99ms systemd-sysctl.service
    82ms systemd-readahead-replay.service
    80ms systemd-vconsole-setup.service
    63ms systemd-user-sessions.service
    62ms systemd-remount-fs.service
    58ms systemd-readahead-collect.service
    55ms sys-kernel-debug.mount
    43ms dev-sda2.swap
    43ms dev-mqueue.mount
    42ms dev-hugepages.mount
    26ms systemd-tmpfiles-setup.service
    20ms srv.mount
    13ms tmp.mount
    12ms systemd-udev.service
    10ms boot.mount
    9ms home.mount
    oliarch ~ sudo journalctl --no-pager -a | grep slim
    Jun 24 14:25:01 oliarch systemd[1]: slim.service: main process exited, code=exited, status=1
    Jun 24 14:25:01 oliarch systemd[1]: Unit slim.service entered failed state.

  • Slim freezes after entering login information

    I have a strange problem with Slim. I've used it for a while and everything has always worked fine (indeed, a different computer with similar setup is still fine), but two weeks ago I couldn't log in. The problem did not develop after an update of slim. I haven't found any similar symptoms described in the forums or wiki.
    I start slim through the inittab method, and I usually boot into awesome, but sometimes into openbox, so I followed the instructions for setting up slim for multiple environments. Booting into either worked fine previously.
    Now when booting, I can get to slim fine. If I immediately enter my user info and then hit "enter" to start the default WM (which is awesome), then slim just freezes. The user and password box disappear, but the background remains, and nothing else happens. I need to use ctl-alt-F1 to login again from tty and reboot. The strange thing is that if after booting, I enter my user info into slim and then hit "F1" then I can select awesome and boot normally. But just hitting enter after user and password (which should boot the default WM, which is awesome) without selecting awesome from F1 causes the freeze. Also, if I use F1 to select openbox, I get the same freeze.
    I have tried modifying my .xinitrc just to open awesome rather than using the multiple-environment setup (see below), and with this .xinitrc, I still got the freezing problem, but obviously couldn't get around it by using F1.
    Finally, if I get into awesome using the F1 method and then logout of awesome to go back to slim, then logging in to either awesome without hitting F1 or even logging in to openbox work fine. Very strange.
    My slim.log has absolutely nothing useful in it. Here are the last lines from the last 7 boots (the ones where it says "Slim: unexpected signal 15" are the ones where I had to use tty to reboot, the others are where I've booted successfully).
    slim: waiting for X server to begin accepting connections.
    slim: unexpected signal 15
    slim: waiting for X server to begin accepting connections.
    slim: waiting for X server to begin accepting connections.
    slim: unexpected signal 15
    slim: waiting for X server to begin accepting connections.
    slim: waiting for X server to begin accepting connections.
    slim: waiting for X server to begin accepting connections.
    slim: unexpected signal 15
    slim: waiting for X server to begin accepting connections.
    Here's my .xinitrc. When testing whether the multiple-environment setup was the problem, I commented everything except the last line (which I uncommented) and still had the same problem.
    #xset +fp /usr/share/fonts/local
    #xset fp rehash
    #exec ck-launch-session dbus-launch openbox-session
    DEFAULT_SESSION=awesome
    case $1 in
    awesome)
    # exec dbus-launch awesome
    exec awesome
    openbox)
    # exec dbus-launch openbox-session
    exec openbox-session
    exec $DEFAULT_SESSION
    esac
    #exec awesome
    Here's my slim.conf. Everything should be the default settings except for the login command (where I added "dbus-launch") and the sessions line where I specify options for awesome and openbox.
    # Path, X server and arguments (if needed)
    # Note: -xauth $authfile is automatically appended
    default_path /bin:/usr/bin:/usr/local/bin
    default_xserver /usr/bin/X
    xserver_arguments -nolisten tcp vt07
    # Commands for halt, login, etc.
    halt_cmd /sbin/shutdown -h now
    reboot_cmd /sbin/shutdown -r now
    console_cmd /usr/bin/xterm -C -fg white -bg black +sb -T "Console login" -e /bin/sh -c "/bin/cat /etc/issue; exec /bin/login"
    #suspend_cmd /usr/sbin/suspend
    # Full path to the xauth binary
    xauth_path /usr/bin/xauth
    # Xauth file for server
    authfile /var/run/slim.auth
    # Activate numlock when slim starts. Valid values: on|off
    # numlock on
    # Hide the mouse cursor (note: does not work with some WMs).
    # Valid values: true|false
    # hidecursor false
    # This command is executed after a succesful login.
    # you can place the %session and %theme variables
    # to handle launching of specific commands in .xinitrc
    # depending of chosen session and slim theme
    # NOTE: if your system does not have bash you need
    # to adjust the command according to your preferred shell,
    # i.e. for freebsd use:
    # login_cmd exec /bin/sh - ~/.xinitrc %session
    # login_cmd exec /bin/bash -login ~/.xinitrc %session
    login_cmd exec dbus-launch /bin/bash -login ~/.xinitrc %session
    # Commands executed when starting and exiting a session.
    # They can be used for registering a X11 session with
    # sessreg. You can use the %user variable
    # sessionstart_cmd some command
    # sessionstop_cmd some command
    # Start in daemon mode. Valid values: yes | no
    # Note that this can be overriden by the command line
    # options "-d" and "-nodaemon"
    # daemon yes
    # Available sessions (first one is the default).
    # The current chosen session name is replaced in the login_cmd
    # above, so your login command can handle different sessions.
    # see the xinitrc.sample file shipped with slim sources
    sessions awesome,openbox
    # Executed when pressing F11 (requires imagemagick)
    screenshot_cmd import -window root /slim.png
    # welcome message. Available variables: %host, %domain
    welcome_msg Welcome to %host
    # Session message. Prepended to the session name when pressing F1
    # session_msg Session:
    # shutdown / reboot messages
    shutdown_msg The system is halting...
    reboot_msg The system is rebooting...
    # default user, leave blank or remove this line
    # for avoid pre-loading the username.
    #default_user simone
    # Focus the password field on start when default_user is set
    # Set to "yes" to enable this feature
    #focus_password no
    # Automatically login the default user (without entering
    # the password. Set to "yes" to enable this feature
    #auto_login no
    # current theme, use comma separated list to specify a set to
    # randomly choose from
    current_theme default
    # Lock file
    lockfile /var/lock/slim.lock
    # Log file
    logfile /var/log/slim.log
    Anyway, I can get around this by using F1, but it is somewhat of a pain as sometimes I forget. Any ideas?

    I'm having a very similar problem.   My post is in the newbie corner forum.  So far, I have not found a solution.
    Rob
    rasteenb wrote:
    I solved my problem - slim was not the last daemon I started in rc.conf.  By moving it to the end, I get password auto-focus and everything works.
    Now my rc.conf looks like
    # DAEMONS
    DAEMONS=(syslog-ng dbus acpid @network @wicd @openntpd @cupsd @crond slim)
    I found this recommendation in the Display Manager wiki page while researching the problem:
    Ensure you start the display manager last in the DAEMONS array, otherwise X will later allocate a tty device which was previously claimed by Getty (see /etc/inittab). Not placing the display manager at the end can cause X crashes, and is therefore unsupported.
    I'd just been lucky before that there wasn't a conflict.
    There is a "flicker" during login where I'm shown the XFCE splash, then the SLIM splash again, then the XFCE desktop.  Not sure what's going on there, but it's no big deal.
    Cheers,
    Rob
    Last edited by rasteenb (2012-07-17 11:30:39)

  • Cannot login my Windows 8.1 Pro with my live ID, don't have the Microsoft Logon Option

    My laptop was installed with a Windows 8.1 Pro, and it worked very well before, i can login with my domain account and Windows Live ID, but today when i startup my laptop and i cannot find the option "Login with Microsoft/Live ID", i only can login
    with "Domain account/Local Account/SmartCard".
    Microsoft Account/Live ID is a local administrator but my domain account seems is not a local administrator.
    Now even i can login with my domain account, but i cannot change anything, because i'm not a administator, so how to make the "Microsoft Account" login available when i login the windows? (by the way, i cannot add a new login in the "Change
    PC Settings->Accounts", because my domain account is not a local administrator)
    thanks.
    William
    William

    Hi William,
    According to your description,I would like to know if you can see "Other User" option on the login screen.
    If you can see it,please click it and type your microsoft account.
    If you cannot see this option,please click Switch user to check the result.
    If the issue still persists, please upload the screenshot.
    Regards,
    Regards,
    Kelvin hsu
    TechNet Community Support

  • Boot time goes from seconds to minutes with udev and systemd

    A few weeks ago updated and saw that on reboot I was getting messages from systemd that it was waiting for all my LVM partitions, and then finally that:
    'A start job is running for udev Wait for Complete Device Initialization'
    This has never happened before and I can't find any information about it in dmesg.
    Here is my fstab:
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    # UUID=f9f12b36-2333-4c46-949a-0bd86e1ab254
    /dev/mapper/Linux-Arch / ext4 rw,relatime,data=ordered 0 1
    # UUID=21ee7aa4-234e-463d-af2a-6c4cb3551ea8
    /dev/mapper/Linux-Home /home ext4 rw,relatime,data=ordered 0 2
    # UUID=E421-470F LABEL=SYSTEM_DRV
    /dev/sda2 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
    # UUID=11bf5a3f-86a5-48b7-93da-994e39463f0d
    /dev/mapper/Linux-Swap none swap defaults 0 0
    # Windows
    # /dev/sda5 /mnt/Windows ntfs-3g defaults,ro,noauto 0 0
    I've been digging around for a few weeks and I can't find anything and my boot time is really slow.
    systemd-analyze blame:
    1min 1.644s systemd-udev-settle.service
    10.079s systemd-udev-trigger.service
    9.999s systemd-remount-fs.service
    1.003s lvm2-pvscan@8:8.service
    795ms systemd-timesyncd.service
    700ms systemd-update-utmp.service
    583ms systemd-sysctl.service
    560ms rtkit-daemon.service
    469ms udisks2.service
    449ms NetworkManager.service
    438ms kmod-static-nodes.service
    363ms systemd-vconsole-setup.service
    214ms tmp.mount
    184ms sys-kernel-debug.mount
    144ms sys-kernel-config.mount
    123ms systemd-tmpfiles-clean.service
    116ms dev-mqueue.mount
    90ms [email protected]
    85ms systemd-logind.service
    82ms dev-hugepages.mount
    79ms bluetooth.service
    57ms [email protected]
    42ms polkit.service
    31ms accounts-daemon.service
    31ms wpa_supplicant.service
    24ms systemd-fsck@dev-mapper-Linux\x2dHome.service
    20ms colord.service
    20ms gdm.service
    20ms upower.service
    19ms [email protected]
    18ms [email protected]
    17ms [email protected]
    15ms boot.mount
    12ms systemd-tmpfiles-setup-dev.service
    8ms dev-mapper-Linux\x2dSwap.swap
    8ms systemd-tmpfiles-setup.service
    8ms systemd-journal-flush.service
    5ms home.mount
    5ms systemd-user-sessions.service
    4ms systemd-backlight@backlight:intel_backlight.service
    3ms systemd-random-seed.service
    2ms systemd-udevd.service
    1ms sys-fs-fuse-connections.mount
    EDIT 2: Dmesg output:
    [ 0.000000] Initializing cgroup subsys cpuset
    [ 0.000000] Initializing cgroup subsys cpu
    [ 0.000000] Initializing cgroup subsys cpuacct
    [ 0.000000] Linux version 3.14.23-1-lts (nobody@home-andyrtr-arch64-chroots-testing-x86_64-andyrtr) (gcc version 4.9.1 20140903 (prerelease) (GCC) ) #1 SMP Thu Oct 30 19:41:12 CET 2014
    [ 0.000000] Command line: initrd=\initramfs-linux-lts.img root=/dev/mapper/Linux-Arch rw resume=/dev/mapper/Linux-Swap pcie_aspm=force i915.i915_enable_rc6=1
    [ 0.000000] e820: BIOS-provided physical RAM map:
    [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000087fff] usable
    [ 0.000000] BIOS-e820: [mem 0x0000000000088000-0x00000000000bffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable
    [ 0.000000] BIOS-e820: [mem 0x0000000020000000-0x00000000201fffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x0000000020200000-0x0000000040003fff] usable
    [ 0.000000] BIOS-e820: [mem 0x0000000040004000-0x0000000040004fff] reserved
    [ 0.000000] BIOS-e820: [mem 0x0000000040005000-0x00000000c4daffff] usable
    [ 0.000000] BIOS-e820: [mem 0x00000000c4db0000-0x00000000c61affff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000c61b0000-0x00000000ca7befff] usable
    [ 0.000000] BIOS-e820: [mem 0x00000000ca7bf000-0x00000000caebefff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000caebf000-0x00000000cafbefff] ACPI NVS
    [ 0.000000] BIOS-e820: [mem 0x00000000cafbf000-0x00000000caffefff] ACPI data
    [ 0.000000] BIOS-e820: [mem 0x00000000cafff000-0x00000000caffffff] usable
    [ 0.000000] BIOS-e820: [mem 0x00000000cb000000-0x00000000cf9fffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000f0000000-0x00000000f3ffffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000feb00000-0x00000000feb03fff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000fed10000-0x00000000fed19fff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000fed98000-0x00000000fed9ffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000ffcc0000-0x00000000ffffffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000022f5fffff] usable
    [ 0.000000] NX (Execute Disable) protection: active
    [ 0.000000] e820: update [mem 0xc3217018-0xc3227057] usable ==> usable
    [ 0.000000] extended physical RAM map:
    [ 0.000000] reserve setup_data: [mem 0x0000000000000000-0x0000000000087fff] usable
    [ 0.000000] reserve setup_data: [mem 0x0000000000088000-0x00000000000bffff] reserved
    [ 0.000000] reserve setup_data: [mem 0x0000000000100000-0x000000001fffffff] usable
    [ 0.000000] reserve setup_data: [mem 0x0000000020000000-0x00000000201fffff] reserved
    [ 0.000000] reserve setup_data: [mem 0x0000000020200000-0x0000000040003fff] usable
    [ 0.000000] reserve setup_data: [mem 0x0000000040004000-0x0000000040004fff] reserved
    [ 0.000000] reserve setup_data: [mem 0x0000000040005000-0x00000000c3217017] usable
    [ 0.000000] reserve setup_data: [mem 0x00000000c3217018-0x00000000c3227057] usable
    [ 0.000000] reserve setup_data: [mem 0x00000000c3227058-0x00000000c4daffff] usable
    [ 0.000000] reserve setup_data: [mem 0x00000000c4db0000-0x00000000c61affff] reserved
    [ 0.000000] reserve setup_data: [mem 0x00000000c61b0000-0x00000000ca7befff] usable
    [ 0.000000] reserve setup_data: [mem 0x00000000ca7bf000-0x00000000caebefff] reserved
    [ 0.000000] reserve setup_data: [mem 0x00000000caebf000-0x00000000cafbefff] ACPI NVS
    [ 0.000000] reserve setup_data: [mem 0x00000000cafbf000-0x00000000caffefff] ACPI data
    [ 0.000000] reserve setup_data: [mem 0x00000000cafff000-0x00000000caffffff] usable
    [ 0.000000] reserve setup_data: [mem 0x00000000cb000000-0x00000000cf9fffff] reserved
    [ 0.000000] reserve setup_data: [mem 0x00000000f0000000-0x00000000f3ffffff] reserved
    [ 0.000000] reserve setup_data: [mem 0x00000000feb00000-0x00000000feb03fff] reserved
    [ 0.000000] reserve setup_data: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
    [ 0.000000] reserve setup_data: [mem 0x00000000fed10000-0x00000000fed19fff] reserved
    [ 0.000000] reserve setup_data: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
    [ 0.000000] reserve setup_data: [mem 0x00000000fed98000-0x00000000fed9ffff] reserved
    [ 0.000000] reserve setup_data: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
    [ 0.000000] reserve setup_data: [mem 0x00000000ffcc0000-0x00000000ffffffff] reserved
    [ 0.000000] reserve setup_data: [mem 0x0000000100000000-0x000000022f5fffff] usable
    [ 0.000000] efi: EFI v2.31 by INSYDE Corp.
    [ 0.000000] efi: ACPI=0xcaffe000 ACPI 2.0=0xcaffe014 SMBIOS=0xcaebef98
    [ 0.000000] efi: mem00: type=3, attr=0xf, range=[0x0000000000000000-0x0000000000001000) (0MB)
    [ 0.000000] efi: mem01: type=2, attr=0xf, range=[0x0000000000001000-0x0000000000007000) (0MB)
    [ 0.000000] efi: mem02: type=7, attr=0xf, range=[0x0000000000007000-0x000000000006f000) (0MB)
    [ 0.000000] efi: mem03: type=4, attr=0xf, range=[0x000000000006f000-0x0000000000070000) (0MB)
    [ 0.000000] efi: mem04: type=7, attr=0xf, range=[0x0000000000070000-0x0000000000088000) (0MB)
    [ 0.000000] efi: mem05: type=6, attr=0x800000000000000f, range=[0x0000000000088000-0x00000000000a0000) (0MB)
    [ 0.000000] efi: mem06: type=7, attr=0xf, range=[0x0000000000100000-0x0000000001000000) (15MB)
    [ 0.000000] efi: mem07: type=2, attr=0xf, range=[0x0000000001000000-0x0000000001f62000) (15MB)
    [ 0.000000] efi: mem08: type=7, attr=0xf, range=[0x0000000001f62000-0x0000000020000000) (480MB)
    [ 0.000000] efi: mem09: type=0, attr=0xf, range=[0x0000000020000000-0x0000000020200000) (2MB)
    [ 0.000000] efi: mem10: type=7, attr=0xf, range=[0x0000000020200000-0x0000000040004000) (510MB)
    [ 0.000000] efi: mem11: type=0, attr=0xf, range=[0x0000000040004000-0x0000000040005000) (0MB)
    [ 0.000000] efi: mem12: type=7, attr=0xf, range=[0x0000000040005000-0x000000007fba4000) (1019MB)
    [ 0.000000] efi: mem13: type=2, attr=0xf, range=[0x000000007fba4000-0x0000000080000000) (4MB)
    [ 0.000000] efi: mem14: type=7, attr=0xf, range=[0x0000000080000000-0x00000000c31c0000) (1073MB)
    [ 0.000000] efi: mem15: type=4, attr=0xf, range=[0x00000000c31c0000-0x00000000c31e0000) (0MB)
    [ 0.000000] efi: mem16: type=7, attr=0xf, range=[0x00000000c31e0000-0x00000000c3217000) (0MB)
    [ 0.000000] efi: mem17: type=2, attr=0xf, range=[0x00000000c3217000-0x00000000c3228000) (0MB)
    [ 0.000000] efi: mem18: type=1, attr=0xf, range=[0x00000000c3228000-0x00000000c418a000) (15MB)
    [ 0.000000] efi: mem19: type=4, attr=0xf, range=[0x00000000c418a000-0x00000000c4db0000) (12MB)
    [ 0.000000] efi: mem20: type=0, attr=0xf, range=[0x00000000c4db0000-0x00000000c61b0000) (20MB)
    [ 0.000000] efi: mem21: type=7, attr=0xf, range=[0x00000000c61b0000-0x00000000c61b8000) (0MB)
    [ 0.000000] efi: mem22: type=2, attr=0xf, range=[0x00000000c61b8000-0x00000000c61bb000) (0MB)
    [ 0.000000] efi: mem23: type=7, attr=0xf, range=[0x00000000c61bb000-0x00000000c61bc000) (0MB)
    [ 0.000000] efi: mem24: type=2, attr=0xf, range=[0x00000000c61bc000-0x00000000c61bf000) (0MB)
    [ 0.000000] efi: mem25: type=7, attr=0xf, range=[0x00000000c61bf000-0x00000000c63a8000) (1MB)
    [ 0.000000] efi: mem26: type=1, attr=0xf, range=[0x00000000c63a8000-0x00000000c63bf000) (0MB)
    [ 0.000000] efi: mem27: type=7, attr=0xf, range=[0x00000000c63bf000-0x00000000c76e6000) (19MB)
    [ 0.000000] efi: mem28: type=4, attr=0xf, range=[0x00000000c76e6000-0x00000000c864a000) (15MB)
    [ 0.000000] efi: mem29: type=7, attr=0xf, range=[0x00000000c864a000-0x00000000c864c000) (0MB)
    [ 0.000000] efi: mem30: type=4, attr=0xf, range=[0x00000000c864c000-0x00000000c864e000) (0MB)
    [ 0.000000] efi: mem31: type=7, attr=0xf, range=[0x00000000c864e000-0x00000000c8650000) (0MB)
    [ 0.000000] efi: mem32: type=4, attr=0xf, range=[0x00000000c8650000-0x00000000c8697000) (0MB)
    [ 0.000000] efi: mem33: type=7, attr=0xf, range=[0x00000000c8697000-0x00000000c8699000) (0MB)
    [ 0.000000] efi: mem34: type=4, attr=0xf, range=[0x00000000c8699000-0x00000000c86cb000) (0MB)
    [ 0.000000] efi: mem35: type=7, attr=0xf, range=[0x00000000c86cb000-0x00000000c86cc000) (0MB)
    [ 0.000000] efi: mem36: type=4, attr=0xf, range=[0x00000000c86cc000-0x00000000c87ff000) (1MB)
    [ 0.000000] efi: mem37: type=7, attr=0xf, range=[0x00000000c87ff000-0x00000000c8803000) (0MB)
    [ 0.000000] efi: mem38: type=4, attr=0xf, range=[0x00000000c8803000-0x00000000c8806000) (0MB)
    [ 0.000000] efi: mem39: type=7, attr=0xf, range=[0x00000000c8806000-0x00000000c8807000) (0MB)
    [ 0.000000] efi: mem40: type=4, attr=0xf, range=[0x00000000c8807000-0x00000000c885a000) (0MB)
    [ 0.000000] efi: mem41: type=7, attr=0xf, range=[0x00000000c885a000-0x00000000c8882000) (0MB)
    [ 0.000000] efi: mem42: type=4, attr=0xf, range=[0x00000000c8882000-0x00000000c88b0000) (0MB)
    [ 0.000000] efi: mem43: type=7, attr=0xf, range=[0x00000000c88b0000-0x00000000c88b1000) (0MB)
    [ 0.000000] efi: mem44: type=4, attr=0xf, range=[0x00000000c88b1000-0x00000000c8c65000) (3MB)
    [ 0.000000] efi: mem45: type=7, attr=0xf, range=[0x00000000c8c65000-0x00000000c8c67000) (0MB)
    [ 0.000000] efi: mem46: type=4, attr=0xf, range=[0x00000000c8c67000-0x00000000c8c78000) (0MB)
    [ 0.000000] efi: mem47: type=7, attr=0xf, range=[0x00000000c8c78000-0x00000000c8c7a000) (0MB)
    [ 0.000000] efi: mem48: type=4, attr=0xf, range=[0x00000000c8c7a000-0x00000000ca3bf000) (23MB)
    [ 0.000000] efi: mem49: type=7, attr=0xf, range=[0x00000000ca3bf000-0x00000000ca435000) (0MB)
    [ 0.000000] efi: mem50: type=3, attr=0xf, range=[0x00000000ca435000-0x00000000ca7bf000) (3MB)
    [ 0.000000] efi: mem51: type=5, attr=0x800000000000000f, range=[0x00000000ca7bf000-0x00000000ca865000) (0MB)
    [ 0.000000] efi: mem52: type=6, attr=0x800000000000000f, range=[0x00000000ca865000-0x00000000ca866000) (0MB)
    [ 0.000000] efi: mem53: type=5, attr=0x800000000000000f, range=[0x00000000ca866000-0x00000000ca868000) (0MB)
    [ 0.000000] efi: mem54: type=6, attr=0x800000000000000f, range=[0x00000000ca868000-0x00000000ca869000) (0MB)
    [ 0.000000] efi: mem55: type=5, attr=0x800000000000000f, range=[0x00000000ca869000-0x00000000ca86f000) (0MB)
    [ 0.000000] efi: mem56: type=6, attr=0x800000000000000f, range=[0x00000000ca86f000-0x00000000ca870000) (0MB)
    [ 0.000000] efi: mem57: type=5, attr=0x800000000000000f, range=[0x00000000ca870000-0x00000000ca883000) (0MB)
    [ 0.000000] efi: mem58: type=6, attr=0x800000000000000f, range=[0x00000000ca883000-0x00000000ca884000) (0MB)
    [ 0.000000] efi: mem59: type=5, attr=0x800000000000000f, range=[0x00000000ca884000-0x00000000ca894000) (0MB)
    [ 0.000000] efi: mem60: type=6, attr=0x800000000000000f, range=[0x00000000ca894000-0x00000000ca895000) (0MB)
    [ 0.000000] efi: mem61: type=5, attr=0x800000000000000f, range=[0x00000000ca895000-0x00000000ca8a9000) (0MB)
    [ 0.000000] efi: mem62: type=6, attr=0x800000000000000f, range=[0x00000000ca8a9000-0x00000000ca8aa000) (0MB)
    [ 0.000000] efi: mem63: type=5, attr=0x800000000000000f, range=[0x00000000ca8aa000-0x00000000ca8e3000) (0MB)
    [ 0.000000] efi: mem64: type=6, attr=0x800000000000000f, range=[0x00000000ca8e3000-0x00000000ca935000) (0MB)
    [ 0.000000] efi: mem65: type=5, attr=0x800000000000000f, range=[0x00000000ca935000-0x00000000ca9bf000) (0MB)
    [ 0.000000] efi: mem66: type=6, attr=0x800000000000000f, range=[0x00000000ca9bf000-0x00000000caabf000) (1MB)
    [ 0.000000] efi: mem67: type=0, attr=0xf, range=[0x00000000caabf000-0x00000000caebf000) (4MB)
    [ 0.000000] efi: mem68: type=10, attr=0xf, range=[0x00000000caebf000-0x00000000cafbf000) (1MB)
    [ 0.000000] efi: mem69: type=9, attr=0xf, range=[0x00000000cafbf000-0x00000000cafff000) (0MB)
    [ 0.000000] efi: mem70: type=4, attr=0xf, range=[0x00000000cafff000-0x00000000cb000000) (0MB)
    [ 0.000000] efi: mem71: type=7, attr=0xf, range=[0x0000000100000000-0x000000022f600000) (4854MB)
    [ 0.000000] efi: mem72: type=0, attr=0x0, range=[0x00000000000a0000-0x00000000000c0000) (0MB)
    [ 0.000000] efi: mem73: type=0, attr=0x0, range=[0x00000000cb000000-0x00000000cfa00000) (74MB)
    [ 0.000000] efi: mem74: type=11, attr=0x8000000000000001, range=[0x00000000f0000000-0x00000000f4000000) (64MB)
    [ 0.000000] efi: mem75: type=11, attr=0x8000000000000001, range=[0x00000000feb00000-0x00000000feb04000) (0MB)
    [ 0.000000] efi: mem76: type=11, attr=0x8000000000000001, range=[0x00000000fec00000-0x00000000fec01000) (0MB)
    [ 0.000000] efi: mem77: type=11, attr=0x8000000000000001, range=[0x00000000fed10000-0x00000000fed1a000) (0MB)
    [ 0.000000] efi: mem78: type=11, attr=0x8000000000000001, range=[0x00000000fed1c000-0x00000000fed20000) (0MB)
    [ 0.000000] efi: mem79: type=0, attr=0x0, range=[0x00000000fed98000-0x00000000feda0000) (0MB)
    [ 0.000000] efi: mem80: type=11, attr=0x8000000000000001, range=[0x00000000fee00000-0x00000000fee01000) (0MB)
    [ 0.000000] efi: mem81: type=11, attr=0x8000000000000000, range=[0x00000000ffcc0000-0x0000000100000000) (3MB)
    [ 0.000000] SMBIOS 2.7 present.
    [ 0.000000] DMI: LENOVO 20175/INVALID, BIOS 66CN54WW 01/21/2013
    [ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
    [ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
    [ 0.000000] No AGP bridge found
    [ 0.000000] e820: last_pfn = 0x22f600 max_arch_pfn = 0x400000000
    [ 0.000000] MTRR default type: uncachable
    [ 0.000000] MTRR fixed ranges enabled:
    [ 0.000000] 00000-9FFFF write-back
    [ 0.000000] A0000-BFFFF uncachable
    [ 0.000000] C0000-E7FFF write-protect
    [ 0.000000] E8000-EFFFF write-combining
    [ 0.000000] F0000-FFFFF write-protect
    [ 0.000000] MTRR variable ranges enabled:
    [ 0.000000] 0 base 000000000 mask F80000000 write-back
    [ 0.000000] 1 base 080000000 mask FC0000000 write-back
    [ 0.000000] 2 base 0C0000000 mask FF8000000 write-back
    [ 0.000000] 3 base 0C8000000 mask FFE000000 write-back
    [ 0.000000] 4 base 0CA000000 mask FFF000000 write-back
    [ 0.000000] 5 base 0FFC00000 mask FFFC00000 write-protect
    [ 0.000000] 6 base 100000000 mask F00000000 write-back
    [ 0.000000] 7 base 200000000 mask FC0000000 write-back
    [ 0.000000] 8 base 22F600000 mask FFFE00000 uncachable
    [ 0.000000] 9 base 22F800000 mask FFF800000 uncachable
    [ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    [ 0.000000] e820: last_pfn = 0xcb000 max_arch_pfn = 0x400000000
    [ 0.000000] Scanning 1 areas for low memory corruption
    [ 0.000000] Base memory trampoline at [ffff880000082000] 82000 size 24576
    [ 0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
    [ 0.000000] [mem 0x00000000-0x000fffff] page 4k
    [ 0.000000] BRK [0x01b40000, 0x01b40fff] PGTABLE
    [ 0.000000] BRK [0x01b41000, 0x01b41fff] PGTABLE
    [ 0.000000] BRK [0x01b42000, 0x01b42fff] PGTABLE
    [ 0.000000] init_memory_mapping: [mem 0x22f400000-0x22f5fffff]
    [ 0.000000] [mem 0x22f400000-0x22f5fffff] page 2M
    [ 0.000000] BRK [0x01b43000, 0x01b43fff] PGTABLE
    [ 0.000000] init_memory_mapping: [mem 0x22c000000-0x22f3fffff]
    [ 0.000000] [mem 0x22c000000-0x22f3fffff] page 2M
    [ 0.000000] init_memory_mapping: [mem 0x200000000-0x22bffffff]
    [ 0.000000] [mem 0x200000000-0x22bffffff] page 2M
    [ 0.000000] init_memory_mapping: [mem 0x00100000-0x1fffffff]
    [ 0.000000] [mem 0x00100000-0x001fffff] page 4k
    [ 0.000000] [mem 0x00200000-0x1fffffff] page 2M
    [ 0.000000] init_memory_mapping: [mem 0x20200000-0x40003fff]
    [ 0.000000] [mem 0x20200000-0x3fffffff] page 2M
    [ 0.000000] [mem 0x40000000-0x40003fff] page 4k
    [ 0.000000] BRK [0x01b44000, 0x01b44fff] PGTABLE
    [ 0.000000] BRK [0x01b45000, 0x01b45fff] PGTABLE
    [ 0.000000] init_memory_mapping: [mem 0x40005000-0xc4daffff]
    [ 0.000000] [mem 0x40005000-0x401fffff] page 4k
    [ 0.000000] [mem 0x40200000-0xc4bfffff] page 2M
    [ 0.000000] [mem 0xc4c00000-0xc4daffff] page 4k
    [ 0.000000] init_memory_mapping: [mem 0xc61b0000-0xca7befff]
    [ 0.000000] [mem 0xc61b0000-0xc61fffff] page 4k
    [ 0.000000] [mem 0xc6200000-0xca5fffff] page 2M
    [ 0.000000] [mem 0xca600000-0xca7befff] page 4k
    [ 0.000000] init_memory_mapping: [mem 0xcafff000-0xcaffffff]
    [ 0.000000] [mem 0xcafff000-0xcaffffff] page 4k
    [ 0.000000] init_memory_mapping: [mem 0x100000000-0x1ffffffff]
    [ 0.000000] [mem 0x100000000-0x1ffffffff] page 2M
    [ 0.000000] RAMDISK: [mem 0x7fba4000-0x7fffffff]
    [ 0.000000] ACPI: RSDP 00000000caffe014 000024 (v02 LENOVO)
    [ 0.000000] ACPI: XSDT 00000000caffe210 0000DC (v01 LENOVO CB-01 00000001 01000013)
    [ 0.000000] ACPI: FACP 00000000caff5000 00010C (v05 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: DSDT 00000000cafe9000 008814 (v01 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: FACS 00000000cafbb000 000040
    [ 0.000000] ACPI: SLIC 00000000caffd000 000176 (v01 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: UEFI 00000000caffc000 000236 (v01 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: SSDT 00000000caffb000 000662 (v01 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: SSDT 00000000caffa000 000A39 (v01 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: SSDT 00000000caff9000 000098 (v01 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: SSDT 00000000caff8000 000058 (v01 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: SSDT 00000000caff7000 000757 (v01 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: ASF! 00000000caff6000 0000A5 (v32 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: HPET 00000000caff4000 000038 (v01 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: APIC 00000000caff3000 00008C (v03 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: MCFG 00000000caff2000 00003C (v01 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: WDAT 00000000cafe8000 000224 (v01 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: SSDT 00000000cafe6000 001068 (v01 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: BOOT 00000000cafe4000 000028 (v01 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: ASPT 00000000cafe2000 000034 (v07 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: DBGP 00000000cafe1000 000034 (v01 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: FPDT 00000000cafdf000 000044 (v01 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: MSDM 00000000cafde000 000055 (v03 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: SSDT 00000000cafdd000 0009AA (v01 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: SSDT 00000000cafdc000 000B22 (v01 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: DMAR 00000000cafdb000 0000B8 (v01 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: BGRT 00000000cafda000 000038 (v01 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: Local APIC address 0xfee00000
    [ 0.000000] No NUMA configuration found
    [ 0.000000] Faking a node at [mem 0x0000000000000000-0x000000022f5fffff]
    [ 0.000000] Initmem setup node 0 [mem 0x00000000-0x22f5fffff]
    [ 0.000000] NODE_DATA [mem 0x22f5f1000-0x22f5f5fff]
    [ 0.000000] [ffffea0000000000-ffffea0008bfffff] PMD -> [ffff880226c00000-ffff88022ebfffff] on node 0
    [ 0.000000] Zone ranges:
    [ 0.000000] DMA [mem 0x00001000-0x00ffffff]
    [ 0.000000] DMA32 [mem 0x01000000-0xffffffff]
    [ 0.000000] Normal [mem 0x100000000-0x22f5fffff]
    [ 0.000000] Movable zone start for each node
    [ 0.000000] Early memory node ranges
    [ 0.000000] node 0: [mem 0x00001000-0x00087fff]
    [ 0.000000] node 0: [mem 0x00100000-0x1fffffff]
    [ 0.000000] node 0: [mem 0x20200000-0x40003fff]
    [ 0.000000] node 0: [mem 0x40005000-0xc4daffff]
    [ 0.000000] node 0: [mem 0xc61b0000-0xca7befff]
    [ 0.000000] node 0: [mem 0xcafff000-0xcaffffff]
    [ 0.000000] node 0: [mem 0x100000000-0x22f5fffff]
    [ 0.000000] On node 0 totalpages: 2066246
    [ 0.000000] DMA zone: 64 pages used for memmap
    [ 0.000000] DMA zone: 22 pages reserved
    [ 0.000000] DMA zone: 3975 pages, LIFO batch:0
    [ 0.000000] DMA32 zone: 12807 pages used for memmap
    [ 0.000000] DMA32 zone: 819647 pages, LIFO batch:31
    [ 0.000000] Normal zone: 19416 pages used for memmap
    [ 0.000000] Normal zone: 1242624 pages, LIFO batch:31
    [ 0.000000] ACPI: PM-Timer IO Port: 0x408
    [ 0.000000] ACPI: Local APIC address 0xfee00000
    [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x00] disabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x00] disabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x00] disabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x00] disabled)
    [ 0.000000] ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
    [ 0.000000] IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
    [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    [ 0.000000] ACPI: IRQ0 used by override.
    [ 0.000000] ACPI: IRQ2 used by override.
    [ 0.000000] ACPI: IRQ9 used by override.
    [ 0.000000] Using ACPI (MADT) for SMP configuration information
    [ 0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
    [ 0.000000] smpboot: Allowing 8 CPUs, 4 hotplug CPUs
    [ 0.000000] nr_irqs_gsi: 40
    [ 0.000000] PM: Registered nosave memory: [mem 0x00088000-0x000bffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0x000c0000-0x000fffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0x20000000-0x201fffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0x40004000-0x40004fff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xc3217000-0xc3217fff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xc3227000-0xc3227fff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xc4db0000-0xc61affff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xca7bf000-0xcaebefff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xcaebf000-0xcafbefff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xcafbf000-0xcaffefff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xcb000000-0xcf9fffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xcfa00000-0xefffffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xf0000000-0xf3ffffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xf4000000-0xfeafffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xfeb00000-0xfeb03fff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xfeb04000-0xfebfffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xfec01000-0xfed0ffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xfed10000-0xfed19fff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xfed1a000-0xfed1bfff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfed97fff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xfed98000-0xfed9ffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xfeda0000-0xfedfffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xfee01000-0xffcbffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xffcc0000-0xffffffff]
    [ 0.000000] e820: [mem 0xcfa00000-0xefffffff] available for PCI devices
    [ 0.000000] Booting paravirtualized kernel on bare hardware
    [ 0.000000] setup_percpu: NR_CPUS:128 nr_cpumask_bits:128 nr_cpu_ids:8 nr_node_ids:1
    [ 0.000000] PERCPU: Embedded 29 pages/cpu @ffff88022f200000 s86656 r8192 d23936 u262144
    [ 0.000000] pcpu-alloc: s86656 r8192 d23936 u262144 alloc=1*2097152
    [ 0.000000] pcpu-alloc: [0] 0 1 2 3 4 5 6 7
    [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 2033937
    [ 0.000000] Policy zone: Normal
    [ 0.000000] Kernel command line: initrd=\initramfs-linux-lts.img root=/dev/mapper/Linux-Arch rw resume=/dev/mapper/Linux-Swap pcie_aspm=force i915.i915_enable_rc6=1
    [ 0.000000] PCIe ASPM is forcibly enabled
    [ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
    [ 0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
    [ 0.000000] Checking aperture...
    [ 0.000000] No AGP bridge found
    [ 0.000000] Calgary: detecting Calgary via BIOS EBDA area
    [ 0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
    [ 0.000000] Memory: 7988560K/8264984K available (5187K kernel code, 858K rwdata, 1640K rodata, 1136K init, 1300K bss, 276424K reserved)
    [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
    [ 0.000000] Hierarchical RCU implementation.
    [ 0.000000] RCU restricting CPUs from NR_CPUS=128 to nr_cpu_ids=8.
    [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
    [ 0.000000] NR_IRQS:8448 nr_irqs:744 16
    [ 0.000000] Console: colour dummy device 80x25
    [ 0.000000] console [tty0] enabled
    [ 0.000000] allocated 33554432 bytes of page_cgroup
    [ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
    [ 0.000000] hpet clockevent registered
    [ 0.000000] tsc: Fast TSC calibration using PIT
    [ 0.000000] tsc: Detected 2494.263 MHz processor
    [ 0.000042] Calibrating delay loop (skipped), value calculated using timer frequency.. 4988.52 BogoMIPS (lpj=24942630)
    [ 0.000045] pid_max: default: 32768 minimum: 301
    [ 0.000053] ACPI: Core revision 20131218
    [ 0.008110] ACPI: All ACPI Tables successfully acquired
    [ 0.034617] Security Framework initialized
    [ 0.034625] Yama: becoming mindful.
    [ 0.035238] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
    [ 0.037855] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
    [ 0.039006] Mount-cache hash table entries: 16384 (order: 5, 131072 bytes)
    [ 0.039017] Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes)
    [ 0.039253] Initializing cgroup subsys memory
    [ 0.039259] Initializing cgroup subsys devices
    [ 0.039260] Initializing cgroup subsys freezer
    [ 0.039262] Initializing cgroup subsys net_cls
    [ 0.039264] Initializing cgroup subsys blkio
    [ 0.039291] CPU: Physical Processor ID: 0
    [ 0.039293] CPU: Processor Core ID: 0
    [ 0.039298] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
    ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
    [ 0.039769] mce: CPU supports 7 MCE banks
    [ 0.039782] CPU0: Thermal monitoring enabled (TM1)
    [ 0.039792] Last level iTLB entries: 4KB 512, 2MB 8, 4MB 8
    Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32, 1GB 0
    tlb_flushall_shift: 2
    [ 0.039910] Freeing SMP alternatives memory: 20K (ffffffff819f4000 - ffffffff819f9000)
    [ 0.043468] ftrace: allocating 20111 entries in 79 pages
    [ 0.054896] dmar: Host address width 36
    [ 0.054899] dmar: DRHD base: 0x000000fed90000 flags: 0x0
    [ 0.054906] dmar: IOMMU 0: reg_base_addr fed90000 ver 1:0 cap c0000020e60262 ecap f0101a
    [ 0.054908] dmar: DRHD base: 0x000000fed91000 flags: 0x1
    [ 0.054912] dmar: IOMMU 1: reg_base_addr fed91000 ver 1:0 cap c9008020660262 ecap f0105a
    [ 0.054914] dmar: RMRR base: 0x000000cae8c000 end: 0x000000caeabfff
    [ 0.054915] dmar: RMRR base: 0x000000cb800000 end: 0x000000cf9fffff
    [ 0.054992] IOAPIC id 0 under DRHD base 0xfed91000 IOMMU 1
    [ 0.054994] HPET id 0 under DRHD base 0xfed91000
    [ 0.054995] Queued invalidation will be enabled to support x2apic and Intr-remapping.
    [ 0.055169] Enabled IRQ remapping in x2apic mode
    [ 0.055170] Enabling x2apic
    [ 0.055172] Enabled x2apic
    [ 0.055180] Switched APIC routing to cluster x2apic.
    [ 0.055649] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    [ 0.155770] smpboot: CPU0: Intel(R) Core(TM) i7-3537U CPU @ 2.00GHz (fam: 06, model: 3a, stepping: 09)
    [ 0.155781] TSC deadline timer enabled
    [ 0.155793] Performance Events: PEBS fmt1+, 16-deep LBR, IvyBridge events, full-width counters, Intel PMU driver.
    [ 0.155800] ... version: 3
    [ 0.155802] ... bit width: 48
    [ 0.155803] ... generic registers: 4
    [ 0.155804] ... value mask: 0000ffffffffffff
    [ 0.155805] ... max period: 0000ffffffffffff
    [ 0.155806] ... fixed-purpose events: 3
    [ 0.155807] ... event mask: 000000070000000f
    [ 0.157083] x86: Booting SMP configuration:
    [ 0.157086] .... node #0, CPUs: #1 #2 #3
    [ 0.198397] x86: Booted up 1 node, 4 CPUs
    [ 0.198401] smpboot: Total of 4 processors activated (19954.10 BogoMIPS)
    [ 0.202933] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
    [ 0.203185] devtmpfs: initialized
    [ 0.206444] PM: Registering ACPI NVS region [mem 0xcaebf000-0xcafbefff] (1048576 bytes)
    [ 0.207361] pinctrl core: initialized pinctrl subsystem
    [ 0.207403] RTC time: 18:04:53, date: 11/03/14
    [ 0.207440] NET: Registered protocol family 16
    [ 0.207534] cpuidle: using governor ladder
    [ 0.207535] cpuidle: using governor menu
    [ 0.207568] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
    [ 0.207570] ACPI: bus type PCI registered
    [ 0.207572] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
    [ 0.207648] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf0000000-0xf3ffffff] (base 0xf0000000)
    [ 0.207651] PCI: MMCONFIG at [mem 0xf0000000-0xf3ffffff] reserved in E820
    [ 0.207745] PCI: Using configuration type 1 for base access
    [ 0.208531] bio: create slab <bio-0> at 0
    [ 0.208645] ACPI: Added _OSI(Module Device)
    [ 0.208647] ACPI: Added _OSI(Processor Device)
    [ 0.208648] ACPI: Added _OSI(3.0 _SCP Extensions)
    [ 0.208649] ACPI: Added _OSI(Processor Aggregator Device)
    [ 0.211733] ACPI: Executed 1 blocks of module-level executable AML code
    [ 0.236410] ACPI: SSDT 00000000cae17018 00083B (v01 PmRef Cpu0Cst 00003001 INTL 20121220)
    [ 0.236803] ACPI: Dynamic OEM Table Load:
    [ 0.236805] ACPI: SSDT (null) 00083B (v01 PmRef Cpu0Cst 00003001 INTL 20121220)
    [ 0.266214] ACPI: SSDT 00000000cae18a98 000303 (v01 PmRef ApIst 00003000 INTL 20121220)
    [ 0.266634] ACPI: Dynamic OEM Table Load:
    [ 0.266636] ACPI: SSDT (null) 000303 (v01 PmRef ApIst 00003000 INTL 20121220)
    [ 0.296118] ACPI: SSDT 00000000cae16d98 000119 (v01 PmRef ApCst 00003000 INTL 20121220)
    [ 0.296501] ACPI: Dynamic OEM Table Load:
    [ 0.296503] ACPI: SSDT (null) 000119 (v01 PmRef ApCst 00003000 INTL 20121220)
    [ 0.773800] ACPI: Interpreter enabled
    [ 0.773808] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131218/hwxface-580)
    [ 0.773813] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131218/hwxface-580)
    [ 0.773829] ACPI: (supports S0 S3 S4 S5)
    [ 0.773831] ACPI: Using IOAPIC for interrupt routing
    [ 0.773864] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
    [ 0.774030] ACPI: No dock devices found.
    [ 0.780437] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
    [ 0.780443] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
    [ 0.780579] \_SB_.PCI0:_OSC invalid UUID
    [ 0.780581] _OSC request data:1 1f 0
    [ 0.780585] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
    [ 0.781130] PCI host bridge to bus 0000:00
    [ 0.781133] pci_bus 0000:00: root bus resource [bus 00-3e]
    [ 0.781136] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
    [ 0.781137] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
    [ 0.781139] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
    [ 0.781141] pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000c3fff]
    [ 0.781143] pci_bus 0000:00: root bus resource [mem 0x000c4000-0x000c7fff]
    [ 0.781145] pci_bus 0000:00: root bus resource [mem 0x000c8000-0x000cbfff]
    [ 0.781147] pci_bus 0000:00: root bus resource [mem 0x000cc000-0x000cffff]
    [ 0.781148] pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d3fff]
    [ 0.781150] pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff]
    [ 0.781152] pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff]
    [ 0.781154] pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff]
    [ 0.781156] pci_bus 0000:00: root bus resource [mem 0x000e0000-0x000e3fff]
    [ 0.781157] pci_bus 0000:00: root bus resource [mem 0x000e4000-0x000e7fff]
    [ 0.781159] pci_bus 0000:00: root bus resource [mem 0x000e8000-0x000ebfff]
    [ 0.781161] pci_bus 0000:00: root bus resource [mem 0x000ec000-0x000effff]
    [ 0.781163] pci_bus 0000:00: root bus resource [mem 0xcfa00000-0xfeafffff]
    [ 0.781171] pci 0000:00:00.0: [8086:0154] type 00 class 0x060000
    [ 0.781277] pci 0000:00:02.0: [8086:0166] type 00 class 0x030000
    [ 0.781291] pci 0000:00:02.0: reg 0x10: [mem 0xe0000000-0xe03fffff 64bit]
    [ 0.781299] pci 0000:00:02.0: reg 0x18: [mem 0xd0000000-0xdfffffff 64bit pref]
    [ 0.781305] pci 0000:00:02.0: reg 0x20: [io 0x2000-0x203f]
    [ 0.781403] pci 0000:00:04.0: [8086:0153] type 00 class 0x118000
    [ 0.781415] pci 0000:00:04.0: reg 0x10: [mem 0xfed98000-0xfed9ffff 64bit]
    [ 0.781541] pci 0000:00:14.0: [8086:1e31] type 00 class 0x0c0330
    [ 0.781567] pci 0000:00:14.0: reg 0x10: [mem 0xe0400000-0xe040ffff 64bit]
    [ 0.781646] pci 0000:00:14.0: PME# supported from D3hot D3cold
    [ 0.781694] pci 0000:00:14.0: System wakeup disabled by ACPI
    [ 0.781745] pci 0000:00:16.0: [8086:1e3a] type 00 class 0x078000
    [ 0.781772] pci 0000:00:16.0: reg 0x10: [mem 0xe041c000-0xe041c00f 64bit]
    [ 0.781856] pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
    [ 0.781955] pci 0000:00:1a.0: [8086:1e2d] type 00 class 0x0c0320
    [ 0.781980] pci 0000:00:1a.0: reg 0x10: [mem 0xe0421000-0xe04213ff]
    [ 0.782080] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
    [ 0.782144] pci 0000:00:1a.0: System wakeup disabled by ACPI
    [ 0.782193] pci 0000:00:1b.0: [8086:1e20] type 00 class 0x040300
    [ 0.782212] pci 0000:00:1b.0: reg 0x10: [mem 0xe0418000-0xe041bfff 64bit]
    [ 0.782296] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
    [ 0.782345] pci 0000:00:1b.0: System wakeup disabled by ACPI
    [ 0.782396] pci 0000:00:1d.0: [8086:1e26] type 00 class 0x0c0320
    [ 0.782420] pci 0000:00:1d.0: reg 0x10: [mem 0xe0420000-0xe04203ff]
    [ 0.782520] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
    [ 0.782583] pci 0000:00:1d.0: System wakeup disabled by ACPI
    [ 0.782634] pci 0000:00:1f.0: [8086:1e56] type 00 class 0x060100
    [ 0.782828] pci 0000:00:1f.2: [8086:1e03] type 00 class 0x010601
    [ 0.782850] pci 0000:00:1f.2: reg 0x10: [io 0x2088-0x208f]
    [ 0.782859] pci 0000:00:1f.2: reg 0x14: [io 0x2094-0x2097]
    [ 0.782869] pci 0000:00:1f.2: reg 0x18: [io 0x2080-0x2087]
    [ 0.782877] pci 0000:00:1f.2: reg 0x1c: [io 0x2090-0x2093]
    [ 0.782887] pci 0000:00:1f.2: reg 0x20: [io 0x2060-0x207f]
    [ 0.782897] pci 0000:00:1f.2: reg 0x24: [mem 0xe041f000-0xe041f7ff]
    [ 0.782948] pci 0000:00:1f.2: PME# supported from D3hot
    [ 0.783031] pci 0000:00:1f.3: [8086:1e22] type 00 class 0x0c0500
    [ 0.783050] pci 0000:00:1f.3: reg 0x10: [mem 0xe041d000-0xe041d0ff 64bit]
    [ 0.783074] pci 0000:00:1f.3: reg 0x20: [io 0x2040-0x205f]
    [ 0.783173] pci 0000:00:1f.6: [8086:1e24] type 00 class 0x118000
    [ 0.783198] pci 0000:00:1f.6: reg 0x10: [mem 0xe041e000-0xe041efff 64bit]
    [ 0.783553] ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 10 11 12 14 15) *0, disabled.
    [ 0.783614] ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 10 11 12 14 15) *0, disabled.
    [ 0.783672] ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 10 11 12 14 15) *0, disabled.
    [ 0.783732] ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 10 11 12 14 15) *0, disabled.
    [ 0.783790] ACPI: PCI Interrupt Link [LNKE] (IRQs 1 3 4 5 6 10 11 12 14 15) *0, disabled.
    [ 0.783848] ACPI: PCI Interrupt Link [LNKF] (IRQs 1 3 4 5 6 10 11 12 14 15) *0, disabled.
    [ 0.783908] ACPI: PCI Interrupt Link [LNKG] (IRQs 1 3 4 5 6 10 11 12 14 15) *0, disabled.
    [ 0.783966] ACPI: PCI Interrupt Link [LNKH] (IRQs 1 3 4 5 6 10 11 12 14 15) *0, disabled.
    [ 0.784076] ACPI: Enabled 5 GPEs in block 00 to 3F
    [ 0.784121] ACPI : EC: GPE = 0x17, I/O: command/status = 0x66, data = 0x62
    [ 0.784209] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
    [ 0.784212] vgaarb: loaded
    [ 0.784213] vgaarb: bridge control possible 0000:00:02.0
    [ 0.784333] PCI: Using ACPI for IRQ routing
    [ 0.786165] PCI: pci_cache_line_size set to 64 bytes
    [ 0.786172] pci 0000:00:04.0: no compatible bridge window for [mem 0xfed98000-0xfed9ffff 64bit]
    [ 0.786212] e820: reserve RAM buffer [mem 0x00088000-0x0008ffff]
    [ 0.786214] e820: reserve RAM buffer [mem 0x40004000-0x43ffffff]
    [ 0.786216] e820: reserve RAM buffer [mem 0xc3217018-0xc3ffffff]
    [ 0.786217] e820: reserve RAM buffer [mem 0xc4db0000-0xc7ffffff]
    [ 0.786219] e820: reserve RAM buffer [mem 0xca7bf000-0xcbffffff]
    [ 0.786221] e820: reserve RAM buffer [mem 0xcb000000-0xcbffffff]
    [ 0.786222] e820: reserve RAM buffer [mem 0x22f600000-0x22fffffff]
    [ 0.786315] NetLabel: Initializing
    [ 0.786317] NetLabel: domain hash size = 128
    [ 0.786318] NetLabel: protocols = UNLABELED CIPSOv4
    [ 0.786331] NetLabel: unlabeled traffic allowed by default
    [ 0.786356] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
    [ 0.786361] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
    [ 0.788395] Switched to clocksource hpet
    [ 0.793449] pnp: PnP ACPI init
    [ 0.793466] ACPI: bus type PNP registered
    [ 0.793581] pnp 00:00: [dma 4]
    [ 0.793609] pnp 00:00: Plug and Play ACPI device, IDs PNP0200 (active)
    [ 0.793633] pnp 00:01: Plug and Play ACPI device, IDs INT0800 (active)
    [ 0.793732] pnp 00:02: Plug and Play ACPI device, IDs PNP0103 (active)
    [ 0.793773] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
    [ 0.793820] system 00:04: [io 0x0680-0x069f] has been reserved
    [ 0.793822] system 00:04: [io 0x1000-0x100f] has been reserved
    [ 0.793824] system 00:04: [io 0xffff] has been reserved
    [ 0.793826] system 00:04: [io 0xffff] has been reserved
    [ 0.793829] system 00:04: [io 0x0400-0x0453] could not be reserved
    [ 0.793831] system 00:04: [io 0x0458-0x047f] has been reserved
    [ 0.793833] system 00:04: [io 0x0500-0x057f] has been reserved
    [ 0.793835] system 00:04: [io 0x164e-0x164f] has been reserved
    [ 0.793838] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
    [ 0.793870] pnp 00:05: Plug and Play ACPI device, IDs PNP0b00 (active)
    [ 0.793919] system 00:06: [io 0x0454-0x0457] has been reserved
    [ 0.793922] system 00:06: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
    [ 0.793963] pnp 00:07: Plug and Play ACPI device, IDs PNP0303 (active)
    [ 0.794001] pnp 00:08: Plug and Play ACPI device, IDs SYN2b01 SYN2b00 SYN0002 PNP0f13 (active)
    [ 0.794134] system 00:09: [mem 0xfed1c000-0xfed1ffff] has been reserved
    [ 0.794137] system 00:09: [mem 0xfed10000-0xfed17fff] has been reserved
    [ 0.794139] system 00:09: [mem 0xfed18000-0xfed18fff] has been reserved
    [ 0.794141] system 00:09: [mem 0xfed19000-0xfed19fff] has been reserved
    [ 0.794143] system 00:09: [mem 0xf0000000-0xf3ffffff] has been reserved
    [ 0.794145] system 00:09: [mem 0xfed20000-0xfed3ffff] has been reserved
    [ 0.794148] system 00:09: [mem 0xfed90000-0xfed93fff] could not be reserved
    [ 0.794150] system 00:09: [mem 0xff000000-0xffffffff] could not be reserved
    [ 0.794152] system 00:09: [mem 0xfee00000-0xfeefffff] could not be reserved
    [ 0.794154] system 00:09: [mem 0xcfa00000-0xcfa00fff] has been reserved
    [ 0.794157] system 00:09: Plug and Play ACPI device, IDs PNP0c02 (active)
    [ 0.794451] system 00:0a: [mem 0x20000000-0x201fffff] has been reserved
    [ 0.794453] system 00:0a: [mem 0x40004000-0x40004fff] has been reserved
    [ 0.794456] system 00:0a: Plug and Play ACPI device, IDs PNP0c01 (active)
    [ 0.794473] pnp: PnP ACPI: found 11 devices
    [ 0.794475] ACPI: bus type PNP unregistered
    [ 0.801229] pci 0000:00:04.0: BAR 0: assigned [mem 0xcfa08000-0xcfa0ffff 64bit]
    [ 0.801237] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
    [ 0.801239] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
    [ 0.801241] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
    [ 0.801243] pci_bus 0000:00: resource 7 [mem 0x000c0000-0x000c3fff]
    [ 0.801245] pci_bus 0000:00: resource 8 [mem 0x000c4000-0x000c7fff]
    [ 0.801247] pci_bus 0000:00: resource 9 [mem 0x000c8000-0x000cbfff]
    [ 0.801249] pci_bus 0000:00: resource 10 [mem 0x000cc000-0x000cffff]
    [ 0.801251] pci_bus 0000:00: resource 11 [mem 0x000d0000-0x000d3fff]
    [ 0.801253] pci_bus 0000:00: resource 12 [mem 0x000d4000-0x000d7fff]
    [ 0.801254] pci_bus 0000:00: resource 13 [mem 0x000d8000-0x000dbfff]
    [ 0.801256] pci_bus 0000:00: resource 14 [mem 0x000dc000-0x000dffff]
    [ 0.801258] pci_bus 0000:00: resource 15 [mem 0x000e0000-0x000e3fff]
    [ 0.801260] pci_bus 0000:00: resource 16 [mem 0x000e4000-0x000e7fff]
    [ 0.801262] pci_bus 0000:00: resource 17 [mem 0x000e8000-0x000ebfff]
    [ 0.801264] pci_bus 0000:00: resource 18 [mem 0x000ec000-0x000effff]
    [ 0.801266] pci_bus 0000:00: resource 19 [mem 0xcfa00000-0xfeafffff]
    [ 0.801299] NET: Registered protocol family 2
    [ 0.801504] TCP established hash table entries: 65536 (order: 7, 524288 bytes)
    [ 0.801681] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
    [ 0.801864] TCP: Hash tables configured (established 65536 bind 65536)
    [ 0.801881] TCP: reno registered
    [ 0.801894] UDP hash table entries: 4096 (order: 5, 131072 bytes)
    [ 0.801927] UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
    [ 0.802001] NET: Registered protocol family 1
    [ 0.802012] pci 0000:00:02.0: Boot video device
    [ 0.838581] PCI: CLS 64 bytes, default 64
    [ 0.838623] Unpacking initramfs...
    [ 0.931743] Freeing initrd memory: 4464K (ffff88007fba4000 - ffff880080000000)
    [ 0.931755] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
    [ 0.931757] software IO TLB [mem 0xbf1c0000-0xc31c0000] (64MB) mapped at [ffff8800bf1c0000-ffff8800c31bffff]
    [ 0.931789] Simple Boot Flag at 0x44 set to 0x1
    [ 0.932025] microcode: CPU0 sig=0x306a9, pf=0x10, revision=0x17
    [ 0.932033] microcode: CPU1 sig=0x306a9, pf=0x10, revision=0x17
    [ 0.932042] microcode: CPU2 sig=0x306a9, pf=0x10, revision=0x17
    [ 0.932051] microcode: CPU3 sig=0x306a9, pf=0x10, revision=0x17
    [ 0.932111] microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
    [ 0.932127] Scanning for low memory corruption every 60 seconds
    [ 0.932408] futex hash table entries: 2048 (order: 5, 131072 bytes)
    [ 0.948267] HugeTLB registered 2 MB page size, pre-allocated 0 pages
    [ 0.949675] zbud: loaded
    [ 0.949848] VFS: Disk quotas dquot_6.5.2
    [ 0.949897] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
    [ 0.950024] msgmni has been set to 15732
    [ 0.950080] Key type big_key registered
    [ 0.950224] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
    [ 0.950262] io scheduler noop registered
    [ 0.950265] io scheduler deadline registered (default)
    [ 0.950296] io scheduler cfq registered
    [ 0.950355] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    [ 0.950370] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
    [ 0.950401] efifb: probing for efifb
    [ 0.950423] efifb: framebuffer at 0xd0000000, mapped to 0xffffc90004f00000, using 5628k, total 5625k
    [ 0.950425] efifb: mode is 1600x900x32, linelength=6400, pages=1
    [ 0.950426] efifb: scrolling: redraw
    [ 0.950428] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
    [ 0.955222] Console: switching to colour frame buffer device 200x56
    [ 0.959939] fb0: EFI VGA frame buffer device
    [ 0.959947] intel_idle: MWAIT substates: 0x21120
    [ 0.959948] intel_idle: v0.4 model 0x3A
    [ 0.959949] intel_idle: lapic_timer_reliable_states 0xffffffff
    [ 0.960140] GHES: HEST is not enabled!
    [ 0.960192] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    [ 0.960674] Linux agpgart interface v0.103
    [ 0.960719] rtc_cmos 00:05: RTC can wake from S4
    [ 0.960854] rtc_cmos 00:05: rtc core: registered rtc_cmos as rtc0
    [ 0.960891] rtc_cmos 00:05: alarms up to one month, 242 bytes nvram, hpet irqs
    [ 0.960901] Intel P-state driver initializing.
    [ 0.960913] Intel pstate controlling: cpu 0
    [ 0.960933] Intel pstate controlling: cpu 1
    [ 0.960948] Intel pstate controlling: cpu 2
    [ 0.960965] Intel pstate controlling: cpu 3
    [ 0.960993] ledtrig-cpu: registered to indicate activity on CPUs
    [ 0.961133] TCP: cubic registered
    [ 0.961239] NET: Registered protocol family 10
    [ 0.961427] NET: Registered protocol family 17
    [ 0.961965] registered taskstats version 1
    [ 0.962642] Magic number: 6:677:88
    [ 0.962705] acpi INT3F0D:00: hash matches
    [ 0.962828] rtc_cmos 00:05: setting system clock to 2014-11-03 18:04:54 UTC (1415037894)
    [ 0.963002] PM: Checking hibernation image partition /dev/mapper/Linux-Swap
    [ 0.963010] PM: Hibernation image not present or could not be loaded.
    [ 0.964972] Freeing unused kernel memory: 1136K (ffffffff818d8000 - ffffffff819f4000)
    [ 0.964975] Write protecting the kernel read-only data: 8192k
    [ 0.970240] Freeing unused kernel memory: 944K (ffff880001514000 - ffff880001600000)
    [ 0.971926] Freeing unused kernel memory: 408K (ffff88000179a000 - ffff880001800000)
    [ 0.980028] random: systemd-tmpfile urandom read with 3 bits of entropy available
    [ 0.981987] systemd-udevd[57]: starting version 216
    [ 0.993396] i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
    [ 0.999168] ACPI: bus type USB registered
    [ 0.999188] usbcore: registered new interface driver usbfs
    [ 0.999195] usbcore: registered new interface driver hub
    [ 0.999618] SCSI subsystem initialized
    [ 0.999671] usbcore: registered new device driver usb
    [ 1.000171] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    [ 1.000324] ehci-pci: EHCI PCI platform driver
    [ 1.000472] ehci-pci 0000:00:1a.0: EHCI Host Controller
    [ 1.000479] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
    [ 1.000498] ehci-pci 0000:00:1a.0: debug port 2
    [ 1.001114] libata version 3.00 loaded.
    [ 1.004412] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
    [ 1.004425] ehci-pci 0000:00:1a.0: irq 16, io mem 0xe0421000
    [ 1.005570] serio: i8042 KBD port at 0x60,0x64 irq 1
    [ 1.005576] serio: i8042 AUX port at 0x60,0x64 irq 12
    [ 1.018706] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
    [ 1.018976] hub 1-0:1.0: USB hub found
    [ 1.018989] hub 1-0:1.0: 2 ports detected
    [ 1.019277] ehci-pci 0000:00:1d.0: EHCI Host Controller
    [ 1.019281] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
    [ 1.019293] ehci-pci 0000:00:1d.0: debug port 2
    [ 1.023202] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
    [ 1.023218] ehci-pci 0000:00:1d.0: irq 23, io mem 0xe0420000
    [ 1.028001] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
    [ 1.038738] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
    [ 1.039375] hub 2-0:1.0: USB hub found
    [ 1.039401] hub 2-0:1.0: 2 ports detected
    [ 1.039970] xhci_hcd 0000:00:14.0: xHCI Host Controller
    [ 1.039984] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 3
    [ 1.040112] xhci_hcd 0000:00:14.0: cache line size of 64 is not supported
    [ 1.040137] xhci_hcd 0000:00:14.0: irq 42 for MSI/MSI-X
    [ 1.040384] hub 3-0:1.0: USB hub found
    [ 1.040404] hub 3-0:1.0: 4 ports detected
    [ 1.040970] xhci_hcd 0000:00:14.0: xHCI Host Controller
    [ 1.040975] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 4
    [ 1.041377] hub 4-0:1.0: USB hub found
    [ 1.041406] hub 4-0:1.0: 4 ports detected
    [ 1.041933] ahci 0000:00:1f.2: version 3.0
    [ 1.042141] ahci 0000:00:1f.2: irq 43 for MSI/MSI-X
    [ 1.042189] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 3 Gbps 0x1 impl SATA mode
    [ 1.042192] ahci 0000:00:1f.2: flags: 64bit ncq pm led clo pio slum part ems apst
    [ 1.042951] scsi0 : ahci
    [ 1.043089] scsi1 : ahci
    [ 1.043205] scsi2 : ahci
    [ 1.043321] scsi3 : ahci
    [ 1.043443] scsi4 : ahci
    [ 1.043605] scsi5 : ahci
    [ 1.043699] ata1: SATA max UDMA/133 abar m2048@0xe041f000 port 0xe041f100 irq 43
    [ 1.043704] ata2: DUMMY
    [ 1.043707] ata3: DUMMY
    [ 1.043709] ata4: DUMMY
    [ 1.043711] ata5: DUMMY
    [ 1.043713] ata6: DUMMY
    [ 1.339195] usb 1-1: new high-speed USB device number 2 using ehci-pci
    [ 1.389168] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    [ 1.390125] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
    [ 1.390134] ata1.00: ATA-9: SAMSUNG MZMTD256HAGM-000L1, DXT42L0Q, max UDMA/133
    [ 1.390139] ata1.00: 500118192 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
    [ 1.390821] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
    [ 1.390986] ata1.00: configured for UDMA/133
    [ 1.391372] scsi 0:0:0:0: Direct-Access ATA SAMSUNG MZMTD256 DXT4 PQ: 0 ANSI: 5
    [ 1.401296] sd 0:0:0:0: [sda] 500118192 512-byte logical blocks: (256 GB/238 GiB)
    [ 1.401579] sd 0:0:0:0: [sda] Write Protect is off
    [ 1.401588] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
    [ 1.401790] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [ 1.404906] sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8
    [ 1.406850] sd 0:0:0:0: [sda] Attached SCSI disk
    [ 1.490272] hub 1-1:1.0: USB hub found
    [ 1.490465] hub 1-1:1.0: 6 ports detected
    [ 1.512747] device-mapper: uevent: version 1.0.3
    [ 1.512926] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: [email protected]
    [ 1.519284] bio: create slab <bio-1> at 1
    [ 1.545404] PM: Starting manual resume from disk
    [ 1.545409] PM: Hibernation image partition 254:0 present
    [ 1.545411] PM: Looking for hibernation image.
    [ 1.545576] PM: Image not found (code -22)
    [ 1.545578] PM: Hibernation image not present or could not be loaded.
    [ 1.579429] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0).
    [ 1.579432] atkbd serio0: Use 'setkeycodes e03e <keycode>' to make it known.
    [ 1.583409] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null)
    [ 1.584558] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0).
    [ 1.584561] atkbd serio0: Use 'setkeycodes e03e <keycode>' to make it known.
    [ 1.609376] usb 2-1: new high-speed USB device number 2 using ehci-pci
    [ 1.665486] systemd[1]: Mounting cgroup to /sys/fs/cgroup/cpuset of type cgroup with options cpuset.
    [ 1.665742] systemd[1]: Mounting cgroup to /sys/fs/cgroup/cpu,cpuacct of type cgroup with options cpu,cpuacct.
    [ 1.665813] systemd[1]: Mounting cgroup to /sys/fs/cgroup/memory of type cgroup with options memory.
    [ 1.665853] systemd[1]: Mounting cgroup to /sys/fs/cgroup/devices of type cgroup with options devices.
    [ 1.665880] systemd[1]: Mounting cgroup to /sys/fs/cgroup/freezer of type cgroup with options freezer.
    [ 1.665906] systemd[1]: Mounting cgroup to /sys/fs/cgroup/net_cls of type cgroup with options net_cls.
    [ 1.665932] systemd[1]: Mounting cgroup to /sys/fs/cgroup/blkio of type cgroup with options blkio.
    [ 1.665987] systemd[1]: systemd 216 running in system mode. (+PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN )
    [ 1.666093] systemd[1]: Detected architecture 'x86-64'.
    [ 1.667499] systemd[1]: Set hostname to <arch-yogi>.
    [ 1.668059] systemd[1]: Using cgroup controller name=systemd. File system hierarchy is at /sys/fs/cgroup/systemd.
    [ 1.668094] systemd[1]: Installed release agent.
    [ 1.668133] systemd[1]: Set up TFD_TIMER_CANCEL_ON_SET timerfd.
    [ 1.669521] systemd[146]: Spawned /usr/lib/systemd/system-generators/systemd-getty-generator as 147.
    [ 1.669581] systemd[146]: Spawned /usr/lib/systemd/system-generators/systemd-gpt-auto-generator as 148.
    [ 1.669637] systemd[146]: Spawned /usr/lib/systemd/system-generators/systemd-fstab-generator as 149.
    [ 1.669689] systemd[146]: Spawned /usr/lib/systemd/system-generators/systemd-system-update-generator as 150.
    [ 1.669743] systemd[146]: Spawned /usr/lib/systemd/system-generators/lvm2-activation-generator as 151.
    [ 1.669826] systemd[146]: Spawned /usr/lib/systemd/system-generators/systemd-efi-boot-generator as 152.
    [ 1.669899] systemd[146]: Spawned /usr/lib/systemd/system-generators/systemd-debug-generator as 153.
    [ 1.669992] systemd[146]: Spawned /usr/lib/systemd/system-generators/systemd-cryptsetup-generator as 154.
    [ 1.671020] systemd[146]: /usr/lib/systemd/system-generators/systemd-getty-generator succeeded.
    [ 1.677317] systemd[146]: /usr/lib/systemd/system-generators/systemd-gpt-auto-generator succeeded.
    [ 1.678493] systemd[146]: /usr/lib/systemd/system-generators/systemd-fstab-generator succeeded.
    [ 1.678499] systemd[146]: /usr/lib/systemd/system-generators/systemd-system-update-generator succeeded.
    [ 1.689210] systemd[146]: /usr/lib/systemd/system-generators/lvm2-activation-generator succeeded.
    [ 1.689216] systemd[146]: /usr/lib/systemd/system-generators/systemd-efi-boot-generator succeeded.
    [ 1.689220] systemd[146]: /usr/lib/systemd/system-generators/systemd-debug-generator succeeded.
    [ 1.689223] systemd[146]: /usr/lib/systemd/system-generators/systemd-cryptsetup-generator succeeded.
    [ 1.689278] systemd[1]: /usr/lib/systemd/system-generators succeeded.
    [ 1.689509] systemd[1]: Looking for unit files in (higher priority first):
    [ 1.689512] systemd[1]: /etc/systemd/system
    [ 1.689513] systemd[1]: /run/systemd/system
    [ 1.689514] systemd[1]: /run/systemd/generator
    [ 1.689516] systemd[1]: /usr/local/lib/systemd/system
    [ 1.689517] systemd[1]: /usr/lib/systemd/system
    [ 1.689518] systemd[1]: /run/systemd/generator.late
    [ 1.689520] systemd[1]: SysV init scripts and rcN.d links support disabled
    [ 1.696010] systemd[1]: Failed to load configuration for auditd.service: No such file or directory
    [ 1.699470] systemd[1]: Failed to load configuration for plymouth-start.service: No such file or directory
    [ 1.704745] systemd[1]: Failed to load configuration for syslog.service: No such file or directory
    [ 1.711661] systemd[1]: Failed to load configuration for plymouth-quit.service: No such file or directory
    [ 1.712238] systemd[1]: Failed to load configuration for plymouth-quit-wait.service: No such file or directory
    [ 1.720811] systemd[1]: Using notification socket /run/systemd/notify
    [ 1.720824] systemd[1]: Successfully created private D-Bus server.
    [ 1.720829] systemd[1]: -.mount changed dead -> mounted
    [ 1.720856] systemd[1]: Activating default unit: default.target
    [ 1.720860] systemd[1]: Trying to enqueue job graphical.target/start/isolate
    [ 1.720991] systemd[1]: Looking at job [email protected]/stop conflicted_by=yes
    [ 1.720993] systemd[1]: Looking at job [email protected]/start conflicted_by=no
    [ 1.720996] systemd[1]: Fixing conflicting jobs [email protected]/stop,[email protected]/start by deleting job [email protected]/start
    [ 1.720998] systemd[1]: Looking at job gdm.service/start conflicted_by=no
    [ 1.721000] systemd[1]: Looking at job gdm.service/stop conflicted_by=no
    [ 1.721002] systemd[1]: Fixing conflicting jobs gdm.service/start,gdm.service/stop by deleting job gdm.service/stop
    [ 1.721036] systemd[1]: Installed new job graphical.target/start as 1
    [ 1.721044] systemd[1]: Installed new job multi-user.target/start as 2
    [ 1.721048] systemd[1]: Installed new job basic.target/start as 3
    [ 1.721052] systemd[1]: Installed new job sysinit.target/start as 4
    [ 1.721056] systemd[1]: Installed new job local-fs.target/start as 5
    [ 1.721059] systemd[1]: Installed new job boot.mount/start as 6
    [ 1.721063] systemd[1]: Installed new job system.slice/start as 8
    [ 1.721067] systemd[1]: Installed new job -.slice/start as 9
    [ 1.721070] systemd[1]: Installed new job dev-sda2.device/start as 10
    [ 1.721077] systemd[1]: Installed new job [email protected]/start as 11
    [ 1.721082] systemd[1]: Installed new job system-systemd\x2dfsck.slice/start as 12
    [ 1.721085] systemd[1]: Installed new job home.mount/start as 15
    [ 1.721089] systemd[1]: Installed new job dev-mapper-Linux\x2dHome.device/start as 16
    [ 1.721093] systemd[1]: Installed new job systemd-fsck@dev-mapper-Linux\x2dHome.service/start as 17
    [ 1.721097] systemd[1]: Installed new job systemd-fsck-root.service/start as 18
    [ 1.721100] systemd[1]: Installed new job tmp.mount/start as 19
    [ 1.721104] systemd[1]: Installed new job systemd-remount-fs.service/start as 20
    [ 1.721107] systemd[1]: Installed new job local-fs-pre.target/start as 21
    [ 1.721110] systemd[1]: Installed new job boot.automount/start as 22
    [ 1.721114] systemd[1]: Installed new job swap.target/start as 23
    [ 1.721117] systemd[1]: Installed new job dev-mapper-Linux\x2dSwap.swap/start as 24
    [ 1.721121] systemd[1]: Installed new job dev-mapper-Linux\x2dSwap.device/start as 25
    [ 1.721124] systemd[1]: Installed new job systemd-timesyncd.service/start as 26
    [ 1.721127] systemd[1]: Installed new job time-sync.target/start as 27
    [ 1.721131] systemd[1]: Installed new job ldconfig.service/start as 28
    [ 1.721134] systemd[1]: Installed new job sys-kernel-debug.mount/start as 29
    [ 1.721137] systemd[1]: Installed new job systemd-vconsole-setup.service/start as 30
    [ 1.721140] systemd[1]: Installed new job sys-kernel-config.mount/start as 31
    [ 1.721144] systemd[1]: Installed new job systemd-journal-flush.service/start as 32
    [ 1.721147] systemd[1]: Installed new job systemd-journald.service/start as 33
    [ 1.721150] systemd[1]: Installed new job systemd-journald.socket/start as 34
    [ 1.721154] systemd[1]: Installed new job systemd-journald-dev-log.socket/start as 35
    [ 1.721157] systemd[1]: Installed new job systemd-sysctl.service/start as 36
    [ 1.721160] systemd[1]: Installed new job systemd-firstboot.service/start as 37
    [ 1.721164] systemd[1]: Installed new job cryptsetup.target/start as 38
    [ 1.721167] systemd[1]: Installed new job lvm2-lvmetad.socket/start as 39
    [ 1.721170] systemd[1]: Installed new job kmod-static-nodes.service/start as 40
    [ 1.721173] systemd[1]: Installed new job systemd-binfmt.service/start as 41
    [ 1.721177] systemd[1]: Installed new job sys-fs-fuse-connections.mount/start as 42
    [ 1.721180] systemd[1]: Installed new job systemd-journal-catalog-update.service/start as 43
    [ 1.721184] systemd[1]: Installed new job systemd-udevd.service/start as 44
    [ 1.721187] systemd[1]: Installed new job systemd-udevd-control.socket/start as 45
    [ 1.721191] systemd[1]: Installed new job systemd-udevd-kernel.socket/start as 46
    [ 1.721194] systemd[1]: Installed new job systemd-ask-password-console.path/start as 47
    [ 1.721197] systemd[1]: Installed new job systemd-random-seed.service/start as 48
    [ 1.721200] systemd[1]: Installed new job dev-mqueue.mount/start as 49
    [ 1.721204] systemd[1]: Installed new job systemd-modules-load.service/start as 50
    [ 1.721207] systemd[1]: Installed new job proc-sys-fs-binfmt_misc.automount/start as 51
    [ 1.721211] systemd[1]: Installed new job systemd-tmpfiles-setup-dev.service/start as 52
    [ 1.721214] systemd[1]: Installed new job systemd-udev-trigger.service/start as 53
    [ 1.721217] systemd[1]: Installed new job systemd-tmpfiles-setup.service/start as 54
    [ 1.721220] systemd[1]: Installed new job systemd-update-utmp.service/start as 55
    [ 1.721224] systemd[1]: Installed new job dev-hugepages.mount/start as 56
    [ 1.721227] systemd[1]: Installed new job systemd-sysusers.service/start as 57
    [ 1.721230] systemd[1]: Installed new job systemd-udev-hwdb-update.service/start as 58
    [ 1.721233] systemd[1]: Installed new job systemd-update-done.service/start as 59
    [ 1.721237] systemd[1]: Installed new job sockets.target/start as 62
    [ 1.721240] systemd[1]: Installed new job acpid.socket/start as 63
    [ 1.721244] systemd[1]: Installed new job systemd-shutdownd.socket/start as 64
    [ 1.721247] systemd[1]: Installed new job dm-event.socket/start as 65
    [ 1.721250] systemd[1]: Installed new job systemd-initctl.socket/start as 66
    [ 1.721254] systemd[1]: Installed new job dbus.socket/start as 67
    [ 1.721257] systemd[1]: Installed new job timers.target/start as 68
    [ 1.721260] systemd[1]: Installed new job systemd-tmpfiles-clean.timer/start as 69
    [ 1.721263] systemd[1]: Installed new job paths.target/start as 70
    [ 1.721267] systemd[1]: Installed new job slices.target/start as 71
    [ 1.721270] systemd[1]: Installed new job acpid.service/start as 72
    [ 1.721272] systemd[1]: Installed new job systemd-udev-settle.service/start as 73
    [ 1.721276] systemd[1]: Installed new job remote-fs.target/start as 74
    [ 1.721279] systemd[1]: Installed new job NetworkManager.service/start as 75
    [ 1.721282] systemd[1]: Installed new job network.target/start as 76
    [ 1.721286] systemd[1]: Installed new job man-db.timer/start as 77
    [ 1.721289] systemd[1]: Installed new job dbus.service/start as 78
    [ 1.721292] systemd[1]: Installed new job getty.target/start as 79
    [ 1.721295] systemd[1]: Installed new job system-getty.slice/start as 81
    [ 1.721299] systemd[1]: Installed new job gdm.service

    So it times out (taking 3 minutes) then says
    [FAILED] Failed to start udev Wait for Complete Device Initialization.
    See "systemctl status systemd-udev-settle.service" for details
    [DEPEND] Dependency failed for ACPI event daemon
    so I ran
    systemctl status systemd-udev-settle
    with this output:
    ● systemd-udev-settle.service - udev Wait for Complete Device Initialization
    Loaded: loaded (/usr/lib/systemd/system/systemd-udev-settle.service; static)
    Active: active (exited) since Thu 2014-11-13 11:40:16 EST; 1min 24s ago
    Docs: man:udev(7)
    man:systemd-udevd.service(8)
    Process: 583 ExecStart=/usr/bin/udevadm settle (code=exited, status=0/SUCCESS)
    Main PID: 583 (code=exited, status=0/SUCCESS)
    CGroup: /system.slice/systemd-udev-settle.service
    Nov 13 11:40:14 arch-yogi systemd[1]: systemd-udev-settle.service changed failed -> start
    Nov 13 11:40:16 arch-yogi systemd[1]: Child 583 belongs to systemd-udev-settle.service
    Nov 13 11:40:16 arch-yogi systemd[1]: systemd-udev-settle.service: main process exited, code=exited, status=0/SUCCESS
    Nov 13 11:40:16 arch-yogi systemd[1]: systemd-udev-settle.service changed start -> exited
    Nov 13 11:40:16 arch-yogi systemd[1]: Job systemd-udev-settle.service/start finished, result=done
    Nov 13 11:40:16 arch-yogi systemd[1]: Started udev Wait for Complete Device Initialization.
    Nov 13 11:40:16 arch-yogi systemd[1]: systemd-udev-settle.service: cgroup is empty
    and after another
    systemd-analyze blame
    I get:
    2.358s systemd-udev-settle.service
    995ms lvm2-pvscan@8:8.service
    558ms rtkit-daemon.service
    488ms NetworkManager.service
    458ms udisks2.service
    341ms systemd-udev-trigger.service
    341ms systemd-binfmt.service
    319ms systemd-tmpfiles-setup-dev.service
    315ms systemd-random-seed.service
    301ms systemd-journald.service
    299ms proc-sys-fs-binfmt_misc.mount
    166ms systemd-udevd.service
    133ms [email protected]
    108ms systemd-journal-flush.service
    98ms systemd-logind.service
    90ms systemd-timesyncd.service
    80ms bluetooth.service
    65ms [email protected]
    47ms polkit.service
    37ms accounts-daemon.service
    28ms wpa_supplicant.service
    26ms systemd-sysctl.service
    25ms colord.service
    23ms systemd-fsck@dev-mapper-Linux\x2dHome.service
    23ms [email protected]
    22ms [email protected]
    21ms [email protected]
    19ms boot.mount
    18ms upower.service
    17ms avahi-daemon.service
    14ms systemd-remount-fs.service
    13ms gdm.service
    11ms tmp.mount
    11ms systemd-vconsole-setup.service
    10ms sys-kernel-debug.mount
    9ms dev-mapper-Linux\x2dSwap.swap
    8ms kmod-static-nodes.service
    6ms systemd-tmpfiles-setup.service
    5ms systemd-user-sessions.service
    5ms dev-mqueue.mount
    4ms systemd-update-utmp.service
    3ms home.mount
    3ms sys-kernel-config.mount
    3ms sys-fs-fuse-connections.mount
    3ms systemd-backlight@backlight:intel_backlight.service
    2ms dev-hugepages.mount
    systemd-analyze gets it right though:
    Startup finished in 2.538s (firmware) + 62ms (loader) + 2.238s (kernel) + 3min 3.161s (userspace) = 3min 8.001s
    What can I do?

  • Cannot login [get Darwin/BSD] after installing latest Security Update?!?

    "Software Update" prompted install of new Apple update - after restart, long startup wait & login at regular User screen then flashes to black "Darwin/BSD" page - then blue screen... I've run Disk Util [off Install CD], run repair & fix permissions [no change]. Performed suggested Single-User "fix" for possible corrupt NetInfo & still, no login available. Need help, other troubleshooting advice? Don't know if my next step is to re-install OS X? [am booting off an external FW drive that's brand new]

    When booted into Single User mode, did you type in reboot and exit, so
    the computer would know you wanted it to get out of Single User and to
    start up in the GUI of your OSX? It may need such a prompt even if you
    did not ask it to be in Single User in the first place.
    Did SafeBoot> repair disk permissions> restart, do anything different?
    The key may likely still be in the single user or fsck mode. Another user
    had a similar issue recently in one of these forum pages.
    Good luck & happy computing!

  • [solved] Systemd hangs sometimes on boot with linux-ck

    Hi i have linux-ck kernel installes and a Systemd-only init.
    Sometimes it hangs on boot and then, instead of starting X / LXDM, drops to a commandline login prompt. It does not happen on every boot and never happend with arch stock kernel so far. I cant't login to search in systemd journal for errors because the keyboard does not work corret, e.g. if I press "o" it writes a "6"
    here a shot from last time it happend. In the shot the last messages from Systemd are visible, but sometimes the screen is cleard before the login prompt appears.
    Last edited by SiD (2012-09-08 07:51:58)

    ok I activated syslog-ng and found this in the logs from last boot that not worked
    Xorg log
    # grep -e EE -e WW /var/log/Xorg.0.log.old
    [ 1.932] Current Operating System: Linux sunny 3.5.3-2-ck #1 SMP PREEMPT Mon Aug 27 15:48:39 EDT 2012 x86_64
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 1.942] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 1.944] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 1.944] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 1.948] (II) Loading extension MIT-SCREEN-SAVER
    [ 2.133] (EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module. Please see the
    [ 2.133] (EE) NVIDIA(0): system's kernel log for additional error messages and
    [ 2.133] (EE) NVIDIA(0): consult the NVIDIA README for details.
    [ 2.133] (EE) NVIDIA(0): *** Aborting ***
    [ 2.133] (EE) NVIDIA(0): Failing initialization of X screen 0
    [ 2.133] (EE) Screen(s) found, but none have a usable configuration.
    lxdm log
    # cat /var/log/lxdm.log.old
    ** Message: find greeter (nil)
    ** Message: find idle (nil)
    ** Message: add xserver watch
    X.Org X Server 1.12.4
    Release Date: 2012-08-27
    X Protocol Version 11, Revision 0
    Build Operating System: Linux 3.4.8-1-ARCH x86_64
    Current Operating System: Linux sunny 3.5.3-2-ck #1 SMP PREEMPT Mon Aug 27 15:48:39 EDT 2012 x86_64
    Kernel command line: root=UUID=3e32c396-fffb-4e00-b513-08db5c5da177 i915.i915_enable_rc6=1 ro initrd=../initramfs-linux-ck.img BOOT_IMAGE=../vmlinuz-linux-ck
    Build Date: 27 August 2012 08:04:39AM
    Current version of pixman: 0.26.2
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    (==) Log file: "/var/log/Xorg.0.log", Time: Mon Sep 3 18:45:01 2012
    (==) Using config directory: "/etc/X11/xorg.conf.d"
    NVIDIA: could not open the device file /dev/nvidiactl (No such device or address).
    Fatal server error:
    no screens found
    Please consult the The X.Org Foundation support
    at http://wiki.x.org
    for help.
    Please also check the log file at "/var/log/Xorg.0.log" for additional information.
    Server terminated with error (1). Closing log file.
    ** Message: exit cb
    ** Message: free session
    arc 1
    and in everything log
    Sep 3 18:45:03 localhost systemd[1]: Startup finished in 1s 157ms 589us (kernel) + 2s 645ms 840us (userspace) = 3s 803ms 429us.
    Sep 3 18:45:04 localhost dbus-daemon[317]: dbus[317]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
    Sep 3 18:45:04 localhost dbus[317]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
    Sep 3 18:45:04 localhost dbus[317]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details.
    Sep 3 18:45:04 localhost dbus-daemon[317]: dbus[317]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details.
    Sep 3 18:45:06 localhost systemd[1]: lxdm.service: main process exited, code=exited, status=1
    Sep 3 18:45:06 localhost systemd[1]: Unit lxdm.service entered failed state.
    Sep 3 18:45:06 localhost dbus-daemon[317]: dbus[317]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
    Sep 3 18:45:06 localhost dbus[317]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
    Sep 3 18:45:06 localhost dbus[317]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details.
    Sep 3 18:45:06 localhost dbus-daemon[317]: dbus[317]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details.
    Seems to me there is a problem loading the Nvidia driver.  Don't know if the dbus errors matter ...
    EDIT:
    Makes sence to me, without a graphics driver loaded X / LXDM can not start.
    Last edited by SiD (2012-09-03 17:12:23)

Maybe you are looking for

  • Flash just doesn't work right, period.

    Flash has multiple problems over ALL common browsers, including Chrome. Some browsers worse than others. Have the latest version. Videos stutter constantly. Videos just stop dead in their tracks. Restating gives me a few more minutes and then they ma

  • "Error: Windows 7 Build 7601 This copy of Windows is not genuine" keeps popping up

    hi,     we have recently been getting the windows not geuine message and our desktop has gone black,it says that we should activat windows but the avtivation code has worn off the sticker at the bottom of our g550.   hope you can help

  • OK, Apple Just Said it's done something to remedy SloMail...field reports?

    I just received this message, and have noticed some mail improvement in the last few days. I guess there's no way to know until the workweek kicks up. I am still very disappointed in Apple's response/communications re this problem. (yes, I may be con

  • Problem installing Sun Java Web Server

    Hi I'm trying to install Sun Identity Server which need Sun Java Web Server... I try to install identity server and web server using Sun Java Enterprise System Install Wizard... When I came to page Identity Server:Sun Java System Web Server (3 of 6 )

  • SB audigy 2 microphone problems when running fullscreened a

    Sounds odd, but here is the deal. Drivers works perfectly, nothing strange, thing is, im using Ventrilo(voice chat prog.) pretty much and here it comes: ?the other people cant hear me when im tabbed into a fullscreen game or any other fullscreen appl