Philippe Gerum wrote: > On Tue, 2010-07-06 at 17:54 +0200, Jan Kiszka wrote: >>>> CONFIG_XENO_OPT_WATCHDOG=y >>>> CONFIG_XENO_OPT_WATCHDOG_TIMEOUT=60 >>> 60s seems way too long to have a chance of recovering from a runaway >>> loop to a reasonably sane state. >> That's required for debugging the kernel. >> > > I don't understand this requirement. Any insight?
While you step though a Xenomai task context, timers continue to tick. So the period spent in that context gets huge, and soon the task will be shot by the watchdog. Likely a limitation of kvm (interrupts should be blockable in singlestep mode). Haven't looked at all details yet, just picked the lazy workaround. Of course, we don't use this value on real HW. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux _______________________________________________ Xenomai-core mailing list Xenomaiemail@example.com https://mail.gna.org/listinfo/xenomai-core