Hundreds of Unreportable Errors a minute on Problem Reporting Tool

Ask Fedora
1 
BOOT_IMAGE=(hd0,gpt5)/vmlinuz-5.5.5-200.fc31.x86_64 root=/dev/mapper/fedora-root ro resume=/dev/mapper/fedora-swap rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap rhgb quiet

what’s more perplexing is that I’m getting the error from two different versions of the kernel simultaneously.

I am getting alternating versions of

irq 31: nobody cared (try booting with the "irqpoll" option)
CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.5.5-200.fc31.x86_64 #1
Hardware name: LENOVO 20QDA005KR/20QDA005KR, BIOS N2HET21W (1.04 ) 06/03/2019
Call Trace:

irq 31: nobody cared (try booting with the "irqpoll" option)
CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.4.18-200.fc31.x86_64 #1
Hardware name: LENOVO 20QDA005KR/20QDA005KR, BIOS N2HET21W (1.04 ) 06/03/2019
Call Trace:

813ab642e08d34c478a30a29103de0dc39009e15.png
813ab642e08d34c478a30a29103de0dc39009e15.png3840×2106 334 KB

2

Check for firmware updates for starters. UEFI systems have more frequent updates (more bugs to fix) than BIOS systems did. It may not fix this problem but it’s a start. Maybe it’s related to this:
https://bugzilla.kernel.org/show_bug.cgi?id=204121

However, you have a legit complaint in that there’s no sense in constantly reporting this problem over and over. Once is enough. You could file a bug against abrt component. Attach dmesg/journal and a screenshot of all the abrt complaints.

2 Likes