On Fri, Sep 26, 2008 at 6:12 PM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Fri, 2008-09-26 at 17:47 +0300, Muli Ben-Yehuda wrote: > >> The way to debug this is to figure out why device 00:1f.2 is trying to >> read from DMA address fffbf000 and does not have permission to do >> so. This could be indicative of a driver bug where it is programming >> the device to read from some buffer that has not been allocated >> through the DMA API and thus does not have a valid IOMMU mapping, or a >> hardware quirk where the device tries to read from memory without host >> involvement. The former is much more likely. > > The same is probably true for the iwlagn case which was > >> [ 4184.617392] DMAR:[DMA Read] Request device [03:00.0] fault addr fa946000 >> [ 4184.617393] DMAR:[fault reason 06] PTE Read access is not set >> [ 4184.644081] iwlagn: Microcode HW error detected. Restarting. > > and indeed matches experience from myself and Marcel that DMA bugs seem > to lurk. Meanwhile it all reported bugs in this case points to 64 bit installations, I'll give it more testing Thnaks. Tomas -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
