This kmemleak is new with this kernel at my ThinkPad T400, if I s2ram it and wake it up (FWIW while it is docked) : tfoerste@n22 ~ $ cat /sys/kernel/debug/kmemleakunreferenced object 0xd9381aa0 (size 32): comm "default.sh", pid 15806, jiffies 326609 (age 779.386s) hex dump (first 32 bytes): 00 af 0c f7 ff 1e 30 f8 04 e7 14 f7 00 00 00 00 ......0......... 10 6d 14 f7 cc 67 0e f7 00 03 00 00 00 00 00 00 .m...g.......... backtrace: [<c123e297>] kmemleak_alloc+0x27/0x50 [<c10a001f>] __kmalloc+0xbf/0x120 [<f85e5dd2>] usbhid_submit_report+0x92/0x2e0 [usbhid] [<f85e60de>] usb_hidinput_input_event+0xbe/0x110 [usbhid] [<c11c7961>] input_dev_reset+0x61/0x180 [<c11c7aaf>] input_dev_resume+0x2f/0x60 [<c11996a6>] pm_op+0xf6/0x1d0 [<c1199c6c>] device_resume+0x5c/0xf0 [<c1199dd5>] dpm_resume_end+0xd5/0x300 [<c106407c>] suspend_devices_and_enter+0x11c/0x1b0 [<c10641da>] enter_state+0xca/0xe0 [<c106397b>] state_store+0x6b/0xb0 [<c112dfa0>] kobj_attr_store+0x20/0x30 [<c10eb894>] sysfs_write_file+0x94/0xf0 [<c10a5f5a>] vfs_write+0x9a/0x170 [<c10a60ed>] sys_write+0x3d/0x70
Created attachment 37632 [details] kmemleak Some more examples : hex dump (first 32 bytes): 00 5f 53 42 5f 2e 50 43 49 30 2e 4c 50 43 5f 2e ._SB_.PCI0.LPC_. 45 43 5f 5f 2e 48 4b 45 59 2e 47 42 44 43 00 00 EC__.HKEY.GBDC.. hex dump (first 32 bytes): 00 5f 53 42 5f 2e 50 43 49 30 2e 4c 50 43 5f 2e ._SB_.PCI0.LPC_. 45 43 5f 5f 2e 48 4b 45 59 2e 4d 48 4b 4d 00 00 EC__.HKEY.MHKM.. hex dump (first 32 bytes): 00 03 04 00 02 00 00 00 49 30 2e 53 41 54 41 2e ........I0.SATA. 50 52 54 30 2e 5f 47 54 46 00 00 00 00 00 00 00 PRT0._GTF.......
Those appear to be ACPI paths
Closing as obsolete, if this is still seen with modern kernels please re-open and update