Read out key range in Mainstage via scripter?

Hey people,
I just realized, that scripter seems to be a powerful plugin.
Anyways I didn't find a "detailed" tutorial to the scripter. I found the documentation of apple called "mainstage effects" and it says a bit about the scripter. But I'm wondering (for example), which parameters is the scripter able to get with the function GetParameters? There is no list in the internet, which shows the possible or processable parameters.
The main thing I'm interested in:
Mainstage has a pretty good workflow. But it's anoying that it's not possible to assign the learn-buttons for key ranges to buttons. This would be nice, if I can create two buttons that handle this.
And another thing:
Is the scripter able to read out the key range which is set in the channelstrip and send it out the lowest and highest key as single CC command? (I'm right now into creating a key-light-system, based on to what Native Instruments implemented in their new keyboards).
Thank you very much,
Chris

Here's script for Scripter with a Learn button.
It has an extra parameter for learning.
Hope this helps!
DaCaptain
>>>>>>>
// limit pitch range of notes
var activeNotes = [];
function ParameterChanged(param, value)
    switch(param)
    {                          // if it's the slider you just created
       case 0:  HandleMIDI.maxPitch = value; break;
       case 1:  HandleMIDI.minPitch = value; break;
       case 2:  HandleMIDI.learnState = value;  break;   
function HandleMIDI(event)
  if (event instanceof NoteOn)
    if(HandleMIDI.learnState != 1)
      var pitch = event.pitch;
  if(HandleMIDI.learnState == 0) // first note
     HandleMIDI.minPitch = pitch;
     HandleMIDI.learnState = -1;
     SetParameter('Minimum Pitch', pitch);
  else if(HandleMIDI.learnState == -1)
       HandleMIDI.maxPitch = pitch;    
       SetParameter('Learn', 1); 
       SetParameter('Maximum Pitch', pitch);
  if (event.pitch > HandleMIDI.maxPitch)
  return undefined;  // don't send if too high
  if (event.pitch < HandleMIDI.minPitch)
  return undefined;  // don't send if too low
  else {
  activeNotes.push(event);
  event.send()
  else if (event instanceof NoteOff) {
  for (i=0; i < activeNotes.length; i++) {
  if (event.pitch == activeNotes[i].pitch) {
  event.send();
  activeNotes.splice(i,1);
  break;
  else { // pass non-note events through
  event.send();
var PluginParameters = [
  { name:'Maximum Pitch', type:'lin',
  minValue:0, maxValue:127, numberOfSteps:127, defaultValue:115},
  { name:'Minimum Pitch', type:'lin',
  minValue:0, maxValue:127, numberOfSteps:127, defaultValue:30},
  {name:"Learn", type:"menu", valueStrings:["On", "Off"],
  defaultValue:1}

Similar Messages

  • Auto Notification for reading out of range in IK11.

    Hi,
    Our client requirement is, system should trigger auto notification if measurement reading entered is out of upper and lower limit.
    I have the user exit and code ready with me, But is there any way that we can do this by standard config in SPRO.
    Thanks & Regards,
    Nilesh

    Hi there,
    There is no customizing available to set a auto trigger for a notification. You have to do it with the user exit.
    Regards,
    Johan

  • In MAX my Fieldpoint FP-TC-120 module's CJC is reading "out of range."

    Is this a sign that the module is broken or is there some other explanation? More importantly, is there anything I can do about it?
    Thanks,
    Matt
    Attachments:
    Screen_Shot.bmp ‏2707 KB

    Matt,
    Do you have a TB-3 terminal base for the FP-TC-120? The CJC thermistor is embedded in the TB-3. If you do not have the TB-3 terminal base then that is the issue, if you do then you should try swapping the TB-3 with another one if you have it. Otherwise it sounds like the TB-3 CJC is broken. You can do an RMA by calling 1-877-493-2406.
    Ames
    Applications Engineering
    National Instruments

  • Config copy via snmp - value out of range

    Hi,
    I have problem with configuration file copy via snmp on cisco AP 1121. I use this mib CISCO-CONFIG-COPY-MIB.
    I use this oid's and i get error ".1.3.6.1.4.1.9.9.96.1.1.1.1.16.333: Value out of range (<tftp_server_ip>)""
    snmpset -v1 -c <rwcommunity> <ap_ip> .1.3.6.1.4.1.9.9.96.1.1.1.1.2.333 i 1
    .1.3.6.1.4.1.9.9.96.1.1.1.1.3.333 i 4
    .1.3.6.1.4.1.9.9.96.1.1.1.1.4.333 i 1
    .1.3.6.1.4.1.9.9.96.1.1.1.1.16.333 inetaddress "<tftp_server_ip>"
    .1.3.6.1.4.1.9.9.96.1.1.1.1.16.333: Value out of range (<tftp_server_ip>)
    Any Ideas? Thanks for help.

    Hi,
    I have problem with configuration file copy via snmp on cisco AP 1121. I use this mib CISCO-CONFIG-COPY-MIB.
    I use this oid's and i get error ".1.3.6.1.4.1.9.9.96.1.1.1.1.16.333: Value out of range (<tftp_server_ip>)""
    snmpset -v1 -c <rwcommunity> <ap_ip> .1.3.6.1.4.1.9.9.96.1.1.1.1.2.333 i 1
    .1.3.6.1.4.1.9.9.96.1.1.1.1.3.333 i 4
    .1.3.6.1.4.1.9.9.96.1.1.1.1.4.333 i 1
    .1.3.6.1.4.1.9.9.96.1.1.1.1.16.333 inetaddress "<tftp_server_ip>"
    .1.3.6.1.4.1.9.9.96.1.1.1.1.16.333: Value out of range (<tftp_server_ip>)
    Any Ideas? Thanks for help.

  • How to read out data via usb

    Hello,
    i am trying to get the measurements of a dial indicator, "MarCator 1075", product of Mahr Co. via USB-Cable.
    I installed all the drivers and MAX shows that its a COM-Device and its working properly. So i configured the settings: baud rate 4800, data bits 7, parity even, stop bits 2, apllied and saved the changes.
    I tried those 2 attached VI's, but it doesnt work.
    1. basic_serial_write_and_read.vi is the standard VI for USB-communication of NI.
    2. Sylvac Read.vi is a VI the vendor send after i talked to him to inform me about the dial indicator. He said its a VI to get Data via RS232, but the problem is that i dont have a RS232-slot in my computer. In order to that i have to realize it via USB.
    I think it doesnt work because there are no databits to be read out. When the dataflow arrives the "VISA-Read" theres is an error. This occures in both VI's.
    Error -1073807339 occurred at VISA basic_serial_write_and_read.vi
    Possible reason(s): VISA:  (Hex 0xBFFF0015) Timeout expired before operation completed.
    Anyone who can help me with my issue??
    thx in advance
    best regards
    Attachments:
    basic_serial_write_and_read.vi ‏34 KB
    Sylvac Read.vi ‏22 KB

    Hello FCHansa,
    have you installed the proper drivers?
    Which version of LabVIEW are you using?
    Which OS are you working on?
    In the LabVIEW Example Finder you have a simple example how you can communicate to a USB HW via NI-VISA.
    It's called "Basic TCPIP or USB VISA Write and Read - PDA.lvproj". Or another would be "Basic TCPIP or USB VISA Write and Read - Touch Panel.lvproj"
    Have you configured your USB Device to a virtual COM interface?
    Also please have a look to these links:
    What is the Difference Between USB Raw Control and USB Raw Bulk?
    http://digital.ni.com/public.nsf/allkb/400D6EAB5CFE1C6B86257395005F5D48?OpenDocument
    USB RAW Controller
    https://decibel.ni.com/content/docs/DOC-2022
    Also, please follow the advises of smercurio_fc! As he said you need to know to which commands your Hardware is responding to.
    Best regards,
    Abduelkerim
    Sales
    NI Germany

  • Curve 8310 error Unc.Exception: string index out of range: 0

    I'm getting the following error message: "Uncaught Exception: string index out of range: 0" and no way to clear that message.
    Could someone help me to fix it? Actually the only way to get BB-8310 back working is remove the battery.
    Thanks in adavance
    Solved!
    Go to Solution.

    Hi and Welcome to the Community!!
    There's pretty much no diagnosing those -- they are the equivalent of the random errors in Windows for which tracing the root cause is fruitless. Basically, these are the last out in the programming code -- some event occurred for which there is no handler in the code. The fix is a code update that handles the event...but, again, knowing what the event is is pretty much impossible. So, there are a few things to try:
    Sometimes, the code simply becomes corrupt and needs to be refreshed -- just like a reboot:
    Anytime random strange behavior or sluggishness creeps in, the first thing to do is a battery pop reboot. With power ON, remove the back cover and pull out the battery. Wait about a minute then replace the battery and cover. Power up and wait patiently through the long reboot -- ~5 minutes. See if things have returned to good operation. Like all computing devices, BB's suffer from memory leaks and such...with a hard reboot being the best cure.
    If it won't boot up cleanly, then you may need to try Safe Mode:
    KB17877 How to start a BlackBerry smartphone in safe mode
    There might be an updated code set from the carrier -- check them via this portal:
     http://na.blackberry.com/eng/support/downloads/download_sites.jsp
    The toughest possible cause is a badly behaving app. To find it, there are a couple of options. One is to see if you can read the log file:
    Go to the home screen. Hold down the "alt" key and type 'lglg'. (You will not see anything while you type).This will bring up the log file. Scroll down (probably many pages) untill you see a line that says 'uncaught execption'. Click on this line. The name of the app will be in the info. Alternative methods for bringing up the logs are in this KB:
    KB05349How to enable, access, and extract the event logs on a BlackBerry smartphone
    The other method is to remove apps one at a time, waiting a while in between (I usually recommend a week), until the problem ceases...thereby discovering the offending app. Still another method is to reload the BB OS cleanly, leaving some time between adding other apps onto the BB so as to be able to determine exactly which one is the cause.
    Good luck and let us know!
    Occam's Razor nearly always applies when troubleshooting technology issues!
    If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
    Join our BBM Channels
    BSCF General Channel
    PIN: C0001B7B4   Display/Scan Bar Code
    Knowledge Base Updates
    PIN: C0005A9AA   Display/Scan Bar Code

  • How to get name of the slicer via script

    Hi Gurus,
    I was wondering if we could get the name of the slicer added in IR Query section, via script ??
    That is, I have a bqy connecting to Essbase OLAP.
    Now I am adding a slicer in OLAP Section via script.
    For Ex : ActiveDocument.Sections["Query2"].Slicers.Add('Market.Gen3,Market' , 'Market.LA')
    Now,for some reason, I wanted to retrieve the name of the slicer I added and assign it to a variable. Is this possible ?? I couldn't see any option for this. Please help me out if any one has done this before ?
    Thank You,
    Aji

    Sethil,
    Use your date(let us say Date1) instead of sy-datum.
    CALL FUNCTION 'MONTH_NAMES_GET'
    EXPORTING
    LANGUAGE = SY-LANGU
    IMPORTING
    RETURN_CODE =
    TABLES
    MONTH_NAMES = itab_month
    EXCEPTIONS
    MONTH_NAMES_NOT_FOUND = 1
    OTHERS = 2
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    READ TABLE itab_month
    WITH KEY MNR = date1+4(2).
    itab_month-LTX will contain the value you are looking for
    Good luck
    Raghava

  • Xen Kernel randomly fails to load and goes out of range

    Been having an on/off issue lately that requires a hard reset of my system.  Essentially what happens is the system begins to load when my monitor reports an error that the signal is out of range.  I try to pretend login and reboot, but it does not work.  Instead, I am forced to simply reset the system and once reset it appears to boot OK without any issues.  In fact I can go a few reboots before once again it decides to break.  Below is what should be one of the logs from a failed boot, in fact, the system is in this same failed state right now as well.
    arch_1 ~ :( # journalctl -b -1
    -- Logs begin at Sat 2013-12-28 00:39:50 EST, end at Thu 2014-01-02 23:28:03 EST. --
    Jan 02 23:22:36 arch_1 systemd-journal[129]: Runtime journal is using 332.0K (max 91.3M, leaving 137.0M of fre
    Jan 02 23:22:36 arch_1 systemd-journal[129]: Runtime journal is using 336.0K (max 91.3M, leaving 137.0M of fre
    Jan 02 23:22:36 arch_1 kernel: Initializing cgroup subsys cpuset
    Jan 02 23:22:36 arch_1 kernel: Initializing cgroup subsys cpu
    Jan 02 23:22:36 arch_1 kernel: Initializing cgroup subsys cpuacct
    Jan 02 23:22:36 arch_1 kernel: Linux version 3.12.6-1-ARCH (tobias@T-POWA-LX) (gcc version 4.8.2 (GCC) ) #1 SM
    Jan 02 23:22:36 arch_1 kernel: Command line: /vmlinuz-linux root=/dev/mapper/vg_arch-lv_root rw console=tty0
    Jan 02 23:22:36 arch_1 kernel: Freeing 9e-100 pfn range: 98 pages freed
    Jan 02 23:22:36 arch_1 kernel: 1-1 mapping on 9e->100
    Jan 02 23:22:36 arch_1 kernel: 1-1 mapping on bd9ff->100000
    Jan 02 23:22:36 arch_1 kernel: Released 98 pages of unused memory
    Jan 02 23:22:36 arch_1 kernel: Set 271971 page(s) to 1-1 mapping
    Jan 02 23:22:36 arch_1 kernel: Populating 80000-80062 pfn range: 98 pages added
    Jan 02 23:22:36 arch_1 kernel: e820: BIOS-provided physical RAM map:
    Jan 02 23:22:36 arch_1 kernel: Xen: [mem 0x0000000000000000-0x000000000009dfff] usable
    Jan 02 23:22:36 arch_1 kernel: Xen: [mem 0x00000000000a0000-0x00000000000fffff] reserved
    Jan 02 23:22:36 arch_1 kernel: Xen: [mem 0x0000000000100000-0x00000000bd9fefff] usable
    Jan 02 23:22:36 arch_1 kernel: Xen: [mem 0x00000000bd9ffc00-0x00000000bda53bff] ACPI NVS
    Jan 02 23:22:36 arch_1 kernel: Xen: [mem 0x00000000bda53c00-0x00000000bda55bff] ACPI data
    Jan 02 23:22:36 arch_1 kernel: Xen: [mem 0x00000000bda55c00-0x00000000bfffffff] reserved
    Jan 02 23:22:36 arch_1 kernel: Xen: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
    Jan 02 23:22:36 arch_1 kernel: Xen: [mem 0x00000000fec00000-0x00000000fed003ff] reserved
    Jan 02 23:22:36 arch_1 kernel: Xen: [mem 0x00000000fed20000-0x00000000fed9ffff] reserved
    Jan 02 23:22:36 arch_1 kernel: Xen: [mem 0x00000000fee00000-0x00000000feefffff] reserved
    Jan 02 23:22:36 arch_1 kernel: Xen: [mem 0x00000000ffb00000-0x00000000ffffffff] reserved
    Jan 02 23:22:36 arch_1 kernel: Xen: [mem 0x0000000100000000-0x0000000237ffffff] usable
    Jan 02 23:22:36 arch_1 kernel: NX (Execute Disable) protection: active
    Jan 02 23:22:36 arch_1 kernel: SMBIOS 2.5 present.
    Jan 02 23:22:36 arch_1 kernel: DMI: Dell Inc. OptiPlex 960 /0Y958C, BIOS A10 12/20/2010
    Jan 02 23:22:36 arch_1 kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
    Jan 02 23:22:36 arch_1 kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
    Jan 02 23:22:36 arch_1 kernel: No AGP bridge found
    Jan 02 23:22:36 arch_1 kernel: e820: last_pfn = 0x238000 max_arch_pfn = 0x400000000
    Jan 02 23:22:36 arch_1 kernel: e820: last_pfn = 0xbd9ff max_arch_pfn = 0x400000000
    Jan 02 23:22:36 arch_1 kernel: Scanning 1 areas for low memory corruption
    Jan 02 23:22:36 arch_1 kernel: Base memory trampoline at [ffff880000098000] 98000 size 24576
    Jan 02 23:22:36 arch_1 kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
    Jan 02 23:22:36 arch_1 kernel: [mem 0x00000000-0x000fffff] page 4k
    Jan 02 23:22:36 arch_1 kernel: init_memory_mapping: [mem 0x7fe00000-0x7fffffff]
    Jan 02 23:22:36 arch_1 kernel: [mem 0x7fe00000-0x7fffffff] page 4k
    Jan 02 23:22:36 arch_1 kernel: BRK [0x01b47000, 0x01b47fff] PGTABLE
    Jan 02 23:22:36 arch_1 kernel: BRK [0x01b48000, 0x01b48fff] PGTABLE
    Jan 02 23:22:36 arch_1 kernel: init_memory_mapping: [mem 0x7c000000-0x7fdfffff]
    Jan 02 23:22:36 arch_1 kernel: [mem 0x7c000000-0x7fdfffff] page 4k
    Jan 02 23:22:36 arch_1 kernel: BRK [0x01b49000, 0x01b49fff] PGTABLE
    Jan 02 23:22:36 arch_1 kernel: BRK [0x01b4a000, 0x01b4afff] PGTABLE
    Jan 02 23:22:36 arch_1 kernel: BRK [0x01b4b000, 0x01b4bfff] PGTABLE
    Jan 02 23:22:36 arch_1 kernel: BRK [0x01b4c000, 0x01b4cfff] PGTABLE
    Jan 02 23:22:36 arch_1 kernel: init_memory_mapping: [mem 0x00100000-0x7bffffff]
    Jan 02 23:22:36 arch_1 kernel: [mem 0x00100000-0x7bffffff] page 4k
    Jan 02 23:22:36 arch_1 kernel: init_memory_mapping: [mem 0x80000000-0xbd9fefff]
    Jan 02 23:22:36 arch_1 kernel: [mem 0x80000000-0xbd9fefff] page 4k
    Jan 02 23:22:36 arch_1 kernel: init_memory_mapping: [mem 0x100000000-0x237ffffff]
    Jan 02 23:22:36 arch_1 kernel: [mem 0x100000000-0x237ffffff] page 4k
    Jan 02 23:22:36 arch_1 kernel: RAMDISK: [mem 0x01f54000-0x029fefff]
    Jan 02 23:22:36 arch_1 kernel: ACPI: RSDP 00000000000fec00 00024 (v02 DELL )
    Jan 02 23:22:36 arch_1 kernel: ACPI: XSDT 00000000000fc7d7 00084 (v01 DELL B10K 00000015 ASL 00000061)
    Jan 02 23:22:36 arch_1 kernel: ACPI: FACP 00000000000fc907 000F4 (v03 DELL B10K 00000015 ASL 00000061)
    Jan 02 23:22:36 arch_1 kernel: ACPI: DSDT 00000000ffe9e423 05744 (v01 DELL dt_ex 00001000 INTL 20050624)
    Jan 02 23:22:36 arch_1 kernel: ACPI: FACS 00000000bd9ffc00 00040
    Jan 02 23:22:36 arch_1 kernel: ACPI: SSDT 00000000ffea3d30 00087 (v01 DELL st_ex 00001000 INTL 20050624)
    Jan 02 23:22:36 arch_1 kernel: ACPI: APIC 00000000000fc9fb 00092 (v01 DELL B10K 00000015 ASL 00000061)
    Jan 02 23:22:36 arch_1 kernel: ACPI: BOOT 00000000000fca8d 00028 (v01 DELL B10K 00000015 ASL 00000061)
    Jan 02 23:22:36 arch_1 kernel: ACPI: ASF! 00000000000fcab5 00096 (v32 DELL B10K 00000015 ASL 00000061)
    Jan 02 23:22:36 arch_1 kernel: ACPI: MCFG 00000000000fcb4b 0003C (v01 DELL B10K 00000015 ASL 00000061)
    Jan 02 23:22:36 arch_1 kernel: ACPI: HPET 00000000000fcb87 00038 (v01 DELL B10K 00000015 ASL 00000061)
    Jan 02 23:22:36 arch_1 kernel: ACPI: TCPA 00000000000fcde3 00032 (v01 DELL B10K 00000015 ASL 00000061)
    Jan 02 23:22:36 arch_1 kernel: ACPI: DMAR 00000000000fce15 00108 (v01 DELL B10K 00000015 ASL 00000061)
    Jan 02 23:22:36 arch_1 kernel: ACPI: SSDT 00000000bd9ffc40 001F9 (v01 DpgPmm Cpu0Ist 00000011 INTL 20050624)
    Jan 02 23:22:36 arch_1 kernel: ACPI: SSDT 00000000bda00049 001F9 (v01 DpgPmm Cpu1Ist 00000011 INTL 20050624)
    Jan 02 23:22:36 arch_1 kernel: ACPI: SSDT 00000000bda00452 00190 (v01 DpgPmm CpuPm 00000010 INTL 20050624)
    Jan 02 23:22:36 arch_1 kernel: ACPI: Local APIC address 0xfee00000
    Jan 02 23:22:36 arch_1 kernel: NUMA turned off
    Jan 02 23:22:36 arch_1 kernel: Faking a node at [mem 0x0000000000000000-0x0000000237ffffff]
    Jan 02 23:22:36 arch_1 kernel: Initmem setup node 0 [mem 0x00000000-0x237ffffff]
    Jan 02 23:22:36 arch_1 kernel: NODE_DATA [mem 0x7f0c7000-0x7f0cbfff]
    Jan 02 23:22:36 arch_1 kernel: Zone ranges:
    Jan 02 23:22:36 arch_1 kernel: DMA [mem 0x00001000-0x00ffffff]
    Jan 02 23:22:36 arch_1 kernel: DMA32 [mem 0x01000000-0xffffffff]
    Jan 02 23:22:36 arch_1 kernel: Normal [mem 0x100000000-0x237ffffff]
    Jan 02 23:22:36 arch_1 kernel: Movable zone start for each node
    Jan 02 23:22:36 arch_1 kernel: Early memory node ranges
    Jan 02 23:22:36 arch_1 kernel: node 0: [mem 0x00001000-0x0009dfff]
    Jan 02 23:22:36 arch_1 kernel: node 0: [mem 0x00100000-0xbd9fefff]
    Jan 02 23:22:36 arch_1 kernel: node 0: [mem 0x100000000-0x237ffffff]
    Jan 02 23:22:36 arch_1 kernel: On node 0 totalpages: 2054556
    Jan 02 23:22:36 arch_1 kernel: DMA zone: 64 pages used for memmap
    Jan 02 23:22:36 arch_1 kernel: DMA zone: 21 pages reserved
    Jan 02 23:22:36 arch_1 kernel: DMA zone: 3997 pages, LIFO batch:0
    Jan 02 23:22:36 arch_1 kernel: DMA32 zone: 12072 pages used for memmap
    Jan 02 23:22:36 arch_1 kernel: DMA32 zone: 772607 pages, LIFO batch:31
    Jan 02 23:22:36 arch_1 kernel: Normal zone: 19968 pages used for memmap
    Jan 02 23:22:36 arch_1 kernel: Normal zone: 1277952 pages, LIFO batch:31
    Jan 02 23:22:36 arch_1 kernel: ACPI: PM-Timer IO Port: 0x808
    Jan 02 23:22:36 arch_1 kernel: ACPI: Local APIC address 0xfee00000
    Jan 02 23:22:36 arch_1 kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
    Jan 02 23:22:36 arch_1 kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
    Jan 02 23:22:36 arch_1 kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x05] disabled)
    Jan 02 23:22:36 arch_1 kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x07] disabled)
    Jan 02 23:22:36 arch_1 kernel: ACPI: LAPIC (acpi_id[0x05] lapic_id[0x00] disabled)
    Jan 02 23:22:36 arch_1 kernel: ACPI: LAPIC (acpi_id[0x06] lapic_id[0x01] disabled)
    Jan 02 23:22:36 arch_1 kernel: ACPI: LAPIC (acpi_id[0x07] lapic_id[0x02] disabled)
    Jan 02 23:22:36 arch_1 kernel: ACPI: LAPIC (acpi_id[0x08] lapic_id[0x03] disabled)
    Jan 02 23:22:36 arch_1 kernel: ACPI: LAPIC_NMI (acpi_id[0xff] high level lint[0x1])
    Jan 02 23:22:36 arch_1 kernel: ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
    Jan 02 23:22:36 arch_1 kernel: IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
    Jan 02 23:22:36 arch_1 kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    Jan 02 23:22:36 arch_1 kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    Jan 02 23:22:36 arch_1 kernel: ACPI: IRQ0 used by override.
    Jan 02 23:22:36 arch_1 kernel: ACPI: IRQ2 used by override.
    Jan 02 23:22:36 arch_1 kernel: ACPI: IRQ9 used by override.
    Jan 02 23:22:36 arch_1 kernel: Using ACPI (MADT) for SMP configuration information
    Jan 02 23:22:36 arch_1 kernel: ACPI: HPET id: 0x8086a701 base: 0xfed00000
    Jan 02 23:22:36 arch_1 kernel: smpboot: Allowing 8 CPUs, 6 hotplug CPUs
    Jan 02 23:22:36 arch_1 kernel: nr_irqs_gsi: 40
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0x0009e000-0x0009ffff]
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000fffff]
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0xbd9ff000-0xbd9fffff]
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0xbda00000-0xbda52fff]
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0xbda53000-0xbda53fff]
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0xbda54000-0xbda54fff]
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0xbda55000-0xbda55fff]
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0xbda56000-0xbfffffff]
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0xc0000000-0xf7ffffff]
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0xfc000000-0xfebfffff]
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0xfec00000-0xfecfffff]
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0xfed00000-0xfed1ffff]
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0xfed20000-0xfed9ffff]
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0xfeda0000-0xfedfffff]
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0xfee00000-0xfeefffff]
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0xfef00000-0xffafffff]
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0xffb00000-0xffffffff]
    Jan 02 23:22:36 arch_1 kernel: e820: [mem 0xc0000000-0xf7ffffff] available for PCI devices
    Jan 02 23:22:36 arch_1 kernel: Booting paravirtualized kernel on Xen
    Jan 02 23:22:36 arch_1 kernel: Xen version: 4.3.1 (preserve-AD)
    Jan 02 23:22:36 arch_1 kernel: setup_percpu: NR_CPUS:128 nr_cpumask_bits:128 nr_cpu_ids:8 nr_node_ids:1
    Jan 02 23:22:36 arch_1 kernel: PERCPU: Embedded 29 pages/cpu @ffff88007ee00000 s86464 r8192 d24128 u262144
    Jan 02 23:22:36 arch_1 kernel: pcpu-alloc: s86464 r8192 d24128 u262144 alloc=1*2097152
    Jan 02 23:22:36 arch_1 kernel: pcpu-alloc: [0] 0 1 2 3 4 5 6 7
    Jan 02 23:22:36 arch_1 kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 2022431
    Jan 02 23:22:36 arch_1 kernel: Policy zone: Normal
    Jan 02 23:22:36 arch_1 kernel: Kernel command line: /vmlinuz-linux root=/dev/mapper/vg_arch-lv_root rw console
    Jan 02 23:22:36 arch_1 kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
    Jan 02 23:22:36 arch_1 kernel: xsave: enabled xstate_bv 0x3, cntxt size 0x240
    Jan 02 23:22:36 arch_1 kernel: software IO TLB [mem 0x72a00000-0x76a00000] (64MB) mapped at [ffff880072a00000-
    Jan 02 23:22:36 arch_1 kernel: Memory: 1857868K/8218224K available (5124K kernel code, 807K rwdata, 1628K roda
    Jan 02 23:22:36 arch_1 kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
    Jan 02 23:22:36 arch_1 kernel: Preemptible hierarchical RCU implementation.
    Jan 02 23:22:36 arch_1 kernel: RCU dyntick-idle grace-period acceleration is enabled.
    Jan 02 23:22:36 arch_1 kernel: Dump stacks of tasks blocking RCU-preempt GP.
    Jan 02 23:22:36 arch_1 kernel: RCU restricting CPUs from NR_CPUS=128 to nr_cpu_ids=2.
    Jan 02 23:22:36 arch_1 kernel: NR_IRQS:8448 nr_irqs:512 16
    Jan 02 23:22:36 arch_1 kernel: xen: sci override: global_irq=9 trigger=0 polarity=0
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 9 triggering 0 polarity 0
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=9 -> irq=9 (gsi=9)
    Jan 02 23:22:36 arch_1 kernel: xen: acpi sci 9
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=1 -> irq=1 (gsi=1)
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=2 -> irq=2 (gsi=2)
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=3 -> irq=3 (gsi=3)
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=4 -> irq=4 (gsi=4)
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=5 -> irq=5 (gsi=5)
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=6 -> irq=6 (gsi=6)
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=7 -> irq=7 (gsi=7)
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=8 -> irq=8 (gsi=8)
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=10 -> irq=10 (gsi=10)
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=11 -> irq=11 (gsi=11)
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=12 -> irq=12 (gsi=12)
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=13 -> irq=13 (gsi=13)
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=14 -> irq=14 (gsi=14)
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=15 -> irq=15 (gsi=15)
    Jan 02 23:22:36 arch_1 kernel: Console: colour VGA+ 80x25
    Jan 02 23:22:36 arch_1 kernel: console [tty0] enabled
    Jan 02 23:22:36 arch_1 kernel: allocated 33030144 bytes of page_cgroup
    Jan 02 23:22:36 arch_1 kernel: please try 'cgroup_disable=memory' option if you don't want memory cgroups
    Jan 02 23:22:36 arch_1 kernel: Xen: using vcpuop timer interface
    Jan 02 23:22:36 arch_1 kernel: installing Xen timer for CPU 0
    Jan 02 23:22:36 arch_1 kernel: tsc: Detected 2992.224 MHz processor
    Jan 02 23:22:36 arch_1 kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 5986
    Jan 02 23:22:36 arch_1 kernel: pid_max: default: 32768 minimum: 301
    Jan 02 23:22:36 arch_1 kernel: Security Framework initialized
    Jan 02 23:22:36 arch_1 kernel: AppArmor: AppArmor disabled by boot time parameter
    Jan 02 23:22:36 arch_1 kernel: Yama: becoming mindful.
    Jan 02 23:22:36 arch_1 kernel: Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
    Jan 02 23:22:36 arch_1 kernel: Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
    Jan 02 23:22:36 arch_1 kernel: Mount-cache hash table entries: 256
    Jan 02 23:22:36 arch_1 kernel: Initializing cgroup subsys memory
    Jan 02 23:22:36 arch_1 kernel: Initializing cgroup subsys devices
    Jan 02 23:22:36 arch_1 kernel: Initializing cgroup subsys freezer
    Jan 02 23:22:36 arch_1 kernel: Initializing cgroup subsys net_cls
    Jan 02 23:22:36 arch_1 kernel: Initializing cgroup subsys blkio
    Jan 02 23:22:36 arch_1 kernel: CPU: Physical Processor ID: 0
    Jan 02 23:22:36 arch_1 kernel: CPU: Processor Core ID: 0
    Jan 02 23:22:36 arch_1 kernel: mce: CPU supports 2 MCE banks
    Jan 02 23:22:36 arch_1 kernel: Last level iTLB entries: 4KB 128, 2MB 4, 4MB 4
    Last level dTLB entries: 4KB 256, 2MB 0, 4MB 32
    tlb_flushall_shift: -1
    Jan 02 23:22:36 arch_1 kernel: Freeing SMP alternatives memory: 20K (ffffffff819e9000 - ffffffff819ee000)
    Jan 02 23:22:36 arch_1 kernel: ACPI: Core revision 20130725
    Jan 02 23:22:36 arch_1 kernel: ACPI: All ACPI Tables successfully acquired
    Jan 02 23:22:36 arch_1 kernel: ftrace: allocating 20318 entries in 80 pages
    Jan 02 23:22:36 arch_1 kernel: Performance Events: unsupported p6 CPU model 23 no PMU driver, software events
    Jan 02 23:22:36 arch_1 kernel: NMI watchdog: disabled (cpu0): hardware events not enabled
    Jan 02 23:22:36 arch_1 kernel: installing Xen timer for CPU 1
    Jan 02 23:22:36 arch_1 kernel: Brought up 2 CPUs
    Jan 02 23:22:36 arch_1 kernel: devtmpfs: initialized
    Jan 02 23:22:36 arch_1 kernel: PM: Registering ACPI NVS region [mem 0xbd9ffc00-0xbda53bff] (344064 bytes)
    Jan 02 23:22:36 arch_1 kernel: xen:grant_table: Grant tables using version 2 layout
    Jan 02 23:22:36 arch_1 kernel: Grant table initialized
    Jan 02 23:22:36 arch_1 kernel: RTC time: 4:22:33, date: 01/03/14
    Jan 02 23:22:36 arch_1 kernel: NET: Registered protocol family 16
    Jan 02 23:22:36 arch_1 kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
    Jan 02 23:22:36 arch_1 kernel: ACPI: bus type PCI registered
    Jan 02 23:22:36 arch_1 kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
    Jan 02 23:22:36 arch_1 kernel: PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base
    Jan 02 23:22:36 arch_1 kernel: PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
    Jan 02 23:22:36 arch_1 kernel: PCI: Using configuration type 1 for base access
    Jan 02 23:22:36 arch_1 kernel: dmi type 0xB1 record - unknown flag
    Jan 02 23:22:36 arch_1 kernel: bio: create slab <bio-0> at 0
    Jan 02 23:22:36 arch_1 kernel: ACPI: Added _OSI(Module Device)
    Jan 02 23:22:36 arch_1 kernel: ACPI: Added _OSI(Processor Device)
    Jan 02 23:22:36 arch_1 kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
    Jan 02 23:22:36 arch_1 kernel: ACPI: Added _OSI(Processor Aggregator Device)
    Jan 02 23:22:36 arch_1 kernel: ACPI: EC: Look up EC in DSDT
    Jan 02 23:22:36 arch_1 kernel: [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
    Jan 02 23:22:36 arch_1 kernel: ACPI BIOS Warning (bug): Incorrect checksum in table [TCPA] - 0x00, should be 0
    Jan 02 23:22:36 arch_1 kernel: ACPI: Interpreter enabled
    Jan 02 23:22:36 arch_1 kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20130725/hw
    Jan 02 23:22:36 arch_1 kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20130725/hw
    Jan 02 23:22:36 arch_1 kernel: ACPI: (supports S0 S1 S4 S5)
    Jan 02 23:22:36 arch_1 kernel: ACPI: Using IOAPIC for interrupt routing
    Jan 02 23:22:36 arch_1 kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and rep
    Jan 02 23:22:36 arch_1 kernel: ACPI: ACPI Dock Station Driver: 1 docks/bays found
    Jan 02 23:22:36 arch_1 kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
    Jan 02 23:22:36 arch_1 kernel: acpi PNP0A03:00: ACPI _OSC support notification failed, disabling PCIe ASPM
    Jan 02 23:22:36 arch_1 kernel: acpi PNP0A03:00: Unable to request _OSC control (_OSC support mask: 0x08)
    Jan 02 23:22:36 arch_1 kernel: acpi PNP0A03:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only par
    Jan 02 23:22:36 arch_1 kernel: PCI host bridge to bus 0000:00
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: root bus resource [bus 00-ff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000effff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: root bus resource [mem 0x000f0000-0x000fffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: root bus resource [mem 0xfc000000-0xfec00000]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: root bus resource [mem 0xbdb00000-0xf7ffffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: root bus resource [mem 0xff980000-0xff980fff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: root bus resource [mem 0xff97c000-0xff97ffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: root bus resource [mem 0xff970000-0xff9707ff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: root bus resource [mem 0xfed20000-0xfed9ffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: root bus resource [mem 0xfeda6000-0xfeda6fff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: root bus resource [mem 0xfeda7000-0xfeda7fff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:00.0: [8086:2e10] type 00 class 0x060000
    Jan 02 23:22:36 arch_1 kernel: DMAR: Forcing write-buffer flush capability
    Jan 02 23:22:36 arch_1 kernel: DMAR: Disabling IOMMU for graphics on this chipset
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:01.0: [8086:2e11] type 01 class 0x060400
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:01.0: System wakeup disabled by ACPI
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:02.0: [8086:2e12] type 00 class 0x030000
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:02.0: reg 0x10: [mem 0xf7c00000-0xf7ffffff 64bit]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:02.0: reg 0x18: [mem 0xe0000000-0xefffffff 64bit pref]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:02.0: reg 0x20: [io 0xecb0-0xecb7]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:02.1: [8086:2e13] type 00 class 0x038000
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:02.1: reg 0x10: [mem 0xf7b00000-0xf7bfffff 64bit]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:03.0: [8086:2e14] type 00 class 0x078000
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:03.0: reg 0x10: [mem 0xfeda6000-0xfeda600f 64bit]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:03.2: [8086:2e16] type 00 class 0x010185
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:03.2: reg 0x10: [io 0xfe80-0xfe87]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:03.2: reg 0x14: [io 0xfe90-0xfe93]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:03.2: reg 0x18: [io 0xfea0-0xfea7]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:03.2: reg 0x1c: [io 0xfeb0-0xfeb3]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:03.2: reg 0x20: [io 0xfef0-0xfeff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:03.3: [8086:2e17] type 00 class 0x070002
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:03.3: reg 0x10: [io 0xecb8-0xecbf]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:03.3: reg 0x14: [mem 0xf7adc000-0xf7adcfff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:19.0: [8086:10de] type 00 class 0x020000
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:19.0: reg 0x10: [mem 0xf7ae0000-0xf7afffff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:19.0: reg 0x14: [mem 0xf7add000-0xf7addfff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:19.0: reg 0x18: [io 0xece0-0xecff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:19.0: PME# supported from D0 D3hot D3cold
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1a.0: [8086:3a67] type 00 class 0x0c0300
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1a.0: reg 0x20: [io 0xff20-0xff3f]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1a.0: System wakeup disabled by ACPI
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1a.1: [8086:3a68] type 00 class 0x0c0300
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1a.1: reg 0x20: [io 0xff00-0xff1f]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1a.1: System wakeup disabled by ACPI
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1a.2: [8086:3a69] type 00 class 0x0c0300
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1a.2: reg 0x20: [io 0xfc00-0xfc1f]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1a.2: System wakeup disabled by ACPI
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1a.7: [8086:3a6c] type 00 class 0x0c0320
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1a.7: reg 0x10: [mem 0xf7ade000-0xf7ade3ff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.0: [8086:3a70] type 01 class 0x060400
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.0: System wakeup disabled by ACPI
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.1: [8086:3a72] type 01 class 0x060400
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.1: System wakeup disabled by ACPI
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1d.0: [8086:3a64] type 00 class 0x0c0300
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1d.0: reg 0x20: [io 0xff80-0xff9f]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1d.0: System wakeup disabled by ACPI
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1d.1: [8086:3a65] type 00 class 0x0c0300
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1d.1: reg 0x20: [io 0xff60-0xff7f]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1d.1: System wakeup disabled by ACPI
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1d.2: [8086:3a66] type 00 class 0x0c0300
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1d.2: reg 0x20: [io 0xff40-0xff5f]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1d.2: System wakeup disabled by ACPI
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1d.7: [8086:3a6a] type 00 class 0x0c0320
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1d.7: reg 0x10: [mem 0xff980000-0xff9803ff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: [8086:244e] type 01 class 0x060401
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: System wakeup disabled by ACPI
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1f.0: [8086:3a14] type 00 class 0x060100
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1f.2: [8086:3a02] type 00 class 0x010601
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1f.2: reg 0x10: [io 0xfe00-0xfe07]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1f.2: reg 0x14: [io 0xfe10-0xfe13]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1f.2: reg 0x18: [io 0xfe20-0xfe27]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1f.2: reg 0x1c: [io 0xfe30-0xfe33]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1f.2: reg 0x20: [io 0xfec0-0xfedf]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1f.2: reg 0x24: [mem 0xff970000-0xff9707ff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1f.2: PME# supported from D3hot
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1f.3: [8086:3a60] type 00 class 0x0c0500
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1f.3: reg 0x10: [mem 0xf7adf000-0xf7adf0ff 64bit]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1f.3: reg 0x20: [io 0x0940-0x095f]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:01:00.0: [8086:105e] type 00 class 0x020000
    Jan 02 23:22:36 arch_1 kernel: pci 0000:01:00.0: reg 0x10: [mem 0xf7880000-0xf789ffff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:01:00.0: reg 0x14: [mem 0xf78a0000-0xf78bffff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:01:00.0: reg 0x18: [io 0xdcc0-0xdcdf]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:01:00.0: reg 0x30: [mem 0xf7900000-0xf791ffff pref]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:01:00.0: PME# supported from D0 D3hot D3cold
    Jan 02 23:22:36 arch_1 kernel: pci 0000:01:00.1: [8086:105e] type 00 class 0x020000
    Jan 02 23:22:36 arch_1 kernel: pci 0000:01:00.1: reg 0x10: [mem 0xf78c0000-0xf78dffff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:01:00.1: reg 0x14: [mem 0xf78e0000-0xf78fffff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:01:00.1: reg 0x18: [io 0xdce0-0xdcff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:01:00.1: PME# supported from D0 D3hot D3cold
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:01.0: bridge window [io 0xd000-0xdfff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:01.0: bridge window [mem 0xf7800000-0xf79fffff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.0: PCI bridge to [bus 02]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.0: bridge window [mem 0xf7700000-0xf77fffff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.1: PCI bridge to [bus 03]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.1: bridge window [mem 0xf7600000-0xf76fffff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:04:00.0: [1102:0007] type 00 class 0x040100
    Jan 02 23:22:36 arch_1 kernel: pci 0000:04:00.0: reg 0x10: [io 0xcce0-0xccff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:04:00.0: supports D1 D2
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: PCI bridge to [bus 04] (subtractive decode)
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: bridge window [io 0xc000-0xcfff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: bridge window [io 0x0d00-0xffff] (subtractive decode)
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive deco
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: bridge window [mem 0x000c0000-0x000effff] (subtractive deco
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: bridge window [mem 0x000f0000-0x000fffff] (subtractive deco
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: bridge window [mem 0xfc000000-0xfec00000] (subtractive deco
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: bridge window [mem 0xbdb00000-0xf7ffffff] (subtractive deco
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: bridge window [mem 0xff980000-0xff980fff] (subtractive deco
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: bridge window [mem 0xff97c000-0xff97ffff] (subtractive deco
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: bridge window [mem 0xff970000-0xff9707ff] (subtractive deco
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: bridge window [mem 0xfed20000-0xfed9ffff] (subtractive deco
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: bridge window [mem 0xfeda6000-0xfeda6fff] (subtractive deco
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: bridge window [mem 0xfeda7000-0xfeda7fff] (subtractive deco
    Jan 02 23:22:36 arch_1 kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 15)
    Jan 02 23:22:36 arch_1 kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 *5 6 7 9 10 11 12 15)
    Jan 02 23:22:36 arch_1 kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 *9 10 11 12 15)
    Jan 02 23:22:36 arch_1 kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 *10 11 12 15)
    Jan 02 23:22:36 arch_1 kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 11 12 15) *0, disabled.
    Jan 02 23:22:36 arch_1 kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 *4 5 6 7 9 10 11 12 15)
    Jan 02 23:22:36 arch_1 kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 *5 6 7 9 10 11 12 15)
    Jan 02 23:22:36 arch_1 kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs *3 4 5 6 7 9 10 11 12 15)
    Jan 02 23:22:36 arch_1 kernel: ACPI: Enabled 2 GPEs in block 00 to 3F
    Jan 02 23:22:36 arch_1 kernel: ACPI: \_SB_.PCI0: notify handler is installed
    Jan 02 23:22:36 arch_1 kernel: Found 1 acpi root devices
    Jan 02 23:22:36 arch_1 kernel: xen:balloon: Initialising balloon driver
    Jan 02 23:22:36 arch_1 kernel: xen_balloon: Initialising balloon driver
    Jan 02 23:22:36 arch_1 kernel: vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
    Jan 02 23:22:36 arch_1 kernel: vgaarb: loaded
    Jan 02 23:22:36 arch_1 kernel: vgaarb: bridge control possible 0000:00:02.0
    Jan 02 23:22:36 arch_1 kernel: PCI: Using ACPI for IRQ routing
    Jan 02 23:22:36 arch_1 kernel: PCI: pci_cache_line_size set to 64 bytes
    Jan 02 23:22:36 arch_1 kernel: Expanded resource reserved due to conflict with PCI Bus 0000:00
    Jan 02 23:22:36 arch_1 kernel: Expanded resource reserved due to conflict with PCI Bus 0000:00
    Jan 02 23:22:36 arch_1 kernel: e820: reserve RAM buffer [mem 0x0009e000-0x0009ffff]
    Jan 02 23:22:36 arch_1 kernel: e820: reserve RAM buffer [mem 0xbd9ff000-0xbfffffff]
    Jan 02 23:22:36 arch_1 kernel: NetLabel: Initializing
    Jan 02 23:22:36 arch_1 kernel: NetLabel: domain hash size = 128
    Jan 02 23:22:36 arch_1 kernel: NetLabel: protocols = UNLABELED CIPSOv4
    Jan 02 23:22:36 arch_1 kernel: NetLabel: unlabeled traffic allowed by default
    Jan 02 23:22:36 arch_1 kernel: Switched to clocksource xen
    Jan 02 23:22:36 arch_1 kernel: pnp: PnP ACPI init
    Jan 02 23:22:36 arch_1 kernel: ACPI: bus type PNP registered
    Jan 02 23:22:36 arch_1 kernel: system 00:00: [io 0x0800-0x085f] could not be reserved
    Jan 02 23:22:36 arch_1 kernel: system 00:00: [io 0x0c00-0x0c7f] has been reserved
    Jan 02 23:22:36 arch_1 kernel: system 00:00: [io 0x0860-0x08ff] has been reserved
    Jan 02 23:22:36 arch_1 kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
    Jan 02 23:22:36 arch_1 kernel: pnp 00:01: [dma 4]
    Jan 02 23:22:36 arch_1 kernel: pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 13 triggering 1 polarity 0
    Jan 02 23:22:36 arch_1 kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0c04 (active)
    Jan 02 23:22:36 arch_1 kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0800 (active)
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 8 triggering 1 polarity 0
    Jan 02 23:22:36 arch_1 kernel: pnp 00:04: Plug and Play ACPI device, IDs PNP0b00 (active)
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 6 triggering 1 polarity 0
    Jan 02 23:22:36 arch_1 kernel: pnp 00:05: [dma 2]
    Jan 02 23:22:36 arch_1 kernel: pnp 00:05: Plug and Play ACPI device, IDs PNP0700 (active)
    Jan 02 23:22:36 arch_1 kernel: pnp 00:06: Plug and Play ACPI device, IDs PNP0103 (active)
    Jan 02 23:22:36 arch_1 kernel: pnp: PnP ACPI: found 7 devices
    Jan 02 23:22:36 arch_1 kernel: ACPI: bus type PNP unregistered
    Jan 02 23:22:36 arch_1 kernel: PM-Timer failed consistency check (0xffffff) - aborting.
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.0: bridge window [io 0x1000-0x0fff] to [bus 02] add_size 1000
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.1: bridge window [io 0x1000-0x0fff] to [bus 03] add_size 1000
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.1: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_si
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.1: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_si
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.0: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.1: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.0: BAR 15: assigned [mem 0xfc000000-0xfc1fffff 64bit pref]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.1: BAR 15: assigned [mem 0xfc200000-0xfc3fffff 64bit pref]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.0: BAR 13: assigned [io 0x1000-0x1fff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.1: BAR 13: assigned [io 0x2000-0x2fff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:01.0: bridge window [io 0xd000-0xdfff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:01.0: bridge window [mem 0xf7800000-0xf79fffff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.0: PCI bridge to [bus 02]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.0: bridge window [io 0x1000-0x1fff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.0: bridge window [mem 0xf7700000-0xf77fffff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.0: bridge window [mem 0xfc000000-0xfc1fffff 64bit pref]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.1: PCI bridge to [bus 03]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.1: bridge window [io 0x2000-0x2fff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.1: bridge window [mem 0xf7600000-0xf76fffff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.1: bridge window [mem 0xfc200000-0xfc3fffff 64bit pref]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: PCI bridge to [bus 04]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: bridge window [io 0xc000-0xcfff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: resource 7 [mem 0x000c0000-0x000effff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: resource 8 [mem 0x000f0000-0x000fffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: resource 9 [mem 0xfc000000-0xfec00000]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: resource 10 [mem 0xbdb00000-0xf7ffffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: resource 11 [mem 0xff980000-0xff980fff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: resource 12 [mem 0xff97c000-0xff97ffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: resource 13 [mem 0xff970000-0xff9707ff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: resource 14 [mem 0xfed20000-0xfed9ffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: resource 15 [mem 0xfeda6000-0xfeda6fff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: resource 16 [mem 0xfeda7000-0xfeda7fff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:01: resource 0 [io 0xd000-0xdfff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:01: resource 1 [mem 0xf7800000-0xf79fffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:02: resource 0 [io 0x1000-0x1fff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:02: resource 1 [mem 0xf7700000-0xf77fffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:02: resource 2 [mem 0xfc000000-0xfc1fffff 64bit pref]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:03: resource 0 [io 0x2000-0x2fff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:03: resource 1 [mem 0xf7600000-0xf76fffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:03: resource 2 [mem 0xfc200000-0xfc3fffff 64bit pref]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:04: resource 0 [io 0xc000-0xcfff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:04: resource 4 [io 0x0000-0x0cf7]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:04: resource 5 [io 0x0d00-0xffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:04: resource 6 [mem 0x000a0000-0x000bffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:04: resource 7 [mem 0x000c0000-0x000effff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:04: resource 8 [mem 0x000f0000-0x000fffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:04: resource 9 [mem 0xfc000000-0xfec00000]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:04: resource 10 [mem 0xbdb00000-0xf7ffffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:04: resource 11 [mem 0xff980000-0xff980fff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:04: resource 12 [mem 0xff97c000-0xff97ffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:04: resource 13 [mem 0xff970000-0xff9707ff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:04: resource 14 [mem 0xfed20000-0xfed9ffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:04: resource 15 [mem 0xfeda6000-0xfeda6fff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:04: resource 16 [mem 0xfeda7000-0xfeda7fff]
    Jan 02 23:22:36 arch_1 kernel: NET: Registered protocol family 2
    Jan 02 23:22:36 arch_1 kernel: TCP established hash table entries: 65536 (order: 8, 1048576 bytes)
    Jan 02 23:22:36 arch_1 kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
    Jan 02 23:22:36 arch_1 kernel: TCP: Hash tables configured (established 65536 bind 65536)
    Jan 02 23:22:36 arch_1 kernel: TCP: reno registered
    Jan 02 23:22:36 arch_1 kernel: UDP hash table entries: 4096 (order: 5, 131072 bytes)
    Jan 02 23:22:36 arch_1 kernel: UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
    Jan 02 23:22:36 arch_1 kernel: NET: Registered protocol family 1
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:02.0: Boot video device
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 16 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=16 -> irq=16 (gsi=16)
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 17 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=17 -> irq=17 (gsi=17)
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 22 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=22 -> irq=22 (gsi=22)
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 22 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :22
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 23 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=23 -> irq=23 (gsi=23)
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 17 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :17
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 18 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=18 -> irq=18 (gsi=18)
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 23 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :23
    Jan 02 23:22:36 arch_1 kernel: PCI: CLS 64 bytes, default 64
    Jan 02 23:22:36 arch_1 kernel: Unpacking initramfs...
    Jan 02 23:22:36 arch_1 kernel: Freeing initrd memory: 10924K (ffff880001f54000 - ffff8800029ff000)
    Jan 02 23:22:36 arch_1 kernel: Simple Boot Flag at 0x7a set to 0x1
    Jan 02 23:22:36 arch_1 kernel: Scanning for low memory corruption every 60 seconds
    Jan 02 23:22:36 arch_1 kernel: audit: initializing netlink socket (disabled)
    Jan 02 23:22:36 arch_1 kernel: type=2000 audit(1388722954.276:1): initialized
    Jan 02 23:22:36 arch_1 kernel: HugeTLB registered 2 MB page size, pre-allocated 0 pages
    Jan 02 23:22:36 arch_1 kernel: zbud: loaded
    Jan 02 23:22:36 arch_1 kernel: VFS: Disk quotas dquot_6.5.2
    Jan 02 23:22:36 arch_1 kernel: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
    Jan 02 23:22:36 arch_1 kernel: msgmni has been set to 3650
    Jan 02 23:22:36 arch_1 kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
    Jan 02 23:22:36 arch_1 kernel: io scheduler noop registered
    Jan 02 23:22:36 arch_1 kernel: io scheduler deadline registered
    Jan 02 23:22:36 arch_1 kernel: io scheduler cfq registered (default)
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 16 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :16
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 16 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :16
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 17 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :17
    Jan 02 23:22:36 arch_1 kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    Jan 02 23:22:36 arch_1 kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
    Jan 02 23:22:36 arch_1 kernel: intel_idle: does not run on family 6 model 23
    Jan 02 23:22:36 arch_1 kernel: GHES: HEST is not enabled!
    Jan 02 23:22:36 arch_1 kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 17 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :17
    Jan 02 23:22:36 arch_1 kernel: 0000:00:03.3: ttyS0 at I/O 0xecb8 (irq = 17, base_baud = 115200) is a 16550A
    Jan 02 23:22:36 arch_1 kernel: hpet_acpi_add: no address or irqs in _CRS
    Jan 02 23:22:36 arch_1 kernel: Linux agpgart interface v0.103
    Jan 02 23:22:36 arch_1 kernel: i8042: PNP: No PS/2 controller found. Probing ports directly.
    Jan 02 23:22:36 arch_1 kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
    Jan 02 23:22:36 arch_1 kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
    Jan 02 23:22:36 arch_1 kernel: mousedev: PS/2 mouse device common for all mice
    Jan 02 23:22:36 arch_1 kernel: rtc_cmos 00:04: RTC can wake from S4
    Jan 02 23:22:36 arch_1 kernel: rtc_cmos 00:04: rtc core: registered rtc_cmos as rtc0
    Jan 02 23:22:36 arch_1 kernel: rtc_cmos 00:04: alarms up to one day, 242 bytes nvram
    Jan 02 23:22:36 arch_1 kernel: drop_monitor: Initializing network drop monitor service
    Jan 02 23:22:36 arch_1 kernel: TCP: cubic registered
    Jan 02 23:22:36 arch_1 kernel: NET: Registered protocol family 10
    Jan 02 23:22:36 arch_1 kernel: NET: Registered protocol family 17
    Jan 02 23:22:36 arch_1 kernel: Key type dns_resolver registered
    Jan 02 23:22:36 arch_1 kernel: registered taskstats version 1
    Jan 02 23:22:36 arch_1 kernel: Magic number: 14:436:362
    Jan 02 23:22:36 arch_1 kernel: rtc_cmos 00:04: setting system clock to 2014-01-03 04:22:34 UTC (1388722954)
    Jan 02 23:22:36 arch_1 kernel: PM: Hibernation image not present or could not be loaded.
    Jan 02 23:22:36 arch_1 kernel: Freeing unused kernel memory: 1144K (ffffffff818cb000 - ffffffff819e9000)
    Jan 02 23:22:36 arch_1 kernel: Write protecting the kernel read-only data: 8192k
    Jan 02 23:22:36 arch_1 kernel: Freeing unused kernel memory: 1008K (ffff880001504000 - ffff880001600000)
    Jan 02 23:22:36 arch_1 kernel: Freeing unused kernel memory: 420K (ffff880001797000 - ffff880001800000)
    Jan 02 23:22:36 arch_1 systemd-udevd[50]: starting version 208
    Jan 02 23:22:36 arch_1 kernel: Floppy drive(s): fd0 is 1.44M
    Jan 02 23:22:36 arch_1 kernel: ACPI: bus type USB registered
    Jan 02 23:22:36 arch_1 kernel: usbcore: registered new interface driver usbfs
    Jan 02 23:22:36 arch_1 kernel: usbcore: registered new interface driver hub
    Jan 02 23:22:36 arch_1 kernel: SCSI subsystem initialized
    Jan 02 23:22:36 arch_1 kernel: usbcore: registered new device driver usb
    Jan 02 23:22:36 arch_1 kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    Jan 02 23:22:36 arch_1 kernel: ehci-pci: EHCI PCI platform driver
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 22 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :22
    Jan 02 23:22:36 arch_1 kernel: ehci-pci 0000:00:1a.7: setting latency timer to 64
    Jan 02 23:22:36 arch_1 kernel: ehci-pci 0000:00:1a.7: EHCI Host Controller
    Jan 02 23:22:36 arch_1 kernel: ehci-pci 0000:00:1a.7: new USB bus registered, assigned bus number 1
    Jan 02 23:22:36 arch_1 kernel: ehci-pci 0000:00:1a.7: debug port 1
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd: USB Universal Host Controller Interface driver
    Jan 02 23:22:36 arch_1 kernel: ehci-pci 0000:00:1a.7: cache line size of 64 is not supported
    Jan 02 23:22:36 arch_1 kernel: ehci-pci 0000:00:1a.7: irq 22, io mem 0xf7ade000
    Jan 02 23:22:36 arch_1 kernel: FDC 0 is a post-1991 82077
    Jan 02 23:22:36 arch_1 kernel: libata version 3.00 loaded.
    Jan 02 23:22:36 arch_1 kernel: ehci-pci 0000:00:1a.7: USB 2.0 started, EHCI 1.00
    Jan 02 23:22:36 arch_1 kernel: hub 1-0:1.0: USB hub found
    Jan 02 23:22:36 arch_1 kernel: hub 1-0:1.0: 6 ports detected
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 16 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :16
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1a.0: setting latency timer to 64
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1a.0: UHCI Host Controller
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 2
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1a.0: irq 16, io base 0x0000ff20
    Jan 02 23:22:36 arch_1 kernel: hub 2-0:1.0: USB hub found
    Jan 02 23:22:36 arch_1 kernel: hub 2-0:1.0: 2 ports detected
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 17 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :17
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1a.1: setting latency timer to 64
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1a.1: UHCI Host Controller
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 3
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1a.1: irq 17, io base 0x0000ff00
    Jan 02 23:22:36 arch_1 kernel: hub 3-0:1.0: USB hub found
    Jan 02 23:22:36 arch_1 kernel: hub 3-0:1.0: 2 ports detected
    Jan 02 23:22:36 arch_1 kernel: ahci 0000:00:1f.2: version 3.0
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 18 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :18
    Jan 02 23:22:36 arch_1 kernel: ahci 0000:00:1f.2: AHCI 0001.0200 32 slots 6 ports 3 Gbps 0x2f impl SATA mode
    Jan 02 23:22:36 arch_1 kernel: ahci 0000:00:1f.2: flags: 64bit ncq sntf led clo pio ems sxs
    Jan 02 23:22:36 arch_1 kernel: ahci 0000:00:1f.2: setting latency timer to 64
    Jan 02 23:22:36 arch_1 kernel: scsi0 : ahci
    Jan 02 23:22:36 arch_1 kernel: scsi1 : ahci
    Jan 02 23:22:36 arch_1 kernel: scsi2 : ahci
    Jan 02 23:22:36 arch_1 kernel: scsi3 : ahci
    Jan 02 23:22:36 arch_1 kernel: scsi4 : ahci
    Jan 02 23:22:36 arch_1 kernel: scsi5 : ahci
    Jan 02 23:22:36 arch_1 kernel: ata1: SATA max UDMA/133 abar m2048@0xff970000 port 0xff970100 irq 58
    Jan 02 23:22:36 arch_1 kernel: ata2: SATA max UDMA/133 abar m2048@0xff970000 port 0xff970180 irq 58
    Jan 02 23:22:36 arch_1 kernel: ata3: SATA max UDMA/133 abar m2048@0xff970000 port 0xff970200 irq 58
    Jan 02 23:22:36 arch_1 kernel: ata4: SATA max UDMA/133 abar m2048@0xff970000 port 0xff970280 irq 58
    Jan 02 23:22:36 arch_1 kernel: ata5: DUMMY
    Jan 02 23:22:36 arch_1 kernel: ata6: SATA max UDMA/133 abar m2048@0xff970000 port 0xff970380 irq 58
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 18 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :18
    Jan 02 23:22:36 arch_1 kernel: pata_acpi 0000:00:03.2: setting latency timer to 64
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 22 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :22
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1a.2: setting latency timer to 64
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1a.2: UHCI Host Controller
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1a.2: new USB bus registered, assigned bus number 4
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1a.2: irq 22, io base 0x0000fc00
    Jan 02 23:22:36 arch_1 kernel: hub 4-0:1.0: USB hub found
    Jan 02 23:22:36 arch_1 kernel: hub 4-0:1.0: 2 ports detected
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 23 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :23
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1d.0: setting latency timer to 64
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1d.0: UHCI Host Controller
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 5
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1d.0: irq 23, io base 0x0000ff80
    Jan 02 23:22:36 arch_1 kernel: hub 5-0:1.0: USB hub found
    Jan 02 23:22:36 arch_1 kernel: hub 5-0:1.0: 2 ports detected
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 17 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :17
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1d.1: setting latency timer to 64
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1d.1: UHCI Host Controller
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 6
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1d.1: irq 17, io base 0x0000ff60
    Jan 02 23:22:36 arch_1 kernel: hub 6-0:1.0: USB hub found
    Jan 02 23:22:36 arch_1 kernel: hub 6-0:1.0: 2 ports detected
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 18 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :18
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1d.2: setting latency timer to 64
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1d.2: UHCI Host Controller
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 7
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000ff40
    Jan 02 23:22:36 arch_1 kernel: hub 7-0:1.0: USB hub found
    Jan 02 23:22:36 arch_1 kernel: hub 7-0:1.0: 2 ports detected
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 23 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :23
    Jan 02 23:22:36 arch_1 kernel: ehci-pci 0000:00:1d.7: setting latency timer to 64
    Jan 02 23:22:36 arch_1 kernel: ehci-pci 0000:00:1d.7: EHCI Host Controller
    Jan 02 23:22:36 arch_1 kernel: ehci-pci 0000:00:1d.7: new USB bus registered, assigned bus number 8
    Jan 02 23:22:36 arch_1 kernel: ehci-pci 0000:00:1d.7: debug port 1
    Jan 02 23:22:36 arch_1 kernel: ehci-pci 0000:00:1d.7: cache line size of 64 is not supported
    Jan 02 23:22:36 arch_1 kernel: ehci-pci 0000:00:1d.7: irq 23, io mem 0xff980000
    Jan 02 23:22:36 arch_1 kernel: ehci-pci 0000:00:1d.7: USB 2.0 started, EHCI 1.00
    Jan 02 23:22:36 arch_1 kernel: hub 8-0:1.0: USB hub found
    Jan 02 23:22:36 arch_1 kernel: hub 8-0:1.0: 6 ports detected
    Jan 02 23:22:36 arch_1 kernel: hub 5-0:1.0: USB hub found
    Jan 02 23:22:36 arch_1 kernel: hub 5-0:1.0: 2 ports detected
    Jan 02 23:22:36 arch_1 kernel: hub 6-0:1.0: USB hub found
    Jan 02 23:22:36 arch_1 kernel: hub 6-0:1.0: 2 ports detected
    Jan 02 23:22:36 arch_1 kernel: hub 7-0:1.0: USB hub found
    Jan 02 23:22:36 arch_1 kernel: hub 7-0:1.0: 2 ports detected
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 18 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :18
    Jan 02 23:22:36 arch_1 kernel: ata_generic 0000:00:03.2: setting latency timer to 64
    Jan 02 23:22:36 arch_1 kernel: scsi6 : ata_generic
    Jan 02 23:22:36 arch_1 kernel: scsi7 : ata_generic
    Jan 02 23:22:36 arch_1 kernel: ata7: PATA max UDMA/100 cmd 0xfe80 ctl 0xfe90 bmdma 0xfef0 irq 18
    Jan 02 23:22:36 arch_1 kernel: ata8: PATA max UDMA/100 cmd 0xfea0 ctl 0xfeb0 bmdma 0xfef8 irq 18
    Jan 02 23:22:36 arch_1 kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    Jan 02 23:22:36 arch_1 kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    Jan 02 23:22:36 arch_1 kernel: ata4: SATA link down (SStatus 0 SControl 300)
    Jan 02 23:22:36 arch_1 kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    Jan 02 23:22:36 arch_1 kernel: ata6: SATA link down (SStatus 0 SControl 300)
    Jan 02 23:22:36 arch_1 kernel: ata2.00: ATAPI: PIONEER DVD-RW DVR-217D, 1.07, max UDMA/66
    Jan 02 23:22:36 arch_1 kernel: ata3.00: ATA-8: WDC WD15EARX-00ZUDB0, 80.00A80, max UDMA/133
    Jan 02 23:22:36 arch_1 kernel: ata3.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
    Jan 02 23:22:36 arch_1 kernel: ata1.00: ATA-6: WDC WD360GD-00FNA0, 34.06J34, max UDMA/133
    Jan 02 23:22:36 arch_1 kernel: ata1.00: 72303840 sectors, multi 0: LBA48
    Jan 02 23:22:36 arch_1 kernel: ata1.00: applying bridge limits
    Jan 02 23:22:36 arch_1 kernel: ata2.00: configured for UDMA/66
    Jan 02 23:22:36 arch_1 kernel: ata3.00: configured for UDMA/133
    Jan 02 23:22:36 arch_1 kernel: ata1.00: configured for UDMA/100
    Jan 02 23:22:36 arch_1 kernel: scsi 0:0:0:0: Direct-Access ATA WDC WD360GD-00FN 34.0 PQ: 0 ANSI: 5
    Jan 02 23:22:36 arch_1 kernel: scsi 1:0:0:0: CD-ROM PIONEER DVD-RW DVR-217D 1.07 PQ: 0 ANSI: 5
    Jan 02 23:22:36 arch_1 kernel: scsi 2:0:0:0: Direct-Access ATA WDC WD15EARX-00Z 80.0 PQ: 0 ANSI: 5
    Jan 02 23:22:36 arch_1 kernel: sd 0:0:0:0: [sda] 72303840 512-byte logical blocks: (37.0 GB/34.4 GiB)
    Jan 02 23:22:36 arch_1 kernel: sd 2:0:0:0: [sdb] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
    Jan 02 23:22:36 arch_1 kernel: sd 2:0:0:0: [sdb] 4096-byte physical blocks
    Jan 02 23:22:36 arch_1 kernel: sd 0:0:0:0: [sda] Write Protect is off
    Jan 02 23:22:36 arch_1 kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
    Jan 02 23:22:36 arch_1 kernel: sd 2:0:0:0: [sdb] Write Protect is off
    Jan 02 23:22:36 arch_1 kernel: sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00
    Jan 02 23:22:36 arch_1 kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DP
    Jan 02 23:22:36 arch_1 kernel: sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DP
    Jan 02 23:22:36 arch_1 kernel: sda: sda1 sda2
    Jan 02 23:22:36 arch_1 kernel: sdb: sdb1
    Jan 02 23:22:36 arch_1 kernel: sd 0:0:0:0: [sda] Attached SCSI disk
    Jan 02 23:22:36 arch_1 kernel: sd 2:0:0:0: [sdb] Attached SCSI disk
    Jan 02 23:22:36 arch_1 kernel: sr0: scsi3-mmc drive: 16x/16x writer cd/rw xa/form2 cdda tray
    Jan 02 23:22:36 arch_1 kernel: cdrom: Uniform CD-ROM driver Revision: 3.20
    Jan 02 23:22:36 arch_1 kernel: sr 1:0:0:0: Attached scsi CD-ROM sr0
    Jan 02 23:22:36 arch_1 kernel: usb 3-2: new full-speed USB device number 2 using uhci_hcd
    Jan 02 23:22:36 arch_1 kernel: end_request: I/O error, dev fd0, sector 0
    Jan 02 23:22:36 arch_1 kernel: end_request: I/O error, dev fd0, sector 0
    Jan 02 23:22:36 arch_1 kernel: hub 3-2:1.0: USB hub found
    Jan 02 23:22:36 arch_1 kernel: hub 3-2:1.0: 3 ports detected
    Jan 02 23:22:36 arch_1 kernel: device-mapper: uevent: version 1.0.3
    Jan 02 23:22:36 arch_1 kernel: device-mapper: ioctl: 4.26.0-ioctl (2013-08-15) initialised: [email protected]
    Jan 02 23:22:36 arch_1 kernel: bio: create slab <bio-1> at 1
    Jan 02 23:22:36 arch_1 kernel: usb 3-2.2: new full-speed USB device number 3 using uhci_hcd
    Jan 02 23:22:36 arch_1 kernel: hidraw: raw HID events driver (C) Jiri Kosina
    Jan 02 23:22:36 arch_1 kernel: usbcore: registered new interface driver usbhid
    Jan 02 23:22:36 arch_1 kernel: usbhid: USB HID core driver
    Jan 02 23:22:36 arch_1 kernel: input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:1a.1/u
    Jan 02 23:22:36 arch_1 kernel: hid-generic 0003:046D:C713.0001: input,hidraw0: USB HID v1.11 Keyboard [Logitec
    Jan 02 23:22:36 arch_1 kernel: EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
    Jan 02 23:22:36 arch_1 kernel: usb 3-2.3: new full-speed USB device number 4 using uhci_hcd
    Jan 02 23:22:36 arch_1 systemd[1]: systemd 208 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SY
    Jan 02 23:22:36 arch_1 systemd[1]: Detected virtualization 'xen'.
    Jan 02 23:22:36 arch_1 systemd[1]: Set hostname to <arch_1>.
    Jan 02 23:22:36 arch_1 systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit
    Jan 02 23:22:36 arch_1 systemd[1]: Expecting device dev-hvc0.device...
    Jan 02 23:22:36 arch_1 systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
    Jan 02 23:22:36 arch_1 systemd[1]: Started Forward Password Requests to Wall Directory Watch.
    Jan 02 23:22:36 arch_1 systemd[1]: Starting Remote File Systems.
    Jan 02 23:22:36 arch_1 systemd[1]: Reached target Remote File Systems.
    Jan 02 23:22:36 arch_1 systemd[1]: Expecting device sys-subsystem-net-devices-enp0s25.device...
    Jan 02 23:22:36 arch_1 systemd[1]: Starting LVM2 metadata daemon socket.
    Jan 02 23:22:36 arch_1 systemd[1]: Listening on LVM2 metadata daemon socket.
    Jan 02 23:22:36 arch_1 systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
    Jan 02 23:22:36 arch_1 systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
    Jan 02 23:22:36 arch_1 systemd[1]: Starting Delayed Shutdown Socket.
    Jan 02 23:22:36 arch_1 systemd[1]: Listening on Delayed Shutdown Socket.
    Jan 02 23:22:36 arch_1 systemd[1]: Starting Device-mapper event daemon FIFOs.
    Jan 02 23:22:36 arch_1 systemd[1]: Listening on Device-mapper event daemon FIFOs.
    Jan 02 23:22:36 arch_1 systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
    Jan 02 23:22:36 arch_1 systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
    Jan 02 23:22:36 arch_1 systemd[1]: Starting Paths.
    Jan 02 23:22:36 arch_1 systemd[1]: Reached target Paths.
    Jan 02 23:22:36 arch_1 systemd[1]: Starting Journal Socket.
    Jan 02 23:22:36 arch_1 systemd[1]: Listening on Journal Socket.
    Jan 02 23:22:36 arch_1 systemd[1]: Starting Setup Virtual Console...
    Jan 02 23:22:36 arch_1 systemd[1]: Starting Load Kernel Modules...
    Jan 02 23:22:36 arch_1 systemd[1]: Starting Journal Service...
    Jan 02 23:22:36 arch_1 systemd[1]: Started Journal Service.
    Jan 02 23:22:36 arch_1 systemd-journal[129]: Journal started
    Jan 02 23:22:36 arch_1 systemd[1]: Starting udev Kernel Socket.
    Jan 02 23:22:36 arch_1 systemd[1]: Listening on udev Kernel Socket.
    Jan 02 23:22:36 arch_1 systemd[1]: Starting udev Control Socket.
    Jan 02 23:22:36 arch_1 systemd[1]: Listening on udev Control Socket.
    Jan 02 23:22:36 arch_1 systemd[1]: Starting udev Coldplug all Devices...
    Jan 02 23:22:36 arch_1 systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
    Jan 02 23:22:36 arch_1 systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Po
    Jan 02 23:22:36 arch_1 systemd[1]: Started Set Up Additional Binary Formats.
    Jan 02 23:22:36 arch_1 systemd[1]: Starting Create list of required static device nodes for the current kernel
    Jan 02 23:22:36 arch_1 systemd[1]: Mounting Huge Pages File System...
    Jan 02 23:22:36 arch_1 systemd[1]: Starting Encrypted Volumes.
    Jan 02 23:22:36 arch_1 systemd[1]: Reached target Encrypted Volumes.
    Jan 02 23:22:36 arch_1 systemd[1]: Mounting Debug File System...
    Jan 02 23:22:36 arch_1 systemd[1]: Mounting POSIX Message Queue File System...
    Jan 02 23:22:37 arch_1 systemd[1]: Starting Apply Kernel Variables...
    Jan 02 23:22:37 arch_1 systemd[1]: Starting Swap.
    Jan 02 23:22:37 arch_1 systemd[1]: Reached target Swap.
    Jan 02 23:22:37 arch_1 systemd[1]: Started File System Check on Root Device.
    Jan 02 23:22:37 arch_1 systemd[1]: Starting Remount Root and Kernel File Systems...
    Jan 02 23:22:37 arch_1 systemd[1]: Expecting device dev-disk-by\x2duuid-1f355bf1\x2d1469\x2d4722\x2d8f65\x2d01
    Jan 02 23:22:37 arch_1 systemd[1]: Starting Root Slice.
    Jan 02 23:22:37 arch_1 systemd[1]: Created slice Root Slice.
    Jan 02 23:22:37 arch_1 systemd[1]: Starting User and Session Slice.
    Jan 02 23:22:37 arch_1 systemd[1]: Created slice User and Session Slice.
    Jan 02 23:22:37 arch_1 systemd[1]: Starting System Slice.
    Jan 02 23:22:37 arch_1 systemd[1]: Created slice System Slice.
    Jan 02 23:22:37 arch_1 systemd[1]: Starting system-netctl.slice.
    Jan 02 23:22:37 arch_1 systemd[1]: Created slice system-netctl.slice.
    Jan 02 23:22:37 arch_1 systemd[1]: Starting system-getty.slice.
    Jan 02 23:22:37 arch_1 systemd[1]: Created slice system-getty.slice.
    Jan 02 23:22:37 arch_1 systemd[1]: Starting system-serial\x2dgetty.slice.
    Jan 02 23:22:37 arch_1 systemd[1]: Created slice system-serial\x2dgetty.slice.
    Jan 02 23:22:37 arch_1 systemd[1]: Starting Slices.
    Jan 02 23:22:37 arch_1 systemd[1]: Reached target Slices.
    Jan 02 23:22:37 arch_1 systemd[1]: Started udev Coldplug all Devices.
    Jan 02 23:22:37 arch_1 kernel: FS-Cache: Loaded
    Jan 02 23:22:37 arch_1 kernel: RPC: Registered named UNIX socket transport module.
    Jan 02 23:22:37 arch_1 kernel: RPC: Registered udp transport module.
    Jan 02 23:22:37 arch_1 kernel: RPC: Registered tcp transport module.
    Jan 02 23:22:37 arch_1 kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
    Jan 02 23:22:37 arch_1 systemd-modules-load[128]: Inserted module 'nfs'
    Jan 02 23:22:37 arch_1 kernel: FS-Cache: Netfs 'nfs' registered for caching
    Jan 02 23:22:37 arch_1 systemd-modules-load[128]: Inserted module 'xen_evtchn'
    Jan 02 23:22:37 arch_1 kernel: xen:xen_evtchn: Event-channel device installed
    Jan 02 23:22:37 arch_1 systemd-modules-load[128]: Inserted module 'xen_gntdev'
    Jan 02 23:22:37 arch_1 systemd-modules-load[128]: Inserted module 'xen_gntalloc'
    Jan 02 23:22:37 arch_1 systemd-modules-load[128]: Inserted module 'xen_blkback'
    Jan 02 23:22:37 arch_1 systemd-modules-load[128]: Inserted module 'xen_netback'
    Jan 02 23:22:37 arch_1 systemd-modules-load[128]: Inserted module 'xen_pciback'
    Jan 02 23:22:37 arch_1 kernel: xen_pciback: backend is vpci
    Jan 02 23:22:37 arch_1 kernel: ACPI: Requesting acpi_cpufreq
    Jan 02 23:22:37 arch_1 kernel: Monitor-Mwait will be used to enter C-1 state
    Jan 02 23:22:37 arch_1 kernel: Warning: Processor Platform Limit not supported.
    Jan 02 23:22:37 arch_1 systemd[1]: Started Apply Kernel Variables.
    Jan 02 23:22:37 arch_1 systemd[1]: Started Setup Virtual Console.
    Jan 02 23:22:37 arch_1 systemd[1]: Mounted Huge Pages File System.
    Jan 02 23:22:37 arch_1 kernel: xen_acpi_processor: Uploading Xen processor PM info
    Jan 02 23:22:37 arch_1 systemd[1]: Mounted Debug File System.
    Jan 02 23:22:37 arch_1 systemd-modules-load[128]: Inserted module 'xen_acpi_processor'
    Jan 02 23:22:37 arch_1 systemd[1]: Mounted POSIX Message Queue File System.
    Jan 02 23:22:37 arch_1 systemd[1]: Started Load Kernel Modules.
    Jan 02 23:22:37 arch_1 systemd[1]: Mounting Configuration File System...
    Jan 02 23:22:37 arch_1 systemd[1]: Mounted FUSE Control File System.
    Jan 02 23:22:37 arch_1 systemd[1]: Mounted Configuration File System.
    Jan 02 23:22:37 arch_1 systemd[1]: Started Create list of required static device nodes for the current kernel.
    Jan 02 23:22:37 arch_1 systemd[1]: Starting Create static device nodes in /dev...
    Jan 02 23:22:37 arch_1 systemd[1]: Started Remount Root and Kernel File Systems.
    Jan 02 23:22:37 arch_1 systemd[1]: Starting Load/Save Random Seed...
    Jan 02 23:22:37 arch_1 kernel: EXT4-fs (dm-0): re-mounted. Opts: data=ordered
    Jan 02 23:22:37 arch_1 systemd[1]: Started Load/Save Random Seed.
    Jan 02 23:22:37 arch_1 systemd[1]: Started Create static device nodes in /dev.
    Jan 02 23:22:37 arch_1 systemd[1]: Starting udev Kernel Device Manager...
    Jan 02 23:22:37 arch_1 systemd[1]: Starting Local File Systems (Pre).
    Jan 02 23:22:37 arch_1 systemd[1]: Reached target Local File Systems (Pre).
    Jan 02 23:22:37 arch_1 systemd[1]: Mounting /tmp...
    Jan 02 23:22:37 arch_1 systemd[1]: Mountin

    I have the same problem on Fedora Core 20 with xen 4.3.1 32bit Sempron3200+ with turned off HPET tables on South bridge and these boot options
    xen: noreboot nosmp console_to_ring console=vga vga=text-80x50
    linux: pci=noacpi pci=nommconf
    Image on Yandex disk
    When I solve it I notify you.
    Last edited by maskimko (2014-01-16 08:12:35)

  • G3 Monitor saying "out of range" after itunes upgrade - HELP PLEASE

    I'm running a G3 with 512RAM. It has been running Panther totally reliably for a year. I upgraded to 10.3.9 and the G3 ran no problem. I upgraded to the latest Itunes, restarted the G3 and now after the tones the monitor turns black with the message "out of range" refering to the frequency setting. I can hear to G3 drive running but I cant progress beyond this message on the monitor. Please help...have I lost my G3 for ever? is there a safe mode I can start the G3 in? I have the Panther discs but I don't seem able to do anything to start this G3 now. Please help..I love this Mac, I dont want to loose it, don't mind loosing the data, but not the mac..any ideas..please

    Refer to mac manual - Resetting the PRAM (parameter randon access memory).
    Restart whilst holding Command/option/p/r keys and release after second tones. Suggest changing internal battery also.

  • "Out of Range"

    I just got a new mac mini (1.83ghz, 1g memory, and 120gb hard drive). Previously I had a PC and still have the monitor (evov 17" lcd display). I hooked up the mac mini when I got it and turned the mac mini on and the monitor. All the monitor displayed was the message; "out of range" vga in: 1024x768 H. SYNC :+68.5 V SYNC :+84.7 Clock: 114.00 MHZ. On my PC I checked out the display setting and tried messing around with that and prey I could use my new mac.Of course, nothing worked and the same message still persist on a blank screen. I noticed when I was messing around with the display setting on my PC that it mentioned that the monitor could not display a screen refresh rate of 85hertz but only 60 or 75hertz. I am not sure but I think that that may have something to do with my problem.
    I figured that if i could some how without using the monitor (because I can't anyway) turn on the mac mini and go to system preferences and go to display and change the screen's resolution. I don't think there is a keyboard command code for this procedure, but I may be wrong. I could just wait a month because that is when I will be getting a 27" LCD HDTV but I want to use my mac mini know!Wouldn't you I you got a brand new one??
    If you happen to have any solutions PLEASE HELP ME I want to use my brand new mac mini!

    You might try starting up in Safe Mode. Basically, after you hear the bong sound when you start the mini, immediately press and hold the Shift key until you see a gray screen with a little spinny wheel gear looking thing. At that point you can let go of the Shift key. The Mac will finishing booting into Safe Mode.
    In Safe Mode the Mac uses a lower, generic type resolution that almost any monitor should handle. Once you have booted into OS X. You can go under the blue apple at the top left and find System Preferences. Within System Preferences you will find a Display icon and if you click on that it will let you set options for your display. Try setting to 1280 x 1024 and 60 Hz refresh. Hopefully that will result in a useable screen and hopefully when you restart the Mac normally (without holding down the shift key) the newly chosen resolution will stick. Good luck.

  • Monitor out of range

    Brand new Mac Mini out of the box.   Hooking HDMI to a Westinghouse L2610NW.  Showing "out of range".  No way to hook up VGA with what is out of box because there is only a DVI-D adaptor. Tried powering on with no HDMI connected.  Tried connecting another computer to the monitor and that works. No DVI connection on the monitor.  No other monitor available to connect to.  Can you set to 1024x768 out of the box just to get through the set up?

    The native resolution for your L2610NW is 1920 x 1200 and the Mac Mini supports that using the HDMI port.
    With the monitor connected, reset the PRAM as per > About NVRAM and PRAM
    1. Shut down the computer.
    2. Locate the following keys on the keyboard: Command, Option, P, and R. You will need to hold these keys down simultaneously in step 4.
    3. Turn on the computer.
    4. Press and hold the Command-Option-P-R keys. You must press this key combination before the gray screen appears.
    5. Hold the keys down until the computer restarts and you hear the startup sound for the second time.
    6. Release the keys.

  • "Rise of Atlantis" Mac game created "out of range" message through switch

    I've got a mac-mini. I've been running the mac game download from apple "Rise of Atlantis" for a while now. I have an older SONY SDM-HS95P DVI/SVGA monitor (capable of 1280 x 1024 resolution) connected to the mac via DVI to SVGA adapter out of the mac mini, and SVGA into the Monitor. No problems when launching or playing the game.
    However, I just added an SVGA Distribution Amp to the chain (capable of 1600 x 1280). So now it's DVI to SVGA adapter out of the mac min, SVGA into the SVGA Distribution Amp, and one SVGA output of the DA goes to the SONY computer monitor, and the other SVGA output of the Distribution Amp goes to my SONY HDTV via it's PC/SVGA input. I did this so I could stream videos off the computer to the TV. This all works well. I change my screen resolution from 800 x 600 (when sitting in front of the computer so all text is very big because of bad eyes) to 1260 x 768 when streaming to the HDTV so the picture fills the screen.
    However, I just introduced a problem with the game "Rise to Atlantis" that I didn't have before I added the distribution amp. When launching the game now, the screen flashes to black and I get an
    "out of range" message. The message stays there, and from the mac mini, I can't even get it back to the normal screen without rebooting the mac mini.
    However, if I remote into the Mac Mini via remote desktop connection from my 27" imac quad core, I can see the game and control the computer. But this isn't a viable solution.
    I have tried setting the mac mini display resolutions to lower, middle and higher resolution settings before actually launching the program, but nothing helps. I also disconnected the SVGA output of the SVGA distribution amp. going to the HDTV to see if that would help, but it does not.
    So it appears that the SVGA Distribution amp. is causing some sort of a hiccup that throws the SONY computer display to black and that "out of range" message.
    Can anyone suggest anything that might allow me to keep things hooked up as they are and still be able to play the game? 'Rise of Atlantis" is a mac game, downloadable from apple, ....but it's the type of game that seems to take over the entire screen....so you can't see FINDER or your desktop when playing it...it's definetly throwing the SONY display into some sort of "take over" mode.
    Any input would be appreciated.

    No, I did not try swapping the outputs as neither is marked primary or secondary, indicating that they were in any way different. However, I did resolve the issue. I didn't realize that in "Rise Of Atlantis" it was automatically set to display FULL SCREEN and that I could set it to NOT do that. I made that change and now I can see FINDER/DESKTOP behind the game while it still pretty much fills the screen and this has eliminated the problem I posted about. However, thank you very much for your input. I appreciate it.

  • My 2011 mac mini screen is black and has an "out of range" message

    My 2011 mac mini is hooked up to a monitor and it has a black screen with an "out of range" message. I'm not sure how to fix it. everything is plugged in. please help!

    Reset the PRAM > Resetting your Mac's PRAM and NVRAM
    1. Shut down the computer.
    2. Locate the following keys on the keyboard: Command, Option, P, and R. You will need to hold these keys down simultaneously in step 4.
    3. Turn on the computer.
    4. Press and hold the Command-Option-P-R keys. You must press this key combination before the gray screen appears.
    5. Hold the keys down until the computer restarts and you hear the startup sound for the second time.
    6. Release the keys.

  • G3 mini-tower beige powerpc. monitor signal out of range w/ upgrade to OSX

    Hi. I have a beige G3 minitower with an 80 gig hd, 448 mb ram, ATY Mach 64 3DUPro 6mb vram pci. Monitor is a NEC Multisync FE770. I have an 8 gig partition on which I successfully installed OSX10.2.08, and another partition has 9.2.2.
    I can boot in 9.2 no problem, but when I boot up in 10.2, I get a red bordered box on a black screen that says "Signal frequency is out of range. FH>80 OKHZ. FV>75OHZ. Please change signal timing."Monitor preferences have been reset to different frequencies, but it still persists.
    I have read for hours on this forum, and have tried resetting pram via keyboard, only to get the "?" start-up screen. I was able to boot in OS9 to get to utilities to re-choose the startup disc. But nothing changed, still got the out of range box. I also tried the Mac solution posted here, "Blue or Black screen after updating" but that did nothing. Anyhow, I know you suggested replacing the battery, but why would it work in OS9 if the battery is the problem? Can anyone suggest any fix to this? I have been trying to get this computer updated for my 10 year old son, and have put way too much time into it:) Best,JER

    daordster wrote:
    daordster wrote:
    daordster wrote:
    Hi. I have a beige G3 minitower with an 80 gig hd, 448 mb ram, ATY Mach 64 3DUPro 6mb vram pci. Monitor is a NEC Multisync FE770. I have an 8 gig partition on which I successfully installed OSX10.2.08, and another partition has 9.2.2.
    I can boot in 9.2 no problem, but when I boot up in 10.2, I get a red bordered box on a black screen that says "Signal frequency is out of range. FH>80 OKHZ. FV>75OHZ. Please change signal timing."Monitor preferences have been reset to different frequencies, but it still persists.
    I have read for hours on this forum, and have tried resetting pram via keyboard, only to get the "?" start-up screen. I was able to boot in OS9 to get to utilities to re-choose the startup disc. But nothing changed, still got the out of range box. I also tried the Mac solution posted here, "Blue or Black screen after updating" but that did nothing. Anyhow, I know you suggested replacing the battery, but why would it work in OS9 if the battery is the problem? Can anyone suggest any fix to this? I have been trying to get this computer updated for my 10 year old son, and have put way too much time into it:) Best,JER
    Hi, I am updating this original post to say that I ordered and installed a new battery into my G3, and I still am getting the "out of range" warning on my monitor at startup. Can anyone offer a solution? It only happens when I boot in OSX, and never happened in system 9. The only additional info I can offer is that I installed 10.2 with the grey install discs from an older IMAC. Someone on the forum mentioned that the grey install discs would only work for the same machine, though I was able to do a clean install. Does a disc meant for an imac install a system geared to that model? Could it be a reason for the monitor issue? I am grasping at straws. Any additional help is welcome. Best,JER
    Hey, I just borrowed a retail disc of OSX 10.2, and went through a clean install, only to get the SAME out of frequency message on start-up. So that eliminates that. New pram battery also done. Any other ideas? If the monitor is generating the message, and nec is no help, what next? Can the NEC adaptor work for another crt monitor? I have a PC computer with a monitor the same size. I guess I'll check to see. Best,JER
    What is happening is that the physical pixel characteristics of your monitor don't match the resolution that your Mac is calling for (this is one area that Windoze's display handling routines differ on PC; windoze will "cut off" or black out portions of the display to make it fit.)
    I just had this happen yesterday with an oddly-shaped LCD monitor that is slightly squarish. Zapping the Mac's PRAM did no good because it defaults to 800 X 600, which the monitor was geometrically unable to achieve. The resolution had to be set to 640 X 480 (or 1280 x 960 or other common denominator.)
    The reason OS 9 can display it is because a compatible resolution is stored in the prefs, while OS X does not contain it.
    I solved my problem by booting from a secondary disk and replacing the display pref with a known-good one. Since you can't swap prefs between 9 and X, you could boot with a different monitor, set the resolution to a compatible setting, then hook up the previous monitor.

  • Mic mini to IIyama ProLite E431S: signal frequency out of range

    Hi, I've just got a problem with the display (despite everything worked well together for more than a year): the screen is black, with only the following message:
    Attention signal frequency out of range
    H: 05.2 KHz V: 05.2 Hz
    Please change signal timing
    It suddenly happened yesterday, but everything was OK since I bought it, except some quick shutdown of the display from times to times
    I don't know what to do, since I've got only one display so I can't modify the parameters of the mac mini
    Thank goodness I also have a laptop to write this message.

    Try starting in Safe mode. To do this, hold down the shift key during a restart. Hopefully you will get a working screen back. Then change the display settings to what you had before and restart normally.

Maybe you are looking for

  • How to delete an App I did not install on my machine

    My son's school requires them to use MacBookPro's (three cheers).   His laptop broke so I restored his Time Machine backup to an external drive which is attached to my desktop system.  That way he could keep up with his work until the repairs were co

  • Creation of Inbound Delivery

    Hi Gurus, I want to create Inbound Delivery using Function Module or BAPI. Can anybody tell what function module or BAPI to create Inbound Delivery? Thanks

  • Impossible d'afficher le fichier dans Explorer

    J'ai windows Vista et j'ai installé Adobe Reader 9.5.0. Le problème est que je n'arrive pas à ouvrir des fichiers sur internet. Comment faire?

  • Installing CiscoWorks 3.2

    Hi, I am installing CiscoWorks 3.2 on a Windows 2003 server. I am getting the following error "Cannot create the install dependency file." Any assistance would be useful. Thanks... Shaun

  • Why isn't camera raw 8.3 compatible with PSE 11?

    I'm furious and want to know who to complain to. Less than one year ago I purchased PSE 11 which is what I needed for it to work with my Nikon D7100, also less than a year old. I have just purchased a Nikon D610 and it seems I need to downlaod Camera