From: Johannes Hirte <johannes.hirte-rSzmJuYucINa7YElYzY8/Q@public.gmane.org>
To: Chunming Zhou <zhoucm1-5C7GfCeVMHo@public.gmane.org>
Cc: Martin Babutzka
<martin.babutzka-BGeptl67XyCzQB+pC5nmwQ@public.gmane.org>,
amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: Kernel crash/Null pointer dereference on vblank
Date: Thu, 23 Nov 2017 13:27:11 +0100 [thread overview]
Message-ID: <20171123122711.GA3445@probook> (raw)
In-Reply-To: <56b938ac-4597-a354-0f4a-0c2625b10c5a-5C7GfCeVMHo@public.gmane.org>
On 2017 Nov 23, Chunming Zhou wrote:
> See the attached email, they fixed same issue, each of them is ok to fix
> your issue, your calltrace is same as the second.
>
> We should already push the first patch in early time, could you check if
> the first patch is in your branch?
>
This patch (series) is not upstream yet. Just tested it, but this doesn't fix the
use-after-free on S3 resume with dc enabled.
--
Regards,
Johannes
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2017-11-23 12:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 7:06 Kernel crash/Null pointer dereference on vblank Martin Babutzka
[not found] ` <1228839336.50367.1511334398694-NM1PAhYDU/Oo9dU1Uvar1Q@public.gmane.org>
2017-11-22 15:07 ` Johannes Hirte
2017-11-22 22:31 ` Johannes Hirte
2017-11-23 2:18 ` Chunming Zhou
[not found] ` <58b24f03-b71b-4208-4cb7-4706ba947dea-5C7GfCeVMHo@public.gmane.org>
2017-11-23 8:31 ` Johannes Hirte
2017-11-23 10:07 ` Chunming Zhou
[not found] ` <56b938ac-4597-a354-0f4a-0c2625b10c5a-5C7GfCeVMHo@public.gmane.org>
2017-11-23 12:27 ` Johannes Hirte [this message]
2017-11-23 15:17 ` Leo Li
[not found] ` <eb1a453e-0705-ede7-bedd-dbc8668cd71d-5C7GfCeVMHo@public.gmane.org>
2017-11-23 17:28 ` Johannes Hirte
-- strict thread matches above, loose matches on Subject: below --
2017-11-19 21:54 Martin Babutzka
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=20171123122711.GA3445@probook \
--to=johannes.hirte-rszmjuyucina7yelyzy8/q@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=martin.babutzka-BGeptl67XyCzQB+pC5nmwQ@public.gmane.org \
--cc=zhoucm1-5C7GfCeVMHo@public.gmane.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.