From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Joerg Roedel <joro@8bytes.org>
Cc: Meelis Roos <mroos@linux.ee>,
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 10:52:58 -0300 [thread overview]
Message-ID: <20160713135258.GE20253@khazad-dum.debian.net> (raw)
In-Reply-To: <20160713090332.GK12639@8bytes.org>
On Wed, 13 Jul 2016, Joerg Roedel wrote:
> On Wed, Jul 13, 2016 at 11:31:02AM +0300, Meelis Roos wrote:
> > > > Bisecting kernel configs shows that it's DMAR+IOMMU. When it is
> > > > activated, there is high probability of NMI-s in random places.
> > >
> > > Hmm, strange. But nothing could really surprise when you have an HP
> > > BIOS.
> >
> > BIOS P64 01/22/2015. There seems to be a newer 2015.08.16 BIOS out but
> > the release notes only describe updated CPU microcode for security
> > reasons.
>
> It is probably something HP is selling as a "feature" and not a BIOS
> bug.
Well, based on the date, it should be the microcode-level fix for this:
https://www.blackhat.com/docs/us-15/materials/us-15-Domas-The-Memory-Sinkhole-Unleashing-An-x86-Design-Flaw-Allowing-Universal-Privilege-Escalation-wp.pdf
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2016-07-13 13:53 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 ` 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 ` Henrique de Moraes Holschuh [this message]
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=20160713135258.GE20253@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--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
all inboxes | Powered by JetHome®