Technical article 101595

What is the error "Warning SMPW (iobase 0x0000xxxx) possible cable fault"?

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4

Written · Last revised

Problem

When doing large file transfers using rcp(C) or ftp(TC), this error message sporadically occurs:

Warning SMPW (iobase 0x0000fc00) possible cable fault

(where the iobase value will depend on where the NIC is configured), and the networking subsystem on the server may lock up. In some cases, a reboot may be necessary to clear the hang.

Cause

This error condition may occur on any of the NICs supported by
SCO that use the "smpw" or "spwr" drivers from Standard Microsystems             (SMC).  The complete list of network cards is as follows:

SMC SMC8432BA EtherPower PCI Ethernet Adapter SMC SMC8432BT EtherPower PCI Ethernet Adapter SMC SMC8432BTA EtherPower PCI Ethernet Adapter SMC SMC8432T EtherPower PCI Ethernet Adapter SMC SMC8432TA EtherPower PCI Ethernet Adapter SMC SMC8434T EtherPower2 Dual Channel PCI Ethernet SMC SMC8434BT EtherPower2 Dual Channel PCI Ethernet SMC SMC9332 EtherPower 10/100 PCI Ethernet Adapter SMC SMC9432 EtherPower II 10/100 PCI Ethernet Adapter

The error is a message from the driver. It indicates that there may be a problem in detecting the carrier signal, or with the physical attachment to the network.

Solution

SMC has been made aware of possible problems with the driver and/or firmware for some of these cards.

Some users have seen better performance by doing the following:

o Using the following commands, check for streams failures, Ierrs/Oerrs, collisions, dropped connections, and so on, which may indicate other problems with the network:

netstat -s
netstat -m
netstat -i
llistat -l
ifconfig -a

o Upgrade the system BIOS to PCI 2.0 or later.

o Using netconfig's "advanced options", manually configure the media type to match your network configuration; do NOT allow the driver to auto-select the media type.

o Disable busmastering (if possible).

o Ensure that all machines have unique IP addresses and the same netmask and broadcast addresses; make sure no machine has an IP address that is the same as the network address.

o Check for bad cables or connectors, a bad connection to the transceiver (if applicable), or possibly a bad port on the hub or switch. Try plugging the system into a known good cable and/or port, if possible.

If the problem is intermittent, the driver should recover and allow the server to stay connected to the network.

From the Xinuos technical article database, record 101595. Reproduced with permission. The original is at www.sco.com/ta/101595, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.