[SOLVED] Error msg in terminal: "No irq handler for vector"

[robgeek]

Hi, guys. A few years ago i got this problem, and i never solved. After a while, i gave up and learned to live with it. Now, i ask your help to try to solve it again.
I have an old computer a Pentium4 3Ghz, 2Gb Ram, 256Mb Nvidia7300Gt.
Yesterday, i installed Debian Wheezy and this problem keeps popping up.
I just can not use the terminal command, as the following error message appears repeatedly! Actually, i can use the terminal command, but with this error message appearing all time, which is very annoying! Each time this message appears on the terminal, the alarm of the motherboard beeps. I solved this problem by disabling the alarm.

Message from syslogd@robgeek at Jul 19 19:51:15 ...
kernel:[ 680.082048] do_IRQ: 0.107 No irq handler for vector (irq -1)

or

Message from syslogd@robgeek at Jul 19 19:52:04 ...
kernel:[ 729.014072] do_IRQ: 0.107 No irq handler for vector (irq -1)

or

Message from syslogd@robgeek at Jul 19 19:53:19 ...
kernel:[ 804.182872] do_IRQ: 0.107 No irq handler for vector (irq -1)

or

Same message, but "...kernel:[ this number changes ] do_IRQ: ...

With older versions of Debian and the kernel, the message also appears, and is always the same. It appears more frequently when not install the video driver. Once it is installed, the message keeps popping up, but at a lower frequency. How can i prevent it from appearing? Or how can i solve the problem? With others distros the same thing happens.

[bw123]

the only time i have been bugged like that was when a usb header on the motherboard was failing because of heat. i'd look at hardware mis-seated or overheating, cracks, burns on the motherboard. if there's a bios setting for "assign irq for vga" maybe try turning that off?

[robgeek]

the only time i have been bugged like that was when a usb header on the motherboard was failing because of heat. i'd look at hardware mis-seated or overheating, cracks, burns on the motherboard. if there's a bios setting for "assign irq for vga" maybe try turning that off?

Did not work! Here my advanced options in BIOS:

Advanced
PCIPnP
Plug & Play O/S' [No]
Resources Controlled By [AUTO]
*IRQ Resources "nothing here, and the color of this option is gray."
Assign IRQ For VGA [DISABLED] "Like you said to do."

** PCI Express relative itens **
Maximum Payload Size [409 6]

Assign IRQ For VGA now is enabled because disabled did not work.

[robgeek]

Guys. In bios, Advanced -> PCIPnP -> Resources Controlled By [AUTO], if i set him to MANUAL, the option " * IRQ Resources" becomes avaliable. In this option i have the following options:

IRQ - 3 assigned to [PCI DEVICE] "reserved is the other option"
IRQ - 4 assigned to [PCI DEVICE] "reserved is the other option"
IRQ - 5 assigned to [PCI DEVICE] "reserved is the other option"
IRQ - 7 assigned to [PCI DEVICE] "reserved is the other option"
IRQ - 9 assigned to [PCI DEVICE] "reserved is the other option"
IRQ - 10 assigned to [PCI DEVICE] "reserved is the other option"
IRQ - 11 assigned to [PCI DEVICE] "reserved is the other option"
IRQ - 14 assigned to [PCI DEVICE] "reserved is the other option"
IRQ - 15 assigned to [PCI DEVICE] "reserved is the other option"

There is something to do here to solve my problem?

[cynwulf]

No need to mess with BIOS settings. I searched duckduckgo for "No irq handler for vector (irq -1)" and came up with a few useful results...

Have a look here: http://lime-technology.com/forum/index.php?topic=5005.0

[robgeek]

cynwulf.

It seems to me that i have to add "pci=nomsi,noaer" into the boot code, but where is "syslinux.cfg" file?
How can i do that?

[robgeek]

Guys, please! I really nedd to know how edit syslinux.cfg file.
Here is a possible fix to my problem.

Well, according to this it's an issue with some VIA chipsets
I was able to get rid of that messages including this param. into the boot code:

pci=nomsi,noaer

Now, my syslinux.cfg file looks like this:

root@Tower:/boot# cat syslinux.cfg
default menu.c32
menu title Lime Technology LLC
prompt 0
timeout 50
label unRAID OS
menu default
kernel bzimage
append initrd=bzroot pci=nomsi,noaer
label Memtest86+
kernel memtest
root@Tower:/boot#

So, i would like to edit my boot code or... i don't know!

[cynwulf]

Boot the system, edit the grub kernel line and add those options to the end and boot... If it works you'll need to edit the grub config to make the changes permanent. I don't use grub, so no idea beyond that. If you search the forums, adding grub boot options has been covered a lot.

[robgeek]

Boot the system, edit the grub kernel line and add those options to the end and boot... If it works you'll need to edit the grub config to make the changes permanent. I don't use grub, so no idea beyond that. If you search the forums, adding grub boot options has been covered a lot.

Dude!
Don't even know where to start, but thanks.

[Randicus]

As an experiment, I entered "adding grub boot options" in the forum's search window. Some of the results looked promising, such as the fifth one on the list.
http://forums.debian.net/viewtopic.php? ... ns#p491551

[robgeek]

Guys. Could you, please, tell me another forum that i can get fix this problem?
Or if i create a new post in "Installation"? What do you think?

[cynwulf]

You don't need to worry about syslinux...

Just boot the system, when the grub menu appears hit the letter 'e' to edit the line

Move the cursor to the end of the line (usually after "ro") and type the options "pci=nomsi,noaer", without the quotes, there.

Then do CTRL+x to boot from that kernel. If that does the trick you can look into doing a permanent edit to the grub configuration.

[fsmithred]

The permanent edit that cynwulf mentioned goes in /etc/default/grub. Put it between the quote marks in the line that says

Code: Select all

GRUB_CMDLINE_LINUX=""

And then run 'update-grub'

[robgeek]

Guys. Problem fixed! Thank you very, very much!
After 3 years with this annoying problem finally he wont piss me off again.

I oppened /etc/default/grub and i added ( pci=nomsi,noaer ) between the quote marks in GRUB_CMDLINE_LINUX="" line.

Like this:

GRUB_CMDLINE_LINUX="pci=nomsi,noaer"

And finally, in terminal: update-grub

Well, actually i have no idea what i did, but it worked.

[Tom Booth]

"pci=nomsi,noaer" ?

Isn't that kind of like disconnecting the "Check Engine" light. noaer - translation: No advanced error reporting.

Anyway, I get the same, or similar "No IRQ handler for vector" error every time I boot up ANY Linux distro. I'm using Easy2Boot mutiboot from USBs.

There is a pause at this error, often for quite a long time, then the boot will eventually continue successfully. It is only slightly annoying. Mostly I was just wondering what might be causing it and if there might be some cure, Just to speed up boot time if nothing else, it seems to cause a substantial delay.

[andrea77]

I solved changing "XHCI Mode" in BIOS: from "Windows 10" to "Windows 7"