Philippe Gerum wrote:
I never observe this on my dual PIII whereas I always have the NMI
watchdog option enabled. Are you running with or without the tracer ?
w/o.
enabling xeno nmi watchdog whereas the nucleus module is built-in break
Linux nmi watchdog test. Maybe some setups are
On Sun, 2006-07-09 at 14:50 +0200, Gilles Chanteperdrix wrote:
Philippe Gerum wrote:
I never observe this on my dual PIII whereas I always have the NMI
watchdog option enabled. Are you running with or without the tracer ?
w/o.
enabling xeno nmi watchdog whereas the nucleus
Philippe Gerum wrote:
On Sun, 2006-07-09 at 14:50 +0200, Gilles Chanteperdrix wrote:
Philippe Gerum wrote:
I never observe this on my dual PIII whereas I always have the NMI
watchdog option enabled. Are you running with or without the tracer ?
w/o.
enabling xeno nmi
On Sun, 2006-07-09 at 18:56 +0200, Jan Kiszka wrote:
I can confirm the failing NMI test here on my notebook with both nucleus
and native skin built into the kernel. I haven't seen false positive
NMIs yet, but the tracer is still on. Will switch off and re-check.
FWIW, here, the false positive
Hi,
it's a bit crazy but it seems to work: This tiny patch against an I-pipe
kernel really allows suspend to disk/ram for a *running* Xenomai system.
Just the TSC-based timers are skewed up after resume so that, e.g., the
latency test takes a longer pause then. But a serious use-case would
rather
Philippe Gerum wrote:
On Sun, 2006-07-09 at 18:56 +0200, Jan Kiszka wrote:
I can confirm the failing NMI test here on my notebook with both nucleus
and native skin built into the kernel. I haven't seen false positive
NMIs yet, but the tracer is still on. Will switch off and re-check.
FWIW,
Philippe Gerum wrote:
On Sun, 2006-07-09 at 18:56 +0200, Jan Kiszka wrote:
I can confirm the failing NMI test here on my notebook with both nucleus
and native skin built into the kernel. I haven't seen false positive
NMIs yet, but the tracer is still on. Will switch off and re-check.
