From: "Owen T. Heisler" <writer@owenh.net>
To: Linux regressions mailing list <regressions@lists.linux.dev>,
stable@vger.kernel.org
Cc: nouveau@lists.freedesktop.org, Karol Herbst <kherbst@redhat.com>,
Lyude Paul <lyude@redhat.com>, Ben Skeggs <bskeggs@redhat.com>,
Sasha Levin <sashal@kernel.org>
Subject: Re: [REGRESSION]: nouveau: Asynchronous wait on fence
Date: Wed, 1 Nov 2023 23:11:08 -0500 [thread overview]
Message-ID: <f98d5544-34f8-4b35-9466-80fa9671686d@owenh.net> (raw)
In-Reply-To: <5ecf0eac-a089-4da9-b76e-b45272c98393@leemhuis.info>
On 10/31/23 04:18, Linux regression tracking (Thorsten Leemhuis) wrote:
> Thanks for your report. With a bit of luck someone will look into this,
> But I doubt it, as this report has some aspects why it might be ignored.
> Mainly: (a) the report was about a stable/longterm kernel and (b)it's
> afaics unclear if the problem even happens with the latest mainline
> kernel.
> You thus might want to check if the problem occurs with 6.6 -- and
> ideally also check if reverting the culprit there fixes things for you.
Thorsten,
Thank you for your reply and suggestions. I will try (a) testing on
mainline (when I tried before I was interrupted by another, unrelated
regression) and (b) reverting the culprit commit there if I am able to
reproduce the problem.
Thanks,
Owen
--
Owen T. Heisler
https://owenh.net
next prev parent reply other threads:[~2023-11-02 4:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-28 2:46 [REGRESSION]: nouveau: Asynchronous wait on fence Owen T. Heisler
2023-10-31 9:18 ` Linux regression tracking (Thorsten Leemhuis)
2023-11-02 4:11 ` Owen T. Heisler [this message]
2023-11-15 6:19 ` Owen T. Heisler
2023-11-21 15:16 ` Linux regression tracking (Thorsten Leemhuis)
2023-11-21 20:23 ` Owen T. Heisler
2023-11-29 0:37 ` Owen T. Heisler
2023-12-05 12:33 ` Thorsten Leemhuis
2023-12-06 4:08 ` Owen T. Heisler
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=f98d5544-34f8-4b35-9466-80fa9671686d@owenh.net \
--to=writer@owenh.net \
--cc=bskeggs@redhat.com \
--cc=kherbst@redhat.com \
--cc=lyude@redhat.com \
--cc=nouveau@lists.freedesktop.org \
--cc=regressions@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).