Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.
Admin message
Equinix is shutting down its operations with us on April 30, 2025. They have graciously supported us for almost 5 years, but all good things come to an end. We are expecting to transition to new infrastructure between late March and mid-April. We do not yet have a firm timeline for this, but it will involve (probably multiple) periods of downtime as we move our services whilst also changing them to be faster and more responsive. Any updates will be posted in freedesktop/freedesktop#2011 as it becomes clear, and any downtime will be announced with further broadcast messages.
Mathieu Malaterrechanged title from WARNING: CPU: 0 PID: 430 at drivers/gpu/drm/nouveau/nvkm/engine/gr/g84.c:171 g84_gr_tlb_flush+0x2eb/0x300 [nouveau] to RIP: 0010:g84_gr_tlb_flush+0x2eb/0x300 [nouveau]
changed title from WARNING: CPU: 0 PID: 430 at drivers/gpu/drm/nouveau/nvkm/engine/gr/g84.c:171 g84_gr_tlb_flush+0x2eb/0x300 [nouveau] to RIP: 0010:g84_gr_tlb_flush+0x2eb/0x300 [nouveau]
oh sorry, I meant the full dmesg from the time the crash/error happens. This one looks quite clean. I was more interested in anything happening before the error occurs.
ssh from a different computer, run tail -f /var/log/messages
from my DELL workstation, play either with mpv or browse internet with chromium
eventually I get the hard-lock
I am pretty sure, there will be nothing more than what was is in the dmesg I posted. So if we move forward are you sure you don't want me to modprobe nouveau with some kind of verbosity level, eg (totally made-up):
mhhhh, if this is with mpv it could be the multi threading issue we have when you have multiple contexts within the same application. Like OpenGL and VAAPI/VDPAU.
I have some patches to try to fix this, but "ugh".. this is hard to fix as I don't want to cause regressions.
Could you reference the bug you are referring to ? If there is a small reproducer, I should be able to try it and then close the current bug as duplicate of this other one.
Since I have no better choice, I tried compiling nvidia-driver on my Debian/buster/bpo system, I was able to trigger the following symptoms. See: