From time to time, often after I’ve restored from sleep or finished playing a Steam game, one of my CPU cores is pinned at 100% with no indication of what might be doing it. Running htop, btop, or GNOME system monitor all show the same thing: CPU0 at 100% while the rest are doing near-nothing, and no process in particular seems to be using those resources.

If I restart, it’s back to normal, and sometimes I can play a game in Steam or let the computer go to sleep and it doesn’t do this, but it happens often enough that’s annoying/confusing so I’d like to know if there’s a way to either (a) diagnose which processes are using which CPU cores, or (b) somehow “reset” the checking of these values to make sure that something’s not just being misreported.

This is a desktop system running Arch & GNOME.

  • piexil@lemmy.world
    24·
    2 months ago

    Show kernel threads, it’s a setting in the htop config menu that is off by default.

    • Daniel Quinn@lemmy.caOPEnglish
      10·
      2 months ago

      There it is! Thank you! It’s a process owned by root called kworker/0:0+kacpid. Any idea what that is?

      [Edit 1] Interestingly, I can’t even kill -9 it.

      [Edit 2] With kworker kacpid to work with, I did a quick search and found this SO page that has some interesting information that I only partially understand, but the following worked like a charm:

      # grep -Ev "^[ ]*0" /sys/firmware/acpi/interrupts/gpe?? | sort --field-separator=: --key=2 --numeric --reverse | head -1
/sys/firmware/acpi/interrupts/gpe09:11131050     STS enabled      unmasked
# echo disable > /sys/firmware/acpi/interrupts/gpe09

      It’s not clear to me what an interrupt is or whether this gpe09 value is meant to be persistent across reboots, or why this only seems to be happening in the last couple months, but if I can make it go away by running the above from time to time, I guess it’s alright?

      • scrion@lemmy.world
        17·
        2 months ago

        An interrupt is an input that can be triggered to interrupt normal execution. It is used for e. g. hardware devices to signal the processor something has happened that requires timely processing, so that real-time behavior can be achieved (for variable definitions of real-time). Interrupts can also be triggered by software, and this explanation is a gross oversimplification, but that information is what is most likely relevant and interesting for your case at this point.

        The commands you posted will sort the interrupts and output the one with the highest count (via head -1), thereby determining the interrupt that gets triggered the most. It will then disable that interrupt via the user-space interface to the ACPI interrupts.

        One of the goals of ACPI is to provide a kind of general hardware abstraction without knowing the particular details about each and every hardware device. This is facilitated by offering (among other things), general purpose events - GPEs. One of these GPEs is being triggered a lot, and the processing of that interrupt is what causes your CPU spikes.

        The changes you made will not persist after a reboot.

        Since this is handled by kworker, you could try and investigate further via the workqueue tools: https://github.com/torvalds/linux/tree/master/tools/workqueue

        In general, Linux will detect if excessive GPEs are generated (look for the term “GPE storm” in your kernel log) and stop handling the interrupts by switching to polling. If that happens, or if the interrupts are manually disabled, the system might not react to certain events in a timely manner. What that means for each particular case depends on what the interrupts are being responsible for - hard to tell without additional details.

      • cmnybo@discuss.tchncs.deEnglish
        13·
        2 months ago

        That’s a kernel worker for ACPI. It sounds like you may have a driver for something that is misbehaving.

      • henfredemars@infosec.pubEnglish
        6·
        2 months ago

        You can’t kill that because it’s a kernel thread. They are not like normal process; these objects are part of the operating system and terminating such a thread can cause in stability.

      • henfredemars@infosec.pubEnglish
        3·
        2 months ago

        To me it sounds like your root cause is either a driver problem or your hardware is misbehaving a little bit in a way the driver doesn’t expect, firing a lot of interrupts that shouldn’t normally happen.

        If this seems to resolve your issue, I wouldn’t lose any sleep over it. I would think my hardware is a little bit weird or there’s a bug somewhere in the driver for it. You can also try different kernel versions if your distribution gives you the option, because kernels come with different versions of drivers.

  • astrsk@fedia.io
    133·
    2 months ago

    It’s the Linux version of steam taking advantage of idle time to process shaders. It’s a critical part of making all those proton launched games working right. I wish it had better control for when to run it but it is what it is.

  • Tenkard@lemmy.ml
    8·
    2 months ago

    Another quick tip for htop: the red color in the CPU bar means kernel stuff. In my case it was an issue with interrupts

  • TechnoCat@lemm.ee
    7·
    2 months ago

    I have been fighting with this for a long time, do you have an external monitor? I find this happens if I wake from light-sleep (not hibernation) while an external monitor is plugged in.

    One of my ACPI interrupts just goes off the charts.

    • Daniel Quinn@lemmy.caOPEnglish
      2·
      2 months ago

      In one of the other comments, we worked out that it was definitely something to do with ACPI, but yes I do have an external monitor. This is a desktop system.

      Disabling the interrupt did the job, but I don’t know why it’s happening. If this is related to the monitor, could this be an Nvidia thing?

      • TechnoCat@lemm.ee
        1·
        2 months ago

        I have a pretty old integrated Intel GPU. Happens to my Thinkpad pretty regularly.

    • muhyb@programming.dev
      1·
      2 months ago

      Similar thing happens to me with my two monitor setup. No problem when I use single monitor. No problem when I use two monitor. However when I plugged out the second monitor or switch to single monitor with my script, the CPU starts doing random spikes on single cores in short intervals. Only a reboot fixes this.

  • thingsiplay@beehaw.org
    21·
    2 months ago

    It’s probably Shader compilation. Funny enough the top result of my websearch is my own post/thread in Reddit 4 years ago. I had this exact same question on my old computer: https://www.reddit.com/r/linux_gaming/comments/kyf1wf/why_is_steam_using_one_core_always_but_doing/ Shader compilation is done from time to time in the background while Steam runs. This prepares games to run better.

    Look if there is a process called fosselize. That was the process name back then doing the Shader compilation.

      • thingsiplay@beehaw.org
        2·
        2 months ago

        Yes. That’s the benefit of having a single hardware to target. Same goes for consoles. They obviously know the hardware (like in Steam Deck’s case) and can precompile and ship it. There was plans (or just talks? not sure if this was ever realized) that users can download precompiled Shaders from other users, if its the exact same hardware.

  • ReversalHatchery@beehaw.orgEnglish
    1·
    2 months ago

    since your CPU has 16 threads (“cores” but not really cores, you probably only have 8 of that), if a process uses up all the capacity of a single core, that will have a 100/16 = ~6% cpu usage. In my experience looking for this really works… at least on windows, please don’t hurt me. it should on linux too, but there I don’t have it at such a visible place.

    this may not work that much though when your system is under a higher load, and the process you’re looking for also has a higher CPU usage, like 30% or something.
    in this case you’ll want to look for the cpu usage of the individual threads of processes with a higher cpu usage. if you have a process which has a thread with 6% cpu usage (in case of a 16 hardware thread cpu), then that process is at fault. by looking at the name of the thread you may even find out what is its purpose.