From: "M. Koehrer" <mathias_koehrer@domain.hid>
To: jan.kiszka@domain.hid, mathias_koehrer@domain.hid
Cc: xenomai@xenomai.org, rtnet-users@domain.hid
Subject: Aw: Re: [RTnet-users] [Xenomai-help] rtnet / Xenomai: Kernel 2.6.19.1
Date: Mon, 18 Dec 2006 15:20:23 +0100 (CET) [thread overview]
Message-ID: <10606813.1166451623805.JavaMail.ngmail@domain.hid> (raw)
Hi Jan,
I tried disabling SMP - but no success...
Unfortuantely, the SMI watchdog does not work on my machine.
After booting the PC, dmesg shows me the line
Xenomai: NMI watchdog not available.
Is the NMI watchdog support somehow configurable or is this a real hardware issue?
For patching the kernel, I used the adeos-ipipe-2.6.19-i386-1.6-02.patch which is
part of Xenomai.
As I do not see an easy way to get the 2.6.19.* running, I think, I will switch back to
the latest 2.6.17.* kernel (2.6.17.14) which works fine.
Regards
Mathias
> > I have an issue with the latest Xenomai (svn #1962) and rtnet (svn #1095)
> versions
> > using kernel 2.6.19.1. The very same application worked fine on 2.6.17.7
> (same Xenomai/rtnet).
>
> /Might/ be an issue of the still fresh 2.6.19 patch. You are using
> latest ipipe 1.6-02? Any difference with an earlier version of the
> patch? Is the IRQ routing identical for both 2.6.19 and .17?
>
> > My application does the following steps in user space:
> > 1) I open one UDP socket to an embedded device.
> > 2) The timeout of the socket is set to 5 seconds.
> > 3) I send out one UDP message A via rt_dev_send() to the device.
> > 4) Then I wait for the response for A in rt_dev_recv()
> > 5) Directly after the return of rt_dev_recv() I send message B via
> rt_dev_send()
> > 6) Then I wait for the response for B in rt_dev_recv()
> > Here my PC freezes. I am no longer able to access it, I have to press the
> reset button on the PC.
> >
> > I have connected the PC and the embedded device with a hub. This allows me
> to monitor the network
> > traffic using a second PC. Ethereal shows me, that message B is sent to
> the embedded device
> > and the response of B is sent back to the PC.
> >
> > Whenever I place a printf() directly after the rt_dev_recv() statements to
> see what happens,
> > everything works fine and the PC no longer freezes.
>
> printf causes a mode switch and certainly some delay that may let the
> system avoid the race situation above.
>
> >
> > As mentioned above, when I use the very same application with 2.6.17.7
> (same Xenomai, rtnet version)
> > everything is perfect!
> > I have a Pentium 4 Dual core, SMP enabled.
> >
> > Any idea on this strange behaviour?
>
> Not directly.
>
> OK, this is what you could try: Switch on the Xenomai watchdogs (soft
> and NMI). Check if the NMI watchdog is working: boot log messages, maybe
> even a test triggering via small /proc/xenomai/nmi_maxlat (we had
> problems with it already on some other user's box, so some confirmation
> the NMI works is useful). Then see if you system can at least issue some
> oops on lock-up. Attach a serial console to grab it.
>
> Beyond this test, could you also try with CONFIG_SMP switched off?
>
> Jan
>
>
>
--
Mathias Koehrer
mathias_koehrer@domain.hid
Viel oder wenig? Schnell oder langsam? Unbegrenzt surfen + telefonieren
ohne Zeit- und Volumenbegrenzung? DAS TOP ANGEBOT JETZT bei Arcor: günstig
und schnell mit DSL - das All-Inclusive-Paket für clevere Doppel-Sparer,
nur 44,85 inkl. DSL- und ISDN-Grundgebühr!
http://www.arcor.de/rd/emf-dsl-2
next reply other threads:[~2006-12-18 14:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-18 14:20 M. Koehrer [this message]
2006-12-18 14:26 ` [RTnet-users] [Xenomai-help] rtnet / Xenomai: Kernel 2.6.19.1 Jan Kiszka
2006-12-18 14:29 ` Aw: " Gilles Chanteperdrix
2006-12-18 15:20 ` Aw: Re: Aw: Re: [RTnet-users] [Xenomai-help] rtnet / Xenomai: Kernel M. Koehrer
2006-12-18 15:32 ` 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=10606813.1166451623805.JavaMail.ngmail@domain.hid \
--to=mathias_koehrer@domain.hid \
--cc=jan.kiszka@domain.hid \
--cc=rtnet-users@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.