Date: Thu, 1 Apr 2021 04:41:06 +0800 From: Ka Ho Ng <khng@FreeBSD.org> To: Oleg Ginzburg <olevole@olevole.ru> Cc: freebsd-virtualization@freebsd.org Subject: Re: recent changed in vmm lead to panic: AMD, ivhd_setup_intr Message-ID: <bbc1e069-c02a-e3e3-0fc9-e5ae1c1f8c9e@FreeBSD.org> In-Reply-To: <CAMsb%2Bmb%2BxH6k69LBC-i6v5_BhNQoM5d7fJr9XAhjfj9Xz=ko7w@mail.gmail.com> References: <CAMsb%2BmZtH3b_hhe=fmGY-1Y4Wa8Na%2BLzQy8sOhvhs1Dv9S-mzQ@mail.gmail.com> <51113310-d4f3-a38a-b3cb-bd8d55a280cc@FreeBSD.org> <CAMsb%2Bmb%2BxH6k69LBC-i6v5_BhNQoM5d7fJr9XAhjfj9Xz=ko7w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/1/21 4:36 am, Oleg Ginzburg wrote: > pci0: <base peripheral, IOMMU> at device 0.2 (no driver attached) 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. Thanks, Ka Ho
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bbc1e069-c02a-e3e3-0fc9-e5ae1c1f8c9e>