All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Cc: "Laurent Vivier" <lvivier@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Cornelia Huck" <cohuck@redhat.com>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: any remaining for-6.0 issues?
Date: Wed, 14 Apr 2021 14:48:10 +0200	[thread overview]
Message-ID: <fef000db-6562-f41c-24c0-5fb0f8fb4dd3@redhat.com> (raw)
In-Reply-To: <CAFEAcA8=qEFgvUqGFdWLJ+1ePPv2Ybisomrs2o77PyiAZA2sXg@mail.gmail.com>

On 12/04/2021 17.32, Peter Maydell wrote:
> Last call to note anything we need to fix for 6.0 on
> https://wiki.qemu.org/Planning/6.0#Known_issues please.
> The schedule is to tag rc3 tomorrow, which I would ideally like
> to be the last rc before release. After rc3 I will only be taking
> fixes for bugs which are absolutely critical...

  Hi Peter,

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?

  Thomas



  parent reply	other threads:[~2021-04-14 12:56 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 [this message]
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
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=fef000db-6562-f41c-24c0-5fb0f8fb4dd3@redhat.com \
    --to=thuth@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=cohuck@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.