Serial I/O IRQ Method

I am trying to do some simple I/O using an NI 9870 serial module in a cRIO with a NI-9014 host (LabVIEW 9, RIO 3.2.1) .  I am already using 3 DMA FIFO's for other things and was trying to pass the data in and out of the FPGA using an interrupt driven approach.  The baud rate is 57600 which if you do the calculations is ~60 characters in 15 milliseconds.  So here is what I tried and the RT Host immediately stops running after the timeout -  I realize there are all sorts of unhandled conditions in this code but it won't even eat one character....
So here is the FPGA side - there is a pre-allocated array of 255 elements - the loop runs until the array is nearly full or a timeout occurs - at which point an interrupt is generated -
Here is the host side - wait for an IRQ and then read the array, after that ack the IRQ -
Am I missing something simple ?????

Hello, is your wait function on the FPGA set to mSec or uSec or ticks? If its set to mSec then you will have your FPGA code wait 15 ms before even executing the second frame of the sequence so you will reach a timeout on the wait on IRQ every time (when set to 5 ms).
Also, I suggest having a stop control wired to the Stop Terminal of your host loop rather than a true constant so that you can manually stop the loop and have the code complete  ( including closing the FPGA VI reference which I assume is sitting right outside your while loop. This Close FPGA Reference stops your FPGA code and cleans up the reference.
National Instruments

Similar Messages

  • Serial Number Transaction Report Window isn't opening when adding AR Invoice

    Hi,
    For One of my Client the Serial Number Transaction Report Window is not opening when adding the AR Invoice.
    In the Invoice all the item's that is present in the line level are SERIAL MANAGED and Management Method is ON RELEASE ONLY.
    Why is it so?

    Hi,
    Do you receive any error message? Is it possible to add without selecting invoice without selecting serial number?
    What is your B1 version and PL?
    Thanks & Regards,
    Nagarajan

  • Unable to release item recieved with management method release only

    hey i received few quantity from good receipt which is serial managed and management method is release only so sap didn't asked for serial no but when i issue that item out of sap through good issue it ask for serial no but actually there is no serial no. so how to release that  quntity of item out of inventory.

    hai,
    When we invoice item (manage serial No. on release only), system ask select serial No. (Window u2013 serial No. selection) u2013 select the raw of item u2013 right click the mouse u2013 select serial no. management selection criteria press OK- serial no. management selection complete-select automatic creation in right bottom, if u have huge no of items u2013 set no. format & manufacturing serial no. in Automatic serial no. creation window- string (alphabet)-enter no next raw (select Number +increase) then OK
    Select the serial no. from available list, press u201C>u201D then automatically transfer to selected serial no. list u2013 update and returned to invoice.try this way this may be help u
    Regards
    Janeesh

  • BAPI or FM for Get serial number

    Hi,
           We ahve many material for whcih we are maintaining serial numbers,  now  we are excuting some T. code with 3rd party software  and the communication is done through RFC,  as in case of Material issue  with movement type 201,  for serialize material we have to enter the serial number,  we can enter it manually  or if we click on create serial number automatically,  system get the automatic serial number, so thier  any Function al module or BAPi  for getiing serial number automatically  for the materials. which we can use in RFC.
          regards,
            zafar

    Hello,,
    ASSIGN_SERIAL_NUMBER_SD        Listing of Material Serial Nrs
    SERIAL_NUMBER_GET_MATERIALS  Get Serial Nrs
    SELECT_MATERIAL_SERIAL_NRS     Alternate method for selection of serial Nrs
    Or esle check
    Use - BAPI_EQUI_GETSTATUS  i think it should give you the info
    Or else check below given tables for your requirement
    Tables,
    SER00 General Header Table for Serial Number Management
    SER01 Document Header for Serial Numbers for Delivery
    SER02 Document Header for Serial Nos for Maint.Contract (SD Order)
    SER03 Document Header for Serial Numbers for Goods Movements
    SER04 Document Header for Serial Numbers for Inspection Lot
    SER05 Document Header for Serial Numbers for PP Order
    SER06 Document Header for Serial Numbers for Handling Unit-Content
    SER07 Document Header for Serial Numbers in Physical Inventory
    EQBS Serial Number Stock Segment
    EQSE Serial Number Records
    EQST Equipment to BOM Link
    EQUI Equipment master data
    Regards
    Mahesh Naik

  • Read serial number in badi MB_MIGO_ITEM_BADI

    Dear all,
    I'm trying to read the serial number in the method item_modify for a MIGO.
    The structure which can be read in this BADI doesn 't contain the serial number. I searched on the forum, but doesn 't find some guidance. Someone who can help me ?
    thnx in advance !

    Hi Bjorn,
    I'm trying to do the same, which is to modify the serial number that was auto populated, you achieved this via an additional tab?
    Regards,
    Neesha

  • Serial Number selection at order level

    Create an Item managed by Stock, sales and purchased. On 'General'  tab, under 'Serial and Batch Numbers' select 'Manage Item by Serial Numbers' and 'Management method On release only'.
    Create a sales Order for the Item, enter the quantity and the price. Right click on 'Quantity field' for the item, it displays the option 'Batch/Serial number' but this option does not work, it does not open the Batch/Serial Number selection.
    The Customer needs to complete the Serial numbers at Order level. (Now he loads the Serial Numbers scanning a barcode on the Item and updating directly the Sales Order. The storekeeper can see the Serial Numbers on the order and prepare the pallet and the delivery).
    Edited by: Andrea Mosca on Dec 17, 2007 3:21 PM

    Hello Andrea,
    at the moment it is only possible to select a batch number in the Sales Order.
    You could try to work with a draft Delivery document, here you can select the serial numbers.
    Regards,
    Anton.

  • Wait on Multiple IRQs

    If I wire an array of IRQs {0,1,2} to the "Wait on IRQ" Invoke method with a timeout of -1 does the method wait for all the IRQs or at least one?

    Hi Richard,
    It seems that the function will wait until it receives any one of the interrupts specified within the array.
    You can see which one is called from the IRQ asserted array output of the "wait on IRQ" method node.
    Best regards,
    Stephen C
    Applications Engineer

  • A better way to Read Bytes until Done ?

    My question involves reading an unknown number of bytes from the serial
    port. One method is to just wait a defined amount of time to receive
    the bytes and hope you caught all of them. Better: count them until
    they are all received. I have attached an image which shows the method
    I use to count bytes until all bytes are received. However, this method
    is rather slow. It's taking me 500mS to read data that I can normally
    read in 230mS. Is the shift register making this loop slow? Is there a
    better way to read the bytes until all bytes are in?
    Richard
    Attachments:
    ReadBytes.gif ‏5 KB

    Thanks for your reply Chilly.
    Actually, you are correct on both accounts, the delay and the wire from
    the output of Write, and in fact, I usually do those things. I was just
    in a hurry to get an example posted and didn't have my real data.
    To put my issue in broader prospective, I have attached an image that shows boh methods I've used to count bytes. One
    shows the method I use to count bytes until all bytes are received. The
    other is a "hard wired" timer method that I try to avoid, but at least
    it is fast. Notice the text in red. Why would I be able to read the
    byes so much faster in the "hard wired" version? It has to be either
    the shift register, the AND, or the compare functions, and I still
    can't beleive these things would be slower than the Express timer
    function in the other method.
    Methodology: The 235mS timer used in the "hard wired" method was
    emperically derived. The 150 bytes are received 100% of the time when
    235mS is allowed. 230mS yields about 90% of the bytes, the it goes down
    exponentially. I found that the shift register method method trakes
    ~515mS avg by putting a tick count on both sides of the loop and
    finding the resulting time. I also did that with the hard wired method
    and found it to be dead on 235mS which at least proves the Express vi
    works very well
    Message Edited by Broken Arrow on 09-05-2005 08:31 PM
    Message Edited by Broken Arrow on 09-05-2005 08:32 PM
    Richard
    Attachments:
    CoutingBytes.GIF ‏25 KB

  • Eth0 with e1000e stopped working after upgrade to 3.6.2

    Hi!
    After the recent upgrade my eth0 network device does not come up properly anymore.  The Laptop is a Thinkpad x60s and I use the e1000e kernel module for the network card.  After a suspend/wakeup cycle the card/device works properly BTW.. Any help on this would be appreciated!
    ifconfig gives me the following output for eth0:
    eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
    ether 00:16:d3:3b:ac:45 txqueuelen 1000 (Ethernet)
    RX packets 0 bytes 0 (0.0 B)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 0 bytes 0 (0.0 B)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
    device interrupt 16 memory 0xee000000-ee020000
    this section of the dmesg output seems to be suspicient:
    [ 21.226766] e1000e 0000:02:00.0: eth0: Error reading PHY register
    [ 21.227634] e1000e 0000:02:00.0: eth0: Error reading PHY register
    [ 21.228495] e1000e 0000:02:00.0: eth0: Error reading PHY register
    [ 21.229355] e1000e 0000:02:00.0: eth0: Error reading PHY register
    [ 21.230243] e1000e 0000:02:00.0: eth0: Error reading PHY register
    [ 21.232686] e1000e 0000:02:00.0: eth0: Error reading PHY register
    [ 21.233594] e1000e 0000:02:00.0: eth0: Error reading PHY register
    [ 21.234705] e1000e 0000:02:00.0: eth0: Error reading PHY register
    [ 21.235571] e1000e 0000:02:00.0: eth0: Error reading PHY register
    [ 21.236432] e1000e 0000:02:00.0: eth0: Error reading PHY register
    [ 21.249538] uhci_hcd 0000:00:1d.2: power state changed by ACPI to D0
    [ 21.249639] uhci_hcd 0000:00:1d.2: setting latency timer to 64
    [ 21.927013] e1000e 0000:02:00.0: eth0: Cannot change link characteristics when SoL/IDER is active.
    [ 21.930111] e1000e 0000:02:00.0: eth0: Cannot change link characteristics when SoL/IDER is active.
    [ 22.484883] EXT4-fs (sda3): re-mounted. Opts: data=ordered,commit=360
    [ 22.523746] EXT4-fs (dm-0): re-mounted. Opts: data=ordered,commit=360
    [ 22.555973] EXT4-fs (sda1): re-mounted. Opts: (null)
    [ 25.677082] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 31.123064] e1000e 0000:02:00.0: irq 44 for MSI/MSI-X
    [ 31.223549] e1000e 0000:02:00.0: irq 44 for MSI/MSI-X
    [ 31.224213] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 37.550719] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 37.616891] e1000e 0000:02:00.0: Disabling ASPM L0s L1
    [ 37.617086] e1000e 0000:02:00.0: irq 44 for MSI/MSI-X
    [ 37.619424] e1000e 0000:02:00.0: eth0: MAC Wakeup cause - Link Status Change
    [ 37.783054] e1000e 0000:02:00.0: irq 44 for MSI/MSI-X
    [ 37.883540] e1000e 0000:02:00.0: irq 44 for MSI/MSI-X
    full dmesg output:
    [ 0.000000] Initializing cgroup subsys cpuset
    [ 0.000000] Initializing cgroup subsys cpu
    [ 0.000000] Linux version 3.6.2-1-ARCH (tobias@testing) (gcc version 4.7.2 (GCC) ) #1 SMP PREEMPT Sat Oct 13 07:19:40 CEST 2012
    [ 0.000000] Disabled fast string operations
    [ 0.000000] e820: BIOS-provided physical RAM map:
    [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
    [ 0.000000] BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000000d2000-0x00000000000d3fff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000000dc000-0x00000000000fffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000007f6cffff] usable
    [ 0.000000] BIOS-e820: [mem 0x000000007f6d0000-0x000000007f6defff] ACPI data
    [ 0.000000] BIOS-e820: [mem 0x000000007f6df000-0x000000007f6fffff] ACPI NVS
    [ 0.000000] BIOS-e820: [mem 0x000000007f700000-0x000000007fffffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000f0000000-0x00000000f3ffffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec0ffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed003ff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000fed14000-0x00000000fed19fff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed8ffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000ff800000-0x00000000ffffffff] reserved
    [ 0.000000] Notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel!
    [ 0.000000] DMI present.
    [ 0.000000] DMI: LENOVO 17033WG/17033WG, BIOS 7BETD7WW (2.18 ) 11/20/2008
    [ 0.000000] e820: update [mem 0x00000000-0x0000ffff] usable ==> reserved
    [ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
    [ 0.000000] e820: last_pfn = 0x7f6d0 max_arch_pfn = 0x100000
    [ 0.000000] MTRR default type: uncachable
    [ 0.000000] MTRR fixed ranges enabled:
    [ 0.000000] 00000-9FFFF write-back
    [ 0.000000] A0000-BFFFF uncachable
    [ 0.000000] C0000-CFFFF write-protect
    [ 0.000000] D0000-DBFFF uncachable
    [ 0.000000] DC000-DFFFF write-back
    [ 0.000000] E0000-FFFFF write-protect
    [ 0.000000] MTRR variable ranges enabled:
    [ 0.000000] 0 base 000000000 mask F80000000 write-back
    [ 0.000000] 1 base 07F700000 mask FFFF00000 uncachable
    [ 0.000000] 2 base 07F800000 mask FFF800000 uncachable
    [ 0.000000] 3 disabled
    [ 0.000000] 4 disabled
    [ 0.000000] 5 disabled
    [ 0.000000] 6 disabled
    [ 0.000000] 7 disabled
    [ 0.000000] PAT not supported by CPU.
    [ 0.000000] found SMP MP-table at [mem 0x000f67f0-0x000f67ff] mapped at [c00f67f0]
    [ 0.000000] initial memory mapped: [mem 0x00000000-0x00bfffff]
    [ 0.000000] Base memory trampoline at [c009b000] 9b000 size 16384
    [ 0.000000] init_memory_mapping: [mem 0x00000000-0x377fdfff]
    [ 0.000000] [mem 0x00000000-0x003fffff] page 4k
    [ 0.000000] [mem 0x00400000-0x373fffff] page 2M
    [ 0.000000] [mem 0x37400000-0x377fdfff] page 4k
    [ 0.000000] kernel direct mapping tables up to 0x377fdfff @ [mem 0x00bfa000-0x00bfffff]
    [ 0.000000] RAMDISK: [mem 0x7f3ee000-0x7f6cefff]
    [ 0.000000] Allocated new RAMDISK: [mem 0x3751d000-0x377fd609]
    [ 0.000000] Move RAMDISK from [mem 0x7f3ee000-0x7f6ce609] to [mem 0x3751d000-0x377fd609]
    [ 0.000000] ACPI: RSDP 000f67c0 00024 (v02 LENOVO)
    [ 0.000000] ACPI: XSDT 7f6d179e 00094 (v01 LENOVO TP-7B 00002180 LTP 00000000)
    [ 0.000000] ACPI: FACP 7f6d1900 000F4 (v03 LENOVO TP-7B 00002180 LNVO 00000001)
    [ 0.000000] ACPI BIOS Bug: Warning: 32/64X length mismatch in FADT/Gpe1Block: 0/32 (20120711/tbfadt-567)
    [ 0.000000] ACPI BIOS Bug: Warning: Optional FADT field Gpe1Block has zero address or length: 0x000000000000102C/0x0 (20120711/tbfadt-598)
    [ 0.000000] ACPI: DSDT 7f6d1c90 0CFB9 (v01 LENOVO TP-7B 00002180 MSFT 0100000E)
    [ 0.000000] ACPI: FACS 7f6f4000 00040
    [ 0.000000] ACPI: SSDT 7f6d1ab4 001DC (v01 LENOVO TP-7B 00002180 MSFT 0100000E)
    [ 0.000000] ACPI: ECDT 7f6dec49 00052 (v01 LENOVO TP-7B 00002180 LNVO 00000001)
    [ 0.000000] ACPI: TCPA 7f6dec9b 00032 (v02 LENOVO TP-7B 00002180 LNVO 00000001)
    [ 0.000000] ACPI: APIC 7f6deccd 00068 (v01 LENOVO TP-7B 00002180 LNVO 00000001)
    [ 0.000000] ACPI: MCFG 7f6ded35 0003C (v01 LENOVO TP-7B 00002180 LNVO 00000001)
    [ 0.000000] ACPI: HPET 7f6ded71 00038 (v01 LENOVO TP-7B 00002180 LNVO 00000001)
    [ 0.000000] ACPI: SLIC 7f6dee62 00176 (v01 LENOVO TP-7B 00002180 LTP 00000000)
    [ 0.000000] ACPI: BOOT 7f6defd8 00028 (v01 LENOVO TP-7B 00002180 LTP 00000001)
    [ 0.000000] ACPI: SSDT 7f6f2645 0025F (v01 LENOVO TP-7B 00002180 INTL 20050513)
    [ 0.000000] ACPI: SSDT 7f6f28a4 000A6 (v01 LENOVO TP-7B 00002180 INTL 20050513)
    [ 0.000000] ACPI: SSDT 7f6f294a 004F7 (v01 LENOVO TP-7B 00002180 INTL 20050513)
    [ 0.000000] ACPI: SSDT 7f6f2e41 008BD (v01 LENOVO TP-7B 00002180 INTL 20050513)
    [ 0.000000] ACPI: SSDT 7f6f36fe 006AC (v01 LENOVO TP-7B 00002180 INTL 20050513)
    [ 0.000000] ACPI: Local APIC address 0xfee00000
    [ 0.000000] 1150MB HIGHMEM available.
    [ 0.000000] 887MB LOWMEM available.
    [ 0.000000] mapped low ram: 0 - 377fe000
    [ 0.000000] low ram: 0 - 377fe000
    [ 0.000000] Zone ranges:
    [ 0.000000] DMA [mem 0x00010000-0x00ffffff]
    [ 0.000000] Normal [mem 0x01000000-0x377fdfff]
    [ 0.000000] HighMem [mem 0x377fe000-0x7f6cffff]
    [ 0.000000] Movable zone start for each node
    [ 0.000000] Early memory node ranges
    [ 0.000000] node 0: [mem 0x00010000-0x0009efff]
    [ 0.000000] node 0: [mem 0x00100000-0x7f6cffff]
    [ 0.000000] On node 0 totalpages: 521823
    [ 0.000000] free_area_init_node: node 0, pgdat c064fec0, node_mem_map f652c200
    [ 0.000000] DMA zone: 32 pages used for memmap
    [ 0.000000] DMA zone: 0 pages reserved
    [ 0.000000] DMA zone: 3951 pages, LIFO batch:0
    [ 0.000000] Normal zone: 1744 pages used for memmap
    [ 0.000000] Normal zone: 221486 pages, LIFO batch:31
    [ 0.000000] HighMem zone: 2302 pages used for memmap
    [ 0.000000] HighMem zone: 292308 pages, LIFO batch:31
    [ 0.000000] Using APIC driver default
    [ 0.000000] ACPI: PM-Timer IO Port: 0x1008
    [ 0.000000] ACPI: Local APIC address 0xfee00000
    [ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
    [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
    [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
    [ 0.000000] ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
    [ 0.000000] IOAPIC[0]: apic_id 1, version 32, address 0xfec00000, GSI 0-23
    [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    [ 0.000000] ACPI: IRQ0 used by override.
    [ 0.000000] ACPI: IRQ2 used by override.
    [ 0.000000] ACPI: IRQ9 used by override.
    [ 0.000000] Using ACPI (MADT) for SMP configuration information
    [ 0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
    [ 0.000000] smpboot: Allowing 2 CPUs, 0 hotplug CPUs
    [ 0.000000] nr_irqs_gsi: 40
    [ 0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
    [ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000d2000
    [ 0.000000] PM: Registered nosave memory: 00000000000d2000 - 00000000000d4000
    [ 0.000000] PM: Registered nosave memory: 00000000000d4000 - 00000000000dc000
    [ 0.000000] PM: Registered nosave memory: 00000000000dc000 - 0000000000100000
    [ 0.000000] e820: [mem 0x80000000-0xefffffff] available for PCI devices
    [ 0.000000] Booting paravirtualized kernel on bare hardware
    [ 0.000000] setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:2 nr_node_ids:1
    [ 0.000000] PERCPU: Embedded 13 pages/cpu @f6506000 s32320 r0 d20928 u53248
    [ 0.000000] pcpu-alloc: s32320 r0 d20928 u53248 alloc=13*4096
    [ 0.000000] pcpu-alloc: [0] 0 [0] 1
    [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 517745
    [ 0.000000] Kernel command line: root=/dev/sda3 ro initrd=../initramfs-linux.img BOOT_IMAGE=../vmlinuz-linux
    [ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
    [ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
    [ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
    [ 0.000000] __ex_table already sorted, skipping sort
    [ 0.000000] Initializing CPU#0
    [ 0.000000] Initializing HighMem for node 0 (000377fe:0007f6d0)
    [ 0.000000] Memory: 2060116k/2087744k available (3939k kernel code, 27176k reserved, 1535k data, 532k init, 1178440k highmem)
    [ 0.000000] virtual kernel memory layout:
    fixmap : 0xfff16000 - 0xfffff000 ( 932 kB)
    pkmap : 0xff800000 - 0xffc00000 (4096 kB)
    vmalloc : 0xf7ffe000 - 0xff7fe000 ( 120 MB)
    lowmem : 0xc0000000 - 0xf77fe000 ( 887 MB)
    .init : 0xc0659000 - 0xc06de000 ( 532 kB)
    .data : 0xc04d8ff2 - 0xc0658f80 (1535 kB)
    .text : 0xc0100000 - 0xc04d8ff2 (3939 kB)
    [ 0.000000] Checking if this processor honours the WP bit even in supervisor mode...Ok.
    [ 0.000000] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
    [ 0.000000] Preemptible hierarchical RCU implementation.
    [ 0.000000] RCU dyntick-idle grace-period acceleration is enabled.
    [ 0.000000] Dump stacks of tasks blocking RCU-preempt GP.
    [ 0.000000] RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=2.
    [ 0.000000] NR_IRQS:2304 nr_irqs:512 16
    [ 0.000000] CPU 0 irqstacks, hard=f6008000 soft=f600a000
    [ 0.000000] Extended CMOS year: 2000
    [ 0.000000] Console: colour VGA+ 80x25
    [ 0.000000] console [tty0] enabled
    [ 0.000000] hpet clockevent registered
    [ 0.000000] tsc: Fast TSC calibration using PIT
    [ 0.000000] tsc: Detected 1662.621 MHz processor
    [ 0.003335] Calibrating delay loop (skipped), value calculated using timer frequency.. 3326.79 BogoMIPS (lpj=5542070)
    [ 0.003340] pid_max: default: 32768 minimum: 301
    [ 0.003381] Security Framework initialized
    [ 0.003387] AppArmor: AppArmor disabled by boot time parameter
    [ 0.003409] Mount-cache hash table entries: 512
    [ 0.003722] Initializing cgroup subsys cpuacct
    [ 0.003725] Initializing cgroup subsys devices
    [ 0.003728] Initializing cgroup subsys freezer
    [ 0.003730] Initializing cgroup subsys net_cls
    [ 0.003733] Initializing cgroup subsys blkio
    [ 0.003766] Disabled fast string operations
    [ 0.003772] CPU: Physical Processor ID: 0
    [ 0.003774] CPU: Processor Core ID: 0
    [ 0.003777] mce: CPU supports 6 MCE banks
    [ 0.003788] CPU0: Thermal monitoring enabled (TM2)
    [ 0.003792] process: using mwait in idle threads
    [ 0.003803] Last level iTLB entries: 4KB 128, 2MB 0, 4MB 2
    Last level dTLB entries: 4KB 128, 2MB 0, 4MB 8
    tlb_flushall_shift is 0x6
    [ 0.007811] ACPI: Core revision 20120711
    [ 0.020011] ftrace: allocating 17289 entries in 34 pages
    [ 0.030073] Enabling APIC mode: Flat. Using 1 I/O APICs
    [ 0.030544] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    [ 0.065739] smpboot: CPU0: Intel(R) Core(TM) Duo CPU L2400 @ 1.66GHz stepping 0c
    [ 0.066662] Performance Events: Core events, core PMU driver.
    [ 0.066662] ... version: 1
    [ 0.066662] ... bit width: 40
    [ 0.066662] ... generic registers: 2
    [ 0.066662] ... value mask: 000000ffffffffff
    [ 0.066662] ... max period: 000000007fffffff
    [ 0.066662] ... fixed-purpose events: 0
    [ 0.066662] ... event mask: 0000000000000003
    [ 0.090070] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
    [ 0.103341] CPU 1 irqstacks, hard=f60b8000 soft=f60ba000
    [ 0.103344] smpboot: Booting Node 0, Processors #1 OK
    [ 0.006666] Initializing CPU#1
    [ 0.006666] Disabled fast string operations
    [ 0.116462] TSC synchronization [CPU#0 -> CPU#1]:
    [ 0.116467] Measured 527230 cycles TSC warp between CPUs, turning off TSC clock.
    [ 0.116470] tsc: Marking TSC unstable due to check_tsc_sync_source failed
    [ 0.116510] Brought up 2 CPUs
    [ 0.116510] smpboot: Total of 2 processors activated (6653.58 BogoMIPS)
    [ 0.118215] devtmpfs: initialized
    [ 0.118215] PM: Registering ACPI NVS region [mem 0x7f6df000-0x7f6fffff] (135168 bytes)
    [ 0.118215] NET: Registered protocol family 16
    [ 0.118215] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
    [ 0.118215] ACPI: bus type pci registered
    [ 0.118215] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf0000000-0xf3ffffff] (base 0xf0000000)
    [ 0.118215] PCI: MMCONFIG at [mem 0xf0000000-0xf3ffffff] reserved in E820
    [ 0.118215] PCI: Using MMCONFIG for extended config space
    [ 0.118215] PCI: Using configuration type 1 for base access
    [ 0.120035] bio: create slab <bio-0> at 0
    [ 0.120066] ACPI: Added _OSI(Module Device)
    [ 0.120066] ACPI: Added _OSI(Processor Device)
    [ 0.120066] ACPI: Added _OSI(3.0 _SCP Extensions)
    [ 0.120066] ACPI: Added _OSI(Processor Aggregator Device)
    [ 0.121079] ACPI: EC: EC description table is found, configuring boot EC
    [ 0.137147] ACPI: SSDT 7f6f1d26 00240 (v01 PmRef Cpu0Ist 00000100 INTL 20050513)
    [ 0.137827] ACPI: Dynamic OEM Table Load:
    [ 0.137831] ACPI: SSDT (null) 00240 (v01 PmRef Cpu0Ist 00000100 INTL 20050513)
    [ 0.138031] ACPI: SSDT 7f6f1feb 0065A (v01 PmRef Cpu0Cst 00000100 INTL 20050513)
    [ 0.138742] ACPI: Dynamic OEM Table Load:
    [ 0.138746] ACPI: SSDT (null) 0065A (v01 PmRef Cpu0Cst 00000100 INTL 20050513)
    [ 0.138765] ACPI: SSDT 7f6f1c5e 000C8 (v01 PmRef Cpu1Ist 00000100 INTL 20050513)
    [ 0.138765] ACPI: Dynamic OEM Table Load:
    [ 0.138765] ACPI: SSDT (null) 000C8 (v01 PmRef Cpu1Ist 00000100 INTL 20050513)
    [ 0.138765] ACPI: SSDT 7f6f1f66 00085 (v01 PmRef Cpu1Cst 00000100 INTL 20050513)
    [ 0.138765] ACPI: Dynamic OEM Table Load:
    [ 0.138765] ACPI: SSDT (null) 00085 (v01 PmRef Cpu1Cst 00000100 INTL 20050513)
    [ 0.140232] ACPI: Interpreter enabled
    [ 0.140241] ACPI: (supports S0 S3 S4 S5)
    [ 0.140264] ACPI: Using IOAPIC for interrupt routing
    [ 0.144225] ACPI: Power Resource [PUBS] (on)
    [ 0.150588] ACPI: EC: GPE = 0x1c, I/O: command/status = 0x66, data = 0x62
    [ 0.151210] ACPI: ACPI Dock Station Driver: 4 docks/bays found
    [ 0.151210] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
    [ 0.151459] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
    [ 0.151500] pci_root PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge
    [ 0.151549] PCI host bridge to bus 0000:00
    [ 0.151555] pci_bus 0000:00: busn_res: [bus 00-ff] is inserted under domain [bus 00-ff]
    [ 0.151558] pci_bus 0000:00: root bus resource [bus 00-ff]
    [ 0.151562] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
    [ 0.151566] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
    [ 0.151569] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
    [ 0.151573] pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff]
    [ 0.151576] pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff]
    [ 0.151580] pci_bus 0000:00: root bus resource [mem 0x80000000-0xfebfffff]
    [ 0.151594] pci 0000:00:00.0: [8086:27a0] type 00 class 0x060000
    [ 0.151650] pci 0000:00:02.0: [8086:27a2] type 00 class 0x030000
    [ 0.151665] pci 0000:00:02.0: reg 10: [mem 0xee100000-0xee17ffff]
    [ 0.151674] pci 0000:00:02.0: reg 14: [io 0x1800-0x1807]
    [ 0.151682] pci 0000:00:02.0: reg 18: [mem 0xd0000000-0xdfffffff pref]
    [ 0.151690] pci 0000:00:02.0: reg 1c: [mem 0xee200000-0xee23ffff]
    [ 0.151738] pci 0000:00:02.1: [8086:27a6] type 00 class 0x038000
    [ 0.151750] pci 0000:00:02.1: reg 10: [mem 0xee180000-0xee1fffff]
    [ 0.153358] pci 0000:00:1b.0: [8086:27d8] type 00 class 0x040300
    [ 0.153383] pci 0000:00:1b.0: reg 10: [mem 0xee240000-0xee243fff 64bit]
    [ 0.153490] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
    [ 0.153525] pci 0000:00:1c.0: [8086:27d0] type 01 class 0x060400
    [ 0.153638] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
    [ 0.153676] pci 0000:00:1c.1: [8086:27d2] type 01 class 0x060400
    [ 0.153789] pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
    [ 0.153831] pci 0000:00:1c.2: [8086:27d4] type 01 class 0x060400
    [ 0.153944] pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
    [ 0.153981] pci 0000:00:1c.3: [8086:27d6] type 01 class 0x060400
    [ 0.154095] pci 0000:00:1c.3: PME# supported from D0 D3hot D3cold
    [ 0.154133] pci 0000:00:1d.0: [8086:27c8] type 00 class 0x0c0300
    [ 0.154191] pci 0000:00:1d.0: reg 20: [io 0x1820-0x183f]
    [ 0.154236] pci 0000:00:1d.1: [8086:27c9] type 00 class 0x0c0300
    [ 0.154293] pci 0000:00:1d.1: reg 20: [io 0x1840-0x185f]
    [ 0.154338] pci 0000:00:1d.2: [8086:27ca] type 00 class 0x0c0300
    [ 0.154396] pci 0000:00:1d.2: reg 20: [io 0x1860-0x187f]
    [ 0.154441] pci 0000:00:1d.3: [8086:27cb] type 00 class 0x0c0300
    [ 0.154499] pci 0000:00:1d.3: reg 20: [io 0x1880-0x189f]
    [ 0.154556] pci 0000:00:1d.7: [8086:27cc] type 00 class 0x0c0320
    [ 0.154582] pci 0000:00:1d.7: reg 10: [mem 0xee444000-0xee4443ff]
    [ 0.154690] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
    [ 0.154720] pci 0000:00:1e.0: [8086:2448] type 01 class 0x060401
    [ 0.154823] pci 0000:00:1f.0: [8086:27b9] type 00 class 0x060100
    [ 0.154939] pci 0000:00:1f.0: quirk: [io 0x1000-0x107f] claimed by ICH6 ACPI/GPIO/TCO
    [ 0.154947] pci 0000:00:1f.0: quirk: [io 0x1180-0x11bf] claimed by ICH6 GPIO
    [ 0.154953] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 1600 (mask 007f)
    [ 0.154958] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 2 PIO at 15e0 (mask 000f)
    [ 0.154964] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 3 PIO at 1680 (mask 001f)
    [ 0.155030] pci 0000:00:1f.2: [8086:27c4] type 00 class 0x010180
    [ 0.155052] pci 0000:00:1f.2: reg 10: [io 0x0000-0x0007]
    [ 0.155066] pci 0000:00:1f.2: reg 14: [io 0x0000-0x0003]
    [ 0.155079] pci 0000:00:1f.2: reg 18: [io 0x0000-0x0007]
    [ 0.155092] pci 0000:00:1f.2: reg 1c: [io 0x0000-0x0003]
    [ 0.155105] pci 0000:00:1f.2: reg 20: [io 0x18b0-0x18bf]
    [ 0.155164] pci 0000:00:1f.2: PME# supported from D3hot
    [ 0.155187] pci 0000:00:1f.3: [8086:27da] type 00 class 0x0c0500
    [ 0.155262] pci 0000:00:1f.3: reg 20: [io 0x18e0-0x18ff]
    [ 0.155375] pci_bus 0000:02: busn_res: [bus 02] is inserted under [bus 00-ff]
    [ 0.155475] pci 0000:02:00.0: [8086:109a] type 00 class 0x020000
    [ 0.155508] pci 0000:02:00.0: reg 10: [mem 0xee000000-0xee01ffff]
    [ 0.155551] pci 0000:02:00.0: reg 18: [io 0x2000-0x201f]
    [ 0.155736] pci 0000:02:00.0: PME# supported from D0 D3hot D3cold
    [ 0.160078] pci 0000:00:1c.0: PCI bridge to [bus 02]
    [ 0.160084] pci 0000:00:1c.0: bridge window [io 0x2000-0x2fff]
    [ 0.160091] pci 0000:00:1c.0: bridge window [mem 0xee000000-0xee0fffff]
    [ 0.160159] pci_bus 0000:03: busn_res: [bus 03] is inserted under [bus 00-ff]
    [ 0.160190] pci 0000:03:00.0: [168c:1014] type 00 class 0x020000
    [ 0.160224] pci 0000:03:00.0: reg 10: [mem 0xedf00000-0xedf0ffff 64bit]
    [ 0.166676] pci 0000:00:1c.1: PCI bridge to [bus 03]
    [ 0.166683] pci 0000:00:1c.1: bridge window [io 0x3000-0x4fff]
    [ 0.166689] pci 0000:00:1c.1: bridge window [mem 0xec000000-0xedffffff]
    [ 0.166699] pci 0000:00:1c.1: bridge window [mem 0xe4000000-0xe40fffff 64bit pref]
    [ 0.166761] pci_bus 0000:04: busn_res: [bus 04-0b] is inserted under [bus 00-ff]
    [ 0.166766] pci 0000:00:1c.2: PCI bridge to [bus 04-0b]
    [ 0.166772] pci 0000:00:1c.2: bridge window [io 0x5000-0x6fff]
    [ 0.166779] pci 0000:00:1c.2: bridge window [mem 0xe8000000-0xe9ffffff]
    [ 0.166788] pci 0000:00:1c.2: bridge window [mem 0xe4100000-0xe41fffff 64bit pref]
    [ 0.166850] pci_bus 0000:0c: busn_res: [bus 0c-13] is inserted under [bus 00-ff]
    [ 0.166855] pci 0000:00:1c.3: PCI bridge to [bus 0c-13]
    [ 0.166862] pci 0000:00:1c.3: bridge window [io 0x7000-0x8fff]
    [ 0.166868] pci 0000:00:1c.3: bridge window [mem 0xea000000-0xebffffff]
    [ 0.166877] pci 0000:00:1c.3: bridge window [mem 0xe4200000-0xe42fffff 64bit pref]
    [ 0.166912] pci_bus 0000:15: busn_res: [bus 15-18] is inserted under [bus 00-ff]
    [ 0.166929] pci 0000:15:00.0: [1180:0476] type 02 class 0x060700
    [ 0.166955] pci 0000:15:00.0: reg 10: [mem 0xe4300000-0xe4300fff]
    [ 0.166994] pci 0000:15:00.0: supports D1 D2
    [ 0.166998] pci 0000:15:00.0: PME# supported from D0 D1 D2 D3hot D3cold
    [ 0.167024] pci 0000:15:00.1: [1180:0552] type 00 class 0x0c0010
    [ 0.167049] pci 0000:15:00.1: reg 10: [mem 0xe4301000-0xe43017ff]
    [ 0.167150] pci 0000:15:00.1: PME# supported from D0 D3hot D3cold
    [ 0.167176] pci 0000:15:00.2: [1180:0822] type 00 class 0x080500
    [ 0.167199] pci 0000:15:00.2: reg 10: [mem 0xe4301800-0xe43018ff]
    [ 0.167303] pci 0000:15:00.2: supports D1 D2
    [ 0.167307] pci 0000:15:00.2: PME# supported from D0 D1 D2 D3hot D3cold
    [ 0.167388] pci 0000:00:1e.0: PCI bridge to [bus 15-18] (subtractive decode)
    [ 0.167395] pci 0000:00:1e.0: bridge window [io 0x9000-0xcfff]
    [ 0.167401] pci 0000:00:1e.0: bridge window [mem 0xe4300000-0xe7ffffff]
    [ 0.167410] pci 0000:00:1e.0: bridge window [mem 0xe0000000-0xe3ffffff 64bit pref]
    [ 0.167414] pci 0000:00:1e.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
    [ 0.167418] pci 0000:00:1e.0: bridge window [io 0x0d00-0xffff] (subtractive decode)
    [ 0.167421] pci 0000:00:1e.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
    [ 0.167425] pci 0000:00:1e.0: bridge window [mem 0x000d4000-0x000d7fff] (subtractive decode)
    [ 0.167428] pci 0000:00:1e.0: bridge window [mem 0x000d8000-0x000dbfff] (subtractive decode)
    [ 0.167432] pci 0000:00:1e.0: bridge window [mem 0x80000000-0xfebfffff] (subtractive decode)
    [ 0.167478] pci_bus 0000:16: busn_res: can not insert [bus 16-ff] under [bus 15-18] (conflicts with (null) [bus 15-18])
    [ 0.167485] pci_bus 0000:16: busn_res: [bus 16-ff] end is updated to 17
    [ 0.167488] pci_bus 0000:16: busn_res: [bus 16-17] is inserted under [bus 15-18]
    [ 0.167526] pci_bus 0000:00: on NUMA node 0
    [ 0.167531] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    [ 0.167642] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP0._PRT]
    [ 0.167684] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP1._PRT]
    [ 0.167724] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP2._PRT]
    [ 0.167771] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP3._PRT]
    [ 0.167818] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT]
    [ 0.168141] pci0000:00: Requesting ACPI _OSC control (0x1d)
    [ 0.168560] pci0000:00: ACPI _OSC control (0x1d) granted
    [ 0.173416] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11)
    [ 0.173512] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 *11)
    [ 0.173605] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 *11)
    [ 0.173698] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 *11)
    [ 0.173791] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 *11)
    [ 0.173884] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 *11)
    [ 0.173977] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 9 10 *11)
    [ 0.174070] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 10 *11)
    [ 0.174153] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
    [ 0.174153] vgaarb: loaded
    [ 0.174153] vgaarb: bridge control possible 0000:00:02.0
    [ 0.174153] PCI: Using ACPI for IRQ routing
    [ 0.176770] PCI: pci_cache_line_size set to 64 bytes
    [ 0.176881] e820: reserve RAM buffer [mem 0x0009f000-0x0009ffff]
    [ 0.176884] e820: reserve RAM buffer [mem 0x7f6d0000-0x7fffffff]
    [ 0.177040] NetLabel: Initializing
    [ 0.177042] NetLabel: domain hash size = 128
    [ 0.177044] NetLabel: protocols = UNLABELED CIPSOv4
    [ 0.177062] NetLabel: unlabeled traffic allowed by default
    [ 0.177096] HPET: 3 timers in total, 0 timers will be used for per-cpu timer
    [ 0.177103] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
    [ 0.177110] hpet0: 3 comparators, 64-bit 14.318180 MHz counter
    [ 0.193342] Switching to clocksource hpet
    [ 0.202830] pnp: PnP ACPI init
    [ 0.202861] ACPI: bus type pnp registered
    [ 0.203474] pnp 00:00: [mem 0x00000000-0x0009ffff]
    [ 0.203478] pnp 00:00: [mem 0x000c0000-0x000c3fff]
    [ 0.203481] pnp 00:00: [mem 0x000c4000-0x000c7fff]
    [ 0.203485] pnp 00:00: [mem 0x000c8000-0x000cbfff]
    [ 0.203488] pnp 00:00: [mem 0x000cc000-0x000cffff]
    [ 0.203491] pnp 00:00: [mem 0x000d0000-0x000d3fff]
    [ 0.203495] pnp 00:00: [mem 0x000d4000-0x000d3fff disabled]
    [ 0.203498] pnp 00:00: [mem 0x000d8000-0x000d7fff disabled]
    [ 0.203501] pnp 00:00: [mem 0x000dc000-0x000dffff]
    [ 0.203504] pnp 00:00: [mem 0x000e0000-0x000e3fff]
    [ 0.203508] pnp 00:00: [mem 0x000e4000-0x000e7fff]
    [ 0.203511] pnp 00:00: [mem 0x000e8000-0x000ebfff]
    [ 0.203514] pnp 00:00: [mem 0x000ec000-0x000effff]
    [ 0.203517] pnp 00:00: [mem 0x000f0000-0x000fffff]
    [ 0.203521] pnp 00:00: [mem 0x00100000-0x7fffffff]
    [ 0.203524] pnp 00:00: [mem 0xfec00000-0xffffffff]
    [ 0.203527] pnp 00:00: [mem 0xfed41000-0xfed40fff disabled]
    [ 0.203626] system 00:00: [mem 0x00000000-0x0009ffff] could not be reserved
    [ 0.203631] system 00:00: [mem 0x000c0000-0x000c3fff] could not be reserved
    [ 0.203635] system 00:00: [mem 0x000c4000-0x000c7fff] could not be reserved
    [ 0.203639] system 00:00: [mem 0x000c8000-0x000cbfff] has been reserved
    [ 0.203643] system 00:00: [mem 0x000cc000-0x000cffff] could not be reserved
    [ 0.203647] system 00:00: [mem 0x000d0000-0x000d3fff] could not be reserved
    [ 0.203651] system 00:00: [mem 0x000dc000-0x000dffff] could not be reserved
    [ 0.203655] system 00:00: [mem 0x000e0000-0x000e3fff] could not be reserved
    [ 0.203659] system 00:00: [mem 0x000e4000-0x000e7fff] could not be reserved
    [ 0.203663] system 00:00: [mem 0x000e8000-0x000ebfff] could not be reserved
    [ 0.203667] system 00:00: [mem 0x000ec000-0x000effff] could not be reserved
    [ 0.203671] system 00:00: [mem 0x000f0000-0x000fffff] could not be reserved
    [ 0.203675] system 00:00: [mem 0x00100000-0x7fffffff] could not be reserved
    [ 0.203679] system 00:00: [mem 0xfec00000-0xffffffff] could not be reserved
    [ 0.203685] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
    [ 0.203717] pnp 00:01: [bus 00-ff]
    [ 0.203721] pnp 00:01: [io 0x0cf8-0x0cff]
    [ 0.203725] pnp 00:01: [io 0x0000-0x0cf7 window]
    [ 0.203728] pnp 00:01: [io 0x0d00-0xffff window]
    [ 0.203732] pnp 00:01: [mem 0x000a0000-0x000bffff window]
    [ 0.203735] pnp 00:01: [mem 0x000c0000-0x000c3fff window]
    [ 0.203739] pnp 00:01: [mem 0x000c4000-0x000c7fff window]
    [ 0.203742] pnp 00:01: [mem 0x000c8000-0x000cbfff window]
    [ 0.203745] pnp 00:01: [mem 0x000cc000-0x000cffff window]
    [ 0.203749] pnp 00:01: [mem 0x000d0000-0x000d3fff window]
    [ 0.203752] pnp 00:01: [mem 0x000d4000-0x000d7fff window]
    [ 0.203755] pnp 00:01: [mem 0x000d8000-0x000dbfff window]
    [ 0.203759] pnp 00:01: [mem 0x000dc000-0x000dffff window]
    [ 0.203762] pnp 00:01: [mem 0x000e0000-0x000e3fff window]
    [ 0.203769] pnp 00:01: [mem 0x000e4000-0x000e7fff window]
    [ 0.203772] pnp 00:01: [mem 0x000e8000-0x000ebfff window]
    [ 0.203776] pnp 00:01: [mem 0x000ec000-0x000effff window]
    [ 0.203779] pnp 00:01: [mem 0x80000000-0xfebfffff window]
    [ 0.203783] pnp 00:01: [mem 0xfed40000-0xfed40fff window]
    [ 0.203856] pnp 00:01: Plug and Play ACPI device, IDs PNP0a08 PNP0a03 (active)
    [ 0.203954] pnp 00:02: [io 0x0010-0x001f]
    [ 0.203958] pnp 00:02: [io 0x0090-0x009f]
    [ 0.203961] pnp 00:02: [io 0x0024-0x0025]
    [ 0.203964] pnp 00:02: [io 0x0028-0x0029]
    [ 0.203968] pnp 00:02: [io 0x002c-0x002d]
    [ 0.203971] pnp 00:02: [io 0x0030-0x0031]
    [ 0.203974] pnp 00:02: [io 0x0034-0x0035]
    [ 0.203977] pnp 00:02: [io 0x0038-0x0039]
    [ 0.203980] pnp 00:02: [io 0x003c-0x003d]
    [ 0.203983] pnp 00:02: [io 0x00a4-0x00a5]
    [ 0.203986] pnp 00:02: [io 0x00a8-0x00a9]
    [ 0.203989] pnp 00:02: [io 0x00ac-0x00ad]
    [ 0.203992] pnp 00:02: [io 0x00b0-0x00b5]
    [ 0.203996] pnp 00:02: [io 0x00b8-0x00b9]
    [ 0.203999] pnp 00:02: [io 0x00bc-0x00bd]
    [ 0.204002] pnp 00:02: [io 0x0050-0x0053]
    [ 0.204005] pnp 00:02: [io 0x0072-0x0077]
    [ 0.204008] pnp 00:02: [io 0x164e-0x164f]
    [ 0.204011] pnp 00:02: [io 0x002e-0x002f]
    [ 0.204014] pnp 00:02: [io 0x1000-0x107f]
    [ 0.204018] pnp 00:02: [io 0x1180-0x11bf]
    [ 0.204021] pnp 00:02: [io 0x0800-0x080f]
    [ 0.204024] pnp 00:02: [io 0x15e0-0x15ef]
    [ 0.204027] pnp 00:02: [io 0x1600-0x165f]
    [ 0.204030] pnp 00:02: [mem 0xf0000000-0xf3ffffff]
    [ 0.204034] pnp 00:02: [mem 0xfed1c000-0xfed1ffff]
    [ 0.204037] pnp 00:02: [mem 0xfed14000-0xfed17fff]
    [ 0.204040] pnp 00:02: [mem 0xfed18000-0xfed18fff]
    [ 0.204044] pnp 00:02: [mem 0xfed19000-0xfed19fff]
    [ 0.204047] pnp 00:02: [mem 0xfed40000-0xfed40fff]
    [ 0.204158] system 00:02: [io 0x164e-0x164f] has been reserved
    [ 0.204162] system 00:02: [io 0x1000-0x107f] has been reserved
    [ 0.204166] system 00:02: [io 0x1180-0x11bf] has been reserved
    [ 0.204170] system 00:02: [io 0x0800-0x080f] has been reserved
    [ 0.204174] system 00:02: [io 0x15e0-0x15ef] has been reserved
    [ 0.204178] system 00:02: [io 0x1600-0x165f] could not be reserved
    [ 0.204183] system 00:02: [mem 0xf0000000-0xf3ffffff] has been reserved
    [ 0.204187] system 00:02: [mem 0xfed1c000-0xfed1ffff] has been reserved
    [ 0.204191] system 00:02: [mem 0xfed14000-0xfed17fff] has been reserved
    [ 0.204195] system 00:02: [mem 0xfed18000-0xfed18fff] has been reserved
    [ 0.204200] system 00:02: [mem 0xfed19000-0xfed19fff] has been reserved
    [ 0.204204] system 00:02: [mem 0xfed40000-0xfed40fff] has been reserved
    [ 0.204210] system 00:02: Plug and Play ACPI device, IDs PNP0c02 (active)
    [ 0.204257] pnp 00:03: [mem 0xfed00000-0xfed003ff]
    [ 0.204297] pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active)
    [ 0.204310] pnp 00:04: [io 0x0000-0x000f]
    [ 0.204314] pnp 00:04: [io 0x0080-0x008f]
    [ 0.204317] pnp 00:04: [io 0x00c0-0x00df]
    [ 0.204320] pnp 00:04: [dma 4]
    [ 0.204359] pnp 00:04: Plug and Play ACPI device, IDs PNP0200 (active)
    [ 0.204371] pnp 00:05: [io 0x0061]
    [ 0.204415] pnp 00:05: Plug and Play ACPI device, IDs PNP0800 (active)
    [ 0.204430] pnp 00:06: [io 0x00f0]
    [ 0.204445] pnp 00:06: [irq 13]
    [ 0.204485] pnp 00:06: Plug and Play ACPI device, IDs PNP0c04 (active)
    [ 0.204498] pnp 00:07: [io 0x0070-0x0071]
    [ 0.204505] pnp 00:07: [irq 8]
    [ 0.204546] pnp 00:07: Plug and Play ACPI device, IDs PNP0b00 (active)
    [ 0.204559] pnp 00:08: [io 0x0060]
    [ 0.204562] pnp 00:08: [io 0x0064]
    [ 0.204569] pnp 00:08: [irq 1]
    [ 0.204613] pnp 00:08: Plug and Play ACPI device, IDs PNP0303 (active)
    [ 0.204629] pnp 00:09: [irq 12]
    [ 0.204672] pnp 00:09: Plug and Play ACPI device, IDs IBM3780 PNP0f13 (active)
    [ 0.204819] pnp 00:0a: Plug and Play ACPI device, IDs PNP0501 (disabled)
    [ 0.204951] pnp 00:0b: Plug and Play ACPI device, IDs PNP0400 (disabled)
    [ 0.205120] pnp 00:0c: Plug and Play ACPI device, IDs IBM0071 PNP0511 (disabled)
    [ 0.206014] pnp: PnP ACPI: found 13 devices
    [ 0.206017] ACPI: ACPI bus type pnp unregistered
    [ 0.244152] pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 02] add_size 200000
    [ 0.244204] pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_size add_size 200000
    [ 0.244213] pci 0000:00:1c.0: BAR 15: assigned [mem 0x80000000-0x801fffff 64bit pref]
    [ 0.244218] pci 0000:00:1c.0: PCI bridge to [bus 02]
    [ 0.244224] pci 0000:00:1c.0: bridge window [io 0x2000-0x2fff]
    [ 0.244231] pci 0000:00:1c.0: bridge window [mem 0xee000000-0xee0fffff]
    [ 0.244238] pci 0000:00:1c.0: bridge window [mem 0x80000000-0x801fffff 64bit pref]
    [ 0.244247] pci 0000:00:1c.1: PCI bridge to [bus 03]
    [ 0.244252] pci 0000:00:1c.1: bridge window [io 0x3000-0x4fff]
    [ 0.244260] pci 0000:00:1c.1: bridge window [mem 0xec000000-0xedffffff]
    [ 0.244266] pci 0000:00:1c.1: bridge window [mem 0xe4000000-0xe40fffff 64bit pref]
    [ 0.244275] pci 0000:00:1c.2: PCI bridge to [bus 04-0b]
    [ 0.244280] pci 0000:00:1c.2: bridge window [io 0x5000-0x6fff]
    [ 0.244288] pci 0000:00:1c.2: bridge window [mem 0xe8000000-0xe9ffffff]
    [ 0.244294] pci 0000:00:1c.2: bridge window [mem 0xe4100000-0xe41fffff 64bit pref]
    [ 0.244303] pci 0000:00:1c.3: PCI bridge to [bus 0c-13]
    [ 0.244308] pci 0000:00:1c.3: bridge window [io 0x7000-0x8fff]
    [ 0.244316] pci 0000:00:1c.3: bridge window [mem 0xea000000-0xebffffff]
    [ 0.244322] pci 0000:00:1c.3: bridge window [mem 0xe4200000-0xe42fffff 64bit pref]
    [ 0.244334] pci 0000:15:00.0: res[15]=[mem 0x04000000-0x03ffffff pref] get_res_add_size add_size 4000000
    [ 0.244338] pci 0000:15:00.0: res[16]=[mem 0x04000000-0x03ffffff] get_res_add_size add_size 4000000
    [ 0.244342] pci 0000:15:00.0: res[13]=[io 0x0100-0x00ff] get_res_add_size add_size 100
    [ 0.244346] pci 0000:15:00.0: res[14]=[io 0x0100-0x00ff] get_res_add_size add_size 100
    [ 0.244350] pci 0000:15:00.0: BAR 15: assigned [mem 0xe0000000-0xe3ffffff pref]
    [ 0.244355] pci 0000:15:00.0: BAR 16: assigned [mem 0x84000000-0x87ffffff]
    [ 0.244359] pci 0000:15:00.0: BAR 13: assigned [io 0x9000-0x90ff]
    [ 0.244363] pci 0000:15:00.0: BAR 14: assigned [io 0x9400-0x94ff]
    [ 0.244367] pci 0000:15:00.0: CardBus bridge to [bus 16-17]
    [ 0.244371] pci 0000:15:00.0: bridge window [io 0x9000-0x90ff]
    [ 0.244377] pci 0000:15:00.0: bridge window [io 0x9400-0x94ff]
    [ 0.244383] pci 0000:15:00.0: bridge window [mem 0xe0000000-0xe3ffffff pref]
    [ 0.244389] pci 0000:15:00.0: bridge window [mem 0x84000000-0x87ffffff]
    [ 0.244396] pci 0000:00:1e.0: PCI bridge to [bus 15-18]
    [ 0.244401] pci 0000:00:1e.0: bridge window [io 0x9000-0xcfff]
    [ 0.244408] pci 0000:00:1e.0: bridge window [mem 0xe4300000-0xe7ffffff]
    [ 0.244415] pci 0000:00:1e.0: bridge window [mem 0xe0000000-0xe3ffffff 64bit pref]
    [ 0.244474] pci 0000:00:1e.0: enabling device (0005 -> 0007)
    [ 0.244482] pci 0000:00:1e.0: setting latency timer to 64
    [ 0.244501] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
    [ 0.244504] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
    [ 0.244508] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
    [ 0.244511] pci_bus 0000:00: resource 7 [mem 0x000d4000-0x000d7fff]
    [ 0.244514] pci_bus 0000:00: resource 8 [mem 0x000d8000-0x000dbfff]
    [ 0.244518] pci_bus 0000:00: resource 9 [mem 0x80000000-0xfebfffff]
    [ 0.244522] pci_bus 0000:02: resource 0 [io 0x2000-0x2fff]
    [ 0.244525] pci_bus 0000:02: resource 1 [mem 0xee000000-0xee0fffff]
    [ 0.244529] pci_bus 0000:02: resource 2 [mem 0x80000000-0x801fffff 64bit pref]
    [ 0.244532] pci_bus 0000:03: resource 0 [io 0x3000-0x4fff]
    [ 0.244536] pci_bus 0000:03: resource 1 [mem 0xec000000-0xedffffff]
    [ 0.244540] pci_bus 0000:03: resource 2 [mem 0xe4000000-0xe40fffff 64bit pref]
    [ 0.244543] pci_bus 0000:04: resource 0 [io 0x5000-0x6fff]
    [ 0.244547] pci_bus 0000:04: resource 1 [mem 0xe8000000-0xe9ffffff]
    [ 0.244550] pci_bus 0000:04: resource 2 [mem 0xe4100000-0xe41fffff 64bit pref]
    [ 0.244554] pci_bus 0000:0c: resource 0 [io 0x7000-0x8fff]
    [ 0.244557] pci_bus 0000:0c: resource 1 [mem 0xea000000-0xebffffff]
    [ 0.244561] pci_bus 0000:0c: resource 2 [mem 0xe4200000-0xe42fffff 64bit pref]
    [ 0.244564] pci_bus 0000:15: resource 0 [io 0x9000-0xcfff]
    [ 0.244568] pci_bus 0000:15: resource 1 [mem 0xe4300000-0xe7ffffff]
    [ 0.244572] pci_bus 0000:15: resource 2 [mem 0xe0000000-0xe3ffffff 64bit pref]
    [ 0.244575] pci_bus 0000:15: resource 4 [io 0x0000-0x0cf7]
    [ 0.244578] pci_bus 0000:15: resource 5 [io 0x0d00-0xffff]
    [ 0.244582] pci_bus 0000:15: resource 6 [mem 0x000a0000-0x000bffff]
    [ 0.244585] pci_bus 0000:15: resource 7 [mem 0x000d4000-0x000d7fff]
    [ 0.244589] pci_bus 0000:15: resource 8 [mem 0x000d8000-0x000dbfff]
    [ 0.244592] pci_bus 0000:15: resource 9 [mem 0x80000000-0xfebfffff]
    [ 0.244596] pci_bus 0000:16: resource 0 [io 0x9000-0x90ff]
    [ 0.244599] pci_bus 0000:16: resource 1 [io 0x9400-0x94ff]
    [ 0.244603] pci_bus 0000:16: resource 2 [mem 0xe0000000-0xe3ffffff pref]
    [ 0.244606] pci_bus 0000:16: resource 3 [mem 0x84000000-0x87ffffff]
    [ 0.244654] NET: Registered protocol family 2
    [ 0.244870] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
    [ 0.245648] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
    [ 0.246032] TCP: Hash tables configured (established 131072 bind 65536)
    [ 0.246064] TCP: reno registered
    [ 0.246068] UDP hash table entries: 512 (order: 2, 16384 bytes)
    [ 0.246079] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
    [ 0.246186] NET: Registered protocol family 1
    [ 0.246211] pci 0000:00:02.0: Boot video device
    [ 0.246246] pci 0000:00:1d.0: power state changed by ACPI to D0
    [ 0.246313] pci 0000:00:1d.2: power state changed by ACPI to D0
    [ 0.246432] PCI: CLS mismatch (64 != 32), using 64 bytes
    [ 0.246510] Unpacking initramfs...
    [ 0.343371] Freeing initrd memory: 2948k freed
    [ 0.345047] Simple Boot Flag at 0x35 set to 0x1
    [ 0.345220] apm: BIOS not found.
    [ 0.345590] audit: initializing netlink socket (disabled)
    [ 0.345613] type=2000 audit(1350565779.343:1): initialized
    [ 0.360319] bounce pool size: 64 pages
    [ 0.360336] HugeTLB registered 4 MB page size, pre-allocated 0 pages
    [ 0.362947] VFS: Disk quotas dquot_6.5.2
    [ 0.363023] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
    [ 0.363270] msgmni has been set to 1727
    [ 0.363612] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
    [ 0.363664] io scheduler noop registered
    [ 0.363667] io scheduler deadline registered
    [ 0.363679] io scheduler cfq registered (default)
    [ 0.363883] pcieport 0000:00:1c.0: irq 40 for MSI/MSI-X
    [ 0.364080] pcieport 0000:00:1c.1: irq 41 for MSI/MSI-X
    [ 0.364274] pcieport 0000:00:1c.2: irq 42 for MSI/MSI-X
    [ 0.364469] pcieport 0000:00:1c.3: irq 43 for MSI/MSI-X
    [ 0.364643] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
    [ 0.364647] pci 0000:02:00.0: Signaling PME through PCIe PME interrupt
    [ 0.364653] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
    [ 0.364680] pcieport 0000:00:1c.1: Signaling PME through PCIe PME interrupt
    [ 0.364683] pci 0000:03:00.0: Signaling PME through PCIe PME interrupt
    [ 0.364689] pcie_pme 0000:00:1c.1:pcie01: service driver pcie_pme loaded
    [ 0.364715] pcieport 0000:00:1c.2: Signaling PME through PCIe PME interrupt
    [ 0.364721] pcie_pme 0000:00:1c.2:pcie01: service driver pcie_pme loaded
    [ 0.364747] pcieport 0000:00:1c.3: Signaling PME through PCIe PME interrupt
    [ 0.364753] pcie_pme 0000:00:1c.3:pcie01: service driver pcie_pme loaded
    [ 0.364898] intel_idle: does not run on family 6 model 14
    [ 0.364936] GHES: HEST is not enabled!
    [ 0.364955] isapnp: Scanning for PnP cards...
    [ 0.721955] isapnp: No Plug & Play device found
    [ 0.722029] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    [ 0.722532] serial 00:0a: [io 0x03f8-0x03ff]
    [ 0.722605] serial 00:0a: [irq 4]
    [ 0.722938] serial 00:0a: activated
    [ 0.743734] 00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
    [ 0.744133] i8042: PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12
    [ 0.752722] serio: i8042 KBD port at 0x60,0x64 irq 1
    [ 0.752766] serio: i8042 AUX port at 0x60,0x64 irq 12
    [ 0.752919] mousedev: PS/2 mouse device common for all mice
    [ 0.753016] rtc_cmos 00:07: RTC can wake from S4
    [ 0.753202] rtc_cmos 00:07: rtc core: registered rtc_cmos as rtc0
    [ 0.753237] rtc0: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
    [ 0.753263] cpuidle: using governor ladder
    [ 0.753266] cpuidle: using governor menu
    [ 0.753419] drop_monitor: Initializing network drop monitor service
    [ 0.753557] TCP: cubic registered
    [ 0.753760] NET: Registered protocol family 10
    [ 0.754005] NET: Registered protocol family 17
    [ 0.754037] Key type dns_resolver registered
    [ 0.754232] Using IPI No-Shortcut mode
    [ 0.754391] PM: Hibernation image not present or could not be loaded.
    [ 0.754409] registered taskstats version 1
    [ 0.755066] rtc_cmos 00:07: setting system clock to 2012-10-18 13:09:40 UTC (1350565780)
    [ 0.755246] Freeing unused kernel memory: 532k freed
    [ 0.755574] Write protecting the kernel text: 3940k
    [ 0.755610] Write protecting the kernel read-only data: 1176k
    [ 0.757855] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
    [ 0.766785] systemd-udevd[42]: starting version 194
    [ 0.816138] ACPI: bus type usb registered
    [ 0.816184] usbcore: registered new interface driver usbfs
    [ 0.816202] usbcore: registered new interface driver hub
    [ 0.818130] usbcore: registered new device driver usb
    [ 0.819809] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    [ 0.819871] ehci_hcd 0000:00:1d.7: setting latency timer to 64
    [ 0.819877] ehci_hcd 0000:00:1d.7: EHCI Host Controller
    [ 0.819887] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
    [ 0.823207] SCSI subsystem initialized
    [ 0.823813] ehci_hcd 0000:00:1d.7: debug port 1
    [ 0.823825] ehci_hcd 0000:00:1d.7: cache line size of 64 is not supported
    [ 0.823853] ehci_hcd 0000:00:1d.7: irq 19, io mem 0xee444000
    [ 0.825386] uhci_hcd: USB Universal Host Controller Interface driver
    [ 0.826295] ACPI: bus type scsi registered
    [ 0.828011] libata version 3.00 loaded.
    [ 0.833623] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
    [ 0.833993] hub 1-0:1.0: USB hub found
    [ 0.834000] hub 1-0:1.0: 8 ports detected
    [ 0.834661] uhci_hcd 0000:00:1d.0: setting latency timer to 64
    [ 0.834667] uhci_hcd 0000:00:1d.0: UHCI Host Controller
    [ 0.834677] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
    [ 0.834728] uhci_hcd 0000:00:1d.0: irq 16, io base 0x00001820
    [ 0.835719] hub 2-0:1.0: USB hub found
    [ 0.835727] hub 2-0:1.0: 2 ports detected
    [ 0.835846] uhci_hcd 0000:00:1d.1: setting latency timer to 64
    [ 0.835851] uhci_hcd 0000:00:1d.1: UHCI Host Controller
    [ 0.835859] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
    [ 0.835908] uhci_hcd 0000:00:1d.1: irq 17, io base 0x00001840
    [ 0.836142] hub 3-0:1.0: USB hub found
    [ 0.836148] hub 3-0:1.0: 2 ports detected
    [ 0.836260] uhci_hcd 0000:00:1d.2: setting latency timer to 64
    [ 0.836265] uhci_hcd 0000:00:1d.2: UHCI Host Controller
    [ 0.836272] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
    [ 0.836314] uhci_hcd 0000:00:1d.2: irq 18, io base 0x00001860
    [ 0.836529] hub 4-0:1.0: USB hub found
    [ 0.836535] hub 4-0:1.0: 2 ports detected
    [ 0.836646] uhci_hcd 0000:00:1d.3: setting latency timer to 64
    [ 0.836651] uhci_hcd 0000:00:1d.3: UHCI Host Controller
    [ 0.836659] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
    [ 0.836720] uhci_hcd 0000:00:1d.3: irq 19, io base 0x00001880
    [ 0.837288] hub 5-0:1.0: USB hub found
    [ 0.837294] hub 5-0:1.0: 2 ports detected
    [ 0.837501] ata_piix 0000:00:1f.2: version 2.13
    [ 0.837518] ata_piix 0000:00:1f.2: MAP [
    [ 0.837520] P0 P2 IDE IDE ]
    [ 0.990043] ata_piix 0000:00:1f.2: setting latency timer to 64
    [ 0.990564] scsi0 : ata_piix
    [ 0.990932] scsi1 : ata_piix
    [ 0.991202] ata1: SATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0x18b0 irq 14
    [ 0.991205] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x18b8 irq 15
    [ 1.140030] usb 1-6: new high-speed USB device number 2 using ehci_hcd
    [ 1.150736] ata2.00: ATAPI: DVD-ROM UJDA775, DA03, max UDMA/33
    [ 1.151416] ata1.00: ATA-8: HITACHI HTS722010K9SA00, DC2ZC75A, max UDMA/133
    [ 1.151421] ata1.00: 195371568 sectors, multi 16: LBA48 NCQ (depth 0/32)
    [ 1.163946] ata2.00: configured for UDMA/33
    [ 1.164071] ata1.00: configured for UDMA/133
    [ 1.164253] scsi 0:0:0:0: Direct-Access ATA HITACHI HTS72201 DC2Z PQ: 0 ANSI: 5
    [ 1.178126] scsi 1:0:0:0: CD-ROM MATSHITA DVD-ROM UJDA775 DA03 PQ: 0 ANSI: 5
    [ 1.164562] ACPI: Invalid Power Resource to register!
    [ 1.178566] ACPI: Invalid Power Resource to register!
    [ 1.182312] sd 0:0:0:0: [sda] 195371568 512-byte logical blocks: (100 GB/93.1 GiB)
    [ 1.182385] sd 0:0:0:0: [sda] Write Protect is off
    [ 1.182389] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
    [ 1.182421] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [ 1.206975] sda: sda1 sda2 sda3 sda4
    [ 1.207544] sd 0:0:0:0: [sda] Attached SCSI disk
    [ 1.209920] sr0: scsi3-mmc drive: 24x/24x cd/rw xa/form2 cdda tray
    [ 1.209925] cdrom: Uniform CD-ROM driver Revision: 3.20
    [ 1.210342] sr 1:0:0:0: Attached scsi CD-ROM sr0
    [ 1.264015] hub 1-6:1.0: USB hub found
    [ 1.264154] hub 1-6:1.0: 4 ports detected
    [ 1.596700] usb 5-2: new full-speed USB device number 2 using uhci_hcd
    [ 1.635381] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
    [ 1.963410] usb 1-6.1: new high-speed USB device number 4 using ehci_hcd
    [ 2.060708] hub 1-6.1:1.0: USB hub found
    [ 2.060779] hub 1-6.1:1.0: 4 ports detected
    [ 2.340162] usb 1-6.1.3: new full-speed USB device number 5 using ehci_hcd
    [ 2.520161] usb 1-6.1.4: new full-speed USB device number 6 using ehci_hcd
    [ 2.938256] systemd-udevd[137]: starting version 194
    [ 3.357151] ACPI: Requesting acpi_cpufreq
    [ 3.372454] ACPI: acpi_idle registered with cpuidle
    [ 3.526218] fuse init (API version 7.20)
    [ 3.704869] FS-Cache: Loaded
    [ 3.758416] RPC: Registered named UNIX socket transport module.
    [ 3.758420] RPC: Registered udp transport module.
    [ 3.758422] RPC: Registered tcp transport module.
    [ 3.758424] RPC: Registered tcp NFSv4.1 backchannel transport module.
    [ 3.816566] FS-Cache: Netfs 'nfs' registered for caching
    [ 3.865161] input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input1
    [ 3.865514] ACPI: Lid Switch [LID]
    [ 3.868532] input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input2
    [ 3.868540] ACPI: Sleep Button [SLPB]
    [ 3.869184] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
    [ 3.869191] ACPI: Power Button [PWRF]
    [ 3.870237] acpi device:02: registered as cooling_device2
    [ 3.870293] ACPI: Video Device [VID] (multi-head: yes rom: no post: no)
    [ 3.870365] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input4
    [ 3.911351] NET: Registered protocol family 23
    [ 3.971349] ACPI: AC Adapter [AC] (on-line)
    [ 3.987220] ACPI: Battery Slot [BAT0] (battery present)
    [ 3.988310] thermal LNXTHERM:00: registered as thermal_zone0
    [ 3.988315] ACPI: Thermal Zone [THM0] (39 C)
    [ 3.990678] thermal LNXTHERM:01: registered as thermal_zone1
    [ 3.990683] ACPI: Thermal Zone [THM1] (40 C)
    [ 4.078721] Linux agpgart interface v0.103
    [ 4.121082] intel_rng: FWH not detected
    [ 4.156543] ACPI Warning: 0x00001028-0x0000102f SystemIO conflicts with Region \_SB_.PCI0.LPC_.PMIO 1 (20120711/utaddress-251)
    [ 4.156557] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
    [ 4.156565] ACPI Warning: 0x00001180-0x000011bf SystemIO conflicts with Region \_SB_.PCI0.LPC_.LPIO 1 (20120711/utaddress-251)
    [ 4.156575] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
    [ 4.156578] lpc_ich: Resource conflict(s) found affecting gpio_ich
    [ 4.168300] nsc-ircc 00:0c: [io 0x02f8-0x02ff]
    [ 4.168409] nsc-ircc 00:0c: [irq 3]
    [ 4.168416] nsc-ircc 00:0c: [dma 1]
    [ 4.169064] nsc-ircc 00:0c: activated
    [ 4.169126] nsc-ircc, chip->init
    [ 4.169142] nsc-ircc, Found chip at base=0x164e
    [ 4.169183] nsc-ircc, driver loaded (Dag Brattli)
    [ 4.169550] IrDA: Registered device irda0
    [ 4.169555] nsc-ircc, Using dongle: IBM31T1100 or Temic TFDS6000/TFDS6500
    [ 4.169647] nsc-ircc, chip->init
    [ 4.169669] nsc-ircc, Found chip at base=0x02e
    [ 4.169710] nsc-ircc, driver loaded (Dag Brattli)
    [ 4.169724] nsc_ircc_open(), can't get iobase of 0x2f8
    [ 4.281381] e1000e: Intel(R) PRO/1000 Network Driver - 2.0.0-k
    [ 4.281389] e1000e: Copyright(c) 1999 - 2012 Intel Corporation.
    [ 4.281450] e1000e 0000:02:00.0: Disabling ASPM L0s L1
    [ 4.281639] e1000e 0000:02:00.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
    [ 4.281744] e1000e 0000:02:00.0: irq 44 for MSI/MSI-X
    [ 4.288485] cfg80211: Calling CRDA to update world regulatory domain
    [ 4.352614] leds_ss4200: no LED devices found
    [ 4.364538] parport_pc 00:0b: [io 0x03bc-0x03be]
    [ 4.364625] parport_pc 00:0b: [irq 7]
    [ 4.365054] parport_pc 00:0b: activated
    [ 4.365059] parport_pc 00:0b: reported by Plug and Play ACPI
    [ 4.365117] parport0: PC-style at 0x3bc, irq 7 [PCSPP,TRISTATE]
    [ 4.371354] agpgart-intel 0000:00:00.0: Intel 945GM Chipset
    [ 4.371436] agpgart-intel 0000:00:00.0: detected gtt size: 262144K total, 262144K mappable
    [ 4.372020] agpgart-intel 0000:00:00.0: detected 8192K stolen memory
    [ 4.372693] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xd0000000
    [ 4.396917] e1000e 0000:02:00.0: eth0: (PCI Express:2.5GT/s:Width x1) 00:16:d3:3b:ac:45
    [ 4.396923] e1000e 0000:02:00.0: eth0: Intel(R) PRO/1000 Network Connection
    [ 4.397002] e1000e 0000:02:00.0: eth0: MAC: 2, PHY: 2, PBA No: 005302-003
    [ 4.491297] sdhci: Secure Digital Host Controller Interface driver
    [ 4.491304] sdhci: Copyright(c) Pierre Ossman
    [ 4.541025] ppdev: user-space parallel port driver
    [ 4.578786] iTCO_vendor_support: vendor-support=0
    [ 4.638121] i801_smbus 0000:00:1f.3: SMBus using PCI Interrupt
    [ 4.686186] yenta_cardbus 0000:15:00.0: CardBus bridge found [17aa:201c]
    [ 4.760660] Non-volatile memory driver v1.3
    [ 4.786377] psmouse serio1: hgpk: ID: 10 00 64
    [ 4.810789] yenta_cardbus 0000:15:00.0: ISA IRQ mask 0x0c30, PCI irq 16
    [ 4.810796] yenta_cardbus 0000:15:00.0: Socket status: 30000006
    [ 4.810809] yenta_cardbus 0000:15:00.0: pcmcia: parent PCI bridge window: [io 0x9000-0xcfff]
    [ 4.810815] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x9000-0xcfff:
    [ 4.812665] excluding 0x9000-0x90ff 0x9400-0x94ff
    [ 4.841676] yenta_cardbus 0000:15:00.0: pcmcia: parent PCI bridge window: [mem 0xe4300000-0xe7ffffff]
    [ 4.841682] pcmcia_socket pcmcia_socket0: cs: memory probe 0xe4300000-0xe7ffffff:
    [ 4.841686] excluding 0xe4300000-0xe46cffff
    [ 4.841702] yenta_cardbus 0000:15:00.0: pcmcia: parent PCI bridge window: [mem 0xe0000000-0xe3ffffff 64bit pref]
    [ 4.841706] pcmcia_socket pcmcia_socket0: cs: memory probe 0xe0000000-0xe3ffffff:
    [ 4.841721] excluding 0xe0000000-0xe3ffffff
    [ 4.871842] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10
    [ 4.871894] iTCO_wdt: Found a ICH7-M or ICH7-U TCO device (Version=2, TCOBASE=0x1060)
    [ 4.872464] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
    [ 4.980183] firewire_ohci 0000:15:00.1: added OHCI v1.0 device as card 0, 4 IR + 4 IT contexts, quirks 0x11
    [ 4.980529] sdhci-pci 0000:15:00.2: SDHCI controller found [1180:0822] (rev 18)
    [ 4.981592] sdhci-pci 0000:15:00.2: Will use DMA mode even though HW doesn't fully claim to support it.
    [ 4.981604] sdhci-pci 0000:15:00.2: setting latency timer to 64
    [ 4.982622] sdhci-pci 0000:15:00.2: Will use DMA mode even though HW doesn't fully claim to support it.
    [ 4.982702] Registered led device: mmc0::
    [ 5.008762] mmc0: SDHCI controller on PCI [0000:15:00.2] using DMA
    [ 5.017713] ath5k 0000:03:00.0: registered as 'phy0'
    [ 5.037476] sdhci-pci 0000:15:00.2: Will use DMA mode even though HW doesn't fully claim to support it.
    [ 5.058323] thinkpad_acpi: ThinkPad ACPI Extras v0.24
    [ 5.058330] thinkpad_acpi: http://ibm-acpi.sf.net/
    [ 5.058334] thinkpad_acpi: ThinkPad BIOS 7BETD7WW (2.18 ), EC 7BHT40WW-1.13
    [ 5.058337] thinkpad_acpi: Lenovo ThinkPad X60s, model 17033WG
    [ 5.060804] thinkpad_acpi: detected a 8-level brightness capable ThinkPad
    [ 5.061581] thinkpad_acpi: ACPI backlight control delay disabled
    [ 5.061786] thinkpad_acpi: radio switch found; radios are enabled
    [ 5.061823] thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver
    [ 5.061826] thinkpad_acpi: Disabling thinkpad-acpi brightness events by default...
    [ 5.065579] Registered led device: tpacpi::thinklight
    [ 5.066198] Registered led device: tpacpi::power
    [ 5.066854] Registered led device: tpacpi::standby
    [ 5.067460] Registered led device: tpacpi::thinkvantage
    [ 5.069575] thinkpad_acpi: Standard ACPI backlight interface available, not loading native one
    [ 5.073307] thinkpad_acpi: Console audio control enabled, mode: monitor (read only)
    [ 5.078614] input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input5
    [ 5.095400] sdhci-pci 0000:15:00.2: Will use DMA mode even though HW doesn't fully claim to support it.
    [ 5.117055] psmouse serio1: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3
    [ 5.140000] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/input/input6
    [ 5.151096] sdhci-pci 0000:15:00.2: Will use DMA mode even though HW doesn't fully claim to support it.
    [ 5.153224] microcode: CPU0 sig=0x6ec, pf=0x20, revision=0x54
    [ 5.164786] microcode: CPU1 sig=0x6ec, pf=0x20, revision=0x54
    [ 5.165320] microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
    [ 5.207805] sdhci-pci 0000:15:00.2: Will use DMA mode even though HW doesn't fully claim to support it.
    [ 5.230590] [drm] Initialized drm 1.1.0 20060810
    [ 5.230609] hda_intel: probe_mask set to 0x1 for device 17aa:2010
    [ 5.230693] snd_hda_intel 0000:00:1b.0: irq 45 for MSI/MSI-X
    [ 5.233890] usbcore: registered new interface driver usbhid
    [ 5.233893] usbhid: USB HID core driver
    [ 5.302730] input: Razer Razer Abyssus as /devices/pci0000:00/0000:00:1d.7/usb1/1-6/1-6.1/1-6.1.3/1-6.1.3:1.0/input/input7
    [ 5.305459] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input8
    [ 5.308922] hid-generic 0003:1532:001C.0001: input,hidraw0: USB HID v1.11 Mouse [Razer Razer Abyssus] on usb-0000:00:1d.7-6.1.3/input0
    [ 5.312138] input: Logitech Logitech Illuminated Keyboard as /devices/pci0000:00/0000:00:1d.7/usb1/1-6/1-6.1/1-6.1.4/1-6.1.4:1.0/input/input9
    [ 5.315939] hid-generic 0003:046D:C318.0002: input,hidraw1: USB HID v1.11 Keyboard [Logitech Logitech Illuminated Keyboard] on usb-0000:00:1d.7-6.1.4/input0
    [ 5.318601] input: Logitech Logitech Illuminated Keyboard as /devices/pci0000:00/0000:00:1d.7/usb1/1-6/1-6.1/1-6.1.4/1-6.1.4:1.1/input/input10
    [ 5.321840] hid-generic 0003:046D:C318.0003: input,hiddev0,hidraw2: USB HID v1.11 Device [Logitech Logitech Illuminated Keyboard] on usb-0000:00:1d.7-6.1.4/input1
    [ 5.438593] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af:
    [ 5.440382] excluding 0x170-0x177 0x1f0-0x1f7 0x2f8-0x2ff 0x370-0x377
    [ 5.441643] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff:
    [ 5.442231] excluding 0x3f0-0x3ff 0x4d0-0x4d7
    [ 5.442857] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff:
    [ 5.443951] clean.
    [ 5.444080] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7:
    [ 5.445209] clean.
    [ 5.445331] pcmcia_socket pcmcia_socket0: cs: memory probe 0x0c0000-0x0fffff:
    [ 5.445342] excluding 0xc0000-0xd3fff 0xdc000-0xfffff
    [ 5.445474] pcmcia_socket pcmcia_socket0: cs: memory probe 0xa0000000-0xa0ffffff:
    [ 5.445502] clean.
    [ 5.445617] pcmcia_socket pcmcia_socket0: cs: memory probe 0x60000000-0x60ffffff:
    [ 5.445637] excluding 0x60000000-0x60ffffff
    [ 5.445762] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff:
    [ 5.446982] clean.
    [ 5.480269] firewire_core 0000:15:00.1: created device fw0: GUID 000ae4070008202a, S400
    [ 5.528492] i915 0000:00:02.0: setting latency timer to 64
    [ 5.530227] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
    [ 5.530232] [drm] Driver supports precise vblank timestamp query.
    [ 5.530309] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
    [ 5.665563] ath: EEPROM regdomain: 0x62
    [ 5.665569] ath: EEPROM indicates we should expect a direct regpair map
    [ 5.665575] ath: Country alpha2 being used: 00
    [ 5.665578] ath: Regpair used: 0x62
    [ 5.669776] [drm] initialized overlay support
    [ 5.724409] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
    [ 5.724970] Registered led device: ath5k-phy0::rx
    [ 5.725025] Registered led device: ath5k-phy0::tx
    [ 5.725049] ath5k: phy0: Atheros AR5414 chip found (MAC: 0xa3, PHY: 0x61)
    [ 5.831536] fbcon: inteldrmfb (fb0) is primary device
    [ 5.931289] Console: switching to colour frame buffer device 128x48
    [ 5.938186] fb0: inteldrmfb frame buffer device
    [ 5.938188] drm: registered panic notifier
    [ 5.938198] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
    [ 6.307315] device-mapper: uevent: version 1.0.3
    [ 6.307458] device-mapper: ioctl: 4.23.0-ioctl (2012-07-25) initialised: [email protected]
    [ 16.007070] EXT4-fs (sda3): re-mounted. Opts: (null)
    [ 16.104507] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
    [ 16.104954] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem
    [ 16.106707] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null)
    [ 16.129381] Adding 265068k swap on /dev/sda2. Priority:-1 extents:1 across:265068k
    [ 17.726117] thinkpad_acpi: procfs hotkey enable/disable: access by process with PID 498
    [ 17.726122] ------------[ cut here ]------------
    [ 17.726140] WARNING: at drivers/platform/x86/thinkpad_acpi.c:3822 hotkey_enabledisable_warn+0x54/0x60 [thinkpad_acpi]()
    [ 17.726143] Hardware name: 17033WG
    [ 17.726145] thinkpad_acpi: hotkey enable/disable functionality has been removed from the driver. Hotkeys are always enabled.
    [ 17.726147] Modules linked in: aes_i586 ablk_helper cryptd aes_generic xts gf128mul dm_crypt dm_mod arc4 i915 i2c_algo_bit drm_kms_helper joydev snd_hda_codec_analog hid_generic snd_hda_intel usbhid drm microcode kvm_intel snd_hda_codec snd_pcm snd_page_alloc snd_hwdep thinkpad_acpi ath5k ath sdhci_pci firewire_ohci firewire_core iTCO_wdt pcmcia hid nvram kvm snd_timer snd yenta_socket pcmcia_rsrc serio_raw i2c_i801 psmouse iTCO_vendor_support ppdev mac80211 sdhci mmc_core crc_itu_t pcmcia_core intel_agp parport_pc soundcore cfg80211 evdev intel_gtt e1000e nsc_ircc lpc_ich parport rfkill i2c_core agpgart coretemp thermal battery ac irda crc_ccitt video button nfs lockd sunrpc fscache fuse cpufreq_conservative acpi_cpufreq mperf processor ext4 crc16 jbd2 mbcache sr_mod cdrom sd_mod pata_acpi ata_generic
    [ 17.726230] ata_piix libata uhci_hcd scsi_mod ehci_hcd usbcore usb_common
    [ 17.726240] Pid: 498, comm: rc.local Not tainted 3.6.2-1-ARCH #1
    [ 17.726243] Call Trace:
    [ 17.726252] [<c0139f22>] warn_slowpath_common+0x72/0xa0
    [ 17.726259] [<f857bca4>] ? hotkey_enabledisable_warn+0x54/0x60 [thinkpad_acpi]
    [ 17.726266] [<f857bca4>] ? hotkey_enabledisable_warn+0x54/0x60 [thinkpad_acpi]
    [ 17.726270] [<c0139ff3>] warn_slowpath_fmt+0x33/0x40
    [ 17.726276] [<f857bca4>] hotkey_enabledisable_warn+0x54/0x60 [thinkpad_acpi]
    [ 17.726283] [<f857bd21>] hotkey_write+0x71/0x1d0 [thinkpad_acpi]
    [ 17.726290] [<f857c0ce>] dispatch_proc_write+0x6e/0xb0 [thinkpad_acpi]
    [ 17.726296] [<f857c060>] ? dispatch_proc_open+0x20/0x20 [thinkpad_acpi]
    [ 17.726302] [<c0282703>] proc_reg_write+0x63/0x90
    [ 17.726306] [<c02826a0>] ? proc_reg_poll+0x90/0x90
    [ 17.726312] [<c0233b48>] vfs_write+0x88/0x160
    [ 17.726316] [<c02826a0>] ? proc_reg_poll+0x90/0x90
    [ 17.726320] [<c0233e3d>] sys_write+0x3d/0x80
    [ 17.726326] [<c04d7e1f>] sysenter_do_call+0x12/0x28
    [ 17.726329] ---[ end trace 3bac869c0496cae5 ]---
    [ 17.726334] thinkpad_acpi: setting the hotkey mask to 0xffffffff is likely not the best way to go about it
    [ 17.726336] thinkpad_acpi: please consider using the driver defaults, and refer to up-to-date thinkpad-acpi documentation
    [ 17.730165] thinkpad_acpi: asked for hotkey mask 0xffffffff, but firmware forced it to 0x00ffffff
    [ 21.087969] uhci_hcd 0000:00:1d.0: power state changed by ACPI to D2
    [ 21.088892] uhci_hcd 0000:00:1d.2: power state changed by ACPI to D2
    [ 21.175503] uhci_hcd 0000:00:1d.0: power state changed by ACPI to D0
    [ 21.176385] uhci_hcd 0000:00:1d.0: setting latency timer to 64
    [ 21.212915] uhci_hcd 0000:00:1d.1: setting latency timer to 64
    [ 21.226766] e1000e 0000:02:00.0: eth0: Error reading PHY register
    [ 21.227634] e1000e 0000:02:00.0: eth0: Error reading PHY register
    [ 21.228495] e1000e 0000:02:00.0: eth0: Error reading PHY register
    [ 21.229355] e1000e 0000:02:00.0: eth0: Error reading PHY register
    [ 21.230243] e1000e 0000:02:00.0: eth0: Error reading PHY register
    [ 21.232686] e1000e 0000:02:00.0: eth0: Error reading PHY register
    [ 21.233594] e1000e 0000:02:00.0: eth0: Error reading PHY register
    [ 21.234705] e1000e 0000:02:00.0: eth0: Error reading PHY register
    [ 21.235571] e1000e 0000:02:00.0: eth0: Error reading PHY register
    [ 21.236432] e1000e 0000:02:00.0: eth0: Error reading PHY register
    [ 21.249538] uhci_hcd 0000:00:1d.2: power state changed by ACPI to D0
    [ 21.249639] uhci_hcd 0000:00:1d.2: setting latency timer to 64
    [ 21.927013] e1000e 0000:02:00.0: eth0: Cannot change link characteristics when SoL/IDER is active.
    [ 21.930111] e1000e 0000:02:00.0: eth0: Cannot change link characteristics when SoL/IDER is active.
    [ 22.484883] EXT4-fs (sda3): re-mounted. Opts: data=ordered,commit=360
    [ 22.523746] EXT4-fs (dm-0): re-mounted. Opts: data=ordered,commit

    You are not alone with issues related to the e1000e (but all they concluded was that reloading the module makes it work again):
    https://bbs.archlinux.org/viewtopic.php?id=145564
    It seems like this is more your issue:
    http://permalink.gmane.org/gmane.linux. … devel/8932
    But if none of those boot flags work for you, then there's not much you can do, and you'll have to write a script to reload the module each time after initial boot finishes I guess until the module gets fixed.
    Also, power management of the PCIe interface causes the e1000e to shut off after a while as well (lots of people on CentOS noticing this):
    http://serverfault.com/questions/226319 … ie-aspm-do
    So you can use that boot parameter to stop that from happening, if that becomes an issue for you as well.

  • How to store a class-based exception as container element?

    Hello,
    In a BO type method, there are situations where unexpected class-based exceptions can occur, I handle them with TRY ... CATCH ... ENDTRY.
    If such an error occurs, my BO type method also returns a BO type method exception using a return code (as usually).
    1) Now, my question is how can I store the exception instance in the task container ? (so that to get more information about what happened... it is an unexpected error as I said)
    Note that my question may apply to any class instance.
    2) To achieve this, I have an idea but not sure if it's realistic (maybe the question is not realistic too ). I'll create a new BO type ZOOINSTANC with string attribute containing the serialized instance, with a method to display it.
    Example how it could work, in my BO type method (it returns EXCEPTION parameter of type ZOOINSTANC):
    TRY.
      CATCH cx_root INTO lo_exc.
        DATA l_exc TYPE string.
        CALL TRANSFORMATION id
            SOURCE oo = lo_exc
            RESULT XML l_exc.
        DATA l_bor_zooinstanc TYPE swc_object.
        swc_create_object l_bor_zooinstanc 'ZOOINSTANC' ''. "no key
        swc_set_property l_bor_zooinstanc l_exc.
        swc_set_element container 'EXCEPTION' l_exc.
        exit_return 1001 '' '' '' ''.
    ENDTRY.
    One important issue is that I don't know any API to display the instance :-p
    Do you have any ideas, advices, ... ?
    Thx
    sandra

    Hi Mike, thank you for your answer, and sorry for the delay.
    > I'd rather go with the idea of returning the error details in a structured format that you can view in the container
    Yes, but that's the issue as I don't know which exceptions can be triggered, as I'd like to handle all exceptions.
    > I'd also ask why it's necessary to use BOR for this?
    When a BOR method fails, I want technical support to have all the details of the error, not only a generic error message. It's why I want to store the exception in the workitem container, and be able to display it later.
    > It's obviously your own development, so why not use classes. Subclasses of CX_BO_ERROR are recognised by workflow and you can even  bring a proper message back to the WF log. There's also some info on this in the second edition of the WF book.
    I did a test using demo workflow WS56400159 ("absence"), where I forced CX_BO_ERROR right after SWX_FORMABS_CREATE call in CL_SWF_FORMABSENC / CREATE method, but it seems that only the short text of the exception is kept.
    So, I'm a little disappointed to see that we have a great exception "tool" with class-based exceptions, but only the last text is kept in the system! That would have been great to be able to store the whole information (the attributes, and the whole bunch of cascading exceptions (PREVIOUS attribute), instead of only a simple text).
    sandra

  • Virtual column partitioning - explain plan takes lot of time.

    I have some problem with table with partitioning based on virtual column.
    Explain plan generates for some simple select 2-5 minutes,
    but the same select but without part of where clausule generate in secounds.
    In both query there is the same explain plan.
    Could someone explain why?
    Table:
    CREATE TABLE "SUBSCRIPTION"
    "CUSTOMER_ID" VARCHAR2(100 BYTE),
    "IDENT_SOURCE_ID" VARCHAR2(20 BYTE),
    "ACCOUNT_ID" VARCHAR2(100 BYTE),
    "MSISDN" VARCHAR2(500 BYTE),
    "IMSI" VARCHAR2(500 BYTE),
    "SIM" VARCHAR2(500 BYTE),
    "IMEI" VARCHAR2(500 BYTE),
    "MEID" VARCHAR2(15 BYTE),
    "EMAIL" VARCHAR2(100 BYTE),
    "TELCOOP" VARCHAR2(1000 BYTE),
    "MSISDN_TYPE" VARCHAR2(20 BYTE),
    "GSM" NUMBER(1,0),
    "CDMA" NUMBER(1,0),
    "VALID_FROM" DATE,
    "VALID_TO" DATE,
    "MSISDN_HASH" NUMBER(3,0) GENERATED ALWAYS AS (MOD(TO_NUMBER(NVL2(RTRIM(TRANSLATE(NVL(SUBSTR("MSISDN",-3),NVL("MSISDN",'err')),'123456789','000000000'),'0'),'-1',NVL(SUBSTR("MSISDN",-3),"MSISDN"))),125)) VIRTUAL VISIBLE, --generali mod from 3 last digits of msisdn
    ) PARTITION BY LIST ( "MSISDN_HASH" )
    PARTITION "PCHR" VALUES ( -1 )
    PARTITION "P000" VALUES ( 0 )
    PARTITION "P001" VALUES ( 1 )
    ... and so on till...
    PARTITION "P124" VALUES (124)
    PARALLEL 4;
    Slow select:
    select CUSTOMER_ID, IDENT_SOURCE_ID, ACCOUNT_ID, MSISDN, IMSI, SIM, IMEI, MEID, EMAIL, TELCOOP
    from dbident2.subscription
    where MSISDN = '600489461'
    AND MSISDN_HASH = 86
    AND VALID_FROM <=TO_DATE('2012-02-10 00:00:00', 'YYYY-MM-DD HH24:MI:SS')
    Fast select:
    select CUSTOMER_ID, IDENT_SOURCE_ID, ACCOUNT_ID, MSISDN, IMSI, SIM, IMEI, MEID, EMAIL, TELCOOP
    from dbident2.subscription
    where MSISDN = '600489461'
    AND MSISDN_HASH = 86

    --Slower select trace:
    Registered qb: SEL$1 0xf4ea2a20 (PARSER)
    QUERY BLOCK SIGNATURE
    signature (): qb_name=SEL$1 nbfros=1 flg=0
    fro(0): flg=4 objn=848731 hint_alias="SUBSCRIPTION"@"SEL$1"
    SPM: statement not found in SMB
    SPM: statement not a candidate for auto-capture
    Dynamic sampling level auto-adjusted from 6 to 6
    Automatic degree of parallelism (ADOP)
    Automatic degree of parallelism is disabled: Parameter.
    PM: Considering predicate move-around in query block SEL$1 (#0)
    Predicate Move-Around (PM)
    OPTIMIZER INFORMATION
    ----- Current SQL Statement for this session (sql_id=afjvvjmx6tqgr) -----
    explain plan for
    select CUSTOMER_ID, IDENT_SOURCE_ID, ACCOUNT_ID, MSISDN, IMSI, SIM, IMEI, MEID, EMAIL, TELCOOP
    from subscription
    where MSISDN = '600600600' AND MSISDN_HASH = 86
    AND VALID_FROM <=TO_DATE('2012-02-10 00:00:00', 'YYYY-MM-DD HH24:MI:SS')
    Legend
    The following abbreviations are used by optimizer trace.
    CBQT - cost-based query transformation
    JPPD - join predicate push-down
    OJPPD - old-style (non-cost-based) JPPD
    FPD - filter push-down
    PM - predicate move-around
    CVM - complex view merging
    SPJ - select-project-join
    SJC - set join conversion
    SU - subquery unnesting
    OBYE - order by elimination
    OST - old style star transformation
    ST - new (cbqt) star transformation
    CNT - count(col) to count(*) transformation
    JE - Join Elimination
    JF - join factorization
    SLP - select list pruning
    DP - distinct placement
    qb - query block
    LB - leaf blocks
    DK - distinct keys
    LB/K - average number of leaf blocks per key
    DB/K - average number of data blocks per key
    CLUF - clustering factor
    NDV - number of distinct values
    Resp - response cost
    Card - cardinality
    Resc - resource cost
    NL - nested loops (join)
    SM - sort merge (join)
    HA - hash (join)
    CPUSPEED - CPU Speed
    IOTFRSPEED - I/O transfer speed
    IOSEEKTIM - I/O seek time
    SREADTIM - average single block read time
    MREADTIM - average multiblock read time
    MBRC - average multiblock read count
    MAXTHR - maximum I/O system throughput
    SLAVETHR - average slave I/O throughput
    dmeth - distribution method
    1: no partitioning required
    2: value partitioned
    4: right is random (round-robin)
    128: left is random (round-robin)
    8: broadcast right and partition left
    16: broadcast left and partition right
    32: partition left using partitioning of right
    64: partition right using partitioning of left
    256: run the join in serial
    0: invalid distribution method
    sel - selectivity
    ptn - partition
    PARAMETERS USED BY THE OPTIMIZER
    PARAMETERS WITH ALTERED VALUES
    Compilation Environment Dump
    pgamax_size = 1258280 KB
    parallel_query_default_dop = 32
    db_file_multiblock_read_count = 16
    Bug Fix Control Environment
    PARAMETERS IN OPT_PARAM HINT
    Column Usage Monitoring is ON: tracking level = 1
    Considering Query Transformations on query block SEL$1 (#0)
    Query transformations (QT)
    JF: Checking validity of join factorization for query block SEL$1 (#0)
    JF: Bypassed: not a UNION or UNION-ALL query block.
    ST: not valid since star transformation parameter is FALSE
    TE: Checking validity of table expansion for query block SEL$1 (#0)
    TE: Bypassed: No relevant table found.
    CBQT bypassed for query block SEL$1 (#0): no complex view, sub-queries or UNION (ALL) queries.
    CBQT: Validity checks failed for afjvvjmx6tqgr.
    CSE: Considering common sub-expression elimination in query block SEL$1 (#0)
    Common Subexpression elimination (CSE)
    CSE: CSE not performed on query block SEL$1 (#0).
    OBYE: Considering Order-by Elimination from view SEL$1 (#0)
    Order-by elimination (OBYE)
    OBYE: OBYE bypassed: no order by to eliminate.
    CVM: Considering view merge in query block SEL$1 (#0)
    query block SEL$1 (#0) unchanged
    Considering Query Transformations on query block SEL$1 (#0)
    Query transformations (QT)
    JF: Checking validity of join factorization for query block SEL$1 (#0)
    JF: Bypassed: not a UNION or UNION-ALL query block.
    ST: not valid since star transformation parameter is FALSE
    TE: Checking validity of table expansion for query block SEL$1 (#0)
    TE: Bypassed: No relevant table found.
    CBQT bypassed for query block SEL$1 (#0): no complex view, sub-queries or UNION (ALL) queries.
    CBQT: Validity checks failed for afjvvjmx6tqgr.
    CSE: Considering common sub-expression elimination in query block SEL$1 (#0)
    Common Subexpression elimination (CSE)
    CSE: CSE not performed on query block SEL$1 (#0).
    SU: Considering subquery unnesting in query block SEL$1 (#0)
    Subquery Unnest (SU)
    SJC: Considering set-join conversion in query block SEL$1 (#0)
    Set-Join Conversion (SJC)
    SJC: not performed
    PM: Considering predicate move-around in query block SEL$1 (#0)
    Predicate Move-Around (PM)
    PM: PM bypassed: Outer query contains no views.
    PM: PM bypassed: Outer query contains no views.
    query block SEL$1 (#0) unchanged
    FPD: Considering simple filter push in query block SEL$1 (#0)
    "SUBSCRIPTION"."MSISDN"='600600600' AND "SUBSCRIPTION"."MSISDN_HASH"=86 AND "SUBSCRIPTION"."VALID_FROM"<=TO_DATE(' 2012-02-10 00:00:00', 'syyyy-mm-dd hh24:mi:ss')
    try to generate transitive predicate from check constraints for query block SEL$1 (#0)
    finally: "SUBSCRIPTION"."MSISDN"='600600600' AND "SUBSCRIPTION"."MSISDN_HASH"=86 AND "SUBSCRIPTION"."VALID_FROM"<=TO_DATE(' 2012-02-10 00:00:00', 'syyyy-mm-dd hh24:mi:ss')
    apadrv-start sqlid=12053738773107497463
    call(in-use=8176, alloc=32712), compile(in-use=114912, alloc=116848), execution(in-use=175432, alloc=178928)
    Peeked values of the binds in SQL statement
    Final query after transformations:******* UNPARSED QUERY IS *******
    SELECT "SUBSCRIPTION"."CUSTOMER_ID" "CUSTOMER_ID","SUBSCRIPTION"."IDENT_SOURCE_ID" "IDENT_SOURCE_ID","SUBSCRIPTION"."ACCOUNT_ID" "ACCOUNT_ID","SUBSCRIPTION"."MSISDN" "MSISDN","SUBSCRIPTION"."IMSI" "IMSI","SUBSCRIPTION"."SIM" "SIM","SUBSCRIPTION"."IMEI" "IMEI","SUBSCRIPTION"."MEID" "MEID","SUBSCRIPTION"."EMAIL" "EMAIL","SUBSCRIPTION"."TELCOOP" "TELCOOP" FROM "DBIDENT2"."SUBSCRIPTION" "SUBSCRIPTION" WHERE "SUBSCRIPTION"."MSISDN"='600600600' AND "SUBSCRIPTION"."MSISDN_HASH"=86 AND "SUBSCRIPTION"."VALID_FROM"<=TO_DATE(' 2012-02-10 00:00:00', 'syyyy-mm-dd hh24:mi:ss')
    kkoqbc: optimizing query block SEL$1 (#0)
    call(in-use=8320, alloc=32712), compile(in-use=115880, alloc=116848), execution(in-use=175432, alloc=178928)
    kkoqbc-subheap (create addr=0x2b24ebece950)
    QUERY BLOCK TEXT
    select CUSTOMER_ID, IDENT_SOURCE_ID, ACCOUNT_ID, MSISDN, IMSI, SIM, IMEI, MEID, EMAIL, TELCOOP
    from subscription
    where MSISDN = '600600600' AND MSISDN_HASH = 86
    AND VALID_FROM <=TO_DATE('2012-02-10 00:00:00', 'YYYY-MM-DD HH24:MI:SS')
    QUERY BLOCK SIGNATURE
    signature (optimizer): qb_name=SEL$1 nbfros=1 flg=0
    fro(0): flg=0 objn=848731 hint_alias="SUBSCRIPTION"@"SEL$1"
    SYSTEM STATISTICS INFORMATION
    Using NOWORKLOAD Stats
    CPUSPEEDNW: 714 millions instructions/sec (default is 100)
    IOTFRSPEED: 4096 bytes per millisecond (default is 4096)
    IOSEEKTIM: 10 milliseconds (default is 10)
    MBRC: -1 blocks (default is 16)
    BASE STATISTICAL INFORMATION
    Table Stats::
    Table: SUBSCRIPTION Alias: SUBSCRIPTION Partition [87]
    #Rows: 218104 #Blks: 11008 AvgRowLen: 129.00 ChainCnt: 0.00
    #Rows: 218104 #Blks: 11008 AvgRowLen: 129.00 ChainCnt: 0.00
    Index Stats::
    Index: SUBSCRIPTION_NDX_ACCID Col#: 3
    LVLS: 3 #LB: 121036 #DK: 9767936 LB/K: 1.00 DB/K: 1.00 CLUF: 13921256.00
    Index: SUBSCRIPTION_NDX_CUSID Col#: 1 2 18
    LVLS: 3 #LB: 142123 #DK: 24665396 LB/K: 1.00 DB/K: 1.00 CLUF: 24842146.00
    Index: SUBSCRIPTION_NDX_EMAIL Col#: 9
    LVLS: 2 #LB: 8365 #DK: 1361827 LB/K: 1.00 DB/K: 1.00 CLUF: 1361798.00
    Index: SUBSCRIPTION_NDX_EXT1 Col#: 19
    LVLS: 2 #LB: 65756 #DK: 67792 LB/K: 1.00 DB/K: 80.00 CLUF: 5446485.00
    Index: SUBSCRIPTION_NDX_IMEI Col#: 7
    LVLS: 2 #LB: 44539 #DK: 9199616 LB/K: 1.00 DB/K: 1.00 CLUF: 10413439.00
    Index: SUBSCRIPTION_NDX_IMSI Col#: 5
    LVLS: 3 #LB: 92914 #DK: 12846080 LB/K: 1.00 DB/K: 1.00 CLUF: 23472821.00
    Index: SUBSCRIPTION_NDX_MEID Col#: 8
    LVLS: 1 #LB: 132 #DK: 12585 LB/K: 1.00 DB/K: 1.00 CLUF: 18419.00
    Index: SUBSCRIPTION_NDX_MSISDN Col#: 4 PARTITION [87]
    LVLS: 2 #LB: 1092 #DK: 74848 LB/K: 1.00 DB/K: 2.00 CLUF: 191920.00
    LVLS: 2 #LB: 1092 #DK: 74848 LB/K: 1.00 DB/K: 2.00 CLUF: 191920.00
    Index: SUBSCRIPTION_NDX_SIM Col#: 6
    LVLS: 2 #LB: 88153 #DK: 13169664 LB/K: 1.00 DB/K: 1.00 CLUF: 24727298.00
    Index: SUBSCRIPTION_NDX_SRCID Col#: 2 17
    LVLS: 2 #LB: 81729 #DK: 4 LB/K: 20432.00 DB/K: 257314.00 CLUF: 1029257.00
    Access path analysis for SUBSCRIPTION
    SINGLE TABLE ACCESS PATH
    Single Table Cardinality Estimation for SUBSCRIPTION[SUBSCRIPTION]
    *** 2012-06-12 12:34:53.283
    ** Performing dynamic sampling initial checks. **
    Column (#14):
    NewDensity:0.000020, OldDensity:0.000366 BktCnt:254, PopBktCnt:22, PopValCnt:1, NDV:46252
    Column (#14):
    NewDensity:0.000163, OldDensity:0.000378 BktCnt:254, PopBktCnt:12, PopValCnt:1, NDV:5852
    Column (#14): VALID_FROM( Part#: 87
    AvgLen: 8 NDV: 5852 Nulls: 2 Density: 0.000163 Min: 2450364 Max: 2456082
    Histogram: HtBal #Bkts: 254 UncompBkts: 254 EndPtVals: 244
    Column (#14): VALID_FROM(
    AvgLen: 8 NDV: 5852 Nulls: 2 Density: 0.000163 Min: 2450364 Max: 2456082
    Histogram: HtBal #Bkts: 254 UncompBkts: 254 EndPtVals: 244
    Column (#4):
    NewDensity:0.000000, OldDensity:0.000000 BktCnt:254, PopBktCnt:0, PopValCnt:0, NDV:9730048
    Column (#4):
    NewDensity:0.000013, OldDensity:0.000033 BktCnt:254, PopBktCnt:0, PopValCnt:0, NDV:74848
    Column (#4): MSISDN( Part#: 87
    AvgLen: 10 NDV: 74848 Nulls: 0 Density: 0.000013
    Histogram: HtBal #Bkts: 254 UncompBkts: 254 EndPtVals: 255
    Column (#4): MSISDN(
    AvgLen: 10 NDV: 74848 Nulls: 0 Density: 0.000013
    Histogram: HtBal #Bkts: 254 UncompBkts: 254 EndPtVals: 255
    ** Dynamic sampling initial checks returning TRUE (level = 6).
    *** 2012-06-12 12:34:53.284
    ** Generated dynamic sampling query:
    query text :
    SELECT /* OPT_DYN_SAMP */ /*+ ALL_ROWS IGNORE_WHERE_CLAUSE NO_PARALLEL(SAMPLESUB) opt_param('parallel_execution_enabled', 'false') NO_PARALLEL_INDEX(SAMPLESUB) NO_SQL_TUNE */ NVL(SUM(C1),0), NVL(SUM(C2),0) FROM (SELECT /*+ IGNORE_WHERE_CLAUSE NO_PARALLEL("SUBSCRIPTION") FULL("SUBSCRIPTION") NO_PARALLEL_INDEX("SUBSCRIPTION") */ 1 AS C1, CASE WHEN "SUBSCRIPTION"."MSISDN"='600600600' AND "SUBSCRIPTION"."VALID_FROM"<=TO_DATE(' 2012-02-10 00:00:00', 'syyyy-mm-dd hh24:mi:ss') THEN 1 ELSE 0 END AS C2 FROM "DBIDENT2"."SUBSCRIPTION" SAMPLE BLOCK (1.153706 , 1) SEED (1) "SUBSCRIPTION" WHERE "SUBSCRIPTION"."MSISDN"='600600600' AND "SUBSCRIPTION"."VALID_FROM"<=TO_DATE(' 2012-02-10 00:00:00', 'syyyy-mm-dd hh24:mi:ss')) SAMPLESUB
    *** 2012-06-12 12:36:44.452
    ** Executed dynamic sampling query:
    level : 6
    sample pct. : 1.153706
    total partitions : 1
    partitions for sampling : 1
    actual sample size : 342182
    filtered sample card. : 0
    orig. card. : 218104
    block cnt. table stat. : 11008
    block cnt. for sampling: 11008
    max. sample block cnt. : 128
    sample block cnt. : 127
    min. sel. est. : 0.00001260
    ** Not using dynamic sampling for single table sel. or cardinality.
    DS Failed for : ----- Current SQL Statement for this session (sql_id=afjvvjmx6tqgr) -----
    explain plan for
    select CUSTOMER_ID, IDENT_SOURCE_ID, ACCOUNT_ID, MSISDN, IMSI, SIM, IMEI, MEID, EMAIL, TELCOOP
    from subscription
    where MSISDN = '600600600' AND MSISDN_HASH = 86
    AND VALID_FROM <=TO_DATE('2012-02-10 00:00:00', 'YYYY-MM-DD HH24:MI:SS')
    Column (#21):
    NewDensity:0.002912, OldDensity:0.000000 BktCnt:14078, PopBktCnt:14078, PopValCnt:126, NDV:126
    Column (#21): MSISDN_HASH( Part#: 87
    AvgLen: 3 NDV: 1 Nulls: 0 Density: 0.000002 Min: 86 Max: 86
    Histogram: Freq #Bkts: 1 UncompBkts: 13365 EndPtVals: 1
    Column (#21): MSISDN_HASH(
    AvgLen: 3 NDV: 1 Nulls: 0 Density: 0.000002 Min: 86 Max: 86
    Histogram: Freq #Bkts: 1 UncompBkts: 13365 EndPtVals: 1
    Column (#1):
    NewDensity:0.000000, OldDensity:0.000241 BktCnt:254, PopBktCnt:31, PopValCnt:2, NDV:9768960
    Column (#1):
    NewDensity:0.000009, OldDensity:0.000250 BktCnt:254, PopBktCnt:36, PopValCnt:3, NDV:99208
    Column (#1): CUSTOMER_ID( Part#: 87
    AvgLen: 11 NDV: 99208 Nulls: 0 Density: 0.000009
    Histogram: HtBal #Bkts: 254 UncompBkts: 254 EndPtVals: 222
    Column (#1): CUSTOMER_ID(
    AvgLen: 11 NDV: 99208 Nulls: 0 Density: 0.000009
    Histogram: HtBal #Bkts: 254 UncompBkts: 254 EndPtVals: 222
    Column (#2):
    NewDensity:0.000639, OldDensity:0.000000 BktCnt:14078, PopBktCnt:14078, PopValCnt:3, NDV:3
    Column (#2):
    NewDensity:0.000786, OldDensity:0.000002 BktCnt:13365, PopBktCnt:13365, PopValCnt:3, NDV:3
    Column (#2): IDENT_SOURCE_ID( Part#: 87
    AvgLen: 5 NDV: 3 Nulls: 0 Density: 0.000786
    Histogram: Freq #Bkts: 3 UncompBkts: 13365 EndPtVals: 3
    Column (#2): IDENT_SOURCE_ID(
    AvgLen: 5 NDV: 3 Nulls: 0 Density: 0.000786
    Histogram: Freq #Bkts: 3 UncompBkts: 13365 EndPtVals: 3
    ColGroup (#1, Index) SUBSCRIPTION_NDX_CUSID
    Col#: 1 2 18 CorStregth: -1.00
    ColGroup (#2, Index) SUBSCRIPTION_NDX_SRCID
    Col#: 2 17 CorStregth: -1.00
    ColGroup Usage:: PredCnt: 2 Matches Full: Partial:
    ***** Virtual column Adjustment ******
    Column name MSISDN_HASH
    cost_cpu 2300.00
    cost_io 179769313486231570814527423731704356798070567525844996598917476803157260780028538760589558632766878171540458953514382464234321326889464182768467546703537516986049910576551282076245490090389328944075868508455133942304583236903222948165808559332123348274797826204144723168738177180919299881250404026184124858368.00
    ***** End virtual column Adjustment ******
    Table: SUBSCRIPTION Alias: SUBSCRIPTION
    Card: Original: 218104.000000 Rounded: 3 Computed: 2.75 Non Adjusted: 2.75
    Access Path: TableScan
    Cost: 2420.71 Resp: 672.42 Degree: 0
    Cost_io: 2409.00 Cost_cpu: 100334308
    Resp_io: 669.17 Resp_cpu: 27870641
    kkofmx: index filter:"SUBSCRIPTION"."MSISDN_HASH"=86
    ***** Virtual column Adjustment ******
    Column name MSISDN_HASH
    cost_cpu 2300.00
    cost_io 179769313486231570814527423731704356798070567525844996598917476803157260780028538760589558632766878171540458953514382464234321326889464182768467546703537516986049910576551282076245490090389328944075868508455133942304583236903222948165808559332123348274797826204144723168738177180919299881250404026184124858368.00
    ***** End virtual column Adjustment ******
    Access Path: index (AllEqRange)
    Index: SUBSCRIPTION_NDX_MSISDN
    resc_io: 6.00 resc_cpu: 36840
    ix_sel: 0.000013 ix_sel_with_filters: 0.000013
    ***** Logdef predicate Adjustment ******
    Final IO cst 0.00 , CPU cst 2300.00
    ***** End Logdef Adjustment ******
    Cost: 6.01 Resp: 6.01 Degree: 1
    Best:: AccessPath: IndexRange
    Index: SUBSCRIPTION_NDX_MSISDN
    Cost: 6.01 Degree: 1 Resp: 6.01 Card: 2.75 Bytes: 0
    OPTIMIZER STATISTICS AND COMPUTATIONS
    GENERAL PLANS
    Considering cardinality-based initial join order.
    Permutations for Starting Table :0
    Join order[1]: SUBSCRIPTION[SUBSCRIPTION]#0
    Best so far: Table#: 0 cost: 6.0051 card: 2.7487 bytes: 291
    ****** Recost for parallel table scan *******
    Access path analysis for SUBSCRIPTION
    SINGLE TABLE ACCESS PATH
    Single Table Cardinality Estimation for SUBSCRIPTION[SUBSCRIPTION]
    *** 2012-06-12 12:36:44.454
    ** Performing dynamic sampling initial checks. **
    ** TABLE SUBSCRIPTION Alias: SUBSCRIPTION : reused cached dynamic sampling result (failure).
    ColGroup Usage:: PredCnt: 2 Matches Full: Partial:
    ***** Virtual column Adjustment ******
    Column name MSISDN_HASH
    cost_cpu 2300.00
    cost_io 179769313486231570814527423731704356798070567525844996598917476803157260780028538760589558632766878171540458953514382464234321326889464182768467546703537516986049910576551282076245490090389328944075868508455133942304583236903222948165808559332123348274797826204144723168738177180919299881250404026184124858368.00
    ***** End virtual column Adjustment ******
    Table: SUBSCRIPTION Alias: SUBSCRIPTION
    Card: Original: 218104.000000 Rounded: 3 Computed: 2.75 Non Adjusted: 2.75
    Access Path: TableScan
    Cost: 2420.71 Resp: 672.42 Degree: 0
    Cost_io: 2409.00 Cost_cpu: 100334308
    Resp_io: 669.17 Resp_cpu: 27870641
    Best:: AccessPath: TableScan
    Cost: 672.42 Degree: 4 Resp: 672.42 Card: 2.75 Bytes: 97
    Join order[1]: SUBSCRIPTION[SUBSCRIPTION]#0
    Join order aborted: cost > best plan cost
    (newjo-stop-1) k:0, spcnt:0, perm:1, maxperm:2000
    Number of join permutations tried: 1
    Enumerating distribution method (advanced)
    Trying or-Expansion on query block SEL$1 (#0)
    Transfer Optimizer annotations for query block SEL$1 (#0)
    id=0 frofkks[i] (index start key) predicate="SUBSCRIPTION"."MSISDN"='600600600'
    id=0 frofkke[i] (index stop key) predicate="SUBSCRIPTION"."MSISDN"='600600600'
    id=0 frofand predicate="SUBSCRIPTION"."VALID_FROM"<=TO_DATE(' 2012-02-10 00:00:00', 'syyyy-mm-dd hh24:mi:ss')
    Final cost for query block SEL$1 (#0) - All Rows Plan:
    Best join order: 1
    Cost: 6.0051 Degree: 1 Card: 3.0000 Bytes: 291
    Resc: 6.0051 Resc_io: 6.0000 Resc_cpu: 43740
    Resp: 6.0051 Resp_io: 6.0000 Resc_cpu: 43740
    kkoqbc-subheap (delete addr=0x2b24ebece950, in-use=21280, alloc=32840)
    kkoqbc-end:
    call(in-use=252920, alloc=343912), compile(in-use=129048, alloc=133000), execution(in-use=192248, alloc=195240)
    kkoqbc: finish optimizing query block SEL$1 (#0)
    apadrv-end
    call(in-use=252920, alloc=343912), compile(in-use=129960, alloc=133000), execution(in-use=192248, alloc=195240)
    Starting SQL statement dump
    user_id=115 user_name=xxx module=SQL*Plus action=
    sql_id=afjvvjmx6tqgr plan_hash_value=1672204165 problem_type=3
    ----- Current SQL Statement for this session (sql_id=afjvvjmx6tqgr) -----
    explain plan for
    select CUSTOMER_ID, IDENT_SOURCE_ID, ACCOUNT_ID, MSISDN, IMSI, SIM, IMEI, MEID, EMAIL, TELCOOP
    from subscription
    where MSISDN = '600600600' AND MSISDN_HASH = 86
    AND VALID_FROM <=TO_DATE('2012-02-10 00:00:00', 'YYYY-MM-DD HH24:MI:SS')
    sql_text_length=266
    sql=explain plan for
    select CUSTOMER_ID, IDENT_SOURCE_ID, ACCOUNT_ID, MSISDN, IMSI, SIM, IMEI, MEID, EMAIL, TELCOOP
    from subscription
    where MSISDN = '600600600' AND MSISDN_HASH = 86
    AND VALID_FROM <=TO_DATE('2012-02-10 00:00:00', 'YYYY-MM-DD HH2
    sql=4:MI:SS')
    ----- Explain Plan Dump -----
    ----- Plan Table -----
    ============
    Plan Table
    ============
    -----------------------------------------------------------------------------------------------------------------------+
    | Id | Operation | Name | Rows | Bytes | Cost | Time | Pstart| Pstop |
    -----------------------------------------------------------------------------------------------------------------------+
    | 0 | SELECT STATEMENT | | | | 6 | | | |
    | 1 | PARTITION LIST SINGLE | | 3 | 291 | 6 | 00:00:01 | 88 | 88 |
    | 2 | TABLE ACCESS BY LOCAL INDEX ROWID | SUBSCRIPTION | 3 | 291 | 6 | 00:00:01 | 88 | 88 |
    | 3 | INDEX RANGE SCAN | SUBSCRIPTION_NDX_MSISDN| 3 | | 3 | 00:00:01 | 88 | 88 |
    -----------------------------------------------------------------------------------------------------------------------+
    Predicate Information:
    2 - filter("VALID_FROM"<=TO_DATE(' 2012-02-10 00:00:00', 'syyyy-mm-dd hh24:mi:ss'))
    3 - access("MSISDN"='600600600')
    Content of other_xml column
    ===========================
    nodeid/pflags: 1 1 db_version : 11.2.0.2
    parse_schema : xxx
    plan_hash : 1672204165
    plan_hash_2 : 1960934971
    Outline Data:
    /*+
    BEGIN_OUTLINE_DATA
    IGNORE_OPTIM_EMBEDDED_HINTS
    OPTIMIZER_FEATURES_ENABLE('11.2.0.2')
    DB_VERSION('11.2.0.2')
    OPT_PARAM('optimizer_dynamic_sampling' 6)
    ALL_ROWS
    OUTLINE_LEAF(@"SEL$1")
    INDEX_RS_ASC(@"SEL$1" "SUBSCRIPTION"@"SEL$1" ("SUBSCRIPTION"."MSISDN"))
    END_OUTLINE_DATA
    Query Block Registry:
    SEL$1 0xf4ea2a20 (PARSER) [FINAL]
    call(in-use=259392, alloc=343912), compile(in-use=170344, alloc=270888), execution(in-use=344120, alloc=346656)
    End of Optimizer State Dump
    Dumping Hints
    =============
    ====================== END SQL Statement Dump ======================
    Edited by: user3754081 on 2012-06-12 08:07

  • How To transfer Data From FPGA to Host?

    Hi, I am using Crio 9025 Other Input card for my project.
    I am acquiring current input using 9203, and incoder input using 9411 differencial DI module.
    I am getting encoder pulse count perfectally in both the direction.
    Now What i have to do is. i want to store current input at each encoder pulse.
    for example
     Pulse number  AI1       Al2
         1                30.50    30.89
         2                26.78    26.98
    till last pulse.
    1024                35.89    31.45
    Thats It. Test Over.
    What is the best why to do this.
    CLAD
    Labiew programmer

    Hi Brijesh,
    Kindly have a look at the NI example finder, I am sure you will find DMA or IRQ methods of data transfer.
    Shreyas Hebbare
    Shreyas Technologies
    India

  • Direct Delta, Queued and Unseralized V3

    HI
    FOR IM datasources, BF and UM, the guide mentions Direct Delta as the preferred selection. How do we decide this?
    Also for LO cockpit DS in SD, what selection is chosen?
    Thanks
    Harie

    hi Harie,
    take a look oss note 505700 -LBWE: New update methods as of PI 2002.1 and 500426 - BW extraction SD: alternatives to V3 updating
    hope this helps.
    505700
    Symptom
    Up to and including PI 2001.2 or PI-A 2001.2, only the "Serialized V3 update" update method was used for all applications of the logistics extract structures Customizing Cockpit. As a result of the new plug-in, three new update methods are now also available for each application.
    The "Serialized V3 update" update method is no longer offered as of PI 2003.1 or PI-A 2003.1. Between installing PI 2002.1 or PI-A 2002.1 and installing PI 2003.1 or PI-A 2003.1, you should therefore switch to one of these new methods in all applications offering alternative update methods.
    Rather than describing an error, this note helps you make the right selection of update methods for the applications relating to the logistics extract structures Customizing Cockpit.
    Read this note carefully and in particular, refer to the essential notes required for some applications when using the new update methods.
    You will also find more detailed information on the SAP  Service Marketplace at: http://service.sap.com/~sapidb/011000358700005772172002
    Or:
    http://service.sap.com/BW > SAP BW InfoIndex > Delta Handling > New Update Methods in Logistics Extraction with PI2002.1 2.0x/3.0x (ppt)
    Other terms
    V3 update, V3, serialization, TMCEXUPD
    Reason and Prerequisites
    New design
    Solution
    1. Why should I no longer use the "Serialized V3 update" as of PI 2002.1 or PI-A 2002.1?
    The following restrictions and problems with the "serialized V3 update" resulted in alternative update methods being provided with the new plug-in and the "serialized V3 update" update method no longer being provided with an offset of 2 plug-in releases.
    a) If, in an R/3 System, several users who are logged on in different languages enter documents in an application, the V3 collective run only ever processes the update entries for one language during a process call. Subsequently, a process call is automatically started for the update entries from the documents that were entered in the next language. During the serialized V3 update, only update entries that were generated in direct chronological order and with the same logon language can therefore be processed. If the language in the sequence of the update entries changes, the V3 collective update process is terminated and then restarted with the new language.
    For every restart, the VBHDR update table is read sequentially on the database. If the update tables contain a very high number of entries, it may require so much time to process the update data that more new update records are simultaneously generated than the number of records being processed.
    b) The serialized V3 update can only guarantee the correct sequence of extraction data in a document if the document has not been changed twice in one second.
    c) Furthermore, the serialized V3 update can only ensure that the extraction data of a document is in the correct sequence if the times have been synchronized exactly on all system instances, since the time of the update record (which is determined using the locale time of the application server) is used in sorting the update data.
    d) In addition, the serialized V3 update can only ensure that the extraction data of a document is in the correct sequence if an error did not occur beforehand in the U2 update, since the V3 update only processes update data, for which the U2 update is successfully processed.
    2. New "direct delta" update method:
    With this update mode, extraction data is transferred directly to the BW delta queues every time a document is posted. In this way, each document posted with delta extraction is converted to exactly one LUW in the related BW delta queues.
    If you are using this method, there is no need to schedule a job at regular intervals to transfer the data to the BW delta queues. On the other hand, the number of LUWs per DataSource increases significantly in the BW delta queues because the deltas of many documents are not summarized into one LUW in the BW delta queues as was previously the case for the V3 update.
    If you are using this update mode, note that you cannot post any documents during delta initialization in an application from the start of the recompilation run in the OLTP until all delta init requests have been successfully updated successfully in BW. Otherwise, data from documents posted in the meantime is irretrievably lost.
    The restrictions and problems described in relation to the "Serialized V3 update" do not apply to this update method.
    This update method is recommended for the following general criteria:
    a) A maximum of 10,000 document changes (creating, changing or deleting documents) are accrued between two delta extractions for the application in question. A (considerably) larger number of LUWs in the BW delta queue can result in terminations during extraction.
    b) With a future delta initialization, you can ensure that no documents are posted from the start of the recompilation run in R/3 until all delta-init requests have been successfully posted. This applies particularly if, for example, you want to include more organizational units such as another plant or sales organization in the extraction. Stopping the posting of documents always applies to the entire client.
    3. The new "queued delta" update method:
    With this update mode, the extraction data for the affected application is compiled in an extraction queue (instead of in the update data) and can be transferred to the BW delta queues by an update collective run, as previously executed during the V3 update.
    Up to 10,000 delta extractions of documents to an LUW in the BW delta queues are cumulated in this way per DataSource, depending on the application.
    If you use this method, it is also necessary to schedule a job to regularly transfer the data to the BW delta queues ("update collective run"). However, you should note that reports delivered using the logistics extract structures Customizing cockpit are used during this scheduling. There is no point in scheduling with the RSM13005 report for this update method since this report only processes V3 update entries. The simplest way to perform scheduling is via the "Job control" function in the logistics extract structures Customizing Cockpit. We recommend that you schedule the job hourly during normal operation - that is, after successful delta initialization.
    In the case of a delta initialization, the document postings of the affected application can be included again after successful execution of the recompilation run in the OLTP, provided that you make sure that the update collective run is not started before all delta Init requests have been successfully updated in the BW.
    In the posting-free phase during the recompilation run in OLTP, you should execute the update collective run once (as before) to make sure that there are no old delta extraction data remaining in the extraction queues when you resume posting of documents.
    If you want to use the functions of the logistics extract structures Customizing cockpit to make changes to the extract structures of an application (for which you selected this update method), you should make absolutely sure that there is no data in the extraction queue before executing these changes in the affected systems. This applies in particular to the transfer of changes to a production system. You can perform a check when the V3 update is already in use in the respective target system using the RMCSBWCC check report.
    In the following cases, the extraction queues should never contain any data:
    - Importing an R/3 Support Package
    - Performing an R/3 upgrade
    - Importing a plug-in Support Packages
    - Executing a plug-in upgrade
    For an overview of the data of all extraction queues of the logistics extract structures Customizing Cockpit, use transaction LBWQ. You may also obtain this overview via the "Log queue overview" function in the logistics extract structures Customizing cockpit. Only the extraction queues that currently contain extraction data are displayed in this case.
    The restrictions and problems described in relation to the "Serialized V3 update" do not apply to this update method.
    This update method is recommended for the following general criteria:
    a) More than 10,000 document changes (creating, changing or deleting a documents) are performed each day for the application in question.
    b) In future delta initializations, you must reduce the posting-free phase to executing the recompilation run in R/3. The document postings should be included again when the delta Init requests are posted in BW. Of course, the conditions described above for the update collective run must be taken into account.
    4. The new "unserialized V3 update" update method:
    With this update mode, the extraction data of the application in question continues to be written to the update tables using a V3 update module and is retained there until the data is read and processed by a collective update run.
    However, unlike the current default values (serialized V3 update), the data is read in the update collective run (without taking the sequence from the update tables into account) and then transferred to the BW delta queues.
    The restrictions and problems described in relation to the "Serialized V3 update" do not apply to this update method since serialized data transfer is never the aim of this update method. However, you should note the following limitation of this update method:
    The extraction data of a document posting, where update terminations occurred in the V2 update, can only be processed by the V3 update when the V2 update has been successfully posted.
    This update method is recommended for the following general criteria:
    a) Due to the design of the data targets in BW and for the particular application in question, it is irrelevant whether or not the extraction data is transferred to BW in exactly the same sequence in which the data was generated in R/3.
    5. Other essential points to consider:
    a) If you want to select a new update method in application 02 (Purchasing), it is IMPERATIVE that you implement note 500736. Otherwise, even if you have selected another update method, the data will still be written to the V3 update. The update data can then no longer be processed using the RMBV302 report.
    b) If you want to select a new update method in application 03 (Inventory Management), it is IMPERATIVE that you implement note 486784. Otherwise, even if you have selected another update method, the data will still be written to the V3 update. The update data can then no longer be processed using the RMBWV303 report.
    c) If you want to select a new update method in application 04 (Production Planning and Control), it is IMPERATIVE that you implement note 491382. Otherwise, even if you have selected another update method, the data will still be written to the V3 update. The update data can then no longer be processed using the RMBWV304 report.
    d) If you want to select a new update method in application 45 (Agency Business), it is IMPERATIVE that you implement note 507357. Otherwise, even if you have selected another update method, the data will still be written to the V3 update. The update data can then no longer be processed using the RMBWV345 report.
    e) If you want to change the update method of an application to "queued delta", we urgently recommended that you install the latest qRFC version. In this case, you must refer to note 438015.
    f) If you use the new selection function in the logistics extract structures Customizing Cockpit in an application to change from the "Serialized V3" update method to the "direct delta" or "queued delta", you must make sure that there are no pending V3 updates for the applications concerned before importing the relevant correction in all affected systems. To check this, use transaction SA38 to run the RMCSBWCC report with one of the following extract structures in the relevant systems:
        Application 02:   MC02M_0HDR
        Application 03:   MC03BF0
        Application 04:   MC04PE0ARB
        Application 05:   MC05Q00ACT
        Application 08:   MC08TR0FKP
        Application 11:   MC11VA0HDR
        Application 12:   MC12VC0HDR
        Application 13:   MC13VD0HDR
        Application 17:   MC17I00ACT
        Application 18:   MC18I00ACT
        Application 40:   MC40RP0REV
        Application 43:   MC43RK0CAS
        Application 44:   MC44RB0REC
        Application 45:   MC45W_0HDR.
    You can switch the update method if this report does return any information on open V3 updates. Of course, you must not post any documents in the affected application after checking with the report and until you import the relevant Customizing request. This procedure applies in particular to importing the relevant Customizing request into a production system.
    Otherwise, the pending V3 updates are no longer processed. This processing is still feasible even after you import the Customizing request using the RSM13005 report. However, in this case, you can be sure that the serialization of data in the BW delta queues has not been preserved.
    g) Early delta initialization in the logistics extraction:
    As of PI 2002.1 and BW Release 3.0B, you can use the early delta initialization to perform the delta initialization for selected DataSources.
    Only the DataSources of applications 11, 12 and 13 support this procedure in the logistics extraction for PI 2002.1.
    The early delta initialization is used to admit document postings in the OLTP system as early as possible during the initialization procedure. If an early delta initialization InfoPackage was started in BW, data may be written immediately to the delta queue of the central delta management.
    When you use the "direct delta" update method in the logistics extraction, you do not have to wait for the successful conclusion of all delta Init requests in order to readmit document postings in the OLTP if you are using an early delta initialization.
    When you use the "queued delta" update method, early delta initialization is essentially of no advantage because here, as with conventional initialization procedures, you can readmit document postings after successfully filling the setup tables, provided that you ensure that no data is transferred from the extraction queue to the delta queue, that is, an update collective run is not triggered until all of the delta init requests have been successfully posted.
    Regardless of the initialization procedure or update method selected, it is nevertheless necessary to stop any document postings for the affected application during a recompilation run in the OLTP (filling the setup tables).
    500426
    Symptom
    With the BW extraction with the structures of the logistics extract structures customizing cockpit there is only V3 updating as an update method up to plug-in release PI-2001.2.
    To make every possible effort to ensure the transfer of document postings to BW in the correct sequence the parameter "SERIAL" was added to the V3 collective update (refer also to note 385099). If this parameter is set at the start of the V3 collective update, the update data is read and processed by the database in the sequence of its creation time.
    However, this procedure gives rise to the following major performance problem:
    If documents are entered in an application in an R/3 System by several users that are logged on in different languages, the V3 collective run will only ever process the update entries for one language in a process call. A process call is then started automatically for the update entries of the documents which were entered in the next language. Accordingly, during the serialized V3 update only update entries which were generated in direct chronological sequence and with the same logon language can ever be processed. If the language changes in the sequence of the update entries, the V3 collective update process is terminated and restarted with the new language.
    During every restart, the update table VBHDR is read sequentially on the database. If there are very many entries in the update tables, this can cause the processing of the update data taking so much time that more new update records are generated simultaneously than are processed.
    Furthermore, the serialization is not 100% guaranteed in all scenarios when the V3 update is used, as described also in note 384211.
    From plug-in PI 2002.1 the option is offered for the most important applications of the logistics extract structures customizing cockpit of selecting between several alternative update methods.
    The serialized V3 update is no longer provided from plug-in PI-2003.1.
    The modification provided here enables you to use the new update methods for the applications 11, 12 and 13 as early as from patch 5 of PI 2001.2 or PI-A 2001.2.
    The following update methods are offered:
    direct delta (update mode A):
    With this update mode the extraction data is transferred directly into the BW delta queues with every document posting. Every document posting with delta extraction becomes exactly one LUW in the corresponding BW delta queues.
    If you use this method it is therefore no longer necessary to regularly schedule a job to transfer the data to the BW delta queues. Otherwise there will be a substantial increase in the number of LUWs per DataSource in the BW delta queues since, unlike previously, with V3 updating the deltas of many documents are grouped together to form an LUW in the BW delta queues.
    Furthermore you should note when using this update mode that during delta initialization in an application, from the start of the recompilation run in the OLTP no document postings may be made until all delta Init requests have been updated successfully in BW. Otherwise data in documents posted in the interim will be irretrievably lost.
    queued delta (Update mode B):
    With this update mode the extraction data of the affected application is collected in an 'extraction queue' instead of in the update dataand can be transferred via an update collective run into the BW delta queues, as is already the case during V3 updating.
    For each DataSource,1000 delta extractions are summarized by documents of the application to form an LUW in the BW delta queues.
    If you are using this method it is thus also necessary to regularly schedule a job for transferring the data to the BW delta queues. This scheduling is carried out with the same report which is used when you use the V3 updating (RMBWV311, RMBWV312 or RMBWV313). You are recommended to schedule the job on an hourly basis in normal operation - that is following the successful delta initialization.
    In the case of a delta initialization the document postings of the affected application can be included again after the successful execution of the recompilation run in the OLTP (OLI7BW, OLI8BW or OLI9BW) if you ensure that the update collective run is not started before all delta Init requests are updated successfully in BW.
    In the posting-free phase during the recompilation run in the OLTP - as previously - the update collective run should be be run once successfully to ensure that there is no old delta extraction data in the extraction queues during the reinsertion of the document posting.
    Using transaction SMQ1 and the queue names MCEX11, MCEX12 or MCEX13 you can get an overview of the data in the extraction queues.
    unserialized V3 update (update mode C):
    With this update mode the extraction data of the affected application is written to the update tables as before with the aid of a V3 update module and kept there until the data is read and processed by an update collective run.
    However, unlike the current default values (serialized V3 update), in the update collective run the data is read and transferred to the BW delta queues without taking into account the sequence from the update tables. This is why the performance problem described above does not arise in this case.
    This method should only be used if, due to the design of the cubes or ODS objects in the BW system, it does not matter whether the data is transferred to BW in exactly the same sequence in which it was generated in the OLTP System.
    Other terms
    V3 update
    Reason and Prerequisites
    Additional desired functions.
    Solution
    If you already want to use one of the above-described new update methods in the applications 11, 12 or 13 with PI 2001.2 or PI-A 2001.2, you can do this with the corrections given here. However, it is vital that you bear in mind the following points:
    1. The corrections described here consist ofa modification which is not included in any PI Support Package. Check whether the described corrections are necessary. When you import a PI Support Package, parts of these corrections may be overwritten. When importing the PI Support Package ensure that you have got all of these corrections (SPAM/SPAU).
    2. Only copy these modifications in consultation with SAP logistics extraction development.
    3. The corrections presented here should only ever be regarded as an interim solution. The functions are only fully available with PI 2002.1 and PI-A 2002.1. You should also consider the option of upgrading soon to PI 2002.1 or PI-A 2002.1.
    Note also that if the update methods of the applications 11, 12 and 13 are changed prematurely, other applications can still only offer the serialized V3 update. The performance problem described above continues to apply to these applications. It should, however, be significantly reduced by the absence of the modules of applications 11, 12 and 13.
    4. The corrections described here necessitate the importing of Support Package 5 of PI 2001.2 or PI-A 2001.2. The corrections described here are not possible in a lower plug-in release or Support Package status since the functions of the new update methods are not available.
    5. If you want to change the update method of an application to "queued delta", you are strongly recommended to first install the most current qRFC version. Refer to note 438015.
    6. If you use the corrections below to change from the update method "Serialized V3" to "Direct delta" or "queued delta" in an application, you must ensure that before the corresponding corrections are imported there are no more open V3 updates for the corresponding applications in all affected systems. To check this, you can execute the report RMCSBWCC in the corresponding systems with transaction SA38 with one of the following extract structures:
        Application 11:   MC11VA0HDR
        Application 12:   MC12VC0HDR
        Application 13:   MC13VD0HDR.
    The change is possible if you are not referred to open V3 updates. Of course, no document postings should be made in the affected application after the check with the report until the transfer of the corrections. This procedure applies in particular to the importing of the corrections into a production system.
    7. If you are already using the update mode "queued delta" with one of the applications 11, 12 or 13 with the corrections stored here before PI 2002.1 and if you want to make changes to the extract structures in this phase via the cockpit, you should ensure that there is no data in the extraction queues before you execute these changes in the affected systems. In particular this applies to the transportation of changes into a production system. In this case it is not sufficient to execute the check report RMCSBWCC recommended in the cockpit and to eliminate the problem areas specified there.
    Below we describe how you can check and ensure this condition.
    8. When you import PI 2002.1 the changes made here will always be ineffective and you will get the update method "serialized V3" again as the preset update method.
    If you have already changed to a different update method in advance in one of the applications 11, 12 or 13 via the corrections stored here, you must consider the following points during the plug-in upgrade to PI 2002.1 or PI-A 2002.1:
    a) Before the upgrade you must ensure that there is no more data in the extraction queues MCEX11, MCEX12 and MCEX13. Otherwise it may no longer be possible to process the data, which may have to be deleted from the queues, due to an extract structure enhancement with the new plug-in. You can do this by starting the collective update report (RMBWV311, RMBWV312 or RMBWV313) and by subsequently checking the extraction queues using transaction SMQ1.
    b) After the upgrade you must ensure that before the inclusion of new document postings, the update method of the corresponding application used in advance by the corrections specified here is also set in the cockpit of the logistics extraction (LBWE), and that this setting is transported into all clients of the affected systems.
    Note in this context that the corrections specified here change the update method so that it is client-independent. The new functions in the cockpit of the logistics extraction from PI 2002.1 or PI-A 2002.1 then allow the client-specific selection of the update methods.
    9. If you want to use the update method "direct delta" in application 11 instead of the serialized V3 update, copy the changes specified in the correction instructions "0120061532 0000373868" given below for the include MCEX11TOP using the ABAP editor (transaction SE38) (these guidelines can be used both for PI 2001.2 and PI-A 2001.2).
    10. If you want to use the update method "direct delta" in application 12 instead of the serialized V3 update, copy the changes specified in the correction instructions "0120061532 0000373868" given below for the include MCEX12TOP using the ABAP editor (transaction SE38) (these guidelines can be used both for PI 2001.2 and PI-A 2001.2).
    11. If you want to use the update method "direct delta" in application 13 instead of the serialized V3 update, copy the changes specified in the correction instructions "0120061532 0000373868" given below for the include MCEX13TOP using the ABAP editor (transaction SE38) (these guidelines can be used both for PI 2001.2 and PI-A 2001.2).
    12. If you want to use the update method "queued delta" in application 11 instead of the serialized V3 update, copy the changes specified in the correction instructions "0120061532 0000380083" given below for the include MCEX11TOP using the ABAP editor (transaction SE38) (these guidelines can be used both for PI 2001.2 and PI-A 2001.2).
    13. If you want to use the update method "queued delta" in application 12 instead of the serialized V3 update, copy the changes specified in the correction instructions "0120061532 0000380083" given below for the include MCEX12TOP using the ABAP editor (transaction SE38) (these guidelines can be used both for PI 2001.2 and PI-A 2001.2).
    14. If you want to use the update method "queued delta" in application 13 instead of the serialized V3 update, copy the changes specified in the correction instructions "0120061532 0000380083" given below for the include MCEX13TOP using the ABAP editor (transaction SE38) (these guidelines can be used both for PI 2001.2 and PI-A 2001.2).
    15. If you want to use the update method "unserialized V3 update" in application 11 instead of the serialized V3 update, copy the changes specified in the correction instructions "0120061532 0000380084" given below for the include MCEX11TOP using the ABAP editor (transaction SE38) (these guidelines can be used both for PI 2001.2 and PI-A 2001.2).
    16. If you want to use the update method "unserialized V3 update" in application 12 instead of the serialized V3 update, copy the changes specified in the correction instructions "0120061532 0000380084" given below for the include MCEX12TOP using the ABAP editor (transaction SE38) (these guidelines can be used both for PI 2001.2 and PI-A 2001.2).
    17. If you want to use the update method "unserialized V3 update" in application 13 instead of the serialized V3 update, copy the changes specified in the correction instructions "0120061532 0000380084" given below for the include MCEX13TOP using the ABAP editor (transaction SE38) (these guidelines can be used both for PI 2001.2 and PI-A 2001.2).

  • RE: (forte-users) Serialisation

    Singh,
    Any message sent across partition boundaries is serialized. This includes
    method invokations, events and exceptions. The signature of the message
    itself is serialized, as well as the values of all parameters/attributes.
    Serializing a scalar value requires less overhead then serialising an
    object, however, the difference isn't as big as you might think. Objects
    have more attributes then just the value you're interested in and these
    attributes are serialised as well. Each object is an instance of a class and
    each class has a UUID, which is added to the serialized stream as well.
    However, methods are NOT serialised. What happens is this. Forte serializes
    an object into a stream containing only the values of the attributes
    (including nested attributes). This stream is given a header which sais of
    which class this object is an instance (the UUID is used for that). The
    receiving partition reads the serialized stream, finds the definition of the
    class (defined by UUID) in its own code, creates an instance of this class
    and fills the data out of the serialized stream into this new object.
    You can imagine what might happen if there is a mismatch between the
    class-definitions in both partitions. You either get
    serialization-deserialization errors, or the receiving partition complains
    that it doesn't even know the UUID of the received streamed object, or you
    get no errors at all and just have an object that displays different
    behaviour, depending what partition it's in.
    If there are no problems, then the main issue is the
    serializing-deserializing overhead. Note that the receiving partition has to
    instantiate a new object for every serialized object it receives and will
    therefore execute all code in the Init() method. This overhead is not
    required for scalar types, for which Forte only needs to reserve a small
    amount of memory space on the stack.
    Any call to a database is also a message sent across partitions and is
    therefore serialized. However, one partition is a Forte partition and the
    other one isn't. Therefore, Forte's internal serialization mechanism isn't
    used. Forte serializes the SQL-query into a format understood by the
    database (which is different for every vendor). Forte then receives a stream
    back which has a different format for every different database type. This
    stream is deserialized and written to attributes that Forte has reserved to
    contain the data. Whether these are scalar, datavalues or domains only
    impacts performance inside the Forte partition. It has no effect on the
    communication with the database.
    Pascal Rottier
    Atos Origin Nederland (BAS/West End User Computing)
    Tel. +31 (0)10-2661223
    Fax. +31 (0)10-2661199
    E-mail: Pascal.Rottiernl.origin-it.com
    ++++++++++++++++++++++++++++
    Philip Morris (Afd. MIS)
    Tel. +31 (0)164-295149
    Fax. +31 (0)164-294444
    E-mail: Rottier.Pascalpmintl.ch
    -----Original Message-----
    From: Singh [mailto:fortelistyahoo.com]
    Sent: Thursday, February 22, 2001 3:30 AM
    To: forte-userslists.xpedior.com
    Subject: (forte-users) Serialisation
    Hello All
    I have a question that has been bugging me for some
    time.
    We all know that it is better to use scalar data
    types, as opposed to objects, when passing data across
    a network.
    The reason, if I understand correctly, is that when
    you send an object across a network, the whole object
    (properties, attributes and methods) is deserialised
    into zero's and one's before being sent across and
    then serialised back into the object when it gets to
    the other side. This would take longer for an object
    since for a scalar value, just the value is
    deserialised and serialised.
    But when you are writing to a database from the tier
    before the database to the database, does it matter
    what type you use. The reason for saying this is that
    the values are serialised before they go across and
    then deserialised when they get to the base, in other
    words, they are sent as zero's and one's. For a scalar
    - just the value is sent across but for an object -
    does just the value go across or the complete object.
    If just the value of the object goes across, then it
    doesn't really matter whether a scalar or object is
    sent across.
    Am I correct in this assumption.
    Thanks in advance for your help.
    Regards,
    Singh
    For the archives, go to: http://lists.xpedior.com/forte-users and use
    the login: forte and the password: archive. To unsubscribe, send in a new
    email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

    Hi,
    I cannot get hold of Tech Note 10398..... can anyone email me a copy?
    Tx
    Etienne
    -----Original Message-----
    From: Klerk, Theo de [SMTP:Theo.de.Klerkcompaq.com]
    Sent: Wednesday, February 09, 2000 4:26 PM
    To: 'Jason de Cean'; 'Forte Users'
    Subject: RE: (forte-users) Serialisation
    There are a number of flags that will show you some of the required
    information in a log file (not within the application itself). Technote
    10398 has many more flags listed for a variety of obscure, useful, not so
    useful and exotic information:
    trc:cm:*:4 and *:8 - show packet serialisation, open, closes between
    partition communication
    trc:do:*:2 - proxy creation/deletion, exception events
    trc:do:*:5 - individual message tracing between proxies
    trc:do:*:8 - serialisation information
    Theo
    For the archives, go to: http://lists.xpedior.com/forte-users and use
    the login: forte and the password: archive. To unsubscribe, send in a new
    email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

  • 2lis_03_um initial data load

    Dear Consultants,
    Our r/3 system is very busy.So I don't want to stop the r/3 system to extract the stock data.Is there any way to do it.I mean Can I extract the initial data while r/3 system is running.I am worrying about loosing the data.
    Best regards

    Hi,
    In case of V3 update of Queue Delta update methodes,We have to lock the users when we are filling the setup tables. But in cese of Direct Delta update Mode, we need to lock the R/3 users until we complete both Filling set uptale and Delta init.
    For more information on all these Methods, take a look on the note: 505700
    <i>1. Why should I no longer use the "Serialized V3 update" as of PI 2002.1 or PI-A 2002.1?
    The following restrictions and problems with the "serialized V3 update" resulted in alternative update methods being provided with the new plug-in and the "serialized V3 update" update method no longer being provided with an offset of 2 plug-in releases.
    a) If, in an R/3 System, several users who are logged on in different languages enter documents in an application, the V3 collective run only ever processes the update entries for one language during a process call. Subsequently, a process call is automatically started for the update entries from the documents that were entered in the next language. During the serialized V3 update, only update entries that were generated in direct chronological order and with the same logon language can therefore be processed. If the language in the sequence of the update entries changes, the V3 collective update process is terminated and then restarted with the new language.
    For every restart, the VBHDR update table is read sequentially on the database. If the update tables contain a very high number of entries, it may require so much time to process the update data that more new update records are simultaneously generated than the number of records being processed.
    b) The serialized V3 update can only guarantee the correct sequence of extraction data in a document if the document has not been changed twice in one second.
    c) Furthermore, the serialized V3 update can only ensure that the extraction data of a document is in the correct sequence if the times have been synchronized exactly on all system instances, since the time of the update record (which is determined using the locale time of the application server) is used in sorting the update data.
    d) In addition, the serialized V3 update can only ensure that the extraction data of a document is in the correct sequence if an error did not occur beforehand in the U2 update, since the V3 update only processes update data, for which the U2 update is successfully processed.
    2. New "direct delta" update method:
    With this update mode, extraction data is transferred directly to the BW delta queues every time a document is posted. In this way, each document posted with delta extraction is converted to exactly one LUW in the related BW delta queues.
    If you are using this method, there is no need to schedule a job at regular intervals to transfer the data to the BW delta queues. On the other hand, the number of LUWs per DataSource increases significantly in the BW delta queues because the deltas of many documents are not summarized into one LUW in the BW delta queues as was previously the case for the V3 update.
    If you are using this update mode, note that you cannot post any documents during delta initialization in an application from the start of the recompilation run in the OLTP until all delta init requests have been successfully updated successfully in BW. Otherwise, data from documents posted in the meantime is irretrievably lost.
    The restrictions and problems described in relation to the "Serialized V3 update" do not apply to this update method.
    This update method is recommended for the following general criteria:
    a) A maximum of 10,000 document changes (creating, changing or deleting documents) are accrued between two delta extractions for the application in question. A (considerably) larger number of LUWs in the BW delta queue can result in terminations during extraction.
    b) With a future delta initialization, you can ensure that no documents are posted from the start of the recompilation run in R/3 until all delta-init requests have been successfully posted. This applies particularly if, for example, you want to include more organizational units such as another plant or sales organization in the extraction. Stopping the posting of documents always applies to the entire client.
    3. The new "queued delta" update method:
    With this update mode, the extraction data for the affected application is compiled in an extraction queue (instead of in the update data) and can be transferred to the BW delta queues by an update collective run, as previously executed during the V3 update.
    Up to 10,000 delta extractions of documents to an LUW in the BW delta queues are cumulated in this way per DataSource, depending on the application.
    If you use this method, it is also necessary to schedule a job to regularly transfer the data to the BW delta queues ("update collective run"). However, you should note that reports delivered using the logistics extract structures Customizing cockpit are used during this scheduling. There is no point in scheduling with the RSM13005 report for this update method since this report only processes V3 update entries. The simplest way to perform scheduling is via the "Job control" function in the logistics extract structures Customizing Cockpit. We recommend that you schedule the job hourly during normal operation - that is, after successful delta initialization.
    In the case of a delta initialization, the document postings of the affected application can be included again after successful execution of the recompilation run in the OLTP, provided that you make sure that the update collective run is not started before all delta Init requests have been successfully updated in the BW.
    In the posting-free phase during the recompilation run in OLTP, you should execute the update collective run once (as before) to make sure that there are no old delta extraction data remaining in the extraction queues when you resume posting of documents.
    If you want to use the functions of the logistics extract structures Customizing cockpit to make changes to the extract structures of an application (for which you selected this update method), you should make absolutely sure that there is no data in the extraction queue before executing these changes in the affected systems. This applies in particular to the transfer of changes to a production system. You can perform a check when the V3 update is already in use in the respective target system using the RMCSBWCC check report.
    In the following cases, the extraction queues should never contain any data:
    - Importing an R/3 Support Package
    - Performing an R/3 upgrade
    - Importing a plug-in Support Packages
    - Executing a plug-in upgrade
    For an overview of the data of all extraction queues of the logistics extract structures Customizing Cockpit, use transaction LBWQ. You may also obtain this overview via the "Log queue overview" function in the logistics extract structures Customizing cockpit. Only the extraction queues that currently contain extraction data are displayed in this case.
    The restrictions and problems described in relation to the "Serialized V3 update" do not apply to this update method.
    This update method is recommended for the following general criteria:
    a) More than 10,000 document changes (creating, changing or deleting a documents) are performed each day for the application in question.
    b) In future delta initializations, you must reduce the posting-free phase to executing the recompilation run in R/3. The document postings should be included again when the delta Init requests are posted in BW. Of course, the conditions described above for the update collective run must be taken into account.
    4. The new "unserialized V3 update" update method:
    With this update mode, the extraction data of the application in question continues to be written to the update tables using a V3 update module and is retained there until the data is read and processed by a collective update run.
    However, unlike the current default values (serialized V3 update), the data is read in the update collective run (without taking the sequence from the update tables into account) and then transferred to the BW delta queues.
    The restrictions and problems described in relation to the "Serialized V3 update" do not apply to this update method since serialized data transfer is never the aim of this update method. However, you should note the following limitation of this update method:
    The extraction data of a document posting, where update terminations occurred in the V2 update, can only be processed by the V3 update when the V2 update has been successfully posted.
    This update method is recommended for the following general criteria:
    a) Due to the design of the data targets in BW and for the particular application in question, it is irrelevant whether or not the extraction data is transferred to BW in exactly the same sequence in which the data was generated in R/3.
    5. Other essential points to consider:
    a) If you want to select a new update method in application 02 (Purchasing), it is IMPERATIVE that you implement note 500736. Otherwise, even if you have selected another update method, the data will still be written to the V3 update. The update data can then no longer be processed using the RMBV302 report.
    b) If you want to select a new update method in application 03 (Inventory Management), it is IMPERATIVE that you implement note 486784. Otherwise, even if you have selected another update method, the data will still be written to the V3 update. The update data can then no longer be processed using the RMBWV303 report.
    c) If you want to select a new update method in application 04 (Production Planning and Control), it is IMPERATIVE that you implement note 491382. Otherwise, even if you have selected another update method, the data will still be written to the V3 update. The update data can then no longer be processed using the RMBWV304 report.
    d) If you want to select a new update method in application 45 (Agency Business), it is IMPERATIVE that you implement note 507357. Otherwise, even if you have selected another update method, the data will still be written to the V3 update. The update data can then no longer be processed using the RMBWV345 report.
    e) If you want to change the update method of an application to "queued delta", we urgently recommended that you install the latest qRFC version. In this case, you must refer to note 438015.
    f) If you use the new selection function in the logistics extract structures Customizing Cockpit in an application to change from the "Serialized V3" update method to the "direct delta" or "queued delta", you must make sure that there are no pending V3 updates for the applications concerned before importing the relevant correction in all affected systems. To check this, use transaction SA38 to run the RMCSBWCC report with one of the following extract structures in the relevant systems:
        Application 02:   MC02M_0HDR
        Application 03:   MC03BF0
        Application 04:   MC04PE0ARB
        Application 05:   MC05Q00ACT
        Application 08:   MC08TR0FKP
        Application 11:   MC11VA0HDR
        Application 12:   MC12VC0HDR
        Application 13:   MC13VD0HDR
        Application 17:   MC17I00ACT
        Application 18:   MC18I00ACT
        Application 40:   MC40RP0REV
        Application 43:   MC43RK0CAS
        Application 44:   MC44RB0REC
        Application 45:   MC45W_0HDR.
    You can switch the update method if this report does return any information on open V3 updates. Of course, you must not post any documents in the affected application after checking with the report and until you import the relevant Customizing request. This procedure applies in particular to importing the relevant Customizing request into a production system.
    Otherwise, the pending V3 updates are no longer processed. This processing is still feasible even after you import the Customizing request using the RSM13005 report. However, in this case, you can be sure that the serialization of data in the BW delta queues has not been preserved.
    g) Early delta initialization in the logistics extraction:
    As of PI 2002.1 and BW Release 3.0B, you can use the early delta initialization to perform the delta initialization for selected DataSources.
    Only the DataSources of applications 11, 12 and 13 support this procedure in the logistics extraction for PI 2002.1.
    The early delta initialization is used to admit document postings in the OLTP system as early as possible during the initialization procedure. If an early delta initialization InfoPackage was started in BW, data may be written immediately to the delta queue of the central delta management.
    When you use the "direct delta" update method in the logistics extraction, you do not have to wait for the successful conclusion of all delta Init requests in order to readmit document postings in the OLTP if you are using an early delta initialization.
    When you use the "queued delta" update method, early delta initialization is essentially of no advantage because here, as with conventional initialization procedures, you can readmit document postings after successfully filling the setup tables, provided that you ensure that no data is transferred from the extraction queue to the delta queue, that is, an update collective run is not triggered until all of the delta init requests have been successfully posted.
    Regardless of the initialization procedure or update method selected, it is nevertheless necessary to stop any document postings for the affected application during a recompilation run in the OLTP (filling the setup tables).</i>
    With rgds,
    Anil Kumar Sharma .P

Maybe you are looking for