> > > 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 (mr...@linux.ee) _______________________________________________ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu
