Return-path: Received: from 75-101-62-95.dsl.static.sonic.net ([75.101.62.95]:61505 "EHLO saboo.goop.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754311Ab1FBV3Q (ORCPT ); Thu, 2 Jun 2011 17:29:16 -0400 Message-ID: <4DE6CC6C.7000703@goop.org> (sfid-20110602_232920_713974_79991E18) Date: Wed, 01 Jun 2011 16:34:04 -0700 From: Jeremy Fitzhardinge MIME-Version: 1.0 To: NetDev , Linux Kernel Mailing List , linux-wireless@vger.kernel.org Subject: Re: 3.0-rc1: DMAR errors from iwlagn References: <4DE55A26.6040702@goop.org> In-Reply-To: <4DE55A26.6040702@goop.org> Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: Cc: linux-wireless On 05/31/2011 02:14 PM, Jeremy Fitzhardinge wrote: > I have a Lenovo X220 with: > > 03:00.0 Network controller: Intel Corporation Centrino Ultimate-N 6300 (rev 35) > Subsystem: Intel Corporation Centrino Ultimate-N 6300 3x3 AGN > Flags: bus master, fast devsel, latency 0, IRQ 50 > Memory at d2500000 (64-bit, non-prefetchable) [size=8K] > Capabilities: > Kernel driver in use: iwlagn > Kernel modules: iwlagn > > With 3.0-rc1, I'm seeing these in dmesg: > > DRHD: handling fault status reg 2 > DMAR:[DMA Write] Request device [03:00.0] fault addr ffe8a000 > DMAR:[fault reason 05] PTE Write access is not set > DRHD: handling fault status reg 2 > DMAR:[DMA Write] Request device [03:00.0] fault addr ffd5a000 > DMAR:[fault reason 05] PTE Write access is not set > DRHD: handling fault status reg 2 > DMAR:[DMA Write] Request device [03:00.0] fault addr ffd52000 > DMAR:[fault reason 05] PTE Write access is not set > > but the device seems to be working OK. > > Thanks, > J > > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ >