From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752290AbcGNIb5 (ORCPT <rfc822;w@1wt.eu>);
	Thu, 14 Jul 2016 04:31:57 -0400
Received: from 8bytes.org ([81.169.241.247]:35827 "EHLO theia.8bytes.org"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751530AbcGNIbL (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Thu, 14 Jul 2016 04:31:11 -0400
Date: Thu, 14 Jul 2016 10:31:06 +0200
From: Joerg Roedel <joro@8bytes.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Meelis Roos <mroos@linux.ee>, Linda Knippers <linda.knippers@hpe.com>,
        David Woodhouse <dwmw2@infradead.org>,
        iommu@lists.linux-foundation.org,
        Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: IOMMU+DMAR causing NMIs-s
Message-ID: <20160714083106.GQ12639@8bytes.org>
References: <alpine.LRH.2.20.1607131122010.20366@math.ut.ee>
 <20160713090332.GK12639@8bytes.org>
 <alpine.LRH.2.20.1607131239410.20366@math.ut.ee>
 <20160713094917.GM12639@8bytes.org>
 <alpine.LRH.2.20.1607131257390.20366@math.ut.ee>
 <20160713101859.GO12639@8bytes.org>
 <20160713084830.09453584@t450s.home>
 <1a4c4b65-c716-08a5-af89-1b0f551024ed@hpe.com>
 <alpine.LRH.2.20.1607132258001.30020@math.ut.ee>
 <20160713170408.6e5d2534@t450s.home>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20160713170408.6e5d2534@t450s.home>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Wed, Jul 13, 2016 at 05:04:08PM -0600, Alex Williamson wrote:
> With hpwdt disabled, can you reboot a few times and look for DMAR
> faults in the dmesg to see if they're all consistent, ie. device 1e.0
> doing a read from 0xb000?  Is there any correlation to radeon hanging
> and one of those DMAR faults appearing in the log (you can make use of
> the iLO for a serial console so you can record more of the boot than
> what can be captured on the VGA console).  Also, this should be an
> X58-based system, which reminds me of Joerg's recent commit
> a4c34ff1c029 that's intended to fix a hang on such systems.  That was
> included starting in v4.7-rc4, so if this is a new issue, testing
> before and after that commit might be relevant.  Thanks,

That commit fixed a hang while the IOMMU is being initialized. This hang
is different, as the IOMMU already runs. So I doubt that it fixes this
problem, but it is worth a test, of course.


	Joerg