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 find
Rob A
On 2019-04-12 11:46 a.m., Kyle Brenneman wrote:
> 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 IRQ errors.
>
--
Chief SW Engineering
Andrews Consulting
Ottawa, ON, CA
+1 613.435.7489 (Office)
+1 613.447.7154 (Cell)
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 find
Rob A
On 2019-04-12 11:46 a.m., Kyle Brenneman wrote:
> 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 IRQ errors.
>
--
Chief SW Engineering
Andrews Consulting
Ottawa, ON, CA
+1 613.435.7489 (Office)
+1 613.447.7154 (Cell)