From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 16489] New: kmemleak after suspend2ram in cpufreq driver
Date: Sun, 1 Aug 2010 14:19:35 GMT [thread overview]
Message-ID: <bug-16489-12968@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=16489
Summary: kmemleak after suspend2ram in cpufreq driver
Product: Power Management
Version: 2.5
Kernel Version: 2.6.35-rc6+
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: cpufreq
AssignedTo: cpufreq@vger.kernel.org
ReportedBy: toralf.foerster@gmx.de
Regression: No
If I suspend2ram my ThinkPad T400 and wake it up, then
/sys/kernel/debug/kmemleak contains an entry like this:
unreferenced object 0xf6788640 (size 64):
comm "modprobe", pid 1038, jiffies 4294676277 (age 7682.155s)
hex dump (first 32 bytes):
00 00 00 00 e8 a2 24 00 01 00 00 00 00 9f 24 00 ......$.......$.
02 00 00 00 00 6a 18 00 03 00 00 00 00 35 0c 00 .....j.......5..
backtrace:
[<c122f8f7>] kmemleak_alloc+0x27/0x50
[<c109cb6f>] __kmalloc+0xcf/0x110
[<f94f87de>] acpi_cpufreq_cpu_init+0x1ee/0x4e4 [acpi_cpufreq]
[<c11c3a72>] cpufreq_add_dev+0x142/0x3a0
[<c1187e27>] sysdev_driver_register+0x97/0x110
[<c11c2a06>] cpufreq_register_driver+0x86/0x140
[<f94fc080>] 0xf94fc080
[<c100112d>] do_one_initcall+0x2d/0x180
[<c105ef29>] sys_init_module+0x99/0x1e0
[<c1002d97>] sysenter_do_call+0x12/0x26
[<ffffffff>] 0xffffffff
What's interesting is that this entry only appears after the wakeup (and an
additional wait time of usually 20 minutes) however the "age" is from the boot
time of that system.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2010-08-01 14:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-01 14:19 bugzilla-daemon [this message]
2010-08-23 12:51 ` [Bug 16489] kmemleak after suspend2ram in cpufreq driver bugzilla-daemon
2010-09-23 21:30 ` bugzilla-daemon
2010-09-23 21:30 ` bugzilla-daemon
2010-09-28 20:30 ` bugzilla-daemon
2010-10-03 20:21 ` bugzilla-daemon
2011-03-03 1:11 ` bugzilla-daemon
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=bug-16489-12968@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=cpufreq@vger.kernel.org \
/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