On 2024/10/14 14:30, Stuart Henderson wrote: > On 2024/10/08 11:08, Mark Kettenis wrote: > > > > $ ls -lh /var/log/Xorg.0.log* > > > > -rw-r--r-- 1 root wheel 45.6K Oct 7 13:37 /var/log/Xorg.0.log > > > > -rw-r--r-- 1 root wheel 433M Oct 3 11:48 /var/log/Xorg.0.log.old > > > > > > > > hmm, there are loads of modeline dumps: > > > > Probably means there is an issue with hotplug detection. Could be a > > dodgy cable, but if it happens on more machines that is unlikely. > > There are two types of machine, running the exact same config / > software, with the same monitor type. Mostly the newer ones with > > + (II) modeset(0): glamor X acceleration enabled on Mesa Intel(R) Graphics > (ADL-N) > + (II) modeset(0): [DRI2] DRI driver: iris > > which are seeing the problem, but there are still a few older > ones with > > - (II) modeset(0): glamor X acceleration enabled on Mesa Intel(R) HD Graphics > 4400 (HSW GT2) > - (II) modeset(0): [DRI2] DRI driver: crocus > > which aren't running into it. > > I'll get a test machine and have a look at DRMDEBUG for clues there, > any suggestions for anything else I can look at?
I've not got a test machine running yet, but from observations (I haven't gone through all the logs to verify, those "seconds after start" logs are a pain to correlate with time of day!) it seems to only happen when the monitor is in a dpms power-saving mode. Not sure if that rings any bells..
