QPS crashing on some hardware (hyperthreading-related?)

Hi there,

I have noticed that QPS, the system tool that displays and manage processes, installed by default cannot work when the CPU mitigation file is loaded by GRUB (/etc/default/grub.d/40_cpu_mitigations.cfg).

Once this configuration file isn’t loaded by GRUB, the application QPS works fine.

3 Likes

What in particular isn’t working? It seems fine here, and I have 40_cpu_mitigations.cfg enabled.

2 Likes

When trying to launch QPS from terminal, it returns a message saying that CPU can’t be reached in its entirely. Sorry, not in front of the machine to reproduce it right now

1 Like

Hmm, ok. If you can take a screenshot once you can reproduce it, that would be quite useful.

2 Likes

I have reproduced it once the CPU mitigations cfg file is again taken into account by GRUB. See image.

Besides, htop and top work just fine, with or without the CPU mitigations cfg.

3 Likes

Can you run cat /proc/stat on the affected machine and share the output here?

2 Likes

Here is the result (picture from Mobile, can’t connect the machine to the net right now)

3 Likes

OK, I think I know what’s going on. One last test, can you please:

  • Disable the CPU mitigations file the same way you did before (presumably something like sudo mv /etc/default/grub.d/40_cpu_mitigations.cfg /home/sysmaint/; sudo update-grub)
  • Reboot the system, but then when the boot menu appears…
  • …hover over PERSISTENT Mode | USER Session | daily activities, and then press e rather than pressing Enter.
  • Move the cursor to the line that starts with the word linux, then move it to the end of the line.
  • Type a single space, then type nosmt=force.
  • Press Ctrl+X to boot with the modified boot configuration.
  • Try to launch QPS again and see if it fails with the same error.

I think what’s happening is that your CPU doesn’t present all cores as contiguous when hyperthreading is turned off, and QPS doesn’t know how to handle gaps in the cores.

2 Likes

Hello,

Sorry for late reply.

I did follow your instructions and QPS still falls to start with the same error:

1 Like

Yeah, then that’s almost certainly what’s happening. I’ll report the issue to LXQt and Debian.

3 Likes

Thanks, I hope this can help

2 Likes

Reproduced, reported upstream:

2 Likes