Nouveau - Dec 2023 - [REGRESSION]: nouveau: Asynchronous wait on fence

On 11/21/23 14:23, Owen T. Heisler wrote:
> On 11/21/23 09:16, Linux regression tracking (Thorsten Leemhuis) wrote:
>> On 15.11.23 07:19, Owen T. Heisler wrote:
>>> On 10/31/23 04:18, Linux regression tracking (Thorsten Leemhuis)
wrote:
>>>> On 28.10.23 04:46, Owen T. Heisler wrote:
>>>>> #regzbot introduced:
d386a4b54607cf6f76e23815c2c9a3abc1d66882
>>>>> #regzbot link:
https://gitlab.freedesktop.org/drm/nouveau/-/issues/180
>>>>>
>>>>> 3. Suddenly the secondary Nvidia-connected display turns
off and X
>>>>> stops responding to keyboard/mouse input.
> I am currently testing v6.6 with the culprit commit reverted.
- v6.6: fails
- v6.6 with the culprit commit reverted: works

See <https://gitlab.freedesktop.org/drm/nouveau/-/issues/180> for full 
details including a decoded kernel log.

Thanks,
Owen

--
Owen T. Heisler
<https://owenh.net>

Karol, Lyude, and Daniel:

On 29.11.23 01:37, Owen T. Heisler wrote:
> On 11/21/23 14:23, Owen T. Heisler wrote:
>> On 11/21/23 09:16, Linux regression tracking (Thorsten Leemhuis) wrote:
>>> On 15.11.23 07:19, Owen T. Heisler wrote:
>>>> On 10/31/23 04:18, Linux regression tracking (Thorsten
Leemhuis) wrote:
>>>>> On 28.10.23 04:46, Owen T. Heisler wrote:
>>>>>> #regzbot introduced:
d386a4b54607cf6f76e23815c2c9a3abc1d66882
>>>>>> #regzbot link:
>>>>>> https://gitlab.freedesktop.org/drm/nouveau/-/issues/180
>>>>>>
>>>>>> 3. Suddenly the secondary Nvidia-connected display
turns off and X
>>>>>> stops responding to keyboard/mouse input.
> 
>> I am currently testing v6.6 with the culprit commit reverted.
> 
> - v6.6: fails
> - v6.6 with the culprit commit reverted: works
> 
> See <https://gitlab.freedesktop.org/drm/nouveau/-/issues/180> for
full
> details including a decoded kernel log.
Not sure about the others, but it's kind of confusing that you update
the issue descriptions all the time and never add a comment to that ticket.

Anyway: Nouveau maintainers, could any of you at least comment on this?
Sure, it's the regression is caused by an old commit (6eaa1f3c59a707 was
merged for v5.14-rc7) and reverting it likely is not a option, but it
nevertheless it would be great if this could be solved somehow.

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.

#regzbot poke

Hi Thorsten and others,

On 12/5/23 06:33, Thorsten Leemhuis wrote:
> On 29.11.23 01:37, Owen T. Heisler wrote:
>> On 11/21/23 14:23, Owen T. Heisler wrote:
>>> On 11/21/23 09:16, Linux regression tracking (Thorsten Leemhuis)
wrote:
>>>> On 15.11.23 07:19, Owen T. Heisler wrote:
>>>>> On 10/31/23 04:18, Linux regression tracking (Thorsten
Leemhuis) wrote:
>>>>>> On 28.10.23 04:46, Owen T. Heisler wrote:
>>>>>>> #regzbot introduced:
d386a4b54607cf6f76e23815c2c9a3abc1d66882
>>>>>>> #regzbot link:
>>>>>>>
https://gitlab.freedesktop.org/drm/nouveau/-/issues/180
>>>>>>>
>>>>>>> 3. Suddenly the secondary Nvidia-connected display
turns off and X
>>>>>>> stops responding to keyboard/mouse input.
>>
>>> I am currently testing v6.6 with the culprit commit reverted.
>>
>> - v6.6: fails
>> - v6.6 with the culprit commit reverted: works
>>
>> See <https://gitlab.freedesktop.org/drm/nouveau/-/issues/180> for
full
>> details including a decoded kernel log.
> 
> Not sure about the others, but it's kind of confusing that you update
> the issue descriptions all the time and never add a comment to that ticket.
Thank you for the feedback; I will use comments more for future updates 
there. I didn't know anyone was following that issue (I haven't received
any reply from nouveau developers on the nouveau list [1] or on gitlab 
[2]) so I have tried to keep that issue description succinct and 
up-to-date for anyone reading it for the first time.

[1]: 
<https://lists.freedesktop.org/archives/nouveau/2022-September/041001.html>
[2]: But Karol Herbst did add the "regression" label.
> Anyway: Nouveau maintainers, could any of you at least comment on this?
> Sure, it's the regression is caused by an old commit (6eaa1f3c59a707
was
> merged for v5.14-rc7) and reverting it likely is not a option, but it
> nevertheless it would be great if this could be solved somehow.
Also if anyone has any ideas about any stress-tests or anything else 
that I might be able to trigger the crash with, please share.

Thanks,
Owen

--
Owen T. Heisler
<https://owenh.net>