From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai-help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] crash after termination
Date: Tue, 23 Mar 2010 18:23:12 +0100 [thread overview]
Message-ID: <4BA8F900.5000602@domain.hid> (raw)
In-Reply-To: <4BA8F732.10206@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1825 bytes --]
Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
>> Stefan Kisdaroczi wrote:
>>> Hi Jan,
>>>
>>> Only user space using the native skin. Some additional notes:
>>> I'm using the freepascal compiler and link against libnative, i dont use gcc.
>>> There is one process starting the other ten processes using fork() & execl().
>>> The tasks do a lot of mode switching between primary/secondary.
>>> The stacksize for the tasks is 1MB. We only use between 4K-16K of stack in our
>>> applications. So there should be still a bit less than 1 MB for socket calls
>>> and printf, is this to low ?
>> Also stack overflows must not crash the kernel, they may only cause
>> application crashes.
>>
>>> I rebuilt the kernel without arcnet and isdn and disabled smp too, using 2.5.1.
>>> It still crashes every time on termination. If I pull the network connector,
>>> I could start and shutdown the applications 5 times without problem. If the
>>> network is connected, as soon as there is some network activity like ssh/samba
>>> on termination the box crashes. Sometimes it gets even back to the prompt before
>>> crashing. Its a rtl8139 network card, but happens in a virtualbox-vm with a pcnet
>>> card too. In the traces is always a "do_IRQ+0x...", so I think the problem is
>>> related to IRQ-handling.
>> That sounds promising! If you can provide your test case to us (or me
>> privately), we could try to reproduce - inside a proper hypervisor which
>> has proper debugging facilities. :)
>
> I do not know if this could be related, but you have two drivers we 8139
> in their name. Could there be a conflict?
>
I would say only the 8139cp gets hold of all the hardware - unless there
cards plugged that only the 8139too supported. Otherwise, that 8139too
should simply remain unused.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2010-03-23 17:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 15:46 [Xenomai-help] crash after termination Stefan Kisdaroczi
2010-03-20 15:53 ` Jan Kiszka
2010-03-22 10:36 ` Stefan Kisdaroczi
2010-03-23 8:00 ` Jan Kiszka
2010-03-23 13:25 ` Stefan Kisdaroczi
2010-03-23 17:06 ` Jan Kiszka
2010-03-23 17:15 ` Gilles Chanteperdrix
2010-03-23 17:23 ` Jan Kiszka [this message]
2010-03-24 2:54 ` [Xenomai-help] Problem in irq_handle robert165
2010-03-24 10:22 ` Gilles Chanteperdrix
2010-03-25 2:55 ` robert165
2010-03-25 7:55 ` Gilles Chanteperdrix
2010-03-25 12:50 ` robert165
2010-03-25 13:49 ` Gilles Chanteperdrix
2010-03-25 14:28 ` Jan Kiszka
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=4BA8F900.5000602@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=gilles.chanteperdrix@xenomai.org \
--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.