Date: Thu, 1 Apr 2021 06:18:34 +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: <a5857e91-854c-d385-4db3-11fc591d254d@FreeBSD.org> In-Reply-To: <9b8652d4-d5a1-589f-c4ec-21908356315c@FreeBSD.org> 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> <bbc1e069-c02a-e3e3-0fc9-e5ae1c1f8c9e@FreeBSD.org> <688df763-38bd-8eb9-4a71-961b3e48d5f2@freebsd.org> <9b8652d4-d5a1-589f-c4ec-21908356315c@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/1/21 5:27 am, Ka Ho Ng wrote: > 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) >>> >>> 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 >> >> 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-unsubscribe@freebsd.org" > > Could you try the attached quick dirty fix and see if it works? > > Ka Ho For your reference, here is the differential: https://reviews.freebsd.org/D29521 Best, Ka Ho
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a5857e91-854c-d385-4db3-11fc591d254d>