From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752649AbcGMI3G (ORCPT ); Wed, 13 Jul 2016 04:29:06 -0400 Received: from smtp1.it.da.ut.ee ([193.40.5.66]:44303 "EHLO smtp1.it.da.ut.ee" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750883AbcGMI3C (ORCPT ); Wed, 13 Jul 2016 04:29:02 -0400 Date: Wed, 13 Jul 2016 11:31:02 +0300 (EEST) From: Meelis Roos To: Joerg Roedel 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) In-Reply-To: <20160713081817.GJ12639@8bytes.org> Message-ID: References: <5630546.0MIYeGNSYG@vostro.rjw.lan> <20160713081817.GJ12639@8bytes.org> User-Agent: Alpine 2.20 (LRH 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > 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. BIOS P64 01/22/2015. There seems to be a newer 2015.08.16 BIOS out but the release notes only describe updated CPU microcode for security reasons. > 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. Will try but I do not know a working base yet - this was broken in both 4.6 and 4.7-rc. -- Meelis Roos (mroos@linux.ee)