Broadcom NetXtreme BCM57 Series, Руководство пользователя

Страница: 137 / 174

Broadcom Gigabit Ethernet Teaming Services NetXtreme User Guide
Broadcom
®
April 2017 • 2CS57XX-CDUM514-R Page 137
Intermediate Driver (Virtual Adapter/Team)
Table 16 lists the event log messages supported by the intermediate driver, explains the cause for the message,
and provides the recommended action.
20 Driver initialization failed. Unspecified failure during
driver initialization.
Reinstall the driver, update
to a newer driver, run
Broadcom Advanced
Control Suite diagnostics,
or replace the adapter.
21 Ethernet@WireSpeed is enabled
and could not negotiate maximum
link speed.
Potential faulty cable or
connection.
Reconnect the cable or
change the cable.
22 Unable to install device driver for
obsolete network controller for this
Operating System.
The latest outbox driver
doesn't support obsolete
device any more.
Use OS inbox driver, or
replace the device with
latest one.
256 Not enough contiguous physical
memory for coalescing pool.
Driver can't allocate
enough shared memory for
coalescing packet buffers.
Remove/Disable other
adapter from the system or
increase system memory.
Table 16: Intermediate Driver Event Log Messages
System Event
Message Number Message Cause Corrective Action
1 Unable to register with NDIS. The driver cannot register
with the NDIS interface.
Unload other NDIS drivers.
2 Unable to instantiate the
management interface.
The driver cannot create a
device instance.
Reboot the operating system.
3 Unable to create symbolic link
for the management interface.
Another driver has created
a conflicting device name.
Unload the conflicting device
driver that uses the name Blf .
4 Broadcom Advanced Server
Program Driver has started.
Another driver has created
a conflicting device name.
Informational message only. No
action is required.
5 Broadcom Advanced Server
Program Driver has stopped.
The driver has stopped. Informational message only. No
action is required.
6 Could not allocate memory for
internal data structures.
The driver cannot allocate
memory from the operating
system.
Close running applications to
free memory
7 Could not bind to adapter. The driver could not open
one of the team physical
adapters.
Unload and reload the physical
adapter driver, install an
updated physical adapter
driver, or replace the physical
adapter.
8 Successfully bind to adapter. The driver successfully
opened the physical
adapter.
Informational message only. No
action is required.
Table 15: Base Driver Event Log Messages (Cont.)
Message
Number
Message Cause Corrective Action