Return-path: Received: from mail2.candelatech.com ([208.74.158.173]:34366 "EHLO mail2.candelatech.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752153AbdDMSMN (ORCPT ); Thu, 13 Apr 2017 14:12:13 -0400 To: "linux-wireless@vger.kernel.org" , netdev From: Ben Greear Subject: How to debug DMAR errors? Message-ID: (sfid-20170413_201244_100223_E4287776) Date: Thu, 13 Apr 2017 11:12:12 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Sender: linux-wireless-owner@vger.kernel.org List-ID: Hello, I have been seeing a regular occurrence of DMAR errors, looking something like this when testing my ath10k driver/firmware under some specific loads (maximum receive of 512 byte frames in AP mode): DMAR: DRHD: handling fault status reg 3 DMAR: [DMA Read] Request device [05:00.0] fault addr fd99f000 [fault reason 06] PTE Read access is not set ath10k_pci 0000:05:00.0: firmware crashed! (uuid 594b1393-ae35-42b5-9dec-74ff0c6791ff) So, I am wondering if there is any way I can get more information about what this fd99f000 address is? Once this problem hits, the entire OS locks hard (not even sysrq-boot will do anything), so I guess I would need the DMAR logic to print out more info on that address somehow. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com