On 9/28/18 2:52 PM, Stefan Seyfried wrote:
Hi,
I think I'm seeing a continuously rising usage of kmalloc-2048 slabs in /proc/slabinfo and slabtop. Before I rebooted from 4.19rc3 to 4.19rc5, I had about 4.5GB of kmalloc-2048 after about 13d8h uptime.
Now, after almost 10 minutes uptime, it has already grown to 4MB: 2166 2166 100% 2.00K 1083 2 4332K kmalloc-2048
How can I debug this? The usage started to increase immediately after boot into an idle XFCE desktop, running a small X11 application (gkrellm system monitor) via SSH on a remote machine
After disabling networking in NetworkManager, kmalloc-2048 usage went down (from about ~2500 objects to 2388 active objects right now), now on a stable, lightly fluctuating level.
This is a Lenovo Thinkpad T420, Core i5-2520M CPU, 8GB RAM, Intel Centrino Advanced-N 6205 [Taylor Peak] WIFI module, Ethernet unused.
Once I know how to find out more details, I'm ready to report this upstream ;-)
The easiest way to find out what is causing this memory leak is to configure a kernel with KMEMLEAK enabled. The critical configuration parameters are CONFIG_DEBUG_KMEMLEAK=y CONFIG_DEBUG_KMEMLEAK_EARLY_LOG_SIZE=2000 If you get a log entry that kmemleak has been aborted when the kernel is started, then you may need to increase the early log size parameter. Once the system is running, do the following as root: echo scan > /sys/kernel/debug/kmemleak cat /sys/kernel/debug/kmemleak The resulting list will show you what component has leaked, and the address where it occurred. You can then use gdb to pinpoint the source line in the code. Larry -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org