linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pat Verner <pat@isis.co.za>
To: Manfred Spraul <manfred@colorfullife.com>,
	Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org, Alan@redhat.com
Subject: Re: PROBLEM: Network hanging - Tulip driver with Netgear (Lite-On)
Date: Tue, 27 Feb 2001 08:16:11 +0200	[thread overview]
Message-ID: <4.3.2.7.0.20010227081118.00aa1b80@192.168.0.18> (raw)
In-Reply-To: <3A9AC372.A86DC6C7@colorfullife.com>
In-Reply-To: <3A9A30C7.3C62E34@colorfullife.com> <3A9AB84C.A17D20AE@mandrakesoft.com>

Good morning all.

First thing this morning I applied Jeff's patch, as below.  Started off 
well, ran for about 20 minutes (and 40 MBytes) before hanging.

Reversed out Jeff's change and applied Manfred's patch to the same lines in 
pnic.c.  Ran for about 15 minutes (28 Mbytes) before hanging.  It is still 
early, and the network is still quiet, so the volume of data received is 
still low, but the hanging problem is unfortunately still there.

=Pat

At 09:58 PM 26/02/2001 +0100, Manfred Spraul wrote:
>Jeff Garzik wrote:
> > Pat, Manfred, in pnic_check_duplex, make this change:
> > > -        negotiated = mii_reg5 & tp->advertising[0];
> > > +        negotiated = mii_reg5 & tulip_mdio_read(dev, tp->phys[0], 4);
> >
>The changed fixed the problem.
>
> >
> > Manfred Spraul wrote:
> > >
> > > I think I found the bug:
> > >
> > > Someone (Jeff?) removed the line
> > >
> > >         tp->advertising[phy_idx++] = reg4;
> > >
> > > from tulip/tulip_core.c
> > >
> > > pnic_check_duplex uses that variable :-(
> > >
> > > There are 2 workarounds:
> > >
> > > * change pnic_check_duplex:
> > > s/tp->advertising[0]/tp->mii_advertise/g
> > >
> > > * remove the new mii_advertise variable and replace it with
> > > 'tp->advertising[i]'.
> >
> > mii_advertise is what MII is currently advertising on the current
> > media.  tp->advertising is per-phy, on the other hand.
> >
>
>Could you double check the code in tulip_core.c, around line 1450?
>IMHO it's bogus.
>
>1) if the network card contains multiple mii's, then the the advertised
>value of all mii's is changed to the advertised value of the first mii.
>
>2) the new driver starts with the current advertised value, the previous
>driver recalculated the value from mii_status
>
>[ mii_status = tulip_mdio_read(dev,phy,1); ]
>
>- reg4 = ((mii_status>>6)& tp->to_advertise) | 1;
>
>That could trigger 2 problems:
>* I tested with 'options=11', and the new driver announces '100baseT4'
>support, but the PHY doesn't support 100baseT4.
>* If the mii is incorrectly initialized, then a wrong advertised value
>is not corrected.
>
>--
>         Manfred

--
Pat Verner				E-Mail:  pat@isis.co.za
           Isis Information Systems (Pty) Ltd
           PO Box 281, Irene, 0062, South Africa
Phone: +27-12-667-1411	      	Fax: +27-12-667-3800


  parent reply	other threads:[~2001-02-27  6:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-26 10:32 PROBLEM: Network hanging - Tulip driver with Netgear (Lite-On) Manfred Spraul
2001-02-26 20:10 ` Jeff Garzik
2001-02-26 20:58   ` Manfred Spraul
2001-03-02 21:15     ` Jeff Garzik
2001-03-02 21:03       ` I/O problem with sustained writes Collectively Unconscious
2001-03-02 23:57         ` Andrew Morton
2001-03-02 22:20       ` PROBLEM: Network hanging - Tulip driver with Netgear (Lite-On) Manfred Spraul
2001-03-02 22:48         ` Donald Becker
2001-02-27  6:16   ` Pat Verner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-02-27  6:31 Pat Verner
2001-02-26  7:45 Pat Verner
2001-02-22  7:56 PROBLEM: Network hanging - Tulip driver with Netgear (Lite-On) NIC Pat Verner
2001-02-22 10:42 ` PROBLEM: Network hanging - Tulip driver with Netgear (Lite-On) Alan Cox
2001-02-22 20:12   ` Jeff Garzik
2001-02-22 12:42 ` Pat Verner

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=4.3.2.7.0.20010227081118.00aa1b80@192.168.0.18 \
    --to=pat@isis.co.za \
    --cc=Alan@redhat.com \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.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).