On Fri, 2 Mar 2001, Manfred Spraul wrote:
> Jeff Garzik wrote:
> > Manfred Spraul wrote:
> > > 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
Jeff Garzik wrote:
>
> Manfred Spraul wrote:
> > 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.
>
Manfred Spraul wrote:
> 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.
I'm really curious about this one
Manfred Spraul wrote:
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.
I'm really curious about this one
Jeff Garzik wrote:
Manfred Spraul wrote:
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.
I'm really
On Fri, 2 Mar 2001, Manfred Spraul wrote:
Jeff Garzik wrote:
Manfred Spraul wrote:
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
Later, for what its worth:
Up to now, I have only had one of the network cards active, and connected
to the hub. I have just connected a second card to the hub, with an
additional IP address. After running IPTRAF, it hung after about 5
minutes, after which BOTH network cards stopped
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.
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
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:
>
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
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
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:
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
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.
Later, for what its worth:
Up to now, I have only had one of the network cards active, and connected
to the hub. I have just connected a second card to the hub, with an
additional IP address. After running IPTRAF, it hung after about 5
minutes, after which BOTH network cards stopped
26 Feb 2001:
Rebuilt the kernel to version 2.4.2-ac4, to include the latest tulip patches.
The performance is better, but it is still not quite right; this time it
received just over 48 MBytes before hanging :-(
Using a 3C590B card on Friday, I ran IPTRAF for about 6 hours, and several
26 Feb 2001:
Rebuilt the kernel to version 2.4.2-ac4, to include the latest tulip patches.
The performance is better, but it is still not quite right; this time it
received just over 48 MBytes before hanging :-(
Using a 3C590B card on Friday, I ran IPTRAF for about 6 hours, and several
On Thu, 22 Feb 2001, Alan Cox wrote:
> > three Netgear NICs and am experiencing considerable trouble with the=20
> > combination:
> >
> > Kernel 2.4.[01]:ifconfig shows that the card see's traffic on t=
> > he=20
> > network, but does not transmit anything (no response to ping).
>
> Use
Rebuilt the kernel using using 2.4.1 + patch-2.4.1-ac20 :
Initial state is good, and now ping works. However, if I run IPTRAF, then
the card grinds to a halt after receiving about 2.6 Mbytes on try 1, then
11 Mbytes on try 2, after which it will neither receive or transmit :-(
After this the
Rebuilt the kernel using using 2.4.1 + patch-2.4.1-ac20 :
Initial state is good, and now ping works. However, if I run IPTRAF, then
the card grinds to a halt after receiving about 2.6 Mbytes on try 1, then
11 Mbytes on try 2, after which it will neither receive or transmit :-(
After this the
On Thu, 22 Feb 2001, Alan Cox wrote:
three Netgear NICs and am experiencing considerable trouble with the=20
combination:
Kernel 2.4.[01]:ifconfig shows that the card see's traffic on t=
he=20
network, but does not transmit anything (no response to ping).
Use a current
1. Network hanging - Tulip driver with Netgear (Lite-On) NIC
2. I am trying to prepare a new firewall host with a Pentium III and
three Netgear NICs and am experiencing considerable trouble with the
combination:
Kernel 2.4.[01]:ifconfig shows that the card see's traffic on
1. Network hanging - Tulip driver with Netgear (Lite-On) NIC
2. I am trying to prepare a new firewall host with a Pentium III and
three Netgear NICs and am experiencing considerable trouble with the
combination:
Kernel 2.4.[01]:ifconfig shows that the card see's traffic on
24 matches
Mail list logo
