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 S1751750AbcGMKTP (ORCPT <rfc822;w@1wt.eu>);
	Wed, 13 Jul 2016 06:19:15 -0400
Received: from 8bytes.org ([81.169.241.247]:52612 "EHLO theia.8bytes.org"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751082AbcGMKTC (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Wed, 13 Jul 2016 06:19:02 -0400
Date: Wed, 13 Jul 2016 12:18:59 +0200
From: Joerg Roedel <joro@8bytes.org>
To: Meelis Roos <mroos@linux.ee>
Cc: iommu@lists.linux-foundation.org,
        Linux Kernel list <linux-kernel@vger.kernel.org>,
        David Woodhouse <dwmw2@infradead.org>
Subject: Re: IOMMU+DMAR causing NMIs-s (was: 4.7-rc6: NMI in intel_idle on HP
 Proliant G6)
Message-ID: <20160713101859.GO12639@8bytes.org>
References: <alpine.LRH.2.20.1607121525060.2088@math.ut.ee>
 <5630546.0MIYeGNSYG@vostro.rjw.lan>
 <alpine.LRH.2.20.1607121654490.2088@math.ut.ee>
 <alpine.LRH.2.20.1607130855210.11080@math.ut.ee>
 <20160713081817.GJ12639@8bytes.org>
 <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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.LRH.2.20.1607131257390.20366@math.ut.ee>
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 12:58:24PM +0300, Meelis Roos wrote:
> > > 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.
> > 
> > This looks interesting. Can you please post output of 'lspci -vvv' and
> > 'lspci -t'?
> 
> Here.

Thanks. So device 00:1e.0 is a PCI-bridge which has some 32-bit
PCI-devices behind it. One of these devices tries to read address
0xb000, which is blocked by the IOMMU and causes the fault seen in the
screen-shot. The fault also causes a PCI-error which is then reported
through the NMI, causing your kernel panic.

So the 32bit PCI devices behind the bridge are:

01:03.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] ES1000 (rev 02) (prog-if 00 [VGA controller])
01:04.0 System peripheral: Compaq Computer Corporation Integrated Lights Out Controller (rev 03)
01:04.2 System peripheral: Compaq Computer Corporation Integrated Lights Out  Processor (rev 03)
01:04.4 USB controller: Hewlett-Packard Company Integrated Lights-Out Standard Virtual USB Controller (prog-if 00 [UHCI])
01:04.6 IPMI SMIC interface: Hewlett-Packard Company Integrated Lights-Out Standard KCS Interface (prog-if 01)

Can you try to disable this 'Lights Out' processor? Maybe it is causing
the issues. On the other side, the radeon driver for the ATI card is
also know for causing faults from time to time. Can you capture the
kernel messages right before a crash too?


Thanks,

	Joerg