linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
	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 15:27:48 +0200	[thread overview]
Message-ID: <20190624132748.n4lgg4swj4nzirdb@linutronix.de> (raw)
In-Reply-To: <20190624105340.GA21414@amd>

On 2019-06-24 12:53:40 [+0200], Pavel Machek wrote:
> Hi!
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.
> 
> I tried 4.19.13-rt1-cip1 among others. Crash is early in boot, I can
> try some early printing...

The latest is v4.19.50-rt22 I would suggest that one. There was a bug
which was fixed either in 4.19.23-rt14 or in the following version.

If the latest one does not work please let me know and I will have a
look.

> Best regards,
> 									Pavel

Sebastian

  parent reply	other threads:[~2019-06-24 13:27 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
2019-06-24 13:27     ` Sebastian Andrzej Siewior [this message]
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=20190624132748.n4lgg4swj4nzirdb@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=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).