The Linux® operating system detected a failure in a driver or subsystem.
The first five characters (BFyyy) of these SRCs indicate the driver or subsystem responsible for the error:
The last three characters specify the error condition. The last three characters of the SRCs are arranged such that 1xx is lowest severity and Fxx is highest severity. For example:
Use the following table to locate the last four characters of the (BF77) Linux SRC that you want to find, then perform the suggested actions:
Table 1. (BF77 0xxx) Linux reference codes (olympic driver)
| Reference Code | Description/Action Perform all actions before exchanging Failing Items | Failing Item |
|---|---|---|
| 0A00 | Unrecognized command code or unrecognized buffer
address. Have the customer do the following:
|
NEXTLVL |
| 0F01 | The olympic driver was unable to initialize the token ring card.
Corrective action may be possible depending upon the error code. |
IOADPTR |
| 0F02 | The Cardbus token ring adapter did not respond to initialization commands.
Ensure that Cardbus adapter is properly inserted. |
IOADPTR |
| 0F03 | The token ring adapter was unable to join the ring.
Have the customer use the network configuration tool supplied by the distributor to specify a ring speed (instead of automatically detecting ring speed). |
IOADPTR |
| 0F04 | The adapter open request failed with the specified error code. | IOADPTR |
| 0800 | The driver was unable to send a received packet to the upper layer
protocols because there is insufficient free memory.
The customer may need to increase system memory. |
LPARCFG |
| 0F05 | The specified hardware, PCI or parity error has occurred.
Have the customer reset the adapter |
IOADPTR |
| 0F06 | The specified interrupt has occurred, but was not expected by the driver
or a timeout occurred during device close processing.
For occasional occurances, no action is required. For excessive occurrences, have the customer reset the adapter. If resetting the adapter does not work, perform the action specified in the Failing Item column. |
IOADPTR |
| 0F07 | Unrecognized srb command or cannot set mac/laa address while card is
open.
Have the customer reload the driver |
IOADPTR |
| 0F08 | A short circuit has been detected. Have the customer do the following:
|
IOADPTR |
| 0F09 | An internal hardware error has been detected in the specified adapter
during auto removal processing.
Have the customer reload the driver |
IOADPTR |
| 0F0A | An FDX protocol error has been detected.
Have the customer reload the driver |
IOADPTR |
| 0F0B | Invalid return code in asb.
Have the customer upgrade the driver |
IOADPTR |
Table 2. (BF77 5xxx) Linux reference codes (pcnet32 driver)
| Reference Code | Description/Action Perform all actions before exchanging Failing Items | Failing Item |
|---|---|---|
| 5800 | The driver was unable to use 32-bit DMA.
Have the customer verify the driver software level. |
NEXTLVL |
| 5801 | Memory allocation failed. Have the customer do the following:
|
NEXTLVL |
| 5802 | Transmit timed out, resetting.
Have the customer verify the driver software level. |
NEXTLVL |
| 5803 | A FIFO error has occurred.
Have the customer verify the driver software level. |
NEXTLVL |
| 5804 | The transmit pointers are out of synchronization.
Have the customer verify the driver software level. |
NEXTLVL |
| 5F00 | The driver could not enable the PCI device. | IOADPTR |
| 5F01 | The hardware did not request any IO resources. | IOADPTR |
| 5F02 | The IO addresses for the card are already allocated.
Have the customer verify the driver software level. |
IOADPTR |
| 5F03 | The chip can not be accessed in 32-bit or 16-bit mode.
Have the customer verify the driver software level. |
IOADPTR |
Table 3. (BF77 6xxx) Linux reference codes (bcm 5700 driver)
| Reference Code | Description/Action Perform all actions before exchanging Failing Items | Failing Item |
|---|---|---|
| 6500 | Unable to find or create the directory under /proc/net.
Have the customer verify that procfs is supported by the kernel. |
NEXTLVL |
| 6501 | Insufficient kernel memory available for allocation. Have the customer
do the following:
|
NEXTLVL |
| 6502 | The driver was unable to use either 64-bit or 32-bit DMA.
Have the customer verify driver software level. |
NEXTLVL |
| 6503 | Linux does not support a hardware feature which has been enabled.
Run diagnostics to disable Turbo Teaming. |
NEXTLVL |
| 6504 | Memory allocation failed - buffer parameters may be set too high. Have
the customer do the following:
|
NEXTLVL |
| 6505 | Conflicting rx_coalesce_ticks (0) and rx_max_coalesce_frames (0) parameters.
Have the customer do the following:
|
NEXTLVL |
| 6506 | Conflicting tx_coalesce_ticks (0) and tx_max_coalesce_frames (0) parameters.
Have the customer do the following:
|
NEXTLVL |
| 6507 | The value given to the stats_coalesce_ticks parameter is invalid.
Have the customer change the stats_coalesce_ticks parameter of the driver. |
NEXTLVL |
| 6800 | Either this adapter or the system does not allow the use of adapter
based transmit descriptors. Have the customer do the following:
|
NEXTLVL |
| 6801 | This adapter does not support hardware checksum offload. Have the customer
do the following:
|
NEXTLVL |
| 6802 | This adapter does not support hardware TSO. Have the customer do the
following:
|
NEXTLVL |
| 6A00 | This adapter hardware does not support frames sizes over 1500 bytes.
Have the customer verify the driver software level If you replace the adapter, use one that offers additional capablities |
IOADPTR |
| 6F00 | Unable to read the adapter's NVRAM.
Have the customer verify the driver software level |
IOADPTR |
| 6F01 | Cannot get MAC addr from NVRAM.
Have the customer verify the driver software level |
IOADPTR |
| 6F02 | Unable to read PCI Config space or NVRAM.
Have the customer verify the driver software level |
IOADPTR |
Table 4. (BF77 7xxx) Linux reference codes (e100 driver)
| Reference Code | Description/Action Perform all actions before exchanging Failing Items | Failing Item |
|---|---|---|
| SRC | Probable Causes | Actions |
| 7800 | Internal error in driver, kernel, or firmware. Have the customer do
the following:
|
NEXTLVL |
| 7801 | Insufficient kernel memory is available for the driver. Have the customer
do the following:
|
NEXTLVL |
| 7802 | Internal error in driver, kernel, or firmware. Have the customer do
the following:
|
NEXTLVL |
| 7E00 | Not enough memory for the driver. Unable to initialize (or reinitialize)
the adapter card. Have the customer do the following:
|
IOADPTR |
| 7E01 | The BIOS has assigned conflicting address spaces to different devices.
Have the customer do the following:
|
IOADPTR |
| 7E02 | The driver requested a DMA configuration that your system does not
support. Have the customer do the following:
|
IOADPTR |
| 7E03 | The adapter's MAC address is not a valid Ethernet address. Have the
customer do the following:
|
IOADPTR |
| 7F00 | The EEPROM on the network adapter may be corrupted. | IOADPTR |
| 7F01 | The driver cannot enable the adapter as a PCI device. | IOADPTR |
| 7F02 | The network adapter failed its self-test. | IOADPTR |
Table 5. (BF77 8xxx) Linux reference codes (e1000 driver)
| Reference Code | Description/Action Perform all actions before exchanging Failing Items | Failing Item |
|---|---|---|
| 8E00 | Cannot enable DMA for either 32 bits or 64 bits. | NEXTLVL |
| 8E01 | Unable to access PCI data area for checksum value. However, the device
id is valid. Have the customer do the following:
|
NEXTLVL |
| 8E02 | The MAC type is not ethernet as expected. Have the customer do the
following:
|
IOADPTR |
| 8F00 | Adapter hardware failure. | IOADPTR |