From: Borislav Petkov <bp@alien8.de>
To: "Christian König" <christian.koenig@amd.com>
Cc: Huang Rui <ray.huang@amd.com>,
lkml <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org
Subject: Re: 5.11-rc1 TTM list corruption
Date: Mon, 4 Jan 2021 11:58:02 +0100 [thread overview]
Message-ID: <20210104105802.GD32151@zn.tnic> (raw)
In-Reply-To: <e3bfa0a4-5d0a-bd68-6cc8-73db1d29f22c@amd.com>
On Fri, Jan 01, 2021 at 03:34:28PM +0100, Christian König wrote:
> Going to double check the code, but can you reproduce this issue
> reliable?
Lemme find a test box which can trigger it too - the splat happened
on my workstation and I'd like to avoid debugging there for obvious
reasons.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@alien8.de>
To: "Christian König" <christian.koenig@amd.com>
Cc: Huang Rui <ray.huang@amd.com>,
dri-devel@lists.freedesktop.org,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: 5.11-rc1 TTM list corruption
Date: Mon, 4 Jan 2021 11:58:02 +0100 [thread overview]
Message-ID: <20210104105802.GD32151@zn.tnic> (raw)
In-Reply-To: <e3bfa0a4-5d0a-bd68-6cc8-73db1d29f22c@amd.com>
On Fri, Jan 01, 2021 at 03:34:28PM +0100, Christian König wrote:
> Going to double check the code, but can you reproduce this issue
> reliable?
Lemme find a test box which can trigger it too - the splat happened
on my workstation and I'd like to avoid debugging there for obvious
reasons.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2021-01-04 10:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-31 10:40 5.11-rc1 TTM list corruption Borislav Petkov
2020-12-31 10:40 ` Borislav Petkov
2021-01-01 3:46 ` Hillf Danton
2021-01-01 14:34 ` Christian König
2021-01-01 14:34 ` Christian König
2021-01-04 10:58 ` Borislav Petkov [this message]
2021-01-04 10:58 ` Borislav Petkov
2021-01-04 14:48 ` Christian König
2021-01-04 14:48 ` Christian König
2021-01-05 4:12 ` Huang Rui
2021-01-05 4:12 ` Huang Rui
2021-01-05 10:31 ` Borislav Petkov
2021-01-05 10:31 ` Borislav Petkov
2021-01-05 11:08 ` Huang Rui
2021-01-05 11:08 ` Huang Rui
2021-01-05 11:34 ` Christian König
2021-01-05 11:34 ` Christian König
2021-01-05 11:43 ` Borislav Petkov
2021-01-05 11:43 ` Borislav Petkov
2021-01-05 12:20 ` Huang Rui
2021-01-05 12:20 ` Huang Rui
2021-01-05 15:40 ` Christian König
2021-01-05 15:40 ` Christian König
2021-01-06 16:54 ` David Woodhouse
2021-01-06 16:54 ` David Woodhouse
2021-01-06 17:10 ` Alex Deucher
2021-01-06 17:10 ` Alex Deucher
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=20210104105802.GD32151@zn.tnic \
--to=bp@alien8.de \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ray.huang@amd.com \
/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.