HI LQ,
I have a RHEL 6.4 workstation with a HW RAID 0 drive that is mounted to another 6.4 workstation. I am recieving kernel:do_IRQ: 1.205 No irq handler for vector (irq -1) on the machines with the drive that has the local HW RASID 0 drive. The other machine that has the drive mounted soes not have this error message.

Not sure if this info makes any difference or not, but I did have a hit on Google yesterday about this error and the syncing of a RAID drive.

More simply stated I have a kernel:do_IRQ: 1.205 No irq handler for vector (irq -1) error and do not have a clue what to look at to get rid of it.

All help greatly appreciated!!

Hello,

if you do have RH subscription one of them could help or go ahead and open a case
https://access.redhat.com/site/solutions/110053
https://access.redhat.com/site/solutions/517583

if dont then reinstall to an OS which support is free :P

I updated the bios yesterday after a hit from another forum. So far both machines have not posted the error since then. Thanks for these two solutions. I am hoping the bios update has solved the issue, but if this is not the case, your links will certainly get me to resolution.

Many thanks for your help! Will leave this thread open for the time being and update accordingly.

It's back... I looked at the articles again and I do not see a way to disable Interupt Remapping in the bios and changing the setting in the /boot/grub/grub.cong file would take a bit more expanation for me to do. I have four different kernal boot lines in that file.

On these HP Z800's this is not in the bios at least what i can see of it. Found another article about the chipset istself that mentioned disabling Interupt Remapping for various reasons and detailed instruction of how it is done. Not going to happen in the HP bios. In that same post what was causing the issues dealt with VT-d. I did not find VT-d in the bios but did find VT-d2 and went ahead and disabled this feature.

We'll see what happens. If you're familiar with getting deeper into the HP bios please let me know.
Thanks!

Looks like disabling VT-d2 in the bios was the fix. No errors since then. Will repost if the problem re-surfaces.