Systemd Issues - Failed to start MyApp daemon
Hi all,
Sorry if I'm asking a stupid question, I'm new to Arch Linux, Pi, and Python. I have a Python script I'd like to start automatically after boot so I created a myapp.service file:
[Unit]
Description=MyApp daemon
Requires=network.target
[Service]
Type=forking
ExecStart=/root/bin/myapp/initmyapp.py
ExecStop=/bin/kill $MAINPID
[Install]
WantedBy=multi-user.target
After initmyapp.py runs it calls "myapp.py &" that's why I tried type=forking. I tested "systemctl start myapp" and it looks like it's working; I can see the process running. So, I did "systemctl enable myapp" which ran without errors and then I rebooted. After reboot, however, the process is not running and "systemctl status myapp" tells me this:
myapp.service - MyApp daemon
Loaded: loaded (/etc/systemd/system/myapp.service; enabled)
Active: failed (Result: exit-code) since Wed, 1969-12-31 19:00:10 EST; 43 years and 0 months ago
Process: 102 ExecStart=/root/bin/myapp/initmyapp.py (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/myapp.service
Dec 31 19:00:09 mybox initmyapp.py[102]: '_open', req)
Dec 31 19:00:09 mybox initmyapp.py[102]: File "/usr/lib/python2.7/urllib2.py", line 378, in _call_chain
Dec 31 19:00:09 mybox initmyapp.py[102]: result = func(*args)
Dec 31 19:00:09 mybox initmyapp.py[102]: File "/usr/lib/python2.7/urllib2.py", line 1207, in http_open
Dec 31 19:00:09 mybox initmyapp.py[102]: return self.do_open(httplib.HTTPConnection, req)
Dec 31 19:00:09 mybox initmyapp.py[102]: File "/usr/lib/python2.7/urllib2.py", line 1177, in do_open
Dec 31 19:00:10 mybox initmyapp.py[102]: raise URLError(err)
Dec 31 19:00:10 mybox initmyapp.py[102]: urllib2.URLError: <urlopen error [Errno -2] Name or service not known>
Dec 31 19:00:10 mybox systemd[1]: Failed to start MyApp daemon.
Dec 31 19:00:10 mybox systemd[1]: Unit myapp.service entered failed state
Does this mean that networking is not ready yet? Instead of Requires=network.target I also tried Requires=multi-user.target but didn't work. I have no idea what I'm doing so any suggestion would be appreciated.
Thank you for the quick response. I removed the kill part and "stop" still works. I also removed all the network includes to test it out and the background call too and after hours of trial and error I was finally able to make it work. Now I just have to figure out how to tell when the network is up. That article covers it for C (I think) but not for Python. It also seems very technical.
Anyway, thanks again for your help.
Similar Messages
-
I'm trying SSL thru the iMS 5.2
I've down a frish installation for the iMS 5.2
I'm facing this problem, when i start the messaging server i got this ERROR:
development # ./start-msg
/app/ims-thru-ssl: POP3 daemon process already running: 4043
/app/ims-thru-ssl: IMAP4 daemon process already running: 4057
/app/ims-thru-ssl: Starting HTTP daemon ...Cannot bind to port 80: Address already in use
ERROR: Failed to start HTTP daemon: /app/ims-thru-ssl/bin/msg/store/bin/mshttpd
Dispatcher already running
Starting ENS daemon
ERROR: The following services failed to start, or were already:
HTTP daemon
Could someone help me on this issue...Use netstat to see what's listening on port 80. Perhaps a web server or something?
It looks like you're trying to start a server that's partially running already, so you will want to check what processes are running, too -
Tip regarding the "systemd[1]: Failed to start Journal Service" error
Just a tip regarding the well-known
systemd[1]: Failed to start Journal Service
error (which I ran into last weekend) to maybe save one or two among you a couple of hours of your time:
The error is described here https://bbs.archlinux.org/viewtopic.php?id=151012 as well as in several other threads in other language boards / in other forums etc. It is usually (as in the linked thread) 'solved' by reinstalling the system - good old Windows magic, also useful when dealing with systemd.
The Problem with this error is that you do not get into your system. Instead, systemd will print you the mentioned "Failed to start Journal Service" error message a couple of million times. There are also no logs that you could retrieve (when booting from a livesystem) and that would give you any helpful hints, since journal is systemd's logging service, old-style system logs are not kept, and the dmesg log doesn't survive the reboot with default settings.
As pointed out in the above mentioned thread, you will see a few more instructive error messages when adding 'emergency' to the kernel line in the bootloader config.
Now there may be plenty of reasons why the systemd journal service might not work. The most common and most annoying, however, appears to be this one:
In this case you will see that the problem actually lies in
systemd[1]: Cannot open /etc/machine-id: No such file or directory
Now, 'man machine-id' reveals that "the /etc/machine-id file contains the unique machine id of the local system that is set during installation. (...) The machine ID is usually generated from a random source (...)". It is obviously perfectly justified to refuse to boot the system because an absolutely insignificant random number is missing. As far as systemd is concerned anyway.
Usually, it seems, the /etc/machine-id is set by /usr/bin/systemd-machine-id-setup during installation or system upgrade. It is not documented anywhere that this is a rather important step and that you should better check if this was or was not actually done before rebooting. Obviously (but for no apparent reasons) systemd fails to run this (or to run this successfully) sometimes.
Also to be recommended: Always retain (back up) your old kernel and initramfs and edit your bootloader config appropriately to be able to boot with your old kernel again ... just to have one or two options left to get back into the system in case of running into an unpleasant surprise from the side of systemd or other packages.
The solution is, obviously, to create this file /etc/machine-id ... You probably want to do that from a livesystem (if you want to try it from the emergency shell, you would need to remount / (i.e. root) as rw and hope that systemd will not punish you for that) by just running the program that was designed for creating this file manually: /usr/bin/systemd-machine-id-setup
http://permalink.gmane.org/gmane.comp.s … devel/7528 states that it might also work with merely creating the file 'touch /etc/machine-id'. Though I didn't try that since I had enough fun with systemd for one week and didn't want to break my system again just to see if that works.Jristz wrote:
ackalker wrote:Sorry for necrobumping this.
Generating the machine-id in a consistent way is very important when working with KVM and containers, where the machine-id can be set for the VM or container. See `man systemd-machine-id-setup`.
Again, _don't_ just put some random UUID in there, especially not in the systemd package install script, this makes provisioning Arch Linux containers a PITA.
If you thing that the way that arch is handlynbg the machine-id is wrong or can be improved, then file a bug.
He already did.
Jristz wrote:Anyway, I thing if reinstalling systemd package or if systemd have a command to reinitialize the machine-id file.
Like so many of your posts, I had to read this a half dozen times before it made any sense. I think you're hinting at the utility that ackalker already pointed out in the post you're replying to. And, if you read the install scriptlet, you wouldn't need to think about whether or not reinstalling would be an option. You would know that it isn't. -
[SOLVED] systemd : services failing to start on boot
I have removed sysvinit completely as per the systemd wiki pages.
I don't usually re-boot very often so I'm not sure exactly when the problem started.
I only noticed this problem about 4 or 5 days ago.
But now whenever I reboot my machine 2 services fail consistently.
adsl.service
colord.service
They both start flawlessly once I can log in at a console.
I'm using kde and in the last couple of days, while trying to fix my problem, the kdm service has failed to start a couple of times too - saying there is no X server.
Before switching to systemd I never had any of these problems using the old rc.conf method. My DAEMONS array had the adsl service start after the network service.
I need some help and advice to find out what is causing the problem and how to fix it.
Last edited by bhrgunatha (2012-10-25 05:44:22)Thanks. That seems plausible. So I've been snooping at the journal.
journalctl -ab
Oct 25 17:06:13 starch systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
Oct 25 17:06:14 starch systemd[1]: Started Recreate Volatile Files and Directories.
Oct 25 17:06:14 starch systemd[1]: Starting System Initialization.
Oct 25 17:06:14 starch systemd[1]: Reached target System Initialization.
Oct 25 17:06:14 starch systemd[1]: Starting CUPS Printing Service Sockets.
Oct 25 17:06:14 starch systemd[1]: Listening on CUPS Printing Service Sockets.
Oct 25 17:06:14 starch systemd[1]: Starting Console System Startup Logging...
Oct 25 17:06:14 starch systemd[1]: Starting Restore Sound Card State...
Oct 25 17:06:14 starch systemd[1]: Starting CUPS Printer Service Spool.
Oct 25 17:06:14 starch systemd[1]: Started CUPS Printer Service Spool.
Oct 25 17:06:14 starch systemd[1]: Starting D-Bus System Message Bus Socket.
Oct 25 17:06:16 starch ntpd[381]: ntpd [email protected] Tue Aug 21 15:06:24 UTC 2012 (1)
Oct 25 17:06:16 starch ntpd[413]: proto: precision = 0.156 usec
Oct 25 17:06:17 starch ntpd[413]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
Oct 25 17:06:17 starch ntpd[413]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Oct 25 17:06:18 starch ntpd[413]: Listen and drop on 1 v6wildcard :: UDP 123
Oct 25 17:06:18 starch ntpd[413]: Listen normally on 2 lo 127.0.0.1 UDP 123
Oct 25 17:06:18 starch ntpd[413]: Listen normally on 3 lo ::1 UDP 123
Oct 25 17:06:18 starch ntpd[413]: peers refreshed
Oct 25 17:06:18 starch ntpd[413]: Listening on routing socket on fd #20 for interface updates
Oct 25 17:06:18 starch dbus[384]: [system] Activating systemd to hand-off: service name='org.freedesktop.ColorManager' unit='colord.service'
Oct 25 17:06:18 starch dbus[384]: [system] Successfully activated service 'org.freedesktop.systemd1'
Oct 25 17:07:03 starch dbus[384]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Oct 25 17:07:03 starch dbus[384]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service'
Oct 25 17:07:03 starch dbus[384]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Oct 25 17:07:04 starch kernel: r8169 0000:02:00.0: eth0: link down
Oct 25 17:07:03 starch systemd[1]: Starting Manage, Install and Generate Color Profiles...
Oct 25 17:07:03 starch systemd[1]: Started Manage, Install and Generate Color Profiles.
Oct 25 17:07:03 starch systemd[1]: colord.service: main process exited, code=killed, status=6
Oct 25 17:07:03 starch systemd[1]: Unit colord.service entered failed state.
Oct 25 17:07:04 starch kernel: r8169 0000:02:00.0: eth0: link down
Oct 25 17:07:04 starch kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Oct 25 17:07:04 starch kernel: PPP generic driver version 2.4.2
Oct 25 17:07:04 starch cupsd[380]: Unknown directive DefaultAuthType on line 26.
Oct 25 17:07:04 starch kernel: r8169 0000:02:00.0: eth0: link up
Oct 25 17:07:04 starch kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Oct 25 17:07:04 starch pppoe-start[382]: TIMED OUT
Oct 25 17:07:04 starch kernel: NET: Registered protocol family 24
Oct 25 17:07:04 starch pppoe-start[382]: /usr/sbin/pppoe-start: line 193: 394 Terminated $CONNECT "$@" > /dev/null 2>&1
That seems to confirm your theory.
eth0 link is not up when attempting to start colord and adsl
So the $64,000 question:
How do I defer them until eth0 is ready?
Or how can I force the eth0 link to be up before colord or adsl try to use it?
Last edited by bhrgunatha (2012-10-25 01:33:36) -
Systemd: Slim fails to start automatically after boot
Hi, after some update a couple of weeks ago (I don't remember exactly), slim fails to start after boot. I use systemd and just had enabled the slim.service file that is included in the package. After boot, I can login on the tty and then restart the slim.service, and everything works.
In the slim.log file it says:
Fatal server error:
no screens found
Giving up.
slim: unable to connect to X server
/usr/bin/xauth: file /var/run/slim.auth does not exist
It seems like slim is started before X, since everything works when I restart the service manually. What is causing this problem and how can I solve it?
Best regards and thanks,
Jan Oliveroliarch ~ sudo systemd-analyze blame
2460ms net-auto-wireless.service
243ms rsyslog.service
239ms sshd.service
183ms console-kit-log-system-start.service
136ms systemd-logind.service
124ms console-kit-daemon.service
119ms systemd-udev-trigger.service
99ms systemd-sysctl.service
82ms systemd-readahead-replay.service
80ms systemd-vconsole-setup.service
63ms systemd-user-sessions.service
62ms systemd-remount-fs.service
58ms systemd-readahead-collect.service
55ms sys-kernel-debug.mount
43ms dev-sda2.swap
43ms dev-mqueue.mount
42ms dev-hugepages.mount
26ms systemd-tmpfiles-setup.service
20ms srv.mount
13ms tmp.mount
12ms systemd-udev.service
10ms boot.mount
9ms home.mount
oliarch ~ sudo journalctl --no-pager -a | grep slim
Jun 24 14:25:01 oliarch systemd[1]: slim.service: main process exited, code=exited, status=1
Jun 24 14:25:01 oliarch systemd[1]: Unit slim.service entered failed state. -
Sickbeard fails to start. "Unable to write PID file" [Solved]
I've installed sickbeard from the AUR but can't seem to get it started.
when running "sudo systemctl start sickbeard.service" I get the following output:
Job for sickbeard.service failed. See 'systemctl status sickbeard.service' and 'journalctl -xn' for details.
'systemctl status sickbeard.service' provides:
sickbeard.service - SickBeard daemon
Loaded: loaded (/etc/systemd/system/sickbeard.service; disabled)
Active: failed (Result: exit-code) since Sat 2013-02-23 14:49:19 CST; 1min 4s ago
Process: 11518 ExecStart=/usr/bin/sickbeard --nolaunch --daemon --quiet --config $SB_CONF --datadir $SB_DATA --port $SB_PORT --pidfile=/run/sickbeard/sickbeard-8081.pid (code=exited, status=1/FAILURE)
Feb 23 14:49:18 arch systemd[1]: Starting SickBeard daemon...
Feb 23 14:49:19 arch sickbeard[11518]: Unable to write PID file: No such file or directory [2]
Feb 23 14:49:19 arch systemd[1]: sickbeard.service: control process exited, code=exited status=1
Feb 23 14:49:19 arch systemd[1]: Failed to start SickBeard daemon.
Feb 23 14:49:19 arch systemd[1]: Unit sickbeard.service entered failed state
And it looks like 'journalctl -xn' provides about the same info:
-- Logs begin at Tue 2013-01-08 17:25:44 CST, end at Sat 2013-02-23 14:53:29 CST. --
Feb 23 14:49:19 arch sickbeard[11518]: Unable to write PID file: No such file or directory [2]
Feb 23 14:49:19 arch systemd[1]: sickbeard.service: control process exited, code=exited status=1
Feb 23 14:49:19 arch systemd[1]: Failed to start SickBeard daemon.
-- Subject: Unit sickbeard.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
-- Documentation: http://www.freedesktop.org/wiki/Softwar … e9d022f03d
-- Unit sickbeard.service has failed.
-- The result is failed.
Feb 23 14:49:19 arch systemd[1]: Unit sickbeard.service entered failed state
Also, here is the current systemd file for sickbeard, if that helps:
[Unit]
Description=SickBeard daemon
After=network.target
[Service]
EnvironmentFile=/etc/conf.d/sickbeard
User=sickbeard
Group=sickbeard
ExecStart=/usr/bin/sickbeard --nolaunch --daemon --quiet --config "$SB_CONF" --datadir "$SB_DATA" --port "$SB_PORT" --pidfile=/run/sickbeard/sickbeard-8081.pid
Type=forking
TimeoutStopSec=20
PIDFile=/run/sickbeard/sickbeard-8081.pid
[Install]
WantedBy=multi-user.target
So I guess obviously the important part is "Unable to write PID file: No such file or directory [2]", but I'm not really sure what that means or how to fix it. I've played around with the PIDfile configuration for the systemd service (tried renaming from sickbeard to sickbeard-8081) but I always get the same error.
Any ideas?
Edit: Solved by teekay
Last edited by spurious_access (2013-02-24 08:09:01)The sabnzbd systemd unit file doesn't use a pidfile. Not sure why. It would make more sense there than it does for sickbeard, because IMHO sickbeard should run as the user who owns the target tv-series media folders. Using tmpfiles.d just causes a headache when you are going to update it using the AUR package.
I installed it once using sickbeard-git from AUR, changed the systemd unit file and /usr/lib/tmpfiles.d/sickbeard.conf to match my user, chown -R'ed /opt/sickbeard, ran "pacman -R --dbonly sickbeard-git", and ever since use "git pull" to update. That also works directly from web interface.
Last edited by teekay (2013-02-24 08:47:42) -
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 pheHi,
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. -
Systemd logind.service reports an error: Failed to start login service
Hello,
I found this error in /var/log/errors.log and /var/log/daemon.log although my system functions normally.
It's been written there every 90 seconds!!!!:
Dec 19 23:52:59 localhost systemd[1]: Failed to start Login Service.
Dec 19 23:54:29 localhost systemd[1]: Failed to start Login Service.
Dec 19 23:55:59 localhost systemd[1]: Failed to start Login Service.
Dec 19 23:57:29 localhost systemd[1]: Failed to start Login Service.
Dec 19 23:58:59 localhost systemd[1]: Failed to start Login Service.
the process: systemd-logind.service seems to be working fine:
[xxx@archbox ~]$ sudo systemctl status systemd-logind.service
[sudo] password for xxx:
systemd-logind.service - Login Service
Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static)
Active: activating (start) since Wed, 2012-12-19 23:49:59 CET; 49s ago
Docs: man:systemd-logind.service(8)
man:logind.conf(5)
http://www.freedesktop.org/wiki/Software/systemd/multiseat
Main PID: 11822 (systemd-logind)
CGroup: name=systemd:/system/systemd-logind.service
└─11822 /usr/lib/systemd/systemd-logind
Dec 19 23:49:59 archbox systemd[1]: Starting Login Service...
Dec 19 23:49:59 archbox systemd-logind[11822]: New seat seat0.
Dec 19 23:49:59 archbox systemd-logind[11822]: Watching system buttons on /dev/input/event6 (P...on)
Dec 19 23:49:59 archbox systemd-logind[11822]: Watching system buttons on /dev/input/event7 (V...us)
Dec 19 23:49:59 archbox systemd-logind[11822]: Watching system buttons on /dev/input/event4 (L...ch)
Dec 19 23:49:59 archbox systemd-logind[11822]: Watching system buttons on /dev/input/event5 (S...on)
Dec 19 23:49:59 archbox systemd-logind[11822]: Watching system buttons on /dev/input/event3 (T...ns)
Dec 19 23:49:59 archbox systemd-logind[11822]: New session 1 of user xxx.
Dec 19 23:49:59 archbox systemd-logind[11822]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-...ay.
and journalctl _PID=11822 returns:
Dec 19 23:38:01 archbox sudo[21335]: xxx : TTY=pts/1 ; PWD=/home/xxx ; USER=root ; COMMAND=/usr/bin/
Dec 19 23:38:01 archbox sudo[21335]: pam_unix(sudo:session): session opened for user root by xxx(uid
Dec 19 23:38:01 archbox sudo[21335]: pam_unix(sudo:session): session closed for user root
Dec 19 23:38:44 archbox sudo[22682]: xxx : TTY=pts/1 ; PWD=/home/xxx ; USER=root ; COMMAND=/usr/bin/
Dec 19 23:38:44 archbox sudo[22682]: pam_unix(sudo:session): session opened for user root by xxx(uid
Dec 19 23:38:44 archbox sudo[22682]: pam_unix(sudo:session): session closed for user root
Dec 19 23:39:10 archbox sudo[23516]: xxx : TTY=pts/1 ; PWD=/home/xxx ; USER=root ; COMMAND=/usr/bin/
Dec 19 23:39:10 archbox sudo[23516]: pam_unix(sudo:session): session opened for user root by xxx(uid
Dec 19 23:39:29 archbox systemd[1]: systemd-logind.service operation timed out. Terminating.
Dec 19 23:39:29 archbox systemd[1]: Failed to start Login Service.
Dec 19 23:39:29 archbox systemd[1]: Unit systemd-logind.service entered failed state
Dec 19 23:39:29 archbox systemd[1]: systemd-logind.service holdoff time over, scheduling restart.
Dec 19 23:39:29 archbox systemd[1]: Stopping Login Service...
Dec 19 23:39:29 archbox systemd[1]: Starting Login Service...
Dec 19 23:39:29 archbox systemd-logind[24096]: New seat seat0.
Dec 19 23:39:29 archbox systemd-logind[24096]: Watching system buttons on /dev/input/event6 (Power B
Dec 19 23:39:29 archbox systemd-logind[24096]: Watching system buttons on /dev/input/event7 (Video B
Dec 19 23:39:29 archbox systemd-logind[24096]: Watching system buttons on /dev/input/event4 (Lid Swi
Dec 19 23:39:29 archbox systemd-logind[24096]: Watching system buttons on /dev/input/event5 (Sleep B
Dec 19 23:39:29 archbox systemd-logind[24096]: Watching system buttons on /dev/input/event3 (ThinkPa
Dec 19 23:39:29 archbox systemd-logind[24096]: New session 1 of user xxx.
Dec 19 23:39:29 archbox systemd-logind[24096]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-displa
Dec 19 23:39:30 archbox sudo[23516]: pam_unix(sudo:session): session closed for user root
Dec 19 23:40:08 archbox sudo[25314]: xxx : TTY=pts/1 ; PWD=/home/xxx ; USER=root ; COMMAND=/usr/bin/
Dec 19 23:40:08 archbox sudo[25314]: pam_unix(sudo:session): session opened for user root by xxx(uid
Dec 19 23:40:09 archbox sudo[25314]: pam_unix(sudo:session): session closed for user root
Dec 19 23:40:43 archbox slim[641]: error 8: BadMatch (invalid parameter attributes) request 142 mino
Dec 19 23:40:43 archbox slim[641]: error 9: BadDrawable (invalid Pixmap or Window parameter) request
Dec 19 23:40:43 archbox slim[641]: error 4: BadPixmap (invalid Pixmap parameter) request 54 minor 0
Dec 19 23:40:56 archbox sudo[26739]: xxx : TTY=pts/0 ; PWD=/home/xxx ; USER=root ; COMMAND=/usr/bin/
Dec 19 23:40:56 archbox sudo[26739]: pam_unix(sudo:session): session opened for user root by xxx(uid
Dec 19 23:40:59 archbox systemd[1]: systemd-logind.service operation timed out. Terminating.
Dec 19 23:40:59 archbox systemd[1]: Failed to start Login Service.
Dec 19 23:40:59 archbox systemd[1]: Unit systemd-logind.service entered failed state
Dec 19 23:40:59 archbox systemd[1]: systemd-logind.service holdoff time over, scheduling restart.
Dec 19 23:40:59 archbox systemd[1]: Stopping Login Service...
Dec 19 23:40:59 archbox systemd[1]: Starting Login Service...
Dec 19 23:40:59 archbox systemd-logind[26935]: New seat seat0.
Dec 19 23:40:59 archbox systemd-logind[26935]: Watching system buttons on /dev/input/event6 (Power B
Dec 19 23:40:59 archbox systemd-logind[26935]: Watching system buttons on /dev/input/event7 (Video B
Dec 19 23:40:59 archbox systemd-logind[26935]: Watching system buttons on /dev/input/event4 (Lid Swi
Dec 19 23:40:59 archbox systemd-logind[26935]: Watching system buttons on /dev/input/event5 (Sleep B
Dec 19 23:40:59 archbox systemd-logind[26935]: Watching system buttons on /dev/input/event3 (ThinkPa
Dec 19 23:40:59 archbox systemd-logind[26935]: New session 1 of user xxx.
Dec 19 23:40:59 archbox systemd-logind[26935]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-displa
Updating system with pacman didn't solve it.
Did I miss something out while migrating to systemd, is it a problem with SLiM or user session maybe ? Do you guys have any ideas where to start ? Thanks.
Last edited by nastycino (2012-12-30 17:46:43)My /etc/systemd/logind.conf:
# This file is part of systemd.
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
# See logind.conf(5) for details
[Login]
#NAutoVTs=6
#ReserveVT=6
#KillUserProcesses=no
#KillOnlyUsers=
#KillExcludeUsers=root
#Controllers=
#ResetControllers=cpu
#InhibitDelayMaxSec=5
HandlePowerKey=poweroff
HandleSuspendKey=suspend
HandleHibernateKey=hibernate
HandleLidSwitch=suspend
#PowerKeyIgnoreInhibited=no
#SuspendKeyIgnoreInhibited=no
#HibernateKeyIgnoreInhibited=no
#LidSwitchIgnoreInhibited=yes
Is there any way of reinstalling parts of systemd like logind.service? -
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
ThanksI'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 -
Systemd and Tmpfiles : Fail to start because of opencryptoki
Hi,
I got an error message on boot saying that tmpfiles fails to start.
systemctl --failed
● systemd-tmpfiles-clean.service loaded failed failed Cleanup of Temporary Directories
● systemd-tmpfiles-setup-dev.service loaded failed failed Create Static Device Nodes in /dev
● systemd-tmpfiles-setup.service loaded failed failed Create Volatile Files and Directories
sudo systemctl status systemd-tmpfiles-setup
● systemd-tmpfiles-setup.service - Create Volatile Files and Directories
Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static)
Active: failed (Result: exit-code) since lun. 2014-04-07 11:06:29 CEST; 22min ago
Docs: man:tmpfiles.d(5)
man:systemd-tmpfiles(8)
Process: 371 ExecStart=/usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE)
Main PID: 371 (code=exited, status=1/FAILURE)
avril 07 11:06:29 silence systemd-tmpfiles[371]: [/usr/lib/tmpfiles.d/opencryptoki.conf:39] Unknown modifier 'stdll'
avril 07 11:06:29 silence systemd-tmpfiles[371]: [/usr/lib/tmpfiles.d/opencryptoki.conf:40] Syntax error.
avril 07 11:06:29 silence systemd-tmpfiles[371]: [/usr/lib/tmpfiles.d/opencryptoki.conf:42] Unknown modifier 'slot'
avril 07 11:06:29 silence systemd-tmpfiles[371]: [/usr/lib/tmpfiles.d/opencryptoki.conf:43] Syntax error.
avril 07 11:06:29 silence systemd-tmpfiles[371]: [/usr/lib/tmpfiles.d/opencryptoki.conf:44] Unknown modifier 'stdll'
avril 07 11:06:29 silence systemd-tmpfiles[371]: [/usr/lib/tmpfiles.d/opencryptoki.conf:45] Unknown modifier 'confname'
avril 07 11:06:29 silence systemd-tmpfiles[371]: [/usr/lib/tmpfiles.d/opencryptoki.conf:46] Syntax error.
avril 07 11:06:29 silence systemd[1]: systemd-tmpfiles-setup.service: main process exited, code=exited, status=1/FAILURE
avril 07 11:06:29 silence systemd[1]: Failed to start Create Volatile Files and Directories.
avril 07 11:06:29 silence systemd[1]: Unit systemd-tmpfiles-setup.service entered failed state.
Inside /usr/lib/tmpfiles.d there is indeed a opencryptoki.conf that is a symobolic link like this :
lrwxrwxrwx 1 root root 35 4 avril 11:06 opencryptoki.conf -> /etc/opencryptoki/opencryptoki.conf
And finally here is the content of my opencryptoki.conf
version opencryptoki-3.0
# The following defaults are defined:
# hwversion = 0.0
# firmwareversion = 0.0
# description = Linux
# manufacturer = IBM
# The slot definitions below may be overriden and/or customized.
# For example:
# slot 0
# stdll = libpkcs11_cca.so
# description = "OCK CCA Token"
# manufacturer = "MyCompany Inc."
# hwversion = 2.32
# firmwareversion = 1.0
# See man(5) opencryptoki.conf for further information.
slot 0
stdll = libpkcs11_tpm.so
slot 1
stdll = libpkcs11_ica.so
slot 2
stdll = libpkcs11_cca.so
slot 3
stdll = libpkcs11_sw.so
slot 4
stdll = libpkcs11_ep11.so
confname = ep11tok.conf
There is no .pacnew in this folder, so I guess something broke opencryptoki. That doesn't seem to cause me troubles right now but right now I failed to start my httpd service because of a lack of disk space. I guess that is not a good thing.
Could someone help me ?Agree with Raynman, it doesn't make sense for that link to be there. That file is supposed to get a different sort of config (see `man tmpfiles.d`). I would just try:
sudo rm /usr/lib/tmpfiles.d/opencryptoki.conf
It's not a 100% kosher solution, but it should fix the issue for now, and hopefully if the AUR package gets an update they will fix that problem.
But mostly I'm posting because I wanted to say thanks for sharing all of your troubleshooting steps! I had an unrelated problem with my tmpfiles, searching brought me here, and your steps helped me both confirm that I had a different issue and fix my own issue. -
[SOLVED] Network Manager systemd unit fails after update
EDIT: Reinstalling libnm-glib resolved this issue
After updating to the latest version of NetworkManager (networkmanager-0.9.8.10-3), the systemd unit fails to start. It works fine after downgrading back to the previous version though (networkmanager-0.9.8.10-1). I'm not sure if this is a bug or an error on my end; since the previous package works I've just dowgraded for the time being. For the update that doesn't work, here is the output of "systemctl status" and the systemd journal:
>>sudo systemctl daemon-reload
>> sudo systemctl status NetworkManager
● NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled)
Active: failed (Result: exit-code) since Wed 2014-06-11 15:28:25 EDT; 10s ago
Process: 24073 ExecStart=/usr/bin/NetworkManager --no-daemon (code=exited, status=127)
Main PID: 24073 (code=exited, status=127)
Jun 11 15:28:25 kyle systemd[1]: NetworkManager.service: main process exited, code=exited, status=127/n/a
Jun 11 15:28:25 kyle systemd[1]: Failed to start Network Manager.
Jun 11 15:28:25 kyle systemd[1]: Unit NetworkManager.service entered failed state.
>> journalctl -xn
-- Logs begin at Tue 2014-06-10 12:47:19 EDT, end at Wed 2014-06-11 15:28:36 EDT. --
Jun 11 15:28:25 kyle sudo[24070]: pam_unix(sudo:session): session opened for user root by kyle(uid=0)
Jun 11 15:28:25 kyle systemd[1]: Starting Network Manager...
-- Subject: Unit NetworkManager.service has begun with start-up
-- Defined-By: systemd
-- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
-- Unit NetworkManager.service has begun starting up.
Jun 11 15:28:25 kyle systemd[1]: NetworkManager.service: main process exited, code=exited, status=127/n/a
Jun 11 15:28:25 kyle systemd[1]: Failed to start Network Manager.
-- Subject: Unit NetworkManager.service has failed
-- Defined-By: systemd
-- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
-- Unit NetworkManager.service has failed.
-- The result is failed.
Jun 11 15:28:25 kyle systemd[1]: Unit NetworkManager.service entered failed state.
Jun 11 15:28:25 kyle sudo[24070]: pam_unix(sudo:session): session closed for user root
Jun 11 15:28:28 kyle dbus[489]: [system] Failed to activate service 'org.freedesktop.nm_dispatcher': timed out
Jun 11 15:28:36 kyle sudo[24075]: kyle : TTY=pts/2 ; PWD=/var/cache/pacman/pkg ; USER=root ; COMMAND=/usr/bin/systemctl status NetworkManager
Jun 11 15:28:36 kyle sudo[24075]: pam_unix(sudo:session): session opened for user root by kyle(uid=0)
Jun 11 15:28:36 kyle sudo[24075]: pam_unix(sudo:session): session closed for user root
Last edited by T0k3n (2014-07-03 15:18:01)Check the changes:
https://projects.archlinux.org/svntogit … e192881dc5
https://projects.archlinux.org/svntogit … ee906b6c44
When posting configs, code or command output, please use [ code ] tags, not [ quote ] tags https://bbs.archlinux.org/help.php#bbcode
like this
It makes the code more readable and - in case of longer listings - more convenient to scroll through. -
[SOLVED]sensord.service fails to start
Hi there!
I made a clean Arch install a couple of days ago and I've had problems trying to get sensord to work apropriately. I've went through the troubleshooting of this particular service and googled a lot the last couple of days about this topic but I found nothing really useful (or nothing that I could really understand. Maybe my search terms are not so effective ).
# systemctl status sensord -l
[sudo] password for daniel:
● sensord.service - Log hardware monitoring data
Loaded: loaded (/usr/lib/systemd/system/sensord.service; enabled)
Active: failed (Result: exit-code) since mié 2014-09-03 09:14:04 CLT; 7min ago
Process: 4231 ExecStart=/usr/sbin/sensord -i $INTERVAL -l $LOG_INTERVAL -f daemon (code=exited, status=127)
sep 03 09:14:04 Ophiel sensord[4231]: /usr/sbin/sensord: error while loading shared libraries: librrd.so.4: cannot open shared object file: No such file or directory
sep 03 09:14:04 Ophiel systemd[1]: sensord.service: control process exited, code=exited status=127
sep 03 09:14:04 Ophiel systemd[1]: Failed to start Log hardware monitoring data.
sep 03 09:14:04 Ophiel systemd[1]: Unit sensord.service entered failed state.
This is just a minor annoyance. My system performs great and I have no issues with it. It just annoys the heck out of me to see a service failing in my start up screen.
I don't know if hardware specs or other logs are useful. But if you need more info, just let me know
Thanks in advance.
Last edited by Silex89 (2014-09-03 14:16:15)Silex89 wrote:My system performs great and I have no issues with it
Hmmm ...
Silex89 wrote:This thread is SOLVED.
Really ? Maybe there are services working but unrequested, have a look here:
https://bbs.archlinux.org/viewtopic.php?id=186244
I thought, that you explicitly installed sensord. Do you need a round robin database to visualize graphically your measured values in Nagios e.g. ?
Last edited by midixinga (2014-09-03 18:06:06) -
Arch32.service fails on start. bundled 32bit system
I am using the install bundled 32bit system in 64bit system wiki and I think I am having trouble in the systemd service part.
I am getting an error starting the arch32 service with systemctl. I have looked at the error messages and I am just not sure what is wrong here. Can someone point out what the error message is telling me, so that I can, in the future, read error messages better? I have did searches and google came up short. I am an eager Linux student. I would more than appreaciate any "hints" so that I can become better and be more value as I help others. Thank you.
systemctl start arch32
## Job for arch32.service failed. See "systemctl status arch32.service" and "journalctl -xe" for details.
The result of systemct status message...
# systemctl status -l arch32
● arch32.service - 32-bit chroot
Loaded: loaded (/etc/systemd/system/arch32.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2015-05-22 10:32:54 EDT; 8min ago
Process: 980 ExecStart=/usr/local/bin/arch32 start (code=exited, status=1/FAILURE)
Main PID: 980 (code=exited, status=1/FAILURE)
May 22 10:32:53 archhost systemd[1]: Starting 32-bit chroot...
May 22 10:32:54 archhost systemd[1]: arch32.service: main process exited, code=exited, status=1/FAILURE
May 22 10:32:54 archhost systemd[1]: Failed to start 32-bit chroot.
May 22 10:32:54 archhost systemd[1]: Unit arch32.service entered failed state.
May 22 10:32:54 archhost systemd[1]: arch32.service failed.
The result of jouornalctl message...
# journalctl -xe
May 23 07:41:27 archhost org.a11y.Bus[3104]: Activating service name='org.a11y.atspi.Registry'
May 23 07:41:28 archhost org.a11y.Bus[3104]: Successfully activated service 'org.a11y.atspi.Registry'
May 23 07:41:28 archhost org.a11y.atspi.Registry[3233]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
May 23 07:41:28 archhost polkitd[3111]: Registered Authentication Agent for unix-session:c1 (system bus name :1.13 [/usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1], object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
May 23 07:41:32 archhost kernel: dell_wmi: Unknown WMI event type 0x11: 0xffd0
May 23 07:41:32 archhost kernel: dell_wmi: Unknown WMI event type 0x11: 0xffd1
May 23 07:41:32 archhost kernel: dell_wmi: Unknown WMI event type 0x11: 0x187
May 23 07:41:32 archhost kernel: dell_wmi: Unknown WMI event type 0x11: 0x188
May 23 07:41:32 archhost kernel: dell_wmi: Unknown WMI event type 0x11: 0x187
May 23 07:41:33 archhost kernel: dell_wmi: Unknown WMI event type 0x11: 0x188
May 23 07:49:50 archhost sudo[3422]: codeamend : TTY=pts/0 ; PWD=/usr/local/bin ; USER=root ; COMMAND=/usr/bin/systemctl start arch32
May 23 07:49:50 archhost sudo[3422]: pam_unix(sudo:session): session opened for user root by codeamend(uid=0)
May 23 07:49:50 archhost polkitd[3111]: Registered Authentication Agent for unix-process:3423:70961 (system bus name :1.14 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
May 23 07:49:50 archhost systemd[1]: Starting 32-bit chroot...
-- Subject: Unit arch32.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit arch32.service has begun starting up.
May 23 07:49:50 archhost arch32[3428]: mount: mount point /opt/arch32/scratch does not exist
May 23 07:49:50 archhost systemd[1]: arch32.service: main process exited, code=exited, status=1/FAILURE
May 23 07:49:50 archhost systemd[1]: Failed to start 32-bit chroot.
-- Subject: Unit arch32.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit arch32.service has failed.
-- The result is failed.
May 23 07:49:50 archhost systemd[1]: Unit arch32.service entered failed state.
May 23 07:49:50 archhost systemd[1]: arch32.service failed.
May 23 07:49:50 archhost sudo[3422]: pam_unix(sudo:session): session closed for user root
May 23 07:49:50 archhost polkitd[3111]: Unregistered Authentication Agent for unix-process:3423:70961 (system bus name :1.14, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
May 23 07:53:11 archhost systemd[1]: Starting Cleanup of Temporary Directories...
-- Subject: Unit systemd-tmpfiles-clean.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-tmpfiles-clean.service has begun starting up.
May 23 07:53:11 archhost systemd[1]: Started Cleanup of Temporary Directories.
-- Subject: Unit systemd-tmpfiles-clean.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-tmpfiles-clean.service has finished starting up.
-- The start-up result is done.
Last edited by AcousticBruce (2015-05-23 15:57:21)graysky wrote:Edit your /usr/local/bin/arch32 script removing the reference to '/scratch' unless you actually have it on your system. That was a typo from me on the wiki which has now been corrected.
I removed the /scratch from two areas and made a copy of the wiki version just in case I was wrong. I still got these errors.
$ systemctl status -l arch32.service
● arch32.service - 32-bit chroot
Loaded: loaded (/etc/systemd/system/arch32.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2015-05-24 08:53:49 EDT; 20s ago
Process: 2139 ExecStart=/usr/local/bin/arch32 start (code=exited, status=1/FAILURE)
Main PID: 2139 (code=exited, status=1/FAILURE)
May 24 08:53:49 archhost systemd[1]: Starting 32-bit chroot...
May 24 08:53:49 archhost systemd[1]: arch32.service: main process exited, code=exited, status=1/FAILURE
May 24 08:53:49 archhost systemd[1]: Failed to start 32-bit chroot.
May 24 08:53:49 archhost systemd[1]: Unit arch32.service entered failed state.
May 24 08:53:49 archhost systemd[1]: arch32.service failed
$ journalctl -xe
-- Unit arch32.service has begun starting up.
May 24 08:49:36 archhost systemd[1]: arch32.service: main process exited, code=exited, status=1/FAILURE
May 24 08:49:36 archhost systemd[1]: Failed to start 32-bit chroot.
-- Subject: Unit arch32.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit arch32.service has failed.
-- The result is failed.
May 24 08:49:36 archhost polkitd[663]: Unregistered Authentication Agent for unix-process:2103:877657 (system bus name :1.20, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
May 24 08:49:36 archhost systemd[1]: Unit arch32.service entered failed state.
May 24 08:49:36 archhost systemd[1]: arch32.service failed.
May 24 08:53:45 archhost polkitd[663]: Registered Authentication Agent for unix-process:2132:902936 (system bus name :1.24 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
May 24 08:53:49 archhost polkitd[663]: Operator of unix-session:c1 successfully authenticated as unix-user:codeamend to gain TEMPORARY authorization for action org.freedesktop.systemd1.manage-units for system-bus-name::1.25 [systemctl start arch32] (owned by unix-user:codeamend)
May 24 08:53:49 archhost systemd[1]: Starting 32-bit chroot...
-- Subject: Unit arch32.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit arch32.service has begun starting up.
May 24 08:53:49 archhost systemd[1]: arch32.service: main process exited, code=exited, status=1/FAILURE
May 24 08:53:49 archhost systemd[1]: Failed to start 32-bit chroot.
-- Subject: Unit arch32.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit arch32.service has failed.
-- The result is failed.
May 24 08:53:49 archhost systemd[1]: Unit arch32.service entered failed state.
May 24 08:53:49 archhost systemd[1]: arch32.service failed.
May 24 08:53:49 archhost polkitd[663]: Unregistered Authentication Agent for unix-process:2132:902936 (system bus name :1.24, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
May 24 08:56:04 archhost sudo[2156]: codeamend : TTY=pts/2 ; PWD=/opt/arch32/usr/local/bin ; USER=root ; COMMAND=/usr/bin/nano arch32
May 24 08:56:04 archhost sudo[2156]: pam_unix(sudo:session): session opened for user root by codeamend(uid=0)
May 24 08:56:21 archhost sudo[2156]: pam_unix(sudo:session): session closed for user root
May 24 08:56:24 archhost polkitd[663]: Registered Authentication Agent for unix-process:2160:918835 (system bus name :1.28 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
May 24 08:56:28 archhost polkitd[663]: Operator of unix-session:c1 successfully authenticated as unix-user:codeamend to gain TEMPORARY authorization for action org.freedesktop.systemd1.manage-units for system-bus-name::1.29 [systemctl start arch32] (owned by unix-user:codeamend)
May 24 08:56:28 archhost systemd[1]: Starting 32-bit chroot...
-- Subject: Unit arch32.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit arch32.service has begun starting up.
May 24 08:56:28 archhost systemd[1]: arch32.service: main process exited, code=exited, status=1/FAILURE
May 24 08:56:28 archhost systemd[1]: Failed to start 32-bit chroot.
-- Subject: Unit arch32.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit arch32.service has failed.
-- The result is failed.
May 24 08:56:28 archhost systemd[1]: Unit arch32.service entered failed state.
May 24 08:56:28 archhost systemd[1]: arch32.service failed.
May 24 08:56:28 archhost polkitd[663]: Unregistered Authentication Agent for unix-process:2160:918835 (system bus name :1.28, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) -
I was going about the process to set up the 32-bit chroot so I could use Adobe Acrobat on my system, but systemctl failed to start the service. Output of "systemctl status arch32.service" is as follows:
Loaded: loaded (/etc/systemd/system/arch32.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2015-05-29 18:10:29 EDT; 11s ago
Process: 1295 ExecStart=/usr/local/bin/arch32 start (code=exited, status=1/FAILURE)
Main PID: 1295 (code=exited, status=1/FAILURE)
May 29 18:10:29 the-enforcer systemd[1]: Starting 32-bit chroot...
May 29 18:10:29 the-enforcer systemd[1]: arch32.service: main process exited, code=exited, status=1/FAILURE
May 29 18:10:29 the-enforcer systemd[1]: Failed to start 32-bit chroot.
May 29 18:10:29 the-enforcer systemd[1]: Unit arch32.service entered failed state.
May 29 18:10:29 the-enforcer systemd[1]: arch32.service failed.
output of "journalctl -xe" is as follows
-- Subject: Unit arch32.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit arch32.service has failed.
-- The result is failed.
May 29 18:09:07 the-enforcer systemd[1]: Unit arch32.service entered failed state.
May 29 18:09:07 the-enforcer systemd[1]: arch32.service failed.
May 29 18:09:07 the-enforcer polkitd[309]: Unregistered Authentication Agent for unix-process:1242:62178 (system bus name :1.65, object path /org/freedesktop/PolicyKit1/Authen
May 29 18:09:07 the-enforcer sudo[1241]: pam_unix(sudo:session): session closed for user root
May 29 18:09:25 the-enforcer sudo[1258]: shaun : TTY=pts/0 ; PWD=/home/shaun ; USER=root ; COMMAND=/usr/local/bin/arch32 start
May 29 18:09:25 the-enforcer sudo[1258]: pam_unix(sudo:session): session opened for user root by shaun(uid=0)
May 29 18:09:25 the-enforcer sudo[1258]: pam_unix(sudo:session): session closed for user root
May 29 18:09:51 the-enforcer /usr/lib/gdm/gdm-x-session[517]: Activating service name='org.gnome.Terminal'
May 29 18:09:51 the-enforcer /usr/lib/gdm/gdm-x-session[517]: Successfully activated service 'org.gnome.Terminal'
May 29 18:10:02 the-enforcer sudo[1281]: shaun : TTY=pts/0 ; PWD=/home/shaun ; USER=root ; COMMAND=/usr/local/bin/arch32 stop
May 29 18:10:02 the-enforcer sudo[1281]: pam_unix(sudo:session): session opened for user root by shaun(uid=0)
May 29 18:10:03 the-enforcer sudo[1281]: pam_unix(sudo:session): session closed for user root
May 29 18:10:29 the-enforcer sudo[1289]: shaun : TTY=pts/0 ; PWD=/home/shaun ; USER=root ; COMMAND=/usr/bin/systemctl start arch32.service
May 29 18:10:29 the-enforcer sudo[1289]: pam_unix(sudo:session): session opened for user root by shaun(uid=0)
May 29 18:10:29 the-enforcer polkitd[309]: Registered Authentication Agent for unix-process:1290:70456 (system bus name :1.66 [/usr/bin/pkttyagent --notify-fd 5 --fallback], o
May 29 18:10:29 the-enforcer systemd[1]: Starting 32-bit chroot...
-- Subject: Unit arch32.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit arch32.service has begun starting up.
May 29 18:10:29 the-enforcer systemd[1]: arch32.service: main process exited, code=exited, status=1/FAILURE
May 29 18:10:29 the-enforcer systemd[1]: Failed to start 32-bit chroot.
-- Subject: Unit arch32.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit arch32.service has failed.
-- The result is failed.
May 29 18:10:29 the-enforcer systemd[1]: Unit arch32.service entered failed state.
May 29 18:10:29 the-enforcer systemd[1]: arch32.service failed.
May 29 18:10:29 the-enforcer sudo[1289]: pam_unix(sudo:session): session closed for user root
May 29 18:10:29 the-enforcer polkitd[309]: Unregistered Authentication Agent for unix-process:1290:70456 (system bus name :1.66, object path /org/freedesktop/PolicyKit1/Authen
lines 1322-1364/1364 (END)
Here's what my arch32.service file looks like:
[Unit]
Description=32-bit chroot
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/local/bin/arch32 start
ExecStop=/usr/local/bin/arch32 stop
[Install]
WantedBy=multi-user.target
Here's what my /usr/local/bin/arch32 file looks like
#!/bin/bash
## User variables.
MOUNTPOINT=/opt/arch32
## Set MANAGEPARTITION to any value if /opt/arch32 resides on a separate
## partition and not mounted by /etc/fstab or some other means.
## If /opt/arch32 is part of your rootfs, leave this empty.
MANAGEPARTITION=
## Leave USEDISTCC empty unless you wish to use distccd from within the chroot.
USEDISTCC=
DISTCC_SUBNET='10.9.8.0/24'
## PIDFILE shouldn't need to ba changed from this default.
PIDFILE=/run/arch32
start_distccd() {
[[ ! -L "$MOUNTPOINT"/usr/bin/distccd-chroot ]] &&
ln -s /usr/bin/distccd "$MOUNTPOINT"/usr/bin/distccd-chroot
DISTCC_ARGS="--user nobody --allow $DISTCC_SUBNET --port 3692 --log-level warning --log-file /tmp/distccd-i686.log"
[[ -z "$(pgrep distccd-chroot)" ]] &&
linux32 chroot "$MOUNTPOINT" /bin/bash -c "/usr/bin/distccd-chroot --daemon $DISTCC_ARGS"
stop_distccd() {
[[ -n "$(pgrep distccd-chroot)" ]] &&
linux32 chroot "$MOUNTPOINT" /bin/bash -c "pkill -SIGTERM distccd-chroot"
case $1 in
start)
[[ -f "$PIDFILE" ]] && exit 1
if [[ -n "$MANAGEPARTITION" ]]; then
mountpoint -q $MOUNTPOINT || mount LABEL="arch32" $MOUNTPOINT
fi
dirs=(/tmp /dev /dev/pts /home)
for d in "${dirs[@]}"; do
mount -o bind $d "$MOUNTPOINT"$d
done
mount -t proc none "$MOUNTPOINT/proc"
mount -t sysfs none "$MOUNTPOINT/sys"
touch "$PIDFILE"
[[ -n "$USEDISTCC" ]] && start_distccd
stop)
[[ ! -f "$PIDFILE" ]] && exit 1
[[ -n "$USEDISTCC" ]] && stop_distccd
if [[ -n "$MANAGEPARTITION" ]]; then
umount -R -A -l "$MOUNTPOINT"
else
dirs=(/home /dev/pts /dev /tmp)
[[ -n "$USEDISTCC" ]] && stop_distccd
umount "$MOUNTPOINT"/{sys,proc}
for d in "${dirs[@]}"; do
umount -l "$MOUNTPOINT$d"
done
fi
rm -f "$PIDFILE"
echo "usage: $0 (start|stop)"
exit 1
esac
Any ideas as to what's going on?I was going about the process to set up the 32-bit chroot so I could use Adobe Acrobat on my system, but systemctl failed to start the service. Output of "systemctl status arch32.service" is as follows:
Loaded: loaded (/etc/systemd/system/arch32.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2015-05-29 18:10:29 EDT; 11s ago
Process: 1295 ExecStart=/usr/local/bin/arch32 start (code=exited, status=1/FAILURE)
Main PID: 1295 (code=exited, status=1/FAILURE)
May 29 18:10:29 the-enforcer systemd[1]: Starting 32-bit chroot...
May 29 18:10:29 the-enforcer systemd[1]: arch32.service: main process exited, code=exited, status=1/FAILURE
May 29 18:10:29 the-enforcer systemd[1]: Failed to start 32-bit chroot.
May 29 18:10:29 the-enforcer systemd[1]: Unit arch32.service entered failed state.
May 29 18:10:29 the-enforcer systemd[1]: arch32.service failed.
output of "journalctl -xe" is as follows
-- Subject: Unit arch32.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit arch32.service has failed.
-- The result is failed.
May 29 18:09:07 the-enforcer systemd[1]: Unit arch32.service entered failed state.
May 29 18:09:07 the-enforcer systemd[1]: arch32.service failed.
May 29 18:09:07 the-enforcer polkitd[309]: Unregistered Authentication Agent for unix-process:1242:62178 (system bus name :1.65, object path /org/freedesktop/PolicyKit1/Authen
May 29 18:09:07 the-enforcer sudo[1241]: pam_unix(sudo:session): session closed for user root
May 29 18:09:25 the-enforcer sudo[1258]: shaun : TTY=pts/0 ; PWD=/home/shaun ; USER=root ; COMMAND=/usr/local/bin/arch32 start
May 29 18:09:25 the-enforcer sudo[1258]: pam_unix(sudo:session): session opened for user root by shaun(uid=0)
May 29 18:09:25 the-enforcer sudo[1258]: pam_unix(sudo:session): session closed for user root
May 29 18:09:51 the-enforcer /usr/lib/gdm/gdm-x-session[517]: Activating service name='org.gnome.Terminal'
May 29 18:09:51 the-enforcer /usr/lib/gdm/gdm-x-session[517]: Successfully activated service 'org.gnome.Terminal'
May 29 18:10:02 the-enforcer sudo[1281]: shaun : TTY=pts/0 ; PWD=/home/shaun ; USER=root ; COMMAND=/usr/local/bin/arch32 stop
May 29 18:10:02 the-enforcer sudo[1281]: pam_unix(sudo:session): session opened for user root by shaun(uid=0)
May 29 18:10:03 the-enforcer sudo[1281]: pam_unix(sudo:session): session closed for user root
May 29 18:10:29 the-enforcer sudo[1289]: shaun : TTY=pts/0 ; PWD=/home/shaun ; USER=root ; COMMAND=/usr/bin/systemctl start arch32.service
May 29 18:10:29 the-enforcer sudo[1289]: pam_unix(sudo:session): session opened for user root by shaun(uid=0)
May 29 18:10:29 the-enforcer polkitd[309]: Registered Authentication Agent for unix-process:1290:70456 (system bus name :1.66 [/usr/bin/pkttyagent --notify-fd 5 --fallback], o
May 29 18:10:29 the-enforcer systemd[1]: Starting 32-bit chroot...
-- Subject: Unit arch32.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit arch32.service has begun starting up.
May 29 18:10:29 the-enforcer systemd[1]: arch32.service: main process exited, code=exited, status=1/FAILURE
May 29 18:10:29 the-enforcer systemd[1]: Failed to start 32-bit chroot.
-- Subject: Unit arch32.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit arch32.service has failed.
-- The result is failed.
May 29 18:10:29 the-enforcer systemd[1]: Unit arch32.service entered failed state.
May 29 18:10:29 the-enforcer systemd[1]: arch32.service failed.
May 29 18:10:29 the-enforcer sudo[1289]: pam_unix(sudo:session): session closed for user root
May 29 18:10:29 the-enforcer polkitd[309]: Unregistered Authentication Agent for unix-process:1290:70456 (system bus name :1.66, object path /org/freedesktop/PolicyKit1/Authen
lines 1322-1364/1364 (END)
Here's what my arch32.service file looks like:
[Unit]
Description=32-bit chroot
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/local/bin/arch32 start
ExecStop=/usr/local/bin/arch32 stop
[Install]
WantedBy=multi-user.target
Here's what my /usr/local/bin/arch32 file looks like
#!/bin/bash
## User variables.
MOUNTPOINT=/opt/arch32
## Set MANAGEPARTITION to any value if /opt/arch32 resides on a separate
## partition and not mounted by /etc/fstab or some other means.
## If /opt/arch32 is part of your rootfs, leave this empty.
MANAGEPARTITION=
## Leave USEDISTCC empty unless you wish to use distccd from within the chroot.
USEDISTCC=
DISTCC_SUBNET='10.9.8.0/24'
## PIDFILE shouldn't need to ba changed from this default.
PIDFILE=/run/arch32
start_distccd() {
[[ ! -L "$MOUNTPOINT"/usr/bin/distccd-chroot ]] &&
ln -s /usr/bin/distccd "$MOUNTPOINT"/usr/bin/distccd-chroot
DISTCC_ARGS="--user nobody --allow $DISTCC_SUBNET --port 3692 --log-level warning --log-file /tmp/distccd-i686.log"
[[ -z "$(pgrep distccd-chroot)" ]] &&
linux32 chroot "$MOUNTPOINT" /bin/bash -c "/usr/bin/distccd-chroot --daemon $DISTCC_ARGS"
stop_distccd() {
[[ -n "$(pgrep distccd-chroot)" ]] &&
linux32 chroot "$MOUNTPOINT" /bin/bash -c "pkill -SIGTERM distccd-chroot"
case $1 in
start)
[[ -f "$PIDFILE" ]] && exit 1
if [[ -n "$MANAGEPARTITION" ]]; then
mountpoint -q $MOUNTPOINT || mount LABEL="arch32" $MOUNTPOINT
fi
dirs=(/tmp /dev /dev/pts /home)
for d in "${dirs[@]}"; do
mount -o bind $d "$MOUNTPOINT"$d
done
mount -t proc none "$MOUNTPOINT/proc"
mount -t sysfs none "$MOUNTPOINT/sys"
touch "$PIDFILE"
[[ -n "$USEDISTCC" ]] && start_distccd
stop)
[[ ! -f "$PIDFILE" ]] && exit 1
[[ -n "$USEDISTCC" ]] && stop_distccd
if [[ -n "$MANAGEPARTITION" ]]; then
umount -R -A -l "$MOUNTPOINT"
else
dirs=(/home /dev/pts /dev /tmp)
[[ -n "$USEDISTCC" ]] && stop_distccd
umount "$MOUNTPOINT"/{sys,proc}
for d in "${dirs[@]}"; do
umount -l "$MOUNTPOINT$d"
done
fi
rm -f "$PIDFILE"
echo "usage: $0 (start|stop)"
exit 1
esac
Any ideas as to what's going on? -
I have a simple system set up in virtualbox, mostly to browse and torrent. Rarely have major problems. Recently I realized that cron was not working when flexget was not activated as expected. A check of journalctl threw up repeated instances of the following:
Jun 04 15:41:11 arch32VB systemd[1]: systemd-logind.service operation timed out. Terminating.
Jun 04 15:41:11 arch32VB systemd[1]: Failed to start Login Service.
Jun 04 15:41:11 arch32VB systemd[1]: Unit systemd-logind.service entered failed state.
Jun 04 15:41:11 arch32VB systemd[1]: systemd-logind.service holdoff time over, scheduling restart.
Jun 04 15:41:11 arch32VB systemd[1]: Stopping Login Service...
Jun 04 15:41:11 arch32VB systemd[1]: Starting Login Service...
Jun 04 15:41:11 arch32VB systemd-logind[665]: Watching system buttons on /dev/input/event3 (Power Button)
Jun 04 15:41:11 arch32VB systemd-logind[665]: Watching system buttons on /dev/input/event4 (Sleep Button)
Jun 04 15:41:11 arch32VB systemd-logind[665]: New seat seat0.
Jun 04 15:41:11 arch32VB systemd-logind[665]: New session 1 of user calvin.
Jun 04 15:42:41 arch32VB systemd[1]: systemd-logind.service operation timed out. Terminating.
Jun 04 15:42:41 arch32VB systemd[1]: Failed to start Login Service.
Jun 04 15:42:41 arch32VB systemd[1]: Unit systemd-logind.service entered failed state.
Jun 04 15:42:41 arch32VB systemd[1]: systemd-logind.service holdoff time over, scheduling restart.
Jun 04 15:42:41 arch32VB systemd[1]: Stopping Login Service...
Jun 04 15:42:41 arch32VB systemd[1]: Starting Login Service...
Jun 04 15:42:41 arch32VB systemd-logind[693]: Watching system buttons on /dev/input/event3 (Power Button)
Jun 04 15:42:41 arch32VB systemd-logind[693]: Watching system buttons on /dev/input/event4 (Sleep Button)
Jun 04 15:42:41 arch32VB systemd-logind[693]: New seat seat0.
Jun 04 15:42:41 arch32VB systemd-logind[693]: New session 1 of user calvin.
I use autologin to console (and then to X via bash_profile) and there is no glitch except that I find that getting to desktop takes a little longer these days. Thought it is due to psd. I have no idea when this happened as things have been OK.
Any advice? I suspect that cron's failure is due to this issue though honestly I have no basis to think so. Systemctl shows cronie.service loaded and running. System is up to date.With all the changes over the past year, I have been wanting to set up a fresh installation to remove any old issues that might not have been properly dealt with over time. This current issue, and the fact that the move to consolidate everything to /usr/bin has happened, tilted the balance.
New installation, login is OK, no repeated messages from systemd-logind, cronie is working.
Why the problems, I have no idea. But the new installation is working well.
Maybe you are looking for
-
I downloaded an Adobe file from my email (service provider is MWeb) but now cannot find it on my hard drive and it's not in the recycle bin. It does, however, appear in Firefox downloads but I'm unable to open it from there. How can I recover the fil
-
Bluetooth issues with car with iOS 8.0.2 and iPhone 5
I am still experiencing issues with connection my phone to my brand new car, after updating to iOS8, and now iOS 8.0.2. I can connect to the bluetooth, but this gives me a phantom call, my car keeps telling me that an incoming call is inbound. I cann
-
Just replaced a lost lumia 822 and now i can't get it activated.
What do I need to do to activate my replacement lumia? i was unable to connect to verizon or anything.
-
Unable to use option key on startup
My Macbook Pro is running Yosemite (version 10.10) and runs Windows 7 through Boot Camp. Until now I have been able to hold down the Option key on startup to enable me to select OS X or Windows. Starting today the option key does not make any dif
-
SMTP Error 5.7.1 Unable to relay - from webmail interface
Hi, This is some strange problem i faced for the first time. Below Messaging Version on Solaris 10 which is working fine. Sun Java(tm) System Messaging Server 6.2-7.05 (built Sep 5 2006) libimta.so 6.2-7.05 (built 12:18:44, Sep 5 2006) Sometimes (ver