2024-06-24, 07:06 PM
(2024-06-24, 04:29 PM)pcm Wrote: I'd start atI don't think the container allows this, as it's good practice to lock containers down as much as possible.sysloganddmesgin the container to see what's going on when the error happens. If there's nothing in the container's syslogs/dmesg then i'd check host'sdmesg.
(2024-06-24, 04:29 PM)pcm Wrote: Another thing you could do is enable nvlog.I can't find anything about this online, could you explain a bit more?(2024-06-24, 04:29 PM)pcm Wrote: IMHO unattended upgrade should not cause such behavior (atleast not for me and I am way behind on my upgrade for my gpu)... It could be an actual hardware issue (with your specific GPU) or could be a bug with your specific GPU device driver (either in the passthru module or somewhere else)...I do actually think this could be caused by a driver upgrade, the container has a loaded library that communicates with the docker passed through device, if the host driver suddenly changes, the library can't communicate with the gpu anymore as it suddenly uses a mismatched driver.