All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Ian Jackson <ian.jackson@citrix.com>
Cc: Juergen Gross <jgross@suse.com>,
	Andrew Cooper <Andrew.Cooper3@citrix.com>,
	George Dunlap <George.Dunlap@citrix.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [Xen-devel] debina hang after "random: crng init done"
Date: Fri, 6 Dec 2019 17:57:40 +0100	[thread overview]
Message-ID: <23d38b1b-291b-4abb-07b5-66b982e758dd@suse.com> (raw)
In-Reply-To: <24042.34572.522244.289318@mariner.uk.xensource.com>

On 06.12.2019 17:51, Ian Jackson wrote:
> Ian Jackson writes ("Re: [Xen-devel] [xen-unstable test] 144289: tolerable FAIL"):
>> Jan Beulich writes ("Re: [Xen-devel] [xen-unstable test] 144289: tolerable FAIL"):
>>> On 25.11.2019 14:58, osstest service owner wrote:
>> ...
>>>>  test-amd64-amd64-libvirt-xsm  7 xen-boot                   fail pass in 144283
>>>
>>> Other than the shell prompt not appearing, I can't see any
>>> indication of what may have gone wrong here for which reason.
>>
>> The last message printed was
>>   random: crng init done
>>
>> This seemed familiar.  Searching my email found
>>
>>   osstest service owner writes ("[osstest test] 143493: regressions - FAIL"):
>>   > flight 143493 osstest real [real]
>>   > http://logs.test-lab.xenproject.org/osstest/logs/143493/
>>   > 
>>   > Regressions :-(
>>   > 
>>   > Tests which did not succeed and are blocking,
>>   > including tests which could not be run:
>>   >  test-amd64-amd64-pair        10 xen-boot/src_host        fail REGR. vs. 143392
>>
>>   I don't know what this is.  Linux fails to boot under Xen.  The last
>>   message is
>>     random: crng init done
>>   But it doesn't seem at all probable that this is anything to do
>>   with osstest.
>>
>> That was with debina1.
>>
>> So either both these hosts have a similar hardware fault, or there is
>> something else wrong.
> 
> Hi.  Is it possible that some x86 or kernel expert could help to
> investigate this ?

For kernel I guess you meant to Cc Boris and Jürgen, not so much
Konrad?

> I have a repro with Debian buster, too, here:
>   http://logs.test-lab.xenproject.org/osstest/logs/144312/test-amd64-i386-xl-raw/info.html

Does "repro" mean you're able to reliable trigger this? I ask
because so far, with all branches affected afaict, it looked
pretty sporadic.

Jan

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2019-12-06 16:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-25 13:58 [Xen-devel] [xen-unstable test] 144289: tolerable FAIL osstest service owner
2019-11-25 14:05 ` Jan Beulich
2019-11-25 14:58   ` Ian Jackson
2019-12-06 16:51     ` [Xen-devel] debina hang after "random: crng init done" Ian Jackson
2019-12-06 16:57       ` Jan Beulich [this message]
2019-12-06 18:09         ` Ian Jackson
2019-12-06 23:58         ` Boris Ostrovsky

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=23d38b1b-291b-4abb-07b5-66b982e758dd@suse.com \
    --to=jbeulich@suse.com \
    --cc=Andrew.Cooper3@citrix.com \
    --cc=George.Dunlap@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=ian.jackson@citrix.com \
    --cc=jgross@suse.com \
    --cc=roger.pau@citrix.com \
    --cc=xen-devel@lists.xenproject.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.