[SOLVED] systemd boot fails - Removable on fstab
Just converted to the dark (systemd) side.
Very straight forward, simple and easy enough.
I have one problem with boot process.
I have three usb devices that i use frequently, below is my fstab
# Removable Media
UUID=6e4bc1aa-3414-48b9-9598-5eedfaadbe2b /media/FreeAgent1 ext4 defaults,user 0 0
UUID=14219291-0703-45b6-95db-976c5b7c3b7b /media/FreeAgent2 ext4 defaults,user 0 0
UUID=0590bbe0-d098-4f81-a9c7-c72654aa54a5 /media/Sandisk ext4 defaults,user 0 0
USB devices at the moment arent on the pc.
With init process, everything was fine.
Boot process gave me prompt.
With systemd, my archlinux box doesnt boot (at all)
http://ebalaskas.gr/img/systemd_removeable.png
Reading https://bbs.archlinux.org/viewtopic.php?id=146982 & http://lists.freedesktop.org/archives/s … 06292.html
i get the feeling that perhaps is a bug.
But i am not sure.
The emergency mode (^D) doesnt work either - keyboard seemed dead.
Used old transitional init=/bin/sh to comment out the removable devices from my fstab
-- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr] --
Last edited by ebal (2012-08-24 06:43:52)
ebal wrote:
Nothing is needed to be done to fstab file !
it shouldnt
it mustnt
with the heck i must edit my fstab cause systemd doesnt have a proper function to timeout when there are devices that are not present at boot time !!!
That dont even make sense.
Thank you all for your answers but PLZ ... try to focus on the actual problem that systemd is failing to boot and not to fstab !
btw from my first post i 've already mentioned that i commented out these entries just to boot with systemd.
what is the problem with using nofail or noauto,x-systemd.automount? systemd does the right thing here, it tries to mount the device on boot and waits for it - it's just that the timeout is very long (afaik 90 seconds).
the only reason this worked with initscripts is that afaik initscripts just tries to mount the device and won't wait for it if it isn't there, but instead just fails immediately. While this worked, it was still the wrong approach. You should have added noauto or nofail in the first place.
Similar Messages
-
[SOLVED] systemd --user: "Failed to open private bus connection:"
EDIT: The solution was to set DBUS_SESSION_BUS_ADDRESS, as suggested by gtmanfred in irc. By putting the following before executing systemd --user, the error vanished:
export DBUS_SESSION_BUS_ADDRESS=/run/user/$(id -u)/dbus/user_bus_socket
===================
Original problem:
Everything on my box appears to be working ok, but I'm getting this error consistently in tty1 and at the top of journalctl (as user) whenever I start systemd --user:
systemd[3975]: Failed to open private bus connection: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
I roughly have my system setup per this wiki section https://wiki.archlinux.org/index.php/Sy … ur_Session. I start systemd --user via a small script in my .bash_profile. Here are my relevant dbus{.service,socket} files, from the package user-session-units mentioned in the wiki: (Edit: xorg is started through xorg-launch-helper, also from that wiki page) Edit2: I'm not using autologin. I noticed that under the autologin section of that page, DBUS_SESSION_BUS_ADDRESS is set to some path. In my setup that isn't set anywhere, so I may try to copy that later but I don't have time to play with it right now. Will post back later.
=====/usr/lib/systemd/user/dbus.service=====
[Unit]
Description=D-Bus System Message Bus
Requires=dbus.socket
[Service]
ExecStart=/usr/bin/dbus-daemon --session --address=systemd: --nofork --systemd-activation
ExecReload=/usr/bin/dbus-send --print-reply --session --type=method_call --dest=org.freedesktop.DBus / org.freedesktop.DBus.ReloadConfig
=====/usr/lib/systemd/user/dbus.socket=====
[Unit]
Description=D-Bus System Message Bus Socket
[Socket]
ListenStream=%t/dbus/user_bus_socket
And the output of sudo systemctl status dbus:
dbus.service - D-Bus System Message Bus
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
Active: active (running) since Tue 2013-02-05 14:50:30 EST; 22min ago
Main PID: 369 (dbus-daemon)
CGroup: name=systemd:/system/dbus.service
└─369 /usr/bin/dbus-daemon --system --address=systemd: --no...
Feb 05 14:50:30 sellers-laptop systemd[1]: Starting D-Bus System Message Bus...
Feb 05 14:50:30 sellers-laptop systemd[1]: Started D-Bus System Message Bus.
Feb 05 14:51:18 sellers-laptop dbus-daemon[369]: dbus[369]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Feb 05 14:51:18 sellers-laptop dbus[369]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Feb 05 14:51:18 sellers-laptop dbus[369]: [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.
Feb 05 14:51:18 sellers-laptop dbus-daemon[369]: dbus[369]: [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.
I'm not sure what the error even means or how to go about debugging it. Any suggestions would be appreciated.
Last edited by Feynman (2013-02-05 22:07:23)NVM...didn't notice it was already solved.
Last edited by the sad clown (2013-02-05 22:33:10) -
[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) -
My /home is on a raid 1 disk which is in /dev/mapper/nvidia_cjjcaiiep1.
First of all my home partition is part of a raid 1.
When booting with init=/bin/systemd I have the following phenomenon:
Job dev-mapper-nvidia_cjjcaiiep1.device/start timed out and booting stops and I'm in a rescue shell.
my /home partition is not mounted.
/dev/mapper/nvidia_cjjcaiiep1 exists.
Systemctl start dev-mapper-nvidia_cjjcaiiep1.device gives the same result timeout.
and my /home is not mounted
After:
#mount /dev/mapper/nvidia_cjjcaiiep1 /boot this is a typo I ment /home
mount /dev/mapper/nvidia_cjjcaiiep1 /home
/home is mounted
Systemctl default
my system resumes booting and finally comes online.
I 'm new to systemd so if someone can be so kind to give me some hints how / where to start searching for the problem or maybe the problem is already known ...
Thanks in advance.
Fred
Last edited by fvsc (2012-08-14 09:07:36)I have the same problem, since I updated my system yesterday and resized my root-partition online (by this time I do not believe that the later is the reason):
When I boot my system, systemd comes to the point, where it has mounted /boot, waits there for a minute and tells me that it ran into problems. root was mounted, but it failed on home (in my case /dev/mapper/main-home). It was however possible to mount it by hand. However, starting my login-manager (slim) didn't work after that.
This is the output of journalctl:
Aug 14 16:41:55 merkur systemd-journal[180]: Journal started
Aug 14 16:41:55 merkur systemd-modules-load[181]: Inserted module 'vboxdrv'
Aug 14 16:41:59 merkur mtp-probe[332]: checking bus 3, device 2: "/sys/devices/pci0000:00/0000:00:1a.1/usb3/3-1"
Aug 14 16:41:59 merkur mtp-probe[342]: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-6"
Aug 14 16:41:59 merkur mtp-probe[342]: bus: 1, device: 4 was not an MTP device
Aug 14 16:41:59 merkur mtp-probe[332]: bus: 3, device: 2 was not an MTP device
Aug 14 16:42:00 merkur systemd-fsck[388]: boot: sauber, 30/122880 Dateien, 48260/489948 Blöcke (Prüfung nach nächstem Einhängen)
Aug 14 16:43:25 merkur systemd[1]: ^[[1;39mJob dev-mapper-main\x2dhome.device/start timed out.
Aug 14 16:43:25 merkur systemd[1]: ^[[1;39mJob local-fs.target/start failed with result 'dependency'.
Aug 14 16:43:25 merkur systemd[1]: Triggering OnFailure= dependencies of local-fs.target.
Aug 14 16:43:25 merkur systemd[1]: ^[[1;39mJob systemd-user-sessions.service/start failed with result 'dependency'.
Aug 14 16:43:25 merkur systemd[1]: ^[[1;39mJob slim.service/start failed with result 'dependency'.
Aug 14 16:43:25 merkur systemd[1]: ^[[1;39mJob graphical.target/start failed with result 'dependency'.
Aug 14 16:43:25 merkur systemd[1]: ^[[1;39mJob multi-user.target/start failed with result 'dependency'.
Aug 14 16:43:25 merkur systemd[1]: ^[[1;39mJob syslog-ng.service/start failed with result 'dependency'.
Aug 14 16:43:25 merkur systemd[1]: ^[[1;39mJob cronie.service/start failed with result 'dependency'.
Aug 14 16:43:25 merkur systemd[1]: ^[[1;39mJob acpid.service/start failed with result 'dependency'.
Aug 14 16:43:25 merkur systemd[1]: ^[[1;39mJob rc-local.service/start failed with result 'dependency'.
Aug 14 16:43:25 merkur systemd[1]: ^[[1;39mJob systemd-logind.service/start failed with result 'dependency'.
Aug 14 16:43:25 merkur systemd[1]: ^[[1;39mJob dbus.service/start failed with result 'dependency'.
Aug 14 16:43:25 merkur systemd[1]: ^[[1;39mJob [email protected]/start failed with result 'dependency'.
Aug 14 16:43:25 merkur systemd[1]: ^[[1;39mJob home.mount/start failed with result 'dependency'.
Aug 14 16:43:25 merkur systemd-journal[180]: Journal stopped
Aug 14 16:43:25 merkur systemd-journal[403]: Journal started
Aug 14 16:43:25 merkur systemd[401]: ^[[1;39mFailed at step EXEC spawning /bin/plymouth: No such file or directory
Aug 14 16:49:31 merkur systemd[1]: ^[[1;39mRequested transaction contradicts existing jobs: Transaction is destructive.
Aug 14 16:49:31 merkur systemd[1]: ^[[1;39memergency.service: control process exited, code=exited status=1
Aug 14 16:49:31 merkur systemd[1]: ^[[1;39mUnit emergency.service entered failed state.
Aug 14 16:49:31 merkur systemd[1]: ^[[1;39mShutting down.
Aug 14 16:49:31 merkur systemd[1]: Hardware watchdog 'iTCO_wdt', version 0
Aug 14 16:49:31 merkur systemd[1]: Set hardware watchdog to 10min.
Aug 14 16:49:31 merkur systemd-journal[403]: Journal stopped
my /etc/mkinitcpio.conf only differs in the following line from the default:
HOOKS="base udev autodetect pata scsi sata usb usbinput keymap encrypt lvm2 filesystems fsck"
My /etc/fstab
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
LABEL=boot /boot ext4 defaults 0 1
LABEL=root / ext4 defaults 0 1
#Those are not working:
LABEL=home /home ext4 defaults 0 1
LABEL=swap swap swap defaults 0 0
A possible workaround is to comment the home-partition in /etc/fstab (in my case the swap too) and login as root on a virtual terminal, where you mount your home by hand and then restart the login-manager.
Edit:
PS: using device-names instead of Labels in /etc/fstab didn't change anything
Last edited by FlorianJW (2012-08-14 15:27:40) -
[SOLVED]dual boot-Failed to mount real root device
Hello,
Here is my drives partition info:
/dev/sda1 2,949,122,048 3,907,028,991 957,906,944 7 NTFS / exFAT / HPFS
/dev/sda2 2,048 901,117,951 901,115,904 83 Linux
/dev/sda3 * 901,117,952 1,925,115,903 1,023,997,952 f W95 Extended (LBA)
/dev/sda5 901,120,000 901,439,487 319,488 83 Linux
/dev/sda6 901,441,536 905,648,127 4,206,592 82 Linux swap / Solaris
/dev/sda7 905,650,176 1,925,115,903 1,019,465,728 83 Linux
/dev/sda4 1,925,115,904 2,949,122,047 1,024,006,144 7 NTFS / exFAT / HPFS
/dev/sdb1 2,048 2,099,199 2,097,152 83 Linux
/dev/sdb2 2,099,200 53,299,199 51,200,000 83 Linux
/dev/sdb3 53,299,200 73,779,199 20,480,000 83 Linux
/dev/sdb4 73,779,200 224,673,791 150,894,592 7 NTFS / exFAT / HPFS
I installed Opensuse 12.1 on /dev/sda5. It is booting with Grub, working with no problems. The computer boots directly to Grub menu.
THEN, I installed Arch linux (last release) on both sda and sdb following these mounting points:
/dev/sdb1 mounted as /boot Ext2
/dev/sdb2 mounted as / BTRFS
/dev/sdb3 mounted as /usr BTRFS
/dev/sda2 mounted as /home BTRFS
Intstallation went smooth until the end. Installed the bootloader.
Now, I am trying to configure GRUB to boot Arch.
Here is what I added on /boot/grub/menu.lst, in sda5 under Opensuse:
title Arch Linux [/boot/vmlinuz-linux]
root (hd1,0)
kernel /vmlinuz-linux root=/dev/sdb1 ro
initrd /initramfs-linux.img
In Opensuse, i can check that vmlinux and grub/menu.lst are indeed in /dev/sdb1
My /etc/fstab is on /dev/sdb2
=============================== sdb2/etc/fstab: ==========
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
/dev/sda2 /home btrfs defaults 0 1
/dev/sdb1 /boot ext2 defaults 0 1
/dev/sdb2 / btrfs defaults 0 1
/dev/sdb3 /usr btrfs defaults 0 1
With this parameters, i got an message error when booting Arch:
Mounting /dev/sdb1 on /new_root failed: no such device.
Error : failed to mount the real root device.
So, at busybox prompt, I tried this command line :
ramfs # mount -t ext2 /dev/sdb1
Got an error : Can't read /etc/fstab
I tried too to give a uuid adress to sdb1 in my menu.lst file, but it didn't change anything, so I am sure partition number is correct.
It seems to me in fact that GRUB can't find fstab.
Two questions :
-Would it be better in fact to use only 1 GRUB file for both systems? If yes, shall I keep only the grub config from Opensuse?
-What do I wrong with Arch booting? Why can't I boot Arch?
EDIT :1- just realised there is no BOOT flag in my partiton table on /dev/sdb.
2- root is on /dev/sdb2, not sdb1.
1-I toggled my first partition bootable using fdisk
2-changed root to point to /dev/sdb2
Now booting into Arch login
Last edited by gabx (2011-11-22 22:33:09)It was a very simple problem. I used the wrong uuid for my /
Correct entry in 40_custom is:
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry "Arch Linux uuid" {
insmod part_msdos
insmod ext2
search --fs-uuid --no-floppy --set=root 8516fa60-0d45-4f33-b269-817c5290f6cc
linux /vmlinuz26 root=/dev/disk/by-uuid/9f32e668-2548-4ed4-a10b-3fbea66a6d95 ro vga=775
initrd /kernel26.img
Now the boot is working great. Next thing was that my /home and swap was not detected.
That was simply because /etc/fstab was still using /dev/sda etc naming. changing that to uuid solved that part as well.
To use uuid all the way and of cause the correct one solved everything
/Christer
Last edited by agkbill (2011-07-15 16:00:30) -
[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 suspend fails everytime
Hi,
I've been using Arch Linux on my laptop for a while now and suddenly my laptop would not go into suspend anymore.
My laptop is Asus UX32VD.
Here's the whole journalctl between suspend starting and suspend failing.
I also get this at bootup:
[drm:intel_dp_start_link_train] *ERROR* too many voltage retries, give up
some while ago the iSSD in my laptop failed but it was later that the computer stopped suspending.
Does anyone see the problem?
Thanks.
Edit: When I try to mount the iSSD partitions I get the same error messages that begin with "ata2.00" so those errors seem to be connected to the iSSD drive. Now, I can't disable the drive in bios, is it possible to make arch linux ignore it all together?
Edit2: Arch Linux is installed on sda (ata1) and the bad drive is sdb (ata2)
Edit3: The broken ssd was the culprit. When I write 1 to /sys/block/sdb/device/delete the laptop suspends correctly.
So I made the following systemd service:
[Unit]
Description=Disable my fault ssd drive at suspend
[Service]
Type=OneShot
ExecStart=/bin/sh -c 'echo 1 > /sys/block/sdb/device/delete'
[Install]
WantedBy=sleep.target
Changing status to solved
Last edited by granra (2014-04-18 23:01:57)Rexilion wrote:What is stopping you from taking it out?
It's soldered to the motherboard. -
Systemd.timesyncd fails on boot [Solved]
Upgraded systemd to 217-1 and now each boot sees timesyncd fail:
● systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled)
Active: failed (Result: start-limit) since Fri 2014-10-31 10:25:59 NZDT; 5min ago
Docs: man:systemd-timesyncd.service(8)
Process: 303 ExecStart=/usr/lib/systemd/systemd-timesyncd (code=exited, status=1/FAILURE)
Main PID: 303 (code=exited, status=1/FAILURE)
Status: "Shutting down..."
Oct 31 10:25:59 Shiv systemd[1]: Failed to start Network Time Synchronization.
Oct 31 10:25:59 Shiv systemd[1]: Unit systemd-timesyncd.service entered failed state.
Oct 31 10:25:59 Shiv systemd[1]: systemd-timesyncd.service failed.
Oct 31 10:25:59 Shiv systemd[1]: start request repeated too quickly for systemd-timesyncd.service
Oct 31 10:25:59 Shiv systemd[1]: Failed to start Network Time Synchronization.
Oct 31 10:25:59 Shiv systemd[1]: Unit systemd-timesyncd.service entered failed state.
Oct 31 10:25:59 Shiv systemd[1]: systemd-timesyncd.service failed.
Once I log in, I am able to restart the service without any complaint.
Anyone else seeing this?
# edit: perhaps related to this fixed(?) bug: http://lists.freedesktop.org/archives/s … 03199.htmltl;dr answer:
# sed -i 's/ remote-fs.target$//' /usr/lib/systemd/system/systemd-journal-flush.service
Long answer:
In systemd 217 a few changes were made with regard to ordering of early boot units, resulting in certain setups which used to work with systemd 216 to make problems with systemd 217. The fix above was also applied in systemd upstream by this commit:
commit 919699ec301ea507edce4a619141ed22e789ac0d
Author: Lennart Poettering <[email protected]>
Date: Fri Oct 31 16:22:36 2014 +0100
units: don't order journal flushing afte remote-fs.target
Instead, only depend on the actual file systems we need.
This should solve dep loops on setups where remote-fs.target is moved
into late boot.
For example, in my case, connman.service explicitly requests to be ordered before remote-fs.target, leading to all kinds of fun:
systemd[1]: Found ordering cycle on basic.target/start
systemd[1]: Found dependency on sysinit.target/start
systemd[1]: Found dependency on systemd-tmpfiles-setup.service/start
systemd[1]: Found dependency on systemd-journal-flush.service/start
systemd[1]: Found dependency on remote-fs.target/start
systemd[1]: Found dependency on connman.service/start
systemd[1]: Found dependency on basic.target/start
systemd[1]: Breaking ordering cycle by deleting job systemd-tmpfiles-setup.service/start
systemd-timesyncd[201]: Failed to allocate manager: No such file or directory
systemd[1]: systemd-timesyncd.service: main process exited, code=exited, status=1/FAILURE
systemd[1]: Failed to start Network Time Synchronization.
systemd[1]: Unit systemd-timesyncd.service entered failed state.
systemd[1]: systemd-timesyncd.service failed.
Explanation:
systemd-journal-flush.service wants to be ordered after remote-fs.target whereas connman.service wants to be ordered before remote-fs.target. Additionally, connman.service requires basic.target. (This is implicit behavior for units which don't declare "DefaultDependencies=no".) This is why basic.target ends up getting pulled in so early in the first place.
Furthermore, systemd-timesyncd.service relies on properly initialized runtime directories in order to work, so it wants to be ordered after systemd-tmpfiles-setup.service.
In order to be able to start basic.target, systemd breaks the ordering cycle by taking systemd-tmpfiles-setup.service out of the transaction, thereby preventing systemd-timesyncd.service from starting up correctly.
Last edited by csn (2014-11-01 22:18:37) -
[SOLVED]systemd-tmpfiles-setup.service fails
Hi,
I have installed arch on an old laptop (dell inspiron 6000). I haven't used arch linux for last 2 years. It seems system management style has changed drastically.
Anyways, systemctl status systemd-tmpfiles-setup.service returns this;
● systemd-tmpfiles-setup.service - Create Volatile Files and Directories
Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Sal 2015-06-09 11:00:18 EEST; 38min ago
Docs: man:tmpfiles.d(5)
man:systemd-tmpfiles(8)
Process: 228 ExecStart=/usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE)
Main PID: 228 (code=exited, status=1/FAILURE)
Haz 09 11:00:18 yasar-laptop systemd[1]: Starting Create Volatile Files and Directories...
Haz 09 11:00:18 yasar-laptop systemd[1]: systemd-tmpfiles-setup.service: main process exited, code=exited, status=1/FAILURE
Haz 09 11:00:18 yasar-laptop systemd[1]: Failed to start Create Volatile Files and Directories.
Haz 09 11:00:18 yasar-laptop systemd[1]: Unit systemd-tmpfiles-setup.service entered failed state.
Haz 09 11:00:18 yasar-laptop systemd[1]: systemd-tmpfiles-setup.service failed.
Is this something that I should be concerned? I don't really know what this service supposed to do?
If I should be concerned, how to troubleshoot it? Keep in mind that this is a fresh arch install.
Last edited by yasar11732 (2015-06-09 16:31:04)Thanks,
I have add acl option to fstab file, it works now. If anyone else has this problem, here is how my fstab file looks now;
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
UUID=936297ec-2bc3-45ef-bdb0-0a4ce7239204 / ext4 rw,relatime,data=ordered 0 1
UUID=d1fd9d31-99b5-45ba-97f4-a4c20b96e48b /var reiserfs rw,relatime,acl 0 2
UUID=6a9b3e39-8ea2-446f-9a71-79faab7cdafe /home xfs rw,relatime,attr2,inode64,noquota 0 2
# UUID=eb0b40d3-43ac-4f1f-8b29-97cd16a534d4
UUID=eb0b40d3-43ac-4f1f-8b29-97cd16a534d4 none swap defaults 0 0 -
[SOLVED] systemd & separate /boot causing boot failure
I'm working on moving to systemd, and I'm having a boot issue. I don't think my setup is particularly peculiar, but essentially: I have 2 disks, sda and sdb. sda contains some windows partitions, and /dev/sda4 is my data/homedir partition. /dev/sdb holds my arch install:
/dev/sda4 - /home (btrfs) (no label)
/dev/sdb1 - /boot (ext2) label=arch-boot
/dev/sdb2 - swap label=arch-swap
/dev/sdb3 - / (btrfs) label=arch-root
I have the expected entries in /etc/fstab:
UUID=XXXX / btrfs default 0 1
UUID=XXXX /boot ext2 defaults 0 1
UUID=XXXX /home btrfs defaults,relatime,ssd 0 1
UUID=XXXX swap swap defaults 0 0
This worked fine under initscripts (again, nothing hugely weird here), but under systemd what effectively happens is the various devices seem to be automounted by systemd, as well as being mounted via fstab. So, during boot I get mounts:
/dev/sdb3 on /media/arch-root type btrfs
/dev/sdb1 on /media/arch-boot type ext4
/dev/sda4 on /media/usbhd-sda4
as well as the "fstab versions":
/dev/sdb3 on / type btrfs
/dev/sda4 on /home type btrfs
Notably, the "fstab version" of /boot is missing. During boot, the 'boot.mount' unit fails, with:
mount: /dev/sdb1 is already mounted or /boot busy
mount: /dev/sdb1 is already mounted on /media/arch-boot
And bootup stops. Manually invoking "mount /boot" fails with the same error. I see the "automount" unit:
$ systemctl|grep boot.mount
boot.mount load failed failed /boot
media-arch\x2dboot.mount load active mounted /media/arch-boot
So, I can then issue:
$ systemctl stop 'media-arch\x2dboot.mount'
$ systemctl start 'boot.mount'
Which does successfully unmount the "automount" version, and mount the "fstab version", and I can then exit the emergency shell and boot normally. However, I am unable to issue, say "systemctl disable 'media-arch\x2dboot.mount'"; I simply get a complaint of "Failed to issue method call: No such file or directory." This probably makes sense, and comes down to a misunderstanding on my part between units, services, targets, etc.
I'm assuming it's *not* expected that we just allow all devices to be automounted (i.e. just remove my /boot entry from fstab)? How can I mark these entries as "do not automatically create mount points under /media"? Or, alternatively, make sure the fstab entries are loaded first, obviating the need for the automount? I'm guessing I'm missing something obvious here as I doubt this is a strange setup, but unfortunately I haven't had much google success when my search criteria are "systemd" and "/boot"...
Last edited by nogoma (2012-08-16 14:10:34)So, this was actually not systemd related, as I discovered when I booted under initscripts again. Essentially, I had an overly general rule in /etc/udev/rules.d that was causing the automount behavior; restricting the matching devices to my non-boot disks fixed the issue.
-
Can anyone help with this please? Sorry if it's a well known issue and I have just failed to find the solution, but I have searched for one.
I use yaourt -Syu regularly, and generally it's great.
BUT - every time linux-3.17...-x86_64.pkg.tar.xz is upgraded the system fails to reboot! Throwing something like:
Nov 17 16:09:49 cart systemd[1]: boot-efi.mount mount process exited, code=exited status=32
Nov 17 16:09:49 cart systemd[1]: Failed to mount /boot/efi.
Nov 17 16:09:49 cart systemd[1]: Unit boot-efi.mount entered failed state.
Nov 17 16:09:49 cart mount[232]: mount: unknown filesystem type 'vfat'
After much struggling I have discovered a workaround, but I don't understand it - or like it. This is what I do:
1. Boot from an archiso image cd in UEFI mode
2. Mount the correct partitions on / /home and /boot
3. # arch-chroot /mnt /bin/bash
4. # cd /var/cache/pacman/pkg
5. # pacman -U linux-3.16.3-1-x86_64.pkg.tar.xz (or whatever is the latest upgrade)
Then, when I exit and reboot all is well again.
I use the rEFInd boot manager to choose between ArchLinux and ,reluctantly, Windows 8.1 - I suspect that might have something to do with my problem but I don't know what.
If anyone can tell what I am doing wrong, please explain.
Thanks
John
Last edited by JohnColeman (2014-11-18 15:58:51)Hi Matt,
I think you've done it - thanks a lot.
I changed this line in my /etc/fstab :
UUID=0E51-F605 /boot/efi vfat ...
to
UUID=0E51-F605 /boot vfat ...
and I think that's done the trick.
I did pacman -U linux-3.16.3-1-x86_64.pkg.tar.xz again without booting from an archiso image cd in UEFI mode, which would previously have failed - and it didn't.
I look forward to the next actual upgrade of linux-3...
Thanks again, I can't remember how, or why, I went wrong in fstab but I won't do it again.
John -
[SOLVED]Systemd Tmpfile Setup Service Fails
I'm not sure what version this began but I'm using systemd 185-1 and systemd-arch-units 20120606-4. Service just fails to start. Is this fixable?
└╼ $ systemctl status systemd-tmpfiles-setup.service
systemd-tmpfiles-setup.service - Recreate Volatile Files and Directories
Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static)
Active: failed (Result: exit-code) since Fri, 22 Jun 2012 04:22:15 -0400; 36s ago
Docs: man:tmpfiles.d(5)
Process: 931 ExecStart=/usr/bin/systemd-tmpfiles --create --remove (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/systemd-tmpfiles-setup.service
Last edited by Hspasta (2012-06-23 04:31:05)swanson wrote:Check fstab and comment out the tmp there.
Did and didn't help.
WorMzy wrote:
Do you have any aur/custom-made packages that put *.conf files in /usr/lib/tmpfiles.d or /usr/local/lib/tmpfiles.d?
Does the system journal have any more information about the failure?
Hm...I have a lot of stuff in /usr/lib/tmpfiles.d/
└╼ $ ls /usr/lib/tmpfiles.d/
total 44K
-rw-r--r-- 1 root root 30 Jun 4 16:12 console.conf
-rw-r--r-- 1 root root 29 May 27 00:29 consolekit.conf
-rw-r--r-- 1 root root 74 Jun 6 19:02 initscripts.conf
-rw-r--r-- 1 root root 719 Jun 4 16:12 legacy.conf
-rw-r--r-- 1 root root 61 Jun 16 01:28 lvm2.conf
-rw-r--r-- 1 root root 24 Jun 1 00:04 mpd.conf
-rw-r--r-- 1 root root 27 Jun 9 03:29 nscd.conf
-rw-r--r-- 1 root root 30 Jun 9 01:41 openssh.conf
-rw-r--r-- 1 root root 729 Jun 4 16:12 systemd.conf
-rw-r--r-- 1 root root 449 Jun 4 16:12 tmp.conf
-rw-r--r-- 1 root root 622 Jun 4 16:12 x11.conf
I feel like something in my system is broken... -
[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]systemd-fstab-generator and syslog error?
here is the bootup error message:
Nov 2 07:27:58 localhost [ 9.207762] systemd-fstab-generator[151]: Failed to create unit file: File exists
Nov 2 07:27:58 localhost [ 10.119699] systemd[1]: /usr/lib/systemd/system-generators/systemd-fstab-generator exited with exit status 1.
Nov 2 07:27:58 localhost [ 10.544789] systemd[1]: Socket service syslog.service not loaded, refusing.
Nov 2 07:27:58 localhost [ 10.544974] systemd[1]: Failed to listen on Syslog Socket.
and my fstab is here:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
/dev/sdb1 /boot ext2 defaults 0 1
/dev/sdb5 / jfs defaults 0 1
/dev/sdb6 /home ext4 defaults,user_xattr 0 1
/dev/sdb7 /var reiserfs defaults 0 1
/dev/sdb8 /tmp reiserfs defaults 0 1
Last edited by frat (2012-11-02 03:21:07)systemd-fstab-generator is fixed,thank you.
syslog errors still:
Nov 2 10:29:44 localhost [ 10.051816] systemd[1]: Socket service syslog.service not loaded, refusing.
Nov 2 10:29:44 localhost [ 10.052000] systemd[1]: Failed to listen on Syslog Socket.
#systemctl status syslog
syslog.service
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)
#systemctl status syslog.socket
syslog.socket - Syslog Socket
Loaded: loaded (/usr/lib/systemd/system/syslog.socket; static)
Active: inactive (dead)
Docs: man:systemd.special(7)
http://www.freedesktop.org/wiki/Software/systemd/syslog
CGroup: name=systemd:/system/syslog.socket
any advice?
Last edited by frat (2012-11-02 02:56:37) -
[SOLVED] Slow boot. Ran systemd-analyze blame.
Issue:
Boot seems snappy, but when I get to the tty login there's a ~35s-1m10s delay before the login completes.
What I've tried:
- Boot with WiFi switch off
- Remove wpa_supplicant
- "Remove" systemd-hostnamed service files (backed them up and restored them when I saw it hadn't helped)
- Add Type=simple to autologin.conf
- Remove autologin.conf
- Disable openvpn
- Disable connman
- Removed some RAM? Success!
$ systemd-analyze blame
1min 9.815s [email protected]
1min 5.556s wpa_supplicant.service
35.248s systemd-hostnamed.service
12.764s [email protected]
7.402s systemd-backlight@backlight:acpi_video0.service
7.394s systemd-backlight@backlight:radeon_bl0.service
7.353s shadow.service
7.189s logrotate.service
6.880s systemd-user-sessions.service
1.267s systemd-logind.service
1.265s connman.service
1.255s chrony.service
1.067s systemd-tmpfiles-clean.service
1.049s alsa-restore.service
914ms systemd-remount-fs.service
860ms dev-hugepages.mount
858ms dev-mqueue.mount
856ms sys-kernel-config.mount
854ms sys-kernel-debug.mount
851ms tmp.mount
755ms systemd-udev-trigger.service
631ms kmod-static-nodes.service
586ms systemd-fsck@dev-disk-by\x2duuid-12636bd2\x2d5d5b\x2d4267\x2d843f\x2db1bbc130e62c.service
282ms systemd-vconsole-setup.service
223ms systemd-random-seed.service
204ms [email protected]
165ms systemd-sysctl.service
158ms boot.mount
147ms systemd-tmpfiles-setup.service
98ms systemd-tmpfiles-setup-dev.service
59ms systemd-update-utmp.service
51ms systemd-udevd.service
12ms connman-vpn.service
3ms systemd-journal-flush.service
1ms [email protected]
Wow! What's going on?
$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @20.574s
└─multi-user.target @20.553s
└─[email protected] @7.768s +12.764s
└─basic.target @7.765s
└─timers.target @7.765s
└─updatedb.timer @7.765s
└─sysinit.target @7.735s
└─systemd-journald.service @1min 42.978s
└─system.slice @1.255s
└─-.slice @1.250s
$ systemctl status user@1000
● [email protected] - User Manager for UID 1000
Loaded: loaded (/usr/lib/systemd/system/[email protected]; static)
Active: active (running) since Mon 2014-11-03 08:34:13 EST; 6min ago
Main PID: 350 (systemd)
Status: "Startup finished in 35.658s."
CGroup: /user.slice/user-1000.slice/[email protected]
├─350 /usr/lib/systemd/systemd --user
└─351 (sd-pam)
Nov 03 08:33:37 arch2 systemd[350]: pam_unix(systemd-user:session): session opened for user geosmin by (uid=0)
Nov 03 08:34:13 arch2 systemd[1]: Started User Manager for UID 1000.
$ systemctl status wpa_supplicant
● wpa_supplicant.service - WPA supplicant
Loaded: loaded (/usr/lib/systemd/system/wpa_supplicant.service; disabled)
Active: active (running) since Mon 2014-11-03 08:34:13 EST; 8min ago
Main PID: 356 (wpa_supplicant)
CGroup: /system.slice/wpa_supplicant.service
└─356 /usr/bin/wpa_supplicant -u
$ systemctl status systemd-hostnamed
● systemd-hostnamed.service - Hostname Service
Loaded: loaded (/usr/lib/systemd/system/systemd-hostnamed.service; static)
Active: failed (Result: exit-code) since Mon 2014-11-03 08:34:13 EST; 8min ago
Docs: man:systemd-hostnamed.service(8)
man:hostname(5)
man:machine-info(5)
[url]http://www.freedesktop.org/wiki/Software/systemd/hostnamed[/url]
Process: 355 ExecStart=/usr/lib/systemd/systemd-hostnamed (code=exited, status=1/FAILURE)
Main PID: 355 (code=exited, status=1/FAILURE)
Nov 03 08:34:12 arch2 systemd-hostnamed[355]: Failed to register name: Connection timed out
Nov 03 08:34:13 arch2 systemd[1]: systemd-hostnamed.service: main process exited, code=exited, status=1/FAILURE
Nov 03 08:34:13 arch2 systemd[1]: Failed to start Hostname Service.
Any input appreciated.
Last edited by geosmin (2014-11-05 08:16:24)Decided to be reckless and did:
# mv /usr/lib/systemd/systemd-hostnamed /usr/lib/systemd/systemd-hostnamed~
# mv /usr/lib/systemd/system/systemd-hostnamed.service /usr/lib/systemd/system/systemd-hostnamed.service~
Now systemd-analyze blame shows:
50.804s wpa_supplicant.service
50.803s connman-vpn.service
3.367s [email protected]
I have no idea what's going on.
Last edited by geosmin (2014-11-05 07:26:11)
Maybe you are looking for
-
How to Sort Print Presets in IDCS3
Hello I have a long list of print presets, and I would like to sort them. Is there a way??? I would hate to manually recreate like 30 of them. Thanks, Art
-
I am unable to figure out what I am having trouble with this, here is the code public class Tools3 protected long item_number; protected String product_name; protected long units_in_stock; protected double price_of_each_unit; prot
-
Curve/Level RGB Doesn't Change Individual Channels
Weird. When I adjust slider in Levels or point in Curves using the RGB master (default), and then go to the individual color channels, none of them have changed at all. Has anyone else seen this behavior?
-
Some basic questions about foriegn key , and relationships.
Hi Thank you for reading my post I read some documents about foreugn key and tables relation ships. but i still can not understnad some stuff. 1-when we have a foreign key , we have two tables that we want to relate them together in a way that one of
-
The system cannot download information from the SQLSERVER server.
Hi All, After BPC 7.0 SP6 for MS install we get the following when trying to access the "Manage Application Sets" or any other admin console task, when we try to execute the connection wizard: The system cannot download information from the SQLSERVER