lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <903a1932-c530-5c45-31ab-a3b4d61d48eb@siemens.com>
Date:   Mon, 24 Jun 2019 12:58:04 +0200
From:   Jan Kiszka <jan.kiszka@...mens.com>
To:     Pavel Machek <pavel@....cz>
Cc:     linux-rt-users@...r.kernel.org,
        kernel list <linux-kernel@...r.kernel.org>, mwhitehe@...hat.com
Subject: Re: PREEMPT_RT_FULL on x86-32 machine

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ