Annoying systemd boot mounting behaviour?

Id like to change behaviour..
Currently....
When you have some unmountable entry at fstab, it wont let you boot in the system, even if it were an usb? I experienced that with a secondary harddrive. (or maybe it did not boot because there is a swap on the second hdd)
If systemd really does not boot in to the login prompt,because ofunmountable entry in fstab,can it be changed ?

thisoldman wrote:
Add 'nofail' to the mount options for the USB drive in your fstab.
From 'man mount':
nofail Do not report errors for this device if it does not exist.
Owe thanks This bugged the crap out of me too.
Awebb wrote:Curious. I remember the same effect a year ago. Maybe you had some other configurations done preventing this behavior in the past.
No, initscripts do not have this problem.
Last edited by hunterthomson (2012-12-25 01:54:50)

Similar Messages

[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

Systemd boot is extremely "loud" with the quiet kernel parameter

Systemd boot got really slow at some point.
It prints all the messages with all the green OK status. It is extremely slow, in fact, slower that any sequential boot 20 years ago. No errors though.
Kernel parameters are as per silent boot article with quiet and log level set appropriately.
Any help is appreciated. Maybe I can fiddle with some other systemd parameters? It does not look it parallelised at all.

headkase wrote:You're welcome. Do post your Blame when you can.
Here you go...
5.339s NetworkManager-wait-online.service
1.432s man-db.service
345ms dev-sda2.device
298ms NetworkManager.service
207ms systemd-journald.service
131ms systemd-modules-load.service
129ms proc-fs-nfsd.mount
114ms logrotate.service
113ms shadow.service
109ms polkit.service
103ms upower.service
85ms systemd-journal-flush.service
83ms [email protected]
82ms systemd-random-seed.service
76ms gssproxy.service
76ms wpa_supplicant.service
73ms rpc-statd-notify.service
70ms systemd-tmpfiles-clean.service
62ms home.mount
58ms nfs-config.service
52ms systemd-udevd.service
48ms accounts-daemon.service
41ms boot.mount
36ms var-lib-nfs-rpc_pipefs.mount
31ms systemd-udev-trigger.service
29ms colord.service
28ms udisks2.service
25ms systemd-sysctl.service
25ms gdm.service
20ms systemd-tmpfiles-setup.service
20ms systemd-logind.service
19ms systemd-update-utmp.service
17ms systemd-remount-fs.service
15ms sys-kernel-debug.mount
15ms [email protected]
12ms tmp.mount
10ms dev-hugepages.mount
9ms dev-mqueue.mount
8ms systemd-tmpfiles-setup-dev.service
8ms systemd-vconsole-setup.service
6ms kmod-static-nodes.service
5ms sys-fs-fuse-connections.mount
5ms rtkit-daemon.service
4ms systemd-user-sessions.service
4ms systemd-backlight@backlight:acpi_video0.service
2ms [email protected]
2ms [email protected]
1ms systemd-backlight@backlight:intel_backlight.service
1ms sys-kernel-config.mount
Please use code text when posting snippets -- Inxsible
Last edited by Inxsible (2015-05-01 14:26:02)

Logging all file opens immediately at systemd boot?

when I start my stage-2 systemd boot, I want to log every file that is being opened for reading or writing (to /var/log/accessed.log). am I reinventing the wheel if I write this or is there already a standard service that does this?
my plan is to use the fanotify_event framework to write a file logger, presumably with a service file like.
[Unit]
Description=fanotify-logger
DefaultDependencies=no
After=local-fs.target
[Service]
Type=oneshot
ExecStart=/usr/local/bin/fanotify-all / /var/log/accessed.log
is there a best-practices recommendation where local sysadmins should insert such services (e.g., which directory, steps, etc.) and, does my logger need to know how to shutdown, or will the standard systemd service shut this down by itself?
/iaw

You used to be able to do this with boot.kernel.org, but not anymore.
pxelinux.0 isn't the kernel, and you can only use it if you have an actual pxe installation available which I don't think is there at releng.archlinux.org.
You have to install your own pxe setup and yes it does use NFS.
If you are using qemu you don't even need the ipxe, it is already included with qemu.
Last edited by nomorewindows (2012-08-03 23:42:16)

[SOLVED] Can't get systemd to mount nfs on boot

I have "/usr/lib/systemd/system/mnt-shared.mount" with
[Unit]
Description=/mnt/shared
Wants=rpc-statd.service
After=network.target rpc-statd.service
[Mount]
What=10.0.0.3:/home/shared
Where=/mnt/shared
Type=nfs
but when I reboot the mount never occurs. I have to manually do "systemctl start mnt-shared.mount" every time.
Is there something special I have to do for systemd to use .mount files automatically?
Last edited by boast (2012-07-13 20:43:21)

In the beginning with systemd I had nfs mounting problems too. But after some extensive testing I found that the fstab mounting was the best with some systemd adjustments.
192.168.1.250:/ /mnt/SERVER_NYTT nfs4 noauto,rw,hard,async,intr,rsize=81920,wsize=81920,_netdev,clientaddr=192.168.1.251,x-systemd.automount 0 0
All these options might not suit you but noauto and x-systemd.automount are the important ones. You can test it by doing systemd-analyze blame. With this setup systemd takes care of all the before, after, requires stuff pretty well by itself.
Last edited by swanson (2012-07-13 08:35:50)

LVM /dev/mapper is empty, + systemd boot hangs

Hi!
1st problem:
I have 2 vgs with 1 lv each -- called Sys/Linux and Sys2/Var. Booting the kernel with root=/dev/mapper/Sys-Linux works, but after mounting the root fs, /dev/mapper is empty:
$ ls /dev/mapper
control
2nd problem:
I changed UUID= to /dev/dm-1 for /var for testing purposes, but systemd will timeout on mounting /var. Note: after entering the emergency console, I can just type mount /var and it will mount.
The system is was quite old and I changed to systemd-only right now, because I upgraded the filesystem package (that removes /bin, /sbin, /usr/sbin and required me to remove outdated packages). ((Yes, I'm late )).
I hope anyone has some pointers; please tell me, which config files you need to see if any, to help out.
Thanks,
Andy
Last edited by Black Sliver (2013-08-12 20:14:40)

[2013-08-12 19:33] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2013-08-12 19:33] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> Starting build: 3.10.5-1-ARCH
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [lvm2]
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> ERROR: file not found: `/usr/sbin/dmsetup'
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [resume]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [shutdown]
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> Creating lzma initcpio image: /boot/initramfs-linux.img
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> WARNING: errors were encountered during the build. The image may not be complete.
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> Starting build: 3.10.5-1-ARCH
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: bfa
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: smsmdtv
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [lvm2]
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> ERROR: file not found: `/usr/sbin/dmsetup'
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [resume]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [shutdown]
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> Creating lzma initcpio image: /boot/initramfs-linux-fallback.img
[2013-08-12 19:34] [ALPM-SCRIPTLET] ==> WARNING: errors were encountered during the build. The image may not be complete.
Note that initial mounting of root=/dev/mapper/Sys-Linux works. Can this be the problem anyway? I rebuilt the initrd, I'll try to boot it tomorrow.
[2013-08-12 19:42] [PACMAN] Running 'pacman -R initscripts sysvinit' # NOTE: this was required for the filesystem upgrade to work (/sbin)
[2013-08-12 19:42] [ALPM] warning: /etc/rc.conf saved as /etc/rc.conf.pacsave
[2013-08-12 19:42] [ALPM] warning: /etc/inittab saved as /etc/inittab.pacsave
Theese are not required with systemd ?
Everything else is just upgrade/install/remove or uninteresting. Or do you want to see everything?
Last edited by Black Sliver (2013-08-12 22:48:32)

[Solved]Controlling systemd's 'emergency-behaviour'

So after boot-cycling some systems only to return to the 'emergency-console' because something went wrong during boot, I'm wondering if there is any way to control 'when' exactly the system(d) decides it can no longer continue booting.
More specifically, I know why the boot fails, its because of a certain mount line in /etc/fstab.
Sometimes the filesystem just isn't available, in my case because the kernel-module needed hasn't been rebuilt after a kernel upgrade, but its easy to image other scenarios like networked filesystems and such.
So I'm wondering how to stop systemd from dropping into 'emergency-room-mode' just because of a failed mount line in /etc/fstb, and more generally if/where/how more fine grained control is possible.
Any ideas?
Last edited by hungerfish (2014-08-17 13:32:05)

...but for my purposes I'd rather the boot process be as permissive as possible.
Exactly my point, it could be more permissive in case such as non-essential fs not being available.*
The 'nofail' option apparently does just that (tell the system that a fs is not essential). This fixes my 'problem'.
And it gets to chose when to stick to the rules and when to ignore some, and it gets to chose which ones to ignore.
The whole point of me asking was to find out how to to instruct the system towards behaving in a appropriate fashion. The 'nofail' option tells the system to 'ignore some stuff', in this case a filesystem, I don't get your angle.
What's the problem, again?
*While using 'nofail' works fine, the 'problem/nag' that remains is that this could be the default for non-essential mountpoints thus eliminating the need for adding the option manually. But I guess there's a ton of reasons for it not being so, or maybe not...

Systemd boot fails

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)

Slow systemd boot on laptop.

Hey folks!
I'm having an issue with my boot speed since re-installing arch on my laptop. (Lenovo Y580).
[root@shard matt]# systemd-analyze
Startup finished in 2.796s (kernel) + 3min 3.038s (userspace) = 3min 5.834s
It's taking 3 min's to boot.
[root@shard matt]# systemd-analyze blame
3.136s NetworkManager.service
1.768s dev-sdb3.swap
1.488s systemd-logind.service
1.022s systemd-journal-flush.service
697ms polkit.service
410ms wpa_supplicant.service
390ms kmod-static-nodes.service
368ms systemd-user-sessions.service
292ms [email protected]
276ms dev-mqueue.mount
274ms dev-hugepages.mount
168ms systemd-udev-trigger.service
163ms systemd-remount-fs.service
156ms systemd-vconsole-setup.service
155ms systemd-sysctl.service
151ms systemd-backlight@acpi_video0.service
151ms systemd-backlight@acpi_video1.service
141ms upower.service
134ms udisks2.service
131ms systemd-tmpfiles-setup-dev.service
94ms systemd-update-utmp.service
44ms sys-kernel-debug.mount
42ms sys-kernel-config.mount
37ms systemd-random-seed.service
16ms systemd-udevd.service
6ms alsa-restore.service
5ms systemd-tmpfiles-setup.service
1ms tmp.mount
[root@shard matt]# systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @1min 33.912s
`-multi-user.target @1min 33.912s
`-NetworkManager.service @1min 30.775s +3.136s
`-basic.target @1min 30.775s
`-timers.target @1min 30.773s
`-systemd-tmpfiles-clean.timer @1min 30.772s
`-sysinit.target @1min 30.771s
`-systemd-backlight@acpi_video1.service @4.920s +151ms
`-systemd-remount-fs.service @1.009s +163ms
`-systemd-journald.socket @772ms
`--.mount @771ms
`-system.slice @1.048s
`--.slice @1.048s
I'm still not sure which process is causing the delay, but it was only seconds to boot before.
Last edited by vanic (2013-09-25 12:04:10)

Try systemd-analyze plot > plot.svg and have a look at that file; maybe it shows you what you want

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

IBook G4 won't boot / patchy behaviour

I'd like some input on debugging a friend's iBook G4.
System specs: White 12" 1.3GHz, 512MB RAM (wired), airport card, stock tiger, no other peripherals.
Only extra drivers I could see installed were for an MS Bluetooth keyboard/mouse. No uninstaller apparent, and can't see specific drivers for these devices in relevant system folders.
System was booting to kernel panic screen, and with an urgent paid writing assignment she brought it to me for assistance. Occasionally (after power off?) the system would boot and run for a few minutes before kernel panic.
Response to special key combos is patchy at boot time. It's hard to get the system to boot into any special mode, seems like the keyboard only responds sometimes.
When I can get it to boot, safe mode runs consistently, while normal (unsafe?) mode kernel panics quickly.
We tested the disk for errors while booted off the 10.4 install CD. No issues.
We ran an archive+install but this behaved exactly as before. (Repeated to confirm. Same results.)
I did notice that plugging a USB mouse before boot would prevent the system from booting. Plugging the mouse in during or after boot produced two results; either a working mouse, or a non-working mouse.
Trackpad works intermittently. She reported that she had cleaned the trackpad (not sure if this was very recent).
My suspicion is that something has caused an issue in a USB device, possibly the trackpad, and that the kernel panics if the USB drivers are fully loaded (would explain it working better in safe mode) but isn't sensitive to the same odd behaviour when basic drivers only are loaded.
This is pretty much a best guess, based on me having tried to isolate the issue at various other points and failed to find anything else specific to work with.
We disconnected the trackpad connector, but this didn't improve the situation; still frozen if USB device connected at boot, and still boots to kernel panic otherwise.
Are there some specific drivers I could disable to test this theory? I don't expect this to help much, however, as driver issues are not indicated by the usb mouse freezing system at boot time.
She would be very pleased to have the machine working again. Any suggestions or input will be much appreciated!
Thanks

Our iBook G4 started having kernel panics about 2 weeks ago. It would panic at start up or after a few minutes of running, similar to your story. To cut to the chase I did the standard routine for a kernel panic down to archiving and installing with no luck (http://www.thexlab.com/faqs/kernelpanics.html ). When I checked the panic log after all this it seemed to indicate a problem with the airport. I managed to get it to boot and turned the airport off and the problem went away.
I took it in to get checked today thinking the Airport would be an easy fix. They ran a diagnostic DVD and told me the problem was with the CPU and was not fixable without replacing the whole board.
I did some looking today and this seems to be a common problem with this model. The best summary of the various threads is at http://www.appledefects.com/wiki/index.php?title=IBookG41.33GHz . The only solution I could find seems to be in French and has a scary photo of a flaming computer at the end! http://www.applintosh.net/readarticle.php?article_id=1
I got back to the store about this particular fault and if it applied to my ibook and they kindly replied
"Yes I am aware of people having problems with this, I pulled the top case of the machine off and disconnected all the peripherals as part of our process of elimination, it still only booted to a black screen when trying to boot our diagnostic hard drive(this was with the airport/Bluetooth card Disconnected) I then connected the optical drive up and booted our diagnostics disc up, it still failed the CPU test.
From having the diagnostic test fail and the fact that it would not even turn on when every peripheral was disconnected leaves me with a 100% guarantee that it can only be the main logic board.
19 out of the last 22 of the iBooks that I have seen that have had kernal panic issues and then we have found it to be a conflict with the airport card have all had faulty logic boards, we have tried new airport cards many of times with no luck. 1 was a faulty airport card but it was faulty from day one of purchase and the other 2 were because they had liquid spilt on the keyboard and it leaks down right on top of the airport card."
So I dont know if the problem is in the airport itself or the logic board but it would seem that in this model they are one and the same. More depressing news was to follow - logic boards cost $1600 NZ so it would seem a new computer is the more sensible option. Bit disappointing after just 2 and a bit years use.
The iBook itself works fine when the airport is off, even with an ethernet cable connected to enable internet access. Dont feel that happy though doing anything important with a computer with a faulty logic board though no matter how well backed up..
Hope this helps a fellow Kiwi. If you find anything useful out let me know. FYI the local stores I tried were Ubertech and Magnum Mac.

Systemd boot up errors

Hi all,
I successfully moved to systemd after the gnome 3.6 update, however I have few issues reporting during boot up that I cannot figure out nor finding information on the forum/wiki/web hence the topic.
See below journalctl outpout:
Nov 26 10:58:55 linuxbox gnome-keyring-daemon[666]: Gkm: using old keyring directory: /home/sweetth/.gnome2/keyrings
Nov 26 10:58:55 linuxbox gnome-keyring-daemon[666]: Gkm: using old keyring directory: /home/sweetth/.gnome2/keyrings
Nov 26 10:58:57 linuxbox pulseaudio[731]: [pulseaudio] source.c: Default and alternate sample rates are the same.
Nov 26 10:58:57 linuxbox pulseaudio[731]: [pulseaudio] bluetooth-util.c: org.bluez.Manager.ListAdapters() failed: org.freedesktop.systemd1.LoadFailed: Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details.
Nov 26 10:58:57 linuxbox pulseaudio[731]: [pulseaudio] module.c: module-combine is deprecated: Please use module-combine-sink instead of module-combine!
Nov 26 10:58:57 linuxbox pulseaudio[731]: [pulseaudio] module-combine.c: We will now load module-combine-sink. Please make sure to remove module-combine from your configuration.
Nov 26 10:58:58 linuxbox pulseaudio[761]: [pulseaudio] pid.c: Daemon already running.
Nov 26 10:59:01 linuxbox goa[796]: goa-daemon version 3.6.2 starting [main.c:112, main()]
Nov 26 10:59:02 linuxbox gnome-keyring-daemon[666]: keyring alias directory: /home/sweetth/.gnome2/keyrings
And the output of
sudo systemctl status dbus-org.bluez.service
dbus-org.bluez.service
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)
Many thanks for your time,
Looking forward for your comments and advices,
Regards,

I have the same question related to the keyring issue as I get the following on boot:
Nov 30 07:25:03 thinkpad gnome-keyring-daemon[676]: Gkm: using old keyring directory: /home/orschiro/.gnome2/keyrings
Nov 30 07:25:03 thinkpad gnome-keyring-daemon[676]: Gkm: using old keyring directory: /home/orschiro/.gnome2/keyrings
Nov 30 07:26:27 thinkpad gnome-keyring-daemon[676]: keyring alias directory: /home/orschiro/.gnome2/keyrings
Nov 30 07:26:44 thinkpad gnome-keyring-daemon[676]: couldn't allocate secure memory to keep passwords and or keys from being written to the disk
Does anybody know what this mean exactly?

Systemd (auto)mount USB fails due to fsck

Hi,
I am trying to get 'hotplugging' functionality working for usb storage devices with systemd with the ultimate goal of running a backup service via systemd which will require certain devices and mounts to be active.
After a few searchers, I decided the approach of adding the external storage device to fstab with a couple systemd options
Here's the relevant line in my fstab
# USB for data where CoW not desired
UUID=964cc231-af3f-49ef-94f3-f73ffd551fda /media/storage_nocow ext4 noauto,x-systemd.automount 0 2
That worked nicely. The device is mounted anytime the mountpoint is requested (e.g. by cd'ing into that directory) provided that the device has not been unmounted.
If the device has been unmounted (with systemctl stop media-storage_nocow.mount) or removed, and then plugged back in, the mount unit fails with very vague error message. I looked around but didn't find anything definitive on how to address the issue
systemctl status media-storage_nocow.mount | tail -n 2
#May 28 11:40:57 archLenFlex systemd[1]: Dependency failed for /media/storage_nocow.
#May 28 11:40:57 archLenFlex systemd[1]: Job media-storage_nocow.mount/start failed with result 'dependency'.
I checked that the device is active
systemctl status --full dev-disk-by\\x2dlabel-CORSAIR64.device
● dev-disk-by\x2dlabel-CORSAIR64.device - Voyager_VEGA CORSAIR64
Follow: unit currently follows state of sys-devices-pci0000:00-0000:00:14.0-usb3-3\x2d1-3\x2d1:1.0-host4-target4:0:0-4:0:0:0-block-sdb-sdb1.device
Loaded: loaded
Active: active (plugged) since Thu 2015-05-28 15:43:36 EDT; 2h 2min ago
Device: /sys/devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0/host4/target4:0:0/4:0:0:0/block/sdb/sdb1
The messages from journalctl were of little help. I dug around into the unit files which are generated from fstab and found that the mount requires a couple services
RequiresOverridable=systemd-fsck@dev-disk-by\x2duuid-964cc231\x2daf3f\x2d49ef\x2d94f3\x2df73ffd551fda.service
After=systemd-fsck@dev-disk-by\x2duuid-964cc231\x2daf3f\x2d49ef\x2d94f3\x2df73ffd551fda.service
[Mount]
What=/dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda
Where=/media/storage_nocow
Type=ext4
Options=nofail,rw,noauto,x-systemd.automount
the requires/after units failed
systemctl status --full systemd-fsck@dev-disk-by\\x2duuid-964cc231\\x2daf3f\\x2d49ef\\x2d94f3\\x2df73ffd551fda.service
● systemd-fsck@dev-disk-by\x2duuid-964cc231\x2daf3f\x2d49ef\x2d94f3\x2df73ffd551fda.service - File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda
Loaded: loaded (/usr/lib/systemd/system/[email protected]; static; vendor preset: disabled)
Active: inactive (dead) since Thu 2015-05-28 15:43:26 EDT; 30min ago
Docs: man:[email protected](8)
Process: 797 ExecStart=/usr/lib/systemd/systemd-fsck %f (code=exited, status=0/SUCCESS)
Main PID: 797 (code=exited, status=0/SUCCESS)
May 28 15:31:27 archLenFlex systemd[1]: Starting File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda...
May 28 15:31:27 archLenFlex systemd-fsck[797]: CORSAIR64: clean, 12/3784704 files, 283568/15123984 blocks
May 28 15:31:27 archLenFlex systemd[1]: Started File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda.
May 28 15:43:26 archLenFlex systemd[1]: Stopped File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda.
May 28 15:43:26 archLenFlex systemd[1]: Stopping File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda...
May 28 15:45:22 archLenFlex systemd[1]: Dependency failed for File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda.
May 28 15:45:22 archLenFlex systemd[1]: Job systemd-fsck@dev-disk-by\x2duuid-964cc231\x2daf3f\x2d49ef\x2d94f3\x2df73ffd551fda.service/start failed with result 'dependency'.
Looking further into those units - the fsck service has a couple dependencies:
After=%i.device systemd-fsck-root.service local-fs-pre.target
Before=shutdown.target
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/lib/systemd/systemd-fsck %f
StandardOutput=journal+console
TimeoutSec=0
The only one that failed was the sytemd-fsck-root.service - the other two were active/successful.
● systemd-fsck-root.service - File System Check on Root Device
Loaded: loaded (/usr/lib/systemd/system/systemd-fsck-root.service; static; vendor preset: disabled)
Active: inactive (dead)
Docs: man:systemd-fsck-root.service(8)
So, I figured I can skip the fsck in fstab and it should work. This is the case, with the following fstab line for the device,
UUID=964cc231-af3f-49ef-94f3-f73ffd551fda /media/storage_nocow ext4 noauto,x-systemd.automount 0 0
From there, requesting the mountpoint activates the mount via the automount, provided the mount unit was stopped but the device wasn't unplugged. If the device is unplugged, it is necessary stop the mount unit and reload the systemctl daemon.
I think it is preferable to have the device fsck'd.
So can anyone advise why the fsck is failing and how to get the mount to work while keeping the fsck option in fstab? Why does the usb device mount even require the root fsck? I would think it should only require its own fsck.
Thanks in advance.
Last edited by akpol (2015-05-28 22:16:44)

Hi,
I am trying to get 'hotplugging' functionality working for usb storage devices with systemd with the ultimate goal of running a backup service via systemd which will require certain devices and mounts to be active.
After a few searchers, I decided the approach of adding the external storage device to fstab with a couple systemd options
Here's the relevant line in my fstab
# USB for data where CoW not desired
UUID=964cc231-af3f-49ef-94f3-f73ffd551fda /media/storage_nocow ext4 noauto,x-systemd.automount 0 2
That worked nicely. The device is mounted anytime the mountpoint is requested (e.g. by cd'ing into that directory) provided that the device has not been unmounted.
If the device has been unmounted (with systemctl stop media-storage_nocow.mount) or removed, and then plugged back in, the mount unit fails with very vague error message. I looked around but didn't find anything definitive on how to address the issue
systemctl status media-storage_nocow.mount | tail -n 2
#May 28 11:40:57 archLenFlex systemd[1]: Dependency failed for /media/storage_nocow.
#May 28 11:40:57 archLenFlex systemd[1]: Job media-storage_nocow.mount/start failed with result 'dependency'.
I checked that the device is active
systemctl status --full dev-disk-by\\x2dlabel-CORSAIR64.device
● dev-disk-by\x2dlabel-CORSAIR64.device - Voyager_VEGA CORSAIR64
Follow: unit currently follows state of sys-devices-pci0000:00-0000:00:14.0-usb3-3\x2d1-3\x2d1:1.0-host4-target4:0:0-4:0:0:0-block-sdb-sdb1.device
Loaded: loaded
Active: active (plugged) since Thu 2015-05-28 15:43:36 EDT; 2h 2min ago
Device: /sys/devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0/host4/target4:0:0/4:0:0:0/block/sdb/sdb1
The messages from journalctl were of little help. I dug around into the unit files which are generated from fstab and found that the mount requires a couple services
RequiresOverridable=systemd-fsck@dev-disk-by\x2duuid-964cc231\x2daf3f\x2d49ef\x2d94f3\x2df73ffd551fda.service
After=systemd-fsck@dev-disk-by\x2duuid-964cc231\x2daf3f\x2d49ef\x2d94f3\x2df73ffd551fda.service
[Mount]
What=/dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda
Where=/media/storage_nocow
Type=ext4
Options=nofail,rw,noauto,x-systemd.automount
the requires/after units failed
systemctl status --full systemd-fsck@dev-disk-by\\x2duuid-964cc231\\x2daf3f\\x2d49ef\\x2d94f3\\x2df73ffd551fda.service
● systemd-fsck@dev-disk-by\x2duuid-964cc231\x2daf3f\x2d49ef\x2d94f3\x2df73ffd551fda.service - File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda
Loaded: loaded (/usr/lib/systemd/system/[email protected]; static; vendor preset: disabled)
Active: inactive (dead) since Thu 2015-05-28 15:43:26 EDT; 30min ago
Docs: man:[email protected](8)
Process: 797 ExecStart=/usr/lib/systemd/systemd-fsck %f (code=exited, status=0/SUCCESS)
Main PID: 797 (code=exited, status=0/SUCCESS)
May 28 15:31:27 archLenFlex systemd[1]: Starting File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda...
May 28 15:31:27 archLenFlex systemd-fsck[797]: CORSAIR64: clean, 12/3784704 files, 283568/15123984 blocks
May 28 15:31:27 archLenFlex systemd[1]: Started File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda.
May 28 15:43:26 archLenFlex systemd[1]: Stopped File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda.
May 28 15:43:26 archLenFlex systemd[1]: Stopping File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda...
May 28 15:45:22 archLenFlex systemd[1]: Dependency failed for File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda.
May 28 15:45:22 archLenFlex systemd[1]: Job systemd-fsck@dev-disk-by\x2duuid-964cc231\x2daf3f\x2d49ef\x2d94f3\x2df73ffd551fda.service/start failed with result 'dependency'.
Looking further into those units - the fsck service has a couple dependencies:
After=%i.device systemd-fsck-root.service local-fs-pre.target
Before=shutdown.target
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/lib/systemd/systemd-fsck %f
StandardOutput=journal+console
TimeoutSec=0
The only one that failed was the sytemd-fsck-root.service - the other two were active/successful.
● systemd-fsck-root.service - File System Check on Root Device
Loaded: loaded (/usr/lib/systemd/system/systemd-fsck-root.service; static; vendor preset: disabled)
Active: inactive (dead)
Docs: man:systemd-fsck-root.service(8)
So, I figured I can skip the fsck in fstab and it should work. This is the case, with the following fstab line for the device,
UUID=964cc231-af3f-49ef-94f3-f73ffd551fda /media/storage_nocow ext4 noauto,x-systemd.automount 0 0
From there, requesting the mountpoint activates the mount via the automount, provided the mount unit was stopped but the device wasn't unplugged. If the device is unplugged, it is necessary stop the mount unit and reload the systemctl daemon.
I think it is preferable to have the device fsck'd.
So can anyone advise why the fsck is failing and how to get the mount to work while keeping the fsck option in fstab? Why does the usb device mount even require the root fsck? I would think it should only require its own fsck.
Thanks in advance.
Last edited by akpol (2015-05-28 22:16:44)

Systemd Boot Problem - Times out waiting for LVM partitions

At first I had a problem in which the initramfs didn't map LVM partitions to /dev/vg0/lv, only /dev/mapper/vg0-lv. I changed /dev/vg0/root to /dev/mapper/vg0-root in bootloader configuration as a hacky workaround.
Getting closer to a working system, systemd failed boot because my fstab entries are uuids, and for some reason, my LVM volumes aren't showing up in /dev/disk/by-*. My flash drive boot partition shows up in there though.
I replaced the uuids with /dev/mapper/vg0-* and tried again. Now my boot fails with this:
Oct 21 19:19:31 archserver systemd[1]: Job dev-mapper-vg0\x2dmedia.device/start timed out.
Oct 21 19:19:31 archserver systemd[1]: Timed out waiting for device dev-mapper-vg0\x2dmedia.device.
Oct 21 19:19:31 archserver systemd[1]: Dependency failed for /mnt/media.
Oct 21 19:19:31 archserver systemd[1]: Dependency failed for Local File Systems.
Boot log: http://sprunge.us/LEhG
mkinitcpio.conf: http://sprunge.us/QEBK
What should I do?

This may be LVM's incompatibility with anything hotplug (it may not be, your issue sounds more obscure). You need to create your own, local lvm service file. I'll tell you how. This is /usr/lib/systemd/system/lvm.service:
[Unit]
Description=LVM activation
DefaultDependencies=no
Requires=systemd-udev-settle.service
After=systemd-udev-settle.service
Before=basic.target shutdown.target
Conflicts=shutdown.target
[Service]
ExecStart=/sbin/vgchange --available y
Type=oneshot
TimeoutSec=0
RemainAfterExit=yes
[Install]
WantedBy=basic.target
Create /etc/systemd/system/lvm_local.service:
[Unit]
Description=LVM activation
DefaultDependencies=no
Requires=dev-something-something1.device
After=dev-something-something1.device
Requires=dev-something-something2.device
After=dev-something-something2.device
Before=basic.target shutdown.target
Conflicts=shutdown.target
[Service]
ExecStart=/sbin/vgchange --available y
Type=oneshot
TimeoutSec=0
RemainAfterExit=yes
[Install]
WantedBy=basic.target
No, what to you put in those "something-something1" places above? For each LVM physical volume, run 'systemctl status /dev/disk/by-uuid/$UUID' where $UUID is the UUID of your physical volume. You'll get a status output showing the exact name of the correct .device unit. Then 'systemctl enable lvm_local.service'.
This speeds up boot and makes sure lvm is properly initialized. After writing all this, I am unsure if this is at all related to your problem, as your volume group is activated in initramfs and the links should be set up by udev.

USB ISO Boot Mounter!!!

I prefer my Easy2Boot setup. I can change it on the fly without having to find the program I complied it on.
http://www.easy2boot.com/make-an-easy2boot-usb-drive/

I've a few CD's i use regularly now on USB's etc. I'd like to have a sngle USB which can mount an ISO collection for booting rather than carry everthing. I used to have one which worked most of the tie but it was basically built ad hoc by someone who new about such things. Any ideas on software for this?
This topic first appeared in the Spiceworks Community

Annoying systemd boot mounting behaviour?

Similar Messages

Maybe you are looking for