All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: xenomai-core <xenomai@xenomai.org>
Subject: [Xenomai-core] [BUG?] delayed PIC timer event
Date: Thu, 19 Oct 2006 18:21:14 +0200	[thread overview]
Message-ID: <4537A5FA.509@domain.hid> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1221 bytes --]

Hi,

while actually cross-checking some user's problem with RTnet (not on
Xenomai), I happen to stumble over another weirdness. Scenario:

RTnet under high load (>5 KHz network IRQ rate, large packets), "latency
-p1000" as additional load, Pentium 266 MHz (tried boards from different
vendors), kernel 2.6.17.13, Xenomai trunk, ipipe-1.5-00, CONFIG_M586TSC,
!CONFIG_X86_UP_APIC

Main protagonists:
 - "display-" (user, PID 909, prio 0/-1)
 - "samplin" (user, PID 910, prio 99)
 - stack manager (kernel, PID -1, prio 98)
 - "client", the RTnet test (user, PID 903, prio 10)

So the sampling task is definitely the chief and should only be delayed
by IRQ handlers. Generally it is (~120 us with i-pipe tracer enabled),
but there happen to be delays of more than 500 us. Attached is such a trace.

Specifically suspicious is the fact that the timer IRQ, which should
have popped up around -500, is not blocked by some hard IRQ lock. Rather
it takes someone else (the RTnet test) to start another timer, and then
the delayed event gets raised immediately. Hardware issue? Bug in
Xenomai? With the same boot image on a P-III, this does not happen.

Any ideas what to check first are welcome.

Jan

[-- Attachment #1.2: dump.gz --]
[-- Type: application/x-gzip, Size: 30684 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

             reply	other threads:[~2006-10-19 16:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-19 16:21 Jan Kiszka [this message]
2006-10-22 13:39 ` [Xenomai-core] [BUG?] delayed PIC timer event Gilles Chanteperdrix
2006-10-22 14:03   ` Philippe Gerum

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=4537A5FA.509@domain.hid \
    --to=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.