BLOB management

Hello,
I have to manipulate blob field from my vb application. I have to use a oracle client 7.3. When I connect to the DB with MS OLE DB provider for Oracle, an error occurs when I try to retrieve the blob field (datatype unsupported). So I see that the Oracle OLE DB provider supports blob field in ADO recordset. But Oracle OLEDB provider is only available from client 8i.
Is it possible to install Oracle OLEDB provider on a client 7.3 ?
Do you know another way to retrieve blob field from a vb application and using oracle client 7.3 ?
Thanks.

Database is 11gR2.
Inserting data from Java Program through prepared statement.
Sample code of Java program :
orclRawTrapsInsertStmt.setLong(1, rts.id);
                              orclRawTrapsInsertStmt.setString(2, rts.source_ip);
                              orclRawTrapsInsertStmt.setString(3, rts.oid);
                              orclRawTrapsInsertStmt.setString(4, rts.varbinds);
                              orclRawTrapsInsertStmt.setBytes(5, rts.trapObject); ------------ This is the line setting Java Object (as byte array) as Blob column value
                              orclRawTrapsInsertStmt.setString(6, rts.receivedTime);
                              orclRawTrapsInsertStmt.setInt(7, rts.trapVersion);
orclRawTrapsInsertStmt.executeUpdate();

Similar Messages

  • Write blobs to olite with VB and read/display with jsp

    How can I insert an image BLOB with Visual Basic into OLite 9i and afterwards read it again with JSP to display the image BLOB?

    Sure. There is even sample code for both VB and JSP in the Mobile SDK.
    ORACLE_HOME\Mobile\Sdk\Examples\BLOB Manager\SourceCode
    ORACLE_HOME\Mobile\Sdk\wtgsdk\src\sample6

  • SQL Server 2012 Management Studio: XML XQuery-query the XML Blob using CTE: How to specify the coorelation name in bulk rowset?

    Hi all,
    I just started doing the XML Xquery programming in my SQL Server 2012 Management Studio. I executed the following code:
    --query the XML Blob using a CTE (pulling from the XML file each time) Products
    WITH XmlFile (Contents) AS (
    SELECT CONVERT (XML, BulkColumn)
    FROM OPENROWSET (BULK 'H:\Products.xml', SINGLE_BLOB) ) AS XmlData
    SELECT *
    FROM XmlFile
    GO
    I got the the following Msg:
    Msg 491, Level 16, State 1, Line 4
    A correlation name must be specified for the bulk rowset in the from clause.
    How can I specify the correction name for the bulk rowset in my project?
    Please kindly help, advise and respond.
    Thanks in advance,
    Scott Chang

    Hello Scott,
    You have to assign a table alias for the OPENROWSET =>
    --query the XML Blob using a CTE (pulling from the XML file each time) Products
    WITH XmlFile (Contents) AS (
    SELECT CONVERT (XML, BulkColumn)
    FROM OPENROWSET (BULK 'H:\Products.xml', SINGLE_BLOB) AS MyXML ) AS XmlData
    SELECT *
    FROM XmlFile
    GO
    Olaf Helper
    [ Blog] [ Xing] [ MVP]

  • Managing blob images using ADF and JSF or struts

    Hello everyone. I am an ADF newbe and I am developing a web app. that has to manage (display, insert,update and delete) blob images from/to an oracle DB. I've seen the "howto" on image managing using intermedia and struts, but, for this new app I wanted to use JSF (something that is not mandatory) and, what is important is that the DB has already stored the images in blob format.
    Can anybody point me in the right direction please??? Is there any howtos on this subject???
    Thanks in advance.

    jfin wrote:
    but so far I have to say that I like the fact that I'll have to do very little
    System.out.println(<..../>....<>....</>).Assuming that you rather mean out.println() where out is the ServletOutputStream reference returned by HttpServletResponse#getOutputStream(), I can only agree with you. That's certainly not the way how JSP/Servlet code is to be written. The maintainability, extendability, reusability and testability would be far below the freezing point then. You need to write presentation logic in JSP files, not in Servlets and absolutely not in scriptlets inside a JSP.
    When you need to write presentation logic which may change per request, use JSTL and EL for that. Again, not scriptlets. For business and controlling logic, use Servlets. For transfer of data, use javabeans (DTO's, VO's). For data access logic, use DAO classes which are to be interacted by servlets.
    JSF removes the need for creating Servlets and using JSTL/EL in JSP files. You just have JSP pages with JSF tags for presentation and javabeans for the request values and backing beans for business logic.
    When would one use JSF over the other two? When Struts2? When Shale?And you ask that in a JSF forum? At least my opinion is predictable :)

  • Manage multiple blob in wizard

    Hi all,
    i need to temporarily store multiple blob files during a wizard before to save in tables, but a collection has only one blob attribute, so is there another way to create my wizard?
    Thanks,
    Sergio

    Hi,
    But you can have multiple rows in apex_collection.
    Create own collection for blob, and insert as many row you like.
    If you need link blob data to other collection data, use other collection columns
    Regards,
    Jari

  • Manage Blob files

    Hi there,
    I have a problem: I'm trying to open a .jpg file stored in a BLOB field of the Database. I've followed the instructions founded on the online help but what I get is a file which is totally different from the original one!
    here's my piece of code.. where am i wrong? Is there a better method to open a Blob file? thanks to all.
    CODE:
    String filename = "C:\\temp.jpg";
    File tempFile = new File(filename);
    BlobDomain myBlob = (BlobDomain) k.getAttribute("Documento");
    InputStream blobIn = myBlob.getBinaryStream();
    OutputStream fileOut = new FileOutputStream(tempFile);
    int next;
    while ((next = blobIn.read()) != -1) {
    fileOut.write(next);
    blobIn.close();
    fileOut.close();

    How are you selecting the unique row for the blob?

  • Can i see the column DATA(BLOB type) in PM_OBJECTS of DCM schema

    we installed DCM managed clustering .it is Database repository type.
    i am trying to see the column DATA(BLOB type) in PM_OBJECTS of DCM schema .
    I wrote a program in java to read blob data type and write it into a temporary file.
    when i open temporary files all the data in junk format.
    can i see the real data of thatcolumn.Is it possible?
    first of all for what purpose DCM shema will be used?

    Hi,
    There is no option to show the comments on the diagram.
    We plan to add such feature in the next version.
    Ivan

  • Unable to generate XML's for BLOB datatypes from Concurrent program

    Hi All,
    I've a requirement to print images on rtf layout. Images are uploaded by end user through attahments men
    there are getting stored in fnd_lobs tables.
    for printing blob images we need to convert them into CLOB and generate XML's.
    I've done the conversion through a function and calling the function in the select query which is generating XML when i run it from toad.
    SELECT xmlgen.getXml(
    'SELECT file_id,mob_getbase64String(file_data) photo
    FROM fnd_lobs
    WHERE file_id = 2490481'
    ,0
    ) FROM dual;
    But the same thing we i registered as concurrent program (SQL*Plus) the program is running into error.
    Output file
    The XML page cannot be displayed
    Cannot view XML input using style sheet. Please correct the error and then click the Refresh button, or try again later.
    Invalid at the top level of the document. Error processing resource 'https://dbtdev5i.oracleoutsourcing.com/OA_CGI/FNDWRR.e...
    Input truncated to 17 characters
    ^
    Log file
    Concurrent Manager encountered an error while running SQL*Plus for your concurrent request 10868311.
    Review your concurrent request log and/or report output file for more detailed information.
    Can anyone help me through on how to bypass this error and generate XML's.
    Thanks in Advance
    Jana

    Hi Priya..,
    I have changed the query and registered in apps and now i am able to generate XML's of the blob image and the same is getting printed on the tempate..
    DECLARE
    v_colb CLOB;
    v_query VARCHAR2(1000);
    BEGIN
    v_query := 'SELECT file_id,mob_getbase64String(file_data) photo
    FROM fnd_lobs fl,
    fnd_documents_vl fd
    WHERE fd.media_id = fl.file_id
    AND (fd.end_date_active IS NULL
    OR fd.end_date_active > SYSDATE)
    AND fd.security_type = 2
    AND fd.security_id = fnd_profile.value(''GL_SET_OF_BKS_ID'')';
    --FND_FILE.put_line( FND_FILE.LOG,v_query);
    v_colb := xmlgen.getxml (v_query, 0);
    --DBMS_OUTPUT.put_line (v_query);
    FND_FILE.put_line( FND_FILE.OUTPUT,v_colb);
    END;
    /

  • How to manage image in a column of a table

    Hi all,
    I am using Jdeveloper 11.1.1.2 and ADF faces.
    I would like to have a table with a column to save an image. After that I would like to have a page .jspx that visualize the fields of the table, including the image.
    I would like to know how I have to do:
    1) in the database to save the image
    2) to visualize and manage images on my .jspx page
    I have read something on the forum and googling, but I have found threads of one-two years ago, and I don't know if they give to me the right solution for my version of Jdeveloper.
    Can you give me a step by step procedure to solve my problem? Do you have any links to suggest me?
    Regards
    Andrea

    We did a web app a while ago and used image files for warehouse to show images of parts
    1. BLOB
    2. We didn't use adf. also I am using 10.1.3.4.

  • Reading the Blob and writing it to an external file in an xml tree format

    Hi,
    We have a table by name clarity_response_log and content of the column(Response_file) is BLOB and we have xml file or xml content in that column. Most probably the column or table may be having more than 5 records and hence we need to read the corresponding blob content and write to an external file.
    CREATE TABLE CLARITY_RESPONSE_LOG
      REQUEST_CODE   NUMBER,
      RESPONSE_FILE  BLOB,
      DATE_CRATED    DATE                           NOT NULL,
      CREATED_BY     NUMBER                         NOT NULL,
      UPDATED_BY     NUMBER                         DEFAULT 1,
      DATE_UPDATED   VARCHAR2(20 BYTE)              DEFAULT SYSDATE
    )The xml content in the insert statement is very small because of some reason and cannot be made public and indeed we have a very big xml file stored in the BLOB column or Response_File column
    Insert into CLARITY_RESPONSE_LOG
       (REQUEST_CODE, RESPONSE_FILE, DATE_CRATED, CREATED_BY, UPDATED_BY, DATE_UPDATED)
    Values
       (5, '<?xml version="1.0" encoding="UTF-8"?><xml-response><phone-number>1212121212</tracking-number></xml-response>', TO_DATE('09/23/2010 09:01:34', 'MM/DD/YYYY HH24:MI:SS'), 1, 1, '23-SEP-10');
    Insert into CLARITY_RESPONSE_LOG
       (REQUEST_CODE, RESPONSE_FILE, DATE_CRATED, CREATED_BY, UPDATED_BY, DATE_UPDATED)
    Values
       (6, '<?xml version="1.0" encoding="UTF-8"?><xml-response><phone-number>1212121212</tracking-number></xml-response>', TO_DATE('09/23/2010 09:01:34', 'MM/DD/YYYY HH24:MI:SS'), 1, 1, '23-SEP-10');
    Insert into CLARITY_RESPONSE_LOG
       (REQUEST_CODE, RESPONSE_FILE, DATE_CRATED, CREATED_BY, UPDATED_BY, DATE_UPDATED)
    Values
       (7, '<?xml version="1.0" encoding="UTF-8"?><xml-response><phone-number>1212121212</tracking-number></xml-response>', TO_DATE('09/23/2010 09:01:34', 'MM/DD/YYYY HH24:MI:SS'), 1, 1, '23-SEP-10');
    Insert into CLARITY_RESPONSE_LOG
       (REQUEST_CODE, RESPONSE_FILE, DATE_CRATED, CREATED_BY, UPDATED_BY, DATE_UPDATED)
    Values
       (8, '<?xml version="1.0" encoding="UTF-8"?><xml-response><phone-number>1212121212</tracking-number></xml-response>', TO_DATE('09/23/2010 09:01:34', 'MM/DD/YYYY HH24:MI:SS'), 1, 1, '23-SEP-10');
    Insert into CLARITY_RESPONSE_LOG
       (REQUEST_CODE, RESPONSE_FILE, DATE_CRATED, CREATED_BY, UPDATED_BY, DATE_UPDATED)
    Values
       (9, '<?xml version="1.0" encoding="UTF-8"?><xml-response><phone-number>1212121212</tracking-number></xml-response>', TO_DATE('09/23/2010 09:01:34', 'MM/DD/YYYY HH24:MI:SS'), 1, 1, '23-SEP-10');THe corresponding proc for reading the data and writing the data to an external file goes something like this
    SET serveroutput ON
    DECLARE
       vstart     NUMBER             := 1;
       bytelen    NUMBER             := 32000;
       len        NUMBER;
       my_vr      RAW (32000);
       x          NUMBER;
       l_output   UTL_FILE.FILE_TYPE;
    BEGIN
    -- define output directory
       l_output :=
          UTL_FILE.FOPEN ('CWFSTORE_RESPONCE_XML', 'extract500.txt', 'wb', 32760);
       vstart := 1;
       bytelen := 32000;
    ---get the Blob locator
       FOR rec IN (SELECT response_file vblob
                     FROM clarity_response_log
                    WHERE TRUNC (date_crated) = TRUNC (SYSDATE - 1))
       LOOP
    --get length of the blob
    len := DBMS_LOB.getlength (rec.vblob);
          DBMS_OUTPUT.PUT_LINE (len);
          x := len;
    ---- If small enough for a single write
    IF len < 32760
          THEN
             UTL_FILE.put_raw (l_output, rec.vblob);
             UTL_FILE.FFLUSH (l_output);
          ELSE  
    -------- write in pieces
             vstart := 1;
             WHILE vstart < len AND bytelen > 0
             LOOP
                DBMS_LOB.READ (rec.vblob, bytelen, vstart, my_vr);
                UTL_FILE.put_raw (l_output, my_vr);
                UTL_FILE.FFLUSH (l_output);
    ---------------- set the start position for the next cut
                vstart := vstart + bytelen;
    ---------- set the end position if less than 32000 bytes
                x := x - bytelen;
                IF x < 32000
                THEN
                   bytelen := x;
                END IF;
                UTL_FILE.NEW_LINE (l_output);
             END LOOP;
    ----------------- --- UTL_FILE.NEW_LINE(l_output);
          END IF;
       END LOOP;
       UTL_FILE.FCLOSE (l_output);
    END;The above code works well and all the records or xml contents are being written simultaneously adjacent to each other but we each records must be written to a new line or there must be a line gap or a blank line between any two records
    the code which I get is as follow all all xml data comes on a single line
    <?xml version="1.0" encoding="ISO-8859-1"?><emp><empno>7369</empno><ename>James</ename><job>Manager</job><salary>1000</salary></emp><?xml version="1.0" encoding="ISO-8859-1"?><emp><empno>7370</empno><ename>charles</ename><job>President</job><salary>500</salary></emp>But the code written to an external file has to be something like this.
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <emp>
      <empno>7369</empno>
      <ename>James</ename>
      <job>Manager</job>
      <salary>1000</salary>
    </emp>
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <emp>
    <empno>7370</empno>
    <ename>charles</ename>
    <job>President</job>
    <salary>500</salary>
    </emp>Please advice

    What was wrong with the previous answers given on your other thread:
    Export Blob data to text file(-29285-ORA-29285: file write error)
    If there's a continuing issue, stay with the same thread, don't just ask the same question again and again, it's really Pi**es people off and causes confusion as not everyone will be familiar with what answers you've already had. You're just wasting people's time by doing that.
    As already mentioned before, convert your BLOB to a CLOB and then to XMLTYPE where it can be treated as XML and written out to file in a variety of ways including the way I showed you on the other thread.
    You really seem to be struggling to get the worst possible way to work.

  • Sync files across the Managed Server.

    We have exploded war deployed in the Weblogic Cluster and in this there is a feature which would create a zip file in the exploded folder and this zip file will be downloaded through the URL. Now the problem in clustered environment is when the application write the zip file which will be available in only one of the managed server and when we try to download the zip file through the LoadBalancer URL it may not hit the same Managed Server in which the zip file is available.
    Is there a way in weblogic cluster to sync the files across all the managed server so that we can access the file through loadbalancer.

    Hi Suresh
    1. Your issue has nothing to do with the cluster setup and the way you deploy the application (as EAR or Exploded). Basically in your application, you generate a file and automatically that gets stored in that machines location. Now when you access it from a load balancer, the request may go to other machine and naturally it will not find the file there. There is nothing in the cluster setup or something that can copy the files and replicate acorss the machines. Infact that will be way too complex. I will couple of solutions.
    2. Create a shared folder like public folder. Say in Windows, create a folder with some folder structure and map it as say X: Drive. now this X Drive can be accessed from any other machine like Machine1, Machine2 (after setting the sharing properties). First try directly from Windows Explorer itself. Now within your application, when you generate and store the file, refer this X: Drive with full path. You can make it more flexible by using a .properties file that has key value pair. Key is like FILE_LOCATION and value can be like X:\a\b\c. Now using simple Java Properties class API to load the contents from this file. You can add all the constants, check for if .properties file exist like that. Once you have all the properties loaded, then refer this key, to get its value and use that to store the file generated. Use the same approach, while retrieving the file also. Use the key to get the location and then look for the file you want to download. This should work, when the request goes to any managed server in the cluster. I used it. I created a utility class like MyAppPropertiesLoader, with some static methods, that reads the file only once, if it is null, and then get values using simle methods like getString(String aKey), getLong(String aKey) etc. The huge BENEFIT of this is, once you deploy the application say in Unix, natually, the shared location has to be one of the unix boxes. Then just mount this location on both the managed servers (mount is similar to mapping a drive in Windows OS). Also the location of the files can be changed anytime in the properties file. Say in QC, the location may be X:\a\b\c\qc. But for UAT on Unix it can be like /x/y/z/uat/. Now this .properties file can exist directly under the Domain root folder so you can access it directly without any path in your java code. You can also use System properties like user.home etc. Make sure to copy this .properties file on both the domains. The original master domain. And the psueduo domain that is generated when you run the unpack command if you have managed server in another machine.
    3. This is much simpler but kind of not recommended. Simply, create a simple table with few header columns and one BLOB/CLOB column. Store the file in this database table and retrieve from it. This means you will have JDBC code, and the code to create clob to store and generate file from clob for retrieval.
    My preference is the first option given above. Getting tools to copy files may be complex. Its not like syncing the data across but its the files that needs to be copied across the machines.
    Thanks
    Ravi Jegga

  • IR Report found 1 million record with blob files performance is too slow!

    we are using
    oracle apex 4.2.x
    Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - Production
    mod_plsql with Apache
    Hardware: HP proliant ML350P
    OS: WINDOWS 2008 R2
    customized content management system developed in apex.when open the IR report have 1 ml rows found and each rows have blob(<5MB as pdf/tiff/bmp/jpg) it will be raising rows in future! but the searching performance is very slow!
    how can increasing the performance?
    how can showing progressing status to user while searching progress going on IR report itself?
    Thanx,
    Ram

    It's impossible to make definitive recommendations on performance improvement based on the limited information provided (in particular the absence of APEX debug traces and SQL execution plans), and lacking knowledge of the application  requirements and access to real data.
    As noted above, this is mainly a matter of data model and application design rather than a problem with APEX.
    Based on what has been made available on apex.oracle.com, taking action on the following points may improve performance.
    I have concerns about the data model. The multiple DMS_TOPMGT_MASTER.NWM_DOC_LVL_0x_COD_NUM columns are indications of incomplete normalization, and the use of the DMS_TOPMGT_DETAILS table hints at an EAV model. Look at normalizing the model so that the WM_DOC_LVL_0x_COD_NUM relationship data can be retrieved using a single join rather than multiple scalar subqueries. Store 1:1 document attributes as column values in DMS_TOPMGT_MASTER rather than rows in DMS_TOPMGT_DETAILS.
    There are no statistics on any of the application tables. Make sure statistics are gathered and kept up to date to enable the optimizer to determine correct execution plans.
    There are no indexes on any of the FK columns or search columns. Create indexes on FK columns to improve join performance, and on searched columns to improve search performance.
    More than 50% of the columns in the report query are hidden and not apparently used anywhere in the report. Why is this? A number of these columns are retrieved using scalar subqueries, which will adversely impact performance in a query processing 1 million+ rows. Remove any unnecessary columns from the report query.
    A number of functions are applied to columns in the report query. These will incur processing time for the functions themselves and context switching overhead in the case of the non-kernel dbms_lob.get_length calls. Remove these function calls from the query and replace them with alternative processing that will not impact query performance, particularly the use of APEX column attributes that will only apply transformations to values that are actually displayed, rather than to all rows processed in the query.
    Remove to_char calls from date columns and format them using date format masks in column attributes.
    Remove decode/case switches. Replace this logic using Display as Text (based on LOV, escape special characters) display types based on appropriate LOVs.
    Remove the dbms_lob.get_length calls. Instead add a file length column to the table, compute the file size when files are added/modified using your application or a trigger, and use this as the BLOB column in the query.
    Searching using the Search Field text box in the APEX interactive report Search Bar generates query like:
    select
    from
      (select
      from
        (...your report query...)
      ) r
      where ((instr(upper("NWM_DOC_REF_NO"), upper(:APXWS_SEARCH_STRING_1)) > 0
      or instr(upper("NWM_DOC_DESC"), upper(:APXWS_SEARCH_STRING_1)) > 0
      or instr(upper("SECTION_NAME"), upper(:APXWS_SEARCH_STRING_1)) > 0
      or instr(upper("CODE_TYPE"), upper(:APXWS_SEARCH_STRING_1)) > 0
      or instr(upper("REF_NUMBER_INDEX"), upper(:APXWS_SEARCH_STRING_1)) > 0
      or instr(upper("DATE_INDEX"), upper(:APXWS_SEARCH_STRING_1)) > 0
      or instr(upper("SUBJECT_INDEX"), upper(:apxws_search_string_1)) > 0
      or instr(upper("NWM_DOC_SERIEL"), upper(:APXWS_SEARCH_STRING_1)) > 0
      or instr(upper("NWM_DOC_DESCRIPTION"), upper(:APXWS_SEARCH_STRING_1)) > 0
      or instr(upper("NWM_DOC_STATUS"), upper(:APXWS_SEARCH_STRING_1)) > 0
      or instr(upper("MIME_TYPE"), upper(:APXWS_SEARCH_STRING_1)) > 0
      or instr(upper("NWM_DOC_FILE_BINARY"), upper(:APXWS_SEARCH_STRING_1)) > 0 ))
      ) r
    where
      rownum <= to_number(:APXWS_MAX_ROW_CNT)
    This will clearly never make use of any available indexes on your table. If you only want users to be able to search using values from 3 columns then remove the Search Field from the Search Bar and only allow users to create explicit filters on those columns. It may then be possible for the optimizer to push the resulting simple predicates down into the inlined report query to make use of indexes on the searched column.
    I have created a copy of your search page on page 33 of your app and created an After Regions page process that will create Debug entries containing the complete IR query and bind variables used so they can be extracted for easier performance analysis and tuning outside of APEX. You can copy this to your local app and modify the page and region ID parameters as required.

  • Network manager takes lot of time during boot

    HOw to reduce my networkmanager boot time
    Below is my systemd-analyze time
    [root@gauranga simha]# systemd-analyze time
    Startup finished in 5449ms (kernel) + 82854ms (userspace) = 88303ms
    Below is my systemd-analyze blame
    [root@gauranga simha]# systemd-analyze blame
    39261ms NetworkManager.service
    13083ms mysqld.service
    3764ms sys-kernel-debug.mount
    3733ms dev-mqueue.mount
    3720ms dev-hugepages.mount
    3566ms systemd-remount-fs.service
    3423ms systemd-binfmt.service
    3342ms systemd-vconsole-setup.service
    3038ms proc-sys-fs-binfmt_misc.mount
    2349ms media-GAUR.mount
    1954ms polkit.service
    1938ms colord.service
    1226ms systemd-udevd.service
    970ms bluetooth.service
    934ms systemd-logind.service
    881ms systemd-udev-trigger.service
    460ms systemd-sysctl.service
    439ms systemd-modules-load.service
    426ms dev-sda6.swap
    410ms systemd-tmpfiles-setup.service
    256ms httpd.service
    229ms systemd-readahead-replay.service
    80ms systemd-readahead-collect.service
    54ms udisks2.service
    53ms console-kit-log-system-start.service
    52ms wpa_supplicant.service
    49ms console-kit-daemon.service
    19ms systemd-user-sessions.service
    19ms tmp.mount
    14ms rtkit-daemon.service
    8ms modem-manager.service
    5ms upower.service
    1ms sys-fs-fuse-connections.mount
    Output for journalctl -b
    [root@gauranga simha]# journalctl -b
    -- Logs begin at Mon 2013-03-11 15:14:32 IST, end at Fri 2013-03-22 18:34:03 IST. --
    Mar 22 18:32:32 gauranga systemd-journal[114]: Allowing runtime journal files to grow to 145.1M.
    Mar 22 18:32:32 gauranga kernel: Initializing cgroup subsys cpuset
    Mar 22 18:32:32 gauranga kernel: Initializing cgroup subsys cpu
    Mar 22 18:32:32 gauranga kernel: Linux version 3.5.4-1-ARCH (tobias@T-POWA-LX) (gcc version 4.7.1 20120721 (prerelease) (GCC) ) #1 SMP PREEMPT Sat Sep 15 13:
    Mar 22 18:32:32 gauranga kernel: Disabled fast string operations
    Mar 22 18:32:32 gauranga kernel: e820: BIOS-provided physical RAM map:
    Mar 22 18:32:32 gauranga kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
    Mar 22 18:32:32 gauranga kernel: BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
    Mar 22 18:32:32 gauranga kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
    Mar 22 18:32:32 gauranga kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000b64e0fff] usable
    Mar 22 18:32:32 gauranga kernel: BIOS-e820: [mem 0x00000000b64e1000-0x00000000b64e3fff] ACPI NVS
    Mar 22 18:32:32 gauranga kernel: BIOS-e820: [mem 0x00000000b64e4000-0x00000000b7a6afff] usable
    Mar 22 18:32:32 gauranga kernel: BIOS-e820: [mem 0x00000000b7a6b000-0x00000000b7abefff] reserved
    Mar 22 18:32:32 gauranga kernel: BIOS-e820: [mem 0x00000000b7abf000-0x00000000b7b84fff] usable
    Mar 22 18:32:32 gauranga kernel: BIOS-e820: [mem 0x00000000b7b85000-0x00000000b7bbefff] ACPI NVS
    Mar 22 18:32:32 gauranga kernel: BIOS-e820: [mem 0x00000000b7bbf000-0x00000000b7be3fff] usable
    Mar 22 18:32:32 gauranga kernel: BIOS-e820: [mem 0x00000000b7be4000-0x00000000b7bf6fff] ACPI data
    Mar 22 18:32:32 gauranga kernel: BIOS-e820: [mem 0x00000000b7bf7000-0x00000000b7bfffff] usable
    Mar 22 18:32:32 gauranga kernel: BIOS-e820: [mem 0x00000000b7c00000-0x00000000bfffffff] reserved
    Mar 22 18:32:32 gauranga kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
    Mar 22 18:32:32 gauranga kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
    Mar 22 18:32:32 gauranga kernel: BIOS-e820: [mem 0x00000000fed10000-0x00000000fed13fff] reserved
    Mar 22 18:32:32 gauranga kernel: BIOS-e820: [mem 0x00000000fed18000-0x00000000fed19fff] reserved
    Mar 22 18:32:32 gauranga kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
    Mar 22 18:32:32 gauranga kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
    Mar 22 18:32:32 gauranga kernel: BIOS-e820: [mem 0x00000000fff00000-0x00000000ffffffff] reserved
    Mar 22 18:32:32 gauranga kernel: BIOS-e820: [mem 0x0000000100000000-0x000000013fffffff] usable
    Mar 22 18:32:32 gauranga kernel: Notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel!
    Mar 22 18:32:32 gauranga kernel: DMI 2.4 present.
    Mar 22 18:32:32 gauranga kernel: DMI: Sony Corporation VGN-CS230J/VAIO, BIOS R1100Q2 09/01/2009
    Mar 22 18:32:32 gauranga kernel: e820: update [mem 0x00000000-0x0000ffff] usable ==> reserved
    Mar 22 18:32:32 gauranga kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
    Mar 22 18:32:32 gauranga kernel: e820: last_pfn = 0xb7c00 max_arch_pfn = 0x100000
    Mar 22 18:32:32 gauranga kernel: MTRR default type: uncachable
    Mar 22 18:32:32 gauranga kernel: MTRR fixed ranges enabled:
    Mar 22 18:32:32 gauranga kernel: 00000-9FFFF write-back
    Mar 22 18:32:32 gauranga kernel: A0000-BFFFF uncachable
    Mar 22 18:32:32 gauranga kernel: C0000-C7FFF write-through
    Mar 22 18:32:32 gauranga kernel: C8000-FFFFF uncachable
    Mar 22 18:32:32 gauranga kernel: MTRR variable ranges enabled:
    Mar 22 18:32:32 gauranga kernel: 0 base 0FFF00000 mask FFFF00000 write-protect
    Mar 22 18:32:32 gauranga kernel: 1 base 000000000 mask F80000000 write-back
    Mar 22 18:32:32 gauranga kernel: 2 base 080000000 mask FC0000000 write-back
    Mar 22 18:32:32 gauranga kernel: 3 base 0B8000000 mask FF8000000 uncachable
    Mar 22 18:32:32 gauranga kernel: 4 disabled
    Mar 22 18:32:32 gauranga kernel: 5 base 100000000 mask FC0000000 write-back
    Mar 22 18:32:32 gauranga kernel: 6 disabled
    Mar 22 18:32:32 gauranga kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    Mar 22 18:32:32 gauranga kernel: initial memory mapped: [mem 0x00000000-0x01bfffff]
    Mar 22 18:32:32 gauranga kernel: Base memory trampoline at [c009b000] 9b000 size 16384
    Mar 22 18:32:32 gauranga kernel: init_memory_mapping: [mem 0x00000000-0x377fdfff]
    Mar 22 18:32:32 gauranga kernel: [mem 0x00000000-0x003fffff] page 4k
    Mar 22 18:32:32 gauranga kernel: [mem 0x00400000-0x373fffff] page 2M
    Mar 22 18:32:32 gauranga kernel: [mem 0x37400000-0x377fdfff] page 4k
    Mar 22 18:32:32 gauranga kernel: kernel direct mapping tables up to 0x377fdfff @ [mem 0x01bfa000-0x01bfffff]
    Mar 22 18:32:32 gauranga kernel: RAMDISK: [mem 0x37966000-0x37caafff]
    Mar 22 18:32:32 gauranga kernel: Allocated new RAMDISK: [mem 0x374b9000-0x377fd447]
    Mar 22 18:32:32 gauranga kernel: Move RAMDISK from [mem 0x37966000-0x37caa447] to [mem 0x374b9000-0x377fd447]
    Mar 22 18:32:32 gauranga kernel: ACPI: RSDP 000fe020 00024 (v02 Sony)
    Mar 22 18:32:32 gauranga kernel: ACPI: XSDT b7bf6120 0006C (v01 Sony VAIO 20090901 INTL 20061109)
    Mar 22 18:32:32 gauranga kernel: ACPI: FACP b7bf5000 000F4 (v04 Sony VAIO 20090901 INTL 20061109)
    Mar 22 18:32:32 gauranga kernel: ACPI: DSDT b7bea000 0674D (v01 Sony VAIO 20090901 INTL 20061109)
    Mar 22 18:32:32 gauranga kernel: ACPI: FACS b7b92000 00040
    Mar 22 18:32:32 gauranga kernel: ACPI: HPET b7bf4000 00038 (v01 Sony VAIO 20090901 INTL 20061109)
    Mar 22 18:32:32 gauranga kernel: ACPI: APIC b7bf3000 0006C (v02 Sony VAIO 20090901 INTL 20061109)
    Mar 22 18:32:32 gauranga kernel: ACPI: MCFG b7bf2000 0003C (v01 Sony VAIO 20090901 INTL 20061109)
    Mar 22 18:32:32 gauranga kernel: ACPI: ASF! b7bf1000 000A5 (v32 Sony VAIO 20090901 INTL 20061109)
    Mar 22 18:32:32 gauranga kernel: ACPI: SLIC b7be9000 00176 (v01 Sony VAIO 20090901 INTL 20061109)
    Mar 22 18:32:32 gauranga kernel: ACPI: BOOT b7be8000 00028 (v01 Sony VAIO 20090901 INTL 20061109)
    Mar 22 18:32:32 gauranga kernel: ACPI: SSDT b7be7000 000D9 (v01 Sony VAIO 20090901 INTL 20061109)
    Mar 22 18:32:32 gauranga kernel: ACPI: SSDT b7be4000 00655 (v01 Sony VAIO 20090901 INTL 20061109)
    Mar 22 18:32:32 gauranga kernel: ACPI: Local APIC address 0xfee00000
    Mar 22 18:32:32 gauranga kernel: 2052MB HIGHMEM available.
    Mar 22 18:32:32 gauranga kernel: 887MB LOWMEM available.
    Mar 22 18:32:32 gauranga kernel: mapped low ram: 0 - 377fe000
    Mar 22 18:32:32 gauranga kernel: low ram: 0 - 377fe000
    Mar 22 18:32:32 gauranga kernel: Zone ranges:
    Mar 22 18:32:32 gauranga kernel: DMA [mem 0x00010000-0x00ffffff]
    Mar 22 18:32:32 gauranga kernel: Normal [mem 0x01000000-0x377fdfff]
    Mar 22 18:32:32 gauranga kernel: HighMem [mem 0x377fe000-0xb7bfffff]
    Mar 22 18:32:32 gauranga kernel: Movable zone start for each node
    Mar 22 18:32:32 gauranga kernel: Early memory node ranges
    Mar 22 18:32:32 gauranga kernel: node 0: [mem 0x00010000-0x0009efff]
    Mar 22 18:32:32 gauranga kernel: node 0: [mem 0x00100000-0xb64e0fff]
    Mar 22 18:32:32 gauranga kernel: node 0: [mem 0xb64e4000-0xb7a6afff]
    Mar 22 18:32:32 gauranga kernel: node 0: [mem 0xb7abf000-0xb7b84fff]
    Mar 22 18:32:32 gauranga kernel: node 0: [mem 0xb7bbf000-0xb7be3fff]
    Mar 22 18:32:32 gauranga kernel: node 0: [mem 0xb7bf7000-0xb7bfffff]
    Mar 22 18:32:32 gauranga kernel: On node 0 totalpages: 752363
    Mar 22 18:32:32 gauranga kernel: free_area_init_node: node 0, pgdat c1539c40, node_mem_map f5dc0200
    Mar 22 18:32:32 gauranga kernel: DMA zone: 32 pages used for memmap
    Mar 22 18:32:32 gauranga kernel: DMA zone: 0 pages reserved
    Mar 22 18:32:32 gauranga kernel: DMA zone: 3951 pages, LIFO batch:0
    Mar 22 18:32:32 gauranga kernel: Normal zone: 1744 pages used for memmap
    Mar 22 18:32:32 gauranga kernel: Normal zone: 221486 pages, LIFO batch:31
    Mar 22 18:32:32 gauranga kernel: HighMem zone: 4105 pages used for memmap
    Mar 22 18:32:32 gauranga kernel: HighMem zone: 521045 pages, LIFO batch:31
    Mar 22 18:32:32 gauranga kernel: Using APIC driver default
    Mar 22 18:32:32 gauranga kernel: ACPI: PM-Timer IO Port: 0x408
    Mar 22 18:32:32 gauranga kernel: ACPI: Local APIC address 0xfee00000
    Mar 22 18:32:32 gauranga kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
    Mar 22 18:32:32 gauranga kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
    Mar 22 18:32:32 gauranga kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x00] disabled)
    Mar 22 18:32:32 gauranga kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x00] disabled)
    Mar 22 18:32:32 gauranga kernel: ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
    Mar 22 18:32:32 gauranga kernel: IOAPIC[0]: apic_id 4, version 32, address 0xfec00000, GSI 0-23
    Mar 22 18:32:32 gauranga kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    Mar 22 18:32:32 gauranga kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    Mar 22 18:32:32 gauranga kernel: ACPI: IRQ0 used by override.
    Mar 22 18:32:32 gauranga kernel: ACPI: IRQ2 used by override.
    Mar 22 18:32:32 gauranga kernel: ACPI: IRQ9 used by override.
    Mar 22 18:32:32 gauranga kernel: Using ACPI (MADT) for SMP configuration information
    Mar 22 18:32:32 gauranga kernel: ACPI: HPET id: 0x8086a201 base: 0xfed00000
    Mar 22 18:32:32 gauranga kernel: SMP: Allowing 4 CPUs, 2 hotplug CPUs
    Mar 22 18:32:32 gauranga kernel: nr_irqs_gsi: 40
    Mar 22 18:32:32 gauranga kernel: PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
    Mar 22 18:32:32 gauranga kernel: PM: Registered nosave memory: 00000000000a0000 - 00000000000e0000
    Mar 22 18:32:32 gauranga kernel: PM: Registered nosave memory: 00000000000e0000 - 0000000000100000
    Mar 22 18:32:32 gauranga kernel: e820: [mem 0xc0000000-0xf7ffffff] available for PCI devices
    Mar 22 18:32:32 gauranga kernel: Booting paravirtualized kernel on bare hardware
    Mar 22 18:32:32 gauranga kernel: setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:4 nr_node_ids:1
    Mar 22 18:32:32 gauranga kernel: PERCPU: Embedded 13 pages/cpu @f5d7a000 s31616 r0 d21632 u53248
    Mar 22 18:32:32 gauranga kernel: pcpu-alloc: s31616 r0 d21632 u53248 alloc=13*4096
    Mar 22 18:32:32 gauranga kernel: pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
    Mar 22 18:32:32 gauranga kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 746482
    Mar 22 18:32:32 gauranga kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=de9c1526-30ec-4261-a7fe-c21f74aefba0 ro resume=/dev/sda6 quiet
    Mar 22 18:32:32 gauranga kernel: PID hash table entries: 4096 (order: 2, 16384 bytes)
    Mar 22 18:32:32 gauranga kernel: Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
    Mar 22 18:32:32 gauranga kernel: Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
    Mar 22 18:32:32 gauranga kernel: __ex_table already sorted, skipping sort
    Mar 22 18:32:32 gauranga kernel: Initializing CPU#0
    Mar 22 18:32:32 gauranga kernel: xsave/xrstor: enabled xstate_bv 0x3, cntxt size 0x240
    Mar 22 18:32:32 gauranga kernel: allocated 6020992 bytes of page_cgroup
    Mar 22 18:32:32 gauranga kernel: please try 'cgroup_disable=memory' option if you don't want memory cgroups
    Mar 22 18:32:32 gauranga kernel: Initializing HighMem for node 0 (000377fe:000b7c00)
    Mar 22 18:32:32 gauranga kernel: Memory: 2968736k/3010560k available (3896k kernel code, 40716k reserved, 1491k data, 532k init, 2100600k highmem)
    Mar 22 18:32:32 gauranga kernel: [379B blob data]
    Mar 22 18:32:32 gauranga kernel: Checking if this processor honours the WP bit even in supervisor mode...Ok.
    Mar 22 18:32:32 gauranga kernel: SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
    Mar 22 18:32:32 gauranga kernel: Preemptible hierarchical RCU implementation.
    Mar 22 18:32:32 gauranga kernel: RCU dyntick-idle grace-period acceleration is enabled.
    Mar 22 18:32:32 gauranga kernel: Dump stacks of tasks blocking RCU-preempt GP.
    Mar 22 18:32:32 gauranga kernel: NR_IRQS:2304 nr_irqs:712 16
    Mar 22 18:32:32 gauranga kernel: CPU 0 irqstacks, hard=f500a000 soft=f500c000
    Mar 22 18:32:32 gauranga kernel: Extended CMOS year: 2000
    Mar 22 18:32:32 gauranga kernel: Console: colour dummy device 80x25
    Mar 22 18:32:32 gauranga kernel: console [tty0] enabled
    Mar 22 18:32:32 gauranga kernel: hpet clockevent registered
    Mar 22 18:32:32 gauranga kernel: Fast TSC calibration using PIT
    Mar 22 18:32:32 gauranga kernel: Detected 2394.003 MHz processor.
    Mar 22 18:32:32 gauranga kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 4789.50 BogoMIPS (lpj=7980010)
    Mar 22 18:32:32 gauranga kernel: pid_max: default: 32768 minimum: 301
    Mar 22 18:32:32 gauranga kernel: Security Framework initialized
    Mar 22 18:32:32 gauranga kernel: AppArmor: AppArmor disabled by boot time parameter
    Mar 22 18:32:32 gauranga kernel: Mount-cache hash table entries: 512
    Mar 22 18:32:32 gauranga kernel: Initializing cgroup subsys cpuacct
    Mar 22 18:32:32 gauranga kernel: Initializing cgroup subsys memory
    Mar 22 18:32:32 gauranga kernel: Initializing cgroup subsys devices
    Mar 22 18:32:32 gauranga kernel: Initializing cgroup subsys freezer
    Mar 22 18:32:32 gauranga kernel: Initializing cgroup subsys net_cls
    Mar 22 18:32:32 gauranga kernel: Initializing cgroup subsys blkio
    Mar 22 18:32:32 gauranga kernel: Disabled fast string operations
    Mar 22 18:32:32 gauranga kernel: CPU: Physical Processor ID: 0
    Mar 22 18:32:32 gauranga kernel: CPU: Processor Core ID: 0
    Mar 22 18:32:32 gauranga kernel: mce: CPU supports 6 MCE banks
    Mar 22 18:32:32 gauranga kernel: CPU0: Thermal monitoring handled by SMI
    Mar 22 18:32:32 gauranga kernel: using mwait in idle threads.
    Mar 22 18:32:32 gauranga kernel: ACPI: Core revision 20120320
    Mar 22 18:32:32 gauranga kernel: ftrace: allocating 17053 entries in 34 pages
    Mar 22 18:32:32 gauranga kernel: Enabling APIC mode: Flat. Using 1 I/O APICs
    Mar 22 18:32:32 gauranga kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    Mar 22 18:32:32 gauranga kernel: CPU0: Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz stepping 0a
    Mar 22 18:32:32 gauranga kernel: Performance Events: PEBS fmt0+, 4-deep LBR, Core2 events, Intel PMU driver.
    Mar 22 18:32:32 gauranga kernel: ... version: 2
    Mar 22 18:32:32 gauranga kernel: ... bit width: 40
    Mar 22 18:32:32 gauranga kernel: ... generic registers: 2
    Mar 22 18:32:32 gauranga kernel: ... value mask: 000000ffffffffff
    Mar 22 18:32:32 gauranga kernel: ... max period: 000000007fffffff
    Mar 22 18:32:32 gauranga kernel: ... fixed-purpose events: 3
    Mar 22 18:32:32 gauranga kernel: ... event mask: 0000000700000003
    Mar 22 18:32:32 gauranga kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
    Mar 22 18:32:32 gauranga kernel: CPU 1 irqstacks, hard=f50f8000 soft=f50fa000
    Mar 22 18:32:32 gauranga kernel: Initializing CPU#1
    Mar 22 18:32:32 gauranga kernel: Disabled fast string operations
    Mar 22 18:32:32 gauranga kernel: CPU1: Thermal monitoring handled by SMI
    Mar 22 18:32:32 gauranga kernel: Booting Node 0, Processors #1
    Mar 22 18:32:32 gauranga kernel: Brought up 2 CPUs
    Mar 22 18:32:32 gauranga kernel: Total of 2 processors activated (9579.01 BogoMIPS).
    Mar 22 18:32:32 gauranga kernel: devtmpfs: initialized
    Mar 22 18:32:32 gauranga kernel: PM: Registering ACPI NVS region [mem 0xb64e1000-0xb64e3fff] (12288 bytes)
    Mar 22 18:32:32 gauranga kernel: PM: Registering ACPI NVS region [mem 0xb7b85000-0xb7bbefff] (237568 bytes)
    Mar 22 18:32:32 gauranga kernel: NET: Registered protocol family 16
    Mar 22 18:32:32 gauranga kernel: ACPI: bus type pci registered
    Mar 22 18:32:32 gauranga kernel: PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
    Mar 22 18:32:32 gauranga kernel: PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
    Mar 22 18:32:32 gauranga kernel: PCI: Using MMCONFIG for extended config space
    Mar 22 18:32:32 gauranga kernel: PCI: Using configuration type 1 for base access
    Mar 22 18:32:32 gauranga kernel: mtrr: your CPUs had inconsistent variable MTRR settings
    Mar 22 18:32:32 gauranga kernel: mtrr: probably your BIOS does not setup all CPUs.
    Mar 22 18:32:32 gauranga kernel: mtrr: corrected configuration.
    Mar 22 18:32:32 gauranga kernel: bio: create slab <bio-0> at 0
    Mar 22 18:32:32 gauranga kernel: ACPI: Added _OSI(Module Device)
    Mar 22 18:32:32 gauranga kernel: ACPI: Added _OSI(Processor Device)
    Mar 22 18:32:32 gauranga kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
    Mar 22 18:32:32 gauranga kernel: ACPI: Added _OSI(Processor Aggregator Device)
    Mar 22 18:32:32 gauranga kernel: ACPI: EC: Look up EC in DSDT
    Mar 22 18:32:32 gauranga kernel: ACPI: Executed 1 blocks of module-level executable AML code
    Mar 22 18:32:32 gauranga kernel: [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
    Mar 22 18:32:32 gauranga kernel: ACPI: SSDT b7a76c18 00265 (v01 Sony VAIO 20090901 INTL 20061109)
    Mar 22 18:32:32 gauranga kernel: ACPI: Dynamic OEM Table Load:
    Mar 22 18:32:32 gauranga kernel: ACPI: SSDT (null) 00265 (v01 Sony VAIO 20090901 INTL 20061109)
    Mar 22 18:32:32 gauranga kernel: ACPI: SSDT b7a74618 005B3 (v01 Sony VAIO 20090901 INTL 20061109)
    Mar 22 18:32:32 gauranga kernel: ACPI: Dynamic OEM Table Load:
    Mar 22 18:32:32 gauranga kernel: ACPI: SSDT (null) 005B3 (v01 Sony VAIO 20090901 INTL 20061109)
    Mar 22 18:32:32 gauranga kernel: ACPI: SSDT b7a75e18 001CF (v01 Sony VAIO 20090901 INTL 20061109)
    Mar 22 18:32:32 gauranga kernel: ACPI: Dynamic OEM Table Load:
    Mar 22 18:32:32 gauranga kernel: ACPI: SSDT (null) 001CF (v01 Sony VAIO 20090901 INTL 20061109)
    Mar 22 18:32:32 gauranga kernel: ACPI: SSDT b7a76f18 0008D (v01 Sony VAIO 20090901 INTL 20061109)
    Mar 22 18:32:32 gauranga kernel: ACPI: Dynamic OEM Table Load:
    Mar 22 18:32:32 gauranga kernel: ACPI: SSDT (null) 0008D (v01 Sony VAIO 20090901 INTL 20061109)
    Mar 22 18:32:32 gauranga kernel: ACPI: Interpreter enabled
    Mar 22 18:32:32 gauranga kernel: ACPI: (supports S0 S3 S4 S5)
    Mar 22 18:32:32 gauranga kernel: ACPI: Using IOAPIC for interrupt routing
    Mar 22 18:32:32 gauranga kernel: ACPI: EC: GPE = 0x17, I/O: command/status = 0x66, data = 0x62
    Mar 22 18:32:32 gauranga kernel: ACPI: No dock devices found.
    Mar 22 18:32:32 gauranga kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
    Mar 22 18:32:32 gauranga kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
    Mar 22 18:32:32 gauranga kernel: pci_root PNP0A08:00: host bridge window [io 0x0000-0x0cf7]
    Mar 22 18:32:32 gauranga kernel: pci_root PNP0A08:00: host bridge window [io 0x0d00-0xffff]
    Mar 22 18:32:32 gauranga kernel: pci_root PNP0A08:00: host bridge window [mem 0x000a0000-0x000bffff]
    Mar 22 18:32:32 gauranga kernel: pci_root PNP0A08:00: host bridge window [mem 0xc0000000-0xfebfffff]
    Mar 22 18:32:32 gauranga kernel: PCI host bridge to bus 0000:00
    Mar 22 18:32:32 gauranga kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
    Mar 22 18:32:32 gauranga kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
    Mar 22 18:32:32 gauranga kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
    Mar 22 18:32:32 gauranga kernel: pci_bus 0000:00: root bus resource [mem 0xc0000000-0xfebfffff]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:00.0: [8086:2a40] type 00 class 0x060000
    Mar 22 18:32:32 gauranga kernel: DMAR: Forcing write-buffer flush capability
    Mar 22 18:32:32 gauranga kernel: DMAR: Disabling IOMMU for graphics on this chipset
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:02.0: [8086:2a42] type 00 class 0x030000
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:02.0: reg 10: [mem 0xd0000000-0xd03fffff 64bit]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:02.0: reg 18: [mem 0xc0000000-0xcfffffff 64bit pref]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:02.0: reg 20: [io 0x60f0-0x60f7]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:02.1: [8086:2a43] type 00 class 0x038000
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:02.1: reg 10: [mem 0xd3400000-0xd34fffff 64bit]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1a.0: [8086:2937] type 00 class 0x0c0300
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1a.0: reg 20: [io 0x60c0-0x60df]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1a.1: [8086:2938] type 00 class 0x0c0300
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1a.1: reg 20: [io 0x60a0-0x60bf]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1a.7: [8086:293c] type 00 class 0x0c0320
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1a.7: reg 10: [mem 0xd6804c00-0xd6804fff]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1b.0: [8086:293e] type 00 class 0x040300
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1b.0: reg 10: [mem 0xd6800000-0xd6803fff 64bit]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1c.0: [8086:2940] type 01 class 0x060400
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1c.2: [8086:2944] type 01 class 0x060400
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1c.4: [8086:2948] type 01 class 0x060400
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1d.0: [8086:2934] type 00 class 0x0c0300
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1d.0: reg 20: [io 0x6080-0x609f]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1d.1: [8086:2935] type 00 class 0x0c0300
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1d.1: reg 20: [io 0x6060-0x607f]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1d.2: [8086:2936] type 00 class 0x0c0300
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1d.2: reg 20: [io 0x6040-0x605f]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1d.7: [8086:293a] type 00 class 0x0c0320
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1d.7: reg 10: [mem 0xd6804800-0xd6804bff]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1e.0: [8086:2448] type 01 class 0x060401
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1f.0: [8086:2919] type 00 class 0x060100
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1f.2: [8086:2929] type 00 class 0x010601
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1f.2: reg 10: [io 0x60e8-0x60ef]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1f.2: reg 14: [io 0x60fc-0x60ff]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1f.2: reg 18: [io 0x60e0-0x60e7]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1f.2: reg 1c: [io 0x60f8-0x60fb]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1f.2: reg 20: [io 0x6020-0x603f]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1f.2: reg 24: [mem 0xd6804000-0xd68047ff]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1f.2: PME# supported from D3hot
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1f.3: [8086:2930] type 00 class 0x0c0500
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1f.3: reg 10: [mem 0xd6805000-0xd68050ff 64bit]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1f.3: reg 20: [io 0x6000-0x601f]
    Mar 22 18:32:32 gauranga kernel: pci 0000:02:00.0: [11ab:4354] type 00 class 0x020000
    Mar 22 18:32:32 gauranga kernel: pci 0000:02:00.0: reg 10: [mem 0xd5700000-0xd5703fff 64bit]
    Mar 22 18:32:32 gauranga kernel: pci 0000:02:00.0: reg 18: [io 0x4000-0x40ff]
    Mar 22 18:32:32 gauranga kernel: pci 0000:02:00.0: supports D1 D2
    Mar 22 18:32:32 gauranga kernel: pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1c.0: PCI bridge to [bus 02-02]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1c.0: bridge window [io 0x4000-0x5fff]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1c.0: bridge window [mem 0xd5700000-0xd67fffff]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1c.0: bridge window [mem 0xd0400000-0xd13fffff 64bit pref]
    Mar 22 18:32:32 gauranga kernel: pci 0000:03:00.0: [8086:4232] type 00 class 0x028000
    Mar 22 18:32:32 gauranga kernel: pci 0000:03:00.0: reg 10: [mem 0xd4600000-0xd4601fff 64bit]
    Mar 22 18:32:32 gauranga kernel: pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1c.2: PCI bridge to [bus 03-03]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1c.2: bridge window [io 0x3000-0x3fff]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1c.2: bridge window [mem 0xd4600000-0xd56fffff]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1c.2: bridge window [mem 0xd1400000-0xd23fffff 64bit pref]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1c.4: PCI bridge to [bus 04-05]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1c.4: bridge window [io 0x2000-0x2fff]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1c.4: bridge window [mem 0xd3600000-0xd45fffff]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1c.4: bridge window [mem 0xd2400000-0xd33fffff 64bit pref]
    Mar 22 18:32:32 gauranga kernel: pci 0000:06:02.0: [1180:0832] type 00 class 0x0c0010
    Mar 22 18:32:32 gauranga kernel: pci 0000:06:02.0: reg 10: [mem 0xd3500000-0xd35007ff]
    Mar 22 18:32:32 gauranga kernel: pci 0000:06:02.0: PME# supported from D0 D3hot D3cold
    Mar 22 18:32:32 gauranga kernel: pci 0000:06:02.1: [1180:0822] type 00 class 0x080500
    Mar 22 18:32:32 gauranga kernel: pci 0000:06:02.1: reg 10: [mem 0xd3500900-0xd35009ff]
    Mar 22 18:32:32 gauranga kernel: pci 0000:06:02.1: supports D1 D2
    Mar 22 18:32:32 gauranga kernel: pci 0000:06:02.1: PME# supported from D0 D1 D2 D3hot D3cold
    Mar 22 18:32:32 gauranga kernel: pci 0000:06:02.2: [1180:0592] type 00 class 0x088000
    Mar 22 18:32:32 gauranga kernel: pci 0000:06:02.2: reg 10: [mem 0xd3500800-0xd35008ff]
    Mar 22 18:32:32 gauranga kernel: pci 0000:06:02.2: supports D1 D2
    Mar 22 18:32:32 gauranga kernel: pci 0000:06:02.2: PME# supported from D0 D1 D2 D3hot D3cold
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1e.0: PCI bridge to [bus 06-06] (subtractive decode)
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1e.0: bridge window [mem 0xd3500000-0xd35fffff]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1e.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1e.0: bridge window [io 0x0d00-0xffff] (subtractive decode)
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1e.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1e.0: bridge window [mem 0xc0000000-0xfebfffff] (subtractive decode)
    Mar 22 18:32:32 gauranga kernel: pci_bus 0000:00: on NUMA node 0
    Mar 22 18:32:32 gauranga kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    Mar 22 18:32:32 gauranga kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P32_._PRT]
    Mar 22 18:32:32 gauranga kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP1._PRT]
    Mar 22 18:32:32 gauranga kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP3._PRT]
    Mar 22 18:32:32 gauranga kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP5._PRT]
    Mar 22 18:32:32 gauranga kernel: pci0000:00: Requesting ACPI _OSC control (0x1d)
    Mar 22 18:32:32 gauranga kernel: pci0000:00: ACPI _OSC request failed (AE_NOT_FOUND), returned control mask: 0x1d
    Mar 22 18:32:32 gauranga kernel: ACPI _OSC control for PCIe not granted, disabling ASPM
    Mar 22 18:32:32 gauranga kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 9 10 *11 12)
    Mar 22 18:32:32 gauranga kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 9 10 11 12) *0, disabled.
    Mar 22 18:32:32 gauranga kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 9 10 *11 12)
    Mar 22 18:32:32 gauranga kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 9 10 *11 12)
    Mar 22 18:32:32 gauranga kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 9 10 11 12) *0, disabled.
    Mar 22 18:32:32 gauranga kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 9 *10 11 12)
    Mar 22 18:32:32 gauranga kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 7 9 10 *11 12)
    Mar 22 18:32:32 gauranga kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 7 9 10 *11 12)
    Mar 22 18:32:32 gauranga kernel: vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
    Mar 22 18:32:32 gauranga kernel: vgaarb: loaded
    Mar 22 18:32:32 gauranga kernel: vgaarb: bridge control possible 0000:00:02.0
    Mar 22 18:32:32 gauranga kernel: PCI: Using ACPI for IRQ routing
    Mar 22 18:32:32 gauranga kernel: PCI: pci_cache_line_size set to 64 bytes
    Mar 22 18:32:32 gauranga kernel: e820: reserve RAM buffer [mem 0x0009fc00-0x0009ffff]
    Mar 22 18:32:32 gauranga kernel: e820: reserve RAM buffer [mem 0xb64e1000-0xb7ffffff]
    Mar 22 18:32:32 gauranga kernel: e820: reserve RAM buffer [mem 0xb7a6b000-0xb7ffffff]
    Mar 22 18:32:32 gauranga kernel: e820: reserve RAM buffer [mem 0xb7b85000-0xb7ffffff]
    Mar 22 18:32:32 gauranga kernel: e820: reserve RAM buffer [mem 0xb7be4000-0xb7ffffff]
    Mar 22 18:32:32 gauranga kernel: e820: reserve RAM buffer [mem 0xb7c00000-0xb7ffffff]
    Mar 22 18:32:32 gauranga kernel: NetLabel: Initializing
    Mar 22 18:32:32 gauranga kernel: NetLabel: domain hash size = 128
    Mar 22 18:32:32 gauranga kernel: NetLabel: protocols = UNLABELED CIPSOv4
    Mar 22 18:32:32 gauranga kernel: NetLabel: unlabeled traffic allowed by default
    Mar 22 18:32:32 gauranga kernel: HPET: 4 timers in total, 0 timers will be used for per-cpu timer
    Mar 22 18:32:32 gauranga kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0
    Mar 22 18:32:32 gauranga kernel: hpet0: 4 comparators, 64-bit 14.318180 MHz counter
    Mar 22 18:32:32 gauranga kernel: Switching to clocksource hpet
    Mar 22 18:32:32 gauranga kernel: pnp: PnP ACPI init
    Mar 22 18:32:32 gauranga kernel: ACPI: bus type pnp registered
    Mar 22 18:32:32 gauranga kernel: pnp 00:00: [bus 00-ff]
    Mar 22 18:32:32 gauranga kernel: pnp 00:00: [io 0x0000-0x0cf7 window]
    Mar 22 18:32:32 gauranga kernel: pnp 00:00: [io 0x0cf8-0x0cff]
    Mar 22 18:32:32 gauranga kernel: pnp 00:00: [io 0x0d00-0xffff window]
    Mar 22 18:32:32 gauranga kernel: pnp 00:00: [mem 0x000a0000-0x000bffff window]
    Mar 22 18:32:32 gauranga kernel: pnp 00:00: [mem 0x000c0000-0x000c3fff window]
    Mar 22 18:32:32 gauranga kernel: pnp 00:00: [mem 0x000c4000-0x000c7fff window]
    Mar 22 18:32:32 gauranga kernel: pnp 00:00: [mem 0x000c8000-0x000cbfff window]
    Mar 22 18:32:32 gauranga kernel: pnp 00:00: [mem 0x000cc000-0x000cffff window]
    Mar 22 18:32:32 gauranga kernel: pnp 00:00: [mem 0x000d0000-0x000d3fff window]
    Mar 22 18:32:32 gauranga kernel: pnp 00:00: [mem 0x000d4000-0x000d7fff window]
    Mar 22 18:32:32 gauranga kernel: pnp 00:00: [mem 0x000d8000-0x000dbfff window]
    Mar 22 18:32:32 gauranga kernel: pnp 00:00: [mem 0x000dc000-0x000dffff window]
    Mar 22 18:32:32 gauranga kernel: pnp 00:00: [mem 0x000e0000-0x000e3fff window]
    Mar 22 18:32:32 gauranga kernel: pnp 00:00: [mem 0x000e4000-0x000e7fff window]
    Mar 22 18:32:32 gauranga kernel: pnp 00:00: [mem 0x000e8000-0x000ebfff window]
    Mar 22 18:32:32 gauranga kernel: pnp 00:00: [mem 0x000ec000-0x000effff window]
    Mar 22 18:32:32 gauranga kernel: pnp 00:00: [mem 0x000f0000-0x000fffff window]
    Mar 22 18:32:32 gauranga kernel: pnp 00:00: [mem 0xc0000000-0xfebfffff window]
    Mar 22 18:32:32 gauranga kernel: pnp 00:00: [mem 0xfed40000-0xfed44fff window]
    Mar 22 18:32:32 gauranga kernel: pnp 00:00: Plug and Play ACPI device, IDs PNP0a08 PNP0a03 (active)
    Mar 22 18:32:32 gauranga kernel: pnp 00:01: [io 0x002e-0x002f]
    Mar 22 18:32:32 gauranga kernel: pnp 00:01: [io 0x004e-0x004f]
    Mar 22 18:32:32 gauranga kernel: pnp 00:01: [io 0x164e-0x164f]
    Mar 22 18:32:32 gauranga kernel: pnp 00:01: [io 0x0061]
    Mar 22 18:32:32 gauranga kernel: pnp 00:01: [io 0x0070]
    Mar 22 18:32:32 gauranga kernel: pnp 00:01: [io 0x0080]
    Mar 22 18:32:32 gauranga kernel: pnp 00:01: [io 0x0092]
    Mar 22 18:32:32 gauranga kernel: pnp 00:01: [io 0x00b2-0x00b3]
    Mar 22 18:32:32 gauranga kernel: pnp 00:01: [io 0x0063]
    Mar 22 18:32:32 gauranga kernel: pnp 00:01: [io 0x0065]
    Mar 22 18:32:32 gauranga kernel: pnp 00:01: [io 0x0067]
    Mar 22 18:32:32 gauranga kernel: pnp 00:01: [io 0x0200-0x020f]
    Mar 22 18:32:32 gauranga kernel: pnp 00:01: [io 0x0600-0x060f]
    Mar 22 18:32:32 gauranga kernel: pnp 00:01: [io 0x0610]
    Mar 22 18:32:32 gauranga kernel: pnp 00:01: [io 0x0800-0x080f]
    Mar 22 18:32:32 gauranga kernel: pnp 00:01: [io 0x0810-0x0817]
    Mar 22 18:32:32 gauranga kernel: pnp 00:01: [io 0x0820-0x0823]
    Mar 22 18:32:32 gauranga kernel: pnp 00:01: [io 0x0400-0x047f]
    Mar 22 18:32:32 gauranga kernel: pnp 00:01: [io 0x0500-0x053f]
    Mar 22 18:32:32 gauranga kernel: pnp 00:01: [mem 0xf8000000-0xfbffffff]
    Mar 22 18:32:32 gauranga kernel: pnp 00:01: [mem 0xfed1c000-0xfed1ffff]
    Mar 22 18:32:32 gauranga kernel: pnp 00:01: [mem 0xfed10000-0xfed13fff]
    Mar 22 18:32:32 gauranga kernel: pnp 00:01: [mem 0xfed18000-0xfed18fff]
    Mar 22 18:32:32 gauranga kernel: pnp 00:01: [mem 0xfed19000-0xfed19fff]
    Mar 22 18:32:32 gauranga kernel: pnp 00:01: [mem 0xfec00000-0xfec00fff]
    Mar 22 18:32:32 gauranga kernel: pnp 00:01: [mem 0xfed20000-0xfed3ffff]
    Mar 22 18:32:32 gauranga kernel: pnp 00:01: [mem 0xfed40000-0xfed44fff]
    Mar 22 18:32:32 gauranga kernel: pnp 00:01: [mem 0xfed45000-0xfed8ffff]
    Mar 22 18:32:32 gauranga kernel: pnp 00:01: [mem 0xfee00000-0xfee00fff]
    Mar 22 18:32:32 gauranga kernel: system 00:01: [io 0x164e-0x164f] has been reserved
    Mar 22 18:32:32 gauranga kernel: system 00:01: [io 0x0200-0x020f] has been reserved
    Mar 22 18:32:32 gauranga kernel: system 00:01: [io 0x0600-0x060f] has been reserved
    Mar 22 18:32:32 gauranga kernel: system 00:01: [io 0x0610] has been reserved
    Mar 22 18:32:32 gauranga kernel: system 00:01: [io 0x0800-0x080f] has been reserved
    Mar 22 18:32:32 gauranga kernel: system 00:01: [io 0x0810-0x0817] has been reserved
    Mar 22 18:32:32 gauranga kernel: system 00:01: [io 0x0820-0x0823] has been reserved
    Mar 22 18:32:32 gauranga kernel: system 00:01: [io 0x0400-0x047f] has been reserved
    Mar 22 18:32:32 gauranga kernel: system 00:01: [io 0x0500-0x053f] has been reserved
    Mar 22 18:32:32 gauranga kernel: system 00:01: [mem 0xf8000000-0xfbffffff] has been reserved
    Mar 22 18:32:32 gauranga kernel: system 00:01: [mem 0xfed1c000-0xfed1ffff] has been reserved
    Mar 22 18:32:32 gauranga kernel: system 00:01: [mem 0xfed10000-0xfed13fff] has been reserved
    Mar 22 18:32:32 gauranga kernel: system 00:01: [mem 0xfed18000-0xfed18fff] has been reserved
    Mar 22 18:32:32 gauranga kernel: system 00:01: [mem 0xfed19000-0xfed19fff] has been reserved
    Mar 22 18:32:32 gauranga kernel: system 00:01: [mem 0xfec00000-0xfec00fff] could not be reserved
    Mar 22 18:32:32 gauranga kernel: system 00:01: [mem 0xfed20000-0xfed3ffff] has been reserved
    Mar 22 18:32:32 gauranga kernel: system 00:01: [mem 0xfed40000-0xfed44fff] has been reserved
    Mar 22 18:32:32 gauranga kernel: system 00:01: [mem 0xfed45000-0xfed8ffff] has been reserved
    Mar 22 18:32:32 gauranga kernel: system 00:01: [mem 0xfee00000-0xfee00fff] has been reserved
    Mar 22 18:32:32 gauranga kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
    Mar 22 18:32:32 gauranga kernel: pnp 00:02: [io 0x0000-0x001f]
    Mar 22 18:32:32 gauranga kernel: pnp 00:02: [io 0x0081-0x0091]
    Mar 22 18:32:32 gauranga kernel: pnp 00:02: [io 0x0093-0x009f]
    Mar 22 18:32:32 gauranga kernel: pnp 00:02: [io 0x00c0-0x00df]
    Mar 22 18:32:32 gauranga kernel: pnp 00:02: [dma 4]
    Mar 22 18:32:32 gauranga kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0200 (active)
    Mar 22 18:32:32 gauranga kernel: pnp 00:03: [io 0x0070-0x0077]
    Mar 22 18:32:32 gauranga kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active)
    Mar 22 18:32:32 gauranga kernel: pnp 00:04: [irq 0 disabled]
    Mar 22 18:32:32 gauranga kernel: pnp 00:04: [irq 8]
    Mar 22 18:32:32 gauranga kernel: pnp 00:04: [mem 0xfed00000-0xfed003ff]
    Mar 22 18:32:32 gauranga kernel: pnp 00:04: Plug and Play ACPI device, IDs PNP0103 (active)
    Mar 22 18:32:32 gauranga kernel: pnp 00:05: [io 0x00f0]
    Mar 22 18:32:32 gauranga kernel: pnp 00:05: [irq 13]
    Mar 22 18:32:32 gauranga kernel: pnp 00:05: Plug and Play ACPI device, IDs PNP0c04 (active)
    Mar 22 18:32:32 gauranga kernel: pnp 00:06: [io 0x0060]
    Mar 22 18:32:32 gauranga kernel: pnp 00:06: [io 0x0064]
    Mar 22 18:32:32 gauranga kernel: pnp 00:06: [irq 1]
    Mar 22 18:32:32 gauranga kernel: pnp 00:06: Plug and Play ACPI device, IDs PNP0303 (active)
    Mar 22 18:32:32 gauranga kernel: pnp 00:07: [irq 12]
    Mar 22 18:32:32 gauranga kernel: pnp 00:07: Plug and Play ACPI device, IDs SNY900f PNP0f13 (active)
    Mar 22 18:32:32 gauranga kernel: pnp: PnP ACPI: found 8 devices
    Mar 22 18:32:32 gauranga kernel: ACPI: ACPI bus type pnp unregistered
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1c.0: PCI bridge to [bus 02-02]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1c.0: bridge window [io 0x4000-0x5fff]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1c.0: bridge window [mem 0xd5700000-0xd67fffff]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1c.0: bridge window [mem 0xd0400000-0xd13fffff 64bit pref]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1c.2: PCI bridge to [bus 03-03]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1c.2: bridge window [io 0x3000-0x3fff]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1c.2: bridge window [mem 0xd4600000-0xd56fffff]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1c.2: bridge window [mem 0xd1400000-0xd23fffff 64bit pref]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1c.4: PCI bridge to [bus 04-05]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1c.4: bridge window [io 0x2000-0x2fff]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1c.4: bridge window [mem 0xd3600000-0xd45fffff]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1c.4: bridge window [mem 0xd2400000-0xd33fffff 64bit pref]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1e.0: PCI bridge to [bus 06-06]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1e.0: bridge window [mem 0xd3500000-0xd35fffff]
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1c.4: enabling device (0000 -> 0003)
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:1e.0: setting latency timer to 64
    Mar 22 18:32:32 gauranga kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
    Mar 22 18:32:32 gauranga kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
    Mar 22 18:32:32 gauranga kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
    Mar 22 18:32:32 gauranga kernel: pci_bus 0000:00: resource 7 [mem 0xc0000000-0xfebfffff]
    Mar 22 18:32:32 gauranga kernel: pci_bus 0000:02: resource 0 [io 0x4000-0x5fff]
    Mar 22 18:32:32 gauranga kernel: pci_bus 0000:02: resource 1 [mem 0xd5700000-0xd67fffff]
    Mar 22 18:32:32 gauranga kernel: pci_bus 0000:02: resource 2 [mem 0xd0400000-0xd13fffff 64bit pref]
    Mar 22 18:32:32 gauranga kernel: pci_bus 0000:03: resource 0 [io 0x3000-0x3fff]
    Mar 22 18:32:32 gauranga kernel: pci_bus 0000:03: resource 1 [mem 0xd4600000-0xd56fffff]
    Mar 22 18:32:32 gauranga kernel: pci_bus 0000:03: resource 2 [mem 0xd1400000-0xd23fffff 64bit pref]
    Mar 22 18:32:32 gauranga kernel: pci_bus 0000:04: resource 0 [io 0x2000-0x2fff]
    Mar 22 18:32:32 gauranga kernel: pci_bus 0000:04: resource 1 [mem 0xd3600000-0xd45fffff]
    Mar 22 18:32:32 gauranga kernel: pci_bus 0000:04: resource 2 [mem 0xd2400000-0xd33fffff 64bit pref]
    Mar 22 18:32:32 gauranga kernel: pci_bus 0000:06: resource 1 [mem 0xd3500000-0xd35fffff]
    Mar 22 18:32:32 gauranga kernel: pci_bus 0000:06: resource 4 [io 0x0000-0x0cf7]
    Mar 22 18:32:32 gauranga kernel: pci_bus 0000:06: resource 5 [io 0x0d00-0xffff]
    Mar 22 18:32:32 gauranga kernel: pci_bus 0000:06: resource 6 [mem 0x000a0000-0x000bffff]
    Mar 22 18:32:32 gauranga kernel: pci_bus 0000:06: resource 7 [mem 0xc0000000-0xfebfffff]
    Mar 22 18:32:32 gauranga kernel: NET: Registered protocol family 2
    Mar 22 18:32:32 gauranga kernel: IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
    Mar 22 18:32:32 gauranga kernel: TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
    Mar 22 18:32:32 gauranga kernel: TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
    Mar 22 18:32:32 gauranga kernel: TCP: Hash tables configured (established 131072 bind 65536)
    Mar 22 18:32:32 gauranga kernel: TCP: reno registered
    Mar 22 18:32:32 gauranga kernel: UDP hash table entries: 512 (order: 2, 16384 bytes)
    Mar 22 18:32:32 gauranga kernel: UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
    Mar 22 18:32:32 gauranga kernel: NET: Registered protocol family 1
    Mar 22 18:32:32 gauranga kernel: pci 0000:00:02.0: Boot video device
    Mar 22 18:32:32 gauranga kernel: PCI: CLS 64 bytes, default 64
    Mar 22 18:32:32 gauranga kernel: Unpacking initramfs...
    Mar 22 18:32:32 gauranga kernel: Freeing initrd memory: 3348k freed
    Mar 22 18:32:32 gauranga kernel: Simple Boot Flag value 0x5 read from CMOS RAM was invalid
    Mar 22 18:32:32 gauranga kernel: Simple Boot Flag at 0x44 set to 0x1
    Mar 22 18:32:32 gauranga kernel: apm: BIOS not found.
    Mar 22 18:32:32 gauranga kernel: audit: initializing netlink socket (disabled)
    Mar 22 18:32:32 gauranga kernel: type=2000 audit(1363957344.346:1): initialized
    Mar 22 18:32:32 gauranga kernel: highmem bounce pool size: 64 pages
    Mar 22 18:32:32 gauranga kernel: HugeTLB registered 4 MB page size, pre-allocated 0 pages
    Mar 22 18:32:32 gauranga kernel: VFS: Disk quotas dquot_6.5.2
    Mar 22 18:32:32 gauranga kernel: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
    Mar 22 18:32:32 gauranga kernel: msgmni has been set to 1702
    Mar 22 18:32:32 gauranga kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
    Mar 22 18:32:32 gauranga kernel: io scheduler noop registered
    Mar 22 18:32:32 gauranga kernel: io scheduler deadline registered
    Mar 22 18:32:32 gauranga kernel: io scheduler cfq registered (default)
    Mar 22 18:32:32 gauranga kernel: pcieport 0000:00:1c.0: irq 40 for MSI/MSI-X
    Mar 22 18:32:32 gauranga kernel: pcieport 0000:00:1c.2: irq 41 for MSI/MSI-X
    Mar 22 18:32:32 gauranga kernel: pcieport 0000:00:1c.4: irq 42 for MSI/MSI-X
    Mar 22 18:32:32 gauranga kernel: vesafb: mode is 1280x800x32, linelength=5120, pages=0
    Mar 22 18:32:32 gauranga kernel: vesafb: scrolling: redraw
    Mar 22 18:32:32 gauranga kernel: vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
    Mar 22 18:32:32 gauranga kernel: vesafb: framebuffer at 0xc0000000, mapped to 0xf8080000, using 4032k, total 4032k
    Mar 22 18:32:32 gauranga kernel: Console: switching to colour frame buffer device 160x50
    Mar 22 18:32:32 gauranga kernel: fb0: VESA VGA frame buffer device
    Mar 22 18:32:32 gauranga kernel: intel_idle: does not run on family 6 model 23
    Mar 22 18:32:32 gauranga kernel: GHES: HEST is not enabled!
    Mar 22 18:32:32 gauranga kernel: isapnp: Scanning for PnP cards...
    Mar 22 18:32:32 gauranga kernel: isapnp: No Plug & Play device found
    Mar 22 18:32:32 gauranga kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    Mar 22 18:32:32 gauranga kernel: i8042: PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:MOUE] at 0x60,0x64 irq 1,12
    Mar 22 18:32:32 gauranga kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
    Mar 22 18:32:32 gauranga kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
    Mar 22 18:32:32 gauranga kernel: mousedev: PS/2 mouse device common for all mice
    Mar 22 18:32:32 gauranga kernel: rtc_cmos 00:03: RTC can wake from S4
    Mar 22 18:32:32 gauranga kernel: rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
    Mar 22 18:32:32 gauranga kernel: rtc0: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
    Mar 22 18:32:32 gauranga kernel: cpuidle: using governor ladder
    Mar 22 18:32:32 gauranga kernel: cpuidle: using governor menu
    Mar 22 18:32:32 gauranga kernel: drop_monitor: Initializing network drop monitor service
    Mar 22 18:32:32 gauranga kernel: TCP: cubic registered
    Mar 22 18:32:32 gauranga kernel: NET: Registered protocol family 10
    Mar 22 18:32:32 gauranga kernel: NET: Registered protocol family 17
    Mar 22 18:32:32 gauranga kernel: Key type dns_resolver registered
    Mar 22 18:32:32 gauranga kernel: Using IPI No-Shortcut mode
    Mar 22 18:32:32 gauranga kernel: PM: Checking hibernation image partition /dev/sda6
    Mar 22 18:32:32 gauranga kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
    Mar 22 18:32:32 gauranga kernel: PM: Hibernation image not present or could not be loaded.
    Mar 22 18:32:32 gauranga kernel: registered taskstats version 1
    Mar 22 18:32:32 gauranga kernel: rtc_cmos 00:03: setting system clock to 2013-03-22 13:02:25 UTC (1363957345)
    Mar 22 18:32:32 gauranga kernel: Freeing unused kernel memory: 532k freed
    Mar 22 18:32:32 gauranga kernel: Write protecting the kernel text: 3900k
    Mar 22 18:32:32 gauranga kernel: Write protecting the kernel read-only data: 1136k
    Mar 22 18:32:32 gauranga systemd-udevd[39]: starting version 197
    Mar 22 18:32:32 gauranga kernel: Linux agpgart interface v0.103
    Mar 22 18:32:32 gauranga kernel: [drm] Initialized drm 1.1.0 20060810
    Mar 22 18:32:32 gauranga kernel: agpgart-intel 0000:00:00.0: Intel GM45 Chipset
    Mar 22 18:32:32 gauranga kernel: agpgart-intel 0000:00:00.0: detected gtt size: 2097152K total, 262144K mappable
    Mar 22 18:32:32 gauranga kernel: agpgart-intel 0000:00:00.0: detected 131072K stolen memory
    Mar 22 18:32:32 gauranga kernel: agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xc0000000
    Mar 22 18:32:32 gauranga kernel: input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1
    Mar 22 18:32:32 gauranga kernel: ACPI: Power Button [PWRB]
    Mar 22 18:32:32 gauranga kernel: input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input2
    Mar 22 18:32:32 gauranga kernel: ACPI: Lid Switch [LID0]
    Mar 22 18:32:32 gauranga kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
    Mar 22 18:32:32 gauranga kernel: ACPI: Power Button [PWRF]
    Mar 22 18:32:32 gauranga kernel: checking generic (c0000000 3f0000) vs hw (c0000000 10000000)
    Mar 22 18:32:32 gauranga kernel: fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver
    Mar 22 18:32:32 gauranga kernel: Console: switching to colour dummy device 80x25
    Mar 22 18:32:32 gauranga kernel: i915 0000:00:02.0: setting latency timer to 64
    Mar 22 18:32:32 gauranga kernel: i915 0000:00:02.0: irq 43 for MSI/MSI-X
    Mar 22 18:32:32 gauranga kernel: [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
    Mar 22 18:32:32 gauranga kernel: [drm] Driver supports precise vblank timestamp query.
    Mar 22 18:32:32 gauranga kernel: vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
    Mar 22 18:32:32 gauranga kernel: fbcon: inteldrmfb (fb0) is primary device
    Mar 22 18:32:32 gauranga kernel: Refined TSC clocksource calibration: 2393.999 MHz.
    Mar 22 18:32:32 gauranga kernel: Switching to clocksource tsc
    Mar 22 18:32:32 gauranga kernel: Console: switching to colour frame buffer device 160x50
    Mar 22 18:32:32 gauranga kernel: fb0: inteldrmfb frame buffer device
    Mar 22 18:32:32 gauranga kernel: drm: registered panic notifier
    Mar 22 18:32:32 gauranga kernel: acpi device:02: registered as cooling_device0
    Mar 22 18:32:32 gauranga kernel: ACPI: Video Device [OVGA] (multi-head: yes rom: no post: no)
    Mar 22 18:32:32 gauranga kernel: input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input4
    Mar 22 18:32:32 gauranga kernel: [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
    Mar 22 18:32:32 gauranga kernel: ACPI: bus type usb registered
    Mar 22 18:32:32 gauranga kernel: usbcore: registered new interface driver usbfs
    Mar 22 18:32:32 gauranga kernel: usbcore: registered new interface driver hub
    Mar 22 18:32:32 gauranga kernel: usbcore: registered new device driver usb
    Mar 22 18:32:32 gauranga kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    Mar 22 18:32:32 gauranga kernel: ehci_hcd 0000:00:1a.7: setting latency timer to 64
    Mar 22 18:32:32 gauranga kernel: ehci_hcd 0000:00:1a.7: EHCI Host Controller
    Mar 22 18:32:32 gauranga kernel: ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1
    Mar 22 18:32:32 gauranga kernel: ehci_hcd 0000:00:1a.7: debug port 1
    Mar 22 18:32:32 gauranga kernel: ehci_hcd 0000:00:1a.7: cache line size of 64 is not supported
    Mar 22 18:32:32 gauranga kernel: ehci_hcd 0000:00:1a.7: irq 19, io mem 0xd6804c00
    Mar 22 18:32:32 gauranga kernel: SCSI subsystem initialized
    Mar 22 18:32:32 gauranga kernel: libata version 3.00 loaded.
    Mar 22 18:32:32 gauranga kernel: firewire_ohci 0000:06:02.0: setting latency timer to 64
    Mar 22 18:32:32 gauranga kernel: uhci_hcd: USB Universal Host Controller Interface driver
    Mar 22 18:32:32 gauranga kernel: sdhci: Secure Digital Host Controller Interface driver
    Mar 22 18:32:32 gauranga kernel: sdhci: Copyright(c) Pierre Ossman
    Mar 22 18:32:32 gauranga kernel: ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00
    Mar 22 18:32:32 gauranga kernel: hub 1-0:1.0: USB hub found
    Mar 22 18:32:32 gauranga kernel: hub 1-0:1.0: 4 ports detected
    Mar 22 18:32:32 gauranga kernel: ehci_hcd 0000:00:1d.7: setting latency timer to 64
    Mar 22 18:32:32 gauranga kernel: ehci_hcd 0000:00:1d.7: EHCI Host Controller
    Mar 22 18:32:32 gauranga kernel: ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2
    Mar 22 18:32:32 gauranga kernel: ehci_hcd 0000:00:1d.7: debug port 1
    Mar 22 18:32:32 gauranga kernel: ehci_hcd 0000:00:1d.7: cache line size of 64 is not supported
    Mar 22 18:32:32 gauranga kernel: ehci_hcd 0000:00:1d.7: irq 23, io mem 0xd6804800
    Mar 22 18:32:32 gauranga kernel: ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
    Mar 22 18:32:32 gauranga kernel: hub 2-0:1.0: USB hub found
    Mar 22 18:32:32 gauranga kernel: hub 2-0:1.0: 6 ports detected
    Mar 22 18:32:32 gauranga kernel: uhci_hcd 0000:00:1a.0: setting latency timer to 64
    Mar 22 18:32:32 gauranga kernel: uhci_hcd 0000:00:1a.0: UHCI Host Controller
    Mar 22 18:32:32 gauranga kernel: uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3
    Mar 22 18:32:32 gauranga kernel: uhci_hcd 0000:00:1a.0: irq 16, io base 0x000060c0
    Mar 22 18:32:32 gauranga kernel: hub 3-0:1.0: USB hub found
    Mar 22 18:32:32 gauranga kernel: hub 3-0:1.0: 2 ports detected
    Mar 22 18:32:32 gauranga kernel: uhci_hcd 0000:00:1a.1: setting latency timer to 64
    Mar 22 18:32:32 gauranga kernel: uhci_hcd 0000:00:1a.1: UHCI Host Controller
    Mar 22 18:32:32 gauranga kernel: uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4
    Mar 22 18:32:32 gauranga kernel: uhci_hcd 0000:00:1a.1: irq 21, io base 0x000060a0
    Mar 22 18:32:32 gauranga kernel: hub 4-0:1.0: USB hub found
    Mar 22 18:32:32 gauranga kernel: hub 4-0:1.0: 2 ports detected
    Mar 22 18:32:32 gauranga kernel: uhci_hcd 0000:00:1d.0: setting latency timer to 64
    Mar 22 18:32:32 gauranga kernel: uhci_hcd 0000:00:1d.0: UHCI Host Controller
    Mar 22 18:32:32 gauranga kernel: uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 5
    Mar 22 18:32:32 gauranga kernel: uhci_hcd 0000:00:1d.0: irq 23, io base 0x00006080
    Mar 22 18:32:32 gauranga kernel: hub 5-0:1.0: USB hub found
    Mar 22 18:32:32 gauranga kernel: hub 5-0:1.0: 2 ports detected
    Mar 22 18:32:32 gauranga kernel: uhci_hcd 0000:00:1d.1: setting latency timer to 64
    Mar 22 18:32:32 gauranga kernel: uhci_hcd 0000:00:1d.1: UHCI Host Controller
    Mar 22 18:32:32 gauranga kernel: uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 6
    Mar 22 18:32:32 gauranga kernel: uhci_hcd 0000:00:1d.1: irq 19, io base 0x00006060
    Mar 22 18:32:32 gauranga kernel: hub 6-0:1.0: USB hub found
    Mar 22 18:32:32 gauranga kernel: hub 6-0:1.0: 2 ports detected
    Mar 22 18:32:32 gauranga kernel: uhci_hcd 0000:00:1d.2: setting latency timer to 64
    Mar 22 18:32:32 gauranga kernel: uhci_hcd 0000:00:1d.2: UHCI Host Controller
    Mar 22 18:32:32 gauranga kernel: uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 7
    Mar 22 18:32:32 gauranga kernel: uhci_hcd 0000:00:1d.2: irq 16, io base 0x00006040
    Mar 22 18:32:32 gauranga kernel: hub 7-0:1.0: USB hub found
    Mar 22 18:32:32 gauranga kernel: hub 7-0:1.0: 2 ports detected
    Mar 22 18:32:32 gauranga kernel: ahci 0000:00:1f.2: version 3.0
    Mar 22 18:32:32 gauranga kernel: ahci 0000:00:1f.2: irq 44 for MSI/MSI-X
    Mar 22 18:32:32 gauranga kernel: ahci: SSS flag set, parallel bus scan disabled
    Mar 22 18:32:32 gauranga kernel: ahci 0000:00:1f.2: AHCI 0001.0200 32 slots 4 ports 3 Gbps 0x3 impl SATA mode
    Mar 22 18:32:32 gauranga kernel: ahci 0000:00:1f.2: flags: 64bit ncq sntf stag pm led clo pio slum part ccc ems
    Mar 22 18:32:32 gauranga kernel: ahci 0000:00:1f.2: setting latency timer to 64
    Mar 22 18:32:32 gauranga kernel: scsi0 : ahci
    Mar 22 18:32:32 gauranga kernel: scsi1 : ahci
    Mar 22 18:32:32 gauranga kernel: scsi2 : ahci
    Mar 22 18:32:32 gauranga kernel: scsi3 : ahci
    Mar 22 18:32:32 gauranga kernel: ata1: SATA max UDMA/133 abar m2048@0xd6804000 port 0xd6804100 irq 44
    Mar 22 18:32:32 gauranga kernel: ata2: SATA max UDMA/133 abar m2048@0xd6804000 port 0xd6804180 irq 44
    Mar 22 18:32:32 gauranga kernel: ata3: DUMMY
    Mar 22 18:32:32 gauranga kernel: ata4: DUMMY
    Mar 22 18:32:32 gauranga kernel: firewire_ohci 0000:06:02.0: added OHCI v1.0 device as card 0, 4 IR + 4 IT contexts, quirks 0x11
    Mar 22 18:32:32 gauranga kernel: sdhci-pci 0000:06:02.1: SDHCI controller found [1180:0822] (rev 22)
    Mar 22 18:32:32 gauranga kernel: sdhci-pci 0000:06:02.1: Will use DMA mode even though HW doesn't fully claim to support it.
    Mar 22 18:32:32 gauranga kernel: sdhci-pci 0000:06:02.1: setting latency timer to 64
    Mar 22 18:32:32 gauranga kernel: sdhci-pci 0000:06:02.1: Will use DMA mode even though HW doesn't fully claim to support it.
    Mar 22 18:32:32 gauranga kernel: Registered led device: mmc0::
    Mar 22 18:32:32 gauranga kernel: mmc0: SDHCI controller on PCI [0000:06:02.1] using DMA
    Mar 22 18:32:32 gauranga kernel: sdhci-pci 0000:06:02.1: Will use DMA mode even though HW doesn't fully claim to support it.
    Mar 22 18:32:32 gauranga kernel: sdhci-pci 0000:06:02.1: Will use DMA mode even though HW doesn't fully claim to support it.
    Mar 22 18:32:32 gauranga kernel: sdhci-pci 0000:06:02.1: Will use DMA mode even though HW doesn't fully claim to support it.
    Mar 22 18:32:32 gauranga kernel: sdhci-pci 0000:06:02.1: Will use DMA mode even though HW doesn't fully claim to support it.
    Mar 22 18:32:32 gauranga kernel: usb 1-2: new high-speed USB device number 2 using ehci_hcd
    Mar 22 18:32:32 gauranga kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    Mar 22 18:32:32 gauranga kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
    Mar 22 18:32:32 gauranga kernel: ata1.00: ATA-8: TOSHIBA MK3252GSX, LV010A, max UDMA/100
    Mar 22 18:32:32 gauranga kernel: ata1.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
    Mar 22 18:32:32 gauranga kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
    Mar 22 18:32:32 gauranga kernel: ata1.00: configured for UDMA/100
    Mar 22 18:32:32 gauranga kernel: scsi 0:0:0:0: Direct-Access ATA TOSHIBA MK3252GS LV01 PQ: 0 ANSI: 5
    Mar 22 18:32:32 gauranga kernel: firewire_core 0000:06:02.0: created device fw0: GUID 0800460304dbc9e2, S400
    Mar 22 18:32:32 gauranga kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    Mar 22 18:32:32 gauranga kernel: ata2.00: ATAPI: MATSHITADVD-RAM UJ880AS, 1.20, max UDMA/33
    Mar 22 18:32:32 gauranga kernel: ata2.00: configured for UDMA/33
    Mar 22 18:32:32 gauranga kernel: scsi 1:0:0:0: CD-ROM MATSHITA DVD-RAM UJ880AS 1.20 PQ: 0 ANSI: 5
    Mar 22 18:32:32 gauranga kernel: sd 0:0:0:0: [sda] 625142448 512-byte logical blocks: (320 GB/298 GiB)
    Mar 22 18:32:32 gauranga kernel: sd 0:0:0:0: [sda] Write Protect is off
    Mar 22 18:32:32 gauranga kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
    Mar 22 18:32:32 gauranga kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    Mar 22 18:32:32 gauranga kernel: sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
    Mar 22 18:32:32 gauranga kernel: cdrom: Uniform CD-ROM driver Revision: 3.20
    Mar 22 18:32:32 gauranga kernel: sr 1:0:0:0: Attached scsi CD-ROM sr0
    Mar 22 18:32:32 gauranga kernel: sda: sda1 sda2 sda3 < sda5 sda6 >
    Mar 22 18:32:32 gauranga kernel: sd 0:0:0:0: [sda] Attached SCSI disk
    Mar 22 18:32:32 gauranga kernel: usb 7-1: new full-speed USB device number 2 using uhci_hcd
    Mar 22 18:32:32 gauranga kernel: EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
    Mar 22 18:32:32 gauranga systemd[1]: systemd 197 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)
    Mar 22 18:32:32 gauranga systemd[1]: Inserted module 'autofs4'
    Mar 22 18:32:32 gauranga systemd[1]: Set hostname to <gauranga>.
    Mar 22 18:32:32 gauranga systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No su
    Mar 22 18:32:32 gauranga systemd[1]: Starting Collect Read-Ahead Data...
    Mar 22 18:32:32 gauranga systemd[1]: Starting Replay Read-Ahead Data...
    Mar 22 18:32:32 gauranga systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
    Mar 22 18:32:32 gauranga systemd[1]: Started Forward Password Requests to Wall Directory Watch.
    Mar 22 18:32:32 gauranga systemd[1]: Starting Remote File Systems.
    Mar 22 18:32:32 gauranga systemd[1]: Reached target Remote File Systems.
    Mar 22 18:32:32 gauranga systemd[1]: Starting Device-mapper event daemon FIFOs.
    Mar 22 18:32:32 gauranga systemd[1]: Listening on Device-mapper event daemon FIFOs.
    Mar 22 18:32:32 gauranga systemd[1]: Starting Delayed Shutdown Socket.
    Mar 22 18:32:32 gauranga systemd[1]: Listening on Delayed Shutdown Socket.
    Mar 22 18:32:32 gauranga systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
    Mar 22 18:32:32 gauranga systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
    Mar 22 18:32:32 gauranga systemd[1]: Starting LVM2 metadata daemon socket.
    Mar 22 18:32:32 gauranga systemd[1]: Listening on LVM2 metadata daemon socket.
    Mar 22 18:32:32 gauranga systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
    Mar 22 18:32:32 gauranga systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
    Mar 22 18:32:32 gauranga systemd[1]: Starting Encrypted Volumes.
    Mar 22 18:32:32 gauranga systemd[1]: Reached target Encrypted Volumes.
    Mar 22 18:32:32 gauranga systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
    Mar 22 18:32:32 gauranga systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
    Mar 22 18:32:32 gauranga systemd[1]: Starting udev Kernel Socket.
    Mar 22 18:32:32 gauranga systemd[1]: Listening on udev Kernel Socket.
    Mar 22 18:32:32 gauranga systemd[1]: Starting udev Control Socket.
    Mar 22 18:32:32 gauranga systemd[1]: Listening on udev Control Socket.
    Mar 22 18:32:32 gauranga systemd[1]: Expecting device dev-sda6.device...
    Mar 22 18:32:32 gauranga systemd[1]: Expecting device dev-sda2.device...
    Mar 22 18:32:32 gauranga systemd[1]: Starting Journal Socket.
    Mar 22 18:32:32 gauranga systemd[1]: Listening on Journal Socket.
    Mar 22 18:32:32 gauranga systemd[1]: Mounting Debug File System...
    Mar 22 18:32:32 gauranga systemd-readahead[108]: Bumped block_nr parameter of 8:0 to 20480. This is a temporary hack and should be removed one day.
    Mar 22 18:32:32 gauranga systemd[1]: Starting udev Kernel Device Manager...
    Mar 22 18:32:32 gauranga systemd[1]: Mounting POSIX Message Queue File System...
    Mar 22 18:32:32 gauranga systemd[1]: Starting udev Coldplug all Devices...
    Mar 22 18:32:32 gauranga systemd[1]: Mounting Huge Pages File System...
    Mar 22 18:32:32 gauranga systemd[1]: Starting Journal Service...
    Mar 22 18:32:32 gauranga systemd[1]: Started Journal Service.
    Mar 22 18:32:32 gauranga kernel: vboxdrv: Found 2 processor cores.
    Mar 22 18:32:32 gauranga kernel: vboxdrv: fAsync=0 offMin=0x225 offMax=0x13f8
    Mar 22 18:32:32 gauranga kernel: vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
    Mar 22 18:32:32 gauranga kernel: vboxdrv: Successfully loaded version 4.2.0 (interface 0x001a0004).
    Mar 22 18:32:32 gauranga systemd-udevd[110]: starting version 197
    Mar 22 18:32:32 gauranga systemd-journal[114]: Journal started
    Mar 22 18:32:32 gauranga systemd[1]: Started Collect Read-Ahead Data.
    Mar 22 18:32:32 gauranga systemd[1]: Started Replay Read-Ahead Data.
    Mar 22 18:32:32 gauranga systemd[1]: Started File System Check on Root Device.
    Mar 22 18:32:32 gauranga systemd[1]: Starting Remount Root and Kernel File Systems...
    Mar 22 18:32:32 gauranga systemd[1]: Starting Setup Virtual Console...
    Mar 22 18:32:32 gauranga systemd[1]: Starting Set Up Additional Binary Formats...
    Mar 22 18:32:32 gauranga systemd[1]: Starting Load Kernel Modules...
    Mar 22 18:32:32 gauranga systemd[1]: Starting Apply Kernel Variables...
    Mar 22 18:32:32 gauranga systemd[1]: Mounting Arbitrary Executable File Formats File System...
    Mar 22 18:32:32 gauranga systemd-modules-load[118]: Inserted module 'vboxdrv'
    Mar 22 18:32:32 gauranga systemd[1]: Started Load Kernel Modules.
    Mar 22 18:32:33 gauranga kernel: ACPI: AC Adapter [AC] (on-line)
    Mar 22 18:32:33 gauranga kernel: thermal LNXTHERM:00: registered as thermal_zone0
    Mar 22 18:32:33 gauranga kernel: ACPI: Thermal Zone [THRM] (51 C)
    Mar 22 18:32:34 gauranga kernel: ACPI: Battery Slot [BAT1] (battery present)
    Mar 22 18:32:34 gauranga kernel: input: PC Speaker as /devices/platform/pcspkr/input/input5
    Mar 22 18:32:34 gauranga kernel: ACPI Warning: 0x00000428-0x0000042f SystemIO conflicts with Region \PMBA 1 (20120320/utaddress-251)
    Mar 22 18:32:34 gauranga kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
    Mar 22 18:32:34 gauranga kernel: ACPI Warning: 0x00000500-0x0000053f SystemIO conflicts with Region \GPIO 1 (20120320/utaddress-251)
    Mar 22 18:32:34 gauranga kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
    Mar 22 18:32:34 gauranga kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
    Mar 22 18:32:34 gauranga kernel: ACPI: Requesting acpi_cpufreq
    Mar 22 18:32:34 gauranga kernel: Monitor-Mwait will be used to enter C-1 state
    Mar 22 18:32:34 gauranga kernel: cfg80211: Calling CRDA to update world regulatory domain
    Mar 22 18:32:34 gauranga kernel: Monitor-Mwait will be used to enter C-2 state
    Mar 22 18:32:34 gauranga kernel: Monitor-Mwait will be used to enter C-3 state
    Mar 22 18:32:34 gauranga kernel: Marking TSC unstable due to TSC halts in idle
    Mar 22 18:32:34 gauranga kernel: ACPI: acpi_idle registered with cpuidle
    Mar 22 18:32:34 gauranga kernel: Switching to clocksource hpet
    Mar 22 18:32:34 gauranga kernel: sky2: driver version 1.30
    Mar 22 18:32:34 gauranga kernel: sky2 0000:02:00.0: Yukon-2 FE+ chip revision 0
    Mar 22 18:32:34 gauranga kernel: sky2 0000:02:00.0: irq 45 for MSI/MSI-X
    Mar 22 18:32:34 gauranga kernel: sky2 0000:02:00.0: eth0: addr 00:1d:ba:07:87:98
    Mar 22 18:32:34 gauranga kernel: iTCO_vendor_support: vendor-support=0
    Mar 22 18:32:34 gauranga kernel: sony_laptop: Sony Notebook Control Driver v0.6
    Mar 22 18:32:34 gauranga kernel: input: Sony Vaio Keys as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0a/SNY5001:00/input/input6
    Mar 22 18:32:34 gauranga kernel: input: Sony Vaio Jogdial as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0a/SNY5001:00/input/input7
    Mar 22 18:32:34 gauranga kernel: iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07
    Mar 22 18:32:34 gauranga kernel: iTCO_wdt: Found a ICH9M TCO device (Version=2, TCOBASE=0x0460)
    Mar 22 18:32:34 gauranga kernel: iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
    Mar 22 18:32:34 gauranga kernel: microcode: CPU0 sig=0x1067a, pf=0x80, revision=0xa07
    Mar 22 18:32:34 gauranga kernel: sony_laptop: brightness ignored, must be controlled by ACPI video driver
    Mar 22 18:32:34 gauranga kernel: microcode: CPU1 sig=0x1067a, pf=0x80, revision=0xa07
    Mar 22 18:32:34 gauranga kernel: microcode: Microcode Update Driver: v2.00 <tigran@aiva

    hi
    enable Readahead from systemd
    https://wiki.archlinux.org/index.php/Systemd#Readahead
    # systemctl enable systemd-readahead-collect systemd-readahead-replay

  • How to create a new blob to store VHD's to present to VM's (not a programmer!)

    Hello all,
    I'm using the IAAS components of Azure. I have a several vm's spun up and only had the default storage account setup. until I became aware of how Azure manages storage in terms of IOPS and throughput.. in an effort to increase performance and keep certain
    workloads on different spindles I created a second storage account. Then a container. Thinking I would then be able to select this or manually enter the url for the storage container when attaching a disk to a VM. however I understand now that's not how it
    works. That's the good news. What I don't understand is how it DOES work. all the references I find to creating a new blob are for developers and are talking about code writing and such and that's only for programmatic access not access from the "attach
    new disk" gui in the management portal (where you cant just simply change the url even if I managed to create a new page blob. I just want to be able to use that new storage location to store VHDS in and use it when attaching disks. Any help would be
    appreciated.

    Hi Jose;
    If i understand it correctly you are trying to create a new storage account and then transfer the existing VHD please make sure that the VM needs to be shutdown before you move it. Steps involved are : 
    Shut down the VM
    Copy the system disk's VHD to the new storage account (use
    Copy Blob feature!)
    Create a new VM based on the copied VHD   
    As you have posted you are not a programmer i have listed the detailed steps.
    Link
    to create a new storage account.
    To transfer vhd/ blob storage to a different storage account please use Cloud Explorer given below is  the details.
    How to Use Cross-Account Copy with CloudBerry Explorer
    1. Run CloudBerry Explorer for Windows Azure.
    2. Select two different Windows Azure storage accounts from the “Source” drop-down list.
    3. Move any object you want just as usually. Your objects will be transferred using Azure cross-account copy feature.
    Note: cross-account copy feature works only when moving data from any Windows Azure accounts to those that have been created after June 7th 2012. For transferring data to accounts that were
    created earlier cross-account copy wouldn't work.
    If you want more details about Azure cross-account copy feature, please check
    Windows Azure Storage Team Blog.
    Hope this is helpful.
    Warm Regards
    Prasant

  • How to set CORS properties for BLOB Storage using node?

    Hi - I just got started with Azure using a Node-based web site and mobile services.
    I am following various documentation in order to provide an API for users to upload images via a time-restricted SAS for the BLOB Storage.
    In order to upload my image, I need to set the CORS configuration for the BLOB Storage. Unfortunately this cannot be done via the management portal.
    I'm unclear as to how to accomplish this. I'm considering using the startup.js file in my mobile service to make a post request to the BLOB Storage REST API:
    http://msdn.microsoft.com/en-us/library/windowsazure/hh452235.aspx
    Are there appropriate methods in the Node SDK to make this easier, especially the signing part?
    What is the recommended way for setting CORS properties for the BLOB Storage via Node?
    Thanks for your help
    Stefan

    Unfortunately Node SDK does not support CORS functionality yet. Your option would be to write code which consumes the REST API for setting CORS. Not sure if it helps but there's a free tool out there written by my company which you can use to set CORS
    on your storage account. More information about this tool can be found here:
    http://blog.cynapta.com/2013/12/cynapta-azure-cors-helper-free-tool-to-manage-cors-rules-for-windows-azure-blob-storage/
    Hope this helps.

Maybe you are looking for

  • Multiple user mapping challenge, without an AD.

    Dear IdM gurus, I have a challenging situation here and was wondering whether anyone else has made experiences with it. We have the usual collection of ERP ABAP systems + BW + BI Portal + some non-SAP systems which we want to connect to a central IdM

  • ITunes and iPad syncing issues?

    I have songs that appear on my ipad (show iCloud songs is turned off so only songs on my ipad appear) but these songs do not appear when I connect the ipad to my computer when I view what music is on my ipad in iTunes. Same for several music videos.

  • MAC WITH NO FIREWIRE!

    My Lime iMac 333 (X.1) dosent have any fire wire ports for fourth gen ipod. This may sound crazy, but is there some kinda adapter ting that converts USB to FireWire??

  • Mass Change fuctionality for Delivery Documents

    Hi all, I want to carry out a mass change for a field in the delivery document header. I know the transaction MASS is not catering for that. Is that any other standard  transaction to do a mass change in the delivery document header level, other than

  • Space for Archive and Install

    Hello All, I am having the same login problems everyone else seems to be having with a new twist, when i go to archive and install and hopefully fix this mess, i realize that i now only have 6gigs left on my hd, and i need 11 to install. I am assumin