From nobody Mon Jun 17 15:17:52 2024 X-Original-To: xen@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4W2tmg0gSFz5P3rL for ; Mon, 17 Jun 2024 15:17:55 +0000 (UTC) (envelope-from kevans@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4W2tmf5phwz52LB; Mon, 17 Jun 2024 15:17:54 +0000 (UTC) (envelope-from kevans@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1718637474; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=UMtZC0CjiTK7DC9XTezfnQg6Cmvs/2WbjLUrhetfgqw=; b=uUvwSosX4Afn1HzmKu6Pf7HqYSJWcUdkcCG3ti/NMu3goRyN6ed4RfcwHAzMxnfVZxTZdZ GChcdSHdAuyG7ziOJbpstj8+IRLY89IfdYm5ax9v1O//iKufIG4kk4PdOQ0RPNdE4ahP+p VP0sYyTbzobT1BNZAKKon2Z1tuj2ATBLxwgUyDTo+KK+rhg93ddz9brfspGR/7Ao3cwHzv A1Kb+2i115y+wvob7IK7ZnvQY1Y1Y+bTHrj1eS5xJgx2LkhPV+pvZ4xVfbbZ4MgyMhnFGB G1lA/U4ZkaxmRWFDNjPGK05wRpwcUEJaEdjHNkmKa5IviTQeL6Mn6Lk4SCFGeQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1718637474; a=rsa-sha256; cv=none; b=eAxDOPSauMqpbUptTmGCG4Wp+VRqJVLYM7osBG5Ql/L3FQNyBzbGb5bxeYNbDH70459uu0 fJEbYZA8LnY1PhJ7jhhUyzeNfYAoLGuOqh9V0RQa702pQmAQSW85K2y39gKCKRBCoyWuEw lS2JC4Dd/suQ8TbzU0mqP2OFb72bioFvIAFH9mrhQ7cpfbP5EduY+6MrMkOVtJbbyTMrJV ef2qn+EpDTMIAoJoYSzjnMYc7nrQsvvAUm2UO3oVWDLi5CCaF6Mt1iShE32+gUDu+N9OR7 j1snRK5Q0Vc3oKdr+WfT24ckLZT30Q5reWDtB+oVmE4seQdkrY9fV/HCDvl31w== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1718637474; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=UMtZC0CjiTK7DC9XTezfnQg6Cmvs/2WbjLUrhetfgqw=; b=CXhxYuaCerOiSkJAcRKx0nXO37okB+jhoRok72/aKO6tytOBhjZFCy5WKfPr0NAvcHtDLR 83ILgyqboWRC5tf9Gd24Qu7FKP4biFE5d71w4iPvJ2B25zJ+S7Q/NCbqkC1e3hUbRdX4vY abrllEo3LyZ0cLkWW7BdVcZNZB4AIj1dkTojv7ccW5NsHOVJqVNh2WBb50oVY6hO5Mtf4j baWfarW1YVXcd0WJZx4pHRFNmaiS6E0Y36rGweT6E1DflJAdQUKZ2W3HfKB9Cs0EhIX85I NOQwa+lHmQpjw3lZamfyebGVsGi/shygF2PVxaKUnmP4pxdlsaZMhWzKS3c0rw== Received: from [10.9.4.95] (unknown [209.182.120.176]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: kevans/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4W2tmf3DBSzRQL; Mon, 17 Jun 2024 15:17:54 +0000 (UTC) (envelope-from kevans@FreeBSD.org) Message-ID: <102314ab-334c-4652-aa9b-d155c49fd186@FreeBSD.org> Date: Mon, 17 Jun 2024 10:17:52 -0500 List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-xen List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-xen@freebsd.org Sender: owner-freebsd-xen@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: 13.2-RELEASE-p11 dom0 fails to boot unlike -p10 To: Marcin Cieslak , xen@freebsd.org References: Content-Language: en-US Cc: cperciva@FreeBSD.org From: Kyle Evans In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 6/15/24 11:24, Marcin Cieslak wrote: > Hello, > > After upgrading 13.2-RELEASE-p10 amd64  machine to 13.2-RELEASE-p11, > the dom0 stops booting, last lines being: > > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > > (see screenshot) > > After the pci0 the following would normally follow: > > pcib1: irq 16 at device 1.0 on pci0 > pci1: on pcib1 > vgapci0: port 0xf000-0xf03f mem > 0xf7800000-0xf7bfffff,0xe0000000-0xefffffff irq 16 at device 2.0 on pci0 > vgapci0: Boot video device > > > GENERIC kernel. > Xen version used: > > # pkg -c /mnt info -x xen > edk2-xen-x64-g202308_4 > xen-kernel-4.18.2.20240411 > xen-tools-4.18.2.20240411_1 > > xen 4.18.0 also didn't boot. > > I realized that reverting 8f1f4e60ceb9b8e5eddd54cf1fde62944f56eaa4 > fixes the issue. > > I am a bit puzzled, since I don't even load if_wg, but > checking out f5ac4e174fdd3497749e351c27aafb34171c5730 > and reverting 8f1f4e60 helped. > There's 0% chance of that change directly causing this, especially if you don't even load the module or build it into your kernel. Even if you did, this is too early for tunnels to be constructed and pass traffic which would certainly be a prerequisite. > Reverting f3195cc08ccc99365ec00900a3c1abc59ceefc9c alone didn't fix > it (I tried this first). > > What's going on..? > I would rather suspect that for some reason or another your kernel is linking in a different order between the two builds and you're getting really unlucky (e.g., maybe there's a pair of sysinits that, when flipped, are causing this). CC'ing cperciva@ because he's done more recent work with sysinit reordering (though I don't think anything that landed in 13.x) in case this particular case rings a bell. > Marcin Thanks, Kyle Evans