linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linda Knippers <linda.knippers@hpe.com>
To: Alex Williamson <alex.williamson@redhat.com>,
	Joerg Roedel <joro@8bytes.org>
Cc: Meelis Roos <mroos@linux.ee>,
	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
Date: Wed, 13 Jul 2016 11:13:59 -0400	[thread overview]
Message-ID: <1a4c4b65-c716-08a5-af89-1b0f551024ed@hpe.com> (raw)
In-Reply-To: <20160713084830.09453584@t450s.home>



On 7/13/2016 10:48 AM, Alex Williamson wrote:
> On Wed, 13 Jul 2016 12:18:59 +0200
> Joerg Roedel <joro@8bytes.org> wrote:
> 
>> 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?
> 
> IIRC, blacklisting the hpwdt module can defuse those NMIs and might
> help us see more of the actual DMAR faults.  Blacklist in modprobe.d
> and rebuild initrd. Thanks,
> 
> Alex
> 
> PS - never assume BIOS release notes are actually complete

I agree. I'd do the BIOS update and also make sure the iLO FW is current.

-- ljk
> _______________________________________________
> iommu mailing list
> iommu@lists.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/iommu
> 

  reply	other threads:[~2016-07-13 15:48 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
2016-07-13 14:48                       ` Alex Williamson
2016-07-13 15:13                         ` Linda Knippers [this message]
2016-07-13 21:52                           ` IOMMU+DMAR causing NMIs-s 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=1a4c4b65-c716-08a5-af89-1b0f551024ed@hpe.com \
    --to=linda.knippers@hpe.com \
    --cc=alex.williamson@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.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).