[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200422183112.nfbxob7gv33fsqgp@beryllium.lan>
Date: Wed, 22 Apr 2020 20:31:12 +0200
From: Daniel Wagner <wagi@...om.org>
To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc: Thomas Gleixner <tglx@...utronix.de>,
LKML <linux-kernel@...r.kernel.org>,
linux-rt-users <linux-rt-users@...r.kernel.org>,
Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [ANNOUNCE] v5.6.4-rt3
On Wed, Apr 22, 2020 at 08:12:32PM +0200, Sebastian Andrzej Siewior wrote:
> 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)?
Correct, all tests pass and from a quick glance there are no backtraces in the
logs. IIRC, lava detects warnings and backtraces in the logs and marks them as
error.
v5.6.4-rt seems to be in a good shape as far my quick tests tell me.
Powered by blists - more mailing lists