[Solved] Systemd journal in conjunction with syslog-ng?

The wiki has this item:
https://wiki.archlinux.org/index.php/Sy … log_daemon
I'm just wondering what that is all about. Is that for causing systemd to be the source of syslog log entries rather than syslog?
I don't really see the point of this, and don't want to be double-logging everything. I'm happy with the systemd journal (for now). Should I just shut down syslog-ng? I assume the command is "systemctl disable syslog-ng.service"?
Last edited by PaulBx1 (2012-08-30 07:14:39)

Did you make sure syslog does not show up in your rc.conf "daemons" array? That was what was screwing me up. You can tell if syslog is still operating by doing a "systemctl list-units".
This is my conf file:
# 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 journald.conf(5) for details
[Journal]
#Compress=yes
#RateLimitInterval=10s
#RateLimitBurst=200
#SystemMaxUse=
#SystemKeepFree=
#SystemMaxFileSize=
#SystemMinFileSize=
#RuntimeMaxUse=
#RuntimeKeepFree=
#RuntimeMaxFileSize=
#RuntimeMinFileSize=
#ForwardToSyslog=yes
#ForwardToKMsg=no
#ForwardToConsole=no
#ImportKernel=no
#TTYPath=/dev/console
#MaxLevelStore=debug
#MaxLevelSyslog=debug
#MaxLevelKMsg=notice
#MaxLevelConsole=info
#Storage=auto
Last edited by PaulBx1 (2012-08-30 20:35:16)

Similar Messages

  • [solved] systemd-journal and shadow.pacnew updates

    After a recent install and update I have come across the same issue described here where the user was recommended to ignore and erase some .pacnew files. My update generated the following:
    /etc/dhcpcd.conf.pacnew
    /etc/group.pacnew
    /etc/passwd.pacnew
    /etc/shadow.pacnew
    /etc/gshadow.pacnew
    The first, dhcpcd, seemed sensible enough and I incorporated the changes. The latter four all share the following characteristics:
    1. Removed mentions of systemd-journal-remote and systemd-journal-upload. I'm not sure why so I left those records in place.
    2. Changed a few permissions here or there, which i incorporated into /etc/group and /etc/password.
    3. Changed the default shell for a few users; these changes I incorporated.
    I was unable to open /etc/shadow or /etc/gshadow in write mode so I've left these files. Perhaps that's fine because the thread mentioned above says so. However, there's no explanation of why or where this information was obtained (or ordained!)
    Is it fine to leave these two files? Why have syssystemd-journal-remote and systemd-journal-upload been omitted?
    Last edited by Deau (2014-08-29 06:54:18)

    The steps you took look quite sane to me.
    These groups are not in the defaults provided by filesystem (e.g. I don't have them). see the edit
    Apparently systemd creates system groups and users on it's own, see 'man systemd-sysusers'. Do you know / can figure out why these groups are created in the first place ? not important in this case, see the edit as well
    FYI e.g.: https://bugs.archlinux.org/task/41717
    The filesystem package provides those files as defaults (group, passwd, shadow, gshadow amongst otheres). However there are some packages that actually add additional groups they need (like ntp e.g.). The filesystem package cannot know about these. Therefor it's likely to have more groups in your local installation than in the .pacnew files you get.
    The same applies for manually created users and groups of course.
    If needed see the man pages for explanations of the respective files (e.g. 'man group').
    Edit: Ok, I see that after an update I have them as well, so these are apparently new systemd groups and users. I think the rest I said above is still valid, so leaving those in place was the right thing to do.
    Last edited by rebootl (2014-08-28 20:46:43)

  • [SOLVED] Systemd journal not preserved through reboot

    It appears that my journal in /var/log/journal is being flushed just before reboot. Every time I view the journal with the --all flag, the furthest back I can go is to right before the last reboot or power-off. Moreover, my /var/log/journal directory seems incapable of growing bigger than 2.6Mb or so, even though I have the journal configured to max out at 50Mb.
    Here's my /etc/journald.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 journald.conf(5) for details
    [Journal]
    Storage=auto
    #Compress=yes
    #Seal=yes
    #SplitMode=login
    #SyncIntervalSec=5m
    #RateLimitInterval=10s
    #RateLimitBurst=200
    SystemMaxUse=50M
    #SystemKeepFree=
    #SystemMaxFileSize=
    #RuntimeMaxUse=500M
    #RuntimeKeepFree=
    #RuntimeMaxFileSize=
    #MaxRetentionSec=
    #MaxFileSec=1month
    #ForwardToSyslog=yes
    #ForwardToKMsg=no
    #ForwardToConsole=no
    #TTYPath=/dev/console
    #MaxLevelStore=debug
    #MaxLevelSyslog=debug
    #MaxLevelKMsg=notice
    #MaxLevelConsole=info
    Any ideas?
    Last edited by nbtrap (2013-07-01 10:10:47)

    Also of free space and that will trump SystemMaxUse. I know because it happens on my system. As /var fills, systemd keeps smaller persistent journal records.
    EDIT:
    SystemMaxUse= and RuntimeMaxUse= control how much disk space the
               journal may use up at maximum. Defaults to 10% of the size of the respective file system.  SystemKeepFree= and
               RuntimeKeepFree= control how much disk space the journal shall always leave free for other uses if less than the disk space
               configured in SystemMaxUse= and RuntimeMaxUse= is available. Defaults to 15% of the size of the respective file system.
               SystemMaxFileSize= and RuntimeMaxFileSize= control how large individual journal files may grow at maximum.
    Strictly speaking this seems inaccurate, though. You have more than the value of SystemMaxUse available so SystemKeepFree should not apply. However, it does.
    Last edited by cfr (2013-07-01 02:41:22)

  • [SOLVED] systemd: Launch helper exited with unknown return code1

    Why might I be seeing messages like the following when trying to set up systemd?
    [root@blah ~]# hostnamectl set-hostname foobar
    Failed to issue method call: Launch helper exited with unknown return code 1
    EDIT: The solution for me was to remove sysvinit and initscripts and go for pure systemd.
    Last edited by amadar (2012-11-01 05:47:08)

    amadar wrote:
    2ManyDogs wrote:Did you search the forum, as I suggested?
    https://bbs.archlinux.org/viewtopic.php?id=151633
    Yeah, I already found that post but the solution is not there. I'm not trying to use echo to set hostname manually, I'm trying to see why my hostnamectl command (and other *ctl comands) doesn't work, and there's no solution on that thread, just a workaround.
    I have systemd 195 and polkit 0.107 installed.
    EDIT: I replaced sysvinit with systemd-sysvcompat; then enabled syslog-ng, NetworkManager, and cronie services using systemctl enable; then I uninstalled initscripts. I'm not sure where during that process the commands started working, but they work now. But, that doesn't help people trying to migrate without having to replace sysvinit or remove initscripts first.
    This is a problem because the wiki explicitly says to migrate rc.d settings to the new files used by systemd. However, since the *ctl commands don't work at this point, it's impossible for the user to know how to make the config files manually without intimate knowledge of their formats without using *ctl commands.
    For example, how is one supposed to complete step one on the following wiki section? https://wiki.archlinux.org/index.php/Sy … stallation
    As you can see in those instructions, there is no information on how to create the new config files other than using *ctl commands, which don't even work at that stage. Some of the examples show a sample file, but the problematice ones are the ones that don't show a sample file.
    For example, how do you make /etc/adjtime without timedatectl?
    The wiki says that timedatectl [...] "will generate /etc/adjtime automatically; no further configuration is required", but then the Failed message in my original post is displayed.
    I think I will change the wiki to offer a better walk through when I get the chance to migrate to systemd on my desktop which has many daemons and modules.
    the same problem here....

  • [SOLVED] systemd-arch-units conflicts with mdadm and xinetd packages

    Trying to upgrade my testing box today to latest/greatest and running into a file conflict between systemd-arch-linux providing systemd profiles for xinetd and mdadm which also think they control the same files:
    error: failed to commit transaction (conflicting files)
    /usr/lib/systemd/system/mdadm.service exists in both 'mdadm' and 'systemd-arch-units'
    /usr/lib/systemd/system/xinetd.service exists in both 'systemd-arch-units' and 'xinetd'
    Errors occurred, no packages were upgraded.
    Should I just do a force? I am not relying on systemd yet. Or should I just remove systemd?
    Chester
    Last edited by chetwisniewski (2012-05-15 18:17:45)

    silent wrote:So now the new version of mdadm and xinetd moved to [core] and I have the same conflict with systemd-arch-units in [community].
    Try -Syu again?

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

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

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

  • [SOLVED] systemd, systemd-journal constantly at high CPU %age

    Hi all,
    I've switched a computer to systemd, and everything works nicely. The system is responsive and booting is even faster than before. Yay!
    However, both my CPU cores are constantly between 80% and 90%. When I do top in a terminal, I see systemd constantly in the 90%-100% range and systemd-journal in the 60%-100% range, also continuously. My CPU temperature is a lot higher than normal as well (currently at 61.0C)
    Is this normal?
    Last edited by diederick76 (2012-09-13 06:03:11)

    I'm having a similar problem.  I temporarily fixed it by replacing the cupsd.conf with the cupsd.con.default.  Everything ran great, got the printer configured again, journald stopped thrashing my precious SSD by producing millions of these warnings (I didn't wc them, but I was probably getting thousands every second) and all was well.  Until I "shared" the printer again.  Immediately cupsd got locked into restarting thousands of times every second, once again thrashing my cpu and SSD.
    Edit:
    I guess I should probably share my cupsd.conf.  I didn't manually edit it, I used the web interface:
    cat /etc/cups/cupsd.conf
    LogLevel warn
    SystemGroup sys root
    # Allow remote access
    Port 631
    Listen /var/run/cups/cups.sock
    # Share local printers on the local network.
    Browsing On
    BrowseLocalProtocols dnssd
    DefaultAuthType Basic
    WebInterface Yes
    <Location />
    # Allow shared printing...
    Order allow,deny
    Allow all
    </Location>
    <Location /admin>
    </Location>
    <Location /admin/conf>
    AuthType Default
    Require user @SYSTEM
    </Location>
    <Policy default>
    JobPrivateAccess default
    JobPrivateValues default
    SubscriptionPrivateAccess default
    SubscriptionPrivateValues default
    <Limit Create-Job Print-Job Print-URI Validate-Job>
    Order deny,allow
    </Limit>
    <Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job Cancel-My-Jobs Close-Job CUPS-Move-Job CUPS-Get-Document>
    Require user @OWNER @SYSTEM
    Order deny,allow
    </Limit>
    <Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default CUPS-Get-Devices>
    AuthType Default
    Require user @SYSTEM
    Order deny,allow
    </Limit>
    <Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After Cancel-Jobs CUPS-Accept-Jobs CUPS-Reject-Jobs>
    AuthType Default
    Require user @SYSTEM
    Order deny,allow
    </Limit>
    <Limit Cancel-Job CUPS-Authenticate-Job>
    Require user @OWNER @SYSTEM
    Order deny,allow
    </Limit>
    <Limit All>
    Order deny,allow
    </Limit>
    </Policy>
    <Policy authenticated>
    JobPrivateAccess default
    JobPrivateValues default
    SubscriptionPrivateAccess default
    SubscriptionPrivateValues default
    <Limit Create-Job Print-Job Print-URI Validate-Job>
    AuthType Default
    Order deny,allow
    </Limit>
    <Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job Cancel-My-Jobs Close-Job CUPS-Move-Job CUPS-Get-Document>
    AuthType Default
    Require user @OWNER @SYSTEM
    Order deny,allow
    </Limit>
    <Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default>
    AuthType Default
    Require user @SYSTEM
    Order deny,allow
    </Limit>
    <Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After Cancel-Jobs CUPS-Accept-Jobs CUPS-Reject-Jobs>
    AuthType Default
    Require user @SYSTEM
    Order deny,allow
    </Limit>
    <Limit Cancel-Job CUPS-Authenticate-Job>
    AuthType Default
    Require user @OWNER @SYSTEM
    Order deny,allow
    </Limit>
    <Limit All>
    Order deny,allow
    </Limit>
    </Policy>
    Edit02:
    I should mention that I tried the fix described here:  https://bbs.archlinux.org/viewtopic.php?id=146154
    Deiderick:  Have you "shared" your printer?  I suspect that this may be what is causing the problem.
    To Mods:  At this point, because the OP's problem has been resolved, and this thread is marked "solved" should I make a new thread?  It is possible that my problem is not identical to the OP's.
    As a side note, I ran "journalctl | wc -l"  it took about a minute of maxing out one core to finish.  The final number:  1232889.   I have a feeling that this reflects only a fraction of the warnings that cups produced, seeing as I only allocated limited hd space for journal messages.
    Edit03:  After re-reading the etiquette thread, I've decided to start a new thread.  This one is marked "solved" and although very similar, it may not be exactly the same problem that I am having.
    Last edited by Convergence (2012-09-23 00:28:14)

  • [Solved] systemd-cryptsetup with remote header

    Synopsys: Remote headers are not supported by systemd-cryptsetup.
    I was able to get my root partition working with a remote header by adding the '--header=' parameter to the encrypt hook but my searches can only find reference to request for the addition of support to systemd-cryptsetup from about a year ago. I'd also like to have remote headers for my data partitions.
    This is the entry in /etc/crypttab:
    myRecordings /dev/sdc1 /opt/lK/cK.splashK1280x1024.jpg luks --header=/boot/myRecordings-header.img
    ...and this is the error I see in the systemd journal:
    systemd-cryptsetup[314]: Encountered unknown /etc/crypttab option '--header=/boot/myRecordings-header.img', ignoring.
    How do I confirm that support for the '--header=' parameter has been added (or not) to systemd-cryptsetup?
    Last edited by KairiTech (2014-07-21 13:33:13)

    Looks like this was added to systemd recently:
    You can find "header" in the source now.
    http://cgit.freedesktop.org/systemd/sys … 7376e83528
    https://bugs.freedesktop.org/show_bug.cgi?id=66396
    I upgraded to testing to try this out and it works. I am using the remote header option and lvm on luks.
    No more hacks are required, it is all implemented in systemd now.
    EDIT:
    This is already mentioned in the wiki here:
    https://wiki.archlinux.org/index.php/Dm … _initramfs
    Last edited by teateawhy (2015-02-18 00:18:57)

  • [SOLVED]systemd-fstab-generator and syslog error?

    here is the bootup error message:
    Nov  2 07:27:58 localhost [    9.207762] systemd-fstab-generator[151]: Failed to create unit file: File exists
    Nov  2 07:27:58 localhost [   10.119699] systemd[1]: /usr/lib/systemd/system-generators/systemd-fstab-generator exited with exit status 1.
    Nov  2 07:27:58 localhost [   10.544789] systemd[1]: Socket service syslog.service not loaded, refusing.
    Nov  2 07:27:58 localhost [   10.544974] systemd[1]: Failed to listen on Syslog Socket.
    and my fstab is here:
    # /etc/fstab: static file system information
    # <file system>    <dir>    <type>    <options>    <dump>    <pass>
    tmpfs        /tmp    tmpfs    nodev,nosuid    0    0
    /dev/sdb1 /boot ext2 defaults 0 1
    /dev/sdb5 / jfs defaults 0 1
    /dev/sdb6 /home ext4 defaults,user_xattr 0 1
    /dev/sdb7 /var reiserfs defaults 0 1
    /dev/sdb8 /tmp reiserfs defaults 0 1
    Last edited by frat (2012-11-02 03:21:07)

    systemd-fstab-generator is fixed,thank you.
    syslog errors still:
    Nov  2 10:29:44 localhost [   10.051816] systemd[1]: Socket service syslog.service not loaded, refusing.
    Nov  2 10:29:44 localhost [   10.052000] systemd[1]: Failed to listen on Syslog Socket.
    #systemctl status syslog
    syslog.service
          Loaded: error (Reason: No such file or directory)
          Active: inactive (dead)
    #systemctl status syslog.socket
    syslog.socket - Syslog Socket
          Loaded: loaded (/usr/lib/systemd/system/syslog.socket; static)
          Active: inactive (dead)
            Docs: man:systemd.special(7)
                  http://www.freedesktop.org/wiki/Software/systemd/syslog
          CGroup: name=systemd:/system/syslog.socket
    any advice?
    Last edited by frat (2012-11-02 02:56:37)

  • [SOLVED] SystemD NTFS partition issue's

    Hey archers,
    hope someone here can help me
    recently began testing systemd & I am facing a problem where I have to ctrl+d or give root password during every boot up due to systemd having problems with my ntfs partition ( i mount at boot as I have symlinks to that partition for documents & programs which run in wine)
    I have not enabled anything to do with mounting or even added the fuse module to load as it has already picked that up!
    here are the entries I think are related to this from journalctl:
    Aug 29 07:57:37 b0x ntfs-3g[568]: Version 2012.1.15 external FUSE 29
    Aug 29 07:57:37 b0x ntfs-3g[568]: Mounted /dev/sdb1 (Read-Write, label "Win7-sys", NTFS 3.1)
    Aug 29 07:57:37 b0x ntfs-3g[568]: Cmdline options: rw,noatime,sync,gid=100,umask=002
    Aug 29 07:57:37 b0x ntfs-3g[568]: Mount options: rw,sync,allow_other,nonempty,noatime,fsname=/dev/sdb1,blkdev,blksize=4096,default_permissions
    Aug 29 07:57:37 b0x ntfs-3g[568]: Global ownership and permissions enforced, configuration type 7
    Aug 29 07:57:37 b0x ntfs-3g[568]: Warning : using problematic uid==0 and gid!=0
    Aug 29 07:57:37 b0x mount[572]: Mount is denied because the NTFS volume is already exclusively opened.
    Aug 29 07:57:37 b0x mount[572]: The volume may be already mounted, or another software may use it which
    Aug 29 07:57:37 b0x mount[572]: could be identified for example by the help of the 'fuser' command.
    Aug 29 07:57:37 b0x systemd[1]: media-Win7.mount mount process exited, code=exited status=16
    Aug 29 07:57:37 b0x systemd[1]: Job local-fs.target/start failed with result 'dependency'.
    Aug 29 07:57:37 b0x systemd[1]: Triggering OnFailure= dependencies of local-fs.target.
    Aug 29 07:57:37 b0x systemd[1]: Job systemd-user-sessions.service/start failed with result 'dependency'.
    Aug 29 07:57:37 b0x systemd[1]: Job lightdm.service/start failed with result 'dependency'.
    Aug 29 07:57:37 b0x systemd[1]: Job graphical.target/start failed with result 'dependency'.
    Aug 29 07:57:37 b0x systemd[1]: Job multi-user.target/start failed with result 'dependency'.
    Aug 29 07:57:37 b0x systemd[1]: Job systemd-logind.service/start failed with result 'dependency'.
    Aug 29 07:57:37 b0x systemd[1]: Job dbus.service/start failed with result 'dependency'.
    Aug 29 07:57:37 b0x systemd[1]: Job [email protected]/start failed with result 'dependency'.
    Aug 29 07:57:37 b0x systemd[1]: Job hwclock.service/start failed with result 'dependency'.
    Aug 29 07:57:37 b0x systemd[1]: Job syslog-ng.service/start failed with result 'dependency'.
    Aug 29 07:57:37 b0x systemd[1]: Job network.service/start failed with result 'dependency'.
    Aug 29 07:57:37 b0x systemd[1]: Job cronie.service/start failed with result 'dependency'.
    Aug 29 07:57:37 b0x systemd[1]: Job snmpd.service/start failed with result 'dependency'.
    Aug 29 07:57:37 b0x systemd[1]: Job samba.service/start failed with result 'dependency'.
    Aug 29 07:57:37 b0x systemd[1]: Job webmin.service/start failed with result 'dependency'.
    Aug 29 07:57:37 b0x systemd[1]: Job systemd-tmpfiles-clean.timer/start failed with result 'dependency'.
    Aug 29 07:57:37 b0x systemd-journal[181]: Journal stopped
    Aug 29 07:57:37 b0x systemd-journal[584]: Journal started
    Aug 29 07:57:37 b0x ntfs-3g[568]: Unmounting /dev/sdb1 (Win7-sys)
    Aug 29 07:57:37 b0x systemd-udevd[224]: '/usr/sbin/alsactl restore 0' [500] terminated by signal 15 (Terminated)
    Aug 29 07:57:38 b0x systemd[1]: Startup finished in 3s 111ms 648us (kernel) + 6s 425ms 155us (userspace) = 9s 536ms 803us.
    Aug 29 07:57:38 b0x systemd[582]: Failed at step EXEC spawning /bin/plymouth: No such file or directory
    Aug 29 07:58:25 b0x systemd[1]: Cannot add dependency job for unit avani-dnsconfd.service, ignoring: Unit avani-dnsconfd.service failed to load: No such file or directory. See system lo...e' for details.
    Aug 29 07:58:25 b0x systemd[1]: Socket service syslog.service not loaded, refusing.
    Aug 29 07:58:26 b0x arch-modules-load[609]: mkdir: cannot create directory ‘/run/modules-load.d’: File exists
    Aug 29 07:58:26 b0x systemd-modules-load[706]: Module 'vhba' is already loaded
    Aug 29 07:58:26 b0x systemd-modules-load[706]: Module 'fuse' is already loaded
    Aug 29 07:58:26 b0x systemd-fsck[646]: public: clean, 385878/2039808 files, 5060668/8159011 blocks
    Aug 29 07:58:26 b0x systemd-fsck[653]: VM: clean, 228/5677056 files, 5637221/22680575 blocks
    Aug 29 07:58:26 b0x systemd-fsck[644]: Home: clean, 90204/1327104 files, 984778/5305458 blocks
    Aug 29 07:58:26 b0x ntfs-3g[871]: Version 2012.1.15 external FUSE 29
    Aug 29 07:58:26 b0x ntfs-3g[871]: Mounted /dev/sdb1 (Read-Write, label "Win7-sys", NTFS 3.1)
    Aug 29 07:58:26 b0x ntfs-3g[871]: Cmdline options: rw,gid=100,fmask=113,dmask=002
    Aug 29 07:58:26 b0x ntfs-3g[871]: Mount options: rw,allow_other,nonempty,relatime,fsname=/dev/sdb1,blkdev,blksize=4096,default_permissions
    Aug 29 07:58:26 b0x ntfs-3g[871]: Global ownership and permissions enforced, configuration type 7
    Aug 29 07:58:26 b0x ntfs-3g[871]: Warning : using problematic uid==0 and gid!=0
    Here is the entry in /etc/fstab for this partition:
    ## Entry for /dev/sdb1 SYSTEM:(Win7)
    UUID=44083B9668A3E0CC /media/Win7 ntfs-3g gid=users,fmask=113,dmask=002 0 0
    I have been all over goggle & am unable to find out anything which can help.
    As stated before I have links to this partition & so really want/need this partition to be mounted at boot.
    Any help on this will be greatly appreciated
    Thanks in advance
    EDIT #1
    rebooted again, still the same happening
    ran:
    $ sudo mount -l
    proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
    sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
    dev on /dev type devtmpfs (rw,nosuid,relatime,size=3022708k,nr_inodes=755677,mode=755)
    run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
    /dev/sda1 on / type ext4 (rw,relatime,data=ordered) [Arch-sys]
    securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
    tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
    devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
    tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755)
    cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
    cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
    cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu)
    cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
    cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
    cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
    cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
    cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
    systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
    debugfs on /sys/kernel/debug type debugfs (rw,relatime)
    mqueue on /dev/mqueue type mqueue (rw,relatime)
    hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
    fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
    tmpfs on /tmp type tmpfs (rw,nosuid,nodev,relatime)
    /dev/sdb3 on /media/wine type ext4 (rw,noatime,errors=remount-ro,data=ordered) [wine] <<<THIS SHOULD NOT BE HERE!<<<<<<<<<
    /dev/sdd1 on /media/spare2 type ext4 (rw,noatime,errors=remount-ro,data=ordered) [spare2] <<<THIS SHOULD NOT BE HERE!<<<<<<<<<<
    /dev/sdc1 on /media/spare type ext4 (rw,noatime,errors=remount-ro,data=ordered) [spare] <<<THIS SHOULD NOT BE HERE!<<<<<<<<<<<
    /dev/sde1 on /media/USB-HDD2 type vfat (rw,noatime,sync,gid=100,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) [USB-HDD2] <<<<<THIS IS NORMAL
    /dev/sdb4 on /media/pac type ext4 (rw,noatime,errors=remount-ro,data=ordered) [pac] <<<THIS SHOULD NOT BE HERE!
    /dev/sdd1 on /media/Spare2 type ext4 (rw,relatime,errors=remount-ro,data=ordered) [spare2] <<<<<THIS IS NORMAL
    /dev/sdc1 on /media/Spare type ext4 (rw,relatime,errors=remount-ro,data=ordered) [spare] <<<<<THIS IS NORMAL
    /dev/sdb2 on /media/VM type ext4 (rw,relatime,errors=remount-ro,data=ordered) [VM] <<<<<THIS IS NORMAL
    /dev/sdb3 on /var/wine type ext4 (rw,relatime,errors=remount-ro,data=ordered) [wine] <<<<<THIS IS NORMAL
    /dev/sdb4 on /var/cache/pacman type ext4 (rw,relatime,errors=remount-ro,data=ordered) [pac] <<<<<THIS IS NORMAL
    /dev/sdb1 on /media/Win7 type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096) [Win7-sys] <<<<<THIS IS NORMAL
    /dev/sda3 on /public type ext4 (rw,relatime,errors=remount-ro,data=ordered) [public] <<<<<THIS IS NORMAL
    /dev/sda5 on /home type ext4 (rw,relatime,errors=remount-ro,data=ordered) [Home] <<<<<THIS IS NORMAL
    gvfs-fuse-daemon on /run/user/1000/gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
    binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
    gvfs-fuse-daemon on /root/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,relatime,user_id=0,group_id=0)
    as you can see my partitions are being mounted TWICE which is not what I want or expected!
    is there more documentation on what systemd does with mounts that could explain why i have multiple mount points for partitions or is this due to systemd discovering my partitions & mounting them at points based on label names & then parsing my FSTAB as well!
    I have read the wikki but there is very small info there & the links have not provided an explanation for this unwanted behaviour
    EDIT #2
    >>>>>>>>>>>SOLVED<<<<<<<<<<<<<<
    not an NTFS or FUSE issue
    I had previously installed mnttools!
    removed & now all is well
    sorry
    Last edited by t0m5k1 (2012-08-29 08:30:11)

    OK,
    After being spurred on to try to do this thing properly, this is what I came up with today.
    My fstab line (for a USB NTFS disk):
    /dev/sdb1 /media/samsung ntfs-3g noauto,users,rw,nodev 0 0
    Then I created the /media/samsung folder and gave the audio group read/write permissions.
    It seems that non-root users can only mount an ntfs partition if they use a version of ntfs-3g with fuse included, so I replaced ntfs-3g with the version from AUR, having removed from the PKGBUILD file the option "-with-fuse=external" (see this thread: http://bbs.archlinux.org/viewtopic.php?id=44844 ).   I also had to set
    the ntfs-3g binary to setuid-root, dealt with here: http://www.tuxera.com/community/ntfs-3g … privileged (note- the instructions say this is discouraged, but it seems using ntfs partitions in linux requires some compromises).
    I can now mount the drive as an ordinary user.
    Then I set mpd back to run as user mpd, checked the audio group had access to all the mpd folders, and all was well.
    One hiccup which you might not have: mpd was unable to access my (external) sound card at first.  To solve this one, I used
    chmod 770 /dev/snd -R && chgrp audio /dev/snd -R
    As far as I can remember, that's everything.
    Last edited by Henry Flower (2010-04-20 12:54:26)

  • (Solved) systemd-journald extremely high CPU usage

    I started noticing this problem a few days ago, but I thought it was because I was running too much with too little RAM. But when running nothing more than a KDE desktop, my CPU usage bounces between 50% and 100%, making things laggy. It looks like systemd-journald is to blame, as it is using 50% of the CPU. This is an AMD Phenom II dual core, so this definitely shouldn't be happening. I noticed journal logs were more than 2 GB, so I deleted everything within /var/log/journal/. Rebooted, no change, so I disabled journal storage, but that did not solve the problem.
    Nothing in the logs looks like a problem to me:
    $ sudo journalctl
    -- Logs begin at Tue 2013-03-12 17:31:37 PDT, end at Tue 2013-03-12 18:15:56 PDT. --
    Mar 12 17:31:37 silverstone systemd-journal[149]: Allowing runtime journal files to grow to 298.6M.
    Mar 12 17:31:37 silverstone kernel: Initializing cgroup subsys cpuset
    Mar 12 17:31:37 silverstone kernel: Initializing cgroup subsys cpu
    Mar 12 17:31:37 silverstone kernel: Linux version 3.7.10-1-ARCH (tobias@T-POWA-LX) (gcc version 4.7.2 (G
    Mar 12 17:31:37 silverstone kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=31669ea0-76db
    Mar 12 17:31:37 silverstone kernel: e820: BIOS-provided physical RAM map:
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x00000000000e2000-0x00000000000fffff] reserved
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000cff8ffff] usable
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x00000000cff90000-0x00000000cff9dfff] ACPI data
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x00000000cff9e000-0x00000000cffdffff] ACPI NVS
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x00000000cffe0000-0x00000000cfffffff] reserved
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x00000000ffe00000-0x00000000ffffffff] reserved
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x0000000100000000-0x00000001afffffff] usable
    Mar 12 17:31:37 silverstone kernel: NX (Execute Disable) protection: active
    Mar 12 17:31:37 silverstone kernel: SMBIOS 2.5 present.
    Mar 12 17:31:37 silverstone kernel: DMI: MSI MS-7642/890GXM-G65 (MS-7642) , BIOS V1.2 03/31/2010
    Mar 12 17:31:37 silverstone kernel: e820: update [mem 0x00000000-0x0000ffff] usable ==> reserved
    Mar 12 17:31:37 silverstone kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
    Mar 12 17:31:37 silverstone kernel: No AGP bridge found
    Mar 12 17:31:37 silverstone kernel: e820: last_pfn = 0x1b0000 max_arch_pfn = 0x400000000
    Mar 12 17:31:37 silverstone kernel: MTRR default type: uncachable
    Mar 12 17:31:37 silverstone kernel: MTRR fixed ranges enabled:
    Mar 12 17:31:37 silverstone kernel: 00000-9FFFF write-back
    Mar 12 17:31:37 silverstone kernel: A0000-EFFFF uncachable
    Mar 12 17:31:37 silverstone kernel: F0000-FFFFF write-protect
    Mar 12 17:31:37 silverstone kernel: MTRR variable ranges enabled:
    Mar 12 17:31:37 silverstone kernel: 0 base 000000000000 mask FFFF80000000 write-back
    Mar 12 17:31:37 silverstone kernel: 1 base 000080000000 mask FFFFC0000000 write-back
    Mar 12 17:31:37 silverstone kernel: 2 base 0000C0000000 mask FFFFF0000000 write-back
    Mar 12 17:31:37 silverstone kernel: 3 disabled
    Mar 12 17:31:37 silverstone kernel: 4 disabled
    Mar 12 17:31:37 silverstone kernel: 5 disabled
    Mar 12 17:31:37 silverstone kernel: 6 disabled
    Mar 12 17:31:37 silverstone kernel: 7 disabled
    Mar 12 17:31:37 silverstone kernel: TOM2: 00000001b0000000 aka 6912M
    Mar 12 17:31:37 silverstone kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    Mar 12 17:31:37 silverstone kernel: e820: update [mem 0xd0000000-0xffffffff] usable ==> reserved
    Mar 12 17:31:37 silverstone kernel: e820: last_pfn = 0xcff90 max_arch_pfn = 0x400000000
    Mar 12 17:31:37 silverstone kernel: found SMP MP-table at [mem 0x000ff780-0x000ff78f] mapped at [ffff880
    Mar 12 17:31:37 silverstone kernel: initial memory mapped: [mem 0x00000000-0x1fffffff]
    Mar 12 17:31:37 silverstone kernel: Base memory trampoline at [ffff880000099000] 99000 size 24576
    $ systemctl status systemd-journald
    systemd-journald.service - Journal Service
    Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static)
    Active: active (running) since Tue 2013-03-12 18:10:41 PDT; 8min ago
    Docs: man:systemd-journald.service(8)
    man:journald.conf(5)
    Main PID: 142 (systemd-journal)
    Status: "Processing requests..."
    CGroup: name=systemd:/system/systemd-journald.service
    `-142 /usr/lib/systemd/systemd-journald
    However, it looks like the log files keep getting corrupted:
    $ sudo journalctl --verify
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@5e6edd359123491f9998a310206ccbf9-000000000007f543-0004d7c4445effa4.journal
    Invalid object contents at 124687944ââââââââââââââââââââââââââââââââââââââââââ 49%
    File corruption detected at /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000a8cb7-0004d7c3d52e9748.journal:124687944 (of 134074368, 92%).
    FAIL: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000a8cb7-0004d7c3d52e9748.journal (Bad message)
    Invalid object contents at 75715936âââââââââââââââââââââââââââââââââââââââââââ 49%
    File corruption detected at /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system.journal:75715936 (of 76156928, 99%).
    FAIL: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system.journal (Bad message)
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000290d6-0004d7c3a0033472.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@5e6edd359123491f9998a310206ccbf9-0000000000000001-0004d7c413227650.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/[email protected]~
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000fcfc0-0004d7c3fd8ee9c5.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/[email protected]~
    Invalid object contents at 124701856ââââââââââââââââââââââââââââââââââââââââââ 49%
    File corruption detected at /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-0000000000000001-0004d7c3876dda65.journal:124701856 (of 134049792, 93%).
    FAIL: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-0000000000000001-0004d7c3876dda65.journal (Bad message)
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@5e6edd359123491f9998a310206ccbf9-00000000000a9da8-0004d7c45187e39e.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000d26b1-0004d7c3ea1b73f7.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@5e6edd359123491f9998a310206ccbf9-000000000002a43f-0004d7c425785944.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000539fb-0004d7c3b2d1f935.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@5e6edd359123491f9998a310206ccbf9-0000000000054d23-0004d7c4354da4ef.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/user-1000@2c1af599e637441985385fe37ded2a2c-0000000000001706-0004d7c38cd3de88.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/user-1000@5e6edd359123491f9998a310206ccbf9-00000000000019b4-0004d7c4153f8628.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-000000000007e345-0004d7c3c3ed8197.journal
    I am using a two or three year old SSD, so maybe it has gotten some bad sectors? But that doesn't explain why journald still bricks things when it isn't logging anything. The install is 10 months old, and I switched from init to systemd around October. Is there anything I can do, short of reinstalling?
    Thanks,
    Nicholas
    Last edited by bicyclingrevolution (2013-03-14 05:57:13)

    Thanks for the tip ilkyest, but it didn't make any difference to the systemd-journald problem.
    However, I looked at journalctl again and found it cluttered with CUPS failures:
    -- Logs begin at Tue 2013-03-12 19:17:00 PDT, end at Wed 2013-03-13 22:31:31 PDT. --
    Mar 12 19:17:00 silverstone spideroak_inotify[796]: Program started
    Mar 12 19:21:30 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:30 silverstone systemd-journal[143]: Suppressed 7199 messages from /system
    Mar 12 19:21:27 silverstone systemd[1]: Starting CUPS Printing Service...
    Mar 12 19:21:30 silverstone systemd-journal[143]: Suppressed 5471 messages from /system
    Mar 12 19:21:27 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:30 silverstone systemd-journal[143]: Suppressed 5699 messages from /system
    Mar 12 19:21:27 silverstone systemd[1]: Failed to start CUPS Printing Service.
    Mar 12 19:21:27 silverstone systemd[1]: Starting CUPS Printing Service...
    Mar 12 19:21:27 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:27 silverstone systemd[1]: Failed to start CUPS Printing Service.
    Mar 12 19:21:27 silverstone systemd[1]: Starting CUPS Printing Service...
    Mar 12 19:21:27 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:27 silverstone systemd[1]: Failed to start CUPS Printing Service.
    Mar 12 19:21:27 silverstone systemd[1]: Starting CUPS Printing Service...
    Mar 12 19:21:27 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:30 silverstone systemd-coredump[1592]: Process 1590 (cupsd) dumped core.
    Mar 12 19:21:28 silverstone colord[354]: Profile added: Deskjet_3840-Gray..
    Mar 12 19:21:28 silverstone colord[354]: Profile added: Deskjet_3840-RGB..
    Mar 12 19:21:28 silverstone colord[354]: Device added: cups-Deskjet_3840
    Mar 12 19:21:28 silverstone colord[354]: Profile added: Deskjet_F4100-Gray..
    Mar 12 19:21:28 silverstone colord[354]: Profile added: Deskjet_F4100-RGB..
    Mar 12 19:21:28 silverstone colord[354]: Device added: cups-Deskjet_F4100
    Mar 12 19:21:28 silverstone dbus[337]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
    Mar 12 19:21:28 silverstone dbus[337]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs
    Mar 12 19:21:28 silverstone colord[354]: Profile removed: Deskjet_3840-Gray..
    Mar 12 19:21:28 silverstone colord[354]: Profile removed: Deskjet_3840-RGB..
    Mar 12 19:21:28 silverstone colord[354]: device removed: cups-Deskjet_3840
    Mar 12 19:21:31 silverstone colord[354]: Profile removed: Deskjet_F4100-Gray..
    Mar 12 19:21:31 silverstone colord[354]: Profile removed: Deskjet_F4100-RGB..
    Mar 12 19:21:31 silverstone colord[354]: device removed: cups-Deskjet_F4100
    Mar 12 19:21:31 silverstone dbus-daemon[337]: dbus[337]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
    Mar 12 19:21:31 silverstone dbus-daemon[337]: dbus[337]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or director
    Mar 12 19:21:31 silverstone systemd-journal[143]: Missed 6365 kernel messages
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:31 silverstone cupsd[1590]: Unknown directive DefaultAuthType on line 9.
    Mar 12 19:21:31 silverstone cupsd[1590]: cupsd: client.c:757: avahi_client_get_host_name: Assertion `client' failed.
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:31 silverstone cupsd[1594]: Unknown directive DefaultAuthType on line 9.
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Disabling cups solved the CPU usage issue.
    It looks like the root of the problem is Avahi failing to start, but I have no idea why it isn't working.
    $ systemctl status dbus-org.freedesktop.Avahi.service
    dbus-org.freedesktop.Avahi.service
    Loaded: error (Reason: No such file or directory)
    Active: inactive (dead)

  • [SOLVED] Graphics problem in laptop with dual NVIDIA cards

    I'm trying to install Arch on an Lenovo IdeaPad Y510. The laptop have 2 NVIDIA GT755M.
    The second graphics card is removable. If I remove that card I can see with lspci that there also is a intel graphics chip. If the second card is mounted lspci only shows me one GT 755m.
    The problem is that I cannot start X. I have installed gdm and gnome and when booted normally the screen goes blank and the cpu-fan speeds up and after a while the computer reboots.
    This is the log for that boot:
    May 09 22:21:01 arch kernel: [Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module parameter "video.allow_duplicates=1"if the current driver doesn't work.
    May 09 22:21:01 arch kernel: [Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module parameter "video.allow_duplicates=1"if the current driver doesn't work.
    May 09 22:21:02 arch gdm-Xorg-:0[382]: (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
    May 09 22:21:02 arch gdm-Xorg-:0[382]: (==) NVIDIA(0): RGB weight 888
    May 09 22:21:02 arch gdm-Xorg-:0[382]: (==) NVIDIA(0): Default visual is TrueColor
    May 09 22:21:02 arch gdm-Xorg-:0[382]: (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
    May 09 22:21:02 arch gdm-Xorg-:0[382]: (**) NVIDIA(0): Option "AllowEmptyInitialConfiguration" "true"
    May 09 22:21:02 arch gdm-Xorg-:0[382]: (**) NVIDIA(0): Enabling 2D acceleration
    May 09 22:21:02 arch kernel: nvidia 0000:01:00.0: irq 49 for MSI/MSI-X
    May 09 22:21:02 arch systemd-logind[368]: Watching system buttons on /dev/input/event13 (Video Bus)
    May 09 22:21:02 arch kernel: ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    May 09 22:21:02 arch kernel: ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    May 09 22:21:02 arch kernel: ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    May 09 22:21:02 arch kernel: ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    May 09 22:21:02 arch kernel: ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    May 09 22:21:02 arch kernel: ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    May 09 22:21:02 arch kernel: ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    May 09 22:21:02 arch kernel: ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    May 09 22:21:02 arch kernel: ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    May 09 22:21:10 arch kernel: NVRM: GPU at 0000:01:00.0 has fallen off the bus.
    May 09 22:21:10 arch gdm-Xorg-:0[382]: (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA GPU at PCI:1:0:0. Please
    May 09 22:21:10 arch gdm-Xorg-:0[382]: (EE) NVIDIA(GPU-0): check your system's kernel log for additional error
    May 09 22:21:10 arch gdm-Xorg-:0[382]: (EE) NVIDIA(GPU-0): messages and refer to Chapter 8: Common Problems in the
    May 09 22:21:10 arch gdm-Xorg-:0[382]: (EE) NVIDIA(GPU-0): README for additional information.
    May 09 22:21:10 arch gdm-Xorg-:0[382]: (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA graphics device!
    May 09 22:21:10 arch gdm-Xorg-:0[382]: (EE) NVIDIA(0): Failing initialization of X screen 0
    May 09 22:21:10 arch gdm-Xorg-:0[382]: (II) UnloadModule: "nvidia"
    May 09 22:21:10 arch gdm-Xorg-:0[382]: (II) UnloadSubModule: "wfb"
    May 09 22:21:10 arch gdm-Xorg-:0[382]: (II) UnloadSubModule: "fb"
    May 09 22:21:10 arch gdm-Xorg-:0[382]: (EE) Screen(s) found, but none have a usable configuration.
    May 09 22:21:10 arch gdm-Xorg-:0[382]: (EE)
    May 09 22:21:10 arch gdm-Xorg-:0[382]: Fatal server error:
    May 09 22:21:10 arch gdm-Xorg-:0[382]: (EE) no screens found(EE)
    May 09 22:21:10 arch gdm-Xorg-:0[382]: (EE)
    May 09 22:21:10 arch gdm-Xorg-:0[382]: Please consult the The X.Org Foundation support
    May 09 22:21:10 arch gdm-Xorg-:0[382]: at http://wiki.x.org
    May 09 22:21:10 arch gdm-Xorg-:0[382]: for help.
    May 09 22:21:10 arch gdm-Xorg-:0[382]: (EE) Please also check the log file at "/dev/null" for additional information.
    May 09 22:21:10 arch gdm-Xorg-:0[382]: (EE)
    May 09 22:21:10 arch kernel: NVRM: RmInitAdapter failed! (0x25:0x28:1150)
    May 09 22:21:10 arch kernel: NVRM: rm_init_adapter failed for device bearing minor number 0
    May 09 22:21:10 arch kernel: NVRM: nvidia_frontend_open: minor 0, module->open() failed, error -5
    May 09 22:21:10 arch gdm-Xorg-:0[382]: (EE) Server terminated with error (1). Closing log file.
    May 09 22:21:11 arch gdm[377]: Child process 382 was already dead.
    How do I set video.allow_duplicates=1 ?
    When the computer reboots I start with runlevel 3 and then tries a startx. This gives me the following /var/log/Xorg.0.log:
    [ 231.105] (II) NVIDIA GLX Module 337.12 Fri Apr 4 14:34:00 PDT 2014
    [ 231.107] Loading extension GLX
    [ 231.107] (II) LoadModule: "nvidia"
    [ 231.108] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
    [ 231.114] (II) Module nvidia: vendor="NVIDIA Corporation"
    [ 231.114] compiled for 4.0.2, module version = 1.0.0
    [ 231.114] Module class: X.Org Video Driver
    [ 231.115] (II) NVIDIA dlloader X Driver 337.12 Fri Apr 4 14:13:45 PDT 2014
    [ 231.115] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    [ 231.115] (--) using VT number 2
    [ 231.130] (II) Loading sub module "fb"
    [ 231.130] (II) LoadModule: "fb"
    [ 231.130] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 231.132] (II) Module fb: vendor="X.Org Foundation"
    [ 231.132] compiled for 1.15.1, module version = 1.0.0
    [ 231.132] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 231.132] (WW) Unresolved symbol: fbGetGCPrivateKey
    [ 231.132] (II) Loading sub module "wfb"
    [ 231.132] (II) LoadModule: "wfb"
    [ 231.132] (II) Loading /usr/lib/xorg/modules/libwfb.so
    [ 231.134] (II) Module wfb: vendor="X.Org Foundation"
    [ 231.134] compiled for 1.15.1, module version = 1.0.0
    [ 231.134] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 231.134] (II) Loading sub module "ramdac"
    [ 231.134] (II) LoadModule: "ramdac"
    [ 231.134] (II) Module "ramdac" already built-in
    [ 231.690] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
    [ 231.690] (==) NVIDIA(0): RGB weight 888
    [ 231.690] (==) NVIDIA(0): Default visual is TrueColor
    [ 231.690] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
    [ 231.693] (**) NVIDIA(0): Enabling 2D acceleration
    [ 240.591] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA GPU at PCI:1:0:0. Please
    [ 240.591] (EE) NVIDIA(GPU-0): check your system's kernel log for additional error
    [ 240.591] (EE) NVIDIA(GPU-0): messages and refer to Chapter 8: Common Problems in the
    [ 240.591] (EE) NVIDIA(GPU-0): README for additional information.
    [ 240.591] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA graphics device!
    [ 240.591] (EE) NVIDIA(0): Failing initialization of X screen 0
    [ 240.591] (II) UnloadModule: "nvidia"
    [ 240.591] (II) UnloadSubModule: "wfb"
    [ 240.591] (II) UnloadSubModule: "fb"
    [ 240.591] (EE) Screen(s) found, but none have a usable configuration.
    [ 240.591] (EE)
    Fatal server error:
    [ 240.591] (EE) no screens found(EE)
    [ 240.591] (EE)
    Please consult the The X.Org Foundation support
    at http://wiki.x.org
    for help.
    [ 240.591] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
    [ 240.591] (EE)
    [ 240.608] (EE) Server terminated with error (1). Closing log file.
    I've tried without a xorg.conf and with one generated by nvidia-xconfig but they give the same result.
    Where do I find the README mentioned in the log?
    Anyone knows what the problem is?
    I tried Ubuntu before installing Arch and that worked (with NVIDIA drivers version 331) so it should be possible to get this machine working.
    Any help is appreciated!
    Last edited by bitbjorn (2014-05-20 19:10:58)

    I've given up on the nvidia-drivers and try with nouveau-driver. Still no success.
    Screen is black at bootup. I can, however, login and type reboot and the computer reboots (although I cant see anything).
    If I add nomodeset to bootline I can see the login-prompt and login, if I then run startx I get the following in /var/log/Xorg.0.log:
    [drm] KMS not enabled
    This link https://wiki.archlinux.org/index.php/ke … de_setting  does not help very much, I've tried the "Early KMS start" thing but I still have the same problem.
    If I have gdm enabled with
    systemctl enable gdm.service
    and boot the computer the screen is blank. If I login with ssh I can see that gdm is started.
    Journalctl -b -0 from the ssh-session gives this:
    [bjorn@arch ~]$ journalctl -b -0
    -- Logs begin at Wed 2014-05-07 00:30:45 CEST, end at Sun 2014-05-11 11:58:50 CEST. --
    May 11 11:58:32 arch systemd-journal[219]: Runtime journal is using 8.0M (max allowed 799.9M, trying to leave 1.1G free of 7.8G avail
    May 11 11:58:32 arch systemd-journal[219]: Runtime journal is using 8.0M (max allowed 799.9M, trying to leave 1.1G free of 7.8G avail
    May 11 11:58:32 arch kernel: Initializing cgroup subsys cpuset
    May 11 11:58:32 arch kernel: Initializing cgroup subsys cpu
    May 11 11:58:32 arch kernel: Initializing cgroup subsys cpuacct
    May 11 11:58:32 arch kernel: Linux version 3.14.3-1-ARCH (nobody@var-lib-archbuild-testing-x86_64-tobias) (gcc version 4.9.0 (GCC) )
    May 11 11:58:32 arch kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=4a950c38-be98-4678-9a12-9caebece5745 rw quiet
    May 11 11:58:32 arch kernel: e820: BIOS-provided physical RAM map:
    May 11 11:58:32 arch kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000006efff] usable
    May 11 11:58:32 arch kernel: BIOS-e820: [mem 0x000000000006f000-0x000000000006ffff] reserved
    May 11 11:58:32 arch kernel: BIOS-e820: [mem 0x0000000000070000-0x0000000000087fff] usable
    May 11 11:58:32 arch kernel: BIOS-e820: [mem 0x0000000000088000-0x00000000000bffff] reserved
    May 11 11:58:32 arch kernel: BIOS-e820: [mem 0x0000000000100000-0x000000006e6effff] usable
    May 11 11:58:32 arch kernel: BIOS-e820: [mem 0x000000006e6f0000-0x000000006faeffff] reserved
    May 11 11:58:32 arch kernel: BIOS-e820: [mem 0x000000006faf0000-0x000000008eebefff] usable
    May 11 11:58:32 arch kernel: BIOS-e820: [mem 0x000000008eebf000-0x000000008f0befff] type 20
    May 11 11:58:32 arch kernel: BIOS-e820: [mem 0x000000008f0bf000-0x000000008f6befff] reserved
    May 11 11:58:32 arch kernel: BIOS-e820: [mem 0x000000008f6bf000-0x000000008f7befff] ACPI NVS
    May 11 11:58:32 arch kernel: BIOS-e820: [mem 0x000000008f7bf000-0x000000008f7fefff] ACPI data
    May 11 11:58:32 arch kernel: BIOS-e820: [mem 0x000000008f7ff000-0x000000008f7fffff] usable
    May 11 11:58:32 arch kernel: BIOS-e820: [mem 0x000000008f800000-0x000000008fffffff] reserved
    May 11 11:58:32 arch kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
    May 11 11:58:32 arch kernel: BIOS-e820: [mem 0x00000000feb00000-0x00000000feb0ffff] reserved
    May 11 11:58:32 arch kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
    May 11 11:58:32 arch kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fee00fff] reserved
    May 11 11:58:32 arch kernel: BIOS-e820: [mem 0x00000000ffb80000-0x00000000ffffffff] reserved
    May 11 11:58:32 arch kernel: BIOS-e820: [mem 0x0000000100000000-0x000000046effffff] usable
    May 11 11:58:32 arch kernel: NX (Execute Disable) protection: active
    May 11 11:58:32 arch kernel: efi: EFI v2.31 by INSYDE Corp.
    May 11 11:58:32 arch kernel: efi: ACPI=0x8f7fe000 ACPI 2.0=0x8f7fe014 SMBIOS=0x8f6bef98
    May 11 11:58:32 arch kernel: efi: mem00: type=3, attr=0xf, range=[0x0000000000000000-0x0000000000001000) (0MB)
    May 11 11:58:32 arch kernel: efi: mem01: type=7, attr=0xf, range=[0x0000000000001000-0x000000000006f000) (0MB)
    May 11 11:58:32 arch kernel: efi: mem02: type=0, attr=0xf, range=[0x000000000006f000-0x0000000000070000) (0MB)
    May 11 11:58:32 arch kernel: efi: mem03: type=7, attr=0xf, range=[0x0000000000070000-0x0000000000080000) (0MB)
    May 11 11:58:32 arch kernel: efi: mem04: type=3, attr=0xf, range=[0x0000000000080000-0x0000000000082000) (0MB)
    May 11 11:58:32 arch kernel: efi: mem05: type=7, attr=0xf, range=[0x0000000000082000-0x0000000000088000) (0MB)
    May 11 11:58:32 arch kernel: efi: mem06: type=6, attr=0x800000000000000f, range=[0x0000000000088000-0x000000000009f000) (0MB)
    May 11 11:58:32 arch kernel: efi: mem07: type=0, attr=0xf, range=[0x000000000009f000-0x00000000000a0000) (0MB)
    May 11 11:58:32 arch kernel: efi: mem08: type=2, attr=0xf, range=[0x0000000000100000-0x000000000105b000) (15MB)
    May 11 11:58:32 arch kernel: efi: mem09: type=7, attr=0xf, range=[0x000000000105b000-0x0000000002000000) (15MB)
    May 11 11:58:32 arch kernel: efi: mem10: type=2, attr=0xf, range=[0x0000000002000000-0x0000000002f5b000) (15MB)
    May 11 11:58:32 arch kernel: efi: mem11: type=7, attr=0xf, range=[0x0000000002f5b000-0x0000000037622000) (838MB)
    May 11 11:58:32 arch kernel: efi: mem12: type=2, attr=0xf, range=[0x0000000037622000-0x0000000037b09000) (4MB)
    May 11 11:58:32 arch kernel: efi: mem13: type=7, attr=0xf, range=[0x0000000037b09000-0x000000004a79d000) (300MB)
    May 11 11:58:32 arch kernel: efi: mem14: type=2, attr=0xf, range=[0x000000004a79d000-0x000000006cb00000) (547MB)
    May 11 11:58:32 arch kernel: efi: mem15: type=4, attr=0xf, range=[0x000000006cb00000-0x000000006cb20000) (0MB)
    May 11 11:58:32 arch kernel: efi: mem16: type=7, attr=0xf, range=[0x000000006cb20000-0x000000006d6f1000) (11MB)
    May 11 11:58:32 arch kernel: efi: mem17: type=4, attr=0xf, range=[0x000000006d6f1000-0x000000006e6f0000) (15MB)
    May 11 11:58:32 arch kernel: efi: mem18: type=0, attr=0xf, range=[0x000000006e6f0000-0x000000006faf0000) (20MB)
    May 11 11:58:32 arch kernel: efi: mem19: type=7, attr=0xf, range=[0x000000006faf0000-0x000000006fce2000) (1MB)
    May 11 11:58:32 arch kernel: efi: mem20: type=1, attr=0xf, range=[0x000000006fce2000-0x000000006fcff000) (0MB)
    May 11 11:58:32 arch kernel: efi: mem21: type=7, attr=0xf, range=[0x000000006fcff000-0x00000000730e5000) (51MB)
    May 11 11:58:32 arch kernel: efi: mem22: type=4, attr=0xf, range=[0x00000000730e5000-0x0000000073123000) (0MB)
    May 11 11:58:32 arch kernel: efi: mem23: type=7, attr=0xf, range=[0x0000000073123000-0x0000000073124000) (0MB)
    May 11 11:58:32 arch kernel: efi: mem24: type=4, attr=0xf, range=[0x0000000073124000-0x00000000732d5000) (1MB)
    May 11 11:58:32 arch kernel: efi: mem25: type=7, attr=0xf, range=[0x00000000732d5000-0x00000000732d6000) (0MB)
    May 11 11:58:32 arch kernel: efi: mem26: type=4, attr=0xf, range=[0x00000000732d6000-0x00000000733e8000) (1MB)
    May 11 11:58:32 arch kernel: efi: mem27: type=7, attr=0xf, range=[0x00000000733e8000-0x00000000733e9000) (0MB)
    May 11 11:58:32 arch kernel: efi: mem28: type=4, attr=0xf, range=[0x00000000733e9000-0x000000007461b000) (18MB)
    May 11 11:58:32 arch kernel: efi: mem29: type=7, attr=0xf, range=[0x000000007461b000-0x000000007461d000) (0MB)
    May 11 11:58:32 arch kernel: efi: mem30: type=4, attr=0xf, range=[0x000000007461d000-0x000000007461e000) (0MB)
    May 11 11:58:32 arch kernel: efi: mem31: type=7, attr=0xf, range=[0x000000007461e000-0x0000000074620000) (0MB)
    May 11 11:58:32 arch kernel: efi: mem32: type=4, attr=0xf, range=[0x0000000074620000-0x000000007463c000) (0MB)
    May 11 11:58:32 arch kernel: efi: mem33: type=7, attr=0xf, range=[0x000000007463c000-0x000000007463d000) (0MB)
    May 11 11:58:32 arch kernel: efi: mem34: type=4, attr=0xf, range=[0x000000007463d000-0x0000000074646000) (0MB)
    May 11 11:58:32 arch kernel: efi: mem35: type=7, attr=0xf, range=[0x0000000074646000-0x0000000074648000) (0MB)
    May 11 11:58:32 arch kernel: efi: mem36: type=4, attr=0xf, range=[0x0000000074648000-0x000000007466f000) (0MB)
    May 11 11:58:32 arch kernel: efi: mem37: type=7, attr=0xf, range=[0x000000007466f000-0x0000000074671000) (0MB)
    May 11 11:58:32 arch kernel: efi: mem38: type=4, attr=0xf, range=[0x0000000074671000-0x000000007480b000) (1MB)
    May 11 11:58:32 arch kernel: efi: mem39: type=7, attr=0xf, range=[0x000000007480b000-0x000000007480f000) (0MB)
    May 11 11:58:32 arch kernel: efi: mem40: type=4, attr=0xf, range=[0x000000007480f000-0x0000000074810000) (0MB)
    May 11 11:58:32 arch kernel: efi: mem41: type=7, attr=0xf, range=[0x0000000074810000-0x0000000074813000) (0MB)
    May 11 11:58:32 arch kernel: efi: mem42: type=4, attr=0xf, range=[0x0000000074813000-0x000000007688f000) (32MB)
    May 11 11:58:32 arch kernel: efi: mem43: type=7, attr=0xf, range=[0x000000007688f000-0x000000008ea5e000) (385MB)
    May 11 11:58:32 arch kernel: efi: mem44: type=2, attr=0xf, range=[0x000000008ea5e000-0x000000008ea68000) (0MB)
    May 11 11:58:32 arch kernel: efi: mem45: type=3, attr=0xf, range=[0x000000008ea68000-0x000000008eebf000) (4MB)
    May 11 11:58:32 arch kernel: efi: mem46: type=5, attr=0x800000000000000f, range=[0x000000008eebf000-0x000000008f0bf000) (2MB)
    May 11 11:58:32 arch kernel: efi: mem47: type=6, attr=0x800000000000000f, range=[0x000000008f0bf000-0x000000008f2bf000) (2MB)
    May 11 11:58:32 arch kernel: efi: mem48: type=0, attr=0xf, range=[0x000000008f2bf000-0x000000008f6bf000) (4MB)
    May 11 11:58:32 arch kernel: efi: mem49: type=10, attr=0xf, range=[0x000000008f6bf000-0x000000008f7bf000) (1MB)
    May 11 11:58:32 arch kernel: efi: mem50: type=9, attr=0xf, range=[0x000000008f7bf000-0x000000008f7ff000) (0MB)
    May 11 11:58:32 arch kernel: efi: mem51: type=4, attr=0xf, range=[0x000000008f7ff000-0x000000008f800000) (0MB)
    May 11 11:58:32 arch kernel: efi: mem52: type=7, attr=0xf, range=[0x0000000100000000-0x000000046f000000) (14064MB)
    May 11 11:58:32 arch kernel: efi: mem53: type=0, attr=0x0, range=[0x00000000000a0000-0x00000000000c0000) (0MB)
    May 11 11:58:32 arch kernel: efi: mem54: type=0, attr=0x0, range=[0x000000008f800000-0x0000000090000000) (8MB)
    May 11 11:58:32 arch kernel: efi: mem55: type=11, attr=0x8000000000000001, range=[0x00000000e0000000-0x00000000f0000000) (256MB)
    May 11 11:58:32 arch kernel: efi: mem56: type=11, attr=0x8000000000000001, range=[0x00000000feb00000-0x00000000feb10000) (0MB)
    May 11 11:58:32 arch kernel: efi: mem57: type=11, attr=0x8000000000000001, range=[0x00000000fec00000-0x00000000fec01000) (0MB)
    May 11 11:58:32 arch kernel: efi: mem58: type=11, attr=0x8000000000000001, range=[0x00000000fed00000-0x00000000fed1c000) (0MB)
    May 11 11:58:32 arch kernel: efi: mem59: type=11, attr=0x8000000000000000, range=[0x00000000fed1c000-0x00000000fed20000) (0MB)
    May 11 11:58:32 arch kernel: efi: mem60: type=11, attr=0x8000000000000001, range=[0x00000000fed20000-0x00000000fee01000) (0MB)
    May 11 11:58:32 arch kernel: efi: mem61: type=11, attr=0x8000000000000001, range=[0x00000000ffb80000-0x0000000100000000) (4MB)
    May 11 11:58:32 arch kernel: SMBIOS 2.7 present.
    May 11 11:58:32 arch kernel: DMI: LENOVO 20217/VIQY0Y1, BIOS 74CN44WW(V3.05) 09/18/2013
    May 11 11:58:32 arch kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
    May 11 11:58:32 arch kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
    May 11 11:58:32 arch kernel: No AGP bridge found
    May 11 11:58:32 arch kernel: e820: last_pfn = 0x46f000 max_arch_pfn = 0x400000000
    May 11 11:58:32 arch kernel: MTRR default type: uncachable
    May 11 11:58:32 arch kernel: MTRR fixed ranges enabled:
    May 11 11:58:32 arch kernel: 00000-9FFFF write-back
    May 11 11:58:32 arch kernel: A0000-BFFFF uncachable
    May 11 11:58:32 arch kernel: C0000-E7FFF write-protect
    May 11 11:58:32 arch kernel: E8000-EFFFF write-combining
    May 11 11:58:32 arch kernel: F0000-FFFFF write-protect
    May 11 11:58:32 arch kernel: MTRR variable ranges enabled:
    May 11 11:58:32 arch kernel: 0 base 0000000000 mask 7800000000 write-back
    May 11 11:58:32 arch kernel: 1 base 008F800000 mask 7FFF800000 uncachable
    May 11 11:58:32 arch kernel: 2 base 0090000000 mask 7FF0000000 uncachable
    May 11 11:58:32 arch kernel: 3 base 00A0000000 mask 7FE0000000 uncachable
    May 11 11:58:32 arch kernel: 4 base 00C0000000 mask 7FC0000000 uncachable
    May 11 11:58:32 arch kernel: 5 disabled
    May 11 11:58:32 arch kernel: 6 disabled
    May 11 11:58:32 arch kernel: 7 disabled
    May 11 11:58:32 arch kernel: 8 disabled
    May 11 11:58:32 arch kernel: 9 disabled
    May 11 11:58:32 arch kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    May 11 11:58:32 arch kernel: e820: update [mem 0x8f800000-0xffffffff] usable ==> reserved
    May 11 11:58:32 arch kernel: e820: last_pfn = 0x8f800 max_arch_pfn = 0x400000000
    May 11 11:58:32 arch kernel: Scanning 1 areas for low memory corruption
    May 11 11:58:32 arch kernel: Base memory trampoline at [ffff880000082000] 82000 size 24576
    May 11 11:58:32 arch kernel: Using GB pages for direct mapping
    May 11 11:58:32 arch kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
    May 11 11:58:32 arch kernel: [mem 0x00000000-0x000fffff] page 4k
    May 11 11:58:32 arch kernel: BRK [0x02b39000, 0x02b39fff] PGTABLE
    May 11 11:58:32 arch kernel: BRK [0x02b3a000, 0x02b3afff] PGTABLE
    May 11 11:58:32 arch kernel: BRK [0x02b3b000, 0x02b3bfff] PGTABLE
    May 11 11:58:32 arch kernel: init_memory_mapping: [mem 0x46ee00000-0x46effffff]
    May 11 11:58:32 arch kernel: [mem 0x46ee00000-0x46effffff] page 2M
    May 11 11:58:32 arch kernel: BRK [0x02b3c000, 0x02b3cfff] PGTABLE
    May 11 11:58:32 arch kernel: init_memory_mapping: [mem 0x46c000000-0x46edfffff]
    May 11 11:58:32 arch kernel: [mem 0x46c000000-0x46edfffff] page 2M
    May 11 11:58:32 arch kernel: init_memory_mapping: [mem 0x400000000-0x46bffffff]
    May 11 11:58:32 arch kernel: [mem 0x400000000-0x43fffffff] page 1G
    May 11 11:58:32 arch kernel: [mem 0x440000000-0x46bffffff] page 2M
    May 11 11:58:32 arch kernel: init_memory_mapping: [mem 0x00100000-0x6e6effff]
    May 11 11:58:32 arch kernel: [mem 0x00100000-0x001fffff] page 4k
    May 11 11:58:32 arch kernel: [mem 0x00200000-0x6e5fffff] page 2M
    May 11 11:58:32 arch kernel: [mem 0x6e600000-0x6e6effff] page 4k
    May 11 11:58:32 arch kernel: init_memory_mapping: [mem 0x6faf0000-0x8eebefff]
    May 11 11:58:32 arch kernel: [mem 0x6faf0000-0x6fbfffff] page 4k
    May 11 11:58:32 arch kernel: [mem 0x6fc00000-0x8edfffff] page 2M
    May 11 11:58:32 arch kernel: [mem 0x8ee00000-0x8eebefff] page 4k
    May 11 11:58:32 arch kernel: BRK [0x02b3d000, 0x02b3dfff] PGTABLE
    May 11 11:58:32 arch kernel: BRK [0x02b3e000, 0x02b3efff] PGTABLE
    May 11 11:58:32 arch kernel: init_memory_mapping: [mem 0x8f7ff000-0x8f7fffff]
    May 11 11:58:32 arch kernel: [mem 0x8f7ff000-0x8f7fffff] page 4k
    May 11 11:58:32 arch kernel: init_memory_mapping: [mem 0x100000000-0x3ffffffff]
    May 11 11:58:32 arch kernel: [mem 0x100000000-0x3ffffffff] page 1G
    May 11 11:58:32 arch kernel: RAMDISK: [mem 0x37622000-0x37b08fff]
    May 11 11:58:32 arch kernel: ACPI: RSDP 000000008f7fe014 000024 (v02 LENOVO)
    May 11 11:58:32 arch kernel: ACPI: XSDT 000000008f7fe210 0000B4 (v01 LENOVO CB-01 00000001 01000013)
    May 11 11:58:32 arch kernel: ACPI: FACP 000000008f7f7000 00010C (v05 LENOVO CB-01 00000001 ACPI 00040000)
    May 11 11:58:32 arch kernel: ACPI: DSDT 000000008f7e7000 00C690 (v01 LENOVO CB-01 00000001 ACPI 00040000)
    May 11 11:58:32 arch kernel: ACPI: FACS 000000008f7ba000 000040
    May 11 11:58:32 arch kernel: ACPI: SLIC 000000008f7fd000 000176 (v01 LENOVO CB-01 00000001 ACPI 00040000)
    May 11 11:58:32 arch kernel: ACPI: UEFI 000000008f7fc000 000236 (v01 LENOVO CB-01 00000001 ACPI 00040000)
    May 11 11:58:32 arch kernel: ACPI: FPDT 000000008f7fa000 000044 (v01 LENOVO CB-01 00000001 ACPI 00040000)
    May 11 11:58:32 arch kernel: ACPI: MSDM 000000008f7f9000 000055 (v03 LENOVO CB-01 00000001 ACPI 00040000)
    May 11 11:58:32 arch kernel: ACPI: ASF! 000000008f7f8000 0000A5 (v32 LENOVO CB-01 00000001 ACPI 00040000)
    May 11 11:58:32 arch kernel: ACPI: HPET 000000008f7f6000 000038 (v01 LENOVO CB-01 00000001 ACPI 00040000)
    May 11 11:58:32 arch kernel: ACPI: APIC 000000008f7f5000 00008C (v03 LENOVO CB-01 00000001 ACPI 00040000)
    May 11 11:58:32 arch kernel: ACPI: MCFG 000000008f7f4000 00003C (v01 LENOVO CB-01 00000001 ACPI 00040000)
    May 11 11:58:32 arch kernel: ACPI: SSDT 000000008f7e6000 000838 (v01 LENOVO CB-01 00000001 ACPI 00040000)
    May 11 11:58:32 arch kernel: ACPI: BOOT 000000008f7e4000 000028 (v01 LENOVO CB-01 00000001 ACPI 00040000)
    May 11 11:58:32 arch kernel: ACPI: ASPT 000000008f7e2000 000034 (v07 LENOVO CB-01 00000001 ACPI 00040000)
    May 11 11:58:32 arch kernel: ACPI: DBGP 000000008f7e1000 000034 (v01 LENOVO CB-01 00000001 ACPI 00040000)
    May 11 11:58:32 arch kernel: ACPI: SSDT 000000008f7d9000 000539 (v01 LENOVO CB-01 00000001 ACPI 00040000)
    May 11 11:58:32 arch kernel: ACPI: SSDT 000000008f7d8000 000AD8 (v01 LENOVO CB-01 00000001 ACPI 00040000)
    May 11 11:58:32 arch kernel: ACPI: SSDT 000000008f7d4000 00326E (v01 LENOVO CB-01 00000001 ACPI 00040000)
    May 11 11:58:32 arch kernel: ACPI: SSDT 000000008f7d1000 0012FF (v01 LENOVO CB-01 00000001 ACPI 00040000)
    May 11 11:58:32 arch kernel: ACPI: BGRT 000000008f7d3000 000038 (v01 LENOVO CB-01 00000001 ACPI 00040000)
    May 11 11:58:32 arch kernel: ACPI: Local APIC address 0xfee00000
    May 11 11:58:32 arch kernel: No NUMA configuration found
    May 11 11:58:32 arch kernel: Faking a node at [mem 0x0000000000000000-0x000000046effffff]
    May 11 11:58:32 arch kernel: Initmem setup node 0 [mem 0x00000000-0x46effffff]
    May 11 11:58:32 arch kernel: NODE_DATA [mem 0x46eff7000-0x46effbfff]
    May 11 11:58:32 arch kernel: [ffffea0000000000-ffffea0011bfffff] PMD -> [ffff88045e600000-ffff88046e5fffff] on node 0
    May 11 11:58:32 arch kernel: Zone ranges:
    May 11 11:58:32 arch kernel: DMA [mem 0x00001000-0x00ffffff]
    May 11 11:58:32 arch kernel: DMA32 [mem 0x01000000-0xffffffff]
    May 11 11:58:32 arch kernel: Normal [mem 0x100000000-0x46effffff]
    May 11 11:58:32 arch kernel: Movable zone start for each node
    May 11 11:58:32 arch kernel: Early memory node ranges
    May 11 11:58:32 arch kernel: node 0: [mem 0x00001000-0x0006efff]
    May 11 11:58:32 arch kernel: node 0: [mem 0x00070000-0x00087fff]
    May 11 11:58:32 arch kernel: node 0: [mem 0x00100000-0x6e6effff]
    May 11 11:58:32 arch kernel: node 0: [mem 0x6faf0000-0x8eebefff]
    May 11 11:58:32 arch kernel: node 0: [mem 0x8f7ff000-0x8f7fffff]
    May 11 11:58:32 arch kernel: node 0: [mem 0x100000000-0x46effffff]
    May 11 11:58:32 arch kernel: On node 0 totalpages: 4180550
    May 11 11:58:32 arch kernel: DMA zone: 64 pages used for memmap
    May 11 11:58:32 arch kernel: DMA zone: 24 pages reserved
    May 11 11:58:32 arch kernel: DMA zone: 3974 pages, LIFO batch:0
    May 11 11:58:32 arch kernel: DMA32 zone: 9003 pages used for memmap
    May 11 11:58:32 arch kernel: DMA32 zone: 576192 pages, LIFO batch:31
    May 11 11:58:32 arch kernel: Normal zone: 56256 pages used for memmap
    May 11 11:58:32 arch kernel: Normal zone: 3600384 pages, LIFO batch:31
    May 11 11:58:32 arch kernel: ACPI: PM-Timer IO Port: 0x1808
    May 11 11:58:32 arch kernel: ACPI: Local APIC address 0xfee00000
    May 11 11:58:32 arch kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
    May 11 11:58:32 arch kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
    May 11 11:58:32 arch kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
    May 11 11:58:32 arch kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
    May 11 11:58:32 arch kernel: ACPI: LAPIC (acpi_id[0x05] lapic_id[0x04] enabled)
    May 11 11:58:32 arch kernel: ACPI: LAPIC (acpi_id[0x06] lapic_id[0x05] enabled)
    May 11 11:58:32 arch kernel: ACPI: LAPIC (acpi_id[0x07] lapic_id[0x06] enabled)
    May 11 11:58:32 arch kernel: ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] enabled)
    May 11 11:58:32 arch kernel: ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
    May 11 11:58:32 arch kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
    May 11 11:58:32 arch kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    May 11 11:58:32 arch kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    May 11 11:58:32 arch kernel: ACPI: IRQ0 used by override.
    May 11 11:58:32 arch kernel: ACPI: IRQ2 used by override.
    May 11 11:58:32 arch kernel: ACPI: IRQ9 used by override.
    May 11 11:58:32 arch kernel: Using ACPI (MADT) for SMP configuration information
    May 11 11:58:32 arch kernel: ACPI: HPET id: 0x8086a201 base: 0xfed00000
    May 11 11:58:32 arch kernel: smpboot: Allowing 8 CPUs, 0 hotplug CPUs
    May 11 11:58:32 arch kernel: nr_irqs_gsi: 40
    May 11 11:58:32 arch kernel: PM: Registered nosave memory: [mem 0x0006f000-0x0006ffff]
    May 11 11:58:32 arch kernel: PM: Registered nosave memory: [mem 0x00088000-0x000bffff]
    May 11 11:58:32 arch kernel: PM: Registered nosave memory: [mem 0x000c0000-0x000fffff]
    May 11 11:58:32 arch kernel: PM: Registered nosave memory: [mem 0x6e6f0000-0x6faeffff]
    May 11 11:58:32 arch kernel: PM: Registered nosave memory: [mem 0x8eebf000-0x8f0befff]
    May 11 11:58:32 arch kernel: PM: Registered nosave memory: [mem 0x8f0bf000-0x8f6befff]
    May 11 11:58:32 arch kernel: PM: Registered nosave memory: [mem 0x8f6bf000-0x8f7befff]
    May 11 11:58:32 arch kernel: PM: Registered nosave memory: [mem 0x8f7bf000-0x8f7fefff]
    May 11 11:58:32 arch kernel: PM: Registered nosave memory: [mem 0x8f800000-0x8fffffff]
    May 11 11:58:32 arch kernel: PM: Registered nosave memory: [mem 0x90000000-0xdfffffff]
    May 11 11:58:32 arch kernel: PM: Registered nosave memory: [mem 0xe0000000-0xefffffff]
    May 11 11:58:32 arch kernel: PM: Registered nosave memory: [mem 0xf0000000-0xfeafffff]
    May 11 11:58:32 arch kernel: PM: Registered nosave memory: [mem 0xfeb00000-0xfeb0ffff]
    May 11 11:58:32 arch kernel: PM: Registered nosave memory: [mem 0xfeb10000-0xfebfffff]
    May 11 11:58:32 arch kernel: PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
    May 11 11:58:32 arch kernel: PM: Registered nosave memory: [mem 0xfec01000-0xfecfffff]
    May 11 11:58:32 arch kernel: PM: Registered nosave memory: [mem 0xfed00000-0xfee00fff]
    May 11 11:58:32 arch kernel: PM: Registered nosave memory: [mem 0xfee01000-0xffb7ffff]
    May 11 11:58:32 arch kernel: PM: Registered nosave memory: [mem 0xffb80000-0xffffffff]
    May 11 11:58:32 arch kernel: e820: [mem 0x90000000-0xdfffffff] available for PCI devices
    May 11 11:58:32 arch kernel: Booting paravirtualized kernel on bare hardware
    May 11 11:58:32 arch kernel: setup_percpu: NR_CPUS:128 nr_cpumask_bits:128 nr_cpu_ids:8 nr_node_ids:1
    May 11 11:58:32 arch kernel: PERCPU: Embedded 29 pages/cpu @ffff88046ec00000 s87040 r8192 d23552 u262144
    May 11 11:58:32 arch kernel: pcpu-alloc: s87040 r8192 d23552 u262144 alloc=1*2097152
    May 11 11:58:32 arch kernel: pcpu-alloc: [0] 0 1 2 3 4 5 6 7
    May 11 11:58:32 arch kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 4115203
    May 11 11:58:32 arch kernel: Policy zone: Normal
    May 11 11:58:32 arch kernel: Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=4a950c38-be98-4678-9a12-9caebece5745 rw quiet
    May 11 11:58:32 arch kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
    May 11 11:58:32 arch kernel: xsave: enabled xstate_bv 0x7, cntxt size 0x340
    May 11 11:58:32 arch kernel: Checking aperture...
    May 11 11:58:32 arch kernel: No AGP bridge found
    May 11 11:58:32 arch kernel: Calgary: detecting Calgary via BIOS EBDA area
    May 11 11:58:32 arch kernel: Calgary: Unable to locate Rio Grande table in EBDA - bailing!
    May 11 11:58:32 arch kernel: Memory: 16298272K/16722200K available (5230K kernel code, 857K rwdata, 1632K rodata, 1120K init, 1288K b
    May 11 11:58:32 arch kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
    May 11 11:58:32 arch kernel: Preemptible hierarchical RCU implementation.
    May 11 11:58:32 arch kernel: RCU dyntick-idle grace-period acceleration is enabled.
    May 11 11:58:32 arch kernel: Dump stacks of tasks blocking RCU-preempt GP.
    May 11 11:58:32 arch kernel: RCU restricting CPUs from NR_CPUS=128 to nr_cpu_ids=8.
    May 11 11:58:32 arch kernel: RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
    May 11 11:58:32 arch kernel: NR_IRQS:8448 nr_irqs:744 16
    May 11 11:58:32 arch kernel: Console: colour dummy device 80x25
    May 11 11:58:32 arch kernel: console [tty0] enabled
    May 11 11:58:32 arch kernel: allocated 67108864 bytes of page_cgroup
    May 11 11:58:32 arch kernel: please try 'cgroup_disable=memory' option if you don't want memory cgroups
    May 11 11:58:32 arch kernel: hpet clockevent registered
    May 11 11:58:32 arch kernel: tsc: Fast TSC calibration using PIT
    May 11 11:58:32 arch kernel: tsc: Detected 2394.453 MHz processor
    May 11 11:58:32 arch kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 4790.44 BogoMIPS (lpj=7981510
    May 11 11:58:32 arch kernel: pid_max: default: 32768 minimum: 301
    May 11 11:58:32 arch kernel: ACPI: Core revision 20131218
    May 11 11:58:32 arch kernel: ACPI: All ACPI Tables successfully acquired
    May 11 11:58:32 arch kernel: Security Framework initialized
    May 11 11:58:32 arch kernel: Yama: becoming mindful.
    May 11 11:58:32 arch kernel: Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes)
    May 11 11:58:32 arch kernel: Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes)
    May 11 11:58:32 arch kernel: Mount-cache hash table entries: 32768 (order: 6, 262144 bytes)
    May 11 11:58:32 arch kernel: Mountpoint-cache hash table entries: 32768 (order: 6, 262144 bytes)
    May 11 11:58:32 arch kernel: Initializing cgroup subsys memory
    May 11 11:58:32 arch kernel: Initializing cgroup subsys devices
    May 11 11:58:32 arch kernel: Initializing cgroup subsys freezer
    May 11 11:58:32 arch kernel: Initializing cgroup subsys net_cls
    May 11 11:58:32 arch kernel: Initializing cgroup subsys blkio
    May 11 11:58:32 arch kernel: CPU: Physical Processor ID: 0
    May 11 11:58:32 arch kernel: CPU: Processor Core ID: 0
    May 11 11:58:32 arch kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
    ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
    May 11 11:58:32 arch kernel: mce: CPU supports 9 MCE banks
    May 11 11:58:32 arch kernel: CPU0: Thermal monitoring enabled (TM1)
    May 11 11:58:32 arch kernel: Last level iTLB entries: 4KB 1024, 2MB 1024, 4MB 1024
    Last level dTLB entries: 4KB 1024, 2MB 1024, 4MB 1024, 1GB 4
    tlb_flushall_shift: 6
    May 11 11:58:32 arch kernel: Freeing SMP alternatives memory: 20K (ffffffff819f0000 - ffffffff819f5000)
    May 11 11:58:32 arch kernel: ftrace: allocating 20028 entries in 79 pages
    May 11 11:58:32 arch kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    May 11 11:58:32 arch kernel: smpboot: CPU0: Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz (fam: 06, model: 3c, stepping: 03)
    May 11 11:58:32 arch kernel: TSC deadline timer enabled
    May 11 11:58:32 arch kernel: Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
    May 11 11:58:32 arch kernel: ... version: 3
    May 11 11:58:32 arch kernel: ... bit width: 48
    May 11 11:58:32 arch kernel: ... generic registers: 4
    May 11 11:58:32 arch kernel: ... value mask: 0000ffffffffffff
    May 11 11:58:32 arch kernel: ... max period: 0000ffffffffffff
    May 11 11:58:32 arch kernel: ... fixed-purpose events: 3
    May 11 11:58:32 arch kernel: ... event mask: 000000070000000f
    May 11 11:58:32 arch kernel: x86: Booting SMP configuration:
    May 11 11:58:32 arch kernel: .... node #0, CPUs: #1
    May 11 11:58:32 arch kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
    May 11 11:58:32 arch kernel: #2 #3 #4 #5 #6 #7
    May 11 11:58:32 arch kernel: x86: Booted up 1 node, 8 CPUs
    May 11 11:58:32 arch kernel: smpboot: Total of 8 processors activated (38326.55 BogoMIPS)
    May 11 11:58:32 arch kernel: devtmpfs: initialized
    May 11 11:58:32 arch kernel: PM: Registering ACPI NVS region [mem 0x8f6bf000-0x8f7befff] (1048576 bytes)
    May 11 11:58:32 arch kernel: pinctrl core: initialized pinctrl subsystem
    May 11 11:58:32 arch kernel: RTC time: 9:58:25, date: 05/11/14
    May 11 11:58:32 arch kernel: NET: Registered protocol family 16
    May 11 11:58:32 arch kernel: cpuidle: using governor ladder
    May 11 11:58:32 arch kernel: cpuidle: using governor menu
    May 11 11:58:32 arch kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
    May 11 11:58:32 arch kernel: ACPI: bus type PCI registered
    May 11 11:58:32 arch kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
    May 11 11:58:32 arch kernel: PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
    May 11 11:58:32 arch kernel: PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820
    May 11 11:58:32 arch kernel: PCI: Using configuration type 1 for base access
    May 11 11:58:32 arch kernel: bio: create slab <bio-0> at 0
    May 11 11:58:32 arch kernel: ACPI: Added _OSI(Module Device)
    May 11 11:58:32 arch kernel: ACPI: Added _OSI(Processor Device)
    May 11 11:58:32 arch kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
    May 11 11:58:32 arch kernel: ACPI: Added _OSI(Processor Aggregator Device)
    May 11 11:58:32 arch kernel: ACPI: Executed 1 blocks of module-level executable AML code
    May 11 11:58:32 arch kernel: [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
    May 11 11:58:32 arch kernel: ACPI: SSDT 000000008f658c18 0003D3 (v01 PmRef Cpu0Cst 00003001 INTL 20130117)
    May 11 11:58:32 arch kernel: ACPI: Dynamic OEM Table Load:
    May 11 11:58:32 arch kernel: ACPI: SSDT (null) 0003D3 (v01 PmRef Cpu0Cst 00003001 INTL 20130117)
    May 11 11:58:32 arch kernel: ACPI: SSDT 000000008f658618 0005AA (v01 PmRef ApIst 00003000 INTL 20130117)
    May 11 11:58:32 arch kernel: ACPI: Dynamic OEM Table Load:
    May 11 11:58:32 arch kernel: ACPI: SSDT (null) 0005AA (v01 PmRef ApIst 00003000 INTL 20130117)
    May 11 11:58:32 arch kernel: ACPI: SSDT 000000008f657d98 000119 (v01 PmRef ApCst 00003000 INTL 20130117)
    May 11 11:58:32 arch kernel: ACPI: Dynamic OEM Table Load:
    May 11 11:58:32 arch kernel: ACPI: SSDT (null) 000119 (v01 PmRef ApCst 00003000 INTL 20130117)
    May 11 11:58:32 arch kernel: ACPI: Interpreter enabled
    May 11 11:58:32 arch kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131218/hwxface-580)
    May 11 11:58:32 arch kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131218/hwxface-580)
    May 11 11:58:32 arch kernel: ACPI: (supports S0 S3 S4 S5)
    May 11 11:58:32 arch kernel: ACPI: Using IOAPIC for interrupt routing
    May 11 11:58:32 arch kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
    May 11 11:58:32 arch kernel: ACPI: No dock devices found.
    May 11 11:58:32 arch kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-fe])
    May 11 11:58:32 arch kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
    May 11 11:58:32 arch kernel: acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
    May 11 11:58:32 arch kernel: PCI host bridge to bus 0000:00
    May 11 11:58:32 arch kernel: pci_bus 0000:00: root bus resource [bus 00-fe]
    May 11 11:58:32 arch kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
    May 11 11:58:32 arch kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
    May 11 11:58:32 arch kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
    May 11 11:58:32 arch kernel: pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000c3fff]
    May 11 11:58:32 arch kernel: pci_bus 0000:00: root bus resource [mem 0x000c4000-0x000c7fff]
    May 11 11:58:32 arch kernel: pci_bus 0000:00: root bus resource [mem 0x000c8000-0x000cbfff]
    May 11 11:58:32 arch kernel: pci_bus 0000:00: root bus resource [mem 0x000cc000-0x000cffff]
    May 11 11:58:32 arch kernel: pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d3fff]
    May 11 11:58:32 arch kernel: pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff]
    May 11 11:58:32 arch kernel: pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff]
    May 11 11:58:32 arch kernel: pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff]
    May 11 11:58:32 arch kernel: pci_bus 0000:00: root bus resource [mem 0x000e0000-0x000e3fff]
    May 11 11:58:32 arch kernel: pci_bus 0000:00: root bus resource [mem 0x000e4000-0x000e7fff]
    May 11 11:58:32 arch kernel: pci_bus 0000:00: root bus resource [mem 0x000e8000-0x000ebfff]
    May 11 11:58:32 arch kernel: pci_bus 0000:00: root bus resource [mem 0x000ec000-0x000effff]
    May 11 11:58:32 arch kernel: pci_bus 0000:00: root bus resource [mem 0x90000000-0xfeafffff]
    May 11 11:58:32 arch kernel: pci 0000:00:00.0: [8086:0c04] type 00 class 0x060000
    May 11 11:58:32 arch kernel: pci 0000:00:01.0: [8086:0c01] type 01 class 0x060400
    May 11 11:58:32 arch kernel: pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
    May 11 11:58:32 arch kernel: pci 0000:00:01.0: System wakeup disabled by ACPI
    May 11 11:58:32 arch kernel: pci 0000:00:01.1: [8086:0c05] type 01 class 0x060400
    May 11 11:58:32 arch kernel: pci 0000:00:01.1: PME# supported from D0 D3hot D3cold
    May 11 11:58:32 arch kernel: pci 0000:00:01.1: System wakeup disabled by ACPI
    May 11 11:58:32 arch kernel: pci 0000:00:14.0: [8086:8c31] type 00 class 0x0c0330
    May 11 11:58:32 arch kernel: pci 0000:00:14.0: reg 0x10: [mem 0xd5200000-0xd520ffff 64bit]
    May 11 11:58:32 arch kernel: pci 0000:00:14.0: PME# supported from D3hot D3cold
    May 11 11:58:32 arch kernel: pci 0000:00:14.0: System wakeup disabled by ACPI
    May 11 11:58:32 arch kernel: pci 0000:00:16.0: [8086:8c3a] type 00 class 0x078000
    May 11 11:58:32 arch kernel: pci 0000:00:16.0: reg 0x10: [mem 0xd5214000-0xd521400f 64bit]
    May 11 11:58:32 arch kernel: pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
    May 11 11:58:32 arch kernel: pci 0000:00:1a.0: [8086:8c2d] type 00 class 0x0c0320
    May 11 11:58:32 arch kernel: pci 0000:00:1a.0: reg 0x10: [mem 0xd5219000-0xd52193ff]
    May 11 11:58:32 arch kernel: pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
    May 11 11:58:32 arch kernel: pci 0000:00:1a.0: System wakeup disabled by ACPI
    May 11 11:58:32 arch kernel: pci 0000:00:1b.0: [8086:8c20] type 00 class 0x040300
    May 11 11:58:32 arch kernel: pci 0000:00:1b.0: reg 0x10: [mem 0xd5210000-0xd5213fff 64bit]
    May 11 11:58:32 arch kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
    May 11 11:58:32 arch kernel: pci 0000:00:1c.0: [8086:8c16] type 01 class 0x060400
    May 11 11:58:32 arch kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
    May 11 11:58:32 arch kernel: pci 0000:00:1c.0: System wakeup disabled by ACPI
    May 11 11:58:32 arch kernel: pci 0000:00:1c.4: [8086:8c18] type 01 class 0x060400
    May 11 11:58:32 arch kernel: pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
    May 11 11:58:32 arch kernel: pci 0000:00:1d.0: [8086:8c26] type 00 class 0x0c0320
    May 11 11:58:32 arch kernel: pci 0000:00:1d.0: reg 0x10: [mem 0xd5218000-0xd52183ff]
    May 11 11:58:32 arch kernel: pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
    May 11 11:58:32 arch kernel: pci 0000:00:1d.0: System wakeup disabled by ACPI
    May 11 11:58:32 arch kernel: pci 0000:00:1f.0: [8086:8c49] type 00 class 0x060100
    May 11 11:58:32 arch kernel: pci 0000:00:1f.2: [8086:8c03] type 00 class 0x010601
    May 11 11:58:32 arch kernel: pci 0000:00:1f.2: reg 0x10: [io 0x6048-0x604f]
    May 11 11:58:32 arch kernel: pci 0000:00:1f.2: reg 0x14: [io 0x6054-0x6057]
    May 11 11:58:32 arch kernel: pci 0000:00:1f.2: reg 0x18: [io 0x6040-0x6047]
    May 11 11:58:32 arch kernel: pci 0000:00:1f.2: reg 0x1c: [io 0x6050-0x6053]
    May 11 11:58:32 arch kernel: pci 0000:00:1f.2: reg 0x20: [io 0x6020-0x603f]
    May 11 11:58:32 arch kernel: pci 0000:00:1f.2: reg 0x24: [mem 0xd5217000-0xd52177ff]
    May 11 11:58:32 arch kernel: pci 0000:00:1f.2: PME# supported from D3hot
    May 11 11:58:32 arch kernel: pci 0000:00:1f.3: [8086:8c22] type 00 class 0x0c0500
    May 11 11:58:32 arch kernel: pci 0000:00:1f.3: reg 0x10: [mem 0xd5215000-0xd52150ff 64bit]
    May 11 11:58:32 arch kernel: pci 0000:00:1f.3: reg 0x20: [io 0x6000-0x601f]
    May 11 11:58:32 arch kernel: pci 0000:01:00.0: [10de:0fcd] type 00 class 0x030000
    May 11 11:58:32 arch kernel: pci 0000:01:00.0: reg 0x10: [mem 0xd3000000-0xd3ffffff]
    May 11 11:58:32 arch kernel: pci 0000:01:00.0: reg 0x14: [mem 0xa0000000-0xafffffff 64bit pref]
    May 11 11:58:32 arch kernel: pci 0000:01:00.0: reg 0x1c: [mem 0xb0000000-0xb1ffffff 64bit pref]
    May 11 11:58:32 arch kernel: pci 0000:01:00.0: reg 0x24: [io 0x5000-0x507f]
    May 11 11:58:32 arch kernel: pci 0000:01:00.0: reg 0x30: [mem 0xfff80000-0xffffffff pref]
    May 11 11:58:32 arch kernel: pci 0000:01:00.1: [10de:0e1b] type 00 class 0x040300
    May 11 11:58:32 arch kernel: pci 0000:01:00.1: reg 0x10: [mem 0xd4000000-0xd4003fff]
    May 11 11:58:32 arch kernel: pci 0000:00:01.0: PCI bridge to [bus 01-06]
    May 11 11:58:32 arch kernel: pci 0000:00:01.0: bridge window [io 0x5000-0x5fff]
    May 11 11:58:32 arch kernel: pci 0000:00:01.0: bridge window [mem 0xd3000000-0xd4ffffff]
    May 11 11:58:32 arch kernel: pci 0000:00:01.0: bridge window [mem 0xa0000000-0xbfffffff 64bit pref]
    May 11 11:58:32 arch kernel: pci 0000:07:00.0: [10de:0fcd] type 00 class 0x030200
    May 11 11:58:32 arch kernel: pci 0000:07:00.0: reg 0x10: [mem 0xd2000000-0xd2ffffff]
    May 11 11:58:32 arch kernel: pci 0000:07:00.0: reg 0x14: [mem 0xc0000000-0xcfffffff 64bit pref]
    May 11 11:58:32 arch kernel: pci 0000:07:00.0: reg 0x1c: [mem 0xd0000000-0xd1ffffff 64bit pref]
    May 11 11:58:32 arch kernel: pci 0000:07:00.0: reg 0x24: [io 0x4000-0x407f]
    May 11 11:58:32 arch kernel: pci 0000:07:00.0: reg 0x30: [mem 0xfff80000-0xffffffff pref]
    May 11 11:58:32 arch kernel: pci 0000:00:01.1: PCI bridge to [bus 07]
    May 11 11:58:32 arch kernel: pci 0000:00:01.1: bridge window [io 0x4000-0x4fff]
    May 11 11:58:32 arch kernel: pci 0000:00:01.1: bridge window [mem 0xd2000000-0xd2ffffff]
    May 11 11:58:32 arch kernel: pci 0000:00:01.1: bridge window [mem 0xc0000000-0xd1ffffff 64bit pref]
    May 11 11:58:32 arch kernel: pci 0000:08:00.0: [1969:10a1] type 00 class 0x020000
    May 11 11:58:32 arch kernel: pci 0000:08:00.0: reg 0x10: [mem 0xd5100000-0xd513ffff 64bit]
    May 11 11:58:32 arch kernel: pci 0000:08:00.0: reg 0x18: [io 0x3000-0x307f]
    May 11 11:58:32 arch kernel: pci 0000:08:00.0: PME# supported from D0 D1 D2 D3hot D3cold
    May 11 11:58:32 arch kernel: pci 0000:00:1c.0: PCI bridge to [bus 08]
    May 11 11:58:32 arch kernel: pci 0000:00:1c.0: bridge window [io 0x3000-0x3fff]
    May 11 11:58:32 arch kernel: pci 0000:00:1c.0: bridge window [mem 0xd5100000-0xd51fffff]
    May 11 11:58:32 arch kernel: pci 0000:09:00.0: [8086:0888] type 00 class 0x028000
    May 11 11:58:32 arch kernel: pci 0000:09:00.0: reg 0x10: [mem 0xd5000000-0xd5001fff 64bit]
    May 11 11:58:32 arch kernel: pci 0000:09:00.0: PME# supported from D0 D3hot D3cold
    May 11 11:58:32 arch kernel: pci 0000:00:1c.4: PCI bridge to [bus 09]
    May 11 11:58:32 arch kernel: pci 0000:00:1c.4: bridge window [mem 0xd5000000-0xd50fffff]
    May 11 11:58:32 arch kernel: acpi PNP0A08:00: Disabling ASPM (FADT indicates it is unsupported)
    May 11 11:58:32 arch kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
    May 11 11:58:32 arch kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
    May 11 11:58:32 arch kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
    May 11 11:58:32 arch kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
    May 11 11:58:32 arch kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
    May 11 11:58:32 arch kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
    May 11 11:58:32 arch kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
    May 11 11:58:32 arch kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
    May 11 11:58:32 arch kernel: ACPI: Enabled 7 GPEs in block 00 to 3F
    May 11 11:58:32 arch kernel: ACPI : EC: GPE = 0x17, I/O: command/status = 0x66, data = 0x62
    May 11 11:58:32 arch kernel: vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=none,locks=none
    May 11 11:58:32 arch kernel: vgaarb: loaded
    May 11 11:58:32 arch kernel: vgaarb: bridge control possible 0000:01:00.0
    May 11 11:58:32 arch kernel: PCI: Using ACPI for IRQ routing
    May 11 11:58:32 arch kernel: PCI: pci_cache_line_size set to 64 bytes
    May 11 11:58:32 arch kernel: e820: reserve RAM buffer [mem 0x0006f000-0x0006ffff]
    May 11 11:58:32 arch kernel: e820: reserve RAM buffer [mem 0x00088000-0x0008ffff]
    May 11 11:58:32 arch kernel: e820: reserve RAM buffer [mem 0x6e6f0000-0x6fffffff]
    May 11 11:58:32 arch kernel: e820: reserve RAM buffer [mem 0x8eebf000-0x8fffffff]
    May 11 11:58:32 arch kernel: e820: reserve RAM buffer [mem 0x8f800000-0x8fffffff]
    May 11 11:58:32 arch kernel: e820: reserve RAM buffer [mem 0x46f000000-0x46fffffff]
    May 11 11:58:32 arch kernel: NetLabel: Initializing
    May 11 11:58:32 arch kernel: NetLabel: domain hash size = 128
    May 11 11:58:32 arch kernel: NetLabel: protocols = UNLABELED CIPSOv4
    May 11 11:58:32 arch kernel: NetLabel: unlabeled traffic allowed by default
    May 11 11:58:32 arch kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
    May 11 11:58:32 arch kernel: hpet0: 8 comparators, 64-bit 14.318180 MHz counter
    May 11 11:58:32 arch kernel: Switched to clocksource hpet
    May 11 11:58:32 arch kernel: pnp: PnP ACPI init
    May 11 11:58:32 arch kernel: ACPI: bus type PNP registered
    May 11 11:58:32 arch kernel: pnp 00:00: [dma 4]
    May 11 11:58:32 arch kernel: pnp 00:00: Plug and Play ACPI device, IDs PNP0200 (active)
    May 11 11:58:32 arch kernel: pnp 00:01: Plug and Play ACPI device, IDs INT0800 (active)
    May 11 11:58:32 arch kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0103 (active)
    May 11 11:58:32 arch kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
    May 11 11:58:32 arch kernel: system 00:04: [io 0x0680-0x069f] has been reserved
    May 11 11:58:32 arch kernel: system 00:04: [io 0xffff] has been reserved
    May 11 11:58:32 arch kernel: system 00:04: [io 0xffff] has been reserved
    May 11 11:58:32 arch kernel: system 00:04: [io 0xffff] has been reserved
    May 11 11:58:32 arch kernel: system 00:04: [io 0x0400-0x0453] has been reserved
    May 11 11:58:32 arch kernel: system 00:04: [io 0x0800-0x08fe] has been reserved
    May 11 11:58:32 arch kernel: system 00:04: [io 0x0900-0x09fe] has been reserved
    May 11 11:58:32 arch kernel: system 00:04: [io 0x0a00-0x0afe] has been reserved
    May 11 11:58:32 arch kernel: system 00:04: [io 0x0b00-0x0bfe] has been reserved
    May 11 11:58:32 arch kernel: system 00:04: [io 0x1800-0x18fe] could not be reserved
    May 11 11:58:32 arch kernel: system 00:04: [io 0x164e-0x164f] has been reserved
    May 11 11:58:32 arch kernel: system 00:04: [io 0x0d60-0x0d63] has been reserved
    May 11 11:58:32 arch kernel: system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
    May 11 11:58:32 arch kernel: system 00:05: [io 0x0800-0x087f] has been reserved
    May 11 11:58:32 arch kernel: system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active)
    May 11 11:58:32 arch kernel: pnp 00:06: Plug and Play ACPI device, IDs PNP0b00 (active)
    May 11 11:58:32 arch kernel: system 00:07: [io 0x1854-0x1857] has been reserved
    May 11 11:58:32 arch kernel: system 00:07: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
    May 11 11:58:32 arch kernel: pnp 00:08: Plug and Play ACPI device, IDs PNP0303 (active)
    May 11 11:58:32 arch kernel: pnp 00:09: Plug and Play ACPI device, IDs ETD060b PNP0f13 (active)
    May 11 11:58:32 arch kernel: system 00:0a: [mem 0xfed1c000-0xfed1ffff] has been reserved
    May 11 11:58:32 arch kernel: system 00:0a: [mem 0xfed10000-0xfed17fff] has been reserved
    May 11 11:58:32 arch kernel: system 00:0a: [mem 0xfed18000-0xfed18fff] has been reserved
    May 11 11:58:32 arch kernel: system 00:0a: [mem 0xfed19000-0xfed19fff] has been reserved
    May 11 11:58:32 arch kernel: system 00:0a: [mem 0xe0000000-0xefffffff] has been reserved
    May 11 11:58:32 arch kernel: system 00:0a: [mem 0xfed20000-0xfed3ffff] has been reserved
    May 11 11:58:32 arch kernel: system 00:0a: [mem 0xfed90000-0xfed93fff] has been reserved
    May 11 11:58:32 arch kernel: system 00:0a: [mem 0xff000000-0xffffffff] could not be reserved
    May 11 11:58:32 arch kernel: system 00:0a: [mem 0xfee00000-0xfeefffff] could not be reserved
    May 11 11:58:32 arch kernel: system 00:0a: [mem 0x90020000-0x90020fff] has been reserved
    May 11 11:58:32 arch kernel: system 00:0a: [mem 0x90010000-0x9001ffff] has been reserved
    May 11 11:58:32 arch kernel: system 00:0a: Plug and Play ACPI device, IDs PNP0c02 (active)
    May 11 11:58:32 arch kernel: pnp: PnP ACPI: found 11 devices
    May 11 11:58:32 arch kernel: ACPI: bus type PNP unregistered
    May 11 11:58:32 arch kernel: pci 0000:01:00.0: no compatible bridge window for [mem 0xfff80000-0xffffffff pref]
    May 11 11:58:32 arch kernel: pci 0000:07:00.0: no compatible bridge window for [mem 0xfff80000-0xffffffff pref]
    May 11 11:58:32 arch kernel: pci 0000:01:00.0: BAR 6: assigned [mem 0xb2000000-0xb207ffff pref]
    May 11 11:58:32 arch kernel: pci 0000:00:01.0: PCI bridge to [bus 01-06]
    May 11 11:58:32 arch kernel: pci 0000:00:01.0: bridge window [io 0x5000-0x5fff]
    May 11 11:58:32 arch kernel: pci 0000:00:01.0: bridge window [mem 0xd3000000-0xd4ffffff]
    May 11 11:58:32 arch kernel: pci 0000:00:01.0: bridge window [mem 0xa0000000-0xbfffffff 64bit pref]
    May 11 11:58:32 arch kernel: pci 0000:07:00.0: BAR 6: can't assign mem pref (size 0x80000)
    May 11 11:58:32 arch kernel: pci 0000:00:01.1: PCI bridge to [bus 07]
    May 11 11:58:32 arch kernel: pci 0000:00:01.1: bridge window [io 0x4000-0x4fff]
    May 11 11:58:32 arch kernel: pci 0000:00:01.1: bridge window [mem 0xd2000000-0xd2ffffff]
    May 11 11:58:32 arch kernel: pci 0000:00:01.1: bridge window [mem 0xc0000000-0xd1ffffff 64bit pref]
    May 11 11:58:32 arch kernel: pci 0000:00:1c.0: PCI bridge to [bus 08]
    May 11 11:58:32 arch kernel: pci 0000:00:1c.0: bridge window [io 0x3000-0x3fff]
    May 11 11:58:32 arch kernel: pci 0000:00:1c.0: bridge window [mem 0xd5100000-0xd51fffff]
    May 11 11:58:32 arch kernel: pci 0000:00:1c.4: PCI bridge to [bus 09]
    May 11 11:58:32 arch kernel: pci 0000:00:1c.4: bridge window [mem 0xd5000000-0xd50fffff]
    May 11 11:58:32 arch kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
    May 11 11:58:32 arch kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
    May 11 11:58:32 arch kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
    May 11 11:58:32 arch kernel: pci_bus 0000:00: resource 7 [mem 0x000c0000-0x000c3fff]
    May 11 11:58:32 arch kernel: pci_bus 0000:00: resource 8 [mem 0x000c4000-0x000c7fff]
    May 11 11:58:32 arch kernel: pci_bus 0000:00: resource 9 [mem 0x000c8000-0x000cbfff]
    May 11 11:58:32 arch kernel: pci_bus 0000:00: resource 10 [mem 0x000cc000-0x000cffff]
    May 11 11:58:32 arch kernel: pci_bus 0000:00: resource 11 [mem 0x000d0000-0x000d3fff]
    May 11 11:58:32 arch kernel: pci_bus 0000:00: resource 12 [mem 0x000d4000-0x000d7fff]
    May 11 11:58:32 arch kernel: pci_bus 0000:00: resource 13 [mem 0x000d8000-0x000dbfff]
    May 11 11:58:32 arch kernel: pci_bus 0000:00: resource 14 [mem 0x000dc000-0x000dffff]
    May 11 11:58:32 arch kernel: pci_bus 0000:00: resource 15 [mem 0x000e0000-0x000e3fff]
    May 11 11:58:32 arch kernel: pci_bus 0000:00: resource 16 [mem 0x000e4000-0x000e7fff]
    May 11 11:58:32 arch kernel: pci_bus 0000:00: resource 17 [mem 0x000e8000-0x000ebfff]
    May 11 11:58:32 arch kernel: pci_bus 0000:00: resource 18 [mem 0x000ec000-0x000effff]
    May 11 11:58:32 arch kernel: pci_bus 0000:00: resource 19 [mem 0x90000000-0xfeafffff]
    May 11 11:58:32 arch kernel: pci_bus 0000:01: resource 0 [io 0x5000-0x5fff]
    May 11 11:58:32 arch kernel: pci_bus 0000:01: resource 1 [mem 0xd3000000-0xd4ffffff]
    May 11 11:58:32 arch kernel: pci_bus 0000:01: resource 2 [mem 0xa0000000-0xbfffffff 64bit pref]
    May 11 11:58:32 arch kernel: pci_bus 0000:07: resource 0 [io 0x4000-0x4fff]
    May 11 11:58:32 arch kernel: pci_bus 0000:07: resource 1 [mem 0xd2000000-0xd2ffffff]
    May 11 11:58:32 arch kernel: pci_bus 0000:07: resource 2 [mem 0xc0000000-0xd1ffffff 64bit pref]
    May 11 11:58:32 arch kernel: pci_bus 0000:08: resource 0 [io 0x3000-0x3fff]
    May 11 11:58:32 arch kernel: pci_bus 0000:08: resource 1 [mem 0xd5100000-0xd51fffff]
    May 11 11:58:32 arch kernel: pci_bus 0000:09: resource 1 [mem 0xd5000000-0xd50fffff]
    May 11 11:58:32 arch kernel: NET: Registered protocol family 2
    May 11 11:58:32 arch kernel: TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
    May 11 11:58:32 arch kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
    May 11 11:58:32 arch kernel: TCP: Hash tables configured (established 131072 bind 65536)
    May 11 11:58:32 arch kernel: TCP: reno registered
    May 11 11:58:32 arch kernel: UDP hash table entries: 8192 (order: 6, 262144 bytes)
    May 11 11:58:32 arch kernel: UDP-Lite hash table entries: 8192 (order: 6, 262144 bytes)
    May 11 11:58:32 arch kernel: NET: Registered protocol family 1
    May 11 11:58:32 arch kernel: pci 0000:08:00.0: set MSI_INTX_DISABLE_BUG flag
    May 11 11:58:32 arch kernel: PCI: CLS 64 bytes, default 64
    May 11 11:58:32 arch kernel: Unpacking initramfs...
    May 11 11:58:32 arch kernel: Freeing initrd memory: 5020K (ffff880037622000 - ffff880037b09000)
    May 11 11:58:32 arch kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
    May 11 11:58:32 arch kernel: software IO TLB [mem 0x8aa68000-0x8ea68000] (64MB) mapped at [ffff88008aa68000-ffff88008ea67fff]
    May 11 11:58:32 arch kernel: Simple Boot Flag at 0x44 set to 0x1
    May 11 11:58:32 arch kernel: RAPL PMU detected, hw unit 2^-14 Joules, API unit is 2^-32 Joules, 3 fixed counters 655360 ms ovfl timer
    May 11 11:58:32 arch kernel: Scanning for low memory corruption every 60 seconds
    May 11 11:58:32 arch kernel: futex hash table entries: 2048 (order: 5, 131072 bytes)
    May 11 11:58:32 arch kernel: HugeTLB registered 2 MB page size, pre-allocated 0 pages
    May 11 11:58:32 arch kernel: zbud: loaded
    May 11 11:58:32 arch kernel: VFS: Disk quotas dquot_6.5.2
    May 11 11:58:32 arch kernel: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
    May 11 11:58:32 arch kernel: msgmni has been set to 31994
    May 11 11:58:32 arch kernel: Key type big_key registered
    May 11 11:58:32 arch kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
    May 11 11:58:32 arch kernel: io scheduler noop registered
    May 11 11:58:32 arch kernel: io scheduler deadline registered
    May 11 11:58:32 arch kernel: io scheduler cfq registered (default)
    May 11 11:58:32 arch kernel: pcieport 0000:00:01.0: device [8086:0c01] has invalid IRQ; check vendor BIOS
    May 11 11:58:32 arch kernel: pcieport 0000:00:01.0: irq 40 for MSI/MSI-X
    May 11 11:58:32 arch kernel: pcieport 0000:00:01.1: device [8086:0c05] has invalid IRQ; check vendor BIOS
    May 11 11:58:32 arch kernel: pcieport 0000:00:01.1: irq 41 for MSI/MSI-X
    May 11 11:58:32 arch kernel: pcieport 0000:00:1c.0: device [8086:8c16] has invalid IRQ; check vendor BIOS
    May 11 11:58:32 arch kernel: pcieport 0000:00:1c.0: irq 42 for MSI/MSI-X
    May 11 11:58:32 arch kernel: pcieport 0000:00:1c.4: device [8086:8c18] has invalid IRQ; check vendor BIOS
    May 11 11:58:32 arch kernel: pcieport 0000:00:1c.4: irq 43 for MSI/MSI-X
    May 11 11:58:32 arch kernel: pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
    May 11 11:58:32 arch kernel: pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
    May 11 11:58:32 arch kernel: pci 0000:01:00.1: Signaling PME through PCIe PME interrupt
    May 11 11:58:32 arch kernel: pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
    May 11 11:58:32 arch kernel: pcieport 0000:00:01.1: Signaling PME through PCIe PME interrupt
    May 11 11:58:32 arch kernel: pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
    May 11 11:58:32 arch kernel: pcie_pme 0000:00:01.1:pcie01: service driver pcie_pme loaded
    May 11 11:58:32 arch kernel: pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
    May 11 11:58:32 arch kernel: pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
    May 11 11:58:32 arch kernel: pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
    May 11 11:58:32 arch kernel: pcieport 0000:00:1c.4: Signaling PME through PCIe PME interrupt
    May 11 11:58:32 arch kernel: pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
    May 11 11:58:32 arch kernel: pcie_pme 0000:00:1c.4:pcie01: service driver pcie_pme loaded
    May 11 11:58:32 arch kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    May 11 11:58:32 arch kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
    May 11 11:58:32 arch kernel: efifb: probing for efifb
    May 11 11:58:32 arch kernel: efifb: framebuffer at 0xa0000000, mapped to 0xffffc90011c00000, using 8128k, total 8128k
    May 11 11:58:32 arch kernel: efifb: mode is 1920x1080x32, linelength=7680, pages=1
    May 11 11:58:32 arch kernel: efifb: scrolling: redraw
    May 11 11:58:32 arch kernel: efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
    May 11 11:58:32 arch kernel: Console: switching to colour frame buffer device 240x67
    May 11 11:58:32 arch kernel: fb0: EFI VGA frame buffer device
    May 11 11:58:32 arch kernel: intel_idle: MWAIT substates: 0x42120
    May 11 11:58:32 arch kernel: intel_idle: v0.4 model 0x3C
    May 11 11:58:32 arch kernel: intel_idle: lapic_timer_reliable_states 0xffffffff
    May 11 11:58:32 arch kernel: GHES: HEST is not enabled!
    May 11 11:58:32 arch kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    May 11 11:58:32 arch kernel: Linux agpgart interface v0.103
    May 11 11:58:32 arch kernel: rtc_cmos 00:06: RTC can wake from S4
    May 11 11:58:32 arch kernel: rtc_cmos 00:06: rtc core: registered rtc_cmos as rtc0
    May 11 11:58:32 arch kernel: rtc_cmos 00:06: alarms up to one month, 242 bytes nvram, hpet irqs
    May 11 11:58:32 arch kernel: Intel P-state driver initializing.
    May 11 11:58:32 arch kernel: Intel pstate controlling: cpu 0
    May 11 11:58:32 arch kernel: Intel pstate controlling: cpu 1
    May 11 11:58:32 arch kernel: Intel pstate controlling: cpu 2
    May 11 11:58:32 arch kernel: Intel pstate controlling: cpu 3
    May 11 11:58:32 arch kernel: Intel pstate controlling: cpu 4
    May 11 11:58:32 arch kernel: Intel pstate controlling: cpu 5
    May 11 11:58:32 arch kernel: Intel pstate controlling: cpu 6
    May 11 11:58:32 arch kernel: Intel pstate controlling: cpu 7
    May 11 11:58:32 arch kernel: ledtrig-cpu: registered to indicate activity on CPUs
    May 11 11:58:32 arch kernel: TCP: cubic registered
    May 11 11:58:32 arch kernel: NET: Registered protocol family 10
    May 11 11:58:32 arch kernel: NET: Registered protocol family 17
    May 11 11:58:32 arch kernel: registered taskstats version 1
    May 11 11:58:32 arch kernel: Magic number: 14:215:980
    May 11 11:58:32 arch kernel: rtc_cmos 00:06: setting system clock to 2014-05-11 09:58:26 UTC (1399802306)
    May 11 11:58:32 arch kernel: PM: Hibernation image not present or could not be loaded.
    May 11 11:58:32 arch kernel: Freeing unused kernel memory: 1120K (ffffffff818d8000 - ffffffff819f0000)
    May 11 11:58:32 arch kernel: Write protecting the kernel read-only data: 8192k
    May 11 11:58:32 arch kernel: Freeing unused kernel memory: 904K (ffff88000251e000 - ffff880002600000)
    May 11 11:58:32 arch kernel: Freeing unused kernel memory: 416K (ffff880002798000 - ffff880002800000)
    May 11 11:58:32 arch kernel: random: systemd-tmpfile urandom read with 1 bits of entropy available
    May 11 11:58:32 arch systemd-udevd[78]: starting version 212
    May 11 11:58:32 arch kernel: [drm] Initialized drm 1.1.0 20060810
    May 11 11:58:32 arch kernel: wmi: Mapper loaded
    May 11 11:58:32 arch kernel: ACPI: Video Device [PEGP] (multi-head: yes rom: yes post: no)
    May 11 11:58:32 arch kernel: acpi device:4e: registered as cooling_device0
    May 11 11:58:32 arch kernel: ACPI Error: [\_SB_.PCI0.LPCB.EC0_.BLVL] Namespace lookup failure, AE_NOT_FOUND (20131218/psargs-359)
    May 11 11:58:32 arch kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.PEG0.PEGP.DD01._BQC] (Node ffff88045e068d48), AE_N
    May 11 11:58:32 arch kernel: ACPI Warning: Evaluating _BQC failed (20131218/video-648)
    May 11 11:58:32 arch kernel: tsc: Refined TSC clocksource calibration: 2394.454 MHz
    May 11 11:58:32 arch kernel: ACPI Error: [\_SB_.PCI0.LPCB.EC0_.BLVL] Namespace lookup failure, AE_NOT_FOUND (20131218/psargs-359)
    May 11 11:58:32 arch kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.PEG0.PEGP.DD01._BCM] (Node ffff88045e068d70), AE_N
    May 11 11:58:32 arch kernel: ACPI Error: Evaluating _BCM failed (20131218/video-382)
    May 11 11:58:32 arch kernel: ACPI Error: [\_SB_.PCI0.LPCB.EC0_.BLVL] Namespace lookup failure, AE_NOT_FOUND (20131218/psargs-359)
    May 11 11:58:32 arch kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.PEG0.PEGP.DD02._BQC] (Node ffff88045e068eb0), AE_N
    May 11 11:58:32 arch kernel: ACPI Warning: Evaluating _BQC failed (20131218/video-648)
    May 11 11:58:32 arch kernel: ACPI Error: [\_SB_.PCI0.LPCB.EC0_.BLVL] Namespace lookup failure, AE_NOT_FOUND (20131218/psargs-359)
    May 11 11:58:32 arch kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.PEG0.PEGP.DD02._BCM] (Node ffff88045e068ed8), AE_N
    May 11 11:58:32 arch kernel: ACPI Error: Evaluating _BCM failed (20131218/video-382)
    May 11 11:58:32 arch kernel: Switched to clocksource tsc
    May 11 11:58:32 arch kernel: ACPI Error: [\_SB_.PCI0.LPCB.EC0_.BLVL] Namespace lookup failure, AE_NOT_FOUND (20131218/psargs-359)
    May 11 11:58:32 arch kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.PEG0.PEGP.DD03._BQC] (Node ffff88045e06d050), AE_N
    May 11 11:58:32 arch kernel: ACPI Warning: Evaluating _BQC failed (20131218/video-648)
    May 11 11:58:32 arch kernel: ACPI Error: [\_SB_.PCI0.LPCB.EC0_.BLVL] Namespace lookup failure, AE_NOT_FOUND (20131218/psargs-359)
    May 11 11:58:32 arch kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.PEG0.PEGP.DD03._BCM] (Node ffff88045e06d078), AE_N
    May 11 11:58:32 arch kernel: ACPI Error: Evaluating _BCM failed (20131218/video-382)
    May 11 11:58:32 arch kernel: ACPI Error: [\_SB_.PCI0.LPCB.EC0_.BLVL] Namespace lookup failure, AE_NOT_FOUND (20131218/psargs-359)
    May 11 11:58:32 arch kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.PEG0.PEGP.DD04._BQC] (Node ffff88045e06d1e0), AE_N
    May 11 11:58:32 arch kernel: ACPI Warning: Evaluating _BQC failed (20131218/video-648)
    May 11 11:58:32 arch kernel: ACPI Error: [\_SB_.PCI0.LPCB.EC0_.BLVL] Namespace lookup failure, AE_NOT_FOUND (20131218/psargs-359)
    May 11 11:58:32 arch kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.PEG0.PEGP.DD04._BCM] (Node ffff88045e06d208), AE_N
    May 11 11:58:32 arch kernel: ACPI Error: Evaluating _BCM failed (20131218/video-382)
    May 11 11:58:32 arch kernel: ACPI Error: [\_SB_.PCI0.LPCB.EC0_.BLVL] Namespace lookup failure, AE_NOT_FOUND (20131218/psargs-359)
    May 11 11:58:32 arch kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.PEG0.PEGP.DD05._BQC] (Node ffff88045e06d370), AE_N
    May 11 11:58:32 arch kernel: ACPI Warning: Evaluating _BQC failed (20131218/video-648)
    May 11 11:58:32 arch kernel: ACPI Error: [\_SB_.PCI0.LPCB.EC0_.BLVL] Namespace lookup failure, AE_NOT_FOUND (20131218/psargs-359)
    May 11 11:58:32 arch kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.PEG0.PEGP.DD05._BCM] (Node ffff88045e06d398), AE_N
    May 11 11:58:32 arch kernel: ACPI Error: Evaluating _BCM failed (20131218/video-382)
    May 11 11:58:32 arch kernel: ACPI Error: [\_SB_.PCI0.LPCB.EC0_.BLVL] Namespace lookup failure, AE_NOT_FOUND (20131218/psargs-359)
    May 11 11:58:32 arch kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.PEG0.PEGP.DD06._BQC] (Node ffff88045e06d500), AE_N
    May 11 11:58:32 arch kernel: ACPI Warning: Evaluating _BQC failed (20131218/video-648)
    May 11 11:58:32 arch kernel: ACPI Error: [\_SB_.PCI0.LPCB.EC0_.BLVL] Namespace lookup failure, AE_NOT_FOUND (20131218/psargs-359)
    May 11 11:58:32 arch kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.PEG0.PEGP.DD06._BCM] (Node ffff88045e06d528), AE_N
    May 11 11:58:32 arch kernel: ACPI Error: Evaluating _BCM failed (20131218/video-382)
    May 11 11:58:32 arch kernel: ACPI Error: [\_SB_.PCI0.LPCB.EC0_.BLVL] Namespace lookup failure, AE_NOT_FOUND (20131218/psargs-359)
    May 11 11:58:32 arch kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.PEG0.PEGP.DD07._BQC] (Node ffff88045e06d690), AE_N
    May 11 11:58:32 arch kernel: ACPI Warning: Evaluating _BQC failed (20131218/video-648)
    May 11 11:58:32 arch kernel: ACPI Error: [\_SB_.PCI0.LPCB.EC0_.BLVL] Namespace lookup failure, AE_NOT_FOUND (20131218/psargs-359)
    May 11 11:58:32 arch kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.PEG0.PEGP.DD07._BCM] (Node ffff88045e06d6b8), AE_N
    May 11 11:58:32 arch kernel: ACPI Error: Evaluating _BCM failed (20131218/video-382)
    May 11 11:58:32 arch kernel: input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:4d/LNXVIDEO:00/input/input0
    May 11 11:58:32 arch kernel: [Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module paramete
    May 11 11:58:32 arch kernel: [Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module paramete
    May 11 11:58:32 arch kernel: [Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module paramete
    May 11 11:58:32 arch kernel: [Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module paramete
    May 11 11:58:32 arch kernel: [Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module paramete
    May 11 11:58:32 arch kernel: input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:02/PNP0C0C:00/input/input1
    May 11 11:58:32 arch kernel: ACPI: Power Button [PWRB]
    May 11 11:58:32 arch kernel: input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:02/PNP0C0E:00/input/input2
    May 11 11:58:32 arch kernel: ACPI: Sleep Button [SLPB]
    May 11 11:58:32 arch kernel: input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input3
    May 11 11:58:32 arch kernel: ACPI: Lid Switch [LID0]
    May 11 11:58:32 arch kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
    May 11 11:58:32 arch kernel: ACPI: Power Button [PWRF]
    May 11 11:58:32 arch kernel: MXM: GUID detected in BIOS
    May 11 11:58:32 arch kernel: ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Pack
    May 11 11:58:32 arch kernel: ACPI: \_SB_.PCI0.PEG0.PEGP: failed to evaluate _DSM
    May 11 11:58:32 arch kernel: checking generic (a0000000 7f0000) vs hw (a0000000 10000000)
    May 11 11:58:32 arch kernel: fb: conflicting fb hw usage nouveaufb vs EFI VGA - removing generic driver
    May 11 11:58:32 arch kernel: Console: switching to colour dummy device 80x25
    May 11 11:58:32 arch kernel: nouveau [ DEVICE][0000:01:00.0] BOOT0 : 0x0e70d0a2
    May 11 11:58:32 arch kernel: nouveau [ DEVICE][0000:01:00.0] Chipset: GK107 (NVE7)
    May 11 11:58:32 arch kernel: nouveau [ DEVICE][0000:01:00.0] Family : NVE0
    May 11 11:58:32 arch kernel: nouveau [ VBIOS][0000:01:00.0] checking PRAMIN for image...
    May 11 11:58:32 arch kernel: nouveau [ VBIOS][0000:01:00.0] ... signature not found
    May 11 11:58:32 arch kernel: nouveau [ VBIOS][0000:01:00.0] checking PROM for image...
    May 11 11:58:32 arch kernel: nouveau [ VBIOS][0000:01:00.0] ... signature not found
    May 11 11:58:32 arch kernel: nouveau [ VBIOS][0000:01:00.0] checking ACPI for image...
    May 11 11:58:32 arch kernel: nouveau [ VBIOS][0000:01:00.0] ... signature not found
    May 11 11:58:32 arch kernel: nouveau [ VBIOS][0000:01:00.0] checking PCIROM for image...
    May 11 11:58:32 arch kernel: nouveau 0000:01:00.0: Invalid ROM contents
    May 11 11:58:32 arch kernel: nouveau [ VBIOS][0000:01:00.0] ... signature not found
    May 11 11:58:32 arch kernel: nouveau [ VBIOS][0000:01:00.0] checking PLATFORM for image...
    May 11 11:58:32 arch kernel: nouveau [ VBIOS][0000:01:00.0] ... signature not found
    May 11 11:58:32 arch kernel: nouveau E[ VBIOS][0000:01:00.0] unable to locate usable image
    May 11 11:58:32 arch kernel: nouveau E[ DEVICE][0000:01:00.0] failed to create 0x10000001, -22
    May 11 11:58:32 arch kernel: nouveau E[ DRM] failed to create 0x80000080, -22
    May 11 11:58:32 arch kernel: nouveau: probe of 0000:01:00.0 failed with error -22
    May 11 11:58:32 arch kernel: nouveau 0000:07:00.0: enabling device (0006 -> 0007)
    May 11 11:58:32 arch kernel: [drm] hdmi device not found 7 0 1
    May 11 11:58:32 arch kernel: nouveau [ DEVICE][0000:07:00.0] BOOT0 : 0x0e70d0a2
    May 11 11:58:32 arch kernel: nouveau [ DEVICE][0000:07:00.0] Chipset: GK107 (NVE7)
    May 11 11:58:32 arch kernel: nouveau [ DEVICE][0000:07:00.0] Family : NVE0
    May 11 11:58:32 arch kernel: nouveau [ VBIOS][0000:07:00.0] checking PRAMIN for image...
    May 11 11:58:32 arch kernel: nouveau [ VBIOS][0000:07:00.0] ... signature not found
    May 11 11:58:32 arch kernel: nouveau [ VBIOS][0000:07:00.0] checking PROM for image...
    May 11 11:58:32 arch kernel: nouveau [ VBIOS][0000:07:00.0] ... appears to be valid
    May 11 11:58:32 arch kernel: nouveau [ VBIOS][0000:07:00.0] using image from PROM
    May 11 11:58:32 arch kernel: nouveau [ VBIOS][0000:07:00.0] BIT signature found
    May 11 11:58:32 arch kernel: nouveau [ VBIOS][0000:07:00.0] version 80.07.a8.00.32
    May 11 11:58:32 arch kernel: nouveau [ DEVINIT][0000

  • Can. I use my MAC Mini in conjunction with my iMac?

    Can I use my MAC Mini in conjunction with my iMAC? I can not upgrade the OS of the iMAC due to software that I need and Lion does not support it.
    If I could bounce back an forth or use the software from the MAC Mini with the iMAC, this would solve my dilemma.

    Before I buy a networked drive can I use the airport to connect with an external
    USB drive and set both macs  use the  drive as a time machine
    Can you hook this up? Sure.
    Is is supported by Apple?  No.
    Some users report that this seems to work when they try it.
    Others....like me....have corruption problems anywhere from a few days to a few months after I set up a test....which I do whenever a new version of firmware or a new operating system becomes available.
    We cannot predict your results, so if you decide to try this, and your backups are valuable, you might want to have a secondary backup plan in place as well....just in case.

  • Journalwatch - Minimal log watcher/notifier for the systemd journal

    Inspired by a blogpost I started a small project: A tool similiar to logwatch/logcheck, but much more KISS, and working with the systemd journal. It's written using Python3.
    Git repository
    AUR package (journalwatch)
    PyPi page
    The configuration is very simple: You define patterns for log messages you're not interested in, like this:
    _SYSTEMD_UNIT = systemd-logind.service
    New session [a-z]?\d+ of user \w+\.
    Removed session [a-z]?\d+\.
    SYSLOG_IDENTIFIER = /(CROND|crond)/
    pam_unix\(crond:session\): session (opened|closed) for user \w+
    \(\w+\) CMD .*
    Then if anything happens which is not filtered by your patterns, you get a mail (or the lines printed on stdout).
    From the README:
    journalwatch is a tool which can find error messages in the systemd journal.
    It is similiar to tools like logwatch/logcheck except it's much more KISS and only works with the systemd journal. It works by defining patterns to match all log lines which are not interesting, and then prints all log lines not matching those patterns (or sends them by mail).
    When you start it the first time, it'll write the default pattern and config to $XDG_CONFIG_HOME/.config/journalwatch ($XDG_CONFIG_HOME is your home if unset). Details on how to configure journalwatch are available in these files.
    Feedback of any kind is very welcome!

    Hello mate, a good while ago I started working on automated self adapting log analyser. I wanted something that will read audited logs and learn system patterns so during normal operation it would raise alert each time something unusual happens. I wanted this to be done in C (just a thought that C is much easier than C++ to do things right even though I'm very far to call myself a proper programmer).
    http://sourceforge.net/projects/intelligentloganalyser/
    (in progress, when busy time at day work is over I'm finishing that project off)

  • [SOLVED] Systemd breaks truecrypt

    Today I got my system up to date, then decided to try systemd by putting init=/bin/systemd in my grub kernel line (not in the fallback line though). Now everything looks cool booting, but when I get into lxde and run truecrypt to mount my volume, I get a fail message from truecrypt after entering my password, "Failed to set up a loop device: <my container>"
    I can find the container in the correct place.
    If I reboot the fallback, which doesn't use systemd, I can mount this volume no problem. Going back to systemd, I can't.
    I have checked that loop is there with lsmod. I find no thread here with this problem, nor with a general google.
    I haven't done anything else to further implement systemd other than installing systemd-arch-units.
    The only thing that looked a bit strange in the systemd journal is "systemd-tmpfiles[289]: Two or more conflicting lines for /tmp configured, ignoring."
    Last edited by PaulBx1 (2012-06-02 01:51:48)

    Wrong again, it was not the upgrade. It was the fact rc.conf is not being run in systemd native mode.
    FYI, to fix this I followed the procedure here:
    https://wiki.archlinux.org/index.php/Sy … uring_boot
    That is I created the file /etc/modules-load.d/truecrypt.conf:
    # truecrypt needs to have loop loaded
    loop
    This had previously been loaded in /etc/rc.conf when using the sysv boot (the "MODULES" array). BTW it might be a good idea to modify the systemd wiki page saying that anything that happened in rc.conf now has to be handled in a different way, since (I guess) rc.conf is no longer being run. Er, I guess it does say that at one point, but it didn't really jump out at me. Also, the very last sentence of the truecrypt wiki page needs additional information concerning systemd. I suppose I need to figure out how to modify wiki pages...

Maybe you are looking for

  • SBH52 and Smart Connect problems

    Hi everyone, I just found some problems with my new Z2 and SBH52 - Sometimes SBH52 connected, Walkman started, tracks played, but there's no sound. - After turning off SBH52, the notification "SBH52 disconnected" can't be cleared from Notifications p

  • Software Update - "Server unavailable. Try again later." ???

    I've given my old 12" G3 iBook to a friend for his kid to use, and done a clean OS install today using the original OS X 10.3 CD's - but when connecting to Software Update, I've been getting the message "Server unavailable. Try again later." Problem?

  • P7N CPU list up at MSI..good QX9650 info..steppings critical

    Like the title says..MSI has finally posted the CPU list for the P7N..not all Yorkfields are supported yet, and the Quads in general are not all compatible as of yet.  Steppings appear to be crucial for official support at this time. Link>  http://gl

  • How to draw in class from out side of it ???

    Hi Im trying to create : class MySomething extends Component { public MySomething() {} public void paint(Graphics g) { g.drawString("MySomething",10,10); but when i call it from a applet it doesnt draw in the applet. Thanks for all the help

  • HT4113 how do you reset a forgotten passcode?

    how do you reset a forgotten passcode?