linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lin Ming <ming.m.lin@intel.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: new kmemleak w/ latest ACPI updates
Date: Tue, 13 Apr 2010 10:03:16 +0800	[thread overview]
Message-ID: <1271124196.3656.0.camel@minggr.sh.intel.com> (raw)
In-Reply-To: <201004102102.57235.toralf.foerster@gmx.de>

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

  reply	other threads:[~2010-04-13  2:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-10 19:02 new kmemleak w/ latest ACPI updates Toralf Förster
2010-04-13  2:03 ` Lin Ming [this message]
     [not found]   ` <201004130939.40175.toralf.foerster@gmx.de>
2010-04-13  7:52     ` Lin Ming

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1271124196.3656.0.camel@minggr.sh.intel.com \
    --to=ming.m.lin@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=toralf.foerster@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).