On Wed, May 6, 2020 at 3:21 AM <tu...@posteo.de> wrote: > > > Hi, > > while rendering with Blender the system performance (especially > graphic related stuff) lacks. That's not nice but it seems that this > is the way it is designed. > > What makes me a little nervous are freezes of several seconds. It not > onlu freezes but the whole graphical interface of everything locks > down (I couldn't find a corona computer virus, though). > > In the Xorg log I found this: > > [ 2808.761] (WW) NVIDIA: Wait for channel idle timed out. > > which possibly match such a moment of a freeze. > > My setup: > Blender 2.90a (alpha) and Blender 2.83 (beta) and > Blender 2.82a (stable). > All Blender versions show the same problem. > > X11/Openbox > > NVidia 484.82 as delivered by NVidia, since the Gentoo > package does not install all files of the driver which > are needed for Blender (for example to support Optix). > > No other application, which heavily uses the GPU was > running at that time. > > MSI RTX 2060 SUPER > Ryzen 5 3600 > 32GB RAM > MSI Tomahawk MAX > > Does everyone has the same problems probably already solved > or any idea how I can those freezes? > > Any help or idea what causes this freezes is very appreciated! :) > > Cheers! > Meino > > >
Meino, Generically, you need to set up some sort of real-time monitoring and watch to see what is using CPU and/or I/O when the machine 'appears' to hang. I say 'appears' because the machine is probably running correctly but doing something other than Blender work. NOTE: You didn't say that there is or isn't any disk activity when this happens. When I look at this sort of problem I set up a second machine, ssh in with a bunch of terminals and start with 'top' and 'iotop' to watch for what process might be using resources. top watches CPU, iotop watches disk. Conceptually networking can lock up the machine but it's never happened to me. You can also look to see if some piece of hardware is generating too many interrupts. Do watch cat /proc/interrupts in a wide terminal when not running Blender to get used to what the machine does when idle, then run Blender and see if anything is going crazy generating interrupts. I hope some part of this helps you find your problem. Mark
