Systemd-hostnamed.service fails to start

I'm finding the systemd-hostnamed.service isnt working
$ sudo systemctl --state=failed
[sudo] password for kevdog:
UNIT LOAD ACTIVE SUB DESCRIPTION
● systemd-hostnamed.service loaded failed failed Hostname Service
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
1 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
$ sudo systemctl status systemd-hostnamed.service
● systemd-hostnamed.service - Hostname Service
Loaded: loaded (/usr/lib/systemd/system/systemd-hostnamed.service; static)
Active: failed (Result: timeout) since Tue 2014-12-16 23:11:36 CST; 10min ago
Docs: man:systemd-hostnamed.service(8)
man:hostname(5)
man:machine-info(5)
http://www.freedesktop.org/wiki/Software/systemd/hostnamed
Main PID: 4584
Dec 16 23:08:35 orphan systemd[1]: systemd-hostnamed.service start operation timed out. Terminating.
Dec 16 23:10:06 orphan systemd[1]: systemd-hostnamed.service stop-final-sigterm timed out. Killing.
Dec 16 23:11:36 orphan systemd[1]: systemd-hostnamed.service still around after final SIGKILL. Entering failed mode.
Dec 16 23:11:36 orphan systemd[1]: Failed to start Hostname Service.
Dec 16 23:11:36 orphan systemd[1]: Unit systemd-hostnamed.service entered failed state.
Dec 16 23:11:36 orphan systemd[1]: systemd-hostnamed.service failed.
I found this addressed in this topic:
https://github.com/ev3dev/ev3dev/issues/189
Within this page they state:
Confirmed that removing PrivateNetwork=yes from the service file works as a workaround. Maybe need to enable CONFIG_NAMESPACES=y and CONFIG_NET_NS=y kernel modules
I removed the PrivateNetwork=yes from the service file, however this didn't seem to work. I did not enable the kernel modules. I am currently running the following kernel: 3.17.6-1-ARCH
Thanks

Similar Messages

[Solved] systemd-hostnamed.service broken in systemd 212?

Can someone confirm by checking
hostnamectl status
and
systemctl --failed
Thanks!
Last edited by gedgon (2014-04-03 20:30:03)

teateawhy wrote:Works for me.
Hmm, interesting. In v.212 systemd-hostnamed.service failing for me, and hostnamectl timing out. Works fine after downgrading.
Edit: Problem caused by wrong /var/tmp permission. Thanks, teateawhy.
Last edited by gedgon (2014-04-03 20:29:47)

Systemd-logind occasionally fails to start

Hi,
I am running Arch with Cinnamon started by mdm-display-manager. I had this running for quite some time without an issue.
Recently an issue popped out - OCCASIONALLY systemd-logind fails to start and I get stuck on boot screen. This happens maybe once in 5-10 boots. I have to do hard reset afterwards. CTL+ALT+DEL won't work, I can not switch to other console and I have no network to SSH to that machine.
Other than that, system starts just fine.
I am not sure, how to debug this further and would appreciate advice.
# journalctl --since=today --unit=systemd-logind
May 26 09:42:34 phenom systemd[1]: Starting Login Service...
May 26 09:42:59 phenom systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
May 26 09:42:59 phenom systemd[1]: Failed to start Login Service.
May 26 09:42:59 phenom systemd[1]: Unit systemd-logind.service entered failed state.
May 26 09:42:59 phenom systemd[1]: systemd-logind.service failed.
May 26 09:42:59 phenom systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
# journalctl --since=today
May 26 09:42:34 phenom systemd-journal[198]: Runtime journal is using 8.0M (max allowed 802.5M, trying to leave 1.1G free of 7.7G available → current limit 802.5M).
May 26 09:42:34 phenom systemd-journal[198]: Permanent journal is using 2.0G (max allowed 4.0G, trying to leave 4.0G free of 36.6G available → current limit 4.0G).
May 26 09:42:34 phenom systemd-journal[198]: Time spent on flushing to /var is 11.024ms for 2 entries.
May 26 09:42:34 phenom kernel: Initializing cgroup subsys cpuset
May 26 09:42:34 phenom kernel: Initializing cgroup subsys cpu
May 26 09:42:34 phenom kernel: Initializing cgroup subsys cpuacct
May 26 09:42:34 phenom kernel: Linux version 4.0.4-2-ARCH (builduser@foutrelis) (gcc version 5.1.0 (GCC) ) #1 SMP PREEMPT Fri May 22 03:05:23 UTC 2015
May 26 09:42:34 phenom kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=d36ad497-1614-4cc5-8cc9-da2d5e5a417c rw
May 26 09:42:34 phenom kernel: tseg: 00cff00000
May 26 09:42:34 phenom kernel: e820: BIOS-provided physical RAM map:
May 26 09:42:34 phenom kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000099fff] usable
May 26 09:42:34 phenom kernel: BIOS-e820: [mem 0x000000000009f800-0x000000000009ffff] reserved
May 26 09:42:34 phenom kernel: BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
May 26 09:42:34 phenom kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000cfd9ffff] usable
May 26 09:42:34 phenom kernel: BIOS-e820: [mem 0x00000000cfda0000-0x00000000cfdd0fff] ACPI NVS
May 26 09:42:34 phenom kernel: BIOS-e820: [mem 0x00000000cfdd1000-0x00000000cfdfffff] ACPI data
May 26 09:42:34 phenom kernel: BIOS-e820: [mem 0x00000000cfe00000-0x00000000cfefffff] reserved
May 26 09:42:34 phenom kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
May 26 09:42:34 phenom kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000ffffffff] reserved
May 26 09:42:34 phenom kernel: BIOS-e820: [mem 0x0000000100000000-0x000000042fffffff] usable
May 26 09:42:34 phenom kernel: NX (Execute Disable) protection: active
May 26 09:42:34 phenom kernel: SMBIOS 2.4 present.
May 26 09:42:34 phenom kernel: DMI: Gigabyte Technology Co., Ltd. GA-990XA-UD3/GA-990XA-UD3, BIOS F9 10/13/2011
May 26 09:42:34 phenom kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
May 26 09:42:34 phenom kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
May 26 09:42:34 phenom kernel: AGP: No AGP bridge found
May 26 09:42:34 phenom kernel: e820: last_pfn = 0x430000 max_arch_pfn = 0x400000000
May 26 09:42:34 phenom kernel: MTRR default type: uncachable
May 26 09:42:34 phenom kernel: MTRR fixed ranges enabled:
May 26 09:42:34 phenom kernel: 00000-9FFFF write-back
May 26 09:42:34 phenom kernel: A0000-BFFFF uncachable
May 26 09:42:34 phenom kernel: C0000-C7FFF write-protect
May 26 09:42:34 phenom kernel: C8000-FFFFF uncachable
May 26 09:42:34 phenom kernel: MTRR variable ranges enabled:
May 26 09:42:34 phenom kernel: 0 base 000000000000 mask FFFF80000000 write-back
May 26 09:42:34 phenom kernel: 1 base 000080000000 mask FFFFC0000000 write-back
May 26 09:42:34 phenom kernel: 2 base 0000C0000000 mask FFFFF0000000 write-back
May 26 09:42:34 phenom kernel: 3 base 0000CFE00000 mask FFFFFFE00000 uncachable
May 26 09:42:34 phenom kernel: 4 disabled
May 26 09:42:34 phenom kernel: 5 disabled
May 26 09:42:34 phenom kernel: 6 disabled
May 26 09:42:34 phenom kernel: 7 disabled
May 26 09:42:34 phenom kernel: TOM2: 0000000430000000 aka 17152M
May 26 09:42:34 phenom kernel: PAT configuration [0-7]: WB WC UC- UC WB WC UC- UC
May 26 09:42:34 phenom kernel: e820: update [mem 0xcfe00000-0xffffffff] usable ==> reserved
May 26 09:42:34 phenom kernel: e820: last_pfn = 0xcfda0 max_arch_pfn = 0x400000000
May 26 09:42:34 phenom kernel: found SMP MP-table at [mem 0x000f4b30-0x000f4b3f] mapped at [ffff8800000f4b30]
May 26 09:42:34 phenom kernel: Scanning 1 areas for low memory corruption
May 26 09:42:34 phenom kernel: Base memory trampoline at [ffff880000094000] 94000 size 24576
May 26 09:42:34 phenom kernel: Using GB pages for direct mapping
May 26 09:42:34 phenom kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
May 26 09:42:34 phenom kernel: [mem 0x00000000-0x000fffff] page 4k
May 26 09:42:34 phenom kernel: BRK [0x01b1d000, 0x01b1dfff] PGTABLE
May 26 09:42:34 phenom kernel: BRK [0x01b1e000, 0x01b1efff] PGTABLE
May 26 09:42:34 phenom kernel: BRK [0x01b1f000, 0x01b1ffff] PGTABLE
May 26 09:42:34 phenom kernel: init_memory_mapping: [mem 0x42fe00000-0x42fffffff]
May 26 09:42:34 phenom kernel: [mem 0x42fe00000-0x42fffffff] page 2M
May 26 09:42:34 phenom kernel: BRK [0x01b20000, 0x01b20fff] PGTABLE
May 26 09:42:34 phenom kernel: init_memory_mapping: [mem 0x420000000-0x42fdfffff]
May 26 09:42:34 phenom kernel: [mem 0x420000000-0x42fdfffff] page 2M
May 26 09:42:34 phenom kernel: init_memory_mapping: [mem 0x400000000-0x41fffffff]
May 26 09:42:34 phenom kernel: [mem 0x400000000-0x41fffffff] page 2M
May 26 09:42:34 phenom kernel: init_memory_mapping: [mem 0x00100000-0xcfd9ffff]
May 26 09:42:34 phenom kernel: [mem 0x00100000-0x001fffff] page 4k
May 26 09:42:34 phenom kernel: [mem 0x00200000-0x3fffffff] page 2M
May 26 09:42:34 phenom kernel: [mem 0x40000000-0xbfffffff] page 1G
May 26 09:42:34 phenom kernel: [mem 0xc0000000-0xcfbfffff] page 2M
May 26 09:42:34 phenom kernel: [mem 0xcfc00000-0xcfd9ffff] page 4k
May 26 09:42:34 phenom kernel: init_memory_mapping: [mem 0x100000000-0x3ffffffff]
May 26 09:42:34 phenom kernel: [mem 0x100000000-0x3ffffffff] page 1G
May 26 09:42:34 phenom kernel: RAMDISK: [mem 0x362ae000-0x3714efff]
May 26 09:42:34 phenom kernel: ACPI: Early table checksum verification disabled
May 26 09:42:34 phenom kernel: ACPI: RSDP 0x00000000000F6A50 000014 (v00 GBT )
May 26 09:42:34 phenom kernel: ACPI: RSDT 0x00000000CFDD1000 000048 (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
May 26 09:42:34 phenom kernel: ACPI: FACP 0x00000000CFDD1080 000074 (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
May 26 09:42:34 phenom kernel: ACPI: DSDT 0x00000000CFDD1100 007A4B (v01 GBT GBTUACPI 00001000 MSFT 03000000)
May 26 09:42:34 phenom kernel: ACPI: FACS 0x00000000CFDA0000 000040
May 26 09:42:34 phenom kernel: ACPI: SSDT 0x00000000CFDD8C40 000EDC (v01 PTLTD POWERNOW 00000001 LTP 00000001)
May 26 09:42:34 phenom kernel: ACPI: MSDM 0x00000000CFDD9B40 000055 (v03 GBT GBTUACPI 42302E31 GBTU 01010101)
May 26 09:42:34 phenom kernel: ACPI: HPET 0x00000000CFDD9BC0 000038 (v01 GBT GBTUACPI 42302E31 GBTU 00000098)
May 26 09:42:34 phenom kernel: ACPI: MCFG 0x00000000CFDD9C00 00003C (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
May 26 09:42:34 phenom kernel: ACPI: MATS 0x00000000CFDD9C80 000034 (v01 GBT 00000000 00000000)
May 26 09:42:34 phenom kernel: ACPI: TAMG 0x00000000CFDD9CF0 000202 (v01 GBT GBT B0 5455312E BG?? 53450101)
May 26 09:42:34 phenom kernel: ACPI: APIC 0x00000000CFDD8B80 0000BC (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
May 26 09:42:34 phenom kernel: ACPI: MATS 0x00000000CFDD9F00 006207 (v01 MATS RCM 80000001 INTL 20061109)
May 26 09:42:34 phenom kernel: ACPI: Local APIC address 0xfee00000
May 26 09:42:34 phenom kernel: Scanning NUMA topology in Northbridge 24
May 26 09:42:34 phenom kernel: No NUMA configuration found
May 26 09:42:34 phenom kernel: Faking a node at [mem 0x0000000000000000-0x000000042fffffff]
May 26 09:42:34 phenom kernel: NODE_DATA(0) allocated [mem 0x42fffa000-0x42fffdfff]
May 26 09:42:34 phenom kernel: [ffffea0000000000-ffffea0010bfffff] PMD -> [ffff88041f600000-ffff88042f5fffff] on node 0
May 26 09:42:34 phenom kernel: Zone ranges:
May 26 09:42:34 phenom kernel: DMA [mem 0x0000000000001000-0x0000000000ffffff]
May 26 09:42:34 phenom kernel: DMA32 [mem 0x0000000001000000-0x00000000ffffffff]
May 26 09:42:34 phenom kernel: Normal [mem 0x0000000100000000-0x000000042fffffff]
May 26 09:42:34 phenom kernel: Movable zone start for each node
May 26 09:42:34 phenom kernel: Early memory node ranges
May 26 09:42:34 phenom kernel: node 0: [mem 0x0000000000001000-0x0000000000099fff]
May 26 09:42:34 phenom kernel: node 0: [mem 0x0000000000100000-0x00000000cfd9ffff]
May 26 09:42:34 phenom kernel: node 0: [mem 0x0000000100000000-0x000000042fffffff]
May 26 09:42:34 phenom kernel: Initmem setup node 0 [mem 0x0000000000001000-0x000000042fffffff]
May 26 09:42:34 phenom kernel: On node 0 totalpages: 4193593
May 26 09:42:34 phenom kernel: DMA zone: 64 pages used for memmap
May 26 09:42:34 phenom kernel: DMA zone: 21 pages reserved
May 26 09:42:34 phenom kernel: DMA zone: 3993 pages, LIFO batch:0
May 26 09:42:34 phenom kernel: DMA32 zone: 13239 pages used for memmap
May 26 09:42:34 phenom kernel: DMA32 zone: 847264 pages, LIFO batch:31
May 26 09:42:34 phenom kernel: Normal zone: 52224 pages used for memmap
May 26 09:42:34 phenom kernel: Normal zone: 3342336 pages, LIFO batch:31
May 26 09:42:34 phenom kernel: ACPI: PM-Timer IO Port: 0x808
May 26 09:42:34 phenom kernel: ACPI: Local APIC address 0xfee00000
May 26 09:42:34 phenom kernel: ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
May 26 09:42:34 phenom kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
May 26 09:42:34 phenom kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
May 26 09:42:34 phenom kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
May 26 09:42:34 phenom kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] enabled)
May 26 09:42:34 phenom kernel: ACPI: LAPIC (acpi_id[0x05] lapic_id[0x05] enabled)
May 26 09:42:34 phenom kernel: ACPI: LAPIC (acpi_id[0x06] lapic_id[0x06] disabled)
May 26 09:42:34 phenom kernel: ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] disabled)
May 26 09:42:34 phenom kernel: ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
May 26 09:42:34 phenom kernel: ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
May 26 09:42:34 phenom kernel: ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
May 26 09:42:34 phenom kernel: ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1])
May 26 09:42:34 phenom kernel: ACPI: LAPIC_NMI (acpi_id[0x04] dfl dfl lint[0x1])
May 26 09:42:34 phenom kernel: ACPI: LAPIC_NMI (acpi_id[0x05] dfl dfl lint[0x1])
May 26 09:42:34 phenom kernel: ACPI: LAPIC_NMI (acpi_id[0x06] dfl dfl lint[0x1])
May 26 09:42:34 phenom kernel: ACPI: LAPIC_NMI (acpi_id[0x07] dfl dfl lint[0x1])
May 26 09:42:34 phenom kernel: ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
May 26 09:42:34 phenom kernel: IOAPIC[0]: apic_id 8, version 33, address 0xfec00000, GSI 0-23
May 26 09:42:34 phenom kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
May 26 09:42:34 phenom kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
May 26 09:42:34 phenom kernel: ACPI: IRQ0 used by override.
May 26 09:42:34 phenom kernel: ACPI: IRQ9 used by override.
May 26 09:42:34 phenom kernel: Using ACPI (MADT) for SMP configuration information
May 26 09:42:34 phenom kernel: ACPI: HPET id: 0x10b9a201 base: 0xfed00000
May 26 09:42:34 phenom kernel: smpboot: Allowing 8 CPUs, 2 hotplug CPUs
May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0x0009a000-0x0009ffff]
May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000effff]
May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0x000f0000-0x000fffff]
May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0xcfda0000-0xcfdd0fff]
May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0xcfdd1000-0xcfdfffff]
May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0xcfe00000-0xcfefffff]
May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0xcff00000-0xdfffffff]
May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0xe0000000-0xefffffff]
May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0xf0000000-0xfebfffff]
May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0xfec00000-0xffffffff]
May 26 09:42:34 phenom kernel: e820: [mem 0xcff00000-0xdfffffff] available for PCI devices
May 26 09:42:34 phenom kernel: Booting paravirtualized kernel on bare hardware
May 26 09:42:34 phenom kernel: setup_percpu: NR_CPUS:128 nr_cpumask_bits:128 nr_cpu_ids:8 nr_node_ids:1
May 26 09:42:34 phenom kernel: PERCPU: Embedded 31 pages/cpu @ffff88042fc00000 s86232 r8192 d32552 u262144
May 26 09:42:34 phenom kernel: pcpu-alloc: s86232 r8192 d32552 u262144 alloc=1*2097152
May 26 09:42:34 phenom kernel: pcpu-alloc: [0] 0 1 2 3 4 5 6 7
May 26 09:42:34 phenom kernel: Built 1 zonelists in Node order, mobility grouping on. Total pages: 4128045
May 26 09:42:34 phenom kernel: Policy zone: Normal
May 26 09:42:34 phenom kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=d36ad497-1614-4cc5-8cc9-da2d5e5a417c rw
May 26 09:42:34 phenom kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
May 26 09:42:34 phenom kernel: AGP: Checking aperture...
May 26 09:42:34 phenom kernel: AGP: No AGP bridge found
May 26 09:42:34 phenom kernel: AGP: Node 0: aperture [bus addr 0xc4000000-0xc5ffffff] (32MB)
May 26 09:42:34 phenom kernel: Aperture pointing to e820 RAM. Ignoring.
May 26 09:42:34 phenom kernel: AGP: Your BIOS doesn't leave a aperture memory hole
May 26 09:42:34 phenom kernel: AGP: Please enable the IOMMU option in the BIOS setup
May 26 09:42:34 phenom kernel: AGP: This costs you 64MB of RAM
May 26 09:42:34 phenom kernel: AGP: Mapping aperture over RAM [mem 0xc4000000-0xc7ffffff] (65536KB)
May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0xc4000000-0xc7ffffff]
May 26 09:42:34 phenom kernel: Memory: 16352908K/16774372K available (5628K kernel code, 840K rwdata, 1784K rodata, 1160K init, 1152K bss, 421464K reserved, 0K cma-reserved)
May 26 09:42:34 phenom kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
May 26 09:42:34 phenom kernel: Preemptible hierarchical RCU implementation.
May 26 09:42:34 phenom kernel: RCU dyntick-idle grace-period acceleration is enabled.
May 26 09:42:34 phenom kernel: RCU restricting CPUs from NR_CPUS=128 to nr_cpu_ids=8.
May 26 09:42:34 phenom kernel: RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
May 26 09:42:34 phenom kernel: NR_IRQS:8448 nr_irqs:488 16
May 26 09:42:34 phenom kernel: spurious 8259A interrupt: IRQ7.
May 26 09:42:34 phenom kernel: Console: colour dummy device 80x25
May 26 09:42:34 phenom kernel: console [tty0] enabled
May 26 09:42:34 phenom kernel: hpet clockevent registered
May 26 09:42:34 phenom kernel: tsc: Fast TSC calibration using PIT
May 26 09:42:34 phenom kernel: tsc: Detected 3300.124 MHz processor
May 26 09:42:34 phenom kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 6602.25 BogoMIPS (lpj=11000413)
May 26 09:42:34 phenom kernel: pid_max: default: 32768 minimum: 301
May 26 09:42:34 phenom kernel: ACPI: Core revision 20150204
May 26 09:42:34 phenom kernel: ACPI: All ACPI Tables successfully acquired
May 26 09:42:34 phenom kernel: Security Framework initialized
May 26 09:42:34 phenom kernel: Yama: becoming mindful.
May 26 09:42:34 phenom kernel: Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes)
May 26 09:42:34 phenom kernel: Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes)
May 26 09:42:34 phenom kernel: Mount-cache hash table entries: 32768 (order: 6, 262144 bytes)
May 26 09:42:34 phenom kernel: Mountpoint-cache hash table entries: 32768 (order: 6, 262144 bytes)
May 26 09:42:34 phenom kernel: Initializing cgroup subsys blkio
May 26 09:42:34 phenom kernel: Initializing cgroup subsys memory
May 26 09:42:34 phenom kernel: Initializing cgroup subsys devices
May 26 09:42:34 phenom kernel: Initializing cgroup subsys freezer
May 26 09:42:34 phenom kernel: Initializing cgroup subsys net_cls
May 26 09:42:34 phenom kernel: CPU: Physical Processor ID: 0
May 26 09:42:34 phenom kernel: CPU: Processor Core ID: 0
May 26 09:42:34 phenom kernel: mce: CPU supports 6 MCE banks
May 26 09:42:34 phenom kernel: LVT offset 0 assigned for vector 0xf9
May 26 09:42:34 phenom kernel: process: using AMD E400 aware idle routine
May 26 09:42:34 phenom kernel: Last level iTLB entries: 4KB 512, 2MB 16, 4MB 8
May 26 09:42:34 phenom kernel: Last level dTLB entries: 4KB 512, 2MB 128, 4MB 64, 1GB 0
May 26 09:42:34 phenom kernel: Freeing SMP alternatives memory: 20K (ffffffff819f6000 - ffffffff819fb000)
May 26 09:42:34 phenom kernel: ftrace: allocating 21316 entries in 84 pages
May 26 09:42:34 phenom kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
May 26 09:42:34 phenom kernel: smpboot: CPU0: AMD Phenom(tm) II X6 1100T Processor (fam: 10, model: 0a, stepping: 00)
May 26 09:42:34 phenom kernel: Performance Events: AMD PMU driver.
May 26 09:42:34 phenom kernel: ... version: 0
May 26 09:42:34 phenom kernel: ... bit width: 48
May 26 09:42:34 phenom kernel: ... generic registers: 4
May 26 09:42:34 phenom kernel: ... value mask: 0000ffffffffffff
May 26 09:42:34 phenom kernel: ... max period: 00007fffffffffff
May 26 09:42:34 phenom kernel: ... fixed-purpose events: 0
May 26 09:42:34 phenom kernel: ... event mask: 000000000000000f
May 26 09:42:34 phenom kernel: process: System has AMD C1E enabled
May 26 09:42:34 phenom kernel: process: Switch to broadcast mode on CPU0
May 26 09:42:34 phenom kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
May 26 09:42:34 phenom kernel: x86: Booting SMP configuration:
May 26 09:42:34 phenom kernel: .... node #0, CPUs: #1
May 26 09:42:34 phenom kernel: process: Switch to broadcast mode on CPU1
May 26 09:42:34 phenom kernel: #2
May 26 09:42:34 phenom kernel: process: Switch to broadcast mode on CPU2
May 26 09:42:34 phenom kernel: #3
May 26 09:42:34 phenom kernel: process: Switch to broadcast mode on CPU3
May 26 09:42:34 phenom kernel: #4
May 26 09:42:34 phenom kernel: process: Switch to broadcast mode on CPU4
May 26 09:42:34 phenom kernel: #5
May 26 09:42:34 phenom kernel: x86: Booted up 1 node, 6 CPUs
May 26 09:42:34 phenom kernel: smpboot: Total of 6 processors activated (39617.54 BogoMIPS)
May 26 09:42:34 phenom kernel: process: Switch to broadcast mode on CPU5
May 26 09:42:34 phenom kernel: devtmpfs: initialized
May 26 09:42:34 phenom kernel: PM: Registering ACPI NVS region [mem 0xcfda0000-0xcfdd0fff] (200704 bytes)
May 26 09:42:34 phenom kernel: pinctrl core: initialized pinctrl subsystem
May 26 09:42:34 phenom kernel: RTC time: 7:42:28, date: 05/26/15
May 26 09:42:34 phenom kernel: NET: Registered protocol family 16
May 26 09:42:34 phenom kernel: cpuidle: using governor ladder
May 26 09:42:34 phenom kernel: cpuidle: using governor menu
May 26 09:42:34 phenom kernel: node 0 link 0: io port [9000, ffff]
May 26 09:42:34 phenom kernel: TOM: 00000000d0000000 aka 3328M
May 26 09:42:34 phenom kernel: Fam 10h mmconf [mem 0xe0000000-0xe00fffff]
May 26 09:42:34 phenom kernel: node 0 link 0: mmio [a0000, bffff]
May 26 09:42:34 phenom kernel: node 0 link 0: mmio [d0000000, dfffffff]
May 26 09:42:34 phenom kernel: node 0 link 0: mmio [f0000000, ffffffff]
May 26 09:42:34 phenom kernel: node 0 link 0: mmio [e0000000, e06fffff] ==> [e0100000, e06fffff]
May 26 09:42:34 phenom kernel: TOM2: 0000000430000000 aka 17152M
May 26 09:42:34 phenom kernel: bus: [bus 00-06] on node 0 link 0
May 26 09:42:34 phenom kernel: bus: 00 [io 0x0000-0xffff]
May 26 09:42:34 phenom kernel: bus: 00 [mem 0x000a0000-0x000bffff]
May 26 09:42:34 phenom kernel: bus: 00 [mem 0xd0000000-0xdfffffff]
May 26 09:42:34 phenom kernel: bus: 00 [mem 0xe0700000-0xffffffff]
May 26 09:42:34 phenom kernel: bus: 00 [mem 0xe0100000-0xe06fffff]
May 26 09:42:34 phenom kernel: bus: 00 [mem 0x430000000-0xfcffffffff]
May 26 09:42:34 phenom kernel: ACPI: bus type PCI registered
May 26 09:42:34 phenom kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
May 26 09:42:34 phenom kernel: PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
May 26 09:42:34 phenom kernel: PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820
May 26 09:42:34 phenom kernel: PCI: Using configuration type 1 for base access
May 26 09:42:34 phenom kernel: mtrr: your CPUs had inconsistent variable MTRR settings
May 26 09:42:34 phenom kernel: mtrr: probably your BIOS does not setup all CPUs.
May 26 09:42:34 phenom kernel: mtrr: corrected configuration.
May 26 09:42:34 phenom kernel: ACPI: Added _OSI(Module Device)
May 26 09:42:34 phenom kernel: ACPI: Added _OSI(Processor Device)
May 26 09:42:34 phenom kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
May 26 09:42:34 phenom kernel: ACPI: Added _OSI(Processor Aggregator Device)
May 26 09:42:34 phenom kernel: ACPI: Actual Package length (1) is larger than NumElements field (0), truncated
May 26 09:42:34 phenom kernel: ACPI: Actual Package length (1) is larger than NumElements field (0), truncated
May 26 09:42:34 phenom kernel: ACPI: Actual Package length (1) is larger than NumElements field (0), truncated
May 26 09:42:34 phenom kernel: ACPI: Actual Package length (1) is larger than NumElements field (0), truncated
May 26 09:42:34 phenom kernel: ACPI: Interpreter enabled
May 26 09:42:34 phenom kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20150204/hwxface-580)
May 26 09:42:34 phenom kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20150204/hwxface-580)
May 26 09:42:34 phenom kernel: ACPI: (supports S0 S3 S4 S5)
May 26 09:42:34 phenom kernel: ACPI: Using IOAPIC for interrupt routing
May 26 09:42:34 phenom kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
May 26 09:42:34 phenom kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
May 26 09:42:34 phenom kernel: acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
May 26 09:42:34 phenom kernel: acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
May 26 09:42:34 phenom kernel: PCI host bridge to bus 0000:00
May 26 09:42:34 phenom kernel: pci_bus 0000:00: root bus resource [bus 00-ff]
May 26 09:42:34 phenom kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7 window]
May 26 09:42:34 phenom kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window]
May 26 09:42:34 phenom kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
May 26 09:42:34 phenom kernel: pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000dffff window]
May 26 09:42:34 phenom kernel: pci_bus 0000:00: root bus resource [mem 0xfed40000-0xfed44fff window]
May 26 09:42:34 phenom kernel: pci_bus 0000:00: root bus resource [mem 0xd0000000-0xfebfffff window]
May 26 09:42:34 phenom kernel: pci 0000:00:00.0: [1002:5a14] type 00 class 0x060000
May 26 09:42:34 phenom kernel: pci 0000:00:00.0: [Firmware Bug]: reg 0x1c: invalid BAR (can't size)
May 26 09:42:34 phenom kernel: pci 0000:00:02.0: [1002:5a16] type 01 class 0x060400
May 26 09:42:34 phenom kernel: pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
May 26 09:42:34 phenom kernel: pci 0000:00:02.0: System wakeup disabled by ACPI
May 26 09:42:34 phenom kernel: pci 0000:00:04.0: [1002:5a18] type 01 class 0x060400
May 26 09:42:34 phenom kernel: pci 0000:00:04.0: PME# supported from D0 D3hot D3cold
May 26 09:42:34 phenom kernel: pci 0000:00:04.0: System wakeup disabled by ACPI
May 26 09:42:34 phenom kernel: pci 0000:00:09.0: [1002:5a1c] type 01 class 0x060400
May 26 09:42:34 phenom kernel: pci 0000:00:09.0: PME# supported from D0 D3hot D3cold
May 26 09:42:34 phenom kernel: pci 0000:00:09.0: System wakeup disabled by ACPI
May 26 09:42:34 phenom kernel: pci 0000:00:0a.0: [1002:5a1d] type 01 class 0x060400
May 26 09:42:34 phenom kernel: pci 0000:00:0a.0: PME# supported from D0 D3hot D3cold
May 26 09:42:34 phenom kernel: pci 0000:00:0a.0: System wakeup disabled by ACPI
May 26 09:42:34 phenom kernel: pci 0000:00:11.0: [1002:4391] type 00 class 0x010601
May 26 09:42:34 phenom kernel: pci 0000:00:11.0: reg 0x10: [io 0xff00-0xff07]
May 26 09:42:34 phenom kernel: pci 0000:00:11.0: reg 0x14: [io 0xfe00-0xfe03]
May 26 09:42:34 phenom kernel: pci 0000:00:11.0: reg 0x18: [io 0xfd00-0xfd07]
May 26 09:42:34 phenom kernel: pci 0000:00:11.0: reg 0x1c: [io 0xfc00-0xfc03]
May 26 09:42:34 phenom kernel: pci 0000:00:11.0: reg 0x20: [io 0xfb00-0xfb0f]
May 26 09:42:34 phenom kernel: pci 0000:00:11.0: reg 0x24: [mem 0xfdfff000-0xfdfff3ff]
May 26 09:42:34 phenom kernel: pci 0000:00:12.0: [1002:4397] type 00 class 0x0c0310
May 26 09:42:34 phenom kernel: pci 0000:00:12.0: reg 0x10: [mem 0xfdffe000-0xfdffefff]
May 26 09:42:34 phenom kernel: pci 0000:00:12.0: System wakeup disabled by ACPI
May 26 09:42:34 phenom kernel: pci 0000:00:12.2: [1002:4396] type 00 class 0x0c0320
May 26 09:42:34 phenom kernel: pci 0000:00:12.2: reg 0x10: [mem 0xfdffd000-0xfdffd0ff]
May 26 09:42:34 phenom kernel: pci 0000:00:12.2: supports D1 D2
May 26 09:42:34 phenom kernel: pci 0000:00:12.2: PME# supported from D0 D1 D2 D3hot
May 26 09:42:34 phenom kernel: pci 0000:00:12.2: System wakeup disabled by ACPI
May 26 09:42:34 phenom kernel: pci 0000:00:13.0: [1002:4397] type 00 class 0x0c0310
May 26 09:42:34 phenom kernel: pci 0000:00:13.0: reg 0x10: [mem 0xfdffc000-0xfdffcfff]
May 26 09:42:34 phenom kernel: pci 0000:00:13.0: System wakeup disabled by ACPI
May 26 09:42:34 phenom kernel: pci 0000:00:13.2: [1002:4396] type 00 class 0x0c0320
May 26 09:42:34 phenom kernel: pci 0000:00:13.2: reg 0x10: [mem 0xfdffb000-0xfdffb0ff]
May 26 09:42:34 phenom kernel: pci 0000:00:13.2: supports D1 D2
May 26 09:42:34 phenom kernel: pci 0000:00:13.2: PME# supported from D0 D1 D2 D3hot
May 26 09:42:34 phenom kernel: pci 0000:00:13.2: System wakeup disabled by ACPI
May 26 09:42:34 phenom kernel: pci 0000:00:14.0: [1002:4385] type 00 class 0x0c0500
May 26 09:42:34 phenom kernel: pci 0000:00:14.1: [1002:439c] type 00 class 0x01018a
May 26 09:42:34 phenom kernel: pci 0000:00:14.1: reg 0x10: [io 0x0000-0x0007]
May 26 09:42:34 phenom kernel: pci 0000:00:14.1: reg 0x14: [io 0x0000-0x0003]
May 26 09:42:34 phenom kernel: pci 0000:00:14.1: reg 0x18: [io 0x0000-0x0007]
May 26 09:42:34 phenom kernel: pci 0000:00:14.1: reg 0x1c: [io 0x0000-0x0003]
May 26 09:42:34 phenom kernel: pci 0000:00:14.1: reg 0x20: [io 0xfa00-0xfa0f]
May 26 09:42:34 phenom kernel: pci 0000:00:14.1: legacy IDE quirk: reg 0x10: [io 0x01f0-0x01f7]
May 26 09:42:34 phenom kernel: pci 0000:00:14.1: legacy IDE quirk: reg 0x14: [io 0x03f6]
May 26 09:42:34 phenom kernel: pci 0000:00:14.1: legacy IDE quirk: reg 0x18: [io 0x0170-0x0177]
May 26 09:42:34 phenom kernel: pci 0000:00:14.1: legacy IDE quirk: reg 0x1c: [io 0x0376]
May 26 09:42:34 phenom kernel: pci 0000:00:14.2: [1002:4383] type 00 class 0x040300
May 26 09:42:34 phenom kernel: pci 0000:00:14.2: reg 0x10: [mem 0xfdff4000-0xfdff7fff 64bit]
May 26 09:42:34 phenom kernel: pci 0000:00:14.2: PME# supported from D0 D3hot D3cold
May 26 09:42:34 phenom kernel: pci 0000:00:14.2: System wakeup disabled by ACPI
May 26 09:42:34 phenom kernel: pci 0000:00:14.3: [1002:439d] type 00 class 0x060100
May 26 09:42:34 phenom kernel: pci 0000:00:14.4: [1002:4384] type 01 class 0x060401
May 26 09:42:34 phenom kernel: pci 0000:00:14.4: System wakeup disabled by ACPI
May 26 09:42:34 phenom kernel: pci 0000:00:14.5: [1002:4399] type 00 class 0x0c0310
May 26 09:42:34 phenom kernel: pci 0000:00:14.5: reg 0x10: [mem 0xfdffa000-0xfdffafff]
May 26 09:42:34 phenom kernel: pci 0000:00:14.5: System wakeup disabled by ACPI
May 26 09:42:34 phenom kernel: pci 0000:00:15.0: [1002:43a0] type 01 class 0x060400
May 26 09:42:34 phenom kernel: pci 0000:00:15.0: supports D1 D2
May 26 09:42:34 phenom kernel: pci 0000:00:15.0: System wakeup disabled by ACPI
May 26 09:42:34 phenom kernel: pci 0000:00:16.0: [1002:4397] type 00 class 0x0c0310
May 26 09:42:34 phenom kernel: pci 0000:00:16.0: reg 0x10: [mem 0xfdff9000-0xfdff9fff]
May 26 09:42:34 phenom kernel: pci 0000:00:16.0: System wakeup disabled by ACPI
May 26 09:42:34 phenom kernel: pci 0000:00:16.2: [1002:4396] type 00 class 0x0c0320
May 26 09:42:34 phenom kernel: pci 0000:00:16.2: reg 0x10: [mem 0xfdff8000-0xfdff80ff]
May 26 09:42:34 phenom kernel: pci 0000:00:16.2: supports D1 D2
May 26 09:42:34 phenom kernel: pci 0000:00:16.2: PME# supported from D0 D1 D2 D3hot
May 26 09:42:34 phenom kernel: pci 0000:00:16.2: System wakeup disabled by ACPI
May 26 09:42:34 phenom kernel: pci 0000:00:18.0: [1022:1200] type 00 class 0x060000
May 26 09:42:34 phenom kernel: pci 0000:00:18.1: [1022:1201] type 00 class 0x060000
May 26 09:42:34 phenom kernel: pci 0000:00:18.2: [1022:1202] type 00 class 0x060000
May 26 09:42:34 phenom kernel: pci 0000:00:18.3: [1022:1203] type 00 class 0x060000
May 26 09:42:34 phenom kernel: pci 0000:00:18.4: [1022:1204] type 00 class 0x060000
May 26 09:42:34 phenom kernel: pci 0000:01:00.0: [1002:6779] type 00 class 0x030000
May 26 09:42:34 phenom kernel: pci 0000:01:00.0: reg 0x10: [mem 0xd0000000-0xdfffffff 64bit pref]
May 26 09:42:34 phenom kernel: pci 0000:01:00.0: reg 0x18: [mem 0xfd5c0000-0xfd5dffff 64bit]
May 26 09:42:34 phenom kernel: pci 0000:01:00.0: reg 0x20: [io 0xce00-0xceff]
May 26 09:42:34 phenom kernel: pci 0000:01:00.0: reg 0x30: [mem 0x00000000-0x0001ffff pref]
May 26 09:42:34 phenom kernel: pci 0000:01:00.0: supports D1 D2
May 26 09:42:34 phenom kernel: pci 0000:01:00.1: [1002:aa98] type 00 class 0x040300
May 26 09:42:34 phenom kernel: pci 0000:01:00.1: reg 0x10: [mem 0xfd5fc000-0xfd5fffff 64bit]
May 26 09:42:34 phenom kernel: pci 0000:01:00.1: supports D1 D2
May 26 09:42:34 phenom kernel: pci 0000:00:02.0: PCI bridge to [bus 01]
May 26 09:42:34 phenom kernel: pci 0000:00:02.0: bridge window [io 0xc000-0xcfff]
May 26 09:42:34 phenom kernel: pci 0000:00:02.0: bridge window [mem 0xfd500000-0xfd5fffff]
May 26 09:42:34 phenom kernel: pci 0000:00:02.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
May 26 09:42:34 phenom kernel: pci 0000:02:00.0: [1b6f:7023] type 00 class 0x0c0330
May 26 09:42:34 phenom kernel: pci 0000:02:00.0: reg 0x10: [mem 0xfd4f8000-0xfd4fffff 64bit]
May 26 09:42:34 phenom kernel: pci 0000:02:00.0: supports D1 D2
May 26 09:42:34 phenom kernel: pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
May 26 09:42:34 phenom kernel: pci 0000:00:04.0: PCI bridge to [bus 02]
May 26 09:42:34 phenom kernel: pci 0000:00:04.0: bridge window [io 0xb000-0xbfff]
May 26 09:42:34 phenom kernel: pci 0000:00:04.0: bridge window [mem 0xfd400000-0xfd4fffff]
May 26 09:42:34 phenom kernel: pci 0000:00:04.0: bridge window [mem 0xfde00000-0xfdefffff 64bit pref]
May 26 09:42:34 phenom kernel: pci 0000:03:00.0: [10ec:8168] type 00 class 0x020000
May 26 09:42:34 phenom kernel: pci 0000:03:00.0: reg 0x10: [io 0xee00-0xeeff]
May 26 09:42:34 phenom kernel: pci 0000:03:00.0: reg 0x18: [mem 0xfdcff000-0xfdcfffff 64bit pref]
May 26 09:42:34 phenom kernel: pci 0000:03:00.0: reg 0x20: [mem 0xfdcf8000-0xfdcfbfff 64bit pref]
May 26 09:42:34 phenom kernel: pci 0000:03:00.0: supports D1 D2
May 26 09:42:34 phenom kernel: pci 0000:03:00.0: PME# supported from D0 D1 D2 D3hot D3cold
May 26 09:42:34 phenom kernel: pci 0000:00:09.0: PCI bridge to [bus 03]
May 26 09:42:34 phenom kernel: pci 0000:00:09.0: bridge window [io 0xe000-0xefff]
May 26 09:42:34 phenom kernel: pci 0000:00:09.0: bridge window [mem 0xfdd00000-0xfddfffff]
May 26 09:42:34 phenom kernel: pci 0000:00:09.0: bridge window [mem 0xfdc00000-0xfdcfffff 64bit pref]
May 26 09:42:34 phenom kernel: pci 0000:04:00.0: [1b6f:7023] type 00 class 0x0c0330
May 26 09:42:34 phenom kernel: pci 0000:04:00.0: reg 0x10: [mem 0xfdbf8000-0xfdbfffff 64bit]
May 26 09:42:34 phenom kernel: pci 0000:04:00.0: supports D1 D2
May 26 09:42:34 phenom kernel: pci 0000:04:00.0: PME# supported from D0 D1 D2 D3hot D3cold
May 26 09:42:34 phenom kernel: pci 0000:00:0a.0: PCI bridge to [bus 04]
May 26 09:42:34 phenom kernel: pci 0000:00:0a.0: bridge window [io 0xd000-0xdfff]
May 26 09:42:34 phenom kernel: pci 0000:00:0a.0: bridge window [mem 0xfdb00000-0xfdbfffff]
May 26 09:42:34 phenom kernel: pci 0000:00:0a.0: bridge window [mem 0xfd800000-0xfd8fffff 64bit pref]
May 26 09:42:34 phenom kernel: pci 0000:05:0e.0: [1106:3044] type 00 class 0x0c0010
May 26 09:42:34 phenom kernel: pci 0000:05:0e.0: reg 0x10: [mem 0xfdaff000-0xfdaff7ff]
May 26 09:42:34 phenom kernel: pci 0000:05:0e.0: reg 0x14: [io 0xaf00-0xaf7f]
May 26 09:42:34 phenom kernel: pci 0000:05:0e.0: supports D2
May 26 09:42:34 phenom kernel: pci 0000:05:0e.0: PME# supported from D2 D3hot D3cold
May 26 09:42:34 phenom kernel: pci 0000:00:14.4: PCI bridge to [bus 05] (subtractive decode)
May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [io 0xa000-0xafff]
May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [mem 0xfda00000-0xfdafffff]
May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [mem 0xfd900000-0xfd9fffff pref]
May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [io 0x0000-0x0cf7 window] (subtractive decode)
May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [io 0x0d00-0xffff window] (subtractive decode)
May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [mem 0x000a0000-0x000bffff window] (subtractive decode)
May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [mem 0x000c0000-0x000dffff window] (subtractive decode)
May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [mem 0xfed40000-0xfed44fff window] (subtractive decode)
May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [mem 0xd0000000-0xfebfffff window] (subtractive decode)
May 26 09:42:34 phenom kernel: pci 0000:00:15.0: PCI bridge to [bus 06]
May 26 09:42:34 phenom kernel: pci 0000:00:15.0: bridge window [io 0x9000-0x9fff]
May 26 09:42:34 phenom kernel: pci 0000:00:15.0: bridge window [mem 0xfd700000-0xfd7fffff]
May 26 09:42:34 phenom kernel: pci 0000:00:15.0: bridge window [mem 0xfd600000-0xfd6fffff 64bit pref]
May 26 09:42:34 phenom kernel: pci_bus 0000:00: on NUMA node 0
May 26 09:42:34 phenom kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 11) *0
May 26 09:42:34 phenom kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 11) *0
May 26 09:42:34 phenom kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 11) *0
May 26 09:42:34 phenom kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 11) *0
May 26 09:42:34 phenom kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11) *0
May 26 09:42:34 phenom kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11) *0
May 26 09:42:34 phenom kernel: ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 5 6 7 10 11) *0
May 26 09:42:34 phenom kernel: ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 10 11) *0
May 26 09:42:34 phenom kernel: vgaarb: setting as boot device: PCI:0000:01:00.0
May 26 09:42:34 phenom kernel: vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
May 26 09:42:34 phenom kernel: vgaarb: loaded
May 26 09:42:34 phenom kernel: vgaarb: bridge control possible 0000:01:00.0
May 26 09:42:34 phenom kernel: PCI: Using ACPI for IRQ routing
May 26 09:42:34 phenom kernel: PCI: pci_cache_line_size set to 64 bytes
May 26 09:42:34 phenom kernel: e820: reserve RAM buffer [mem 0x0009a000-0x0009ffff]
May 26 09:42:34 phenom kernel: e820: reserve RAM buffer [mem 0xcfda0000-0xcfffffff]
May 26 09:42:34 phenom kernel: NetLabel: Initializing
May 26 09:42:34 phenom kernel: NetLabel: domain hash size = 128
May 26 09:42:34 phenom kernel: NetLabel: protocols = UNLABELED CIPSOv4
May 26 09:42:34 phenom kernel: NetLabel: unlabeled traffic allowed by default
May 26 09:42:34 phenom kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
May 26 09:42:34 phenom kernel: hpet0: 3 comparators, 32-bit 14.318180 MHz counter
May 26 09:42:34 phenom kernel: Switched to clocksource hpet
May 26 09:42:34 phenom kernel: pnp: PnP ACPI init
May 26 09:42:34 phenom kernel: system 00:00: [io 0x04d0-0x04d1] has been reserved
May 26 09:42:34 phenom kernel: system 00:00: [io 0x0220-0x0225] has been reserved
May 26 09:42:34 phenom kernel: system 00:00: [io 0x0290-0x0294] has been reserved
May 26 09:42:34 phenom kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
May 26 09:42:34 phenom kernel: pnp 00:01: disabling [mem 0x00000000-0x00000fff window] because it overlaps 0000:01:00.0 BAR 6 [mem 0x00000000-0x0001ffff pref]
May 26 09:42:34 phenom kernel: system 00:01: [io 0x0900-0x091f] has been reserved
May 26 09:42:34 phenom kernel: system 00:01: [io 0x0228-0x022f] has been reserved
May 26 09:42:34 phenom kernel: system 00:01: [io 0x040b] has been reserved
May 26 09:42:34 phenom kernel: system 00:01: [io 0x04d6] has been reserved
May 26 09:42:34 phenom kernel: system 00:01: [io 0x0c00-0x0c01] has been reserved
May 26 09:42:34 phenom kernel: system 00:01: [io 0x0c14] has been reserved
May 26 09:42:34 phenom kernel: system 00:01: [io 0x0c50-0x0c52] has been reserved
May 26 09:42:34 phenom kernel: system 00:01: [io 0x0c6c-0x0c6d] has been reserved
May 26 09:42:34 phenom kernel: system 00:01: [io 0x0c6f] has been reserved
May 26 09:42:34 phenom kernel: system 00:01: [io 0x0cd0-0x0cd1] has been reserved
May 26 09:42:34 phenom kernel: system 00:01: [io 0x0cd2-0x0cd3] has been reserved
May 26 09:42:34 phenom kernel: system 00:01: [io 0x0cd4-0x0cdf] has been reserved
May 26 09:42:34 phenom kernel: system 00:01: [io 0x0800-0x08fe] could not be reserved
May 26 09:42:34 phenom kernel: system 00:01: [io 0x0a10-0x0a17] has been reserved
May 26 09:42:34 phenom kernel: system 00:01: [io 0x0b00-0x0b0f] has been reserved
May 26 09:42:34 phenom kernel: system 00:01: [io 0x0b10-0x0b1f] has been reserved
May 26 09:42:34 phenom kernel: system 00:01: [io 0x0b20-0x0b3f] has been reserved
May 26 09:42:34 phenom kernel: system 00:01: [mem 0xfee00400-0xfee00fff window] has been reserved
May 26 09:42:34 phenom kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
May 26 09:42:34 phenom kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
May 26 09:42:34 phenom kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0501 (active)
May 26 09:42:34 phenom kernel: system 00:04: [mem 0xe0000000-0xefffffff] has been reserved
May 26 09:42:34 phenom kernel: system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
May 26 09:42:34 phenom kernel: system 00:05: [mem 0x000d4200-0x000d7fff] has been reserved
May 26 09:42:34 phenom kernel: system 00:05: [mem 0x000f0000-0x000f7fff] could not be reserved
May 26 09:42:34 phenom kernel: system 00:05: [mem 0x000f8000-0x000fbfff] could not be reserved
May 26 09:42:34 phenom kernel: system 00:05: [mem 0x000fc000-0x000fffff] could not be reserved
May 26 09:42:34 phenom kernel: system 00:05: [mem 0xcfda0000-0xcfdfffff] could not be reserved
May 26 09:42:34 phenom kernel: system 00:05: [mem 0xffff0000-0xffffffff] has been reserved
May 26 09:42:34 phenom kernel: system 00:05: [mem 0x00000000-0x0009ffff] could not be reserved
May 26 09:42:34 phenom kernel: system 00:05: [mem 0x00100000-0xcfd9ffff] could not be reserved
May 26 09:42:34 phenom kernel: system 00:05: [mem 0xcfe00000-0xcfefffff] has been reserved
May 26 09:42:34 phenom kernel: system 00:05: [mem 0xcff00000-0xcfffffff] could not be reserved
May 26 09:42:34 phenom kernel: system 00:05: [mem 0xfec00000-0xfec00fff] could not be reserved
May 26 09:42:34 phenom kernel: system 00:05: [mem 0xfee00000-0xfee00fff] could not be reserved
May 26 09:42:34 phenom kernel: system 00:05: [mem 0xfff80000-0xfffeffff] has been reserved
May 26 09:42:34 phenom kernel: system 00:05: Plug and Play ACPI device, IDs PNP0c01 (active)
May 26 09:42:34 phenom kernel: pnp: PnP ACPI: found 6 devices
May 26 09:42:34 phenom kernel: pci 0000:01:00.0: BAR 6: assigned [mem 0xfd500000-0xfd51ffff pref]
May 26 09:42:34 phenom kernel: pci 0000:00:02.0: PCI bridge to [bus 01]
May 26 09:42:34 phenom kernel: pci 0000:00:02.0: bridge window [io 0xc000-0xcfff]
May 26 09:42:34 phenom kernel: pci 0000:00:02.0: bridge window [mem 0xfd500000-0xfd5fffff]
May 26 09:42:34 phenom kernel: pci 0000:00:02.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
May 26 09:42:34 phenom kernel: pci 0000:00:04.0: PCI bridge to [bus 02]
May 26 09:42:34 phenom kernel: pci 0000:00:04.0: bridge window [io 0xb000-0xbfff]
May 26 09:42:34 phenom kernel: pci 0000:00:04.0: bridge window [mem 0xfd400000-0xfd4fffff]
May 26 09:42:34 phenom kernel: pci 0000:00:04.0: bridge window [mem 0xfde00000-0xfdefffff 64bit pref]
May 26 09:42:34 phenom kernel: pci 0000:00:09.0: PCI bridge to [bus 03]
May 26 09:42:34 phenom kernel: pci 0000:00:09.0: bridge window [io 0xe000-0xefff]
May 26 09:42:34 phenom kernel: pci 0000:00:09.0: bridge window [mem 0xfdd00000-0xfddfffff]
May 26 09:42:34 phenom kernel: pci 0000:00:09.0: bridge window [mem 0xfdc00000-0xfdcfffff 64bit pref]
May 26 09:42:34 phenom kernel: pci 0000:00:0a.0: PCI bridge to [bus 04]
May 26 09:42:34 phenom kernel: pci 0000:00:0a.0: bridge window [io 0xd000-0xdfff]
May 26 09:42:34 phenom kernel: pci 0000:00:0a.0: bridge window [mem 0xfdb00000-0xfdbfffff]
May 26 09:42:34 phenom kernel: pci 0000:00:0a.0: bridge window [mem 0xfd800000-0xfd8fffff 64bit pref]
May 26 09:42:34 phenom kernel: pci 0000:00:14.4: PCI bridge to [bus 05]
May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [io 0xa000-0xafff]
May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [mem 0xfda00000-0xfdafffff]
May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [mem 0xfd900000-0xfd9fffff pref]
May 26 09:42:34 phenom kernel: pci 0000:00:15.0: PCI bridge to [bus 06]
May 26 09:42:34 phenom kernel: pci 0000:00:15.0: bridge window [io 0x9000-0x9fff]
May 26 09:42:34 phenom kernel: pci 0000:00:15.0: bridge window [mem 0xfd700000-0xfd7fffff]
May 26 09:42:34 phenom kernel: pci 0000:00:15.0: bridge window [mem 0xfd600000-0xfd6fffff 64bit pref]
May 26 09:42:34 phenom kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7 window]
May 26 09:42:34 phenom kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff window]
May 26 09:42:34 phenom kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
May 26 09:42:34 phenom kernel: pci_bus 0000:00: resource 7 [mem 0x000c0000-0x000dffff window]
May 26 09:42:34 phenom kernel: pci_bus 0000:00: resource 8 [mem 0xfed40000-0xfed44fff window]
May 26 09:42:34 phenom kernel: pci_bus 0000:00: resource 9 [mem 0xd0000000-0xfebfffff window]
May 26 09:42:34 phenom kernel: pci_bus 0000:01: resource 0 [io 0xc000-0xcfff]
May 26 09:42:34 phenom kernel: pci_bus 0000:01: resource 1 [mem 0xfd500000-0xfd5fffff]
May 26 09:42:34 phenom kernel: pci_bus 0000:01: resource 2 [mem 0xd0000000-0xdfffffff 64bit pref]
May 26 09:42:34 phenom kernel: pci_bus 0000:02: resource 0 [io 0xb000-0xbfff]
May 26 09:42:34 phenom kernel: pci_bus 0000:02: resource 1 [mem 0xfd400000-0xfd4fffff]
May 26 09:42:34 phenom kernel: pci_bus 0000:02: resource 2 [mem 0xfde00000-0xfdefffff 64bit pref]
May 26 09:42:34 phenom kernel: pci_bus 0000:03: resource 0 [io 0xe000-0xefff]
May 26 09:42:34 phenom kernel: pci_bus 0000:03: resource 1 [mem 0xfdd00000-0xfddfffff]
May 26 09:42:34 phenom kernel: pci_bus 0000:03: resource 2 [mem 0xfdc00000-0xfdcfffff 64bit pref]
May 26 09:42:34 phenom kernel: pci_bus 0000:04: resource 0 [io 0xd000-0xdfff]
May 26 09:42:34 phenom kernel: pci_bus 0000:04: resource 1 [mem 0xfdb00000-0xfdbfffff]
May 26 09:42:34 phenom kernel: pci_bus 0000:04: resource 2 [mem 0xfd800000-0xfd8fffff 64bit pref]
May 26 09:42:34 phenom kernel: pci_bus 0000:05: resource 0 [io 0xa000-0xafff]
May 26 09:42:34 phenom kernel: pci_bus 0000:05: resource 1 [mem 0xfda00000-0xfdafffff]
May 26 09:42:34 phenom kernel: pci_bus 0000:05: resource 2 [mem 0xfd900000-0xfd9fffff pref]
May 26 09:42:34 phenom kernel: pci_bus 0000:05: resource 4 [io 0x0000-0x0cf7 window]
May 26 09:42:34 phenom kernel: pci_bus 0000:05: resource 5 [io 0x0d00-0xffff window]
May 26 09:42:34 phenom kernel: pci_bus 0000:05: resource 6 [mem 0x000a0000-0x000bffff window]
May 26 09:42:34 phenom kernel: pci_bus 0000:05: resource 7 [mem 0x000c0000-0x000dffff window]
May 26 09:42:34 phenom kernel: pci_bus 0000:05: resource 8 [mem 0xfed40000-0xfed44fff window]
May 26 09:42:34 phenom kernel: pci_bus 0000:05: resource 9 [mem 0xd0000000-0xfebfffff window]
May 26 09:42:34 phenom kernel: pci_bus 0000:06: resource 0 [io 0x9000-0x9fff]
May 26 09:42:34 phenom kernel: pci_bus 0000:06: resource 1 [mem 0xfd700000-0xfd7fffff]
May 26 09:42:34 phenom kernel: pci_bus 0000:06: resource 2 [mem 0xfd600000-0xfd6fffff 64bit pref]
May 26 09:42:34 phenom kernel: NET: Registered protocol family 2
May 26 09:42:34 phenom kernel: TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
May 26 09:42:34 phenom kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
May 26 09:42:34 phenom kernel: TCP: Hash tables configured (established 131072 bind 65536)
May 26 09:42:34 phenom kernel: TCP: reno registered
May 26 09:42:34 phenom kernel: UDP hash table entries: 8192 (order: 6, 262144 bytes)
May 26 09:42:34 phenom kernel: UDP-Lite hash table entries: 8192 (order: 6, 262144 bytes)
May 26 09:42:34 phenom kernel: NET: Registered protocol family 1
May 26 09:42:34 phenom kernel: pci 0000:01:00.0: Video device with shadowed ROM
May 26 09:42:34 phenom kernel: PCI: CLS 64 bytes, default 64
May 26 09:42:34 phenom kernel: Unpacking initramfs...
May 26 09:42:34 phenom kernel: Freeing initrd memory: 14980K (ffff8800362ae000 - ffff88003714f000)
May 26 09:42:34 phenom kernel: PCI-DMA: Disabling AGP.
May 26 09:42:34 phenom kernel: PCI-DMA: aperture base @ c4000000 size 65536 KB
May 26 09:42:34 phenom kernel: PCI-DMA: using GART IOMMU.
May 26 09:42:34 phenom kernel: PCI-DMA: Reserving 64MB of IOMMU area in the AGP aperture
May 26 09:42:34 phenom kernel: microcode: CPU0: patch_level=0x010000bf
May 26 09:42:34 phenom kernel: microcode: CPU1: patch_level=0x010000bf
May 26 09:42:34 phenom kernel: microcode: CPU2: patch_level=0x010000bf
May 26 09:42:34 phenom kernel: microcode: CPU3: patch_level=0x010000bf
May 26 09:42:34 phenom kernel: microcode: CPU4: patch_level=0x010000bf
May 26 09:42:34 phenom kernel: microcode: CPU5: patch_level=0x010000bf
May 26 09:42:34 phenom kernel: microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
May 26 09:42:34 phenom kernel: LVT offset 1 assigned for vector 0x400
May 26 09:42:34 phenom kernel: IBS: LVT offset 1 assigned
May 26 09:42:34 phenom kernel: perf: AMD IBS detected (0x0000001f)
May 26 09:42:34 phenom kernel: Scanning for low memory corruption every 60 seconds
May 26 09:42:34 phenom kernel: futex hash table entries: 2048 (order: 5, 131072 bytes)
May 26 09:42:34 phenom kernel: Initialise system trusted keyring
May 26 09:42:34 phenom kernel: HugeTLB registered 2 MB page size, pre-allocated 0 pages
May 26 09:42:34 phenom kernel: zpool: loaded
May 26 09:42:34 phenom kernel: zbud: loaded
May 26 09:42:34 phenom kernel: VFS: Disk quotas dquot_6.5.2
May 26 09:42:34 phenom kernel: VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
May 26 09:42:34 phenom kernel: Key type big_key registered
May 26 09:42:34 phenom kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
May 26 09:42:34 phenom kernel: io scheduler noop registered
May 26 09:42:34 phenom kernel: io scheduler deadline registered
May 26 09:42:34 phenom kernel: io scheduler cfq registered (default)
May 26 09:42:34 phenom kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
May 26 09:42:34 phenom kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
May 26 09:42:34 phenom kernel: vesafb: mode is 1600x1200x32, linelength=6400, pages=0
May 26 09:42:34 phenom kernel: vesafb: scrolling: redraw
May 26 09:42:34 phenom kernel: vesafb: Truecolor: size=0:8:8:8, shift=0:16:8:0
May 26 09:42:34 phenom kernel: vesafb: framebuffer at 0xd0000000, mapped to 0xffffc90011c00000, using 7552k, total 7552k
May 26 09:42:34 phenom kernel: Console: switching to colour frame buffer device 200x75
May 26 09:42:34 phenom kernel: fb0: VESA VGA frame buffer device
May 26 09:42:34 phenom kernel: GHES: HEST is not enabled!
May 26 09:42:34 phenom kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
May 26 09:42:34 phenom kernel: 00:03: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
May 26 09:42:34 phenom kernel: Linux agpgart interface v0.103
May 26 09:42:34 phenom kernel: rtc_cmos 00:02: RTC can wake from S4
May 26 09:42:34 phenom kernel: rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
May 26 09:42:34 phenom kernel: rtc_cmos 00:02: alarms up to one month, 242 bytes nvram, hpet irqs
May 26 09:42:34 phenom kernel: rtc-cmos: BIOS has alarm-disable quirk.
May 26 09:42:34 phenom kernel: RTC alarms disabled
May 26 09:42:34 phenom kernel: ledtrig-cpu: registered to indicate activity on CPUs
May 26 09:42:34 phenom kernel: TCP: cubic registered
May 26 09:42:34 phenom kernel: NET: Registered protocol family 10
May 26 09:42:34 phenom kernel: NET: Registered protocol family 17
May 26 09:42:34 phenom kernel: Loading compiled-in X.509 certificates
May 26 09:42:34 phenom kernel: registered taskstats version 1
May 26 09:42:34 phenom kernel: Magic number: 15:372:724
May 26 09:42:34 phenom kernel: rtc_cmos 00:02: setting system clock to 2015-05-26 07:42:29 UTC (1432626149)
May 26 09:42:34 phenom kernel: PM: Hibernation image not present or could not be loaded.
May 26 09:42:34 phenom kernel: Freeing unused kernel memory: 1160K (ffffffff818d4000 - ffffffff819f6000)
May 26 09:42:34 phenom kernel: Write protecting the kernel read-only data: 8192k
May 26 09:42:34 phenom kernel: Freeing unused kernel memory: 504K (ffff880001582000 - ffff880001600000)
May 26 09:42:34 phenom kernel: Freeing unused kernel memory: 264K (ffff8800017be000 - ffff880001800000)
May 26 09:42:34 phenom kernel: random: systemd-tmpfile urandom read with 3 bits of entropy available
May 26 09:42:34 phenom kernel: [drm] Initialized drm 1.1.0 20060810
May 26 09:42:34 phenom kernel: [drm] radeon kernel modesetting enabled.
May 26 09:42:34 phenom kernel: checking generic (d0000000 760000) vs hw (d0000000 10000000)
May 26 09:42:34 phenom kernel: fb: switching to radeondrmfb from VESA VGA
May 26 09:42:34 phenom kernel: Console: switching to colour dummy device 80x25
May 26 09:42:34 phenom kernel: [drm] initializing kernel modesetting (CAICOS 0x1002:0x6779 0x1043:0x0483).
May 26 09:42:34 phenom kernel: [drm] register mmio base: 0xFD5C0000
May 26 09:42:34 phenom kernel: [drm] register mmio size: 131072
May 26 09:42:34 phenom kernel: ATOM BIOS: 6779.13.12.0.45.AS01
May 26 09:42:34 phenom kernel: radeon 0000:01:00.0: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF (1024M used)
May 26 09:42:34 phenom kernel: radeon 0000:01:00.0: GTT: 1024M 0x0000000040000000 - 0x000000007FFFFFFF
May 26 09:42:34 phenom kernel: [drm] Detected VRAM RAM=1024M, BAR=256M
May 26 09:42:34 phenom kernel: [drm] RAM width 64bits DDR
May 26 09:42:34 phenom kernel: [TTM] Zone kernel: Available graphics memory: 8217894 kiB
May 26 09:42:34 phenom kernel: [TTM] Zone dma32: Available graphics memory: 2097152 kiB
May 26 09:42:34 phenom kernel: [TTM] Initializing pool allocator
May 26 09:42:34 phenom kernel: [TTM] Initializing DMA pool allocator
May 26 09:42:34 phenom kernel: [drm] radeon: 1024M of VRAM memory ready
May 26 09:42:34 phenom kernel: [drm] radeon: 1024M of GTT memory ready.
May 26 09:42:34 phenom kernel: [drm] Loading CAICOS Microcode
May 26 09:42:34 phenom kernel: [drm] Internal thermal controller without fan control
May 26 09:42:34 phenom kernel: [drm] radeon: dpm initialized
May 26 09:42:34 phenom kernel: [drm] GART: num cpu pages 262144, num gpu pages 262144
May 26 09:42:34 phenom kernel: [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0
May 26 09:42:34 phenom kernel: [drm] PCIE GART of 1024M enabled (table at 0x0000000000274000).
May 26 09:42:34 phenom kernel: radeon 0000:01:00.0: WB enabled
May 26 09:42:34 phenom kernel: radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff88041a0cdc00
May 26 09:42:34 phenom kernel: radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff88041a0cdc0c
May 26 09:42:34 phenom kernel: radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000072118 and cpu addr 0xffffc900126b2118
May 26 09:42:34 phenom kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
May 26 09:42:34 phenom kernel: [drm] Driver supports precise vblank timestamp query.
May 26 09:42:34 phenom kernel: radeon 0000:01:00.0: radeon: MSI limited to 32-bit
May 26 09:42:34 phenom kernel: radeon 0000:01:00.0: radeon: using MSI.
May 26 09:42:34 phenom kernel: [drm] radeon: irq initialized.
May 26 09:42:34 phenom kernel: [drm] ring test on 0 succeeded in 2 usecs
May 26 09:42:34 phenom kernel: [drm] ring test on 3 succeeded in 7 usecs
May 26 09:42:34 phenom kernel: [drm] ring test on 5 succeeded in 2 usecs
May 26 09:42:34 phenom kernel: [drm] UVD initialized successfully.
May 26 09:42:34 phenom kernel: [drm] ib test on ring 0 succeeded in 0 usecs
May 26 09:42:34 phenom kernel: [drm] ib test on ring 3 succeeded in 0 usecs
May 26 09:42:34 phenom kernel: [drm] ib test on ring 5 succeeded
May 26 09:42:34 phenom kernel: [drm] Radeon Display Connectors
May 26 09:42:34 phenom kernel: [drm] Connector 0:
May 26 09:42:34 phenom kernel: [drm] HDMI-A-1
May 26 09:42:34 phenom kernel: [drm] HPD1
May 26 09:42:34 phenom kernel: [drm] DDC: 0x6460 0x6460 0x6464 0x6464 0x6468 0x6468 0x646c 0x646c
May 26 09:42:34 phenom kernel: [drm] Encoders:
May 26 09:42:34 phenom kernel: [drm] DFP1: INTERNAL_UNIPHY1
May 26 09:42:34 phenom kernel: [drm] Connector 1:
May 26 09:42:34 phenom kernel: [drm] DVI-D-1
May 26 09:42:34 phenom kernel: [drm] HPD4
May 26 09:42:34 phenom kernel: [drm] DDC: 0x6450 0x6450 0x6454 0x6454 0x6458 0x6458 0x645c 0x645c
May 26 09:42:34 phenom kernel: [drm] Encoders:
May 26 09:42:34 phenom kernel: [drm] DFP2: INTERNAL_UNIPHY
May 26 09:42:34 phenom kernel: [drm] Connector 2:
May 26 09:42:34 phenom kernel: [drm] VGA-1
May 26 09:42:34 phenom kernel: [drm] DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 0x643c 0x643c
May 26 09:42:34 phenom kernel: [drm] Encoders:
May 26 09:42:34 phenom kernel: [drm] CRT1: INTERNAL_KLDSCP_DAC1
May 26 09:42:34 phenom kernel: tsc: Refined TSC clocksource calibration: 3300.098 MHz
May 26 09:42:34 phenom kernel: [drm] fb mappable at 0xD0475000
May 26 09:42:34 phenom kernel: [drm] vram apper at 0xD0000000
May 26 09:42:34 phenom kernel: [drm] size 9216000
May 26 09:42:34 phenom kernel: [drm] fb depth is 24
May 26 09:42:34 phenom kernel: [drm] pitch is 7680
May 26 09:42:34 phenom kernel: fbcon: radeondrmfb (fb0) is primary device
May 26 09:42:34 phenom kernel: Console: switching to colour frame buffer device 240x75
May 26 09:42:34 phenom kernel: radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device
May 26 09:42:34 phenom kernel: radeon 0000:01:00.0: registered panic notifier
May 26 09:42:34 phenom kernel: [drm] Initialized radeon 2.41.0 20080528 for 0000:01:00.0 on minor 0
May 26 09:42:34 phenom kernel: wmi: Mapper loaded
May 26 09:42:34 phenom kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
May 26 09:42:34 phenom kernel: ACPI: Power Button [PWRB]
May 26 09:42:34 phenom kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
May 26 09:42:34 phenom kernel: ACPI: Power Button [PWRF]
May 26 09:42:34 phenom kernel: MXM: GUID detected in BIOS
May 26 09:42:34 phenom kernel: i8042: PNP: No PS/2 controller found. Probing ports directly.
May 26 09:42:34 phenom kernel: i8042: Failed to disable AUX port, but continuing anyway... Is this a SiS?
May 26 09:42:34 phenom kernel: i8042: If AUX port is really absent please use the 'i8042.noaux' option
May 26 09:42:34 phenom kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
May 26 09:42:34 phenom kernel: ACPI: bus type USB registered
May 26 09:42:34 phenom kernel: usbcore: registered new interface driver usbfs
May 26 09:42:34 phenom kernel: SCSI subsystem initialized
May 26 09:42:34 phenom kernel: usbcore: registered new interface driver hub
May 26 09:42:34 phenom kernel: usbcore: registered new device driver usb
May 26 09:42:34 phenom kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
May 26 09:42:34 phenom kernel: ehci-pci: EHCI PCI platform driver
May 26 09:42:34 phenom kernel: QUIRK: Enable AMD PLL fix
May 26 09:42:34 phenom kernel: ehci-pci 0000:00:12.2: EHCI Host Controller
May 26 09:42:34 phenom kernel: ehci-pci 0000:00:12.2: new USB bus registered, assigned bus number 1
May 26 09:42:34 phenom kernel: ehci-pci 0000:00:12.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround
May 26 09:42:34 phenom kernel: ehci-pci 0000:00:12.2: debug port 1
May 26 09:42:34 phenom kernel: ehci-pci 0000:00:12.2: irq 17, io mem 0xfdffd000
May 26 09:42:34 phenom kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
May 26 09:42:34 phenom kernel: ohci-pci: OHCI PCI platform driver
May 26 09:42:34 phenom kernel: libata version 3.00 loaded.
May 26 09:42:34 phenom kernel: ehci-pci 0000:00:12.2: USB 2.0 started, EHCI 1.00
May 26 09:42:34 phenom kernel: hub 1-0:1.0: USB hub found
May 26 09:42:34 phenom kernel: hub 1-0:1.0: 5 ports detected
May 26 09:42:34 phenom kernel: xhci_hcd 0000:02:00.0: xHCI Host Controller
May 26 09:42:34 phenom kernel: xhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 2
May 26 09:42:34 phenom kernel: xhci_hcd 0000:02:00.0: hcc params 0x040050af hci version 0x100 quirks 0x00080490
May 26 09:42:34 phenom kernel: hub 2-0:1.0: USB hub found
May 26 09:42:34 phenom kernel: hub 2-0:1.0: 2 ports detected
May 26 09:42:34 phenom kernel: xhci_hcd 0000:02:00.0: xHCI Host Controller
May 26 09:42:34 phenom kernel: xhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 3
May 26 09:42:34 phenom kernel: ehci-pci 0000:00:13.2: EHCI Host Controller
May 26 09:42:34 phenom kernel: hub 3-0:1.0: USB hub found
May 26 09:42:34 phenom kernel: hub 3-0:1.0: 2 ports detected
May 26 09:42:34 phenom kernel: ehci-pci 0000:00:13.2: new USB bus registered, assigned bus number 4
May 26 09:42:34 phenom kernel: ehci-pci 0000:00:13.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround
May 26 09:42:34 phenom kernel: ehci-pci 0000:00:13.2: debug port 1
May 26 09:42:34 phenom kernel: ehci-pci 0000:00:13.2: irq 17, io mem 0xfdffb000
May 26 09:42:34 phenom kernel: ehci-pci 0000:00:13.2: USB 2.0 started, EHCI 1.00
May 26 09:42:34 phenom kernel: hub 4-0:1.0: USB hub found
May 26 09:42:34 phenom kernel: hub 4-0:1.0: 5 ports detected
May 26 09:42:34 phenom kernel: xhci_hcd 0000:04:00.0: xHCI Host Controller
May 26 09:42:34 phenom kernel: xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 5
May 26 09:42:34 phenom kernel: xhci_hcd 0000:04:00.0: hcc params 0x040050af hci version 0x100 quirks 0x00080490
May 26 09:42:34 phenom kernel: hub 5-0:1.0: USB hub found
May 26 09:42:34 phenom kernel: hub 5-0:1.0: 2 ports detected
May 26 09:42:34 phenom kernel: xhci_hcd 0000:04:00.0: xHCI Host Controller
May 26 09:42:34 phenom kernel: xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 6
May 26 09:42:34 phenom kernel: ehci-pci 0000:00:16.2: EHCI Host Controller
May 26 09:42:34 phenom kernel: hub 6-0:1.0: USB hub found
May 26 09:42:34 phenom kernel: hub 6-0:1.0: 2 ports detected
May 26 09:42:34 phenom kernel: ehci-pci 0000:00:16.2: new USB bus registered, assigned bus number 7
May 26 09:42:34 phenom kernel: ehci-pci 0000:00:16.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround
May 26 09:42:34 phenom kernel: ehci-pci 0000:00:16.2: debug port 1
May 26 09:42:34 phenom kernel: ehci-pci 0000:00:16.2: irq 17, io mem 0xfdff8000
May 26 09:42:34 phenom kernel: ehci-pci 0000:00:16.2: USB 2.0 started, EHCI 1.00
May 26 09:42:34 phenom kernel: hub 7-0:1.0: USB hub found
May 26 09:42:34 phenom kernel: hub 7-0:1.0: 4 ports detected
May 26 09:42:34 phenom kernel: ohci-pci 0000:00:12.0: OHCI PCI host controller
May 26 09:42:34 phenom kernel: ohci-pci 0000:00:12.0: new USB bus registered, assigned bus number 8
May 26 09:42:34 phenom kernel: ohci-pci 0000:00:12.0: irq 18, io mem 0xfdffe000
May 26 09:42:34 phenom kernel: firewire_ohci 0000:05:0e.0: added OHCI v1.10 device as card 0, 4 IR + 8 IT contexts, quirks 0x11
May 26 09:42:34 phenom kernel: hub 8-0:1.0: USB hub found
May 26 09:42:34 phenom kernel: hub 8-0:1.0: 5 ports detected
May 26 09:42:34 phenom kernel: ohci-pci 0000:00:13.0: OHCI PCI host controller
May 26 09:42:34 phenom kernel: ohci-pci 0000:00:13.0: new USB bus registered, assigned bus number 9
May 26 09:42:34 phenom kernel: ohci-pci 0000:00:13.0: irq 18, io mem 0xfdffc000
May 26 09:42:34 phenom kernel: hub 9-0:1.0: USB hub found
May 26 09:42:34 phenom kernel: hub 9-0:1.0: 5 ports detected
May 26 09:42:34 phenom kernel: ohci-pci 0000:00:14.5: OHCI PCI host controller
May 26 09:42:34 phenom kernel: ohci-pci 0000:00:14.5: new USB bus registered, assigned bus number 10
May 26 09:42:34 phenom kernel: ohci-pci 0000:00:14.5: irq 18, io mem 0xfdffa000
May 26 09:42:34 phenom kernel: hub 10-0:1.0: USB hub found
May 26 09:42:34 phenom kernel: hub 10-0:1.0: 2 ports detected
May 26 09:42:34 phenom kernel: ohci-pci 0000:00:16.0: OHCI PCI host controller
May 26 09:42:34 phenom kernel: ohci-pci 0000:00:16.0: new USB bus registered, assigned bus number 11
May 26 09:42:34 phenom kernel: ohci-pci 0000:00:16.0: irq 18, io mem 0xfdff9000
May 26 09:42:34 phenom kernel: hub 11-0:1.0: USB hub found
May 26 09:42:34 phenom kernel: hub 11-0:1.0: 4 ports detected
May 26 09:42:34 phenom kernel: scsi host0: pata_atiixp
May 26 09:42:34 phenom kernel: scsi host1: pata_atiixp
May 26 09:42:34 phenom kernel: ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xfa00 irq 14
May 26 09:42:34 phenom kernel: ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xfa08 irq 15
May 26 09:42:34 phenom kernel: ahci 0000:00:11.0: version 3.0
May 26 09:42:34 phenom kernel: ahci 0000:00:11.0: AHCI 0001.0200 32 slots 4 ports 6 Gbps 0xf impl SATA mode
May 26 09:42:34 phenom kernel: ahci 0000:00:11.0: flags: 64bit ncq sntf ilck pm led clo pmp pio slum part
May 26 09:42:34 phenom kernel: scsi host2: ahci
May 26 09:42:34 phenom kernel: scsi host3: ahci
May 26 09:42:34 phenom kernel: scsi host4: ahci
May 26 09:42:34 phenom kernel: scsi host5: ahci
May 26 09:42:34 phenom kernel: ata3: SATA max UDMA/133 abar m1024@0xfdfff000 port 0xfdfff100 irq 19
May 26 09:42:34 phenom kernel: ata4: SATA max UDMA/133 abar m1024@0xfdfff000 port 0xfdfff180 irq 19
May 26 09:42:34 phenom kernel: ata5: SATA max UDMA/133 abar m1024@0xfdfff000 port 0xfdfff200 irq 19
May 26 09:42:34 phenom kernel: ata6: SATA max UDMA/133 abar m1024@0xfdfff000 port 0xfdfff280 irq 19
May 26 09:42:34 phenom kernel: usb 1-1: new high-speed USB device number 2 using ehci-pci
May 26 09:42:34 phenom kernel: usb 2-2: new high-speed USB device number 2 using xhci_hcd
May 26 09:42:34 phenom kernel: usb 7-4: new high-speed USB device number 2 using ehci-pci
May 26 09:42:34 phenom kernel: ata1.01: ATAPI: PLEXTOR DVDR PX-820A, 1.00, max UDMA/66
May 26 09:42:34 phenom kernel: ata1.01: limited to UDMA/33 due to 40-wire cable
May 26 09:42:34 phenom kernel: hub 1-1:1.0: USB hub found
May 26 09:42:34 phenom kernel: hub 1-1:1.0: 4 ports detected
May 26 09:42:34 phenom kernel: ata1.01: configured for UDMA/33
May 26 09:42:34 phenom kernel: scsi 0:0:1:0: CD-ROM PLEXTOR DVDR PX-820A 1.00 PQ: 0 ANSI: 5
May 26 09:42:34 phenom kernel: firewire_core 0000:05:0e.0: created device fw0: GUID 0049e55059f30500, S400
May 26 09:42:34 phenom kernel: ata3: SATA link down (SStatus 0 SControl 300)
May 26 09:42:34 phenom kernel: ata4: SATA link down (SStatus 0 SControl 300)
May 26 09:42:34 phenom kernel: Switched to clocksource tsc
May 26 09:42:34 phenom kernel: usb 1-1.1: new low-speed USB device number 3 using ehci-pci
May 26 09:42:34 phenom kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
May 26 09:42:34 phe

Hi,
I have exactly the same problem. systemd-logind sporadically fails to start, therefore preventing the login prompt to appear. Resetting the machine is the only solution in that case. Most of the time, the system start works without problems though. Here are a few relevant lines from my logs:
# journalctl --unit=systemd-logind | grep -C50 'Connection timed out'
-- Reboot --
Apr 22 10:16:36 deltaflyer systemd[1]: Starting Login Service...
Apr 22 10:17:01 deltaflyer systemd-logind[377]: Failed to enable subscription: Connection timed out
Apr 22 10:17:01 deltaflyer systemd-logind[377]: Failed to fully start up daemon: Connection timed out
Apr 22 10:17:01 deltaflyer systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
Apr 22 10:17:01 deltaflyer systemd[1]: Failed to start Login Service.
Apr 22 10:17:01 deltaflyer systemd[1]: Unit systemd-logind.service entered failed state.
Apr 22 10:17:01 deltaflyer systemd[1]: systemd-logind.service failed.
Apr 22 10:17:01 deltaflyer systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
-- Reboot --
Here is relevant output from the complete log (not only systemd-logind):
# journalctl | grep -C10 'Connection timed out'
Apr 22 10:17:01 deltaflyer dbus[389]: [system] Successfully activated service 'org.freedesktop.systemd1'
Apr 22 10:17:01 deltaflyer NetworkManager[387]: <info> NetworkManager (version 1.0.0) is starting...
Apr 22 10:17:01 deltaflyer acpid[386]: starting up with netlink and the input layer
Apr 22 10:17:01 deltaflyer smartd[381]: Unable to monitor any SMART enabled devices. Try debug (-d) option. Exiting...
Apr 22 10:17:01 deltaflyer /usr/bin/gpm[390]: imps2: Auto-detected intellimouse PS/2
Apr 22 10:17:01 deltaflyer dbus[389]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service'
Apr 22 10:17:01 deltaflyer NetworkManager[387]: <info> Read config: /etc/NetworkManager/NetworkManager.conf
Apr 22 10:17:01 deltaflyer NetworkManager[387]: <info> WEXT support is enabled
Apr 22 10:16:36 deltaflyer systemd[1]: Starting Virtual console mouse server...
Apr 22 10:16:36 deltaflyer systemd[1]: Started D-Bus System Message Bus.
Apr 22 10:17:01 deltaflyer systemd-logind[377]: Failed to enable subscription: Connection timed out
Apr 22 10:17:01 deltaflyer systemd-logind[377]: Failed to fully start up daemon: Connection timed out
Apr 22 10:17:01 deltaflyer systemd[1]: Failed to register name: Connection timed out
Apr 22 10:17:01 deltaflyer systemd[1]: Failed to set up API bus: Connection timed out
Apr 22 10:17:01 deltaflyer systemd[1]: Starting D-Bus System Message Bus...
Apr 22 10:17:01 deltaflyer systemd[1]: Started LVM2 PV scan on device 254:0.
Apr 22 10:17:01 deltaflyer lvm[320]: 7 logical volume(s) in volume group "deltaflyer" now active
Apr 22 10:17:01 deltaflyer dbus[389]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service'
Apr 22 10:17:01 deltaflyer acpid[386]: 1 rule loaded
Apr 22 10:17:01 deltaflyer acpid[386]: waiting for events: event logging is off
Apr 22 10:17:01 deltaflyer NetworkManager[387]: <info> VPN: loaded org.freedesktop.NetworkManager.openvpn
Apr 22 10:17:01 deltaflyer NetworkManager[387]: <info> Loaded plugin keyfile: (c) 2007 - 2013 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
Apr 22 10:17:01 deltaflyer systemd[1]: Started Restore Sound Card State.
Mai 11 11:20:56 deltaflyer acpid[638]: starting up with netlink and the input layer
Mai 11 11:20:56 deltaflyer smartd[640]: Monitoring 1 ATA and 0 SCSI devices
Mai 11 11:20:56 deltaflyer /usr/bin/gpm[637]: imps2: Auto-detected intellimouse PS/2
Mai 11 11:20:56 deltaflyer dbus[642]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service'
Mai 11 11:20:56 deltaflyer NetworkManager[633]: <info> Read config: /etc/NetworkManager/NetworkManager.conf
Mai 11 11:20:56 deltaflyer NetworkManager[633]: <info> WEXT support is enabled
Mai 11 11:20:56 deltaflyer dbus[642]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service'
Mai 11 11:20:56 deltaflyer acpid[638]: 1 rule loaded
Mai 11 11:20:56 deltaflyer acpid[638]: waiting for events: event logging is off
Mai 11 11:20:31 deltaflyer systemd[1]: Started D-Bus System Message Bus.
Mai 11 11:20:56 deltaflyer systemd-logind[634]: Failed to enable subscription: Connection timed out
Mai 11 11:20:56 deltaflyer systemd-logind[634]: Failed to fully start up daemon: Connection timed out
Mai 11 11:20:56 deltaflyer systemd[1]: Failed to register name: Connection timed out
Mai 11 11:20:56 deltaflyer systemd[1]: Failed to set up API bus: Connection timed out
Mai 11 11:20:56 deltaflyer systemd[1]: Starting D-Bus System Message Bus...
Mai 11 11:20:56 deltaflyer systemd[1]: Started Manage Sound Card State (restore and store).
Mai 11 11:20:56 deltaflyer systemd[1]: Starting Restore Sound Card State...
Mai 11 11:20:56 deltaflyer systemd[1]: Started Daily man-db cache update.
Mai 11 11:20:56 deltaflyer systemd[1]: Starting Daily man-db cache update.
Mai 11 11:20:56 deltaflyer systemd[1]: Started Daily verification of password and group files.
Mai 11 11:20:56 deltaflyer systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
Mai 11 11:20:56 deltaflyer systemd[1]: Failed to start Login Service.
Mai 11 11:20:56 deltaflyer systemd[1]: Unit systemd-logind.service entered failed state.
Mai 11 11:20:56 deltaflyer systemd[1]: systemd-logind.service failed.
Mai 27 16:47:34 deltaflyer smartd[399]: Device: /dev/sda [SAT], VBOX HARDDISK, S/N:VB9c7c4cff-f1cdf11a, FW:1.0, 500 GB
Mai 27 16:47:34 deltaflyer smartd[399]: Device: /dev/sda [SAT], not found in smartd database.
Mai 27 16:47:34 deltaflyer smartd[399]: Device: /dev/sda [SAT], lacks SMART capability
Mai 27 16:47:34 deltaflyer smartd[399]: Device: /dev/sda [SAT], to proceed anyway, use '-T permissive' Directive.
Mai 27 16:47:34 deltaflyer smartd[399]: Unable to monitor any SMART enabled devices. Try debug (-d) option. Exiting...
Mai 27 16:47:59 deltaflyer /usr/bin/gpm[400]: *** info [mice.c(1990)]:
Mai 27 16:47:59 deltaflyer dbus[402]: [system] Successfully activated service 'org.freedesktop.systemd1'
Mai 27 16:47:59 deltaflyer nm-dispatcher[395]: Could not get the system bus (Timeout was reached). Make sure the message bus daemon is running!
Mai 27 16:47:59 deltaflyer acpid[391]: starting up with netlink and the input layer
Mai 27 16:47:34 deltaflyer systemd[1]: Started D-Bus System Message Bus.
Mai 27 16:47:59 deltaflyer systemd-logind[392]: Failed to enable subscription: Connection timed out
Mai 27 16:47:59 deltaflyer systemd-logind[392]: Failed to fully start up daemon: Connection timed out
Mai 27 16:47:59 deltaflyer systemd[1]: Failed to register name: Connection timed out
Mai 27 16:47:59 deltaflyer systemd[1]: Failed to set up API bus: Connection timed out
Mai 27 16:47:59 deltaflyer systemd[1]: Starting D-Bus System Message Bus...
Mai 27 16:47:59 deltaflyer systemd[1]: Starting Preprocess NFS configuration...
Mai 27 16:47:59 deltaflyer systemd[1]: Starting Network Manager...
Mai 27 16:47:59 deltaflyer systemd[1]: Starting VirtualBox Guest Service...
Mai 27 16:47:59 deltaflyer systemd[1]: Started LVM2 PV scan on device 254:0.
Mai 27 16:47:59 deltaflyer /usr/bin/gpm[400]: imps2: Auto-detected intellimouse PS/2
Mai 27 16:47:59 deltaflyer dbus[402]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service'
Mai 27 16:47:59 deltaflyer upowerd[393]: (upowerd:393): UPower-WARNING **: Failed to acquire org.freedesktop.UPower: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Mai 27 16:47:59 deltaflyer upowerd[393]: (upowerd:393): UPower-WARNING **: Could not acquire name; bailing out
Mai 27 16:47:59 deltaflyer systemd[1]: Started Restore Sound Card State.
It almost seems to be a problem with a dbus and/or NetworkManager race condition.

[solved] What makes systemd-logind.service fail?

After last update made yesterday I was unable to reboot. With the help of an installation cd and chrooting I disabled my graphical login manager lxdm which, when started, seems to do nothing and the system is stuck.
Without lxdm service enabled, I can start xfce4 with
startxfce4
from commandline and everything seems to run fine.
But the booting process gives me several messages telling that the service systemd-logind failed. Apart from the virtual console created while booting and the one running X11 there is no other one (no login prompt when pressing strg+alt f3 e.g.)
[root@amd64-archlinux ~]# systemctl status systemd-logind
● systemd-logind.service - Login Service
Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static)
Active: failed (Result: start-limit) since Sun 2014-06-08 19:09:24 CEST; 5min ago
Docs: man:systemd-logind.service(8)
man:logind.conf(5)
http://www.freedesktop.org/wiki/Software/systemd/logind
http://www.freedesktop.org/wiki/Software/systemd/multiseat
Process: 336 ExecStart=/usr/lib/systemd/systemd-logind (code=exited, status=1/FAILURE)
Main PID: 336 (code=exited, status=1/FAILURE)
Status: "Shutting down..."
Jun 08 19:09:24 amd64-archlinux systemd[1]: Failed to start Login Service.
Jun 08 19:09:24 amd64-archlinux systemd[1]: Unit systemd-logind.service entered failed state.
Jun 08 19:09:24 amd64-archlinux systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
Jun 08 19:09:24 amd64-archlinux systemd[1]: Stopping Login Service...
Jun 08 19:09:24 amd64-archlinux systemd[1]: Starting Login Service...
Jun 08 19:09:24 amd64-archlinux systemd[1]: systemd-logind.service start request repeated too quickly, refusing to start.
Jun 08 19:09:24 amd64-archlinux systemd[1]: Failed to start Login Service.
Jun 08 19:09:24 amd64-archlinux systemd[1]: Unit systemd-logind.service entered failed state.
Has anyone an idea where to lead me?
Last edited by bernd_b (2014-06-09 11:20:21)

I don't know if I got you point - but here is a try:
I am running X11 started manually with "startxfce4". So firing up a konsole in X11 I do and get
root@amd64-archlinux pkg]# systemctl stop systemd-logind
[root@amd64-archlinux pkg]# systemctl start systemd-logind
Job for systemd-logind.service failed. See 'systemctl status systemd-logind.service' and 'journalctl -xn' for details.
journalctl -xn:
-- Unit systemd-logind.service has begun shutting down.
Jun 08 21:38:18 amd64-archlinux systemd[1]: Starting Login Service...
-- Subject: Unit systemd-logind.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-logind.service has begun starting up.
Jun 08 21:38:18 amd64-archlinux systemd[1]: systemd-logind.service start request repeated too quickly, refusing to start.
Jun 08 21:38:18 amd64-archlinux systemd[1]: Failed to start Login Service.
-- Subject: Unit systemd-logind.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-logind.service has failed.
-- The result is failed.
I ran the service directly I get:
[root@amd64-archlinux pkg]# /usr/lib/systemd/systemd-logind
Failed to connect to system bus: No such file or directory
Failed to fully start up daemon: No such file or directory
What I figured out so far is this in addition:
- krusader does not start- there is no response or message in the konsole when firing up this application.
- I can only mount nfs-shares with the option "-o nolock" otherwise I get, e.g.
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mount.nfs: an incorrect mount option was specified
Last edited by bernd_b (2014-06-08 19:48:43)

Systemd dhcpcd service failing on boot

Hi folks,
I'm trying to convert my workstation to "pure" systemd configuration (no initscripts-systemd):
[csingley@quadrupel ~]$ pacman -Qs systemd
local/libsystemd 185-3
systemd client libraries
local/systemd 185-3
system and service manager
local/systemd-arch-units 20120612-5
Arch specific Systemd unit files
local/systemd-sysvcompat 185-3
sysvinit compat for systemd
local/systemd-tools 185-3
standalone tools from systemd
Per the instructions on the wiki, I enabled [email protected], but the service fails to start upon boot.
[root@quadrupel csingley]# systemctl status [email protected]
[email protected] - dhcpcd on eth0
Loaded: loaded (/usr/lib/systemd/system/[email protected]; enabled)
Active: failed (Result: exit-code) since Thu, 28 Jun 2012 12:36:16 -0500; 39s ago
Process: 299 ExecStart=/sbin/dhcpcd -A -q -w %I (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/[email protected]/eth0
However, I can start the service manually after the boot process is complete:
[root@quadrupel csingley]# systemctl start [email protected]
[root@quadrupel csingley]#
Presumably not all dependencies have been satisfied when systemd tries to run dhcpcd during boot.
I'm very new to systemd; any tips for troubleshooting this issue?
TIA

dj-x-cess wrote:
I have the same problem.
It seems, at least for my machine, dhcpcd starts before eth0 gets initialized on boot time:
Sep 05 07:38:39 vostro dhcpcd[180]: version 5.6.0 starting
Sep 05 07:38:39 vostro dhcpcd[180]: eth0: interface not found or invalid
Sep 05 07:38:39 vostro kernel: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
Sep 05 07:38:39 vostro kernel: r8169 0000:13:00.0: irq 47 for MSI/MSI-X
Sep 05 07:38:39 vostro kernel: r8169 0000:13:00.0: eth0: RTL8168d/8111d at 0xf9c00000, a4:ba:db:a6:a6:33, XID 083000c0 IRQ 47
Sep 05 07:38:39 vostro kernel: r8169 0000:13:00.0: eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
Yes. Same thing here with the latest install. I put "tg3" in /etc/modules-load.d/tigon.conf. Guess it loads it sooner then and now it gets an IP. Couldn't you make dhcpcd wait for eth0 to come up? It looks important, I mean dhcp should work I'm a newbie with Arch, installed it for the first time.
Here are my logs before the fix (I was looking in /var/log/, but then I found out that there is a journalctl command):
Nov 14 15:33:40 neimastina dhcpcd[176]: version 5.6.2 starting
Nov 14 15:33:40 neimastina dhcpcd[176]: eth0: interface not found or invalid
Nov 14 15:33:44 neimastina systemd[1]: [email protected]: control process exited, code=exited status=1
Nov 14 15:33:45 neimastina kernel: EDAC MC: Ver: 3.0.0
Nov 14 15:33:45 neimastina kernel: wmi: Mapper loaded
Nov 14 15:33:45 neimastina kernel: iTCO_vendor_support: vendor-support=0
Nov 14 15:33:45 neimastina kernel: tg3.c:v3.124 (March 21, 2012)
Nov 14 15:33:45 neimastina kernel: EDAC MC0: Giving out device to 'x38_edac' 'x38': DEV 0000:00:00.0
Nov 14 15:33:45 neimastina kernel: tg3 0000:34:00.0: eth0: Tigon3 [partno(BCM95751A519FLP) rev 4201] (PCI Express) MAC address 00:10:18:53:12:b7
Nov 14 15:33:45 neimastina kernel: tg3 0000:34:00.0: eth0: attached PHY is 5750 (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0])
Nov 14 15:33:45 neimastina kernel: tg3 0000:34:00.0: eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]
Nov 14 15:33:45 neimastina kernel: tg3 0000:34:00.0: eth0: dma_rwctrl[76180000] dma_mask[64-bit]
Nov 14 15:33:45 neimastina kernel: gpio_ich: GPIO from 195 to 255 on gpio_ich

Trying to install the latest iTunes on my Gateway w/ Windows XP. I keep getting the message "Service 'Bonjour Service' (Bonjour Service) failed to start. Verify that you have sufficient privileges to start system services."

Hi, I'm trying to re-install the latest iTunes on my Gateway w/ Windows XP. I had to update it a while back to put songs on my brother's iPod, but my computer froze halfway through and nothing has worked right since.
I keep getting the message "Service 'Bonjour Service' (Bonjour Service) failed to start. Verify that you have sufficient privileges to start system services."
I looked through older discussions that told me to go to right click My Computer - Manage - Services and Applications - Services - Find Bonjour and restart it.
Well, the only option that I can click on is Start. When I do, it says "Windows could not restart the Bonjour Service service on Local Computer. Error 2: The system cannot find the file specified."
Where do I go from here? Help would be greatly appreciated, I've been trying to fix this for over a year now with no dice. Also, I cannot do a factory reset (last effort) because it says the administor's account is disabled and I do not have the disc.

Sorry if double posting is a no-no here, but I forgot to add that I've already tried disabling Spyware Doctor.

Apple Mobile Device Service fails to start

The last update failed on my window 7 pc,
resulting in me having to try it manually download and install, this also
failed eventually it told me to delete and reinstall, this fails due to the
apple mobile device service failing to start, and asking me if I have
sufficient privileges to start system service, help please

Hi there Jbrashear,
It sounds like you want to know how to restart the Apple Mobile Device Service because of an alert that was displayed when you were trying to update or reinstall iTunes.
The article below will walk you through the process starting or stopping the Apple Mobile Device Service on your PC.
How to restart the Apple Mobile Device Service (AMDS) on Windows - Apple Support
Also, if you haven't already, take a look at this article which walk you through the process of completely removing iTunes and then reinstalling it.
Remove and reinstall iTunes and related software components for Windows Vista, Windows 7, or Windows 8 - Apple Support
Take care,
-Jason

Apple Mobile Device Service failed to start which eventually leads to windows error 193 which never goes away no matter what I do and the dreaded

Mid way through download of I-Tunes after clearing every Apple program from my computer I get "Apple Mobile Device Service" failed to start message. Eventually leading to Windows error 193 (error 7). How do I get Apple Mobile Device Service to start so I do not get error messages and failure of I-Tunes to install?

If you have a 64-bit machine, then try the "for older video cards" version...
For general advice see Troubleshooting issues with iTunes for Windows updates.
The steps in the second box are a guide to removing everything related to iTunes and then rebuilding it which is often a good starting point unless the symptoms indicate a more specific approach. Review the other boxes and the list of support documents further down the page in case one of them applies.
The further information area has direct links to the current and recent builds in case you have problems downloading, need to revert to an older version or want to try the iTunes for Windows (64-bit - for older video cards) release as a workaround for installation or performance issues, or compatibility with QuickTime or third party software.
Your library should be unaffected by these steps but there are also links to backup and recovery advice should it be needed.
tt2

I'm installing the newest itunes 64 bit on my win 7 64 bit professional os. using the itunes installer it loads itunes part way and then i get an error message saying that bonjour service failed to start. i cant get itunes any further. i have to back out

I'm installing the newest version of Itunes over the last version on my laptop. win 7 pro os. it starts the install then a error msg comes up stating that Bonjour service failed to start. verify that i have sufficient priveleges to start system services. I can't retry, ignore only cancel which un-installs all that it has installed and reverts me to the last version which i had. any idea?

it starts the install then a error msg comes up stating that Bonjour service failed to start. verify that i have sufficient priveleges to start system services.
Sometimes we can get past that one by disabling the Bonjour Service prior to the install.
In your Start menu, right-click Computer and select "Manage".
Expand "Services & Applications".
Open "Services". (Perhaps maximise the screen to better see what's going on.)
Right-click the Bonjour Service and select "Properties".
In the General tab, set the Startup type to "Disabled":
... and click OK.
Restart the PC and try another iTunes install. Does it go through properly this time?

When I download itunes, it says that Ipod Service failed to start. I checked the services under task manager and when I try to start it, it says access denied. How to I get access and for the ipod service to start and run?

Please help. My ipod classic could not be recognised by itunes when I connect my ipod to PC. Previously it has been recognised before I updated. This was a while ago now and so I removed all apple files and re installed the latest itunes but am having the same problem.
When I download itunes, it says that Ipod Service failed to start. I checked the services under task manager and when I try to start it, it says access denied. How to I get access and for the ipod service to start and run?

Some anti-virus programs (e.g., McAfee) have this rule that can be invoked under the "maximum protection" settings: PREVENT PROGRAMS REGISTERING AS A SERVICE. If that rule is set to BLOCK, then any attempt to install or upgrade iTunes will fail with an "iPod service failed to start" message.
If you are getting this problem with iTunes, check to see if your anti-virus has this setting and unset it, at least for as long as the iTunes install requires. Exactly how to find the rule and turn it on and off will vary, depending upon your anti-malware software. However, if your anti-virus or anti-malware software produces a log of its activities, examining the log may help you find the problem.
For example, here's the log entry for McAfee:
9/23/2009 3:18:45 PM Blocked by Access Protection rule NT AUTHORITY\SYSTEM C:\WINDOWS\system32\services.exe \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\iPod Service Common Maximum Protection:Prevent programs registering as a service Action blocked : Create
Note that the log says "Common Maximum Protection: Prevent programs registering as a service". The "Common Maximum Protection" is the location of the rule, "Prevent programs registering as a service" is the rule. I used that information to track down the location in the McAfee VirusScan Console where I could turn the rule off.
After I made the change, iTunes installed without complaint.

Help!!! iTunes install error "Apple Mobile Device Service Failed To Start". Error 7 (Windows Error 193)

Help! Following a standard upgrade I got the error message "iTunes was not installed correctly. Please reinstall iTunes. Error 7 (Windows Error 193).
I am running Windows 7 and installing again brings the message "Apple Mobile Device Service failed to start. Verify that you have sufficient privileges to start system services"
I have uninstalled everything Apple, deleted all related folders and run as administrator numerous times with no luck.
I had hoped that iTunes 12.1.2 would resolve the issue, unfortunately it failed to do so leaving me iTunes free which is driving me mad!
Can anyone advise what else I can do to resolve the error and bring back iTunes?
Thanks

For general advice see Troubleshooting issues with iTunes for Windows updates.
The steps in the second box are a guide to removing everything related to iTunes and then rebuilding it which is often a good starting point unless the symptoms indicate a more specific approach. Review the other boxes and the list of support documents further down the page in case one of them applies.
The further information area has direct links to the current and recent builds in case you have problems downloading, need to revert to an older version, or want to try the iTunes for Windows (64-bit - for older video cards) release as a workaround for installation or performance issues, or compatibility with QuickTime or third party software.
Your library should be unaffected by these steps but there are also links to backup and recovery advice should it be needed.
tt2

Dell 64 bit pc . Tried updating to latest version. Error message says Apple mobile device service failed to start. Verify you have sufficient privileges to start system services. What does that mean?

I have a dell 64 bit pc and had an older version of ITunes installed. When I tried to install the 12--- version, the install stopped with the message, "Apple Mobile Device Services failed to start, verify that you have sufficient privileges to start systems services". I have no clue what that means. can anyone help. ????

Hi doywks,
The Apple Mobile Device is a component of iTunes that communicates between your computer and your iPhone or iOS device. The error message you are seeing "verify that you have sufficient privileges to start system services" has to do with the Windows operating system. It's possible that you are not logged in as the administrator for your Windows PC. Or, you may have antivirus software stopping the Apple Mobile Device from running.
If you are having issues updating iTunes on your PC, follow the steps in the article below.
If you can't install or update iTunes for Windows - Apple Support
https://support.apple.com/en-us/HT201668
How to restart the Apple Mobile Device Service (AMDS) on Windows - Apple Support
https://support.apple.com/en-us/HT203188
I hope this information helps ....
- Judy

Service 'Apple Mobile Device Service' (Apple Mobile Device Service) failed to start. Verify that you have sufficient privileges to start system services????

I recently got an iPhone 5s and had to download the new itunes which I had been putting off for ages, otherwise it wouldn't sync. It wouldn't let me download and instead said 'service mobile device service' failed to start. I then tried to uninstall (as recommended by apple) and re install but the same error came up. If i click ignore, it finishes downloading but refuses to open, instead coming up with 'error 7 windows error 193'. Ive tried everything and this is really frustrating, help would be much appreciated

OK Dave, i just found one solution that worked for me. However, I find that solutions appearing on discussion threads often are very OS and machine specific, so I normally try a variety of suggestions. After awhile one suggestion normally works. So try this one, remembering I have a Dell PC with Win 7 x 64 which may not fit your situation.
Go to https://discussions.apple.com/message/24606166#24606166 where you will find a solution from touringtest2. The soulition requires an easy uninstall of Apple software items. I followed the steps outlined exactly and have successfully installed the most recent iTunes software. Hope this works for you and a few others too. Apple support sure doesn't make it easy for interested users which is why I appreciate support communities like this. Thank you touringtest2 wherever you are. Best - RonS42

HT1926 Installation fails because Apple Mobile Device Service failed to start?

When I attempted to update ITunes, it failed at the starting services point because "Apple Mobile Device Service failed to start". The ignore button would not work. Retry did not fix it. I have deleted all ITunes from my computer, restarted, and attempted a new install. Same problem. Help.

The frequently suggested repair steps listed in comments at http://support.apple.com/kb/HT1923 and http://support.apple.com/kb/HT1926 did not work for me yesterday when I attempted for an entire day to fix this commonly reported problem with the newest iTunes update. I now realize that I overlooked one step listed in http://support.apple.com/kb/HT1923.
My computer has a Windows 64 bit operating system. I should have paid attention to this instruction:
"If you have a 64-bit version of Windows, you'll need to confirm that the following folders have been removed:
C:\Program Files (x86)\Bonjour
C:\Program Files (x86)\Common Files\Apple\
C:\Program Files (x86)\iTunes\
C:\Program Files (x86)\iPod\ "
Tonight, I removed those previous version files from the Program Files (x86) directory and executed the rest of the steps listed. Success resulted. If you are struggling like I did to install the iTunes newest update on a Windows 64 bit operating system, you might benefit to recheck that you followed the instruction listed above.

Service "Bonjour Service' failed to start. Verify that you have sufficient privileges to start system services.

Greetings,
Having a little problem installing Itunes 12. Upon trying to install the program, i'm confronted with this error: "Service "Bonjour Service' failed to start. Verify that you have sufficient privileges to start system services". Nothing I've done seems to be able to get the program to be installed. It asks if i want to retry or cancel. Clicking Retry only prompts me again with the same error message. After i hit cancel the entire installation rolls back.
I'm currently logged in as administrator ( I don't have any other accounts on this computer), I've tried uninstalling all the components relating to apple along with its folders and restarting+RT clicking>Run as Administrator. It still refuses to install. Very frustrating. Any ideas?

Sorry if double posting is a no-no here, but I forgot to add that I've already tried disabling Spyware Doctor.

Systemd-hostnamed.service fails to start

Similar Messages

Maybe you are looking for