kmemleak, cpu usage jump out of nowhere

public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed

* kmemleak, cpu usage jump out of nowhere
@ 2010-07-14  6:12 Zeno Davatz
  2010-07-14  8:05 ` Pekka Enberg
  2010-07-14  9:57 ` Catalin Marinas
  0 siblings, 2 replies; 44+ messages in thread
From: Zeno Davatz @ 2010-07-14  6:12 UTC (permalink / raw)
  To: linux-kernel

[-- Attachment #1: Type: text/plain, Size: 988 bytes --]

Hi

I got a new Intel core-8 i7 processor.

I am on kernel uname -a

Linux zenogentoo 2.6.35-rc5 #97 SMP Tue Jul 13 16:13:25 CEST 2010 i686
Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz GenuineIntel GNU/Linux

Sometimes in the middle of nowhere all of a sudden all of my 8-cores
are at 100% CPU usage and my machine really lags and hangs and is not
useable anymore. Some random process just grabs a bunch CPUs according
to htop.

dmesg tell me that

kmemleak: 38 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
kmemleak: 2 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
kmemleak: 1 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
kmemleak: 2 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
kmemleak: 2 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
kmemleak: 1 new suspected memory leaks (see /sys/kernel/debug/kmemleak)

I am attaching you the file from /sys/kernel/debug/kmemleak

Let me know if you need anything else.

Best
Zeno

[-- Attachment #2: kmemleak --]
[-- Type: application/octet-stream, Size: 33456 bytes --]

unreferenced object 0xf6d80740 (size 64):
  comm "swapper", pid 1, jiffies 4294892590 (age 57258.752s)
  hex dump (first 32 bytes):
    00 00 ee c7 00 00 00 00 ff b7 ee c7 00 00 00 00  ................
    7c 09 52 c1 00 00 00 80 00 f2 5e c1 20 ac 6f c1  |.R.......^. .o.
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10ad53f>] kmem_cache_alloc+0xa3/0xd4
    [<c163b782>] __reserve_region_with_split+0x29/0x149
    [<c163b86a>] __reserve_region_with_split+0x111/0x149
    [<c163b89a>] __reserve_region_with_split+0x141/0x149
    [<c163b89a>] __reserve_region_with_split+0x141/0x149
    [<c163b89a>] __reserve_region_with_split+0x141/0x149
    [<c163b8de>] reserve_region_with_split+0x3c/0x4f
    [<c162e307>] e820_reserve_resources_late+0xea/0x108
    [<c16504e6>] pcibios_resource_survey+0x23/0x2a
    [<c1652022>] pcibios_init+0x61/0x73
    [<c165172b>] pci_subsys_init+0x43/0x48
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
    [<c10238b6>] kernel_thread_helper+0x6/0x10
    [<ffffffff>] 0xffffffff
unreferenced object 0xf6d232a0 (size 32):
  comm "swapper", pid 1, jiffies 4294892601 (age 57258.708s)
  hex dump (first 32 bytes):
    70 6e 70 20 30 30 3a 30 31 00 d2 f6 fa 00 0b c1  pnp 00:01.......
    00 00 00 00 04 aa dc f6 2c 00 00 00 01 00 00 00  ........,.......
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10ad53f>] kmem_cache_alloc+0xa3/0xd4
    [<c123040b>] reserve_range+0x3b/0x13f
    [<c1230597>] system_pnp_probe+0x88/0xb0
    [<c122b0f7>] pnp_device_probe+0x67/0xaf
    [<c12d5246>] driver_probe_device+0x5b/0x148
    [<c12d539a>] __driver_attach+0x67/0x69
    [<c12d4c33>] bus_for_each_dev+0x46/0x64
    [<c12d512c>] driver_attach+0x19/0x1b
    [<c12d46f5>] bus_add_driver+0x17a/0x225
    [<c12d55b8>] driver_register+0x65/0x110
    [<c122af44>] pnp_register_driver+0x17/0x19
    [<c1647a91>] pnp_system_init+0xd/0xf
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
    [<c10238b6>] kernel_thread_helper+0x6/0x10
unreferenced object 0xf6d7a200 (size 64):
  comm "swapper", pid 1, jiffies 4294892601 (age 57258.708s)
  hex dump (first 32 bytes):
    00 a0 c8 fe 00 00 00 00 ff af c8 fe 00 00 00 00  ................
    a0 32 d2 f6 00 00 00 00 34 57 dc f6 c0 a1 d7 f6  .2......4W......
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10ad53f>] kmem_cache_alloc+0xa3/0xd4
    [<c10564a7>] __request_region+0x47/0x201
    [<c12304ef>] reserve_range+0x11f/0x13f
    [<c1230597>] system_pnp_probe+0x88/0xb0
    [<c122b0f7>] pnp_device_probe+0x67/0xaf
    [<c12d5246>] driver_probe_device+0x5b/0x148
    [<c12d539a>] __driver_attach+0x67/0x69
    [<c12d4c33>] bus_for_each_dev+0x46/0x64
    [<c12d512c>] driver_attach+0x19/0x1b
    [<c12d46f5>] bus_add_driver+0x17a/0x225
    [<c12d55b8>] driver_register+0x65/0x110
    [<c122af44>] pnp_register_driver+0x17/0x19
    [<c1647a91>] pnp_system_init+0xd/0xf
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
unreferenced object 0xf6d23280 (size 32):
  comm "swapper", pid 1, jiffies 4294892601 (age 57258.708s)
  hex dump (first 32 bytes):
    70 6e 70 20 30 30 3a 30 31 00 20 00 8c 32 d2 f6  pnp 00:01. ..2..
    8c 32 d2 f6 90 00 d2 f6 94 32 d2 f6 48 87 74 f7  .2.......2..H.t.
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10ad53f>] kmem_cache_alloc+0xa3/0xd4
    [<c123040b>] reserve_range+0x3b/0x13f
    [<c1230597>] system_pnp_probe+0x88/0xb0
    [<c122b0f7>] pnp_device_probe+0x67/0xaf
    [<c12d5246>] driver_probe_device+0x5b/0x148
    [<c12d539a>] __driver_attach+0x67/0x69
    [<c12d4c33>] bus_for_each_dev+0x46/0x64
    [<c12d512c>] driver_attach+0x19/0x1b
    [<c12d46f5>] bus_add_driver+0x17a/0x225
    [<c12d55b8>] driver_register+0x65/0x110
    [<c122af44>] pnp_register_driver+0x17/0x19
    [<c1647a91>] pnp_system_init+0xd/0xf
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
    [<c10238b6>] kernel_thread_helper+0x6/0x10
unreferenced object 0xf6d7a1c0 (size 64):
  comm "swapper", pid 1, jiffies 4294892601 (age 57258.708s)
  hex dump (first 32 bytes):
    00 00 d1 fe 00 00 00 00 ff 0f d1 fe 00 00 00 00  ................
    80 32 d2 f6 00 00 00 00 34 57 dc f6 c0 0f cc f6  .2......4W......
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10ad53f>] kmem_cache_alloc+0xa3/0xd4
    [<c10564a7>] __request_region+0x47/0x201
    [<c12304ef>] reserve_range+0x11f/0x13f
    [<c1230597>] system_pnp_probe+0x88/0xb0
    [<c122b0f7>] pnp_device_probe+0x67/0xaf
    [<c12d5246>] driver_probe_device+0x5b/0x148
    [<c12d539a>] __driver_attach+0x67/0x69
    [<c12d4c33>] bus_for_each_dev+0x46/0x64
    [<c12d512c>] driver_attach+0x19/0x1b
    [<c12d46f5>] bus_add_driver+0x17a/0x225
    [<c12d55b8>] driver_register+0x65/0x110
    [<c122af44>] pnp_register_driver+0x17/0x19
    [<c1647a91>] pnp_system_init+0xd/0xf
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
unreferenced object 0xf6d231e0 (size 32):
  comm "swapper", pid 1, jiffies 4294892601 (age 57258.708s)
  hex dump (first 32 bytes):
    70 6e 70 20 30 30 3a 30 37 00 d2 f6 e8 31 d2 f6  pnp 00:07....1..
    a8 0c d2 f6 a4 a8 dc f6 cf a8 dc f6 a8 32 d2 f6  .............2..
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10ad53f>] kmem_cache_alloc+0xa3/0xd4
    [<c123040b>] reserve_range+0x3b/0x13f
    [<c1230597>] system_pnp_probe+0x88/0xb0
    [<c122b0f7>] pnp_device_probe+0x67/0xaf
    [<c12d5246>] driver_probe_device+0x5b/0x148
    [<c12d539a>] __driver_attach+0x67/0x69
    [<c12d4c33>] bus_for_each_dev+0x46/0x64
    [<c12d512c>] driver_attach+0x19/0x1b
    [<c12d46f5>] bus_add_driver+0x17a/0x225
    [<c12d55b8>] driver_register+0x65/0x110
    [<c122af44>] pnp_register_driver+0x17/0x19
    [<c1647a91>] pnp_system_init+0xd/0xf
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
    [<c10238b6>] kernel_thread_helper+0x6/0x10
unreferenced object 0xf6cc0fc0 (size 64):
  comm "swapper", pid 1, jiffies 4294892601 (age 57258.708s)
  hex dump (first 32 bytes):
    00 c0 d1 fe 00 00 00 00 ff ff d1 fe 00 00 00 00  ................
    e0 31 d2 f6 00 00 00 00 34 57 dc f6 80 0f cc f6  .1......4W......
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10ad53f>] kmem_cache_alloc+0xa3/0xd4
    [<c10564a7>] __request_region+0x47/0x201
    [<c12304ef>] reserve_range+0x11f/0x13f
    [<c1230597>] system_pnp_probe+0x88/0xb0
    [<c122b0f7>] pnp_device_probe+0x67/0xaf
    [<c12d5246>] driver_probe_device+0x5b/0x148
    [<c12d539a>] __driver_attach+0x67/0x69
    [<c12d4c33>] bus_for_each_dev+0x46/0x64
    [<c12d512c>] driver_attach+0x19/0x1b
    [<c12d46f5>] bus_add_driver+0x17a/0x225
    [<c12d55b8>] driver_register+0x65/0x110
    [<c122af44>] pnp_register_driver+0x17/0x19
    [<c1647a91>] pnp_system_init+0xd/0xf
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
unreferenced object 0xf6d23fe0 (size 32):
  comm "swapper", pid 1, jiffies 4294892601 (age 57258.708s)
  hex dump (first 32 bytes):
    70 6e 70 20 30 30 3a 30 37 00 00 00 00 00 00 00  pnp 00:07.......
    00 00 00 00 00 00 00 00 6c 6e 6c 6e d5 ee d5 ee  ........lnln....
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10ad53f>] kmem_cache_alloc+0xa3/0xd4
    [<c123040b>] reserve_range+0x3b/0x13f
    [<c1230597>] system_pnp_probe+0x88/0xb0
    [<c122b0f7>] pnp_device_probe+0x67/0xaf
    [<c12d5246>] driver_probe_device+0x5b/0x148
    [<c12d539a>] __driver_attach+0x67/0x69
    [<c12d4c33>] bus_for_each_dev+0x46/0x64
    [<c12d512c>] driver_attach+0x19/0x1b
    [<c12d46f5>] bus_add_driver+0x17a/0x225
    [<c12d55b8>] driver_register+0x65/0x110
    [<c122af44>] pnp_register_driver+0x17/0x19
    [<c1647a91>] pnp_system_init+0xd/0xf
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
    [<c10238b6>] kernel_thread_helper+0x6/0x10
unreferenced object 0xf6cc0f80 (size 64):
  comm "swapper", pid 1, jiffies 4294892601 (age 57258.708s)
  hex dump (first 32 bytes):
    00 00 d2 fe 00 00 00 00 ff ff d3 fe 00 00 00 00  ................
    e0 3f d2 f6 00 00 00 00 34 57 dc f6 40 0f cc f6  .?......4W..@...
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10ad53f>] kmem_cache_alloc+0xa3/0xd4
    [<c10564a7>] __request_region+0x47/0x201
    [<c12304ef>] reserve_range+0x11f/0x13f
    [<c1230597>] system_pnp_probe+0x88/0xb0
    [<c122b0f7>] pnp_device_probe+0x67/0xaf
    [<c12d5246>] driver_probe_device+0x5b/0x148
    [<c12d539a>] __driver_attach+0x67/0x69
    [<c12d4c33>] bus_for_each_dev+0x46/0x64
    [<c12d512c>] driver_attach+0x19/0x1b
    [<c12d46f5>] bus_add_driver+0x17a/0x225
    [<c12d55b8>] driver_register+0x65/0x110
    [<c122af44>] pnp_register_driver+0x17/0x19
    [<c1647a91>] pnp_system_init+0xd/0xf
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
unreferenced object 0xf6d23fc0 (size 32):
  comm "swapper", pid 1, jiffies 4294892601 (age 57258.708s)
  hex dump (first 32 bytes):
    70 6e 70 20 30 30 3a 30 37 00 21 c1 48 cb 21 c1  pnp 00:07.!.H.!.
    10 00 00 00 30 dc fe ff 01 00 00 00 73 77 61 70  ....0.......swap
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10ad53f>] kmem_cache_alloc+0xa3/0xd4
    [<c123040b>] reserve_range+0x3b/0x13f
    [<c1230597>] system_pnp_probe+0x88/0xb0
    [<c122b0f7>] pnp_device_probe+0x67/0xaf
    [<c12d5246>] driver_probe_device+0x5b/0x148
    [<c12d539a>] __driver_attach+0x67/0x69
    [<c12d4c33>] bus_for_each_dev+0x46/0x64
    [<c12d512c>] driver_attach+0x19/0x1b
    [<c12d46f5>] bus_add_driver+0x17a/0x225
    [<c12d55b8>] driver_register+0x65/0x110
    [<c122af44>] pnp_register_driver+0x17/0x19
    [<c1647a91>] pnp_system_init+0xd/0xf
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
    [<c10238b6>] kernel_thread_helper+0x6/0x10
unreferenced object 0xf6cc0f40 (size 64):
  comm "swapper", pid 1, jiffies 4294892601 (age 57258.708s)
  hex dump (first 32 bytes):
    00 00 d4 fe 00 00 00 00 ff ff d8 fe 00 00 00 00  ................
    c0 3f d2 f6 00 00 00 00 34 57 dc f6 00 00 00 00  .?......4W......
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10ad53f>] kmem_cache_alloc+0xa3/0xd4
    [<c10564a7>] __request_region+0x47/0x201
    [<c12304ef>] reserve_range+0x11f/0x13f
    [<c1230597>] system_pnp_probe+0x88/0xb0
    [<c122b0f7>] pnp_device_probe+0x67/0xaf
    [<c12d5246>] driver_probe_device+0x5b/0x148
    [<c12d539a>] __driver_attach+0x67/0x69
    [<c12d4c33>] bus_for_each_dev+0x46/0x64
    [<c12d512c>] driver_attach+0x19/0x1b
    [<c12d46f5>] bus_add_driver+0x17a/0x225
    [<c12d55b8>] driver_register+0x65/0x110
    [<c122af44>] pnp_register_driver+0x17/0x19
    [<c1647a91>] pnp_system_init+0xd/0xf
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
unreferenced object 0xf6d23f60 (size 32):
  comm "swapper", pid 1, jiffies 4294892601 (age 57258.708s)
  hex dump (first 32 bytes):
    70 6e 70 20 30 30 3a 30 39 00 dc f6 a4 20 d2 f6  pnp 00:09.... ..
    fa 00 0b c1 00 00 00 00 a4 a8 dc f6 2c 00 00 00  ............,...
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10ad53f>] kmem_cache_alloc+0xa3/0xd4
    [<c123040b>] reserve_range+0x3b/0x13f
    [<c1230597>] system_pnp_probe+0x88/0xb0
    [<c122b0f7>] pnp_device_probe+0x67/0xaf
    [<c12d5246>] driver_probe_device+0x5b/0x148
    [<c12d539a>] __driver_attach+0x67/0x69
    [<c12d4c33>] bus_for_each_dev+0x46/0x64
    [<c12d512c>] driver_attach+0x19/0x1b
    [<c12d46f5>] bus_add_driver+0x17a/0x225
    [<c12d55b8>] driver_register+0x65/0x110
    [<c122af44>] pnp_register_driver+0x17/0x19
    [<c1647a91>] pnp_system_init+0xd/0xf
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
    [<c10238b6>] kernel_thread_helper+0x6/0x10
unreferenced object 0xf6cc0f00 (size 64):
  comm "swapper", pid 1, jiffies 4294892601 (age 57258.708s)
  hex dump (first 32 bytes):
    00 00 c0 ff 00 00 00 00 ff ff ef ff 00 00 00 00  ................
    60 3f d2 f6 00 00 00 00 68 ac 6f c1 00 00 00 00  `?......h.o.....
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10ad53f>] kmem_cache_alloc+0xa3/0xd4
    [<c10564a7>] __request_region+0x47/0x201
    [<c12304ef>] reserve_range+0x11f/0x13f
    [<c1230597>] system_pnp_probe+0x88/0xb0
    [<c122b0f7>] pnp_device_probe+0x67/0xaf
    [<c12d5246>] driver_probe_device+0x5b/0x148
    [<c12d539a>] __driver_attach+0x67/0x69
    [<c12d4c33>] bus_for_each_dev+0x46/0x64
    [<c12d512c>] driver_attach+0x19/0x1b
    [<c12d46f5>] bus_add_driver+0x17a/0x225
    [<c12d55b8>] driver_register+0x65/0x110
    [<c122af44>] pnp_register_driver+0x17/0x19
    [<c1647a91>] pnp_system_init+0xd/0xf
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
unreferenced object 0xf6d23f00 (size 32):
  comm "swapper", pid 1, jiffies 4294892601 (age 57258.708s)
  hex dump (first 32 bytes):
    70 6e 70 20 30 30 3a 30 61 00 21 c1 ba ad 21 c1  pnp 00:0a.!...!.
    7c c1 21 c1 f2 7e 21 c1 11 ed 21 c1 6f d2 21 c1  |.!..~!...!.o.!.
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10ad53f>] kmem_cache_alloc+0xa3/0xd4
    [<c123040b>] reserve_range+0x3b/0x13f
    [<c1230597>] system_pnp_probe+0x88/0xb0
    [<c122b0f7>] pnp_device_probe+0x67/0xaf
    [<c12d5246>] driver_probe_device+0x5b/0x148
    [<c12d539a>] __driver_attach+0x67/0x69
    [<c12d4c33>] bus_for_each_dev+0x46/0x64
    [<c12d512c>] driver_attach+0x19/0x1b
    [<c12d46f5>] bus_add_driver+0x17a/0x225
    [<c12d55b8>] driver_register+0x65/0x110
    [<c122af44>] pnp_register_driver+0x17/0x19
    [<c1647a91>] pnp_system_init+0xd/0xf
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
    [<c10238b6>] kernel_thread_helper+0x6/0x10
unreferenced object 0xf6cc0ec0 (size 64):
  comm "swapper", pid 1, jiffies 4294892601 (age 57258.708s)
  hex dump (first 32 bytes):
    00 00 e0 fe 00 00 00 00 ff 0f e0 fe 00 00 00 00  ................
    00 3f d2 f6 00 00 00 00 44 ac 6f c1 00 00 00 00  .?......D.o.....
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10ad53f>] kmem_cache_alloc+0xa3/0xd4
    [<c10564a7>] __request_region+0x47/0x201
    [<c12304ef>] reserve_range+0x11f/0x13f
    [<c1230597>] system_pnp_probe+0x88/0xb0
    [<c122b0f7>] pnp_device_probe+0x67/0xaf
    [<c12d5246>] driver_probe_device+0x5b/0x148
    [<c12d539a>] __driver_attach+0x67/0x69
    [<c12d4c33>] bus_for_each_dev+0x46/0x64
    [<c12d512c>] driver_attach+0x19/0x1b
    [<c12d46f5>] bus_add_driver+0x17a/0x225
    [<c12d55b8>] driver_register+0x65/0x110
    [<c122af44>] pnp_register_driver+0x17/0x19
    [<c1647a91>] pnp_system_init+0xd/0xf
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
unreferenced object 0xf6d23ee0 (size 32):
  comm "swapper", pid 1, jiffies 4294892601 (age 57258.708s)
  hex dump (first 32 bytes):
    70 6e 70 20 30 30 3a 30 61 00 0a c1 d6 0d 22 c1  pnp 00:0a.....".
    6a 0e 22 c1 40 f5 21 c1 59 03 22 c1 2d 04 22 c1  j.".@.!.Y.".-.".
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10ad53f>] kmem_cache_alloc+0xa3/0xd4
    [<c123040b>] reserve_range+0x3b/0x13f
    [<c1230597>] system_pnp_probe+0x88/0xb0
    [<c122b0f7>] pnp_device_probe+0x67/0xaf
    [<c12d5246>] driver_probe_device+0x5b/0x148
    [<c12d539a>] __driver_attach+0x67/0x69
    [<c12d4c33>] bus_for_each_dev+0x46/0x64
    [<c12d512c>] driver_attach+0x19/0x1b
    [<c12d46f5>] bus_add_driver+0x17a/0x225
    [<c12d55b8>] driver_register+0x65/0x110
    [<c122af44>] pnp_register_driver+0x17/0x19
    [<c1647a91>] pnp_system_init+0xd/0xf
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
    [<c10238b6>] kernel_thread_helper+0x6/0x10
unreferenced object 0xf6cc0e80 (size 64):
  comm "swapper", pid 1, jiffies 4294892601 (age 57258.708s)
  hex dump (first 32 bytes):
    00 a0 c8 fe 00 00 00 00 ff af c8 fe 00 00 00 00  ................
    e0 3e d2 f6 00 00 00 00 00 a2 d7 f6 00 00 00 00  .>..............
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10ad53f>] kmem_cache_alloc+0xa3/0xd4
    [<c10564a7>] __request_region+0x47/0x201
    [<c12304ef>] reserve_range+0x11f/0x13f
    [<c1230597>] system_pnp_probe+0x88/0xb0
    [<c122b0f7>] pnp_device_probe+0x67/0xaf
    [<c12d5246>] driver_probe_device+0x5b/0x148
    [<c12d539a>] __driver_attach+0x67/0x69
    [<c12d4c33>] bus_for_each_dev+0x46/0x64
    [<c12d512c>] driver_attach+0x19/0x1b
    [<c12d46f5>] bus_add_driver+0x17a/0x225
    [<c12d55b8>] driver_register+0x65/0x110
    [<c122af44>] pnp_register_driver+0x17/0x19
    [<c1647a91>] pnp_system_init+0xd/0xf
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
unreferenced object 0xf6951920 (size 32):
  comm "swapper", pid 1, jiffies 4294892614 (age 57258.656s)
  hex dump (first 32 bytes):
    63 70 75 69 64 6c 65 00 2f 76 69 72 74 75 61 6c  cpuidle./virtual
    2f 67 72 61 70 68 69 63 73 2f 66 62 63 6f 6e 00  /graphics/fbcon.
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10adb0c>] __kmalloc+0xd4/0x10d
    [<c11e33c6>] kvasprintf+0x2a/0x47
    [<c11db5d7>] kobject_set_name_vargs+0x17/0x52
    [<c11db629>] kobject_add_varg+0x17/0x41
    [<c11db67a>] kobject_init_and_add+0x27/0x2d
    [<c1389b0c>] cpuidle_add_sysfs+0x3e/0x56
    [<c138944e>] __cpuidle_register_device+0xfb/0x116
    [<c13895fc>] cpuidle_register_device+0x18/0x54
    [<c1645397>] intel_idle_init+0x2b9/0x327
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
    [<c10238b6>] kernel_thread_helper+0x6/0x10
    [<ffffffff>] 0xffffffff
unreferenced object 0xf69518e0 (size 32):
  comm "swapper", pid 1, jiffies 4294892614 (age 57258.656s)
  hex dump (first 32 bytes):
    63 70 75 69 64 6c 65 00 a2 17 a2 17 45 9d 45 9d  cpuidle.....E.E.
    3c 1f 3c 1f 4b 85 4b 85 15 66 15 66 92 e1 92 e1  <.<.K.K..f.f....
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10adb0c>] __kmalloc+0xd4/0x10d
    [<c11e33c6>] kvasprintf+0x2a/0x47
    [<c11db5d7>] kobject_set_name_vargs+0x17/0x52
    [<c11db629>] kobject_add_varg+0x17/0x41
    [<c11db67a>] kobject_init_and_add+0x27/0x2d
    [<c1389b0c>] cpuidle_add_sysfs+0x3e/0x56
    [<c138944e>] __cpuidle_register_device+0xfb/0x116
    [<c13895fc>] cpuidle_register_device+0x18/0x54
    [<c1645397>] intel_idle_init+0x2b9/0x327
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
    [<c10238b6>] kernel_thread_helper+0x6/0x10
    [<ffffffff>] 0xffffffff
unreferenced object 0xf69518a0 (size 32):
  comm "swapper", pid 1, jiffies 4294892614 (age 57258.656s)
  hex dump (first 32 bytes):
    63 70 75 69 64 6c 65 00 a2 17 a2 17 45 9d 45 9d  cpuidle.....E.E.
    3c 1f 3c 1f 4b 85 4b 85 15 66 15 66 92 e1 92 e1  <.<.K.K..f.f....
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10adb0c>] __kmalloc+0xd4/0x10d
    [<c11e33c6>] kvasprintf+0x2a/0x47
    [<c11db5d7>] kobject_set_name_vargs+0x17/0x52
    [<c11db629>] kobject_add_varg+0x17/0x41
    [<c11db67a>] kobject_init_and_add+0x27/0x2d
    [<c1389b0c>] cpuidle_add_sysfs+0x3e/0x56
    [<c138944e>] __cpuidle_register_device+0xfb/0x116
    [<c13895fc>] cpuidle_register_device+0x18/0x54
    [<c1645397>] intel_idle_init+0x2b9/0x327
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
    [<c10238b6>] kernel_thread_helper+0x6/0x10
    [<ffffffff>] 0xffffffff
unreferenced object 0xf6951860 (size 32):
  comm "swapper", pid 1, jiffies 4294892614 (age 57258.656s)
  hex dump (first 32 bytes):
    63 70 75 69 64 6c 65 00 a2 17 a2 17 45 9d 45 9d  cpuidle.....E.E.
    3c 1f 3c 1f 4b 85 4b 85 15 66 15 66 92 e1 92 e1  <.<.K.K..f.f....
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10adb0c>] __kmalloc+0xd4/0x10d
    [<c11e33c6>] kvasprintf+0x2a/0x47
    [<c11db5d7>] kobject_set_name_vargs+0x17/0x52
    [<c11db629>] kobject_add_varg+0x17/0x41
    [<c11db67a>] kobject_init_and_add+0x27/0x2d
    [<c1389b0c>] cpuidle_add_sysfs+0x3e/0x56
    [<c138944e>] __cpuidle_register_device+0xfb/0x116
    [<c13895fc>] cpuidle_register_device+0x18/0x54
    [<c1645397>] intel_idle_init+0x2b9/0x327
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
    [<c10238b6>] kernel_thread_helper+0x6/0x10
    [<ffffffff>] 0xffffffff
unreferenced object 0xf6951820 (size 32):
  comm "swapper", pid 1, jiffies 4294892614 (age 57258.656s)
  hex dump (first 32 bytes):
    63 70 75 69 64 6c 65 00 6c 43 6c 43 c2 87 c2 87  cpuidle.lClC....
    f0 1a f0 1a 18 d2 18 d2 b9 1d b9 1d 0a ac 0a ac  ................
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10adb0c>] __kmalloc+0xd4/0x10d
    [<c11e33c6>] kvasprintf+0x2a/0x47
    [<c11db5d7>] kobject_set_name_vargs+0x17/0x52
    [<c11db629>] kobject_add_varg+0x17/0x41
    [<c11db67a>] kobject_init_and_add+0x27/0x2d
    [<c1389b0c>] cpuidle_add_sysfs+0x3e/0x56
    [<c138944e>] __cpuidle_register_device+0xfb/0x116
    [<c13895fc>] cpuidle_register_device+0x18/0x54
    [<c1645397>] intel_idle_init+0x2b9/0x327
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
    [<c10238b6>] kernel_thread_helper+0x6/0x10
    [<ffffffff>] 0xffffffff
unreferenced object 0xf69517e0 (size 32):
  comm "swapper", pid 1, jiffies 4294892614 (age 57258.656s)
  hex dump (first 32 bytes):
    63 70 75 69 64 6c 65 00 6c 43 6c 43 c2 87 c2 87  cpuidle.lClC....
    f0 1a f0 1a 18 d2 18 d2 b9 1d b9 1d 0a ac 0a ac  ................
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10adb0c>] __kmalloc+0xd4/0x10d
    [<c11e33c6>] kvasprintf+0x2a/0x47
    [<c11db5d7>] kobject_set_name_vargs+0x17/0x52
    [<c11db629>] kobject_add_varg+0x17/0x41
    [<c11db67a>] kobject_init_and_add+0x27/0x2d
    [<c1389b0c>] cpuidle_add_sysfs+0x3e/0x56
    [<c138944e>] __cpuidle_register_device+0xfb/0x116
    [<c13895fc>] cpuidle_register_device+0x18/0x54
    [<c1645397>] intel_idle_init+0x2b9/0x327
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
    [<c10238b6>] kernel_thread_helper+0x6/0x10
    [<ffffffff>] 0xffffffff
unreferenced object 0xf69517a0 (size 32):
  comm "swapper", pid 1, jiffies 4294892614 (age 57258.656s)
  hex dump (first 32 bytes):
    63 70 75 69 64 6c 65 00 6c 43 6c 43 c2 87 c2 87  cpuidle.lClC....
    f0 1a f0 1a 18 d2 18 d2 b9 1d b9 1d 0a ac 0a ac  ................
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10adb0c>] __kmalloc+0xd4/0x10d
    [<c11e33c6>] kvasprintf+0x2a/0x47
    [<c11db5d7>] kobject_set_name_vargs+0x17/0x52
    [<c11db629>] kobject_add_varg+0x17/0x41
    [<c11db67a>] kobject_init_and_add+0x27/0x2d
    [<c1389b0c>] cpuidle_add_sysfs+0x3e/0x56
    [<c138944e>] __cpuidle_register_device+0xfb/0x116
    [<c13895fc>] cpuidle_register_device+0x18/0x54
    [<c1645397>] intel_idle_init+0x2b9/0x327
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
    [<c10238b6>] kernel_thread_helper+0x6/0x10
    [<ffffffff>] 0xffffffff
unreferenced object 0xf6951760 (size 32):
  comm "swapper", pid 1, jiffies 4294892614 (age 57258.656s)
  hex dump (first 32 bytes):
    63 70 75 69 64 6c 65 00 e1 1a e1 1a 2e b4 2e b4  cpuidle.........
    6a cb 6a cb 7e ce 7e ce d9 c0 d9 c0 a4 01 a4 01  j.j.~.~.........
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10adb0c>] __kmalloc+0xd4/0x10d
    [<c11e33c6>] kvasprintf+0x2a/0x47
    [<c11db5d7>] kobject_set_name_vargs+0x17/0x52
    [<c11db629>] kobject_add_varg+0x17/0x41
    [<c11db67a>] kobject_init_and_add+0x27/0x2d
    [<c1389b0c>] cpuidle_add_sysfs+0x3e/0x56
    [<c138944e>] __cpuidle_register_device+0xfb/0x116
    [<c13895fc>] cpuidle_register_device+0x18/0x54
    [<c1645397>] intel_idle_init+0x2b9/0x327
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
    [<c10238b6>] kernel_thread_helper+0x6/0x10
    [<ffffffff>] 0xffffffff
unreferenced object 0xf60045c0 (size 32):
  comm "swapper", pid 1, jiffies 4294893885 (age 57253.572s)
  hex dump (first 32 bytes):
    30 00 64 4b bc a3 bc a3 80 f5 80 f5 a7 15 a7 15  0.dK............
    34 07 34 07 69 4f 69 4f f4 47 f4 47 ef 27 ef 27  4.4.iOiO.G.G.'.'
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10adb0c>] __kmalloc+0xd4/0x10d
    [<c11e33c6>] kvasprintf+0x2a/0x47
    [<c11db5d7>] kobject_set_name_vargs+0x17/0x52
    [<c11db629>] kobject_add_varg+0x17/0x41
    [<c11db6ac>] kobject_add+0x2c/0x54
    [<c138ad14>] add_sysfs_fw_map_entry+0x43/0x7c
    [<c164f00f>] memmap_init+0x16/0x30
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
    [<c10238b6>] kernel_thread_helper+0x6/0x10
    [<ffffffff>] 0xffffffff
unreferenced object 0xf6004580 (size 32):
  comm "swapper", pid 1, jiffies 4294893885 (age 57253.572s)
  hex dump (first 32 bytes):
    31 00 8a 82 71 51 71 51 f2 4c f2 4c 60 f0 60 f0  1...qQqQ.L.L`.`.
    22 24 22 24 de c7 de c7 6b a6 6b a6 2d fd 2d fd  "$"$....k.k.-.-.
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10adb0c>] __kmalloc+0xd4/0x10d
    [<c11e33c6>] kvasprintf+0x2a/0x47
    [<c11db5d7>] kobject_set_name_vargs+0x17/0x52
    [<c11db629>] kobject_add_varg+0x17/0x41
    [<c11db6ac>] kobject_add+0x2c/0x54
    [<c138ad14>] add_sysfs_fw_map_entry+0x43/0x7c
    [<c164f00f>] memmap_init+0x16/0x30
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
    [<c10238b6>] kernel_thread_helper+0x6/0x10
    [<ffffffff>] 0xffffffff
unreferenced object 0xf6004500 (size 32):
  comm "swapper", pid 1, jiffies 4294893885 (age 57253.572s)
  hex dump (first 32 bytes):
    33 00 8a 82 71 51 71 51 f2 4c f2 4c 60 f0 60 f0  3...qQqQ.L.L`.`.
    22 24 22 24 de c7 de c7 6b a6 6b a6 2d fd 2d fd  "$"$....k.k.-.-.
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10adb0c>] __kmalloc+0xd4/0x10d
    [<c11e33c6>] kvasprintf+0x2a/0x47
    [<c11db5d7>] kobject_set_name_vargs+0x17/0x52
    [<c11db629>] kobject_add_varg+0x17/0x41
    [<c11db6ac>] kobject_add+0x2c/0x54
    [<c138ad14>] add_sysfs_fw_map_entry+0x43/0x7c
    [<c164f00f>] memmap_init+0x16/0x30
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
    [<c10238b6>] kernel_thread_helper+0x6/0x10
    [<ffffffff>] 0xffffffff
unreferenced object 0xf60044c0 (size 32):
  comm "swapper", pid 1, jiffies 4294893885 (age 57253.572s)
  hex dump (first 32 bytes):
    34 00 db 30 bc 2a bc 2a 0d a9 0d a9 b0 38 b0 38  4..0.*.*.....8.8
    5a 3d 5a 3d 5d 18 5d 18 fc df fc df 42 0f 42 0f  Z=Z=].].....B.B.
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10adb0c>] __kmalloc+0xd4/0x10d
    [<c11e33c6>] kvasprintf+0x2a/0x47
    [<c11db5d7>] kobject_set_name_vargs+0x17/0x52
    [<c11db629>] kobject_add_varg+0x17/0x41
    [<c11db6ac>] kobject_add+0x2c/0x54
    [<c138ad14>] add_sysfs_fw_map_entry+0x43/0x7c
    [<c164f00f>] memmap_init+0x16/0x30
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
    [<c10238b6>] kernel_thread_helper+0x6/0x10
    [<ffffffff>] 0xffffffff
unreferenced object 0xf6004480 (size 32):
  comm "swapper", pid 1, jiffies 4294893885 (age 57253.576s)
  hex dump (first 32 bytes):
    35 00 db 30 bc 2a bc 2a 0d a9 0d a9 b0 38 b0 38  5..0.*.*.....8.8
    5a 3d 5a 3d 5d 18 5d 18 fc df fc df 42 0f 42 0f  Z=Z=].].....B.B.
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10adb0c>] __kmalloc+0xd4/0x10d
    [<c11e33c6>] kvasprintf+0x2a/0x47
    [<c11db5d7>] kobject_set_name_vargs+0x17/0x52
    [<c11db629>] kobject_add_varg+0x17/0x41
    [<c11db6ac>] kobject_add+0x2c/0x54
    [<c138ad14>] add_sysfs_fw_map_entry+0x43/0x7c
    [<c164f00f>] memmap_init+0x16/0x30
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
    [<c10238b6>] kernel_thread_helper+0x6/0x10
    [<ffffffff>] 0xffffffff
unreferenced object 0xf6004440 (size 32):
  comm "swapper", pid 1, jiffies 4294893885 (age 57253.576s)
  hex dump (first 32 bytes):
    36 00 db 30 bc 2a bc 2a 0d a9 0d a9 b0 38 b0 38  6..0.*.*.....8.8
    5a 3d 5a 3d 5d 18 5d 18 fc df fc df 42 0f 42 0f  Z=Z=].].....B.B.
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10adb0c>] __kmalloc+0xd4/0x10d
    [<c11e33c6>] kvasprintf+0x2a/0x47
    [<c11db5d7>] kobject_set_name_vargs+0x17/0x52
    [<c11db629>] kobject_add_varg+0x17/0x41
    [<c11db6ac>] kobject_add+0x2c/0x54
    [<c138ad14>] add_sysfs_fw_map_entry+0x43/0x7c
    [<c164f00f>] memmap_init+0x16/0x30
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
    [<c10238b6>] kernel_thread_helper+0x6/0x10
    [<ffffffff>] 0xffffffff
unreferenced object 0xf6004400 (size 32):
  comm "swapper", pid 1, jiffies 4294893885 (age 57253.576s)
  hex dump (first 32 bytes):
    37 00 35 f9 71 d8 71 d8 80 ef 80 ef 88 22 88 22  7.5.q.q......"."
    b3 e1 b3 e1 15 6f 15 6f 63 3e 63 3e 80 d5 80 d5  .....o.oc>c>....
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10adb0c>] __kmalloc+0xd4/0x10d
    [<c11e33c6>] kvasprintf+0x2a/0x47
    [<c11db5d7>] kobject_set_name_vargs+0x17/0x52
    [<c11db629>] kobject_add_varg+0x17/0x41
    [<c11db6ac>] kobject_add+0x2c/0x54
    [<c138ad14>] add_sysfs_fw_map_entry+0x43/0x7c
    [<c164f00f>] memmap_init+0x16/0x30
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
    [<c10238b6>] kernel_thread_helper+0x6/0x10
    [<ffffffff>] 0xffffffff
unreferenced object 0xf60043c0 (size 32):
  comm "swapper", pid 1, jiffies 4294893885 (age 57253.576s)
  hex dump (first 32 bytes):
    38 00 35 f9 71 d8 71 d8 80 ef 80 ef 88 22 88 22  8.5.q.q......"."
    b3 e1 b3 e1 15 6f 15 6f 63 3e 63 3e 80 d5 80 d5  .....o.oc>c>....
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10adb0c>] __kmalloc+0xd4/0x10d
    [<c11e33c6>] kvasprintf+0x2a/0x47
    [<c11db5d7>] kobject_set_name_vargs+0x17/0x52
    [<c11db629>] kobject_add_varg+0x17/0x41
    [<c11db6ac>] kobject_add+0x2c/0x54
    [<c138ad14>] add_sysfs_fw_map_entry+0x43/0x7c
    [<c164f00f>] memmap_init+0x16/0x30
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
    [<c10238b6>] kernel_thread_helper+0x6/0x10
    [<ffffffff>] 0xffffffff
unreferenced object 0xf6004380 (size 32):
  comm "swapper", pid 1, jiffies 4294893885 (age 57253.576s)
  hex dump (first 32 bytes):
    39 00 35 f9 71 d8 71 d8 80 ef 80 ef 88 22 88 22  9.5.q.q......"."
    b3 e1 b3 e1 15 6f 15 6f 63 3e 63 3e 80 d5 80 d5  .....o.oc>c>....
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10adb0c>] __kmalloc+0xd4/0x10d
    [<c11e33c6>] kvasprintf+0x2a/0x47
    [<c11db5d7>] kobject_set_name_vargs+0x17/0x52
    [<c11db629>] kobject_add_varg+0x17/0x41
    [<c11db6ac>] kobject_add+0x2c/0x54
    [<c138ad14>] add_sysfs_fw_map_entry+0x43/0x7c
    [<c164f00f>] memmap_init+0x16/0x30
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
    [<c10238b6>] kernel_thread_helper+0x6/0x10
    [<ffffffff>] 0xffffffff
unreferenced object 0xf6004340 (size 32):
  comm "swapper", pid 1, jiffies 4294893885 (age 57253.576s)
  hex dump (first 32 bytes):
    31 30 00 b6 1f 19 1f 19 11 24 11 24 e1 22 e1 22  10.......$.$."."
    01 f9 01 f9 df 38 df 38 62 cd 62 cd 0e 04 0e 04  .....8.8b.b.....
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10adb0c>] __kmalloc+0xd4/0x10d
    [<c11e33c6>] kvasprintf+0x2a/0x47
    [<c11db5d7>] kobject_set_name_vargs+0x17/0x52
    [<c11db629>] kobject_add_varg+0x17/0x41
    [<c11db6ac>] kobject_add+0x2c/0x54
    [<c138ad14>] add_sysfs_fw_map_entry+0x43/0x7c
    [<c164f00f>] memmap_init+0x16/0x30
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
    [<c10238b6>] kernel_thread_helper+0x6/0x10
    [<ffffffff>] 0xffffffff
unreferenced object 0xf6681400 (size 1024):
  comm "async/2", pid 1307, jiffies 4294894138 (age 57252.564s)
  hex dump (first 32 bytes):
    80 87 ff ff c4 ff ff ff c4 ff ff ff c4 ff ff ff  ................
    fc ff ff ff fc ff ff ff fc ff ff ff fc ff ff ff  ................
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10adb0c>] __kmalloc+0xd4/0x10d
    [<c10ae982>] pcpu_mem_alloc+0x18/0x3a
    [<c10af239>] pcpu_extend_area_map+0x1a/0xad
    [<c10af578>] pcpu_alloc+0x2ac/0x82b
    [<c10afb10>] __alloc_percpu+0xa/0xc
    [<c11d4518>] alloc_disk_node+0x2e/0xbf
    [<c11d45b6>] alloc_disk+0xd/0xf
    [<c130260c>] sd_probe+0x54/0x298
    [<c12d5246>] driver_probe_device+0x5b/0x148
    [<c12d53ca>] __device_attach+0x2e/0x32
    [<c12d49f3>] bus_for_each_drv+0x46/0x64
    [<c12d5449>] device_attach+0x5c/0x60
    [<c12d484d>] bus_probe_device+0x1a/0x30
    [<c12d358a>] device_add+0x448/0x509
    [<c12fb881>] scsi_sysfs_add_sdev+0x54/0x212
unreferenced object 0xf6b10620 (size 32):
  comm "X", pid 2268, jiffies 4294894722 (age 57250.228s)
  hex dump (first 32 bytes):
    6e 6f 75 76 65 61 75 40 70 63 69 3a 30 30 30 30  nouveau@pci:0000
    3a 30 35 3a 30 30 2e 30 00 00 00 00 00 00 00 00  :05:00.0........
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10adb0c>] __kmalloc+0xd4/0x10d
    [<c125315e>] drm_setversion+0x140/0x1bf
    [<c12514f2>] drm_ioctl+0x258/0x3d7
    [<c10bdd42>] vfs_ioctl+0x27/0x9b
    [<c10bdee2>] do_vfs_ioctl+0x66/0x54b
    [<c10be3fa>] sys_ioctl+0x33/0x4f
    [<c102339c>] sysenter_do_call+0x12/0x2c
    [<ffffffff>] 0xffffffff

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-14  6:12 kmemleak, cpu usage jump out of nowhere Zeno Davatz
@ 2010-07-14  8:05 ` Pekka Enberg
  2010-07-14  8:27   ` Zeno Davatz
  2010-07-14  8:31   ` Damien Wyart
  2010-07-14  9:57 ` Catalin Marinas
  1 sibling, 2 replies; 44+ messages in thread
From: Pekka Enberg @ 2010-07-14  8:05 UTC (permalink / raw)
  To: Zeno Davatz; +Cc: linux-kernel, Catalin Marinas, Andrew Morton

On Wed, Jul 14, 2010 at 9:12 AM, Zeno Davatz <zdavatz@gmail.com> wrote:
> I got a new Intel core-8 i7 processor.
>
> I am on kernel uname -a
>
> Linux zenogentoo 2.6.35-rc5 #97 SMP Tue Jul 13 16:13:25 CEST 2010 i686
> Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz GenuineIntel GNU/Linux
>
> Sometimes in the middle of nowhere all of a sudden all of my 8-cores
> are at 100% CPU usage and my machine really lags and hangs and is not
> useable anymore. Some random process just grabs a bunch CPUs according
> to htop.

Why did you enable CONFIG_DEBUG_KMEMLEAK? Memory leak scanning is
likely the source of these pauses.

> dmesg tell me that
>
> kmemleak: 38 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
> kmemleak: 2 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
> kmemleak: 1 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
> kmemleak: 2 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
> kmemleak: 2 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
> kmemleak: 1 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
>
> I am attaching you the file from /sys/kernel/debug/kmemleak

Zeno, can you post your dmesg and .config, please?

We have a bunch of suspected leaks here. The first class of leaks is
related to reserve_region():

unreferenced object 0xf6d80740 (size 64):
  comm "swapper", pid 1, jiffies 4294892590 (age 57258.752s)
  hex dump (first 32 bytes):
    00 00 ee c7 00 00 00 00 ff b7 ee c7 00 00 00 00  ................
    7c 09 52 c1 00 00 00 80 00 f2 5e c1 20 ac 6f c1  |.R.......^. .o.
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10ad53f>] kmem_cache_alloc+0xa3/0xd4
    [<c163b782>] __reserve_region_with_split+0x29/0x149
    [<c163b86a>] __reserve_region_with_split+0x111/0x149
    [<c163b89a>] __reserve_region_with_split+0x141/0x149
    [<c163b89a>] __reserve_region_with_split+0x141/0x149
    [<c163b89a>] __reserve_region_with_split+0x141/0x149
    [<c163b8de>] reserve_region_with_split+0x3c/0x4f
    [<c162e307>] e820_reserve_resources_late+0xea/0x108
    [<c16504e6>] pcibios_resource_survey+0x23/0x2a
    [<c1652022>] pcibios_init+0x61/0x73
    [<c165172b>] pci_subsys_init+0x43/0x48
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
    [<c10238b6>] kernel_thread_helper+0x6/0x10
    [<ffffffff>] 0xffffffff

unreferenced object 0xf6d232a0 (size 32):
  comm "swapper", pid 1, jiffies 4294892601 (age 57258.708s)
  hex dump (first 32 bytes):
    70 6e 70 20 30 30 3a 30 31 00 d2 f6 fa 00 0b c1  pnp 00:01.......
    00 00 00 00 04 aa dc f6 2c 00 00 00 01 00 00 00  ........,.......
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10ad53f>] kmem_cache_alloc+0xa3/0xd4
    [<c123040b>] reserve_range+0x3b/0x13f
    [<c1230597>] system_pnp_probe+0x88/0xb0
    [<c122b0f7>] pnp_device_probe+0x67/0xaf
    [<c12d5246>] driver_probe_device+0x5b/0x148
    [<c12d539a>] __driver_attach+0x67/0x69
    [<c12d4c33>] bus_for_each_dev+0x46/0x64
    [<c12d512c>] driver_attach+0x19/0x1b
    [<c12d46f5>] bus_add_driver+0x17a/0x225
    [<c12d55b8>] driver_register+0x65/0x110
    [<c122af44>] pnp_register_driver+0x17/0x19
    [<c1647a91>] pnp_system_init+0xd/0xf
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
    [<c10238b6>] kernel_thread_helper+0x6/0x10

I scanned through both call sites briefly but didn't find anything obvious.

The second class of leaks seems to be related to kobjects:

unreferenced object 0xf6951920 (size 32):
  comm "swapper", pid 1, jiffies 4294892614 (age 57258.656s)
  hex dump (first 32 bytes):
    63 70 75 69 64 6c 65 00 2f 76 69 72 74 75 61 6c  cpuidle./virtual
    2f 67 72 61 70 68 69 63 73 2f 66 62 63 6f 6e 00  /graphics/fbcon.
  backtrace:
    [<c11e33c6>] kvasprintf+0x2a/0x47
    [<c11db5d7>] kobject_set_name_vargs+0x17/0x52
    [<c11db629>] kobject_add_varg+0x17/0x41
    [<c11db67a>] kobject_init_and_add+0x27/0x2d
    [<c1389b0c>] cpuidle_add_sysfs+0x3e/0x56
    [<c138944e>] __cpuidle_register_device+0xfb/0x116
    [<c13895fc>] cpuidle_register_device+0x18/0x54
    [<c1645397>] intel_idle_init+0x2b9/0x327
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
    [<c10238b6>] kernel_thread_helper+0x6/0x10
    [<ffffffff>] 0xffffffff

unreferenced object 0xf60045c0 (size 32):
  comm "swapper", pid 1, jiffies 4294893885 (age 57253.572s)
  hex dump (first 32 bytes):
    30 00 64 4b bc a3 bc a3 80 f5 80 f5 a7 15 a7 15  0.dK............
    34 07 34 07 69 4f 69 4f f4 47 f4 47 ef 27 ef 27  4.4.iOiO.G.G.'.'
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10adb0c>] __kmalloc+0xd4/0x10d
    [<c11e33c6>] kvasprintf+0x2a/0x47
    [<c11db5d7>] kobject_set_name_vargs+0x17/0x52
    [<c11db629>] kobject_add_varg+0x17/0x41
    [<c11db6ac>] kobject_add+0x2c/0x54
    [<c138ad14>] add_sysfs_fw_map_entry+0x43/0x7c
    [<c164f00f>] memmap_init+0x16/0x30
    [<c1001114>] do_one_initcall+0x27/0x178
    [<c162b357>] kernel_init+0x129/0x1c7
    [<c10238b6>] kernel_thread_helper+0x6/0x10
    [<ffffffff>] 0xffffffff

The third class of leaks is relateed to drm_setversion():

unreferenced object 0xf6b10620 (size 32):
  comm "X", pid 2268, jiffies 4294894722 (age 57250.228s)
  hex dump (first 32 bytes):
    6e 6f 75 76 65 61 75 40 70 63 69 3a 30 30 30 30  nouveau@pci:0000
    3a 30 35 3a 30 30 2e 30 00 00 00 00 00 00 00 00  :05:00.0........
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10adb0c>] __kmalloc+0xd4/0x10d
    [<c125315e>] drm_setversion+0x140/0x1bf
    [<c12514f2>] drm_ioctl+0x258/0x3d7
    [<c10bdd42>] vfs_ioctl+0x27/0x9b
    [<c10bdee2>] do_vfs_ioctl+0x66/0x54b
    [<c10be3fa>] sys_ioctl+0x33/0x4f
    [<c102339c>] sysenter_do_call+0x12/0x2c
    [<ffffffff>] 0xffffffff

for which I wasn't able to find the allocation call-site. Maybe Zeno
has some out-of-tree DRM module?

The fourth class of leaks is related to per-CPU allocations in the block layer:

unreferenced object 0xf6681400 (size 1024):
  comm "async/2", pid 1307, jiffies 4294894138 (age 57252.564s)
  hex dump (first 32 bytes):
    80 87 ff ff c4 ff ff ff c4 ff ff ff c4 ff ff ff  ................
    fc ff ff ff fc ff ff ff fc ff ff ff fc ff ff ff  ................
  backtrace:
    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
    [<c10adb0c>] __kmalloc+0xd4/0x10d
    [<c10ae982>] pcpu_mem_alloc+0x18/0x3a
    [<c10af239>] pcpu_extend_area_map+0x1a/0xad
    [<c10af578>] pcpu_alloc+0x2ac/0x82b
    [<c10afb10>] __alloc_percpu+0xa/0xc
    [<c11d4518>] alloc_disk_node+0x2e/0xbf
    [<c11d45b6>] alloc_disk+0xd/0xf
    [<c130260c>] sd_probe+0x54/0x298
    [<c12d5246>] driver_probe_device+0x5b/0x148
    [<c12d53ca>] __device_attach+0x2e/0x32
    [<c12d49f3>] bus_for_each_drv+0x46/0x64
    [<c12d5449>] device_attach+0x5c/0x60
    [<c12d484d>] bus_probe_device+0x1a/0x30
    [<c12d358a>] device_add+0x448/0x509
    [<c12fb881>] scsi_sysfs_add_sdev+0x54/0x212

for which I didn't find anything obvious that could explain it.

I suspect most of the reports are false positives. Catalin, what do
you make out of them?

                        Pekka

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-14  8:05 ` Pekka Enberg
@ 2010-07-14  8:27   ` Zeno Davatz
  2010-07-14  9:47     ` Catalin Marinas
  2010-07-14  8:31   ` Damien Wyart
  1 sibling, 1 reply; 44+ messages in thread
From: Zeno Davatz @ 2010-07-14  8:27 UTC (permalink / raw)
  To: Pekka Enberg; +Cc: linux-kernel, Catalin Marinas, Andrew Morton

[-- Attachment #1: Type: text/plain, Size: 2788 bytes --]

Dear Pekka

On Wed, Jul 14, 2010 at 10:05 AM, Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> On Wed, Jul 14, 2010 at 9:12 AM, Zeno Davatz <zdavatz@gmail.com> wrote:
>> I got a new Intel core-8 i7 processor.
>>
>> I am on kernel uname -a
>>
>> Linux zenogentoo 2.6.35-rc5 #97 SMP Tue Jul 13 16:13:25 CEST 2010 i686
>> Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz GenuineIntel GNU/Linux
>>
>> Sometimes in the middle of nowhere all of a sudden all of my 8-cores
>> are at 100% CPU usage and my machine really lags and hangs and is not
>> useable anymore. Some random process just grabs a bunch CPUs according
>> to htop.
>
> Why did you enable CONFIG_DEBUG_KMEMLEAK? Memory leak scanning is
> likely the source of these pauses.

Shall I disable that? I will do that and try again.

>> I am attaching you the file from /sys/kernel/debug/kmemleak
>
> Zeno, can you post your dmesg and .config, please?

Sure, see attached files.

> The third class of leaks is relateed to drm_setversion():
>
> unreferenced object 0xf6b10620 (size 32):
>  comm "X", pid 2268, jiffies 4294894722 (age 57250.228s)
>  hex dump (first 32 bytes):
>    6e 6f 75 76 65 61 75 40 70 63 69 3a 30 30 30 30  nouveau@pci:0000
>    3a 30 35 3a 30 30 2e 30 00 00 00 00 00 00 00 00  :05:00.0........
>  backtrace:
>    [<c145d4eb>] kmemleak_alloc+0x27/0x4d
>    [<c10adb0c>] __kmalloc+0xd4/0x10d
>    [<c125315e>] drm_setversion+0x140/0x1bf
>    [<c12514f2>] drm_ioctl+0x258/0x3d7
>    [<c10bdd42>] vfs_ioctl+0x27/0x9b
>    [<c10bdee2>] do_vfs_ioctl+0x66/0x54b
>    [<c10be3fa>] sys_ioctl+0x33/0x4f
>    [<c102339c>] sysenter_do_call+0x12/0x2c
>    [<ffffffff>] 0xffffffff
>
> for which I wasn't able to find the allocation call-site. Maybe Zeno
> has some out-of-tree DRM module?

I am using the nouveau drivers in the kernel as I got an Nvidia Graphics card.

05:00.0 VGA compatible controller: nVidia Corporation G98 [GeForce
8400 GS] (rev a1) (prog-if 00 [VGA controller])
        Subsystem: ASUSTeK Computer Inc. Device 8321
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at fa000000 (32-bit, non-prefetchable) [size=16M]
        Memory at d0000000 (64-bit, prefetchable) [size=256M]
        Memory at f8000000 (64-bit, non-prefetchable) [size=32M]
        I/O ports at ec00 [size=128]
        [virtual] Expansion ROM at fb000000 [disabled] [size=128K]
        Capabilities: [60] Power Management version 3
        Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [78] Express Endpoint, MSI 00
        Capabilities: [100] Virtual Channel <?>
        Capabilities: [128] Power Budgeting <?>
        Capabilities: [600] Vendor Specific Information <?>
        Kernel driver in use: nouveau

Best
Zeno

[-- Attachment #2: .config --]
[-- Type: application/octet-stream, Size: 63537 bytes --]

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.35-rc4
# Mon Jul  5 09:18:17 2010
#
# CONFIG_64BIT is not set
CONFIG_X86_32=y
# CONFIG_X86_64 is not set
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
CONFIG_OUTPUT_FORMAT="elf32-i386"
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/i386_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_NEED_DMA_MAP_STATE is not set
CONFIG_NEED_SG_DMA_LENGTH=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
# CONFIG_GENERIC_TIME_VSYSCALL is not set
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 is not set
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
# CONFIG_ZONE_DMA32 is not set
CONFIG_ARCH_POPULATES_NODE_MAP=y
# CONFIG_AUDIT_ARCH is not set
CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
CONFIG_HAVE_EARLY_RES=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_32_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_TRAMPOLINE=y
CONFIG_X86_32_LAZY_GS=y
CONFIG_ARCH_HWEIGHT_CFLAGS="-fcall-saved-ecx -fcall-saved-edx"
CONFIG_KTIME_SCALAR=y
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_CROSS_COMPILE=""
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_BZIP2=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_HAVE_KERNEL_LZO=y
CONFIG_KERNEL_GZIP=y
# CONFIG_KERNEL_BZIP2 is not set
# CONFIG_KERNEL_LZMA is not set
# 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 is not set
# 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=32
# CONFIG_RCU_FANOUT_EXACT is not set
# CONFIG_RCU_FAST_NO_HZ is not set
# CONFIG_TREE_RCU_TRACE is not set
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=14
CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
# CONFIG_CGROUPS is not set
# CONFIG_SYSFS_DEPRECATED_V2 is not set
# CONFIG_RELAY is not set
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 is not set
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
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 is not set
# 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_PERF_COUNTERS is not set
# CONFIG_DEBUG_PERF_USE_VMALLOC is not set
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_PCI_QUIRKS=y
CONFIG_COMPAT_BRK=y
CONFIG_SLAB=y
# CONFIG_SLUB is not set
# CONFIG_SLOB is not set
CONFIG_PROFILING=y
CONFIG_OPROFILE=y
# CONFIG_OPROFILE_EVENT_MULTIPLEX is not set
CONFIG_HAVE_OPROFILE=y
# CONFIG_KPROBES is not set
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
CONFIG_USER_RETURN_NOTIFIER=y
CONFIG_HAVE_IOREMAP_PROT=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_OPTPROBES=y
CONFIG_HAVE_ARCH_TRACEHOOK=y
CONFIG_HAVE_DMA_ATTRS=y
CONFIG_HAVE_REGS_AND_STACK_ACCESS_API=y
CONFIG_HAVE_DMA_API_DEBUG=y
CONFIG_HAVE_HW_BREAKPOINT=y
CONFIG_HAVE_MIXED_BREAKPOINTS_REGS=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=y
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=y
CONFIG_MODVERSIONS=y
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_STOP_MACHINE=y
CONFIG_BLOCK=y
# CONFIG_LBDAF is not set
# CONFIG_BLK_DEV_BSG is not set
# CONFIG_BLK_DEV_INTEGRITY is not set

#
# 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_PREEMPT_NOTIFIERS=y
# 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 is not set
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_SMP=y
# CONFIG_SPARSE_IRQ is not set
CONFIG_X86_MPPARSE=y
# CONFIG_X86_BIGSMP is not set
CONFIG_X86_EXTENDED_PLATFORM=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_MRST is not set
# CONFIG_X86_RDC321X is not set
# CONFIG_X86_32_NON_STANDARD is not set
CONFIG_X86_SUPPORTS_MEMORY_FAILURE=y
CONFIG_SCHED_OMIT_FRAME_POINTER=y
CONFIG_PARAVIRT_GUEST=y
# CONFIG_XEN is not set
# CONFIG_VMI is not set
CONFIG_KVM_CLOCK=y
CONFIG_KVM_GUEST=y
# CONFIG_LGUEST_GUEST is not set
CONFIG_PARAVIRT=y
# CONFIG_PARAVIRT_SPINLOCKS is not set
CONFIG_PARAVIRT_CLOCK=y
# CONFIG_PARAVIRT_DEBUG is not set
CONFIG_NO_BOOTMEM=y
# 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=y
# 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 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CPU=y
CONFIG_X86_INTERNODE_CACHE_SHIFT=7
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_X86_XADD=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_TSC=y
CONFIG_X86_CMPXCHG64=y
CONFIG_X86_CMOV=y
CONFIG_X86_MINIMUM_CPU_FAMILY=5
CONFIG_X86_DEBUGCTLMSR=y
CONFIG_CPU_SUP_INTEL=y
CONFIG_CPU_SUP_CYRIX_32=y
CONFIG_CPU_SUP_AMD=y
CONFIG_CPU_SUP_CENTAUR=y
CONFIG_CPU_SUP_TRANSMETA_32=y
CONFIG_CPU_SUP_UMC_32=y
CONFIG_HPET_TIMER=y
CONFIG_DMI=y
# CONFIG_IOMMU_HELPER is not set
# CONFIG_IOMMU_API is not set
CONFIG_NR_CPUS=8
CONFIG_SCHED_SMT=y
CONFIG_SCHED_MC=y
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
# CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS is not set
CONFIG_X86_MCE=y
CONFIG_X86_MCE_INTEL=y
# CONFIG_X86_MCE_AMD is not set
# CONFIG_X86_ANCIENT_MCE is not set
CONFIG_X86_MCE_THRESHOLD=y
# CONFIG_X86_MCE_INJECT is not set
CONFIG_X86_THERMAL_VECTOR=y
CONFIG_VM86=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_X86_REBOOTFIXUPS is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
CONFIG_X86_CPUID=y
# CONFIG_NOHIGHMEM is not set
# CONFIG_HIGHMEM4G is not set
CONFIG_HIGHMEM64G=y
CONFIG_PAGE_OFFSET=0xC0000000
CONFIG_HIGHMEM=y
CONFIG_X86_PAE=y
CONFIG_ARCH_PHYS_ADDR_T_64BIT=y
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_ILLEGAL_POINTER_VALUE=0
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_SPARSEMEM_STATIC=y
CONFIG_PAGEFLAGS_EXTENDED=y
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_PHYS_ADDR_T_64BIT=y
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_VIRT_TO_BUS=y
CONFIG_MMU_NOTIFIER=y
# CONFIG_KSM is not set
CONFIG_DEFAULT_MMAP_MIN_ADDR=4096
CONFIG_ARCH_SUPPORTS_MEMORY_FAILURE=y
# CONFIG_MEMORY_FAILURE is not set
# CONFIG_HIGHPTE is not set
# CONFIG_X86_CHECK_BIOS_CORRUPTION is not set
CONFIG_X86_RESERVE_LOW_64K=y
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_MTRR_SANITIZER is not set
CONFIG_X86_PAT=y
CONFIG_ARCH_USES_PG_UNCACHED=y
# CONFIG_EFI is not set
CONFIG_SECCOMP=y
# CONFIG_CC_STACKPROTECTOR is not set
# CONFIG_HZ_100 is not set
CONFIG_HZ_250=y
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=250
# CONFIG_SCHED_HRTICK is not set
# CONFIG_KEXEC is not set
# CONFIG_CRASH_DUMP is not set
CONFIG_PHYSICAL_START=0x1000000
# CONFIG_RELOCATABLE is not set
CONFIG_PHYSICAL_ALIGN=0x100000
CONFIG_HOTPLUG_CPU=y
CONFIG_COMPAT_VDSO=y
# CONFIG_CMDLINE_BOOL is not set
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y

#
# Power management and ACPI options
#
CONFIG_PM=y
# CONFIG_PM_DEBUG is not set
CONFIG_PM_SLEEP_SMP=y
CONFIG_PM_SLEEP=y
CONFIG_SUSPEND_NVS=y
CONFIG_SUSPEND=y
CONFIG_SUSPEND_FREEZER=y
# CONFIG_HIBERNATION is not set
# CONFIG_PM_RUNTIME is not set
CONFIG_PM_OPS=y
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_PROCFS=y
CONFIG_ACPI_PROCFS_POWER=y
# CONFIG_ACPI_POWER_METER is not set
CONFIG_ACPI_SYSFS_POWER=y
CONFIG_ACPI_PROC_EVENT=y
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_VIDEO=y
CONFIG_ACPI_FAN=y
CONFIG_ACPI_DOCK=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_HOTPLUG_CPU=y
# CONFIG_ACPI_PROCESSOR_AGGREGATOR is not set
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_CUSTOM_DSDT is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
# CONFIG_ACPI_PCI_SLOT is not set
CONFIG_X86_PM_TIMER=y
CONFIG_ACPI_CONTAINER=y
# CONFIG_ACPI_SBS is not set
# CONFIG_ACPI_HED is not set
# CONFIG_ACPI_APEI is not set
# CONFIG_SFI is not set
# CONFIG_APM 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 is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_GOV_POWERSAVE is not set
# CONFIG_CPU_FREQ_GOV_USERSPACE is not set
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
# CONFIG_CPU_FREQ_GOV_CONSERVATIVE is not set

#
# CPUFreq processor drivers
#
# CONFIG_X86_PCC_CPUFREQ is not set
# CONFIG_X86_ACPI_CPUFREQ is not set
# CONFIG_X86_POWERNOW_K6 is not set
# CONFIG_X86_POWERNOW_K7 is not set
# CONFIG_X86_POWERNOW_K8 is not set
# CONFIG_X86_GX_SUSPMOD is not set
# CONFIG_X86_SPEEDSTEP_CENTRINO is not set
# CONFIG_X86_SPEEDSTEP_ICH is not set
# CONFIG_X86_SPEEDSTEP_SMI is not set
# CONFIG_X86_P4_CLOCKMOD is not set
# CONFIG_X86_CPUFREQ_NFORCE2 is not set
# CONFIG_X86_LONGRUN is not set
# CONFIG_X86_LONGHAUL is not set
# CONFIG_X86_E_POWERSAVER is not set

#
# shared options
#
# CONFIG_X86_SPEEDSTEP_LIB is not set
CONFIG_CPU_IDLE=y
CONFIG_CPU_IDLE_GOV_LADDER=y
CONFIG_CPU_IDLE_GOV_MENU=y
CONFIG_INTEL_IDLE=y

#
# Bus options (PCI etc.)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
# CONFIG_PCI_GOOLPC is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCI_DOMAINS=y
# CONFIG_PCI_CNB20LE_QUIRK is not set
# CONFIG_PCIEPORTBUS is not set
CONFIG_ARCH_SUPPORTS_MSI=y
# CONFIG_PCI_MSI is not set
# CONFIG_PCI_DEBUG is not set
# CONFIG_PCI_STUB is not set
CONFIG_HT_IRQ=y
# CONFIG_PCI_IOV is not set
CONFIG_PCI_IOAPIC=y
CONFIG_ISA_DMA_API=y
CONFIG_ISA=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
# CONFIG_OLPC is not set
CONFIG_K8_NB=y
# CONFIG_PCCARD is not set
# CONFIG_HOTPLUG_PCI is not set

#
# Executable file formats / Emulations
#
CONFIG_BINFMT_ELF=y
# CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set
CONFIG_HAVE_AOUT=y
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_MISC=y
CONFIG_HAVE_ATOMIC_IOMAP=y
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_UNIX=y
CONFIG_XFRM=y
# CONFIG_XFRM_USER is not set
# CONFIG_XFRM_SUB_POLICY is not set
# CONFIG_XFRM_MIGRATE is not set
# CONFIG_XFRM_STATISTICS is not set
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_FIB_HASH=y
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_XFRM_TUNNEL is not set
# CONFIG_INET_TUNNEL is not set
CONFIG_INET_XFRM_MODE_TRANSPORT=y
CONFIG_INET_XFRM_MODE_TUNNEL=y
CONFIG_INET_XFRM_MODE_BEET=y
# CONFIG_INET_LRO is not set
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_TCP_MD5SIG is not set
# CONFIG_IPV6 is not set
# CONFIG_NETWORK_SECMARK is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_NETFILTER_ADVANCED=y
CONFIG_BRIDGE_NETFILTER=y

#
# Core Netfilter Configuration
#
# CONFIG_NETFILTER_NETLINK_QUEUE is not set
# CONFIG_NETFILTER_NETLINK_LOG is not set
# CONFIG_NF_CONNTRACK is not set
CONFIG_NETFILTER_XTABLES=y

#
# Xtables combined modules
#
# CONFIG_NETFILTER_XT_MARK is not set

#
# Xtables targets
#
# CONFIG_NETFILTER_XT_TARGET_CLASSIFY is not set
# CONFIG_NETFILTER_XT_TARGET_MARK is not set
# CONFIG_NETFILTER_XT_TARGET_NFLOG is not set
# CONFIG_NETFILTER_XT_TARGET_NFQUEUE is not set
# CONFIG_NETFILTER_XT_TARGET_RATEEST is not set
# CONFIG_NETFILTER_XT_TARGET_TEE is not set
# CONFIG_NETFILTER_XT_TARGET_TCPMSS is not set

#
# Xtables matches
#
# CONFIG_NETFILTER_XT_MATCH_COMMENT is not set
# CONFIG_NETFILTER_XT_MATCH_DCCP is not set
# CONFIG_NETFILTER_XT_MATCH_DSCP is not set
# CONFIG_NETFILTER_XT_MATCH_ESP is not set
# CONFIG_NETFILTER_XT_MATCH_HASHLIMIT is not set
# CONFIG_NETFILTER_XT_MATCH_HL is not set
# CONFIG_NETFILTER_XT_MATCH_IPRANGE is not set
# CONFIG_NETFILTER_XT_MATCH_LENGTH is not set
# CONFIG_NETFILTER_XT_MATCH_LIMIT is not set
# CONFIG_NETFILTER_XT_MATCH_MAC is not set
# CONFIG_NETFILTER_XT_MATCH_MARK is not set
# CONFIG_NETFILTER_XT_MATCH_MULTIPORT is not set
# CONFIG_NETFILTER_XT_MATCH_OWNER is not set
# CONFIG_NETFILTER_XT_MATCH_POLICY is not set
# CONFIG_NETFILTER_XT_MATCH_PHYSDEV is not set
# CONFIG_NETFILTER_XT_MATCH_PKTTYPE is not set
# CONFIG_NETFILTER_XT_MATCH_QUOTA is not set
# CONFIG_NETFILTER_XT_MATCH_RATEEST is not set
# CONFIG_NETFILTER_XT_MATCH_REALM is not set
# CONFIG_NETFILTER_XT_MATCH_RECENT is not set
# CONFIG_NETFILTER_XT_MATCH_SCTP is not set
# CONFIG_NETFILTER_XT_MATCH_STATISTIC is not set
# CONFIG_NETFILTER_XT_MATCH_STRING is not set
# CONFIG_NETFILTER_XT_MATCH_TCPMSS is not set
# CONFIG_NETFILTER_XT_MATCH_TIME is not set
# CONFIG_NETFILTER_XT_MATCH_U32 is not set
# CONFIG_IP_VS is not set

#
# IP: Netfilter Configuration
#
# CONFIG_NF_DEFRAG_IPV4 is not set
CONFIG_IP_NF_QUEUE=y
# CONFIG_IP_NF_IPTABLES is not set
# CONFIG_IP_NF_ARPTABLES is not set
# CONFIG_BRIDGE_NF_EBTABLES is not set
# CONFIG_IP_DCCP is not set
# CONFIG_IP_SCTP is not set
# CONFIG_RDS is not set
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_L2TP is not set
CONFIG_STP=y
CONFIG_BRIDGE=y
CONFIG_BRIDGE_IGMP_SNOOPING=y
# CONFIG_NET_DSA is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
CONFIG_LLC=y
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_PHONET is not set
# CONFIG_IEEE802154 is not set
# CONFIG_NET_SCHED is not set
# CONFIG_DCB is not set
CONFIG_RPS=y

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_HAMRADIO is not set
# CONFIG_CAN is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_AF_RXRPC is not set
CONFIG_WIRELESS=y
# CONFIG_CFG80211 is not set
# CONFIG_LIB80211 is not set

#
# CFG80211 needs to be enabled for MAC80211
#

#
# Some wireless drivers require a rate control algorithm
#
# CONFIG_WIMAX is not set
# CONFIG_RFKILL is not set
# CONFIG_NET_9P is not set
# CONFIG_CAIF is not set

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
# CONFIG_DEVTMPFS is not set
CONFIG_STANDALONE=y
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 is not set
# CONFIG_MTD is not set
CONFIG_PARPORT=y
CONFIG_PARPORT_PC=y
# CONFIG_PARPORT_SERIAL is not set
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_GSC is not set
# CONFIG_PARPORT_AX88796 is not set
# CONFIG_PARPORT_1284 is not set
CONFIG_PNP=y
CONFIG_PNP_DEBUG_MESSAGES=y

#
# Protocols
#
# CONFIG_ISAPNP is not set
# CONFIG_PNPBIOS is not set
CONFIG_PNPACPI=y
CONFIG_BLK_DEV=y
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set

#
# DRBD disabled because PROC_FS, INET or CONNECTOR not selected
#
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_UB is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set
# CONFIG_BLK_DEV_HD is not set
CONFIG_MISC_DEVICES=y
# CONFIG_AD525X_DPOT is not set
# CONFIG_IBM_ASM is not set
# CONFIG_PHANTOM is not set
# CONFIG_SGI_IOC4 is not set
# CONFIG_TIFM_CORE is not set
# CONFIG_ICS932S401 is not set
# CONFIG_ENCLOSURE_SERVICES is not set
# CONFIG_CS5535_MFGPT is not set
# CONFIG_HP_ILO is not set
# CONFIG_ISL29003 is not set
# CONFIG_SENSORS_TSL2550 is not set
# CONFIG_DS1682 is not set
# CONFIG_VMWARE_BALLOON is not set
# CONFIG_C2PORT is not set

#
# EEPROM support
#
# CONFIG_EEPROM_AT24 is not set
# CONFIG_EEPROM_LEGACY is not set
# CONFIG_EEPROM_MAX6875 is not set
# CONFIG_EEPROM_93CX6 is not set
# CONFIG_CB710_CORE is not set
CONFIG_HAVE_IDE=y
CONFIG_IDE=y

#
# Please see Documentation/ide/ide.txt for help/info on IDE drives
#
CONFIG_IDE_XFER_MODE=y
CONFIG_IDE_TIMINGS=y
CONFIG_IDE_ATAPI=y
# CONFIG_BLK_DEV_IDE_SATA is not set
CONFIG_IDE_GD=y
CONFIG_IDE_GD_ATA=y
# CONFIG_IDE_GD_ATAPI is not set
CONFIG_BLK_DEV_IDECD=y
CONFIG_BLK_DEV_IDECD_VERBOSE_ERRORS=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEACPI is not set
# CONFIG_IDE_TASK_IOCTL is not set
CONFIG_IDE_PROC_FS=y

#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_PLATFORM is not set
CONFIG_BLK_DEV_CMD640=y
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEDMA_SFF=y

#
# PCI IDE chipsets support
#
CONFIG_BLK_DEV_IDEPCI=y
# CONFIG_IDEPCI_PCIBUS_ORDER is not set
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
CONFIG_BLK_DEV_RZ1000=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_ATIIXP is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_CS5535 is not set
# CONFIG_BLK_DEV_CS5536 is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_JMICRON is not set
# CONFIG_BLK_DEV_SC1200 is not set
CONFIG_BLK_DEV_PIIX=y
# CONFIG_BLK_DEV_IT8172 is not set
# CONFIG_BLK_DEV_IT8213 is not set
# CONFIG_BLK_DEV_IT821X is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_BLK_DEV_TC86C001 is not set

#
# Other IDE chipsets support
#

#
# Note: most of these also require special kernel boot parameters
#
# CONFIG_BLK_DEV_4DRIVES is not set
# CONFIG_BLK_DEV_ALI14XX is not set
# CONFIG_BLK_DEV_DTC2278 is not set
# CONFIG_BLK_DEV_HT6560B is not set
# CONFIG_BLK_DEV_QD65XX is not set
# CONFIG_BLK_DEV_UMC8672 is not set
CONFIG_BLK_DEV_IDEDMA=y

#
# SCSI device support
#
CONFIG_SCSI_MOD=y
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
# CONFIG_SCSI_TGT is not set
# CONFIG_SCSI_NETLINK is not set
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=y
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=y
# CONFIG_CHR_DEV_SCH is not set
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
# CONFIG_SCSI_SCAN_ASYNC is not set
CONFIG_SCSI_WAIT_SCAN=m

#
# SCSI Transports
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS is not set
# CONFIG_SCSI_SRP_ATTRS is not set
CONFIG_SCSI_LOWLEVEL=y
# CONFIG_ISCSI_TCP is not set
# CONFIG_SCSI_BNX2_ISCSI is not set
# CONFIG_BE2ISCSI is not set
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_HPSA is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_3W_SAS is not set
# CONFIG_SCSI_7000FASST is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AHA152X is not set
# CONFIG_SCSI_AHA1542 is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_AIC94XX is not set
# CONFIG_SCSI_MVSAS is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_IN2000 is not set
# CONFIG_SCSI_ARCMSR is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_MEGARAID_SAS is not set
# CONFIG_SCSI_MPT2SAS is not set
# CONFIG_SCSI_HPTIOP is not set
# CONFIG_SCSI_BUSLOGIC is not set
CONFIG_VMWARE_PVSCSI=y
# CONFIG_LIBFC is not set
# CONFIG_LIBFCOE is not set
# CONFIG_FCOE is not set
# CONFIG_FCOE_FNIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_DTC3280 is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_GENERIC_NCR5380 is not set
# CONFIG_SCSI_GENERIC_NCR5380_MMIO is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_NCR53C406A is not set
# CONFIG_SCSI_STEX is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_PAS16 is not set
# CONFIG_SCSI_QLOGIC_FAS is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_QLA_FC is not set
# CONFIG_SCSI_QLA_ISCSI is not set
# CONFIG_SCSI_LPFC is not set
# CONFIG_SCSI_SYM53C416 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_T128 is not set
# CONFIG_SCSI_U14_34F is not set
# CONFIG_SCSI_ULTRASTOR is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_SCSI_PMCRAID is not set
# CONFIG_SCSI_PM8001 is not set
# CONFIG_SCSI_SRP is not set
# CONFIG_SCSI_BFA_FC is not set
# CONFIG_SCSI_DH is not set
# CONFIG_SCSI_OSD_INITIATOR 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

#
# Controllers with non-SFF native interface
#
CONFIG_SATA_AHCI=y
CONFIG_SATA_AHCI_PLATFORM=y
# CONFIG_SATA_INIC162X is not set
# CONFIG_SATA_SIL24 is not set
CONFIG_ATA_SFF=y

#
# SFF controllers with custom DMA interface
#
# CONFIG_PDC_ADMA is not set
# CONFIG_SATA_QSTOR is not set
# CONFIG_SATA_SX4 is not set
CONFIG_ATA_BMDMA=y

#
# SATA SFF controllers with BMDMA
#
CONFIG_ATA_PIIX=y
# CONFIG_SATA_MV is not set
CONFIG_SATA_NV=y
# CONFIG_SATA_PROMISE is not set
# CONFIG_SATA_SIL is not set
# CONFIG_SATA_SIS is not set
# CONFIG_SATA_SVW is not set
# CONFIG_SATA_ULI is not set
# CONFIG_SATA_VIA is not set
# CONFIG_SATA_VITESSE is not set

#
# PATA SFF controllers with BMDMA
#
# CONFIG_PATA_ALI is not set
# CONFIG_PATA_AMD is not set
# CONFIG_PATA_ARTOP is not set
# CONFIG_PATA_ATIIXP is not set
# CONFIG_PATA_ATP867X is not set
# CONFIG_PATA_CMD64X is not set
# CONFIG_PATA_CS5520 is not set
# CONFIG_PATA_CS5530 is not set
# CONFIG_PATA_CS5535 is not set
# CONFIG_PATA_CS5536 is not set
# CONFIG_PATA_CYPRESS is not set
# CONFIG_PATA_EFAR is not set
# CONFIG_PATA_HPT366 is not set
# CONFIG_PATA_HPT37X is not set
# CONFIG_PATA_HPT3X2N is not set
# CONFIG_PATA_HPT3X3 is not set
# CONFIG_PATA_IT8213 is not set
# CONFIG_PATA_IT821X is not set
# CONFIG_PATA_JMICRON is not set
# CONFIG_PATA_MARVELL is not set
# CONFIG_PATA_NETCELL is not set
# CONFIG_PATA_NINJA32 is not set
# CONFIG_PATA_NS87415 is not set
# CONFIG_PATA_OLDPIIX is not set
# CONFIG_PATA_OPTIDMA is not set
# CONFIG_PATA_PDC2027X is not set
# CONFIG_PATA_PDC_OLD is not set
# CONFIG_PATA_RADISYS is not set
# CONFIG_PATA_RDC is not set
# CONFIG_PATA_SC1200 is not set
# CONFIG_PATA_SCH is not set
# CONFIG_PATA_SERVERWORKS is not set
# CONFIG_PATA_SIL680 is not set
# CONFIG_PATA_SIS is not set
# CONFIG_PATA_TOSHIBA is not set
# CONFIG_PATA_TRIFLEX is not set
# CONFIG_PATA_VIA is not set
# CONFIG_PATA_WINBOND is not set

#
# PIO-only SFF controllers
#
# CONFIG_PATA_CMD640_PCI is not set
# CONFIG_PATA_MPIIX is not set
# CONFIG_PATA_NS87410 is not set
# CONFIG_PATA_OPTI is not set
# CONFIG_PATA_QDI is not set
# CONFIG_PATA_RZ1000 is not set
# CONFIG_PATA_WINBOND_VLB is not set

#
# Generic fallback / legacy drivers
#
# CONFIG_PATA_ACPI is not set
# CONFIG_ATA_GENERIC is not set
# CONFIG_PATA_LEGACY is not set
# CONFIG_MD is not set
# CONFIG_FUSION is not set

#
# IEEE 1394 (FireWire) support
#

#
# You can enable one or both FireWire driver stacks.
#

#
# The newer stack is recommended.
#
# CONFIG_FIREWIRE is not set
CONFIG_IEEE1394=y
CONFIG_IEEE1394_OHCI1394=y
# CONFIG_IEEE1394_PCILYNX is not set
# CONFIG_IEEE1394_SBP2 is not set
# CONFIG_IEEE1394_ETH1394_ROM_ENTRY is not set
# CONFIG_IEEE1394_ETH1394 is not set
CONFIG_IEEE1394_RAWIO=y
# CONFIG_IEEE1394_VIDEO1394 is not set
# CONFIG_IEEE1394_DV1394 is not set
# CONFIG_IEEE1394_VERBOSEDEBUG is not set
# CONFIG_I2O is not set
# CONFIG_MACINTOSH_DRIVERS is not set
CONFIG_NETDEVICES=y
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_MACVLAN is not set
# CONFIG_EQUALIZER is not set
CONFIG_TUN=y
# CONFIG_VETH is not set
# CONFIG_NET_SB1000 is not set
# CONFIG_ARCNET is not set
# CONFIG_NET_ETHERNET is not set
CONFIG_MII=y
CONFIG_NETDEV_1000=y
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
CONFIG_E1000=y
# CONFIG_E1000E is not set
# CONFIG_IP1000 is not set
# CONFIG_IGB is not set
# CONFIG_IGBVF is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
CONFIG_R8169=y
# CONFIG_SIS190 is not set
# CONFIG_SKGE is not set
# CONFIG_SKY2 is not set
# CONFIG_VIA_VELOCITY is not set
# CONFIG_TIGON3 is not set
# CONFIG_BNX2 is not set
# CONFIG_CNIC is not set
# CONFIG_QLA3XXX is not set
# CONFIG_ATL1 is not set
# CONFIG_ATL1E is not set
# CONFIG_ATL1C is not set
# CONFIG_JME is not set
# CONFIG_NETDEV_10000 is not set
# CONFIG_TR is not set
CONFIG_WLAN=y
# CONFIG_AIRO is not set
# CONFIG_ATMEL is not set
# CONFIG_PRISM54 is not set
# CONFIG_USB_ZD1201 is not set
# CONFIG_HOSTAP is not set

#
# Enable WiMAX (Networking options) to see the WiMAX drivers
#

#
# USB Network Adapters
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set
CONFIG_USB_IPHETH=y
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
# CONFIG_NETCONSOLE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_VMXNET3 is not set
# CONFIG_ISDN is not set
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y
CONFIG_INPUT_FF_MEMLESS=y
# CONFIG_INPUT_POLLDEV is not set
# CONFIG_INPUT_SPARSEKMAP is not set

#
# 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 is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
# CONFIG_KEYBOARD_ADP5588 is not set
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_QT2160 is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_TCA6416 is not set
# CONFIG_KEYBOARD_MAX7359 is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_OPENCORES is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
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 is not set
# CONFIG_MOUSE_PS2_SENTELIC is not set
# CONFIG_MOUSE_PS2_TOUCHKIT is not set
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_APPLETOUCH is not set
# CONFIG_MOUSE_BCM5974 is not set
# CONFIG_MOUSE_INPORT is not set
# CONFIG_MOUSE_LOGIBM is not set
# CONFIG_MOUSE_PC110PAD is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_MOUSE_SYNAPTICS_I2C is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set

#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_SERIO_ALTERA_PS2 is not set
# CONFIG_GAMEPORT is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_VT_HW_CONSOLE_BINDING is not set
CONFIG_DEVKMEM=y
# CONFIG_SERIAL_NONSTANDARD is not set
# CONFIG_N_GSM is not set
# CONFIG_NOZOMI is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
# CONFIG_SERIAL_8250_CONSOLE is not set
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_PNP=y
CONFIG_SERIAL_8250_NR_UARTS=4
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
# CONFIG_SERIAL_JSM is not set
# CONFIG_SERIAL_TIMBERDALE is not set
# CONFIG_SERIAL_ALTERA_JTAGUART is not set
# CONFIG_SERIAL_ALTERA_UART is not set
CONFIG_UNIX98_PTYS=y
# CONFIG_DEVPTS_MULTIPLE_INSTANCES is not set
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
CONFIG_PRINTER=y
# CONFIG_LP_CONSOLE is not set
# CONFIG_PPDEV is not set
# CONFIG_IPMI_HANDLER is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
# CONFIG_RTC is not set
# CONFIG_GEN_RTC is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set
# CONFIG_MWAVE is not set
# CONFIG_PC8736x_GPIO is not set
# CONFIG_NSC_GPIO is not set
# CONFIG_CS5535_GPIO is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HPET is not set
# CONFIG_HANGCHECK_TIMER is not set
# CONFIG_TCG_TPM is not set
# CONFIG_TELCLOCK is not set
CONFIG_DEVPORT=y
# CONFIG_RAMOOPS is not set
CONFIG_I2C=y
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_COMPAT=y
# CONFIG_I2C_CHARDEV is not set
CONFIG_I2C_HELPER_AUTO=y
CONFIG_I2C_ALGOBIT=y

#
# I2C Hardware Bus support
#

#
# PC SMBus host controller drivers
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_I801 is not set
# CONFIG_I2C_ISCH is not set
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set

#
# ACPI drivers
#
# CONFIG_I2C_SCMI is not set

#
# I2C system bus drivers (mostly embedded / system-on-chip)
#
# CONFIG_I2C_OCORES is not set
# CONFIG_I2C_PCA_PLATFORM is not set
# CONFIG_I2C_SIMTEC is not set
# CONFIG_I2C_XILINX is not set

#
# External I2C/SMBus adapter drivers
#
# CONFIG_I2C_PARPORT is not set
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_TAOS_EVM is not set
# CONFIG_I2C_TINY_USB is not set

#
# Other I2C/SMBus bus drivers
#
# CONFIG_I2C_PCA_ISA is not set
# CONFIG_I2C_STUB is not set
# CONFIG_SCx200_ACB is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_SPI is not set

#
# PPS support
#
# CONFIG_PPS is not set
CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y
# CONFIG_GPIOLIB is not set
# CONFIG_W1 is not set
CONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not set
# CONFIG_PDA_POWER is not set
# CONFIG_TEST_POWER is not set
# CONFIG_BATTERY_DS2760 is not set
# CONFIG_BATTERY_DS2782 is not set
# CONFIG_BATTERY_BQ27x00 is not set
# CONFIG_BATTERY_MAX17040 is not set
CONFIG_HWMON=y
# CONFIG_HWMON_VID is not set
# CONFIG_HWMON_DEBUG_CHIP is not set

#
# Native drivers
#
# CONFIG_SENSORS_ABITUGURU is not set
# CONFIG_SENSORS_ABITUGURU3 is not set
# CONFIG_SENSORS_AD7414 is not set
# CONFIG_SENSORS_AD7418 is not set
# CONFIG_SENSORS_ADM1021 is not set
# CONFIG_SENSORS_ADM1025 is not set
# CONFIG_SENSORS_ADM1026 is not set
# CONFIG_SENSORS_ADM1029 is not set
# CONFIG_SENSORS_ADM1031 is not set
# CONFIG_SENSORS_ADM9240 is not set
# CONFIG_SENSORS_ADT7411 is not set
# CONFIG_SENSORS_ADT7462 is not set
# CONFIG_SENSORS_ADT7470 is not set
# CONFIG_SENSORS_ADT7475 is not set
# CONFIG_SENSORS_ASC7621 is not set
# CONFIG_SENSORS_K8TEMP is not set
# CONFIG_SENSORS_K10TEMP is not set
# CONFIG_SENSORS_ASB100 is not set
# CONFIG_SENSORS_ATXP1 is not set
# CONFIG_SENSORS_DS1621 is not set
# CONFIG_SENSORS_I5K_AMB is not set
# CONFIG_SENSORS_F71805F is not set
# CONFIG_SENSORS_F71882FG is not set
# CONFIG_SENSORS_F75375S is not set
# CONFIG_SENSORS_FSCHMD is not set
# CONFIG_SENSORS_G760A is not set
# CONFIG_SENSORS_GL518SM is not set
# CONFIG_SENSORS_GL520SM is not set
# CONFIG_SENSORS_CORETEMP is not set
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_LM63 is not set
# CONFIG_SENSORS_LM73 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM77 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM80 is not set
# CONFIG_SENSORS_LM83 is not set
# CONFIG_SENSORS_LM85 is not set
# CONFIG_SENSORS_LM87 is not set
# CONFIG_SENSORS_LM90 is not set
# CONFIG_SENSORS_LM92 is not set
# CONFIG_SENSORS_LM93 is not set
# CONFIG_SENSORS_LTC4215 is not set
# CONFIG_SENSORS_LTC4245 is not set
# CONFIG_SENSORS_LM95241 is not set
# CONFIG_SENSORS_MAX1619 is not set
# CONFIG_SENSORS_MAX6650 is not set
# CONFIG_SENSORS_PC87360 is not set
# CONFIG_SENSORS_PC87427 is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_SENSORS_SIS5595 is not set
# CONFIG_SENSORS_DME1737 is not set
# CONFIG_SENSORS_EMC1403 is not set
# CONFIG_SENSORS_SMSC47M1 is not set
# CONFIG_SENSORS_SMSC47M192 is not set
# CONFIG_SENSORS_SMSC47B397 is not set
# CONFIG_SENSORS_ADS7828 is not set
# CONFIG_SENSORS_AMC6821 is not set
# CONFIG_SENSORS_THMC50 is not set
# CONFIG_SENSORS_TMP102 is not set
# CONFIG_SENSORS_TMP401 is not set
# CONFIG_SENSORS_TMP421 is not set
# CONFIG_SENSORS_VIA_CPUTEMP is not set
# CONFIG_SENSORS_VIA686A is not set
# CONFIG_SENSORS_VT1211 is not set
# CONFIG_SENSORS_VT8231 is not set
# CONFIG_SENSORS_W83781D is not set
# CONFIG_SENSORS_W83791D is not set
# CONFIG_SENSORS_W83792D is not set
# CONFIG_SENSORS_W83793 is not set
# CONFIG_SENSORS_W83L785TS is not set
# CONFIG_SENSORS_W83L786NG is not set
# CONFIG_SENSORS_W83627HF is not set
# CONFIG_SENSORS_W83627EHF is not set
# CONFIG_SENSORS_HDAPS is not set
# CONFIG_SENSORS_LIS3_I2C is not set
# CONFIG_SENSORS_APPLESMC is not set

#
# ACPI drivers
#
# CONFIG_SENSORS_ATK0110 is not set
# CONFIG_SENSORS_LIS3LV02D is not set
CONFIG_THERMAL=y
CONFIG_THERMAL_HWMON=y
# CONFIG_WATCHDOG is not set
CONFIG_SSB_POSSIBLE=y

#
# Sonics Silicon Backplane
#
# CONFIG_SSB is not set
CONFIG_MFD_SUPPORT=y
# CONFIG_MFD_CORE is not set
# CONFIG_MFD_88PM860X is not set
# CONFIG_MFD_SM501 is not set
# CONFIG_HTC_PASIC3 is not set
# CONFIG_TPS6507X is not set
# CONFIG_TWL4030_CORE is not set
# CONFIG_MFD_TC35892 is not set
# CONFIG_MFD_TMIO is not set
# CONFIG_PMIC_DA903X is not set
# CONFIG_PMIC_ADP5520 is not set
# CONFIG_MFD_MAX8925 is not set
# CONFIG_MFD_WM8400 is not set
# CONFIG_MFD_WM831X is not set
# CONFIG_MFD_WM8350_I2C is not set
# CONFIG_MFD_WM8994 is not set
# CONFIG_MFD_PCF50633 is not set
# CONFIG_ABX500_CORE is not set
# CONFIG_LPC_SCH is not set
# CONFIG_MFD_RDC321X is not set
# CONFIG_MFD_JANZ_CMODIO is not set
# CONFIG_REGULATOR is not set
CONFIG_MEDIA_SUPPORT=y

#
# Multimedia core support
#
# CONFIG_VIDEO_DEV is not set
# CONFIG_DVB_CORE is not set
# CONFIG_VIDEO_MEDIA is not set

#
# Multimedia drivers
#
CONFIG_IR_CORE=y
CONFIG_VIDEO_IR=y
CONFIG_RC_MAP=y
CONFIG_IR_NEC_DECODER=y
# CONFIG_IR_RC5_DECODER is not set
# CONFIG_IR_RC6_DECODER is not set
# CONFIG_IR_JVC_DECODER is not set
# CONFIG_IR_SONY_DECODER is not set
# CONFIG_IR_IMON is not set
# CONFIG_DAB is not set

#
# Graphics support
#
CONFIG_AGP=y
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
# CONFIG_AGP_INTEL is not set
# CONFIG_AGP_NVIDIA is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_VIA is not set
# CONFIG_AGP_EFFICEON is not set
CONFIG_VGA_ARB=y
CONFIG_VGA_ARB_MAX_GPUS=16
# CONFIG_VGA_SWITCHEROO is not set
CONFIG_DRM=y
CONFIG_DRM_KMS_HELPER=y
CONFIG_DRM_TTM=y
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
# CONFIG_DRM_RADEON is not set
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_DRM_VIA is not set
# CONFIG_DRM_SAVAGE is not set
# CONFIG_VGASTATE is not set
CONFIG_VIDEO_OUTPUT_CONTROL=y
CONFIG_FB=y
# CONFIG_FIRMWARE_EDID is not set
# CONFIG_FB_DDC is not set
# CONFIG_FB_BOOT_VESA_SUPPORT is not set
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set
# CONFIG_FB_SYS_FILLRECT is not set
# CONFIG_FB_SYS_COPYAREA is not set
# CONFIG_FB_SYS_IMAGEBLIT is not set
# CONFIG_FB_FOREIGN_ENDIAN is not set
# CONFIG_FB_SYS_FOPS is not set
# CONFIG_FB_SVGALIB is not set
# CONFIG_FB_MACMODES is not set
CONFIG_FB_BACKLIGHT=y
# CONFIG_FB_MODE_HELPERS is not set
# CONFIG_FB_TILEBLITTING is not set

#
# Frame buffer hardware drivers
#
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ARC is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_VESA is not set
# CONFIG_FB_N411 is not set
# CONFIG_FB_HGA is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_LE80578 is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_S3 is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_VIA is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_VT8623 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_ARK is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_CARMINE is not set
# CONFIG_FB_GEODE is not set
# CONFIG_FB_VIRTUAL is not set
# CONFIG_FB_METRONOME is not set
# CONFIG_FB_MB862XX is not set
# CONFIG_FB_BROADSHEET is not set
CONFIG_BACKLIGHT_LCD_SUPPORT=y
# CONFIG_LCD_CLASS_DEVICE is not set
CONFIG_BACKLIGHT_CLASS_DEVICE=y
# CONFIG_BACKLIGHT_GENERIC is not set
# CONFIG_BACKLIGHT_PROGEAR is not set
# CONFIG_BACKLIGHT_MBP_NVIDIA is not set
# CONFIG_BACKLIGHT_SAHARA is not set
# CONFIG_BACKLIGHT_ADP8860 is not set

#
# 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_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
# CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set
# CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
# CONFIG_LOGO is not set
CONFIG_SOUND=y
CONFIG_SOUND_OSS_CORE=y
CONFIG_SOUND_OSS_CORE_PRECLAIM=y
CONFIG_SND=y
CONFIG_SND_TIMER=y
CONFIG_SND_PCM=y
CONFIG_SND_HWDEP=y
CONFIG_SND_RAWMIDI=y
CONFIG_SND_SEQUENCER=y
# CONFIG_SND_SEQ_DUMMY is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=y
CONFIG_SND_PCM_OSS=y
CONFIG_SND_PCM_OSS_PLUGINS=y
CONFIG_SND_SEQUENCER_OSS=y
# CONFIG_SND_DYNAMIC_MINORS is not set
CONFIG_SND_SUPPORT_OLD_API=y
CONFIG_SND_VERBOSE_PROCFS=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set
CONFIG_SND_DMA_SGBUF=y
CONFIG_SND_RAWMIDI_SEQ=y
# CONFIG_SND_OPL3_LIB_SEQ is not set
# CONFIG_SND_OPL4_LIB_SEQ is not set
# CONFIG_SND_SBAWE_SEQ is not set
# CONFIG_SND_EMU10K1_SEQ is not set
# CONFIG_SND_DRIVERS is not set
# CONFIG_SND_ISA is not set
# CONFIG_SND_PCI is not set
CONFIG_SND_USB=y
CONFIG_SND_USB_AUDIO=y
# CONFIG_SND_USB_UA101 is not set
# CONFIG_SND_USB_USX2Y is not set
# CONFIG_SND_USB_CAIAQ is not set
# CONFIG_SND_USB_US122L is not set
# CONFIG_SND_SOC is not set
# CONFIG_SOUND_PRIME is not set
CONFIG_HID_SUPPORT=y
CONFIG_HID=y
# CONFIG_HIDRAW is not set

#
# USB Input Devices
#
CONFIG_USB_HID=y
# CONFIG_HID_PID is not set
# CONFIG_USB_HIDDEV is not set

#
# Special HID drivers
#
# CONFIG_HID_3M_PCT is not set
CONFIG_HID_A4TECH=y
CONFIG_HID_APPLE=y
CONFIG_HID_BELKIN=y
# CONFIG_HID_CANDO is not set
CONFIG_HID_CHERRY=y
CONFIG_HID_CHICONY=y
# CONFIG_HID_PRODIKEYS is not set
CONFIG_HID_CYPRESS=y
CONFIG_HID_DRAGONRISE=y
# CONFIG_DRAGONRISE_FF is not set
# CONFIG_HID_EGALAX is not set
CONFIG_HID_EZKEY=y
CONFIG_HID_KYE=y
CONFIG_HID_GYRATION=y
CONFIG_HID_TWINHAN=y
CONFIG_HID_KENSINGTON=y
CONFIG_HID_LOGITECH=y
# CONFIG_LOGITECH_FF is not set
# CONFIG_LOGIRUMBLEPAD2_FF is not set
# CONFIG_LOGIG940_FF is not set
CONFIG_HID_MICROSOFT=y
# CONFIG_HID_MOSART is not set
CONFIG_HID_MONTEREY=y
CONFIG_HID_NTRIG=y
CONFIG_HID_ORTEK=y
CONFIG_HID_PANTHERLORD=y
# CONFIG_PANTHERLORD_FF is not set
CONFIG_HID_PETALYNX=y
# CONFIG_HID_PICOLCD is not set
# CONFIG_HID_QUANTA is not set
# CONFIG_HID_ROCCAT is not set
# CONFIG_HID_ROCCAT_KONE is not set
CONFIG_HID_SAMSUNG=y
CONFIG_HID_SONY=y
# CONFIG_HID_STANTUM is not set
CONFIG_HID_SUNPLUS=y
CONFIG_HID_GREENASIA=y
# CONFIG_GREENASIA_FF is not set
CONFIG_HID_SMARTJOYPLUS=y
# CONFIG_SMARTJOYPLUS_FF is not set
CONFIG_HID_TOPSEED=y
CONFIG_HID_THRUSTMASTER=y
CONFIG_THRUSTMASTER_FF=y
CONFIG_HID_ZEROPLUS=y
# CONFIG_ZEROPLUS_FF is not set
# CONFIG_HID_ZYDACRON is not set
CONFIG_USB_SUPPORT=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set
# CONFIG_USB_ANNOUNCE_NEW_DEVICES is not set

#
# Miscellaneous USB options
#
# CONFIG_USB_DEVICEFS is not set
CONFIG_USB_DEVICE_CLASS=y
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_MON is not set
# CONFIG_USB_WUSB is not set
# CONFIG_USB_WUSB_CBAF is not set

#
# USB Host Controller Drivers
#
# CONFIG_USB_C67X00_HCD is not set
# CONFIG_USB_XHCI_HCD is not set
CONFIG_USB_EHCI_HCD=y
# CONFIG_USB_EHCI_ROOT_HUB_TT is not set
# CONFIG_USB_EHCI_TT_NEWSCHED is not set
# CONFIG_USB_OXU210HP_HCD is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_ISP1760_HCD is not set
# CONFIG_USB_ISP1362_HCD is not set
# CONFIG_USB_OHCI_HCD is not set
CONFIG_USB_UHCI_HCD=y
# CONFIG_USB_SL811_HCD is not set
# CONFIG_USB_R8A66597_HCD is not set
# CONFIG_USB_WHCI_HCD is not set
# CONFIG_USB_HWA_HCD is not set

#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set
# CONFIG_USB_WDM is not set
# CONFIG_USB_TMC is not set

#
# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may
#

#
# also be needed; see USB_STORAGE Help for more info
#
CONFIG_USB_STORAGE=y
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_USBAT is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set
# CONFIG_USB_STORAGE_ALAUDA is not set
# CONFIG_USB_STORAGE_ONETOUCH is not set
# CONFIG_USB_STORAGE_KARMA is not set
# CONFIG_USB_STORAGE_CYPRESS_ATACB is not set
# CONFIG_USB_LIBUSUAL is not set

#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set

#
# USB port drivers
#
# CONFIG_USB_USS720 is not set
CONFIG_USB_SERIAL=y
# CONFIG_USB_SERIAL_CONSOLE is not set
# CONFIG_USB_EZUSB is not set
# CONFIG_USB_SERIAL_GENERIC is not set
# CONFIG_USB_SERIAL_AIRCABLE is not set
# CONFIG_USB_SERIAL_ARK3116 is not set
# CONFIG_USB_SERIAL_BELKIN is not set
# CONFIG_USB_SERIAL_CH341 is not set
# CONFIG_USB_SERIAL_WHITEHEAT is not set
# CONFIG_USB_SERIAL_DIGI_ACCELEPORT is not set
# CONFIG_USB_SERIAL_CP210X is not set
# CONFIG_USB_SERIAL_CYPRESS_M8 is not set
# CONFIG_USB_SERIAL_EMPEG is not set
# CONFIG_USB_SERIAL_FTDI_SIO is not set
# CONFIG_USB_SERIAL_FUNSOFT is not set
CONFIG_USB_SERIAL_VISOR=y
# CONFIG_USB_SERIAL_IPAQ is not set
# CONFIG_USB_SERIAL_IR is not set
# CONFIG_USB_SERIAL_EDGEPORT is not set
# CONFIG_USB_SERIAL_EDGEPORT_TI is not set
# CONFIG_USB_SERIAL_GARMIN is not set
# CONFIG_USB_SERIAL_IPW is not set
# CONFIG_USB_SERIAL_IUU is not set
# CONFIG_USB_SERIAL_KEYSPAN_PDA is not set
# CONFIG_USB_SERIAL_KEYSPAN is not set
# CONFIG_USB_SERIAL_KLSI is not set
# CONFIG_USB_SERIAL_KOBIL_SCT is not set
# CONFIG_USB_SERIAL_MCT_U232 is not set
# CONFIG_USB_SERIAL_MOS7720 is not set
# CONFIG_USB_SERIAL_MOS7840 is not set
# CONFIG_USB_SERIAL_MOTOROLA is not set
# CONFIG_USB_SERIAL_NAVMAN is not set
# CONFIG_USB_SERIAL_PL2303 is not set
# CONFIG_USB_SERIAL_OTI6858 is not set
# CONFIG_USB_SERIAL_QCAUX is not set
# CONFIG_USB_SERIAL_QUALCOMM is not set
# CONFIG_USB_SERIAL_SPCP8X5 is not set
# CONFIG_USB_SERIAL_HP4X is not set
# CONFIG_USB_SERIAL_SAFE is not set
# CONFIG_USB_SERIAL_SIEMENS_MPI is not set
# CONFIG_USB_SERIAL_SIERRAWIRELESS is not set
CONFIG_USB_SERIAL_SYMBOL=y
# CONFIG_USB_SERIAL_TI is not set
# CONFIG_USB_SERIAL_CYBERJACK is not set
# CONFIG_USB_SERIAL_XIRCOM is not set
# CONFIG_USB_SERIAL_OPTION is not set
# CONFIG_USB_SERIAL_OMNINET is not set
# CONFIG_USB_SERIAL_OPTICON is not set
# CONFIG_USB_SERIAL_VIVOPAY_SERIAL is not set
# CONFIG_USB_SERIAL_ZIO is not set
# CONFIG_USB_SERIAL_DEBUG is not set

#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_ADUTUX is not set
# CONFIG_USB_SEVSEG is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_FTDI_ELAN is not set
# CONFIG_USB_APPLEDISPLAY is not set
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_ISIGHTFW is not set
# CONFIG_USB_GADGET is not set

#
# OTG and related infrastructure
#
# CONFIG_NOP_USB_XCEIV is not set
# CONFIG_UWB is not set
# CONFIG_MMC is not set
# CONFIG_MEMSTICK is not set
# CONFIG_NEW_LEDS is not set
# CONFIG_ACCESSIBILITY is not set
# CONFIG_INFINIBAND is not set
# CONFIG_EDAC is not set
# CONFIG_RTC_CLASS is not set
# CONFIG_DMADEVICES is not set
# CONFIG_AUXDISPLAY is not set
# CONFIG_UIO is not set
CONFIG_STAGING=y
# CONFIG_STAGING_EXCLUDE_BUILD is not set
# CONFIG_ET131X is not set
# CONFIG_SLICOSS is not set
# CONFIG_USB_IP_COMMON is not set
# CONFIG_PRISM2_USB is not set
# CONFIG_ECHO is not set
# CONFIG_RT2860 is not set
# CONFIG_RT2870 is not set
# CONFIG_COMEDI is not set
# CONFIG_ASUS_OLED is not set
# CONFIG_PANEL is not set
# CONFIG_R8187SE is not set
# CONFIG_RTL8192SU is not set
# CONFIG_RTL8192U is not set
# CONFIG_RTL8192E is not set
# CONFIG_TRANZPORT is not set
# CONFIG_POHMELFS is not set
# CONFIG_IDE_PHISON is not set
# CONFIG_LINE6_USB is not set
# CONFIG_DRM_VMWGFX is not set
CONFIG_DRM_NOUVEAU=y
CONFIG_DRM_NOUVEAU_BACKLIGHT=y
CONFIG_DRM_NOUVEAU_DEBUG=y

#
# I2C encoder or helper chips
#
# CONFIG_DRM_I2C_CH7006 is not set
# CONFIG_USB_SERIAL_QUATECH2 is not set
# CONFIG_USB_SERIAL_QUATECH_USB2 is not set
# CONFIG_VT6655 is not set
# CONFIG_VT6656 is not set
# CONFIG_FB_UDL is not set
# CONFIG_HYPERV is not set
# CONFIG_VME_BUS is not set

#
# RAR Register Driver
#
# CONFIG_RAR_REGISTER is not set
# CONFIG_IIO is not set
# CONFIG_RAMZSWAP is not set
# CONFIG_BATMAN_ADV is not set
# CONFIG_FB_SM7XX is not set
# CONFIG_DT3155 is not set
# CONFIG_CRYSTALHD is not set

#
# Texas Instruments shared transport line discipline
#
# CONFIG_FB_XGI is not set
CONFIG_X86_PLATFORM_DEVICES=y
# CONFIG_ACERHDF is not set
# CONFIG_ASUS_LAPTOP is not set
# CONFIG_FUJITSU_LAPTOP is not set
# CONFIG_TC1100_WMI is not set
# CONFIG_PANASONIC_LAPTOP is not set
# CONFIG_THINKPAD_ACPI is not set
# CONFIG_INTEL_MENLOW is not set
# CONFIG_ACPI_WMI is not set
# CONFIG_ACPI_ASUS is not set
# CONFIG_TOPSTAR_LAPTOP is not set
# CONFIG_ACPI_TOSHIBA is not set
# CONFIG_TOSHIBA_BT_RFKILL is not set
# CONFIG_ACPI_CMPC is not set

#
# Firmware Drivers
#
# CONFIG_EDD is not set
CONFIG_FIRMWARE_MEMMAP=y
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not set
CONFIG_DMIID=y
# CONFIG_ISCSI_IBFT_FIND is not set

#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
# CONFIG_EXT2_FS_XIP is not set
# CONFIG_EXT3_FS is not set
# CONFIG_EXT4_FS is not set
# CONFIG_REISERFS_FS is not set
CONFIG_JFS_FS=y
CONFIG_JFS_POSIX_ACL=y
CONFIG_JFS_SECURITY=y
CONFIG_JFS_DEBUG=y
CONFIG_JFS_STATISTICS=y
CONFIG_FS_POSIX_ACL=y
# CONFIG_XFS_FS is not set
# CONFIG_OCFS2_FS is not set
# CONFIG_BTRFS_FS is not set
# CONFIG_NILFS2_FS is not set
CONFIG_FILE_LOCKING=y
CONFIG_FSNOTIFY=y
CONFIG_DNOTIFY=y
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=y
# CONFIG_FUSE_FS is not set

#
# Caches
#
CONFIG_FSCACHE=y
CONFIG_FSCACHE_STATS=y
CONFIG_FSCACHE_HISTOGRAM=y
CONFIG_FSCACHE_DEBUG=y
# CONFIG_FSCACHE_OBJECT_LIST is not set
CONFIG_CACHEFILES=y
CONFIG_CACHEFILES_DEBUG=y
CONFIG_CACHEFILES_HISTOGRAM=y

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
CONFIG_UDF_FS=y
CONFIG_UDF_NLS=y

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
CONFIG_NTFS_FS=y
CONFIG_NTFS_DEBUG=y
CONFIG_NTFS_RW=y

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
# CONFIG_TMPFS_POSIX_ACL is not set
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_CONFIGFS_FS=y
CONFIG_MISC_FILESYSTEMS=y
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_LOGFS is not set
# CONFIG_CRAMFS is not set
# CONFIG_SQUASHFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_OMFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=y
# CONFIG_NFS_V3 is not set
# CONFIG_NFS_V4 is not set
# CONFIG_NFS_FSCACHE is not set
CONFIG_NFSD=y
# CONFIG_NFSD_V3 is not set
# CONFIG_NFSD_V4 is not set
CONFIG_LOCKD=y
CONFIG_EXPORTFS=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
# CONFIG_RPCSEC_GSS_KRB5 is not set
# CONFIG_RPCSEC_GSS_SPKM3 is not set
CONFIG_SMB_FS=y
CONFIG_SMB_NLS_DEFAULT=y
CONFIG_SMB_NLS_REMOTE="cp437"
# CONFIG_CEPH_FS is not set
CONFIG_CIFS=y
CONFIG_CIFS_STATS=y
CONFIG_CIFS_STATS2=y
# CONFIG_CIFS_WEAK_PW_HASH is not set
CONFIG_CIFS_XATTR=y
CONFIG_CIFS_POSIX=y
# CONFIG_CIFS_DEBUG2 is not set
# CONFIG_CIFS_EXPERIMENTAL is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ASCII is not set
CONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_UTF8 is not set
# CONFIG_DLM is not set

#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
# CONFIG_PRINTK_TIME is not set
# CONFIG_ENABLE_WARN_DEPRECATED is not set
# CONFIG_ENABLE_MUST_CHECK is not set
CONFIG_FRAME_WARN=1024
# CONFIG_MAGIC_SYSRQ is not set
# 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 is not set
CONFIG_TIMER_STATS=y
# CONFIG_DEBUG_OBJECTS is not set
# CONFIG_DEBUG_SLAB is not set
CONFIG_DEBUG_KMEMLEAK=y
CONFIG_DEBUG_KMEMLEAK_EARLY_LOG_SIZE=400
# CONFIG_DEBUG_KMEMLEAK_TEST 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_HIGHMEM is not set
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_INFO is not set
# 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_LKDTM is not set
# CONFIG_CPU_NOTIFIER_ERROR_INJECT is not set
# CONFIG_FAULT_INJECTION is not set
# CONFIG_LATENCYTOP is not set
CONFIG_SYSCTL_SYSCALL_CHECK=y
# CONFIG_DEBUG_PAGEALLOC is not set
CONFIG_USER_STACKTRACE_SUPPORT=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_RING_BUFFER_ALLOW_SWAP=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_ENABLE_DEFAULT_TRACERS 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_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 is not set
# CONFIG_MMIOTRACE is not set
# CONFIG_RING_BUFFER_BENCHMARK is not set
# CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set
# CONFIG_DYNAMIC_DEBUG is not set
# CONFIG_DMA_API_DEBUG is not set
# CONFIG_ATOMIC64_SELFTEST is not set
# CONFIG_SAMPLES is not set
CONFIG_HAVE_ARCH_KGDB=y
# CONFIG_KGDB is not set
CONFIG_HAVE_ARCH_KMEMCHECK=y
# CONFIG_KMEMCHECK is not set
# CONFIG_STRICT_DEVMEM is not set
CONFIG_X86_VERBOSE_BOOTUP=y
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 is not set
# CONFIG_DEBUG_NX_TEST is not set
# CONFIG_4KSTACKS is not set
CONFIG_DOUBLEFAULT=y
# 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 is not set
# CONFIG_DEBUG_STRICT_USER_COPY_CHECKS is not set

#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set
# CONFIG_SECURITYFS is not set
# CONFIG_DEFAULT_SECURITY_SELINUX is not set
# CONFIG_DEFAULT_SECURITY_SMACK is not set
# CONFIG_DEFAULT_SECURITY_TOMOYO is not set
CONFIG_DEFAULT_SECURITY_DAC=y
CONFIG_DEFAULT_SECURITY=""
CONFIG_CRYPTO=y

#
# Crypto core or helper
#
# CONFIG_CRYPTO_MANAGER is not set
# CONFIG_CRYPTO_MANAGER2 is not set
# CONFIG_CRYPTO_GF128MUL is not set
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_PCRYPT is not set
# CONFIG_CRYPTO_CRYPTD is not set
# CONFIG_CRYPTO_AUTHENC is not set
# CONFIG_CRYPTO_TEST is not set

#
# Authenticated Encryption with Associated Data
#
# CONFIG_CRYPTO_CCM is not set
# CONFIG_CRYPTO_GCM is not set
# CONFIG_CRYPTO_SEQIV is not set

#
# Block modes
#
# CONFIG_CRYPTO_CBC is not set
# CONFIG_CRYPTO_CTR is not set
# CONFIG_CRYPTO_CTS is not set
# CONFIG_CRYPTO_ECB is not set
# CONFIG_CRYPTO_LRW is not set
# CONFIG_CRYPTO_PCBC is not set
# CONFIG_CRYPTO_XTS is not set

#
# Hash modes
#
# CONFIG_CRYPTO_HMAC is not set
# CONFIG_CRYPTO_XCBC is not set
# CONFIG_CRYPTO_VMAC is not set

#
# Digest
#
# CONFIG_CRYPTO_CRC32C is not set
# CONFIG_CRYPTO_CRC32C_INTEL is not set
# CONFIG_CRYPTO_GHASH is not set
# CONFIG_CRYPTO_MD4 is not set
# CONFIG_CRYPTO_MD5 is not set
# CONFIG_CRYPTO_MICHAEL_MIC is not set
# CONFIG_CRYPTO_RMD128 is not set
# CONFIG_CRYPTO_RMD160 is not set
# CONFIG_CRYPTO_RMD256 is not set
# CONFIG_CRYPTO_RMD320 is not set
# CONFIG_CRYPTO_SHA1 is not set
# CONFIG_CRYPTO_SHA256 is not set
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_TGR192 is not set
# CONFIG_CRYPTO_WP512 is not set

#
# Ciphers
#
# CONFIG_CRYPTO_AES is not set
# CONFIG_CRYPTO_AES_586 is not set
# CONFIG_CRYPTO_ANUBIS is not set
# CONFIG_CRYPTO_ARC4 is not set
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_CAMELLIA is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
# CONFIG_CRYPTO_DES is not set
# CONFIG_CRYPTO_FCRYPT is not set
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_SALSA20 is not set
# CONFIG_CRYPTO_SALSA20_586 is not set
# CONFIG_CRYPTO_SEED is not set
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_TEA is not set
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_TWOFISH_586 is not set

#
# Compression
#
# CONFIG_CRYPTO_DEFLATE is not set
# CONFIG_CRYPTO_ZLIB is not set
# CONFIG_CRYPTO_LZO is not set

#
# Random Number Generation
#
# CONFIG_CRYPTO_ANSI_CPRNG is not set
CONFIG_CRYPTO_HW=y
# CONFIG_CRYPTO_DEV_PADLOCK is not set
# CONFIG_CRYPTO_DEV_GEODE is not set
# CONFIG_CRYPTO_DEV_HIFN_795X is not set
CONFIG_HAVE_KVM=y
CONFIG_HAVE_KVM_IRQCHIP=y
CONFIG_HAVE_KVM_EVENTFD=y
CONFIG_KVM_APIC_ARCHITECTURE=y
CONFIG_KVM_MMIO=y
CONFIG_VIRTUALIZATION=y
CONFIG_KVM=y
CONFIG_KVM_INTEL=y
# CONFIG_KVM_AMD is not set
# CONFIG_VHOST_NET is not set
# CONFIG_LGUEST is not set
# CONFIG_VIRTIO_PCI is not set
# CONFIG_VIRTIO_BALLOON is not set
# CONFIG_BINARY_PRINTF is not set

#
# 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 is not set
# CONFIG_CRC16 is not set
CONFIG_CRC_T10DIF=y
CONFIG_CRC_ITU_T=y
CONFIG_CRC32=y
# CONFIG_CRC7 is not set
# CONFIG_LIBCRC32C is not set
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y
CONFIG_NLATTR=y

[-- Attachment #3: dmesg --]
[-- Type: application/octet-stream, Size: 15472 bytes --]

-0xfed8ffff]
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
UDP hash table entries: 512 (order: 2, 16384 bytes)
UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
pci 0000:05:00.0: Boot video device
PCI: CLS 256 bytes, default 64
highmem bounce pool size: 64 pages
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
NTFS driver 2.1.29 [Flags: R/W DEBUG].
JFS: nTxBlock = 8192, nTxLock = 65536
msgmni has been set to 1560
io scheduler noop registered (default)
io scheduler deadline registered
io scheduler cfq registered
intel_idle: MWAIT substates: 0x1120
intel_idle: v0.4 model 0x1A
intel_idle: lapic_timer_reliable_states 0x2
input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
ACPI: Power Button [PWRB]
input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
ACPI: Power Button [PWRF]
ACPI: acpi_idle yielding to intel_idle
lp: driver loaded but no devices found
Linux agpgart interface v0.103
[drm] Initialized drm 1.1.0 20060810
nouveau 0000:05:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
nouveau 0000:05:00.0: setting latency timer to 64
[drm] nouveau 0000:05:00.0: Detected an NV50 generation card (0x298200a2)
[drm] nouveau 0000:05:00.0: Attempting to load BIOS image from ACPI
[drm] nouveau 0000:05:00.0: ... BIOS signature not found
[drm] nouveau 0000:05:00.0: Attempting to load BIOS image from PRAMIN
[drm] nouveau 0000:05:00.0: ... appears to be valid
[drm] nouveau 0000:05:00.0: BIT BIOS found
[drm] nouveau 0000:05:00.0: Bios version 62.98.29.00
[drm] nouveau 0000:05:00.0: TMDS table revision 2.0 not currently supported
[drm] nouveau 0000:05:00.0: Found Display Configuration Block version 4.0
[drm] nouveau 0000:05:00.0: Raw DCB entry 0: 02000300 00000028
[drm] nouveau 0000:05:00.0: Raw DCB entry 1: 01000302 00000030
[drm] nouveau 0000:05:00.0: Raw DCB entry 2: 04011310 00000028
[drm] nouveau 0000:05:00.0: DCB connector table: VHER 0x40 5 16 4
[drm] nouveau 0000:05:00.0:   0: 0x00001030: type 0x30 idx 0 tag 0x07
[drm] nouveau 0000:05:00.0:   1: 0x00000100: type 0x00 idx 1 tag 0xff
[drm] nouveau 0000:05:00.0: Parsing VBIOS init table 0 at offset 0xD40E
[drm] nouveau 0000:05:00.0: Parsing VBIOS init table 1 at offset 0xD785
[drm] nouveau 0000:05:00.0: Parsing VBIOS init table 2 at offset 0xE02B
[drm] nouveau 0000:05:00.0: Parsing VBIOS init table 3 at offset 0xE11D
[drm] nouveau 0000:05:00.0: Parsing VBIOS init table 4 at offset 0xE2F9
[drm] nouveau 0000:05:00.0: Parsing VBIOS init table at offset 0xE35E
[drm] nouveau 0000:05:00.0: 0xE35E: Condition still not met after 20ms, skipping following opcodes
[drm] nouveau 0000:05:00.0: 0xC3D8: parsing output script 0
[drm] nouveau 0000:05:00.0: Detected 512MiB VRAM
[TTM] Zone  kernel: Available graphics memory: 399474 kiB.
[TTM] Zone highmem: Available graphics memory: 6233462 kiB.
[TTM] Initializing pool allocator.
Switched to NOHz mode on CPU #0
Switched to NOHz mode on CPU #6
Switched to NOHz mode on CPU #7
Switched to NOHz mode on CPU #2
Switched to NOHz mode on CPU #4
Switched to NOHz mode on CPU #3
Switched to NOHz mode on CPU #5
Switched to NOHz mode on CPU #1
[drm] nouveau 0000:05:00.0: 512 MiB GART (aperture)
mtrr: type mismatch for d0000000,10000000 old: write-back new: write-combining
[drm] nouveau 0000:05:00.0: Allocating FIFO number 1
[drm] nouveau 0000:05:00.0: nouveau_channel_alloc: initialised FIFO 1
[drm] nouveau 0000:05:00.0: Detected a DAC output
[drm] nouveau 0000:05:00.0: Detected a TMDS output
[drm] nouveau 0000:05:00.0: Detected a DAC output
[drm] nouveau 0000:05:00.0: Detected a DVI-I connector
[drm] nouveau 0000:05:00.0: Detected a VGA connector
[drm] nouveau 0000:05:00.0: allocated 1280x1024 fb: 0x40250000, bo f652ce00
[drm] nouveau 0000:05:00.0: 0xC3F6: parsing output script 1
[drm] nouveau 0000:05:00.0: 0xC3F7: parsing output script 2
[drm] nouveau 0000:05:00.0: 0xC0E6: parsing clock script 0
[drm] nouveau 0000:05:00.0: 0xBA22: parsing clock script 1
Console: switching to colour frame buffer device 160x64
fb0: nouveaufb frame buffer device
drm: registered panic notifier
[drm] Initialized nouveau 0.0.16 20090420 for 0000:05:00.0 on minor 0
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
00:0b: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Floppy drive(s): fd0 is 1.44M
floppy0: no floppy controllers found
loop: module loaded
Uniform Multi-Platform E-IDE driver
ide_generic: please use "probe_mask=0x3f" module parameter for probing all legacy ISA IDE ports
Probing IDE interface ide0...
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
ide1 at 0x170-0x177,0x376 on irq 15
ide-gd driver 1.18
ide-cd driver 5.00
VMware PVSCSI driver - version 1.0.1.0-k
ahci 0000:03:00.0: version 3.0
ahci 0000:03:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
ahci 0000:03:00.0: AHCI 0001.0000 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
ahci 0000:03:00.0: flags: 64bit ncq pm led clo pmp pio slum part 
ahci 0000:03:00.0: setting latency timer to 64
scsi0 : ahci
ata1: SATA max UDMA/133 abar m8192@0xf7ffe000 port 0xf7ffe100 irq 16
ata_piix 0000:00:1f.2: version 2.13
ata_piix 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
ata_piix 0000:00:1f.2: setting latency timer to 64
scsi1 : ata_piix
scsi2 : ata_piix
ata2: SATA max UDMA/133 cmd 0x9c00 ctl 0x9880 bmdma 0x9400 irq 19
ata3: SATA max UDMA/133 cmd 0x9800 ctl 0x9480 bmdma 0x9408 irq 19
ata_piix 0000:00:1f.5: PCI INT B -> GSI 19 (level, low) -> IRQ 19
ata_piix 0000:00:1f.5: MAP [ P0 -- P1 -- ]
ata_piix 0000:00:1f.5: setting latency timer to 64
scsi3 : ata_piix
scsi4 : ata_piix
ata4: SATA max UDMA/133 cmd 0xac00 ctl 0xa880 bmdma 0xa400 irq 19
ata5: SATA max UDMA/133 cmd 0xa800 ctl 0xa480 bmdma 0xa408 irq 19
e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k6-NAPI
e1000: Copyright (c) 1999-2006 Intel Corporation.
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
r8169 0000:01:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
r8169 0000:01:00.0: setting latency timer to 64
r8169 0000:01:00.0: no MSI. Back to INTx.
r8169 0000:01:00.0: eth0: RTL8168d/8111d at 0xf8b36000, 00:25:22:2f:bb:2d, XID 081000c0 IRQ 17
usbcore: registered new interface driver ipheth
ohci1394 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
ohci1394 0000:02:00.0: setting latency timer to 64
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[17]  MMIO=[f7eef800-f7eeffff]  Max Packet=[2048]  IR/IT contexts=[4/8]
ieee1394: raw1394: /dev/raw1394 device initialized
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 18 (level, low) -> IRQ 18
ehci_hcd 0000:00:1a.7: setting latency timer to 64
ehci_hcd 0000:00:1a.7: EHCI Host Controller
ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1a.7: debug port 1
ehci_hcd 0000:00:1a.7: cache line size of 256 is not supported
ehci_hcd 0000:00:1a.7: irq 18, io mem 0xf7cf6000
ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 6 ports detected
ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23
ehci_hcd 0000:00:1d.7: setting latency timer to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2
ehci_hcd 0000:00:1d.7: debug port 1
ehci_hcd 0000:00:1d.7: cache line size of 256 is not supported
ehci_hcd 0000:00:1d.7: irq 23, io mem 0xf7cfc000
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 6 ports detected
uhci_hcd: USB Universal Host Controller Interface driver
uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
uhci_hcd 0000:00:1a.0: setting latency timer to 64
uhci_hcd 0000:00:1a.0: UHCI Host Controller
uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1a.0: irq 16, io base 0x00008400
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21
uhci_hcd 0000:00:1a.1: setting latency timer to 64
uhci_hcd 0000:00:1a.1: UHCI Host Controller
uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1a.1: irq 21, io base 0x00008480
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
uhci_hcd 0000:00:1a.2: PCI INT D -> GSI 19 (level, low) -> IRQ 19
uhci_hcd 0000:00:1a.2: setting latency timer to 64
uhci_hcd 0000:00:1a.2: UHCI Host Controller
uhci_hcd 0000:00:1a.2: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:1a.2: irq 19, io base 0x00008800
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
uhci_hcd 0000:00:1d.0: setting latency timer to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 6
uhci_hcd 0000:00:1d.0: irq 23, io base 0x00008880
hub 6-0:1.0: USB hub found
hub 6-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
uhci_hcd 0000:00:1d.1: setting latency timer to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 7
uhci_hcd 0000:00:1d.1: irq 19, io base 0x00008c00
hub 7-0:1.0: USB hub found
hub 7-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
uhci_hcd 0000:00:1d.2: setting latency timer to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 8
uhci_hcd 0000:00:1d.2: irq 18, io base 0x00009000
hub 8-0:1.0: USB hub found
hub 8-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbserial
usbserial: USB Serial Driver core
USB Serial support registered for symbol
usbcore: registered new interface driver symbol
USB Serial support registered for Handspring Visor / Palm OS
USB Serial support registered for Sony Clie 3.5
USB Serial support registered for Sony Clie 5.0
usbcore: registered new interface driver visor
visor: USB HandSpring Visor / Palm OS driver
PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
IR NEC protocol handler initialized
cpuidle: using governor ladder
cpuidle: using governor menu
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
usbcore: registered new interface driver snd-usb-audio
ALSA device list:
  No soundcards found.
oprofile: using NMI interrupt.
TCP cubic registered
NET: Registered protocol family 17
Bridge firewalling registered
Using IPI No-Shortcut mode
kmemleak: Kernel memory leak detector initialized
kmemleak: Automatic memory scanning thread started
ata1: SATA link down (SStatus 0 SControl 300)
ata2.00: link resume succeeded after 1 retries
ata4: link resume succeeded after 1 retries
ata5: link resume succeeded after 1 retries
ata4: SATA link down (SStatus 0 SControl 300)
ata5: SATA link down (SStatus 0 SControl 300)
ata3.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3.01: SATA link down (SStatus 0 SControl 300)
ata3.00: ATA-7: INTEL SSDSA2MH160G1GC, 045C8820, max UDMA/133
ata3.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 0/31)
ata3.00: configured for UDMA/133
usb 3-2: new low speed USB device using uhci_hcd and address 2
ata2.01: link resume succeeded after 1 retries
input: Logitech USB Mouse as /devices/pci0000:00/0000:00:1a.0/usb3/3-2/3-2:1.0/input/input2
generic-usb 0003:046D:C00C.0001: input: USB HID v1.10 Mouse [Logitech USB Mouse] on usb-0000:00:1a.0-2/input0
ata2.00: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.01: SATA link down (SStatus 0 SControl 300)
ata2.01: link offline, clearing class 3 to NONE
ata2.00: ATAPI: Optiarc DVD RW AD-7240S, 1.03, max UDMA/100
ata2.00: configured for UDMA/100
scsi 1:0:0:0: CD-ROM            Optiarc  DVD RW AD-7240S  1.03 PQ: 0 ANSI: 5
sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 1:0:0:0: Attached scsi CD-ROM sr0
sr 1:0:0:0: Attached scsi generic sg0 type 5
scsi 2:0:0:0: Direct-Access     ATA      INTEL SSDSA2MH16 045C PQ: 0 ANSI: 5
sd 2:0:0:0: [sda] 312581808 512-byte logical blocks: (160 GB/149 GiB)
sd 2:0:0:0: Attached scsi generic sg1 type 0
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1 sda2 sda3
sd 2:0:0:0: [sda] Attached SCSI disk
UDF-fs: No partition found (1)
VFS: Mounted root (jfs filesystem) readonly on device 8:3.
Freeing unused kernel memory: 424k freed
usb 8-1: new full speed USB device using uhci_hcd and address 2
ieee1394: Host added: ID:BUS[0-00:1023]  GUID[008f13007f940800]
udev: starting version 146
input: Logitech Logitech USB Headset as /devices/pci0000:00/0000:00:1d.2/usb8/8-1/8-1:1.3/input/input3
generic-usb 0003:046D:0A01.0002: input: USB HID v1.00 Device [Logitech Logitech USB Headset] on usb-0000:00:1d.2-1/input3
udev: renamed network interface eth0 to eth2
usb 8-2: new full speed USB device using uhci_hcd and address 3
hub 8-2:1.0: USB hub found
hub 8-2:1.0: 4 ports detected
usb 8-2.2: new full speed USB device using uhci_hcd and address 4
input: HID 05f3:0007 as /devices/pci0000:00/0000:00:1d.2/usb8/8-2/8-2.2/8-2.2:1.0/input/input4
generic-usb 0003:05F3:0007.0003: input: USB HID v1.00 Keyboard [HID 05f3:0007] on usb-0000:00:1d.2-2.2/input0
input: HID 05f3:0007 as /devices/pci0000:00/0000:00:1d.2/usb8/8-2/8-2.2/8-2.2:1.1/input/input5
generic-usb 0003:05F3:0007.0004: input: USB HID v1.00 Device [HID 05f3:0007] on usb-0000:00:1d.2-2.2/input1
Adding 192776k swap on /dev/sda2.  Priority:-1 extents:1 across:192776k SS
r8169 0000:01:00.0: eth2: link down
r8169 0000:01:00.0: eth2: link down
[drm] nouveau 0000:05:00.0: Allocating FIFO number 2
[drm] nouveau 0000:05:00.0: nouveau_channel_alloc: initialised FIFO 2
r8169 0000:01:00.0: eth2: link up
kmemleak: 38 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
kmemleak: 2 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
kmemleak: 1 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
kmemleak: 2 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
kmemleak: 2 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
kmemleak: 1 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
usb 1-3: new high speed USB device using ehci_hcd and address 3
scsi5 : usb-storage 1-3:1.0
scsi 5:0:0:0: Direct-Access     Kindle   Internal Storage 0100 PQ: 0 ANSI: 2
sd 5:0:0:0: Attached scsi generic sg2 type 0
sd 5:0:0:0: [sdb] Attached SCSI removable disk
process `skype' is using obsolete setsockopt SO_BSDCOMPAT
timeout: still 8 active urbs..

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-14  8:27   ` Zeno Davatz
@ 2010-07-14  9:47     ` Catalin Marinas
  2010-07-14  9:55       ` Pekka Enberg
  0 siblings, 1 reply; 44+ messages in thread
From: Catalin Marinas @ 2010-07-14  9:47 UTC (permalink / raw)
  To: Zeno Davatz; +Cc: Pekka Enberg, linux-kernel, Andrew Morton

On Wed, 2010-07-14 at 09:27 +0100, Zeno Davatz wrote:
> On Wed, Jul 14, 2010 at 10:05 AM, Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> > On Wed, Jul 14, 2010 at 9:12 AM, Zeno Davatz <zdavatz@gmail.com> wrote:

> >> I am attaching you the file from /sys/kernel/debug/kmemleak
> >
> > Zeno, can you post your dmesg and .config, please?
> 
> Sure, see attached files.

It looks like NO_BOOTMEM is enabled. You can try the attached patch (I
need to post it again on the list).


kmemleak: Add support for NO_BOOTMEM configurations

From: Catalin Marinas <catalin.marinas@arm.com>

With commits 08677214 and 59be5a8e, alloc_bootmem()/free_bootmem() and
friends use the early_res functions for memory management when
NO_BOOTMEM is enabled. This patch adds the kmemleak calls in the
corresponding code paths for bootmem allocations.

Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Cc: Yinghai Lu <yinghai@kernel.org>
Cc: H. Peter Anvin <hpa@zytor.com>
---
 mm/bootmem.c    |    2 ++
 mm/page_alloc.c |    1 +
 2 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/mm/bootmem.c b/mm/bootmem.c
index 58c66cc..0747f68 100644
--- a/mm/bootmem.c
+++ b/mm/bootmem.c
@@ -435,6 +435,7 @@ void __init free_bootmem_node(pg_data_t *pgdat, unsigned long physaddr,
 {
 #ifdef CONFIG_NO_BOOTMEM
 	free_early(physaddr, physaddr + size);
+	kmemleak_free_part(__va(physaddr), size);
 #else
 	unsigned long start, end;
 
@@ -460,6 +461,7 @@ void __init free_bootmem(unsigned long addr, unsigned long size)
 {
 #ifdef CONFIG_NO_BOOTMEM
 	free_early(addr, addr + size);
+	kmemleak_free_part(__va(addr), size);
 #else
 	unsigned long start, end;
 
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index 431214b..f29f00b 100644
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -3659,6 +3659,7 @@ void * __init __alloc_memory_core_early(int nid, u64 size, u64 align,
 		ptr = phys_to_virt(addr);
 		memset(ptr, 0, size);
 		reserve_early_without_check(addr, addr + size, "BOOTMEM");
+		kmemleak_alloc(ptr, size, 1, 0);
 		return ptr;
 	}
 


-- 
Catalin


^ permalink raw reply related	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-14  9:47     ` Catalin Marinas
@ 2010-07-14  9:55       ` Pekka Enberg
  2010-07-14 10:00         ` Zeno Davatz
  2010-07-15 14:58         ` Catalin Marinas
  0 siblings, 2 replies; 44+ messages in thread
From: Pekka Enberg @ 2010-07-14  9:55 UTC (permalink / raw)
  To: Catalin Marinas; +Cc: Zeno Davatz, linux-kernel, Andrew Morton

Catalin Marinas wrote:
> On Wed, 2010-07-14 at 09:27 +0100, Zeno Davatz wrote:
>> On Wed, Jul 14, 2010 at 10:05 AM, Pekka Enberg <penberg@cs.helsinki.fi> wrote:
>>> On Wed, Jul 14, 2010 at 9:12 AM, Zeno Davatz <zdavatz@gmail.com> wrote:
> 
>>>> I am attaching you the file from /sys/kernel/debug/kmemleak
>>> Zeno, can you post your dmesg and .config, please?
>> Sure, see attached files.
> 
> It looks like NO_BOOTMEM is enabled. You can try the attached patch (I
> need to post it again on the list).
> 
> 
> kmemleak: Add support for NO_BOOTMEM configurations
> 
> From: Catalin Marinas <catalin.marinas@arm.com>
> 
> With commits 08677214 and 59be5a8e, alloc_bootmem()/free_bootmem() and
> friends use the early_res functions for memory management when
> NO_BOOTMEM is enabled. This patch adds the kmemleak calls in the
> corresponding code paths for bootmem allocations.
> 
> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Yinghai Lu <yinghai@kernel.org>
> Cc: H. Peter Anvin <hpa@zytor.com>

Makes sense.

Acked-by: Pekka Enberg <penberg@cs.helsinki.fi>

Zeno, this should fix the kmemleak false positives but not the big 
pauses you're seeing.

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-14  9:55       ` Pekka Enberg
@ 2010-07-14 10:00         ` Zeno Davatz
  2010-07-15 14:58         ` Catalin Marinas
  1 sibling, 0 replies; 44+ messages in thread
From: Zeno Davatz @ 2010-07-14 10:00 UTC (permalink / raw)
  To: Pekka Enberg; +Cc: Catalin Marinas, linux-kernel, Andrew Morton

On Wed, Jul 14, 2010 at 11:55 AM, Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> Catalin Marinas wrote:
>>
>> On Wed, 2010-07-14 at 09:27 +0100, Zeno Davatz wrote:
>>>
>>> On Wed, Jul 14, 2010 at 10:05 AM, Pekka Enberg <penberg@cs.helsinki.fi>
>>> wrote:
>>>>
>>>> On Wed, Jul 14, 2010 at 9:12 AM, Zeno Davatz <zdavatz@gmail.com> wrote:
>>
>>>>> I am attaching you the file from /sys/kernel/debug/kmemleak
>>>>
>>>> Zeno, can you post your dmesg and .config, please?
>>>
>>> Sure, see attached files.
>>
>> It looks like NO_BOOTMEM is enabled. You can try the attached patch (I
>> need to post it again on the list).
>>
>>
>> kmemleak: Add support for NO_BOOTMEM configurations
>>
>> From: Catalin Marinas <catalin.marinas@arm.com>
>>
>> With commits 08677214 and 59be5a8e, alloc_bootmem()/free_bootmem() and
>> friends use the early_res functions for memory management when
>> NO_BOOTMEM is enabled. This patch adds the kmemleak calls in the
>> corresponding code paths for bootmem allocations.
>>
>> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
>> Cc: Yinghai Lu <yinghai@kernel.org>
>> Cc: H. Peter Anvin <hpa@zytor.com>
>
> Makes sense.
>
> Acked-by: Pekka Enberg <penberg@cs.helsinki.fi>
>
> Zeno, this should fix the kmemleak false positives but not the big pauses
> you're seeing.

Thank for this detailed info Pekka! I will not apply the patch at the
moment. Will it be in with the next RC from Linus? Or do you recommend
I apply it?

What I want it is to tame the temper of Tux and restrict him from
eating my CPU-donuts (cores) at random. I need them for other
processes. ;)

Best
Zeno

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-14  9:55       ` Pekka Enberg
  2010-07-14 10:00         ` Zeno Davatz
@ 2010-07-15 14:58         ` Catalin Marinas
  2010-07-15 15:15           ` Zeno Davatz
  1 sibling, 1 reply; 44+ messages in thread
From: Catalin Marinas @ 2010-07-15 14:58 UTC (permalink / raw)
  To: Pekka Enberg; +Cc: Zeno Davatz, linux-kernel, Andrew Morton

On Wed, 2010-07-14 at 10:55 +0100, Pekka Enberg wrote:
> Catalin Marinas wrote:
> > On Wed, 2010-07-14 at 09:27 +0100, Zeno Davatz wrote:
> >> On Wed, Jul 14, 2010 at 10:05 AM, Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> >>> On Wed, Jul 14, 2010 at 9:12 AM, Zeno Davatz <zdavatz@gmail.com> wrote:
> >
> >>>> I am attaching you the file from /sys/kernel/debug/kmemleak
> >>> Zeno, can you post your dmesg and .config, please?
> >> Sure, see attached files.
> >
> > It looks like NO_BOOTMEM is enabled. You can try the attached patch (I
> > need to post it again on the list).
> >
> >
> > kmemleak: Add support for NO_BOOTMEM configurations
> >
> > From: Catalin Marinas <catalin.marinas@arm.com>
> >
> > With commits 08677214 and 59be5a8e, alloc_bootmem()/free_bootmem() and
> > friends use the early_res functions for memory management when
> > NO_BOOTMEM is enabled. This patch adds the kmemleak calls in the
> > corresponding code paths for bootmem allocations.
> >
> > Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
> > Cc: Yinghai Lu <yinghai@kernel.org>
> > Cc: H. Peter Anvin <hpa@zytor.com>
> 
> Makes sense.
> 
> Acked-by: Pekka Enberg <penberg@cs.helsinki.fi>

I'll post an updated patch since I missed a callback. I've been testing
it since yesterday and seems ok.

Thanks.

-- 
Catalin


^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-15 14:58         ` Catalin Marinas
@ 2010-07-15 15:15           ` Zeno Davatz
  2010-07-15 15:54             ` Pekka Enberg
  0 siblings, 1 reply; 44+ messages in thread
From: Zeno Davatz @ 2010-07-15 15:15 UTC (permalink / raw)
  To: Catalin Marinas; +Cc: Pekka Enberg, linux-kernel, Andrew Morton

Dear Catalin

On Thu, Jul 15, 2010 at 4:58 PM, Catalin Marinas
<catalin.marinas@arm.com> wrote:
> On Wed, 2010-07-14 at 10:55 +0100, Pekka Enberg wrote:
>> Catalin Marinas wrote:
>> > On Wed, 2010-07-14 at 09:27 +0100, Zeno Davatz wrote:
>> >> On Wed, Jul 14, 2010 at 10:05 AM, Pekka Enberg <penberg@cs.helsinki.fi> wrote:
>> >>> On Wed, Jul 14, 2010 at 9:12 AM, Zeno Davatz <zdavatz@gmail.com> wrote:
>> >
>> >>>> I am attaching you the file from /sys/kernel/debug/kmemleak
>> >>> Zeno, can you post your dmesg and .config, please?
>> >> Sure, see attached files.
>> >
>> > It looks like NO_BOOTMEM is enabled. You can try the attached patch (I
>> > need to post it again on the list).
>> >
>> >
>> > kmemleak: Add support for NO_BOOTMEM configurations
>> >
>> > From: Catalin Marinas <catalin.marinas@arm.com>
>> >
>> > With commits 08677214 and 59be5a8e, alloc_bootmem()/free_bootmem() and
>> > friends use the early_res functions for memory management when
>> > NO_BOOTMEM is enabled. This patch adds the kmemleak calls in the
>> > corresponding code paths for bootmem allocations.
>> >
>> > Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
>> > Cc: Yinghai Lu <yinghai@kernel.org>
>> > Cc: H. Peter Anvin <hpa@zytor.com>
>>
>> Makes sense.
>>
>> Acked-by: Pekka Enberg <penberg@cs.helsinki.fi>
>
> I'll post an updated patch since I missed a callback. I've been testing
> it since yesterday and seems ok.

I also did not have anymore hangs and random bad moods of my CPUs that
all of a sudden grab 100% of all 8 cores of my CPU power across my
machine since I disabled

CONFIG_NO_BOOTMEM:

Best
Zeno

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-15 15:15           ` Zeno Davatz
@ 2010-07-15 15:54             ` Pekka Enberg
  2010-07-15 16:28               ` Damien Wyart
  0 siblings, 1 reply; 44+ messages in thread
From: Pekka Enberg @ 2010-07-15 15:54 UTC (permalink / raw)
  To: Zeno Davatz
  Cc: Catalin Marinas, linux-kernel, Andrew Morton, x86, mingo, yinghai,
	damien.wyart

Zeno Davatz wrote:
> Dear Catalin
> 
> On Thu, Jul 15, 2010 at 4:58 PM, Catalin Marinas
> <catalin.marinas@arm.com> wrote:
>> On Wed, 2010-07-14 at 10:55 +0100, Pekka Enberg wrote:
>>> Catalin Marinas wrote:
>>>> On Wed, 2010-07-14 at 09:27 +0100, Zeno Davatz wrote:
>>>>> On Wed, Jul 14, 2010 at 10:05 AM, Pekka Enberg <penberg@cs.helsinki.fi> wrote:
>>>>>> On Wed, Jul 14, 2010 at 9:12 AM, Zeno Davatz <zdavatz@gmail.com> wrote:
>>>>>>> I am attaching you the file from /sys/kernel/debug/kmemleak
>>>>>> Zeno, can you post your dmesg and .config, please?
>>>>> Sure, see attached files.
>>>> It looks like NO_BOOTMEM is enabled. You can try the attached patch (I
>>>> need to post it again on the list).
>>>>
>>>>
>>>> kmemleak: Add support for NO_BOOTMEM configurations
>>>>
>>>> From: Catalin Marinas <catalin.marinas@arm.com>
>>>>
>>>> With commits 08677214 and 59be5a8e, alloc_bootmem()/free_bootmem() and
>>>> friends use the early_res functions for memory management when
>>>> NO_BOOTMEM is enabled. This patch adds the kmemleak calls in the
>>>> corresponding code paths for bootmem allocations.
>>>>
>>>> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
>>>> Cc: Yinghai Lu <yinghai@kernel.org>
>>>> Cc: H. Peter Anvin <hpa@zytor.com>
>>> Makes sense.
>>>
>>> Acked-by: Pekka Enberg <penberg@cs.helsinki.fi>
>> I'll post an updated patch since I missed a callback. I've been testing
>> it since yesterday and seems ok.
> 
> I also did not have anymore hangs and random bad moods of my CPUs that
> all of a sudden grab 100% of all 8 cores of my CPU power across my
> machine since I disabled
> 
> CONFIG_NO_BOOTMEM:

Interesting. Damien, does disabling CONFIG_NO_BOOTMEM fix you problem too?

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-15 15:54             ` Pekka Enberg
@ 2010-07-15 16:28               ` Damien Wyart
  2010-07-15 19:16                 ` Damien Wyart
  0 siblings, 1 reply; 44+ messages in thread
From: Damien Wyart @ 2010-07-15 16:28 UTC (permalink / raw)
  To: Pekka Enberg
  Cc: Zeno Davatz, Catalin Marinas, linux-kernel, Andrew Morton, x86,
	mingo, yinghai

Hello,

> > I also did not have anymore hangs and random bad moods of my CPUs
> > that all of a sudden grab 100% of all 8 cores of my CPU power across
> > my machine since I disabled
> > CONFIG_NO_BOOTMEM:

* Pekka Enberg <penberg@cs.helsinki.fi> [2010-07-15 18:54]:
> Interesting. Damien, does disabling CONFIG_NO_BOOTMEM fix you problem too?

I will test in the coming hours, and report back tomorrow... Just
recompiled 2.6.35-rc5-git1 with this option disabled.

-- 
Damien

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-15 16:28               ` Damien Wyart
@ 2010-07-15 19:16                 ` Damien Wyart
  2010-07-15 19:50                   ` Pekka Enberg
  0 siblings, 1 reply; 44+ messages in thread
From: Damien Wyart @ 2010-07-15 19:16 UTC (permalink / raw)
  To: Pekka Enberg
  Cc: Zeno Davatz, Catalin Marinas, linux-kernel, Andrew Morton, x86,
	mingo, yinghai

> > > I also did not have anymore hangs and random bad moods of my CPUs
> > > that all of a sudden grab 100% of all 8 cores of my CPU power across
> > > my machine since I disabled
> > > CONFIG_NO_BOOTMEM:

> * Pekka Enberg <penberg@cs.helsinki.fi> [2010-07-15 18:54]:
> > Interesting. Damien, does disabling CONFIG_NO_BOOTMEM fix you problem too?

> I will test in the coming hours, and report back tomorrow... Just
> recompiled 2.6.35-rc5-git1 with this option disabled.

For now, I can't reproduce the problem with CONFIG_NO_BOOTMEM disabled ;
with the option and rc5 the problem was happening quite quickly after
boot and normal use of the machine. So it seems I can confirme what Zeno
has seen and I hope this will give a hint to debug the problem. I guess
this has not been reported that much because many testers might not have
enabled CONFIG_NO_BOOTMEM... Maybe the scheduler folks could test their
benchmark with a kernel having this option enabled?

-- 
Damien

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-15 19:16                 ` Damien Wyart
@ 2010-07-15 19:50                   ` Pekka Enberg
  2010-07-15 20:00                     ` Damien Wyart
  0 siblings, 1 reply; 44+ messages in thread
From: Pekka Enberg @ 2010-07-15 19:50 UTC (permalink / raw)
  To: Damien Wyart
  Cc: Zeno Davatz, Catalin Marinas, linux-kernel, Andrew Morton, x86,
	mingo, yinghai, Peter Zijlstra

On Thu, Jul 15, 2010 at 10:16 PM, Damien Wyart <damien.wyart@free.fr> wrote:
>> > > I also did not have anymore hangs and random bad moods of my CPUs
>> > > that all of a sudden grab 100% of all 8 cores of my CPU power across
>> > > my machine since I disabled
>> > > CONFIG_NO_BOOTMEM:
>
>> * Pekka Enberg <penberg@cs.helsinki.fi> [2010-07-15 18:54]:
>> > Interesting. Damien, does disabling CONFIG_NO_BOOTMEM fix you problem too?
>
>> I will test in the coming hours, and report back tomorrow... Just
>> recompiled 2.6.35-rc5-git1 with this option disabled.
>
> For now, I can't reproduce the problem with CONFIG_NO_BOOTMEM disabled ;
> with the option and rc5 the problem was happening quite quickly after
> boot and normal use of the machine. So it seems I can confirme what Zeno
> has seen and I hope this will give a hint to debug the problem. I guess
> this has not been reported that much because many testers might not have
> enabled CONFIG_NO_BOOTMEM... Maybe the scheduler folks could test their
> benchmark with a kernel having this option enabled?

To be honest, the bug is bit odd. It's related to boot-time memory
allocator changes but yet it seems to manifest itself as a scheduling
problem. So if you have some spare time and want to speed up the
debugging process, please test v2.6.34 and v2.6.35-rc1 with
CONFIG_NO_BOOTMEM and if former is good and latter is bad, try to see
if you can identify the offending commit with "git bisect."

                         Pekka

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-15 19:50                   ` Pekka Enberg
@ 2010-07-15 20:00                     ` Damien Wyart
  2010-07-15 20:38                       ` Zeno Davatz
  2010-07-15 20:52                       ` Pekka Enberg
  0 siblings, 2 replies; 44+ messages in thread
From: Damien Wyart @ 2010-07-15 20:00 UTC (permalink / raw)
  To: Pekka Enberg
  Cc: Zeno Davatz, Catalin Marinas, linux-kernel, Andrew Morton, x86,
	mingo, yinghai, Peter Zijlstra

> > For now, I can't reproduce the problem with CONFIG_NO_BOOTMEM disabled ;
> > with the option and rc5 the problem was happening quite quickly after
> > boot and normal use of the machine. So it seems I can confirme what Zeno
> > has seen and I hope this will give a hint to debug the problem. I guess
> > this has not been reported that much because many testers might not have
> > enabled CONFIG_NO_BOOTMEM... Maybe the scheduler folks could test their
> > benchmark with a kernel having this option enabled?

* Pekka Enberg <penberg@cs.helsinki.fi> [2010-07-15 22:50]:
> To be honest, the bug is bit odd. It's related to boot-time memory
> allocator changes but yet it seems to manifest itself as a scheduling
> problem. So if you have some spare time and want to speed up the
> debugging process, please test v2.6.34 and v2.6.35-rc1 with
> CONFIG_NO_BOOTMEM and if former is good and latter is bad, try to see
> if you can identify the offending commit with "git bisect."

Not sure I will have enough time in the coming days (doing that remotely
is fishy since ssh access is almost stuck when the problem occurs); if
Zeno can and would like to do it, maybe this could be done faster.

As the scheduler is now very well instrumented (many debugging features
are available), reproducing the bug on a test platform (it happens quite
quickly for me) might also give some hints. So testers, if you have
time, please test 2.6.35-rc5 with CONFIG_NO_BOOTMEM on a Core i7 and see
if you can reproduce the problem!

-- 
Damien

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-15 20:00                     ` Damien Wyart
@ 2010-07-15 20:38                       ` Zeno Davatz
  2010-07-15 20:50                         ` Pekka Enberg
  2010-07-15 20:52                       ` Pekka Enberg
  1 sibling, 1 reply; 44+ messages in thread
From: Zeno Davatz @ 2010-07-15 20:38 UTC (permalink / raw)
  To: Damien Wyart
  Cc: Pekka Enberg, Catalin Marinas, linux-kernel@vger.kernel.org,
	Andrew Morton, x86@kernel.org, mingo@elte.hu, yinghai@kernel.org,
	Peter Zijlstra

Am 15.07.2010 um 22:00 schrieb Damien Wyart <damien.wyart@free.fr>:

>>> For now, I can't reproduce the problem with CONFIG_NO_BOOTMEM disabled ;
>>> with the option and rc5 the problem was happening quite quickly after
>>> boot and normal use of the machine. So it seems I can confirme what Zeno
>>> has seen and I hope this will give a hint to debug the problem. I guess
>>> this has not been reported that much because many testers might not have
>>> enabled CONFIG_NO_BOOTMEM... Maybe the scheduler folks could test their
>>> benchmark with a kernel having this option enabled?
> 
> * Pekka Enberg <penberg@cs.helsinki.fi> [2010-07-15 22:50]:
>> To be honest, the bug is bit odd. It's related to boot-time memory
>> allocator changes but yet it seems to manifest itself as a scheduling
>> problem. So if you have some spare time and want to speed up the
>> debugging process, please test v2.6.34 and v2.6.35-rc1 with
>> CONFIG_NO_BOOTMEM and if former is good and latter is bad, try to see
>> if you can identify the offending commit with "git bisect."
> 
> Not sure I will have enough time in the coming days (doing that remotely
> is fishy since ssh access is almost stuck when the problem occurs); if
> Zeno can and would like to do it, maybe this could be done faster.
> 
> As the scheduler is now very well instrumented (many debugging features
> are available), reproducing the bug on a test platform (it happens quite
> quickly for me) might also give some hints. So testers, if you have
> time, please test 2.6.35-rc5 with CONFIG_NO_BOOTMEM on a Core i7 and see
> if you can reproduce the problem!

Will try to do so. Can you point me to the git bisect howto with the versions you want.

Best
Zeno

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-15 20:38                       ` Zeno Davatz
@ 2010-07-15 20:50                         ` Pekka Enberg
  2010-07-15 20:57                           ` Zeno Davatz
                                             ` (3 more replies)
  0 siblings, 4 replies; 44+ messages in thread
From: Pekka Enberg @ 2010-07-15 20:50 UTC (permalink / raw)
  To: Zeno Davatz
  Cc: Damien Wyart, Catalin Marinas, linux-kernel@vger.kernel.org,
	Andrew Morton, x86@kernel.org, mingo@elte.hu, yinghai@kernel.org,
	Peter Zijlstra

On Thu, Jul 15, 2010 at 11:38 PM, Zeno Davatz <zdavatz@gmail.com> wrote:
> Am 15.07.2010 um 22:00 schrieb Damien Wyart <damien.wyart@free.fr>:
>
>>>> For now, I can't reproduce the problem with CONFIG_NO_BOOTMEM disabled ;
>>>> with the option and rc5 the problem was happening quite quickly after
>>>> boot and normal use of the machine. So it seems I can confirme what Zeno
>>>> has seen and I hope this will give a hint to debug the problem. I guess
>>>> this has not been reported that much because many testers might not have
>>>> enabled CONFIG_NO_BOOTMEM... Maybe the scheduler folks could test their
>>>> benchmark with a kernel having this option enabled?
>>
>> * Pekka Enberg <penberg@cs.helsinki.fi> [2010-07-15 22:50]:
>>> To be honest, the bug is bit odd. It's related to boot-time memory
>>> allocator changes but yet it seems to manifest itself as a scheduling
>>> problem. So if you have some spare time and want to speed up the
>>> debugging process, please test v2.6.34 and v2.6.35-rc1 with
>>> CONFIG_NO_BOOTMEM and if former is good and latter is bad, try to see
>>> if you can identify the offending commit with "git bisect."
>>
>> Not sure I will have enough time in the coming days (doing that remotely
>> is fishy since ssh access is almost stuck when the problem occurs); if
>> Zeno can and would like to do it, maybe this could be done faster.
>>
>> As the scheduler is now very well instrumented (many debugging features
>> are available), reproducing the bug on a test platform (it happens quite
>> quickly for me) might also give some hints. So testers, if you have
>> time, please test 2.6.35-rc5 with CONFIG_NO_BOOTMEM on a Core i7 and see
>> if you can reproduce the problem!
>
> Will try to do so. Can you point me to the git bisect howto with the versions you want.

Cool. So like I said, you first want to test 2.6.34 to find a known
good version. Please remember to make sure you have CONFIG_NO_BOOTMEM
enabled. You can also try to speed up the process by testing
2.6.35-rc1 which is likely to include the offending commit. That's not
strictly necessary as long as you are sure that you have some
2.6.35-rc kernel that's bad.

After that, bisecting is as simple as:

  git bisect start
  git bisect good v2.6.34
  git bisect bad v2.6.31-rc1 # or some other kernel you know to be bad
  <compile, boot, and try to trigger the problem>

then

  git bisect bad # if you were able to trigger the problem

or

  git bisect good # if the problem doesn't exist

git will then find the next revision to test after which you do

  <compile, boot, and try to trigger the problem>

and repeat the "git bisect good/bad" step until git tells you it has
found the offending commit.

There's more information on the git bisect man pages:

http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html

Let me know if you need more help with this.

                        Pekka

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-15 20:50                         ` Pekka Enberg
@ 2010-07-15 20:57                           ` Zeno Davatz
  2010-07-16  7:12                           ` Zeno Davatz
                                             ` (2 subsequent siblings)
  3 siblings, 0 replies; 44+ messages in thread
From: Zeno Davatz @ 2010-07-15 20:57 UTC (permalink / raw)
  To: Pekka Enberg
  Cc: Damien Wyart, Catalin Marinas, linux-kernel@vger.kernel.org,
	Andrew Morton, x86@kernel.org, mingo@elte.hu, yinghai@kernel.org,
	Peter Zijlstra

Am 15.07.2010 um 22:50 schrieb Pekka Enberg <penberg@cs.helsinki.fi>:

> On Thu, Jul 15, 2010 at 11:38 PM, Zeno Davatz <zdavatz@gmail.com> wrote:
>> Am 15.07.2010 um 22:00 schrieb Damien Wyart <damien.wyart@free.fr>:
>> 
>>>>> For now, I can't reproduce the problem with CONFIG_NO_BOOTMEM disabled ;
>>>>> with the option and rc5 the problem was happening quite quickly after
>>>>> boot and normal use of the machine. So it seems I can confirme what Zeno
>>>>> has seen and I hope this will give a hint to debug the problem. I guess
>>>>> this has not been reported that much because many testers might not have
>>>>> enabled CONFIG_NO_BOOTMEM... Maybe the scheduler folks could test their
>>>>> benchmark with a kernel having this option enabled?
>>> 
>>> * Pekka Enberg <penberg@cs.helsinki.fi> [2010-07-15 22:50]:
>>>> To be honest, the bug is bit odd. It's related to boot-time memory
>>>> allocator changes but yet it seems to manifest itself as a scheduling
>>>> problem. So if you have some spare time and want to speed up the
>>>> debugging process, please test v2.6.34 and v2.6.35-rc1 with
>>>> CONFIG_NO_BOOTMEM and if former is good and latter is bad, try to see
>>>> if you can identify the offending commit with "git bisect."
>>> 
>>> Not sure I will have enough time in the coming days (doing that remotely
>>> is fishy since ssh access is almost stuck when the problem occurs); if
>>> Zeno can and would like to do it, maybe this could be done faster.
>>> 
>>> As the scheduler is now very well instrumented (many debugging features
>>> are available), reproducing the bug on a test platform (it happens quite
>>> quickly for me) might also give some hints. So testers, if you have
>>> time, please test 2.6.35-rc5 with CONFIG_NO_BOOTMEM on a Core i7 and see
>>> if you can reproduce the problem!
>> 
>> Will try to do so. Can you point me to the git bisect howto with the versions you want.
> 
> Cool. So like I said, you first want to test 2.6.34 to find a known
> good version. Please remember to make sure you have CONFIG_NO_BOOTMEM
> enabled. You can also try to speed up the process by testing
> 2.6.35-rc1 which is likely to include the offending commit. That's not
> strictly necessary as long as you are sure that you have some
> 2.6.35-rc kernel that's bad.
> 
> After that, bisecting is as simple as:
> 
>  git bisect start
>  git bisect good v2.6.34
>  git bisect bad v2.6.31-rc1 # or some other kernel you know to be bad
>  <compile, boot, and try to trigger the problem>
> 
> then
> 
>  git bisect bad # if you were able to trigger the problem
> 
> or
> 
>  git bisect good # if the problem doesn't exist
> 
> git will then find the next revision to test after which you do
> 
>  <compile, boot, and try to trigger the problem>
> 
> and repeat the "git bisect good/bad" step until git tells you it has
> found the offending commit.
> 
> There's more information on the git bisect man pages:
> 
> http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html
> 
> Let me know if you need more help with this.

Ok, thanks for the guidance, will start some time tomorrow. Hope to make it in the morning.

Best
Zeno

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-15 20:50                         ` Pekka Enberg
  2010-07-15 20:57                           ` Zeno Davatz
@ 2010-07-16  7:12                           ` Zeno Davatz
  2010-07-16  7:29                           ` Zeno Davatz
  2010-07-16  7:37                           ` Zeno Davatz
  3 siblings, 0 replies; 44+ messages in thread
From: Zeno Davatz @ 2010-07-16  7:12 UTC (permalink / raw)
  To: Pekka Enberg
  Cc: Damien Wyart, Catalin Marinas, linux-kernel@vger.kernel.org,
	Andrew Morton, x86@kernel.org, mingo@elte.hu, yinghai@kernel.org,
	Peter Zijlstra

On Thu, Jul 15, 2010 at 10:50 PM, Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> On Thu, Jul 15, 2010 at 11:38 PM, Zeno Davatz <zdavatz@gmail.com> wrote:
>> Am 15.07.2010 um 22:00 schrieb Damien Wyart <damien.wyart@free.fr>:
>>
>>>>> For now, I can't reproduce the problem with CONFIG_NO_BOOTMEM disabled ;
>>>>> with the option and rc5 the problem was happening quite quickly after
>>>>> boot and normal use of the machine. So it seems I can confirme what Zeno
>>>>> has seen and I hope this will give a hint to debug the problem. I guess
>>>>> this has not been reported that much because many testers might not have
>>>>> enabled CONFIG_NO_BOOTMEM... Maybe the scheduler folks could test their
>>>>> benchmark with a kernel having this option enabled?
>>>
>>> * Pekka Enberg <penberg@cs.helsinki.fi> [2010-07-15 22:50]:
>>>> To be honest, the bug is bit odd. It's related to boot-time memory
>>>> allocator changes but yet it seems to manifest itself as a scheduling
>>>> problem. So if you have some spare time and want to speed up the
>>>> debugging process, please test v2.6.34 and v2.6.35-rc1 with
>>>> CONFIG_NO_BOOTMEM and if former is good and latter is bad, try to see
>>>> if you can identify the offending commit with "git bisect."
>>>
>>> Not sure I will have enough time in the coming days (doing that remotely
>>> is fishy since ssh access is almost stuck when the problem occurs); if
>>> Zeno can and would like to do it, maybe this could be done faster.
>>>
>>> As the scheduler is now very well instrumented (many debugging features
>>> are available), reproducing the bug on a test platform (it happens quite
>>> quickly for me) might also give some hints. So testers, if you have
>>> time, please test 2.6.35-rc5 with CONFIG_NO_BOOTMEM on a Core i7 and see
>>> if you can reproduce the problem!
>>
>> Will try to do so. Can you point me to the git bisect howto with the versions you want.
>
> Cool. So like I said, you first want to test 2.6.34 to find a known
> good version. Please remember to make sure you have CONFIG_NO_BOOTMEM
> enabled. You can also try to speed up the process by testing
> 2.6.35-rc1 which is likely to include the offending commit. That's not
> strictly necessary as long as you are sure that you have some
> 2.6.35-rc kernel that's bad.
>
> After that, bisecting is as simple as:
>
>  git bisect start
>  git bisect good v2.6.34
>  git bisect bad v2.6.31-rc1 # or some other kernel you know to be bad
>  <compile, boot, and try to trigger the problem>
>
> then
>
>  git bisect bad # if you were able to trigger the problem
>
> or
>
>  git bisect good # if the problem doesn't exist
>
> git will then find the next revision to test after which you do
>
>  <compile, boot, and try to trigger the problem>
>
> and repeat the "git bisect good/bad" step until git tells you it has
> found the offending commit.
>
> There's more information on the git bisect man pages:
>
> http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html
>
> Let me know if you need more help with this.

Ok, something sure is wrong with 2.6.34-rc8 I could not boot after I
done the normal bit bisect, cp bzImage and then running lilo -v

http://www.flickr.com/photos/zrr/4798077725/

I am gonna continue bisecting. 2.6.34-rc7 is fine. No CPU eaters around.

Best
Zeno

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-15 20:50                         ` Pekka Enberg
  2010-07-15 20:57                           ` Zeno Davatz
  2010-07-16  7:12                           ` Zeno Davatz
@ 2010-07-16  7:29                           ` Zeno Davatz
  2010-07-16  7:37                           ` Zeno Davatz
  3 siblings, 0 replies; 44+ messages in thread
From: Zeno Davatz @ 2010-07-16  7:29 UTC (permalink / raw)
  To: Pekka Enberg
  Cc: Damien Wyart, Catalin Marinas, linux-kernel@vger.kernel.org,
	Andrew Morton, x86@kernel.org, mingo@elte.hu, yinghai@kernel.org,
	Peter Zijlstra

On Thu, Jul 15, 2010 at 10:50 PM, Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> On Thu, Jul 15, 2010 at 11:38 PM, Zeno Davatz <zdavatz@gmail.com> wrote:
>> Am 15.07.2010 um 22:00 schrieb Damien Wyart <damien.wyart@free.fr>:
>>
>>>>> For now, I can't reproduce the problem with CONFIG_NO_BOOTMEM disabled ;
>>>>> with the option and rc5 the problem was happening quite quickly after
>>>>> boot and normal use of the machine. So it seems I can confirme what Zeno
>>>>> has seen and I hope this will give a hint to debug the problem. I guess
>>>>> this has not been reported that much because many testers might not have
>>>>> enabled CONFIG_NO_BOOTMEM... Maybe the scheduler folks could test their
>>>>> benchmark with a kernel having this option enabled?
>>>
>>> * Pekka Enberg <penberg@cs.helsinki.fi> [2010-07-15 22:50]:
>>>> To be honest, the bug is bit odd. It's related to boot-time memory
>>>> allocator changes but yet it seems to manifest itself as a scheduling
>>>> problem. So if you have some spare time and want to speed up the
>>>> debugging process, please test v2.6.34 and v2.6.35-rc1 with
>>>> CONFIG_NO_BOOTMEM and if former is good and latter is bad, try to see
>>>> if you can identify the offending commit with "git bisect."
>>>
>>> Not sure I will have enough time in the coming days (doing that remotely
>>> is fishy since ssh access is almost stuck when the problem occurs); if
>>> Zeno can and would like to do it, maybe this could be done faster.
>>>
>>> As the scheduler is now very well instrumented (many debugging features
>>> are available), reproducing the bug on a test platform (it happens quite
>>> quickly for me) might also give some hints. So testers, if you have
>>> time, please test 2.6.35-rc5 with CONFIG_NO_BOOTMEM on a Core i7 and see
>>> if you can reproduce the problem!
>>
>> Will try to do so. Can you point me to the git bisect howto with the versions you want.
>
> Cool. So like I said, you first want to test 2.6.34 to find a known
> good version. Please remember to make sure you have CONFIG_NO_BOOTMEM
> enabled. You can also try to speed up the process by testing
> 2.6.35-rc1 which is likely to include the offending commit. That's not
> strictly necessary as long as you are sure that you have some
> 2.6.35-rc kernel that's bad.
>
> After that, bisecting is as simple as:
>
>  git bisect start
>  git bisect good v2.6.34
>  git bisect bad v2.6.31-rc1 # or some other kernel you know to be bad
>  <compile, boot, and try to trigger the problem>
>
> then
>
>  git bisect bad # if you were able to trigger the problem
>
> or
>
>  git bisect good # if the problem doesn't exist
>
> git will then find the next revision to test after which you do
>
>  <compile, boot, and try to trigger the problem>
>
> and repeat the "git bisect good/bad" step until git tells you it has
> found the offending commit.
>
> There's more information on the git bisect man pages:
>
> http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html
>
> Let me know if you need more help with this.

This one also causes a panic:

http://www.flickr.com/photos/zrr/4798092747/in/photostream/

but this version boots just fine again:

Linux zenogentoo 2.6.34-05459-gac3ee84 #102 SMP Fri Jul 16 09:22:25
CEST 2010 i686 Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz GenuineIntel
GNU/Linux

Best
Zeno

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-15 20:50                         ` Pekka Enberg
                                             ` (2 preceding siblings ...)
  2010-07-16  7:29                           ` Zeno Davatz
@ 2010-07-16  7:37                           ` Zeno Davatz
  2010-07-16  7:50                             ` Pekka Enberg
  3 siblings, 1 reply; 44+ messages in thread
From: Zeno Davatz @ 2010-07-16  7:37 UTC (permalink / raw)
  To: Pekka Enberg
  Cc: Damien Wyart, Catalin Marinas, linux-kernel@vger.kernel.org,
	Andrew Morton, x86@kernel.org, mingo@elte.hu, yinghai@kernel.org,
	Peter Zijlstra

On Thu, Jul 15, 2010 at 10:50 PM, Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> On Thu, Jul 15, 2010 at 11:38 PM, Zeno Davatz <zdavatz@gmail.com> wrote:
>> Am 15.07.2010 um 22:00 schrieb Damien Wyart <damien.wyart@free.fr>:
>>
>>>>> For now, I can't reproduce the problem with CONFIG_NO_BOOTMEM disabled ;
>>>>> with the option and rc5 the problem was happening quite quickly after
>>>>> boot and normal use of the machine. So it seems I can confirme what Zeno
>>>>> has seen and I hope this will give a hint to debug the problem. I guess
>>>>> this has not been reported that much because many testers might not have
>>>>> enabled CONFIG_NO_BOOTMEM... Maybe the scheduler folks could test their
>>>>> benchmark with a kernel having this option enabled?
>>>
>>> * Pekka Enberg <penberg@cs.helsinki.fi> [2010-07-15 22:50]:
>>>> To be honest, the bug is bit odd. It's related to boot-time memory
>>>> allocator changes but yet it seems to manifest itself as a scheduling
>>>> problem. So if you have some spare time and want to speed up the
>>>> debugging process, please test v2.6.34 and v2.6.35-rc1 with
>>>> CONFIG_NO_BOOTMEM and if former is good and latter is bad, try to see
>>>> if you can identify the offending commit with "git bisect."
>>>
>>> Not sure I will have enough time in the coming days (doing that remotely
>>> is fishy since ssh access is almost stuck when the problem occurs); if
>>> Zeno can and would like to do it, maybe this could be done faster.
>>>
>>> As the scheduler is now very well instrumented (many debugging features
>>> are available), reproducing the bug on a test platform (it happens quite
>>> quickly for me) might also give some hints. So testers, if you have
>>> time, please test 2.6.35-rc5 with CONFIG_NO_BOOTMEM on a Core i7 and see
>>> if you can reproduce the problem!
>>
>> Will try to do so. Can you point me to the git bisect howto with the versions you want.
>
> Cool. So like I said, you first want to test 2.6.34 to find a known
> good version. Please remember to make sure you have CONFIG_NO_BOOTMEM
> enabled. You can also try to speed up the process by testing
> 2.6.35-rc1 which is likely to include the offending commit. That's not
> strictly necessary as long as you are sure that you have some
> 2.6.35-rc kernel that's bad.
>
> After that, bisecting is as simple as:
>
>  git bisect start
>  git bisect good v2.6.34
>  git bisect bad v2.6.31-rc1 # or some other kernel you know to be bad
>  <compile, boot, and try to trigger the problem>
>
> then
>
>  git bisect bad # if you were able to trigger the problem
>
> or
>
>  git bisect good # if the problem doesn't exist
>
> git will then find the next revision to test after which you do
>
>  <compile, boot, and try to trigger the problem>
>
> and repeat the "git bisect good/bad" step until git tells you it has
> found the offending commit.
>
> There's more information on the git bisect man pages:
>
> http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html
>
> Let me know if you need more help with this.

The next RC again hangs on me:

http://www.flickr.com/photos/zrr/4798744700/sizes/l/

Gruss
Zeno

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-16  7:37                           ` Zeno Davatz
@ 2010-07-16  7:50                             ` Pekka Enberg
  2010-07-16  9:17                               ` Zeno Davatz
  0 siblings, 1 reply; 44+ messages in thread
From: Pekka Enberg @ 2010-07-16  7:50 UTC (permalink / raw)
  To: Zeno Davatz
  Cc: Damien Wyart, Catalin Marinas, linux-kernel@vger.kernel.org,
	Andrew Morton, x86@kernel.org, mingo@elte.hu, yinghai@kernel.org,
	Peter Zijlstra

On Fri, Jul 16, 2010 at 10:37 AM, Zeno Davatz <zdavatz@gmail.com> wrote:
>> Let me know if you need more help with this.
>
> The next RC again hangs on me:
>
> http://www.flickr.com/photos/zrr/4798744700/sizes/l/

Doesn't look like a kernel bug to me. Maybe some Gentoo person knows
better but the 'root' parameter you pass to the kernel in your lilo
configuration looks a little strange. You should try passing
"/dev/sdXX" to it where XX is whatever partition your root filesystems
is on.

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-16  7:50                             ` Pekka Enberg
@ 2010-07-16  9:17                               ` Zeno Davatz
  2010-07-16  9:32                                 ` Pekka Enberg
  0 siblings, 1 reply; 44+ messages in thread
From: Zeno Davatz @ 2010-07-16  9:17 UTC (permalink / raw)
  To: Pekka Enberg
  Cc: Damien Wyart, Catalin Marinas, linux-kernel@vger.kernel.org,
	Andrew Morton, x86@kernel.org, mingo@elte.hu, yinghai@kernel.org,
	Peter Zijlstra

On Fri, Jul 16, 2010 at 9:50 AM, Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> On Fri, Jul 16, 2010 at 10:37 AM, Zeno Davatz <zdavatz@gmail.com> wrote:
>>> Let me know if you need more help with this.
>>
>> The next RC again hangs on me:
>>
>> http://www.flickr.com/photos/zrr/4798744700/sizes/l/
>
> Doesn't look like a kernel bug to me. Maybe some Gentoo person knows
> better but the 'root' parameter you pass to the kernel in your lilo
> configuration looks a little strange. You should try passing
> "/dev/sdXX" to it where XX is whatever partition your root filesystems
> is on.

This version has some problem with the DRM but no CPU eater yet.

http://www.flickr.com/photos/zrr/4798885756/

This version boots again just fine:

Linux zenogentoo 2.6.34-rc5-00059-gc2b4127 #105 SMP Fri Jul 16
11:13:21 CEST 2010 i686 Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz
GenuineIntel GNU/Linux

As I understand I am bisecting upwards. Every time it does not boot
correctly I do

git bisect bad after the next boot.

Best
Zeno

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-16  9:17                               ` Zeno Davatz
@ 2010-07-16  9:32                                 ` Pekka Enberg
  2010-07-16  9:42                                   ` Zeno Davatz
  2010-07-16  9:47                                   ` Zeno Davatz
  0 siblings, 2 replies; 44+ messages in thread
From: Pekka Enberg @ 2010-07-16  9:32 UTC (permalink / raw)
  To: Zeno Davatz
  Cc: Damien Wyart, Catalin Marinas, linux-kernel@vger.kernel.org,
	Andrew Morton, x86@kernel.org, mingo@elte.hu, yinghai@kernel.org,
	Peter Zijlstra

Hi Zeno,

Zeno Davatz wrote:
> This version has some problem with the DRM but no CPU eater yet.
> 
> http://www.flickr.com/photos/zrr/4798885756/
> 
> This version boots again just fine:
> 
> Linux zenogentoo 2.6.34-rc5-00059-gc2b4127 #105 SMP Fri Jul 16
> 11:13:21 CEST 2010 i686 Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz
> GenuineIntel GNU/Linux

You're going into the wrong direction. If 2.6.34-rc7 works just fine, 
you shouldn't be testing 2.6.34-rc5.

> 
> As I understand I am bisecting upwards. Every time it does not boot
> correctly I do
> 
> git bisect bad after the next boot.

No, you should only do "git bisect bad" if you find a CPU eater and "git 
bisect good" if you don't. For the non-booting kernels you should do 
"git bisect skip"; otherwise git gets confused as we can see here.

Did you test v2.6.35-rc1? Does it have the CPU eater problem? If yes, 
please just reset your bisection

   git bisect reset
   git bisect start
   git bisect good v2.6.34-rc7
   git bisect bad v2.6.35-rc1

and use 'git bisect skip' for kernels that don't boot or build.

			Pekka

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-16  9:32                                 ` Pekka Enberg
@ 2010-07-16  9:42                                   ` Zeno Davatz
  2010-07-16  9:47                                   ` Zeno Davatz
  1 sibling, 0 replies; 44+ messages in thread
From: Zeno Davatz @ 2010-07-16  9:42 UTC (permalink / raw)
  To: Pekka Enberg
  Cc: Damien Wyart, Catalin Marinas, linux-kernel@vger.kernel.org,
	Andrew Morton, x86@kernel.org, mingo@elte.hu, yinghai@kernel.org,
	Peter Zijlstra

On Fri, Jul 16, 2010 at 11:32 AM, Pekka Enberg <penberg@cs.helsinki.fi> wrote:

> No, you should only do "git bisect bad" if you find a CPU eater and "git
> bisect good" if you don't. For the non-booting kernels you should do "git
> bisect skip"; otherwise git gets confused as we can see here.
>
> Did you test v2.6.35-rc1? Does it have the CPU eater problem? If yes, please
> just reset your bisection
>
>  git bisect reset
>  git bisect start
>  git bisect good v2.6.34-rc7
>  git bisect bad v2.6.35-rc1
>
> and use 'git bisect skip' for kernels that don't boot or build.

Ok I done above and reboot onto the new bzImage:

This version looks fine.

Linux zenogentoo 2.6.34-04401-gf896546 #106 SMP Fri Jul 16 11:37:04
CEST 2010 i686 Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz GenuineIntel
GNU/Linux

Best
Zeno

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-16  9:32                                 ` Pekka Enberg
  2010-07-16  9:42                                   ` Zeno Davatz
@ 2010-07-16  9:47                                   ` Zeno Davatz
  2010-07-16 18:27                                     ` Yinghai Lu
  1 sibling, 1 reply; 44+ messages in thread
From: Zeno Davatz @ 2010-07-16  9:47 UTC (permalink / raw)
  To: Pekka Enberg
  Cc: Damien Wyart, Catalin Marinas, linux-kernel@vger.kernel.org,
	Andrew Morton, x86@kernel.org, mingo@elte.hu, yinghai@kernel.org,
	Peter Zijlstra

On Fri, Jul 16, 2010 at 11:32 AM, Pekka Enberg <penberg@cs.helsinki.fi> wrote:

> Zeno Davatz wrote:
>>
>> This version has some problem with the DRM but no CPU eater yet.
>>
>> http://www.flickr.com/photos/zrr/4798885756/
>>
>> This version boots again just fine:
>>
>> Linux zenogentoo 2.6.34-rc5-00059-gc2b4127 #105 SMP Fri Jul 16
>> 11:13:21 CEST 2010 i686 Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz
>> GenuineIntel GNU/Linux
>
> You're going into the wrong direction. If 2.6.34-rc7 works just fine, you
> shouldn't be testing 2.6.34-rc5.
>
>>
>> As I understand I am bisecting upwards. Every time it does not boot
>> correctly I do
>>
>> git bisect bad after the next boot.
>
> No, you should only do "git bisect bad" if you find a CPU eater and "git
> bisect good" if you don't. For the non-booting kernels you should do "git
> bisect skip"; otherwise git gets confused as we can see here.
>
> Did you test v2.6.35-rc1? Does it have the CPU eater problem? If yes, please
> just reset your bisection
>
>  git bisect reset
>  git bisect start
>  git bisect good v2.6.34-rc7
>  git bisect bad v2.6.35-rc1
>
> and use 'git bisect skip' for kernels that don't boot or build.
This one looks good to:

Linux zenogentoo 2.6.34-06562-gd79df0b #107 SMP Fri Jul 16 11:44:36
CEST 2010 i686 Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz GenuineIntel
GNU/Linux

Best
Zeno

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-16  9:47                                   ` Zeno Davatz
@ 2010-07-16 18:27                                     ` Yinghai Lu
  2010-07-16 20:29                                       ` Zeno Davatz
  0 siblings, 1 reply; 44+ messages in thread
From: Yinghai Lu @ 2010-07-16 18:27 UTC (permalink / raw)
  To: Zeno Davatz
  Cc: Pekka Enberg, Damien Wyart, Catalin Marinas,
	linux-kernel@vger.kernel.org, Andrew Morton, x86@kernel.org,
	mingo@elte.hu, Peter Zijlstra

it seems that you are using 32bit kernel. please check if this one help.

Thanks

Yinghai

Subject: [PATCH -v3] x86,mm: fix 32bit numa sparsemem

Borislav Petkov <borislav.petkov@amd.com> reported his 32bit numa has problem:

[    0.000000] Reserving total of 4c00 pages for numa KVA remap
[    0.000000] kva_start_pfn ~ 32800 max_low_pfn ~ 375fe
[    0.000000] max_pfn = 238000
[    0.000000] 8202MB HIGHMEM available.
[    0.000000] 885MB LOWMEM available.
[    0.000000]   mapped low ram: 0 - 375fe000
[    0.000000]   low ram: 0 - 375fe000
[    0.000000] alloc (nid=8 100000 - 7ee00000) (1000000 - ffffffff) 1000 1000 => 34e7000
[    0.000000] alloc (nid=8 100000 - 7ee00000) (1000000 - ffffffff) 200 40 => 34c9d80
[    0.000000] alloc (nid=0 100000 - 7ee00000) (1000000 - ffffffffffffffff) 180 40 => 34e6140
[    0.000000] alloc (nid=1 80000000 - c7e60000) (1000000 - ffffffffffffffff) 240 40 => 80000000
[    0.000000] BUG: unable to handle kernel paging request at 40000000
[    0.000000] IP: [<c2c8cff1>] __alloc_memory_core_early+0x147/0x1d6
[    0.000000] *pdpt = 0000000000000000 *pde = f000ff53f000ff00 
...
[    0.000000] Call Trace:
[    0.000000]  [<c2c8b4f8>] ? __alloc_bootmem_node+0x216/0x22f
[    0.000000]  [<c2c90c9b>] ? sparse_early_usemaps_alloc_node+0x5a/0x10b
[    0.000000]  [<c2c9149e>] ? sparse_init+0x1dc/0x499
[    0.000000]  [<c2c79118>] ? paging_init+0x168/0x1df
[    0.000000]  [<c2c780ff>] ? native_pagetable_setup_start+0xef/0x1bb

looks like it allocate much high address for bootmem.

try to cut limit with get_max_mapped()

-v3: make alloc_bootmem_node could fallback to other node.
     just like old alloc_bootmem_node did

need this patch for 2.6.34 and 2.6.35

Reported-by: Borislav Petkov <borislav.petkov@amd.com>
Signed-off-by: Yinghai Lu <yinghai@kernel.org>
Cc: stable@kernel.org

---
 mm/bootmem.c    |   24 ++++++++++++++++++++----
 mm/page_alloc.c |    3 +++
 2 files changed, 23 insertions(+), 4 deletions(-)

Index: linux-2.6/mm/page_alloc.c
===================================================================
--- linux-2.6.orig/mm/page_alloc.c
+++ linux-2.6/mm/page_alloc.c
@@ -3634,6 +3634,9 @@ void * __init __alloc_memory_core_early(
 	int i;
 	void *ptr;
 
+	if (limit > get_max_mapped())
+		limit = get_max_mapped();
+
 	/* need to go over early_node_map to find out good range for node */
 	for_each_active_range_index_in_nid(i, nid) {
 		u64 addr;
Index: linux-2.6/mm/bootmem.c
===================================================================
--- linux-2.6.orig/mm/bootmem.c
+++ linux-2.6/mm/bootmem.c
@@ -833,15 +833,24 @@ static void * __init ___alloc_bootmem_no
 void * __init __alloc_bootmem_node(pg_data_t *pgdat, unsigned long size,
 				   unsigned long align, unsigned long goal)
 {
+	void *ptr;
+
 	if (WARN_ON_ONCE(slab_is_available()))
 		return kzalloc_node(size, GFP_NOWAIT, pgdat->node_id);
 
 #ifdef CONFIG_NO_BOOTMEM
-	return __alloc_memory_core_early(pgdat->node_id, size, align,
+	ptr = __alloc_memory_core_early(pgdat->node_id, size, align,
+					 goal, -1ULL);
+	if (ptr)
+		return ptr;
+
+	ptr = __alloc_memory_core_early(MAX_NUMNODES, size, align,
 					 goal, -1ULL);
 #else
-	return ___alloc_bootmem_node(pgdat->bdata, size, align, goal, 0);
+	ptr = ___alloc_bootmem_node(pgdat->bdata, size, align, goal, 0);
 #endif
+
+	return ptr;
 }
 
 void * __init __alloc_bootmem_node_high(pg_data_t *pgdat, unsigned long size,
@@ -977,14 +986,21 @@ void * __init __alloc_bootmem_low(unsign
 void * __init __alloc_bootmem_low_node(pg_data_t *pgdat, unsigned long size,
 				       unsigned long align, unsigned long goal)
 {
+	void *ptr;
+
 	if (WARN_ON_ONCE(slab_is_available()))
 		return kzalloc_node(size, GFP_NOWAIT, pgdat->node_id);
 
 #ifdef CONFIG_NO_BOOTMEM
-	return __alloc_memory_core_early(pgdat->node_id, size, align,
+	ptr = __alloc_memory_core_early(pgdat->node_id, size, align,
+				goal, ARCH_LOW_ADDRESS_LIMIT);
+	if (ptr)
+		return ptr;
+	ptr = __alloc_memory_core_early(MAX_NUMNODES, size, align,
 				goal, ARCH_LOW_ADDRESS_LIMIT);
 #else
-	return ___alloc_bootmem_node(pgdat->bdata, size, align,
+	ptr = ___alloc_bootmem_node(pgdat->bdata, size, align,
 				goal, ARCH_LOW_ADDRESS_LIMIT);
 #endif
+	return ptr;
 }

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-16 18:27                                     ` Yinghai Lu
@ 2010-07-16 20:29                                       ` Zeno Davatz
  2010-07-16 20:59                                         ` Yinghai Lu
  0 siblings, 1 reply; 44+ messages in thread
From: Zeno Davatz @ 2010-07-16 20:29 UTC (permalink / raw)
  To: Yinghai Lu
  Cc: Pekka Enberg, Damien Wyart, Catalin Marinas,
	linux-kernel@vger.kernel.org, Andrew Morton, x86@kernel.org,
	mingo@elte.hu, Peter Zijlstra


Am 16.07.2010 um 20:27 schrieb Yinghai Lu <yinghai@kernel.org>:

> it seems that you are using 32bit kernel. please check if this one help.

Thanks! What RC should I patch? 2.6.35-rc5?

Best
Zeno

> Subject: [PATCH -v3] x86,mm: fix 32bit numa sparsemem
> 
> Borislav Petkov <borislav.petkov@amd.com> reported his 32bit numa has problem:
> 
> [    0.000000] Reserving total of 4c00 pages for numa KVA remap
> [    0.000000] kva_start_pfn ~ 32800 max_low_pfn ~ 375fe
> [    0.000000] max_pfn = 238000
> [    0.000000] 8202MB HIGHMEM available.
> [    0.000000] 885MB LOWMEM available.
> [    0.000000]   mapped low ram: 0 - 375fe000
> [    0.000000]   low ram: 0 - 375fe000
> [    0.000000] alloc (nid=8 100000 - 7ee00000) (1000000 - ffffffff) 1000 1000 => 34e7000
> [    0.000000] alloc (nid=8 100000 - 7ee00000) (1000000 - ffffffff) 200 40 => 34c9d80
> [    0.000000] alloc (nid=0 100000 - 7ee00000) (1000000 - ffffffffffffffff) 180 40 => 34e6140
> [    0.000000] alloc (nid=1 80000000 - c7e60000) (1000000 - ffffffffffffffff) 240 40 => 80000000
> [    0.000000] BUG: unable to handle kernel paging request at 40000000
> [    0.000000] IP: [<c2c8cff1>] __alloc_memory_core_early+0x147/0x1d6
> [    0.000000] *pdpt = 0000000000000000 *pde = f000ff53f000ff00 
> ...
> [    0.000000] Call Trace:
> [    0.000000]  [<c2c8b4f8>] ? __alloc_bootmem_node+0x216/0x22f
> [    0.000000]  [<c2c90c9b>] ? sparse_early_usemaps_alloc_node+0x5a/0x10b
> [    0.000000]  [<c2c9149e>] ? sparse_init+0x1dc/0x499
> [    0.000000]  [<c2c79118>] ? paging_init+0x168/0x1df
> [    0.000000]  [<c2c780ff>] ? native_pagetable_setup_start+0xef/0x1bb
> 
> looks like it allocate much high address for bootmem.
> 
> try to cut limit with get_max_mapped()
> 
> -v3: make alloc_bootmem_node could fallback to other node.
>     just like old alloc_bootmem_node did
> 
> need this patch for 2.6.34 and 2.6.35
> 
> Reported-by: Borislav Petkov <borislav.petkov@amd.com>
> Signed-off-by: Yinghai Lu <yinghai@kernel.org>
> Cc: stable@kernel.org
> 
> ---
> mm/bootmem.c    |   24 ++++++++++++++++++++----
> mm/page_alloc.c |    3 +++
> 2 files changed, 23 insertions(+), 4 deletions(-)
> 
> Index: linux-2.6/mm/page_alloc.c
> ===================================================================
> --- linux-2.6.orig/mm/page_alloc.c
> +++ linux-2.6/mm/page_alloc.c
> @@ -3634,6 +3634,9 @@ void * __init __alloc_memory_core_early(
>    int i;
>    void *ptr;
> 
> +    if (limit > get_max_mapped())
> +        limit = get_max_mapped();
> +
>    /* need to go over early_node_map to find out good range for node */
>    for_each_active_range_index_in_nid(i, nid) {
>        u64 addr;
> Index: linux-2.6/mm/bootmem.c
> ===================================================================
> --- linux-2.6.orig/mm/bootmem.c
> +++ linux-2.6/mm/bootmem.c
> @@ -833,15 +833,24 @@ static void * __init ___alloc_bootmem_no
> void * __init __alloc_bootmem_node(pg_data_t *pgdat, unsigned long size,
>                   unsigned long align, unsigned long goal)
> {
> +    void *ptr;
> +
>    if (WARN_ON_ONCE(slab_is_available()))
>        return kzalloc_node(size, GFP_NOWAIT, pgdat->node_id);
> 
> #ifdef CONFIG_NO_BOOTMEM
> -    return __alloc_memory_core_early(pgdat->node_id, size, align,
> +    ptr = __alloc_memory_core_early(pgdat->node_id, size, align,
> +                     goal, -1ULL);
> +    if (ptr)
> +        return ptr;
> +
> +    ptr = __alloc_memory_core_early(MAX_NUMNODES, size, align,
>                     goal, -1ULL);
> #else
> -    return ___alloc_bootmem_node(pgdat->bdata, size, align, goal, 0);
> +    ptr = ___alloc_bootmem_node(pgdat->bdata, size, align, goal, 0);
> #endif
> +
> +    return ptr;
> }
> 
> void * __init __alloc_bootmem_node_high(pg_data_t *pgdat, unsigned long size,
> @@ -977,14 +986,21 @@ void * __init __alloc_bootmem_low(unsign
> void * __init __alloc_bootmem_low_node(pg_data_t *pgdat, unsigned long size,
>                       unsigned long align, unsigned long goal)
> {
> +    void *ptr;
> +
>    if (WARN_ON_ONCE(slab_is_available()))
>        return kzalloc_node(size, GFP_NOWAIT, pgdat->node_id);
> 
> #ifdef CONFIG_NO_BOOTMEM
> -    return __alloc_memory_core_early(pgdat->node_id, size, align,
> +    ptr = __alloc_memory_core_early(pgdat->node_id, size, align,
> +                goal, ARCH_LOW_ADDRESS_LIMIT);
> +    if (ptr)
> +        return ptr;
> +    ptr = __alloc_memory_core_early(MAX_NUMNODES, size, align,
>                goal, ARCH_LOW_ADDRESS_LIMIT);
> #else
> -    return ___alloc_bootmem_node(pgdat->bdata, size, align,
> +    ptr = ___alloc_bootmem_node(pgdat->bdata, size, align,
>                goal, ARCH_LOW_ADDRESS_LIMIT);
> #endif
> +    return ptr;
> }

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-16 20:29                                       ` Zeno Davatz
@ 2010-07-16 20:59                                         ` Yinghai Lu
  2010-07-17  8:46                                           ` Zeno Davatz
  0 siblings, 1 reply; 44+ messages in thread
From: Yinghai Lu @ 2010-07-16 20:59 UTC (permalink / raw)
  To: Zeno Davatz
  Cc: Pekka Enberg, Damien Wyart, Catalin Marinas,
	linux-kernel@vger.kernel.org, Andrew Morton, x86@kernel.org,
	mingo@elte.hu, Peter Zijlstra

On 07/16/2010 01:29 PM, Zeno Davatz wrote:
> 
> Am 16.07.2010 um 20:27 schrieb Yinghai Lu <yinghai@kernel.org>:
> 
>> it seems that you are using 32bit kernel. please check if this one help.
> 
> Thanks! What RC should I patch? 2.6.35-rc5?

current linus tree or 2.6.35-rc5.

Thanks

Yinghai

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-16 20:59                                         ` Yinghai Lu
@ 2010-07-17  8:46                                           ` Zeno Davatz
  0 siblings, 0 replies; 44+ messages in thread
From: Zeno Davatz @ 2010-07-17  8:46 UTC (permalink / raw)
  To: Yinghai Lu
  Cc: Pekka Enberg, Damien Wyart, Catalin Marinas,
	linux-kernel@vger.kernel.org, Andrew Morton, x86@kernel.org,
	mingo@elte.hu, Peter Zijlstra

On Fri, Jul 16, 2010 at 10:59 PM, Yinghai Lu <yinghai@kernel.org> wrote:
> On 07/16/2010 01:29 PM, Zeno Davatz wrote:
>>
>> Am 16.07.2010 um 20:27 schrieb Yinghai Lu <yinghai@kernel.org>:
>>
>>> it seems that you are using 32bit kernel. please check if this one help.
>>
>> Thanks! What RC should I patch? 2.6.35-rc5?
>
> current linus tree or 2.6.35-rc5.

Tried to patch 2.6.35-rc5 but I get:

/usr/src/my2.6> sudo patch -p1 < patch_yinghai
patching file mm/page_alloc.c
Hunk #1 FAILED at 3634.
1 out of 1 hunk FAILED -- saving rejects to file mm/page_alloc.c.rej
patching file mm/bootmem.c
Hunk #1 FAILED at 833.
Hunk #2 FAILED at 986.
2 out of 2 hunks FAILED -- saving rejects to file mm/bootmem.c.rej

Any hints?

It seems that 2.6.35-rc1 does not have the CPU eater problem. I still
running it without any interference (though I was away from the
computer for some time).

Best
Zeno

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-15 20:00                     ` Damien Wyart
  2010-07-15 20:38                       ` Zeno Davatz
@ 2010-07-15 20:52                       ` Pekka Enberg
  2010-08-03  9:05                         ` Peter Zijlstra
  1 sibling, 1 reply; 44+ messages in thread
From: Pekka Enberg @ 2010-07-15 20:52 UTC (permalink / raw)
  To: Damien Wyart
  Cc: Zeno Davatz, Catalin Marinas, linux-kernel, Andrew Morton, x86,
	mingo, yinghai, Peter Zijlstra

On Thu, Jul 15, 2010 at 11:00 PM, Damien Wyart <damien.wyart@free.fr> wrote:
>> > For now, I can't reproduce the problem with CONFIG_NO_BOOTMEM disabled ;
>> > with the option and rc5 the problem was happening quite quickly after
>> > boot and normal use of the machine. So it seems I can confirme what Zeno
>> > has seen and I hope this will give a hint to debug the problem. I guess
>> > this has not been reported that much because many testers might not have
>> > enabled CONFIG_NO_BOOTMEM... Maybe the scheduler folks could test their
>> > benchmark with a kernel having this option enabled?
>
> * Pekka Enberg <penberg@cs.helsinki.fi> [2010-07-15 22:50]:
>> To be honest, the bug is bit odd. It's related to boot-time memory
>> allocator changes but yet it seems to manifest itself as a scheduling
>> problem. So if you have some spare time and want to speed up the
>> debugging process, please test v2.6.34 and v2.6.35-rc1 with
>> CONFIG_NO_BOOTMEM and if former is good and latter is bad, try to see
>> if you can identify the offending commit with "git bisect."
>
> Not sure I will have enough time in the coming days (doing that remotely
> is fishy since ssh access is almost stuck when the problem occurs); if
> Zeno can and would like to do it, maybe this could be done faster.
>
> As the scheduler is now very well instrumented (many debugging features
> are available), reproducing the bug on a test platform (it happens quite
> quickly for me) might also give some hints. So testers, if you have
> time, please test 2.6.35-rc5 with CONFIG_NO_BOOTMEM on a Core i7 and see
> if you can reproduce the problem!

Yeah, there's "perf sched" tool available for that:

  http://lwn.net/Articles/353295/

The only problem is that we'd need a scheduler hacker to decipher the
report and all of them seem to be missing at the moment (probably at
OLS). Anyway, like I said, git bisect will probably speed up the
debugging process, that's all.

                          Pekka

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-15 20:52                       ` Pekka Enberg
@ 2010-08-03  9:05                         ` Peter Zijlstra
  2010-08-03  9:11                           ` Zeno Davatz
  0 siblings, 1 reply; 44+ messages in thread
From: Peter Zijlstra @ 2010-08-03  9:05 UTC (permalink / raw)
  To: Pekka Enberg
  Cc: Damien Wyart, Zeno Davatz, Catalin Marinas, linux-kernel,
	Andrew Morton, x86, mingo, yinghai

On Thu, 2010-07-15 at 23:52 +0300, Pekka Enberg wrote:
> On Thu, Jul 15, 2010 at 11:00 PM, Damien Wyart <damien.wyart@free.fr> wrote:
> >> > For now, I can't reproduce the problem with CONFIG_NO_BOOTMEM disabled ;
> >> > with the option and rc5 the problem was happening quite quickly after
> >> > boot and normal use of the machine. So it seems I can confirme what Zeno
> >> > has seen and I hope this will give a hint to debug the problem. I guess
> >> > this has not been reported that much because many testers might not have
> >> > enabled CONFIG_NO_BOOTMEM... Maybe the scheduler folks could test their
> >> > benchmark with a kernel having this option enabled?
> >
> > * Pekka Enberg <penberg@cs.helsinki.fi> [2010-07-15 22:50]:
> >> To be honest, the bug is bit odd. It's related to boot-time memory
> >> allocator changes but yet it seems to manifest itself as a scheduling
> >> problem. So if you have some spare time and want to speed up the
> >> debugging process, please test v2.6.34 and v2.6.35-rc1 with
> >> CONFIG_NO_BOOTMEM and if former is good and latter is bad, try to see
> >> if you can identify the offending commit with "git bisect."
> >
> > Not sure I will have enough time in the coming days (doing that remotely
> > is fishy since ssh access is almost stuck when the problem occurs); if
> > Zeno can and would like to do it, maybe this could be done faster.
> >
> > As the scheduler is now very well instrumented (many debugging features
> > are available), reproducing the bug on a test platform (it happens quite
> > quickly for me) might also give some hints. So testers, if you have
> > time, please test 2.6.35-rc5 with CONFIG_NO_BOOTMEM on a Core i7 and see
> > if you can reproduce the problem!
> 
> Yeah, there's "perf sched" tool available for that:
> 
>   http://lwn.net/Articles/353295/
> 
> The only problem is that we'd need a scheduler hacker to decipher the
> report and all of them seem to be missing at the moment (probably at
> OLS). Anyway, like I said, git bisect will probably speed up the
> debugging process, that's all.

Vacation.. but now I'm back ;-)

Even something simple as: perf top -r 1 (make sure you're root in order
to run with real-time prios) could give a clue as to what is consuming
all your cpu-time.

Or did the issue get sorted already?

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-08-03  9:05                         ` Peter Zijlstra
@ 2010-08-03  9:11                           ` Zeno Davatz
  2010-08-03  9:15                             ` damien.wyart
  0 siblings, 1 reply; 44+ messages in thread
From: Zeno Davatz @ 2010-08-03  9:11 UTC (permalink / raw)
  To: Peter Zijlstra
  Cc: Pekka Enberg, Damien Wyart, Catalin Marinas, linux-kernel,
	Andrew Morton, x86, mingo, yinghai

On Tue, Aug 3, 2010 at 11:05 AM, Peter Zijlstra <peterz@infradead.org> wrote:
> On Thu, 2010-07-15 at 23:52 +0300, Pekka Enberg wrote:
>> On Thu, Jul 15, 2010 at 11:00 PM, Damien Wyart <damien.wyart@free.fr> wrote:
>> >> > For now, I can't reproduce the problem with CONFIG_NO_BOOTMEM disabled ;
>> >> > with the option and rc5 the problem was happening quite quickly after
>> >> > boot and normal use of the machine. So it seems I can confirme what Zeno
>> >> > has seen and I hope this will give a hint to debug the problem. I guess
>> >> > this has not been reported that much because many testers might not have
>> >> > enabled CONFIG_NO_BOOTMEM... Maybe the scheduler folks could test their
>> >> > benchmark with a kernel having this option enabled?
>> >
>> > * Pekka Enberg <penberg@cs.helsinki.fi> [2010-07-15 22:50]:
>> >> To be honest, the bug is bit odd. It's related to boot-time memory
>> >> allocator changes but yet it seems to manifest itself as a scheduling
>> >> problem. So if you have some spare time and want to speed up the
>> >> debugging process, please test v2.6.34 and v2.6.35-rc1 with
>> >> CONFIG_NO_BOOTMEM and if former is good and latter is bad, try to see
>> >> if you can identify the offending commit with "git bisect."
>> >
>> > Not sure I will have enough time in the coming days (doing that remotely
>> > is fishy since ssh access is almost stuck when the problem occurs); if
>> > Zeno can and would like to do it, maybe this could be done faster.
>> >
>> > As the scheduler is now very well instrumented (many debugging features
>> > are available), reproducing the bug on a test platform (it happens quite
>> > quickly for me) might also give some hints. So testers, if you have
>> > time, please test 2.6.35-rc5 with CONFIG_NO_BOOTMEM on a Core i7 and see
>> > if you can reproduce the problem!
>>
>> Yeah, there's "perf sched" tool available for that:
>>
>>   http://lwn.net/Articles/353295/
>>
>> The only problem is that we'd need a scheduler hacker to decipher the
>> report and all of them seem to be missing at the moment (probably at
>> OLS). Anyway, like I said, git bisect will probably speed up the
>> debugging process, that's all.
>
> Vacation.. but now I'm back ;-)
>
> Even something simple as: perf top -r 1 (make sure you're root in order
> to run with real-time prios) could give a clue as to what is consuming
> all your cpu-time.
>
> Or did the issue get sorted already?

Thank you for the hint.

I am on 2.6.35 now and all seems to be fine again.

Best
Zeno

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-08-03  9:11                           ` Zeno Davatz
@ 2010-08-03  9:15                             ` damien.wyart
  2010-08-03  9:18                               ` Zeno Davatz
  2010-08-20  9:32                               ` Damien Wyart
  0 siblings, 2 replies; 44+ messages in thread
From: damien.wyart @ 2010-08-03  9:15 UTC (permalink / raw)
  To: Zeno Davatz
  Cc: Peter Zijlstra, Pekka Enberg, Damien Wyart, Catalin Marinas,
	linux-kernel, Andrew Morton, x86, mingo, yinghai

> > Vacation.. but now I'm back ;-)
> >
> > Even something simple as: perf top -r 1 (make sure you're root in order
> > to run with real-time prios) could give a clue as to what is consuming
> > all your cpu-time.
> >
> > Or did the issue get sorted already?
>
> Thank you for the hint.
>
> I am on 2.6.35 now and all seems to be fine again.

Are you 100% sure you compiled it with CONFIG_NO_BOOTMEM enabled?

I did not test 2.6.35 yet but I did not see anything related to this bug
commited since the discussion so I am very surprised the problem disappeared by
itself...

Will be on vacation very soon, so not sure I will have time to test 2.6.35
before leaving.

Damien

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-08-03  9:15                             ` damien.wyart
@ 2010-08-03  9:18                               ` Zeno Davatz
  2010-08-20  9:32                               ` Damien Wyart
  1 sibling, 0 replies; 44+ messages in thread
From: Zeno Davatz @ 2010-08-03  9:18 UTC (permalink / raw)
  To: damien.wyart
  Cc: Peter Zijlstra, Pekka Enberg, Catalin Marinas, linux-kernel,
	Andrew Morton, x86, mingo, yinghai

On Tue, Aug 3, 2010 at 11:15 AM,  <damien.wyart@free.fr> wrote:
>> > Vacation.. but now I'm back ;-)
>> >
>> > Even something simple as: perf top -r 1 (make sure you're root in order
>> > to run with real-time prios) could give a clue as to what is consuming
>> > all your cpu-time.
>> >
>> > Or did the issue get sorted already?
>>
>> Thank you for the hint.
>>
>> I am on 2.6.35 now and all seems to be fine again.
>
> Are you 100% sure you compiled it with CONFIG_NO_BOOTMEM enabled?
>
> I did not test 2.6.35 yet but I did not see anything related to this bug
> commited since the discussion so I am very surprised the problem disappeared by
> itself...
>
> Will be on vacation very soon, so not sure I will have time to test 2.6.35
> before leaving.

Yes: I got:

# CONFIG_PARAVIRT_SPINLOCKS is not set
CONFIG_PARAVIRT_CLOCK=y
# CONFIG_PARAVIRT_DEBUG is not set
CONFIG_NO_BOOTMEM=y
# CONFIG_MEMTEST is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set

in my .config.

Linux zenogentoo 2.6.35 #122 SMP Mon Aug 2 10:26:05 CEST 2010 i686
Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz GenuineIntel GNU/Linux

Best
Zeno

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-08-03  9:15                             ` damien.wyart
  2010-08-03  9:18                               ` Zeno Davatz
@ 2010-08-20  9:32                               ` Damien Wyart
  2010-08-20  9:40                                 ` Peter Zijlstra
  1 sibling, 1 reply; 44+ messages in thread
From: Damien Wyart @ 2010-08-20  9:32 UTC (permalink / raw)
  To: Zeno Davatz
  Cc: Peter Zijlstra, Pekka Enberg, Catalin Marinas, linux-kernel,
	Andrew Morton, x86, mingo, yinghai

Hi,

> > > Vacation.. but now I'm back ;-)

> > > Even something simple as: perf top -r 1 (make sure you're root in
> > > order to run with real-time prios) could give a clue as to what is
> > > consuming all your cpu-time.

> > > Or did the issue get sorted already?

> > Thank you for the hint.

> > I am on 2.6.35 now and all seems to be fine again.

> Are you 100% sure you compiled it with CONFIG_NO_BOOTMEM enabled?

> I did not test 2.6.35 yet but I did not see anything related to this
> bug commited since the discussion so I am very surprised the problem
> disappeared by itself...

> Will be on vacation very soon, so not sure I will have time to test 2.6.35
> before leaving.

After a few days of running 2.6.35.2 without problem, I got the same
huge slowness for a few tens of seconds yesterday. Did not have time to
run perf (and the system was almost unresponsive), but I will try to do
so if the problem occurs again. Anyway, even if less frequent than
during the -rcs, and as nothing had been commited to fix it before
final, the problem is still there...

It seems that the problem occurs after some CPU intensive tasks have
been run for some time (ie compiling a kernel) and only on Core i7
machines with NO_BOOTMEM. I am surprised so few people reported it and
that it has not been seen on test machines running CPU/scheduler
benchmark tools.

-- 
Damien Wyart

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-08-20  9:32                               ` Damien Wyart
@ 2010-08-20  9:40                                 ` Peter Zijlstra
  0 siblings, 0 replies; 44+ messages in thread
From: Peter Zijlstra @ 2010-08-20  9:40 UTC (permalink / raw)
  To: Damien Wyart
  Cc: Zeno Davatz, Pekka Enberg, Catalin Marinas, linux-kernel,
	Andrew Morton, x86, mingo, yinghai

On Fri, 2010-08-20 at 11:32 +0200, Damien Wyart wrote:

> After a few days of running 2.6.35.2 without problem, 

>  I am surprised so few people reported it and
> that it has not been seen on test machines running CPU/scheduler
> benchmark tools.
> 
My machines are lucky if a kernel has hours of runtime, days almost
never happens, there's always the next kernel to test ;-)

But yeah, you'd expect more people to run into something like this..

Most odd thing..

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-14  8:05 ` Pekka Enberg
  2010-07-14  8:27   ` Zeno Davatz
@ 2010-07-14  8:31   ` Damien Wyart
  2010-07-14  8:34     ` Zeno Davatz
  1 sibling, 1 reply; 44+ messages in thread
From: Damien Wyart @ 2010-07-14  8:31 UTC (permalink / raw)
  To: Pekka Enberg; +Cc: Zeno Davatz, linux-kernel, Catalin Marinas, Andrew Morton

Hi,

> On Wed, Jul 14, 2010 at 9:12 AM, Zeno Davatz <zdavatz@gmail.com> wrote:
> > I got a new Intel core-8 i7 processor.

> > I am on kernel uname -a

> > Linux zenogentoo 2.6.35-rc5 #97 SMP Tue Jul 13 16:13:25 CEST 2010 i686
> > Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz GenuineIntel GNU/Linux

> > Sometimes in the middle of nowhere all of a sudden all of my 8-cores
> > are at 100% CPU usage and my machine really lags and hangs and is not
> > useable anymore. Some random process just grabs a bunch CPUs according
> > to htop.

* Pekka Enberg <penberg@cs.helsinki.fi> [2010-07-14 11:05]:
> Why did you enable CONFIG_DEBUG_KMEMLEAK? Memory leak scanning is
> likely the source of these pauses.

I am seeing the same problem with a Core i7 920 and 2.6.35-rc5, and I do
not have CONFIG_DEBUG_KMEMLEAK enabled, so I think this is not related.

I do not see anything special in the logs, just the load becoming mad
and almost preventing ssh access. I've been seeing that since the first
2.6.35 rc I tested (-rc2 or -rc3, I don't remember) and I did not have
time to report it before but I was surprised nobody else did. No problem
with 2.6.34 and 2.6.34.1.

-- 
Damien

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-14  8:31   ` Damien Wyart
@ 2010-07-14  8:34     ` Zeno Davatz
  2010-07-14  8:38       ` Pekka Enberg
  0 siblings, 1 reply; 44+ messages in thread
From: Zeno Davatz @ 2010-07-14  8:34 UTC (permalink / raw)
  To: Damien Wyart; +Cc: Pekka Enberg, linux-kernel, Catalin Marinas, Andrew Morton

On Wed, Jul 14, 2010 at 10:31 AM, Damien Wyart <damien.wyart@free.fr> wrote:

>> On Wed, Jul 14, 2010 at 9:12 AM, Zeno Davatz <zdavatz@gmail.com> wrote:
>> > I got a new Intel core-8 i7 processor.
>
>> > I am on kernel uname -a
>
>> > Linux zenogentoo 2.6.35-rc5 #97 SMP Tue Jul 13 16:13:25 CEST 2010 i686
>> > Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz GenuineIntel GNU/Linux
>
>> > Sometimes in the middle of nowhere all of a sudden all of my 8-cores
>> > are at 100% CPU usage and my machine really lags and hangs and is not
>> > useable anymore. Some random process just grabs a bunch CPUs according
>> > to htop.
>
> * Pekka Enberg <penberg@cs.helsinki.fi> [2010-07-14 11:05]:
>> Why did you enable CONFIG_DEBUG_KMEMLEAK? Memory leak scanning is
>> likely the source of these pauses.
>
> I am seeing the same problem with a Core i7 920 and 2.6.35-rc5, and I do
> not have CONFIG_DEBUG_KMEMLEAK enabled, so I think this is not related.
>
> I do not see anything special in the logs, just the load becoming mad
> and almost preventing ssh access. I've been seeing that since the first
> 2.6.35 rc I tested (-rc2 or -rc3, I don't remember) and I did not have
> time to report it before but I was surprised nobody else did. No problem
> with 2.6.34 and 2.6.34.1.

same with me. My last build I tested was 2.6.34-rc7. No problems
there. No CPU jumps out of nowhere.

It is like any application all of a sudden use 400% CPU i.e. htop.

Best
Zeno

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-14  8:34     ` Zeno Davatz
@ 2010-07-14  8:38       ` Pekka Enberg
  2010-07-14  8:54         ` Zeno Davatz
  0 siblings, 1 reply; 44+ messages in thread
From: Pekka Enberg @ 2010-07-14  8:38 UTC (permalink / raw)
  To: Zeno Davatz, Mike Galbraith
  Cc: Damien Wyart, linux-kernel, Catalin Marinas, Andrew Morton, mingo,
	a.p.zijlstra

Zeno Davatz wrote:
> On Wed, Jul 14, 2010 at 10:31 AM, Damien Wyart <damien.wyart@free.fr> wrote:
> 
>>> On Wed, Jul 14, 2010 at 9:12 AM, Zeno Davatz <zdavatz@gmail.com> wrote:
>>>> I got a new Intel core-8 i7 processor.
>>>> I am on kernel uname -a
>>>> Linux zenogentoo 2.6.35-rc5 #97 SMP Tue Jul 13 16:13:25 CEST 2010 i686
>>>> Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz GenuineIntel GNU/Linux
>>>> Sometimes in the middle of nowhere all of a sudden all of my 8-cores
>>>> are at 100% CPU usage and my machine really lags and hangs and is not
>>>> useable anymore. Some random process just grabs a bunch CPUs according
>>>> to htop.
>> * Pekka Enberg <penberg@cs.helsinki.fi> [2010-07-14 11:05]:
>>> Why did you enable CONFIG_DEBUG_KMEMLEAK? Memory leak scanning is
>>> likely the source of these pauses.
>> I am seeing the same problem with a Core i7 920 and 2.6.35-rc5, and I do
>> not have CONFIG_DEBUG_KMEMLEAK enabled, so I think this is not related.
>>
>> I do not see anything special in the logs, just the load becoming mad
>> and almost preventing ssh access. I've been seeing that since the first
>> 2.6.35 rc I tested (-rc2 or -rc3, I don't remember) and I did not have
>> time to report it before but I was surprised nobody else did. No problem
>> with 2.6.34 and 2.6.34.1.
> 
> same with me. My last build I tested was 2.6.34-rc7. No problems
> there. No CPU jumps out of nowhere.
> 
> It is like any application all of a sudden use 400% CPU i.e. htop.

Interesting. Lets CC some scheduler folks for help.

			Pekka

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-14  8:38       ` Pekka Enberg
@ 2010-07-14  8:54         ` Zeno Davatz
  2010-07-14  8:57           ` Pekka Enberg
  0 siblings, 1 reply; 44+ messages in thread
From: Zeno Davatz @ 2010-07-14  8:54 UTC (permalink / raw)
  To: Pekka Enberg
  Cc: Mike Galbraith, Damien Wyart, linux-kernel, Catalin Marinas,
	Andrew Morton, mingo, a.p.zijlstra

On Wed, Jul 14, 2010 at 10:38 AM, Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> Zeno Davatz wrote:
>>
>> On Wed, Jul 14, 2010 at 10:31 AM, Damien Wyart <damien.wyart@free.fr>
>> wrote:
>>
>>>> On Wed, Jul 14, 2010 at 9:12 AM, Zeno Davatz <zdavatz@gmail.com> wrote:
>>>>>
>>>>> I got a new Intel core-8 i7 processor.
>>>>> I am on kernel uname -a
>>>>> Linux zenogentoo 2.6.35-rc5 #97 SMP Tue Jul 13 16:13:25 CEST 2010 i686
>>>>> Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz GenuineIntel GNU/Linux
>>>>> Sometimes in the middle of nowhere all of a sudden all of my 8-cores
>>>>> are at 100% CPU usage and my machine really lags and hangs and is not
>>>>> useable anymore. Some random process just grabs a bunch CPUs according
>>>>> to htop.
>>>
>>> * Pekka Enberg <penberg@cs.helsinki.fi> [2010-07-14 11:05]:
>>>>
>>>> Why did you enable CONFIG_DEBUG_KMEMLEAK? Memory leak scanning is
>>>> likely the source of these pauses.
>>>
>>> I am seeing the same problem with a Core i7 920 and 2.6.35-rc5, and I do
>>> not have CONFIG_DEBUG_KMEMLEAK enabled, so I think this is not related.
>>>
>>> I do not see anything special in the logs, just the load becoming mad
>>> and almost preventing ssh access. I've been seeing that since the first
>>> 2.6.35 rc I tested (-rc2 or -rc3, I don't remember) and I did not have
>>> time to report it before but I was surprised nobody else did. No problem
>>> with 2.6.34 and 2.6.34.1.
>>
>> same with me. My last build I tested was 2.6.34-rc7. No problems
>> there. No CPU jumps out of nowhere.
>>
>> It is like any application all of a sudden use 400% CPU i.e. htop.
>
> Interesting. Lets CC some scheduler folks for help.

Once it is gdm, once it is firefox-bin once it is htop. Its really od.
Nothing crashes one of those just uses lots of CPU. The machine just
gets really slow and then calms down again and everything is back to
normal.

;)

Maybe a bad temper?

Best
Zeno

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-14  8:54         ` Zeno Davatz
@ 2010-07-14  8:57           ` Pekka Enberg
  0 siblings, 0 replies; 44+ messages in thread
From: Pekka Enberg @ 2010-07-14  8:57 UTC (permalink / raw)
  To: Zeno Davatz
  Cc: Mike Galbraith, Damien Wyart, linux-kernel, Catalin Marinas,
	Andrew Morton, mingo, a.p.zijlstra

On Wed, Jul 14, 2010 at 11:54 AM, Zeno Davatz <zdavatz@gmail.com> wrote:
> On Wed, Jul 14, 2010 at 10:38 AM, Pekka Enberg <penberg@cs.helsinki.fi> wrote:
>> Zeno Davatz wrote:
>>>
>>> On Wed, Jul 14, 2010 at 10:31 AM, Damien Wyart <damien.wyart@free.fr>
>>> wrote:
>>>
>>>>> On Wed, Jul 14, 2010 at 9:12 AM, Zeno Davatz <zdavatz@gmail.com> wrote:
>>>>>>
>>>>>> I got a new Intel core-8 i7 processor.
>>>>>> I am on kernel uname -a
>>>>>> Linux zenogentoo 2.6.35-rc5 #97 SMP Tue Jul 13 16:13:25 CEST 2010 i686
>>>>>> Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz GenuineIntel GNU/Linux
>>>>>> Sometimes in the middle of nowhere all of a sudden all of my 8-cores
>>>>>> are at 100% CPU usage and my machine really lags and hangs and is not
>>>>>> useable anymore. Some random process just grabs a bunch CPUs according
>>>>>> to htop.
>>>>
>>>> * Pekka Enberg <penberg@cs.helsinki.fi> [2010-07-14 11:05]:
>>>>>
>>>>> Why did you enable CONFIG_DEBUG_KMEMLEAK? Memory leak scanning is
>>>>> likely the source of these pauses.
>>>>
>>>> I am seeing the same problem with a Core i7 920 and 2.6.35-rc5, and I do
>>>> not have CONFIG_DEBUG_KMEMLEAK enabled, so I think this is not related.
>>>>
>>>> I do not see anything special in the logs, just the load becoming mad
>>>> and almost preventing ssh access. I've been seeing that since the first
>>>> 2.6.35 rc I tested (-rc2 or -rc3, I don't remember) and I did not have
>>>> time to report it before but I was surprised nobody else did. No problem
>>>> with 2.6.34 and 2.6.34.1.
>>>
>>> same with me. My last build I tested was 2.6.34-rc7. No problems
>>> there. No CPU jumps out of nowhere.
>>>
>>> It is like any application all of a sudden use 400% CPU i.e. htop.
>>
>> Interesting. Lets CC some scheduler folks for help.
>
> Once it is gdm, once it is firefox-bin once it is htop. Its really od.
> Nothing crashes one of those just uses lots of CPU. The machine just
> gets really slow and then calms down again and everything is back to
> normal.

That's the part that makes me think it's scheduler and/or cpufreq related.

> ;)
>
> Maybe a bad temper?

Yeah, maybe Tux is having a bad day. :-)

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-14  6:12 kmemleak, cpu usage jump out of nowhere Zeno Davatz
  2010-07-14  8:05 ` Pekka Enberg
@ 2010-07-14  9:57 ` Catalin Marinas
  2010-07-14 10:04   ` Zeno Davatz
  1 sibling, 1 reply; 44+ messages in thread
From: Catalin Marinas @ 2010-07-14  9:57 UTC (permalink / raw)
  To: Zeno Davatz; +Cc: linux-kernel

Zeno Davatz <zdavatz@gmail.com> wrote:
> I got a new Intel core-8 i7 processor.
>
> I am on kernel uname -a
>
> Linux zenogentoo 2.6.35-rc5 #97 SMP Tue Jul 13 16:13:25 CEST 2010 i686
> Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz GenuineIntel GNU/Linux
>
> Sometimes in the middle of nowhere all of a sudden all of my 8-cores
> are at 100% CPU usage and my machine really lags and hangs and is not
> useable anymore. Some random process just grabs a bunch CPUs according
> to htop.
>
> dmesg tell me that
>
> kmemleak: 38 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
> kmemleak: 2 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
> kmemleak: 1 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
> kmemleak: 2 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
> kmemleak: 2 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
> kmemleak: 1 new suspected memory leaks (see /sys/kernel/debug/kmemleak)

These may be related to the NO_BOOTMEM configuration (I sent a patch in
a separate reply).

But even when kmemleak scans the memory, it only uses a single thread
and you should only see a single CPU going to 100%. I don't think
kmemleak scanning can explain why all the 8 cores are going up to 100%.

-- 
Catalin

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-14  9:57 ` Catalin Marinas
@ 2010-07-14 10:04   ` Zeno Davatz
  2010-07-14 11:54     ` Catalin Marinas
  0 siblings, 1 reply; 44+ messages in thread
From: Zeno Davatz @ 2010-07-14 10:04 UTC (permalink / raw)
  To: Catalin Marinas; +Cc: linux-kernel

Dear Catalin

On Wed, Jul 14, 2010 at 11:57 AM, Catalin Marinas
<catalin.marinas@arm.com> wrote:
> Zeno Davatz <zdavatz@gmail.com> wrote:
>> I got a new Intel core-8 i7 processor.
>>
>> I am on kernel uname -a
>>
>> Linux zenogentoo 2.6.35-rc5 #97 SMP Tue Jul 13 16:13:25 CEST 2010 i686
>> Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz GenuineIntel GNU/Linux
>>
>> Sometimes in the middle of nowhere all of a sudden all of my 8-cores
>> are at 100% CPU usage and my machine really lags and hangs and is not
>> useable anymore. Some random process just grabs a bunch CPUs according
>> to htop.
>>
>> dmesg tell me that
>>
>> kmemleak: 38 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
>> kmemleak: 2 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
>> kmemleak: 1 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
>> kmemleak: 2 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
>> kmemleak: 2 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
>> kmemleak: 1 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
>
> These may be related to the NO_BOOTMEM configuration (I sent a patch in
> a separate reply).
>
> But even when kmemleak scans the memory, it only uses a single thread
> and you should only see a single CPU going to 100%. I don't think
> kmemleak scanning can explain why all the 8 cores are going up to 100%.

I am doing:

/usr/src/my2.6> sudo patch -p1 < patch_catalin
patching file mm/bootmem.c
Hunk #1 FAILED at 435.
Hunk #2 FAILED at 461.
2 out of 2 hunks FAILED -- saving rejects to file mm/bootmem.c.rej
patching file mm/page_alloc.c
Hunk #1 FAILED at 3659.
1 out of 1 hunk FAILED -- saving rejects to file mm/page_alloc.c.rej

Any hints why it wont apply? Will this patch be in the next RC?

Best
Zeno

^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-14 10:04   ` Zeno Davatz
@ 2010-07-14 11:54     ` Catalin Marinas
  2010-07-14 11:59       ` Zeno Davatz
  0 siblings, 1 reply; 44+ messages in thread
From: Catalin Marinas @ 2010-07-14 11:54 UTC (permalink / raw)
  To: Zeno Davatz; +Cc: linux-kernel

On Wed, 2010-07-14 at 11:04 +0100, Zeno Davatz wrote:
> On Wed, Jul 14, 2010 at 11:57 AM, Catalin Marinas
> <catalin.marinas@arm.com> wrote:
> > Zeno Davatz <zdavatz@gmail.com> wrote:
> >> Sometimes in the middle of nowhere all of a sudden all of my 8-cores
> >> are at 100% CPU usage and my machine really lags and hangs and is not
> >> useable anymore. Some random process just grabs a bunch CPUs according
> >> to htop.
> >
> > These may be related to the NO_BOOTMEM configuration (I sent a patch in
> > a separate reply).
> >
> > But even when kmemleak scans the memory, it only uses a single thread
> > and you should only see a single CPU going to 100%. I don't think
> > kmemleak scanning can explain why all the 8 cores are going up to 100%.
> 
> I am doing:
> 
> /usr/src/my2.6> sudo patch -p1 < patch_catalin
> patching file mm/bootmem.c
> Hunk #1 FAILED at 435.
> Hunk #2 FAILED at 461.
> 2 out of 2 hunks FAILED -- saving rejects to file mm/bootmem.c.rej
> patching file mm/page_alloc.c
> Hunk #1 FAILED at 3659.
> 1 out of 1 hunk FAILED -- saving rejects to file mm/page_alloc.c.rej
> 
> Any hints why it wont apply? Will this patch be in the next RC?

The patch is against 2.6.35-rc4. I'll send it to Linus and hopefully it
will get merged during rc.

BTW, you can disable kmemleak scanning by doing:

# echo scan=off > /sys/kernel/debug/kmemleak

Do you still get that high CPU usage?

-- 
Catalin


^ permalink raw reply	[flat|nested] 44+ messages in thread

* Re: kmemleak, cpu usage jump out of nowhere
  2010-07-14 11:54     ` Catalin Marinas
@ 2010-07-14 11:59       ` Zeno Davatz
  0 siblings, 0 replies; 44+ messages in thread
From: Zeno Davatz @ 2010-07-14 11:59 UTC (permalink / raw)
  To: Catalin Marinas; +Cc: linux-kernel

On Wed, Jul 14, 2010 at 1:54 PM, Catalin Marinas
<catalin.marinas@arm.com> wrote:
> On Wed, 2010-07-14 at 11:04 +0100, Zeno Davatz wrote:
>> On Wed, Jul 14, 2010 at 11:57 AM, Catalin Marinas
>> <catalin.marinas@arm.com> wrote:
>> > Zeno Davatz <zdavatz@gmail.com> wrote:
>> >> Sometimes in the middle of nowhere all of a sudden all of my 8-cores
>> >> are at 100% CPU usage and my machine really lags and hangs and is not
>> >> useable anymore. Some random process just grabs a bunch CPUs according
>> >> to htop.
>> >
>> > These may be related to the NO_BOOTMEM configuration (I sent a patch in
>> > a separate reply).
>> >
>> > But even when kmemleak scans the memory, it only uses a single thread
>> > and you should only see a single CPU going to 100%. I don't think
>> > kmemleak scanning can explain why all the 8 cores are going up to 100%.
>>
>> I am doing:
>>
>> /usr/src/my2.6> sudo patch -p1 < patch_catalin
>> patching file mm/bootmem.c
>> Hunk #1 FAILED at 435.
>> Hunk #2 FAILED at 461.
>> 2 out of 2 hunks FAILED -- saving rejects to file mm/bootmem.c.rej
>> patching file mm/page_alloc.c
>> Hunk #1 FAILED at 3659.
>> 1 out of 1 hunk FAILED -- saving rejects to file mm/page_alloc.c.rej
>>
>> Any hints why it wont apply? Will this patch be in the next RC?
>
> The patch is against 2.6.35-rc4. I'll send it to Linus and hopefully it
> will get merged during rc.
>
> BTW, you can disable kmemleak scanning by doing:
>
> # echo scan=off > /sys/kernel/debug/kmemleak

Thank you for the hint!

> Do you still get that high CPU usage?

Not at the moment. I disabled

CONFIG_NO_BOOTMEM:

and rebooted onto the new bzImage. No "CPU-bad-mood" at the moment.

Best
Zeno

^ permalink raw reply	[flat|nested] 44+ messages in thread

end of thread, other threads:[~2010-08-20  9:40 UTC | newest]

Thread overview: 44+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-07-14  6:12 kmemleak, cpu usage jump out of nowhere Zeno Davatz
2010-07-14  8:05 ` Pekka Enberg
2010-07-14  8:27   ` Zeno Davatz
2010-07-14  9:47     ` Catalin Marinas
2010-07-14  9:55       ` Pekka Enberg
2010-07-14 10:00         ` Zeno Davatz
2010-07-15 14:58         ` Catalin Marinas
2010-07-15 15:15           ` Zeno Davatz
2010-07-15 15:54             ` Pekka Enberg
2010-07-15 16:28               ` Damien Wyart
2010-07-15 19:16                 ` Damien Wyart
2010-07-15 19:50                   ` Pekka Enberg
2010-07-15 20:00                     ` Damien Wyart
2010-07-15 20:38                       ` Zeno Davatz
2010-07-15 20:50                         ` Pekka Enberg
2010-07-15 20:57                           ` Zeno Davatz
2010-07-16  7:12                           ` Zeno Davatz
2010-07-16  7:29                           ` Zeno Davatz
2010-07-16  7:37                           ` Zeno Davatz
2010-07-16  7:50                             ` Pekka Enberg
2010-07-16  9:17                               ` Zeno Davatz
2010-07-16  9:32                                 ` Pekka Enberg
2010-07-16  9:42                                   ` Zeno Davatz
2010-07-16  9:47                                   ` Zeno Davatz
2010-07-16 18:27                                     ` Yinghai Lu
2010-07-16 20:29                                       ` Zeno Davatz
2010-07-16 20:59                                         ` Yinghai Lu
2010-07-17  8:46                                           ` Zeno Davatz
2010-07-15 20:52                       ` Pekka Enberg
2010-08-03  9:05                         ` Peter Zijlstra
2010-08-03  9:11                           ` Zeno Davatz
2010-08-03  9:15                             ` damien.wyart
2010-08-03  9:18                               ` Zeno Davatz
2010-08-20  9:32                               ` Damien Wyart
2010-08-20  9:40                                 ` Peter Zijlstra
2010-07-14  8:31   ` Damien Wyart
2010-07-14  8:34     ` Zeno Davatz
2010-07-14  8:38       ` Pekka Enberg
2010-07-14  8:54         ` Zeno Davatz
2010-07-14  8:57           ` Pekka Enberg
2010-07-14  9:57 ` Catalin Marinas
2010-07-14 10:04   ` Zeno Davatz
2010-07-14 11:54     ` Catalin Marinas
2010-07-14 11:59       ` Zeno Davatz

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox