From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751476AbcGMJiw (ORCPT ); Wed, 13 Jul 2016 05:38:52 -0400 Received: from smtp1.it.da.ut.ee ([193.40.5.66]:37262 "EHLO smtp1.it.da.ut.ee" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750739AbcGMJio (ORCPT ); Wed, 13 Jul 2016 05:38:44 -0400 Date: Wed, 13 Jul 2016 12:40:39 +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: <20160713090332.GK12639@8bytes.org> Message-ID: References: <5630546.0MIYeGNSYG@vostro.rjw.lan> <20160713081817.GJ12639@8bytes.org> <20160713090332.GK12639@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 > > > 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. > > Oh, in that case it is not related to the recent iova changes. Does the > box have any hardware error log which you can access and send to us > (right after some NMIs happened)? Just got http://kodu.ut.ee/~mroos/4.6-dmar-fault2.png when playing with BIOS settings (disabling NUMA). It is the first time I see at least some info in NMI decode. -- Meelis Roos (mroos@linux.ee)