From: Andi Kleen <ak@muc.de>
To: "David S. Miller" <davem@davemloft.net>
Cc: jgarzik@pobox.com, netdev@oss.sgi.com
Subject: Re: Mystery packet killing tg3
Date: Wed, 04 May 2005 20:30:00 +0200 [thread overview]
Message-ID: <m14qdiyhcn.fsf@muc.de> (raw)
In-Reply-To: <20050502200251.38271b61.davem@davemloft.net> (David S. Miller's message of "Mon, 2 May 2005 20:02:51 -0700")
"David S. Miller" <davem@davemloft.net> writes:
>
> This usually means that there is some DMA corruption.
> For example, some bug in the x86_64 IOMMU code or similar
> causes a bogus DMA address to be fed to the tg3 or even
> worse a DMA mapping is unmapped before tg3 is actually
> done with it.
IOMMU code on x86-64 should be never active unless Stephen
used IOMMU_DEBUG or iommu=force. THat is because the tg3
is a 64bit capable device and should always use bypass.
> Since AMD promised me an Opteron system last year, but never
> made good on that promise, I've never been able to work on
> fixing this bug myself. :-/
You could just buy one ,-) Lowend A64s boards+cpus are *really* cheap
these days. And it will likely be much quieter than a noisy
original AMD box. And the IOMMU works on that too if you force
it (normally it is never active because they dont have enough
memory to need remapping)
-Andi
next prev parent reply other threads:[~2005-05-04 18:30 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-02 23:24 Mystery packet killing tg3 Stephen Hemminger
2005-05-03 3:02 ` David S. Miller
2005-05-03 21:05 ` Stephen Hemminger
2005-05-03 21:13 ` David S. Miller
2005-05-03 20:41 ` Michael Chan
2005-05-03 22:03 ` David S. Miller
2005-05-03 21:28 ` Michael Chan
2005-05-03 22:53 ` David S. Miller
2005-05-03 22:45 ` Stephen Hemminger
2005-05-03 22:39 ` David S. Miller
2005-05-03 22:59 ` Stephen Hemminger
2005-05-03 21:29 ` Stephen Hemminger
2005-05-04 18:30 ` Andi Kleen [this message]
2005-05-04 18:44 ` Peter Buckingham
2005-05-05 11:43 ` Andi Kleen
2005-05-05 16:20 ` Stephen Hemminger
2005-05-05 18:01 ` Andi Kleen
2005-05-05 17:09 ` Peter Buckingham
2005-05-05 17:32 ` Rick Jones
2005-05-05 17:38 ` Peter Buckingham
2005-05-05 17:45 ` John Heffner
2005-05-05 18:06 ` Andi Kleen
2005-05-05 18:21 ` Peter Buckingham
2005-05-05 18:31 ` Andi Kleen
2005-05-05 18:40 ` Peter Buckingham
2005-05-05 18:56 ` Andi Kleen
2005-05-05 19:02 ` Peter Buckingham
2005-05-05 19:24 ` Andi Kleen
2005-05-04 19:41 ` Stephen Hemminger
-- strict thread matches above, loose matches on Subject: below --
2005-05-04 6:09 Michael Chan
2005-05-04 6:27 Michael Chan
2005-05-04 22:51 ` Stephen Hemminger
2005-05-04 22:30 ` Michael Chan
[not found] ` <20050505113356.0f1b4c00.davem@davemloft.net>
2005-05-05 19:56 ` Michael Chan
2005-05-05 21:42 ` David S. Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m14qdiyhcn.fsf@muc.de \
--to=ak@muc.de \
--cc=davem@davemloft.net \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).