On Sat, Jun 21, 2025 at 07:00:56PM +0200, Matthieu Herrb wrote: Hello Matthieu,
>> As of somewhere in the last 10-14 days or so, my amd64 machine has >> stopped reliably suspending (for reference: it's reliably suspended for >> the past 9-10 months). Unfortunately I haven't worked out *what* the >> sequence of events that causes this is, so bisecting has proven >> impossible (I tried...). When `zzz` is unsuccessful, X disappears, the >> machine drops to the console (i.e. displaying "Login:" or whatever was >> there last), and then is stuck there indefinitely: it doesn't get as far >> as "Syncing disks". The machine's fans spin up after a while, so >> presumably something is stuck in a busy loop. > I'm seeing something similar on my X395 since some weeks. I *think* > failure to suspend happens only after I've played a few large (HD) video > with mpv, maybe in chrome too. I've not tried to figure out a reproducer. That's interesting! First obvious connection: we're both running AMD systems. I only watch videos in the browser but, yes, I can imagine this might have something to do with the problem. Certainly, it seems I have to do quite a bit of stuff in X before suspend stops working. I perhaps end up watching 1 or 2 videos a day, so that might be why I see the problem intermittently. Jonathan has been patiently dealing with my very vague bug reports. I have ruled out at least two things: the problem doesn't appear to be in the kernel (I went back as far as a May 1st kernel and the problem was still there); and doesn't appear to be in the latest AMD firmware (I downgraded and the problem persistent). As far as I can see that leaves two culprits: xenocara; or something in ports. I haven't yet tried rewinding xenocara. I think that might be a bit tricky, but you might be better placed than me to try that given your familiarity with xenocara :) The idea that something in ports could trigger this would have seemed bonkers to me 2 days ago, but since I've just successfully debugged a bizarre problem where Firefox somehow stops other programs receiving X events [1], I'm now more open-minded on that front! For example: I don't know what the status of the VA-API / Vulkan stuff is. Perhaps something there has been enabled for one or more ports, and that they somehow cause issues? I am clutching at straws a little bit... Laurie [1] https://marc.info/?l=openbsd-bugs&m=175050766031631&w=2
