From: Borislav Petkov <bp@alien8.de>
To: Michal Kubecek <mkubecek@suse.cz>
Cc: "Christian König" <christian.koenig@amd.com>,
amd-gfx@lists.freedesktop.org,
"Mikhail Gavrilov" <mikhail.v.gavrilov@gmail.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: amdgpu refcount saturation
Date: Thu, 22 Dec 2022 23:43:20 +0100 [thread overview]
Message-ID: <Y6TdiG5atyse+5De@zn.tnic> (raw)
In-Reply-To: <20221222212037.bynlebvgt6ejehut@lion.mk-sys.cz>
On Thu, Dec 22, 2022 at 10:20:37PM +0100, Michal Kubecek wrote:
> Unfortunately, just like Boris, I always seem to have multiple stack
> traces tangled together.
See if this fixes it:
https://lore.kernel.org/r/20221219104718.21677-1-christian.koenig@amd.com
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
prev parent reply other threads:[~2022-12-22 22:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-17 11:53 amdgpu refcount saturation Borislav Petkov
2022-12-19 8:23 ` Christian König
2022-12-22 21:20 ` Michal Kubecek
2022-12-22 22:43 ` Borislav Petkov [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=Y6TdiG5atyse+5De@zn.tnic \
--to=bp@alien8.de \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=mkubecek@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).