trouble with mismatched network
Kirk Reiser
kirk@braille.uwo.ca
Mon Oct 25 22:19:36 1999
>From: Donald Becker <becker@cesdis.gsfc.nasa.gov>
>Hmmm, is your machine slow or very overloaded?
>Make certain it isn't going into power-save mode and slowing down the CPU!
I finally received a copy of this message. I think myabe Donald you
were asking me this question instead of William. The computer is a
pentium-3-450 so I don't think it would be considered a slow system.
I am not sure what you mean by power safe mode, except maybe from a
power management perspective. It isn't doing this at all as far as I
can tell. I will include a portion of the output from the kmsg's and
the output from a tulip-diag I ran.
NET4: Ethernet Bridge 005 for NET4.0
PPP: version 2.3.7 (demand dialling)
TCP compression code copyright 1989 Regents of the University of California
PPP line discipline registered.
IPv4 over IPv4 tunneling driver
tulip.c:v0.91g 7/16/99 becker@cesdis.gsfc.nasa.gov
eth0: Lite-On 82c168 PNIC rev 32 at 0xe400, 00:A0:CC:51:7F:1C, IRQ 10.
eth0: MII transceiver #1 config 3000 status 7829 advertising 01e1.
eth1: Lite-On 82c168 PNIC rev 32 at 0xe800, 00:A0:CC:51:8D:1A, IRQ 12.
eth1: MII transceiver #1 config 3000 status 7829 advertising 01e1.
eth1: Setting full-duplex based on MII#1 link partner capability of 45e1.
tcpdump uses obsolete (PF_INET,SOCK_PACKET)
eth0: Promiscuous mode enabled.
device eth0 entered promiscuous mode
eth0: Promiscuous mode enabled.
device eth0 left promiscuous mode
eth0: Promiscuous mode enabled.
device eth0 entered promiscuous mode
eth0: Promiscuous mode enabled.
device eth0 left promiscuous mode
eth0: Promiscuous mode enabled.
device eth0 entered promiscuous mode
eth0: Promiscuous mode enabled.
device eth0 left promiscuous mode
eth0: Promiscuous mode enabled.
device eth0 entered promiscuous mode
tulip-diag.c:v1.19 10/2/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Index #1: Found a Lite-On 82c168 PNIC adapter at 0xe400.
Port selection is MII, half-duplex.
Transmit started, Receive started, half-duplex.
The Rx process state is 'Waiting for packets'.
The Tx process state is 'Idle'.
The transmit threshold is 72.
Index #2: Found a Lite-On 82c168 PNIC adapter at 0xe800.
Port selection is MII, full-duplex.
Transmit started, Receive started, full-duplex.
The Rx process state is 'Waiting for packets'.
The Tx process state is 'Idle'.
The transmit threshold is 128.
Use '-a' or '-aa' to show device registers,
'-e' to show EEPROM contents, -ee for parsed contents,
or '-m' or '-mm' to show MII management registers.