Received: by 2002:a05:6a10:6006:0:0:0:0 with SMTP id w6csp319233pxa; Thu, 27 Aug 2020 03:18:15 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxrmBGIJ+82hArZBslAEBAXGbFjTLcD8aylR1SjjMnOLwSMtFQ6J7Zl079rz24Jd2P8leoP X-Received: by 2002:a17:906:1756:: with SMTP id d22mr19943391eje.29.1598523495364; Thu, 27 Aug 2020 03:18:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1598523495; cv=none; d=google.com; s=arc-20160816; b=RrqFS5uWOpfa8c1/HCaiPWMJZFIQkuM53yMlwm83tynbQX+GokGXhiqsuI0RqggC8w Y8YsnJh+UhuTNyO+Y6wtQKG5sgnQoVECwHpv8VTTJgLJsTAPT8C60RKfLZAvCzjrp9xU pyuGIm9v+kzVuqb5K57BguLdO8sgorGXuILDoCDPvkqu+jruJRskhieHmv00NCb80U6c unk+Fa5KPEDusPknLln+oUoh/TWg6kGh4PVxNvFQDJU5XapWwZk0JIYhrWCMekug8vaw itPq0KVEtuofNoBAqO/Iq31eRjeLeJ5uJWpVn4o5MzQ7Nb/38qH4YRUJsJB9MrnNd6v3 9avQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=w9BLky1aJokk2B4ITifVmyoSgDm9RT5qwqeWrUiWCaA=; b=SbKhGNv9s81zJa+SmLxsm+7FhijGwawBHF6KbTe07PpNQE7JmNVAuqQiIHpOLFZMYL eotKA5/zGd6e72qGX1loIikLxWb+ry6EdRXsyMyvGJkpvxR1kuOmIMRCDaR9KbXPQCHK gtmnyDbZOijAOa8crL3ZBvhIacFmCNqVTNGaU+m7rY/Hi4NyeH98ek7Jmxzwv0CLwU4X 0Je19rykmAi4qMMHT9NbsE8BflkdGHGlTBEqU2Nijk1ZX8K9NIWNC/GWIKexqnM/tRMf ZAXap3uCU2FrqtswRBE7Ve/rUVafmY3gG72YOW5beiSTuLY93NppWJaL7katwIz9EYhp 280Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=monom.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id s23si1076892ejr.413.2020.08.27.03.17.52; Thu, 27 Aug 2020 03:18:15 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=monom.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728917AbgH0KQd (ORCPT + 99 others); Thu, 27 Aug 2020 06:16:33 -0400 Received: from mail.monom.org ([188.138.9.77]:50060 "EHLO mail.monom.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728508AbgH0KQZ (ORCPT ); Thu, 27 Aug 2020 06:16:25 -0400 Received: from mail.monom.org (localhost [127.0.0.1]) by filter.mynetwork.local (Postfix) with ESMTP id E73E150035A; Thu, 27 Aug 2020 12:16:22 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on mail.monom.org X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham autolearn_force=no version=3.4.2 Received: from localhost (unknown [94.31.100.251]) by mail.monom.org (Postfix) with ESMTPSA id A25AE500103; Thu, 27 Aug 2020 12:16:22 +0200 (CEST) Date: Thu, 27 Aug 2020 12:16:22 +0200 From: Daniel Wagner To: Sebastian Andrzej Siewior Cc: Thomas Gleixner , LKML , linux-rt-users , Steven Rostedt Subject: Re: [ANNOUNCE] v5.9-rc2-rt1 Message-ID: <20200827101622.xx4jzecouxrlwbii@beryllium.lan> References: <20200824154605.v66t2rsxobt3r5jg@linutronix.de> <20200826080802.5lnnf5wh3kcwfykz@beryllium.lan> <20200826081211.bvk5kfuzh4vlbh5k@linutronix.de> <20200826090518.m6vblobggnfdjau5@beryllium.lan> <20200826104326.xfexkwovwbi2q4el@beryllium.lan> <20200827091910.ibuyr53qprb7qmju@beryllium.lan> <20200827092743.kjl6hkaephx3a64a@linutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200827092743.kjl6hkaephx3a64a@linutronix.de> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Aug 27, 2020 at 11:27:43AM +0200, Sebastian Andrzej Siewior wrote: > So v5.9-rc2-rt1 with PREEMPT_RT=y enabled leads to the problem and > v5.9-rc2-rt1 with PREEMPT_PREEMPT=y boots fine? Yes. But it must be something with uboot related since it's not the kernel printing the error message. It's likely just an infrastructure problem on my side. Properly related to the kernel size: -rw-r--r-- 1 wagi users 31910400 Aug 26 12:54 rpi3-image-ll-v5.9-rc2-rt1-rebase-1-gdf6b97f22351 -rw-r--r-- 1 wagi users 31910400 Aug 26 12:49 rpi3-image-nohz-v5.9-rc2-rt1-rebase-1-gdf6b97f22351 -rw-r--r-- 1 wagi users 32891392 Aug 26 12:47 rpi3-image-none-v5.9-rc2-rt1-rebase-1-gdf6b97f22351 -rw-r--r-- 1 wagi users 38224384 Aug 26 12:45 rpi3-image-rt-v5.9-rc2-rt1-rebase-1-gdf6b97f22351 -rw-r--r-- 1 wagi users 31910400 Aug 26 12:54 rpi3-image-up-v5.9-rc2-rt1-rebase-1-gdf6b97f22351 -rw-r--r-- 1 wagi users 32891392 Aug 26 12:52 rpi3-image-vp-v5.9-rc2-rt1-rebase-1-gdf6b97f22351 The -rt kernel is roughly 6MB larger. Just need to check the memory ranges u-boot is using.