Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Mon, 24 Jun 2019 15:27:48 +0200
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
Message-ID: <20190624132748.n4lgg4swj4nzirdb@linutronix.de>
References: <20190622081954.GA10751@amd>
 <2804bc5b-18c1-2793-171c-045c0725a6a7@siemens.com>
 <20190624105340.GA21414@amd>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20190624105340.GA21414@amd>
User-Agent: NeoMutt/20180716
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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