* new kmemleak w/ latest ACPI updates
@ 2010-04-10 19:02 Toralf Förster
2010-04-13 2:03 ` Lin Ming
0 siblings, 1 reply; 3+ messages in thread
From: Toralf Förster @ 2010-04-10 19:02 UTC (permalink / raw)
To: linux-acpi
Hello,
running git kernel v2.6.34-rc3-500-g0eddb51 I observe this new kmemleak :
unreferenced object 0xcd3fe6a0 (size 32):
comm "pm-suspend", pid 21698, jiffies 9344750 (age 1363.181s)
hex dump (first 32 bytes):
34 32 54 34 36 34 34 00 34 32 54 34 36 34 34 00 42T4644.42T4644.
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<c122cb0d>] kmemleak_alloc+0x3d/0x60
[<c109c8c2>] __kmalloc+0xf2/0x120
[<c1162c0f>] acpi_ut_create_buffer_object+0x49/0x83
[<c115303b>] acpi_ex_read_data_from_field+0xbe/0x12b
[<c1157988>] acpi_ex_resolve_node_to_value+0x154/0x1c8
[<c1153950>] acpi_ex_resolve_to_value+0x1bc/0x1c8
[<c114e9c3>] acpi_ds_evaluate_name_path+0x6e/0xe3
[<c114d8c0>] acpi_ds_exec_end_op+0x88/0x368
[<c115da04>] acpi_ps_parse_loop+0x701/0x855
[<c115cd0a>] acpi_ps_parse_aml+0x87/0x261
[<c115e0df>] acpi_ps_execute_method+0x18e/0x247
[<c1159dcf>] acpi_ns_evaluate+0xcb/0x17c
[<c115990c>] acpi_evaluate_object+0x10e/0x1eb
[<f80cb37a>] acpi_battery_update+0xb3/0x200 [battery]
[<f80cb54e>] acpi_battery_resume+0x20/0x24 [battery]
[<c114603a>] acpi_device_resume+0x1e/0x24
which might be introduced by the ACPi changes since f5284e I think.
--
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: new kmemleak w/ latest ACPI updates
2010-04-10 19:02 new kmemleak w/ latest ACPI updates Toralf Förster
@ 2010-04-13 2:03 ` Lin Ming
[not found] ` <201004130939.40175.toralf.foerster@gmx.de>
0 siblings, 1 reply; 3+ messages in thread
From: Lin Ming @ 2010-04-13 2:03 UTC (permalink / raw)
To: Toralf Förster; +Cc: linux-acpi@vger.kernel.org
On Sun, 2010-04-11 at 03:02 +0800, Toralf Förster wrote:
> Hello,
>
> running git kernel v2.6.34-rc3-500-g0eddb51 I observe this new kmemleak :
>
> unreferenced object 0xcd3fe6a0 (size 32):
> comm "pm-suspend", pid 21698, jiffies 9344750 (age 1363.181s)
> hex dump (first 32 bytes):
> 34 32 54 34 36 34 34 00 34 32 54 34 36 34 34 00 42T4644.42T4644.
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> backtrace:
> [<c122cb0d>] kmemleak_alloc+0x3d/0x60
> [<c109c8c2>] __kmalloc+0xf2/0x120
> [<c1162c0f>] acpi_ut_create_buffer_object+0x49/0x83
> [<c115303b>] acpi_ex_read_data_from_field+0xbe/0x12b
> [<c1157988>] acpi_ex_resolve_node_to_value+0x154/0x1c8
> [<c1153950>] acpi_ex_resolve_to_value+0x1bc/0x1c8
> [<c114e9c3>] acpi_ds_evaluate_name_path+0x6e/0xe3
> [<c114d8c0>] acpi_ds_exec_end_op+0x88/0x368
> [<c115da04>] acpi_ps_parse_loop+0x701/0x855
> [<c115cd0a>] acpi_ps_parse_aml+0x87/0x261
> [<c115e0df>] acpi_ps_execute_method+0x18e/0x247
> [<c1159dcf>] acpi_ns_evaluate+0xcb/0x17c
> [<c115990c>] acpi_evaluate_object+0x10e/0x1eb
> [<f80cb37a>] acpi_battery_update+0xb3/0x200 [battery]
> [<f80cb54e>] acpi_battery_resume+0x20/0x24 [battery]
> [<c114603a>] acpi_device_resume+0x1e/0x24
>
> which might be introduced by the ACPi changes since f5284e I think.
>
Hi,
I can't reproduce this.
Could you please send the acpidump output?
Thanks,
Lin Ming
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-04-13 8:12 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-04-10 19:02 new kmemleak w/ latest ACPI updates Toralf Förster
2010-04-13 2:03 ` Lin Ming
[not found] ` <201004130939.40175.toralf.foerster@gmx.de>
2010-04-13 7:52 ` Lin Ming
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).