From: "David S. Miller" <davem@davemloft.net>
To: "Michael Chan" <mchan@broadcom.com>
Cc: peterc@gelato.unsw.edu.au, netdev@oss.sgi.com
Subject: Re: TG3 fix for slow switches (Was: TG3 driver failure on HP 16-way)
Date: Wed, 22 Dec 2004 20:31:38 -0800 [thread overview]
Message-ID: <20041222203138.778fedb3.davem@davemloft.net> (raw)
In-Reply-To: <B1508D50A0692F42B217C22C02D84972020F3CED@NT-IRVA-0741.brcm.ad.broadcom.com>
On Wed, 22 Dec 2004 16:02:44 -0800
"Michael Chan" <mchan@broadcom.com> wrote:
> David, While the 2nd patch or something similar should be applied, I
> think the underlying cause of tg3_readphy() returning error should be
> further investigated.
Would this condition be possible if something, such as ASF, were
continually polling the PHY in parallel with the driver?
On the other hand, it doesn't seem so foreign for the PHY to
block out register accesses for long periods of time for various
reasons.
But yes I'd also like to know more about exactly what is going on
in this case.
next prev parent reply other threads:[~2004-12-23 4:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-23 0:02 TG3 fix for slow switches (Was: TG3 driver failure on HP 16-way) Michael Chan
2004-12-23 4:31 ` David S. Miller [this message]
2005-05-31 15:38 ` Grant Grundler
2005-05-31 17:22 ` Michael Chan
2005-05-31 18:36 ` Grant Grundler
2005-05-31 17:42 ` Michael Chan
2005-05-31 19:03 ` Grant Grundler
2005-05-31 18:22 ` Michael Chan
-- strict thread matches above, loose matches on Subject: below --
2004-12-23 8:14 Michael Chan
2004-12-21 0:12 Peter Chubb
2004-12-21 0:15 ` David S. Miller
2004-12-21 1:11 ` Peter Chubb
2004-12-21 6:19 ` David S. Miller
2005-01-06 23:19 ` David S. Miller
2005-01-07 0:17 ` Darren Williams
2005-01-07 3:48 ` David S. Miller
2005-01-07 5:30 ` Darren Williams
2005-01-07 5:28 ` David S. Miller
2005-01-07 9:25 ` Darren Williams
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=20041222203138.778fedb3.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=mchan@broadcom.com \
--cc=netdev@oss.sgi.com \
--cc=peterc@gelato.unsw.edu.au \
/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).