From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: "Owen T. Heisler" <writer@owenh.net>, stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
regressions@lists.linux.dev, nouveau@lists.freedesktop.org,
Ben Skeggs <bskeggs@redhat.com>
Subject: Re: [Nouveau] [REGRESSION]: nouveau: Asynchronous wait on fence
Date: Tue, 31 Oct 2023 10:18:50 +0100 [thread overview]
Message-ID: <5ecf0eac-a089-4da9-b76e-b45272c98393@leemhuis.info> (raw)
In-Reply-To: <6f027566-c841-4415-bc85-ce11a5832b14@owenh.net>
On 28.10.23 04:46, Owen T. Heisler wrote:
> #regzbot introduced: d386a4b54607cf6f76e23815c2c9a3abc1d66882
> #regzbot link: https://gitlab.freedesktop.org/drm/nouveau/-/issues/180
>
> ## Problem
>
> 1. Connect external display to DVI port on dock and run X with both
> displays in use.
> 2. Wait hours or days.
> 3. Suddenly the secondary Nvidia-connected display turns off and X stops
> responding to keyboard/mouse input. In *some* cases it is possible to
> switch to a virtual TTY with Ctrl+Alt+Fn and log in there. In any
> case, shutdown/reboot after this happens is *usually* not successful
> (forced power-off is required).
>
> This started happening after the upgrade to Debian bullseye, and the
> problem remains with Debian bookworm.
> [...]
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. For details about these aspects, see:
https://linux-regtracking.leemhuis.info/post/frequent-reasons-why-linux-kernel-bug-reports-are-ignored/
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.
That might help getting things rolling, but it's a pretty old
regression, which complicates things.
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.
next prev parent reply other threads:[~2023-10-31 9:39 UTC|newest]
Thread overview: 10+ 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) [this message]
2023-11-02 4:11 ` Owen T. Heisler
2023-11-15 6:19 ` Owen T. Heisler
2023-11-21 15:16 ` [Nouveau] " 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 ` [Nouveau] " Owen T. Heisler
2023-12-11 8:19 ` Linux regression tracking #update (Thorsten Leemhuis)
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=5ecf0eac-a089-4da9-b76e-b45272c98393@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=bskeggs@redhat.com \
--cc=nouveau@lists.freedesktop.org \
--cc=regressions@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=writer@owenh.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).