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
On Tue, Jan 10, 2023 at 05:02:58PM -0500, Stefan Berger wrote:
>
>
> On 1/10/23 14:47, Stefan Berger wrote:
> >
> >
> > On 1/10/23 14:27, Daniel P. Berrangé wrote:
> > > On Tue, Jan 10, 2023 at 01:50:26PM -0500, Stefan Berger wrote:
> > > >
> > > >
> > > > On 1/6/23 10:16, Stefan Berger wrote
On Tue, 10 Jan 2023 at 19:25, Daniel P. Berrangé wrote:
>
> On Fri, Jan 06, 2023 at 03:39:31PM +, Peter Maydell wrote:
> > Yeah. It would be good if we didn't deadlock without printing
> > the assertion, though...
> >
> > I guess we could improve qtest_kill_qemu() so it doesn't wait
> > indefi
On 1/10/23 14:47, Stefan Berger wrote:
On 1/10/23 14:27, Daniel P. Berrangé wrote:
On Tue, Jan 10, 2023 at 01:50:26PM -0500, Stefan Berger wrote:
On 1/6/23 10:16, Stefan Berger wrote:
This here seems to be the root cause. An unknown control channel
command was received from the TPM emul
On 1/10/23 14:27, Daniel P. Berrangé wrote:
On Tue, Jan 10, 2023 at 01:50:26PM -0500, Stefan Berger wrote:
On 1/6/23 10:16, Stefan Berger wrote:
This here seems to be the root cause. An unknown control channel
command was received from the TPM emulator backend by the control channel
threa
On Fri, Jan 06, 2023 at 10:16:36AM -0500, Stefan Berger wrote:
>
>
> On 1/6/23 07:10, Peter Maydell wrote:
> > I'm seeing an intermittent hang on the s390 CI runner in the
> > bios-tables-test test. It looks like we've deadlocked because:
> >
> > * the TPM device is waiting for data on its soc
On Fri, Jan 06, 2023 at 03:39:31PM +, Peter Maydell wrote:
> On Fri, 6 Jan 2023 at 15:16, Stefan Berger wrote:
> >
> >
> >
> > On 1/6/23 07:10, Peter Maydell wrote:
> > > I'm seeing an intermittent hang on the s390 CI runner in the
> > > bios-tables-test test. It looks like we've deadlocked be
On Tue, Jan 10, 2023 at 01:50:26PM -0500, Stefan Berger wrote:
>
>
> On 1/6/23 10:16, Stefan Berger wrote:
>> This here seems to be the root cause. An unknown control channel
>> command was received from the TPM emulator backend by the control channel
>> thread and we end up in g_assert_not_reac
On 1/6/23 10:16, Stefan Berger wrote:
On 1/6/23 07:10, Peter Maydell wrote:
I'm seeing an intermittent hang on the s390 CI runner in the
bios-tables-test test. It looks like we've deadlocked because:
* the TPM device is waiting for data on its socket that never arrives,
and it's hold
On 1/6/23 10:39, Peter Maydell wrote:
On Fri, 6 Jan 2023 at 15:16, Stefan Berger wrote:
On 1/6/23 07:10, Peter Maydell wrote:
I'm seeing an intermittent hang on the s390 CI runner in the
bios-tables-test test. It looks like we've deadlocked because:
Thread 3 (Thread 0x3ff8dafe900 (
On Fri, 6 Jan 2023 at 15:16, Stefan Berger wrote:
>
>
>
> On 1/6/23 07:10, Peter Maydell wrote:
> > I'm seeing an intermittent hang on the s390 CI runner in the
> > bios-tables-test test. It looks like we've deadlocked because:
> >
> > * the TPM device is waiting for data on its socket that neve
On 1/6/23 07:10, Peter Maydell wrote:
I'm seeing an intermittent hang on the s390 CI runner in the
bios-tables-test test. It looks like we've deadlocked because:
* the TPM device is waiting for data on its socket that never arrives,
and it's holding the iothread lock
* QEMU is therefo
On Fri, 6 Jan 2023 at 13:53, Stefan Berger wrote:
>
>
>
> On 1/6/23 07:10, Peter Maydell wrote:
> > I'm seeing an intermittent hang on the s390 CI runner in the
> Is this a new hang or has this been occurring for a while? I am asking
> because the test case is not new.
It's intermittent, so no i
On 1/6/23 07:10, Peter Maydell wrote:
I'm seeing an intermittent hang on the s390 CI runner in the
Is this a new hang or has this been occurring for a while? I am asking because
the test case is not new.
Stefan
14 matches
Mail list logo
