All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Petr Cervenka <grugh@domain.hid>
Cc: xenomai-help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] xenomai 2.4.10 - invalid opcode: 0000
Date: Tue, 15 Dec 2009 18:34:40 +0100	[thread overview]
Message-ID: <4B27C8B0.3030902@domain.hid> (raw)
In-Reply-To: <4B241D1B.1030002@domain.hid>

Jan Kiszka wrote:
> Jan Kiszka wrote:
>> ...
>> Reproducible with your .config under kvm, will investigate later.
>>
> 
> It looks like we have a problem with CONFIG_PREEMPT on x86-SMP at the
> moment (2.6.30&.31, maybe also older kernels). You may try with
> CONFIG_PREEMPT_VOLUNTARY/NONE, but I can't promise that this heals the
> issue, maybe it just makes it far less probable.
> 
> The corruption is easy to reproduce - but always at different spots,
> thus it's very hard to catch. Still investigating.
> 

I think I found all gremlins, the last one [1] was probably the major
contributor. Could you try if the patches in [2] help you? Works for me
so far.

Jan

[1]http://permalink.gmane.org/gmane.linux.kernel.adeos.general/1491
[2]http://git.kiszka.org/?p=ipipe-2.6.git;a=shortlog;h=refs/heads/queues/2.6.31-x86

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux


  reply	other threads:[~2009-12-15 17:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-08 14:14 [Xenomai-help] xenomai 2.4.10 - invalid opcode: 0000 Petr Cervenka
2009-12-08 15:04 ` Jan Kiszka
2009-12-09 14:50   ` Petr Cervenka
2009-12-09 18:28     ` Jan Kiszka
2009-12-10 10:07       ` Petr Cervenka
2009-12-10 12:00         ` Jan Kiszka
2009-12-12 22:45           ` Jan Kiszka
2009-12-15 17:34             ` Jan Kiszka [this message]
2009-12-17  8:28               ` Petr Cervenka
2009-12-09 15:08   ` Petr Cervenka

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=4B27C8B0.3030902@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=grugh@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.