• 0 Posts
  • 40 Comments
Joined 2 years ago
cake
Cake day: November 7th, 2023

help-circle
  • Jesus, how do you people always come up with the most inane conspiracies. I have a company that manufactures devices that communicate wirelessly. The new RED is a huge pain in the ass, along with the CRA.

    Absolutely no company pushed for this. The new legislations and directives cause a ton of additional work and obligations for companies, e. g. software has to be certified as part of the compliance check, things that were previously approved via self-reports now involve trusted 3rd parties, and reports of violations to government bodies are now mandatory.

    And you know what, even though this costs a bunch of money that could go elsewhere and the whole thing is so new that even the certification bodies have no idea what is going on, even though we have to setup completely new processes, spend endless hours documenting things, I still appreciate both initiatives.

    As an end customer, I would love if e. g. the software that runs on the mobile payment terminal taking my card info is certified. I would love if the developer of the software running on the PLC on my shop floor has to check CVEs, inform me about security issues and has to deliver 5 to 10 years of updates.

    Not a fan of Samsung and their shitty software, but they’re simply preemptively covering their ass, nothing more.

    I’d also still want to unlock my bootloader. I’m sure the whole legal situation will become less muddled, enabling just that.






  • I don’t know what your previous setup was, but given that running resolved fixes your DNS issues, run:

    ln -sf ../run/systemd/resolve/stub-resolv.conf /etc/resolv.conf

    This will point programs that use /etc/resolved.conf during DNS resolution to the local DNS server provided by systemd-resolved.

    Then, enable resolved so that it is started when you reboot:

    systemctl enable systemd-resolved.service

    Finally, start the service so that it is available immediately:

    systemctl start systemd-resolved.service

    You will want it run those with the required permissions, e. g. via sudo.






  • 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.