From owner-freebsd-virtualization@freebsd.org Wed Mar 31 20:41:09 2021 Return-Path: Delivered-To: freebsd-virtualization@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 36DCB5AFD61 for ; Wed, 31 Mar 2021 20:41:09 +0000 (UTC) (envelope-from khng@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F9dWT1Bhgz4cQx; Wed, 31 Mar 2021 20:41:09 +0000 (UTC) (envelope-from khng@FreeBSD.org) Received: from Kas-MacBook-Pro.lan (unknown [IPv6:2001:470:f816:0:f523:df21:9e7f:8cba]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: khng/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 6EE79C02C; Wed, 31 Mar 2021 20:41:08 +0000 (UTC) (envelope-from khng@FreeBSD.org) Subject: Re: recent changed in vmm lead to panic: AMD, ivhd_setup_intr To: Oleg Ginzburg Cc: freebsd-virtualization@freebsd.org References: <51113310-d4f3-a38a-b3cb-bd8d55a280cc@FreeBSD.org> From: Ka Ho Ng Message-ID: Date: Thu, 1 Apr 2021 04:41:06 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Mar 2021 20:41:09 -0000 On 4/1/21 4:36 am, Oleg Ginzburg wrote: > pci0: 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