JMS adapter for MQSeries: Changing from MQ5.3 to 6.X libraries

Hi,
Can someone point in the direction of documentation as to how I would migrate/update a BPEL 10.1.3.5.0 environment using JMS adapters for MQSeries 5.3 to use new libraries for MQSeries 6.x.
In a test env I have located the following, but I am not sure now to proceed.
[bpel@omv2rrm2 5.3]$ pwd
/opt/oracle/product/10.1.3.1/OracleAS_1/j2ee/oc4j_soa/shared-lib/oracle.mqseries/5.3
[bpel@omv2rrm2 5.3]$
[bpel@omv2rrm2 5.3]$ ls -l
total 2124
-rwx------ 1 bpel dba 352652 Apr 17 2008 com.ibm.mq-5.3.jar
-rwx------ 1 bpel dba 1798896 Apr 17 2008 com.ibm.mqjms-5.3.jar
[bpel@omv2rrm2 5.3]$
...and...
[bpel@omv2rrm2 config]$ pwd
/opt/oracle/product/10.1.3.1/OracleAS_1/j2ee/oc4j_soa/config
[bpel@omv2rrm2 config]$ cat server.xml
<?xml version="1.0"?>
<application-server xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://xmlns.oracle.com/oracleas/schema/application-server-10_1.xsd" localhostIsAdmin="true"
application-directory="../applications"
check-for-updates="adminClientOnly"
deployment-directory="../application-deployments"
connector-directory="../connectors"
schema-major-version="10" schema-minor-version="0" >
<shared-library name="global.libraries" version="1.0" library-compatible="true">
<code-source path="../applib"/>
<import-shared-library name="oracle.ws.jaxrpc"/>
</shared-library>
<shared-library name="oracle.mqseries" version="5.3">
<code-source path="/opt/oracle/product/10.1.3.1/OracleAS_1/j2ee/oc4j_soa/shared-lib/oracle.mqseries/5.3/com.ibm.mqjms-5.3.jar"/>
<code-source path="/opt/oracle/product/10.1.3.1/OracleAS_1/j2ee/oc4j_soa/shared-lib/oracle.mqseries/5.3/com.ibm.mq-5.3.jar"/>
<import-shared-library name="oracle.ws.jaxrpc"/>
</shared-library>

Just upgrade your SOA to 10.1.3.5.0 and then point to the newer MQ jars in those 2 files.

Similar Messages

  • Mediator Resequencer,JMS Adapter: queue consumers increase from PS2 to PS4

    Hi,
    We have an environment using SOA Suite and Mediator Resequencer, it is using a FIFO approach. It has been running fine in SOA Suite version 11.1.1.3.
    We are using a JMS Adapter, consuming the messages from the UDD queues as we have a SOA cluster of two managed servers.
    Well we are now doing some test for upgrading to PS4 (11.1.15) and we have noticed some differences after the upgrade in terms of # consumers on the UDD queues.
    In 11.1.1.3 eache member of the UDD was showing just 1 consumer. Looks like this is the right configuration when using and mediator resequencer FIFO approach, as they say you need to have a single-threaded approach to avoid unpredictible result.
    After upgrade that, we have noticed that in 11.1.1.5 each UDD member shows 2 consumers, we have not changed anything, we just follow the upgrade guide to do that. To be honest we are not sure wheter it is a problem or not.
    Can anybody advise about that? If it is an issue, How and where can configure it to get back to 1 consumer connected to UDD member?
    Thanks a lot!

    The Bridge is configured to use the MQ CF and destination directly without the foreign JMS wrapper. Does this make any difference to the bridge's transactional behaviour with MQ?
    Even with the foreign jms wrapper, the local jndi name of the MQ CF is still mapped to com.ibm.mq.jms.MQXAQueueConnectionFactory class. So I think there is no wrapper classes are used from foreign JMS perspective. But if a bridge is configured to lookup local jndi, does it add any wrapper classes which handles the XA interactions with MQ in a different way ?
    I am trying to see if introducing a foreign server resolves the problem. Not sure if its worth to take this path.
    Thanks in advance.
    Regards,
    Atheek

  • JMS Adapter (for DI) does not allow passing username and password to JMS connection

    Post Author: PLed76
    CA Forum: Data Integration
    JMS Adapter (for DI) does not allow passing username and password to JMS connection. It has those fields only for MSMQ. Our Production environment does not allow us to connect to JMS (we use Tibco EMS) anonymously, so it prevents us from use of Data Integrator. Is there any way to pass those params, or obtain the correct version of JMS Adapter, or obtain source codes of the JMS Adapter so we can correct them ourselves (we can send you the corrected sources back) ? Thanks in advance for any help. (PL)ed76 Renaissance Capital

    Bump - Were having the same issue.
    Has anyone found a way to connect to Tibco with a user/pwd?
    Version 14.0.297.

  • JMS Adapter for TIBCO BUSINESS WORKS v5.6

    Hi,
    We have a requirement to send a data from BI system to TIBCO BUSINESS WORKS via PI 7.1.
    We are suggested to to use JMS adapter for connecting TIBCO BUSINESS WORKS. I searched in the forum, but could not find any related thread for TIBCO BUSINES WORK.
    Please share your experience on TIBCO BUSINES WORK with SAP PI with JMS adapter.
    1. How to get the drivers of TIBCO and installed it in Java stack
    2. What is the Transport protocol??
    3. Queue name,server etc?
    4. XSD file for receiver. ( Hope, 3rd party ll provide )
    Thanks in advance
    Regards
    Baskaran K

    Selvam,
      It was long time before I did.. I guess I did added   com.sap.aii.adapter.lib_api.jar file as well in addition to the required driver files.
    Cheers
    Agasthuri

  • Anyone successfully deployed BPEL + JMS Adapter (for MQ) to WebSphere?

    Anyone successfully deployed BPEL Process Manager + JMS Adapter (for MQ) to WebSphere (i.e not OAS/OC4J)?
    If you have - I would love to see a valid example of the ra.xml and oc4j-ra.xml files in your jca/JmsAdapter.rar file - to see how you configured access for the JMS Adapter to your remote MQ queues.
    Thank you
    Dennis

    Hi Garima,
    Please check the following:
    1. Add dhbcore.jar also to aii_af_jmsproviderlib.sda and deploy it.
    2. Check the existence of your JMS drivers.
    3. Check the following link and Install the drivers as the way it is mentioned in the guide 'How To Install And Configure External Drivers For JDBC & JMS'
    https://websmp204.sap-ag.de/~form/sapnet?_SHORTKEY=01200252310000071155&_SCENARIO=01100035870000000202
    There are 4 files which needs to be added. http://help.sap.com/saphelp_nw04/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/frameset.htm
    Any of the above solutions should help you solve the problem.
    Regards,
    Abhy

  • I purchased an adapter for playing videos from my ipod touch on my tv. It works fine for episodes I have purchased from Itunes, but won't play videos from Hulu Plus. What should I do to remedy the situation? Thank you!

    I purchased an adapter for playing videos from my ipod touch on my tv. It works fine for videos I have purchased but won't allow me to watch videos from Hulu Plus. What should I do to remedy the situation? Thanks!

    The iPod TV out only works for aps that support TV out.  The description of Hulu Plus only states that iiPad supports HDMI video out (SD only)

  • Configuring JMS adapter for a BPEL process which puts a msg in a Q of MQ

    Hi,
    I am trying to develop a BPEL process which picks up a message from a Q in Websphere MQ and puts that message in another Q of MQ after processing that.
    I have updated the oc4j-ra.xml with the following inputs:
    <connector-factory location="eis/MQSeries/Queue" connector-name="Jms Adapter">
              <config-property name="connectionFactoryLocation" value="com.ibm.mq.jms.MQQueueConnectionFactory"/>
              <config-property name="factoryProperties" value="QueueManager=TestManager;TransportType=1;Hostname=machine's ip address;Port=1414;Channel=channel name for connecting to client"/>
              <config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/>
              <config-property name="isTopic" value="false"/>
              <config-property name="isTransacted" value="true"/>
              <config-property name="username" value="admin"/>
              <config-property name="password" value="welcome"/>
         </connector-factory>
    But while testing the BPEL process, I get the error:
    <remoteFault>
    <part name="code" >
    <code>null</code>
    </part>
    <part name="summary" >
    <summary>file:/D:/OraBPELPM_2/integration/orabpel/domains/default/tmp/.bpel_MQMessaging_1.0.jar/Outbound.wsdl [ Produce_Message_ptt::Produce_Message(SourceEmployee) ] - WSIF JCA Execute of operation 'Produce_Message' failed due to: Adapter Framework unable to create outbound JCA connection. file:/D:/OraBPELPM_2/integration/orabpel/domains/default/tmp/.bpel_MQMessaging_1.0.jar/Outbound.wsdl [ Produce_Message_ptt::Produce_Message(SourceEmployee) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: ORABPEL-12141 ERRJMS_CONN_FAC_NOT_FOUND. Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor com.ibm.mq.jms.MQQueueConnectionFactory neither through JNDI nor instantiate it as a Java class Please examine the log file to determine the problem. ; nested exception is: ORABPEL-12511 Adapter Framework unable to create outbound JCA connection. file:/D:/OraBPELPM_2/integration/orabpel/domains/default/tmp/.bpel_MQMessaging_1.0.jar/Outbound.wsdl [ Produce_Message_ptt::Produce_Message(SourceEmployee) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: ORABPEL-12141 ERRJMS_CONN_FAC_NOT_FOUND. Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor com.ibm.mq.jms.MQQueueConnectionFactory neither through JNDI nor instantiate it as a Java class Please examine the log file to determine the problem. Please examine the log file for any reasons. Enable DEBUG logging in the BPEL Console. </summary>
    </part>
    <part name="detail" >
    <detail>null</detail>
    </part>
    </remoteFault>
    Can anyone tell me what has gone wrong in setting the connection factory for the Q or what else I have to configure to sort out this problem?
    Thanks,
    Jayatu

    I am experiencing the exact same issue while configuring for Tibco EMS!!!
    I have also checked the oc4j-xa.xml file etc and I am also unable to find any guidance on the steps required from XML config files through to adapter wizard entries!

  • JMS adapter does not recover from error

    Hello everyone,
    We are noticing some strange behavior with the JMS adapter, and would like your help. We have messages coming into XI from WebSphere MQ. We have configured a Sender Comm channel (MQ_SENDER) with the appropriate JMS adapter, with a specified queue name (TEST.Q) . We have installed the appropriate MQ-JMS libraries for v6.0.
    Here's the problem scenario... initially the application sending the messages to the specified queue was putting an incorrectly formatted MQRFH2 structure in the message. Predictably, this caused our comm channel to fail, and it shows up on the adapter monitor in the failed state with the message "MQJMS1050: The MQRFH2 header has an incorrect format Code: MQJMS1050". This in itself is not a problem, we realized that the application was sending a malformed message. The problem occurs when we fixed the sending application to completely strip out the MQRFH2 header altogether. When the new message is sent, the comm channel seems "stuck" on the previous error, and does not even pick up the new message from the queue. The adapter monitor continues to show the same error for the comm channel. Now when we modified the comm channel to read from a DIFFERENT queue (TEST2.Q) , the comm channel got out of the error state and is able to successfully process new messages coming into that queue. However, when we revert the comm channel back to the original queue (TEST.Q) it reverts back to the original MQJMS1050 error, and does not pick up new messages on the queue.
    Any assistance would be greatly appreciated...

    Hi,
    1) Try to refresh the metadata
    2) Check the Queue status
    3) Once again check the Queue name. try to make the Sender JMS adapter inactive .save  it..again make it active  and  save it and  activate the object.
    4) Refresh the Cache :
    a)Start transaction SXI_CACHE.
    b)From the context menu XI Runtime Cache select Start Complete Cache Refresh.
    If you still face issue try this .
    Many actions require to access System Landscape Directory content from the Integration Builder. To optimize performance, this content is loaded into a cache so that the System Landscape Directory does not have to be accessed directly each time that System Landscape Directory content is required.
    However, this cache is not automatically updated if changes are made to the content of the System Landscape Directory. For this reason that we delete the System Landscape Directory cache if changes have been made to content in the System Landscape Directory. The cache is then filled each time that the System Landscape Directory is accessed. If we log on to the Integration Builder after we have made a change in the SLD, we do not need to delete the SLD cache.
    To clear the SLD cache, from the Integration Builder main menu, choose Environment ® Delete Cache for SLD Data.
    Once we have deleted the cache for SLD data, accessing objects in the SLD may take longer than usual initially.
    Regards
    Agasthuri Doss

  • Jms adapter not polling messages from jms topic

    Hi
    We have a jms adapter configured in BPEL process which need to poll messages from JMS topic.Unfortunately its not polling message from JMS Topic if we add Message Selector and Durable Subscriber properties in jca file.Please find jca file content below
    <adapter-config name="SyncCustomerPartyListCDHJMSConsumer" adapter="JMS Adapter" wsdlLocation="oramds:/apps/AIAMetaData/AIAComponents/ApplicationConnectorServiceLibrary/CDH/V1/ProviderABCS/SyncCustomerPartyListCDHProvABCSImpl.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
      <connection-factory location="eis/jms/aia/syncCustomerParty_cf" UIJmsProvider="WLSJMS" UIConnectionName="Dev"/>
      <endpoint-activation portType="Consume_Message_ptt" operation="Consume_Message">
        <activation-spec className="oracle.tip.adapter.jms.inbound.JmsConsumeActivationSpec">
          <!--property name="DurableSubscriber" value="XYZ"/-->
          <property name="PayloadType" value="TextMessage"/>
          <!--property name="MessageSelector" value="Target in ('XYZ')"/-->
          <property name="UseMessageListener" value="true"/>
          <property name="DestinationName" value="jms/aia/Topic.jms.COMMON.CustomerParty.PUBLISH"/>
        </activation-spec>
      </endpoint-activation>
    </adapter-config>
    If we remove Durable subscriber and message selector properties,its able to poll messages.
    Any pointer will help
    thanks in advance
    Baji

    After changing below property in jca file.JMS adapter is able to poll messages from JMS Topic.
    <property name="UseMessageListener" value="false"/>
    But if i un comment below line and deploy my code again, it stop pulling the messages from topic.
    <property name="DurableSubscriber" value="XYZ"/>
    If i bounce the server after above change and deployment ,it will start polling the message.I am not sure why i need to restart my server after adding above property.
    Thanks
    Baji

  • Wireless adapter name is changing from wlp0s26u1u1 to wlan0

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

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

  • When & Why to Use WL Adapter for MQSeries as compared to MDB?

              We have a need to both send and receive message via MQSeries in asynch mode.
              Initial assessment was to receive messages via MDB and send messages by use a
              pool of Sessions to the MQ Mgr connection.
              Given this why should one use WL Adapter for MQ?
              Thanks
              Tariq.
              

    I assume you are referring to the "WLI" adapter? Perhaps try posting
              your question to the "weblogic.integration.developer" or
              "weblogic.integration.interest" newsgroup.
              If you are referring to the "Messaging Bridge", which comes with
              WebLogic server, then the advantage is that MQ need not be up for the
              senders to continue sending. Senders can send messages to a WebLogic
              queue, which the bridge can in turn forward to an MQ queue. The
              disadvantage is that the extra bridge hop may slow down your app.
              Tom, BEA
              P.S. You are likely by now aware that WL 8.1 (just released in beta),
              can automatically pool foreign (or WebLogic) sessions for you.
              Additionallly, it provides help in that you can configure wrappers for
              foreign JMS objects. See "Accessing JMS Foreign Providers" and
              "Accessing JMS via Servlets and EJBs" listed under new features:
              http://e-docs.bea.com/wls/docs81/notes/new.html#1125379
              Tariq Bhatti wrote:
              > We have a need to both send and receive message via MQSeries in asynch mode.
              > Initial assessment was to receive messages via MDB and send messages by use a
              > pool of Sessions to the MQ Mgr connection.
              >
              > Given this why should one use WL Adapter for MQ?
              >
              > Thanks
              > Tariq.
              >
              

  • MDB,MDB container or JMS adapter stops processing messages from JMS queue

    Hi guys,
    we have created a component using Enterprise Java Beans, let's say a product catalog, deployed it on a Glassfish v2 instance, and connected it to a legacy system using JMS and Sun MQ v4.1 as messaging system. The catalog component thus starts one MDB that listens on a JMS queue, let's say a queue named catalog_business_events_in, and waits for incoming messages, i.e. in our case update events. The problem is, that in general this approach works well, but sometimes the MDBs/JMS adapter stops for some reason fetching and processing messages from the JMS queue. We don't know why - no exceptions, etc.. Seems to be a Glassfish EJB container, JMS adapter or Sun MQ configuration issue. It seems to be that our component is not the problem.
    The messages are compressed/uncompressed by Sun MQ automatically. We actually have 2 Sun MQ instances in clustered mode running to have some kind of failover - no HA cluster, yet. Sun MQ instances are accessed from Glassfish instances running in different Glassfish clusters - so we have a dedicated Sun MQ cluster not a Sun MQ instance per Glassfish instance. Each Glassfish instance is configured such that it knows both Sun MQ instances to allow automatic failover.
    Has someone an idea, why the MDBs/ MDB container/ JMS adapter - stops processing messages? We are kind of puzzled as it happens more often now and apparently when traffic is (very) low not high!
    Thanks for your help.
    Cheers,
    Martin
    Edited by: east1979 on Jan 13, 2009 8:06 AM

    Hi Manoj,
    I have a very similar if not identical issue,
    Error while running realtime jobs that read from JMS tables via JMS MQ adapter:
    15/11/12 09:10:08  JMS GET OPERATION ERROR : TIMEOUT.UNABLE TO RECEIVE RESPONSE FROM THE INVOKED DATA SERVICES SERVICE.ADAPTER OPERA
    TION TO CONTINUE.
    15/11/12 09:10:15  Communication Error. See real time job log for details.
    Dump available:
    https://sapmats.wdf.sap.corp/download/download.cgi?id=5C0KZAHA3RSXBJW3ABLMUUT2P5UUKWO2TM3EJDM5W2HGDZUDID
    Version of DS:14.0.3.273
    Any comments?
    Thansk and kind Regards,
    Kenneth

  • Error in  JMS Adapter  for MQ series

    We have configured a JMS Adpater to connect to  MQ Serries queue manager running on our local server. The XI Server is a remote server where JMS adapter is deployed.
    Upon deployment we see following string in JMS adapter log -
    Sender channel. Details: com.ibm.mq.jms.MQQueueConnectionFactory
    And the status of Adpater is RED.
    The Adpater is configured in sender mode.
    We have created a local queue in Queme Manger and a Server Connectio  channel which is being used in adpater configuration.
    Please suggest what could be the missing link here.
    Appreciate if you can provide us link s to any docuemtn which details the steps to configure an MQ JMS adapter.
    Thanks,
    Garima

    Hi Garima,
    Please check the following:
    1. Add dhbcore.jar also to aii_af_jmsproviderlib.sda and deploy it.
    2. Check the existence of your JMS drivers.
    3. Check the following link and Install the drivers as the way it is mentioned in the guide 'How To Install And Configure External Drivers For JDBC & JMS'
    https://websmp204.sap-ag.de/~form/sapnet?_SHORTKEY=01200252310000071155&_SCENARIO=01100035870000000202
    There are 4 files which needs to be added. http://help.sap.com/saphelp_nw04/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/frameset.htm
    Any of the above solutions should help you solve the problem.
    Regards,
    Abhy

  • Generic JMS Adapter for SeeBeyond

    Hi Guys,
    I am trying to post a mesage on a SeeBeyond JMS queue and so, I have to access it using a JMS Adapter of Generic Type. (as SeeBeyond JMS service does not support a JNDI lookup)
    To do the same, we have already imported all the JAR files needed to access a SeeBeyond JMS service into out XI Server.
    Any help on how to configure a JMS adapter Generically to accees the SeeBeyond JMS in specific or how to configure a Generic JMS adapter would be very helpful.
    Thanks and Regards,
    Bhavesh

    Bump - Were having the same issue.
    Has anyone found a way to connect to Tibco with a user/pwd?
    Version 14.0.297.

  • Configure plain http adapter for receiving message from an external system

    Hi,
    we use Pi/700.
    Now I have an external system and I have to use HTTP (plain) to send messages to XI (via plain http adapter).
    I have no experiences with HTTP!
    In the external system I can only configure "URL, Username, Password" for sending messages - that's all!
    What do I have to configure in XI (communication channel, abap-stack, java-stack,...)?
    I don't know the URL of my XI-system. Is there an transaction code to get this information?
    Why do I need a Username/Pasword?
    For testing I can use a "http-post test tool" I found here in this forum.
    Thank you all for any help!
    Regards
    Wolfgang

    Hi Hummel,
    In Exteranl System u have to use these values
    name="myhost"      value="xiserver"
    name="myport"      value="8000"
    name="mysystem"    value="XY_BSservice"
    name="myinterface" value="Order_out"
    name="mynamespace" value="urn:xi:hcl:powebapp"
    name="myqos"       value="BE"
    name="myclient"    value="300"
    name="myuser"      value="XYZCLNT"
    name="mypass"      value="xiuser"
    Here My system is the Business service created in Integration directory of XI, Interface is the one created in Integration Repository (This is Outbaound from external sys to XI)
    In XI U have to create
    Data Types : 1) Source Structure data type(from extenal sys)
                 2) Target structure (where u want to send from XI)
    Message Types : 2 with above DT's
    Message Interface: 1) Outbound, Async (Order_out)
                       2) Inbound , Async (for the target sys)
    Then Message mapping and Interface mapping as usual..
    And in ID u have to create 2 services one is XY_BSservice for sending system and the other is for receiving system...
    For sending system no communication channel required...
    Hope u will get idea from the above..
    Need any further u r welcome..
    Regards
    Sridhar

Maybe you are looking for

  • My iPhone 4 will charge on a wall socket but WILL NOT charge on computer or even connect to the computer and show up???

    My iPhone 4 will not connect to my MacBookPro. It will not charge on my MacBookPro, but it will charge on a wall socket and it will play music in a 3rd party speaker system?? This is extremely frustrating not only can I not back up my iPhone but I al

  • PHP Startup: Unable to load dynamic library './oci8.so' - ./oci8.so:

    I have oracle 11g, php5, and apache2 are running on server(A). One of my php application need to connect Oracle 10g on server(B). so I have to configure PHP5 and OCI8. Here is what I have done. #env ORACLE_SID=demo ORACLE_BASE=/u01/app/oracle ORACLE_

  • BRCONNECT fails after system copy

    Hi After doing a system copy , in transaction DB13 , all my jobs are failing with "insufficient privileges" . I have already applied the following note 113747 , 583861 and 717677. Please help.............. Job started Step 001 started (program RSDBAJ

  • Tax  Procedure-TAXINJ/TAXINN-----cin

    Hi Gurus, We have a stanrdard pricing procedure like RVAA01 and inthis procedure we maintain all conditions like pricing, discount, frieght, tax..etc., but my doubt is why we need tax pricing procedure specially...like TAXINJ, TAXVAT, TAXINN..? And i

  • Error while calling EAI viewer

    Dear Sir/Mam When i m trying open the autocad or 3-d view in my User Id i received this error "Error while calling EAI viewer" this message occured not to all user if i m using another PC i m able to open the documnet.Please guide Regards kunal