On Sun, Jun 09, 2024 at 01:16:32PM +0000, Joost Roeleveld wrote > > I run with xorg-server set suid, and no elogind. Could that have > > caused it? > > It might, but then I would expect it more often. > Did, by any chance, the cooling fail (even temporarily) and the system > hard-locked when the overheat protection of the CPU or GPU kicked in?
Thanks; that may be it. I normally build my kernel with default frequency governor = "userspace", and "p_states" disabled in boot options, to allow me to run a custom script to select the CPU speed manually in various steps from 800 mhz to 2.9 Ghz. Structures seem to have changed recently and my script no longer works. My ICEWM toolbar showed the CPU speed was pegged at 2.901 Ghz, even when idling. Run the CPU at max speed 24x7 and it likely will overheat. I rebuilt the kernel with default governor "schedutil", and with "p_states" enabled, and enabled "p_states" in boot options. Now the default frequency is 800 mhz when idling, according to ICEWM tooltip. I ran a "torture test" like so. As root... * cd /usr/src/linux * mv .config .. (*VERY IMPORTANT*!!!) * make mrproper (cleans up /usr/src/linux) * cp ../.config . ...and recompiled the kernel again. Under "schedutil", the CPU tooltip showed the frequency bouncing around 4.1 to 4.2 Ghz!!! How is this even possible? I ran the compile under the "time" command, and got... real 15m17.424s user 13m56.194s sys 1m3.516s ...including copying the kernel, the map file, and the .config file to /boot. This is a record fast time for a full compile on my desktop PC. As soon as this finishes, the frequency falls back down to 800 mhz. The freeze that I posted about happened while watching Youtube. Depending on the video/commercial, the frequency while watching Youtube now bounces around 1 Ghz to 2 Ghz. I hope this is the actual solution. -- Roses are red Roses are blue Depending on their velocity Relative to you
