No irq handler for vector

[Charlie68]

Greetings to all, it is a long time that I fight to no longer view this message when starting any Linux distribution, the message is "No irq handler for vector" repeated three times.
It should be noted that this happens on a notebook acer aspire E1 - 522 with Amd Quad-Core E2-3800 processor with integrated graphics Amd Radeon HD 8280, the system works well, no problem, the only problem are these damn messages at startup. Right now my notebook has installed openSUSE Tumblewwed and as mentioned everything works very well. I will post the interested part of dmesg :
[ 0.000000] ACPI: Core revision 20180531
[ 0.000000] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 13
3484873504 ns
[ 0.000000] hpet clockevent registered
[ 0.000000] APIC: Switch to symmetric I/O mode setup
[ 0.000000] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.020000] tsc: Fast TSC calibration using PIT
[ 0.024000] tsc: Detected 1297.591 MHz processor
[ 0.024000] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x12b43a4fa15,
max_idle_ns: 440795209028 ns
[ 0.024000] Calibrating delay loop (skipped), value calculated using timer frequency..
2595.18 BogoMIPS (lpj=5190364)
[ 0.024000] pid_max: default: 32768 minimum: 301
[ 0.028175] Security Framework initialized
[ 0.028241] AppArmor: AppArmor initialized
[ 0.032624] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
[ 0.034363] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
[ 0.034493] Mount-cache hash table entries: 16384 (order: 5, 131072 bytes)
[ 0.034556] Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes)
[ 0.035132] mce: CPU supports 6 MCE banks
[ 0.035152] Last level iTLB entries: 4KB 512, 2MB 8, 4MB 4
[ 0.035155] Last level dTLB entries: 4KB 512, 2MB 256, 4MB 128, 1GB 0
[ 0.035160] Spectre V2 : Mitigation: Full AMD retpoline
[ 0.035162] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context swi
tch
[ 0.035166] Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via
prctl and seccomp
[ 0.035446] Freeing SMP alternatives memory: 32K
[ 0.048000] smpboot: CPU0: AMD E2-3800 APU with Radeon(TM) HD Graphics (family: 0x16, m
odel: 0x0, stepping: 0x1)
[ 0.068065] Performance Events: AMD PMU driver.
[ 0.068080] ... version: 0
[ 0.068082] ... bit width: 48
[ 0.068083] ... generic registers: 4
[ 0.068086] ... value mask: 0000ffffffffffff
[ 0.068087] ... max period: 00007fffffffffff
[ 0.068089] ... fixed-purpose events: 0
[ 0.068091] ... event mask: 000000000000000f
[ 0.076037] Hierarchical SRCU implementation.
[ 0.092263] NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.
[ 0.100035] smp: Bringing up secondary CPUs ...
[ 0.140150] x86: Booting SMP configuration:
[ 0.140155] .... node #0, CPUs: #1
[ 0.004000] do_IRQ: 1.55 No irq handler for vector
[ 0.184144] #2
[ 0.004000] do_IRQ: 2.55 No irq handler for vector
[ 0.228149] #3
[ 0.004000] do_IRQ: 3.55 No irq handler for vector
[ 0.231739] smp: Brought up 1 node, 4 CPUs
[ 0.231739] smpboot: Max logical packages: 1
[ 0.231739] smpboot: Total of 4 processors activated (10380.72 BogoMIPS)
[ 0.236049] node 0 initialised, 1111742 pages in 4ms
[ 0.237003] devtmpfs: initialized
[ 0.237003] x86/mm: Memory block size: 128MB
[ 0.240079] PM: Registering ACPI NVS region [mem 0x0006e000-0x0006ffff] (8192 bytes)
[ 0.240084] PM: Registering ACPI NVS region [mem 0xbf97f000-0xbfb7efff] (2097152 bytes)
[ 0.240406] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:
7645041785100000 ns
Thank you

[Charlie68]

Thanks, so we hope it will be solved with the 4.19 kernel, I'm waiting for the update that will come soon. I thought it was a problem related to Amd drivers, so I posted here, but I was wrong. Thanks a lot.

[Charlie68]

I did a bit of research on this problem and I found several open bugs and it seems that the 4.18 kernel does not solve the problem.
I'm not sure that this bug has nothing to do with Amd, all the open bugs I've read (all recent) have Amd graphics.
For example this https://bugs.debian.org/cgi-bin/bugr...cgi?bug=912085 or https://bugs.launchpad.net/ubuntu/+s...x/+bug/1781016 or https://www.mail-archive.com/search?...2&o=newest&f=1

[Charlie68]

Yes, the problem is just these stupid message at startup that would not be a problem for me, but when I install it to some of my friends, these messages are a problem despite my attempt to reassure them that they are harmless.
Possible that there is not a way to hide them? Can we go to Mars and we can not hide these messages?

[pqwoerituytrueiwoq]

I recently noticed this annoying message on my install of xubuntu 18.04 linux 4.15/4.18 and after around 2 hours messing with stuff i noticed finally tracking down how to make it STFU, in my BIOS i have a Super I/O section that contains a PS/2 Y cable option and a serial port function, with the serial port option disabled the message is gone, page 122 of this my manual: ftp://asrock.cn/Manual/Fatal1ty%20Z9...ofessional.pdf

i have 2 main profiles saved, one is for my daily overclock and one is my non overlcocked settings, this message only appeared on my OC profile but turning off all OC stuff did not remove it after going through every difference using a cell phone camera to compare settings 1 page at a time when i found this difference that triggers the issue

[Charlie68]

It is also possible to compile the kernel for your hardware regardless of the distribution in use. But I was only asking if there is a way to hide those messages.

[Charlie68]

I recently noticed this annoying message on my install of xubuntu 18.04 linux 4.15/4.18 and after around 2 hours messing with stuff i noticed finally tracking down how to make it STFU, in my BIOS i have a Super I/O section that contains a PS/2 Y cable option and a serial port function, with the serial port option disabled the message is gone, page 122 of this my manual: ftp://asrock.cn/Manual/Fatal1ty%20Z9...ofessional.pdf

i have 2 main profiles saved, one is for my daily overclock and one is my non overlcocked settings, this message only appeared on my OC profile but turning off all OC stuff did not remove it after going through every difference using a cell phone camera to compare settings 1 page at a time when i found this difference that triggers the issue

Thanks, unfortunately, my bios is very minimal and I have no rumors about it.

[Charlie68]

I think it's too difficult for me, anyway I thank you.

[Charlie68]

You would benefit a lot of a custom non debug 1000Hz timer kernel. Booting is many seconds faster even with an ssd and programs runs faster. Debian based distributions are easier, faster and lighter than tumbleweed.

https://distrowatch.com/weekly.php?issue=20181210#opensuse

On the negative side, a number of things didn't work during my time with the distribution. Media support was broken, the Discover software manager had a number of issues and some configuration modules caused me headaches. These rough edges sometimes get fixed, but may be traded out for other problems since the operating system is ever in flux.

In the long term, a bigger issue may be the amount of network bandwidth and disk space Tumbleweed consumes. Just to keep up with updates we need set aside around 1GB of downloads per month and (when Btrfs snapshots are used) even more disk space. In a few weeks Tumbleweed consumed more disk space with far fewer programs installed as my installation of MX Linux.

I understand, however they are only messages, the system works very well and does not change distribution due to these messages. I feel very comfortable with Tumbleweed and with openSUSE in general (I also use Leap 15) so I do not change distribution, also because Tumbleweed on my PC works great and gives me the possibility to have the last packages when they pass the tests, moreover Yast is spectacular! So I will never go to Debian for this reason. A greeting.

[Charlie68]

Sorry, but if you like Debian use Debian, nobody tells you to change, I prefer Tumbleweed and use tumbleweed. I do not like Debian, I do not like package management, I've always had problems with Debian and Debian based, but I do not want to convince you, I do not care, but please avoid convincing me of the contrary!