* acpi_idle: Very idle Core i7 machine never enters C3
@ 2010-01-26 8:47 Jeff Garrett
2010-01-26 12:41 ` peng huang
` (2 more replies)
0 siblings, 3 replies; 54+ messages in thread
From: Jeff Garrett @ 2010-01-26 8:47 UTC (permalink / raw)
To: linux-kernel, Len Brown, linux-acpi
[-- Attachment #1: Type: text/plain, Size: 2331 bytes --]
Hi,
I was trying to chase down a theory that my desktop machine (a core i7)
is running warm (the fan sounds like it's at full speed all the time,
and I think it's not always acted this way -- hence the theory).
powertop is never showing it spending any time in C3...
I compiled a kernel without USB/sound/radeon, and ran without X. I was
able to get the wakeups/sec down below 20, but no time is spent in C3.
sysfs looks to agree with powertop here (time = 0 on C3):
/sys/devices/system/cpu/cpu0/cpuidle/state0/desc: CPUIDLE CORE POLL IDLE
/sys/devices/system/cpu/cpu0/cpuidle/state0/latency: 0
/sys/devices/system/cpu/cpu0/cpuidle/state0/name: C0
/sys/devices/system/cpu/cpu0/cpuidle/state0/power: 4294967295
/sys/devices/system/cpu/cpu0/cpuidle/state0/time: 457
/sys/devices/system/cpu/cpu0/cpuidle/state0/usage: 59
/sys/devices/system/cpu/cpu0/cpuidle/state1/desc: ACPI FFH INTEL MWAIT 0x0
/sys/devices/system/cpu/cpu0/cpuidle/state1/latency: 1
/sys/devices/system/cpu/cpu0/cpuidle/state1/name: C1
/sys/devices/system/cpu/cpu0/cpuidle/state1/power: 1000
/sys/devices/system/cpu/cpu0/cpuidle/state1/time: 308177
/sys/devices/system/cpu/cpu0/cpuidle/state1/usage: 3975
/sys/devices/system/cpu/cpu0/cpuidle/state2/desc: ACPI FFH INTEL MWAIT 0x10
/sys/devices/system/cpu/cpu0/cpuidle/state2/latency: 17
/sys/devices/system/cpu/cpu0/cpuidle/state2/name: C2
/sys/devices/system/cpu/cpu0/cpuidle/state2/power: 500
/sys/devices/system/cpu/cpu0/cpuidle/state2/time: 873440787
/sys/devices/system/cpu/cpu0/cpuidle/state2/usage: 239038
/sys/devices/system/cpu/cpu0/cpuidle/state3/desc: ACPI FFH INTEL MWAIT 0x20
/sys/devices/system/cpu/cpu0/cpuidle/state3/latency: 17
/sys/devices/system/cpu/cpu0/cpuidle/state3/name: C3
/sys/devices/system/cpu/cpu0/cpuidle/state3/power: 350
/sys/devices/system/cpu/cpu0/cpuidle/state3/time: 0
/sys/devices/system/cpu/cpu0/cpuidle/state3/usage: 0
This may be a complete red herring, but I added some printk logic to
acpi_idle_bm_check(), and it is getting called often, but bm_status is
always 1. [I infer from this that the idle logic is trying to go into
C3, but this check is stopping it... Unless I misread something.]
Is this expected behavior or is this a legitimate problem?
How might I investigate this further?
Attaching dmesg, /proc/cpuinfo, powertop -d output.
Thanks,
Jeff Garrett
[-- Attachment #2: dmesg --]
[-- Type: text/plain, Size: 40068 bytes --]
[ 0.000000] Linux version 2.6.33-rc5 (root@korrek) (gcc version 4.4.3 (Ubuntu 4.4.3-1ubuntu1) ) #14 SMP Mon Jan 25 22:25:02 CST 2010
[ 0.000000] Command line: root=UUID=0671ec67-a417-4716-b4c8-90ef225e524d ro quiet splash usbcore.autosuspend=1 pci=use_crs
[ 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 - 00000000bf790000 (usable)
[ 0.000000] BIOS-e820: 00000000bf790000 - 00000000bf79e000 (ACPI data)
[ 0.000000] BIOS-e820: 00000000bf79e000 - 00000000bf7d0000 (ACPI NVS)
[ 0.000000] BIOS-e820: 00000000bf7d0000 - 00000000bf7e0000 (reserved)
[ 0.000000] BIOS-e820: 00000000bf7ec000 - 00000000c0000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
[ 0.000000] BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
[ 0.000000] BIOS-e820: 0000000100000000 - 0000000340000000 (usable)
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] DMI present.
[ 0.000000] No AGP bridge found
[ 0.000000] last_pfn = 0x340000 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-DFFFF uncachable
[ 0.000000] E0000-E3FFF write-protect
[ 0.000000] E4000-E7FFF write-through
[ 0.000000] E8000-EBFFF write-protect
[ 0.000000] EC000-EFFFF write-through
[ 0.000000] F0000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 000000000 mask E00000000 write-back
[ 0.000000] 1 base 200000000 mask F00000000 write-back
[ 0.000000] 2 base 300000000 mask FC0000000 write-back
[ 0.000000] 3 base 0C0000000 mask FC0000000 uncachable
[ 0.000000] 4 base 0BF800000 mask FFF800000 uncachable
[ 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] e820 update range: 00000000bf800000 - 0000000100000000 (usable) ==> (reserved)
[ 0.000000] last_pfn = 0xbf790 max_arch_pfn = 0x400000000
[ 0.000000] e820 update range: 0000000000001000 - 0000000000010000 (usable) ==> (reserved)
[ 0.000000] Scanning 1 areas for low memory corruption
[ 0.000000] modified physical RAM map:
[ 0.000000] modified: 0000000000000000 - 0000000000001000 (usable)
[ 0.000000] modified: 0000000000001000 - 0000000000010000 (reserved)
[ 0.000000] modified: 0000000000010000 - 000000000009fc00 (usable)
[ 0.000000] modified: 000000000009fc00 - 00000000000a0000 (reserved)
[ 0.000000] modified: 00000000000e0000 - 0000000000100000 (reserved)
[ 0.000000] modified: 0000000000100000 - 00000000bf790000 (usable)
[ 0.000000] modified: 00000000bf790000 - 00000000bf79e000 (ACPI data)
[ 0.000000] modified: 00000000bf79e000 - 00000000bf7d0000 (ACPI NVS)
[ 0.000000] modified: 00000000bf7d0000 - 00000000bf7e0000 (reserved)
[ 0.000000] modified: 00000000bf7ec000 - 00000000c0000000 (reserved)
[ 0.000000] modified: 00000000fee00000 - 00000000fee01000 (reserved)
[ 0.000000] modified: 00000000ffb00000 - 0000000100000000 (reserved)
[ 0.000000] modified: 0000000100000000 - 0000000340000000 (usable)
[ 0.000000] initial memory mapped : 0 - 20000000
[ 0.000000] found SMP MP-table at [ffff8800000ff780] ff780
[ 0.000000] init_memory_mapping: 0000000000000000-00000000bf790000
[ 0.000000] 0000000000 - 00bf600000 page 2M
[ 0.000000] 00bf600000 - 00bf790000 page 4k
[ 0.000000] kernel direct mapping tables up to bf790000 @ 16000-1b000
[ 0.000000] init_memory_mapping: 0000000100000000-0000000340000000
[ 0.000000] 0100000000 - 0340000000 page 2M
[ 0.000000] kernel direct mapping tables up to 340000000 @ 19000-27000
[ 0.000000] RAMDISK: 34b37000 - 37fefc3d
[ 0.000000] ACPI: RSDP 00000000000f9ce0 00014 (v00 ACPIAM)
[ 0.000000] ACPI: RSDT 00000000bf790000 00044 (v01 DELL FX09 20090415 MSFT 00000097)
[ 0.000000] ACPI: FACP 00000000bf790200 00084 (v01 DELL FX09 20090415 MSFT 00000097)
[ 0.000000] ACPI: DSDT 00000000bf790660 056A7 (v01 1AAAA 1AAAA000 00000000 INTL 20051117)
[ 0.000000] ACPI: FACS 00000000bf79e000 00040
[ 0.000000] ACPI: APIC 00000000bf790390 0008C (v01 DELL FX09 20090415 MSFT 00000097)
[ 0.000000] ACPI: MCFG 00000000bf790420 0003C (v01 DELL OEMMCFG 20090415 MSFT 00000097)
[ 0.000000] ACPI: SLIC 00000000bf790460 00176 (v01 DELL FX09 20090415 MSFT 00000097)
[ 0.000000] ACPI: OSFR 00000000bf7905e0 00080 (v01 DELL FX09 20090415 MSFT 00000097)
[ 0.000000] ACPI: OEMB 00000000bf79e040 00072 (v01 DELL FX09 20090415 MSFT 00000097)
[ 0.000000] ACPI: HPET 00000000bf798660 00038 (v01 DELL OEMHPET 20090415 MSFT 00000097)
[ 0.000000] ACPI: SSDT 00000000bf79f670 01298 (v01 DpgPmm CpuPm 00000012 INTL 20051117)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] No NUMA configuration found
[ 0.000000] Faking a node at 0000000000000000-0000000340000000
[ 0.000000] Bootmem setup node 0 0000000000000000-0000000340000000
[ 0.000000] NODE_DATA [0000000000022000 - 0000000000026fff]
[ 0.000000] bootmap [0000000000027000 - 000000000008efff] pages 68
[ 0.000000] (13 early reservations) ==> bootmem [0000000000 - 0340000000]
[ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
[ 0.000000] #1 [0001000000 - 00019eba18] TEXT DATA BSS ==> [0001000000 - 00019eba18]
[ 0.000000] #2 [0034b37000 - 0037fefc3d] RAMDISK ==> [0034b37000 - 0037fefc3d]
[ 0.000000] #3 [00019ec000 - 00019ec0fc] BRK ==> [00019ec000 - 00019ec0fc]
[ 0.000000] #4 [00000ff790 - 0000100000] BIOS reserved ==> [00000ff790 - 0000100000]
[ 0.000000] #5 [00000ff780 - 00000ff790] MP-table mpf ==> [00000ff780 - 00000ff790]
[ 0.000000] #6 [000009fc00 - 00000fcee0] BIOS reserved ==> [000009fc00 - 00000fcee0]
[ 0.000000] #7 [00000fd074 - 00000ff780] BIOS reserved ==> [00000fd074 - 00000ff780]
[ 0.000000] #8 [00000fcee0 - 00000fd074] MP-table mpc ==> [00000fcee0 - 00000fd074]
[ 0.000000] #9 [0000010000 - 0000012000] TRAMPOLINE ==> [0000010000 - 0000012000]
[ 0.000000] #10 [0000012000 - 0000016000] ACPI WAKEUP ==> [0000012000 - 0000016000]
[ 0.000000] #11 [0000016000 - 0000019000] PGTABLE ==> [0000016000 - 0000019000]
[ 0.000000] #12 [0000019000 - 0000022000] PGTABLE ==> [0000019000 - 0000022000]
[ 0.000000] [ffffea0000000000-ffffea000b5fffff] PMD -> [ffff880028600000-ffff880032dfffff] on node 0
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0x00000000 -> 0x00001000
[ 0.000000] DMA32 0x00001000 -> 0x00100000
[ 0.000000] Normal 0x00100000 -> 0x00340000
[ 0.000000] Movable zone start PFN for each node
[ 0.000000] early_node_map[4] active PFN ranges
[ 0.000000] 0: 0x00000000 -> 0x00000001
[ 0.000000] 0: 0x00000010 -> 0x0000009f
[ 0.000000] 0: 0x00000100 -> 0x000bf790
[ 0.000000] 0: 0x00100000 -> 0x00340000
[ 0.000000] On node 0 totalpages: 3143456
[ 0.000000] DMA zone: 56 pages used for memmap
[ 0.000000] DMA zone: 114 pages reserved
[ 0.000000] DMA zone: 3814 pages, LIFO batch:0
[ 0.000000] DMA32 zone: 14280 pages used for memmap
[ 0.000000] DMA32 zone: 765896 pages, LIFO batch:31
[ 0.000000] Normal zone: 32256 pages used for memmap
[ 0.000000] Normal zone: 2327040 pages, LIFO batch:31
[ 0.000000] ACPI: PM-Timer IO Port: 0x808
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x84] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x85] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x86] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x87] disabled)
[ 0.000000] ACPI: IOAPIC (id[0x07] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 7, 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: 0xffffffff base: 0xfed00000
[ 0.000000] SMP: Allowing 8 CPUs, 4 hotplug CPUs
[ 0.000000] nr_irqs_gsi: 24
[ 0.000000] PM: Registered nosave memory: 0000000000001000 - 0000000000010000
[ 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] PM: Registered nosave memory: 00000000bf790000 - 00000000bf79e000
[ 0.000000] PM: Registered nosave memory: 00000000bf79e000 - 00000000bf7d0000
[ 0.000000] PM: Registered nosave memory: 00000000bf7d0000 - 00000000bf7e0000
[ 0.000000] PM: Registered nosave memory: 00000000bf7e0000 - 00000000bf7ec000
[ 0.000000] PM: Registered nosave memory: 00000000bf7ec000 - 00000000c0000000
[ 0.000000] PM: Registered nosave memory: 00000000c0000000 - 00000000fee00000
[ 0.000000] PM: Registered nosave memory: 00000000fee00000 - 00000000fee01000
[ 0.000000] PM: Registered nosave memory: 00000000fee01000 - 00000000ffb00000
[ 0.000000] PM: Registered nosave memory: 00000000ffb00000 - 0000000100000000
[ 0.000000] Allocating PCI resources starting at c0000000 (gap: c0000000:3ee00000)
[ 0.000000] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:8 nr_node_ids:1
[ 0.000000] PERCPU: Embedded 28 pages/cpu @ffff880028200000 s83608 r8192 d22888 u262144
[ 0.000000] pcpu-alloc: s83608 r8192 d22888 u262144 alloc=1*2097152
[ 0.000000] pcpu-alloc: [0] 0 1 2 3 4 5 6 7
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 3096750
[ 0.000000] Policy zone: Normal
[ 0.000000] Kernel command line: root=UUID=0671ec67-a417-4716-b4c8-90ef225e524d ro quiet splash usbcore.autosuspend=1 pci=use_crs
[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.000000] Checking aperture...
[ 0.000000] No AGP bridge found
[ 0.000000] Memory: 12270428k/13631488k available (3924k kernel code, 1057664k absent, 303396k reserved, 4815k data, 564k init)
[ 0.000000] SLUB: Genslabs=14, HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] NR_IRQS:4352 nr_irqs:472
[ 0.000000] Console: colour VGA+ 80x25
[ 0.000000] console [tty0] enabled
[ 0.000000] hpet clockevent registered
[ 0.000000] Fast TSC calibration using PIT
[ 0.010000] Detected 2660.467 MHz processor.
[ 0.000003] Calibrating delay loop (skipped), value calculated using timer frequency.. 5320.93 BogoMIPS (lpj=26604670)
[ 0.000019] Security Framework initialized
[ 0.000022] Smack: Initializing.
[ 0.000877] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes)
[ 0.003760] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes)
[ 0.004996] Mount-cache hash table entries: 256
[ 0.005097] CPU: Physical Processor ID: 0
[ 0.005098] CPU: Processor Core ID: 0
[ 0.005103] mce: CPU supports 9 MCE banks
[ 0.005112] CPU0: Thermal monitoring enabled (TM1)
[ 0.005115] CPU 0 MCA banks CMCI:2 CMCI:3 CMCI:5 CMCI:6 SHD:8
[ 0.005121] using mwait in idle threads.
[ 0.005122] Performance Events: Nehalem/Corei7 events, Intel PMU driver.
[ 0.005126] ... version: 3
[ 0.005127] ... bit width: 48
[ 0.005128] ... generic registers: 4
[ 0.005129] ... value mask: 0000ffffffffffff
[ 0.005130] ... max period: 000000007fffffff
[ 0.005131] ... fixed-purpose events: 3
[ 0.005132] ... event mask: 000000070000000f
[ 0.005146] ACPI: Core revision 20091214
[ 0.035121] Setting APIC routing to flat
[ 0.035439] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.173879] CPU0: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 04
[ 0.288392] Booting Node 0, Processors #1
[ 0.447920] CPU 1 MCA banks CMCI:2 CMCI:3 CMCI:5 SHD:6 SHD:8
[ 0.467991] #2
[ 0.627465] CPU 2 MCA banks CMCI:2 CMCI:3 CMCI:5 SHD:6 SHD:8
[ 0.647507] #3
[ 0.807011] CPU 3 MCA banks CMCI:2 CMCI:3 CMCI:5 SHD:6 SHD:8
[ 0.827079] Brought up 4 CPUs
[ 0.827081] Total of 4 processors activated (21280.65 BogoMIPS).
[ 0.828400] regulator: core version 0.5
[ 0.828423] Time: 4:28:29 Date: 01/26/10
[ 0.828451] NET: Registered protocol family 16
[ 0.828530] ACPI: bus type pci registered
[ 0.828582] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
[ 0.828584] PCI: not using MMCONFIG
[ 0.828585] PCI: Using configuration type 1 for base access
[ 0.829154] bio: create slab <bio-0> at 0
[ 0.830321] ACPI: EC: Look up EC in DSDT
[ 0.832803] ACPI: Executed 1 blocks of module-level executable AML code
[ 0.840148] ACPI: Interpreter enabled
[ 0.840151] ACPI: (supports S0 S3 S4 S5)
[ 0.840168] ACPI: Using IOAPIC for interrupt routing
[ 0.840214] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
[ 0.842058] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in ACPI motherboard resources
[ 0.855463] ACPI: No dock devices found.
[ 0.855610] ACPI: PCI Root Bridge [PCI0] (0000:00)
[ 0.855895] pci_root PNP0A08:00: host bridge window [io 0x0000-0x0cf7]
[ 0.855898] pci_root PNP0A08:00: host bridge window [io 0x0d00-0xffff]
[ 0.855899] pci_root PNP0A08:00: host bridge window [mem 0x000a0000-0x000bffff]
[ 0.855901] pci_root PNP0A08:00: host bridge window [mem 0x000d0000-0x000dffff]
[ 0.855903] pci_root PNP0A08:00: host bridge window [mem 0xc0000000-0xdfffffff]
[ 0.855905] pci_root PNP0A08:00: host bridge window [mem 0xf0000000-0xfed8ffff]
[ 0.855954] pci 0000:00:00.0: PME# supported from D0 D3hot D3cold
[ 0.855957] pci 0000:00:00.0: PME# disabled
[ 0.856011] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
[ 0.856013] pci 0000:00:01.0: PME# disabled
[ 0.856065] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
[ 0.856068] pci 0000:00:03.0: PME# disabled
[ 0.856121] pci 0000:00:07.0: PME# supported from D0 D3hot D3cold
[ 0.856124] pci 0000:00:07.0: PME# disabled
[ 0.856225] IOH bus: [00, fb]
[ 0.856227] IOH bus: 00 index 0 io port: [0, ffff]
[ 0.856229] IOH bus: 00 index 1 mmio: [e0000000, fdffffff]
[ 0.856398] pci 0000:00:19.0: reg 10: [mem 0xfbcc0000-0xfbcdffff]
[ 0.856404] pci 0000:00:19.0: reg 14: [mem 0xfbcf4000-0xfbcf4fff]
[ 0.856409] pci 0000:00:19.0: reg 18: [io 0xa080-0xa09f]
[ 0.856443] pci 0000:00:19.0: PME# supported from D0 D3hot D3cold
[ 0.856446] pci 0000:00:19.0: PME# disabled
[ 0.856486] pci 0000:00:1a.0: reg 20: [io 0xa400-0xa41f]
[ 0.856543] pci 0000:00:1a.1: reg 20: [io 0xa480-0xa49f]
[ 0.856600] pci 0000:00:1a.2: reg 20: [io 0xa800-0xa81f]
[ 0.856657] pci 0000:00:1a.7: reg 10: [mem 0xfbcf6000-0xfbcf63ff]
[ 0.856705] pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
[ 0.856709] pci 0000:00:1a.7: PME# disabled
[ 0.856739] pci 0000:00:1b.0: reg 10: [mem 0xfbcf8000-0xfbcfbfff 64bit]
[ 0.856775] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 0.856778] pci 0000:00:1b.0: PME# disabled
[ 0.856835] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[ 0.856838] pci 0000:00:1c.0: PME# disabled
[ 0.856901] pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
[ 0.856904] pci 0000:00:1c.1: PME# disabled
[ 0.856952] pci 0000:00:1d.0: reg 20: [io 0xa880-0xa89f]
[ 0.857010] pci 0000:00:1d.1: reg 20: [io 0xac00-0xac1f]
[ 0.857068] pci 0000:00:1d.2: reg 20: [io 0xb000-0xb01f]
[ 0.857125] pci 0000:00:1d.7: reg 10: [mem 0xfbcfc000-0xfbcfc3ff]
[ 0.857174] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
[ 0.857177] pci 0000:00:1d.7: PME# disabled
[ 0.857280] pci 0000:00:1f.0: quirk: [io 0x0800-0x087f] claimed by ICH6 ACPI/GPIO/TCO
[ 0.857283] pci 0000:00:1f.0: quirk: [io 0x0500-0x053f] claimed by ICH6 GPIO
[ 0.857286] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0a00 (mask 00ff)
[ 0.857332] pci 0000:00:1f.2: reg 10: [io 0xbc00-0xbc07]
[ 0.857337] pci 0000:00:1f.2: reg 14: [io 0xb880-0xb883]
[ 0.857341] pci 0000:00:1f.2: reg 18: [io 0xb800-0xb807]
[ 0.857346] pci 0000:00:1f.2: reg 1c: [io 0xb480-0xb483]
[ 0.857351] pci 0000:00:1f.2: reg 20: [io 0xb400-0xb40f]
[ 0.857355] pci 0000:00:1f.2: reg 24: [io 0xb080-0xb08f]
[ 0.857395] pci 0000:00:1f.3: reg 10: [mem 0xfbcffc00-0xfbcffcff 64bit]
[ 0.857407] pci 0000:00:1f.3: reg 20: [io 0x0400-0x041f]
[ 0.857440] pci 0000:00:1f.5: reg 10: [io 0xcc00-0xcc07]
[ 0.857445] pci 0000:00:1f.5: reg 14: [io 0xc880-0xc883]
[ 0.857449] pci 0000:00:1f.5: reg 18: [io 0xc800-0xc807]
[ 0.857454] pci 0000:00:1f.5: reg 1c: [io 0xc480-0xc483]
[ 0.857458] pci 0000:00:1f.5: reg 20: [io 0xc400-0xc40f]
[ 0.857463] pci 0000:00:1f.5: reg 24: [io 0xc080-0xc08f]
[ 0.857509] pci 0000:00:01.0: PCI bridge to [bus 06-06]
[ 0.857534] pci 0000:00:03.0: PCI bridge to [bus 05-05]
[ 0.857561] pci 0000:04:00.0: reg 10: [mem 0xd0000000-0xdfffffff 64bit pref]
[ 0.857569] pci 0000:04:00.0: reg 18: [mem 0xfbee0000-0xfbeeffff 64bit]
[ 0.857574] pci 0000:04:00.0: reg 20: [io 0xe000-0xe0ff]
[ 0.857581] pci 0000:04:00.0: reg 30: [mem 0xfbec0000-0xfbedffff pref]
[ 0.857597] pci 0000:04:00.0: supports D1 D2
[ 0.857623] pci 0000:04:00.1: reg 10: [mem 0xfbefc000-0xfbefffff 64bit]
[ 0.857653] pci 0000:04:00.1: supports D1 D2
[ 0.857680] pci 0000:00:07.0: PCI bridge to [bus 04-04]
[ 0.857683] pci 0000:00:07.0: bridge window [io 0xe000-0xefff]
[ 0.857686] pci 0000:00:07.0: bridge window [mem 0xfbe00000-0xfbefffff]
[ 0.857690] pci 0000:00:07.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
[ 0.857723] pci 0000:00:1c.0: PCI bridge to [bus 03-03]
[ 0.857776] pci 0000:02:00.0: reg 10: [mem 0xfbdff800-0xfbdfffff 64bit]
[ 0.857785] pci 0000:02:00.0: reg 18: [io 0xd800-0xd8ff]
[ 0.857851] pci 0000:02:00.0: supports D2
[ 0.857853] pci 0000:02:00.0: PME# supported from D2 D3hot D3cold
[ 0.857858] pci 0000:02:00.0: PME# disabled
[ 0.857906] pci 0000:00:1c.1: PCI bridge to [bus 02-02]
[ 0.857910] pci 0000:00:1c.1: bridge window [io 0xd000-0xdfff]
[ 0.857913] pci 0000:00:1c.1: bridge window [mem 0xfbd00000-0xfbdfffff]
[ 0.857959] pci 0000:00:1e.0: PCI bridge to [bus 01-01] (subtractive decode)
[ 0.857988] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[ 0.858306] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P4._PRT]
[ 0.858359] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P5._PRT]
[ 0.858422] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NPE1._PRT]
[ 0.858474] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NPE3._PRT]
[ 0.858533] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NPE7._PRT]
[ 0.884188] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 6 7 *10 11 12 14 15)
[ 0.884289] ACPI: PCI Interrupt Link [LNKB] (IRQs *5)
[ 0.884386] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 6 7 10 11 12 14 *15)
[ 0.884484] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 6 7 10 *11 12 14 15)
[ 0.884583] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 *4 6 7 10 11 12 14 15)
[ 0.884681] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 6 *7 10 11 12 14 15)
[ 0.884780] ACPI: PCI Interrupt Link [LNKG] (IRQs *3 4 6 7 10 11 12 14 15)
[ 0.884878] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 6 7 10 11 12 *14 15)
[ 0.884960] vgaarb: device added: PCI:0000:04:00.0,decodes=io+mem,owns=io+mem,locks=none
[ 0.884963] vgaarb: loaded
[ 0.885031] SCSI subsystem initialized
[ 0.885082] libata version 3.00 loaded.
[ 0.885175] ACPI: WMI: Mapper loaded
[ 0.885177] PCI: Using ACPI for IRQ routing
[ 0.885178] PCI: pci_cache_line_size set to 64 bytes
[ 0.885312] Bluetooth: Core ver 2.15
[ 0.885331] NET: Registered protocol family 31
[ 0.885332] Bluetooth: HCI device and connection manager initialized
[ 0.885333] Bluetooth: HCI socket layer initialized
[ 0.885335] NetLabel: Initializing
[ 0.885336] NetLabel: domain hash size = 128
[ 0.885337] NetLabel: protocols = UNLABELED CIPSOv4
[ 0.885346] NetLabel: unlabeled traffic allowed by default
[ 0.885350] HPET: 4 timers in total, 0 timers will be used for per-cpu timer
[ 0.885354] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0
[ 0.885357] hpet0: 4 comparators, 64-bit 14.318180 MHz counter
[ 0.906879] Switching to clocksource tsc
[ 0.908147] pnp: PnP ACPI init
[ 0.908154] ACPI: bus type pnp registered
[ 0.910306] pnp: PnP ACPI: found 14 devices
[ 0.910308] ACPI: ACPI bus type pnp unregistered
[ 0.910315] system 00:01: [mem 0xfbf00000-0xfbffffff] has been reserved
[ 0.910317] system 00:01: [mem 0xfc000000-0xfcffffff] has been reserved
[ 0.910319] system 00:01: [mem 0xfd000000-0xfdffffff] has been reserved
[ 0.910321] system 00:01: [mem 0xfe000000-0xfebfffff] has been reserved
[ 0.910324] system 00:01: [mem 0xfec8a000-0xfec8afff] has been reserved
[ 0.910326] system 00:01: [mem 0xfed10000-0xfed10fff] has been reserved
[ 0.910330] system 00:06: [io 0x0a00-0x0a0f] has been reserved
[ 0.910332] system 00:06: [io 0x0a10-0x0a1f] has been reserved
[ 0.910334] system 00:06: [io 0x0a20-0x0a2f] has been reserved
[ 0.910336] system 00:06: [io 0x0a30-0x0a3f] has been reserved
[ 0.910340] system 00:07: [io 0x04d0-0x04d1] has been reserved
[ 0.910342] system 00:07: [io 0x0800-0x087f] has been reserved
[ 0.910344] system 00:07: [io 0x0500-0x057f] could not be reserved
[ 0.910346] system 00:07: [mem 0xfed1c000-0xfed1ffff] has been reserved
[ 0.910348] system 00:07: [mem 0xfed20000-0xfed3ffff] has been reserved
[ 0.910350] system 00:07: [mem 0xfed40000-0xfed8ffff] has been reserved
[ 0.910354] system 00:0a: [mem 0xffc00000-0xffefffff] has been reserved
[ 0.910358] system 00:0b: [mem 0xfec00000-0xfec00fff] could not be reserved
[ 0.910360] system 00:0b: [mem 0xfee00000-0xfee00fff] has been reserved
[ 0.910364] system 00:0c: [mem 0xe0000000-0xefffffff] has been reserved
[ 0.910367] system 00:0d: [mem 0x00000000-0x0009ffff] could not be reserved
[ 0.910369] system 00:0d: [mem 0x000c0000-0x000cffff] has been reserved
[ 0.910371] system 00:0d: [mem 0x000e0000-0x000fffff] could not be reserved
[ 0.910374] system 00:0d: [mem 0x00100000-0xbfffffff] could not be reserved
[ 0.910376] system 00:0d: [mem 0xfed90000-0xffffffff] could not be reserved
[ 0.915061] pci 0000:00:1c.0: BAR 14: assigned [mem 0xc0000000-0xc01fffff]
[ 0.915064] pci 0000:00:1c.0: BAR 15: assigned [mem 0xc0200000-0xc03fffff 64bit pref]
[ 0.915066] pci 0000:00:1c.1: BAR 15: assigned [mem 0xc0400000-0xc05fffff 64bit pref]
[ 0.915068] pci 0000:00:1c.0: BAR 13: assigned [io 0x1000-0x1fff]
[ 0.915070] pci 0000:00:01.0: PCI bridge to [bus 06-06]
[ 0.915071] pci 0000:00:01.0: bridge window [io disabled]
[ 0.915074] pci 0000:00:01.0: bridge window [mem disabled]
[ 0.915077] pci 0000:00:01.0: bridge window [mem pref disabled]
[ 0.915081] pci 0000:00:03.0: PCI bridge to [bus 05-05]
[ 0.915082] pci 0000:00:03.0: bridge window [io disabled]
[ 0.915085] pci 0000:00:03.0: bridge window [mem disabled]
[ 0.915088] pci 0000:00:03.0: bridge window [mem pref disabled]
[ 0.915092] pci 0000:00:07.0: PCI bridge to [bus 04-04]
[ 0.915095] pci 0000:00:07.0: bridge window [io 0xe000-0xefff]
[ 0.915098] pci 0000:00:07.0: bridge window [mem 0xfbe00000-0xfbefffff]
[ 0.915101] pci 0000:00:07.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
[ 0.915106] pci 0000:00:1c.0: PCI bridge to [bus 03-03]
[ 0.915108] pci 0000:00:1c.0: bridge window [io 0x1000-0x1fff]
[ 0.915112] pci 0000:00:1c.0: bridge window [mem 0xc0000000-0xc01fffff]
[ 0.915115] pci 0000:00:1c.0: bridge window [mem 0xc0200000-0xc03fffff 64bit pref]
[ 0.915120] pci 0000:00:1c.1: PCI bridge to [bus 02-02]
[ 0.915122] pci 0000:00:1c.1: bridge window [io 0xd000-0xdfff]
[ 0.915126] pci 0000:00:1c.1: bridge window [mem 0xfbd00000-0xfbdfffff]
[ 0.915129] pci 0000:00:1c.1: bridge window [mem 0xc0400000-0xc05fffff 64bit pref]
[ 0.915134] pci 0000:00:1e.0: PCI bridge to [bus 01-01]
[ 0.915135] pci 0000:00:1e.0: bridge window [io disabled]
[ 0.915139] pci 0000:00:1e.0: bridge window [mem disabled]
[ 0.915142] pci 0000:00:1e.0: bridge window [mem pref disabled]
[ 0.915152] pci 0000:00:01.0: setting latency timer to 64
[ 0.915159] pci 0000:00:03.0: setting latency timer to 64
[ 0.915165] pci 0000:00:07.0: setting latency timer to 64
[ 0.915171] pci 0000:00:1c.0: enabling device (0104 -> 0107)
[ 0.915174] alloc irq_desc for 17 on node -1
[ 0.915175] alloc kstat_irqs on node -1
[ 0.915180] pci 0000:00:1c.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 0.915183] pci 0000:00:1c.0: setting latency timer to 64
[ 0.915189] alloc irq_desc for 16 on node -1
[ 0.915190] alloc kstat_irqs on node -1
[ 0.915193] pci 0000:00:1c.1: PCI INT B -> GSI 16 (level, low) -> IRQ 16
[ 0.915196] pci 0000:00:1c.1: setting latency timer to 64
[ 0.915201] pci 0000:00:1e.0: setting latency timer to 64
[ 0.915203] pci_bus 0000:00: resource 0 [io 0x0000-0x0cf7]
[ 0.915205] pci_bus 0000:00: resource 1 [io 0x0d00-0xffff]
[ 0.915207] pci_bus 0000:00: resource 2 [mem 0x000a0000-0x000bffff]
[ 0.915208] pci_bus 0000:00: resource 3 [mem 0x000d0000-0x000dffff]
[ 0.915210] pci_bus 0000:00: resource 4 [mem 0xc0000000-0xdfffffff]
[ 0.915211] pci_bus 0000:00: resource 5 [mem 0xf0000000-0xfed8ffff]
[ 0.915213] pci_bus 0000:04: resource 0 [io 0xe000-0xefff]
[ 0.915215] pci_bus 0000:04: resource 1 [mem 0xfbe00000-0xfbefffff]
[ 0.915216] pci_bus 0000:04: resource 2 [mem 0xd0000000-0xdfffffff 64bit pref]
[ 0.915218] pci_bus 0000:03: resource 0 [io 0x1000-0x1fff]
[ 0.915220] pci_bus 0000:03: resource 1 [mem 0xc0000000-0xc01fffff]
[ 0.915222] pci_bus 0000:03: resource 2 [mem 0xc0200000-0xc03fffff 64bit pref]
[ 0.915223] pci_bus 0000:02: resource 0 [io 0xd000-0xdfff]
[ 0.915225] pci_bus 0000:02: resource 1 [mem 0xfbd00000-0xfbdfffff]
[ 0.915226] pci_bus 0000:02: resource 2 [mem 0xc0400000-0xc05fffff 64bit pref]
[ 0.915228] pci_bus 0000:01: resource 3 [io 0x0000-0x0cf7]
[ 0.915230] pci_bus 0000:01: resource 4 [io 0x0d00-0xffff]
[ 0.915231] pci_bus 0000:01: resource 5 [mem 0x000a0000-0x000bffff]
[ 0.915233] pci_bus 0000:01: resource 6 [mem 0x000d0000-0x000dffff]
[ 0.915234] pci_bus 0000:01: resource 7 [mem 0xc0000000-0xdfffffff]
[ 0.915236] pci_bus 0000:01: resource 8 [mem 0xf0000000-0xfed8ffff]
[ 0.915250] NET: Registered protocol family 2
[ 0.915506] IP route cache hash table entries: 524288 (order: 10, 4194304 bytes)
[ 0.916412] TCP established hash table entries: 524288 (order: 11, 8388608 bytes)
[ 0.917656] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
[ 0.917793] TCP: Hash tables configured (established 524288 bind 65536)
[ 0.917794] TCP reno registered
[ 0.917812] UDP hash table entries: 8192 (order: 6, 262144 bytes)
[ 0.917873] UDP-Lite hash table entries: 8192 (order: 6, 262144 bytes)
[ 0.917994] NET: Registered protocol family 1
[ 0.918151] pci 0000:04:00.0: Boot video device
[ 0.918159] PCI: CLS 64 bytes, default 64
[ 0.918194] Trying to unpack rootfs image as initramfs...
[ 1.929433] Freeing initrd memory: 53987k freed
[ 1.936850] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[ 1.936854] Placing 64MB software IO TLB between ffff880020000000 - ffff880024000000
[ 1.936856] software IO TLB at phys 0x20000000 - 0x24000000
[ 1.937101] Scanning for low memory corruption every 60 seconds
[ 1.937724] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[ 1.938693] VFS: Disk quotas dquot_6.5.2
[ 1.938725] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 1.939121] fuse init (API version 7.13)
[ 1.939178] msgmni has been set to 24071
[ 1.939333] alg: No test for stdrng (krng)
[ 1.939370] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[ 1.939372] io scheduler noop registered
[ 1.939374] io scheduler deadline registered
[ 1.939416] io scheduler cfq registered (default)
[ 1.939490] pcieport 0000:00:01.0: setting latency timer to 64
[ 1.939515] alloc irq_desc for 24 on node -1
[ 1.939516] alloc kstat_irqs on node -1
[ 1.939523] pcieport 0000:00:01.0: irq 24 for MSI/MSI-X
[ 1.939571] pcieport 0000:00:03.0: setting latency timer to 64
[ 1.939594] alloc irq_desc for 25 on node -1
[ 1.939596] alloc kstat_irqs on node -1
[ 1.939600] pcieport 0000:00:03.0: irq 25 for MSI/MSI-X
[ 1.939647] pcieport 0000:00:07.0: setting latency timer to 64
[ 1.939670] alloc irq_desc for 26 on node -1
[ 1.939672] alloc kstat_irqs on node -1
[ 1.939676] pcieport 0000:00:07.0: irq 26 for MSI/MSI-X
[ 1.939725] pcieport 0000:00:1c.0: setting latency timer to 64
[ 1.939751] alloc irq_desc for 27 on node -1
[ 1.939752] alloc kstat_irqs on node -1
[ 1.939757] pcieport 0000:00:1c.0: irq 27 for MSI/MSI-X
[ 1.939815] pcieport 0000:00:1c.1: setting latency timer to 64
[ 1.939841] alloc irq_desc for 28 on node -1
[ 1.939843] alloc kstat_irqs on node -1
[ 1.939848] pcieport 0000:00:1c.1: irq 28 for MSI/MSI-X
[ 1.939911] aer 0000:00:01.0:pcie02: AER service couldn't init device: no _OSC support
[ 1.939916] aer 0000:00:03.0:pcie02: AER service couldn't init device: no _OSC support
[ 1.939920] aer 0000:00:07.0:pcie02: AER service couldn't init device: no _OSC support
[ 1.939932] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 1.939988] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[ 1.940053] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
[ 1.940055] ACPI: Power Button [PWRB]
[ 1.940087] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
[ 1.940089] ACPI: Power Button [PWRF]
[ 1.940865] ACPI: SSDT 00000000bf79e0c0 00403 (v01 DpgPmm P001Ist 00000011 INTL 20051117)
[ 1.941358] ACPI: SSDT 00000000bf79f100 003B2 (v01 PmRef P001Cst 00003001 INTL 20051117)
[ 1.941769] Monitor-Mwait will be used to enter C-1 state
[ 1.941784] Monitor-Mwait will be used to enter C-2 state
[ 1.941796] Monitor-Mwait will be used to enter C-3 state
[ 1.942248] ACPI: SSDT 00000000bf79e4d0 00403 (v01 DpgPmm P002Ist 00000012 INTL 20051117)
[ 1.942663] ACPI: SSDT 00000000bf79f4c0 00085 (v01 PmRef P002Cst 00003000 INTL 20051117)
[ 1.943561] ACPI: SSDT 00000000bf79e8e0 00403 (v01 DpgPmm P003Ist 00000012 INTL 20051117)
[ 1.943983] ACPI: SSDT 00000000bf79f550 00085 (v01 PmRef P003Cst 00003000 INTL 20051117)
[ 1.944923] ACPI: SSDT 00000000bf79ecf0 00403 (v01 DpgPmm P004Ist 00000012 INTL 20051117)
[ 1.945348] ACPI: SSDT 00000000bf79f5e0 00085 (v01 PmRef P004Cst 00003000 INTL 20051117)
[ 1.948530] Linux agpgart interface v0.103
[ 1.948546] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 1.949391] brd: module loaded
[ 1.949700] loop: module loaded
[ 1.949746] input: Macintosh mouse button emulation as /devices/virtual/input/input2
[ 1.949818] ata_piix 0000:00:1f.2: version 2.13
[ 1.949827] alloc irq_desc for 19 on node -1
[ 1.949828] alloc kstat_irqs on node -1
[ 1.949832] ata_piix 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
[ 1.949836] ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
[ 1.949862] ata_piix 0000:00:1f.2: setting latency timer to 64
[ 1.949900] scsi0 : ata_piix
[ 1.949944] scsi1 : ata_piix
[ 1.951501] ata1: SATA max UDMA/133 cmd 0xbc00 ctl 0xb880 bmdma 0xb400 irq 19
[ 1.951506] ata2: SATA max UDMA/133 cmd 0xb800 ctl 0xb480 bmdma 0xb408 irq 19
[ 1.951521] ata_piix 0000:00:1f.5: PCI INT B -> GSI 19 (level, low) -> IRQ 19
[ 1.951524] ata_piix 0000:00:1f.5: MAP [ P0 -- P1 -- ]
[ 1.951548] ata_piix 0000:00:1f.5: setting latency timer to 64
[ 1.951570] scsi2 : ata_piix
[ 1.951603] scsi3 : ata_piix
[ 1.952780] ata3: SATA max UDMA/133 cmd 0xcc00 ctl 0xc880 bmdma 0xc400 irq 19
[ 1.952783] ata4: SATA max UDMA/133 cmd 0xc800 ctl 0xc480 bmdma 0xc408 irq 19
[ 1.953307] Fixed MDIO Bus: probed
[ 1.953330] PPP generic driver version 2.4.2
[ 1.953384] PNP: No PS/2 controller found. Probing ports directly.
[ 1.953720] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 1.953726] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 1.953763] mice: PS/2 mouse device common for all mice
[ 1.953818] rtc_cmos 00:03: RTC can wake from S4
[ 1.953837] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
[ 1.953860] rtc0: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
[ 1.953938] device-mapper: uevent: version 1.0.3
[ 1.953990] device-mapper: ioctl: 4.16.0-ioctl (2009-11-05) initialised: dm-devel@redhat.com
[ 1.954043] device-mapper: multipath: version 1.1.1 loaded
[ 1.954045] device-mapper: multipath round-robin: version 1.0.0 loaded
[ 1.954219] cpuidle: using governor ladder
[ 1.954348] cpuidle: using governor menu
[ 1.954370] oprofile: using NMI interrupt.
[ 1.954555] TCP cubic registered
[ 1.954653] NET: Registered protocol family 10
[ 1.954927] lo: Disabled Privacy Extensions
[ 1.955073] NET: Registered protocol family 17
[ 1.955083] Bluetooth: L2CAP ver 2.14
[ 1.955084] Bluetooth: L2CAP socket layer initialized
[ 1.955086] Bluetooth: SCO (Voice Link) ver 0.6
[ 1.955087] Bluetooth: SCO socket layer initialized
[ 1.955107] Bluetooth: RFCOMM TTY layer initialized
[ 1.955109] Bluetooth: RFCOMM socket layer initialized
[ 1.955110] Bluetooth: RFCOMM ver 1.11
[ 1.956577] PM: Resume from disk failed.
[ 1.956847] Magic number: 10:270:465
[ 1.956932] rtc_cmos 00:03: setting system clock to 2010-01-26 04:28:30 UTC (1264480110)
[ 1.956935] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 1.956936] EDD information not available.
[ 2.294611] ata3: SATA link down (SStatus 0 SControl 300)
[ 2.305384] ata4: SATA link down (SStatus 0 SControl 300)
[ 2.802603] ata1.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 2.802617] ata1.01: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 2.802795] ata2.00: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 2.802809] ata2.01: SATA link down (SStatus 0 SControl 300)
[ 2.802820] ata2.01: link offline, clearing class 3 to NONE
[ 2.822789] ata2.00: ATAPI: TSSTcorpDVD-ROM TS-H353B, D700, max UDMA/33
[ 2.842863] ata1.00: ATA-7: Hitachi HUA721010KLA330, GKAOA9RA, max UDMA/133
[ 2.842867] ata1.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32)
[ 2.842908] ata1.01: ATAPI: HL-DT-ST DVD+/-RW GH30N, A102, max UDMA/100
[ 2.862625] ata2.00: configured for UDMA/33
[ 2.882783] ata1.00: configured for UDMA/133
[ 2.922455] ata1.01: configured for UDMA/100
[ 2.922917] scsi 0:0:0:0: Direct-Access ATA Hitachi HUA72101 GKAO PQ: 0 ANSI: 5
[ 2.923057] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 2.923179] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[ 2.924398] scsi 0:0:1:0: CD-ROM HL-DT-ST DVD+-RW GH30N A102 PQ: 0 ANSI: 5
[ 2.924466] sd 0:0:0:0: [sda] Write Protect is off
[ 2.924469] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 2.925367] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2.928400] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
[ 2.928403] Uniform CD-ROM driver Revision: 3.20
[ 2.928451] sda:
[ 2.928491] sr 0:0:1:0: Attached scsi CD-ROM sr0
[ 2.928537] sr 0:0:1:0: Attached scsi generic sg1 type 5
[ 2.929829] scsi 1:0:0:0: CD-ROM TSSTcorp DVD-ROM TS-H353B D700 PQ: 0 ANSI: 5
[ 2.935782] sr1: scsi3-mmc drive: 4x/48x cd/rw xa/form2 cdda tray
[ 2.935871] sr 1:0:0:0: Attached scsi CD-ROM sr1
[ 2.935914] sr 1:0:0:0: Attached scsi generic sg2 type 5
[ 2.941613] sda1 sda2 < sda5 >
[ 2.961235] sd 0:0:0:0: [sda] Attached SCSI disk
[ 2.961308] Freeing unused kernel memory: 564k freed
[ 2.961406] Write protecting the kernel read-only data: 8192k
[ 2.961669] Freeing unused kernel memory: 152k freed
[ 2.961943] Freeing unused kernel memory: 2016k freed
[ 3.005798] e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2
[ 3.005800] e1000e: Copyright (c) 1999 - 2009 Intel Corporation.
[ 3.005835] alloc irq_desc for 20 on node -1
[ 3.005836] alloc kstat_irqs on node -1
[ 3.005842] e1000e 0000:00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[ 3.005849] e1000e 0000:00:19.0: setting latency timer to 64
[ 3.005917] alloc irq_desc for 29 on node -1
[ 3.005918] alloc kstat_irqs on node -1
[ 3.005925] e1000e 0000:00:19.0: irq 29 for MSI/MSI-X
[ 3.018823] ohci1394 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 3.018830] ohci1394 0000:02:00.0: setting latency timer to 64
[ 3.074194] ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[17] MMIO=[fbdff800-fbdfffff] Max Packet=[2048] IR/IT contexts=[4/8]
[ 3.533416] 0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1) 00:24:e8:08:87:ea
[ 3.533420] 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
[ 3.533441] 0000:00:19.0: eth0: MAC: 7, PHY: 8, PBA No: ffffff-0ff
[ 3.728120] kjournald starting. Commit interval 5 seconds
[ 3.728129] EXT3-fs (sda1): mounted filesystem with writeback data mode
[ 4.400386] ieee1394: Host added: ID:BUS[0-00:1023] GUID[0024e880000887ea]
[ 6.497804] Adding 36041788k swap on /dev/sda5. Priority:-1 extents:1 across:36041788k
[ 7.068086] EXT3-fs (sda1): using internal journal
[ 7.111992] udev: starting version 149
[ 8.865194] dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2)
[ 9.177999] lp: driver loaded but no devices found
[ 11.720904] mv[3135]: segfault at 7ffe93aa8dd8 ip 00007fc0c7ec2305 sp 00007ffe93aa8de0 error 6 in libattr.so.1.1.0[7fc0c7ec0000+4000]
[ 12.061347] e1000e 0000:00:19.0: irq 29 for MSI/MSI-X
[ 12.120923] e1000e 0000:00:19.0: irq 29 for MSI/MSI-X
[ 12.122729] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 15.434647] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[ 15.436410] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 22.683358] pci 0000:04:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 26.358101] eth0: no IPv6 routers present
[ 28.977712] CPUFREQ: Per core ondemand sysfs interface is deprecated - ignore_nice_load
[ 32.148921] ppdev: user-space parallel port driver
[ 534.926499] coretemp coretemp.0: Unable to access MSR 0xEE, for Tjmax, left at default
[ 534.926542] coretemp coretemp.1: Unable to access MSR 0xEE, for Tjmax, left at default
[ 534.926582] coretemp coretemp.2: Unable to access MSR 0xEE, for Tjmax, left at default
[ 534.926621] coretemp coretemp.3: Unable to access MSR 0xEE, for Tjmax, left at default
[-- Attachment #3: powertop --]
[-- Type: text/plain, Size: 1964 bytes --]
PowerTOP 1.12 (C) 2007, 2008 Intel Corporation
Collecting data for 15 seconds
Cn Avg residency
C0 (cpu running) ( 1.0%)
polling 0.0ms ( 0.0%)
C1 mwait 0.0ms ( 0.0%)
C2 mwait 63.7ms (99.0%)
C3 mwait 0.0ms ( 0.0%)
P-states (frequencies)
Turbo Mode 0.0%
2.67 Ghz 0.0%
2.54 Ghz 0.0%
2.40 Ghz 0.0%
1.60 Ghz 100.0%
Wakeups-from-idle per second : 15.5 interval: 15.0s
no ACPI power usage estimate available
Top causes for wakeups:
26.2% ( 16.6) [kernel scheduler] Load balancing tick
18.1% ( 11.5) [extra timer interrupt]
16.4% ( 10.4) [ata_piix, ata_piix] <interrupt>
15.5% ( 9.8) [Rescheduling interrupts] <kernel IPI>
7.9% ( 5.0) offlineimap
4.5% ( 2.9) [kernel core] hrtimer_start (tick_sched_timer)
3.2% ( 2.0) [kernel core] add_timer_on (clocksource_watchdog)
1.7% ( 1.1) hald-addon-stor
1.6% ( 1.0) ntpd
1.1% ( 0.7) [eth0] <interrupt>
1.1% ( 0.7) devkit-disks-da
0.8% ( 0.5) events/1
0.4% ( 0.3) [kernel core] enqueue_task_rt (sched_rt_period_timer)
0.3% ( 0.2) [kernel core] __mod_timer (dev_watchdog)
0.3% ( 0.2) rtkit-daemon
0.1% ( 0.1) events/2
0.1% ( 0.1) [kernel core] __mod_timer (tcp_delack_timer)
0.1% ( 0.1) sshd
0.1% ( 0.1) [kernel core] __mod_timer (neigh_timer_handler)
0.1% ( 0.1) ssh-agent
0.1% ( 0.1) [kernel core] __mod_timer (cfq_idle_slice_timer)
0.1% ( 0.1) mythbackend
0.1% ( 0.1) NetworkManager
0.1% ( 0.1) rsyslogd
0.1% ( 0.1) [kernel core] __mod_timer (sync_supers_timer_fn)
Suggestion: Enable the CONFIG_USB_SUSPEND kernel configuration option.
This option will automatically disable UHCI USB when not in use, and may
save approximately 1 Watt of power.
Recent USB suspend statistics
Active Device name
Recent audio activity statistics
Active Device name
Recent SATA AHCI link activity statistics
Active Partial Slumber Device name
[-- Attachment #4: cpuinfo --]
[-- Type: text/plain, Size: 3240 bytes --]
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 26
model name : Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz
stepping : 4
cpu MHz : 1600.000
cache size : 8192 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid
bogomips : 5320.93
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 26
model name : Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz
stepping : 4
cpu MHz : 1600.000
cache size : 8192 KB
physical id : 0
siblings : 4
core id : 1
cpu cores : 4
apicid : 2
initial apicid : 2
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid
bogomips : 5319.90
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 2
vendor_id : GenuineIntel
cpu family : 6
model : 26
model name : Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz
stepping : 4
cpu MHz : 1600.000
cache size : 8192 KB
physical id : 0
siblings : 4
core id : 2
cpu cores : 4
apicid : 4
initial apicid : 4
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid
bogomips : 5319.91
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 3
vendor_id : GenuineIntel
cpu family : 6
model : 26
model name : Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz
stepping : 4
cpu MHz : 1600.000
cache size : 8192 KB
physical id : 0
siblings : 4
core id : 3
cpu cores : 4
apicid : 6
initial apicid : 6
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid
bogomips : 5319.90
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: acpi_idle: Very idle Core i7 machine never enters C3
2010-01-26 8:47 acpi_idle: Very idle Core i7 machine never enters C3 Jeff Garrett
@ 2010-01-26 12:41 ` peng huang
2010-01-26 21:45 ` Andi Kleen
2010-02-01 14:10 ` Pavel Machek
2 siblings, 0 replies; 54+ messages in thread
From: peng huang @ 2010-01-26 12:41 UTC (permalink / raw)
To: Jeff Garrett; +Cc: linux-kernel, Len Brown, linux-acpi
Hi,
can you show me the file /proc/acpi/processor/CPU*/power.
and are you sure your cpu usage is 0 or nearly zero.
this is the info of my laptop(using core 2 processors):
powertop's output:
Cn Avg residency P-states (frequencies)
C0 (cpu running) (10.6%) 2.00 Ghz 1.9%
C0 0.0ms ( 0.0%) 1.67 Ghz 0.1%
C1 mwait 0.0ms ( 0.0%) 1333 Mhz 0.0%
C2 mwait 0.0ms ( 0.0%) 1000 Mhz 98.0%
C3 mwait 1.1ms (89.4%)
and power things:
huang@huang-laptop:~$ cat /proc/acpi/processor/CPU0/power
active state: C0
max_cstate: C8
maximum allowed latency: 2000000000 usec
states:
C1: type[C1] promotion[--] demotion[--]
latency[001] usage[00002364] duration[00000000000000000000]
C2: type[C2] promotion[--] demotion[--]
latency[001] usage[00070662] duration[00000000000006013816]
C3: type[C3] promotion[--] demotion[--]
latency[017] usage[04774185] duration[00000000010838418152]
you can see C3 with powertop,so i think your BIOS has enabled Deep
C-state.
-huang
2010-01-26 (火) の 02:47 -0600 に Jeff Garrett さんは書きました:
> Hi,
>
> I was trying to chase down a theory that my desktop machine (a core i7)
> is running warm (the fan sounds like it's at full speed all the time,
> and I think it's not always acted this way -- hence the theory).
>
> powertop is never showing it spending any time in C3...
>
> I compiled a kernel without USB/sound/radeon, and ran without X. I was
> able to get the wakeups/sec down below 20, but no time is spent in C3.
>
> sysfs looks to agree with powertop here (time = 0 on C3):
> /sys/devices/system/cpu/cpu0/cpuidle/state0/desc: CPUIDLE CORE POLL IDLE
> /sys/devices/system/cpu/cpu0/cpuidle/state0/latency: 0
> /sys/devices/system/cpu/cpu0/cpuidle/state0/name: C0
> /sys/devices/system/cpu/cpu0/cpuidle/state0/power: 4294967295
> /sys/devices/system/cpu/cpu0/cpuidle/state0/time: 457
> /sys/devices/system/cpu/cpu0/cpuidle/state0/usage: 59
> /sys/devices/system/cpu/cpu0/cpuidle/state1/desc: ACPI FFH INTEL MWAIT 0x0
> /sys/devices/system/cpu/cpu0/cpuidle/state1/latency: 1
> /sys/devices/system/cpu/cpu0/cpuidle/state1/name: C1
> /sys/devices/system/cpu/cpu0/cpuidle/state1/power: 1000
> /sys/devices/system/cpu/cpu0/cpuidle/state1/time: 308177
> /sys/devices/system/cpu/cpu0/cpuidle/state1/usage: 3975
> /sys/devices/system/cpu/cpu0/cpuidle/state2/desc: ACPI FFH INTEL MWAIT 0x10
> /sys/devices/system/cpu/cpu0/cpuidle/state2/latency: 17
> /sys/devices/system/cpu/cpu0/cpuidle/state2/name: C2
> /sys/devices/system/cpu/cpu0/cpuidle/state2/power: 500
> /sys/devices/system/cpu/cpu0/cpuidle/state2/time: 873440787
> /sys/devices/system/cpu/cpu0/cpuidle/state2/usage: 239038
> /sys/devices/system/cpu/cpu0/cpuidle/state3/desc: ACPI FFH INTEL MWAIT 0x20
> /sys/devices/system/cpu/cpu0/cpuidle/state3/latency: 17
> /sys/devices/system/cpu/cpu0/cpuidle/state3/name: C3
> /sys/devices/system/cpu/cpu0/cpuidle/state3/power: 350
> /sys/devices/system/cpu/cpu0/cpuidle/state3/time: 0
> /sys/devices/system/cpu/cpu0/cpuidle/state3/usage: 0
>
> This may be a complete red herring, but I added some printk logic to
> acpi_idle_bm_check(), and it is getting called often, but bm_status is
> always 1. [I infer from this that the idle logic is trying to go into
> C3, but this check is stopping it... Unless I misread something.]
>
> Is this expected behavior or is this a legitimate problem?
>
> How might I investigate this further?
>
> Attaching dmesg, /proc/cpuinfo, powertop -d output.
>
> Thanks,
> Jeff Garrett
--
peng huang <huangpeng.linux@gmail.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: acpi_idle: Very idle Core i7 machine never enters C3
@ 2010-01-26 12:41 ` peng huang
0 siblings, 0 replies; 54+ messages in thread
From: peng huang @ 2010-01-26 12:41 UTC (permalink / raw)
To: Jeff Garrett; +Cc: linux-kernel, Len Brown, linux-acpi
Hi,
can you show me the file /proc/acpi/processor/CPU*/power.
and are you sure your cpu usage is 0 or nearly zero.
this is the info of my laptop(using core 2 processors):
powertop's output:
Cn Avg residency P-states (frequencies)
C0 (cpu running) (10.6%) 2.00 Ghz 1.9%
C0 0.0ms ( 0.0%) 1.67 Ghz 0.1%
C1 mwait 0.0ms ( 0.0%) 1333 Mhz 0.0%
C2 mwait 0.0ms ( 0.0%) 1000 Mhz 98.0%
C3 mwait 1.1ms (89.4%)
and power things:
huang@huang-laptop:~$ cat /proc/acpi/processor/CPU0/power
active state: C0
max_cstate: C8
maximum allowed latency: 2000000000 usec
states:
C1: type[C1] promotion[--] demotion[--]
latency[001] usage[00002364] duration[00000000000000000000]
C2: type[C2] promotion[--] demotion[--]
latency[001] usage[00070662] duration[00000000000006013816]
C3: type[C3] promotion[--] demotion[--]
latency[017] usage[04774185] duration[00000000010838418152]
you can see C3 with powertop,so i think your BIOS has enabled Deep
C-state.
-huang
2010-01-26 (火) の 02:47 -0600 に Jeff Garrett さんは書きました:
> Hi,
>
> I was trying to chase down a theory that my desktop machine (a core i7)
> is running warm (the fan sounds like it's at full speed all the time,
> and I think it's not always acted this way -- hence the theory).
>
> powertop is never showing it spending any time in C3...
>
> I compiled a kernel without USB/sound/radeon, and ran without X. I was
> able to get the wakeups/sec down below 20, but no time is spent in C3.
>
> sysfs looks to agree with powertop here (time = 0 on C3):
> /sys/devices/system/cpu/cpu0/cpuidle/state0/desc: CPUIDLE CORE POLL IDLE
> /sys/devices/system/cpu/cpu0/cpuidle/state0/latency: 0
> /sys/devices/system/cpu/cpu0/cpuidle/state0/name: C0
> /sys/devices/system/cpu/cpu0/cpuidle/state0/power: 4294967295
> /sys/devices/system/cpu/cpu0/cpuidle/state0/time: 457
> /sys/devices/system/cpu/cpu0/cpuidle/state0/usage: 59
> /sys/devices/system/cpu/cpu0/cpuidle/state1/desc: ACPI FFH INTEL MWAIT 0x0
> /sys/devices/system/cpu/cpu0/cpuidle/state1/latency: 1
> /sys/devices/system/cpu/cpu0/cpuidle/state1/name: C1
> /sys/devices/system/cpu/cpu0/cpuidle/state1/power: 1000
> /sys/devices/system/cpu/cpu0/cpuidle/state1/time: 308177
> /sys/devices/system/cpu/cpu0/cpuidle/state1/usage: 3975
> /sys/devices/system/cpu/cpu0/cpuidle/state2/desc: ACPI FFH INTEL MWAIT 0x10
> /sys/devices/system/cpu/cpu0/cpuidle/state2/latency: 17
> /sys/devices/system/cpu/cpu0/cpuidle/state2/name: C2
> /sys/devices/system/cpu/cpu0/cpuidle/state2/power: 500
> /sys/devices/system/cpu/cpu0/cpuidle/state2/time: 873440787
> /sys/devices/system/cpu/cpu0/cpuidle/state2/usage: 239038
> /sys/devices/system/cpu/cpu0/cpuidle/state3/desc: ACPI FFH INTEL MWAIT 0x20
> /sys/devices/system/cpu/cpu0/cpuidle/state3/latency: 17
> /sys/devices/system/cpu/cpu0/cpuidle/state3/name: C3
> /sys/devices/system/cpu/cpu0/cpuidle/state3/power: 350
> /sys/devices/system/cpu/cpu0/cpuidle/state3/time: 0
> /sys/devices/system/cpu/cpu0/cpuidle/state3/usage: 0
>
> This may be a complete red herring, but I added some printk logic to
> acpi_idle_bm_check(), and it is getting called often, but bm_status is
> always 1. [I infer from this that the idle logic is trying to go into
> C3, but this check is stopping it... Unless I misread something.]
>
> Is this expected behavior or is this a legitimate problem?
>
> How might I investigate this further?
>
> Attaching dmesg, /proc/cpuinfo, powertop -d output.
>
> Thanks,
> Jeff Garrett
--
peng huang <huangpeng.linux@gmail.com>
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: acpi_idle: Very idle Core i7 machine never enters C3
2010-01-26 12:41 ` peng huang
@ 2010-01-26 14:59 ` Jeff Garrett
-1 siblings, 0 replies; 54+ messages in thread
From: Jeff Garrett @ 2010-01-26 14:59 UTC (permalink / raw)
To: peng huang; +Cc: linux-kernel, Len Brown, linux-acpi
On Tue, Jan 26, 2010 at 09:41:00PM +0900, peng huang wrote:
> Hi,
> can you show me the file /proc/acpi/processor/CPU*/power.
> and are you sure your cpu usage is 0 or nearly zero.
Yea, I'm pretty sure my cpu usage is nearly zero. powertop shows fewer
than 20 wakeups per second, shows 99% C2 residency, top shows 100% idle,
perf top shows acpi_idle_enter_simple as the most common function
(~50%). Very little is running on the box, and I've compiled out the
heavier parts of the kernel (such as USB)...
(It still has ordinary userspace running, e.g. udev & hal, and still has
sshd and network traffic, as examples.)
This is all consistent with a very idle machine, I think.
> this is the info of my laptop(using core 2 processors):
> powertop's output:
> Cn Avg residency P-states (frequencies)
> C0 (cpu running) (10.6%) 2.00 Ghz 1.9%
> C0 0.0ms ( 0.0%) 1.67 Ghz 0.1%
> C1 mwait 0.0ms ( 0.0%) 1333 Mhz 0.0%
> C2 mwait 0.0ms ( 0.0%) 1000 Mhz 98.0%
> C3 mwait 1.1ms (89.4%)
Yea, my laptop also (also core 2) has 700-1000 wakeups/sec and spends
greater than 80% of its time in C3... That's partly why I'm curious
about what my core i7 desktop is doing.
> and power things:
> huang@huang-laptop:~$ cat /proc/acpi/processor/CPU0/power
> active state: C0
> max_cstate: C8
> maximum allowed latency: 2000000000 usec
> states:
> C1: type[C1] promotion[--] demotion[--]
> latency[001] usage[00002364] duration[00000000000000000000]
> C2: type[C2] promotion[--] demotion[--]
> latency[001] usage[00070662] duration[00000000000006013816]
> C3: type[C3] promotion[--] demotion[--]
> latency[017] usage[04774185] duration[00000000010838418152]
>
> you can see C3 with powertop,so i think your BIOS has enabled Deep
> C-state.
Here's my power files...
/proc/acpi/processor/CPU0/power:
active state: C0
max_cstate: C8
maximum allowed latency: 2000000000 usec
states:
C1: type[C1] promotion[--] demotion[--] latency[001] usage[00001470] duration[00000000000000000000]
C2: type[C2] promotion[--] demotion[--] latency[017] usage[00234416] duration[00000000017165798539]
C3: type[C3] promotion[--] demotion[--] latency[017] usage[00000000] duration[00000000000000000000]
/proc/acpi/processor/CPU1/power:
active state: C0
max_cstate: C8
maximum allowed latency: 2000000000 usec
states:
C1: type[C1] promotion[--] demotion[--] latency[001] usage[00000481] duration[00000000000000000000]
C2: type[C2] promotion[--] demotion[--] latency[017] usage[00090169] duration[00000000017188463157]
C3: type[C3] promotion[--] demotion[--] latency[017] usage[00000000] duration[00000000000000000000]
/proc/acpi/processor/CPU2/power:
active state: C0
max_cstate: C8
maximum allowed latency: 2000000000 usec
states:
C1: type[C1] promotion[--] demotion[--] latency[001] usage[00000418] duration[00000000000000000000]
C2: type[C2] promotion[--] demotion[--] latency[017] usage[00068874] duration[00000000017193805291]
C3: type[C3] promotion[--] demotion[--] latency[017] usage[00000000] duration[00000000000000000000]
/proc/acpi/processor/CPU3/power:
active state: C0
max_cstate: C8
maximum allowed latency: 2000000000 usec
states:
C1: type[C1] promotion[--] demotion[--] latency[001] usage[00001356] duration[00000000000000000000]
C2: type[C2] promotion[--] demotion[--] latency[017] usage[00362752] duration[00000000017156707397]
C3: type[C3] promotion[--] demotion[--] latency[017] usage[00000000] duration[00000000000000000000]
>
> -huang
>
> 2010-01-26 (火) の 02:47 -0600 に Jeff Garrett さんは書きました:
> > Hi,
> >
> > I was trying to chase down a theory that my desktop machine (a core i7)
> > is running warm (the fan sounds like it's at full speed all the time,
> > and I think it's not always acted this way -- hence the theory).
> >
> > powertop is never showing it spending any time in C3...
> >
> > I compiled a kernel without USB/sound/radeon, and ran without X. I was
> > able to get the wakeups/sec down below 20, but no time is spent in C3.
> >
> > sysfs looks to agree with powertop here (time = 0 on C3):
> > /sys/devices/system/cpu/cpu0/cpuidle/state0/desc: CPUIDLE CORE POLL IDLE
> > /sys/devices/system/cpu/cpu0/cpuidle/state0/latency: 0
> > /sys/devices/system/cpu/cpu0/cpuidle/state0/name: C0
> > /sys/devices/system/cpu/cpu0/cpuidle/state0/power: 4294967295
> > /sys/devices/system/cpu/cpu0/cpuidle/state0/time: 457
> > /sys/devices/system/cpu/cpu0/cpuidle/state0/usage: 59
> > /sys/devices/system/cpu/cpu0/cpuidle/state1/desc: ACPI FFH INTEL MWAIT 0x0
> > /sys/devices/system/cpu/cpu0/cpuidle/state1/latency: 1
> > /sys/devices/system/cpu/cpu0/cpuidle/state1/name: C1
> > /sys/devices/system/cpu/cpu0/cpuidle/state1/power: 1000
> > /sys/devices/system/cpu/cpu0/cpuidle/state1/time: 308177
> > /sys/devices/system/cpu/cpu0/cpuidle/state1/usage: 3975
> > /sys/devices/system/cpu/cpu0/cpuidle/state2/desc: ACPI FFH INTEL MWAIT 0x10
> > /sys/devices/system/cpu/cpu0/cpuidle/state2/latency: 17
> > /sys/devices/system/cpu/cpu0/cpuidle/state2/name: C2
> > /sys/devices/system/cpu/cpu0/cpuidle/state2/power: 500
> > /sys/devices/system/cpu/cpu0/cpuidle/state2/time: 873440787
> > /sys/devices/system/cpu/cpu0/cpuidle/state2/usage: 239038
> > /sys/devices/system/cpu/cpu0/cpuidle/state3/desc: ACPI FFH INTEL MWAIT 0x20
> > /sys/devices/system/cpu/cpu0/cpuidle/state3/latency: 17
> > /sys/devices/system/cpu/cpu0/cpuidle/state3/name: C3
> > /sys/devices/system/cpu/cpu0/cpuidle/state3/power: 350
> > /sys/devices/system/cpu/cpu0/cpuidle/state3/time: 0
> > /sys/devices/system/cpu/cpu0/cpuidle/state3/usage: 0
> >
> > This may be a complete red herring, but I added some printk logic to
> > acpi_idle_bm_check(), and it is getting called often, but bm_status is
> > always 1. [I infer from this that the idle logic is trying to go into
> > C3, but this check is stopping it... Unless I misread something.]
> >
> > Is this expected behavior or is this a legitimate problem?
> >
> > How might I investigate this further?
> >
> > Attaching dmesg, /proc/cpuinfo, powertop -d output.
> >
> > Thanks,
> > Jeff Garrett
>
>
> --
> peng huang <huangpeng.linux@gmail.com>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: acpi_idle: Very idle Core i7 machine never enters C3
@ 2010-01-26 14:59 ` Jeff Garrett
0 siblings, 0 replies; 54+ messages in thread
From: Jeff Garrett @ 2010-01-26 14:59 UTC (permalink / raw)
To: peng huang; +Cc: linux-kernel, Len Brown, linux-acpi
On Tue, Jan 26, 2010 at 09:41:00PM +0900, peng huang wrote:
> Hi,
> can you show me the file /proc/acpi/processor/CPU*/power.
> and are you sure your cpu usage is 0 or nearly zero.
Yea, I'm pretty sure my cpu usage is nearly zero. powertop shows fewer
than 20 wakeups per second, shows 99% C2 residency, top shows 100% idle,
perf top shows acpi_idle_enter_simple as the most common function
(~50%). Very little is running on the box, and I've compiled out the
heavier parts of the kernel (such as USB)...
(It still has ordinary userspace running, e.g. udev & hal, and still has
sshd and network traffic, as examples.)
This is all consistent with a very idle machine, I think.
> this is the info of my laptop(using core 2 processors):
> powertop's output:
> Cn Avg residency P-states (frequencies)
> C0 (cpu running) (10.6%) 2.00 Ghz 1.9%
> C0 0.0ms ( 0.0%) 1.67 Ghz 0.1%
> C1 mwait 0.0ms ( 0.0%) 1333 Mhz 0.0%
> C2 mwait 0.0ms ( 0.0%) 1000 Mhz 98.0%
> C3 mwait 1.1ms (89.4%)
Yea, my laptop also (also core 2) has 700-1000 wakeups/sec and spends
greater than 80% of its time in C3... That's partly why I'm curious
about what my core i7 desktop is doing.
> and power things:
> huang@huang-laptop:~$ cat /proc/acpi/processor/CPU0/power
> active state: C0
> max_cstate: C8
> maximum allowed latency: 2000000000 usec
> states:
> C1: type[C1] promotion[--] demotion[--]
> latency[001] usage[00002364] duration[00000000000000000000]
> C2: type[C2] promotion[--] demotion[--]
> latency[001] usage[00070662] duration[00000000000006013816]
> C3: type[C3] promotion[--] demotion[--]
> latency[017] usage[04774185] duration[00000000010838418152]
>
> you can see C3 with powertop,so i think your BIOS has enabled Deep
> C-state.
Here's my power files...
/proc/acpi/processor/CPU0/power:
active state: C0
max_cstate: C8
maximum allowed latency: 2000000000 usec
states:
C1: type[C1] promotion[--] demotion[--] latency[001] usage[00001470] duration[00000000000000000000]
C2: type[C2] promotion[--] demotion[--] latency[017] usage[00234416] duration[00000000017165798539]
C3: type[C3] promotion[--] demotion[--] latency[017] usage[00000000] duration[00000000000000000000]
/proc/acpi/processor/CPU1/power:
active state: C0
max_cstate: C8
maximum allowed latency: 2000000000 usec
states:
C1: type[C1] promotion[--] demotion[--] latency[001] usage[00000481] duration[00000000000000000000]
C2: type[C2] promotion[--] demotion[--] latency[017] usage[00090169] duration[00000000017188463157]
C3: type[C3] promotion[--] demotion[--] latency[017] usage[00000000] duration[00000000000000000000]
/proc/acpi/processor/CPU2/power:
active state: C0
max_cstate: C8
maximum allowed latency: 2000000000 usec
states:
C1: type[C1] promotion[--] demotion[--] latency[001] usage[00000418] duration[00000000000000000000]
C2: type[C2] promotion[--] demotion[--] latency[017] usage[00068874] duration[00000000017193805291]
C3: type[C3] promotion[--] demotion[--] latency[017] usage[00000000] duration[00000000000000000000]
/proc/acpi/processor/CPU3/power:
active state: C0
max_cstate: C8
maximum allowed latency: 2000000000 usec
states:
C1: type[C1] promotion[--] demotion[--] latency[001] usage[00001356] duration[00000000000000000000]
C2: type[C2] promotion[--] demotion[--] latency[017] usage[00362752] duration[00000000017156707397]
C3: type[C3] promotion[--] demotion[--] latency[017] usage[00000000] duration[00000000000000000000]
>
> -huang
>
> 2010-01-26 (火) の 02:47 -0600 に Jeff Garrett さんは書きました:
> > Hi,
> >
> > I was trying to chase down a theory that my desktop machine (a core i7)
> > is running warm (the fan sounds like it's at full speed all the time,
> > and I think it's not always acted this way -- hence the theory).
> >
> > powertop is never showing it spending any time in C3...
> >
> > I compiled a kernel without USB/sound/radeon, and ran without X. I was
> > able to get the wakeups/sec down below 20, but no time is spent in C3.
> >
> > sysfs looks to agree with powertop here (time = 0 on C3):
> > /sys/devices/system/cpu/cpu0/cpuidle/state0/desc: CPUIDLE CORE POLL IDLE
> > /sys/devices/system/cpu/cpu0/cpuidle/state0/latency: 0
> > /sys/devices/system/cpu/cpu0/cpuidle/state0/name: C0
> > /sys/devices/system/cpu/cpu0/cpuidle/state0/power: 4294967295
> > /sys/devices/system/cpu/cpu0/cpuidle/state0/time: 457
> > /sys/devices/system/cpu/cpu0/cpuidle/state0/usage: 59
> > /sys/devices/system/cpu/cpu0/cpuidle/state1/desc: ACPI FFH INTEL MWAIT 0x0
> > /sys/devices/system/cpu/cpu0/cpuidle/state1/latency: 1
> > /sys/devices/system/cpu/cpu0/cpuidle/state1/name: C1
> > /sys/devices/system/cpu/cpu0/cpuidle/state1/power: 1000
> > /sys/devices/system/cpu/cpu0/cpuidle/state1/time: 308177
> > /sys/devices/system/cpu/cpu0/cpuidle/state1/usage: 3975
> > /sys/devices/system/cpu/cpu0/cpuidle/state2/desc: ACPI FFH INTEL MWAIT 0x10
> > /sys/devices/system/cpu/cpu0/cpuidle/state2/latency: 17
> > /sys/devices/system/cpu/cpu0/cpuidle/state2/name: C2
> > /sys/devices/system/cpu/cpu0/cpuidle/state2/power: 500
> > /sys/devices/system/cpu/cpu0/cpuidle/state2/time: 873440787
> > /sys/devices/system/cpu/cpu0/cpuidle/state2/usage: 239038
> > /sys/devices/system/cpu/cpu0/cpuidle/state3/desc: ACPI FFH INTEL MWAIT 0x20
> > /sys/devices/system/cpu/cpu0/cpuidle/state3/latency: 17
> > /sys/devices/system/cpu/cpu0/cpuidle/state3/name: C3
> > /sys/devices/system/cpu/cpu0/cpuidle/state3/power: 350
> > /sys/devices/system/cpu/cpu0/cpuidle/state3/time: 0
> > /sys/devices/system/cpu/cpu0/cpuidle/state3/usage: 0
> >
> > This may be a complete red herring, but I added some printk logic to
> > acpi_idle_bm_check(), and it is getting called often, but bm_status is
> > always 1. [I infer from this that the idle logic is trying to go into
> > C3, but this check is stopping it... Unless I misread something.]
> >
> > Is this expected behavior or is this a legitimate problem?
> >
> > How might I investigate this further?
> >
> > Attaching dmesg, /proc/cpuinfo, powertop -d output.
> >
> > Thanks,
> > Jeff Garrett
>
>
> --
> peng huang <huangpeng.linux@gmail.com>
>
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: acpi_idle: Very idle Core i7 machine never enters C3
2010-01-26 8:47 acpi_idle: Very idle Core i7 machine never enters C3 Jeff Garrett
@ 2010-01-26 21:45 ` Andi Kleen
2010-01-26 21:45 ` Andi Kleen
2010-02-01 14:10 ` Pavel Machek
2 siblings, 0 replies; 54+ messages in thread
From: Andi Kleen @ 2010-01-26 21:45 UTC (permalink / raw)
To: Jeff Garrett; +Cc: linux-kernel, Len Brown, linux-acpi
jeff@jgarrett.org (Jeff Garrett) writes:
> Hi,
>
> I was trying to chase down a theory that my desktop machine (a core i7)
> is running warm (the fan sounds like it's at full speed all the time,
> and I think it's not always acted this way -- hence the theory).
>
> powertop is never showing it spending any time in C3...
>
> I compiled a kernel without USB/sound/radeon, and ran without X. I was
> able to get the wakeups/sec down below 20, but no time is spent in C3.
[...]
> This may be a complete red herring, but I added some printk logic to
> acpi_idle_bm_check(), and it is getting called often, but bm_status is
> always 1. [I infer from this that the idle logic is trying to go into
> C3, but this check is stopping it... Unless I misread something.]
Normally a Core i7 (or any modern Intel systems) should not use
bm_check at all. That's only for older systems that didn't support
MWAIT with c-state hint, but relied on the old port based interface.
So something is already confused there.
I think it should still work though.
Of course if you really have a lot of bus mastering in the background
then yes there will be no C3.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: acpi_idle: Very idle Core i7 machine never enters C3
@ 2010-01-26 21:45 ` Andi Kleen
0 siblings, 0 replies; 54+ messages in thread
From: Andi Kleen @ 2010-01-26 21:45 UTC (permalink / raw)
To: Jeff Garrett; +Cc: linux-kernel, Len Brown, linux-acpi
jeff@jgarrett.org (Jeff Garrett) writes:
> Hi,
>
> I was trying to chase down a theory that my desktop machine (a core i7)
> is running warm (the fan sounds like it's at full speed all the time,
> and I think it's not always acted this way -- hence the theory).
>
> powertop is never showing it spending any time in C3...
>
> I compiled a kernel without USB/sound/radeon, and ran without X. I was
> able to get the wakeups/sec down below 20, but no time is spent in C3.
[...]
> This may be a complete red herring, but I added some printk logic to
> acpi_idle_bm_check(), and it is getting called often, but bm_status is
> always 1. [I infer from this that the idle logic is trying to go into
> C3, but this check is stopping it... Unless I misread something.]
Normally a Core i7 (or any modern Intel systems) should not use
bm_check at all. That's only for older systems that didn't support
MWAIT with c-state hint, but relied on the old port based interface.
So something is already confused there.
I think it should still work though.
Of course if you really have a lot of bus mastering in the background
then yes there will be no C3.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: acpi_idle: Very idle Core i7 machine never enters C3
2010-01-26 14:59 ` Jeff Garrett
@ 2010-01-27 13:27 ` peng huang
-1 siblings, 0 replies; 54+ messages in thread
From: peng huang @ 2010-01-27 13:27 UTC (permalink / raw)
To: Jeff Garrett; +Cc: linux-kernel, Len Brown, linux-acpi, huangpeng.linux
2010-01-26 (火) の 08:59 -0600 に Jeff Garrett さんは書きました:
> On Tue, Jan 26, 2010 at 09:41:00PM +0900, peng huang wrote:
> > Hi,
> > can you show me the file /proc/acpi/processor/CPU*/power.
> > and are you sure your cpu usage is 0 or nearly zero.
>
> Yea, I'm pretty sure my cpu usage is nearly zero. powertop shows fewer
> than 20 wakeups per second, shows 99% C2 residency, top shows 100% idle,
> perf top shows acpi_idle_enter_simple as the most common function
> (~50%). Very little is running on the box, and I've compiled out the
> heavier parts of the kernel (such as USB)...
>
> (It still has ordinary userspace running, e.g. udev & hal, and still has
> sshd and network traffic, as examples.)
>
> This is all consistent with a very idle machine, I think.
yes,you processor is always in c2,it does means your system is nearly
ilde.
> > this is the info of my laptop(using core 2 processors):
> > powertop's output:
> > Cn Avg residency P-states (frequencies)
> > C0 (cpu running) (10.6%) 2.00 Ghz 1.9%
> > C0 0.0ms ( 0.0%) 1.67 Ghz 0.1%
> > C1 mwait 0.0ms ( 0.0%) 1333 Mhz 0.0%
> > C2 mwait 0.0ms ( 0.0%) 1000 Mhz 98.0%
> > C3 mwait 1.1ms (89.4%)
>
> Yea, my laptop also (also core 2) has 700-1000 wakeups/sec and spends
> greater than 80% of its time in C3... That's partly why I'm curious
> about what my core i7 desktop is doing.
So I think it is a core i7 thing.I have heard that some intel cpu have a
problem when in c2-state,maybe that is why you cpu cant enter c3-state.
I think there is some configuration about deep c-state in the bios,may
be you can try it(it cannot solve this problem...).
And in some bios there is a enhanced idle state configuration ,but i
dont known if it is the reason why the cpu cannot enter c3-state.You can
try it anyway.
With disable the deep c-state you BIOS will not give c3-info to the
OS,then you would see there is no c3-state in the OS.
> > and power things:
> > huang@huang-laptop:~$ cat /proc/acpi/processor/CPU0/power
> > active state: C0
> > max_cstate: C8
> > maximum allowed latency: 2000000000 usec
> > states:
> > C1: type[C1] promotion[--] demotion[--]
> > latency[001] usage[00002364] duration[00000000000000000000]
> > C2: type[C2] promotion[--] demotion[--]
> > latency[001] usage[00070662] duration[00000000000006013816]
> > C3: type[C3] promotion[--] demotion[--]
> > latency[017] usage[04774185] duration[00000000010838418152]
> >
> > you can see C3 with powertop,so i think your BIOS has enabled Deep
> > C-state.
>
> Here's my power files...
>
> /proc/acpi/processor/CPU0/power:
> active state: C0
> max_cstate: C8
> maximum allowed latency: 2000000000 usec
> states:
> C1: type[C1] promotion[--] demotion[--] latency[001] usage[00001470] duration[00000000000000000000]
> C2: type[C2] promotion[--] demotion[--] latency[017] usage[00234416] duration[00000000017165798539]
> C3: type[C3] promotion[--] demotion[--] latency[017] usage[00000000] duration[00000000000000000000]
> /proc/acpi/processor/CPU1/power:
> active state: C0
> max_cstate: C8
> maximum allowed latency: 2000000000 usec
> states:
> C1: type[C1] promotion[--] demotion[--] latency[001] usage[00000481] duration[00000000000000000000]
> C2: type[C2] promotion[--] demotion[--] latency[017] usage[00090169] duration[00000000017188463157]
> C3: type[C3] promotion[--] demotion[--] latency[017] usage[00000000] duration[00000000000000000000]
> /proc/acpi/processor/CPU2/power:
> active state: C0
> max_cstate: C8
> maximum allowed latency: 2000000000 usec
> states:
> C1: type[C1] promotion[--] demotion[--] latency[001] usage[00000418] duration[00000000000000000000]
> C2: type[C2] promotion[--] demotion[--] latency[017] usage[00068874] duration[00000000017193805291]
> C3: type[C3] promotion[--] demotion[--] latency[017] usage[00000000] duration[00000000000000000000]
> /proc/acpi/processor/CPU3/power:
> active state: C0
> max_cstate: C8
> maximum allowed latency: 2000000000 usec
> states:
> C1: type[C1] promotion[--] demotion[--] latency[001] usage[00001356] duration[00000000000000000000]
> C2: type[C2] promotion[--] demotion[--] latency[017] usage[00362752] duration[00000000017156707397]
> C3: type[C3] promotion[--] demotion[--] latency[017] usage[00000000] duration[00000000000000000000]
>
> >
> > -huang
> >
> > 2010-01-26 (火) の 02:47 -0600 に Jeff Garrett さんは書きました:
> > > Hi,
> > >
> > > I was trying to chase down a theory that my desktop machine (a core i7)
> > > is running warm (the fan sounds like it's at full speed all the time,
> > > and I think it's not always acted this way -- hence the theory).
> > >
> > > powertop is never showing it spending any time in C3...
> > >
> > > I compiled a kernel without USB/sound/radeon, and ran without X. I was
> > > able to get the wakeups/sec down below 20, but no time is spent in C3.
> > >
> > > sysfs looks to agree with powertop here (time = 0 on C3):
> > > /sys/devices/system/cpu/cpu0/cpuidle/state0/desc: CPUIDLE CORE POLL IDLE
> > > /sys/devices/system/cpu/cpu0/cpuidle/state0/latency: 0
> > > /sys/devices/system/cpu/cpu0/cpuidle/state0/name: C0
> > > /sys/devices/system/cpu/cpu0/cpuidle/state0/power: 4294967295
> > > /sys/devices/system/cpu/cpu0/cpuidle/state0/time: 457
> > > /sys/devices/system/cpu/cpu0/cpuidle/state0/usage: 59
> > > /sys/devices/system/cpu/cpu0/cpuidle/state1/desc: ACPI FFH INTEL MWAIT 0x0
> > > /sys/devices/system/cpu/cpu0/cpuidle/state1/latency: 1
> > > /sys/devices/system/cpu/cpu0/cpuidle/state1/name: C1
> > > /sys/devices/system/cpu/cpu0/cpuidle/state1/power: 1000
> > > /sys/devices/system/cpu/cpu0/cpuidle/state1/time: 308177
> > > /sys/devices/system/cpu/cpu0/cpuidle/state1/usage: 3975
> > > /sys/devices/system/cpu/cpu0/cpuidle/state2/desc: ACPI FFH INTEL MWAIT 0x10
> > > /sys/devices/system/cpu/cpu0/cpuidle/state2/latency: 17
> > > /sys/devices/system/cpu/cpu0/cpuidle/state2/name: C2
> > > /sys/devices/system/cpu/cpu0/cpuidle/state2/power: 500
> > > /sys/devices/system/cpu/cpu0/cpuidle/state2/time: 873440787
> > > /sys/devices/system/cpu/cpu0/cpuidle/state2/usage: 239038
> > > /sys/devices/system/cpu/cpu0/cpuidle/state3/desc: ACPI FFH INTEL MWAIT 0x20
> > > /sys/devices/system/cpu/cpu0/cpuidle/state3/latency: 17
> > > /sys/devices/system/cpu/cpu0/cpuidle/state3/name: C3
> > > /sys/devices/system/cpu/cpu0/cpuidle/state3/power: 350
> > > /sys/devices/system/cpu/cpu0/cpuidle/state3/time: 0
> > > /sys/devices/system/cpu/cpu0/cpuidle/state3/usage: 0
> > >
> > > This may be a complete red herring, but I added some printk logic to
> > > acpi_idle_bm_check(), and it is getting called often, but bm_status is
> > > always 1. [I infer from this that the idle logic is trying to go into
> > > C3, but this check is stopping it... Unless I misread something.]
> > >
> > > Is this expected behavior or is this a legitimate problem?
> > >
> > > How might I investigate this further?
> > >
> > > Attaching dmesg, /proc/cpuinfo, powertop -d output.
> > >
> > > Thanks,
> > > Jeff Garrett
> >
> >
> > --
> > peng huang <huangpeng.linux@gmail.com>
> >
--
peng huang <huangpeng.linux@gmail.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: acpi_idle: Very idle Core i7 machine never enters C3
@ 2010-01-27 13:27 ` peng huang
0 siblings, 0 replies; 54+ messages in thread
From: peng huang @ 2010-01-27 13:27 UTC (permalink / raw)
To: Jeff Garrett; +Cc: linux-kernel, Len Brown, linux-acpi, huangpeng.linux
2010-01-26 (火) の 08:59 -0600 に Jeff Garrett さんは書きました:
> On Tue, Jan 26, 2010 at 09:41:00PM +0900, peng huang wrote:
> > Hi,
> > can you show me the file /proc/acpi/processor/CPU*/power.
> > and are you sure your cpu usage is 0 or nearly zero.
>
> Yea, I'm pretty sure my cpu usage is nearly zero. powertop shows fewer
> than 20 wakeups per second, shows 99% C2 residency, top shows 100% idle,
> perf top shows acpi_idle_enter_simple as the most common function
> (~50%). Very little is running on the box, and I've compiled out the
> heavier parts of the kernel (such as USB)...
>
> (It still has ordinary userspace running, e.g. udev & hal, and still has
> sshd and network traffic, as examples.)
>
> This is all consistent with a very idle machine, I think.
yes,you processor is always in c2,it does means your system is nearly
ilde.
> > this is the info of my laptop(using core 2 processors):
> > powertop's output:
> > Cn Avg residency P-states (frequencies)
> > C0 (cpu running) (10.6%) 2.00 Ghz 1.9%
> > C0 0.0ms ( 0.0%) 1.67 Ghz 0.1%
> > C1 mwait 0.0ms ( 0.0%) 1333 Mhz 0.0%
> > C2 mwait 0.0ms ( 0.0%) 1000 Mhz 98.0%
> > C3 mwait 1.1ms (89.4%)
>
> Yea, my laptop also (also core 2) has 700-1000 wakeups/sec and spends
> greater than 80% of its time in C3... That's partly why I'm curious
> about what my core i7 desktop is doing.
So I think it is a core i7 thing.I have heard that some intel cpu have a
problem when in c2-state,maybe that is why you cpu cant enter c3-state.
I think there is some configuration about deep c-state in the bios,may
be you can try it(it cannot solve this problem...).
And in some bios there is a enhanced idle state configuration ,but i
dont known if it is the reason why the cpu cannot enter c3-state.You can
try it anyway.
With disable the deep c-state you BIOS will not give c3-info to the
OS,then you would see there is no c3-state in the OS.
> > and power things:
> > huang@huang-laptop:~$ cat /proc/acpi/processor/CPU0/power
> > active state: C0
> > max_cstate: C8
> > maximum allowed latency: 2000000000 usec
> > states:
> > C1: type[C1] promotion[--] demotion[--]
> > latency[001] usage[00002364] duration[00000000000000000000]
> > C2: type[C2] promotion[--] demotion[--]
> > latency[001] usage[00070662] duration[00000000000006013816]
> > C3: type[C3] promotion[--] demotion[--]
> > latency[017] usage[04774185] duration[00000000010838418152]
> >
> > you can see C3 with powertop,so i think your BIOS has enabled Deep
> > C-state.
>
> Here's my power files...
>
> /proc/acpi/processor/CPU0/power:
> active state: C0
> max_cstate: C8
> maximum allowed latency: 2000000000 usec
> states:
> C1: type[C1] promotion[--] demotion[--] latency[001] usage[00001470] duration[00000000000000000000]
> C2: type[C2] promotion[--] demotion[--] latency[017] usage[00234416] duration[00000000017165798539]
> C3: type[C3] promotion[--] demotion[--] latency[017] usage[00000000] duration[00000000000000000000]
> /proc/acpi/processor/CPU1/power:
> active state: C0
> max_cstate: C8
> maximum allowed latency: 2000000000 usec
> states:
> C1: type[C1] promotion[--] demotion[--] latency[001] usage[00000481] duration[00000000000000000000]
> C2: type[C2] promotion[--] demotion[--] latency[017] usage[00090169] duration[00000000017188463157]
> C3: type[C3] promotion[--] demotion[--] latency[017] usage[00000000] duration[00000000000000000000]
> /proc/acpi/processor/CPU2/power:
> active state: C0
> max_cstate: C8
> maximum allowed latency: 2000000000 usec
> states:
> C1: type[C1] promotion[--] demotion[--] latency[001] usage[00000418] duration[00000000000000000000]
> C2: type[C2] promotion[--] demotion[--] latency[017] usage[00068874] duration[00000000017193805291]
> C3: type[C3] promotion[--] demotion[--] latency[017] usage[00000000] duration[00000000000000000000]
> /proc/acpi/processor/CPU3/power:
> active state: C0
> max_cstate: C8
> maximum allowed latency: 2000000000 usec
> states:
> C1: type[C1] promotion[--] demotion[--] latency[001] usage[00001356] duration[00000000000000000000]
> C2: type[C2] promotion[--] demotion[--] latency[017] usage[00362752] duration[00000000017156707397]
> C3: type[C3] promotion[--] demotion[--] latency[017] usage[00000000] duration[00000000000000000000]
>
> >
> > -huang
> >
> > 2010-01-26 (火) の 02:47 -0600 に Jeff Garrett さんは書きました:
> > > Hi,
> > >
> > > I was trying to chase down a theory that my desktop machine (a core i7)
> > > is running warm (the fan sounds like it's at full speed all the time,
> > > and I think it's not always acted this way -- hence the theory).
> > >
> > > powertop is never showing it spending any time in C3...
> > >
> > > I compiled a kernel without USB/sound/radeon, and ran without X. I was
> > > able to get the wakeups/sec down below 20, but no time is spent in C3.
> > >
> > > sysfs looks to agree with powertop here (time = 0 on C3):
> > > /sys/devices/system/cpu/cpu0/cpuidle/state0/desc: CPUIDLE CORE POLL IDLE
> > > /sys/devices/system/cpu/cpu0/cpuidle/state0/latency: 0
> > > /sys/devices/system/cpu/cpu0/cpuidle/state0/name: C0
> > > /sys/devices/system/cpu/cpu0/cpuidle/state0/power: 4294967295
> > > /sys/devices/system/cpu/cpu0/cpuidle/state0/time: 457
> > > /sys/devices/system/cpu/cpu0/cpuidle/state0/usage: 59
> > > /sys/devices/system/cpu/cpu0/cpuidle/state1/desc: ACPI FFH INTEL MWAIT 0x0
> > > /sys/devices/system/cpu/cpu0/cpuidle/state1/latency: 1
> > > /sys/devices/system/cpu/cpu0/cpuidle/state1/name: C1
> > > /sys/devices/system/cpu/cpu0/cpuidle/state1/power: 1000
> > > /sys/devices/system/cpu/cpu0/cpuidle/state1/time: 308177
> > > /sys/devices/system/cpu/cpu0/cpuidle/state1/usage: 3975
> > > /sys/devices/system/cpu/cpu0/cpuidle/state2/desc: ACPI FFH INTEL MWAIT 0x10
> > > /sys/devices/system/cpu/cpu0/cpuidle/state2/latency: 17
> > > /sys/devices/system/cpu/cpu0/cpuidle/state2/name: C2
> > > /sys/devices/system/cpu/cpu0/cpuidle/state2/power: 500
> > > /sys/devices/system/cpu/cpu0/cpuidle/state2/time: 873440787
> > > /sys/devices/system/cpu/cpu0/cpuidle/state2/usage: 239038
> > > /sys/devices/system/cpu/cpu0/cpuidle/state3/desc: ACPI FFH INTEL MWAIT 0x20
> > > /sys/devices/system/cpu/cpu0/cpuidle/state3/latency: 17
> > > /sys/devices/system/cpu/cpu0/cpuidle/state3/name: C3
> > > /sys/devices/system/cpu/cpu0/cpuidle/state3/power: 350
> > > /sys/devices/system/cpu/cpu0/cpuidle/state3/time: 0
> > > /sys/devices/system/cpu/cpu0/cpuidle/state3/usage: 0
> > >
> > > This may be a complete red herring, but I added some printk logic to
> > > acpi_idle_bm_check(), and it is getting called often, but bm_status is
> > > always 1. [I infer from this that the idle logic is trying to go into
> > > C3, but this check is stopping it... Unless I misread something.]
> > >
> > > Is this expected behavior or is this a legitimate problem?
> > >
> > > How might I investigate this further?
> > >
> > > Attaching dmesg, /proc/cpuinfo, powertop -d output.
> > >
> > > Thanks,
> > > Jeff Garrett
> >
> >
> > --
> > peng huang <huangpeng.linux@gmail.com>
> >
--
peng huang <huangpeng.linux@gmail.com>
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: acpi_idle: Very idle Core i7 machine never enters C3
2010-01-26 8:47 acpi_idle: Very idle Core i7 machine never enters C3 Jeff Garrett
2010-01-26 12:41 ` peng huang
2010-01-26 21:45 ` Andi Kleen
@ 2010-02-01 14:10 ` Pavel Machek
2010-02-05 16:30 ` Jeff Garrett
2 siblings, 1 reply; 54+ messages in thread
From: Pavel Machek @ 2010-02-01 14:10 UTC (permalink / raw)
To: Jeff Garrett; +Cc: linux-kernel, Len Brown, linux-acpi
On Tue 2010-01-26 02:47:40, Jeff Garrett wrote:
> Hi,
>
> I was trying to chase down a theory that my desktop machine (a core i7)
> is running warm (the fan sounds like it's at full speed all the time,
> and I think it's not always acted this way -- hence the theory).
>
> powertop is never showing it spending any time in C3...
>
> I compiled a kernel without USB/sound/radeon, and ran without X. I was
> able to get the wakeups/sec down below 20, but no time is spent in C3.
> This may be a complete red herring, but I added some printk logic to
> acpi_idle_bm_check(), and it is getting called often, but bm_status is
> always 1. [I infer from this that the idle logic is trying to go into
> C3, but this check is stopping it... Unless I misread something.]
>
> Is this expected behavior or is this a legitimate problem?
>
> How might I investigate this further?
DMA keeps system awake? Possibly USB?
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: acpi_idle: Very idle Core i7 machine never enters C3
2010-01-26 21:45 ` Andi Kleen
(?)
@ 2010-02-05 16:09 ` Jeff Garrett
2010-02-05 17:45 ` Len Brown
-1 siblings, 1 reply; 54+ messages in thread
From: Jeff Garrett @ 2010-02-05 16:09 UTC (permalink / raw)
To: Andi Kleen; +Cc: linux-kernel, Len Brown, linux-acpi
On Tue, Jan 26, 2010 at 10:45:20PM +0100, Andi Kleen wrote:
> jeff@jgarrett.org (Jeff Garrett) writes:
>
> > Hi,
> >
> > I was trying to chase down a theory that my desktop machine (a core i7)
> > is running warm (the fan sounds like it's at full speed all the time,
> > and I think it's not always acted this way -- hence the theory).
> >
> > powertop is never showing it spending any time in C3...
> >
> > I compiled a kernel without USB/sound/radeon, and ran without X. I was
> > able to get the wakeups/sec down below 20, but no time is spent in C3.
>
> [...]
> > This may be a complete red herring, but I added some printk logic to
> > acpi_idle_bm_check(), and it is getting called often, but bm_status is
> > always 1. [I infer from this that the idle logic is trying to go into
> > C3, but this check is stopping it... Unless I misread something.]
>
> Normally a Core i7 (or any modern Intel systems) should not use
> bm_check at all. That's only for older systems that didn't support
> MWAIT with c-state hint, but relied on the old port based interface.
bm_check = 1, bm_control = 0
I don't know what any of this means. :)
I tried changing processor_idle.c. It reads (for C3):
1106 state->enter = pr->flags.bm_check ?
1107 acpi_idle_enter_bm :
1108 acpi_idle_enter_simple;
So it always calls acpi_idle_enter_bm in my case. I tried modifying it
to call acpi_idle_enter_simple for entering C3 instead. When I did
this, it did make it into C3 according to powertop, but the wakeups per
second grew by at least 10x. I couldn't get that below ~400-800/s, and
the residency in C3 was limited to about ~50%, as reported by powertop.
> So something is already confused there.
Might just be me. :)
> I think it should still work though.
> Of course if you really have a lot of bus mastering in the background
> then yes there will be no C3.
>
> -Andi
I have no idea what counts as bus mastering (is it just DMA transfers to
PCI devices?)... But with a fairly idle system, with things like USB
configured out, what could be doing it if it exists? Would there be
some nice function I could instrument with a few printk's to, to see? I
compiled with PCI_DEBUG=y, and "bus master" doesn't show up in the
dmesg.
-Jeff
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: acpi_idle: Very idle Core i7 machine never enters C3
2010-01-27 13:27 ` peng huang
@ 2010-02-05 16:22 ` Jeff Garrett
-1 siblings, 0 replies; 54+ messages in thread
From: Jeff Garrett @ 2010-02-05 16:22 UTC (permalink / raw)
To: peng huang; +Cc: linux-kernel, Len Brown, linux-acpi
On Wed, Jan 27, 2010 at 10:27:17PM +0900, peng huang wrote:
> 2010-01-26 (火) の 08:59 -0600 に Jeff Garrett さんは書きました:
> > On Tue, Jan 26, 2010 at 09:41:00PM +0900, peng huang wrote:
> > > Hi,
> > > can you show me the file /proc/acpi/processor/CPU*/power.
> > > and are you sure your cpu usage is 0 or nearly zero.
> >
> > Yea, I'm pretty sure my cpu usage is nearly zero. powertop shows fewer
> > than 20 wakeups per second, shows 99% C2 residency, top shows 100% idle,
> > perf top shows acpi_idle_enter_simple as the most common function
> > (~50%). Very little is running on the box, and I've compiled out the
> > heavier parts of the kernel (such as USB)...
> >
> > (It still has ordinary userspace running, e.g. udev & hal, and still has
> > sshd and network traffic, as examples.)
> >
> > This is all consistent with a very idle machine, I think.
>
> yes,you processor is always in c2,it does means your system is nearly
> ilde.
>
> > > this is the info of my laptop(using core 2 processors):
> > > powertop's output:
> > > Cn Avg residency P-states (frequencies)
> > > C0 (cpu running) (10.6%) 2.00 Ghz 1.9%
> > > C0 0.0ms ( 0.0%) 1.67 Ghz 0.1%
> > > C1 mwait 0.0ms ( 0.0%) 1333 Mhz 0.0%
> > > C2 mwait 0.0ms ( 0.0%) 1000 Mhz 98.0%
> > > C3 mwait 1.1ms (89.4%)
> >
> > Yea, my laptop also (also core 2) has 700-1000 wakeups/sec and spends
> > greater than 80% of its time in C3... That's partly why I'm curious
> > about what my core i7 desktop is doing.
>
> So I think it is a core i7 thing.I have heard that some intel cpu have a
> problem when in c2-state,maybe that is why you cpu cant enter c3-state.
> I think there is some configuration about deep c-state in the bios,may
> be you can try it(it cannot solve this problem...).
My BIOS has very few options. Almost nothing with regard to
power management. They do let me choose whether to enable
Intel SpeedStep. They also let me choose which state to use
for ACPI suspend (set to S3) but that appears to be it.
> And in some bios there is a enhanced idle state configuration ,but i
> dont known if it is the reason why the cpu cannot enter c3-state.You can
> try it anyway.
I would if I could. :)
> With disable the deep c-state you BIOS will not give c3-info to the
> OS,then you would see there is no c3-state in the OS.
I also found a thread (I think LKML) which said the max c-state is
limited when HT is disabled. I had HT disabled in the BIOS.
Re-enabling HT in the BIOS (with CONFIG_X86_HT=y) doesn't
appear to make any difference.
Thanks,
Jeff
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: acpi_idle: Very idle Core i7 machine never enters C3
@ 2010-02-05 16:22 ` Jeff Garrett
0 siblings, 0 replies; 54+ messages in thread
From: Jeff Garrett @ 2010-02-05 16:22 UTC (permalink / raw)
To: peng huang; +Cc: linux-kernel, Len Brown, linux-acpi
On Wed, Jan 27, 2010 at 10:27:17PM +0900, peng huang wrote:
> 2010-01-26 (火) の 08:59 -0600 に Jeff Garrett さんは書きました:
> > On Tue, Jan 26, 2010 at 09:41:00PM +0900, peng huang wrote:
> > > Hi,
> > > can you show me the file /proc/acpi/processor/CPU*/power.
> > > and are you sure your cpu usage is 0 or nearly zero.
> >
> > Yea, I'm pretty sure my cpu usage is nearly zero. powertop shows fewer
> > than 20 wakeups per second, shows 99% C2 residency, top shows 100% idle,
> > perf top shows acpi_idle_enter_simple as the most common function
> > (~50%). Very little is running on the box, and I've compiled out the
> > heavier parts of the kernel (such as USB)...
> >
> > (It still has ordinary userspace running, e.g. udev & hal, and still has
> > sshd and network traffic, as examples.)
> >
> > This is all consistent with a very idle machine, I think.
>
> yes,you processor is always in c2,it does means your system is nearly
> ilde.
>
> > > this is the info of my laptop(using core 2 processors):
> > > powertop's output:
> > > Cn Avg residency P-states (frequencies)
> > > C0 (cpu running) (10.6%) 2.00 Ghz 1.9%
> > > C0 0.0ms ( 0.0%) 1.67 Ghz 0.1%
> > > C1 mwait 0.0ms ( 0.0%) 1333 Mhz 0.0%
> > > C2 mwait 0.0ms ( 0.0%) 1000 Mhz 98.0%
> > > C3 mwait 1.1ms (89.4%)
> >
> > Yea, my laptop also (also core 2) has 700-1000 wakeups/sec and spends
> > greater than 80% of its time in C3... That's partly why I'm curious
> > about what my core i7 desktop is doing.
>
> So I think it is a core i7 thing.I have heard that some intel cpu have a
> problem when in c2-state,maybe that is why you cpu cant enter c3-state.
> I think there is some configuration about deep c-state in the bios,may
> be you can try it(it cannot solve this problem...).
My BIOS has very few options. Almost nothing with regard to
power management. They do let me choose whether to enable
Intel SpeedStep. They also let me choose which state to use
for ACPI suspend (set to S3) but that appears to be it.
> And in some bios there is a enhanced idle state configuration ,but i
> dont known if it is the reason why the cpu cannot enter c3-state.You can
> try it anyway.
I would if I could. :)
> With disable the deep c-state you BIOS will not give c3-info to the
> OS,then you would see there is no c3-state in the OS.
I also found a thread (I think LKML) which said the max c-state is
limited when HT is disabled. I had HT disabled in the BIOS.
Re-enabling HT in the BIOS (with CONFIG_X86_HT=y) doesn't
appear to make any difference.
Thanks,
Jeff
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: acpi_idle: Very idle Core i7 machine never enters C3
2010-02-01 14:10 ` Pavel Machek
@ 2010-02-05 16:30 ` Jeff Garrett
0 siblings, 0 replies; 54+ messages in thread
From: Jeff Garrett @ 2010-02-05 16:30 UTC (permalink / raw)
To: Pavel Machek; +Cc: linux-kernel, Len Brown, linux-acpi
[-- Attachment #1: Type: text/plain, Size: 1434 bytes --]
On Mon, Feb 01, 2010 at 03:10:38PM +0100, Pavel Machek wrote:
> On Tue 2010-01-26 02:47:40, Jeff Garrett wrote:
> > Hi,
> >
> > I was trying to chase down a theory that my desktop machine (a core i7)
> > is running warm (the fan sounds like it's at full speed all the time,
> > and I think it's not always acted this way -- hence the theory).
> >
> > powertop is never showing it spending any time in C3...
> >
> > I compiled a kernel without USB/sound/radeon, and ran without X. I was
> > able to get the wakeups/sec down below 20, but no time is spent in C3.
>
> > This may be a complete red herring, but I added some printk logic to
> > acpi_idle_bm_check(), and it is getting called often, but bm_status is
> > always 1. [I infer from this that the idle logic is trying to go into
> > C3, but this check is stopping it... Unless I misread something.]
> >
> > Is this expected behavior or is this a legitimate problem?
> >
> > How might I investigate this further?
>
> DMA keeps system awake? Possibly USB?
X is not running. USB is not enabled at all (CONFIG_USB_SUPPORT is not
set), and likewise for sound & drm. What could be doing the DMA? :)
If there is DMA, it could be disk or network related. However, I
find it hard to believe that this activity is so constant on a nearly
idle system... Of course, I haven't thought of a way to test this yet.
Attaching my config & dmesg of my latest try.
Thanks,
-Jeff
[-- Attachment #2: config --]
[-- Type: text/plain, Size: 80091 bytes --]
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.33-rc6
# Mon Feb 1 08:59:09 2010
#
CONFIG_64BIT=y
# CONFIG_X86_32 is not set
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_OUTPUT_FORMAT="elf64-x86-64"
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig"
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_GENERIC_GPIO=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_RWSEM_GENERIC_SPINLOCK=y
# CONFIG_RWSEM_XCHGADD_ALGORITHM is not set
CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_DEFAULT_IDLE=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y
CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
CONFIG_HAVE_CPUMASK_OF_CPU_MAP=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ZONE_DMA32=y
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_AUDIT_ARCH=y
CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_HARDIRQS_NO__DO_IRQ=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_USE_GENERIC_SMP_HELPERS=y
CONFIG_X86_64_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_TRAMPOLINE=y
# CONFIG_KTIME_SCALAR is not set
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
CONFIG_CONSTRUCTORS=y
#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION=""
# CONFIG_LOCALVERSION_AUTO is not set
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_BZIP2=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_HAVE_KERNEL_LZO=y
# CONFIG_KERNEL_GZIP is not set
# CONFIG_KERNEL_BZIP2 is not set
CONFIG_KERNEL_LZMA=y
# CONFIG_KERNEL_LZO is not set
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_POSIX_MQUEUE_SYSCTL=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_BSD_PROCESS_ACCT_V3=y
# CONFIG_TASKSTATS is not set
# CONFIG_AUDIT is not set
#
# RCU Subsystem
#
CONFIG_TREE_RCU=y
# CONFIG_TREE_PREEMPT_RCU is not set
# CONFIG_TINY_RCU is not set
# CONFIG_RCU_TRACE is not set
CONFIG_RCU_FANOUT=64
# CONFIG_RCU_FANOUT_EXACT is not set
# CONFIG_TREE_RCU_TRACE is not set
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=18
CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
# CONFIG_GROUP_SCHED is not set
# CONFIG_CGROUPS is not set
# CONFIG_SYSFS_DEPRECATED_V2 is not set
CONFIG_RELAY=y
CONFIG_NAMESPACES=y
# CONFIG_UTS_NS is not set
# CONFIG_IPC_NS is not set
# CONFIG_USER_NS is not set
# CONFIG_PID_NS is not set
# CONFIG_NET_NS is not set
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_RD_GZIP=y
CONFIG_RD_BZIP2=y
CONFIG_RD_LZMA=y
CONFIG_RD_LZO=y
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
CONFIG_ANON_INODES=y
# CONFIG_EMBEDDED is not set
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_PCSPKR_PLATFORM=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_AIO=y
CONFIG_HAVE_PERF_EVENTS=y
#
# Kernel Performance Events And Counters
#
CONFIG_PERF_EVENTS=y
CONFIG_EVENT_PROFILE=y
# CONFIG_PERF_COUNTERS is not set
# CONFIG_DEBUG_PERF_USE_VMALLOC is not set
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_PCI_QUIRKS=y
CONFIG_SLUB_DEBUG=y
# CONFIG_COMPAT_BRK is not set
# CONFIG_SLAB is not set
CONFIG_SLUB=y
# CONFIG_SLOB is not set
CONFIG_PROFILING=y
CONFIG_TRACEPOINTS=y
CONFIG_OPROFILE=y
# CONFIG_OPROFILE_IBS is not set
CONFIG_OPROFILE_EVENT_MULTIPLEX=y
CONFIG_HAVE_OPROFILE=y
# CONFIG_KPROBES is not set
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
CONFIG_HAVE_IOREMAP_PROT=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_ARCH_TRACEHOOK=y
CONFIG_HAVE_DMA_ATTRS=y
CONFIG_HAVE_DMA_API_DEBUG=y
CONFIG_HAVE_HW_BREAKPOINT=y
CONFIG_HAVE_USER_RETURN_NOTIFIER=y
#
# GCOV-based kernel profiling
#
# CONFIG_GCOV_KERNEL is not set
CONFIG_SLOW_WORK=y
# CONFIG_SLOW_WORK_DEBUG is not set
# CONFIG_HAVE_GENERIC_DMA_COHERENT is not set
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
# CONFIG_MODULE_FORCE_LOAD is not set
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_MODVERSIONS=y
CONFIG_MODULE_SRCVERSION_ALL=y
CONFIG_STOP_MACHINE=y
CONFIG_BLOCK=y
CONFIG_BLK_DEV_BSG=y
CONFIG_BLK_DEV_INTEGRITY=y
CONFIG_BLOCK_COMPAT=y
#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"
# CONFIG_INLINE_SPIN_TRYLOCK is not set
# CONFIG_INLINE_SPIN_TRYLOCK_BH is not set
# CONFIG_INLINE_SPIN_LOCK is not set
# CONFIG_INLINE_SPIN_LOCK_BH is not set
# CONFIG_INLINE_SPIN_LOCK_IRQ is not set
# CONFIG_INLINE_SPIN_LOCK_IRQSAVE is not set
CONFIG_INLINE_SPIN_UNLOCK=y
# CONFIG_INLINE_SPIN_UNLOCK_BH is not set
CONFIG_INLINE_SPIN_UNLOCK_IRQ=y
# CONFIG_INLINE_SPIN_UNLOCK_IRQRESTORE is not set
# CONFIG_INLINE_READ_TRYLOCK is not set
# CONFIG_INLINE_READ_LOCK is not set
# CONFIG_INLINE_READ_LOCK_BH is not set
# CONFIG_INLINE_READ_LOCK_IRQ is not set
# CONFIG_INLINE_READ_LOCK_IRQSAVE is not set
CONFIG_INLINE_READ_UNLOCK=y
# CONFIG_INLINE_READ_UNLOCK_BH is not set
CONFIG_INLINE_READ_UNLOCK_IRQ=y
# CONFIG_INLINE_READ_UNLOCK_IRQRESTORE is not set
# CONFIG_INLINE_WRITE_TRYLOCK is not set
# CONFIG_INLINE_WRITE_LOCK is not set
# CONFIG_INLINE_WRITE_LOCK_BH is not set
# CONFIG_INLINE_WRITE_LOCK_IRQ is not set
# CONFIG_INLINE_WRITE_LOCK_IRQSAVE is not set
CONFIG_INLINE_WRITE_UNLOCK=y
# CONFIG_INLINE_WRITE_UNLOCK_BH is not set
CONFIG_INLINE_WRITE_UNLOCK_IRQ=y
# CONFIG_INLINE_WRITE_UNLOCK_IRQRESTORE is not set
CONFIG_MUTEX_SPIN_ON_OWNER=y
CONFIG_FREEZER=y
#
# Processor type and features
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_SMP=y
CONFIG_SPARSE_IRQ=y
CONFIG_NUMA_IRQ_DESC=y
CONFIG_X86_MPPARSE=y
CONFIG_X86_EXTENDED_PLATFORM=y
# CONFIG_X86_VSMP is not set
CONFIG_X86_SUPPORTS_MEMORY_FAILURE=y
CONFIG_SCHED_OMIT_FRAME_POINTER=y
# CONFIG_PARAVIRT_GUEST is not set
# CONFIG_MEMTEST is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MGEODE_LX is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_MVIAC7 is not set
# CONFIG_MPSC is not set
# CONFIG_MCORE2 is not set
# CONFIG_MATOM is not set
CONFIG_GENERIC_CPU=y
CONFIG_X86_CPU=y
CONFIG_X86_INTERNODE_CACHE_SHIFT=7
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_TSC=y
CONFIG_X86_CMPXCHG64=y
CONFIG_X86_CMOV=y
CONFIG_X86_MINIMUM_CPU_FAMILY=64
CONFIG_X86_DEBUGCTLMSR=y
CONFIG_CPU_SUP_INTEL=y
CONFIG_CPU_SUP_AMD=y
CONFIG_CPU_SUP_CENTAUR=y
# CONFIG_X86_DS is not set
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_DMI=y
CONFIG_GART_IOMMU=y
# CONFIG_CALGARY_IOMMU is not set
CONFIG_AMD_IOMMU=y
CONFIG_AMD_IOMMU_STATS=y
CONFIG_SWIOTLB=y
CONFIG_IOMMU_HELPER=y
CONFIG_IOMMU_API=y
# CONFIG_MAXSMP is not set
CONFIG_NR_CPUS=64
CONFIG_SCHED_SMT=y
CONFIG_SCHED_MC=y
CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_INTEL=y
CONFIG_X86_MCE_AMD=y
CONFIG_X86_MCE_THRESHOLD=y
CONFIG_X86_MCE_INJECT=m
CONFIG_X86_THERMAL_VECTOR=y
CONFIG_I8K=m
CONFIG_MICROCODE=m
CONFIG_MICROCODE_INTEL=y
CONFIG_MICROCODE_AMD=y
CONFIG_MICROCODE_OLD_INTERFACE=y
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m
CONFIG_ARCH_PHYS_ADDR_T_64BIT=y
CONFIG_DIRECT_GBPAGES=y
CONFIG_NUMA=y
# CONFIG_K8_NUMA is not set
CONFIG_X86_64_ACPI_NUMA=y
CONFIG_NODES_SPAN_OTHER_NODES=y
# CONFIG_NUMA_EMU is not set
CONFIG_NODES_SHIFT=6
CONFIG_ARCH_PROC_KCORE_TEXT=y
CONFIG_ARCH_SPARSEMEM_DEFAULT=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_ILLEGAL_POINTER_VALUE=0xdead000000000000
CONFIG_SELECT_MEMORY_MODEL=y
# CONFIG_FLATMEM_MANUAL is not set
# CONFIG_DISCONTIGMEM_MANUAL is not set
CONFIG_SPARSEMEM_MANUAL=y
CONFIG_SPARSEMEM=y
CONFIG_NEED_MULTIPLE_NODES=y
CONFIG_HAVE_MEMORY_PRESENT=y
CONFIG_SPARSEMEM_EXTREME=y
CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y
CONFIG_SPARSEMEM_VMEMMAP=y
# CONFIG_MEMORY_HOTPLUG is not set
CONFIG_PAGEFLAGS_EXTENDED=y
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_MIGRATION=y
CONFIG_PHYS_ADDR_T_64BIT=y
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_VIRT_TO_BUS=y
# CONFIG_KSM is not set
CONFIG_DEFAULT_MMAP_MIN_ADDR=65536
CONFIG_ARCH_SUPPORTS_MEMORY_FAILURE=y
CONFIG_MEMORY_FAILURE=y
# CONFIG_HWPOISON_INJECT is not set
CONFIG_X86_CHECK_BIOS_CORRUPTION=y
CONFIG_X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK=y
CONFIG_X86_RESERVE_LOW_64K=y
CONFIG_MTRR=y
CONFIG_MTRR_SANITIZER=y
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=0
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1
CONFIG_X86_PAT=y
CONFIG_ARCH_USES_PG_UNCACHED=y
CONFIG_EFI=y
CONFIG_SECCOMP=y
# CONFIG_CC_STACKPROTECTOR is not set
CONFIG_HZ_100=y
# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=100
CONFIG_SCHED_HRTICK=y
CONFIG_KEXEC=y
CONFIG_CRASH_DUMP=y
CONFIG_KEXEC_JUMP=y
CONFIG_PHYSICAL_START=0x200000
CONFIG_RELOCATABLE=y
CONFIG_PHYSICAL_ALIGN=0x1000000
CONFIG_HOTPLUG_CPU=y
# CONFIG_COMPAT_VDSO is not set
# CONFIG_CMDLINE_BOOL is not set
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID=y
#
# Power management and ACPI options
#
CONFIG_ARCH_HIBERNATION_HEADER=y
CONFIG_PM=y
CONFIG_PM_DEBUG=y
# CONFIG_PM_VERBOSE is not set
CONFIG_CAN_PM_TRACE=y
CONFIG_PM_TRACE=y
CONFIG_PM_TRACE_RTC=y
CONFIG_PM_SLEEP_SMP=y
CONFIG_PM_SLEEP=y
CONFIG_SUSPEND=y
CONFIG_PM_TEST_SUSPEND=y
CONFIG_SUSPEND_FREEZER=y
CONFIG_HIBERNATION_NVS=y
CONFIG_HIBERNATION=y
CONFIG_PM_STD_PARTITION=""
CONFIG_PM_RUNTIME=y
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_PROCFS=y
# CONFIG_ACPI_PROCFS_POWER is not set
CONFIG_ACPI_POWER_METER=m
CONFIG_ACPI_SYSFS_POWER=y
# CONFIG_ACPI_PROC_EVENT is not set
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_FAN=y
CONFIG_ACPI_DOCK=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_HOTPLUG_CPU=y
CONFIG_ACPI_PROCESSOR_AGGREGATOR=m
CONFIG_ACPI_THERMAL=y
CONFIG_ACPI_NUMA=y
CONFIG_ACPI_CUSTOM_DSDT_FILE=""
# CONFIG_ACPI_CUSTOM_DSDT is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
CONFIG_ACPI_DEBUG=y
# CONFIG_ACPI_DEBUG_FUNC_TRACE is not set
CONFIG_ACPI_PCI_SLOT=y
CONFIG_X86_PM_TIMER=y
CONFIG_ACPI_CONTAINER=y
CONFIG_ACPI_SBS=y
# CONFIG_SFI is not set
#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
# CONFIG_CPU_FREQ_DEBUG is not set
CONFIG_CPU_FREQ_STAT=y
CONFIG_CPU_FREQ_STAT_DETAILS=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=y
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
#
# CPUFreq processor drivers
#
CONFIG_X86_ACPI_CPUFREQ=y
CONFIG_X86_POWERNOW_K8=y
# CONFIG_X86_SPEEDSTEP_CENTRINO is not set
CONFIG_X86_P4_CLOCKMOD=m
#
# shared options
#
CONFIG_X86_SPEEDSTEP_LIB=m
CONFIG_CPU_IDLE=y
CONFIG_CPU_IDLE_GOV_LADDER=y
CONFIG_CPU_IDLE_GOV_MENU=y
#
# Memory power savings
#
CONFIG_I7300_IDLE_IOAT_CHANNEL=y
CONFIG_I7300_IDLE=m
#
# Bus options (PCI etc.)
#
CONFIG_PCI=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCI_DOMAINS=y
# CONFIG_DMAR is not set
# CONFIG_INTR_REMAP is not set
CONFIG_PCIEPORTBUS=y
CONFIG_HOTPLUG_PCI_PCIE=y
CONFIG_PCIEAER=y
# CONFIG_PCIE_ECRC is not set
# CONFIG_PCIEAER_INJECT is not set
# CONFIG_PCIEASPM is not set
CONFIG_ARCH_SUPPORTS_MSI=y
CONFIG_PCI_MSI=y
# CONFIG_PCI_LEGACY is not set
CONFIG_PCI_DEBUG=y
CONFIG_PCI_STUB=m
CONFIG_HT_IRQ=y
CONFIG_PCI_IOV=y
CONFIG_PCI_IOAPIC=y
CONFIG_ISA_DMA_API=y
CONFIG_K8_NB=y
# CONFIG_PCCARD is not set
CONFIG_HOTPLUG_PCI=y
CONFIG_HOTPLUG_PCI_FAKE=m
CONFIG_HOTPLUG_PCI_ACPI=m
CONFIG_HOTPLUG_PCI_ACPI_IBM=m
CONFIG_HOTPLUG_PCI_CPCI=y
CONFIG_HOTPLUG_PCI_CPCI_ZT5550=m
CONFIG_HOTPLUG_PCI_CPCI_GENERIC=m
CONFIG_HOTPLUG_PCI_SHPC=m
#
# Executable file formats / Emulations
#
CONFIG_BINFMT_ELF=y
CONFIG_COMPAT_BINFMT_ELF=y
CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=y
# CONFIG_HAVE_AOUT is not set
# CONFIG_BINFMT_MISC is not set
CONFIG_IA32_EMULATION=y
# CONFIG_IA32_AOUT is not set
CONFIG_COMPAT=y
CONFIG_COMPAT_FOR_U64_ALIGNMENT=y
CONFIG_SYSVIPC_COMPAT=y
CONFIG_NET=y
CONFIG_COMPAT_NETLINK_MESSAGES=y
#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=y
CONFIG_XFRM=y
CONFIG_XFRM_USER=m
# CONFIG_XFRM_SUB_POLICY is not set
# CONFIG_XFRM_MIGRATE is not set
# CONFIG_XFRM_STATISTICS is not set
CONFIG_XFRM_IPCOMP=m
CONFIG_NET_KEY=m
# CONFIG_NET_KEY_MIGRATE is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_ASK_IP_FIB_HASH=y
# CONFIG_IP_FIB_TRIE is not set
CONFIG_IP_FIB_HASH=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_VERBOSE=y
# CONFIG_IP_PNP is not set
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE=m
CONFIG_NET_IPGRE_BROADCAST=y
CONFIG_IP_MROUTE=y
CONFIG_IP_PIMSM_V1=y
CONFIG_IP_PIMSM_V2=y
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
CONFIG_INET_AH=m
CONFIG_INET_ESP=m
CONFIG_INET_IPCOMP=m
CONFIG_INET_XFRM_TUNNEL=m
CONFIG_INET_TUNNEL=m
CONFIG_INET_XFRM_MODE_TRANSPORT=m
CONFIG_INET_XFRM_MODE_TUNNEL=m
CONFIG_INET_XFRM_MODE_BEET=m
CONFIG_INET_LRO=y
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
CONFIG_TCP_CONG_ADVANCED=y
CONFIG_TCP_CONG_BIC=m
CONFIG_TCP_CONG_CUBIC=y
CONFIG_TCP_CONG_WESTWOOD=m
CONFIG_TCP_CONG_HTCP=m
CONFIG_TCP_CONG_HSTCP=m
CONFIG_TCP_CONG_HYBLA=m
CONFIG_TCP_CONG_VEGAS=m
CONFIG_TCP_CONG_SCALABLE=m
CONFIG_TCP_CONG_LP=m
CONFIG_TCP_CONG_VENO=m
CONFIG_TCP_CONG_YEAH=m
CONFIG_TCP_CONG_ILLINOIS=m
# CONFIG_DEFAULT_BIC is not set
CONFIG_DEFAULT_CUBIC=y
# CONFIG_DEFAULT_HTCP is not set
# CONFIG_DEFAULT_VEGAS is not set
# CONFIG_DEFAULT_WESTWOOD is not set
# CONFIG_DEFAULT_RENO is not set
CONFIG_DEFAULT_TCP_CONG="cubic"
CONFIG_TCP_MD5SIG=y
CONFIG_IPV6=y
CONFIG_IPV6_PRIVACY=y
# CONFIG_IPV6_ROUTER_PREF is not set
# CONFIG_IPV6_OPTIMISTIC_DAD is not set
CONFIG_INET6_AH=m
CONFIG_INET6_ESP=m
CONFIG_INET6_IPCOMP=m
# CONFIG_IPV6_MIP6 is not set
CONFIG_INET6_XFRM_TUNNEL=m
CONFIG_INET6_TUNNEL=m
CONFIG_INET6_XFRM_MODE_TRANSPORT=m
CONFIG_INET6_XFRM_MODE_TUNNEL=m
CONFIG_INET6_XFRM_MODE_BEET=m
CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION=m
CONFIG_IPV6_SIT=m
# CONFIG_IPV6_SIT_6RD is not set
CONFIG_IPV6_NDISC_NODETYPE=y
CONFIG_IPV6_TUNNEL=m
CONFIG_IPV6_MULTIPLE_TABLES=y
# CONFIG_IPV6_SUBTREES is not set
# CONFIG_IPV6_MROUTE is not set
CONFIG_NETLABEL=y
CONFIG_NETWORK_SECMARK=y
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_NETFILTER_ADVANCED=y
CONFIG_BRIDGE_NETFILTER=y
#
# Core Netfilter Configuration
#
CONFIG_NETFILTER_NETLINK=m
CONFIG_NETFILTER_NETLINK_QUEUE=m
CONFIG_NETFILTER_NETLINK_LOG=m
CONFIG_NF_CONNTRACK=m
CONFIG_NF_CT_ACCT=y
CONFIG_NF_CONNTRACK_MARK=y
CONFIG_NF_CONNTRACK_SECMARK=y
CONFIG_NF_CONNTRACK_EVENTS=y
CONFIG_NF_CT_PROTO_DCCP=m
CONFIG_NF_CT_PROTO_GRE=m
CONFIG_NF_CT_PROTO_SCTP=m
CONFIG_NF_CT_PROTO_UDPLITE=m
CONFIG_NF_CONNTRACK_AMANDA=m
CONFIG_NF_CONNTRACK_FTP=m
CONFIG_NF_CONNTRACK_H323=m
CONFIG_NF_CONNTRACK_IRC=m
CONFIG_NF_CONNTRACK_NETBIOS_NS=m
CONFIG_NF_CONNTRACK_PPTP=m
CONFIG_NF_CONNTRACK_SANE=m
CONFIG_NF_CONNTRACK_SIP=m
CONFIG_NF_CONNTRACK_TFTP=m
CONFIG_NF_CT_NETLINK=m
CONFIG_NETFILTER_TPROXY=m
CONFIG_NETFILTER_XTABLES=m
CONFIG_NETFILTER_XT_TARGET_CLASSIFY=m
CONFIG_NETFILTER_XT_TARGET_CONNMARK=m
CONFIG_NETFILTER_XT_TARGET_CONNSECMARK=m
CONFIG_NETFILTER_XT_TARGET_DSCP=m
CONFIG_NETFILTER_XT_TARGET_HL=m
CONFIG_NETFILTER_XT_TARGET_LED=m
CONFIG_NETFILTER_XT_TARGET_MARK=m
CONFIG_NETFILTER_XT_TARGET_NFLOG=m
CONFIG_NETFILTER_XT_TARGET_NFQUEUE=m
CONFIG_NETFILTER_XT_TARGET_NOTRACK=m
CONFIG_NETFILTER_XT_TARGET_RATEEST=m
CONFIG_NETFILTER_XT_TARGET_TPROXY=m
CONFIG_NETFILTER_XT_TARGET_TRACE=m
CONFIG_NETFILTER_XT_TARGET_SECMARK=m
CONFIG_NETFILTER_XT_TARGET_TCPMSS=m
# CONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP is not set
CONFIG_NETFILTER_XT_MATCH_CLUSTER=m
CONFIG_NETFILTER_XT_MATCH_COMMENT=m
CONFIG_NETFILTER_XT_MATCH_CONNBYTES=m
CONFIG_NETFILTER_XT_MATCH_CONNLIMIT=m
CONFIG_NETFILTER_XT_MATCH_CONNMARK=m
CONFIG_NETFILTER_XT_MATCH_CONNTRACK=m
CONFIG_NETFILTER_XT_MATCH_DCCP=m
CONFIG_NETFILTER_XT_MATCH_DSCP=m
CONFIG_NETFILTER_XT_MATCH_ESP=m
CONFIG_NETFILTER_XT_MATCH_HASHLIMIT=m
CONFIG_NETFILTER_XT_MATCH_HELPER=m
CONFIG_NETFILTER_XT_MATCH_HL=m
CONFIG_NETFILTER_XT_MATCH_IPRANGE=m
CONFIG_NETFILTER_XT_MATCH_LENGTH=m
CONFIG_NETFILTER_XT_MATCH_LIMIT=m
CONFIG_NETFILTER_XT_MATCH_MAC=m
CONFIG_NETFILTER_XT_MATCH_MARK=m
CONFIG_NETFILTER_XT_MATCH_MULTIPORT=m
CONFIG_NETFILTER_XT_MATCH_OWNER=m
CONFIG_NETFILTER_XT_MATCH_POLICY=m
CONFIG_NETFILTER_XT_MATCH_PHYSDEV=m
CONFIG_NETFILTER_XT_MATCH_PKTTYPE=m
CONFIG_NETFILTER_XT_MATCH_QUOTA=m
CONFIG_NETFILTER_XT_MATCH_RATEEST=m
CONFIG_NETFILTER_XT_MATCH_REALM=m
CONFIG_NETFILTER_XT_MATCH_RECENT=m
# CONFIG_NETFILTER_XT_MATCH_RECENT_PROC_COMPAT is not set
CONFIG_NETFILTER_XT_MATCH_SCTP=m
CONFIG_NETFILTER_XT_MATCH_SOCKET=m
CONFIG_NETFILTER_XT_MATCH_STATE=m
CONFIG_NETFILTER_XT_MATCH_STATISTIC=m
CONFIG_NETFILTER_XT_MATCH_STRING=m
CONFIG_NETFILTER_XT_MATCH_TCPMSS=m
CONFIG_NETFILTER_XT_MATCH_TIME=m
CONFIG_NETFILTER_XT_MATCH_U32=m
CONFIG_NETFILTER_XT_MATCH_OSF=m
CONFIG_IP_VS=m
CONFIG_IP_VS_IPV6=y
# CONFIG_IP_VS_DEBUG is not set
CONFIG_IP_VS_TAB_BITS=12
#
# IPVS transport protocol load balancing support
#
CONFIG_IP_VS_PROTO_TCP=y
CONFIG_IP_VS_PROTO_UDP=y
CONFIG_IP_VS_PROTO_AH_ESP=y
CONFIG_IP_VS_PROTO_ESP=y
CONFIG_IP_VS_PROTO_AH=y
#
# IPVS scheduler
#
CONFIG_IP_VS_RR=m
CONFIG_IP_VS_WRR=m
CONFIG_IP_VS_LC=m
CONFIG_IP_VS_WLC=m
CONFIG_IP_VS_LBLC=m
CONFIG_IP_VS_LBLCR=m
CONFIG_IP_VS_DH=m
CONFIG_IP_VS_SH=m
CONFIG_IP_VS_SED=m
CONFIG_IP_VS_NQ=m
#
# IPVS application helper
#
CONFIG_IP_VS_FTP=m
#
# IP: Netfilter Configuration
#
CONFIG_NF_DEFRAG_IPV4=m
CONFIG_NF_CONNTRACK_IPV4=m
CONFIG_NF_CONNTRACK_PROC_COMPAT=y
CONFIG_IP_NF_QUEUE=m
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_ADDRTYPE=m
CONFIG_IP_NF_MATCH_AH=m
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
CONFIG_NF_NAT=m
CONFIG_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_NETMAP=m
CONFIG_IP_NF_TARGET_REDIRECT=m
CONFIG_NF_NAT_SNMP_BASIC=m
CONFIG_NF_NAT_PROTO_DCCP=m
CONFIG_NF_NAT_PROTO_GRE=m
CONFIG_NF_NAT_PROTO_UDPLITE=m
CONFIG_NF_NAT_PROTO_SCTP=m
CONFIG_NF_NAT_FTP=m
CONFIG_NF_NAT_IRC=m
CONFIG_NF_NAT_TFTP=m
CONFIG_NF_NAT_AMANDA=m
CONFIG_NF_NAT_PPTP=m
CONFIG_NF_NAT_H323=m
CONFIG_NF_NAT_SIP=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_CLUSTERIP=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_TTL=m
CONFIG_IP_NF_RAW=m
CONFIG_IP_NF_SECURITY=m
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
CONFIG_IP_NF_ARP_MANGLE=m
#
# IPv6: Netfilter Configuration
#
CONFIG_NF_CONNTRACK_IPV6=m
CONFIG_IP6_NF_QUEUE=m
CONFIG_IP6_NF_IPTABLES=m
CONFIG_IP6_NF_MATCH_AH=m
CONFIG_IP6_NF_MATCH_EUI64=m
CONFIG_IP6_NF_MATCH_FRAG=m
CONFIG_IP6_NF_MATCH_OPTS=m
CONFIG_IP6_NF_MATCH_HL=m
CONFIG_IP6_NF_MATCH_IPV6HEADER=m
CONFIG_IP6_NF_MATCH_MH=m
CONFIG_IP6_NF_MATCH_RT=m
CONFIG_IP6_NF_TARGET_HL=m
CONFIG_IP6_NF_TARGET_LOG=m
CONFIG_IP6_NF_FILTER=m
CONFIG_IP6_NF_TARGET_REJECT=m
CONFIG_IP6_NF_MANGLE=m
CONFIG_IP6_NF_RAW=m
CONFIG_IP6_NF_SECURITY=m
#
# DECnet: Netfilter Configuration
#
CONFIG_DECNET_NF_GRABULATOR=m
CONFIG_BRIDGE_NF_EBTABLES=m
CONFIG_BRIDGE_EBT_BROUTE=m
CONFIG_BRIDGE_EBT_T_FILTER=m
CONFIG_BRIDGE_EBT_T_NAT=m
CONFIG_BRIDGE_EBT_802_3=m
CONFIG_BRIDGE_EBT_AMONG=m
CONFIG_BRIDGE_EBT_ARP=m
CONFIG_BRIDGE_EBT_IP=m
CONFIG_BRIDGE_EBT_IP6=m
CONFIG_BRIDGE_EBT_LIMIT=m
CONFIG_BRIDGE_EBT_MARK=m
CONFIG_BRIDGE_EBT_PKTTYPE=m
CONFIG_BRIDGE_EBT_STP=m
CONFIG_BRIDGE_EBT_VLAN=m
CONFIG_BRIDGE_EBT_ARPREPLY=m
CONFIG_BRIDGE_EBT_DNAT=m
CONFIG_BRIDGE_EBT_MARK_T=m
CONFIG_BRIDGE_EBT_REDIRECT=m
CONFIG_BRIDGE_EBT_SNAT=m
CONFIG_BRIDGE_EBT_LOG=m
CONFIG_BRIDGE_EBT_ULOG=m
CONFIG_BRIDGE_EBT_NFLOG=m
CONFIG_IP_DCCP=m
CONFIG_INET_DCCP_DIAG=m
#
# DCCP CCIDs Configuration (EXPERIMENTAL)
#
# CONFIG_IP_DCCP_CCID2_DEBUG is not set
CONFIG_IP_DCCP_CCID3=y
# CONFIG_IP_DCCP_CCID3_DEBUG is not set
CONFIG_IP_DCCP_CCID3_RTO=100
CONFIG_IP_DCCP_TFRC_LIB=y
#
# DCCP Kernel Hacking
#
# CONFIG_IP_DCCP_DEBUG is not set
CONFIG_IP_SCTP=m
# CONFIG_SCTP_DBG_MSG is not set
# CONFIG_SCTP_DBG_OBJCNT is not set
# CONFIG_SCTP_HMAC_NONE is not set
# CONFIG_SCTP_HMAC_SHA1 is not set
CONFIG_SCTP_HMAC_MD5=y
CONFIG_RDS=m
CONFIG_RDS_TCP=m
# CONFIG_RDS_DEBUG is not set
CONFIG_TIPC=m
# CONFIG_TIPC_ADVANCED is not set
# CONFIG_TIPC_DEBUG is not set
CONFIG_ATM=m
CONFIG_ATM_CLIP=m
# CONFIG_ATM_CLIP_NO_ICMP is not set
CONFIG_ATM_LANE=m
CONFIG_ATM_MPOA=m
CONFIG_ATM_BR2684=m
# CONFIG_ATM_BR2684_IPFILTER is not set
CONFIG_STP=m
CONFIG_GARP=m
CONFIG_BRIDGE=m
CONFIG_NET_DSA=y
CONFIG_NET_DSA_TAG_DSA=y
CONFIG_NET_DSA_TAG_EDSA=y
CONFIG_NET_DSA_TAG_TRAILER=y
CONFIG_NET_DSA_MV88E6XXX=y
CONFIG_NET_DSA_MV88E6060=y
CONFIG_NET_DSA_MV88E6XXX_NEED_PPU=y
CONFIG_NET_DSA_MV88E6131=y
CONFIG_NET_DSA_MV88E6123_61_65=y
CONFIG_VLAN_8021Q=m
CONFIG_VLAN_8021Q_GVRP=y
CONFIG_DECNET=m
# CONFIG_DECNET_ROUTER is not set
CONFIG_LLC=y
CONFIG_LLC2=m
CONFIG_IPX=m
# CONFIG_IPX_INTERN is not set
CONFIG_ATALK=m
CONFIG_DEV_APPLETALK=m
CONFIG_IPDDP=m
CONFIG_IPDDP_ENCAP=y
CONFIG_IPDDP_DECAP=y
CONFIG_X25=m
CONFIG_LAPB=m
CONFIG_ECONET=m
CONFIG_ECONET_AUNUDP=y
CONFIG_ECONET_NATIVE=y
CONFIG_WAN_ROUTER=m
CONFIG_PHONET=m
CONFIG_IEEE802154=m
CONFIG_NET_SCHED=y
#
# Queueing/Scheduling
#
CONFIG_NET_SCH_CBQ=m
CONFIG_NET_SCH_HTB=m
CONFIG_NET_SCH_HFSC=m
CONFIG_NET_SCH_ATM=m
CONFIG_NET_SCH_PRIO=m
CONFIG_NET_SCH_MULTIQ=m
CONFIG_NET_SCH_RED=m
CONFIG_NET_SCH_SFQ=m
CONFIG_NET_SCH_TEQL=m
CONFIG_NET_SCH_TBF=m
CONFIG_NET_SCH_GRED=m
CONFIG_NET_SCH_DSMARK=m
CONFIG_NET_SCH_NETEM=m
CONFIG_NET_SCH_DRR=m
CONFIG_NET_SCH_INGRESS=m
#
# Classification
#
CONFIG_NET_CLS=y
CONFIG_NET_CLS_BASIC=m
CONFIG_NET_CLS_TCINDEX=m
CONFIG_NET_CLS_ROUTE4=m
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=m
CONFIG_NET_CLS_U32=m
# CONFIG_CLS_U32_PERF is not set
CONFIG_CLS_U32_MARK=y
CONFIG_NET_CLS_RSVP=m
CONFIG_NET_CLS_RSVP6=m
CONFIG_NET_CLS_FLOW=m
CONFIG_NET_EMATCH=y
CONFIG_NET_EMATCH_STACK=32
CONFIG_NET_EMATCH_CMP=m
CONFIG_NET_EMATCH_NBYTE=m
CONFIG_NET_EMATCH_U32=m
CONFIG_NET_EMATCH_META=m
CONFIG_NET_EMATCH_TEXT=m
CONFIG_NET_CLS_ACT=y
CONFIG_NET_ACT_POLICE=m
CONFIG_NET_ACT_GACT=m
CONFIG_GACT_PROB=y
CONFIG_NET_ACT_MIRRED=m
CONFIG_NET_ACT_IPT=m
CONFIG_NET_ACT_NAT=m
CONFIG_NET_ACT_PEDIT=m
CONFIG_NET_ACT_SIMP=m
CONFIG_NET_ACT_SKBEDIT=m
# CONFIG_NET_CLS_IND is not set
CONFIG_NET_SCH_FIFO=y
CONFIG_DCB=y
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_NET_DROP_MONITOR is not set
# CONFIG_HAMRADIO is not set
CONFIG_CAN=m
CONFIG_CAN_RAW=m
CONFIG_CAN_BCM=m
#
# CAN Device Drivers
#
CONFIG_CAN_VCAN=m
CONFIG_CAN_DEV=m
# CONFIG_CAN_CALC_BITTIMING is not set
# CONFIG_CAN_MCP251X is not set
CONFIG_CAN_SJA1000=m
CONFIG_CAN_SJA1000_PLATFORM=m
CONFIG_CAN_EMS_PCI=m
CONFIG_CAN_KVASER_PCI=m
# CONFIG_CAN_DEBUG_DEVICES is not set
CONFIG_IRDA=m
#
# IrDA protocols
#
CONFIG_IRLAN=m
CONFIG_IRNET=m
CONFIG_IRCOMM=m
CONFIG_IRDA_ULTRA=y
#
# IrDA options
#
CONFIG_IRDA_CACHE_LAST_LSAP=y
CONFIG_IRDA_FAST_RR=y
CONFIG_IRDA_DEBUG=y
#
# Infrared-port device drivers
#
#
# SIR device drivers
#
CONFIG_IRTTY_SIR=m
#
# Dongle support
#
CONFIG_DONGLE=y
CONFIG_ESI_DONGLE=m
CONFIG_ACTISYS_DONGLE=m
CONFIG_TEKRAM_DONGLE=m
CONFIG_TOIM3232_DONGLE=m
CONFIG_LITELINK_DONGLE=m
CONFIG_MA600_DONGLE=m
CONFIG_GIRBIL_DONGLE=m
CONFIG_MCP2120_DONGLE=m
CONFIG_OLD_BELKIN_DONGLE=m
CONFIG_ACT200L_DONGLE=m
#
# FIR device drivers
#
CONFIG_NSC_FIR=m
CONFIG_WINBOND_FIR=m
CONFIG_SMC_IRCC_FIR=m
CONFIG_ALI_FIR=m
CONFIG_VLSI_FIR=m
CONFIG_VIA_FIR=m
CONFIG_BT=y
CONFIG_BT_L2CAP=y
CONFIG_BT_SCO=y
CONFIG_BT_RFCOMM=y
CONFIG_BT_RFCOMM_TTY=y
CONFIG_BT_BNEP=m
CONFIG_BT_BNEP_MC_FILTER=y
CONFIG_BT_BNEP_PROTO_FILTER=y
CONFIG_BT_CMTP=m
CONFIG_BT_HIDP=m
#
# Bluetooth device drivers
#
CONFIG_BT_HCIUART=m
CONFIG_BT_HCIUART_H4=y
CONFIG_BT_HCIUART_BCSP=y
CONFIG_BT_HCIUART_LL=y
CONFIG_BT_HCIVHCI=m
CONFIG_BT_MRVL=m
CONFIG_AF_RXRPC=m
# CONFIG_AF_RXRPC_DEBUG is not set
CONFIG_RXKAD=m
CONFIG_FIB_RULES=y
CONFIG_WIRELESS=y
CONFIG_WIRELESS_EXT=y
CONFIG_WEXT_CORE=y
CONFIG_WEXT_PROC=y
CONFIG_WEXT_SPY=y
CONFIG_WEXT_PRIV=y
# CONFIG_CFG80211 is not set
# CONFIG_WIRELESS_EXT_SYSFS is not set
CONFIG_LIB80211=m
CONFIG_LIB80211_CRYPT_WEP=m
CONFIG_LIB80211_CRYPT_CCMP=m
CONFIG_LIB80211_CRYPT_TKIP=m
# CONFIG_LIB80211_DEBUG is not set
#
# CFG80211 needs to be enabled for MAC80211
#
# CONFIG_WIMAX is not set
# CONFIG_RFKILL is not set
# CONFIG_NET_9P is not set
#
# Device Drivers
#
#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH=""
# CONFIG_DEVTMPFS is not set
# CONFIG_STANDALONE is not set
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE=""
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_SYS_HYPERVISOR is not set
CONFIG_CONNECTOR=y
CONFIG_PROC_EVENTS=y
CONFIG_MTD=m
# CONFIG_MTD_DEBUG is not set
CONFIG_MTD_TESTS=m
CONFIG_MTD_CONCAT=m
CONFIG_MTD_PARTITIONS=y
CONFIG_MTD_REDBOOT_PARTS=m
CONFIG_MTD_REDBOOT_DIRECTORY_BLOCK=-1
# CONFIG_MTD_REDBOOT_PARTS_UNALLOCATED is not set
# CONFIG_MTD_REDBOOT_PARTS_READONLY is not set
CONFIG_MTD_AR7_PARTS=m
#
# User Modules And Translation Layers
#
CONFIG_MTD_CHAR=m
CONFIG_HAVE_MTD_OTP=y
CONFIG_MTD_BLKDEVS=m
CONFIG_MTD_BLOCK=m
CONFIG_MTD_BLOCK_RO=m
CONFIG_FTL=m
CONFIG_NFTL=m
CONFIG_NFTL_RW=y
CONFIG_INFTL=m
CONFIG_RFD_FTL=m
CONFIG_SSFDC=m
CONFIG_MTD_OOPS=m
#
# RAM/ROM/Flash chip drivers
#
CONFIG_MTD_CFI=m
CONFIG_MTD_JEDECPROBE=m
CONFIG_MTD_GEN_PROBE=m
# CONFIG_MTD_CFI_ADV_OPTIONS is not set
CONFIG_MTD_MAP_BANK_WIDTH_1=y
CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_MAP_BANK_WIDTH_4=y
# CONFIG_MTD_MAP_BANK_WIDTH_8 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_16 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_32 is not set
CONFIG_MTD_CFI_I1=y
CONFIG_MTD_CFI_I2=y
# CONFIG_MTD_CFI_I4 is not set
# CONFIG_MTD_CFI_I8 is not set
CONFIG_MTD_CFI_INTELEXT=m
CONFIG_MTD_CFI_AMDSTD=m
CONFIG_MTD_CFI_STAA=m
CONFIG_MTD_CFI_UTIL=m
CONFIG_MTD_RAM=m
CONFIG_MTD_ROM=m
CONFIG_MTD_ABSENT=m
#
# Mapping drivers for chip access
#
CONFIG_MTD_COMPLEX_MAPPINGS=y
CONFIG_MTD_PHYSMAP=m
# CONFIG_MTD_PHYSMAP_COMPAT is not set
CONFIG_MTD_SC520CDP=m
CONFIG_MTD_NETSC520=m
CONFIG_MTD_TS5500=m
CONFIG_MTD_SBC_GXX=m
CONFIG_MTD_AMD76XROM=m
CONFIG_MTD_ICHXROM=m
CONFIG_MTD_ESB2ROM=m
CONFIG_MTD_CK804XROM=m
CONFIG_MTD_SCB2_FLASH=m
CONFIG_MTD_NETtel=m
CONFIG_MTD_L440GX=m
CONFIG_MTD_PCI=m
CONFIG_MTD_GPIO_ADDR=m
CONFIG_MTD_INTEL_VR_NOR=m
CONFIG_MTD_PLATRAM=m
#
# Self-contained MTD device drivers
#
CONFIG_MTD_PMC551=m
# CONFIG_MTD_PMC551_BUGFIX is not set
# CONFIG_MTD_PMC551_DEBUG is not set
CONFIG_MTD_DATAFLASH=m
# CONFIG_MTD_DATAFLASH_WRITE_VERIFY is not set
CONFIG_MTD_DATAFLASH_OTP=y
CONFIG_MTD_M25P80=m
CONFIG_M25PXX_USE_FAST_READ=y
CONFIG_MTD_SST25L=m
CONFIG_MTD_SLRAM=m
CONFIG_MTD_PHRAM=m
CONFIG_MTD_MTDRAM=m
CONFIG_MTDRAM_TOTAL_SIZE=4096
CONFIG_MTDRAM_ERASE_SIZE=128
CONFIG_MTD_BLOCK2MTD=m
#
# Disk-On-Chip Device Drivers
#
CONFIG_MTD_DOC2000=m
CONFIG_MTD_DOC2001=m
CONFIG_MTD_DOC2001PLUS=m
CONFIG_MTD_DOCPROBE=m
CONFIG_MTD_DOCECC=m
# CONFIG_MTD_DOCPROBE_ADVANCED is not set
CONFIG_MTD_DOCPROBE_ADDRESS=0
CONFIG_MTD_NAND=m
# CONFIG_MTD_NAND_VERIFY_WRITE is not set
# CONFIG_MTD_NAND_ECC_SMC is not set
# CONFIG_MTD_NAND_MUSEUM_IDS is not set
CONFIG_MTD_NAND_IDS=m
CONFIG_MTD_NAND_DISKONCHIP=m
# CONFIG_MTD_NAND_DISKONCHIP_PROBE_ADVANCED is not set
CONFIG_MTD_NAND_DISKONCHIP_PROBE_ADDRESS=0
# CONFIG_MTD_NAND_DISKONCHIP_BBTWRITE is not set
CONFIG_MTD_NAND_CAFE=m
CONFIG_MTD_NAND_NANDSIM=m
CONFIG_MTD_NAND_PLATFORM=m
CONFIG_MTD_ONENAND=m
CONFIG_MTD_ONENAND_VERIFY_WRITE=y
CONFIG_MTD_ONENAND_GENERIC=m
# CONFIG_MTD_ONENAND_OTP is not set
CONFIG_MTD_ONENAND_2X_PROGRAM=y
CONFIG_MTD_ONENAND_SIM=m
#
# LPDDR flash memory drivers
#
CONFIG_MTD_LPDDR=m
CONFIG_MTD_QINFO_PROBE=m
#
# UBI - Unsorted block images
#
CONFIG_MTD_UBI=m
CONFIG_MTD_UBI_WL_THRESHOLD=4096
CONFIG_MTD_UBI_BEB_RESERVE=1
CONFIG_MTD_UBI_GLUEBI=m
#
# UBI debugging options
#
# CONFIG_MTD_UBI_DEBUG is not set
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_SERIAL=m
CONFIG_PARPORT_PC_FIFO=y
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_GSC is not set
CONFIG_PARPORT_AX88796=m
CONFIG_PARPORT_1284=y
CONFIG_PARPORT_NOT_PC=y
CONFIG_PNP=y
CONFIG_PNP_DEBUG_MESSAGES=y
#
# Protocols
#
CONFIG_PNPACPI=y
CONFIG_BLK_DEV=y
CONFIG_BLK_DEV_FD=m
CONFIG_PARIDE=m
#
# Parallel IDE high-level drivers
#
CONFIG_PARIDE_PD=m
CONFIG_PARIDE_PCD=m
CONFIG_PARIDE_PF=m
CONFIG_PARIDE_PT=m
CONFIG_PARIDE_PG=m
#
# Parallel IDE protocol modules
#
CONFIG_PARIDE_ATEN=m
CONFIG_PARIDE_BPCK=m
CONFIG_PARIDE_COMM=m
CONFIG_PARIDE_DSTR=m
CONFIG_PARIDE_FIT2=m
CONFIG_PARIDE_FIT3=m
CONFIG_PARIDE_EPAT=m
# CONFIG_PARIDE_EPATC8 is not set
CONFIG_PARIDE_EPIA=m
CONFIG_PARIDE_FRIQ=m
CONFIG_PARIDE_FRPW=m
CONFIG_PARIDE_KBIC=m
CONFIG_PARIDE_KTTI=m
CONFIG_PARIDE_ON20=m
CONFIG_PARIDE_ON26=m
CONFIG_BLK_CPQ_DA=m
CONFIG_BLK_CPQ_CISS_DA=m
CONFIG_CISS_SCSI_TAPE=y
CONFIG_BLK_DEV_DAC960=m
CONFIG_BLK_DEV_UMEM=m
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_CRYPTOLOOP=m
# CONFIG_BLK_DEV_DRBD is not set
CONFIG_BLK_DEV_NBD=m
CONFIG_BLK_DEV_OSD=m
CONFIG_BLK_DEV_SX8=m
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=65536
# CONFIG_BLK_DEV_XIP is not set
CONFIG_CDROM_PKTCDVD=y
CONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not set
CONFIG_ATA_OVER_ETH=m
# CONFIG_BLK_DEV_HD is not set
CONFIG_MISC_DEVICES=y
# CONFIG_AD525X_DPOT is not set
CONFIG_IBM_ASM=m
CONFIG_PHANTOM=m
CONFIG_SGI_IOC4=m
CONFIG_TIFM_CORE=m
CONFIG_TIFM_7XX1=m
CONFIG_ICS932S401=m
CONFIG_ENCLOSURE_SERVICES=m
# CONFIG_CS5535_MFGPT is not set
CONFIG_HP_ILO=m
CONFIG_ISL29003=m
CONFIG_DS1682=m
# CONFIG_TI_DAC7512 is not set
CONFIG_C2PORT=m
CONFIG_C2PORT_DURAMAR_2150=m
#
# EEPROM support
#
CONFIG_EEPROM_AT24=m
CONFIG_EEPROM_AT25=m
CONFIG_EEPROM_LEGACY=m
CONFIG_EEPROM_MAX6875=m
CONFIG_EEPROM_93CX6=m
CONFIG_CB710_CORE=m
# CONFIG_CB710_DEBUG is not set
CONFIG_CB710_DEBUG_ASSUMPTIONS=y
CONFIG_HAVE_IDE=y
# CONFIG_IDE is not set
#
# SCSI device support
#
CONFIG_RAID_ATTRS=m
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
CONFIG_SCSI_TGT=m
CONFIG_SCSI_NETLINK=y
CONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
CONFIG_CHR_DEV_ST=m
CONFIG_CHR_DEV_OSST=m
CONFIG_BLK_DEV_SR=y
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_CHR_DEV_SG=y
CONFIG_CHR_DEV_SCH=m
CONFIG_SCSI_ENCLOSURE=m
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y
CONFIG_SCSI_SCAN_ASYNC=y
CONFIG_SCSI_WAIT_SCAN=m
#
# SCSI Transports
#
CONFIG_SCSI_SPI_ATTRS=m
CONFIG_SCSI_FC_ATTRS=m
CONFIG_SCSI_FC_TGT_ATTRS=y
CONFIG_SCSI_ISCSI_ATTRS=m
CONFIG_SCSI_SAS_ATTRS=m
CONFIG_SCSI_SAS_LIBSAS=m
CONFIG_SCSI_SAS_ATA=y
CONFIG_SCSI_SAS_HOST_SMP=y
# CONFIG_SCSI_SAS_LIBSAS_DEBUG is not set
CONFIG_SCSI_SRP_ATTRS=m
CONFIG_SCSI_SRP_TGT_ATTRS=y
CONFIG_SCSI_LOWLEVEL=y
CONFIG_ISCSI_TCP=m
CONFIG_SCSI_CXGB3_ISCSI=m
CONFIG_SCSI_BNX2_ISCSI=m
CONFIG_BE2ISCSI=m
CONFIG_BLK_DEV_3W_XXXX_RAID=m
# CONFIG_SCSI_HPSA is not set
CONFIG_SCSI_3W_9XXX=m
# CONFIG_SCSI_3W_SAS is not set
CONFIG_SCSI_ACARD=m
CONFIG_SCSI_AACRAID=m
CONFIG_SCSI_AIC7XXX=m
CONFIG_AIC7XXX_CMDS_PER_DEVICE=8
CONFIG_AIC7XXX_RESET_DELAY_MS=15000
CONFIG_AIC7XXX_DEBUG_ENABLE=y
CONFIG_AIC7XXX_DEBUG_MASK=0
CONFIG_AIC7XXX_REG_PRETTY_PRINT=y
# CONFIG_SCSI_AIC7XXX_OLD is not set
CONFIG_SCSI_AIC79XX=m
CONFIG_AIC79XX_CMDS_PER_DEVICE=32
CONFIG_AIC79XX_RESET_DELAY_MS=5000
CONFIG_AIC79XX_DEBUG_ENABLE=y
CONFIG_AIC79XX_DEBUG_MASK=0
CONFIG_AIC79XX_REG_PRETTY_PRINT=y
CONFIG_SCSI_AIC94XX=m
# CONFIG_AIC94XX_DEBUG is not set
CONFIG_SCSI_MVSAS=m
CONFIG_SCSI_MVSAS_DEBUG=y
CONFIG_SCSI_DPT_I2O=m
CONFIG_SCSI_ADVANSYS=m
CONFIG_SCSI_ARCMSR=m
CONFIG_SCSI_ARCMSR_AER=y
CONFIG_MEGARAID_NEWGEN=y
CONFIG_MEGARAID_MM=m
CONFIG_MEGARAID_MAILBOX=m
CONFIG_MEGARAID_LEGACY=m
CONFIG_MEGARAID_SAS=m
CONFIG_SCSI_MPT2SAS=m
CONFIG_SCSI_MPT2SAS_MAX_SGE=128
# CONFIG_SCSI_MPT2SAS_LOGGING is not set
CONFIG_SCSI_HPTIOP=m
CONFIG_SCSI_BUSLOGIC=m
# CONFIG_VMWARE_PVSCSI is not set
CONFIG_LIBFC=m
CONFIG_LIBFCOE=m
CONFIG_FCOE=m
CONFIG_FCOE_FNIC=m
CONFIG_SCSI_DMX3191D=m
CONFIG_SCSI_EATA=m
CONFIG_SCSI_EATA_TAGGED_QUEUE=y
CONFIG_SCSI_EATA_LINKED_COMMANDS=y
CONFIG_SCSI_EATA_MAX_TAGS=16
CONFIG_SCSI_FUTURE_DOMAIN=m
CONFIG_SCSI_GDTH=m
CONFIG_SCSI_IPS=m
CONFIG_SCSI_INITIO=m
CONFIG_SCSI_INIA100=m
CONFIG_SCSI_PPA=m
CONFIG_SCSI_IMM=m
# CONFIG_SCSI_IZIP_EPP16 is not set
# CONFIG_SCSI_IZIP_SLOW_CTR is not set
CONFIG_SCSI_STEX=m
CONFIG_SCSI_SYM53C8XX_2=m
CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1
CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16
CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64
CONFIG_SCSI_SYM53C8XX_MMIO=y
CONFIG_SCSI_IPR=m
# CONFIG_SCSI_IPR_TRACE is not set
# CONFIG_SCSI_IPR_DUMP is not set
CONFIG_SCSI_QLOGIC_1280=m
CONFIG_SCSI_QLA_FC=m
CONFIG_SCSI_QLA_ISCSI=m
CONFIG_SCSI_LPFC=m
CONFIG_SCSI_LPFC_DEBUG_FS=y
CONFIG_SCSI_DC395x=m
CONFIG_SCSI_DC390T=m
CONFIG_SCSI_DEBUG=m
CONFIG_SCSI_PMCRAID=m
# CONFIG_SCSI_PM8001 is not set
CONFIG_SCSI_SRP=m
CONFIG_SCSI_BFA_FC=m
CONFIG_SCSI_DH=y
CONFIG_SCSI_DH_RDAC=m
CONFIG_SCSI_DH_HP_SW=m
CONFIG_SCSI_DH_EMC=m
CONFIG_SCSI_DH_ALUA=m
CONFIG_SCSI_OSD_INITIATOR=m
CONFIG_SCSI_OSD_ULD=m
CONFIG_SCSI_OSD_DPRINT_SENSE=1
# CONFIG_SCSI_OSD_DEBUG is not set
CONFIG_ATA=y
# CONFIG_ATA_NONSTANDARD is not set
CONFIG_ATA_VERBOSE_ERROR=y
CONFIG_ATA_ACPI=y
CONFIG_SATA_PMP=y
CONFIG_SATA_AHCI=y
CONFIG_SATA_SIL24=y
CONFIG_ATA_SFF=y
CONFIG_SATA_SVW=y
CONFIG_ATA_PIIX=y
CONFIG_SATA_MV=m
CONFIG_SATA_NV=y
CONFIG_PDC_ADMA=y
CONFIG_SATA_QSTOR=y
CONFIG_SATA_PROMISE=y
CONFIG_SATA_SX4=y
CONFIG_SATA_SIL=y
CONFIG_SATA_SIS=y
CONFIG_SATA_ULI=y
CONFIG_SATA_VIA=m
CONFIG_SATA_VITESSE=y
CONFIG_SATA_INIC162X=y
CONFIG_PATA_ACPI=y
CONFIG_PATA_ALI=y
CONFIG_PATA_AMD=y
CONFIG_PATA_ARTOP=y
CONFIG_PATA_ATP867X=m
CONFIG_PATA_ATIIXP=y
CONFIG_PATA_CMD640_PCI=m
CONFIG_PATA_CMD64X=y
CONFIG_PATA_CS5520=y
CONFIG_PATA_CS5530=y
CONFIG_PATA_CYPRESS=m
CONFIG_PATA_EFAR=y
CONFIG_ATA_GENERIC=y
CONFIG_PATA_HPT366=y
CONFIG_PATA_HPT37X=y
CONFIG_PATA_HPT3X2N=m
CONFIG_PATA_HPT3X3=y
# CONFIG_PATA_HPT3X3_DMA is not set
CONFIG_PATA_IT821X=y
CONFIG_PATA_IT8213=m
CONFIG_PATA_JMICRON=y
CONFIG_PATA_TRIFLEX=y
CONFIG_PATA_MARVELL=y
CONFIG_PATA_MPIIX=y
CONFIG_PATA_OLDPIIX=y
CONFIG_PATA_NETCELL=y
CONFIG_PATA_NINJA32=m
CONFIG_PATA_NS87410=y
CONFIG_PATA_NS87415=y
CONFIG_PATA_OPTI=m
CONFIG_PATA_OPTIDMA=m
CONFIG_PATA_PDC2027X=y
CONFIG_PATA_PDC_OLD=y
CONFIG_PATA_RADISYS=m
CONFIG_PATA_RDC=m
CONFIG_PATA_RZ1000=y
CONFIG_PATA_SC1200=y
CONFIG_PATA_SERVERWORKS=y
CONFIG_PATA_SIL680=y
CONFIG_PATA_SIS=y
# CONFIG_PATA_TOSHIBA is not set
CONFIG_PATA_VIA=y
CONFIG_PATA_WINBOND=y
CONFIG_PATA_SCH=y
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_AUTODETECT=y
CONFIG_MD_LINEAR=m
CONFIG_MD_RAID0=m
CONFIG_MD_RAID1=m
CONFIG_MD_RAID10=m
CONFIG_MD_RAID456=m
# CONFIG_MULTICORE_RAID456 is not set
CONFIG_MD_RAID6_PQ=m
CONFIG_ASYNC_RAID6_TEST=m
CONFIG_MD_MULTIPATH=m
CONFIG_MD_FAULTY=m
CONFIG_BLK_DEV_DM=y
# CONFIG_DM_DEBUG is not set
CONFIG_DM_CRYPT=m
CONFIG_DM_SNAPSHOT=y
CONFIG_DM_MIRROR=y
# CONFIG_DM_LOG_USERSPACE is not set
CONFIG_DM_ZERO=m
CONFIG_DM_MULTIPATH=y
CONFIG_DM_MULTIPATH_QL=m
CONFIG_DM_MULTIPATH_ST=m
# CONFIG_DM_DELAY is not set
CONFIG_DM_UEVENT=y
CONFIG_FUSION=y
CONFIG_FUSION_SPI=m
CONFIG_FUSION_FC=m
CONFIG_FUSION_SAS=m
CONFIG_FUSION_MAX_SGE=128
CONFIG_FUSION_CTL=m
CONFIG_FUSION_LAN=m
CONFIG_FUSION_LOGGING=y
#
# IEEE 1394 (FireWire) support
#
#
# You can enable one or both FireWire driver stacks.
#
#
# The newer stack is recommended.
#
CONFIG_FIREWIRE=m
CONFIG_FIREWIRE_OHCI=m
CONFIG_FIREWIRE_OHCI_DEBUG=y
CONFIG_FIREWIRE_SBP2=m
CONFIG_FIREWIRE_NET=m
CONFIG_IEEE1394=m
CONFIG_IEEE1394_OHCI1394=m
CONFIG_IEEE1394_PCILYNX=m
CONFIG_IEEE1394_SBP2=m
# CONFIG_IEEE1394_SBP2_PHYS_DMA is not set
CONFIG_IEEE1394_ETH1394_ROM_ENTRY=y
CONFIG_IEEE1394_ETH1394=m
CONFIG_IEEE1394_RAWIO=m
CONFIG_IEEE1394_VIDEO1394=m
CONFIG_IEEE1394_DV1394=m
# CONFIG_IEEE1394_VERBOSEDEBUG is not set
CONFIG_I2O=m
CONFIG_I2O_LCT_NOTIFY_ON_CHANGES=y
CONFIG_I2O_EXT_ADAPTEC=y
CONFIG_I2O_EXT_ADAPTEC_DMA64=y
CONFIG_I2O_CONFIG=m
CONFIG_I2O_CONFIG_OLD_IOCTL=y
CONFIG_I2O_BUS=m
CONFIG_I2O_BLOCK=m
CONFIG_I2O_SCSI=m
CONFIG_I2O_PROC=m
CONFIG_MACINTOSH_DRIVERS=y
CONFIG_MAC_EMUMOUSEBTN=y
CONFIG_NETDEVICES=y
CONFIG_IFB=m
CONFIG_DUMMY=m
CONFIG_BONDING=m
CONFIG_MACVLAN=m
CONFIG_EQUALIZER=m
CONFIG_TUN=m
CONFIG_VETH=m
CONFIG_NET_SB1000=m
CONFIG_ARCNET=m
CONFIG_ARCNET_1201=m
CONFIG_ARCNET_1051=m
CONFIG_ARCNET_RAW=m
CONFIG_ARCNET_CAP=m
CONFIG_ARCNET_COM90xx=m
CONFIG_ARCNET_COM90xxIO=m
CONFIG_ARCNET_RIM_I=m
CONFIG_ARCNET_COM20020=m
CONFIG_ARCNET_COM20020_PCI=m
CONFIG_PHYLIB=y
#
# MII PHY device drivers
#
CONFIG_MARVELL_PHY=y
CONFIG_DAVICOM_PHY=y
CONFIG_QSEMI_PHY=y
CONFIG_LXT_PHY=y
CONFIG_CICADA_PHY=y
CONFIG_VITESSE_PHY=y
CONFIG_SMSC_PHY=y
CONFIG_BROADCOM_PHY=y
CONFIG_ICPLUS_PHY=y
CONFIG_REALTEK_PHY=y
CONFIG_NATIONAL_PHY=y
CONFIG_STE10XP=y
CONFIG_LSI_ET1011C_PHY=y
CONFIG_FIXED_PHY=y
CONFIG_MDIO_BITBANG=y
CONFIG_MDIO_GPIO=y
CONFIG_NET_ETHERNET=y
CONFIG_MII=m
CONFIG_HAPPYMEAL=m
CONFIG_SUNGEM=m
CONFIG_CASSINI=m
CONFIG_NET_VENDOR_3COM=y
CONFIG_VORTEX=m
CONFIG_TYPHOON=m
# CONFIG_ENC28J60 is not set
CONFIG_ETHOC=m
CONFIG_DNET=m
CONFIG_NET_TULIP=y
CONFIG_DE2104X=m
CONFIG_DE2104X_DSL=0
CONFIG_TULIP=m
# CONFIG_TULIP_MWI is not set
# CONFIG_TULIP_MMIO is not set
# CONFIG_TULIP_NAPI is not set
CONFIG_DE4X5=m
CONFIG_WINBOND_840=m
CONFIG_DM9102=m
CONFIG_ULI526X=m
CONFIG_HP100=m
# CONFIG_IBM_NEW_EMAC_ZMII is not set
# CONFIG_IBM_NEW_EMAC_RGMII is not set
# CONFIG_IBM_NEW_EMAC_TAH is not set
# CONFIG_IBM_NEW_EMAC_EMAC4 is not set
# CONFIG_IBM_NEW_EMAC_NO_FLOW_CTRL is not set
# CONFIG_IBM_NEW_EMAC_MAL_CLR_ICINTSTAT is not set
# CONFIG_IBM_NEW_EMAC_MAL_COMMON_ERR is not set
CONFIG_NET_PCI=y
CONFIG_PCNET32=m
CONFIG_AMD8111_ETH=m
CONFIG_ADAPTEC_STARFIRE=m
CONFIG_B44=m
CONFIG_B44_PCI_AUTOSELECT=y
CONFIG_B44_PCICORE_AUTOSELECT=y
CONFIG_B44_PCI=y
CONFIG_FORCEDETH=m
# CONFIG_FORCEDETH_NAPI is not set
CONFIG_E100=m
CONFIG_FEALNX=m
CONFIG_NATSEMI=m
CONFIG_NE2K_PCI=m
CONFIG_8139CP=m
CONFIG_8139TOO=m
CONFIG_8139TOO_PIO=y
# CONFIG_8139TOO_TUNE_TWISTER is not set
CONFIG_8139TOO_8129=y
# CONFIG_8139_OLD_RX_RESET is not set
# CONFIG_R6040 is not set
CONFIG_SIS900=m
CONFIG_EPIC100=m
CONFIG_SMSC9420=m
CONFIG_SUNDANCE=m
# CONFIG_SUNDANCE_MMIO is not set
CONFIG_TLAN=m
CONFIG_KS8842=m
CONFIG_KS8851=m
CONFIG_KS8851_MLL=m
CONFIG_VIA_RHINE=m
CONFIG_VIA_RHINE_MMIO=y
CONFIG_SC92031=m
CONFIG_NET_POCKET=y
CONFIG_ATP=m
CONFIG_DE600=m
CONFIG_DE620=m
CONFIG_ATL2=m
CONFIG_NETDEV_1000=y
CONFIG_ACENIC=m
# CONFIG_ACENIC_OMIT_TIGON_I is not set
# CONFIG_DL2K is not set
CONFIG_E1000=m
CONFIG_E1000E=m
CONFIG_IP1000=m
CONFIG_IGB=m
CONFIG_IGBVF=m
CONFIG_NS83820=m
CONFIG_HAMACHI=m
CONFIG_YELLOWFIN=m
CONFIG_R8169=m
CONFIG_R8169_VLAN=y
CONFIG_SIS190=m
CONFIG_SKGE=m
# CONFIG_SKGE_DEBUG is not set
CONFIG_SKY2=m
# CONFIG_SKY2_DEBUG is not set
CONFIG_VIA_VELOCITY=m
CONFIG_TIGON3=m
CONFIG_BNX2=m
CONFIG_CNIC=m
CONFIG_QLA3XXX=m
CONFIG_ATL1=m
CONFIG_ATL1E=m
CONFIG_ATL1C=m
CONFIG_JME=m
CONFIG_NETDEV_10000=y
CONFIG_MDIO=m
CONFIG_CHELSIO_T1=m
CONFIG_CHELSIO_T1_1G=y
CONFIG_CHELSIO_T3_DEPENDS=y
CONFIG_CHELSIO_T3=m
CONFIG_ENIC=m
CONFIG_IXGBE=m
CONFIG_IXGBE_DCB=y
CONFIG_IXGB=m
CONFIG_S2IO=m
CONFIG_VXGE=m
# CONFIG_VXGE_DEBUG_TRACE_ALL is not set
CONFIG_MYRI10GE=m
CONFIG_NETXEN_NIC=m
CONFIG_NIU=m
CONFIG_MLX4_EN=m
CONFIG_MLX4_CORE=m
CONFIG_MLX4_DEBUG=y
CONFIG_TEHUTI=m
CONFIG_BNX2X=m
CONFIG_QLGE=m
CONFIG_SFC=m
CONFIG_SFC_MTD=y
CONFIG_BE2NET=m
CONFIG_TR=y
CONFIG_IBMOL=m
CONFIG_3C359=m
CONFIG_TMS380TR=m
CONFIG_TMSPCI=m
CONFIG_ABYSS=m
CONFIG_WLAN=y
CONFIG_AIRO=m
CONFIG_ATMEL=m
CONFIG_PCI_ATMEL=m
CONFIG_PRISM54=m
CONFIG_HOSTAP=m
CONFIG_HOSTAP_FIRMWARE=y
CONFIG_HOSTAP_FIRMWARE_NVRAM=y
CONFIG_HOSTAP_PLX=m
CONFIG_HOSTAP_PCI=m
#
# Enable WiMAX (Networking options) to see the WiMAX drivers
#
CONFIG_WAN=y
CONFIG_LANMEDIA=m
CONFIG_HDLC=m
CONFIG_HDLC_RAW=m
CONFIG_HDLC_RAW_ETH=m
CONFIG_HDLC_CISCO=m
CONFIG_HDLC_FR=m
CONFIG_HDLC_PPP=m
CONFIG_HDLC_X25=m
CONFIG_PCI200SYN=m
CONFIG_WANXL=m
# CONFIG_PC300TOO is not set
CONFIG_FARSYNC=m
CONFIG_DSCC4=m
CONFIG_DSCC4_PCISYNC=y
CONFIG_DSCC4_PCI_RST=y
CONFIG_DLCI=m
CONFIG_DLCI_MAX=8
CONFIG_WAN_ROUTER_DRIVERS=m
CONFIG_CYCLADES_SYNC=m
CONFIG_CYCLOMX_X25=y
CONFIG_LAPBETHER=m
CONFIG_X25_ASY=m
CONFIG_SBNI=m
# CONFIG_SBNI_MULTILINE is not set
CONFIG_ATM_DRIVERS=y
# CONFIG_ATM_DUMMY is not set
CONFIG_ATM_TCP=m
CONFIG_ATM_LANAI=m
CONFIG_ATM_ENI=m
# CONFIG_ATM_ENI_DEBUG is not set
# CONFIG_ATM_ENI_TUNE_BURST is not set
CONFIG_ATM_FIRESTREAM=m
CONFIG_ATM_ZATM=m
# CONFIG_ATM_ZATM_DEBUG is not set
CONFIG_ATM_IDT77252=m
# CONFIG_ATM_IDT77252_DEBUG is not set
# CONFIG_ATM_IDT77252_RCV_ALL is not set
CONFIG_ATM_IDT77252_USE_SUNI=y
CONFIG_ATM_AMBASSADOR=m
# CONFIG_ATM_AMBASSADOR_DEBUG is not set
CONFIG_ATM_HORIZON=m
# CONFIG_ATM_HORIZON_DEBUG is not set
CONFIG_ATM_IA=m
# CONFIG_ATM_IA_DEBUG is not set
CONFIG_ATM_FORE200E=m
# CONFIG_ATM_FORE200E_USE_TASKLET is not set
CONFIG_ATM_FORE200E_TX_RETRY=16
CONFIG_ATM_FORE200E_DEBUG=0
CONFIG_ATM_HE=m
CONFIG_ATM_HE_USE_SUNI=y
CONFIG_ATM_SOLOS=m
CONFIG_IEEE802154_DRIVERS=m
# CONFIG_IEEE802154_FAKEHARD is not set
CONFIG_FDDI=y
CONFIG_DEFXX=m
# CONFIG_DEFXX_MMIO is not set
CONFIG_SKFP=m
CONFIG_HIPPI=y
CONFIG_ROADRUNNER=m
# CONFIG_ROADRUNNER_LARGE_RINGS is not set
CONFIG_PLIP=m
CONFIG_PPP=y
CONFIG_PPP_MULTILINK=y
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_BSDCOMP=m
CONFIG_PPP_MPPE=m
CONFIG_PPPOE=m
CONFIG_PPPOATM=m
CONFIG_PPPOL2TP=m
CONFIG_SLIP=m
CONFIG_SLIP_COMPRESSED=y
CONFIG_SLHC=y
CONFIG_SLIP_SMART=y
CONFIG_SLIP_MODE_SLIP6=y
CONFIG_NET_FC=y
CONFIG_NETCONSOLE=m
CONFIG_NETCONSOLE_DYNAMIC=y
CONFIG_NETPOLL=y
# CONFIG_NETPOLL_TRAP is not set
CONFIG_NET_POLL_CONTROLLER=y
CONFIG_VMXNET3=m
CONFIG_ISDN=y
CONFIG_ISDN_I4L=m
CONFIG_MISDN=m
CONFIG_MISDN_DSP=m
CONFIG_MISDN_L1OIP=m
#
# mISDN hardware drivers
#
CONFIG_MISDN_HFCPCI=m
CONFIG_MISDN_HFCMULTI=m
CONFIG_MISDN_AVMFRITZ=m
CONFIG_MISDN_SPEEDFAX=m
CONFIG_MISDN_INFINEON=m
CONFIG_MISDN_W6692=m
CONFIG_MISDN_NETJET=m
CONFIG_MISDN_IPAC=m
CONFIG_MISDN_ISAR=m
CONFIG_ISDN_PPP=y
CONFIG_ISDN_PPP_VJ=y
CONFIG_ISDN_MPP=y
CONFIG_IPPP_FILTER=y
CONFIG_ISDN_PPP_BSDCOMP=m
CONFIG_ISDN_AUDIO=y
CONFIG_ISDN_TTY_FAX=y
CONFIG_ISDN_X25=y
#
# ISDN feature submodules
#
CONFIG_ISDN_DIVERSION=m
#
# ISDN4Linux hardware drivers
#
#
# Passive cards
#
CONFIG_ISDN_DRV_HISAX=m
#
# D-channel protocol features
#
CONFIG_HISAX_EURO=y
CONFIG_DE_AOC=y
# CONFIG_HISAX_NO_SENDCOMPLETE is not set
# CONFIG_HISAX_NO_LLC is not set
# CONFIG_HISAX_NO_KEYPAD is not set
CONFIG_HISAX_1TR6=y
CONFIG_HISAX_NI1=y
CONFIG_HISAX_MAX_CARDS=8
#
# HiSax supported cards
#
CONFIG_HISAX_16_3=y
CONFIG_HISAX_S0BOX=y
CONFIG_HISAX_FRITZPCI=y
CONFIG_HISAX_AVM_A1_PCMCIA=y
CONFIG_HISAX_ELSA=y
CONFIG_HISAX_DIEHLDIVA=y
CONFIG_HISAX_SEDLBAUER=y
CONFIG_HISAX_NICCY=y
CONFIG_HISAX_GAZEL=y
CONFIG_HISAX_HFC_SX=y
# CONFIG_HISAX_DEBUG is not set
#
# HiSax PCMCIA card service modules
#
#
# HiSax sub driver modules
#
CONFIG_HISAX_HFC4S8S=m
#
# Active cards
#
CONFIG_HYSDN=m
CONFIG_HYSDN_CAPI=y
CONFIG_ISDN_HDLC=m
CONFIG_ISDN_CAPI=m
CONFIG_ISDN_DRV_AVMB1_VERBOSE_REASON=y
CONFIG_CAPI_TRACE=y
CONFIG_ISDN_CAPI_MIDDLEWARE=y
CONFIG_ISDN_CAPI_CAPI20=m
CONFIG_ISDN_CAPI_CAPIFS_BOOL=y
CONFIG_ISDN_CAPI_CAPIFS=m
CONFIG_ISDN_CAPI_CAPIDRV=m
#
# CAPI hardware drivers
#
CONFIG_CAPI_AVM=y
CONFIG_ISDN_DRV_AVMB1_B1PCI=m
CONFIG_ISDN_DRV_AVMB1_B1PCIV4=y
CONFIG_ISDN_DRV_AVMB1_B1PCMCIA=m
CONFIG_ISDN_DRV_AVMB1_T1PCI=m
CONFIG_ISDN_DRV_AVMB1_C4=m
CONFIG_CAPI_EICON=y
CONFIG_ISDN_DIVAS=m
CONFIG_ISDN_DIVAS_BRIPCI=y
CONFIG_ISDN_DIVAS_PRIPCI=y
CONFIG_ISDN_DIVAS_DIVACAPI=m
CONFIG_ISDN_DIVAS_USERIDI=m
CONFIG_ISDN_DIVAS_MAINT=m
CONFIG_ISDN_DRV_GIGASET=m
# CONFIG_GIGASET_CAPI is not set
CONFIG_GIGASET_I4L=y
# CONFIG_GIGASET_DUMMYLL is not set
CONFIG_GIGASET_M101=m
# CONFIG_GIGASET_DEBUG is not set
CONFIG_PHONE=m
CONFIG_PHONE_IXJ=m
#
# Input device support
#
CONFIG_INPUT=y
CONFIG_INPUT_FF_MEMLESS=m
CONFIG_INPUT_POLLDEV=m
CONFIG_INPUT_SPARSEKMAP=m
#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_JOYDEV=m
CONFIG_INPUT_EVDEV=y
CONFIG_INPUT_EVBUG=m
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ADP5588=m
CONFIG_KEYBOARD_ATKBD=y
CONFIG_QT2160=m
CONFIG_KEYBOARD_LKKBD=m
CONFIG_KEYBOARD_GPIO=m
CONFIG_KEYBOARD_MATRIX=m
CONFIG_KEYBOARD_LM8323=m
CONFIG_KEYBOARD_MAX7359=m
CONFIG_KEYBOARD_NEWTON=m
CONFIG_KEYBOARD_OPENCORES=m
CONFIG_KEYBOARD_STOWAWAY=m
CONFIG_KEYBOARD_SUNKBD=m
CONFIG_KEYBOARD_TWL4030=m
CONFIG_KEYBOARD_XTKBD=m
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=m
CONFIG_MOUSE_PS2_ALPS=y
CONFIG_MOUSE_PS2_LOGIPS2PP=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
CONFIG_MOUSE_PS2_LIFEBOOK=y
CONFIG_MOUSE_PS2_TRACKPOINT=y
CONFIG_MOUSE_PS2_ELANTECH=y
CONFIG_MOUSE_PS2_SENTELIC=y
# CONFIG_MOUSE_PS2_TOUCHKIT is not set
CONFIG_MOUSE_SERIAL=m
CONFIG_MOUSE_VSXXXAA=m
CONFIG_MOUSE_GPIO=m
CONFIG_MOUSE_SYNAPTICS_I2C=m
CONFIG_INPUT_JOYSTICK=y
CONFIG_JOYSTICK_ANALOG=m
CONFIG_JOYSTICK_A3D=m
CONFIG_JOYSTICK_ADI=m
CONFIG_JOYSTICK_COBRA=m
CONFIG_JOYSTICK_GF2K=m
CONFIG_JOYSTICK_GRIP=m
CONFIG_JOYSTICK_GRIP_MP=m
CONFIG_JOYSTICK_GUILLEMOT=m
CONFIG_JOYSTICK_INTERACT=m
CONFIG_JOYSTICK_SIDEWINDER=m
CONFIG_JOYSTICK_TMDC=m
CONFIG_JOYSTICK_IFORCE=m
CONFIG_JOYSTICK_IFORCE_232=y
CONFIG_JOYSTICK_WARRIOR=m
CONFIG_JOYSTICK_MAGELLAN=m
CONFIG_JOYSTICK_SPACEORB=m
CONFIG_JOYSTICK_SPACEBALL=m
CONFIG_JOYSTICK_STINGER=m
CONFIG_JOYSTICK_TWIDJOY=m
CONFIG_JOYSTICK_ZHENHUA=m
CONFIG_JOYSTICK_DB9=m
CONFIG_JOYSTICK_GAMECON=m
CONFIG_JOYSTICK_TURBOGRAFX=m
CONFIG_JOYSTICK_JOYDUMP=m
CONFIG_JOYSTICK_WALKERA0701=m
CONFIG_INPUT_TABLET=y
CONFIG_INPUT_TOUCHSCREEN=y
CONFIG_TOUCHSCREEN_ADS7846=m
CONFIG_TOUCHSCREEN_AD7877=m
CONFIG_TOUCHSCREEN_AD7879_I2C=m
CONFIG_TOUCHSCREEN_AD7879=m
CONFIG_TOUCHSCREEN_DA9034=m
# CONFIG_TOUCHSCREEN_DYNAPRO is not set
CONFIG_TOUCHSCREEN_EETI=m
CONFIG_TOUCHSCREEN_FUJITSU=m
CONFIG_TOUCHSCREEN_GUNZE=m
CONFIG_TOUCHSCREEN_ELO=m
CONFIG_TOUCHSCREEN_WACOM_W8001=m
CONFIG_TOUCHSCREEN_MCS5000=m
CONFIG_TOUCHSCREEN_MTOUCH=m
CONFIG_TOUCHSCREEN_INEXIO=m
CONFIG_TOUCHSCREEN_MK712=m
CONFIG_TOUCHSCREEN_PENMOUNT=m
CONFIG_TOUCHSCREEN_TOUCHRIGHT=m
CONFIG_TOUCHSCREEN_TOUCHWIN=m
# CONFIG_TOUCHSCREEN_MC13783 is not set
CONFIG_TOUCHSCREEN_TOUCHIT213=m
CONFIG_TOUCHSCREEN_TSC2007=m
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=m
# CONFIG_INPUT_APANEL is not set
CONFIG_INPUT_ATLAS_BTNS=m
CONFIG_INPUT_TWL4030_PWRBUTTON=m
CONFIG_INPUT_UINPUT=m
CONFIG_INPUT_WINBOND_CIR=m
CONFIG_INPUT_PCF50633_PMU=m
CONFIG_INPUT_GPIO_ROTARY_ENCODER=m
#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=m
CONFIG_SERIO_CT82C710=m
CONFIG_SERIO_PARKBD=m
CONFIG_SERIO_PCIPS2=m
CONFIG_SERIO_LIBPS2=y
CONFIG_SERIO_RAW=m
# CONFIG_SERIO_ALTERA_PS2 is not set
CONFIG_GAMEPORT=m
CONFIG_GAMEPORT_NS558=m
CONFIG_GAMEPORT_L4=m
CONFIG_GAMEPORT_EMU10K1=m
CONFIG_GAMEPORT_FM801=m
#
# Character devices
#
CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_VT_HW_CONSOLE_BINDING=y
# CONFIG_DEVKMEM is not set
CONFIG_SERIAL_NONSTANDARD=y
CONFIG_COMPUTONE=m
CONFIG_ROCKETPORT=m
CONFIG_CYCLADES=m
# CONFIG_CYZ_INTR is not set
CONFIG_DIGIEPCA=m
CONFIG_MOXA_INTELLIO=m
CONFIG_MOXA_SMARTIO=m
# CONFIG_ISI is not set
CONFIG_SYNCLINK=m
CONFIG_SYNCLINKMP=m
CONFIG_SYNCLINK_GT=m
CONFIG_N_HDLC=m
CONFIG_RISCOM8=m
CONFIG_SPECIALIX=m
CONFIG_STALDRV=y
CONFIG_STALLION=m
CONFIG_ISTALLION=m
CONFIG_NOZOMI=m
#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_PNP=y
CONFIG_SERIAL_8250_NR_UARTS=48
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
CONFIG_SERIAL_8250_SHARE_IRQ=y
# CONFIG_SERIAL_8250_DETECT_IRQ is not set
CONFIG_SERIAL_8250_RSA=y
#
# Non-8250 serial port support
#
CONFIG_SERIAL_MAX3100=m
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_CONSOLE_POLL=y
CONFIG_SERIAL_JSM=m
CONFIG_UNIX98_PTYS=y
CONFIG_DEVPTS_MULTIPLE_INSTANCES=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=0
CONFIG_PRINTER=m
# CONFIG_LP_CONSOLE is not set
CONFIG_PPDEV=m
CONFIG_IPMI_HANDLER=m
# CONFIG_IPMI_PANIC_EVENT is not set
CONFIG_IPMI_DEVICE_INTERFACE=m
CONFIG_IPMI_SI=m
CONFIG_IPMI_WATCHDOG=m
CONFIG_IPMI_POWEROFF=m
CONFIG_HW_RANDOM=y
CONFIG_HW_RANDOM_TIMERIOMEM=m
CONFIG_HW_RANDOM_INTEL=m
CONFIG_HW_RANDOM_AMD=m
CONFIG_HW_RANDOM_VIA=m
CONFIG_NVRAM=m
CONFIG_R3964=m
CONFIG_APPLICOM=m
CONFIG_MWAVE=m
CONFIG_PC8736x_GPIO=m
CONFIG_NSC_GPIO=m
CONFIG_RAW_DRIVER=m
CONFIG_MAX_RAW_DEVS=256
CONFIG_HPET=y
CONFIG_HPET_MMAP=y
CONFIG_HANGCHECK_TIMER=m
CONFIG_TCG_TPM=m
CONFIG_TCG_TIS=m
CONFIG_TCG_NSC=m
CONFIG_TCG_ATMEL=m
CONFIG_TCG_INFINEON=m
CONFIG_TELCLOCK=m
CONFIG_DEVPORT=y
CONFIG_I2C=y
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_COMPAT=y
CONFIG_I2C_CHARDEV=m
# CONFIG_I2C_HELPER_AUTO is not set
#
# I2C Algorithms
#
CONFIG_I2C_ALGOBIT=y
CONFIG_I2C_ALGOPCF=m
CONFIG_I2C_ALGOPCA=m
#
# I2C Hardware Bus support
#
#
# PC SMBus host controller drivers
#
CONFIG_I2C_ALI1535=m
CONFIG_I2C_ALI1563=m
CONFIG_I2C_ALI15X3=m
CONFIG_I2C_AMD756=m
CONFIG_I2C_AMD756_S4882=m
CONFIG_I2C_AMD8111=m
CONFIG_I2C_I801=m
CONFIG_I2C_ISCH=m
CONFIG_I2C_PIIX4=m
CONFIG_I2C_NFORCE2=m
CONFIG_I2C_NFORCE2_S4985=m
CONFIG_I2C_SIS5595=m
CONFIG_I2C_SIS630=m
CONFIG_I2C_SIS96X=m
CONFIG_I2C_VIA=m
CONFIG_I2C_VIAPRO=m
#
# ACPI drivers
#
CONFIG_I2C_SCMI=m
#
# I2C system bus drivers (mostly embedded / system-on-chip)
#
CONFIG_I2C_GPIO=m
CONFIG_I2C_OCORES=m
CONFIG_I2C_SIMTEC=m
#
# External I2C/SMBus adapter drivers
#
CONFIG_I2C_PARPORT=m
CONFIG_I2C_PARPORT_LIGHT=m
CONFIG_I2C_TAOS_EVM=m
#
# Other I2C/SMBus bus drivers
#
CONFIG_I2C_PCA_PLATFORM=m
CONFIG_I2C_STUB=m
#
# Miscellaneous I2C Chip support
#
CONFIG_SENSORS_TSL2550=m
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set
CONFIG_SPI=y
# CONFIG_SPI_DEBUG is not set
CONFIG_SPI_MASTER=y
#
# SPI Master Controller Drivers
#
CONFIG_SPI_BITBANG=m
CONFIG_SPI_BUTTERFLY=m
CONFIG_SPI_GPIO=m
CONFIG_SPI_LM70_LLP=m
# CONFIG_SPI_XILINX is not set
# CONFIG_SPI_DESIGNWARE is not set
#
# SPI Protocol Masters
#
CONFIG_SPI_SPIDEV=m
CONFIG_SPI_TLE62X0=m
#
# PPS support
#
CONFIG_PPS=m
# CONFIG_PPS_DEBUG is not set
CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y
CONFIG_GPIOLIB=y
# CONFIG_DEBUG_GPIO is not set
CONFIG_GPIO_SYSFS=y
#
# Memory mapped GPIO expanders:
#
#
# I2C GPIO expanders:
#
CONFIG_GPIO_MAX732X=m
CONFIG_GPIO_PCA953X=m
CONFIG_GPIO_PCF857X=m
CONFIG_GPIO_TWL4030=m
# CONFIG_GPIO_ADP5588 is not set
#
# PCI GPIO expanders:
#
# CONFIG_GPIO_CS5535 is not set
CONFIG_GPIO_LANGWELL=y
#
# SPI GPIO expanders:
#
CONFIG_GPIO_MAX7301=m
CONFIG_GPIO_MCP23S08=m
CONFIG_GPIO_MC33880=m
#
# AC97 GPIO expanders:
#
CONFIG_W1=m
CONFIG_W1_CON=y
#
# 1-wire Bus Masters
#
CONFIG_W1_MASTER_MATROX=m
CONFIG_W1_MASTER_DS2482=m
CONFIG_W1_MASTER_GPIO=m
#
# 1-wire Slaves
#
CONFIG_W1_SLAVE_THERM=m
CONFIG_W1_SLAVE_SMEM=m
CONFIG_W1_SLAVE_DS2431=m
CONFIG_W1_SLAVE_DS2433=m
# CONFIG_W1_SLAVE_DS2433_CRC is not set
CONFIG_W1_SLAVE_DS2760=m
CONFIG_W1_SLAVE_BQ27000=m
CONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not set
CONFIG_PDA_POWER=m
CONFIG_WM8350_POWER=m
CONFIG_BATTERY_DS2760=m
CONFIG_BATTERY_DS2782=m
CONFIG_BATTERY_BQ27x00=m
CONFIG_BATTERY_DA9030=m
CONFIG_BATTERY_MAX17040=m
CONFIG_CHARGER_PCF50633=m
CONFIG_HWMON=y
CONFIG_HWMON_VID=m
# CONFIG_HWMON_DEBUG_CHIP is not set
#
# Native drivers
#
CONFIG_SENSORS_ABITUGURU=m
CONFIG_SENSORS_ABITUGURU3=m
CONFIG_SENSORS_AD7414=m
CONFIG_SENSORS_AD7418=m
CONFIG_SENSORS_ADCXX=m
CONFIG_SENSORS_ADM1021=m
CONFIG_SENSORS_ADM1025=m
CONFIG_SENSORS_ADM1026=m
CONFIG_SENSORS_ADM1029=m
CONFIG_SENSORS_ADM1031=m
CONFIG_SENSORS_ADM9240=m
CONFIG_SENSORS_ADT7462=m
CONFIG_SENSORS_ADT7470=m
CONFIG_SENSORS_ADT7473=m
CONFIG_SENSORS_ADT7475=m
CONFIG_SENSORS_K8TEMP=m
# CONFIG_SENSORS_K10TEMP is not set
CONFIG_SENSORS_ASB100=m
CONFIG_SENSORS_ATXP1=m
CONFIG_SENSORS_DS1621=m
CONFIG_SENSORS_I5K_AMB=m
CONFIG_SENSORS_F71805F=m
CONFIG_SENSORS_F71882FG=m
CONFIG_SENSORS_F75375S=m
CONFIG_SENSORS_FSCHMD=m
CONFIG_SENSORS_G760A=m
CONFIG_SENSORS_GL518SM=m
CONFIG_SENSORS_GL520SM=m
CONFIG_SENSORS_CORETEMP=m
CONFIG_SENSORS_IBMAEM=m
CONFIG_SENSORS_IBMPEX=m
CONFIG_SENSORS_IT87=m
CONFIG_SENSORS_LM63=m
CONFIG_SENSORS_LM70=m
# CONFIG_SENSORS_LM73 is not set
CONFIG_SENSORS_LM75=m
CONFIG_SENSORS_LM77=m
CONFIG_SENSORS_LM78=m
CONFIG_SENSORS_LM80=m
CONFIG_SENSORS_LM83=m
CONFIG_SENSORS_LM85=m
CONFIG_SENSORS_LM87=m
CONFIG_SENSORS_LM90=m
CONFIG_SENSORS_LM92=m
CONFIG_SENSORS_LM93=m
CONFIG_SENSORS_LTC4215=m
CONFIG_SENSORS_LTC4245=m
CONFIG_SENSORS_LM95241=m
CONFIG_SENSORS_MAX1111=m
CONFIG_SENSORS_MAX1619=m
CONFIG_SENSORS_MAX6650=m
CONFIG_SENSORS_PC87360=m
CONFIG_SENSORS_PC87427=m
CONFIG_SENSORS_PCF8591=m
CONFIG_SENSORS_SHT15=m
CONFIG_SENSORS_SIS5595=m
CONFIG_SENSORS_DME1737=m
CONFIG_SENSORS_SMSC47M1=m
CONFIG_SENSORS_SMSC47M192=m
CONFIG_SENSORS_SMSC47B397=m
CONFIG_SENSORS_ADS7828=m
# CONFIG_SENSORS_AMC6821 is not set
CONFIG_SENSORS_THMC50=m
CONFIG_SENSORS_TMP401=m
CONFIG_SENSORS_TMP421=m
# CONFIG_SENSORS_VIA_CPUTEMP is not set
CONFIG_SENSORS_VIA686A=m
CONFIG_SENSORS_VT1211=m
CONFIG_SENSORS_VT8231=m
CONFIG_SENSORS_W83781D=m
CONFIG_SENSORS_W83791D=m
CONFIG_SENSORS_W83792D=m
CONFIG_SENSORS_W83793=m
CONFIG_SENSORS_W83L785TS=m
CONFIG_SENSORS_W83L786NG=m
CONFIG_SENSORS_W83627HF=m
CONFIG_SENSORS_W83627EHF=m
CONFIG_SENSORS_WM8350=m
CONFIG_SENSORS_HDAPS=m
# CONFIG_SENSORS_LIS3_I2C is not set
CONFIG_SENSORS_APPLESMC=m
# CONFIG_SENSORS_MC13783_ADC is not set
#
# ACPI drivers
#
CONFIG_SENSORS_ATK0110=m
CONFIG_SENSORS_LIS3LV02D=m
CONFIG_THERMAL=y
CONFIG_THERMAL_HWMON=y
CONFIG_WATCHDOG=y
# CONFIG_WATCHDOG_NOWAYOUT is not set
#
# Watchdog Device Drivers
#
CONFIG_SOFT_WATCHDOG=m
CONFIG_WM8350_WATCHDOG=m
CONFIG_TWL4030_WATCHDOG=m
CONFIG_ACQUIRE_WDT=m
CONFIG_ADVANTECH_WDT=m
CONFIG_ALIM1535_WDT=m
CONFIG_ALIM7101_WDT=m
CONFIG_SC520_WDT=m
CONFIG_SBC_FITPC2_WATCHDOG=m
CONFIG_EUROTECH_WDT=m
CONFIG_IB700_WDT=m
CONFIG_IBMASR=m
CONFIG_WAFER_WDT=m
CONFIG_I6300ESB_WDT=m
CONFIG_ITCO_WDT=m
CONFIG_ITCO_VENDOR_SUPPORT=y
CONFIG_IT8712F_WDT=m
CONFIG_IT87_WDT=m
# CONFIG_HP_WATCHDOG is not set
CONFIG_SC1200_WDT=m
CONFIG_PC87413_WDT=m
CONFIG_60XX_WDT=m
CONFIG_SBC8360_WDT=m
CONFIG_CPU5_WDT=m
CONFIG_SMSC_SCH311X_WDT=m
CONFIG_SMSC37B787_WDT=m
CONFIG_W83627HF_WDT=m
CONFIG_W83697HF_WDT=m
CONFIG_W83697UG_WDT=m
CONFIG_W83877F_WDT=m
CONFIG_W83977F_WDT=m
CONFIG_MACHZ_WDT=m
CONFIG_SBC_EPX_C3_WATCHDOG=m
#
# PCI-based Watchdog Cards
#
CONFIG_PCIPCWATCHDOG=m
CONFIG_WDTPCI=m
CONFIG_SSB_POSSIBLE=y
#
# Sonics Silicon Backplane
#
CONFIG_SSB=m
CONFIG_SSB_SPROM=y
CONFIG_SSB_PCIHOST_POSSIBLE=y
CONFIG_SSB_PCIHOST=y
# CONFIG_SSB_B43_PCI_BRIDGE is not set
# CONFIG_SSB_DEBUG is not set
CONFIG_SSB_DRIVER_PCICORE_POSSIBLE=y
CONFIG_SSB_DRIVER_PCICORE=y
#
# Multifunction device drivers
#
CONFIG_MFD_CORE=m
CONFIG_MFD_SM501=m
# CONFIG_MFD_SM501_GPIO is not set
CONFIG_HTC_PASIC3=m
CONFIG_TPS65010=m
CONFIG_TWL4030_CORE=y
# CONFIG_TWL4030_CODEC is not set
# CONFIG_MFD_TMIO is not set
CONFIG_PMIC_DA903X=y
# CONFIG_PMIC_ADP5520 is not set
CONFIG_MFD_WM8400=m
# CONFIG_MFD_WM831X is not set
CONFIG_MFD_WM8350=m
CONFIG_MFD_WM8350_I2C=m
CONFIG_MFD_PCF50633=m
CONFIG_MFD_MC13783=m
CONFIG_PCF50633_ADC=m
CONFIG_PCF50633_GPIO=m
CONFIG_AB3100_CORE=m
CONFIG_AB3100_OTP=m
# CONFIG_EZX_PCAP is not set
# CONFIG_MFD_88PM8607 is not set
# CONFIG_AB4500_CORE is not set
CONFIG_REGULATOR=y
# CONFIG_REGULATOR_DEBUG is not set
# CONFIG_REGULATOR_FIXED_VOLTAGE is not set
CONFIG_REGULATOR_VIRTUAL_CONSUMER=m
CONFIG_REGULATOR_USERSPACE_CONSUMER=m
CONFIG_REGULATOR_BQ24022=m
CONFIG_REGULATOR_MAX1586=m
# CONFIG_REGULATOR_MAX8660 is not set
CONFIG_REGULATOR_TWL4030=y
CONFIG_REGULATOR_WM8350=m
CONFIG_REGULATOR_WM8400=m
CONFIG_REGULATOR_DA903X=m
CONFIG_REGULATOR_PCF50633=m
CONFIG_REGULATOR_LP3971=m
CONFIG_REGULATOR_MC13783=m
CONFIG_REGULATOR_AB3100=m
CONFIG_REGULATOR_TPS65023=m
CONFIG_REGULATOR_TPS6507X=m
CONFIG_MEDIA_SUPPORT=m
#
# Multimedia core support
#
CONFIG_VIDEO_DEV=m
CONFIG_VIDEO_V4L2_COMMON=m
CONFIG_VIDEO_ALLOW_V4L1=y
CONFIG_VIDEO_V4L1_COMPAT=y
CONFIG_DVB_CORE=m
CONFIG_VIDEO_MEDIA=m
#
# Multimedia drivers
#
CONFIG_VIDEO_SAA7146=m
CONFIG_VIDEO_SAA7146_VV=m
CONFIG_IR_CORE=m
CONFIG_VIDEO_IR=m
CONFIG_MEDIA_ATTACH=y
CONFIG_MEDIA_TUNER=m
# CONFIG_MEDIA_TUNER_CUSTOMISE is not set
CONFIG_MEDIA_TUNER_SIMPLE=m
CONFIG_MEDIA_TUNER_TDA8290=m
CONFIG_MEDIA_TUNER_TDA827X=m
CONFIG_MEDIA_TUNER_TDA18271=m
CONFIG_MEDIA_TUNER_TDA9887=m
CONFIG_MEDIA_TUNER_TEA5761=m
CONFIG_MEDIA_TUNER_TEA5767=m
CONFIG_MEDIA_TUNER_MT20XX=m
CONFIG_MEDIA_TUNER_MT2131=m
CONFIG_MEDIA_TUNER_XC2028=m
CONFIG_MEDIA_TUNER_XC5000=m
CONFIG_MEDIA_TUNER_MXL5005S=m
CONFIG_MEDIA_TUNER_MC44S803=m
CONFIG_VIDEO_V4L2=m
CONFIG_VIDEO_V4L1=m
CONFIG_VIDEOBUF_GEN=m
CONFIG_VIDEOBUF_DMA_SG=m
CONFIG_VIDEOBUF_VMALLOC=m
CONFIG_VIDEOBUF_DVB=m
CONFIG_VIDEO_BTCX=m
CONFIG_VIDEO_TVEEPROM=m
CONFIG_VIDEO_TUNER=m
CONFIG_VIDEO_CAPTURE_DRIVERS=y
# CONFIG_VIDEO_ADV_DEBUG is not set
# CONFIG_VIDEO_FIXED_MINOR_RANGES is not set
CONFIG_VIDEO_HELPER_CHIPS_AUTO=y
CONFIG_VIDEO_IR_I2C=m
CONFIG_VIDEO_TVAUDIO=m
CONFIG_VIDEO_TDA7432=m
CONFIG_VIDEO_TDA9840=m
CONFIG_VIDEO_TEA6415C=m
CONFIG_VIDEO_TEA6420=m
CONFIG_VIDEO_MSP3400=m
CONFIG_VIDEO_CS5345=m
CONFIG_VIDEO_CS53L32A=m
CONFIG_VIDEO_M52790=m
CONFIG_VIDEO_WM8775=m
CONFIG_VIDEO_WM8739=m
CONFIG_VIDEO_VP27SMPX=m
CONFIG_VIDEO_SAA6588=m
CONFIG_VIDEO_BT819=m
CONFIG_VIDEO_BT856=m
CONFIG_VIDEO_BT866=m
CONFIG_VIDEO_KS0127=m
CONFIG_VIDEO_OV7670=m
CONFIG_VIDEO_SAA7110=m
CONFIG_VIDEO_SAA711X=m
CONFIG_VIDEO_SAA717X=m
CONFIG_VIDEO_VPX3220=m
CONFIG_VIDEO_CX25840=m
CONFIG_VIDEO_CX2341X=m
CONFIG_VIDEO_SAA7127=m
CONFIG_VIDEO_SAA7185=m
CONFIG_VIDEO_ADV7170=m
CONFIG_VIDEO_ADV7175=m
CONFIG_VIDEO_UPD64031A=m
CONFIG_VIDEO_UPD64083=m
CONFIG_VIDEO_VIVI=m
CONFIG_VIDEO_BT848=m
CONFIG_VIDEO_BT848_DVB=y
CONFIG_VIDEO_BWQCAM=m
CONFIG_VIDEO_CQCAM=m
CONFIG_VIDEO_W9966=m
CONFIG_VIDEO_CPIA=m
CONFIG_VIDEO_CPIA_PP=m
CONFIG_VIDEO_SAA5246A=m
CONFIG_VIDEO_SAA5249=m
CONFIG_VIDEO_STRADIS=m
CONFIG_VIDEO_ZORAN=m
CONFIG_VIDEO_ZORAN_DC30=m
CONFIG_VIDEO_ZORAN_ZR36060=m
CONFIG_VIDEO_ZORAN_BUZ=m
CONFIG_VIDEO_ZORAN_DC10=m
CONFIG_VIDEO_ZORAN_LML33=m
CONFIG_VIDEO_ZORAN_LML33R10=m
CONFIG_VIDEO_ZORAN_AVS6EYES=m
CONFIG_VIDEO_SAA7134=m
CONFIG_VIDEO_SAA7134_DVB=m
CONFIG_VIDEO_MXB=m
CONFIG_VIDEO_HEXIUM_ORION=m
CONFIG_VIDEO_HEXIUM_GEMINI=m
CONFIG_VIDEO_CX88=m
CONFIG_VIDEO_CX88_BLACKBIRD=m
CONFIG_VIDEO_CX88_DVB=m
CONFIG_VIDEO_CX88_MPEG=m
CONFIG_VIDEO_CX88_VP3054=m
CONFIG_VIDEO_CX23885=m
CONFIG_VIDEO_IVTV=m
CONFIG_VIDEO_CX18=m
CONFIG_VIDEO_SAA7164=m
CONFIG_VIDEO_CAFE_CCIC=m
CONFIG_SOC_CAMERA=m
CONFIG_SOC_CAMERA_MT9M001=m
CONFIG_SOC_CAMERA_MT9M111=m
CONFIG_SOC_CAMERA_MT9T031=m
# CONFIG_SOC_CAMERA_MT9T112 is not set
CONFIG_SOC_CAMERA_MT9V022=m
# CONFIG_SOC_CAMERA_RJ54N1 is not set
CONFIG_SOC_CAMERA_TW9910=m
CONFIG_SOC_CAMERA_PLATFORM=m
CONFIG_SOC_CAMERA_OV772X=m
# CONFIG_SOC_CAMERA_OV9640 is not set
CONFIG_RADIO_ADAPTERS=y
CONFIG_RADIO_GEMTEK_PCI=m
CONFIG_RADIO_MAXIRADIO=m
CONFIG_RADIO_MAESTRO=m
CONFIG_I2C_SI4713=m
CONFIG_RADIO_SI4713=m
CONFIG_RADIO_SI470X=y
CONFIG_I2C_SI470X=m
CONFIG_RADIO_TEA5764=m
# CONFIG_RADIO_TEF6862 is not set
CONFIG_DVB_MAX_ADAPTERS=8
CONFIG_DVB_DYNAMIC_MINORS=y
CONFIG_DVB_CAPTURE_DRIVERS=y
#
# Supported SAA7146 based PCI Adapters
#
CONFIG_TTPCI_EEPROM=m
CONFIG_DVB_AV7110=m
CONFIG_DVB_AV7110_OSD=y
CONFIG_DVB_BUDGET_CORE=m
CONFIG_DVB_BUDGET=m
CONFIG_DVB_BUDGET_CI=m
CONFIG_DVB_BUDGET_AV=m
CONFIG_DVB_BUDGET_PATCH=m
CONFIG_SMS_SIANO_MDTV=m
#
# Siano module components
#
#
# Supported FlexCopII (B2C2) Adapters
#
CONFIG_DVB_B2C2_FLEXCOP=m
CONFIG_DVB_B2C2_FLEXCOP_PCI=m
# CONFIG_DVB_B2C2_FLEXCOP_DEBUG is not set
#
# Supported BT878 Adapters
#
CONFIG_DVB_BT8XX=m
#
# Supported Pluto2 Adapters
#
CONFIG_DVB_PLUTO2=m
#
# Supported SDMC DM1105 Adapters
#
CONFIG_DVB_DM1105=m
#
# Supported FireWire (IEEE 1394) Adapters
#
CONFIG_DVB_FIREDTV=m
CONFIG_DVB_FIREDTV_FIREWIRE=y
CONFIG_DVB_FIREDTV_IEEE1394=y
CONFIG_DVB_FIREDTV_INPUT=y
#
# Supported Earthsoft PT1 Adapters
#
CONFIG_DVB_PT1=m
#
# Supported Mantis Adapters
#
# CONFIG_MANTIS_CORE is not set
#
# Supported DVB Frontends
#
# CONFIG_DVB_FE_CUSTOMISE is not set
CONFIG_DVB_STB0899=m
CONFIG_DVB_STB6100=m
CONFIG_DVB_CX24110=m
CONFIG_DVB_CX24123=m
CONFIG_DVB_MT312=m
CONFIG_DVB_ZL10036=m
CONFIG_DVB_ZL10039=m
CONFIG_DVB_S5H1420=m
CONFIG_DVB_STV0288=m
CONFIG_DVB_STB6000=m
CONFIG_DVB_STV0299=m
CONFIG_DVB_STV6110=m
CONFIG_DVB_STV0900=m
CONFIG_DVB_TDA8083=m
CONFIG_DVB_TDA10086=m
CONFIG_DVB_TDA8261=m
CONFIG_DVB_VES1X93=m
CONFIG_DVB_TUNER_ITD1000=m
CONFIG_DVB_TUNER_CX24113=m
CONFIG_DVB_TDA826X=m
CONFIG_DVB_TUA6100=m
CONFIG_DVB_CX24116=m
CONFIG_DVB_SI21XX=m
CONFIG_DVB_DS3000=m
CONFIG_DVB_SP8870=m
CONFIG_DVB_SP887X=m
CONFIG_DVB_CX22702=m
CONFIG_DVB_L64781=m
CONFIG_DVB_TDA1004X=m
CONFIG_DVB_NXT6000=m
CONFIG_DVB_MT352=m
CONFIG_DVB_ZL10353=m
CONFIG_DVB_DIB7000P=m
CONFIG_DVB_TDA10048=m
CONFIG_DVB_VES1820=m
CONFIG_DVB_TDA10021=m
CONFIG_DVB_TDA10023=m
CONFIG_DVB_STV0297=m
CONFIG_DVB_NXT200X=m
CONFIG_DVB_OR51211=m
CONFIG_DVB_OR51132=m
CONFIG_DVB_BCM3510=m
CONFIG_DVB_LGDT330X=m
CONFIG_DVB_LGDT3305=m
CONFIG_DVB_S5H1409=m
CONFIG_DVB_S5H1411=m
CONFIG_DVB_PLL=m
CONFIG_DVB_LNBP21=m
CONFIG_DVB_ISL6405=m
CONFIG_DVB_ISL6421=m
CONFIG_DAB=y
#
# Graphics support
#
# CONFIG_AGP is not set
CONFIG_VGA_ARB=y
# CONFIG_DRM is not set
# CONFIG_VGASTATE is not set
# CONFIG_VIDEO_OUTPUT_CONTROL is not set
# CONFIG_FB is not set
CONFIG_BACKLIGHT_LCD_SUPPORT=y
# CONFIG_LCD_CLASS_DEVICE is not set
CONFIG_BACKLIGHT_CLASS_DEVICE=m
CONFIG_BACKLIGHT_GENERIC=m
CONFIG_BACKLIGHT_PROGEAR=m
CONFIG_BACKLIGHT_DA903X=m
CONFIG_BACKLIGHT_MBP_NVIDIA=m
CONFIG_BACKLIGHT_SAHARA=m
#
# Display device support
#
# CONFIG_DISPLAY_SUPPORT is not set
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VGACON_SOFT_SCROLLBACK is not set
CONFIG_DUMMY_CONSOLE=y
# CONFIG_SOUND is not set
# CONFIG_HID_SUPPORT is not set
CONFIG_HID=m
# CONFIG_USB_SUPPORT is not set
# CONFIG_UWB is not set
# CONFIG_MMC is not set
# CONFIG_MEMSTICK is not set
CONFIG_NEW_LEDS=y
CONFIG_LEDS_CLASS=m
#
# LED drivers
#
CONFIG_LEDS_ALIX2=m
CONFIG_LEDS_PCA9532=m
CONFIG_LEDS_GPIO=m
CONFIG_LEDS_GPIO_PLATFORM=y
CONFIG_LEDS_LP3944=m
# CONFIG_LEDS_CLEVO_MAIL is not set
CONFIG_LEDS_PCA955X=m
CONFIG_LEDS_WM8350=m
CONFIG_LEDS_DA903X=m
CONFIG_LEDS_DAC124S085=m
# CONFIG_LEDS_REGULATOR is not set
CONFIG_LEDS_BD2802=m
# CONFIG_LEDS_INTEL_SS4200 is not set
# CONFIG_LEDS_LT3593 is not set
#
# LED Triggers
#
CONFIG_LEDS_TRIGGERS=y
CONFIG_LEDS_TRIGGER_TIMER=m
CONFIG_LEDS_TRIGGER_HEARTBEAT=m
CONFIG_LEDS_TRIGGER_BACKLIGHT=m
CONFIG_LEDS_TRIGGER_GPIO=m
CONFIG_LEDS_TRIGGER_DEFAULT_ON=m
#
# iptables trigger is under Netfilter config (LED target)
#
# CONFIG_ACCESSIBILITY is not set
# CONFIG_INFINIBAND is not set
CONFIG_EDAC=y
#
# Reporting subsystems
#
# CONFIG_EDAC_DEBUG is not set
CONFIG_EDAC_DECODE_MCE=m
CONFIG_EDAC_MM_EDAC=m
CONFIG_EDAC_AMD64=m
# CONFIG_EDAC_AMD64_ERROR_INJECTION is not set
CONFIG_EDAC_E752X=m
CONFIG_EDAC_I82975X=m
CONFIG_EDAC_I3000=m
CONFIG_EDAC_I3200=m
CONFIG_EDAC_X38=m
CONFIG_EDAC_I5400=m
CONFIG_EDAC_I5000=m
CONFIG_EDAC_I5100=m
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
# CONFIG_RTC_DEBUG is not set
#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
CONFIG_RTC_INTF_DEV_UIE_EMUL=y
CONFIG_RTC_DRV_TEST=m
#
# I2C RTC drivers
#
CONFIG_RTC_DRV_DS1307=m
CONFIG_RTC_DRV_DS1374=m
CONFIG_RTC_DRV_DS1672=m
CONFIG_RTC_DRV_MAX6900=m
CONFIG_RTC_DRV_RS5C372=m
CONFIG_RTC_DRV_ISL1208=m
CONFIG_RTC_DRV_X1205=m
CONFIG_RTC_DRV_PCF8563=m
CONFIG_RTC_DRV_PCF8583=m
CONFIG_RTC_DRV_M41T80=m
CONFIG_RTC_DRV_M41T80_WDT=y
# CONFIG_RTC_DRV_BQ32K is not set
CONFIG_RTC_DRV_TWL4030=m
CONFIG_RTC_DRV_S35390A=m
CONFIG_RTC_DRV_FM3130=m
CONFIG_RTC_DRV_RX8581=m
CONFIG_RTC_DRV_RX8025=m
#
# SPI RTC drivers
#
CONFIG_RTC_DRV_M41T94=m
CONFIG_RTC_DRV_DS1305=m
CONFIG_RTC_DRV_DS1390=m
CONFIG_RTC_DRV_MAX6902=m
CONFIG_RTC_DRV_R9701=m
CONFIG_RTC_DRV_RS5C348=m
CONFIG_RTC_DRV_DS3234=m
CONFIG_RTC_DRV_PCF2123=m
#
# Platform RTC drivers
#
CONFIG_RTC_DRV_CMOS=y
CONFIG_RTC_DRV_DS1286=m
CONFIG_RTC_DRV_DS1511=m
CONFIG_RTC_DRV_DS1553=m
CONFIG_RTC_DRV_DS1742=m
CONFIG_RTC_DRV_STK17TA8=m
CONFIG_RTC_DRV_M48T86=m
CONFIG_RTC_DRV_M48T35=m
CONFIG_RTC_DRV_M48T59=m
# CONFIG_RTC_DRV_MSM6242 is not set
CONFIG_RTC_DRV_BQ4802=m
# CONFIG_RTC_DRV_RP5C01 is not set
CONFIG_RTC_DRV_V3020=m
CONFIG_RTC_DRV_WM8350=m
CONFIG_RTC_DRV_PCF50633=m
CONFIG_RTC_DRV_AB3100=m
#
# on-CPU RTC drivers
#
# CONFIG_RTC_DRV_MC13783 is not set
# CONFIG_DMADEVICES is not set
# CONFIG_AUXDISPLAY is not set
CONFIG_UIO=m
CONFIG_UIO_CIF=m
CONFIG_UIO_PDRV=m
CONFIG_UIO_PDRV_GENIRQ=m
CONFIG_UIO_SMX=m
CONFIG_UIO_AEC=m
CONFIG_UIO_SERCOS3=m
CONFIG_UIO_PCI_GENERIC=m
#
# TI VLYNQ
#
CONFIG_STAGING=y
CONFIG_STAGING_EXCLUDE_BUILD=y
# CONFIG_X86_PLATFORM_DEVICES is not set
#
# Firmware Drivers
#
CONFIG_EDD=y
CONFIG_EDD_OFF=y
CONFIG_FIRMWARE_MEMMAP=y
CONFIG_EFI_VARS=y
CONFIG_DELL_RBU=m
CONFIG_DCDBAS=m
CONFIG_DMIID=y
CONFIG_ISCSI_IBFT_FIND=y
CONFIG_ISCSI_IBFT=m
#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_FS=y
# CONFIG_EXT3_DEFAULTS_TO_ORDERED is not set
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_EXT4_FS=y
CONFIG_EXT4_FS_XATTR=y
CONFIG_EXT4_FS_POSIX_ACL=y
CONFIG_EXT4_FS_SECURITY=y
# CONFIG_EXT4_DEBUG is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_JBD2=y
# CONFIG_JBD2_DEBUG is not set
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=m
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
CONFIG_REISERFS_FS_XATTR=y
CONFIG_REISERFS_FS_POSIX_ACL=y
CONFIG_REISERFS_FS_SECURITY=y
CONFIG_JFS_FS=m
CONFIG_JFS_POSIX_ACL=y
CONFIG_JFS_SECURITY=y
# CONFIG_JFS_DEBUG is not set
CONFIG_JFS_STATISTICS=y
CONFIG_FS_POSIX_ACL=y
CONFIG_XFS_FS=m
CONFIG_XFS_QUOTA=y
CONFIG_XFS_POSIX_ACL=y
CONFIG_XFS_RT=y
# CONFIG_XFS_DEBUG is not set
CONFIG_GFS2_FS=m
CONFIG_GFS2_FS_LOCKING_DLM=y
CONFIG_OCFS2_FS=m
CONFIG_OCFS2_FS_O2CB=m
CONFIG_OCFS2_FS_USERSPACE_CLUSTER=m
CONFIG_OCFS2_FS_STATS=y
CONFIG_OCFS2_DEBUG_MASKLOG=y
# CONFIG_OCFS2_DEBUG_FS is not set
CONFIG_BTRFS_FS=m
CONFIG_BTRFS_FS_POSIX_ACL=y
CONFIG_NILFS2_FS=m
CONFIG_FILE_LOCKING=y
CONFIG_FSNOTIFY=y
CONFIG_DNOTIFY=y
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
CONFIG_QUOTA=y
CONFIG_QUOTA_NETLINK_INTERFACE=y
# CONFIG_PRINT_QUOTA_WARNING is not set
CONFIG_QUOTA_TREE=m
CONFIG_QFMT_V1=m
CONFIG_QFMT_V2=m
CONFIG_QUOTACTL=y
CONFIG_AUTOFS_FS=m
CONFIG_AUTOFS4_FS=m
CONFIG_FUSE_FS=y
CONFIG_CUSE=m
CONFIG_GENERIC_ACL=y
#
# Caches
#
CONFIG_FSCACHE=m
# CONFIG_FSCACHE_STATS is not set
# CONFIG_FSCACHE_HISTOGRAM is not set
# CONFIG_FSCACHE_DEBUG is not set
# CONFIG_FSCACHE_OBJECT_LIST is not set
CONFIG_CACHEFILES=m
# CONFIG_CACHEFILES_DEBUG is not set
# CONFIG_CACHEFILES_HISTOGRAM is not set
#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_UDF_FS=m
CONFIG_UDF_NLS=y
#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
CONFIG_NTFS_FS=m
# CONFIG_NTFS_DEBUG is not set
# CONFIG_NTFS_RW is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_VMCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
CONFIG_CONFIGFS_FS=m
CONFIG_MISC_FILESYSTEMS=y
CONFIG_ADFS_FS=m
# CONFIG_ADFS_FS_RW is not set
CONFIG_AFFS_FS=m
CONFIG_ECRYPT_FS=y
CONFIG_HFS_FS=m
CONFIG_HFSPLUS_FS=m
CONFIG_BEFS_FS=m
# CONFIG_BEFS_DEBUG is not set
CONFIG_BFS_FS=m
CONFIG_EFS_FS=m
CONFIG_JFFS2_FS=m
CONFIG_JFFS2_FS_DEBUG=0
CONFIG_JFFS2_FS_WRITEBUFFER=y
# CONFIG_JFFS2_FS_WBUF_VERIFY is not set
# CONFIG_JFFS2_SUMMARY is not set
# CONFIG_JFFS2_FS_XATTR is not set
CONFIG_JFFS2_COMPRESSION_OPTIONS=y
CONFIG_JFFS2_ZLIB=y
CONFIG_JFFS2_LZO=y
CONFIG_JFFS2_RTIME=y
# CONFIG_JFFS2_RUBIN is not set
# CONFIG_JFFS2_CMODE_NONE is not set
# CONFIG_JFFS2_CMODE_PRIORITY is not set
# CONFIG_JFFS2_CMODE_SIZE is not set
CONFIG_JFFS2_CMODE_FAVOURLZO=y
CONFIG_UBIFS_FS=m
CONFIG_UBIFS_FS_XATTR=y
# CONFIG_UBIFS_FS_ADVANCED_COMPR is not set
CONFIG_UBIFS_FS_LZO=y
CONFIG_UBIFS_FS_ZLIB=y
# CONFIG_UBIFS_FS_DEBUG is not set
CONFIG_CRAMFS=m
CONFIG_SQUASHFS=m
# CONFIG_SQUASHFS_EMBEDDED is not set
CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE=3
CONFIG_VXFS_FS=m
CONFIG_MINIX_FS=m
CONFIG_OMFS_FS=m
CONFIG_HPFS_FS=m
CONFIG_QNX4FS_FS=m
CONFIG_ROMFS_FS=m
CONFIG_ROMFS_BACKED_BY_BLOCK=y
# CONFIG_ROMFS_BACKED_BY_MTD is not set
# CONFIG_ROMFS_BACKED_BY_BOTH is not set
CONFIG_ROMFS_ON_BLOCK=y
CONFIG_SYSV_FS=m
CONFIG_UFS_FS=m
# CONFIG_UFS_FS_WRITE is not set
# CONFIG_UFS_DEBUG is not set
CONFIG_EXOFS_FS=m
# CONFIG_EXOFS_DEBUG is not set
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
# CONFIG_NFS_V4_1 is not set
# CONFIG_NFS_FSCACHE is not set
CONFIG_NFSD=m
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFSD_V4=y
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=m
CONFIG_NFS_ACL_SUPPORT=m
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=m
CONFIG_SUNRPC_GSS=m
CONFIG_RPCSEC_GSS_KRB5=m
CONFIG_RPCSEC_GSS_SPKM3=m
CONFIG_SMB_FS=m
# CONFIG_SMB_NLS_DEFAULT is not set
CONFIG_CIFS=m
# CONFIG_CIFS_STATS is not set
CONFIG_CIFS_WEAK_PW_HASH=y
CONFIG_CIFS_UPCALL=y
CONFIG_CIFS_XATTR=y
CONFIG_CIFS_POSIX=y
# CONFIG_CIFS_DEBUG2 is not set
CONFIG_CIFS_DFS_UPCALL=y
CONFIG_CIFS_EXPERIMENTAL=y
CONFIG_NCP_FS=m
CONFIG_NCPFS_PACKET_SIGNING=y
CONFIG_NCPFS_IOCTL_LOCKING=y
CONFIG_NCPFS_STRONG=y
CONFIG_NCPFS_NFS_NS=y
CONFIG_NCPFS_OS2_NS=y
# CONFIG_NCPFS_SMALLDOS is not set
CONFIG_NCPFS_NLS=y
CONFIG_NCPFS_EXTRAS=y
CONFIG_CODA_FS=m
CONFIG_AFS_FS=m
# CONFIG_AFS_DEBUG is not set
# CONFIG_AFS_FSCACHE is not set
#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
CONFIG_ACORN_PARTITION=y
# CONFIG_ACORN_PARTITION_CUMANA is not set
# CONFIG_ACORN_PARTITION_EESOX is not set
CONFIG_ACORN_PARTITION_ICS=y
# CONFIG_ACORN_PARTITION_ADFS is not set
# CONFIG_ACORN_PARTITION_POWERTEC is not set
CONFIG_ACORN_PARTITION_RISCIX=y
CONFIG_OSF_PARTITION=y
CONFIG_AMIGA_PARTITION=y
CONFIG_ATARI_PARTITION=y
CONFIG_MAC_PARTITION=y
CONFIG_MSDOS_PARTITION=y
CONFIG_BSD_DISKLABEL=y
CONFIG_MINIX_SUBPARTITION=y
CONFIG_SOLARIS_X86_PARTITION=y
CONFIG_UNIXWARE_DISKLABEL=y
CONFIG_LDM_PARTITION=y
# CONFIG_LDM_DEBUG is not set
CONFIG_SGI_PARTITION=y
CONFIG_ULTRIX_PARTITION=y
CONFIG_SUN_PARTITION=y
CONFIG_KARMA_PARTITION=y
CONFIG_EFI_PARTITION=y
CONFIG_SYSV68_PARTITION=y
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="cp437"
CONFIG_NLS_CODEPAGE_437=m
CONFIG_NLS_CODEPAGE_737=m
CONFIG_NLS_CODEPAGE_775=m
CONFIG_NLS_CODEPAGE_850=m
CONFIG_NLS_CODEPAGE_852=m
CONFIG_NLS_CODEPAGE_855=m
CONFIG_NLS_CODEPAGE_857=m
CONFIG_NLS_CODEPAGE_860=m
CONFIG_NLS_CODEPAGE_861=m
CONFIG_NLS_CODEPAGE_862=m
CONFIG_NLS_CODEPAGE_863=m
CONFIG_NLS_CODEPAGE_864=m
CONFIG_NLS_CODEPAGE_865=m
CONFIG_NLS_CODEPAGE_866=m
CONFIG_NLS_CODEPAGE_869=m
CONFIG_NLS_CODEPAGE_936=m
CONFIG_NLS_CODEPAGE_950=m
CONFIG_NLS_CODEPAGE_932=m
CONFIG_NLS_CODEPAGE_949=m
CONFIG_NLS_CODEPAGE_874=m
CONFIG_NLS_ISO8859_8=m
CONFIG_NLS_CODEPAGE_1250=m
CONFIG_NLS_CODEPAGE_1251=m
CONFIG_NLS_ASCII=m
CONFIG_NLS_ISO8859_1=m
CONFIG_NLS_ISO8859_2=m
CONFIG_NLS_ISO8859_3=m
CONFIG_NLS_ISO8859_4=m
CONFIG_NLS_ISO8859_5=m
CONFIG_NLS_ISO8859_6=m
CONFIG_NLS_ISO8859_7=m
CONFIG_NLS_ISO8859_9=m
CONFIG_NLS_ISO8859_13=m
CONFIG_NLS_ISO8859_14=m
CONFIG_NLS_ISO8859_15=m
CONFIG_NLS_KOI8_R=m
CONFIG_NLS_KOI8_U=m
CONFIG_NLS_UTF8=m
CONFIG_DLM=m
# CONFIG_DLM_DEBUG is not set
#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_PRINTK_TIME=y
# CONFIG_ENABLE_WARN_DEPRECATED is not set
# CONFIG_ENABLE_MUST_CHECK is not set
CONFIG_FRAME_WARN=1024
CONFIG_MAGIC_SYSRQ=y
# CONFIG_STRIP_ASM_SYMS is not set
CONFIG_UNUSED_SYMBOLS=y
CONFIG_DEBUG_FS=y
# CONFIG_HEADERS_CHECK is not set
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SHIRQ is not set
CONFIG_DETECT_SOFTLOCKUP=y
# CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC is not set
CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=0
CONFIG_DETECT_HUNG_TASK=y
# CONFIG_BOOTPARAM_HUNG_TASK_PANIC is not set
CONFIG_BOOTPARAM_HUNG_TASK_PANIC_VALUE=0
CONFIG_SCHED_DEBUG=y
CONFIG_SCHEDSTATS=y
CONFIG_TIMER_STATS=y
# CONFIG_DEBUG_OBJECTS is not set
# CONFIG_SLUB_DEBUG_ON is not set
# CONFIG_SLUB_STATS is not set
# CONFIG_DEBUG_KMEMLEAK is not set
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_MUTEXES is not set
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_PROVE_LOCKING is not set
# CONFIG_LOCK_STAT is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
CONFIG_STACKTRACE=y
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_DEBUG_INFO=y
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_VIRTUAL is not set
# CONFIG_DEBUG_WRITECOUNT is not set
CONFIG_DEBUG_MEMORY_INIT=y
# CONFIG_DEBUG_LIST is not set
# CONFIG_DEBUG_SG is not set
# CONFIG_DEBUG_NOTIFIERS is not set
# CONFIG_DEBUG_CREDENTIALS is not set
CONFIG_ARCH_WANT_FRAME_POINTERS=y
CONFIG_FRAME_POINTER=y
# CONFIG_BOOT_PRINTK_DELAY is not set
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_RCU_CPU_STALL_DETECTOR is not set
# CONFIG_BACKTRACE_SELF_TEST is not set
# CONFIG_DEBUG_BLOCK_EXT_DEVT is not set
# CONFIG_DEBUG_FORCE_WEAK_PER_CPU is not set
# CONFIG_FAULT_INJECTION is not set
CONFIG_LATENCYTOP=y
CONFIG_SYSCTL_SYSCALL_CHECK=y
# CONFIG_DEBUG_PAGEALLOC is not set
CONFIG_USER_STACKTRACE_SUPPORT=y
CONFIG_NOP_TRACER=y
CONFIG_HAVE_FUNCTION_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_FP_TEST=y
CONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=y
CONFIG_HAVE_DYNAMIC_FTRACE=y
CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y
CONFIG_HAVE_SYSCALL_TRACEPOINTS=y
CONFIG_RING_BUFFER=y
CONFIG_EVENT_TRACING=y
CONFIG_CONTEXT_SWITCH_TRACER=y
CONFIG_RING_BUFFER_ALLOW_SWAP=y
CONFIG_TRACING=y
CONFIG_GENERIC_TRACER=y
CONFIG_TRACING_SUPPORT=y
CONFIG_FTRACE=y
# CONFIG_FUNCTION_TRACER is not set
# CONFIG_IRQSOFF_TRACER is not set
# CONFIG_SYSPROF_TRACER is not set
# CONFIG_SCHED_TRACER is not set
# CONFIG_FTRACE_SYSCALLS is not set
# CONFIG_BOOT_TRACER is not set
CONFIG_BRANCH_PROFILE_NONE=y
# CONFIG_PROFILE_ANNOTATED_BRANCHES is not set
# CONFIG_PROFILE_ALL_BRANCHES is not set
# CONFIG_POWER_TRACER is not set
# CONFIG_KSYM_TRACER is not set
# CONFIG_STACK_TRACER is not set
# CONFIG_KMEMTRACE is not set
# CONFIG_WORKQUEUE_TRACER is not set
CONFIG_BLK_DEV_IO_TRACE=y
# CONFIG_FTRACE_STARTUP_TEST is not set
# CONFIG_MMIOTRACE is not set
# CONFIG_RING_BUFFER_BENCHMARK is not set
# CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set
# CONFIG_FIREWIRE_OHCI_REMOTE_DMA is not set
# CONFIG_DYNAMIC_DEBUG is not set
# CONFIG_DMA_API_DEBUG is not set
# CONFIG_SAMPLES is not set
CONFIG_HAVE_ARCH_KGDB=y
CONFIG_KGDB=y
CONFIG_KGDB_SERIAL_CONSOLE=y
# CONFIG_KGDB_TESTS is not set
CONFIG_HAVE_ARCH_KMEMCHECK=y
CONFIG_STRICT_DEVMEM=y
# CONFIG_X86_VERBOSE_BOOTUP is not set
CONFIG_EARLY_PRINTK=y
# CONFIG_EARLY_PRINTK_DBGP is not set
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_PER_CPU_MAPS is not set
# CONFIG_X86_PTDUMP is not set
CONFIG_DEBUG_RODATA=y
# CONFIG_DEBUG_RODATA_TEST is not set
# CONFIG_DEBUG_NX_TEST is not set
# CONFIG_IOMMU_DEBUG is not set
# CONFIG_IOMMU_STRESS is not set
CONFIG_HAVE_MMIOTRACE_SUPPORT=y
CONFIG_IO_DELAY_TYPE_0X80=0
CONFIG_IO_DELAY_TYPE_0XED=1
CONFIG_IO_DELAY_TYPE_UDELAY=2
CONFIG_IO_DELAY_TYPE_NONE=3
# CONFIG_IO_DELAY_0X80 is not set
CONFIG_IO_DELAY_0XED=y
# CONFIG_IO_DELAY_UDELAY is not set
# CONFIG_IO_DELAY_NONE is not set
CONFIG_DEFAULT_IO_DELAY_TYPE=1
# CONFIG_DEBUG_BOOT_PARAMS is not set
# CONFIG_CPA_DEBUG is not set
CONFIG_OPTIMIZE_INLINING=y
# CONFIG_DEBUG_STRICT_USER_COPY_CHECKS is not set
#
# Security options
#
CONFIG_KEYS=y
# CONFIG_KEYS_DEBUG_PROC_KEYS is not set
CONFIG_SECURITY=y
CONFIG_SECURITYFS=y
CONFIG_SECURITY_NETWORK=y
# CONFIG_SECURITY_NETWORK_XFRM is not set
CONFIG_SECURITY_PATH=y
CONFIG_SECURITY_SMACK=y
CONFIG_SECURITY_TOMOYO=y
# CONFIG_IMA is not set
# CONFIG_DEFAULT_SECURITY_SELINUX is not set
CONFIG_DEFAULT_SECURITY_SMACK=y
# CONFIG_DEFAULT_SECURITY_TOMOYO is not set
# CONFIG_DEFAULT_SECURITY_DAC is not set
CONFIG_DEFAULT_SECURITY="smack"
CONFIG_XOR_BLOCKS=m
CONFIG_ASYNC_CORE=m
CONFIG_ASYNC_MEMCPY=m
CONFIG_ASYNC_XOR=m
CONFIG_ASYNC_PQ=m
CONFIG_ASYNC_RAID6_RECOV=m
CONFIG_CRYPTO=y
#
# Crypto core or helper
#
CONFIG_CRYPTO_FIPS=y
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ALGAPI2=y
CONFIG_CRYPTO_AEAD=m
CONFIG_CRYPTO_AEAD2=y
CONFIG_CRYPTO_BLKCIPHER=y
CONFIG_CRYPTO_BLKCIPHER2=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_HASH2=y
CONFIG_CRYPTO_RNG=m
CONFIG_CRYPTO_RNG2=y
CONFIG_CRYPTO_PCOMP=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_MANAGER2=y
CONFIG_CRYPTO_GF128MUL=m
CONFIG_CRYPTO_NULL=m
CONFIG_CRYPTO_WORKQUEUE=y
CONFIG_CRYPTO_CRYPTD=m
CONFIG_CRYPTO_AUTHENC=m
CONFIG_CRYPTO_TEST=m
#
# Authenticated Encryption with Associated Data
#
CONFIG_CRYPTO_CCM=m
CONFIG_CRYPTO_GCM=m
CONFIG_CRYPTO_SEQIV=m
#
# Block modes
#
CONFIG_CRYPTO_CBC=y
CONFIG_CRYPTO_CTR=m
CONFIG_CRYPTO_CTS=m
CONFIG_CRYPTO_ECB=y
CONFIG_CRYPTO_LRW=m
CONFIG_CRYPTO_PCBC=m
CONFIG_CRYPTO_XTS=m
CONFIG_CRYPTO_FPU=m
#
# Hash modes
#
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_XCBC=m
CONFIG_CRYPTO_VMAC=m
#
# Digest
#
CONFIG_CRYPTO_CRC32C=m
CONFIG_CRYPTO_CRC32C_INTEL=m
CONFIG_CRYPTO_GHASH=m
CONFIG_CRYPTO_MD4=m
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_MICHAEL_MIC=m
CONFIG_CRYPTO_RMD128=m
CONFIG_CRYPTO_RMD160=m
CONFIG_CRYPTO_RMD256=m
CONFIG_CRYPTO_RMD320=m
CONFIG_CRYPTO_SHA1=m
CONFIG_CRYPTO_SHA256=m
CONFIG_CRYPTO_SHA512=m
CONFIG_CRYPTO_TGR192=m
CONFIG_CRYPTO_WP512=m
# CONFIG_CRYPTO_GHASH_CLMUL_NI_INTEL is not set
#
# Ciphers
#
CONFIG_CRYPTO_AES=m
CONFIG_CRYPTO_AES_X86_64=m
CONFIG_CRYPTO_AES_NI_INTEL=m
CONFIG_CRYPTO_ANUBIS=m
CONFIG_CRYPTO_ARC4=m
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_CAMELLIA=m
CONFIG_CRYPTO_CAST5=m
CONFIG_CRYPTO_CAST6=m
CONFIG_CRYPTO_DES=m
CONFIG_CRYPTO_FCRYPT=m
CONFIG_CRYPTO_KHAZAD=m
CONFIG_CRYPTO_SALSA20=m
CONFIG_CRYPTO_SALSA20_X86_64=m
CONFIG_CRYPTO_SEED=m
CONFIG_CRYPTO_SERPENT=m
CONFIG_CRYPTO_TEA=m
CONFIG_CRYPTO_TWOFISH=m
CONFIG_CRYPTO_TWOFISH_COMMON=m
CONFIG_CRYPTO_TWOFISH_X86_64=m
#
# Compression
#
CONFIG_CRYPTO_DEFLATE=m
CONFIG_CRYPTO_ZLIB=m
CONFIG_CRYPTO_LZO=m
#
# Random Number Generation
#
CONFIG_CRYPTO_ANSI_CPRNG=m
CONFIG_CRYPTO_HW=y
CONFIG_CRYPTO_DEV_PADLOCK=y
CONFIG_CRYPTO_DEV_PADLOCK_AES=m
CONFIG_CRYPTO_DEV_PADLOCK_SHA=m
CONFIG_CRYPTO_DEV_HIFN_795X=m
CONFIG_CRYPTO_DEV_HIFN_795X_RNG=y
CONFIG_HAVE_KVM=y
# CONFIG_VIRTUALIZATION is not set
CONFIG_BINARY_PRINTF=y
#
# Library routines
#
CONFIG_BITREVERSE=y
CONFIG_GENERIC_FIND_FIRST_BIT=y
CONFIG_GENERIC_FIND_NEXT_BIT=y
CONFIG_GENERIC_FIND_LAST_BIT=y
CONFIG_CRC_CCITT=m
CONFIG_CRC16=y
CONFIG_CRC_T10DIF=y
CONFIG_CRC_ITU_T=m
CONFIG_CRC32=y
CONFIG_CRC7=m
CONFIG_LIBCRC32C=m
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=m
CONFIG_LZO_COMPRESS=m
CONFIG_LZO_DECOMPRESS=y
CONFIG_DECOMPRESS_GZIP=y
CONFIG_DECOMPRESS_BZIP2=y
CONFIG_DECOMPRESS_LZMA=y
CONFIG_DECOMPRESS_LZO=y
CONFIG_REED_SOLOMON=m
CONFIG_REED_SOLOMON_DEC16=y
CONFIG_TEXTSEARCH=y
CONFIG_TEXTSEARCH_KMP=m
CONFIG_TEXTSEARCH_BM=m
CONFIG_TEXTSEARCH_FSM=m
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y
CONFIG_CHECK_SIGNATURE=y
CONFIG_NLATTR=y
[-- Attachment #3: dmesg --]
[-- Type: text/plain, Size: 61488 bytes --]
[ 0.000000] Linux version 2.6.33-rc6 (root@korrek) (gcc version 4.4.3 (Ubuntu 4.4.3-1ubuntu2) ) #25 SMP Mon Feb 1 13:29:32 CST 2010
[ 0.000000] Command line: root=UUID=0671ec67-a417-4716-b4c8-90ef225e524d ro quiet splash usbcore.autosuspend=1 clocksource=hpet
[ 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 - 00000000bf790000 (usable)
[ 0.000000] BIOS-e820: 00000000bf790000 - 00000000bf79e000 (ACPI data)
[ 0.000000] BIOS-e820: 00000000bf79e000 - 00000000bf7d0000 (ACPI NVS)
[ 0.000000] BIOS-e820: 00000000bf7d0000 - 00000000bf7e0000 (reserved)
[ 0.000000] BIOS-e820: 00000000bf7ec000 - 00000000c0000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
[ 0.000000] BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
[ 0.000000] BIOS-e820: 0000000100000000 - 0000000340000000 (usable)
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] DMI present.
[ 0.000000] No AGP bridge found
[ 0.000000] last_pfn = 0x340000 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-DFFFF uncachable
[ 0.000000] E0000-E3FFF write-protect
[ 0.000000] E4000-E7FFF write-through
[ 0.000000] E8000-EBFFF write-protect
[ 0.000000] EC000-EFFFF write-through
[ 0.000000] F0000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 000000000 mask E00000000 write-back
[ 0.000000] 1 base 200000000 mask F00000000 write-back
[ 0.000000] 2 base 300000000 mask FC0000000 write-back
[ 0.000000] 3 base 0C0000000 mask FC0000000 uncachable
[ 0.000000] 4 base 0BF800000 mask FFF800000 uncachable
[ 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] e820 update range: 00000000bf800000 - 0000000100000000 (usable) ==> (reserved)
[ 0.000000] last_pfn = 0xbf790 max_arch_pfn = 0x400000000
[ 0.000000] e820 update range: 0000000000001000 - 0000000000010000 (usable) ==> (reserved)
[ 0.000000] Scanning 1 areas for low memory corruption
[ 0.000000] modified physical RAM map:
[ 0.000000] modified: 0000000000000000 - 0000000000001000 (usable)
[ 0.000000] modified: 0000000000001000 - 0000000000010000 (reserved)
[ 0.000000] modified: 0000000000010000 - 000000000009fc00 (usable)
[ 0.000000] modified: 000000000009fc00 - 00000000000a0000 (reserved)
[ 0.000000] modified: 00000000000e0000 - 0000000000100000 (reserved)
[ 0.000000] modified: 0000000000100000 - 00000000bf790000 (usable)
[ 0.000000] modified: 00000000bf790000 - 00000000bf79e000 (ACPI data)
[ 0.000000] modified: 00000000bf79e000 - 00000000bf7d0000 (ACPI NVS)
[ 0.000000] modified: 00000000bf7d0000 - 00000000bf7e0000 (reserved)
[ 0.000000] modified: 00000000bf7ec000 - 00000000c0000000 (reserved)
[ 0.000000] modified: 00000000fee00000 - 00000000fee01000 (reserved)
[ 0.000000] modified: 00000000ffb00000 - 0000000100000000 (reserved)
[ 0.000000] modified: 0000000100000000 - 0000000340000000 (usable)
[ 0.000000] initial memory mapped : 0 - 20000000
[ 0.000000] found SMP MP-table at [ffff8800000ff780] ff780
[ 0.000000] init_memory_mapping: 0000000000000000-00000000bf790000
[ 0.000000] 0000000000 - 00bf600000 page 2M
[ 0.000000] 00bf600000 - 00bf790000 page 4k
[ 0.000000] kernel direct mapping tables up to bf790000 @ 16000-1b000
[ 0.000000] init_memory_mapping: 0000000100000000-0000000340000000
[ 0.000000] 0100000000 - 0340000000 page 2M
[ 0.000000] kernel direct mapping tables up to 340000000 @ 19000-27000
[ 0.000000] RAMDISK: 34bca000 - 37fefafd
[ 0.000000] ACPI: RSDP 00000000000f9ce0 00014 (v00 ACPIAM)
[ 0.000000] ACPI: RSDT 00000000bf790000 00044 (v01 DELL FX09 20090415 MSFT 00000097)
[ 0.000000] ACPI: FACP 00000000bf790200 00084 (v01 DELL FX09 20090415 MSFT 00000097)
[ 0.000000] ACPI: DSDT 00000000bf790660 056A7 (v01 1AAAA 1AAAA000 00000000 INTL 20051117)
[ 0.000000] ACPI: FACS 00000000bf79e000 00040
[ 0.000000] ACPI: APIC 00000000bf790390 0008C (v01 DELL FX09 20090415 MSFT 00000097)
[ 0.000000] ACPI: MCFG 00000000bf790420 0003C (v01 DELL OEMMCFG 20090415 MSFT 00000097)
[ 0.000000] ACPI: SLIC 00000000bf790460 00176 (v01 DELL FX09 20090415 MSFT 00000097)
[ 0.000000] ACPI: OSFR 00000000bf7905e0 00080 (v01 DELL FX09 20090415 MSFT 00000097)
[ 0.000000] ACPI: OEMB 00000000bf79e040 00072 (v01 DELL FX09 20090415 MSFT 00000097)
[ 0.000000] ACPI: HPET 00000000bf798660 00038 (v01 DELL OEMHPET 20090415 MSFT 00000097)
[ 0.000000] ACPI: SSDT 00000000bf7a08f0 01298 (v01 DpgPmm CpuPm 00000012 INTL 20051117)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] No NUMA configuration found
[ 0.000000] Faking a node at 0000000000000000-0000000340000000
[ 0.000000] Bootmem setup node 0 0000000000000000-0000000340000000
[ 0.000000] NODE_DATA [0000000000022000 - 0000000000026fff]
[ 0.000000] bootmap [0000000000027000 - 000000000008efff] pages 68
[ 0.000000] (13 early reservations) ==> bootmem [0000000000 - 0340000000]
[ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
[ 0.000000] #1 [0001000000 - 00017e8698] TEXT DATA BSS ==> [0001000000 - 00017e8698]
[ 0.000000] #2 [0034bca000 - 0037fefafd] RAMDISK ==> [0034bca000 - 0037fefafd]
[ 0.000000] #3 [00017e9000 - 00017e90fc] BRK ==> [00017e9000 - 00017e90fc]
[ 0.000000] #4 [00000ff790 - 0000100000] BIOS reserved ==> [00000ff790 - 0000100000]
[ 0.000000] #5 [00000ff780 - 00000ff790] MP-table mpf ==> [00000ff780 - 00000ff790]
[ 0.000000] #6 [000009fc00 - 00000fcee0] BIOS reserved ==> [000009fc00 - 00000fcee0]
[ 0.000000] #7 [00000fd074 - 00000ff780] BIOS reserved ==> [00000fd074 - 00000ff780]
[ 0.000000] #8 [00000fcee0 - 00000fd074] MP-table mpc ==> [00000fcee0 - 00000fd074]
[ 0.000000] #9 [0000010000 - 0000012000] TRAMPOLINE ==> [0000010000 - 0000012000]
[ 0.000000] #10 [0000012000 - 0000016000] ACPI WAKEUP ==> [0000012000 - 0000016000]
[ 0.000000] #11 [0000016000 - 0000019000] PGTABLE ==> [0000016000 - 0000019000]
[ 0.000000] #12 [0000019000 - 0000022000] PGTABLE ==> [0000019000 - 0000022000]
[ 0.000000] [ffffea0000000000-ffffea000b5fffff] PMD -> [ffff880028600000-ffff880032dfffff] on node 0
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0x00000000 -> 0x00001000
[ 0.000000] DMA32 0x00001000 -> 0x00100000
[ 0.000000] Normal 0x00100000 -> 0x00340000
[ 0.000000] Movable zone start PFN for each node
[ 0.000000] early_node_map[4] active PFN ranges
[ 0.000000] 0: 0x00000000 -> 0x00000001
[ 0.000000] 0: 0x00000010 -> 0x0000009f
[ 0.000000] 0: 0x00000100 -> 0x000bf790
[ 0.000000] 0: 0x00100000 -> 0x00340000
[ 0.000000] On node 0 totalpages: 3143456
[ 0.000000] DMA zone: 56 pages used for memmap
[ 0.000000] DMA zone: 114 pages reserved
[ 0.000000] DMA zone: 3814 pages, LIFO batch:0
[ 0.000000] DMA32 zone: 14280 pages used for memmap
[ 0.000000] DMA32 zone: 765896 pages, LIFO batch:31
[ 0.000000] Normal zone: 32256 pages used for memmap
[ 0.000000] Normal zone: 2327040 pages, LIFO batch:31
[ 0.000000] ACPI: PM-Timer IO Port: 0x808
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x01] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x03] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x05] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] enabled)
[ 0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 8, 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: 0xffffffff base: 0xfed00000
[ 0.000000] SMP: Allowing 8 CPUs, 0 hotplug CPUs
[ 0.000000] nr_irqs_gsi: 24
[ 0.000000] PM: Registered nosave memory: 0000000000001000 - 0000000000010000
[ 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] PM: Registered nosave memory: 00000000bf790000 - 00000000bf79e000
[ 0.000000] PM: Registered nosave memory: 00000000bf79e000 - 00000000bf7d0000
[ 0.000000] PM: Registered nosave memory: 00000000bf7d0000 - 00000000bf7e0000
[ 0.000000] PM: Registered nosave memory: 00000000bf7e0000 - 00000000bf7ec000
[ 0.000000] PM: Registered nosave memory: 00000000bf7ec000 - 00000000c0000000
[ 0.000000] PM: Registered nosave memory: 00000000c0000000 - 00000000fee00000
[ 0.000000] PM: Registered nosave memory: 00000000fee00000 - 00000000fee01000
[ 0.000000] PM: Registered nosave memory: 00000000fee01000 - 00000000ffb00000
[ 0.000000] PM: Registered nosave memory: 00000000ffb00000 - 0000000100000000
[ 0.000000] Allocating PCI resources starting at c0000000 (gap: c0000000:3ee00000)
[ 0.000000] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:8 nr_node_ids:1
[ 0.000000] PERCPU: Embedded 28 pages/cpu @ffff880028200000 s83608 r8192 d22888 u262144
[ 0.000000] pcpu-alloc: s83608 r8192 d22888 u262144 alloc=1*2097152
[ 0.000000] pcpu-alloc: [0] 0 1 2 3 4 5 6 7
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 3096750
[ 0.000000] Policy zone: Normal
[ 0.000000] Kernel command line: root=UUID=0671ec67-a417-4716-b4c8-90ef225e524d ro quiet splash usbcore.autosuspend=1 clocksource=hpet
[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.000000] Checking aperture...
[ 0.000000] No AGP bridge found
[ 0.000000] Memory: 12273076k/13631488k available (3871k kernel code, 1057664k absent, 300748k reserved, 2809k data, 564k init)
[ 0.000000] SLUB: Genslabs=14, HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] NR_IRQS:4352 nr_irqs:472
[ 0.000000] Console: colour VGA+ 80x25
[ 0.000000] console [tty0] enabled
[ 0.000000] hpet clockevent registered
[ 0.000000] Fast TSC calibration using PIT
[ 0.010000] Detected 2659.815 MHz processor.
[ 0.000003] Calibrating delay loop (skipped), value calculated using timer frequency.. 5319.63 BogoMIPS (lpj=26598150)
[ 0.000018] Security Framework initialized
[ 0.000021] Smack: Initializing.
[ 0.000870] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes)
[ 0.003772] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes)
[ 0.005010] Mount-cache hash table entries: 256
[ 0.005111] CPU: Physical Processor ID: 0
[ 0.005112] CPU: Processor Core ID: 0
[ 0.005117] mce: CPU supports 9 MCE banks
[ 0.005125] CPU0: Thermal monitoring enabled (TM1)
[ 0.005127] CPU 0 MCA banks CMCI:2 CMCI:3 CMCI:5 CMCI:6 CMCI:8
[ 0.005134] using mwait in idle threads.
[ 0.005135] Performance Events: Nehalem/Corei7 events, Intel PMU driver.
[ 0.005139] ... version: 3
[ 0.005140] ... bit width: 48
[ 0.005141] ... generic registers: 4
[ 0.005142] ... value mask: 0000ffffffffffff
[ 0.005143] ... max period: 000000007fffffff
[ 0.005144] ... fixed-purpose events: 3
[ 0.005145] ... event mask: 000000070000000f
[ 0.005159] ACPI: Core revision 20091214
[ 0.034611] Setting APIC routing to flat
[ 0.034927] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.134676] CPU0: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 04
[ 0.278332] APIC calibration not consistent with PM-Timer: 129ms instead of 100ms
[ 0.278334] APIC delta adjusted to PM-Timer: 831248 (1080618)
[ 0.278423] Booting Node 0, Processors #1
[ 0.437950] CPU 1 MCA banks CMCI:2 CMCI:3 CMCI:5 SHD:6 SHD:8
[ 0.458012] #2
[ 0.617495] CPU 2 MCA banks CMCI:2 CMCI:3 CMCI:5 SHD:6 SHD:8
[ 0.637599] #3
[ 0.797042] CPU 3 MCA banks CMCI:2 CMCI:3 CMCI:5 SHD:6 SHD:8
[ 0.817087] #4
[ 0.976588] CPU 4 MCA banks SHD:2 SHD:3 SHD:5 SHD:6 SHD:8
[ 0.996614] #5
[ 1.156132] CPU 5 MCA banks SHD:2 SHD:3 SHD:5 SHD:6 SHD:8
[ 1.176206] #6
[ 1.335678] CPU 6 MCA banks SHD:2 SHD:3 SHD:5 SHD:6 SHD:8
[ 1.355767] #7 Ok.
[ 1.515224] CPU 7 MCA banks SHD:2 SHD:3 SHD:5 SHD:6 SHD:8
[ 1.535243] Brought up 8 CPUs
[ 1.535245] Total of 8 processors activated (42558.96 BogoMIPS).
[ 1.538268] regulator: core version 0.5
[ 1.538291] Time: 16:23:20 Date: 02/05/10
[ 1.538317] NET: Registered protocol family 16
[ 1.538395] ACPI: bus type pci registered
[ 1.538439] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
[ 1.538441] PCI: not using MMCONFIG
[ 1.538442] PCI: Using configuration type 1 for base access
[ 1.539059] bio: create slab <bio-0> at 0
[ 1.540256] ACPI: EC: Look up EC in DSDT
[ 1.542713] ACPI: Executed 1 blocks of module-level executable AML code
[ 1.550005] ACPI: Interpreter enabled
[ 1.550008] ACPI: (supports S0 S3 S4 S5)
[ 1.550026] ACPI: Using IOAPIC for interrupt routing
[ 1.550071] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
[ 1.551899] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in ACPI motherboard resources
[ 1.565083] ACPI: No dock devices found.
[ 1.565234] ACPI: PCI Root Bridge [PCI0] (0000:00)
[ 1.565261] pci_root PNP0A08:00: ignoring host bridge windows from ACPI; boot with "pci=use_crs" to use them
[ 1.565524] pci_root PNP0A08:00: host bridge window [io 0x0000-0x0cf7] (ignored)
[ 1.565526] pci_root PNP0A08:00: host bridge window [io 0x0d00-0xffff] (ignored)
[ 1.565528] pci_root PNP0A08:00: host bridge window [mem 0x000a0000-0x000bffff] (ignored)
[ 1.565530] pci_root PNP0A08:00: host bridge window [mem 0x000d0000-0x000dffff] (ignored)
[ 1.565532] pci_root PNP0A08:00: host bridge window [mem 0xc0000000-0xdfffffff] (ignored)
[ 1.565533] pci_root PNP0A08:00: host bridge window [mem 0xf0000000-0xfed8ffff] (ignored)
[ 1.565535] pci_bus 0000:00: scanning bus
[ 1.565546] pci 0000:00:00.0: found [8086:3400] class 000600 header type 00
[ 1.565574] pci 0000:00:00.0: calling quirk_resource_alignment+0x0/0x19d
[ 1.565577] pci 0000:00:00.0: calling pci_fixup_transparent_bridge+0x0/0x2a
[ 1.565594] pci 0000:00:00.0: PME# supported from D0 D3hot D3cold
[ 1.565596] pci 0000:00:00.0: PME# disabled
[ 1.565618] pci 0000:00:01.0: found [8086:3408] class 000604 header type 01
[ 1.565635] pci 0000:00:01.0: calling quirk_resource_alignment+0x0/0x19d
[ 1.565637] pci 0000:00:01.0: calling pci_fixup_transparent_bridge+0x0/0x2a
[ 1.565657] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
[ 1.565660] pci 0000:00:01.0: PME# disabled
[ 1.565679] pci 0000:00:03.0: found [8086:340a] class 000604 header type 01
[ 1.565696] pci 0000:00:03.0: calling quirk_resource_alignment+0x0/0x19d
[ 1.565698] pci 0000:00:03.0: calling pci_fixup_transparent_bridge+0x0/0x2a
[ 1.565718] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
[ 1.565721] pci 0000:00:03.0: PME# disabled
[ 1.565742] pci 0000:00:07.0: found [8086:340e] class 000604 header type 01
[ 1.565759] pci 0000:00:07.0: calling quirk_resource_alignment+0x0/0x19d
[ 1.565761] pci 0000:00:07.0: calling pci_fixup_transparent_bridge+0x0/0x2a
[ 1.565781] pci 0000:00:07.0: PME# supported from D0 D3hot D3cold
[ 1.565783] pci 0000:00:07.0: PME# disabled
[ 1.565805] pci 0000:00:10.0: found [8086:3425] class 000800 header type 00
[ 1.565831] pci 0000:00:10.0: calling quirk_resource_alignment+0x0/0x19d
[ 1.565833] pci 0000:00:10.0: calling pci_fixup_transparent_bridge+0x0/0x2a
[ 1.565850] pci 0000:00:10.1: found [8086:3426] class 000800 header type 00
[ 1.565874] pci 0000:00:10.1: calling quirk_resource_alignment+0x0/0x19d
[ 1.565877] pci 0000:00:10.1: calling pci_fixup_transparent_bridge+0x0/0x2a
[ 1.565894] pci 0000:00:14.0: found [8086:342e] class 000800 header type 00
[ 1.565918] pci 0000:00:14.0: calling quirk_resource_alignment+0x0/0x19d
[ 1.565920] pci 0000:00:14.0: calling pci_fixup_transparent_bridge+0x0/0x2a
[ 1.565939] pci 0000:00:14.1: found [8086:3422] class 000800 header type 00
[ 1.565963] pci 0000:00:14.1: calling quirk_resource_alignment+0x0/0x19d
[ 1.565965] pci 0000:00:14.1: calling pci_fixup_transparent_bridge+0x0/0x2a
[ 1.565984] pci 0000:00:14.2: found [8086:3423] class 000800 header type 00
[ 1.566008] pci 0000:00:14.2: calling quirk_resource_alignment+0x0/0x19d
[ 1.566010] pci 0000:00:14.2: calling pci_fixup_transparent_bridge+0x0/0x2a
[ 1.566028] pci 0000:00:14.3: found [8086:3438] class 000800 header type 00
[ 1.566052] pci 0000:00:14.3: calling quirk_resource_alignment+0x0/0x19d
[ 1.566054] pci 0000:00:14.3: calling pci_fixup_transparent_bridge+0x0/0x2a
[ 1.566076] pci 0000:00:19.0: found [8086:10cd] class 000200 header type 00
[ 1.566090] pci 0000:00:19.0: reg 10: [mem 0xfbcc0000-0xfbcdffff]
[ 1.566095] pci 0000:00:19.0: reg 14: [mem 0xfbcf4000-0xfbcf4fff]
[ 1.566100] pci 0000:00:19.0: reg 18: [io 0xa080-0xa09f]
[ 1.566118] pci 0000:00:19.0: calling quirk_resource_alignment+0x0/0x19d
[ 1.566120] pci 0000:00:19.0: calling pci_fixup_transparent_bridge+0x0/0x2a
[ 1.566138] pci 0000:00:19.0: PME# supported from D0 D3hot D3cold
[ 1.566141] pci 0000:00:19.0: PME# disabled
[ 1.566158] pci 0000:00:1a.0: found [8086:3a37] class 000c03 header type 00
[ 1.566183] pci 0000:00:1a.0: reg 20: [io 0xa400-0xa41f]
[ 1.566195] pci 0000:00:1a.0: calling quirk_resource_alignment+0x0/0x19d
[ 1.566197] pci 0000:00:1a.0: calling pci_fixup_transparent_bridge+0x0/0x2a
[ 1.566221] pci 0000:00:1a.1: found [8086:3a38] class 000c03 header type 00
[ 1.566247] pci 0000:00:1a.1: reg 20: [io 0xa480-0xa49f]
[ 1.566258] pci 0000:00:1a.1: calling quirk_resource_alignment+0x0/0x19d
[ 1.566260] pci 0000:00:1a.1: calling pci_fixup_transparent_bridge+0x0/0x2a
[ 1.566285] pci 0000:00:1a.2: found [8086:3a39] class 000c03 header type 00
[ 1.566310] pci 0000:00:1a.2: reg 20: [io 0xa800-0xa81f]
[ 1.566322] pci 0000:00:1a.2: calling quirk_resource_alignment+0x0/0x19d
[ 1.566324] pci 0000:00:1a.2: calling pci_fixup_transparent_bridge+0x0/0x2a
[ 1.566357] pci 0000:00:1a.7: found [8086:3a3c] class 000c03 header type 00
[ 1.566373] pci 0000:00:1a.7: reg 10: [mem 0xfbcf6000-0xfbcf63ff]
[ 1.566402] pci 0000:00:1a.7: calling quirk_resource_alignment+0x0/0x19d
[ 1.566404] pci 0000:00:1a.7: calling pci_fixup_transparent_bridge+0x0/0x2a
[ 1.566426] pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
[ 1.566430] pci 0000:00:1a.7: PME# disabled
[ 1.566450] pci 0000:00:1b.0: found [8086:3a3e] class 000403 header type 00
[ 1.566461] pci 0000:00:1b.0: reg 10: [mem 0xfbcf8000-0xfbcfbfff 64bit]
[ 1.566482] pci 0000:00:1b.0: calling quirk_resource_alignment+0x0/0x19d
[ 1.566484] pci 0000:00:1b.0: calling pci_fixup_transparent_bridge+0x0/0x2a
[ 1.566502] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 1.566505] pci 0000:00:1b.0: PME# disabled
[ 1.566522] pci 0000:00:1c.0: found [8086:3a40] class 000604 header type 01
[ 1.566546] pci 0000:00:1c.0: calling quirk_resource_alignment+0x0/0x19d
[ 1.566548] pci 0000:00:1c.0: calling pci_fixup_transparent_bridge+0x0/0x2a
[ 1.566569] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[ 1.566572] pci 0000:00:1c.0: PME# disabled
[ 1.566591] pci 0000:00:1c.1: found [8086:3a42] class 000604 header type 01
[ 1.566615] pci 0000:00:1c.1: calling quirk_resource_alignment+0x0/0x19d
[ 1.566617] pci 0000:00:1c.1: calling pci_fixup_transparent_bridge+0x0/0x2a
[ 1.566638] pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
[ 1.566641] pci 0000:00:1c.1: PME# disabled
[ 1.566665] pci 0000:00:1d.0: found [8086:3a34] class 000c03 header type 00
[ 1.566691] pci 0000:00:1d.0: reg 20: [io 0xa880-0xa89f]
[ 1.566702] pci 0000:00:1d.0: calling quirk_resource_alignment+0x0/0x19d
[ 1.566704] pci 0000:00:1d.0: calling pci_fixup_transparent_bridge+0x0/0x2a
[ 1.566729] pci 0000:00:1d.1: found [8086:3a35] class 000c03 header type 00
[ 1.566754] pci 0000:00:1d.1: reg 20: [io 0xac00-0xac1f]
[ 1.566766] pci 0000:00:1d.1: calling quirk_resource_alignment+0x0/0x19d
[ 1.566768] pci 0000:00:1d.1: calling pci_fixup_transparent_bridge+0x0/0x2a
[ 1.566792] pci 0000:00:1d.2: found [8086:3a36] class 000c03 header type 00
[ 1.566818] pci 0000:00:1d.2: reg 20: [io 0xb000-0xb01f]
[ 1.566829] pci 0000:00:1d.2: calling quirk_resource_alignment+0x0/0x19d
[ 1.566831] pci 0000:00:1d.2: calling pci_fixup_transparent_bridge+0x0/0x2a
[ 1.566864] pci 0000:00:1d.7: found [8086:3a3a] class 000c03 header type 00
[ 1.566881] pci 0000:00:1d.7: reg 10: [mem 0xfbcfc000-0xfbcfc3ff]
[ 1.566909] pci 0000:00:1d.7: calling quirk_resource_alignment+0x0/0x19d
[ 1.566912] pci 0000:00:1d.7: calling pci_fixup_transparent_bridge+0x0/0x2a
[ 1.566934] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
[ 1.566937] pci 0000:00:1d.7: PME# disabled
[ 1.566954] pci 0000:00:1e.0: found [8086:244e] class 000604 header type 01
[ 1.566975] pci 0000:00:1e.0: calling quirk_resource_alignment+0x0/0x19d
[ 1.566977] pci 0000:00:1e.0: calling pci_fixup_transparent_bridge+0x0/0x2a
[ 1.567002] pci 0000:00:1f.0: found [8086:3a16] class 000601 header type 00
[ 1.567047] pci 0000:00:1f.0: calling ich_force_enable_hpet+0x0/0x1c8
[ 1.567050] pci 0000:00:1f.0: calling quirk_ich7_lpc+0x0/0x65
[ 1.567053] pci 0000:00:1f.0: quirk: [io 0x0800-0x087f] claimed by ICH6 ACPI/GPIO/TCO
[ 1.567056] pci 0000:00:1f.0: quirk: [io 0x0500-0x053f] claimed by ICH6 GPIO
[ 1.567059] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0a00 (mask 00ff)
[ 1.567066] pci 0000:00:1f.0: calling quirk_resource_alignment+0x0/0x19d
[ 1.567068] pci 0000:00:1f.0: calling pci_fixup_transparent_bridge+0x0/0x2a
[ 1.567099] pci 0000:00:1f.2: found [8086:3a20] class 000101 header type 00
[ 1.567110] pci 0000:00:1f.2: reg 10: [io 0xbc00-0xbc07]
[ 1.567115] pci 0000:00:1f.2: reg 14: [io 0xb880-0xb883]
[ 1.567119] pci 0000:00:1f.2: reg 18: [io 0xb800-0xb807]
[ 1.567124] pci 0000:00:1f.2: reg 1c: [io 0xb480-0xb483]
[ 1.567128] pci 0000:00:1f.2: reg 20: [io 0xb400-0xb40f]
[ 1.567133] pci 0000:00:1f.2: reg 24: [io 0xb080-0xb08f]
[ 1.567141] pci 0000:00:1f.2: calling quirk_resource_alignment+0x0/0x19d
[ 1.567144] pci 0000:00:1f.2: calling pci_fixup_transparent_bridge+0x0/0x2a
[ 1.567169] pci 0000:00:1f.3: found [8086:3a30] class 000c05 header type 00
[ 1.567180] pci 0000:00:1f.3: reg 10: [mem 0xfbcffc00-0xfbcffcff 64bit]
[ 1.567191] pci 0000:00:1f.3: reg 20: [io 0x0400-0x041f]
[ 1.567202] pci 0000:00:1f.3: calling quirk_resource_alignment+0x0/0x19d
[ 1.567204] pci 0000:00:1f.3: calling pci_fixup_transparent_bridge+0x0/0x2a
[ 1.567219] pci 0000:00:1f.5: found [8086:3a26] class 000101 header type 00
[ 1.567231] pci 0000:00:1f.5: reg 10: [io 0xcc00-0xcc07]
[ 1.567235] pci 0000:00:1f.5: reg 14: [io 0xc880-0xc883]
[ 1.567240] pci 0000:00:1f.5: reg 18: [io 0xc800-0xc807]
[ 1.567245] pci 0000:00:1f.5: reg 1c: [io 0xc480-0xc483]
[ 1.567249] pci 0000:00:1f.5: reg 20: [io 0xc400-0xc40f]
[ 1.567254] pci 0000:00:1f.5: reg 24: [io 0xc080-0xc08f]
[ 1.567262] pci 0000:00:1f.5: calling quirk_resource_alignment+0x0/0x19d
[ 1.567264] pci 0000:00:1f.5: calling pci_fixup_transparent_bridge+0x0/0x2a
[ 1.567285] pci_bus 0000:00: fixups for bus
[ 1.567288] pci 0000:00:01.0: scanning behind bridge, config 060600, pass 0
[ 1.567292] pci_bus 0000:06: scanning bus
[ 1.567307] pci_bus 0000:06: fixups for bus
[ 1.567309] pci 0000:00:01.0: PCI bridge to [bus 06-06]
[ 1.567316] pci_bus 0000:06: bus scan returning with max=06
[ 1.567319] pci 0000:00:03.0: scanning behind bridge, config 050500, pass 0
[ 1.567322] pci_bus 0000:05: scanning bus
[ 1.567338] pci_bus 0000:05: fixups for bus
[ 1.567339] pci 0000:00:03.0: PCI bridge to [bus 05-05]
[ 1.567346] pci_bus 0000:05: bus scan returning with max=05
[ 1.567349] pci 0000:00:07.0: scanning behind bridge, config 040400, pass 0
[ 1.567352] pci_bus 0000:04: scanning bus
[ 1.567362] pci 0000:04:00.0: found [1002:9442] class 000300 header type 00
[ 1.567365] pci 0000:04:00.0: calling quirk_no_ata_d3+0x0/0x1b
[ 1.567375] pci 0000:04:00.0: reg 10: [mem 0xd0000000-0xdfffffff 64bit pref]
[ 1.567382] pci 0000:04:00.0: reg 18: [mem 0xfbee0000-0xfbeeffff 64bit]
[ 1.567387] pci 0000:04:00.0: reg 20: [io 0xe000-0xe0ff]
[ 1.567394] pci 0000:04:00.0: reg 30: [mem 0xfbec0000-0xfbedffff pref]
[ 1.567398] pci 0000:04:00.0: calling quirk_resource_alignment+0x0/0x19d
[ 1.567413] pci 0000:04:00.0: supports D1 D2
[ 1.567430] pci 0000:04:00.1: found [1002:aa30] class 000403 header type 00
[ 1.567433] pci 0000:04:00.1: calling quirk_no_ata_d3+0x0/0x1b
[ 1.567442] pci 0000:04:00.1: reg 10: [mem 0xfbefc000-0xfbefffff 64bit]
[ 1.567461] pci 0000:04:00.1: calling quirk_resource_alignment+0x0/0x19d
[ 1.567475] pci 0000:04:00.1: supports D1 D2
[ 1.567501] pci_bus 0000:04: fixups for bus
[ 1.567503] pci 0000:00:07.0: PCI bridge to [bus 04-04]
[ 1.567506] pci 0000:00:07.0: bridge window [io 0xe000-0xefff]
[ 1.567508] pci 0000:00:07.0: bridge window [mem 0xfbe00000-0xfbefffff]
[ 1.567513] pci 0000:00:07.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
[ 1.567515] pci_bus 0000:04: bus scan returning with max=04
[ 1.567518] pci 0000:00:1c.0: scanning behind bridge, config 030300, pass 0
[ 1.567522] pci_bus 0000:03: scanning bus
[ 1.567549] pci_bus 0000:03: fixups for bus
[ 1.567550] pci 0000:00:1c.0: PCI bridge to [bus 03-03]
[ 1.567558] pci_bus 0000:03: bus scan returning with max=03
[ 1.567561] pci 0000:00:1c.1: scanning behind bridge, config 020200, pass 0
[ 1.567565] pci_bus 0000:02: scanning bus
[ 1.567589] pci 0000:02:00.0: found [1106:3403] class 000c00 header type 00
[ 1.567593] pci 0000:02:00.0: calling quirk_no_ata_d3+0x0/0x1b
[ 1.567613] pci 0000:02:00.0: reg 10: [mem 0xfbdff800-0xfbdfffff 64bit]
[ 1.567622] pci 0000:02:00.0: reg 18: [io 0xd800-0xd8ff]
[ 1.567657] pci 0000:02:00.0: calling quirk_resource_alignment+0x0/0x19d
[ 1.567692] pci 0000:02:00.0: supports D2
[ 1.567693] pci 0000:02:00.0: PME# supported from D2 D3hot D3cold
[ 1.567699] pci 0000:02:00.0: PME# disabled
[ 1.567747] pci_bus 0000:02: fixups for bus
[ 1.567748] pci 0000:00:1c.1: PCI bridge to [bus 02-02]
[ 1.567752] pci 0000:00:1c.1: bridge window [io 0xd000-0xdfff]
[ 1.567755] pci 0000:00:1c.1: bridge window [mem 0xfbd00000-0xfbdfffff]
[ 1.567759] pci_bus 0000:02: bus scan returning with max=02
[ 1.567763] pci 0000:00:1e.0: scanning behind bridge, config 010100, pass 0
[ 1.567767] pci_bus 0000:01: scanning bus
[ 1.567804] pci_bus 0000:01: fixups for bus
[ 1.567806] pci 0000:00:1e.0: PCI bridge to [bus 01-01] (subtractive decode)
[ 1.567814] pci_bus 0000:01: bus scan returning with max=01
[ 1.567817] pci 0000:00:01.0: scanning behind bridge, config 060600, pass 1
[ 1.567821] pci 0000:00:03.0: scanning behind bridge, config 050500, pass 1
[ 1.567826] pci 0000:00:07.0: scanning behind bridge, config 040400, pass 1
[ 1.567830] pci 0000:00:1c.0: scanning behind bridge, config 030300, pass 1
[ 1.567835] pci 0000:00:1c.1: scanning behind bridge, config 020200, pass 1
[ 1.567839] pci 0000:00:1e.0: scanning behind bridge, config 010100, pass 1
[ 1.567843] pci_bus 0000:00: bus scan returning with max=06
[ 1.567847] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[ 1.568168] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P4._PRT]
[ 1.568220] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P5._PRT]
[ 1.568282] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NPE1._PRT]
[ 1.568334] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NPE3._PRT]
[ 1.568393] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NPE7._PRT]
[ 1.593935] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 6 7 *10 11 12 14 15)
[ 1.594034] ACPI: PCI Interrupt Link [LNKB] (IRQs *5)
[ 1.594131] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 6 7 10 11 12 14 *15)
[ 1.594229] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 6 7 10 *11 12 14 15)
[ 1.594327] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 *4 6 7 10 11 12 14 15)
[ 1.594428] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 6 *7 10 11 12 14 15)
[ 1.594526] ACPI: PCI Interrupt Link [LNKG] (IRQs *3 4 6 7 10 11 12 14 15)
[ 1.594624] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 6 7 10 11 12 *14 15)
[ 1.594703] vgaarb: device added: PCI:0000:04:00.0,decodes=io+mem,owns=io+mem,locks=none
[ 1.594706] vgaarb: loaded
[ 1.594772] SCSI subsystem initialized
[ 1.594859] libata version 3.00 loaded.
[ 1.594914] PCI: Using ACPI for IRQ routing
[ 1.594916] PCI: pci_cache_line_size set to 64 bytes
[ 1.594931] pci 0000:00:19.0: BAR 0: reserving [mem 0xfbcc0000-0xfbcdffff flags 0x20200] (d=0, p=0)
[ 1.594934] pci 0000:00:19.0: BAR 1: reserving [mem 0xfbcf4000-0xfbcf4fff flags 0x20200] (d=0, p=0)
[ 1.594937] pci 0000:00:19.0: BAR 2: reserving [io 0xa080-0xa09f flags 0x20101] (d=0, p=0)
[ 1.594940] pci 0000:00:1a.0: BAR 4: reserving [io 0xa400-0xa41f flags 0x20101] (d=0, p=0)
[ 1.594944] pci 0000:00:1a.1: BAR 4: reserving [io 0xa480-0xa49f flags 0x20101] (d=0, p=0)
[ 1.594947] pci 0000:00:1a.2: BAR 4: reserving [io 0xa800-0xa81f flags 0x20101] (d=0, p=0)
[ 1.594951] pci 0000:00:1a.7: BAR 0: reserving [mem 0xfbcf6000-0xfbcf63ff flags 0x20200] (d=0, p=0)
[ 1.594955] pci 0000:00:1b.0: BAR 0: reserving [mem 0xfbcf8000-0xfbcfbfff flags 0x120204] (d=0, p=0)
[ 1.594961] pci 0000:00:1d.0: BAR 4: reserving [io 0xa880-0xa89f flags 0x20101] (d=0, p=0)
[ 1.594964] pci 0000:00:1d.1: BAR 4: reserving [io 0xac00-0xac1f flags 0x20101] (d=0, p=0)
[ 1.594968] pci 0000:00:1d.2: BAR 4: reserving [io 0xb000-0xb01f flags 0x20101] (d=0, p=0)
[ 1.594972] pci 0000:00:1d.7: BAR 0: reserving [mem 0xfbcfc000-0xfbcfc3ff flags 0x20200] (d=0, p=0)
[ 1.594978] pci 0000:00:1f.2: BAR 0: reserving [io 0xbc00-0xbc07 flags 0x20101] (d=0, p=0)
[ 1.594980] pci 0000:00:1f.2: BAR 1: reserving [io 0xb880-0xb883 flags 0x20101] (d=0, p=0)
[ 1.594983] pci 0000:00:1f.2: BAR 2: reserving [io 0xb800-0xb807 flags 0x20101] (d=0, p=0)
[ 1.594985] pci 0000:00:1f.2: BAR 3: reserving [io 0xb480-0xb483 flags 0x20101] (d=0, p=0)
[ 1.594987] pci 0000:00:1f.2: BAR 4: reserving [io 0xb400-0xb40f flags 0x20101] (d=0, p=0)
[ 1.594989] pci 0000:00:1f.2: BAR 5: reserving [io 0xb080-0xb08f flags 0x20101] (d=0, p=0)
[ 1.594993] pci 0000:00:1f.3: BAR 0: reserving [mem 0xfbcffc00-0xfbcffcff flags 0x120204] (d=0, p=0)
[ 1.594995] pci 0000:00:1f.3: BAR 4: reserving [io 0x0400-0x041f flags 0x20101] (d=0, p=0)
[ 1.594999] pci 0000:00:1f.5: BAR 0: reserving [io 0xcc00-0xcc07 flags 0x20101] (d=0, p=0)
[ 1.595001] pci 0000:00:1f.5: BAR 1: reserving [io 0xc880-0xc883 flags 0x20101] (d=0, p=0)
[ 1.595003] pci 0000:00:1f.5: BAR 2: reserving [io 0xc800-0xc807 flags 0x20101] (d=0, p=0)
[ 1.595005] pci 0000:00:1f.5: BAR 3: reserving [io 0xc480-0xc483 flags 0x20101] (d=0, p=0)
[ 1.595008] pci 0000:00:1f.5: BAR 4: reserving [io 0xc400-0xc40f flags 0x20101] (d=0, p=0)
[ 1.595010] pci 0000:00:1f.5: BAR 5: reserving [io 0xc080-0xc08f flags 0x20101] (d=0, p=0)
[ 1.595017] pci 0000:04:00.0: BAR 0: reserving [mem 0xd0000000-0xdfffffff flags 0x12120c] (d=0, p=0)
[ 1.595019] pci 0000:04:00.0: BAR 2: reserving [mem 0xfbee0000-0xfbeeffff flags 0x120204] (d=0, p=0)
[ 1.595022] pci 0000:04:00.0: BAR 4: reserving [io 0xe000-0xe0ff flags 0x20101] (d=0, p=0)
[ 1.595025] pci 0000:04:00.1: BAR 0: reserving [mem 0xfbefc000-0xfbefffff flags 0x120204] (d=0, p=0)
[ 1.595030] pci 0000:02:00.0: BAR 0: reserving [mem 0xfbdff800-0xfbdfffff flags 0x120204] (d=0, p=0)
[ 1.595033] pci 0000:02:00.0: BAR 2: reserving [io 0xd800-0xd8ff flags 0x20101] (d=0, p=0)
[ 1.595125] Bluetooth: Core ver 2.15
[ 1.595146] NET: Registered protocol family 31
[ 1.595147] Bluetooth: HCI device and connection manager initialized
[ 1.595149] Bluetooth: HCI socket layer initialized
[ 1.595150] NetLabel: Initializing
[ 1.595151] NetLabel: domain hash size = 128
[ 1.595152] NetLabel: protocols = UNLABELED CIPSOv4
[ 1.595161] NetLabel: unlabeled traffic allowed by default
[ 1.595165] HPET: 4 timers in total, 0 timers will be used for per-cpu timer
[ 1.595170] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0
[ 1.595173] hpet0: 4 comparators, 64-bit 14.318180 MHz counter
[ 1.635005] Switching to clocksource hpet
[ 1.636487] pnp: PnP ACPI init
[ 1.636497] ACPI: bus type pnp registered
[ 1.638653] pnp: PnP ACPI: found 14 devices
[ 1.638655] ACPI: ACPI bus type pnp unregistered
[ 1.638662] system 00:01: [mem 0xfbf00000-0xfbffffff] has been reserved
[ 1.638664] system 00:01: [mem 0xfc000000-0xfcffffff] has been reserved
[ 1.638667] system 00:01: [mem 0xfd000000-0xfdffffff] has been reserved
[ 1.638669] system 00:01: [mem 0xfe000000-0xfebfffff] has been reserved
[ 1.638671] system 00:01: [mem 0xfec8a000-0xfec8afff] has been reserved
[ 1.638673] system 00:01: [mem 0xfed10000-0xfed10fff] has been reserved
[ 1.638678] system 00:06: [io 0x0a00-0x0a0f] has been reserved
[ 1.638680] system 00:06: [io 0x0a10-0x0a1f] has been reserved
[ 1.638681] system 00:06: [io 0x0a20-0x0a2f] has been reserved
[ 1.638683] system 00:06: [io 0x0a30-0x0a3f] has been reserved
[ 1.638687] system 00:07: [io 0x04d0-0x04d1] has been reserved
[ 1.638689] system 00:07: [io 0x0800-0x087f] has been reserved
[ 1.638691] system 00:07: [io 0x0500-0x057f] could not be reserved
[ 1.638694] system 00:07: [mem 0xfed1c000-0xfed1ffff] has been reserved
[ 1.638696] system 00:07: [mem 0xfed20000-0xfed3ffff] has been reserved
[ 1.638698] system 00:07: [mem 0xfed40000-0xfed8ffff] has been reserved
[ 1.638702] system 00:0a: [mem 0xffc00000-0xffefffff] has been reserved
[ 1.638706] system 00:0b: [mem 0xfec00000-0xfec00fff] could not be reserved
[ 1.638708] system 00:0b: [mem 0xfee00000-0xfee00fff] has been reserved
[ 1.638711] system 00:0c: [mem 0xe0000000-0xefffffff] has been reserved
[ 1.638715] system 00:0d: [mem 0x00000000-0x0009ffff] could not be reserved
[ 1.638717] system 00:0d: [mem 0x000c0000-0x000cffff] has been reserved
[ 1.638719] system 00:0d: [mem 0x000e0000-0x000fffff] could not be reserved
[ 1.638721] system 00:0d: [mem 0x00100000-0xbfffffff] could not be reserved
[ 1.638724] system 00:0d: [mem 0xfed90000-0xffffffff] could not be reserved
[ 1.643465] pci 0000:00:1c.0: BAR 14: assigned [mem 0xc0000000-0xc01fffff]
[ 1.643467] pci 0000:00:1c.0: BAR 15: assigned [mem 0xc0200000-0xc03fffff 64bit pref]
[ 1.643469] pci 0000:00:1c.1: BAR 15: assigned [mem 0xc0400000-0xc05fffff 64bit pref]
[ 1.643472] pci 0000:00:1c.0: BAR 13: assigned [io 0x1000-0x1fff]
[ 1.643473] pci 0000:00:01.0: PCI bridge to [bus 06-06]
[ 1.643475] pci 0000:00:01.0: bridge window [io disabled]
[ 1.643478] pci 0000:00:01.0: bridge window [mem disabled]
[ 1.643480] pci 0000:00:01.0: bridge window [mem pref disabled]
[ 1.643484] pci 0000:00:03.0: PCI bridge to [bus 05-05]
[ 1.643486] pci 0000:00:03.0: bridge window [io disabled]
[ 1.643489] pci 0000:00:03.0: bridge window [mem disabled]
[ 1.643491] pci 0000:00:03.0: bridge window [mem pref disabled]
[ 1.643496] pci 0000:00:07.0: PCI bridge to [bus 04-04]
[ 1.643498] pci 0000:00:07.0: bridge window [io 0xe000-0xefff]
[ 1.643502] pci 0000:00:07.0: bridge window [mem 0xfbe00000-0xfbefffff]
[ 1.643505] pci 0000:00:07.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
[ 1.643509] pci 0000:00:1c.0: PCI bridge to [bus 03-03]
[ 1.643511] pci 0000:00:1c.0: bridge window [io 0x1000-0x1fff]
[ 1.643515] pci 0000:00:1c.0: bridge window [mem 0xc0000000-0xc01fffff]
[ 1.643518] pci 0000:00:1c.0: bridge window [mem 0xc0200000-0xc03fffff 64bit pref]
[ 1.643523] pci 0000:00:1c.1: PCI bridge to [bus 02-02]
[ 1.643525] pci 0000:00:1c.1: bridge window [io 0xd000-0xdfff]
[ 1.643529] pci 0000:00:1c.1: bridge window [mem 0xfbd00000-0xfbdfffff]
[ 1.643533] pci 0000:00:1c.1: bridge window [mem 0xc0400000-0xc05fffff 64bit pref]
[ 1.643537] pci 0000:00:1e.0: PCI bridge to [bus 01-01]
[ 1.643538] pci 0000:00:1e.0: bridge window [io disabled]
[ 1.643542] pci 0000:00:1e.0: bridge window [mem disabled]
[ 1.643545] pci 0000:00:1e.0: bridge window [mem pref disabled]
[ 1.643555] pci 0000:00:01.0: setting latency timer to 64
[ 1.643562] pci 0000:00:03.0: setting latency timer to 64
[ 1.643568] pci 0000:00:07.0: setting latency timer to 64
[ 1.643574] pci 0000:00:1c.0: enabling device (0104 -> 0107)
[ 1.643577] alloc irq_desc for 17 on node -1
[ 1.643579] alloc kstat_irqs on node -1
[ 1.643583] pci 0000:00:1c.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 1.643586] pci 0000:00:1c.0: setting latency timer to 64
[ 1.643592] alloc irq_desc for 16 on node -1
[ 1.643593] alloc kstat_irqs on node -1
[ 1.643596] pci 0000:00:1c.1: PCI INT B -> GSI 16 (level, low) -> IRQ 16
[ 1.643599] pci 0000:00:1c.1: setting latency timer to 64
[ 1.643604] pci 0000:00:1e.0: setting latency timer to 64
[ 1.643607] pci_bus 0000:00: resource 0 [io 0x0000-0xffff]
[ 1.643608] pci_bus 0000:00: resource 1 [mem 0x00000000-0xffffffffffffffff]
[ 1.643610] pci_bus 0000:04: resource 0 [io 0xe000-0xefff]
[ 1.643612] pci_bus 0000:04: resource 1 [mem 0xfbe00000-0xfbefffff]
[ 1.643614] pci_bus 0000:04: resource 2 [mem 0xd0000000-0xdfffffff 64bit pref]
[ 1.643616] pci_bus 0000:03: resource 0 [io 0x1000-0x1fff]
[ 1.643617] pci_bus 0000:03: resource 1 [mem 0xc0000000-0xc01fffff]
[ 1.643619] pci_bus 0000:03: resource 2 [mem 0xc0200000-0xc03fffff 64bit pref]
[ 1.643621] pci_bus 0000:02: resource 0 [io 0xd000-0xdfff]
[ 1.643622] pci_bus 0000:02: resource 1 [mem 0xfbd00000-0xfbdfffff]
[ 1.643624] pci_bus 0000:02: resource 2 [mem 0xc0400000-0xc05fffff 64bit pref]
[ 1.643626] pci_bus 0000:01: resource 3 [io 0x0000-0xffff]
[ 1.643627] pci_bus 0000:01: resource 4 [mem 0x00000000-0xffffffffffffffff]
[ 1.643643] NET: Registered protocol family 2
[ 1.643903] IP route cache hash table entries: 524288 (order: 10, 4194304 bytes)
[ 1.644826] TCP established hash table entries: 524288 (order: 11, 8388608 bytes)
[ 1.646060] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
[ 1.646194] TCP: Hash tables configured (established 524288 bind 65536)
[ 1.646196] TCP reno registered
[ 1.646214] UDP hash table entries: 8192 (order: 6, 262144 bytes)
[ 1.646274] UDP-Lite hash table entries: 8192 (order: 6, 262144 bytes)
[ 1.646392] NET: Registered protocol family 1
[ 1.646404] pci 0000:00:00.0: calling quirk_e100_interrupt+0x0/0x173
[ 1.646408] pci 0000:00:00.0: calling quirk_cardbus_legacy+0x0/0x1b
[ 1.646411] pci 0000:00:00.0: calling quirk_usb_early_handoff+0x0/0x565
[ 1.646413] pci 0000:00:00.0: calling pci_fixup_video+0x0/0xb8
[ 1.646418] pci 0000:00:01.0: calling quirk_e100_interrupt+0x0/0x173
[ 1.646420] pci 0000:00:01.0: calling quirk_cardbus_legacy+0x0/0x1b
[ 1.646422] pci 0000:00:01.0: calling quirk_usb_early_handoff+0x0/0x565
[ 1.646424] pci 0000:00:01.0: calling pci_fixup_video+0x0/0xb8
[ 1.646428] pci 0000:00:03.0: calling quirk_e100_interrupt+0x0/0x173
[ 1.646430] pci 0000:00:03.0: calling quirk_cardbus_legacy+0x0/0x1b
[ 1.646432] pci 0000:00:03.0: calling quirk_usb_early_handoff+0x0/0x565
[ 1.646434] pci 0000:00:03.0: calling pci_fixup_video+0x0/0xb8
[ 1.646438] pci 0000:00:07.0: calling quirk_e100_interrupt+0x0/0x173
[ 1.646440] pci 0000:00:07.0: calling quirk_cardbus_legacy+0x0/0x1b
[ 1.646442] pci 0000:00:07.0: calling quirk_usb_early_handoff+0x0/0x565
[ 1.646444] pci 0000:00:07.0: calling pci_fixup_video+0x0/0xb8
[ 1.646448] pci 0000:00:10.0: calling quirk_e100_interrupt+0x0/0x173
[ 1.646450] pci 0000:00:10.0: calling quirk_cardbus_legacy+0x0/0x1b
[ 1.646452] pci 0000:00:10.0: calling quirk_usb_early_handoff+0x0/0x565
[ 1.646454] pci 0000:00:10.0: calling pci_fixup_video+0x0/0xb8
[ 1.646458] pci 0000:00:10.1: calling quirk_e100_interrupt+0x0/0x173
[ 1.646460] pci 0000:00:10.1: calling quirk_cardbus_legacy+0x0/0x1b
[ 1.646462] pci 0000:00:10.1: calling quirk_usb_early_handoff+0x0/0x565
[ 1.646464] pci 0000:00:10.1: calling pci_fixup_video+0x0/0xb8
[ 1.646468] pci 0000:00:14.0: calling quirk_e100_interrupt+0x0/0x173
[ 1.646470] pci 0000:00:14.0: calling quirk_cardbus_legacy+0x0/0x1b
[ 1.646472] pci 0000:00:14.0: calling quirk_usb_early_handoff+0x0/0x565
[ 1.646474] pci 0000:00:14.0: calling pci_fixup_video+0x0/0xb8
[ 1.646478] pci 0000:00:14.1: calling quirk_e100_interrupt+0x0/0x173
[ 1.646480] pci 0000:00:14.1: calling quirk_cardbus_legacy+0x0/0x1b
[ 1.646482] pci 0000:00:14.1: calling quirk_usb_early_handoff+0x0/0x565
[ 1.646484] pci 0000:00:14.1: calling pci_fixup_video+0x0/0xb8
[ 1.646488] pci 0000:00:14.2: calling quirk_e100_interrupt+0x0/0x173
[ 1.646490] pci 0000:00:14.2: calling quirk_cardbus_legacy+0x0/0x1b
[ 1.646492] pci 0000:00:14.2: calling quirk_usb_early_handoff+0x0/0x565
[ 1.646494] pci 0000:00:14.2: calling pci_fixup_video+0x0/0xb8
[ 1.646497] pci 0000:00:14.3: calling quirk_e100_interrupt+0x0/0x173
[ 1.646500] pci 0000:00:14.3: calling quirk_cardbus_legacy+0x0/0x1b
[ 1.646502] pci 0000:00:14.3: calling quirk_usb_early_handoff+0x0/0x565
[ 1.646504] pci 0000:00:14.3: calling pci_fixup_video+0x0/0xb8
[ 1.646507] pci 0000:00:19.0: calling quirk_e100_interrupt+0x0/0x173
[ 1.646510] pci 0000:00:19.0: calling quirk_cardbus_legacy+0x0/0x1b
[ 1.646512] pci 0000:00:19.0: calling quirk_usb_early_handoff+0x0/0x565
[ 1.646514] pci 0000:00:19.0: calling pci_fixup_video+0x0/0xb8
[ 1.646518] pci 0000:00:1a.0: calling quirk_e100_interrupt+0x0/0x173
[ 1.646520] pci 0000:00:1a.0: calling quirk_cardbus_legacy+0x0/0x1b
[ 1.646522] pci 0000:00:1a.0: calling quirk_usb_early_handoff+0x0/0x565
[ 1.646536] pci 0000:00:1a.0: calling pci_fixup_video+0x0/0xb8
[ 1.646540] pci 0000:00:1a.1: calling quirk_e100_interrupt+0x0/0x173
[ 1.646542] pci 0000:00:1a.1: calling quirk_cardbus_legacy+0x0/0x1b
[ 1.646544] pci 0000:00:1a.1: calling quirk_usb_early_handoff+0x0/0x565
[ 1.646557] pci 0000:00:1a.1: calling pci_fixup_video+0x0/0xb8
[ 1.646561] pci 0000:00:1a.2: calling quirk_e100_interrupt+0x0/0x173
[ 1.646563] pci 0000:00:1a.2: calling quirk_cardbus_legacy+0x0/0x1b
[ 1.646565] pci 0000:00:1a.2: calling quirk_usb_early_handoff+0x0/0x565
[ 1.646578] pci 0000:00:1a.2: calling pci_fixup_video+0x0/0xb8
[ 1.646582] pci 0000:00:1a.7: calling quirk_e100_interrupt+0x0/0x173
[ 1.646585] pci 0000:00:1a.7: calling quirk_cardbus_legacy+0x0/0x1b
[ 1.646587] pci 0000:00:1a.7: calling quirk_usb_early_handoff+0x0/0x565
[ 1.646604] pci 0000:00:1a.7: calling pci_fixup_video+0x0/0xb8
[ 1.646608] pci 0000:00:1b.0: calling quirk_e100_interrupt+0x0/0x173
[ 1.646610] pci 0000:00:1b.0: calling quirk_cardbus_legacy+0x0/0x1b
[ 1.646612] pci 0000:00:1b.0: calling quirk_usb_early_handoff+0x0/0x565
[ 1.646614] pci 0000:00:1b.0: calling pci_fixup_video+0x0/0xb8
[ 1.646618] pci 0000:00:1c.0: calling quirk_e100_interrupt+0x0/0x173
[ 1.646621] pci 0000:00:1c.0: calling quirk_cardbus_legacy+0x0/0x1b
[ 1.646623] pci 0000:00:1c.0: calling quirk_usb_early_handoff+0x0/0x565
[ 1.646625] pci 0000:00:1c.0: calling pci_fixup_video+0x0/0xb8
[ 1.646629] pci 0000:00:1c.1: calling quirk_e100_interrupt+0x0/0x173
[ 1.646631] pci 0000:00:1c.1: calling quirk_cardbus_legacy+0x0/0x1b
[ 1.646633] pci 0000:00:1c.1: calling quirk_usb_early_handoff+0x0/0x565
[ 1.646635] pci 0000:00:1c.1: calling pci_fixup_video+0x0/0xb8
[ 1.646639] pci 0000:00:1d.0: calling quirk_e100_interrupt+0x0/0x173
[ 1.646641] pci 0000:00:1d.0: calling quirk_cardbus_legacy+0x0/0x1b
[ 1.646643] pci 0000:00:1d.0: calling quirk_usb_early_handoff+0x0/0x565
[ 1.646656] pci 0000:00:1d.0: calling pci_fixup_video+0x0/0xb8
[ 1.646660] pci 0000:00:1d.1: calling quirk_e100_interrupt+0x0/0x173
[ 1.646662] pci 0000:00:1d.1: calling quirk_cardbus_legacy+0x0/0x1b
[ 1.646664] pci 0000:00:1d.1: calling quirk_usb_early_handoff+0x0/0x565
[ 1.646677] pci 0000:00:1d.1: calling pci_fixup_video+0x0/0xb8
[ 1.646681] pci 0000:00:1d.2: calling quirk_e100_interrupt+0x0/0x173
[ 1.646684] pci 0000:00:1d.2: calling quirk_cardbus_legacy+0x0/0x1b
[ 1.646686] pci 0000:00:1d.2: calling quirk_usb_early_handoff+0x0/0x565
[ 1.646699] pci 0000:00:1d.2: calling pci_fixup_video+0x0/0xb8
[ 1.646703] pci 0000:00:1d.7: calling quirk_e100_interrupt+0x0/0x173
[ 1.646705] pci 0000:00:1d.7: calling quirk_cardbus_legacy+0x0/0x1b
[ 1.646707] pci 0000:00:1d.7: calling quirk_usb_early_handoff+0x0/0x565
[ 1.646729] pci 0000:00:1d.7: calling pci_fixup_video+0x0/0xb8
[ 1.646734] pci 0000:00:1e.0: calling quirk_e100_interrupt+0x0/0x173
[ 1.646736] pci 0000:00:1e.0: calling quirk_cardbus_legacy+0x0/0x1b
[ 1.646738] pci 0000:00:1e.0: calling quirk_usb_early_handoff+0x0/0x565
[ 1.646740] pci 0000:00:1e.0: calling pci_fixup_video+0x0/0xb8
[ 1.646744] pci 0000:00:1f.0: calling quirk_e100_interrupt+0x0/0x173
[ 1.646746] pci 0000:00:1f.0: calling quirk_cardbus_legacy+0x0/0x1b
[ 1.646748] pci 0000:00:1f.0: calling quirk_usb_early_handoff+0x0/0x565
[ 1.646750] pci 0000:00:1f.0: calling pci_fixup_video+0x0/0xb8
[ 1.646754] pci 0000:00:1f.2: calling quirk_e100_interrupt+0x0/0x173
[ 1.646757] pci 0000:00:1f.2: calling quirk_cardbus_legacy+0x0/0x1b
[ 1.646759] pci 0000:00:1f.2: calling quirk_usb_early_handoff+0x0/0x565
[ 1.646760] pci 0000:00:1f.2: calling pci_fixup_video+0x0/0xb8
[ 1.646764] pci 0000:00:1f.3: calling quirk_e100_interrupt+0x0/0x173
[ 1.646767] pci 0000:00:1f.3: calling quirk_cardbus_legacy+0x0/0x1b
[ 1.646769] pci 0000:00:1f.3: calling quirk_usb_early_handoff+0x0/0x565
[ 1.646771] pci 0000:00:1f.3: calling pci_fixup_video+0x0/0xb8
[ 1.646774] pci 0000:00:1f.5: calling quirk_e100_interrupt+0x0/0x173
[ 1.646777] pci 0000:00:1f.5: calling quirk_cardbus_legacy+0x0/0x1b
[ 1.646779] pci 0000:00:1f.5: calling quirk_usb_early_handoff+0x0/0x565
[ 1.646781] pci 0000:00:1f.5: calling pci_fixup_video+0x0/0xb8
[ 1.646784] pci 0000:04:00.0: calling quirk_cardbus_legacy+0x0/0x1b
[ 1.646786] pci 0000:04:00.0: calling quirk_usb_early_handoff+0x0/0x565
[ 1.646788] pci 0000:04:00.0: calling pci_fixup_video+0x0/0xb8
[ 1.646791] pci 0000:04:00.0: Boot video device
[ 1.646795] pci 0000:04:00.1: calling quirk_cardbus_legacy+0x0/0x1b
[ 1.646797] pci 0000:04:00.1: calling quirk_usb_early_handoff+0x0/0x565
[ 1.646799] pci 0000:04:00.1: calling pci_fixup_video+0x0/0xb8
[ 1.646802] pci 0000:02:00.0: calling via_no_dac+0x0/0x54
[ 1.646804] pci 0000:02:00.0: calling quirk_cardbus_legacy+0x0/0x1b
[ 1.646806] pci 0000:02:00.0: calling quirk_usb_early_handoff+0x0/0x565
[ 1.646808] pci 0000:02:00.0: calling pci_fixup_video+0x0/0xb8
[ 1.646813] PCI: CLS 64 bytes, default 64
[ 1.646847] Trying to unpack rootfs image as initramfs...
[ 2.642788] Freeing initrd memory: 53398k freed
[ 2.650176] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[ 2.650180] Placing 64MB software IO TLB between ffff880020000000 - ffff880024000000
[ 2.650182] software IO TLB at phys 0x20000000 - 0x24000000
[ 2.650615] Scanning for low memory corruption every 60 seconds
[ 2.651231] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[ 2.652250] VFS: Disk quotas dquot_6.5.2
[ 2.652282] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 2.652688] fuse init (API version 7.13)
[ 2.652741] msgmni has been set to 24075
[ 2.652952] alg: No test for stdrng (krng)
[ 2.652989] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[ 2.652991] io scheduler noop registered
[ 2.652992] io scheduler deadline registered
[ 2.653034] io scheduler cfq registered (default)
[ 2.653107] pcieport 0000:00:01.0: setting latency timer to 64
[ 2.653132] alloc irq_desc for 24 on node -1
[ 2.653134] alloc kstat_irqs on node -1
[ 2.653141] pcieport 0000:00:01.0: irq 24 for MSI/MSI-X
[ 2.653192] pcieport 0000:00:03.0: setting latency timer to 64
[ 2.653215] alloc irq_desc for 25 on node -1
[ 2.653216] alloc kstat_irqs on node -1
[ 2.653221] pcieport 0000:00:03.0: irq 25 for MSI/MSI-X
[ 2.653269] pcieport 0000:00:07.0: setting latency timer to 64
[ 2.653292] alloc irq_desc for 26 on node -1
[ 2.653293] alloc kstat_irqs on node -1
[ 2.653298] pcieport 0000:00:07.0: irq 26 for MSI/MSI-X
[ 2.653348] pcieport 0000:00:1c.0: setting latency timer to 64
[ 2.653374] alloc irq_desc for 27 on node -1
[ 2.653375] alloc kstat_irqs on node -1
[ 2.653380] pcieport 0000:00:1c.0: irq 27 for MSI/MSI-X
[ 2.653439] pcieport 0000:00:1c.1: setting latency timer to 64
[ 2.653465] alloc irq_desc for 28 on node -1
[ 2.653467] alloc kstat_irqs on node -1
[ 2.653472] pcieport 0000:00:1c.1: irq 28 for MSI/MSI-X
[ 2.653536] aer 0000:00:01.0:pcie02: AER service couldn't init device: no _OSC support
[ 2.653541] aer 0000:00:03.0:pcie02: AER service couldn't init device: no _OSC support
[ 2.653545] aer 0000:00:07.0:pcie02: AER service couldn't init device: no _OSC support
[ 2.653558] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 2.653616] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[ 2.653680] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
[ 2.653682] ACPI: Power Button [PWRB]
[ 2.653715] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
[ 2.653717] ACPI: Power Button [PWRF]
[ 2.654493] ACPI: SSDT 00000000bf79e0c0 00403 (v01 DpgPmm P001Ist 00000011 INTL 20051117)
[ 2.654991] ACPI: SSDT 00000000bf7a0140 003B2 (v01 PmRef P001Cst 00003001 INTL 20051117)
[ 2.655405] Monitor-Mwait will be used to enter C-1 state
[ 2.655422] Monitor-Mwait will be used to enter C-2 state
[ 2.655437] Monitor-Mwait will be used to enter C-3 state
[ 2.655896] ACPI: SSDT 00000000bf79e4d0 00403 (v01 DpgPmm P002Ist 00000012 INTL 20051117)
[ 2.656315] ACPI: SSDT 00000000bf7a0500 00085 (v01 PmRef P002Cst 00003000 INTL 20051117)
[ 2.657237] ACPI: SSDT 00000000bf79e8e0 00403 (v01 DpgPmm P003Ist 00000012 INTL 20051117)
[ 2.657661] ACPI: SSDT 00000000bf7a0590 00085 (v01 PmRef P003Cst 00003000 INTL 20051117)
[ 2.658591] ACPI: SSDT 00000000bf79ecf0 00403 (v01 DpgPmm P004Ist 00000012 INTL 20051117)
[ 2.659015] ACPI: SSDT 00000000bf7a0620 00085 (v01 PmRef P004Cst 00003000 INTL 20051117)
[ 2.659944] ACPI: SSDT 00000000bf79f100 00403 (v01 DpgPmm P005Ist 00000012 INTL 20051117)
[ 2.660372] ACPI: SSDT 00000000bf7a06b0 00085 (v01 PmRef P005Cst 00003000 INTL 20051117)
[ 2.661308] ACPI: SSDT 00000000bf79f510 00403 (v01 DpgPmm P006Ist 00000012 INTL 20051117)
[ 2.661740] ACPI: SSDT 00000000bf7a0740 00085 (v01 PmRef P006Cst 00003000 INTL 20051117)
[ 2.662664] ACPI: SSDT 00000000bf79f920 00403 (v01 DpgPmm P007Ist 00000012 INTL 20051117)
[ 2.663095] ACPI: SSDT 00000000bf7a07d0 00085 (v01 PmRef P007Cst 00003000 INTL 20051117)
[ 2.664050] ACPI: SSDT 00000000bf79fd30 00403 (v01 DpgPmm P008Ist 00000012 INTL 20051117)
[ 2.664488] ACPI: SSDT 00000000bf7a0860 00085 (v01 PmRef P008Cst 00003000 INTL 20051117)
[ 2.667673] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 2.668515] brd: module loaded
[ 2.668829] loop: module loaded
[ 2.668879] input: Macintosh mouse button emulation as /devices/virtual/input/input2
[ 2.668949] ata_piix 0000:00:1f.2: version 2.13
[ 2.668957] alloc irq_desc for 19 on node -1
[ 2.668959] alloc kstat_irqs on node -1
[ 2.668963] ata_piix 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
[ 2.668967] ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
[ 2.668980] ata_piix 0000:00:1f.2: using 32bit DMA mask
[ 2.668981] ata_piix 0000:00:1f.2: using 32bit consistent DMA mask
[ 2.668997] ata_piix 0000:00:1f.2: setting latency timer to 64
[ 2.669036] scsi0 : ata_piix
[ 2.669084] scsi1 : ata_piix
[ 2.670651] ata1: SATA max UDMA/133 cmd 0xbc00 ctl 0xb880 bmdma 0xb400 irq 19
[ 2.670655] ata2: SATA max UDMA/133 cmd 0xb800 ctl 0xb480 bmdma 0xb408 irq 19
[ 2.670670] ata_piix 0000:00:1f.5: PCI INT B -> GSI 19 (level, low) -> IRQ 19
[ 2.670674] ata_piix 0000:00:1f.5: MAP [ P0 -- P1 -- ]
[ 2.670686] ata_piix 0000:00:1f.5: using 32bit DMA mask
[ 2.670687] ata_piix 0000:00:1f.5: using 32bit consistent DMA mask
[ 2.670702] ata_piix 0000:00:1f.5: setting latency timer to 64
[ 2.670727] scsi2 : ata_piix
[ 2.670761] scsi3 : ata_piix
[ 2.671944] ata3: SATA max UDMA/133 cmd 0xcc00 ctl 0xc880 bmdma 0xc400 irq 19
[ 2.671947] ata4: SATA max UDMA/133 cmd 0xc800 ctl 0xc480 bmdma 0xc408 irq 19
[ 2.672474] Fixed MDIO Bus: probed
[ 2.672495] PPP generic driver version 2.4.2
[ 2.672549] PNP: No PS/2 controller found. Probing ports directly.
[ 2.672893] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 2.672897] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 2.672934] mice: PS/2 mouse device common for all mice
[ 2.672990] rtc_cmos 00:03: RTC can wake from S4
[ 2.673010] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
[ 2.673032] rtc0: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
[ 2.673112] device-mapper: uevent: version 1.0.3
[ 2.673171] device-mapper: ioctl: 4.16.0-ioctl (2009-11-05) initialised: dm-devel@redhat.com
[ 2.673279] device-mapper: multipath: version 1.1.1 loaded
[ 2.673281] device-mapper: multipath round-robin: version 1.0.0 loaded
[ 2.673585] cpuidle: using governor ladder
[ 2.673852] cpuidle: using governor menu
[ 2.673861] oprofile: using NMI interrupt.
[ 2.674040] TCP cubic registered
[ 2.674138] NET: Registered protocol family 10
[ 2.674426] lo: Disabled Privacy Extensions
[ 2.674645] NET: Registered protocol family 17
[ 2.674657] Bluetooth: L2CAP ver 2.14
[ 2.674658] Bluetooth: L2CAP socket layer initialized
[ 2.674659] Bluetooth: SCO (Voice Link) ver 0.6
[ 2.674660] Bluetooth: SCO socket layer initialized
[ 2.674688] Bluetooth: RFCOMM TTY layer initialized
[ 2.674691] Bluetooth: RFCOMM socket layer initialized
[ 2.674693] Bluetooth: RFCOMM ver 1.11
[ 2.677671] PM: Resume from disk failed.
[ 2.677945] Magic number: 14:867:387
[ 2.677952] thermal cooling_device2: hash matches
[ 2.678051] rtc_cmos 00:03: setting system clock to 2010-02-05 16:23:21 UTC (1265387001)
[ 2.678054] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 2.678055] EDD information not available.
[ 3.022572] ata4: SATA link down (SStatus 0 SControl 300)
[ 3.033408] ata3: SATA link down (SStatus 0 SControl 300)
[ 3.520536] ata1.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 3.520551] ata1.01: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 3.533621] ata2.00: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 3.533635] ata2.01: SATA link down (SStatus 0 SControl 300)
[ 3.533646] ata2.01: link offline, clearing class 3 to NONE
[ 3.543813] ata2.00: ATAPI: TSSTcorpDVD-ROM TS-H353B, D700, max UDMA/33
[ 3.560774] ata1.00: ATA-7: Hitachi HUA721010KLA330, GKAOA9RA, max UDMA/133
[ 3.560777] ata1.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32)
[ 3.560817] ata1.01: ATAPI: HL-DT-ST DVD+/-RW GH30N, A102, max UDMA/100
[ 3.580521] ata2.00: configured for UDMA/33
[ 3.600653] ata1.00: configured for UDMA/133
[ 3.640340] ata1.01: configured for UDMA/100
[ 3.640820] scsi 0:0:0:0: Direct-Access ATA Hitachi HUA72101 GKAO PQ: 0 ANSI: 5
[ 3.640939] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 3.641730] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[ 3.642325] scsi 0:0:1:0: CD-ROM HL-DT-ST DVD+-RW GH30N A102 PQ: 0 ANSI: 5
[ 3.642382] sd 0:0:0:0: [sda] Write Protect is off
[ 3.642385] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 3.643310] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 3.646247] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
[ 3.646251] Uniform CD-ROM driver Revision: 3.20
[ 3.646331] sda:
[ 3.646333] sr 0:0:1:0: Attached scsi CD-ROM sr0
[ 3.646377] sr 0:0:1:0: Attached scsi generic sg1 type 5
[ 3.647596] scsi 1:0:0:0: CD-ROM TSSTcorp DVD-ROM TS-H353B D700 PQ: 0 ANSI: 5
[ 3.653345] sr1: scsi3-mmc drive: 4x/48x cd/rw xa/form2 cdda tray
[ 3.653433] sr 1:0:0:0: Attached scsi CD-ROM sr1
[ 3.653474] sr 1:0:0:0: Attached scsi generic sg2 type 5
[ 3.660425] sda1 sda2 < sda5 >
[ 3.680105] sd 0:0:0:0: [sda] Attached SCSI disk
[ 3.680183] Freeing unused kernel memory: 564k freed
[ 3.680284] Write protecting the kernel read-only data: 6144k
[ 3.680524] Freeing unused kernel memory: 208k freed
[ 3.680620] Freeing unused kernel memory: 16k freed
[ 3.729288] e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2
[ 3.729291] e1000e: Copyright (c) 1999 - 2009 Intel Corporation.
[ 3.729331] alloc irq_desc for 20 on node -1
[ 3.729333] alloc kstat_irqs on node -1
[ 3.729340] e1000e 0000:00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[ 3.729343] e1000e 0000:00:19.0: using 64bit DMA mask
[ 3.729345] e1000e 0000:00:19.0: using 64bit consistent DMA mask
[ 3.729353] e1000e 0000:00:19.0: setting latency timer to 64
[ 3.729456] alloc irq_desc for 29 on node -1
[ 3.729458] alloc kstat_irqs on node -1
[ 3.729465] e1000e 0000:00:19.0: irq 29 for MSI/MSI-X
[ 3.738405] ohci1394 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 3.738410] ohci1394 0000:02:00.0: calling quirk_via_vlink+0x0/0xc5
[ 3.738417] ohci1394 0000:02:00.0: setting latency timer to 64
[ 3.791856] ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[17] MMIO=[fbdff800-fbdfffff] Max Packet=[2048] IR/IT contexts=[4/8]
[ 4.261169] 0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1) 00:24:e8:08:87:ea
[ 4.261172] 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
[ 4.261194] 0000:00:19.0: eth0: MAC: 7, PHY: 8, PBA No: ffffff-0ff
[ 4.496790] kjournald starting. Commit interval 5 seconds
[ 4.496797] EXT3-fs (sda1): mounted filesystem with writeback data mode
[ 5.109184] ieee1394: Host added: ID:BUS[0-00:1023] GUID[0024e880000887ea]
[ 7.241517] Adding 36041788k swap on /dev/sda5. Priority:-1 extents:1 across:36041788k
[ 7.856346] EXT3-fs (sda1): using internal journal
[ 7.901304] udev: starting version 149
[ 9.313567] dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2)
[ 9.588770] lp: driver loaded but no devices found
[ 12.650741] mv[3151]: segfault at 7ffeffffd298 ip 00007fe905e5b305 sp 00007ffeffffd2a0 error 6 in libattr.so.1.1.0[7fe905e59000+4000]
[ 13.389059] e1000e 0000:00:19.0: irq 29 for MSI/MSI-X
[ 13.448775] e1000e 0000:00:19.0: irq 29 for MSI/MSI-X
[ 13.450603] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 16.529376] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[ 16.531141] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 17.064835] pci 0000:04:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 22.210996] CPUFREQ: Per core ondemand sysfs interface is deprecated - ignore_nice_load
[ 25.946469] ppdev: user-space parallel port driver
[ 26.904410] eth0: no IPv6 routers present
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: acpi_idle: Very idle Core i7 machine never enters C3
2010-02-05 16:09 ` Jeff Garrett
@ 2010-02-05 17:45 ` Len Brown
2010-02-05 20:53 ` Jeff Garrett
2010-04-27 2:40 ` Philip Langdale
0 siblings, 2 replies; 54+ messages in thread
From: Len Brown @ 2010-02-05 17:45 UTC (permalink / raw)
To: Jeff Garrett; +Cc: Andi Kleen, linux-kernel, linux-acpi
Jeff,
What do you see if you apply just the patch below?
Also, in addition to "powertop -d" to show what the kernel requests,
please run turbostat to show what the hardware actually did:
http://userweb.kernel.org/~lenb/acpi/utils/pmtools-latest/turbostat/turbostat.c
eg.
# turbostat -d -v sleep 5
thanks,
-Len Brown, Intel Open Source Technology Center
---
diff --git a/drivers/acpi/processor_idle.c b/drivers/acpi/processor_idle.c
index 7c0441f..f528625 100644
--- a/drivers/acpi/processor_idle.c
+++ b/drivers/acpi/processor_idle.c
@@ -763,7 +763,7 @@ static const struct file_operations acpi_processor_power_fops = {
static int acpi_idle_bm_check(void)
{
u32 bm_status = 0;
-
+return bm_status;
acpi_read_bit_register(ACPI_BITREG_BUS_MASTER_STATUS, &bm_status);
if (bm_status)
acpi_write_bit_register(ACPI_BITREG_BUS_MASTER_STATUS, 1);
^ permalink raw reply related [flat|nested] 54+ messages in thread
* Re: acpi_idle: Very idle Core i7 machine never enters C3
2010-02-05 17:45 ` Len Brown
@ 2010-02-05 20:53 ` Jeff Garrett
2010-04-27 2:40 ` Philip Langdale
1 sibling, 0 replies; 54+ messages in thread
From: Jeff Garrett @ 2010-02-05 20:53 UTC (permalink / raw)
To: Len Brown; +Cc: Andi Kleen, linux-kernel, linux-acpi
[-- Attachment #1: Type: text/plain, Size: 1710 bytes --]
On Fri, Feb 05, 2010 at 12:45:21PM -0500, Len Brown wrote:
> Jeff,
> What do you see if you apply just the patch below?
>
> Also, in addition to "powertop -d" to show what the kernel requests,
> please run turbostat to show what the hardware actually did:
>
> http://userweb.kernel.org/~lenb/acpi/utils/pmtools-latest/turbostat/turbostat.c
>
> eg.
> # turbostat -d -v sleep 5
>
> thanks,
> -Len Brown, Intel Open Source Technology Center
With the patch, powertop reports good C3 residency and wakeups
remain very low. Seems to work. :)
I attached the powertop & turbostat output with this patch.
However, this confuses me. In a previous experiment in the
acpi_processor_setup_cpuidle() function, I replaced the pointer
to acpi_idle_enter_bm() with a pointer to
acpi_idle_enter_simple() even when bm_check is nonzero. With
that, I was able to get into C3, but the wakeups ballooned. But
the difference between what I did, and what you did, is the
difference between acpi_idle_enter_bm() with acpi_idle_bm_check()
returning zero and acpi_idle_enter_simple(). Those code paths
look almost identical. The bm path calls acpi_unlazy_tlb(), and
doesn't appear to call the ACPI_FLUSH_CPU_CACHE(), and they call
sched_clock_idle_sleep_event() in different places. I don't
understand why any of these differences would have had any
significant effect on wakeups.
I'm left wondering if it's a problem on my part. I should repeat
that previous experiment and see if there really is something
significantly different there.
BTW, getting a bit off topic, but since the two code paths are
almost identical, is there any reason not to unite them?
Something like the attached patch might work?
Thanks,
Jeff
[-- Attachment #2: powertop.out --]
[-- Type: text/plain, Size: 1829 bytes --]
PowerTOP 1.12 (C) 2007, 2008 Intel Corporation
Collecting data for 15 seconds
Cn Avg residency
C0 (cpu running) ( 2.7%)
polling 0.0ms ( 0.0%)
C1 mwait 0.0ms ( 0.0%)
C2 mwait 0.0ms ( 0.0%)
C3 mwait 151.8ms (97.3%)
P-states (frequencies)
Turbo Mode 0.0%
2.67 Ghz 0.0%
2.54 Ghz 0.0%
2.40 Ghz 0.0%
1.60 Ghz 100.0%
Wakeups-from-idle per second : 6.4 interval: 15.0s
no ACPI power usage estimate available
Top causes for wakeups:
38.4% ( 11.2) [extra timer interrupt]
29.7% ( 8.7) [kernel scheduler] Load balancing tick
11.2% ( 3.3) [kernel core] hrtimer_start (tick_sched_timer)
7.1% ( 2.1) [Rescheduling interrupts] <kernel IPI>
6.9% ( 2.0) [kernel core] add_timer_on (clocksource_watchdog)
1.8% ( 0.5) events/3
1.6% ( 0.5) [eth0] <interrupt>
0.7% ( 0.2) [kernel core] __mod_timer (dev_watchdog)
0.5% ( 0.1) [ata_piix, ata_piix] <interrupt>
0.2% ( 0.1) [kernel core] __mod_timer (tcp_delack_timer)
0.2% ( 0.1) sshd
0.2% ( 0.1) [kernel core] enqueue_task_rt (sched_rt_period_timer)
0.2% ( 0.1) expr
0.2% ( 0.1) [kernel core] __mod_timer (cfq_idle_slice_timer)
0.2% ( 0.1) [kernel core] queue_delayed_work (delayed_work_timer_fn)
0.2% ( 0.1) [kernel core] __mod_timer (peer_check_expire)
0.2% ( 0.1) [kernel core] __mod_timer (neigh_timer_handler)
0.2% ( 0.1) [kernel core] __mod_timer (sync_supers_timer_fn)
Suggestion: Enable the CONFIG_USB_SUSPEND kernel configuration option.
This option will automatically disable UHCI USB when not in use, and may
save approximately 1 Watt of power.
Recent USB suspend statistics
Active Device name
Recent audio activity statistics
Active Device name
Recent SATA AHCI link activity statistics
Active Partial Slumber Device name
[-- Attachment #3: turbostat.out --]
[-- Type: text/plain, Size: 1089 bytes --]
turbostat Jan-27, 2010 - Len Brown <lenb@kernel.org>
num_cpus 8
CPUID GenuineIntel 11 levels family:model:stepping 6:26:4
Nehalem multiplier 20, TSC frequency 2667 MHz
MSR_NEHALEM_PLATFORM_INFO: 0xc0000001400
Nehalem 4 cores active: 21 mult, max turbo frequency = 2800 MHz
Nehalem 3 cores active: 21 mult, max turbo frequency = 2800 MHz
Nehalem 2 cores active: 21 mult, max turbo frequency = 2800 MHz
Nehalem 1 core active: 22 mult, max turbo frequency = 2933 MHz
5.002349 sec
CPU GHz TSC %c0 %c1 %c3 %c6 %pc3 %pc6 %pc7
0 1.60 2.66 0.02 0.07 0.00 99.92 0.00 0.00 0.00
1 1.60 2.66 0.01 0.02 0.00 99.97 0.00 0.00 0.00
2 1.60 2.66 0.02 0.04 0.00 99.94 0.00 0.00 0.00
3 1.60 2.66 0.09 0.13 0.00 99.78 0.00 0.00 0.00
4 1.60 2.66 0.05 0.04 0.00 99.91 0.00 0.00 0.00
5 1.60 2.66 0.01 0.02 0.00 99.97 0.00 0.00 0.00
6 1.60 2.66 0.01 0.05 0.00 99.94 0.00 0.00 0.00
7 1.59 2.66 0.05 0.16 0.00 99.79 0.00 0.00 0.00
[-- Attachment #4: patch --]
[-- Type: text/plain, Size: 4741 bytes --]
diff --git a/drivers/acpi/processor_idle.c b/drivers/acpi/processor_idle.c
index 7c0441f..8c636de 100644
--- a/drivers/acpi/processor_idle.c
+++ b/drivers/acpi/processor_idle.c
@@ -849,73 +851,6 @@ static int acpi_idle_enter_c1(struct cpuidle_device *dev,
return idle_time;
}
-/**
- * acpi_idle_enter_simple - enters an ACPI state without BM handling
- * @dev: the target CPU
- * @state: the state data
- */
-static int acpi_idle_enter_simple(struct cpuidle_device *dev,
- struct cpuidle_state *state)
-{
- struct acpi_processor *pr;
- struct acpi_processor_cx *cx = cpuidle_get_statedata(state);
- ktime_t kt1, kt2;
- s64 idle_time;
- s64 sleep_ticks = 0;
-
- pr = __get_cpu_var(processors);
-
- if (unlikely(!pr))
- return 0;
-
- if (acpi_idle_suspend)
- return(acpi_idle_enter_c1(dev, state));
-
- local_irq_disable();
- current_thread_info()->status &= ~TS_POLLING;
- /*
- * TS_POLLING-cleared state must be visible before we test
- * NEED_RESCHED:
- */
- smp_mb();
-
- if (unlikely(need_resched())) {
- current_thread_info()->status |= TS_POLLING;
- local_irq_enable();
- return 0;
- }
-
- /*
- * Must be done before busmaster disable as we might need to
- * access HPET !
- */
- lapic_timer_state_broadcast(pr, cx, 1);
-
- if (cx->type == ACPI_STATE_C3)
- ACPI_FLUSH_CPU_CACHE();
-
- kt1 = ktime_get_real();
- /* Tell the scheduler that we are going deep-idle: */
- sched_clock_idle_sleep_event();
- acpi_idle_do_entry(cx);
- kt2 = ktime_get_real();
- idle_time = ktime_to_us(ktime_sub(kt2, kt1));
-
- sleep_ticks = us_to_pm_timer_ticks(idle_time);
-
- /* Tell the scheduler how much we idled: */
- sched_clock_idle_wakeup_event(sleep_ticks*PM_TIMER_TICK_NS);
-
- local_irq_enable();
- current_thread_info()->status |= TS_POLLING;
-
- cx->usage++;
-
- lapic_timer_state_broadcast(pr, cx, 0);
- cx->time += sleep_ticks;
- return idle_time;
-}
-
static int c3_cpu_count;
static DEFINE_SPINLOCK(c3_lock);
@@ -944,7 +879,7 @@ static int acpi_idle_enter_bm(struct cpuidle_device *dev,
if (acpi_idle_suspend)
return(acpi_idle_enter_c1(dev, state));
- if (acpi_idle_bm_check()) {
+ if (cx->type == ACPI_STATE_C3 && pr->flags.bm_check && acpi_idle_bm_check()) {
if (dev->safe_state) {
dev->last_state = dev->safe_state;
return dev->safe_state->enter(dev, dev->safe_state);
@@ -970,17 +905,24 @@ static int acpi_idle_enter_bm(struct cpuidle_device *dev,
return 0;
}
- acpi_unlazy_tlb(smp_processor_id());
+ if (cx->type == ACPI_STATE_C3 && pr->flags.bm_check)
+ acpi_unlazy_tlb(smp_processor_id());
/* Tell the scheduler that we are going deep-idle: */
- sched_clock_idle_sleep_event();
+ if (cx->type == ACPI_STATE_C3 && pr->flags.bm_check)
+ sched_clock_idle_sleep_event();
/*
* Must be done before busmaster disable as we might need to
* access HPET !
*/
lapic_timer_state_broadcast(pr, cx, 1);
+ if (cx->type == ACPI_STATE_C3 && !pr->flags.bm_check)
+ ACPI_FLUSH_CPU_CACHE();
+
kt1 = ktime_get_real();
+ if (cx->type != ACPI_STATE_C3 || !pr->flags.bm_check)
+ sched_clock_idle_sleep_event();
/*
* disable bus master
* bm_check implies we need ARB_DIS
@@ -991,21 +933,19 @@ static int acpi_idle_enter_bm(struct cpuidle_device *dev,
* not set. In that case we cannot do much, we enter C3
* without doing anything.
*/
- if (pr->flags.bm_check && pr->flags.bm_control) {
+ if (cx->type == ACPI_STATE_C3 && pr->flags.bm_check && pr->flags.bm_control) {
spin_lock(&c3_lock);
c3_cpu_count++;
/* Disable bus master arbitration when all CPUs are in C3 */
if (c3_cpu_count == num_online_cpus())
acpi_write_bit_register(ACPI_BITREG_ARB_DISABLE, 1);
spin_unlock(&c3_lock);
- } else if (!pr->flags.bm_check) {
- ACPI_FLUSH_CPU_CACHE();
}
acpi_idle_do_entry(cx);
/* Re-enable bus master arbitration */
- if (pr->flags.bm_check && pr->flags.bm_control) {
+ if (cx->type == ACPI_STATE_C3 && pr->flags.bm_check && pr->flags.bm_control) {
spin_lock(&c3_lock);
acpi_write_bit_register(ACPI_BITREG_ARB_DISABLE, 0);
c3_cpu_count--;
@@ -1095,7 +1035,7 @@ static int acpi_processor_setup_cpuidle(struct acpi_processor *pr)
case ACPI_STATE_C2:
state->flags |= CPUIDLE_FLAG_BALANCED;
state->flags |= CPUIDLE_FLAG_TIME_VALID;
- state->enter = acpi_idle_enter_simple;
+ state->enter = acpi_idle_enter_bm;
dev->safe_state = state;
break;
@@ -1103,9 +1043,7 @@ static int acpi_processor_setup_cpuidle(struct acpi_processor *pr)
state->flags |= CPUIDLE_FLAG_DEEP;
state->flags |= CPUIDLE_FLAG_TIME_VALID;
state->flags |= CPUIDLE_FLAG_CHECK_BM;
- state->enter = pr->flags.bm_check ?
- acpi_idle_enter_bm :
- acpi_idle_enter_simple;
+ state->enter = acpi_idle_enter_bm;
break;
}
^ permalink raw reply related [flat|nested] 54+ messages in thread
* Re: acpi_idle: Very idle Core i7 machine never enters C3
2010-02-05 17:45 ` Len Brown
2010-02-05 20:53 ` Jeff Garrett
@ 2010-04-27 2:40 ` Philip Langdale
2010-04-27 7:26 ` Len Brown
2010-04-27 12:47 ` Jeff Garrett
1 sibling, 2 replies; 54+ messages in thread
From: Philip Langdale @ 2010-04-27 2:40 UTC (permalink / raw)
To: Len Brown; +Cc: Jeff Garrett, Andi Kleen, linux-kernel, linux-acpi
On Fri, 05 Feb 2010 12:45:21 -0500 (EST)
Len Brown <lenb@kernel.org> wrote:
> Jeff,
> What do you see if you apply just the patch below?
>
> Also, in addition to "powertop -d" to show what the kernel requests,
> please run turbostat to show what the hardware actually did:
>
> http://userweb.kernel.org/~lenb/acpi/utils/pmtools-latest/turbostat/turbostat.c
>
> eg.
> # turbostat -d -v sleep 5
>
> thanks,
> -Len Brown, Intel Open Source Technology Center
> ---
To resurrect this thread...
I have a giga-byte GA-P55M-UD4 motherboard and I have this same problem
as well. Len's patch "works" in that I see C6 being used, but it also
cripples the system - if I do a make -j16 kernel build, I see most jobs
serialized onto one or two cores. Without the patch, I see the
full utilization of all 8 hyper-threads as expected.
Now, gigabyte have already b0rked these boards up by using the UHCI
controllers on the PCH instead of the rate matching hubs. Maybe that's
directly the cause of BM activity - maybe they screwed something else
up - is it possible for BIOS/ACPI mistakes to lead to this behaviour?
Jeff - is your board gigabyte too?
--phil
> diff --git a/drivers/acpi/processor_idle.c
> b/drivers/acpi/processor_idle.c index 7c0441f..f528625 100644
> --- a/drivers/acpi/processor_idle.c
> +++ b/drivers/acpi/processor_idle.c
> @@ -763,7 +763,7 @@ static const struct file_operations
> acpi_processor_power_fops = { static int acpi_idle_bm_check(void)
> {
> u32 bm_status = 0;
> -
> +return bm_status;
> acpi_read_bit_register(ACPI_BITREG_BUS_MASTER_STATUS,
> &bm_status); if (bm_status)
> acpi_write_bit_register(ACPI_BITREG_BUS_MASTER_STATUS,
> 1);
>
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
>
--phil
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: acpi_idle: Very idle Core i7 machine never enters C3
2010-04-27 2:40 ` Philip Langdale
@ 2010-04-27 7:26 ` Len Brown
2010-04-27 15:41 ` Philip Langdale
2010-04-27 12:47 ` Jeff Garrett
1 sibling, 1 reply; 54+ messages in thread
From: Len Brown @ 2010-04-27 7:26 UTC (permalink / raw)
To: Philip Langdale; +Cc: Jeff Garrett, Andi Kleen, linux-kernel, linux-acpi
On Mon, 26 Apr 2010, Philip Langdale wrote:
> On Fri, 05 Feb 2010 12:45:21 -0500 (EST)
> Len Brown <lenb@kernel.org> wrote:
>
> > Jeff,
> > What do you see if you apply just the patch below?
> >
> > Also, in addition to "powertop -d" to show what the kernel requests,
> > please run turbostat to show what the hardware actually did:
> >
> > http://userweb.kernel.org/~lenb/acpi/utils/pmtools-latest/turbostat/turbostat.c
> >
> > eg.
> > # turbostat -d -v sleep 5
> >
> > thanks,
> > -Len Brown, Intel Open Source Technology Center
> > ---
>
> To resurrect this thread...
>
> I have a giga-byte GA-P55M-UD4 motherboard and I have this same problem
> as well. Len's patch "works" in that I see C6 being used, but it also
> cripples the system - if I do a make -j16 kernel build, I see most jobs
> serialized onto one or two cores. Without the patch, I see the
> full utilization of all 8 hyper-threads as expected.
Curious failure.
I could imagine that there is something in the design of this board
where we want to not enter a deep C-state, and thus the board and
Linux are doing the right thing by avoiding the C-state.
However, ignoring the bm-status check and blindly going to that state
I would expect to impact throughput and latency, but don't see
how that might 'serialize' the workload or otherwise cause it
to use some cores and not others.
It is possible that we jump into those deep states just to be
immediately forced to jump right back out. You'd see this in
high usage counts under /sys/devices/system/cpu/cpu*/cpuidle
turbostat, of course, would tell you the actual residency in those states.
Of course there is a twist... The hardware has a feature to recognize
thrashing and may demote an OS request for a deep state into
an actual hardware request for a shallower state. this is one reason
that the output of powertop (request) and turbostat (result)
may be different.
cheers,
-Len
> Now, gigabyte have already b0rked these boards up by using the UHCI
> controllers on the PCH instead of the rate matching hubs. Maybe that's
> directly the cause of BM activity - maybe they screwed something else
> up - is it possible for BIOS/ACPI mistakes to lead to this behaviour?
>
> Jeff - is your board gigabyte too?
>
> --phil
>
> > diff --git a/drivers/acpi/processor_idle.c
> > b/drivers/acpi/processor_idle.c index 7c0441f..f528625 100644
> > --- a/drivers/acpi/processor_idle.c
> > +++ b/drivers/acpi/processor_idle.c
> > @@ -763,7 +763,7 @@ static const struct file_operations
> > acpi_processor_power_fops = { static int acpi_idle_bm_check(void)
> > {
> > u32 bm_status = 0;
> > -
> > +return bm_status;
> > acpi_read_bit_register(ACPI_BITREG_BUS_MASTER_STATUS,
> > &bm_status); if (bm_status)
> > acpi_write_bit_register(ACPI_BITREG_BUS_MASTER_STATUS,
> > 1);
> >
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: acpi_idle: Very idle Core i7 machine never enters C3
2010-04-27 2:40 ` Philip Langdale
2010-04-27 7:26 ` Len Brown
@ 2010-04-27 12:47 ` Jeff Garrett
2010-04-30 14:57 ` Philip Langdale
` (2 more replies)
1 sibling, 3 replies; 54+ messages in thread
From: Jeff Garrett @ 2010-04-27 12:47 UTC (permalink / raw)
To: Philip Langdale; +Cc: Len Brown, Andi Kleen, linux-kernel, linux-acpi
On Mon, Apr 26, 2010 at 07:40:02PM -0700, Philip Langdale wrote:
> On Fri, 05 Feb 2010 12:45:21 -0500 (EST)
> Len Brown <lenb@kernel.org> wrote:
> > Jeff,
> > What do you see if you apply just the patch below?
> >
> > Also, in addition to "powertop -d" to show what the kernel requests,
> > please run turbostat to show what the hardware actually did:
> >
> > http://userweb.kernel.org/~lenb/acpi/utils/pmtools-latest/turbostat/turbostat.c
> >
> > eg.
> > # turbostat -d -v sleep 5
> >
> > thanks,
> > -Len Brown, Intel Open Source Technology Center
> > ---
>
> To resurrect this thread...
>
> I have a giga-byte GA-P55M-UD4 motherboard and I have this same problem
> as well. Len's patch "works" in that I see C6 being used, but it also
> cripples the system - if I do a make -j16 kernel build, I see most jobs
> serialized onto one or two cores. Without the patch, I see the
> full utilization of all 8 hyper-threads as expected.
>
> Now, gigabyte have already b0rked these boards up by using the UHCI
> controllers on the PCH instead of the rate matching hubs. Maybe that's
> directly the cause of BM activity - maybe they screwed something else
> up - is it possible for BIOS/ACPI mistakes to lead to this behaviour?
>
> Jeff - is your board gigabyte too?
>
> --phil
My board identifies it as a Dell. No idea if they rebranded a gigabyte.
The patch seems to work for me as well, powertop shows 97.5% c3,
turbostat shows 93.6% c6 now. I do get weird latency spikes (on I/O)
from time to time.
When I was investigating, I completely configured USB off, and it still
wouldn't go into deep sleep. Not sure how well that meshes with your
UHCI theory.
-Jeff
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: acpi_idle: Very idle Core i7 machine never enters C3
2010-04-27 7:26 ` Len Brown
@ 2010-04-27 15:41 ` Philip Langdale
0 siblings, 0 replies; 54+ messages in thread
From: Philip Langdale @ 2010-04-27 15:41 UTC (permalink / raw)
To: Len Brown; +Cc: Jeff Garrett, Andi Kleen, linux-kernel, linux-acpi
On Tue, 27 Apr 2010 03:26:34 -0400 (EDT)
Len Brown <lenb@kernel.org> wrote:
>
>
> Curious failure.
> I could imagine that there is something in the design of this board
> where we want to not enter a deep C-state, and thus the board and
> Linux are doing the right thing by avoiding the C-state.
> However, ignoring the bm-status check and blindly going to that state
> I would expect to impact throughput and latency, but don't see
> how that might 'serialize' the workload or otherwise cause it
> to use some cores and not others.
Hmm - and now I can't reproduce it. I got proper parallelization across
the kernel compile. I guess some sort of runtime state was messed up,
and I obviously lost that then I rebooted. :-/
> It is possible that we jump into those deep states just to be
> immediately forced to jump right back out. You'd see this in
> high usage counts under /sys/devices/system/cpu/cpu*/cpuidle
>
> turbostat, of course, would tell you the actual residency in those
> states. Of course there is a twist... The hardware has a feature to
> recognize thrashing and may demote an OS request for a deep state into
> an actual hardware request for a shallower state. this is one reason
> that the output of powertop (request) and turbostat (result)
> may be different.
Without the patch, Turbostat showed C3 residency of 99% for most
hyper-threads with one or two getting ~15% C6 residency. PC3 was 75%.
Cores were at their lowest P state.
With the patch, C6 residency is 99%, PC6 is 75% and 7 hyper-threads at
lowest P state with one stubborning running at a higher level.
I have a very similarly configured machine with an asus motherboard and
it doesn't have this problem - which is another reason I'm wondering if
it's an OEM screwup.
--phil
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: acpi_idle: Very idle Core i7 machine never enters C3
2010-04-27 12:47 ` Jeff Garrett
@ 2010-04-30 14:57 ` Philip Langdale
2010-04-30 16:25 ` Len Brown
2010-07-22 5:34 ` Len Brown
2 siblings, 0 replies; 54+ messages in thread
From: Philip Langdale @ 2010-04-30 14:57 UTC (permalink / raw)
To: Jeff Garrett; +Cc: Len Brown, Andi Kleen, linux-kernel, linux-acpi
On Tue, 27 Apr 2010 07:47:03 -0500
jeff@jgarrett.org (Jeff Garrett) wrote:
> My board identifies it as a Dell. No idea if they rebranded a
> gigabyte.
>
> The patch seems to work for me as well, powertop shows 97.5% c3,
> turbostat shows 93.6% c6 now. I do get weird latency spikes (on I/O)
> from time to time.
>
> When I was investigating, I completely configured USB off, and it
> still wouldn't go into deep sleep. Not sure how well that meshes
> with your UHCI theory.
Does your board expose UHCI controllers or just EHCI with the rate
matching hubs? When you say 'configured USB off'?, do you mean off
in the BIOS or just no drivers?
--phil
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: acpi_idle: Very idle Core i7 machine never enters C3
@ 2010-04-30 14:57 ` Philip Langdale
0 siblings, 0 replies; 54+ messages in thread
From: Philip Langdale @ 2010-04-30 14:57 UTC (permalink / raw)
To: Jeff Garrett; +Cc: Len Brown, Andi Kleen, linux-kernel, linux-acpi
On Tue, 27 Apr 2010 07:47:03 -0500
jeff@jgarrett.org (Jeff Garrett) wrote:
> My board identifies it as a Dell. No idea if they rebranded a
> gigabyte.
>
> The patch seems to work for me as well, powertop shows 97.5% c3,
> turbostat shows 93.6% c6 now. I do get weird latency spikes (on I/O)
> from time to time.
>
> When I was investigating, I completely configured USB off, and it
> still wouldn't go into deep sleep. Not sure how well that meshes
> with your UHCI theory.
Does your board expose UHCI controllers or just EHCI with the rate
matching hubs? When you say 'configured USB off'?, do you mean off
in the BIOS or just no drivers?
--phil
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: acpi_idle: Very idle Core i7 machine never enters C3
2010-04-27 12:47 ` Jeff Garrett
2010-04-30 14:57 ` Philip Langdale
@ 2010-04-30 16:25 ` Len Brown
2010-04-30 17:44 ` Matthew Garrett
2010-07-22 5:34 ` Len Brown
2 siblings, 1 reply; 54+ messages in thread
From: Len Brown @ 2010-04-30 16:25 UTC (permalink / raw)
To: Jeff Garrett; +Cc: Philip Langdale, Andi Kleen, linux-kernel, linux-acpi
Philip, Jeff,
Please open up a bugzilla.kernel.org report and attach the output from
acpidump from your machines.
I am hopeful that the "right thin to do" is to not look at bm-status
and that perhaps there is a bug where we are looking at it
"by mistake".
However, it is important that the system be operating properly
when it indeed using c6 as it does with that 1 line patch
earlier in this thread. So if that patch causes abnormal
operation, please let me know.
thanks,
Len Brown, Intel Open Source Technology Center
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: acpi_idle: Very idle Core i7 machine never enters C3
2010-04-30 16:25 ` Len Brown
@ 2010-04-30 17:44 ` Matthew Garrett
2010-04-30 18:35 ` Philip Langdale
0 siblings, 1 reply; 54+ messages in thread
From: Matthew Garrett @ 2010-04-30 17:44 UTC (permalink / raw)
To: Len Brown
Cc: Jeff Garrett, Philip Langdale, Andi Kleen, linux-kernel, linux-acpi
On Fri, Apr 30, 2010 at 12:25:44PM -0400, Len Brown wrote:
> I am hopeful that the "right thin to do" is to not look at bm-status
> and that perhaps there is a bug where we are looking at it
> "by mistake".
https://patchwork.kernel.org/patch/58962/ - it seems to be a win.
--
Matthew Garrett | mjg59@srcf.ucam.org
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: acpi_idle: Very idle Core i7 machine never enters C3
2010-04-30 17:44 ` Matthew Garrett
@ 2010-04-30 18:35 ` Philip Langdale
0 siblings, 0 replies; 54+ messages in thread
From: Philip Langdale @ 2010-04-30 18:35 UTC (permalink / raw)
To: Matthew Garrett
Cc: Len Brown, Jeff Garrett, Andi Kleen, linux-kernel, linux-acpi
On Fri, 30 Apr 2010 18:44:47 +0100, Matthew Garrett <mjg59@srcf.ucam.org>
wrote:
> On Fri, Apr 30, 2010 at 12:25:44PM -0400, Len Brown wrote:
>
>> I am hopeful that the "right thin to do" is to not look at bm-status
>> and that perhaps there is a bug where we are looking at it
>> "by mistake".
>
> https://patchwork.kernel.org/patch/58962/ - it seems to be a win.
Indeed. This patch does solve the C6 problem. I'm not in a position to
speak about whether there's any undesirable I/O latency, but it
passes the basic sanity check.
I have filed https://bugzilla.kernel.org/show_bug.cgi?id=15886 with
my acpi dump - assuming that's still useful.
--phil
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: acpi_idle: Very idle Core i7 machine never enters C3
@ 2010-04-30 18:35 ` Philip Langdale
0 siblings, 0 replies; 54+ messages in thread
From: Philip Langdale @ 2010-04-30 18:35 UTC (permalink / raw)
To: Matthew Garrett
Cc: Len Brown, Jeff Garrett, Andi Kleen, linux-kernel, linux-acpi
On Fri, 30 Apr 2010 18:44:47 +0100, Matthew Garrett <mjg59@srcf.ucam.org>
wrote:
> On Fri, Apr 30, 2010 at 12:25:44PM -0400, Len Brown wrote:
>
>> I am hopeful that the "right thin to do" is to not look at bm-status
>> and that perhaps there is a bug where we are looking at it
>> "by mistake".
>
> https://patchwork.kernel.org/patch/58962/ - it seems to be a win.
Indeed. This patch does solve the C6 problem. I'm not in a position to
speak about whether there's any undesirable I/O latency, but it
passes the basic sanity check.
I have filed https://bugzilla.kernel.org/show_bug.cgi?id=15886 with
my acpi dump - assuming that's still useful.
--phil
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: acpi_idle: Very idle Core i7 machine never enters C3
2010-04-30 18:35 ` Philip Langdale
(?)
@ 2010-05-25 5:43 ` Len Brown
2010-05-25 5:59 ` Yu, Luming
2010-05-25 12:37 ` acpi_idle: Very idle Core i7 machine never enters C3 Matthew Garrett
-1 siblings, 2 replies; 54+ messages in thread
From: Len Brown @ 2010-05-25 5:43 UTC (permalink / raw)
To: Philip Langdale
Cc: Matthew Garrett, Jeff Garrett, Andi Kleen,
Linux Kernel Mailing List, linux-acpi, luming.yu, venki
> >> I am hopeful that the "right thing to do" is to not look at bm-status
> >> and that perhaps there is a bug where we are looking at it
> >> "by mistake".
> >
> > https://patchwork.kernel.org/patch/58962/ - it seems to be a win.
>
> Indeed. This patch does solve the C6 problem. I'm not in a position to
> speak about whether there's any undesirable I/O latency, but it
> passes the basic sanity check.
>
> I have filed https://bugzilla.kernel.org/show_bug.cgi?id=15886 with
> my acpi dump - assuming that's still useful.
Luming's patch above basically deletes acpi_idle_bm_check() --
the BM_STS check -- from the C3 path on all Intel SMP boxes.
This is effectively the same as my test patch
https://patchwork.kernel.org/patch/77370/
that made acpi_idle_bm_check() do nothing.
I'm told by the hardware guys that BM_STS is _not_ always
a NOP, and so we're not supposed to simply ignore it on C3 --
though it should be extremely rare that we see it set.
If it is ever set, it should go on and off depending on
activity on some latency sensitive device, like out on the LPC.
It may be possible for the BIOS writer to configure the chipset
so that BM_STS is enabled always, presumably to accomodate
some latency sensitve device -- or maybe by mistake.
(is it observed to be set always on your systems, or does
it ever change its value?)
The logic in Luming's patch doesn't make sense to me.
bm_check and bm_control are related to C3 need to flush
the cache or ability to invoke ARB_DIS. They are not
directly related to BM_STS -- which is a bit that tells
us if there has recently been bus master activity of
a type that would break us out of C3.
-Len Brown, Intel Open Source Technology Center
^ permalink raw reply [flat|nested] 54+ messages in thread
* RE: acpi_idle: Very idle Core i7 machine never enters C3
2010-05-25 5:43 ` Len Brown
@ 2010-05-25 5:59 ` Yu, Luming
2010-05-25 12:39 ` Matthew Garrett
2010-05-25 12:43 ` Matthew Garrett
2010-05-25 12:37 ` acpi_idle: Very idle Core i7 machine never enters C3 Matthew Garrett
1 sibling, 2 replies; 54+ messages in thread
From: Yu, Luming @ 2010-05-25 5:59 UTC (permalink / raw)
To: Len Brown, Philip Langdale
Cc: Matthew Garrett, Jeff Garrett, Andi Kleen,
Linux Kernel Mailing List, linux-acpi, venki
> -----Original Message-----
> From: Len Brown [mailto:lenb@kernel.org]
> Sent: Tuesday, May 25, 2010 1:43 PM
> To: Philip Langdale
> Cc: Matthew Garrett; Jeff Garrett; Andi Kleen; Linux Kernel Mailing
> List; linux-acpi@vger.kernel.org; Yu, Luming; venki@google.com
> Subject: Re: acpi_idle: Very idle Core i7 machine never enters C3
>
> > >> I am hopeful that the "right thing to do" is to not look at bm-
> status
> > >> and that perhaps there is a bug where we are looking at it
> > >> "by mistake".
> > >
> > > https://patchwork.kernel.org/patch/58962/ - it seems to be a win.
> >
> > Indeed. This patch does solve the C6 problem. I'm not in a position
> to
> > speak about whether there's any undesirable I/O latency, but it
> > passes the basic sanity check.
> >
> > I have filed https://bugzilla.kernel.org/show_bug.cgi?id=15886 with
> > my acpi dump - assuming that's still useful.
>
> Luming's patch above basically deletes acpi_idle_bm_check() --
> the BM_STS check -- from the C3 path on all Intel SMP boxes.
> This is effectively the same as my test patch
> https://patchwork.kernel.org/patch/77370/
> that made acpi_idle_bm_check() do nothing.
>
> I'm told by the hardware guys that BM_STS is _not_ always
> a NOP, and so we're not supposed to simply ignore it on C3 --
> though it should be extremely rare that we see it set.
On some platforms like NHM-EX, I was told that it's a NOP,
But I might be given wrong information at that time when I wrote that patch.
IIRC, acpi spec just say it's optional..
Thanks,
Luming
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: acpi_idle: Very idle Core i7 machine never enters C3
2010-05-25 5:43 ` Len Brown
2010-05-25 5:59 ` Yu, Luming
@ 2010-05-25 12:37 ` Matthew Garrett
2010-05-25 15:40 ` Len Brown
1 sibling, 1 reply; 54+ messages in thread
From: Matthew Garrett @ 2010-05-25 12:37 UTC (permalink / raw)
To: Len Brown
Cc: Philip Langdale, Jeff Garrett, Andi Kleen,
Linux Kernel Mailing List, linux-acpi, luming.yu, venki
On Tue, May 25, 2010 at 01:43:26AM -0400, Len Brown wrote:
> I'm told by the hardware guys that BM_STS is _not_ always
> a NOP, and so we're not supposed to simply ignore it on C3 --
> though it should be extremely rare that we see it set.
> If it is ever set, it should go on and off depending on
> activity on some latency sensitive device, like out on the LPC.
> It may be possible for the BIOS writer to configure the chipset
> so that BM_STS is enabled always, presumably to accomodate
> some latency sensitve device -- or maybe by mistake.
On some hardware we've seen BM_STS be enabled approximately 50% of the
time without any obvious cause.
--
Matthew Garrett | mjg59@srcf.ucam.org
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: acpi_idle: Very idle Core i7 machine never enters C3
2010-05-25 5:59 ` Yu, Luming
@ 2010-05-25 12:39 ` Matthew Garrett
2010-05-25 12:43 ` Matthew Garrett
1 sibling, 0 replies; 54+ messages in thread
From: Matthew Garrett @ 2010-05-25 12:39 UTC (permalink / raw)
To: Yu, Luming
Cc: Len Brown, Philip Langdale, Jeff Garrett, Andi Kleen,
Linux Kernel Mailing List, linux-acpi, venki
On Tue, May 25, 2010 at 01:59:39PM +0800, Yu, Luming wrote:
> On some platforms like NHM-EX, I was told that it's a NOP,
> But I might be given wrong information at that time when I wrote that patch.
>
> IIRC, acpi spec just say it's optional..
Implementing it is optional, but the spec implies that it should be used
if it's present.
--
Matthew Garrett | mjg59@srcf.ucam.org
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: acpi_idle: Very idle Core i7 machine never enters C3
2010-05-25 5:59 ` Yu, Luming
@ 2010-05-25 12:43 ` Matthew Garrett
2010-05-25 12:43 ` Matthew Garrett
1 sibling, 0 replies; 54+ messages in thread
From: Matthew Garrett @ 2010-05-25 12:43 UTC (permalink / raw)
To: Yu, Luming
Cc: Len Brown, Philip Langdale, Jeff Garrett, Andi Kleen,
Linux Kernel Mailing List, linux-acpi, venki
On the other hand, the relevant section of spec is:
"OSPM uses the BM_STS bit to determine the power state to enter when
considering a transition to or from the C2/C3 power state. The BM_STS is
an optional bit that indicates when bus masters are active. OSPM uses
this bit to determine the policy between the C2 and C3 power states: a
lot of bus master activity demotes the CPU power state to the C2 (or C1
if C2 is not supported), no bus master activity promotes the CPU power
state to the C3 power state. OSPM keeps a running history of the BM_STS
bit to determine CPU power state policy."
while the description of the bit itself is:
"This is the bus master status bit. This bit is set any time a system
bus master requests the system bus, and can only be cleared by writing a
“1” to this bit position. Notice that this bit reflects bus master
activity, not CPU activity (this bit monitors any bus master that can
cause an incoherent cache for a processor in the C3 state when the bus
master performs a memory transaction)."
which implies that as long as you don't have any cache coherency
concerns, it's acceptable (if potentially suboptimal) to enter C3 even
if the bit is set.
--
Matthew Garrett | mjg59@srcf.ucam.org
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: acpi_idle: Very idle Core i7 machine never enters C3
@ 2010-05-25 12:43 ` Matthew Garrett
0 siblings, 0 replies; 54+ messages in thread
From: Matthew Garrett @ 2010-05-25 12:43 UTC (permalink / raw)
To: Yu, Luming
Cc: Len Brown, Philip Langdale, Jeff Garrett, Andi Kleen,
Linux Kernel Mailing List, linux-acpi, venki
On the other hand, the relevant section of spec is:
"OSPM uses the BM_STS bit to determine the power state to enter when
considering a transition to or from the C2/C3 power state. The BM_STS is
an optional bit that indicates when bus masters are active. OSPM uses
this bit to determine the policy between the C2 and C3 power states: a
lot of bus master activity demotes the CPU power state to the C2 (or C1
if C2 is not supported), no bus master activity promotes the CPU power
state to the C3 power state. OSPM keeps a running history of the BM_STS
bit to determine CPU power state policy."
while the description of the bit itself is:
"This is the bus master status bit. This bit is set any time a system
bus master requests the system bus, and can only be cleared by writing a
“1” to this bit position. Notice that this bit reflects bus master
activity, not CPU activity (this bit monitors any bus master that can
cause an incoherent cache for a processor in the C3 state when the bus
master performs a memory transaction)."
which implies that as long as you don't have any cache coherency
concerns, it's acceptable (if potentially suboptimal) to enter C3 even
if the bit is set.
--
Matthew Garrett | mjg59@srcf.ucam.org
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: acpi_idle: Very idle Core i7 machine never enters C3
2010-05-25 12:43 ` Matthew Garrett
(?)
@ 2010-05-25 15:33 ` Len Brown
2010-05-25 18:55 ` Matthew Garrett
-1 siblings, 1 reply; 54+ messages in thread
From: Len Brown @ 2010-05-25 15:33 UTC (permalink / raw)
To: Matthew Garrett
Cc: Yu, Luming, Philip Langdale, Jeff Garrett, Andi Kleen,
Linux Kernel Mailing List, linux-acpi, venki
[-- Attachment #1: Type: TEXT/PLAIN, Size: 3162 bytes --]
On Tue, 25 May 2010, Matthew Garrett wrote:
> On the other hand, the relevant section of spec is:
>
> "OSPM uses the BM_STS bit to determine the power state to enter when
> considering a transition to or from the C2/C3 power state. The BM_STS is
> an optional bit that indicates when bus masters are active. OSPM uses
> this bit to determine the policy between the C2 and C3 power states: a
> lot of bus master activity demotes the CPU power state to the C2 (or C1
> if C2 is not supported), no bus master activity promotes the CPU power
> state to the C3 power state. OSPM keeps a running history of the BM_STS
> bit to determine CPU power state policy."
>
> while the description of the bit itself is:
>
> "This is the bus master status bit. This bit is set any time a system
> bus master requests the system bus, and can only be cleared by writing a
> “1” to this bit position. Notice that this bit reflects bus master
> activity, not CPU activity (this bit monitors any bus master that can
> cause an incoherent cache for a processor in the C3 state when the bus
> master performs a memory transaction)."
>
> which implies that as long as you don't have any cache coherency
> concerns, it's acceptable (if potentially suboptimal) to enter C3 even
> if the bit is set.
As I wrote, the HW people tell me that implication is usually correct,
but there exist cases where it is incorrect. (Of course the way
it is supposed to work is that when BM_STS is not meaningful,
it always returns zero)
The ACPI spec talks about BM_STS being set by traffic that is incoherent
with the frozen cache of C3, requiring a wake up of the processor
from C3 to snoop the traffic. It was written 10 years before the
hardware started automatically snooping the L3 when the processor was off,
and before the hardware learned how to automatically flush the cache
to get into deep C-states. So the description is stale, but the
underlying issue is unchanged. There exist devices which can not
handle the wakeup latency of some deep C-states. The BM_STS bit
is a chip-set bit that the BIOS writer can use to prevent the OS
from using the deep C-states when those devices are active.
I'm told that the cases in question are some legacy devices
hanging off the LPC bus, which should be rare. More interesting
in isochronous traffic over some 1394 controllers -- though
I don't know if Linux runs into that. If we do, one option
would be to ignore BM_STS, but to use pm_qos to disable the
deep c-state when needed -- a mechanism we've used for
several devices in the past.
I believe that the BIOS writer also has the option to keep
BM_STS set always. However, that doesn't make sense to me
as it would be simpler to just disable the C-state in _CST
on that platform.
So if we see a nehalem system that has BM_STS *always* set,
even when no devices are active in the system, my guess is
that the BIOS mis-configured the chip-set and we should
ignore that bit. If BM_STS is changing at run time, then
that is a more interesting situation, and we should endeavor
to find what device activity is changing it.
Len Brown, Intel Open Source Technology Center
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: acpi_idle: Very idle Core i7 machine never enters C3
2010-05-25 12:37 ` acpi_idle: Very idle Core i7 machine never enters C3 Matthew Garrett
@ 2010-05-25 15:40 ` Len Brown
0 siblings, 0 replies; 54+ messages in thread
From: Len Brown @ 2010-05-25 15:40 UTC (permalink / raw)
To: Matthew Garrett
Cc: Philip Langdale, Jeff Garrett, Andi Kleen,
Linux Kernel Mailing List, linux-acpi, luming.yu, venki
> > I'm told by the hardware guys that BM_STS is _not_ always
> > a NOP, and so we're not supposed to simply ignore it on C3 --
> > though it should be extremely rare that we see it set.
> > If it is ever set, it should go on and off depending on
> > activity on some latency sensitive device, like out on the LPC.
> > It may be possible for the BIOS writer to configure the chipset
> > so that BM_STS is enabled always, presumably to accomodate
> > some latency sensitve device -- or maybe by mistake.
>
> On some hardware we've seen BM_STS be enabled approximately 50% of the
> time without any obvious cause.
Assuming it is modern hardware, please get the acpidump and lspci -vv
output from that harware to this bug report:
https://bugzilla.kernel.org/show_bug.cgi?id=15886
thanks,
-Len Brown, Intel Open Source Technology Center
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: acpi_idle: Very idle Core i7 machine never enters C3
2010-05-25 15:33 ` Len Brown
@ 2010-05-25 18:55 ` Matthew Garrett
2010-07-21 21:31 ` [PATCH] ACPI: make acpi_idle Nehalem-aware Len Brown
0 siblings, 1 reply; 54+ messages in thread
From: Matthew Garrett @ 2010-05-25 18:55 UTC (permalink / raw)
To: Len Brown
Cc: Yu, Luming, Philip Langdale, Jeff Garrett, Andi Kleen,
Linux Kernel Mailing List, linux-acpi, venki
On Tue, May 25, 2010 at 11:33:39AM -0400, Len Brown wrote:
> So if we see a nehalem system that has BM_STS *always* set,
> even when no devices are active in the system, my guess is
> that the BIOS mis-configured the chip-set and we should
> ignore that bit. If BM_STS is changing at run time, then
> that is a more interesting situation, and we should endeavor
> to find what device activity is changing it.
Right. Determining that seems... awkward. FWIW, we've been shipping
Luming's patch for several months now without anything obviously
breaking in the process. This behaviour seems reasonably prevelant on
Nehalem-EX systems.
--
Matthew Garrett | mjg59@srcf.ucam.org
^ permalink raw reply [flat|nested] 54+ messages in thread
* [PATCH] ACPI: make acpi_idle Nehalem-aware
2010-05-25 18:55 ` Matthew Garrett
@ 2010-07-21 21:31 ` Len Brown
2010-07-22 0:53 ` Venkatesh Pallipadi
` (2 more replies)
0 siblings, 3 replies; 54+ messages in thread
From: Len Brown @ 2010-07-21 21:31 UTC (permalink / raw)
To: Matthew Garrett
Cc: Yu, Luming, Philip Langdale, Jeff Garrett, Andi Kleen,
Linux Kernel Mailing List, linux-acpi, venki
From: Len Brown <len.brown@intel.com>
The BIOS exports deep C-states on modern Intel processors
as "C3-type" to satisfy various legacy Operating Systems.
However, the hardware actually supports C2-type, and does
not require the extra costs of C3-type.
One of the costs is to check the BM_STS (Bus Master Status)
bit before entering C3, and instead choose a shallower C-state
if there was "recent bus master activity".
We have found a number of systems in the field that erroneously
set BM_STS and prevent entry into deep C-states.
Re-define BIOS presented C3-type states as C2-type states
on modern processors to avoid this issue.
If a device in the system really does want to prevent use
of a deep C-state, its Linux driver should register its
constraints via pm_qos_add_request().
https://bugzilla.kernel.org/show_bug.cgi?id=15886
Signed-off-by: Len Brown <len.brown@intel.com>
---
drivers/acpi/processor_idle.c | 38 ++++++++++++++++++++++++++++++++++++++
1 files changed, 38 insertions(+), 0 deletions(-)
diff --git a/drivers/acpi/processor_idle.c b/drivers/acpi/processor_idle.c
index b1b3856..14d1a0c 100644
--- a/drivers/acpi/processor_idle.c
+++ b/drivers/acpi/processor_idle.c
@@ -607,6 +607,38 @@ static void acpi_processor_power_verify_c3(struct acpi_processor *pr,
return;
}
+/*
+ * Modern Intel processors support only ACPI C2-type C-states.
+ * But the BIOS tends to report its deepest C-state as C3-type
+ * to satisfy various old operating systems. We can skip
+ * C3 OS overhead by treating the deep-states as C2-type.
+ * Also, we can avoid checking BM_STS, which on some systems
+ * erroneously prevents entry into C3-type states.
+ */
+static int acpi_c3type_is_really_c2type(void) {
+
+ if (boot_cpu_data.x86_vendor != X86_VENDOR_INTEL)
+ return 0;
+
+ if (boot_cpu_data.x86 != 6)
+ return 0;
+
+ switch(boot_cpu_data.x86_model) {
+ case 0x1A: /* Core i7, Xeon 5500 series */
+ case 0x1E: /* Core i7 and i5 Processor */
+ case 0x1F: /* Core i7 and i5 Processor */
+ case 0x2E: /* NHM-EX Xeon */
+ case 0x2F: /* WSM-EX Xeon */
+ case 0x25: /* WSM */
+ case 0x2C: /* WSM */
+ case 0x2A: /* SNB */
+ case 0x2D: /* SNB Xeon */
+ return 1;
+ default:
+ return 0;
+ }
+}
+
static int acpi_processor_power_verify(struct acpi_processor *pr)
{
unsigned int i;
@@ -617,6 +649,12 @@ static int acpi_processor_power_verify(struct acpi_processor *pr)
for (i = 1; i < ACPI_PROCESSOR_MAX_POWER && i <= max_cstate; i++) {
struct acpi_processor_cx *cx = &pr->power.states[i];
+ if ((cx->type == ACPI_STATE_C3)
+ && acpi_c3type_is_really_c2type()) {
+ ACPI_DEBUG_PRINT((ACPI_DB_INFO, "Redefining C3-type to C2\n"));
+ cx->type = ACPI_STATE_C2;
+ }
+
switch (cx->type) {
case ACPI_STATE_C1:
cx->valid = 1;
--
1.7.2.rc3.43.g24e7a
^ permalink raw reply related [flat|nested] 54+ messages in thread
* Re: [PATCH] ACPI: make acpi_idle Nehalem-aware
2010-07-21 21:31 ` [PATCH] ACPI: make acpi_idle Nehalem-aware Len Brown
@ 2010-07-22 0:53 ` Venkatesh Pallipadi
2010-07-22 7:47 ` Andi Kleen
2010-08-03 6:55 ` Pavel Machek
2 siblings, 0 replies; 54+ messages in thread
From: Venkatesh Pallipadi @ 2010-07-22 0:53 UTC (permalink / raw)
To: Len Brown
Cc: Matthew Garrett, Yu, Luming, Philip Langdale, Jeff Garrett,
Andi Kleen, Linux Kernel Mailing List, linux-acpi
On Wed, Jul 21, 2010 at 2:31 PM, Len Brown <lenb@kernel.org> wrote:
> From: Len Brown <len.brown@intel.com>
>
> The BIOS exports deep C-states on modern Intel processors
> as "C3-type" to satisfy various legacy Operating Systems.
>
> However, the hardware actually supports C2-type, and does
> not require the extra costs of C3-type.
>
> One of the costs is to check the BM_STS (Bus Master Status)
> bit before entering C3, and instead choose a shallower C-state
> if there was "recent bus master activity".
>
> We have found a number of systems in the field that erroneously
> set BM_STS and prevent entry into deep C-states.
> Re-define BIOS presented C3-type states as C2-type states
> on modern processors to avoid this issue.
>
> If a device in the system really does want to prevent use
> of a deep C-state, its Linux driver should register its
> constraints via pm_qos_add_request().
>
> https://bugzilla.kernel.org/show_bug.cgi?id=15886
>
Agree with the intent. But, I think its cleaner to keep all arch model
checks in arch/x86/kernel/acpi/cstate.c.
Thanks,
Venki
> Signed-off-by: Len Brown <len.brown@intel.com>
> ---
> drivers/acpi/processor_idle.c | 38 ++++++++++++++++++++++++++++++++++++++
> 1 files changed, 38 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/acpi/processor_idle.c b/drivers/acpi/processor_idle.c
> index b1b3856..14d1a0c 100644
> --- a/drivers/acpi/processor_idle.c
> +++ b/drivers/acpi/processor_idle.c
> @@ -607,6 +607,38 @@ static void acpi_processor_power_verify_c3(struct acpi_processor *pr,
> return;
> }
>
> +/*
> + * Modern Intel processors support only ACPI C2-type C-states.
> + * But the BIOS tends to report its deepest C-state as C3-type
> + * to satisfy various old operating systems. We can skip
> + * C3 OS overhead by treating the deep-states as C2-type.
> + * Also, we can avoid checking BM_STS, which on some systems
> + * erroneously prevents entry into C3-type states.
> + */
> +static int acpi_c3type_is_really_c2type(void) {
> +
> + if (boot_cpu_data.x86_vendor != X86_VENDOR_INTEL)
> + return 0;
> +
> + if (boot_cpu_data.x86 != 6)
> + return 0;
> +
> + switch(boot_cpu_data.x86_model) {
> + case 0x1A: /* Core i7, Xeon 5500 series */
> + case 0x1E: /* Core i7 and i5 Processor */
> + case 0x1F: /* Core i7 and i5 Processor */
> + case 0x2E: /* NHM-EX Xeon */
> + case 0x2F: /* WSM-EX Xeon */
> + case 0x25: /* WSM */
> + case 0x2C: /* WSM */
> + case 0x2A: /* SNB */
> + case 0x2D: /* SNB Xeon */
> + return 1;
> + default:
> + return 0;
> + }
> +}
> +
> static int acpi_processor_power_verify(struct acpi_processor *pr)
> {
> unsigned int i;
> @@ -617,6 +649,12 @@ static int acpi_processor_power_verify(struct acpi_processor *pr)
> for (i = 1; i < ACPI_PROCESSOR_MAX_POWER && i <= max_cstate; i++) {
> struct acpi_processor_cx *cx = &pr->power.states[i];
>
> + if ((cx->type == ACPI_STATE_C3)
> + && acpi_c3type_is_really_c2type()) {
> + ACPI_DEBUG_PRINT((ACPI_DB_INFO, "Redefining C3-type to C2\n"));
> + cx->type = ACPI_STATE_C2;
> + }
> +
> switch (cx->type) {
> case ACPI_STATE_C1:
> cx->valid = 1;
> --
> 1.7.2.rc3.43.g24e7a
>
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [PATCH] ACPI: make acpi_idle Nehalem-aware
@ 2010-07-22 0:53 ` Venkatesh Pallipadi
0 siblings, 0 replies; 54+ messages in thread
From: Venkatesh Pallipadi @ 2010-07-22 0:53 UTC (permalink / raw)
To: Len Brown
Cc: Matthew Garrett, Yu, Luming, Philip Langdale, Jeff Garrett,
Andi Kleen, Linux Kernel Mailing List, linux-acpi
On Wed, Jul 21, 2010 at 2:31 PM, Len Brown <lenb@kernel.org> wrote:
> From: Len Brown <len.brown@intel.com>
>
> The BIOS exports deep C-states on modern Intel processors
> as "C3-type" to satisfy various legacy Operating Systems.
>
> However, the hardware actually supports C2-type, and does
> not require the extra costs of C3-type.
>
> One of the costs is to check the BM_STS (Bus Master Status)
> bit before entering C3, and instead choose a shallower C-state
> if there was "recent bus master activity".
>
> We have found a number of systems in the field that erroneously
> set BM_STS and prevent entry into deep C-states.
> Re-define BIOS presented C3-type states as C2-type states
> on modern processors to avoid this issue.
>
> If a device in the system really does want to prevent use
> of a deep C-state, its Linux driver should register its
> constraints via pm_qos_add_request().
>
> https://bugzilla.kernel.org/show_bug.cgi?id=15886
>
Agree with the intent. But, I think its cleaner to keep all arch model
checks in arch/x86/kernel/acpi/cstate.c.
Thanks,
Venki
> Signed-off-by: Len Brown <len.brown@intel.com>
> ---
> drivers/acpi/processor_idle.c | 38 ++++++++++++++++++++++++++++++++++++++
> 1 files changed, 38 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/acpi/processor_idle.c b/drivers/acpi/processor_idle.c
> index b1b3856..14d1a0c 100644
> --- a/drivers/acpi/processor_idle.c
> +++ b/drivers/acpi/processor_idle.c
> @@ -607,6 +607,38 @@ static void acpi_processor_power_verify_c3(struct acpi_processor *pr,
> return;
> }
>
> +/*
> + * Modern Intel processors support only ACPI C2-type C-states.
> + * But the BIOS tends to report its deepest C-state as C3-type
> + * to satisfy various old operating systems. We can skip
> + * C3 OS overhead by treating the deep-states as C2-type.
> + * Also, we can avoid checking BM_STS, which on some systems
> + * erroneously prevents entry into C3-type states.
> + */
> +static int acpi_c3type_is_really_c2type(void) {
> +
> + if (boot_cpu_data.x86_vendor != X86_VENDOR_INTEL)
> + return 0;
> +
> + if (boot_cpu_data.x86 != 6)
> + return 0;
> +
> + switch(boot_cpu_data.x86_model) {
> + case 0x1A: /* Core i7, Xeon 5500 series */
> + case 0x1E: /* Core i7 and i5 Processor */
> + case 0x1F: /* Core i7 and i5 Processor */
> + case 0x2E: /* NHM-EX Xeon */
> + case 0x2F: /* WSM-EX Xeon */
> + case 0x25: /* WSM */
> + case 0x2C: /* WSM */
> + case 0x2A: /* SNB */
> + case 0x2D: /* SNB Xeon */
> + return 1;
> + default:
> + return 0;
> + }
> +}
> +
> static int acpi_processor_power_verify(struct acpi_processor *pr)
> {
> unsigned int i;
> @@ -617,6 +649,12 @@ static int acpi_processor_power_verify(struct acpi_processor *pr)
> for (i = 1; i < ACPI_PROCESSOR_MAX_POWER && i <= max_cstate; i++) {
> struct acpi_processor_cx *cx = &pr->power.states[i];
>
> + if ((cx->type == ACPI_STATE_C3)
> + && acpi_c3type_is_really_c2type()) {
> + ACPI_DEBUG_PRINT((ACPI_DB_INFO, "Redefining C3-type to C2\n"));
> + cx->type = ACPI_STATE_C2;
> + }
> +
> switch (cx->type) {
> case ACPI_STATE_C1:
> cx->valid = 1;
> --
> 1.7.2.rc3.43.g24e7a
>
>
>
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: acpi_idle: Very idle Core i7 machine never enters C3
2010-04-27 12:47 ` Jeff Garrett
2010-04-30 14:57 ` Philip Langdale
2010-04-30 16:25 ` Len Brown
@ 2010-07-22 5:34 ` Len Brown
2 siblings, 0 replies; 54+ messages in thread
From: Len Brown @ 2010-07-22 5:34 UTC (permalink / raw)
To: Jeff Garrett; +Cc: Philip Langdale, Andi Kleen, linux-kernel, linux-acpi
Jeff,
Please attach the output from acpidump for your dell to this bug report:
https://bugzilla.kernel.org/show_bug.cgi?id=15886
I think we know how to cleanly solve the issue to make Philip's Gigabye
happy, and I'd like to know if your Dell is the same situation
or a different one.
Unfortunately, Matthew's HP fails for a different reason than Philip's
Gigabyete. (The BIOS asks for it - so we'll have to poke at the chipset
to find out the reason it is setting BM_STS)
thanks,
Len Brown, Intel Open Source Technology Center
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [PATCH] ACPI: make acpi_idle Nehalem-aware
2010-07-21 21:31 ` [PATCH] ACPI: make acpi_idle Nehalem-aware Len Brown
2010-07-22 0:53 ` Venkatesh Pallipadi
@ 2010-07-22 7:47 ` Andi Kleen
2010-07-22 15:57 ` Len Brown
2010-08-03 6:55 ` Pavel Machek
2 siblings, 1 reply; 54+ messages in thread
From: Andi Kleen @ 2010-07-22 7:47 UTC (permalink / raw)
To: Len Brown
Cc: Matthew Garrett, Yu, Luming, Philip Langdale, Jeff Garrett,
Andi Kleen, Linux Kernel Mailing List, linux-acpi, venki
> If a device in the system really does want to prevent use
> of a deep C-state, its Linux driver should register its
> constraints via pm_qos_add_request().
I reviewed the patch and it looks good to me.
I would suggest to have a command line option for this too,
in case someone wants to run an older kernel on a new system not
known by your patch yet.
-Andi
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [PATCH] ACPI: make acpi_idle Nehalem-aware
2010-07-22 7:47 ` Andi Kleen
@ 2010-07-22 15:57 ` Len Brown
2010-07-22 21:21 ` [PATCH] ACPI: skip checking BM_STS if the BIOS doesn't ask for it Len Brown
2010-07-22 21:25 ` [PATCH] ACPI: make acpi_idle Nehalem-aware Iain
0 siblings, 2 replies; 54+ messages in thread
From: Len Brown @ 2010-07-22 15:57 UTC (permalink / raw)
To: Andi Kleen
Cc: Matthew Garrett, Yu, Luming, Philip Langdale, Jeff Garrett,
Linux Kernel Mailing List, linux-acpi, venki
This patch is kaput.
As detailed in the bug report
https://bugzilla.kernel.org/show_bug.cgi?id=15886
we should be able to fix some of these boxes
by paying attention to an ACPI flag we didn't
realize existed until yesterday.
I'll follow-up with a new patch today.
However, we'll still have issues with systems
like the HP DL360 G6 which explicity set the
flag to ask for BM_STS checking and configure
the chipset such that BM_STS is active.
That may require a BIOS fix, or we may
have to run intel_idle on that box --
since intel_idle ignores BM_STS always
and instead relies on drivers to use pm_qos
to register device latency constraints.
thanks,
Len Brown, Intel Open Source Technology Center
^ permalink raw reply [flat|nested] 54+ messages in thread
* [PATCH] ACPI: skip checking BM_STS if the BIOS doesn't ask for it
2010-07-22 15:57 ` Len Brown
@ 2010-07-22 21:21 ` Len Brown
2010-07-22 21:40 ` [PATCH] ACPI: create "processor.bm_check_disable" boot param Len Brown
2010-07-22 21:25 ` [PATCH] ACPI: make acpi_idle Nehalem-aware Iain
1 sibling, 1 reply; 54+ messages in thread
From: Len Brown @ 2010-07-22 21:21 UTC (permalink / raw)
To: Andi Kleen
Cc: Matthew Garrett, Yu, Luming, Philip Langdale, Jeff Garrett,
Linux Kernel Mailing List, linux-acpi, venki
From: Len Brown <len.brown@intel.com>
It turns out that there is a bit in the _CST for Intel FFH C3
that tells the OS if we should be checking BM_STS or not.
Linux has been unconditionally checking BM_STS.
If the chip-set is configured to enable BM_STS,
it can retard or completely prevent entry into
deep C-states -- as illustrated by turbostat:
http://userweb.kernel.org/~lenb/acpi/utils/pmtools/turbostat/
ref: Intel Processor Vendor-Specific ACPI Interface Specification
table 4 "_CST FFH GAS Field Encoding"
Bit 1: Set to 1 if OSPM should use Bus Master avoidance for this C-state
https://bugzilla.kernel.org/show_bug.cgi?id=15886
Signed-off-by: Len Brown <len.brown@intel.com>
---
arch/x86/kernel/acpi/cstate.c | 9 +++++++++
drivers/acpi/processor_idle.c | 2 +-
include/acpi/processor.h | 3 ++-
3 files changed, 12 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kernel/acpi/cstate.c b/arch/x86/kernel/acpi/cstate.c
index 2e837f5..fb7a5f0 100644
--- a/arch/x86/kernel/acpi/cstate.c
+++ b/arch/x86/kernel/acpi/cstate.c
@@ -145,6 +145,15 @@ int acpi_processor_ffh_cstate_probe(unsigned int cpu,
percpu_entry->states[cx->index].eax = cx->address;
percpu_entry->states[cx->index].ecx = MWAIT_ECX_INTERRUPT_BREAK;
}
+
+ /*
+ * For _CST FFH on Intel, if GAS.access_size bit 1 is cleared,
+ * then we should skip checking BM_STS for this C-state.
+ * ref: "Intel Processor Vendor-Specific ACPI Interface Specification"
+ */
+ if ((c->x86_vendor == X86_VENDOR_INTEL) && !(reg->access_size & 0x2))
+ cx->bm_sts_skip = 1;
+
return retval;
}
EXPORT_SYMBOL_GPL(acpi_processor_ffh_cstate_probe);
diff --git a/drivers/acpi/processor_idle.c b/drivers/acpi/processor_idle.c
index b1b3856..b351342 100644
--- a/drivers/acpi/processor_idle.c
+++ b/drivers/acpi/processor_idle.c
@@ -947,7 +947,7 @@ static int acpi_idle_enter_bm(struct cpuidle_device *dev,
if (acpi_idle_suspend)
return(acpi_idle_enter_c1(dev, state));
- if (acpi_idle_bm_check()) {
+ if (!cx->bm_sts_skip && acpi_idle_bm_check()) {
if (dev->safe_state) {
dev->last_state = dev->safe_state;
return dev->safe_state->enter(dev, dev->safe_state);
diff --git a/include/acpi/processor.h b/include/acpi/processor.h
index da565a4..a68ca8a 100644
--- a/include/acpi/processor.h
+++ b/include/acpi/processor.h
@@ -48,7 +48,7 @@ struct acpi_power_register {
u8 space_id;
u8 bit_width;
u8 bit_offset;
- u8 reserved;
+ u8 access_size;
u64 address;
} __attribute__ ((packed));
@@ -63,6 +63,7 @@ struct acpi_processor_cx {
u32 power;
u32 usage;
u64 time;
+ u8 bm_sts_skip;
char desc[ACPI_CX_DESC_LEN];
};
--
1.7.2
^ permalink raw reply related [flat|nested] 54+ messages in thread
* Re: [PATCH] ACPI: make acpi_idle Nehalem-aware
2010-07-22 15:57 ` Len Brown
2010-07-22 21:21 ` [PATCH] ACPI: skip checking BM_STS if the BIOS doesn't ask for it Len Brown
@ 2010-07-22 21:25 ` Iain
2010-07-22 21:53 ` Iain
2010-07-22 22:01 ` Len Brown
1 sibling, 2 replies; 54+ messages in thread
From: Iain @ 2010-07-22 21:25 UTC (permalink / raw)
To: Len Brown
Cc: Andi Kleen, Matthew Garrett, Yu, Luming, Philip Langdale,
Jeff Garrett, Linux Kernel Mailing List, linux-acpi, venki
Len Brown wrote:
> However, we'll still have issues with systems
> like the HP DL360 G6 which explicity set the
> flag to ask for BM_STS checking and configure
> the chipset such that BM_STS is active.
> That may require a BIOS fix, or we may
> have to run intel_idle on that box --
> since intel_idle ignores BM_STS always
> and instead relies on drivers to use pm_qos
> to register device latency constraints.
I'm curious as to why you see a problem with the DL380G6 as the one I have here happily sits in C6 when idle.
your turbostat util shows:
CPU GHz TSC %c0 %c1 %c3 %c6 %pc3 %pc6
avg 1.64 2.27 0.16 0.12 0.00 99.71 0.00 90.15
and powertop has results like:
Cn Avg residency P-states (frequencies)
C0 (cpu running) ( 0,1%) Turbo Mode 0,0%
polling 0,0ms ( 0,0%) 2,27 Ghz 0,0%
C1 mwait 0,1ms ( 0,0%) 2,13 Ghz 0,0%
C2 mwait 1,0ms ( 0,0%) 2,00 Ghz 0,0%
C3 mwait 90,4ms (99,9%) 1,60 Ghz 100,0%
this is with v2.6.35-rc5-176-gcd5b8f8 and using acpi_idle. I've deliberately disabled intel_idle to test, however using intel_idle
gives almost identical results.
Looking at the bug 15886, the Access Size 0x03 entries you mentioned are all 0x01 on this system. I've also uploaded the acpidump
from this DL380G6 to that bug so that you can check I've not just looked in the wrong place.
Did the first acpidump come from a system with the 'HP Power Regulator' setting in the bios set to OS Control mode ? My system is
set this way and it seems to work as expected.
The other settings for this option appear to be designed to override OS power management controls, for example the description of
the 'Static High Performance' option suggests it'll somehow force the CPU to operate in the highest performance mode all of the
time: "HP Static High Performance Mode: Processors will run in their maximum power/performance state at all times regardless of the
OS power management policy".
If this does turn out to be as simple as a bios setting, should we really be trying to workaround what may be a legitimate decision
by the servers admin ?
Iain
^ permalink raw reply [flat|nested] 54+ messages in thread
* [PATCH] ACPI: create "processor.bm_check_disable" boot param
2010-07-22 21:21 ` [PATCH] ACPI: skip checking BM_STS if the BIOS doesn't ask for it Len Brown
@ 2010-07-22 21:40 ` Len Brown
2010-07-26 7:24 ` Andi Kleen
0 siblings, 1 reply; 54+ messages in thread
From: Len Brown @ 2010-07-22 21:40 UTC (permalink / raw)
To: Andi Kleen
Cc: Matthew Garrett, Yu, Luming, Philip Langdale, Jeff Garrett,
Linux Kernel Mailing List, linux-acpi, venki
From: Len Brown <len.brown@intel.com>
processor.bm_check_disable=1" prevents Linux from checking BM_STS
before entering C3-type cpu power states.
This may be useful for a system running acpi_idle
where the BIOS exports FADT C-states, _CST IO C-states,
or _CST FFH C-states with the BM_STS bit set;
while configuring the chipset to set BM_STS
more frequently than perhaps is optimal.
Note that such systems may have been developed
using a tickful OS that would quickly clear BM_STS,
rather than a tickless OS that may go for some time
between checking and clearing BM_STS.
Note also that an alternative for newer systems
is to use the intel_idle driver, which always
ignores BM_STS, relying Linux device drivers
to register constraints explicitly via PM_QOS.
https://bugzilla.kernel.org/show_bug.cgi?id=15886
Signed-off-by: Len Brown <len.brown@intel.com>
---
drivers/acpi/processor_idle.c | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/drivers/acpi/processor_idle.c b/drivers/acpi/processor_idle.c
index b351342..1d41048 100644
--- a/drivers/acpi/processor_idle.c
+++ b/drivers/acpi/processor_idle.c
@@ -76,6 +76,8 @@ static unsigned int max_cstate __read_mostly = ACPI_PROCESSOR_MAX_POWER;
module_param(max_cstate, uint, 0000);
static unsigned int nocst __read_mostly;
module_param(nocst, uint, 0000);
+static int bm_check_disable __read_mostly;
+module_param(bm_check_disable, uint, 0000);
static unsigned int latency_factor __read_mostly = 2;
module_param(latency_factor, uint, 0644);
@@ -763,6 +765,9 @@ static int acpi_idle_bm_check(void)
{
u32 bm_status = 0;
+ if (bm_check_disable)
+ return 0;
+
acpi_read_bit_register(ACPI_BITREG_BUS_MASTER_STATUS, &bm_status);
if (bm_status)
acpi_write_bit_register(ACPI_BITREG_BUS_MASTER_STATUS, 1);
--
1.7.2
^ permalink raw reply related [flat|nested] 54+ messages in thread
* Re: [PATCH] ACPI: make acpi_idle Nehalem-aware
2010-07-22 21:25 ` [PATCH] ACPI: make acpi_idle Nehalem-aware Iain
@ 2010-07-22 21:53 ` Iain
2010-07-22 22:01 ` Len Brown
1 sibling, 0 replies; 54+ messages in thread
From: Iain @ 2010-07-22 21:53 UTC (permalink / raw)
To: Iain
Cc: Len Brown, Andi Kleen, Matthew Garrett, Yu, Luming,
Philip Langdale, Jeff Garrett, Linux Kernel Mailing List,
linux-acpi, venki
Iain wrote:
> Len Brown wrote:
>> However, we'll still have issues with systems
>> like the HP DL360 G6 which explicity set the
>
> I'm curious as to why you see a problem with the DL380G6 as the one I have here happily sits in C6 when idle.
Please ignore me, apologies for the noise.
Just noticed the problem system was a DL360 and mine is a DL380. Long day spent working with both 360's and 380's - I don't seem to
be able to tell them apart anymore..
Iain
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [PATCH] ACPI: make acpi_idle Nehalem-aware
2010-07-22 21:25 ` [PATCH] ACPI: make acpi_idle Nehalem-aware Iain
2010-07-22 21:53 ` Iain
@ 2010-07-22 22:01 ` Len Brown
2010-07-23 12:40 ` Iain
1 sibling, 1 reply; 54+ messages in thread
From: Len Brown @ 2010-07-22 22:01 UTC (permalink / raw)
To: Iain
Cc: Andi Kleen, Matthew Garrett, Yu, Luming, Philip Langdale,
Jeff Garrett, Linux Kernel Mailing List, linux-acpi, venki
> I'm curious as to why you see a problem with the DL380G6 as the one I have
> here happily sits in C6 when idle.
yay!
> your turbostat util shows:
>
> CPU GHz TSC %c0 %c1 %c3 %c6 %pc3 %pc6
> avg 1.64 2.27 0.16 0.12 0.00 99.71 0.00 90.15
> Looking at the bug 15886, the Access Size 0x03 entries you mentioned are all
> 0x01 on this system. I've also uploaded the acpidump from this DL380G6 to that
> bug so that you can check I've not just looked in the wrong place.
You read it correctly, your BIOS does not request BM_STS, mjg59's does.
> Did the first acpidump come from a system with the 'HP Power Regulator'
> setting in the bios set to OS Control mode ? My system is set this way and it
> seems to work as expected.
I expect that is to enable PCC, which would change P-states,
but unlikely would have an effect on C-states.
If you can try it both ways that might be good to know.
(include powertop display once again)
Of course, the default setting is what 99% of customers use...
> The other settings for this option appear to be designed to override OS power
> management controls, for example the description of the 'Static High
> Performance' option suggests it'll somehow force the CPU to operate in the
> highest performance mode all of the time: "HP Static High Performance Mode:
> Processors will run in their maximum power/performance state at all times
> regardless of the OS power management policy".
This is BIOS writer "value add".
Unclear how it migh be an improvement over what Linux has been shipping
for years.
> If this does turn out to be as simple as a bios setting, should we really be
> trying to workaround what may be a legitimate decision by the servers admin ?
Ideally we will do exactly as the BIOS requests.
However, somtimes what they request makes lots of sense
on some version of Windows, and may make less sense
when running Linux.
Please upload the output from dmidecode to the bug report.
I am hopeful that you have a current BIOS and that
Matthew may have an pre-production BIOS.
thanks,
Len Brown, Intel Open Source Technology Center
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [PATCH] ACPI: make acpi_idle Nehalem-aware
2010-07-22 22:01 ` Len Brown
@ 2010-07-23 12:40 ` Iain
0 siblings, 0 replies; 54+ messages in thread
From: Iain @ 2010-07-23 12:40 UTC (permalink / raw)
To: Len Brown
Cc: Andi Kleen, Matthew Garrett, Yu, Luming, Philip Langdale,
Jeff Garrett, Linux Kernel Mailing List, linux-acpi, venki
Len Brown wrote:
> You read it correctly, your BIOS does not request BM_STS, mjg59's does.
Right, and on a DL360 G6 with the 07-24-2009 bios version I saw the same.
> I expect that is to enable PCC, which would change P-states,
> but unlikely would have an effect on C-states.
I found another option in the bios to limit or disable the C-states today, so plenty of opportunity to configure the system into an
odd state.
> If you can try it both ways that might be good to know.
> (include powertop display once again)
> Of course, the default setting is what 99% of customers use...
I'll upload an archive to the bugzilla entry with the details. What seems to happen is that when you set the default Balanced Power
and Performance mode the CST code vanishes completely and the processor manages to get to c6 some of the time. Enable OS Control
mode and the bad CST code appears.
> This is BIOS writer "value add".
> Unclear how it migh be an improvement over what Linux has been shipping
> for years.
Well yes, having Linux and the bios fighting for control probably isn't going to help.
> Please upload the output from dmidecode to the bug report.
> I am hopeful that you have a current BIOS and that
> Matthew may have an pre-production BIOS.
I've uploaded an archive with dmidecode, turbostat and powertop dumps. There are dumps with the bios set to the default, and to OS
Control mode.
The original bios on my DL360G6 was 07-24-2009 and has the same issue as Matthew. I upgraded the machine to the latest 2010.05.15
and repeated the tests.
Good news is that the new bios has fixed the CST code so that the Access length values are all 0x01 when they're present and the
dumps show the processor getting into c6 much more.
So you were correct, bios fix was needed.
Iain
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [PATCH] ACPI: create "processor.bm_check_disable" boot param
2010-07-22 21:40 ` [PATCH] ACPI: create "processor.bm_check_disable" boot param Len Brown
@ 2010-07-26 7:24 ` Andi Kleen
0 siblings, 0 replies; 54+ messages in thread
From: Andi Kleen @ 2010-07-26 7:24 UTC (permalink / raw)
To: Len Brown
Cc: Matthew Garrett, Yu, Luming, Philip Langdale, Jeff Garrett,
Linux Kernel Mailing List, linux-acpi, venki
Len Brown <lenb@kernel.org> writes:
>
> Note also that an alternative for newer systems
> is to use the intel_idle driver, which always
> ignores BM_STS, relying Linux device drivers
> to register constraints explicitly via PM_QOS.
>
> https://bugzilla.kernel.org/show_bug.cgi?id=15886
Thanks. I don't fully understand why the check for this option
is in a different place than the register check in the earlier patch?
This needs to be also documented in Documentation/kernel-parameters.txt
Other than that it looks good.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [PATCH] ACPI: create "processor.bm_check_disable" boot param
@ 2010-07-26 7:24 ` Andi Kleen
0 siblings, 0 replies; 54+ messages in thread
From: Andi Kleen @ 2010-07-26 7:24 UTC (permalink / raw)
To: Len Brown
Cc: Matthew Garrett, Yu, Luming, Philip Langdale, Jeff Garrett,
Linux Kernel Mailing List, linux-acpi, venki
Len Brown <lenb@kernel.org> writes:
>
> Note also that an alternative for newer systems
> is to use the intel_idle driver, which always
> ignores BM_STS, relying Linux device drivers
> to register constraints explicitly via PM_QOS.
>
> https://bugzilla.kernel.org/show_bug.cgi?id=15886
Thanks. I don't fully understand why the check for this option
is in a different place than the register check in the earlier patch?
This needs to be also documented in Documentation/kernel-parameters.txt
Other than that it looks good.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [PATCH] ACPI: create "processor.bm_check_disable" boot param
2010-07-26 7:24 ` Andi Kleen
(?)
@ 2010-07-27 0:19 ` Len Brown
2010-07-27 11:28 ` Andi Kleen
-1 siblings, 1 reply; 54+ messages in thread
From: Len Brown @ 2010-07-27 0:19 UTC (permalink / raw)
To: Andi Kleen
Cc: Matthew Garrett, Yu, Luming, Philip Langdale, Jeff Garrett,
Linux Kernel Mailing List, linux-acpi, venki
> > Note also that an alternative for newer systems
> > is to use the intel_idle driver, which always
> > ignores BM_STS, relying Linux device drivers
> > to register constraints explicitly via PM_QOS.
> >
> > https://bugzilla.kernel.org/show_bug.cgi?id=15886
>
> Thanks. I don't fully understand why the check for this option
> is in a different place than the register check in the earlier patch?
Technically, it could have been.
There are a comple of constraints in the layout of this code.
The _CST flag is x86 (actually Intel) specific -- so the detection
went into arch/x86/kernel/acpi/cstate.c
However, the operation of the that flag is per C-state,
not necessarily per system -- so we remember the flag
in in a cx->bm_sts_skip flag and check it in the
'acpi generic' drivers/acpi/processor_idle.c
But we can't test a per cx flag inside acpi_idle_bm_check()
because it doesn't have access to the cx, so i put that
test at the site of its only caller.
In this 2nd patch...
we added a 'generic' ACPI bootparam that applies
to all C-states. So it overrides any per-cstate flag
and it is static to the processor_idle.c file,
so it seemed cleanest (to me)
to push it down inside acpi_idle_bm_check()
rather than in its only caller.
> This needs to be also documented in Documentation/kernel-parameters.txt
I thought about that and decided against it.
While we do document some driver specific modparams
in kernel-parameters.txt, I do not expect this one to
be used that often -- mostly for diagnosis of BIOS bugs.
I know of two machines that need it,
and both of those machines have a BIOS update
or a BIOS update in progress that make it unnecessary.
thanks for caring.
Len Brown, Intel Open Source Technology Center.
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [PATCH] ACPI: create "processor.bm_check_disable" boot param
2010-07-27 0:19 ` Len Brown
@ 2010-07-27 11:28 ` Andi Kleen
2010-07-28 18:58 ` Len Brown
0 siblings, 1 reply; 54+ messages in thread
From: Andi Kleen @ 2010-07-27 11:28 UTC (permalink / raw)
To: Len Brown
Cc: Andi Kleen, Matthew Garrett, Yu, Luming, Philip Langdale,
Jeff Garrett, Linux Kernel Mailing List, linux-acpi, venki
> > This needs to be also documented in Documentation/kernel-parameters.txt
>
> I thought about that and decided against it.
> While we do document some driver specific modparams
> in kernel-parameters.txt, I do not expect this one to
> be used that often -- mostly for diagnosis of BIOS bugs.
> I know of two machines that need it,
> and both of those machines have a BIOS update
> or a BIOS update in progress that make it unnecessary.
I think even obscure parameters should be documented.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [PATCH] ACPI: create "processor.bm_check_disable" boot param
2010-07-27 11:28 ` Andi Kleen
@ 2010-07-28 18:58 ` Len Brown
0 siblings, 0 replies; 54+ messages in thread
From: Len Brown @ 2010-07-28 18:58 UTC (permalink / raw)
To: Andi Kleen
Cc: Matthew Garrett, Yu, Luming, Philip Langdale, Jeff Garrett,
Linux Kernel Mailing List, linux-acpi, venki
On Tue, 27 Jul 2010, Andi Kleen wrote:
> > > This needs to be also documented in Documentation/kernel-parameters.txt
> >
> > I thought about that and decided against it.
> > While we do document some driver specific modparams
> > in kernel-parameters.txt, I do not expect this one to
> > be used that often -- mostly for diagnosis of BIOS bugs.
> > I know of two machines that need it,
> > and both of those machines have a BIOS update
> > or a BIOS update in progress that make it unnecessary.
>
> I think even obscure parameters should be documented.
Where?
kernel-parameters.txt seems to be mostly about core kernel parameters.
While there are some key driver parameters in there, they
appear to be the exception.
-Len
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [PATCH] ACPI: make acpi_idle Nehalem-aware
2010-07-21 21:31 ` [PATCH] ACPI: make acpi_idle Nehalem-aware Len Brown
2010-07-22 0:53 ` Venkatesh Pallipadi
2010-07-22 7:47 ` Andi Kleen
@ 2010-08-03 6:55 ` Pavel Machek
2010-08-03 7:05 ` Andi Kleen
2 siblings, 1 reply; 54+ messages in thread
From: Pavel Machek @ 2010-08-03 6:55 UTC (permalink / raw)
To: Len Brown
Cc: Matthew Garrett, Yu, Luming, Philip Langdale, Jeff Garrett,
Andi Kleen, Linux Kernel Mailing List, linux-acpi, venki
On Wed 2010-07-21 17:31:27, Len Brown wrote:
> From: Len Brown <len.brown@intel.com>
>
> The BIOS exports deep C-states on modern Intel processors
> as "C3-type" to satisfy various legacy Operating Systems.
Can you elaborate on this? I though the only difference between
C2-type and C3-type is busmastering...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [PATCH] ACPI: make acpi_idle Nehalem-aware
2010-08-03 6:55 ` Pavel Machek
@ 2010-08-03 7:05 ` Andi Kleen
0 siblings, 0 replies; 54+ messages in thread
From: Andi Kleen @ 2010-08-03 7:05 UTC (permalink / raw)
To: Pavel Machek
Cc: Len Brown, Matthew Garrett, Yu, Luming, Philip Langdale,
Jeff Garrett, Andi Kleen, Linux Kernel Mailing List, linux-acpi,
venki
On Tue, Aug 03, 2010 at 08:55:14AM +0200, Pavel Machek wrote:
> On Wed 2010-07-21 17:31:27, Len Brown wrote:
> > From: Len Brown <len.brown@intel.com>
> >
> > The BIOS exports deep C-states on modern Intel processors
> > as "C3-type" to satisfy various legacy Operating Systems.
>
> Can you elaborate on this? I though the only difference between
> C2-type and C3-type is busmastering...
The main difference is latency.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
^ permalink raw reply [flat|nested] 54+ messages in thread
end of thread, other threads:[~2010-08-03 7:05 UTC | newest]
Thread overview: 54+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-01-26 8:47 acpi_idle: Very idle Core i7 machine never enters C3 Jeff Garrett
2010-01-26 12:41 ` peng huang
2010-01-26 12:41 ` peng huang
2010-01-26 14:59 ` Jeff Garrett
2010-01-26 14:59 ` Jeff Garrett
2010-01-27 13:27 ` peng huang
2010-01-27 13:27 ` peng huang
2010-02-05 16:22 ` Jeff Garrett
2010-02-05 16:22 ` Jeff Garrett
2010-01-26 21:45 ` Andi Kleen
2010-01-26 21:45 ` Andi Kleen
2010-02-05 16:09 ` Jeff Garrett
2010-02-05 17:45 ` Len Brown
2010-02-05 20:53 ` Jeff Garrett
2010-04-27 2:40 ` Philip Langdale
2010-04-27 7:26 ` Len Brown
2010-04-27 15:41 ` Philip Langdale
2010-04-27 12:47 ` Jeff Garrett
2010-04-30 14:57 ` Philip Langdale
2010-04-30 14:57 ` Philip Langdale
2010-04-30 16:25 ` Len Brown
2010-04-30 17:44 ` Matthew Garrett
2010-04-30 18:35 ` Philip Langdale
2010-04-30 18:35 ` Philip Langdale
2010-05-25 5:43 ` Len Brown
2010-05-25 5:59 ` Yu, Luming
2010-05-25 12:39 ` Matthew Garrett
2010-05-25 12:43 ` Matthew Garrett
2010-05-25 12:43 ` Matthew Garrett
2010-05-25 15:33 ` Len Brown
2010-05-25 18:55 ` Matthew Garrett
2010-07-21 21:31 ` [PATCH] ACPI: make acpi_idle Nehalem-aware Len Brown
2010-07-22 0:53 ` Venkatesh Pallipadi
2010-07-22 0:53 ` Venkatesh Pallipadi
2010-07-22 7:47 ` Andi Kleen
2010-07-22 15:57 ` Len Brown
2010-07-22 21:21 ` [PATCH] ACPI: skip checking BM_STS if the BIOS doesn't ask for it Len Brown
2010-07-22 21:40 ` [PATCH] ACPI: create "processor.bm_check_disable" boot param Len Brown
2010-07-26 7:24 ` Andi Kleen
2010-07-26 7:24 ` Andi Kleen
2010-07-27 0:19 ` Len Brown
2010-07-27 11:28 ` Andi Kleen
2010-07-28 18:58 ` Len Brown
2010-07-22 21:25 ` [PATCH] ACPI: make acpi_idle Nehalem-aware Iain
2010-07-22 21:53 ` Iain
2010-07-22 22:01 ` Len Brown
2010-07-23 12:40 ` Iain
2010-08-03 6:55 ` Pavel Machek
2010-08-03 7:05 ` Andi Kleen
2010-05-25 12:37 ` acpi_idle: Very idle Core i7 machine never enters C3 Matthew Garrett
2010-05-25 15:40 ` Len Brown
2010-07-22 5:34 ` Len Brown
2010-02-01 14:10 ` Pavel Machek
2010-02-05 16:30 ` Jeff Garrett
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.