From: Marc Zyngier <marc.zyngier@arm.com>
To: Mike Galbraith <efault@gmx.de>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
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: bisected - arm64 kvm unit test failures
Date: Wed, 01 Aug 2018 08:22:17 +0100 [thread overview]
Message-ID: <864lgey2ja.wl-marc.zyngier@arm.com> (raw)
In-Reply-To: <1533103345.4735.19.camel@gmx.de>
On Wed, 01 Aug 2018 07:02:25 +0100,
Mike Galbraith <efault@gmx.de> wrote:
>
> [1 <text/plain; ISO-8859-15 (7bit)>]
> On Wed, 2018-08-01 at 06:35 +0100, Marc Zyngier wrote:
> >
> > Is it something that is reproducible with the current mainline (non-RT)?
>
> These waters are a bit muddy, it's config dependent. I'm trying to
> generate a reproducing !RT config for -rc7 as we speak. If I build
> openSUSE/master-default, it does NOT reproduce. That with the bisect
> config just finished building, and.... yup, it reproduced
> (attached).
Thanks for that.
>
> Every RT tree 4.16..master.today reproduces, and is fixed up (modulo
> the RT specific failure) by reverting the fingered commit.
>
> > Pretty worrying. What HW is that on?
>
> Box is a 4 node/64 core TaiShan 2280.
Is that what is also known as D05/HIP07, with 64 Cortex-A72? If so, I
think we have one somewhere... I'll try to reproduce it once I'm back
into the office (things seem to run just fine on my A72-based laptop,
so it definitely smells of being config dependent).
Cheers,
M.
--
Jazz is not dead, it just smell funny.
next prev parent reply other threads:[~2018-08-01 7:22 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 21:57 [ANNOUNCE] v4.16.18-rt11 Sebastian Andrzej Siewior
2018-07-28 9:07 ` candidates for @devel-rt localversion-rt++ Mike Galbraith
2018-07-28 9:13 ` [rt-patch 1/3] arm64/acpi/perf: move pmu allocation to an early CPU up hook Mike Galbraith
2018-08-02 13:45 ` [rt-patch 1/3 v2] " Mike Galbraith
2018-07-29 6:55 ` candidates for @devel-rt localversion-rt++ Mike Galbraith
2018-07-29 11:47 ` Mike Galbraith
2018-07-30 16:24 ` Mike Galbraith
2018-07-31 18:28 ` bisected - arm64 kvm unit test failures Mike Galbraith
2018-08-01 5:35 ` Marc Zyngier
2018-08-01 6:02 ` Mike Galbraith
2018-08-01 7:22 ` Marc Zyngier [this message]
2018-08-01 7:48 ` Mike Galbraith
2018-08-01 9:20 ` Mike Galbraith
2018-08-21 15:34 ` Marc Zyngier
2018-08-22 13:38 ` Mike Galbraith
2018-08-22 13:50 ` Marc Zyngier
2018-08-22 13:57 ` Mike Galbraith
[not found] ` <1532764179.9882.14.camel@gmx.de>
2018-07-28 9:07 ` [rt-patch 2/3] sched: Introduce raw_cond_resched_lock() Mike Galbraith
2018-07-28 9:07 ` [rt-patch 3/3] arm, KVM: convert vgic_irq.irq_lock to raw_spinlock_t Mike Galbraith
2018-07-30 9:27 ` Peter Zijlstra
2018-07-30 13:34 ` Mike Galbraith
2018-08-02 6:56 ` [rt-patch 4/3] arm,KVM: Move phys_timer handling to hard irq context Mike Galbraith
2018-08-02 16:31 ` Steven Rostedt
2018-08-02 16:50 ` Mike Galbraith
2018-08-02 17:43 ` Mike Galbraith
2018-08-04 12:25 ` Mike Galbraith
2018-08-05 4:52 ` Mike Galbraith
2018-08-07 14:46 ` Sebastian Andrzej Siewior
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=864lgey2ja.wl-marc.zyngier@arm.com \
--to=marc.zyngier@arm.com \
--cc=bigeasy@linutronix.de \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).