From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752436AbcGMIS3 (ORCPT ); Wed, 13 Jul 2016 04:18:29 -0400 Received: from 8bytes.org ([81.169.241.247]:51514 "EHLO theia.8bytes.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751220AbcGMISX (ORCPT ); Wed, 13 Jul 2016 04:18:23 -0400 Date: Wed, 13 Jul 2016 10:18:17 +0200 From: Joerg Roedel To: Meelis Roos Cc: iommu@lists.linux-foundation.org, Linux Kernel list , David Woodhouse Subject: Re: IOMMU+DMAR causing NMIs-s (was: 4.7-rc6: NMI in intel_idle on HP Proliant G6) Message-ID: <20160713081817.GJ12639@8bytes.org> References: <5630546.0MIYeGNSYG@vostro.rjw.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 13, 2016 at 10:17:59AM +0300, Meelis Roos wrote: > Bisecting kernel configs shows that it's DMAR+IOMMU. When it is > activated, there is high probability of NMI-s in random places. Hmm, strange. But nothing could really surprise when you have an HP BIOS. Can you probably use the faulty config and bisect this down to a specific commit? In v4.7-rc1 some changes to the iova-allocation code got merged, but I have no idea how those could cause NMIs. Thanks, Joerg