From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 213201] [KAVERI] memory leak - unreferenced object 0xffff8881700cf988 (size 56)
Date: Tue, 15 Jun 2021 19:33:36 +0000 [thread overview]
Message-ID: <bug-213201-2300-4ql6bVCIQw@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-213201-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=213201
--- Comment #5 from Erhard F. (erhard_f@mailbox.org) ---
Created attachment 297375
--> https://bugzilla.kernel.org/attachment.cgi?id=297375&action=edit
kernel dmesg (4.4.271, AMD A10 PRO-7800B)
Bisecting was no success, but I traced the memory leak back to kernel 4.4.x
series.
Kernels v4.3.6 and v4.2.8 won't boot on the machine. But probably the leak has
been there since amdgpu got first introduced in kernel 4.2 anyhow.
[...]
unreferenced object 0xffff8803ecbef380 (size 56):
comm "systemd-udevd", pid 222, jiffies 4294880256 (age 1158.457s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 0d 01 70 00 00 00 00 00 ..........p.....
7b 58 01 00 00 c9 ff ff 00 00 00 00 00 00 00 00 {X..............
backtrace:
[<ffffffffa110c0c9>] create_object+0x162/0x280
[<ffffffffa13d741a>] kmemleak_alloc+0x20/0x3c
[<ffffffffa10fa921>] slab_post_alloc_hook+0x44/0x65
[<ffffffffa10fc73a>] kmem_cache_alloc+0xbf/0xe2
[<ffffffffa1263026>] acpi_os_acquire_object+0x28/0x2a
[<ffffffffa126306f>] acpi_ps_alloc_op+0x39/0x69
[<ffffffffa12622ff>] acpi_ps_create_op+0x105/0x234
[<ffffffffa1261cf2>] acpi_ps_parse_loop+0x1db/0x586
[<ffffffffa1262b62>] acpi_ps_parse_aml+0x93/0x265
[<ffffffffa126335c>] acpi_ps_execute_method+0x14e/0x185
[<ffffffffa125d96c>] acpi_ns_evaluate+0x1bf/0x25b
[<ffffffffa12604a9>] acpi_evaluate_object+0x13c/0x24c
[<ffffffffc075864e>] amdgpu_atcs_call+0x83/0xd9 [amdgpu]
[<ffffffffc0758bdf>] amdgpu_acpi_init+0x62/0x4ef [amdgpu]
[<ffffffffc06f6028>] amdgpu_driver_load_kms+0x83/0x103 [amdgpu]
[<ffffffffc04445f1>] drm_dev_register+0x6d/0xae [drm]
unreferenced object 0xffff8803ecbeef00 (size 56):
comm "systemd-udevd", pid 222, jiffies 4294880256 (age 1158.457s)
hex dump (first 32 bytes):
80 f3 be ec 03 88 ff ff 0d 01 2d 00 00 00 00 00 ..........-.....
7c 58 01 00 00 c9 ff ff 00 00 00 00 00 00 00 00 |X..............
backtrace:
[<ffffffffa110c0c9>] create_object+0x162/0x280
[<ffffffffa13d741a>] kmemleak_alloc+0x20/0x3c
[<ffffffffa10fa921>] slab_post_alloc_hook+0x44/0x65
[<ffffffffa10fc73a>] kmem_cache_alloc+0xbf/0xe2
[<ffffffffa1263026>] acpi_os_acquire_object+0x28/0x2a
[<ffffffffa126306f>] acpi_ps_alloc_op+0x39/0x69
[<ffffffffa12622ff>] acpi_ps_create_op+0x105/0x234
[<ffffffffa1261cf2>] acpi_ps_parse_loop+0x1db/0x586
[<ffffffffa1262b62>] acpi_ps_parse_aml+0x93/0x265
[<ffffffffa126335c>] acpi_ps_execute_method+0x14e/0x185
[<ffffffffa125d96c>] acpi_ns_evaluate+0x1bf/0x25b
[<ffffffffa12604a9>] acpi_evaluate_object+0x13c/0x24c
[<ffffffffc075864e>] amdgpu_atcs_call+0x83/0xd9 [amdgpu]
[<ffffffffc0758bdf>] amdgpu_acpi_init+0x62/0x4ef [amdgpu]
[<ffffffffc06f6028>] amdgpu_driver_load_kms+0x83/0x103 [amdgpu]
[<ffffffffc04445f1>] drm_dev_register+0x6d/0xae [drm]
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2021-06-15 19:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 15:31 [Bug 213201] New: [KAVERI] memory leak - unreferenced object 0xffff8881700cf988 (size 56) bugzilla-daemon
2021-05-24 15:33 ` [Bug 213201] " bugzilla-daemon
2021-05-24 18:46 ` bugzilla-daemon
2021-05-24 19:29 ` bugzilla-daemon
2021-05-24 21:42 ` bugzilla-daemon
2021-06-15 19:33 ` bugzilla-daemon [this message]
2021-06-15 19:35 ` bugzilla-daemon
2021-06-15 19:36 ` bugzilla-daemon
2021-07-19 13:29 ` bugzilla-daemon
2021-07-19 13:30 ` bugzilla-daemon
2021-07-19 13:32 ` bugzilla-daemon
2021-08-06 0:12 ` bugzilla-daemon
2021-08-06 0:13 ` bugzilla-daemon
2021-08-06 0:17 ` bugzilla-daemon
2021-10-04 23:46 ` 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-213201-2300-4ql6bVCIQw@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.