qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: "Laurent Vivier" <lvivier@redhat.com>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Thomas Huth" <thuth@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: any remaining for-6.0 issues?
Date: Mon, 19 Apr 2021 19:02:24 +0200	[thread overview]
Message-ID: <20210419190224.33408d0e.cohuck@redhat.com> (raw)
In-Reply-To: <20210419090551.4a3ae4eb.cohuck@redhat.com>

On Mon, 19 Apr 2021 09:05:51 +0200
Cornelia Huck <cohuck@redhat.com> wrote:

> On Sun, 18 Apr 2021 11:38:09 +0100
> Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk> wrote:
> 
> > On 17/04/2021 20:46, Peter Maydell 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.)    
> > 
> > I don't think so. I tried a run with a possible candidate patch reverted (see 
> > https://lists.gnu.org/archive/html/qemu-devel/2021-04/msg02345.html) but Cornelia's 
> > response indicates that the result is still inconclusive :(  
> 
> That patch seems to be our best candidate so far, but the intermittent
> nature of the failures make it hard to pin down... I don't see anything
> obviously wrong with the patch, maybe some linux-user experts have a
> better idea?

FWIW, I tried reproducing the issue on some local systems (no luck),
and on code pushed out to gitlab (where it works most of the time, and
the user builds where it fails are unpredictable.)

I fear the best we can do right now is stare at the code and try to
figure out what might be wrong :(



  reply	other threads:[~2021-04-19 17:05 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
2021-04-18 10:38       ` Mark Cave-Ayland
2021-04-19  7:05         ` Cornelia Huck
2021-04-19 17:02           ` Cornelia Huck [this message]
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=20210419190224.33408d0e.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=lvivier@redhat.com \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=peter.maydell@linaro.org \
    --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).