I have an APC UPS too. Great find. Who would have guessed an IRQ handling
problem message from the kernel was due to a serial or USB device. Wow.
On Thu, Apr 18, 2019 at 7:16 AM Kai-Heng Feng
wrote:
> Thanks for the info. Have anyone filed a bug against upstream apcupsd?
>
> --
> You received
Thanks for the info. Have anyone filed a bug against upstream apcupsd?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1781016
Title:
Slow flood of do_IRQ: No irq for vector
Status in
+1 Kyle, configuring apcupsd properly solved the problem for me too.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1781016
Title:
Slow flood of do_IRQ: No irq for vector
Status in
Confirmed on my system as well. . .
Even though /etc/default/apcupsd ISCONFIGURED=no I was getting the
do_IRQ: 6.34 No irq handler for vector message continuously.
After commenting out the "DEVICE /dev/ttyS0" and restarting the apcupsd
service the no irq error has stopped.
Thankyou for this
Kyle - excellent find, I have confirmed that this was the cause of my
issue, too. Thank you!
I had taken a quick glance at /etc/apcupsd/apcupsd.conf when I was
failing to see communication working with my UPS, as I saw the expected
lines to configure apcupsd for USB mode I had assumed there was a
On my system, I found that the immediate cause of those messages was
running apcupsd, with the default configuration of trying to talk over a
serial cable, but without a UPS connected to it. Even if it was
otherwise configured for USB, I also had to remove the "DEVICE
/dev/ttyS0" line to fix the
HP Z820 Workstation machine
HP 158B motherboard
4.15.0-47-generic kernel
same error
...
[ 821.269834] do_IRQ: 4.38 No irq handler for vector
[ 823.270705] do_IRQ: 4.38 No irq handler for vector
[ 824.271303] do_IRQ: 4.38 No irq handler for vector
[ 826.272120] do_IRQ: 4.38 No irq handler for
A,
The default kernel doesn't enable IRQ debugfs so there's no
"/sys/kernel/debug/irq".
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1781016
Title:
Slow flood of do_IRQ: No irq for
Running an Intel S2600ST motherboard with dual Gold 6148 I get this
error regularly after the last kernel update I did.
The number before the dot seems to be a CPU number since I see many varied
numbers and there's 40 cores/80 threads on my motherboard
e.g.
[Wed Dec 26 14:20:25 2018] do_IRQ:
TJ,
I think Target is the CPU#, not a device identity.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1781016
Title:
Slow flood of do_IRQ: No irq for vector
Status in linux package in
daftykins:
Your issue is there is no handler so you won't find anything in
debug/irg for it:
[ 167.279809] do_IRQ: 1.35 No irq handler for vector
HOWEVER, you should be able to find which target device is responsible
by searching for matching Target: value, e.g. something like:
$ grep -l
Many thanks, I have given this a try today but unfortunately can't
locate the specific Target & Vector combination. Here's what I saw:
$ uname -r
4.20.0-1-generic
$ dmesg | tail
[ 167.279809] do_IRQ: 1.35 No irq handler for vector
# grep 35 /sys/kernel/debug/irq/irqs/*
Please install and boot kernel [1] which enables IRQ debugfs.
Then you can find the "do_IRQ: X.Y" means. On my system:
# ls /sys/kernel/debug/irq/irqs
0 1 10 11 12 120 121 122 123 124 125 126 127 128 129 13 130
131 132 133 14 15 16 17 18 19 2 3 4 5 51 6 67 7 8
I am also affected by this issue, however on a wholly different platform
- an intel H370 based motherboard with a Core i3-8100 CPU. It was
suggested that I attempt to supress logging output via a sysrq keyboard
combo, so I pressed alt+sysrq+0 but this appears to be disabled by
default as I saw the
Mine is a desktop, and no suspend occurs, ever. Are you (Kai-Heng Feng)
asking me to suspend it and wake it up and see if it goes away?
On Mon, Sep 24, 2018 at 10:45 AM Kai-Heng Feng
wrote:
> Do you see this after S3?
>
> --
> You received this bug notification because you are subscribed to the
Do you see this after S3?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1781016
Title:
Slow flood of do_IRQ: No irq for vector
Status in linux package in Ubuntu:
Incomplete
Bug
I'd also like to mention that my system was a clean 18.04 install.
Also, would it be beneficial if I added my system info somehow? If so,
is there a way to add the same type of info Doug added without
generating a whole new bug report with say "ubuntu-bug linux"??
--
You received this bug
Ubuntu does not appear to be the only one with this issue on the 4.15 kernel:
https://bugzilla.redhat.com/show_bug.cgi?id=1551605
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1781016
Same here. Not sure when this started:
~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04 LTS
Release:18.04
Codename: bionic
~$ uname -a
Linux w00t 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17 15:39:52 UTC 2018 x86_64
x86_64 x86_64
Still happening:
doug@doug-dt:~$ uname -a
Linux doug-dt 4.18.0-041800rc5-generic #201807152130 SMP Sun Jul 15 21:32:10
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
doug@doug-dt:~$ dmesg | tail
[ 169.701341] usb 1-4: Warning! Unlikely big volume range (=4096), cval->res
is probably wrong.
[
Exactly. It never happened in ubuntu 17.10. Started happening after
installing ubuntu 18.04. Can't say I know exactly what kernel version
17.10 was up to, sorry. It was the standard one, whatever dist-upgrade
would have gave me.
I'll try the kernel version you proposed and update this bug after I
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18
22 matches
Mail list logo
