RZ11 - sapgui/user_scripting - effects if we change from FALSE to TRUE

Hi Gurus,
While executing eCATT in produciton system, I need to make pre requisite settings like in RZ11- sapgui/user_scripting I need to change value to TRUE. But as It is related to "Scripting", can somebody explain me effects of making this value from FALSE to TRUE. Does that affect somewhere as such.. in other programs or other codes or etc..
I would really appreciate if you reply <removed by moderator>
thanks in advance
regards
Amol
Edited by: Thomas Zloch on Aug 8, 2011 2:57 PM

Hi,
GuiXT is a client-server based software technology that provides user interface customization solutions to SAP applications.
It takes existing functionality in SAP t-codes and allows us to redesign the layout and business process to match the customer needs. One important thing to be noted is that it already comes installed with SAP GUI. Since it comes with SAP GUI, GuiXT can help us customize just about any transaction in SAP.  
TRUE : Enabling scripting on front end.
on each user machine, we have to activate the GUIXT .
Thanks,
Anitha A

Similar Messages

  • Changing Connect Profile Opt-in Setting from False to True

    Users on Connect who cannot accept Invitation IDs to our Preview programs want to update their accounts to indicate that Opt-in equals true.
    Despite instructions showing a radio button control for this setting, I cannot find the setting itself within my Connect profile.
    Please help.
    Thanks!

    Might send a message here.
    https://connect.microsoft.com/Help/EmailSupportNew.aspx?Category=3
    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]
    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

  • [svn:fx-trunk] 7868: Fixed bug in flex4test testWheel app; it needed to be updated to the latest effects API after motionPaths changed from an Array to a Vector . MotionPath

    Revision: 7868
    Author:   [email protected]
    Date:     2009-06-15 16:37:33 -0700 (Mon, 15 Jun 2009)
    Log Message:
    Fixed bug in flex4test testWheel app; it needed to be updated to the latest effects API after motionPaths changed from an Array to a Vector.
    Modified Paths:
        flex/sdk/trunk/development/eclipse/flex/flex4test/src/testWheel.mxml

    Walter Laan wrote:
    almightywiz wrote:
    Walter Laan wrote:
    The security popup really messes with the focus in Firefox (3.6.16) though.Not saying you're wrong, but I'm using FireFox 3.6.16, as well, and I have none of the focus troubles you've described.Cannot reproduce it now either. Weird.I got the impression you were referring to keyboard focus, so I did some further tests on focus behavior. The test results are listed in the Accumulated Results table on the 1st post.
    The only browser so far that works as I'd expect, or at least as I'd like, is IE.
    Applets and keyboard navigation have always been a PITA. Some time ago I vaguely recall seeing an update involving a new parameter to regulate initial focus (applet or page, ..or another applet), but for the life of me I cannot locate it now. Given that it was a parameter for initial focus, I doubt it would help in this case.
    Edited by: Andrew Thompson on Mar 26, 2011 6:18 PM
    Removed table which has now been expanded & added to 1st post.

  • Silly question, maybe. I want to change from Verizon DSL to cable, but cable company doesn't supply router.  can I use my Airport Extreme as wireless router?

    We currently have the following wireless home-network configuration, powered by Verizon DSL. 
    2 macbook pro’s
    1 emachine
    HP PhotoSmart 6122 all-in-one printer
    Apple TV
    Apple Airport Extreme Base Port A 1408
    Westell 7500 router
    Thinking I’d get wider wireless coverage throughout my 2 bedroom home, I purchased the Airport Extreme. It is connected to the router via its sole usb port.  The result was only a tiny increase in speed, and no increase in coverage, so I don’t know why I have it.
    We now want to change from DSL to cable, thus ditching Verizon.  Our new cable provider supplies the cable box, but no router for wireless networking. 
    Here are my questions.
    Can I use the Airport Extreme (AE) as a wireless router? 
    If so, how should I hook it up?  Should the usb cable go from the AE to the cable box, and all the other devices connect wirelessly?
    If not, how should I be using the AE to some advantage?  What can I get out of the investment?
    Thank you very much for your help!  Beatriz

    What I wrote has nothing to do with what the cable company charges for their installation. And, usually they will help with the router setup even if you supply your own router. I don't know what they will charge for the modem.
    Note that you need to get just a modem. You don't want a modem/router combination. That will make using an AEBS effectively nearly impossible. You will need to ask specifically for just a standalone modem, and that you will supply your own router.

  • The application detected an error that prevents changes from being saved.

    Hi. I'm having this problem almost all the time when I do some color correction.
    "The application detected an error that prevents changes from being saved. To avoid losing your work, quit Final Cut Pro."
    Any ideas why this is happening?
    I'm on a 2010 Mac Pro running latest Mavericks and latest FCP X.
    I already removed FCP X, and all the effects I have installed. But still the issue persists.
    Thanks.

    That could have happened. I can't remember though.
    Is there any work around?
    I currently only have 1 open library and 1 event on it. If I move or copy that event into a new library, would that in theory work?
    Thanks for the help so far.

  • Field Mobile phone (ADR2-R3_USER) vendor master changed from Blank to 1

    Hi
    Where I can find Mobile phone (ADR2-R3_USER) in Vendor master.
    We have updated Purchasing block to vendor master via LSMW and after that if i am going to see the changes in vendor master (XK03)
    Found that the field Mobile phone (ADR2-R3_USER) changed from BLANK to ONE
    Field            Mobile phone (ADR2-R3_USER)
      from
      to                1
    Not sure what happened.
    Can any one throw some ides on this?
    Regards
    Jai

    Hello,
    F1 on the field ADR2-R3_USER gave the below information.  Check if this is useful.
    Indicator: Telephone is a Mobile Telephone
    This field specifies whether the telephone number is a mobile telephone number.
    Input values
    ' ' :  The telephone number is a fixed-line telephone
    '1' :  The telephone number is the standard fixed-line telephone
    '2' :  The telephone nubmer is a mobile telephone
    '3' :  The telephone number is the standard mobile telephone
    Dependencies
    Either the standard fixed-line telephone number or the standard mobile telephone number is also the standard telephone number (FLGDEFAULT = 'X').
    In older data sets, this field may have also have the value ' ' for the standard fixed-line telephone. In this case, however, FLGDEFAULT is always 'X'.
    Effects on Customizing
    In Customizing, you can specify whether the SMS-compatible indicator is to be proposed for new mobile telephone numbers created in dialog by choosing General Settings -> Set countries  -> Define Mobile Telephone Attributes for each country.
    Cheers
    Balaji

  • Login changes from WLCS 3.2 vs WLCS 3.5

    I am upgrading my current prototype using WLCS3.2 to 3.5. I use the
    exampleportal demo and plug in a few JSP's from my web application.
    In 3.2, after you enter your login information the request object that all
    portlets have access to contains 3 parameters: loginAction, username and
    password. I use this information in order to log into my application which
    allows me to have a single signon.
    In 3.5, things have changed and the only parameter that I have access to
    through the request object is 'dest' which has the path to
    /something/loginSuccess.jsp. How do I now get access to login information
    from the portal similar to what was available to me in 3.2?
    thank you
    shane

    Peter,
    Thanks for the quick reply. I'll let you know how I make out.
    thanks
    shane
    "Peter Laird" <[email protected]> wrote in message
    news:[email protected]...
    >
    Shane,
    Excellent question. Let me point you to some reading:
    1. There is a brand new security guide for 3.5 athttp://edocs.bea.com/wlcs/docs35/secguide/index.htm
    >
    2. Read the Security chapter of the Servlet 2.2 spec, found athttp://java.sun.com/products/servlet/index.html
    >
    >
    Realize that the 3.2 portal's implementation of the security mechanismpredated
    the standard J2EE declarative security model. The 3.5 release of portalreimplemented
    security to adhere to the standard. So the missing attributes is aside-effect
    of this change.
    In 3.2, the portal was responsible for doing its own user authentication.Therefore
    the username and password was available to the portal code. In 3.5, theservlet
    container (WLS) performs the authentication on behalf of the portal. Asyou see
    in the Servlet spec, the methods available to a servlet afterauthentication allow
    you to get the username via request.getUserPrincipal(). But there is nostandard
    way to get the password. So if you require the password to propagate theidentity
    to another application, you are out of luck.
    All is not lost though. I can think of three avenues for you.
    1. Reread section 11.6 of the Servlet 2.2 spec. It declares that thecontainer
    must maintain authentication at the container-scope, and not the web-appscope.
    Know that the portal is deployed as a webapp. If your secondaryapplication can
    be deployed as a J2EE web-app on the same server, authentication can bemaintained
    across web-apps.
    2. If you cannot deploy your app as a web-app, there is still anotheroption.
    WLS supports an "Authentication Filter" which is invoked both immediatelyprior
    and immediately after the j_security_check authentication mechanism. Thisallows
    you to provide a callback which accepts the HttpRequest. Therefore, youshould
    be able to stash the j_password into the Session before WLS clears it outof the
    Request. I don't have time to try this today, but if you do please postyour results!
    Read here for more info on the AuthFilterhttp://e-docs.bea.com/wls/docs60//javadocs/weblogic/servlet/security/AuthFil
    ter.html
    >
    >
    3. If the above options don't work for you, you may wish to implement acustom
    WLS security realm which will provide passwords for users upon request.
    Post back to the newsgroup with your thoughts/results.
    PJL
    "Shane Daniels" <[email protected]> wrote:
    I am upgrading my current prototype using WLCS3.2 to 3.5. I use the
    exampleportal demo and plug in a few JSP's from my web application.
    In 3.2, after you enter your login information the request object that
    all
    portlets have access to contains 3 parameters: loginAction, username
    and
    password. I use this information in order to log into my application
    which
    allows me to have a single signon.
    In 3.5, things have changed and the only parameter that I have access
    to
    through the request object is 'dest' which has the path to
    /something/loginSuccess.jsp. How do I now get access to login
    information
    from the portal similar to what was available to me in 3.2?
    thank you
    shane

  • Is there any retro effect for this changes we made in 2001 Infotype for

    HI Experts...
    Please advice me on the follwing absence issue.
    In my clients company.... .... one of Personnel areas employees Earned leave records are not updating in 2001 Infotype from the begining.
    Now they wish to have to update in 2001 Infotype.
    What  are the  Retro effects after updating the EL s in 2001 IT for previous dates.
    Is there any retro effect for this changes we made in 2001 Infotype for the past dates.
    We dont need retro effected from those changes.
    Please advice...
    Sai.

    HI Vincent....
    Thanks for the reply.
    Last month professional tax rates were shown up correctly only.
    For the employees slab rates are similar  that is  200 per month.
    Last month professional  tax rates  were correct only.
    For the current month also the prof tax amount is showing up correctly only.
    Please advice to get the professional tax amount in the payslip.
    Regards,
    V Sai.

  • Wireless adapter name is changing from wlp0s26u1u1 to wlan0

    If I reboot my computer from an on state the name changes from wlp0s26u1u1 to wlan0 which makes me unable to connect to wifi, even if I make a netctl profile for wlan0, it fails.
    If I start my computer from an off state, the adapter takes the name wlp0s26u1u1 and everything works smoothly.
    Why does this happen? Is it a bug? How can I fix it?
    Thanks.

    Cold
    -- Logs begin at Fri 2013-09-20 15:59:51 PDT, end at Sun 2014-03-09 06:40:40 PDT. --
    Mar 09 06:33:04 ---- systemd-journal[136]: Runtime journal is using 8.0M (max allowed 598.7M, trying to leave 898.1M free of 5.8G available → current limit 598.7M).
    Mar 09 06:33:04 ---- systemd-journal[136]: Runtime journal is using 8.0M (max allowed 598.7M, trying to leave 898.1M free of 5.8G available → current limit 598.7M).
    Mar 09 06:33:04 ---- kernel: Initializing cgroup subsys cpuset
    Mar 09 06:33:04 ---- kernel: Initializing cgroup subsys cpu
    Mar 09 06:33:04 ---- kernel: Initializing cgroup subsys cpuacct
    Mar 09 06:33:04 ---- kernel: Linux version 3.13.6-1-ARCH (nobody@var-lib-archbuild-extra-x86_64-thomas) (gcc version 4.8.2 20140206 (prerelease) (GCC) ) #1 SMP PREEMPT Fri Mar 7 22:47:48 CET 2014
    Mar 09 06:33:04 ---- kernel: Command line: BOOT_IMAGE=../vmlinuz-linux root=/dev/sda1 rw nomodeset initrd=../initramfs-linux.img
    Mar 09 06:33:04 ---- kernel: e820: BIOS-provided physical RAM map:
    Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009d7ff] usable
    Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x000000000009d800-0x000000000009ffff] reserved
    Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
    Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000dd74efff] usable
    Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x00000000dd74f000-0x00000000de052fff] reserved
    Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x00000000de053000-0x00000000de0dffff] usable
    Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x00000000de0e0000-0x00000000de17dfff] ACPI NVS
    Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x00000000de17e000-0x00000000de979fff] reserved
    Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x00000000de97a000-0x00000000de97afff] usable
    Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x00000000de97b000-0x00000000de9bdfff] ACPI NVS
    Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x00000000de9be000-0x00000000df3f6fff] usable
    Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x00000000df3f7000-0x00000000df7f1fff] reserved
    Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x00000000df7f2000-0x00000000df7fffff] usable
    Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
    Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
    Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
    Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
    Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
    Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
    Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x0000000100000000-0x000000031effffff] usable
    Mar 09 06:33:04 ---- kernel: NX (Execute Disable) protection: active
    Mar 09 06:33:04 ---- kernel: SMBIOS 2.7 present.
    Mar 09 06:33:04 ---- kernel: DMI: To Be Filled By O.E.M. To Be Filled By O.E.M./Z77 Extreme4, BIOS P2.70 11/28/2012
    Mar 09 06:33:04 ---- kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
    Mar 09 06:33:04 ---- kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
    Mar 09 06:33:04 ---- kernel: No AGP bridge found
    Mar 09 06:33:04 ---- kernel: e820: last_pfn = 0x31f000 max_arch_pfn = 0x400000000
    Mar 09 06:33:04 ---- kernel: MTRR default type: uncachable
    Mar 09 06:33:04 ---- kernel: MTRR fixed ranges enabled:
    Mar 09 06:33:04 ---- kernel: 00000-9FFFF write-back
    Mar 09 06:33:04 ---- kernel: A0000-BFFFF uncachable
    Mar 09 06:33:04 ---- kernel: C0000-CFFFF write-protect
    Mar 09 06:33:04 ---- kernel: D0000-E7FFF uncachable
    Mar 09 06:33:04 ---- kernel: E8000-FFFFF write-protect
    Mar 09 06:33:04 ---- kernel: MTRR variable ranges enabled:
    Mar 09 06:33:04 ---- kernel: 0 base 000000000 mask E00000000 write-back
    Mar 09 06:33:04 ---- kernel: 1 base 200000000 mask F00000000 write-back
    Mar 09 06:33:04 ---- kernel: 2 base 300000000 mask FF0000000 write-back
    Mar 09 06:33:04 ---- kernel: 3 base 310000000 mask FF8000000 write-back
    Mar 09 06:33:04 ---- kernel: 4 base 318000000 mask FFC000000 write-back
    Mar 09 06:33:04 ---- kernel: 5 base 31C000000 mask FFE000000 write-back
    Mar 09 06:33:04 ---- kernel: 6 base 31E000000 mask FFF000000 write-back
    Mar 09 06:33:04 ---- kernel: 7 base 0E0000000 mask FE0000000 uncachable
    Mar 09 06:33:04 ---- kernel: 8 disabled
    Mar 09 06:33:04 ---- kernel: 9 disabled
    Mar 09 06:33:04 ---- kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    Mar 09 06:33:04 ---- kernel: e820: update [mem 0xe0000000-0xffffffff] usable ==> reserved
    Mar 09 06:33:04 ---- kernel: e820: last_pfn = 0xdf800 max_arch_pfn = 0x400000000
    Mar 09 06:33:04 ---- kernel: found SMP MP-table at [mem 0x000fd8d0-0x000fd8df] mapped at [ffff8800000fd8d0]
    Mar 09 06:33:04 ---- kernel: Scanning 1 areas for low memory corruption
    Mar 09 06:33:04 ---- kernel: Base memory trampoline at [ffff880000097000] 97000 size 24576
    Mar 09 06:33:04 ---- kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
    Mar 09 06:33:04 ---- kernel: [mem 0x00000000-0x000fffff] page 4k
    Mar 09 06:33:04 ---- kernel: BRK [0x01b3f000, 0x01b3ffff] PGTABLE
    Mar 09 06:33:04 ---- kernel: BRK [0x01b40000, 0x01b40fff] PGTABLE
    Mar 09 06:33:04 ---- kernel: BRK [0x01b41000, 0x01b41fff] PGTABLE
    Mar 09 06:33:04 ---- kernel: init_memory_mapping: [mem 0x31ee00000-0x31effffff]
    Mar 09 06:33:04 ---- kernel: [mem 0x31ee00000-0x31effffff] page 2M
    Mar 09 06:33:04 ---- kernel: BRK [0x01b42000, 0x01b42fff] PGTABLE
    Mar 09 06:33:04 ---- kernel: init_memory_mapping: [mem 0x31c000000-0x31edfffff]
    Mar 09 06:33:04 ---- kernel: [mem 0x31c000000-0x31edfffff] page 2M
    Mar 09 06:33:04 ---- kernel: init_memory_mapping: [mem 0x300000000-0x31bffffff]
    Mar 09 06:33:04 ---- kernel: [mem 0x300000000-0x31bffffff] page 2M
    Mar 09 06:33:04 ---- kernel: init_memory_mapping: [mem 0x00100000-0xdd74efff]
    Mar 09 06:33:04 ---- kernel: [mem 0x00100000-0x001fffff] page 4k
    Mar 09 06:33:04 ---- kernel: [mem 0x00200000-0xdd5fffff] page 2M
    Mar 09 06:33:04 ---- kernel: [mem 0xdd600000-0xdd74efff] page 4k
    Mar 09 06:33:04 ---- kernel: init_memory_mapping: [mem 0xde053000-0xde0dffff]
    Mar 09 06:33:04 ---- kernel: [mem 0xde053000-0xde0dffff] page 4k
    Mar 09 06:33:04 ---- kernel: BRK [0x01b43000, 0x01b43fff] PGTABLE
    Mar 09 06:33:04 ---- kernel: init_memory_mapping: [mem 0xde97a000-0xde97afff]
    Mar 09 06:33:04 ---- kernel: [mem 0xde97a000-0xde97afff] page 4k
    Mar 09 06:33:04 ---- kernel: BRK [0x01b44000, 0x01b44fff] PGTABLE
    Mar 09 06:33:04 ---- kernel: init_memory_mapping: [mem 0xde9be000-0xdf3f6fff]
    Mar 09 06:33:04 ---- kernel: [mem 0xde9be000-0xde9fffff] page 4k
    Mar 09 06:33:04 ---- kernel: [mem 0xdea00000-0xdf1fffff] page 2M
    Mar 09 06:33:04 ---- kernel: [mem 0xdf200000-0xdf3f6fff] page 4k
    Mar 09 06:33:04 ---- kernel: init_memory_mapping: [mem 0xdf7f2000-0xdf7fffff]
    Mar 09 06:33:04 ---- kernel: [mem 0xdf7f2000-0xdf7fffff] page 4k
    Mar 09 06:33:04 ---- kernel: init_memory_mapping: [mem 0x100000000-0x2ffffffff]
    Mar 09 06:33:04 ---- kernel: [mem 0x100000000-0x2ffffffff] page 2M
    Mar 09 06:33:04 ---- kernel: RAMDISK: [mem 0x7fcfd000-0x7fffffff]
    Mar 09 06:33:04 ---- kernel: ACPI: RSDP 00000000000f0490 000024 (v02 ALASKA)
    Mar 09 06:33:04 ---- kernel: ACPI: XSDT 00000000de16f078 00006C (v01 ALASKA A M I 01072009 AMI 00010013)
    Mar 09 06:33:04 ---- kernel: ACPI: FACP 00000000de178f58 00010C (v05 ALASKA A M I 01072009 AMI 00010013)
    Mar 09 06:33:04 ---- kernel: ACPI: DSDT 00000000de16f178 009DDD (v02 ALASKA A M I 00000022 INTL 20051117)
    Mar 09 06:33:04 ---- kernel: ACPI: FACS 00000000de17c080 000040
    Mar 09 06:33:04 ---- kernel: ACPI: APIC 00000000de179068 000072 (v03 ALASKA A M I 01072009 AMI 00010013)
    Mar 09 06:33:04 ---- kernel: ACPI: FPDT 00000000de1790e0 000044 (v01 ALASKA A M I 01072009 AMI 00010013)
    Mar 09 06:33:04 ---- kernel: ACPI: MCFG 00000000de179128 00003C (v01 ALASKA A M I 01072009 MSFT 00000097)
    Mar 09 06:33:04 ---- kernel: ACPI: AAFT 00000000de179168 000112 (v01 ALASKA OEMAAFT 01072009 MSFT 00000097)
    Mar 09 06:33:04 ---- kernel: ACPI: HPET 00000000de179280 000038 (v01 ALASKA A M I 01072009 AMI. 00000005)
    Mar 09 06:33:04 ---- kernel: ACPI: SSDT 00000000de1792b8 00036D (v01 SataRe SataTabl 00001000 INTL 20091112)
    Mar 09 06:33:04 ---- kernel: ACPI: SSDT 00000000de179628 000A92 (v01 PmRef CpuPm 00003000 INTL 20051117)
    Mar 09 06:33:04 ---- kernel: ACPI: BGRT 00000000de17a0c0 000038 (v00 ALASKA A M I 01072009 AMI 00010013)
    Mar 09 06:33:04 ---- kernel: ACPI: Local APIC address 0xfee00000
    Mar 09 06:33:04 ---- kernel: No NUMA configuration found
    Mar 09 06:33:04 ---- kernel: Faking a node at [mem 0x0000000000000000-0x000000031effffff]
    Mar 09 06:33:04 ---- kernel: Initmem setup node 0 [mem 0x00000000-0x31effffff]
    Mar 09 06:33:04 ---- kernel: NODE_DATA [mem 0x31efed000-0x31eff1fff]
    Mar 09 06:33:04 ---- kernel: [ffffea0000000000-ffffea000c7fffff] PMD -> [ffff880312600000-ffff88031e5fffff] on node 0
    Mar 09 06:33:04 ---- kernel: Zone ranges:
    Mar 09 06:33:04 ---- kernel: DMA [mem 0x00001000-0x00ffffff]
    Mar 09 06:33:04 ---- kernel: DMA32 [mem 0x01000000-0xffffffff]
    Mar 09 06:33:04 ---- kernel: Normal [mem 0x100000000-0x31effffff]
    Mar 09 06:33:04 ---- kernel: Movable zone start for each node
    Mar 09 06:33:04 ---- kernel: Early memory node ranges
    Mar 09 06:33:04 ---- kernel: node 0: [mem 0x00001000-0x0009cfff]
    Mar 09 06:33:04 ---- kernel: node 0: [mem 0x00100000-0xdd74efff]
    Mar 09 06:33:04 ---- kernel: node 0: [mem 0xde053000-0xde0dffff]
    Mar 09 06:33:04 ---- kernel: node 0: [mem 0xde97a000-0xde97afff]
    Mar 09 06:33:04 ---- kernel: node 0: [mem 0xde9be000-0xdf3f6fff]
    Mar 09 06:33:04 ---- kernel: node 0: [mem 0xdf7f2000-0xdf7fffff]
    Mar 09 06:33:04 ---- kernel: node 0: [mem 0x100000000-0x31effffff]
    Mar 09 06:33:04 ---- kernel: On node 0 totalpages: 3133888
    Mar 09 06:33:04 ---- kernel: DMA zone: 64 pages used for memmap
    Mar 09 06:33:04 ---- kernel: DMA zone: 21 pages reserved
    Mar 09 06:33:04 ---- kernel: DMA zone: 3996 pages, LIFO batch:0
    Mar 09 06:33:04 ---- kernel: DMA32 zone: 14153 pages used for memmap
    Mar 09 06:33:04 ---- kernel: DMA32 zone: 905764 pages, LIFO batch:31
    Mar 09 06:33:04 ---- kernel: Normal zone: 34752 pages used for memmap
    Mar 09 06:33:04 ---- kernel: Normal zone: 2224128 pages, LIFO batch:31
    Mar 09 06:33:04 ---- kernel: ACPI: PM-Timer IO Port: 0x408
    Mar 09 06:33:04 ---- kernel: ACPI: Local APIC address 0xfee00000
    Mar 09 06:33:04 ---- kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
    Mar 09 06:33:04 ---- kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
    Mar 09 06:33:04 ---- kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
    Mar 09 06:33:04 ---- kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)
    Mar 09 06:33:04 ---- kernel: ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
    Mar 09 06:33:04 ---- kernel: ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
    Mar 09 06:33:04 ---- kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
    Mar 09 06:33:04 ---- kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    Mar 09 06:33:04 ---- kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    Mar 09 06:33:04 ---- kernel: ACPI: IRQ0 used by override.
    Mar 09 06:33:04 ---- kernel: ACPI: IRQ2 used by override.
    Mar 09 06:33:04 ---- kernel: ACPI: IRQ9 used by override.
    Mar 09 06:33:04 ---- kernel: Using ACPI (MADT) for SMP configuration information
    Mar 09 06:33:04 ---- kernel: ACPI: HPET id: 0x8086a701 base: 0xfed00000
    Mar 09 06:33:04 ---- kernel: smpboot: Allowing 4 CPUs, 0 hotplug CPUs
    Mar 09 06:33:04 ---- kernel: nr_irqs_gsi: 40
    Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0x0009d000-0x0009dfff]
    Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0x0009e000-0x0009ffff]
    Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
    Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
    Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0xdd74f000-0xde052fff]
    Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0xde0e0000-0xde17dfff]
    Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0xde17e000-0xde979fff]
    Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0xde97b000-0xde9bdfff]
    Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0xdf3f7000-0xdf7f1fff]
    Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0xdf800000-0xf7ffffff]
    Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
    Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0xfc000000-0xfebfffff]
    Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
    Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0xfec01000-0xfecfffff]
    Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0xfed00000-0xfed03fff]
    Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0xfed04000-0xfed1bfff]
    Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
    Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0xfed20000-0xfedfffff]
    Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
    Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0xfee01000-0xfeffffff]
    Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
    Mar 09 06:33:04 ---- kernel: e820: [mem 0xdf800000-0xf7ffffff] available for PCI devices
    Mar 09 06:33:04 ---- kernel: Booting paravirtualized kernel on bare hardware
    Mar 09 06:33:04 ---- kernel: setup_percpu: NR_CPUS:128 nr_cpumask_bits:128 nr_cpu_ids:4 nr_node_ids:1
    Mar 09 06:33:04 ---- kernel: PERCPU: Embedded 29 pages/cpu @ffff88031ec00000 s86336 r8192 d24256 u524288
    Mar 09 06:33:04 ---- kernel: pcpu-alloc: s86336 r8192 d24256 u524288 alloc=1*2097152
    Mar 09 06:33:04 ---- kernel: pcpu-alloc: [0] 0 1 2 3
    Mar 09 06:33:04 ---- kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 3084898
    Mar 09 06:33:04 ---- kernel: Policy zone: Normal
    Mar 09 06:33:04 ---- kernel: Kernel command line: BOOT_IMAGE=../vmlinuz-linux root=/dev/sda1 rw nomodeset initrd=../initramfs-linux.img
    Mar 09 06:33:04 ---- kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
    Mar 09 06:33:04 ---- kernel: xsave: enabled xstate_bv 0x7, cntxt size 0x340
    Mar 09 06:33:04 ---- kernel: Checking aperture...
    Mar 09 06:33:04 ---- kernel: No AGP bridge found
    Mar 09 06:33:04 ---- kernel: Calgary: detecting Calgary via BIOS EBDA area
    Mar 09 06:33:04 ---- kernel: Calgary: Unable to locate Rio Grande table in EBDA - bailing!
    Mar 09 06:33:04 ---- kernel: Memory: 12257392K/12535552K available (5270K kernel code, 836K rwdata, 1672K rodata, 1128K init, 1324K bss, 278160K reserved)
    Mar 09 06:33:04 ---- kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
    Mar 09 06:33:04 ---- kernel: Preemptible hierarchical RCU implementation.
    Mar 09 06:33:04 ---- kernel: RCU dyntick-idle grace-period acceleration is enabled.
    Mar 09 06:33:04 ---- kernel: Dump stacks of tasks blocking RCU-preempt GP.
    Mar 09 06:33:04 ---- kernel: RCU restricting CPUs from NR_CPUS=128 to nr_cpu_ids=4.
    Mar 09 06:33:04 ---- kernel: NR_IRQS:8448 nr_irqs:712 16
    Mar 09 06:33:04 ---- kernel: Console: colour VGA+ 80x25
    Mar 09 06:33:04 ---- kernel: console [tty0] enabled
    Mar 09 06:33:04 ---- kernel: allocated 50331648 bytes of page_cgroup
    Mar 09 06:33:04 ---- kernel: please try 'cgroup_disable=memory' option if you don't want memory cgroups
    Mar 09 06:33:04 ---- kernel: hpet clockevent registered
    Mar 09 06:33:04 ---- kernel: tsc: Fast TSC calibration using PIT
    Mar 09 06:33:04 ---- kernel: tsc: Detected 3399.681 MHz processor
    Mar 09 06:33:04 ---- kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 6802.66 BogoMIPS (lpj=11332270)
    Mar 09 06:33:04 ---- kernel: pid_max: default: 32768 minimum: 301
    Mar 09 06:33:04 ---- kernel: Security Framework initialized
    Mar 09 06:33:04 ---- kernel: AppArmor: AppArmor disabled by boot time parameter
    Mar 09 06:33:04 ---- kernel: Yama: becoming mindful.
    Mar 09 06:33:04 ---- kernel: Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes)
    Mar 09 06:33:04 ---- kernel: Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes)
    Mar 09 06:33:04 ---- kernel: Mount-cache hash table entries: 256
    Mar 09 06:33:04 ---- kernel: Initializing cgroup subsys memory
    Mar 09 06:33:04 ---- kernel: Initializing cgroup subsys devices
    Mar 09 06:33:04 ---- kernel: Initializing cgroup subsys freezer
    Mar 09 06:33:04 ---- kernel: Initializing cgroup subsys net_cls
    Mar 09 06:33:04 ---- kernel: Initializing cgroup subsys blkio
    Mar 09 06:33:04 ---- kernel: CPU: Physical Processor ID: 0
    Mar 09 06:33:04 ---- kernel: CPU: Processor Core ID: 0
    Mar 09 06:33:04 ---- kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
    ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
    Mar 09 06:33:04 ---- kernel: mce: CPU supports 9 MCE banks
    Mar 09 06:33:04 ---- kernel: CPU0: Thermal monitoring enabled (TM1)
    Mar 09 06:33:04 ---- kernel: Last level iTLB entries: 4KB 512, 2MB 0, 4MB 0
    Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32
    tlb_flushall_shift: 2
    Mar 09 06:33:04 ---- kernel: Freeing SMP alternatives memory: 20K (ffffffff819ed000 - ffffffff819f2000)
    Mar 09 06:33:04 ---- kernel: ACPI: Core revision 20131115
    Mar 09 06:33:04 ---- kernel: ACPI: All ACPI Tables successfully acquired
    Mar 09 06:33:04 ---- kernel: ftrace: allocating 21060 entries in 83 pages
    Mar 09 06:33:04 ---- kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    Mar 09 06:33:04 ---- kernel: smpboot: CPU0: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz (fam: 06, model: 3a, stepping: 09)
    Mar 09 06:33:04 ---- kernel: TSC deadline timer enabled
    Mar 09 06:33:04 ---- kernel: Performance Events: PEBS fmt1+, 16-deep LBR, IvyBridge events, full-width counters, Intel PMU driver.
    Mar 09 06:33:04 ---- kernel: ... version: 3
    Mar 09 06:33:04 ---- kernel: ... bit width: 48
    Mar 09 06:33:04 ---- kernel: ... generic registers: 8
    Mar 09 06:33:04 ---- kernel: ... value mask: 0000ffffffffffff
    Mar 09 06:33:04 ---- kernel: ... max period: 0000ffffffffffff
    Mar 09 06:33:04 ---- kernel: ... fixed-purpose events: 3
    Mar 09 06:33:04 ---- kernel: ... event mask: 00000007000000ff
    Mar 09 06:33:04 ---- kernel: x86: Booting SMP configuration:
    Mar 09 06:33:04 ---- kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
    Mar 09 06:33:04 ---- kernel: .... node #0, CPUs: #1 #2 #3
    Mar 09 06:33:04 ---- kernel: x86: Booted up 1 node, 4 CPUs
    Mar 09 06:33:04 ---- kernel: smpboot: Total of 4 processors activated (27208.67 BogoMIPS)
    Mar 09 06:33:04 ---- kernel: devtmpfs: initialized
    Mar 09 06:33:04 ---- kernel: PM: Registering ACPI NVS region [mem 0xde0e0000-0xde17dfff] (647168 bytes)
    Mar 09 06:33:04 ---- kernel: PM: Registering ACPI NVS region [mem 0xde97b000-0xde9bdfff] (274432 bytes)
    Mar 09 06:33:04 ---- kernel: RTC time: 13:33:02, date: 03/09/14
    Mar 09 06:33:04 ---- kernel: NET: Registered protocol family 16
    Mar 09 06:33:04 ---- kernel: cpuidle: using governor ladder
    Mar 09 06:33:04 ---- kernel: cpuidle: using governor menu
    Mar 09 06:33:04 ---- kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
    Mar 09 06:33:04 ---- kernel: ACPI: bus type PCI registered
    Mar 09 06:33:04 ---- kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
    Mar 09 06:33:04 ---- kernel: PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
    Mar 09 06:33:04 ---- kernel: PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
    Mar 09 06:33:04 ---- kernel: PCI: Using configuration type 1 for base access
    Mar 09 06:33:04 ---- kernel: bio: create slab <bio-0> at 0
    Mar 09 06:33:04 ---- kernel: ACPI: Added _OSI(Module Device)
    Mar 09 06:33:04 ---- kernel: ACPI: Added _OSI(Processor Device)
    Mar 09 06:33:04 ---- kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
    Mar 09 06:33:04 ---- kernel: ACPI: Added _OSI(Processor Aggregator Device)
    Mar 09 06:33:04 ---- kernel: ACPI: Executed 1 blocks of module-level executable AML code
    Mar 09 06:33:04 ---- kernel: ACPI Error: [\_PR_.CPU0._PPC] Namespace lookup failure, AE_NOT_FOUND (20131115/psargs-359)
    Mar 09 06:33:04 ---- kernel: ACPI Error: Method parse/execution failed [\_PR_.CPU0._PDC] (Node ffff88030d496280), AE_NOT_FOUND (20131115/psparse-536)
    Mar 09 06:33:04 ---- kernel: ACPI: SSDT 00000000de002c18 000119 (v01 PmRef ApCst 00003000 INTL 20051117)
    Mar 09 06:33:04 ---- kernel: ACPI: Dynamic OEM Table Load:
    Mar 09 06:33:04 ---- kernel: ACPI: SSDT (null) 000119 (v01 PmRef ApCst 00003000 INTL 20051117)
    Mar 09 06:33:04 ---- kernel: ACPI: Interpreter enabled
    Mar 09 06:33:04 ---- kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
    Mar 09 06:33:04 ---- kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
    Mar 09 06:33:04 ---- kernel: ACPI: (supports S0 S3 S4 S5)
    Mar 09 06:33:04 ---- kernel: ACPI: Using IOAPIC for interrupt routing
    Mar 09 06:33:04 ---- kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
    Mar 09 06:33:04 ---- kernel: ACPI: No dock devices found.
    Mar 09 06:33:04 ---- kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
    Mar 09 06:33:04 ---- kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
    Mar 09 06:33:04 ---- kernel: acpi PNP0A08:00: _OSC: platform does not support [PCIeHotplug PME]
    Mar 09 06:33:04 ---- kernel: acpi PNP0A08:00: _OSC: OS now controls [AER PCIeCapability]
    Mar 09 06:33:04 ---- kernel: PCI host bridge to bus 0000:00
    Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: root bus resource [bus 00-3e]
    Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
    Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
    Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
    Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d3fff]
    Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff]
    Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff]
    Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff]
    Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: root bus resource [mem 0x000e0000-0x000e3fff]
    Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: root bus resource [mem 0x000e4000-0x000e7fff]
    Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: root bus resource [mem 0xe0000000-0xfeafffff]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:00.0: [8086:0150] type 00 class 0x060000
    Mar 09 06:33:04 ---- kernel: pci 0000:00:01.0: [8086:0151] type 01 class 0x060400
    Mar 09 06:33:04 ---- kernel: pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
    Mar 09 06:33:04 ---- kernel: pci 0000:00:01.0: System wakeup disabled by ACPI
    Mar 09 06:33:04 ---- kernel: pci 0000:00:14.0: [8086:1e31] type 00 class 0x0c0330
    Mar 09 06:33:04 ---- kernel: pci 0000:00:14.0: reg 0x10: [mem 0xf7f00000-0xf7f0ffff 64bit]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:14.0: PME# supported from D3hot D3cold
    Mar 09 06:33:04 ---- kernel: pci 0000:00:14.0: System wakeup disabled by ACPI
    Mar 09 06:33:04 ---- kernel: pci 0000:00:16.0: [8086:1e3a] type 00 class 0x078000
    Mar 09 06:33:04 ---- kernel: pci 0000:00:16.0: reg 0x10: [mem 0xf7f1a000-0xf7f1a00f 64bit]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1a.0: [8086:1e2d] type 00 class 0x0c0320
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1a.0: reg 0x10: [mem 0xf7f18000-0xf7f183ff]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1a.0: System wakeup disabled by ACPI
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1b.0: [8086:1e20] type 00 class 0x040300
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1b.0: reg 0x10: [mem 0xf7f10000-0xf7f13fff 64bit]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1b.0: System wakeup disabled by ACPI
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.0: [8086:1e10] type 01 class 0x060400
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.0: System wakeup disabled by ACPI
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.3: [8086:1e16] type 01 class 0x060400
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.3: PME# supported from D0 D3hot D3cold
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.3: System wakeup disabled by ACPI
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.4: [8086:1e18] type 01 class 0x060400
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.4: System wakeup disabled by ACPI
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.5: [8086:1e1a] type 01 class 0x060400
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.5: System wakeup disabled by ACPI
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.7: [8086:1e1e] type 01 class 0x060400
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.7: System wakeup disabled by ACPI
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1d.0: [8086:1e26] type 00 class 0x0c0320
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1d.0: reg 0x10: [mem 0xf7f17000-0xf7f173ff]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1d.0: System wakeup disabled by ACPI
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1f.0: [8086:1e44] type 00 class 0x060100
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1f.2: [8086:1e02] type 00 class 0x010601
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1f.2: reg 0x10: [io 0xf070-0xf077]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1f.2: reg 0x14: [io 0xf060-0xf063]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1f.2: reg 0x18: [io 0xf050-0xf057]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1f.2: reg 0x1c: [io 0xf040-0xf043]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1f.2: reg 0x20: [io 0xf020-0xf03f]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1f.2: reg 0x24: [mem 0xf7f16000-0xf7f167ff]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1f.2: PME# supported from D3hot
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1f.3: [8086:1e22] type 00 class 0x0c0500
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1f.3: reg 0x10: [mem 0xf7f15000-0xf7f150ff 64bit]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1f.3: reg 0x20: [io 0xf000-0xf01f]
    Mar 09 06:33:04 ---- kernel: pci 0000:01:00.0: [1002:6738] type 00 class 0x030000
    Mar 09 06:33:04 ---- kernel: pci 0000:01:00.0: reg 0x10: [mem 0xe0000000-0xefffffff 64bit pref]
    Mar 09 06:33:04 ---- kernel: pci 0000:01:00.0: reg 0x18: [mem 0xf7e20000-0xf7e3ffff 64bit]
    Mar 09 06:33:04 ---- kernel: pci 0000:01:00.0: reg 0x20: [io 0xe000-0xe0ff]
    Mar 09 06:33:04 ---- kernel: pci 0000:01:00.0: reg 0x30: [mem 0xf7e00000-0xf7e1ffff pref]
    Mar 09 06:33:04 ---- kernel: pci 0000:01:00.0: supports D1 D2
    Mar 09 06:33:04 ---- kernel: pci 0000:01:00.1: [1002:aa88] type 00 class 0x040300
    Mar 09 06:33:04 ---- kernel: pci 0000:01:00.1: reg 0x10: [mem 0xf7e40000-0xf7e43fff 64bit]
    Mar 09 06:33:04 ---- kernel: pci 0000:01:00.1: supports D1 D2
    Mar 09 06:33:04 ---- kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:01.0: bridge window [io 0xe000-0xefff]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:01.0: bridge window [mem 0xf7e00000-0xf7efffff]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:01.0: bridge window [mem 0xe0000000-0xefffffff 64bit pref]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.0: PCI bridge to [bus 02]
    Mar 09 06:33:04 ---- kernel: pci 0000:03:00.0: [1b21:0612] type 00 class 0x010601
    Mar 09 06:33:04 ---- kernel: pci 0000:03:00.0: reg 0x10: [io 0xd050-0xd057]
    Mar 09 06:33:04 ---- kernel: pci 0000:03:00.0: reg 0x14: [io 0xd040-0xd043]
    Mar 09 06:33:04 ---- kernel: pci 0000:03:00.0: reg 0x18: [io 0xd030-0xd037]
    Mar 09 06:33:04 ---- kernel: pci 0000:03:00.0: reg 0x1c: [io 0xd020-0xd023]
    Mar 09 06:33:04 ---- kernel: pci 0000:03:00.0: reg 0x20: [io 0xd000-0xd01f]
    Mar 09 06:33:04 ---- kernel: pci 0000:03:00.0: reg 0x24: [mem 0xf7d00000-0xf7d001ff]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.3: PCI bridge to [bus 03]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.3: bridge window [io 0xd000-0xdfff]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.3: bridge window [mem 0xf7d00000-0xf7dfffff]
    Mar 09 06:33:04 ---- kernel: pci 0000:04:00.0: [14e4:16b1] type 00 class 0x020000
    Mar 09 06:33:04 ---- kernel: pci 0000:04:00.0: reg 0x10: [mem 0xf0010000-0xf001ffff 64bit pref]
    Mar 09 06:33:04 ---- kernel: pci 0000:04:00.0: reg 0x18: [mem 0xf0000000-0xf000ffff 64bit pref]
    Mar 09 06:33:04 ---- kernel: pci 0000:04:00.0: reg 0x30: [mem 0xf7c00000-0xf7c007ff pref]
    Mar 09 06:33:04 ---- kernel: pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.4: PCI bridge to [bus 04]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.4: bridge window [mem 0xf7c00000-0xf7cfffff]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.4: bridge window [mem 0xf0000000-0xf00fffff 64bit pref]
    Mar 09 06:33:04 ---- kernel: pci 0000:05:00.0: [1b21:1080] type 01 class 0x060401
    Mar 09 06:33:04 ---- kernel: pci 0000:05:00.0: System wakeup disabled by ACPI
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.5: PCI bridge to [bus 05-06]
    Mar 09 06:33:04 ---- kernel: pci 0000:05:00.0: PCI bridge to [bus 06] (subtractive decode)
    Mar 09 06:33:04 ---- kernel: pci 0000:05:00.0: bridge window [??? 0x00000000 flags 0x0] (subtractive decode)
    Mar 09 06:33:04 ---- kernel: pci 0000:05:00.0: bridge window [??? 0x00000000 flags 0x0] (subtractive decode)
    Mar 09 06:33:04 ---- kernel: pci 0000:05:00.0: bridge window [??? 0x00000000 flags 0x0] (subtractive decode)
    Mar 09 06:33:04 ---- kernel: pci 0000:05:00.0: bridge window [??? 0x00000000 flags 0x0] (subtractive decode)
    Mar 09 06:33:04 ---- kernel: pci 0000:07:00.0: [1b21:1042] type 00 class 0x0c0330
    Mar 09 06:33:04 ---- kernel: pci 0000:07:00.0: reg 0x10: [mem 0xf7b00000-0xf7b07fff 64bit]
    Mar 09 06:33:04 ---- kernel: pci 0000:07:00.0: PME# supported from D3hot D3cold
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.7: PCI bridge to [bus 07]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.7: bridge window [mem 0xf7b00000-0xf7bfffff]
    Mar 09 06:33:04 ---- kernel: acpi PNP0A08:00: Disabling ASPM (FADT indicates it is unsupported)
    Mar 09 06:33:04 ---- kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15)
    Mar 09 06:33:04 ---- kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *10 11 12 14 15)
    Mar 09 06:33:04 ---- kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 10 *11 12 14 15)
    Mar 09 06:33:04 ---- kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 10 11 12 14 15)
    Mar 09 06:33:04 ---- kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
    Mar 09 06:33:04 ---- kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
    Mar 09 06:33:04 ---- kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs *3 4 5 6 10 11 12 14 15)
    Mar 09 06:33:04 ---- kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 *4 5 6 10 11 12 14 15)
    Mar 09 06:33:04 ---- kernel: ACPI: Enabled 4 GPEs in block 00 to 3F
    Mar 09 06:33:04 ---- kernel: ACPI: \_SB_.PCI0: notify handler is installed
    Mar 09 06:33:04 ---- kernel: Found 1 acpi root devices
    Mar 09 06:33:04 ---- kernel: vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
    Mar 09 06:33:04 ---- kernel: vgaarb: loaded
    Mar 09 06:33:04 ---- kernel: vgaarb: bridge control possible 0000:01:00.0
    Mar 09 06:33:04 ---- kernel: PCI: Using ACPI for IRQ routing
    Mar 09 06:33:04 ---- kernel: PCI: pci_cache_line_size set to 64 bytes
    Mar 09 06:33:04 ---- kernel: e820: reserve RAM buffer [mem 0x0009d800-0x0009ffff]
    Mar 09 06:33:04 ---- kernel: e820: reserve RAM buffer [mem 0xdd74f000-0xdfffffff]
    Mar 09 06:33:04 ---- kernel: e820: reserve RAM buffer [mem 0xde0e0000-0xdfffffff]
    Mar 09 06:33:04 ---- kernel: e820: reserve RAM buffer [mem 0xde97b000-0xdfffffff]
    Mar 09 06:33:04 ---- kernel: e820: reserve RAM buffer [mem 0xdf3f7000-0xdfffffff]
    Mar 09 06:33:04 ---- kernel: e820: reserve RAM buffer [mem 0xdf800000-0xdfffffff]
    Mar 09 06:33:04 ---- kernel: e820: reserve RAM buffer [mem 0x31f000000-0x31fffffff]
    Mar 09 06:33:04 ---- kernel: NetLabel: Initializing
    Mar 09 06:33:04 ---- kernel: NetLabel: domain hash size = 128
    Mar 09 06:33:04 ---- kernel: NetLabel: protocols = UNLABELED CIPSOv4
    Mar 09 06:33:04 ---- kernel: NetLabel: unlabeled traffic allowed by default
    Mar 09 06:33:04 ---- kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
    Mar 09 06:33:04 ---- kernel: hpet0: 8 comparators, 64-bit 14.318180 MHz counter
    Mar 09 06:33:04 ---- kernel: Switched to clocksource hpet
    Mar 09 06:33:04 ---- kernel: pnp: PnP ACPI init
    Mar 09 06:33:04 ---- kernel: ACPI: bus type PNP registered
    Mar 09 06:33:04 ---- kernel: system 00:00: [mem 0xfed40000-0xfed44fff] has been reserved
    Mar 09 06:33:04 ---- kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
    Mar 09 06:33:04 ---- kernel: pnp 00:01: [dma 4]
    Mar 09 06:33:04 ---- kernel: pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
    Mar 09 06:33:04 ---- kernel: pnp 00:02: Plug and Play ACPI device, IDs INT0800 (active)
    Mar 09 06:33:04 ---- kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active)
    Mar 09 06:33:04 ---- kernel: system 00:04: [io 0x0680-0x069f] has been reserved
    Mar 09 06:33:04 ---- kernel: system 00:04: [io 0x1000-0x100f] has been reserved
    Mar 09 06:33:04 ---- kernel: system 00:04: [io 0xffff] has been reserved
    Mar 09 06:33:04 ---- kernel: system 00:04: [io 0xffff] has been reserved
    Mar 09 06:33:04 ---- kernel: system 00:04: [io 0x0400-0x0453] could not be reserved
    Mar 09 06:33:04 ---- kernel: system 00:04: [io 0x0458-0x047f] has been reserved
    Mar 09 06:33:04 ---- kernel: system 00:04: [io 0x0500-0x057f] has been reserved
    Mar 09 06:33:04 ---- kernel: system 00:04: [io 0x164e-0x164f] has been reserved
    Mar 09 06:33:04 ---- kernel: system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
    Mar 09 06:33:04 ---- kernel: pnp 00:05: Plug and Play ACPI device, IDs PNP0b00 (active)
    Mar 09 06:33:04 ---- kernel: system 00:06: [io 0x0454-0x0457] has been reserved
    Mar 09 06:33:04 ---- kernel: system 00:06: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
    Mar 09 06:33:04 ---- kernel: system 00:07: [io 0x0290-0x029f] has been reserved
    Mar 09 06:33:04 ---- kernel: system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
    Mar 09 06:33:04 ---- kernel: system 00:08: [io 0x04d0-0x04d1] has been reserved
    Mar 09 06:33:04 ---- kernel: system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
    Mar 09 06:33:04 ---- kernel: pnp 00:09: Plug and Play ACPI device, IDs PNP0c04 (active)
    Mar 09 06:33:04 ---- kernel: pnp 00:0a: Plug and Play ACPI device, IDs PNP0303 PNP030b (active)
    Mar 09 06:33:04 ---- kernel: system 00:0b: [mem 0xfed1c000-0xfed1ffff] has been reserved
    Mar 09 06:33:04 ---- kernel: system 00:0b: [mem 0xfed10000-0xfed17fff] has been reserved
    Mar 09 06:33:04 ---- kernel: system 00:0b: [mem 0xfed18000-0xfed18fff] has been reserved
    Mar 09 06:33:04 ---- kernel: system 00:0b: [mem 0xfed19000-0xfed19fff] has been reserved
    Mar 09 06:33:04 ---- kernel: system 00:0b: [mem 0xf8000000-0xfbffffff] has been reserved
    Mar 09 06:33:04 ---- kernel: system 00:0b: [mem 0xfed20000-0xfed3ffff] has been reserved
    Mar 09 06:33:04 ---- kernel: system 00:0b: [mem 0xfed90000-0xfed93fff] has been reserved
    Mar 09 06:33:04 ---- kernel: system 00:0b: [mem 0xfed45000-0xfed8ffff] has been reserved
    Mar 09 06:33:04 ---- kernel: system 00:0b: [mem 0xff000000-0xffffffff] has been reserved
    Mar 09 06:33:04 ---- kernel: system 00:0b: [mem 0xfee00000-0xfeefffff] could not be reserved
    Mar 09 06:33:04 ---- kernel: system 00:0b: [mem 0xf0100000-0xf0100fff] has been reserved
    Mar 09 06:33:04 ---- kernel: system 00:0b: Plug and Play ACPI device, IDs PNP0c02 (active)
    Mar 09 06:33:04 ---- kernel: pnp: PnP ACPI: found 12 devices
    Mar 09 06:33:04 ---- kernel: ACPI: bus type PNP unregistered
    Mar 09 06:33:04 ---- kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:01.0: bridge window [io 0xe000-0xefff]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:01.0: bridge window [mem 0xf7e00000-0xf7efffff]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:01.0: bridge window [mem 0xe0000000-0xefffffff 64bit pref]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.0: PCI bridge to [bus 02]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.3: PCI bridge to [bus 03]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.3: bridge window [io 0xd000-0xdfff]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.3: bridge window [mem 0xf7d00000-0xf7dfffff]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.4: PCI bridge to [bus 04]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.4: bridge window [mem 0xf7c00000-0xf7cfffff]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.4: bridge window [mem 0xf0000000-0xf00fffff 64bit pref]
    Mar 09 06:33:04 ---- kernel: pci 0000:05:00.0: PCI bridge to [bus 06]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.5: PCI bridge to [bus 05-06]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.7: PCI bridge to [bus 07]
    Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.7: bridge window [mem 0xf7b00000-0xf7bfffff]
    Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
    Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
    Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
    Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: resource 7 [mem 0x000d0000-0x000d3fff]
    Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: resource 8 [mem 0x000d4000-0x000d7fff]
    Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: resource 9 [mem 0x000d8000-0x000dbfff]
    Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: resource 10 [mem 0x000dc000-0x000dffff]
    Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: resource 11 [mem 0x000e0000-0x000e3fff]
    Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: resource 12 [mem 0x000e4000-0x000e7fff]
    Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: resource 13 [mem 0xe0000000-0xfeafffff]
    Mar 09 06:33:04 ---- kernel: pci_bus 0000:01: resource 0 [io 0xe000-0xefff]
    Mar 09 06:33:04 ---- kernel: pci_bus 0000:01: resource 1 [mem 0xf7e00000-0xf7efffff]
    Mar 09 06:33:04 ---- kernel: pci_bus 0000:01: resource 2 [mem 0xe0000000-0xefffffff 64bit pref]
    Mar 09 06:33:04 ---- kernel: pci_bus 0000:03: resource 0 [io 0xd000-0xdfff]
    Mar 09 06:33:04 ---- kernel: pci_bus 0000:03: resource 1 [mem 0xf7d00000-0xf7dfffff]
    Mar 09 06:33:04 ---- kernel: pci_bus 0000:04: resource 1 [mem 0xf7c00000-0xf7cfffff]
    Mar 09 06:33:04 ---- kernel: pci_bus 0000:04: resource 2 [mem 0xf0000000-0xf00fffff 64bit pref]
    Mar 09 06:33:04 ---- kernel: pci_bus 0000:07: resource 1 [mem 0xf7b00000-0xf7bfffff]
    Mar 09 06:33:04 ---- kernel: NET: Registered protocol family 2
    Mar 09 06:33:04 ---- kernel: TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
    Mar 09 06:33:04 ---- kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
    Mar 09 06:33:04 ---- kernel: TCP: Hash tables configured (established 131072 bind 65536)
    Mar 09 06:33:04 ---- kernel: TCP: reno registered
    Mar 09 06:33:04 ---- kernel: UDP hash table entries: 8192 (order: 6, 262144 bytes)
    Mar 09 06:33:04 ---- kernel: UDP-Lite hash table entries: 8192 (order: 6, 262144 bytes)
    Mar 09 06:33:04 ---- kernel: NET: Registered protocol family 1
    Mar 09 06:33:04 ---- kernel: pci 0000:01:00.0: Boot video device
    Mar 09 06:33:04 ---- kernel: PCI: CLS 64 bytes, default 64
    Mar 09 06:33:04 ---- kernel: Unpacking initramfs...
    Mar 09 06:33:04 ---- kernel: Freeing initrd memory: 3084K (ffff88007fcfd000 - ffff880080000000)
    Mar 09 06:33:04 ---- kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
    Mar 09 06:33:04 ---- kernel: software IO TLB [mem 0xd974f000-0xdd74f000] (64MB) mapped at [ffff8800d974f000-ffff8800dd74efff]
    Mar 09 06:33:04 ---- kernel: Scanning for low memory corruption every 60 seconds
    Mar 09 06:33:04 ---- kernel: audit: initializing netlink socket (disabled)
    Mar 09 06:33:04 ---- kernel: type=2000 audit(1394371982.283:1): initialized
    Mar 09 06:33:04 ---- kernel: HugeTLB registered 2 MB page size, pre-allocated 0 pages
    Mar 09 06:33:04 ---- kernel: zbud: loaded
    Mar 09 06:33:04 ---- kernel: VFS: Disk quotas dquot_6.5.2
    Mar 09 06:33:04 ---- kernel: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
    Mar 09 06:33:04 ---- kernel: msgmni has been set to 23946
    Mar 09 06:33:04 ---- kernel: Key type big_key registered
    Mar 09 06:33:04 ---- kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
    Mar 09 06:33:04 ---- kernel: io scheduler noop registered
    Mar 09 06:33:04 ---- kernel: io scheduler deadline registered
    Mar 09 06:33:04 ---- kernel: io scheduler cfq registered (default)
    Mar 09 06:33:04 ---- kernel: pcieport 0000:00:01.0: irq 40 for MSI/MSI-X
    Mar 09 06:33:04 ---- kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    Mar 09 06:33:04 ---- kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
    Mar 09 06:33:04 ---- kernel: intel_idle: MWAIT substates: 0x1120
    Mar 09 06:33:04 ---- kernel: intel_idle: v0.4 model 0x3A
    Mar 09 06:33:04 ---- kernel: intel_idle: lapic_timer_reliable_states 0xffffffff
    Mar 09 06:33:04 ---- kernel: GHES: HEST is not enabled!
    Mar 09 06:33:04 ---- kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    Mar 09 06:33:04 ---- kernel: Linux agpgart interface v0.103
    Mar 09 06:33:04 ---- kernel: rtc_cmos 00:05: RTC can wake from S4
    Mar 09 06:33:04 ---- kernel: rtc_cmos 00:05: rtc core: registered rtc_cmos as rtc0
    Mar 09 06:33:04 ---- kernel: rtc_cmos 00:05: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
    Mar 09 06:33:04 ---- kernel: Intel P-state driver initializing.
    Mar 09 06:33:04 ---- kernel: Intel pstate controlling: cpu 0
    Mar 09 06:33:04 ---- kernel: Intel pstate controlling: cpu 1
    Mar 09 06:33:04 ---- kernel: Intel pstate controlling: cpu 2
    Mar 09 06:33:04 ---- kernel: Intel pstate controlling: cpu 3
    Mar 09 06:33:04 ---- kernel: drop_monitor: Initializing network drop monitor service
    Mar 09 06:33:04 ---- kernel: TCP: cubic registered
    Mar 09 06:33:04 ---- kernel: NET: Registered protocol family 10
    Mar 09 06:33:04 ---- kernel: NET: Registered protocol family 17
    Mar 09 06:33:04 ---- kernel: Key type dns_resolver registered
    Mar 09 06:33:04 ---- kernel: registered taskstats version 1
    Mar 09 06:33:04 ---- kernel: Magic number: 6:65:584
    Mar 09 06:33:04 ---- kernel: pci_bus 0000:05: hash matches
    Mar 09 06:33:04 ---- kernel: rtc_cmos 00:05: setting system clock to 2014-03-09 13:33:02 UTC (1394371982)
    Mar 09 06:33:04 ---- kernel: PM: Hibernation image not present or could not be loaded.
    Mar 09 06:33:04 ---- kernel: Freeing unused kernel memory: 1128K (ffffffff818d3000 - ffffffff819ed000)
    Mar 09 06:33:04 ---- kernel: Write protecting the kernel read-only data: 8192k
    Mar 09 06:33:04 ---- kernel: Freeing unused kernel memory: 864K (ffff880001528000 - ffff880001600000)
    Mar 09 06:33:04 ---- kernel: Freeing unused kernel memory: 376K (ffff8800017a2000 - ffff880001800000)
    Mar 09 06:33:04 ---- kernel: random: systemd-tmpfile urandom read with 1 bits of entropy available
    Mar 09 06:33:04 ---- systemd-udevd[56]: starting version 210
    Mar 09 06:33:04 ---- kernel: i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
    Mar 09 06:33:04 ---- kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
    Mar 09 06:33:04 ---- kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
    Mar 09 06:33:04 ---- kernel: ACPI: bus type USB registered
    Mar 09 06:33:04 ---- kernel: usbcore: registered new interface driver usbfs
    Mar 09 06:33:04 ---- kernel: usbcore: registered new interface driver hub
    Mar 09 06:33:04 ---- kernel: usbcore: registered new device driver usb
    Mar 09 06:33:04 ---- kernel: SCSI subsystem initialized
    Mar 09 06:33:04 ---- kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    Mar 09 06:33:04 ---- kernel: ehci-pci: EHCI PCI platform driver
    Mar 09 06:33:04 ---- kernel: ehci-pci 0000:00:1a.0: EHCI Host Controller
    Mar 09 06:33:04 ---- kernel: ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
    Mar 09 06:33:04 ---- kernel: ehci-pci 0000:00:1a.0: debug port 2
    Mar 09 06:33:04 ---- kernel: libata version 3.00 loaded.
    Mar 09 06:33:04 ---- kernel: ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
    Mar 09 06:33:04 ---- kernel: ehci-pci 0000:00:1a.0: irq 16, io mem 0xf7f18000
    Mar 09 06:33:04 ---- kernel: ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
    Mar 09 06:33:04 ---- kernel: hub 1-0:1.0: USB hub found
    Mar 09 06:33:04 ---- kernel: hub 1-0:1.0: 2 ports detected
    Mar 09 06:33:04 ---- kernel: ehci-pci 0000:00:1d.0: EHCI Host Controller
    Mar 09 06:33:04 ---- kernel: ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
    Mar 09 06:33:04 ---- kernel: ehci-pci 0000:00:1d.0: debug port 2
    Mar 09 06:33:04 ---- kernel: ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
    Mar 09 06:33:04 ---- kernel: ehci-pci 0000:00:1d.0: irq 23, io mem 0xf7f17000
    Mar 09 06:33:04 ---- kernel: ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
    Mar 09 06:33:04 ---- kernel: hub 2-0:1.0: USB hub found
    Mar 09 06:33:04 ---- kernel: hub 2-0:1.0: 2 ports detected
    Mar 09 06:33:04 ---- kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller
    Mar 09 06:33:04 ---- kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 3
    Mar 09 06:33:04 ---- kernel: xhci_hcd 0000:00:14.0: cache line size of 64 is not supported
    Mar 09 06:33:04 ---- kernel: xhci_hcd 0000:00:14.0: irq 41 for MSI/MSI-X
    Mar 09 06:33:04 ---- kernel: hub 3-0:1.0: USB hub found
    Mar 09 06:33:04 ---- kernel: hub 3-0:1.0: 4 ports detected
    Mar 09 06:33:04 ---- kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller
    Mar 09 06:33:04 ---- kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 4
    Mar 09 06:33:04 ---- kernel: hub 4-0:1.0: USB hub found
    Mar 09 06:33:04 ---- kernel: hub 4-0:1.0: 4 ports detected
    Mar 09 06:33:04 ---- kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
    Mar 09 06:33:04 ---- kernel: ahci 0000:00:1f.2: version 3.0
    Mar 09 06:33:04 ---- kernel: xhci_hcd 0000:07:00.0: xHCI Host Controller
    Mar 09 06:33:04 ---- kernel: xhci_hcd 0000:07:00.0: new USB bus registered, assigned bus number 5
    Mar 09 06:33:04 ---- kernel: ahci 0000:00:1f.2: irq 42 for MSI/MSI-X
    Mar 09 06:33:04 ---- kernel: ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x3f impl SATA mode
    Mar 09 06:33:04 ---- kernel: ahci 0000:00:1f.2: flags: 64bit ncq pm led clo pio slum part ems apst
    Mar 09 06:33:04 ---- kernel: scsi0 : ahci
    Mar 09 06:33:04 ---- kernel: scsi1 : ahci
    Mar 09 06:33:04 ---- kernel: scsi2 : ahci
    Mar 09 06:33:04 ---- kernel: scsi3 : ahci
    Mar 09 06:33:04 ---- kernel: scsi4 : ahci
    Mar 09 06:33:04 ---- kernel: scsi5 : ahci
    Mar 09 06:33:04 ---- kernel: ata1: SATA max UDMA/133 abar m2048@0xf7f16000 port 0xf7f16100 irq 42
    Mar 09 06:33:04 ---- kernel: ata2: SATA max UDMA/133 abar m2048@0xf7f16000 port 0xf7f16180 irq 42
    Mar 09 06:33:04 ---- kernel: ata3: SATA max UDMA/133 abar m2048@0xf7f16000 port 0xf7f16200 irq 42
    Mar 09 06:33:04 ---- kernel: ata4: SATA max UDMA/133 abar m2048@0xf7f16000 port 0xf7f16280 irq 42
    Mar 09 06:33:04 ---- kernel: ata5: SATA max UDMA/133 abar m2048@0xf7f16000 port 0xf7f16300 irq 42
    Mar 09 06:33:04 ---- kernel: ata6: SATA max UDMA/133 abar m2048@0xf7f16000 port 0xf7f16380 irq 42
    Mar 09 06:33:04 ---- kernel: ahci 0000:03:00.0: irq 43 for MSI/MSI-X
    Mar 09 06:33:04 ---- kernel: ahci 0000:03:00.0: SSS flag set, parallel bus scan disabled
    Mar 09 06:33:04 ---- kernel: ahci 0000:03:00.0: AHCI 0001.0200 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
    Mar 09 06:33:04 ---- kernel: ahci 0000:03:00.0: flags: 64bit ncq sntf stag led clo pmp pio slum part ccc sxs
    Mar 09 06:33:04 ---- kernel: scsi6 : ahci
    Mar 09 06:33:04 ---- kernel: scsi7 : ahci
    Mar 09 06:33:04 ---- kernel: ata7: SATA max UDMA/133 abar m512@0xf7d00000 port 0xf7d00100 irq 43
    Mar 09 06:33:04 ---- kernel: ata8: SATA max UDMA/133 abar m512@0xf7d00000 port 0xf7d00180 irq 43
    Mar 09 06:33:04 ---- kernel: xhci_hcd 0000:07:00.0: irq 44 for MSI/MSI-X
    Mar 09 06:33:04 ---- kernel: xhci_hcd 0000:07:00.0: irq 45 for MSI/MSI-X
    Mar 09 06:33:04 ---- kernel: xhci_hcd 0000:07:00.0: irq 46 for MSI/MSI-X
    Mar 09 06:33:04 ---- kernel: xhci_hcd 0000:07:00.0: irq 47 for MSI/MSI-X
    Mar 09 06:33:04 ---- kernel: xhci_hcd 0000:07:00.0: irq 48 for MSI/MSI-X
    Mar 09 06:33:04 ---- kernel: hub 5-0:1.0: USB hub found
    Mar 09 06:33:04 ---- kernel: hub 5-0:1.0: 2 ports detected
    Mar 09 06:33:04 ---- kernel: xhci_hcd 0000:07:00.0: xHCI Host Controller
    Mar 09 06:33:04 ---- kernel: xhci_hcd 0000:07:00.0: new USB bus registered, assigned bus number 6
    Mar 09 06:33:04 ---- kernel: hub 6-0:1.0: USB hub found
    Mar 09 06:33:04 ---- kernel: hub 6-0:1.0: 2 ports detected
    Mar 09 06:33:04 ---- kernel: usb 1-1: new high-speed USB device number 2 using ehci-pci
    Mar 09 06:33:04 ---- kernel: ata1: SATA link down (SStatus 0 SControl 300)
    Mar 09 06:33:04 ---- kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    Mar 09 06:33:04 ---- kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    Mar 09 06:33:04 ---- kernel: ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
    Mar 09 06:33:04 ---- kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
    Mar 09 06:33:04 ---- kernel: ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
    Mar 09 06:33:04 ---- kernel: ata2.00: ATA-8: Corsair CSSD-V64GB2, 2.2, max UDMA/133
    Mar 09 06:33:04 ---- kernel: ata2.00: 125045424 sectors, multi 1: LBA48 NCQ (depth 31/32), AA
    Mar 09 06:33:04 ---- kernel: ata7: SATA link down (SStatus 0 SControl 300)
    Mar 09 06:33:04 ---- kernel: ata5: SATA link down (SStatus 0 SControl 300)
    Mar 09 06:33:04 ---- kernel: ata6: SATA link down (SStatus 0 SControl 300)
    Mar 09 06:33:04 ---- kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    Mar 09 06:33:04 ---- kernel: ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
    Mar 09 06:33:04 ---- kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
    Mar 09 06:33:04 ---- kernel: ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
    Mar 09 06:33:04 ---- kernel: ata2.00: configured for UDMA/133
    Mar 09 06:33:04 ---- kernel: scsi 1:0:0:0: Direct-Access ATA Corsair CSSD-V64 2.2 PQ: 0 ANSI: 5
    Mar 09 06:33:04 ---- kernel: ata4.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
    Mar 09 06:33:04 ---- kernel: ata4.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
    Mar 09 06:33:04 ---- kernel: ata4.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
    Mar 09 06:33:04 ---- kernel: sd 1:0:0:0: [sda] 125045424 512-byte logical blocks: (64.0 GB/59.6 GiB)
    Mar 09 06:33:04 ---- kernel: sd 1:0:0:0: [sda] Write Protect is off
    Mar 09 06:33:04 ---- kernel: sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
    Mar 09 06:33:04 ---- kernel: sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    Mar 09 06:33:04 ---- kernel: ata4.00: ATA-8: WDC WD6400AACS-00G8B1, 05.04C05, max UDMA/133
    Mar 09 06:33:04 ---- kernel: ata4.00: 1250263728 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
    Mar 09 06:33:04 ---- kernel: ata3.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
    Mar 09 06:33:04 ---- kernel: ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
    Mar 09 06:33:04 ---- kernel: ata3.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
    Mar 09 06:33:04 ---- kernel: ata4.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
    Mar 09 06:33:04 ---- kernel: ata4.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
    Mar 09 06:33:04 ---- kernel: ata4.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
    Mar 09 06:33:04 ---- kernel: sda: sda1
    Mar 09 06:33:04 ---- kernel: ata4.00: configured for UDMA/133
    Mar 09 06:33:04 ---- kernel: sd 1:0:0:0: [sda] Attached SCSI disk
    Mar 09 06:33:04 ---- kernel: hub 1-1:1.0: USB hub found
    Mar 09 06:33:04 ---- kernel: hub 1-1:1.0: 6 ports detected
    Mar 09 06:33:04 ---- kernel: ata3.00: ATA-8: SAMSUNG HD103SJ, 1AJ10001, max UDMA/133
    Mar 09 06:33:04 ---- kernel: ata3.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
    Mar 09 06:33:04 ---- kernel: ata3.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
    Mar 09 06:33:04 ---- kernel: ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
    Mar 09 06:33:04 ---- kernel: ata3.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
    Mar 09 06:33:04 ---- kernel: ata3.00: configured for UDMA/133
    Mar 09 06:33:04 ---- kernel: scsi 2:0:0:0: Direct-Access ATA SAMSUNG HD103SJ 1AJ1 PQ: 0 ANSI: 5
    Mar 09 06:33:04 ---- kernel: sd 2:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
    Mar 09 06:33:04 ---- kernel: sd 2:0:0:0: [sdb] Write Protect is off
    Mar 09 06:33:04 ---- kernel: sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00
    Mar 09 06:33:04 ---- kernel: scsi 3:0:0:0: Direct-Access ATA WDC WD6400AACS-0 05.0 PQ: 0 ANSI: 5
    Mar 09 06:33:04 ---- kernel: sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    Mar 09 06:33:04 ---- kernel: sd 3:0:0:0: [sdc] 1250263728 512-byte logical blocks: (640 GB/596 GiB)
    Mar 09 06:33:04 ---- kernel: sd 3:0:0:0: [sdc] Write Protect is off
    Mar 09 06:33:04 ---- kernel: sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
    Mar 09 06:33:04 ---- kernel: sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    Mar 09 06:33:04 ---- kernel: sdc: sdc1 sdc2
    Mar 09 06:33:04 ---- kernel: sd 3:0:0:0: [sdc] Attached SCSI disk
    Mar 09 06:33:04 ---- kernel: usb 2-1: new high-speed USB device number 2 using ehci-pci
    Mar 09 06:33:04 ---- kernel: sdb: sdb1 sdb2
    Mar 09 06:33:04 ---- kernel: sd 2:0:0:0: [sdb] Attached SCSI disk
    Mar 09 06:33:04 ---- kernel: hub 2-1:1.0: USB hub found
    Mar 09 06:33:04 ---- kernel: hub 2-1:1.0: 8 ports detected
    Mar 09 06:33:04 ---- kernel: usb 1-1.1: new high-speed USB device number 3 using ehci-pci
    Mar 09 06:33:04 ---- kernel: ata8: SATA link down (SStatus 0 SControl 300)
    Mar 09 06:33:04 ---- kernel: usb 2-1.5: new low-speed USB device number 3 using ehci-pci
    Mar 09 06:33:04 ---- kernel: tsc: Refined TSC clocksource calibration: 3400.023 MHz
    Mar 09 06:33:04 ---- kernel: hidraw: raw HID events driver (C) Jiri Kosina
    Mar 09 06:33:04 ---- kernel: usbcore: registered new interface driver usbhid
    Mar 09 06:33:04 ---- kernel: usbhid: USB HID core driver
    Mar 09 06:33:04 ---- kernel: input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/input/input1
    Mar 09 06:33:04 ---- kernel: hid-generic 0003:046D:C051.0001: input,hidraw0: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:1d.0-1.5/input0
    Mar 09 06:33:04 ---- kernel: EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
    Mar 09 06:33:04 ---- kernel: random: nonblocking pool is initialized
    Mar 09 06:33:04 ---- systemd[1]: systemd 210 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ +SECCOMP -APPARMOR)
    Mar 09 06:33:04 ---- systemd[1]: Detected architecture 'x86-64'.
    Mar 09 06:33:04 ---- systemd[1]: Set hostname to <---->.
    Mar 09 06:33:04 ---- systemd[1]: Configuration file /etc/systemd/system/netctl@wlp0s26u1u1\x2dXXXXX.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
    Mar 09 06:33:04 ---- systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory.
    Mar 09 06:33:04 ---- systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
    Mar 09 06:33:04 ---- systemd[1]: Started Forward Password Requests to Wall Directory Watch.
    Mar 09 06:33:04 ---- systemd[1]: Expecting device sys-subsystem-net-devices-wlp0s26u1u1.device...
    Mar 09 06:33:04 ---- systemd[1]: Starting Remote File Systems.
    Mar 09 06:33:04 ---- systemd[1]: Reached target Remote File Systems.
    Mar 09 06:33:04 ---- systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
    Mar 09 06:33:04 ---- systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
    Mar 09 06:33:04 ---- systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
    Mar 09 06:33:04 ---- systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
    Mar 09 06:33:04 ---- systemd[1]: Starting Paths.
    Mar 09 06:33:04 ---- systemd[1]: Reached target Paths.
    Mar 09 06:33:04 ---- systemd[1]: Starting Encrypted Volumes.
    Mar 09 06:33:04 ---- systemd[1]: Reached target Encrypted Volumes.
    Mar 09 06:33:04 ---- systemd[1]: Starting Swap.
    Mar 09 06:33:04 ---- systemd[1]: Reached target Swap.
    Mar 09 06:33:04 ---- systemd[1]: Expecting device dev-disk-by\x2duuid-174c1e56\x2de13d\x2d4806\x2db77b\x2dfd36effe9148.device...
    Mar 09 06:33:04 ---- systemd[1]: Expecting device dev-disk-by\x2duuid-7553f5d7\x2deb2c\x2d4f49\x2db9a1\x2d3e1c2850bf5f.device...
    Mar 09 06:33:04 ---- systemd[1]: Starting Root Slice.
    Mar 09 06:33:04 ---- systemd[1]: Created slice Root Slice.
    Mar 09 06:33:04 ---- systemd[1]: Starting User and Session Slice.
    Mar 09 06:33:04 ---- systemd[1]: Created slice User and Session Slice.
    Mar 09 06:33:04 ---- systemd[1]: Starting Device-mapper event daemon FIFOs.
    Mar 09 06:33:04 ---- systemd[1]: Listening on Device-mapper event daemon FIFOs.
    Mar 09 06:33:04 ---- systemd[1]: Starting Delayed Shutdown Socket.
    Mar 09 06:33:04 ---- systemd[1]: Listening on Delayed Shutdown Socket.
    Mar 09 06:33:04 ---- systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
    Mar 09 06:33:04 ---- systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
    Mar 09 06:33:04 ---- systemd[1]: Starting LVM2 metadata daemon socket.
    Mar 09 06:33:04 ---- systemd[1]: Listening on LVM2 metadata daemon socket.
    Mar 09 06:33:04 ---- systemd[1]: Starting udev Kernel Socket.
    Mar 09 06:33:04 ---- systemd[1]: Listening on udev Kernel Socket.
    Mar 09 06:33:04 ---- systemd[1]: Starting udev Control Socket.
    Mar 09 06:33:04 ---- systemd[1]: Listening on udev Control Socket.
    Mar 09 06:33:04 ---- systemd[1]: Starting Journal Socket.
    Mar 09 06:33:04 ---- systemd[1]: Listening on Journal Socket.
    Mar 09 06:33:04 ---- systemd[1]: Starting System Slice.
    Mar 09 06:33:04 ---- systemd[1]: Created slice System Slice.
    Mar 09 06:33:04 ---- systemd[1]: Started File System Check on Root Device.
    Mar 09 06:33:04 ---- systemd[1]: Starting system-systemd\x2dfsck.slice.
    Mar 09 06:33:04 ---- systemd[1]: Created slice system-systemd\x2dfsck.slice.
    Mar 09 06:33:04 ---- systemd[1]: Mounting Temporary Directory...
    Mar 09 06:33:04 ---- systemd[1]: Starting system-netctl.slice.
    Mar 09 06:33:04 ---- systemd[1]: Created slice system-netctl.slice.
    Mar 09 06:33:04 ---- systemd[1]: Starting system-getty.slice.
    Mar 09 06:33:04 ---- systemd[1]: Created slice system-getty.slice.
    Mar 09 06:33:04 ---- systemd[1]: Started Set Up Additional Binary Formats.
    Mar 09 06:33:04 ---- systemd[1]: Starting Load Kernel Modules...
    Mar 09 06:33:04 ---- systemd[1]: Mounting Huge Pages File System...
    Mar 09 06:33:04 ---- systemd[1]: Mounting Debug File System...
    Mar 09 06:33:04 ---- systemd[1]: Starting Apply Kernel Variables...
    Mar 09 06:33:04 ---- systemd[1]: Mounting POSIX Message Queue File System...
    Mar 09 06:33:04 ---- systemd[1]: Starting udev Coldplug all Devices...
    Mar 09 06:33:04 ---- systemd[1]: Starting Create list of required static device nodes for the current kernel...
    Mar 09 06:33:04 ---- systemd[1]: Starting Setup Virtual Console...
    Mar 09 06:33:04 ---- systemd[1]: Starting Journal Service...
    Mar 09 06:33:04 ---- systemd[1]: Started Journal Service.
    Mar 09 06:33:04 ---- kernel: EXT4-fs (sda1): re-mounted. Opts: data=ordered
    Mar 09 06:33:04 ---- kernel: input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input2
    Mar 09 06:33:04 ---- kernel: ACPI: Power Button [PWRB]
    Mar 09 06:33:04 ---- kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
    Mar 09 06:33:04 ---- kernel: ACPI: Power Button [PWRF]
    Mar 09 06:33:04 ---- kernel: AMD IOMMUv2 driver by Joerg Roedel <[email protected]>
    Mar 09 06:33:04 ---- kernel: AMD IOMMUv2 functionality not available on this system
    Mar 09 06:33:04 ---- systemd-journal[136]: Journal started
    Mar 09 06:33:04 ---- systemd[1]: Starting Slices.
    Mar 09 06:33:04 ---- systemd[1]: Reached target Slices.
    Mar 09 06:33:04 ---- systemd[1]: Starting Remount Root and Kernel File Systems...
    Mar 09 06:33:04 ---- systemd[1]: Started Apply Kernel Variables.
    Mar 09 06:33:04 ---- systemd[1]: Started Setup Virtual Console.
    Mar 09 06:33:04 ---- systemd[1]: Mounted Debug File System.
    Mar 09 06:33:04 ---- systemd[1]: Mounted Huge Pages File System.
    Mar 09 06:33:04 ---- systemd[1]: Started udev Coldplug all Devices.
    Mar 09 06:33:04 ---- systemd[1]: Mounted POSIX Message Queue File System.
    Mar 09 06:33:04 ---- systemd[1]: Mounted Temporary Directory.
    Mar 09 06:33:04 ---- systemd[1]: Started Remount Root and Kernel File Systems.
    Mar 09 06:33:04 ---- systemd[1]: Starting Create static device nodes in /dev...
    Mar 09 06:33:04 ---- systemd[1]: Started Create static device nodes in /dev.
    Mar 09 06:33:04 ---- systemd[1]: Starting udev Kernel Device Manager...
    Mar 09 06:33:04 ---- systemd[1]: Starting Local File Systems (Pre).
    Mar 09 06:33:04 ---- systemd[1]: Reached target Local File Systems (Pre).
    Mar 09 06:33:04 ---- systemd[1]: Started udev Kernel Device Manager.
    Mar 09 06:33:04 ---- systemd-udevd[150]: starting version 210
    Mar 09 06:33:04 ---- kernel: fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
    Mar 09 06:33:04 ---- kernel: Disabling lock debugging due to kernel taint
    Mar 09 06:33:04 ---- systemd-modules-load[126]: Inserted module 'fglrx'
    Mar 09 06:33:04 ---- kernel: <6>[fglrx] Maximum main memory to use for locked dma buffers: 11672 MBytes.
    Mar 09 06:33:04 ---- kernel: <6>[fglrx] vendor: 1002 device: 6738 count: 1
    Mar 09 06:33:04 ---- kernel: <6>[fglrx] ioport: bar 4, base 0xe000, size: 0x100
    Mar 09 06:33:04 ---- kernel: <6>[fglrx] Kernel PAT support is enabled
    Mar 09 06:33:04 ---- kernel: <6>[fglrx] module loaded - fglrx 13.25.5 [Dec 6 2013] with 1 minors
    Mar 09 06:33:04 ---- systemd-modules-load[126]: Inserted module 'vboxdrv'
    Mar 09 06:33:04 ---- systemd-modules-load[126]: Inserted module 'vboxnetadp'
    Mar 09 06:33:04 ---- kernel: vboxdrv: Found 4 processor cores.
    Mar 09 06:33:04 ---- kernel: vboxdrv: fAsync=0 offMin=0x179 offMax=0x32f1
    Mar 09 06:33:04 ---- kernel: vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
    Mar 09 06:33:04 ---- kernel: vboxdrv: Successfully loaded version 4.3.8_OSE (interface 0x001a0007).
    Mar 09 06:33:04 ---- systemd-modules-load[126]: Inserted module 'vboxnetflt'
    Mar 09 06:33:04 ---- systemd-modules-load[126]: Inserted module 'vboxpci'
    Mar 09 06:33:04 ---- systemd[1]: Started Load Kernel Modules.
    Mar 09 06:33:04 ---- systemd[1]: Mounted FUSE Control File System.
    Mar 09 06:33:04 ---- systemd[1]: Mounting Configuration File System...
    Mar 09 06:33:04 ---- kernel: vboxpci: IOMMU not found (not registered)
    Mar 09 06:33:04 ---- systemd[1]: Mounted Configuration File System.
    Mar 09 06:33:04 ---- kernel: ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \PMIO 1 (20131115/utaddress-251)
    Mar 09 06:33:04 ---- kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
    Mar 09 06:33:04 ---- kernel: ACPI Warning: 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \GPR2 1 (20131115/utaddress-251)
    Mar 09 06:33:04 ---- kernel: ACPI Warning: 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \GPIO 2 (20131115/utaddress-251)
    Mar 09 06:33:04 ---- kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
    Mar 09 06:33:04 ---- kernel: ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPR2 1 (20131115/utaddress-251)
    Mar 09 06:33:04 ---- kernel: ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIO 2 (20131115/utaddress-251)
    Mar 09 06:33:04 ---- kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
    Mar 09 06:33:04 ---- kernel: lpc_ich: Resource confl

  • Example Fade effect for data change?

    Is there an example of how to use the fade effect when
    transitioning from one record to another in a dataset?
    What I have now is causing a blinking. The old data fades
    out, new data appears then fades in.
    <script type="text/javascript">
    <!-- // special effects - Fade in/out -->
    var fadePOout = new Spry.Effect.Fade('PO',{duration: 1000,
    from: 100, to: 0});
    var fadePOin = new Spry.Effect.Fade('PO',{duration: 1000,
    from: 0, to: 100});
    function observerPO(notificationType, notifier, data) {
    if (notificationType == "onPreLoad") {
    fadePOout.start();
    if (notificationType == "onPostLoad") {
    fadePOin.start();
    dsPO.addObserver(observerPO);
    </script>
    REF: Spry 1.5

    Yes, the example is what I want to happen. Am just not sure
    it can work with a pagedview dataset as the master. Tried very hard
    to follow your directions; Corrected the code in the
    SpryEffects.js. Made the CSS entry for the 'PO' region to have
    opacity:0. Copied your code and changed ds1 to my detail dataset
    (dsPO) (also tried my master dataset, dsPOrders, out of
    frustration). Changed the region name from 'description' to 'PO'
    (which is the name of my region to fade in and out). Added
    onclick="fadeOutContentThenSetRow('{ds_RowID}');" to the master
    dataset record. (Yes, I added it. I still have no clue as to how
    changes from the pagedview master dataset can update a detail
    dataset, but it does.)
    End result is the detail dataset appears as though the CSS
    was not read. I know this because I can see spry:state="loading"
    graphic. Then the data appears. It then disappears and fades in.
    Clicking on a master dataset record repeats the above result.
    Via Firebug am able to see that the function
    fadeOutContentThenSetRow never runs. The function fadeInContent
    runs several times. It appears to run through all events of the
    data region twice (Accounting for why the data is seen
    twice.)

  • How to move the changes from one system to other without using CMS

    Hi
    In our project they are migrating NWDI 6.40 to NWDI 7.0.
    During migration CMS won't be available.
    Could you plesae tell what are the different options are there to move the WebDynpro changes from (NWDS) Development to Quality system and then production system without using CMS server?
    If i will create a development package and import this packgae in Quality package will my new changes also be available in Quality server?
    Thanks & Regards
    Susmita

    Hi Susmita
    I wasn't completely sure, but from your description of your problem, it seemed like you would have access to your DTR during your upgrade. The following solution assumes as much. If this is not the case, you'll need to do things slightly differently, but the solution will still be possible.
    Depending on the scope and size of your changes, it may be practical for your developers to deploy directly from their NetWeaver Developer Studio (or for a designated administrator to install the NWDS and do the same). To do so, from the Development Configurations perspective, create a new NWDS project for each of the DCs you want to deploy. Then right-click the project and choose from one of the deployment options. (Deploy new archive and run will allow you to see if your deployment has taken effect.) When deploying, the target server is the one set up as your J2EE engine in the NWDS properties - you'll consequently have to modify this when the target server for your deployment changes (from QA to production, or vice versa).
    Note that this is only applicable in certain situations, and only as a short term stopgap measure. This sort of practice - developers or administrators deploying haphazardly to servers other than those intended for development - is precisely what the NWDI is designed to prevent (and is one of very few things it's fairly good at doing). For instance, if your QA and production systems are attached as TEST and PROD runtimes systems respectively in your NWDI, a full assembly and subsequent full deployment would usually occur to these servers when deploying with the NWDI. This is a much stronger guarantee of consistency than the build that will be performed within your local NWDS to deploy your changes. (Conversely, the rigidity of the assembly is perhaps the NWDI's greatest design flaw.)
    (Also, Snehal: thanks for the information on the sapmake_util blog. It's not something I've encountered before and looks very useful.)
    James

  • My Carrier Version changed from 14.0 to 13.2?

    I rebooted my phone after a long day at school, and I noticed when I messed around in the settings my carrier version changed from 14.0 to 13.2, if I remembered correctly carrier versions are suppose to go up not down right. Will this effect my iphone at all or no? I'm using an iphone 4 on virgin mobile usa. Thanks and God Bless.

    Here you go.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Attachments:
    121414_Jenny_v1.vi ‏10 KB

  • Outline of After Effects CS4 scripting changes

    Here's a link to a blog post that provides information about the new and changed features in a sparse outline format:
    "After Effects CS4 scripting changes"

    > We use no compression because the LED signs will not take any file that is compressed. I assumed that meant there was no codec involved. Is there a codec applied in CS6, even though it is uncompressed?
    What Rick and I are getting at is: when you render from AE, in the Export Settings dialog there is a codec field; what do you set that to?
    Quick terminology lesson. Codec and compression are not the same thing. When you encode video, you are always using a codec. Most codecs use compression, but some do not. "None" or "Uncompressed" codecs do not use compression.
    After Effects does not add any compression other than what you specifiy in the Export Settings dialog. There should not be a significant difference between the files produced from AE CS4 and AE CS6. AVI, as a format, has not changed in many years. In other words, we know of no difference that would specifically cause this problem.
    If the LED sign software has a problem with an AVI from AE CS6, we need to know the requirements of the LED sign software and how that AVI is failing it. So far all you have told us is "other people say it doesn't work".

  • Problems auto-connecting after sleep & startup (Changed from WPA to WEP)

    Okay, I know there have been several issues similar to this, but after two days of sifting through posts, I still can't resolve this.
    A few days ago I switched my AirPort network security from WPA to WEP-128. This was required to allow my Nintendo DS to connect to the netwrok, by the way. After the change, two similar, but slightly different problems started:
    My 15" PowerBook G4 no longer auto-connects to the network at startup. The network is listed in the drop-down, and connects with no problem when I choose it manually. The computer seems to have no problem re-connecting after waking from sleep, which is odd because...
    My other PowerBook, a 12" G4, won't auto-connect at startup AND won't re-connect after sleep. As above, it has no problem connecting using the Keychain once the network is selected from the drop-down.
    So far I have tried, on both machines:
    - trashing the system airport prefs
    - deleting and resetting the network's keychain entry
    - repairing the keychain (no errors found)
    - turning off some unneeded power mgt options
    - disconnecting USB peripherals
    I have also reloaded the software on both my AirPort Extreme base and my AirPort Express hub, as well as restarting both hubs. I've also made sure that AirPort is at the top of the network connection list.
    Both laptops are running 10.4.3 and have all the latest software updates installed.
    What am I missing?
    Thanks.

    Both of these replies are helpful, in that they help confirm something I figured out this morning, almost accidentally.
    One thing I didn't mention was that during the change from WPA to WEP I changed the network password. Now, I assumed that since the Keychain seemed to be working and I could get on the network manually without needing to enter the password each time, that meant the new password had correctly propagated throughout the system.
    So, this morning I go into the Network settings, switch from Automatic to Preferred, select my network, look at the properties, and notice that somehow it has way too many bullets for that to be the correct password. I re-entered the password and that seems to have solved the problem. The new password I had entered somehow didn't make it into this setting. I guess trashing the network prefs, or renaming the network would have had the same effect.

  • Issue on payroll area which is changing from biweekly to monthly in Mid of

    Dear Experts,
    I have an issue on payroll area which is changing from biweekly to monthly in Mid of the Month.
    One employee was retired on 29th of March, so his payroll area was changed from biweekly to monthly on 29th. For retire we are running the payroll on 8th of every month. When we are running payroll for April he has received only 29th and 30th retire salary, by the time he is not yet retired also.
    In this case the main problem is monthly payroll time is early then biweekly. so the employee is getting retire salary then his regular pay.
    Can you guide me where we can control that monthly payroll area should not be triggered at this movement.
    Thanks
    Chandra

    You can do that but it is not that easy as it sounds if you have to do that over a period of say 10-20 years...lot of operational work!!
    Also say if you load the retiree action one month ahead say on 03/01/2011. And the employee is retiring on  03/29.
    Retire payroll is on 04/08
    Biweekly is on 04/15
    Now you decide to lock the employees after the 1st biweekly check of March...say which was process 14 days before 04/15 would be 04/01. The employee number is locked between 04/01 to 04/15. For 14 days you have locked these employees!!
    What happens if there is adjustment pay...you have to manually go and unlock the employee and lock him after the adjustment check.
    I will let you decide based on the comfort, SAP effort, Operational effort and system maintenance.

Maybe you are looking for

  • Proper way to embed PDF into IE6 or 7

    Does anyone know the official proper way to embed these files? I have seen it this way [code] EMBED src="example1.pdf" width="450" height="450" href="example1.pdf"> /EMBED> [/code] and this way [code] OBJECT CLASSID="clsid:CA8A9780-280D-11CF-A24D-444

  • Problem to find the javax.media.jai package

    hi everyone!! it's not the first time I ask this question, but i have troubles to find javax.media.jai.. I've downloaded the jai 1.1 and everything is fine... However, I have to use classes from the javax.media.jai... I made the import, and it doesn'

  • My firmware has downloaded but wont install the update.

    I recently bought an older macbook, and I went to install updates on it. All but one of them inatstalled. The frimware for some reason will not install. The macbook was purchased in 2009, and is running off of mac os x 10.6.8. im not sure if any of t

  • Can I give a down-payment before financing using the Barclaycard?

    I am looking to buy a mac of about $2000. I know the barclay card as an 18 month 0 APR on purchases over $1600. I am wondering if I can give a $400 downpayment on $2000 mac then finance the remaining $1600? This way I have a lower monthly  payment, i

  • Background events cover overlapping events that are in the foreground.

    Background events cover overlapping events that are in the foreground. When I have 2 overlapping events, clicking on one to bring it to the foreground keeps the text of the background event visable and obfuscates the froeground text. Anyone else seei