Re: Always require second ifdown/ifup after reboot

Just one further useful data point: I've verified that the tulip driver
that comes with linux 2.2.20, v0.91g-ppc 7/16/99, works perfectly. It's
only the 2.4.20 driver, 0.9.15-pre12 8/9/02 that causes the problem.
Sometimes the card only stays up for a few seconds at a time before it
needs to be ifdown/ifup again; other times it lasts a little longer.

--Adam

On Sun, Feb 16, 2003 at 02:48:15PM -0500, Adam Kessel wrote:
> On Sun, Feb 16, 2003 at 11:25:23AM -0500, Donald Becker wrote:
> > > 00:11.0 Ethernet controller: Lite-On Communications Inc LNE100TX [Linksys EtherFast 10/100] (rev 25)
> > > tulip is compiled into the kernel (Debian unstable/linux 2.4.20).  
> > > Oddly, every time I reboot, I need to ifdown and ifup to get the card to
> > > work.
> > What driver version are you using?
> 
> tulip.c says:
> 
> #define DRV_VERSION     "0.9.15-pre12"
> #define DRV_RELDATE     "Aug 9, 2002"
> 
> Interestingly, I don't think this problem was occurring with the 2.2
> kernel, which used "v0.91g-ppc 7/16/99".
> 
> (in both cases I'm using the Debian stock source, which in this case I
> don't think differs from vanilla kernel source).
> 
> > What is the detection message?
> 
> syslog reports:
> 
> eth0: Autonegotiation failed, using 10baseT, link beat status 10cc.
> 
> Also, I frequently see:
> 
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: PNIC2 transmit timed out, status e4260000, CSR6/7 e0402002 / effffbff CSR12 000000c8, resetting...
> 
> ....
> 
> eth0: PNIC2 transmit timed out, status e4260000, CSR6/7 e0402002 / effffbff CSR12 000000c8, resetting...
> eth0: Out-of-sync dirty pointer, 19 vs. 38.
> 
> and so on.
> 
> Sometimes it seems to me more frequent than others, and switches back and
> forth between 100baseT and 10 baseT.
> ---
> Adam Kessel ([email protected])

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+UPDcdTf3ZklQ6qYRAmFdAJ4r6shD/sixvlJNWIkCOJcg6kYpfACfWjgV
wjtPyfI6WuZOU/h1zw7RJxs=
=XMTs
-----END PGP SIGNATURE-----