Received: by 2002:a25:f815:0:0:0:0:0 with SMTP id u21csp2287689ybd; Mon, 24 Jun 2019 03:59:33 -0700 (PDT) X-Google-Smtp-Source: APXvYqzh9OsAKhQMGi45IplCXDQOCC9yCmTIy0OXMNBbBzo6hWZUZzwVbLqsXIinR+LHL7deUVNH X-Received: by 2002:a17:90a:2506:: with SMTP id j6mr24840417pje.129.1561373973646; Mon, 24 Jun 2019 03:59:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561373973; cv=none; d=google.com; s=arc-20160816; b=ffMK4/pqifpmtMC8S9czoJZiYYGMaKAV7T9wSv2LGbheGz1pBIHiLrZJk5E+2cxn9S uBE2l/erYSU9M5oXMRjMewHEOAnBIWHMt30WxTLv7e1S6R+zLWipMinb2dW7WJ9VWVva GKN5dlXfvpHRM/rDfH3GtPAUL2ZpxWrVpWTDTIkJixsv9NyJknBvLtzG0uJ4RZzsDoz+ u54WGT2pD5r7+IfvuI8CmQ9uguREE061ldtnQ6tTDwmF3zQv/DTFdS4QFQv0pP14Q77e X76+oJP6k4WcSU1FOzwHqjg2ltbMpebEOOUpq2vOMkOsIddwVigNlEeVivGVAnrazP00 ggXQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=DmQHAW3Ox7rK3ahM+nW5gMzX9Gi0d0ByW2NuEeKU9pA=; b=t51D+CInEkuLSLPv+KfI2qEjrYEz6sbWZM3ST/H2R9iguar4u8f/fpUtRQYLYXB0TR qzKp1HZ+9/XIByWU9tSIOMRdhOIsV7HMGCQPGefw5NQd4O5GHhmvVV0rOAruDwXbGl2u x7eAy8g71LVFEDWFQKhajgG2VmMVCAQyvVE5PKZNARwRVXBVNmW7arSQS7KdFBerF6MF VFup37UN/96OK1aaAYP7bghyfzJev9zLC50rD4jhOtNK0im/eYMMCXazAMNa6Y+kkp8E 1MOHSoS3uSfU+jwVCvYOnPGMLJuHU+SAMJjEgc1tKxmZ6h0JWVn08V4xSsKyVxO7xSpC VzoQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=siemens.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d8si9217744plr.237.2019.06.24.03.59.17; Mon, 24 Jun 2019 03:59:33 -0700 (PDT) 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; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=siemens.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729403AbfFXK6Y (ORCPT + 99 others); Mon, 24 Jun 2019 06:58:24 -0400 Received: from gecko.sbs.de ([194.138.37.40]:42687 "EHLO gecko.sbs.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727730AbfFXK6Y (ORCPT ); Mon, 24 Jun 2019 06:58:24 -0400 Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by gecko.sbs.de (8.15.2/8.15.2) with ESMTPS id x5OAw6vg021376 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 24 Jun 2019 12:58:06 +0200 Received: from [139.25.68.37] (md1q0hnc.ad001.siemens.net [139.25.68.37] (may be forged)) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id x5OAw5ja021035; Mon, 24 Jun 2019 12:58:05 +0200 Subject: Re: PREEMPT_RT_FULL on x86-32 machine To: Pavel Machek Cc: linux-rt-users@vger.kernel.org, kernel list , mwhitehe@redhat.com References: <20190622081954.GA10751@amd> <2804bc5b-18c1-2793-171c-045c0725a6a7@siemens.com> <20190624105340.GA21414@amd> From: Jan Kiszka Message-ID: <903a1932-c530-5c45-31ab-a3b4d61d48eb@siemens.com> Date: Mon, 24 Jun 2019 12:58:04 +0200 User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 In-Reply-To: <20190624105340.GA21414@amd> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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