[Top] [All Lists]

Re: Mystery packet killing tg3

To: Peter Buckingham <peter@xxxxxxxxxxxx>
Subject: Re: Mystery packet killing tg3
From: Andi Kleen <ak@xxxxxx>
Date: 5 May 2005 20:56:35 +0200
Date: Thu, 5 May 2005 20:56:35 +0200
Cc: "David S. Miller" <davem@xxxxxxxxxxxxx>, jgarzik@xxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <427A6898.4070804@xxxxxxxxxxxx>
References: <20050502162405.65dfb4a9@xxxxxxxxxxxxxxxxxxxxx> <20050502200251.38271b61.davem@xxxxxxxxxxxxx> <m14qdiyhcn.fsf@xxxxxx> <42791825.2080204@xxxxxxxxxxxx> <20050505114327.GA51761@xxxxxx> <427A5363.2080703@xxxxxxxxxxxx> <20050505180609.GB24386@xxxxxx> <427A6426.40104@xxxxxxxxxxxx> <20050505183144.GD24386@xxxxxx> <427A6898.4070804@xxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.4.1i
On Thu, May 05, 2005 at 11:40:24AM -0700, Peter Buckingham wrote:
> Andi Kleen wrote:
> >That should be impossible. Or it sounds like a serious
> >hardware problem. DAC should normally always work with all e1000 AFAIK.
> okay.
> I basically just force it to take a 32bit dma mask. I admit i'm a little 
> clueless as to what this truely means. I had assumed that it would 
> result in only dma'ing to an area below 4GB, but I hadn't really 
> validated that assumption :-(

If you dont use iommu=force it will only cause IOMMU remapping
when the memory buffer is beyond 4GB. It is basically random
if that happens or not, depending on how fully your memory is.

With iommu=force or CONFIG_IOMMU_DEBUG all IO is foced 
through the IOMMU.

> >Most likely you have some hardware problem and it is somehow magically
> >worked around by IOMMU remapping. One difference is that
> >the remapping makes all IO slower, perhaps the changed timing
> >works around some bug.
> this is always a possibility, can you suggest some ways of isolating 
> this problem?

Hmm - if you want to hack the kernel you could add udelay()s
to the no IOMMU paths in arch/x86_64/kernel/pci-gart.c 
and see if that cures the problem too.  If yes then the timing
theory would be proved.
Actually the IOMMU code does more than just delaying, it also
does config space accesses which might flush or synchronize
things in the PCI bridges. Perhaps adding some dummy access
for that would be good too.

The dmesg looks similar to the previous one from the IOMMU
code perspective.


<Prev in Thread] Current Thread [Next in Thread>