From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 8D29C139694 for ; Mon, 15 May 2017 19:47:35 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D5313E0C94; Mon, 15 May 2017 19:47:26 +0000 (UTC) Received: from mail-it0-x235.google.com (mail-it0-x235.google.com [IPv6:2607:f8b0:4001:c0b::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 869AAE0C52 for ; Mon, 15 May 2017 19:47:26 +0000 (UTC) Received: by mail-it0-x235.google.com with SMTP id c15so49805409ith.0 for ; Mon, 15 May 2017 12:47:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=mZS6vOcxJuUVXn23eVu7hFpj+OiT8vROO85oek+WFUE=; b=Cl+vywRbO8cFpCbCuvmARz5ulandf7YWdefjtmJ0JSmkNuf6aIJPHdsNhS2bwxXioa ibkYm5HBEBZUsa3DvXaMDmG40nUlxHFoHzEpzaosU4G55I+JS4l07GF/PMAxKkHTXy7k SJ2Y06S3OLmXE0x83/pwW7E780rT2Y6vuoGrHd89X7HUnXhB8OB7Lgj3n4VBi0g5z3JF iHhLXUze2Cyee6dSnQ/rmWfglc+jwP0bGjN8XlAwaRM7tdMR4AKhlL4V6XHQxT98034u 9rbJME8L3a+d0/kuBJVM/GVrFGFmImMEaMbbZ82hngUCv8VCgVQB+Qc38BGLcuRUNzl0 enyg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=mZS6vOcxJuUVXn23eVu7hFpj+OiT8vROO85oek+WFUE=; b=thhvjTZibculP8LS0h0x66bj2QncNkD4kt0R+STBaluWQHSNcvjI0U2ehZ2qUYqibo BoODeVlkVbmWRUy7UoMcRDsc7Igx307bI5o7ywLjnnWk9jWDziRUScLg/yV26Ys0m9IW 93r3b1vj9NETE1XJNOSkWd42zBLZRJwn1hGjUjsLVIGLbI86WqTM7fFDBZ4L0G6l423H PSPtjoPZVp6JOjBEuyPrT/BNC19jSH3cCZ2gWwfchMKb5FJahEh0REJlR7rSB7Fs8Ag7 2VOMoFEqPai03gDfEUb1Uv0GCMun4dvIFoCpKHbCi7zYq8wniUKgxCZvS12PFvYC/ac1 +01Q== X-Gm-Message-State: AODbwcAYRNEmmAuLztxza+S2I2NSoZOJWk/Ja5i+0qLtbY/pETPPVr4f 58DX0dzfy9xkvxR5oKLH1fs0HvjFD0oZ X-Received: by 10.36.104.72 with SMTP id v69mr7101815itb.27.1494877645624; Mon, 15 May 2017 12:47:25 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.36.230.194 with HTTP; Mon, 15 May 2017 12:47:25 -0700 (PDT) In-Reply-To: References: From: R0b0t1 Date: Mon, 15 May 2017 14:47:25 -0500 Message-ID: Subject: Re: [gentoo-user] Issues with AMD_IOMMU To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset="UTF-8" X-Archives-Salt: aab0bb38-798f-4cbf-a89d-d1ed84559ea0 X-Archives-Hash: b1c695686751cf44272ce39bb43e4d24 On Sun, May 14, 2017 at 12:31 AM, Adam Carter wrote: > Tried kernels 4.10.13 and 4.11, with > CONFIG_GART_IOMMU=y > CONFIG_IOMMU_HELPER=y > CONFIG_IOMMU_API=y > CONFIG_IOMMU_SUPPORT=y > CONFIG_IOMMU_IOVA=y > CONFIG_AMD_IOMMU=y > CONFIG_AMD_IOMMU_V2=m > Chipset is 990FX, and AFAICT the V2 is for the APU (bdver3 and 4 vintage). > > When I enable the IOMMU in the BIOS I get stack traces. Is anyone using > AMD_IOMMU successfully? If so, any tips? I don't mean to suggest the problem is intractable, but on fairly new hardware (i7-4770K, MSI Z87-G45) there has been a regression in the kernel's nested KVM support that makes me view VT-x/AMD-V VT-d/AMD-Vi with a great deal of suspicion. In any case, devices are liable to just spontaneously not work, even if the hardware reports it has been properly initialized. This may require changes to the kernel and the information needed to make those changes may or may not be available.