Bug 16489

Summary: kmemleak after suspend2ram in cpufreq driver
Product: Power Management Reporter: Toralf Förster (toralf.foerster)
Component: cpufreqAssignee: cpufreq
Status: CLOSED DUPLICATE    
Severity: normal CC: lenb
Priority: P1    
Hardware: All   
OS: Linux   
Kernel Version: 2.6.35.6 Subsystem:
Regression: No Bisected commit-id:

Description Toralf Förster 2010-08-01 14:19:34 UTC
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.
Comment 1 Toralf Förster 2010-09-23 21:30:25 UTC
After s2ram and wakeup I got this BTW :


unreferenced object 0xe29f9d40 (size 64):
  comm "default.sh", pid 15954, jiffies 1585745 (age 12642.714s)
  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:
    [<c122fb97>] kmemleak_alloc+0x27/0x50
    [<c109caff>] __kmalloc+0xcf/0x110
    [<f95a87de>] acpi_cpufreq_cpu_init+0x1ee/0x4e4 [acpi_cpufreq]
    [<c11c3cb2>] cpufreq_add_dev+0x142/0x3a0
    [<c123ba46>] cpufreq_cpu_callback+0x5b/0x65
    [<c104c895>] notifier_call_chain+0x35/0x60
    [<c104c9a9>] __raw_notifier_call_chain+0x19/0x20
    [<c103459f>] __cpu_notify+0x1f/0x40
    [<c123a7bd>] _cpu_up+0xc1/0xfe
    [<c122eff7>] enable_nonboot_cpus+0x77/0xb0
    [<c105ffec>] suspend_devices_and_enter+0xec/0x190
    [<c106015a>] enter_state+0xca/0xe0
    [<c105f97b>] state_store+0x6b/0xb0
    [<c1124560>] kobj_attr_store+0x20/0x30
    [<c10e79c4>] sysfs_write_file+0x94/0xf0
    [<c10a28ea>] vfs_write+0x9a/0x190
Comment 2 Toralf Förster 2010-10-03 20:21:54 UTC

*** This bug has been marked as a duplicate of bug 15807 ***