From: Philippe Gerum <rpm@xenomai.org>
To: roderik.wildenburg@domain.hid
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] network stall
Date: Wed, 18 Nov 2009 14:37:25 +0100 [thread overview]
Message-ID: <1258551445.2348.148.camel@domain.hid> (raw)
In-Reply-To: <5D63919D95F87E4D9D34FF7748CE2C2A01D8F93D@ARVMAIL1.mra.roland-man.biz>
On Tue, 2009-11-17 at 10:42 +0100, roderik.wildenburg@domain.hid
wrote:
> On one of our platforms (PPC 5200B Kernel 2.4, Xenomai 2.4.8, PCI-bus) we face rare network stalls (once a day).
> In this situation network communication seems to be completly dead, but obviously only the receive direction is affected as receive-interrupts in /proc/interrupts aren´t incremented while transmit interrupts are incremented.
> Wireshark-protocoll (taken via port mirroring of the switch) says that packets are sent to the target, but tcpdump on the target does not show these packets (which is obvious, if receive-interrupt isn´t operational).
> In the send direction only arp-requests are monitored (on the target and on the switch).
> Unfortunatelly this situation can´t be reproduced in an laboratory environment
>
> On our other platform, which is very similar (PPC 5200B Kernel 2.4, Xenomai 2.4.8) but without PCI we don´t have this problem. Therefore I am thinking whether Ipipe (in combination with PCI) could be responsible for the interrupt lock?
>
> Does anybody have an idea/suggestion how we can track down the reason for interrupt blockade?
> Are there some helpful /proc entries (/proc/ipipe wasn´t very useful for me)?
> Unfortunatelly, as far as I know, Ipipe-tacer is only available for Kernel 2.6. Am I right?
Yes.
>
>
> I would appreciate any suggestion very much!
>
Make sure to disable CONFIG_XENO_OPT_ISHIELD. This option was reported
to introduce interrupt propagation issues at least once, certainly adds
some overhead, and won't buy you anything with your configuration. It
has been removed from 2.5.
> Roderik
>
> --------------------------------------------------------
> manroland AG
> Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
> Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, Dr. Markus Rall, Paul Steidle
> Sitz der Gesellschaft: Offenbach am Main, Registergericht: Amtsgericht Offenbach HRB-Nr. 42592
> USt-Ident-Nr. DE 250200933
>
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help
--
Philippe.
prev parent reply other threads:[~2009-11-18 13:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 9:42 [Xenomai-help] network stall roderik.wildenburg
2009-11-17 14:05 ` Gilles Chanteperdrix
2009-11-17 16:04 ` Wolfgang Grandegger
2009-11-18 7:41 ` roderik.wildenburg
2009-11-18 12:14 ` Wolfgang Grandegger
2009-11-18 13:37 ` Philippe Gerum [this message]
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=1258551445.2348.148.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=roderik.wildenburg@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.