Re: kern/55667: regression: XEN3_DOM0 fails to boot on

[Frank Kardel <kardel%netbsd.org@localhost>]

The following reply was made to PR kern/55667; it has been noted by GNATS.

From: Frank Kardel <kardel%netbsd.org@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: kern/55667: regression: XEN3_DOM0 fails to boot on
Date: Fri, 19 Feb 2021 11:29:07 +0100

 Now a gave it a shot at 9.99.80 XEN3_DOM0. Things have changed from
 getting stuck to panic:
 
 [   1.0000030] ixg1: clearing prefetchable bit
 [   1.0000030] xpq_flush_queue: 2 entries (0 successful) on cpu0 (0)
 [   1.0000030] panic: HYPERVISOR_mmu_update failed, ret: -22
 
 [   1.0000030] cpu0: Begin traceback...
 [   1.0000030] vpanic() at netbsd:vpanic+0x14a
 [   1.0000030] snprintf() at netbsd:snprintf
 [   1.0000030] xpq_queue_machphys_update() at 
 netbsd:xpq_queue_machphys_update
 [   1.0000030] pmap_zero_page() at netbsd:pmap_zero_page+0xe3
 [   1.0000030] uvm_pagealloc_strat() at netbsd:uvm_pagealloc_strat+0x218
 [   1.0000030] pmap_get_physpage() at netbsd:pmap_get_physpage+0x1c9
 [   1.0000030] pmap_growkernel() at netbsd:pmap_growkernel+0x1b0
 [   1.0000030] uvm_map_prepare() at netbsd:uvm_map_prepare+0x350
 [   1.0000030] uvm_map() at netbsd:uvm_map+0x6e
 [   1.0000030] uvm_km_alloc() at netbsd:uvm_km_alloc+0xfc
 [   1.0000030] x86_mem_add_mapping() at netbsd:x86_mem_add_mapping+0x98
 [   1.0000030] bus_space_map() at netbsd:bus_space_map+0x59
 [   1.0000030] ixgbe_attach() at netbsd:ixgbe_attach+0x311
 [   1.0000030] config_attach_loc() at netbsd:config_attach_loc+0x176
 [   1.0000030] pci_probe_device() at netbsd:pci_probe_device+0x582
 [   1.0000030] pci_enumerate_bus() at netbsd:pci_enumerate_bus+0x1b5
 [   1.0000030] pcirescan() at netbsd:pcirescan+0x4e
 [   1.0000030] pciattach() at netbsd:pciattach+0x186
 [   1.0000030] config_attach_loc() at netbsd:config_attach_loc+0x176
 [   1.0000030] ppbattach() at netbsd:ppbattach+0x1c5
 [   1.0000030] config_attach_loc() at netbsd:config_attach_loc+0x176
 [   1.0000030] pci_probe_device() at netbsd:pci_probe_device+0x582
 [   1.0000030] pci_enumerate_bus() at netbsd:pci_enumerate_bus+0x1b5
 [   1.0000030] pcirescan() at netbsd:pcirescan+0x4e
 [   1.0000030] pciattach() at netbsd:pciattach+0x186
 [   1.0000030] config_attach_loc() at netbsd:config_attach_loc+0x176
 [   1.0000030] mp_pci_scan() at netbsd:mp_pci_scan+0x9e
 [   1.0000030] hypervisor_attach() at netbsd:hypervisor_attach+0x3f0
 [   1.0000030] config_attach_loc() at netbsd:config_attach_loc+0x176
 [   1.0000030] xen_mainbus_attach() at netbsd:xen_mainbus_attach+0x53
 [   1.0000030] mainbus_attach() at netbsd:mainbus_attach+0x4a
 [   1.0000030] config_attach_loc() at netbsd:config_attach_loc+0x176
 [   1.0000030] cpu_configure() at netbsd:cpu_configure+0x25
 [   1.0000030] main() at netbsd:main+0x32c
 [   1.0000030] cpu0: End traceback...
 [   1.0000030] fatal breakpoint trap in supervisor mode
 [   1.0000030] trap type 1 code 0 rip 0xffffffff8023e93d cs 0xe030 
 rflags 0x202 cr2 0 ilevel 0x8 rsp 0xffffffff8316be50
 [   1.0000030] curlwp 0xffffffff80e48340 pid 0.0 lowest kstack 
 0xffffffff831682c0
 Stopped in pid 0.0 (system) at  netbsd:breakpoint+0x5:  leave
 
 panic stack traces are like the above in different path sof autoconf. I 
 saw also panics in
 acpi device configuration.
 The panic is always panic: HYPERVISOR_mmu_update failed, ret: -22.