Systemd practices?

I decided to move to systemd a while back, by following the guide on the wiki.
I got as far as to pure systemd, but my rc.local and rc.local.shutdown aren't empty.
So now I'm stuck, because I don't know what the "best practice" is with these startup/shutdown scripts.
rc.local contains this:
/usr/local/sbin/acpidpwr-update
and rc.local.shutdown this:
find /home/bladt/.tmp -atime +30 -exec rm {} \;
The line in rc.local makes sure acpid gets updated about the power supply after boot (I'm on a laptop).
Supposedly systemd can handle some of the stuff acpid handles, but not this.
(maybe it should be a udev rule or something?)
The line in rc.local.shutdown just cleans up a little in a directory I use for temporary files (vim ~ and .swap files and screen dumps mostly).
Now where should I put these? should they be made into services or what is the right way?

OK. It turns out that you also need to read 'man systemd-tmpfiles'. The 'Type' field doesn't really mean anything other than pay 'attention to this directory' when cleaning. In your case, use d as per tmp.conf. This was a terrible design decision. The grammar should have been as follows:
Line ::= Type Path Arguments*
|| Constraints
Type ::= CreateTypes
|RemoveTypes
|WriteTypes
|CleanTypes
|SELinuxTypes
|LinkTypes
// f: create file
// F: create and truncate file
// p: create pipe
// c: create char dev
// b: create block dev
// d: create dir
// D: create and truncate dir
CreateTypes ::= 'f'|'F'|'p'|'c'|'b'|'d'|'D'
// r: remove
// R: remove recursive
RemoveTypes ::= 'r'|'R'
// w: write string to...
WriteTypes ::= 'w'
// c: clean this directory
// x: except these files
CleanTypes ::= 'c'|'x'
// z: restore label
// Z: recursively restore label
SELinuxTypes ::= 'z'|'Z'
// L: link
LinkTypes ::= 'L'
Arguments ::= CreateArguments
Arguments |RemoveArguments
|WriteArguments
|CleanArguments
|SELinuxArguments
|LinkArguments
CreateArguments ::= Mode|UID|GID
RemoveArguments ::= Path
WriteArguments ::= String
CleanArguments ::= Age
SELinuxArguments ::= Label
LinkArguments ::= Path
Constraints ::= CreateConstraint
|| RemoveConstraint
|| WriteConstraint
|| CleanConstraint
|| SELinuxConstraint
|| LinkConstraint
CreateConstraint ::= CreateTypes Path Mode UID GID
RemoveConstraint ::= RemoveTypes Path
WriteConstraint ::= WriteTypes Path String
CleanConstraint ::= CleanTypes Path Age
SELinuxConstraint ::= SELinuxTypes Path Label
LinkConstraint ::= LinkTypes Path Path
TL;DR: clean in separate rules and define arguments on a per type basis.
(define gratuitous  <this>)
-- edit: glaring discrepancies.
Last edited by Stebalien (2012-10-19 03:57:04)

Similar Messages

  • [SOLVED] Best Practice for systemd, udisks, udev, polkit,and openbox

    I have to admit I am stymied here.  I have been in the wiki and forums most of the day and am just not finding the solution here.
    I have both udisks and udisks2 installed
    I am running a pure systemd
    I do not use a login manager
    I use startx that has a switch clause based on an environmental variable to pick the environment I want.
    For now, let's limit this to xfce4 and openbox.
    I used to be able to log in and mount usb and SD volumes using Thunar, Dolphin, and palimpsest.  I can no longer do that; I receive an error indicating I've not the proper privileges.
    Even more fun, I log into a console and use udiskie, and can mount volumes without issue.
    I start X with startx, launch a terminal program, and udiskie will no longer allow me to mount.  I can read volumes mounted by udiskie before I started X.
    I have tried various combinations of ck-launch-session, dbus-launch in concert with openbox-session and startxfce4.  Nothing allows me to automount as a normal user.  This used to work, but something has gone south, but I am not clear when.
    Anyone have suggestions for a stable solution here?
    A couple files as they exist right now:
    ewaller@odin:~ 1005 %cat .xinitrc
    #xset b off
    setxkbmap -option ctrl:nocaps
    case $WM in
    openbox)
    exec ck-launch-session openbox-session
    e17)
    dbus-launch
    enlightenment_start
    vb)
    VirtualBox -startvm "Windows XP" -fullscreen
    xfce4)
    exec ck-launch-session startxfce4
    exec ck-launch-session startxfce4
    esac
    ewaller@odin:~ 1006 %cat /etc/polkit-1/localauthority/50-local.d/10-udisks.pkla
    [Local Users udisk2]
    Identity=unix-group:users
    Action=org.freedesktop.udisks2.*
    ResultAny=yes
    ResultInactive=yes
    ResultActive=yes
    [Local Users udisk]
    Identity=unix-group:users
    Action=org.freedesktop.udisks.*
    ResultAny=yes
    ResultInactive=yes
    ResultActive=yes
    ewaller@odin:~ 1007 %
    ewaller@odin:~[1] 1007 %
    Last edited by ewaller (2012-10-16 03:28:49)

    Are you starting X onto the same vt you logged into i.e. startx -- vt1 for tty1 or startx -- vt$(fgconsole) (or falconindy's xserverrc) for a more general case?   If you don't, systemd-logind cannot keep track of the session and the -kit permissions will thus break.
    You can see sessions using loginctl:
    └$ loginctl
    SESSION UID USER SEAT
    1 1000 zekesulastin seat0
    4 1000 zekesulastin seat0
    2 sessions listed.
    You can see information about your sessions using loginctl show-session $num - the session must be Active:
    └$ loginctl show-session 4
    Id=4
    Timestamp=Sun, 14 Oct 2012 23:18:56 -0400
    TimestampMonotonic=49646619798
    DefaultControlGroup=name=systemd:/user/zekesulastin/4
    VTNr=1
    TTY=tty1
    Remote=no
    Service=login
    Leader=12771
    Audit=4
    Type=tty
    Class=user
    Active=yes <-- This must be "yes"
    State=active
    KillProcesses=no
    IdleHint=yes
    IdleSinceHint=1350271136064237
    IdleSinceHintMonotonic=49646611251
    Name=zekesulastin
    (I personally have a conditional in bash_profile to exec startx -- vt1 if I log in on tty1.)
    Last edited by ZekeSulastin (2012-10-15 04:37:59)

  • [Solved] Keyboard layout - best practice

    I have two laptops running Arch Linux. On the first I have set norwegian keyboard with:
    Option "XkbLayout" "no"
    in then keyboard section of /etc/X11/xorg.conf.d/10-evdev.conf.
    On the second I have usede
    localectl set-x11-keymap no
    from CLI to set the keymap.
    What ist best practice?
    Last edited by torors (2014-07-30 14:53:22)

    localectl creates /etc/X11/xorg.conf.d/00-keyboard.conf
    $ cat /etc/X11/xorg.conf.d/00-keyboard.conf
    # Read and parsed by systemd-localed. It's probably wise not to edit this file
    # manually too freely.
    Section "InputClass"
    Identifier "system-keyboard"
    MatchIsKeyboard "on"
    Option "XkbLayout" "pl"
    EndSection
    Another computer:
    $ cat /etc/X11/xorg.conf.d/00-keyboard.conf
    # Read and parsed by systemd-localed. It's probably wise not to edit this file
    # manually too freely.
    Section "InputClass"
    Identifier "system-keyboard"
    MatchIsKeyboard "on"
    Option "XkbLayout" "pl"
    Option "XkbModel" "pc105"
    Option "XkbOptions" "terminate:ctrl_alt_bksp"
    EndSection
    Neither of hem has /etc/X11/xorg.conf.d/10-evdev.conf, but they have /usr/share/X11/xorg.conf.d/10-evdev.conf - xorg-server 1.16 style.
    Last edited by karol (2014-07-30 12:54:24)

  • Systemd list-unit-files shows lots of session-c$X$Y.scope's

    Hey guys,
    as the title already tells, my systemd shows a lot of session-c$X$Y.scope files counting from session-c4.scope to session-c56.scope, some numbers seem to be left out.
    Even while not knowing what those scope's actually are, I presume that this behaviour can't be normal, or is it?
    And why are there so many of those files? Did they appear after an update, that broke something? Is there a new scope file for each time I use my PC?
    greetings
    Kofweh

    [ 3700.327] (++) Using config file: "/root/xorg.conf.new"
    - running X as root is considered bad practice
    - X has good autodetection , vast majority of users don't need any config files.
    Try running X as user without any configuration files you created.

  • Systemd? why?

    i installed systemd with initscripts for arch.
    i improve my boot just a little and something like rc.local.service don't work.
    my question is: why systemd for a fast distribution like archlinux?

    mrmylanman wrote:
    Just to throw some additional information in here:
    systemd will be officially supported soon (see http://mailman.archlinux.org/pipermail/ … 2803.html), and may even become the default.
    Not sure if anyone knew that or not, but I'd say this lends more "credibility" to it, in my opinion.  I also have had nothing but pleasant experiences using it.
    Yeah i read that, which was what made me wanting to vent and ask and discuss it again.
    tomegun wrote:
    PReP wrote:
    1: - on demand activation of services (e.g. you really don't need cups running all the time)
       My take on this, is that it is better to not run too many services in the first place,
       even if you "feel" like you need this and that.
       For the few that you use very rarely, i feel it very easy to just start it myself.
       In this case, instead of "running cups all the time", one would run the system to check when to run this or that - all the time instead.
    I don't really get your point here. With systemd you get all the benefit of not running any unneeded daemons, but at the same time you never have to start daemons manually when needed... Why would you rather manually start cups when you need it instead of having it start by itself only when needed?
    2: - almost anything is a unit, meaning it can be a dependency (e.g. any sysfs path, device, filesystem path)
       What are the biggest benifit of this in practice, for a fine-tuned maching not running too many services?
    The simpler your setup, the smaller the benefit of course. That said, the benefit would be that you can start a daemon when a certain device is plugged in (e.g. bluez when a bluetooth adapter appears or cups when a printer is connected), or when a certain file appears, etc.
    This is obviously not something for everyone, but for early boot (think rc.sysinit) this kind of control is very useful, and allows us to remove some hacks that we currently have.
    3: - automounting of any device on first access with fsck pre-mount (how often do you really need /boot mounted?)
       For me, all the normal drives are mounted in fstab, to be there all the time anyways,
       and others, like my usb or cd'drives, i really do prefer to mount them myself at need,
       most usb drives has a long wake-up time, so it is quite annoying to have it re-mounted when accessed,
       and it takes quite a bit of time,
    Systemd is only meant to control devices in /etc/fstab, typically your usb devices would be controlled by udisks, so that is sort of a different discussion. It might be worth pointing out that systemd would not "re-mount on access", the fs is fsck'ed and mounted on first access and stays mounted after that. Examples of why this might be useful is, as Dave mentioned, fs'es that are rarely used (/boot), but also fs'es that are always mounted might benefit from automounting. In order to speed up my boot I automount my /home. This means that systemd will start fscking/mounting it as soon as it can, but it will not wait for /home to be available before starting kdm (or any other service). Rather, if and when kdm tries to access /home it will just wait until the directory becomes available.
    4; - daemon supervision
       This i cannot comment, since i do not have much knowledge on the subject,
       what are supervised, besides from the previously noted dep-check, and what are the benifits?
    This (along with the point below) is the most important feature of systemd, imho. The point is that with systemd an administrator can know the state of the system, which is not really possible with sysvinit. You can find out if a daemon is running, stopped or crashed, and you know which processes belong to which daemon. Even if you have several instances of the same daemon, and it's children have double-forked (so a simple "ps aux" tells you nothing). Once we have this, we can make policies of what to do in given scenarios. Restarting crashing daemons, etc. As of the next version of systemd we'll also have (optional) watchdog support. I.e., if a daemon hangs without crashing, it will be restarted, and if systemd itself hangs  the computer will be rebooted.
    5: - fine grained control of services -- niceness, oom_adj_score, scheduling policy, fd 0,1,2 redirections, syslog facility/prio, security limits...
       Are these really properties that we cannot already control without systemd as a system-swiss-army-knife?
    Everything can be controlled in the individual rc script now. However, especially in the case of security sensitive settings, getting it right is very difficult so it either not done, or it is done wrongly. In systemd's unit file, you just specifiy what you want, and systemd itself will take care of all the fiddly details to get it right (and if there are bugs, they will be fixed in one place that benefit all daemons, on all distros).
    Finally, the boot-time discussion also feels a bit unmotivated,
    again, not booting every service under the sun already,
    and computer-speed increasing alleviates this.
    I believe that boot-time can never be fast enough, and with systemd we have the opportunity to improve it a lot. Imagine the embedded case of switching on a phone / TV. You don't want to wait around for several seconds before you can use it. The fact that we accept long waits when it comes to computers is just sad imho.
    While systemd already improves speed somewhat (or a lot, depending on who you ask), there are still lots of cases to improve, so I am very optimistic about this. The difference between systemd and sysvinit is that in sysvinit we don't have the architecture in place to start optimizing, and we don't have contributors who focus on this.
    The booting time is the thing that bothers me most to be hearing about repetively as a reason for systemd, even if that might not be it's larger drive.
    The boot times _are_ fast already, when one deals carefully with what one runs or loads,
    shaving,. say, 1-10 to perhaps even 20 seconds for booting off (if going extreme), what would one have done in those few seconds that was so important?
    For me, it feels like taking one, or three sips on my coffe or not, before getting to business,
    it is not something that hinders me from completing my work, those few seconds,
    and a stable system is not meant to be booted often at all.
    Even booting as often as once a day, 20 seconds a day is not a critical lose of time.
    I boot in about 8 seconds after bios and grub has done their thing, and my mothers much older machine does it in 15 perhaps,
    it was a long time ago boot time felt annyoing in my opinion.
    The other virtues you meantion, they do sound like good things, certainly,
    but as it stands now, having followed the systemd mailing list, and arch-dev-mail discussions, and threads here on arch,
    i still don't see any great benifits from what i read people discussing/saying/reporting.
    Most often, it is about why something that has already worked well, does not work that easily, with systemd.
    And in the systemd mailing list, many replies to things not working seems to end with stuff like:
    "Well, we won't support that no more/that is not supported no more on fedora, other distros will probably follow suit",
    Why all the fuss?, do we really need to repair things?
    I will deal with systemd when i have too, i just do not think it fits into either KISS,, or linux principle,
    And i hope Arch can be on systemd and still feel Arch, not just turning into "a distro like the others only with pacman".
    Systemd gives me this feeling of slowly loosing the control i have gotten with linux, over,
    say, windows-systems and their "services".
    But, i think i will save some of my arguments until we have seen where systemd takes us, in linux,
    I just hope people stay positively/constructively critical and thinks things over closely
    (Oh i do find it hard explaining my thoughts on this in words)
    Last edited by PReP (2012-04-15 16:46:23)

  • [SOLVED} systemd, netcfg, interface aliases and race conditions

    Not using NetworkManager - base Arch Linux with standard netcfg
    The situation (coming from an old SysV-init guy who's pretty new to systemd):
    I have an application that has a dependency on a specific interface alias.  To be more specific:
    1) eth0 comes up as a DHCP interface (but the address is static on the DHCP server side) and assigns the base IP, which we'll call 192.168.1.2
    2) network.target is satisfied since the interface is up
       3a) netcfg POST_UP executes on the interface, assigning IP address 192.168.1.3 with label eth0:0 to eth0
       3b) The application service (with an After of network.target) starts, attempting to bind a port listener on address 192.168.1.3
    Therein lies the rub.  3a and 3b happen in parallel, creating a race condition.  If the alias happens to be assigned before the application starts, all is well.  If the application initializes before the alias, it dies an ugly death, failing to bind to a non-existent address.  It's a coin toss which one "wins".
    My solution thus far has been to add a ExecStartPre stanza to the application's service calling "/usr/bin/sleep 5", pretty much guaranteeing that the alias will be defined before the application's ExecStart.  This is so ugly and inelegant it's embarassing.
    Two questions:
    - Is there a cleaner way to approach this - perhaps some way to indicate to systemd that eth0:0 must exist prior to starting the application (along the lines of a mythical AfterInterface element ?  I'd considered creating a 0-byte file in /tmp in POST_UP and having my application service check for existence, but it seems that if it doesn't exist, systemd will just skip launching the service, not delay its launch.  I cannot create the alias as part of ExecStartPre for the application, since this interface alias is actually used by multiple applications/services.
    - Would migrating to netctl alleviate this at all (to be more specific, does netctl have a more coherent definition of interface aliasing than hand-creating them via POST_UP, and if so, are the aliases defined by netctl prior to satisfying network.target)?
    Thanks much for any insight,
    Rodney
    Last edited by rhester72 (2013-05-03 16:46:47)

    I can...but my understanding of why the AL wiki recommends assigning aliases in POST_UP is to ensure they are consistently assigned if the interface should be brought offline and back online.  I'm not sure if this is an issue in practice, however - since the same contention would exist on the simplest-possible construct (i.e. what happens to all the services that have network listeners if eth0 just goes away for a while and comes back?).
    Rodney

  • Logging all file opens immediately at systemd boot?

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

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

  • How am I reading systemd boot screen?

    Hello,
    There should be a message during boot time (like this), but quickly disappear. Is there a way to add Press any key to continue after the last systemd process.
    Some time, at logout, I can see some message there in a ladder-shape manner. But that I don't mind, just to mention.
    I saw systemd listing while booting archiso, that screen persist up to login.
    Usually I can't see it unless some failure appear, but swiftly goes to login prompt or graphical login. So when some failure comes up I'd like to have a chance to put a stop and read the message.

    karol wrote:
    Post your
    cat /proc/cmdline
    root=LABEL=Linux64 quiet rw pcie_aspm=off rcutree.rcu_idle_gp_delay=1 initrd=/initramfs-linux.img
    I'm not on the right computer, now. Anyways it's a learning practice, rather than a troubleshooting
    karol wrote:f you log in to the tty manually, you can keep the systemd output on the screen.
    I don't get you. I suppose if my target is graphical.target then I won't see anything, still. In facts we generally enable a *dm.service.
    But as you may want to tell me, I may set cmdline to stop ad multi-user.target. Even that, the login prompt will go in a cleared screen.
    Like the era of sysV, I was using a script in rc.local (or initrc I don't remember) to stop that display. Here my question is about how to make a similar condition. It could be a *.service that will kick in within sysinit,target and graphical.target and display Press any key to continue message.
    I just need some clue
    Last edited by TheSaint (2014-10-31 06:23:45)

  • Logical level in Fact tables - best practice

    Hi all,
    I am currently working on a complex OBIEE project/solution where I am going straight to the production tables, so the fact (and dimension) tables are pretty complex since I am using more sources in the logical tables to increase performance. Anyway, what I am many times struggling with is the Logical Levels (in Content tab) where the level of each dimension is to be set. In a star schema (one-to-many) this is pretty straight forward and easy to set up, but when the Business Model (and physical model) gets more complex I sometimes struggle with the aggregates - to get them work/appear with different dimensions. (Using the menu "More" - "Get levels" does not allways give the best solution......far from). I have some combinations of left- and right outer join as well, making it even more complicated for the BI server.
    For instance - I have about 10-12 different dimensions - should all of them allways be connected to each fact table? Either on Detail or Total level. I can see the use of the logical levels when using aggregate fact tables (on quarter, month etc.), but is it better just to skip the logical level setup when no aggregate tables are used? Sometimes it seems like that is the easiest approach...
    Does anyone have a best practice concerning this issue? I have googled for this but I haven't found anything good yet. Any ideas/articles are highly appreciated.

    Hi User,
    For instance - I have about 10-12 different dimensions - should all of them always be connected to each fact table? Either on Detail or Total level.It not necessary to connect to all dimensions completely based on the report that you are creating ,but as a best practice we should maintain all at Detail level only,when you are mentioning any join conditions in physical layer
    for example for the sales table if u want to report at ProductDimension.ProductnameLevel then u should use detail level else total level(at Product,employee level)
    Get Levels. (Available only for fact tables) Changes aggregation content. If joins do not exist between fact table sources and dimension table sources (for example, if the same physical table is in both sources), the aggregation content determined by the administration tool will not include the aggregation content of this dimension.
    Source admin guide(get level definition)
    thanks,
    Saichand.v

  • Best practices for setting up users on a small office network?

    Hello,
    I am setting up a small office and am wondering what the best practices/steps are to setup/manage the admin, user logins and sharing privileges for the below setup:
    Users: 5 users on new iMacs (x3) and upgraded G4s (x2)
    Video Editing Suite: Want to connect a new iMac and a Mac Pro, on an open login (multiple users)
    All machines are to be able to connect to the network, peripherals and external hard drive. Also, I would like to setup drop boxes as well to easily share files between the computers (I was thinking of using the external harddrive for this).
    Thank you,

    Hi,
    Thanks for your posting.
    When you install AD DS in the hub or staging site, disconnect the installed domain controller, and then ship the computer to the remote site, you are disconnecting a viable domain controller from the replication topology.
    For more and detail information, please refer to:
    Best Practices for Adding Domain Controllers in Remote Sites
    http://technet.microsoft.com/en-us/library/cc794962(v=ws.10).aspx
    Regards.
    Vivian Wang

  • [systemd] shutdown takes a long time

    Hello.
    It takes quite a long time for my system to shutdown. The systemd ArchWiki suggests to log the shutdown like this. I am not quite sure what to look for. I suspect that smplayer or deluged might be the problem. Am I right and furthermore what can I do about it?
    Thank you for your time.
    Here the shutdown log:
    [ 0.000000] Initializing cgroup subsys cpuset
    [ 0.000000] Initializing cgroup subsys cpu
    [ 0.000000] Linux version 3.5.3-1-ARCH (tobias@T-POWA-LX) (gcc version 4.7.1 20120721 (prerelease) (GCC) ) #1 SMP PREEMPT Sun Aug 26 09:14:51 CEST 2012
    [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=55614e59-14b9-47c5-a609-fd76662e6403 ro systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M enforcing=0 quiet
    [ 0.000000] e820: BIOS-provided physical RAM map:
    [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009bfff] usable
    [ 0.000000] BIOS-e820: [mem 0x000000000009c000-0x000000000009ffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000005ffeffff] usable
    [ 0.000000] BIOS-e820: [mem 0x000000005fff0000-0x000000005fff2fff] ACPI NVS
    [ 0.000000] BIOS-e820: [mem 0x000000005fff3000-0x000000005fffffff] ACPI data
    [ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000ffffffff] reserved
    [ 0.000000] NX (Execute Disable) protection: active
    [ 0.000000] DMI 2.2 present.
    [ 0.000000] DMI: /MS-7030, BIOS 6.00 PG 11/10/2005
    [ 0.000000] e820: update [mem 0x00000000-0x0000ffff] usable ==> reserved
    [ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
    [ 0.000000] AGP bridge at 00:00:00
    [ 0.000000] Aperture from AGP @ e0000000 old size 32 MB
    [ 0.000000] Aperture size 4096 MB (APSIZE 0) is not right, using settings from NB
    [ 0.000000] Aperture from AGP @ e0000000 size 32 MB (APSIZE 0)
    [ 0.000000] e820: last_pfn = 0x5fff0 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-BFFFF uncachable
    [ 0.000000] C0000-C7FFF write-protect
    [ 0.000000] C8000-FFFFF uncachable
    [ 0.000000] MTRR variable ranges enabled:
    [ 0.000000] 0 base 0000000000 mask FFC0000000 write-back
    [ 0.000000] 1 base 0040000000 mask FFE0000000 write-back
    [ 0.000000] 2 base 00E0000000 mask FFF0000000 write-combining
    [ 0.000000] 3 disabled
    [ 0.000000] 4 disabled
    [ 0.000000] 5 disabled
    [ 0.000000] 6 disabled
    [ 0.000000] 7 disabled
    [ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    [ 0.000000] found SMP MP-table at [mem 0x000f4fc0-0x000f4fcf] mapped at [ffff8800000f4fc0]
    [ 0.000000] initial memory mapped: [mem 0x00000000-0x1fffffff]
    [ 0.000000] Base memory trampoline at [ffff880000096000] 96000 size 24576
    [ 0.000000] init_memory_mapping: [mem 0x00000000-0x5ffeffff]
    [ 0.000000] [mem 0x00000000-0x5fdfffff] page 2M
    [ 0.000000] [mem 0x5fe00000-0x5ffeffff] page 4k
    [ 0.000000] kernel direct mapping tables up to 0x5ffeffff @ [mem 0x1fcfd000-0x1fffffff]
    [ 0.000000] log_buf_len: 1048576
    [ 0.000000] early log buf free: 521388(99%)
    [ 0.000000] RAMDISK: [mem 0x37a32000-0x37d10fff]
    [ 0.000000] ACPI: RSDP 00000000000f8eb0 00014 (v00 Nvidia)
    [ 0.000000] ACPI: RSDT 000000005fff3040 00034 (v01 Nvidia AWRDACPI 42302E31 AWRD 00000000)
    [ 0.000000] ACPI: FACP 000000005fff30c0 00074 (v01 Nvidia AWRDACPI 42302E31 AWRD 00000000)
    [ 0.000000] ACPI: DSDT 000000005fff3180 048C1 (v01 NVIDIA AWRDACPI 00001000 MSFT 0100000E)
    [ 0.000000] ACPI: FACS 000000005fff0000 00040
    [ 0.000000] ACPI: SSDT 000000005fff7b80 000D6 (v01 PTLTD POWERNOW 00000001 LTP 00000001)
    [ 0.000000] ACPI: SRAT 000000005fff7cc0 00090 (v01 AMD HAMMER 00000001 AMD 00000001)
    [ 0.000000] ACPI: APIC 000000005fff7ac0 0007C (v01 Nvidia AWRDACPI 42302E31 AWRD 00000000)
    [ 0.000000] ACPI: Local APIC address 0xfee00000
    [ 0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
    [ 0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x0009ffff]
    [ 0.000000] SRAT: Node 0 PXM 0 [mem 0x00100000-0x5fffffff]
    [ 0.000000] NUMA: Node 0 [mem 0x00000000-0x0009ffff] + [mem 0x00100000-0x5ffeffff] -> [mem 0x00000000-0x5ffeffff]
    [ 0.000000] Initmem setup node 0 [mem 0x00000000-0x5ffeffff]
    [ 0.000000] NODE_DATA [mem 0x5feec000-0x5feeffff]
    [ 0.000000] [ffffea0000000000-ffffea00017fffff] PMD -> [ffff88005de00000-ffff88005f5fffff] on node 0
    [ 0.000000] Zone ranges:
    [ 0.000000] DMA [mem 0x00010000-0x00ffffff]
    [ 0.000000] DMA32 [mem 0x01000000-0xffffffff]
    [ 0.000000] Normal empty
    [ 0.000000] Movable zone start for each node
    [ 0.000000] Early memory node ranges
    [ 0.000000] node 0: [mem 0x00010000-0x0009bfff]
    [ 0.000000] node 0: [mem 0x00100000-0x5ffeffff]
    [ 0.000000] On node 0 totalpages: 393084
    [ 0.000000] DMA zone: 64 pages used for memmap
    [ 0.000000] DMA zone: 6 pages reserved
    [ 0.000000] DMA zone: 3910 pages, LIFO batch:0
    [ 0.000000] DMA32 zone: 6080 pages used for memmap
    [ 0.000000] DMA32 zone: 383024 pages, LIFO batch:31
    [ 0.000000] Nvidia board detected. Ignoring ACPI timer override.
    [ 0.000000] If you got timer trouble try acpi_use_timer_override
    [ 0.000000] ACPI: PM-Timer IO Port: 0x4008
    [ 0.000000] ACPI: Local APIC address 0xfee00000
    [ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] disabled)
    [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
    [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
    [ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
    [ 0.000000] IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23
    [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    [ 0.000000] ACPI: BIOS IRQ0 override ignored.
    [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge)
    [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge)
    [ 0.000000] ACPI: IRQ9 used by override.
    [ 0.000000] ACPI: IRQ14 used by override.
    [ 0.000000] ACPI: IRQ15 used by override.
    [ 0.000000] Using ACPI (MADT) for SMP configuration information
    [ 0.000000] SMP: Allowing 2 CPUs, 1 hotplug CPUs
    [ 0.000000] nr_irqs_gsi: 40
    [ 0.000000] PM: Registered nosave memory: 000000000009c000 - 00000000000a0000
    [ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000f0000
    [ 0.000000] PM: Registered nosave memory: 00000000000f0000 - 0000000000100000
    [ 0.000000] e820: [mem 0x60000000-0xfebfffff] available for PCI devices
    [ 0.000000] Booting paravirtualized kernel on bare hardware
    [ 0.000000] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:2 nr_node_ids:1
    [ 0.000000] PERCPU: Embedded 28 pages/cpu @ffff88005fc00000 s83392 r8192 d23104 u1048576
    [ 0.000000] pcpu-alloc: s83392 r8192 d23104 u1048576 alloc=1*2097152
    [ 0.000000] pcpu-alloc: [0] 0 1
    [ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 386934
    [ 0.000000] Policy zone: DMA32
    [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=55614e59-14b9-47c5-a609-fd76662e6403 ro systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M enforcing=0 quiet
    [ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
    [ 0.000000] __ex_table already sorted, skipping sort
    [ 0.000000] Checking aperture...
    [ 0.000000] AGP bridge at 00:00:00
    [ 0.000000] Aperture from AGP @ e0000000 old size 32 MB
    [ 0.000000] Aperture size 4096 MB (APSIZE 0) is not right, using settings from NB
    [ 0.000000] Aperture from AGP @ e0000000 size 32 MB (APSIZE 0)
    [ 0.000000] Node 0: aperture @ e0000000 size 256 MB
    [ 0.000000] Memory: 1532356k/1572800k available (4635k kernel code, 464k absent, 39980k reserved, 4212k data, 756k init)
    [ 0.000000] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, 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] NR_IRQS:4352 nr_irqs:512 16
    [ 0.000000] spurious 8259A interrupt: IRQ7.
    [ 0.000000] Console: colour dummy device 80x25
    [ 0.000000] console [tty0] enabled
    [ 0.000000] allocated 6291456 bytes of page_cgroup
    [ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
    [ 0.000000] Fast TSC calibration using PIT
    [ 0.000000] Detected 2009.231 MHz processor.
    [ 0.000000] Marking TSC unstable due to TSCs unsynchronized
    [ 0.006673] Calibrating delay loop (skipped), value calculated using timer frequency.. 4020.89 BogoMIPS (lpj=6697436)
    [ 0.006678] pid_max: default: 32768 minimum: 301
    [ 0.006716] Security Framework initialized
    [ 0.006725] AppArmor: AppArmor disabled by boot time parameter
    [ 0.006963] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
    [ 0.010848] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
    [ 0.012136] Mount-cache hash table entries: 256
    [ 0.012496] Initializing cgroup subsys cpuacct
    [ 0.012500] Initializing cgroup subsys memory
    [ 0.012520] Initializing cgroup subsys devices
    [ 0.012522] Initializing cgroup subsys freezer
    [ 0.012524] Initializing cgroup subsys net_cls
    [ 0.012526] Initializing cgroup subsys blkio
    [ 0.012564] tseg: 0000000000
    [ 0.012585] mce: CPU supports 5 MCE banks
    [ 0.012635] SMP alternatives: switching to UP code
    [ 0.018800] ACPI: Core revision 20120320
    [ 0.022927] ftrace: allocating 17956 entries in 71 pages
    [ 0.030518] ..TIMER: vector=0x30 apic1=0 pin1=0 apic2=-1 pin2=-1
    [ 0.064541] CPU0: AMD Athlon(tm) 64 Processor 3000+ stepping 00
    [ 0.066663] Performance Events: AMD PMU driver.
    [ 0.066663] ... version: 0
    [ 0.066663] ... bit width: 48
    [ 0.066663] ... generic registers: 4
    [ 0.066663] ... value mask: 0000ffffffffffff
    [ 0.066663] ... max period: 00007fffffffffff
    [ 0.066663] ... fixed-purpose events: 0
    [ 0.066663] ... event mask: 000000000000000f
    [ 0.083576] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
    [ 0.083636] Brought up 1 CPUs
    [ 0.083638] Total of 1 processors activated (4020.89 BogoMIPS).
    [ 0.084405] devtmpfs: initialized
    [ 0.086410] PM: Registering ACPI NVS region [mem 0x5fff0000-0x5fff2fff] (12288 bytes)
    [ 0.087408] NET: Registered protocol family 16
    [ 0.087567] node 0 link 0: io port [9000, ffff]
    [ 0.087570] TOM: 0000000060000000 aka 1536M
    [ 0.087573] node 0 link 0: mmio [a0000, bffff]
    [ 0.087577] node 0 link 0: mmio [d0000000, fe02ffff]
    [ 0.087580] bus: [00, 02] on node 0 link 0
    [ 0.087583] bus: 00 [io 0x0000-0xffff]
    [ 0.087585] bus: 00 [mem 0x000a0000-0x000bffff]
    [ 0.087587] bus: 00 [mem 0x60000000-0xfcffffffff]
    [ 0.087627] ACPI: bus type pci registered
    [ 0.087696] PCI: Using configuration type 1 for base access
    [ 0.088295] bio: create slab <bio-0> at 0
    [ 0.088374] ACPI: Added _OSI(Module Device)
    [ 0.088376] ACPI: Added _OSI(Processor Device)
    [ 0.088378] ACPI: Added _OSI(3.0 _SCP Extensions)
    [ 0.088380] ACPI: Added _OSI(Processor Aggregator Device)
    [ 0.089228] ACPI: EC: Look up EC in DSDT
    [ 0.093337] ACPI: Interpreter enabled
    [ 0.093342] ACPI: (supports S0 S1 S4 S5)
    [ 0.093368] ACPI: Using IOAPIC for interrupt routing
    [ 0.094190] ACPI: Power Resource [ISAV] (on)
    [ 0.099077] ACPI: No dock devices found.
    [ 0.099086] PCI: Ignoring host bridge windows from ACPI; if necessary, use "pci=use_crs" and report a bug
    [ 0.099148] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
    [ 0.099226] pci_root PNP0A03:00: host bridge window [io 0x0000-0x0cf7] (ignored)
    [ 0.099229] pci_root PNP0A03:00: host bridge window [io 0x0d00-0xffff] (ignored)
    [ 0.099233] pci_root PNP0A03:00: host bridge window [mem 0x000a0000-0x000bffff] (ignored)
    [ 0.099236] pci_root PNP0A03:00: host bridge window [mem 0x000c0000-0x000dffff] (ignored)
    [ 0.099238] pci_root PNP0A03:00: host bridge window [mem 0x60000000-0xfebfffff] (ignored)
    [ 0.099241] PCI: root bus 00: hardware-probed resources
    [ 0.099287] PCI host bridge to bus 0000:00
    [ 0.099291] pci_bus 0000:00: root bus resource [io 0x0000-0xffff]
    [ 0.099293] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
    [ 0.099296] pci_bus 0000:00: root bus resource [mem 0x60000000-0xfcffffffff]
    [ 0.099312] pci 0000:00:00.0: [10de:00e1] type 00 class 0x060000
    [ 0.099321] pci 0000:00:00.0: reg 10: [mem 0xe0000000-0xefffffff pref]
    [ 0.099381] pci 0000:00:01.0: [10de:00e0] type 00 class 0x060100
    [ 0.099413] pci 0000:00:01.1: [10de:00e4] type 00 class 0x0c0500
    [ 0.099420] pci 0000:00:01.1: reg 10: [io 0xfc00-0xfc1f]
    [ 0.099432] pci 0000:00:01.1: reg 20: [io 0x4c00-0x4c3f]
    [ 0.099437] pci 0000:00:01.1: reg 24: [io 0x4c40-0x4c7f]
    [ 0.099451] pci 0000:00:01.1: PME# supported from D3hot D3cold
    [ 0.099470] pci 0000:00:02.0: [10de:00e7] type 00 class 0x0c0310
    [ 0.099477] pci 0000:00:02.0: reg 10: [mem 0xfe02f000-0xfe02ffff]
    [ 0.099502] pci 0000:00:02.0: supports D1 D2
    [ 0.099504] pci 0000:00:02.0: PME# supported from D0 D1 D2 D3hot D3cold
    [ 0.099518] pci 0000:00:02.1: [10de:00e7] type 00 class 0x0c0310
    [ 0.099525] pci 0000:00:02.1: reg 10: [mem 0xfe02e000-0xfe02efff]
    [ 0.099550] pci 0000:00:02.1: supports D1 D2
    [ 0.099552] pci 0000:00:02.1: PME# supported from D0 D1 D2 D3hot D3cold
    [ 0.099567] pci 0000:00:02.2: [10de:00e8] type 00 class 0x0c0320
    [ 0.099575] pci 0000:00:02.2: reg 10: [mem 0xfe02d000-0xfe02d0ff]
    [ 0.099605] pci 0000:00:02.2: supports D1 D2
    [ 0.099607] pci 0000:00:02.2: PME# supported from D0 D1 D2 D3hot D3cold
    [ 0.099628] pci 0000:00:06.0: [10de:00ea] type 00 class 0x040100
    [ 0.099635] pci 0000:00:06.0: reg 10: [io 0xf000-0xf0ff]
    [ 0.099640] pci 0000:00:06.0: reg 14: [io 0xec00-0xec7f]
    [ 0.099645] pci 0000:00:06.0: reg 18: [mem 0xfe02c000-0xfe02cfff]
    [ 0.099665] pci 0000:00:06.0: supports D1 D2
    [ 0.099680] pci 0000:00:08.0: [10de:00e5] type 00 class 0x01018a
    [ 0.099696] pci 0000:00:08.0: reg 20: [io 0xe000-0xe00f]
    [ 0.099723] pci 0000:00:09.0: [10de:00ee] type 00 class 0x010185
    [ 0.099730] pci 0000:00:09.0: reg 10: [io 0x09e0-0x09e7]
    [ 0.099735] pci 0000:00:09.0: reg 14: [io 0x0be0-0x0be3]
    [ 0.099740] pci 0000:00:09.0: reg 18: [io 0x0960-0x0967]
    [ 0.099744] pci 0000:00:09.0: reg 1c: [io 0x0b60-0x0b63]
    [ 0.099749] pci 0000:00:09.0: reg 20: [io 0xcc00-0xcc0f]
    [ 0.099754] pci 0000:00:09.0: reg 24: [io 0xc800-0xc87f]
    [ 0.099779] pci 0000:00:0a.0: [10de:00e3] type 00 class 0x010185
    [ 0.099786] pci 0000:00:0a.0: reg 10: [io 0x09f0-0x09f7]
    [ 0.099791] pci 0000:00:0a.0: reg 14: [io 0x0bf0-0x0bf3]
    [ 0.099796] pci 0000:00:0a.0: reg 18: [io 0x0970-0x0977]
    [ 0.099801] pci 0000:00:0a.0: reg 1c: [io 0x0b70-0x0b73]
    [ 0.099806] pci 0000:00:0a.0: reg 20: [io 0xb400-0xb40f]
    [ 0.099810] pci 0000:00:0a.0: reg 24: [io 0xb000-0xb07f]
    [ 0.099834] pci 0000:00:0b.0: [10de:00e2] type 01 class 0x060400
    [ 0.099865] pci 0000:00:0e.0: [10de:00ed] type 01 class 0x060400
    [ 0.099892] pci 0000:00:18.0: [1022:1100] type 00 class 0x060000
    [ 0.099913] pci 0000:00:18.1: [1022:1101] type 00 class 0x060000
    [ 0.099931] pci 0000:00:18.2: [1022:1102] type 00 class 0x060000
    [ 0.099951] pci 0000:00:18.3: [1022:1103] type 00 class 0x060000
    [ 0.100003] pci 0000:01:00.0: [10de:0221] type 00 class 0x030000
    [ 0.100017] pci 0000:01:00.0: reg 10: [mem 0xfa000000-0xfaffffff]
    [ 0.100025] pci 0000:01:00.0: reg 14: [mem 0xd0000000-0xdfffffff pref]
    [ 0.100033] pci 0000:01:00.0: reg 18: [mem 0xfb000000-0xfbffffff]
    [ 0.100056] pci 0000:01:00.0: reg 30: [mem 0x00000000-0x0001ffff pref]
    [ 0.100111] pci 0000:00:0b.0: PCI bridge to [bus 01-01]
    [ 0.100115] pci 0000:00:0b.0: bridge window [io 0xa000-0xafff]
    [ 0.100119] pci 0000:00:0b.0: bridge window [mem 0xfa000000-0xfcffffff]
    [ 0.100123] pci 0000:00:0b.0: bridge window [mem 0xd0000000-0xdfffffff pref]
    [ 0.100147] pci 0000:02:07.0: [1814:0301] type 00 class 0x028000
    [ 0.100158] pci 0000:02:07.0: reg 10: [mem 0xfdff0000-0xfdff7fff]
    [ 0.100216] pci 0000:02:08.0: [10ec:8139] type 00 class 0x020000
    [ 0.100228] pci 0000:02:08.0: reg 10: [io 0x9c00-0x9cff]
    [ 0.100235] pci 0000:02:08.0: reg 14: [mem 0xfdfff000-0xfdfff0ff]
    [ 0.100260] pci 0000:02:08.0: reg 30: [mem 0x00000000-0x0000ffff pref]
    [ 0.100278] pci 0000:02:08.0: supports D1 D2
    [ 0.100280] pci 0000:02:08.0: PME# supported from D1 D2 D3hot D3cold
    [ 0.100298] pci 0000:02:09.0: [1106:3038] type 00 class 0x0c0300
    [ 0.100326] pci 0000:02:09.0: reg 20: [io 0x9800-0x981f]
    [ 0.100351] pci 0000:02:09.0: supports D1 D2
    [ 0.100354] pci 0000:02:09.0: PME# supported from D0 D1 D2 D3hot D3cold
    [ 0.100371] pci 0000:02:09.1: [1106:3038] type 00 class 0x0c0300
    [ 0.100399] pci 0000:02:09.1: reg 20: [io 0x9400-0x941f]
    [ 0.100424] pci 0000:02:09.1: supports D1 D2
    [ 0.100427] pci 0000:02:09.1: PME# supported from D0 D1 D2 D3hot D3cold
    [ 0.100445] pci 0000:02:09.2: [1106:3104] type 00 class 0x0c0320
    [ 0.100456] pci 0000:02:09.2: reg 10: [mem 0xfdffe000-0xfdffe0ff]
    [ 0.100499] pci 0000:02:09.2: supports D1 D2
    [ 0.100501] pci 0000:02:09.2: PME# supported from D0 D1 D2 D3hot D3cold
    [ 0.100527] pci 0000:00:0e.0: PCI bridge to [bus 02-02]
    [ 0.100531] pci 0000:00:0e.0: bridge window [io 0x9000-0x9fff]
    [ 0.100534] pci 0000:00:0e.0: bridge window [mem 0xfdf00000-0xfdffffff]
    [ 0.100537] pci 0000:00:0e.0: bridge window [mem 0xfde00000-0xfdefffff pref]
    [ 0.100546] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    [ 0.100629] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
    [ 0.100813] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGPB._PRT]
    [ 0.100901] pci0000:00: Unable to request _OSC control (_OSC support mask: 0x1e)
    [ 0.125942] ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 *10 11 12 14 15)
    [ 0.125994] ACPI: PCI Interrupt Link [LNK2] (IRQs 3 4 5 6 7 10 *11 12 14 15)
    [ 0.126043] ACPI: PCI Interrupt Link [LNK3] (IRQs 3 4 *5 6 7 10 11 12 14 15)
    [ 0.126092] ACPI: PCI Interrupt Link [LNK4] (IRQs 3 4 5 6 7 *10 11 12 14 15)
    [ 0.126140] ACPI: PCI Interrupt Link [LNK5] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
    [ 0.126195] ACPI: PCI Interrupt Link [LUBA] (IRQs 3 4 5 6 7 *10 11 12 14 15)
    [ 0.126245] ACPI: PCI Interrupt Link [LUBB] (IRQs 3 4 5 6 7 10 *11 12 14 15)
    [ 0.126293] ACPI: PCI Interrupt Link [LMAC] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
    [ 0.126341] ACPI: PCI Interrupt Link [LAPU] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
    [ 0.126391] ACPI: PCI Interrupt Link [LACI] (IRQs 3 4 *5 6 7 10 11 12 14 15)
    [ 0.126440] ACPI: PCI Interrupt Link [LMCI] (IRQs 3 4 5 6 7 10 *11 12 14 15)
    [ 0.126489] ACPI: PCI Interrupt Link [LSMB] (IRQs 3 4 *5 6 7 10 11 12 14 15)
    [ 0.126538] ACPI: PCI Interrupt Link [LUB2] (IRQs 3 4 *5 6 7 10 11 12 14 15)
    [ 0.126591] ACPI: PCI Interrupt Link [LFIR] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
    [ 0.126640] ACPI: PCI Interrupt Link [L3CM] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
    [ 0.126697] ACPI: PCI Interrupt Link [LIDE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
    [ 0.126753] ACPI: PCI Interrupt Link [LSID] (IRQs 3 4 5 6 7 *10 11 12 14 15)
    [ 0.126812] ACPI: PCI Interrupt Link [LFID] (IRQs 3 4 5 6 7 10 *11 12 14 15)
    [ 0.126889] ACPI: PCI Interrupt Link [APC1] (IRQs 16) *0
    [ 0.126950] ACPI: PCI Interrupt Link [APC2] (IRQs 17) *0
    [ 0.127010] ACPI: PCI Interrupt Link [APC3] (IRQs 18) *0
    [ 0.127070] ACPI: PCI Interrupt Link [APC4] (IRQs 19) *0
    [ 0.127110] ACPI: PCI Interrupt Link [APC5] (IRQs *16), disabled.
    [ 0.127183] ACPI: PCI Interrupt Link [APCF] (IRQs 20 21 22 23) *0
    [ 0.127250] ACPI: PCI Interrupt Link [APCG] (IRQs 20 21 22 23) *0
    [ 0.127316] ACPI: PCI Interrupt Link [APCH] (IRQs 20 21 22 23) *0, disabled.
    [ 0.127382] ACPI: PCI Interrupt Link [APCI] (IRQs 20 21 22 23) *0, disabled.
    [ 0.127449] ACPI: PCI Interrupt Link [APCJ] (IRQs 20 21 22 23) *0
    [ 0.127515] ACPI: PCI Interrupt Link [APCK] (IRQs 20 21 22 23) *0
    [ 0.127581] ACPI: PCI Interrupt Link [APCS] (IRQs 20 21 22 23) *0
    [ 0.127647] ACPI: PCI Interrupt Link [APCL] (IRQs 20 21 22 23) *0
    [ 0.127713] ACPI: PCI Interrupt Link [APCM] (IRQs 20 21 22 23) *0, disabled.
    [ 0.127780] ACPI: PCI Interrupt Link [AP3C] (IRQs 20 21 22 23) *0, disabled.
    [ 0.127847] ACPI: PCI Interrupt Link [APCZ] (IRQs 20 21 22 23) *0, disabled.
    [ 0.127919] ACPI: PCI Interrupt Link [APSI] (IRQs 20 21 22 23) *0
    [ 0.127991] ACPI: PCI Interrupt Link [APSJ] (IRQs 20 21 22 23) *0
    [ 0.128144] vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
    [ 0.128148] vgaarb: loaded
    [ 0.128149] vgaarb: bridge control possible 0000:01:00.0
    [ 0.128204] PCI: Using ACPI for IRQ routing
    [ 0.128208] PCI: pci_cache_line_size set to 64 bytes
    [ 0.128221] pci 0000:00:00.0: address space collision: [mem 0xe0000000-0xefffffff pref] conflicts with GART [mem 0xe0000000-0xefffffff]
    [ 0.128280] e820: reserve RAM buffer [mem 0x0009c000-0x0009ffff]
    [ 0.128283] e820: reserve RAM buffer [mem 0x5fff0000-0x5fffffff]
    [ 0.128429] NetLabel: Initializing
    [ 0.128430] NetLabel: domain hash size = 128
    [ 0.128432] NetLabel: protocols = UNLABELED CIPSOv4
    [ 0.128453] NetLabel: unlabeled traffic allowed by default
    [ 0.139353] pnp: PnP ACPI init
    [ 0.139383] ACPI: bus type pnp registered
    [ 0.139432] pnp 00:00: [io 0x4000-0x407f]
    [ 0.139434] pnp 00:00: [io 0x4080-0x40ff]
    [ 0.139437] pnp 00:00: [io 0x4400-0x447f]
    [ 0.139439] pnp 00:00: [io 0x4480-0x44ff]
    [ 0.139441] pnp 00:00: [io 0x4800-0x487f]
    [ 0.139444] pnp 00:00: [io 0x4880-0x48ff]
    [ 0.139550] system 00:00: [io 0x4000-0x407f] has been reserved
    [ 0.139554] system 00:00: [io 0x4080-0x40ff] has been reserved
    [ 0.139557] system 00:00: [io 0x4400-0x447f] has been reserved
    [ 0.139560] system 00:00: [io 0x4480-0x44ff] has been reserved
    [ 0.139563] system 00:00: [io 0x4800-0x487f] has been reserved
    [ 0.139566] system 00:00: [io 0x4880-0x48ff] has been reserved
    [ 0.139572] system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
    [ 0.139776] pnp 00:01: [mem 0x0009e000-0x000a1fff]
    [ 0.139779] pnp 00:01: [mem 0x000cec00-0x000cffff]
    [ 0.139781] pnp 00:01: [mem 0x000f0000-0x000fbfff]
    [ 0.139784] pnp 00:01: [mem 0x000fc000-0x000fffff]
    [ 0.139786] pnp 00:01: [mem 0x5fff0000-0x5fffffff]
    [ 0.139789] pnp 00:01: [mem 0xffff0000-0xffffffff]
    [ 0.139792] pnp 00:01: [mem 0x00000000-0x0009ffff]
    [ 0.139794] pnp 00:01: [mem 0x00100000-0x5ffeffff]
    [ 0.139797] pnp 00:01: [mem 0xfec00000-0xfec00fff]
    [ 0.139799] pnp 00:01: [mem 0xfee00000-0xfeefffff]
    [ 0.139802] pnp 00:01: [mem 0xfefff000-0xfeffffff]
    [ 0.139804] pnp 00:01: [mem 0xfff80000-0xfff80fff]
    [ 0.139807] pnp 00:01: [mem 0xfff90000-0xfffbffff]
    [ 0.139809] pnp 00:01: [mem 0xfffed000-0xfffeffff]
    [ 0.139815] pnp 00:01: disabling [mem 0x0009e000-0x000a1fff] because it overlaps 0000:00:00.0 BAR 0 [mem 0x00000000-0x0fffffff pref]
    [ 0.139819] pnp 00:01: disabling [mem 0x000cec00-0x000cffff] because it overlaps 0000:00:00.0 BAR 0 [mem 0x00000000-0x0fffffff pref]
    [ 0.139823] pnp 00:01: disabling [mem 0x000f0000-0x000fbfff] because it overlaps 0000:00:00.0 BAR 0 [mem 0x00000000-0x0fffffff pref]
    [ 0.139827] pnp 00:01: disabling [mem 0x000fc000-0x000fffff] because it overlaps 0000:00:00.0 BAR 0 [mem 0x00000000-0x0fffffff pref]
    [ 0.139830] pnp 00:01: disabling [mem 0x00000000-0x0009ffff] because it overlaps 0000:00:00.0 BAR 0 [mem 0x00000000-0x0fffffff pref]
    [ 0.139834] pnp 00:01: disabling [mem 0x00100000-0x5ffeffff] because it overlaps 0000:00:00.0 BAR 0 [mem 0x00000000-0x0fffffff pref]
    [ 0.139885] system 00:01: [mem 0x5fff0000-0x5fffffff] could not be reserved
    [ 0.139889] system 00:01: [mem 0xffff0000-0xffffffff] has been reserved
    [ 0.139892] system 00:01: [mem 0xfec00000-0xfec00fff] could not be reserved
    [ 0.139895] system 00:01: [mem 0xfee00000-0xfeefffff] has been reserved
    [ 0.139898] system 00:01: [mem 0xfefff000-0xfeffffff] has been reserved
    [ 0.139902] system 00:01: [mem 0xfff80000-0xfff80fff] has been reserved
    [ 0.139905] system 00:01: [mem 0xfff90000-0xfffbffff] has been reserved
    [ 0.139908] system 00:01: [mem 0xfffed000-0xfffeffff] has been reserved
    [ 0.139912] system 00:01: Plug and Play ACPI device, IDs PNP0c01 (active)
    [ 0.139976] pnp 00:02: [bus 00-ff]
    [ 0.140003] pnp 00:02: [io 0x0cf8-0x0cff]
    [ 0.140006] pnp 00:02: [io 0x0cf0-0x0cf3]
    [ 0.140009] pnp 00:02: [io 0x0000-0x0cf7 window]
    [ 0.140011] pnp 00:02: [io 0x0d00-0xffff window]
    [ 0.140014] pnp 00:02: [mem 0x000a0000-0x000bffff window]
    [ 0.140017] pnp 00:02: [mem 0x000c0000-0x000dffff window]
    [ 0.140020] pnp 00:02: [mem 0x60000000-0xfebfffff window]
    [ 0.140101] pnp 00:02: Plug and Play ACPI device, IDs PNP0a03 (active)
    [ 0.140629] pnp 00:03: [io 0x0010-0x001f]
    [ 0.140631] pnp 00:03: [io 0x0022-0x003f]
    [ 0.140634] pnp 00:03: [io 0x0044-0x005f]
    [ 0.140636] pnp 00:03: [io 0x0062-0x0063]
    [ 0.140639] pnp 00:03: [io 0x0065-0x006f]
    [ 0.140641] pnp 00:03: [io 0x0074-0x007f]
    [ 0.140644] pnp 00:03: [io 0x0091-0x0093]
    [ 0.140646] pnp 00:03: [io 0x00a2-0x00bf]
    [ 0.140648] pnp 00:03: [io 0x00e0-0x00ef]
    [ 0.140651] pnp 00:03: [io 0x0b78-0x0b7b]
    [ 0.140653] pnp 00:03: [io 0x0f78-0x0f7b]
    [ 0.140656] pnp 00:03: [io 0x0a78-0x0a7b]
    [ 0.140658] pnp 00:03: [io 0x0e78-0x0e7b]
    [ 0.140660] pnp 00:03: [io 0x0bbc-0x0bbf]
    [ 0.140663] pnp 00:03: [io 0x0fbc-0x0fbf]
    [ 0.140665] pnp 00:03: [io 0x04d0-0x04d1]
    [ 0.140741] system 00:03: [io 0x0b78-0x0b7b] has been reserved
    [ 0.140744] system 00:03: [io 0x0f78-0x0f7b] has been reserved
    [ 0.140748] system 00:03: [io 0x0a78-0x0a7b] has been reserved
    [ 0.140751] system 00:03: [io 0x0e78-0x0e7b] has been reserved
    [ 0.140754] system 00:03: [io 0x0bbc-0x0bbf] has been reserved
    [ 0.140757] system 00:03: [io 0x0fbc-0x0fbf] has been reserved
    [ 0.140760] system 00:03: [io 0x04d0-0x04d1] has been reserved
    [ 0.140763] system 00:03: Plug and Play ACPI device, IDs PNP0c02 (active)
    [ 0.140777] pnp 00:04: [dma 4]
    [ 0.140780] pnp 00:04: [io 0x0000-0x000f]
    [ 0.140782] pnp 00:04: [io 0x0080-0x0090]
    [ 0.140785] pnp 00:04: [io 0x0094-0x009f]
    [ 0.140787] pnp 00:04: [io 0x00c0-0x00df]
    [ 0.140832] pnp 00:04: Plug and Play ACPI device, IDs PNP0200 (active)
    [ 0.140844] pnp 00:05: [io 0x0070-0x0073]
    [ 0.140862] pnp 00:05: [irq 8]
    [ 0.140904] pnp 00:05: Plug and Play ACPI device, IDs PNP0b00 (active)
    [ 0.140914] pnp 00:06: [io 0x0061]
    [ 0.140959] pnp 00:06: Plug and Play ACPI device, IDs PNP0800 (active)
    [ 0.140969] pnp 00:07: [io 0x00f0-0x00ff]
    [ 0.140976] pnp 00:07: [irq 13]
    [ 0.141019] pnp 00:07: Plug and Play ACPI device, IDs PNP0c04 (active)
    [ 0.141243] pnp 00:08: [io 0x03f8-0x03ff]
    [ 0.141251] pnp 00:08: [irq 4]
    [ 0.141340] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
    [ 0.141514] pnp 00:09: [io 0x02f8-0x02ff]
    [ 0.141522] pnp 00:09: [irq 3]
    [ 0.141596] pnp 00:09: Plug and Play ACPI device, IDs PNP0501 (active)
    [ 0.141881] pnp 00:0a: [io 0x0378-0x037f]
    [ 0.141883] pnp 00:0a: [io 0x0778-0x077b]
    [ 0.141890] pnp 00:0a: [irq 7]
    [ 0.141960] pnp 00:0a: Plug and Play ACPI device, IDs PNP0400 (active)
    [ 0.142046] pnp 00:0b: [io 0x0060]
    [ 0.142049] pnp 00:0b: [io 0x0064]
    [ 0.142055] pnp 00:0b: [irq 1]
    [ 0.142106] pnp 00:0b: Plug and Play ACPI device, IDs PNP0303 PNP030b (active)
    [ 0.142129] pnp: PnP ACPI: found 12 devices
    [ 0.142131] ACPI: ACPI bus type pnp unregistered
    [ 0.148689] Switching to clocksource acpi_pm
    [ 0.148760] pci 0000:01:00.0: BAR 6: assigned [mem 0xfc000000-0xfc01ffff pref]
    [ 0.148765] pci 0000:00:0b.0: PCI bridge to [bus 01-01]
    [ 0.148769] pci 0000:00:0b.0: bridge window [io 0xa000-0xafff]
    [ 0.148774] pci 0000:00:0b.0: bridge window [mem 0xfa000000-0xfcffffff]
    [ 0.148778] pci 0000:00:0b.0: bridge window [mem 0xd0000000-0xdfffffff pref]
    [ 0.148787] pci 0000:02:08.0: BAR 6: assigned [mem 0xfde00000-0xfde0ffff pref]
    [ 0.148790] pci 0000:00:0e.0: PCI bridge to [bus 02-02]
    [ 0.148793] pci 0000:00:0e.0: bridge window [io 0x9000-0x9fff]
    [ 0.148796] pci 0000:00:0e.0: bridge window [mem 0xfdf00000-0xfdffffff]
    [ 0.148799] pci 0000:00:0e.0: bridge window [mem 0xfde00000-0xfdefffff pref]
    [ 0.148814] pci 0000:00:0e.0: setting latency timer to 64
    [ 0.148818] pci_bus 0000:00: resource 4 [io 0x0000-0xffff]
    [ 0.148821] pci_bus 0000:00: resource 5 [mem 0x000a0000-0x000bffff]
    [ 0.148824] pci_bus 0000:00: resource 6 [mem 0x60000000-0xfcffffffff]
    [ 0.148827] pci_bus 0000:01: resource 0 [io 0xa000-0xafff]
    [ 0.148829] pci_bus 0000:01: resource 1 [mem 0xfa000000-0xfcffffff]
    [ 0.148832] pci_bus 0000:01: resource 2 [mem 0xd0000000-0xdfffffff pref]
    [ 0.148835] pci_bus 0000:02: resource 0 [io 0x9000-0x9fff]
    [ 0.148837] pci_bus 0000:02: resource 1 [mem 0xfdf00000-0xfdffffff]
    [ 0.148840] pci_bus 0000:02: resource 2 [mem 0xfde00000-0xfdefffff pref]
    [ 0.148906] NET: Registered protocol family 2
    [ 0.149029] IP route cache hash table entries: 65536 (order: 7, 524288 bytes)
    [ 0.149029] TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
    [ 0.153406] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
    [ 0.154706] TCP: Hash tables configured (established 262144 bind 65536)
    [ 0.154710] TCP: reno registered
    [ 0.154724] UDP hash table entries: 1024 (order: 3, 32768 bytes)
    [ 0.154769] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes)
    [ 0.154934] NET: Registered protocol family 1
    [ 0.155185] ACPI: PCI Interrupt Link [APCF] enabled at IRQ 23
    [ 0.223475] ACPI: PCI Interrupt Link [APCG] enabled at IRQ 22
    [ 0.290128] ACPI: PCI Interrupt Link [APCL] enabled at IRQ 21
    [ 0.290189] pci 0000:01:00.0: Boot video device
    [ 0.290265] ACPI: PCI Interrupt Link [APC4] enabled at IRQ 19
    [ 0.290348] ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
    [ 0.290425] ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17
    [ 0.290445] PCI: CLS 32 bytes, default 64
    [ 0.290526] Unpacking initramfs...
    [ 0.372340] Freeing initrd memory: 2940k freed
    [ 0.379476] agpgart-amd64 0000:00:00.0: AGP bridge [10de/00e1]
    [ 0.379485] agpgart-amd64 0000:00:00.0: aperture size 4096 MB is not right, using settings from NB
    [ 0.379493] agpgart-amd64 0000:00:00.0: setting up Nforce3 AGP
    [ 0.388295] agpgart-amd64 0000:00:00.0: AGP aperture is 256M @ 0xe0000000
    [ 0.388742] audit: initializing netlink socket (disabled)
    [ 0.388762] type=2000 audit(1346927638.386:1): initialized
    [ 0.402840] HugeTLB registered 2 MB page size, pre-allocated 0 pages
    [ 0.405016] VFS: Disk quotas dquot_6.5.2
    [ 0.405085] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
    [ 0.405228] msgmni has been set to 2998
    [ 0.405471] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
    [ 0.405502] io scheduler noop registered
    [ 0.405504] io scheduler deadline registered
    [ 0.405574] io scheduler cfq registered (default)
    [ 0.412567] vesafb: mode is 1280x1024x32, linelength=5120, pages=0
    [ 0.412569] vesafb: scrolling: redraw
    [ 0.412572] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
    [ 0.412814] vesafb: framebuffer at 0xd0000000, mapped to 0xffffc90000900000, using 5120k, total 5120k
    [ 0.475467] Console: switching to colour frame buffer device 160x64
    [ 0.537946] fb0: VESA VGA frame buffer device
    [ 0.538002] GHES: HEST is not enabled!
    [ 0.538068] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    [ 0.558511] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
    [ 0.578950] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
    [ 0.599584] 00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
    [ 0.620075] 00:09: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
    [ 0.620233] Linux agpgart interface v0.103
    [ 0.620290] i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
    [ 0.620292] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
    [ 0.620995] serio: i8042 KBD port at 0x60,0x64 irq 1
    [ 0.621096] mousedev: PS/2 mouse device common for all mice
    [ 0.621204] rtc_cmos 00:05: RTC can wake from S4
    [ 0.621333] rtc_cmos 00:05: rtc core: registered rtc_cmos as rtc0
    [ 0.621357] rtc0: alarms up to one year, y3k, 242 bytes nvram
    [ 0.621367] cpuidle: using governor ladder
    [ 0.621370] cpuidle: using governor menu
    [ 0.621586] drop_monitor: Initializing network drop monitor service
    [ 0.621691] TCP: cubic registered
    [ 0.621838] NET: Registered protocol family 10
    [ 0.622084] NET: Registered protocol family 17
    [ 0.622099] Key type dns_resolver registered
    [ 0.622262] PM: Hibernation image not present or could not be loaded.
    [ 0.622282] registered taskstats version 1
    [ 0.622840] rtc_cmos 00:05: setting system clock to 2012-09-06 10:33:58 UTC (1346927638)
    [ 0.624542] Freeing unused kernel memory: 756k freed
    [ 0.625249] Write protecting the kernel read-only data: 8192k
    [ 0.631386] Freeing unused kernel memory: 1496k freed
    [ 0.635859] Freeing unused kernel memory: 616k freed
    [ 0.647736] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
    [ 0.654805] systemd-udevd[38]: starting version 189
    [ 0.730408] ACPI: bus type usb registered
    [ 0.730453] usbcore: registered new interface driver usbfs
    [ 0.730468] usbcore: registered new interface driver hub
    [ 0.735252] usbcore: registered new device driver usb
    [ 0.735879] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    [ 0.739107] SCSI subsystem initialized
    [ 0.746050] ehci_hcd 0000:00:02.2: setting latency timer to 64
    [ 0.746058] ehci_hcd 0000:00:02.2: EHCI Host Controller
    [ 0.746075] ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 1
    [ 0.746108] ehci_hcd 0000:00:02.2: debug port 1
    [ 0.746114] ehci_hcd 0000:00:02.2: cache line size of 32 is not supported
    [ 0.746141] ehci_hcd 0000:00:02.2: irq 21, io mem 0xfe02d000
    [ 0.749031] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
    [ 0.750857] uhci_hcd: USB Universal Host Controller Interface driver
    [ 0.753402] ehci_hcd 0000:00:02.2: USB 2.0 started, EHCI 1.00
    [ 0.753609] hub 1-0:1.0: USB hub found
    [ 0.753616] hub 1-0:1.0: 8 ports detected
    [ 0.753784] uhci_hcd 0000:02:09.0: UHCI Host Controller
    [ 0.753793] uhci_hcd 0000:02:09.0: new USB bus registered, assigned bus number 2
    [ 0.753839] uhci_hcd 0000:02:09.0: irq 19, io base 0x00009800
    [ 0.753984] hub 2-0:1.0: USB hub found
    [ 0.753989] hub 2-0:1.0: 2 ports detected
    [ 0.754706] libata version 3.00 loaded.
    [ 0.756811] ohci_hcd 0000:00:02.0: setting latency timer to 64
    [ 0.756817] ohci_hcd 0000:00:02.0: OHCI Host Controller
    [ 0.756829] ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 3
    [ 0.756869] ohci_hcd 0000:00:02.0: irq 23, io mem 0xfe02f000
    [ 0.757452] uhci_hcd 0000:02:09.1: UHCI Host Controller
    [ 0.757461] uhci_hcd 0000:02:09.1: new USB bus registered, assigned bus number 4
    [ 0.757493] uhci_hcd 0000:02:09.1: irq 16, io base 0x00009400
    [ 0.757704] hub 4-0:1.0: USB hub found
    [ 0.757711] hub 4-0:1.0: 2 ports detected
    [ 0.761428] ehci_hcd 0000:02:09.2: EHCI Host Controller
    [ 0.761447] ehci_hcd 0000:02:09.2: new USB bus registered, assigned bus number 5
    [ 0.761512] ehci_hcd 0000:02:09.2: irq 17, io mem 0xfdffe000
    [ 0.770064] ehci_hcd 0000:02:09.2: USB 2.0 started, EHCI 1.00
    [ 0.770287] hub 5-0:1.0: USB hub found
    [ 0.770294] hub 5-0:1.0: 4 ports detected
    [ 0.812239] hub 3-0:1.0: USB hub found
    [ 0.812251] hub 3-0:1.0: 4 ports detected
    [ 0.816572] ohci_hcd 0000:00:02.1: setting latency timer to 64
    [ 0.816577] ohci_hcd 0000:00:02.1: OHCI Host Controller
    [ 0.816589] ohci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 6
    [ 0.816630] ohci_hcd 0000:00:02.1: irq 22, io mem 0xfe02e000
    [ 0.868954] hub 6-0:1.0: USB hub found
    [ 0.868962] hub 6-0:1.0: 4 ports detected
    [ 0.873501] sata_nv 0000:00:09.0: version 3.5
    [ 0.873756] ACPI: PCI Interrupt Link [APSI] enabled at IRQ 20
    [ 0.873833] sata_nv 0000:00:09.0: setting latency timer to 64
    [ 0.874345] scsi0 : sata_nv
    [ 0.874497] scsi1 : sata_nv
    [ 0.874645] ata1: SATA max UDMA/133 cmd 0x9e0 ctl 0xbe0 bmdma 0xcc00 irq 20
    [ 0.874648] ata2: SATA max UDMA/133 cmd 0x960 ctl 0xb60 bmdma 0xcc08 irq 20
    [ 0.878342] ACPI: PCI Interrupt Link [APSJ] enabled at IRQ 23
    [ 0.878391] sata_nv 0000:00:0a.0: setting latency timer to 64
    [ 0.878840] scsi2 : sata_nv
    [ 0.878963] scsi3 : sata_nv
    [ 0.879110] ata3: SATA max UDMA/133 cmd 0x9f0 ctl 0xbf0 bmdma 0xb400 irq 23
    [ 0.879112] ata4: SATA max UDMA/133 cmd 0x970 ctl 0xb70 bmdma 0xb408 irq 23
    [ 0.886479] pata_acpi 0000:00:08.0: power state changed by ACPI to D0
    [ 0.886484] pata_acpi 0000:00:08.0: power state changed by ACPI to D0
    [ 0.886533] pata_acpi 0000:00:08.0: setting latency timer to 64
    [ 1.186695] ata1: SATA link down (SStatus 0 SControl 300)
    [ 1.343364] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    [ 1.350214] ata3.00: ATA-7: SAMSUNG SP1614C, SW100-34, max UDMA7
    [ 1.350217] ata3.00: 312581808 sectors, multi 16: LBA48
    [ 1.356871] ata3.00: configured for UDMA/133
    [ 1.370024] usb 4-1: new low-speed USB device number 2 using uhci_hcd
    [ 1.500024] ata2: SATA link down (SStatus 0 SControl 300)
    [ 1.500200] scsi 2:0:0:0: Direct-Access ATA SAMSUNG SP1614C SW10 PQ: 0 ANSI: 5
    [ 1.966704] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    [ 2.020180] ata4.00: ATA-8: WDC WD15EARS-00Z5B1, 80.00A80, max UDMA/133
    [ 2.020183] ata4.00: 2930277168 sectors, multi 16: LBA48 NCQ (depth 0/32)
    [ 2.033588] ata4.00: configured for UDMA/133
    [ 2.033760] scsi 3:0:0:0: Direct-Access ATA WDC WD15EARS-00Z 80.0 PQ: 0 ANSI: 5
    [ 2.036921] pata_amd 0000:00:08.0: version 0.4.1
    [ 2.036948] pata_amd 0000:00:08.0: power state changed by ACPI to D0
    [ 2.036952] pata_amd 0000:00:08.0: power state changed by ACPI to D0
    [ 2.037017] pata_amd 0000:00:08.0: setting latency timer to 64
    [ 2.040074] scsi4 : pata_amd
    [ 2.041581] sd 2:0:0:0: [sda] 312581808 512-byte logical blocks: (160 GB/149 GiB)
    [ 2.041663] sd 2:0:0:0: [sda] Write Protect is off
    [ 2.041667] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
    [ 2.041692] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [ 2.042020] scsi5 : pata_amd
    [ 2.042592] ata5: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xe000 irq 14
    [ 2.042595] ata6: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xe008 irq 15
    [ 2.042887] sd 3:0:0:0: [sdb] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
    [ 2.042937] sd 3:0:0:0: [sdb] Write Protect is off
    [ 2.042941] sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
    [ 2.042964] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [ 2.055764] sdb: sdb1
    [ 2.056082] sd 3:0:0:0: [sdb] Attached SCSI disk
    [ 2.056117] usbcore: registered new interface driver usbhid
    [ 2.056119] usbhid: USB HID core driver
    [ 2.073368] sda: sda1 sda2 sda3 sda4
    [ 2.073827] sd 2:0:0:0: [sda] Attached SCSI disk
    [ 2.200466] ata5.00: ATA-6: ST340810A, 3.39, max UDMA/100
    [ 2.200473] ata5.00: 78165360 sectors, multi 16: LBA
    [ 2.200484] ata5: nv_mode_filter: 0x3f39f&0x739f->0x739f, BIOS=0x7000 (0xc000c000) ACPI=0x701f (60:120:0x1b)
    [ 2.213741] ata5.00: configured for UDMA/33
    [ 2.213893] scsi 4:0:0:0: Direct-Access ATA ST340810A 3.39 PQ: 0 ANSI: 5
    [ 2.214133] sd 4:0:0:0: [sdc] 78165360 512-byte logical blocks: (40.0 GB/37.2 GiB)
    [ 2.214189] sd 4:0:0:0: [sdc] Write Protect is off
    [ 2.214193] sd 4:0:0:0: [sdc] Mode Sense: 00 3a 00 00
    [ 2.214216] sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [ 2.244630] sdc: sdc1
    [ 2.244919] sd 4:0:0:0: [sdc] Attached SCSI disk
    [ 2.373623] ata6.00: ATAPI: _NEC DVD_RW ND-3540A, 1.01, max UDMA/33
    [ 2.373634] ata6: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc000c000) ACPI=0x701f (60:120:0x1b)
    [ 2.386892] ata6.00: configured for UDMA/33
    [ 2.388189] scsi 5:0:0:0: CD-ROM _NEC DVD_RW ND-3540A 1.01 PQ: 0 ANSI: 5
    [ 2.391609] input: OM as /devices/pci0000:00/0000:00:0e.0/0000:02:09.1/usb4/4-1/4-1:1.0/input/input1
    [ 2.393267] hid-generic 0003:04F3:0234.0001: input,hidraw0: USB HID v1.11 Mouse [OM] on usb-0000:02:09.1-1/input0
    [ 2.397693] sr0: scsi3-mmc drive: 48x/48x writer cd/rw xa/form2 cdda tray
    [ 2.397702] cdrom: Uniform CD-ROM driver Revision: 3.20
    [ 2.397986] sr 5:0:0:0: Attached scsi CD-ROM sr0
    [ 3.150376] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
    [ 3.949356] systemd[1]: Successfully opened /dev/kmsg for logging.
    [ 3.949760] systemd[1]: Mounting cgroup to /sys/fs/cgroup/cpuset of type cgroup with options cpuset.
    [ 3.949905] systemd[1]: Mounting cgroup to /sys/fs/cgroup/cpu,cpuacct of type cgroup with options cpu,cpuacct.
    [ 3.950054] systemd[1]: Mounting cgroup to /sys/fs/cgroup/memory of type cgroup with options memory.
    [ 3.950167] systemd[1]: Mounting cgroup to /sys/fs/cgroup/devices of type cgroup with options devices.
    [ 3.953404] systemd[1]: Mounting cgroup to /sys/fs/cgroup/freezer of type cgroup with options freezer.
    [ 3.953500] systemd[1]: Mounting cgroup to /sys/fs/cgroup/net_cls of type cgroup with options net_cls.
    [ 3.953597] systemd[1]: Mounting cgroup to /sys/fs/cgroup/blkio of type cgroup with options blkio.
    [ 3.956761] systemd[1]: systemd 189 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ; arch)
    [ 3.979310] systemd[1]: Your kernel apparently lacks built-in autofs4 support. Might be a good idea to compile it in. We'll now try to work around this by loading the module...
    [ 4.144298] systemd[1]: Inserted module 'autofs4'
    [ 4.152053] systemd[1]: Set hostname to <box>.
    [ 4.157882] systemd[1]: Using cgroup controller name=systemd. File system hierarchy is at /sys/fs/cgroup/systemd/system.
    [ 4.157991] systemd[1]: Installed release agent.
    [ 4.158142] systemd[1]: Created root group.
    [ 4.158219] systemd[1]: Using notification socket @/org/freedesktop/systemd1/notify
    [ 4.158401] systemd[1]: Successfully created private D-Bus server.
    [ 4.184882] systemd[1]: Spawned /usr/lib/systemd/system-generators/systemd-cryptsetup-generator as 114
    [ 4.185117] systemd[1]: Spawned /usr/lib/systemd/system-generators/systemd-system-update-generator as 115
    [ 4.185365] systemd[1]: Spawned /usr/lib/systemd/system-generators/systemd-getty-generator as 116
    [ 4.185641] systemd[1]: Spawned /usr/lib/systemd/system-generators/systemd-fstab-generator as 117
    [ 4.255375] systemd[1]: /usr/lib/systemd/system-generators/systemd-cryptsetup-generator exited successfully.
    [ 4.255400] systemd[1]: /usr/lib/systemd/system-generators/systemd-system-update-generator exited successfully.
    [ 4.255408] systemd[1]: /usr/lib/systemd/system-generators/systemd-getty-generator exited successfully.
    [ 4.255416] systemd[1]: /usr/lib/systemd/system-generators/systemd-fstab-generator exited successfully.
    [ 4.313459] systemd[1]: Looking for unit files in:
    [ 4.313463] systemd[1]: /etc/systemd/system
    [ 4.313465] systemd[1]: /run/systemd/generator
    [ 4.313468] systemd[1]: /usr/lib/systemd/system
    [ 4.313471] systemd[1]: Disabled SysV init scripts and rcN.d links support
    [ 4.422041] systemd[1]: Failed to load configuration for syslog.service: No such file or directory
    [ 4.495651] systemd[1]: Failed to load configuration for plymouth-start.service: No such file or directory
    [ 4.564783] systemd[1]: Failed to load configuration for rc-local.service: No such file or directory
    [ 4.564799] systemd[1]: Failed to load configuration for plymouth-quit-wait.service: No such file or directory
    [ 4.709247] systemd[1]: Failed to load configuration for auditd.service: No such file or directory
    [ 4.752803] systemd[1]: -.mount changed dead -> mounted
    [ 4.752894] systemd[1]: Activating default unit: default.target
    [ 4.752901] systemd[1]: Trying to enqueue job graphical.target/start/replace
    [ 4.753079] systemd[1]: Installed new job graphical.target/start as 1
    [ 4.753085] systemd[1]: Installed new job multi-user.target/start as 2
    [ 4.753089] systemd[1]: Installed new job basic.target/start as 3
    [ 4.753094] systemd[1]: Installed new job sysinit.target/start as 4
    [ 4.753098] systemd[1]: Installed new job local-fs.target/start as 5
    [ 4.753102] systemd[1]: Installed new job home-hasardeur-Ext.mount/start as 6
    [ 4.753108] systemd[1]: Installed new job systemd-journald.socket/start as 7
    [ 4.753112] systemd[1]: Installed new job systemd-fsck@dev-disk-by\x2duuid-1A54880F5487EBB7.service/start as 9
    [ 4.753116] systemd[1]: Installed new job dev-disk-by\x2duuid-1A54880F5487EBB7.device/start as 10
    [ 4.753138] systemd[1]: Installed new job local-fs-pre.target/start as 11
    [ 4.753142] systemd[1]: Installed new job home-hasardeur-Space.mount/start as 14
    [ 4.753147] systemd[1]: Installed new job systemd-fsck@dev-disk-by\x2duuid-72290182\x2d7429\x2d4fb3\x2da421\x2d1e3bdf21dda9.service/start as 15
    [ 4.753151] systemd[1]: Installed new job dev-disk-by\x2duuid-72290182\x2d7429\x2d4fb3\x2da421\x2d1e3bdf21dda9.device/start as 16
    [ 4.753161] systemd[1]: Installed new job tmp.mount/start as 17
    [ 4.753164] systemd[1]: Installed new job systemd-fsck-root.service/start as 18
    [ 4.753168] systemd[1]: Installed new job systemd-remount-fs.service/start as 19
    [ 4.753172] systemd[1]: Installed new job swap.target/start as 20
    [ 4.753176] systemd[1]: Installed new job dev-disk-by\x2duuid-b5f8685d\x2d2706\x2d44fc\x2d882d\x2d662cc23e7c07.swap/start as 21
    [ 4.753181] systemd[1]: Installed new job dev-disk-by\x2duuid-b5f8685d\x2d2706\x2d44fc\x2d882d\x2d662cc23e7c07.device/start as 22
    [ 4.753191] systemd[1]: Installed new job systemd-udevd.service/start as 23
    [ 4.753195] systemd[1]: Installed new job systemd-udevd-control.socket/start as 24
    [ 4.753198] systemd[1]: Installed new job systemd-udevd-kernel.socket/start as 25
    [ 4.753202] systemd[1]: Installed new job dev-mqueue.mount/start as 26
    [ 4.753206] systemd[1]: Installed new job sys-kernel-config.mount/start as 27
    [ 4.753209] systemd[1]: Installed new job systemd-random-seed-load.service/start as 28
    [ 4.753213] systemd[1]: Installed new job systemd-ask-password-console.path/start as 29
    [ 4.753217] systemd[1]: Installed new job systemd-udev-trigger.service/start as 30
    [ 4.753220] systemd[1]: Installed new job sys-kernel-debug.mount/start as 31
    [ 4.753224] systemd[1]: Installed new job systemd-modules-load.service/start as 32
    [ 4.753228] systemd[1]: Installed new job sys-fs-fuse-connections.mount/start as 33
    [ 4.753231] systemd[1]: Installed new job proc-sys-fs-binfmt_misc.automount/start as 34
    [ 4.753235] systemd[1]: Installed new job systemd-journald.service/start as 35
    [ 4.753239] systemd[1]: Installed new job systemd-journal-flush.service/start as 36
    [ 4.753242] systemd[1]: Installed new job dev-hugepages.mount/start as 37
    [ 4.753246] systemd[1]: Installed new job systemd-tmpfiles-setup.service/start as 38
    [ 4.753249] systemd[1]: Installed new job cryptsetup.target/start as 39
    [ 4.753253] systemd[1]: Installed new job systemd-sysctl.service/start as 40
    [ 4.753256] systemd[1]: Installed new job systemd-vconsole-setup.service/start as 41
    [ 4.753260] systemd[1]: Installed new job systemd-binfmt.service/start as 42
    [ 4.753263] systemd[1]: Installed new job sockets.target/start as 45
    [ 4.753267] systemd[1]: Installed new job dbus.socket/start as 46
    [ 4.753271] systemd[1]: Installed new job systemd-initctl.socket/start as 47
    [ 4.753274] systemd[1]: Installed new job systemd-shutdownd.socket/start as 48
    [ 4.753278] systemd[1]: Installed new job alsa-restore.service/start as 49
    [ 4.753281] systemd[1]: Installed new job console-kit-log-system-start.service/start as 50
    [ 4.753285] systemd[1]: Installed new job systemd-tmpfiles-clean.timer/start as 51
    [ 4.753289] systemd[1]: Installed new job ntpd.service/start as 52
    [ 4.753292] systemd[1]: Installed new job remote-fs.target/start as 53
    [ 4.753296] systemd[1]: Installed new job netcfg.service/start as 54
    [ 4.753299] systemd[1]: Installed new job network.target/start as 55
    [ 4.753302] systemd[1]: Installed new job cronie.service/start as 56
    [ 4.753306] systemd[1]: Installed new job getty.target/start as 57
    [ 4.753309] systemd[1]: Installed new job [email protected]/start as 58
    [ 4.753313] systemd[1]: Installed new job systemd-ask-password-wall.path/start as 59
    [ 4.753316] systemd[1]: Installed new job dbus.service/start as 60
    [ 4.753320] systemd[1]: Installed new job systemd-logind.service/start as 61
    [ 4.753323] systemd[1]: Installed new job systemd-user-sessions.service/start as 62
    [ 4.753327] systemd[1]: Installed new job systemd-update-utmp-runlevel.service/start as 63
    [ 4.753331] systemd[1]: Installed new job lxdm.service/start as 66
    [ 4.753365] systemd[1]: Enqueued job graphical.target/start as 1
    [ 4.753380] systemd[1]: Loaded units and determined initial transaction in 594ms 940us.
    [ 4.753507] systemd[1]: Got SIGCHLD for process 113 (switch_root)
    [ 4.753580] systemd[1]: Child 113 died (code=exited, status=0/SUCCESS)
    [ 4.753667] systemd[1]: systemd-ask-password-wall.path changed dead -> waiting
    [ 4.753676] systemd[1]: Job systemd-ask-password-wall.path/start finished, result=done
    [ 4.753692] systemd[1]: remote-fs.target changed dead -> active
    [ 4.753700] systemd[1]: Job remote-fs.target/start finished, result=done
    [ 4.753747] systemd[1]: systemd-shutdownd.socket changed dead -> listening
    [ 4.753755] systemd[1]: Job systemd-shutdownd.socket/start finished, result=done
    [ 4.753786] systemd[1]: systemd-initctl.socket changed dead -> listening
    [ 4.753793] systemd[1]: Job systemd-initctl.socket/start finished, result=done
    [ 4.753807] systemd[1]: cryptsetup.target changed dead -> active
    [ 4.753815] systemd[1]: Job cryptsetup.target/start finished, result=done
    [ 4.753875] systemd[1]: Autofs kernel version 1.0
    [ 4.753969] systemd[1]: Autofs protocol version 5.2
    [ 4.753979] systemd[1]: proc-sys-fs-binfmt_misc.automount changed dead -> waiting
    [ 4.753987] systemd[1]: Job proc-sys-fs-binfmt_misc.automount/start finished, result=done
    [ 4.754036] systemd[1]: systemd-ask-password-console.path changed dead -> waiting
    [ 4.754044] systemd[1]: Job systemd-ask-password-console.path/start finished, result=done
    [ 4.754155] systemd[1]: systemd-udevd-kernel.socket changed dead -> listening
    [ 4.754164] systemd[1]: Job systemd-udevd-kernel.socket/start finished, result=done
    [ 4.754246] systemd[1]: systemd-udevd-control.socket changed dead -> listening
    [ 4.754254] systemd[1]: Job systemd-udevd-control.socket/start finished, result=done
    [ 4.754341] systemd[1]: systemd-journald.socket changed dead -> listening
    [ 4.754349] systemd[1]: Job systemd-journald.socket/start finished, result=done
    [ 4.754375] systemd[1]: Starting of systemd-fsck-root.service requested but condition failed. Ignoring.
    [ 4.754379] systemd[1]: Job systemd-fsck-root.service/start finished, result=done
    [ 4.754453] systemd[1]: About to execute: /usr/lib/systemd/systemd-remount-fs
    [ 4.758929] systemd[1]: Forked /usr/lib/systemd/systemd-remount-fs as 118
    [ 4.759050] systemd[1]: systemd-remount-fs.service changed dead -> start
    [ 4.759250] systemd[1]: About to execute: /usr/lib/systemd/systemd-udevd
    [ 4.826866] systemd[1]: Forked /usr/lib/systemd/systemd-udevd as 120
    [ 4.826993] systemd[1]: systemd-udevd.service changed dead -> start
    [ 4.827101] systemd[1]: About to execute: /bin/mount mqueue /dev/mqueue -t mqueue
    [ 4.828859] systemd[1]: Forked /bin/mount as 121
    [ 4.828923] systemd[1]: dev-mqueue.mount changed dead -> mounting
    [ 4.829234] systemd[1]: About to execute: /usr/bin/udevadm trigger --type=subsystems --action=add
    [ 4.833375] systemd[1]: Forked /usr/bin/udevadm as 122
    [ 4.833513] systemd[1]: systemd-udev-trigger.service changed dead -> start
    [ 4.833594] systemd[1]: About to execute: /bin/mount debugfs /sys/kernel/debug -t debugfs
    [ 4.834846] systemd[1]: Forked /bin/mount as 123
    [ 4.834893] systemd[1]: sys-kernel-debug.mount changed dead -> mounting
    [ 4.859660] systemd[1]: About to execute: /usr/lib/systemd/systemd-modules-load
    [ 4.860937] systemd[1]: Forked /usr/lib/systemd/systemd-modules-load as 124
    [ 4.861068] systemd[1]: systemd-modules-load.service changed dead -> start
    [ 4.861180] systemd[1]: About to execute: /bin/mount hugetlbfs /dev/hugepages -t hugetlbfs
    [ 4.863410] systemd[1]: Forked /bin/mount as 125
    [ 4.863451] systemd[1]: dev-hugepages.mount changed dead -> mounting
    [ 4.917003] systemd[1]: About to execute: /usr/lib/systemd/systemd-sysctl
    [ 4.918344] systemd[1]: Forked /usr/lib/systemd/systemd-sysctl as 126
    [ 4.918493] systemd[1]: systemd-sysctl.service changed dead -> start
    [ 4.918602] systemd[1]: About to execute: /usr/lib/systemd/systemd-vconsole-setup
    [ 4.920070] systemd[1]: Forked /usr/lib/systemd/systemd-vconsole-setup as 127
    [ 4.920224] systemd[1]: systemd-vconsole-setup.service changed dead -> start
    [ 4.926908] systemd[1]: Starting of systemd-binfmt.service requested but condition failed. Ignoring.
    [ 4.926918] systemd[1]: Job systemd-binfmt.service/start finished, result=done
    [ 4.927036] systemd[1]: About to execute: /usr/lib/systemd/systemd-journald
    [ 4.928214] systemd[1]: Forked /usr/lib/systemd/systemd-journald as 128
    [ 4.928417] systemd[1]: systemd-journald.service changed dead -> running
    [ 4.928436] systemd[1]: Job systemd-journald.service/start finished, result=done
    [ 4.928562] systemd[1]: Running GC...
    [ 4.929089] systemd[1]: Received SIGCHLD from PID 116 (n/a).
    [ 4.929352] systemd[1]: Incoming traffic on systemd-journald.socket
    [ 4.929370] systemd[1]: systemd-journald.socket changed listening -> running
    [ 4.957457] systemd[1]: Got notification message for unit systemd-udevd.service
    [ 4.957468] systemd[1]: systemd-udevd.service: Got message
    [ 4.957473] systemd[1]: systemd-udevd.service: got READY=1
    [ 4.957551] systemd[1]: systemd-udevd.service changed start -> running
    [ 4.957567] systemd[1]: Job systemd-udevd.service/start finished, result=done
    [ 4.957642] systemd-udevd[120]: starting version 189
    [ 5.064497] systemd[1]: Incoming traffic on systemd-udevd-kernel.socket
    [ 5.064520] systemd[1]: systemd-udevd-kernel.socket changed listening -> running
    [ 5.066198] systemd[1]: Received SIGCHLD from PID 122 (udevadm).
    [ 5.066234] systemd[1]: Got SIGCHLD for process 122 (udevadm)
    [ 5.066313] systemd[1]: Child 122 died (code=exited, status=0/SUCCESS)
    [ 5.066317] systemd[1]: Child 122 belongs to systemd-udev-trigger.service
    [ 5.066333] systemd[1]: systemd-udev-trigger.service: main process exited, code=exited, status=0
    [ 5.066341] systemd[1]: systemd-udev-trigger.service running next main command for state start
    [ 5.066359] systemd[1]: About to execute: /usr/bin/udevadm trigger --type=devices --action=add
    [ 5.067931] systemd[1]: Forked /usr/bin/udevadm as 130
    [ 5.083596] systemd[1]: Received SIGCHLD from PID 130 (udevadm).
    [ 5.083638] systemd[1]: Got SIGCHLD for process 130 (udevadm)
    [ 5.083717] systemd[1]: Child 130 died (code=exited, status=0/SUCCESS)
    [ 5.083721] systemd[1]: Child 130 belongs to systemd-udev-trigger.service
    [ 5.083737] systemd[1]: systemd-udev-trigger.service: main process exited, code=exited, status=0
    [ 5.084106] systemd[1]: systemd-udev-trigger.service changed start -> exited
    [ 5.084118] systemd[1]: Job systemd-udev-trigger.service/start finished, result=done
    [ 5.088748] systemd[1]: Received SIGCHLD from PID 126 (systemd-sysctl).
    [ 5.088779] systemd[1]: Got SIGCHLD for process 126 (systemd-sysctl)
    [ 5.088852] systemd[1]: Child 126 died (code=exited, status=0/SUCCESS)
    [ 5.088856] systemd[1]: Child 126 belongs to systemd-sysctl.service
    [ 5.088873] systemd[1]: systemd-sysctl.service: main process exited, code=exited, status=0
    [ 5.089199] systemd[1]: systemd-sysctl.service changed start -> exited
    [ 5.089210] systemd[1]: Job systemd-sysctl.service/start finished, result=done
    [ 5.336181] FS-Cache: Loaded
    [ 5.379562] RPC: Registered named UNIX socket transport module.
    [ 5.379567] RPC: Registered udp transport module.
    [ 5.379569] RPC: Registered tcp transport module.
    [ 5.379570] RPC: Registered tcp NFSv4.1 backchannel transport module.
    [ 5.585237] NFS: Registering the id_resolver key type
    [ 5.585264] Key type id_resolver registered
    [ 5.585266] Key type id_legacy registered
    [ 5.585278] FS-Cache: Netfs 'nfs' registered for caching
    [ 5.586108] systemd[1]: Received SIGCHLD from PID 124 (systemd-modules).
    [ 5.586146] systemd[1]: Got SIGCHLD for process 124 (systemd-modules)
    [ 5.586225] systemd[1]: Child 124 died (code=exited, status=0/SUCCESS)
    [ 5.586229] systemd[1]: Child 124 belongs to systemd-modules-load.service
    [ 5.586250] systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=0
    [ 5.586590] systemd[1]: systemd-modules-load.service changed start -> exited
    [ 5.586605] systemd[1]: Job systemd-modules-load.service/start finished, result=done
    [ 5.586717] systemd[1]: Starting of sys-kernel-config.mount requested but condition failed. Ignoring.
    [ 5.586722] systemd[1]: Job sys-kernel-config.mount/start finished, result=done
    [ 5.586742] systemd[1]: Starting of sys-fs-fuse-connections.mount requested but condition failed. Ignoring.
    [ 5.586746] systemd[1]: Job sys-fs-fuse-connections.mount/start finished, result=done
    [ 5.615412] systemd[1]: Accepted connection on private bus.
    [ 5.725920] systemd-journald[128]: Successfully opened /dev/kmsg for logging.
    [ 5.758577] systemd-journald[128]: Fixed max_use=75.1M max_size=9.3M min_size=64.0K keep_free=37.5M
    [ 5.758646] systemd-journald[128]: Reserving 17095 entries in hash table.
    [ 5.759414] systemd-journald[128]: Vacuuming...
    [ 5.759466] systemd-journald[128]: Flushing /dev/kmsg...
    [ 5.777632] systemd[1]: dev-hugepages.mount changed mounting -> mounting-done
    [ 5.777647] systemd[1]: Job dev-hugepages.mount/start finished, result=done
    [ 5.777687] systemd[1]: sys-kernel-debug.mount changed mounting -> mounting-done
    [ 5.777694] systemd[1]: Job sys-kernel-debug.mount/start finished, result=done
    [ 5.777716] systemd[1]: dev-mqueue.mount changed mounting -> mounting-done
    [ 5.777724] systemd[1]: Job dev-mqueue.mount/start finished, result=done
    [ 5.777819] systemd[1]: Received SIGCHLD from PID 125 (mount).
    [ 5.777855] systemd[1]: Got SIGCHLD for process 121 (mount)
    [ 5.777932] systemd[1]: Child 121 died (code=exited, status=0/SUCCESS)
    [ 5.777935] systemd[1]: Child 121 belongs to dev-mqueue.mount
    [ 5.777949] systemd[1]: dev-mqueue.mount mount process exited, code=exited status=0
    [ 5.777962] systemd[1]: dev-mqueue.mount changed mounting-done -> mounted
    [ 5.777998] systemd[1]: Got SIGCHLD for process 123 (mount)
    [ 5.778052] systemd[1]: Child 123 died (code=exited, status=0/SUCCESS)
    [ 5.778056] systemd[1]: Child 123 belongs to sys-kernel-debug.mount
    [ 5.778064] systemd[1]: sys-kernel-debug.mount mount process exited, code=exited status=0
    [ 5.778073] systemd[1]: sys-kernel-debug.mount changed mounting-done -> mounted
    [ 5.778104] systemd[1]: Got SIGCHLD for process 125 (mount)
    [ 5.778159] systemd[1]: Child 125 died (code=exited, status=0/SUCCESS)
    [ 5.778163] systemd[1]: Child 125 belongs to dev-hugepages.mount
    [ 5.778171] systemd[1]: dev-hugepages.mount mount process exited, code=exited status=0
    [ 5.778179] systemd[1]: dev-hugepages.mount changed mounting-done -> mounted
    [ 5.778270] systemd[1]: Accepted connection on private bus.
    [ 5.778429] systemd[1]: Accepted connection on private bus.
    [ 5.778509] systemd[1]: Accepted connection on private bus.
    [ 5.779032] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
    [ 5.779152] systemd[1]: systemd-udev-trigger.service: cgroup is empty
    [ 5.779481] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 5.779740] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
    [ 5.786928] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
    [ 5.790217] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 5.790280] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 5.790338] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
    [ 5.796880] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 5.807799] systemd-journald[128]: systemd-journald running as pid 128
    [ 5.808306] systemd[1]: Got notification message for unit systemd-journald.service
    [ 5.808312] systemd[1]: systemd-journald.service: Got message
    [ 5.808318] systemd[1]: systemd-journald.service: got STATUS=Processing requests...
    [ 6.246284] EXT4-fs (sda2): re-mounted. Opts: (null)
    [ 6.247294] systemd[1]: Received SIGCHLD from PID 118 (systemd-remount).
    [ 6.247328] systemd[1]: Got SIGCHLD for process 118 (systemd-remount)
    [ 6.247396] systemd[1]: Child 118 died (code=exited, status=0/SUCCESS)
    [ 6.247401] systemd[1]: Child 118 belongs to systemd-remount-fs.service
    [ 6.247419] systemd[1]: systemd-remount-fs.service: main process exited, code=exited, status=0
    [ 6.247721] systemd[1]: systemd-remount-fs.service changed start -> exited
    [ 6.247733] systemd[1]: Job systemd-remount-fs.service/start finished, result=done
    [ 6.247797] systemd[1]: local-fs-pre.target changed dead -> active
    [ 6.247805] systemd[1]: Job local-fs-pre.target/start finished, result=done
    [ 6.317889] systemd[1]: About to execute: /bin/mount tmpfs /tmp -t tmpfs -o nodev,nosuid
    [ 6.319475] systemd[1]: Forked /bin/mount as 140
    [ 6.319523] systemd[1]: tmp.mount changed dead -> mounting
    [ 6.319680] systemd[1]: About to execute: /usr/lib/systemd/systemd-random-seed load
    [ 6.323401] systemd[1]: Forked /usr/lib/systemd/systemd-random-seed as 141
    [ 6.323546] systemd[1]: systemd-random-seed-load.service changed dead -> start
    [ 6.347887] systemd[1]: tmp.mount changed mounting -> mounting-done
    [ 6.347901] systemd[1]: Job tmp.mount/start finished, result=done
    [ 6.348383] systemd[1]: Received SIGCHLD from PID 140 (mount).
    [ 6.348417] systemd[1]: Got SIGCHLD for process 140 (mount)
    [ 6.348489] systemd[1]: Child 140 died (code=exited, status=0/SUCCESS)
    [ 6.348493] systemd[1]: Child 140 belongs to tmp.mount
    [ 6.348504] systemd[1]: tmp.mount mount process exited, code=exited status=0
    [ 6.348515] systemd[1]: tmp.mount changed mounting-done -> mounted
    [ 6.349779] systemd[1]: Accepted connection on private bus.
    [ 6.350675] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
    [ 6.351301] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 6.433691] systemd[1]: dev-ttyS2.device changed dead -> plugged
    [ 6.433715] systemd[1]: sys-devices-platform-serial8250-tty-ttyS2.device changed dead -> plugged
    [ 6.434762] systemd[1]: dev-ttyS3.device changed dead -> plugged
    [ 6.434780] systemd[1]: sys-devices-platform-serial8250-tty-ttyS3.device changed dead -> plugged
    [ 6.439475] systemd[1]: Received SIGCHLD from PID 141 (systemd-random-).
    [ 6.439513] systemd[1]: Got SIGCHLD for process 141 (systemd-random-)
    [ 6.439

    Should I file a bug report? If so, with Arch or upstream?

  • Add fields in transformations in BI 7 (best practice)?

    Hi Experts,
    I have a question regarding transformation of data in BI 7.0.
    Task:
    Add new fields in a second level DSO, based on some manipulation of first level DSO data. In 3.5 we would have used a start routine to manipulate and append the new fields to the structure.
    Possible solutions:
    1) Add the new fields to first level DSO as well (empty)
    - Pro: Simple, easy to understand
    - Con: Disc space consuming, performance degrading when writing to first level DSO
    2) Use routines in the field mapping
    - Pro: Simple
    - Con: Hard to performance optimize (we could of course fill an internal table in the start routine and then read from this to get some performance optimization, but the solution would be more complex).
    3) Update the fields in the End routine
    - Pro: Simple, easy to understand, can be performance optimized
    - Con: We need to ensure that the data we need also exists (i.e. if we have one field in DSO 1 that we only use to calculate a field in DSO 2, this would also have to be mapped to DSO 2 in order to exist in the routine).
    Does anybody know what is best practice is? Or do you have any experience regarding what you see as the best solution?
    Thank you in advance,
    Mikael

    Hi Mikael.
    I like the 3rd option and have used this many many times.  In answer to your question:-
    Update the fields in the End routine
    - Pro: Simple, easy to understand, can be performance optimized  - Yes have read and tested this that it works faster.  A OSS consulting note is out there indicating the speed of the end routine.
    - Con: We need to ensure that the data we need also exists (i.e. if we have one field in DSO 1 that we only use to calculate a field in DSO 2, this would also have to be mapped to DSO 2 in order to exist in the routine). - Yes but by using the result package, the manipulation can be done easily.
    Hope it helps.
    Thanks,
    Pom

  • Temp Tables - Best Practice

    Hello,
    I have a customer who uses temp tables all over their application.
    This customer is a novice and the app has its roots in VB6. We are converting it to .net
    I would really like to know the best practice for using temp tables.
    I have seen code like this in the app.
    CR2.Database.Tables.Item(1).Location = "tempdb.dbo.[##Scott_xwPaySheetDtlForN]"
    That seems to work, though i do not know why the full tempdb.dbo.[## is required.
    However, when i use this in the new report I am doing I get runtime errors.
    i also tried this
    CR2.Database.Tables.Item(1).Location = "##Scott_xwPaySheetDtlForN"
    I did not get errors, but I was returned data i did not expect.
    Before i delve into different ways to do this, i could use some help with a good pattern to use.
    thanks

    Hi Scott,
    Are you using the RDC still? It's not clear but looks like it.
    We had an API that could piggy back the HDBC handle in the RDC ( craxdrt.dll ) but that API is no longer available in .NET. Also, the RDC is not supported in .NET since .NET uses the framework and RDC is COM.
    Work around is to copy the temp data into a data set and then set location to the data set. There is no way that I know of to get to the tempdb from .NET. Reason being is there is no CR API to set the owner of the table to the user, MS SQL Server locks the tempdb to that user has exclusinve rights on it.
    Thank you
    Don

  • Best Practice for Significant Amounts of Data

    This is basically a best-practice/concept question and it spans both Xcelsius & Excel functions:
    I am working on a dashboard for the US Military to report on some basic financial transactions that happen on bases around the globe.  These transactions fall into four categories, so my aggregation is as follows:
    Year,Month,Country,Base,Category (data is Transaction Count and Total Amount)
    This is a rather high level of aggregation, and it takes about 20 million transactions and aggregates them into about 6000 rows of data for a two year period.
    I would like to allow the users to select a Category and a country and see a chart which summarizes transactions for that country ( X-axis for Month, Y-axis Transaction Count or Amount ).  I would like each series on this chart to represent a Base.
    My problem is that 6000 rows still appears to be too many rows for an Xcelsius dashboard to handle.  I have followed the Concatenated Key approach and used SUMIF to populate a matrix with the data for use in the Chart.  This matrix would have Bases for row headings (only those within the selected country) and the Column Headings would be Month.  The data would be COUNT. (I also need the same matrix with Dollar Amounts as the data). 
    In Excel this matrix works fine and seems to be very fast.  The problem is with Xcelsius.  I have imported the Spreadsheet, but have NOT even created the chart yet and Xcelsius is CHOKING (and crashing).  I changed Max Rows to 7000 to accommodate the data.  I placed a simple combo box and a grid on the Canvas u2013 BUT NO CHART yet u2013 and the dashboard takes forever to generate and is REALLY slow to react to a simple change in the Combo Box.
    So, I guess this brings up a few questions:
    1)     Am I doing something wrong and did I miss something that would prevent this problem?
    2)     If this is standard Xcelsius behavior, what are the Best Practices to solve the problem?
    a.     Do I have to create 50 different Data Ranges in order to improve performance (i.e. Each Country-Category would have a separate range)?
    b.     Would it even work if it had that many data ranges in it?
    c.     Do you aggregate it as a crosstab (Months as Column headings) and insert that crosstabbed data into Excel.
    d.     Other ideas  that Iu2019m missing?
    FYI:  These dashboards will be exported to PDF and distributed.  They will not be connected to a server or data source.
    Any thoughts or guidance would be appreciated.
    Thanks,
    David

    Hi David,
    I would leave your query
    "Am I doing something wrong and did I miss something that would prevent this problem?"
    to the experts/ gurus out here on this forum.
    From my end, you can follow
    TOP 10 EXCEL TIPS FOR SUCCESS
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/204c3259-edb2-2b10-4a84-a754c9e1aea8
    Please follow the Xcelsius Best Practices at
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a084a11c-6564-2b10-79ac-cc1eb3f017ac
    In order to reduce the size of xlf and swf files follow
    http://myxcelsius.com/2009/03/18/reduce-the-size-of-your-xlf-and-swf-files/
    Hope this helps to certain extent.
    Regards
    Nikhil

  • Best-practice for Catalog Views ? :|

    Hello community,
    A best practice question:
    The situtation: I have several product categories (110), several items in those categories (4000) and 300 end-users.    I would like to know which is the best practice for segment the catalog.   I mean, some users should only see categories 10,20 & 30.  Other users only category 80, etc.    The problem is how can I implement this ?
    My first idea is:
    1. Create 110 Procurement Catalogs (1 for every prod.category).   Each catalog should contain only its product category.
    2. Assign in my Org Model, in a user-level all the "catalogs" that the user should access.
    Do you have any idea in order to improve this ?
    Saludos desde Mexico,
    Diego

    Hi,
    Your way of doing will work, but you'll get maintenance issues (to many catalogs, and catalog link to maintain for each user).
    The other way is to built your views in CCM, and assign these views to the users, either on the roles (PFCG) or on the user (SU01). The problem is that with CCM 1.0 this is limitated, cause you'll have to assign one by one the items to each view (no dynamic or mass processes), it has been enhanced in CCM 2.0.
    My advice:
    -Challenge your customer about views, and try to limit the number of views, with for example strategic and non strategic
    -With CCM 1.0 stick to the procurement catalogs, or implement BADIs to assign items to the views (I experienced it, it works, but is quite difficult), but with a limitated number of views
    Good luck.
    Vadim

Maybe you are looking for

  • What is the best all-in-one printer out there today

    I have a home office.  I have been running either Canon or Epson printers for years.  My Canon MP830 is dying - I am getting a blac stripe down the middle of every paper.  I need a new all-in-one printer.  I want it to work wirelessly and the ink sho

  • T61 and Presentation director 4.03

    Hi, I have a T61 notebook, upgraded ThinkVantage software and now I am facing serious problem with Presentation director. When I open the presentation chooser with Fn+F7, I can see all old profiles to be imported from previous version. The problem is

  • Airport express (x2) is not recognised by airport utility despite factory hard re-set. Unbelievably annoying! Any ideas?

    My airpor express (2 of them) is not recognised by itunes or by airport utility over wife despite a hard reset. I am using windows xp ..... So so frustrating -

  • How can i delete an element in a XMLTYPE-Column?

    Hi! I have the following xml-doc in an xmltype-column: <root> [...a lot of different elements...] <a_element type="a">[...]</a_element> <a_element type="b">[...]</a_element> [...a lot of different elements...] </root> Now I want to "delete" all a_ele

  • Error in Electronic bank statement

    Hi Guys, am trying to do Electronic bank statement, statement is generating but automatic clearing with GL (Main Bank and Bank clearing account) is not happening. T.code: FEBAN error shown under this transaction... i did not get any error log...how d