From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id A68AAC3DA59 for ; Mon, 22 Jul 2024 13:03:47 +0000 (UTC) Received: from list by lists.xenproject.org with outflank-mailman.761928.1171988 (Exim 4.92) (envelope-from ) id 1sVshY-0003dr-N0; Mon, 22 Jul 2024 13:03:40 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 761928.1171988; Mon, 22 Jul 2024 13:03:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1sVshY-0003dk-K7; Mon, 22 Jul 2024 13:03:40 +0000 Received: by outflank-mailman (input) for mailman id 761928; Mon, 22 Jul 2024 13:03:39 +0000 Received: from mail.xenproject.org ([104.130.215.37]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1sVshX-0003de-JI for xen-devel@lists.xenproject.org; Mon, 22 Jul 2024 13:03:39 +0000 Received: from xenbits.xenproject.org ([104.239.192.120]) by mail.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1sVshT-0006Xn-TV; Mon, 22 Jul 2024 13:03:35 +0000 Received: from lfbn-lyo-1-451-148.w2-7.abo.wanadoo.fr ([2.7.43.148] helo=l14) by xenbits.xenproject.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1sVshT-0002jl-Hm; Mon, 22 Jul 2024 13:03:35 +0000 X-BeenThere: xen-devel@lists.xenproject.org List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xenproject.org Precedence: list Sender: "Xen-devel" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=xenproject.org; s=20200302mail; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date; bh=HU/DtLBI9PeorLTyXzROt07pc9drFKDPdMTdi3WazlU=; b=6BbXYCxhWfJZ13XwlSA3f/H/VK OZaKVqddH5eqz+hb4VlX/J6j6oImhPzKusxc0OMXdCNEKhIboyM/ZmKoz5z116TyWuiCweooCBE3m 7YMCspQsMN+5/CBBktkx6YKYHxzHw3iDfRjvvMU28LthqI1jDP479KgIuHGGwsD9IZgU=; Date: Mon, 22 Jul 2024 15:03:32 +0200 From: Anthony PERARD To: Jan Beulich Cc: osstest service owner , xen-devel@lists.xenproject.org, Julien Grall , Stefano Stabellini , Volodymyr Babchuk , Bertrand Marquis , Michal Orzel Subject: Re: [linux-linus test] 186932: regressions - FAIL Message-ID: References: <39d87a30-7722-45ec-bc13-11111eb46483@suse.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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