Hello. Problem: cat /proc/mounts none /run /hurd/tmpfs writable,no-suid,relatime,no-inherit-dir-group,no sync,size=206440K 0 0 none /run/lock /hurd/tmpfs writable,no-suid,no-exec,relatime,no-inherit-dir- group,no-sync,size=5M 0 0 none /dev/shm /hurd/tmpfs writable,relatime,no-inherit-dir-group,no- sync,size=1032268K 0 0
Solution: settrans -fg /dev/shm chmod 1777 /dev/shm The mount of /dev/shm as tmpfs caused the problem. Now under X windows on hurd-i386: glxgears ... 1300 frames in 5.0 seconds = 260.000 FPS. This problem is similar to the problems reported at:https://darnassus.sceen.net/~hurd-web/open_issues/tmpfs/ Thanks! On Tue, 2026-01-27 at 16:23 +0100, Svante Signell wrote: > Hi, > > Krzysztof Sobiecki (@sobkas) is porting mesa to GNU/Hurd using software > rendering options, see > https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3927 > > According to my findings these patches works fine on hurd-amd64 both > for ssh -Y and in the X window manager. However, on hurd-i386 only > works with ssh -Y, not in X. The error is bus error, but looking closer > with gdb, the problem is a memory error (probably shared memory): > Example: Cannot access memory at address 0xfab2000Cannot access memory > at address 0xfab2000... > > Version of mesa tested on both 32bit and 64bit Hurd is 25.3.3-1. > Also tested several versions of my own patches with libdrm is 25.2.8-2 > on 32bit. All with the same memory error. > > sobkas has tested upstream version 26.0.0~devel{11/12} and claims > everything is fine both on 32bit and 64bit Hurd. > > Can somebody please check if the 32-bit Hurd version 25.3.3-1 fails or > works on 32bit (and 64bit). Attached are sobkas upstream patches, > 39277.patch, together with patches for > debian/{changelog,rules,control.in,libglx-mesa0.symbols.hurd} > > Maybe the patch for libdrm-dev, debian_control.in.patch1 does not apply > until an updated debian/control is generated. Easily fixed by > debian/rules clean followed by dpkg-buildpackage ... > > Thanks! >
