Re: 13.2-RELEASE-p11 dom0 fails to boot unlike -p10

On Sat, Jun 15, 2024 at 04:58:16PM +0000, Marcin Cieslak wrote:
> (resend, wrong address)
> 
> Hello,
> 
> After upgrading 13.2-RELEASE-p10 amd64  machine to 13.2-RELEASE-p11,
> the dom0 stops booting, last lines being:
> 
> pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
> pci0: <ACPI PCI bus> on pcib0
> 
> After the pci0 the following would normally follow:
> 
> pcib1: <ACPI PCI-PCI bridge> irq 16 at device 1.0 on pci0
> pci1: <ACPI PCI bus> on pcib1
> vgapci0: <VGA-compatible display> 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.

That's weird.  8f1f4e60ceb9b8e shouldn't have anything to do with Xen.
I suspect if anything this is more likely a code generation issue with
clang/llvm, rather than source code issue.

Tested right now and the current HEAD:

ba95b4aea789 cxgbe(4): New knob to limit driver to the specified types of doorbells.

Seems to work fine for me.

A couple of things to test:

Can you check whether just re-building
f5ac4e174fdd3497749e351c27aafb34171c5730 without any reverts also
leads to a non-working kernel?

Can you boot with the following in loader.conf:

boot_verbose="YES"
xen_kernel="/boot/xen-debug"

And see if it makes any difference regarding the printed messages?

Does the box have a serial console so you can get Xen messages?

Regards, Roger.