Re: RedHat 7.3 & vpn client 3.5.2 on T23

Michael Barnes <[email protected]>
Newsgroups gmane.linux.drivers.eepro100.devel
Message-ID <[email protected]>
Donald Becker wrote:
> 
> On Fri, 21 Jun 2002, Michael Barnes wrote:
> > Donald Becker wrote:
> > > On Fri, 21 Jun 2002, Michael Barnes wrote:
> > > > I just got an IBM T23, installed RedHat 7.3, and did up2date.
> > > > Jun 21 13:56:23 dhcp-2545-22 kernel: eepro100: wait_for_cmd_done timeout!
> > > ..
> > > > Jun 21 13:58:27 dhcp-2545-22 kernel: NETDEV WATCHDOG: eth0: transmit timed
> > > > out
> > > > Jun 21 13:58:27 dhcp-2545-22 kernel: eth0: Transmit timed out: status 0050
> > > > 0c80 at 30928/30988 command 200c0000.
> ...
> > > > I saw in the archive a message that suggests to disable sleep mode, but I
> > > > can't find instructions on how to do that, if that would help.
> > > Run
> > >   eepro100-diag -ee
> 
> > I am getting the same errors even after using that command. What else could
> > be the cause?
> 
> What did the command report?

This is the console log from when I checked the interface, disabled sleep
mode, and re-checked the interface 

[root@localhost eepro100-diag]# ./eepro100-diag -ee -f
eepro100-diag.c:v2.08 4/17/2002 Donald Becker ([email protected])
 http://www.scyld.com/diag/index.html
Index #1: Found a Intel Pro/100 VE (type 1031) adapter at 0x6400.
EEPROM contents, size 64x16:
    00: d000 bf59 b1ec 1a03 0000 0201 4701 0000
  0x08: 0000 0000 49a2 0209 1014 007f 0000 0000
      ...
  0x20: 0000 0000 0000 1031 0000 0000 0000 0000
      ...
  0x30: 002c 4000 4016 0000 0000 0000 0000 0000
  0x38: 0000 0000 0000 4030 0000 0000 0000 e98f
 The EEPROM checksum is correct.
Intel EtherExpress Pro 10/100 EEPROM contents:
  Station address 00:D0:59:BF:EC:B1.
  Board assembly 000000-000, Physical connectors present: RJ45
  Primary interface chip i82555 PHY #1.
   Sleep mode is enabled.  This is not recommended.
   Under high load the card may not respond to
   PCI requests, and thus cause a master abort.
   To clear sleep mode use the '-G 0 -w -w -f' options.
[root@localhost eepro100-diag]# ./eepro100-diag -G 0 -w -w -f
eepro100-diag.c:v2.08 4/17/2002 Donald Becker ([email protected])
 http://www.scyld.com/diag/index.html
Index #1: Found a Intel Pro/100 VE (type 1031) adapter at 0x6400.
Writing 49a0 to configuration word 10.
 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.
[root@localhost eepro100-diag]#
[root@localhost eepro100-diag]#
[root@localhost eepro100-diag]# ./eepro100-diag -ee
eepro100-diag.c:v2.08 4/17/2002 Donald Becker ([email protected])
 http://www.scyld.com/diag/index.html
Index #1: Found a Intel Pro/100 VE (type 1031) adapter at 0x6400.
A potential i82557 chip has been found, but it appears to be active.
Either shutdown the network, or use the '-f' flag.
[root@localhost eepro100-diag]# ./eepro100-diag -ee -f
eepro100-diag.c:v2.08 4/17/2002 Donald Becker ([email protected])
 http://www.scyld.com/diag/index.html
Index #1: Found a Intel Pro/100 VE (type 1031) adapter at 0x6400.
EEPROM contents, size 64x16:
    00: d000 bf59 b1ec 1a03 0000 0201 4701 0000
  0x08: 0000 0000 49a0 0209 1014 007f 0000 0000
      ...
  0x20: 0000 0000 0000 1031 0000 0000 0000 0000
      ...
  0x30: 002c 4000 4016 0000 0000 0000 0000 0000
  0x38: 0000 0000 0000 4030 0000 0000 0000 e991
 The EEPROM checksum is correct.
Intel EtherExpress Pro 10/100 EEPROM contents:
  Station address 00:D0:59:BF:EC:B1.
  Board assembly 000000-000, Physical connectors present: RJ45
  Primary interface chip i82555 PHY #1.


> What driver version are you using?

It looks like it is v1.09 Revision 1.36

> --
> Donald Becker                           [email protected]
> Scyld Computing Corporation             http://www.scyld.com
> 410 Severn Ave. Suite 210               Second Generation Beowulf Clusters
> Annapolis MD 21403                      410-990-9993

-- 
Michael Barnes
Core IP Eng - Routing
408-525-2785
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.