[SOLVED] systemd-journald errors

I set up a MythTV box the other day based on Arch (basically Arch+Openbox+Mythtv) and I get strange errors on shut down. It goes by extremely fast, but what I'm able to catch is:
systemd-journald failed to write entry 25 items
And some other stuff.
I'm not sure if it's related but in dmesg I see:
File /var/log/journal/eaa2513b7edf4267912b45e38d85d0e1/user-1000.journal corrupted or uncleanly shut down, renaming and replacing
I've deleted the entire /var/log/journal/eaa2513b7edf4267912b45e38d85d0e1 folder so it would be regenerated, but it didn't help.
Also, I've Googled this issue and found a bunch of topics with symptoms that match mine, but none of them have any solutions.
Last edited by jlacroix (2014-02-02 05:15:28)

WonderWoofy wrote:
I don't know, that is why I posed the possibility of sending an upstream report as a question...
Have you tried XBMC?  I use that and it is pretty great (of course I have no other point of comparison).  It also appears to have infrared remote control support (lirc) and also has android remote control application that works quite well (and some nice unofficial ones as well).
No, I've not had a reason to try XBMC because MythTV has worked so well for me. I'm not sure what XBMC's capabilities are, but in Myth TV I was able to create custom menus using XML for my games, which is very helpful (I prefer to do this by hand, so I avoid the mythgame plugin). This HTPC is working _extremely_ well, I'm just trying to eliminate errors so I can take a clean image of it in case it needs to be restored down the road. I noticed another error regarding cgroup stating "option or name mismatch" on shut down which from what I'm reading appears to be harmless but I'm still investigating this one.

Similar Messages

  • (Solved) systemd-journald extremely high CPU usage

    I started noticing this problem a few days ago, but I thought it was because I was running too much with too little RAM. But when running nothing more than a KDE desktop, my CPU usage bounces between 50% and 100%, making things laggy. It looks like systemd-journald is to blame, as it is using 50% of the CPU. This is an AMD Phenom II dual core, so this definitely shouldn't be happening. I noticed journal logs were more than 2 GB, so I deleted everything within /var/log/journal/. Rebooted, no change, so I disabled journal storage, but that did not solve the problem.
    Nothing in the logs looks like a problem to me:
    $ sudo journalctl
    -- Logs begin at Tue 2013-03-12 17:31:37 PDT, end at Tue 2013-03-12 18:15:56 PDT. --
    Mar 12 17:31:37 silverstone systemd-journal[149]: Allowing runtime journal files to grow to 298.6M.
    Mar 12 17:31:37 silverstone kernel: Initializing cgroup subsys cpuset
    Mar 12 17:31:37 silverstone kernel: Initializing cgroup subsys cpu
    Mar 12 17:31:37 silverstone kernel: Linux version 3.7.10-1-ARCH (tobias@T-POWA-LX) (gcc version 4.7.2 (G
    Mar 12 17:31:37 silverstone kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=31669ea0-76db
    Mar 12 17:31:37 silverstone kernel: e820: BIOS-provided physical RAM map:
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x00000000000e2000-0x00000000000fffff] reserved
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000cff8ffff] usable
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x00000000cff90000-0x00000000cff9dfff] ACPI data
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x00000000cff9e000-0x00000000cffdffff] ACPI NVS
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x00000000cffe0000-0x00000000cfffffff] reserved
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x00000000ffe00000-0x00000000ffffffff] reserved
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x0000000100000000-0x00000001afffffff] usable
    Mar 12 17:31:37 silverstone kernel: NX (Execute Disable) protection: active
    Mar 12 17:31:37 silverstone kernel: SMBIOS 2.5 present.
    Mar 12 17:31:37 silverstone kernel: DMI: MSI MS-7642/890GXM-G65 (MS-7642) , BIOS V1.2 03/31/2010
    Mar 12 17:31:37 silverstone kernel: e820: update [mem 0x00000000-0x0000ffff] usable ==> reserved
    Mar 12 17:31:37 silverstone kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
    Mar 12 17:31:37 silverstone kernel: No AGP bridge found
    Mar 12 17:31:37 silverstone kernel: e820: last_pfn = 0x1b0000 max_arch_pfn = 0x400000000
    Mar 12 17:31:37 silverstone kernel: MTRR default type: uncachable
    Mar 12 17:31:37 silverstone kernel: MTRR fixed ranges enabled:
    Mar 12 17:31:37 silverstone kernel: 00000-9FFFF write-back
    Mar 12 17:31:37 silverstone kernel: A0000-EFFFF uncachable
    Mar 12 17:31:37 silverstone kernel: F0000-FFFFF write-protect
    Mar 12 17:31:37 silverstone kernel: MTRR variable ranges enabled:
    Mar 12 17:31:37 silverstone kernel: 0 base 000000000000 mask FFFF80000000 write-back
    Mar 12 17:31:37 silverstone kernel: 1 base 000080000000 mask FFFFC0000000 write-back
    Mar 12 17:31:37 silverstone kernel: 2 base 0000C0000000 mask FFFFF0000000 write-back
    Mar 12 17:31:37 silverstone kernel: 3 disabled
    Mar 12 17:31:37 silverstone kernel: 4 disabled
    Mar 12 17:31:37 silverstone kernel: 5 disabled
    Mar 12 17:31:37 silverstone kernel: 6 disabled
    Mar 12 17:31:37 silverstone kernel: 7 disabled
    Mar 12 17:31:37 silverstone kernel: TOM2: 00000001b0000000 aka 6912M
    Mar 12 17:31:37 silverstone kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    Mar 12 17:31:37 silverstone kernel: e820: update [mem 0xd0000000-0xffffffff] usable ==> reserved
    Mar 12 17:31:37 silverstone kernel: e820: last_pfn = 0xcff90 max_arch_pfn = 0x400000000
    Mar 12 17:31:37 silverstone kernel: found SMP MP-table at [mem 0x000ff780-0x000ff78f] mapped at [ffff880
    Mar 12 17:31:37 silverstone kernel: initial memory mapped: [mem 0x00000000-0x1fffffff]
    Mar 12 17:31:37 silverstone kernel: Base memory trampoline at [ffff880000099000] 99000 size 24576
    $ systemctl status systemd-journald
    systemd-journald.service - Journal Service
    Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static)
    Active: active (running) since Tue 2013-03-12 18:10:41 PDT; 8min ago
    Docs: man:systemd-journald.service(8)
    man:journald.conf(5)
    Main PID: 142 (systemd-journal)
    Status: "Processing requests..."
    CGroup: name=systemd:/system/systemd-journald.service
    `-142 /usr/lib/systemd/systemd-journald
    However, it looks like the log files keep getting corrupted:
    $ sudo journalctl --verify
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@5e6edd359123491f9998a310206ccbf9-000000000007f543-0004d7c4445effa4.journal
    Invalid object contents at 124687944ââââââââââââââââââââââââââââââââââââââââââ 49%
    File corruption detected at /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000a8cb7-0004d7c3d52e9748.journal:124687944 (of 134074368, 92%).
    FAIL: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000a8cb7-0004d7c3d52e9748.journal (Bad message)
    Invalid object contents at 75715936âââââââââââââââââââââââââââââââââââââââââââ 49%
    File corruption detected at /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system.journal:75715936 (of 76156928, 99%).
    FAIL: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system.journal (Bad message)
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000290d6-0004d7c3a0033472.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@5e6edd359123491f9998a310206ccbf9-0000000000000001-0004d7c413227650.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/[email protected]~
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000fcfc0-0004d7c3fd8ee9c5.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/[email protected]~
    Invalid object contents at 124701856ââââââââââââââââââââââââââââââââââââââââââ 49%
    File corruption detected at /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-0000000000000001-0004d7c3876dda65.journal:124701856 (of 134049792, 93%).
    FAIL: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-0000000000000001-0004d7c3876dda65.journal (Bad message)
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@5e6edd359123491f9998a310206ccbf9-00000000000a9da8-0004d7c45187e39e.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000d26b1-0004d7c3ea1b73f7.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@5e6edd359123491f9998a310206ccbf9-000000000002a43f-0004d7c425785944.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000539fb-0004d7c3b2d1f935.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@5e6edd359123491f9998a310206ccbf9-0000000000054d23-0004d7c4354da4ef.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/user-1000@2c1af599e637441985385fe37ded2a2c-0000000000001706-0004d7c38cd3de88.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/user-1000@5e6edd359123491f9998a310206ccbf9-00000000000019b4-0004d7c4153f8628.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-000000000007e345-0004d7c3c3ed8197.journal
    I am using a two or three year old SSD, so maybe it has gotten some bad sectors? But that doesn't explain why journald still bricks things when it isn't logging anything. The install is 10 months old, and I switched from init to systemd around October. Is there anything I can do, short of reinstalling?
    Thanks,
    Nicholas
    Last edited by bicyclingrevolution (2013-03-14 05:57:13)

    Thanks for the tip ilkyest, but it didn't make any difference to the systemd-journald problem.
    However, I looked at journalctl again and found it cluttered with CUPS failures:
    -- Logs begin at Tue 2013-03-12 19:17:00 PDT, end at Wed 2013-03-13 22:31:31 PDT. --
    Mar 12 19:17:00 silverstone spideroak_inotify[796]: Program started
    Mar 12 19:21:30 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:30 silverstone systemd-journal[143]: Suppressed 7199 messages from /system
    Mar 12 19:21:27 silverstone systemd[1]: Starting CUPS Printing Service...
    Mar 12 19:21:30 silverstone systemd-journal[143]: Suppressed 5471 messages from /system
    Mar 12 19:21:27 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:30 silverstone systemd-journal[143]: Suppressed 5699 messages from /system
    Mar 12 19:21:27 silverstone systemd[1]: Failed to start CUPS Printing Service.
    Mar 12 19:21:27 silverstone systemd[1]: Starting CUPS Printing Service...
    Mar 12 19:21:27 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:27 silverstone systemd[1]: Failed to start CUPS Printing Service.
    Mar 12 19:21:27 silverstone systemd[1]: Starting CUPS Printing Service...
    Mar 12 19:21:27 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:27 silverstone systemd[1]: Failed to start CUPS Printing Service.
    Mar 12 19:21:27 silverstone systemd[1]: Starting CUPS Printing Service...
    Mar 12 19:21:27 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:30 silverstone systemd-coredump[1592]: Process 1590 (cupsd) dumped core.
    Mar 12 19:21:28 silverstone colord[354]: Profile added: Deskjet_3840-Gray..
    Mar 12 19:21:28 silverstone colord[354]: Profile added: Deskjet_3840-RGB..
    Mar 12 19:21:28 silverstone colord[354]: Device added: cups-Deskjet_3840
    Mar 12 19:21:28 silverstone colord[354]: Profile added: Deskjet_F4100-Gray..
    Mar 12 19:21:28 silverstone colord[354]: Profile added: Deskjet_F4100-RGB..
    Mar 12 19:21:28 silverstone colord[354]: Device added: cups-Deskjet_F4100
    Mar 12 19:21:28 silverstone dbus[337]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
    Mar 12 19:21:28 silverstone dbus[337]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs
    Mar 12 19:21:28 silverstone colord[354]: Profile removed: Deskjet_3840-Gray..
    Mar 12 19:21:28 silverstone colord[354]: Profile removed: Deskjet_3840-RGB..
    Mar 12 19:21:28 silverstone colord[354]: device removed: cups-Deskjet_3840
    Mar 12 19:21:31 silverstone colord[354]: Profile removed: Deskjet_F4100-Gray..
    Mar 12 19:21:31 silverstone colord[354]: Profile removed: Deskjet_F4100-RGB..
    Mar 12 19:21:31 silverstone colord[354]: device removed: cups-Deskjet_F4100
    Mar 12 19:21:31 silverstone dbus-daemon[337]: dbus[337]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
    Mar 12 19:21:31 silverstone dbus-daemon[337]: dbus[337]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or director
    Mar 12 19:21:31 silverstone systemd-journal[143]: Missed 6365 kernel messages
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:31 silverstone cupsd[1590]: Unknown directive DefaultAuthType on line 9.
    Mar 12 19:21:31 silverstone cupsd[1590]: cupsd: client.c:757: avahi_client_get_host_name: Assertion `client' failed.
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:31 silverstone cupsd[1594]: Unknown directive DefaultAuthType on line 9.
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Disabling cups solved the CPU usage issue.
    It looks like the root of the problem is Avahi failing to start, but I have no idea why it isn't working.
    $ systemctl status dbus-org.freedesktop.Avahi.service
    dbus-org.freedesktop.Avahi.service
    Loaded: error (Reason: No such file or directory)
    Active: inactive (dead)

  • [Solved] systemd-journald periodically uses 50% CPU

    Hello!
    I run KDE 4.11 on Arch fully upgraded. Since shortly my system seems to choke periodically at the systemd-journald process. It takes 50% of the CPU power available and everything else is starting to studder and freeze. using jounalctl only shows normal log entries and not (like suggested somewhere else) a huge amount of error entries within seconds.
    I have tried to remedy this:
    - I disabled cups as mentioned somewhere else
    - I deleted all configuration files concerning alsa and pulseaudio (cause I found errors with journalctl) and reinstalled both
    - I set /var/log/journal to "copy on write" because it is on a btrfs partition (another suggestion in a thread)
    - I tried to somehow to disable systemd-journald (seems this is not possible)
    Nothing seems to solve the problem - still my the systemd-journald process peaks to 50% CPU every few minutes and stays at this ressource eating level for a few minutes. Then it drops down to normal again using only minimal ressources for a few minutes ...
    I am lost here. My system is really quite unusable though it is a fresh install from only two weeks ago. I only noticed this behaviour three days ago - afterwards I upgraded to kernel 3.10.9 but this hasn't changed anything either.
    Any ideas anyone?
    thx for reading,
    piedro
    Last edited by piedro (2015-02-08 18:24:45)

    Hi jrusell!
    Well I think I could solve it ... here is what I did:
    - I deleted /var/log/journal
    - rebooted and looked at the fresh log via journalctl: now it generated fresh entries again and there it was: (like in similar problems) the log has been flushed with hundreds fo fail messages! ... something like a "user burst limit exceeded" for rtkit and I found a problem with nepomukindexer (should have guessed it's KDE again - after the update to 4.11)
    - so I stopped all nepomuk stuff and deleted ~/.kde4/share/apps/nepomuk, then let nepomuk trun again recreating the whole indexing database in the process (to be honest it's still in the process but ressources aren't used excessively)
    Since then there hasn't been any problem with the journald process yet ... :-)
    thx everybody for reading,
    p.
    Last edited by piedro (2013-08-26 14:11:32)

  • [SOLVED] systemd-journald & tmpfiles-setup Failures

    Hello,
    I have a weird situation. After I've finished installing my system, I got errors with journald...
    After logging as root I get the following errors:
    systemd-journald[338]: Failed to get machine id: No such file or directory
    systemd-journald[340]: Failed to get machine id: No such file or directory
    systemd-journald[345]: Failed to get machine id: No such file or directory
    systemd-journald[347]: Failed to get machine id: No such file or directory
    systemd-journald[349]: Failed to get machine id: No such file or directory
    systemd[1]: Failed to start Journal Service.
    systemd[1]: Dependency failed for Trigger Flushing of Journal to Presistent Storage.
    systemd[1]: Failed to start Journal Service
    and after I typed
    systemctl
    to see what's more, I got errors at the following:
    systemd-journal-flush.service loaded failed failed
    systemd-journald.service loaded failed failed
    systemd-tmpfiles-setup-dev.service loaded failed failed
    systemd-tmpfiles-setup.service loaded failed failed
    systemd-journald-dev-log.socket loaded failed failed
    systemd-journald.socket loaded failed failed
    and other problems related to the above like
    Failed to start Cleanup of Temporary Directories.
    Note that it is my first time I have problems with journald and tmpfiles-setup and I'm not sure what happened...
    Any help would be very appreciated and thank you very much in advance.
    Last edited by heyom (2014-08-30 09:24:24)

    I just had the same problem while installing a new Arch system. I managed to fix it by running `systemd-machine-id-setup` as root (not sudo).
    Also, before I did that, while installing a package I got an error message about dbus not finding a machine id, and that error message suggested running `dbus-uuidgen > /var/lib/dbus/machine-id` (again as root, not sudo). So, you may need to do that, too.

  • [SOLVED] systemd-udevd errors?

    Hi folks,
    How can I fix these udevd errors and get rid of it? Any help is appreciated! :-)
    errors.log
    Feb 4 18:46:48 localhost [ 8.611130] systemd-udevd[96]: unknown key 'SYSFS{idVendor}' in /etc/udev/rules.d/55-atik.rules:18
    Feb 4 18:46:48 localhost [ 8.611263] systemd-udevd[96]: invalid rule '/etc/udev/rules.d/55-atik.rules:18'
    Feb 4 18:46:48 localhost [ 8.611388] systemd-udevd[96]: unknown key 'SYSFS{idVendor}' in /etc/udev/rules.d/55-atik.rules:19
    Feb 4 18:46:48 localhost [ 8.611511] systemd-udevd[96]: invalid rule '/etc/udev/rules.d/55-atik.rules:19'
    Feb 4 18:46:48 localhost [ 8.611635] systemd-udevd[96]: unknown key 'SYSFS{idVendor}' in /etc/udev/rules.d/55-atik.rules:21
    Feb 4 18:46:48 localhost [ 8.611758] systemd-udevd[96]: invalid rule '/etc/udev/rules.d/55-atik.rules:21'
    Feb 4 18:46:48 localhost [ 8.611881] systemd-udevd[96]: unknown key 'SYSFS{idVendor}' in /etc/udev/rules.d/55-atik.rules:22
    Feb 4 18:46:48 localhost [ 8.612004] systemd-udevd[96]: invalid rule '/etc/udev/rules.d/55-atik.rules:22'
    Feb 4 18:46:48 localhost [ 8.612128] systemd-udevd[96]: unknown key 'SYSFS{idVendor}' in /etc/udev/rules.d/55-atik.rules:24
    Feb 4 18:46:48 localhost [ 8.612250] systemd-udevd[96]: invalid rule '/etc/udev/rules.d/55-atik.rules:24'
    Feb 4 18:46:48 localhost [ 8.612374] systemd-udevd[96]: unknown key 'SYSFS{idVendor}' in /etc/udev/rules.d/55-atik.rules:25
    Feb 4 18:46:48 localhost [ 8.612496] systemd-udevd[96]: invalid rule '/etc/udev/rules.d/55-atik.rules:25'
    Feb 4 18:46:48 localhost [ 8.612620] systemd-udevd[96]: unknown key 'SYSFS{idVendor}' in /etc/udev/rules.d/55-atik.rules:26
    Feb 4 18:46:48 localhost [ 8.612743] systemd-udevd[96]: invalid rule '/etc/udev/rules.d/55-atik.rules:26'
    Feb 4 18:46:48 localhost [ 8.612866] systemd-udevd[96]: unknown key 'SYSFS{idVendor}' in /etc/udev/rules.d/55-atik.rules:27
    Feb 4 18:46:48 localhost [ 8.612989] systemd-udevd[96]: invalid rule '/etc/udev/rules.d/55-atik.rules:27'
    Feb 4 18:46:48 localhost [ 8.613113] systemd-udevd[96]: unknown key 'SYSFS{idVendor}' in /etc/udev/rules.d/55-atik.rules:28
    Feb 4 18:46:48 localhost [ 8.613235] systemd-udevd[96]: invalid rule '/etc/udev/rules.d/55-atik.rules:28'
    Feb 4 18:46:48 localhost [ 8.613440] systemd-udevd[96]: unknown key 'SYSFS{idVendor}' in /etc/udev/rules.d/55-atik.rules:29
    Feb 4 18:46:48 localhost [ 8.613564] systemd-udevd[96]: invalid rule '/etc/udev/rules.d/55-atik.rules:29'
    Feb 4 18:46:48 localhost [ 8.613690] systemd-udevd[96]: unknown key 'SYSFS{idVendor}' in /etc/udev/rules.d/55-atik.rules:33
    Feb 4 18:46:48 localhost [ 8.613813] systemd-udevd[96]: invalid rule '/etc/udev/rules.d/55-atik.rules:33'
    Feb 4 18:46:48 localhost [ 8.632780] systemd-udevd[96]: unknown key 'SYSFS{idVendor}' in /etc/udev/rules.d/55-shoestring.rules:17
    Feb 4 18:46:48 localhost [ 8.632917] systemd-udevd[96]: invalid rule '/etc/udev/rules.d/55-shoestring.rules:17'
    Feb 4 18:46:48 localhost [ 8.633045] systemd-udevd[96]: unknown key 'SYSFS{idVendor}' in /etc/udev/rules.d/55-shoestring.rules:20
    Feb 4 18:46:48 localhost [ 8.633170] systemd-udevd[96]: invalid rule '/etc/udev/rules.d/55-shoestring.rules:20'
    Last edited by OpenEye (2013-02-05 15:21:51)

    falconindy wrote:Did you read your own post? The errors quite clearly point out the invalid rules. SYSFS{$key} hasn't been valid in nearly a year, and has been superseded by ATTR{$key}.
    Thanks for the reply! So what I do? Just replace all SYSFS tags with ATTR tags? Is that correct?

  • [SOLVED] systemd-udev error after fresh install

    I downloaded the last arch install medium (2012-11-01), the installation on my laptop was OK, (just arch as only OS), I use the same CD to install it on my desktop.
    I have windows xp and arch (dual boot) after install arch on my desktop, grub boots just fine, but I ran into the emergency console of systemctl,  ctrl + D give me this:
    "systemd-udevd[805]: worker [835] did not accept message -1 (Connection refused), kill it" over and over again
    and then, the emergency console again.
    here is my fstab
    http://pastebin.com/2Qg8Qa8X
    this is the log (everything is ok before the hard drives)
    http://pastebin.com/Ce5nEWNn
    Last edited by helenaryuu (2012-11-05 02:30:49)

    I install the ntfs-3g and ntfsprogs packages installed via live CD [pacstrap /mnt ntfs-3g ntfsprogs]
    sorry about that

  • [SOLVED] systemd 208 journald process CPU spike on LXC container start

    Hi,
    The problem is that whenever I start an LXC container, systemd-journald process goes on 100% CPU utilization and only stops when I stop the container.
    Setup details:
    % cat /var/lib/lxc/projects/config
    lxc.network.type = veth
    lxc.arch = x86_64
    lxc.utsname = projects
    lxc.network.link = virbr3
    lxc.network.flags = up
    lxc.network.ipv4 = 192.168.200.11
    lxc.rootfs = /mnt/lxc/projects
    lxc.pts = 1000
    lxc.autodev = 1
    lxc.cgroup.memory.limit_in_bytes = 256M
    The rootfs indicated is on a logical volume, /dev/mapper/virtual-projects.
    Details of journal when the spike happened:
    -- Logs begin at Sun 2013-08-04 07:19:25 IST. --
    Oct 05 09:03:30 core systemd[1]: Unit [email protected] entered failed state.
    Oct 05 09:03:30 core kernel: virbr3: port 2(vethl7BeWT) entered disabled state
    Oct 05 09:03:30 core kernel: device vethl7BeWT left promiscuous mode
    Oct 05 09:03:30 core kernel: virbr3: port 2(vethl7BeWT) entered disabled state
    Oct 05 09:03:31 core ntpd[813]: Deleting interface #13 vethl7BeWT, fe80::fcf2:f2ff:fea0:9473#123, interface stats: received=0, sent=0, dropped=0, active_time=11 secs
    Oct 05 09:03:31 core ntpd[813]: peers refreshed
    Oct 05 09:03:40 core dbus-daemon[533]: dbus[533]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service'
    Oct 05 09:03:40 core dbus[533]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service'
    Oct 05 09:03:40 core dbus[533]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory.
    Oct 05 09:03:40 core dbus-daemon[533]: dbus[533]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory.
    Oct 05 09:05:30 core systemd[1]: Starting Linux Container projects...
    Oct 05 09:05:30 core systemd[1]: Started Linux Container projects.
    Oct 05 09:05:30 core systemd-sysctl[4562]: Overwriting earlier assignment of kernel/sysrq in file '/etc/sysctl.d/zz-sysctl.conf'.
    Oct 05 09:05:30 core kernel: device vethmHU7wo entered promiscuous mode
    Oct 05 09:05:30 core kernel: IPv6: ADDRCONF(NETDEV_UP): vethmHU7wo: link is not ready
    Oct 05 09:05:30 core NetworkManager[521]: <warn> /sys/devices/virtual/net/vethSIUSbq: couldn't determine device driver; ignoring...
    Oct 05 09:05:30 core systemd-sysctl[4564]: Overwriting earlier assignment of kernel/sysrq in file '/etc/sysctl.d/zz-sysctl.conf'.
    Oct 05 09:05:30 core kernel: virbr3: topology change detected, propagating
    Oct 05 09:05:30 core kernel: virbr3: port 2(vethmHU7wo) entered forwarding state
    Oct 05 09:05:30 core kernel: virbr3: port 2(vethmHU7wo) entered forwarding state
    Oct 05 09:05:30 core kernel: virbr3: port 2(vethmHU7wo) entered disabled state
    Oct 05 09:05:30 core NetworkManager[521]: <warn> /sys/devices/virtual/net/vethmHU7wo: couldn't determine device driver; ignoring...
    Oct 05 09:05:30 core kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethmHU7wo: link becomes ready
    Oct 05 09:05:30 core kernel: virbr3: topology change detected, propagating
    Oct 05 09:05:30 core kernel: virbr3: port 2(vethmHU7wo) entered forwarding state
    Oct 05 09:05:30 core kernel: virbr3: port 2(vethmHU7wo) entered forwarding state
    Oct 05 09:05:30 core libvirtd[809]: nl_recv returned with error: No buffer space available
    Oct 05 09:05:30 core upowerd[660]: (upowerd:660): UPower-Linux-WARNING **: treating add event as change event on /org/freedesktop/UPower/devices/line_power_AC0
    Oct 05 09:05:30 core systemd-logind[516]: Watching system buttons on /dev/input/event3 (Power Button)
    Oct 05 09:05:30 core upowerd[660]: (upowerd:660): UPower-Linux-WARNING **: treating add event as change event on /org/freedesktop/UPower/devices/battery_BAT0
    Oct 05 09:05:30 core systemd-logind[516]: Watching system buttons on /dev/input/event5 (Video Bus)
    Oct 05 09:05:30 core systemd-logind[516]: Watching system buttons on /dev/input/event2 (Sleep Button)
    Oct 05 09:05:30 core systemd-logind[516]: Watching system buttons on /dev/input/event1 (Lid Switch)
    Oct 05 09:05:30 core systemd-logind[516]: Watching system buttons on /dev/input/event4 (Video Bus)
    Oct 05 09:05:30 core mtp-probe[4711]: checking bus 3, device 4: "/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2"
    Oct 05 09:05:30 core mtp-probe[4712]: checking bus 3, device 5: "/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.4"
    Oct 05 09:05:30 core mtp-probe[4711]: bus: 3, device: 4 was not an MTP device
    Oct 05 09:05:30 core mtp-probe[4712]: bus: 3, device: 5 was not an MTP device
    Oct 05 09:05:30 core systemd-udevd[4561]: error opening ATTR{/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.4/3-1.4:1.0/host6/scsi_host/host6/link_power_management_policy} for writing: No such file or directory
    Oct 05 09:05:32 core ntpd[813]: Listen normally on 14 vethmHU7wo fe80::fcf0:74ff:fe68:aade UDP 123
    Oct 05 09:05:32 core ntpd[813]: peers refreshed
    Oct 05 09:05:32 core ntpd[813]: new interface(s) found: waking up resolver
    Oct 05 09:05:40 core dbus-daemon[533]: dbus[533]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service'
    Oct 05 09:05:40 core dbus[533]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service'
    Oct 05 09:05:40 core dbus[533]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory.
    Oct 05 09:05:40 core dbus-daemon[533]: dbus[533]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory.
    Oct 05 09:06:15 core kernel: EXT4-fs (dm-10): re-mounted. Opts: commit=600
    Oct 05 09:06:15 core kernel: EXT4-fs (dm-12): re-mounted. Opts: acl,commit=600
    Oct 05 09:06:15 core kernel: EXT4-fs (dm-18): re-mounted. Opts: commit=600
    Oct 05 09:06:15 core kernel: EXT4-fs (sda1): re-mounted. Opts: commit=600
    Oct 05 09:06:16 core kernel: EXT4-fs (sda4): re-mounted. Opts: acl,commit=600
    Oct 05 09:06:21 core kernel: EXT4-fs (dm-10): re-mounted. Opts: commit=0
    Oct 05 09:06:21 core kernel: EXT4-fs (dm-12): re-mounted. Opts: acl,commit=0
    Oct 05 09:06:21 core kernel: EXT4-fs (dm-18): re-mounted. Opts: commit=0
    Oct 05 09:06:21 core kernel: EXT4-fs (sda1): re-mounted. Opts: commit=0
    Oct 05 09:06:28 core kernel: EXT4-fs (dm-10): re-mounted. Opts: commit=600
    Oct 05 09:06:28 core kernel: EXT4-fs (dm-12): re-mounted. Opts: acl,commit=600
    Oct 05 09:06:28 core kernel: EXT4-fs (dm-18): re-mounted. Opts: commit=600
    Oct 05 09:06:28 core kernel: EXT4-fs (sda1): re-mounted. Opts: commit=600
    Oct 05 09:06:28 core kernel: EXT4-fs (sda4): re-mounted. Opts: acl,commit=600
    Oct 05 09:06:31 core kernel: EXT4-fs (dm-10): re-mounted. Opts: commit=0
    Oct 05 09:06:31 core kernel: EXT4-fs (dm-12): re-mounted. Opts: acl,commit=0
    Oct 05 09:06:31 core kernel: EXT4-fs (dm-18): re-mounted. Opts: commit=0
    Oct 05 09:06:31 core kernel: EXT4-fs (sda1): re-mounted. Opts: commit=0
    Oct 05 09:06:38 core systemd[1]: Stopping Linux Container projects...
    Oct 05 09:06:38 core systemd[1]: [email protected]: main process exited, code=exited, status=137/n/a
    Oct 05 09:06:38 core systemd[1]: Stopped Linux Container projects.
    Oct 05 09:06:38 core systemd[1]: Unit [email protected] entered failed state.
    Oct 05 09:06:38 core kernel: virbr3: port 2(vethmHU7wo) entered disabled state
    Oct 05 09:06:38 core kernel: device vethmHU7wo left promiscuous mode
    Oct 05 09:06:38 core kernel: virbr3: port 2(vethmHU7wo) entered disabled state
    Oct 05 09:06:39 core ntpd[813]: Deleting interface #14 vethmHU7wo, fe80::fcf0:74ff:fe68:aade#123, interface stats: received=0, sent=0, dropped=0, active_time=67 secs
    Oct 05 09:06:39 core ntpd[813]: peers refreshed
    Nothing really leaps out to me.
    This only happens on Systemd-208. Rolling back to systemd-207 resolved the issue for now, but I can't help but wonder if I won't have this problem again on systemd-209 or whatever. Is there any additional configuration that I need to do in order to get LXC working properly with systemd 208+?
    Also, I don't know if this is relevant, but I got some filesystem permissions warnings on upgrading (and later downgrading) systemd.
    Last edited by railmaniac (2013-10-12 14:03:47)

    Some journal entries from the guest
    There's a bunch of these:
    ct 12 18:52:24 projects systemd-udevd[30]: Failed to apply ACL on /dev/dri/card0: No such file or directory
    Oct 12 18:52:24 projects systemd-udevd[38]: Failed to apply ACL on /dev/snd/hwC0D3: No such file or directory
    Oct 12 18:52:24 projects systemd-udevd[42]: Failed to apply ACL on /dev/snd/pcmC0D0c: No such file or directory
    Oct 12 18:52:24 projects systemd-udevd[37]: Failed to apply ACL on /dev/snd/hwC0D0: No such file or directory
    Oct 12 18:52:24 projects systemd-udevd[44]: Failed to apply ACL on /dev/snd/pcmC0D3p: No such file or directory
    Oct 12 18:52:24 projects systemd-udevd[43]: Failed to apply ACL on /dev/snd/pcmC0D0p: No such file or directory
    Oct 12 18:52:24 projects systemd-udevd[31]: Failed to apply ACL on /dev/snd/controlC0: No such file or directory
    Oct 12 18:52:24 projects systemd-udevd[35]: inotify_add_watch(7, /dev/sda, 10) failed: No such file or directory
    Oct 12 18:52:24 projects systemd-udevd[36]: Failed to apply ACL on /dev/sr0: No such file or directory
    Oct 12 18:52:24 projects systemd-udevd[34]: Failed to apply ACL on /dev/sg1: No such file or directory
    Oct 12 18:52:24 projects systemd-udevd[28]: Error, opening device '/dev/input/event12': No such file or directory
    Oct 12 18:52:24 projects systemd-udevd[32]: Failed to apply ACL on /dev/video0: No such file or directory
    Oct 12 18:52:24 projects systemd-udevd[25]: inotify_add_watch(7, /dev/sdb, 10) failed: No such file or directory
    Oct 12 18:52:24 projects systemd-udevd[33]: Failed to apply ACL on /dev/kvm: No such file or directory
    Oct 12 18:52:24 projects systemd-udevd[29]: inotify_add_watch(7, /dev/sda1, 10) failed: No such file or directory
    Oct 12 18:52:24 projects systemd[1]: Listening on D-Bus System Message Bus Socket.
    Oct 12 18:52:24 projects systemd-udevd[30]: inotify_add_watch(7, /dev/sda2, 10) failed: No such file or directory
    Oct 12 18:52:24 projects systemd-udevd[27]: Failed to apply ACL on /dev/snd/timer: No such file or directory
    Oct 12 18:52:24 projects systemd[1]: Starting Sockets.
    Oct 12 18:52:24 projects systemd-udevd[35]: inotify_add_watch(7, /dev/sda4, 10) failed: No such file or directory
    Oct 12 18:52:24 projects systemd-udevd[31]: inotify_add_watch(7, /dev/sda3, 10) failed: No such file or directory
    And there's a bunch of these, which seems relevant since the logind part was changed in 208:
    Oct 12 18:52:24 projects systemd-logind[59]: New seat seat0.
    Oct 12 18:52:24 projects systemd[1]: Startup finished in 487ms.
    Oct 12 18:52:24 projects systemd-logind[59]: Failed to open event3: No such file or directory
    Oct 12 18:52:24 projects systemd-logind[59]: Failed to open event5: No such file or directory
    Oct 12 18:52:24 projects systemd-logind[59]: Failed to open event4: No such file or directory
    Oct 12 18:52:24 projects systemd-logind[59]: Failed to open event1: No such file or directory
    Oct 12 18:52:24 projects systemd-logind[59]: Failed to open event2: No such file or directory
    Oct 12 18:52:26 projects systemd-journal[64]: Permanent journal is using 87.6M (max 30.0M, leaving 1.1G of free 4.4G, current limit 30.0M).
    Oct 12 18:52:26 projects systemd-journal[64]: Journal started
    Oct 12 18:52:26 projects systemd[1]: systemd-journald.service: main process exited, code=exited, status=1/FAILURE
    Oct 12 18:52:26 projects systemd[1]: Unit systemd-journald.service entered failed state.
    Oct 12 18:52:26 projects systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage...
    Oct 12 18:52:26 projects systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
    Hmm, just noticed it says systemd-journald exited with FAILURE. This is probably pretty informative to someone.

  • [SOLVED] Some systemd processes (e.g. systemd-journald) can't start.

    After a fresh install on a new laptop (dual boot with Windows 8.1 vie rEFInd) I notice some error messages whilst booting. systemd-journald fails to start, and I also see some errors relating to the creation of the volatile filesystem. It's hard for me to give a lot detail about this as without journaling as I'm not sure how to get the error messages.
    I did see this from dmesg:
    [ 128.638674] systemd[1]: Starting Stop Read-Ahead Data Collection...
    [ 128.662550] systemd[1]: Started Stop Read-Ahead Data Collection.
    [ 194.545294] systemd[1]: Starting Journal Socket (/dev/log).
    [ 194.545391] systemd[1]: Listening on Journal Socket (/dev/log).
    [ 194.545471] systemd[1]: Starting Journal Socket.
    [ 194.545540] systemd[1]: Listening on Journal Socket.
    [ 194.545613] systemd[1]: Starting Journal Service...
    [ 194.546604] systemd[1]: Started Journal Service.
    [ 194.549797] systemd-journald[711]: Failed to get machine id: No such file or directory
    [ 194.553931] systemd[1]: systemd-journald.service has no holdoff time, scheduling restart.
    [ 194.554205] systemd[1]: Stopping Journal Service...
    [ 24.362121] systemd-tmpfiles[330]: [/usr/lib/tmpfiles.d/systemd.conf:26] Failed to replace specifiers: /run/log/journal/%m
    [ 24.364106] systemd-tmpfiles[330]: [/usr/lib/tmpfiles.d/systemd.conf:29] Failed to replace specifiers: /var/log/journal/%m
    [ 24.404888] systemd[1]: systemd-tmpfiles-setup.service: main process exited, code=exited, status=1/FAILURE
    [ 24.409499] systemd[1]: Failed to start Create Volatile Files and Directories.
    [ 24.412303] systemd[1]: Unit systemd-tmpfiles-setup.service entered failed state.
    And if I check the status of journald through systemctl I get:
    systemd-journald.service - Journal Service
    Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static)
    Active: failed (Result: start-limit) since Wed 2014-08-27 10:37:50 UTC; 1h 2min ago
    Docs: man:systemd-journald.service(8)
    man:journald.conf(5)
    Process: 720 ExecStart=/usr/lib/systemd/systemd-journald (code=exited, status=1/FAILURE)
    Main PID: 720 (code=exited, status=1/FAILURE)
    Status: "Shutting down..."
    I've tried reinstalling systemd, and adding systemd to HOOKS in mkinitcpio.conf, neither of these things seem to help. I also can't start the services manually.
    If anybody can help it would be greatly appreciated, thanks!
    Last edited by Tim Butters (2014-08-28 15:49:50)

    Normally, as Loqs said, 'systemd-firstboot --setup-machine-id' should have been run when you first installed the systemd package.
    You can verify if the '/etc/machine-id' file exists:
    $ ls -l /etc/machine-id
    -rw-r--r-- 1 root root 33 25 mars 2009 /etc/machine-id
    If you don't find one, maybe use 'systemd-machine-id-setup' instead to create one.
    But have you seen error messages during the Arch installation? Because that should not be necessary.
    Edit: 'systemd-firstboot' is new in systemd 216, so should not be found in the live installation disk 2014.08.
    Last edited by berbae (2014-08-28 15:44:52)

  • [SOLVED] systemd: no kernel messages in the journal

    Hi
    Currently the journal holds only application logs; I do not see any kernel logs in the journal. This is an old Arch system that was using syslog-ng but was transitioned to systemd when Arch made systemd default. This was working well until about three weeks back, when journal stopped holding kernel messages. The journal was causing journalctl to crash and I couldn't verify the journal since I had FSS setup but forgotten the keys. So, I had disabled the FSS, cleared the journals to startover again. Only to see kernel messages are not getting logged.
    I would be grrateful for any help in resolving the issue. Thank you!
    Last edited by chaembian (2013-11-20 02:53:00)

    OK, I removed the commandline options, regenerated grub config, rebooted.
    journalctl --dmesg starts:
    -- Logs begin at Sun 2013-11-17 23:26:51 IST, end at Sun 2013-11-17 23:35:38 IST. --
    Nov 17 23:26:51 chaembian kernel: input: HDA ATI SB Front Headphone as /devices/pci0000:00/0000:00:14.2/sound/card0/input3
    Nov 17 23:26:51 chaembian kernel: input: HDA ATI SB Line Out Side as /devices/pci0000:00/0000:00:14.2/sound/card0/input4
    Nov 17 23:26:51 chaembian kernel: input: HDA ATI SB Line Out CLFE as /devices/pci0000:00/0000:00:14.2/sound/card0/input5
    Nov 17 23:26:51 chaembian kernel: input: HDA ATI SB Line Out Surround as /devices/pci0000:00/0000:00:14.2/sound/card0/input6
    Nov 17 23:26:51 chaembian kernel: input: HDA ATI SB Line Out Front as /devices/pci0000:00/0000:00:14.2/sound/card0/input7
    Nov 17 23:26:51 chaembian kernel: input: HDA ATI SB Line as /devices/pci0000:00/0000:00:14.2/sound/card0/input8
    Nov 17 23:26:51 chaembian kernel: input: HDA ATI SB Rear Mic as /devices/pci0000:00/0000:00:14.2/sound/card0/input9
    Nov 17 23:26:51 chaembian kernel: input: HDA ATI SB Front Mic as /devices/pci0000:00/0000:00:14.2/sound/card0/input10
    Nov 17 23:26:51 chaembian kernel: snd_hda_intel 0000:01:05.1: setting latency timer to 64
    Nov 17 23:26:51 chaembian kernel: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:05.1/sound/card1/input11
    Nov 17 23:26:51 chaembian kernel: microcode: CPU0: new patch_level=0x010000c8
    Nov 17 23:26:51 chaembian kernel: microcode: CPU1: patch_level=0x010000b6
    Nov 17 23:26:51 chaembian kernel: microcode: CPU1: new patch_level=0x010000c8
    Nov 17 23:26:51 chaembian kernel: microcode: CPU2: patch_level=0x010000b6
    Nov 17 23:26:51 chaembian kernel: microcode: CPU2: new patch_level=0x010000c8
    Nov 17 23:26:51 chaembian kernel: microcode: CPU3: patch_level=0x010000b6
    Nov 17 23:26:51 chaembian kernel: microcode: CPU3: new patch_level=0x010000c8
    Nov 17 23:26:51 chaembian kernel: microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
    Nov 17 23:26:51 chaembian kernel: media: Linux media interface: v0.10
    Nov 17 23:26:51 chaembian kernel: Linux video capture interface: v2.00
    Nov 17 23:26:51 chaembian kernel: kvm: Nested Virtualization enabled
    Nov 17 23:26:51 chaembian kernel: kvm: Nested Paging enabled
    Nov 17 23:26:52 chaembian kernel: hidraw: raw HID events driver (C) Jiri Kosina
    That is indeed a step in the right direction.
    dmesg for cross-reference
    [ 0.000000] Initializing cgroup subsys cpuset
    [ 0.000000] Initializing cgroup subsys cpu
    [ 0.000000] Initializing cgroup subsys cpuacct
    [ 0.000000] Linux version 3.11.6-1-ARCH (nobody@var-lib-archbuild-extra-x86_64-thomas) (gcc version 4.8.1 20130725 (prerelease) (GCC) ) #1 SMP PREEMPT Fri Oct 18 23:22:36 CEST 2013
    [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=639e14d4-e548-48ed-a6e5-c73a19c618ff rw quiet
    [ 0.000000] e820: BIOS-provided physical RAM map:
    [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009abff] usable
    [ 0.000000] BIOS-e820: [mem 0x000000000009ac00-0x000000000009ffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000000e2000-0x00000000000fffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000cff7ffff] usable
    [ 0.000000] BIOS-e820: [mem 0x00000000cff80000-0x00000000cff97fff] ACPI data
    [ 0.000000] BIOS-e820: [mem 0x00000000cff98000-0x00000000cffcffff] ACPI NVS
    [ 0.000000] BIOS-e820: [mem 0x00000000cffd0000-0x00000000cfffffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000ffa00000-0x00000000ffffffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000011fffffff] usable
    [ 0.000000] NX (Execute Disable) protection: active
    [ 0.000000] SMBIOS 2.5 present.
    [ 0.000000] DMI: System manufacturer System Product Name/M4A88TD-M EVO, BIOS 1702 12/10/2010
    [ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
    [ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
    [ 0.000000] No AGP bridge found
    [ 0.000000] e820: last_pfn = 0x120000 max_arch_pfn = 0x400000000
    [ 0.000000] MTRR default type: uncachable
    [ 0.000000] MTRR fixed ranges enabled:
    [ 0.000000] 00000-9FFFF write-back
    [ 0.000000] A0000-EFFFF uncachable
    [ 0.000000] F0000-FFFFF write-protect
    [ 0.000000] MTRR variable ranges enabled:
    [ 0.000000] 0 base 000000000000 mask FFFF80000000 write-back
    [ 0.000000] 1 base 000080000000 mask FFFFC0000000 write-back
    [ 0.000000] 2 base 0000C0000000 mask FFFFF0000000 write-back
    [ 0.000000] 3 disabled
    [ 0.000000] 4 disabled
    [ 0.000000] 5 disabled
    [ 0.000000] 6 disabled
    [ 0.000000] 7 disabled
    [ 0.000000] TOM2: 0000000130000000 aka 4864M
    [ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    [ 0.000000] e820: update [mem 0xd0000000-0xffffffff] usable ==> reserved
    [ 0.000000] e820: last_pfn = 0xcff80 max_arch_pfn = 0x400000000
    [ 0.000000] found SMP MP-table at [mem 0x000ff780-0x000ff78f] mapped at [ffff8800000ff780]
    [ 0.000000] Scanning 1 areas for low memory corruption
    [ 0.000000] Base memory trampoline at [ffff880000094000] 94000 size 24576
    [ 0.000000] Using GB pages for direct mapping
    [ 0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
    [ 0.000000] [mem 0x00000000-0x000fffff] page 4k
    [ 0.000000] BRK [0x01b2f000, 0x01b2ffff] PGTABLE
    [ 0.000000] BRK [0x01b30000, 0x01b30fff] PGTABLE
    [ 0.000000] BRK [0x01b31000, 0x01b31fff] PGTABLE
    [ 0.000000] init_memory_mapping: [mem 0x11fe00000-0x11fffffff]
    [ 0.000000] [mem 0x11fe00000-0x11fffffff] page 2M
    [ 0.000000] BRK [0x01b32000, 0x01b32fff] PGTABLE
    [ 0.000000] init_memory_mapping: [mem 0x11c000000-0x11fdfffff]
    [ 0.000000] [mem 0x11c000000-0x11fdfffff] page 2M
    [ 0.000000] init_memory_mapping: [mem 0x100000000-0x11bffffff]
    [ 0.000000] [mem 0x100000000-0x11bffffff] page 2M
    [ 0.000000] init_memory_mapping: [mem 0x00100000-0xcff7ffff]
    [ 0.000000] [mem 0x00100000-0x001fffff] page 4k
    [ 0.000000] [mem 0x00200000-0x3fffffff] page 2M
    [ 0.000000] [mem 0x40000000-0xbfffffff] page 1G
    [ 0.000000] [mem 0xc0000000-0xcfdfffff] page 2M
    [ 0.000000] [mem 0xcfe00000-0xcff7ffff] page 4k
    [ 0.000000] RAMDISK: [mem 0x37690000-0x37b3ffff]
    [ 0.000000] ACPI: RSDP 00000000000fb570 00024 (v02 ACPIAM)
    [ 0.000000] ACPI: XSDT 00000000cff80100 0005C (v01 121010 XSDT1437 20101210 MSFT 00000097)
    [ 0.000000] ACPI: FACP 00000000cff80290 000F4 (v03 121010 FACP1437 20101210 MSFT 00000097)
    [ 0.000000] ACPI: DSDT 00000000cff80450 0F2D6 (v01 A1581 A1581001 00000001 INTL 20060113)
    [ 0.000000] ACPI: FACS 00000000cff98000 00040
    [ 0.000000] ACPI: APIC 00000000cff80390 0007C (v01 121010 APIC1437 20101210 MSFT 00000097)
    [ 0.000000] ACPI: MCFG 00000000cff80410 0003C (v01 121010 OEMMCFG 20101210 MSFT 00000097)
    [ 0.000000] ACPI: OEMB 00000000cff98040 00072 (v01 121010 OEMB1437 20101210 MSFT 00000097)
    [ 0.000000] ACPI: SRAT 00000000cff8f8a0 000E8 (v01 AMD FAM_F_10 00000002 AMD 00000001)
    [ 0.000000] ACPI: HPET 00000000cff8f990 00038 (v01 121010 OEMHPET 20101210 MSFT 00000097)
    [ 0.000000] ACPI: SSDT 00000000cff8f9d0 0088C (v01 A M I POWERNOW 00000001 AMD 00000001)
    [ 0.000000] ACPI: Local APIC address 0xfee00000
    [ 0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
    [ 0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
    [ 0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
    [ 0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
    [ 0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x0009ffff]
    [ 0.000000] SRAT: Node 0 PXM 0 [mem 0x00100000-0xcfffffff]
    [ 0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x12fffffff]
    [ 0.000000] NUMA: Node 0 [mem 0x00000000-0x0009ffff] + [mem 0x00100000-0xcfffffff] -> [mem 0x00000000-0xcfffffff]
    [ 0.000000] NUMA: Node 0 [mem 0x00000000-0xcfffffff] + [mem 0x100000000-0x11fffffff] -> [mem 0x00000000-0x11fffffff]
    [ 0.000000] Initmem setup node 0 [mem 0x00000000-0x11fffffff]
    [ 0.000000] NODE_DATA [mem 0x11fff9000-0x11fffdfff]
    [ 0.000000] [ffffea0000000000-ffffea00047fffff] PMD -> [ffff88011ba00000-ffff88011f5fffff] on node 0
    [ 0.000000] Zone ranges:
    [ 0.000000] DMA [mem 0x00001000-0x00ffffff]
    [ 0.000000] DMA32 [mem 0x01000000-0xffffffff]
    [ 0.000000] Normal [mem 0x100000000-0x11fffffff]
    [ 0.000000] Movable zone start for each node
    [ 0.000000] Early memory node ranges
    [ 0.000000] node 0: [mem 0x00001000-0x00099fff]
    [ 0.000000] node 0: [mem 0x00100000-0xcff7ffff]
    [ 0.000000] node 0: [mem 0x100000000-0x11fffffff]
    [ 0.000000] On node 0 totalpages: 982809
    [ 0.000000] DMA zone: 64 pages used for memmap
    [ 0.000000] DMA zone: 21 pages reserved
    [ 0.000000] DMA zone: 3993 pages, LIFO batch:0
    [ 0.000000] DMA32 zone: 13246 pages used for memmap
    [ 0.000000] DMA32 zone: 847744 pages, LIFO batch:31
    [ 0.000000] Normal zone: 2048 pages used for memmap
    [ 0.000000] Normal zone: 131072 pages, LIFO batch:31
    [ 0.000000] ACPI: PM-Timer IO Port: 0x808
    [ 0.000000] ACPI: Local APIC address 0xfee00000
    [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x84] disabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x85] disabled)
    [ 0.000000] ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
    [ 0.000000] IOAPIC[0]: apic_id 4, version 33, address 0xfec00000, GSI 0-23
    [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
    [ 0.000000] ACPI: IRQ0 used by override.
    [ 0.000000] ACPI: IRQ2 used by override.
    [ 0.000000] ACPI: IRQ9 used by override.
    [ 0.000000] Using ACPI (MADT) for SMP configuration information
    [ 0.000000] ACPI: HPET id: 0x8300 base: 0xfed00000
    [ 0.000000] smpboot: Allowing 6 CPUs, 2 hotplug CPUs
    [ 0.000000] nr_irqs_gsi: 40
    [ 0.000000] PM: Registered nosave memory: [mem 0x0009a000-0x0009afff]
    [ 0.000000] PM: Registered nosave memory: [mem 0x0009b000-0x0009ffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000e1fff]
    [ 0.000000] PM: Registered nosave memory: [mem 0x000e2000-0x000fffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xcff80000-0xcff97fff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xcff98000-0xcffcffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xcffd0000-0xcfffffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xd0000000-0xff9fffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xffa00000-0xffffffff]
    [ 0.000000] e820: [mem 0xd0000000-0xff9fffff] available for PCI devices
    [ 0.000000] Booting paravirtualized kernel on bare hardware
    [ 0.000000] setup_percpu: NR_CPUS:128 nr_cpumask_bits:128 nr_cpu_ids:6 nr_node_ids:1
    [ 0.000000] PERCPU: Embedded 29 pages/cpu @ffff88011fc00000 s86528 r8192 d24064 u262144
    [ 0.000000] pcpu-alloc: s86528 r8192 d24064 u262144 alloc=1*2097152
    [ 0.000000] pcpu-alloc: [0] 0 1 2 3 4 5 - -
    [ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 967430
    [ 0.000000] Policy zone: Normal
    [ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=639e14d4-e548-48ed-a6e5-c73a19c618ff rw quiet
    [ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
    [ 0.000000] Checking aperture...
    [ 0.000000] No AGP bridge found
    [ 0.000000] Node 0: aperture @ c4000000 size 32 MB
    [ 0.000000] Aperture pointing to e820 RAM. Ignoring.
    [ 0.000000] Your BIOS doesn't leave a aperture memory hole
    [ 0.000000] Please enable the IOMMU option in the BIOS setup
    [ 0.000000] This costs you 64 MB of RAM
    [ 0.000000] Mapping aperture over 65536 KB of RAM @ c4000000
    [ 0.000000] PM: Registered nosave memory: [mem 0xc4000000-0xc7ffffff]
    [ 0.000000] Memory: 3720876K/3931236K available (5050K kernel code, 799K rwdata, 1696K rodata, 1140K init, 1288K bss, 210360K reserved)
    [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=6, Nodes=1
    [ 0.000000] Preemptible hierarchical RCU implementation.
    [ 0.000000] RCU dyntick-idle grace-period acceleration is enabled.
    [ 0.000000] Dump stacks of tasks blocking RCU-preempt GP.
    [ 0.000000] RCU restricting CPUs from NR_CPUS=128 to nr_cpu_ids=6.
    [ 0.000000] NR_IRQS:8448 nr_irqs:728 16
    [ 0.000000] spurious 8259A interrupt: IRQ7.
    [ 0.000000] Console: colour dummy device 80x25
    [ 0.000000] console [tty0] enabled
    [ 0.000000] allocated 15728640 bytes of page_cgroup
    [ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
    [ 0.000000] hpet clockevent registered
    [ 0.000000] tsc: Fast TSC calibration using PIT
    [ 0.003333] tsc: Detected 3415.125 MHz processor
    [ 0.000003] Calibrating delay loop (skipped), value calculated using timer frequency.. 6832.84 BogoMIPS (lpj=11383750)
    [ 0.000005] pid_max: default: 32768 minimum: 301
    [ 0.000027] Security Framework initialized
    [ 0.000033] AppArmor: AppArmor disabled by boot time parameter
    [ 0.000034] Yama: becoming mindful.
    [ 0.000231] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
    [ 0.001248] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
    [ 0.001717] Mount-cache hash table entries: 256
    [ 0.001875] Initializing cgroup subsys memory
    [ 0.001885] Initializing cgroup subsys devices
    [ 0.001887] Initializing cgroup subsys freezer
    [ 0.001888] Initializing cgroup subsys net_cls
    [ 0.001889] Initializing cgroup subsys blkio
    [ 0.001904] tseg: 0000000000
    [ 0.001910] CPU: Physical Processor ID: 0
    [ 0.001910] CPU: Processor Core ID: 0
    [ 0.001912] mce: CPU supports 6 MCE banks
    [ 0.001916] LVT offset 0 assigned for vector 0xf9
    [ 0.001919] process: using AMD E400 aware idle routine
    [ 0.001921] Last level iTLB entries: 4KB 512, 2MB 16, 4MB 8
    Last level dTLB entries: 4KB 512, 2MB 128, 4MB 64
    tlb_flushall_shift: 4
    [ 0.001983] Freeing SMP alternatives memory: 20K (ffffffff819e6000 - ffffffff819eb000)
    [ 0.002531] ACPI: Core revision 20130517
    [ 0.006010] ACPI: All ACPI Tables successfully acquired
    [ 0.109344] ftrace: allocating 20100 entries in 79 pages
    [ 0.116210] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    [ 0.149233] smpboot: CPU0: AMD Phenom(tm) II X4 965 Processor (fam: 10, model: 04, stepping: 03)
    [ 0.253603] Performance Events: AMD PMU driver.
    [ 0.253606] ... version: 0
    [ 0.253607] ... bit width: 48
    [ 0.253608] ... generic registers: 4
    [ 0.253609] ... value mask: 0000ffffffffffff
    [ 0.253609] ... max period: 00007fffffffffff
    [ 0.253610] ... fixed-purpose events: 0
    [ 0.253611] ... event mask: 000000000000000f
    [ 0.253639] process: System has AMD C1E enabled
    [ 0.253645] process: Switch to broadcast mode on CPU0
    [ 0.270404] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
    [ 0.290256] process: Switch to broadcast mode on CPU1
    [ 0.306943] process: Switch to broadcast mode on CPU2
    [ 0.277079] smpboot: Booting Node 0, Processors #1 #2 #3
    [ 0.323592] Brought up 4 CPUs
    [ 0.323595] smpboot: Total of 4 processors activated (27331.37 BogoMIPS)
    [ 0.323636] process: Switch to broadcast mode on CPU3
    [ 0.328034] devtmpfs: initialized
    [ 0.329347] PM: Registering ACPI NVS region [mem 0xcff98000-0xcffcffff] (229376 bytes)
    [ 0.330091] RTC time: 17:56:43, date: 11/17/13
    [ 0.330127] NET: Registered protocol family 16
    [ 0.330208] node 0 link 0: io port [1000, ffffff]
    [ 0.330210] TOM: 00000000d0000000 aka 3328M
    [ 0.330212] Fam 10h mmconf [mem 0xe0000000-0xefffffff]
    [ 0.330213] node 0 link 0: mmio [a0000, bffff]
    [ 0.330215] node 0 link 0: mmio [d0000000, efffffff] ==> [d0000000, dfffffff]
    [ 0.330217] node 0 link 0: mmio [f0000000, fe6fffff]
    [ 0.330219] node 0 link 0: mmio [fe700000, fe8fffff]
    [ 0.330220] node 0 link 0: mmio [fe900000, ffdfffff]
    [ 0.330221] TOM2: 0000000130000000 aka 4864M
    [ 0.330222] bus: [bus 00-07] on node 0 link 0
    [ 0.330223] bus: 00 [io 0x0000-0xffff]
    [ 0.330224] bus: 00 [mem 0x000a0000-0x000bffff]
    [ 0.330225] bus: 00 [mem 0xd0000000-0xdfffffff]
    [ 0.330226] bus: 00 [mem 0xf0000000-0xffffffff]
    [ 0.330227] bus: 00 [mem 0x130000000-0xfcffffffff]
    [ 0.330268] ACPI: bus type PCI registered
    [ 0.330269] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
    [ 0.330314] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
    [ 0.330316] PCI: not using MMCONFIG
    [ 0.330317] PCI: Using configuration type 1 for base access
    [ 0.330317] PCI: Using configuration type 1 for extended access
    [ 0.330790] bio: create slab <bio-0> at 0
    [ 0.330911] ACPI: Added _OSI(Module Device)
    [ 0.330913] ACPI: Added _OSI(Processor Device)
    [ 0.330914] ACPI: Added _OSI(3.0 _SCP Extensions)
    [ 0.330915] ACPI: Added _OSI(Processor Aggregator Device)
    [ 0.331704] ACPI: EC: Look up EC in DSDT
    [ 0.343813] ACPI: Executed 3 blocks of module-level executable AML code
    [ 0.657725] ACPI: Interpreter enabled
    [ 0.657735] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20130517/hwxface-571)
    [ 0.657746] ACPI: (supports S0 S1 S3 S4 S5)
    [ 0.657748] ACPI: Using IOAPIC for interrupt routing
    [ 0.657763] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
    [ 0.658965] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in ACPI motherboard resources
    [ 0.665871] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
    [ 0.665931] ACPI: No dock devices found.
    [ 0.670245] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
    [ 0.670357] acpi PNP0A03:00: Requesting ACPI _OSC control (0x1d)
    [ 0.670453] acpi PNP0A03:00: ACPI _OSC control (0x1d) granted
    [ 0.670632] PCI host bridge to bus 0000:00
    [ 0.670635] pci_bus 0000:00: root bus resource [bus 00-ff]
    [ 0.670636] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
    [ 0.670638] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
    [ 0.670639] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
    [ 0.670641] pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000dffff]
    [ 0.670642] pci_bus 0000:00: root bus resource [mem 0xd0000000-0xdfffffff]
    [ 0.670643] pci_bus 0000:00: root bus resource [mem 0xf0000000-0xfebfffff]
    [ 0.670652] pci 0000:00:00.0: [1022:9601] type 00 class 0x060000
    [ 0.670728] pci 0000:00:01.0: [1043:9602] type 01 class 0x060400
    [ 0.670791] pci 0000:00:05.0: [1022:9605] type 01 class 0x060400
    [ 0.670818] pci 0000:00:05.0: PME# supported from D0 D3hot D3cold
    [ 0.670846] pci 0000:00:05.0: System wakeup disabled by ACPI
    [ 0.670871] pci 0000:00:07.0: [1022:9607] type 01 class 0x060400
    [ 0.670897] pci 0000:00:07.0: PME# supported from D0 D3hot D3cold
    [ 0.670924] pci 0000:00:07.0: System wakeup disabled by ACPI
    [ 0.670947] pci 0000:00:09.0: [1022:9608] type 01 class 0x060400
    [ 0.670974] pci 0000:00:09.0: PME# supported from D0 D3hot D3cold
    [ 0.671001] pci 0000:00:09.0: System wakeup disabled by ACPI
    [ 0.671023] pci 0000:00:0a.0: [1022:9609] type 01 class 0x060400
    [ 0.671050] pci 0000:00:0a.0: PME# supported from D0 D3hot D3cold
    [ 0.671077] pci 0000:00:0a.0: System wakeup disabled by ACPI
    [ 0.671108] pci 0000:00:11.0: [1002:4391] type 00 class 0x010601
    [ 0.671122] pci 0000:00:11.0: reg 0x10: [io 0x9000-0x9007]
    [ 0.671129] pci 0000:00:11.0: reg 0x14: [io 0x8000-0x8003]
    [ 0.671135] pci 0000:00:11.0: reg 0x18: [io 0x7000-0x7007]
    [ 0.671142] pci 0000:00:11.0: reg 0x1c: [io 0x6000-0x6003]
    [ 0.671149] pci 0000:00:11.0: reg 0x20: [io 0x5000-0x500f]
    [ 0.671156] pci 0000:00:11.0: reg 0x24: [mem 0xfe6ffc00-0xfe6fffff]
    [ 0.671231] pci 0000:00:12.0: [1002:4397] type 00 class 0x0c0310
    [ 0.671241] pci 0000:00:12.0: reg 0x10: [mem 0xfe6fe000-0xfe6fefff]
    [ 0.671303] pci 0000:00:12.0: System wakeup disabled by ACPI
    [ 0.671332] pci 0000:00:12.2: [1002:4396] type 00 class 0x0c0320
    [ 0.671346] pci 0000:00:12.2: reg 0x10: [mem 0xfe6ff800-0xfe6ff8ff]
    [ 0.671405] pci 0000:00:12.2: supports D1 D2
    [ 0.671406] pci 0000:00:12.2: PME# supported from D0 D1 D2 D3hot
    [ 0.671435] pci 0000:00:12.2: System wakeup disabled by ACPI
    [ 0.671464] pci 0000:00:13.0: [1002:4397] type 00 class 0x0c0310
    [ 0.671474] pci 0000:00:13.0: reg 0x10: [mem 0xfe6fd000-0xfe6fdfff]
    [ 0.671536] pci 0000:00:13.0: System wakeup disabled by ACPI
    [ 0.671563] pci 0000:00:13.2: [1002:4396] type 00 class 0x0c0320
    [ 0.671577] pci 0000:00:13.2: reg 0x10: [mem 0xfe6ff400-0xfe6ff4ff]
    [ 0.671635] pci 0000:00:13.2: supports D1 D2
    [ 0.671637] pci 0000:00:13.2: PME# supported from D0 D1 D2 D3hot
    [ 0.671665] pci 0000:00:13.2: System wakeup disabled by ACPI
    [ 0.671691] pci 0000:00:14.0: [1002:4385] type 00 class 0x0c0500
    [ 0.671780] pci 0000:00:14.2: [1002:4383] type 00 class 0x040300
    [ 0.671795] pci 0000:00:14.2: reg 0x10: [mem 0xfe6f4000-0xfe6f7fff 64bit]
    [ 0.671842] pci 0000:00:14.2: PME# supported from D0 D3hot D3cold
    [ 0.671870] pci 0000:00:14.2: System wakeup disabled by ACPI
    [ 0.671893] pci 0000:00:14.3: [1002:439d] type 00 class 0x060100
    [ 0.671979] pci 0000:00:14.4: [1002:4384] type 01 class 0x060401
    [ 0.672026] pci 0000:00:14.4: System wakeup disabled by ACPI
    [ 0.672049] pci 0000:00:14.5: [1002:4399] type 00 class 0x0c0310
    [ 0.672059] pci 0000:00:14.5: reg 0x10: [mem 0xfe6fc000-0xfe6fcfff]
    [ 0.672121] pci 0000:00:14.5: System wakeup disabled by ACPI
    [ 0.672146] pci 0000:00:16.0: [1002:4397] type 00 class 0x0c0310
    [ 0.672156] pci 0000:00:16.0: reg 0x10: [mem 0xfe6f3000-0xfe6f3fff]
    [ 0.672218] pci 0000:00:16.0: System wakeup disabled by ACPI
    [ 0.672245] pci 0000:00:16.2: [1002:4396] type 00 class 0x0c0320
    [ 0.672258] pci 0000:00:16.2: reg 0x10: [mem 0xfe6ff000-0xfe6ff0ff]
    [ 0.672317] pci 0000:00:16.2: supports D1 D2
    [ 0.672318] pci 0000:00:16.2: PME# supported from D0 D1 D2 D3hot
    [ 0.672347] pci 0000:00:16.2: System wakeup disabled by ACPI
    [ 0.672372] pci 0000:00:18.0: [1022:1200] type 00 class 0x060000
    [ 0.672416] pci 0000:00:18.1: [1022:1201] type 00 class 0x060000
    [ 0.672457] pci 0000:00:18.2: [1022:1202] type 00 class 0x060000
    [ 0.672499] pci 0000:00:18.3: [1022:1203] type 00 class 0x060000
    [ 0.672542] pci 0000:00:18.4: [1022:1204] type 00 class 0x060000
    [ 0.672618] pci 0000:01:05.0: [1002:9715] type 00 class 0x030000
    [ 0.672624] pci 0000:01:05.0: reg 0x10: [mem 0xd0000000-0xdfffffff pref]
    [ 0.672628] pci 0000:01:05.0: reg 0x14: [io 0xa000-0xa0ff]
    [ 0.672632] pci 0000:01:05.0: reg 0x18: [mem 0xfe8f0000-0xfe8fffff]
    [ 0.672639] pci 0000:01:05.0: reg 0x24: [mem 0xfe700000-0xfe7fffff]
    [ 0.672654] pci 0000:01:05.0: supports D1 D2
    [ 0.672678] pci 0000:01:05.1: [1002:970f] type 00 class 0x040300
    [ 0.672684] pci 0000:01:05.1: reg 0x10: [mem 0xfe8e8000-0xfe8ebfff]
    [ 0.672709] pci 0000:01:05.1: supports D1 D2
    [ 0.672750] pci 0000:00:01.0: PCI bridge to [bus 01]
    [ 0.672753] pci 0000:00:01.0: bridge window [io 0xa000-0xafff]
    [ 0.672755] pci 0000:00:01.0: bridge window [mem 0xfe700000-0xfe8fffff]
    [ 0.672758] pci 0000:00:01.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
    [ 0.672796] pci 0000:02:00.0: [1033:0194] type 00 class 0x0c0330
    [ 0.672810] pci 0000:02:00.0: reg 0x10: [mem 0xfe9fe000-0xfe9fffff 64bit]
    [ 0.672875] pci 0000:02:00.0: PME# supported from D0 D3hot
    [ 0.680606] pci 0000:00:05.0: PCI bridge to [bus 02]
    [ 0.680611] pci 0000:00:05.0: bridge window [mem 0xfe900000-0xfe9fffff]
    [ 0.680673] pci 0000:03:00.0: [1106:3403] type 00 class 0x0c0010
    [ 0.680702] pci 0000:03:00.0: reg 0x10: [mem 0xfeaff800-0xfeafffff 64bit]
    [ 0.680717] pci 0000:03:00.0: reg 0x18: [io 0xb800-0xb8ff]
    [ 0.680838] pci 0000:03:00.0: supports D2
    [ 0.680839] pci 0000:03:00.0: PME# supported from D2 D3hot D3cold
    [ 0.690631] pci 0000:00:07.0: PCI bridge to [bus 03]
    [ 0.690635] pci 0000:00:07.0: bridge window [io 0xb000-0xbfff]
    [ 0.690637] pci 0000:00:07.0: bridge window [mem 0xfea00000-0xfeafffff]
    [ 0.690704] pci 0000:04:00.0: [1106:0415] type 00 class 0x010185
    [ 0.690726] pci 0000:04:00.0: reg 0x10: [io 0xcc00-0xcc07]
    [ 0.690740] pci 0000:04:00.0: reg 0x14: [io 0xc880-0xc883]
    [ 0.690755] pci 0000:04:00.0: reg 0x18: [io 0xc800-0xc807]
    [ 0.690769] pci 0000:04:00.0: reg 0x1c: [io 0xc480-0xc483]
    [ 0.690783] pci 0000:04:00.0: reg 0x20: [io 0xc400-0xc40f]
    [ 0.690811] pci 0000:04:00.0: reg 0x30: [mem 0xfebe0000-0xfebeffff pref]
    [ 0.690883] pci 0000:04:00.0: supports D1 D2
    [ 0.690885] pci 0000:04:00.0: PME# supported from D1 D2 D3hot
    [ 0.700620] pci 0000:00:09.0: PCI bridge to [bus 04]
    [ 0.700625] pci 0000:00:09.0: bridge window [io 0xc000-0xcfff]
    [ 0.700627] pci 0000:00:09.0: bridge window [mem 0xfeb00000-0xfebfffff]
    [ 0.700675] pci 0000:05:00.0: [10ec:8168] type 00 class 0x020000
    [ 0.700687] pci 0000:05:00.0: reg 0x10: [io 0xd800-0xd8ff]
    [ 0.700705] pci 0000:05:00.0: reg 0x18: [mem 0xfdfff000-0xfdffffff 64bit pref]
    [ 0.700717] pci 0000:05:00.0: reg 0x20: [mem 0xfdff8000-0xfdffbfff 64bit pref]
    [ 0.700768] pci 0000:05:00.0: supports D1 D2
    [ 0.700769] pci 0000:05:00.0: PME# supported from D0 D1 D2 D3hot D3cold
    [ 0.710623] pci 0000:00:0a.0: PCI bridge to [bus 05]
    [ 0.710627] pci 0000:00:0a.0: bridge window [io 0xd000-0xdfff]
    [ 0.710631] pci 0000:00:0a.0: bridge window [mem 0xfdf00000-0xfdffffff 64bit pref]
    [ 0.710674] pci 0000:06:05.0: [1412:1724] type 00 class 0x040100
    [ 0.710691] pci 0000:06:05.0: reg 0x10: [io 0xec00-0xec1f]
    [ 0.710701] pci 0000:06:05.0: reg 0x14: [io 0xe880-0xe8ff]
    [ 0.710769] pci 0000:06:05.0: supports D2
    [ 0.710824] pci 0000:00:14.4: PCI bridge to [bus 06] (subtractive decode)
    [ 0.710827] pci 0000:00:14.4: bridge window [io 0xe000-0xefff]
    [ 0.710832] pci 0000:00:14.4: bridge window [io 0x0000-0x0cf7] (subtractive decode)
    [ 0.710833] pci 0000:00:14.4: bridge window [io 0x0d00-0xffff] (subtractive decode)
    [ 0.710835] pci 0000:00:14.4: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
    [ 0.710836] pci 0000:00:14.4: bridge window [mem 0x000d0000-0x000dffff] (subtractive decode)
    [ 0.710837] pci 0000:00:14.4: bridge window [mem 0xd0000000-0xdfffffff] (subtractive decode)
    [ 0.710839] pci 0000:00:14.4: bridge window [mem 0xf0000000-0xfebfffff] (subtractive decode)
    [ 0.711399] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 *5 6 7 9 10 11 14 15)
    [ 0.711445] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 14 15)
    [ 0.711491] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 *9 10 11 14 15)
    [ 0.711536] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 9 10 *11 14 15)
    [ 0.711572] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 11 14 15) *0
    [ 0.711602] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 11 14 15) *0
    [ 0.711631] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 9 10 11 14 15) *0
    [ 0.711661] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 10 11 14 15) *0
    [ 0.711760] ACPI: Enabled 1 GPEs in block 00 to 1F
    [ 0.711764] ACPI: \_SB_.PCI0: notify handler is installed
    [ 0.711791] Found 1 acpi root devices
    [ 0.711811] ACPI: EC: GPE = 0xa, I/O: command/status = 0x66, data = 0x62
    [ 0.711884] vgaarb: device added: PCI:0000:01:05.0,decodes=io+mem,owns=io+mem,locks=none
    [ 0.711885] vgaarb: loaded
    [ 0.711886] vgaarb: bridge control possible 0000:01:05.0
    [ 0.711914] PCI: Using ACPI for IRQ routing
    [ 0.717926] PCI: pci_cache_line_size set to 64 bytes
    [ 0.717976] e820: reserve RAM buffer [mem 0x0009ac00-0x0009ffff]
    [ 0.717978] e820: reserve RAM buffer [mem 0xcff80000-0xcfffffff]
    [ 0.718041] NetLabel: Initializing
    [ 0.718042] NetLabel: domain hash size = 128
    [ 0.718042] NetLabel: protocols = UNLABELED CIPSOv4
    [ 0.718052] NetLabel: unlabeled traffic allowed by default
    [ 0.718064] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
    [ 0.718066] hpet0: 3 comparators, 32-bit 14.318180 MHz counter
    [ 0.720112] Switched to clocksource hpet
    [ 0.723318] pnp: PnP ACPI init
    [ 0.723328] ACPI: bus type PNP registered
    [ 0.723421] system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
    [ 0.723488] pnp 00:01: [dma 4]
    [ 0.723503] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
    [ 0.723526] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
    [ 0.723543] pnp 00:03: Plug and Play ACPI device, IDs PNP0800 (active)
    [ 0.723560] pnp 00:04: Plug and Play ACPI device, IDs PNP0c04 (active)
    [ 0.723934] pnp 00:05: [dma 0 disabled]
    [ 0.724064] pnp 00:05: Plug and Play ACPI device, IDs PNP0400 (active)
    [ 0.724097] pnp 00:06: Plug and Play ACPI device, IDs PNP0103 (active)
    [ 0.724374] pnp 00:07: [dma 0 disabled]
    [ 0.724425] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
    [ 0.724491] system 00:08: [mem 0xfec00000-0xfec00fff] could not be reserved
    [ 0.724493] system 00:08: [mem 0xfee00000-0xfee00fff] has been reserved
    [ 0.724495] system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
    [ 0.724649] system 00:09: [io 0x04d0-0x04d1] has been reserved
    [ 0.724651] system 00:09: [io 0x040b] has been reserved
    [ 0.724653] system 00:09: [io 0x04d6] has been reserved
    [ 0.724654] system 00:09: [io 0x0c00-0x0c01] has been reserved
    [ 0.724656] system 00:09: [io 0x0c14] has been reserved
    [ 0.724657] system 00:09: [io 0x0c50-0x0c51] has been reserved
    [ 0.724659] system 00:09: [io 0x0c52] has been reserved
    [ 0.724660] system 00:09: [io 0x0c6c] has been reserved
    [ 0.724661] system 00:09: [io 0x0c6f] has been reserved
    [ 0.724663] system 00:09: [io 0x0cd0-0x0cd1] has been reserved
    [ 0.724664] system 00:09: [io 0x0cd2-0x0cd3] has been reserved
    [ 0.724666] system 00:09: [io 0x0cd4-0x0cd5] has been reserved
    [ 0.724667] system 00:09: [io 0x0cd6-0x0cd7] has been reserved
    [ 0.724669] system 00:09: [io 0x0cd8-0x0cdf] has been reserved
    [ 0.724670] system 00:09: [io 0x0b00-0x0b3f] has been reserved
    [ 0.724672] system 00:09: [io 0x0800-0x089f] could not be reserved
    [ 0.724673] system 00:09: [io 0x0b00-0x0b1f] has been reserved
    [ 0.724675] system 00:09: [io 0x0b20-0x0b3f] has been reserved
    [ 0.724677] system 00:09: [io 0x0900-0x090f] has been reserved
    [ 0.724678] system 00:09: [io 0x0910-0x091f] has been reserved
    [ 0.724680] system 00:09: [io 0xfe00-0xfefe] has been reserved
    [ 0.724682] system 00:09: [mem 0xffb80000-0xffbfffff] has been reserved
    [ 0.724683] system 00:09: [mem 0xfec10000-0xfec1001f] has been reserved
    [ 0.724685] system 00:09: [mem 0xfed40000-0xfed44fff] has been reserved
    [ 0.724686] system 00:09: [mem 0xfed80000-0xfed80fff] has been reserved
    [ 0.724688] system 00:09: Plug and Play ACPI device, IDs PNP0c02 (active)
    [ 0.724807] system 00:0a: [io 0x0230-0x023f] has been reserved
    [ 0.724809] system 00:0a: [io 0x0290-0x029f] has been reserved
    [ 0.724810] system 00:0a: [io 0x0300-0x030f] has been reserved
    [ 0.724812] system 00:0a: [io 0x0a30-0x0a3f] has been reserved
    [ 0.724814] system 00:0a: Plug and Play ACPI device, IDs PNP0c02 (active)
    [ 0.724858] system 00:0b: [mem 0xe0000000-0xefffffff] has been reserved
    [ 0.724860] system 00:0b: Plug and Play ACPI device, IDs PNP0c02 (active)
    [ 0.724952] system 00:0c: [mem 0x00000000-0x0009ffff] could not be reserved
    [ 0.724953] system 00:0c: [mem 0x000c0000-0x000cffff] could not be reserved
    [ 0.724955] system 00:0c: [mem 0x000e0000-0x000fffff] could not be reserved
    [ 0.724957] system 00:0c: [mem 0x00100000-0xcfffffff] could not be reserved
    [ 0.724958] system 00:0c: [mem 0xfec00000-0xffffffff] could not be reserved
    [ 0.724960] system 00:0c: Plug and Play ACPI device, IDs PNP0c01 (active)
    [ 0.725022] pnp: PnP ACPI: found 13 devices
    [ 0.725022] ACPI: bus type PNP unregistered
    [ 0.731469] pci 0000:00:01.0: PCI bridge to [bus 01]
    [ 0.731472] pci 0000:00:01.0: bridge window [io 0xa000-0xafff]
    [ 0.731474] pci 0000:00:01.0: bridge window [mem 0xfe700000-0xfe8fffff]
    [ 0.731476] pci 0000:00:01.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
    [ 0.731479] pci 0000:00:05.0: PCI bridge to [bus 02]
    [ 0.731481] pci 0000:00:05.0: bridge window [mem 0xfe900000-0xfe9fffff]
    [ 0.731484] pci 0000:00:07.0: PCI bridge to [bus 03]
    [ 0.731486] pci 0000:00:07.0: bridge window [io 0xb000-0xbfff]
    [ 0.731488] pci 0000:00:07.0: bridge window [mem 0xfea00000-0xfeafffff]
    [ 0.731491] pci 0000:00:09.0: PCI bridge to [bus 04]
    [ 0.731493] pci 0000:00:09.0: bridge window [io 0xc000-0xcfff]
    [ 0.731495] pci 0000:00:09.0: bridge window [mem 0xfeb00000-0xfebfffff]
    [ 0.731498] pci 0000:00:0a.0: PCI bridge to [bus 05]
    [ 0.731499] pci 0000:00:0a.0: bridge window [io 0xd000-0xdfff]
    [ 0.731502] pci 0000:00:0a.0: bridge window [mem 0xfdf00000-0xfdffffff 64bit pref]
    [ 0.731505] pci 0000:00:14.4: PCI bridge to [bus 06]
    [ 0.731507] pci 0000:00:14.4: bridge window [io 0xe000-0xefff]
    [ 0.731716] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
    [ 0.731718] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
    [ 0.731719] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
    [ 0.731721] pci_bus 0000:00: resource 7 [mem 0x000d0000-0x000dffff]
    [ 0.731722] pci_bus 0000:00: resource 8 [mem 0xd0000000-0xdfffffff]
    [ 0.731723] pci_bus 0000:00: resource 9 [mem 0xf0000000-0xfebfffff]
    [ 0.731725] pci_bus 0000:01: resource 0 [io 0xa000-0xafff]
    [ 0.731726] pci_bus 0000:01: resource 1 [mem 0xfe700000-0xfe8fffff]
    [ 0.731727] pci_bus 0000:01: resource 2 [mem 0xd0000000-0xdfffffff 64bit pref]
    [ 0.731729] pci_bus 0000:02: resource 1 [mem 0xfe900000-0xfe9fffff]
    [ 0.731730] pci_bus 0000:03: resource 0 [io 0xb000-0xbfff]
    [ 0.731732] pci_bus 0000:03: resource 1 [mem 0xfea00000-0xfeafffff]
    [ 0.731733] pci_bus 0000:04: resource 0 [io 0xc000-0xcfff]
    [ 0.731734] pci_bus 0000:04: resource 1 [mem 0xfeb00000-0xfebfffff]
    [ 0.731736] pci_bus 0000:05: resource 0 [io 0xd000-0xdfff]
    [ 0.731737] pci_bus 0000:05: resource 2 [mem 0xfdf00000-0xfdffffff 64bit pref]
    [ 0.731739] pci_bus 0000:06: resource 0 [io 0xe000-0xefff]
    [ 0.731740] pci_bus 0000:06: resource 4 [io 0x0000-0x0cf7]
    [ 0.731741] pci_bus 0000:06: resource 5 [io 0x0d00-0xffff]
    [ 0.731742] pci_bus 0000:06: resource 6 [mem 0x000a0000-0x000bffff]
    [ 0.731744] pci_bus 0000:06: resource 7 [mem 0x000d0000-0x000dffff]
    [ 0.731745] pci_bus 0000:06: resource 8 [mem 0xd0000000-0xdfffffff]
    [ 0.731746] pci_bus 0000:06: resource 9 [mem 0xf0000000-0xfebfffff]
    [ 0.731774] NET: Registered protocol family 2
    [ 0.731920] TCP established hash table entries: 32768 (order: 7, 524288 bytes)
    [ 0.732050] TCP bind hash table entries: 32768 (order: 7, 524288 bytes)
    [ 0.732170] TCP: Hash tables configured (established 32768 bind 32768)
    [ 0.732202] TCP: reno registered
    [ 0.732208] UDP hash table entries: 2048 (order: 4, 65536 bytes)
    [ 0.732229] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes)
    [ 0.732295] NET: Registered protocol family 1
    [ 0.732302] pci 0000:00:01.0: MSI quirk detected; subordinate MSI disabled
    [ 1.774244] pci 0000:01:05.0: Boot video device
    [ 1.774293] PCI: CLS 64 bytes, default 64
    [ 1.774329] Unpacking initramfs...
    [ 1.838503] Freeing initrd memory: 4800K (ffff880037690000 - ffff880037b40000)
    [ 1.839314] PCI-DMA: Disabling AGP.
    [ 1.839384] PCI-DMA: aperture base @ c4000000 size 65536 KB
    [ 1.839385] PCI-DMA: using GART IOMMU.
    [ 1.839387] PCI-DMA: Reserving 64MB of IOMMU area in the AGP aperture
    [ 1.842458] LVT offset 1 assigned for vector 0x400
    [ 1.842466] IBS: LVT offset 1 assigned
    [ 1.842487] perf: AMD IBS detected (0x0000001f)
    [ 1.842507] Scanning for low memory corruption every 60 seconds
    [ 1.842725] audit: initializing netlink socket (disabled)
    [ 1.842734] type=2000 audit(1384711004.543:1): initialized
    [ 1.851049] HugeTLB registered 2 MB page size, pre-allocated 0 pages
    [ 1.852054] zbud: loaded
    [ 1.852166] VFS: Disk quotas dquot_6.5.2
    [ 1.852200] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
    [ 1.852354] msgmni has been set to 7405
    [ 1.852587] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
    [ 1.852634] io scheduler noop registered
    [ 1.852637] io scheduler deadline registered
    [ 1.852674] io scheduler cfq registered (default)
    [ 1.852784] pcieport 0000:00:05.0: irq 40 for MSI/MSI-X
    [ 1.852849] pcieport 0000:00:07.0: irq 41 for MSI/MSI-X
    [ 1.852906] pcieport 0000:00:09.0: irq 42 for MSI/MSI-X
    [ 1.852964] pcieport 0000:00:0a.0: irq 43 for MSI/MSI-X
    [ 1.853049] pcieport 0000:00:05.0: Signaling PME through PCIe PME interrupt
    [ 1.853053] pci 0000:02:00.0: Signaling PME through PCIe PME interrupt
    [ 1.853055] pcie_pme 0000:00:05.0:pcie01: service driver pcie_pme loaded
    [ 1.853064] pcieport 0000:00:07.0: Signaling PME through PCIe PME interrupt
    [ 1.853066] pci 0000:03:00.0: Signaling PME through PCIe PME interrupt
    [ 1.853068] pcie_pme 0000:00:07.0:pcie01: service driver pcie_pme loaded
    [ 1.853078] pcieport 0000:00:09.0: Signaling PME through PCIe PME interrupt
    [ 1.853079] pci 0000:04:00.0: Signaling PME through PCIe PME interrupt
    [ 1.853081] pcie_pme 0000:00:09.0:pcie01: service driver pcie_pme loaded
    [ 1.853092] pcieport 0000:00:0a.0: Signaling PME through PCIe PME interrupt
    [ 1.853093] pci 0000:05:00.0: Signaling PME through PCIe PME interrupt
    [ 1.853095] pcie_pme 0000:00:0a.0:pcie01: service driver pcie_pme loaded
    [ 1.853105] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    [ 1.853116] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
    [ 1.853160] vesafb: mode is 1920x1440x32, linelength=7680, pages=0
    [ 1.853161] vesafb: scrolling: redraw
    [ 1.853162] vesafb: Truecolor: size=0:8:8:8, shift=0:16:8:0
    [ 1.853503] vesafb: framebuffer at 0xd0000000, mapped to 0xffffc90010800000, using 10816k, total 10816k
    [ 2.187925] Console: switching to colour frame buffer device 240x90
    [ 2.522112] fb0: VESA VGA frame buffer device
    [ 2.522136] GHES: HEST is not enabled!
    [ 2.522194] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    [ 2.542718] 00:07: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
    [ 2.543025] Linux agpgart interface v0.103
    [ 2.543063] i8042: PNP: No PS/2 controller found. Probing ports directly.
    [ 2.543414] serio: i8042 KBD port at 0x60,0x64 irq 1
    [ 2.543440] serio: i8042 AUX port at 0x60,0x64 irq 12
    [ 2.543545] mousedev: PS/2 mouse device common for all mice
    [ 2.543591] rtc_cmos 00:02: RTC can wake from S4
    [ 2.543688] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
    [ 2.543707] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
    [ 2.543713] cpuidle: using governor ladder
    [ 2.543715] cpuidle: using governor menu
    [ 2.543764] drop_monitor: Initializing network drop monitor service
    [ 2.543811] TCP: cubic registered
    [ 2.543876] NET: Registered protocol family 10
    [ 2.544001] NET: Registered protocol family 17
    [ 2.544009] Key type dns_resolver registered
    [ 2.544240] PM: Hibernation image not present or could not be loaded.
    [ 2.544247] registered taskstats version 1
    [ 2.544768] Magic number: 5:4:947
    [ 2.544782] tty tty4: hash matches
    [ 2.544801] cpu cpu2: hash matches
    [ 2.544807] memory memory0: hash matches
    [ 2.544836] rtc_cmos 00:02: setting system clock to 2013-11-17 17:56:45 UTC (1384711005)
    [ 2.545743] Freeing unused kernel memory: 1140K (ffffffff818c9000 - ffffffff819e6000)
    [ 2.545745] Write protecting the kernel read-only data: 8192k
    [ 2.547931] Freeing unused kernel memory: 1084K (ffff8800014f1000 - ffff880001600000)
    [ 2.548636] Freeing unused kernel memory: 352K (ffff8800017a8000 - ffff880001800000)
    [ 2.554741] systemd-udevd[57]: starting version 208
    [ 2.556092] SCSI subsystem initialized
    [ 2.556877] ACPI: bus type ATA registered
    [ 2.556944] libata version 3.00 loaded.
    [ 2.557360] ahci 0000:00:11.0: version 3.0
    [ 2.557535] ahci 0000:00:11.0: AHCI 0001.0200 32 slots 6 ports 6 Gbps 0x3f impl SATA mode
    [ 2.557538] ahci 0000:00:11.0: flags: 64bit ncq sntf ilck pm led clo pmp pio slum part
    [ 2.558505] scsi0 : ahci
    [ 2.558599] scsi1 : ahci
    [ 2.558778] scsi2 : ahci
    [ 2.558868] scsi3 : ahci
    [ 2.559022] scsi4 : ahci
    [ 2.559089] scsi5 : ahci
    [ 2.559150] ata1: SATA max UDMA/133 abar m1024@0xfe6ffc00 port 0xfe6ffd00 irq 19
    [ 2.559153] ata2: SATA max UDMA/133 abar m1024@0xfe6ffc00 port 0xfe6ffd80 irq 19
    [ 2.559155] ata3: SATA max UDMA/133 abar m1024@0xfe6ffc00 port 0xfe6ffe00 irq 19
    [ 2.559156] ata4: SATA max UDMA/133 abar m1024@0xfe6ffc00 port 0xfe6ffe80 irq 19
    [ 2.559159] ata5: SATA max UDMA/133 abar m1024@0xfe6ffc00 port 0xfe6fff00 irq 19
    [ 2.559161] ata6: SATA max UDMA/133 abar m1024@0xfe6ffc00 port 0xfe6fff80 irq 19
    [ 2.560807] [drm] Initialized drm 1.1.0 20060810
    [ 2.564745] [drm] radeon kernel modesetting enabled.
    [ 2.564805] checking generic (d0000000 a90000) vs hw (d0000000 10000000)
    [ 2.564808] fb: conflicting fb hw usage radeondrmfb vs VESA VGA - removing generic driver
    [ 2.564821] Console: switching to colour dummy device 80x25
    [ 2.565086] [drm] initializing kernel modesetting (RS880 0x1002:0x9715 0x1043:0x843E).
    [ 2.565095] [drm] register mmio base: 0xFE8F0000
    [ 2.565096] [drm] register mmio size: 65536
    [ 2.565630] ATOM BIOS: 113
    [ 2.565643] radeon 0000:01:05.0: VRAM: 368M 0x00000000C0000000 - 0x00000000D6FFFFFF (368M used)
    [ 2.565645] radeon 0000:01:05.0: GTT: 512M 0x00000000A0000000 - 0x00000000BFFFFFFF
    [ 2.565648] [drm] Detected VRAM RAM=368M, BAR=256M
    [ 2.565649] [drm] RAM width 32bits DDR
    [ 2.565696] [TTM] Zone kernel: Available graphics memory: 1897112 kiB
    [ 2.565697] [TTM] Initializing pool allocator
    [ 2.565700] [TTM] Initializing DMA pool allocator
    [ 2.565716] [drm] radeon: 368M of VRAM memory ready
    [ 2.565717] [drm] radeon: 512M of GTT memory ready.
    [ 2.565725] [drm] GART: num cpu pages 131072, num gpu pages 131072
    [ 2.576556] [drm] Loading RS780 Microcode
    [ 2.578778] [drm] PCIE GART of 512M enabled (table at 0x00000000C0040000).
    [ 2.578836] radeon 0000:01:05.0: WB enabled
    [ 2.578838] radeon 0000:01:05.0: fence driver on ring 0 use gpu addr 0x00000000a0000c00 and cpu addr 0xffff880117cfdc00
    [ 2.578839] radeon 0000:01:05.0: fence driver on ring 3 use gpu addr 0x00000000a0000c0c and cpu addr 0xffff880117cfdc0c
    [ 2.578841] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
    [ 2.578842] [drm] Driver supports precise vblank timestamp query.
    [ 2.578860] [drm] radeon: irq initialized.
    [ 2.579084] radeon 0000:01:05.0: setting latency timer to 64
    [ 2.611015] [drm] ring test on 0 succeeded in 1 usecs
    [ 2.611072] [drm] ring test on 3 succeeded in 1 usecs
    [ 2.611137] [drm] ib test on ring 0 succeeded in 0 usecs
    [ 2.611149] [drm] ib test on ring 3 succeeded in 0 usecs
    [ 2.611351] [drm] Radeon Display Connectors
    [ 2.611352] [drm] Connector 0:
    [ 2.611353] [drm] VGA-1
    [ 2.611355] [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c
    [ 2.611355] [drm] Encoders:
    [ 2.611356] [drm] CRT1: INTERNAL_KLDSCP_DAC1
    [ 2.611357] [drm] Connector 1:
    [ 2.611357] [drm] DVI-D-1
    [ 2.611358] [drm] HPD1
    [ 2.611359] [drm] DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c
    [ 2.611360] [drm] Encoders:
    [ 2.611361] [drm] DFP3: INTERNAL_KLDSCP_LVTMA
    [ 2.611408] [drm] radeon: power management initialized
    [ 2.652806] [drm] fb mappable at 0xD0142000
    [ 2.652807] [drm] vram apper at 0xD0000000
    [ 2.652808] [drm] size 5242880
    [ 2.652808] [drm] fb depth is 24
    [ 2.652809] [drm] pitch is 5120
    [ 2.652866] fbcon: radeondrmfb (fb0) is primary device
    [ 2.664744] Console: switching to colour frame buffer device 160x64
    [ 2.675575] radeon 0000:01:05.0: fb0: radeondrmfb frame buffer device
    [ 2.675577] radeon 0000:01:05.0: registered panic notifier
    [ 2.675630] [drm] Initialized radeon 2.34.0 20080528 for 0000:01:05.0 on minor 0
    [ 2.692173] pata_via 0000:04:00.0: version 0.3.4
    [ 2.693001] scsi6 : pata_via
    [ 2.693202] scsi7 : pata_via
    [ 2.693237] ata7: PATA max UDMA/133 cmd 0xcc00 ctl 0xc880 bmdma 0xc400 irq 17
    [ 2.693238] ata8: PATA max UDMA/133 cmd 0xc800 ctl 0xc480 bmdma 0xc408 irq 17
    [ 2.693302] ACPI: bus type USB registered
    [ 2.693369] usbcore: registered new interface driver usbfs
    [ 2.693378] usbcore: registered new interface driver hub
    [ 2.693419] usbcore: registered new device driver usb
    [ 2.694028] xhci_hcd 0000:02:00.0: xHCI Host Controller
    [ 2.694034] xhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 1
    [ 2.694163] xhci_hcd 0000:02:00.0: irq 44 for MSI/MSI-X
    [ 2.694168] xhci_hcd 0000:02:00.0: irq 45 for MSI/MSI-X
    [ 2.694173] xhci_hcd 0000:02:00.0: irq 46 for MSI/MSI-X
    [ 2.694177] xhci_hcd 0000:02:00.0: irq 47 for MSI/MSI-X
    [ 2.694181] xhci_hcd 0000:02:00.0: irq 48 for MSI/MSI-X
    [ 2.694382] xHCI xhci_add_endpoint called for root hub
    [ 2.694383] xHCI xhci_check_bandwidth called for root hub
    [ 2.694913] hub 1-0:1.0: USB hub found
    [ 2.694918] hub 1-0:1.0: 2 ports detected
    [ 2.695055] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    [ 2.695347] ehci-pci: EHCI PCI platform driver
    [ 2.695437] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
    [ 2.695532] ohci-pci: OHCI PCI platform driver
    [ 2.695613] xhci_hcd 0000:02:00.0: xHCI Host Controller
    [ 2.695617] xhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 2
    [ 2.697530] ehci-pci 0000:00:12.2: EHCI Host Controller
    [ 2.697595] xHCI xhci_add_endpoint called for root hub
    [ 2.697596] xHCI xhci_check_bandwidth called for root hub
    [ 2.697636] hub 2-0:1.0: USB hub found
    [ 2.697645] hub 2-0:1.0: 2 ports detected
    [ 2.697762] ehci-pci 0000:00:12.2: new USB bus registered, assigned bus number 3
    [ 2.697764] QUIRK: Enable AMD PLL fix
    [ 2.697766] ehci-pci 0000:00:12.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround
    [ 2.697776] ehci-pci 0000:00:12.2: debug port 1
    [ 2.697800] ehci-pci 0000:00:12.2: irq 17, io mem 0xfe6ff800
    [ 2.704582] ehci-pci 0000:00:12.2: USB 2.0 started, EHCI 1.00
    [ 2.704674] hub 3-0:1.0: USB hub found
    [ 2.704677] hub 3-0:1.0: 5 ports detected
    [ 2.704845] ehci-pci 0000:00:13.2: EHCI Host Controller
    [ 2.704850] ehci-pci 0000:00:13.2: new USB bus registered, assigned bus number 4
    [ 2.704852] ehci-pci 0000:00:13.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround
    [ 2.704861] ehci-pci 0000:00:13.2: debug port 1
    [ 2.704883] ehci-pci 0000:00:13.2: irq 17, io mem 0xfe6ff400
    [ 2.714637] ehci-pci 0000:00:13.2: USB 2.0 started, EHCI 1.00
    [ 2.714734] hub 4-0:1.0: USB hub found
    [ 2.714737] hub 4-0:1.0: 5 ports detected
    [ 2.714896] ehci-pci 0000:00:16.2: EHCI Host Controller
    [ 2.714900] ehci-pci 0000:00:16.2: new USB bus registered, assigned bus number 5
    [ 2.714903] ehci-pci 0000:00:16.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround
    [ 2.714911] ehci-pci 0000:00:16.2: debug port 1
    [ 2.714930] ehci-pci 0000:00:16.2: irq 17, io mem 0xfe6ff000
    [ 2.724628] ehci-pci 0000:00:16.2: USB 2.0 started, EHCI 1.00
    [ 2.724725] hub 5-0:1.0: USB hub found
    [ 2.724728] hub 5-0:1.0: 4 ports detected
    [ 2.724888] ohci-pci 0000:00:12.0: OHCI PCI host controller
    [ 2.724892] ohci-pci 0000:00:12.0: new USB bus registered, assigned bus number 6
    [ 2.724904] ohci-pci 0000:00:12.0: irq 18, io mem 0xfe6fe000
    [ 2.758021] firewire_ohci 0000:03:00.0: added OHCI v1.10 device as card 0, 4 IR + 8 IT contexts, quirks 0x11
    [ 2.782133] hub 6-0:1.0: USB hub found
    [ 2.782138] hub 6-0:1.0: 5 ports detected
    [ 2.782291] ohci-pci 0000:00:13.0: OHCI PCI host controller
    [ 2.782296] ohci-pci 0000:00:13.0: new USB bus registered, assigned bus number 7
    [ 2.782308] ohci-pci 0000:00:13.0: irq 18, io mem 0xfe6fd000
    [ 2.838807] hub 7-0:1.0: USB hub found
    [ 2.838813] hub 7-0:1.0: 5 ports detected
    [ 2.838974] ohci-pci 0000:00:14.5: OHCI PCI host controller
    [ 2.838978] ohci-pci 0000:00:14.5: new USB bus registered, assigned bus number 8
    [ 2.838989] ohci-pci 0000:00:14.5: irq 18, io mem 0xfe6fc000
    [ 2.844705] tsc: Refined TSC clocksource calibration: 3415.257 MHz
    [ 2.871387] ata1: SATA link down (SStatus 0 SControl 300)
    [ 2.874721] ata6: SATA link down (SStatus 0 SControl 300)
    [ 2.878060] ata4: SATA link down (SStatus 0 SControl 300)
    [ 2.878096] ata3: SATA link down (SStatus 0 SControl 300)
    [ 2.895510] hub 8-0:1.0: USB hub found
    [ 2.895515] hub 8-0:1.0: 2 ports detected
    [ 2.895650] ohci-pci 0000:00:16.0: OHCI PCI host controller
    [ 2.895654] ohci-pci 0000:00:16.0: new USB bus registered, assigned bus number 9
    [ 2.895665] ohci-pci 0000:00:16.0: irq 18, io mem 0xfe6f3000
    [ 2.952187] hub 9-0:1.0: USB hub found
    [ 2.952192] hub 9-0:1.0: 4 ports detected
    [ 3.011462] usb 3-3: new high-speed USB device number 2 using ehci-pci
    [ 3.041482] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    [ 3.042668] ata5.00: ATA-8: ST31000524AS, JC45, max UDMA/133
    [ 3.042671] ata5.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
    [ 3.044091] ata5.00: configured for UDMA/133
    [ 3.044818] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    [ 3.046010] ata2.00: ATA-8: ST31000524AS, JC45, max UDMA/133
    [ 3.046012] ata2.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
    [ 3.047443] ata2.00: configured for UDMA/133
    [ 3.047593] scsi 1:0:0:0: Direct-Access ATA ST31000524AS JC45 PQ: 0 ANSI: 5
    [ 3.047815] scsi 4:0:0:0: Direct-Access ATA ST31000524AS JC45 PQ: 0 ANSI: 5
    [ 3.048310] sd 1:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
    [ 3.048332] sd 4:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
    [ 3.048407] sd 1:0:0:0: [sda] Write Protect is off
    [ 3.048410] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
    [ 3.048414] sd 4:0:0:0: [sdb] Write Protect is off
    [ 3.048416] sd 4:0:0:0: [sdb] Mode Sense: 00 3a 00 00
    [ 3.048445] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [ 3.048454] sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [ 3.082120] sdb: sdb1 < sdb5 >
    [ 3.082492] sd 4:0:0:0: [sdb] Attached SCSI disk
    [ 3.123617] sda: sda1 < sda5 sda6 sda7 sda8 sda9 sda10 >
    [ 3.124128] sd 1:0:0:0: [sda] Attached SCSI disk
    [ 3.258326] firewire_core 0000:03:00.0: created device fw0: GUID 001e8c0000dded87, S400
    [ 3.845323] Switched to clocksource tsc
    [ 3.887097] JFS: nTxBlock = 8192, nTxLock = 65536
    [ 4.225475] usb 7-1: new low-speed USB device number 2 using ohci-pci
    [ 4.639033] usb 9-4: new full-speed USB device number 2 using ohci-pci
    [ 4.953305] systemd[1]: systemd 208 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)
    [ 4.973795] systemd[1]: Set hostname to <chaembian>.
    [ 5.179335] usb 6-4: new full-speed USB device number 2 using ohci-pci
    [ 5.596246] usb 6-5: new low-speed USB device number 3 using ohci-pci
    [ 5.801932] systemd[1]: Cannot add dependency job for unit vnstat.service, ignoring: Unit vnstat.service failed to load: No such file or directory.
    [ 5.801948] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory.
    [ 5.802146] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
    [ 5.802185] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
    [ 5.802193] systemd[1]: Starting Login Prompts.
    [ 5.802200] systemd[1]: Reached target Login Prompts.
    [ 5.802206] systemd[1]: Starting Remote File Systems.
    [ 5.802211] systemd[1]: Reached target Remote File Systems.
    [ 5.802218] systemd[1]: Starting Delayed Shutdown Socket.
    [ 5.802235] systemd[1]: Listening on Delayed Shutdown Socket.
    [ 5.802240] systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
    [ 5.802253] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
    [ 5.802258] systemd[1]: Starting LVM2 metadata daemon socket.
    [ 5.802272] systemd[1]: Listening on LVM2 metadata daemon socket.
    [ 5.802278] systemd[1]: Starting Device-mapper event daemon FIFOs.
    [ 5.802294] systemd[1]: Listening on Device-mapper event daemon FIFOs.
    [ 5.802303] systemd[1]: Starting udev Kernel Socket.
    [ 5.802314] systemd[1]: Listening on udev Kernel Socket.
    [ 5.802321] systemd[1]: Starting udev Control Socket.
    [ 5.802332] systemd[1]: Listening on udev Control Socket.
    [ 5.802340] systemd[1]: Starting Journal Socket.
    [ 5.802364] systemd[1]: Listening on Journal Socket.
    [ 5.828144] systemd[1]: Started Load Kernel Modules.
    [ 5.837412] systemd[1]: Starting Apply Kernel Variables...
    [ 5.837770] systemd[1]: Starting udev Coldplug all Devices...
    [ 5.838054] systemd[1]: Starting Setup Virtual Console...
    [ 5.838365] systemd[1]: Starting Journal Service...
    [ 5.838647] systemd[1]: Started Journal Service.
    [ 6.402315] systemd-journald[139]: Vacuuming done, freed 0 bytes
    [ 7.319880] systemd-udevd[177]: starting version 208
    [ 7.794545] wmi: Mapper loaded
    [ 7.847347] parport_pc 00:05: reported by Plug and Play ACPI
    [ 7.847391] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
    [ 7.851969] ACPI Warning: 0x0000000000000b00-0x0000000000000b07 SystemIO conflicts with Region \_SB_.PCI0.SBRG.ASOC.SMRG 1 (20130517/utaddress-251)
    [ 7.851974] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
    [ 7.874491] sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver v0.05
    [ 7.874519] sp5100_tco: PCI Revision ID: 0x41
    [ 7.874547] sp5100_tco: Using 0xfed80b00 for watchdog MMIO address
    [ 7.874557] sp5100_tco: Last reboot was not triggered by watchdog.
    [ 7.874600] sp5100_tco: initialized (0xffffc900123fcb00). heartbeat=60 sec (nowayout=0)
    [ 7.881641] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
    [ 7.881645] ACPI: Power Button [PWRB]
    [ 7.881697] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
    [ 7.881699] ACPI: Power Button [PWRF]
    [ 7.882757] ACPI: processor limited to max C-state 1
    [ 7.905064] acpi-cpufreq: overriding BIOS provided _PSD data
    [ 7.918926] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
    [ 8.165090] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
    [ 8.165417] r8169 0000:05:00.0: irq 49 for MSI/MSI-X
    [ 8.165792] r8169 0000:05:00.0 eth0: RTL8168e/8111e at 0xffffc900123fe000, 20:cf:30:4c:49:a9, XID 0c200000 IRQ 49
    [ 8.165800] r8169 0000:05:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
    [ 8.342332] MCE: In-kernel MCE decoding enabled.
    [ 8.346927] EDAC MC: Ver: 3.0.0
    [ 8.348961] AMD64 EDAC driver v3.4.0
    [ 8.349044] EDAC amd64: DRAM ECC disabled.
    [ 8.349073] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
    Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
    (Note that use of the override may cause unknown side effects.)
    [ 8.495021] input: PC Speaker as /devices/platform/pcspkr/input/input2
    [ 8.558418] snd_ice1724 0000:06:05.0: enabling device (0000 -> 0001)
    [ 8.558556] snd_ice1724 0000:06:05.0: setting latency timer to 64
    [ 8.587452] ice1724: No matching model found for ID 0xffffffa0
    [ 8.588183] ice1724: Invalid EEPROM (size = 255)
    [ 8.588437] snd_ice1724: probe of 0000:06:05.0 failed with error -5
    [ 8.607952] microcode: CPU0: patch_level=0x010000b6
    [ 8.629397] ppdev: user-space parallel port driver
    [ 8.825646] input: HDA ATI SB Front Headphone as /devices/pci0000:00/0000:00:14.2/sound/card0/input3
    [ 8.825863] input: HDA ATI SB Line Out Side as /devices/pci0000:00/0000:00:14.2/sound/card0/input4
    [ 8.826029] input: HDA ATI SB Line Out CLFE as /devices/pci0000:00/0000:00:14.2/sound/card0/input5
    [ 8.826190] input: HDA ATI SB Line Out Surround as /devices/pci0000:00/0000:00:14.2/sound/card0/input6
    [ 8.826357] input: HDA ATI SB Line Out Front as /devices/pci0000:00/0000:00:14.2/sound/card0/input7
    [ 8.826514] input: HDA ATI SB Line as /devices/pci0000:00/0000:00:14.2/sound/card0/input8
    [ 8.826667] input: HDA ATI SB Rear Mic as /devices/pci0000:00/0000:00:14.2/sound/card0/input9
    [ 8.826823] input: HDA ATI SB Front Mic as /devices/pci0000:00/0000:00:14.2/sound/card0/input10
    [ 8.827628] snd_hda_intel 0000:01:05.1: setting latency timer to 64
    [ 8.868368] input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:05.1/sound/card1/input11
    [ 9.003261] microcode: CPU0: new patch_level=0x010000c8
    [ 9.003302] microcode: CPU1: patch_level=0x010000b6
    [ 9.003328] microcode: CPU1: new patch_level=0x010000c8
    [ 9.003357] microcode: CPU2: patch_level=0x010000b6
    [ 9.003381] microcode: CPU2: new patch_level=0x010000c8
    [ 9.003396] microcode: CPU3: patch_level=0x010000b6
    [ 9.003412] microcode: CPU3: new patch_level=0x010000c8
    [ 9.003552] microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
    [ 9.031976] media: Linux media interface: v0.10
    [ 9.034867] Linux video capture interface: v2.00
    [ 9.043789] kvm: Nested Virtualization enabled
    [ 9.043793] kvm: Nested Paging enabled
    [ 9.244784] hidraw: raw HID events driver (C) Jiri Kosina
    [ 9.423576] usbcore: registered new interface driver usbhid
    [ 9.423583] usbhid: USB HID core driver
    [ 9.513383] input: Plus More Enterprise LTD. USB-compliant keyboard as /devices/pci0000:00/0000:00:13.0/usb7/7-1/7-1:1.0/input/input12
    [ 9.513638] hid-generic 0003:0518:0001.0001: input,hidraw0: USB HID v1.10 Keyboard [Plus More Enterprise LTD. USB-compliant keyboard] on usb-0000:00:13.0-1/input0
    [ 9.514469] input: Plus More Enterprise LTD. USB-compliant keyboard as /devices/pci0000:00/0000:00:13.0/usb7/7-1/7-1:1.1/input/input13
    [ 9.514899] hid-generic 0003:0518:0001.0002: input,hidraw1: USB HID v1.10 Mouse [Plus More Enterprise LTD. USB-compliant keyboard] on usb-0000:00:13.0-1/input1
    [ 9.516355] input: C-Media Electronics Inc. Philips SPA5210 as /devices/pci0000:00/0000:00:16.0/usb9/9-4/9-4:1.2/input/input14
    [ 9.516925] hid-generic 0003:0D8C:0126.0003: input,hidraw2: USB HID v1.00 Device [C-Media Electronics Inc. Philips SPA5210] on usb-0000:00:16.0-4/input2
    [ 9.595842] hid-generic 0003:051D:0002.0004: hiddev0,hidraw3: USB HID v1.00 Device [American Power Conversion Back-UPS RS 1000G-IN FW:900.L4 .I USB FW:L4 ] on usb-0000:00:12.0-4/input0
    [ 9.596476] input: Logitech USB Optical Mouse as /devices/pci0000:00/0000:00:12.0/usb6/6-5/6-5:1.0/input/input15
    [ 9.596993] hid-generic 0003:046D:C05B.0005: input,hidraw4: USB HID v1.11 Mouse [Logitech USB Optical Mouse] on usb-0000:00:12.0-5/input0
    [ 9.885366] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    [ 9.886617] ata5.00: failed to set xfermode (err_mask=0x100)
    [ 10.370083] set resolution quirk: cval->res = 384
    [ 10.370534] uvcvideo: Found UVC 1.00 device <unnamed> (046d:081b)
    [ 10.385720] input: UVC Camera (046d:081b) as /devices/pci0000:00/0000:00:12.2/usb3/3-3/3-3:1.0/input/input16
    [ 10.385897] usbcore: registered new interface driver uvcvideo
    [ 10.385902] USB Video Class driver (1.1.1)
    [ 10.443673] usbcore: registered new interface driver snd-usb-audio
    [ 10.530521] Adding 995992k swap on /dev/sda7. Priority:-1 extents:1 across:995992k FS
    [ 17.204835] systemd-journald[139]: Received request to flush runtime journal from PID 1
    [ 17.564410] systemd-journald[139]: Vacuuming done, freed 4194304 bytes
    [ 17.564429] systemd-journald[139]: Vacuuming done, freed 0 bytes
    [ 17.594012] systemd-journald[139]: Vacuuming done, freed 4198400 bytes
    [ 17.594091] systemd-journald[139]: Deleted empty journal /run/log/journal/e44c../[email protected] (684032 bytes).
    [ 17.594101] systemd-journald[139]: Vacuuming done, freed 684032 bytes
    [ 18.430485] r8169 0000:05:00.0 eth0: link down
    [ 18.430501] r8169 0000:05:00.0 eth0: link down
    [ 18.430540] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 20.057527] r8169 0000:05:00.0 eth0: link up
    [ 20.057545] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 26.308009] systemd-journald[139]: File /var/log/journal/e44c../user-1004.journal corrupted or uncleanly shut down, renaming and replacing.
    [ 31.900749] hda-intel: IRQ timing workaround is activated for card #1. Suggest a bigger bdl_pos_adj.
    [ 32.146160] fuse init (API version 7.22)
    [ 63.406994] systemd-journald[139]: File /var/log/journal/e44c../user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
    I did not get any output when I tried: " journalctl -b --dmesg | grep systemd". However, when I tried  "journalctl | grep systemd", I got these:
    Nov 17 23:26:51 chaembian systemd[1]: Starting Sound Card.
    Nov 17 23:26:51 chaembian systemd[1]: Reached target Sound Card.
    Nov 17 23:26:52 chaembian systemd[1]: Found device ST31000524AS.
    Nov 17 23:26:52 chaembian systemd[1]: Starting File System Check on /dev/disk/by-uuid/cd1ecac7-97b5-4bcc-b114-858efb77e4c5...
    Nov 17 23:26:52 chaembian systemd[1]: Found device ST31000524AS.
    Nov 17 23:26:52 chaembian systemd[1]: Starting File System Check on /dev/disk/by-uuid/8f972288-02c8-4dd7-a590-400f4fe60244...
    Nov 17 23:26:53 chaembian systemd[1]: Found device ST31000524AS.
    Nov 17 23:26:53 chaembian systemd[1]: Activating swap /dev/disk/by-uuid/cf5549b8-edd7-465a-985c-c096f39b916e...
    Nov 17 23:26:53 chaembian systemd-fsck[254]: fsck.jfs version 1.1.15, 04-Mar-2011
    Nov 17 23:26:53 chaembian systemd-fsck[254]: processing started: 11/17/2013 23:26:53
    Nov 17 23:26:53 chaembian systemd-fsck[254]: The current device is: /dev/sda9
    Nov 17 23:26:53 chaembian systemd-fsck[254]: Block size in bytes: 4096
    Nov 17 23:26:53 chaembian systemd-fsck[254]: Filesystem size in blocks: 50000094
    Nov 17 23:26:53 chaembian systemd-fsck[254]: **Phase 0 - Replay Journal Log
    Nov 17 23:26:53 chaembian systemd-fsck[254]: Filesystem is clean.
    Nov 17 23:26:53 chaembian systemd[1]: Started File System Check on /dev/disk/by-uuid/8f972288-02c8-4dd7-a590-400f4fe60244.
    Nov 17 23:26:53 chaembian systemd[1]: Activated swap /dev/disk/by-uuid/cf5549b8-edd7-465a-985c-c096f39b916e.
    Nov 17 23:26:53 chaembian systemd[1]: Starting Swap.
    Nov 17 23:26:53 chaembian systemd[1]: Reached target Swap.
    Nov 17 23:26:53 chaembian systemd[1]: Found device ST31000524AS.
    Nov 17 23:26:53 chaembian systemd[1]: Starting File System Check on /dev/disk/by-uuid/b36313d6-8efb-444c-b6c9-0d3ca3bdaad1...
    Nov 17 23:26:53 chaembian systemd[1]: Found device ST31000524AS.
    Nov 17 23:26:53 chaembian systemd[1]: Starting File System Check on /dev/disk/by-uuid/e4ee5aff-ef4a-436c-9385-cb37b98df3e1...
    Nov 17 23:26:53 chaembian systemd[1]: Found device ST31000524AS.
    Nov 17 23:26:53 chaembian systemd[1]: Starting File System Check on /dev/disk/by-uuid/da692a03-33e5-4aad-b716-7dedfea99f85...
    Nov 17 23:26:53 chaembian systemd-fsck[267]: fsck.jfs version 1.1.15, 04-Mar-2011
    Nov 17 23:26:53 chaembian systemd-fsck[267]: processing started: 11/17/2013 23:26:53
    Nov 17 23:26:53 chaembian systemd-fsck[267]: The current device is: /dev/sda8
    Nov 17 23:26:53 chaembian systemd-fsck[267]: Block size in bytes: 4096
    Nov 17 23:26:53 chaembian systemd-fsck[267]: Filesystem size in blocks: 24999140
    Nov 17 23:26:53 chaembian systemd-fsck[267]: **Phase 0 - Replay Journal Log
    Nov 17 23:26:53 chaembian systemd-fsck[267]: Filesystem is clean.
    Nov 17 23:26:53 chaembian systemd[1]: Started File System Check on /dev/disk/by-uuid/b36313d6-8efb-444c-b6c9-0d3ca3bdaad1.
    Nov 17 23:26:53 chaembian systemd[1]: Mounting /home...
    Nov 17 23:26:53 chaembian systemd-fsck[273]: fsck.jfs version 1.1.15, 04-Mar-2011
    Nov 17 23:26:53 chaembian systemd-fsck[273]: processing started: 11/17/2013 23:26:53
    Nov 17 23:26:53 chaembian systemd-fsck[273]: The current device is: /dev/sda10
    Nov 17 23:26:53 chaembian systemd-fsck[273]: Block size in bytes: 4096
    Nov 17 23:26:53 chaembian systemd-fsck[273]: Filesystem size in blocks: 161393838
    Nov 17 23:26:53 chaembian systemd-fsck[273]: **Phase 0 - Replay Journal Log
    Nov 17 23:26:53 chaembian systemd-fsck[273]: Filesystem i

  • HOW TO SOLVE THE R6034 ERROR IN ITUNES INSTALATION

    I need toknow how to solve the R6034 error in itunes instalation becouse y can´t buk up muy phone

    How to solve this ?
    #import <UIKit/UIKit.h>
    int main(int argc, char *argv[]) {
        NSAutoreleasePool * pool = [[NSAutoreleasePool alloc] init];
       -> int retVal = UIApplicationMain(argc, argv, nil, nil);
        [pool release];
        return retVal;

  • How i can solve 6753 airport error

    how i can solve 6753 airport error?

    IIRC, it's not uncommon to spot this after a firmware update to 7.6.1.  And IIRC, wasn't there a 7.6.2 release today?  Unplug the express, plug it back in, and generally this should self-resolve.

  • How to solve Audition CS6 error "The amount of audio to burn will not fit on the CD........."?

    I have a brand new PC that is MORE than adequate. I have once succeeded in burning a CD after learning all about time tracks and merging them. (made a few with only ONE track)
    Two things:
    1) I find that I must add a CD marker at the end of the WAV because Audition CS6 erases whatever is the last CD marker I've made. Very frustrating but now I know I have to do this but I have no idea WHY!!
    2) Right now I have a WAV that is just over 1 hour and 3 minutes with a total of 637.74MB of info. When I try to export/burn a CD, I get an error message stating "The amount of audio to burn will not fit.......".  I am using TDK 700MB blanks with a Pioneer Blu-ray burner.
    Obviously it will fit.
    What am I doing wrong, all of a sudden?

    Hey ryclark,
    Thanks for responding. Something else is going on here.....
    Here's what I re-replied to our friend...
    Thanks for the response.
    When I built this computer last Nov/Dec, it was built with the second 
    fastest Intel 7i, quad-core chipset on an 64-bit ASUS motherboard. It's  running
    Win 7 Pro. It has a 500GB SSD "C" drive with another 14 TB of true hard 
    drive space. It is set up with 64 bit. I had been using Audition CS3 for  many
    years and even go back to it's origin: Cool Edit and Cool Edit Pro. My 
    learning curve was minimal, sans the CD burning, which I used other software
    for  which is now antiquated, so I need Audition for this. Between this and 
    IZotope 3 I've repaired and improved many a recording. All-in-all extremely 
    useful software.
    As for the idea "to burn it anyway", well the error message comes up and 
    that's it - if I "X" out of that message and try to burn again the message
    comes  back  - so Audition will not let me. It is convinced that this file is 
    longer than it really is, but only when I add track  marks to it!
    There are only 11 tracks.
    I was able to burn a CD of this same file but without all the track marks, 
    so the same exact file length/size will burn, only as the one track.
    I've also succeeded in burning other WAV's , both greater and smaller, with
    and without multiple track marks, without issue. Of course all with less 
    than the CD's max. capacity.
    This problem seems to be with this one file. I've even  re-made/re-recorded
    the file from scratch with no change. There's something else  going on here
    that I can't put my finger on. (I am "recording" LP's and making  personal
    CDs of them)
    Also, only from time to time, I have another error after burning a CD that 
    states it could not verify the CD. For this I assume it is the blank rather
    than AA? The first might burn without issue and with the second burn I 
    get the error. It is near the end of a stack of blanks, so.....
    As for the need to "mark the end" of the file makes a lot of sense but of 
    all the other CD track-marking software I've used, none needed one to do
    this,  but this IS Adobe after all.
    You'd think there might be a smidge of intuitiveness with Adobe, but maybe 
    not.
    - Mark
    In a message dated 8/2/2014 8:11:52 A.M. Eastern Daylight Time, 
    [email protected] writes:
    How  to solve Audition CS6 error "The amount of audio to burn will not fit
    on  the CD........."?
    created by ryclark (https://forums.adobe.com/people/ryclark)  in 
    Audition CS5.5, CS6 & CC - View the full  discussion
    (https://forums.adobe.com/message/6605916#6605916)

  • How to solve the 404 error

    Hi,
    How to catch or solve the 404 error in application.
    Some time we are giving some file name but that file is not avialable at that time it will give 404 error. how to avoid this error.
    If 404 error comes i want call some other file. Is it posible.
    Thanks Advance.

    Yes, this is because IE 5.5 (?) and higher have this wacky "Show friendly HTTP error messages" setting. You can disable this by going to tools -> internet options -> advanced and unchecking "Show friendly HTTP error messages". However as the default IE setting has "Show friendly HTTP error messages" enabled this isn't a good solution.
    I believe that if your error page is less than a certain size (in bytes) then IE defaults to it's own error page when "Show friendly HTTP error messages" are enabled. This size is something like 512 bytes or fewer in length.
    So basically try making your error page larger (more than 512 bytes in size) and see if that works.

  • "Error 16" solution doesn't solve problem, same error message pops up.  Further steps?

    Steps followed: all Adobe products (CS6 Suite and CC) have been removed (w/uninstaller and manual Library cleanup) and reinstalled (from discs and downloads); permissions corrected as per KB note on Error 16, to no change. This occurred after updating Mac OS to 10.9x. The OS was then reinstalled, new admin & standard users created (MacPro hardware passes all tests). "Error 16" permission solution performed at every stage to no change in error generation. Adobe Reader, Lightroom 4, and CS6Bridge do launch, but Acrobat Professional, Photoshop (13, CS6), and CC Photoshop stop launch w/error 16.  Stumped!

    Thanks for the suggestion, Gene, but it had no affect on the ³error 16²
    situation, I¹m afraid.  I think I¹m going to have to start with a new drive
    and import/update until I find the source of this issue.
    Jim
    "Error 16" solution doesn't solve problem, same error message pops up.
    Further steps?
    created by gener7 <https://forums.adobe.com/people/gener7>  in Photoshop
    General Discussion - View the full discussion
    <https://forums.adobe.com/message/7154907#7154907>
    Permissions problem.  Open Terminal and copy/paste this line: sudo chmod -R
    777 /Library/Application\ Support/Adobe Gene
    If the reply above answers your question, please take a moment to mark this
    answer as correct by visiting:
    https://forums.adobe.com/message/7154907#7154907 and clicking ŒCorrect¹ below
    the answer Replies to this message go to everyone subscribed to this thread,
    not directly to the person who posted the message. To post a reply, either
    reply to this email or visit the message page:
    Please note that the Adobe
    Forums do not accept email attachments. If you want to embed an image in your
    message please visit the thread in the forum and click the camera icon:
    https://forums.adobe.com/message/7154907#7154907 To unsubscribe from this
    thread, please visit the message page at
    , click "Following" at the
    top right, & "Stop Following" Start a new discussion in Photoshop General
    Discussion by email
    <mailto:[email protected]>  or
    at Adobe Community
    <https://forums.adobe.com/choose-container.jspa?contentType=1&containerType=14
    &container=4694>  For more information about maintaining your forum email
    notifications please go to https://forums.adobe.com/thread/1516624.
    >

  • HT201405 how to solve time machine error-1

    how to solve time machine error-1

    I checked the pondini fixes and ended up doing the following - in case this could help someone else with OSX Lion and Time Capsule... http://pondini.org/TM/Troubleshooting.html
    First, I downloaded and used Airport Utility 5.6 instead of 6.1 - BTW, I had to attempt download and installation THREE times before the program actually installed.  Be persistant.
    Pondini #5: It's possible some names (of all things!) may be a problem.    See item C9.  I had to re-name my Mac, Time Capsule, network, etc... to remove all apostrophes and spaces.
    Pondini #7:  If you have WD SmartWare installed on Lion, it's not compatible, per RoaringApps, and there are reports it can cause this problem as well.   Use Western Digital's uninstaller, or delete the app from /Applications and the files com.wdc.WDDMservice.plist and com.wdc.WDSmartWareServer.plist from /Library/LaunchDaemons.   There may also be a file in Library/Application Support.
    I then had to shut down computer, unplug Time Capsule, unplug modem; plug everything in again, then reboot computer; then had to go to Apple- System Preferences- Network- and reselect my Time Capsule to connect to WiFi again.
    Then opened Time Machine preferences again and attempted back up - it worked!

Maybe you are looking for