Hi Claudio, On Mon, Nov 17, 2025 at 11:50:08AM +0100, Claudio Jeker wrote: > On Mon, Nov 17, 2025 at 10:45:00AM +0000, Stuart Henderson wrote: > > On 2025/11/17 10:20, Martin Pieuchot wrote: > > > Hello Walter, > > > > > > On 17/11/25(Mon) 07:27, Walter Alejandro Iglesias wrote: > > > > On Tue, Nov 11, 2025 at 12:12:19PM +0100, Walter Alejandro Iglesias > > > > wrote: > > > > > Lately I reported this in ports@: > > > > > > > > > > https://marc.info/?l=openbsd-ports&m=176262090530440&w=2 > > > > > > > > > > I'm moving this here since I don't think it's a problem with blender > > > > > but > > > > > with Xorg and drm (not too long ago Xorg freezed on this machine while > > > > > watching a video with mpv.) > > > > > > > > > > > > > Apparently, on this machine and with OpenBSD, any program that stresses > > > > the CPU eventually causes X11 to become completely unresponsive. We are > > > > talking about a i3 from 2022 with 32GB RAM. Today, running this: > > > > > > > > $ stress -v --cpu 4 --io 4 --vm 2 --vm-bytes 128M > > > > > > Where is this command coming from? > > > > ports/sysutils/stress > > > > it might be educational to turn off some of the process types on > > the 'stress' command line and see if it still occurs with e.g. > > just vm workers, or just io workers, or whether a combination is > > needed. > > > > Also check out the diff from jca@ to fix an issue in sleep handling in the > drm code. This could cause things to fail in strange ways.
Could you point me a link to that diff, please? > > -- > :wq Claudio > -- Walter
