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;
Date:   Wed, 22 Apr 2020 20:12:32 +0200
From:   Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To:     Daniel Wagner <wagi@monom.org>
Cc:     Thomas Gleixner <tglx@linutronix.de>,
        LKML <linux-kernel@vger.kernel.org>,
        linux-rt-users <linux-rt-users@vger.kernel.org>,
        Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [ANNOUNCE] v5.6.4-rt3
Message-ID: <20200422181232.a33sfm6udmy2zcvy@linutronix.de>
References: <20200416164510.kbrklqahdng5uhij@linutronix.de>
 <20200422173359.inlikfugjzsjyyp6@beryllium.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20200422173359.inlikfugjzsjyyp6@beryllium.lan>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On 2020-04-22 19:33:59 [+0200], Daniel Wagner wrote:
> Hi Sebastian,

Hi Daniel,

> On Thu, Apr 16, 2020 at 06:45:10PM +0200, Sebastian Andrzej Siewior wrote:
> > I'm pleased to announce the v5.6.4-rt3 patch set.
> 
> Finally solved my lab setup issue (NFS wants to use TCP per default now) and
> all looks good. The fallout on rt-tests-migrate was a configuration bug on my
> side. All rt-tests work and pass on my three system (Beaglebone Black 32bit,
> RPi3 64bit and old x86_64 Core2 Duo CPU E8400 box in 64bit mode).

So there is no backtrace of any kind in any configuration (bug or no
bug)?

> The only thing I've observed was higher latency numbers in sigwaittest but
> that could be anything.
> 
> Thanks,
> Daniel

Sebastian