From: Meelis Roos <mroos-Y27EyoLml9s@public.gmane.org>
To: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
Linux Kernel list
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 11:31:02 +0300 (EEST) [thread overview]
Message-ID: <alpine.LRH.2.20.1607131122010.20366@math.ut.ee> (raw)
In-Reply-To: <20160713081817.GJ12639-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
> > 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.
> Can you probably use the faulty config and bisect this down to a
> specific commit? In v4.7-rc1 some changes to the iova-allocation code
> got merged, but I have no idea how those could cause NMIs.
Will try but I do not know a working base yet - this was broken in both
4.6 and 4.7-rc.
--
Meelis Roos (mroos-Y27EyoLml9s@public.gmane.org)
WARNING: multiple messages have this Message-ID (diff)
From: Meelis Roos <mroos@linux.ee>
To: Joerg Roedel <joro@8bytes.org>
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 11:31:02 +0300 (EEST) [thread overview]
Message-ID: <alpine.LRH.2.20.1607131122010.20366@math.ut.ee> (raw)
In-Reply-To: <20160713081817.GJ12639@8bytes.org>
> > 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.
> Can you probably use the faulty config and bisect this down to a
> specific commit? In v4.7-rc1 some changes to the iova-allocation code
> got merged, but I have no idea how those could cause NMIs.
Will try but I do not know a working base yet - this was broken in both
4.6 and 4.7-rc.
--
Meelis Roos (mroos@linux.ee)
next prev parent reply other threads:[~2016-07-13 8:31 UTC|newest]
Thread overview: 37+ 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
[not found] ` <alpine.LRH.2.20.1607130855210.11080-ptEonEWSGqKptlylMvRsHA@public.gmane.org>
2016-07-13 8:18 ` Joerg Roedel
2016-07-13 8:18 ` Joerg Roedel
[not found] ` <20160713081817.GJ12639-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2016-07-13 8:31 ` Meelis Roos [this message]
2016-07-13 8:31 ` Meelis Roos
[not found] ` <alpine.LRH.2.20.1607131122010.20366-ptEonEWSGqKptlylMvRsHA@public.gmane.org>
2016-07-13 9:03 ` Joerg Roedel
2016-07-13 9:03 ` Joerg Roedel
[not found] ` <20160713090332.GK12639-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2016-07-13 9:16 ` Meelis Roos
2016-07-13 9:16 ` Meelis Roos
[not found] ` <alpine.LRH.2.20.1607131206430.20366-ptEonEWSGqKptlylMvRsHA@public.gmane.org>
2016-07-13 9:43 ` Joerg Roedel
2016-07-13 9:43 ` Joerg Roedel
2016-07-13 9:40 ` Meelis Roos
2016-07-13 9:40 ` Meelis Roos
[not found] ` <alpine.LRH.2.20.1607131239410.20366-ptEonEWSGqKptlylMvRsHA@public.gmane.org>
2016-07-13 9:49 ` Joerg Roedel
2016-07-13 9:49 ` Joerg Roedel
[not found] ` <20160713094917.GM12639-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2016-07-13 9:58 ` Meelis Roos
2016-07-13 9:58 ` Meelis Roos
[not found] ` <alpine.LRH.2.20.1607131257390.20366-ptEonEWSGqKptlylMvRsHA@public.gmane.org>
2016-07-13 10:18 ` Joerg Roedel
2016-07-13 10:18 ` Joerg Roedel
[not found] ` <20160713101859.GO12639-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2016-07-13 14:48 ` Alex Williamson
2016-07-13 14:48 ` Alex Williamson
[not found] ` <20160713084830.09453584-1yVPhWWZRC1BDLzU/O5InQ@public.gmane.org>
2016-07-13 15:13 ` IOMMU+DMAR causing NMIs-s Linda Knippers
2016-07-13 15:13 ` Linda Knippers
[not found] ` <1a4c4b65-c716-08a5-af89-1b0f551024ed-ZPxbGqLxI0U@public.gmane.org>
2016-07-13 21:52 ` Meelis Roos
2016-07-13 21:52 ` Meelis Roos
[not found] ` <alpine.LRH.2.20.1607132258001.30020-ptEonEWSGqKptlylMvRsHA@public.gmane.org>
2016-07-13 23:04 ` Alex Williamson
2016-07-13 23:04 ` Alex Williamson
[not found] ` <20160713170408.6e5d2534-1yVPhWWZRC1BDLzU/O5InQ@public.gmane.org>
2016-07-14 8:31 ` Joerg Roedel
2016-07-14 8:31 ` Joerg Roedel
2016-08-24 8:19 ` Meelis Roos
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=alpine.LRH.2.20.1607131122010.20366@math.ut.ee \
--to=mroos-y27eyolml9s@public.gmane.org \
--cc=dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.