From: "David S. Miller" <davem@davemloft.net>
To: "Michael Chan" <mchan@broadcom.com>
Cc: shemminger@osdl.org, jgarzik@pobox.com, netdev@oss.sgi.com
Subject: Re: Mystery packet killing tg3
Date: Tue, 3 May 2005 15:03:33 -0700 [thread overview]
Message-ID: <20050503150333.1ac1c159.davem@davemloft.net> (raw)
In-Reply-To: <1115152907.15156.26.camel@rh4>
On Tue, 03 May 2005 13:41:47 -0700
"Michael Chan" <mchan@broadcom.com> wrote:
> MSI is buggy on 5703 and tg3 will not enable MSI on that chip. MSI only
> works on the latest PCI Express chips.
Ok, and he has a pre-MSI copy of the tg3 driver anyways.
Michael, there were no master/target abort bits set in the PCI status
register from his dump. If one of the DMA units locks up on the tg3,
will it still be able to update the PCI_STATUS register appropriately
when it encounters a DMA transaction error (ie. master or target abort)
or would we also need to look at the PCI host bridge PCI config space
registers as well?
I strongly suspect one of two things in these AMD system cases of tg3
wedging:
1) some DMA problem
2) register write reordering
Lack of master/target abort indication in tg3's PCI status register
makes me feel that #2 is more likely to be the problem cause.
Just for fun, Stephen, can you make tg3_get_invariants() always set
the TG3_FLAG_MBOX_WRITE_REORDER bit in tp->tg3_flags and see if that
makes the problem go away?
Thanks.
next prev parent reply other threads:[~2005-05-03 22:03 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 [this message]
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
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=20050503150333.1ac1c159.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jgarzik@pobox.com \
--cc=mchan@broadcom.com \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.org \
/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).