On Tue, 27 May 2008 15:37:00 -0700 vb <vb@xxxxxxxx> wrote: > On Tue, May 27, 2008 at 3:31 PM, Josh Boyer <jwboyer@xxxxxxxxx> wrote: > > On Tue, 27 May 2008 14:57:50 -0700 > > David VomLehn <dvomlehn@xxxxxxxxx> wrote: > > > >> Continuous Logging for Watchdog Timer Expiration > >> ------------------------------------------------ > >> We run with a watchdog timer that can reboot the system. When we reboot, we lose > >> all of our status, making it very difficult to determine what went wrong. > >> Fortunately, there is only one major cause of not refreshing the watchdog--a > >> driver disabled interrupts for so long that the timer function that resets the > >> watchdog timer never had a chance to run. So, a way to log what functions were > >> enable and disabling interrupts on a continuous basis, along with a memory > >> section that wouldn't be overwritten on reboot, would allow capturing the cause > >> for these otherwise "silent" reboots. > > > > I believe lttng (or ltt-ng or whatever) has the ability to do > > continuous IRQ tracing. It also does much more. Have you looked at > > that at all? > > > > Ideally not just IRQs but all exceptions need to be traced and saved > in this log. lttng can trace quite a few events. Interrupts, system calls, etc. Might be worth a look, and it's quite well maintained against various kernel versions. josh -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
