qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: "Laurent Vivier" <lvivier@redhat.com>,
	"Thomas Huth" <thuth@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Cornelia Huck" <cohuck@redhat.com>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: any remaining for-6.0 issues?
Date: Sat, 17 Apr 2021 20:46:24 +0100	[thread overview]
Message-ID: <CAFEAcA9Q7q5eoE+qBOY9LYQnnaccSfMux=fOzb3+BtRWjXm6gw@mail.gmail.com> (raw)
In-Reply-To: <c63bbf7e-2230-44b2-7671-086c7dacd787@ilande.co.uk>

On Wed, 14 Apr 2021 at 14:58, Mark Cave-Ayland
<mark.cave-ayland@ilande.co.uk> wrote:
>
> On 14/04/2021 13:48, Thomas Huth wrote:
> > I've seen some intermittend, non-reproducible crashes with usermode QEMU in some of
> > my CI runs, e.g.:
> >
> > https://gitlab.com/thuth/qemu/-/jobs/1178256498#L3876
> >
> > https://gitlab.com/thuth/qemu/-/jobs/1146276208#L3241
> >
> > This was only with ccache enabled, so I thought that it might be related to my
> > work-in-progress ccache patches...
> >
> > ... but now Cornelia reported that she has seen such a crash in one of her branches,
> > too (which is completely unrelated to my ccache patches):
> >
> > https://gitlab.com/cohuck/qemu/-/jobs/1178860927#L3867
> >
> > That makes me wonder whether we currently have a real problem with user-mode in the
> > master branch? Did anybody else see such problems?
>
> I've definitely seen the same issue as Cornelia in my Gitlab CI builds for the ESP
> security fixes (first version of which appeared just before rc0). The user builds
> always fail on "run-tcg-tests-s390x-linux-user" for me.

Do we have any better understanding yet of the cause here?
(I ask because I think we're going to need an rc4 for other reasons,
so if there's a ready-to-go fix then we could consider it.)

thanks
-- PMM


  parent reply	other threads:[~2021-04-17 19:49 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-12 15:32 any remaining for-6.0 issues? Peter Maydell
2021-04-12 18:44 ` Mark Cave-Ayland
2021-04-12 19:40   ` Peter Maydell
2021-04-12 21:13     ` Mark Cave-Ayland
2021-04-12 22:19     ` Mark Cave-Ayland
2021-04-13  4:38 ` Markus Armbruster
2021-04-13  5:56 ` Bin Meng
2021-04-13  6:19   ` Stefan Weil
2021-04-14  8:30     ` Bin Meng
2021-04-14  9:18       ` Stefan Weil
2021-04-14  9:34       ` Peter Maydell
2021-04-14 12:57         ` Bin Meng
2021-04-14 12:48 ` Thomas Huth
2021-04-14 13:57   ` Mark Cave-Ayland
2021-04-14 14:15     ` Mark Cave-Ayland
2021-04-14 14:36       ` Cornelia Huck
2021-04-14 16:26         ` Mark Cave-Ayland
2021-04-17 19:46     ` Peter Maydell [this message]
2021-04-18 10:38       ` Mark Cave-Ayland
2021-04-19  7:05         ` Cornelia Huck
2021-04-19 17:02           ` Cornelia Huck
2021-04-19 19:38             ` Mark Cave-Ayland
2021-04-20  9:58               ` Cornelia Huck

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='CAFEAcA9Q7q5eoE+qBOY9LYQnnaccSfMux=fOzb3+BtRWjXm6gw@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=cohuck@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=thuth@redhat.com \
    /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).