[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LRH.2.20.1607131239410.20366@math.ut.ee>
Date: Wed, 13 Jul 2016 12:40:39 +0300 (EEST)
From: Meelis Roos <mroos@...ux.ee>
To: Joerg Roedel <joro@...tes.org>
cc: iommu@...ts.linux-foundation.org,
Linux Kernel list <linux-kernel@...r.kernel.org>,
David Woodhouse <dwmw2@...radead.org>
Subject: Re: IOMMU+DMAR causing NMIs-s (was: 4.7-rc6: NMI in intel_idle on
HP Proliant G6)
> > > 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.
>
> Oh, in that case it is not related to the recent iova changes. Does the
> box have any hardware error log which you can access and send to us
> (right after some NMIs happened)?
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.
--
Meelis Roos (mroos@...ux.ee)
Powered by blists - more mailing lists