Changing From Workgroups to Domain

Hi Alli know this has been floating around the community but i have not seen a answer that explains what i need. Here goes.I am support a company with over 500+ users across 4 sites.At our main site, they have decided to change to a domain instead of a workgroup.i have been told this last minute and i have no experience in domain, we do not have a budget to hire a third party consultant so it has all landed on my head and i am in a little to deep.i do not know what the best way to convert to domain and to be quite honest i wouldnt know how.The issue i face is that 1- i am not experienced to do this migration 2 - our router currently runs as our DHCP & DNS so i will need to workout what we are going to do to insure minimal downtime.basically guy i need a step by step, i understand most of you dont have time to write something like that...

Hey guys!This is a very exiting moment for us, for Spiceworks and hopefully for you!We have released a widget for Spiceworks that will help you to audit Active Directory, Group Policy and Exchange Server. The freewidget is called Netwrix Change Notifier:See what was changed in your Active Directory, Group Policy and Exchange ServerFind out when a specific change was madeFilter out changes by date, object or action typeHere is the widget download page:http://community.spiceworks.com/appcenter/app/plugin_1696And here is a how to that will help you to install itand configure:http://community.spiceworks.com/how_to/116030-how-to-setup-netwrix-change-notifier-widget-for-spicew...Share your thoughts and feedback!

Similar Messages

  • Advice on moving from workgroup to domain for very small network

    Hello all,
    I work for a small company and inherited the part time IT/Operations position and I want to understand the impact of changing from workgroup to domain.  I understand the process and I have set up small test domains before but I want to be certain I
    understand this so I figured I better ask the pros.
    The setup:
    1 Desktop class system, recent i5 quad, 16GB RAM, 1TB HD with Server 2008 R2.  Current roles are File Sharing and WSUS. 
    3 Desktops running Win 7 Home
    1 Desktop with win 7 Pro
    1 Laptop with Vista Home
    1 Laptop with Win 7
    1 Laptop with Win 8 Pro
    I have configured all devices to uses the WSUS for updates as they wanted these managed and this seems to be the easiest way.
    Right now all users have an account on the server that is used to map to their shares.  I know that the home versions cannot join to a domain and with this small of a network I don't want to join any device to a domain as we have only one server and
    it would not be reasonable to add more servers.
    The thing is they want to setup local sharing of calendars and contacts, etc.  I have 2010 exchange server and it is required to be on a domain.
    The Questions:
    Can the domain still "act" as a workgroup and users still connect to the shares and exchange without being joined to the domain?  What is the impact on performance for this server?  Will the home version users still be able to connect to
    the shares (I assume yes) and to the exchange through outlook?  Is there a better way to achieve the workgroup features of exchange without using exchange and not subscribing to Office 365?  We do not have an internet domain name for this business.
    Does this matter for setting up a domain?
    Anything you can think of that I should consider please feel free.
    Thank you all for your advice.

    Hi Paul,
    You are very welcome, I am very glad that my suggestions helped.
    For your first question, in a domain, the Domain Controller clearly has much more tasks to perform than a work group server, while it also has more management options for an administrator to better control his/her client machines.
    In addition, domain acts as a central management solution will reduce the work of the administrator. For an example, under workgroup mode, if we have multiple servers which have shared resources, we need to create the same user
    accounts on each of them, while in a domain, we only need to create accounts once on the DC, then all the accounts can be recognized across the whole domain, no matter how many servers and client machines are within it.
    For the second question, yes, single lable domain name is not recommended, but it is allowed. Single lable domains are supported in
    Exchange Server 2007 Service Pack 1 (SP1) and Exchange 2010, while single label DNS name resolution is also possible.
    However, there are other Microsoft and third-party products which don’t support
    single lable domains. My suggestion is don’t use it while it will cause you trouble.
    More information for you:
    Single-Labeled Domain Names and Exchange 2007 SP1
    http://technet.microsoft.com/en-us/library/cc788134(v=EXCHG.80).aspx
    Microsoft Exchange compatibility with Single Label Domains, Disjointed Namespaces, and Discontiguous Namespaces
    http://support.microsoft.com/kb/2269838
    Help and support for namespaces in Microsoft products including Single Label Domains (SLDs), Disjoint Namespaces, and Discontiguous Namespaces.
    http://support.microsoft.com/gp/gp_namespace_master#tab3
    Providing Single-Label DNS Name Resolution
    http://technet.microsoft.com/en-us/library/cc816610(v=WS.10).aspx
    Regards,
    Amy

  • Changing Server from Workgroup to Domine

    Hai!
    I am using SAP B1 PL 40.
    can u say me what will be the impact in SAP,if i change my  Server from Workgroup to Domine.
    The issue in Detail:
    Now, my server is in workgroup, we planned to bring that into Domine.
    If i do so, wheather it will affect SAP Intallation. I mean, wheather my Hardware Key will change?
    Please tell me, what are all the preventive steps i have to do before changing to domine.
    Regards,
    Thanga Raj.K

    Hi Thanga Raj.K,
    this is the kind of stuff that really needs some thought and I would be more conserned about the preformance and connectivity of my SQL server than the SAP installation.  
    I know if the servername is changed this forces a new hardware key, not sure about the domain change causing the hardware key change, but i would expect it to change and plan the downtime for this accordingly.  You should be able to get some priority on the replacement key from your SAP reseller.
    Personally I would be more conserned about the conectivity of the SQL database when it is moved to the domain.  This could cause some tricky configuration to work correctly.  I would give some serious concideration to building a new server on the domain and installing SQL and SAP. bring it online, test conectivity and move to production replacing the old one.  Once this is done you can move your existing server in to the domain and use it as a test system...
    Thanks,
    Mike

  • Domain change from Local

    Hi all,
    I recently installed a BI test server locally and now what to include it in the domain, can you please point out how I should go about doing this?
    Thanks,
    Iqbal

    Hi Alex:
    Yes, you can change the current installation from Local to Domain based; I don't think there's a document to perform that; do the following:
    1) Create both the Service Account and the <SID>ADM user’s on the DC.
    2) Add the computer has a member of the new domain and logon with the new domain user <SID>ADM to create the domain user profile in the server. The logoff and logon with the local <SID>ADM now copy the current user profile to the new domain based; that is to have all environment variables in the new domain user. You can do this from My Computer (right click)
    3) Add the user’s account from the domain as a member of the local Administrators and any SAP (global and local) groups in the local server.
    4) Shutdown the SAP instance and DB instance; I assume you are running MSSQL Server 2000.
    5) Shutdown the SQL Server services.
    6) Now open Services.msc and search for the SAP services; double click on it and go to Logon tab and change the account from LOCAL to DOMAIN based; I will suggest browsing within the new domain to find the user IDs.
    7) Repeat each step for every SAP instance service and for the SQL services if they are configured with the Local SAP accounts.
    8) Start DB and SAP…
    I think that's all!
    BTW; have a current backup always!!!
    Hope this helps!
    Best Regards,
    Federico G. Babelis
    NetWeaver Certified Consultant
    http://www.gazum.com

  • Has anybody found out how to change the workgroup name in 10.5?

    I have been trying to connect to XP machine shared folders and it is not working.
    I've tried using smb and it gives connection error or says Ithe user has not permission in the machine
    I've started in 10.4 from backup disk and it is working OK.
    I see that in 10.4 it asked for DOMAIN/ Workgroup name , and this option has disappeared in 10.5
    Has anybody found out how to change the workgroup name in 10.5?

    System Preferences - Networking

  • I need to change from Japan App Store to Australia App Store. I get this every time I try using My MacID: "This Apple ID is only valid for purchases in the Japanese iTunes Store. You will be switched to that Store." What next TY. JohnCahill

    I moved from Japan to Australia. I need to change from Japan App Store to the Australian App Store. I get the following message every time I try using My MacID which was set up in Japan: "This Apple ID is only valid for purchases in the Japanese iTunes Store. You will be switched to that Store." At one point... by which path I do not remember... I was instructed to created a new ID. I fill out the new ID forms, but the address is rejected each time... quite confusing. Does it want a new name? But it says I cannot use an apple domain (tag?) even though I guess it has to be an apple address... ? So I have iTunes crdit cards purchansed in Australia, can't spend in AUstralian iTunes Store, get directed back to Japan each time, and can't open a new ID... What am I doing wrong? Thank you in advance.  John. Australia.

    You must have a separate Apple ID registered in the other store along with a valid bank-issued charge card in the other country, and a legal billing address in the other country.
    Sorry... But... You cannot use other countries itunes stores.
    You must be within the Country with a Valid Billing Address and Credit Card for that Country to use the iTunes Store of that Country..
    iTunes Store Terms of Service
    http://www.apple.com/legal/itunes/us/terms.html#SERVICE

  • Changing the Workgroup Name on a Mac

    How do I change the work group name on a MAC?

    From http://docs.info.apple.com/article.html?artnum=107137
    To change the workgroup, follow these steps:
    1. Open Directory Access (/Applications/Utilities/).
    2. Click the padlock to authenticate as an Admin user.
    3. Select SMB from the Services list.
    4. Click Configure.
    5. Select the name of the workgroup from the list, or type the name of the workgroup you wish to create.
    6. Click OK.
    7. Click Apply.
    8. Quit Directory Access.
    Note: Changes in Directory Access may take up to 5 minutes to be recognized by other computers on the network. To force a quicker update, stop and restart Windows File Sharing.

  • Changing a DC in Domain, with Same name and IP

    hey we have a domain with 3DC (srv1, DC Operation Master and GC ; srv2 DC and GC ; and srv3 only DC)
    srv3 is a file server with many shares like //srv3/folder/myfiles 
    so i really want to keep the name and IP!!
    my plan is to degrade the srv3 to normal server and add to a workgroup. 
    Delete it from ad under domain controllers. So my domain only works with my two domain controllers.
    Wait 1 or 2 Days. perhaps do a manuel replication ... so be clear tat the srv3 is really removed from the domain.
    And after all i would take my brand new Server give him same name and ip an add him to the domain. level him up to a dc and i hope all would be fine :)

    Greetings!
    Just demote the DC successfully (No Force Removal!)and check the replication between two domain controllers. If everything were in good condition you can use the same IP and Name in a new server. No need to wait for couple of days.
    Regards.
    Mahdi Tehrani   |  
      |  
    www.mahditehrani.ir
    Please click on Propose As Answer or to mark this post as
    and helpful for other people.
    This posting is provided AS-IS with no warranties, and confers no rights.
    How to query members of 'Local Administrators' group in all computers?

  • Loading a combobox with data from a different domain

    I have filled in a combobox with values from an .asp page and
    have used it
    successfully. The problem is that if the flash file is ran
    from a different
    domain from the load location, the combobox doesn't get
    filled in (as
    apposed to the error if I ran it off of my drive).
    datafeed.asp spits out the appropriate stuff for the AddItems
    function to
    read correctly. (as I has said, it does work). The combobox
    gets filled in
    the development environment (Macromedia Flash MX Professional
    2004) as well
    as flash player.
    But when I upload it to one of my other websites, the data is
    never
    retrieved. Even though that the webserver containing the data
    feed, the
    webserver hosting the flash file and my machine can all read
    datafeed.asp.
    Am I missing a setting that allows a flash file to read data
    from another
    domain?
    The following code has been changed for security reasons. But
    believe me it
    works in its original format.
    myData = new LoadVars();
    myData.onLoad = AddItems;
    myData.load("
    http://www.mydomain.com/datafeed.asp")
    function AddItems() {
    for (i=0; i<numItems; i++) {
    var ProductID = eval("myData.ProductID"+i);
    var ProductName = eval("myData.ProductName"+i);
    var ProductSale = eval("myData.ProductSale"+i);
    var DataProvider = { productid
    roductID, productsale
    roductSale };
    _root.application.chooseproducts.prodlist_cb.addItem(ProductName,
    DataProvider);
    Thank You,
    Julian

    not sure, but this might be what you need...
    //allow loading of files from domain
    System.security.allowDomain("
    http://www.mydomain.com");

  • Any changes in workgroup manager I make are not working!

    First off I know this isn't the place to vent, but I am so sick of all the bugs loaded in the directory system of mac. I think Apple has produced a horrible product and it is always one problem after another. I am experienced with all the other directory systems and I firmly believe Open Directory is the worst!
    Ok, now on to my problem. Our set up includes 6 Mac OS X 10.6 servers. 1 is the Master OD and the others are all replicas. We recently upgrades the servers from 10.5 and ever since I have been having problems with OD. During the upgrades I took an archive of the system, decommissioned the Master and all replicas, then after the upgrade I restored the archive and replicated all the others. Things worked fine for a couple of days. Everyone can login and I could create new users and make changes in workgroup manager. After a couple of days I could no longer make any changes in workgroup manager. I can physically make the changes and create new users and save with no errors, but when I try to log into the file server with the new user or use the changed password, it doesn't work. No errors in the logs that I looked in.
    Here is something weird: When I log into workgroup manager using the local administrator account, I do not see the changes I made in workgroup manager. When I click the unlock button and log in as the diradmin I can see the changes.
    Any, ANY, help would be greatly appreciated. I've been working on this for weeks now. Please don't advise to decommission the Master and rebuild the directory. I already tried that about 10 times with the same result.
    Thanks!

    5 days should be plenty, unless you have a really slow link. Here are a few diagnostics that come to mind to figure out more about what's going on:
    To test to figure out of I'm right about replication being the source of the problem, and if so which replicas aren't up to date, use the "ldapsearch" command to compare the data in the master vs. the various replicas. For instance, to check whether a new user named "fred" has shown up in the server at serverIP, run the command: ldapsearch –LLL –x –h serverIP –b cn=users,dc=masterserver,dc=example,dc=com “(uid=fred)”
    (replace serverIP with your server's address, "dc=masterserver,dc=example,dc=com" with your search base, and fred with the actual account name). Try this on the master and the various replicas, and see which (if any) of the replicas are out of sync.
    If some/all of the replicas are out of sync, check /var/log/slapd.log on the problematic replica(s). It's visible in Server Admin -> servername > Open Directory in sidebar -> Logs in toolbar -> LDAP Log in the View pop-up at the bottom of the window.
    Also, check the replica status in Server Admin -> Open Directory -> Settings -> General.
    Also, on the problematic replica(s), check the replication connections: "sudo lsof -i | grep ldap" should show an entry starting with "slapd" and ending "->masterserver.example.com:ldap (ESTABLISHED)". If it doesn't, you may have some sort of network connectivity/firewall issue.
    If you want to get even more detailed, running "sudo tcpdump host masterserver.example.com and port ldap" on the replica will let you spy on the content of the replication connection.

  • OAS 10.1.2.3, changing the ip and domain on one machine

    Hello
    We are changing the ip and domain of the hardware (hostname remains the same). We have OAS 10.1.2.3 infra, metadata repository (created with MRCA), middle tier on one and the same machine on Aix 5300-10 (I know you are wondering at this). Middle tier is of the Business Intelligence and Forms type. I'm not sure of the procedure. Also the new metadata repository which has to be created, because changing the domain name of identity management with metadata repository according to administrator's guide is not supported, will be on the same machine.
    Should I follow this procedure:
    (1) Deregister the metadata repository from OID with MRCA.
    (2) Change the domain dame and the ip of the identity management.
    (3) Create a new metadata repository and register it with OID.
    (4) Upgrade the metadata repository to 10.1.2.3.
    (5) Install a new middle tier 10.1.0.2 to use the identity management which is on 10.1.2.3
    (6) Upgrade the middle tier to 10.1.2.3.
    Or is there a simpler supported way of changing the ip&domain when everything is all the time only on one machine. If not, is there something not mentioned here which should be taken into account when following the procedure above.
    I'd much appreciate a comment.
    Best Regards

    For midtier is script chgiphost.sh for infra this one doesn'w work cause only let you change IP I belive.
    I think you can try to make a new installation backing up your users from ldap (SSO-OID) and import them to the new installation and try to re-assign the midtiers to the new infra.
    Greetinges.

  • 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

  • Names in Members field under the UNIX Attributes Tab have changed from standard format (i.e. John Doe) to the actual account name (jdoe)

    Hello,
    Names in Members field under the UNIX Attributes Tab have changed from standard format (i.e. John Doe) to the actual account name (jdoe). The only time this happens is if a domain account is deleted and the remnant of the account remains and has to be removed
    manually. However all of the accounts, with the exception of any new ones recently added, now show the account name only. Any ideas on what caused this and how to fix it?
    Thanks :)

    Hi,
    I have not heard from you for some days, currently I am providing the related article for you. Hope this will help you on this matter.
    The UNIX Attributes tab does not appear in the Active Directory Users and Computers MMC snap-in when Server for NIS is installed in the domain
    http://support.microsoft.com/kb/921913/en-us
    Thank you.
    Best regards,
    Steven Song
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Lvanlys.dll Real IFT function change from version 6.1 to version 7

    I am aware that the dll file "lvanalys.dll" changed from LabVIEW version 6.1 to 7. Specifically I have found that the inverse real FFT function not only changed name but _seems_ to have changed in operation.
    The version 6.1 function is called "ReInvFFTCx", the version 7 function is called "InvReNIFFTH". Due to the difficulty in building VIs that use the two different functions from the dll's, I have attached pictures of the output that is obtained from each function. I put the same magnitude and phase vectors into each IFT function and as shown the time domain signals as well as the power spectra are very different. I am hoping that someone that knows about these changes can verify that th
    ere were some functionality changes made and furthermore can shed some light on what was done to test the new function that is included in version 7. The output from the version 6.1 function seems to be much more reasonable to me, especially considering the power spectra vs. the input magnitude spectra.
    Any help on this issue would be greatly appreciated, but for now I am resorting to building my own VIs that use the old function, but this is certainly not convenient considering you have to keep track of he dll, etc.
    Attachments:
    IFT_results_V6.1_vs_V7.pdf ‏21 KB

    I appreciate your response. The symmetry of the input data is clearly an issue that I was not aware of and overlooked. I have done some reading and modified the input signals so that the real portion has even symmetry and the imaginary part has odd symmetry. However, the time domain output is still different between the versions of the dll file and furthermore the power spectrum is still much worse with the version 7 dll than the version 6.1 dll as compared to the input frequency domain signal (see new PDF file attached below).
    I can not be sure that there not something else wrong with my input, but I have to say that it seems like something is very wrong with the version 7 implementation of the Real IFT. I don't understand how NI could have mis
    sed this, but if they did, I would think they would care a great deal about finding it as the FT is so instrumental in so many VIs within LabVIEW.
    Attachments:
    IFT_results_with_Re_and_Im_V6.1_vs_V7.pdf ‏33 KB

  • Objects showing from another forest\domain ...

    Hello Community
        On Windows 2008 Server when I go to Windows Explorer, under "Network"
    in the right pane there are 4 columns:
    Name               Category              WorkGroup            
    Network Location
        It is here that I see my server's names under "Name", Computers under
    "Category", NetBios name under "Workgroup" and FQDN\Forest name under
    "Network Location" which is fine.
        However in addition to my own objects that I see in the right pane of
    Windows Explorer I also see objects from another domain the exists in
    a totally separate forest, how can I see or how could those objects reside
    or be displayed in my forest\domain (unless someone else put them there)?
        Thank you
        Shabeaut

    Hello Susie Long
        There is only one network.
        There are 2 separate forests.
        Each forests has has separate domains.
        Under "Network" not all of the objects from the other domain 
    in the other forest are being displayed, only some of the objects 
    from the other domain in the other forest are being displayed under "Network"
    in this forest.
        That is what is puzzling, are you saying that all of the objects from
    the other domain in the other forest should be visible in this forest and if
    so why aren't all of the objects visible (I was under the impression that
    only the objects in this domain in this forest should be visible under "Network"
    in this forest)?
        Thank you
        Shabeaut

Maybe you are looking for

  • Idoc monitoring tool .

    Guys , Is there any tool to monitor the Inbound and the outbound IDoc s from one server to another server . ?  I know there are transactions to view the Idoc , reprocess it , But i need to know is there any tool kinda thing which monotors all of the

  • Thunderbird PC conflicting with Android Pad when connected home

    With Thunderbird running on PC and android Pad running in another room also connected to my email account (Pad doesn't have Thundrbird as we all know) . Every so often Thunderbird will not connect to email provider and ask for password. Which does no

  • Text/documents in DVD SP

    Hi I want to create a DVD where users will have access to PDF docs as part of the supporting material supplied. I know I can include these in the rom area, but in addition I wonder is there a way of creating a launchable browser style viewer that use

  • Filtering with Smart Collection

    In a next version of LR (2.2 or 3.0) I would love see the collections window improved. When I select two Smart Collections (by Ctrl-clicking) in the menu, LR comes up with all photos that appear in one or both of the collections I selected. When I se

  • Mars 6.0.7 Syslog Requirement for Enterasys Dragon NIDS 7.x

    Apparently the MARS docs are incorrect when it comes to fashioning a syslog message from a Dragon 7.x NIDS. I formatted the message as requested but MARS keeps displaying "Unknown Device Event". The Event IDs are correct but MARS does not recognize t