Can't create HAStoragePlus resource

Hello.
I'm trying to create cluster with failover solaris container and take a problem - can't create HAStoragePlus resource
A have a two sparc nodes (h2 h3) with latest patched Solaris 10u6 and Sun Cluster 3.2u2 and Fibre Channel storage.
$ cldevice show d13
=== DID Device Instances ===
DID Device Name: /dev/did/rdsk/d13
Full Device Path: h2:/dev/rdsk/c2t60060480000290102925533030304142d0
Full Device Path: h3:/dev/rdsk/c4t60060480000290102925533030304142d0
Replication: none
default_fencing: global
$ clrg show
=== Resource Groups and Resources ===
Resource Group: vh1-rg
RG_description: <NULL>
RG_mode: Failover
RG_state: Unmanaged
Failback: False
Nodelist: h3 h2
* on h2
$ grep d13 /etc/vfstab
/dev/did/dsk/d13s0 /dev/did/rdsk/d13s0 /global/vh1 ufs 2 no logging
* on h3
$ grep d13 /etc/vfstab
/dev/did/dsk/d13s0 /dev/did/rdsk/d13s0 /global/vh1 ufs 2 no logging
$ mount /global/vh1
$ df -k | grep d13
/dev/did/dsk/d13s0 247779831 65553 245236480 1% /global/vh1
$ clrs create -g vh1-rg -t SUNW.HAStoragePlus -p FilesystemMountPoints=/global/vh1 -p Affinityon=true vh1-hasp-rs
clrs: h3:global - Invalid global device path /dev/did/dsk/d13s0 detected for mount point /global/vh1.
clrs: (C189917) VALIDATE on resource vh1-hasp-rs, resource group vh1-rg, exited with non-zero exit status.
clrs: (C720144) Validation of resource vh1-hasp-rs in resource group vh1-rg on node h3 failed.
clrs: (C891200) Failed to create resource "vh1-hasp-rs".
I don't understand what's wrong. Please help me!
Thanks,
Alexander

OK. The clue has appeared.
[root@h3 /]$ cat /etc/vfstab
/dev/global/dsk/d13s0 /dev/global/rdsk/d13s0 /global/vh1 ufs 2 no logging
[root@h3 /]$ clrs create -g vh1-rg -t SUNW.HAStoragePlus -p FilesystemMountPoints=/global/vh1 -p Affinityon=true vh1-hasp-rs
clrs: h2:global - Failed to analyze the device file /dev/global/dsk/d13s0: No such file or directory.
clrs: h2:global - Failed to obtain the global service name of device /dev/global/dsk/d13s0 for mount point /global/vh1.
clrs: (C189917) VALIDATE on resource vh1-hasp-rs, resource group vh1-rg, exited with non-zero exit status.
clrs: (C720144) Validation of resource vh1-hasp-rs in resource group vh1-rg on node h2 failed.
clrs: (C891200) Failed to create resource "vh1-hasp-rs".
[root@h3 /]$ ls -l /dev/did/dsk/d13s0
lrwxrwxrwx 1 root root 42 Feb 3 15:41 /dev/did/dsk/d13s0 -> ../../../devices/pseudo/did@13:13,13s0,blk
[root@h3 /]$ ls -l /dev/global/dsk/d13s0
lrwxrwxrwx 1 root root 42 Jan 30 13:48 /dev/global/dsk/d13s0 -> ../../../devices/pseudo/did@13:13,13s0,blk
[root@h2 /]$ ls -l /dev/did/dsk/d13s0
lrwxrwxrwx 1 root root 42 Feb 3 16:27 /dev/did/dsk/d13s0 -> ../../../devices/pseudo/did@13:13,13s0,blk
[root@h2 /]$ ls -l /dev/global/dsk/d13s0
/dev/global/dsk/d13s0: No such file or directory
h3 - node@1
h2 - node@2
[root@h2 /]$ ls -l /global/.devices/node@2/
total 0
[root@h2 /]$ ls -l /global/.devices/node@1/
total 26
drwxrwxr-x 17 root root 3584 Feb 5 19:07 dev
drwxrwxr-x 3 root root 512 Jan 30 13:48 devices
drwx------ 2 root root 8192 Jan 28 18:31 lost+found
$ mount | grep node
/global/.devices/node@1 on /dev/md/dsk/d20 read/write/setuid/devices/intr/largefiles/logging/noquota/global/xattr/nodfratime/onerror=panic/dev=1540014 on Wed Feb 4 19:57:41 2009
[root@h3 /]$ mount | grep node
/global/.devices/node@1 on /dev/md/dsk/d20 read/write/setuid/devices/intr/largefiles/logging/noquota/global/xattr/nodfratime/onerror=panic/dev=1540014 on Wed Feb 4 19:57:41 2009
[root@h2 /]$ mount | grep node
/global/.devices/node@1 on /dev/md/dsk/d20 read/write/setuid/devices/intr/largefiles/logging/noquota/global/xattr/nodfratime/onerror=panic/dev=1540014 on Wed Feb 4 19:57:41 2009
/global/.devices/node@2 is not mounted, but I don't care how it should look as a result
[root@h2 /]$ grep node /etc/vfstab
/dev/md/dsk/d20 /dev/md/rdsk/d20 /global/.devices/node@2 ufs 2 no global
[root@h2 /]$ mount | grep node
/global/.devices/node@1 on /dev/md/dsk/d20 read/write/setuid/devices/intr/largefiles/logging/noquota/global/xattr/nodfratime/onerror=panic/dev=1540014 on Fri Feb 6 16:27:23 2009
[root@h2 /]$ mount /global/.devices/node@2
mount: /dev/md/dsk/d20 is already mounted or /global/.devices/node@2 is busy
/dev/md/dsk/d20 - it's a mirrored slice on local disks

Similar Messages

  • Where to place mysqlconnector in BPM?Can't create external resource databas

    I've encountered this error while trying to create a new external resource for MYSQL database. Can anyone please help me out? And may I also ask where do I place the mysqlconnector to connect it? Cos it says it JDBC drivers are missing. So is it that I have to place the mysqlconnector into somewhere to start the connection? Please help. :(
    This is the error message that it appears:
    An exception occured while initializing a connector.
    Detail: The connector [newConfiguration:SQL:MYSQL] caused an exception when initializing
    An exception occurred while initializing a connector.
    Detail:The connector [newConfiguration:SQL:MYSQL] caused an exception when initializing.
    Caused by: The JDBC driver library files for the connector were not found.
    Detail:Connector [newConfiguration:SQL:MYSQL] caused an exception when initializing.
    The driver class [org.gjt.mm.mysql.Driver] was not found.
    Verify that the JDBC driver libraries are defined as external resources in the environment.
    fuego.connector.ConnectorException: An exception occurred while initializing a connector.
    Detail:The connector [newConfiguration:SQL:MYSQL] caused an exception when initializing.
         at fuego.connector.ConnectorException.exceptionOnInit(ConnectorException.java:103)
         at fuego.connector.SynchConnectorService.getConnector(SynchConnectorService.java:163)
         at fuego.connector.ConnectorService.getConnectorInterface(ConnectorService.java:509)
         at fuego.connector.CompositeConnectorService.getConnectorInterface(CompositeConnectorService.java:256)
         at fuego.connector.ConnectorTransaction.getConnectorInterface(ConnectorTransaction.java:225)
         at fuego.connector.JDBCHelper.getReadOnlyConnection(JDBCHelper.java:87)
         at fuego.sqlintrospector.BrowserPanel.connect(BrowserPanel.java:398)
         at fuego.sqlintrospector.BrowserPanel.populateTree(BrowserPanel.java:200)
         at fuego.ui.wizards.ui.CheckTreeBrowser$1.construct(CheckTreeBrowser.java:56)
         at fuego.ui.SwingWorker$2.run(SwingWorker.java:39)
         at java.lang.Thread.run(Unknown Source)
    Caused by: fuego.connector.ConnectorException: The JDBC driver library files for the connector were not found.
    Detail:Connector [newConfiguration:SQL:MYSQL] caused an exception when initializing.
    The driver class [org.gjt.mm.mysql.Driver] was not found.
    Verify that the JDBC driver libraries are defined as external resources in the environment.
         at fuego.connector.ConnectorException.jdbcDriverNotFound(ConnectorException.java:130)
         at fuego.connector.impl.BaseJDBCConnector.start(BaseJDBCConnector.java:279)
         at fuego.connector.SynchConnectorService.getConnector(SynchConnectorService.java:159)
         ... 9 more

    What is on the external drive?
    If it is a Time Machine backup, no. That is not bootable.
    The directions for cloning are at https://discussions.apple.com/thread/4190995
    Allan

  • Applying Sticky Error in saving to DB: Can't create sticky because resource is not allocated.

    When trying to setup Stick http-cookies and when I deploy i'm getting the following error.
    Error in saving to DB: Can't create sticky because resource is not allocated.

    just a wild shot. you sure have resource class with sticky resources created.

  • How can i  create and access resource file(with .res ext) in j2me

    hi,
    i am developing an mobile international application using jsr-238 an optional api to implement the idea of internationalizationand localization.
    please tell me how can i create .res files in my application to store strings of different languages.thanks inadvance.

    Hello GG RA,
    which fileformat do you want to use (binary or ASCII)?
    There are some LabVIEW shipping examples for File I/O
    You could use the LabVIEW NI Example Finder (Help --> Find Examples..(search item "file")) to get an overview about the different file-formats in LabVIEW.
    Hope this helped out and feel free to reply if you have more questions about File I/O in LabVIEW
    Best regards
    Benjamin

  • Can not create temp file---- Error code:-2147215357 [CRSDK00000615] Error code name:internal

    Hello,
    While exporting Export reporting from BI4 getting exception
    Can not create temp file---- Error code:-2147215357 [CRSDK00000615] Error code name:internal
    In Trace Log I am getting
    com.crystaldecisions.xml.serialization.XMLWriter||Failed to create an object instance for CrystalReports.TextObjectFormat
    java.util.MissingResourceException: Can't find resource for bundle java.util.PropertyResourceBundle, key CrystalReports.TextObjectFormat
      at java.util.ResourceBundle.getObject(ResourceBundle.java:374)
      at java.util.ResourceBundle.getString(ResourceBundle.java:334)
    I tried following solution according to the all forums but still issue exist.
    Done changes mention in KB article In <Installation-dir-of-BO>\Common\4.0\java\CRConfig.XML we have to increase the JAVA heap MIN and Max size
              <JVMMaxHeap>64000000</JVMMaxHeap>          <JVMMinHeap>32000000</JVMMinHeap>
    Increase the value in the ReportApplicationServer Services in the CMC for "Number of database records to read when previewing or refreshing a report". The value -1 is for unlimited records but not recommended for performance.
    Check for temporary read write permission on server
    Using SDK library from C:\Program Files (x86)\SAP Business Objects\SAP BusinessObjects Enterprise XI 4.0\java\lib
    Can you please let me know is there anything missing.

    Hi,
    We face the same problem with some BI4 reports.
    The same report works well with the "Crystal Reports Viewers API", as used in Infoview, but not with the "Report Application Server (RAS) API".
    This error appears after some time working on a report. If we reproduce the same report, but from zero, no problem.
    Hope it can help.
    Ludovic.

  • How can i create datasource on apache server for ADF application?

    Hi All,
    i my use case i have created simple adf application using ADF BC and want to deploy on Apache server 6.x.
    So my question is that  how can i create Data Source i have goggling and find  two different way to do this.
    1. write following line of code on apache server conf/Context.xml file.
    <Resource name="jdbc/TestDB" auth="Container"
                  type="javax.sql.DataSource"
                   driverClassName="oracle.jdbc.OracleDriver"
                  url="jdbc:oracle:thin:@localhost:dst"
                  username="jagrandb" password="jagrantest" maxActive="20" maxIdle="10"
                  maxWait="-1"/>
    but when i have used this way i got following exception.
    org.apache.tomcat.dbcp.dbcp.PoolingDataSource$PoolGuardConnectionWrapper cannot be cast to oracle.jdbc.OracleConnection
    check link-
    https://forums.oracle.com/thread/2564233
    2. write following line of code apache conf/Server.xml file
    <GlobalNamingResources>
        <!-- Editable user database that can also be used by
             UserDatabaseRealm to authenticate users
        -->
        <Resource name="UserDatabase" auth="Container"
                  type="org.apache.catalina.UserDatabase"
                  description="User database that can be updated and saved"
                  factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
                  pathname="conf/tomcat-users.xml" />
    <Resource name="jdbc/TestDB" auth="Container"
                  type="oracle.jdbc.pool.OracleDataSource"
                  description="User database that can be updated and saved"
                  driverClassName="oracle.jdbc.driver.OracleDriver"
                  factory="oracle.jdbc.pool.OracleDataSourceFactory"
                  url="jdbc:oracle:thin:@//172.31.43.207:1521:dst"
                  username="jagrandb" password="jagrantest" maxActive="20" maxIdle="10"
                  maxWait="-1"   />
      </GlobalNamingResources>
    and add this line in context.xml file inside <context> tag
    <ResourceLink global="jdbc/TestDB" name="jdbc/TestDB" type="oracle.jdbc.pool.OracleDataSource"/>
    but when i have run application i have got following error
    log-
    javax.servlet.jsp.JspException: Unable to get connection, DataSource invalid: "java.sql.SQLException: invalid arguments in call"
      at org.apache.taglibs.standard.tag.common.sql.QueryTagSupport.getConnection(QueryTagSupport.java:298)
      at org.apache.taglibs.standard.tag.common.sql.QueryTagSupport.doStartTag(QueryTagSupport.java:181)
      at org.apache.jsp.test_jsp._jspx_meth_sql_005fquery_005f0(test_jsp.java:110)
      at org.apache.jsp.test_jsp._jspService(test_jsp.java:63)
      at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
      at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:374)
      at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:342)
      at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:267)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
      at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
      at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
      at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
      at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
      at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
      at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
      at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:857)
      at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:565)
      at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1509)
      at java.lang.Thread.run(Thread.java:662)
    Aug 2, 2013 5:17:21 PM org.apache.catalina.core.StandardWrapperValve invoke
    SEVERE: Servlet.service() for servlet jsp threw exception
    javax.servlet.jsp.JspException: Unable to get connection, DataSource invalid: "java.sql.SQLException: invalid arguments in call"
      at org.apache.taglibs.standard.tag.common.sql.QueryTagSupport.getConnection(QueryTagSupport.java:298)
      at org.apache.taglibs.standard.tag.common.sql.QueryTagSupport.doStartTag(QueryTagSupport.java:181)
      at org.apache.jsp.test_jsp._jspx_meth_sql_005fquery_005f0(test_jsp.java:110)
      at org.apache.jsp.test_jsp._jspService(test_jsp.java:63)
      at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
      at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:374)
      at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:342)
      at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:267)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
      at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
      at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
      at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
      at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
      at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
      at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
      at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:857)
      at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:565)
      at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1509)
      at java.lang.Thread.run(Thread.java:662)
    so what is the solution how to create datasource on apche server which suitable for adf application?
    when i test data source using  following code used 1. way as i mentioned above  its running fine bt not for second.
    <%@ taglib uri="http://java.sun.com/jsp/jstl/sql" prefix="sql" %>
    <%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
    <sql:query var="rs" dataSource="jdbc/TestDB">
    select empname from pay_emphdr where empcd='JK1306'
    </sql:query>
    <html>
      <head>
        <title>DB Test</title>
      </head>
      <body>
      <h2>Results</h2>
    <c:forEach var="row" items="${rs.rows}">
        Foo ${row.empname}<br/>
    </c:forEach>
      </body>
    </html>
    please help me. it is very urgent.
    thanks in Advance
    Manish

    Hi Lindalnci
    i have already tried  this tutorial and in my post i have defined first way to do using this procedure.
    in that case i have got following exception as i have mentioned above
    org.apache.tomcat.dbcp.dbcp.PoolingDataSource$PoolGuardConnectionWrapper cannot be cast to oracle.jdbc.OracleConnection

  • 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.

  • Can we create a developersite in O365 SP Online programiatically ? what is the template code for it ?

    Hi
    I am trying to create sites programmatically in O365 SharePoint Online. So, just want to know that can we create a DeveloperSite ?? what is the template code for it viz. Team site- STS#0, etc
    If possible provide me the MSDN link where I can refer for available site templates for O365 SP Online sites creation.
    Thank you 

    http://community.office365.com/en-us/f/154/t/61145.aspx
    Are you meaning to create sites on SharePoint Online by invoking web services in your own program? SharePoint Online indeed provide some web services for custom programming, however, the web methods for creating a new site seems not included in them. Here
    are some resources for the development of SharePoint Online for your reference:
    SharePoint Online for developers
    http://msdn.microsoft.com/en-us/sharepoint/gg153540.aspx
    Code example for SharePoint Online: Accessing Web Services
    http://code.msdn.microsoft.com/office/SharePoint-Online-0bdeb2ca
    As to create a site collection, the parameter "Template" is the name of the template you want to use, as to find the name of the custom site template, you can use the powershell command "Get-SPOWebTemplate",
    it will list all the templates with the names.
    Note, The Template and LocaleId parameters must be a valid combination as returned from the Get-SPOWebTemplate cmdlet.
    Also check
    http://stackoverflow.com/questions/21268629/creating-new-site-collection-in-office-365-from-an-app
    If this helped you resolve your issue, please mark it Answered

  • HT3529 My group messaging on/off label isn't showing up at all. I can only create group messages but every time someone starts a group chat it says its send to my number but I never got any text. I wen't to settings Messages and I can't find any on/off sw

    I can only create group messages but every time someone starts a group chat it says its send to my number but I never got any text. I wen't to settings>Messages and I can't find any on/off switch.

    Hello there, Idaniabb.
    The following Knowledge Base article offers up some great information in regards to group messaging and also links to another excellent resource for troubleshooting messages as well:
    iOS: Understanding group messaging
    http://support.apple.com/kb/HT5760
    Thanks for reaching out to Apple Support Communities.
    Cheers,
    Pedro.

  • How can I create Hyperlinks with a Fixed-Ratio EPUB?

    I am using InDesign 2014's fixed ratio epub exporter. It looks great but all my hyperlinks are lost and I can't find any resources on how to maintain them or to recreate them in a reader program, if possible. Any help much appreciated?

    Are the hyperlinks you want to make supposed to go to specific pages of the document, or to a url.
    If it's to go to pages of the document, then click the Create Bookmarks when creating the TOC, it's in the bottom left, you may need to Show Options in the TOC dialog box.
    If it's for a URL, or to link to a different page other than what the TOC points to, then you can
    New Hyperlink Destination
    Choose URL/Page
    Insert a unique name
    Insert the url/page no.
    Then say ok
    Go to Hyperlink Options
    Type: URL
    Name: Choose the unique name you've created
    URL: it should show up as what you've put in the Name, if not just type it in
    similar for page no.
    Remember to inlcude bookmarks and hyperlinks when creating the PDF too.

  • With SP16-17 we can't create support message from satellite system anymore

    hello,
    We have implemented the support package 16 and 17 SAPKITL427 in solution manager last week-end and since then all satellite systems can not create support message anymore.
    The process is perfectly working in solman itself and we don't think we have thus a process customizing issue here but who knows...
    The key user creates the message with the help -> create support message
    and when he saves it (clicking the mailbox button) he gets the following error
    Error in Local Message System: Function not available Message was Not
    Created
    In fact the error Message is BCOS088
    We debugged the function BCOS_CREATE_MSG and we found out that the function
    DNO_OW_CREATE_NOTIFICATION is returning error code 1.
    We checked out RFC connection and it looks ok
    There is no dumps in ST22, no error in SLG1 in both system...a nightmare
    The notification SLF1 is created in solman but the status field of the notification is empty and it looks that the record is somehow corrupted because you can't modify it with dnotifwl.
    Due to the fact that the notification is not correctly created the support message is also not created.
    SAP and our solman consultant are working on it since 2 days but don't have a clue.  Maybe some program where no regenerated correctly ?
    If you would have any idea in which direction to look, i would greatly appreciate
    thanks a lot
    best regards Xavier

    hi Rohit,
    on the satellit I have the following versions
    SAP_BASIS     700     0012     SAPKB70012     SAP Basis Component
    SAP_ABA     700     0012     SAPKA70012     Cross-Application Component
    PI_BASIS     2005_1_700     0012     SAPKIPYJ7C     PI_BASIS 2005_1_700
    ST-PI     2005_1_700     0006     SAPKITLQI6     SAP Solution Tools Plug-In
    SAP_BW     700     0013     SAPKW70013     SAP NetWeaver BI 7.0
    SAP_AP     700     0009     SAPKNA7009     SAP Application Platform
    SAP_HR     600     0018     SAPKE60018     Human Resources
    SAP_APPL     600     0010     SAPKH60010     Logistics and Accounting
    EA-IPPE     400     0010     SAPKGPID10     SAP iPPE
    EA-APPL     600     0010     SAPKGPAD10     SAP Enterprise Extension PLM, SCM, Financials
    EA-DFPS     600     0010     SAPKGPDD10     SAP Enterprise Extension Defense Forces & Public Security
    EA-HR     600     0018     SAPKGPHD18     SAP Enterprise Extension HR
    EA-FINSERV     600     0010     SAPKGPFD10     SAP Enterprise Extension Financial Services
    FINBASIS     600     0010     SAPK-60010INFINBASIS     Fin. Basis
    EA-PS     600     0010     SAPKGPPD10     SAP Enterprise Extension Public Services
    EA-RETAIL     600     0010     SAPKGPRD10     SAP Enterprise Extension Retail
    EA-GLTRADE     600     0010     SAPKGPGD10     SAP Enterprise Extension Global Trade
    IS-PS-CA     600     0010     SAPK-60010INISPSCA     IS-PUBLIC SECTOR CONTRACT ACCOUNTING
    IS-OIL     600     0010     SAPK-60010INISOIL     IS-OIL
    IS-M     600     0010     SAPK-60010INISM     SAP MEDIA
    IS-H     600     0010     SAPK-60010INISH     SAP Healthcare
    IS-CWM     600     0010     SAPK-60010INISCWM     Industry Solution Catch Weight Management
    INSURANCE     600     0010     SAPK-60010ININSURANC     SAP Insurance
    FI-CAX     600     0010     SAPK-60010INFICAX     FI-CA Extended
    FI-CA     600     0010     SAPK-60010INFICA     FI-CA
    ERECRUIT     600     0010     SAPK-60010INERECRUIT     E-Recruiting
    ECC-DIMP     600     0010     SAPK-60010INECCDIMP     DIMP
    IS-UT     600     0010     SAPK-60010INISUT     SAP Utilities/Telecommunication
    SEM-BW     600     0010     SAPKGS6010     SEM-BW: Strategic Enterprise Management
    LSOFE     600     0010     SAPK-60010INLSOFE     SAP Learning Solution Front-End
    ST-A/PI     01K_ECC600     0000          -     Application Servicetools for ECC 600
    APICON     1470000000     0000          -     APICON GmbH, Interface Add ON
    thank you Xavier

  • 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

  • Can I create a form that doesn't trigger Acrobat's JavaScript disabled / security issues warning?

    Hello,
    Can I create a pdf that doesn't trigger Acrobat's JavaScript is currently disabled and this document uses it for some features.  Enabling JavaScript can lead to potential security issues.
    I even get this error when I create a blank pdf.
    I'm not using any JavaScript in the form and the nature of the message might tend to be a bit scary to some people since it mentions enabling JS can lead to potential security issues.  I basically want to disable the messaging of a feature I'm not even using.
    Anyone know if this is possible and if so, how I go about it?
    Thank you.

    Hi,
    I too share your frustration!!
    Unfortunately I do not have a complete answer for you.
    From the start I must say that Stefan Cameron has been very helpful (http://forms.stefcameron.com/2010/01/14/acrobatreader-9-3-now-available/), however I have not had sufficient time available to deal with the issue (or find a satisfactory resolution).
    The original post that Srini shared with you related to an XFA form that had FormCalc and Javascript in it. I will now share with you another situation that is closer to your experiences.
    Sometimes where we have a complex solution/form, we often give our users a PDF with instructions and demonstrations. We generate these using Adobe products:
    LiveCycle Designer ES to generate the solution/form;
    Captivate to record the demonstration (.swf);
    Acrobat to package it up in a static PDF.
    The screen shots below are from a PDF that includes written instructions and six Flash (.swf) files. The PDF does NOT include fields/form objects and does NOT include any FormCalc or Javascript.
    One of the big sells in Acrobat 9 was that Adobe had fully integrated Flash (Adobe product, ex. Macromedia) into Acrobat 9. This mean that .swf files could run natively inside a PDF. Brilliant!!!  The website today is still pushing this message, for example:
    Now bear in mind that the following screenshots are from a PDF that does not contain any scripting - its sole purpose is to "inform" the user, "look as good as the work I put into it", incorporate instruction and "multimedia" in a "single polished file" and I should be "confident that my audience will be able to view my work exactly as intended".
    Not so!!
    When the user now opens the form, all looks OK. No warning. They can read the instructions and scroll down to the multimedia (.swf files).
    However when the user clicks on the multimedia, the yellow bar appears:
    I go through the "trust" process:
    And the PDF looks like it is OK, no yellow bar. When I click on the multimedia, it begins to play - yes!! BUT ONLY FOR A SECOND OR TWO AND THEN IT STOPS AND GOES BACK TO THE START - AGGGGHHHHHHH!!!!!. I would apologise for shouting, but this is beyond frustration. The work in capturing six screencasts in Captivate, annotating them, publishing to .swf and packaging up in Acrobat has been a complete waste of time. Worse than that I now have several PDFs out there, that do not work. Good advertisement for my business? I don't think so!!
    The document that Stefan provided (Managing JavaScript Execution in the Acrobat Family of Products) does not mention Flash/.swf as being a problem. However I would recommend that you go through this document, as it may help you.
    So, where to now? I don't know. The previous posts and Stefan's responses have several urls that may help. You should maybe consider logging your experiences as a bug (log at Adobe).
    In the meantime good luck,
    Niall
    UPDATE:
    This behaviour (.swf playing for only a few seconds) happens in PDFs where the .swf is inserted as legacy media to run in earlier versions of Acrobat/Reader. In this case Acrobat/Reader is making an external call to Flash Player. Hence the yellow bar. However it does not explain why the Flash video still does not play when trusted.
    If the .swf is added into the PDF as Flash media to run on Acrobat 9 and above, then it works without displaying the yellow warning bar.
    So maybe any feature of your PDF that calls an external resource is likely to show the yellow warning bar.

  • Problem with Access Policies (create multiple resources)

    I'm having a problem with Access Policies:
    The first policy must create a resource.
    And the following policies should create childs on the resource.
    The problem here is that when policies will add the childs, the resource is not provisioned yet.
    And then each one will create a resource but i just want one resource with the childs.
    When the resource is already provisioned, the policies update this resource properly.
    How can I fix this?
    tks

    Ricardo,
    I had a similar problem. In a post-process handler I was managing the user membership in specific roles through the removeMemberUser and the addMemberUser of the tcGroupOperationsIntf class.
    The last parameter of this method was a boolean which, when true, would automatically trigger the access policies programmatically in the post-process.
    The problem is that there also is an OOTB event handler for triggering access policies, so I was basically triggering the access policies twice and duplicated resources were appearing.
    Hope this helps.
    Cheers

Maybe you are looking for

  • Can installing Oracle 11g on a client in the same network as another implementation cause problems?

    Hi, I have a running Oracle 11g r2 installation running.  Same network, different subnet.  I want to install 11gR2 for development/testing on another machine not connected in any way to the other system other than they are on the same network (differ

  • Smartform's Service Tax Error

    Dear All, We have a Smartform, its a invoice. It has got 37 items, Base Total (=555,000.00) is correct, <b>but Service Tax @ 12% is wrong which is dependent on Base Total</b>. BUT again the "TOTAL VALUE(=622,932.00) = Base Total + Tax @ 12% + Educati

  • Bi content not imported

    Hi Friends, in saint when I go to support packeges in the System I find SAPKIBIIIH with status not imported. How can I import the package? And furthermore, note 916834 says I have to download the file CSR0120031469_0023365.PAT from service marketplac

  • Downloading from photo stream

    How do I download photos from a friend's photo stream?

  • Not a bootable device

    Hi all, i'm a newbie to the mac world and need somm help if you please.i found this old G3 at the ASU surplus wharehouse and picked it up for a dollar and figured the cd-rom and zip drive were worth that. when i got home i found it had 320gb's of ram