* memleaks, acpi + ext4 + tty
@ 2009-08-28 5:25 Luis R. Rodriguez
2009-08-28 16:32 ` Catalin Marinas
0 siblings, 1 reply; 26+ messages in thread
From: Luis R. Rodriguez @ 2009-08-28 5:25 UTC (permalink / raw)
To: linux-kernel
I have an assorted collection of kmemleak reports for acpi, ext4 and
tty, not sure how to read these yet to fix so figure I'd at least post
them. To reproduce I can just dd=/dev/zero to some big file and played
some video.
unreferenced object 0xffff88003e0015c0 (size 64):
comm "swapper", pid 1, jiffies 4294892352
backtrace:
[<ffffffff81121fad>] create_object+0x13d/0x2d0
[<ffffffff81122265>] kmemleak_alloc+0x25/0x60
[<ffffffff81118a03>] kmem_cache_alloc_node+0x193/0x200
[<ffffffff8152509e>] process_zones+0x70/0x1cd
[<ffffffff81525230>] pageset_cpuup_callback+0x35/0x92
[<ffffffff8152c9b7>] notifier_call_chain+0x47/0x90
[<ffffffff81078549>] __raw_notifier_call_chain+0x9/0x10
[<ffffffff81523f25>] _cpu_up+0x75/0x130
[<ffffffff8152403a>] cpu_up+0x5a/0x6a
[<ffffffff8181969e>] kernel_init+0xcc/0x1ba
[<ffffffff810130ca>] child_rip+0xa/0x20
[<ffffffffffffffff>] 0xffffffffffffffff
unreferenced object 0xffff88003cb5f700 (size 64):
comm "swapper", pid 1, jiffies 4294892459
backtrace:
[<ffffffff81121fad>] create_object+0x13d/0x2d0
[<ffffffff81122265>] kmemleak_alloc+0x25/0x60
[<ffffffff81119f3b>] __kmalloc+0x16b/0x250
[<ffffffff812bb549>] kzalloc+0xf/0x11
[<ffffffff812bbb53>] acpi_add_single_object+0x58e/0xd3c
[<ffffffff812bc51c>] acpi_bus_scan+0x125/0x1af
[<ffffffff81842361>] acpi_scan_init+0xc8/0xe9
[<ffffffff8184211c>] acpi_init+0x21f/0x265
[<ffffffff8100a05b>] do_one_initcall+0x4b/0x1b0
[<ffffffff81819736>] kernel_init+0x164/0x1ba
[<ffffffff810130ca>] child_rip+0xa/0x20
[<ffffffffffffffff>] 0xffffffffffffffff
unreferenced object 0xffff88003cb5f740 (size 64):
comm "swapper", pid 1, jiffies 4294892460
backtrace:
[<ffffffff81121fad>] create_object+0x13d/0x2d0
[<ffffffff81122265>] kmemleak_alloc+0x25/0x60
[<ffffffff81119f3b>] __kmalloc+0x16b/0x250
[<ffffffff812bb549>] kzalloc+0xf/0x11
[<ffffffff812bbb53>] acpi_add_single_object+0x58e/0xd3c
[<ffffffff812bc51c>] acpi_bus_scan+0x125/0x1af
[<ffffffff81842361>] acpi_scan_init+0xc8/0xe9
[<ffffffff8184211c>] acpi_init+0x21f/0x265
[<ffffffff8100a05b>] do_one_initcall+0x4b/0x1b0
[<ffffffff81819736>] kernel_init+0x164/0x1ba
[<ffffffff810130ca>] child_rip+0xa/0x20
[<ffffffffffffffff>] 0xffffffffffffffff
unreferenced object 0xffff88003cb5f780 (size 64):
comm "swapper", pid 1, jiffies 4294892463
backtrace:
[<ffffffff81121fad>] create_object+0x13d/0x2d0
[<ffffffff81122265>] kmemleak_alloc+0x25/0x60
[<ffffffff81119f3b>] __kmalloc+0x16b/0x250
[<ffffffff812bb549>] kzalloc+0xf/0x11
[<ffffffff812bbb53>] acpi_add_single_object+0x58e/0xd3c
[<ffffffff812bc51c>] acpi_bus_scan+0x125/0x1af
[<ffffffff81842361>] acpi_scan_init+0xc8/0xe9
[<ffffffff8184211c>] acpi_init+0x21f/0x265
[<ffffffff8100a05b>] do_one_initcall+0x4b/0x1b0
[<ffffffff81819736>] kernel_init+0x164/0x1ba
[<ffffffff810130ca>] child_rip+0xa/0x20
[<ffffffffffffffff>] 0xffffffffffffffff
unreferenced object 0xffff88003cb5f7c0 (size 64):
comm "swapper", pid 1, jiffies 4294892465
backtrace:
[<ffffffff81121fad>] create_object+0x13d/0x2d0
[<ffffffff81122265>] kmemleak_alloc+0x25/0x60
[<ffffffff81119f3b>] __kmalloc+0x16b/0x250
[<ffffffff812bb549>] kzalloc+0xf/0x11
[<ffffffff812bbb53>] acpi_add_single_object+0x58e/0xd3c
[<ffffffff812bc51c>] acpi_bus_scan+0x125/0x1af
[<ffffffff81842361>] acpi_scan_init+0xc8/0xe9
[<ffffffff8184211c>] acpi_init+0x21f/0x265
[<ffffffff8100a05b>] do_one_initcall+0x4b/0x1b0
[<ffffffff81819736>] kernel_init+0x164/0x1ba
[<ffffffff810130ca>] child_rip+0xa/0x20
[<ffffffffffffffff>] 0xffffffffffffffff
unreferenced object 0xffff88002e93da80 (size 192):
comm "swapper", pid 1, jiffies 4294892831
backtrace:
[<ffffffff81121fad>] create_object+0x13d/0x2d0
[<ffffffff81122265>] kmemleak_alloc+0x25/0x60
[<ffffffff81119f3b>] __kmalloc+0x16b/0x250
[<ffffffff812e0f82>] acpi_processor_register_performance+0x2ad/0x3eb
[<ffffffff8102438d>] acpi_cpufreq_cpu_init+0xad/0x520
[<ffffffff81425b25>] cpufreq_add_dev+0x175/0x720
[<ffffffff81325fd6>] sysdev_driver_register+0xa6/0x130
[<ffffffff81424b10>] cpufreq_register_driver+0x80/0x170
[<ffffffff81823596>] acpi_cpufreq_init+0x92/0xc9
[<ffffffff8100a05b>] do_one_initcall+0x4b/0x1b0
[<ffffffff81819736>] kernel_init+0x164/0x1ba
[<ffffffff810130ca>] child_rip+0xa/0x20
[<ffffffffffffffff>] 0xffffffffffffffff
unreferenced object 0xffff88002e93df00 (size 192):
comm "swapper", pid 1, jiffies 4294892832
backtrace:
[<ffffffff81121fad>] create_object+0x13d/0x2d0
[<ffffffff81122265>] kmemleak_alloc+0x25/0x60
[<ffffffff81119f3b>] __kmalloc+0x16b/0x250
[<ffffffff812e0f82>] acpi_processor_register_performance+0x2ad/0x3eb
[<ffffffff8102438d>] acpi_cpufreq_cpu_init+0xad/0x520
[<ffffffff81425b25>] cpufreq_add_dev+0x175/0x720
[<ffffffff81325fd6>] sysdev_driver_register+0xa6/0x130
[<ffffffff81424b10>] cpufreq_register_driver+0x80/0x170
[<ffffffff81823596>] acpi_cpufreq_init+0x92/0xc9
[<ffffffff8100a05b>] do_one_initcall+0x4b/0x1b0
[<ffffffff81819736>] kernel_init+0x164/0x1ba
[<ffffffff810130ca>] child_rip+0xa/0x20
[<ffffffffffffffff>] 0xffffffffffffffff
unreferenced object 0xffff880039571800 (size 1024):
comm "exe", pid 1168, jiffies 4294893410
backtrace:
[<ffffffff81121fad>] create_object+0x13d/0x2d0
[<ffffffff81122265>] kmemleak_alloc+0x25/0x60
[<ffffffff81119f3b>] __kmalloc+0x16b/0x250
[<ffffffff811e1d71>] ext4_mb_init+0x1a1/0x590
[<ffffffff811d2da3>] ext4_fill_super+0x1df3/0x26c0
[<ffffffff8112774f>] get_sb_bdev+0x16f/0x1b0
[<ffffffff811c8fd3>] ext4_get_sb+0x13/0x20
[<ffffffff81127216>] vfs_kern_mount+0x76/0x180
[<ffffffff8112738d>] do_kern_mount+0x4d/0x130
[<ffffffff8113fc57>] do_mount+0x307/0x8b0
[<ffffffff8114028f>] sys_mount+0x8f/0xe0
[<ffffffff81011f02>] system_call_fastpath+0x16/0x1b
[<ffffffffffffffff>] 0xffffffffffffffff
unreferenced object 0xffff880039571400 (size 1024):
comm "exe", pid 1168, jiffies 4294893410
backtrace:
[<ffffffff81121fad>] create_object+0x13d/0x2d0
[<ffffffff81122265>] kmemleak_alloc+0x25/0x60
[<ffffffff81119f3b>] __kmalloc+0x16b/0x250
[<ffffffff811e1d71>] ext4_mb_init+0x1a1/0x590
[<ffffffff811d2da3>] ext4_fill_super+0x1df3/0x26c0
[<ffffffff8112774f>] get_sb_bdev+0x16f/0x1b0
[<ffffffff811c8fd3>] ext4_get_sb+0x13/0x20
[<ffffffff81127216>] vfs_kern_mount+0x76/0x180
[<ffffffff8112738d>] do_kern_mount+0x4d/0x130
[<ffffffff8113fc57>] do_mount+0x307/0x8b0
[<ffffffff8114028f>] sys_mount+0x8f/0xe0
[<ffffffff81011f02>] system_call_fastpath+0x16/0x1b
[<ffffffffffffffff>] 0xffffffffffffffff
unreferenced object 0xffff880039570800 (size 1024):
comm "exe", pid 1168, jiffies 4294893410
backtrace:
[<ffffffff81121fad>] create_object+0x13d/0x2d0
[<ffffffff81122265>] kmemleak_alloc+0x25/0x60
[<ffffffff81119f3b>] __kmalloc+0x16b/0x250
[<ffffffff811e1d71>] ext4_mb_init+0x1a1/0x590
[<ffffffff811d2da3>] ext4_fill_super+0x1df3/0x26c0
[<ffffffff8112774f>] get_sb_bdev+0x16f/0x1b0
[<ffffffff811c8fd3>] ext4_get_sb+0x13/0x20
[<ffffffff81127216>] vfs_kern_mount+0x76/0x180
[<ffffffff8112738d>] do_kern_mount+0x4d/0x130
[<ffffffff8113fc57>] do_mount+0x307/0x8b0
[<ffffffff8114028f>] sys_mount+0x8f/0xe0
[<ffffffff81011f02>] system_call_fastpath+0x16/0x1b
[<ffffffffffffffff>] 0xffffffffffffffff
unreferenced object 0xffff880039572000 (size 1024):
comm "exe", pid 1168, jiffies 4294893410
backtrace:
[<ffffffff81121fad>] create_object+0x13d/0x2d0
[<ffffffff81122265>] kmemleak_alloc+0x25/0x60
[<ffffffff81119f3b>] __kmalloc+0x16b/0x250
[<ffffffff811e1d71>] ext4_mb_init+0x1a1/0x590
[<ffffffff811d2da3>] ext4_fill_super+0x1df3/0x26c0
[<ffffffff8112774f>] get_sb_bdev+0x16f/0x1b0
[<ffffffff811c8fd3>] ext4_get_sb+0x13/0x20
[<ffffffff81127216>] vfs_kern_mount+0x76/0x180
[<ffffffff8112738d>] do_kern_mount+0x4d/0x130
[<ffffffff8113fc57>] do_mount+0x307/0x8b0
[<ffffffff8114028f>] sys_mount+0x8f/0xe0
[<ffffffff81011f02>] system_call_fastpath+0x16/0x1b
[<ffffffffffffffff>] 0xffffffffffffffff
unreferenced object 0xffff880039573c00 (size 1024):
comm "exe", pid 1168, jiffies 4294893410
backtrace:
[<ffffffff81121fad>] create_object+0x13d/0x2d0
[<ffffffff81122265>] kmemleak_alloc+0x25/0x60
[<ffffffff81119f3b>] __kmalloc+0x16b/0x250
[<ffffffff811e1d71>] ext4_mb_init+0x1a1/0x590
[<ffffffff811d2da3>] ext4_fill_super+0x1df3/0x26c0
[<ffffffff8112774f>] get_sb_bdev+0x16f/0x1b0
[<ffffffff811c8fd3>] ext4_get_sb+0x13/0x20
[<ffffffff81127216>] vfs_kern_mount+0x76/0x180
[<ffffffff8112738d>] do_kern_mount+0x4d/0x130
[<ffffffff8113fc57>] do_mount+0x307/0x8b0
[<ffffffff8114028f>] sys_mount+0x8f/0xe0
[<ffffffff81011f02>] system_call_fastpath+0x16/0x1b
[<ffffffffffffffff>] 0xffffffffffffffff
unreferenced object 0xffff880039572800 (size 1024):
comm "exe", pid 1168, jiffies 4294893410
backtrace:
[<ffffffff81121fad>] create_object+0x13d/0x2d0
[<ffffffff81122265>] kmemleak_alloc+0x25/0x60
[<ffffffff81119f3b>] __kmalloc+0x16b/0x250
[<ffffffff811e1d71>] ext4_mb_init+0x1a1/0x590
[<ffffffff811d2da3>] ext4_fill_super+0x1df3/0x26c0
[<ffffffff8112774f>] get_sb_bdev+0x16f/0x1b0
[<ffffffff811c8fd3>] ext4_get_sb+0x13/0x20
[<ffffffff81127216>] vfs_kern_mount+0x76/0x180
[<ffffffff8112738d>] do_kern_mount+0x4d/0x130
[<ffffffff8113fc57>] do_mount+0x307/0x8b0
[<ffffffff8114028f>] sys_mount+0x8f/0xe0
[<ffffffff81011f02>] system_call_fastpath+0x16/0x1b
[<ffffffffffffffff>] 0xffffffffffffffff
unreferenced object 0xffff880006ce0400 (size 1024):
comm "mplayer", pid 5293, jiffies 4295366945
backtrace:
[<ffffffff81121fad>] create_object+0x13d/0x2d0
[<ffffffff81122265>] kmemleak_alloc+0x25/0x60
[<ffffffff81119f3b>] __kmalloc+0x16b/0x250
[<ffffffff813021b0>] tty_buffer_request_room+0xc0/0x190
[<ffffffff8130244c>] tty_insert_flip_string+0x3c/0xb0
[<ffffffff81302f49>] pty_write+0x49/0x70
[<ffffffff812fd3b0>] n_tty_write+0x1c0/0x450
[<ffffffff812f9ec1>] tty_write+0x1a1/0x290
[<ffffffff81124518>] vfs_write+0xb8/0x1a0
[<ffffffff81124fcc>] sys_write+0x4c/0x80
[<ffffffff81011f02>] system_call_fastpath+0x16/0x1b
[<ffffffffffffffff>] 0xffffffffffffffff
unreferenced object 0xffff880006ce1800 (size 1024):
comm "mplayer", pid 5293, jiffies 4295366970
backtrace:
[<ffffffff81121fad>] create_object+0x13d/0x2d0
[<ffffffff81122265>] kmemleak_alloc+0x25/0x60
[<ffffffff81119f3b>] __kmalloc+0x16b/0x250
[<ffffffff813021b0>] tty_buffer_request_room+0xc0/0x190
[<ffffffff8130244c>] tty_insert_flip_string+0x3c/0xb0
[<ffffffff81302f49>] pty_write+0x49/0x70
[<ffffffff812fd3b0>] n_tty_write+0x1c0/0x450
[<ffffffff812f9ec1>] tty_write+0x1a1/0x290
[<ffffffff81124518>] vfs_write+0xb8/0x1a0
[<ffffffff81124fcc>] sys_write+0x4c/0x80
[<ffffffff81011f02>] system_call_fastpath+0x16/0x1b
[<ffffffffffffffff>] 0xffffffffffffffff
unreferenced object 0xffff880006ce1400 (size 1024):
comm "mplayer", pid 5293, jiffies 4295367045
backtrace:
[<ffffffff81121fad>] create_object+0x13d/0x2d0
[<ffffffff81122265>] kmemleak_alloc+0x25/0x60
[<ffffffff81119f3b>] __kmalloc+0x16b/0x250
[<ffffffff813021b0>] tty_buffer_request_room+0xc0/0x190
[<ffffffff8130244c>] tty_insert_flip_string+0x3c/0xb0
[<ffffffff81302f49>] pty_write+0x49/0x70
[<ffffffff812fd3b0>] n_tty_write+0x1c0/0x450
[<ffffffff812f9ec1>] tty_write+0x1a1/0x290
[<ffffffff81124518>] vfs_write+0xb8/0x1a0
[<ffffffff81124fcc>] sys_write+0x4c/0x80
[<ffffffff81011f02>] system_call_fastpath+0x16/0x1b
[<ffffffffffffffff>] 0xffffffffffffffff
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: memleaks, acpi + ext4 + tty
2009-08-28 5:25 memleaks, acpi + ext4 + tty Luis R. Rodriguez
@ 2009-08-28 16:32 ` Catalin Marinas
2009-08-28 16:52 ` Luis R. Rodriguez
2009-08-30 16:34 ` Aneesh Kumar K.V
0 siblings, 2 replies; 26+ messages in thread
From: Catalin Marinas @ 2009-08-28 16:32 UTC (permalink / raw)
To: Luis R. Rodriguez; +Cc: linux-kernel, Aneesh Kumar K.V, Greg Kroah-Hartman
"Luis R. Rodriguez" <mcgrof@gmail.com> wrote:
> I have an assorted collection of kmemleak reports for acpi, ext4 and
> tty, not sure how to read these yet to fix so figure I'd at least post
> them. To reproduce I can just dd=/dev/zero to some big file and played
> some video.
If you do a few echo scan > /sys/kernel/debug/kmemleak, do they
disappear (i.e. transient false positives)?
Which kernel version is this?
> unreferenced object 0xffff88003e0015c0 (size 64):
> comm "swapper", pid 1, jiffies 4294892352
> backtrace:
> [<ffffffff81121fad>] create_object+0x13d/0x2d0
> [<ffffffff81122265>] kmemleak_alloc+0x25/0x60
> [<ffffffff81118a03>] kmem_cache_alloc_node+0x193/0x200
> [<ffffffff8152509e>] process_zones+0x70/0x1cd
> [<ffffffff81525230>] pageset_cpuup_callback+0x35/0x92
> [<ffffffff8152c9b7>] notifier_call_chain+0x47/0x90
> [<ffffffff81078549>] __raw_notifier_call_chain+0x9/0x10
> [<ffffffff81523f25>] _cpu_up+0x75/0x130
> [<ffffffff8152403a>] cpu_up+0x5a/0x6a
> [<ffffffff8181969e>] kernel_init+0xcc/0x1ba
> [<ffffffff810130ca>] child_rip+0xa/0x20
> [<ffffffffffffffff>] 0xffffffffffffffff
Can't really tell. Maybe a false positive caused by kmemleak not
scanning the pgdata node_zones. Can you post your .config file?
> unreferenced object 0xffff88003cb5f700 (size 64):
> comm "swapper", pid 1, jiffies 4294892459
> backtrace:
> [<ffffffff81121fad>] create_object+0x13d/0x2d0
> [<ffffffff81122265>] kmemleak_alloc+0x25/0x60
> [<ffffffff81119f3b>] __kmalloc+0x16b/0x250
> [<ffffffff812bb549>] kzalloc+0xf/0x11
> [<ffffffff812bbb53>] acpi_add_single_object+0x58e/0xd3c
> [<ffffffff812bc51c>] acpi_bus_scan+0x125/0x1af
> [<ffffffff81842361>] acpi_scan_init+0xc8/0xe9
> [<ffffffff8184211c>] acpi_init+0x21f/0x265
> [<ffffffff8100a05b>] do_one_initcall+0x4b/0x1b0
> [<ffffffff81819736>] kernel_init+0x164/0x1ba
> [<ffffffff810130ca>] child_rip+0xa/0x20
> [<ffffffffffffffff>] 0xffffffffffffffff
I get ACPI reports as well and they may be real leaks. However, I
didn't have time to analyse the code (pretty complicated reference
counting).
> unreferenced object 0xffff880039571800 (size 1024):
> comm "exe", pid 1168, jiffies 4294893410
> backtrace:
> [<ffffffff81121fad>] create_object+0x13d/0x2d0
> [<ffffffff81122265>] kmemleak_alloc+0x25/0x60
> [<ffffffff81119f3b>] __kmalloc+0x16b/0x250
> [<ffffffff811e1d71>] ext4_mb_init+0x1a1/0x590
> [<ffffffff811d2da3>] ext4_fill_super+0x1df3/0x26c0
> [<ffffffff8112774f>] get_sb_bdev+0x16f/0x1b0
> [<ffffffff811c8fd3>] ext4_get_sb+0x13/0x20
> [<ffffffff81127216>] vfs_kern_mount+0x76/0x180
> [<ffffffff8112738d>] do_kern_mount+0x4d/0x130
> [<ffffffff8113fc57>] do_mount+0x307/0x8b0
> [<ffffffff8114028f>] sys_mount+0x8f/0xe0
> [<ffffffff81011f02>] system_call_fastpath+0x16/0x1b
> [<ffffffffffffffff>] 0xffffffffffffffff
The ext4 reports are real leaks and patch was posted here -
http://lkml.org/lkml/2009/7/15/62. However, it hasn't been merged into
mainline yet (I cc'ed Aneesh).
The patch is merged in my "kmemleak-fixes" branch on
git://linux-arm.org/linux-2.6.git.
> unreferenced object 0xffff880006ce0400 (size 1024):
> comm "mplayer", pid 5293, jiffies 4295366945
> backtrace:
> [<ffffffff81121fad>] create_object+0x13d/0x2d0
> [<ffffffff81122265>] kmemleak_alloc+0x25/0x60
> [<ffffffff81119f3b>] __kmalloc+0x16b/0x250
> [<ffffffff813021b0>] tty_buffer_request_room+0xc0/0x190
> [<ffffffff8130244c>] tty_insert_flip_string+0x3c/0xb0
> [<ffffffff81302f49>] pty_write+0x49/0x70
> [<ffffffff812fd3b0>] n_tty_write+0x1c0/0x450
> [<ffffffff812f9ec1>] tty_write+0x1a1/0x290
> [<ffffffff81124518>] vfs_write+0xb8/0x1a0
> [<ffffffff81124fcc>] sys_write+0x4c/0x80
> [<ffffffff81011f02>] system_call_fastpath+0x16/0x1b
> [<ffffffffffffffff>] 0xffffffffffffffff
It could be a real leak as you get several of these. I cc'ed Greg KH
for any suggestions he may have. It looks like it only happens when
running mplayer.
Thanks.
--
Catalin
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: memleaks, acpi + ext4 + tty
2009-08-28 16:32 ` Catalin Marinas
@ 2009-08-28 16:52 ` Luis R. Rodriguez
2009-08-28 21:50 ` Luis R. Rodriguez
2009-08-29 21:41 ` Catalin Marinas
2009-08-30 16:34 ` Aneesh Kumar K.V
1 sibling, 2 replies; 26+ messages in thread
From: Luis R. Rodriguez @ 2009-08-28 16:52 UTC (permalink / raw)
To: Catalin Marinas; +Cc: linux-kernel, Aneesh Kumar K.V, Greg Kroah-Hartman
[-- Attachment #1: Type: text/plain, Size: 4938 bytes --]
On Fri, Aug 28, 2009 at 9:32 AM, Catalin Marinas<catalin.marinas@arm.com> wrote:
> "Luis R. Rodriguez" <mcgrof@gmail.com> wrote:
>> I have an assorted collection of kmemleak reports for acpi, ext4 and
>> tty, not sure how to read these yet to fix so figure I'd at least post
>> them. To reproduce I can just dd=/dev/zero to some big file and played
>> some video.
>
> If you do a few echo scan > /sys/kernel/debug/kmemleak, do they
> disappear (i.e. transient false positives)?
Sure, I will once on rc8.
> Which kernel version is this?
v2.6.31-rc7-33172-gf4a9f9a
This is from wireless-testing, which has wireless patches on top of
rc7. John just rebased to rc8 so will give that a shot at work.
>> unreferenced object 0xffff88003e0015c0 (size 64):
>> comm "swapper", pid 1, jiffies 4294892352
>> backtrace:
>> [<ffffffff81121fad>] create_object+0x13d/0x2d0
>> [<ffffffff81122265>] kmemleak_alloc+0x25/0x60
>> [<ffffffff81118a03>] kmem_cache_alloc_node+0x193/0x200
>> [<ffffffff8152509e>] process_zones+0x70/0x1cd
>> [<ffffffff81525230>] pageset_cpuup_callback+0x35/0x92
>> [<ffffffff8152c9b7>] notifier_call_chain+0x47/0x90
>> [<ffffffff81078549>] __raw_notifier_call_chain+0x9/0x10
>> [<ffffffff81523f25>] _cpu_up+0x75/0x130
>> [<ffffffff8152403a>] cpu_up+0x5a/0x6a
>> [<ffffffff8181969e>] kernel_init+0xcc/0x1ba
>> [<ffffffff810130ca>] child_rip+0xa/0x20
>> [<ffffffffffffffff>] 0xffffffffffffffff
>
> Can't really tell. Maybe a false positive caused by kmemleak not
> scanning the pgdata node_zones. Can you post your .config file?
Sure, attached.
>> unreferenced object 0xffff88003cb5f700 (size 64):
>> comm "swapper", pid 1, jiffies 4294892459
>> backtrace:
>> [<ffffffff81121fad>] create_object+0x13d/0x2d0
>> [<ffffffff81122265>] kmemleak_alloc+0x25/0x60
>> [<ffffffff81119f3b>] __kmalloc+0x16b/0x250
>> [<ffffffff812bb549>] kzalloc+0xf/0x11
>> [<ffffffff812bbb53>] acpi_add_single_object+0x58e/0xd3c
>> [<ffffffff812bc51c>] acpi_bus_scan+0x125/0x1af
>> [<ffffffff81842361>] acpi_scan_init+0xc8/0xe9
>> [<ffffffff8184211c>] acpi_init+0x21f/0x265
>> [<ffffffff8100a05b>] do_one_initcall+0x4b/0x1b0
>> [<ffffffff81819736>] kernel_init+0x164/0x1ba
>> [<ffffffff810130ca>] child_rip+0xa/0x20
>> [<ffffffffffffffff>] 0xffffffffffffffff
>
> I get ACPI reports as well and they may be real leaks. However, I
> didn't have time to analyse the code (pretty complicated reference
> counting).
Heh OK thanks for reviewing them though.
>> unreferenced object 0xffff880039571800 (size 1024):
>> comm "exe", pid 1168, jiffies 4294893410
>> backtrace:
>> [<ffffffff81121fad>] create_object+0x13d/0x2d0
>> [<ffffffff81122265>] kmemleak_alloc+0x25/0x60
>> [<ffffffff81119f3b>] __kmalloc+0x16b/0x250
>> [<ffffffff811e1d71>] ext4_mb_init+0x1a1/0x590
>> [<ffffffff811d2da3>] ext4_fill_super+0x1df3/0x26c0
>> [<ffffffff8112774f>] get_sb_bdev+0x16f/0x1b0
>> [<ffffffff811c8fd3>] ext4_get_sb+0x13/0x20
>> [<ffffffff81127216>] vfs_kern_mount+0x76/0x180
>> [<ffffffff8112738d>] do_kern_mount+0x4d/0x130
>> [<ffffffff8113fc57>] do_mount+0x307/0x8b0
>> [<ffffffff8114028f>] sys_mount+0x8f/0xe0
>> [<ffffffff81011f02>] system_call_fastpath+0x16/0x1b
>> [<ffffffffffffffff>] 0xffffffffffffffff
>
> The ext4 reports are real leaks and patch was posted here -
> http://lkml.org/lkml/2009/7/15/62. However, it hasn't been merged into
> mainline yet (I cc'ed Aneesh).
>
> The patch is merged in my "kmemleak-fixes" branch on
> git://linux-arm.org/linux-2.6.git.
Will try to suck them out and try them.
>> unreferenced object 0xffff880006ce0400 (size 1024):
>> comm "mplayer", pid 5293, jiffies 4295366945
>> backtrace:
>> [<ffffffff81121fad>] create_object+0x13d/0x2d0
>> [<ffffffff81122265>] kmemleak_alloc+0x25/0x60
>> [<ffffffff81119f3b>] __kmalloc+0x16b/0x250
>> [<ffffffff813021b0>] tty_buffer_request_room+0xc0/0x190
>> [<ffffffff8130244c>] tty_insert_flip_string+0x3c/0xb0
>> [<ffffffff81302f49>] pty_write+0x49/0x70
>> [<ffffffff812fd3b0>] n_tty_write+0x1c0/0x450
>> [<ffffffff812f9ec1>] tty_write+0x1a1/0x290
>> [<ffffffff81124518>] vfs_write+0xb8/0x1a0
>> [<ffffffff81124fcc>] sys_write+0x4c/0x80
>> [<ffffffff81011f02>] system_call_fastpath+0x16/0x1b
>> [<ffffffffffffffff>] 0xffffffffffffffff
>
> It could be a real leak as you get several of these. I cc'ed Greg KH
> for any suggestions he may have. It looks like it only happens when
> running mplayer.
It took me a while to figure out how to reproduce, and it really
didn't make sense to see this playing video, why would playing video
affect tty?
Luis
[-- Attachment #2: .config --]
[-- Type: application/octet-stream, Size: 74472 bytes --]
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.31-rc7
# Mon Aug 24 23:03:11 2009
#
CONFIG_64BIT=y
# CONFIG_X86_32 is not set
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_OUTPUT_FORMAT="elf64-x86-64"
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig"
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_FAST_CMPXCHG_LOCAL=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_RWSEM_GENERIC_SPINLOCK=y
# CONFIG_RWSEM_XCHGADD_ALGORITHM is not set
CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_DEFAULT_IDLE=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_HAVE_DYNAMIC_PER_CPU_AREA=y
CONFIG_HAVE_CPUMASK_OF_CPU_MAP=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ZONE_DMA32=y
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_AUDIT_ARCH=y
CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_HARDIRQS_NO__DO_IRQ=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_USE_GENERIC_SMP_HELPERS=y
CONFIG_X86_64_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_TRAMPOLINE=y
# CONFIG_KTIME_SCALAR is not set
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
CONFIG_CONSTRUCTORS=y
#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION=""
# CONFIG_LOCALVERSION_AUTO is not set
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_BZIP2=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_KERNEL_GZIP=y
# CONFIG_KERNEL_BZIP2 is not set
# CONFIG_KERNEL_LZMA is not set
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_POSIX_MQUEUE_SYSCTL=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_BSD_PROCESS_ACCT_V3=y
CONFIG_TASKSTATS=y
# CONFIG_TASK_DELAY_ACCT is not set
CONFIG_TASK_XACCT=y
CONFIG_TASK_IO_ACCOUNTING=y
CONFIG_AUDIT=y
CONFIG_AUDITSYSCALL=y
CONFIG_AUDIT_TREE=y
#
# RCU Subsystem
#
CONFIG_CLASSIC_RCU=y
# CONFIG_TREE_RCU is not set
# CONFIG_PREEMPT_RCU is not set
# CONFIG_TREE_RCU_TRACE is not set
# CONFIG_PREEMPT_RCU_TRACE is not set
# CONFIG_IKCONFIG is not set
CONFIG_LOG_BUF_SHIFT=17
CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
CONFIG_GROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
CONFIG_RT_GROUP_SCHED=y
# CONFIG_USER_SCHED is not set
CONFIG_CGROUP_SCHED=y
CONFIG_CGROUPS=y
# CONFIG_CGROUP_DEBUG is not set
CONFIG_CGROUP_NS=y
CONFIG_CGROUP_FREEZER=y
# CONFIG_CGROUP_DEVICE is not set
CONFIG_CPUSETS=y
CONFIG_PROC_PID_CPUSET=y
CONFIG_CGROUP_CPUACCT=y
CONFIG_RESOURCE_COUNTERS=y
CONFIG_CGROUP_MEM_RES_CTLR=y
# CONFIG_CGROUP_MEM_RES_CTLR_SWAP is not set
CONFIG_MM_OWNER=y
# CONFIG_SYSFS_DEPRECATED_V2 is not set
CONFIG_RELAY=y
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
# CONFIG_USER_NS is not set
CONFIG_PID_NS=y
CONFIG_NET_NS=y
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_RD_GZIP=y
CONFIG_RD_BZIP2=y
CONFIG_RD_LZMA=y
# 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=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_PCSPKR_PLATFORM=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_AIO=y
CONFIG_HAVE_PERF_COUNTERS=y
#
# Performance Counters
#
CONFIG_PERF_COUNTERS=y
CONFIG_EVENT_PROFILE=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_PCI_QUIRKS=y
CONFIG_SLUB_DEBUG=y
# CONFIG_STRIP_ASM_SYMS is not set
# CONFIG_COMPAT_BRK is not set
# CONFIG_SLAB is not set
CONFIG_SLUB=y
# CONFIG_SLOB is not set
CONFIG_PROFILING=y
CONFIG_TRACEPOINTS=y
CONFIG_MARKERS=y
# CONFIG_OPROFILE is not set
CONFIG_HAVE_OPROFILE=y
CONFIG_KPROBES=y
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
CONFIG_KRETPROBES=y
CONFIG_HAVE_IOREMAP_PROT=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_ARCH_TRACEHOOK=y
CONFIG_HAVE_DMA_ATTRS=y
CONFIG_HAVE_DMA_API_DEBUG=y
#
# GCOV-based kernel profiling
#
# CONFIG_GCOV_KERNEL is not set
# CONFIG_SLOW_WORK is not set
# CONFIG_HAVE_GENERIC_DMA_COHERENT is not set
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
# CONFIG_MODULE_FORCE_LOAD is not set
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_MODVERSIONS=y
CONFIG_MODULE_SRCVERSION_ALL=y
CONFIG_STOP_MACHINE=y
CONFIG_BLOCK=y
# CONFIG_BLK_DEV_BSG is not set
CONFIG_BLK_DEV_INTEGRITY=y
CONFIG_BLOCK_COMPAT=y
#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_AS is not set
# 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_FREEZER=y
#
# Processor type and features
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_SMP=y
CONFIG_SPARSE_IRQ=y
CONFIG_NUMA_IRQ_DESC=y
CONFIG_X86_MPPARSE=y
CONFIG_X86_EXTENDED_PLATFORM=y
# CONFIG_X86_VSMP is not set
CONFIG_SCHED_OMIT_FRAME_POINTER=y
CONFIG_PARAVIRT_GUEST=y
CONFIG_XEN=y
CONFIG_XEN_MAX_DOMAIN_MEMORY=32
CONFIG_XEN_SAVE_RESTORE=y
# CONFIG_XEN_DEBUG_FS is not set
CONFIG_KVM_CLOCK=y
CONFIG_KVM_GUEST=y
CONFIG_PARAVIRT=y
CONFIG_PARAVIRT_SPINLOCKS=y
CONFIG_PARAVIRT_CLOCK=y
# CONFIG_PARAVIRT_DEBUG is not set
# CONFIG_MEMTEST is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MGEODE_LX is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_MVIAC7 is not set
# CONFIG_MPSC is not set
# CONFIG_MCORE2 is not set
CONFIG_GENERIC_CPU=y
CONFIG_X86_CPU=y
CONFIG_X86_L1_CACHE_BYTES=64
CONFIG_X86_INTERNODE_CACHE_BYTES=64
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_TSC=y
CONFIG_X86_CMPXCHG64=y
CONFIG_X86_CMOV=y
CONFIG_X86_MINIMUM_CPU_FAMILY=64
CONFIG_X86_DEBUGCTLMSR=y
CONFIG_CPU_SUP_INTEL=y
CONFIG_CPU_SUP_AMD=y
CONFIG_CPU_SUP_CENTAUR=y
# CONFIG_X86_DS is not set
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_DMI=y
CONFIG_GART_IOMMU=y
CONFIG_CALGARY_IOMMU=y
CONFIG_CALGARY_IOMMU_ENABLED_BY_DEFAULT=y
CONFIG_AMD_IOMMU=y
CONFIG_AMD_IOMMU_STATS=y
CONFIG_SWIOTLB=y
CONFIG_IOMMU_HELPER=y
CONFIG_IOMMU_API=y
# CONFIG_MAXSMP is not set
CONFIG_NR_CPUS=64
CONFIG_SCHED_SMT=y
CONFIG_SCHED_MC=y
# CONFIG_PREEMPT_NONE 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=y
# CONFIG_X86_MCE is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
# CONFIG_X86_CPU_DEBUG is not set
CONFIG_ARCH_PHYS_ADDR_T_64BIT=y
CONFIG_DIRECT_GBPAGES=y
CONFIG_NUMA=y
CONFIG_K8_NUMA=y
CONFIG_X86_64_ACPI_NUMA=y
CONFIG_NODES_SPAN_OTHER_NODES=y
# CONFIG_NUMA_EMU is not set
CONFIG_NODES_SHIFT=6
CONFIG_ARCH_SPARSEMEM_DEFAULT=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_SELECT_MEMORY_MODEL=y
# CONFIG_FLATMEM_MANUAL is not set
# CONFIG_DISCONTIGMEM_MANUAL is not set
CONFIG_SPARSEMEM_MANUAL=y
CONFIG_SPARSEMEM=y
CONFIG_NEED_MULTIPLE_NODES=y
CONFIG_HAVE_MEMORY_PRESENT=y
CONFIG_SPARSEMEM_EXTREME=y
CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y
CONFIG_SPARSEMEM_VMEMMAP=y
#
# Memory hotplug is currently incompatible with Software Suspend
#
CONFIG_PAGEFLAGS_EXTENDED=y
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_MIGRATION=y
CONFIG_PHYS_ADDR_T_64BIT=y
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_VIRT_TO_BUS=y
CONFIG_HAVE_MLOCK=y
CONFIG_HAVE_MLOCKED_PAGE_BIT=y
CONFIG_MMU_NOTIFIER=y
CONFIG_DEFAULT_MMAP_MIN_ADDR=65536
CONFIG_X86_CHECK_BIOS_CORRUPTION=y
CONFIG_X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK=y
CONFIG_X86_RESERVE_LOW_64K=y
CONFIG_MTRR=y
CONFIG_MTRR_SANITIZER=y
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=0
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1
# CONFIG_X86_PAT is not set
CONFIG_EFI=y
CONFIG_SECCOMP=y
CONFIG_CC_STACKPROTECTOR_ALL=y
CONFIG_CC_STACKPROTECTOR=y
# 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=y
CONFIG_KEXEC=y
CONFIG_CRASH_DUMP=y
CONFIG_KEXEC_JUMP=y
CONFIG_PHYSICAL_START=0x200000
CONFIG_RELOCATABLE=y
CONFIG_PHYSICAL_ALIGN=0x1000000
CONFIG_HOTPLUG_CPU=y
# CONFIG_COMPAT_VDSO is not set
# CONFIG_CMDLINE_BOOL is not set
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID=y
#
# Power management and ACPI options
#
CONFIG_ARCH_HIBERNATION_HEADER=y
CONFIG_PM=y
CONFIG_PM_DEBUG=y
# CONFIG_PM_VERBOSE is not set
CONFIG_CAN_PM_TRACE=y
CONFIG_PM_TRACE=y
CONFIG_PM_TRACE_RTC=y
CONFIG_PM_SLEEP_SMP=y
CONFIG_PM_SLEEP=y
CONFIG_SUSPEND=y
CONFIG_PM_TEST_SUSPEND=y
CONFIG_SUSPEND_FREEZER=y
CONFIG_HIBERNATION_NVS=y
CONFIG_HIBERNATION=y
CONFIG_PM_STD_PARTITION=""
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_PROCFS=y
CONFIG_ACPI_PROCFS_POWER=y
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=m
CONFIG_ACPI_FAN=y
CONFIG_ACPI_DOCK=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_HOTPLUG_CPU=y
CONFIG_ACPI_THERMAL=y
CONFIG_ACPI_NUMA=y
CONFIG_ACPI_CUSTOM_DSDT_FILE=""
# CONFIG_ACPI_CUSTOM_DSDT is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_PCI_SLOT=y
CONFIG_X86_PM_TIMER=y
CONFIG_ACPI_CONTAINER=y
CONFIG_ACPI_SBS=y
#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
# CONFIG_CPU_FREQ_DEBUG is not set
CONFIG_CPU_FREQ_STAT=y
CONFIG_CPU_FREQ_STAT_DETAILS=y
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=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=y
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
#
# CPUFreq processor drivers
#
CONFIG_X86_ACPI_CPUFREQ=y
CONFIG_X86_POWERNOW_K8=y
CONFIG_X86_SPEEDSTEP_CENTRINO=y
# CONFIG_X86_P4_CLOCKMOD 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
#
# Memory power savings
#
# CONFIG_I7300_IDLE is not set
#
# Bus options (PCI etc.)
#
CONFIG_PCI=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCI_DOMAINS=y
# CONFIG_DMAR is not set
# CONFIG_INTR_REMAP is not set
CONFIG_PCIEPORTBUS=y
CONFIG_HOTPLUG_PCI_PCIE=y
CONFIG_PCIEAER=y
# CONFIG_PCIE_ECRC is not set
# CONFIG_PCIEAER_INJECT is not set
# CONFIG_PCIEASPM is not set
CONFIG_ARCH_SUPPORTS_MSI=y
CONFIG_PCI_MSI=y
CONFIG_PCI_LEGACY=y
# CONFIG_PCI_DEBUG is not set
# CONFIG_PCI_STUB is not set
CONFIG_HT_IRQ=y
CONFIG_PCI_IOV=y
CONFIG_ISA_DMA_API=y
CONFIG_K8_NB=y
CONFIG_PCCARD=m
# CONFIG_PCMCIA_DEBUG is not set
CONFIG_PCMCIA=m
CONFIG_PCMCIA_LOAD_CIS=y
CONFIG_PCMCIA_IOCTL=y
CONFIG_CARDBUS=y
#
# PC-card bridges
#
CONFIG_YENTA=m
CONFIG_YENTA_O2=y
CONFIG_YENTA_RICOH=y
CONFIG_YENTA_TI=y
CONFIG_YENTA_ENE_TUNE=y
CONFIG_YENTA_TOSHIBA=y
# CONFIG_PD6729 is not set
# CONFIG_I82092 is not set
CONFIG_PCCARD_NONSTATIC=m
CONFIG_HOTPLUG_PCI=y
# CONFIG_HOTPLUG_PCI_FAKE is not set
# CONFIG_HOTPLUG_PCI_ACPI is not set
CONFIG_HOTPLUG_PCI_CPCI=y
# CONFIG_HOTPLUG_PCI_CPCI_ZT5550 is not set
# CONFIG_HOTPLUG_PCI_CPCI_GENERIC is not set
# CONFIG_HOTPLUG_PCI_SHPC is not set
#
# Executable file formats / Emulations
#
CONFIG_BINFMT_ELF=y
CONFIG_COMPAT_BINFMT_ELF=y
# CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set
# CONFIG_HAVE_AOUT is not set
CONFIG_BINFMT_MISC=m
CONFIG_IA32_EMULATION=y
# CONFIG_IA32_AOUT is not set
CONFIG_COMPAT=y
CONFIG_COMPAT_FOR_U64_ALIGNMENT=y
CONFIG_SYSVIPC_COMPAT=y
CONFIG_NET=y
CONFIG_COMPAT_NETLINK_MESSAGES=y
#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_ASK_IP_FIB_HASH=y
# CONFIG_IP_FIB_TRIE is not set
CONFIG_IP_FIB_HASH=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_VERBOSE=y
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
CONFIG_IP_MROUTE=y
CONFIG_IP_PIMSM_V1=y
CONFIG_IP_PIMSM_V2=y
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
# CONFIG_INET_AH 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 is not set
# CONFIG_INET_XFRM_MODE_TUNNEL is not set
# CONFIG_INET_XFRM_MODE_BEET is not set
CONFIG_INET_LRO=y
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
CONFIG_TCP_CONG_ADVANCED=y
# CONFIG_TCP_CONG_BIC is not set
CONFIG_TCP_CONG_CUBIC=y
# CONFIG_TCP_CONG_WESTWOOD is not set
# CONFIG_TCP_CONG_HTCP is not set
# CONFIG_TCP_CONG_HSTCP is not set
# CONFIG_TCP_CONG_HYBLA is not set
# CONFIG_TCP_CONG_VEGAS is not set
# CONFIG_TCP_CONG_SCALABLE is not set
# CONFIG_TCP_CONG_LP is not set
# CONFIG_TCP_CONG_VENO is not set
# CONFIG_TCP_CONG_YEAH is not set
# CONFIG_TCP_CONG_ILLINOIS is not set
# CONFIG_DEFAULT_BIC is not set
CONFIG_DEFAULT_CUBIC=y
# CONFIG_DEFAULT_HTCP is not set
# CONFIG_DEFAULT_VEGAS is not set
# CONFIG_DEFAULT_WESTWOOD is not set
# CONFIG_DEFAULT_RENO is not set
CONFIG_DEFAULT_TCP_CONG="cubic"
CONFIG_TCP_MD5SIG=y
CONFIG_IPV6=y
CONFIG_IPV6_PRIVACY=y
# CONFIG_IPV6_ROUTER_PREF is not set
# CONFIG_IPV6_OPTIMISTIC_DAD is not set
# CONFIG_INET6_AH is not set
# CONFIG_INET6_ESP is not set
# CONFIG_INET6_IPCOMP is not set
# CONFIG_IPV6_MIP6 is not set
# CONFIG_INET6_XFRM_TUNNEL is not set
# CONFIG_INET6_TUNNEL is not set
# CONFIG_INET6_XFRM_MODE_TRANSPORT is not set
# CONFIG_INET6_XFRM_MODE_TUNNEL is not set
# CONFIG_INET6_XFRM_MODE_BEET is not set
# CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION is not set
# CONFIG_IPV6_SIT is not set
# CONFIG_IPV6_TUNNEL is not set
CONFIG_IPV6_MULTIPLE_TABLES=y
# CONFIG_IPV6_SUBTREES is not set
# CONFIG_IPV6_MROUTE is not set
CONFIG_NETLABEL=y
CONFIG_NETWORK_SECMARK=y
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_NETFILTER_ADVANCED=y
CONFIG_BRIDGE_NETFILTER=y
#
# Core Netfilter Configuration
#
# CONFIG_NETFILTER_NETLINK_QUEUE is not set
# CONFIG_NETFILTER_NETLINK_LOG is not set
# CONFIG_NF_CONNTRACK is not set
# CONFIG_NETFILTER_XTABLES is not set
# CONFIG_IP_VS is not set
#
# IP: Netfilter Configuration
#
# CONFIG_NF_DEFRAG_IPV4 is not set
# CONFIG_IP_NF_QUEUE is not set
# CONFIG_IP_NF_IPTABLES is not set
# CONFIG_IP_NF_ARPTABLES is not set
#
# IPv6: Netfilter Configuration
#
# CONFIG_IP6_NF_QUEUE is not set
# CONFIG_IP6_NF_IPTABLES is not set
# CONFIG_BRIDGE_NF_EBTABLES is not set
# CONFIG_IP_DCCP is not set
# CONFIG_IP_SCTP is not set
# CONFIG_TIPC is not set
CONFIG_ATM=y
CONFIG_ATM_CLIP=y
# CONFIG_ATM_CLIP_NO_ICMP is not set
# CONFIG_ATM_LANE is not set
# CONFIG_ATM_BR2684 is not set
CONFIG_STP=m
CONFIG_BRIDGE=m
CONFIG_NET_DSA=y
CONFIG_NET_DSA_TAG_DSA=y
CONFIG_NET_DSA_TAG_EDSA=y
CONFIG_NET_DSA_TAG_TRAILER=y
CONFIG_NET_DSA_MV88E6XXX=y
CONFIG_NET_DSA_MV88E6060=y
CONFIG_NET_DSA_MV88E6XXX_NEED_PPU=y
CONFIG_NET_DSA_MV88E6131=y
CONFIG_NET_DSA_MV88E6123_61_65=y
# CONFIG_VLAN_8021Q 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=y
#
# Queueing/Scheduling
#
# CONFIG_NET_SCH_CBQ is not set
# CONFIG_NET_SCH_HTB is not set
# CONFIG_NET_SCH_HFSC is not set
# CONFIG_NET_SCH_ATM is not set
# CONFIG_NET_SCH_PRIO is not set
# CONFIG_NET_SCH_MULTIQ is not set
# CONFIG_NET_SCH_RED is not set
# CONFIG_NET_SCH_SFQ is not set
# CONFIG_NET_SCH_TEQL is not set
# CONFIG_NET_SCH_TBF is not set
# CONFIG_NET_SCH_GRED is not set
# CONFIG_NET_SCH_DSMARK is not set
# CONFIG_NET_SCH_NETEM is not set
# CONFIG_NET_SCH_DRR is not set
# CONFIG_NET_SCH_INGRESS is not set
#
# Classification
#
CONFIG_NET_CLS=y
# CONFIG_NET_CLS_BASIC is not set
# CONFIG_NET_CLS_TCINDEX is not set
# CONFIG_NET_CLS_ROUTE4 is not set
# CONFIG_NET_CLS_FW is not set
# CONFIG_NET_CLS_U32 is not set
# CONFIG_NET_CLS_RSVP is not set
# CONFIG_NET_CLS_RSVP6 is not set
# CONFIG_NET_CLS_FLOW is not set
CONFIG_NET_CLS_CGROUP=y
CONFIG_NET_EMATCH=y
CONFIG_NET_EMATCH_STACK=32
# CONFIG_NET_EMATCH_CMP is not set
# CONFIG_NET_EMATCH_NBYTE is not set
# CONFIG_NET_EMATCH_U32 is not set
# CONFIG_NET_EMATCH_META is not set
# CONFIG_NET_EMATCH_TEXT is not set
CONFIG_NET_CLS_ACT=y
# CONFIG_NET_ACT_POLICE is not set
# CONFIG_NET_ACT_GACT is not set
# CONFIG_NET_ACT_MIRRED is not set
# CONFIG_NET_ACT_NAT is not set
# CONFIG_NET_ACT_PEDIT is not set
# CONFIG_NET_ACT_SIMP is not set
# CONFIG_NET_ACT_SKBEDIT is not set
CONFIG_NET_SCH_FIFO=y
CONFIG_DCB=y
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_NET_TCPPROBE is not set
# CONFIG_NET_DROP_MONITOR is not set
CONFIG_HAMRADIO=y
#
# Packet Radio protocols
#
# CONFIG_AX25 is not set
# CONFIG_CAN is not set
# CONFIG_IRDA is not set
CONFIG_BT=m
CONFIG_BT_L2CAP=m
CONFIG_BT_SCO=m
CONFIG_BT_RFCOMM=m
CONFIG_BT_RFCOMM_TTY=y
CONFIG_BT_BNEP=m
CONFIG_BT_BNEP_MC_FILTER=y
CONFIG_BT_BNEP_PROTO_FILTER=y
# CONFIG_BT_HIDP is not set
#
# Bluetooth device drivers
#
CONFIG_BT_HCIBTUSB=m
# CONFIG_BT_HCIBTSDIO is not set
# CONFIG_BT_HCIUART is not set
# CONFIG_BT_HCIBCM203X is not set
# CONFIG_BT_HCIBPA10X is not set
# CONFIG_BT_HCIBFUSB is not set
# CONFIG_BT_HCIDTL1 is not set
# CONFIG_BT_HCIBT3C is not set
# CONFIG_BT_HCIBLUECARD is not set
# CONFIG_BT_HCIBTUART is not set
# CONFIG_BT_HCIVHCI is not set
# CONFIG_AF_RXRPC is not set
CONFIG_FIB_RULES=y
CONFIG_WIRELESS=y
CONFIG_CFG80211=m
# CONFIG_NL80211_TESTMODE is not set
# CONFIG_CFG80211_DEVELOPER_WARNINGS is not set
CONFIG_CFG80211_REG_DEBUG=y
CONFIG_CFG80211_DEFAULT_PS=y
CONFIG_CFG80211_DEFAULT_PS_VALUE=1
CONFIG_CFG80211_DEBUGFS=y
# CONFIG_WIRELESS_OLD_REGULATORY is not set
CONFIG_WIRELESS_EXT=y
CONFIG_WIRELESS_EXT_SYSFS=y
CONFIG_LIB80211=y
CONFIG_LIB80211_CRYPT_WEP=y
CONFIG_LIB80211_CRYPT_CCMP=y
CONFIG_LIB80211_CRYPT_TKIP=y
# CONFIG_LIB80211_DEBUG is not set
CONFIG_MAC80211=m
#
# Rate control algorithm selection
#
CONFIG_MAC80211_RC_MINSTREL=y
# CONFIG_MAC80211_RC_DEFAULT_PID is not set
CONFIG_MAC80211_RC_DEFAULT_MINSTREL=y
CONFIG_MAC80211_RC_DEFAULT="minstrel"
CONFIG_MAC80211_MESH=y
CONFIG_MAC80211_LEDS=y
CONFIG_MAC80211_DEBUGFS=y
CONFIG_MAC80211_DEBUG_MENU=y
# CONFIG_MAC80211_DEBUG_PACKET_ALIGNMENT is not set
# CONFIG_MAC80211_NOINLINE is not set
CONFIG_MAC80211_VERBOSE_DEBUG=y
CONFIG_MAC80211_HT_DEBUG=y
# CONFIG_MAC80211_TKIP_DEBUG is not set
# CONFIG_MAC80211_IBSS_DEBUG is not set
CONFIG_MAC80211_VERBOSE_PS_DEBUG=y
# CONFIG_MAC80211_VERBOSE_MPL_DEBUG is not set
CONFIG_MAC80211_DEBUG_COUNTERS=y
# CONFIG_MAC80211_DRIVER_API_TRACER is not set
# CONFIG_WIMAX is not set
CONFIG_RFKILL=m
CONFIG_RFKILL_LEDS=y
CONFIG_RFKILL_INPUT=y
# CONFIG_NET_9P is not set
#
# Device Drivers
#
#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
# CONFIG_STANDALONE is not set
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE=""
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_SYS_HYPERVISOR is not set
CONFIG_CONNECTOR=y
CONFIG_PROC_EVENTS=y
# CONFIG_MTD is not set
CONFIG_PARPORT=m
# CONFIG_PARPORT_PC is not set
# CONFIG_PARPORT_GSC is not set
# CONFIG_PARPORT_AX88796 is not set
CONFIG_PARPORT_1284=y
CONFIG_PNP=y
CONFIG_PNP_DEBUG_MESSAGES=y
#
# Protocols
#
CONFIG_PNPACPI=y
CONFIG_BLK_DEV=y
# CONFIG_BLK_DEV_FD 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
# 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=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=65536
# CONFIG_BLK_DEV_XIP is not set
CONFIG_CDROM_PKTCDVD=y
CONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not set
# CONFIG_ATA_OVER_ETH is not set
# CONFIG_XEN_BLKDEV_FRONTEND is not set
# CONFIG_BLK_DEV_HD is not set
CONFIG_MISC_DEVICES=y
# 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_HP_ILO is not set
# CONFIG_ISL29003 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=m
# CONFIG_CB710_CORE is not set
CONFIG_HAVE_IDE=y
# CONFIG_IDE is not set
#
# SCSI device support
#
# 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 is not set
CONFIG_CHR_DEV_SG=y
# CONFIG_CHR_DEV_SCH is not set
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y
CONFIG_SCSI_SCAN_ASYNC=y
CONFIG_SCSI_WAIT_SCAN=m
#
# SCSI Transports
#
# CONFIG_SCSI_SPI_ATTRS 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_CXGB3_ISCSI is not set
# CONFIG_SCSI_BNX2_ISCSI is not set
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_ACARD 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_ARCMSR is not set
CONFIG_MEGARAID_NEWGEN=y
# CONFIG_MEGARAID_MM 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_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_EATA is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_STEX is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR 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_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_SCSI_SRP is not set
CONFIG_SCSI_LOWLEVEL_PCMCIA=y
# CONFIG_PCMCIA_FDOMAIN is not set
# CONFIG_PCMCIA_QLOGIC is not set
# CONFIG_PCMCIA_SYM53C500 is not set
CONFIG_SCSI_DH=y
# CONFIG_SCSI_DH_RDAC is not set
# CONFIG_SCSI_DH_HP_SW is not set
# CONFIG_SCSI_DH_EMC is not set
# CONFIG_SCSI_DH_ALUA is not set
# CONFIG_SCSI_OSD_INITIATOR is not set
CONFIG_ATA=y
# CONFIG_ATA_NONSTANDARD is not set
CONFIG_ATA_ACPI=y
CONFIG_SATA_PMP=y
CONFIG_SATA_AHCI=y
CONFIG_SATA_SIL24=y
CONFIG_ATA_SFF=y
CONFIG_SATA_SVW=y
CONFIG_ATA_PIIX=y
# CONFIG_SATA_MV is not set
CONFIG_SATA_NV=y
CONFIG_PDC_ADMA=y
CONFIG_SATA_QSTOR=y
CONFIG_SATA_PROMISE=y
CONFIG_SATA_SX4=y
CONFIG_SATA_SIL=y
CONFIG_SATA_SIS=y
CONFIG_SATA_ULI=y
CONFIG_SATA_VIA=y
CONFIG_SATA_VITESSE=y
CONFIG_SATA_INIC162X=y
CONFIG_PATA_ACPI=y
CONFIG_PATA_ALI=y
CONFIG_PATA_AMD=y
CONFIG_PATA_ARTOP=y
CONFIG_PATA_ATIIXP=y
# CONFIG_PATA_CMD640_PCI is not set
CONFIG_PATA_CMD64X=y
CONFIG_PATA_CS5520=y
CONFIG_PATA_CS5530=y
# CONFIG_PATA_CYPRESS is not set
CONFIG_PATA_EFAR=y
CONFIG_ATA_GENERIC=y
CONFIG_PATA_HPT366=y
CONFIG_PATA_HPT37X=y
# CONFIG_PATA_HPT3X2N is not set
CONFIG_PATA_HPT3X3=y
# CONFIG_PATA_HPT3X3_DMA is not set
CONFIG_PATA_IT821X=y
# CONFIG_PATA_IT8213 is not set
CONFIG_PATA_JMICRON=y
CONFIG_PATA_TRIFLEX=y
CONFIG_PATA_MARVELL=y
CONFIG_PATA_MPIIX=y
CONFIG_PATA_OLDPIIX=y
CONFIG_PATA_NETCELL=y
# CONFIG_PATA_NINJA32 is not set
CONFIG_PATA_NS87410=y
CONFIG_PATA_NS87415=y
# CONFIG_PATA_OPTI is not set
# CONFIG_PATA_OPTIDMA is not set
# CONFIG_PATA_PCMCIA is not set
CONFIG_PATA_PDC_OLD=y
# CONFIG_PATA_RADISYS is not set
CONFIG_PATA_RZ1000=y
CONFIG_PATA_SC1200=y
CONFIG_PATA_SERVERWORKS=y
CONFIG_PATA_PDC2027X=y
CONFIG_PATA_SIL680=y
CONFIG_PATA_SIS=y
CONFIG_PATA_VIA=y
CONFIG_PATA_WINBOND=y
CONFIG_PATA_SCH=y
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_AUTODETECT=y
# CONFIG_MD_LINEAR is not set
# CONFIG_MD_RAID0 is not set
# CONFIG_MD_RAID1 is not set
# CONFIG_MD_RAID10 is not set
# CONFIG_MD_RAID456 is not set
# CONFIG_MD_MULTIPATH is not set
# CONFIG_MD_FAULTY is not set
CONFIG_BLK_DEV_DM=y
# CONFIG_DM_DEBUG is not set
# CONFIG_DM_CRYPT is not set
CONFIG_DM_SNAPSHOT=y
CONFIG_DM_MIRROR=y
# CONFIG_DM_LOG_USERSPACE is not set
# CONFIG_DM_ZERO is not set
CONFIG_DM_MULTIPATH=y
# CONFIG_DM_MULTIPATH_QL is not set
# CONFIG_DM_MULTIPATH_ST is not set
# CONFIG_DM_DELAY is not set
CONFIG_DM_UEVENT=y
CONFIG_FUSION=y
# CONFIG_FUSION_SPI is not set
# CONFIG_FUSION_FC is not set
# CONFIG_FUSION_SAS is not set
CONFIG_FUSION_MAX_SGE=128
CONFIG_FUSION_LOGGING=y
#
# IEEE 1394 (FireWire) support
#
#
# You can enable one or both FireWire driver stacks.
#
#
# See the help texts for more information.
#
# CONFIG_FIREWIRE is not set
CONFIG_IEEE1394=m
CONFIG_IEEE1394_OHCI1394=m
# 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 is not set
# 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=y
CONFIG_MAC_EMUMOUSEBTN=y
CONFIG_NETDEVICES=y
# CONFIG_IFB is not set
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_MACVLAN is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_VETH is not set
# CONFIG_NET_SB1000 is not set
# CONFIG_ARCNET is not set
CONFIG_PHYLIB=y
#
# MII PHY device drivers
#
# CONFIG_MARVELL_PHY is not set
# CONFIG_DAVICOM_PHY is not set
# CONFIG_QSEMI_PHY is not set
# CONFIG_LXT_PHY is not set
# CONFIG_CICADA_PHY is not set
# CONFIG_VITESSE_PHY is not set
# CONFIG_SMSC_PHY is not set
# CONFIG_BROADCOM_PHY is not set
# CONFIG_ICPLUS_PHY is not set
# CONFIG_REALTEK_PHY is not set
# CONFIG_NATIONAL_PHY is not set
# CONFIG_STE10XP is not set
# CONFIG_LSI_ET1011C_PHY is not set
CONFIG_FIXED_PHY=y
# CONFIG_MDIO_BITBANG is not set
CONFIG_NET_ETHERNET=y
CONFIG_MII=m
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_CASSINI is not set
CONFIG_NET_VENDOR_3COM=y
# CONFIG_VORTEX is not set
# CONFIG_TYPHOON is not set
# CONFIG_ETHOC is not set
# CONFIG_DNET is not set
CONFIG_NET_TULIP=y
# CONFIG_DE2104X is not set
# CONFIG_TULIP is not set
# CONFIG_DE4X5 is not set
# CONFIG_WINBOND_840 is not set
# CONFIG_DM9102 is not set
# CONFIG_ULI526X is not set
# CONFIG_PCMCIA_XIRCOM is not set
# CONFIG_HP100 is not set
# CONFIG_IBM_NEW_EMAC_ZMII is not set
# CONFIG_IBM_NEW_EMAC_RGMII is not set
# CONFIG_IBM_NEW_EMAC_TAH is not set
# CONFIG_IBM_NEW_EMAC_EMAC4 is not set
# CONFIG_IBM_NEW_EMAC_NO_FLOW_CTRL is not set
# CONFIG_IBM_NEW_EMAC_MAL_CLR_ICINTSTAT is not set
# CONFIG_IBM_NEW_EMAC_MAL_COMMON_ERR is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_B44 is not set
# CONFIG_FORCEDETH is not set
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
# CONFIG_R6040 is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SMSC9420 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_KS8842 is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_SC92031 is not set
CONFIG_NET_POCKET=y
# CONFIG_ATP is not set
# CONFIG_DE600 is not set
# CONFIG_DE620 is not set
# CONFIG_ATL2 is not set
CONFIG_NETDEV_1000=y
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
CONFIG_E1000E=m
# 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 is not set
# 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=y
# CONFIG_CHELSIO_T1 is not set
CONFIG_CHELSIO_T3_DEPENDS=y
# CONFIG_CHELSIO_T3 is not set
# CONFIG_ENIC is not set
# CONFIG_IXGBE is not set
# CONFIG_IXGB is not set
# CONFIG_S2IO is not set
# CONFIG_VXGE is not set
# CONFIG_MYRI10GE is not set
# CONFIG_NETXEN_NIC is not set
# CONFIG_NIU is not set
# CONFIG_MLX4_EN is not set
# CONFIG_MLX4_CORE is not set
# CONFIG_TEHUTI is not set
# CONFIG_BNX2X is not set
# CONFIG_QLGE is not set
# CONFIG_SFC is not set
# CONFIG_BE2NET is not set
CONFIG_TR=y
# CONFIG_IBMOL is not set
# CONFIG_3C359 is not set
# CONFIG_TMS380TR is not set
#
# Wireless LAN
#
CONFIG_WLAN_PRE80211=y
CONFIG_STRIP=m
CONFIG_PCMCIA_WAVELAN=m
CONFIG_PCMCIA_NETWAVE=m
CONFIG_WLAN_80211=y
CONFIG_PCMCIA_RAYCS=m
CONFIG_LIBERTAS=m
CONFIG_LIBERTAS_USB=m
CONFIG_LIBERTAS_CS=m
CONFIG_LIBERTAS_SDIO=m
CONFIG_LIBERTAS_DEBUG=y
# CONFIG_LIBERTAS_THINFIRM is not set
CONFIG_AIRO=m
CONFIG_ATMEL=y
CONFIG_PCI_ATMEL=m
CONFIG_PCMCIA_ATMEL=m
CONFIG_AT76C50X_USB=m
CONFIG_AIRO_CS=m
CONFIG_PCMCIA_WL3501=m
CONFIG_PRISM54=m
CONFIG_USB_ZD1201=m
CONFIG_USB_NET_RNDIS_WLAN=m
CONFIG_RTL8180=m
CONFIG_RTL8187=m
CONFIG_RTL8187_LEDS=y
CONFIG_ADM8211=m
CONFIG_MAC80211_HWSIM=m
# CONFIG_MWL8K is not set
CONFIG_P54_COMMON=m
CONFIG_P54_USB=m
CONFIG_P54_PCI=m
CONFIG_P54_LEDS=y
CONFIG_ATH_COMMON=m
CONFIG_ATH5K=m
CONFIG_ATH5K_DEBUG=y
CONFIG_ATH9K=m
CONFIG_ATH9K_DEBUG=y
CONFIG_AR9170_USB=m
CONFIG_AR9170_LEDS=y
CONFIG_IPW2100=m
CONFIG_IPW2100_MONITOR=y
CONFIG_IPW2100_DEBUG=y
CONFIG_IPW2200=m
CONFIG_IPW2200_MONITOR=y
CONFIG_IPW2200_RADIOTAP=y
CONFIG_IPW2200_PROMISCUOUS=y
CONFIG_IPW2200_QOS=y
CONFIG_IPW2200_DEBUG=y
CONFIG_LIBIPW=m
CONFIG_LIBIPW_DEBUG=y
CONFIG_IWLWIFI=m
CONFIG_IWLWIFI_LEDS=y
CONFIG_IWLWIFI_SPECTRUM_MEASUREMENT=y
CONFIG_IWLWIFI_DEBUG=y
CONFIG_IWLWIFI_DEBUGFS=y
CONFIG_IWLAGN=m
CONFIG_IWL4965=y
CONFIG_IWL5000=y
CONFIG_IWL3945=m
CONFIG_IWL3945_SPECTRUM_MEASUREMENT=y
CONFIG_HOSTAP=y
CONFIG_HOSTAP_FIRMWARE=y
CONFIG_HOSTAP_FIRMWARE_NVRAM=y
CONFIG_HOSTAP_PLX=y
CONFIG_HOSTAP_PCI=y
CONFIG_HOSTAP_CS=m
CONFIG_B43=m
CONFIG_B43_PCI_AUTOSELECT=y
CONFIG_B43_PCICORE_AUTOSELECT=y
CONFIG_B43_PCMCIA=y
CONFIG_B43_PIO=y
# CONFIG_B43_PHY_LP is not set
CONFIG_B43_LEDS=y
CONFIG_B43_HWRNG=y
CONFIG_B43_DEBUG=y
CONFIG_B43_FORCE_PIO=y
CONFIG_B43LEGACY=m
CONFIG_B43LEGACY_PCI_AUTOSELECT=y
CONFIG_B43LEGACY_PCICORE_AUTOSELECT=y
CONFIG_B43LEGACY_LEDS=y
CONFIG_B43LEGACY_HWRNG=y
CONFIG_B43LEGACY_DEBUG=y
CONFIG_B43LEGACY_DMA=y
CONFIG_B43LEGACY_PIO=y
CONFIG_B43LEGACY_DMA_AND_PIO_MODE=y
# CONFIG_B43LEGACY_DMA_MODE is not set
# CONFIG_B43LEGACY_PIO_MODE is not set
# CONFIG_ZD1211RW is not set
CONFIG_RT2X00=m
CONFIG_RT2400PCI=m
CONFIG_RT2500PCI=m
CONFIG_RT61PCI=m
CONFIG_RT2500USB=m
CONFIG_RT73USB=m
CONFIG_RT2800USB=m
CONFIG_RT2X00_LIB_PCI=m
CONFIG_RT2X00_LIB_USB=m
CONFIG_RT2X00_LIB=m
CONFIG_RT2X00_LIB_HT=y
CONFIG_RT2X00_LIB_FIRMWARE=y
CONFIG_RT2X00_LIB_CRYPTO=y
CONFIG_RT2X00_LIB_LEDS=y
CONFIG_RT2X00_LIB_DEBUGFS=y
CONFIG_RT2X00_DEBUG=y
CONFIG_HERMES=m
CONFIG_HERMES_CACHE_FW_ON_INIT=y
CONFIG_PLX_HERMES=m
CONFIG_TMD_HERMES=m
CONFIG_NORTEL_HERMES=m
CONFIG_PCI_HERMES=m
CONFIG_PCMCIA_HERMES=m
CONFIG_PCMCIA_SPECTRUM=m
CONFIG_WL12XX=y
CONFIG_WL1251=m
CONFIG_WL1251_SDIO=m
CONFIG_IWM=m
CONFIG_IWM_DEBUG=y
#
# 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=m
CONFIG_USB_NET_AX8817X=m
CONFIG_USB_NET_CDCETHER=m
# CONFIG_USB_NET_CDC_EEM is not set
# CONFIG_USB_NET_DM9601 is not set
# CONFIG_USB_NET_SMSC95XX is not set
# CONFIG_USB_NET_GL620A is not set
CONFIG_USB_NET_NET1080=m
# CONFIG_USB_NET_PLUSB is not set
# CONFIG_USB_NET_MCS7830 is not set
CONFIG_USB_NET_RNDIS_HOST=m
CONFIG_USB_NET_CDC_SUBSET=m
# CONFIG_USB_ALI_M5632 is not set
# CONFIG_USB_AN2720 is not set
CONFIG_USB_BELKIN=y
CONFIG_USB_ARMLINUX=y
# CONFIG_USB_EPSON2888 is not set
# CONFIG_USB_KC2190 is not set
CONFIG_USB_NET_ZAURUS=m
# CONFIG_USB_HSO is not set
# CONFIG_USB_NET_INT51X1 is not set
CONFIG_NET_PCMCIA=y
# CONFIG_PCMCIA_3C589 is not set
# CONFIG_PCMCIA_3C574 is not set
# CONFIG_PCMCIA_FMVJ18X is not set
# CONFIG_PCMCIA_PCNET is not set
# CONFIG_PCMCIA_NMCLAN is not set
# CONFIG_PCMCIA_SMC91C92 is not set
# CONFIG_PCMCIA_XIRC2PS is not set
# CONFIG_PCMCIA_AXNET is not set
# CONFIG_PCMCIA_IBMTR is not set
CONFIG_WAN=y
# CONFIG_HDLC is not set
# CONFIG_DLCI is not set
# CONFIG_SBNI is not set
CONFIG_ATM_DRIVERS=y
# CONFIG_ATM_DUMMY is not set
# CONFIG_ATM_TCP is not set
# CONFIG_ATM_LANAI is not set
# CONFIG_ATM_ENI is not set
# CONFIG_ATM_FIRESTREAM is not set
# CONFIG_ATM_ZATM is not set
# CONFIG_ATM_IDT77252 is not set
# CONFIG_ATM_AMBASSADOR is not set
# CONFIG_ATM_HORIZON is not set
# CONFIG_ATM_IA is not set
# CONFIG_ATM_FORE200E is not set
# CONFIG_ATM_HE is not set
# CONFIG_ATM_SOLOS is not set
# CONFIG_XEN_NETDEV_FRONTEND is not set
CONFIG_FDDI=y
# CONFIG_DEFXX is not set
# CONFIG_SKFP is not set
CONFIG_HIPPI=y
# CONFIG_ROADRUNNER is not set
# CONFIG_PLIP is not set
CONFIG_PPP=y
CONFIG_PPP_MULTILINK=y
CONFIG_PPP_FILTER=y
# CONFIG_PPP_ASYNC is not set
# CONFIG_PPP_SYNC_TTY is not set
# CONFIG_PPP_DEFLATE is not set
# CONFIG_PPP_BSDCOMP is not set
# CONFIG_PPP_MPPE is not set
# CONFIG_PPPOE is not set
# CONFIG_PPPOATM is not set
# CONFIG_PPPOL2TP is not set
# CONFIG_SLIP is not set
CONFIG_SLHC=y
CONFIG_NET_FC=y
# CONFIG_NETCONSOLE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
CONFIG_ISDN=y
# CONFIG_MISDN is not set
# CONFIG_ISDN_I4L is not set
# CONFIG_ISDN_CAPI is not set
# CONFIG_PHONE is not set
#
# Input device support
#
CONFIG_INPUT=y
# CONFIG_INPUT_FF_MEMLESS is not set
# CONFIG_INPUT_POLLDEV 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=m
CONFIG_INPUT_EVDEV=y
# CONFIG_INPUT_EVBUG is not set
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_LM8323 is not set
# CONFIG_KEYBOARD_NEWTON 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=m
CONFIG_MOUSE_PS2_ALPS=y
CONFIG_MOUSE_PS2_LOGIPS2PP=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
CONFIG_MOUSE_PS2_LIFEBOOK=y
CONFIG_MOUSE_PS2_TRACKPOINT=y
CONFIG_MOUSE_PS2_ELANTECH=y
# CONFIG_MOUSE_PS2_TOUCHKIT is not set
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_APPLETOUCH is not set
# CONFIG_MOUSE_BCM5974 is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_MOUSE_SYNAPTICS_I2C is not set
CONFIG_INPUT_JOYSTICK=y
# CONFIG_JOYSTICK_ANALOG is not set
# CONFIG_JOYSTICK_A3D is not set
# CONFIG_JOYSTICK_ADI is not set
# CONFIG_JOYSTICK_COBRA is not set
# CONFIG_JOYSTICK_GF2K is not set
# CONFIG_JOYSTICK_GRIP is not set
# CONFIG_JOYSTICK_GRIP_MP is not set
# CONFIG_JOYSTICK_GUILLEMOT is not set
# CONFIG_JOYSTICK_INTERACT is not set
# CONFIG_JOYSTICK_SIDEWINDER is not set
# CONFIG_JOYSTICK_TMDC is not set
# CONFIG_JOYSTICK_IFORCE is not set
# CONFIG_JOYSTICK_WARRIOR is not set
# CONFIG_JOYSTICK_MAGELLAN is not set
# CONFIG_JOYSTICK_SPACEORB is not set
# CONFIG_JOYSTICK_SPACEBALL is not set
# CONFIG_JOYSTICK_STINGER is not set
# CONFIG_JOYSTICK_TWIDJOY is not set
# CONFIG_JOYSTICK_ZHENHUA is not set
# CONFIG_JOYSTICK_DB9 is not set
# CONFIG_JOYSTICK_GAMECON is not set
# CONFIG_JOYSTICK_TURBOGRAFX is not set
# CONFIG_JOYSTICK_JOYDUMP is not set
# CONFIG_JOYSTICK_XPAD is not set
# CONFIG_JOYSTICK_WALKERA0701 is not set
CONFIG_INPUT_TABLET=y
# CONFIG_TABLET_USB_ACECAD is not set
# CONFIG_TABLET_USB_AIPTEK is not set
# CONFIG_TABLET_USB_GTCO is not set
# CONFIG_TABLET_USB_KBTAB is not set
# CONFIG_TABLET_USB_WACOM is not set
CONFIG_INPUT_TOUCHSCREEN=y
# CONFIG_TOUCHSCREEN_AD7879_I2C is not set
# CONFIG_TOUCHSCREEN_AD7879 is not set
# CONFIG_TOUCHSCREEN_DA9034 is not set
# CONFIG_TOUCHSCREEN_EETI is not set
# CONFIG_TOUCHSCREEN_FUJITSU is not set
# CONFIG_TOUCHSCREEN_GUNZE is not set
# CONFIG_TOUCHSCREEN_ELO is not set
# CONFIG_TOUCHSCREEN_WACOM_W8001 is not set
# CONFIG_TOUCHSCREEN_MTOUCH is not set
# CONFIG_TOUCHSCREEN_INEXIO is not set
# CONFIG_TOUCHSCREEN_MK712 is not set
# CONFIG_TOUCHSCREEN_PENMOUNT is not set
# CONFIG_TOUCHSCREEN_TOUCHRIGHT is not set
# CONFIG_TOUCHSCREEN_TOUCHWIN is not set
# CONFIG_TOUCHSCREEN_USB_COMPOSITE is not set
# CONFIG_TOUCHSCREEN_TOUCHIT213 is not set
# CONFIG_TOUCHSCREEN_TSC2007 is not set
# CONFIG_TOUCHSCREEN_W90X900 is not set
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=m
# CONFIG_INPUT_APANEL is not set
# CONFIG_INPUT_ATLAS_BTNS is not set
# CONFIG_INPUT_ATI_REMOTE is not set
# CONFIG_INPUT_ATI_REMOTE2 is not set
# CONFIG_INPUT_KEYSPAN_REMOTE is not set
# CONFIG_INPUT_POWERMATE is not set
# CONFIG_INPUT_YEALINK is not set
# CONFIG_INPUT_CM109 is not set
# CONFIG_INPUT_TWL4030_PWRBUTTON is not set
# CONFIG_INPUT_UINPUT 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=m
# 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=y
# CONFIG_DEVKMEM is not set
CONFIG_SERIAL_NONSTANDARD=y
# CONFIG_COMPUTONE is not set
# CONFIG_ROCKETPORT is not set
# CONFIG_CYCLADES is not set
# CONFIG_DIGIEPCA is not set
# CONFIG_MOXA_INTELLIO is not set
# CONFIG_MOXA_SMARTIO is not set
# CONFIG_ISI is not set
# CONFIG_SYNCLINK is not set
# CONFIG_SYNCLINKMP is not set
# CONFIG_SYNCLINK_GT is not set
# CONFIG_N_HDLC is not set
# CONFIG_RISCOM8 is not set
# CONFIG_SPECIALIX is not set
# CONFIG_SX is not set
# CONFIG_RIO is not set
CONFIG_STALDRV=y
# CONFIG_STALLION is not set
# CONFIG_ISTALLION is not set
# CONFIG_NOZOMI is not set
#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_PNP=y
# CONFIG_SERIAL_8250_CS is not set
CONFIG_SERIAL_8250_NR_UARTS=48
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
CONFIG_SERIAL_8250_SHARE_IRQ=y
# CONFIG_SERIAL_8250_DETECT_IRQ is not set
CONFIG_SERIAL_8250_RSA=y
#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_CONSOLE_POLL=y
# CONFIG_SERIAL_JSM is not set
CONFIG_UNIX98_PTYS=y
CONFIG_DEVPTS_MULTIPLE_INSTANCES=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=0
CONFIG_PRINTER=m
# CONFIG_LP_CONSOLE is not set
CONFIG_PPDEV=m
CONFIG_HVC_DRIVER=y
CONFIG_HVC_IRQ=y
CONFIG_HVC_XEN=y
# CONFIG_IPMI_HANDLER is not set
CONFIG_HW_RANDOM=y
# CONFIG_HW_RANDOM_TIMERIOMEM is not set
# CONFIG_HW_RANDOM_INTEL is not set
# CONFIG_HW_RANDOM_AMD is not set
# CONFIG_HW_RANDOM_VIA is not set
CONFIG_NVRAM=m
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
#
# PCMCIA character devices
#
# CONFIG_SYNCLINK_CS is not set
# CONFIG_CARDMAN_4000 is not set
# CONFIG_CARDMAN_4040 is not set
# CONFIG_IPWIRELESS is not set
# CONFIG_MWAVE is not set
# CONFIG_PC8736x_GPIO is not set
# CONFIG_RAW_DRIVER is not set
CONFIG_HPET=y
CONFIG_HPET_MMAP=y
# CONFIG_HANGCHECK_TIMER is not set
# CONFIG_TCG_TPM is not set
# CONFIG_TELCLOCK is not set
CONFIG_DEVPORT=y
CONFIG_I2C=y
CONFIG_I2C_BOARDINFO=y
# CONFIG_I2C_CHARDEV is not set
# CONFIG_I2C_HELPER_AUTO is not set
#
# I2C Algorithms
#
CONFIG_I2C_ALGOBIT=m
# CONFIG_I2C_ALGOPCF is not set
# CONFIG_I2C_ALGOPCA is not set
#
# 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
#
# I2C system bus drivers (mostly embedded / system-on-chip)
#
# CONFIG_I2C_OCORES is not set
# CONFIG_I2C_SIMTEC 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
#
# Graphics adapter I2C/DDC channel drivers
#
# CONFIG_I2C_VOODOO3 is not set
#
# Other I2C/SMBus bus drivers
#
# CONFIG_I2C_PCA_PLATFORM is not set
# CONFIG_I2C_STUB is not set
#
# Miscellaneous I2C Chip support
#
# CONFIG_DS1682 is not set
# CONFIG_SENSORS_PCF8574 is not set
# CONFIG_PCF8575 is not set
# CONFIG_SENSORS_PCA9539 is not set
# CONFIG_SENSORS_TSL2550 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_I2C_DEBUG_CHIP 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_BATTERY_DS2760 is not set
# CONFIG_BATTERY_DS2782 is not set
# CONFIG_BATTERY_BQ27x00 is not set
# CONFIG_BATTERY_DA9030 is not set
# CONFIG_BATTERY_MAX17040 is not set
CONFIG_HWMON=y
# CONFIG_HWMON_VID is not set
# 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_ADT7462 is not set
# CONFIG_SENSORS_ADT7470 is not set
# CONFIG_SENSORS_ADT7473 is not set
# CONFIG_SENSORS_ADT7475 is not set
# CONFIG_SENSORS_K8TEMP is not set
# CONFIG_SENSORS_ASB100 is not set
# CONFIG_SENSORS_ATK0110 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_FSCHER is not set
# CONFIG_SENSORS_FSCPOS 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_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_SMSC47M1 is not set
# CONFIG_SENSORS_SMSC47M192 is not set
# CONFIG_SENSORS_SMSC47B397 is not set
# CONFIG_SENSORS_ADS7828 is not set
# CONFIG_SENSORS_THMC50 is not set
# CONFIG_SENSORS_TMP401 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_LIS3LV02D is not set
# CONFIG_SENSORS_APPLESMC is not set
# CONFIG_HWMON_DEBUG_CHIP is not set
CONFIG_THERMAL=y
CONFIG_THERMAL_HWMON=y
CONFIG_WATCHDOG=y
# CONFIG_WATCHDOG_NOWAYOUT is not set
#
# Watchdog Device Drivers
#
# CONFIG_SOFT_WATCHDOG is not set
# CONFIG_TWL4030_WATCHDOG is not set
# CONFIG_ACQUIRE_WDT is not set
# CONFIG_ADVANTECH_WDT is not set
# CONFIG_ALIM1535_WDT is not set
# CONFIG_ALIM7101_WDT is not set
# CONFIG_SC520_WDT is not set
# CONFIG_EUROTECH_WDT is not set
# CONFIG_IB700_WDT is not set
# CONFIG_IBMASR is not set
# CONFIG_WAFER_WDT is not set
# CONFIG_I6300ESB_WDT is not set
# CONFIG_ITCO_WDT is not set
# CONFIG_IT8712F_WDT is not set
# CONFIG_IT87_WDT is not set
# CONFIG_HP_WATCHDOG is not set
# CONFIG_SC1200_WDT is not set
# CONFIG_PC87413_WDT is not set
# CONFIG_60XX_WDT is not set
# CONFIG_SBC8360_WDT is not set
# CONFIG_CPU5_WDT is not set
# CONFIG_SMSC_SCH311X_WDT is not set
# CONFIG_SMSC37B787_WDT is not set
# CONFIG_W83627HF_WDT is not set
# CONFIG_W83697HF_WDT is not set
# CONFIG_W83697UG_WDT is not set
# CONFIG_W83877F_WDT is not set
# CONFIG_W83977F_WDT is not set
# CONFIG_MACHZ_WDT is not set
# CONFIG_SBC_EPX_C3_WATCHDOG is not set
#
# PCI-based Watchdog Cards
#
# CONFIG_PCIPCWATCHDOG is not set
# CONFIG_WDTPCI is not set
#
# USB-based Watchdog Cards
#
# CONFIG_USBPCWATCHDOG is not set
CONFIG_SSB_POSSIBLE=y
#
# Sonics Silicon Backplane
#
CONFIG_SSB=m
CONFIG_SSB_SPROM=y
CONFIG_SSB_BLOCKIO=y
CONFIG_SSB_PCIHOST_POSSIBLE=y
CONFIG_SSB_PCIHOST=y
CONFIG_SSB_B43_PCI_BRIDGE=y
CONFIG_SSB_PCMCIAHOST_POSSIBLE=y
CONFIG_SSB_PCMCIAHOST=y
# CONFIG_SSB_DEBUG is not set
CONFIG_SSB_DRIVER_PCICORE_POSSIBLE=y
CONFIG_SSB_DRIVER_PCICORE=y
#
# Multifunction device drivers
#
# CONFIG_MFD_CORE is not set
# CONFIG_MFD_SM501 is not set
# CONFIG_HTC_PASIC3 is not set
CONFIG_TWL4030_CORE=y
# CONFIG_MFD_TMIO is not set
CONFIG_PMIC_DA903X=y
# CONFIG_MFD_WM8400 is not set
# CONFIG_MFD_WM8350_I2C is not set
# CONFIG_MFD_PCF50633 is not set
# CONFIG_AB3100_CORE is not set
CONFIG_REGULATOR=y
# CONFIG_REGULATOR_DEBUG is not set
# CONFIG_REGULATOR_FIXED_VOLTAGE is not set
# CONFIG_REGULATOR_VIRTUAL_CONSUMER is not set
# CONFIG_REGULATOR_USERSPACE_CONSUMER is not set
# CONFIG_REGULATOR_BQ24022 is not set
# CONFIG_REGULATOR_MAX1586 is not set
CONFIG_REGULATOR_TWL4030=y
# CONFIG_REGULATOR_DA903X is not set
# CONFIG_REGULATOR_LP3971 is not set
# CONFIG_MEDIA_SUPPORT is not set
#
# Graphics support
#
CONFIG_AGP=y
CONFIG_AGP_AMD64=y
CONFIG_AGP_INTEL=m
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_VIA is not set
CONFIG_DRM=m
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
# CONFIG_DRM_RADEON is not set
# CONFIG_DRM_I810 is not set
# CONFIG_DRM_I830 is not set
CONFIG_DRM_I915=m
CONFIG_DRM_I915_KMS=y
# 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=m
CONFIG_FB=y
CONFIG_FIRMWARE_EDID=y
# 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 is not set
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_TILEBLITTING=y
#
# 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=y
CONFIG_FB_IMSTT=y
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_UVESA is not set
# CONFIG_FB_VESA is not set
CONFIG_FB_EFI=y
# 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=y
# CONFIG_FB_GEODE_LX is not set
# CONFIG_FB_GEODE_GX is not set
# CONFIG_FB_GEODE_GX1 is not set
# CONFIG_FB_VIRTUAL is not set
# CONFIG_XEN_FBDEV_FRONTEND 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_DA903X is not set
# CONFIG_BACKLIGHT_MBP_NVIDIA is not set
# CONFIG_BACKLIGHT_SAHARA 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_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=m
# 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=m
CONFIG_SOUND_OSS_CORE=y
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_JACK=y
CONFIG_SND_SEQUENCER=m
CONFIG_SND_SEQ_DUMMY=m
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_PCM_OSS_PLUGINS=y
CONFIG_SND_SEQUENCER_OSS=y
# CONFIG_SND_HRTIMER is not set
CONFIG_SND_DYNAMIC_MINORS=y
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_VMASTER=y
# CONFIG_SND_RAWMIDI_SEQ is not set
# 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=y
# CONFIG_SND_PCSP is not set
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_VIRMIDI is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_MTS64 is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set
# CONFIG_SND_PORTMAN2X4 is not set
CONFIG_SND_PCI=y
# CONFIG_SND_AD1889 is not set
# CONFIG_SND_ALS300 is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_ATIIXP_MODEM is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AW2 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CA0106 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_OXYGEN is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS5530 is not set
# CONFIG_SND_CTXFI is not set
# CONFIG_SND_DARLA20 is not set
# CONFIG_SND_GINA20 is not set
# CONFIG_SND_LAYLA20 is not set
# CONFIG_SND_DARLA24 is not set
# CONFIG_SND_GINA24 is not set
# CONFIG_SND_LAYLA24 is not set
# CONFIG_SND_MONA is not set
# CONFIG_SND_MIA is not set
# CONFIG_SND_ECHO3G is not set
# CONFIG_SND_INDIGO is not set
# CONFIG_SND_INDIGOIO is not set
# CONFIG_SND_INDIGODJ is not set
# CONFIG_SND_INDIGOIOX is not set
# CONFIG_SND_INDIGODJX is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_EMU10K1X is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_FM801 is not set
CONFIG_SND_HDA_INTEL=m
# CONFIG_SND_HDA_HWDEP is not set
CONFIG_SND_HDA_INPUT_BEEP=y
CONFIG_SND_HDA_INPUT_JACK=y
CONFIG_SND_HDA_CODEC_REALTEK=y
CONFIG_SND_HDA_CODEC_ANALOG=y
CONFIG_SND_HDA_CODEC_SIGMATEL=y
CONFIG_SND_HDA_CODEC_VIA=y
CONFIG_SND_HDA_CODEC_ATIHDMI=y
CONFIG_SND_HDA_CODEC_NVHDMI=y
CONFIG_SND_HDA_CODEC_INTELHDMI=y
CONFIG_SND_HDA_ELD=y
CONFIG_SND_HDA_CODEC_CONEXANT=y
CONFIG_SND_HDA_CODEC_CA0110=y
CONFIG_SND_HDA_CODEC_CMEDIA=y
CONFIG_SND_HDA_CODEC_SI3054=y
CONFIG_SND_HDA_GENERIC=y
CONFIG_SND_HDA_POWER_SAVE=y
CONFIG_SND_HDA_POWER_SAVE_DEFAULT=0
# CONFIG_SND_HDSP is not set
# CONFIG_SND_HDSPM is not set
# CONFIG_SND_HIFIER is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
# CONFIG_SND_INTEL8X0 is not set
# CONFIG_SND_INTEL8X0M is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_LX6464ES is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_PCXHR is not set
# CONFIG_SND_RIPTIDE is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VIA82XX_MODEM is not set
# CONFIG_SND_VIRTUOSO is not set
# CONFIG_SND_VX222 is not set
# CONFIG_SND_YMFPCI is not set
CONFIG_SND_USB=y
# CONFIG_SND_USB_AUDIO 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_PCMCIA=y
# CONFIG_SND_VXPOCKET is not set
# CONFIG_SND_PDAUDIOCF is not set
# CONFIG_SND_SOC is not set
# CONFIG_SOUND_PRIME is not set
CONFIG_HID_SUPPORT=y
CONFIG_HID=y
# CONFIG_HID_DEBUG is not set
CONFIG_HIDRAW=y
#
# USB Input Devices
#
CONFIG_USB_HID=m
CONFIG_HID_PID=y
# CONFIG_USB_HIDDEV is not set
#
# Special HID drivers
#
CONFIG_HID_A4TECH=m
CONFIG_HID_APPLE=m
CONFIG_HID_BELKIN=m
CONFIG_HID_CHERRY=m
CONFIG_HID_CHICONY=m
CONFIG_HID_CYPRESS=m
CONFIG_HID_DRAGONRISE=m
# CONFIG_DRAGONRISE_FF is not set
CONFIG_HID_EZKEY=m
CONFIG_HID_KYE=m
CONFIG_HID_GYRATION=m
CONFIG_HID_KENSINGTON=m
CONFIG_HID_LOGITECH=m
# CONFIG_LOGITECH_FF is not set
# CONFIG_LOGIRUMBLEPAD2_FF is not set
CONFIG_HID_MICROSOFT=m
CONFIG_HID_MONTEREY=m
CONFIG_HID_NTRIG=m
CONFIG_HID_PANTHERLORD=m
# CONFIG_PANTHERLORD_FF is not set
CONFIG_HID_PETALYNX=m
CONFIG_HID_SAMSUNG=m
CONFIG_HID_SONY=m
CONFIG_HID_SUNPLUS=m
CONFIG_HID_GREENASIA=m
# CONFIG_GREENASIA_FF is not set
CONFIG_HID_SMARTJOYPLUS=m
# CONFIG_SMARTJOYPLUS_FF is not set
CONFIG_HID_TOPSEED=m
CONFIG_HID_THRUSTMASTER=m
# CONFIG_THRUSTMASTER_FF is not set
CONFIG_HID_ZEROPLUS=m
# CONFIG_ZEROPLUS_FF 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 is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
CONFIG_USB_SUSPEND=y
# CONFIG_USB_OTG is not set
CONFIG_USB_MON=y
# 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=y
CONFIG_USB_EHCI_TT_NEWSCHED=y
# CONFIG_USB_OXU210HP_HCD is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_ISP1760_HCD is not set
CONFIG_USB_OHCI_HCD=y
# CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
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 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 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_BERRY_CHARGE 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=m
# CONFIG_USB_SISUSBVGA_CON 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_VST is not set
# CONFIG_USB_ATM is not set
# CONFIG_USB_GADGET is not set
#
# OTG and related infrastructure
#
# CONFIG_TWL4030_USB is not set
# CONFIG_NOP_USB_XCEIV is not set
# CONFIG_UWB is not set
CONFIG_MMC=y
# CONFIG_MMC_DEBUG is not set
# CONFIG_MMC_UNSAFE_RESUME is not set
#
# MMC/SD/SDIO Card Drivers
#
# CONFIG_MMC_BLOCK is not set
# CONFIG_SDIO_UART is not set
# CONFIG_MMC_TEST is not set
#
# MMC/SD/SDIO Host Controller Drivers
#
# CONFIG_MMC_SDHCI is not set
# CONFIG_MMC_WBSD is not set
# CONFIG_MMC_TIFM_SD is not set
# CONFIG_MMC_SDRICOH_CS is not set
# CONFIG_MMC_CB710 is not set
# CONFIG_MMC_VIA_SDMMC is not set
# CONFIG_MEMSTICK is not set
CONFIG_NEW_LEDS=y
CONFIG_LEDS_CLASS=m
#
# LED drivers
#
# CONFIG_LEDS_ALIX2 is not set
# CONFIG_LEDS_PCA9532 is not set
# CONFIG_LEDS_LP3944 is not set
# CONFIG_LEDS_CLEVO_MAIL is not set
# CONFIG_LEDS_PCA955X is not set
# CONFIG_LEDS_DA903X is not set
# CONFIG_LEDS_BD2802 is not set
#
# LED Triggers
#
CONFIG_LEDS_TRIGGERS=y
# CONFIG_LEDS_TRIGGER_TIMER is not set
# CONFIG_LEDS_TRIGGER_HEARTBEAT is not set
# CONFIG_LEDS_TRIGGER_BACKLIGHT is not set
# CONFIG_LEDS_TRIGGER_DEFAULT_ON is not set
#
# iptables trigger is under Netfilter config (LED target)
#
# CONFIG_ACCESSIBILITY is not set
# CONFIG_INFINIBAND is not set
CONFIG_EDAC=y
#
# Reporting subsystems
#
# CONFIG_EDAC_DEBUG is not set
# CONFIG_EDAC_MM_EDAC is not set
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
# CONFIG_RTC_DEBUG is not set
#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
CONFIG_RTC_INTF_DEV_UIE_EMUL=y
# CONFIG_RTC_DRV_TEST is not set
#
# I2C RTC drivers
#
# CONFIG_RTC_DRV_DS1307 is not set
# CONFIG_RTC_DRV_DS1374 is not set
# CONFIG_RTC_DRV_DS1672 is not set
# CONFIG_RTC_DRV_MAX6900 is not set
# CONFIG_RTC_DRV_RS5C372 is not set
# CONFIG_RTC_DRV_ISL1208 is not set
# CONFIG_RTC_DRV_X1205 is not set
# CONFIG_RTC_DRV_PCF8563 is not set
# CONFIG_RTC_DRV_PCF8583 is not set
# CONFIG_RTC_DRV_M41T80 is not set
# CONFIG_RTC_DRV_TWL4030 is not set
# CONFIG_RTC_DRV_S35390A is not set
# CONFIG_RTC_DRV_FM3130 is not set
# CONFIG_RTC_DRV_RX8581 is not set
# CONFIG_RTC_DRV_RX8025 is not set
#
# SPI RTC drivers
#
#
# Platform RTC drivers
#
CONFIG_RTC_DRV_CMOS=y
# CONFIG_RTC_DRV_DS1286 is not set
# CONFIG_RTC_DRV_DS1511 is not set
# CONFIG_RTC_DRV_DS1553 is not set
# CONFIG_RTC_DRV_DS1742 is not set
# CONFIG_RTC_DRV_STK17TA8 is not set
# CONFIG_RTC_DRV_M48T86 is not set
# CONFIG_RTC_DRV_M48T35 is not set
# CONFIG_RTC_DRV_M48T59 is not set
# CONFIG_RTC_DRV_BQ4802 is not set
# CONFIG_RTC_DRV_V3020 is not set
#
# on-CPU RTC drivers
#
CONFIG_DMADEVICES=y
#
# DMA Devices
#
# CONFIG_INTEL_IOATDMA is not set
CONFIG_AUXDISPLAY=y
# CONFIG_UIO is not set
#
# TI VLYNQ
#
# CONFIG_XEN_BALLOON is not set
# CONFIG_XEN_DEV_EVTCHN is not set
# CONFIG_XENFS is not set
# CONFIG_XEN_SYS_HYPERVISOR is not set
# CONFIG_STAGING is not set
CONFIG_X86_PLATFORM_DEVICES=y
# CONFIG_ACER_WMI is not set
# CONFIG_ACERHDF is not set
# CONFIG_ASUS_LAPTOP is not set
# CONFIG_DELL_WMI is not set
# CONFIG_FUJITSU_LAPTOP is not set
# CONFIG_HP_WMI is not set
# CONFIG_MSI_LAPTOP is not set
# CONFIG_PANASONIC_LAPTOP is not set
# CONFIG_COMPAL_LAPTOP is not set
# CONFIG_SONY_LAPTOP is not set
CONFIG_THINKPAD_ACPI=m
CONFIG_THINKPAD_ACPI_DEBUGFACILITIES=y
# CONFIG_THINKPAD_ACPI_DEBUG is not set
# CONFIG_THINKPAD_ACPI_UNSAFE_LEDS is not set
CONFIG_THINKPAD_ACPI_VIDEO=y
CONFIG_THINKPAD_ACPI_HOTKEY_POLL=y
# CONFIG_INTEL_MENLOW is not set
# CONFIG_EEEPC_LAPTOP is not set
CONFIG_ACPI_WMI=y
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_TOSHIBA is not set
#
# Firmware Drivers
#
CONFIG_EDD=y
CONFIG_EDD_OFF=y
CONFIG_FIRMWARE_MEMMAP=y
CONFIG_EFI_VARS=y
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not set
CONFIG_DMIID=y
CONFIG_ISCSI_IBFT_FIND=y
# CONFIG_ISCSI_IBFT is not set
#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_FS=y
# CONFIG_EXT3_DEFAULTS_TO_ORDERED is not set
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_EXT4_FS=y
# CONFIG_EXT4DEV_COMPAT is not set
CONFIG_EXT4_FS_XATTR=y
CONFIG_EXT4_FS_POSIX_ACL=y
CONFIG_EXT4_FS_SECURITY=y
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_JBD2=y
# CONFIG_JBD2_DEBUG is not set
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
# CONFIG_XFS_FS is not set
# CONFIG_GFS2_FS is not set
# CONFIG_OCFS2_FS is not set
# CONFIG_BTRFS_FS is not set
CONFIG_FILE_LOCKING=y
CONFIG_FSNOTIFY=y
CONFIG_DNOTIFY=y
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
CONFIG_QUOTA=y
CONFIG_QUOTA_NETLINK_INTERFACE=y
CONFIG_PRINT_QUOTA_WARNING=y
# CONFIG_QFMT_V1 is not set
# CONFIG_QFMT_V2 is not set
CONFIG_QUOTACTL=y
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
CONFIG_FUSE_FS=y
# CONFIG_CUSE is not set
CONFIG_GENERIC_ACL=y
#
# Caches
#
# CONFIG_FSCACHE is not set
#
# CD-ROM/DVD Filesystems
#
# CONFIG_ISO9660_FS is not set
# CONFIG_UDF_FS is not set
#
# DOS/FAT/NT Filesystems
#
# CONFIG_MSDOS_FS is not set
# CONFIG_VFAT_FS is not set
# CONFIG_NTFS_FS is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_VMCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
# CONFIG_CONFIGFS_FS is not set
CONFIG_MISC_FILESYSTEMS=y
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
CONFIG_ECRYPT_FS=y
# 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_CRAMFS=y
# 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_NILFS2_FS is not set
CONFIG_NETWORK_FILESYSTEMS=y
# CONFIG_NFS_FS is not set
# CONFIG_NFSD is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS 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=y
CONFIG_ACORN_PARTITION=y
# CONFIG_ACORN_PARTITION_CUMANA is not set
# CONFIG_ACORN_PARTITION_EESOX is not set
CONFIG_ACORN_PARTITION_ICS=y
# CONFIG_ACORN_PARTITION_ADFS is not set
# CONFIG_ACORN_PARTITION_POWERTEC is not set
CONFIG_ACORN_PARTITION_RISCIX=y
CONFIG_OSF_PARTITION=y
CONFIG_AMIGA_PARTITION=y
CONFIG_ATARI_PARTITION=y
CONFIG_MAC_PARTITION=y
CONFIG_MSDOS_PARTITION=y
CONFIG_BSD_DISKLABEL=y
CONFIG_MINIX_SUBPARTITION=y
CONFIG_SOLARIS_X86_PARTITION=y
CONFIG_UNIXWARE_DISKLABEL=y
CONFIG_LDM_PARTITION=y
# CONFIG_LDM_DEBUG is not set
CONFIG_SGI_PARTITION=y
CONFIG_ULTRIX_PARTITION=y
CONFIG_SUN_PARTITION=y
CONFIG_KARMA_PARTITION=y
CONFIG_EFI_PARTITION=y
CONFIG_SYSV68_PARTITION=y
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="cp437"
# CONFIG_NLS_CODEPAGE_437 is not set
# 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 is not set
# 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=y
# CONFIG_ENABLE_WARN_DEPRECATED is not set
# CONFIG_ENABLE_MUST_CHECK is not set
CONFIG_FRAME_WARN=1024
CONFIG_MAGIC_SYSRQ=y
CONFIG_UNUSED_SYMBOLS=y
CONFIG_DEBUG_FS=y
# CONFIG_HEADERS_CHECK is not set
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SHIRQ is not set
CONFIG_DETECT_SOFTLOCKUP=y
# CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC is not set
CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=0
CONFIG_DETECT_HUNG_TASK=y
# CONFIG_BOOTPARAM_HUNG_TASK_PANIC is not set
CONFIG_BOOTPARAM_HUNG_TASK_PANIC_VALUE=0
CONFIG_SCHED_DEBUG=y
CONFIG_SCHEDSTATS=y
CONFIG_TIMER_STATS=y
# CONFIG_DEBUG_OBJECTS is not set
# CONFIG_SLUB_DEBUG_ON is not set
# CONFIG_SLUB_STATS is not set
CONFIG_DEBUG_KMEMLEAK=y
CONFIG_DEBUG_KMEMLEAK_EARLY_LOG_SIZE=400
# CONFIG_DEBUG_KMEMLEAK_TEST is not set
CONFIG_DEBUG_RT_MUTEXES=y
CONFIG_DEBUG_PI_LIST=y
CONFIG_RT_MUTEX_TESTER=y
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_MUTEXES=y
CONFIG_DEBUG_LOCK_ALLOC=y
CONFIG_PROVE_LOCKING=y
CONFIG_LOCKDEP=y
# CONFIG_LOCK_STAT is not set
CONFIG_DEBUG_LOCKDEP=y
CONFIG_TRACE_IRQFLAGS=y
CONFIG_DEBUG_SPINLOCK_SLEEP=y
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
CONFIG_STACKTRACE=y
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_DEBUG_INFO=y
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_VIRTUAL is not set
# CONFIG_DEBUG_WRITECOUNT is not set
CONFIG_DEBUG_MEMORY_INIT=y
# CONFIG_DEBUG_LIST is not set
# CONFIG_DEBUG_SG is not set
# CONFIG_DEBUG_NOTIFIERS is not set
CONFIG_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_KPROBES_SANITY_TEST is not set
# CONFIG_BACKTRACE_SELF_TEST is not set
# CONFIG_DEBUG_BLOCK_EXT_DEVT is not set
# CONFIG_LKDTM is not set
# CONFIG_FAULT_INJECTION is not set
CONFIG_LATENCYTOP=y
CONFIG_SYSCTL_SYSCALL_CHECK=y
# CONFIG_DEBUG_PAGEALLOC is not set
CONFIG_USER_STACKTRACE_SUPPORT=y
CONFIG_NOP_TRACER=y
CONFIG_HAVE_FUNCTION_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_FP_TEST=y
CONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=y
CONFIG_HAVE_DYNAMIC_FTRACE=y
CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y
CONFIG_HAVE_FTRACE_SYSCALLS=y
CONFIG_RING_BUFFER=y
CONFIG_EVENT_TRACING=y
CONFIG_CONTEXT_SWITCH_TRACER=y
CONFIG_TRACING=y
CONFIG_GENERIC_TRACER=y
CONFIG_TRACING_SUPPORT=y
CONFIG_FTRACE=y
# CONFIG_FUNCTION_TRACER is not set
# CONFIG_IRQSOFF_TRACER is not set
# CONFIG_SYSPROF_TRACER is not set
# CONFIG_SCHED_TRACER is not set
# CONFIG_FTRACE_SYSCALLS is not set
# CONFIG_BOOT_TRACER is not set
CONFIG_BRANCH_PROFILE_NONE=y
# CONFIG_PROFILE_ANNOTATED_BRANCHES is not set
# CONFIG_PROFILE_ALL_BRANCHES is not set
# CONFIG_POWER_TRACER is not set
# CONFIG_STACK_TRACER is not set
# CONFIG_KMEMTRACE is not set
# CONFIG_WORKQUEUE_TRACER is not set
CONFIG_BLK_DEV_IO_TRACE=y
# CONFIG_FTRACE_STARTUP_TEST is not set
# CONFIG_MMIOTRACE is not set
# CONFIG_RING_BUFFER_BENCHMARK is not set
# CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set
# CONFIG_DYNAMIC_DEBUG is not set
# CONFIG_DMA_API_DEBUG is not set
# CONFIG_SAMPLES is not set
CONFIG_HAVE_ARCH_KGDB=y
CONFIG_KGDB=y
CONFIG_KGDB_SERIAL_CONSOLE=y
# CONFIG_KGDB_TESTS is not set
CONFIG_HAVE_ARCH_KMEMCHECK=y
# CONFIG_KMEMCHECK is not set
CONFIG_STRICT_DEVMEM=y
# CONFIG_X86_VERBOSE_BOOTUP is not set
CONFIG_EARLY_PRINTK=y
# CONFIG_EARLY_PRINTK_DBGP is not set
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_PER_CPU_MAPS is not set
# CONFIG_X86_PTDUMP is not set
CONFIG_DEBUG_RODATA=y
# CONFIG_DEBUG_RODATA_TEST is not set
# CONFIG_DEBUG_NX_TEST is not set
# CONFIG_IOMMU_DEBUG is not set
# CONFIG_IOMMU_STRESS is not set
CONFIG_HAVE_MMIOTRACE_SUPPORT=y
CONFIG_IO_DELAY_TYPE_0X80=0
CONFIG_IO_DELAY_TYPE_0XED=1
CONFIG_IO_DELAY_TYPE_UDELAY=2
CONFIG_IO_DELAY_TYPE_NONE=3
# CONFIG_IO_DELAY_0X80 is not set
CONFIG_IO_DELAY_0XED=y
# CONFIG_IO_DELAY_UDELAY is not set
# CONFIG_IO_DELAY_NONE is not set
CONFIG_DEFAULT_IO_DELAY_TYPE=1
# CONFIG_DEBUG_BOOT_PARAMS is not set
# CONFIG_CPA_DEBUG is not set
CONFIG_OPTIMIZE_INLINING=y
#
# Security options
#
CONFIG_KEYS=y
# CONFIG_KEYS_DEBUG_PROC_KEYS is not set
CONFIG_SECURITY=y
CONFIG_SECURITYFS=y
CONFIG_SECURITY_NETWORK=y
CONFIG_SECURITY_PATH=y
CONFIG_SECURITY_FILE_CAPABILITIES=y
# CONFIG_SECURITY_ROOTPLUG is not set
CONFIG_LSM_MMAP_MIN_ADDR=65536
CONFIG_SECURITY_SELINUX=y
CONFIG_SECURITY_SELINUX_BOOTPARAM=y
CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=0
CONFIG_SECURITY_SELINUX_DISABLE=y
CONFIG_SECURITY_SELINUX_DEVELOP=y
CONFIG_SECURITY_SELINUX_AVC_STATS=y
CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE=1
# CONFIG_SECURITY_SELINUX_POLICYDB_VERSION_MAX is not set
CONFIG_SECURITY_SMACK=y
CONFIG_SECURITY_TOMOYO=y
# CONFIG_IMA is not set
CONFIG_CRYPTO=y
#
# Crypto core or helper
#
CONFIG_CRYPTO_FIPS=y
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ALGAPI2=y
CONFIG_CRYPTO_AEAD2=y
CONFIG_CRYPTO_BLKCIPHER=y
CONFIG_CRYPTO_BLKCIPHER2=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_HASH2=y
CONFIG_CRYPTO_RNG2=y
CONFIG_CRYPTO_PCOMP=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_MANAGER2=y
# CONFIG_CRYPTO_GF128MUL is not set
# CONFIG_CRYPTO_NULL is not set
CONFIG_CRYPTO_WORKQUEUE=y
# 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=y
# CONFIG_CRYPTO_LRW is not set
# CONFIG_CRYPTO_PCBC is not set
# CONFIG_CRYPTO_XTS is not set
#
# Hash modes
#
CONFIG_CRYPTO_HMAC=y
# CONFIG_CRYPTO_XCBC is not set
#
# Digest
#
# CONFIG_CRYPTO_CRC32C is not set
# CONFIG_CRYPTO_CRC32C_INTEL is not set
# CONFIG_CRYPTO_MD4 is not set
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_MICHAEL_MIC=y
# 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=y
# CONFIG_CRYPTO_AES_X86_64 is not set
# CONFIG_CRYPTO_AES_NI_INTEL is not set
# CONFIG_CRYPTO_ANUBIS is not set
CONFIG_CRYPTO_ARC4=y
# 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_X86_64 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_X86_64 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=y
# CONFIG_CRYPTO_DEV_PADLOCK_AES is not set
# CONFIG_CRYPTO_DEV_PADLOCK_SHA is not set
# CONFIG_CRYPTO_DEV_HIFN_795X is not set
CONFIG_HAVE_KVM=y
CONFIG_HAVE_KVM_IRQCHIP=y
CONFIG_VIRTUALIZATION=y
CONFIG_KVM=m
CONFIG_KVM_INTEL=m
# CONFIG_KVM_AMD is not set
# CONFIG_KVM_TRACE is not set
# CONFIG_VIRTIO_PCI is not set
# CONFIG_VIRTIO_BALLOON is not set
CONFIG_BINARY_PRINTF=y
#
# Library routines
#
CONFIG_BITREVERSE=y
CONFIG_GENERIC_FIND_FIRST_BIT=y
CONFIG_GENERIC_FIND_NEXT_BIT=y
CONFIG_GENERIC_FIND_LAST_BIT=y
CONFIG_CRC_CCITT=m
CONFIG_CRC16=y
CONFIG_CRC_T10DIF=y
CONFIG_CRC_ITU_T=m
CONFIG_CRC32=y
CONFIG_CRC7=m
# CONFIG_LIBCRC32C is not set
CONFIG_ZLIB_INFLATE=y
CONFIG_DECOMPRESS_GZIP=y
CONFIG_DECOMPRESS_BZIP2=y
CONFIG_DECOMPRESS_LZMA=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y
CONFIG_NLATTR=y
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: memleaks, acpi + ext4 + tty
2009-08-28 16:52 ` Luis R. Rodriguez
@ 2009-08-28 21:50 ` Luis R. Rodriguez
2009-08-28 22:09 ` Luis R. Rodriguez
2009-08-29 21:41 ` Catalin Marinas
1 sibling, 1 reply; 26+ messages in thread
From: Luis R. Rodriguez @ 2009-08-28 21:50 UTC (permalink / raw)
To: Catalin Marinas; +Cc: linux-kernel, Aneesh Kumar K.V, Greg Kroah-Hartman
On Fri, Aug 28, 2009 at 9:52 AM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
> On Fri, Aug 28, 2009 at 9:32 AM, Catalin Marinas<catalin.marinas@arm.com> wrote:
>> "Luis R. Rodriguez" <mcgrof@gmail.com> wrote:
>>> I have an assorted collection of kmemleak reports for acpi, ext4 and
>>> tty, not sure how to read these yet to fix so figure I'd at least post
>>> them. To reproduce I can just dd=/dev/zero to some big file and played
>>> some video.
>>
>> If you do a few echo scan > /sys/kernel/debug/kmemleak, do they
>> disappear (i.e. transient false positives)?
>
> Sure, I will once on rc8.
>
>> Which kernel version is this?
>
> v2.6.31-rc7-33172-gf4a9f9a
>
> This is from wireless-testing, which has wireless patches on top of
> rc7. John just rebased to rc8 so will give that a shot at work.
>
>>> unreferenced object 0xffff88003e0015c0 (size 64):
>>> comm "swapper", pid 1, jiffies 4294892352
>>> backtrace:
>>> [<ffffffff81121fad>] create_object+0x13d/0x2d0
>>> [<ffffffff81122265>] kmemleak_alloc+0x25/0x60
>>> [<ffffffff81118a03>] kmem_cache_alloc_node+0x193/0x200
>>> [<ffffffff8152509e>] process_zones+0x70/0x1cd
>>> [<ffffffff81525230>] pageset_cpuup_callback+0x35/0x92
>>> [<ffffffff8152c9b7>] notifier_call_chain+0x47/0x90
>>> [<ffffffff81078549>] __raw_notifier_call_chain+0x9/0x10
>>> [<ffffffff81523f25>] _cpu_up+0x75/0x130
>>> [<ffffffff8152403a>] cpu_up+0x5a/0x6a
>>> [<ffffffff8181969e>] kernel_init+0xcc/0x1ba
>>> [<ffffffff810130ca>] child_rip+0xa/0x20
>>> [<ffffffffffffffff>] 0xffffffffffffffff
>>
>> Can't really tell. Maybe a false positive caused by kmemleak not
>> scanning the pgdata node_zones. Can you post your .config file?
>
> Sure, attached.
>
>>> unreferenced object 0xffff88003cb5f700 (size 64):
>>> comm "swapper", pid 1, jiffies 4294892459
>>> backtrace:
>>> [<ffffffff81121fad>] create_object+0x13d/0x2d0
>>> [<ffffffff81122265>] kmemleak_alloc+0x25/0x60
>>> [<ffffffff81119f3b>] __kmalloc+0x16b/0x250
>>> [<ffffffff812bb549>] kzalloc+0xf/0x11
>>> [<ffffffff812bbb53>] acpi_add_single_object+0x58e/0xd3c
>>> [<ffffffff812bc51c>] acpi_bus_scan+0x125/0x1af
>>> [<ffffffff81842361>] acpi_scan_init+0xc8/0xe9
>>> [<ffffffff8184211c>] acpi_init+0x21f/0x265
>>> [<ffffffff8100a05b>] do_one_initcall+0x4b/0x1b0
>>> [<ffffffff81819736>] kernel_init+0x164/0x1ba
>>> [<ffffffff810130ca>] child_rip+0xa/0x20
>>> [<ffffffffffffffff>] 0xffffffffffffffff
>>
>> I get ACPI reports as well and they may be real leaks. However, I
>> didn't have time to analyse the code (pretty complicated reference
>> counting).
>
> Heh OK thanks for reviewing them though.
>
>>> unreferenced object 0xffff880039571800 (size 1024):
>>> comm "exe", pid 1168, jiffies 4294893410
>>> backtrace:
>>> [<ffffffff81121fad>] create_object+0x13d/0x2d0
>>> [<ffffffff81122265>] kmemleak_alloc+0x25/0x60
>>> [<ffffffff81119f3b>] __kmalloc+0x16b/0x250
>>> [<ffffffff811e1d71>] ext4_mb_init+0x1a1/0x590
>>> [<ffffffff811d2da3>] ext4_fill_super+0x1df3/0x26c0
>>> [<ffffffff8112774f>] get_sb_bdev+0x16f/0x1b0
>>> [<ffffffff811c8fd3>] ext4_get_sb+0x13/0x20
>>> [<ffffffff81127216>] vfs_kern_mount+0x76/0x180
>>> [<ffffffff8112738d>] do_kern_mount+0x4d/0x130
>>> [<ffffffff8113fc57>] do_mount+0x307/0x8b0
>>> [<ffffffff8114028f>] sys_mount+0x8f/0xe0
>>> [<ffffffff81011f02>] system_call_fastpath+0x16/0x1b
>>> [<ffffffffffffffff>] 0xffffffffffffffff
>>
>> The ext4 reports are real leaks and patch was posted here -
>> http://lkml.org/lkml/2009/7/15/62. However, it hasn't been merged into
>> mainline yet (I cc'ed Aneesh).
>>
>> The patch is merged in my "kmemleak-fixes" branch on
>> git://linux-arm.org/linux-2.6.git.
>
> Will try to suck them out and try them.
OK -- tested rc8 + a pull of your tree into mine. The bootup was
really slow and something was just not going right. After a while
memleak complained it had 8 kmemleak logs but I was not able to get my
system usable enough to cat the file.
In cases like these I wish I would hookup my ctrl-alt-del to kexec() a
safe kernel.
After a long period of time it seems X wished it would start, it tried
and then flashed back to the tty. This kept repeating in a loop.
I am not sure if the culprit was rc8 or the kmemleak branch merge --
I'll find out after I boot into rc8 in a few.
These issues seem to be serious blockers, I don't tend to use video
play but I suspect others do, after a decent amount of time playing
the system becomes completely unusable. If you have any other patch
suggestions let me know. I'll try to read the kmemleak docs too, maybe
I can try to figure some of these out.
Luis
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: memleaks, acpi + ext4 + tty
2009-08-28 21:50 ` Luis R. Rodriguez
@ 2009-08-28 22:09 ` Luis R. Rodriguez
2009-08-31 8:23 ` Luis R. Rodriguez
0 siblings, 1 reply; 26+ messages in thread
From: Luis R. Rodriguez @ 2009-08-28 22:09 UTC (permalink / raw)
To: Catalin Marinas; +Cc: linux-kernel, Aneesh Kumar K.V, Greg Kroah-Hartman
On Fri, Aug 28, 2009 at 2:50 PM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
> On Fri, Aug 28, 2009 at 9:52 AM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
>> On Fri, Aug 28, 2009 at 9:32 AM, Catalin Marinas<catalin.marinas@arm.com> wrote:
>>> "Luis R. Rodriguez" <mcgrof@gmail.com> wrote:
>>>> I have an assorted collection of kmemleak reports for acpi, ext4 and
>>>> tty, not sure how to read these yet to fix so figure I'd at least post
>>>> them. To reproduce I can just dd=/dev/zero to some big file and played
>>>> some video.
>>>
>>> If you do a few echo scan > /sys/kernel/debug/kmemleak, do they
>>> disappear (i.e. transient false positives)?
>>
>> Sure, I will once on rc8.
>>
>>> Which kernel version is this?
>>
>> v2.6.31-rc7-33172-gf4a9f9a
>>
>> This is from wireless-testing, which has wireless patches on top of
>> rc7. John just rebased to rc8 so will give that a shot at work.
>>
>>>> unreferenced object 0xffff88003e0015c0 (size 64):
>>>> comm "swapper", pid 1, jiffies 4294892352
>>>> backtrace:
>>>> [<ffffffff81121fad>] create_object+0x13d/0x2d0
>>>> [<ffffffff81122265>] kmemleak_alloc+0x25/0x60
>>>> [<ffffffff81118a03>] kmem_cache_alloc_node+0x193/0x200
>>>> [<ffffffff8152509e>] process_zones+0x70/0x1cd
>>>> [<ffffffff81525230>] pageset_cpuup_callback+0x35/0x92
>>>> [<ffffffff8152c9b7>] notifier_call_chain+0x47/0x90
>>>> [<ffffffff81078549>] __raw_notifier_call_chain+0x9/0x10
>>>> [<ffffffff81523f25>] _cpu_up+0x75/0x130
>>>> [<ffffffff8152403a>] cpu_up+0x5a/0x6a
>>>> [<ffffffff8181969e>] kernel_init+0xcc/0x1ba
>>>> [<ffffffff810130ca>] child_rip+0xa/0x20
>>>> [<ffffffffffffffff>] 0xffffffffffffffff
>>>
>>> Can't really tell. Maybe a false positive caused by kmemleak not
>>> scanning the pgdata node_zones. Can you post your .config file?
>>
>> Sure, attached.
>>
>>>> unreferenced object 0xffff88003cb5f700 (size 64):
>>>> comm "swapper", pid 1, jiffies 4294892459
>>>> backtrace:
>>>> [<ffffffff81121fad>] create_object+0x13d/0x2d0
>>>> [<ffffffff81122265>] kmemleak_alloc+0x25/0x60
>>>> [<ffffffff81119f3b>] __kmalloc+0x16b/0x250
>>>> [<ffffffff812bb549>] kzalloc+0xf/0x11
>>>> [<ffffffff812bbb53>] acpi_add_single_object+0x58e/0xd3c
>>>> [<ffffffff812bc51c>] acpi_bus_scan+0x125/0x1af
>>>> [<ffffffff81842361>] acpi_scan_init+0xc8/0xe9
>>>> [<ffffffff8184211c>] acpi_init+0x21f/0x265
>>>> [<ffffffff8100a05b>] do_one_initcall+0x4b/0x1b0
>>>> [<ffffffff81819736>] kernel_init+0x164/0x1ba
>>>> [<ffffffff810130ca>] child_rip+0xa/0x20
>>>> [<ffffffffffffffff>] 0xffffffffffffffff
>>>
>>> I get ACPI reports as well and they may be real leaks. However, I
>>> didn't have time to analyse the code (pretty complicated reference
>>> counting).
>>
>> Heh OK thanks for reviewing them though.
>>
>>>> unreferenced object 0xffff880039571800 (size 1024):
>>>> comm "exe", pid 1168, jiffies 4294893410
>>>> backtrace:
>>>> [<ffffffff81121fad>] create_object+0x13d/0x2d0
>>>> [<ffffffff81122265>] kmemleak_alloc+0x25/0x60
>>>> [<ffffffff81119f3b>] __kmalloc+0x16b/0x250
>>>> [<ffffffff811e1d71>] ext4_mb_init+0x1a1/0x590
>>>> [<ffffffff811d2da3>] ext4_fill_super+0x1df3/0x26c0
>>>> [<ffffffff8112774f>] get_sb_bdev+0x16f/0x1b0
>>>> [<ffffffff811c8fd3>] ext4_get_sb+0x13/0x20
>>>> [<ffffffff81127216>] vfs_kern_mount+0x76/0x180
>>>> [<ffffffff8112738d>] do_kern_mount+0x4d/0x130
>>>> [<ffffffff8113fc57>] do_mount+0x307/0x8b0
>>>> [<ffffffff8114028f>] sys_mount+0x8f/0xe0
>>>> [<ffffffff81011f02>] system_call_fastpath+0x16/0x1b
>>>> [<ffffffffffffffff>] 0xffffffffffffffff
>>>
>>> The ext4 reports are real leaks and patch was posted here -
>>> http://lkml.org/lkml/2009/7/15/62. However, it hasn't been merged into
>>> mainline yet (I cc'ed Aneesh).
>>>
>>> The patch is merged in my "kmemleak-fixes" branch on
>>> git://linux-arm.org/linux-2.6.git.
>>
>> Will try to suck them out and try them.
>
> OK -- tested rc8 + a pull of your tree into mine. The bootup was
> really slow and something was just not going right. After a while
> memleak complained it had 8 kmemleak logs but I was not able to get my
> system usable enough to cat the file.
>
> In cases like these I wish I would hookup my ctrl-alt-del to kexec() a
> safe kernel.
>
> After a long period of time it seems X wished it would start, it tried
> and then flashed back to the tty. This kept repeating in a loop.
>
> I am not sure if the culprit was rc8 or the kmemleak branch merge --
> I'll find out after I boot into rc8 in a few.
rc8 busted my bootup, the issues are present with just
wireless-testing. I highly doubt the issues are wireless-testing
related so I will not bisect there. Since I am unable to get anything
useful from the kernel to determine what may have gone sour, any
suggestions on a path to bisect, or should I just do the whole tree?
Luis
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: memleaks, acpi + ext4 + tty
2009-08-28 16:52 ` Luis R. Rodriguez
2009-08-28 21:50 ` Luis R. Rodriguez
@ 2009-08-29 21:41 ` Catalin Marinas
1 sibling, 0 replies; 26+ messages in thread
From: Catalin Marinas @ 2009-08-29 21:41 UTC (permalink / raw)
To: Luis R. Rodriguez; +Cc: linux-kernel, Aneesh Kumar K.V, Greg Kroah-Hartman
On Fri, 2009-08-28 at 09:52 -0700, Luis R. Rodriguez wrote:
> On Fri, Aug 28, 2009 at 9:32 AM, Catalin
> Marinas<catalin.marinas@arm.com> wrote:
> > "Luis R. Rodriguez" <mcgrof@gmail.com> wrote:
> >> unreferenced object 0xffff880006ce0400 (size 1024):
> >> comm "mplayer", pid 5293, jiffies 4295366945
> >> backtrace:
> >> [<ffffffff81121fad>] create_object+0x13d/0x2d0
> >> [<ffffffff81122265>] kmemleak_alloc+0x25/0x60
> >> [<ffffffff81119f3b>] __kmalloc+0x16b/0x250
> >> [<ffffffff813021b0>] tty_buffer_request_room+0xc0/0x190
> >> [<ffffffff8130244c>] tty_insert_flip_string+0x3c/0xb0
> >> [<ffffffff81302f49>] pty_write+0x49/0x70
> >> [<ffffffff812fd3b0>] n_tty_write+0x1c0/0x450
> >> [<ffffffff812f9ec1>] tty_write+0x1a1/0x290
> >> [<ffffffff81124518>] vfs_write+0xb8/0x1a0
> >> [<ffffffff81124fcc>] sys_write+0x4c/0x80
> >> [<ffffffff81011f02>] system_call_fastpath+0x16/0x1b
> >> [<ffffffffffffffff>] 0xffffffffffffffff
> >
> > It could be a real leak as you get several of these. I cc'ed Greg KH
> > for any suggestions he may have. It looks like it only happens when
> > running mplayer.
>
> It took me a while to figure out how to reproduce, and it really
> didn't make sense to see this playing video, why would playing video
> affect tty?
Maybe mplayer is just opening the tty for some user interaction.
I managed to the same report just using "top" but it is not persistent,
so it may be a false positive.
--
Catalin
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: memleaks, acpi + ext4 + tty
2009-08-28 16:32 ` Catalin Marinas
2009-08-28 16:52 ` Luis R. Rodriguez
@ 2009-08-30 16:34 ` Aneesh Kumar K.V
2009-08-30 17:17 ` Theodore Tso
1 sibling, 1 reply; 26+ messages in thread
From: Aneesh Kumar K.V @ 2009-08-30 16:34 UTC (permalink / raw)
To: Catalin Marinas, Theodore Tso
Cc: Luis R. Rodriguez, linux-kernel, Greg Kroah-Hartman
On Fri, Aug 28, 2009 at 05:32:10PM +0100, Catalin Marinas wrote:
> "Luis R. Rodriguez" <mcgrof@gmail.com> wrote:
> > I have an assorted collection of kmemleak reports for acpi, ext4 and
> > tty, not sure how to read these yet to fix so figure I'd at least post
> > them. To reproduce I can just dd=/dev/zero to some big file and played
> > some video.
>
> If you do a few echo scan > /sys/kernel/debug/kmemleak, do they
> disappear (i.e. transient false positives)?
>
> Which kernel version is this?
>
> > unreferenced object 0xffff88003e0015c0 (size 64):
> > comm "swapper", pid 1, jiffies 4294892352
> > backtrace:
> > [<ffffffff81121fad>] create_object+0x13d/0x2d0
> > [<ffffffff81122265>] kmemleak_alloc+0x25/0x60
> > [<ffffffff81118a03>] kmem_cache_alloc_node+0x193/0x200
> > [<ffffffff8152509e>] process_zones+0x70/0x1cd
> > [<ffffffff81525230>] pageset_cpuup_callback+0x35/0x92
> > [<ffffffff8152c9b7>] notifier_call_chain+0x47/0x90
> > [<ffffffff81078549>] __raw_notifier_call_chain+0x9/0x10
> > [<ffffffff81523f25>] _cpu_up+0x75/0x130
> > [<ffffffff8152403a>] cpu_up+0x5a/0x6a
> > [<ffffffff8181969e>] kernel_init+0xcc/0x1ba
> > [<ffffffff810130ca>] child_rip+0xa/0x20
> > [<ffffffffffffffff>] 0xffffffffffffffff
>
> Can't really tell. Maybe a false positive caused by kmemleak not
> scanning the pgdata node_zones. Can you post your .config file?
>
> > unreferenced object 0xffff88003cb5f700 (size 64):
> > comm "swapper", pid 1, jiffies 4294892459
> > backtrace:
> > [<ffffffff81121fad>] create_object+0x13d/0x2d0
> > [<ffffffff81122265>] kmemleak_alloc+0x25/0x60
> > [<ffffffff81119f3b>] __kmalloc+0x16b/0x250
> > [<ffffffff812bb549>] kzalloc+0xf/0x11
> > [<ffffffff812bbb53>] acpi_add_single_object+0x58e/0xd3c
> > [<ffffffff812bc51c>] acpi_bus_scan+0x125/0x1af
> > [<ffffffff81842361>] acpi_scan_init+0xc8/0xe9
> > [<ffffffff8184211c>] acpi_init+0x21f/0x265
> > [<ffffffff8100a05b>] do_one_initcall+0x4b/0x1b0
> > [<ffffffff81819736>] kernel_init+0x164/0x1ba
> > [<ffffffff810130ca>] child_rip+0xa/0x20
> > [<ffffffffffffffff>] 0xffffffffffffffff
>
> I get ACPI reports as well and they may be real leaks. However, I
> didn't have time to analyse the code (pretty complicated reference
> counting).
>
> > unreferenced object 0xffff880039571800 (size 1024):
> > comm "exe", pid 1168, jiffies 4294893410
> > backtrace:
> > [<ffffffff81121fad>] create_object+0x13d/0x2d0
> > [<ffffffff81122265>] kmemleak_alloc+0x25/0x60
> > [<ffffffff81119f3b>] __kmalloc+0x16b/0x250
> > [<ffffffff811e1d71>] ext4_mb_init+0x1a1/0x590
> > [<ffffffff811d2da3>] ext4_fill_super+0x1df3/0x26c0
> > [<ffffffff8112774f>] get_sb_bdev+0x16f/0x1b0
> > [<ffffffff811c8fd3>] ext4_get_sb+0x13/0x20
> > [<ffffffff81127216>] vfs_kern_mount+0x76/0x180
> > [<ffffffff8112738d>] do_kern_mount+0x4d/0x130
> > [<ffffffff8113fc57>] do_mount+0x307/0x8b0
> > [<ffffffff8114028f>] sys_mount+0x8f/0xe0
> > [<ffffffff81011f02>] system_call_fastpath+0x16/0x1b
> > [<ffffffffffffffff>] 0xffffffffffffffff
>
> The ext4 reports are real leaks and patch was posted here -
> http://lkml.org/lkml/2009/7/15/62. However, it hasn't been merged into
> mainline yet (I cc'ed Aneesh).
>
The patch is part of ext4-patchqueue http://repo.or.cz/w/ext4-patch-queue.git
Ted,
Any plans to push the patches to linus tree soon ?
-aneesh
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: memleaks, acpi + ext4 + tty
2009-08-30 16:34 ` Aneesh Kumar K.V
@ 2009-08-30 17:17 ` Theodore Tso
2009-08-30 17:29 ` Luis R. Rodriguez
0 siblings, 1 reply; 26+ messages in thread
From: Theodore Tso @ 2009-08-30 17:17 UTC (permalink / raw)
To: Aneesh Kumar K.V
Cc: Catalin Marinas, Luis R. Rodriguez, linux-kernel, Greg Kroah-Hartman
On Sun, Aug 30, 2009 at 10:04:17PM +0530, Aneesh Kumar K.V wrote:
> > The ext4 reports are real leaks and patch was posted here -
> > http://lkml.org/lkml/2009/7/15/62. However, it hasn't been merged into
> > mainline yet (I cc'ed Aneesh).
>
> The patch is part of ext4-patchqueue http://repo.or.cz/w/ext4-patch-queue.git
>
> Any plans to push the patches to linus tree soon ?
Yes, as soon as the next merge window opens. The leak only shows up
when you mount and unmount a filesystem, which under normal
circumstances doesn't happen a huge number of times on most systems.
By the time it showed up it was late enough in the 2.6.31-rcX series
that I figured it was better to wait until the next merge window. I
didn't consider it a high priority bug.
- Ted
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: memleaks, acpi + ext4 + tty
2009-08-30 17:17 ` Theodore Tso
@ 2009-08-30 17:29 ` Luis R. Rodriguez
2009-08-30 18:24 ` Theodore Tso
0 siblings, 1 reply; 26+ messages in thread
From: Luis R. Rodriguez @ 2009-08-30 17:29 UTC (permalink / raw)
To: Theodore Tso, Aneesh Kumar K.V, Catalin Marinas,
Luis R. Rodriguez, linux-kernel, Greg Kroah-Hartman
On Sun, Aug 30, 2009 at 10:17 AM, Theodore Tso<tytso@mit.edu> wrote:
> On Sun, Aug 30, 2009 at 10:04:17PM +0530, Aneesh Kumar K.V wrote:
>> > The ext4 reports are real leaks and patch was posted here -
>> > http://lkml.org/lkml/2009/7/15/62. However, it hasn't been merged into
>> > mainline yet (I cc'ed Aneesh).
>>
>> The patch is part of ext4-patchqueue http://repo.or.cz/w/ext4-patch-queue.git
>>
>> Any plans to push the patches to linus tree soon ?
>
> Yes, as soon as the next merge window opens. The leak only shows up
> when you mount and unmount a filesystem, which under normal
> circumstances doesn't happen a huge number of times on most systems.
> By the time it showed up it was late enough in the 2.6.31-rcX series
> that I figured it was better to wait until the next merge window. I
> didn't consider it a high priority bug.
That's odd I run into this kmemleak with a single bootup, no manual remounts.
Luis
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: memleaks, acpi + ext4 + tty
2009-08-30 17:29 ` Luis R. Rodriguez
@ 2009-08-30 18:24 ` Theodore Tso
2009-09-01 17:59 ` Luis R. Rodriguez
0 siblings, 1 reply; 26+ messages in thread
From: Theodore Tso @ 2009-08-30 18:24 UTC (permalink / raw)
To: Luis R. Rodriguez
Cc: Aneesh Kumar K.V, Catalin Marinas, linux-kernel, Greg Kroah-Hartman
On Sun, Aug 30, 2009 at 10:29:01AM -0700, Luis R. Rodriguez wrote:
> > Yes, as soon as the next merge window opens. The leak only shows up
> > when you mount and unmount a filesystem, which under normal
> > circumstances doesn't happen a huge number of times on most systems.
> > By the time it showed up it was late enough in the 2.6.31-rcX series
> > that I figured it was better to wait until the next merge window. I
> > didn't consider it a high priority bug.
>
> That's odd I run into this kmemleak with a single bootup, no manual remounts.
>
Yeah, but it's a singleton leak. Let me be a bit more precise this
time: the leak happens at mount time because we're essentially doing
this due to some code that was accidentally duplicated when it was
being refactored:
a = kmalloc(sizeof(...)*N, GFP_ATOMIC);
...
a = kmalloc(sizeof(...)*N, GFP_ATOMIC);
So a small amount of memory is leaked each time a filesystem is
mounted. It doesn't become a huge problem unless you are repeatedly
mounting and unmounting the same filesystem in a tight loop.
- Ted
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: memleaks, acpi + ext4 + tty
2009-08-28 22:09 ` Luis R. Rodriguez
@ 2009-08-31 8:23 ` Luis R. Rodriguez
2009-08-31 17:50 ` Luis R. Rodriguez
0 siblings, 1 reply; 26+ messages in thread
From: Luis R. Rodriguez @ 2009-08-31 8:23 UTC (permalink / raw)
To: Catalin Marinas, John W. Linville, H. Peter Anvin
Cc: linux-kernel, Aneesh Kumar K.V, Greg Kroah-Hartman, linux-wireless
On Fri, Aug 28, 2009 at 3:09 PM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
> On Fri, Aug 28, 2009 at 2:50 PM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
>> On Fri, Aug 28, 2009 at 9:52 AM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
>>> On Fri, Aug 28, 2009 at 9:32 AM, Catalin Marinas<catalin.marinas@arm.com> wrote:
>>>> "Luis R. Rodriguez" <mcgrof@gmail.com> wrote:
>>>>> I have an assorted collection of kmemleak reports for acpi, ext4 and
>>>>> tty, not sure how to read these yet to fix so figure I'd at least post
>>>>> them. To reproduce I can just dd=/dev/zero to some big file and played
>>>>> some video.
>>>>
>>>> If you do a few echo scan > /sys/kernel/debug/kmemleak, do they
>>>> disappear (i.e. transient false positives)?
>>>
>>> Sure, I will once on rc8.
>>>
>>>> Which kernel version is this?
>>>
>>> v2.6.31-rc7-33172-gf4a9f9a
>>>
>>> This is from wireless-testing, which has wireless patches on top of
>>> rc7. John just rebased to rc8 so will give that a shot at work.
>>>
>>>>> unreferenced object 0xffff88003e0015c0 (size 64):
>>>>> comm "swapper", pid 1, jiffies 4294892352
>>>>> backtrace:
>>>>> [<ffffffff81121fad>] create_object+0x13d/0x2d0
>>>>> [<ffffffff81122265>] kmemleak_alloc+0x25/0x60
>>>>> [<ffffffff81118a03>] kmem_cache_alloc_node+0x193/0x200
>>>>> [<ffffffff8152509e>] process_zones+0x70/0x1cd
>>>>> [<ffffffff81525230>] pageset_cpuup_callback+0x35/0x92
>>>>> [<ffffffff8152c9b7>] notifier_call_chain+0x47/0x90
>>>>> [<ffffffff81078549>] __raw_notifier_call_chain+0x9/0x10
>>>>> [<ffffffff81523f25>] _cpu_up+0x75/0x130
>>>>> [<ffffffff8152403a>] cpu_up+0x5a/0x6a
>>>>> [<ffffffff8181969e>] kernel_init+0xcc/0x1ba
>>>>> [<ffffffff810130ca>] child_rip+0xa/0x20
>>>>> [<ffffffffffffffff>] 0xffffffffffffffff
>>>>
>>>> Can't really tell. Maybe a false positive caused by kmemleak not
>>>> scanning the pgdata node_zones. Can you post your .config file?
>>>
>>> Sure, attached.
>>>
>>>>> unreferenced object 0xffff88003cb5f700 (size 64):
>>>>> comm "swapper", pid 1, jiffies 4294892459
>>>>> backtrace:
>>>>> [<ffffffff81121fad>] create_object+0x13d/0x2d0
>>>>> [<ffffffff81122265>] kmemleak_alloc+0x25/0x60
>>>>> [<ffffffff81119f3b>] __kmalloc+0x16b/0x250
>>>>> [<ffffffff812bb549>] kzalloc+0xf/0x11
>>>>> [<ffffffff812bbb53>] acpi_add_single_object+0x58e/0xd3c
>>>>> [<ffffffff812bc51c>] acpi_bus_scan+0x125/0x1af
>>>>> [<ffffffff81842361>] acpi_scan_init+0xc8/0xe9
>>>>> [<ffffffff8184211c>] acpi_init+0x21f/0x265
>>>>> [<ffffffff8100a05b>] do_one_initcall+0x4b/0x1b0
>>>>> [<ffffffff81819736>] kernel_init+0x164/0x1ba
>>>>> [<ffffffff810130ca>] child_rip+0xa/0x20
>>>>> [<ffffffffffffffff>] 0xffffffffffffffff
>>>>
>>>> I get ACPI reports as well and they may be real leaks. However, I
>>>> didn't have time to analyse the code (pretty complicated reference
>>>> counting).
>>>
>>> Heh OK thanks for reviewing them though.
>>>
>>>>> unreferenced object 0xffff880039571800 (size 1024):
>>>>> comm "exe", pid 1168, jiffies 4294893410
>>>>> backtrace:
>>>>> [<ffffffff81121fad>] create_object+0x13d/0x2d0
>>>>> [<ffffffff81122265>] kmemleak_alloc+0x25/0x60
>>>>> [<ffffffff81119f3b>] __kmalloc+0x16b/0x250
>>>>> [<ffffffff811e1d71>] ext4_mb_init+0x1a1/0x590
>>>>> [<ffffffff811d2da3>] ext4_fill_super+0x1df3/0x26c0
>>>>> [<ffffffff8112774f>] get_sb_bdev+0x16f/0x1b0
>>>>> [<ffffffff811c8fd3>] ext4_get_sb+0x13/0x20
>>>>> [<ffffffff81127216>] vfs_kern_mount+0x76/0x180
>>>>> [<ffffffff8112738d>] do_kern_mount+0x4d/0x130
>>>>> [<ffffffff8113fc57>] do_mount+0x307/0x8b0
>>>>> [<ffffffff8114028f>] sys_mount+0x8f/0xe0
>>>>> [<ffffffff81011f02>] system_call_fastpath+0x16/0x1b
>>>>> [<ffffffffffffffff>] 0xffffffffffffffff
>>>>
>>>> The ext4 reports are real leaks and patch was posted here -
>>>> http://lkml.org/lkml/2009/7/15/62. However, it hasn't been merged into
>>>> mainline yet (I cc'ed Aneesh).
>>>>
>>>> The patch is merged in my "kmemleak-fixes" branch on
>>>> git://linux-arm.org/linux-2.6.git.
>>>
>>> Will try to suck them out and try them.
>>
>> OK -- tested rc8 + a pull of your tree into mine. The bootup was
>> really slow and something was just not going right. After a while
>> memleak complained it had 8 kmemleak logs but I was not able to get my
>> system usable enough to cat the file.
>>
>> In cases like these I wish I would hookup my ctrl-alt-del to kexec() a
>> safe kernel.
>>
>> After a long period of time it seems X wished it would start, it tried
>> and then flashed back to the tty. This kept repeating in a loop.
>>
>> I am not sure if the culprit was rc8 or the kmemleak branch merge --
>> I'll find out after I boot into rc8 in a few.
>
> rc8 busted my bootup, the issues are present with just
> wireless-testing. I highly doubt the issues are wireless-testing
> related so I will not bisect there. Since I am unable to get anything
> useful from the kernel to determine what may have gone sour, any
> suggestions on a path to bisect, or should I just do the whole tree?
I tried 2.6.31-rc8 from hpa's linux-2.6-allstable.git tree instead of
Linus [1] as I already had that tree, git describe says:
v2.6.31-rc8-15-gadda766
Testing this would be the same as testing Linus' blessed rc8 --
correct me I'm wrong. Contrary to what I expected this tree with the
same config works well!
I have compiled a fresh checkout of wireless-testing origin/master to
double check the issue and it is indeed only present on
wireless-testing. A diff stat between John's merge of 2.6.31-rc8 and
current master branch on wireless-testing [2] doesn't reveal much
other than wireless specific stuff, as expected, so it seems this may
after all be introduced in a recent patches in wireless-testing. I
still find this a bit odd given I see no others reporting major
issues. My boot doesn't go very far, it stalls for a while after input
devices are being detected, then it spits out a kmemleak warning about
13 kmemleaks. Here's a picture [3]. I didn't bother waiting as I did
last time for X to try to come up, something is really wrong. I'll
bisect wireless-testing in the morning, starting with a good marker at
merge-2009-08-28 as that is when John pulled 2.6.31-rc8 (and I confirm
a diff stat between that and v2.6.31-rc8 yields nothing as it should)
and current master as the bad marker. I have 9 steps to go, will leave
first step compiling overnight.
[1] git://git.kernel.org/pub/scm/linux/kernel/git/hpa/linux-2.6-allstable.git
[2] git diff --stat merge-2009-08-28..HEAD
[3] http://bombadil.infradead.org/~mcgrof/images/2009/08/lag-wl-2009-08-31.jpg
[4] git diff --stat merge-2009-08-28..v2.6.31-rc8
Luis
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: memleaks, acpi + ext4 + tty
2009-08-31 8:23 ` Luis R. Rodriguez
@ 2009-08-31 17:50 ` Luis R. Rodriguez
2009-08-31 18:37 ` Luis R. Rodriguez
0 siblings, 1 reply; 26+ messages in thread
From: Luis R. Rodriguez @ 2009-08-31 17:50 UTC (permalink / raw)
To: Catalin Marinas, John W. Linville, H. Peter Anvin
Cc: linux-kernel, Aneesh Kumar K.V, Greg Kroah-Hartman, linux-wireless
On Mon, Aug 31, 2009 at 1:23 AM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
> On Fri, Aug 28, 2009 at 3:09 PM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
>> On Fri, Aug 28, 2009 at 2:50 PM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
>>> On Fri, Aug 28, 2009 at 9:52 AM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
>>>> On Fri, Aug 28, 2009 at 9:32 AM, Catalin Marinas<catalin.marinas@arm.com> wrote:
>>>>> "Luis R. Rodriguez" <mcgrof@gmail.com> wrote:
>>>>>> I have an assorted collection of kmemleak reports for acpi, ext4 and
>>>>>> tty, not sure how to read these yet to fix so figure I'd at least post
>>>>>> them. To reproduce I can just dd=/dev/zero to some big file and played
>>>>>> some video.
>>>>>
>>>>> If you do a few echo scan > /sys/kernel/debug/kmemleak, do they
>>>>> disappear (i.e. transient false positives)?
>>>>
>>>> Sure, I will once on rc8.
>>>>
>>>>> Which kernel version is this?
>>>>
>>>> v2.6.31-rc7-33172-gf4a9f9a
>>>>
>>>> This is from wireless-testing, which has wireless patches on top of
>>>> rc7. John just rebased to rc8 so will give that a shot at work.
>>>>
>>>>>> unreferenced object 0xffff88003e0015c0 (size 64):
>>>>>> comm "swapper", pid 1, jiffies 4294892352
>>>>>> backtrace:
>>>>>> [<ffffffff81121fad>] create_object+0x13d/0x2d0
>>>>>> [<ffffffff81122265>] kmemleak_alloc+0x25/0x60
>>>>>> [<ffffffff81118a03>] kmem_cache_alloc_node+0x193/0x200
>>>>>> [<ffffffff8152509e>] process_zones+0x70/0x1cd
>>>>>> [<ffffffff81525230>] pageset_cpuup_callback+0x35/0x92
>>>>>> [<ffffffff8152c9b7>] notifier_call_chain+0x47/0x90
>>>>>> [<ffffffff81078549>] __raw_notifier_call_chain+0x9/0x10
>>>>>> [<ffffffff81523f25>] _cpu_up+0x75/0x130
>>>>>> [<ffffffff8152403a>] cpu_up+0x5a/0x6a
>>>>>> [<ffffffff8181969e>] kernel_init+0xcc/0x1ba
>>>>>> [<ffffffff810130ca>] child_rip+0xa/0x20
>>>>>> [<ffffffffffffffff>] 0xffffffffffffffff
>>>>>
>>>>> Can't really tell. Maybe a false positive caused by kmemleak not
>>>>> scanning the pgdata node_zones. Can you post your .config file?
>>>>
>>>> Sure, attached.
>>>>
>>>>>> unreferenced object 0xffff88003cb5f700 (size 64):
>>>>>> comm "swapper", pid 1, jiffies 4294892459
>>>>>> backtrace:
>>>>>> [<ffffffff81121fad>] create_object+0x13d/0x2d0
>>>>>> [<ffffffff81122265>] kmemleak_alloc+0x25/0x60
>>>>>> [<ffffffff81119f3b>] __kmalloc+0x16b/0x250
>>>>>> [<ffffffff812bb549>] kzalloc+0xf/0x11
>>>>>> [<ffffffff812bbb53>] acpi_add_single_object+0x58e/0xd3c
>>>>>> [<ffffffff812bc51c>] acpi_bus_scan+0x125/0x1af
>>>>>> [<ffffffff81842361>] acpi_scan_init+0xc8/0xe9
>>>>>> [<ffffffff8184211c>] acpi_init+0x21f/0x265
>>>>>> [<ffffffff8100a05b>] do_one_initcall+0x4b/0x1b0
>>>>>> [<ffffffff81819736>] kernel_init+0x164/0x1ba
>>>>>> [<ffffffff810130ca>] child_rip+0xa/0x20
>>>>>> [<ffffffffffffffff>] 0xffffffffffffffff
>>>>>
>>>>> I get ACPI reports as well and they may be real leaks. However, I
>>>>> didn't have time to analyse the code (pretty complicated reference
>>>>> counting).
>>>>
>>>> Heh OK thanks for reviewing them though.
>>>>
>>>>>> unreferenced object 0xffff880039571800 (size 1024):
>>>>>> comm "exe", pid 1168, jiffies 4294893410
>>>>>> backtrace:
>>>>>> [<ffffffff81121fad>] create_object+0x13d/0x2d0
>>>>>> [<ffffffff81122265>] kmemleak_alloc+0x25/0x60
>>>>>> [<ffffffff81119f3b>] __kmalloc+0x16b/0x250
>>>>>> [<ffffffff811e1d71>] ext4_mb_init+0x1a1/0x590
>>>>>> [<ffffffff811d2da3>] ext4_fill_super+0x1df3/0x26c0
>>>>>> [<ffffffff8112774f>] get_sb_bdev+0x16f/0x1b0
>>>>>> [<ffffffff811c8fd3>] ext4_get_sb+0x13/0x20
>>>>>> [<ffffffff81127216>] vfs_kern_mount+0x76/0x180
>>>>>> [<ffffffff8112738d>] do_kern_mount+0x4d/0x130
>>>>>> [<ffffffff8113fc57>] do_mount+0x307/0x8b0
>>>>>> [<ffffffff8114028f>] sys_mount+0x8f/0xe0
>>>>>> [<ffffffff81011f02>] system_call_fastpath+0x16/0x1b
>>>>>> [<ffffffffffffffff>] 0xffffffffffffffff
>>>>>
>>>>> The ext4 reports are real leaks and patch was posted here -
>>>>> http://lkml.org/lkml/2009/7/15/62. However, it hasn't been merged into
>>>>> mainline yet (I cc'ed Aneesh).
>>>>>
>>>>> The patch is merged in my "kmemleak-fixes" branch on
>>>>> git://linux-arm.org/linux-2.6.git.
>>>>
>>>> Will try to suck them out and try them.
>>>
>>> OK -- tested rc8 + a pull of your tree into mine. The bootup was
>>> really slow and something was just not going right. After a while
>>> memleak complained it had 8 kmemleak logs but I was not able to get my
>>> system usable enough to cat the file.
>>>
>>> In cases like these I wish I would hookup my ctrl-alt-del to kexec() a
>>> safe kernel.
>>>
>>> After a long period of time it seems X wished it would start, it tried
>>> and then flashed back to the tty. This kept repeating in a loop.
>>>
>>> I am not sure if the culprit was rc8 or the kmemleak branch merge --
>>> I'll find out after I boot into rc8 in a few.
>>
>> rc8 busted my bootup, the issues are present with just
>> wireless-testing. I highly doubt the issues are wireless-testing
>> related so I will not bisect there. Since I am unable to get anything
>> useful from the kernel to determine what may have gone sour, any
>> suggestions on a path to bisect, or should I just do the whole tree?
>
> I tried 2.6.31-rc8 from hpa's linux-2.6-allstable.git tree instead of
> Linus [1] as I already had that tree, git describe says:
>
> v2.6.31-rc8-15-gadda766
>
> Testing this would be the same as testing Linus' blessed rc8 --
> correct me I'm wrong. Contrary to what I expected this tree with the
> same config works well!
>
> I have compiled a fresh checkout of wireless-testing origin/master to
> double check the issue and it is indeed only present on
> wireless-testing. A diff stat between John's merge of 2.6.31-rc8 and
> current master branch on wireless-testing [2] doesn't reveal much
> other than wireless specific stuff, as expected, so it seems this may
> after all be introduced in a recent patches in wireless-testing. I
> still find this a bit odd given I see no others reporting major
> issues. My boot doesn't go very far, it stalls for a while after input
> devices are being detected, then it spits out a kmemleak warning about
> 13 kmemleaks. Here's a picture [3]. I didn't bother waiting as I did
> last time for X to try to come up, something is really wrong. I'll
> bisect wireless-testing in the morning, starting with a good marker at
> merge-2009-08-28 as that is when John pulled 2.6.31-rc8 (and I confirm
> a diff stat between that and v2.6.31-rc8 yields nothing as it should)
> and current master as the bad marker. I have 9 steps to go, will leave
> first step compiling overnight.
>
> [1] git://git.kernel.org/pub/scm/linux/kernel/git/hpa/linux-2.6-allstable.git
> [2] git diff --stat merge-2009-08-28..HEAD
> [3] http://bombadil.infradead.org/~mcgrof/images/2009/08/lag-wl-2009-08-31.jpg
> [4] git diff --stat merge-2009-08-28..v2.6.31-rc8
Hah, well this makes no sense:
mcgrof@tux ~/wireless-testing (git::(no branch))$ git bisect bad
a4e774ca75e5f2d8347b4d9746a2e0a9a4fc521b is first bad commit
commit a4e774ca75e5f2d8347b4d9746a2e0a9a4fc521b
Author: John W. Linville <linville@tuxdriver.com>
Date: Wed Feb 27 16:04:18 2008 -0500
Add localversion-wireless to identify builds from this tree.
Signed-off-by: John W. Linville <linville@tuxdriver.com>
:000000 100644 0000000000000000000000000000000000000000
6a05d60db3b21d9c0a0b93b831c6ea453dc98785 A localversion-wireless
I'll try a fresh branch on merge-2009-08-28 ..
Luis
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: memleaks, acpi + ext4 + tty
2009-08-31 17:50 ` Luis R. Rodriguez
@ 2009-08-31 18:37 ` Luis R. Rodriguez
2009-08-31 19:30 ` Luis R. Rodriguez
0 siblings, 1 reply; 26+ messages in thread
From: Luis R. Rodriguez @ 2009-08-31 18:37 UTC (permalink / raw)
To: Catalin Marinas, John W. Linville, H. Peter Anvin
Cc: linux-kernel, Aneesh Kumar K.V, Greg Kroah-Hartman, linux-wireless
On Mon, Aug 31, 2009 at 10:50 AM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
> On Mon, Aug 31, 2009 at 1:23 AM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
>> On Fri, Aug 28, 2009 at 3:09 PM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
>>> On Fri, Aug 28, 2009 at 2:50 PM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
>>>> On Fri, Aug 28, 2009 at 9:52 AM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
>>>>> On Fri, Aug 28, 2009 at 9:32 AM, Catalin Marinas<catalin.marinas@arm.com> wrote:
>>>>>> "Luis R. Rodriguez" <mcgrof@gmail.com> wrote:
>>>>>>> I have an assorted collection of kmemleak reports for acpi, ext4 and
>>>>>>> tty, not sure how to read these yet to fix so figure I'd at least post
>>>>>>> them. To reproduce I can just dd=/dev/zero to some big file and played
>>>>>>> some video.
>>>>>>
>>>>>> If you do a few echo scan > /sys/kernel/debug/kmemleak, do they
>>>>>> disappear (i.e. transient false positives)?
>>>>>
>>>>> Sure, I will once on rc8.
>>>>>
>>>>>> Which kernel version is this?
>>>>>
>>>>> v2.6.31-rc7-33172-gf4a9f9a
>>>>>
>>>>> This is from wireless-testing, which has wireless patches on top of
>>>>> rc7. John just rebased to rc8 so will give that a shot at work.
>>>>>
>>>>>>> unreferenced object 0xffff88003e0015c0 (size 64):
>>>>>>> comm "swapper", pid 1, jiffies 4294892352
>>>>>>> backtrace:
>>>>>>> [<ffffffff81121fad>] create_object+0x13d/0x2d0
>>>>>>> [<ffffffff81122265>] kmemleak_alloc+0x25/0x60
>>>>>>> [<ffffffff81118a03>] kmem_cache_alloc_node+0x193/0x200
>>>>>>> [<ffffffff8152509e>] process_zones+0x70/0x1cd
>>>>>>> [<ffffffff81525230>] pageset_cpuup_callback+0x35/0x92
>>>>>>> [<ffffffff8152c9b7>] notifier_call_chain+0x47/0x90
>>>>>>> [<ffffffff81078549>] __raw_notifier_call_chain+0x9/0x10
>>>>>>> [<ffffffff81523f25>] _cpu_up+0x75/0x130
>>>>>>> [<ffffffff8152403a>] cpu_up+0x5a/0x6a
>>>>>>> [<ffffffff8181969e>] kernel_init+0xcc/0x1ba
>>>>>>> [<ffffffff810130ca>] child_rip+0xa/0x20
>>>>>>> [<ffffffffffffffff>] 0xffffffffffffffff
>>>>>>
>>>>>> Can't really tell. Maybe a false positive caused by kmemleak not
>>>>>> scanning the pgdata node_zones. Can you post your .config file?
>>>>>
>>>>> Sure, attached.
>>>>>
>>>>>>> unreferenced object 0xffff88003cb5f700 (size 64):
>>>>>>> comm "swapper", pid 1, jiffies 4294892459
>>>>>>> backtrace:
>>>>>>> [<ffffffff81121fad>] create_object+0x13d/0x2d0
>>>>>>> [<ffffffff81122265>] kmemleak_alloc+0x25/0x60
>>>>>>> [<ffffffff81119f3b>] __kmalloc+0x16b/0x250
>>>>>>> [<ffffffff812bb549>] kzalloc+0xf/0x11
>>>>>>> [<ffffffff812bbb53>] acpi_add_single_object+0x58e/0xd3c
>>>>>>> [<ffffffff812bc51c>] acpi_bus_scan+0x125/0x1af
>>>>>>> [<ffffffff81842361>] acpi_scan_init+0xc8/0xe9
>>>>>>> [<ffffffff8184211c>] acpi_init+0x21f/0x265
>>>>>>> [<ffffffff8100a05b>] do_one_initcall+0x4b/0x1b0
>>>>>>> [<ffffffff81819736>] kernel_init+0x164/0x1ba
>>>>>>> [<ffffffff810130ca>] child_rip+0xa/0x20
>>>>>>> [<ffffffffffffffff>] 0xffffffffffffffff
>>>>>>
>>>>>> I get ACPI reports as well and they may be real leaks. However, I
>>>>>> didn't have time to analyse the code (pretty complicated reference
>>>>>> counting).
>>>>>
>>>>> Heh OK thanks for reviewing them though.
>>>>>
>>>>>>> unreferenced object 0xffff880039571800 (size 1024):
>>>>>>> comm "exe", pid 1168, jiffies 4294893410
>>>>>>> backtrace:
>>>>>>> [<ffffffff81121fad>] create_object+0x13d/0x2d0
>>>>>>> [<ffffffff81122265>] kmemleak_alloc+0x25/0x60
>>>>>>> [<ffffffff81119f3b>] __kmalloc+0x16b/0x250
>>>>>>> [<ffffffff811e1d71>] ext4_mb_init+0x1a1/0x590
>>>>>>> [<ffffffff811d2da3>] ext4_fill_super+0x1df3/0x26c0
>>>>>>> [<ffffffff8112774f>] get_sb_bdev+0x16f/0x1b0
>>>>>>> [<ffffffff811c8fd3>] ext4_get_sb+0x13/0x20
>>>>>>> [<ffffffff81127216>] vfs_kern_mount+0x76/0x180
>>>>>>> [<ffffffff8112738d>] do_kern_mount+0x4d/0x130
>>>>>>> [<ffffffff8113fc57>] do_mount+0x307/0x8b0
>>>>>>> [<ffffffff8114028f>] sys_mount+0x8f/0xe0
>>>>>>> [<ffffffff81011f02>] system_call_fastpath+0x16/0x1b
>>>>>>> [<ffffffffffffffff>] 0xffffffffffffffff
>>>>>>
>>>>>> The ext4 reports are real leaks and patch was posted here -
>>>>>> http://lkml.org/lkml/2009/7/15/62. However, it hasn't been merged into
>>>>>> mainline yet (I cc'ed Aneesh).
>>>>>>
>>>>>> The patch is merged in my "kmemleak-fixes" branch on
>>>>>> git://linux-arm.org/linux-2.6.git.
>>>>>
>>>>> Will try to suck them out and try them.
>>>>
>>>> OK -- tested rc8 + a pull of your tree into mine. The bootup was
>>>> really slow and something was just not going right. After a while
>>>> memleak complained it had 8 kmemleak logs but I was not able to get my
>>>> system usable enough to cat the file.
>>>>
>>>> In cases like these I wish I would hookup my ctrl-alt-del to kexec() a
>>>> safe kernel.
>>>>
>>>> After a long period of time it seems X wished it would start, it tried
>>>> and then flashed back to the tty. This kept repeating in a loop.
>>>>
>>>> I am not sure if the culprit was rc8 or the kmemleak branch merge --
>>>> I'll find out after I boot into rc8 in a few.
>>>
>>> rc8 busted my bootup, the issues are present with just
>>> wireless-testing. I highly doubt the issues are wireless-testing
>>> related so I will not bisect there. Since I am unable to get anything
>>> useful from the kernel to determine what may have gone sour, any
>>> suggestions on a path to bisect, or should I just do the whole tree?
>>
>> I tried 2.6.31-rc8 from hpa's linux-2.6-allstable.git tree instead of
>> Linus [1] as I already had that tree, git describe says:
>>
>> v2.6.31-rc8-15-gadda766
>>
>> Testing this would be the same as testing Linus' blessed rc8 --
>> correct me I'm wrong. Contrary to what I expected this tree with the
>> same config works well!
>>
>> I have compiled a fresh checkout of wireless-testing origin/master to
>> double check the issue and it is indeed only present on
>> wireless-testing. A diff stat between John's merge of 2.6.31-rc8 and
>> current master branch on wireless-testing [2] doesn't reveal much
>> other than wireless specific stuff, as expected, so it seems this may
>> after all be introduced in a recent patches in wireless-testing. I
>> still find this a bit odd given I see no others reporting major
>> issues. My boot doesn't go very far, it stalls for a while after input
>> devices are being detected, then it spits out a kmemleak warning about
>> 13 kmemleaks. Here's a picture [3]. I didn't bother waiting as I did
>> last time for X to try to come up, something is really wrong. I'll
>> bisect wireless-testing in the morning, starting with a good marker at
>> merge-2009-08-28 as that is when John pulled 2.6.31-rc8 (and I confirm
>> a diff stat between that and v2.6.31-rc8 yields nothing as it should)
>> and current master as the bad marker. I have 9 steps to go, will leave
>> first step compiling overnight.
>>
>> [1] git://git.kernel.org/pub/scm/linux/kernel/git/hpa/linux-2.6-allstable.git
>> [2] git diff --stat merge-2009-08-28..HEAD
>> [3] http://bombadil.infradead.org/~mcgrof/images/2009/08/lag-wl-2009-08-31.jpg
>> [4] git diff --stat merge-2009-08-28..v2.6.31-rc8
>
> Hah, well this makes no sense:
>
> mcgrof@tux ~/wireless-testing (git::(no branch))$ git bisect bad
> a4e774ca75e5f2d8347b4d9746a2e0a9a4fc521b is first bad commit
> commit a4e774ca75e5f2d8347b4d9746a2e0a9a4fc521b
> Author: John W. Linville <linville@tuxdriver.com>
> Date: Wed Feb 27 16:04:18 2008 -0500
>
> Add localversion-wireless to identify builds from this tree.
>
> Signed-off-by: John W. Linville <linville@tuxdriver.com>
>
> :000000 100644 0000000000000000000000000000000000000000
> 6a05d60db3b21d9c0a0b93b831c6ea453dc98785 A localversion-wireless
>
> I'll try a fresh branch on merge-2009-08-28 ..
OK I tried this, I even 'rm -rf * ; git checkout -f' and ..
merge-2009-08-28 tag yields the same issues, long lag upon bootup with
some kmemleaks I cannot even get to check. So somehow something is
different between merge-2009-08-28 and Linus' rc8. This is just
bizarre so to be even safer I'm just going to do a fresh git clone on
wireless-testing.
Luis
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: memleaks, acpi + ext4 + tty
2009-08-31 18:37 ` Luis R. Rodriguez
@ 2009-08-31 19:30 ` Luis R. Rodriguez
2009-08-31 19:33 ` John W. Linville
0 siblings, 1 reply; 26+ messages in thread
From: Luis R. Rodriguez @ 2009-08-31 19:30 UTC (permalink / raw)
To: Catalin Marinas, John W. Linville, H. Peter Anvin
Cc: linux-kernel, Aneesh Kumar K.V, Greg Kroah-Hartman, linux-wireless
On Mon, Aug 31, 2009 at 11:37 AM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
> On Mon, Aug 31, 2009 at 10:50 AM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
>> On Mon, Aug 31, 2009 at 1:23 AM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
>>> On Fri, Aug 28, 2009 at 3:09 PM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
>>>> On Fri, Aug 28, 2009 at 2:50 PM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
>>>>> On Fri, Aug 28, 2009 at 9:52 AM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
>>>>>> On Fri, Aug 28, 2009 at 9:32 AM, Catalin Marinas<catalin.marinas@arm.com> wrote:
>>>>>>> "Luis R. Rodriguez" <mcgrof@gmail.com> wrote:
>>>>>>>> I have an assorted collection of kmemleak reports for acpi, ext4 and
>>>>>>>> tty, not sure how to read these yet to fix so figure I'd at least post
>>>>>>>> them. To reproduce I can just dd=/dev/zero to some big file and played
>>>>>>>> some video.
>>>>>>>
>>>>>>> If you do a few echo scan > /sys/kernel/debug/kmemleak, do they
>>>>>>> disappear (i.e. transient false positives)?
>>>>>>
>>>>>> Sure, I will once on rc8.
>>>>>>
>>>>>>> Which kernel version is this?
>>>>>>
>>>>>> v2.6.31-rc7-33172-gf4a9f9a
>>>>>>
>>>>>> This is from wireless-testing, which has wireless patches on top of
>>>>>> rc7. John just rebased to rc8 so will give that a shot at work.
>>>>>>
>>>>>>>> unreferenced object 0xffff88003e0015c0 (size 64):
>>>>>>>> comm "swapper", pid 1, jiffies 4294892352
>>>>>>>> backtrace:
>>>>>>>> [<ffffffff81121fad>] create_object+0x13d/0x2d0
>>>>>>>> [<ffffffff81122265>] kmemleak_alloc+0x25/0x60
>>>>>>>> [<ffffffff81118a03>] kmem_cache_alloc_node+0x193/0x200
>>>>>>>> [<ffffffff8152509e>] process_zones+0x70/0x1cd
>>>>>>>> [<ffffffff81525230>] pageset_cpuup_callback+0x35/0x92
>>>>>>>> [<ffffffff8152c9b7>] notifier_call_chain+0x47/0x90
>>>>>>>> [<ffffffff81078549>] __raw_notifier_call_chain+0x9/0x10
>>>>>>>> [<ffffffff81523f25>] _cpu_up+0x75/0x130
>>>>>>>> [<ffffffff8152403a>] cpu_up+0x5a/0x6a
>>>>>>>> [<ffffffff8181969e>] kernel_init+0xcc/0x1ba
>>>>>>>> [<ffffffff810130ca>] child_rip+0xa/0x20
>>>>>>>> [<ffffffffffffffff>] 0xffffffffffffffff
>>>>>>>
>>>>>>> Can't really tell. Maybe a false positive caused by kmemleak not
>>>>>>> scanning the pgdata node_zones. Can you post your .config file?
>>>>>>
>>>>>> Sure, attached.
>>>>>>
>>>>>>>> unreferenced object 0xffff88003cb5f700 (size 64):
>>>>>>>> comm "swapper", pid 1, jiffies 4294892459
>>>>>>>> backtrace:
>>>>>>>> [<ffffffff81121fad>] create_object+0x13d/0x2d0
>>>>>>>> [<ffffffff81122265>] kmemleak_alloc+0x25/0x60
>>>>>>>> [<ffffffff81119f3b>] __kmalloc+0x16b/0x250
>>>>>>>> [<ffffffff812bb549>] kzalloc+0xf/0x11
>>>>>>>> [<ffffffff812bbb53>] acpi_add_single_object+0x58e/0xd3c
>>>>>>>> [<ffffffff812bc51c>] acpi_bus_scan+0x125/0x1af
>>>>>>>> [<ffffffff81842361>] acpi_scan_init+0xc8/0xe9
>>>>>>>> [<ffffffff8184211c>] acpi_init+0x21f/0x265
>>>>>>>> [<ffffffff8100a05b>] do_one_initcall+0x4b/0x1b0
>>>>>>>> [<ffffffff81819736>] kernel_init+0x164/0x1ba
>>>>>>>> [<ffffffff810130ca>] child_rip+0xa/0x20
>>>>>>>> [<ffffffffffffffff>] 0xffffffffffffffff
>>>>>>>
>>>>>>> I get ACPI reports as well and they may be real leaks. However, I
>>>>>>> didn't have time to analyse the code (pretty complicated reference
>>>>>>> counting).
>>>>>>
>>>>>> Heh OK thanks for reviewing them though.
>>>>>>
>>>>>>>> unreferenced object 0xffff880039571800 (size 1024):
>>>>>>>> comm "exe", pid 1168, jiffies 4294893410
>>>>>>>> backtrace:
>>>>>>>> [<ffffffff81121fad>] create_object+0x13d/0x2d0
>>>>>>>> [<ffffffff81122265>] kmemleak_alloc+0x25/0x60
>>>>>>>> [<ffffffff81119f3b>] __kmalloc+0x16b/0x250
>>>>>>>> [<ffffffff811e1d71>] ext4_mb_init+0x1a1/0x590
>>>>>>>> [<ffffffff811d2da3>] ext4_fill_super+0x1df3/0x26c0
>>>>>>>> [<ffffffff8112774f>] get_sb_bdev+0x16f/0x1b0
>>>>>>>> [<ffffffff811c8fd3>] ext4_get_sb+0x13/0x20
>>>>>>>> [<ffffffff81127216>] vfs_kern_mount+0x76/0x180
>>>>>>>> [<ffffffff8112738d>] do_kern_mount+0x4d/0x130
>>>>>>>> [<ffffffff8113fc57>] do_mount+0x307/0x8b0
>>>>>>>> [<ffffffff8114028f>] sys_mount+0x8f/0xe0
>>>>>>>> [<ffffffff81011f02>] system_call_fastpath+0x16/0x1b
>>>>>>>> [<ffffffffffffffff>] 0xffffffffffffffff
>>>>>>>
>>>>>>> The ext4 reports are real leaks and patch was posted here -
>>>>>>> http://lkml.org/lkml/2009/7/15/62. However, it hasn't been merged into
>>>>>>> mainline yet (I cc'ed Aneesh).
>>>>>>>
>>>>>>> The patch is merged in my "kmemleak-fixes" branch on
>>>>>>> git://linux-arm.org/linux-2.6.git.
>>>>>>
>>>>>> Will try to suck them out and try them.
>>>>>
>>>>> OK -- tested rc8 + a pull of your tree into mine. The bootup was
>>>>> really slow and something was just not going right. After a while
>>>>> memleak complained it had 8 kmemleak logs but I was not able to get my
>>>>> system usable enough to cat the file.
>>>>>
>>>>> In cases like these I wish I would hookup my ctrl-alt-del to kexec() a
>>>>> safe kernel.
>>>>>
>>>>> After a long period of time it seems X wished it would start, it tried
>>>>> and then flashed back to the tty. This kept repeating in a loop.
>>>>>
>>>>> I am not sure if the culprit was rc8 or the kmemleak branch merge --
>>>>> I'll find out after I boot into rc8 in a few.
>>>>
>>>> rc8 busted my bootup, the issues are present with just
>>>> wireless-testing. I highly doubt the issues are wireless-testing
>>>> related so I will not bisect there. Since I am unable to get anything
>>>> useful from the kernel to determine what may have gone sour, any
>>>> suggestions on a path to bisect, or should I just do the whole tree?
>>>
>>> I tried 2.6.31-rc8 from hpa's linux-2.6-allstable.git tree instead of
>>> Linus [1] as I already had that tree, git describe says:
>>>
>>> v2.6.31-rc8-15-gadda766
>>>
>>> Testing this would be the same as testing Linus' blessed rc8 --
>>> correct me I'm wrong. Contrary to what I expected this tree with the
>>> same config works well!
>>>
>>> I have compiled a fresh checkout of wireless-testing origin/master to
>>> double check the issue and it is indeed only present on
>>> wireless-testing. A diff stat between John's merge of 2.6.31-rc8 and
>>> current master branch on wireless-testing [2] doesn't reveal much
>>> other than wireless specific stuff, as expected, so it seems this may
>>> after all be introduced in a recent patches in wireless-testing. I
>>> still find this a bit odd given I see no others reporting major
>>> issues. My boot doesn't go very far, it stalls for a while after input
>>> devices are being detected, then it spits out a kmemleak warning about
>>> 13 kmemleaks. Here's a picture [3]. I didn't bother waiting as I did
>>> last time for X to try to come up, something is really wrong. I'll
>>> bisect wireless-testing in the morning, starting with a good marker at
>>> merge-2009-08-28 as that is when John pulled 2.6.31-rc8 (and I confirm
>>> a diff stat between that and v2.6.31-rc8 yields nothing as it should)
>>> and current master as the bad marker. I have 9 steps to go, will leave
>>> first step compiling overnight.
>>>
>>> [1] git://git.kernel.org/pub/scm/linux/kernel/git/hpa/linux-2.6-allstable.git
>>> [2] git diff --stat merge-2009-08-28..HEAD
>>> [3] http://bombadil.infradead.org/~mcgrof/images/2009/08/lag-wl-2009-08-31.jpg
>>> [4] git diff --stat merge-2009-08-28..v2.6.31-rc8
>>
>> Hah, well this makes no sense:
>>
>> mcgrof@tux ~/wireless-testing (git::(no branch))$ git bisect bad
>> a4e774ca75e5f2d8347b4d9746a2e0a9a4fc521b is first bad commit
>> commit a4e774ca75e5f2d8347b4d9746a2e0a9a4fc521b
>> Author: John W. Linville <linville@tuxdriver.com>
>> Date: Wed Feb 27 16:04:18 2008 -0500
>>
>> Add localversion-wireless to identify builds from this tree.
>>
>> Signed-off-by: John W. Linville <linville@tuxdriver.com>
>>
>> :000000 100644 0000000000000000000000000000000000000000
>> 6a05d60db3b21d9c0a0b93b831c6ea453dc98785 A localversion-wireless
>>
>> I'll try a fresh branch on merge-2009-08-28 ..
>
> OK I tried this, I even 'rm -rf * ; git checkout -f' and ..
> merge-2009-08-28 tag yields the same issues, long lag upon bootup with
> some kmemleaks I cannot even get to check. So somehow something is
> different between merge-2009-08-28 and Linus' rc8. This is just
> bizarre so to be even safer I'm just going to do a fresh git clone on
> wireless-testing.
Hey John so I tested wireless-testing on the merge-2009-08-28 tag on a
fresh git pull and verified this is indeed busted for me. Although I
had tried hpa's linux-2.6-allstable on HEAD just to be sure I am now
building Linus' tree from a fresh git clone on the v2.6.31-rc8 tag
just to be double check this was indeed not a 2.6.31-rc8 issue but
instead *something* on wireless-testing. What that something is is
unclear to me still, I guess after all these tests I'll run a manual
diff as git doesn't seem to be picking anything up.
Luis
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: memleaks, acpi + ext4 + tty
2009-08-31 19:30 ` Luis R. Rodriguez
@ 2009-08-31 19:33 ` John W. Linville
2009-08-31 19:43 ` Luis R. Rodriguez
0 siblings, 1 reply; 26+ messages in thread
From: John W. Linville @ 2009-08-31 19:33 UTC (permalink / raw)
To: Luis R. Rodriguez
Cc: Catalin Marinas, H. Peter Anvin, linux-kernel, Aneesh Kumar K.V,
Greg Kroah-Hartman, linux-wireless
On Mon, Aug 31, 2009 at 12:30:15PM -0700, Luis R. Rodriguez wrote:
> On Mon, Aug 31, 2009 at 11:37 AM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
> > OK I tried this, I even 'rm -rf * ; git checkout -f' and ..
> > merge-2009-08-28 tag yields the same issues, long lag upon bootup with
> > some kmemleaks I cannot even get to check. So somehow something is
> > different between merge-2009-08-28 and Linus' rc8. This is just
> > bizarre so to be even safer I'm just going to do a fresh git clone on
> > wireless-testing.
>
> Hey John so I tested wireless-testing on the merge-2009-08-28 tag on a
> fresh git pull and verified this is indeed busted for me. Although I
> had tried hpa's linux-2.6-allstable on HEAD just to be sure I am now
> building Linus' tree from a fresh git clone on the v2.6.31-rc8 tag
> just to be double check this was indeed not a 2.6.31-rc8 issue but
> instead *something* on wireless-testing. What that something is is
> unclear to me still, I guess after all these tests I'll run a manual
> diff as git doesn't seem to be picking anything up.
As you determined, there is no difference between merge-2009-08-28
and v2.6.31-rc8. If one works and the other doesn't, then the main
thing not working will be git...
What is linux-2.6-allstable? My guess is that the culprit is between
v2.6.31-rc8 and whatever is at the head of linux-2.6-allstable.
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: memleaks, acpi + ext4 + tty
2009-08-31 19:33 ` John W. Linville
@ 2009-08-31 19:43 ` Luis R. Rodriguez
2009-08-31 19:47 ` John W. Linville
2009-08-31 19:58 ` Luis R. Rodriguez
0 siblings, 2 replies; 26+ messages in thread
From: Luis R. Rodriguez @ 2009-08-31 19:43 UTC (permalink / raw)
To: John W. Linville
Cc: Catalin Marinas, H. Peter Anvin, linux-kernel, Aneesh Kumar K.V,
Greg Kroah-Hartman, linux-wireless
On Mon, Aug 31, 2009 at 12:33 PM, John W.
Linville<linville@tuxdriver.com> wrote:
> On Mon, Aug 31, 2009 at 12:30:15PM -0700, Luis R. Rodriguez wrote:
>> On Mon, Aug 31, 2009 at 11:37 AM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
>
>> > OK I tried this, I even 'rm -rf * ; git checkout -f' and ..
>> > merge-2009-08-28 tag yields the same issues, long lag upon bootup with
>> > some kmemleaks I cannot even get to check. So somehow something is
>> > different between merge-2009-08-28 and Linus' rc8. This is just
>> > bizarre so to be even safer I'm just going to do a fresh git clone on
>> > wireless-testing.
>>
>> Hey John so I tested wireless-testing on the merge-2009-08-28 tag on a
>> fresh git pull and verified this is indeed busted for me. Although I
>> had tried hpa's linux-2.6-allstable on HEAD just to be sure I am now
>> building Linus' tree from a fresh git clone on the v2.6.31-rc8 tag
>> just to be double check this was indeed not a 2.6.31-rc8 issue but
>> instead *something* on wireless-testing. What that something is is
>> unclear to me still, I guess after all these tests I'll run a manual
>> diff as git doesn't seem to be picking anything up.
>
> As you determined, there is no difference between merge-2009-08-28
> and v2.6.31-rc8. If one works and the other doesn't, then the main
> thing not working will be git...
Hm that would suck big time. At any rate, even if it was git
wireless-testing seems to have an issue right now. I'll confirm
shortly with Linus' own tree.
> What is linux-2.6-allstable?
hpa's collection of 2.6 stable kernels, including extraversion stuff.
> My guess is that the culprit is between
> v2.6.31-rc8 and whatever is at the head of linux-2.6-allstable.
But the issue is *not* in linux-2.6-allstable, it is only present on
wireless-testing, and I went as far back as merge-2009-08-28. I was
using whatever tag was available prior to you moving to rc8, and that
worked.
Luis
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: memleaks, acpi + ext4 + tty
2009-08-31 19:43 ` Luis R. Rodriguez
@ 2009-08-31 19:47 ` John W. Linville
2009-08-31 20:02 ` Luis R. Rodriguez
2009-08-31 19:58 ` Luis R. Rodriguez
1 sibling, 1 reply; 26+ messages in thread
From: John W. Linville @ 2009-08-31 19:47 UTC (permalink / raw)
To: Luis R. Rodriguez
Cc: Catalin Marinas, H. Peter Anvin, linux-kernel, Aneesh Kumar K.V,
Greg Kroah-Hartman, linux-wireless
On Mon, Aug 31, 2009 at 12:43:01PM -0700, Luis R. Rodriguez wrote:
> On Mon, Aug 31, 2009 at 12:33 PM, John W.
> Linville<linville@tuxdriver.com> wrote:
> > My guess is that the culprit is between
> > v2.6.31-rc8 and whatever is at the head of linux-2.6-allstable.
>
> But the issue is *not* in linux-2.6-allstable, it is only present on
> wireless-testing, and I went as far back as merge-2009-08-28. I was
> using whatever tag was available prior to you moving to rc8, and that
> worked.
OK, then I can only guess that something went wrong in your bisection
(e.g. dirty build, something not marked properly, etc). That, or
different .config files between your linux-2.6-allstable build and
the merge-2009-08-28 build of wireless-testing?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: memleaks, acpi + ext4 + tty
2009-08-31 19:43 ` Luis R. Rodriguez
2009-08-31 19:47 ` John W. Linville
@ 2009-08-31 19:58 ` Luis R. Rodriguez
2009-09-01 22:10 ` H. Peter Anvin
1 sibling, 1 reply; 26+ messages in thread
From: Luis R. Rodriguez @ 2009-08-31 19:58 UTC (permalink / raw)
To: John W. Linville
Cc: Catalin Marinas, H. Peter Anvin, linux-kernel, Aneesh Kumar K.V,
Greg Kroah-Hartman, linux-wireless
On Mon, Aug 31, 2009 at 12:43 PM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
> On Mon, Aug 31, 2009 at 12:33 PM, John W.
> Linville<linville@tuxdriver.com> wrote:
>> On Mon, Aug 31, 2009 at 12:30:15PM -0700, Luis R. Rodriguez wrote:
>>> On Mon, Aug 31, 2009 at 11:37 AM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
>>
>>> > OK I tried this, I even 'rm -rf * ; git checkout -f' and ..
>>> > merge-2009-08-28 tag yields the same issues, long lag upon bootup with
>>> > some kmemleaks I cannot even get to check. So somehow something is
>>> > different between merge-2009-08-28 and Linus' rc8. This is just
>>> > bizarre so to be even safer I'm just going to do a fresh git clone on
>>> > wireless-testing.
>>>
>>> Hey John so I tested wireless-testing on the merge-2009-08-28 tag on a
>>> fresh git pull and verified this is indeed busted for me. Although I
>>> had tried hpa's linux-2.6-allstable on HEAD just to be sure I am now
>>> building Linus' tree from a fresh git clone on the v2.6.31-rc8 tag
>>> just to be double check this was indeed not a 2.6.31-rc8 issue but
>>> instead *something* on wireless-testing. What that something is is
>>> unclear to me still, I guess after all these tests I'll run a manual
>>> diff as git doesn't seem to be picking anything up.
>>
>> As you determined, there is no difference between merge-2009-08-28
>> and v2.6.31-rc8. If one works and the other doesn't, then the main
>> thing not working will be git...
>
> Hm that would suck big time. At any rate, even if it was git
> wireless-testing seems to have an issue right now. I'll confirm
> shortly with Linus' own tree.
>
>> What is linux-2.6-allstable?
>
> hpa's collection of 2.6 stable kernels, including extraversion stuff.
>
>> My guess is that the culprit is between
>> v2.6.31-rc8 and whatever is at the head of linux-2.6-allstable.
>
> But the issue is *not* in linux-2.6-allstable, it is only present on
> wireless-testing, and I went as far back as merge-2009-08-28. I was
> using whatever tag was available prior to you moving to rc8, and that
> worked.
Good news is Linus' rc8 tag *has the same issue* so the reason why
wireless-testing has it is rc8 *does indeed have it*.
So Peter, if there is something extra or missing from
linux-2.6-allstable head it certainly fixed my issues, will have to
try a new respin of it to ensure it wasn't a fluke. Odd thing too
though is even my distribution kernel (karmic rc8 generic) works fine.
At least now I can safely bisect between rc7 and rc8, or pull the
kmemleaks branch and see if that fixed.
Luis
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: memleaks, acpi + ext4 + tty
2009-08-31 19:47 ` John W. Linville
@ 2009-08-31 20:02 ` Luis R. Rodriguez
2009-08-31 23:54 ` Luis R. Rodriguez
0 siblings, 1 reply; 26+ messages in thread
From: Luis R. Rodriguez @ 2009-08-31 20:02 UTC (permalink / raw)
To: John W. Linville
Cc: Catalin Marinas, H. Peter Anvin, linux-kernel, Aneesh Kumar K.V,
Greg Kroah-Hartman, linux-wireless
On Mon, Aug 31, 2009 at 12:47 PM, John W.
Linville<linville@tuxdriver.com> wrote:
> On Mon, Aug 31, 2009 at 12:43:01PM -0700, Luis R. Rodriguez wrote:
>> On Mon, Aug 31, 2009 at 12:33 PM, John W.
>> Linville<linville@tuxdriver.com> wrote:
>
>> > My guess is that the culprit is between
>> > v2.6.31-rc8 and whatever is at the head of linux-2.6-allstable.
>>
>> But the issue is *not* in linux-2.6-allstable, it is only present on
>> wireless-testing, and I went as far back as merge-2009-08-28. I was
>> using whatever tag was available prior to you moving to rc8, and that
>> worked.
>
> OK, then I can only guess that something went wrong in your bisection
> (e.g. dirty build, something not marked properly, etc).
Well so remember I did a clean git clone of wireless-testing and the
issue was still there, but I determined just now it seems rc8 from
Linus does indeed also have the issue. For some reason the issue was
not present on hpa's rc8 on linux-2.6-allstable. Will double check on
that again.
> That, or
> different .config files between your linux-2.6-allstable build and
> the merge-2009-08-28 build of wireless-testing?
I ensured to diff configs them between builds :T
Luis
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: memleaks, acpi + ext4 + tty
2009-08-31 20:02 ` Luis R. Rodriguez
@ 2009-08-31 23:54 ` Luis R. Rodriguez
2009-09-01 0:26 ` Eric Paris
0 siblings, 1 reply; 26+ messages in thread
From: Luis R. Rodriguez @ 2009-08-31 23:54 UTC (permalink / raw)
To: John W. Linville, Eric Paris
Cc: Catalin Marinas, H. Peter Anvin, linux-kernel, Aneesh Kumar K.V,
Greg Kroah-Hartman, linux-wireless
On Mon, Aug 31, 2009 at 1:02 PM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
> On Mon, Aug 31, 2009 at 12:47 PM, John W.
> Linville<linville@tuxdriver.com> wrote:
>> On Mon, Aug 31, 2009 at 12:43:01PM -0700, Luis R. Rodriguez wrote:
>>> On Mon, Aug 31, 2009 at 12:33 PM, John W.
>>> Linville<linville@tuxdriver.com> wrote:
>>
>>> > My guess is that the culprit is between
>>> > v2.6.31-rc8 and whatever is at the head of linux-2.6-allstable.
>>>
>>> But the issue is *not* in linux-2.6-allstable, it is only present on
>>> wireless-testing, and I went as far back as merge-2009-08-28. I was
>>> using whatever tag was available prior to you moving to rc8, and that
>>> worked.
>>
>> OK, then I can only guess that something went wrong in your bisection
>> (e.g. dirty build, something not marked properly, etc).
>
> Well so remember I did a clean git clone of wireless-testing and the
> issue was still there, but I determined just now it seems rc8 from
> Linus does indeed also have the issue. For some reason the issue was
> not present on hpa's rc8 on linux-2.6-allstable. Will double check on
> that again.
OK so hpa's tree just had all of Linus' stuff pulled, not just rc8. It
turns out Eric Paris' inotify patches are required to fix 2.6.31-rc8
for me.. I tested just one patch and it fixed my bootup lag:
http://git.infradead.org/users/eparis/notify.git/commit/b962e7312ae87006aed6f68ceee94bdf8db08338
FWIW for that patch:
Tested-by: Luis R. Rodriguez <lrodriguez@atheros.com>
So -- you if you're like me and had issues with bootup lag on
wireless-testing, you can probably fix your wireless-testing by
pulling his patches:
git pull git://git.infradead.org/users/eparis/notify.git for-linus
I saw Linus had some other fixes but I'll wait for rc9 for that as my
box seems reasonably stable right now.
Luis
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: memleaks, acpi + ext4 + tty
2009-08-31 23:54 ` Luis R. Rodriguez
@ 2009-09-01 0:26 ` Eric Paris
2009-09-01 0:31 ` Luis R. Rodriguez
0 siblings, 1 reply; 26+ messages in thread
From: Eric Paris @ 2009-09-01 0:26 UTC (permalink / raw)
To: Luis R. Rodriguez
Cc: John W. Linville, Eric Paris, Catalin Marinas, H. Peter Anvin,
linux-kernel, Aneesh Kumar K.V, Greg Kroah-Hartman,
linux-wireless
On Mon, 2009-08-31 at 16:54 -0700, Luis R. Rodriguez wrote:
> On Mon, Aug 31, 2009 at 1:02 PM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
> > On Mon, Aug 31, 2009 at 12:47 PM, John W.
> > Linville<linville@tuxdriver.com> wrote:
> >> On Mon, Aug 31, 2009 at 12:43:01PM -0700, Luis R. Rodriguez wrote:
> >>> On Mon, Aug 31, 2009 at 12:33 PM, John W.
> >>> Linville<linville@tuxdriver.com> wrote:
> >>
> >>> > My guess is that the culprit is between
> >>> > v2.6.31-rc8 and whatever is at the head of linux-2.6-allstable.
> >>>
> >>> But the issue is *not* in linux-2.6-allstable, it is only present on
> >>> wireless-testing, and I went as far back as merge-2009-08-28. I was
> >>> using whatever tag was available prior to you moving to rc8, and that
> >>> worked.
> >>
> >> OK, then I can only guess that something went wrong in your bisection
> >> (e.g. dirty build, something not marked properly, etc).
> >
> > Well so remember I did a clean git clone of wireless-testing and the
> > issue was still there, but I determined just now it seems rc8 from
> > Linus does indeed also have the issue. For some reason the issue was
> > not present on hpa's rc8 on linux-2.6-allstable. Will double check on
> > that again.
>
> OK so hpa's tree just had all of Linus' stuff pulled, not just rc8. It
> turns out Eric Paris' inotify patches are required to fix 2.6.31-rc8
> for me.. I tested just one patch and it fixed my bootup lag:
>
> http://git.infradead.org/users/eparis/notify.git/commit/b962e7312ae87006aed6f68ceee94bdf8db08338
>
> FWIW for that patch:
>
> Tested-by: Luis R. Rodriguez <lrodriguez@atheros.com>
>
> So -- you if you're like me and had issues with bootup lag on
> wireless-testing, you can probably fix your wireless-testing by
> pulling his patches:
>
> git pull git://git.infradead.org/users/eparis/notify.git for-linus
>
> I saw Linus had some other fixes but I'll wait for rc9 for that as my
> box seems reasonably stable right now.
Yes, -rc8 broke pretty badly for a number of people. Linus did pull all
of the fixes that I know of. I wouldn't suggest pulling just that one
commit. All 3 of the post -rc8 patches in my tree fix -rc8
regressions :(
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: memleaks, acpi + ext4 + tty
2009-09-01 0:26 ` Eric Paris
@ 2009-09-01 0:31 ` Luis R. Rodriguez
2009-09-01 6:33 ` Zhu Yi
0 siblings, 1 reply; 26+ messages in thread
From: Luis R. Rodriguez @ 2009-09-01 0:31 UTC (permalink / raw)
To: Eric Paris
Cc: John W. Linville, Eric Paris, Catalin Marinas, H. Peter Anvin,
linux-kernel, Aneesh Kumar K.V, Greg Kroah-Hartman,
linux-wireless
On Mon, Aug 31, 2009 at 5:26 PM, Eric Paris<eparis@redhat.com> wrote:
> On Mon, 2009-08-31 at 16:54 -0700, Luis R. Rodriguez wrote:
>> On Mon, Aug 31, 2009 at 1:02 PM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
>> > On Mon, Aug 31, 2009 at 12:47 PM, John W.
>> > Linville<linville@tuxdriver.com> wrote:
>> >> On Mon, Aug 31, 2009 at 12:43:01PM -0700, Luis R. Rodriguez wrote:
>> >>> On Mon, Aug 31, 2009 at 12:33 PM, John W.
>> >>> Linville<linville@tuxdriver.com> wrote:
>> >>
>> >>> > My guess is that the culprit is between
>> >>> > v2.6.31-rc8 and whatever is at the head of linux-2.6-allstable.
>> >>>
>> >>> But the issue is *not* in linux-2.6-allstable, it is only present on
>> >>> wireless-testing, and I went as far back as merge-2009-08-28. I was
>> >>> using whatever tag was available prior to you moving to rc8, and that
>> >>> worked.
>> >>
>> >> OK, then I can only guess that something went wrong in your bisection
>> >> (e.g. dirty build, something not marked properly, etc).
>> >
>> > Well so remember I did a clean git clone of wireless-testing and the
>> > issue was still there, but I determined just now it seems rc8 from
>> > Linus does indeed also have the issue. For some reason the issue was
>> > not present on hpa's rc8 on linux-2.6-allstable. Will double check on
>> > that again.
>>
>> OK so hpa's tree just had all of Linus' stuff pulled, not just rc8. It
>> turns out Eric Paris' inotify patches are required to fix 2.6.31-rc8
>> for me.. I tested just one patch and it fixed my bootup lag:
>>
>> http://git.infradead.org/users/eparis/notify.git/commit/b962e7312ae87006aed6f68ceee94bdf8db08338
>>
>> FWIW for that patch:
>>
>> Tested-by: Luis R. Rodriguez <lrodriguez@atheros.com>
>>
>> So -- you if you're like me and had issues with bootup lag on
>> wireless-testing, you can probably fix your wireless-testing by
>> pulling his patches:
>>
>> git pull git://git.infradead.org/users/eparis/notify.git for-linus
>>
>> I saw Linus had some other fixes but I'll wait for rc9 for that as my
>> box seems reasonably stable right now.
>
> Yes, -rc8 broke pretty badly for a number of people. Linus did pull all
> of the fixes that I know of. I wouldn't suggest pulling just that one
> commit. All 3 of the post -rc8 patches in my tree fix -rc8
> regressions :(
Thanks, the note -- so I guess best is to just pull from Linus ontop
of wireless-testing.
Luis
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: memleaks, acpi + ext4 + tty
2009-09-01 0:31 ` Luis R. Rodriguez
@ 2009-09-01 6:33 ` Zhu Yi
2009-09-01 18:00 ` Luis R. Rodriguez
0 siblings, 1 reply; 26+ messages in thread
From: Zhu Yi @ 2009-09-01 6:33 UTC (permalink / raw)
To: Luis R. Rodriguez
Cc: Eric Paris, John W. Linville, Eric Paris, Catalin Marinas,
H. Peter Anvin, linux-kernel, Aneesh Kumar K.V,
Greg Kroah-Hartman, linux-wireless
On Tue, 2009-09-01 at 08:31 +0800, Luis R. Rodriguez wrote:
> >>
> http://git.infradead.org/users/eparis/notify.git/commit/b962e7312ae87006aed6f68ceee94bdf8db08338
> >>
> >> FWIW for that patch:
> >>
> >> Tested-by: Luis R. Rodriguez <lrodriguez@atheros.com>
> >>
> >> So -- you if you're like me and had issues with bootup lag on
> >> wireless-testing, you can probably fix your wireless-testing by
> >> pulling his patches:
> >>
> >> git pull git://git.infradead.org/users/eparis/notify.git for-linus
> >>
> >> I saw Linus had some other fixes but I'll wait for rc9 for that as
> my
> >> box seems reasonably stable right now.
> >
> > Yes, -rc8 broke pretty badly for a number of people. Linus did pull
> all
> > of the fixes that I know of. I wouldn't suggest pulling just that
> one
> > commit. All 3 of the post -rc8 patches in my tree fix -rc8
> > regressions :(
>
> Thanks, the note -- so I guess best is to just pull from Linus ontop
> of wireless-testing.
I confirm I'm also suffered with the problem on today's wireless-testing
tip (udevadm --settle hangs on boot) and the above patch does fix the
issue for me. Thanks both for identify and fix the problem.
Thanks,
-yi
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: memleaks, acpi + ext4 + tty
2009-08-30 18:24 ` Theodore Tso
@ 2009-09-01 17:59 ` Luis R. Rodriguez
0 siblings, 0 replies; 26+ messages in thread
From: Luis R. Rodriguez @ 2009-09-01 17:59 UTC (permalink / raw)
To: Theodore Tso, Luis R. Rodriguez, Aneesh Kumar K.V,
Catalin Marinas, linux-kernel, Greg Kroah-Hartman
On Sun, Aug 30, 2009 at 11:24 AM, Theodore Tso<tytso@mit.edu> wrote:
> On Sun, Aug 30, 2009 at 10:29:01AM -0700, Luis R. Rodriguez wrote:
>> > Yes, as soon as the next merge window opens. The leak only shows up
>> > when you mount and unmount a filesystem, which under normal
>> > circumstances doesn't happen a huge number of times on most systems.
>> > By the time it showed up it was late enough in the 2.6.31-rcX series
>> > that I figured it was better to wait until the next merge window. I
>> > didn't consider it a high priority bug.
>>
>> That's odd I run into this kmemleak with a single bootup, no manual remounts.
>>
>
> Yeah, but it's a singleton leak. Let me be a bit more precise this
> time: the leak happens at mount time because we're essentially doing
> this due to some code that was accidentally duplicated when it was
> being refactored:
>
> a = kmalloc(sizeof(...)*N, GFP_ATOMIC);
> ...
> a = kmalloc(sizeof(...)*N, GFP_ATOMIC);
>
> So a small amount of memory is leaked each time a filesystem is
> mounted. It doesn't become a huge problem unless you are repeatedly
> mounting and unmounting the same filesystem in a tight loop.
Thanks for the explanation -- this still does seem like something
which could affect some users, say of, embedded systems which do need
to remount, so while it may be a priority for an average user it seems
high priority for embedded system users using ext4 and remounting a
lot.
Either way, I guess what I'm getting at is it seems rather odd to me
we would not consider fixing some memory leaks on an rc release when
we already have a fix prepared. I understand the merge window is
closing in but we're not there yet -- and in worst case, can't we at
least consider this fix after rc1?
kmeleak reports seem rather useful, I'd hate to see more users told
their memory leak issues won't be fixed until a later kernel release.
That just seems... shitty.
Luis
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: memleaks, acpi + ext4 + tty
2009-09-01 6:33 ` Zhu Yi
@ 2009-09-01 18:00 ` Luis R. Rodriguez
0 siblings, 0 replies; 26+ messages in thread
From: Luis R. Rodriguez @ 2009-09-01 18:00 UTC (permalink / raw)
To: Zhu Yi
Cc: Eric Paris, John W. Linville, Eric Paris, Catalin Marinas,
H. Peter Anvin, linux-kernel, Aneesh Kumar K.V,
Greg Kroah-Hartman, linux-wireless
On Mon, Aug 31, 2009 at 11:33 PM, Zhu Yi<yi.zhu@intel.com> wrote:
> On Tue, 2009-09-01 at 08:31 +0800, Luis R. Rodriguez wrote:
>> >>
>> http://git.infradead.org/users/eparis/notify.git/commit/b962e7312ae87006aed6f68ceee94bdf8db08338
>> >>
>> >> FWIW for that patch:
>> >>
>> >> Tested-by: Luis R. Rodriguez <lrodriguez@atheros.com>
>> >>
>> >> So -- you if you're like me and had issues with bootup lag on
>> >> wireless-testing, you can probably fix your wireless-testing by
>> >> pulling his patches:
>> >>
>> >> git pull git://git.infradead.org/users/eparis/notify.git for-linus
>> >>
>> >> I saw Linus had some other fixes but I'll wait for rc9 for that as
>> my
>> >> box seems reasonably stable right now.
>> >
>> > Yes, -rc8 broke pretty badly for a number of people. Linus did pull
>> all
>> > of the fixes that I know of. I wouldn't suggest pulling just that
>> one
>> > commit. All 3 of the post -rc8 patches in my tree fix -rc8
>> > regressions :(
>>
>> Thanks, the note -- so I guess best is to just pull from Linus ontop
>> of wireless-testing.
>
> I confirm I'm also suffered with the problem on today's wireless-testing
> tip (udevadm --settle hangs on boot) and the above patch does fix the
> issue for me. Thanks both for identify and fix the problem.
Just a heads up -- the relevant fixes are now merged on
wireless-testing, thanks John.
Luis
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: memleaks, acpi + ext4 + tty
2009-08-31 19:58 ` Luis R. Rodriguez
@ 2009-09-01 22:10 ` H. Peter Anvin
0 siblings, 0 replies; 26+ messages in thread
From: H. Peter Anvin @ 2009-09-01 22:10 UTC (permalink / raw)
To: Luis R. Rodriguez
Cc: John W. Linville, Catalin Marinas, H. Peter Anvin, linux-kernel,
Aneesh Kumar K.V, Greg Kroah-Hartman, linux-wireless
On 08/31/2009 12:58 PM, Luis R. Rodriguez wrote:
>
> Good news is Linus' rc8 tag *has the same issue* so the reason why
> wireless-testing has it is rc8 *does indeed have it*.
>
> So Peter, if there is something extra or missing from
> linux-2.6-allstable head it certainly fixed my issues, will have to
> try a new respin of it to ensure it wasn't a fluke. Odd thing too
> though is even my distribution kernel (karmic rc8 generic) works fine.
>
linux-2.6-allstable head is == linus.
-hpa
^ permalink raw reply [flat|nested] 26+ messages in thread
end of thread, other threads:[~2009-09-01 22:12 UTC | newest]
Thread overview: 26+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-08-28 5:25 memleaks, acpi + ext4 + tty Luis R. Rodriguez
2009-08-28 16:32 ` Catalin Marinas
2009-08-28 16:52 ` Luis R. Rodriguez
2009-08-28 21:50 ` Luis R. Rodriguez
2009-08-28 22:09 ` Luis R. Rodriguez
2009-08-31 8:23 ` Luis R. Rodriguez
2009-08-31 17:50 ` Luis R. Rodriguez
2009-08-31 18:37 ` Luis R. Rodriguez
2009-08-31 19:30 ` Luis R. Rodriguez
2009-08-31 19:33 ` John W. Linville
2009-08-31 19:43 ` Luis R. Rodriguez
2009-08-31 19:47 ` John W. Linville
2009-08-31 20:02 ` Luis R. Rodriguez
2009-08-31 23:54 ` Luis R. Rodriguez
2009-09-01 0:26 ` Eric Paris
2009-09-01 0:31 ` Luis R. Rodriguez
2009-09-01 6:33 ` Zhu Yi
2009-09-01 18:00 ` Luis R. Rodriguez
2009-08-31 19:58 ` Luis R. Rodriguez
2009-09-01 22:10 ` H. Peter Anvin
2009-08-29 21:41 ` Catalin Marinas
2009-08-30 16:34 ` Aneesh Kumar K.V
2009-08-30 17:17 ` Theodore Tso
2009-08-30 17:29 ` Luis R. Rodriguez
2009-08-30 18:24 ` Theodore Tso
2009-09-01 17:59 ` Luis R. Rodriguez
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).