From: Philippe Gerum <rpm@xenomai.org>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: Jan Kiszka <jan.kiszka@domain.hid>, xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] nervous nmi-watchdog
Date: Mon, 05 Jun 2006 21:15:00 +0200 [thread overview]
Message-ID: <448482B4.2040105@domain.hid> (raw)
In-Reply-To: <17540.32930.566897.960413@domain.hid>
Gilles Chanteperdrix wrote:
> Philippe Gerum wrote:
> > Jan Kiszka wrote:
> > > Hi,
> > >
> > > I'm getting nmi alarms about latency being > 100 us on a dual P-III 1GHz
> > > (with and without CONFIG_SMP) once I start the latency test tool. But
> > > the must be false positive. Can someone comment on this trace:
> > >
> >
> > Issue confirmed here, on a dual 750 Mhz PIII Celeron. Starting the
> > latency test, the NMI watchdog pulls the break on cpu #0 after a few us,
> > albeit rthal_nmi_arm() had been told to trigger the NMI more than a
> > millisecond in the future (likely the HTICK emulation + 100 us NMI
> > threshold).
> >
> > Running a UP + LAPIC enabled kernel on the same hw did not trigger the
> > spurious NMI, so I'd bet that the issue is SMP related, and not
> > hw/perfctr related.
>
> 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.
--
Philippe.
next prev parent reply other threads:[~2006-06-05 19:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 20:21 [Xenomai-core] nervous nmi-watchdog Jan Kiszka
2006-06-05 16:35 ` Philippe Gerum
2006-06-05 19:06 ` Gilles Chanteperdrix
2006-06-05 19:15 ` Philippe Gerum [this message]
2006-07-09 12:50 ` Gilles Chanteperdrix
2006-07-09 16:41 ` Philippe Gerum
2006-07-09 16:56 ` Jan Kiszka
2006-07-09 17:07 ` Philippe Gerum
2006-07-09 18:13 ` Jan Kiszka
2006-07-09 19:36 ` Gilles Chanteperdrix
2006-07-10 17:28 ` Gilles Chanteperdrix
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=448482B4.2040105@domain.hid \
--to=rpm@xenomai.org \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=jan.kiszka@domain.hid \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.