* 3.x memleaks
@ 2011-09-06 15:50 Sid Boyce
2011-09-07 10:58 ` Américo Wang
0 siblings, 1 reply; 3+ messages in thread
From: Sid Boyce @ 2011-09-06 15:50 UTC (permalink / raw)
To: LKML Mailing List
Since 3.0 I have been seeing memleaks, right up to 3.1.0-rc5. This is
typical.
AMD x86_64, X2, X4's and openSUSE 12.1 Milestones.
unreferenced object 0xffff88022f007000 (size 512):
comm "swapper", pid 1, jiffies 4294667649 (age 17727.056s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<ffffffff81490ba6>] kmemleak_alloc+0x56/0xb0
[<ffffffff8113ca4c>] kmem_cache_alloc_node_trace+0x9c/0x1d0
[<ffffffff81041ea7>] __sdt_alloc+0xa7/0x1e0
[<ffffffff81042014>] __visit_domain_allocation_hell+0x34/0xc0
[<ffffffff8104d489>] build_sched_domains+0x29/0x2e0
[<ffffffff81c4c5de>] sched_init_smp+0x7d/0x168
[<ffffffff81c36cca>] kernel_init+0xb8/0x159
[<ffffffff814bfbb4>] kernel_thread_helper+0x4/0x10
[<ffffffffffffffff>] 0xffffffffffffffff
unreferenced object 0xffff88022f007600 (size 512):
comm "swapper", pid 1, jiffies 4294667649 (age 17727.056s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<ffffffff81490ba6>] kmemleak_alloc+0x56/0xb0
[<ffffffff8113ca4c>] kmem_cache_alloc_node_trace+0x9c/0x1d0
[<ffffffff81041ea7>] __sdt_alloc+0xa7/0x1e0
[<ffffffff81042014>] __visit_domain_allocation_hell+0x34/0xc0
[<ffffffff8104d489>] build_sched_domains+0x29/0x2e0
[<ffffffff81c4c5de>] sched_init_smp+0x7d/0x168
[<ffffffff81c36cca>] kernel_init+0xb8/0x159
[<ffffffff814bfbb4>] kernel_thread_helper+0x4/0x10
[<ffffffffffffffff>] 0xffffffffffffffff
unreferenced object 0xffff88022f007800 (size 512):
comm "swapper", pid 1, jiffies 4294667649 (age 17727.056s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<ffffffff81490ba6>] kmemleak_alloc+0x56/0xb0
[<ffffffff8113ca4c>] kmem_cache_alloc_node_trace+0x9c/0x1d0
[<ffffffff81041ea7>] __sdt_alloc+0xa7/0x1e0
[<ffffffff81042014>] __visit_domain_allocation_hell+0x34/0xc0
[<ffffffff8104d489>] build_sched_domains+0x29/0x2e0
[<ffffffff81c4c5de>] sched_init_smp+0x7d/0x168
[<ffffffff81c36cca>] kernel_init+0xb8/0x159
[<ffffffff814bfbb4>] kernel_thread_helper+0x4/0x10
[<ffffffffffffffff>] 0xffffffffffffffff
unreferenced object 0xffff88022f007a00 (size 512):
comm "swapper", pid 1, jiffies 4294667649 (age 17727.056s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<ffffffff81490ba6>] kmemleak_alloc+0x56/0xb0
[<ffffffff8113ca4c>] kmem_cache_alloc_node_trace+0x9c/0x1d0
[<ffffffff81041ea7>] __sdt_alloc+0xa7/0x1e0
[<ffffffff81042014>] __visit_domain_allocation_hell+0x34/0xc0
[<ffffffff8104d489>] build_sched_domains+0x29/0x2e0
[<ffffffff81c4c5de>] sched_init_smp+0x7d/0x168
[<ffffffff81c36cca>] kernel_init+0xb8/0x159
[<ffffffff814bfbb4>] kernel_thread_helper+0x4/0x10
[<ffffffffffffffff>] 0xffffffffffffffff
unreferenced object 0xffff88022f007c00 (size 512):
comm "swapper", pid 1, jiffies 4294667649 (age 17727.056s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<ffffffff81490ba6>] kmemleak_alloc+0x56/0xb0
[<ffffffff8113ca4c>] kmem_cache_alloc_node_trace+0x9c/0x1d0
[<ffffffff81041ea7>] __sdt_alloc+0xa7/0x1e0
[<ffffffff81042014>] __visit_domain_allocation_hell+0x34/0xc0
[<ffffffff8104d489>] build_sched_domains+0x29/0x2e0
[<ffffffff81c4c5de>] sched_init_smp+0x7d/0x168
[<ffffffff81c36cca>] kernel_init+0xb8/0x159
[<ffffffff814bfbb4>] kernel_thread_helper+0x4/0x10
[<ffffffffffffffff>] 0xffffffffffffffff
unreferenced object 0xffff88022f007e00 (size 512):
comm "swapper", pid 1, jiffies 4294667649 (age 18070.657s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<ffffffff81490ba6>] kmemleak_alloc+0x56/0xb0
[<ffffffff8113ca4c>] kmem_cache_alloc_node_trace+0x9c/0x1d0
[<ffffffff81041ea7>] __sdt_alloc+0xa7/0x1e0
[<ffffffff81042014>] __visit_domain_allocation_hell+0x34/0xc0
[<ffffffff8104d489>] build_sched_domains+0x29/0x2e0
[<ffffffff81c4c5de>] sched_init_smp+0x7d/0x168
[<ffffffff81c36cca>] kernel_init+0xb8/0x159
[<ffffffff814bfbb4>] kernel_thread_helper+0x4/0x10
[<ffffffffffffffff>] 0xffffffffffffffff
****** the rest truncated *************
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: 3.x memleaks
2011-09-06 15:50 3.x memleaks Sid Boyce
@ 2011-09-07 10:58 ` Américo Wang
2011-09-07 23:37 ` Sid Boyce
0 siblings, 1 reply; 3+ messages in thread
From: Américo Wang @ 2011-09-07 10:58 UTC (permalink / raw)
To: sboyce; +Cc: LKML Mailing List
On Tue, Sep 6, 2011 at 11:50 PM, Sid Boyce <sboyce@blueyonder.co.uk> wrote:
> Since 3.0 I have been seeing memleaks, right up to 3.1.0-rc5. This is
> typical.
> AMD x86_64, X2, X4's and openSUSE 12.1 Milestones.
> unreferenced object 0xffff88022f007000 (size 512):
> comm "swapper", pid 1, jiffies 4294667649 (age 17727.056s)
> hex dump (first 32 bytes):
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> backtrace:
> [<ffffffff81490ba6>] kmemleak_alloc+0x56/0xb0
> [<ffffffff8113ca4c>] kmem_cache_alloc_node_trace+0x9c/0x1d0
> [<ffffffff81041ea7>] __sdt_alloc+0xa7/0x1e0
> [<ffffffff81042014>] __visit_domain_allocation_hell+0x34/0xc0
> [<ffffffff8104d489>] build_sched_domains+0x29/0x2e0
> [<ffffffff81c4c5de>] sched_init_smp+0x7d/0x168
> [<ffffffff81c36cca>] kernel_init+0xb8/0x159
> [<ffffffff814bfbb4>] kernel_thread_helper+0x4/0x10
> [<ffffffffffffffff>] 0xffffffffffffffff
Hello,
This should be fixed by: https://lkml.org/lkml/2011/8/29/218
Thanks!
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: 3.x memleaks
2011-09-07 10:58 ` Américo Wang
@ 2011-09-07 23:37 ` Sid Boyce
0 siblings, 0 replies; 3+ messages in thread
From: Sid Boyce @ 2011-09-07 23:37 UTC (permalink / raw)
To: Américo Wang; +Cc: LKML Mailing List
On 07/09/11 11:58, Américo Wang wrote:
> On Tue, Sep 6, 2011 at 11:50 PM, Sid Boyce<sboyce@blueyonder.co.uk> wrote:
>> Since 3.0 I have been seeing memleaks, right up to 3.1.0-rc5. This is
>> typical.
>> AMD x86_64, X2, X4's and openSUSE 12.1 Milestones.
>> unreferenced object 0xffff88022f007000 (size 512):
>> Â comm "swapper", pid 1, jiffies 4294667649 (age 17727.056s)
>> Â hex dump (first 32 bytes):
>> Â Â 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Â ................
>> Â Â 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Â ................
>> Â backtrace:
>> Â Â [<ffffffff81490ba6>] kmemleak_alloc+0x56/0xb0
>> Â Â [<ffffffff8113ca4c>] kmem_cache_alloc_node_trace+0x9c/0x1d0
>> Â Â [<ffffffff81041ea7>] __sdt_alloc+0xa7/0x1e0
>> Â Â [<ffffffff81042014>] __visit_domain_allocation_hell+0x34/0xc0
>> Â Â [<ffffffff8104d489>] build_sched_domains+0x29/0x2e0
>> Â Â [<ffffffff81c4c5de>] sched_init_smp+0x7d/0x168
>> Â Â [<ffffffff81c36cca>] kernel_init+0xb8/0x159
>> Â Â [<ffffffff814bfbb4>] kernel_thread_helper+0x4/0x10
>> Â Â [<ffffffffffffffff>] 0xffffffffffffffff
> Hello,
>
> This should be fixed by: https://lkml.org/lkml/2011/8/29/218
>
> Thanks!
>
I applied the patch to 3.1-rc5 and it's still the same.
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-09-08 0:54 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-09-06 15:50 3.x memleaks Sid Boyce
2011-09-07 10:58 ` Américo Wang
2011-09-07 23:37 ` Sid Boyce
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox