[SOLVED] systemd-fsck does checks on every boot

How do I say it to check only after crashes (bad unmounts and so on..) and just mount without checks otherwise?
I use the classic /etc/fstab layout:
/dev/drive/root / ext4 rw,relatime 0 1
/dev/drive/boot /boot ext4 rw,relatime,noexec 0 2
/dev/drive/swap none swap defaults 0 0
/dev/drive/var /var ext4 rw,relatime,nodev,noexec,nosuid 0 2
/dev/drive/home /home ext4 rw,relatime 0 2
Here is some info from systemd's journal:
дек. 08 22:43:20 localhost systemd[1]: Found device /dev/drive/var.
дек. 08 22:43:21 localhost systemd-fsck[124]: /dev/mapper/drive-root: clean, 56204/2621440 files, 523339/10485760 blocks
дек. 08 22:43:21 localhost systemd[1]: Started File System Check on Root Device.
дек. 08 22:43:21 localhost systemd[1]: Starting File System Check on /dev/drive/var...
дек. 08 22:43:21 localhost systemd[1]: Starting Remount Root and Kernel File Systems...
дек. 08 22:43:21 localhost systemd[1]: Found device /dev/drive/swap.
дек. 08 22:43:21 localhost systemd[1]: Activating swap /dev/drive/swap...
дек. 08 22:43:21 localhost systemd[1]: Found device /dev/drive/boot.
дек. 08 22:43:21 localhost systemd[1]: Starting File System Check on /dev/drive/boot...
дек. 08 22:43:21 localhost systemd[1]: Found device /dev/drive/home.
дек. 08 22:43:21 localhost systemd[1]: Starting File System Check on /dev/drive/home...
дек. 08 22:43:21 localhost systemd-fsck[252]: /dev/mapper/drive-var: clean, 2007/262144 files, 463082/1048576 blocks
дек. 08 22:43:22 localhost systemd[1]: Started Remount Root and Kernel File Systems.
дек. 08 22:43:22 localhost systemd[1]: Starting Local File Systems (Pre).
дек. 08 22:43:22 localhost systemd[1]: Reached target Local File Systems (Pre).
дек. 08 22:43:22 localhost systemd[1]: Mounting /var...
дек. 08 22:43:22 localhost systemd-fsck[257]: /dev/mapper/drive-boot: clean, 313/65536 files, 33914/262144 blocks
дек. 08 22:43:22 localhost systemd[1]: Mounted /var.
дек. 08 22:43:22 localhost systemd-fsck[262]: /dev/mapper/drive-home: clean, 5080/16375808 files, 2332630/65492992 blocks
дек. 08 22:43:22 localhost systemd[1]: Started File System Check on /dev/drive/boot.
дек. 08 22:43:22 localhost systemd[1]: Mounting /boot...
дек. 08 22:43:22 localhost systemd[1]: Started File System Check on /dev/drive/home.
дек. 08 22:43:22 localhost systemd[1]: Mounting /home...
дек. 08 22:43:22 localhost systemd[1]: Mounted /boot.
дек. 08 22:43:23 localhost systemd[1]: Mounted /home.
дек. 08 22:43:23 localhost systemd[1]: Starting Local File Systems.
дек. 08 22:43:23 localhost systemd[1]: Reached target Local File Systems.
These filesystem checks seem to add huge delay to boot time. But I don't want this delay!
Last edited by eruditorum (2012-12-10 19:26:54)

falconindy wrote:These are the same checks that have always occurred.
But I want to remove them!
falconindy wrote:Notice that /home is mounted within the same second timestamp that it's fsck'd. Same goes for /boot, and /var is probably under a second as well. If you're seeing delays, go look elsewhere.
I think filesystem checks add delays (about one second for each logical volume or so), also as you know systemd is doing everything in parallel it can at the given moment of time, for example I can say you that water has already boiled, while it is still going to boil but you don't know it:
дек. 08 22:43:19 localhost systemd[1]: Starting File System Check on Root Device...
дек. 08 22:43:21 localhost systemd-fsck[124]: /dev/mapper/drive-root: clean, 56204/2621440 files, 523339/10485760 blocks
дек. 08 22:43:21 localhost systemd[1]: Started File System Check on Root Device.
дек. 08 22:43:21 localhost systemd[1]: Starting Remount Root and Kernel File Systems...
/var:
дек. 08 22:43:20 localhost systemd[1]: Found device /dev/drive/var.
дек. 08 22:43:21 localhost systemd[1]: Starting File System Check on /dev/drive/var...
дек. 08 22:43:21 localhost systemd-fsck[252]: /dev/mapper/drive-var: clean, 2007/262144 files, 463082/1048576 blocks
дек. 08 22:43:21 localhost systemd[1]: Started File System Check on /dev/drive/var.
дек. 08 22:43:22 localhost systemd[1]: Mounting /var...
дек. 08 22:43:22 localhost systemd[1]: Mounted /var.
/boot:
дек. 08 22:43:21 localhost systemd[1]: Found device /dev/drive/boot.
дек. 08 22:43:21 localhost systemd[1]: Starting File System Check on /dev/drive/boot...
дек. 08 22:43:22 localhost systemd-fsck[257]: /dev/mapper/drive-boot: clean, 313/65536 files, 33914/262144 blocks
дек. 08 22:43:22 localhost systemd[1]: Started File System Check on /dev/drive/boot.
дек. 08 22:43:22 localhost systemd[1]: Mounting /boot...
дек. 08 22:43:22 localhost systemd[1]: Mounted /boot.
/home:
дек. 08 22:43:21 localhost systemd[1]: Found device /dev/drive/home.
дек. 08 22:43:21 localhost systemd[1]: Starting File System Check on /dev/drive/home...
дек. 08 22:43:22 localhost systemd-fsck[262]: /dev/mapper/drive-home: clean, 5080/16375808 files, 2332630/65492992 blocks
дек. 08 22:43:22 localhost systemd[1]: Started File System Check on /dev/drive/home.
дек. 08 22:43:22 localhost systemd[1]: Mounting /home...
дек. 08 22:43:23 localhost systemd[1]: Mounted /home.
Last edited by eruditorum (2012-12-09 13:20:15)

Similar Messages

  • [SOLVED] systemd-fsck prolongs boot time considerably

    Hi folks, I've searched but come up blank on this one...
    I've just migrated fully to systemd and all's working well apart from my boot hanging for around 16 seconds on fsck. Disabling the checks via the final column of fstab reduces my boot to under 9 seconds, which is roughly what it was with initscripts. Boot drive's an SSD, all other partitions on 2 SATA HDDs.
    Here are the relevant parts of fstab
    # /dev/sda3 - Backup
    # ========= ------
    UUID=7e23c7f4-acf6-477c-9705-15ae8870181e /media/Backup ext4 defaults 0 2
    # /dev/sdb2 - ROOT (+/home)
    # ========= ------------
    UUID=ee99e089-a642-41c8-b1f4-5dc80307d438 / ext4 defaults,noatime,discard 0 1
    # /dev/sdc1 - Data
    # ========= ----
    UUID=66c7a8dd-8d92-4353-a4eb-1da425449322 /media/Data ext4 defaults 0 2
    # /dev/sdc2 - Scratch
    # ========= -------
    UUID=a8ca4753-ccca-4360-b702-8c12004bf8f8 /media/Scratch ext4 defaults,noatime 0 2
    # /dev/sdc4 - bootISOs
    # ========= --------
    UUID=eea21a23-b3fa-479d-8a62-2502f4f9edfc /media/bootISOs ext4 defaults,noatime 0 2
    I do have /var on the "Data" partition and a few other relocations...
    /media/Data/var /var none bind 0 0
    /media/Data/logs /home/paul/.logs none bind 0 0
    tmpfs /home/paul/.thumbnails tmpfs nodev,nosuid,noatime 0 0
    tmpfs /home/paul/.Skype/Logs tmpfs nodev,nosuid,noatime 0 0
    tmpfs /media/Data/wine/drive_c/windows/temp tmpfs nodev,nosuid,noatime 0 0
    Without fsck
    $ systemd-analyze
    Startup finished in 1280ms (kernel) + 2220ms (initramfs) + 5112ms (userspace) = 8614ms
    With fsck (typical)
    $ systemd-analyze
    Startup finished in 1276ms (kernel) + 3224ms (initramfs) + 20327ms (userspace) = 24829ms
    Any ideas as to the slowdown or is this to be expected with this many partitions?
    Thanks.
    Last edited by fabertawe (2012-09-06 17:48:57)

    WorMzy wrote:You can add "noauto,x-systemd.automount" to the options of non-essential partitions. That may speed up your boot time.
    Sorry, I should have mentioned I already tried this with the "Data" partition and just got a permanent hang in the boot sequence.
    Edit: I've had 2 boots where it's not had the delay but I've no idea why, nothing was changed.
    Edit2: Seems I was too quick to dismiss "noauto,x-systemd.automount"... I've applied it to all partitions except "Data" (and root, obviously) and now I'm consistently getting boot times under 9 seconds. Marking this thread as solved. Thanks to all who contributed
    Last edited by fabertawe (2012-09-06 17:45:48)

  • [SOLVED] systemd: What does "status=226/NAMESPACE" mean?

    /var/log is on tmpfs here, and Apache refuses to start without /var/log/httpd already being created, so I am trying to create that folder from http.service.  I added the line:
    ExecStartPre=/usr/bin/mkdir -p /var/log/httpd
    Now I am getting a "status=226/NAMESPACE" error.  I am confused about what this error means.  I do know that if I comment out "PrivateTmp=true" from the service file, the error goes away, but I suppose doing that defeats some security measure.
    httpd.service - Apache Web Server
    Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled)
    Active: failed (Result: exit-code) since Sun 2013-01-27 12:27:07 EST; 8s ago
    Process: 671 ExecStartPre=/usr/bin/mkdir -p /var/log/httpd (code=exited, status=226/NAMESPACE)
    Main PID: 644 (code=exited, status=0/SUCCESS)
    CGroup: name=systemd:/system/httpd.service
    Jan 27 12:27:07 satellite systemd[1]: Starting Apache Web Server...
    Jan 27 12:27:07 satellite systemd[1]: httpd.service: control process exited, code=exited status=226
    Jan 27 12:27:07 satellite systemd[1]: Failed to start Apache Web Server.
    Jan 27 12:27:07 satellite systemd[1]: Unit httpd.service entered failed state
    Is there another way to create /var/log/httpd without disabling PrivateTmp?
    Last edited by jlindgren (2013-01-27 20:02:25)

    falconindy wrote:Do you also foolishly have /var/tmp symlinked to /tmp ?
    I did.  When I mount /var/tmp separately, the error disappears.  Thanks.

  • [SOLVED] systemd : services failing to start on boot

    I have removed sysvinit completely as per the systemd wiki pages.
    I don't usually re-boot very often so I'm not sure exactly when the problem started.
    I only noticed this problem about 4 or 5 days ago.
    But now whenever I reboot my machine 2 services fail consistently.
    adsl.service
    colord.service
    They both start flawlessly once I can log in at a console.
    I'm using kde and in the last couple of days, while trying to fix my problem, the kdm service has failed to start a couple of times too - saying there is no X server.
    Before switching to systemd I never had any of these problems using the old rc.conf method. My DAEMONS array had the adsl service start after the network service.
    I need some help and advice to find out what is causing the problem and how to fix it.
    Last edited by bhrgunatha (2012-10-25 05:44:22)

    Thanks. That seems plausible. So I've been snooping at the journal.
    journalctl -ab
    Oct 25 17:06:13 starch systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
    Oct 25 17:06:14 starch systemd[1]: Started Recreate Volatile Files and Directories.
    Oct 25 17:06:14 starch systemd[1]: Starting System Initialization.
    Oct 25 17:06:14 starch systemd[1]: Reached target System Initialization.
    Oct 25 17:06:14 starch systemd[1]: Starting CUPS Printing Service Sockets.
    Oct 25 17:06:14 starch systemd[1]: Listening on CUPS Printing Service Sockets.
    Oct 25 17:06:14 starch systemd[1]: Starting Console System Startup Logging...
    Oct 25 17:06:14 starch systemd[1]: Starting Restore Sound Card State...
    Oct 25 17:06:14 starch systemd[1]: Starting CUPS Printer Service Spool.
    Oct 25 17:06:14 starch systemd[1]: Started CUPS Printer Service Spool.
    Oct 25 17:06:14 starch systemd[1]: Starting D-Bus System Message Bus Socket.
    Oct 25 17:06:16 starch ntpd[381]: ntpd [email protected] Tue Aug 21 15:06:24 UTC 2012 (1)
    Oct 25 17:06:16 starch ntpd[413]: proto: precision = 0.156 usec
    Oct 25 17:06:17 starch ntpd[413]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
    Oct 25 17:06:17 starch ntpd[413]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
    Oct 25 17:06:18 starch ntpd[413]: Listen and drop on 1 v6wildcard :: UDP 123
    Oct 25 17:06:18 starch ntpd[413]: Listen normally on 2 lo 127.0.0.1 UDP 123
    Oct 25 17:06:18 starch ntpd[413]: Listen normally on 3 lo ::1 UDP 123
    Oct 25 17:06:18 starch ntpd[413]: peers refreshed
    Oct 25 17:06:18 starch ntpd[413]: Listening on routing socket on fd #20 for interface updates
    Oct 25 17:06:18 starch dbus[384]: [system] Activating systemd to hand-off: service name='org.freedesktop.ColorManager' unit='colord.service'
    Oct 25 17:06:18 starch dbus[384]: [system] Successfully activated service 'org.freedesktop.systemd1'
    Oct 25 17:07:03 starch dbus[384]: [system] Successfully activated service 'org.freedesktop.ColorManager'
    Oct 25 17:07:03 starch dbus[384]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service'
    Oct 25 17:07:03 starch dbus[384]: [system] Successfully activated service 'org.freedesktop.ColorManager'
    Oct 25 17:07:04 starch kernel: r8169 0000:02:00.0: eth0: link down
    Oct 25 17:07:03 starch systemd[1]: Starting Manage, Install and Generate Color Profiles...
    Oct 25 17:07:03 starch systemd[1]: Started Manage, Install and Generate Color Profiles.
    Oct 25 17:07:03 starch systemd[1]: colord.service: main process exited, code=killed, status=6
    Oct 25 17:07:03 starch systemd[1]: Unit colord.service entered failed state.
    Oct 25 17:07:04 starch kernel: r8169 0000:02:00.0: eth0: link down
    Oct 25 17:07:04 starch kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
    Oct 25 17:07:04 starch kernel: PPP generic driver version 2.4.2
    Oct 25 17:07:04 starch cupsd[380]: Unknown directive DefaultAuthType on line 26.
    Oct 25 17:07:04 starch kernel: r8169 0000:02:00.0: eth0: link up
    Oct 25 17:07:04 starch kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    Oct 25 17:07:04 starch pppoe-start[382]: TIMED OUT
    Oct 25 17:07:04 starch kernel: NET: Registered protocol family 24
    Oct 25 17:07:04 starch pppoe-start[382]: /usr/sbin/pppoe-start: line 193: 394 Terminated $CONNECT "$@" > /dev/null 2>&1
    That seems to confirm your theory.
    eth0 link is not up when attempting to start colord and adsl
    So the $64,000 question:
    How do I defer them until eth0 is ready?
    Or how can I force the eth0 link to be up before colord or adsl try to use it?
    Last edited by bhrgunatha (2012-10-25 01:33:36)

  • [Solved] Network does not starts on every boot

    Yet another problem on fresh arch...
    Network service does not starts every time I booting my headless. For every 10 attempts service starts 5 or 6 times only.
    Ping says: Networking unreachable.
    systemctl status network:
    network.service - Static IP Connectivity
    Loaded: loaded (/etc/systemd/system/network.service; enabled)
    Active: inactive (dead)
    'systemctl start network' just hangs. In order to get it start I have to reboot the box hoping next boot service will start.
    I am not using dhcp (if it makes a sence). Service was configured as described in wiki for static IP assigning.
    The config itself:
    [Unit]
    Description=Static IP Connectivity
    Wants=network.target
    Before=network.target
    BindsTo=sys-subsystem-net-devices-enp4s1.device
    After=sys-subsystem-net-devices-enp4s1.device
    [Service]
    Type=oneshot
    RemainAfterExit=yes
    ExecStart=/sbin/ip link set dev enp4s1 up
    ExecStart=/sbin/ip addr add 192.168.1.5/24 dev enp4s1
    ExecStart=/sbin/ip route add default via 192.168.1.1
    ExecStop=/sbin/ip addr flush dev enp4s1
    ExecStop=/sbin/ip link set dev enp4s1 down
    [Install]
    WantedBy=multi-user.target
    What's wrong?
    Thanks in advance for any help.
    Last edited by chord (2013-06-03 17:04:55)

    Thaks for your reply.
    I got this interface name from ip addr,  how it should be named if 'enp4s1' is wrong?
    journalctl is here: http://bpaste.net/show/104083/
    I found only one string realted to this device name:
    Jun 03 15:18:23 localhost systemd[1]: Expecting device sys-subsystem-net-devices-enp4s1.device...
    Is there some other logs where it can be checked?

  • Systemd-fsck boot message

    systemd-fsck show message when boot evertime. What does meaning? And how to hidding them.
    systemd-fsck[145]: /dev/sda4: clean, 112977/9296096 files, 185427/21217024 blocks
    systemd-fsck[151]: /dev/sda1: clean, 345/26104 files, 34083/104388 blocks (check after next mount)
    edit:
    Sorry, I loss something. Full message is:
    /dev/sda3: clean, 131838/991232 files, 1193255/3933482 blocks
    systemd-fsck[145]: /dev/sda4: clean, 2977/296096 files, 85427/1217024 blocks
    systemd-fsck[151]: /dev/sda1: clean, 345/26104 files, 34083/104388 blocks (check after next mount)
    my lsblk:
    NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
    sda 8:0 0 20G 0 disk
    ├─sda1 8:1 0 102M 0 part /boot
    ├─sda2 8:2 0 258.9M 0 part [SWAP]
    ├─sda3 8:3 0 15G 0 part /
    └─sda4 8:4 0 4.7G 0 part /home
    Last edited by eshizhan (2012-10-22 04:52:13)

    fsck stands for "file system check" [1].  systemd will check all of your filesystems every time you boot [2]. 
    systemd-fsck[145]: /dev/sda4: clean, 2977/296096 files, 85427/1217024 blocks
    systemd-fsck[151]: /dev/sda1: clean, 345/26104 files, 34083/104388 blocks (check after next mount)
    These messages mean that there are no problems with your filesystems and they are "clean".  If there ever was a problem with any of your filesystems, these messages are how fsck will let you know so I don't think you want to hide them.
    [1] https://wiki.archlinux.org/index.php/Fsck
    [2] https://wiki.archlinux.org/index.php/Systemd#Automount

  • [SOLVED] "Filesystem check failed" during boot process

    I was using XFCE on my netbook recently and clicked "shutdown".  It logged out to the command prompt and nothing happened.  Assuming that I'd clicked "logout" by mistake, I typed "pacman -Syu" to run an update...  And moments later it suddenly started the shutdown process.
    Now, whenever I boot up, I see the message below.  I tried booting from a GParted CD to check the filesystems for errors, but none were detected.
    Can anyone suggest what I might need to do to fix the problem?
    rootfs: clean, 11026/246512 files, 477083/984576 blocks
    home: clean, 4386/527280 files, 237183/2105344 blocks
    /dev/sdb2 is mounted. e2fsck: Cannot continue, aborting.
    ************* FILESYSTEM CHECK FAILED ************
    * Please repair manually and reboot. Note that the root
    * file system is currently mounted read-only. To remount
    * it read-write type: mount -n -o remount,rw /
    * when you exit the maintenance shell the system will
    * reboot automatically.
    Give root password for maintenance
    (or type Control-D to continue):
    Last edited by esuhl (2012-03-27 01:20:07)

    Thank you all for your replies :-)
    hadrons123 wrote:What happens when you do try the suggestion given by it?
    I don't exactly know how I should "repair manually"...  I thought a filesystem check in GParted would have been enough...
    lijpbasin wrote:You can boot the system using a archlinux live cd, and run fsck manually on every linux partition in the old system with options.
    DON'T mount any of the filesystems before running fsck, or your data will probably be lost. If you want to check the partition information first, run fdisk -l with root privileges.
    Thanks.  I tried booting from an ArchBang live CD last night and ran "e2fsck -pcv" on each partition.  The check completed, but the problem persists...  I just tried again using "fsck" as you suggested and got the following output (but the machine still fails to boot with the same error as before):
    fsck from util-linux 2.20.1
    e2fsck 1.41.14 (22-Dec-2010)
    usr was not cleanly unmounted, check forced.
    Pass 1: Checking inodes, blocks, and sizes
    Pass 2: Checking directory structure
    Pass 3: Checking directory connectivity
    Pass 4: Checking reference counts
    Pass 5: Checking group summary information
    usr: 115811/458752 files (1.7% non-contiguous), 783161/1834496 blocks
    Gcool wrote:
    /dev/sdb2 is mounted. e2fsck: Cannot continue, aborting.
    As mentioned already, the reason it's failing is because the /dev/sdb2 partition is mounted before it can be fsck'd. What is this partition exactly (which filesystem, what's on it, mountpoint,...)?
    I'm not overly familiar with the Linux boot process, but why would it suddenly be mounting this partition before fsck-ing it?  Even if it was mounted when the netbook shutdown, surely the boot process starts with all partitions unmounted...?  Anyway, the partition details from /etc/fstab are below.
    <file system> <dir> <type> <options> <dump> <pass>
    tmpfs /tmp tmpfs nodev,nosuid 0 0
    /dev/sda1 / ext2 defaults,noatime 0 1
    /dev/sdb1 /home ext2 defaults,noatime,user_xattr 0 1
    /dev/sdb2 /usr ext2 defaults,noatime 0 1
    I'm (now) aware that mounting /usr as a separate partition is a bad idea and (having read the "Error when booting with the new initscripts" thread), I have told pacman to ignore updates to the initscripts package (until I figure out how best to work round or fix that issue).
    Shark wrote:Write umount /dev/sdb2 in konsole or unmount partition in gparted by right click on problematic partition and click unmount. Than proced.
    If I type "umount /dev/sdb2" at the prompt, I get the following error:
    umount: /usr: device is busy.
    (In some cases useful info about processes that use
    the device is found by lsof(8) or fuser(1))
    I tried "umount -l /dev/sdb2" to unmount when the device becomes free... but it never does.
    I also booted into GParted, but there is no option to "unmount" /dev/sdb2.  There is a "mount" option in the menu, but it is greyed out.  If I open a terminal window from the GParted Live environment and type "sudo umount /dev/sdb2" I get the following message:
    umount: /dev/sdb2: not mounted
    DSpider wrote:Are you mounting the root drive with "ro" (read only) in fstab?
    No (as shown above).  I don't *think* I've messed anything up with fstab or any other config files -- everything was working perfectly till the netbook shutdown whilst pacman was running.

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

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

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

  • Filesystem check failed while booting [SOLVED]

    I tried to get some help from my previous post but got no answers, so I'll summarize in hope of getting an answer:
    I've installed linux before windows because I had this operating system before. But, when I've partitioned I've made a NTFS type 83 for windows, cause I know I'd install it later on.
    Now, I've restored my bootloader (grub) but when I try to boot my arch linux copy, a message tells me that my partition sda2 which is my Windows one, isn't clean or corrupt.
    all my linux partition are clean, but my NTFS windows partition make me unable to boot on my linux OS with this error msg:
    fsck.ext4: Bad magic number in super-block while trying to open /dev/sda2
    /dev/sda2:
    The superblock could not be read or does not describe a correct ext filesystem. If the devine is valid and it really contains an ext2 filesystem (and not swao or ufs or simething else), then the superblock is corrupt, and you might try running e2fsck with an alternate superbloc:
    e2fsck -b 8193 <device>
    Next I can do is entering the root psw and use the command line, I really need help to restore my linux partition without formating anything, please.
    My guess is that linux doesn't reorganize the partition as it is NTFS and doesn't boot for this reason, but didn't find how to fix it over internet yet, some help would be really appreciated.
    Last edited by Mazh (2011-06-10 20:30:39)

    My partition layout is:
    fdisk -l output:
    /dev/sda1 ID (5) extended (don't know what's that didn't think I've made that myself, maybe coming from windows when I installed the NTFS partition)
    /dev/sda2 * HPFS/NTFS/exFAT ID (7) (strange cause I had set 87 but well, windows is working correctly it seems)
    /dev/sda3 ID (83) linux
    /dev/sda5 ID (83) linux
    /dev/sda6 ID (83) linux
    /dev/sda7 ID (83) linux
    /dev/sda8 * ID (83) linux
    yep, it's actually strange that my fsck.ext4 check my sda2 partition NTFS...
    cat /etc/fstab:
    /dev/sda2 /home ext4 defaults 0 1
    /dev/sda5 swap defaults 0 0
    /dev/sda6 /var ext4 defaults 0 1
    /dev/sda7 /usr ext4 defaults 0 1
    /dev/sda8 / ext4 defaults 0 1
    menu.lst
    linux grub
    /dev/sd0 (fd0)
    /dev/sda (hd0)
    /dev/sdb2 (hd1,1)
    /dev/sda3 (hd0,2)
    title arch linux
    root (hd0,7)
    kernel /bootvmlinuz26 root=/dev/sda8 ro
    initrd /boot/kernel26.img
    the arch fallback (same)
    title Windows xp lite sp3
    rootnoverify (hd0,1)
    makeactive
    chainloader +1
    I really have to write by hands, so if you wants more info tell me and I'll write more.
    it's strange, could you explain me what does mean hd1 or hd0? isn't the 1st and second hard drive? and the second array the partition? cause if so, i've only 1 drive. But I'm probably not correct. Hope you get enough info to get me out of this problem!
    And no, I'm not using UUIDs, thx for your suggestion!

  • [Solved -sorta] systemd-fsck []: fsck: /sbin/fsck.ext4: execute failed

    Greetings.
    I am getting the following on boot:
    Starting Version 218
    A password is required to access the MyStorage volume:
    Enter passphrase for /dev/sda3
    /dev/mapper/MyStorage-rootvol: clean, 210151/983040 files, 2284613/3932160 block
    [ 78.084720] systemd-fsck [280]: fsck: /sbin/fsck.ext4: execute failed: Exec format error
    [ 78.085215] systemd-fsck [287]: fsck: /sbin/fsck.ext2: execute failed: Exec format error
    I then end up at a login prompt but if I try to login, I get “Login incorrect”. Sometimes Getty will stop and restart on tty1. Then I get returned to the login prompt.
    This came about after upgrading with Pacman (which included “upgraded e2fsprogs (1.42.12-1 -> 1.42.12-2)”) a few days ago. Pacman completed successfully but on reboot the system froze forcing a hard reset.
    I've booted to a USB and run fsck on the boot partition (the only ext2 partition). Ditto on the root and home volumes. All fine. I've also mounted all three and can access the data.
    I would have thought it was something to do with the e2fs upgrade but it obviously scanned the root volume fine and I haven't been able to find any similar reports online.
    I've searched online for ideas and I've also searched for logs which might give me some indication of what the cause is but at this point, I've reached my limits.
    I'd just nuke the data and start again but I really want to understand what happened here.
    Any thoughts on what caused this or suggestions on how to proceed?
    Thank you.
    Stephen
    Last edited by FixedWing (2015-03-16 01:40:20)

    Head_on_a_Stick wrote:
    https://wiki.archlinux.org/index.php/Pa … ond_repair
    However, it may be simplest to just re-install in your case -- it depends whether you want to use the troubleshooting & repairing as a learning process or if you just want your system up & running again ASAP...
    All fixed and working just like nothing happened.
    I did use the advice at the referred link plus a few others on archlinux.org and elsewhere. Yes, an absolutely wonderful learning experience!
    I manually reinstalled e2fsprogs. That got Pacman working again and I was able to boot into the system. Then I used Pacman to reinstall e2fsprogs properly plus the other seven packages which were also installed during the same Pacman session despite their being corrupted.
    What I really don't get is how Pacman could accept a package with 0 bytes and install it? How could such a package possible pass the security check? When I reinstalled the packages, Pacman of course refused to install the corrupt packages in the cache and deleted them. So why didn't that happen initially? I can only think that a corrupt file in that process terminated prematurely and that Pacman wasn't robust enough to detect this so simply continued on, now skipping the scans and installing the corrupt packages. So just to be sure it wasn't a corrupt file in Pacman itself, I also forced a reinstall of that package as well. I've upgraded packages since without issue so I have to assume that whatever the issue was is now gone.
    Anyway, thanx for the help!
    Stephen

  • Arch boot stops on systemd-fsck

    Today I upgraded my packages then I replaced catalyst package with catalyst-total after reboot the booting process stops on this line
    Systemd-fsck[362]: /dev/sda5: clean etc
    The sda5 is my home drive the boot stops after this line
    I pressed alt+f2 to switch in CLI mode then I removed catalyst-total and installed catalyst but the booting process still stops Even when I run startx in CLI mode it gives
    Unable to connect x server
    The xorg log file error is
    DRM report mode setting isn't supported
    Unload module radeon
    Devices detected but none match those in config file

    Not using catalyst myself, so I'm not sure about this. But to me it looks like a conflict w/ either the radeon module or KMS. The wiki has information about this: https://wiki.archlinux.org/index.php/AM … le_at_boot
    See "disable KMS" and "blacklist radeon", have you done these? Edit: Maybe recheck...
    Regards
    Edit2: Also maybe check whether something else is failing, either remove "quiet" from kernel parameters or check via systemctl (see systemd wiki for more information).
    Last edited by rebootl (2014-05-19 22:41:15)

  • Boot is taking forever (systemd-fsck?)

    Im sorry for the bad topic.
    When I boot Arch it stops and shows me this message for about 5 minutes or so (It feels like forever):
    /dev/sda1: clean, 113567/640848 files, 662474/2561272 blocks
    [ 1.582745] kvm: disabled by bios
    systemd-fsck[242]: /dev/sda2: clean, 90976/640848 files, 505908/2558464 blocks
    I dual boot with Windows and I reboot my computer on a daily basis (Im a gamer) so its driving me crazy.
    I have googled it and read a bunch of topics for the past three days now.. Whats wrong?

    Hund wrote:
    Bah.. Whats up with the systemd thingy anyway? Whats the benefits with it? So far Ive just seen a bunch of bugs. Arch used to work flawless for me, but ever since the switch to systemd it all went south. Boot hangs, shutdown hangs, no network at boot and autmounting my Samba share doesnt work.. Yay!
    Edit: Atleast I solved the network at boot a few days ago. But I have no idea how I did it tbh.. Arch used to be so simple! But now with this systemd piece of shit? Its a mess.
    The experience of most people is that sysytemd has introduced benefits; most of the issues that you are describing are probably fixable by some simple configuration changes.
    In any event, we have grown rather tired of the petulant "systemd is a piece of shit"-type rants that a minority feel compelled to vent; please don't bother. If you don't like it, install something else.
    FWIW: anyone who starts a sentence about a rolling release with a fond nostalgia for the past is clearly deluding themselves; change is at the core of Arch, deal with it.

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

  • [solved] systemd services not starting at boot (or at all)

    On my router, some systemd services fail to start at boot.
    The services are :
    adsl (pppoe connetction on the wan interface)
    shorewall (funny again for a router)
    logind (brings up only tty1, and not the others with a 'timeout' error)
    adsl starts fine manually after booting up
    the others don't work, I have to launch shorewall with the old sysvinit rc script (and it works)
    I really don't know, what happened to logind...
    Last edited by scar (2012-11-30 10:20:44)

    cups: avahi client failed
    adsl: timeout (ppp0 running on eth0, the service did not found eth0)
    shorewall: did not work by the systemctl command, only with the old rc script
    I'm not sure if there was an error with logind, but I've had only tty1, not all the others (I have not touched /etc/inittab)
    since this was a very old install (but up to date), I've decided to reinstall the whole thing,
    Everything works
    (But reinstalling does not solve any problem, it erases the problems...)
    Last edited by scar (2012-11-30 10:21:20)

  • [SOLVED] How to cancel systemd-fsck during reboot after power failure.

    Hello
    If power fails (or if I, for any reason, force a physical shutdown ) on my computer, it will display during boot :
    systemd-fsck[171] : arch_data was not cleanly unmounted, check forced
    And then hangs for a long time (10 minutes ) while checking arch_home partition, wich is a 1T ext4 partition.
    then finish the boot.
    Sometimes i want this behavior, but i may need to have my computer up and running as fast as possible, and i don't seem to be able to cancel this fsck.
    Ctrl+C, or escape have no effect.
    How to allow cancelation of system-fsck for this boot, postponing it for the next boot ?
    my fstab :
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    # UUID=cfdf8739-d512-4d99-9893-437a6a3c9bf4 LABEL=Arch root
    /dev/sda12 / ext4 rw,relatime,data=ordered 0 2
    # UUID=98b01aa3-0f7f-4777-a941-8e676a68adce LABEL=Arch boot
    /dev/sda11 /boot ext2 rw,relatime 0 2
    # UUID=8909c168-5f1e-4ae7-974c-3c681237af7a LABEL=Arch var
    /dev/sda13 /var ext4 rw,relatime,data=ordered 0 2
    # UUID=a13efc24-cf66-44d0-b26c-5bb5260627a0 LABEL=Arch tmp
    /dev/sda14 /tmp ext4 rw,relatime,data=ordered 0 2
    # UUID=779aeb69-9360-4df0-af84-da385b7117d1 LABEL=Arch home
    /dev/sdb4 /home ext4 rw,relatime,data=ordered 0 2
    /dev/sdb5 /home/glow/data ext4 rw,relatime,data=ordered 0 2
    Last edited by GloW_on_dub (2013-12-07 16:00:06)

    Maybe you can add a menu item to the grub boot menu so you can pick it from the menu instead of editing the grub line by hand?
    I'm using syslinux, but I can have menu items that only differ in e.g. 'quiet' parameter:
    APPEND root=/dev/sda3 rw init=/usr/lib/systemd/systemd quiet
    APPEND root=/dev/sda3 rw init=/usr/lib/systemd/systemd
    Everything else is the same.

Maybe you are looking for

  • How do I delete OS X Mountain lion off my macbook. I downloaded the app and I ABSOLUTLEY hate it.

    Hi I would like to know how to properly uninstall the app OS X Mountain lion from my computer. Ever since my computer freezes, its very slow. Now I wish i would have never spent the money on this software and I do not like the apps that it comes with

  • Lower than expected speed

    Hi When we signed up to BT a few months ago our estimated speed was 3.5mbps which is what we have been getting, however checking more recently it says we should get 11mbps, however we haven't had any increase in speed. Modem info: Modulation: ADSL2 P

  • Slideshow timing to music

    I have a 378 pic slideshow with 4 iTunes set in a custom playlist with random transitions and asked to time to the music. At the 378th slide the last tune is not done, and continues on for a couple of minutes. I've done this before with other pics an

  • Gateway and database in a different oracle_home

    Hi:   my env : rhel5.8  oracle10G x86_64   the gateways 's version is  oracle11g   so I install the gateway into  another path   How to I configure the listener?   I mean which listenr.ora should I configure . [oracle@server1 bin]$ pwd /opt/app/produ

  • Integration with cfolders and cprojects

    Dear Experts, Provide me cookbook for integration of cfolders and cprojects through KM.OR can anyone guide me about how we can do ? Rewarded for the answer. Thanks