All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Philippe Gerum <rpm@xenomai.org>, Xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] [PULL] ipipe: fixes for 3.14
Date: Mon, 16 Feb 2015 19:52:27 +0100	[thread overview]
Message-ID: <54E23C6B.2020103@siemens.com> (raw)
In-Reply-To: <54E22E5E.7080003@siemens.com>

On 2015-02-16 18:52, Jan Kiszka wrote:
> On 2015-02-16 18:48, Philippe Gerum wrote:
>> On 02/16/2015 06:35 PM, Jan Kiszka wrote:
>>> The following changes since commit 00d8a6f2e95453f61ae97b6587dba03bc91c7e1a:
>>>
>>>   arm/ipipe: Resolve trival merge conflicts (2015-01-14 17:00:22 +0100)
>>>
>>> are available in the git repository at:
>>>
>>>   git://git.xenomai.org/ipipe-jki 
>>>
>>> for you to fetch changes up to f982e48ce99e1bc9e71eac21830adac2db265c98:
>>>
>>>   x86/ipipe: Restore invocation of ipipe_unlock_irq from startup_ioapic_irq (2015-02-16 18:22:21 +0100)
>>>
>>> All patches apply to 3.16 as well but weren't tested there yet. Still
>>> analyzing strange
>>>
>>> traps: (systemd)[1420] trap invalid opcode ip:7f4d138f612b sp:7fff4fd8f568 error:0 in libpthread-2.19.so[7f4d138e5000+18000]
>>>
>>> on the target under 3.14...
>>>
>>
>> Register trashing on the fast call path (system_call_after_gs) maybe.
>> Forcing CONFIG_IPIPE_LEGACY there might help ruling this out.
> 
> That's without any Xenomai configured. But I will check.

This is where it traps in libpthread:

   1112b:       c7 f8 00 00 00 00       xbeginq 11131 <__lll_lock_elision+0x51>

For some reason, glibc starts to believe it could use RTM on that
machine - although this is clearly not available (Haswell i7, thus a
buggy CPU). Need to understand which feature check goes wrong, and why
only on I-pipe enabled kernels.

The good news is that I still have a similar and unresolved report from
early customer tests. That could solve their issues as well (they
caused massive domain migrations).

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux


  reply	other threads:[~2015-02-16 18:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-16 17:35 [Xenomai] [PULL] ipipe: fixes for 3.14 Jan Kiszka
2015-02-16 17:48 ` Philippe Gerum
2015-02-16 17:52   ` Jan Kiszka
2015-02-16 18:52     ` Jan Kiszka [this message]
2015-02-16 19:11       ` Jan Kiszka
2015-02-16 19:35         ` Philippe Gerum
2015-02-16 20:15           ` Jan Kiszka
2015-02-17 14:49             ` Jan Kiszka
2015-02-17 17:27               ` 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=54E23C6B.2020103@siemens.com \
    --to=jan.kiszka@siemens.com \
    --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.