Created attachment 1749967 [details] dmesg 1. Please describe the problem: On every system boot or wake up or power plug-in/out the system prints the following message Message from syslogd@precision at Jan 22 20:01:21 ... kernel:__common_interrupt: 5.33 No irq handler for vector Message from syslogd@precision at Jan 22 21:45:04 ... kernel:__common_interrupt: 5.33 No irq handler for vector Message from syslogd@precision at Jan 22 22:20:27 ... kernel:__common_interrupt: 5.33 No irq handler for vector Message from syslogd@precision at Jan 23 00:52:04 ... kernel:__common_interrupt: 5.33 No irq handler for vector Message from syslogd@precision at Jan 23 06:27:35 ... kernel:__common_interrupt: 5.33 No irq handler for vector Message from syslogd@precision at Jan 23 06:27:35 ... kernel:__common_interrupt: 5.33 No irq handler for vector 2. What is the Version-Release number of the kernel: Operating System: Fedora 33 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.7-200.fc33.x86_64 OS Type: 64-bit Processors: 8 × Intel® Core™ i7-6820HQ CPU @ 2.70GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 530 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : The problem started after I upgraded the BIOS version to 1.15.0 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: It happens consistently on boot, wake up, power connection in and out. 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: 6. Are you running any modules that not shipped with directly Fedora's kernel?: Possibly nvidia 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag. Please also see a previous bug https://bugzilla.redhat.com/show_bug.cgi?id=1551605
This is not Intel-specific. I see the same warnings on boot with an AMD Ryzen 3950X on a Gigabyte Aorus Ultra X570 motherboard.
Also occurs on my Lenovo ThinkPad E585, BIOS v. 1.58, AMD Ryzen 7 2700U with Radeon Vega Mobile Gfx, running Fedora Workstation 33. Happens at every boot.
I've been seeing these on boot since 2020/06/29 after updating bios. (rev 2206) Still seeing it on rev 3204 (released 2021/01/29, only note was "Update AMD AM4 AGESA V2 PI 1.2.0.0") Ryzen 3950X, X570 - (Motherboard: Asus ROG Crosshair VIII Formula) Kernel log: (journalctl --no-hostname -k -b) https://pastebin.com/rsJj1Y9X
I get this every time I boot since first installation of fedora 34 on a new machine (~May/June 2021) Appears at line 282 of the bootlog: https://pastebin.com/68E9QAyA Output of 'uname -srv': (kernel name release version) Linux 5.12.13-300.fc34.x86_64 #1 SMP Wed Jun 23 16:18:11 UTC 2021 Output of 'sudo lshw -c bus': (motherboard info) *-core description: Motherboard product: LNVNB161216 vendor: LENOVO physical id: 0 version: SDK0J40697 WIN Processor is AMD Ryzen 5 4500U with Radeon graphics
Same, I upgraded my PC to an ASUS TUF GAMING B550-PLUS motherboard and an AMD Ryzen 9 5900X CPU and now I'm getting these errors every boot. kernel-5.13.4-200.fc34.x86_64 kernel: __common_interrupt: 1.55 No irq handler for vector kernel: __common_interrupt: 2.55 No irq handler for vector kernel: __common_interrupt: 3.55 No irq handler for vector kernel: __common_interrupt: 4.55 No irq handler for vector kernel: __common_interrupt: 5.55 No irq handler for vector kernel: __common_interrupt: 6.55 No irq handler for vector kernel: __common_interrupt: 7.55 No irq handler for vector kernel: __common_interrupt: 8.55 No irq handler for vector kernel: __common_interrupt: 9.55 No irq handler for vector kernel: __common_interrupt: 10.55 No irq handler for vector
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.