[SOLVED] [systemd] systed-module-load.service inactive (dead)

Hello archers,
I use VirtualBox and I'm tired of loading modules manually so I figured that a conf file can be created in /etc/modprobe.d/ that will load those modules at boot. Well, easier said than done because it doesn't seem to work.
Here's my virtualbox.conf:
# modules relevant to VirtualBox
vboxdrv
vboxnetadp
vboxnetflt
and here's my systemctl status systemd-modules-load.service:
systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static)
Active: inactive (dead)
start condition failed at Sun 2013-10-20 09:27:06 CEST; 6s ago
none of the trigger conditions were met
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
Looking forward to hearing from you.
Last edited by robin92 (2013-10-20 11:10:55)

robin92 wrote:so I figured that a conf file can be created in /etc/modprobe.d/ that will load those modules at boot.
Why not read the Wiki and follow the instructions?
https://wiki.archlinux.org/index.php/VirtualBox
Last edited by loafer (2013-10-20 08:06:04)

Similar Messages

  • Systemd system-modules-load error [Solved]

    After recent update of kernel too linux-3.14.4-1I now cannot boot system due too this error
    -- Logs begin at Fri 2014-05-16 11:58:04 BST, end at Fri 2014-05-16 12:00:56 BST. --
    May 16 11:59:33 arch systemd[1]: Starting Graphical Interface.
    -- Subject: Unit graphical.target has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit graphical.target has begun starting up.
    May 16 11:59:33 arch systemd[1]: Reached target Graphical Interface.
    -- Subject: Unit graphical.target has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit graphical.target has finished starting up.
    -- The start-up result is done.
    May 16 11:59:33 arch systemd[1]: Starting Network.
    -- Subject: Unit network.target has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit network.target has begun starting up.
    May 16 11:59:33 arch systemd[1]: Reached target Network.
    -- Subject: Unit network.target has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit network.target has finished starting up.
    -- The start-up result is done.
    May 16 11:59:33 arch systemd[1]: Startup finished in 4.181s (kernel) + 1min 31.543s (userspace) = 1min 35.724s.
    -- Subject: System start-up is now complete
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- All system services necessary queued for starting at boot have been
    -- successfully started. Note that this does not mean that the machine is
    -- now idle as services might still be busy with completing start-up.
    -- Kernel start-up required 4181476 microseconds.
    -- Initial RAM disk start-up required INITRD_USEC microseconds.
    -- Userspace start-up required 91543070 microseconds.
    May 16 12:00:56 arch systemd[1]: Starting Load Kernel Modules...
    -- Subject: Unit systemd-modules-load.service has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-modules-load.service has begun starting up.
    May 16 12:00:56 arch systemd-modules-load[316]: Failed to lookup alias 'sg': Function not implemented
    May 16 12:00:56 arch systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE
    May 16 12:00:56 arch systemd[1]: Failed to start Load Kernel Modules.
    -- Subject: Unit systemd-modules-load.service has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-modules-load.service has failed.
    -- The result is failed.
    May 16 12:00:56 arch systemd[1]: Unit systemd-modules-load.service entered failed state.
    Might be just that naming of sg has changed have updated and tried to run mkinicpio but it still does not find module?
    Solved put it down to a bad dd clone of drive partition, have rerun and all seems to working now.
    Last edited by Mr Green (2014-05-17 12:20:52)

    Yep. It was my own fault. I had been using the b43 driver for my BCM4331 wifi card, and recently switched to broadcom-wl. However, I still was trying to load b43 in /etc/modules-load even though I had removed the driver and module from my system. Not sure why my system only started complaining in 3.18.5, but in any case removing the offending .conf file solved the problem. Thanks, graysky.

  • [SOLVED]3.18.5-1-ARCH + system-modules-load.service on Macbook Pro 9,2

    After upgrading from 3.18.4-1-ARCH to 3.18.5-1-ARCH this weekend, my systemd service system-modules-load fails during bootup. I checked out
    # systemctl status system-modules-load
    and found nothing but a warning that my journal has been rotated and the log output is incomplete. I have not hunted down the log or rooted through dmesg as of yet - I need my system functional while working during the week, so I downgraded my kernel back to 3.18.4 for now (under which system-modules-load loads fine). I will reinstall 3.18.5 next weekend and see if I can locate the problem - this post is just a feeler to see if anyone else is encountering this problem with the latest kernel.
    Last edited by Olorin (2015-02-06 03:08:31)

    Yep. It was my own fault. I had been using the b43 driver for my BCM4331 wifi card, and recently switched to broadcom-wl. However, I still was trying to load b43 in /etc/modules-load even though I had removed the driver and module from my system. Not sure why my system only started complaining in 3.18.5, but in any case removing the offending .conf file solved the problem. Thanks, graysky.

  • [SOLVED] systemd and rc-local.service

    So, today i decided to try a pure systemd system by migrating my old installation.
    The first problem i faced comes from rc-local.service.
    I followed this:
    https://wiki.archlinux.org/index.php/Sy … s#rc.local
    and created an identical rc-local.service:
    /etc/systemd/system/rc-local.service
    [Unit]
    Description=/etc/rc.local Compatibility
    [Service]
    Type=oneshot
    ExecStart=/etc/rc.local
    TimeoutSec=0
    StandardInput=tty
    RemainAfterExit=yes
    [Install]
    WantedBy=multi-user.target
    ...made it executable and enabled the service via
    systemctl enable rc-local.service
    The problem comes when i issue:
    systemctl --system daemon-reload
    systemctl start rc-local.service
    Here the prompt hangs forever.
    ..so i reeboted and automagically "Something" of my rc.local has been executed.
    What has been left out was a subscript launched in background from my rc.local.
    While in the past my working rc.local executed a script:
    checkmounts.sh & #<-this loops forever
    ...and in ps -ef|grep checkmounts i got it listed, now with systemd i haven't it anymore.
    ...note that to debug issues i echoed several "marks" into a text file, and i'm sure that
    rc.local has been executed till the end and systemctl status reports no errors at all.
    So the question are:
    1) why can't i start rc-local from terminal via sysctl and it works (sort of) if i reboot?
    2) why a script executed from rc.local in background doesn't work?
    Last edited by kokoko3k (2012-08-27 15:43:35)

    I already tried that with the same results.
    Now i found that removing StandardInput=tty works and solved both of the issues (at least issuing manual startups).
    So this:
    [Unit]
    Description=/etc/rc.local Compatibility
    [Service]
    Type=oneshot # is forking instead of oneshot needed here?
    ExecStart=/etc/rc.local
    TimeoutSec=0
    #StandardInput=tty
    RemainAfterExit=yes
    [Install]
    WantedBy=multi-user.target
    Works really well for me, exactly like in the past.
    Plus, i can see all running child processess via systemctl status rc-local.service
    If someone thinks this is wrong for seome reason i'll NOT update the wiki page.
    --EDIT
    Works well after a reboot too, and changing Type= to fork make just fork, parallelizing the boot (kdm+kde for me)
    Last edited by kokoko3k (2012-09-13 13:43:38)

  • [solved] systemd rc.local like service

    Hello everyone !
    Can someone help me to port my rc.local to systemd service?
    #!/bin/bash
    # /etc/rc.local: Local multi-user start-up script.
    myip=$(curl -s ipv4.icanhazip.com)
    /root/bin/sms.sh $myip > /dev/null 2>&1
    The script need to have internet access.
    Thanks a lot for your help !
    Last edited by CEPfister (2012-08-31 15:42:00)

    /root/bin/sendip.sh
    #!/bin/bash
    myip=$(curl -s ipv4.icanhazip.com)
    /root/bin/sms master $myip > /dev/null 2>&1
    /root/bin/sms helene $myip > /dev/null 2>&1
    $ systemctl status sendip.service
    sendip.service - Send IP
    Loaded: loaded (/etc/systemd/system/sendip.service; enabled)
    Active: activating (start) since Fri, 31 Aug 2012 17:01:14 +0200; 4min 15s ago
    Main PID: 267 ((endip.sh))
    CGroup: name=systemd:/system/sendip.service
    └ 267 (endip.sh)
    $ systemd-analyze
    Bootup is not yet finished. Please try again later.
    That's a bit hard to debug.

  • [Solved] systemd[1]: getty@tty7.service.d/autologin.conf

    I've been using Automatic login to virtual console for some time, using "[email protected]".
    Today I tried the new way, which looks much cleaner.
    cat /etc/systemd/system/[email protected]/autologin.conf 
    [Service]
    ExecStart=
    ExecStart=-/sbin/agetty --autologin leo --noclear %I 38400 linux
    Type=
    Type=simple
    At startup I get the error:
    systemd[1]: [/etc/systemd/system/[email protected]/autologin.conf:4] Failed to parse service type, ignoring:
    The only difference I can see is that I use tty7; I start Xorg from zprofile. (I'm old fashioned that way)
    I could just drop the "Type=simple" altogether, but since it is in the wiki, I thought I would ask here first.
    Last edited by Leo Laursen (2013-06-06 17:58:33)

    There is no need to add Type=, because Type is valid only one time in an unit. Instead for ExecStart=, since is valid to add more than one, If you need to clear all previous commands, then you need to specify ExecStart= in blank first.
    This is what I done in archiso
    https://projects.archlinux.org/archiso. … login.conf

  • [SOLVED] pacman -Syu on 10/17/2012, systemd can't load kernel modules

    Ok, I did a [pacman -Syu] on my laptop, and everything went well. So I decided to upgrade my PC as well, did a reboot and then couldn't ssh into it.
    Had to access the machine, and found
    # systemctl --failed
    UNIT LOAD ACTIVE SUB JOB DESCRIPTION
    [email protected] loaded failed failed dhcpcd on eth0
    httpd.service loaded failed failed Apache Web Server
    systemd-modules-load.service loaded failed failed Load Kernel Modules
    LOAD = Reflects whether the unit definition was properly loaded.
    ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
    SUB = The low-level unit activation state, values depend on unit type.
    JOB = Pending job for the unit.
    3 loaded units listed. Pass --all to see loaded but inactive units, too.
    To show all installed unit files use 'systemctl list-unit-files'.
    so it failed to load kernel modules...
    # systemctl status systemd-modules-load.service
    systemd-modules-load.service - Load Kernel Modules
    Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static)
    Active: failed (Result: exit-code) since Wed, 17 Oct 2012 18:27:11 -0400; 45min ago
    Docs: man:systemd-modules-load.service(8)
    man:modules-load.d(5)
    Process: 102 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
    CGroup: name=systemd:/system/systemd-modules-load.service
    Oct 17 18:27:11 MyHost systemd[1]: Failed to start Load Kernel Modules.
    Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
    ... then I checked network devices
    # ip addr
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
    valid_lft forever preferred_lft forever
    # ip addr show dev eth0
    Device "eth0" does not exist.
    ... then the modules; and I saw that none appeared for the Ethernet...
    # lspci -v | grep Ethernet -A8
    00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)
    Subsystem: Hewlett-Packard Company Device 2a6c
    Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 5
    Memory at fe02d000 (32-bit, non-prefetchable) [size=4K]
    I/O ports at fc00 [size=8]
    Capabilities: [44] Power Management version 2
    Capabilities: [50] MSI: Enable- Count=1/8 Maskable+ 64bit+
    Capabilities: [6c] HyperTransport: MSI Mapping Enable- Fixed+
    ... whereas they did for other devices
    # lspci -v | grep Kernel
    Kernel driver in use: ohci_hcd
    Kernel driver in use: ehci_hcd
    Kernel driver in use: sata_nv
    Kernel driver in use: sata_nv
    Kernel driver in use: pcieport
    Kernel driver in use: pcieport
    Kernel driver in use: pcieport
    Kernel driver in use: nouveau
    I'm guessing it's probably something with the new image after the pgrade, but I don't know which module to load nor do I
    understand why systemd isn't loading the modules when it was working stable enough to act as a headless server before. However, I've only been a week or so with systemd and might have overlooked something in the configs. Any help or insight would be greatly appreciated. Please. I'm desperate.
    Last edited by confusion-is-my-sedative (2012-10-26 21:30:01)

    Yep, I got that far, and tried the same advice from a different user with a 'tee' command which did the same thing, but unfortunately the forcedeth module can't be loaded because its in a different directory than the 'uname -r' specification allows modprobe to search for. I posted my attempts here: https://bbs.archlinux.org/viewtopic.php?pid=1181940

  • [SOLVED] systemd-modules-load fails

    .. because it cannot find gspca. My log:
    journalctl -xn
    -- Logs begin at Thu 2013-08-22 11:43:18 CEST, end at Mon 2014-06-23 14:26:30 CEST. --
    Jun 23 14:25:21 jiggs org.kde.knotify[1825]: "/org/freedesktop/UDisks2/block_devices/loop7" has new interfaces: ("org.
    Jun 23 14:25:22 jiggs org.kde.knotify[1825]: "/org/freedesktop/UDisks2/block_devices/loop2" has new interfaces: ("org.
    Jun 23 14:25:22 jiggs org.kde.knotify[1825]: "/org/freedesktop/UDisks2/block_devices/loop1" has new interfaces: ("org.
    Jun 23 14:25:22 jiggs org.kde.knotify[1825]: "/org/freedesktop/UDisks2/block_devices/loop0" has new interfaces: ("org.
    Jun 23 14:26:19 jiggs org.kde.knotify[1825]: "/org/freedesktop/UDisks2/block_devices/loop0" lost interfaces: ("org.fre
    Jun 23 14:26:30 jiggs systemd[1]: Starting Load Kernel Modules...
    -- Subject: Unit systemd-modules-load.service has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-modules-load.service has begun starting up.
    Jun 23 14:26:30 jiggs systemd-modules-load[3138]: Failed to find module 'gspca'
    Jun 23 14:26:30 jiggs systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE
    Jun 23 14:26:30 jiggs systemd[1]: Failed to start Load Kernel Modules.
    -- Subject: Unit systemd-modules-load.service has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-modules-load.service has failed.
    -- The result is failed.
    Jun 23 14:26:30 jiggs systemd[1]: Unit systemd-modules-load.service entered failed state.
    But I have lots of gspca's:
    # ls /lib/modules/`uname -r`/kernel/drivers/media/usb/gspca
    gl860 gspca_kinect.ko gspca_ov534.ko gspca_sonixj.ko gspca_sq905c.ko gspca_topro.ko
    gspca_benq.ko gspca_konica.ko gspca_pac207.ko gspca_spca1528.ko gspca_sq905.ko gspca_tv8532.ko
    gspca_conex.ko gspca_main.ko gspca_pac7302.ko gspca_spca500.ko gspca_sq930x.ko gspca_vc032x.ko
    gspca_cpia1.ko gspca_mars.ko gspca_pac7311.ko gspca_spca501.ko gspca_stk014.ko gspca_vicam.ko
    gspca_etoms.ko gspca_mr97310a.ko gspca_se401.ko gspca_spca505.ko gspca_stk1135.ko gspca_xirlink_cit.ko
    gspca_finepix.ko gspca_nw80x.ko gspca_sn9c2028.ko gspca_spca506.ko gspca_stv0680.ko gspca_zc3xx.ko
    gspca_jeilinj.ko gspca_ov519.ko gspca_sn9c20x.ko gspca_spca508.ko gspca_sunplus.ko m5602
    gspca_jl2005bcd.ko gspca_ov534_9.ko gspca_sonixb.ko gspca_spca561.ko gspca_t613.ko stv06xx
    The only difference I have with respect to a standard installation is that I downloaded an older version of the backport drivers, and in doing so I surely re-installed gspca.
    So my questions are: where is systemd-module-load searching for gspca? How can I persuade it to search in the right directory? And in any case, why is it searching for it in the wrong place to start with?. Just in case,
    # uname -a
    Linux jiggs 3.15.1-1-ARCH #1 SMP PREEMPT Tue Jun 17 09:32:20 CEST 2014 x86_64 GNU/Linux
    Last edited by MariusMatutiae (2014-06-26 09:10:22)

    Problem solved, thanks to both of you guys. For some resason, I had a webcam.conf file in /etc/modules-load.d containing the single line *gspca*, which is not a module: both modprobe and insmod fail, because the correct module name is one of those listed in /lib/modules/`uname -r`/kernel/drivers/media/usb/gspca. They are called gspca_benq.ko       gspca_konica.ko and so on. I simply deleted the file since I  do not need it.
    As for backport drivers: this site, http://drvbp1.linux-foundation.org/~mcg … backports/ has the most recent versions of Linux drivers, backported so that older kernels can install them (I understand this is not a concern for fellow Archers). Whenever I need to upgrade (mostly on Debian) or downgrade (a few times on Arch, because an older version of a driver is free of a newly minted bug) I download these drivers, compile them and install them from source.

  • Systemd fails to load modules with kernel 3.0

    When booting, systemd tells to issue this command:
    sudo systemctl status systemd-modules-load.service
    Password:
    systemd-modules-load.service - Load Kernel Modules
    Loaded: loaded (/lib/systemd/system/systemd-modules-load.service)
    Active: failed since Wed, 03 Aug 2011 00:40:15 +0200; 1min 26s ago
    Process: 237 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
    CGroup: name=systemd:/system/systemd-modules-load.service
    I have no idea about what it's happening or how to solve it.
    Any help would be appreciated. Thanks in advance

    Yes im in audio group. And i tryed that and nothing happend...
    EDIT: one more thing related for this bug, when i installed archboot yesterday it was everything work, then i do pacman -Syu and i updated package initscript and krb5 after this updated package network and audio stoped to work so probaby problem is here in initscrit (i guessing) and i not use kernel 3.0 i use
    uname -a
    Linux myhost 2.6.39-ARCH #1 SMP PREEMPT Sat Jul 9 15:31:04 CEST 2011 i686 Intel(R) Pentium(R) Dual CPU E2200 @ 2.20GHz GenuineIntel GNU/Linux
    Last edited by Kosava (2011-08-04 12:46:48)

  • [SOLVED] systemd and blacklisting modules

    Hi,
    I recently found out about the 'systemctl status foo.service'-cmd and I was finally able to see why the systemd-modules-load-service was failing on my laptop.
    It complains it cannot find service-files for 'blacklist nouveau' and other modules I have blacklisted. The wiki mentions blacklisting is done the same for systemd as for sysV-init, i.e. through a simple 'blacklist <modulename>' inside a .conf-file residing in either:
    /etc/modprobe.d/ or
    /etc/modules-load.d/
    What am I doing wrong?
    Last edited by zenlord (2012-08-24 19:38:38)

    tomegun wrote:The .conf file must be in /etc/modprobe.d and not in /etc/modules-load.d.
    OK, that's the one. I was mistaken to think that both directories had the same functionality.
    THX!
    Marking as solved.
    Last edited by zenlord (2012-08-24 19:38:11)

  • [Solved]Failed to start Load Kernel Modules

    When I boot up Arch it says that it Failed to start Load Kernel Modules and when I get into my Desktop, the screen is tearing.
    Using the latest kernel with i3wm
    my systemctl status systemd-modules-load
    ● systemd-modules-load.service - Load Kernel Modules
    Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static)
    Active: failed (Result: exit-code) since Sat 2014-09-20 17:28:06 PDT; 5min ago
    Docs: man:systemd-modules-load.service(8)
    man:modules-load.d(5)
    Process: 144 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
    Main PID: 144 (code=exited, status=1/FAILURE)
    Sep 20 17:28:06 green systemd-modules-load[144]: Failed to insert 'fglrx': Invalid argument
    Sep 20 17:28:06 green systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE
    Sep 20 17:28:06 green systemd[1]: Failed to start Load Kernel Modules.
    Sep 20 17:28:06 green systemd[1]: Unit systemd-modules-load.service entered failed state.
    Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
    Last edited by Green (2014-09-21 07:31:08)

    anatolik wrote:
    It looks like it is unable to load fglrx.
    Do you have any fglrx specific configuration? Do you have anything in your /etc/modprobe.d ?
    Could it be that fglrx is compiled for previous versions of kernel and this is a problem?
    I don't have any specific fglrx configuration and in /etc/modprobe.d/ I have a file called modprobe.conf that contains
    blacklist radeon
    fglrx
    I dont think fglrx was compiled for previous versions of the kernel because I used the kernel that the latest release contained. My kernel version is 3.16.3-1.
    Last edited by Green (2014-09-21 05:44:03)

  • [SOLVED] systemd swap related service in failed state

    Hi. When I ran systemctl to check my services, there was a failed one related to swap.
    Output of systemctl --failed:
    UNIT LOAD ACTIVE SUB DESCRIPTION
    ● dev-disk-by\x2duuid-7a53052d\x2df673\x2d40c9\x2d8b21\x2d1d5d87127479.swap loaded failed failed /dev/disk/by-uuid/7a53052d-f673-40c9-8b21-1d5d87127479
    Output of systemctl status dev-disk-by\x2duuid-7a53052d\x2df673\x2d40c9\x2d8b21\x2d1d5d87127479.swap:
    ● dev-disk-byx2duuid-7a53052dx2df673x2d40c9x2d8b21x2d1d5d87127479.swap - /dev/disk/byx2duuid/7a53052dx2df673x2d40c9x2d8b21x2d1d5d87127479
    Loaded: loaded
    Active: inactive (dead)
    What: /dev/disk/byx2duuid/7a53052dx2df673x2d40c9x2d8b21x2d1d5d87127479
    However, in the systemctl output there was another service which was active:
    dev-sda6.swap loaded active active Swap Partition
    And this is basically the same partition. In the output of blkid:
    /dev/sda6: UUID="7a53052d-f673-40c9-8b21-1d5d87127479" TYPE="swap" PARTUUID="00c618fd-9807-4fef-89dd-28e0a79192a9"
    As you can see the UUID of /dev/sda6 matches the one of the failing service. Here is the /etc/fstab entry for this partition:
    UUID=7a53052d-f673-40c9-8b21-1d5d87127479 none swap defaults 0 0
    So there are two services related to this partition, one that is active and one that is failed. I don't understand why and I don't know how to fix this. Any explanations and help will be greatly appreciated!
    Last edited by polomi (2015-02-27 20:19:32)

    I commented the swap line in /etc/fstab, and now I don't have the failed service. I also still have the dev-sda6.swap service active. So it looks good?
    However, when booting, I saw a line looking like this:
    Expecting device 7a53052d\x2df673\x2d40c9\x2d8b21\x2d1d5d87127479
    (It's maybe not exactly written like that, the boot is too fast for me to catch the text accurately.)
    It seems like it's partly fixed in any case. Thanks.
    Last edited by polomi (2015-02-27 20:26:56)

  • [SOLVED]systemd-analyze startup delay problem

    Hello,
    i have a problem that my systemd-analyze shows me "Bootup is not yet finished. Please try again later." when im up in my fully functional desktop, because it wants to wait 1min and 30 before it finishes the "boot"
    systemd-analyze
    Startup finished in 3.482s (kernel) + 1min 30.058s (userspace) = 1min 33.541s
    the userspace always takes that amount of time. while it actually takes ~12 sec to load with all set up. working network and stuff like that.
    systemd-analyze blame
    1.426s dkms.service
    215ms ModemManager.service
    207ms NetworkManager.service
    193ms systemd-fsck@dev-disk-by\x2duuid-c9582b14\x2de7f5\x2d4496\x2dbc09\x2d7be584a182f4.s
    148ms systemd-fsck@dev-disk-by\x2duuid-37962c3c\x2dcb8c\x2d4bb4\x2da27a\x2d58e852dcb643.s
    85ms systemd-logind.service
    78ms mnt-stuff.mount
    77ms upower.service
    68ms systemd-tmpfiles-clean.service
    54ms systemd-modules-load.service
    52ms polkit.service
    52ms systemd-udev-trigger.service
    47ms systemd-binfmt.service
    47ms kmod-static-nodes.service
    44ms mnt-downloads.mount
    44ms dev-hugepages.mount
    44ms dev-mqueue.mount
    44ms systemd-vconsole-setup.service
    43ms systemd-sysctl.service
    43ms sys-kernel-debug.mount
    41ms udisks2.service
    25ms [email protected]
    24ms lm_sensors.service
    15ms cpupower.service
    14ms alsa-restore.service
    10ms systemd-journal-flush.service
    8ms systemd-remount-fs.service
    6ms systemd-user-sessions.service
    6ms systemd-tmpfiles-setup.service
    5ms systemd-tmpfiles-setup-dev.service
    5ms rtkit-daemon.service
    4ms systemd-update-utmp.service
    4ms sys-fs-fuse-connections.mount
    3ms proc-sys-fs-binfmt_misc.mount
    3ms tmp.mount
    1ms sys-kernel-config.mount
    1ms systemd-udevd.service
    1ms systemd-random-seed.service
    nothing weird here(i think)?
    systemd-analyze critical-chain
    The time after the unit is active or started is printed after the "@" character.
    The time the unit takes to start is printed after the "+" character.
    graphical.target @1min 30.058s
    └─multi-user.target @1min 30.058s
    └─dkms.service @875ms +1.426s
    └─basic.target @869ms
    └─timers.target @627ms
    └─systemd-tmpfiles-clean.timer @627ms
    └─sysinit.target @626ms
    └─sys-fs-fuse-connections.mount @8.291s +4ms
    └─systemd-modules-load.service @61ms +54ms
    └─systemd-journald.socket @58ms
    └─-.mount @57ms
    └─system.slice @101ms
    └─-.slice @101ms
    as you can see multi-user.target and graphical.target starting at 1.30 only... allthough i dont even understand why they start at that time..cause my graphical interface is long time up already as well as my user account.
    here svg of systemd-analyze plot: https://dl.dropboxusercontent.com/u/28788188/boot.svg
    if anybody has some idea what might cause this i would really appriciate the help.
    its just seems a cosmetical issue though. since my actual boot is around 13 sec from grub to fully functional desktop.
    Last edited by xpander (2013-09-27 14:45:30)

    WonderWoofy wrote:
    These kinds of delays can happen when a service is bound to a particular piece of hardware. 
    So as an example the [email protected] uses "BindsTo=sys-subsystem-net-devices-%i.device".  So when you enable [email protected], the part between the '@' and '.service' is what it will use in place of the '%i' of the BindsTo parameter. 
    This was a common problem when there was the change from the old kernel namespace used for network devices to the persistent udev naming scheme.  During installation (or any time one was in the live media), it would use dhcpcd@eth0, so it would make sense that enabling dhcpcd@eth0 would set you all up for a nice ethernet connection when you launch the system for the first time.  But then the 80-net-slot-names.rules udev file would change the interface name, making the BindsTo parameter time out after a while, since it would not be named something like enp2s0.
    See if there are any failed units in the output of systemctl.  Of course you will have to do this after systemd claims to have "finished" booting.
    thanks, will digg into that. i do have some renaming policy there.. cause i have eth0 shown in ifconfig for example
    i remember i did something about it in the past, because i never got used with the new naming scheme.
    anyway systemctl --failed
    UNIT LOAD ACTIVE SUB DESCRIPTION
    fluidsynth.service loaded failed failed FluidSynth Daemon
    LOAD = Reflects whether the unit definition was properly loaded.
    ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
    SUB = The low-level unit activation state, values depend on unit type.
    1 loaded units listed. Pass --all to see loaded but inactive units, too.
    To show all installed unit files use 'systemctl list-unit-files'.
    and that fluidsynth is no issue. cause with this installed, it still does same. i have fluidynth uninstalled because my pulseadio doesnt work when that is enabled

  • [SOLVED] systemd switch, problems with slim/bootup

    My system will boot, giving me "OK" for everything it's doing. Then my system gives me a tty login prompt, but continues booting:
    gestalt login: [ OK ] Starting Wicd.
    [ OK ] Reached target multi-user.
    [ OK ] Reached target graphical interface.
    So if i just hit enter, it gives me another login prompt, then I can login, but X/fluxbox isn't started or anything.
    My ~/.xinitrc:
    exec startfluxbox
    xset +fp /usr/share/fonts/local
    xset fp rehash
    systemctl list-units --type=target
    UNIT LOAD ACTIVE SUB JOB DESCRIPTION
    basic.target loaded active active Basic System
    cryptsetup.target loaded active active Encrypted Volumes
    getty.target loaded active active Login Prompts
    graphical.target masked active active graphical.target
    local-fs-pre.target loaded active active Local File Systems (Pre)
    local-fs.target loaded active active Local File Systems
    multi-user.target loaded active active Multi-User
    network.target loaded active active Network
    remote-fs.target loaded active active Remote File Systems
    sockets.target loaded active active Sockets
    sound.target loaded active active Sound Card
    swap.target loaded active active Swap
    sysinit.target loaded active active System Initialization
    syslog.target loaded active active Syslog
    LOAD = Reflects whether the unit definition was properly loaded.
    ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
    SUB = The low-level unit activation state, values depend on unit type.
    JOB = Pending job for the unit.
    14 loaded units listed. Pass --all to see loaded but inactive units, too.
    To show all installed unit files use 'systemctl list-unit-files'.
    Graphical target isn't masked, like I thought it would be after reading this
    systemctl status slim.service gives me:
    slim.service - SLiM Simple Login Manager
    Loaded: loaded (/usr/lib/systemd/system/slim.service; enabled)
    Active: failed (Result: exit-code) since Mon, 2012-11-26
    Process: 305 ExecStart=urs/bin/slim -nodaemon(code=exited, status =1/FAILURE)
    CGroup: name=systemd:/system/slim.service
    systemd-analyze blame gives (just going to ignore the times)
    wicd.service
    systemd-vconsole-setup.service
    systemd-binfmt.service
    systemd-logind.service
    systemd-modules-load.service
    dev-hugepages.mount
    systemd-udev-trigger.service
    dev-mqueue.mount
    systemd-udevd.service
    proc-sys-fs-binfmt_service.mount
    console-kit-daemon.service
    polkit.service
    systemd-tmpfiles-setup.service
    home.mount
    systemd-sysctl.service
    tmp.mount
    systemd-user-sesssions.service
    systemd-remount-fs.service
    slim isn't even on this list.
    systemctl --failed
    UNIT LOAD ACTIVE SUB JOB DESCRIPTION
    slim.service loaded failed failed SLiM Simple Login Manager
    LOAD = Reflects whether the unit definition was properly loaded.
    ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
    SUB = The low-level unit activation state, values depend on unit type.
    JOB = Pending job for the unit.
    4 loaded units listed. Pass --all to see loaded but inactive units, too.
    To show all installed unit files use 'systemctl list-unit-files'.
    Hopefully this isn't too much information (or completely irrelevant) for what might be a far simpler problem, but I'm just not sure what's going on. It might be worth noting that I only bothered to start switching to systemd today when I had to reboot and slim wouldn't start/get me into my WM(!) This is interesting to me, since I read (somewhere) that as of slim's last version, it would only work with systemd and not consolekit... but when I try:
    pacman -Qi slim
    It tells me that the last time I last updated/installed slim was November 5 of this year. Any ideas?
    EDIT:
    Latest nVidia drivers weren't working with my 7xxx integrated GPU. Downgrade to 304xx drivers or use nouveau.
    Last edited by brokengestalt (2012-11-28 17:41:50)

    I tried starting X manually (typing in "startx" at the prompt, and I get the following errors:
    modprobe: ERROR: could not insert 'nvidia': No such device
    Fatal server error:
    no screens found
    (EE)
    Server terminated with error (1). Closing log file.
    xinit: giving up
    xinit: unable to connect to X server: Connection refused
    xinit: server error
    It looks like I'm just having problems with my video card, but I have the proprietary nVidia drivers installed and X installed. The systemd wiki page mentions no changes that I would need to make to my xorg or nvidia configuration...

  • [SOLVED] systemd Boot Time

    I noticed something odd when I analyzed boot times...
    systemd-analyze shows:
    Startup finished in 2.339s (kernel) + 1min 30.682s (userspace) = 1min 33.022s
    That is showing 1min 33s for userspace which is NOT right at all. I was in my xfce desktop by the 9s mark.
    systemd-analyze blame:
    5.476s [email protected]
    2.384s systemd-logind.service
    1.484s colord.service
    1.394s alsa-restore.service
    998ms systemd-fsck@dev-disk-by\x2duuid-353c16c3\x2dcec1\x2d4999\x2d9bbb\x2d821c639c68a8.service
    709ms dev-hugepages.mount
    703ms sys-kernel-debug.mount
    687ms systemd-fsck@dev-disk-by\x2duuid-f356e079\x2d6bc4\x2d4df1\x2da6f7\x2d0753be968197.service
    679ms dev-mqueue.mount
    654ms sys-kernel-config.mount
    654ms systemd-remount-fs.service
    649ms tmp.mount
    590ms systemd-fsck@dev-disk-by\x2duuid-56563fab\x2d94d9\x2d4d27\x2db787\x2d89e4624ed842.service
    583ms systemd-udev-trigger.service
    557ms systemd-tmpfiles-setup-dev.service
    556ms systemd-vconsole-setup.service
    491ms dhcpcd.service
    418ms home.mount
    383ms systemd-fsck@dev-disk-by\x2duuid-67C4\x2d6755.service
    339ms systemd-tmpfiles-setup.service
    316ms systemd-sysctl.service
    265ms polkit.service
    200ms upower.service
    160ms boot-efi.mount
    143ms systemd-tmpfiles-clean.service
    128ms systemd-journal-flush.service
    125ms var.mount
    117ms systemd-random-seed-load.service
    104ms systemd-user-sessions.service
    74ms systemd-update-utmp.service
    42ms systemd-udevd.service
    42ms boot.mount
    No way that amounts to 1 minute 33 seconds.
    Last edited by w201 (2013-05-31 00:41:06)

    I ran "sudo journalctl -b" on a fresh boot and got 1,229 lines adding up to roughly 54 seconds, starting at 20:22:52, ending at 20:23:43...still doesn't add up to 1 minute 33 seconds as shown by systemd-analyze, but what's interesting is that most of the boot up process is executed very quickly, and only in the last few lines is where most time is spent.
    I will post the log so hopefully someone might shed some light. Like I said, I think the problem is in the last few lines, and I've gone through it several times hoping to find the problem, but I'm still a new so any help is appreciated!
    -- Logs begin at Sun 2013-02-10 02:56:26 EST, end at Sun 2013-05-26 20:23:43 EDT
    May 26 20:22:52 archw201 systemd-journal[126]: Allowing runtime journal files to
    May 26 20:22:52 archw201 kernel: Initializing cgroup subsys cpuset
    May 26 20:22:52 archw201 kernel: Initializing cgroup subsys cpu
    May 26 20:22:52 archw201 kernel: Linux version 3.9.3-1-ARCH (tobias@T-POWA-LX) (
    May 26 20:22:52 archw201 kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UU
    May 26 20:22:52 archw201 kernel: e820: BIOS-provided physical RAM map:
    May 26 20:22:52 archw201 kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000
    May 26 20:22:52 archw201 kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000cf
    May 26 20:22:52 archw201 kernel: BIOS-e820: [mem 0x00000000cf3e1000-0x00000000cf
    May 26 20:22:52 archw201 kernel: BIOS-e820: [mem 0x00000000cf429000-0x00000000cf
    May 26 20:22:52 archw201 kernel: BIOS-e820: [mem 0x00000000cf437000-0x00000000cf
    May 26 20:22:52 archw201 kernel: BIOS-e820: [mem 0x00000000cf438000-0x00000000cf
    May 26 20:22:52 archw201 kernel: BIOS-e820: [mem 0x00000000cf458000-0x00000000cf
    May 26 20:22:52 archw201 kernel: BIOS-e820: [mem 0x00000000cf47a000-0x00000000cf
    May 26 20:22:52 archw201 kernel: BIOS-e820: [mem 0x00000000cf501000-0x00000000cf
    May 26 20:22:52 archw201 kernel: BIOS-e820: [mem 0x00000000cf502000-0x00000000cf
    May 26 20:22:52 archw201 kernel: BIOS-e820: [mem 0x00000000cf514000-0x00000000cf
    May 26 20:22:52 archw201 kernel: BIOS-e820: [mem 0x00000000cf51f000-0x00000000cf
    May 26 20:22:52 archw201 kernel: BIOS-e820: [mem 0x00000000cf530000-0x00000000cf
    May 26 20:22:52 archw201 kernel: BIOS-e820: [mem 0x00000000cf573000-0x00000000cf
    May 26 20:22:52 archw201 kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fe
    May 26 20:22:52 archw201 kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ff
    lines 1-23...skipping...
    -- Logs begin at Sun 2013-02-10 02:56:26 EST, end at Sun 2013-05-26 20:23:43 EDT. --
    May 26 20:22:52 archw201 systemd-journal[126]: Allowing runtime journal files to grow to 195.8M.
    May 26 20:22:52 archw201 kernel: Initializing cgroup subsys cpuset
    May 26 20:22:52 archw201 kernel: Initializing cgroup subsys cpu
    May 26 20:22:52 archw201 kernel: Linux version 3.9.3-1-ARCH (tobias@T-POWA-LX) (gcc version 4.8.0 20130502 (prerelease) (GCC) ) #1 SMP PREEMPT Sun May 19 22:50
    May 26 20:22:52 archw201 kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=633910d4-7549-417b-9b03-a50f633e1a80 ro quiet
    May 26 20:22:52 archw201 kernel: e820: BIOS-provided physical RAM map:
    May 26 20:22:52 archw201 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
    May 26 20:22:52 archw201 kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000cf3e0fff] usable
    May 26 20:22:52 archw201 kernel: BIOS-e820: [mem 0x00000000cf3e1000-0x00000000cf428fff] ACPI NVS
    May 26 20:22:52 archw201 kernel: BIOS-e820: [mem 0x00000000cf429000-0x00000000cf436fff] ACPI data
    May 26 20:22:52 archw201 kernel: BIOS-e820: [mem 0x00000000cf437000-0x00000000cf437fff] ACPI NVS
    May 26 20:22:52 archw201 kernel: BIOS-e820: [mem 0x00000000cf438000-0x00000000cf457fff] reserved
    May 26 20:22:52 archw201 kernel: BIOS-e820: [mem 0x00000000cf458000-0x00000000cf479fff] ACPI NVS
    May 26 20:22:52 archw201 kernel: BIOS-e820: [mem 0x00000000cf47a000-0x00000000cf500fff] reserved
    May 26 20:22:52 archw201 kernel: BIOS-e820: [mem 0x00000000cf501000-0x00000000cf501fff] ACPI NVS
    May 26 20:22:52 archw201 kernel: BIOS-e820: [mem 0x00000000cf502000-0x00000000cf513fff] reserved
    May 26 20:22:52 archw201 kernel: BIOS-e820: [mem 0x00000000cf514000-0x00000000cf51efff] ACPI NVS
    May 26 20:22:52 archw201 kernel: BIOS-e820: [mem 0x00000000cf51f000-0x00000000cf52ffff] reserved
    May 26 20:22:52 archw201 kernel: BIOS-e820: [mem 0x00000000cf530000-0x00000000cf572fff] ACPI NVS
    May 26 20:22:52 archw201 kernel: BIOS-e820: [mem 0x00000000cf573000-0x00000000cf7fffff] usable
    May 26 20:22:52 archw201 kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed3ffff] reserved
    May 26 20:22:52 archw201 kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
    May 26 20:22:52 archw201 kernel: BIOS-e820: [mem 0x0000000100000000-0x000000012dffffff] usable
    May 26 20:22:52 archw201 kernel: NX (Execute Disable) protection: active
    May 26 20:22:52 archw201 kernel: efi: EFI v2.10 by American Megatrends
    May 26 20:22:52 archw201 kernel: efi: SMBIOS=0xcf52eb98 ACPI=0xcf429000 ACPI 2.0=0xcf429000 MPS=0xf4b40
    May 26 20:22:52 archw201 kernel: efi: mem00: type=3, attr=0xf, range=[0x0000000000000000-0x0000000000008000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem01: type=7, attr=0xf, range=[0x0000000000008000-0x0000000000077000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem02: type=4, attr=0xf, range=[0x0000000000077000-0x0000000000078000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem03: type=3, attr=0xf, range=[0x0000000000078000-0x00000000000a0000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem04: type=3, attr=0xf, range=[0x0000000000100000-0x0000000000110000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem05: type=7, attr=0xf, range=[0x0000000000110000-0x0000000001000000) (14MB)
    May 26 20:22:52 archw201 kernel: efi: mem06: type=2, attr=0xf, range=[0x0000000001000000-0x0000000001100000) (1MB)
    May 26 20:22:52 archw201 kernel: efi: mem07: type=4, attr=0xf, range=[0x0000000001100000-0x0000000001562000) (4MB)
    May 26 20:22:52 archw201 kernel: efi: mem08: type=3, attr=0xf, range=[0x0000000001562000-0x0000000001566000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem09: type=4, attr=0xf, range=[0x0000000001566000-0x0000000001585000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem10: type=3, attr=0xf, range=[0x0000000001585000-0x0000000001593000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem11: type=4, attr=0xf, range=[0x0000000001593000-0x000000000159a000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem12: type=3, attr=0xf, range=[0x000000000159a000-0x000000000159f000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem13: type=4, attr=0xf, range=[0x000000000159f000-0x00000000015a5000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem14: type=3, attr=0xf, range=[0x00000000015a5000-0x00000000015a8000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem15: type=4, attr=0xf, range=[0x00000000015a8000-0x00000000015ac000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem16: type=3, attr=0xf, range=[0x00000000015ac000-0x00000000015b0000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem17: type=4, attr=0xf, range=[0x00000000015b0000-0x00000000015b6000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem18: type=3, attr=0xf, range=[0x00000000015b6000-0x00000000015b7000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem19: type=4, attr=0xf, range=[0x00000000015b7000-0x00000000015d3000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem20: type=3, attr=0xf, range=[0x00000000015d3000-0x00000000015df000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem21: type=4, attr=0xf, range=[0x00000000015df000-0x00000000015e4000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem22: type=3, attr=0xf, range=[0x00000000015e4000-0x00000000015ea000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem23: type=4, attr=0xf, range=[0x00000000015ea000-0x000000000160e000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem24: type=3, attr=0xf, range=[0x000000000160e000-0x0000000001627000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem25: type=4, attr=0xf, range=[0x0000000001627000-0x000000000162e000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem26: type=3, attr=0xf, range=[0x000000000162e000-0x0000000001630000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem27: type=4, attr=0xf, range=[0x0000000001630000-0x0000000001631000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem28: type=3, attr=0xf, range=[0x0000000001631000-0x0000000001632000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem29: type=4, attr=0xf, range=[0x0000000001632000-0x0000000001633000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem30: type=3, attr=0xf, range=[0x0000000001633000-0x0000000001635000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem31: type=4, attr=0xf, range=[0x0000000001635000-0x000000000163d000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem32: type=3, attr=0xf, range=[0x000000000163d000-0x0000000001641000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem33: type=4, attr=0xf, range=[0x0000000001641000-0x0000000001644000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem34: type=3, attr=0xf, range=[0x0000000001644000-0x000000000164b000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem35: type=4, attr=0xf, range=[0x000000000164b000-0x000000000165f000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem36: type=3, attr=0xf, range=[0x000000000165f000-0x0000000001669000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem37: type=4, attr=0xf, range=[0x0000000001669000-0x000000000166e000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem38: type=3, attr=0xf, range=[0x000000000166e000-0x0000000001670000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem39: type=4, attr=0xf, range=[0x0000000001670000-0x0000000001672000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem40: type=3, attr=0xf, range=[0x0000000001672000-0x0000000001674000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem41: type=4, attr=0xf, range=[0x0000000001674000-0x0000000001675000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem42: type=3, attr=0xf, range=[0x0000000001675000-0x0000000001677000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem43: type=4, attr=0xf, range=[0x0000000001677000-0x0000000001682000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem44: type=3, attr=0xf, range=[0x0000000001682000-0x0000000001686000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem45: type=4, attr=0xf, range=[0x0000000001686000-0x0000000001687000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem46: type=3, attr=0xf, range=[0x0000000001687000-0x000000000168f000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem47: type=4, attr=0xf, range=[0x000000000168f000-0x0000000001693000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem48: type=3, attr=0xf, range=[0x0000000001693000-0x0000000001695000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem49: type=4, attr=0xf, range=[0x0000000001695000-0x000000000169a000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem50: type=3, attr=0xf, range=[0x000000000169a000-0x000000000169d000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem51: type=4, attr=0xf, range=[0x000000000169d000-0x00000000016d3000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem52: type=3, attr=0xf, range=[0x00000000016d3000-0x00000000016d9000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem53: type=4, attr=0xf, range=[0x00000000016d9000-0x00000000016db000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem54: type=3, attr=0xf, range=[0x00000000016db000-0x00000000016e3000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem55: type=4, attr=0xf, range=[0x00000000016e3000-0x00000000016eb000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem56: type=3, attr=0xf, range=[0x00000000016eb000-0x000000000170a000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem57: type=4, attr=0xf, range=[0x000000000170a000-0x000000000170e000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem58: type=3, attr=0xf, range=[0x000000000170e000-0x0000000001712000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem59: type=4, attr=0xf, range=[0x0000000001712000-0x0000000001722000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem60: type=3, attr=0xf, range=[0x0000000001722000-0x0000000001732000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem61: type=4, attr=0xf, range=[0x0000000001732000-0x00000000017f3000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem62: type=3, attr=0xf, range=[0x00000000017f3000-0x00000000017f5000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem63: type=4, attr=0xf, range=[0x00000000017f5000-0x00000000017f7000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem64: type=3, attr=0xf, range=[0x00000000017f7000-0x00000000017f8000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem65: type=4, attr=0xf, range=[0x00000000017f8000-0x0000000001802000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem66: type=3, attr=0xf, range=[0x0000000001802000-0x0000000001805000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem67: type=4, attr=0xf, range=[0x0000000001805000-0x0000000001cd7000) (4MB)
    May 26 20:22:52 archw201 kernel: efi: mem68: type=3, attr=0xf, range=[0x0000000001cd7000-0x0000000001cda000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem69: type=4, attr=0xf, range=[0x0000000001cda000-0x0000000001cee000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem70: type=3, attr=0xf, range=[0x0000000001cee000-0x0000000001cef000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem71: type=4, attr=0xf, range=[0x0000000001cef000-0x0000000001cf1000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem72: type=3, attr=0xf, range=[0x0000000001cf1000-0x0000000001cf4000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem73: type=4, attr=0xf, range=[0x0000000001cf4000-0x0000000001d04000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem74: type=3, attr=0xf, range=[0x0000000001d04000-0x0000000001d4a000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem75: type=4, attr=0xf, range=[0x0000000001d4a000-0x0000000001d4f000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem76: type=3, attr=0xf, range=[0x0000000001d4f000-0x0000000001d56000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem77: type=4, attr=0xf, range=[0x0000000001d56000-0x0000000001d89000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem78: type=3, attr=0xf, range=[0x0000000001d89000-0x0000000001d8b000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem79: type=4, attr=0xf, range=[0x0000000001d8b000-0x0000000001da2000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem80: type=3, attr=0xf, range=[0x0000000001da2000-0x0000000001dab000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem81: type=4, attr=0xf, range=[0x0000000001dab000-0x0000000001db8000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem82: type=3, attr=0xf, range=[0x0000000001db8000-0x0000000001dc2000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem83: type=4, attr=0xf, range=[0x0000000001dc2000-0x0000000002132000) (3MB)
    May 26 20:22:52 archw201 kernel: efi: mem84: type=3, attr=0xf, range=[0x0000000002132000-0x0000000002142000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem85: type=4, attr=0xf, range=[0x0000000002142000-0x000000000214a000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem86: type=3, attr=0xf, range=[0x000000000214a000-0x000000000214d000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem87: type=4, attr=0xf, range=[0x000000000214d000-0x0000000002154000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem88: type=3, attr=0xf, range=[0x0000000002154000-0x0000000002156000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem89: type=4, attr=0xf, range=[0x0000000002156000-0x0000000002157000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem90: type=3, attr=0xf, range=[0x0000000002157000-0x000000000215c000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem91: type=4, attr=0xf, range=[0x000000000215c000-0x0000000002164000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem92: type=3, attr=0xf, range=[0x0000000002164000-0x0000000002167000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem93: type=4, attr=0xf, range=[0x0000000002167000-0x000000000216b000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem94: type=3, attr=0xf, range=[0x000000000216b000-0x0000000002172000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem95: type=4, attr=0xf, range=[0x0000000002172000-0x0000000002178000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem96: type=3, attr=0xf, range=[0x0000000002178000-0x000000000217b000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem97: type=4, attr=0xf, range=[0x000000000217b000-0x000000000217c000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem98: type=3, attr=0xf, range=[0x000000000217c000-0x000000000217e000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem99: type=4, attr=0xf, range=[0x000000000217e000-0x0000000002186000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem100: type=3, attr=0xf, range=[0x0000000002186000-0x000000000218b000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem101: type=4, attr=0xf, range=[0x000000000218b000-0x00000000021a8000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem102: type=3, attr=0xf, range=[0x00000000021a8000-0x00000000021ad000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem103: type=4, attr=0xf, range=[0x00000000021ad000-0x00000000021af000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem104: type=3, attr=0xf, range=[0x00000000021af000-0x00000000021b9000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem105: type=4, attr=0xf, range=[0x00000000021b9000-0x00000000021bb000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem106: type=3, attr=0xf, range=[0x00000000021bb000-0x00000000021bd000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem107: type=4, attr=0xf, range=[0x00000000021bd000-0x00000000021bf000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem108: type=3, attr=0xf, range=[0x00000000021bf000-0x00000000021c1000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem109: type=4, attr=0xf, range=[0x00000000021c1000-0x00000000021c4000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem110: type=3, attr=0xf, range=[0x00000000021c4000-0x00000000021c8000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem111: type=4, attr=0xf, range=[0x00000000021c8000-0x00000000021cd000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem112: type=3, attr=0xf, range=[0x00000000021cd000-0x00000000021d0000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem113: type=4, attr=0xf, range=[0x00000000021d0000-0x00000000021d9000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem114: type=3, attr=0xf, range=[0x00000000021d9000-0x00000000021db000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem115: type=4, attr=0xf, range=[0x00000000021db000-0x00000000021ee000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem116: type=3, attr=0xf, range=[0x00000000021ee000-0x00000000021f3000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem117: type=4, attr=0xf, range=[0x00000000021f3000-0x00000000021fa000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem118: type=3, attr=0xf, range=[0x00000000021fa000-0x0000000002206000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem119: type=4, attr=0xf, range=[0x0000000002206000-0x000000000221b000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem120: type=3, attr=0xf, range=[0x000000000221b000-0x000000000221e000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem121: type=4, attr=0xf, range=[0x000000000221e000-0x0000000002227000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem122: type=7, attr=0xf, range=[0x0000000002227000-0x000000000222a000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem123: type=3, attr=0xf, range=[0x000000000222a000-0x000000000223c000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem124: type=4, attr=0xf, range=[0x000000000223c000-0x0000000002504000) (2MB)
    May 26 20:22:52 archw201 kernel: efi: mem125: type=3, attr=0xf, range=[0x0000000002504000-0x000000000250f000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem126: type=4, attr=0xf, range=[0x000000000250f000-0x0000000002511000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem127: type=7, attr=0xf, range=[0x0000000002511000-0x0000000002519000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem128: type=4, attr=0xf, range=[0x0000000002519000-0x00000000026c6000) (1MB)
    May 26 20:22:52 archw201 kernel: efi: mem129: type=7, attr=0xf, range=[0x00000000026c6000-0x00000000026d7000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem130: type=4, attr=0xf, range=[0x00000000026d7000-0x0000000002704000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem131: type=7, attr=0xf, range=[0x0000000002704000-0x0000000002725000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem132: type=4, attr=0xf, range=[0x0000000002725000-0x0000000002727000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem133: type=1, attr=0xf, range=[0x0000000002727000-0x0000000002745000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem134: type=7, attr=0xf, range=[0x0000000002745000-0x00000000027cc000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem135: type=4, attr=0xf, range=[0x00000000027cc000-0x00000000027d7000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem136: type=7, attr=0xf, range=[0x00000000027d7000-0x000000000282d000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem137: type=4, attr=0xf, range=[0x000000000282d000-0x000000000282e000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem138: type=7, attr=0xf, range=[0x000000000282e000-0x0000000002835000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem139: type=4, attr=0xf, range=[0x0000000002835000-0x0000000002838000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem140: type=7, attr=0xf, range=[0x0000000002838000-0x00000000028c6000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem141: type=4, attr=0xf, range=[0x00000000028c6000-0x00000000028d1000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem142: type=7, attr=0xf, range=[0x00000000028d1000-0x000000000292d000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem143: type=4, attr=0xf, range=[0x000000000292d000-0x000000000292e000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem144: type=7, attr=0xf, range=[0x000000000292e000-0x0000000002930000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem145: type=4, attr=0xf, range=[0x0000000002930000-0x0000000002931000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem146: type=7, attr=0xf, range=[0x0000000002931000-0x0000000002933000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem147: type=4, attr=0xf, range=[0x0000000002933000-0x0000000002934000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem148: type=7, attr=0xf, range=[0x0000000002934000-0x0000000002961000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem149: type=4, attr=0xf, range=[0x0000000002961000-0x0000000002962000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem150: type=7, attr=0xf, range=[0x0000000002962000-0x00000000029c0000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem151: type=4, attr=0xf, range=[0x00000000029c0000-0x00000000029cb000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem152: type=7, attr=0xf, range=[0x00000000029cb000-0x0000000002a27000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem153: type=4, attr=0xf, range=[0x0000000002a27000-0x0000000002a2b000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem154: type=7, attr=0xf, range=[0x0000000002a2b000-0x0000000002a58000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem155: type=4, attr=0xf, range=[0x0000000002a58000-0x0000000002a59000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem156: type=7, attr=0xf, range=[0x0000000002a59000-0x0000000002ab7000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem157: type=4, attr=0xf, range=[0x0000000002ab7000-0x0000000002ac2000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem158: type=7, attr=0xf, range=[0x0000000002ac2000-0x0000000002b1a000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem159: type=4, attr=0xf, range=[0x0000000002b1a000-0x0000000002b1b000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem160: type=7, attr=0xf, range=[0x0000000002b1b000-0x0000000002b20000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem161: type=4, attr=0xf, range=[0x0000000002b20000-0x0000000002b21000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem162: type=7, attr=0xf, range=[0x0000000002b21000-0x0000000002baf000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem163: type=4, attr=0xf, range=[0x0000000002baf000-0x0000000002bba000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem164: type=7, attr=0xf, range=[0x0000000002bba000-0x0000000002c17000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem165: type=4, attr=0xf, range=[0x0000000002c17000-0x0000000002c55000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem166: type=7, attr=0xf, range=[0x0000000002c55000-0x0000000002ca6000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem167: type=4, attr=0xf, range=[0x0000000002ca6000-0x0000000002cb1000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem168: type=7, attr=0xf, range=[0x0000000002cb1000-0x0000000002cf2000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem169: type=4, attr=0xf, range=[0x0000000002cf2000-0x0000000002cf3000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem170: type=7, attr=0xf, range=[0x0000000002cf3000-0x0000000002d0a000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem171: type=4, attr=0xf, range=[0x0000000002d0a000-0x0000000002d0b000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem172: type=7, attr=0xf, range=[0x0000000002d0b000-0x0000000002d10000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem173: type=4, attr=0xf, range=[0x0000000002d10000-0x00000000030f9000) (3MB)
    May 26 20:22:52 archw201 kernel: efi: mem174: type=7, attr=0xf, range=[0x00000000030f9000-0x0000000003136000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem175: type=4, attr=0xf, range=[0x0000000003136000-0x00000000031f1000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem176: type=2, attr=0xf, range=[0x00000000031f1000-0x0000000004142000) (15MB)
    May 26 20:22:52 archw201 kernel: efi: mem177: type=7, attr=0xf, range=[0x0000000004142000-0x0000000005000000) (14MB)
    May 26 20:22:52 archw201 kernel: efi: mem178: type=2, attr=0xf, range=[0x0000000005000000-0x0000000005f51000) (15MB)
    May 26 20:22:52 archw201 kernel: efi: mem179: type=7, attr=0xf, range=[0x0000000005f51000-0x0000000037a58000) (795MB)
    May 26 20:22:52 archw201 kernel: efi: mem180: type=2, attr=0xf, range=[0x0000000037a58000-0x0000000037d24000) (2MB)
    May 26 20:22:52 archw201 kernel: efi: mem181: type=7, attr=0xf, range=[0x0000000037d24000-0x000000009be3e000) (1601MB)
    May 26 20:22:52 archw201 kernel: efi: mem182: type=2, attr=0xf, range=[0x000000009be3e000-0x00000000cf3e1000) (821MB)
    May 26 20:22:52 archw201 kernel: efi: mem183: type=10, attr=0xf, range=[0x00000000cf3e1000-0x00000000cf429000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem184: type=9, attr=0xf, range=[0x00000000cf429000-0x00000000cf437000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem185: type=10, attr=0xf, range=[0x00000000cf437000-0x00000000cf438000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem186: type=0, attr=0xf, range=[0x00000000cf438000-0x00000000cf447000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem187: type=5, attr=0x800000000000000f, range=[0x00000000cf447000-0x00000000cf44c000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem188: type=0, attr=0xf, range=[0x00000000cf44c000-0x00000000cf44f000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem189: type=6, attr=0x800000000000000f, range=[0x00000000cf44f000-0x00000000cf458000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem190: type=10, attr=0xf, range=[0x00000000cf458000-0x00000000cf47a000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem191: type=6, attr=0x800000000000000f, range=[0x00000000cf47a000-0x00000000cf4fb000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem192: type=5, attr=0x800000000000000f, range=[0x00000000cf4fb000-0x00000000cf500000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem193: type=6, attr=0x800000000000000f, range=[0x00000000cf500000-0x00000000cf501000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem194: type=10, attr=0xf, range=[0x00000000cf501000-0x00000000cf502000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem195: type=6, attr=0x800000000000000f, range=[0x00000000cf502000-0x00000000cf504000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem196: type=0, attr=0xf, range=[0x00000000cf504000-0x00000000cf514000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem197: type=10, attr=0xf, range=[0x00000000cf514000-0x00000000cf51f000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem198: type=5, attr=0x800000000000000f, range=[0x00000000cf51f000-0x00000000cf521000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem199: type=6, attr=0x800000000000000f, range=[0x00000000cf521000-0x00000000cf523000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem200: type=5, attr=0x800000000000000f, range=[0x00000000cf523000-0x00000000cf52d000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem201: type=6, attr=0x800000000000000f, range=[0x00000000cf52d000-0x00000000cf530000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem202: type=10, attr=0xf, range=[0x00000000cf530000-0x00000000cf573000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem203: type=3, attr=0xf, range=[0x00000000cf573000-0x00000000cf7f5000) (2MB)
    May 26 20:22:52 archw201 kernel: efi: mem204: type=4, attr=0xf, range=[0x00000000cf7f5000-0x00000000cf7f8000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem205: type=3, attr=0xf, range=[0x00000000cf7f8000-0x00000000cf800000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem206: type=7, attr=0xf, range=[0x0000000100000000-0x000000012e000000) (736MB)
    May 26 20:22:52 archw201 kernel: efi: mem207: type=11, attr=0x8000000000000001, range=[0x00000000fed1c000-0x00000000fed20000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem208: type=11, attr=0x8000000000000001, range=[0x00000000fed20000-0x00000000fed40000) (0MB)
    May 26 20:22:52 archw201 kernel: efi: mem209: type=11, attr=0x8000000000000001, range=[0x00000000ff000000-0x0000000100000000) (16MB)
    May 26 20:22:52 archw201 kernel: SMBIOS 2.7 present.
    May 26 20:22:52 archw201 kernel: DMI: Hewlett-Packard HP Compaq 8200 Elite SFF PC/1495, BIOS J01 v02.01 04/06/2011
    May 26 20:22:52 archw201 kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
    May 26 20:22:52 archw201 kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
    May 26 20:22:52 archw201 kernel: No AGP bridge found
    May 26 20:22:52 archw201 kernel: e820: last_pfn = 0x12e000 max_arch_pfn = 0x400000000
    May 26 20:22:52 archw201 kernel: MTRR default type: write-back
    May 26 20:22:52 archw201 kernel: MTRR fixed ranges enabled:
    May 26 20:22:52 archw201 kernel: 00000-9FFFF write-back
    May 26 20:22:52 archw201 kernel: A0000-BFFFF uncachable
    May 26 20:22:52 archw201 kernel: C0000-FFFFF write-protect
    May 26 20:22:52 archw201 kernel: MTRR variable ranges enabled:
    May 26 20:22:52 archw201 kernel: 0 base 0D0000000 mask FF0000000 uncachable
    May 26 20:22:52 archw201 kernel: 1 base 0E0000000 mask FE0000000 uncachable
    May 26 20:22:52 archw201 kernel: 2 base 12E000000 mask FFE000000 uncachable
    May 26 20:22:52 archw201 kernel: 3 disabled
    May 26 20:22:52 archw201 kernel: 4 disabled
    May 26 20:22:52 archw201 kernel: 5 disabled
    May 26 20:22:52 archw201 kernel: 6 disabled
    May 26 20:22:52 archw201 kernel: 7 disabled
    May 26 20:22:52 archw201 kernel: 8 disabled
    May 26 20:22:52 archw201 kernel: 9 disabled
    May 26 20:22:52 archw201 kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    May 26 20:22:52 archw201 kernel: e820: last_pfn = 0xcf800 max_arch_pfn = 0x400000000
    May 26 20:22:52 archw201 kernel: found SMP MP-table at [mem 0x000f4b30-0x000f4b3f] mapped at [ffff8800000f4b30]
    May 26 20:22:52 archw201 kernel: Scanning 1 areas for low memory corruption
    May 26 20:22:52 archw201 kernel: Base memory trampoline at [ffff880000095000] 95000 size 24576
    May 26 20:22:52 archw201 kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
    May 26 20:22:52 archw201 kernel: [mem 0x00000000-0x000fffff] page 4k
    May 26 20:22:52 archw201 kernel: BRK [0x05b30000, 0x05b30fff] PGTABLE
    May 26 20:22:52 archw201 kernel: BRK [0x05b31000, 0x05b31fff] PGTABLE
    May 26 20:22:52 archw201 kernel: BRK [0x05b32000, 0x05b32fff] PGTABLE
    May 26 20:22:52 archw201 kernel: init_memory_mapping: [mem 0x12de00000-0x12dffffff]
    May 26 20:22:52 archw201 kernel: [mem 0x12de00000-0x12dffffff] page 2M
    May 26 20:22:52 archw201 kernel: BRK [0x05b33000, 0x05b33fff] PGTABLE
    May 26 20:22:52 archw201 kernel: init_memory_mapping: [mem 0x12c000000-0x12ddfffff]
    May 26 20:22:52 archw201 kernel: [mem 0x12c000000-0x12ddfffff] page 2M
    May 26 20:22:52 archw201 kernel: init_memory_mapping: [mem 0x100000000-0x12bffffff]
    May 26 20:22:52 archw201 kernel: [mem 0x100000000-0x12bffffff] page 2M
    May 26 20:22:52 archw201 kernel: init_memory_mapping: [mem 0x00100000-0xcf3e0fff]
    May 26 20:22:52 archw201 kernel: [mem 0x00100000-0x001fffff] page 4k
    May 26 20:22:52 archw201 kernel: [mem 0x00200000-0xcf1fffff] page 2M
    May 26 20:22:52 archw201 kernel: [mem 0xcf200000-0xcf3e0fff] page 4k
    May 26 20:22:52 archw201 kernel: init_memory_mapping: [mem 0xcf573000-0xcf7fffff]
    May 26 20:22:52 archw201 kernel: [mem 0xcf573000-0xcf5fffff] page 4k
    May 26 20:22:52 archw201 kernel: [mem 0xcf600000-0xcf7fffff] page 2M
    May 26 20:22:52 archw201 kernel: BRK [0x05b34000, 0x05b34fff] PGTABLE
    May 26 20:22:52 archw201 kernel: RAMDISK: [mem 0x37a58000-0x37d23fff]
    May 26 20:22:52 archw201 kernel: ACPI: RSDP 00000000cf429000 00024 (v02 HPQOEM)
    May 26 20:22:52 archw201 kernel: ACPI: XSDT 00000000cf429078 0006C (v01 HPQOEM SLIC-BPC 01072009 AMI 00010013)
    May 26 20:22:52 archw201 kernel: ACPI: FACP 00000000cf4309b8 000F4 (v04 HPQOEM SLIC-BPC 01072009 AMI 00010013)
    May 26 20:22:52 archw201 kernel: ACPI: DSDT 00000000cf429170 07841 (v02 HPQOEM SLIC-BPC 00000007 INTL 20051117)
    May 26 20:22:52 archw201 kernel: ACPI: FACS 00000000cf516f80 00040
    May 26 20:22:52 archw201 kernel: ACPI: APIC 00000000cf430ab0 00072 (v03 HPQOEM SLIC-BPC 01072009 AMI 00010013)
    May 26 20:22:52 archw201 kernel: ACPI: SSDT 00000000cf430b28 00102 (v01 AMICPU PROC 00000001 MSFT 03000001)
    May 26 20:22:52 archw201 kernel: ACPI: MCFG 00000000cf430c30 0003C (v01 HPQOEM SLIC-BPC 01072009 MSFT 00000097)
    May 26 20:22:52 archw201 kernel: ACPI: HPET 00000000cf430c70 00038 (v01 HPQOEM SLIC-BPC 01072009 AMI. 00000004)
    May 26 20:22:52 archw201 kernel: ACPI: ASF! 00000000cf430ca8 000A0 (v32 INTEL HCG 00000001 TFSM 000F4240)
    May 26 20:22:52 archw201 kernel: ACPI: SSDT 00000000cf430d48 050F4 (v01 COMPAQ WMI 00000001 MSFT 03000001)
    May 26 20:22:52 archw201 kernel: ACPI: SLIC 00000000cf435e40 00176 (v01 HPQOEM SLIC-BPC 00000001 00000000)
    May 26 20:22:52 archw201 kernel: ACPI: TCPA 00000000cf435fb8 00032 (v02 APTIO4 NAPAASF 00000001 MSFT 01000013)
    May 26 20:22:52 archw201 kernel: ACPI: Local APIC address 0xfee00000
    May 26 20:22:52 archw201 kernel: No NUMA configuration found
    May 26 20:22:52 archw201 kernel: Faking a node at [mem 0x0000000000000000-0x000000012dffffff]
    May 26 20:22:52 archw201 kernel: Initmem setup node 0 [mem 0x00000000-0x12dffffff]
    May 26 20:22:52 archw201 kernel: NODE_DATA [mem 0x12dff7000-0x12dffbfff]
    May 26 20:22:52 archw201 kernel: [ffffea0000000000-ffffea0004bfffff] PMD -> [ffff880129600000-ffff88012d5fffff] on node 0
    May 26 20:22:52 archw201 kernel: Zone ranges:
    May 26 20:22:52 archw201 kernel: DMA [mem 0x00001000-0x00ffffff]
    May 26 20:22:52 archw201 kernel: DMA32 [mem 0x01000000-0xffffffff]
    May 26 20:22:52 archw201 kernel: Normal [mem 0x100000000-0x12dffffff]
    May 26 20:22:52 archw201 kernel: Movable zone start for each node
    May 26 20:22:52 archw201 kernel: Early memory node ranges
    May 26 20:22:52 archw201 kernel: node 0: [mem 0x00001000-0x0009ffff]
    May 26 20:22:52 archw201 kernel: node 0: [mem 0x00100000-0xcf3e0fff]
    May 26 20:22:52 archw201 kernel: node 0: [mem 0xcf573000-0xcf7fffff]
    May 26 20:22:52 archw201 kernel: node 0: [mem 0x100000000-0x12dffffff]
    May 26 20:22:52 archw201 kernel: On node 0 totalpages: 1037837
    May 26 20:22:52 archw201 kernel: DMA zone: 64 pages used for memmap
    May 26 20:22:52 archw201 kernel: DMA zone: 46 pages reserved
    May 26 20:22:52 archw201 kernel: DMA zone: 3999 pages, LIFO batch:0
    May 26 20:22:52 archw201 kernel: DMA32 zone: 13210 pages used for memmap
    May 26 20:22:52 archw201 kernel: DMA32 zone: 845422 pages, LIFO batch:31
    May 26 20:22:52 archw201 kernel: Normal zone: 2944 pages used for memmap
    May 26 20:22:52 archw201 kernel: Normal zone: 188416 pages, LIFO batch:31
    May 26 20:22:52 archw201 kernel: ACPI: PM-Timer IO Port: 0x408
    May 26 20:22:52 archw201 kernel: ACPI: Local APIC address 0xfee00000
    May 26 20:22:52 archw201 kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
    May 26 20:22:52 archw201 kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
    May 26 20:22:52 archw201 kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
    May 26 20:22:52 archw201 kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)
    May 26 20:22:52 archw201 kernel: ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
    May 26 20:22:52 archw201 kernel: ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
    May 26 20:22:52 archw201 kernel: IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
    May 26 20:22:52 archw201 kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    May 26 20:22:52 archw201 kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    May 26 20:22:52 archw201 kernel: ACPI: IRQ0 used by override.
    May 26 20:22:52 archw201 kernel: ACPI: IRQ2 used by override.
    May 26 20:22:52 archw201 kernel: ACPI: IRQ9 used by override.
    May 26 20:22:52 archw201 kernel: Using ACPI (MADT) for SMP configuration information
    May 26 20:22:52 archw201 kernel: ACPI: HPET id: 0x8086a701 base: 0xfed00000
    May 26 20:22:52 archw201 kernel: smpboot: Allowing 4 CPUs, 0 hotplug CPUs
    May 26 20:22:52 archw201 kernel: nr_irqs_gsi: 40
    May 26 20:22:52 archw201 kernel: PM: Registered nosave memory: 00000000000a0000 - 0000000000100000
    May 26 20:22:52 archw201 kernel: PM: Registered nosave memory: 00000000cf3e1000 - 00000000cf429000
    May 26 20:22:52 archw201 kernel: PM: Registered nosave memory: 00000000cf429000 - 00000000cf437000
    May 26 20:22:52 archw201 kernel: PM: Registered nosave memory: 00000000cf437000 - 00000000cf438000
    May 26 20:22:52 archw201 kernel: PM: Registered nosave memory: 00000000cf438000 - 00000000cf458000
    May 26 20:22:52 archw201 kernel: PM: Registered nosave memory: 00000000cf458000 - 00000000cf47a000
    May 26 20:22:52 archw201 kernel: PM: Registered nosave memory: 00000000cf47a000 - 00000000cf501000
    May 26 20:22:52 archw201 kernel: PM: Registered nosave memory: 00000000cf501000 - 00000000cf502000
    May 26 20:22:52 archw201 kernel: PM: Registered nosave memory: 00000000cf502000 - 00000000cf514000
    May 26 20:22:52 archw201 kernel: PM: Registered nosave memory: 00000000cf514000 - 00000000cf51f000
    May 26 20:22:52 archw201 kernel: PM: Registered nosave memory: 00000000cf51f000 - 00000000cf530000
    May 26 20:22:52 archw201 kernel: PM: Registered nosave memory: 00000000cf530000 - 00000000cf573000
    May 26 20:22:52 archw201 kernel: PM: Registered nosave memory: 00000000cf800000 - 00000000fed1c000
    May 26 20:22:52 archw201 kernel: PM: Registered nosave memory: 00000000fed1c000 - 00000000fed40000
    May 26 20:22:52 archw201 kernel: PM: Registered nosave memory: 00000000fed40000 - 00000000ff000000
    May 26 20:22:52 archw201 kernel: PM: Registered nosave memory: 00000000ff000000 - 0000000100000000
    May 26 20:22:52 archw201 kernel: e820: [mem 0xcf800000-0xfed1bfff] available for PCI devices
    May 26 20:22:52 archw201 kernel: Booting paravirtualized kernel on bare hardware
    May 26 20:22:52 archw201 kernel: setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:4 nr_node_ids:1
    May 26 20:22:52 archw201 kernel: PERCPU: Embedded 28 pages/cpu @ffff88012dc00000 s85824 r8192 d20672 u524288
    May 26 20:22:52 archw201 kernel: pcpu-alloc: s85824 r8192 d20672 u524288 alloc=1*2097152
    May 26 20:22:52 archw201 kernel: pcpu-alloc: [0] 0 1 2 3
    May 26 20:22:52 archw201 kernel: Built 1 zonelists in Node order, mobility grouping on. Total pages: 1021573
    May 26 20:22:52 archw201 kernel: Policy zone: Normal
    May 26 20:22:52 archw201 kernel: Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=633910d4-7549-417b-9b03-a50f633e1a80 ro quiet
    May 26 20:22:52 archw201 kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
    May 26 20:22:52 archw201 kernel: __ex_table already sorted, skipping sort
    May 26 20:22:52 archw201 kernel: xsave: enabled xstate_bv 0x7, cntxt size 0x340
    May 26 20:22:52 archw201 kernel: Checking aperture...
    May 26 20:22:52 archw201 kernel: No AGP bridge found
    May 26 20:22:52 archw201 kernel: Calgary: detecting Calgary via BIOS EBDA area
    May 26 20:22:52 archw201 kernel: Calgary: Unable to locate Rio Grande table in EBDA - bailing!
    May 26 20:22:52 archw201 kernel: Memory: 3974112k/4947968k available (4983k kernel code, 796620k absent, 177236k reserved, 3967k data, 1092k init)
    May 26 20:22:52 archw201 kernel: SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
    May 26 20:22:52 archw201 kernel: Preemptible hierarchical RCU implementation.
    May 26 20:22:52 archw201 kernel: RCU dyntick-idle grace-period acceleration is enabled.
    May 26 20:22:52 archw201 kernel: Dump stacks of tasks blocking RCU-preempt GP.
    May 26 20:22:52 archw201 kernel: RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=4.
    May 26 20:22:52 archw201 kernel: NR_IRQS:4352 nr_irqs:712 16
    May 26 20:22:52 archw201 kernel: Console: colour dummy device 80x25
    May 26 20:22:52 archw201 kernel: console [tty0] enabled
    May 26 20:22:52 archw201 kernel: allocated 16777216 bytes of page_cgroup
    May 26 20:22:52 archw201 kernel: please try 'cgroup_disable=memory' option if you don't want memory cgroups
    May 26 20:22:52 archw201 kernel: hpet clockevent registered
    May 26 20:22:52 archw201 kernel: tsc: Fast TSC calibration failed
    May 26 20:22:52 archw201 kernel: tsc: PIT calibration matches HPET. 1 loops
    May 26 20:22:52 archw201 kernel: tsc: Detected 3092.785 MHz processor
    May 26 20:22:52 archw201 kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 6188.30 BogoMIPS (lpj=10309283)
    May 26 20:22:52 archw201 kernel: pid_max: default: 32768 minimum: 301
    May 26 20:22:52 archw201 kernel: init_memory_mapping: [mem 0xcf447000-0xcf44bfff]
    May 26 20:22:52 archw201 kernel: [mem 0xcf447000-0xcf44bfff] page 4k
    May 26 20:22:52 archw201 kernel: init_memory_mapping: [mem 0xcf44f000-0xcf457fff]
    May 26 20:22:52 archw201 kernel: [mem 0xcf44f000-0xcf457fff] page 4k
    May 26 20:22:52 archw201 kernel: init_memory_mapping: [mem 0xcf47a000-0xcf4fafff]
    May 26 20:22:52 archw201 kernel: [mem 0xcf47a000-0xcf4fafff] page 4k
    May 26 20:22:52 archw201 kernel: init_memory_mapping: [mem 0xcf4fb000-0xcf4fffff]
    May 26 20:22:52 archw201 kernel: [mem 0xcf4fb000-0xcf4fffff] page 4k
    May 26 20:22:52 archw201 kernel: init_memory_mapping: [mem 0xcf500000-0xcf500fff]
    May 26 20:22:52 archw201 kernel: [mem 0xcf500000-0xcf500fff] page 4k
    May 26 20:22:52 archw201 kernel: init_memory_mapping: [mem 0xcf502000-0xcf503fff]
    May 26 20:22:52 archw201 kernel: [mem 0xcf502000-0xcf503fff] page 4k
    May 26 20:22:52 archw201 kernel: init_memory_mapping: [mem 0xcf51f000-0xcf520fff]
    May 26 20:22:52 archw201 kernel: [mem 0xcf51f000-0xcf520fff] page 4k
    May 26 20:22:52 archw201 kernel: init_memory_mapping: [mem 0xcf521000-0xcf522fff]
    May 26 20:22:52 archw201 kernel: [mem 0xcf521000-0xcf522fff] page 4k
    May 26 20:22:52 archw201 kernel: init_memory_mapping: [mem 0xcf523000-0xcf52cfff]
    May 26 20:22:52 archw201 kernel: [mem 0xcf523000-0xcf52cfff] page 4k
    May 26 20:22:52 archw201 kernel: init_memory_mapping: [mem 0xcf52d000-0xcf52ffff]
    May 26 20:22:52 archw201 kernel: [mem 0xcf52d000-0xcf52ffff] page 4k
    May 26 20:22:52 archw201 kernel: Security Framework initialized
    May 26 20:22:52 archw201 kernel: AppArmor: AppArmor disabled by boot time parameter
    May 26 20:22:52 archw201 kernel: Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
    May 26 20:22:52 archw201 kernel: Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
    May 26 20:22:52 archw201 kernel: Mount-cache hash table entries: 256
    May 26 20:22:52 archw201 kernel: Initializing cgroup subsys cpuacct
    May 26 20:22:52 archw201 kernel: Initializing cgroup subsys memory
    May 26 20:22:52 archw201 kernel: Initializing cgroup subsys devices
    May 26 20:22:52 archw201 kernel: Initializing cgroup subsys freezer
    May 26 20:22:52 archw201 kernel: Initializing cgroup subsys net_cls
    May 26 20:22:52 archw201 kernel: Initializing cgroup subsys blkio
    May 26 20:22:52 archw201 kernel: CPU: Physical Processor ID: 0
    May 26 20:22:52 archw201 kernel: CPU: Processor Core ID: 0
    May 26 20:22:52 archw201 kernel: [117B blob data]
    May 26 20:22:52 archw201 kernel: mce: CPU supports 9 MCE banks
    May 26 20:22:52 archw201 kernel: CPU0: Thermal monitoring enabled (TM1)
    May 26 20:22:52 archw201 kernel: [117B blob data]
    May 26 20:22:52 archw201 kernel: Freeing SMP alternatives: 20k freed
    May 26 20:22:52 archw201 kernel: ACPI: Core revision 20130117
    May 26 20:22:52 archw201 kernel: ACPI: All ACPI Tables successfully acquired
    May 26 20:22:52 archw201 kernel: ftrace: allocating 19546 entries in 77 pages
    May 26 20:22:52 archw201 kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    May 26 20:22:52 archw201 kernel: smpboot: CPU0: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (fam: 06, model: 2a, stepping: 07)
    May 26 20:22:52 archw201 kernel: TSC deadline timer enabled
    May 26 20:22:52 archw201 kernel: Performance Events: PEBS fmt1+, 16-deep LBR, SandyBridge events, Intel PMU driver.
    May 26 20:22:52 archw201 kernel: perf_event_intel: PEBS disabled due to CPU errata, please upgrade microcode
    May 26 20:22:52 archw201 kernel: ... version: 3
    May 26 20:22:52 archw201 kernel: ... bit width: 48
    May 26 20:22:52 archw201 kernel: ... generic registers: 8
    May 26 20:22:52 archw201 kernel: ... value mask: 0000ffffffffffff
    May 26 20:22:52 archw201 kernel: ... max period: 000000007fffffff
    May 26 20:22:52 archw201 kernel: ... fixed-purpose events: 3
    May 26 20:22:52 archw201 kernel: ... event mask: 00000007000000ff
    May 26 20:22:52 archw201 kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
    May 26 20:22:52 archw201 kernel: smpboot: Booting Node 0, Processors #1 #2 #3 OK
    May 26 20:22:52 archw201 kernel: Brought up 4 CPUs
    May 26 20:22:52 archw201 kernel: smpboot: Total of 4 processors activated (24752.20 BogoMIPS)
    May 26 20:22:52 archw201 kernel: devtmpfs: initialized
    May 26 20:22:52 archw201 kernel: PM: Registering ACPI NVS region [mem 0xcf3e1000-0xcf428fff] (294912 bytes)
    May 26 20:22:52 archw201 kernel: PM: Registering ACPI NVS region [mem 0xcf437000-0xcf437fff] (4096 bytes)
    May 26 20:22:52 archw201 kernel: PM: Registering ACPI NVS region [mem 0xcf458000-0xcf479fff] (139264 bytes)
    May 26 20:22:52 archw201 kernel: PM: Registering ACPI NVS region [mem 0xcf501000-0xcf501fff] (4096 bytes)
    May 26 20:22:52 archw201 kernel: PM: Registering ACPI NVS region [mem 0xcf514000-0xcf51efff] (45056 bytes)
    May 26 20:22:52 archw201 kernel: PM: Registering ACPI NVS region [mem 0xcf530000-0xcf572fff] (274432 bytes)
    May 26 20:22:52 archw201 kernel: reboot: BIOS series board detected. Selecting HP Compaq Laptop-method for reboots.
    May 26 20:22:52 archw201 kernel: RTC time: 0:22:48, date: 05/27/13
    May 26 20:22:52 archw201 kernel: NET: Registered protocol family 16
    May 26 20:22:52 archw201 kernel: ACPI: bus type PCI registered
    May 26 20:22:52 archw201 kernel: PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
    May 26 20:22:52 archw201 kernel: PCI: not using MMCONFIG
    May 26 20:22:52 archw201 kernel: PCI: Using configuration type 1 for base access
    May 26 20:22:52 archw201 kernel: bio: create slab <bio-0> at 0
    May 26 20:22:52 archw201 kernel: ACPI: Added _OSI(Module Device)
    May 26 20:22:52 archw201 kernel: ACPI: Added _OSI(Processor Device)
    May 26 20:22:52 archw201 kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
    May 26 20:22:52 archw201 kernel: ACPI: Added _OSI(Processor Aggregator Device)
    May 26 20:22:52 archw201 kernel: ACPI: EC: Look up EC in DSDT
    May 26 20:22:52 archw201 kernel: ACPI: Executed 1 blocks of module-level executable AML code
    May 26 20:22:52 archw201 kernel: ACPI: SSDT 00000000cf515c18 0038C (v01 AMI IST 00000001 MSFT 03000001)
    May 26 20:22:52 archw201 kernel: ACPI: Dynamic OEM Table Load:
    May 26 20:22:52 archw201 kernel: ACPI: SSDT (null) 0038C (v01 AMI IST 00000001 MSFT 03000001)
    May 26 20:22:52 archw201 kernel: ACPI: SSDT 00000000cf516e18 00084 (v01 AMI CST 00000001 MSFT 03000001)
    May 26 20:22:52 archw201 kernel: ACPI: Dynamic OEM Table Load:
    May 26 20:22:52 archw201 kernel: ACPI: SSDT (null) 00084 (v01 AMI CST 00000001 MSFT 03000001)
    May 26 20:22:52 archw201 kernel: ACPI: Interpreter enabled
    May 26 20:22:52 archw201 kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20130117/hwxface-568)
    May 26 20:22:52 archw201 kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20130117/hwxface-568)
    May 26 20:22:52 archw201 kernel: ACPI: (supports S0 S3 S4 S5)
    May 26 20:22:52 archw201 kernel: ACPI: Using IOAPIC for interrupt routing
    May 26 20:22:52 archw201 kernel: PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
    May 26 20:22:52 archw201 kernel: PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in ACPI motherboard resources
    May 26 20:22:52 archw201 kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
    May 26 20:22:52 archw201 kernel: [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
    May 26 20:22:52 archw201 kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
    May 26 20:22:52 archw201 kernel: PCI host bridge to bus 0000:00
    May 26 20:22:52 archw201 kernel: pci_bus 0000:00: root bus resource [bus 00-ff]
    May 26 20:22:52 archw201 kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x03af]
    May 26 20:22:52 archw201 kernel: pci_bus 0000:00: root bus resource [io 0x03e0-0x0cf7]
    May 26 20:22:52 archw201 kernel: pci_bus 0000:00: root bus resource [io 0x03b0-0x03df]
    May 26 20:22:52 archw201 kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
    May 26 20:22:52 archw201 kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
    May 26 20:22:52 archw201 kernel: pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000dffff]
    May 26 20:22:52 archw201 kernel: pci_bus 0000:00: root bus resource [mem 0xd0000000-0xffffffff]
    May 26 20:22:52 archw201 kernel: pci 0000:00:00.0: [8086:0100] type 00 class 0x060000
    May 26 20:22:52 archw201 kernel: pci 0000:00:01.0: [8086:0101] type 01 class 0x060400
    May 26 20:22:52 archw201 kernel: pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
    May 26 20:22:52 archw201 kernel: pci 0000:00:01.0: System wakeup disabled by ACPI
    May 26 20:22:52 archw201 kernel: pci 0000:00:16.0: [8086:1c3a] type 00 class 0x078000
    May 26 20:22:52 archw201 kernel: pci 0000:00:16.0: reg 10: [mem 0xfe72a000-0xfe72a00f 64bit]
    May 26 20:22:52 archw201 kernel: pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
    May 26 20:22:52 archw201 kernel: pci 0000:00:16.2: [8086:1c3c] type 00 class 0x010185
    May 26 20:22:52 archw201 kernel: pci 0000:00:16.2: reg 10: [io 0xf0f0-0xf0f7]
    May 26 20:22:52 archw201 kernel: pci 0000:00:16.2: reg 14: [io 0xf0e0-0xf0e3]
    May 26 20:22:52 archw201 kernel: pci 0000:00:16.2: reg 18: [io 0xf0d0-0xf0d7]
    May 26 20:22:52 archw201 kernel: pci 0000:00:16.2: reg 1c: [io 0xf0c0-0xf0c3]
    May 26 20:22:52 archw201 kernel: pci 0000:00:16.2: reg 20: [io 0xf0b0-0xf0bf]
    May 26 20:22:52 archw201 kernel: pci 0000:00:16.3: [8086:1c3d] type 00 class 0x070002
    May 26 20:22:52 archw201 kernel: pci 0000:00:16.3: reg 10: [io 0xf0a0-0xf0a7]
    May 26 20:22:52 archw201 kernel: pci 0000:00:16.3: reg 14: [mem 0xfe729000-0xfe729fff]
    May 26 20:22:52 archw201 kernel: pci 0000:00:19.0: [8086:1502] type 00 class 0x020000
    May 26 20:22:52 archw201 kernel: pci 0000:00:19.0: reg 10: [mem 0xfe700000-0xfe71ffff]
    May 26 20:22:52 archw201 kernel: pci 0000:00:19.0: reg 14: [mem 0xfe728000-0xfe728fff]
    May 26 20:22:52 archw201 kernel: pci 0000:00:19.0: reg 18: [io 0xf040-0xf05f]
    May 26 20:22:52 archw201 kernel: pci 0000:00:19.0: PME# supported from D0 D3hot D3cold
    May 26 20:22:52 archw201 kernel: pci 0000:00:19.0: System wakeup disabled by ACPI
    May 26 20:22:52 archw201 kernel: pci 0000:00:1a.0: [8086:1c2d] type 00 class 0x0c0320
    May 26 20:22:52 archw201 kernel: pci 0000:00:1a.0: reg 10: [mem 0xfe727000-0xfe7273ff]
    May 26 20:22:52 archw201 kernel: pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
    May 26 20:22:52 archw201 kernel: pci 0000:00:1a.0: System wakeup disabled by ACPI
    May 26 20:22:52 archw201 kernel: pci 0000:00:1b.0: [8086:1c20] type 00 class 0x040300
    May 26 20:22:52 archw201 kernel: pci 0000:00:1b.0: reg 10: [mem 0xfe720000-0xfe723fff 64bit]
    May 26 20:22:52 archw201 kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
    May 26 20:22:52 archw201 kernel: pci 0000:00:1c.0: [8086:1c10] type 01 class 0x060400
    May 26 20:22:52 archw201 kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
    May 26 20:22:52 archw201 kernel: pci 0000:00:1c.0: System wakeup disabled by ACPI
    May 26 20:22:52 archw201 kernel: pci 0000:00:1c.4: [8086:1c18] type 01 class 0x060400
    May 26 20:22:52 archw201 kernel: pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
    May 26 20:22:52 archw201 kernel: pci 0000:00:1c.4: System wakeup disabled by ACPI
    May 26 20:22:52 archw201 kernel: pci 0000:00:1c.6: [8086:1c1c] type 01 class 0x060400
    May 26 20:22:52 archw201 kernel: pci 0000:00:1c.6: PME# supported from D0 D3hot D3cold
    May 26 20:22:52 archw201 kernel: pci 0000:00:1c.6: System wakeup disabled by ACPI
    May 26 20:22:52 archw201 kernel: pci 0000:00:1c.7: [8086:1c1e] type 01 class 0x060400
    May 26 20:22:52 archw201 kernel: pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
    May 26 20:22:52 archw201 kernel: pci 0000:00:1c.7: System wakeup disabled by ACPI
    May 26 20:22:52 archw201 kernel: pci 0000:00:1d.0: [8086:1c26] type 00 class 0x0c0320
    May 26 20:22:52 archw201 kernel: pci 0000:00:1d.0: reg 10: [mem 0xfe726000-0xfe7263ff]
    May 26 20:22:52 archw201 kernel: pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
    May 26 20:22:52 archw201 kernel: pci 0000:00:1d.0: System wakeup disabled by ACPI
    May 26 20:22:52 archw201 kernel: pci 0000:00:1e.0: [8086:244e] type 01 class 0x060401
    May 26 20:22:52 archw201 kernel: pci 0000:00:1e.0: System wakeup disabled by ACPI
    May 26 20:22:52 archw201 kernel: pci 0000:00:1f.0: [8086:1c4e] type 00 class 0x060100
    May 26 20:22:52 archw201 kernel: pci 0000:00:1f.2: [8086:1c02] type 00 class 0x010601
    May 26 20:22:52 archw201 kernel: pci 0000:00:1f.2: reg 10: [io 0xf090-0xf097]
    May 26 20:22:52 archw201 kernel: pci 0000:00:1f.2: reg 14: [io 0xf080-0xf083]
    May 26 20:22:52 archw201 kernel: pci 0000:00:1f.2: reg 18: [io 0xf070-0xf077]
    May 26 20:22:52 archw201 kernel: pci 0000:00:1f.2: reg 1c: [io 0xf060-0xf063]
    May 26 20:22:52 archw201 kernel: pci 0000:00:1f.2: reg 20: [io 0xf020-0xf03f]
    May 26 20:22:52 archw201 kernel: pci 0000:00:1f.2: reg 24: [mem 0xfe725000-0xfe7257ff]
    May 26 20:22:52 archw201 kernel: pci 0000:00:1f.2: PME# supported from D3hot
    May 26 20:22:52 archw201 kernel: pci 0000:00:1f.3: [8086:1c22] type 00 class 0x0c0500
    May 26 20:22:52 archw201 kernel: pci 0000:00:1f.3: reg 10: [mem 0xfe724000-0xfe7240ff 64bit]
    May 26 20:22:52 archw201 kernel: pci 0000:00:1f.3: reg 20: [io 0xf000-0xf01f]
    May 26 20:22:52 archw201 kernel: pci 0000:01:00.0: [1002:6779] type 00 class 0x030000
    May 26 20:22:52 archw201 kernel: pci 0000:01:00.0: reg 10: [mem 0xd0000000-0xdfffffff 64bit pref]
    May 26 20:22:52 archw201 kernel: pci 0000:01:00.0: reg 18: [mem 0xfe620000-0xfe63ffff 64bit]
    May 26 20:22:52 archw201 kernel: pci 0000:01:00.0: reg 20: [io 0xe000-0xe0ff]
    May 26 20:22:52 archw201 kernel: pci 0000:01:00.0: reg 30: [mem 0xfe600000-0xfe61ffff pref]
    May 26 20:22:52 archw201 kernel: pci 0000:01:00.0: supports D1 D2
    May 26 20:22:52 archw201 kernel: pci 0000:01:00.1: [1002:aa98] type 00 class 0x040300
    May 26 20:22:52 archw201 kernel: pci 0000:01:00.1: reg 10: [mem 0xfe640000-0xfe643fff 64bit]
    May 26 20:22:52 archw201 kernel: pci 0000:01:00.1: supports D1 D2
    May 26 20:22:52 archw201 kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
    May 26 20:22:52 archw201 kernel: pci 0000:00:01.0: bridge window [io 0xe000-0xefff]
    May 26 20:22:52 archw201 kernel: pci 0000:00:01.0: bridge window [mem 0xfe600000-0xfe6fffff]
    May 26 20:22:52 archw201 kernel: pci 0000:00:01.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
    May 26 20:22:52 archw201 kernel: pci 0000:00:1c.0: PCI bridge to [bus 02]
    May 26 20:22:52 archw201 kernel: pci 0000:00:1c.4: PCI bridge to [bus 03]
    May 26 20:22:52 archw201 kernel: pci 0000:00:1c.6: PCI bridge to [bus 04]
    May 26 20:22:52 archw201 kernel: pci 0000:00:1c.7: PCI bridge to [bus 05]
    May 26 20:22:52 archw201 kernel: pci 0000:00:1e.0: PCI bridge to [bus 06] (subtractive decode)
    May 26 20:22:52 archw201 kernel: pci 0000:00:1e.0: bridge window [io 0x0000-0x03af] (subtractive decode)
    May 26 20:22:52 archw201 kernel: pci 0000:00:1e.0: bridge window [io 0x03e0-0x0cf7] (subtractive decode)
    May 26 20:22:52 archw201 kernel: pci 0000:00:1e.0: bridge window [io 0x03b0-0x03df] (subtractive decode)
    May 26 20:22:52 archw201 kernel: pci 0000:00:1e.0: bridge window [io 0x0d00-0xffff] (subtractive decode)
    May 26 20:22:52 archw201 kernel: pci 0000:00:1e.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
    May 26 20:22:52 archw201 kernel: pci 0000:00:1e.0: bridge window [mem 0x000c0000-0x000dffff] (subtractive decode)
    May 26 20:22:52 archw201 kernel: pci 0000:00:1e.0: bridge window [mem 0xd0000000-0xffffffff] (subtractive decode)
    May 26 20:22:52 archw201 kernel: acpi PNP0A08:00: Requesting ACPI _OSC control (0x1d)
    May 26 20:22:52 archw201 kernel: acpi PNP0A08:00: ACPI _OSC control (0x1d) granted
    May 26 20:22:52 archw201 kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
    May 26 20:22:52 archw201 kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
    May 26 20:22:52 archw201 kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
    May 26 20:22:52 archw201 kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
    May 26 20:22:52 archw201 kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs *3 4 5 6 7 10 11 12 14 15)
    May 26 20:22:52 archw201 kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0
    May 26 20:22:52 archw201 kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 *7 10 11 12 14 15)
    May 26 20:22:52 archw201 kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 *10 11 12 14 15)
    May 26 20:22:52 archw201 kernel: ACPI: Enabled 3 GPEs in block 00 to 3F
    May 26 20:22:52 archw201 kernel: acpi root: \_SB_.PCI0 notify handler is installed
    May 26 20:22:52 archw201 kernel: Found 1 acpi root devices
    May 26 20:22:52 archw201 kernel: ACPI: No dock devices found.
    May 26 20:22:52 archw201 kernel: vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
    May 26 20:22:52 archw201 kernel: vgaarb: loaded
    May 26 20:22:52 archw201 kernel: vgaarb: bridge control possible 0000:01:00.0
    May 26 20:22:52 archw201 kernel: PCI: Using ACPI for IRQ routing
    May 26 20:22:52 archw201 kernel: PCI: pci_cache_line_size set to 64 bytes
    May 26 20:22:52 archw201 kernel: e820: reserve RAM buffer [mem 0xcf3e1000-0xcfffffff]
    May 26 20:22:52 archw201 kernel: e820: reserve RAM buffer [mem 0xcf800000-0xcfffffff]
    May 26 20:22:52 archw201 kernel: e820: reserve RAM buffer [mem 0x12e000000-0x12fffffff]
    May 26 20:22:52 archw201 kernel: NetLabel: Initializing
    May 26 20:22:52 archw201 kernel: NetLabel: domain hash size = 128
    May 26 20:22:52 archw201 kernel: NetLabel: protocols = UNLABELED CIPSOv4
    May 26 20:22:52 archw201 kernel: NetLabel: unlabeled traffic allowed by default
    May 26 20:22:52 archw201 kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
    May 26 20:22:52 archw201 kernel: hpet0: 8 comparators, 64-bit 14.318180 MHz counter
    May 26 20:22:52 archw201 kernel: Switching to clocksource hpet
    May 26 20:22:52 archw201 kernel: pnp: PnP ACPI init
    May 26 20:22:52 archw201 kernel: ACPI: bus type PNP registered
    May 26 20:22:52 archw201 kernel: system 00:00: [mem 0xfed10000-0xfed19fff] has been reserved
    May 26 20:22:52 archw201 kernel: system 00:00: [mem 0xe0000000-0xefffffff] has been reserved
    May 26 20:22:52 archw201 kernel: system 00:00: [mem 0xfed90000-0xfed93fff] has been reserved
    May 26 20:22:52 archw201 kernel: system 00:00: [mem 0xfed20000-0xfed3ffff] has been reserved
    May 26 20:22:52 archw201 kernel: system 00:00: [mem 0xfee00000-0xfee0ffff] has been reserved
    May 26 20:22:52 archw201 kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
    May 26 20:22:52 archw201 kernel: system 00:01: [io 0x0620-0x063f] has been reserved
    May 26 20:22:52 archw201 kernel: system 00:01: [io 0x0610-0x061f] has been reserved
    May 26 20:22:52 archw201 kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
    May 26 20:22:52 archw201 kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0303 PNP030b (active)
    May 26 20:22:52 archw201 kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0f03 PNP0f13 (active)
    May 26 20:22:52 archw201 kernel: pnp 00:04: [dma 0 disabled]
    May 26 20:22:52 archw201 kernel: pnp 00:04: Plug and Play ACPI device, IDs PNP0501 (active)
    May 26 20:22:52 archw201 kernel: pnp 00:05: [dma 4]
    May 26 20:22:52 archw201 kernel: pnp 00:05: Plug and Play ACPI device, IDs PNP0200 (active)
    May 26 20:22:52 archw201 kernel: pnp 00:06: Plug and Play ACPI device, IDs PNP0b00 (active)
    May 26 20:22:52 archw201 kernel: pnp 00:07: Plug and Play ACPI device, IDs PNP0800 (active)
    May 26 20:22:52 archw201 kernel: system 00:08: [io 0x04d0-0x04d1] has been reserved
    May 26 20:22:52 archw201 kernel: system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
    May 26 20:22:52 archw201 kernel: pnp 00:09: Plug and Play ACPI device, IDs PNP0c04 (active)
    May 26 20:22:52 archw201 kernel: pnp 00:0a: Plug and Play ACPI device, IDs IFX0102 PNP0c31 (active)
    May 26 20:22:52 archw201 kernel: system 00:0b: [io 0x0400-0x0453] has been reserved
    May 26 20:22:52 archw201 kernel: system 00:0b: [io 0x0458-0x047f] has been reserved
    May 26 20:22:52 archw201 kernel: system 00:0b: [io 0x1180-0x119f] has been reserved
    May 26 20:22:52 archw201 kernel: system 00:0b: [io 0x0500-0x057f] has been reserved
    May 26 20:22:52 archw201 kernel: system 00:0b: [mem 0xfed1c000-0xfed1ffff] has been reserved
    May 26 20:22:52 archw201 kernel: system 00:0b: [mem 0xfec00000-0xfecfffff] could not be reserved
    May 26 20:22:52 archw201 kernel: system 00:0b: [mem 0xfed08000-0xfed08fff] has been reserved
    May 26 20:22:52 archw201 kernel: system 00:0b: [mem 0xff000000-0xffffffff] has been reserved
    May 26 20:22:52 archw201 kernel: system 00:0b: Plug and Play ACPI device, IDs PNP0c01 (active)
    May 26 20:22:52 archw201 kernel: system 00:0c: [io 0x0454-0x0457] has been reserved
    May 26 20:22:52 archw201 kernel: system 00:0c: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
    May 26 20:22:52 archw201 kernel: pnp 00:0d: Plug and Play ACPI device, IDs PNP0103 (active)
    May 26 20:22:52 archw201 kernel: pnp: PnP ACPI: found 14 devices
    May 26 20:22:52 archw201 kernel: ACPI: bus type PNP unregistered
    May 26 20:22:52 archw201 kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
    May 26 20:22:52 archw201 kernel: pci 0000:00:01.0: bridge window [io 0xe000-0xefff]
    May 26 20:22:52 archw201 kernel: pci 0000:00:01.0: bridge window [mem 0xfe600000-0xfe6fffff]
    May 26 20:22:52 archw201 kernel: pci 0000:00:01.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
    May 26 20:22:52 archw201 kernel: pci 0000:00:1c.0: PCI bridge to [bus 02]
    May 26 20:22:52 archw201 kernel: pci 0000:00:1c.4: PCI bridge to [bus 03]
    May 26 20:22:52 archw201 kernel: pci 0000:00:1c.6: PCI bridge to [bus 04]
    May 26 20:22:52 archw201 kernel: pci 0000:00:1c.7: PCI bridge to [bus 05]
    May 26 20:22:52 archw201 kernel: pci 0000:00:1e.0: PCI bridge to [bus 06]
    May 26 20:22:52 archw201 kernel: pci 0000:00:1e.0: setting latency timer to 64
    May 26 20:22:52 archw201 kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x03af]
    May 26 20:22:52 archw201 kernel: pci_bus 0000:00: resource 5 [io 0x03e0-0x0cf7]
    May 26 20:22:52 archw201 kernel: pci_bus 0000:00: resource 6 [io 0x03b0-0x03df]
    May 26 20:22:52 archw201 kernel: pci_bus 0000:00: resource 7 [io 0x0d00-0xffff]
    May 26 20:22:52 archw201 kernel: pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
    May 26 20:22:52 archw201 kernel: pci_bus 0000:00: resource 9 [mem 0x000c0000-0x000dffff]
    May 26 20:22:52 archw201 kernel: pci_bus 0000:00: resource 10 [mem 0xd0000000-0xffffffff]
    May 26 20:22:52 archw201 kernel: pci_bus 0000:01: resource 0 [io 0xe000-0xefff]
    May 26 20:22:52 archw201 kernel: pci_bus 0000:01: resource 1 [mem 0xfe600000-0xfe6fffff]
    May 26 20:22:52 archw201 kernel: pci_bus 0000:01: resource 2 [mem 0xd0000000-0xdfffffff 64bit pref]
    May 26 20:22:52 archw201 kernel: pci_bus 0000:06: resource 4 [io 0x0000-0x03af]
    May 26 20:22:52 archw201 kernel: pci_bus 0000:06: resource 5 [io 0x03e0-0x0cf7]
    May 26 20:22:52 archw201 kernel: pci_bus 0000:06: resource 6 [io 0x03b0-0x03df]
    May 26 20:22:52 archw201 kernel: pci_bus 0000:06: resource 7 [io 0x0d00-0xffff]
    May 26 20:22:52 archw201 kernel: pci_bus 0000:06: resource 8 [mem 0x000a0000-0x000bffff]
    May 26 20:22:52 archw201 kernel: pci_bus 0000:06: resource 9 [mem 0x000c0000-0x000dffff]
    May 26 20:22:52 archw201 kernel: pci_bus 0000:06: resource 10 [mem 0xd0000000-0xffffffff]
    May 26 20:22:52 archw201 kernel: NET: Registered protocol family 2
    Ma

Maybe you are looking for

  • Checking to see if files exist not working as expected.

    Hey, so I've set up a script that determines the artist playing on iTunes and sets the background image to a preselected picture of them. I want to expand this to allow different pictures of the artists, and after a few attempts, decided to use a tim

  • Im trying to register my Photoshop Elements 11 and it says my email is not valid

    Hi - I bought PSE11 (upgrading from 6!) and installed it successfully. I then got myself an apple ID on this website, using my email - and that was fine. Now I'm trying to register the software (it keeps asking me to do so on load) but it says my ema

  • Library Projects compiled using Flash Builder and ANT have different outputs

    Hi Guys., I am really having hard time to get something work right with RSL projects in Flex 3.2 SDK. Here is my weird problem. I have a library projects which has the following settings in Flash Builder Link Type : External airglobal.swc framework.s

  • PSE 8 Organizer crash

    I can get into the Editor but not the Organizer. I'm not sure if I caused this when I stopped the upload to Shutterfly or what> Please help

  • Changing the clip board size?

    So I have this multipage document I am working on and I needed more pages so I added the artboards I need however then now go beyond the clip board size (see picture below), how do I change that?