linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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)
Date: Wed, 13 Jul 2016 12:18:59 +0200	[thread overview]
Message-ID: <20160713101859.GO12639@8bytes.org> (raw)
In-Reply-To: <alpine.LRH.2.20.1607131257390.20366@math.ut.ee>

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

  reply	other threads:[~2016-07-13 10:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-12 12:05 4.7-rc6: NMI in intel_idle on HP Proliant G6 Meelis Roos
2016-07-12 12:27 ` Meelis Roos
2016-07-12 12:40   ` Rafael J. Wysocki
2016-07-12 14:22     ` Meelis Roos
2016-07-13  7:17       ` IOMMU+DMAR causing NMIs-s (was: 4.7-rc6: NMI in intel_idle on HP Proliant G6) Meelis Roos
2016-07-13  8:18         ` Joerg Roedel
2016-07-13  8:31           ` Meelis Roos
2016-07-13  9:03             ` Joerg Roedel
2016-07-13  9:16               ` Meelis Roos
2016-07-13  9:43                 ` Joerg Roedel
2016-07-13  9:40               ` Meelis Roos
2016-07-13  9:49                 ` Joerg Roedel
2016-07-13  9:58                   ` Meelis Roos
2016-07-13 10:18                     ` Joerg Roedel [this message]
2016-07-13 14:48                       ` Alex Williamson
2016-07-13 15:13                         ` IOMMU+DMAR causing NMIs-s Linda Knippers
2016-07-13 21:52                           ` Meelis Roos
2016-07-13 23:04                             ` Alex Williamson
2016-07-14  8:31                               ` Joerg Roedel
2016-08-24  8:19                               ` Meelis Roos
2016-07-13 13:52               ` IOMMU+DMAR causing NMIs-s (was: 4.7-rc6: NMI in intel_idle on HP Proliant G6) Henrique de Moraes Holschuh
2016-07-13  7:21       ` 4.7-rc6: NMI in intel_idle on HP Proliant G6 Meelis Roos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160713101859.GO12639@8bytes.org \
    --to=joro@8bytes.org \
    --cc=dwmw2@infradead.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mroos@linux.ee \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).