Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #206314 > unrolled thread

Buster: do_IRQ: 1.35 No irq handler for vector

Started byBruce <debian@halcomp.com>
First post2019-03-18 15:50 +0100
Last post2019-03-19 20:20 +0100
Articles 6 — 4 participants

Back to article view | Back to linux.debian.user

Contents

  Buster: do_IRQ: 1.35 No irq handler for vector Bruce <debian@halcomp.com> - 2019-03-18 15:50 +0100
    Re: Buster: do_IRQ: 1.35 No irq handler for vector "Miguel A. Vallejo" <ea4eoz@gmail.com> - 2019-03-18 16:10 +0100
      Re: Buster: do_IRQ: 1.35 No irq handler for vector Bruce Halco <bruce@halcomp.com> - 2019-03-19 13:40 +0100
        Re: Buster: do_IRQ: 1.35 No irq handler for vector "Miguel A. Vallejo" <ea4eoz@gmail.com> - 2019-03-19 15:40 +0100
          Buster alpha5 -- was Buster: do_IRQ: 1.35 No irq handler for vector ghe <ghe@slsware.net> - 2019-03-19 19:10 +0100
          Re: Buster: do_IRQ: 1.35 No irq handler for vector Bruce <debian@halcomp.com> - 2019-03-19 20:20 +0100

#206314 — Buster: do_IRQ: 1.35 No irq handler for vector

FromBruce <debian@halcomp.com>
Date2019-03-18 15:50 +0100
SubjectBuster: do_IRQ: 1.35 No irq handler for vector
Message-ID<xD1Kp-2FE-7@gated-at.bofh.it>
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 options, 2 of them stopped.

I still get this more than 100 times per day.:

     Message from syslogd@penguin at Mar 18 10:11:08 ...
          kernel:[161132.371343] do_IRQ: 1.35 No irq handler for vector

The time between messages can be as little as 9 seconds, or more than 2 
hours. The messages happen throughout the day, whether I'm at the 
computer or not.

I've tried 'dmesg -n 2', 'dmesg -n 1', and even 'dmesg -D'. The messages 
keep coming. I especially don't understand how 'dmesg -D' doesn't help, 
as it's documented purpose is to 'Disable the printing of messages to 
the console'.

The messages don't correlate to any other events I can find in the log 
files.

On a long shot, I disconnected the optical drives, unplugged the UPS 
from the USB port, and removed the TV capture card. None of that made a 
difference.

Other than the messages, the system is running fine.

The system includes a Phemon II CPU and 16 GB RAM in a Gigabyte 
890GPA-UD3H motherboard.

Any suggestions?

Bruce

[toc] | [next] | [standalone]

#206316

From"Miguel A. Vallejo" <ea4eoz@gmail.com>
Date2019-03-18 16:10 +0100
Message-ID<xD23M-32V-3@gated-at.bofh.it>
In reply to#206314
Same problem here.

For me the messages appear *only* when I start the Arduino IDE and
stops as soon as I close it. I suspect is something related to the
pool of serial ports the Arduino IDE do to detect the plug of a new
Arduino board.

Adding pci=nomsi,noaer didn't work for me so I 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 (<debian@halcomp.com>) 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
> console windows.
>
> There were originally 3 different numeric values in the messages. After
> adding 'pci=nomsi,noaer' to the grub boot options, 2 of them stopped.
>
> I still get this more than 100 times per day.:
>
>      Message from syslogd@penguin at Mar 18 10:11:08 ...
>           kernel:[161132.371343] do_IRQ: 1.35 No irq handler for vector
>
> The time between messages can be as little as 9 seconds, or more than 2
> hours. The messages happen throughout the day, whether I'm at the
> computer or not.
>
> I've tried 'dmesg -n 2', 'dmesg -n 1', and even 'dmesg -D'. The messages
> keep coming. I especially don't understand how 'dmesg -D' doesn't help,
> as it's documented purpose is to 'Disable the printing of messages to
> the console'.
>
> The messages don't correlate to any other events I can find in the log
> files.
>
> On a long shot, I disconnected the optical drives, unplugged the UPS
> from the USB port, and removed the TV capture card. None of that made a
> difference.
>
> Other than the messages, the system is running fine.
>
> The system includes a Phemon II CPU and 16 GB RAM in a Gigabyte
> 890GPA-UD3H motherboard.
>
> Any suggestions?
>
> Bruce
>

[toc] | [prev] | [next] | [standalone]

#206363

FromBruce Halco <bruce@halcomp.com>
Date2019-03-19 13:40 +0100
Message-ID<xDmc9-7nw-7@gated-at.bofh.it>
In reply to#206316
Can you share what changes you made to rsyslog.conf? That's not 
something I've ever messed with.

Thanks.

Bruce

On 3/18/19 11:07 AM, Miguel A. Vallejo wrote:
> Same problem here.
>
> For me the messages appear *only* when I start the Arduino IDE and
> stops as soon as I close it. I suspect is something related to the
> pool of serial ports the Arduino IDE do to detect the plug of a new
> Arduino board.
>
> Adding pci=nomsi,noaer didn't work for me so I 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 (<debian@halcomp.com>) 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
>> console windows.
>>
>> There were originally 3 different numeric values in the messages. After
>> adding 'pci=nomsi,noaer' to the grub boot options, 2 of them stopped.
>>
>> I still get this more than 100 times per day.:
>>
>>       Message from syslogd@penguin at Mar 18 10:11:08 ...
>>            kernel:[161132.371343] do_IRQ: 1.35 No irq handler for vector
>>
>> The time between messages can be as little as 9 seconds, or more than 2
>> hours. The messages happen throughout the day, whether I'm at the
>> computer or not.
>>
>> I've tried 'dmesg -n 2', 'dmesg -n 1', and even 'dmesg -D'. The messages
>> keep coming. I especially don't understand how 'dmesg -D' doesn't help,
>> as it's documented purpose is to 'Disable the printing of messages to
>> the console'.
>>
>> The messages don't correlate to any other events I can find in the log
>> files.
>>
>> On a long shot, I disconnected the optical drives, unplugged the UPS
>> from the USB port, and removed the TV capture card. None of that made a
>> difference.
>>
>> Other than the messages, the system is running fine.
>>
>> The system includes a Phemon II CPU and 16 GB RAM in a Gigabyte
>> 890GPA-UD3H motherboard.
>>
>> Any suggestions?
>>
>> Bruce
>>

[toc] | [prev] | [next] | [standalone]

#206370

From"Miguel A. Vallejo" <ea4eoz@gmail.com>
Date2019-03-19 15:40 +0100
Message-ID<xDo4h-7y-1@gated-at.bofh.it>
In reply to#206363
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 temporary solution until the progem gets fixed, but at
least it allows you to continue doing your work.

Hope this helps.



Bruce Halco (<bruce@halcomp.com>) wrote:
>
> Can you share what changes you made to rsyslog.conf? That's not
> something I've ever messed with.
>
> Thanks.
>
> Bruce

[toc] | [prev] | [next] | [standalone]

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

Fromghe <ghe@slsware.net>
Date2019-03-19 19:10 +0100
SubjectBuster alpha5 -- was Buster: do_IRQ: 1.35 No irq handler for vector
Message-ID<xDrlx-2kr-23@gated-at.bofh.it>
In reply to#206370
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 *slow*. It took 3 or 4 days of man
pages, docs, surfing, rebooting, and some luck to discover that amanda
wants a 32768 block size and tar wants 512. Settable with mt-st, when
there's a tape in the drive.

What is going on with the Debian management? Debian's always been solid
as a rock (stable has, anyway). That tape config, the UUIDs, the s.*d
word, etc. They're buggy and/or badly thought out -- their interfaces to
us mortals are terrible.

-- 
Glenn English

[toc] | [prev] | [next] | [standalone]

#206373

FromBruce <debian@halcomp.com>
Date2019-03-19 20:20 +0100
Message-ID<xDsrf-2Z4-1@gated-at.bofh.it>
In reply to#206370
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 discard.
>
> Once you add the line, restart rsyslog: systemctl restart rsyslog
>
> It's only a temporary solution until the progem gets fixed, but at
> least it allows you to continue doing your work.
>
> Hope this helps.
>
>
>
> Bruce Halco (<bruce@halcomp.com>) wrote:
>> Can you share what changes you made to rsyslog.conf? That's not
>> something I've ever messed with.
>>
>> Thanks.
>>
>> Bruce

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web