All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: rpm@xenomai.org
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] BUG fs/buffer.c with Linux 2.6.26,27
Date: Fri, 20 Feb 2009 13:05:30 +0100	[thread overview]
Message-ID: <499E9C8A.20309@domain.hid> (raw)
In-Reply-To: <499E95F5.10307@domain.hid>

Philippe Gerum wrote:
> Roman Pisl wrote:
>> Hello Philippe, Jan and other experts,
>> I did some tests on the desktop and the bug is still present.
>>
>> I tried both disabling CONFIG_PREEMPT and applying __ipipe_syscall_root
>> patch.
>>
>> Unfortunately I couldn't test Xenomai from trunk with our application,
>> because events are probably broken - attached example segfaults on
>> rt_event_wait. So I still use 2.4.6.1 and that is the reason for the
>> problem with void rthal_propagate_irq when
>> adeos-ipipe-2.6.27.13-x86-2.2-05.patch is applied.
>>
>> Jan wrote:
>> The tracer log for .27 looks strange - did you apply my
>> ipipe-trace-over-ftrace patch or just enabled the existing code? In the
>> latter case, the .26-based trace log would be nice to cross-check and
>> exclude tracer artifacts.
>>
>> Sorry, but I don't know where this patch comes from. I enabled existing
>> code only.
>>
>> .configs and logs are attached.
>>
> 
> FYI, testev.c is broken; the rt_event_wait() arglist is really wrong: mask_r
> is a mandatory arg that may not be passed as NULL, and the mode/timeout args
> have been inverted.

Ah, good to know. I suspected something like that as I also see such
faults in the return path of __rt_event_wait with 2.4.x and the test
binary I received privately. So this is actually a trigger for the ipipe
issue we have.

I'm almost done with understanding the race in ipipe. It looks like
stalling the root domain in __ipipe_handle_exception when
__rt_event_wait triggers some fault over the Xenomai domain is buggy.
Because this stalled state is then propagated to a different Linux task
context, causing the root domain's IRQ corruption. More on this shortly.

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux


  reply	other threads:[~2009-02-20 12:05 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-17 22:14 [Xenomai-help] BUG fs/buffer.c with Linux 2.6.26,27 Roman Pisl
2009-02-17 22:38 ` Philippe Gerum
2009-02-17 22:50 ` Jan Kiszka
2009-02-18  0:07   ` Gilles Chanteperdrix
2009-02-18  0:26     ` Gilles Chanteperdrix
2009-02-18  7:58       ` Jan Kiszka
2009-02-18 10:28         ` Gilles Chanteperdrix
2009-02-18 12:06           ` Jan Kiszka
2009-02-18 13:33             ` [Xenomai-help] __ipipe_syscall_root logic (was: BUG fs/buffer.c with Linux 2.6.26, 27) Jan Kiszka
2009-02-18 13:52               ` [Xenomai-help] __ipipe_syscall_root logic Gilles Chanteperdrix
2009-02-18 13:56                 ` Jan Kiszka
2009-02-19 15:49               ` [Xenomai-help] [Adeos-main] " Philippe Gerum
2009-02-19 16:14                 ` Jan Kiszka
2009-02-19 16:22                   ` Philippe Gerum
2009-02-18 19:15 ` [Xenomai-help] BUG fs/buffer.c with Linux 2.6.26,27 Philippe Gerum
2009-02-19 17:38   ` Roman Pisl
2009-02-19 18:08     ` Jan Kiszka
2009-02-19 18:23       ` Steven Seeger
2009-02-19 18:32         ` Philippe Gerum
2009-02-20 11:37     ` Philippe Gerum
2009-02-20 12:05       ` Jan Kiszka [this message]
2009-02-20 12:10       ` Roman Pisl

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=499E9C8A.20309@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=rpm@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.