LO Extractor's Full update Functionality

Hello All,
I have some few questions regarding the FULL UPDATE functionality of LO extractor.
Till now I was under the assumption that FULL UPDATE will bring all the current data from ECC, but we had a requirement to make a LO extractor (for e.g. 2LIS_02_ITM) has a full update in the info package.
But this is just pulling the data from the Set up tables, hence the newly posted data is not coming to the BW system. If this is the case, then why we have Full Update functionality for the LO extractors?
Does Full update only works for the FI extractors?
Please let me know your ideas,
Thanks,

Hi Ram,
in all the scenarios of LO and LIS, the full update is only accessed from Setup tables.
The deltas are retreived from base tables subsequently.
In case of non LO and LIS extractors the full updateas well as delta is fetched from base table.
If you want latest data aswell to be pulled from ECC then there is no other go, other than filling the set up till that point and perform a full load from BI.
Naveen.A

Similar Messages

Generic extractor based on specific function module with delta update

Hi everybody,
I'm trying to create a specific extractor using a specific function module and a specific structure of record.
In my F.M i merge record from standard table MKPF and MSEg and return the result trhu the structure.
In initialisation mode, there's no problem . But now i'm must be able to use the DELTA mode but i don't know how to do it.
Can somebody help me?
Here is the code of my function module , i know it's not a standard one because i'm not using cursor but i got everything i need. The delta mode must be on creattion time of record in mkpf .
FUNCTION z_bw_extract_mvt_sortant.
""Interface locale :
*" IMPORTING
*"     VALUE(I_REQUNR) TYPE SBIWA_S_INTERFACE-REQUNR
*"     VALUE(I_ISOURCE) TYPE SBIWA_S_INTERFACE-ISOURCE OPTIONAL
*"     VALUE(I_DSOURCE) TYPE SBIWA_S_INTERFACE-ISOURCE OPTIONAL
*"     VALUE(I_MAXSIZE) TYPE SBIWA_S_INTERFACE-MAXSIZE OPTIONAL
*"     VALUE(I_INITFLAG) TYPE SBIWA_S_INTERFACE-INITFLAG OPTIONAL
*" TABLES
*"      E_T_DATA STRUCTURE ZBW_MVTSORTANT OPTIONAL
*"      I_T_SELECT TYPE SBIWA_T_SELECT OPTIONAL
*"      I_T_FIELDS TYPE SBIWA_T_FIELDS OPTIONAL
*" EXCEPTIONS
*"      NO_MORE_DATA
*récupération des données.
CASE i_initflag.
    WHEN space.
      transfert_record it_mvtsor e_t_data i_maxsize.
     DESCRIBE TABLE it_mvtsor LINES sy-tfill.
     IF sy-tfill GT i_maxsize.
       APPEND LINES OF it_mvtsor FROM 1 TO i_maxsize TO e_t_data.
       DELETE it_mvtsor FROM 1 TO i_maxsize.
     ELSEIF sy-tfill GT 0.
       APPEND LINES OF it_mvtsor FROM 1 TO sy-tfill TO e_t_data.
       FREE it_mvtsor.
     ELSE.
       RAISE no_more_data.
     ENDIF.
    WHEN OTHERS.
raffraichissement des variables de travails.
      FREE : r_werks , r_bwart , it_mkpf , it_mseg , it_mvtsor .
      CLEAR : r_werks , r_bwart , it_mkpf , it_mseg , it_mvtsor .
récupération des paramètres.
      PERFORM set_selection_criteria TABLES i_t_select.
      PERFORM init_code_mouvement.
      SELECT * FROM mkpf
      APPENDING CORRESPONDING FIELDS OF TABLE it_mkpf.
WHERE cpudt = sy-datum.
      CHECK NOT it_mkpf IS INITIAL.
      SELECT * FROM mseg
        APPENDING CORRESPONDING FIELDS OF TABLE it_mseg
        FOR ALL ENTRIES IN it_mkpf
        WHERE mblnr = it_mkpf-mblnr
          AND mjahr = it_mkpf-mjahr
          AND werks IN r_werks
          AND bwart IN r_bwart.
      LOOP AT it_mkpf ASSIGNING .
        ENDLOOP.
      ENDLOOP.
ENDCASE.
ENDFUNCTION.
Thanks in advance.

Hi,
first of all: The use of delta in a generic Datasource by FM is not supported by SAP standard. You need to change the extraction method in table ROOSOURCE from F2 to F1. There is no standard transaction to do this, you have to do a hard table update. Be careful not to change any standard datasource by error, otherwise you can get serious problems.
The interface for the FM will change with the new extraction method. You will need a new parameter I_UPDMODE of type SBIWA_S_INTERFACE-UPDMODE to distinguish between Init, Delta and Full Load.
For an example coding please refer to FM RSVD_BW_GET_DELTA_DATA.
Hope that helps
Stephan
Message was edited by: Stephan Müller

In full update not getting all records

Dear BW Masters,
I am working with MM module. Iam using standard extract structure 2LIS_02_ACC
Iam doing full update. Getting full data 1300 records in to PSA. But getting only 298 in to my ODS. I tried changing fields in to KEY FIELDS AND IN TO DATA FIELDS in my ODS
But could not get data.
Pls help me..i have dead line before that i need to complete report on the same.
Its happening with the other HDR and ITM extractors.
PLs help me..

Hi
Please post the query in relavent forum. (BI)
You have posted in MM forum for BW help.
Regards
Ramakrishna

Full update not getting all records from PSA to ODS

Dear BW Masters,
I am working with MM module. Iam using standard extract structure 2LIS_02_ACC
Iam doing full update. Getting full data 1300 records in to PSA. But getting only 298 in to my ODS. I tried changing fields in to KEY FIELDS AND IN TO DATA FIELDS in my ODS
But could not get data.
Pls help me..i have dead line before that i need to complete report on the same.
Its happening with the other HDR and ITM extractors.
PLs help me..

Hello,
Look at this example:
R/3 Record:
CustNo | Name | Order | Amount
1234 | Customer1 | Order 1 | 100
1235 | Customer2 | Order 2 | 200
1234 | Customer1 | Order 3 | 300
If Cust.No is Keyfield, In BW you will get 2 records
1234
1235
If Order No is Key field, you will get 3 records.
It is not necessary to get the same no of records as they are in R/3.

I have a MacBook Air. With latest version of Pages and Yosemite my full-screen function no longer operates.

My full screen function no longer works in Pages after latest software updates for Pages and Yosemite.
Has anyone else experienced this phenomena? It flashes to full screen then immediately reverts to the normal display.

Yes it does.
Open your Pages document in Pages v5.5.1.
To enter full-screen:
Pages > View > Enter Full Screen (or control+command+F)
Hover over the green traffic light in your Title bar. It will show diagonal full-screen arrows. Click.
To exit full-screen:
Hover over the Document Title bar, then Pages > View > Enter Full Screen (or control+command+F)
Move your pointer over the Document Title bar, and press the green traffic light again

How to schedule Process Chain with Full Update for the past closed month

Hello,
I have an HR-BN benefits transactional data extractor - http://help.sap.com/saphelp_nw70/helpdata/en/08/b01d3cf8aa101ce10000000a11405a/frameset.htm
One of the selection fields for that extractor is calendar year/month 0CALMONTH and it is a full update extractor.
SAP recommends running this extractor once a month after the month has been closed.
If I were to include this update/extract into my process chain, would it be possible to automate the process in a way where the process chain is scheduled to execute once a month (I know how to do that), but that also only pulls values for the past/closed CALMONTH (as if it had a variable value of which would be automatically set to the last closed month when pchain is run)? As I mentioned 0CALMONTH is one of the selection criterias in the infopackage for that extractor.
let me know how I might be able to do that.
P.S. we are on BI 7.0/2004s
Thank you

For Calmonth selection in infopackage you can use the SAP-Exit OLAP Variable 0CMLMON (Last Month)
select Type "7" ("OLAP Variable")
and in Details of Type screen, Select OLAP Variable "0CMLMON" Which is SAP-Exit variable for Calmonth, that returns the last month from the current system-date.
If variable 0CMLMON is not active, you need to activate it from Business content.
Assign pts if helpful.

How does Full Update works in BI 7.0???

Dear Experts,
I have a question on BI 7.0 Full Updtae.. How does it works exactly... My question is am loading data from Flat-file as a Full Update... Once If load the data through infopackage.. As we all knew dat. It brings the data to PSA.. later when i run the DTP it gets loaded into Data Targert.. Suppose if wanna load the same file with few changes.. Should i delete the request from PSA.. If not, Itz getting updated with duplicate records.. Suppose, If i delete the request from PSA and reload the same file with changes.. Then itz getting loaded successfully...
Kindly reply to my query.. Answering getz appreciated...
Regards,
Hemanth Aluri

Delta DTP fetches unloaded requests only assuming you have started off with a delta DTP.
Only changed records in the flatfile may not be loaded as DTP fetches all data in the new request into target.
Can you stage a DSO ..will the overwrite functionality suit your business needs?
delta loading throgh flat file in 7.0
How to load delta from flatfile to cube and ods
Full upload then delta
http://help.sap.com/saphelp_nw04/helpdata/en/57/e537373aedaf43e10000009b38f839/content.htm
You can start off with a delta DTP.
Or
Run a pseudo DTP after the Full DTP for deltas to follow.
Or
Delete the request in the source if you are using Full DTP.
Re: Init with out data DTP
Re: Delta DTP with filter
Re: how to load data from one Infocube to another request by request using DTP

Technical issues with update function in help menu

This is likely not the correct place, but I was not able to ascertain where I should ask this. I have the full CS6 suite, and am unable to get anything to happen when I attempt to use the update function within the help menu of any of the programs in the suite. I have even tried to use the update program that came with the suite, but still nothing works. When in the programs, I click the link listed as "updates" and nothing happens what so ever. This is a common occurance regardless of the specific program.
My system specs:
Athlon X6 CPU
16Gb ram
Radeon HD 6950 2Gb
ASrock extreme 3 mb
Hard drive is a pair of seagate 500Gb drives in RAID0 array
OS is Windows 7 Pro 64bit
Current version showing in Photoshop and Illustrator is 13.0.1

Notice where it says
"No update override. If there is no UpdateOverride the Mediator simply propagates the changes to the underlying data sources. "
That's what you want. Want to see it work? "import metadata" for a database table. Open the data service that is created. Execute the function with the same name as the table. Click on the "Edit" button, change some data, click on Submit. You've done it. Re-execute the function with the same name as the table to see the modified data.
And it doesn't stop there - you can build logical data services on top of that physical data services, and when you update data in the logical data service, the changes will be propagated to the underlying physical data services.
is it possible to create a Data Service that performs updates, and make it available for ALSB as a Web Service, like the get methods it already creates?Well, this is a different question now. Yes it is possible, please read : http://e-docs.bea.com/aldsp/docs25/appdev/alsb_support.html

Why are a lot of HR cubes a full update rather than delta?

Hi all,
What might be the best technical reason one can give for; a lot of SAP delivered cubes for HR (like Benefits, staffing assignments, headcount, qualifications) are full update rather than delta. Is it best to keep it that way or make them delta ?
Also none of these cubes have SAP delivered ODS with it, so is it a good idea to keep an ODS layer or an enterprise data warehousing layer?
Can someone share some ideas,
Thanks for inputs in advance,

Delta not depend on cubes, deltas depend on extractors then the issue is not cubes without deltal else extractor without deltas.
I don't know exactly what is the reason but surely was that HR has not change document for some of HR data. (neither alternative method like CO-PA or LIS).

Migrating from Sybase to Oracle - update() function

In sybase i have an update function that let me know when an specific column id updated after and update statement, does Oracle have something similar??
thanks.

Hello <Please Supply Your Name>,
Is this a system function or a user defined function?
Without knowing the full details of what the Sybase "update" function is, there are 3 areas which might be worth investigating.
1) Indentity columns and @@IDENTITY.
Identity columns in Sybase are auto increment columns used mostly for ID's.
@@IDENTITY is a global variable which holds the last updated/inserted identity value in the session your in.
SQL Developer Migration Workbench can automatically migrate both of these.
Identity column are converted to use an Oracle trigger and sequence.
@@IDENTITY is replicated in a sqlserver_utilities package variable. (The identity trigger updates the value).
2) Triggers
If you are not using an identity column in Sybase. But would still like to "catch" a value being updated in your table, you should use a BEFORE/AFTER UPDATE trigger.
You could save this value to a package variable if you wish (much like how we emulate the @@IDENTITY column above).
3) Update Returning Clause
This clause returns the result of an update statement.
http://www.samoratech.com/PLSQL/swArtPLSQLReturn.htm
I hope this helps
Dermot.

First time Full Update Error - a strange phenomena

Hi Gurus,
There is a peculiar phenomenon that I am facing.There is a Z Extractor which brings in data from a Custom Table and a standard table.It uploads in Full Update mode to a DSO.
On few occassions , the first time load fails saying no source data available. If I do a repeat within seconds or anytime after that , it picks up data and loads perfectly in the DSO.
I could find no plausible explanation for this.
Could anyone let me know , why could this happen.
Regards,

kind of hard to reply if we don't know how this Z-extractor has been created, hum

Difference between Full Update V3 and V2

Hi Gurus
explain me briefly abt the difference between the full update V3 and V2..
pls post some links to understand in detail
regards
Prince

Hi Prince,
V1 Update: It is a Synchronous update. Here the Statistics update is carried out at the same time as the document update (in the application tables).
V2 Update: It is an Asynchronous update. Statistics update and the Document update take place as different tasks.
o V1 & V2 dont need scheduling.
Serialized V3 Update: The V3 collective update must be scheduled as a job (via LBWE). Here, document data is collected in the order it was created and transferred into the BW as a batch job. The transfer sequence may not be the same as the order in which the data was created in all scenarios. V3 update only processes the update data that is successfully processed with the V2 update.
FULL update, this will load everything which is there in the source system and then do INIT WITHOUT DATA TRANSFER to set the delta and schedule your delta loads accordingly.
Init Delta
You run an init delta from BW sytem using an info package .
Init delta will create an entry in R3 side table ROOSPRMSC with the filed init state with 'X' . Then upon this entry the system estbalishes a link between Extraction Queue . After succesfull initilization you can see the data source in RSA7 in R3 side . Then after this only you can extract data from the set up table .
Init Delta Types:
Init Delta
This will initialize the delta in R3 and exctract the set up table data into R3 . It is full update .
Init Delta without data transfer
This will only initialize the delta , No extraction takes place .
Use of init delta .
Without init delta you cannot schedule an Extraction . If you have initialized a delta , You can get delta reocrds from the succesive run in the delta Q .
When ever you need to do a extraction if for the first time you run a scheduler you will get
Full Update
Init Delta
Full Update =====> Init Delta + Extraction
Init Delta =======> Initialization first , Extarction
Init Delta Without data transfer ====> Only Initialize in RSA7 .
After the first Run u get ....Folowing in Scheduler
Full Update ,Delta Update .
Queued Delta: Document posting -->Appl table --> Stat table ---> 10,000 LUW ---> LBWQ ---> RSA7 ---> BW delta run delta into BW .
Here 10,000 Transaction is collected as 1 LUW and records moved to RSA7
In case of Queued delta LUW's are posted to Extractor Queue (LBWQ), by scheduling the V3 job we move the documents from Extractor queue to Delta Queue(i.e. RSA7) and we extract the LUW's from Delta Queue to BW side by running Delta Loads. Generally we prefer Queued Delta as it maintain the Extractor Log which us to handle the LUW's which are missed.
Direct Delta:
Document postings -> Appl table -> Stat tables --> RSA7 (Delta Queue ) ---> Using delta run delta come into BW .
Here each transaction is 1 LUW and each LUW is moved to RSA7 .
In case of Direct Delta LUW's are directly posted to Delta Queue(i.e. RSA7) and we extract the LUW's from Delta Queue to BW side by running Delta Loads. If we use Direct Delta it degrades the OLTP system performance because when LUW's are directly posted to Delta Queue (RSA7) the application is kept waiting untill all the enhancement code is executed.
Non-serialized V3 Update:With this update mode, the extraction data for the application considered is written as before into the update tables with the help of a V3 update module. They are kept there as long as the data is selected through an updating collective run and are processed. However, in contrast to the current default settings (serialized V3 update), the data in the updating collective run are thereby read without regard to sequence from the update tables and are transferred to the BW delta queue.
https://websmp102.sap-ag.de/~sapdownload/011000358700007535452002E/HOWTOCREATEGENERICDELTA.PDF (need id)
http://help.sap.com/saphelp_bw33/helpdata/en/3f/548c9ec754ee4d90188a4f108e0121/frameset.htm
Business Intelligence Performance Tuning [original link is broken]
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cccad390-0201-0010-5093-fd9ec8157802
How to load data
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
/people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
Delta Types and methods;&#57245;
Hope this helps.
****Assign Points if Helpful*****
Regards,
Ravikanth
Message was edited by:
Ravikanth.pnv

CO-PA extractor - how to update new budget

Hi,
I have the extractor 1_CO_PA010CLP1 for forecast reports.
when i have new budget approved, i need to the extractor pass that information.
The ETL process as configured as delta, so if i have new budget for the same material, the update dont exist.
As this extractor is a standard SAP, what is the best pratice to do what i need?
Delete all the data and made full update is not so good because we have lot of data, and if this is a option, the performance can worsen.
Someone have any idea or help for this issue?
I can provide more info if its necessary.
thank you.

Hi,
refer below thread
For Cost Center accounting, the most important datasources are 0CO_OM_CCA_9 (actual costs - line items) [http://help.sap.com/saphelp_nw04s/helpdata/en/8f/d93c00e39d5b4fb6eaa3bf16e6fb09/frameset.htm]
and 0CO_OM_CCA_1 (plan and actual costs - totals per fiscal period) [http://help.sap.com/saphelp_nw04s/helpdata/en/ae/8876724e671341a91ff3ba711bacd0/frameset.htm]
Thank,s

Trubleshoot after full update

hi,
after full update and reboot i got to emergency mode.
journalctl -xb
-- Logs begin at Mon 2014-03-03 11:19:31 IST, end at Sun 2014-06-08 01:13:42 IDT. --
Jun 08 01:12:02 up systemd-journal[135]: Runtime journal is using 8.0M (max allowed 100.9M, trying to leave 151.3M free of 1001.1M available → current limit 100.9M).
Jun 08 01:12:02 up systemd-journal[135]: Runtime journal is using 8.0M (max allowed 100.9M, trying to leave 151.3M free of 1001.1M available → current limit 100.9M).
Jun 08 01:12:02 up kernel: Initializing cgroup subsys cpuset
Jun 08 01:12:02 up kernel: Initializing cgroup subsys cpu
Jun 08 01:12:02 up kernel: Initializing cgroup subsys cpuacct
Jun 08 01:12:02 up kernel: Linux version 3.14.5-1-ARCH (nobody@var-lib-archbuild-testing-i686-tobias) (gcc version 4.9.0 20140521 (prerelease) (GCC) ) #1 SMP PREEMPT Sun Jun 1 07:38:50 CEST 2014
Jun 08 01:12:02 up kernel: e820: BIOS-provided physical RAM map:
Jun 08 01:12:02 up kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Jun 08 01:12:02 up kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
Jun 08 01:12:02 up kernel: BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
Jun 08 01:12:02 up kernel: BIOS-e820: [mem 0x0000000000100000-0x000000007fedffff] usable
Jun 08 01:12:02 up kernel: BIOS-e820: [mem 0x000000007fee0000-0x000000007fee2fff] ACPI NVS
Jun 08 01:12:02 up kernel: BIOS-e820: [mem 0x000000007fee3000-0x000000007feeffff] ACPI data
Jun 08 01:12:02 up kernel: BIOS-e820: [mem 0x000000007fef0000-0x000000007fefffff] reserved
Jun 08 01:12:02 up kernel: BIOS-e820: [mem 0x00000000f0000000-0x00000000f3ffffff] reserved
Jun 08 01:12:02 up kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000ffffffff] reserved
Jun 08 01:12:02 up kernel: Notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel!
Jun 08 01:12:02 up kernel: SMBIOS 2.4 present.
Jun 08 01:12:02 up kernel: DMI: System manufacturer System Product Name/M2N-E, BIOS ASUS M2N-E ACPI BIOS Revision 1401 04/01/2008
Jun 08 01:12:02 up kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jun 08 01:12:02 up kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Jun 08 01:12:02 up kernel: e820: last_pfn = 0x7fee0 max_arch_pfn = 0x100000
Jun 08 01:12:02 up kernel: MTRR default type: uncachable
Jun 08 01:12:02 up kernel: MTRR fixed ranges enabled:
Jun 08 01:12:02 up kernel: 00000-9FFFF write-back
Jun 08 01:12:02 up kernel: A0000-BFFFF uncachable
Jun 08 01:12:02 up kernel: C0000-C7FFF write-protect
Jun 08 01:12:02 up kernel: C8000-FFFFF uncachable
Jun 08 01:12:02 up kernel: MTRR variable ranges enabled:
Jun 08 01:12:02 up kernel: 0 base 0000000000 mask FF80000000 write-back
Jun 08 01:12:02 up kernel: 1 base 007FF00000 mask FFFFF00000 uncachable
Jun 08 01:12:02 up kernel: 2 disabled
Jun 08 01:12:02 up kernel: 3 disabled
Jun 08 01:12:02 up kernel: 4 disabled
Jun 08 01:12:02 up kernel: 5 disabled
Jun 08 01:12:02 up kernel: 6 disabled
Jun 08 01:12:02 up kernel: 7 disabled
Jun 08 01:12:02 up kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jun 08 01:12:02 up kernel: found SMP MP-table at [mem 0x000f5a10-0x000f5a1f] mapped at [c00f5a10]
Jun 08 01:12:02 up kernel: Scanning 1 areas for low memory corruption
Jun 08 01:12:02 up kernel: initial memory mapped: [mem 0x00000000-0x01bfffff]
Jun 08 01:12:02 up kernel: Base memory trampoline at [c009b000] 9b000 size 16384
Jun 08 01:12:02 up kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
Jun 08 01:12:02 up kernel: [mem 0x00000000-0x000fffff] page 4k
Jun 08 01:12:02 up kernel: init_memory_mapping: [mem 0x37000000-0x373fffff]
Jun 08 01:12:02 up kernel: [mem 0x37000000-0x373fffff] page 2M
Jun 08 01:12:02 up kernel: init_memory_mapping: [mem 0x30000000-0x36ffffff]
Jun 08 01:12:02 up kernel: [mem 0x30000000-0x36ffffff] page 2M
Jun 08 01:12:02 up kernel: init_memory_mapping: [mem 0x00100000-0x2fffffff]
Jun 08 01:12:02 up kernel: [mem 0x00100000-0x003fffff] page 4k
Jun 08 01:12:02 up kernel: [mem 0x00400000-0x2fffffff] page 2M
Jun 08 01:12:02 up kernel: init_memory_mapping: [mem 0x37400000-0x377fdfff]
Jun 08 01:12:02 up kernel: [mem 0x37400000-0x377fdfff] page 4k
Jun 08 01:12:02 up kernel: BRK [0x01798000, 0x01798fff] PGTABLE
Jun 08 01:12:02 up kernel: RAMDISK: [mem 0x7fbaf000-0x7fedefff]
Jun 08 01:12:02 up kernel: Allocated new RAMDISK: [mem 0x374ce000-0x377fd275]
Jun 08 01:12:02 up kernel: Move RAMDISK from [mem 0x7fbaf000-0x7fede275] to [mem 0x374ce000-0x377fd275]
Jun 08 01:12:02 up kernel: ACPI: RSDP 000f77a0 000024 (v02 Nvidia)
Jun 08 01:12:02 up kernel: ACPI: XSDT 7fee3100 00004C (v01 Nvidia ASUSACPI 42302E31 AWRD 00000000)
Jun 08 01:12:02 up kernel: ACPI: FACP 7feeac80 0000F4 (v03 Nvidia ASUSACPI 42302E31 AWRD 00000000)
Jun 08 01:12:02 up kernel: ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Pm1aEventBlock: 32/8 (20131218/tbfadt-603)
Jun 08 01:12:02 up kernel: ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Pm1aControlBlock: 16/8 (20131218/tbfadt-603)
Jun 08 01:12:02 up kernel: ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/PmTimerBlock: 32/8 (20131218/tbfadt-603)
Jun 08 01:12:02 up kernel: ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Gpe0Block: 64/8 (20131218/tbfadt-603)
Jun 08 01:12:02 up kernel: ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Gpe1Block: 128/8 (20131218/tbfadt-603)
Jun 08 01:12:02 up kernel: ACPI BIOS Warning (bug): Invalid length for FADT/Pm1aEventBlock: 8, using default 32 (20131218/tbfadt-684)
Jun 08 01:12:02 up kernel: ACPI BIOS Warning (bug): Invalid length for FADT/Pm1aControlBlock: 8, using default 16 (20131218/tbfadt-684)
Jun 08 01:12:02 up kernel: ACPI BIOS Warning (bug): Invalid length for FADT/PmTimerBlock: 8, using default 32 (20131218/tbfadt-684)
Jun 08 01:12:02 up kernel: ACPI: DSDT 7fee3280 007985 (v01 NVIDIA AWRDACPI 00001000 MSFT 03000000)
Jun 08 01:12:02 up kernel: ACPI: FACS 7fee0000 000040
Jun 08 01:12:02 up kernel: ACPI: SSDT 7feeaec0 0001C4 (v01 PTLTD POWERNOW 00000001 LTP 00000001)
Jun 08 01:12:02 up kernel: ACPI: HPET 7feeb100 000038 (v01 Nvidia ASUSACPI 42302E31 AWRD 00000098)
Jun 08 01:12:02 up kernel: ACPI: MCFG 7feeb180 00003C (v01 Nvidia ASUSACPI 42302E31 AWRD 00000000)
Jun 08 01:12:02 up kernel: ACPI: APIC 7feeadc0 000098 (v01 Nvidia ASUSACPI 42302E31 AWRD 00000000)
Jun 08 01:12:02 up kernel: ACPI: Local APIC address 0xfee00000
Jun 08 01:12:02 up kernel: 1158MB HIGHMEM available.
Jun 08 01:12:02 up kernel: 887MB LOWMEM available.
Jun 08 01:12:02 up kernel: mapped low ram: 0 - 377fe000
Jun 08 01:12:02 up kernel: low ram: 0 - 377fe000
Jun 08 01:12:02 up kernel: BRK [0x01799000, 0x01799fff] PGTABLE
Jun 08 01:12:02 up kernel: Zone ranges:
Jun 08 01:12:02 up kernel: DMA [mem 0x00001000-0x00ffffff]
Jun 08 01:12:02 up kernel: Normal [mem 0x01000000-0x377fdfff]
Jun 08 01:12:02 up kernel: HighMem [mem 0x377fe000-0x7fedffff]
Jun 08 01:12:02 up kernel: Movable zone start for each node
Jun 08 01:12:02 up kernel: Early memory node ranges
Jun 08 01:12:02 up kernel: node 0: [mem 0x00001000-0x0009efff]
Jun 08 01:12:02 up kernel: node 0: [mem 0x00100000-0x7fedffff]
Jun 08 01:12:02 up kernel: On node 0 totalpages: 523902
Jun 08 01:12:02 up kernel: free_area_init_node: node 0, pgdat c15fc640, node_mem_map f64ce020
Jun 08 01:12:02 up kernel: DMA zone: 32 pages used for memmap
Jun 08 01:12:02 up kernel: DMA zone: 0 pages reserved
Jun 08 01:12:02 up kernel: DMA zone: 3998 pages, LIFO batch:0
Jun 08 01:12:02 up kernel: Normal zone: 1744 pages used for memmap
Jun 08 01:12:02 up kernel: Normal zone: 223230 pages, LIFO batch:31
Jun 08 01:12:02 up kernel: HighMem zone: 2318 pages used for memmap
Jun 08 01:12:02 up kernel: HighMem zone: 296674 pages, LIFO batch:31
Jun 08 01:12:02 up kernel: Using APIC driver default
Jun 08 01:12:02 up kernel: Detected use of extended apic ids on hypertransport bus
Jun 08 01:12:02 up kernel: ACPI: PM-Timer IO Port: 0x1008
Jun 08 01:12:02 up kernel: ACPI: Local APIC address 0xfee00000
Jun 08 01:12:02 up kernel: ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jun 08 01:12:02 up kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jun 08 01:12:02 up kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] disabled)
Jun 08 01:12:02 up kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] disabled)
Jun 08 01:12:02 up kernel: ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jun 08 01:12:02 up kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jun 08 01:12:02 up kernel: ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jun 08 01:12:02 up kernel: ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jun 08 01:12:02 up kernel: ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
Jun 08 01:12:02 up kernel: IOAPIC[0]: apic_id 4, version 17, address 0xfec00000, GSI 0-23
Jun 08 01:12:02 up kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jun 08 01:12:02 up kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jun 08 01:12:02 up kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge)
Jun 08 01:12:02 up kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge)
Jun 08 01:12:02 up kernel: ACPI: IRQ0 used by override.
Jun 08 01:12:02 up kernel: ACPI: IRQ2 used by override.
Jun 08 01:12:02 up kernel: ACPI: IRQ9 used by override.
Jun 08 01:12:02 up kernel: ACPI: IRQ14 used by override.
Jun 08 01:12:02 up kernel: ACPI: IRQ15 used by override.
Jun 08 01:12:02 up kernel: Using ACPI (MADT) for SMP configuration information
Jun 08 01:12:02 up kernel: ACPI: HPET id: 0x10de8201 base: 0xfefff000
Jun 08 01:12:02 up kernel: smpboot: Allowing 4 CPUs, 2 hotplug CPUs
Jun 08 01:12:02 up kernel: nr_irqs_gsi: 40
Jun 08 01:12:02 up kernel: PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jun 08 01:12:02 up kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000effff]
Jun 08 01:12:02 up kernel: PM: Registered nosave memory: [mem 0x000f0000-0x000fffff]
Jun 08 01:12:02 up kernel: e820: [mem 0x7ff00000-0xefffffff] available for PCI devices
Jun 08 01:12:02 up kernel: Booting paravirtualized kernel on bare hardware
Jun 08 01:12:02 up kernel: setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:4 nr_node_ids:1
Jun 08 01:12:02 up kernel: PERCPU: Embedded 14 pages/cpu @f648a000 s33792 r0 d23552 u57344
Jun 08 01:12:02 up kernel: pcpu-alloc: s33792 r0 d23552 u57344 alloc=14*4096
Jun 08 01:12:02 up kernel: pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
Jun 08 01:12:02 up kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 522126
Jun 08 01:12:02 up kernel: Kernel command line: root=/dev/sda5 ro initrd=../initramfs-linux.img BOOT_IMAGE=../vmlinuz-linux
Jun 08 01:12:02 up kernel: PID hash table entries: 4096 (order: 2, 16384 bytes)
Jun 08 01:12:02 up kernel: Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Jun 08 01:12:02 up kernel: Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Jun 08 01:12:02 up kernel: Initializing CPU#0
Jun 08 01:12:02 up kernel: allocated 4191992 bytes of page_cgroup
Jun 08 01:12:02 up kernel: please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jun 08 01:12:02 up kernel: Initializing HighMem for node 0 (000377fe:0007fee0)
Jun 08 01:12:02 up kernel: Initializing Movable for node 0 (00000000:00000000)
Jun 08 01:12:02 up kernel: Memory: 2062936K/2095608K available (4445K kernel code, 470K rwdata, 1280K rodata, 568K init, 956K bss, 32672K reserved, 1186696K highmem)
Jun 08 01:12:02 up kernel: virtual kernel memory layout:
fixmap : 0xfff15000 - 0xfffff000 ( 936 kB)
pkmap : 0xff800000 - 0xffc00000 (4096 kB)
vmalloc : 0xf7ffe000 - 0xff7fe000 ( 120 MB)
lowmem : 0xc0000000 - 0xf77fe000 ( 887 MB)
.init : 0xc160f000 - 0xc169d000 ( 568 kB)
.data : 0xc1457b12 - 0xc160ebc0 (1756 kB)
.text : 0xc1000000 - 0xc1457b12 (4446 kB)
Jun 08 01:12:02 up kernel: Checking if this processor honours the WP bit even in supervisor mode...Ok.
Jun 08 01:12:02 up kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Jun 08 01:12:02 up kernel: Preemptible hierarchical RCU implementation.
Jun 08 01:12:02 up kernel: RCU dyntick-idle grace-period acceleration is enabled.
Jun 08 01:12:02 up kernel: Dump stacks of tasks blocking RCU-preempt GP.
Jun 08 01:12:02 up kernel: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
Jun 08 01:12:02 up kernel: RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
Jun 08 01:12:02 up kernel: NR_IRQS:2304 nr_irqs:712 16
Jun 08 01:12:02 up kernel: CPU 0 irqstacks, hard=f5808000 soft=f580a000
Jun 08 01:12:02 up kernel: spurious 8259A interrupt: IRQ7.
Jun 08 01:12:02 up kernel: Console: colour VGA+ 80x25
Jun 08 01:12:02 up kernel: console [tty0] enabled
Jun 08 01:12:02 up kernel: hpet clockevent registered
Jun 08 01:12:02 up kernel: tsc: Fast TSC calibration using PIT
Jun 08 01:12:02 up kernel: tsc: Detected 2009.051 MHz processor
Jun 08 01:12:02 up kernel: tsc: Marking TSC unstable due to TSCs unsynchronized
Jun 08 01:12:02 up kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 4019.52 BogoMIPS (lpj=6696836)
Jun 08 01:12:02 up kernel: pid_max: default: 32768 minimum: 301
Jun 08 01:12:02 up kernel: ACPI: Core revision 20131218
Jun 08 01:12:02 up kernel: ACPI: All ACPI Tables successfully acquired
Jun 08 01:12:02 up kernel: Security Framework initialized
Jun 08 01:12:02 up kernel: Yama: becoming mindful.
Jun 08 01:12:02 up kernel: Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
Jun 08 01:12:02 up kernel: Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
Jun 08 01:12:02 up kernel: Initializing cgroup subsys memory
Jun 08 01:12:02 up kernel: Initializing cgroup subsys devices
Jun 08 01:12:02 up kernel: Initializing cgroup subsys freezer
Jun 08 01:12:02 up kernel: Initializing cgroup subsys net_cls
Jun 08 01:12:02 up kernel: Initializing cgroup subsys blkio
Jun 08 01:12:02 up kernel: CPU: Physical Processor ID: 0
Jun 08 01:12:02 up kernel: CPU: Processor Core ID: 0
Jun 08 01:12:02 up kernel: mce: CPU supports 5 MCE banks
Jun 08 01:12:02 up kernel: LVT offset 0 assigned for vector 0xf9
Jun 08 01:12:02 up kernel: process: using AMD E400 aware idle routine
Jun 08 01:12:02 up kernel: Last level iTLB entries: 4KB 512, 2MB 8, 4MB 4
Last level dTLB entries: 4KB 512, 2MB 8, 4MB 4, 1GB 0
tlb_flushall_shift: 6
Jun 08 01:12:02 up kernel: Freeing SMP alternatives memory: 16K (c169d000 - c16a1000)
Jun 08 01:12:02 up kernel: ftrace: allocating 18915 entries in 37 pages
Jun 08 01:12:02 up kernel: Enabling APIC mode: Flat. Using 1 I/O APICs
Jun 08 01:12:02 up kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jun 08 01:12:02 up kernel: smpboot: CPU0: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ (fam: 0f, model: 4b, stepping: 02)
Jun 08 01:12:02 up kernel: Performance Events: AMD PMU driver.
Jun 08 01:12:02 up kernel: ... version: 0
Jun 08 01:12:02 up kernel: ... bit width: 48
Jun 08 01:12:02 up kernel: ... generic registers: 4
Jun 08 01:12:02 up kernel: ... value mask: 0000ffffffffffff
Jun 08 01:12:02 up kernel: ... max period: 00007fffffffffff
Jun 08 01:12:02 up kernel: ... fixed-purpose events: 0
Jun 08 01:12:02 up kernel: ... event mask: 000000000000000f
Jun 08 01:12:02 up kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jun 08 01:12:02 up kernel: CPU 1 irqstacks, hard=f58d8000 soft=f58da000
Jun 08 01:12:02 up kernel: x86: Booting SMP configuration:
Jun 08 01:12:02 up kernel: .... node #0, CPUs: #1
Jun 08 01:12:02 up kernel: Initializing CPU#1
Jun 08 01:12:02 up kernel: x86: Booted up 1 node, 2 CPUs
Jun 08 01:12:02 up kernel: smpboot: Total of 2 processors activated (8039.48 BogoMIPS)
Jun 08 01:12:02 up kernel: devtmpfs: initialized
Jun 08 01:12:02 up kernel: PM: Registering ACPI NVS region [mem 0x7fee0000-0x7fee2fff] (12288 bytes)
Jun 08 01:12:02 up kernel: pinctrl core: initialized pinctrl subsystem
Jun 08 01:12:02 up kernel: RTC time: 1:11:55, date: 06/08/14
Jun 08 01:12:02 up kernel: NET: Registered protocol family 16
Jun 08 01:12:02 up kernel: cpuidle: using governor ladder
Jun 08 01:12:02 up kernel: cpuidle: using governor menu
Jun 08 01:12:02 up kernel: node 0 link 0: io port [a000, ffff]
Jun 08 01:12:02 up kernel: TOM: 0000000080000000 aka 2048M
Jun 08 01:12:02 up kernel: node 0 link 0: mmio [a0000, bffff]
Jun 08 01:12:02 up kernel: node 0 link 0: mmio [80000000, efffffff]
Jun 08 01:12:02 up kernel: node 0 link 0: mmio [f4000000, fe02ffff]
Jun 08 01:12:02 up kernel: node 0 link 0: mmio [f0000000, f02fffff]
Jun 08 01:12:02 up kernel: bus: [bus 00-02] on node 0 link 0
Jun 08 01:12:02 up kernel: bus: 00 [io 0x0000-0xffff]
Jun 08 01:12:02 up kernel: bus: 00 [mem 0x000a0000-0x000bffff]
Jun 08 01:12:02 up kernel: bus: 00 [mem 0x80000000-0xf3ffffff]
Jun 08 01:12:02 up kernel: bus: 00 [mem 0xf4000000-0xffffffff]
Jun 08 01:12:02 up kernel: ACPI: bus type PCI registered
Jun 08 01:12:02 up kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jun 08 01:12:02 up kernel: PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf0000000-0xf3ffffff] (base 0xf0000000)
Jun 08 01:12:02 up kernel: PCI: MMCONFIG at [mem 0xf0000000-0xf3ffffff] reserved in E820
Jun 08 01:12:02 up kernel: PCI: Using MMCONFIG for extended config space
Jun 08 01:12:02 up kernel: PCI: Using configuration type 1 for base access
Jun 08 01:12:02 up kernel: bio: create slab <bio-0> at 0
Jun 08 01:12:02 up kernel: ACPI: Added _OSI(Module Device)
Jun 08 01:12:02 up kernel: ACPI: Added _OSI(Processor Device)
Jun 08 01:12:02 up kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
Jun 08 01:12:02 up kernel: ACPI: Added _OSI(Processor Aggregator Device)
Jun 08 01:12:02 up kernel: ACPI: Interpreter enabled
Jun 08 01:12:02 up kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131218/hwxface-580)
Jun 08 01:12:02 up kernel: ACPI: (supports S0 S1 S3 S4 S5)
Jun 08 01:12:02 up kernel: ACPI: Using IOAPIC for interrupt routing
Jun 08 01:12:02 up kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jun 08 01:12:02 up kernel: ACPI: No dock devices found.
Jun 08 01:12:02 up kernel: ACPI: \_PR_.C002: failed to get CPU APIC ID.
Jun 08 01:12:02 up kernel: ACPI: \_PR_.C003: failed to get CPU APIC ID.
Jun 08 01:12:02 up kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
Jun 08 01:12:02 up kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jun 08 01:12:02 up kernel: acpi PNP0A08:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jun 08 01:12:02 up kernel: acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge
Jun 08 01:12:02 up kernel: PCI host bridge to bus 0000:00
Jun 08 01:12:02 up kernel: pci_bus 0000:00: root bus resource [bus 00-ff]
Jun 08 01:12:02 up kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
Jun 08 01:12:02 up kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
Jun 08 01:12:02 up kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jun 08 01:12:02 up kernel: pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000dffff]
Jun 08 01:12:02 up kernel: pci_bus 0000:00: root bus resource [mem 0x7ff00000-0xfebfffff]
Jun 08 01:12:02 up kernel: pci 0000:00:00.0: [10de:0369] type 00 class 0x050000
Jun 08 01:12:02 up kernel: pci 0000:00:01.0: [10de:0360] type 00 class 0x060100
Jun 08 01:12:02 up kernel: pci 0000:00:01.1: [10de:0368] type 00 class 0x0c0500
Jun 08 01:12:02 up kernel: pci 0000:00:01.1: reg 0x10: [io 0xfc00-0xfc3f]
Jun 08 01:12:02 up kernel: pci 0000:00:01.1: reg 0x20: [io 0x1c00-0x1c3f]
Jun 08 01:12:02 up kernel: pci 0000:00:01.1: reg 0x24: [io 0x1c40-0x1c7f]
Jun 08 01:12:02 up kernel: pci 0000:00:01.1: PME# supported from D3hot D3cold
Jun 08 01:12:02 up kernel: pci 0000:00:02.0: [10de:036c] type 00 class 0x0c0310
Jun 08 01:12:02 up kernel: pci 0000:00:02.0: reg 0x10: [mem 0xfe02f000-0xfe02ffff]
Jun 08 01:12:02 up kernel: pci 0000:00:02.0: supports D1 D2
Jun 08 01:12:02 up kernel: pci 0000:00:02.0: PME# supported from D0 D1 D2 D3hot D3cold
Jun 08 01:12:02 up kernel: pci 0000:00:02.0: System wakeup disabled by ACPI
Jun 08 01:12:02 up kernel: pci 0000:00:02.1: [10de:036d] type 00 class 0x0c0320
Jun 08 01:12:02 up kernel: pci 0000:00:02.1: reg 0x10: [mem 0xfe02e000-0xfe02e0ff]
Jun 08 01:12:02 up kernel: pci 0000:00:02.1: supports D1 D2
Jun 08 01:12:02 up kernel: pci 0000:00:02.1: PME# supported from D0 D1 D2 D3hot D3cold
Jun 08 01:12:02 up kernel: pci 0000:00:02.1: System wakeup disabled by ACPI
Jun 08 01:12:02 up kernel: pci 0000:00:04.0: [10de:036e] type 00 class 0x01018a
Jun 08 01:12:02 up kernel: pci 0000:00:04.0: reg 0x20: [io 0xf000-0xf00f]
Jun 08 01:12:02 up kernel: pci 0000:00:05.0: [10de:037f] type 00 class 0x010185
Jun 08 01:12:02 up kernel: pci 0000:00:05.0: reg 0x10: [io 0x09f0-0x09f7]
Jun 08 01:12:02 up kernel: pci 0000:00:05.0: reg 0x14: [io 0x0bf0-0x0bf3]
Jun 08 01:12:02 up kernel: pci 0000:00:05.0: reg 0x18: [io 0x0970-0x0977]
Jun 08 01:12:02 up kernel: pci 0000:00:05.0: reg 0x1c: [io 0x0b70-0x0b73]
Jun 08 01:12:02 up kernel: pci 0000:00:05.0: reg 0x20: [io 0xdc00-0xdc0f]
Jun 08 01:12:02 up kernel: pci 0000:00:05.0: reg 0x24: [mem 0xfe02d000-0xfe02dfff]
Jun 08 01:12:02 up kernel: pci 0000:00:05.1: [10de:037f] type 00 class 0x010185
Jun 08 01:12:02 up kernel: pci 0000:00:05.1: reg 0x10: [io 0x09e0-0x09e7]
Jun 08 01:12:02 up kernel: pci 0000:00:05.1: reg 0x14: [io 0x0be0-0x0be3]
Jun 08 01:12:02 up kernel: pci 0000:00:05.1: reg 0x18: [io 0x0960-0x0967]
Jun 08 01:12:02 up kernel: pci 0000:00:05.1: reg 0x1c: [io 0x0b60-0x0b63]
Jun 08 01:12:02 up kernel: pci 0000:00:05.1: reg 0x20: [io 0xc800-0xc80f]
Jun 08 01:12:02 up kernel: pci 0000:00:05.1: reg 0x24: [mem 0xfe02c000-0xfe02cfff]
Jun 08 01:12:02 up kernel: pci 0000:00:05.2: [10de:037f] type 00 class 0x010185
Jun 08 01:12:02 up kernel: pci 0000:00:05.2: reg 0x10: [io 0xc400-0xc407]
Jun 08 01:12:02 up kernel: pci 0000:00:05.2: reg 0x14: [io 0xc000-0xc003]
Jun 08 01:12:02 up kernel: pci 0000:00:05.2: reg 0x18: [io 0xbc00-0xbc07]
Jun 08 01:12:02 up kernel: pci 0000:00:05.2: reg 0x1c: [io 0xb800-0xb803]
Jun 08 01:12:02 up kernel: pci 0000:00:05.2: reg 0x20: [io 0xb400-0xb40f]
Jun 08 01:12:02 up kernel: pci 0000:00:05.2: reg 0x24: [mem 0xfe02b000-0xfe02bfff]
Jun 08 01:12:02 up kernel: pci 0000:00:06.0: [10de:0370] type 01 class 0x060401
Jun 08 01:12:02 up kernel: pci 0000:00:06.0: System wakeup disabled by ACPI
Jun 08 01:12:02 up kernel: pci 0000:00:06.1: [10de:0371] type 00 class 0x040300
Jun 08 01:12:02 up kernel: pci 0000:00:06.1: reg 0x10: [mem 0xfe024000-0xfe027fff]
Jun 08 01:12:02 up kernel: pci 0000:00:06.1: PME# supported from D3hot D3cold
Jun 08 01:12:02 up kernel: pci 0000:00:06.1: System wakeup disabled by ACPI
Jun 08 01:12:02 up kernel: pci 0000:00:08.0: [10de:0373] type 00 class 0x068000
Jun 08 01:12:02 up kernel: pci 0000:00:08.0: reg 0x10: [mem 0xfe02a000-0xfe02afff]
Jun 08 01:12:02 up kernel: pci 0000:00:08.0: reg 0x14: [io 0xb000-0xb007]
Jun 08 01:12:02 up kernel: pci 0000:00:08.0: reg 0x18: [mem 0xfe029000-0xfe0290ff]
Jun 08 01:12:02 up kernel: pci 0000:00:08.0: reg 0x1c: [mem 0xfe028000-0xfe02800f]
Jun 08 01:12:02 up kernel: pci 0000:00:08.0: supports D1 D2
Jun 08 01:12:02 up kernel: pci 0000:00:08.0: PME# supported from D0 D1 D2 D3hot D3cold
Jun 08 01:12:02 up kernel: pci 0000:00:08.0: System wakeup disabled by ACPI
Jun 08 01:12:02 up kernel: pci 0000:00:0f.0: [10de:0377] type 01 class 0x060400
Jun 08 01:12:02 up kernel: pci 0000:00:0f.0: PME# supported from D0 D1 D2 D3hot D3cold
Jun 08 01:12:02 up kernel: pci 0000:00:0f.0: System wakeup disabled by ACPI
Jun 08 01:12:02 up kernel: pci 0000:00:18.0: [1022:1100] type 00 class 0x060000
Jun 08 01:12:02 up kernel: pci 0000:00:18.1: [1022:1101] type 00 class 0x060000
Jun 08 01:12:02 up kernel: pci 0000:00:18.2: [1022:1102] type 00 class 0x060000
Jun 08 01:12:02 up kernel: pci 0000:00:18.3: [1022:1103] type 00 class 0x060000
Jun 08 01:12:02 up kernel: pci 0000:00:06.0: PCI bridge to [bus 01] (subtractive decode)
Jun 08 01:12:02 up kernel: pci 0000:00:06.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
Jun 08 01:12:02 up kernel: pci 0000:00:06.0: bridge window [io 0x0d00-0xffff] (subtractive decode)
Jun 08 01:12:02 up kernel: pci 0000:00:06.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
Jun 08 01:12:02 up kernel: pci 0000:00:06.0: bridge window [mem 0x000c0000-0x000dffff] (subtractive decode)
Jun 08 01:12:02 up kernel: pci 0000:00:06.0: bridge window [mem 0x7ff00000-0xfebfffff] (subtractive decode)
Jun 08 01:12:02 up kernel: pci 0000:02:00.0: [10de:0392] type 00 class 0x030000
Jun 08 01:12:02 up kernel: pci 0000:02:00.0: reg 0x10: [mem 0xfa000000-0xfaffffff]
Jun 08 01:12:02 up kernel: pci 0000:02:00.0: reg 0x14: [mem 0xe0000000-0xefffffff 64bit pref]
Jun 08 01:12:02 up kernel: pci 0000:02:00.0: reg 0x1c: [mem 0xfb000000-0xfbffffff 64bit]
Jun 08 01:12:02 up kernel: pci 0000:02:00.0: reg 0x24: [io 0xac00-0xac7f]
Jun 08 01:12:02 up kernel: pci 0000:02:00.0: reg 0x30: [mem 0xfcfe0000-0xfcffffff pref]
Jun 08 01:12:02 up kernel: pci 0000:02:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
Jun 08 01:12:02 up kernel: pci 0000:00:0f.0: PCI bridge to [bus 02]
Jun 08 01:12:02 up kernel: pci 0000:00:0f.0: bridge window [io 0xa000-0xafff]
Jun 08 01:12:02 up kernel: pci 0000:00:0f.0: bridge window [mem 0xfa000000-0xfcffffff]
Jun 08 01:12:02 up kernel: pci 0000:00:0f.0: bridge window [mem 0xe0000000-0xefffffff 64bit pref]
Jun 08 01:12:02 up kernel: pci_bus 0000:00: on NUMA node 0
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LNK1] (IRQs 5 7 9 10 11 14 15) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LNK2] (IRQs 5 7 9 10 11 14 15) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LNK3] (IRQs 5 7 9 10 11 14 15) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LNK4] (IRQs 5 7 9 10 11 14 15) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LNK5] (IRQs 5 7 9 10 11 14 15) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LNK6] (IRQs 5 7 9 10 *11 14 15)
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LNK7] (IRQs 5 7 9 10 11 14 15) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LNK8] (IRQs 5 7 9 10 11 14 15) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LP2P] (IRQs 5 7 9 10 11 14 15) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LUBA] (IRQs 5 7 9 *10 11 14 15)
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LMAC] (IRQs 5 7 9 *10 11 14 15)
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LAZA] (IRQs 5 7 9 *10 11 14 15)
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LPMU] (IRQs 5 7 9 10 11 14 15) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LSMB] (IRQs *5 7 9 10 11 14 15)
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LUB2] (IRQs 5 7 9 10 *11 14 15)
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LIDE] (IRQs 5 7 9 10 11 14 15) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LSID] (IRQs *5 7 9 10 11 14 15)
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LFID] (IRQs 5 7 9 *10 11 14 15)
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LSA2] (IRQs 5 7 9 10 *11 14 15)
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APC1] (IRQs 16) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APC2] (IRQs 17) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APC3] (IRQs 18) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APC4] (IRQs 19) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APC5] (IRQs 16) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APC6] (IRQs 16) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APC7] (IRQs 16) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APC8] (IRQs 16) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APCF] (IRQs 20 21 22 23) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APCH] (IRQs 20 21 22 23) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APMU] (IRQs 20 21 22 23) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [AAZA] (IRQs 20 21 22 23) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APCS] (IRQs 20 21 22 23) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APCL] (IRQs 20 21 22 23) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APCM] (IRQs 20 21 22 23) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APCZ] (IRQs 20 21 22 23) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APSI] (IRQs 20 21 22 23) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APSJ] (IRQs 20 21 22 23) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [ASA2] (IRQs 20 21 22 23) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: Enabled 1 GPEs in block 20 to 5F
Jun 08 01:12:02 up kernel: vgaarb: device added: PCI:0000:02:00.0,decodes=io+mem,owns=io+mem,locks=none
Jun 08 01:12:02 up kernel: vgaarb: loaded
Jun 08 01:12:02 up kernel: vgaarb: bridge control possible 0000:02:00.0
Jun 08 01:12:02 up kernel: PCI: Using ACPI for IRQ routing
Jun 08 01:12:02 up kernel: PCI: pci_cache_line_size set to 64 bytes
Jun 08 01:12:02 up kernel: e820: reserve RAM buffer [mem 0x0009f000-0x0009ffff]
Jun 08 01:12:02 up kernel: e820: reserve RAM buffer [mem 0x7fee0000-0x7fffffff]
Jun 08 01:12:02 up kernel: NetLabel: Initializing
Jun 08 01:12:02 up kernel: NetLabel: domain hash size = 128
Jun 08 01:12:02 up kernel: NetLabel: protocols = UNLABELED CIPSOv4
Jun 08 01:12:02 up kernel: NetLabel: unlabeled traffic allowed by default
Jun 08 01:12:02 up kernel: HPET: 3 timers in total, 0 timers will be used for per-cpu timer
Jun 08 01:12:02 up kernel: hpet0: at MMIO 0xfefff000, IRQs 2, 8, 31
Jun 08 01:12:02 up kernel: hpet0: 3 comparators, 32-bit 25.000000 MHz counter
Jun 08 01:12:02 up kernel: Switched to clocksource hpet
Jun 08 01:12:02 up kernel: pnp: PnP ACPI init
Jun 08 01:12:02 up kernel: ACPI: bus type PNP registered
Jun 08 01:12:02 up kernel: system 00:00: [io 0x1000-0x107f] has been reserved
Jun 08 01:12:02 up kernel: system 00:00: [io 0x1080-0x10ff] has been reserved
Jun 08 01:12:02 up kernel: system 00:00: [io 0x1400-0x147f] has been reserved
Jun 08 01:12:02 up kernel: system 00:00: [io 0x1480-0x14ff] has been reserved
Jun 08 01:12:02 up kernel: system 00:00: [io 0x1800-0x187f] has been reserved
Jun 08 01:12:02 up kernel: system 00:00: [io 0x1880-0x18ff] has been reserved
Jun 08 01:12:02 up kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
Jun 08 01:12:02 up kernel: system 00:01: [io 0x04d0-0x04d1] has been reserved
Jun 08 01:12:02 up kernel: system 00:01: [io 0x0800-0x087f] has been reserved
Jun 08 01:12:02 up kernel: system 00:01: [io 0x0290-0x0297] has been reserved
Jun 08 01:12:02 up kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
Jun 08 01:12:02 up kernel: pnp 00:02: [dma 4]
Jun 08 01:12:02 up kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0200 (active)
Jun 08 01:12:02 up kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active)
Jun 08 01:12:02 up kernel: pnp 00:04: Plug and Play ACPI device, IDs PNP0b00 (active)
Jun 08 01:12:02 up kernel: pnp 00:05: Plug and Play ACPI device, IDs PNP0800 (active)
Jun 08 01:12:02 up kernel: pnp 00:06: Plug and Play ACPI device, IDs PNP0c04 (active)
Jun 08 01:12:02 up kernel: pnp 00:07: [dma 2]
Jun 08 01:12:02 up kernel: pnp 00:07: Plug and Play ACPI device, IDs PNP0700 (active)
Jun 08 01:12:02 up kernel: pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jun 08 01:12:02 up kernel: pnp 00:09: Plug and Play ACPI device, IDs PNP0400 (active)
Jun 08 01:12:02 up kernel: system 00:0a: [mem 0xf0000000-0xf3ffffff] has been reserved
Jun 08 01:12:02 up kernel: system 00:0a: Plug and Play ACPI device, IDs PNP0c02 (active)
Jun 08 01:12:02 up kernel: system 00:0b: [mem 0x000cde00-0x000cffff] has been reserved
Jun 08 01:12:02 up kernel: system 00:0b: [mem 0x000f0000-0x000f7fff] could not be reserved
Jun 08 01:12:02 up kernel: system 00:0b: [mem 0x000f8000-0x000fbfff] could not be reserved
Jun 08 01:12:02 up kernel: system 00:0b: [mem 0x000fc000-0x000fffff] could not be reserved
Jun 08 01:12:02 up kernel: system 00:0b: [mem 0xfefff000-0xfefff0ff] has been reserved
Jun 08 01:12:02 up kernel: system 00:0b: [mem 0x7fee0000-0x7fefffff] could not be reserved
Jun 08 01:12:02 up kernel: system 00:0b: [mem 0xffff0000-0xffffffff] has been reserved
Jun 08 01:12:02 up kernel: system 00:0b: [mem 0x00000000-0x0009ffff] could not be reserved
Jun 08 01:12:02 up kernel: system 00:0b: [mem 0x00100000-0x7fedffff] could not be reserved
Jun 08 01:12:02 up kernel: system 00:0b: [mem 0xfec00000-0xfec00fff] could not be reserved
Jun 08 01:12:02 up kernel: system 00:0b: [mem 0xfee00000-0xfeefffff] has been reserved
Jun 08 01:12:02 up kernel: system 00:0b: [mem 0xfefff000-0xfeffffff] could not be reserved
Jun 08 01:12:02 up kernel: system 00:0b: [mem 0xfff80000-0xfff80fff] has been reserved
Jun 08 01:12:02 up kernel: system 00:0b: [mem 0xfff90000-0xfffbffff] has been reserved
Jun 08 01:12:02 up kernel: system 00:0b: [mem 0xfffed000-0xfffeffff] has been reserved
Jun 08 01:12:02 up kernel: system 00:0b: Plug and Play ACPI device, IDs PNP0c01 (active)
Jun 08 01:12:02 up kernel: pnp: PnP ACPI: found 12 devices
Jun 08 01:12:02 up kernel: ACPI: bus type PNP unregistered
Jun 08 01:12:02 up kernel: pci 0000:00:06.0: PCI bridge to [bus 01]
Jun 08 01:12:02 up kernel: pci 0000:00:0f.0: PCI bridge to [bus 02]
Jun 08 01:12:02 up kernel: pci 0000:00:0f.0: bridge window [io 0xa000-0xafff]
Jun 08 01:12:02 up kernel: pci 0000:00:0f.0: bridge window [mem 0xfa000000-0xfcffffff]
Jun 08 01:12:02 up kernel: pci 0000:00:0f.0: bridge window [mem 0xe0000000-0xefffffff 64bit pref]
Jun 08 01:12:02 up kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
Jun 08 01:12:02 up kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
Jun 08 01:12:02 up kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
Jun 08 01:12:02 up kernel: pci_bus 0000:00: resource 7 [mem 0x000c0000-0x000dffff]
Jun 08 01:12:02 up kernel: pci_bus 0000:00: resource 8 [mem 0x7ff00000-0xfebfffff]
Jun 08 01:12:02 up kernel: pci_bus 0000:01: resource 4 [io 0x0000-0x0cf7]
Jun 08 01:12:02 up kernel: pci_bus 0000:01: resource 5 [io 0x0d00-0xffff]
Jun 08 01:12:02 up kernel: pci_bus 0000:01: resource 6 [mem 0x000a0000-0x000bffff]
Jun 08 01:12:02 up kernel: pci_bus 0000:01: resource 7 [mem 0x000c0000-0x000dffff]
Jun 08 01:12:02 up kernel: pci_bus 0000:01: resource 8 [mem 0x7ff00000-0xfebfffff]
Jun 08 01:12:02 up kernel: pci_bus 0000:02: resource 0 [io 0xa000-0xafff]
Jun 08 01:12:02 up kernel: pci_bus 0000:02: resource 1 [mem 0xfa000000-0xfcffffff]
Jun 08 01:12:02 up kernel: pci_bus 0000:02: resource 2 [mem 0xe0000000-0xefffffff 64bit pref]
Jun 08 01:12:02 up kernel: NET: Registered protocol family 2
Jun 08 01:12:02 up kernel: TCP established hash table entries: 8192 (order: 3, 32768 bytes)
Jun 08 01:12:02 up kernel: TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
Jun 08 01:12:02 up kernel: TCP: Hash tables configured (established 8192 bind 8192)
Jun 08 01:12:02 up kernel: TCP: reno registered
Jun 08 01:12:02 up kernel: UDP hash table entries: 512 (order: 2, 16384 bytes)
Jun 08 01:12:02 up kernel: UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
Jun 08 01:12:02 up kernel: NET: Registered protocol family 1
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APCF] enabled at IRQ 23
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APCL] enabled at IRQ 22
Jun 08 01:12:02 up kernel: pci 0000:00:05.0: Enabling HT MSI Mapping
Jun 08 01:12:02 up kernel: pci 0000:00:05.1: Enabling HT MSI Mapping
Jun 08 01:12:02 up kernel: pci 0000:00:05.2: Enabling HT MSI Mapping
Jun 08 01:12:02 up kernel: pci 0000:00:06.0: Enabling HT MSI Mapping
Jun 08 01:12:02 up kernel: pci 0000:00:06.1: Enabling HT MSI Mapping
Jun 08 01:12:02 up kernel: pci 0000:00:08.0: Enabling HT MSI Mapping
Jun 08 01:12:02 up kernel: pci 0000:00:0f.0: Enabling HT MSI Mapping
Jun 08 01:12:02 up kernel: pci 0000:02:00.0: Boot video device
Jun 08 01:12:02 up kernel: PCI: CLS 32 bytes, default 64
Jun 08 01:12:02 up kernel: Unpacking initramfs...
Jun 08 01:12:02 up kernel: Freeing initrd memory: 3264K (f74ce000 - f77fe000)
Jun 08 01:12:02 up kernel: apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
Jun 08 01:12:02 up kernel: apm: disabled - APM is not SMP safe.
Jun 08 01:12:02 up kernel: Scanning for low memory corruption every 60 seconds
Jun 08 01:12:02 up kernel: futex hash table entries: 1024 (order: 4, 65536 bytes)
Jun 08 01:12:02 up kernel: bounce pool size: 64 pages
Jun 08 01:12:02 up kernel: HugeTLB registered 4 MB page size, pre-allocated 0 pages
Jun 08 01:12:02 up kernel: zbud: loaded
Jun 08 01:12:02 up kernel: VFS: Disk quotas dquot_6.5.2
Jun 08 01:12:02 up kernel: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Jun 08 01:12:02 up kernel: msgmni has been set to 1717
Jun 08 01:12:02 up kernel: Key type big_key registered
Jun 08 01:12:02 up kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jun 08 01:12:02 up kernel: io scheduler noop registered
Jun 08 01:12:02 up kernel: io scheduler deadline registered
Jun 08 01:12:02 up kernel: io scheduler cfq registered (default)
Jun 08 01:12:02 up kernel: pcieport 0000:00:0f.0: irq 40 for MSI/MSI-X
Jun 08 01:12:02 up kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jun 08 01:12:02 up kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jun 08 01:12:02 up kernel: GHES: HEST is not enabled!
Jun 08 01:12:02 up kernel: isapnp: Scanning for PnP cards...
Jun 08 01:12:02 up kernel: isapnp: No Plug & Play device found
Jun 08 01:12:02 up kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
Jun 08 01:12:02 up kernel: 00:08: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jun 08 01:12:02 up kernel: rtc_cmos 00:04: RTC can wake from S4
Jun 08 01:12:02 up kernel: rtc_cmos 00:04: rtc core: registered rtc_cmos as rtc0
Jun 08 01:12:02 up kernel: rtc_cmos 00:04: alarms up to one year, y3k, 242 bytes nvram, hpet irqs
Jun 08 01:12:02 up kernel: ledtrig-cpu: registered to indicate activity on CPUs
Jun 08 01:12:02 up kernel: TCP: cubic registered
Jun 08 01:12:02 up kernel: NET: Registered protocol family 10
Jun 08 01:12:02 up kernel: NET: Registered protocol family 17
Jun 08 01:12:02 up kernel: Using IPI No-Shortcut mode
Jun 08 01:12:02 up kernel: registered taskstats version 1
Jun 08 01:12:02 up kernel: Magic number: 2:319:154
Jun 08 01:12:02 up kernel: acpi device:21: hash matches
Jun 08 01:12:02 up kernel: rtc_cmos 00:04: setting system clock to 2014-06-08 01:11:56 UTC (1402189916)
Jun 08 01:12:02 up kernel: PM: Hibernation image not present or could not be loaded.
Jun 08 01:12:02 up kernel: Freeing unused kernel memory: 568K (c160f000 - c169d000)
Jun 08 01:12:02 up kernel: Write protecting the kernel text: 4448k
Jun 08 01:12:02 up kernel: Write protecting the kernel read-only data: 1284k
Jun 08 01:12:02 up kernel: random: systemd-tmpfile urandom read with 0 bits of entropy available
Jun 08 01:12:02 up systemd-udevd[47]: starting version 213
Jun 08 01:12:02 up kernel: i8042: PNP: No PS/2 controller found. Probing ports directly.
Jun 08 01:12:02 up kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Jun 08 01:12:02 up kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Jun 08 01:12:02 up kernel: Floppy drive(s): fd0 is 1.44M
Jun 08 01:12:02 up kernel: ACPI: bus type USB registered
Jun 08 01:12:02 up kernel: usbcore: registered new interface driver usbfs
Jun 08 01:12:02 up kernel: usbcore: registered new interface driver hub
Jun 08 01:12:02 up kernel: usbcore: registered new device driver usb
Jun 08 01:12:02 up kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jun 08 01:12:02 up kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jun 08 01:12:02 up kernel: ohci-pci: OHCI PCI platform driver
Jun 08 01:12:02 up kernel: ohci-pci 0000:00:02.0: OHCI PCI host controller
Jun 08 01:12:02 up kernel: ohci-pci 0000:00:02.0: new USB bus registered, assigned bus number 1
Jun 08 01:12:02 up kernel: ohci-pci 0000:00:02.0: irq 23, io mem 0xfe02f000
Jun 08 01:12:02 up kernel: SCSI subsystem initialized
Jun 08 01:12:02 up kernel: ehci-pci: EHCI PCI platform driver
Jun 08 01:12:02 up kernel: libata version 3.00 loaded.
Jun 08 01:12:02 up kernel: FDC 0 is a post-1991 82077
Jun 08 01:12:02 up kernel: hub 1-0:1.0: USB hub found
Jun 08 01:12:02 up kernel: hub 1-0:1.0: 10 ports detected
Jun 08 01:12:02 up kernel: ehci-pci 0000:00:02.1: EHCI Host Controller
Jun 08 01:12:02 up kernel: ehci-pci 0000:00:02.1: new USB bus registered, assigned bus number 2
Jun 08 01:12:02 up kernel: ehci-pci 0000:00:02.1: debug port 1
Jun 08 01:12:02 up kernel: ehci-pci 0000:00:02.1: cache line size of 32 is not supported
Jun 08 01:12:02 up kernel: ehci-pci 0000:00:02.1: irq 22, io mem 0xfe02e000
Jun 08 01:12:02 up kernel: ehci-pci 0000:00:02.1: USB 2.0 started, EHCI 1.00
Jun 08 01:12:02 up kernel: hub 2-0:1.0: USB hub found
Jun 08 01:12:02 up kernel: hub 2-0:1.0: 10 ports detected
Jun 08 01:12:02 up kernel: hub 1-0:1.0: USB hub found
Jun 08 01:12:02 up kernel: hub 1-0:1.0: 10 ports detected
Jun 08 01:12:02 up kernel: sata_nv 0000:00:05.0: version 3.5
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APSI] enabled at IRQ 21
Jun 08 01:12:02 up kernel: sata_nv 0000:00:05.0: Using SWNCQ mode
Jun 08 01:12:02 up kernel: scsi0 : sata_nv
Jun 08 01:12:02 up kernel: scsi1 : sata_nv
Jun 08 01:12:02 up kernel: ata1: SATA max UDMA/133 cmd 0x9f0 ctl 0xbf0 bmdma 0xdc00 irq 21
Jun 08 01:12:02 up kernel: ata2: SATA max UDMA/133 cmd 0x970 ctl 0xb70 bmdma 0xdc08 irq 21
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APSJ] enabled at IRQ 20
Jun 08 01:12:02 up kernel: sata_nv 0000:00:05.1: Using SWNCQ mode
Jun 08 01:12:02 up kernel: scsi2 : sata_nv
Jun 08 01:12:02 up kernel: scsi3 : sata_nv
Jun 08 01:12:02 up kernel: ata3: SATA max UDMA/133 cmd 0x9e0 ctl 0xbe0 bmdma 0xc800 irq 20
Jun 08 01:12:02 up kernel: ata4: SATA max UDMA/133 cmd 0x960 ctl 0xb60 bmdma 0xc808 irq 20
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [ASA2] enabled at IRQ 23
Jun 08 01:12:02 up kernel: sata_nv 0000:00:05.2: Using SWNCQ mode
Jun 08 01:12:02 up kernel: scsi4 : sata_nv
Jun 08 01:12:02 up kernel: scsi5 : sata_nv
Jun 08 01:12:02 up kernel: ata5: SATA max UDMA/133 cmd 0xc400 ctl 0xc000 bmdma 0xb400 irq 23
Jun 08 01:12:02 up kernel: ata6: SATA max UDMA/133 cmd 0xbc00 ctl 0xb800 bmdma 0xb408 irq 23
Jun 08 01:12:02 up kernel: pata_amd 0000:00:04.0: version 0.4.1
Jun 08 01:12:02 up kernel: scsi6 : pata_amd
Jun 08 01:12:02 up kernel: scsi7 : pata_amd
Jun 08 01:12:02 up kernel: ata7: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xf000 irq 14
Jun 08 01:12:02 up kernel: ata8: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xf008 irq 15
Jun 08 01:12:02 up kernel: ata3: SATA link down (SStatus 0 SControl 300)
Jun 08 01:12:02 up kernel: ata5: SATA link down (SStatus 0 SControl 300)
Jun 08 01:12:02 up kernel: usb 2-4: new high-speed USB device number 4 using ehci-pci
Jun 08 01:12:02 up kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jun 08 01:12:02 up kernel: ata1.00: ATA-8: WDC WD6400AAKS-00A7B0, 01.03B01, max UDMA/133
Jun 08 01:12:02 up kernel: ata1.00: 1250263728 sectors, multi 1: LBA48 NCQ (depth 31/32)
Jun 08 01:12:02 up kernel: hub 2-4:1.0: USB hub found
Jun 08 01:12:02 up kernel: hub 2-4:1.0: 4 ports detected
Jun 08 01:12:02 up kernel: ata1.00: configured for UDMA/133
Jun 08 01:12:02 up kernel: scsi 0:0:0:0: Direct-Access ATA WDC WD6400AAKS-0 01.0 PQ: 0 ANSI: 5
Jun 08 01:12:02 up kernel: ata2: SATA link down (SStatus 0 SControl 300)
Jun 08 01:12:02 up kernel: usb 1-2: new low-speed USB device number 2 using ohci-pci
Jun 08 01:12:02 up kernel: ata4: SATA link down (SStatus 0 SControl 300)
Jun 08 01:12:02 up kernel: hidraw: raw HID events driver (C) Jiri Kosina
Jun 08 01:12:02 up kernel: sd 0:0:0:0: [sda] 1250263728 512-byte logical blocks: (640 GB/596 GiB)
Jun 08 01:12:02 up kernel: sd 0:0:0:0: [sda] Write Protect is off
Jun 08 01:12:02 up kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Jun 08 01:12:02 up kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jun 08 01:12:02 up kernel: usbcore: registered new interface driver usbhid
Jun 08 01:12:02 up kernel: usbhid: USB HID core driver
Jun 08 01:12:02 up kernel: input: Microsoft Comfort Curve Keyboard 3000 as /devices/pci0000:00/0000:00:02.0/usb1/1-2/1-2:1.0/0003:045E:0780.0001/input/input2
Jun 08 01:12:02 up kernel: hid-generic 0003:045E:0780.0001: input,hidraw0: USB HID v1.11 Keyboard [Microsoft Comfort Curve Keyboard 3000] on usb-0000:00:02.0-2/input0
Jun 08 01:12:02 up kernel: input: Microsoft Comfort Curve Keyboard 3000 as /devices/pci0000:00/0000:00:02.0/usb1/1-2/1-2:1.1/0003:045E:0780.0002/input/input3
Jun 08 01:12:02 up kernel: hid-generic 0003:045E:0780.0002: input,hidraw1: USB HID v1.11 Device [Microsoft Comfort Curve Keyboard 3000] on usb-0000:00:02.0-2/input1
Jun 08 01:12:02 up kernel: sda: sda1 sda2 sda3 < sda5 sda6 sda7 > sda4
Jun 08 01:12:02 up kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Jun 08 01:12:02 up kernel: usb 1-3: new low-speed USB device number 3 using ohci-pci
Jun 08 01:12:02 up kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jun 08 01:12:02 up kernel: ata6.00: ATA-7: WDC WD2500KS-00MJB0, 02.01C03, max UDMA/133
Jun 08 01:12:02 up kernel: ata6.00: 488397168 sectors, multi 1: LBA48
Jun 08 01:12:02 up kernel: ata6.00: configured for UDMA/133
Jun 08 01:12:02 up kernel: scsi 5:0:0:0: Direct-Access ATA WDC WD2500KS-00M 02.0 PQ: 0 ANSI: 5
Jun 08 01:12:02 up kernel: sd 5:0:0:0: [sdb] 488397168 512-byte logical blocks: (250 GB/232 GiB)
Jun 08 01:12:02 up kernel: ata8: port disabled--ignoring
Jun 08 01:12:02 up kernel: sd 5:0:0:0: [sdb] Write Protect is off
Jun 08 01:12:02 up kernel: sd 5:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Jun 08 01:12:02 up kernel: sd 5:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jun 08 01:12:02 up kernel: sdb: sdb1 sdb4
Jun 08 01:12:02 up kernel: sd 5:0:0:0: [sdb] Attached SCSI disk
Jun 08 01:12:02 up kernel: input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:02.0/usb1/1-3/1-3:1.0/0003:046D:C025.0003/input/input4
Jun 08 01:12:02 up kernel: hid-generic 0003:046D:C025.0003: input,hidraw2: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:02.0-3/input0
Jun 08 01:12:02 up kernel: random: nonblocking pool is initialized
Jun 08 01:12:02 up kernel: EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
Jun 08 01:12:02 up systemd[1]: RTC configured in localtime, applying delta of 180 minutes to system time.
Jun 08 01:12:02 up systemd[1]: systemd 213 running in system mode. (+PAM -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ +SECCOMP -APPARMOR)
Jun 08 01:12:02 up systemd[1]: Detected architecture 'x86'.
Jun 08 01:12:02 up systemd[1]: Set hostname to <up>.
Jun 08 01:12:02 up systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
Jun 08 01:12:02 up systemd[1]: Started Forward Password Requests to Wall Directory Watch.
Jun 08 01:12:02 up systemd[1]: Starting Remote File Systems.
Jun 08 01:12:02 up systemd[1]: Reached target Remote File Systems.
Jun 08 01:12:02 up systemd[1]: Starting Encrypted Volumes.
Jun 08 01:12:02 up systemd[1]: Reached target Encrypted Volumes.
Jun 08 01:12:02 up systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
Jun 08 01:12:02 up systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
Jun 08 01:12:02 up systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
Jun 08 01:12:02 up systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
Jun 08 01:12:02 up systemd[1]: Starting Paths.
Jun 08 01:12:02 up systemd[1]: Reached target Paths.
Jun 08 01:12:02 up systemd[1]: Starting Swap.
Jun 08 01:12:02 up systemd[1]: Reached target Swap.
Jun 08 01:12:02 up systemd[1]: Expecting device dev-sda6.device...
Jun 08 01:12:02 up systemd[1]: Starting Root Slice.
Jun 08 01:12:02 up systemd[1]: Created slice Root Slice.
Jun 08 01:12:02 up systemd[1]: Starting User and Session Slice.
Jun 08 01:12:02 up systemd[1]: Created slice User and Session Slice.
Jun 08 01:12:02 up systemd[1]: Starting Delayed Shutdown Socket.
Jun 08 01:12:02 up systemd[1]: Listening on Delayed Shutdown Socket.
Jun 08 01:12:02 up systemd[1]: Starting Device-mapper event daemon FIFOs.
Jun 08 01:12:02 up systemd[1]: Listening on Device-mapper event daemon FIFOs.
Jun 08 01:12:02 up systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
Jun 08 01:12:02 up systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
Jun 08 01:12:02 up systemd[1]: Starting udev Kernel Socket.
Jun 08 01:12:02 up systemd[1]: Listening on udev Kernel Socket.
Jun 08 01:12:02 up systemd[1]: Starting udev Control Socket.
Jun 08 01:12:02 up systemd[1]: Listening on udev Control Socket.
Jun 08 01:12:02 up systemd[1]: Starting LVM2 metadata daemon socket.
Jun 08 01:12:02 up systemd[1]: Listening on LVM2 metadata daemon socket.
Jun 08 01:12:02 up systemd[1]: Starting Journal Socket.
Jun 08 01:12:02 up systemd[1]: Listening on Journal Socket.
Jun 08 01:12:02 up systemd[1]: Starting System Slice.
Jun 08 01:12:02 up systemd[1]: Created slice System Slice.
Jun 08 01:12:02 up systemd[1]: Starting File System Check on Root Device...
Jun 08 01:12:02 up systemd[1]: Starting system-systemd\x2dfsck.slice.
Jun 08 01:12:02 up systemd[1]: Created slice system-systemd\x2dfsck.slice.
Jun 08 01:12:02 up systemd[1]: Mounting Temporary Directory...
Jun 08 01:12:02 up systemd[1]: tmp.mount: Directory /tmp to mount over is not empty, mounting anyway.
Jun 08 01:12:02 up systemd[1]: Starting system-getty.slice.
Jun 08 01:12:02 up systemd[1]: Created slice system-getty.slice.
Jun 08 01:12:02 up systemd[1]: Starting Set Up Additional Binary Formats...
Jun 08 01:12:02 up systemd[1]: Starting udev Coldplug all Devices...
Jun 08 01:12:02 up systemd[1]: Mounting Huge Pages File System...
Jun 08 01:12:02 up systemd[1]: Mounting Debug File System...
Jun 08 01:12:02 up systemd[1]: Starting Load Kernel Modules...
Jun 08 01:12:02 up systemd[1]: Mounting POSIX Message Queue File System...
Jun 08 01:12:02 up systemd[1]: Starting Create list of required static device nodes for the current kernel...
Jun 08 01:12:02 up systemd[1]: Starting Setup Virtual Console...
Jun 08 01:12:02 up systemd[1]: Starting Apply Kernel Variables...
Jun 08 01:12:02 up systemd[1]: Starting Journal Service...
Jun 08 01:12:02 up systemd[1]: Started Journal Service.
Jun 08 01:12:02 up kernel: vboxdrv: Found 2 processor cores.
Jun 08 01:12:02 up kernel: vboxdrv: fAsync=1 offMin=0x20125 offMax=0x20125
Jun 08 01:12:02 up kernel: vboxdrv: TSC mode is 'asynchronous', kernel timer mode is 'normal'.
Jun 08 01:12:02 up kernel: vboxdrv: Successfully loaded version 4.3.12_OSE (interface 0x001a0007).
Jun 08 01:12:02 up systemd-journal[135]: Journal started
-- Subject: The Journal has been started
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- The system journal process has been starting up, opened the journal
-- files for writing and is now ready to process requests.
Jun 08 01:12:02 up systemd[1]: Starting Slices.
-- Subject: Unit slices.target has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit slices.target has begun starting up.
Jun 08 01:12:02 up systemd[1]: Reached target Slices.
-- Subject: Unit slices.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit slices.target has finished starting up.
-- The start-up result is done.
Jun 08 01:12:02 up systemd[1]: Mounted Temporary Directory.
-- Subject: Unit tmp.mount has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit tmp.mount has finished starting up.
-- The start-up result is done.
Jun 08 01:12:02 up systemd[1]: Started Setup Virtual Console.
-- Subject: Unit systemd-vconsole-setup.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-vconsole-setup.service has finished starting up.
-- The start-up result is done.
Jun 08 01:12:02 up systemd[1]: Got automount request for /proc/sys/fs/binfmt_misc, triggered by 126 (systemd-binfmt)
Jun 08 01:12:02 up systemd[1]: Mounting Arbitrary Executable File Formats File System...
-- Subject: Unit proc-sys-fs-binfmt_misc.mount has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit proc-sys-fs-binfmt_misc.mount has begun starting up.
Jun 08 01:12:02 up systemd[1]: Mounted Huge Pages File System.
-- Subject: Unit dev-hugepages.mount has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit dev-hugepages.mount has finished starting up.
-- The start-up result is done.
Jun 08 01:12:02 up systemd[1]: Mounted Arbitrary Executable File Formats File System.
-- Subject: Unit proc-sys-fs-binfmt_misc.mount has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit proc-sys-fs-binfmt_misc.mount has finished starting up.
-- The start-up result is done.
Jun 08 01:12:02 up systemd[1]: Mounted POSIX Message Queue File System.
-- Subject: Unit dev-mqueue.mount has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit dev-mqueue.mount has finished starting up.
-- The start-up result is done.
Jun 08 01:12:02 up systemd[1]: Mounted Debug File System.
-- Subject: Unit sys-kernel-debug.mount has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit sys-kernel-debug.mount has finished starting up.
-- The start-up result is done.
Jun 08 01:12:02 up systemd[1]: Started Apply Kernel Variables.
-- Subject: Unit systemd-sysctl.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-sysctl.service has finished starting up.
-- The start-up result is done.
Jun 08 01:12:02 up systemd-modules-load[130]: Inserted module 'vboxdrv'
Jun 08 01:12:02 up systemd[1]: Started Create Static Device Nodes in /dev.
-- Subject: Unit systemd-tmpfiles-setup-dev.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-tmpfiles-setup-dev.service has finished starting up.
-- The start-up result is done.
Jun 08 01:12:02 up systemd[1]: Started Load Kernel Modules.
-- Subject: Unit systemd-modules-load.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-modules-load.service has finished starting up.
-- The start-up result is done.
Jun 08 01:12:02 up systemd[1]: Mounted FUSE Control File System.
-- Subject: Unit sys-fs-fuse-connections.mount has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit sys-fs-fuse-connections.mount has finished starting up.
-- The start-up result is done.
Jun 08 01:12:02 up systemd[1]: Mounting Configuration File System...
-- Subject: Unit sys-kernel-config.mount has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit sys-kernel-config.mount has begun starting up.
Jun 08 01:12:02 up systemd[1]: Starting udev Kernel Device Manager...
-- Subject: Unit systemd-udevd.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-udevd.service has begun starting up.
Jun 08 01:12:02 up systemd-fsck[121]: /dev/sda5: Superblock last write time is in the future.
Jun 08 01:12:02 up systemd-fsck[121]: (by less than a day, probably due to the hardware clock being incorrectly set). FIXED.
Jun 08 01:12:02 up systemd[1]: Mounted Configuration File System.
-- Subject: Unit sys-kernel-config.mount has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit sys-kernel-config.mount has finished starting up.
-- The start-up result is done.
Jun 08 01:12:02 up systemd[1]: Started udev Kernel Device Manager.
-- Subject: Unit systemd-udevd.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-udevd.service has finished starting up.
-- The start-up result is done.
Jun 08 01:12:02 up systemd-udevd[153]: starting version 213
Jun 08 01:12:02 up systemd-udevd[153]: invalid key/value pair in file /etc/udev/rules.d/50-embedded_devices.rules on line 8,starting at character 97 ('')
Jun 08 01:12:03 up kernel: input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input5
Jun 08 01:12:03 up kernel: ACPI: Power Button [PWRB]
Jun 08 01:12:03 up kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input6
Jun 08 01:12:03 up kernel: ACPI: Power Button [PWRF]
Jun 08 01:12:03 up kernel: ACPI: [Package] has zero elements (f5bfc400)
Jun 08 01:12:03 up kernel: ACPI: Invalid passive threshold
Jun 08 01:12:03 up kernel: thermal LNXTHERM:00: registered as thermal_zone0
Jun 08 01:12:03 up kernel: ACPI: Thermal Zone [THRM] (40 C)
Jun 08 01:12:03 up kernel: ACPI: Fan [FAN] (on)
Jun 08 01:12:03 up kernel: k8temp 0000:00:18.3: Temperature readouts might be wrong - check erratum #141
Jun 08 01:12:03 up kernel: input: PC Speaker as /devices/platform/pcspkr/input/input7
Jun 08 01:12:04 up kernel: microcode: AMD CPU family 0xf not supported
Jun 08 01:12:04 up kernel: kvm: Nested Virtualization enabled
Jun 08 01:12:04 up kernel: ACPI: PCI Interrupt Link [AAZA] enabled at IRQ 22
Jun 08 01:12:04 up kernel: hda_intel: msi for device 1043:81f6 set to 0
Jun 08 01:12:04 up kernel: microcode: AMD CPU family 0xf not supported
Jun 08 01:12:04 up kernel: powernow-k8: fid 0xc (2000 MHz), vid 0xc
Jun 08 01:12:04 up kernel: powernow-k8: fid 0xa (1800 MHz), vid 0xe
Jun 08 01:12:04 up kernel: powernow-k8: fid 0x2 (1000 MHz), vid 0x12
Jun 08 01:12:04 up kernel: powernow-k8: Found 1 AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ (2 cpu cores) (version 2.20.00)
Jun 08 01:12:04 up kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jun 08 01:12:04 up kernel: parport_pc 00:09: reported by Plug and Play ACPI
Jun 08 01:12:04 up kernel: parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE,EPP]
Jun 08 01:12:04 up kernel: forcedeth: Reverse Engineered nForce ethernet driver. Version 0.64.
Jun 08 01:12:04 up kernel: ACPI: PCI Interrupt Link [APCH] enabled at IRQ 21
Jun 08 01:12:04 up kernel: ppdev: user-space parallel port driver
Jun 08 01:12:04 up kernel: Linux agpgart interface v0.103
Jun 08 01:12:04 up kernel: forcedeth 0000:00:08.0: ifname eth0, PHY OUI 0x5043 @ 1, addr 00:1a:92:20:f8:d7
Jun 08 01:12:04 up kernel: forcedeth 0000:00:08.0: highdma csum vlan pwrctl mgmt gbit lnktim msi desc-v3
Jun 08 01:12:04 up kernel: i2c i2c-0: nForce2 SMBus adapter at 0x1c00
Jun 08 01:12:04 up kernel: ACPI Warning: SystemIO range 0x00001c40-0x00001c7f conflicts with OpRegion 0x00001c40-0x00001c45 (\_SB_.PCI0.SM01) (20131218/utaddress-258)
Jun 08 01:12:04 up kernel: ACPI Warning: SystemIO range 0x00001c40-0x00001c7f conflicts with OpRegion 0x00001c40-0x00001c45 (\_SB_.PCI0.SM00) (20131218/utaddress-258)
Jun 08 01:12:04 up kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jun 08 01:12:04 up kernel: nv_tco: NV TCO WatchDog Timer Driver v0.01
Jun 08 01:12:04 up kernel: nv_tco: Watchdog reboot not detected
Jun 08 01:12:04 up kernel: nv_tco: initialized (0x1440). heartbeat=30 sec (nowayout=0)
Jun 08 01:12:05 up mtp-probe[205]: checking bus 1, device 2: "/sys/devices/pci0000:00/0000:00:02.0/usb1/1-2"
Jun 08 01:12:05 up mtp-probe[204]: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:02.0/usb1/1-3"
Jun 08 01:12:05 up mtp-probe[204]: bus: 1, device: 3 was not an MTP device
Jun 08 01:12:05 up mtp-probe[205]: bus: 1, device: 2 was not an MTP device
Jun 08 01:12:05 up kernel: nvidia: module license 'NVIDIA' taints kernel.
Jun 08 01:12:05 up kernel: Disabling lock debugging due to kernel taint
Jun 08 01:12:05 up kernel: ACPI: PCI Interrupt Link [APC6] enabled at IRQ 16
Jun 08 01:12:05 up kernel: vgaarb: device changed decodes: PCI:0000:02:00.0,olddecodes=io+mem,decodes=none:owns=none
Jun 08 01:12:05 up kernel: NVRM: loading NVIDIA UNIX x86 Kernel Module 304.121 Tue Mar 4 19:50:35 PST 2014
Jun 08 01:12:05 up kernel: mousedev: PS/2 mouse device common for all mice
Jun 08 01:12:06 up kernel: input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:06.1/input/input9
Jun 08 01:12:07 up kernel: input: HDA NVidia Line Out Side as /devices/pci0000:00/0000:00:06.1/sound/card0/input15
Jun 08 01:12:07 up kernel: input: HDA NVidia Line Out CLFE as /devices/pci0000:00/0000:00:06.1/sound/card0/input14
Jun 08 01:12:07 up kernel: input: HDA NVidia Line Out Surround as /devices/pci0000:00/0000:00:06.1/sound/card0/input13
Jun 08 01:12:07 up kernel: input: HDA NVidia Line Out Front as /devices/pci0000:00/0000:00:06.1/sound/card0/input12
Jun 08 01:12:07 up kernel: input: HDA NVidia Line as /devices/pci0000:00/0000:00:06.1/sound/card0/input11
Jun 08 01:12:07 up kernel: input: HDA NVidia Rear Mic as /devices/pci0000:00/0000:00:06.1/sound/card0/input10
Jun 08 01:12:07 up systemd[1]: Starting Sound Card.
-- Subject: Unit sound.target has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit sound.target has begun starting up.
Jun 08 01:12:07 up systemd[1]: Reached target Sound Card.
-- Subject: Unit sound.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit sound.target has finished starting up.
-- The start-up result is done.
Jun 08 01:12:09 up systemd-fsck[121]: /dev/sda5: 175829/1228800 files (1.0% non-contiguous), 2992507/4907849 blocks
Jun 08 01:12:09 up systemd[1]: Started File System Check on Root Device.
-- Subject: Unit systemd-fsck-root.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-fsck-root.service has finished starting up.
-- The start-up result is done.
Jun 08 01:12:09 up systemd[1]: Starting Remount Root and Kernel File Systems...
-- Subject: Unit systemd-remount-fs.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-remount-fs.service has begun starting up.
Jun 08 01:12:09 up systemd[1]: Started Remount Root and Kernel File Systems.
-- Subject: Unit systemd-remount-fs.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-remount-fs.service has finished starting up.
-- The start-up result is done.
Jun 08 01:12:09 up systemd[1]: Starting Load/Save Random Seed...
-- Subject: Unit systemd-random-seed.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-random-seed.service has begun starting up.
Jun 08 01:12:09 up systemd[1]: Starting Local File Systems (Pre).
-- Subject: Unit local-fs-pre.target has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit local-fs-pre.target has begun starting up.
Jun 08 01:12:09 up systemd[1]: Reached target Local File Systems (Pre).
-- Subject: Unit local-fs-pre.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit local-fs-pre.target has finished starting up.
-- The start-up result is done.
Jun 08 01:12:09 up kernel: EXT4-fs (sda5): re-mounted. Opts: (null)
Jun 08 01:12:09 up systemd[1]: St

It sounds like a known bug for which a fix is already in [testing] and other information is available here on the forums.
Is your hardware clock set to UTC? and/or do you dual boot with Windows?

Update Functional Area on Secondary Cost Element

Hi gurus,
I'm trying to update Functional Area on Secondary Cost Element. I've created a LSMW to make it but when I run the bacthinput the system give me a message in order to inform me that this changes might need a lot of time because there are several internal changes to do.
The problem is that no functional area is updating, and I'm trying with just an item and the system needs a lot of time to update just one Funcional Area, more than a hour!
So, I don't know if some of you already had the same problem or is a problem with performance of system, because in Develop System I didn't have any issue to update this information.
Is there any form to update this information than LSMS or Individual transaction?
Kr
Jorge

Hi Jorge
I was trying to change it manually in KA02 and there are tasks the systems does before confirming.
This is the root cause.
"Field changes to field Functional Area lead to
complicated tests of the data involved, which
may take some time. Do you really want to change
the field online? "
There is an option to change it in background.
Regards

LO Extractor's Full update Functionality

Similar Messages

Maybe you are looking for