From: Jan Kiszka <jan.kiszka@siemens.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-rt-users@vger.kernel.org,
kernel list <linux-kernel@vger.kernel.org>,
mwhitehe@redhat.com
Subject: Re: PREEMPT_RT_FULL on x86-32 machine
Date: Mon, 24 Jun 2019 12:58:04 +0200 [thread overview]
Message-ID: <903a1932-c530-5c45-31ab-a3b4d61d48eb@siemens.com> (raw)
In-Reply-To: <20190624105340.GA21414@amd>
On 24.06.19 12:53, Pavel Machek wrote:
> Hi!
>
>>> Is full preemption supposed to work on x86-32 machines?
>>>
>>> Because it does not work for me. It crashes early in boot, no messages
>>> make it to console. Similar configuration for x86-64 boots ok.
>>>
>>
>> Maybe you can also tell which version(s) you tried, and in which
>> configuration(s), and how the crash looked like.
>
> I wanted to know if the configuration is supposed to work at all
> before starting heavy debugging. From your reply I assume that it
> should work.
We still have at least one 4.4-based 32-bit-only target on RT. But there is
likely more, even though I'm promoting to use at least a 64-bit kernel on 64-bit
capable hw for many years, irrespective of RT.
Jan
>
> I tried 4.19.13-rt1-cip1 among others. Crash is early in boot, I can
> try some early printing...
>
> Best regards,
> Pavel
>
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2019-06-24 10:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-22 8:19 PREEMPT_RT_FULL on x86-32 machine Pavel Machek
2019-06-24 9:29 ` Jan Kiszka
2019-06-24 10:53 ` Pavel Machek
2019-06-24 10:58 ` Jan Kiszka [this message]
2019-06-24 13:27 ` Sebastian Andrzej Siewior
2019-06-28 12:51 ` Pavel Machek
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=903a1932-c530-5c45-31ab-a3b4d61d48eb@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mwhitehe@redhat.com \
--cc=pavel@ucw.cz \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).