Re: recent changed in vmm lead to panic: AMD, ivhd_setup_intr

[Ka Ho Ng]

On 4/1/21 4:43 am, Ka Ho Ng wrote:

On 4/1/21 4:41 am, Ka Ho Ng wrote:

On 4/1/21 4:36 am, Oleg Ginzburg wrote:

pci0: <base peripheral, IOMMU> at device 0.2 (no driver attached)

Thanks,
Ka Ho

That is the most related cause to the panic. Currently the code assumes evaluating a propagated ACPI ivrs table will come with attached amd iommu devices as well.

Forgot to mention, /usr/local/bin/acpidump comes from
sysutils/acpica-tools.

Ka Ho
_______________________________________________
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization

To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"

Could you try the attached quick dirty fix and see if it works?

Ka Ho

diff --git a/sys/amd64/vmm/amd/ivrs_drv.c b/sys/amd64/vmm/amd/ivrs_drv.c
index 6291895c212f..d2e3d0b0acdb 100644
--- a/sys/amd64/vmm/amd/ivrs_drv.c
+++ b/sys/amd64/vmm/amd/ivrs_drv.c
@@ -122,7 +122,6 @@ ivrs_is_ivhd(UINT8 type)
        switch(type) {
        case IVRS_TYPE_HARDWARE_LEGACY:
        case IVRS_TYPE_HARDWARE_EFR:
-       case IVRS_TYPE_HARDWARE_MIXED:
                return (true);
 
        default:

OpenPGP_signature
Description: OpenPGP digital signature