Airport randomly fails

It seems that my airport would randomly fail. Sometimes the airport signal indicator will just illuminate the dot while other times there will be an exclamation mark and it would say no internet. Sometimes the signal indicator just constantly animates with one signal bar moving upwards when I get no signal. The location I use my computer in is not far from the wireless router and all other computers can get strong signals where I use it. Usually after waiting about 10 or 15 minutes I can get the signal again. This problem especially happens after my computer comes out of standby or hibernation. During the times when the airport fails I have to get really close to my router to get a signal and when I attempt to connect away from my router it always says connection has timed out. This problem has been happening ever since I upgraded my laptop to Snow Leopard. Can somebody please explain what is happening?

See my FAQ*:
http://www.macmaps.com/WIFI1048.html
Test at a WiFi hotspot like a coffee shop to see if the issue is your router configuration, or computer.
- * Links to my pages may give me compensation.

Similar Messages

  • Cluster Network Randomly Failing on Hyper-V Cluster

    Please let me know if there is a more appropriate forum. I am having a really strange issue that is seemingly random. I have a 3 host cluster that are all identical hardware and running Hyper-V Server 2012 R2. The networking is as follows and each network
    is a different VLAN/Subnet:
    3 Cluster networks for virtual machines
    1 Cluster network for cluster traffic/management
    1 Heartbeat network
    2 iSCSI networks for storage
    All of the networks are perfectly fine except for one which seems to fail on a random node at a random time during the day (so far, a maximum of once per day).
    If I start to live migrate virtual machines that are on the failed network, the cluster network comes back up. The cluster networks are teamed using SCVMM and they are switch independent and running the Dynamic teaming algorithm. We have tried changing the
    network switches to see if it was faulty network hardware and things ran fine for one day and then just happened again today so we've ruled that out. The only error message I get is 1127 which is the error stating that the cluster network has gone into a failed
    state which doesn't help much. I've run the cluster validation tool for networking several times and it always passes 100%. What I am worried about is hardware incompatibilities as I am using Dell servers (PowerEdge R720) that have Broadcom NIC's in them.
    We have 12 Ethernet ports in each server and they are all identical hardware. Four of them are integrated Broadcom, another four that are from a Broadcom quad add-on NIC, and another 4 that are from an Intel quad add-on NIC. All are server grade NIC's. The
    only problem I've had in the past is with VMQ which we've had to disable as a workaround but that has always stabilized our virtual networks. In any case all of the cluster networks for virtual machines are set up identically and only this particular one randomly
    fails on any one of the three hosts (it has happened at least once on each node now).
    I am wondering if anyone has had this experience before. I have read that there are some nasty compatibility issues between Broadcom and Hyper-V  but I am wondering if someone could give me some ideas to find out how to narrow this down since the event
    logs don't seem to be speaking in obvious terms to me.
    Please let me know if you have any suggestions on how to narrow down what's causing this or if there is more information that I could provide. In the meantime, I'm going to try and take note of which virtual machines are running on the host that has the
    network fail just in case there's some correlation there but that could take a while to accrue any useful data and our users aren't too happy with the instability...
    Thank you in advance for your time and sorry for the lengthy post!

    Since I made the change last Friday evening, 4/10, I haven't experienced the issue. I won't be completely convinced that this resolved it until I monitor for at least one more week since it didn't actually present itself for the first time until I was already
    one week into live deployment. Also, this link below is much more eloquent than how I put it and describes my issue exactly. Coupled with the KB article that someone posted within this comments section (the same that I posted earlier here) of the article,
    this is what led me to check the VMQ status through PowerShell which is much better than going through the registry to do it (I'm running Hyper-V Server 2012 R2 which is like core so I don't have the GUI options shown in the article).
    http://alexappleton.net/post/77116755157/hyper-v-virtual-machines-losing-network
    I could try updating the driver but there is mention in the comments of this post that driver updates have yet to resolve this issue so we may still be waiting on Broadcom for a fix. Please confirm otherwise if anyone has any information.

  • Dv6 2170us sound randomly fails

    Laptop audio sound randomly fails.  Only way I've found to fix it is to plug my headphones into the microphone jack...suddenly it will work.  When you unplug - it goes quiet.  Now - sound works through the head phones (when plugged into the head phone jack) but not through the external speakers.  As far as I can tell, the firmware driver gets confused by whether to send the sound through the speaker/headphone jack...or simply the headphone jack.  Weird.  
    Weirder.  Give it a while after doing the "plug the headphones into the mic jack" and the external speakers will keep working after you unplug. 
    HP - Please fix!  Its annoying and driving me nuts.  Getting ready to stop recommending HP's after this experience.

    Hi,
    Your laptop is under warranty so You may give it to the service. Please contact with HP and tell them about this problem. How to do it all informations here (just choose Your country).
    ** Say thanks by clicking the "Thumb up" icon which is on the left. **
    ** Make it easier for other people to find solutions, by marking my answer with "Accept as Solution" if it solves your issue. **

  • Queued files randomly failing with "Unknown error"

    This making no sense. Any file I queue singularly into ME from premiere will export fine. If I queue up a bunch and let it go on its own, the files randomly fail. The log says unknown error.
    I'm on win 7, I have 16 GB of RAM, I am using Mercury acceleration, ppreHeadless.exe is using 2.1 GB or RAM, resource monitor is telling em I have 5 GB of RAM not in use that is available and CPU usage is maxed.
    ANY ideas what could be the issue?
    EDIT:
    Seems ot be happening randomly with singular vids as well. All possible updates are installed. It gets right to rendering the last frame of the file and then hangs and then the sheep yells at me.
    Edit 2: Exporting them right of Premiere works just fine.

    Hello,
    Thanks for letting us know about your problem. It seems that there is some problem in your profile. Creating a new profile may fix your problem. Create a new profile and sync with your Firefox Account.
    For Creating a profile, Please do following:
    If Firefox is already included in your Linux distribution or if you have installed Firefox with the package manager of your Linux distribution:
    # Close your Firefox.
    # In '''Terminal''' run: <br/> <code>firefox -P</code>
    # To start the Create Profile Wizard, click '''Create Profile...''' Button in the Profile Manager.
    # Click {button Next} and enter the name of the profile. Use a profile name that is descriptive, such as your personal name. This name is not exposed on the Internet.
    # To create the new profile, click '''Finish'''
    For more instruction regarding creating a new profile, please see this article. [[Use the Profile Manager to create and remove Firefox profiles]]

  • Export data to MS excel dynamically, randomly fail

    Hello, there,
    I developed a package to export data from SQL 2005 to xlsx file.
    In the package, I have a foreach loop to loop through a recordset, ie. Group_Name, Group_ID
    Inside the foreach loop, I create a spreadsheet using the Group_Name (passed by variable) in the destination excel file and then use Group_ID to select data that belongs to that Group_ID and populate the data into the Group_Name tab.
    So, if there are 10 Group_Names, then 10 spreadsheets will be created in the excel file, if there are 50 group_names, then 50 will be created ...
    I run this package in my local machine for now...
    What puzzles me is this package randomly fails in the middle of process. Sometimes it succeed. And I am running the same data ... Even it fails, it does not fail on any particular spreadsheet (group_name), sometimes this, sometimes that ...
    When it failes, it gives me error message like this
    error: 0xC0202009 at Data Flow Task - PopulateData, Excel Destination [12]: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80040E37.
    Error: 0xC02020E8 at Data Flow Task - PopulateData, Excel Destination [12]: Opening a rowset for "GroupName_101" failed. Check that the object exists in the database.
    Error: 0xC004706B at Data Flow Task - PopulateData, SSIS.Pipeline: "Excel Destination" failed validation and returned validation status "VS_ISBROKEN".
    Error: 0xC004700C at Data Flow Task - PopulateData, SSIS.Pipeline: One or more component failed validation.
    Error: 0xC0024107 at Data Flow Task - PopulateData: There were errors during task validation.
    I really want to understand why it is not stable.
    Thanks.

    Thanks for the reply. My process is very similar to yours, using variable to create sheets. I am just running it at my desktop, right click the package, click execute ... It randomly fails
    At some point, I suspect it is because I have too many application open: I have VS 2010 open, where this project is being developed, BIDS2008 open, a couple of SSMS open ...
    Not very sure why, just wonder if anybody else had this experience ...
    Thanks.
    SQL Developer from PA
    I think I should tell you that the process is supposed to create about 80 spreadsheets in one excel file and quite often it fails at around 20th sheet. But some times, it finishes creating and populating data in 80 sheets without any problem.

  • BOL randomly failing

    We're running into an issue with our Bills of Lading where they will randomly fail to with an OPP error after ship confirmation. We can reprint the same trip/delivery with no issues.
    Some of the OPP errors we get are
    java.lang.ClassCastException: java.io.File
              at oracle.apps.xdo.template.FOProcessor.createFO(FOProcessor.java:1566)
              at oracle.apps.xdo.template.FOProcessor.generate(FOProcessor.java:951)
              at oracle.apps.xdo.oa.schema.server.TemplateHelper.runProcessTemplate(TemplateHelper.java:5975)
              at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3555)
              at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3614)
              at oracle.apps.fnd.cp.opp.XMLPublisherProcessor.process(XMLPublisherProcessor.java:247)
              at oracle.apps.fnd.cp.opp.OPPRequestThread.run(OPPRequestThread.java:153)
    [UNEXPECTED] [39753:RT18542341] java.lang.NullPointerException
              at oracle.apps.xdo.template.fo.area.PageNumber.formatString(PageNumber.java:104)
              at oracle.apps.xdo.template.fo.IDManager.registerId(IDManager.java:44)
              at oracle.apps.xdo.template.fo.area.AreaTree.registerLastPageJoinSeq(AreaTree.java:1106)
              at oracle.apps.xdo.template.fo.area.AreaTree.incrementJoinSequenceIndex(AreaTree.java:219)
              at oracle.apps.xdo.template.fo.area.AreaTree.registerLastPageDocument(AreaTree.java:1089)
              at oracle.apps.xdo.template.fo.area.AreaTree.forceOutput(AreaTree.java:471)
              at oracle.apps.xdo.template.fo.elements.FORoot.end(FORoot.java:58)
              at oracle.apps.xdo.template.fo.FOHandler.endElement(FOHandler.java:386)
              at oracle.xml.parser.v2.XMLContentHandler.endElement(XMLContentHandler.java:196)
              at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1212)
              at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:301)
              at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:268)
              at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:149)
              at oracle.apps.xdo.template.fo.FOProcessingEngine.process(FOProcessingEngine.java:279)
              at oracle.apps.xdo.template.FOProcessor.generate(FOProcessor.java:1022)
              at oracle.apps.xdo.oa.schema.server.TemplateHelper.runProcessTemplate(TemplateHelper.java:5975)
              at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3555)
              at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3614)
              at oracle.apps.fnd.cp.opp.XMLPublisherProcessor.process(XMLPublisherProcessor.java:247)
              at oracle.apps.fnd.cp.opp.OPPRequestThread.run(OPPRequestThread.java:153)
    has anyone else encountered this and what might we do to resolve this?

    This was an issue with my A/D converter being switched to "digital in" when it should be set to "analog in". It does switch over by itself. I also need to ensure that the 'play' button is pushed in the import window.

  • Airport Express fails to connect

    Ok. i know there are like a million of these posts regarding the same topic. however, i cannot find an answer as i have searched pretty much each and every post. here is my problem.
    I have 2 airport expresses. Both are older versions. One connects with no issues at all. the other i have tried to configure several times, but when it "restarts" to apply my config settings. the airport utility fails to recognize it. It does see my first one, but not the second. I have even tried to copy the config from the known working one to the one that is giving me grief. That did not work either. It makes no sense to me, because clearly it sees my wireless network if i can use the utility to configure it (after defaults are applied and restart given). Or is that the issue? i am not connecting to it via my wireless. but rather to the default wireless of the AX. And there something with the actual wireless within the airport itself? Please any help would be greatly appreciated......it is driving me mad. If i have been vague in my explanation, please let me know and i can supply more details.

    It's always possible that you may have defective AirPort Express (AX) that will not hold its configuration settings.
    Try a Factory Default Reset first as follows:
    Power down the AX and leave it off at least 5-10 minutes
    Hold in the reset button and keep holding it in while you plug the AX back in to power
    Keep holding the reset button until you have seen the amber light blink quickly for 4-5 seconds, then release
    Wait 40-45 seconds for the AX to restart and you see the amber light blinking slowly
    Temporarily, connect an ethernet cable from your computer to the AX
    Open AirPort Utility - click Manual Setup
    Click the Base Station tab below the row of icons to name your device, assign a device password and adjust Time Zone settings
    Click the Wireless tab
    Wireless Mode = Join a wireless network
    Wireless Network Name = Same name as your wireless network that you have been using
    Wireless Security = Same setting as your other AX
    Wireless Password = Same password as your wireless network
    Confirm Password
    Click Update. As soon as you see the message that the settings have been stored, close AirPort Utility and disconnect the temporary ethernet cable
    Wait 40-45 seconds to see if you get the green light
    If you try this a few times and the AX will not join the network correctly, you likely have an defective AX that will need to be replaced.

  • IE Windows randomly fails to show  swapped images preloaded

    if you look at this page in IE6 Windows (did not test in
    IE5):
    http://ever-together.com/site/product_detail.php
    and use the little numbers or next-previous arrows to swap
    the main image, randomly (it seems), the
    image will just not show up.
    Since it seems random, you might have to try several times
    before an image does not show.
    Even an image that has showed before, sometimes does not show
    if you just click on its corresponding
    number again.
    The images are preloaded using <body
    onLoad="MM_PreLoadImages()">
    The javascript code to swap the images is different on the
    numbers, which use MM_setTextOfLayer and
    on the previous-next arrows, which use a custom script, but
    both randomly fail to display the images
    in IE6, so I assume it is an IE bug?
    Anybody encountered this problem before?
    seb ( [email protected])
    http://webtrans1.com | high-end web
    design
    Downloads: Slide Show, Directory Browser, Mailing List

    <a href="#" onClick="...;return false;">
    Murray --- ICQ 71997575
    Adobe Community Expert
    (If you *MUST* email me, don't LAUGH when you do so!)
    ==================
    http://www.dreamweavermx-templates.com
    - Template Triage!
    http://www.projectseven.com/go
    - DW FAQs, Tutorials & Resources
    http://www.dwfaq.com - DW FAQs,
    Tutorials & Resources
    http://www.macromedia.com/support/search/
    - Macromedia (MM) Technotes
    ==================
    "(_seb_)" <[email protected]> wrote in message
    news:e3tolh$4i$[email protected]..
    > (_seb_) wrote:
    >> if you look at this page in IE6 Windows (did not
    test in IE5):
    >>
    >>
    http://ever-together.com/site/product_detail.php
    >>
    >> and use the little numbers or next-previous arrows
    to swap the main
    >> image, randomly (it seems), the image will just not
    show up.
    >> Since it seems random, you might have to try several
    times before an
    >> image does not show.
    >> Even an image that has showed before, sometimes does
    not show if you just
    >> click on its corresponding number again.
    >>
    >> The images are preloaded using <body
    onLoad="MM_PreLoadImages()">
    >>
    >> The javascript code to swap the images is different
    on the numbers, which
    >> use MM_setTextOfLayer and on the previous-next
    arrows, which use a custom
    >> script, but both randomly fail to display the images
    in IE6, so I assume
    >> it is an IE bug?
    >>
    >> Anybody encountered this problem before?
    >>
    >>
    >
    > ok I just remember I had the same problem before and
    "solved" it by using
    > <a href="#" onClick="...">
    > instead of
    > <a href="javascript:;" onClick="...">
    > The later does NOT swap images in IE, the former does.
    > Why, I am still wondering.
    > And I would like it to work with "javascript:;", so that
    on smaller
    > screens my page is not going to jump back to the top
    each time the buttons
    > are pressed...
    >
    > Anybody knows a real solution?
    >
    >
    >
    > --
    > seb ( [email protected])
    >
    http://webtrans1.com | high-end web
    design
    > Downloads: Slide Show, Directory Browser, Mailing List

  • Ipad randomly failing to show videos inside webpages

    I just updated my ipad to the new OS 4.2.1, and since then some vimeo videos embedded in webpages are failing to appear.
    I was able to strem them untill one hour ago when i upgraded, now the ipad randomly fails showing some of those.
    This webpage is an example:
    www.frame.it/page/Portfolio/op/view/id/175/LogoRai1
    This videos still work on ipads with the old OS, so is not an encoding issue.
    On the new OS, the player mask is actually generated, but remains transparent.

    mmmikele wrote:
    Hi Michael,
    of course is supposed to play those and sometimes plays fine on my ipad too.
    I will try explaining myself a bit better:
    There are 5 or 6 videos on this page.
    The ipad randomly fails to show some of these, sometimes it shows 4 sometimes 2.
    And i mean it fails "to show the video box in the page". If you see the play button and the background image it will work fine, but you will notice some blank spaces beetween one video and another, those are not loaded videos.
    The mask just remains transparent.
    Yes, I see the same behavior with 4.2.1. It's probably a Safari bug. If you haven't already done so report it at: http://www.apple.com/feedback/ipad.html
    I couldn't find a work-around for it. The bug is probably in common rending code since it also appears in the iCab browser as well.

  • Airport settings failed in diagnostics

    ok i am about ready to throw my new macbook out the window. I just downloaded the new software update for leopard and now i cant connect wirelessly. when i run the diagnostics it says airport settings failed. please help before i shoot this macbook

    Apparently Apple are aware of this problem and there should be a fix released on Software Update quite soon. I am experiencing similar problems, but when I run Network Diagnostics I am able to reconnect. Looks like you've been waiting quite some time for the fix though looking at the date you posted your message.

  • IBook G4 Airport randomly disconnecting

    hi,
    I have had my ibook G4 for about 3 monhes basicly since I had it, it's airport card has been disconnecting randomly and taking several minutes to recognise that my airport express base station is connected. At first my airport icon in the top bar of my comp says it has a perfect connection, then maybe 2 or 3 hours later it will drop down to one, then zero. I am only about 10 feet away from my airport express. what is the problem here? We have 2 other iBook G4s which arent having this problem.

    My PBG4 12" 867 has recently started losing the connection with my base station. Initially I thought the problem was with the base station failing or interference (suggestions from Buffalo helpdesk). I connected my airport express which showed exactly the same signal loss - iStumbler showed there was a connection, though intermittent. Last night I realised that it happens when the PB is plugged in and the battery is fully charged. Restarting the PB unplugged restored the signal. I can't work out why this happens. I can't even blame it on Tiger. Is there anything to wear out in an airport card? Any suggestions gratefully received.

  • Airport Extreme Fails to mount/share disk

    Recently I disconnected all users from my LaCie HD shared from my Apple Airport Extreme to back it up to another 1TB drive formatted as FAT32. I did this while directly connected to the MacbookPro.
    1) It appears that there is no easy disconnected way to cleanly unmount a disk from the extreme. I was forced when connecting the drive to the MacbokPro to repair both the disk and permissions. Is there a safe way to do this?? I really found this as an artifact to the second and for me personnaly larger problem.
    2) The drive now appears in the airport utility shared disks window as a 698GB disk, but I cannot get sharing to work under any circumstances. The Airport Utility will not otherwise recognize the disk. Both MAC and PC clients now (after having removed and replaced the disk) can now no longer see the base station as a "server". It gives a "not operational" error when using the BS/WAP name. When using the IP (internal address) it fails with a slightly different error (cannot be found).
    I looked through the original 20 or so pages of posts trying to find something similar. I did not see anything.
    Any suggestions??

    Like Todd, in the original post, I have:
    1. verified that connection between cable modem & comcast is fine by connecting both ThinkPad and PowerBook and both remain connected and are able to perform random downloads for hours on end.
    2. Wireless connectivity works fine for my two laptops as they both work with an airport express and a Linksys wireless access point & router.
    3. Hard reset teh Airport Extreme till I'm blue in the face.
    4. Already have firmware 5.7 installed, the AEBS is brand new.
    Symptoms are:
    Both Thinkpad and Powerbook work fine after a power reset on the AEBS. But after an indeterminate amount of time -- anywhere from 15 minutes to three hours they fail to get beyond the AEBS out to the net.
    It isn't the WiFi, because I can have one laptop computer connnected to the ethernet port and it fails get beyond the AEBS.
    By simply restarting teh AEBS via the Airport Admin Utility or disconnecting power when the Airport Admin utility fails to connect to the AEBS, I can resume my work on the net.
    It's not like I'm transferring large amounts of data, just doing casual surfing, so the error buffers should be overfilled.
    It is that comcast is doing a regular expiration of my WAN IP address.
    any clues?
    any way to fix it?
    PBook & ThinkPad   Windows XP Pro  

  • XML Publisher Report Bursting Program Randomly failing

    Hi,
    In our environment "XML Publisher Report Bursting Program" fails randomly and failures are very very few and random, and can not be reproduced.
    The error message is
    +++++++++++++++++++++++++++++++++++++++++++
    Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
    XDOBURSTREP module: XML Publisher Report Bursting Program
    Current system time is 16-APR-2013 14:00:42
    Exception in thread "main" java.lang.NullPointerException
    at java.util.Hashtable.put(Hashtable.java:394)
    at oracle.apps.xdo.oa.cp.CPUtil.getSessionProperties(CPUtil.java:42)
    at oracle.apps.xdo.oa.cp.JCP4XDOBurstingEngine.runProgram(JCP4XDOBurstingEngine.java:84)
    at oracle.apps.fnd.cp.request.Run.main(Run.java:161)
    Start of log messages from FND_FILE
    End of log messages from FND_FILE
    oracle.apps.xdo.oa.cp.JCP4XDOBurstingEngine
    Program exited with status 1
    Executing request completion options...
    ++++++++++++++++++++++++++++++++++++++++++++++
    Had been trying to find out any pattern, but no fix time or particular parent request.
    Only common point in failure with above error are below columns in fnd_concurrent_request
    Description - blank
    LFILE_SIZE - 1476
    & interim_status_code - Blank
    Any suggestions will be helpful

    Hi;
    Similar issue mention at below notes, Please review:
    NPE Error While Bursting Using XDOBURSTREP in EBS R12 [ID 754790.1]
    Bursting Engine Ends With Java.Lang.Nullpointerexception[Article ID 559443.1]
    XDOBURSTREP - XML Publisher Report Bursting Program Fails with InvalidPropertyValueException[Article ID 603424.1]
    If its not help I suggest rise SR
    Regard
    Helios

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

  • Idoc-xi-rfc scenario random fails to be processed

    Hallo all .
    Let me first describe our scenario.
    Generally it is an IDOC - > XI -> RFC case.
    Idocs are created after an order creation .
    In XI there are two different mappings, depending on the idoc structure (the IDOC  type is the same, but the segments created are different)  and two different receivers, each one with an individual communication channel. Each channel is allowed to have up to 200 multiple simultaneous connections .
    Then, each functions decides whether the inbound data is appropriate for it and processes it or not .
    Our problem is this :
    If we send a bunch of orders (eg 100), all of them are processed successfully except of some of them, (eg 4 ).
    In the SXMB__MONI, they are all marked as "waiting for acknowledgment" .
    Yet, there is no obvious reason for their failure.
    If we send again the failed orders, then 3 of them may be processed.
    And finally if we send them again even the last one will be processed.
    So, from what I can see, this problem cannot exist due to the data we send, or the XI configuration, or the functions that are finally called. Actually, it seems to be absolutely random.
    Any suggestions would be highly appreciated .
    Edited by: John Syrigos on Dec 30, 2008 6:08 PM
    Some clarifications : The business scenario is to handle the ORDER idocs that created in the SAP ERP system from SD (Outbound Deliveries) or the Stock Transport Orders (Outbound Deliveries). The problem for the created IDocs is that if the outbound delivery is coming from SD then for each line item of the sd document fills the segment A for example and if the outbound delivery is coming from the Stock Transport Order then fills another IDOC segment for example B. For this reason we decide to create two separate interface mappings in order to send each IDOC in both of the Function Module that handle which of them will be executed. In the daily order processing the user every afternoon use a standard SAP ERP transaction and collect all the outbound deliveries and create for the collectively the appropriate IDOCs. We suppose the mass processing will create some problems.
    Thanks in advance

    hi,
    one simple advice (less then one day) would be to change
    >Generally it is an IDOC - > XI -> RFC case.
    either to:
    Generally it is an IDOC - > XI -> ABAP proxy case.
    or if this is not abap proxy enabled receiver system to:
    Generally it is an IDOC - > XI -> IDOC case.
    if you already have a working RFC then changing it to and IDOC
    and changing a mapping is less then one day and in both cases
    abap proxy and IDOC you will have a clear status and LOG!
    (as both IDOCs and ABAP proxies are persistent in receiver system)
    this is the best possible option I believe and nothing will get lost for sure
    Regards,
    Michal Krawczyk
    http://mypigenie.com XI/PI FAQ

Maybe you are looking for