From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 213201] [KAVERI] memory leak - unreferenced object 0xffff8881700cf988 (size 56)
Date: Mon, 04 Oct 2021 23:46:40 +0000 [thread overview]
Message-ID: <bug-213201-2300-vKEv6pFWpY@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 #14 from Erhard F. (erhard_f@mailbox.org) ---
Created attachment 299101
--> https://bugzilla.kernel.org/attachment.cgi?id=299101&action=edit
utput of /sys/kernel/debug/kmemleak (kernel 5.15-rc4, AMD PRO A10-8750B)
Same board, another CPU:
# cat /sys/kernel/debug/kmemleak
unreferenced object 0xffff8881010b5278 (size 56):
comm "systemd-udevd", pid 198, jiffies 4294881523 (age 926.930s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 0d 01 70 00 00 00 00 00 ..........p.....
4b 5f 02 00 00 c9 ff ff 00 00 00 00 00 00 00 00 K_..............
backtrace:
[<ffffffff9df51ae1>] acpi_ps_alloc_op+0x8b/0x1c4
[<ffffffff9df4ec89>] acpi_ps_create_op+0x48c/0x8ca
[<ffffffff9df4d7b9>] acpi_ps_parse_loop+0x401/0x1062
[<ffffffff9df50a3e>] acpi_ps_parse_aml+0x1cd/0x6ea
[<ffffffff9df5255e>] acpi_ps_execute_method+0x51f/0x57b
[<ffffffff9df42193>] acpi_ns_evaluate+0x64b/0x885
[<ffffffff9df4a12f>] acpi_evaluate_object+0x333/0x68d
[<ffffffffc15b70f9>] amdgpu_atcs_call.constprop.0+0x129/0x1f0 [amdgpu]
[<ffffffffc15b7b79>] amdgpu_atcs_pci_probe_handle.isra.0+0x159/0x2d0
[amdgpu]
[<ffffffffc15b8950>] amdgpu_acpi_detect+0xb0/0x470 [amdgpu]
[<ffffffffc243b0a8>] chacha_2block_xor_avx2+0xa8/0x220 [chacha_x86_64]
[<ffffffff9d001b0b>] do_one_initcall+0xbb/0x3e0
[<ffffffff9d2a7509>] do_init_module+0x1c9/0x6e0
[<ffffffff9d2af427>] load_module+0x78c7/0x9bb0
[<ffffffff9d2b1a40>] __do_sys_finit_module+0x110/0x180
[<ffffffff9e7f1836>] do_syscall_64+0x66/0x90
unreferenced object 0xffff8881010b5c38 (size 56):
comm "systemd-udevd", pid 198, jiffies 4294881523 (age 926.930s)
hex dump (first 32 bytes):
78 52 0b 01 81 88 ff ff 0d 01 2d 00 00 00 00 00 xR........-.....
4c 5f 02 00 00 c9 ff ff 00 00 00 00 00 00 00 00 L_..............
backtrace:
[<ffffffff9df51ae1>] acpi_ps_alloc_op+0x8b/0x1c4
[<ffffffff9df4ec89>] acpi_ps_create_op+0x48c/0x8ca
[<ffffffff9df4d7b9>] acpi_ps_parse_loop+0x401/0x1062
[<ffffffff9df50a3e>] acpi_ps_parse_aml+0x1cd/0x6ea
[<ffffffff9df5255e>] acpi_ps_execute_method+0x51f/0x57b
[<ffffffff9df42193>] acpi_ns_evaluate+0x64b/0x885
[<ffffffff9df4a12f>] acpi_evaluate_object+0x333/0x68d
[<ffffffffc15b70f9>] amdgpu_atcs_call.constprop.0+0x129/0x1f0 [amdgpu]
[<ffffffffc15b7b79>] amdgpu_atcs_pci_probe_handle.isra.0+0x159/0x2d0
[amdgpu]
[<ffffffffc15b8950>] amdgpu_acpi_detect+0xb0/0x470 [amdgpu]
[<ffffffffc243b0a8>] chacha_2block_xor_avx2+0xa8/0x220 [chacha_x86_64]
[<ffffffff9d001b0b>] do_one_initcall+0xbb/0x3e0
[<ffffffff9d2a7509>] do_init_module+0x1c9/0x6e0
[<ffffffff9d2af427>] load_module+0x78c7/0x9bb0
[<ffffffff9d2b1a40>] __do_sys_finit_module+0x110/0x180
[<ffffffff9e7f1836>] do_syscall_64+0x66/0x90
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2021-10-04 23:46 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
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 [this message]
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-vKEv6pFWpY@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox