From: Stefan Berger <stefanb@linux.ibm.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Eric Auger" <eric.auger@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Laurent Vivier" <lvivier@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: intermittent hang, s390x host, bios-tables-test test, TPM
Date: Wed, 11 Jan 2023 08:00:20 -0500 [thread overview]
Message-ID: <0b5e0b81-653a-9d89-a79a-278f1cc1e5c4@linux.ibm.com> (raw)
In-Reply-To: <Y7576DXofEJC24q6@redhat.com>
On 1/11/23 04:05, Daniel P. Berrangé wrote:
> On Tue, Jan 10, 2023 at 05:02:58PM -0500, Stefan Berger wrote:
>>
>>
>>>
>>> Yes, my ppc64 machine is also little endian. If the issue was not an intermittent but a permanent
>>> failure I would look for something like that. I would think it's more some sort of initialization
>>> issue, like a value on the stack that occasionally set to an undesirable value -- maybe even in a
>>> dependency.
>>
>> I found I still had access to an s390x machine. ~2700 loops on this test case
>> so far but nothing... it would be good to be able to recreate the issue and
>> apply the fix but we'll have to do it without testing then I guess.
I just stopped the tests after looping for ~37000 times. No hang here.
Stefan
next prev parent reply other threads:[~2023-01-11 13:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 12:10 intermittent hang, s390x host, bios-tables-test test, TPM Peter Maydell
2023-01-06 13:53 ` Stefan Berger
2023-01-06 14:04 ` Peter Maydell
2023-01-06 15:16 ` Stefan Berger
2023-01-06 15:39 ` Peter Maydell
2023-01-06 15:58 ` Stefan Berger
2023-01-10 19:25 ` Daniel P. Berrangé
2023-01-10 22:10 ` Peter Maydell
2023-01-10 18:50 ` Stefan Berger
2023-01-10 19:27 ` Daniel P. Berrangé
2023-01-10 19:47 ` Stefan Berger
2023-01-10 22:02 ` Stefan Berger
2023-01-11 9:05 ` Daniel P. Berrangé
2023-01-11 13:00 ` Stefan Berger [this message]
2023-01-10 19:44 ` Daniel P. Berrangé
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=0b5e0b81-653a-9d89-a79a-278f1cc1e5c4@linux.ibm.com \
--to=stefanb@linux.ibm.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=eric.auger@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).