Systemd broken

Hey I updated my arch install according to the systemd guide on the wiki but now systemd boots up normally, I can start to login (and probably would succeed were I fast enough) but then it reproducably shuts down again. This is a log of the last time I bothered trying to start this way. http://pastebin.com/AiTUnDjC
I already removed sysvinit and initscripts, so I doubt they are the culprit. More than happy to provide more info, but I don't know where to start to debug this. Any ideas?
Last edited by kaste (2013-04-18 06:01:13)

lumpl login[338]: FAILED LOGIN SESSION FROM pts/0 FOR (unknown), Error in service module   >>> thats weird
did you enable or disable any .service s since the upgrade?
btw: you could always chroot and do some maintenance

Similar Messages

  • Broken functionality after update (gnome, pam, glib2, systemd, etc.)

    I upgraded my system yesterday after going for a month or two without updates and a ton of authentication-related stuff broke. Here are some of the issues/symptoms I'm currently experiencing:
    Seeing this message in journalctl:
    May 22 13:13:50 deepspace1 slim[203]: pam_loginuid(slim:session): set_loginuid failed
    Pulseaudio is not started when logged into GNOME; aplay does not list any cards when invoked by my user:
    [mcmlxxxvi@deepspace1 ~]$ aplay -l
    aplay: device_list:268: no soundcards found...
    [mcmlxxxvi@deepspace1 ~]$ sudo aplay -l
    **** List of PLAYBACK Hardware Devices ****
    card 0: NVidia [HDA NVidia], device 0: ALC662 rev1 Analog [ALC662 rev1 Analog]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
    When I start pulseaudio manually, it only lists the dummy output.
    USB sticks no longer auto-mount
    I had been using GNOME 3 on forced fallback and logging in through SLiM.
    I tried to upgrade libreoffice, which made me upgrade glib2 (to 2.36.2-1), which caused some other problems (pnglib, etc.) so eventually I upgraded everything (including kernel, systemd, pam (to 1.1.6-3) and gnome (to 3.8)) without rebooting. A couple of hours later I was suddenly thrown out of my session and saw something about some journaling/logging utility being passed too large a block (cannot find it in the logs at the moment) on the console. I rebooted and after logging in, gnome-session-failed (the "Oh no" screen) was started. GNOME started successfully when I logged in as root.
    Googling around, some threads on here and based on the PAM message above, I tried to downgrade glib2 (to 2.36.1-3, 2.34.3-1, 2.34.2-2 and 2.32.4-1), to upgrade pam (to 1.1.6-4, which had appeared in the meantime) and then downgrade it (back to 1.1.6-3 and then to 1.1.6-1).
    glib2 downgrade led to nowhere - later versions led to gnome-session-failed, while with earlier ones GNOME would not start at all). Downgrading pam led me to a situation where I received a "Login incorrect" after entering the username (both console & SLiM) which I had to fix through init=/bin/bash .
    Following the advice here I cleared the hidden GNOME files and was finally able to log in (default mode, not fallback). Enabling fallback via gsettings (gsettings set org.gnome.desktop.session session-name gnome) brought back gnome-session-failed.
    So I'm led to believe that I originally had 2 problems: fallback mode, which I read had been disabled, and the authentication problem. I'm currently struggling with the latter and would like help on how to approach the situation.
    I'm not sure which logs would be needed for troubleshooting, and I'm still quite clumsy with journalctl, but will provide any logs requested.

    You should *never* do partial upgrades.  There is a reason why everywhere you see people saying that "partial upgrades are not supported". 
    I am not sure how you can be "clumsy with journalctl".  As far as its most basic functionality, it is pretty darn straight forward.  Though that is assuming you are willing to do a quick read of the man page... or even the output of "--help".

  • Systemd / Logind session broken?

    Hi,
    I am having problems with my standard desktop user. Several things don't work, I already posted the issue in the update-subforum. I think I might have narrowed down the issue some more and it does not seem to be update-related. Hence this new try to get help :-)
    I have been using systemd since Arch changed to it from initscripts. Since recently without problems. https://wiki.archlinux.org/index.php/Users_and_Groups/ says, that no groups are needed for the standard desktop user. But I can not mount usb storage, have no sound and no control over networkmanager. I can however start VirtualBox, although my user is not in the "vboxusers" group, my user is in "users" and "wheel" only. The page also mentions, that if things don't work, I should check https://wiki.archlinux.org/index.php/Ge … ermissions, which I did. The output of
    loginctl show-session $XDG_SESSION_ID
    ControlGroupHierarchy=/user
    ResetControllers=cpu
    NAutoVTs=6
    KillExcludeUsers=root
    KillUserProcesses=no
    IdleHint=yes
    IdleSinceHint=0
    IdleSinceHintMonotonic=0
    DelayInhibited=sleep
    InhibitDelayMaxUSec=5s
    HandlePowerKey=poweroff
    HandleSuspendKey=suspend
    HandleHibernateKey=hibernate
    HandleLidSwitch=suspend
    IdleAction=ignore
    IdleActionUSec=30min
    PreparingForShutdown=no
    PreparingForSleep=no
    There should be
    Remote=no
    and
    Active=yes
    , but there is not. If not, I should make sure that X runs on the same tty where the login occurred.
    /etc/X11/xinit/xserverrc
    is supposed to be my friend:
    #!/bin/sh
    if [ -z "$XDG_VTNR" ]; then
    exec /usr/bin/X -nolisten tcp "$@"
    else
    exec /usr/bin/X -nolisten tcp "$@" vt$XDG_VTNR
    fi
    I think my X session is on the same tty session as the login, since I log into KDE (not into ttyX and then start X).
    What to I do now? Is there anything wrong? Can you lead me into the right direction?

    Archcowboy wrote:I think my X session is on the same tty session as the login, since I log into KDE (not into ttyX and then start X).
    The problem might be in the display manager you use to login, which one are you using ?  (KDM, GDM, Slim, XDM, LXDM etc)
    Either way, i suggest you temporarily boot to multi-user.target by adding systemd.unit=multi-user.target to your boot kernel parameters.
    This will bring you to console without starting the DM or X /
    login to console as user, edit ~/.xinitrc to start kde and run startx .
    Once in X, run the loginctl show-session $XDG_SESSION_ID command again (post the output) and compare with the one you posted above.
    if $XDG_SESSION_ID is correct this way (and sound etc work) , the problem is very likely in the configuration of your DM.
    Edit :
    corrected typo's
    Last edited by Lone_Wolf (2013-08-15 13:20:51)

  • [Solved] Bumblebee broken after installing systemd

    Hi Arch Users!
    I recently wanted to give systemd a try and made the switch using the Arch's Wiki as a guide. Everything was fine except when I tried running VLC through Bumblebee.
    First error from optirun was that it could not connect to Bumblebee demaon. To which I did this:
    yaourt -R bumblebee
    yaourt -S bumblebee-systemd
    systemctl enable bumblebee.service
    After reboot the error was it could not load the GPU's drivers (I may be wording this wrong as I cant recall the exact phrasing). Since I recently updated the kernel, I thought it will be a good I idea to re-install Nvidia's drivers. So I did this
    yaourt -S nvidia-utils-bumblebee
    yaourt -S nvidia-bumblebee
    Now I get a new error and do not know how to proceed from here on. The error is:
    $ optirun -vvv vlc
    [ 73.424451] [DEBUG]Reading file: /etc/bumblebee/bumblebee.conf
    [ 73.570852] [DEBUG]optirun version 3.0.1 starting...
    [ 73.570904] [DEBUG]Active configuration:
    [ 73.570916] [DEBUG] bumblebeed config file: /etc/bumblebee/bumblebee.conf
    [ 73.570928] [DEBUG] X display: :8
    [ 73.570938] [DEBUG] LD_LIBRARY_PATH: /usr/lib/nvidia-bumblebee:/usr/lib32/nvidia-bumblebee
    [ 73.570950] [DEBUG] Socket path: /var/run/bumblebee.socket
    [ 73.570960] [DEBUG] VGL Compression: proxy
    [ 73.687431] [INFO]Response: No - error: [XORG] (EE) Failed to load module "mouse" (module does not exist, 0)
    [ 73.687481] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) Failed to load module "mouse" (module does not exist, 0)
    [ 73.687497] [DEBUG]Socket closed.
    [ 73.687530] [ERROR]Aborting because fallback start is disabled.
    [ 73.687543] [DEBUG]Killing all remaining processes.
    It may be purely coincidental that when I switched to sytemd that I see these errors and may well be the updated kernel. My observation is bumblebee was working yesterday and after I made a few system changes today (some that is irrelevant to this problem) bumblebee broke. The changes were
    1. Changed to systemd
    2. Changed to grub2
    3. Updated kernel.
    Any help are on this will very much be appreciated.
    Regards
    J
    Last edited by jlight2011 (2012-09-26 02:08:56)

    HI
    i have same error, To avoit them I removed /etc/X11/xorg.conf.d/20-intel.conf.
    this is my 20-intel.conf content
    Section "Device"
        Identifier  "Intel Graphics"
        Driver      "intel"
        Option      "AccelMethod"  "sna"
    EndSection
    I had used to enable sna instead of uxa, now I'm back to uxa but bumblebee work fine.

  • [Solved] systemd-hostnamed.service broken in systemd 212?

    Can someone confirm by checking
    hostnamectl status
    and
    systemctl --failed
    Thanks!
    Last edited by gedgon (2014-04-03 20:30:03)

    teateawhy wrote:Works for me.
    Hmm, interesting. In v.212 systemd-hostnamed.service failing for me, and hostnamectl timing out. Works fine after downgrading.
    Edit: Problem caused by wrong /var/tmp permission. Thanks, teateawhy.
    Last edited by gedgon (2014-04-03 20:29:47)

  • Creation of swap space broken with systemd

    Hi,
    after switching to systemd the automatic creation of my swap space is not working anymore. Configuration is as follows:
    cat /etc/fstab
    cat /etc/fstab
    # /etc/fstab: static file system information
    # <file system>                    <dir>        <type>    <options>            <dump>    <pass>
    devpts                        /dev/pts    devpts    defaults            0    0
    shm                                   /dev/shm    tmpfs    nodev,nosuid            0    0
    tmpfs                        /tmp        tmpfs    nodev,nosuid            0    0
    /dev/mapper/root                /        ext4    defaults            0    1
    UUID=9699832d-5522-4fd1-8a8d-4baf9ac8ca5f    /boot        ext4    defaults            0    1
    #/dev/mapper/swap                none        swap    defaults            0    0
    UUID=7fef77b7-2c8f-4dca-8246-cd873c47536    none        swap    defaults            0    0
    journalctl gives me:
    Sep 08 09:11:17 x200 systemd[1]: Job dev-disk-by\x2duuid-7fef77b7\x2d2c8f\x2d4dca\x2d8246\x2dcd873c47536.device/start timed out.
    Sep 08 09:11:17 x200 systemd[1]: Job dev-disk-by\x2duuid-7fef77b7\x2d2c8f\x2d4dca\x2d8246\x2dcd873c47536.swap/start failed with result 'dependency'.
    Sep 08 09:11:17 x200 systemd[1]: Job dev-disk-by\x2duuid-7fef77b7\x2d2c8f\x2d4dca\x2d8246\x2dcd873c47536.device/start failed with result 'timeout'.
    Any hints?
    Last edited by flix (2012-09-08 07:16:57)

    Its still not running. Here are some more details:
    /etc/fstab
    /dev/mapper/swap                none        swap    defaults            0    0
    /etc/crypttab
    swap        /dev/disk/by-uuid/833b82f9-d066-4b65-bb87-8dce9e3e54b1    /dev/urandom    swap
    mkswap -U 833b82f9-d066-4b65-bb87-8dce9e3e54b1 /dev/sda2
    Setting up swapspace version 1, size = 2000088 KiB
    no label, UUID=833b82f9-d066-4b65-bb87-8dce9e3e54b1
    swapon -a
    free -m
    -/+ buffers/cache:        690       3162
    Swap:         1953          0       1953
    lsblk -f
    NAME            FSTYPE      LABEL UUID                                 MOUNTPOINT
    sda                                                                   
    ├─sda1          ext4              9699832d-5522-4fd1-8a8d-4baf9ac8ca5f /boot
    ├─sda2          swap              833b82f9-d066-4b65-bb87-8dce9e3e54b1
    │ └─swap (dm-1) swap              cf2e8450-c336-4159-b639-287149f7437b [SWAP]
    └─sda3          crypto_LUKS       82783208-96fe-4f88-a373-021d1aea7238
      └─root (dm-0) ext4        root  a5557a2a-0987-4814-b73d-bbc01d354d5b /
    After reboot lsblk -f shows the following:
    NAME            FSTYPE      LABEL UUID                                 MOUNTPOINT
    sda                                                                   
    ├─sda1          ext4              9699832d-5522-4fd1-8a8d-4baf9ac8ca5f /boot
    ├─sda2                                                                 
    └─sda3          crypto_LUKS       82783208-96fe-4f88-a373-021d1aea7238
      └─root (dm-0) ext4        root  a5557a2a-0987-4814-b73d-bbc01d354d5b /

  • Change to systemd - aafm broken

    hey guys i've recently changed to systemd and now the aafm dont work anymore
    EXECUTE= adb shell ls --help
    Traceback (most recent call last):
    File "/usr/lib/python2.7/site-packages/aafm/aafm-gui.py", line 802, in <module>
    gui = Aafm_GUI()
    File "/usr/lib/python2.7/site-packages/aafm/aafm-gui.py", line 141, in __init__
    self.refresh_host_files()
    File "/usr/lib/python2.7/site-packages/aafm/aafm-gui.py", line 183, in refresh_host_files
    self.host_treeViewFile.load_data(self.dir_scan_host(self.host_cwd))
    File "/usr/lib/python2.7/site-packages/aafm/aafm-gui.py", line 248, in dir_scan_host
    'owner': self.get_owner(path),
    File "/usr/lib/python2.7/site-packages/aafm/aafm-gui.py", line 284, in _get_owner
    user = pwd.getpwuid(uid)[0]
    KeyError: 'getpwuid(): uid not found: 100'
    any tips?

    Try posting this error in the comments on the AUR page of the package, maybe its maintainer or some other user can help you.

  • Broken LVM setup due to recent systemd upgrade

    So yeah, a couple of days ago I let the system upgrade and rebooted. My setup is basically two identical HDDs in a RAID 0 array + LVM. After the recent upgrade, boot hangs somewhere in the reading of the init ramdisk and tells me that it cannot find my volume groups. Any clues as to what I could do to fix it?
    In the case that a fresh install is needed (which would quite annoy me) - any clues as to why the god-damned install media refuses to boot from a USB?

    I haven't tested it but people claim that adding lvmwait to your bootloader command line and modifying the lvm2 hook (/usr/lib/initcpio/hooks/lvm2) to this
    #!/usr/bin/ash
    run_hook() {
    local pvdev
    modprobe -q dm-mod >/dev/null 2>&1
    # If the lvmwait= parameter has been specified on the command line
    # wait for the device(s) before trying to activate the volume group(s)
    for pvdev in ${lvmwait//,/ }; do
    poll_device ${pvdev} ${rootdelay}
    done
    msg "Activating logical volumes..."
    lvm pvscan
    [ -d /etc/lvm ] && lvm vgscan
    if [ -n "$quiet" ]; then
    lvm vgchange --sysinit -a y >/dev/null
    else
    lvm vgchange --sysinit -a y
    fi
    Fixes the problem.
    I've found the fix in this thread : https://bbs.archlinux.org/viewtopic.php?id=145714
    It's not clear where the bug comes from, it's probably upstream but only Arch users have experienced it, so it seems that it was made apparent by the options used during compilation by Arch maintainers.
    Personally I prefer a downgrade to such a work around. I'm tired of new kernels breaking my system. I had major issues after the upgrades to 3.3 and 3.4, and now this.
    Last edited by anon1054572 (2012-09-07 09:22:19)

  • [SOLVED] systemd-tmpfiles-clean takes a very long time to run

    I've been having an issue for a while with systemd-tmpfiles-clean.service taking a very long time to run. I've tried to just ignore it, but it's really bothering me now.
    Measuring by running:
    # time systemd-tmpfiles --clean
    systemd-tmpfiles --clean 11.63s user 110.37s system 10% cpu 19:00.67 total
    I don't seem to have anything funky in any tmpfiles.d:
    # ls /usr/lib/tmpfiles.d/* /run/tmpfiles.d/* /etc/tmpfiles.d/* | pacman -Qo -
    ls: cannot access /etc/tmpfiles.d/*: No such file or directory
    error: No package owns /run/tmpfiles.d/kmod.conf
    /usr/lib/tmpfiles.d/gvfsd-fuse-tmpfiles.conf is owned by gvfs 1.20.1-2
    /usr/lib/tmpfiles.d/lastlog.conf is owned by shadow 4.1.5.1-9
    /usr/lib/tmpfiles.d/legacy.conf is owned by systemd 212-3
    /usr/lib/tmpfiles.d/libvirt.conf is owned by libvirt 1.2.4-1
    /usr/lib/tmpfiles.d/lighttpd.conf is owned by lighttpd 1.4.35-1
    /usr/lib/tmpfiles.d/lirc.conf is owned by lirc-utils 1:0.9.0-71
    /usr/lib/tmpfiles.d/mkinitcpio.conf is owned by mkinitcpio 17-1
    /usr/lib/tmpfiles.d/nscd.conf is owned by glibc 2.19-4
    /usr/lib/tmpfiles.d/postgresql.conf is owned by postgresql 9.3.4-1
    /usr/lib/tmpfiles.d/samba.conf is owned by samba 4.1.7-1
    /usr/lib/tmpfiles.d/slapd.conf is owned by openldap 2.4.39-1
    /usr/lib/tmpfiles.d/sudo.conf is owned by sudo 1.8.10.p2-1
    /usr/lib/tmpfiles.d/svnserve.conf is owned by subversion 1.8.8-1
    /usr/lib/tmpfiles.d/systemd.conf is owned by systemd 212-3
    /usr/lib/tmpfiles.d/systemd-nologin.conf is owned by systemd 212-3
    /usr/lib/tmpfiles.d/tmp.conf is owned by systemd 212-3
    /usr/lib/tmpfiles.d/uuidd.conf is owned by util-linux 2.24.1-6
    /usr/lib/tmpfiles.d/x11.conf is owned by systemd 212-3
    How do I debug why it is taking so long? I've looked in man 8 systemd-tmpfiles and on google, hoping to find some sort of --dubug option, but there seems to be none.
    Is it some how possible to get a list of the directories that it looks at when it runs?
    Anyone have any suggestions on how else to fix this.
    Anyone else have this issue?
    Thanks,
    Gary
    Last edited by garyvdm (2014-05-08 18:57:43)

    Thank you very much falconindy. SYSTEMD_LOG_LEVEL=debug helped my find my issue.
    The cause of the problem was thousands of directories in /var/tmp/ created by a test suite with a broken clean up method. systemd-tmpfiles-clean was recursing through these, but not deleting them.

  • Systemd-logind occasionally fails to start

    Hi,
    I am running Arch with Cinnamon started by mdm-display-manager. I had this running for quite some time without an issue.
    Recently an issue popped out - OCCASIONALLY systemd-logind fails to start and I get stuck on boot screen. This happens maybe once in 5-10 boots. I have to do hard reset afterwards. CTL+ALT+DEL won't work, I can not switch to other console and I have no network to SSH to that machine.
    Other than that, system starts just fine.
    I am not sure, how to debug this further and would appreciate advice.
    # journalctl --since=today --unit=systemd-logind
    May 26 09:42:34 phenom systemd[1]: Starting Login Service...
    May 26 09:42:59 phenom systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
    May 26 09:42:59 phenom systemd[1]: Failed to start Login Service.
    May 26 09:42:59 phenom systemd[1]: Unit systemd-logind.service entered failed state.
    May 26 09:42:59 phenom systemd[1]: systemd-logind.service failed.
    May 26 09:42:59 phenom systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
    # journalctl --since=today
    May 26 09:42:34 phenom systemd-journal[198]: Runtime journal is using 8.0M (max allowed 802.5M, trying to leave 1.1G free of 7.7G available → current limit 802.5M).
    May 26 09:42:34 phenom systemd-journal[198]: Permanent journal is using 2.0G (max allowed 4.0G, trying to leave 4.0G free of 36.6G available → current limit 4.0G).
    May 26 09:42:34 phenom systemd-journal[198]: Time spent on flushing to /var is 11.024ms for 2 entries.
    May 26 09:42:34 phenom kernel: Initializing cgroup subsys cpuset
    May 26 09:42:34 phenom kernel: Initializing cgroup subsys cpu
    May 26 09:42:34 phenom kernel: Initializing cgroup subsys cpuacct
    May 26 09:42:34 phenom kernel: Linux version 4.0.4-2-ARCH (builduser@foutrelis) (gcc version 5.1.0 (GCC) ) #1 SMP PREEMPT Fri May 22 03:05:23 UTC 2015
    May 26 09:42:34 phenom kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=d36ad497-1614-4cc5-8cc9-da2d5e5a417c rw
    May 26 09:42:34 phenom kernel: tseg: 00cff00000
    May 26 09:42:34 phenom kernel: e820: BIOS-provided physical RAM map:
    May 26 09:42:34 phenom kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000099fff] usable
    May 26 09:42:34 phenom kernel: BIOS-e820: [mem 0x000000000009f800-0x000000000009ffff] reserved
    May 26 09:42:34 phenom kernel: BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
    May 26 09:42:34 phenom kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000cfd9ffff] usable
    May 26 09:42:34 phenom kernel: BIOS-e820: [mem 0x00000000cfda0000-0x00000000cfdd0fff] ACPI NVS
    May 26 09:42:34 phenom kernel: BIOS-e820: [mem 0x00000000cfdd1000-0x00000000cfdfffff] ACPI data
    May 26 09:42:34 phenom kernel: BIOS-e820: [mem 0x00000000cfe00000-0x00000000cfefffff] reserved
    May 26 09:42:34 phenom kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
    May 26 09:42:34 phenom kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000ffffffff] reserved
    May 26 09:42:34 phenom kernel: BIOS-e820: [mem 0x0000000100000000-0x000000042fffffff] usable
    May 26 09:42:34 phenom kernel: NX (Execute Disable) protection: active
    May 26 09:42:34 phenom kernel: SMBIOS 2.4 present.
    May 26 09:42:34 phenom kernel: DMI: Gigabyte Technology Co., Ltd. GA-990XA-UD3/GA-990XA-UD3, BIOS F9 10/13/2011
    May 26 09:42:34 phenom kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
    May 26 09:42:34 phenom kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
    May 26 09:42:34 phenom kernel: AGP: No AGP bridge found
    May 26 09:42:34 phenom kernel: e820: last_pfn = 0x430000 max_arch_pfn = 0x400000000
    May 26 09:42:34 phenom kernel: MTRR default type: uncachable
    May 26 09:42:34 phenom kernel: MTRR fixed ranges enabled:
    May 26 09:42:34 phenom kernel: 00000-9FFFF write-back
    May 26 09:42:34 phenom kernel: A0000-BFFFF uncachable
    May 26 09:42:34 phenom kernel: C0000-C7FFF write-protect
    May 26 09:42:34 phenom kernel: C8000-FFFFF uncachable
    May 26 09:42:34 phenom kernel: MTRR variable ranges enabled:
    May 26 09:42:34 phenom kernel: 0 base 000000000000 mask FFFF80000000 write-back
    May 26 09:42:34 phenom kernel: 1 base 000080000000 mask FFFFC0000000 write-back
    May 26 09:42:34 phenom kernel: 2 base 0000C0000000 mask FFFFF0000000 write-back
    May 26 09:42:34 phenom kernel: 3 base 0000CFE00000 mask FFFFFFE00000 uncachable
    May 26 09:42:34 phenom kernel: 4 disabled
    May 26 09:42:34 phenom kernel: 5 disabled
    May 26 09:42:34 phenom kernel: 6 disabled
    May 26 09:42:34 phenom kernel: 7 disabled
    May 26 09:42:34 phenom kernel: TOM2: 0000000430000000 aka 17152M
    May 26 09:42:34 phenom kernel: PAT configuration [0-7]: WB WC UC- UC WB WC UC- UC
    May 26 09:42:34 phenom kernel: e820: update [mem 0xcfe00000-0xffffffff] usable ==> reserved
    May 26 09:42:34 phenom kernel: e820: last_pfn = 0xcfda0 max_arch_pfn = 0x400000000
    May 26 09:42:34 phenom kernel: found SMP MP-table at [mem 0x000f4b30-0x000f4b3f] mapped at [ffff8800000f4b30]
    May 26 09:42:34 phenom kernel: Scanning 1 areas for low memory corruption
    May 26 09:42:34 phenom kernel: Base memory trampoline at [ffff880000094000] 94000 size 24576
    May 26 09:42:34 phenom kernel: Using GB pages for direct mapping
    May 26 09:42:34 phenom kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
    May 26 09:42:34 phenom kernel: [mem 0x00000000-0x000fffff] page 4k
    May 26 09:42:34 phenom kernel: BRK [0x01b1d000, 0x01b1dfff] PGTABLE
    May 26 09:42:34 phenom kernel: BRK [0x01b1e000, 0x01b1efff] PGTABLE
    May 26 09:42:34 phenom kernel: BRK [0x01b1f000, 0x01b1ffff] PGTABLE
    May 26 09:42:34 phenom kernel: init_memory_mapping: [mem 0x42fe00000-0x42fffffff]
    May 26 09:42:34 phenom kernel: [mem 0x42fe00000-0x42fffffff] page 2M
    May 26 09:42:34 phenom kernel: BRK [0x01b20000, 0x01b20fff] PGTABLE
    May 26 09:42:34 phenom kernel: init_memory_mapping: [mem 0x420000000-0x42fdfffff]
    May 26 09:42:34 phenom kernel: [mem 0x420000000-0x42fdfffff] page 2M
    May 26 09:42:34 phenom kernel: init_memory_mapping: [mem 0x400000000-0x41fffffff]
    May 26 09:42:34 phenom kernel: [mem 0x400000000-0x41fffffff] page 2M
    May 26 09:42:34 phenom kernel: init_memory_mapping: [mem 0x00100000-0xcfd9ffff]
    May 26 09:42:34 phenom kernel: [mem 0x00100000-0x001fffff] page 4k
    May 26 09:42:34 phenom kernel: [mem 0x00200000-0x3fffffff] page 2M
    May 26 09:42:34 phenom kernel: [mem 0x40000000-0xbfffffff] page 1G
    May 26 09:42:34 phenom kernel: [mem 0xc0000000-0xcfbfffff] page 2M
    May 26 09:42:34 phenom kernel: [mem 0xcfc00000-0xcfd9ffff] page 4k
    May 26 09:42:34 phenom kernel: init_memory_mapping: [mem 0x100000000-0x3ffffffff]
    May 26 09:42:34 phenom kernel: [mem 0x100000000-0x3ffffffff] page 1G
    May 26 09:42:34 phenom kernel: RAMDISK: [mem 0x362ae000-0x3714efff]
    May 26 09:42:34 phenom kernel: ACPI: Early table checksum verification disabled
    May 26 09:42:34 phenom kernel: ACPI: RSDP 0x00000000000F6A50 000014 (v00 GBT )
    May 26 09:42:34 phenom kernel: ACPI: RSDT 0x00000000CFDD1000 000048 (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
    May 26 09:42:34 phenom kernel: ACPI: FACP 0x00000000CFDD1080 000074 (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
    May 26 09:42:34 phenom kernel: ACPI: DSDT 0x00000000CFDD1100 007A4B (v01 GBT GBTUACPI 00001000 MSFT 03000000)
    May 26 09:42:34 phenom kernel: ACPI: FACS 0x00000000CFDA0000 000040
    May 26 09:42:34 phenom kernel: ACPI: SSDT 0x00000000CFDD8C40 000EDC (v01 PTLTD POWERNOW 00000001 LTP 00000001)
    May 26 09:42:34 phenom kernel: ACPI: MSDM 0x00000000CFDD9B40 000055 (v03 GBT GBTUACPI 42302E31 GBTU 01010101)
    May 26 09:42:34 phenom kernel: ACPI: HPET 0x00000000CFDD9BC0 000038 (v01 GBT GBTUACPI 42302E31 GBTU 00000098)
    May 26 09:42:34 phenom kernel: ACPI: MCFG 0x00000000CFDD9C00 00003C (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
    May 26 09:42:34 phenom kernel: ACPI: MATS 0x00000000CFDD9C80 000034 (v01 GBT 00000000 00000000)
    May 26 09:42:34 phenom kernel: ACPI: TAMG 0x00000000CFDD9CF0 000202 (v01 GBT GBT B0 5455312E BG?? 53450101)
    May 26 09:42:34 phenom kernel: ACPI: APIC 0x00000000CFDD8B80 0000BC (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
    May 26 09:42:34 phenom kernel: ACPI: MATS 0x00000000CFDD9F00 006207 (v01 MATS RCM 80000001 INTL 20061109)
    May 26 09:42:34 phenom kernel: ACPI: Local APIC address 0xfee00000
    May 26 09:42:34 phenom kernel: Scanning NUMA topology in Northbridge 24
    May 26 09:42:34 phenom kernel: No NUMA configuration found
    May 26 09:42:34 phenom kernel: Faking a node at [mem 0x0000000000000000-0x000000042fffffff]
    May 26 09:42:34 phenom kernel: NODE_DATA(0) allocated [mem 0x42fffa000-0x42fffdfff]
    May 26 09:42:34 phenom kernel: [ffffea0000000000-ffffea0010bfffff] PMD -> [ffff88041f600000-ffff88042f5fffff] on node 0
    May 26 09:42:34 phenom kernel: Zone ranges:
    May 26 09:42:34 phenom kernel: DMA [mem 0x0000000000001000-0x0000000000ffffff]
    May 26 09:42:34 phenom kernel: DMA32 [mem 0x0000000001000000-0x00000000ffffffff]
    May 26 09:42:34 phenom kernel: Normal [mem 0x0000000100000000-0x000000042fffffff]
    May 26 09:42:34 phenom kernel: Movable zone start for each node
    May 26 09:42:34 phenom kernel: Early memory node ranges
    May 26 09:42:34 phenom kernel: node 0: [mem 0x0000000000001000-0x0000000000099fff]
    May 26 09:42:34 phenom kernel: node 0: [mem 0x0000000000100000-0x00000000cfd9ffff]
    May 26 09:42:34 phenom kernel: node 0: [mem 0x0000000100000000-0x000000042fffffff]
    May 26 09:42:34 phenom kernel: Initmem setup node 0 [mem 0x0000000000001000-0x000000042fffffff]
    May 26 09:42:34 phenom kernel: On node 0 totalpages: 4193593
    May 26 09:42:34 phenom kernel: DMA zone: 64 pages used for memmap
    May 26 09:42:34 phenom kernel: DMA zone: 21 pages reserved
    May 26 09:42:34 phenom kernel: DMA zone: 3993 pages, LIFO batch:0
    May 26 09:42:34 phenom kernel: DMA32 zone: 13239 pages used for memmap
    May 26 09:42:34 phenom kernel: DMA32 zone: 847264 pages, LIFO batch:31
    May 26 09:42:34 phenom kernel: Normal zone: 52224 pages used for memmap
    May 26 09:42:34 phenom kernel: Normal zone: 3342336 pages, LIFO batch:31
    May 26 09:42:34 phenom kernel: ACPI: PM-Timer IO Port: 0x808
    May 26 09:42:34 phenom kernel: ACPI: Local APIC address 0xfee00000
    May 26 09:42:34 phenom kernel: ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
    May 26 09:42:34 phenom kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
    May 26 09:42:34 phenom kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
    May 26 09:42:34 phenom kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
    May 26 09:42:34 phenom kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] enabled)
    May 26 09:42:34 phenom kernel: ACPI: LAPIC (acpi_id[0x05] lapic_id[0x05] enabled)
    May 26 09:42:34 phenom kernel: ACPI: LAPIC (acpi_id[0x06] lapic_id[0x06] disabled)
    May 26 09:42:34 phenom kernel: ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] disabled)
    May 26 09:42:34 phenom kernel: ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
    May 26 09:42:34 phenom kernel: ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
    May 26 09:42:34 phenom kernel: ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
    May 26 09:42:34 phenom kernel: ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1])
    May 26 09:42:34 phenom kernel: ACPI: LAPIC_NMI (acpi_id[0x04] dfl dfl lint[0x1])
    May 26 09:42:34 phenom kernel: ACPI: LAPIC_NMI (acpi_id[0x05] dfl dfl lint[0x1])
    May 26 09:42:34 phenom kernel: ACPI: LAPIC_NMI (acpi_id[0x06] dfl dfl lint[0x1])
    May 26 09:42:34 phenom kernel: ACPI: LAPIC_NMI (acpi_id[0x07] dfl dfl lint[0x1])
    May 26 09:42:34 phenom kernel: ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
    May 26 09:42:34 phenom kernel: IOAPIC[0]: apic_id 8, version 33, address 0xfec00000, GSI 0-23
    May 26 09:42:34 phenom kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    May 26 09:42:34 phenom kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
    May 26 09:42:34 phenom kernel: ACPI: IRQ0 used by override.
    May 26 09:42:34 phenom kernel: ACPI: IRQ9 used by override.
    May 26 09:42:34 phenom kernel: Using ACPI (MADT) for SMP configuration information
    May 26 09:42:34 phenom kernel: ACPI: HPET id: 0x10b9a201 base: 0xfed00000
    May 26 09:42:34 phenom kernel: smpboot: Allowing 8 CPUs, 2 hotplug CPUs
    May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
    May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0x0009a000-0x0009ffff]
    May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000effff]
    May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0x000f0000-0x000fffff]
    May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0xcfda0000-0xcfdd0fff]
    May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0xcfdd1000-0xcfdfffff]
    May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0xcfe00000-0xcfefffff]
    May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0xcff00000-0xdfffffff]
    May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0xe0000000-0xefffffff]
    May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0xf0000000-0xfebfffff]
    May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0xfec00000-0xffffffff]
    May 26 09:42:34 phenom kernel: e820: [mem 0xcff00000-0xdfffffff] available for PCI devices
    May 26 09:42:34 phenom kernel: Booting paravirtualized kernel on bare hardware
    May 26 09:42:34 phenom kernel: setup_percpu: NR_CPUS:128 nr_cpumask_bits:128 nr_cpu_ids:8 nr_node_ids:1
    May 26 09:42:34 phenom kernel: PERCPU: Embedded 31 pages/cpu @ffff88042fc00000 s86232 r8192 d32552 u262144
    May 26 09:42:34 phenom kernel: pcpu-alloc: s86232 r8192 d32552 u262144 alloc=1*2097152
    May 26 09:42:34 phenom kernel: pcpu-alloc: [0] 0 1 2 3 4 5 6 7
    May 26 09:42:34 phenom kernel: Built 1 zonelists in Node order, mobility grouping on. Total pages: 4128045
    May 26 09:42:34 phenom kernel: Policy zone: Normal
    May 26 09:42:34 phenom kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=d36ad497-1614-4cc5-8cc9-da2d5e5a417c rw
    May 26 09:42:34 phenom kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
    May 26 09:42:34 phenom kernel: AGP: Checking aperture...
    May 26 09:42:34 phenom kernel: AGP: No AGP bridge found
    May 26 09:42:34 phenom kernel: AGP: Node 0: aperture [bus addr 0xc4000000-0xc5ffffff] (32MB)
    May 26 09:42:34 phenom kernel: Aperture pointing to e820 RAM. Ignoring.
    May 26 09:42:34 phenom kernel: AGP: Your BIOS doesn't leave a aperture memory hole
    May 26 09:42:34 phenom kernel: AGP: Please enable the IOMMU option in the BIOS setup
    May 26 09:42:34 phenom kernel: AGP: This costs you 64MB of RAM
    May 26 09:42:34 phenom kernel: AGP: Mapping aperture over RAM [mem 0xc4000000-0xc7ffffff] (65536KB)
    May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0xc4000000-0xc7ffffff]
    May 26 09:42:34 phenom kernel: Memory: 16352908K/16774372K available (5628K kernel code, 840K rwdata, 1784K rodata, 1160K init, 1152K bss, 421464K reserved, 0K cma-reserved)
    May 26 09:42:34 phenom kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
    May 26 09:42:34 phenom kernel: Preemptible hierarchical RCU implementation.
    May 26 09:42:34 phenom kernel: RCU dyntick-idle grace-period acceleration is enabled.
    May 26 09:42:34 phenom kernel: RCU restricting CPUs from NR_CPUS=128 to nr_cpu_ids=8.
    May 26 09:42:34 phenom kernel: RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
    May 26 09:42:34 phenom kernel: NR_IRQS:8448 nr_irqs:488 16
    May 26 09:42:34 phenom kernel: spurious 8259A interrupt: IRQ7.
    May 26 09:42:34 phenom kernel: Console: colour dummy device 80x25
    May 26 09:42:34 phenom kernel: console [tty0] enabled
    May 26 09:42:34 phenom kernel: hpet clockevent registered
    May 26 09:42:34 phenom kernel: tsc: Fast TSC calibration using PIT
    May 26 09:42:34 phenom kernel: tsc: Detected 3300.124 MHz processor
    May 26 09:42:34 phenom kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 6602.25 BogoMIPS (lpj=11000413)
    May 26 09:42:34 phenom kernel: pid_max: default: 32768 minimum: 301
    May 26 09:42:34 phenom kernel: ACPI: Core revision 20150204
    May 26 09:42:34 phenom kernel: ACPI: All ACPI Tables successfully acquired
    May 26 09:42:34 phenom kernel: Security Framework initialized
    May 26 09:42:34 phenom kernel: Yama: becoming mindful.
    May 26 09:42:34 phenom kernel: Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes)
    May 26 09:42:34 phenom kernel: Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes)
    May 26 09:42:34 phenom kernel: Mount-cache hash table entries: 32768 (order: 6, 262144 bytes)
    May 26 09:42:34 phenom kernel: Mountpoint-cache hash table entries: 32768 (order: 6, 262144 bytes)
    May 26 09:42:34 phenom kernel: Initializing cgroup subsys blkio
    May 26 09:42:34 phenom kernel: Initializing cgroup subsys memory
    May 26 09:42:34 phenom kernel: Initializing cgroup subsys devices
    May 26 09:42:34 phenom kernel: Initializing cgroup subsys freezer
    May 26 09:42:34 phenom kernel: Initializing cgroup subsys net_cls
    May 26 09:42:34 phenom kernel: CPU: Physical Processor ID: 0
    May 26 09:42:34 phenom kernel: CPU: Processor Core ID: 0
    May 26 09:42:34 phenom kernel: mce: CPU supports 6 MCE banks
    May 26 09:42:34 phenom kernel: LVT offset 0 assigned for vector 0xf9
    May 26 09:42:34 phenom kernel: process: using AMD E400 aware idle routine
    May 26 09:42:34 phenom kernel: Last level iTLB entries: 4KB 512, 2MB 16, 4MB 8
    May 26 09:42:34 phenom kernel: Last level dTLB entries: 4KB 512, 2MB 128, 4MB 64, 1GB 0
    May 26 09:42:34 phenom kernel: Freeing SMP alternatives memory: 20K (ffffffff819f6000 - ffffffff819fb000)
    May 26 09:42:34 phenom kernel: ftrace: allocating 21316 entries in 84 pages
    May 26 09:42:34 phenom kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    May 26 09:42:34 phenom kernel: smpboot: CPU0: AMD Phenom(tm) II X6 1100T Processor (fam: 10, model: 0a, stepping: 00)
    May 26 09:42:34 phenom kernel: Performance Events: AMD PMU driver.
    May 26 09:42:34 phenom kernel: ... version: 0
    May 26 09:42:34 phenom kernel: ... bit width: 48
    May 26 09:42:34 phenom kernel: ... generic registers: 4
    May 26 09:42:34 phenom kernel: ... value mask: 0000ffffffffffff
    May 26 09:42:34 phenom kernel: ... max period: 00007fffffffffff
    May 26 09:42:34 phenom kernel: ... fixed-purpose events: 0
    May 26 09:42:34 phenom kernel: ... event mask: 000000000000000f
    May 26 09:42:34 phenom kernel: process: System has AMD C1E enabled
    May 26 09:42:34 phenom kernel: process: Switch to broadcast mode on CPU0
    May 26 09:42:34 phenom kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
    May 26 09:42:34 phenom kernel: x86: Booting SMP configuration:
    May 26 09:42:34 phenom kernel: .... node #0, CPUs: #1
    May 26 09:42:34 phenom kernel: process: Switch to broadcast mode on CPU1
    May 26 09:42:34 phenom kernel: #2
    May 26 09:42:34 phenom kernel: process: Switch to broadcast mode on CPU2
    May 26 09:42:34 phenom kernel: #3
    May 26 09:42:34 phenom kernel: process: Switch to broadcast mode on CPU3
    May 26 09:42:34 phenom kernel: #4
    May 26 09:42:34 phenom kernel: process: Switch to broadcast mode on CPU4
    May 26 09:42:34 phenom kernel: #5
    May 26 09:42:34 phenom kernel: x86: Booted up 1 node, 6 CPUs
    May 26 09:42:34 phenom kernel: smpboot: Total of 6 processors activated (39617.54 BogoMIPS)
    May 26 09:42:34 phenom kernel: process: Switch to broadcast mode on CPU5
    May 26 09:42:34 phenom kernel: devtmpfs: initialized
    May 26 09:42:34 phenom kernel: PM: Registering ACPI NVS region [mem 0xcfda0000-0xcfdd0fff] (200704 bytes)
    May 26 09:42:34 phenom kernel: pinctrl core: initialized pinctrl subsystem
    May 26 09:42:34 phenom kernel: RTC time: 7:42:28, date: 05/26/15
    May 26 09:42:34 phenom kernel: NET: Registered protocol family 16
    May 26 09:42:34 phenom kernel: cpuidle: using governor ladder
    May 26 09:42:34 phenom kernel: cpuidle: using governor menu
    May 26 09:42:34 phenom kernel: node 0 link 0: io port [9000, ffff]
    May 26 09:42:34 phenom kernel: TOM: 00000000d0000000 aka 3328M
    May 26 09:42:34 phenom kernel: Fam 10h mmconf [mem 0xe0000000-0xe00fffff]
    May 26 09:42:34 phenom kernel: node 0 link 0: mmio [a0000, bffff]
    May 26 09:42:34 phenom kernel: node 0 link 0: mmio [d0000000, dfffffff]
    May 26 09:42:34 phenom kernel: node 0 link 0: mmio [f0000000, ffffffff]
    May 26 09:42:34 phenom kernel: node 0 link 0: mmio [e0000000, e06fffff] ==> [e0100000, e06fffff]
    May 26 09:42:34 phenom kernel: TOM2: 0000000430000000 aka 17152M
    May 26 09:42:34 phenom kernel: bus: [bus 00-06] on node 0 link 0
    May 26 09:42:34 phenom kernel: bus: 00 [io 0x0000-0xffff]
    May 26 09:42:34 phenom kernel: bus: 00 [mem 0x000a0000-0x000bffff]
    May 26 09:42:34 phenom kernel: bus: 00 [mem 0xd0000000-0xdfffffff]
    May 26 09:42:34 phenom kernel: bus: 00 [mem 0xe0700000-0xffffffff]
    May 26 09:42:34 phenom kernel: bus: 00 [mem 0xe0100000-0xe06fffff]
    May 26 09:42:34 phenom kernel: bus: 00 [mem 0x430000000-0xfcffffffff]
    May 26 09:42:34 phenom kernel: ACPI: bus type PCI registered
    May 26 09:42:34 phenom kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
    May 26 09:42:34 phenom kernel: PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
    May 26 09:42:34 phenom kernel: PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820
    May 26 09:42:34 phenom kernel: PCI: Using configuration type 1 for base access
    May 26 09:42:34 phenom kernel: mtrr: your CPUs had inconsistent variable MTRR settings
    May 26 09:42:34 phenom kernel: mtrr: probably your BIOS does not setup all CPUs.
    May 26 09:42:34 phenom kernel: mtrr: corrected configuration.
    May 26 09:42:34 phenom kernel: ACPI: Added _OSI(Module Device)
    May 26 09:42:34 phenom kernel: ACPI: Added _OSI(Processor Device)
    May 26 09:42:34 phenom kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
    May 26 09:42:34 phenom kernel: ACPI: Added _OSI(Processor Aggregator Device)
    May 26 09:42:34 phenom kernel: ACPI: Actual Package length (1) is larger than NumElements field (0), truncated
    May 26 09:42:34 phenom kernel: ACPI: Actual Package length (1) is larger than NumElements field (0), truncated
    May 26 09:42:34 phenom kernel: ACPI: Actual Package length (1) is larger than NumElements field (0), truncated
    May 26 09:42:34 phenom kernel: ACPI: Actual Package length (1) is larger than NumElements field (0), truncated
    May 26 09:42:34 phenom kernel: ACPI: Interpreter enabled
    May 26 09:42:34 phenom kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20150204/hwxface-580)
    May 26 09:42:34 phenom kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20150204/hwxface-580)
    May 26 09:42:34 phenom kernel: ACPI: (supports S0 S3 S4 S5)
    May 26 09:42:34 phenom kernel: ACPI: Using IOAPIC for interrupt routing
    May 26 09:42:34 phenom kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
    May 26 09:42:34 phenom kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
    May 26 09:42:34 phenom kernel: acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
    May 26 09:42:34 phenom kernel: acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
    May 26 09:42:34 phenom kernel: PCI host bridge to bus 0000:00
    May 26 09:42:34 phenom kernel: pci_bus 0000:00: root bus resource [bus 00-ff]
    May 26 09:42:34 phenom kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7 window]
    May 26 09:42:34 phenom kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window]
    May 26 09:42:34 phenom kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
    May 26 09:42:34 phenom kernel: pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000dffff window]
    May 26 09:42:34 phenom kernel: pci_bus 0000:00: root bus resource [mem 0xfed40000-0xfed44fff window]
    May 26 09:42:34 phenom kernel: pci_bus 0000:00: root bus resource [mem 0xd0000000-0xfebfffff window]
    May 26 09:42:34 phenom kernel: pci 0000:00:00.0: [1002:5a14] type 00 class 0x060000
    May 26 09:42:34 phenom kernel: pci 0000:00:00.0: [Firmware Bug]: reg 0x1c: invalid BAR (can't size)
    May 26 09:42:34 phenom kernel: pci 0000:00:02.0: [1002:5a16] type 01 class 0x060400
    May 26 09:42:34 phenom kernel: pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
    May 26 09:42:34 phenom kernel: pci 0000:00:02.0: System wakeup disabled by ACPI
    May 26 09:42:34 phenom kernel: pci 0000:00:04.0: [1002:5a18] type 01 class 0x060400
    May 26 09:42:34 phenom kernel: pci 0000:00:04.0: PME# supported from D0 D3hot D3cold
    May 26 09:42:34 phenom kernel: pci 0000:00:04.0: System wakeup disabled by ACPI
    May 26 09:42:34 phenom kernel: pci 0000:00:09.0: [1002:5a1c] type 01 class 0x060400
    May 26 09:42:34 phenom kernel: pci 0000:00:09.0: PME# supported from D0 D3hot D3cold
    May 26 09:42:34 phenom kernel: pci 0000:00:09.0: System wakeup disabled by ACPI
    May 26 09:42:34 phenom kernel: pci 0000:00:0a.0: [1002:5a1d] type 01 class 0x060400
    May 26 09:42:34 phenom kernel: pci 0000:00:0a.0: PME# supported from D0 D3hot D3cold
    May 26 09:42:34 phenom kernel: pci 0000:00:0a.0: System wakeup disabled by ACPI
    May 26 09:42:34 phenom kernel: pci 0000:00:11.0: [1002:4391] type 00 class 0x010601
    May 26 09:42:34 phenom kernel: pci 0000:00:11.0: reg 0x10: [io 0xff00-0xff07]
    May 26 09:42:34 phenom kernel: pci 0000:00:11.0: reg 0x14: [io 0xfe00-0xfe03]
    May 26 09:42:34 phenom kernel: pci 0000:00:11.0: reg 0x18: [io 0xfd00-0xfd07]
    May 26 09:42:34 phenom kernel: pci 0000:00:11.0: reg 0x1c: [io 0xfc00-0xfc03]
    May 26 09:42:34 phenom kernel: pci 0000:00:11.0: reg 0x20: [io 0xfb00-0xfb0f]
    May 26 09:42:34 phenom kernel: pci 0000:00:11.0: reg 0x24: [mem 0xfdfff000-0xfdfff3ff]
    May 26 09:42:34 phenom kernel: pci 0000:00:12.0: [1002:4397] type 00 class 0x0c0310
    May 26 09:42:34 phenom kernel: pci 0000:00:12.0: reg 0x10: [mem 0xfdffe000-0xfdffefff]
    May 26 09:42:34 phenom kernel: pci 0000:00:12.0: System wakeup disabled by ACPI
    May 26 09:42:34 phenom kernel: pci 0000:00:12.2: [1002:4396] type 00 class 0x0c0320
    May 26 09:42:34 phenom kernel: pci 0000:00:12.2: reg 0x10: [mem 0xfdffd000-0xfdffd0ff]
    May 26 09:42:34 phenom kernel: pci 0000:00:12.2: supports D1 D2
    May 26 09:42:34 phenom kernel: pci 0000:00:12.2: PME# supported from D0 D1 D2 D3hot
    May 26 09:42:34 phenom kernel: pci 0000:00:12.2: System wakeup disabled by ACPI
    May 26 09:42:34 phenom kernel: pci 0000:00:13.0: [1002:4397] type 00 class 0x0c0310
    May 26 09:42:34 phenom kernel: pci 0000:00:13.0: reg 0x10: [mem 0xfdffc000-0xfdffcfff]
    May 26 09:42:34 phenom kernel: pci 0000:00:13.0: System wakeup disabled by ACPI
    May 26 09:42:34 phenom kernel: pci 0000:00:13.2: [1002:4396] type 00 class 0x0c0320
    May 26 09:42:34 phenom kernel: pci 0000:00:13.2: reg 0x10: [mem 0xfdffb000-0xfdffb0ff]
    May 26 09:42:34 phenom kernel: pci 0000:00:13.2: supports D1 D2
    May 26 09:42:34 phenom kernel: pci 0000:00:13.2: PME# supported from D0 D1 D2 D3hot
    May 26 09:42:34 phenom kernel: pci 0000:00:13.2: System wakeup disabled by ACPI
    May 26 09:42:34 phenom kernel: pci 0000:00:14.0: [1002:4385] type 00 class 0x0c0500
    May 26 09:42:34 phenom kernel: pci 0000:00:14.1: [1002:439c] type 00 class 0x01018a
    May 26 09:42:34 phenom kernel: pci 0000:00:14.1: reg 0x10: [io 0x0000-0x0007]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.1: reg 0x14: [io 0x0000-0x0003]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.1: reg 0x18: [io 0x0000-0x0007]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.1: reg 0x1c: [io 0x0000-0x0003]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.1: reg 0x20: [io 0xfa00-0xfa0f]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.1: legacy IDE quirk: reg 0x10: [io 0x01f0-0x01f7]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.1: legacy IDE quirk: reg 0x14: [io 0x03f6]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.1: legacy IDE quirk: reg 0x18: [io 0x0170-0x0177]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.1: legacy IDE quirk: reg 0x1c: [io 0x0376]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.2: [1002:4383] type 00 class 0x040300
    May 26 09:42:34 phenom kernel: pci 0000:00:14.2: reg 0x10: [mem 0xfdff4000-0xfdff7fff 64bit]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.2: PME# supported from D0 D3hot D3cold
    May 26 09:42:34 phenom kernel: pci 0000:00:14.2: System wakeup disabled by ACPI
    May 26 09:42:34 phenom kernel: pci 0000:00:14.3: [1002:439d] type 00 class 0x060100
    May 26 09:42:34 phenom kernel: pci 0000:00:14.4: [1002:4384] type 01 class 0x060401
    May 26 09:42:34 phenom kernel: pci 0000:00:14.4: System wakeup disabled by ACPI
    May 26 09:42:34 phenom kernel: pci 0000:00:14.5: [1002:4399] type 00 class 0x0c0310
    May 26 09:42:34 phenom kernel: pci 0000:00:14.5: reg 0x10: [mem 0xfdffa000-0xfdffafff]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.5: System wakeup disabled by ACPI
    May 26 09:42:34 phenom kernel: pci 0000:00:15.0: [1002:43a0] type 01 class 0x060400
    May 26 09:42:34 phenom kernel: pci 0000:00:15.0: supports D1 D2
    May 26 09:42:34 phenom kernel: pci 0000:00:15.0: System wakeup disabled by ACPI
    May 26 09:42:34 phenom kernel: pci 0000:00:16.0: [1002:4397] type 00 class 0x0c0310
    May 26 09:42:34 phenom kernel: pci 0000:00:16.0: reg 0x10: [mem 0xfdff9000-0xfdff9fff]
    May 26 09:42:34 phenom kernel: pci 0000:00:16.0: System wakeup disabled by ACPI
    May 26 09:42:34 phenom kernel: pci 0000:00:16.2: [1002:4396] type 00 class 0x0c0320
    May 26 09:42:34 phenom kernel: pci 0000:00:16.2: reg 0x10: [mem 0xfdff8000-0xfdff80ff]
    May 26 09:42:34 phenom kernel: pci 0000:00:16.2: supports D1 D2
    May 26 09:42:34 phenom kernel: pci 0000:00:16.2: PME# supported from D0 D1 D2 D3hot
    May 26 09:42:34 phenom kernel: pci 0000:00:16.2: System wakeup disabled by ACPI
    May 26 09:42:34 phenom kernel: pci 0000:00:18.0: [1022:1200] type 00 class 0x060000
    May 26 09:42:34 phenom kernel: pci 0000:00:18.1: [1022:1201] type 00 class 0x060000
    May 26 09:42:34 phenom kernel: pci 0000:00:18.2: [1022:1202] type 00 class 0x060000
    May 26 09:42:34 phenom kernel: pci 0000:00:18.3: [1022:1203] type 00 class 0x060000
    May 26 09:42:34 phenom kernel: pci 0000:00:18.4: [1022:1204] type 00 class 0x060000
    May 26 09:42:34 phenom kernel: pci 0000:01:00.0: [1002:6779] type 00 class 0x030000
    May 26 09:42:34 phenom kernel: pci 0000:01:00.0: reg 0x10: [mem 0xd0000000-0xdfffffff 64bit pref]
    May 26 09:42:34 phenom kernel: pci 0000:01:00.0: reg 0x18: [mem 0xfd5c0000-0xfd5dffff 64bit]
    May 26 09:42:34 phenom kernel: pci 0000:01:00.0: reg 0x20: [io 0xce00-0xceff]
    May 26 09:42:34 phenom kernel: pci 0000:01:00.0: reg 0x30: [mem 0x00000000-0x0001ffff pref]
    May 26 09:42:34 phenom kernel: pci 0000:01:00.0: supports D1 D2
    May 26 09:42:34 phenom kernel: pci 0000:01:00.1: [1002:aa98] type 00 class 0x040300
    May 26 09:42:34 phenom kernel: pci 0000:01:00.1: reg 0x10: [mem 0xfd5fc000-0xfd5fffff 64bit]
    May 26 09:42:34 phenom kernel: pci 0000:01:00.1: supports D1 D2
    May 26 09:42:34 phenom kernel: pci 0000:00:02.0: PCI bridge to [bus 01]
    May 26 09:42:34 phenom kernel: pci 0000:00:02.0: bridge window [io 0xc000-0xcfff]
    May 26 09:42:34 phenom kernel: pci 0000:00:02.0: bridge window [mem 0xfd500000-0xfd5fffff]
    May 26 09:42:34 phenom kernel: pci 0000:00:02.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
    May 26 09:42:34 phenom kernel: pci 0000:02:00.0: [1b6f:7023] type 00 class 0x0c0330
    May 26 09:42:34 phenom kernel: pci 0000:02:00.0: reg 0x10: [mem 0xfd4f8000-0xfd4fffff 64bit]
    May 26 09:42:34 phenom kernel: pci 0000:02:00.0: supports D1 D2
    May 26 09:42:34 phenom kernel: pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
    May 26 09:42:34 phenom kernel: pci 0000:00:04.0: PCI bridge to [bus 02]
    May 26 09:42:34 phenom kernel: pci 0000:00:04.0: bridge window [io 0xb000-0xbfff]
    May 26 09:42:34 phenom kernel: pci 0000:00:04.0: bridge window [mem 0xfd400000-0xfd4fffff]
    May 26 09:42:34 phenom kernel: pci 0000:00:04.0: bridge window [mem 0xfde00000-0xfdefffff 64bit pref]
    May 26 09:42:34 phenom kernel: pci 0000:03:00.0: [10ec:8168] type 00 class 0x020000
    May 26 09:42:34 phenom kernel: pci 0000:03:00.0: reg 0x10: [io 0xee00-0xeeff]
    May 26 09:42:34 phenom kernel: pci 0000:03:00.0: reg 0x18: [mem 0xfdcff000-0xfdcfffff 64bit pref]
    May 26 09:42:34 phenom kernel: pci 0000:03:00.0: reg 0x20: [mem 0xfdcf8000-0xfdcfbfff 64bit pref]
    May 26 09:42:34 phenom kernel: pci 0000:03:00.0: supports D1 D2
    May 26 09:42:34 phenom kernel: pci 0000:03:00.0: PME# supported from D0 D1 D2 D3hot D3cold
    May 26 09:42:34 phenom kernel: pci 0000:00:09.0: PCI bridge to [bus 03]
    May 26 09:42:34 phenom kernel: pci 0000:00:09.0: bridge window [io 0xe000-0xefff]
    May 26 09:42:34 phenom kernel: pci 0000:00:09.0: bridge window [mem 0xfdd00000-0xfddfffff]
    May 26 09:42:34 phenom kernel: pci 0000:00:09.0: bridge window [mem 0xfdc00000-0xfdcfffff 64bit pref]
    May 26 09:42:34 phenom kernel: pci 0000:04:00.0: [1b6f:7023] type 00 class 0x0c0330
    May 26 09:42:34 phenom kernel: pci 0000:04:00.0: reg 0x10: [mem 0xfdbf8000-0xfdbfffff 64bit]
    May 26 09:42:34 phenom kernel: pci 0000:04:00.0: supports D1 D2
    May 26 09:42:34 phenom kernel: pci 0000:04:00.0: PME# supported from D0 D1 D2 D3hot D3cold
    May 26 09:42:34 phenom kernel: pci 0000:00:0a.0: PCI bridge to [bus 04]
    May 26 09:42:34 phenom kernel: pci 0000:00:0a.0: bridge window [io 0xd000-0xdfff]
    May 26 09:42:34 phenom kernel: pci 0000:00:0a.0: bridge window [mem 0xfdb00000-0xfdbfffff]
    May 26 09:42:34 phenom kernel: pci 0000:00:0a.0: bridge window [mem 0xfd800000-0xfd8fffff 64bit pref]
    May 26 09:42:34 phenom kernel: pci 0000:05:0e.0: [1106:3044] type 00 class 0x0c0010
    May 26 09:42:34 phenom kernel: pci 0000:05:0e.0: reg 0x10: [mem 0xfdaff000-0xfdaff7ff]
    May 26 09:42:34 phenom kernel: pci 0000:05:0e.0: reg 0x14: [io 0xaf00-0xaf7f]
    May 26 09:42:34 phenom kernel: pci 0000:05:0e.0: supports D2
    May 26 09:42:34 phenom kernel: pci 0000:05:0e.0: PME# supported from D2 D3hot D3cold
    May 26 09:42:34 phenom kernel: pci 0000:00:14.4: PCI bridge to [bus 05] (subtractive decode)
    May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [io 0xa000-0xafff]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [mem 0xfda00000-0xfdafffff]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [mem 0xfd900000-0xfd9fffff pref]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [io 0x0000-0x0cf7 window] (subtractive decode)
    May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [io 0x0d00-0xffff window] (subtractive decode)
    May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [mem 0x000a0000-0x000bffff window] (subtractive decode)
    May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [mem 0x000c0000-0x000dffff window] (subtractive decode)
    May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [mem 0xfed40000-0xfed44fff window] (subtractive decode)
    May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [mem 0xd0000000-0xfebfffff window] (subtractive decode)
    May 26 09:42:34 phenom kernel: pci 0000:00:15.0: PCI bridge to [bus 06]
    May 26 09:42:34 phenom kernel: pci 0000:00:15.0: bridge window [io 0x9000-0x9fff]
    May 26 09:42:34 phenom kernel: pci 0000:00:15.0: bridge window [mem 0xfd700000-0xfd7fffff]
    May 26 09:42:34 phenom kernel: pci 0000:00:15.0: bridge window [mem 0xfd600000-0xfd6fffff 64bit pref]
    May 26 09:42:34 phenom kernel: pci_bus 0000:00: on NUMA node 0
    May 26 09:42:34 phenom kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 11) *0
    May 26 09:42:34 phenom kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 11) *0
    May 26 09:42:34 phenom kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 11) *0
    May 26 09:42:34 phenom kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 11) *0
    May 26 09:42:34 phenom kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11) *0
    May 26 09:42:34 phenom kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11) *0
    May 26 09:42:34 phenom kernel: ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 5 6 7 10 11) *0
    May 26 09:42:34 phenom kernel: ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 10 11) *0
    May 26 09:42:34 phenom kernel: vgaarb: setting as boot device: PCI:0000:01:00.0
    May 26 09:42:34 phenom kernel: vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
    May 26 09:42:34 phenom kernel: vgaarb: loaded
    May 26 09:42:34 phenom kernel: vgaarb: bridge control possible 0000:01:00.0
    May 26 09:42:34 phenom kernel: PCI: Using ACPI for IRQ routing
    May 26 09:42:34 phenom kernel: PCI: pci_cache_line_size set to 64 bytes
    May 26 09:42:34 phenom kernel: e820: reserve RAM buffer [mem 0x0009a000-0x0009ffff]
    May 26 09:42:34 phenom kernel: e820: reserve RAM buffer [mem 0xcfda0000-0xcfffffff]
    May 26 09:42:34 phenom kernel: NetLabel: Initializing
    May 26 09:42:34 phenom kernel: NetLabel: domain hash size = 128
    May 26 09:42:34 phenom kernel: NetLabel: protocols = UNLABELED CIPSOv4
    May 26 09:42:34 phenom kernel: NetLabel: unlabeled traffic allowed by default
    May 26 09:42:34 phenom kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
    May 26 09:42:34 phenom kernel: hpet0: 3 comparators, 32-bit 14.318180 MHz counter
    May 26 09:42:34 phenom kernel: Switched to clocksource hpet
    May 26 09:42:34 phenom kernel: pnp: PnP ACPI init
    May 26 09:42:34 phenom kernel: system 00:00: [io 0x04d0-0x04d1] has been reserved
    May 26 09:42:34 phenom kernel: system 00:00: [io 0x0220-0x0225] has been reserved
    May 26 09:42:34 phenom kernel: system 00:00: [io 0x0290-0x0294] has been reserved
    May 26 09:42:34 phenom kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
    May 26 09:42:34 phenom kernel: pnp 00:01: disabling [mem 0x00000000-0x00000fff window] because it overlaps 0000:01:00.0 BAR 6 [mem 0x00000000-0x0001ffff pref]
    May 26 09:42:34 phenom kernel: system 00:01: [io 0x0900-0x091f] has been reserved
    May 26 09:42:34 phenom kernel: system 00:01: [io 0x0228-0x022f] has been reserved
    May 26 09:42:34 phenom kernel: system 00:01: [io 0x040b] has been reserved
    May 26 09:42:34 phenom kernel: system 00:01: [io 0x04d6] has been reserved
    May 26 09:42:34 phenom kernel: system 00:01: [io 0x0c00-0x0c01] has been reserved
    May 26 09:42:34 phenom kernel: system 00:01: [io 0x0c14] has been reserved
    May 26 09:42:34 phenom kernel: system 00:01: [io 0x0c50-0x0c52] has been reserved
    May 26 09:42:34 phenom kernel: system 00:01: [io 0x0c6c-0x0c6d] has been reserved
    May 26 09:42:34 phenom kernel: system 00:01: [io 0x0c6f] has been reserved
    May 26 09:42:34 phenom kernel: system 00:01: [io 0x0cd0-0x0cd1] has been reserved
    May 26 09:42:34 phenom kernel: system 00:01: [io 0x0cd2-0x0cd3] has been reserved
    May 26 09:42:34 phenom kernel: system 00:01: [io 0x0cd4-0x0cdf] has been reserved
    May 26 09:42:34 phenom kernel: system 00:01: [io 0x0800-0x08fe] could not be reserved
    May 26 09:42:34 phenom kernel: system 00:01: [io 0x0a10-0x0a17] has been reserved
    May 26 09:42:34 phenom kernel: system 00:01: [io 0x0b00-0x0b0f] has been reserved
    May 26 09:42:34 phenom kernel: system 00:01: [io 0x0b10-0x0b1f] has been reserved
    May 26 09:42:34 phenom kernel: system 00:01: [io 0x0b20-0x0b3f] has been reserved
    May 26 09:42:34 phenom kernel: system 00:01: [mem 0xfee00400-0xfee00fff window] has been reserved
    May 26 09:42:34 phenom kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
    May 26 09:42:34 phenom kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
    May 26 09:42:34 phenom kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0501 (active)
    May 26 09:42:34 phenom kernel: system 00:04: [mem 0xe0000000-0xefffffff] has been reserved
    May 26 09:42:34 phenom kernel: system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
    May 26 09:42:34 phenom kernel: system 00:05: [mem 0x000d4200-0x000d7fff] has been reserved
    May 26 09:42:34 phenom kernel: system 00:05: [mem 0x000f0000-0x000f7fff] could not be reserved
    May 26 09:42:34 phenom kernel: system 00:05: [mem 0x000f8000-0x000fbfff] could not be reserved
    May 26 09:42:34 phenom kernel: system 00:05: [mem 0x000fc000-0x000fffff] could not be reserved
    May 26 09:42:34 phenom kernel: system 00:05: [mem 0xcfda0000-0xcfdfffff] could not be reserved
    May 26 09:42:34 phenom kernel: system 00:05: [mem 0xffff0000-0xffffffff] has been reserved
    May 26 09:42:34 phenom kernel: system 00:05: [mem 0x00000000-0x0009ffff] could not be reserved
    May 26 09:42:34 phenom kernel: system 00:05: [mem 0x00100000-0xcfd9ffff] could not be reserved
    May 26 09:42:34 phenom kernel: system 00:05: [mem 0xcfe00000-0xcfefffff] has been reserved
    May 26 09:42:34 phenom kernel: system 00:05: [mem 0xcff00000-0xcfffffff] could not be reserved
    May 26 09:42:34 phenom kernel: system 00:05: [mem 0xfec00000-0xfec00fff] could not be reserved
    May 26 09:42:34 phenom kernel: system 00:05: [mem 0xfee00000-0xfee00fff] could not be reserved
    May 26 09:42:34 phenom kernel: system 00:05: [mem 0xfff80000-0xfffeffff] has been reserved
    May 26 09:42:34 phenom kernel: system 00:05: Plug and Play ACPI device, IDs PNP0c01 (active)
    May 26 09:42:34 phenom kernel: pnp: PnP ACPI: found 6 devices
    May 26 09:42:34 phenom kernel: pci 0000:01:00.0: BAR 6: assigned [mem 0xfd500000-0xfd51ffff pref]
    May 26 09:42:34 phenom kernel: pci 0000:00:02.0: PCI bridge to [bus 01]
    May 26 09:42:34 phenom kernel: pci 0000:00:02.0: bridge window [io 0xc000-0xcfff]
    May 26 09:42:34 phenom kernel: pci 0000:00:02.0: bridge window [mem 0xfd500000-0xfd5fffff]
    May 26 09:42:34 phenom kernel: pci 0000:00:02.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
    May 26 09:42:34 phenom kernel: pci 0000:00:04.0: PCI bridge to [bus 02]
    May 26 09:42:34 phenom kernel: pci 0000:00:04.0: bridge window [io 0xb000-0xbfff]
    May 26 09:42:34 phenom kernel: pci 0000:00:04.0: bridge window [mem 0xfd400000-0xfd4fffff]
    May 26 09:42:34 phenom kernel: pci 0000:00:04.0: bridge window [mem 0xfde00000-0xfdefffff 64bit pref]
    May 26 09:42:34 phenom kernel: pci 0000:00:09.0: PCI bridge to [bus 03]
    May 26 09:42:34 phenom kernel: pci 0000:00:09.0: bridge window [io 0xe000-0xefff]
    May 26 09:42:34 phenom kernel: pci 0000:00:09.0: bridge window [mem 0xfdd00000-0xfddfffff]
    May 26 09:42:34 phenom kernel: pci 0000:00:09.0: bridge window [mem 0xfdc00000-0xfdcfffff 64bit pref]
    May 26 09:42:34 phenom kernel: pci 0000:00:0a.0: PCI bridge to [bus 04]
    May 26 09:42:34 phenom kernel: pci 0000:00:0a.0: bridge window [io 0xd000-0xdfff]
    May 26 09:42:34 phenom kernel: pci 0000:00:0a.0: bridge window [mem 0xfdb00000-0xfdbfffff]
    May 26 09:42:34 phenom kernel: pci 0000:00:0a.0: bridge window [mem 0xfd800000-0xfd8fffff 64bit pref]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.4: PCI bridge to [bus 05]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [io 0xa000-0xafff]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [mem 0xfda00000-0xfdafffff]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [mem 0xfd900000-0xfd9fffff pref]
    May 26 09:42:34 phenom kernel: pci 0000:00:15.0: PCI bridge to [bus 06]
    May 26 09:42:34 phenom kernel: pci 0000:00:15.0: bridge window [io 0x9000-0x9fff]
    May 26 09:42:34 phenom kernel: pci 0000:00:15.0: bridge window [mem 0xfd700000-0xfd7fffff]
    May 26 09:42:34 phenom kernel: pci 0000:00:15.0: bridge window [mem 0xfd600000-0xfd6fffff 64bit pref]
    May 26 09:42:34 phenom kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7 window]
    May 26 09:42:34 phenom kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff window]
    May 26 09:42:34 phenom kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
    May 26 09:42:34 phenom kernel: pci_bus 0000:00: resource 7 [mem 0x000c0000-0x000dffff window]
    May 26 09:42:34 phenom kernel: pci_bus 0000:00: resource 8 [mem 0xfed40000-0xfed44fff window]
    May 26 09:42:34 phenom kernel: pci_bus 0000:00: resource 9 [mem 0xd0000000-0xfebfffff window]
    May 26 09:42:34 phenom kernel: pci_bus 0000:01: resource 0 [io 0xc000-0xcfff]
    May 26 09:42:34 phenom kernel: pci_bus 0000:01: resource 1 [mem 0xfd500000-0xfd5fffff]
    May 26 09:42:34 phenom kernel: pci_bus 0000:01: resource 2 [mem 0xd0000000-0xdfffffff 64bit pref]
    May 26 09:42:34 phenom kernel: pci_bus 0000:02: resource 0 [io 0xb000-0xbfff]
    May 26 09:42:34 phenom kernel: pci_bus 0000:02: resource 1 [mem 0xfd400000-0xfd4fffff]
    May 26 09:42:34 phenom kernel: pci_bus 0000:02: resource 2 [mem 0xfde00000-0xfdefffff 64bit pref]
    May 26 09:42:34 phenom kernel: pci_bus 0000:03: resource 0 [io 0xe000-0xefff]
    May 26 09:42:34 phenom kernel: pci_bus 0000:03: resource 1 [mem 0xfdd00000-0xfddfffff]
    May 26 09:42:34 phenom kernel: pci_bus 0000:03: resource 2 [mem 0xfdc00000-0xfdcfffff 64bit pref]
    May 26 09:42:34 phenom kernel: pci_bus 0000:04: resource 0 [io 0xd000-0xdfff]
    May 26 09:42:34 phenom kernel: pci_bus 0000:04: resource 1 [mem 0xfdb00000-0xfdbfffff]
    May 26 09:42:34 phenom kernel: pci_bus 0000:04: resource 2 [mem 0xfd800000-0xfd8fffff 64bit pref]
    May 26 09:42:34 phenom kernel: pci_bus 0000:05: resource 0 [io 0xa000-0xafff]
    May 26 09:42:34 phenom kernel: pci_bus 0000:05: resource 1 [mem 0xfda00000-0xfdafffff]
    May 26 09:42:34 phenom kernel: pci_bus 0000:05: resource 2 [mem 0xfd900000-0xfd9fffff pref]
    May 26 09:42:34 phenom kernel: pci_bus 0000:05: resource 4 [io 0x0000-0x0cf7 window]
    May 26 09:42:34 phenom kernel: pci_bus 0000:05: resource 5 [io 0x0d00-0xffff window]
    May 26 09:42:34 phenom kernel: pci_bus 0000:05: resource 6 [mem 0x000a0000-0x000bffff window]
    May 26 09:42:34 phenom kernel: pci_bus 0000:05: resource 7 [mem 0x000c0000-0x000dffff window]
    May 26 09:42:34 phenom kernel: pci_bus 0000:05: resource 8 [mem 0xfed40000-0xfed44fff window]
    May 26 09:42:34 phenom kernel: pci_bus 0000:05: resource 9 [mem 0xd0000000-0xfebfffff window]
    May 26 09:42:34 phenom kernel: pci_bus 0000:06: resource 0 [io 0x9000-0x9fff]
    May 26 09:42:34 phenom kernel: pci_bus 0000:06: resource 1 [mem 0xfd700000-0xfd7fffff]
    May 26 09:42:34 phenom kernel: pci_bus 0000:06: resource 2 [mem 0xfd600000-0xfd6fffff 64bit pref]
    May 26 09:42:34 phenom kernel: NET: Registered protocol family 2
    May 26 09:42:34 phenom kernel: TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
    May 26 09:42:34 phenom kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
    May 26 09:42:34 phenom kernel: TCP: Hash tables configured (established 131072 bind 65536)
    May 26 09:42:34 phenom kernel: TCP: reno registered
    May 26 09:42:34 phenom kernel: UDP hash table entries: 8192 (order: 6, 262144 bytes)
    May 26 09:42:34 phenom kernel: UDP-Lite hash table entries: 8192 (order: 6, 262144 bytes)
    May 26 09:42:34 phenom kernel: NET: Registered protocol family 1
    May 26 09:42:34 phenom kernel: pci 0000:01:00.0: Video device with shadowed ROM
    May 26 09:42:34 phenom kernel: PCI: CLS 64 bytes, default 64
    May 26 09:42:34 phenom kernel: Unpacking initramfs...
    May 26 09:42:34 phenom kernel: Freeing initrd memory: 14980K (ffff8800362ae000 - ffff88003714f000)
    May 26 09:42:34 phenom kernel: PCI-DMA: Disabling AGP.
    May 26 09:42:34 phenom kernel: PCI-DMA: aperture base @ c4000000 size 65536 KB
    May 26 09:42:34 phenom kernel: PCI-DMA: using GART IOMMU.
    May 26 09:42:34 phenom kernel: PCI-DMA: Reserving 64MB of IOMMU area in the AGP aperture
    May 26 09:42:34 phenom kernel: microcode: CPU0: patch_level=0x010000bf
    May 26 09:42:34 phenom kernel: microcode: CPU1: patch_level=0x010000bf
    May 26 09:42:34 phenom kernel: microcode: CPU2: patch_level=0x010000bf
    May 26 09:42:34 phenom kernel: microcode: CPU3: patch_level=0x010000bf
    May 26 09:42:34 phenom kernel: microcode: CPU4: patch_level=0x010000bf
    May 26 09:42:34 phenom kernel: microcode: CPU5: patch_level=0x010000bf
    May 26 09:42:34 phenom kernel: microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
    May 26 09:42:34 phenom kernel: LVT offset 1 assigned for vector 0x400
    May 26 09:42:34 phenom kernel: IBS: LVT offset 1 assigned
    May 26 09:42:34 phenom kernel: perf: AMD IBS detected (0x0000001f)
    May 26 09:42:34 phenom kernel: Scanning for low memory corruption every 60 seconds
    May 26 09:42:34 phenom kernel: futex hash table entries: 2048 (order: 5, 131072 bytes)
    May 26 09:42:34 phenom kernel: Initialise system trusted keyring
    May 26 09:42:34 phenom kernel: HugeTLB registered 2 MB page size, pre-allocated 0 pages
    May 26 09:42:34 phenom kernel: zpool: loaded
    May 26 09:42:34 phenom kernel: zbud: loaded
    May 26 09:42:34 phenom kernel: VFS: Disk quotas dquot_6.5.2
    May 26 09:42:34 phenom kernel: VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
    May 26 09:42:34 phenom kernel: Key type big_key registered
    May 26 09:42:34 phenom kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
    May 26 09:42:34 phenom kernel: io scheduler noop registered
    May 26 09:42:34 phenom kernel: io scheduler deadline registered
    May 26 09:42:34 phenom kernel: io scheduler cfq registered (default)
    May 26 09:42:34 phenom kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    May 26 09:42:34 phenom kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
    May 26 09:42:34 phenom kernel: vesafb: mode is 1600x1200x32, linelength=6400, pages=0
    May 26 09:42:34 phenom kernel: vesafb: scrolling: redraw
    May 26 09:42:34 phenom kernel: vesafb: Truecolor: size=0:8:8:8, shift=0:16:8:0
    May 26 09:42:34 phenom kernel: vesafb: framebuffer at 0xd0000000, mapped to 0xffffc90011c00000, using 7552k, total 7552k
    May 26 09:42:34 phenom kernel: Console: switching to colour frame buffer device 200x75
    May 26 09:42:34 phenom kernel: fb0: VESA VGA frame buffer device
    May 26 09:42:34 phenom kernel: GHES: HEST is not enabled!
    May 26 09:42:34 phenom kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    May 26 09:42:34 phenom kernel: 00:03: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
    May 26 09:42:34 phenom kernel: Linux agpgart interface v0.103
    May 26 09:42:34 phenom kernel: rtc_cmos 00:02: RTC can wake from S4
    May 26 09:42:34 phenom kernel: rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
    May 26 09:42:34 phenom kernel: rtc_cmos 00:02: alarms up to one month, 242 bytes nvram, hpet irqs
    May 26 09:42:34 phenom kernel: rtc-cmos: BIOS has alarm-disable quirk.
    May 26 09:42:34 phenom kernel: RTC alarms disabled
    May 26 09:42:34 phenom kernel: ledtrig-cpu: registered to indicate activity on CPUs
    May 26 09:42:34 phenom kernel: TCP: cubic registered
    May 26 09:42:34 phenom kernel: NET: Registered protocol family 10
    May 26 09:42:34 phenom kernel: NET: Registered protocol family 17
    May 26 09:42:34 phenom kernel: Loading compiled-in X.509 certificates
    May 26 09:42:34 phenom kernel: registered taskstats version 1
    May 26 09:42:34 phenom kernel: Magic number: 15:372:724
    May 26 09:42:34 phenom kernel: rtc_cmos 00:02: setting system clock to 2015-05-26 07:42:29 UTC (1432626149)
    May 26 09:42:34 phenom kernel: PM: Hibernation image not present or could not be loaded.
    May 26 09:42:34 phenom kernel: Freeing unused kernel memory: 1160K (ffffffff818d4000 - ffffffff819f6000)
    May 26 09:42:34 phenom kernel: Write protecting the kernel read-only data: 8192k
    May 26 09:42:34 phenom kernel: Freeing unused kernel memory: 504K (ffff880001582000 - ffff880001600000)
    May 26 09:42:34 phenom kernel: Freeing unused kernel memory: 264K (ffff8800017be000 - ffff880001800000)
    May 26 09:42:34 phenom kernel: random: systemd-tmpfile urandom read with 3 bits of entropy available
    May 26 09:42:34 phenom kernel: [drm] Initialized drm 1.1.0 20060810
    May 26 09:42:34 phenom kernel: [drm] radeon kernel modesetting enabled.
    May 26 09:42:34 phenom kernel: checking generic (d0000000 760000) vs hw (d0000000 10000000)
    May 26 09:42:34 phenom kernel: fb: switching to radeondrmfb from VESA VGA
    May 26 09:42:34 phenom kernel: Console: switching to colour dummy device 80x25
    May 26 09:42:34 phenom kernel: [drm] initializing kernel modesetting (CAICOS 0x1002:0x6779 0x1043:0x0483).
    May 26 09:42:34 phenom kernel: [drm] register mmio base: 0xFD5C0000
    May 26 09:42:34 phenom kernel: [drm] register mmio size: 131072
    May 26 09:42:34 phenom kernel: ATOM BIOS: 6779.13.12.0.45.AS01
    May 26 09:42:34 phenom kernel: radeon 0000:01:00.0: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF (1024M used)
    May 26 09:42:34 phenom kernel: radeon 0000:01:00.0: GTT: 1024M 0x0000000040000000 - 0x000000007FFFFFFF
    May 26 09:42:34 phenom kernel: [drm] Detected VRAM RAM=1024M, BAR=256M
    May 26 09:42:34 phenom kernel: [drm] RAM width 64bits DDR
    May 26 09:42:34 phenom kernel: [TTM] Zone kernel: Available graphics memory: 8217894 kiB
    May 26 09:42:34 phenom kernel: [TTM] Zone dma32: Available graphics memory: 2097152 kiB
    May 26 09:42:34 phenom kernel: [TTM] Initializing pool allocator
    May 26 09:42:34 phenom kernel: [TTM] Initializing DMA pool allocator
    May 26 09:42:34 phenom kernel: [drm] radeon: 1024M of VRAM memory ready
    May 26 09:42:34 phenom kernel: [drm] radeon: 1024M of GTT memory ready.
    May 26 09:42:34 phenom kernel: [drm] Loading CAICOS Microcode
    May 26 09:42:34 phenom kernel: [drm] Internal thermal controller without fan control
    May 26 09:42:34 phenom kernel: [drm] radeon: dpm initialized
    May 26 09:42:34 phenom kernel: [drm] GART: num cpu pages 262144, num gpu pages 262144
    May 26 09:42:34 phenom kernel: [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0
    May 26 09:42:34 phenom kernel: [drm] PCIE GART of 1024M enabled (table at 0x0000000000274000).
    May 26 09:42:34 phenom kernel: radeon 0000:01:00.0: WB enabled
    May 26 09:42:34 phenom kernel: radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff88041a0cdc00
    May 26 09:42:34 phenom kernel: radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff88041a0cdc0c
    May 26 09:42:34 phenom kernel: radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000072118 and cpu addr 0xffffc900126b2118
    May 26 09:42:34 phenom kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
    May 26 09:42:34 phenom kernel: [drm] Driver supports precise vblank timestamp query.
    May 26 09:42:34 phenom kernel: radeon 0000:01:00.0: radeon: MSI limited to 32-bit
    May 26 09:42:34 phenom kernel: radeon 0000:01:00.0: radeon: using MSI.
    May 26 09:42:34 phenom kernel: [drm] radeon: irq initialized.
    May 26 09:42:34 phenom kernel: [drm] ring test on 0 succeeded in 2 usecs
    May 26 09:42:34 phenom kernel: [drm] ring test on 3 succeeded in 7 usecs
    May 26 09:42:34 phenom kernel: [drm] ring test on 5 succeeded in 2 usecs
    May 26 09:42:34 phenom kernel: [drm] UVD initialized successfully.
    May 26 09:42:34 phenom kernel: [drm] ib test on ring 0 succeeded in 0 usecs
    May 26 09:42:34 phenom kernel: [drm] ib test on ring 3 succeeded in 0 usecs
    May 26 09:42:34 phenom kernel: [drm] ib test on ring 5 succeeded
    May 26 09:42:34 phenom kernel: [drm] Radeon Display Connectors
    May 26 09:42:34 phenom kernel: [drm] Connector 0:
    May 26 09:42:34 phenom kernel: [drm] HDMI-A-1
    May 26 09:42:34 phenom kernel: [drm] HPD1
    May 26 09:42:34 phenom kernel: [drm] DDC: 0x6460 0x6460 0x6464 0x6464 0x6468 0x6468 0x646c 0x646c
    May 26 09:42:34 phenom kernel: [drm] Encoders:
    May 26 09:42:34 phenom kernel: [drm] DFP1: INTERNAL_UNIPHY1
    May 26 09:42:34 phenom kernel: [drm] Connector 1:
    May 26 09:42:34 phenom kernel: [drm] DVI-D-1
    May 26 09:42:34 phenom kernel: [drm] HPD4
    May 26 09:42:34 phenom kernel: [drm] DDC: 0x6450 0x6450 0x6454 0x6454 0x6458 0x6458 0x645c 0x645c
    May 26 09:42:34 phenom kernel: [drm] Encoders:
    May 26 09:42:34 phenom kernel: [drm] DFP2: INTERNAL_UNIPHY
    May 26 09:42:34 phenom kernel: [drm] Connector 2:
    May 26 09:42:34 phenom kernel: [drm] VGA-1
    May 26 09:42:34 phenom kernel: [drm] DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 0x643c 0x643c
    May 26 09:42:34 phenom kernel: [drm] Encoders:
    May 26 09:42:34 phenom kernel: [drm] CRT1: INTERNAL_KLDSCP_DAC1
    May 26 09:42:34 phenom kernel: tsc: Refined TSC clocksource calibration: 3300.098 MHz
    May 26 09:42:34 phenom kernel: [drm] fb mappable at 0xD0475000
    May 26 09:42:34 phenom kernel: [drm] vram apper at 0xD0000000
    May 26 09:42:34 phenom kernel: [drm] size 9216000
    May 26 09:42:34 phenom kernel: [drm] fb depth is 24
    May 26 09:42:34 phenom kernel: [drm] pitch is 7680
    May 26 09:42:34 phenom kernel: fbcon: radeondrmfb (fb0) is primary device
    May 26 09:42:34 phenom kernel: Console: switching to colour frame buffer device 240x75
    May 26 09:42:34 phenom kernel: radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device
    May 26 09:42:34 phenom kernel: radeon 0000:01:00.0: registered panic notifier
    May 26 09:42:34 phenom kernel: [drm] Initialized radeon 2.41.0 20080528 for 0000:01:00.0 on minor 0
    May 26 09:42:34 phenom kernel: wmi: Mapper loaded
    May 26 09:42:34 phenom kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
    May 26 09:42:34 phenom kernel: ACPI: Power Button [PWRB]
    May 26 09:42:34 phenom kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
    May 26 09:42:34 phenom kernel: ACPI: Power Button [PWRF]
    May 26 09:42:34 phenom kernel: MXM: GUID detected in BIOS
    May 26 09:42:34 phenom kernel: i8042: PNP: No PS/2 controller found. Probing ports directly.
    May 26 09:42:34 phenom kernel: i8042: Failed to disable AUX port, but continuing anyway... Is this a SiS?
    May 26 09:42:34 phenom kernel: i8042: If AUX port is really absent please use the 'i8042.noaux' option
    May 26 09:42:34 phenom kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
    May 26 09:42:34 phenom kernel: ACPI: bus type USB registered
    May 26 09:42:34 phenom kernel: usbcore: registered new interface driver usbfs
    May 26 09:42:34 phenom kernel: SCSI subsystem initialized
    May 26 09:42:34 phenom kernel: usbcore: registered new interface driver hub
    May 26 09:42:34 phenom kernel: usbcore: registered new device driver usb
    May 26 09:42:34 phenom kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    May 26 09:42:34 phenom kernel: ehci-pci: EHCI PCI platform driver
    May 26 09:42:34 phenom kernel: QUIRK: Enable AMD PLL fix
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:12.2: EHCI Host Controller
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:12.2: new USB bus registered, assigned bus number 1
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:12.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:12.2: debug port 1
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:12.2: irq 17, io mem 0xfdffd000
    May 26 09:42:34 phenom kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
    May 26 09:42:34 phenom kernel: ohci-pci: OHCI PCI platform driver
    May 26 09:42:34 phenom kernel: libata version 3.00 loaded.
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:12.2: USB 2.0 started, EHCI 1.00
    May 26 09:42:34 phenom kernel: hub 1-0:1.0: USB hub found
    May 26 09:42:34 phenom kernel: hub 1-0:1.0: 5 ports detected
    May 26 09:42:34 phenom kernel: xhci_hcd 0000:02:00.0: xHCI Host Controller
    May 26 09:42:34 phenom kernel: xhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 2
    May 26 09:42:34 phenom kernel: xhci_hcd 0000:02:00.0: hcc params 0x040050af hci version 0x100 quirks 0x00080490
    May 26 09:42:34 phenom kernel: hub 2-0:1.0: USB hub found
    May 26 09:42:34 phenom kernel: hub 2-0:1.0: 2 ports detected
    May 26 09:42:34 phenom kernel: xhci_hcd 0000:02:00.0: xHCI Host Controller
    May 26 09:42:34 phenom kernel: xhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 3
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:13.2: EHCI Host Controller
    May 26 09:42:34 phenom kernel: hub 3-0:1.0: USB hub found
    May 26 09:42:34 phenom kernel: hub 3-0:1.0: 2 ports detected
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:13.2: new USB bus registered, assigned bus number 4
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:13.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:13.2: debug port 1
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:13.2: irq 17, io mem 0xfdffb000
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:13.2: USB 2.0 started, EHCI 1.00
    May 26 09:42:34 phenom kernel: hub 4-0:1.0: USB hub found
    May 26 09:42:34 phenom kernel: hub 4-0:1.0: 5 ports detected
    May 26 09:42:34 phenom kernel: xhci_hcd 0000:04:00.0: xHCI Host Controller
    May 26 09:42:34 phenom kernel: xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 5
    May 26 09:42:34 phenom kernel: xhci_hcd 0000:04:00.0: hcc params 0x040050af hci version 0x100 quirks 0x00080490
    May 26 09:42:34 phenom kernel: hub 5-0:1.0: USB hub found
    May 26 09:42:34 phenom kernel: hub 5-0:1.0: 2 ports detected
    May 26 09:42:34 phenom kernel: xhci_hcd 0000:04:00.0: xHCI Host Controller
    May 26 09:42:34 phenom kernel: xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 6
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:16.2: EHCI Host Controller
    May 26 09:42:34 phenom kernel: hub 6-0:1.0: USB hub found
    May 26 09:42:34 phenom kernel: hub 6-0:1.0: 2 ports detected
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:16.2: new USB bus registered, assigned bus number 7
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:16.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:16.2: debug port 1
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:16.2: irq 17, io mem 0xfdff8000
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:16.2: USB 2.0 started, EHCI 1.00
    May 26 09:42:34 phenom kernel: hub 7-0:1.0: USB hub found
    May 26 09:42:34 phenom kernel: hub 7-0:1.0: 4 ports detected
    May 26 09:42:34 phenom kernel: ohci-pci 0000:00:12.0: OHCI PCI host controller
    May 26 09:42:34 phenom kernel: ohci-pci 0000:00:12.0: new USB bus registered, assigned bus number 8
    May 26 09:42:34 phenom kernel: ohci-pci 0000:00:12.0: irq 18, io mem 0xfdffe000
    May 26 09:42:34 phenom kernel: firewire_ohci 0000:05:0e.0: added OHCI v1.10 device as card 0, 4 IR + 8 IT contexts, quirks 0x11
    May 26 09:42:34 phenom kernel: hub 8-0:1.0: USB hub found
    May 26 09:42:34 phenom kernel: hub 8-0:1.0: 5 ports detected
    May 26 09:42:34 phenom kernel: ohci-pci 0000:00:13.0: OHCI PCI host controller
    May 26 09:42:34 phenom kernel: ohci-pci 0000:00:13.0: new USB bus registered, assigned bus number 9
    May 26 09:42:34 phenom kernel: ohci-pci 0000:00:13.0: irq 18, io mem 0xfdffc000
    May 26 09:42:34 phenom kernel: hub 9-0:1.0: USB hub found
    May 26 09:42:34 phenom kernel: hub 9-0:1.0: 5 ports detected
    May 26 09:42:34 phenom kernel: ohci-pci 0000:00:14.5: OHCI PCI host controller
    May 26 09:42:34 phenom kernel: ohci-pci 0000:00:14.5: new USB bus registered, assigned bus number 10
    May 26 09:42:34 phenom kernel: ohci-pci 0000:00:14.5: irq 18, io mem 0xfdffa000
    May 26 09:42:34 phenom kernel: hub 10-0:1.0: USB hub found
    May 26 09:42:34 phenom kernel: hub 10-0:1.0: 2 ports detected
    May 26 09:42:34 phenom kernel: ohci-pci 0000:00:16.0: OHCI PCI host controller
    May 26 09:42:34 phenom kernel: ohci-pci 0000:00:16.0: new USB bus registered, assigned bus number 11
    May 26 09:42:34 phenom kernel: ohci-pci 0000:00:16.0: irq 18, io mem 0xfdff9000
    May 26 09:42:34 phenom kernel: hub 11-0:1.0: USB hub found
    May 26 09:42:34 phenom kernel: hub 11-0:1.0: 4 ports detected
    May 26 09:42:34 phenom kernel: scsi host0: pata_atiixp
    May 26 09:42:34 phenom kernel: scsi host1: pata_atiixp
    May 26 09:42:34 phenom kernel: ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xfa00 irq 14
    May 26 09:42:34 phenom kernel: ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xfa08 irq 15
    May 26 09:42:34 phenom kernel: ahci 0000:00:11.0: version 3.0
    May 26 09:42:34 phenom kernel: ahci 0000:00:11.0: AHCI 0001.0200 32 slots 4 ports 6 Gbps 0xf impl SATA mode
    May 26 09:42:34 phenom kernel: ahci 0000:00:11.0: flags: 64bit ncq sntf ilck pm led clo pmp pio slum part
    May 26 09:42:34 phenom kernel: scsi host2: ahci
    May 26 09:42:34 phenom kernel: scsi host3: ahci
    May 26 09:42:34 phenom kernel: scsi host4: ahci
    May 26 09:42:34 phenom kernel: scsi host5: ahci
    May 26 09:42:34 phenom kernel: ata3: SATA max UDMA/133 abar m1024@0xfdfff000 port 0xfdfff100 irq 19
    May 26 09:42:34 phenom kernel: ata4: SATA max UDMA/133 abar m1024@0xfdfff000 port 0xfdfff180 irq 19
    May 26 09:42:34 phenom kernel: ata5: SATA max UDMA/133 abar m1024@0xfdfff000 port 0xfdfff200 irq 19
    May 26 09:42:34 phenom kernel: ata6: SATA max UDMA/133 abar m1024@0xfdfff000 port 0xfdfff280 irq 19
    May 26 09:42:34 phenom kernel: usb 1-1: new high-speed USB device number 2 using ehci-pci
    May 26 09:42:34 phenom kernel: usb 2-2: new high-speed USB device number 2 using xhci_hcd
    May 26 09:42:34 phenom kernel: usb 7-4: new high-speed USB device number 2 using ehci-pci
    May 26 09:42:34 phenom kernel: ata1.01: ATAPI: PLEXTOR DVDR PX-820A, 1.00, max UDMA/66
    May 26 09:42:34 phenom kernel: ata1.01: limited to UDMA/33 due to 40-wire cable
    May 26 09:42:34 phenom kernel: hub 1-1:1.0: USB hub found
    May 26 09:42:34 phenom kernel: hub 1-1:1.0: 4 ports detected
    May 26 09:42:34 phenom kernel: ata1.01: configured for UDMA/33
    May 26 09:42:34 phenom kernel: scsi 0:0:1:0: CD-ROM PLEXTOR DVDR PX-820A 1.00 PQ: 0 ANSI: 5
    May 26 09:42:34 phenom kernel: firewire_core 0000:05:0e.0: created device fw0: GUID 0049e55059f30500, S400
    May 26 09:42:34 phenom kernel: ata3: SATA link down (SStatus 0 SControl 300)
    May 26 09:42:34 phenom kernel: ata4: SATA link down (SStatus 0 SControl 300)
    May 26 09:42:34 phenom kernel: Switched to clocksource tsc
    May 26 09:42:34 phenom kernel: usb 1-1.1: new low-speed USB device number 3 using ehci-pci
    May 26 09:42:34 phenom kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    May 26 09:42:34 phe

    Hi,
    I have exactly the same problem. systemd-logind sporadically fails to start, therefore preventing the login prompt to appear. Resetting the machine is the only solution in that case. Most of the time, the system start works without problems though. Here are a few relevant lines from my logs:
    # journalctl --unit=systemd-logind | grep -C50 'Connection timed out'
    -- Reboot --
    Apr 22 10:16:36 deltaflyer systemd[1]: Starting Login Service...
    Apr 22 10:17:01 deltaflyer systemd-logind[377]: Failed to enable subscription: Connection timed out
    Apr 22 10:17:01 deltaflyer systemd-logind[377]: Failed to fully start up daemon: Connection timed out
    Apr 22 10:17:01 deltaflyer systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
    Apr 22 10:17:01 deltaflyer systemd[1]: Failed to start Login Service.
    Apr 22 10:17:01 deltaflyer systemd[1]: Unit systemd-logind.service entered failed state.
    Apr 22 10:17:01 deltaflyer systemd[1]: systemd-logind.service failed.
    Apr 22 10:17:01 deltaflyer systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
    -- Reboot --
    Here is relevant output from the complete log (not only systemd-logind):
    # journalctl | grep -C10 'Connection timed out'
    Apr 22 10:17:01 deltaflyer dbus[389]: [system] Successfully activated service 'org.freedesktop.systemd1'
    Apr 22 10:17:01 deltaflyer NetworkManager[387]: <info> NetworkManager (version 1.0.0) is starting...
    Apr 22 10:17:01 deltaflyer acpid[386]: starting up with netlink and the input layer
    Apr 22 10:17:01 deltaflyer smartd[381]: Unable to monitor any SMART enabled devices. Try debug (-d) option. Exiting...
    Apr 22 10:17:01 deltaflyer /usr/bin/gpm[390]: imps2: Auto-detected intellimouse PS/2
    Apr 22 10:17:01 deltaflyer dbus[389]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service'
    Apr 22 10:17:01 deltaflyer NetworkManager[387]: <info> Read config: /etc/NetworkManager/NetworkManager.conf
    Apr 22 10:17:01 deltaflyer NetworkManager[387]: <info> WEXT support is enabled
    Apr 22 10:16:36 deltaflyer systemd[1]: Starting Virtual console mouse server...
    Apr 22 10:16:36 deltaflyer systemd[1]: Started D-Bus System Message Bus.
    Apr 22 10:17:01 deltaflyer systemd-logind[377]: Failed to enable subscription: Connection timed out
    Apr 22 10:17:01 deltaflyer systemd-logind[377]: Failed to fully start up daemon: Connection timed out
    Apr 22 10:17:01 deltaflyer systemd[1]: Failed to register name: Connection timed out
    Apr 22 10:17:01 deltaflyer systemd[1]: Failed to set up API bus: Connection timed out
    Apr 22 10:17:01 deltaflyer systemd[1]: Starting D-Bus System Message Bus...
    Apr 22 10:17:01 deltaflyer systemd[1]: Started LVM2 PV scan on device 254:0.
    Apr 22 10:17:01 deltaflyer lvm[320]: 7 logical volume(s) in volume group "deltaflyer" now active
    Apr 22 10:17:01 deltaflyer dbus[389]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service'
    Apr 22 10:17:01 deltaflyer acpid[386]: 1 rule loaded
    Apr 22 10:17:01 deltaflyer acpid[386]: waiting for events: event logging is off
    Apr 22 10:17:01 deltaflyer NetworkManager[387]: <info> VPN: loaded org.freedesktop.NetworkManager.openvpn
    Apr 22 10:17:01 deltaflyer NetworkManager[387]: <info> Loaded plugin keyfile: (c) 2007 - 2013 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
    Apr 22 10:17:01 deltaflyer systemd[1]: Started Restore Sound Card State.
    Mai 11 11:20:56 deltaflyer acpid[638]: starting up with netlink and the input layer
    Mai 11 11:20:56 deltaflyer smartd[640]: Monitoring 1 ATA and 0 SCSI devices
    Mai 11 11:20:56 deltaflyer /usr/bin/gpm[637]: imps2: Auto-detected intellimouse PS/2
    Mai 11 11:20:56 deltaflyer dbus[642]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service'
    Mai 11 11:20:56 deltaflyer NetworkManager[633]: <info> Read config: /etc/NetworkManager/NetworkManager.conf
    Mai 11 11:20:56 deltaflyer NetworkManager[633]: <info> WEXT support is enabled
    Mai 11 11:20:56 deltaflyer dbus[642]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service'
    Mai 11 11:20:56 deltaflyer acpid[638]: 1 rule loaded
    Mai 11 11:20:56 deltaflyer acpid[638]: waiting for events: event logging is off
    Mai 11 11:20:31 deltaflyer systemd[1]: Started D-Bus System Message Bus.
    Mai 11 11:20:56 deltaflyer systemd-logind[634]: Failed to enable subscription: Connection timed out
    Mai 11 11:20:56 deltaflyer systemd-logind[634]: Failed to fully start up daemon: Connection timed out
    Mai 11 11:20:56 deltaflyer systemd[1]: Failed to register name: Connection timed out
    Mai 11 11:20:56 deltaflyer systemd[1]: Failed to set up API bus: Connection timed out
    Mai 11 11:20:56 deltaflyer systemd[1]: Starting D-Bus System Message Bus...
    Mai 11 11:20:56 deltaflyer systemd[1]: Started Manage Sound Card State (restore and store).
    Mai 11 11:20:56 deltaflyer systemd[1]: Starting Restore Sound Card State...
    Mai 11 11:20:56 deltaflyer systemd[1]: Started Daily man-db cache update.
    Mai 11 11:20:56 deltaflyer systemd[1]: Starting Daily man-db cache update.
    Mai 11 11:20:56 deltaflyer systemd[1]: Started Daily verification of password and group files.
    Mai 11 11:20:56 deltaflyer systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
    Mai 11 11:20:56 deltaflyer systemd[1]: Failed to start Login Service.
    Mai 11 11:20:56 deltaflyer systemd[1]: Unit systemd-logind.service entered failed state.
    Mai 11 11:20:56 deltaflyer systemd[1]: systemd-logind.service failed.
    Mai 27 16:47:34 deltaflyer smartd[399]: Device: /dev/sda [SAT], VBOX HARDDISK, S/N:VB9c7c4cff-f1cdf11a, FW:1.0, 500 GB
    Mai 27 16:47:34 deltaflyer smartd[399]: Device: /dev/sda [SAT], not found in smartd database.
    Mai 27 16:47:34 deltaflyer smartd[399]: Device: /dev/sda [SAT], lacks SMART capability
    Mai 27 16:47:34 deltaflyer smartd[399]: Device: /dev/sda [SAT], to proceed anyway, use '-T permissive' Directive.
    Mai 27 16:47:34 deltaflyer smartd[399]: Unable to monitor any SMART enabled devices. Try debug (-d) option. Exiting...
    Mai 27 16:47:59 deltaflyer /usr/bin/gpm[400]: *** info [mice.c(1990)]:
    Mai 27 16:47:59 deltaflyer dbus[402]: [system] Successfully activated service 'org.freedesktop.systemd1'
    Mai 27 16:47:59 deltaflyer nm-dispatcher[395]: Could not get the system bus (Timeout was reached). Make sure the message bus daemon is running!
    Mai 27 16:47:59 deltaflyer acpid[391]: starting up with netlink and the input layer
    Mai 27 16:47:34 deltaflyer systemd[1]: Started D-Bus System Message Bus.
    Mai 27 16:47:59 deltaflyer systemd-logind[392]: Failed to enable subscription: Connection timed out
    Mai 27 16:47:59 deltaflyer systemd-logind[392]: Failed to fully start up daemon: Connection timed out
    Mai 27 16:47:59 deltaflyer systemd[1]: Failed to register name: Connection timed out
    Mai 27 16:47:59 deltaflyer systemd[1]: Failed to set up API bus: Connection timed out
    Mai 27 16:47:59 deltaflyer systemd[1]: Starting D-Bus System Message Bus...
    Mai 27 16:47:59 deltaflyer systemd[1]: Starting Preprocess NFS configuration...
    Mai 27 16:47:59 deltaflyer systemd[1]: Starting Network Manager...
    Mai 27 16:47:59 deltaflyer systemd[1]: Starting VirtualBox Guest Service...
    Mai 27 16:47:59 deltaflyer systemd[1]: Started LVM2 PV scan on device 254:0.
    Mai 27 16:47:59 deltaflyer /usr/bin/gpm[400]: imps2: Auto-detected intellimouse PS/2
    Mai 27 16:47:59 deltaflyer dbus[402]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service'
    Mai 27 16:47:59 deltaflyer upowerd[393]: (upowerd:393): UPower-WARNING **: Failed to acquire org.freedesktop.UPower: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
    Mai 27 16:47:59 deltaflyer upowerd[393]: (upowerd:393): UPower-WARNING **: Could not acquire name; bailing out
    Mai 27 16:47:59 deltaflyer systemd[1]: Started Restore Sound Card State.
    It almost seems to be a problem with a dbus and/or NetworkManager race condition.

  • 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?

  • [solved] After Gnome 3.8/Kernel update bumblebee is broken

    After some troubles with Gnome 3.8 and GDM and getting back to work bumblebee is broken. I guess the troubles came with the new kernel.
    $ optirun -vv glxgears
    [ 184.945324] [DEBUG]Reading file: /etc/bumblebee/bumblebee.conf
    [ 184.946196] [DEBUG]optirun version 3.1 starting...
    [ 184.946228] [DEBUG]Active configuration:
    [ 184.946239] [DEBUG] bumblebeed config file: /etc/bumblebee/bumblebee.conf
    [ 184.946250] [DEBUG] X display: :8
    [ 184.946260] [DEBUG] LD_LIBRARY_PATH: /usr/lib/nvidia:/usr/lib32/nvidia
    [ 184.946271] [DEBUG] Socket path: /var/run/bumblebee.socket
    [ 184.946281] [DEBUG] Accel/display bridge: auto
    [ 184.946291] [DEBUG] VGL Compression: proxy
    [ 184.946332] [DEBUG]Using auto-detected bridge virtualgl
    [ 184.974394] [INFO]Response: No - error: [XORG] (EE) Failed to load module "mouse" (module does not exist, 0)
    [ 184.974451] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) Failed to load module "mouse" (module does not exist, 0)
    [ 184.974471] [DEBUG]Socket closed.
    [ 184.974531] [ERROR]Aborting because fallback start is disabled.
    [ 184.974536] [DEBUG]Killing all remaining processes.
    $ systemctl status bumblebeed
    bumblebeed.service - Bumblebee C Daemon
    Loaded: loaded (/usr/lib/systemd/system/bumblebeed.service; enabled)
    Active: active (running) since Mi 2013-04-24 20:00:21 CEST; 4min 40s ago
    Main PID: 264 (bumblebeed)
    CGroup: name=systemd:/system/bumblebeed.service
    └─264 /usr/sbin/bumblebeed
    $ cat /proc/acpi/bbswitch
    0000:01:00.0 ON
    I made a fresh reinstallation of bumblebee but it does not help. All packages inkl. bbswitch are up to date (whole system is up to date). Thx for any hints.
    Last edited by wwn (2013-04-24 18:20:33)

    aaarrrrgh: that was the thing to get gdm and gnome 3.8 get back to work again.!
    devil and the deep blue see

  • [SOLVED] can't mount USB external drive since udev upgrade to systemd

    At somepoint in time around the June 1 change from udev to systemd or the change from udisks to udisks2 something has changed the way my external USB drives auto-mount.
    I have always just plugged them in and they show up in PacmanFM just fine. Now, they do show up but the NTFS drive is showing as read-only and another empty drive that I have reformatted using GParted to xfs, then ext2, and finally again using ext4 gives "Permission Denied" errors when I try to put a file on the drive. Happens no matter how I format it.
    Did something change that I need to manually configure? Up to this point I relied on udev just kind of doing its thing - I never had to configure anything to get these drives to work properly.
    Last edited by AyeCapn (2012-06-26 15:15:59)

    Perhaps the cause of my issue might be relevant:
    While the now deleted udev automount script from the Arch Wiki had worked for months without issue, approximately since the udev/systemd merger it became broken for NTFS partitions on USB devices.
    It still worked with the classic initscripts, but with systemd it only resulted in "Transport endpoint is not connected" for the supposed mount point and ls reported lots of "?" for it.

  • [SOLVED]root partition read only after update systemd

    After update systemd today, the systemd-remount-fs.service fail to start. Root filesystem is read only I tried add rw to fstab mount option, but the root parition is still  read only. I noticed that util-linux package are installed and udev package is dropped , Does it related to my problem?
    Please advice me.
    Sorry for my bad English.
    Update
    After downgard util-linux package, the system work again 
    Update 2
    UUID in grub.conf and fstab  are inconsistent, Thanks to  tomegun for point out this problem.
    Last edited by aduser (2012-06-08 04:05:59)

    output of systemctl status systemd-remount-fs.service
    systemd-remount-fs.service - Remount Root and Kernel File Systems
    Loaded: loaded (/usr/lib/systemd/system/systemd-remount-fs.service; static)
    Active: failed (Result: exit-code) since Sun, 03 Jun 2012 01:17:42 +0800; 5min ago
    Process: 132 ExecStart=/usr/lib/systemd/systemd-remount-fs (code=exited, status=1/FAILURE)
    CGroup: name=systemd:/system/systemd-remount-fs.service
    fstab
    UUID=55326b3a-eec9-498e-8e20-0a7ddd8daf9a / btrfs rw,compress=lzo,space_cache,autodefrag 0 1
    UUID=54c17991-716b-496e-a89b-4e978f2d92a4 /boot ext2 defaults 0 1
    systemctl
    UNIT LOAD ACTIVE SUB JOB DESCRIPTION
    proc-sys...misc.automount loaded active waiting Arbitrary Executable File Formats File System Automount Point
    sys-devi...d-card1.device loaded active plugged RV630 audio device [Radeon HD 2600 Series]
    sys-devi...d-card0.device loaded active plugged 82801I (ICH9 Family) HD Audio Controller
    sys-devi...et-eth0.device loaded active plugged RTL8111/8168B PCI Express Gigabit Ethernet controller
    sys-devi...dd-sdd1.device loaded active plugged ST3120213A
    sys-devi...dd-sdd2.device loaded active plugged ST3120213A
    sys-devi...ock-sdd.device loaded active plugged ST3120213A
    sys-devi...da-sda1.device loaded active plugged WDC_WD6400AAKS-22A7B0
    sys-devi...da-sda2.device loaded active plugged WDC_WD6400AAKS-22A7B0
    sys-devi...da-sda3.device loaded active plugged WDC_WD6400AAKS-22A7B0
    sys-devi...da-sda5.device loaded active plugged WDC_WD6400AAKS-22A7B0
    sys-devi...ock-sda.device loaded active plugged WDC_WD6400AAKS-22A7B0
    sys-devi...db-sdb1.device loaded active plugged WDC_WD1002FAEX-00Z3A0
    sys-devi...db-sdb2.device loaded active plugged WDC_WD1002FAEX-00Z3A0
    sys-devi...db-sdb3.device loaded active plugged WDC_WD1002FAEX-00Z3A0
    sys-devi...db-sdb4.device loaded active plugged WDC_WD1002FAEX-00Z3A0
    sys-devi...db-sdb5.device loaded active plugged WDC_WD1002FAEX-00Z3A0
    sys-devi...ock-sdb.device loaded active plugged WDC_WD1002FAEX-00Z3A0
    sys-devi...dc-sdc1.device loaded active plugged ST980811AS
    sys-devi...dc-sdc2.device loaded active plugged ST980811AS
    sys-devi...ock-sdc.device loaded active plugged ST980811AS
    sys-devi...y-ttyS1.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS1
    sys-devi...y-ttyS2.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS2
    sys-devi...y-ttyS3.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS3
    sys-devi...y-ttyS0.device loaded active plugged /sys/devices/pnp0/00:07/tty/ttyS0
    -.mount loaded active mounted /
    boot.mount loaded active mounted /boot
    dev-hugepages.mount loaded active mounted Huge Pages File System
    dev-mqueue.mount loaded active mounted POSIX Message Queue File System
    sys-kernel-debug.mount loaded active mounted Debug File System
    tmp.mount loaded active mounted /tmp
    xs-big.mount loaded active mounted /xs/big
    xs-dev-\...pace\x5d.mount loaded active mounted /xs/dev/[workspace]
    xs-dev.mount loaded active mounted /xs/dev
    xs-dl.mount loaded active mounted /xs/dl
    xs-file.mount loaded active mounted /xs/file
    systemd-...d-console.path loaded active waiting Dispatch Password Requests to Console Directory Watch
    systemd-...word-wall.path loaded active waiting Forward Password Requests to Wall Directory Watch
    console-...daemon.service loaded active running Console Manager
    console-...-start.service loaded failed failed Console System Startup Logging
    dbus.service loaded active running D-Bus System Message Bus
    [email protected] loaded active running dhcpcd on eth0
    gdm.service loaded active running Gnome Display Manager
    [email protected] loaded active running Getty on tty1
    systemd-journald.service loaded active running Journal Service
    systemd-logind.service loaded active running Login Service
    systemd-...unt-fs.service loaded failed failed Remount Root and Kernel File Systems
    systemd-sysctl.service loaded active exited Apply Kernel Variables
    systemd-...-setup.service loaded active exited Recreate Volatile Files and Directories
    systemd-...rigger.service loaded active exited udev Coldplug all Devices
    systemd-udev.service loaded active running udev Kernel Device Manager
    systemd-...nlevel.service loaded failed failed Update UTMP about System Runlevel Changes
    systemd-...ssions.service loaded active exited Permit User Sessions
    systemd-...-setup.service loaded active exited Setup Virtual Console
    dbus.socket loaded active running D-Bus System Message Bus Socket
    systemd-initctl.socket loaded active listening /dev/initctl Compatibility Named Pipe
    systemd-journald.socket loaded active running Journal Socket
    systemd-shutdownd.socket loaded active listening Delayed Shutdown Socket
    systemd-...control.socket loaded active listening udev Control Socket
    systemd-...-kernel.socket loaded active running udev Kernel Socket
    basic.target loaded active active Basic System
    cryptsetup.target loaded active active Encrypted Volumes
    getty.target loaded active active Login Prompts
    graphical.target loaded active active Graphical Interface
    local-fs-pre.target loaded active active Local File Systems (Pre)
    local-fs.target loaded active active Local File Systems
    multi-user.target loaded active active Multi-User
    network.target loaded active active Network
    remote-fs.target loaded active active Remote File Systems
    sockets.target loaded active active Sockets
    sound.target loaded active active Sound Card
    swap.target loaded active active Swap
    sysinit.target loaded active active System Initialization
    systemd-...es-clean.timer loaded active waiting Daily Cleanup of Temporary Directories
    LOAD = Reflects whether the unit definition was properly loaded.
    ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
    SUB = The low-level unit activation state, values depend on unit type.
    JOB = Pending job for the unit.
    74 units listed. Pass --all to see inactive units, too.
    grub2 conf
    menuentry 'Broken' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-ck kernel-true-852c733e-be0d-4375-8668-d7ae049295a9' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 54c17991-716b-496e-a89b-4e978f2d92a4
    else
    search --no-floppy --fs-uuid --set=root 54c17991-716b-496e-a89b-4e978f2d92a4
    fi
    echo 'Loading Linux ck kernel ...'
    linux /vmlinuz-linux-ck root=UUID=852c733e-be0d-4375-8668-d7ae049295a9 ro rootflags=subvol=broken quiet add_efi_memmap elevator=bfq
    echo 'Loading initial ramdisk ...'
    initrd /initramfs-linux-ck.img
    The update packages
    core/btrfs-progs 0.19.20120328-2 2 -> 3
    core/device-mapper 2.02.95-4 4 -> 6
    core/cryptsetup 1.4.2-1 1 -> 2
    core/gpm 1.20.6-7 7 -> 8
    core/lvm2 2.02.95-4 4 -> 6
    extra/libglapi 8.0.3-1 1 -> 2
    extra/libgl 8.0.3-1 1 -> 2
    extra/ati-dri 8.0.3-1 1 -> 2
    extra/bluez 4.99-2 2 -> 6
    extra/consolekit 0.4.6-3 3 -> 4
    extra/gvfs 1.12.3-1 1 -> 2
    extra/gvfs-obexftp 1.12.3-1 1 -> 2
    extra/libatasmart 0.18-1 1 -> 2
    extra/libcanberra 0.28-4 4 -> 5
    extra/libpulse 2.0-1 1 -> 2
    extra/libcanberra-pulse 0.28-4 4 -> 5
    extra/mesa 8.0.3-1 1 -> 2
    extra/pulseaudio 2.0-1 1 -> 2
    extra/xf86-video-ati 6.14.99-0.20120517 0.20120517 -> 1.20120517
    community/libvirt 0.9.12-7 7 -> 8
    community/ttf-ubuntu-font-family 0.80-2 2 -> 3
    multilib/lib32-libglapi 8.0.3-3 3 -> 3.1
    multilib/lib32-libgl 8.0.3-3 3 -> 3.1
    ==> Software upgrade (new version) :
    core/util-linux 2.21.1-2 -> 2.21.2-1
    core/e2fsprogs 1.42.2-2 -> 1.42.3-1
    core/libpipeline 1.2.0-2 -> 1.2.1-1
    core/libsystemd 44-7 -> 184-2
    core/procps-ng 3.3.2-2 -> 3.3.3-1
    core/systemd 44-7 -> 184-2
    core/systemd-sysvcompat 3-1 -> 184-2
    extra/pixman 0.24.4-1 -> 0.26.0-1
    extra/xorg-server-common 1.12.1.902-1 -> 1.12.2-1
    extra/xorg-server 1.12.1.902-1 -> 1.12.2-1
    community/libuser 0.57.1-2 -> 0.57.6-1
    community/os-prober 1.49-3 -> 1.53-1
    community/systemd-arch-units 20120412-6 -> 20120528-3
    repo-ck/linux-ck-corex 3.3.7-1 -> 3.4-1
    repo-ck/linux-ck-corex-headers 3.3.7-1 -> 3.4-1
    ==> New package :
    core/systemd-tools 184-2 (required by systemd)
    Does the systemd not support btrfs subvolume as root partition??
    Last edited by aduser (2012-06-02 17:45:39)

  • Arch as Vmware guest broken?

    Hi!
    For the past couple of weeks!! (ever since systemd 'upgrade') things in vmware-land have been going from bad to worse.
    I have Arch setup as a guest within vmware running on a windoes host. (Also on a mac host, same problems)
    Now, I migrated the system to systemd, and basically had a functioning vm (with copy & paste, timesync etc.).
    There was one problem though, shared folders would not work.
    More specifically when trying to 'ls' the folder (or indeed accessing it any other way) the kernel would OOPS, basically freez up.
    Others are having the same problem, there's even an official bug-report with open-vm-tools.
    Same problem, and here.
    Bug Report for open-vm-tools.
    There's a comment there about this being fixed with the latest build (9.2.2) but that is not the case.
    I've also updated vmware workstation today from 9.0.0 to 9.0.1 with no change.
    But thing are getting even worse.
    See this bug has been preventing me from updating xorg-server & xorg-server-common from 1.13.0-3 1.13.0-4 as I was seeing the exact same issue as mentioned in the report, and as of yesterday:
    libglapi (9.0-1 -> 9.0.1-1)
    libegl (9.0-1 -> 9.0.1-1)
    libgl (9.0-1 -> 9.0.1-1)
    mesa (9.0-1 -> 9.0.1-1)
    svga-dri (9.0-1 -> 9.0.1-1)
    open-vm-tools (1:9.2.0-2 -> 1:9.2.2-2)
    open-vm-tools-modules (1:9.2.0-3 -> 1:9.2.2-1)
    compositing doesn't seem to work, or at least gnome-session loads but instantly freezes with following segfault:
    (EE) BUG: triggered 'if (inSignalContext)'
    (EE) BUG: log.c:484 in LogVMessageVerb()
    (EE) Warning: attempting to log data in a signal unsafe manner while in signal context.
    Please update to check inSignalContext and/or use LogMessageVerbSigSafe() or ErrorFSigSafe().
    The offending log format message is:
    VMWARE(0): vmmouse enable absolute mode
    (EE)
    (EE) Backtrace:
    (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x58a006]
    (EE) 1: /usr/bin/X (LogVMessageVerb+0x195) [0x595345]
    (EE) 2: /usr/bin/X (xf86Msg+0x8f) [0x48262f]
    (EE) 3: /usr/lib/xorg/modules/input/vmmouse_drv.so (0x7f1c760e2000+0x194f) [0x7f1c760e394f]
    (EE) 4: /usr/bin/X (0x400000+0x75987) [0x475987]
    (EE) 5: /usr/bin/X (0x400000+0x9eff8) [0x49eff8]
    (EE) 6: /usr/lib/libpthread.so.0 (0x7f1c7dc49000+0xf1a0) [0x7f1c7dc581a0]
    (EE) 7: /usr/lib/libc.so.6 (__select+0x13) [0x7f1c7c995f13]
    (EE) 8: /usr/bin/X (WaitForSomething+0x190) [0x587430]
    (EE) 9: /usr/bin/X (0x400000+0x37b41) [0x437b41]
    (EE) 10: /usr/bin/X (0x400000+0x2692a) [0x42692a]
    (EE) 11: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7f1c7c8d7725]
    (EE) 12: /usr/bin/X (0x400000+0x26c6d) [0x426c6d]
    (EE)
    I can run i3 (no compositing) without such problems though, in fact I'm posting from it right now...
    EDIT:
    I forgot one further problem.
    On shutdown/reboot the system hangs, as mentioned here
    So, has anyone else got some or all of these issues, knows of any solutions?
    Last edited by hungerfish (2012-11-19 13:07:04)

    So, finally some success - problem now is I don't know what actually solved it.
    I managed to get Shared folders to work!!
    Now either this just started working after the last kernel upgrade (3.6.6-1 -> 3.6.7-1) OR It's down to this small configuration detail I took away from your config p0x8!!!
    I noticed you were giving the name of your share (.host:/docs, whereas I was omitting it. Adding the correct name resulted in me being able to access my shared folder.
    For completeness:
    $ cat /etc/systemd/system/mnt-hgfs.automount
    [Unit]
    Description=Load VMware shared folders
    ConditionPathExists=.host:/Shared
    [Automount]
    Where=/mnt/hgfs
    [Install]
    WantedBy=multi-user.target
    $ cat /etc/systemd/system/mnt-hgfs.mount
    [Unit]
    Description=Load VMware shared folders
    ConditionPathExists=.host:/Shared
    [Mount]
    What=.host:/Shared
    Where=/mnt/hgfs
    Type=vmhgfs
    #Options=defaults,noatime
    Options=uid=1000,gid=100,fmask=0113,dmask=0022,permissions,nodev,nosuid,exec,nls=utf8,noatime
    [Install]
    WantedBy=multi-user.target
    Maybe I'll downgrade the kernel just to see if it still works, but if that's not the case, this is a bug, as I can omit the Shared folder's name in an ubuntu-guest for instance.
    Thanks again for trying this out p0x8!!
    UPDATE:
    I went ahead and downgraded the kernel, and can now confirm that the problem was down to this configuration issue, not the kernel.
    The issues remaining are gnome3's shell is broken, I am forced to use fallback-mode (great that its still around imho, because things DO break), the latest update to xorg-server and xorg-server-common cause X to crash instantly(version 1.13.1-1 works), and the shut-down delay.(see a few posts down)
    Last edited by hungerfish (2012-12-18 18:31:23)

Maybe you are looking for

  • How can I prevent my iPhone from making calls on its own?

    I often put my iPhone in my pocket. Sometimes I then discover that it is making calls on its own. How can I prevent this? Thanks.

  • Advice on A3 office/graphics grade printers/copiers

    I work for an architects firm and we've had quite a bad experience with A3 copiers/printers. One of our main problems is that we share our machine with a Quantity Surveyor; they need fast warm-up/fast print/black and white. And we need colour. These

  • Resolution issue on Panasonic Plasma HD 1080p with ATV

    With my ATV2 set to Auto resolution or 720pHD, I lose picture on the left and right of my 58" Panasonic plasma HD 1080p TV.  If I reset the resolution to 640x480, I regain the full image, but of course at lower resolution.  Apple Genius was of no hel

  • MS Word crashes when I do find/replace with the OS X 10.5.6

    Does anyone know what I can do about MS Word crashing when I do a find and/or replace in a document? It happens constantly. The interesting thing is that is doesn't occur every single time I do find/replace but the SECOND time I use the feature. The

  • What IOS do I need for SSH and VPN

    Greetings, I am not a Cisco expert but can muddle my way thru configurations. I have inherited my position from someone else who setup our VPN infrastructure long ago. Problem is that we have added a new location and I have been asked to add it to ou