Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
languagenone
Jun 23 16:49:50 low kernel: i2c i2c-0: i2c_pxa: timeout waiting for bus free
Jun 23 16:49:53 low last message repeated 5 times
Jun 25 09:27:58 low kernel: handle_IRQ_event called 4 times for IRQ 3
Jun 25 17:46:14 low kernel: handle_IRQ_event called 4 times for IRQ 3

So it turns out those messages are old and aren't much help.

Those were the only messages before the reboot, and they occurred at least 23 hours earlier, which means the problem is not due to a kernel oops, or any other atypical event that the kernel could detect. It is just the good ol' situation where there seems to be a very small but finite possibly that a PC104 interrupt can be missed, and not retriggered, even though the PC104 IRQ interrupt line is high, such that the interrupt handler is never again called.

I believe restarting the dsm process with a ddn/dup, which closes and re-opens the serial ports, I believe a adn/aup will bring it back too.

I just updated the xml on the low DSM so that every sensor has a timeout. That should The dsm process should then close and reopen each port after detecting the timeout, which should also help to recover from this situation more quickly.

Seems that I need to install a PC104 interrupt watchdog module. There is some indication this has happened on the aircraft, also quite infrequently. A test is being setup out at RAF.