Date: Tue, 31 Jan 2023 21:58:54 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 268486] panic: vtd_add_device: device 0 is not in scope for any DMA remapping unit Message-ID: <bug-268486-227-Yxyece8rgU@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-268486-227@https.bugs.freebsd.org/bugzilla/> References: <bug-268486-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D268486 --- Comment #7 from commit-hook@FreeBSD.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=3D53545967642d850eee4f2dd9fa27cae52= ae981b9 commit 53545967642d850eee4f2dd9fa27cae52ae981b9 Author: Eric Joyner <erj@FreeBSD.org> AuthorDate: 2023-01-30 21:34:03 +0000 Commit: Eric Joyner <erj@FreeBSD.org> CommitDate: 2023-01-31 21:57:42 +0000 vtd: Increase DRHD_MAX_UNITS Observed on a couple Ice Lake-SP platforms (Intel Coyote Pass, Dell R750), there are more than 8 DRHD sections enumerated in the DMAR ACPI section. Since the previous limit was 8, this resulted in some of these not being parsed by vtd when the iommu is initialized; in this case when PCI devices are being passthru'd to a bhyve VM. This omission later causes a kernel panic later in initialization when devices could not be found in a valid DRHD scope because the DHRD containing the device's scope was not added to vtd. Signed-off-by: Eric Joyner <erj@FreeBSD.org> PR: 268486 Sponsored by: Intel Corporation Reviewed by: rew@, corvink@ MFC after: 1 day Differential Revision: https://reviews.freebsd.org/D38285 sys/amd64/vmm/intel/vtd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-268486-227-Yxyece8rgU>