Experimental Physics and
Industrial Control System

Hello,

Our Primary Mirror control system has a beatnik bsp running on a mvme6100 with RTEMS4.10.2 and EPICS 3.14.12.8 (which understandably is not actively supported). We've experienced a single event that we've never seen before. vmeTsi148 ISR: ERROR: no handler 

After this it appears all interrupts were disabled and the VME bus communications are down. This system is normally well behaved with uptimes measured in months. In 2020 we had an uptime of 301 days!

Has anyone seen an error like this on the beatnik bsp?

Subsequent to the error which corresponds closely with a casr command, we see dbScan warnings in our logs. These persisted several times per minute until the system was reboot.

Thanks for any insight.

-Matt Rippa 

<8/3/2021 8:00:32 hst>pcs-mk-ioc> casr
<8/3/2021 8:00:33 hst>Channel Access Server V4.13
<8/3/2021 8:00:33 hst>Connected circuits:
<8/3/2021 8:00:33 hst>TCP xxxxxxxxxxxxxxxxxxxx, V4.13, 6 Channels, Priority=0
<8/3/2021 8:00:33 hst>TCP xxxxxxxxxxxxxxxxxxxx, V4.13, 134 Channels, Priority=80

<8/3/2021 8:00:33 hst>TCP , V4.13, 1 Channels, Priority=0
<8/3/2021 8:00:33 hst>TCP , V4.13, 5 Channels, Priority=0
<8/3/2021 8:00:33 hst>TCP , V4.13, 8 Channels, Priority=0
<8/3/2021 8:00:33 hst>TCP , V4.13, 60 Channels, Priority=0
<8/3/2021 8:00:33 hst>TCP , V4.13, 9 Channels, Priority=0
<8/3/2021 8:00:34 hst>TCP , V4.13, 9 Channels, Priority=0
<8/3/2021 8:00:34 hst>TCP , V4.13, 71 Channels, Priority=0
<8/3/2021 8:00:34 hst>TCP , V4.13, 5 Channels, Priority=0
<8/3/2021 8:00:34 hst>TCP , V4.13, 359 Channels, Priority=20
<8/3/2021 8:00:34 hst>TCP , 741 Channels, Priority=20
<8/3/2021 8:00:34 hst>TCP , V4.13, 5 Channels, Priority=20
<8/3/2021 8:00:34 hst>pcs-mk-ioc> vmeTsi148 ISR: ERROR: no handler registered (level 2) IACK 0x00000045 -- DISABLING level 2
<8/3/2021 8:05:14 hst>vmeTsi148 ISR: ERROR: no handler registered (level 4) IACK 0x00000040 -- DISABLING level 4
<8/3/2021 8:34:54 hst>dbScan warning from '.2 second' scan thread:
<8/3/2021 8:34:54 hst>        Scan processing averages 0.300 seconds (0.300 .. 0.300).
<8/3/2021 8:34:54 hst>        Over-runs have now happened 10 times in a row.
<8/3/2021 8:34:54 hst>        To fix this, move some records to a slower scan rate.
<8/3/2021 8:34:54 hst>
<8/3/2021 8:35:09 hst>dbScan warning from '.2 second' scan thread:
<8/3/2021 8:35:09 hst>        Scan processing averages 0.300 seconds (0.300 .. 0.300).
<8/3/2021 8:35:09 hst>        Over-runs have now happened 10 times in a row.
<8/3/2021 8:35:09 hst>        To fix this, move some records to a slower scan rate.
<8/3/2021 8:35:09 hst>
...