Page 1 of 2
One CPU core maxed out by a process
Posted: Mon Feb 22, 2021 10:40 am
by Villano
HI, as the title says. I'm a total newbie, btw.
Running the 'top' command I get:
Code: Select all
top - 12:33:56 up 12:46, 1 user, load average: 3.72, 3.64, 3.31
Tasks: 255 total, 2 running, 253 sleeping, 0 stopped, 0 zombie
%Cpu(s): 1.3 us, 12.8 sy, 0.0 ni, 85.6 id, 0.0 wa, 0.0 hi, 0.2 si, 0.0 st
MiB Mem : 7747.4 total, 2412.0 free, 1709.3 used, 3626.1 buff/cache
MiB Swap: 2048.0 total, 2047.3 free, 0.7 used. 5596.7 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
98 root -51 0 0 0 0 S 51.3 0.0 171:31.85 irq/9-acpi
24985 root 20 0 0 0 0 R 39.4 0.0 9:03.21 kworker/0:1-kacpi_notify
I have no idea what it is or how to fix it
Re: One CPU core maxed out by a process
Posted: Mon Feb 22, 2021 3:18 pm
by Stevo
Does it persist after a reboot?
Can you run Quick System Info from the menu and just paste it into your next post in this thread?
Sometimes it's easier to just try a newer kernel and see if they fixed it in that...
Re: One CPU core maxed out by a process
Posted: Thu Feb 25, 2021 12:21 pm
by Villano
Stevo wrote: Mon Feb 22, 2021 3:18 pm
Does it persist after a reboot?
Can you run Quick System Info from the menu and just paste it into your next post in this thread?
Sometimes it's easier to just try a newer kernel and see if they fixed it in that...
HI, sorry for the delay!
The problem does persist after reboot, it's constant.
Here's the system info:
Code: Select all
Snapshot created on: 20201203_1342
System: Host: <filter> Kernel: 5.9.1-rt20avl1 x86_64 bits: 64 compiler: N/A
parameters: BOOT_IMAGE=/boot/vmlinuz-5.9.1-rt20avl1
root=UUID=<filter> ro quiet threadirqs noresume
Desktop: KDE Plasma 5.14.5 tk: Qt 5.11.3 wm: kwin_x11 dm: LightDM 1.26.0
Distro: AVL-MXE base: Debian GNU/Linux 10 (buster)
Machine: Type: Laptop System: SAMSUNG product: 700Z7C v: 0.1 serial: <filter> Chassis: type: 9
v: 0.1 serial: <filter>
Mobo: SAMSUNG model: SAMSUNG_NP1234567890 v: FAB1 serial: <filter>
UEFI [Legacy]: Phoenix v: P06AAE date: 02/27/2013
Battery: ID-1: BAT1 charge: 4.0 Wh condition: 50.3/80.2 Wh (63%) volts: 15.1/14.8
model: SAMSUNG Electronics type: Li-ion serial: N/A status: Charging cycles: 1131
CPU: Topology: Quad Core model: Intel Core i7-3615QM bits: 64 type: MT MCP
arch: Ivy Bridge family: 6 model-id: 3A (58) stepping: 9 microcode: 21
L2 cache: 6144 KiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 36716
Speed: 3202 MHz min/max: 1200/3300 MHz Core speeds (MHz): 1: 3202 2: 3203 3: 3120
4: 3158 5: 3106 6: 3129 7: 3130 8: 3148
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW,
STIBP: conditional, RSB filling
Type: srbds status: Vulnerable: No microcode
Type: tsx_async_abort status: Not affected
Graphics: Device-1: Intel 3rd Gen Core processor Graphics vendor: Samsung Co driver: i915
v: kernel bus ID: 00:02.0 chip ID: 8086:0166
Device-2: NVIDIA GK107M [GeForce GT 650M] vendor: Samsung Co driver: N/A
bus ID: 01:00.0 chip ID: 10de:0fd1
Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa
compositor: kwin_x11 resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 4000 (IVB GT2) v: 4.2 Mesa 20.1.8
compat-v: 3.0 direct render: Yes
Audio: Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Samsung Co
driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:1e20
Sound Server: ALSA v: k5.9.1-rt20avl1
Network: Device-1: Intel Centrino Advanced-N 6235 driver: iwlwifi v: kernel port: 3000
bus ID: 02:00.0 chip ID: 8086:088e
IF: wlan0 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Samsung Co
driver: r8169 v: kernel port: 2000 bus ID: 03:00.0 chip ID: 10ec:8168
IF: eth0 state: down mac: <filter>
Drives: Local Storage: total: 473.22 GiB used: 94.08 GiB (19.9%)
ID-1: /dev/sda vendor: Samsung model: SSD 750 EVO 500GB size: 465.76 GiB block size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 1B6Q scheme: MBR
ID-2: /dev/sdb vendor: SanDisk model: SSD i100 8GB size: 7.46 GiB block size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 6.04 scheme: GPT
Partition: ID-1: / raw size: 463.73 GiB size: 455.45 GiB (98.21%) used: 94.08 GiB (20.7%)
fs: ext4 dev: /dev/sda1
ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 10 (default 60)
cache pressure: 100 (default) dev: /dev/sda2
Sensors: System Temperatures: cpu: 86.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos: Active apt repos in: /etc/apt/sources.list
1: deb http://liquorix.net/debian/ sid main
2: deb http://www.bandshed.net/kernels/apt/ buster main
3: deb [trusted=yes] https://cinelerra-gg.org/download/pkgs/debian10/ buster main
4: deb https://dl.winehq.org/wine-builds/debian/ buster main
5: deb https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/Debian_10/ ./
6: deb [arch=amd64] https://download.docker.com/linux/debian/ buster stable
7: deb http://security.debian.org/ buster/updates main
8: deb-src http://security.debian.org/ buster/updates main
No active apt repos in: /etc/apt/sources.list.d/connectify.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian/ buster-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian/ buster main contrib non-free
2: deb http://deb.debian.org/debian-security/ buster/updates main contrib non-free
3: deb-src http://deb.debian.org/debian/ buster main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/kxstudio-debian-ppas.list
1: deb http://ppa.launchpad.net/kxstudio-debian/libs/ubuntu/ bionic main
2: deb http://ppa.launchpad.net/kxstudio-debian/music/ubuntu/ bionic main
3: deb http://ppa.launchpad.net/kxstudio-debian/plugins/ubuntu/ bionic main
4: deb http://ppa.launchpad.net/kxstudio-debian/apps/ubuntu/ bionic main
5: deb http://ppa.launchpad.net/kxstudio-debian/kxstudio/ubuntu/ bionic main
Active apt repos in: /etc/apt/sources.list.d/kxstudio-external.list
1: deb [arch=amd64,i386] https://kx.studio/repo/ stable free
2: deb [arch=amd64,i386] https://kx.studio/repo/ gcc5 free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb https://mirrors.evowise.com/mxlinux-packages/mx/repo/ buster main non-free
Active apt repos in: /etc/apt/sources.list.d/spotify.list
1: deb http://repository.spotify.com/ stable non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 280 Uptime: 10m Memory: 7.57 GiB used: 1.17 GiB (15.5%) Init: SysVinit
v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in
running in: quick-system-in inxi: 3.0.36
Re: One CPU core maxed out by a process
Posted: Thu Feb 25, 2021 12:39 pm
by Adrian
Kernel: 5.9.1-rt20avl1
Does it happen with other kernels (non-rt one?)
Re: One CPU core maxed out by a process
Posted: Thu Feb 25, 2021 1:01 pm
by Villano
Adrian wrote: Thu Feb 25, 2021 12:39 pm
Kernel: 5.9.1-rt20avl1
Does it happen with other kernels (non-rt one?)
Wouldn’t know. I guess that means that I can switch kernels? I’m a total noob, obviously. I’ll see what I can learn online.
Re: One CPU core maxed out by a process
Posted: Thu Feb 25, 2021 1:26 pm
by Adrian
You could install another kernel (also you are running AVL-MXE so this should be probably in the MX Respins subforum
viewforum.php?f=127 or AV Linux forums if they have any since they might know more about that particular kernel)
You can install another kernel from MX Package Installer then at reboot time you can choose to boot into the new or old kernel (so there's no danger from this point of view)
If the new kernel works best you can set it default entry in GRUB with MX Boot Options program.
Re: One CPU core maxed out by a process
Posted: Thu Feb 25, 2021 5:39 pm
by Villano
Adrian wrote: Thu Feb 25, 2021 1:26 pm
You could install another kernel (also you are running AVL-MXE so this should be probably in the MX Respins subforum
viewforum.php?f=127 or AV Linux forums if they have any since they might know more about that particular kernel)
You can install another kernel from MX Package Installer then at reboot time you can choose to boot into the new or old kernel (so there's no danger from this point of view)
If the new kernel works best you can set it default entry in GRUB with MX Boot Options program.
thanks for chiming in! I tried another kernel but it made no difference. I tried installing more kernels but it gives me an error related to winehq. I'll check the Respins forum, thanks!
Re: One CPU core maxed out by a process
Posted: Thu Feb 25, 2021 6:09 pm
by Libernux
There is nothing wrong with this output.
Read the manpage for top eg. 'man top'.
It summarizes the time for all cpus.
Total is always 100 %.
Your cpu is not maxed out.
It is 85.6 % idle.
Hope this will help you in understanding the output of top.
Re: One CPU core maxed out by a process
Posted: Thu Feb 25, 2021 6:24 pm
by Villano
Libernux wrote: Thu Feb 25, 2021 6:09 pm
There is nothing wrong with this output.
Read the manpage for top eg. 'man top'.
It summarizes the time for all cpus.
Total is always 100 %.
Your cpu is not maxed out.
It is 85.6 % idle.
Hope this will help you in understanding the output of top.
ok, I'm reading manpage now, lots to learn... SO are you saying that this numbers are normal? I'm an absolute noob and I thought that having 1 core at 85% but going to 100% meant there was a problem.
EDIT: OK, I get it now, I was reading the whole thing wrong! Thanks a lot for pointing it out, I can relax now
Re: One CPU core maxed out by a process
Posted: Thu Feb 25, 2021 6:44 pm
by Stevo
You're actually using a derivate of MX, AV-Linux, which has its own kernel and forum sections, too. This thread doesn't belong in the standard MX section.