Hello, When I s2ram my ThinkPad T400 and wake it up I get : unreferenced object 0xc2cb4000 (size 8192): comm "X", pid 12263, jiffies 5239314 (age 13650.726s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 0f 00 00 00 0f 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [<c123d2a7>] kmemleak_alloc+0x27/0x50 [<c109fdff>] __kmalloc+0xcf/0x110 [<c10884ce>] kmemdup+0x1e/0x40 [<c10019d2>] copy_thread+0x122/0x150 [<c1032a55>] copy_process+0x645/0xd40 [<c10331ce>] do_fork+0x7e/0x350 [<c100a1cf>] sys_clone+0x2f/0x40 [<c1002e65>] ptregs_clone+0x15/0x30 [<ffffffff>] 0xffffffff
In the meanwhile I realized that it isn't related to s2ram, the kmemleak's age is from the first start of X11 if I boot the notebook and never suspended it in the mean while.
And more exactly it happens when the screen saver under KDE is called (with the command "qdbus org.kde.screensaver /ScreenSaver Lock") to lock the screen.
Well, with kernel 2.6.37 I experienced, that s2ram isn't a necessary step before, it only depends on the KDE screen saver.
Hm, 2.6.37 is pretty old. Does this still happen on 3.4?
system has completely changed in the meanwhile - closed this report
I just looked in my kmemleak logs and found this: unreferenced object 0xffff88010c95c000 (size 8192): comm "X", pid 2134, jiffies 4358659349 (age 114908.568s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 0f 00 00 00 0f 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [<ffffffff815c2d5e>] kmemleak_alloc+0x4e/0xb0 [<ffffffff81170d93>] __kmalloc_track_caller+0x113/0x200 [<ffffffff81138c70>] kmemdup+0x20/0x50 [<ffffffff8100200d>] copy_thread+0x20d/0x2c0 [<ffffffff81045ff9>] copy_process.part.29+0xc09/0x1830 [<ffffffff81046de4>] do_fork+0xe4/0x3a0 [<ffffffff81047126>] SyS_clone+0x16/0x20 [<ffffffff815da2c9>] stub_clone+0x69/0x90 [<ffffffffffffffff>] 0xffffffffffffffff unreferenced object 0xffff880030e0c000 (size 8192): comm "X", pid 2134, jiffies 4358659424 (age 114908.280s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 0f 00 00 00 0f 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [<ffffffff815c2d5e>] kmemleak_alloc+0x4e/0xb0 [<ffffffff81170d93>] __kmalloc_track_caller+0x113/0x200 [<ffffffff81138c70>] kmemdup+0x20/0x50 [<ffffffff8100200d>] copy_thread+0x20d/0x2c0 [<ffffffff81045ff9>] copy_process.part.29+0xc09/0x1830 [<ffffffff81046de4>] do_fork+0xe4/0x3a0 [<ffffffff81047126>] SyS_clone+0x16/0x20 [<ffffffff815da2c9>] stub_clone+0x69/0x90 [<ffffffffffffffff>] 0xffffffffffffffff unreferenced object 0xffff88011185a000 (size 8192): comm "X", pid 2134, jiffies 4358659449 (age 114908.180s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 0f 00 00 00 0f 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [<ffffffff815c2d5e>] kmemleak_alloc+0x4e/0xb0 [<ffffffff81170d93>] __kmalloc_track_caller+0x113/0x200 [<ffffffff81138c70>] kmemdup+0x20/0x50 [<ffffffff8100200d>] copy_thread+0x20d/0x2c0 [<ffffffff81045ff9>] copy_process.part.29+0xc09/0x1830 [<ffffffff81046de4>] do_fork+0xe4/0x3a0 [<ffffffff81047126>] SyS_clone+0x16/0x20 [<ffffffff815da2c9>] stub_clone+0x69/0x90 [<ffffffffffffffff>] 0xffffffffffffffff Kernel: 3.13.0-rc5-git-80-gf41bfc9-00080-gf41bfc9 I have no idea how this was triggered, I think I was just working "normally" with an OpenGL 1.2 program (in software rendering mode). Distro: Arch Linux x86_64 Xorg: 1.15.0 (a few days ago, this was updated from 1.14.5 without restarting X iirc). CPU+IGP: i5-460M I am mentioning this for reference, I do not know how to reproduce it. Uptime is 13 days.