A lot of X is already stood up by the time the X "weave" background is running.
Maybe do a test by having the X server start and just display an xterm instead of another X app? It could be a bunch of stuff hiding in the X init shell script path that's doing "stuff" as part of the X env setup before a window manager is run. (and .. honestly it could even be something stupid like DNS..) -a On Thu, 27 Aug 2026 at 07:19, Mouse <[email protected]> wrote: > > >> So, I'm wondering if anyone knows what might be behind this, or has > >> any suggestions for something to try, or the like. [...] > > Maybe a system call trace to see what is slower on the 10.x kernels? > > A bit of a sledgehammer, but, yes, I may eventually resort to that. At > present I don't even know whether the slowdown is in a syscall, though > it seems likely since a 9.x X server talking to the same hardware > without kernel involvement *shouldn't* be any slower. > > /~\ The ASCII Mouse > \ / Ribbon Campaign > X Against HTML [email protected] > / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B >
