Boot warnings: "No irq handler for vector …"

2020-10-08 Thread nito
node #0, CPUs:#1 [0.068359] __common_interrupt: 1.55 No irq handler for vector [0.364641] #2 [0.068359] __common_interrupt: 2.55 No irq handler for vector [0.364705] #3 [0.068359] __common_interrupt: 3.55 No irq handler for vector [0.366814] #4 [0.06835

Re: No irq handler for vector

2020-08-28 Thread Johann Klammer
On 08/28/2020 10:10 AM, john doe wrote: > > Will need to check on the power supply, no Rugrats in my home so I'm > safe there!!! :) > I meant the people wot program the kernel. NOBODY is safe from those. >> Might also be some part of the box(GPU?) overheating. >> > > As far as I can tell, smart

Re: No irq handler for vector

2020-08-28 Thread john doe
On 8/28/2020 6:35 AM, Johann Klammer wrote: On 08/27/2020 08:00 PM, john doe wrote: Debians, I just installed Debian Buster and I'm seeing the following messages at boot: "[0.005017] do_IRQ: 1.55 No irq handler for vector [0.005017] do_IRQ: 2.55 No irq handler

Re: No irq handler for vector

2020-08-27 Thread Johann Klammer
On 08/27/2020 08:00 PM, john doe wrote: > Debians, > > I just installed Debian Buster and I'm seeing the following messages at > boot: > > > "[ 0.005017] do_IRQ: 1.55 No irq handler for vector > [0.005017] do_IRQ: 2.55 No irq handler for vector &g

Re: No irq handler for vector

2020-08-27 Thread Sven Joachim
On 2020-08-27 19:14 +0100, Brad Rogers wrote: > On Thu, 27 Aug 2020 19:53:01 +0200 > john doe wrote: > > Hello john, > >>What should I do to correct whatever they are telling me? > > Seems to be being worked on ATM. I don't think that is actually the case, the activity in the archlinux forum not

Re: No irq handler for vector

2020-08-27 Thread Brad Rogers
On Thu, 27 Aug 2020 20:41:01 +0200 john doe wrote: Hello john, >Many thanks for the URLs and the short version! :) To be fair, my eyes started to glaze over, trying to absorb it all. I hope I got the gist of it right. >I appriciated. No problem, Jon. -- Regards _ / ) "

Re: No irq handler for vector

2020-08-27 Thread john doe
On 8/27/2020 8:14 PM, Brad Rogers wrote: On Thu, 27 Aug 2020 19:53:01 +0200 john doe wrote: Hello john, Hi there Brad, What should I do to correct whatever they are telling me? Seems to be being worked on ATM. See https://bbs.archlinux.org/viewtopic.php?id=256227 for some insight. See

Re: No irq handler for vector

2020-08-27 Thread Brad Rogers
On Thu, 27 Aug 2020 19:53:01 +0200 john doe wrote: Hello john, >What should I do to correct whatever they are telling me? Seems to be being worked on ATM. See https://bbs.archlinux.org/viewtopic.php?id=256227 for some insight. See https://unix.stackexchange.com/questions/535199/how-to-deduce-

No irq handler for vector

2020-08-27 Thread john doe
Debians, I just installed Debian Buster and I'm seeing the following messages at boot: "[    0.005017] do_IRQ: 1.55 No irq handler for vector [    0.005017] do_IRQ: 2.55 No irq handler for vector [    0.005017] do_IRQ: 3.55 No irq handler for vector" I don't understand

Re: Buster: do_IRQ: 1.35 No irq handler for vector

2019-03-19 Thread Bruce
Works perfectly! Thank you very much. Bruce On 3/19/19 10:37 AM, Miguel A. Vallejo wrote: I added this line as very first line in /etc/rsyslog.conf :msg, contains, "No irq handler for vector" ~ Basically it means: if message contains "No irq handler for vector" then di

Buster alpha5 -- was Buster: do_IRQ: 1.35 No irq handler for vector

2019-03-19 Thread ghe
On 3/19/19 8:37 AM, Miguel A. Vallejo wrote: > It's only a temporary solution until the progem gets fixed, but at > least it allows you to continue doing your work. I installed Buster alpha5 the other day, and the LTO5 tape drive quit working, intermittently. Troubleshooting a tape drive is *slo

Re: Buster: do_IRQ: 1.35 No irq handler for vector

2019-03-19 Thread Miguel A. Vallejo
I added this line as very first line in /etc/rsyslog.conf :msg, contains, "No irq handler for vector" ~ Basically it means: if message contains "No irq handler for vector" then discard. Once you add the line, restart rsyslog: systemctl restart rsyslog It's only a tem

Re: Buster: do_IRQ: 1.35 No irq handler for vector

2019-03-19 Thread Bruce Halco
ió: I upgraded from Squeeze to Buster last week and have been having a problem with "No irq handler for vector" messages appearing in all the console windows. There were originally 3 different numeric values in the messages. After adding 'pci=nomsi,noaer' to the grub boot optio

Re: Buster: do_IRQ: 1.35 No irq handler for vector

2019-03-18 Thread Miguel A. Vallejo
ended tweaking /etc/rsyslog.conf to get rid of them and continue to work as usual. El lun., 18 mar. 2019 a las 15:47, Bruce () escribió: > > I upgraded from Squeeze to Buster last week and have been having a > problem with "No irq handler for vector" messages appearing in all the >

Buster: do_IRQ: 1.35 No irq handler for vector

2019-03-18 Thread Bruce
I upgraded from Squeeze to Buster last week and have been having a problem with "No irq handler for vector" messages appearing in all the console windows. There were originally 3 different numeric values in the messages. After adding 'pci=nomsi,noaer' to the grub boo

Re: No irq handler for vector

2016-03-20 Thread kamaraju kusumanchi
On Wed, Mar 16, 2016 at 11:35 AM, Henrique de Moraes Holschuh wrote: > On Wed, Mar 16, 2016, at 09:45, The Wanderer wrote: >> In my case, it meant that a microcode update which was/is needed on my >> combination of CPU and motherboard was not being applied. This appeared > > What processor is this

Re: No irq handler for vector

2016-03-19 Thread Henrique de Moraes Holschuh
mapping feature of the IOMMU), so it might have been fixed when you updated that BIOS. And I *think* our 3.14 kernel eventually got the patch that bitches about BIOSes that get this wrong and tries to disable it, but I am not sure about this, so a kernel update can certainly fix it (if that

Re: No irq handler for vector

2016-03-19 Thread The Wanderer
on-the-fly again. > And I *think* our 3.14 kernel eventually got the patch that bitches > about BIOSes that get this wrong and tries to disable it, but I am > not sure about this, so a kernel update can certainly fix it (if > that's indeed the root cause of the "no irq handler for

Re: No irq handler for vector

2016-03-19 Thread Henrique de Moraes Holschuh
On Wed, Mar 16, 2016, at 09:45, The Wanderer wrote: > In my case, it meant that a microcode update which was/is needed on my > combination of CPU and motherboard was not being applied. This appeared What processor is this, please? -- "One disk to rule them all, One disk to find them. One disk

Re: No irq handler for vector

2016-03-19 Thread kamaraju kusumanchi
On Wed, Mar 16, 2016 at 8:45 AM, The Wanderer wrote: > > I had this for months on end, but it stopped happening a month or two > ago. Thanks for all the information. Can you please provide the kernel version where this error does not show up. thanks raju -- Kamaraju S Kusumanchi | http://raju.s

Re: No irq handler for vector

2016-03-19 Thread The Wanderer
On 2016-03-16 at 01:00, kamaraju kusumanchi wrote: >> From time to time, this message is printed on my konsole. > > Message from syslogd@hogwarts at Mar 16 00:12:49 ... > kernel:[1219588.659735] do_IRQ: 1.170 No irq handler for vector (irq -1) > > What does it mean?

Re: No irq handler for vector

2016-03-19 Thread The Wanderer
On 2016-03-16 at 11:35, Henrique de Moraes Holschuh wrote: > On Wed, Mar 16, 2016, at 09:45, The Wanderer wrote: > >> In my case, it meant that a microcode update which was/is needed on >> my combination of CPU and motherboard was not being applied. This >> appeared > > What processor is this, p

Re: No irq handler for vector

2016-03-19 Thread The Wanderer
On 2016-03-16 at 23:30, kamaraju kusumanchi wrote: > On Wed, Mar 16, 2016 at 8:45 AM, The Wanderer > wrote: > >> I had this for months on end, but it stopped happening a month or >> two ago. > > Thanks for all the information. Can you please provide the kernel > version where this error does n

No irq handler for vector

2016-03-15 Thread kamaraju kusumanchi
>From time to time, this message is printed on my konsole. Message from syslogd@hogwarts at Mar 16 00:12:49 ... kernel:[1219588.659735] do_IRQ: 1.170 No irq handler for vector (irq -1) What does it mean? How I can rectify the problem? Is something wrong with my hardware or is any component