All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Buckingham <peter@pantasys.com>
To: Andi Kleen <ak@muc.de>
Cc: "David S. Miller" <davem@davemloft.net>,
	jgarzik@pobox.com, netdev@oss.sgi.com
Subject: Re: Mystery packet killing tg3
Date: Thu, 05 May 2005 12:02:15 -0700	[thread overview]
Message-ID: <427A6DB7.10404@pantasys.com> (raw)
In-Reply-To: <20050505185635.GE24386@muc.de>

Andi Kleen wrote:
> With iommu=force or CONFIG_IOMMU_DEBUG all IO is foced 
> through the IOMMU.

okay, that's definitely bad...

> 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.

okay, i'll start to take a look at this, but it'll probably be a little 
while before i can really get to it. i'll let you know what i find out.

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

it actually looks like it's configure correctly now (at least from 
agp-gart messages), before we were getting errors. i guess the bios guys 
finally got it right ;-)

thanks,

peter

  reply	other threads:[~2005-05-05 19:02 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
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 [this message]
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=427A6DB7.10404@pantasys.com \
    --to=peter@pantasys.com \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.