All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: Eli Cohen <elic@nvidia.com>, Thomas Zimmermann <tzimmermann@suse.de>
Cc: daniel.vetter@ffwll.ch, sam@ravnborg.org,
	linux-kernel@vger.kernel.org,
	dri-devel <dri-devel@lists.freedesktop.org>,
	virtualization@lists.linux-foundation.org
Subject: Re: Change eats memory on my server
Date: Mon, 18 Jan 2021 08:43:12 +0100	[thread overview]
Message-ID: <83f74a11-b3c0-db2e-8301-4292d60d803b@amd.com> (raw)
In-Reply-To: <20210117050837.GA225992@mtl-vdi-166.wap.labs.mlnx>

Hi Eli,

have you already tried using kmemleak?

This sounds like a leak of memory allocated using kmalloc(), so kmemleak 
should be able to catch it.

Regards,
Christian.

Am 17.01.21 um 06:08 schrieb Eli Cohen:
> On Fri, Jan 15, 2021 at 10:03:50AM +0100, Thomas Zimmermann wrote:
>> Could you please double-check that 3fb91f56aea4 ("drm/udl: Retrieve USB
>> device from struct drm_device.dev") works correctly
> Checked again, it does not seem to leak.
>
>> and that 823efa922102
>> ("drm/cma-helper: Remove empty drm_gem_cma_prime_vunmap()") is broken?
>>
> Yes, this one leaks, as does the one preceding it:
>
> 1086db71a1db ("drm/vram-helper: Remove invariant parameters from internal kmap function")
>   
>> For one of the broken commits, could you please send us the output of
>>
>>    dmesg | grep -i drm
>>
>> after most of the memory got leaked?
>>
> I ran the following script in the shell:
>
> while true; do cat /proc/meminfo | grep MemFree:; sleep 5; done
>
> and this is what I saw before I got disconnected from the shell:
>
> MemFree:          148208 kB
> MemFree:          148304 kB
> MemFree:          146660 kB
> Connection to nps-server-24 closed by remote host.
> Connection to nps-server-24 closed.
>
>
> I also mointored the output of dmesg | grep -i drm
> The last output I was able to save on disk is this:
>
> [   46.140720] ast 0000:03:00.0: [drm] Using P2A bridge for configuration
> [   46.140737] ast 0000:03:00.0: [drm] AST 2500 detected
> [   46.140754] ast 0000:03:00.0: [drm] Analog VGA only
> [   46.140772] ast 0000:03:00.0: [drm] dram MCLK=800 Mhz type=7 bus_width=16
> [   46.153553] [drm] Initialized ast 0.1.0 20120228 for 0000:03:00.0 on minor 0
> [   46.165097] fbcon: astdrmfb (fb0) is primary device
> [   46.391381] ast 0000:03:00.0: [drm] fb0: astdrmfb frame buffer device
> [   56.097697] systemd[1]: Starting Load Kernel Module drm...
> [   56.343556] systemd[1]: modprobe@drm.service: Succeeded.
> [   56.350382] systemd[1]: Finished Load Kernel Module drm.
> [13319.469462] [   2683] 70889  2683    55586        0    73728      138             0 tdrm
> [13320.658386] [   2683] 70889  2683    55586        0    73728      138             0 tdrm
> [13321.800970] [   2683] 70889  2683    55586        0    73728      138             0 tdrm

_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

WARNING: multiple messages have this Message-ID (diff)
From: "Christian König" <christian.koenig@amd.com>
To: Eli Cohen <elic@nvidia.com>, Thomas Zimmermann <tzimmermann@suse.de>
Cc: daniel.vetter@ffwll.ch, sam@ravnborg.org,
	linux-kernel@vger.kernel.org,
	dri-devel <dri-devel@lists.freedesktop.org>,
	virtualization@lists.linux-foundation.org
Subject: Re: Change eats memory on my server
Date: Mon, 18 Jan 2021 08:43:12 +0100	[thread overview]
Message-ID: <83f74a11-b3c0-db2e-8301-4292d60d803b@amd.com> (raw)
In-Reply-To: <20210117050837.GA225992@mtl-vdi-166.wap.labs.mlnx>

Hi Eli,

have you already tried using kmemleak?

This sounds like a leak of memory allocated using kmalloc(), so kmemleak 
should be able to catch it.

Regards,
Christian.

Am 17.01.21 um 06:08 schrieb Eli Cohen:
> On Fri, Jan 15, 2021 at 10:03:50AM +0100, Thomas Zimmermann wrote:
>> Could you please double-check that 3fb91f56aea4 ("drm/udl: Retrieve USB
>> device from struct drm_device.dev") works correctly
> Checked again, it does not seem to leak.
>
>> and that 823efa922102
>> ("drm/cma-helper: Remove empty drm_gem_cma_prime_vunmap()") is broken?
>>
> Yes, this one leaks, as does the one preceding it:
>
> 1086db71a1db ("drm/vram-helper: Remove invariant parameters from internal kmap function")
>   
>> For one of the broken commits, could you please send us the output of
>>
>>    dmesg | grep -i drm
>>
>> after most of the memory got leaked?
>>
> I ran the following script in the shell:
>
> while true; do cat /proc/meminfo | grep MemFree:; sleep 5; done
>
> and this is what I saw before I got disconnected from the shell:
>
> MemFree:          148208 kB
> MemFree:          148304 kB
> MemFree:          146660 kB
> Connection to nps-server-24 closed by remote host.
> Connection to nps-server-24 closed.
>
>
> I also mointored the output of dmesg | grep -i drm
> The last output I was able to save on disk is this:
>
> [   46.140720] ast 0000:03:00.0: [drm] Using P2A bridge for configuration
> [   46.140737] ast 0000:03:00.0: [drm] AST 2500 detected
> [   46.140754] ast 0000:03:00.0: [drm] Analog VGA only
> [   46.140772] ast 0000:03:00.0: [drm] dram MCLK=800 Mhz type=7 bus_width=16
> [   46.153553] [drm] Initialized ast 0.1.0 20120228 for 0000:03:00.0 on minor 0
> [   46.165097] fbcon: astdrmfb (fb0) is primary device
> [   46.391381] ast 0000:03:00.0: [drm] fb0: astdrmfb frame buffer device
> [   56.097697] systemd[1]: Starting Load Kernel Module drm...
> [   56.343556] systemd[1]: modprobe@drm.service: Succeeded.
> [   56.350382] systemd[1]: Finished Load Kernel Module drm.
> [13319.469462] [   2683] 70889  2683    55586        0    73728      138             0 tdrm
> [13320.658386] [   2683] 70889  2683    55586        0    73728      138             0 tdrm
> [13321.800970] [   2683] 70889  2683    55586        0    73728      138             0 tdrm

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: "Christian König" <christian.koenig@amd.com>
To: Eli Cohen <elic@nvidia.com>, Thomas Zimmermann <tzimmermann@suse.de>
Cc: virtualization@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org, daniel.vetter@ffwll.ch,
	sam@ravnborg.org, dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: Change eats memory on my server
Date: Mon, 18 Jan 2021 08:43:12 +0100	[thread overview]
Message-ID: <83f74a11-b3c0-db2e-8301-4292d60d803b@amd.com> (raw)
In-Reply-To: <20210117050837.GA225992@mtl-vdi-166.wap.labs.mlnx>

Hi Eli,

have you already tried using kmemleak?

This sounds like a leak of memory allocated using kmalloc(), so kmemleak 
should be able to catch it.

Regards,
Christian.

Am 17.01.21 um 06:08 schrieb Eli Cohen:
> On Fri, Jan 15, 2021 at 10:03:50AM +0100, Thomas Zimmermann wrote:
>> Could you please double-check that 3fb91f56aea4 ("drm/udl: Retrieve USB
>> device from struct drm_device.dev") works correctly
> Checked again, it does not seem to leak.
>
>> and that 823efa922102
>> ("drm/cma-helper: Remove empty drm_gem_cma_prime_vunmap()") is broken?
>>
> Yes, this one leaks, as does the one preceding it:
>
> 1086db71a1db ("drm/vram-helper: Remove invariant parameters from internal kmap function")
>   
>> For one of the broken commits, could you please send us the output of
>>
>>    dmesg | grep -i drm
>>
>> after most of the memory got leaked?
>>
> I ran the following script in the shell:
>
> while true; do cat /proc/meminfo | grep MemFree:; sleep 5; done
>
> and this is what I saw before I got disconnected from the shell:
>
> MemFree:          148208 kB
> MemFree:          148304 kB
> MemFree:          146660 kB
> Connection to nps-server-24 closed by remote host.
> Connection to nps-server-24 closed.
>
>
> I also mointored the output of dmesg | grep -i drm
> The last output I was able to save on disk is this:
>
> [   46.140720] ast 0000:03:00.0: [drm] Using P2A bridge for configuration
> [   46.140737] ast 0000:03:00.0: [drm] AST 2500 detected
> [   46.140754] ast 0000:03:00.0: [drm] Analog VGA only
> [   46.140772] ast 0000:03:00.0: [drm] dram MCLK=800 Mhz type=7 bus_width=16
> [   46.153553] [drm] Initialized ast 0.1.0 20120228 for 0000:03:00.0 on minor 0
> [   46.165097] fbcon: astdrmfb (fb0) is primary device
> [   46.391381] ast 0000:03:00.0: [drm] fb0: astdrmfb frame buffer device
> [   56.097697] systemd[1]: Starting Load Kernel Module drm...
> [   56.343556] systemd[1]: modprobe@drm.service: Succeeded.
> [   56.350382] systemd[1]: Finished Load Kernel Module drm.
> [13319.469462] [   2683] 70889  2683    55586        0    73728      138             0 tdrm
> [13320.658386] [   2683] 70889  2683    55586        0    73728      138             0 tdrm
> [13321.800970] [   2683] 70889  2683    55586        0    73728      138             0 tdrm


  reply	other threads:[~2021-01-18  7:43 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-14 15:15 Change eats memory on my server Eli Cohen
2021-01-15  9:03 ` Thomas Zimmermann
2021-01-15  9:03   ` Thomas Zimmermann
2021-01-15  9:03   ` Thomas Zimmermann
2021-01-17  5:08   ` Eli Cohen
2021-01-17  5:08     ` Eli Cohen
2021-01-18  7:43     ` Christian König [this message]
2021-01-18  7:43       ` Christian König
2021-01-18  7:43       ` Christian König
2021-01-18  7:49       ` Eli Cohen
2021-01-18  7:49         ` Eli Cohen
2021-01-18  7:57         ` Christian König
2021-01-18  7:57           ` Christian König
2021-01-18  7:57           ` Christian König
2021-01-18  9:12           ` Eli Cohen
2021-01-18  9:12             ` Eli Cohen
2021-01-18  7:54       ` Thomas Zimmermann
2021-01-18  7:54         ` Thomas Zimmermann
2021-01-18  7:54         ` Thomas Zimmermann
2021-01-18  9:13         ` Eli Cohen
2021-01-18  9:13           ` Eli Cohen
2021-01-18  9:30           ` Thomas Zimmermann
2021-01-18  9:30             ` Thomas Zimmermann
2021-01-18  9:30             ` Thomas Zimmermann
2021-01-18 10:39             ` Eli Cohen
2021-01-18 10:39               ` Eli Cohen
2021-01-18 13:16             ` Eli Cohen
2021-01-18 13:16               ` Eli Cohen
2021-01-18 13:20               ` Thomas Zimmermann
2021-01-18 13:20                 ` Thomas Zimmermann
2021-01-18 13:20                 ` Thomas Zimmermann
2021-01-18 13:22                 ` Eli Cohen
2021-01-18 13:22                   ` Eli Cohen
2021-01-18 13:23                   ` Christian König
2021-01-18 13:23                     ` Christian König
2021-01-18 13:23                     ` Christian König
2021-01-18 14:48                     ` Thomas Zimmermann
2021-01-18 14:48                       ` Thomas Zimmermann
2021-01-18 14:48                       ` Thomas Zimmermann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83f74a11-b3c0-db2e-8301-4292d60d803b@amd.com \
    --to=christian.koenig@amd.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=elic@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=tzimmermann@suse.de \
    --cc=virtualization@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.