From: Anthony PERARD <anthony@xenproject.org>
To: Jan Beulich <jbeulich@suse.com>
Cc: osstest service owner <osstest-admin@xenproject.org>,
xen-devel@lists.xenproject.org, Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Volodymyr Babchuk <volodymyr_babchuk@epam.com>,
Bertrand Marquis <bertrand.marquis@arm.com>,
Michal Orzel <michal.orzel@amd.com>
Subject: Re: [linux-linus test] 186932: regressions - FAIL
Date: Mon, 22 Jul 2024 15:03:32 +0200 [thread overview]
Message-ID: <Zp5YpOt42lATLwQX@l14> (raw)
In-Reply-To: <39d87a30-7722-45ec-bc13-11111eb46483@suse.com>
On Mon, Jul 22, 2024 at 09:05:43AM +0200, Jan Beulich wrote:
> On 22.07.2024 06:56, osstest service owner wrote:
> > flight 186932 linux-linus real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/186932/
> >
> > Regressions :-(
> >
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> > test-arm64-arm64-examine 8 reboot fail REGR. vs. 186827
> > test-arm64-arm64-xl 8 xen-boot fail REGR. vs. 186827
>
> There looks to be a basic problem as of flight 186925, yet a brief look at one
> of the logs doesn't really give any hint other than the system perhaps simply
> being slow. Ideas, anyone?
Well, yes, it's really slow to reach having a running ssh server. If I
let the machine boot, there's two reason in the log for the long time:
Jul 22 11:44:25.216867 Waiting for /dev to be fully populated...Timed out for waiting the udev queue being empty.
Jul 22 11:46:25.469002 done (timeout).
Jul 22 11:46:29.103350 Configuring network interfaces...
Jul 22 11:46:32.127350 ^@Timed out for waiting the udev queue being empty.
Jul 22 11:48:29.256918 [ 403.298102] NET: Registered PF_INET6 protocol family
... more network kernel info after that.
Jul 22 11:48:33.204921 Waiting for xenbr0 to get ready (MAXWAIT is 2 seconds).
Jul 22 11:48:33.204984 done.
(on previous run, "configuring network interface" is followed by
"waiting for xenbr0")
So, we lost already 4 min waiting, out of a budget of 7min for full
reboot.
Also, "reboot" doesn't work with this newer kernel, the machine prints
"Will now restart." then nothing happen.
I have also try without Xen, it's the same behavior.
Cheers,
--
Anthony PERARD
next prev parent reply other threads:[~2024-07-22 13:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-22 4:56 [linux-linus test] 186932: regressions - FAIL osstest service owner
2024-07-22 7:05 ` Jan Beulich
2024-07-22 13:03 ` Anthony PERARD [this message]
2024-07-22 13:06 ` Jan Beulich
2024-07-22 13:41 ` Anthony PERARD
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=Zp5YpOt42lATLwQX@l14 \
--to=anthony@xenproject.org \
--cc=bertrand.marquis@arm.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=osstest-admin@xenproject.org \
--cc=sstabellini@kernel.org \
--cc=volodymyr_babchuk@epam.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.