Creating a resource in ms project

Hi,
We are a Construction company and recently we started using MS project.
We have created three resources cement, sand and aggregates.
Now we want to create a fourth resource named RCC whose unit is CMT which uses cement, sand and aggregates in following weightage;
1.  8 bags of cement
2.  0.9 of aggrgates
3.  0.5 of sand
So if we take cost of cement as 100 dollar per unit and aggregate 15 dollar per unit and sand 5 dollar per unit then the cost of RCC per CMT will be as follow;
100 * 8 + 15 * 0.9 + 5 * 0.5 = 816
Please send us a template if possible.
Thank you. 

Hi Piyush_0,
May I ask what is the reason behind having the fourth resource? Is it for cost purposes or for allocation/assignment (when assigning on CMT you will need 8 cement etc.)
If it is the first option, then you can try to use the standard rate and/or cost per use
If it is the second option then you will need a VBA macro (e.g. after assigning the CMT run the macro so the corresponding cement, sand, aggregates are assigned to the task as well)
Paul 

Similar Messages

  • PS2013 - When creating a new instance of Project Server hangs in 'Waiting for resources' status

    Hi,
    I have one instance of Project Server 2013 fully operational and I tried to duplicate the instance to make some tests. As I know the issue of using the same Content Database of Project Server in the same Server Farm, I used the powershell  backup/restore/dismount
    and mount the content database to change the site IDs to avoid index duplication. The Project server database was a regular SQL backup and restore in another database.
    I created a new Web App in the port 90 as show below.
    Then I included the Content database of Project Server as separated DB from SharePoint for this new SharePoint -acme90 and I tried to create the new instance. The creation hanged in "Waiting for Resources" status.
    To make another check excluding the reuse of the SharePoint-80 I tried to create another instance both in the SharePoint-80 where is the working instance and in the SharePoint-90, everything default and again they all hanged in Waiting for Resource.
    If I try to create the instance using PowerShell I got the following error:
    PS C:\Users\epm_setup> Mount-SPProjectWebInstance -DatabaseName Test_EPM -SiteCo
    llection http://acme02/epm -Lcid 1046
    Mount-SPProjectWebInstance : Cannot find an SPSite object with Id or Url:
    http://acme02/epm.
    At line:1 char:1
    + Mount-SPProjectWebInstance -DatabaseName Test_EPM -SiteCollection
    http://acme02/ ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    ~~~
        + CategoryInfo          : InvalidData: (Microsoft.Offic...ountPwaInstance:
       PSCmdletMountPwaInstance) [Mount-SPProjectWebInstance], SPCmdletPipeBindEx
      ception
        + FullyQualifiedErrorId : Microsoft.Office.Project.Server.Cmdlet.PSCmdletM
       ountPwaInstance
    All SharePoint and Project Server services are running, all App Pools and sites are started at the IIS. I could not find a hanging timer job.
    I cannot stop the hanged process or dismount the instances using Powershell since no instance created.
    How should I solve the hanging status of creation of the instance? As they are in Hyper-V I can go back using one snapshot.
    Thank you.
    Best regards, Ricardo Segawa - Segawas Projetos / Microsoft Partner

    Hi Eric,
    Thank your for your interest in this case.
    I checked for running and crashed PWA jobs and deleted all of them just after restoring the snapshot and tried to create the new instance in the new web app in port 90 (besides the existing and working instance in port 80), but again it hanged in "waiting
    for resources". There is not any timer job hanging, no error in event viewer or in log. So the error is well before working with cloned dbs.
    Answering your questiion, I am working all on 2013. My intention is backup one instance of the port 80 and copy to the instance of port 90, changing of course the url and the index of the content db of SharePoint. The process I used was:
    Create a new web app in port 90, creating a new SharePoint_Content_2 on a
    http://server:90 site.
    Created the top level site called Portal using the Team Site template.
    Create a new content db for new instance of Project Server named EPM_Content_2 using Central Admin.
    Backup content db from port 80 instance of Project Server and restore to this EPM_content_2 using PowerShell cmd.
    Dismounted and mounted this Project Server content db to create new index for existing sites to avoid index conflicts.
    Backup the Project Server DB from port 80 using SQL backup and restored as ProjectWebApp2 db for port 90 instance.
    Tried to create a new instance of Project Server
    http://server:90/pwa on web app of port 90 using the ProjectWebApp2 db and using the same app pool of the other instance. But as in the previous case, it hang out in "Waiting for resources".
    Best regards, Ricardo Segawa - Segawas Projetos / Microsoft Partner

  • PS2013 - Creating a new instance of Project Server does not run and hangs in "Waiting for Resource"

    Hi,
    In my Project Server 2013 environment I created an instance of Project Server which is running in a notebook Hyper-V Windows 2012 Server with 11 GB, 4 threds, 3 GHz, one box configuration with complete version of SQL Server 2012 with SP1, nothing trial.
    PS and SPS 2013 updated with Cumulative Update of Dec 2013.
    I want to create a new empty instance in the same port 80 with a different URL or in the port 90 creating a new web application.
    Whatever option I choose, when I try to create the instance of the Project Server it hangs in "Waiting for Resource" status. No Event Viewer, no hanged timer Jobs, all services running, all pools and sites started and I found out nothing in the
    SharePoint Logs. After every attempt I return the server snapshot to the former state.
    The Project Server and SharePoint continue to work normally.
    Any hints where should I look to solve this issue?
    Thank you.
    Best regards, Ricardo Segawa - Segawas Projetos / Microsoft Partner

    Ricardo,
    so, the only clue I can find in your posting is around the web application.
    if you want a 2nd PWA instance on the same web application (this presums you have one already, working, right?).
    all you really have to do is give it a different "pwa" name - like "Test" or some such and use a unique project database name : Test_ProjectServerData
    there is much more you could do, for isolation into a private content database for example.
    to use a different port, then you need to setup a web application on a different port and proceed as above, selecting that web app to start from.
    if the basic action of new pwa site provision is not working, then it may suggest there is something systemmically wrong with the setup.
    let us know,
    Thanks, Eric S. Pcubed

  • Field for resource allocation in project online

    Hi,
    I'm running Project Pro for Office 365. I'm trying to build some Business Intelligence reports. I would like to make a PivotChart in excel where the X-Axis is the time and the Y-axis is the allocation percentage. I would have a filter to select the resources
    i want to show the bar chart for. That way i can see over the next few weeks/months who is going to be too busy once they go over 100%. How/where do I get the field for a resource allocation in the OData? What is the name for it, is there a list somewhere
    of all the fields one can include into a custom OData?
    Thank you for your help.

    Jim,
    No, using the GUI. Resource Rates are per resource, and will have to be populated when creating the resource.
    However, you can bulk edit the resources in project pro and set the standard rate in one go.
    Cheers,
    Prasanna Adavi, Project MVP
    Blog:
      Podcast:
       Twitter:   
    LinkedIn:
      

  • Resource Assignment without Project Resource Management Module

    Hi Dina,
    We are implementing Oracle projects for one of our customers. The customer does not want to implement Project Resource Management module. Is it possible to assign resources to a project or create a new requirement using the Resources tab in Project screen (HTML page) without implementing the Project Resource Management module. Pls let us know.
    Regards,
    Sri
    Edited by: user12209290 on Nov 18, 2011 9:30 AM

    Hi
    With Project Management you can assign resources to the work plan. Resources might be named people or generic resource by job.
    You can track planned hours by resource versus actual time worked, You can look at roll-up of planned hours across multiple projects for the same resource, or summarization of planned and actual hours using the RBS.
    However, you will not get the functionality of demand published to resource managers, and the search functionality for available person to join the requiring project.
    Dina

  • How to create a resource repository in OSB  ?

    Hi all,
    I am using a set of xsds which needs to be used across projects, instead of copying all the xsds into each project I need to create a repository, which my projects will refer.
    1) Is it possible to create such repository in OSB ?
    2) If so will OSB automatically find the dependncies ?(like warn me if I remove an element used by some other project )
    Thank You

    Hi Arun,
    1) Is it possible to create such repository in OSB ?You may create a separate OSB project for the same, inside same configuration project where you want to use the resources.
    2) If so will OSB automatically find the dependncies ?(like warn me if I remove an element used by some other project )Yes. If any XSD is in use, then OSB will warn you before deleting that.
    Regards,
    Anuj

  • Create a resource filter and add/redefine a property value to a resource?

    Hello,
    I need an advice how to create a resource filter and add a property to a resource. I already created the project and after creating myfilter.java automatically by using the "Service, filter and scheduler taks generation" in my developer studio, there's a filter() method where the filtering has to be implemented. Here I need an example how to read the resource path and add or redefine a property value. (In this case the property value depends on the resource path) So I also need to know, how to get the ressource path. Can anybody please support me with some example code?
    Thanks in advance
    Cheers
    Steffen

    Hi Jaiswin,
    I need to enter 3 formula:
    Setup
    Production
    Teardown
    In PP this is standard but in PP-PI Resource I only see one field 'other formula'.
    How do I enter more then one formula?
    Can it be done in PP-PI?
    Thanks
    Stuart

  • OSB - command line build with resources of coinfiguration project

    Hi!
    I would like to use the com.bea.alsb.core.ConfigExport class to make an OSB build. This class can create the sbconfig.jar for me but without the resources of configuration project (e.g. SMTP server component). If I make a build in eclipse I can set export level (project or resource) in that, but how I could set this in script?
    This is my script:
    <target name="build">
    <echo message="Build ${config.jar} from src"/>
    <available file="${metadata.dir}" type="dir" property="metadata.dir.exists"/>
    <java dir="${eclipse.home}"
    jar="${eclipse.home}/plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar"
    classpath=".;${middleware.home}/modules/com.bea.common.configfwk.ja_1.3.0.0.jar;${osb.home}/lib/sb-kernel-api.jar"
    fork="true"
    failonerror="true"
    maxmemory="1024m">
    <jvmarg value="-Xms512m" />
    <jvmarg value="-Xmx1024m" />
    <jvmarg value="-XX:PermSize=128m" />
    <jvmarg value="-XX:MaxPermSize=512m" />
    <arg line="-data ${workspace.dir}"/>
    <arg line="-application com.bea.alsb.core.ConfigExport"/>
    <arg line="-configProject ${config.project}"/>
    <arg line="-configJar ${config.jar}"/>
    <sysproperty key="weblogic.home" value="${weblogic.home}"/>
    <sysproperty key="osb.home" value="${osb.home}" />
    <sysproperty key="com.bea.plateng.common.util.logging.useJDKlogger" value="true"/>
    </java>
    </target>
    Thanks!
    Viktor

    I think it is not supported through ant script and you may have to contact Oracle Support. Please go through below thread (hisaak's reply) -
    Re: Export OSB configuration jar file using Ant
    Regards,
    Anuj

  • Why Do I get 0h hours for resources after using Resource Levelling in Project 2010?

    Hi,
    We are using MSProject 2010 and Project Server 2010 with Enterprise resources. All resources on all projects in the enterprise are shared resources. We are finding that after resource levelling is applied to the project some resources are only
    being assigned a fraction of their total availability, and in some cases Project will assign 0 hours to a resource for several consecutive weeks even though the resource has capacity for the week the task is scheduled to start. 
    For example: Let's say we have a task that is scheduled to start on 1-20-14. The task is a 112 hours of effort with no constraints and one resource assigned to it. The resource is available 40 hours per week for the next 4 weeks. After resource
    levelling I would expect Project to assign the resource as follows: 40 hours in week 1, 40 hours the next week and 32 hours the next week, for a total of 112 hours. Instead, Project does not assign the resource to the task until week 4 (even
    though the resource has capacity on the start date of the task) and pushes the finish date out. In some weeks the resource has 0h hours showing in the timephased grid on the Resource Usage sheet.  We have experimented with the levelling settings and it
    does not seem to matter which boxes are checked, but following is our preferred settings:
    1. Levelling Calculations set to Manual
    2. Look for overallocations on a day by day basis
    3. Clear levelling values before levelling is CHECKED
    4. Level entire project is selected.
    5. Levelling order is Priority,Standard
    6. Level only within available slack is CHECKED
    7. Levelling can adjust individual assignments on a task is CHECKED
    8. Levelling can create splits in remaining work is UNCHECKED
    9. Level resources with the proposed booking type is UNCHECKED
    10. Level manually scheduled tasks is CHECKED.
    Does anyone have any ideas about why Project is not using the resource's available capacity?
    Thanks, Judy

    Hi Judy,
    Thanks to give us more detail. But actually if you need to level a resource, it means that this resource is overallocated. In your example, since it is not overallocated on the 12weeks task you mention, it means that it should be assigned on another task.
    If not, there would be no need to perform any resource levelling.
    Concerning the fact that levelling assign resource at 0hr per week, this can be absolutely normal.
    Imagine that you have a resource working at 100% on 2 tasks on the same period. imagine also that there is actual work on one of the 2 tasks. Project will level the resource, meaning that it will move ahead the remaining work of one of the task (depending
    on the levelling parameters). But the actual work will not move, thus between the actual work and the moved-foreward remaining work, the resource will be assign at 0hr by time period on the splitted task.
    Please check all the task of the levelled resource and actual work.
    See in my example below:
    Hope this helps.
    Guillaume Rouyre - MBA, MCP, MCTS

  • When Budget Cost Resources is assigned Project Summary Progress is Disabled

    When i create a Budget Cost Resource > assigned this resource to the project summary task > input the value, the "Summary Progress" indicator Bar on the Gantt chart, in project center for example, disappears. I remove the budget resource
    and the progress bar reappears. I have searched extensively and find no info. I can't believe this is intended.
    working with project professional client and server 2013 Dec 2013 CU and client hotfix applied 
    thanks in advance

    Answered on the LinkedIn Microsoft Project Users Group query.

  • Startx on a vmware is throwing a "failed to create screen resources"

    The Bottom line error is:
    Fatal server error:
    [ 1431.076] (EE) failed to create screen resources(EE)
    I am trying to get a browsers running on my new Arch Linux, so I can cut and paste better for questions. I have installed xorg, chromium, firefox. If I try and start "startx", it say the server did not start. I think it is the failed to create screen resources.
    I have edit the video settings to give it 32meg of memory. Also I hack the .vmx file to enable the 3d opttion. I have installed all the vmtools (open version) Again, new to Arch Linux so I sure it is something stupid.
    Not sure if it helps but here are the errors when I try and run the browsers.
    chromium
    [320:320:1121/142755:Error:browser_main_loop.cc(209) Gtk: cannot open display:
    firefox
    (process:354): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
    Error: no display specified
    Entire log Xorg.0.log
    [ 1430.963]
    X.Org X Server 1.16.2
    Release Date: 2014-11-10
    [ 1430.965] X Protocol Version 11, Revision 0
    [ 1430.965] Build Operating System: Linux 3.17.2-1-ARCH x86_64
    [ 1430.967] Current Operating System: Linux PingBuild 3.17.3-1-ARCH #1 SMP PREEMPT Fri Nov 14 23:13:48 CET 2014 x86_64
    [ 1430.967] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=36544952-8a9a-41c9-b169-87189310b752 rw quiet
    [ 1430.969] Build Date: 10 November 2014 07:52:13PM
    [ 1430.970]
    [ 1430.970] Current version of pixman: 0.32.6
    [ 1430.972] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 1430.972] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 1430.975] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Nov 21 12:53:21 2014
    [ 1430.976] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
    [ 1430.976] (==) No Layout section. Using the first Screen section.
    [ 1430.976] (==) No screen section available. Using defaults.
    [ 1430.976] (**) |-->Screen "Default Screen Section" (0)
    [ 1430.976] (**) | |-->Monitor "<default monitor>"
    [ 1430.976] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 1430.976] (==) Automatically adding devices
    [ 1430.976] (==) Automatically enabling devices
    [ 1430.976] (==) Automatically adding GPU devices
    [ 1430.976] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
    [ 1430.976] Entry deleted from font path.
    [ 1430.976] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/OTF/,
    /usr/share/fonts/100dpi/,
    /usr/share/fonts/75dpi/
    [ 1430.976] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 1430.976] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 1430.976] (II) Loader magic: 0x818d80
    [ 1430.976] (II) Module ABI versions:
    [ 1430.976] X.Org ANSI C Emulation: 0.4
    [ 1430.976] X.Org Video Driver: 18.0
    [ 1430.976] X.Org XInput driver : 21.0
    [ 1430.976] X.Org Server Extension : 8.0
    [ 1430.979] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c1
    [ 1430.979] (II) xfree86: Adding drm device (/dev/dri/card0)
    [ 1430.983] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 8 paused 0
    [ 1431.010] (--) PCI:*(0:0:15:0) 15ad:0405:15ad:0405 rev 0, Mem @ 0xd8000000/67108864, 0xd0800000/8388608, I/O @ 0x000010d0/16, BIOS @ 0x????????/32768
    [ 1431.010] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 1431.010] (II) LoadModule: "glx"
    [ 1431.011] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 1431.016] (II) Module glx: vendor="X.Org Foundation"
    [ 1431.016] compiled for 1.16.2, module version = 1.0.0
    [ 1431.016] ABI class: X.Org Server Extension, version 8.0
    [ 1431.016] (==) AIGLX enabled
    [ 1431.016] (==) Matched vmware as autoconfigured driver 0
    [ 1431.016] (==) Matched vmware as autoconfigured driver 1
    [ 1431.016] (==) Matched modesetting as autoconfigured driver 2
    [ 1431.016] (==) Matched fbdev as autoconfigured driver 3
    [ 1431.016] (==) Matched vesa as autoconfigured driver 4
    [ 1431.016] (==) Assigned the driver to the xf86ConfigLayout
    [ 1431.016] (II) LoadModule: "vmware"
    [ 1431.017] (II) Loading /usr/lib/xorg/modules/drivers/vmware_drv.so
    [ 1431.044] (II) Module vmware: vendor="X.Org Foundation"
    [ 1431.044] compiled for 1.16.0, module version = 13.0.2
    [ 1431.044] Module class: X.Org Video Driver
    [ 1431.044] ABI class: X.Org Video Driver, version 18.0
    [ 1431.044] (II) LoadModule: "modesetting"
    [ 1431.044] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
    [ 1431.044] (II) Module modesetting: vendor="X.Org Foundation"
    [ 1431.044] compiled for 1.16.0, module version = 0.9.0
    [ 1431.044] Module class: X.Org Video Driver
    [ 1431.044] ABI class: X.Org Video Driver, version 18.0
    [ 1431.044] (II) LoadModule: "fbdev"
    [ 1431.045] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
    [ 1431.045] (II) Module fbdev: vendor="X.Org Foundation"
    [ 1431.045] compiled for 1.16.0, module version = 0.4.4
    [ 1431.045] Module class: X.Org Video Driver
    [ 1431.045] ABI class: X.Org Video Driver, version 18.0
    [ 1431.045] (II) LoadModule: "vesa"
    [ 1431.045] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
    [ 1431.045] (II) Module vesa: vendor="X.Org Foundation"
    [ 1431.045] compiled for 1.16.0, module version = 2.3.2
    [ 1431.045] Module class: X.Org Video Driver
    [ 1431.045] ABI class: X.Org Video Driver, version 18.0
    [ 1431.045] (II) vmware: driver for VMware SVGA: vmware0405, vmware0710
    [ 1431.045] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
    [ 1431.045] (II) FBDEV: driver for framebuffer: fbdev
    [ 1431.045] (II) VESA: driver for VESA chipsets: vesa
    [ 1431.045] (++) using VT number 1
    [ 1431.045] (--) controlling tty is VT number 1, auto-enabling KeepTty
    [ 1431.045] (WW) Falling back to old probe method for modesetting
    [ 1431.045] (WW) Falling back to old probe method for fbdev
    [ 1431.045] (II) Loading sub module "fbdevhw"
    [ 1431.045] (II) LoadModule: "fbdevhw"
    [ 1431.046] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
    [ 1431.046] (II) Module fbdevhw: vendor="X.Org Foundation"
    [ 1431.046] compiled for 1.16.2, module version = 0.0.2
    [ 1431.046] ABI class: X.Org Video Driver, version 18.0
    [ 1431.046] (WW) Falling back to old probe method for vesa
    [ 1431.046] (II) vmware(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 1431.046] (--) vmware(0): DRM driver version is 2.6.1
    [ 1431.046] (==) vmware(0): Depth 24, (--) framebuffer bpp 32
    [ 1431.046] (==) vmware(0): RGB weight 888
    [ 1431.046] (==) vmware(0): Default visual is TrueColor
    [ 1431.046] (--) vmware(0): Min width 1, Max Width 8192.
    [ 1431.046] (--) vmware(0): Min height 1, Max Height 8192.
    [ 1431.047] (II) vmware(0): Output Virtual1 has no monitor section
    [ 1431.047] (II) vmware(0): Output Virtual2 has no monitor section
    [ 1431.047] (II) vmware(0): Output Virtual3 has no monitor section
    [ 1431.048] (II) vmware(0): Output Virtual4 has no monitor section
    [ 1431.048] (II) vmware(0): Output Virtual5 has no monitor section
    [ 1431.048] (II) vmware(0): Output Virtual6 has no monitor section
    [ 1431.048] (II) vmware(0): Output Virtual7 has no monitor section
    [ 1431.048] (II) vmware(0): Output Virtual8 has no monitor section
    [ 1431.048] (II) vmware(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 489 492 525 -hsync -vsync (31.5 kHz e)
    [ 1431.048] (II) vmware(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 1431.048] (II) vmware(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 1431.048] (II) vmware(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 1431.048] (II) vmware(0): Modeline "1280x768"x59.9 79.50 1280 1344 1472 1664 768 771 778 798 -hsync +vsync (47.8 kHz e)
    [ 1431.048] (II) vmware(0): Modeline "1280x800"x59.8 83.50 1280 1352 1480 1680 800 803 809 831 +hsync -vsync (49.7 kHz e)
    [ 1431.048] (II) vmware(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1360x768"x60.0 85.50 1360 1424 1536 1792 768 771 777 795 +hsync +vsync (47.7 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1400x1050"x60.0 121.75 1400 1488 1632 1864 1050 1053 1057 1089 -hsync +vsync (65.3 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1440x900"x59.9 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1792x1344"x60.0 204.75 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync (83.6 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1856x1392"x60.0 218.25 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync (86.3 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1920x1200"x59.9 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync (74.6 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1920x1440"x60.0 234.00 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync (90.0 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "2560x1600"x60.0 348.50 2560 2752 3032 3504 1600 1603 1609 1658 -hsync +vsync (99.5 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "800x600"x60.0 42.75 800 850 900 950 600 650 700 750 -hsync +vsync (45.0 kHz eP)
    [ 1431.049] (II) vmware(0): Printing probed modes for output Virtual1
    [ 1431.049] (II) vmware(0): Modeline "800x600"x60.0 42.75 800 850 900 950 600 650 700 750 -hsync +vsync (45.0 kHz eP)
    [ 1431.049] (II) vmware(0): Modeline "2560x1600"x60.0 348.50 2560 2752 3032 3504 1600 1603 1609 1658 -hsync +vsync (99.5 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1920x1440"x60.0 234.00 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync (90.0 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1856x1392"x60.0 218.25 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync (86.3 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1792x1344"x60.0 204.75 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync (83.6 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1920x1200"x59.9 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync (74.6 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1400x1050"x60.0 121.75 1400 1488 1632 1864 1050 1053 1057 1089 -hsync +vsync (65.3 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1440x900"x59.9 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1360x768"x60.0 85.50 1360 1424 1536 1792 768 771 777 795 +hsync +vsync (47.7 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1280x800"x59.8 83.50 1280 1352 1480 1680 800 803 809 831 +hsync -vsync (49.7 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1280x768"x59.9 79.50 1280 1344 1472 1664 768 771 778 798 -hsync +vsync (47.8 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 489 492 525 -hsync -vsync (31.5 kHz e)
    [ 1431.049] (II) vmware(0): EDID for output Virtual2
    [ 1431.049] (II) vmware(0): EDID for output Virtual3
    [ 1431.049] (II) vmware(0): EDID for output Virtual4
    [ 1431.049] (II) vmware(0): EDID for output Virtual5
    [ 1431.049] (II) vmware(0): EDID for output Virtual6
    [ 1431.049] (II) vmware(0): EDID for output Virtual7
    [ 1431.049] (II) vmware(0): EDID for output Virtual8
    [ 1431.049] (II) vmware(0): Output Virtual1 connected
    [ 1431.049] (II) vmware(0): Output Virtual2 disconnected
    [ 1431.049] (II) vmware(0): Output Virtual3 disconnected
    [ 1431.049] (II) vmware(0): Output Virtual4 disconnected
    [ 1431.049] (II) vmware(0): Output Virtual5 disconnected
    [ 1431.049] (II) vmware(0): Output Virtual6 disconnected
    [ 1431.049] (II) vmware(0): Output Virtual7 disconnected
    [ 1431.049] (II) vmware(0): Output Virtual8 disconnected
    [ 1431.049] (II) vmware(0): Using exact sizes for initial modes
    [ 1431.049] (II) vmware(0): Output Virtual1 using initial mode 800x600
    [ 1431.049] (II) vmware(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [ 1431.049] (==) vmware(0): DPI set to (96, 96)
    [ 1431.049] (II) Loading sub module "fb"
    [ 1431.049] (II) LoadModule: "fb"
    [ 1431.049] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 1431.050] (II) Module fb: vendor="X.Org Foundation"
    [ 1431.050] compiled for 1.16.2, module version = 1.0.0
    [ 1431.050] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 1431.050] (II) Loading sub module "dri2"
    [ 1431.050] (II) LoadModule: "dri2"
    [ 1431.050] (II) Module "dri2" already built-in
    [ 1431.050] (II) UnloadModule: "modesetting"
    [ 1431.050] (II) Unloading modesetting
    [ 1431.050] (II) UnloadModule: "fbdev"
    [ 1431.050] (II) Unloading fbdev
    [ 1431.050] (II) UnloadSubModule: "fbdevhw"
    [ 1431.050] (II) Unloading fbdevhw
    [ 1431.050] (II) UnloadModule: "vesa"
    [ 1431.050] (II) Unloading vesa
    [ 1431.050] (==) Depth 24 pixmap format is 32 bpp
    [ 1431.050] (II) vmware(0): Initialized VMWARE_CTRL extension version 0.2
    [ 1431.064] (II) vmware(0): Gallium3D XA version: 2.2.0.
    [ 1431.064] (II) vmware(0): Path of drm device is "/dev/dri/card0".
    [ 1431.064] (II) vmware(0): [DRI2] Setup complete
    [ 1431.064] (II) vmware(0): [DRI2] DRI driver: vmwgfx
    [ 1431.064] (--) vmware(0): Render acceleration is enabled.
    [ 1431.064] (==) vmware(0): Rendercheck mode is disabled.
    [ 1431.064] (--) vmware(0): Direct rendering (3D) is enabled.
    [ 1431.064] (==) vmware(0): Direct presents are disabled.
    [ 1431.064] (==) vmware(0): Hardware only presents are disabled.
    [ 1431.064] (==) vmware(0): Backing store enabled
    [ 1431.064] (==) vmware(0): Silken mouse enabled
    [ 1431.064] (II) vmware(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 1431.064] (==) vmware(0): DPMS enabled
    [ 1431.064] (--) RandR disabled
    [ 1431.075] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
    [ 1431.075] (II) AIGLX: enabled GLX_ARB_create_context
    [ 1431.075] (II) AIGLX: enabled GLX_ARB_create_context_profile
    [ 1431.075] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
    [ 1431.075] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
    [ 1431.075] (II) AIGLX: enabled GLX_ARB_fbconfig_float
    [ 1431.075] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
    [ 1431.075] (II) AIGLX: Loaded and initialized vmwgfx
    [ 1431.075] (II) GLX: Initialized DRI2 GL provider for screen 0
    [ 1431.076] (EE)
    Fatal server error:
    [ 1431.076] (EE) failed to create screen resources(EE)
    [ 1431.076] (EE)
    Please consult the The X.Org Foundation support
    at http://wiki.x.org
    for help.
    [ 1431.076] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
    [ 1431.076] (EE)
    [ 1431.076] (II) AIGLX: Suspending AIGLX clients for VT switch
    [ 1431.076] (WW) vmware(0): drmDropMaster failed: Invalid argument
    [ 1431.079] (EE) Server terminated with error (1). Closing log file.
    Journal since boot
    -- Logs begin at Wed 2014-11-19 16:23:50 CST, end at Fri 2014-11-21 14:25:54 CST. --
    Nov 21 14:17:03 PingBuild kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xfeff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:00.0: [8086:7190] type 00 class 0x060000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:01.0: [8086:7191] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.0: [8086:7110] type 00 class 0x060100
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.1: [8086:7111] type 00 class 0x01018a
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.1: reg 0x20: [io 0x10c0-0x10cf]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.1: legacy IDE quirk: reg 0x10: [io 0x01f0-0x01f7]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.1: legacy IDE quirk: reg 0x14: [io 0x03f6]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.1: legacy IDE quirk: reg 0x18: [io 0x0170-0x0177]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.1: legacy IDE quirk: reg 0x1c: [io 0x0376]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.3: [8086:7113] type 00 class 0x068000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.3: quirk: [io 0x1000-0x103f] claimed by PIIX4 ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.3: quirk: [io 0x1040-0x104f] claimed by PIIX4 SMB
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.7: [15ad:0740] type 00 class 0x088000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.7: reg 0x10: [io 0x1080-0x10bf]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.7: reg 0x14: [mem 0xd0000000-0xd0001fff 64bit]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:0f.0: [15ad:0405] type 00 class 0x030000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:0f.0: reg 0x10: [io 0x10d0-0x10df]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:0f.0: reg 0x14: [mem 0xd8000000-0xdbffffff pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:0f.0: reg 0x18: [mem 0xd0800000-0xd0ffffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:0f.0: reg 0x30: [mem 0x00000000-0x00007fff pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:10.0: [1000:0030] type 00 class 0x010000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:10.0: reg 0x10: [io 0x1400-0x14ff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:10.0: reg 0x14: [mem 0xd0040000-0xd005ffff 64bit]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:10.0: reg 0x1c: [mem 0xd0020000-0xd003ffff 64bit]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:10.0: reg 0x30: [mem 0x00000000-0x00003fff pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: [15ad:0790] type 01 class 0x060401
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.0: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.0: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.0: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.1: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.1: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.1: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [32] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [33] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [34] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [35] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [36] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [37] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [38] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [39] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [40] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [41] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [42] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [43] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [44] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [45] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [46] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [47] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [48] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [49] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [50] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [51] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [52] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [53] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [54] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [55] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [56] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [57] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [58] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [59] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [60] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [61] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [62] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [63] registered
    Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: [8086:100f] type 00 class 0x020000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: reg 0x10: [mem 0xd1020000-0xd103ffff 64bit]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: reg 0x18: [mem 0xd1000000-0xd100ffff 64bit]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: reg 0x20: [io 0x2000-0x203f]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: PCI bridge to [bus 02] (subtractive decode)
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [io 0x2000-0x3fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0xd1000000-0xd23fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0xdc400000-0xdc9fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0x000cc000-0x000cffff] (subtractive decode)
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0x000d0000-0x000d3fff] (subtractive decode)
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0x000d4000-0x000d7fff] (subtractive decode)
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0x000d8000-0x000dbfff] (subtractive decode)
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0xc0000000-0xfebfffff] (subtractive decode)
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [io 0x0d00-0xfeff] (subtractive decode)
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: PCI bridge to [bus 03]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: bridge window [io 0x4000-0x4fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: bridge window [mem 0xd2400000-0xd24fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: bridge window [mem 0xd4400000-0xd44fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: PCI bridge to [bus 04]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: bridge window [io 0x8000-0x8fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: bridge window [mem 0xd2800000-0xd28fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: bridge window [mem 0xd4800000-0xd48fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: PCI bridge to [bus 05]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: bridge window [io 0xc000-0xcfff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: bridge window [mem 0xd2c00000-0xd2cfffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: bridge window [mem 0xdcb00000-0xdcbfffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: PCI bridge to [bus 06]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: bridge window [mem 0xd3000000-0xd30fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: bridge window [mem 0xdcd00000-0xdcdfffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: PCI bridge to [bus 07]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: bridge window [mem 0xd3400000-0xd34fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: bridge window [mem 0xdcf00000-0xdcffffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: PCI bridge to [bus 08]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: bridge window [mem 0xd3800000-0xd38fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: bridge window [mem 0xdd100000-0xdd1fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: PCI bridge to [bus 09]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: bridge window [mem 0xd3c00000-0xd3cfffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: bridge window [mem 0xdd300000-0xdd3fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: PCI bridge to [bus 0a]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: bridge window [mem 0xd4000000-0xd40fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: bridge window [mem 0xdd500000-0xdd5fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: PCI bridge to [bus 0b]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: bridge window [io 0x5000-0x5fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: bridge window [mem 0xd2500000-0xd25fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: bridge window [mem 0xd4500000-0xd45fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: PCI bridge to [bus 0c]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: bridge window [io 0x9000-0x9fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: bridge window [mem 0xd2900000-0xd29fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: bridge window [mem 0xd4900000-0xd49fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: PCI bridge to [bus 0d]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: bridge window [io 0xd000-0xdfff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: bridge window [mem 0xd2d00000-0xd2dfffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: bridge window [mem 0xd4b00000-0xd4bfffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: PCI bridge to [bus 0e]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: bridge window [mem 0xd3100000-0xd31fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: bridge window [mem 0xd4d00000-0xd4dfffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: PCI bridge to [bus 0f]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: bridge window [mem 0xd3500000-0xd35fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: bridge window [mem 0xd4f00000-0xd4ffffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: PCI bridge to [bus 10]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: bridge window [mem 0xd3900000-0xd39fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: bridge window [mem 0xd5100000-0xd51fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: PCI bridge to [bus 11]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: bridge window [mem 0xd3d00000-0xd3dfffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: bridge window [mem 0xd5300000-0xd53fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: PCI bridge to [bus 12]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: bridge window [mem 0xd4100000-0xd41fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: bridge window [mem 0xd5500000-0xd55fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: PCI bridge to [bus 13]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: bridge window [io 0x6000-0x6fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: bridge window [mem 0xd2600000-0xd26fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: bridge window [mem 0xd4600000-0xd46fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: PCI bridge to [bus 14]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: bridge window [io 0xa000-0xafff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: bridge window [mem 0xd2a00000-0xd2afffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: bridge window [mem 0xdca00000-0xdcafffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: PCI bridge to [bus 15]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: bridge window [io 0xe000-0xefff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: bridge window [mem 0xd2e00000-0xd2efffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: bridge window [mem 0xdcc00000-0xdccfffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: PCI bridge to [bus 16]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: bridge window [mem 0xd3200000-0xd32fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: bridge window [mem 0xdce00000-0xdcefffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: PCI bridge to [bus 17]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: bridge window [mem 0xd3600000-0xd36fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: bridge window [mem 0xdd000000-0xdd0fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: PCI bridge to [bus 18]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: bridge window [mem 0xd3a00000-0xd3afffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: bridge window [mem 0xdd200000-0xdd2fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: PCI bridge to [bus 19]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: bridge window [mem 0xd3e00000-0xd3efffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: bridge window [mem 0xdd400000-0xdd4fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: PCI bridge to [bus 1a]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: bridge window [mem 0xd4200000-0xd42fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: bridge window [mem 0xdd600000-0xdd6fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.0: PCI bridge to [bus 1b]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.0: bridge window [io 0x7000-0x7fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.0: bridge window [mem 0xd2700000-0xd27fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.0: bridge window [mem 0xd4700000-0xd47fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.1: PCI bridge to [bus 1c]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.1: bridge window [io 0xb000-0xbfff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.1: bridge window [mem 0xd2b00000-0xd2bfffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.1: bridge window [mem 0xd4a00000-0xd4afffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: PCI bridge to [bus 1d]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: bridge window [io 0xf000-0xffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: bridge window [mem 0xd2f00000-0xd2ffffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: bridge window [mem 0xd4c00000-0xd4cfffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: PCI bridge to [bus 1e]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: bridge window [mem 0xd3300000-0xd33fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: bridge window [mem 0xd4e00000-0xd4efffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: PCI bridge to [bus 1f]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: bridge window [mem 0xd3700000-0xd37fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: bridge window [mem 0xd5000000-0xd50fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: PCI bridge to [bus 20]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: bridge window [mem 0xd3b00000-0xd3bfffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: bridge window [mem 0xd5200000-0xd52fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: PCI bridge to [bus 21]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: bridge window [mem 0xd3f00000-0xd3ffffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: bridge window [mem 0xd5400000-0xd54fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: PCI bridge to [bus 22]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: bridge window [mem 0xd4300000-0xd43fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: bridge window [mem 0xd5600000-0xd56fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *9 10 11 14 15)
    Nov 21 14:17:03 PingBuild kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 *11 14 15)
    Nov 21 14:17:03 PingBuild kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 *10 11 14 15)
    Nov 21 14:17:03 PingBuild kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 11 14 15) *0, disabled.
    Nov 21 14:17:03 PingBuild kernel: ACPI: Enabled 2 GPEs in block 00 to 0F
    Nov 21 14:17:03 PingBuild kernel: vgaarb: setting as boot device: PCI:0000:00:0f.0
    Nov 21 14:17:03 PingBuild kernel: vgaarb: device added: PCI:0000:00:0f.0,decodes=io+mem,owns=io+mem,locks=none
    Nov 21 14:17:03 PingBuild kernel: vgaarb: loaded
    Nov 21 14:17:03 PingBuild kernel: vgaarb: bridge control possible 0000:00:0f.0
    Nov 21 14:17:03 PingBuild kernel: PCI: Using ACPI for IRQ routing
    Nov 21 14:17:03 PingBuild kernel: PCI: pci_cache_line_size set to 64 bytes
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: can't claim BAR 13 [io 0xf000-0xffff]: no compatible bridge window
    Nov 21 14:17:03 PingBuild kernel: e820: reserve RAM buffer [mem 0x0009f800-0x0009ffff]
    Nov 21 14:17:03 PingBuild kernel: e820: reserve RAM buffer [mem 0xbfef0000-0xbfffffff]
    Nov 21 14:17:03 PingBuild kernel: NetLabel: Initializing
    Nov 21 14:17:03 PingBuild kernel: NetLabel: domain hash size = 128
    Nov 21 14:17:03 PingBuild kernel: NetLabel: protocols = UNLABELED CIPSOv4
    Nov 21 14:17:03 PingBuild kernel: NetLabel: unlabeled traffic allowed by default
    Nov 21 14:17:03 PingBuild kernel: HPET: 16 timers in total, 0 timers will be used for per-cpu timer
    Nov 21 14:17:03 PingBuild kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
    Nov 21 14:17:03 PingBuild kernel: hpet0: 16 comparators, 64-bit 14.318180 MHz counter
    Nov 21 14:17:03 PingBuild kernel: Switched to clocksource hpet
    Nov 21 14:17:03 PingBuild kernel: pnp: PnP ACPI init
    Nov 21 14:17:03 PingBuild kernel: system 00:00: [io 0x1000-0x103f] could not be reserved
    Nov 21 14:17:03 PingBuild kernel: system 00:00: [io 0x1040-0x104f] has been reserved
    Nov 21 14:17:03 PingBuild kernel: system 00:00: [io 0x0cf0-0x0cf1] has been reserved
    Nov 21 14:17:03 PingBuild kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
    Nov 21 14:17:03 PingBuild kernel: pnp 00:01: Plug and Play ACPI device, IDs PNP0b00 (active)
    Nov 21 14:17:03 PingBuild kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0303 (active)
    Nov 21 14:17:03 PingBuild kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0f13 (active)
    Nov 21 14:17:03 PingBuild kernel: system 00:04: [mem 0xfed00000-0xfed003ff] has been reserved
    Nov 21 14:17:03 PingBuild kernel: system 00:04: Plug and Play ACPI device, IDs PNP0103 PNP0c01 (active)
    Nov 21 14:17:03 PingBuild kernel: pnp 00:05: Plug and Play ACPI device, IDs PNP0400 (active)
    Nov 21 14:17:03 PingBuild kernel: pnp 00:06: Plug and Play ACPI device, IDs PNP0501 (active)
    Nov 21 14:17:03 PingBuild kernel: pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
    Nov 21 14:17:03 PingBuild kernel: pnp 00:08: [dma 2]
    Nov 21 14:17:03 PingBuild kernel: pnp 00:08: Plug and Play ACPI device, IDs PNP0700 (active)
    Nov 21 14:17:03 PingBuild kernel: system 00:09: [io 0x1060-0x107f] has been reserved
    Nov 21 14:17:03 PingBuild kernel: system 00:09: [mem 0xe0000000-0xefffffff] has been reserved
    Nov 21 14:17:03 PingBuild kernel: system 00:09: [mem 0xd0200000-0xd03fffff] has been reserved
    Nov 21 14:17:03 PingBuild kernel: system 00:09: Plug and Play ACPI device, IDs PNP0c02 (active)
    Nov 21 14:17:03 PingBuild kernel: pnp: PnP ACPI: found 10 devices
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: bridge window [io 0x1000-0x0fff] to [bus 06] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: bridge window [io 0x1000-0x0fff] to [bus 07] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: bridge window [io 0x1000-0x0fff] to [bus 08] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: bridge window [io 0x1000-0x0fff] to [bus 09] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: bridge window [io 0x1000-0x0fff] to [bus 0a] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: bridge window [io 0x1000-0x0fff] to [bus 0e] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: bridge window [io 0x1000-0x0fff] to [bus 0f] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: bridge window [io 0x1000-0x0fff] to [bus 10] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: bridge window [io 0x1000-0x0fff] to [bus 11] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: bridge window [io 0x1000-0x0fff] to [bus 12] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: bridge window [io 0x1000-0x0fff] to [bus 16] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: bridge window [io 0x1000-0x0fff] to [bus 17] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: bridge window [io 0x1000-0x0fff] to [bus 18] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: bridge window [io 0x1000-0x0fff] to [bus 19] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: bridge window [io 0x1000-0x0fff] to [bus 1a] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: bridge window [io 0x1000-0x0fff] to [bus 1d] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: bridge window [io 0x1000-0x0fff] to [bus 1e] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: bridge window [io 0x1000-0x0fff] to [bus 1f] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: bridge window [io 0x1000-0x0fff] to [bus 20] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: bridge window [io 0x1000-0x0fff] to [bus 21] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: bridge window [io 0x1000-0x0fff] to [bus 22] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:0f.0: BAR 6: assigned [mem 0xc0000000-0xc0007fff pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:10.0: BAR 6: assigned [mem 0xc0008000-0xc000bfff pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: BAR 6: assigned [mem 0xd1010000-0xd101ffff pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: PCI bridge to [bus 02]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [io 0x2000-0x3fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0xd1000000-0xd23fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0xdc400000-0xdc9fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: PCI bridge to [bus 03]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: bridge window [io 0x4000-0x4fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: bridge window [mem 0xd2400000-0xd24fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: bridge window [mem 0xd4400000-0xd44fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: PCI bridge to [bus 04]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: bridge window [io 0x8000-0x8fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: bridge window [mem 0xd2800000-0xd28fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: bridge window [mem 0xd4800000-0xd48fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: PCI bridge to [bus 05]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: bridge window [io 0xc000-0xcfff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: bridge window [mem 0xd2c00000-0xd2cfffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: bridge window [mem 0xdcb00000-0xdcbfffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: PCI bridge to [bus 06]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: bridge window [mem 0xd3000000-0xd30fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: bridge window [mem 0xdcd00000-0xdcdfffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: PCI bridge to [bus 07]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: bridge window [mem 0xd3400000-0xd34fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: bridge window [mem 0xdcf00000-0xdcffffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: PCI bridge to [bus 08]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: bridge window [mem 0xd3800000-0xd38fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: bridge window [mem 0xdd100000-0xdd1fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: PCI bridge to [bus 09]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: bridge window [mem 0xd3c00000-0xd3cfffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: bridge window [mem 0xdd300000-0xdd3fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: PCI bridge to [bus 0a]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: bridge window [mem 0xd4000000-0xd40fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: bridge window [mem 0xdd500000-0xdd5fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: PCI bridge to [bus 0b]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: bridge window [io 0x5000-0x5fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: bridge window [mem 0xd2500000-0xd25fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: bridge window [mem 0xd4500000-0xd45fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: PCI bridge to [bus 0c]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: bridge window [io 0x9000-0x9fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: bridge window [mem 0xd2900000-0xd29fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: bridge window [mem 0xd4900000-0xd49fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: PCI bridge to [bus 0d]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: bridge window [io 0xd000-0xdfff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: bridge window [mem 0xd2d00000-0xd2dfffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: bridge window [mem 0xd4b00000-0xd4bfffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: PCI bridge to [bus 0e]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: bridge window [mem 0xd3100000-0xd31fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: bridge window [mem 0xd4d00000-0xd4dfffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: PCI bridge to [bus 0f]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: bridge window [mem 0xd3500000-0xd35fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: bridge window [mem 0xd4f00000-0xd4ffffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: PCI bridge to [bus 10]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: bridge window [mem 0xd3900000-0xd39fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: bridge window [mem 0xd5100000-0xd51fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: PCI bridge to [bus 11]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: bridge window [mem 0xd3d00000-0xd3dfffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: bridge window [mem 0xd5300000-0xd53fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: PCI bridge to [bus 12]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: bridge window [mem 0xd4100000-0xd41fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: bridge window [mem 0xd5500000-0xd55fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: PCI bridge to [bus 13]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: bridge window [io 0x6000-0x6fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: bridge window [mem 0xd2600000-0xd26fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: bridge window [mem 0xd4600000-0xd46fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: PCI bridge to [bus 14]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: bridge window [io 0xa000-0xafff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: bridge window [mem 0xd2a00000-0xd2afffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: bridge window [mem 0xdca00000-0xdcafffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: PCI bridge to [bus 15]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: bridge window [io 0xe000-0xefff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: bridge window [mem 0xd2e00000-0xd2efffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: bridge window [mem 0xdcc00000-0xdccfffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: PCI bridge to [bus 16]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: bridge window [mem 0xd3200000-0xd32fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: bridge window [mem 0xdce00000-0xdcefffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: PCI bridge to [bus 17]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: bridge window [mem 0xd3600000-0xd36fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: bridge window [mem 0xdd000000-0xdd0fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: PCI bridge to [bus 18]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: bridge window [mem 0xd3a00000-0xd3afffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: bridge window [mem 0xdd200000-0xdd2fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: PCI bridge to [bus 19]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: bri

    Trilby wrote:
    Thanks, that all sounds correct to me, unfortunalte I can't provide more help as I've never used vmware.  But a couple pointers for pacman use:
    There is no need to use that pipe, `pacman -Q <searchterm>` will work.
    The reason you don't see the mouse package is that grep is case sensitive.  `pacman -Q | grep -i vmware` should also show the mouse package, but this would be much easier as `pacman -Qs vmware` which allows pacman to do the search.  Pacman's search is case-insensitive by default and is a bit more effient that listing all packages and grepping through them.
    Got it. Yes using the 'vmware' the vmmouse shows up. Also searching 'svga' shows Mesa DRI drivers. That is another advantage for letting pacman search, since my search term was svga and what was dispalayed did not have that in the string, pacman search can see behind the covers. :-)
    All this learning is good, now if I could just figure out why 'startx' is failing to create screen resource. ;-)
    Question, does it matter what tty it starts on? I am using 0 (obvious from the log name), could that be an issue? Just thinking out loud.

  • How to create a new Oracle OSB project automaticaly with script without IDE

    Hello,
    I want to create automatically an "Oracle service bus project" and an "Oracle service bus configuration project" with scripts (ANT or Maven or ...) without using IDE, without using workshop or Eclipse. I want to create automatically (ANT or Maven) just a skeleton of an OSB project witch i can use after in workshop.
    I want to create 1 "Oracle service bus configuration project" with many "Oracle service bus project" automatically (ANT or Maven or scripts) witch i can use after in workshop. How to create a new Oracle OSB project automaticaly with script without IDE ? How can i do this ?
    I'm using Oracle service bus 10.3.1
    Thank you for your help.

    Thank you for your response,
    I do not want to just create the services (proxy services and business services) but I want to create a template for 40 OSB project with the same scripts ANT/Maven.
    Template="Oracle service bus configuration project" + "Oracle service bus project" + services of 40 OSB projects
    The goal is that I have more than 40 projects to create and just the name of the projects that changes (when I say the name of the project ie the name of the OSB project, the name of proxy services and the name of business services ).
    So I want to give my script (ANT/Maven) the name of 40 OSB project and the script must generate the skeleton of the 40 projects at once time and after generation of skeleton of the 40 project, I will import them in the workshop to add manually mapping and routing and other things that differs from one project to another.
    So i want to generate automatically a skeletons of 40 OSB projects using a script (ANT / Maven) and I give to the script juste the names of the 40 projects.
    I want to create a "Oracle service bus configuration project" and "Oracle service bus project" automatically of 40 OSB projects (ANT or Maven or scripts) witch i can use after in workshop.
    I want to create one 'template' of all 40 projects in the same time, with the same directory structure (Transforlation, Business services, proxy services, WSDL .....) and all 40 project have the same transport, just the names of projects and services witch changes and i can give to the script all names of projects and services and i can give also all WSDL.
    Regards,
    Tarik

  • Any clues on how to create a resource object to push a user object into res

    I am working on a situation where I have to push a user object via a resource object and not having assigned to the user (in other words not linked to the user).
    any ideas?
    My approach is some thing like this
    IN the "user" object I do set all the attributes required per the resource definition
    Here is the code snippet for resource object creation:
    <Action name='create services resource object' process='Provision'>
    <Argument name='op' value='createResourceObject'/>
    <Argument name='object' value='$(user)'/>
    <Argument name='objectType' value='user'/>
    <Argument name='resourceId' value='UnixUIDServices'/>
    </Action>

    I by no means want to sound belittling... so don't take me that way..
    You need to understand the basics of files, and networks. You can't check if a file exists on another machine if you don't have a network protocol to communicate with. The reason \\ works under windows is because you are using an invisible (to you) network protocol. You probably know it as windows sharing. If your file were not shared under it's own name, that method wouldn't work (I'm assuming your entire drive is shared without a password... a horrible security flaw...but one thing at a time)
    You can use FTP protocol to check if a file exists. You can either send the raw text FTP commands through a socket connection in java, or you can use a freely available FTP java API to make it a bit more simple. You could also write a small java server on the other machine, and have it tell you what you need to know with a socket connection. In this way, you have created your very own network protocol.

  • Creating multiple resource objects at once

    Hi,
    Business roles are multivalued attributes and in order for OIM to manage them, I am creating them as resources. These resources will have role id and role name as its fields. I have close to 50 biz roles in the system. Is there any way I can create them in bulk than having to create the resource obj, process defn. and process forms for each of them manually?
    Thanks,
    Supreetha

    You can create one workflow and uniquely identity the objects names such as:
    RO_NAME, PROV_PROC_DEF, APPR_PROC_DEF, UD_FORM and so on to identify all the objects. Export the workflow. Come up with either code, or some way to find and replace these values with your list of names for your other workflows. Then import the workflows.
    You could try and come up with code that takes a template, and then generates a new xml file with a list of values.
    -Kevin

  • How to create a validation for the project coding mask

    Hi,
    Would just like to ask how to create a validation for the project coding mask wherein the WBS elements hierarchy will be checked against the template saved. For example,
    project coding mask is XXXX-XXXXX-XX-X-X-X-00-X
    mother WBS should be XXXX-XXXXX-X and lower level WBS would be XXXX-XXXXX-XX.
    The validation should not allow a mother WBS to be XXXX-XXXXX-XX.
    How can we go about this?

    Hi Jacquiline Bersamin,
    You can use validation with the combination of the level and the coding mask.
    In the validation:
    Pre requisite: WBS level = 1
    Validation: Prps-posid = prps-posid :1-12:
    Message : Error
    If required you can give the parameters for your detail error message.
    Please let me know if this does not work.
    Thanks
    Regards
    Srinivasan Desingh

Maybe you are looking for

  • Dvd player suddenly no longer recognized

    hi, i have a lacie firewire dvd drive, which has worked fine up till now. suddenly it's not being recognized. this happened after i aborted the one step dvd procedure in iDvd, and now i get a warning from idvd "no supported burner available...". load

  • Why does Firefox 8 lose its settings between sessions?

    Version 8 does not hold its settings from one Windows session to another. I have to keep turning the menu bar back on and resizing the window (the default of the left half of the screen -- absolutely WORST place it could be -- keeps coming back!). Fi

  • How change decimal separator from . to ,

    Hi I need change the decimal separator from . to , and apply ZZZ.ZZ9,99 thanks

  • IDM Error

    After updating to S394 get the following error idm error connecting to sensor "failed to create sensor have tried rebooting the sensor, no change. Am able to log in through command line.

  • MAnual bank reconciliation to Automatic bank reconciliation.

    Hi Sapients, we are doing BRS manually for all collections and disbursement accounts. The details of the bank accounts are 1. HDFC                                       - Collection Account 2. Deutsche Bank                     - Collection Account 3.