0

On Fedora, the lspci command keeps staying at ~100% while I'm not doing anything with my computer. I've done a clean install last week and before that I also had this problem.

Top output gives me:

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND     
10283 tim       20   0   19384   1436   1312 R 100.0  0.0  14:34.63 lspci       
 1752 tim       20   0  624948 144552 109544 S   8.0  1.8   3:49.61 Xorg        
11197 tim       20   0  612712  48612  36336 S   2.0  0.6   0:18.19 gnome-syst+ 
·
·

and if I check system monitor, i see that only 1 cpu running at ~100%.

CPU Usage

Besides, if I try to run the command 'lspci' it just keeps loading and not showing anything.

Some info about my system:

Fedora 27 (up-to-date)
Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz
Core(s) per socket:  4
RAM memory: 8G
  • Is this a laptop? – msp9011 Jul 25 '18 at 13:39
  • Do a system update, this is a known lspci bug that is already fixed. (...) – Rui F Ribeiro Jul 25 '18 at 16:42
  • Thank you for the response. Yes it is a laptop. I've done a dnf --refresh upgrade, and I was up to date already. – Jasper Jul 25 '18 at 17:59
1

You have to figure which process invokes lspci. Replace lspci binary with script. Rename it to lspci.bin (issue commands below as root user):

mv /usr/bin/lspci /usr/bin/lspci.bin

Create script:

touch /usr/bin/lspci

Make it executable:

chmod +x /usr/bin/lspci

Open created script with your favorite text editor (let it be nano for instance)

nano /usr/bin/lspci

and copy/paste the following code:

#!/bin/sh
echo lspci "$@" >> /var/log/lspci.log
date >> /var/log/lspci.log
pstree >> /var/log/lspci.log
exec lspci.bin "$@"

Reboot computer, check if the lspci CPU overload problem exists, open the log file /var/log/lspci.log and try to explain whats happened. If you can't find a reason of the problem, post the content of the log and ask for additional support.

If the problem has gone away, revert back everything:

rm -f /usr/bin/lspci
mv /usr/bin/lspci.bin /usr/bin/lspci
rm -f /var/log/lspci.log
reboot
  • Thank you for your response. I tried you method and it did disappear. Also the command lspci works again. – Jasper Jul 25 '18 at 18:05
  • @Jasper Could you post your lspci.log? – Bob Jul 25 '18 at 20:42

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.