2.6.30 Marvell SATA2 Performance

Not sure what all was affected by the 2.6.29-30 upgrade, but after the upgrade my linux software raid6 array built on 1.5tb seagate drives could only sustain network xfer rates of about 4 to 5 megs a sec.  Downgrading to 2.6.29 returned the speed to 60-70 megs/sec up and 105 megs/sec down.  The array is connected via a Supermicro SAT2-MV8 pcix 8 port sata2 controller.  I don't need the new kernel for anything else so this is more just for information.

Not sure what all was affected by the 2.6.29-30 upgrade, but after the upgrade my linux software raid6 array built on 1.5tb seagate drives could only sustain network xfer rates of about 4 to 5 megs a sec.  Downgrading to 2.6.29 returned the speed to 60-70 megs/sec up and 105 megs/sec down.  The array is connected via a Supermicro SAT2-MV8 pcix 8 port sata2 controller.  I don't need the new kernel for anything else so this is more just for information.

Similar Messages

  • P67A-GD65 (B3) Marvel 6gb/s sATA performance?

    I was talking "elsewhere" on a forum, and the topic of the marvel chip came up. It was argued that the design / implementation of the Marvel controller on these motherboards all were the 91xx series, and they all had a pretty horrifying flaw. They share a 5gb/s bus. For something that is said to support 2 6gb/s devices, that is pretty devastating, so i had to come here, where the knowledge about all things MSI is at its highest density. I mean, if the answer is out there, then it's more likely to be here, then anywhere else.
    So.
    Is this issue a part of the P67A-GD65 (B3) motherboard design?
    Assuming the first answer is yes, is there anything you can do to minimize the impact of it?
    Thank you for your time & effort.
    B!

    It's actually not an issue with the mainboard design, it is a problem with the Marvell controller itself. It is an add-on feature to provide SATA III function, but it is not the best. ASMedia controller isn't really a lot better either. At least the Marvell allows RAID for those that desire it. The answer is in the Intel 'native' SATA III controllers which are quite good. A lot depends on the drives used. With spinner HDD's, SATA II or SATA III doesn't make a lot of difference in their performance anyway.
    Quote
    Assuming the first answer is yes, is there anything you can do to minimize the impact of it?
    Not really, other than maybe a Z87 with all the SATA ports Intel controlled SATA III. 
    Added: I have no experience with them, but maybe an aftermarket add-in SATA III controller card would work better. 

  • Disable Marvell SATA on P55-GD85 ?!

    Hi, is there any way to completely disable the onboard marvell sata controller on my board? I'm using newest BIOS, can't seem to find anything.
    The reason is, im getting worse performance on my SSD on the marvell (sata3) controller compared to the native (sata2) one.
    And even if there's no drive connected to the marvell controller, my boottime is much longer because marvell is searching for drivers

    Yes its saying "Marvell 91XX controller" when it's searching for drives (after POST) and after its done, windows loads in 10 sec.
    So it's ~15-30 sec of doing nothing/waiting (sometimes its not even finding my ssd and i need to reboot, then it finds it) before Win7 starts to load.
    I could cut my bootup in half (or more) if i just could DISABLE the marvell controller completely
    Maybe i can't disable it when a drive is attached? Because i havent tried disable it in BIOS _AND_ remove the SSD from the controller?

  • Optimizing system for best performance/stability and a custom kernel

    I have ArchLinux running on a MacBook 4.1 (early 2008), and it's running very well so far. But I would like to optimize it for best performance and stability (but not at the cost of losing 'graphical interface' quality). I want to compile a custom kernel, and I actually did once, but didn't do it well (and removed it), so I need some help from experts to tell me what should I disable or enable when compiling a custom kernel.
    I will post dmesg and lspci (and rc.conf) here, but if you need any other information, please tell me.
    Thanks.
    Dmesg:
    [ 0.000000] Initializing cgroup subsys cpuset
    [ 0.000000] Initializing cgroup subsys cpu
    [ 0.000000] Linux version 3.4.4-2-ARCH (tobias@T-POWA-LX) (gcc version 4.7.1 (GCC) ) #1 SMP PREEMPT Sun Jun 24 18:59:47 CEST 2012
    [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=98afbd56-6ae5-415e-9710-73b8b4ba946c ro quiet add_efi_memmap loglevel=3 console=tty1 splash=silent,fadein,fadeout,theme:arch-banner-icons
    [ 0.000000] BIOS-provided physical RAM map:
    [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
    [ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
    [ 0.000000] BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
    [ 0.000000] BIOS-e820: 0000000000100000 - 000000007dd31000 (usable)
    [ 0.000000] BIOS-e820: 000000007dd31000 - 000000007df32000 (ACPI NVS)
    [ 0.000000] BIOS-e820: 000000007df32000 - 000000007dfe5000 (ACPI data)
    [ 0.000000] BIOS-e820: 000000007dfe5000 - 000000007dfe7000 (ACPI NVS)
    [ 0.000000] BIOS-e820: 000000007dfe7000 - 000000007eec3000 (ACPI data)
    [ 0.000000] BIOS-e820: 000000007eec3000 - 000000007eec5000 (ACPI NVS)
    [ 0.000000] BIOS-e820: 000000007eec5000 - 000000007eec8000 (ACPI data)
    [ 0.000000] BIOS-e820: 000000007eec8000 - 000000007eecb000 (ACPI NVS)
    [ 0.000000] BIOS-e820: 000000007eecb000 - 000000007eecc000 (ACPI data)
    [ 0.000000] BIOS-e820: 000000007eecc000 - 000000007eedf000 (ACPI NVS)
    [ 0.000000] BIOS-e820: 000000007eedf000 - 000000007eef9000 (ACPI data)
    [ 0.000000] BIOS-e820: 000000007eef9000 - 000000007eeff000 (reserved)
    [ 0.000000] BIOS-e820: 000000007eeff000 - 000000007ef00000 (ACPI data)
    [ 0.000000] BIOS-e820: 000000007ef00000 - 0000000080000000 (reserved)
    [ 0.000000] BIOS-e820: 00000000f0000000 - 00000000f4000000 (reserved)
    [ 0.000000] BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
    [ 0.000000] BIOS-e820: 00000000fed14000 - 00000000fed1a000 (reserved)
    [ 0.000000] BIOS-e820: 00000000fed1c000 - 00000000fed20000 (reserved)
    [ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
    [ 0.000000] BIOS-e820: 00000000ffe00000 - 0000000100000000 (reserved)
    [ 0.000000] NX (Execute Disable) protection: active
    [ 0.000000] DMI 2.4 present.
    [ 0.000000] DMI: Apple Inc. MacBook4,1/Mac-F22788A9, BIOS MB41.88Z.00C1.B00.0802091535 02/09/08
    [ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
    [ 0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
    [ 0.000000] No AGP bridge found
    [ 0.000000] last_pfn = 0x7dd31 max_arch_pfn = 0x400000000
    [ 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-DFFFF uncachable
    [ 0.000000] E0000-FFFFF write-protect
    [ 0.000000] MTRR variable ranges enabled:
    [ 0.000000] 0 base 0FFE00000 mask FFFE00000 write-protect
    [ 0.000000] 1 base 000000000 mask F80000000 write-back
    [ 0.000000] 2 base 07F000000 mask FFF000000 uncachable
    [ 0.000000] 3 base 07EF00000 mask FFFF00000 uncachable
    [ 0.000000] 4 disabled
    [ 0.000000] 5 disabled
    [ 0.000000] 6 disabled
    [ 0.000000] 7 disabled
    [ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    [ 0.000000] initial memory mapped : 0 - 20000000
    [ 0.000000] Base memory trampoline at [ffff88000009a000] 9a000 size 20480
    [ 0.000000] init_memory_mapping: 0000000000000000-000000007dd31000
    [ 0.000000] 0000000000 - 007dc00000 page 2M
    [ 0.000000] 007dc00000 - 007dd31000 page 4k
    [ 0.000000] kernel direct mapping tables up to 7dd31000 @ 1fffc000-20000000
    [ 0.000000] RAMDISK: 37492000 - 37a41000
    [ 0.000000] ACPI: RSDP 00000000000fe020 00024 (v02 APPLE )
    [ 0.000000] ACPI: XSDT 000000007eeee1c0 00084 (v01 APPLE Apple00 000000C1 01000013)
    [ 0.000000] ACPI: FACP 000000007eeec000 000F4 (v03 APPLE Apple00 000000C1 Loki 0000005F)
    [ 0.000000] ACPI: DSDT 000000007eee1000 045C6 (v01 APPLE MacBook 00040001 INTL 20061109)
    [ 0.000000] ACPI: FACS 000000007eecc000 00040
    [ 0.000000] ACPI: HPET 000000007eeeb000 00038 (v01 APPLE Apple00 00000001 Loki 0000005F)
    [ 0.000000] ACPI: APIC 000000007eeea000 00068 (v01 APPLE Apple00 00000001 Loki 0000005F)
    [ 0.000000] ACPI: MCFG 000000007eee9000 0003C (v01 APPLE Apple00 00000001 Loki 0000005F)
    [ 0.000000] ACPI: ASF! 000000007eee8000 000A5 (v32 APPLE Apple00 00000001 Loki 0000005F)
    [ 0.000000] ACPI: SBST 000000007eee7000 00030 (v01 APPLE Apple00 00000001 Loki 0000005F)
    [ 0.000000] ACPI: ECDT 000000007eee6000 00053 (v01 APPLE Apple00 00000001 Loki 0000005F)
    [ 0.000000] ACPI: SSDT 000000007eec7000 004DC (v01 APPLE CpuPm 00003000 INTL 20061109)
    [ 0.000000] ACPI: SSDT 000000007eec6000 0025F (v01 APPLE Cpu0Tst 00003000 INTL 20061109)
    [ 0.000000] ACPI: SSDT 000000007eec5000 000A6 (v01 APPLE Cpu1Tst 00003000 INTL 20061109)
    [ 0.000000] ACPI: SSDT 000000007eee0000 00544 (v01 SataRe SataPri 00001000 INTL 20061109)
    [ 0.000000] ACPI: SSDT 000000007eedf000 00477 (v01 SataRe SataSec 00001000 INTL 20061109)
    [ 0.000000] ACPI: Local APIC address 0xfee00000
    [ 0.000000] No NUMA configuration found
    [ 0.000000] Faking a node at 0000000000000000-000000007dd31000
    [ 0.000000] Initmem setup node 0 0000000000000000-000000007dd31000
    [ 0.000000] NODE_DATA [000000007dd2d000 - 000000007dd30fff]
    [ 0.000000] [ffffea0000000000-ffffea0001ffffff] PMD -> [ffff88007b400000-ffff88007d3fffff] on node 0
    [ 0.000000] Zone PFN ranges:
    [ 0.000000] DMA 0x00000010 -> 0x00001000
    [ 0.000000] DMA32 0x00001000 -> 0x00100000
    [ 0.000000] Normal empty
    [ 0.000000] Movable zone start PFN for each node
    [ 0.000000] Early memory PFN ranges
    [ 0.000000] 0: 0x00000010 -> 0x0000009f
    [ 0.000000] 0: 0x00000100 -> 0x0007dd31
    [ 0.000000] On node 0 totalpages: 515264
    [ 0.000000] DMA zone: 64 pages used for memmap
    [ 0.000000] DMA zone: 5 pages reserved
    [ 0.000000] DMA zone: 3914 pages, LIFO batch:0
    [ 0.000000] DMA32 zone: 7989 pages used for memmap
    [ 0.000000] DMA32 zone: 503292 pages, LIFO batch:31
    [ 0.000000] ACPI: PM-Timer IO Port: 0x408
    [ 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] SMP: 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 - 00000000000e0000
    [ 0.000000] PM: Registered nosave memory: 00000000000e0000 - 0000000000100000
    [ 0.000000] Allocating PCI resources starting at 80000000 (gap: 80000000:70000000)
    [ 0.000000] Booting paravirtualized kernel on bare hardware
    [ 0.000000] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:2 nr_node_ids:1
    [ 0.000000] PERCPU: Embedded 28 pages/cpu @ffff88007da00000 s82880 r8192 d23616 u1048576
    [ 0.000000] pcpu-alloc: s82880 r8192 d23616 u1048576 alloc=1*2097152
    [ 0.000000] pcpu-alloc: [0] 0 1
    [ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 507206
    [ 0.000000] Policy zone: DMA32
    [ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=98afbd56-6ae5-415e-9710-73b8b4ba946c ro quiet add_efi_memmap loglevel=3 console=tty1 splash=silent,fadein,fadeout,theme:arch-banner-icons
    [ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
    [ 0.000000] Checking aperture...
    [ 0.000000] No AGP bridge found
    [ 0.000000] Calgary: detecting Calgary via BIOS EBDA area
    [ 0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
    [ 0.000000] Memory: 2011044k/2061508k available (4538k kernel code, 452k absent, 50012k reserved, 4308k data, 740k init)
    [ 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] NR_IRQS:4352 nr_irqs:512 16
    [ 0.000000] Extended CMOS year: 2000
    [ 0.000000] Console: colour dummy device 80x25
    [ 0.000000] console [tty1] enabled
    [ 0.000000] allocated 8388608 bytes of page_cgroup
    [ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
    [ 0.000000] hpet clockevent registered
    [ 0.000000] Fast TSC calibration failed
    [ 0.000000] TSC: PIT calibration matches HPET. 2 loops
    [ 0.000000] Detected 2393.995 MHz processor.
    [ 0.010005] Calibrating delay loop (skipped), value calculated using timer frequency.. 4789.48 BogoMIPS (lpj=7979983)
    [ 0.010013] pid_max: default: 32768 minimum: 301
    [ 0.010061] Security Framework initialized
    [ 0.010069] AppArmor: AppArmor disabled by boot time parameter
    [ 0.010381] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
    [ 0.011643] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
    [ 0.012201] Mount-cache hash table entries: 256
    [ 0.012567] Initializing cgroup subsys cpuacct
    [ 0.012573] Initializing cgroup subsys memory
    [ 0.012588] Initializing cgroup subsys devices
    [ 0.012592] Initializing cgroup subsys freezer
    [ 0.012595] Initializing cgroup subsys net_cls
    [ 0.012599] Initializing cgroup subsys blkio
    [ 0.012653] CPU: Physical Processor ID: 0
    [ 0.012656] CPU: Processor Core ID: 0
    [ 0.012660] mce: CPU supports 6 MCE banks
    [ 0.012673] CPU0: Thermal monitoring enabled (TM2)
    [ 0.012679] using mwait in idle threads.
    [ 0.015816] ACPI: Core revision 20120320
    [ 0.021231] ftrace: allocating 17820 entries in 70 pages
    [ 0.030546] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    [ 0.064790] CPU0: Intel(R) Core(TM)2 Duo CPU T8300 @ 2.40GHz stepping 06
    [ 0.066663] Performance Events: PEBS fmt0+, 4-deep LBR, Core2 events, Intel PMU driver.
    [ 0.066663] ... version: 2
    [ 0.066663] ... bit width: 40
    [ 0.066663] ... generic registers: 2
    [ 0.066663] ... value mask: 000000ffffffffff
    [ 0.066663] ... max period: 000000007fffffff
    [ 0.066663] ... fixed-purpose events: 3
    [ 0.066663] ... event mask: 0000000700000003
    [ 0.083458] NMI watchdog: enabled, takes one hw-pmu counter.
    [ 0.103350] Booting Node 0, Processors #1 Ok.
    [ 0.116508] NMI watchdog: enabled, takes one hw-pmu counter.
    [ 0.116575] Brought up 2 CPUs
    [ 0.116579] Total of 2 processors activated (9579.97 BogoMIPS).
    [ 0.120053] devtmpfs: initialized
    [ 0.122018] PM: Registering ACPI NVS region [mem 0x7dd31000-0x7df31fff] (2101248 bytes)
    [ 0.122018] PM: Registering ACPI NVS region [mem 0x7dfe5000-0x7dfe6fff] (8192 bytes)
    [ 0.122018] PM: Registering ACPI NVS region [mem 0x7eec3000-0x7eec4fff] (8192 bytes)
    [ 0.122018] PM: Registering ACPI NVS region [mem 0x7eec8000-0x7eecafff] (12288 bytes)
    [ 0.122018] PM: Registering ACPI NVS region [mem 0x7eecc000-0x7eedefff] (77824 bytes)
    [ 0.123629] NET: Registered protocol family 16
    [ 0.123872] ACPI: bus type pci registered
    [ 0.123988] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xf0000000-0xffffffff] (base 0xf0000000)
    [ 0.123995] PCI: MMCONFIG at [mem 0xf0000000-0xffffffff] reserved in E820
    [ 0.124001] PCI: MMCONFIG for 0000 [bus00-3f] at [mem 0xf0000000-0xf3ffffff] (base 0xf0000000) (size reduced!)
    [ 0.153700] PCI: Using configuration type 1 for base access
    [ 0.153895] mtrr: your CPUs had inconsistent variable MTRR settings
    [ 0.153899] mtrr: probably your BIOS does not setup all CPUs.
    [ 0.153901] mtrr: corrected configuration.
    [ 0.154568] bio: create slab <bio-0> at 0
    [ 0.154568] ACPI: Added _OSI(Module Device)
    [ 0.154568] ACPI: Added _OSI(Processor Device)
    [ 0.154568] ACPI: Added _OSI(3.0 _SCP Extensions)
    [ 0.154568] ACPI: Added _OSI(Processor Aggregator Device)
    [ 0.154919] ACPI: EC: EC description table is found, configuring boot EC
    [ 0.159179] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
    [ 0.160245] ACPI: SSDT 000000007eecaa98 00340 (v01 APPLE Cpu0Ist 00003000 INTL 20061109)
    [ 0.160625] ACPI: Dynamic OEM Table Load:
    [ 0.160630] ACPI: SSDT (null) 00340 (v01 APPLE Cpu0Ist 00003000 INTL 20061109)
    [ 0.160795] ACPI: SSDT 000000007eec8c18 002AD (v01 APPLE Cpu0Cst 00003001 INTL 20061109)
    [ 0.161153] ACPI: Dynamic OEM Table Load:
    [ 0.161158] ACPI: SSDT (null) 002AD (v01 APPLE Cpu0Cst 00003001 INTL 20061109)
    [ 0.161186] ACPI: SSDT 000000007eec9f18 000C8 (v01 APPLE Cpu1Ist 00003000 INTL 20061109)
    [ 0.161186] ACPI: Dynamic OEM Table Load:
    [ 0.161186] ACPI: SSDT (null) 000C8 (v01 APPLE Cpu1Ist 00003000 INTL 20061109)
    [ 0.161186] ACPI: SSDT 000000007eec8f18 00085 (v01 APPLE Cpu1Cst 00003000 INTL 20061109)
    [ 0.161187] ACPI: Dynamic OEM Table Load:
    [ 0.161192] ACPI: SSDT (null) 00085 (v01 APPLE Cpu1Cst 00003000 INTL 20061109)
    [ 0.161220] ACPI: Interpreter enabled
    [ 0.161220] ACPI: (supports S0 S3 S4 S5)
    [ 0.161220] ACPI: Using IOAPIC for interrupt routing
    [ 0.173742] ACPI: EC: GPE = 0x17, I/O: command/status = 0x66, data = 0x62
    [ 0.173981] ACPI: No dock devices found.
    [ 0.173988] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
    [ 0.174581] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
    [ 0.175426] pci_root PNP0A08:00: host bridge window [io 0x0000-0x0cf7]
    [ 0.175431] pci_root PNP0A08:00: host bridge window [io 0x0d00-0xffff]
    [ 0.175436] pci_root PNP0A08:00: host bridge window [mem 0x000a0000-0x000bffff]
    [ 0.175443] pci_root PNP0A08:00: host bridge window [mem 0x80000000-0xfebfffff]
    [ 0.175505] PCI host bridge to bus 0000:00
    [ 0.175510] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
    [ 0.175514] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
    [ 0.175518] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
    [ 0.175523] pci_bus 0000:00: root bus resource [mem 0x80000000-0xfebfffff]
    [ 0.175539] pci 0000:00:00.0: [8086:2a00] type 00 class 0x060000
    [ 0.175610] pci 0000:00:02.0: [8086:2a02] type 00 class 0x030000
    [ 0.175631] pci 0000:00:02.0: reg 10: [mem 0x90100000-0x901fffff 64bit]
    [ 0.175645] pci 0000:00:02.0: reg 18: [mem 0x80000000-0x8fffffff 64bit pref]
    [ 0.175655] pci 0000:00:02.0: reg 20: [io 0x6110-0x6117]
    [ 0.175712] pci 0000:00:02.1: [8086:2a03] type 00 class 0x038000
    [ 0.175730] pci 0000:00:02.1: reg 10: [mem 0x90200000-0x902fffff 64bit]
    [ 0.175849] pci 0000:00:1a.0: [8086:2834] type 00 class 0x0c0300
    [ 0.175917] pci 0000:00:1a.0: reg 20: [io 0x60c0-0x60df]
    [ 0.175971] pci 0000:00:1a.1: [8086:2835] type 00 class 0x0c0300
    [ 0.176038] pci 0000:00:1a.1: reg 20: [io 0x60a0-0x60bf]
    [ 0.176110] pci 0000:00:1a.7: [8086:283a] type 00 class 0x0c0320
    [ 0.176140] pci 0000:00:1a.7: reg 10: [mem 0x90704c00-0x90704fff]
    [ 0.176140] pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
    [ 0.176140] pci 0000:00:1b.0: [8086:284b] type 00 class 0x040300
    [ 0.176140] pci 0000:00:1b.0: reg 10: [mem 0x90700000-0x90703fff 64bit]
    [ 0.176140] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
    [ 0.176140] pci 0000:00:1c.0: [8086:283f] type 01 class 0x060400
    [ 0.176140] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
    [ 0.176140] pci 0000:00:1c.4: [8086:2847] type 01 class 0x060400
    [ 0.176140] pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
    [ 0.176140] pci 0000:00:1c.5: [8086:2849] type 01 class 0x060400
    [ 0.176140] pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
    [ 0.176140] pci 0000:00:1d.0: [8086:2830] type 00 class 0x0c0300
    [ 0.176140] pci 0000:00:1d.0: reg 20: [io 0x6080-0x609f]
    [ 0.176140] pci 0000:00:1d.1: [8086:2831] type 00 class 0x0c0300
    [ 0.176140] pci 0000:00:1d.1: reg 20: [io 0x6060-0x607f]
    [ 0.176140] pci 0000:00:1d.2: [8086:2832] type 00 class 0x0c0300
    [ 0.176140] pci 0000:00:1d.2: reg 20: [io 0x6040-0x605f]
    [ 0.176140] pci 0000:00:1d.7: [8086:2836] type 00 class 0x0c0320
    [ 0.176140] pci 0000:00:1d.7: reg 10: [mem 0x90704800-0x90704bff]
    [ 0.176140] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
    [ 0.176140] pci 0000:00:1e.0: [8086:2448] type 01 class 0x060401
    [ 0.176140] pci 0000:00:1f.0: [8086:2815] type 00 class 0x060100
    [ 0.176140] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0680 (mask 000f)
    [ 0.176140] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 2 PIO at 1640 (mask 000f)
    [ 0.176140] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 4 PIO at 0300 (mask 001f)
    [ 0.176140] pci 0000:00:1f.1: [8086:2850] type 00 class 0x01018f
    [ 0.176140] pci 0000:00:1f.1: reg 10: [io 0x6108-0x610f]
    [ 0.176140] pci 0000:00:1f.1: reg 14: [io 0x6124-0x6127]
    [ 0.176140] pci 0000:00:1f.1: reg 18: [io 0x6100-0x6107]
    [ 0.176140] pci 0000:00:1f.1: reg 1c: [io 0x6120-0x6123]
    [ 0.176140] pci 0000:00:1f.1: reg 20: [io 0x60e0-0x60ef]
    [ 0.176140] pci 0000:00:1f.2: [8086:2828] type 00 class 0x01018f
    [ 0.176140] pci 0000:00:1f.2: reg 10: [io 0x60f8-0x60ff]
    [ 0.176140] pci 0000:00:1f.2: reg 14: [io 0x611c-0x611f]
    [ 0.176140] pci 0000:00:1f.2: reg 18: [io 0x60f0-0x60f7]
    [ 0.176140] pci 0000:00:1f.2: reg 1c: [io 0x6118-0x611b]
    [ 0.176140] pci 0000:00:1f.2: reg 20: [io 0x6020-0x602f]
    [ 0.176140] pci 0000:00:1f.2: reg 24: [io 0x4000-0x400f]
    [ 0.176140] pci 0000:00:1f.2: PME# supported from D3hot
    [ 0.176140] pci 0000:00:1f.3: [8086:283e] type 00 class 0x0c0500
    [ 0.176140] pci 0000:00:1f.3: reg 10: [mem 0x90705000-0x907050ff]
    [ 0.176140] pci 0000:00:1f.3: reg 20: [io 0xefa0-0xefbf]
    [ 0.176140] pci 0000:00:1c.0: PCI bridge to [bus 01-01]
    [ 0.176140] pci 0000:00:1c.0: bridge window [mem 0x90600000-0x906fffff]
    [ 0.176140] pci 0000:02:00.0: [14e4:4328] type 00 class 0x028000
    [ 0.176140] pci 0000:02:00.0: reg 10: [mem 0x90500000-0x90503fff 64bit]
    [ 0.176140] pci 0000:02:00.0: reg 18: [mem 0x90000000-0x900fffff 64bit pref]
    [ 0.176140] pci 0000:02:00.0: supports D1 D2
    [ 0.176140] pci 0000:02:00.0: PME# supported from D0 D3hot D3cold
    [ 0.183347] pci 0000:00:1c.4: PCI bridge to [bus 02-02]
    [ 0.183358] pci 0000:00:1c.4: bridge window [mem 0x90500000-0x905fffff]
    [ 0.183369] pci 0000:00:1c.4: bridge window [mem 0x90000000-0x900fffff 64bit pref]
    [ 0.183595] pci 0000:03:00.0: [11ab:436a] type 00 class 0x020000
    [ 0.183741] pci 0000:03:00.0: reg 10: [mem 0x90400000-0x90403fff 64bit]
    [ 0.183826] pci 0000:03:00.0: reg 18: [io 0x5000-0x50ff]
    [ 0.184121] pci 0000:03:00.0: reg 30: [mem 0xfffe0000-0xffffffff pref]
    [ 0.184581] pci 0000:03:00.0: supports D1 D2
    [ 0.184585] pci 0000:03:00.0: PME# supported from D0 D1 D2 D3hot D3cold
    [ 0.184821] pci 0000:00:1c.5: PCI bridge to [bus 03-03]
    [ 0.184828] pci 0000:00:1c.5: bridge window [io 0x5000-0x5fff]
    [ 0.184836] pci 0000:00:1c.5: bridge window [mem 0x90400000-0x904fffff]
    [ 0.184905] pci 0000:04:03.0: [11c1:5811] type 00 class 0x0c0010
    [ 0.184934] pci 0000:04:03.0: reg 10: [mem 0x90300000-0x90300fff]
    [ 0.185056] pci 0000:04:03.0: supports D1 D2
    [ 0.185060] pci 0000:04:03.0: PME# supported from D0 D1 D2 D3hot
    [ 0.185137] pci 0000:00:1e.0: PCI bridge to [bus 04-04] (subtractive decode)
    [ 0.185148] pci 0000:00:1e.0: bridge window [mem 0x90300000-0x903fffff]
    [ 0.185160] pci 0000:00:1e.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
    [ 0.185165] pci 0000:00:1e.0: bridge window [io 0x0d00-0xffff] (subtractive decode)
    [ 0.185169] pci 0000:00:1e.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
    [ 0.185174] pci 0000:00:1e.0: bridge window [mem 0x80000000-0xfebfffff] (subtractive decode)
    [ 0.185211] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    [ 0.185419] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP05._PRT]
    [ 0.185489] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP06._PRT]
    [ 0.185588] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIB._PRT]
    [ 0.185829] pci0000:00: Requesting ACPI _OSC control (0x1d)
    [ 0.186233] pci0000:00: ACPI _OSC control (0x1d) granted
    [ 0.193405] ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 10 12 14 15) *11
    [ 0.193487] ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 *7 11 12 14 15)
    [ 0.193565] ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 *5 6 7 10 12 14 15)
    [ 0.193642] ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 11 12 14 15) *0, disabled.
    [ 0.193720] ACPI: PCI Interrupt Link [LNKE] (IRQs 1 3 4 5 6 7 *10 12 14 15)
    [ 0.193797] ACPI: PCI Interrupt Link [LNKF] (IRQs 1 3 4 5 6 7 11 12 14 15) *9
    [ 0.193874] ACPI: PCI Interrupt Link [LNKG] (IRQs 1 3 4 5 6 7 10 12 14 15) *0, disabled.
    [ 0.193957] ACPI: PCI Interrupt Link [LNKH] (IRQs 1 3 4 5 6 7 11 12 14 15) *0, disabled.
    [ 0.196686] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
    [ 0.196707] vgaarb: loaded
    [ 0.196709] vgaarb: bridge control possible 0000:00:02.0
    [ 0.196788] PCI: Using ACPI for IRQ routing
    [ 0.197237] PCI: pci_cache_line_size set to 64 bytes
    [ 0.197407] reserve RAM buffer: 000000000009fc00 - 000000000009ffff
    [ 0.197411] reserve RAM buffer: 000000007dd31000 - 000000007fffffff
    [ 0.197573] NetLabel: Initializing
    [ 0.197576] NetLabel: domain hash size = 128
    [ 0.197579] NetLabel: protocols = UNLABELED CIPSOv4
    [ 0.197601] NetLabel: unlabeled traffic allowed by default
    [ 0.197632] HPET: 3 timers in total, 0 timers will be used for per-cpu timer
    [ 0.197640] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
    [ 0.197648] hpet0: 3 comparators, 64-bit 14.318180 MHz counter
    [ 0.210013] Switching to clocksource hpet
    [ 0.222129] pnp: PnP ACPI init
    [ 0.222158] ACPI: bus type pnp registered
    [ 0.222675] pnp 00:00: [bus 00-ff]
    [ 0.222680] pnp 00:00: [io 0x0000-0x0cf7 window]
    [ 0.222684] pnp 00:00: [io 0x0cf8-0x0cff]
    [ 0.222688] pnp 00:00: [io 0x0d00-0xffff window]
    [ 0.222692] pnp 00:00: [mem 0x000a0000-0x000bffff window]
    [ 0.222696] pnp 00:00: [mem 0x000c0000-0x000c3fff window]
    [ 0.222700] pnp 00:00: [mem 0x000c4000-0x000c7fff window]
    [ 0.222703] pnp 00:00: [mem 0x000c8000-0x000cbfff window]
    [ 0.222707] pnp 00:00: [mem 0x000cc000-0x000cffff window]
    [ 0.222711] pnp 00:00: [mem 0x000d0000-0x000d3fff window]
    [ 0.222715] pnp 00:00: [mem 0x000d4000-0x000d7fff window]
    [ 0.222718] pnp 00:00: [mem 0x000d8000-0x000dbfff window]
    [ 0.222723] pnp 00:00: [mem 0x000dc000-0x000dffff window]
    [ 0.222726] pnp 00:00: [mem 0x000e0000-0x000e3fff window]
    [ 0.222735] pnp 00:00: [mem 0x000e4000-0x000e7fff window]
    [ 0.222739] pnp 00:00: [mem 0x000e8000-0x000ebfff window]
    [ 0.222743] pnp 00:00: [mem 0x000ec000-0x000effff window]
    [ 0.222746] pnp 00:00: [mem 0x000f0000-0x000fffff window]
    [ 0.222750] pnp 00:00: [mem 0x80000000-0xfebfffff window]
    [ 0.222859] pnp 00:00: Plug and Play ACPI device, IDs PNP0a08 PNP0a03 (active)
    [ 0.222989] pnp 00:01: [mem 0xfed1c000-0xfed1ffff]
    [ 0.222993] pnp 00:01: [mem 0xfed14000-0xfed17fff]
    [ 0.222996] pnp 00:01: [mem 0xfed18000-0xfed18fff]
    [ 0.223000] pnp 00:01: [mem 0xfed19000-0xfed19fff]
    [ 0.223003] pnp 00:01: [mem 0xf0000000-0xf3ffffff]
    [ 0.223006] pnp 00:01: [mem 0xfed20000-0xfed3ffff]
    [ 0.223010] pnp 00:01: [mem 0xfed45000-0xfed8ffff]
    [ 0.223109] system 00:01: [mem 0xfed1c000-0xfed1ffff] has been reserved
    [ 0.223115] system 00:01: [mem 0xfed14000-0xfed17fff] has been reserved
    [ 0.223119] system 00:01: [mem 0xfed18000-0xfed18fff] has been reserved
    [ 0.223124] system 00:01: [mem 0xfed19000-0xfed19fff] has been reserved
    [ 0.223129] system 00:01: [mem 0xf0000000-0xf3ffffff] has been reserved
    [ 0.223134] system 00:01: [mem 0xfed20000-0xfed3ffff] has been reserved
    [ 0.223138] system 00:01: [mem 0xfed45000-0xfed8ffff] has been reserved
    [ 0.223145] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
    [ 0.223455] pnp 00:02: [io 0x0300-0x031f]
    [ 0.223473] pnp 00:02: [irq 6]
    [ 0.223541] pnp 00:02: Plug and Play ACPI device, IDs APP0001 (active)
    [ 0.223606] pnp 00:03: [io 0x0000-0x001f]
    [ 0.223610] pnp 00:03: [io 0x0081-0x0091]
    [ 0.223614] pnp 00:03: [io 0x0093-0x009f]
    [ 0.223617] pnp 00:03: [io 0x00c0-0x00df]
    [ 0.223621] pnp 00:03: [dma 4]
    [ 0.223695] pnp 00:03: Plug and Play ACPI device, IDs PNP0200 (active)
    [ 0.223710] pnp 00:04: [mem 0xff000000-0xffffffff]
    [ 0.223778] pnp 00:04: Plug and Play ACPI device, IDs INT0800 (active)
    [ 0.223883] pnp 00:05: [irq 0 disabled]
    [ 0.223893] pnp 00:05: [irq 8]
    [ 0.223897] pnp 00:05: [mem 0xfed00000-0xfed003ff]
    [ 0.224002] system 00:05: [mem 0xfed00000-0xfed003ff] has been reserved
    [ 0.224009] system 00:05: Plug and Play ACPI device, IDs PNP0103 PNP0c01 (active)
    [ 0.224028] pnp 00:06: [io 0x00f0]
    [ 0.224038] pnp 00:06: [irq 13]
    [ 0.224112] pnp 00:06: Plug and Play ACPI device, IDs PNP0c04 (active)
    [ 0.224132] pnp 00:07: [io 0x002e-0x002f]
    [ 0.224136] pnp 00:07: [io 0x004e-0x004f]
    [ 0.224139] pnp 00:07: [io 0x0061]
    [ 0.224142] pnp 00:07: [io 0x0063]
    [ 0.224145] pnp 00:07: [io 0x0065]
    [ 0.224149] pnp 00:07: [io 0x0067]
    [ 0.224151] pnp 00:07: [io 0x0070]
    [ 0.224154] pnp 00:07: [io 0x0080]
    [ 0.224157] pnp 00:07: [io 0x0092]
    [ 0.224161] pnp 00:07: [io 0x00b2-0x00b3]
    [ 0.224164] pnp 00:07: [io 0x0680-0x069f]
    [ 0.224167] pnp 00:07: [io 0x0800-0x080f]
    [ 0.224170] pnp 00:07: [io 0x0810-0x0817]
    [ 0.224173] pnp 00:07: [io 0x0400-0x047f]
    [ 0.224177] pnp 00:07: [io 0x0500-0x053f]
    [ 0.224180] pnp 00:07: [io 0x1640-0x164f]
    [ 0.224302] system 00:07: [io 0x0680-0x069f] has been reserved
    [ 0.224307] system 00:07: [io 0x0800-0x080f] has been reserved
    [ 0.224312] system 00:07: [io 0x0810-0x0817] has been reserved
    [ 0.224316] system 00:07: [io 0x0400-0x047f] has been reserved
    [ 0.224320] system 00:07: [io 0x0500-0x053f] has been reserved
    [ 0.224325] system 00:07: [io 0x1640-0x164f] has been reserved
    [ 0.224331] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
    [ 0.224346] pnp 00:08: [io 0x0070-0x0077]
    [ 0.224417] pnp 00:08: Plug and Play ACPI device, IDs PNP0b00 (active)
    [ 0.228737] pnp: PnP ACPI: found 9 devices
    [ 0.228741] ACPI: ACPI bus type pnp unregistered
    [ 0.237540] pci 0000:03:00.0: no compatible bridge window for [mem 0xfffe0000-0xffffffff pref]
    [ 0.237582] pci 0000:00:1c.0: bridge window [io 0x1000-0x0fff] to [bus 01-01] add_size 1000
    [ 0.237590] pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 01-01] add_size 200000
    [ 0.237607] pci 0000:00:1c.4: bridge window [io 0x1000-0x0fff] to [bus 02-02] add_size 1000
    [ 0.237623] pci 0000:00:1c.5: bridge window [mem 0x00100000-0x001fffff pref] to [bus 03-03] add_size 200000
    [ 0.237646] pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_size add_size 200000
    [ 0.237652] pci 0000:00:1c.5: res[15]=[mem 0x00100000-0x001fffff pref] get_res_add_size add_size 200000
    [ 0.237657] pci 0000:00:1c.0: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    [ 0.237662] pci 0000:00:1c.4: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    [ 0.237672] pci 0000:00:1c.0: BAR 15: assigned [mem 0x90800000-0x909fffff 64bit pref]
    [ 0.237678] pci 0000:00:1c.5: BAR 15: assigned [mem 0x90a00000-0x90cfffff pref]
    [ 0.237684] pci 0000:00:1c.0: BAR 13: assigned [io 0x2000-0x2fff]
    [ 0.237689] pci 0000:00:1c.4: BAR 13: assigned [io 0x3000-0x3fff]
    [ 0.237694] pci 0000:00:1c.0: PCI bridge to [bus 01-01]
    [ 0.237701] pci 0000:00:1c.0: bridge window [io 0x2000-0x2fff]
    [ 0.237710] pci 0000:00:1c.0: bridge window [mem 0x90600000-0x906fffff]
    [ 0.237718] pci 0000:00:1c.0: bridge window [mem 0x90800000-0x909fffff 64bit pref]
    [ 0.237730] pci 0000:00:1c.4: PCI bridge to [bus 02-02]
    [ 0.237736] pci 0000:00:1c.4: bridge window [io 0x3000-0x3fff]
    [ 0.237746] pci 0000:00:1c.4: bridge window [mem 0x90500000-0x905fffff]
    [ 0.237754] pci 0000:00:1c.4: bridge window [mem 0x90000000-0x900fffff 64bit pref]
    [ 0.237767] pci 0000:03:00.0: BAR 6: assigned [mem 0x90a00000-0x90a1ffff pref]
    [ 0.237772] pci 0000:00:1c.5: PCI bridge to [bus 03-03]
    [ 0.237777] pci 0000:00:1c.5: bridge window [io 0x5000-0x5fff]
    [ 0.237787] pci 0000:00:1c.5: bridge window [mem 0x90400000-0x904fffff]
    [ 0.237795] pci 0000:00:1c.5: bridge window [mem 0x90a00000-0x90cfffff pref]
    [ 0.237807] pci 0000:00:1e.0: PCI bridge to [bus 04-04]
    [ 0.237816] pci 0000:00:1e.0: bridge window [mem 0x90300000-0x903fffff]
    [ 0.237837] pci 0000:00:1c.0: enabling device (0000 -> 0003)
    [ 0.237918] pci 0000:00:1e.0: power state changed by ACPI to D0
    [ 0.237925] pci 0000:00:1e.0: power state changed by ACPI to D0
    [ 0.237934] pci 0000:00:1e.0: setting latency timer to 64
    [ 0.237942] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
    [ 0.237946] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
    [ 0.237950] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
    [ 0.237954] pci_bus 0000:00: resource 7 [mem 0x80000000-0xfebfffff]
    [ 0.237959] pci_bus 0000:01: resource 0 [io 0x2000-0x2fff]
    [ 0.237963] pci_bus 0000:01: resource 1 [mem 0x90600000-0x906fffff]
    [ 0.237967] pci_bus 0000:01: resource 2 [mem 0x90800000-0x909fffff 64bit pref]
    [ 0.237972] pci_bus 0000:02: resource 0 [io 0x3000-0x3fff]
    [ 0.237976] pci_bus 0000:02: resource 1 [mem 0x90500000-0x905fffff]
    [ 0.237980] pci_bus 0000:02: resource 2 [mem 0x90000000-0x900fffff 64bit pref]
    [ 0.237984] pci_bus 0000:03: resource 0 [io 0x5000-0x5fff]
    [ 0.237988] pci_bus 0000:03: resource 1 [mem 0x90400000-0x904fffff]
    [ 0.237992] pci_bus 0000:03: resource 2 [mem 0x90a00000-0x90cfffff pref]
    [ 0.237997] pci_bus 0000:04: resource 1 [mem 0x90300000-0x903fffff]
    [ 0.238001] pci_bus 0000:04: resource 4 [io 0x0000-0x0cf7]
    [ 0.238005] pci_bus 0000:04: resource 5 [io 0x0d00-0xffff]
    [ 0.238009] pci_bus 0000:04: resource 6 [mem 0x000a0000-0x000bffff]
    [ 0.238013] pci_bus 0000:04: resource 7 [mem 0x80000000-0xfebfffff]
    [ 0.238088] NET: Registered protocol family 2
    [ 0.238250] IP route cache hash table entries: 65536 (order: 7, 524288 bytes)
    [ 0.239170] TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
    [ 0.241419] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
    [ 0.241995] TCP: Hash tables configured (established 262144 bind 65536)
    [ 0.241999] TCP: reno registered
    [ 0.242015] UDP hash table entries: 1024 (order: 3, 32768 bytes)
    [ 0.242042] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes)
    [ 0.242207] NET: Registered protocol family 1
    [ 0.242239] pci 0000:00:02.0: Boot video device
    [ 0.242578] PCI: CLS mismatch (256 != 64), using 64 bytes
    [ 0.242662] Unpacking initramfs...
    [ 0.452648] Freeing initrd memory: 5820k freed
    [ 0.456693] audit: initializing netlink socket (disabled)
    [ 0.456719] type=2000 audit(1340724146.456:1): initialized
    [ 0.457302] HugeTLB registered 2 MB page size, pre-allocated 0 pages
    [ 0.460514] VFS: Disk quotas dquot_6.5.2
    [ 0.460597] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
    [ 0.460751] msgmni has been set to 3939
    [ 0.461070] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
    [ 0.461121] io scheduler noop registered
    [ 0.461125] io scheduler deadline registered
    [ 0.461224] io scheduler cfq registered (default)
    [ 0.461477] pcieport 0000:00:1c.0: irq 40 for MSI/MSI-X
    [ 0.461710] pcieport 0000:00:1c.4: irq 41 for MSI/MSI-X
    [ 0.461950] pcieport 0000:00:1c.5: irq 42 for MSI/MSI-X
    [ 0.462157] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
    [ 0.462166] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
    [ 0.462198] pcieport 0000:00:1c.4: Signaling PME through PCIe PME interrupt
    [ 0.462203] pci 0000:02:00.0: Signaling PME through PCIe PME interrupt
    [ 0.462210] pcie_pme 0000:00:1c.4:pcie01: service driver pcie_pme loaded
    [ 0.462242] pcieport 0000:00:1c.5: Signaling PME through PCIe PME interrupt
    [ 0.462246] pci 0000:03:00.0: Signaling PME through PCIe PME interrupt
    [ 0.462253] pcie_pme 0000:00:1c.5:pcie01: service driver pcie_pme loaded
    [ 0.462369] vesafb: mode is 1024x768x32, linelength=4096, pages=0
    [ 0.462374] vesafb: scrolling: redraw
    [ 0.462379] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
    [ 0.464035] vesafb: framebuffer at 0x80000000, mapped to 0xffffc90004980000, using 3072k, total 3072k
    [ 0.508030] Console: switching to colour frame buffer device 128x48
    [ 0.551844] fb0: VESA VGA frame buffer device
    [ 0.551863] efifb: dmi detected MacBook4,1 - framebuffer at 0x80000000 (1024x768, stride 4096)
    [ 0.551868] intel_idle: does not run on family 6 model 23
    [ 0.551930] GHES: HEST is not enabled!
    [ 0.552035] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    [ 0.552762] Linux agpgart interface v0.103
    [ 0.552879] i8042: PNP: No PS/2 controller found. Probing ports directly.
    [ 0.553759] i8042: No controller found
    [ 0.553878] mousedev: PS/2 mouse device common for all mice
    [ 0.553966] rtc_cmos 00:08: RTC can wake from S4
    [ 0.554165] rtc_cmos 00:08: rtc core: registered rtc_cmos as rtc0
    [ 0.554204] rtc0: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
    [ 0.554221] cpuidle: using governor ladder
    [ 0.554225] cpuidle: using governor menu
    [ 0.554454] TCP: cubic registered
    [ 0.554641] NET: Registered protocol family 10
    [ 0.554976] NET: Registered protocol family 17
    [ 0.554983] Registering the dns_resolver key type
    [ 0.555206] PM: Hibernation image not present or could not be loaded.
    [ 0.555216] registered taskstats version 1
    [ 0.556175] rtc_cmos 00:08: setting system clock to 2012-06-26 15:22:26 UTC (1340724146)
    [ 0.556299] Initializing network drop monitor service
    [ 0.558944] Freeing unused kernel memory: 740k freed
    [ 0.559290] Write protecting the kernel read-only data: 8192k
    [ 0.568413] Freeing unused kernel memory: 1588k freed
    [ 0.572710] Freeing unused kernel memory: 640k freed
    [ 0.586045] udevd[40]: starting version 185
    [ 0.590818] [drm] Initialized drm 1.1.0 20060810
    [ 0.592306] agpgart-intel 0000:00:00.0: Intel 965GM Chipset
    [ 0.592621] agpgart-intel 0000:00:00.0: detected gtt size: 524288K total, 262144K mappable
    [ 0.594306] agpgart-intel 0000:00:00.0: detected 16384K stolen memory
    [ 0.594543] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0x80000000
    [ 0.595388] input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input0
    [ 0.595444] ACPI: Lid Switch [LID0]
    [ 0.595539] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1
    [ 0.595547] ACPI: Power Button [PWRB]
    [ 0.595632] input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input2
    [ 0.595639] ACPI: Sleep Button [SLPB]
    [ 0.595763] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
    [ 0.595769] ACPI: Power Button [PWRF]
    [ 0.596508] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input4
    [ 0.596517] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
    [ 0.602545] i915 0000:00:02.0: setting latency timer to 64
    [ 0.749351] i915 0000:00:02.0: irq 43 for MSI/MSI-X
    [ 0.749367] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
    [ 0.749370] [drm] Driver supports precise vblank timestamp query.
    [ 0.749462] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
    [ 1.117606] [drm] initialized overlay support
    [ 1.299854] checking generic (80000000 300000) vs hw (80000000 10000000)
    [ 1.299860] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver
    [ 1.299886] Console: switching to colour dummy device 80x25
    [ 1.301293] fbcon: inteldrmfb (fb0) is primary device
    [ 1.430434] Console: switching to colour frame buffer device 160x50
    [ 1.435865] fb0: inteldrmfb frame buffer device
    [ 1.435868] drm: registered panic notifier
    [ 1.435878] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
    [ 1.456696] Refined TSC clocksource calibration: 2393.999 MHz.
    [ 1.456705] Switching to clocksource tsc
    [ 1.821716] usbcore: registered new interface driver usbfs
    [ 1.821753] usbcore: registered new interface driver hub
    [ 1.826806] usbcore: registered new device driver usb
    [ 1.827520] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    [ 1.827588] ehci_hcd 0000:00:1a.7: setting latency timer to 64
    [ 1.827594] ehci_hcd 0000:00:1a.7: EHCI Host Controller
    [ 1.827633] ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1
    [ 1.827675] ehci_hcd 0000:00:1a.7: debug port 1
    [ 1.831556] ehci_hcd 0000:00:1a.7: cache line size of 64 is not supported
    [ 1.831587] ehci_hcd 0000:00:1a.7: irq 21, io mem 0x90704c00
    [ 1.842320] SCSI subsystem initialized
    [ 1.845102] ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00
    [ 1.845354] hub 1-0:1.0: USB hub found
    [ 1.845362] hub 1-0:1.0: 4 ports detected
    [ 1.845549] ehci_hcd 0000:00:1d.7: setting latency timer to 64
    [ 1.845555] ehci_hcd 0000:00:1d.7: EHCI Host Controller
    [ 1.845572] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2
    [ 1.845613] ehci_hcd 0000:00:1d.7: debug port 1
    [ 1.847254] uhci_hcd: USB Universal Host Controller Interface driver
    [ 1.850589] ehci_hcd 0000:00:1d.7: cache line size of 64 is not supported
    [ 1.850624] ehci_hcd 0000:00:1d.7: irq 20, io mem 0x90704800
    [ 1.851193] libata version 3.00 loaded.
    [ 1.860054] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
    [ 1.860280] hub 2-0:1.0: USB hub found
    [ 1.860289] hub 2-0:1.0: 6 ports detected
    [ 1.860472] uhci_hcd 0000:00:1a.0: setting latency timer to 64
    [ 1.860478] uhci_hcd 0000:00:1a.0: UHCI Host Controller
    [ 1.860494] uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3
    [ 1.860539] uhci_hcd 0000:00:1a.0: irq 20, io base 0x000060c0
    [ 1.860750] hub 3-0:1.0: USB hub found
    [ 1.860757] hub 3-0:1.0: 2 ports detected
    [ 1.860892] uhci_hcd 0000:00:1a.1: setting latency timer to 64
    [ 1.860898] uhci_hcd 0000:00:1a.1: UHCI Host Controller
    [ 1.860912] uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4
    [ 1.860965] uhci_hcd 0000:00:1a.1: irq 16, io base 0x000060a0
    [ 1.861172] hub 4-0:1.0: USB hub found
    [ 1.861178] hub 4-0:1.0: 2 ports detected
    [ 1.861312] uhci_hcd 0000:00:1d.0: setting latency timer to 64
    [ 1.861318] uhci_hcd 0000:00:1d.0: UHCI Host Controller
    [ 1.861332] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 5
    [ 1.861366] uhci_hcd 0000:00:1d.0: irq 16, io base 0x00006080
    [ 1.861578] hub 5-0:1.0: USB hub found
    [ 1.861585] hub 5-0:1.0: 2 ports detected
    [ 1.861717] uhci_hcd 0000:00:1d.1: setting latency timer to 64
    [ 1.861723] uhci_hcd 0000:00:1d.1: UHCI Host Controller
    [ 1.861744] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 6
    [ 1.861795] uhci_hcd 0000:00:1d.1: irq 18, io base 0x00006060
    [ 1.862003] hub 6-0:1.0: USB hub found
    [ 1.862010] hub 6-0:1.0: 2 ports detected
    [ 1.862142] uhci_hcd 0000:00:1d.2: setting latency timer to 64
    [ 1.862148] uhci_hcd 0000:00:1d.2: UHCI Host Controller
    [ 1.862165] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 7
    [ 1.862200] uhci_hcd 0000:00:1d.2: irq 21, io base 0x00006040
    [ 1.862411] hub 7-0:1.0: USB hub found
    [ 1.862417] hub 7-0:1.0: 2 ports detected
    [ 1.862917] ata_piix 0000:00:1f.1: version 2.13
    [ 1.862932] ata_piix 0000:00:1f.1: power state changed by ACPI to D0
    [ 1.862937] ata_piix 0000:00:1f.1: power state changed by ACPI to D0
    [ 1.862993] ata_piix 0000:00:1f.1: setting latency timer to 64
    [ 1.869158] scsi0 : ata_piix
    [ 1.874884] scsi1 : ata_piix
    [ 1.875449] ata1: PATA max UDMA/100 cmd 0x6108 ctl 0x6124 bmdma 0x60e0 irq 21
    [ 1.875454] ata2: PATA max UDMA/100 cmd 0x6100 ctl 0x6120 bmdma 0x60e8 irq 21
    [ 1.875665] ata_piix 0000:00:1f.2: MAP [ P0 -- -- -- ]
    [ 1.875722] ata_piix 0000:00:1f.2: setting latency timer to 64
    [ 1.881780] scsi2 : ata_piix
    [ 1.887944] scsi3 : ata_piix
    [ 1.888739] ata3: SATA max UDMA/133 cmd 0x60f8 ctl 0x611c bmdma 0x6020 irq 18
    [ 1.888745] ata4: SATA max UDMA/133 cmd 0x60f0 ctl 0x6118 bmdma 0x6028 irq 18
    [ 2.033862] ata1.00: ATAPI: MATSHITADVD-R UJ-867, HB01, max UDMA/66
    [ 2.065117] ata1.00: configured for UDMA/66
    [ 2.065887] ata3.00: ATA-8: Hitachi HTS542516K9SA00, BBCAC3GP, max UDMA/133
    [ 2.065893] ata3.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 0/32)
    [ 2.067318] scsi 0:0:0:0: CD-ROM MATSHITA DVD-R UJ-867 HB01 PQ: 0 ANSI: 5
    [ 2.077869] ata3.00: configured for UDMA/133
    [ 2.078045] scsi 2:0:0:0: Direct-Access ATA Hitachi HTS54251 BBCA PQ: 0 ANSI: 5
    [ 2.087306] sr0: scsi3-mmc drive: 62x/62x writer cd/rw xa/form2 cdda tray
    [ 2.087313] cdrom: Uniform CD-ROM driver Revision: 3.20
    [ 2.088645] sr 0:0:0:0: Attached scsi CD-ROM sr0
    [ 2.093226] sd 2:0:0:0: [sda] 312581808 512-byte logical blocks: (160 GB/149 GiB)
    [ 2.093312] sd 2:0:0:0: [sda] Write Protect is off
    [ 2.093318] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
    [ 2.093371] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [ 2.184704] sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 >
    [ 2.184707] sda3: <bsd:bad subpartition - ignored
    [ 2.184709] bad subpartition - ignored
    [ 2.184710] bad subpartition - ignored
    [ 2.184712] bad subpartition - ignored
    [ 2.184713] >
    [ 2.185557] sd 2:0:0:0: [sda] Attached SCSI disk
    [ 2.260045] usb 2-4: new high-speed USB device number 2 using ehci_hcd
    [ 2.770036] usb 3-1: new full-speed USB device number 2 using uhci_hcd
    [ 2.948125] usbhid 3-1:1.0: couldn't find an input interrupt endpoint
    [ 2.948381] usbcore: registered new interface driver usbhid
    [ 2.948385] usbhid: USB HID core driver
    [ 3.170028] usb 7-1: new low-speed USB device number 2 using uhci_hcd
    [ 3.179293] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
    [ 3.576705] usb 7-2: new full-speed USB device number 3 using uhci_hcd
    [ 5.022890] udevd[198]: starting version 185
    [ 5.426262] applesmc: SIS!ui16\xffffffc0\xffffffa6: read arg fail
    [ 5.562551] applesmc: key=220 fan=1 temp=10 acc=1 lux=0 kbd=0
    [ 5.562558] applesmc: init_smcreg() took 50 ms
    [ 5.584285] input: applesmc as /devices/platform/applesmc.768/input/input5
    [ 5.658889] lib80211: common routines for IEEE802.11 drivers
    [ 5.658894] lib80211_crypt: registered algorithm 'NULL'
    [ 5.711977] cfg80211: Calling CRDA to update world regulatory domain
    [ 5.924357] wl: module license 'Mixed/Proprietary' taints kernel.
    [ 5.924364] Disabling lock debugging due to kernel taint
    [ 5.946193] INFO @wl_cfg80211_attach : Registered CFG80211 phy
    [ 6.001836] lib80211_crypt: registered algorithm 'TKIP'
    [ 6.002152] eth0: Broadcom BCM4328 802.11 Hybrid Wireless Controller 5.100.82.112
    [ 6.084085] Linux media interface: v0.10
    [ 6.133183] iTCO_vendor_support: vendor-support=0
    [ 6.134458] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07
    [ 6.134601] iTCO_wdt: Found a ICH8M TCO device (Version=2, TCOBASE=0x0460)
    [ 6.134703] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
    [ 6.156626] ACPI: Battery Slot [BAT0] (battery absent)
    [ 6.163544] ACPI: AC Adapter [ADP1] (on-line)
    [ 6.164216] ACPI: Requesting acpi_cpufreq
    [ 6.173706] Monitor-Mwait will be used to enter C-1 state
    [ 6.178506] Monitor-Mwait will be used to enter C-2 state
    [ 6.183424] Monitor-Mwait will be used to enter C-3 state
    [ 6.183457] Marking TSC unstable due to TSC halts in idle
    [ 6.183507] ACPI: acpi_idle registered with cpuidle
    [ 6.183963] Switching to clocksource hpet
    [ 6.210896] ACPI Warning: 0x000000000000efa0-0x000000000000efbf SystemIO conflicts with Region \_SB_.PCI0.SBUS.SMBI 1 (20120320/utaddress-251)
    [ 6.210909] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
    [ 6.242033] input: PC Speaker as /devices/platform/pcspkr/input/input6
    [ 6.275396] microcode: CPU0 sig=0x10676, pf=0x80, revision=0x60c
    [ 6.338786] Linux video capture interface: v2.00
    [ 6.426865] uvcvideo: Found UVC 1.00 device Built-in iSight (05ac:8501)
    [ 6.429319] uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling workaround.
    [ 6.429831] usbcore: registered new interface driver uvcvideo
    [ 6.429835] USB Video Class driver (1.1.1)
    [ 6.496844] firewire_ohci 0000:04:03.0: added OHCI v1.0 device as card 0, 8 IR + 8 IT contexts, quirks 0x0
    [ 6.587003] sky2: driver version 1.30
    [ 6.587217] sky2 0000:03:00.0: Yukon-2 EC Ultra chip revision 3
    [ 6.587761] sky2 0000:03:00.0: irq 44 for MSI/MSI-X
    [ 6.588473] sky2 0000:03:00.0: eth1: addr 00:22:41:21:43:0c
    [ 6.654740] microcode: CPU1 sig=0x10676, pf=0x80, revision=0x60c
    [ 6.655770] microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
    [ 6.661489] snd_hda_intel 0000:00:1b.0: irq 45 for MSI/MSI-X
    [ 6.700987] udevd[214]: renamed network interface eth0 to wlan0
    [ 6.824841] hda_codec: ALC889A: SKU not ready 0x400000f0
    [ 6.827442] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input7
    [ 6.848101] input: HDA Intel Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input8
    [ 6.850714] input: HDA Intel Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
    [ 6.942266] appletouch: Geyser mode initialized.
    [ 6.942380] input: appletouch as /devices/pci0000:00/0000:00:1d.2/usb7/7-2/7-2:1.1/input/input10
    [ 6.942768] usbcore: registered new interface driver appletouch
    [ 6.996893] firewire_core 0000:04:03.0: created device fw0: GUID 002241fffe41d624, S400
    [ 7.131526] apple 0003:05AC:8242.0001: hiddev0,hidraw0: USB HID v1.11 Device [Apple Computer, Inc. IR Receiver] on usb-0000:00:1d.2-1/input0
    [ 7.135766] input: Apple Computer Apple Internal Keyboard / Trackpad as /devices/pci0000:00/0000:00:1d.2/usb7/7-2/7-2:1.0/input/input11
    [ 7.136230] apple 0003:05AC:0229.0002: input,hidraw1: USB HID v1.11 Keyboard [Apple Computer Apple Internal Keyboard / Trackpad] on usb-0000:00:1d.2-2/input0
    [ 7.139354] input: Apple Computer Apple Internal Keyboard / Trackpad as /devices/pci0000:00/0000:00:1d.2/usb7/7-2/7-2:1.2/input/input12
    [ 7.139526] apple 0003:05AC:0229.0003: input,hidraw2: USB HID v1.11 Device [Apple Computer Apple Internal Keyboard / Trackpad] on usb-0000:00:1d.2-2/input2
    [ 7.423516] usb 3-1: USB disconnect, device number 2
    [ 7.650081] usb 3-1: new full-speed USB device number 3 using uhci_hcd
    [ 8.322211] Bluetooth: Core ver 2.16
    [ 8.322655] NET: Registered protocol family 31
    [ 8.322660] Bluetooth: HCI device and connection manager initialized
    [ 8.322665] Bluetooth: HCI socket layer initialized
    [ 8.322669] Bluetooth: L2CAP socket layer initialized
    [ 8.322680] Bluetooth: SCO socket layer initialized
    [ 8.359817] usbcore: registered new interface driver btusb
    [ 9.183365] EXT4-fs (sda2): re-mounted. Opts: (null)
    [ 9.336886] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
    [ 9.377553] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem
    [ 9.380170] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null)
    [ 9.497613] Adding 4184928k swap on /dev/sda5. Priority:-1 extents:1 across:4184928k
    [ 11.804445] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    [ 11.845740] Bluetooth: RFCOMM TTY layer initialized
    [ 11.845751] Bluetooth: RFCOMM socket layer initialized
    [ 11.845755] Bluetooth: RFCOMM ver 1.11
    [ 12.221084] fbsplashd.stati[78]: segfault at 2c ip 000000000040579b sp 00007f2267333d00 error 4 in fbsplashd.static (deleted)[400000+233000]
    [ 24.154605] sky2 0000:03:00.0: eth1: enabling interface
    [ 24.155329] ADDRCONF(NETDEV_UP): eth1: link is not ready
    [ 28.831988] EXT4-fs (sda2): re-mounted. Opts: commit=0
    [ 28.933444] EXT4-fs (sda6): re-mounted. Opts: commit=0
    [ 29.363373] wlan0: no IPv6 routers present
    [ 30.487575] sky2 0000:03:00.0: eth1: disabling interface
    [ 30.500233] sky2 0000:03:00.0: eth1: enabling interface
    [ 30.501015] ADDRCONF(NETDEV_UP): eth1: link is not ready
    [ 40.563473] wlan0: no IPv6 routers present
    [ 45.535875] fuse init (API version 7.18)
    [ 70.827136] ISO 9660 Extensions: Microsoft Joliet Level 3
    [ 70.867639] ISO 9660 Extensions: RRIP_1991A
    [ 398.754336] ip_tables: (C) 2000-2006 Netfilter Core Team
    [ 398.776167] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
    [ 422.037689] Inbound IN=wlan0 OUT= MAC=00:21:e9:dc:77:c2:00:16:0a:19:9d:62:08:00 SRC=173.194.70.125 DST=192.168.50.100 LEN=78 TOS=0x00 PREC=0x00 TTL=42 ID=16396 PROTO=TCP SPT=5222 DPT=38798 WINDOW=369 RES=0x00 ACK PSH URGP=0
    [ 422.311888] Inbound IN=wlan0 OUT= MAC=00:21:e9:dc:77:c2:00:16:0a:19:9d:62:08:00 SRC=173.194.70.125 DST=192.168.50.100 LEN=78 TOS=0x00 PREC=0x00 TTL=42 ID=16397 PROTO=TCP SPT=5222 DPT=38798 WINDOW=369 RES=0x00 ACK PSH URGP=0
    [ 422.859975] Inbound IN=wlan0 OUT= MAC=00:21:e9:dc:77:c2:00:16:0a:19:9d:62:08:00 SRC=173.194.70.125 DST=192.168.50.100 LEN=78 TOS=0x00 PREC=0x00 TTL=42 ID=16398 PROTO=TCP SPT=5222 DPT=38798 WINDOW=369 RES=0x00 ACK PSH URGP=0
    [ 423.955325] Inbound IN=wlan0 OUT= MAC=00:21:e9:dc:77:c2:00:16:0a:19:9d:62:08:00 SRC=173.194.70.125 DST=192.168.50.100 LEN=78 TOS=0x00 PREC=0x00 TTL=42 ID=16399 PROTO=TCP SPT=5222 DPT=38798 WINDOW=369 RES=0x00 ACK PSH URGP=0
    [ 426.147338] Inbound IN=wlan0 OUT= MAC=00:21:e9:dc:77:c2:00:16:0a:19:9d:62:08:00 SRC=173.194.70.125 DST=192.168.50.100 LEN=78 TOS=0x00 PREC=0x00 TTL=42 ID=16400 PROTO=TCP SPT=5222 DPT=38798 WINDOW=369 RES=0x00 ACK PSH URGP=0
    [ 430.531638] Inbound IN=wlan0 OUT= MAC=00:21:e9:dc:77:c2:00:16:0a:19:9d:62:08:00 SRC=173.194.70.125 DST=192.168.50.100 LEN=78 TOS=0x00 PREC=0x00 TTL=42 ID=16401 PROTO=TCP SPT=5222 DPT=38798 WINDOW=369 RES=0x00 ACK PSH URGP=0
    00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 03)
    00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 03)
    00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (secondary) (rev 03)
    00:1a.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03)
    00:1a.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03)
    00:1a.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03)
    00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
    00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)
    00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 03)
    00:1c.5 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 6 (rev 03)
    00:1d.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03)
    00:1d.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03)
    00:1d.2 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03)
    00:1d.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03)
    00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
    00:1f.0 ISA bridge: Intel Corporation 82801HM (ICH8M) LPC Interface Controller (rev 03)
    00:1f.1 IDE interface: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03)
    00:1f.2 IDE interface: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) SATA Controller [IDE mode] (rev 03)
    00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03)
    02:00.0 Network controller: Broadcom Corporation BCM4321 802.11a/b/g/n (rev 03)
    03:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8058 PCI-E Gigabit Ethernet Controller (rev 13)
    04:03.0 FireWire (IEEE 1394): LSI Corporation FW322/323 [TrueFire] 1394a Controller (rev 61)
    /etc/rc.conf:
    # /etc/rc.conf - Main Configuration for Arch Linux
    # See 'man 5 rc.conf' for more details
    # LOCALIZATION
    HARDWARECLOCK="UTC"
    TIMEZONE="Europe/Skopje"
    KEYMAP="us"
    CONSOLEFONT=
    CONSOLEMAP=
    LOCALE="en_GB.UTF-8"
    DAEMON_LOCALE="yes"
    USECOLOR="yes"
    # HARDWARE
    MODULES=(applesmc wl uvcvideo)
    USEDMRAID="no"
    USEBTRFS="no"
    USELVM="no"
    # NETWORKING
    HOSTNAME=stefan.local
    interface=
    address=
    netmask=
    broadcast=
    gateway=
    NETWORK_PERSIST="no"
    # DAEMONS
    DAEMONS=(syslog-ng sensors dbus network @firestarter @bluetooth crond cmp-daemon gdm @wicd alsa)
    Thanks

    Army wrote:
    This might not help you a lot, but if you want a stable system, try using packages from the repo wherever possible, look at the news before you update your system and don't mess things up (like bad configuration etc.).
    When it comes to performance, you won't gain much by compiling linux by yourself! Just use the linux package from [core] or if you want a bit more performance, install the ck-kernel from
    [repo-ck]
    Server = http://repo-ck.com/$arch
    (this has to go to the bottom of /etc/pacman.conf)
    (use that one which is best for your cpu (in your case this might be the package linux-ck-corex).
    Hmmm, Linux-ck-corex doesn't even load.. I am now trying to install the generic one. Hope it works.
    Edit: I will first try linux-lqx...
    Last edited by exapplegeek (2012-06-26 18:33:31)

  • How to tell between SATA2 and SATA3 hard drives?

    Hello all.
    Googled my little fingers off and couldn't find a clear answer to this ...
    How (the heck) do you find out if a hard drive is SATA3 or SATA2 and/or how do you find out if a hard driveis 6Gb/s or 3Gb/s?
    The situation: WIth the price coming down on SSD drives, I finally caved and bought an SSD to upgrade my 2011 Macbook Pro.  First up, wow ... I realize this SSD drive is brand new and performing at it's best but holy doodle!  It's so fast it feels like a whole new computer. Great upgrade, well worth the money.
    Anyways, my plan was to install the SSD as the primary drive and run the OS and applications off it.  Then take old main HD (a 1TB, 72000rpm HD) and rotate that into the optical bay (for file storage).  I am using the OWC data-doubler kit and that's where the problems started.  The data doubler rack is fine but apparently I can't put a SATA3 (?) drive in the optical bay ...  only SATA2 drives. Something about the optical bay not being able to handle 6Gb/s and only 3Gb/s.
    I might have an out here.  I have three other 2.5" HDs in external USB enclosures (Western Digital My Passport, Freecom etc.) that if I can successfully identify as SATA2 and/or 3Gb/s then I will break open and use that in the optical bay.  Before breaking the enclusore open, I would ideally like to positively identify the drive as having the proper specs.  These enclosures don't appear to be designed to be opened and closed again so it might be a one way mission if I break them open ;-)
    I plugged in the drives and tried System Information and wasn't able to spot anything (maybe I wasn't paying close enough attention)
    If anyone can tell me if it's possible to plug these USB drives and indentify them as SATA2 / SATA3 or 6Gb/s / 3Gb/s that would be awesome.
    Tnx!

    chillpill 
       **** so much for that on the Western Digitals.  The interface is USB3
    goodness, yes, youve got one of those OLD WD drives that has the controller board AND USB all as ONE SINGLE UNIT
    write that HD off. 
    your "classique"  HD here:
    http://karlsbakk.net/bilder/WD10TMVW/wd10tmvw-2.jpg
    tjk Wisconsin 
    So being USB3 doesn't tell us anything at all.
    Yeah it does, it tells me its one of those OLD HD that was made with the "lets save 2 cents and make it all one piece" philosophical designs.

  • What is up with the Marvell 9123 Raid Controller? P55-GD85

    Hi all,
    I recently bought an MSI P55-GD85 - I updated the bios to the latest 1.3.  Everything is good and I love it. 
    The problem came when I bought an SSD.  First of all, I NEVER wanted to use the Marvell Sata ports (white one, Port 7 and 8) because I don't have any SATA III drives but right now It seems that I don't have a choice because of the SSD.
    Originally, I ran Raid 0 on my 2 x Samsung F3 Spinpoint 500GB which is plugged on the P55 sata ports (ports 5 and 6).  Of course that means that the P55 sata controller is running in Raid Mode. 
    Now the SSD came to play and wanted to use it as boot drive. I plugged it into SATA 0 (P55).  I decided to run some benchmarks and tests BEFORE installing Windows 7 on it (still keeping my Raid 0 Samsungs).  I ran some tests and it was amazing.  ATTO and HD Tune pro hits the spec speeds of the SSD.  For the sake of it I also ran test on the Samsung that I have.  In raid 0, I hit 280mbps reads speeds/13.5ms seek which is very very good.
    Now the problem:
    Even though I have a Single SSD drive, TRIM does NOT work because it is connected to the same P55 SATA ports where my Samsung Raid is connected - which is of course, in Raid mode.  As far as I know TRIM will only work in AHCI mode for the P55 ICH10R chip.
    I don't want to give up my Raid setup so I though maybe I should connect it to the Marvell Raid.  I had to reformat and rebuild the RAID volume in Marvell and reinstall Windows 7.  This time I also installed Windows 7 on my SSD so I can benchmark my Raid 0 (marvell controller).  To my shock these are the results:
    Using HD Tune Pro:
    P55 Raid - 2 x 500gb samsung F3s
    Max Read - 280mbps
    Min Read - 220mbps
    Average - Around 240mbps
    seek - 13.5
    Marvell Raid 0 - 2 x 500gb samsung f3s
    Max Read - 160mbps
    Min Read - 113mbps
    Average - Around 130mbps
    seek - 15.6ms
    I made sure that all drivers are updated (unless I need to flash the BIOS for the Marvell chip - is that possible)?  I'm in the office right now as I can't remember the exact version of the marvell, I think it is 1.0.0.1013 (I'll edit as soon as I go home).
    As you can see, the performance is like half!  Which is unacceptable.
    Then, just for tests, I tried to plug in my Single SSD to the Marvell white Port (port 7) and ran some benchmarks.
    Here are the results:
    P55 ports Single - Kingston 64gb SSDNow V series
    Max reads: 180mbps
    Min reads: 130mbps
    Ave reads: 140ish
    Seek: .2ms
    - it did not hit the 210mbps theoretical speed that it pretty decent IMO
    Marvell Sata ports - Single Kingston 64gb SSDNow V series
    Max reads: 130mbps
    Min reads: 110mbps
    Ave reads: 120ish mbps
    seek: .3
    I also noticed real world performance (like boot times and application snappiness) differences between Marvell and the ICH p55 controllers.  The Marvell does not perform well compared to the intel one.
    BTW, I also tried the Jmicron 36x Sata port 9 and it is so much worse.
    Is the Marvell Controller really that slower compared to the Intel Controllers?
    Could any one please help me to improve my RAID and/or AHCI mode of my Marvel; controller?  Also, does TRIM work with Marvell Controllers in AHCI mode?
    Thank you!
    Specs:
    Core i7 870 @ stock
    P55-GD85 BIOS 1.3 (from MSI website)
    EVGA GTX 460 768mb SC
    4 x 2gb G.Skill Ripjaws 1600 (XMP enabled) - runs fine
    2 x 500GB Samsung F3 Spinpoint
    1 x Kingston 64gb SSDNow V SSD
    DVDrom
    Corsair 650TX
    Mugen 2 Rev B
    Thermaltake Armor A90

    Quote from: Jack t.N. on 11-September-10, 02:05:06
    The Marvell Controller Firmware Updates will come as part of the system BIOS Update.  I am not sure if this has to do with the Controller Firmware or the driver version used.  But in any case, I suggest you contact MSI Technical Support and report your findings so they can check it:
    http://support.msi.com/
    Thank you for your reply.
    I hope it is nothing serious. I have to make screenshots and make a better documentation of my findings before I send it to them.
    How about the others that use Marvell 9123 in SATA II or SATA II RAID-0?  Am I just alone? 

  • Is this slow performance when importing CD's into iTunes ?

    Hi,
    My new iMac 20" arrived this weekend. Since then I've been getting acquainted, being new to Macs. I wanted to build up my iTunes library, so I grabbed a box of my CDs and began importing them one by one. I was expecting my new iMac to really fly through them after reading the reviews of how much faster the new Core 2 Duo are over previous iMacs. I remember a table of stats in the MacWorld reviews, and for iTunes test, these machines were clocked at under 2 minutes for whatever it was they ripped in iTunes. YMMV certainly applies, but I was setting my expectation that my iMac could rip a CD in 2 - 3 minutes.
    Umm, my experience is way off that. In fact, I would say my iMac took about as long to rip a CD as my 7 year old Dell PC with 256 MB of mem and a first gen Pent 5.
    I decided to pick a CD and time how long it takes to import on my iMac, then take same CD and time how long it takes to import into iTunes on his new PC.
    CD - Rush, Moving Pictures, 7 songs, 39.8 min, 403.1 MB
    Encoding - AAC, 192 kbps
    My rig - iMac 20", 2 GB RAM, 256 MB VRAM, Core 2 Duo and 250 HB with latest version of OS X
    My son's rig - intel D955xbklkr socket 775 atx mobo, intel pentium D840 3.2 GHz processor, Corsair twinx pc5400 DDR2 667 Mhz mem ( 2 x 1024 mb ), HD - Seagate 250 GB SATA2 7K with 16 MB buffer, Pioneer DVR-111D DVD burner, and XFX 7600GS extreme graphics card, Win XP Pro, SP2 ( we built this beast with gaming in mind, with his own money ) * the CPU and memory are NOT overclocked and no other tweaks. just build it, install it and run it.
    The results:
    iMac - 7 minutes
    PC - 2 minutes
    I ran the import twice on each machine and came up with the same results.
    Neither machine was running anything else at the time.
    Granted there are some differences between the machines that should account for some differences, especially on the hard drive, with SATA2 and a nice 16 MB cache ( it's one sweet HD ) on the PC, but this difference is huge. We're not talking 20, 40 or 60 % faster on the PC. This was > 3x faster, so basically over 300% faster.
    Anyone have an idea ? Without digging into the specs, I'd say the DVD drives should be able to read equally fast, the Core 2 Duo 2.1 GHz with 4 MB cache should be equal if not superior to the older, D 820 3.2 GHz, the memory is the same speed, but I'm not sure about system bus speed on the P C ( 800 MHz ? ). Graphics cards don't factor into this equation, but the HD probably plays a big role, and I think the Seagate in my son's PC has the iMac beat hands down.
    What are other iMac C2D owners seeing for average import times ?
    Thanks,
    Bill

    Trevor,
    When you say your superdrive rips, the import speeds are typically around 20x, what encoding method and bit rate are you using ?
    I imported another CD and watched for what import speed numbers were displayed. Routinely, they hovered around 8x and sometimes up to 12 or 13x, but never higher. I was told by someone at our local user's group meeting that ripping at AAC 192kbps was a double-pass, I think that was the words they used, and therefore slower. ( Many members thought 7 minutes to rip was typical ) I'm not so sure if that means the drive will only spin at half it's rated max speed ? Anyway, I walked over to my son's PC with the CD and ripped it at AAC 192kbps to his iTunes library. The numbers I saw were from 18x to frequently 23, 24 and sometimes briefly to about 26x. His drive has a max of 40x. By my reasoning, anything that would cause iTunes to rip this CD at a slower speed, whether due to the encoding rate or the CD's surface condition, should affect both computers equally, yes ? Yet the drive on the PC performed on average at twice the rate of the iMac. I think it's safe to say the rip speed is comfortably within the operating margins of both drives.
    I'm not yet fully convinced this is normal for an iMac. My CD are in excellent shape. I'm the only one who uses them and I handle them with about as much care as the old audiofiles used to when they handled their vinyl LPs ( well, at least not as far as wearing cotton gloves and sweeping the dust off ). Most of them have absolutely no visible scratches or oily finger prints on their surfaces. I might experiment and see what rates I get if I use MP3 or a lower bit rate for AAC.
    Bill

  • Photoshop CS5 Users - Performance Checks Wanted From You

    A few days ago, while discussing various system configurations in answer to posts asking about what's best in new computers, it occurred to me that while we all know our own computers pretty well, it's practically impossible, without a whole bunch of different systems to work with on hand, to judge what system works best with Photoshop.  Is more cores better?  A superduper video card?  Huge RAM?
    Got a few minutes?
    I propose we try a few "real world" things with Photoshop CS5 on our systems and report how quickly/interactively it does them, as well as our system configurations, in an attempt to understand what works best.  This isn't a "one upsmanship" contest, but just a poll to see what systems really blaze through Photoshop work.
    Let's try to keep the list of "some things" fairly small, so we can all easily try them.  And the timing isn't too critical... Use a stopwatch if you can, or just watch the second hand on your watch or a clock and guestimate the timing to the nearest second.
    List these things about your system:
    A. Your architecture (PC / Mac) and what OS you're running.
    B.  Number of processors / processor models / GHz speed.
    C.  RAM size, speed.
    D.  Hard drives (OS, Photo storage, Photoshop scratch), their sizes and speeds.
    E.  Video card (model, graphics memory on board).
    F.  Your Photoshop Preferences settings - Amount of RAM you've allotted Photoshop, whether you have OpenGL enabled, scratch disk allocations.
    Here are the things I think might be useful for multiple people to try and let us know the time it takes:
    1.  Cold start Photoshop, from where it is not running.  How long does this take from start to everything on the screen painted and ready to work?  Do it several times.  If you use both the 32 bit version and the 64 bit version, see if there's a difference in startup time for each.  This test represents how long you'll have to wait when inspiration hits you and before you can start working.
    2. Create a big, new RGB image, 10000 x 8000 pixels in size, 16 bits/channel.  Time how long it takes to File - Save As a .PSD in the location you often save files.  Make sure you're set for Maximum Compatibility for saving PSDs.  This gives your disk subsystem a bit of a workout.
    3. Choose a round brush, set the Hardness to 0% (i.e., as fuzzy as possible), Spacing down to 10%, disable all the dynamics, and set the foreground color to something other than the background color of your image so you can see your strokes.  How do brush strokes on your screen keep up with you interactively under each of the following conditions?  If not, how long does it seem to take to catch up to where you just painted?  Does it follow everywhere you moved your mouse, or at some point start to skip places where your mouse went if you paint quickly?
    3a. Brush Size 100px.
    3b. Brush Size 200px.
    3c. Brush Size 300px.
    3d. Brush Size 400px.
    3e. Brush Size 600px.
    3f. Brush Size 1000px.
    3g. How big does the Brush Size have to be at 10% spacing and 0% hardness before it gets too laggy to be practically useful without slowing your strokes down hugely.
    4.  Filter - Blur - Lens Blur.  Change all the controls to 0 then the Radius to 20 pixels and time how long it takes to fill the preview with the image (all checkerboard gone).  You can cancel the Blur filter after the display is filled.  This is a single-threaded plug-in.
    5.  How long does it take to complete an Unsharp Mask on the image you've painted, using a setting of 250% amount, 250.0 pixel radius, 0 levels?  Time how long it takes after hitting the OK button to Photoshop being ready for you to do something else.  This is a multi-threaded plug-in.
    You can go ahead and close the above image after the Unsharp Mask operation.
    6. How long does it take to convert a Canon EOS 7D and a Nikon D7000 image with default settings, between hitting the [Open] button in Camera Raw and the image appearing in Photoshop to be ready to edit?  You can find raw files online to try with.  This is where I got the ones I tried:
    http://www.imaging-resource.com/PRODS/E7D/E7DFARI00100.CR2.HTM
    http://www.imaging-resource.com/PRODS/D7000/D7000FARI00100.NEF.HTM
    Please don't be shy about posting your results. 
    Your computer is what it is and there's NOTHING to be ashamed of.  Some are going to be faster than others at different things, and I think it will be really enlightening to see how the different system architectures handle these operations.  It can be a more or less objective way to see what architectures really do give great Photoshop performance.  Then when people ask "what's the best architecture" to get to run Photoshop, we can respond with more confidence and point them to this thread.
    I'll post my own results in a bit.
    Thanks!
    -Noel

    Here's my system in a nutshell:
    A.  Dell Precision T5400 PC Workstation running Windows 7 x64 Ultimate.  I have two 1600 x 1200 pixel Dell 2001FP display monitors.
    B.  2 Intel Xeon X5460 3.16 GHz processors with 12M cache and 4 cores each (8 cores total in the system).
    C.  16 GB of 1333 MHz DDR2 RAM in 8 x 2 GB DIMMs, which provides quad channel access.
    D.  Drive C: is 2 x 1 TB Western Digital RE4 SATA drives in RAID 0, Drive D: is a Hitachi 1 TB SATA drive.  All are 7200 RPM, and using SATA2 connections.
    E.  Video card is ATI Radeon HD 5670 with 1 GB GDDR5 memory, running the ATI Catalyst 11.12 driver.
    F.  Photoshop 32 bit set to use 100% RAM (3255 MB), OpenGL disabled.  Photoshop 64 bit limited at 95% RAM (13962 MB), OpenGL enabled, Normal mode.
    Here are my test results:
    1.  Photoshop 32 bit took 10 seconds initially to come up, then after closing it it took between 4 and 5 seconds to come up on subsequent cold starts.
         Photoshop 64 bit took 6 seconds to come up at first, then after closing it it took about 3 seconds to come up on subsequent cold starts.
    2.  File - Save As - PSD an 80 megapixel 16 bits/channel image took 2 seconds.  File was 468 MB on disk.  Timing was the same in both 32 and 64 bit Photoshop.
    3.  Painting interactivity with various brushes was good up to the larger sizes, where it started to get laggy:
    Photoshop CS5 32 bit:
    3a-d: Brush strokes are perfectly Interactive at 100px through 400px with any speed strokes.
    3e: Started to notice a slight delay at 600px. Stroke across entire image follows the cursor cleanly, but a small fraction of a second later.
    3f. Delay noticeably longer at 1000px, probably 1/3 to 1/2 second. Quick curvy strokes result in loss of some of the positions the mouse traversed, the resultant stroke becoming straight between points.  Still quite usable for painting if the mouse is moved a little bit more slowly.
    3g. At 2500px the brush paints in noticeable jumps, a small fraction of a second apart. Somewhat usable but the mouse would have to be moved extremely slowly.  Practically unusable for painting.
    Photoshop CS5 64 bit (slightly poorer performance than in 32 bit Photoshop, perhaps because of OpenGL setting difference):
    3a-c: Brush strokes perfectly Interactive at 100px through 300px.
    3d: Started to notice a slight delay noticed at 400px. Stroke on screen follows the cursor cleanly, but a small fraction of a second later.
    3e. Delay noticeably longer at 600px, probably 1/3 to 1/2 second. Quick curvy strokes lose some of the positions the mouse traversed, becoming vectored.  Possibly usable for painting but only if the mouse is moved very slowly.
    3f. A quick stroke across the image at 1000px size results in it taking 1 second or more to catch up.  Probably unusable for any kind of painting.
    3g. At 2500px the brush paints in noticeable jumps, about 1/4 second apart. Possibly usable for spot retouching but the mouse would have to be just single-clicked.  Completely unusable for painting.
    4.  Lens Blur, with More Accurate setting and 20 px Radius, took the following times to fill the preview display of the filter, and (per Task Manager) appeared to be using only one core:
    32 Bit Photoshop:  2 minutes 5 seconds (125 seconds).
    64 Bit Photoshop:  1 minute 20 seconds (80 seconds).
    5.  Filter - Sharpen - Unsharp Mask, with 250% Amount and 250.0 px Radius took the following times to complete after pressing OK:
    32 Bit Photoshop: 9 seconds.
    64 Bit Photoshop:  12 seconds.
    6.  Opening raw images took the following times:
    32 Bit Photoshop: Canon 7D Image: 3.8 seconds  ;  Nikon D7000 Image: 1.4 seconds
    64 Bit Photoshop: Canon 7D Image: 2.5 seconds  ;  Nikon D7000 Image: 1.5 seconds
    Looking forward to seeing your results.
    -Noel

  • Initial Load Performance Decrease

    Hi colleagues,
    We noticed a huge decrease initial load performance after installing an
    application in the PDA.
    Our first test we downloaded one data object with nearly 6.6Mb that
    corresponds to 30.000 registries with eight fields each. Initial Load
    to PDA took only 2 minutes.
    We performed a second test with same PDA after a reinstallation and
    new device ID. The difference here is that we installed an MI
    application related to same data object. Same amount of data was sent
    to the PDA. It took 3 hours to download it.
    In third test we change the application in order not to have the
    related data object assigned to it. In this case, download took 2
    minutes again.
    In other words, if we have an application with the data object
    assigned, it results in a huge decrease in initial load.
    In both cases we use direct connection to our LAN.
    Here goes our PDA specs:
    - Windows Mobile 6 Classic
    - Processor: Marvell PXA310 de 624MHz
    - 64MB RAM, 256MB flash ROM (190MB available to user)
    Any similar experiences?
    Thanks.
    Edited by: Renato Petrulis on Jun 1, 2010 4:15 PM

    I am confused on downloading a data object with no application.
    I thought you can only download data if it is associated to a Mobile Component, I guess you just assign the DMSCV manually?
    In any case, I have only experienced scenario two when we were downloading application with mobile component with no packaging of messages.  we had maybe a few thousand records to download and process and it would take an hour or more.
    When we enabled packaging, it would take 15-30 minutes.
    Then I went to Create Setup Package because it was just simpler to install the application and data together with no corruption or failure of DMSCV not going operational and not sending data etc... plus it was a faster download using either FTP or ActiveSync to transfer the install files.

  • USB device can perform faster

    Hi: I'm new to this site so I pray that someone can help out. I own a Sony PCG-61611L or a VPCCE25FX, he proble I'm having is every now ant then I get a message "USB port can perform faster if connected to a USB 2.0 device, I have checked all mu USB ports and they all work, I also noticed an issue with my Ethernet Controller, not sure if the ethernet controller and the USB ports are connected? I deleted the ethernet controler from the device manager and restarted my laptop, the ethernet controller was reinstalled but it still had the same issues. as I stated I don't understand computers and I don't know if the USB port issues and the Ethernet Controller are related, all I know is both are giving me error messages, sony does not show software downloads for my system, at least I can't find driver for either issue, I have searched the internet for soultions without success, any help will be greatly appreciated. mama4252

     
    Hi mama4252, 
    I am sorry to hear your issue. By the way, I think the correct model name is VPCEE25FX, not VPCCE25FX correct? When was the first time you encounter this issue? Is there any USB devices connected to the laptop? What is the Operating System of the laptop? For the mean time, kindly follow the troubleshooting steps here: 
    Power cycle - remove the battery and all peripherals -> press and hold the power button for 5 seconds
    Reset BIOS 
    Install or update these drivers: Sony® Notebook Utilities, Sony® Firmware Extension Parser Device Driver, Sony® Shared Library
    If the issue persists while a USB device in plugged in, check the specs of the USB device. It should match the spec of the port, which is USB 2.0. If the device is just 1.0, then there nothing wrong the the port. 
    You may also reinstall the wireless LAN (Marvell® Atheros® AR9285 Wireless Network Adapter Driver). 
    Hope these help. 
    Best regards,
    Vincent 
    If my post answers your question, please mark it as "Accept as Solution"
     

  • Poor performance ssd 7,1

    Hi my name is Raul and i own a mid 2010 macbbok pro 7,1 core 2 duo 2.4ghz 4 gb ram ddr3, i bought an ssd for my laptop knowing that is not going to use the sata3 because this model is only sata2 capable but the you check in system information and says that:
    Velocidad de enlace:          3 gigabits
    Velocidad de enlace negociada:          1,5 gigabits
    There is any possibility to use the sata2 speed in this laptop, because the ssd is going faster than the traditional hdd 5400rpm but not as fast as other ssd in sata2.
    with TRIM active the maximum performance is 130 read and 90 write while with the hdd was 70 read and 70 write.
    Versión de la ROM de arranque:          MBP71.0039.B0E
    Versión SMC (sistema):          1.62f6
    Tried with a bootcamp and windows 7 64 bit and the same performance...
    Thanks for your replys.

    Very interesting
    But why i see the last line says you have SDD SATA3 240 GB sandforce ? If you have SATA 3 SDD then i have only qouestion why ? because you mac don't support it  
    PS! I have same model macbook pro 7,1 etc. Using SATA2 (ocz octane s2) Link speed: 3 Gigabit . Negotiate Link Speed : 3 Gigabit . Everything is super fast etc.

  • New Marvell (beta) Controller Driver is Released - but not for MSI?

    I've been following the Marvell controller situation pretty closely the past week or so because of the BSOD it's been causing on my board.
    ASUS has just posted a new Marvell driver for the 91XX, which is on the XPower (88SE9128) and I assume many other X-58 boards.
    My question is, does Marvell release one driver that's compatible with all the X-58 boards? Or do they make one for each manufacturer?
    I'm very anxious to try it, see if it helps with the BSOD. Should I wait until MSI posts it on their download page, or am I waiting in vain because maybe they never post Beta releases?
    Thank you guys!

    Thanks Clay - I never did install the MSU software. I was using the most current driver on MSI's site - the 1.0.0.1047 WHQL.
    I've asked around about station-drivers and some say they're fine, others say basically what you did, "be careful."
    They've had the 1.2.00.1002 on their site for awhile, and now I see ASUS has it on their site for their X-58 boards. It's listed as a "Beta."
    Not sure if I'll even bother with it. I rolled back to the msahci and I'm getting the performance I was was getting originally. I think it was only the last official driver - the 1047 - that caused all (or most) of the problems for me.

  • Seeking a solution to optimize my network performance

    Hi, I'm looking for a solution using ipfw/socat or any other combination of firewall/socket redirection to allow certain applications to access servers without Nagle's Algorithm (or net.inet.tcp.delayed_ack=0 set for just those ports) getting in the way of performance.
    The problem I'm facing is with bad TCP ACK times artificially increasing the latency between the destination servers and my terminal. Pinging the server yields 180ms, while the application measures latency to be at 300ms and above.
    I've found solutions using iptables and socat to attain the same kind of results creating a loopback with iptables and then using socat to forward those packets with "nodelay" to the destination server.
    I am using an Alu Imac 24" with Leopard 10.5.1 installed.
    Some other information:
    x11/x11 SDK installed
    Xcode installed
    Macports installed
    socat 1.4.2 installed
    Any help is appreciated and thank you for your time.

    Are the disks connected like this:
    Intel SATA 6G port 1 Gray -                 240GB SSD for OS & Adobe
    Intel SATA 3G port 3/4 Blue -               6tb RAID 0 (2x3tb 7200rpm) for footage
    Marvell SATA 6G port E1 Navy Blue - 256GB SSD Exports drive
    Intel SATA 6G port 2 Gray -                128GB SSD Cache/Media Cache/Previews
    Have you followed the suggestions on Tweakers Page - Tuning Guide

  • Yosemite slowing down macbook air performance

    Ever since upgrading to yosemite, my 2011 macbook air 11' has been very noticeably sluggish compared to how it was with mavericks. At first i thought it might be from some conflicts from the previous OS, so I did a completely fresh install with yosemite, but it's still dragging and sluggish, especially with any kind of graphics intensive process. I know the air isn't supposed to be a marvel at graphics performance, but I never had these performance issues with mavericks.
    Is yosemite just too resource heavy for my macbook air? I wonder if I'd just be better off going back to mavericks. However, if there's some kind of settings I need to adjust, I'd be happy to experiment. I've already tried the 'reduce transparency' trick, but it didn't do much (not that I noticed anyways).

    Gatekeeper is described here: OS X: About Gatekeeper  - Apple Support. It is only one defense to protect you from inadvertently installing malware, and an effective defense does not rely upon only one method.
    ... I can use software that isn't officially "identified" by apple, even though it is trusted.
    Apple's philosophy is such that a Mac user with Admin privileges always has control over what he or she installs. As I wrote Gatekeeper will serve to protect you against inadvertently installing malware, including the adware that is affecting your Mac. Adware does not get installed on its own - it requires your explicit permission, which you provided by supplying your Admin name and password. When that dialog appears, it should be expected, not a surprise, and its implications should be clearly understood. By providing your credentials OS X concludes you know what you're doing and the reason you're doing it. Determining the "trusted" aspect of software thereby falls to you.
    In your case, by choosing the "anywhere" option you effectively circumvented this basic OS X security feature.
    The problem with adware is that it relies upon deception to convince you that it's legitimate software offered for some beneficial purpose, when in fact all it will do is interfere with your normal activity and possibly crash your Mac.
    Is there anything I can do to possibly identify which apps may be slowing my system down?
    Yes, although you installed quite a number of them. For troubleshooting, read below the line that follows the end of this post.
    An EtreCheck report generated on a Mac as it ships from Apple will show no entries under Kernel Extensions, Launch Agents, User Launch Agents, Safari Extensions, 3rd Party Preference Panes, etc. Everything that appears under those headings is there because you installed them. As I wrote it's a user's responsibility to understand the specific benefits they are intended to convey, the effects they will have, and the means of uninstalling them should they result in unacceptable performance - which was your original complaint.
    It's also possible that the slowdowns are not caused by software, but given the extent to which your system has been modified, hardware failure is less likely than incompatible or poorly implemented software.
    ... anything that isn't officially "identified" by apple is adware?
    Although OS X incorporates specific prohibitions against installing common malware, they can hardly attempt to classify specific user-installed modifications as adware. The only certain way to do that would be to prevent user-installed system modifications altogether, in the same manner as they do with iOS (iPads and iPhones).
    Adware's appearance changes approximately every day. Their pathetic developers are desperate to change its appearance in an effort to continue their deceptive tactics, and a simple change of a file name precludes a reliable automated means of intercepting it. That's the reason it's incumbent upon Mac users to educate themselves about its appearance so that they are not so easily gulled into installing some junk. Gatekeeper merely helps you understand that's what you'd be doing.
    Back up your Mac if  you have not already done so. To learn how to to that read Mac Basics: Time Machine backs up your Mac - Apple Support.
    If your Mac is momentarily unresponsive, consider the following.
    Launch the Console app - it is in your Utilities folder. You can find it by selecting Utilities from the Finder's Go menu.
    If the log list column on the left is not already displayed, show the log list by selecting Show Log List from Console's View menu. Select Show Toolbar if it is not already shown.
    Locate system.log in the list and select it. Many date and time-stamped entries will appear, hundreds of them, and you must find the entries relevant to your Mac's problem.
    To do that click the Clear Display button in the Toolbar. All previously displayed log entries will be disappear.
    Next: Perform whatever actions cause the Mac to exhibit the slow behavior. If the problem is caused by errors logged by the system, the Console window will show them being recorded in system.log.
    One or more of them, along with their time stamps, may reveal the reason for the problem you describe.
    Copy and paste those log entries in a reply. If hundreds of the same repetitive messages appear, please edit them before posting. There should be no need for more than a few log entries.
    Most of the entries will be cryptic but will contain information you might consider personal such as your Mac's name. If you do not want that information to appear, delete or obscure it when posting your reply. Leave enough information so that the entries can be deciphered.

  • D20 using DVD on Marvell SAS controler

    I was wondering if I can use a DVD drive on the Marvell SAS ports because I would like to use all the available SATA ports on the motherboard.  The reason for this is that I was told that I would get better performance and also trim support if I use the ICH10 ports for my bood drive that is an SSD so now I can not use the one of the 3 ports for my optical drives.  Is what I am doing ok or is it better to use the SAS controller for my SSD
    Thanks for your help in advance.
    Miike
    Solved!
    Go to Solution.

    using the marvell controller for optical is fine.   if you need TRIM support then ICH10 is your only choice.

Maybe you are looking for