From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 205309] New: kmemleak reports various leaks in amdgpu
Date: Thu, 24 Oct 2019 19:44:30 +0000 [thread overview]
Message-ID: <bug-205309-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=205309
Bug ID: 205309
Summary: kmemleak reports various leaks in amdgpu
Product: Drivers
Version: 2.5
Kernel Version: 5.4-rc4
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: erhard_f@mailbox.org
Regression: No
Created attachment 285635
--> https://bugzilla.kernel.org/attachment.cgi?id=285635&action=edit
kmemleak: 34 new suspected memory leaks
Running X I get various kmemleak dumps for amdgpu:
[...]
unreferenced object 0xffff995f56fde340 (size 224):
comm "Xorg", pid 801, jiffies 4294890593 (age 1572.594s)
hex dump (first 32 bytes):
d0 e3 fd 56 5f 99 ff ff a0 61 7e c0 ff ff ff ff ...V_....a~.....
36 bb 4b 81 0a 00 00 00 48 fe 32 53 5f 99 ff ff 6.K.....H.2S_...
backtrace:
[<00000000531b3f80>] drm_sched_fence_create+0x1d/0xc0 [gpu_sched]
[<00000000dc85bf8c>] drm_sched_job_init+0x5b/0xa0 [gpu_sched]
[<000000005789f820>] amdgpu_job_submit+0x1e/0x90 [amdgpu]
[<00000000f3185640>] amdgpu_copy_buffer+0x1ab/0x290 [amdgpu]
[<0000000053449562>] amdgpu_ttm_copy_mem_to_mem+0x25d/0x520 [amdgpu]
[<00000000810db067>] amdgpu_move_blit.constprop.25+0x85/0x1b0 [amdgpu]
[<0000000051e06c3a>] amdgpu_bo_move+0x164/0x290 [amdgpu]
[<00000000d0345de4>] ttm_bo_handle_move_mem+0x113/0x5b0 [ttm]
[<000000003dbb02d9>] ttm_bo_validate+0x16e/0x1b0 [ttm]
[<0000000096a41e6b>] amdgpu_bo_fault_reserve_notify+0xe5/0x130 [amdgpu]
[<00000000eb688629>] ttm_bo_vm_fault+0xac/0x650 [ttm]
[<0000000061352dd3>] __do_fault+0x31/0xf0
[<00000000ad4b517c>] __handle_mm_fault+0xd31/0x12a0
[<00000000037720cd>] handle_mm_fault+0x165/0x2e0
[<00000000196e733c>] __do_page_fault+0x1a8/0x420
[<000000000c9cfffa>] page_fault+0x31/0x40
[...]
System: Kernel: 5.4.0-rc4 x86_64 bits: 64 Desktop: MATE 1.22.0 Distro:
Gentoo Base System release 2.6
Machine: Type: Server Mobo: Supermicro model: H8SGL v: 1234567890 serial:
<filter> BIOS: American Megatrends v: 3.5b
date: 03/18/2016
CPU: 8-Core: AMD Opteron 6380 type: MT MCP speed: 1584 MHz min/max:
1400/2500 MHz
Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX
470/480/570/570X/580/580X/590] driver: amdgpu
v: kernel
Device-2: Matrox Systems MGA G200eW WPCM450 driver: N/A
Display: x11 server: X.Org 1.20.5 driver: amdgpu,ati unloaded:
modesetting,radeon resolution: 1920x1080~60Hz
OpenGL: renderer: Radeon RX 590 Series (POLARIS10 DRM 3.35.0
5.4.0-rc4 LLVM 8.0.1) v: 4.5 Mesa 19.1.7
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-10-24 19:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 19:44 bugzilla-daemon [this message]
2019-10-24 19:45 ` [Bug 205309] kmemleak reports various leaks in amdgpu bugzilla-daemon
2019-10-24 19:46 ` bugzilla-daemon
2019-11-16 11:03 ` bugzilla-daemon
2019-11-16 11:31 ` bugzilla-daemon
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=bug-205309-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.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.