Failed to start org.freedesktop.Avahi

Every time during boot i see a message:
dbus[725]    [system] Failed to activate service 'org.freedesktop.Avahi': timed out
What cause that service failed to start? Why it is trying to be loaded? Should be?
My system is msi wind u100 with arch and recent updates:
Linux msi 3.0-ARCH #1 SMP PREEMPT Sat Aug 6 16:49:00 CEST 2011 i686 Intel(R) Atom(TM) CPU N270 @ 1.60GHz GenuineIntel GNU/Linux
rc.conf content, if it's relevant:
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="pl_PL.UTF-8"
HARDWARECLOCK="localtime"
USEDIRECTISA="no"
TIMEZONE="Europe/Warsaw"
KEYMAP="pl"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(uvcvideo acpi_cpufreq cpufreq_ondemand cpufreq_powersave !ati_remote !lirc_atiusb)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="msi"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
#eth0="dhcp"
INTERFACES=(eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng dbus hal crond bluetooth alsa wicd !samba kdm !cups !lircd)
Last edited by bagheera (2011-08-14 08:48:29)

bagheera wrote:
karol wrote:You're still using the old rc.conf setup - why? You're blacklisting modules in rc.conf, even though it doesn't work anymore.
#MOD_BLACKLIST=() #deprecated
It's commented out, so it doesn't matter
I was talking about
MODULES=(uvcvideo acpi_cpufreq cpufreq_ondemand cpufreq_powersave !ati_remote !lirc_atiusb)
http://www.archlinux.org/news/changes-t … cklisting/
Before this change you could
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.

Similar Messages

  • Gkr-Message: secret service operation failed: The name org.freedesktop

    When I run svn update in my terminal window, I get lots of these errors..:
    Gkr-Message: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files
    What is this and how do I remove the error?
    Regards,
    BTJ

    If you dont want to store your passwords on harddisk, you can disable it by edit the following lines in ~/.subversion/config
    password-stores =
    store-passwords = no
    Last edited by Corubba (2011-10-31 10:52:51)

  • [SOLVED] apache daemon fails to start on boot, but rc.d restart works?

    I installed apache from the official repos and followed the instructions in the wiki for configuring it. I checked to make sure the http user exists, and I /etc/hosts looks good (to me). Upon boot, the daemon fails to start and I can't load local web pages, but running "rc.d restart httpd" works just fine. Since I'd rather not start it manually every time I boot, is there a way to fix this? Also, httpd is the last daemon in my DAEMONS array.
    /etc/httpd/conf/httpd.conf:
    # This is the main Apache HTTP server configuration file. It contains the
    # configuration directives that give the server its instructions.
    # See <URL:http://httpd.apache.org/docs/2.2> for detailed information.
    # In particular, see
    # <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
    # for a discussion of each configuration directive.
    # Do NOT simply read the instructions in here without understanding
    # what they do. They're here only as hints or reminders. If you are unsure
    # consult the online docs. You have been warned.
    # Configuration and logfile names: If the filenames you specify for many
    # of the server's control files begin with "/" (or "drive:/" for Win32), the
    # server will use that explicit path. If the filenames do *not* begin
    # with "/", the value of ServerRoot is prepended -- so "/var/log/httpd/foo_log"
    # with ServerRoot set to "/etc/httpd" will be interpreted by the
    # server as "/etc/httpd//var/log/httpd/foo_log".
    # ServerRoot: The top of the directory tree under which the server's
    # configuration, error, and log files are kept.
    # Do not add a slash at the end of the directory path. If you point
    # ServerRoot at a non-local disk, be sure to point the LockFile directive
    # at a local disk. If you wish to share the same ServerRoot for multiple
    # httpd daemons, you will need to change at least LockFile and PidFile.
    ServerRoot "/etc/httpd"
    # Listen: Allows you to bind Apache to specific IP addresses and/or
    # ports, instead of the default. See also the <VirtualHost>
    # directive.
    # Change this to Listen on specific IP addresses as shown below to
    # prevent Apache from glomming onto all bound IP addresses.
    #Listen 12.34.56.78:80
    Listen 127.0.0.1:80
    # Dynamic Shared Object (DSO) Support
    # To be able to use the functionality of a module which was built as a DSO you
    # have to place corresponding `LoadModule' lines at this location so the
    # directives contained in it are actually available _before_ they are used.
    # Statically compiled modules (those listed by `httpd -l') do not need
    # to be loaded here.
    # Example:
    # LoadModule foo_module modules/mod_foo.so
    LoadModule authn_file_module modules/mod_authn_file.so
    LoadModule authn_dbm_module modules/mod_authn_dbm.so
    LoadModule authn_anon_module modules/mod_authn_anon.so
    LoadModule authn_dbd_module modules/mod_authn_dbd.so
    LoadModule authn_default_module modules/mod_authn_default.so
    LoadModule authz_host_module modules/mod_authz_host.so
    LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
    LoadModule authz_user_module modules/mod_authz_user.so
    LoadModule authz_dbm_module modules/mod_authz_dbm.so
    LoadModule authz_owner_module modules/mod_authz_owner.so
    LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
    LoadModule authz_default_module modules/mod_authz_default.so
    LoadModule auth_basic_module modules/mod_auth_basic.so
    LoadModule auth_digest_module modules/mod_auth_digest.so
    LoadModule file_cache_module modules/mod_file_cache.so
    LoadModule cache_module modules/mod_cache.so
    LoadModule disk_cache_module modules/mod_disk_cache.so
    LoadModule mem_cache_module modules/mod_mem_cache.so
    LoadModule dbd_module modules/mod_dbd.so
    LoadModule dumpio_module modules/mod_dumpio.so
    LoadModule reqtimeout_module modules/mod_reqtimeout.so
    LoadModule ext_filter_module modules/mod_ext_filter.so
    LoadModule include_module modules/mod_include.so
    LoadModule filter_module modules/mod_filter.so
    LoadModule substitute_module modules/mod_substitute.so
    LoadModule deflate_module modules/mod_deflate.so
    LoadModule ldap_module modules/mod_ldap.so
    LoadModule log_config_module modules/mod_log_config.so
    LoadModule log_forensic_module modules/mod_log_forensic.so
    LoadModule logio_module modules/mod_logio.so
    LoadModule env_module modules/mod_env.so
    LoadModule mime_magic_module modules/mod_mime_magic.so
    LoadModule cern_meta_module modules/mod_cern_meta.so
    LoadModule expires_module modules/mod_expires.so
    LoadModule headers_module modules/mod_headers.so
    LoadModule ident_module modules/mod_ident.so
    LoadModule usertrack_module modules/mod_usertrack.so
    #LoadModule unique_id_module modules/mod_unique_id.so
    LoadModule setenvif_module modules/mod_setenvif.so
    LoadModule version_module modules/mod_version.so
    LoadModule proxy_module modules/mod_proxy.so
    LoadModule proxy_connect_module modules/mod_proxy_connect.so
    LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
    LoadModule proxy_http_module modules/mod_proxy_http.so
    LoadModule proxy_scgi_module modules/mod_proxy_scgi.so
    LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
    LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
    LoadModule ssl_module modules/mod_ssl.so
    LoadModule mime_module modules/mod_mime.so
    LoadModule dav_module modules/mod_dav.so
    LoadModule status_module modules/mod_status.so
    LoadModule autoindex_module modules/mod_autoindex.so
    LoadModule asis_module modules/mod_asis.so
    LoadModule info_module modules/mod_info.so
    LoadModule suexec_module modules/mod_suexec.so
    LoadModule cgi_module modules/mod_cgi.so
    LoadModule cgid_module modules/mod_cgid.so
    LoadModule dav_fs_module modules/mod_dav_fs.so
    LoadModule vhost_alias_module modules/mod_vhost_alias.so
    LoadModule negotiation_module modules/mod_negotiation.so
    LoadModule dir_module modules/mod_dir.so
    LoadModule imagemap_module modules/mod_imagemap.so
    LoadModule actions_module modules/mod_actions.so
    LoadModule speling_module modules/mod_speling.so
    LoadModule userdir_module modules/mod_userdir.so
    LoadModule alias_module modules/mod_alias.so
    LoadModule rewrite_module modules/mod_rewrite.so
    #php
    LoadModule php5_module modules/libphp5.so
    <IfModule !mpm_netware_module>
    <IfModule !mpm_winnt_module>
    # If you wish httpd to run as a different user or group, you must run
    # httpd as root initially and it will switch.
    # User/Group: The name (or #number) of the user/group to run httpd as.
    # It is usually good practice to create a dedicated user and group for
    # running httpd, as with most system services.
    User http
    Group http
    </IfModule>
    </IfModule>
    # 'Main' server configuration
    # The directives in this section set up the values used by the 'main'
    # server, which responds to any requests that aren't handled by a
    # <VirtualHost> definition. These values also provide defaults for
    # any <VirtualHost> containers you may define later in the file.
    # All of these directives may appear inside <VirtualHost> containers,
    # in which case these default settings will be overridden for the
    # virtual host being defined.
    # ServerAdmin: Your address, where problems with the server should be
    # e-mailed. This address appears on some server-generated pages, such
    # as error documents. e.g. [email protected]
    ServerAdmin [email protected]
    # ServerName gives the name and port that the server uses to identify itself.
    # This can often be determined automatically, but we recommend you specify
    # it explicitly to prevent problems during startup.
    # If your host doesn't have a registered DNS name, enter its IP address here.
    #ServerName www.example.com:80
    # DocumentRoot: The directory out of which you will serve your
    # documents. By default, all requests are taken from this directory, but
    # symbolic links and aliases may be used to point to other locations.
    DocumentRoot "/srv/http"
    # Each directory to which Apache has access can be configured with respect
    # to which services and features are allowed and/or disabled in that
    # directory (and its subdirectories).
    # First, we configure the "default" to be a very restrictive set of
    # features.
    <Directory />
    Options FollowSymLinks
    AllowOverride None
    Order deny,allow
    Deny from all
    </Directory>
    # Note that from this point forward you must specifically allow
    # particular features to be enabled - so if something's not working as
    # you might expect, make sure that you have specifically enabled it
    # below.
    # This should be changed to whatever you set DocumentRoot to.
    <Directory "/srv/http">
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    # Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    # The Options directive is both complicated and important. Please see
    # http://httpd.apache.org/docs/2.2/mod/core.html#options
    # for more information.
    Options Indexes FollowSymLinks
    # AllowOverride controls what directives may be placed in .htaccess files.
    # It can be "All", "None", or any combination of the keywords:
    # Options FileInfo AuthConfig Limit
    AllowOverride None
    # Controls who can get stuff from this server.
    Order allow,deny
    Allow from all
    </Directory>
    # DirectoryIndex: sets the file that Apache will serve if a directory
    # is requested.
    <IfModule dir_module>
    DirectoryIndex index.html
    </IfModule>
    # The following lines prevent .htaccess and .htpasswd files from being
    # viewed by Web clients.
    <FilesMatch "^\.ht">
    Order allow,deny
    Deny from all
    Satisfy All
    </FilesMatch>
    # ErrorLog: The location of the error log file.
    # If you do not specify an ErrorLog directive within a <VirtualHost>
    # container, error messages relating to that virtual host will be
    # logged here. If you *do* define an error logfile for a <VirtualHost>
    # container, that host's errors will be logged there and not here.
    ErrorLog "/var/log/httpd/error_log"
    # LogLevel: Control the number of messages logged to the error_log.
    # Possible values include: debug, info, notice, warn, error, crit,
    # alert, emerg.
    LogLevel warn
    <IfModule log_config_module>
    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
    LogFormat "%h %l %u %t \"%r\" %>s %b" common
    <IfModule logio_module>
    # You need to enable mod_logio.c to use %I and %O
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
    </IfModule>
    # The location and format of the access logfile (Common Logfile Format).
    # If you do not define any access logfiles within a <VirtualHost>
    # container, they will be logged here. Contrariwise, if you *do*
    # define per-<VirtualHost> access logfiles, transactions will be
    # logged therein and *not* in this file.
    CustomLog "/var/log/httpd/access_log" common
    # If you prefer a logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    #CustomLog "/var/log/httpd/access_log" combined
    </IfModule>
    <IfModule alias_module>
    # Redirect: Allows you to tell clients about documents that used to
    # exist in your server's namespace, but do not anymore. The client
    # will make a new request for the document at its new location.
    # Example:
    # Redirect permanent /foo http://www.example.com/bar
    # Alias: Maps web paths into filesystem paths and is used to
    # access content that does not live under the DocumentRoot.
    # Example:
    # Alias /webpath /full/filesystem/path
    # If you include a trailing / on /webpath then the server will
    # require it to be present in the URL. You will also likely
    # need to provide a <Directory> section to allow access to
    # the filesystem path.
    # ScriptAlias: This controls which directories contain server scripts.
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the target directory are treated as applications and
    # run by the server when requested rather than as documents sent to the
    # client. The same rules about trailing "/" apply to ScriptAlias
    # directives as to Alias.
    ScriptAlias /cgi-bin/ "/srv/http/cgi-bin/"
    </IfModule>
    <IfModule cgid_module>
    # ScriptSock: On threaded servers, designate the path to the UNIX
    # socket used to communicate with the CGI daemon of mod_cgid.
    #Scriptsock /var/run/httpd/cgisock
    </IfModule>
    # "/srv/http/cgi-bin" should be changed to whatever your ScriptAliased
    # CGI directory exists, if you have that configured.
    <Directory "/srv/http/cgi-bin">
    AllowOverride None
    Options None
    Order allow,deny
    Allow from all
    </Directory>
    # DefaultType: the default MIME type the server will use for a document
    # if it cannot otherwise determine one, such as from filename extensions.
    # If your server contains mostly text or HTML documents, "text/plain" is
    # a good value. If most of your content is binary, such as applications
    # or images, you may want to use "application/octet-stream" instead to
    # keep browsers from trying to display binary files as though they are
    # text.
    DefaultType text/plain
    <IfModule mime_module>
    # TypesConfig points to the file containing the list of mappings from
    # filename extension to MIME-type.
    TypesConfig conf/mime.types
    # AddType allows you to add to or override the MIME configuration
    # file specified in TypesConfig for specific file types.
    #AddType application/x-gzip .tgz
    # AddEncoding allows you to have certain browsers uncompress
    # information on the fly. Note: Not all browsers support this.
    #AddEncoding x-compress .Z
    #AddEncoding x-gzip .gz .tgz
    # If the AddEncoding directives above are commented-out, then you
    # probably should define those extensions to indicate media types:
    AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz
    # AddHandler allows you to map certain file extensions to "handlers":
    # actions unrelated to filetype. These can be either built into the server
    # or added with the Action directive (see below)
    # To use CGI scripts outside of ScriptAliased directories:
    # (You will also need to add "ExecCGI" to the "Options" directive.)
    #AddHandler cgi-script .cgi
    # For type maps (negotiated resources):
    #AddHandler type-map var
    # Filters allow you to process content before it is sent to the client.
    # To parse .shtml files for server-side includes (SSI):
    # (You will also need to add "Includes" to the "Options" directive.)
    #AddType text/html .shtml
    #AddOutputFilter INCLUDES .shtml
    </IfModule>
    # The mod_mime_magic module allows the server to use various hints from the
    # contents of the file itself to determine its type. The MIMEMagicFile
    # directive tells the module where the hint definitions are located.
    MIMEMagicFile conf/magic
    # Customizable error responses come in three flavors:
    # 1) plain text 2) local redirects 3) external redirects
    # Some examples:
    #ErrorDocument 500 "The server made a boo boo."
    #ErrorDocument 404 /missing.html
    #ErrorDocument 404 "/cgi-bin/missing_handler.pl"
    #ErrorDocument 402 http://www.example.com/subscription_info.html
    # MaxRanges: Maximum number of Ranges in a request before
    # returning the entire resource, or one of the special
    # values 'default', 'none' or 'unlimited'.
    # Default setting is to accept 200 Ranges.
    #MaxRanges unlimited
    # EnableMMAP and EnableSendfile: On systems that support it,
    # memory-mapping or the sendfile syscall is used to deliver
    # files. This usually improves server performance, but must
    # be turned off when serving from networked-mounted
    # filesystems or if support for these functions is otherwise
    # broken on your system.
    #EnableMMAP off
    #EnableSendfile off
    # Supplemental configuration
    # The configuration files in the conf/extra/ directory can be
    # included to add extra features or to modify the default configuration of
    # the server, or you may simply copy their contents here and change as
    # necessary.
    # Server-pool management (MPM specific)
    #Include conf/extra/httpd-mpm.conf
    # Multi-language error messages
    Include conf/extra/httpd-multilang-errordoc.conf
    # Fancy directory listings
    Include conf/extra/httpd-autoindex.conf
    # Language settings
    Include conf/extra/httpd-languages.conf
    # User home directories
    Include conf/extra/httpd-userdir.conf
    # Real-time info on requests and configuration
    #Include conf/extra/httpd-info.conf
    # Virtual hosts
    #Include conf/extra/httpd-vhosts.conf
    # Local access to the Apache HTTP Server Manual
    #Include conf/extra/httpd-manual.conf
    # Distributed authoring and versioning (WebDAV)
    #Include conf/extra/httpd-dav.conf
    # Various default settings
    Include conf/extra/httpd-default.conf
    # Secure (SSL/TLS) connections
    #Include conf/extra/httpd-ssl.conf
    #PHP
    Include conf/extra/php5_module.conf
    # Note: The following must must be present to support
    # starting without SSL on platforms with no /dev/random equivalent
    # but a statically compiled-in mod_ssl.
    <IfModule ssl_module>
    SSLRandomSeed startup builtin
    SSLRandomSeed connect builtin
    </IfModule>
    /etc/hosts
    # /etc/hosts: static lookup table for host names
    #<ip-address> <hostname.domain.org> <hostname>
    127.0.0.1 localhost.localdomain localhost laptop
    ::1 localhost.localdomain localhost
    # End of file
    Per the wiki, I also tried commenting out the line that reads
    LoadModule unique_id_module modules/mod_unique_id.so
    Either way, it still fails on boot.
    Last edited by pythonscript (2012-06-10 21:14:44)

    The SIGTERM are from reboots, yes. I'm not absolutely sure that the process isn't running; I just know that I can't access http://localhost immediately upon reboot. I have to restart the httpd daemon, which works fine. How would I be able to tell if it's just hung?
    I checked everything.log, and I don't see anything that leaps off the page to me.
    Jun 9 22:29:30 localhost rtkit-daemon[1910]: Successfully made thread 1930 of process 1908 (/usr/bin/pulseaudio) owned by '120' RT at priority 5.
    Jun 9 22:29:30 localhost rtkit-daemon[1910]: Supervising 2 threads of 1 processes of 1 users.
    Jun 9 22:29:30 localhost rtkit-daemon[1910]: Successfully made thread 1931 of process 1908 (/usr/bin/pulseaudio) owned by '120' RT at priority 5.
    Jun 9 22:29:30 localhost rtkit-daemon[1910]: Supervising 3 threads of 1 processes of 1 users.
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Presence interface=org.freedesktop.DBus.Properties method=GetAll
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager interface=org.freedesktop.DBus.Properties method=GetAll
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager interface=org.gnome.SessionManager method=RegisterClient
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: RegisterClient 106d33cade29b1ba713392593689729000000018320001
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: Adding new client 106d33cade29b1ba713392593689729000000018320001 to session
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): uid = 120
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): pid = 1842
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmStore: Adding object id /org/gnome/SessionManager/Client2 to store
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: Client added: /org/gnome/SessionManager/Client2
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): App gnome-settings-daemon.desktop registered
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase INITIALIZATION
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting phase WINDOW_MANAGER
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase WINDOW_MANAGER
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting phase PANEL
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase PANEL
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting phase DESKTOP
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase DESKTOP
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting phase APPLICATION
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting app '/org/gnome/SessionManager/App1'
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): Starting app: /org/gnome/SessionManager/App1
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmAutostartApp: starting gnome-shell.desktop: command=gnome-shell --gdm-mode startup-id=106d33cade29b1ba713392593689681600000018320000
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmAutostartApp: started pid:1936
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase APPLICATION
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting phase RUNNING
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmPresence: adding idle watch
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GSIdleMonitor: creating new alarm for positive transition wait=600000
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GSIdleMonitor: creating new alarm for negative transition wait=599999
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Client2 interface=org.freedesktop.DBus.Properties method=GetAll
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Client2 interface=org.freedesktop.DBus.Properties method=GetAll
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmShell: Connected to the shell
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:31 localhost kernel: [ 29.003352] wlan0: no IPv6 routers present
    Jun 9 17:29:31 localhost NetworkManager[765]: <warn> could not commit DNS changes: (0) Could not replace /etc/resolv.conf: Operation not permitted
    Jun 9 17:29:31 localhost NetworkManager[765]: <info> Policy set 'Wired connection 1' (eth0) as default for IPv4 routing and DNS.
    Jun 9 17:29:31 localhost NetworkManager[765]: <info> (wlan0): device state change: ip-config -> activated (reason 'none') [70 100 0]
    Jun 9 17:29:31 localhost NetworkManager[765]: <info> Activation (wlan0) successful, device activated.
    Jun 9 17:29:31 localhost NetworkManager[765]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXsmpServer: accept_ice_connection()
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXsmpServer: auth_ice_connection()
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Setting up new connection
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: New client '0x7f9ff0004e60 []'
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmStore: Adding object id /org/gnome/SessionManager/Client3 to store
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmManager: Client added: /org/gnome/SessionManager/Client3
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Initializing client 0x7f9ff0004e60 []
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Client '0x7f9ff0004e60 []' received RegisterClient(106d33cade29b1ba713392593689681600000018320000)
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmManager: Adding new client 106d33cade29b1ba713392593689681600000018320000 to session
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Sending RegisterClientReply to '0x7f9ff0004e60 [106d33cade29b1ba713392593689681600000018320000]'
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Set properties from client '0x7f9ff0004e60 [106d33cade29b1ba713392593689681600000018320000]'
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Program = 'gnome-shell'
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: UserID = 'gdm'
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: RestartStyleHint = 0
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: ProcessID = '1936'
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: CurrentDirectory = '/var/lib/gdm'
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: _GSM_Priority = 20
    Jun 9 17:29:31 localhost dhcpcd[1640]: eth0: sending IPv6 Router Solicitation
    Jun 9 17:29:31 localhost dhcpcd[1640]: eth0: no IPv6 Routers available
    Jun 9 17:29:33 localhost dhcpcd[1677]: wlan0: sending IPv6 Router Solicitation
    Jun 9 17:29:33 localhost dhcpcd[1677]: wlan0: no IPv6 Routers available
    Jun 9 17:29:33 localhost NetworkManager[765]: <warn> error monitoring device for netlink events: error processing netlink message: Object busy
    Jun 9 17:29:34 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Presence interface=org.freedesktop.DBus.Properties method=GetAll
    Jun 9 17:29:34 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Presence interface=org.freedesktop.DBus.Properties method=GetAll
    Jun 9 17:29:34 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:34 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:34 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Presence interface=org.freedesktop.DBus.Properties method=GetAll
    Jun 9 17:29:34 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Presence interface=org.freedesktop.DBus.Properties method=GetAll
    Jun 9 17:29:35 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:35 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:40 localhost NetworkManager[765]: <info> (eth0): IP6 addrconf timed out or failed.
    Jun 9 17:29:40 localhost NetworkManager[765]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
    Jun 9 17:29:40 localhost NetworkManager[765]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) started...
    Jun 9 17:29:40 localhost NetworkManager[765]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
    Jun 9 17:29:41 localhost NetworkManager[765]: <info> (wlan0): IP6 addrconf timed out or failed.
    Jun 9 17:29:41 localhost NetworkManager[765]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
    Jun 9 17:29:41 localhost NetworkManager[765]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started...
    Jun 9 17:29:41 localhost NetworkManager[765]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GdmSignalHandler: handling signal 15
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GdmSignalHandler: Found 1 callbacks
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GdmSignalHandler: running 15 handler: 0x41c9e0
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): Got callback for signal 15
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Logout called
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmShell: Connected to the shell
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: requesting logout
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase RUNNING
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting phase QUERY_END_SESSION
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Client /org/gnome/SessionManager/Client1
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Client /org/gnome/SessionManager/Client2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Client /org/gnome/SessionManager/Client3
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: sending query-end-session to clients (logout mode: forceful)
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: sending QueryEndSession signal to :1.8
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: adding client to query clients: /org/gnome/SessionManager/Client1
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: sending QueryEndSession signal to :1.2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: adding client to query clients: /org/gnome/SessionManager/Client2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: adding client to query clients: /org/gnome/SessionManager/Client3
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): Caught signal 15, shutting down normally.
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GdmSignalHandler: Done handling signals
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Client '0x7f9ff0004e60 [gnome-shell 106d33cade29b1ba713392593689681600000018320000]' received SaveYourselfDone(success = True)
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Response from end session request: is-ok=1 do-last=0 cancel=0 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmXsmpServer: sms_error_handler (0x1491c70, FALSE, 3, 9, 32771, 0)
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Client1 interface=org.gnome.SessionManager.ClientPrivate method=EndSessionResponse
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: got EndSessionResponse is-ok:1 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Response from end session request: is-ok=1 do-last=0 cancel=0 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Client2 interface=org.gnome.SessionManager.ClientPrivate method=EndSessionResponse
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Client2 interface=org.gnome.SessionManager.ClientPrivate method=EndSessionResponse
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: got EndSessionResponse is-ok:1 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Response from end session request: is-ok=1 do-last=0 cancel=0 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: query end session complete
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmShell: Connected to the shell
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase QUERY_END_SESSION
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting phase END_SESSION
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: adding client to end-session clients: /org/gnome/SessionManager/Client1
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: adding client to end-session clients: /org/gnome/SessionManager/Client2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: adding client to end-session clients: /org/gnome/SessionManager/Client3
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Client '0x7f9ff0004e60 [gnome-shell 106d33cade29b1ba713392593689681600000018320000]' received SaveYourselfDone(success = True)
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Response from end session request: is-ok=1 do-last=0 cancel=0 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Client1 interface=org.gnome.SessionManager.ClientPrivate method=EndSessionResponse
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: got EndSessionResponse is-ok:1 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Response from end session request: is-ok=1 do-last=0 cancel=0 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmXsmpServer: sms_error_handler (0x1491c70, FALSE, 3, c, 32771, 0)
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: disconnect client: /org/gnome/SessionManager/Client1
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: disconnect for app 'at-spi-registryd.desktop'
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: unable to find application for client - not restarting
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: Unreffing object: 0x1428a40
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmClient: disposing /org/gnome/SessionManager/Client1
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: emitting removed for /org/gnome/SessionManager/Client1
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Client removed: /org/gnome/SessionManager/Client1
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Client2 interface=org.gnome.SessionManager.ClientPrivate method=EndSessionResponse
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: got EndSessionResponse is-ok:1 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Response from end session request: is-ok=1 do-last=0 cancel=0 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase END_SESSION
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): Using ConsoleKit for session tracking
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting phase EXIT
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: stopped client: /org/gnome/SessionManager/Client2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: xsmp_stop ('0x7f9ff0004e60 [gnome-shell 106d33cade29b1ba713392593689681600000018320000]')
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: stopped client: /org/gnome/SessionManager/Client3
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Client '0x7f9ff0004e60 [gnome-shell 106d33cade29b1ba713392593689681600000018320000]' received CloseConnection
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: disconnect client
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: disconnect client: /org/gnome/SessionManager/Client3
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: in shutdown, not restarting application
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: Unreffing object: 0x7f9ff0004e60
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Client removed: /org/gnome/SessionManager/Client3
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmClient: disposing /org/gnome/SessionManager/Client3
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: xsmp_finalize (0x7f9ff0004e60 [gnome-shell 106d33cade29b1ba713392593689681600000018320000])
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: disconnect client: /org/gnome/SessionManager/Client2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: in shutdown, not restarting application
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: Unreffing object: 0x1428ac0
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmClient: disposing /org/gnome/SessionManager/Client2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: emitting removed for /org/gnome/SessionManager/Client2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Client removed: /org/gnome/SessionManager/Client2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: last client disconnected - exiting
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase EXIT
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): Unreffing manager
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: disposing manager
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: Clearing object store
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: Unreffing object: 0x1473070
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: Unreffing object: 0x1473150
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: emitting removed for /org/gnome/SessionManager/App2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: emitting removed for /org/gnome/SessionManager/App1
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: Clearing object store
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: Clearing object store
    Jun 9 17:29:42 localhost gdm-simple-slave[1728]: WARNING: Child process 1832 was already dead.
    Jun 9 17:29:43 localhost gnome-session[1970]: EggSMClient-WARNING: Desktop file '/home/ak5791/.config/autostart/dropbox.desktop' has malformed Icon key 'dropbox.png'(should not include extension)
    Jun 9 22:29:43 localhost rtkit-daemon[1910]: Successfully made thread 2022 of process 2022 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
    Jun 9 22:29:43 localhost rtkit-daemon[1910]: Supervising 4 threads of 2 processes of 2 users.
    Jun 9 22:29:43 localhost rtkit-daemon[1910]: Successfully made thread 2023 of process 2022 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
    Jun 9 22:29:43 localhost rtkit-daemon[1910]: Supervising 5 threads of 2 processes of 2 users.
    Jun 9 22:29:43 localhost rtkit-daemon[1910]: Successfully made thread 2024 of process 2022 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
    Jun 9 22:29:43 localhost rtkit-daemon[1910]: Supervising 6 threads of 2 processes of 2 users.
    Jun 9 17:29:44 localhost dbus[739]: [system] Activating service name='org.freedesktop.ColorManager' (using servicehelper)
    Jun 9 17:29:44 localhost dbus[739]: [system] Successfully activated service 'org.freedesktop.ColorManager'
    Jun 9 17:29:44 localhost dbus[739]: [system] Activating service name='org.freedesktop.colord-sane' (using servicehelper)
    Jun 9 17:29:45 localhost dbus[739]: [system] Successfully activated service 'org.freedesktop.colord-sane'
    Jun 9 22:29:46 localhost rtkit-daemon[1910]: Successfully made thread 2079 of process 2079 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
    Jun 9 22:29:46 localhost rtkit-daemon[1910]: Supervising 7 threads of 3 processes of 2 users.
    Jun 9 17:29:46 localhost pulseaudio[2079]: [pulseaudio] pid.c: Daemon already running.
    Jun 9 17:29:48 localhost dbus[739]: [system] Activating service name='org.freedesktop.UDisks2' (using servicehelper)
    Jun 9 17:29:48 localhost udisksd[2110]: udisks daemon version 1.94.0 starting
    Jun 9 17:29:48 localhost dbus[739]: [system] Successfully activated service 'org.freedesktop.UDisks2'
    Jun 9 17:29:48 localhost udisksd[2110]: Acquired the name org.freedesktop.UDisks2 on the system message bus
    Jun 9 17:29:48 localhost kernel: [ 46.319778] gnome-shell-cal[2103] trap int3 ip:7ff3f55b85e1 sp:7fff94941890 error:0
    Jun 9 17:30:19 localhost dbus[739]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out
    Jun 9 22:40:53 localhost dbus[739]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out
    Jun 9 22:47:15 localhost kernel: [ 1092.983585] usb 8-1.4.1: new high-speed USB device number 8 using ehci_hcd
    Jun 9 22:47:15 localhost mtp-probe: checking bus 8, device 8: "/sys/devices/pci0000:00/0000:00:1d.7/usb8/8-1/8-1.4/8-1.4.1"
    Jun 9 22:47:15 localhost mtp-probe: bus: 8, device: 8 was not an MTP device
    Jun 9 22:47:15 localhost kernel: [ 1093.132002] usbcore: registered new interface driver uas
    Jun 9 22:47:15 localhost kernel: [ 1093.135601] Initializing USB Mass Storage driver...
    Jun 9 22:47:15 localhost kernel: [ 1093.135785] scsi6 : usb-storage 8-1.4.1:1.0
    Jun 9 22:47:15 localhost kernel: [ 1093.135905] usbcore: registered new interface driver usb-storage
    Jun 9 22:47:15 localhost kernel: [ 1093.135913] USB Mass Storage support registered.
    Jun 9 22:47:16 localhost kernel: [ 1094.137579] scsi 6:0:0:0: Direct-Access Kingston DT 101 G2 1.00 PQ: 0 ANSI: 2
    Jun 9 22:47:16 localhost kernel: [ 1094.140133] sd 6:0:0:0: [sdb] 15636304 512-byte logical blocks: (8.00 GB/7.45 GiB)
    Jun 9 22:47:16 localhost kernel: [ 1094.140631] sd 6:0:0:0: [sdb] Write Protect is off
    Jun 9 22:47:16 localhost kernel: [ 1094.140634] sd 6:0:0:0: [sdb] Mode Sense: 03 00 00 00
    Jun 9 22:47:16 localhost kernel: [ 1094.141128] sd 6:0:0:0: [sdb] No Caching mode page present
    Jun 9 22:47:16 localhost kernel: [ 1094.141132] sd 6:0:0:0: [sdb] Assuming drive cache: write through
    Jun 9 22:47:16 localhost kernel: [ 1094.144916] sd 6:0:0:0: [sdb] No Caching mode page present
    Jun 9 22:47:16 localhost kernel: [ 1094.144921] sd 6:0:0:0: [sdb] Assuming drive cache: write through
    Jun 9 22:47:16 localhost kernel: [ 1094.146680] sdb: sdb1
    Jun 9 22:47:16 localhost kernel: [ 1094.151407] sd 6:0:0:0: [sdb] No Caching mode page present
    Jun 9 22:47:16 localhost kernel: [ 1094.151411] sd 6:0:0:0: [sdb] Assuming drive cache: write through
    Jun 9 22:47:16 localhost kernel: [ 1094.151414] sd 6:0:0:0: [sdb] Attached SCSI removable disk
    Jun 9 22:47:17 localhost ntfs-3g[2636]: Version 2012.1.15 external FUSE 29
    Jun 9 22:47:17 localhost ntfs-3g[2636]: Mounted /dev/sdb1 (Read-Write, label "kingstonGB", NTFS 3.1)
    Jun 9 22:47:17 localhost ntfs-3g[2636]: Cmdline options: rw,nodev,nosuid,uid=1000,gid=100,dmask=0077,fmask=0177,uhelper=udisks2
    Jun 9 22:47:17 localhost ntfs-3g[2636]: Mount options: rw,nodev,nosuid,uhelper=udisks2,allow_other,nonempty,relatime,fsname=/dev/sdb1,blkdev,blksize=4096,default_permissions
    Jun 9 22:47:17 localhost ntfs-3g[2636]: Global ownership and permissions enforced, configuration type 7
    Jun 9 22:47:17 localhost udisksd[2110]: Mounted /dev/sdb1 at /run/media/ak5791/kingstonGB on behalf of uid 1000
    Jun 9 22:47:28 localhost dbus[739]: [system] Activating service name='org.freedesktop.UDisks' (using servicehelper)
    Jun 9 22:47:28 localhost dbus[739]: [system] Successfully activated service 'org.freedesktop.UDisks'
    Jun 9 22:47:46 localhost dbus[739]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out
    Jun 9 22:57:59 localhost dbus[739]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out
    Jun 9 23:01:02 localhost /USR/SBIN/CROND[5529]: (root) CMD (run-parts /etc/cron.hourly)
    Jun 9 23:21:02 localhost -- MARK --
    All I notice is that my system's time is having a few problems, since you'll notice that events occur at 22:00 and change, then 17:00 and change, then back to 22:00 and change afterwards. Could this be the problem? I've had the CMOS batteries peg out on me suddenly in the last few weeks. I would hope this sytem is not also suffering a similar fate. Nothing else was happening on my system except for the standard processes from /etc/rc.conf and other standard ones, since I've just been rebooting, checking the logs, then posting here.

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

  • [PARTIALLY SOLVED] HAL fails to start

    ** UPDATE: PARTIALLY SOLVED - SEE BOTTOM OF THE FIRST POST
    HAL fails to start. I'm not exactly sure why this is, but I believe it has something to do with my attempts to get automounting working under gnome.
    [zen@intellitech ~]$ sudo /etc/rc.d/hal start
    :: Starting Hardware Abstraction Layer [FAIL]
    [zen@intellitech ~]$ vim /etc/rc.conf
    MODULES=(acpi-cpufreq cpufreq_ondemand e1000 iwl4965 snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore thinkpad_acpi uinput vboxdrv)
    DAEMONS=(syslog-ng @network !net-profiles @net-auto @netfs !samba !crond @acpid @dbus @hal @alsa !daemoot !avahi-daemon @cups @ddclient @bluetooth)
    [zen@intellitech ~]$ pacman -Q | grep hal
    hal 0.5.11-1
    hal-info 0.20080508-1
    [zen@intellitech ~]$ /usr/sbin/hald --daemon=no --verbose=yes
    03:13:37.451 [i] hald.c:669: hal 0.5.11
    03:13:37.451 [i] hald.c:734: Will not daemonize
    03:13:37.451 [i] hald_dbus.c:5381: local server is listening at unix:abstract=/var/run/hald/dbus-pdtZvbqaVq,guid=312b47921cba4c5cdbee099a48ec87d1
    03:13:37.452 [E] ck-tracker.c:367: Error doing GetSeats on ConsoleKit: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ConsoleKit was not provided by any .service files
    03:13:37.452 [E] ck-tracker.c:792: Could not get seats and sessions
    03:13:37.452 [W] hald_dbus.c:5806: Could not initialize seats and sessions from ConsoleKit
    Runner started - allowed paths are '/usr/lib/hal:/usr/lib/hal/scripts:/usr/bin'
    03:13:37.453 [i] hald_runner.c:301: Runner has pid 3675
    03:13:37.453 [i] hald_runner.c:182: runner connection is 0x15bdec0
    03:13:37.456 [W] osspec.c:373: Unable to open /proc/mdstat: No such file or directory
    03:13:37.457 [D] util_helper.c:124: drop_privileges: could not set group id
    [zen@intellitech ~]$ vim /etc/group
    root::0:root
    bin::1:root,bin,daemon
    daemon::2:root,bin,daemon
    sys::3:root,bin
    adm::4:root,daemon
    tty::5:root,zen
    disk::6:root,zen
    lp::7:daemon
    mem::8:
    kmem::9:
    wheel::10:root,zen
    ftp::11:
    mail::12:
    log::19:root
    smmsp::25:
    games::50:
    network:x:90:zen
    video:x:91:zen
    audio::92:root,zen
    optical::93:root,zen
    floppy:x:94:root,zen
    storage:x:95:root,zen
    power:x:98:root,zen
    nobody::99:
    users::100:zen
    locate:x:21:
    uucp:x:14:
    http:x:33:
    scanner:x:96:
    dbus:x:81:root,zen
    hal:x:82:root,zen
    avahi:x:84:root,zen
    camera:x:97:
    gdm:x:101:
    vboxusers:x:108:zen
    samba:x:109:zen,root
    * Yes, I know it is bad practice to have a normal user listed under the disk group. It is necessary, however, in order to have raw disk access for virtual box.
    [zen@intellitech ~]$ sudo /etc/rc.d/dbus stop
    :: Stopping D-BUS system messagebus [DONE]
    [zen@intellitech ~]$ sudo /etc/rc.d/hal start
    :: Starting D-BUS system messagebus [DONE]
    :: Starting Hardware Abstraction Layer [FAIL]
    It's odd, because D-BUS will start but hal will not... Anybody have any suggestions?
    * UPDATE (10/08/08): Did a full system upgrade and removed dbus from daemons array in rc.conf. UDEV EVENTS Processing speed seems to be back to normal.
    ** SOLUTION UPDATE: After removing custom ntfs-3g fdi policies from /etc/hal/fdi/policy/, hal seems to load without any problems. This seems to be a bug, since my policies were working at one point, and I believe a hal update caused the problem. I'll see if I can track down the exact hal version that it breaks on, and submit a respective bug report for it.
    ** OFF-TOPIC UPDATE: Using hwdetect --modules to get a modules list, and using these modules in rc.conf with MOD_AUTOLOAD turned off (and also in mkinitcpio.conf and running mkinitcpio -g <path>), seems to have dramatically increased my "Load udev events" processing time. After doing this, my udev speed went from almost 4000ms to literally < 500ms.
    Last edited by intellitech (2008-10-08 14:58:53)

    koch wrote:
    intellitech wrote:DAEMONS=(syslog-ng @network !net-profiles @net-auto @netfs !samba !crond @acpid @dbus @hal @alsa !daemoot !avahi-daemon @cups @ddclient @bluetooth)
    you have dbus starting before hal but hal starts debus by default so please try this...
    DAEMONS=(...@acpid @hal @alsa...)
    and delete debus from that line.
    Removed dbus from the daemons array and hal still won't start. Also, I noticed that the "Loading udev events" portion of the boot process seems to take a lot longer than it used to. Last boot, it took about 19130ms, whereas it used to take < 3000ms. Could these be related?
    Also, I ran a full system upgrade, both udev and hal were upgraded.
    [zen@intellitech ~]$ pacman -Q | grep hal
    hal 0.5.11-4
    hal-info 0.20080508-1
    [zen@intellitech ~]$ pacman -Q | grep udev
    klibc-udev 128-1
    udev 128-5

  • GNOME Fails to start - Polkit? Main.js? - Receive 'Oops' message.

    Been using Arch for years but this is my first problem surprisingly so posting it in this Newbies section.
    I have MATE, KDE, and FLUXBOX working fine as desktop environments for years. Thought I would give GNOME a try and no matter what I've tried I cannot get it working. All I get is a sad face with an 'OOPS' message on screen. Although I am prompted to enter my WiFi password presumably from NetworkManager. None of the errors listed below turn up much on Google so I thought I'd turn to the community. Any help getting GNOME working correctly would be very much appreciated.
    -- Logs begin at Mon 2014-06-09 18:04:18 BST. --
    Jan 19 14:26:50 glow lightdm[1574]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
    Jan 19 14:26:50 glow systemd-logind[432]: New session c4 of user lightdm.
    Jan 19 14:26:50 glow org.a11y.Bus[1582]: Activating service name='org.a11y.atspi.Registry'
    Jan 19 14:26:50 glow org.a11y.Bus[1582]: Successfully activated service 'org.a11y.atspi.Registry'
    Jan 19 14:26:50 glow org.a11y.atspi.Registry[1588]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
    Jan 19 14:26:50 glow systemd-logind[432]: Removed session c1.
    Jan 19 14:26:51 glow NetworkManager[422]: <warn> Could not get scan request result: Scan request rejected
    Jan 19 14:26:59 glow login[1524]: pam_unix(login:session): session opened for user cellardoor by LOGIN(uid=0)
    Jan 19 14:26:59 glow systemd-logind[432]: New session c5 of user cellardoor.
    Jan 19 14:26:59 glow login[1524]: LOGIN ON tty3 BY cellardoor
    Jan 19 14:27:16 glow org.a11y.Bus[1718]: Activating service name='org.a11y.atspi.Registry'
    Jan 19 14:27:16 glow org.a11y.Bus[1718]: Successfully activated service 'org.a11y.atspi.Registry'
    Jan 19 14:27:16 glow org.a11y.atspi.Registry[1725]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
    Jan 19 14:27:16 glow gnome-keyring-daemon[1735]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
    Jan 19 14:27:16 glow gnome-session[1714]: ** Message: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
    Jan 19 14:27:16 glow gnome-session[1714]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
    Jan 19 14:27:16 glow gnome-session[1714]: GPG_AGENT_INFO=/run/user/1000/keyring/gpg:0:1
    Jan 19 14:27:16 glow gnome-session[1714]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
    Jan 19 14:27:16 glow rtkit-daemon[833]: Successfully made thread 1753 of process 1753 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
    Jan 19 14:27:16 glow rtkit-daemon[833]: Supervising 2 threads of 2 processes of 1 users.
    Jan 19 14:27:16 glow pulseaudio[1753]: Daemon already running.
    Jan 19 14:27:16 glow dbus[425]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
    Jan 19 14:27:16 glow dbus[425]: [system] Successfully activated service 'org.freedesktop.hostname1'
    Jan 19 14:27:16 glow dbus[425]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service'
    Jan 19 14:27:16 glow dbus[425]: [system] Successfully activated service 'org.freedesktop.locale1'
    Jan 19 14:27:16 glow gnome-session[1714]: (gnome-shell:1773): Gjs-WARNING **: JS ERROR: Error: Requiring Polkit, version none: Typelib file for namespace 'Polkit' (any version) not found
    Jan 19 14:27:16 glow gnome-session[1714]: @resource:///org/gnome/shell/ui/endSessionDialog.js:28
    Jan 19 14:27:16 glow gnome-session[1714]: @resource:///org/gnome/shell/ui/main.js:15
    Jan 19 14:27:16 glow gnome-session[1714]: @<main>:1
    Jan 19 14:27:16 glow gnome-session[1714]: ** Message: Execution of main.js threw exception: JS_EvaluateScript() failed
    Jan 19 14:27:16 glow gnome-session[1714]: gnome-session[1714]: WARNING: App 'gnome-shell.desktop' exited with code 1
    Jan 19 14:27:16 glow gnome-session[1714]: WARNING: App 'gnome-shell.desktop' exited with code 1
    Jan 19 14:27:17 glow gnome-session[1714]: (gnome-shell:1790): Gjs-WARNING **: JS ERROR: Error: Requiring Polkit, version none: Typelib file for namespace 'Polkit' (any version) not found
    Jan 19 14:27:17 glow gnome-session[1714]: @resource:///org/gnome/shell/ui/endSessionDialog.js:28
    Jan 19 14:27:17 glow gnome-session[1714]: @resource:///org/gnome/shell/ui/main.js:15
    Jan 19 14:27:17 glow gnome-session[1714]: @<main>:1
    Jan 19 14:27:17 glow gnome-session[1714]: ** Message: Execution of main.js threw exception: JS_EvaluateScript() failed
    Jan 19 14:27:17 glow gnome-session[1714]: WARNING: App 'gnome-shell.desktop' exited with code 1
    Jan 19 14:27:17 glow gnome-session[1714]: WARNING: App 'gnome-shell.desktop' respawning too quickly
    Jan 19 14:27:17 glow gnome-session[1714]: gnome-session[1714]: WARNING: App 'gnome-shell.desktop' exited with code 1
    Jan 19 14:27:17 glow gnome-session[1714]: gnome-session[1714]: WARNING: App 'gnome-shell.desktop' respawning too quickly
    Jan 19 14:27:17 glow gnome-session[1714]: Unrecoverable failure in required component gnome-shell.desktop
    Jan 19 14:27:17 glow fingerprint-polkit-agent[1806]: Got "debug" argument.
    Jan 19 14:27:17 glow fingerprint-polkit-agent[1806]: started.
    Jan 19 14:27:17 glow gnome-session[1714]: (uint32 1,)
    Jan 19 14:27:17 glow gnome-session[1714]: Entering running state
    Jan 19 14:27:17 glow gnome-session[1714]: Failed to play sound: File or data not found
    Jan 19 14:27:17 glow gnome-session[1714]: New PolkitAgentListener 0xb637a0
    Jan 19 14:27:17 glow gnome-session[1714]: Adding new listener PolkitQt1::Agent::Listener(0x7fff29d587e0) for 0xb637a0
    Jan 19 14:27:17 glow org.gnome.zeitgeist.Engine[1718]: ** (zeitgeist-datahub:1857): WARNING **: zeitgeist-datahub.vala:226: Unable to get name "org.gnome.zeitgeist.datahub" on the bus!
    Jan 19 14:27:17 glow polkitd[433]: Registered Authentication Agent for unix-session:c5 (system bus name :1.90 [/usr/lib/fingerprint-gui/fingerprint-polkit-agent -d], object path /fingerprintgui/PolicyKit1/AuthenticationAgent, locale en_GB.UTF-8)
    Jan 19 14:27:17 glow fingerprint-polkit-agent[1806]: Listener "/fingerprintgui/PolicyKit1/AuthenticationAgent" registered.
    Jan 19 14:27:17 glow NetworkManager[422]: <info> Auto-activating connection 'The Promised LAN'.
    Jan 19 14:27:17 glow NetworkManager[422]: <info> Activation (wlp3s0) starting connection 'The Promised LAN'
    Jan 19 14:27:17 glow NetworkManager[422]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) scheduled...
    Jan 19 14:27:17 glow NetworkManager[422]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) started...
    Jan 19 14:27:17 glow NetworkManager[422]: <info> (wlp3s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    Jan 19 14:27:17 glow NetworkManager[422]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) scheduled...
    Jan 19 14:27:17 glow NetworkManager[422]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) complete.
    Jan 19 14:27:17 glow NetworkManager[422]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) starting...
    Jan 19 14:27:17 glow NetworkManager[422]: <info> (wlp3s0): device state change: prepare -> config (reason 'none') [40 50 0]
    Jan 19 14:27:17 glow NetworkManager[422]: <info> Activation (wlp3s0/wireless): access point 'The Promised LAN' has security, but secrets are required.
    Jan 19 14:27:17 glow NetworkManager[422]: <info> (wlp3s0): device state change: config -> need-auth (reason 'none') [50 60 0]
    Jan 19 14:27:17 glow NetworkManager[422]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) complete.
    Jan 19 14:27:17 glow org.freedesktop.thumbnails.Cache1[1718]: (tumblerd:1887): tumbler-WARNING **: Failed to load plugin "tumbler-raw-thumbnailer.so": libopenrawgnome.so.1: cannot open shared object file: No such file or directory
    Jan 19 14:27:17 glow org.freedesktop.thumbnails.Cache1[1718]: (tumblerd:1887): tumbler-WARNING **: Failed to load plugin "tumbler-ffmpeg-thumbnailer.so": libffmpegthumbnailer.so.4: cannot open shared object file: No such file or directory
    Jan 19 14:27:17 glow gnome-session[1714]: Traceback (most recent call last):
    Jan 19 14:27:17 glow gnome-session[1714]: File "<frozen importlib._bootstrap>", line 2158, in _find_spec
    Jan 19 14:27:17 glow gnome-session[1714]: AttributeError: 'DynamicImporter' object has no attribute 'find_spec'
    Jan 19 14:27:17 glow gnome-session[1714]: During handling of the above exception, another exception occurred:
    Jan 19 14:27:17 glow gnome-session[1714]: Traceback (most recent call last):
    Jan 19 14:27:17 glow gnome-session[1714]: File "/usr/share/system-config-printer/applet.py", line 45, in <module>
    Jan 19 14:27:17 glow gnome-session[1714]: from gi.repository import Notify
    Jan 19 14:27:17 glow gnome-session[1714]: File "/usr/lib/python3.4/site-packages/gi/importer.py", line 53, in find_module
    Jan 19 14:27:17 glow gnome-session[1714]: 'introspection typelib not found' % namespace)
    Jan 19 14:27:17 glow gnome-session[1714]: ImportError: cannot import name Notify, introspection typelib not found
    Jan 19 14:27:17 glow gnome-session[1714]: (nm-applet:1810): libnm-glib-CRITICAL **: nm_secret_agent_register: assertion 'priv->registered == FALSE' failed
    Jan 19 14:27:17 glow gnome-session[1714]: nm-applet-Message: No keyring secrets found for The Promised LAN/802-11-wireless-security; asking user.
    Jan 19 14:27:17 glow gnome-session[1714]: (gnome-settings-daemon:1742): GLib-GIO-CRITICAL **: g_dbus_proxy_call_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed
    Jan 19 14:27:17 glow gnome-session[1714]: (gnome-settings-daemon:1742): GLib-GIO-CRITICAL **: g_dbus_proxy_call_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed
    Jan 19 14:27:17 glow gnome-session[1714]: (tracker-extract:1813): Tracker-WARNING **: Call to gst_discoverer_discover_uri() failed: GStreamer encountered a general stream error.
    Jan 19 14:27:17 glow gnome-session[1714]: (tracker-extract:1813): Tracker-WARNING **: Task for 'file:///home/cellardoor/test.webm' finished with error: Could not get any metadata for uri:'file:///home/cellardoor/test.webm' and mime:'video/webm'
    Jan 19 14:27:17 glow gnome-session[1714]: (tracker-extract:1813): Tracker-WARNING **: Failed to open file: No OLE2 signature
    Jan 19 14:27:17 glow gnome-session[1714]: (tracker-extract:1813): Tracker-WARNING **: Task for 'file:///home/cellardoor/samsungkeyforserver.pub' finished with error: Could not get any metadata for uri:'file:///home/cellardoor/samsungkeyforserver.pub' and mime:'application/vnd.ms-publisher'
    Jan 19 14:27:18 glow org.gnome.OnlineAccounts[1718]: goa-daemon-Message: goa-daemon version 3.14.2 starting
    Jan 19 14:27:18 glow org.freedesktop.thumbnails.Thumbnailer1[1718]: (tumblerd:1909): tumbler-WARNING **: Failed to load plugin "tumbler-raw-thumbnailer.so": libopenrawgnome.so.1: cannot open shared object file: No such file or directory
    Jan 19 14:27:18 glow org.freedesktop.thumbnails.Thumbnailer1[1718]: (tumblerd:1909): tumbler-WARNING **: Failed to load plugin "tumbler-ffmpeg-thumbnailer.so": libffmpegthumbnailer.so.4: cannot open shared object file: No such file or directory
    Jan 19 14:27:18 glow gnome-session[1714]: (tracker-extract:1813): Tracker-WARNING **: Couldn't create PopplerDocument from uri:'file:///home/cellardoor/Documents/Holiday/certificate_flight_plus_2_a.pdf', PDF document is damaged
    Jan 19 14:27:18 glow gnome-session[1714]: (tracker-extract:1813): Tracker-WARNING **: Task for 'file:///home/cellardoor/Documents/Holiday/certificate_flight_plus_2_a.pdf' finished with error: Could not get any metadata for uri:'file:///home/cellardoor/Documents/Holiday/certificate_flight_plus_2_a.pdf' and mime:'application/pdf'
    Jan 19 14:27:18 glow gnome-session[1714]: (tracker-extract:1813): Tracker-WARNING **: Call to gst_discoverer_discover_uri() failed: Your GStreamer installation is missing a plug-in.
    Jan 19 14:27:18 glow gnome-session[1714]: (tracker-extract:1813): Tracker-WARNING **: Task for 'file:///home/cellardoor/Documents/Java/Assignment3/evidence%20of%20testing%20and%20results%20not%20as%20expected.xcf' finished with error: Could not get any metadata for uri:'file:///home/cellardoor/Documents/Java/Assignment3/evidence%20of%20testing%20and%20results%20not%20as%20expected.xcf' and mime:'image/x-xcf'
    Jan 19 14:27:18 glow gnome-session[1714]: Destroying listener
    Jan 19 14:27:18 glow gnome-session[1714]: Removing listener PolkitQt1::Agent::Listener(0x7fff29d587e0)
    Jan 19 14:27:18 glow polkitd[433]: Unregistered Authentication Agent for unix-session:c5 (system bus name :1.90, object path /fingerprintgui/PolicyKit1/AuthenticationAgent, locale en_GB.UTF-8)
    Jan 19 14:27:18 glow gnome-session[1714]: Received signal:1->'Hangup'
    Jan 19 14:27:18 glow gnome-session[1714]: Received signal:1->'Hangup'
    Jan 19 14:27:18 glow gnome-session[1714]: Received signal:1->'Hangup'
    Jan 19 14:27:18 glow NetworkManager[422]: <warn> No agents were available for this request.
    Jan 19 14:27:18 glow NetworkManager[422]: <info> (wlp3s0): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
    Jan 19 14:27:18 glow NetworkManager[422]: <warn> Activation (wlp3s0) failed for connection 'The Promised LAN'
    Jan 19 14:27:18 glow NetworkManager[422]: <info> (wlp3s0): device state change: failed -> disconnected (reason 'none') [120 30 0]
    Jan 19 14:27:18 glow NetworkManager[422]: <info> (wlp3s0): deactivating device (reason 'none') [0]
    Jan 19 14:27:18 glow NetworkManager[422]: <info> Auto-activating connection 'Security'.
    Jan 19 14:27:18 glow NetworkManager[422]: <info> Activation (wlp3s0) starting connection 'Security'
    Jan 19 14:27:18 glow NetworkManager[422]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) scheduled...
    Jan 19 14:27:18 glow NetworkManager[422]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) started...
    Jan 19 14:27:18 glow NetworkManager[422]: <info> (wlp3s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    Jan 19 14:27:18 glow NetworkManager[422]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) scheduled...
    Jan 19 14:27:18 glow gnome-session[1714]: Received signal:1->'Hangup'
    Jan 19 14:27:18 glow NetworkManager[422]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) complete.
    Jan 19 14:27:18 glow NetworkManager[422]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) starting...
    Jan 19 14:27:18 glow NetworkManager[422]: <info> (wlp3s0): device state change: prepare -> config (reason 'none') [40 50 0]
    Jan 19 14:27:18 glow NetworkManager[422]: <info> Activation (wlp3s0/wireless): access point 'Security' has security, but secrets are required.
    Jan 19 14:27:18 glow NetworkManager[422]: <info> (wlp3s0): device state change: config -> need-auth (reason 'none') [50 60 0]
    Jan 19 14:27:18 glow NetworkManager[422]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) complete.
    Jan 19 14:27:18 glow NetworkManager[422]: <warn> No agents were available for this request.
    Jan 19 14:27:18 glow NetworkManager[422]: <info> (wlp3s0): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
    Jan 19 14:27:18 glow NetworkManager[422]: <warn> Activation (wlp3s0) failed for connection 'Security'
    Jan 19 14:27:18 glow NetworkManager[422]: <info> (wlp3s0): device state change: failed -> disconnected (reason 'none') [120 30 0]
    Jan 19 14:27:18 glow NetworkManager[422]: <info> (wlp3s0): deactivating device (reason 'none') [0]
    Jan 19 14:27:18 glow kernel: tracker-miner-f[1827]: segfault at 130000017a ip 00007f14f57cbdbe sp 00007ffff6a89330 error 4 in libgio-2.0.so.0.4200.1[7f14f5779000+16f000]
    Jan 19 14:27:18 glow org.freedesktop.thumbnails.Cache1[1718]: (tumblerd:1887): GVFS-RemoteVolumeMonitor-WARNING **: Owner of volume monitor org.gtk.Private.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
    Jan 19 14:27:18 glow org.freedesktop.thumbnails.Cache1[1718]: (tumblerd:1887): GVFS-RemoteVolumeMonitor-WARNING **: Owner of volume monitor org.gtk.Private.MTPVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
    Jan 19 14:27:18 glow NetworkManager[422]: <warn> Could not get scan request result: Scan request rejected
    Jan 19 14:27:18 glow org.a11y.Bus[1718]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    Jan 19 14:27:18 glow gnome-session[1714]: g_dbus_connection_real_closed: Remote peer vanished with error: Error receiving message: Connection reset by peer (g-io-error-quark, 0). Exiting.
    Jan 19 14:27:18 glow gnome-session[1714]: Received signal:15->'Terminated'
    Jan 19 14:27:18 glow org.gtk.vfs.Daemon[1718]: A connection to the bus can't be made
    Jan 19 14:27:18 glow org.gtk.vfs.Daemon[1718]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    Jan 19 14:27:18 glow org.freedesktop.Tracker1[1718]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    Jan 19 14:27:18 glow org.gtk.vfs.Daemon[1718]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    Jan 19 14:27:18 glow org.gnome.OnlineAccounts[1718]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    Jan 19 14:27:18 glow org.gtk.Private.UDisks2VolumeMonitor[1718]: g_dbus_connection_real_closed: Remote peer vanished with error: Error receiving message: Connection reset by peer (g-io-error-quark, 0). Exiting.
    Jan 19 14:27:18 glow org.gtk.Private.MTPVolumeMonitor[1718]: g_dbus_connection_real_closed: Remote peer vanished with error: Error receiving message: Connection reset by peer (g-io-error-quark, 0). Exiting.
    Jan 19 14:27:18 glow org.gnome.evolution.dataserver.Sources3[1718]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    Jan 19 14:27:18 glow org.gnome.zeitgeist.Engine[1718]: g_dbus_connection_real_closed: Remote peer vanished with error: Error receiving message: Connection reset by peer (g-io-error-quark, 0). Exiting.
    Jan 19 14:27:18 glow org.freedesktop.Tracker1[1718]: Received signal:15->'Terminated'
    Jan 19 14:27:18 glow org.freedesktop.Tracker1[1718]: OK
    Jan 19 14:27:18 glow ca.desrt.dconf[1718]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    Jan 19 14:27:18 glow gnome-session[1714]: g_dbus_connection_real_closed: Remote peer vanished with error: Error receiving message: Connection reset by peer (g-io-error-quark, 0). Exiting.
    Jan 19 14:27:18 glow org.gnome.zeitgeist.Engine[1718]: [14:27:18.337568 WARNING] zeitgeist-daemon.vala:449: The connection is closed
    Jan 19 14:27:18 glow gnome-session[1714]: Received signal:15->'Terminated'
    Jan 19 14:27:18 glow gnome-session[1714]: OK
    Jan 19 14:27:18 glow org.freedesktop.Telepathy.AccountManager[1718]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    Jan 19 14:27:18 glow org.gnome.evolution.dataserver.Calendar4[1718]: Could not connect: Connection refused
    Jan 19 14:27:18 glow org.freedesktop.thumbnails.Thumbnailer1[1718]: Error creating proxy: The connection is closed (g-io-error-quark, 18)
    Jan 19 14:27:18 glow org.freedesktop.thumbnails.Thumbnailer1[1718]: (tumblerd:1909): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed
    Jan 19 14:27:18 glow org.freedesktop.thumbnails.Thumbnailer1[1718]: Error creating proxy: Error calling StartServiceByName for org.gtk.Private.MTPVolumeMonitor: The connection is closed (g-io-error-quark, 18)
    Jan 19 14:27:18 glow org.freedesktop.thumbnails.Thumbnailer1[1718]: (tumblerd:1909): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed
    Jan 19 14:27:18 glow org.freedesktop.thumbnails.Thumbnailer1[1718]: (tumblerd:1909): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed
    Jan 19 14:27:18 glow org.freedesktop.thumbnails.Thumbnailer1[1718]: Error creating proxy: Error calling StartServiceByName for org.gtk.vfs.Daemon: The connection is closed (g-io-error-quark, 18)
    Jan 19 14:27:18 glow gnome-session[1714]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    Jan 19 14:27:18 glow gnome-session[1714]: Received signal:15->'Terminated'
    Jan 19 14:27:18 glow org.freedesktop.thumbnails.Thumbnailer1[1718]: (tumblerd:1909): tumblerd-WARNING **: Failed to start the thumbnail cache service: Another thumbnail cache service is already running
    Jan 19 14:27:18 glow gnome-session[1714]: OK
    Jan 19 14:27:18 glow systemd-coredump[1943]: Process 1827 (tracker-miner-f) of user 1000 dumped core.
    Thank you!
    Moderator edit:  Added code tags
    Last edited by ewaller (2015-01-19 15:57:10)

    Please use code tags when posting logs. From
    Jan 19 14:27:16 glow gnome-session[1714]: ** Message: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
    Jan 19 14:27:16 glow gnome-session[1714]: (gnome-shell:1773): Gjs-WARNING **: JS ERROR: Error: Requiring Polkit, version none: Typelib file for namespace 'Polkit' (any version) not found
    it seems you're missing dependencies, or they're not started for some reason. Try running GNOME via GDM, installing latter should pull in the full kitchen sink. If you want more hints, google for "gjs polkit not found".
    Last edited by Alad (2015-01-19 15:38:09)

  • Failed to start hibernate.target: Access denied

    I upgraded my machine yesterday and  the Hibernate item in kmenu->Leave are missing. also "systemctl hibernate" dont work:
    $ systemctl hibernate
    Failed to execute operation: Sleep verb not supported
    Failed to start hibernate.target: Access denied
    log:
    Mar 08 22:50:56 arch polkitd[720]: Registered Authentication Agent for unix-process:2370:106040 (system bus name :1.86 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
    Mar 08 22:50:56 arch dbus[363]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.87" (uid=1000 pid=2370 comm="systemctl hibernate -i ") interface="org.freedesktop.systemd1.Manager" member="StartUnit" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ")
    Mar 08 22:50:56 arch polkitd[720]: Unregistered Authentication Agent for unix-process:2370:106040 (system bus name :1.86, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
    Suspend works fine.
    Last edited by ReiserFS (2014-03-09 12:35:46)

    I've got this same problem. For me it's because I haven't got a swap partition (even though I thought I set this machine up with one...). Perhaps you also don't have a swap partition, or maybe it's not mounted? Anyway, I would start with the Swap page of the wiki.

  • Arch32.service fails on start. bundled 32bit system

    I am using the install bundled 32bit system in 64bit system wiki and I think I am having trouble in the systemd service  part.
    I am getting an error starting the arch32 service with systemctl. I have looked at the error messages and I am just not sure what is wrong here. Can someone point out what the error message is telling me, so that I can, in the future, read error messages better? I have did searches and google came up short. I am an eager Linux student. I would more than appreaciate any "hints" so that I can become better and be more value as I help others. Thank you.
    systemctl start arch32
    ## Job for arch32.service failed. See "systemctl status arch32.service" and "journalctl -xe" for details.
    The result of systemct status message...
    # systemctl status -l arch32
    ● arch32.service - 32-bit chroot
    Loaded: loaded (/etc/systemd/system/arch32.service; disabled; vendor preset: disabled)
    Active: failed (Result: exit-code) since Fri 2015-05-22 10:32:54 EDT; 8min ago
    Process: 980 ExecStart=/usr/local/bin/arch32 start (code=exited, status=1/FAILURE)
    Main PID: 980 (code=exited, status=1/FAILURE)
    May 22 10:32:53 archhost systemd[1]: Starting 32-bit chroot...
    May 22 10:32:54 archhost systemd[1]: arch32.service: main process exited, code=exited, status=1/FAILURE
    May 22 10:32:54 archhost systemd[1]: Failed to start 32-bit chroot.
    May 22 10:32:54 archhost systemd[1]: Unit arch32.service entered failed state.
    May 22 10:32:54 archhost systemd[1]: arch32.service failed.
    The result of jouornalctl message...
    # journalctl -xe
    May 23 07:41:27 archhost org.a11y.Bus[3104]: Activating service name='org.a11y.atspi.Registry'
    May 23 07:41:28 archhost org.a11y.Bus[3104]: Successfully activated service 'org.a11y.atspi.Registry'
    May 23 07:41:28 archhost org.a11y.atspi.Registry[3233]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
    May 23 07:41:28 archhost polkitd[3111]: Registered Authentication Agent for unix-session:c1 (system bus name :1.13 [/usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1], object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
    May 23 07:41:32 archhost kernel: dell_wmi: Unknown WMI event type 0x11: 0xffd0
    May 23 07:41:32 archhost kernel: dell_wmi: Unknown WMI event type 0x11: 0xffd1
    May 23 07:41:32 archhost kernel: dell_wmi: Unknown WMI event type 0x11: 0x187
    May 23 07:41:32 archhost kernel: dell_wmi: Unknown WMI event type 0x11: 0x188
    May 23 07:41:32 archhost kernel: dell_wmi: Unknown WMI event type 0x11: 0x187
    May 23 07:41:33 archhost kernel: dell_wmi: Unknown WMI event type 0x11: 0x188
    May 23 07:49:50 archhost sudo[3422]: codeamend : TTY=pts/0 ; PWD=/usr/local/bin ; USER=root ; COMMAND=/usr/bin/systemctl start arch32
    May 23 07:49:50 archhost sudo[3422]: pam_unix(sudo:session): session opened for user root by codeamend(uid=0)
    May 23 07:49:50 archhost polkitd[3111]: Registered Authentication Agent for unix-process:3423:70961 (system bus name :1.14 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
    May 23 07:49:50 archhost systemd[1]: Starting 32-bit chroot...
    -- Subject: Unit arch32.service has begun start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit arch32.service has begun starting up.
    May 23 07:49:50 archhost arch32[3428]: mount: mount point /opt/arch32/scratch does not exist
    May 23 07:49:50 archhost systemd[1]: arch32.service: main process exited, code=exited, status=1/FAILURE
    May 23 07:49:50 archhost systemd[1]: Failed to start 32-bit chroot.
    -- Subject: Unit arch32.service has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit arch32.service has failed.
    -- The result is failed.
    May 23 07:49:50 archhost systemd[1]: Unit arch32.service entered failed state.
    May 23 07:49:50 archhost systemd[1]: arch32.service failed.
    May 23 07:49:50 archhost sudo[3422]: pam_unix(sudo:session): session closed for user root
    May 23 07:49:50 archhost polkitd[3111]: Unregistered Authentication Agent for unix-process:3423:70961 (system bus name :1.14, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
    May 23 07:53:11 archhost systemd[1]: Starting Cleanup of Temporary Directories...
    -- Subject: Unit systemd-tmpfiles-clean.service has begun start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-tmpfiles-clean.service has begun starting up.
    May 23 07:53:11 archhost systemd[1]: Started Cleanup of Temporary Directories.
    -- Subject: Unit systemd-tmpfiles-clean.service has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-tmpfiles-clean.service has finished starting up.
    -- The start-up result is done.
    Last edited by AcousticBruce (2015-05-23 15:57:21)

    graysky wrote:Edit your /usr/local/bin/arch32 script removing the reference to '/scratch' unless you actually have it on your system.  That was a typo from me on the wiki which has now been corrected.
    I removed the /scratch from two areas and made a copy of the wiki version just in case I was wrong. I still got these errors.
    $ systemctl status -l arch32.service
    ● arch32.service - 32-bit chroot
    Loaded: loaded (/etc/systemd/system/arch32.service; disabled; vendor preset: disabled)
    Active: failed (Result: exit-code) since Sun 2015-05-24 08:53:49 EDT; 20s ago
    Process: 2139 ExecStart=/usr/local/bin/arch32 start (code=exited, status=1/FAILURE)
    Main PID: 2139 (code=exited, status=1/FAILURE)
    May 24 08:53:49 archhost systemd[1]: Starting 32-bit chroot...
    May 24 08:53:49 archhost systemd[1]: arch32.service: main process exited, code=exited, status=1/FAILURE
    May 24 08:53:49 archhost systemd[1]: Failed to start 32-bit chroot.
    May 24 08:53:49 archhost systemd[1]: Unit arch32.service entered failed state.
    May 24 08:53:49 archhost systemd[1]: arch32.service failed
    $ journalctl -xe
    -- Unit arch32.service has begun starting up.
    May 24 08:49:36 archhost systemd[1]: arch32.service: main process exited, code=exited, status=1/FAILURE
    May 24 08:49:36 archhost systemd[1]: Failed to start 32-bit chroot.
    -- Subject: Unit arch32.service has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit arch32.service has failed.
    -- The result is failed.
    May 24 08:49:36 archhost polkitd[663]: Unregistered Authentication Agent for unix-process:2103:877657 (system bus name :1.20, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
    May 24 08:49:36 archhost systemd[1]: Unit arch32.service entered failed state.
    May 24 08:49:36 archhost systemd[1]: arch32.service failed.
    May 24 08:53:45 archhost polkitd[663]: Registered Authentication Agent for unix-process:2132:902936 (system bus name :1.24 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
    May 24 08:53:49 archhost polkitd[663]: Operator of unix-session:c1 successfully authenticated as unix-user:codeamend to gain TEMPORARY authorization for action org.freedesktop.systemd1.manage-units for system-bus-name::1.25 [systemctl start arch32] (owned by unix-user:codeamend)
    May 24 08:53:49 archhost systemd[1]: Starting 32-bit chroot...
    -- Subject: Unit arch32.service has begun start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit arch32.service has begun starting up.
    May 24 08:53:49 archhost systemd[1]: arch32.service: main process exited, code=exited, status=1/FAILURE
    May 24 08:53:49 archhost systemd[1]: Failed to start 32-bit chroot.
    -- Subject: Unit arch32.service has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit arch32.service has failed.
    -- The result is failed.
    May 24 08:53:49 archhost systemd[1]: Unit arch32.service entered failed state.
    May 24 08:53:49 archhost systemd[1]: arch32.service failed.
    May 24 08:53:49 archhost polkitd[663]: Unregistered Authentication Agent for unix-process:2132:902936 (system bus name :1.24, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
    May 24 08:56:04 archhost sudo[2156]: codeamend : TTY=pts/2 ; PWD=/opt/arch32/usr/local/bin ; USER=root ; COMMAND=/usr/bin/nano arch32
    May 24 08:56:04 archhost sudo[2156]: pam_unix(sudo:session): session opened for user root by codeamend(uid=0)
    May 24 08:56:21 archhost sudo[2156]: pam_unix(sudo:session): session closed for user root
    May 24 08:56:24 archhost polkitd[663]: Registered Authentication Agent for unix-process:2160:918835 (system bus name :1.28 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
    May 24 08:56:28 archhost polkitd[663]: Operator of unix-session:c1 successfully authenticated as unix-user:codeamend to gain TEMPORARY authorization for action org.freedesktop.systemd1.manage-units for system-bus-name::1.29 [systemctl start arch32] (owned by unix-user:codeamend)
    May 24 08:56:28 archhost systemd[1]: Starting 32-bit chroot...
    -- Subject: Unit arch32.service has begun start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit arch32.service has begun starting up.
    May 24 08:56:28 archhost systemd[1]: arch32.service: main process exited, code=exited, status=1/FAILURE
    May 24 08:56:28 archhost systemd[1]: Failed to start 32-bit chroot.
    -- Subject: Unit arch32.service has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit arch32.service has failed.
    -- The result is failed.
    May 24 08:56:28 archhost systemd[1]: Unit arch32.service entered failed state.
    May 24 08:56:28 archhost systemd[1]: arch32.service failed.
    May 24 08:56:28 archhost polkitd[663]: Unregistered Authentication Agent for unix-process:2160:918835 (system bus name :1.28, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)

  • 32-bit chroot failed to start

    I was going about the process to set up the 32-bit chroot so I could use Adobe Acrobat on my system, but systemctl failed to start the service. Output of "systemctl status arch32.service" is as follows:
    Loaded: loaded (/etc/systemd/system/arch32.service; disabled; vendor preset: disabled)
    Active: failed (Result: exit-code) since Fri 2015-05-29 18:10:29 EDT; 11s ago
    Process: 1295 ExecStart=/usr/local/bin/arch32 start (code=exited, status=1/FAILURE)
    Main PID: 1295 (code=exited, status=1/FAILURE)
    May 29 18:10:29 the-enforcer systemd[1]: Starting 32-bit chroot...
    May 29 18:10:29 the-enforcer systemd[1]: arch32.service: main process exited, code=exited, status=1/FAILURE
    May 29 18:10:29 the-enforcer systemd[1]: Failed to start 32-bit chroot.
    May 29 18:10:29 the-enforcer systemd[1]: Unit arch32.service entered failed state.
    May 29 18:10:29 the-enforcer systemd[1]: arch32.service failed.
    output of "journalctl -xe" is as follows
    -- Subject: Unit arch32.service has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit arch32.service has failed.
    -- The result is failed.
    May 29 18:09:07 the-enforcer systemd[1]: Unit arch32.service entered failed state.
    May 29 18:09:07 the-enforcer systemd[1]: arch32.service failed.
    May 29 18:09:07 the-enforcer polkitd[309]: Unregistered Authentication Agent for unix-process:1242:62178 (system bus name :1.65, object path /org/freedesktop/PolicyKit1/Authen
    May 29 18:09:07 the-enforcer sudo[1241]: pam_unix(sudo:session): session closed for user root
    May 29 18:09:25 the-enforcer sudo[1258]: shaun : TTY=pts/0 ; PWD=/home/shaun ; USER=root ; COMMAND=/usr/local/bin/arch32 start
    May 29 18:09:25 the-enforcer sudo[1258]: pam_unix(sudo:session): session opened for user root by shaun(uid=0)
    May 29 18:09:25 the-enforcer sudo[1258]: pam_unix(sudo:session): session closed for user root
    May 29 18:09:51 the-enforcer /usr/lib/gdm/gdm-x-session[517]: Activating service name='org.gnome.Terminal'
    May 29 18:09:51 the-enforcer /usr/lib/gdm/gdm-x-session[517]: Successfully activated service 'org.gnome.Terminal'
    May 29 18:10:02 the-enforcer sudo[1281]: shaun : TTY=pts/0 ; PWD=/home/shaun ; USER=root ; COMMAND=/usr/local/bin/arch32 stop
    May 29 18:10:02 the-enforcer sudo[1281]: pam_unix(sudo:session): session opened for user root by shaun(uid=0)
    May 29 18:10:03 the-enforcer sudo[1281]: pam_unix(sudo:session): session closed for user root
    May 29 18:10:29 the-enforcer sudo[1289]: shaun : TTY=pts/0 ; PWD=/home/shaun ; USER=root ; COMMAND=/usr/bin/systemctl start arch32.service
    May 29 18:10:29 the-enforcer sudo[1289]: pam_unix(sudo:session): session opened for user root by shaun(uid=0)
    May 29 18:10:29 the-enforcer polkitd[309]: Registered Authentication Agent for unix-process:1290:70456 (system bus name :1.66 [/usr/bin/pkttyagent --notify-fd 5 --fallback], o
    May 29 18:10:29 the-enforcer systemd[1]: Starting 32-bit chroot...
    -- Subject: Unit arch32.service has begun start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit arch32.service has begun starting up.
    May 29 18:10:29 the-enforcer systemd[1]: arch32.service: main process exited, code=exited, status=1/FAILURE
    May 29 18:10:29 the-enforcer systemd[1]: Failed to start 32-bit chroot.
    -- Subject: Unit arch32.service has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit arch32.service has failed.
    -- The result is failed.
    May 29 18:10:29 the-enforcer systemd[1]: Unit arch32.service entered failed state.
    May 29 18:10:29 the-enforcer systemd[1]: arch32.service failed.
    May 29 18:10:29 the-enforcer sudo[1289]: pam_unix(sudo:session): session closed for user root
    May 29 18:10:29 the-enforcer polkitd[309]: Unregistered Authentication Agent for unix-process:1290:70456 (system bus name :1.66, object path /org/freedesktop/PolicyKit1/Authen
    lines 1322-1364/1364 (END)
    Here's what my arch32.service file looks like:
    [Unit]
    Description=32-bit chroot
    [Service]
    Type=oneshot
    RemainAfterExit=yes
    ExecStart=/usr/local/bin/arch32 start
    ExecStop=/usr/local/bin/arch32 stop
    [Install]
    WantedBy=multi-user.target
    Here's what my /usr/local/bin/arch32 file looks like
    #!/bin/bash
    ## User variables.
    MOUNTPOINT=/opt/arch32
    ## Set MANAGEPARTITION to any value if /opt/arch32 resides on a separate
    ## partition and not mounted by /etc/fstab or some other means.
    ## If /opt/arch32 is part of your rootfs, leave this empty.
    MANAGEPARTITION=
    ## Leave USEDISTCC empty unless you wish to use distccd from within the chroot.
    USEDISTCC=
    DISTCC_SUBNET='10.9.8.0/24'
    ## PIDFILE shouldn't need to ba changed from this default.
    PIDFILE=/run/arch32
    start_distccd() {
    [[ ! -L "$MOUNTPOINT"/usr/bin/distccd-chroot ]] &&
    ln -s /usr/bin/distccd "$MOUNTPOINT"/usr/bin/distccd-chroot
    DISTCC_ARGS="--user nobody --allow $DISTCC_SUBNET --port 3692 --log-level warning --log-file /tmp/distccd-i686.log"
    [[ -z "$(pgrep distccd-chroot)" ]] &&
    linux32 chroot "$MOUNTPOINT" /bin/bash -c "/usr/bin/distccd-chroot --daemon $DISTCC_ARGS"
    stop_distccd() {
    [[ -n "$(pgrep distccd-chroot)" ]] &&
    linux32 chroot "$MOUNTPOINT" /bin/bash -c "pkill -SIGTERM distccd-chroot"
    case $1 in
    start)
    [[ -f "$PIDFILE" ]] && exit 1
    if [[ -n "$MANAGEPARTITION" ]]; then
    mountpoint -q $MOUNTPOINT || mount LABEL="arch32" $MOUNTPOINT
    fi
    dirs=(/tmp /dev /dev/pts /home)
    for d in "${dirs[@]}"; do
    mount -o bind $d "$MOUNTPOINT"$d
    done
    mount -t proc none "$MOUNTPOINT/proc"
    mount -t sysfs none "$MOUNTPOINT/sys"
    touch "$PIDFILE"
    [[ -n "$USEDISTCC" ]] && start_distccd
    stop)
    [[ ! -f "$PIDFILE" ]] && exit 1
    [[ -n "$USEDISTCC" ]] && stop_distccd
    if [[ -n "$MANAGEPARTITION" ]]; then
    umount -R -A -l "$MOUNTPOINT"
    else
    dirs=(/home /dev/pts /dev /tmp)
    [[ -n "$USEDISTCC" ]] && stop_distccd
    umount "$MOUNTPOINT"/{sys,proc}
    for d in "${dirs[@]}"; do
    umount -l "$MOUNTPOINT$d"
    done
    fi
    rm -f "$PIDFILE"
    echo "usage: $0 (start|stop)"
    exit 1
    esac
    Any ideas as to what's going on?

    I was going about the process to set up the 32-bit chroot so I could use Adobe Acrobat on my system, but systemctl failed to start the service. Output of "systemctl status arch32.service" is as follows:
    Loaded: loaded (/etc/systemd/system/arch32.service; disabled; vendor preset: disabled)
    Active: failed (Result: exit-code) since Fri 2015-05-29 18:10:29 EDT; 11s ago
    Process: 1295 ExecStart=/usr/local/bin/arch32 start (code=exited, status=1/FAILURE)
    Main PID: 1295 (code=exited, status=1/FAILURE)
    May 29 18:10:29 the-enforcer systemd[1]: Starting 32-bit chroot...
    May 29 18:10:29 the-enforcer systemd[1]: arch32.service: main process exited, code=exited, status=1/FAILURE
    May 29 18:10:29 the-enforcer systemd[1]: Failed to start 32-bit chroot.
    May 29 18:10:29 the-enforcer systemd[1]: Unit arch32.service entered failed state.
    May 29 18:10:29 the-enforcer systemd[1]: arch32.service failed.
    output of "journalctl -xe" is as follows
    -- Subject: Unit arch32.service has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit arch32.service has failed.
    -- The result is failed.
    May 29 18:09:07 the-enforcer systemd[1]: Unit arch32.service entered failed state.
    May 29 18:09:07 the-enforcer systemd[1]: arch32.service failed.
    May 29 18:09:07 the-enforcer polkitd[309]: Unregistered Authentication Agent for unix-process:1242:62178 (system bus name :1.65, object path /org/freedesktop/PolicyKit1/Authen
    May 29 18:09:07 the-enforcer sudo[1241]: pam_unix(sudo:session): session closed for user root
    May 29 18:09:25 the-enforcer sudo[1258]: shaun : TTY=pts/0 ; PWD=/home/shaun ; USER=root ; COMMAND=/usr/local/bin/arch32 start
    May 29 18:09:25 the-enforcer sudo[1258]: pam_unix(sudo:session): session opened for user root by shaun(uid=0)
    May 29 18:09:25 the-enforcer sudo[1258]: pam_unix(sudo:session): session closed for user root
    May 29 18:09:51 the-enforcer /usr/lib/gdm/gdm-x-session[517]: Activating service name='org.gnome.Terminal'
    May 29 18:09:51 the-enforcer /usr/lib/gdm/gdm-x-session[517]: Successfully activated service 'org.gnome.Terminal'
    May 29 18:10:02 the-enforcer sudo[1281]: shaun : TTY=pts/0 ; PWD=/home/shaun ; USER=root ; COMMAND=/usr/local/bin/arch32 stop
    May 29 18:10:02 the-enforcer sudo[1281]: pam_unix(sudo:session): session opened for user root by shaun(uid=0)
    May 29 18:10:03 the-enforcer sudo[1281]: pam_unix(sudo:session): session closed for user root
    May 29 18:10:29 the-enforcer sudo[1289]: shaun : TTY=pts/0 ; PWD=/home/shaun ; USER=root ; COMMAND=/usr/bin/systemctl start arch32.service
    May 29 18:10:29 the-enforcer sudo[1289]: pam_unix(sudo:session): session opened for user root by shaun(uid=0)
    May 29 18:10:29 the-enforcer polkitd[309]: Registered Authentication Agent for unix-process:1290:70456 (system bus name :1.66 [/usr/bin/pkttyagent --notify-fd 5 --fallback], o
    May 29 18:10:29 the-enforcer systemd[1]: Starting 32-bit chroot...
    -- Subject: Unit arch32.service has begun start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit arch32.service has begun starting up.
    May 29 18:10:29 the-enforcer systemd[1]: arch32.service: main process exited, code=exited, status=1/FAILURE
    May 29 18:10:29 the-enforcer systemd[1]: Failed to start 32-bit chroot.
    -- Subject: Unit arch32.service has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit arch32.service has failed.
    -- The result is failed.
    May 29 18:10:29 the-enforcer systemd[1]: Unit arch32.service entered failed state.
    May 29 18:10:29 the-enforcer systemd[1]: arch32.service failed.
    May 29 18:10:29 the-enforcer sudo[1289]: pam_unix(sudo:session): session closed for user root
    May 29 18:10:29 the-enforcer polkitd[309]: Unregistered Authentication Agent for unix-process:1290:70456 (system bus name :1.66, object path /org/freedesktop/PolicyKit1/Authen
    lines 1322-1364/1364 (END)
    Here's what my arch32.service file looks like:
    [Unit]
    Description=32-bit chroot
    [Service]
    Type=oneshot
    RemainAfterExit=yes
    ExecStart=/usr/local/bin/arch32 start
    ExecStop=/usr/local/bin/arch32 stop
    [Install]
    WantedBy=multi-user.target
    Here's what my /usr/local/bin/arch32 file looks like
    #!/bin/bash
    ## User variables.
    MOUNTPOINT=/opt/arch32
    ## Set MANAGEPARTITION to any value if /opt/arch32 resides on a separate
    ## partition and not mounted by /etc/fstab or some other means.
    ## If /opt/arch32 is part of your rootfs, leave this empty.
    MANAGEPARTITION=
    ## Leave USEDISTCC empty unless you wish to use distccd from within the chroot.
    USEDISTCC=
    DISTCC_SUBNET='10.9.8.0/24'
    ## PIDFILE shouldn't need to ba changed from this default.
    PIDFILE=/run/arch32
    start_distccd() {
    [[ ! -L "$MOUNTPOINT"/usr/bin/distccd-chroot ]] &&
    ln -s /usr/bin/distccd "$MOUNTPOINT"/usr/bin/distccd-chroot
    DISTCC_ARGS="--user nobody --allow $DISTCC_SUBNET --port 3692 --log-level warning --log-file /tmp/distccd-i686.log"
    [[ -z "$(pgrep distccd-chroot)" ]] &&
    linux32 chroot "$MOUNTPOINT" /bin/bash -c "/usr/bin/distccd-chroot --daemon $DISTCC_ARGS"
    stop_distccd() {
    [[ -n "$(pgrep distccd-chroot)" ]] &&
    linux32 chroot "$MOUNTPOINT" /bin/bash -c "pkill -SIGTERM distccd-chroot"
    case $1 in
    start)
    [[ -f "$PIDFILE" ]] && exit 1
    if [[ -n "$MANAGEPARTITION" ]]; then
    mountpoint -q $MOUNTPOINT || mount LABEL="arch32" $MOUNTPOINT
    fi
    dirs=(/tmp /dev /dev/pts /home)
    for d in "${dirs[@]}"; do
    mount -o bind $d "$MOUNTPOINT"$d
    done
    mount -t proc none "$MOUNTPOINT/proc"
    mount -t sysfs none "$MOUNTPOINT/sys"
    touch "$PIDFILE"
    [[ -n "$USEDISTCC" ]] && start_distccd
    stop)
    [[ ! -f "$PIDFILE" ]] && exit 1
    [[ -n "$USEDISTCC" ]] && stop_distccd
    if [[ -n "$MANAGEPARTITION" ]]; then
    umount -R -A -l "$MOUNTPOINT"
    else
    dirs=(/home /dev/pts /dev /tmp)
    [[ -n "$USEDISTCC" ]] && stop_distccd
    umount "$MOUNTPOINT"/{sys,proc}
    for d in "${dirs[@]}"; do
    umount -l "$MOUNTPOINT$d"
    done
    fi
    rm -f "$PIDFILE"
    echo "usage: $0 (start|stop)"
    exit 1
    esac
    Any ideas as to what's going on?

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

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

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

  • [Solved] mpd.service fails to start

    hello, i've switched to arch recently,
    love it so far.
    I've been trying to start mpd, with no success :
    systemctl status mpd.service
    mpd.service - Music Player Daemon
    Loaded: loaded (/usr/lib/systemd/system/mpd.service; enabled; vendor preset: disabled)
    Active: failed (Result: exit-code) since Sat 2015-02-21 12:52:02 CET; 3s ago
    Process: 1924 ExecStart=/usr/bin/mpd --no-daemon (code=exited, status=1/FAILURE)
    Main PID: 1924 (code=exited, status=1/FAILURE)
    I cant really see what goes wrong, I get no error message on "systemctl start mpd.service", and I dont see anything in "journalctl" :
    Feb 21 12:30:42 SGC cantata[1694]: libpng warning: iCCP: known incorrect sRGB profile
    Feb 21 12:30:42 SGC cantata[1694]: libpng warning: iCCP: known incorrect sRGB profile
    Feb 21 12:30:42 SGC cantata[1694]: QStringList Solid::Backends::UDisks::UDisksManager::allDevicesInternal() error: "org.freedesktop.DBus.Error.ServiceUnknown"
    Feb 21 12:35:01 SGC baloo_file[507]: "/home/demo/.xsession-errors"
    Feb 21 12:35:01 SGC baloo_file[507]: Normal
    Feb 21 12:35:44 SGC baloo_file[507]: "/home/demo/.xsession-errors"
    Feb 21 12:35:44 SGC baloo_file[507]: Normal
    Feb 21 12:36:50 SGC baloo_file[507]: "/home/demo/.xsession-errors"
    Feb 21 12:36:50 SGC baloo_file[507]: Normal
    Feb 21 12:39:45 SGC konsole[659]: org.kde.kurlfilter-ikws: "d2a291c6bf4fad8aaf7442433364ab6bfb2eecd969885543bfd1e4071db8633b"
    Feb 21 12:40:26 SGC konsole[659]: org.kde.kurlfilter-ikws: "d2a291c6bf4fad8aaf7442433364ab6bfb2eecd969885543bfd1e4071db8633b"
    Feb 21 12:42:48 SGC baloo_file[507]: "/home/demo/.xsession-errors"
    Feb 21 12:42:48 SGC baloo_file[507]: Normal
    Feb 21 12:43:43 SGC baloo_file[507]: "/home/demo/.xsession-errors"
    Feb 21 12:43:43 SGC baloo_file[507]: Normal
    Feb 21 12:43:52 SGC baloo_file[507]: "/home/demo/.xsession-errors"
    Feb 21 12:43:52 SGC baloo_file[507]: Normal
    Feb 21 12:45:45 SGC baloo_file[507]: "/home/demo/.xsession-errors"
    Feb 21 12:45:45 SGC baloo_file[507]: Normal
    Feb 21 12:45:48 SGC konsole[659]: org.kde.kurlfilter-ikws: "systemctl status mpd.service ● mpd.service - Music Player Daemon Loaded: loaded (/usr/lib/systemd/system/mpd.serv
    Feb 21 12:45:56 SGC baloo_file[507]: "/home/demo/.xsession-errors"
    Feb 21 12:45:56 SGC baloo_file[507]: Normal
    Feb 21 12:46:07 SGC baloo_file[507]: "/home/demo/.xsession-errors"
    Feb 21 12:46:07 SGC baloo_file[507]: Normal
    Feb 21 12:48:52 SGC baloo_file[507]: "/home/demo/.xsession-errors"
    Feb 21 12:48:52 SGC baloo_file[507]: Normal
    Feb 21 12:49:07 SGC baloo_file[507]: "/home/demo/.xsession-errors"
    Feb 21 12:49:07 SGC baloo_file[507]: Normal
    Feb 21 12:49:40 SGC konsole[659]: org.kde.kurlfilter-ikws: "Feb 21 12:45:56 SGC baloo_file[507]: Normal Feb 21 12:46:07 SGC baloo_file[507]: "/home/demo/.xsession-errors" Fe
    Feb 21 12:49:44 SGC baloo_file[507]: "/home/demo/.xsession-errors"
    Feb 21 12:49:44 SGC baloo_file[507]: Normal
    Feb 21 12:50:04 SGC baloo_file[507]: "/home/demo/.xsession-errors"
    Feb 21 12:50:04 SGC baloo_file[507]: Normal
    Feb 21 12:50:28 SGC baloo_file[507]: "/home/demo/.xsession-errors"
    Feb 21 12:50:28 SGC baloo_file[507]: Normal
    Feb 21 12:51:00 SGC baloo_file[507]: "/home/demo/.xsession-errors"
    Feb 21 12:51:00 SGC baloo_file[507]: Normal
    Feb 21 12:53:49 SGC konsole[659]: org.kde.kurlfilter-ikws: "Feb 21 12:14:12 SGC kded5[480]: kf5.kservice.sycoca: Trying to open ksycoca from "/home/demo/.cache/ksycoca5" Feb
    Feb 21 12:54:03 SGC baloo_file[507]: "/home/demo/.xsession-errors"
    Feb 21 12:54:03 SGC baloo_file[507]: Normal
    Feb 21 12:54:56 SGC konsole[659]: org.kde.kurlfilter-ikws: "systemctl status mpd.service ● mpd.service - Music Player Daemon Loaded: loaded (/usr/lib/systemd/system/mpd.serv
    Feb 21 12:55:01 SGC baloo_file[507]: "/home/demo/.xsession-errors"
    Feb 21 12:55:01 SGC baloo_file[507]: Normal
    Feb 21 12:55:17 SGC baloo_file[507]: "/home/demo/.xsession-errors"
    Feb 21 12:55:17 SGC baloo_file[507]: Normal
    Feb 21 12:55:36 SGC baloo_file[507]: "/home/demo/.xsession-errors"
    Feb 21 12:55:36 SGC baloo_file[507]: Normal
    Feb 21 12:55:48 SGC baloo_file[507]: "/home/demo/.xsession-errors"
    Feb 21 12:55:48 SGC baloo_file[507]: Normal
    Here's my /etc/mpd.conf :
    # See: /usr/share/doc/mpd/mpdconf.example
    music_directory "~/Music"
    playlist_directory "~/.mpd/playlists"
    db_file "~/.mpd/mpd.db"
    log_file "~/.mpd/mpd.log"
    pid_file "~/.mpd/mpd.pid"
    state_file "~/.mpd/mpdstate"
    bind_to_address "127.0.0.1"
    port "6600"
    audio_output {
    type "alsa"
    name "Output"
    #pid_file "/run/mpd/mpd.pid"
    #db_file "/var/lib/mpd/mpd.db"
    #state_file "/var/lib/mpd/mpdstate"
    #playlist_directory "/var/lib/mpd/playlists"
    Thanks in advance,
    Last edited by demo (2015-02-21 13:14:00)

    Raynman wrote:
    Spider.007 wrote:Mpd runs as a system service
    In this case the system service is indeed the one that failed, but mpd also provides a user service file and all the paths in demo's /etc/mpd.conf (even though that is the default config for the system service) seem to indicate a user service might be more appropriate.
    Indeed, I've made the appropriate change to run it as user service
    (put my mdp.conf in ~/.mpd, and add "mpd ~/.mpd/mpd.conf" to my home ".profile")
    Last edited by demo (2015-02-21 13:13:41)

  • Systemd-hostnamed.service fails to start

    I'm finding the systemd-hostnamed.service isnt working
    $ sudo systemctl --state=failed
    [sudo] password for kevdog:
    UNIT LOAD ACTIVE SUB DESCRIPTION
    ● systemd-hostnamed.service loaded failed failed Hostname Service
    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.
    1 loaded units listed. Pass --all to see loaded but inactive units, too.
    To show all installed unit files use 'systemctl list-unit-files'.
    $ sudo systemctl status systemd-hostnamed.service
    ● systemd-hostnamed.service - Hostname Service
    Loaded: loaded (/usr/lib/systemd/system/systemd-hostnamed.service; static)
    Active: failed (Result: timeout) since Tue 2014-12-16 23:11:36 CST; 10min ago
    Docs: man:systemd-hostnamed.service(8)
    man:hostname(5)
    man:machine-info(5)
    http://www.freedesktop.org/wiki/Software/systemd/hostnamed
    Main PID: 4584
    Dec 16 23:08:35 orphan systemd[1]: systemd-hostnamed.service start operation timed out. Terminating.
    Dec 16 23:10:06 orphan systemd[1]: systemd-hostnamed.service stop-final-sigterm timed out. Killing.
    Dec 16 23:11:36 orphan systemd[1]: systemd-hostnamed.service still around after final SIGKILL. Entering failed mode.
    Dec 16 23:11:36 orphan systemd[1]: Failed to start Hostname Service.
    Dec 16 23:11:36 orphan systemd[1]: Unit systemd-hostnamed.service entered failed state.
    Dec 16 23:11:36 orphan systemd[1]: systemd-hostnamed.service failed.
    I found this addressed in this topic:
    https://github.com/ev3dev/ev3dev/issues/189
    Within this page they state:
    Confirmed that removing PrivateNetwork=yes from the service file works as a workaround. Maybe need to enable CONFIG_NAMESPACES=y and CONFIG_NET_NS=y kernel modules
    I removed the PrivateNetwork=yes from the service file, however this didn't seem to work.  I did not enable the kernel modules.  I am currently running the following kernel: 3.17.6-1-ARCH
    Thanks

    I'm finding the systemd-hostnamed.service isnt working
    $ sudo systemctl --state=failed
    [sudo] password for kevdog:
    UNIT LOAD ACTIVE SUB DESCRIPTION
    ● systemd-hostnamed.service loaded failed failed Hostname Service
    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.
    1 loaded units listed. Pass --all to see loaded but inactive units, too.
    To show all installed unit files use 'systemctl list-unit-files'.
    $ sudo systemctl status systemd-hostnamed.service
    ● systemd-hostnamed.service - Hostname Service
    Loaded: loaded (/usr/lib/systemd/system/systemd-hostnamed.service; static)
    Active: failed (Result: timeout) since Tue 2014-12-16 23:11:36 CST; 10min ago
    Docs: man:systemd-hostnamed.service(8)
    man:hostname(5)
    man:machine-info(5)
    http://www.freedesktop.org/wiki/Software/systemd/hostnamed
    Main PID: 4584
    Dec 16 23:08:35 orphan systemd[1]: systemd-hostnamed.service start operation timed out. Terminating.
    Dec 16 23:10:06 orphan systemd[1]: systemd-hostnamed.service stop-final-sigterm timed out. Killing.
    Dec 16 23:11:36 orphan systemd[1]: systemd-hostnamed.service still around after final SIGKILL. Entering failed mode.
    Dec 16 23:11:36 orphan systemd[1]: Failed to start Hostname Service.
    Dec 16 23:11:36 orphan systemd[1]: Unit systemd-hostnamed.service entered failed state.
    Dec 16 23:11:36 orphan systemd[1]: systemd-hostnamed.service failed.
    I found this addressed in this topic:
    https://github.com/ev3dev/ev3dev/issues/189
    Within this page they state:
    Confirmed that removing PrivateNetwork=yes from the service file works as a workaround. Maybe need to enable CONFIG_NAMESPACES=y and CONFIG_NET_NS=y kernel modules
    I removed the PrivateNetwork=yes from the service file, however this didn't seem to work.  I did not enable the kernel modules.  I am currently running the following kernel: 3.17.6-1-ARCH
    Thanks

  • Sickbeard fails to start. "Unable to write PID file" [Solved]

    I've installed sickbeard from the AUR but can't seem to get it started.
    when running "sudo systemctl start sickbeard.service" I get the following output:
    Job for sickbeard.service failed. See 'systemctl status sickbeard.service' and 'journalctl -xn' for details.
    'systemctl status sickbeard.service' provides:
    sickbeard.service - SickBeard daemon
          Loaded: loaded (/etc/systemd/system/sickbeard.service; disabled)
          Active: failed (Result: exit-code) since Sat 2013-02-23 14:49:19 CST; 1min 4s ago
         Process: 11518 ExecStart=/usr/bin/sickbeard --nolaunch --daemon --quiet --config $SB_CONF --datadir $SB_DATA --port $SB_PORT --pidfile=/run/sickbeard/sickbeard-8081.pid (code=exited, status=1/FAILURE)
    Feb 23 14:49:18 arch systemd[1]: Starting SickBeard daemon...
    Feb 23 14:49:19 arch sickbeard[11518]: Unable to write PID file: No such file or directory [2]
    Feb 23 14:49:19 arch systemd[1]: sickbeard.service: control process exited, code=exited status=1
    Feb 23 14:49:19 arch systemd[1]: Failed to start SickBeard daemon.
    Feb 23 14:49:19 arch systemd[1]: Unit sickbeard.service entered failed state
    And it looks like 'journalctl -xn' provides about the same info:
    -- Logs begin at Tue 2013-01-08 17:25:44 CST, end at Sat 2013-02-23 14:53:29 CST. --
    Feb 23 14:49:19 arch sickbeard[11518]: Unable to write PID file: No such file or directory [2]
    Feb 23 14:49:19 arch systemd[1]: sickbeard.service: control process exited, code=exited status=1
    Feb 23 14:49:19 arch systemd[1]: Failed to start SickBeard daemon.
    -- Subject: Unit sickbeard.service has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/li … temd-devel
    -- Documentation: http://www.freedesktop.org/wiki/Softwar … e9d022f03d
    -- Unit sickbeard.service has failed.
    -- The result is failed.
    Feb 23 14:49:19 arch systemd[1]: Unit sickbeard.service entered failed state
    Also, here is the current systemd file for sickbeard, if that helps:
    [Unit]
    Description=SickBeard daemon
    After=network.target
    [Service]
    EnvironmentFile=/etc/conf.d/sickbeard
    User=sickbeard
    Group=sickbeard
    ExecStart=/usr/bin/sickbeard --nolaunch --daemon --quiet --config "$SB_CONF" --datadir "$SB_DATA" --port "$SB_PORT" --pidfile=/run/sickbeard/sickbeard-8081.pid
    Type=forking
    TimeoutStopSec=20
    PIDFile=/run/sickbeard/sickbeard-8081.pid
    [Install]
    WantedBy=multi-user.target
    So I guess obviously the important part is "Unable to write PID file: No such file or directory [2]", but I'm not really sure what that means or how to fix it. I've played around with the PIDfile configuration for the systemd service (tried renaming from sickbeard to sickbeard-8081) but I always get the same error.
    Any ideas?
    Edit: Solved by teekay
    Last edited by spurious_access (2013-02-24 08:09:01)

    The sabnzbd systemd unit file doesn't use a pidfile. Not sure why. It would make more sense there than it does for sickbeard, because IMHO sickbeard should run as the user who owns the target tv-series media folders. Using tmpfiles.d just causes a headache when you are going to update it using the AUR package.
    I installed it once using sickbeard-git from AUR, changed the systemd unit file and /usr/lib/tmpfiles.d/sickbeard.conf to match my user, chown -R'ed /opt/sickbeard, ran "pacman -R --dbonly sickbeard-git", and ever since use "git pull" to update. That also works directly from web interface.
    Last edited by teekay (2013-02-24 08:47:42)

  • Mariadb failed to start again [solved]

    mariadb is not starting, or restarting. 
    i have poured over topics, tried a few things, but not really sure where to go next.
    $ journalctl -xn
    -- Logs begin at Fri 2014-09-19 23:05:01 PDT, end at Sun 2014-10-26 15:07:23 PDT. --
    Oct 26 15:05:53 falcon systemd[1]: mysqld.service: main process exited, code=exited, status=1/FAILURE
    Oct 26 15:05:53 falcon mysqld[971]: 141026 15:05:53 [ERROR] Aborting
    Oct 26 15:07:23 falcon systemd[1]: mysqld.service start-post operation timed out. Stopping.
    Oct 26 15:07:23 falcon systemd[1]: Failed to start MariaDB database server.
    -- Subject: Unit mysqld.service has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit mysqld.service has failed.
    -- The result is failed.
    Oct 26 15:07:23 falcon systemd[1]: Unit mysqld.service entered failed state.
    Oct 26 15:07:23 falcon systemd[1]: Cannot add dependency job for unit zfs.service, ignoring: Unit zfs.service failed to load: No such file or directory.
    Oct 26 15:07:23 falcon systemd[1]: Cannot add dependency job for unit swat.socket, ignoring: Unit swat.socket failed to load: No such file or directory.
    Oct 26 15:07:23 falcon mysqld[1606]: 141026 15:07:23 [ERROR] /usr/bin/mysqld: ambiguous option '--u' (user, use_stat_tables)
    Oct 26 15:07:23 falcon mysqld[1606]: 141026 15:07:23 [ERROR] Aborting
    Oct 26 15:07:23 falcon systemd[1]: mysqld.service: main process exited, code=exited, status=1/FAILURE
    $ systemctl status mysqld.service
    * mysqld.service - MariaDB database server
    Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled)
    Active: activating (start-post) (Result: exit-code) since Sun 2014-10-26 14:58:07 PDT; 15s ago
    Process: 9807 ExecStart=/usr/bin/mysqld --pid-file=/run/mysqld/mysqld.pid (code=exited, status=1/FAILURE)
    Main PID: 9807 (code=exited, status=1/FAILURE); : 9808 (mysqld-post)
    CGroup: /system.slice/mysqld.service
    `-control
    |-9808 /bin/sh /usr/bin/mysqld-post
    `-9920 sleep 1
    Oct 26 14:58:07 falcon mysqld[9807]: 141026 14:58:07 [ERROR] /usr/bin/mysqld: ambiguous option '--u' (user, use_stat_tables)
    Oct 26 14:58:07 falcon mysqld[9807]: 141026 14:58:07 [ERROR] Aborting
    Oct 26 14:58:07 falcon systemd[1]: mysqld.service: main process exited, code=exited, status=1/FAILURE
    $ mysql -u root -p
    Enter password:
    ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/run/mysqld/mysqld.sock' (2 "No such file or directory")
    $ mysql_install_db --user=mysql --ldata=/var/lib/mysql/
    FATAL ERROR: Could not find ./share/mysql/fill_help_tables.sql
    If you compiled from source, you need to run 'make install' to
    copy the software into the correct location ready for operation.
    If you are using a binary release, you must either be at the top
    level of the extracted archive, or pass the --basedir option
    pointing to that location.
    The latest information about mysql_install_db is available at
    https://mariadb.com/kb/en/installing-system-tables-mysql_install_db
    i looked in /var/log and im not seeing anything related to mysql, no file with the name mysql, and no folder either...   so i looked in my.cnf, saw it was pointing to /var/log/mysqld.log, so i created this file, chowned it to mysql:mysql, chmod 770, and i still cant restart it.  (i havent rebooted since i created the log file, do i need to?)
    i do see it saying something about
    ambiguous option '--u'
    , is that the problem?
    any suggestions on how to dig out more info here so i can figure out whats going on?
    Last edited by wolfdogg (2014-10-26 22:22:12)

    crap, in my mysql conf file, i found the
    u
    , it was here
    u# table_open_cache = 64
    where that came from i have no idea.  it restarted RIGHT away just after that
    $ systemctl start mysqld
    $ systemctl status mysqld.service
    * mysqld.service - MariaDB database server
    Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled)
    Active: active (running) since Sun 2014-10-26 15:19:33 PDT; 1min 47s ago
    Process: 6659 ExecStartPost=/usr/bin/mysqld-post (code=exited, status=0/SUCCESS)
    Main PID: 6658 (mysqld)
    CGroup: /system.slice/mysqld.service
    `-6658 /usr/bin/mysqld --pid-file=/run/mysqld/mysqld.pid
    Oct 26 15:19:27 falcon mysqld[6658]: 141026 15:19:27 [Warning] /usr/bin/mysqld: ignoring option '--character-set-client-handshake' due to invalid value 'utf8'
    Oct 26 15:19:27 falcon mysqld[6658]: 141026 15:19:27 [Warning] option 'max_heap_table_size': unsigned value 0 adjusted to 16384
    Oct 26 15:19:27 falcon mysqld[6658]: 141026 15:19:27 [Warning] Changed limits: max_open_files: 1024 max_connections: 214 table_cache: 400

  • Failed to start Fail2Ban Service

    Hi All,
    I used to use fail2ban service to avoid SSH DDos hack in my Arch system.
    However, I found faiil2ban service failed to be started recently after I perform a system upgrade (pacman -Syu).
    I keep getting failure when try to start fail2ban service by "systemctl start fail2ban.service".
    Checked the status, I got below informatoin:
    [root@archx system]# systemctl status fail2ban.service
    ● fail2ban.service - Fail2Ban Service
       Loaded: loaded (/usr/lib/systemd/system/fail2ban.service; enabled)
       Active: failed (Result: start-limit) since Fri 2014-11-28 09:40:14 CST; 20min ago
         Docs: man:fail2ban(1)
      Process: 493 ExecStart=/usr/bin/fail2ban-client -x start (code=exited, status=1/FAILURE)
    Nov 28 09:40:14 archx systemd[1]: Failed to start Fail2Ban Service.
    Nov 28 09:40:14 archx systemd[1]: Unit fail2ban.service entered failed state.
    Nov 28 09:40:14 archx systemd[1]: fail2ban.service failed.
    Nov 28 09:40:14 archx systemd[1]: start request repeated too quickly for fail2ban.service
    Nov 28 09:40:14 archx systemd[1]: Failed to start Fail2Ban Service.
    Nov 28 09:40:14 archx systemd[1]: Unit fail2ban.service entered failed state.
    Nov 28 09:40:14 archx systemd[1]: fail2ban.service failed.
    From the latest /var/log/error.log.1 I see below information:
    [root@archx log]# tail errors.log.1
    Nov 21 08:14:56 archx sshd[2646]: pam_tally(sshd:auth): pam_get_uid; no such user
    Nov 21 08:14:58 archx sshd[2646]: pam_tally(sshd:auth): pam_get_uid; no such user
    Nov 21 08:15:00 archx sshd[2646]: pam_tally(sshd:auth): pam_get_uid; no such user
    Nov 21 08:15:02 archx sshd[2646]: pam_tally(sshd:auth): pam_get_uid; no such user
    Nov 21 08:15:06 archx sshd[2657]: pam_tally(sshd:auth): pam_get_uid; no such user
    Nov 21 08:15:08 archx sshd[2657]: pam_tally(sshd:auth): pam_get_uid; no such user
    Nov 21 08:15:10 archx sshd[2657]: pam_tally(sshd:auth): pam_get_uid; no such user
    Nov 21 08:15:12 archx sshd[2657]: pam_tally(sshd:auth): pam_get_uid; no such user
    Nov 21 08:15:15 archx sshd[2657]: pam_tally(sshd:auth): pam_get_uid; no such user
    Nov 21 08:30:07 archx systemd-udevd[135]: [/usr/lib/systemd/network/99-default.link:2] Failed to parse interface name policy, ignoring: kernel
    I have no idea about systemd-udevd so I googled about it and found "Predictable Network Interface Names".
    http://www.freedesktop.org/wiki/Softwar … faceNames/
    Is the failure related to it or it's totally different?
    And any idea or guideline that could help me troubleshoot and resolve it?
    Your help is appreciated! Thanks!

    try to set 'backend = systemd' in the /etc/fail2ban/jail.conf file if 'sudo journalctl -xe' say some like
    -- Unit fail2ban.service has begun starting up.
    nov 27 21:39:38 sL1pKn07 fail2ban-client[1813]: ERROR No file(s) found for glob /var/log/auth.log
    nov 27 21:39:38 sL1pKn07 fail2ban-client[1813]: ERROR Failed during configuration: Have not found any log file for sshd jail
    nov 27 21:39:38 sL1pKn07 systemd[1]: fail2ban.service: control process exited, code=exited status=255
    nov 27 21:39:38 sL1pKn07 systemd[1]: Failed to start Fail2Ban Service.
    -- Subject: Unit fail2ban.service has failed
    Last edited by sl1pkn07 (2014-11-27 20:49:03)

Maybe you are looking for

  • How to convert alv list into excel file?

    Hi Experts,         i have created one report for Due Date Analysis. Now My output is displaying in ALV list. But I need to convert the data which in alv list into Excel File. then only i have to send the Excel File to the Customer Thro Email.      S

  • Shipment Cost

    Hi Folks, I have a problem with Shipment cost Document having two line items in that . First line item showing the net value as "Zero"  and Second line item having some net value "xxxxx" . Now my issue why for line item " 1"  the condition type is no

  • Postfix-3.0.0-3 doesn't start

    After upgrade, postfix-3.0.0-3 doesn't start. output of journalctl -xe: Mär 26 22:58:27 arch64-d.xxx.de systemd[1]: Starting Postfix Mail Transport Agent... -- Subject: Unit postfix.service has begun with start-up -- Defined-By: systemd -- Support: h

  • Beware: Adobe CS3 Master Collection could mess with your FCS2

    Found this out today - Was wondering why on my MacPro stuff was cough missing in Motion / FCP... specifically the Video Generators. My only conclusion was the install order on 2 separate computers at my house. FCS2 then Adobe MC and vice versa. Basic

  • Justify property in ADF

    Hi, Can anyone let me know what is the property in ADF which is similar to justify property in Oracle Forms 6i. jusitfy property in Oracle Forms 6i : Specifies the text justification within the item say left,right,centre,start,end similarly how can w