From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 16489] New: kmemleak after suspend2ram in cpufreq driver
Date: Sun, 1 Aug 2010 14:19:35 GMT
Message-ID:
Mime-Version: 1.0
Return-path:
Sender: cpufreq-owner@vger.kernel.org
List-ID:
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: cpufreq@vger.kernel.org
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:
[] kmemleak_alloc+0x27/0x50
[] __kmalloc+0xcf/0x110
[] acpi_cpufreq_cpu_init+0x1ee/0x4e4 [acpi_cpufreq]
[] cpufreq_add_dev+0x142/0x3a0
[] sysdev_driver_register+0x97/0x110
[] cpufreq_register_driver+0x86/0x140
[] 0xf94fc080
[] do_one_initcall+0x2d/0x180
[] sys_init_module+0x99/0x1e0
[] sysenter_do_call+0x12/0x26
[] 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.