Chartread: Error - icoms - usb_is_usb_portno: port number out of range!
Hello. This is the error I get on my iMac Lion using an i1Pro spectrometer and the latest Argyll ICC software. Chartread is the sub program for reading printed color targets.
chartread: Error - icoms - usb_is_usb_portno: port number out of range!
Q. 1 I can't figure out how to fix this and I have no X-Rite software remaining on my computer.
Q. 2 How do I get a list of usb devices (in terminal?) and if I can do that can I assign a new number to that device?
Regards
Mark MacKenzie
Without the KVM the results are the same, except that using the fallback grub entry shows the console but X fails to start
(EE) intel(0): No kernel modesetting driver detected.
(II) UnloadModule: "intel"
(EE) Screen(s) found, but none have a usable configuration.
The same happens if I load the i915 module
MODULES=(i915 !vesafb !uvesafb !vboxdrv)
If I load the i915 and use
kernel /boot/vmlinuz26 root=/dev/sda2 ro vga=795 i915.modeset=1
the console still is unusable, but X boots
And I still see the
fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver
Last edited by noalwin (2009-12-28 12:38:51)
Similar Messages
-
Error "number out of range" in pdf sent through mail using smartform outpu
Hi Experts,
We have a program which sends mail using smartform output in 'PDF' format. We are able to preview smartform correctely in SAP and mail is also getting sent fine with attachment of form as PDF document. But, when we try to open the document, it gives error saying 'Number out of range'. Also, not all of the windows of smartform are appearing in document and some are coming only half.
We are not able to find out the reason for this. Any help would be appriciated.Hi Soumya,
Have you got the solution as we are facing the same issue.
Cheers,
Bharath -
Error "number out of range" in pdf sent through mail using smartform output
Hi Experts,
We have a program which sends mail using smartform output in 'PDF' format. We are able to preview smartform correctely in SAP and mail is also getting sent fine with attachment of form as PDF document. But, when we try to open the document, it gives error saying 'Number out of range'. Also, not all of the windows of smartform are appearing in document and some are coming only half.
We are not able to find out the reason for this. Any help would be appriciated.
Gouri.Hello,
How did you solve this one? We are facing the same problem in ECC6.0.
Thanks in advance,
Benjamin de Rijke -
操作系统：XP
MAX版本：14.0
IMAQdx版本：4.3.5
摄像头：北京嘉恒中自图像OK_AC1360
生产商的应用软件中使用正常。在AMCAP软件（视频测试软件）中使用也正常。
连接Gige摄像机时出错：Error：0xBFF69012 Attribute value is out of range Attribute Name CameraAttributes::AutoFunction::AutoTargetGrayValue
试着修改 ‘AutoTargetGrayValue’ 属性值，但是MAX会无相应并死掉。
Solved!
Go to Solution.Sometimes, camera firmware is the problem. Sometimes, the camera XML file is the problem. Sometimes, the way that IMAQdx tries to force settings onto the camera is the problem.
Things to try:
1. Check with the manufacturer, and ask if new firmware is available for the camera. If the firmware cannot be updated by the end user, you will need to get a Returm Merchandise Authorization number, and send the camera in for the upgrade.
2. Edit the XML file that was downloaded from the camera, and remove all references to CameraAttributes::AutoFunction::AutoTargetGrayValue. Do not alter, or remove the zip file that resides in the same location as the XML. If you do, IMAQdx will request a fresh copy from the camera, and overwritew your changes. You can find the XML file in C:\Users\Public\Documents\National Instruments\NI-IMAQdx\Data\XML
3. Edit the camera .icd file in C:\Users\Public\Documents\National Instruments\NI-IMAQdx\Data, and remove the reference to CameraAttributes::AutoFunction::AutoTargetGrayValue.
Machine Vision, Robotics, Embedded Systems, Surveillance
www.movimed.com - Custom Imaging Solutions -
Workspace Error executing query: String index out of range: -39
I am running a Financial Reporting Book.
When running this book, I am receiving the following error.
Error executing query: String index out of range: -39
What does this mean?
And how do I fix this?
Thank you,
DanThis is happening to a single Financial Reporting book.
Oracle suggested changing the Data Query Optimization settings.
I had checked on Essbase Queries Use MDX on all the reports being called into the book.
Oracle suggested that I uncheck this box.
This did not do the trick.
I ran the reports individually, and they all worked.
I am stumped. -
Getting error: RC-50004 String index out of range when running adclonectx.pl
Hi,
I'm trying to clone a RAC database on the same host. I'm using the MOS note:
Cloning Oracle E-Business Suite Release 12 RAC-Enabled Systems with Rapid Clone ( Doc ID 559518.1 )
I run the command from Step 5.1.3:
perl adclonectx.pl ......
But getting error:
"RC-50004: Error occurred in CloneContext:
String index out of range: 38
ERROR: context creation not completed successfully."
From the Clone Context logfile:
PROMPT :
Number of DATA_TOP's on the Target System [3]
ANSWER :
1
PROMPT :
Target System DATA_TOP Directory 1
ANSWER :
+DATA/prod/datafile
ASM Path, not Validating: +DATA/prod/datafile
Creating ../data/stage/addbhomtgt.xml which will contain Target system database mount points.
StackTrace:
java.lang.StringIndexOutOfBoundsException: String index out of range: 38
at java.lang.String.substring(String.java:1765)
at oracle.apps.ad.context.CloneContext.gen_iFile(CloneContext.java:6681)
at oracle.apps.ad.context.CloneContext.getInputFromUsers(CloneContext.java:1114)
at oracle.apps.ad.context.CloneContext.doClone(CloneContext.java:601)
at oracle.apps.ad.context.CloneContext.main(CloneContext.java:5260)
RC-50004: Error occurred in CloneContext:
String index out of range: 38
Context file creation not succesful
And workaround/solution will be much appreciated. Thanks very much.FYI, I'm cloning on the same host as target. This is 2 node EBS RAC setup.
PATH is OLD source for contextfile.xml
Latest clone patches applied.
Here is the complete output from the log file...
[oracle@PPDBS11 bin]$ cat /u01/app/oracle/product/11.2.0/dbhome_1/appsutil/clone/bin/CloneContext_0908210110.log
Using admin directory: /u01/app/oracle/product/11.2.0/dbhome_1/appsutil/clone/bin
#------Log File time stamp: 0908210110------------
# $Header: CloneContext.java 120.92.12010000.26 2013/05/06 12:02:01 mmanku ship $
# Running on - ppdbs11
# Source Host - null
# Domain Name - <xxxx.yyyy.zz>
# Context Location - /u01/app/oracle/product/11.2.0/dbhome_1/appsutil/PREPROD1_ppdbs11.xml
# Context Type - null
# Context Template - /u01/app/oracle/product/11.2.0/dbhome_1/appsutil/template/adxdbctx.tmp
# Clone Stage Area - null
# Pairs File - /u01/app/oracle/product/11.2.0/dbhome_1/appsutil/clone/pairsfile.txt
# Destination Context - null
# Validation - false
# Platform Migration - false
# no prompt - false
Variables extracted from pairsfile: /u01/app/oracle/product/11.2.0/dbhome_1/appsutil/clone/pairsfile.txt
****************************************************/n
s_undo_tablespace = APPS_UNDOTS1
s_dbClusterInst = 2
s_db_oh = /u01/app/oracle/product/11.2.0/dbhome_1
**************************************************** PROMPT :
Target System Hostname (virtual or normal) [ppdbs11]
ANSWER :
ppdbs11 PROMPT :
It is recommended that your inputs are validated by the program.
However you might choose not to validate them under following circumstances: -If cloning a context on source system for a remote system.
-If cloning a context on a machine where the ports are taken and
you do not want to shutdown the services at this point.
-If cloning a context but the database it needs to connect is not available. Do you want the inputs to be validated (y/n) [n] ?
ANSWER :
n PROMPT :
Target Instance is RAC (y/n) [y]
ANSWER :
y PROMPT :
Target System Database Name
ANSWER :
PROD PROMPT :
Host name [ppdbs11]
ANSWER :
ppdbfmisscan PROMPT :
Virtual Host name [null]
ANSWER :
ppdbs11-vip PROMPT :
Instance number [1]
ANSWER :
1 PROMPT :
Private interconnect name [ppdbs11]
ANSWER :
ppdbs11-priv PROMPT :
Target System Base Directory
ANSWER :
/u01/app/oracle PROMPT :
Oracle OS User [oracle]
ANSWER :
oracle PROMPT :
Oracle OS Group [oinstall]
ANSWER :
oinstall PROMPT :
Target System utl_file_dir Directory List
ANSWER :
/usr/tmp/PROD PROMPT :
Number of DATA_TOP's on the Target System [3]
ANSWER :
1 PROMPT :
Target System DATA_TOP Directory 1
ANSWER :
+DATA/prod/datafile
ASM Path, not Validating: +DATA/prod/datafile
Creating ../data/stage/addbhomtgt.xml which will contain Target system database mount points.
StackTrace:
java.lang.StringIndexOutOfBoundsException: String index out of range: 38
at java.lang.String.substring(String.java:1765)
at oracle.apps.ad.context.CloneContext.gen_iFile(CloneContext.java:6687)
at oracle.apps.ad.context.CloneContext.getInputFromUsers(CloneContext.java:1120)
at oracle.apps.ad.context.CloneContext.doClone(CloneContext.java:601)
at oracle.apps.ad.context.CloneContext.main(CloneContext.java:5266) RC-50004: Error occurred in CloneContext:
String index out of range: 38
Context file creation not succesful -
Error Mapping XI: String index out of range.
Hi Experts,
I have a problem with the mapping in XI. The transformation of data is very complex (see below) for field HBKID. I'm not having understanding the process of mapping is performed for the field HBKID. The creation of the transformation was performed using the graphical method for mapping in XI for this case. I think the person who created this data transformation didn't know that could be used USER DEFINED FUNCTION. Could you explain in more detail this MAPPING?
In the test displays the message: RuntimeException in Message-Mapping transformation: Runtime exception during processing target field mapping /ns1:ZSD000TF01/ZVBAP/item[2]/HBKID.
The message is: Exception:java.lang.StringIndexOutOfBoundsException: String index out of range: 3]
Edited by: Rafael Sá on Feb 9, 2010 10:40 PMHi Experts,
So, I've done several tests on the tab of tests with various XML and I can't understand reason of the error in MAPPING.
I'll detail a little more the problem:
The processing of the interface is made by many items.
MAPPING ERROR:
When the interface processes a first item with the information below:
CHAVE_BANCO = EMPTY
MEIO_PGTO = D
TP_CARTAO_CREDITO = EMPTY
AND a second item with the information below:
CHAVE_BANCO = 314/3705
MEIO_PGTO = W
TP_CARTAO_CREDITO = EMPTY
The error occurs: The message is: Exception:java.lang.StringIndexOutOfBoundsException: String index out of range: 3]
MAPPING OK:
But when the processing is performed inversely, the MAPPING is done correctly.
When the interface processes a first item with the information below:
CHAVE_BANCO = 314/3705
MEIO_PGTO = W
TP_CARTAO_CREDITO = EMPTY
AND a second item with the information below:
CHAVE_BANCO = EMPTY
MEIO_PGTO = D
TP_CARTAO_CREDITO = EMPTY
I don't understand logic mapping for the field HBKID. -
BEx Error - The specified value is out of range
Hi
We areBI 7.0 (SP14) & recently installed SAPGUI 7.10 (patch 7).
When I select a query (Path: Info Areas --> WMH Warehouse Management --
> Shipping KPIu2019s --> Order Turnaround in Detail) and give date range
greater than 2 weeks, then I can a critical error message and the BEx session closes.
Following is the trace file details:
ListSeparator: ,
ExcelVersion: 12.0
AddinVersion: 7100.1.400.1062
10/13/2008 10:16:12 PM----
System.Exception: CriticalProgramError ---> System.Exception: CriticalProgramError ---> System.Exception: CriticalProgramError ---> System.Exception: CriticlaProgramError ---> System.Exception: CriticlaProgramError ---> System.ArgumentException: The specified value is out of range.
at Microsoft.VisualBasic.CompilerServices.LateBinding.InternalLateSet(Object o, Type& objType, String name, Object[] args, String[] paramnames, Boolean OptimisticSet, CallType UseCallType)
at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateSet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean OptimisticSet, Boolean RValueBase, CallType CallType)
at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateSetComplex(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean OptimisticSet, Boolean RValueBase)
at com.sap.bi.et.analyzer.addin.BExExcelItem.set_RangeAddress(String value)
at com.sap.bi.et.analyzer.addin.BExItemGrid.AdjustItemRange()
at com.sap.bi.et.analyzer.addin.BExItemGrid.OnRender(Boolean iForceRendering)
at com.sap.bi.et.analyzer.api.BExItem.Render()
--- End of inner exception stack trace ---
at com.sap.bi.et.analyzer.api.BExItem.Render()
at com.sap.bi.et.analyzer.api.BExApplication.Render()
--- End of inner exception stack trace ---
at com.sap.bi.et.analyzer.api.BExApplication.Render()
at com.sap.bi.et.analyzer.api.BExApplication.set_Synchronize(Boolean iValue)
at com.sap.bi.et.analyzer.addin.BExExcelApplication.OpenQueryThreaded(BExParameter iParameter)
--- End of inner exception stack trace ---
at com.sap.bi.et.analyzer.addin.BExExcelApplication.OpenQueryThreaded(BExParameter iParameter)
at com.sap.bi.et.analyzer.addin.BExThreads.ProcessParameterSubExecuter.Execute()
at com.sap.bi.et.analyzer.addin.BExExcelApplication.OpenQuery(OSObjectInformation iObjectDescription, String iRRIVariableName, String iRRIVariableValue)
at com.sap.bi.et.analyzer.addin.BExThreads.ProcessOpenQueryExecuter.Execute()
--- End of inner exception stack trace ---
at com.sap.bi.et.analyzer.addin.BExThreads.ProcessOpenQueryExecuter.Execute()
at com.sap.bi.et.analyzer.addin.BExMenu.ProcessOpenQuery()
at com.sap.bi.et.analyzer.addin.BExUserInteraction.Process(String iStepName)
--- End of inner exception stack trace ---
at com.sap.bi.et.analyzer.addin.BExUserInteraction.Process(String iStepName)
at com.sap.bi.et.analyzer.addin.BExUserInteraction.ProcessUserInteraction(Sub iSubDelegate, BExStepType iStepType)
at com.sap.bi.et.analyzer.addin.BExMenu.Process(CMD iCMD)
at com.sap.bi.et.analyzer.addin.BExMenu.ProcessCMD(CMD iCMD)
at com.sap.bi.et.analyzer.addin.BExConnect.ExcelCommunication.ProcessBExMenuCommand(String iCMD)
CriticalProgramError
at com.sap.bi.et.analyzer.addin.BExUserInteraction.Process(String iStepName)
at com.sap.bi.et.analyzer.addin.BExUserInteraction.ProcessUserInteraction(Sub iSubDelegate, BExStepType iStepType)
at com.sap.bi.et.analyzer.addin.BExMenu.Process(CMD iCMD)
at com.sap.bi.et.analyzer.addin.BExMenu.ProcessCMD(CMD iCMD)
at com.sap.bi.et.analyzer.addin.BExConnect.ExcelCommunication.ProcessBExMenuCommand(String iCMD)
Thanks & Regards
Madhucheck if oyu can execute this query in RSRT, is so then you need to either go for SP > 16 or BEx Gui = 4 or 5 .,
Hope this helps -
Spatial index creation error -ORA-13011: value is out of range
I am trying to create a spatial index and this is what I get.
ERROR at line 1:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-13200: internal error [ROWID:AAAFXYAADAAABxyAAD] in spatial indexing.
ORA-13206: internal error [] while creating the spatial index
ORA-13011: value is out of range
ORA-00600: internal error code, arguments: [kope2upic014], [], [], [], [],
ORA-06512: at "MDSYS.SDO_INDEX_METHOD", line 7
ORA-06512: at line 1
I can't find any documentation as to how to fix this. How do you determine which row of data is out of range? Any help would be greatly appreciated!Hi Jeff,
The data at rowid AAAFXYAADAAABxyAAD has a problem.
Can see what the issue is by doing:
select sdo_geom.validate_geometry(geom_col_name,diminfo)
from your_table_name a, user_sdo_geom_metadata b
where b.table_name='YOUR_TABLE_NAME'
and a.rowid='AAAFXYAADAAABxyAAD';
If you are using Oracle9iR2 then this would be even better:
select sdo_geom.validate_geometry_with_context(geom_col_name,diminfo)
from your_table_name a, user_sdo_geom_metadata b
where b.table_name='YOUR_TABLE_NAME'
and a.rowid='AAAFXYAADAAABxyAAD'; -
Curve 8310 error Unc.Exception: string index out of range: 0
I'm getting the following error message: "Uncaught Exception: string index out of range: 0" and no way to clear that message.
Could someone help me to fix it? Actually the only way to get BB-8310 back working is remove the battery.
Thanks in adavance
Solved!
Go to Solution.Hi and Welcome to the Community!!
There's pretty much no diagnosing those -- they are the equivalent of the random errors in Windows for which tracing the root cause is fruitless. Basically, these are the last out in the programming code -- some event occurred for which there is no handler in the code. The fix is a code update that handles the event...but, again, knowing what the event is is pretty much impossible. So, there are a few things to try:
Sometimes, the code simply becomes corrupt and needs to be refreshed -- just like a reboot:
Anytime random strange behavior or sluggishness creeps in, the first thing to do is a battery pop reboot. With power ON, remove the back cover and pull out the battery. Wait about a minute then replace the battery and cover. Power up and wait patiently through the long reboot -- ~5 minutes. See if things have returned to good operation. Like all computing devices, BB's suffer from memory leaks and such...with a hard reboot being the best cure.
If it won't boot up cleanly, then you may need to try Safe Mode:
KB17877 How to start a BlackBerry smartphone in safe mode
There might be an updated code set from the carrier -- check them via this portal:
http://na.blackberry.com/eng/support/downloads/download_sites.jsp
The toughest possible cause is a badly behaving app. To find it, there are a couple of options. One is to see if you can read the log file:
Go to the home screen. Hold down the "alt" key and type 'lglg'. (You will not see anything while you type).This will bring up the log file. Scroll down (probably many pages) untill you see a line that says 'uncaught execption'. Click on this line. The name of the app will be in the info. Alternative methods for bringing up the logs are in this KB:
KB05349How to enable, access, and extract the event logs on a BlackBerry smartphone
The other method is to remove apps one at a time, waiting a while in between (I usually recommend a week), until the problem ceases...thereby discovering the offending app. Still another method is to reload the BB OS cleanly, leaving some time between adding other apps onto the BB so as to be able to determine exactly which one is the cause.
Good luck and let us know!
Occam's Razor nearly always applies when troubleshooting technology issues!
If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
Join our BBM Channels
BSCF General Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code -
Parallel Port address out of range for output.vi
Hi all,
I know people have had this question before, but I don't seem to follow the responses.
Basically, I have a Parallel Port connected through a PCI slot with the address BCC8, and I've been trying to talk to a stepper motor using output.vi, but as far as I can tell the address input is limited to I16 values. Is there away to get around this?
HannHi Hann,
What forum postings have you been researching before posting? We need more information about your application, perhaps posting your code would be helping in resolving your issue. Are you using a particular LabVIEW toolkit like the LabVIEW Motion Control Tools or are you using VISA Read and Write functions?Where are you getting the output.vi? What version of LabVIEW are you using.
Joshua B.
National Instruments
NI Services
NI Support Resources
NI Training Resources -
Listener's have same port number
Friends,
I have two listener's configured in listener.ora file with same port number .Is it any problem if i gave the same port number?Please advise me.Yes, it is a problem if host is the same for both.
If You have two listeners with same port number and on same machine You will not be able to start them both, because port number will be already in use. One will start, the second one will through an error.
Change port number for one of them. -
Attribute out of range error with Dalsa Spyder camera
I have a Dalsa Spyder camera SG-11 which seems to work fine in NI MAX. I've also had this camera working successfully in a LabView vi but now, for some reason, I am getting an error message "Attribute out of range (-1074360302)".
I've tried using different gain values (since MAX sometimes gives an attribute out of range error relating to gain) but am not having much success.
Has anyone else experienced this problem and found a work around?
LightworkerHi LightWorker,
I've not seen this probelm specifically with Dalsa Spyder SG-11 cameras but there are several KnowLedge Base Articles on the error for various differnt models of camera. It may be that one of these fixes will apply to your camera as well.
How Do I Resolve "Error: 0xBFF69012 Attribute value is out of range” When Connecting to a GigE Camer...
Why do I get Error 0xBFF69012 "Attribute Value is Out of Range" with my Basler GigE Camera?
Stingray Camera & NI LabView / Vision Builder Error -1074360302 "Attribute is out of range"
Please let us know if any of these solve your issue.
Kind regards,
James W
Controls Systems Engineer
STFC -
Hello, I'm new to FieldPoint. I have a problem with FP-AI-110. The voltage I want to measure is 8 volts. I have set the range from -10.4V to 10.4V in MAX explorer for channel configuration. The voltage is verified with DMM and it's about 8 volts. The problem is that sometimes I can get correct reading but sometimes I get the error code 33487 which means out of range. What could be the reason for this? Thanks very much.
In your program, are you reading just one channel or multiple channels? If reading multiple channels and some are not connected to anything, their inputs will 'float' and may go out of range.
-AK2DM
~~~~~~~~~~~~~~~~~~~~~~~~~~
"It’s the questions that drive us.”
~~~~~~~~~~~~~~~~~~~~~~~~~~ -
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]: MountinI 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)
Maybe you are looking for
-
To get the unique id of the selected row in a JTable as in Database
Hi, After fetching the recodrs from the Database, I have displayed them in a JTable. Though I fetched all the columns from db, I am displying only only 2 columns, say Name and Number neither of which is unique, however I have a unique ID for each rec
-
How can I view my friend's itunes library?
Is there any way that my friend and I could browse each other's itunes music libraries? It would be ideal to be able to click and sample songs as well. We don't want to share the actual music files. This is strictly to expose one another to each o
-
Hi!! Control recipe can be sent to xMII or other systems through CO53. How can we resend the control recipe to xMII? Please Guide. Best Regards, Ajit Dubal.
-
Question About Backing Systems Up
Hi All, We are running several workstations with 10.3.9 on a Windows 2003 server network, and I am curious to know if there is any way to back up each system to the Win 2003 server so that we can recover if there ever are any problems? We are using R
-
Thank you in advance folks! I have a Audio TS & Video TS files and I want to bring into iMovie to slice/cut part of the video at the end. Can I convert Audio/Video TS files to a format I can bring into iMovie to splice the end and send to iDVD. I wan