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: Tue, 17 Feb 2015 18:27:59 +0100 [thread overview]
Message-ID: <54E37A1F.4020405@siemens.com> (raw)
In-Reply-To: <54E354F9.30703@siemens.com>
On 2015-02-17 15:49, Jan Kiszka wrote:
> Retested and, although I could have sworn that !CONFIG_IPIPE doesn't
> cause this effect, it does on 3.14.28. And checking CPU features again,
> there is both "hle" and "rtm" - in contrast to a newer 3.18 kernel where
> those are gone (same distro, same hardware).
>
> So this is not an I-pipe issue, it's something related to the kernel or
> its configuration. Need to study again where the microcode comes from. I
> thought it was pulled from /lib/firmware/somewhere, thus would be shared
> between all kernels on the same rootfs.
Just to close the topic: We had early microcode loading disabled in the
kernel, likely due to some historic reasons (there was a crash once).
That caused systemd to load libpthread before the microcode fix that
disables RTM was loaded. Once the microcode came in, the RTM
instructions suddenly start to cause #UD. Nice. Not sure yet if this
explains the issues in the customer application - we will see later.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2015-02-17 17:27 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
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 [this message]
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=54E37A1F.4020405@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.