The following error messages gives the meaning of the second 8 bits of 32-bit
status values produced by the PCI 100Base-T link driver and its supporting
modules. This is the so-called "driver status" portion. All values are
driver-specific, and are intended to provide additional detail beyond the
generic indication provided by the first 8 bits of status.
For information about the generic portion of the status, you must look at the
first 8 bits, described in the previous section.
The final (rightmost) 16 bits gives the subsystem number of the module
generating the status, or 0 if there was no error or warning.
MESSAGE: No error.
Level: 0 ($00)
CAUSE: The operation was successful. No error occurred.
ACTION: None
MESSAGE: Subsystem is opening link.
Level: 1 ($01)
CAUSE: An upper level subsystem has called the link module
configurator, which has successfully located configuration for the link,
and will now proceed to start it up.
ACTION: This event is informational. No action is
required.
MESSAGE: Driver is starting up.
Level: 2 ($02)
CAUSE: The driver has just completed initial configuration
and is now starting up.
ACTION: This event is informational.
No action is required.
MESSAGE: Driver is starting adapter card.
Level: 3 ($03)
CAUSE: The driver has completed initial startup of the adapter
card, or a restart following a reset, dump, or other recoverable condition.
ACTION: This event is informational.
No action is required.
MESSAGE: Driver is re-starting adapter card.
Level: 4 ($04)
CAUSE: The driver has completed a restart of the adapter
card, following a reset, powerfail, dump, or other recoverable condition.
ACTION: This event is informational.
No action is required.
MESSAGE: Link connected.
Level: 5 ($04)
CAUSE: The first upper layer subsystem to bind to the
driver triggered a link connect, which was successful. This event
is also logged after the link or cable has been successfully reconnected
after being disconnected, or on a link reconnect following a severe
line hit, hub power loss, or other recoverable error.
ACTION: This event is informational. No action is needed
unless the message appears frequently while the link is up, indicating
possible cabling problems; make sure cabling is securely connected
and properly routed away from sources of interference, and is of
the proper UTP category or grade for the type of link (CAT-5 UTP
100Base-T).
MESSAGE: Link disconnected.
Level: 7 ($07)
CAUSE: The last upper layer subsystem has unbound itself
from the driver, triggering a link disconnect. This event is also
logged if the link unexpectedly drops due to a cable disconnect,
hub power loss, severe line hit, or other recoverable error.
ACTION: This event is informational. No action is required
if the network is being shut down. However, if the link was supposed
to be up or the message appears frequently while the link is up,
this indicates possible cabling problems; make sure cabling is securely
connected and properly routed away from sources of interference,
and is of the proper UTP category or grade for the type of link
(CAT-5 for UTP for 100Base-T).
MESSAGE: Driver is shutting down.
Level: 8 ($08)
CAUSE: The driver is being shut down. The last subsystem
that was using the driver is now closing it.
ACTION: This event is informational.
No action is required.
MESSAGE: Subsystem is binding to link driver.
Level: 9 ($09)
CAUSE: An upper-layer protocol has successfully bound
(rendezvoused) to the link driver. Being bound means the driver
can now route incoming data frames to this protocol.
ACTION: This event is informational. No action is required.
If this is the first bind, the link driver will now attempt to reconnect
the link.
MESSAGE: Subsystem is unbinding from link driver.
Level: 10 ($0A)
CAUSE: An upper-layer protocol has begun to unbind (separate)
from the link driver. Once unbound, the driver can no longer route
incoming data frames to this protocol.
ACTION: This event is informational. No action is required.
If this is the last bind, the link driver will now attempt to disconnect
the link.
MESSAGE: Subsystem is closing link.
Level: 11 ($0B)
CAUSE: An upper level subsystem has called the link module
deconfigurator, which has successfully located the link, and will now
proceed to close it.
ACTION: This event is informational.
No action is required.
MESSAGE: Link driver and software were reset.
Level: 12 ($0C)
CAUSE: The link driver was told to reset, or automatically
reset itself following an error.
ACTION: None required, this status is informational only.
An upper layer protocol previously asked to be notified if a reset
occurred in the link driver, and such a reset has occurred, possibly
as a result of running diagnostics. However, an earlier error may
have also occurred.
MESSAGE: Powerfail detected.
Level: 13 ($0D)
CAUSE: The driver was notified of a power failure by
the I/O system, or detected all 1's on a hardware register
read, and, upon checking further, saw that its hardware I/O address
space was disabled, indicating a powerfail had already occurred.
ACTION: Powerfails should not be detected on PCI platforms (due to
UPS support). Verify secure and stable power connections to the system and
if the problem continues, contact your HP representative.
MESSAGE: Cannot release ADA memory object.
Level: 14 ($0E)
CAUSE: During shutdown, the driver requested the I/O system to
release a memory object, but received an error reply in response.
ACTION: This error should not occur. The driver may be confused,
or there is a system problem. However, the driver will ignore the error and
attempt to continue with the shutdown. If this happens frequently, see
Appendix A "Submitting a CR"
MESSAGE: Driver timed out waiting for ISR to shut down.
Level: 15 ($0F)
CAUSE: During link shutdown, the driver signaled the
ISR to shut down, then invoked the ISR. The driver then waited repeatedly
for the signal to clear, but it did not.
ACTION: This is an informational warning. The driver gave up
waiting, and continued with the rest of shutdown. If this happens
frequently, see
Appendix A "Submitting a CR"
MESSAGE: Retrying an operation.
Level: 16 ($10)
CAUSE: An operation which failed or timed out is being
tried again. Several retries may be required. If the operation never
succeeds, an error may be reported and another action taken.
ACTION: No action required, this status is informational
only.
MESSAGE: Cannot release a system plabel.
Level: 17 ($11)
CAUSE: During the final link-close operation by an upper
level subsystem, the link module deconfigurator encountered an error
while trying to release the link's write initiator procedure.
ACTION: This is an informational warning that some system memory
resources may have been lost. The module deconfigurator reported an error,
but attempted to continue with the close. If this happens every time, see
Appendix A "Submitting a CR"
MESSAGE: Cannot close NM logging.
Level: 18 ($12)
CAUSE: The link module configurator or deconfigurator attempted to
close access to the NM logging facility, but encountered an error.
ACTION: This is an informational warning that the logfile may
still be open. Use of the :SWITCHNMLOG command should not be
affected, however there may be a delay at system shutdown time. If this
happens every time, see
Appendix A "Submitting a CR"
MESSAGE: Cannot unfreeze a memory area.
Level: 19 ($13)
CAUSE: After previously freezing a data structure into system
memory, software encountered an error trying to unfreeze the same memory.
ACTION: This is an informational warning that some system memory
resources may have been lost. Software probably continued, ignoring the
error. Software may be confused, or the pointer to the memory area may have
been changed. If this happens every time, see
Appendix A "Submitting a CR"
MESSAGE: Abnormal interrupts detected by adapter card.
Level: 20 ($14)
CAUSE: While checking the cause of an adapter card interrupt, an
abnormal interrupt was found, such as transmit underflow, transmit jabber
timeout, receive buffer unavailable, or transmit or receive process stopped.
ACTION: This event is informational. No action is required. The
driver will attempt to recover and continue, sometimes with some frame loss
which the upper layer protocols may attempt to recover, depending on which
abnormal interrupts occurred. However, most of these interrupts should not
occur during normal operation, so if they are occurring frequently, see
Appendix A "Submitting a CR"
MESSAGE: No DMA buffer was available for a received frame.
Level: 22 ($16)
CAUSE: On receipt of an inbound data frame, the driver
attempted to dequeue a buffer from the inbound buffer cache for
one of the bound protocols, but the cache was empty.
ACTION: This is an internal warning. The driver may use
it to detect the need to request more buffers. Typically the inbound
frame is discarded in this case for flow control reasons, instead
of being queued.
MESSAGE: Cannot initiate a dump. Already dumping.
Level: 25 ($19)
CAUSE: A user attempted to force a driver dump while
a previous driver dump was still occurring.
ACTION: A dump of your problem is already being produced. Wait a
minute or two for the dump to finish. Forward the resulting
NETDMP##.PUB.SYS to Hewlett-Packard for analysis if necessary, and
see Appendix A "Submitting a CR"
MESSAGE: Internal error while initiating a dump. Dump failed.
Level: 26 ($1A)
CAUSE: During processing of some other fatal driver error,
the driver attempted a driver dump, but encountered an error.
ACTION: This error is mainly informational, since the driver did
not dump, but may be indicative of other, possibly-related problems. The
driver will still attempt to auto-reset itself, up to a total of 12 times
or more.
MESSAGE: Late dump-done message received. Dump took too long.
Level: 27 ($1B)
CAUSE: The driver received a driver-dump completion message
when it was not working on a dump.
ACTION: This error is informational only. Probably the
Network Dump Process was delayed by other system processing, such
that it exceeded the time limit set by the driver. The resulting
dump file may or may not be incomplete. A more serious driver problem
has already occurred, after which the driver will now attempt to
auto-reset and continue. If you are trying to reproduce a specific
problem but this error occurs every time, reduce the CPU or disk
activity load before the next attempt. If load is not the problem,
see Appendix A "Submitting a CR"
MESSAGE: A driver dump is starting.
Level: 28 ($1C)
CAUSE: A user is forcing a driver dump to occur, typically
via the VGPBA diagnostic tool program.
ACTION: This error is informational only. The dump is probably
being forced because the system operator suspects a link driver problem.
Forward the resulting NETDMP##.PUB.SYS file to Hewlett-Packard for
analysis if necessary, and see
Appendix A "Submitting a CR"
MESSAGE: A driver dump is starting.
Level: 29 ($1D)
CAUSE: The driver has requested a dump, and the dump
process is logging that the dump is about to occur. This is logged
during setup of the dump file.
ACTION: This error is informational only; however, the dump may be
occurring because the link driver detected other errors. Look for any other
errors logged by the link driver and note them. Forward the resulting
NETDMP##.PUB.SYS file to Hewlett-Packard for analysis if necessary,
and see
Appendix A "Submitting a CR"
MESSAGE: A driver dump was suppressed. Too many dumps already.
Level: 31 ($1F)
CAUSE: During processing of a fatal driver error, the
driver attempted a driver dump, but determined it had already dumped
too many times since it was initially started.
ACTION: By design, the driver attempts to auto-reset itself after
any driver dump. But after 3 dumps, to avoid uncontrollably filling disk
space with driver dumps, additional dumps are automatically suppressed. No
attempt is made to determine whether the dumps are duplicates of the same
problem. The driver did not dump, but will still attempt to auto-reset
itself, up to a total of 12 times or more. There is apparently something
wrong, since many driver dumps are occurring. Collect binary copies of all
dump files (NETDMP##.PUB.SYS) on tape for analysis by
Hewlett-Packard and see
Appendix A "Submitting a CR"
MESSAGE: Low on transmit descriptor resources.
Level: 34 ($22)
CAUSE: This status should not normally be logged externally.
It is designed for internal use by the driver to signal that either
no transmit descriptor was available when one was requested for
a transmit, or that a given transmit was segmented in too many places
and needs to be compacted prior to transmission.
ACTION: This status should not be logged externally, so if it is
seen, see Appendix A "Submitting
a CR"
MESSAGE: Received and discarded a long frame.
Level: 35 ($23)
CAUSE: When processing a frame reception, the link driver
found that the adapter has indicated the frame data spanned more
than a single descriptor, which is not allowed.
ACTION: This is a warning only; the driver automatically
reset the receive descriptors and continued. However, some frames
may have been lost. If the problem occurs often, use link tracing
to determine the source of the long frame transmissions.
MESSAGE: The link is already started.
Level: 39 ($27)
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator attempted to create a new
instance of the link driver, but discovered the driver was already created.
ACTION: This event is informational. No action is required. The
module configurator will ignore this warning and continue to bring the link
driver up, so that the number of users may be checked.
MESSAGE: Driver received an unknown port message.
Level: 41 ($29)
CAUSE: The driver received a port message which it does
not implement, or containing a function code which it does not implement.
ACTION: This is an informational error only. If this error
occurred as part of a driver reset operation, it may be ignored. The driver
did not attempt to return an error reply to the message sender. That sender
may now be hung, awaiting a reply. Attempt to determine what action caused
the error. Activate link tracing, reproduce the problem, then stop link
tracing and save the resulting NMTCnnnn.PUB.SYS trace data file.
See Appendix A "Submitting a CR"
MESSAGE: A received frame could not be delivered.
Level: 43 ($2B)
CAUSE: Just before delivering a received data frame to
an upper layer protocol, the driver found that the rendezvous table
entry specified in the buffer was not in the proper state.
ACTION: This is an internal error which detects a normal race
condition. Probably the protocol separated from the driver while a frame
destined for it was in motion. The frame was not delivered, and the buffer
was silently released. No action is required.
MESSAGE: Link tracing is already enabled.
Level: 46 ($2E)
CAUSE: The driver received a request to turn link tracing
on when it was already on.
ACTION: This event is informational. No action is required.
An error reply was sent in response to the request. Trace was not
started by this request this time, but it remains on.
MESSAGE: Link tracing is already disabled.
Level: 47 ($2F)
CAUSE: The driver received a request to turn link tracing
off when it was already off.
ACTION: This event is informational. No action is required.
An error reply was sent in response to the request. Trace was not
stopped by this request this time, but it remains off.
MESSAGE: Driver encountered a hardware problem.
Level: 50 ($32)
CAUSE: This is a generic hardware error, reported when
any of the driver's hardware access routines reports an
error. By itself it is not descriptive of the problem. This error
is often seen as a result of previous power failures, MII or EEPROM
read/write errors, or other low-level hardware problems.
ACTION: When this error occurs as a result of previous
errors, it mainly serves as a way to track the sequence of the failure
back to what was happening at the time. Check for those errors and look
them up for an additional explanation of the problem.
MESSAGE: Bad hardware ID or path.
Level: 51 ($33)
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator did not find a supported
PCI 100Base-T adapter card at the hardware path specified in NMCONFIG.
ACTION: Verify the path in NMCONFIG is correct and complete,
and matches the path where a supported PCI 100Base-T adapter card
is installed in the computer backplane. Verify the Power LED is
lit on that adapter. If necessary, reseat the board or contact your
Hewlett-Packard Representative for hardware assistance.
MESSAGE: Adapter card reported an fatal bus error.
Level: 52 ($34)
CAUSE: The driver's ISR module awoke to process
a DVR request or an interrupt, but after reading status from the
adapter card, the driver discovered a fatal error bit had been set.
ACTION: The adapter card or system I/O hardware may have
failed. Contact your Hewlett-Packard Representative for hardware
assistance.
MESSAGE: Unable to read from adapter card PCI configuration space.
Level: 54 ($36)
CAUSE: During driver startup, during a restart following
a reset operation, of during processing of a utility register-read
request, the driver called the I/O system to read data from an adapter
PCI configuration space register, but the UI/O system reported an error.
ACTION: The adapter card may have been removed, moved
to a different slot, may not be making the proper contact with the
PCI backplane, or may not be responding. I the I/O slot has a power
on indicator, verify that it is on. Re-seat the board, or if necessary,
contact your HP representative for hardware assistance.
MESSAGE: Driver could not identify the expected PHY on card.
Level: 55 ($37)
CAUSE: After verifying the PHY chip on the adapter card
had been successfully reset, the driver checked the ID of the PHY,
but found it did not match any ID expected for this kind of adapter card.
ACTION: Replace the adapter card.
MESSAGE: Unable to write to adapter card PCI configuration space.
Level: 56 ($38)
CAUSE: During driver startup, during a restart following
a reset operation, or during processing of a utility register-write
request, the driver called the I/O system to write data to an adapter
PCI configuration space register, but the I/O system reported an error.
ACTION: The adapter card may have been removed, moved
to a different slot, may not be making the proper contact with the
PCI backplane, or may not be responding. If the I/O slot has a power
on indicator, verify that it is on. Re-seat the board, or if necessary,
contact your HP representative for hardware assistance.
MESSAGE: MII read error on adapter card.
Level: 57 ($39)
CAUSE: During a link connect, disconnect, or management
operation, the driver attempted to read from an MII hardware register
in a PHY chip on the adapter card, but the read failed to return
the proper acknowledgment bit. This indicates good data was not returned.
ACTION: MII reads can be sensitive to software timing.
If you have GLANCE or a similar tool, run it and check the CPU load
on the system. If the load is high, try reducing the CPU load, then
retry the operation. If the problem persists, the adapter card has
probably failed; replace the adapter card.
MESSAGE: EEPROM read error on adapter card.
Level: 58 ($3A)
CAUSE: During link startup or a diagnostic operation,
the driver attempted to read from an EEPROM non-volatile storage
chip on the adapter card, but the read failed to return one of the
necessary acknowledgment bits. This indicates good data was not returned.
ACTION: EEPROM reads can be sensitive to software timing.
If you have GLANCE or a similar tool, run it and check the CPU load
on the system. If the load is high, try reducing the CPU load, then
retry the operation. If the problem persists, the adapter card has
probably failed; replace the adapter card.
MESSAGE: Adapter card PHY did not finish reset in the time allowed.
Level: 60 ($3C)
CAUSE: During a link connect sequence, the driver tried 3 times to
reset the PHY chip, but it still did not go "ready" after the reset.
ACTION: This is a fatal hardware error. Replace the adapter
card. The driver cannot connect the link if the PHY will not reset.
If the problem persists with a known good card, see
Appendix A "Submitting a CR"
MESSAGE: No adapter card found on specified PCI bus.
Level: 62 ($3E)
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator did not find an PCI bus
at the hardware path specified in NMCONFIG.
ACTION: Verify the path in NMCONFIG is correct and complete, and
matches the path where a supported PCI 100Base-T adapter card is installed
in your computer backplane. If necessary, change NMCONFIG or specify the
correct path. The driver automatically configures software to drive any
high-level bus converters leading to that path, so there should be no need
to install them in SYSGEN, but check SYSGEN for possible path conflicts.
If necessary, contact your Hewlett-Packard Representative for assistance
in determining paths or correcting bus hardware problems.
MESSAGE: Adapter card found does not match software configuration.
Level: 63 ($3F)
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator found a supported adapter
card at the path specified in NMCONFIG, but it was not the right
type of card for the link being started.
ACTION: Correct the network configuration or plug in the
correct type of adapter card, and retry the operation.
MESSAGE: Cannot install interrupt handler.
Level: 75 ($4B)
CAUSE: During initial driver startup, the driver was
unable to add its ISR into the MPE I/O system, as an interrupt handler
routine for any adapter card interrupts on that EIR bit.
ACTION: The driver did not start up. There is probably
an MPE software installation problem, with incomplete or incompatible
O/S software. Verify that the I/O path specified for the adapter
card for a supported adapter. The only other cause is a software bug; see
Appendix A "Submitting a CR"
MESSAGE: Cannot get ADA memory object.
Level: 76 ($4C)
CAUSE: During initial startup, the driver attempted to
obtain a memory object via the I/O system, but received a bad status
in the reply for that request.
ACTION: Probably the amount of frozen memory on the system
is very high; if you have the GLANCE tool you can try to check memory
usage. Try retrying the operation again later, or first terminate
some applications and then retry.
MESSAGE: Cannot reset a system timer.
Level: 78 ($4E)
CAUSE: The driver attempted to get a system timer from
I/O Services but encountered an error. This is either caused by
exhausting all timers due to heavy system load, or by system software
either failing to release timers, or having some other bug.
ACTION: This is a fatal software error. The number of available
timers is not configurable, and the driver cannot operate without the
necessary timers. Typically followed by another error giving more
information about what kind of timer the driver needed; check log data for
that, see
Appendix A "Submitting a CR"
MESSAGE: Cannot free a system timer.
Level: 79 ($4F)
CAUSE: The driver attempted to release a system timer
previously obtained from I/O Services but encountered an error.
This is likely caused by a bug in system software, or by corruption
of the driver's PDA context memory.
ACTION: This is a warning that some timer resources may have been
lost. Possibly followed by another error giving more information about what
kind of timer the driver was releasing; check log data for that error and
look it up also. If the problem happens every time, see
Appendix A "Submitting a CR"
MESSAGE: Cannot send a port message.
Level: 80 ($50)
CAUSE: This is a generic error saying that the link driver,
module configurator or deconfigurator, or other module of the link
subsystem encountered an error when trying to send a port message.
This error could be caused by the target module having been already
shut down. It could also be an indication of a more serious system
software problem, and may be followed by a system abort; probably all
message frames have been exhausted by some module running on the system.
ACTION: Severity and side effects of this error are dependent upon
the purpose of the message that was not sent. Attempt to determine the
conditions that led to the error. If it occurred during a shutdown,
possibly this error can be ignored. Otherwise, if the same problem happens
repeatedly, or if a system abort occurs, take a memory dump and
see Appendix A "Submitting a CR"
MESSAGE: Error from upper layer protocol read completor.
Level: 81 ($51)
CAUSE: The driver finished transferring a data frame
and passed it to an upper layer protocol, but the protocol's
read completor returned an error which was not one of the expected,
legal errors the driver was able to handle.
ACTION: This is an informational error only. The driver
incremented a statistic then attempted to continue. However, the
protocol may not have received the inbound frame, therefore some
applications could be hung. There may be a problem in the upper
layer protocol. If the problem occurs frequently, take a link trace
showing the problem, then see
Appendix A "Submitting a CR"
MESSAGE: Cannot load driver plabel.
Level: 84 ($54)
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator encountered an error while
trying to load the code for the driver.
ACTION: Probably not all software required to operate
this type of link is installed. The software was incorrectly installed,
or you may need to purchase additional link or MPE software or install
newer patches. Reinstall the link software or contact your
Hewlett-Packard Representative for assistance.
MESSAGE: Cannot add driver to I/O system.
Level: 85 ($55)
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator attempted to create a new
instance of the link driver, but encountered an error which was
not one of the legal errors the configurator was able to handle.
ACTION: Verify the path in NMCONFIG is correct and complete,
and matches the path where a supported PCI 100Base-T adapter card
is installed in your computer backplane. If necessary, change NMCONFIG to
specify the correct path, so there should be no need to install
them in SYSGEN, but check SYSGEN for possible path conflicts. If
necessary, contact your Hewlett-Packard Representative for assistance
in determining paths or correcting bus hardware problems.
MESSAGE: Cannot remove driver from I/O system.
Level: 86 ($56)
CAUSE: During the final link-close operation by an upper
level subsystem, the link module deconfigurator attempted to delete
an instance of the link driver, but encountered an I/O system error.
ACTION: Not all resources were released. The driver may
already have been shut down by some other means, or the system I/O
configuration may have been altered. If this happens frequently,
see Appendix A "Submitting a CR"
MESSAGE: Cannot load a system routine.
Level: 87 ($57)
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator encountered an error while
trying to load code for the write initiator procedure needed for
the link type configured in NMCONFIG.
ACTION: Probably not all software required to operate
this type of link is installed. Software was incorrectly installed,
or you may need to purchase additional software or install newer
patches. Reinstall the software or contact your Hewlett-Packard
Representative for assistance.
MESSAGE: Cannot open NM logging.
Level: 88 ($58)
CAUSE: During a link open attempt by an upper-level subsystem,
the link module configurator encountered a positive (error) status
when trying to open NM logging against the link's subsystem ID.
ACTION: This event is informational. No action is required.
The module configurator cleared the error and will attempt to continue.
However, NM logging may not be available to the link. You may need
to install new NM logging patches. If the problem occurs every time,
see Appendix A "Submitting a CR"
MESSAGE: Cannot freeze a memory area.
Level: 89 ($59)
CAUSE: This is a generic error that during a link-open
or some other operation by an upper level subsystem, link software
encountered an error while trying to freeze some data into memory
before passing the driver a pointer to that data.
ACTION: The system may be low on available memory. Try closing any
unnecessary applications or sessions and retry the
operation.
MESSAGE: Did not receive an expected port message.
Level: 90 ($5A)
CAUSE: This is a generic error that during a link-open
or some other operation by an upper level subsystem, link software
sent a port message to the driver, then encountered an error while
awaiting the correct reply message.
ACTION: Severity and side effects of this error are dependent
upon the purpose of the message that was not received. There may
be a system problem with message ports, or the link driver may have
sent the wrong reply message. If this happens every time, see
Appendix A "Submitting a CR"
MESSAGE: Could not releas4 an I/O virtual address.
Level: 94 ($5E)
CAUSE: After successfully allocating an I/O virtual address
and saving it, the driver encountered an error while trying to release
that same address later on.
ACTION: The driver will attempt to continue, and it will
attempt to log the error unless a system abort occurs first. If
the problem occurs repeatedly, too many system I/O resources may
become lost; take a memory dump and see
Appendix A "Submitting a CR"
MESSAGE: Could not allocate or reassign an I/O virtual address.
Level: 95 ($5F)
CAUSE: The driver attempted to allocate a new I/O virtual
address (to describe a temporary data buffer in memory which would
be referenced by the adapter card), or reassign an I/O virtual address
previously allocated to a different block of memory, but the I/O
system reported an error.
ACTION: If this error was logged, it means that I/O virtual
address was required for normal operation so acquisition cannot
be delayed. The driver cannot continue, but will attempt to log
the error unless a system abort occurs first. Probably the system
is out of I/O virtual addresses. You may need to start fewer links
and/or mass storage devices, move some adapter cards onto different
I/O buses, or add more I/O buses to the system.
MESSAGE: Unable to autoconfigure underlying I/O paths.
Level: 96 ($60)
CAUSE: During startup, the driver asked the I/O system to start
I/O drivers for each higher-level bus component leading to the configured
path of the 100Base-T adapter card, but encountered an error.
ACTION: Check the cardcage and/or run an I/O map utility to verify
the correct 100Base-T I/O path was specified in the NMCONFIG file. Ensure
the 100Base-T path ends in "/0/0". Run SYSGEN and check entry I/O context.
Verify the I/O path is not already configured for a different kind of
device; if so, modify and save the configuration, and reboot the system. If
none of this helps, contact your Hewlett-Packard Representative for
assistance.
MESSAGE: Link common reported an inbound buffering problem.
Level: 98 ($62)
CAUSE: Varies. Usually related to an underlying error
condition or resource contention problem in the buffer manager.
ACTION: See
Appendix A "Submitting a CR"
MESSAGE: Link common reported a receive processing problem.
Level: 99 ($63)
CAUSE: Varies. The driver encountered an error condition
when attempting to bind with an upper layer protocol.
ACTION: Check the log file for additional errors related to a
specified sublocation in the code, and look up those sublocation errors for
more specific information, see
Appendix A "Submitting a CR"
MESSAGE: Link common reported a protocol bind problem.
Level: 100 ($64)
CAUSE: Varies. The driver encountered an error condition
when attempting to bind with an upper layer protocol.
ACTION: Check the log file for additional errors related
to a specific sublocation in the code, and look up those sublocation
errors for more specific information, see
Appendix A "Submitting a CR"
MESSAGE: Link common reported a protocol unbind problem.
Level: 101 ($65)
CAUSE: Varies. The driver encountered an error condition
when attempting to unbind from an upper layer protocol.
ACTION: Check the log file for additional errors related to a
specific sublocation in the code, and look up those sublocation errors for
more specific information. The link may be shutting down or may perform an
auto-reset as part of the error recovery. If the problem persists, see
Appendix A "Submitting a CR"
MESSAGE: General buffer manager error encountered.
Level: 105 ($69)
CAUSE: The driver encountered an unexpected error either
from the buffer manager (such as when trying to copy received loopback
data to a return buffer), when calling the Link Common module to
do a buffer related operation (such as refill an inbound buffer
cache), or when obtaining a required buffer.
ACTION: Depending on the error, the driver may attempt
to continue, however some data may not have been transferred, a
protocol may now be low on buffers, etc. If the error did not prevent
driver startup, try stopping and restarting the network. If the
problem persists, see
Appendix A "Submitting a CR"
MESSAGE: General error trying to get a buffer.
Level: 106 ($6A)
CAUSE: When attempting to directly obtain a new buffer
manager buffer from a read pool, to replenish the inbound buffer
cache for one of its bound protocols, the driver's ISR
encountered an error that was not one of the few legal errors it
expected, or was able to handle.
ACTION: The problem could indicate some serious internal problems
within the buffer manager or its data structures, or with the way the
system is configured. Note all log messages, especially the "Cause" status
for this error, and see Appendix A "Submitting a CR"
If the problem persists, take a system memory dump immediately after the
problem has occurred.
MESSAGE: Cannot create a buffer pool.
Level: 107 ($6B)
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator encountered an error while
trying to create an outbound buffer pool or control buffer pool.
ACTION: The system may be low on available memory. Try stopping
some applications or sessions and retry the operation. If the problem
persists, stop all networking and restart it, or restart the system. The
buffer size and pool size are not configurable. If the problem still
occurs, there could be a problem with the buffer manager. See
Appendix A "Submitting a CR"
MESSAGE: Cannot delete a buffer pool.
Level: 108 ($6C)
CAUSE: During a link-close operation by an upper level
subsystem, the link module deconfigurator encountered an error while
trying to delete an outbound buffer pool or control buffer pool.
ACTION: This is an informational warning that some system
memory resources may have been lost. Probably not all buffers were
freed before the pool was deleted. If this happens every time, see
Appendix A "Submitting a CR"
MESSAGE: Driver encountered a software problem.
Level: 115 ($73)
CAUSE: This is a generic software error, reported when
any of the driver's non-hardware routines reports an error.
By itself it is not descriptive of the problem. This error is often
seen as a result of previous errors from intrinsics, reply messages,
or validity checks.
ACTION: When this error occurs as a result of previous
errors, it mainly serves as a way to track the sequence of the failure
back to what was happening at the time. Check for those errors and look
them up for an additional explanation of the problem.
MESSAGE: Internal driver error.
Level: 116 ($74)
CAUSE: While processing a request, the link driver encountered
a problem indicating there is something internally wrong with some other
module of system software. Specific instances include: range or bounds
violation errors while storing or clearing a statistics buffer.
ACTION: This is an indication of a bug in the link software. If
possible, note exactly what actions caused the error to occur, then see
Appendix A "Submitting a CR"
MESSAGE: A driver request failed.
Level: 117 ($75)
CAUSE: This is a generic software error, used when the
driver receives a new request but cannot process it because of an
earlier failure. It is used in the reply to the outside module which
requested the operation, to indicate it could not be processed.
ACTION: If this status is reported, it is because of some
earlier failure. Check log files and locate any previous errors
for this link, to try to find the reason this error is now occurring.
By running the VGPBA diagnostic and trying the Reset function, you
may be able to clear the error.
MESSAGE: Serious error encountered while trying to start heartbeats.
Level: 118 ($76)
CAUSE: During startup, the link driver was unable to
obtain a system timer resource for use in periodic monitoring of
the health of the adapter card and link connection. This is either
caused by exhausting all timers due to heavy system load, or by
system software either failing to release timers, or having some other bug.
ACTION: This is a fatal software error. The number of available
timers is not configurable, and the driver cannot operate reliably without
the ability to monitor the card. The same problem will likely prevent
attempts to get other required timers also. If you suspect a heavy load,
you can try shutting some processes down, then restart the driver.
Otherwise halt the system, take a memory dump, and reboot, see
Appendix A "Submitting a CR"
MESSAGE: Driver dump was forced.
Level: 119 ($77)
CAUSE: A user is forcing a driver dump to occur, typically
via the VGPBA diagnostic tool program.
ACTION: This error is informational only. The dump is probably
being forced because the system operator suspects a link driver problem.
Forward the resulting NETDMP##.PUB.SYS file to Hewlett-Packard for
analysis if necessary, and see
Appendix A "Submitting a CR"
MESSAGE: Driver is going down.
Level: 121 ($79)
CAUSE: A request to the driver failed because the driver
is in the process of shutting down, or because it has encountered
a fatal software error and has not yet been shut down.
ACTION: If this status is reported during a shutdown operation,
it may be ignored. Otherwise this should be a signal to the operator
that the link driver has a problem and needs to be shut down, or
dumped and/or reset.
MESSAGE: Driver has detected data corruption.
Level: 125 ($7D)
CAUSE: The link driver encountered conditions which should
only occur if memory structures have been corrupted. For example,
following a full reset of the driver data structures, the next transmit
resource obtained was not the first in the list.
ACTION: These errors are extremely serious. The driver
halted operations and attempted to capture a snapshot dump of the
problem. The trouble may or may not be the fault of the link driver;
another application on the system could be walking on memory. Collect
all NETDMP##.PUB.SYS dump files and see
Appendix A "Submitting a CR"
MESSAGE: Illegal access to saved port message area.
Level: 128 ($80)
CAUSE: While completing an old blocking request (requiring a
driver exit and later reply), the driver found that the entry in the
pending message save area, where the request was supposedly saved, was no
longer in use, or was not within the range of legal table indexes.
ACTION: This fatal software error is only caused by a
bug or memory corruption, because the driver should never be trying
to complete the same message twice, or passing an illegal index.
After reporting this error, the driver will die, then will either
attempt an auto-reset or else require a manual shutdown and restart.
If the problem persists, take a link trace of the problem, then
see Appendix A "Submitting a CR"
MESSAGE: Cannot read current multicast list.
Level: 130 ($82)
CAUSE: During a link-open or close operation by an upper
level subsystem, the link module configurator tried to read the
current list of multicast addresses produced by the subsystem, but
encountered an error on the read.
ACTION: Try starting a different link, to see if the same errors
occur. Next try restarting the system, and retry the operation. If the
problem persists, you may need to install Link Common patches (Link Common
contains the multicast services) or obtain newer 100Base-T patches; contact
your Hewlett-Packard Representative for assistance.
MESSAGE: An unexpected timeout occurred.
Level: 131 ($83)
CAUSE: This is a generic error reporting that a timeout
occurred during a link driver operation, such as a diagnostic loopback
test or a dump operation, or while awaiting a reply message from
the driver for an operation initiated by the link module configurator
or deconfigurator.
ACTION: A required message or interrupt has not arrived in time.
Reset the link driver using VGPBA diagnostics, or shut it down and restart.
Retry the operation. If the same problem occurs, replace the adapter card
if this is a loopback test, otherwise check system load or see
Appendix A "Submitting a CR"
MESSAGE: Module Configurator cannot access its context area.
Level: 132 ($84)
CAUSE: During a link-close operation by an upper level
subsystem, the link module deconfigurator checked its context memory
area for validity, but did not find the expected data.
ACTION: The module deconfigurator's context memory area is being
overwritten, or is not working properly. The deconfigurator did not perform
the close. If this happens every time, wait until the next time the link is
to be closed; instead of closing the link, halt the system and take a
memory dump, and see
Appendix A "Submitting a CR"
MESSAGE: Open table full. Too many driver users.
Level: 147 ($93)
CAUSE: Too many subsystems are attempting to open the driver at
the same time, or subsystems are shutting down without closing the driver.
ACTION: Shut down any networking subsystems that are not currently
needed and try again. A side-effect of this error may be that the driver
becomes unusable; if so, run VGPBA and execute the Reset function to see
if that restores normal operation.
MESSAGE: Pending message table full. Driver not finishing fast enough.
Level: 150 ($96)
CAUSE: While processing a new blocking request (requiring
a driver exit and later reply) and scanning a table in which to
save the request, the driver found an unused entry, but an entry
counter indicated the table was full.
ACTION: This fatal software error is only caused by a
bug, because the in use flags and counters should match. After reporting
this error, the driver will die, then will either attempt an auto-reset
or else require a manual shutdown and restart. If the problem persists,
take a memory dump and reboot. See
Appendix A "Submitting a CR"
MESSAGE: Out of internal comm frame resources.
Level: 151 ($97)
CAUSE: While attempting to request action from its ISR module, the
driver found that no available communication frames were available on the
referenced queue. The number of available comm frames is not configurable,
and the driver cannot operate if frames run out.
ACTION: This is a fatal software error. After reporting this error,
the driver will attempt a driver dump, then will auto-reset and attempt to
continue. Typically followed by another error giving more information about
what kind of comm the driver was trying to send; check log data for that
error and look it up also. Collect binary copies of all
NETDMP##.PUB.SYS dump files on tape for analysis by
Hewlett-Packard and see
Appendix A "Submitting a CR"
MESSAGE: Driver initialization failed.
Level: 152 ($98)
CAUSE: While processing its very first startup message,
the driver encountered a problem. Probably the configured hardware
is not present, is not the correct kind of adapter card, or there
was a problem configuring the ISR into the I/O system or binding
to the lower bus manager. The link is unusable.
ACTION: This informational error should be preceded by
another error giving a more specific reason for the failure; check
log data for that error and look it up also, for more actions to
take. The driver will attempt to send an error reply for the startup
request. It then enters a "broken" state and awaits a shutdown, which the
module configurator should attempt automatically.
MESSAGE: Configuration failed.
Level: 154 ($9A)
CAUSE: This is a generic error, reported after successful
or unsuccessful completion of initial hardware startup, if the driver
encountered an error bringing up the adapter card, or when opening
the link, or while attempting to send the reply to a pending configuration
request from its module configurator.
ACTION: This is a fatal software error. It might be caused
by a bad adapter card, by having too many driver users, by a heavy
CPU load, or by attempting to operate the network subsystem or tool
which started the link at too low of a CPU process priority, causing
a timeout. Any condition, such as a timeout or abort, which causes
the driver's module configurator to cease awaiting the
reply and dispose of its reply port, might also cause this error.
The driver now "dies" and awaits a shutdown, which
the module configurator should attempt automatically.
MESSAGE: Heartbeat timeout. Adapter card appears to be hung.
Level: 160 ($A0)
CAUSE: The LAN controller chip on the adapter card has
failed to produce any interrupt from normal activity for over 5
seconds. It has also failed, for an additional 5 seconds, to respond
to the driver's inquiry by producing a test interrupt.
The driver has decided the card is dead or hung.
ACTION: This is a fatal hardware error. Replace the adapter
card. The driver will enter a "broken" state and
await a manual shutdown by the operator. If you wish you may try
running the VGPBA diagnostic and attempt a reset. If the problem
persists with a known good card, see
Appendix A "Submitting a CR"
MESSAGE: Card did not go ready after hard reset.
Level: 161 ($A1)
CAUSE: After performing a hard reset of the adapter card
during startup, the HP-PB interface chip did not report "ready" status,
or reported an error.
ACTION: Replace the adapter card. If the same problem
persists even after replacement with a known good card, contact
Hewlett-Packard: your software could be out of date, but a patch
may be available. It is unlikely this would be caused by a system
HP-PB bus hardware problem.
MESSAGE: Hub did not report link up within time allowed.
Level: 170 ($AA)
CAUSE: During a link connect attempt, the driver instructed
the link interface chip to connect, but afterward the LINK signal
still did not appear within the 3 second time allowed. The hub may
not have liked some or all of the frames, although it responded
anyway. If this error is logged, it is because the link did not
connect within 25 to 30 seconds after it was instructed to do so.
ACTION: This error is informational only. The driver will
retry the connect. If the problem happens every time, try checking
the hub port configuration, or replacing the cable and/or adapter
card.
MESSAGE: Timeout while awaiting link autonegotiation completion.
Level: 175 ($AF)
CAUSE: The link appears to be connected, but the driver
thinks it is still waiting for it to connect.
ACTION: This error should not occur. If it happens frequently,
see Appendix A "Submitting a CR"
MESSAGE: Driver bug prevents link training. File CR.
Level: 183 ($B7)
CAUSE: During an attempt to establish the proper stack
context within which to begin 100VG-AnyLAN link training, the driver
tried repeatedly to run without the ISR underneath it, but failed
to even after 4 retries.
ACTION: Shut down the link and restart it. If the same problem
still occurs, see
Appendix A "Submitting a CR"
MESSAGE: Autonegotiation reports link settings are incompatible with hub.
Level: 188 ($BC)
CAUSE: If this error occurs, it is probably because the
link has reported a remote fault. Usually this means the adapter
card and the hub or switch to which it is connected, have failed
to agree on a link speed and duplex setting acceptable to both.
ACTION: Verify that the cable is securely connected to
the adapter card at one end, and to a 100Base-TX or 10Base-T hub
at the other. Verify the cable is a correctly wired, Category-5
UTP cable. Category 3 or 4 cables are not acceptable. If a crossover
cable is being used, make sure it is correctly wired. Check the
configuration of the hub or switch port to which the adapter card
is connected. Adjust that configuration and, if necessary, use NMMGR
to adjust the configuration of the link, so that something will
match. If necessary, specify a forced speed and duplex setting,
and disable autonegotiation, at both ends.
MESSAGE: Unexpected loss of link signal from hub.
Level: 194 ($C2)
CAUSE: While the link was supposedly connected, an event
occurred causing the link driver to check if the link was connected,
and when the PHY chip on the adapter card was checked, it was found
that the link was not connected. Probably the cable was disconnected
from the hub or card.
ACTION: This event is informational. No action is required. The
driver will attempt to reconnect the link automatically.
MESSAGE: Cannot open configuration file.
Level: 198 ($C6)
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator encountered an error while
trying to open the configuration file.
ACTION: Verify an NMCONFIG.PUB.SYS file exists. If so,
try to verify its format matches rest of the operating system. If the
system was updated, you may need to run NMMGRVER.PUB.SYS to
convert the file to a newer format. If the system was backdated, you may
need to restore an older copy of NMCONFIG from a backup tape. Perform a
:LISTF,3 command and make sure the file is not protected by a
lockword, and that the user starting the link has the necessary access
rights to open the file. Perform a :DSTAT ALL command and make sure
the disk drive the file resides on is present and mounted. Make sure the
file resides on Ldev 1. If not, use Fcopy and a file equation with a
";DEV=1" option to force a copy of the file onto Ldev 1. Perform a
:SHOWPROC 1;TREE;SYSTEM command and verify an NMFILE process exists.
If not, shut down and restart the system, and retry the operation. If the
problem persists, contact your Hewlett-Packard Representative for
assistance with NMCONFIG file open problems.
MESSAGE: Cannot read from configuration file.
Level: 199 ($C7)
CAUSE: During a link-open operation by an upper level subsystem,
the link module configurator was able to open the configuration file, but
encountered an error while trying to read data for the link being started.
ACTION: Using NMMGR, verify the path LINK.linkname exists
in the NMCONFIG file and is the exact same linkname which
is now being started. Verify the "Data=Y" flag is set at the top
of that LINK screen (meaning that ENTER has been pressed to save the
configuration data there). If the link is being used with NS or DTS, use
the VALIDATE function to validate the network configuration. Correct any
configuration errors and retry the operation.
MESSAGE: Cannot validate configuration file.
Level: 200 ($C8)
CAUSE: After successfully reading configuration data
for a link being started, the link module configurator checked the
data and found it was not valid. For NS/3000, probably the link
type and NI type do not match.
ACTION: Using NMMGR, verify the path LINK.linkname exists
in the NMCONFIG file and is either a 100Base-T link type. If the subsystem
being started is NS, verify the link type matches the NI type for the
network being started. If these are not the problem, an incorrect version
of NMMGR may have been used to create the NMCONFIG file on your system. Run
NMMAINT.PUB.SYS;PARM=24 to check versions of NMMGR components. The
format of your NMCONFIG file may be incompatible with the link driver
version installed on your system. Run NMMGRVER.PUB.SYS to update
your NMCONFIG file to a newer version, or restore an older version from a
backup tape, whichever is appropriate. If the problem still occurs, contact
your Hewlett-Packard Representative for assistance in using NMMGR to
configure 100Base-T links.
MESSAGE: Cannot determine link type.
Level: 203 ($CB)
CAUSE: Early in a link open operation by an upper level
subsystem, the link module configurator encountered an error while
attempting to use Link Support Services to determine the type of
link being started. Probably the link is not completely configured.
ACTION: If the link is already started, LSS tries to read the link
type from its own link table. Otherwise, it tries to read it from the
NMCONFIG file. Using NMMGR, verify the path LINK.linkname exists
in the NMCONFIG file and is the exact same linkname which
is now being started. Verify the "Data=Y" flag is set at the top
of that LINK screen (meaning that ENTER has been pressed to save the
configuration data there). If the link is being used with NS or DTS, use
the VALIDATE function to validate the network configuration. Correct any
configuration errors and retry the operation.
MESSAGE: Cannot read from link table.
Level: 204 ($CC)
CAUSE: Early in a link open operation by an upper level
subsystem, the link module configurator attempted to determine if
the link was already running, by trying to read from the link table,
but an error occurred which was not one of the expected, legal errors
the configurator was designed to handle.
ACTION: If the linkname being started is a valid linkname,
then there may be a problem with Link Support Services. Halt the
system, take a system memory dump, then restart the system. If the
problem still occurs, see
Appendix A "Submitting a CR"
MESSAGE: Cannot add to link table.
Level: 205 ($CD)
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator successfully started the
driver, but encountered an error trying to add the link to the link table.
ACTION: Possibly too many links are started. If not, try starting
a different link, to see if that works. If not, first try doing a
:LINKCONTROL @ command to see if any LSS errors occur. If they do,
you may need to reinstall MPE software; contact your Hewlett-Packard
Representative for assistance. Otherwise try restarting the system to see
if it corrects the problem or LINKCONTROL errors. If none of these
suggestions helps, see
Appendix A "Submitting a CR"
MESSAGE: Cannot delete from link table.
Level: 206 ($CE)
CAUSE: During the final link-close operation by an upper
level subsystem, the link module deconfigurator attempted to delete
the link from the link table, but encountered an error.
ACTION: The module deconfigurator reported an error, but
attempted to continue with the close. Network management services
may have been shut down. Otherwise, if this happens every time,
see Appendix A "Submitting a CR"
MESSAGE: Cannot open tracing.
Level: 208 ($D0)
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator found that the link was
configured to enable tracing at startup, but encountered an error
trying to open the trace file.
ACTION: Using NMMGR, check if a filename was configured. If so,
verify it is a legal MPE filename. A group and account may need to be
specified. Make sure the user starting the link has the necessary
capabilities to create that file in the group and account specified. Check
whether the system is low on disk space. Check whether too many
NMTCnnnn.PUB.SYS trace data files already exist. Purge files as
necessary to free up disk space, or add more disks. Make sure the version
of the NMCONFIG file matches the rest of the system software, by running
NMMGRVER.PUB.SYS. If none of these suggestions solves the problem,
contact your Hewlett-Packard Representative for assistance with configuring
a 100Base-T link to enable tracing at startup.
MESSAGE: Cannot stop tracing.
Level: 209 ($D1)
CAUSE: After a link-open operation by an upper level
subsystem failed, the link module configurator tried to clean up,
but encountered an error trying to disable driver tracing.
ACTION: Probably the link driver returned an error reply
when asked to disable tracing. The driver may have a problem, or
may already have shut down. Check for other, driver-specific error
messages which may give more information about the problem, and
look them up also. If no other errors are found, see
Appendix A "Submitting a CR"
MESSAGE: Cannot send a trace request.
Level: 210 ($D2)
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator found that the link was
configured to enable tracing at startup. After successfully opened
a trace file, the configurator encountered an error trying to enable
driver tracing.
ACTION: Probably the link driver returned an error reply
when asked to enable tracing. The driver may have a problem. Check
for other, driver-specific error messages which may give more information
about the problem, and look them up also. If no other errors are
found, see
Appendix A "Submitting a CR"
MESSAGE: Unimplemented operation attempted.
Level: 218 ($DA)
CAUSE: The driver was asked to, or attempted to perform
an operation which it is not currently designed to handle.
ACTION: If possible, the driver will attempt to send an
error reply in response to the request. However, depending on the
operation, the driver may not know how to do this, and will not
attempt it. Determine what you were trying to do, then contact your
Hewlett-Packard Representative for assistance.
MESSAGE: Buffer chaining is not supported.
Level: 220 ($DC)
CAUSE: An upper layer protocol attempted to send data
to the driver using a buffer containing chained data. No link subsystems
support this data format.
ACTION: There is a problem in the upper-layer protocol.
Attempt to determine which application produced the error, then
see Appendix A "Submitting a CR"
MESSAGE: One or more bad bind parms passed by upper level protocol.
Level: 223 ($DF)
CAUSE: This is a generic error, reported when the driver
received a bind (rendezvous) from an upper layer protocol, but the
parameters in the request were not satisfactory to the driver. There
are a number of separate causes; look up the specific sublocation
code that was logged, for more information.
ACTION: All such errors are caused by bugs in the upper
layer protocol. Attempt to determine what protocol was trying to
bind, then see
Appendix A "Submitting a CR"
MESSAGE: A data buffer is too long.
Level: 224 ($E0)
CAUSE: During diagnostic loopback testing, the driver
was asked to prepare a data block for transmission, but the block
length or memory allocation was beyond the driver's DMA capabilities.
ACTION: This problem should only be seen in diagnostics, however
it should not be occurring at all. Specify a shorter loopback length, and
see Appendix A "Submitting a CR"
MESSAGE: One or more bad utility parms passed to driver.
Level: 225 ($E1)
CAUSE: The driver received a utility register access
request from an upper level tool program such as LNKUTIL, but the
register number specified was out of the range of legal register
values for the selected register set.
ACTION: This is an informational error only. This problem
most likely occurred while diagnosing some previous problem. Retry
the operation using a legal register number for the register set
you have selected.
MESSAGE: A data buffer is too short.
Level: 226 ($E2)
CAUSE: A diagnostic status, loopback, or statistics operation
did not provide a buffer large enough for the link driver to return
all the driver information being requested.
ACTION: All such errors are caused by version mismatches
between the link driver and the modules requesting the data, or
bugs in the modules requesting the data. Contact your Hewlett-Packard
Representative to determine if additional software patches are already
available to correct this problem.
MESSAGE: Unsupported address format.
Level: 232 ($E8)
CAUSE: An upper layer protocol attempted to send data
through the link driver's write initiator routine, using
an address family which the driver does not support.
ACTION: All such errors are caused by bugs in the upper
layer protocol or mismatched software revisions. Attempt to determine
which protocol was trying to send, then see
Appendix A "Submitting a CR"
MESSAGE: Bad message for current state.
Level: 239 ($EE)
CAUSE: This is a generic error, reported when the driver received
a request from outside when the driver was not in a state where it could
process that type of request, or the when driver has already processed a
message of this type and was not expecting another. The driver may have
encountered a previous fatal error, may be in the middle of startup,
shutdown, or a recovery or dump operation, a message may have arrived too
late, or the sender may be confused.
ACTION: If the message has replies, the driver will attempt to
send an error reply back to the sender. If another error has already
occurred, this event may be ignored. Otherwise, if the problem happens
frequently, or if external subsystems are noticeably impacted after the
error, see
Appendix A "Submitting a CR"
MESSAGE: Unknown file record format.
Level: 240 ($F0)
CAUSE: The trace or log formatter attempted to decode
a record header to obtain basic information such as length and version,
but on inspection found that the record does not appear to be a
100Base-T record supported by this formatter.
ACTION: The formatter will attempt to print this record
in raw form. You may be trying to format a trace or log file taken
on a different system that has newer software than the system you
are formatting on. Format the file on the system you took the trace
or log on, or contact your Hewlett-Packard Representative to check
if patches are already available to update the software on your
current system.
MESSAGE: Unknown data format.
Level: 242 ($F2)
CAUSE: The trace or log formatter attempted to decode
a data entry header. There was sufficient data to cover the entry's
stored length, and the entry header looked OK, but when decoding
was attempted, the entry had an unknown tag, there wasn't
enough entry data for this version of the entry, or a decoder routine
was missing code to handle this version of the entry.
ACTION: The formatter will attempt to print this record
in the raw form. You may be trying to format a trace or log file
taken on a different system that has newer software than the system
you are formatting on. Format the file on the system you took the
trace or log on, or contact your Hewlett-Packard Representative
to check if patches are already available to update the software
on your current system.
MESSAGE: Unknown data version.
Level: 243 ($F3)
CAUSE: The trace or log formatter attempted to decode a record
header to obtain general information such as link type and link name, but
on inspection found that the version of that data was not supported by his
formatter, thus no other fields could be decoded.
ACTION: The formatter will attempt to print this record
in the raw form. You may be trying to format a trace or log file
taken on a different system that has newer software than the system
you are formatting on. Format the file on the system you took the
trace or log on, or contact your Hewlett-Packard Representative
to check if patches are already available to update the software
on your current system.
MESSAGE: Error encountered while decoding an entry.
Level: 244 ($F4)
CAUSE: The trace or log formatter encountered an entry
having an unrecognized entry tag value. The formatter cannot decode
entries of this type.
ACTION: The formatter will attempt to print this record
in raw form. You may be trying to format a trace or log file taken
on a different system that has newer software than the system you
are formatting on. Format the file on the system you took the trace
or log on, or contact your Hewlett-Packard Representative to check
if patches are already available to correct this problem.
MESSAGE: Incomplete data was encountered.
Level: 245 ($F5)
CAUSE: The trace or log formatter attempted to decode
an entry, but on inspection found that the entry did not contain
at least the minimum length of data required for this version of the data.
ACTION: The trace or log file may be corrupted, or you
may be trying to format a trace or log file taken on a different
system that has newer software than the system you are formatting
on. The formatter will attempt to print this entry in raw form.
Format the file on the system you took the trace or log on, or contact
your Hewlett-Packard Representative to check if patches are already
available to correct this problem.
The following are the logging sublocation codes reported by the 100Base-T link
drivers, including sublocation code, log class, log message, and the
appropriate cause of and action to take for each.
For meanings of 32-bit status values generated by the driver, refer to the
sections on status values.
MESSAGE: Cannot freeze a memory area.
Level: 1020 CLAS0001
CAUSE: During a link-open operation by an upper level subsystem,
the link module configurator was preparing to send configuration data to
the driver, but encountered an error while trying to freeze that data into
memory ("Cause" = 32-bit status from the call to freeze).
ACTION: The system may be low on available memory. Try
closing any unnecessary applications or sessions and retry the operation.
The open did not succeed. The module configurator cleaned up and
returned an error to the subsystem.
MESSAGE: Cannot send a port message.
Level: 1040 CLAS0001
CAUSE: During a link-open operation by an upper level subsystem,
the link module configurator was preparing to send configuration data to
the driver, but encountered an error while trying to send the port message
("Cause" = 32-bit status from the call to send_msg).
ACTION: There may be a system problem, or another subsystem has
already shut the driver down while this one was trying to start it. The
open did not succeed. The module configurator cleaned up and returned an
error to the subsystem.
Retry the operation. If this does not help,
try stopping all networks using the link, then retry. If the problem still
persists, halt the system and take a memory dump, then see
Appendix A "Submitting a CR"
MESSAGE: An unexpected timeout occurred.
Level: 1060 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator sent configuration data
to the driver, then encountered a timeout while awaiting the correct
reply message ("Cause" = 32-bit status from the
call to extend_receive, saying there was a timeout).
ACTION: The link driver is probably hung because of a problem in
the driver, or the driver may have sent the wrong message back. The open
did not succeed. The module configurator cleaned up and returned an error
to the subsystem.
Perform a :LINKCONTROL @ command to see if an entry exists for the
linkname being started. If so, then run the VBPBA diagnostic tool and
attempt to force a driver dump. If that works, save the resulting
NETDMP##.PUB.SYS file for analysis by Hewlett-Packard. Otherwise,
halt the system and take a memory dump. The dump should tell
Hewlett-Packard what actions the driver took. See
Appendix A "Submitting a CR"
MESSAGE: Did not receive an expected port message.
Level: 1080 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator sent configuration data
to the driver, then encountered an error while awaiting the correct
reply message ("Cause" = 32-bit
status from the call to extend_receive).
ACTION: There may be a system problem with message ports, or the
link driver may have sent the wrong reply message. The open did not succeed.
The module configurator cleaned up and returned an error to the subsystem.
Perform a :LINKCONTROL @ command to see if an entry exists for the
linkname being started. If so, then run the VBPBA diagnostic tool and
attempt to force a driver dump. If that works, save the resulting
NETDMP##.PUB.SYS file for analysis by Hewlett-Packard. Otherwise,
halt the system and take a memory dump. The dump should tell
Hewlett-Packard what actions the driver took. See
Appendix A "Submitting a CR"
MESSAGE: (Varies)
Level: 1100 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator sent configuration data
to the driver, but the driver returned an error in the reply message
("Cause" is not used here).
ACTION: If this error occurs, there may be additional
driver-specific errors logged, giving more information about the
problem. Attempt to locate those errors and look them up also. The
open did not succeed. The module configurator cleaned up and returned
an error to the subsystem.
MESSAGE: No adapter card found on specified PCI bus.
Level: 1110 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator did not find a PCI bus at
the hardware path specified in NMCONFIG ("Cause" is not used here).
ACTION: The module configurator cleaned up and returned an error
to the subsystem.
Verify the path in NMCONFIG is correct and complete, and matches the path
where a supported 100Base-T adapter card is installed in your computer
backplane. If the path passes through bus converters, verify the SYSGEN
configuration has entries for the higher-level bus converters leading to
that path. A diagram of the backplane slot paths, often found in the rear
of your system near the backplane, may help you. If necessary, change
NMCONFIG or contact your Hewlett-Packard Representative for assistance in
determining paths or correcting bus hardware problems.
MESSAGE: Bad hardware ID or path.
Level: 1120 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator did not find a supported
100Base-T adapter card at the hardware path specified in NMCONFIG.
ACTION: The module configurator cleaned up and returned an error
to the subsystem.
Verify the path in NMCONFIG is correct and complete, and matches the path
where a supported 100Base-T adapter card is installed in the computer
backplane. If necessary, reseat the board or contact your Hewlett-Packard
Representative for hardware assistance.
MESSAGE: Adapter card found does not match software configuration.
Level: 1130 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator found a supported adapter
card at the path specified in NMCONFIG, but it was not the right
type of card for the link being started.
ACTION: Correct the network configuration or plug in the correct
type of adapter card, and retry the operation. The module configurator
cleaned up and returned an error to the subsystem.
MESSAGE: Cannot create a buffer pool.
Level: 1140 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator encountered an error while
trying to create an outbound buffer pool ("Cause" =
32-bit status from the call to bmgr_create_pool).
ACTION: The system may be low on available memory. The module
configurator cleaned up and returned an error to the subsystem.
Try stopping some applications or sessions and retry the operation. If the
problem persists, stop all networking and restart it, or restart the system.
The buffer size and pool size are not configurable. If the problem still
occurs, there could be a problem with the buffer manager.
See Appendix A "Submitting a CR"
MESSAGE: Cannot load driver plabel.
Level: 1160 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator encountered an error while
trying to load the code for the driver ("Cause" =
32-bit status from the call to io_get_mgr_entry).
ACTION: Probably not all software required to operate
this type of link is installed. The software was incorrectly installed,
or you may need to purchase additional software or install newer
patches. Reinstall the link software or contact your Hewlett-Packard
Representative for assistance.
MESSAGE: Cannot load a system routine.
Level: 1170 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator encountered an error while
trying to load code for the write initiator procedure needed for
the link type configured in NMCONFIG ("Cause" =
32-bit status from the call to hpgetsysplabel).
ACTION: Probably not all software required to operate
this type of link is installed. Software was incorrectly installed,
or you may need to purchase additional software or install newer
patches. Reinstall the link software or contact your Hewlett-Packard
Representative for assistance.
MESSAGE: The link is already started.
Level: 1200 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator attempted to create a new
instance of the link driver, but discovered the driver was already
created ("Cause" = 32-bit status from the call to io_configure).
ACTION: This event is informational. No action is required.
It probably would not appear as a log event. The module configurator
will ignore this warning and continue to bring the link driver up,
so that the number of users may be checked. May be followed by another
error.
MESSAGE: Unable to auto-configure underlying I/O paths.
Level: 1220 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator attempted to create a new
instance of the link driver, but encountered an error when configuring
the underlying I/O paths ("Cause" = 32-bit status
from the call to io_configure_path).
ACTION: The module configurator cleaned up and returned an error
to the subsystem.
Verify the path in NMCONFIG is correct and complete, and matches the path
where a supported 100Base-T adapter card is installed in your computer
backplane. If the path passes through bus converters, verify the SYSGEN
configuration has entries for the higher-level bus converters leading to
that path.
A diagram of the backplane slot paths, often found in the rear o your
system near the backplane, may help you. If necessary, change NMCONFIG or
contact your Hewlett-Packard Representative for assistance in determining
paths or correcting bus hardware problems.
MESSAGE: Cannot add driver to I/O system.
Level: 1240 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator attempted to create a new
instance of the link driver, but encountered an error which was
not one of the legal errors the configurator was able to handle
("Cause" = 32-bit status from the call to io_configure).
ACTION: The module configurator cleaned up and returned an error
to the subsystem.
Verify the path in NMCONFIG is correct and complete, and matches the path
where a supported 100Base-T adapter card is installed in your computer
backplane. If the path passes through bus converters, verify the SYSGEN
configuration has entries for the higher-level bus converters leading to
that path. A diagram of the backplane slot paths, often found in the rear
of your system near the backplane, may help you. If necessary, change
NMCONFIG or contact your Hewlett-Packard Representative for assistance in
determining paths or correcting bus hardware problems.
MESSAGE: Cannot open configuration file.
Level: 1400 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator encountered an error while
trying to open the configuration file ("Cause" =
32-bit status from the call to nmconfopen).
ACTION: The module configurator cleaned up and returned an error
to the subsystem.
Verify an NMCONFIG.PUB.SYS file exists. If so, try to verify its
format matches rest of the operating system. If the system was updated, you
may need to run NMMGRVER.PUB.SYS to convert the file to a newer
format. If the system was backdated, you may need to restore an older copy
of NMCONFIG from a backup tape.
Perform a :LISTF,3 command and make sure the file is not protected
by a lockword, and that the user starting the link has the necessary access
rights to open the file.
Perform a :DSTAT ALL command and make sure the disk drive the file
resides on is present and mounted. Make sure the file resides on Ldev 1. If
not, use Fcopy and a file equation with a ";DEV=1" option to force
a copy of the file onto Ldev 1.
Perform a :SHOWPROC 1;TREE;SYSTEM command and verify an NMFILE
process exists. If not, shut down and restart the system, and retry the
operation. If the problem persists, contact your Hewlett-Packard
Representative for assistance with NMCONFIG file open
problems.
MESSAGE: Cannot read from configuration file.
Level: 1420 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator was able to open the configuration
file, but encountered an error while trying to data for the link being
started ("Cause" = 32-bit status from the call to nmconfopen).
ACTION: The module configurator cleaned up and returned an error
to the subsystem.
Using NMMGR, verify the path LINK.linkname exists in the NMCONFIG
file and is the exact same linkname which is now being
started. Verify the "Data=Y" flag is set at the top of that LINK
screen (meaning that ENTER has been pressed to save the configuration data
there). If the link is being used with NS or DTS, use the VALIDATE function
to validate the network configuration. Correct any configuration
errors and retry the operation.
MESSAGE: Cannot validate configuration file.
Level: 1440 CLAS0001
CAUSE: After successfully reading configuration data
for a link being started, the link module configurator checked the
data and found it was not valid ("Cause" is not
used here). For NS/3000, probably the link type and NI type do not match.
ACTION: The module configurator cleaned up and returned an error
to the subsystem.
Using NMMGR, verify the path LINK.linkname exists in the NMCONFIG
file and is either a 100Base-T link type. If the subsystem being started is
NS, verify the link type matches the NI type for the network being started.
If these are not the problem, an incorrect version of NMMGR may have been
used to create the NMCONFIG file on your system. Run
NMMAINT.PUB.SYS;PARM=24 to check versions of NMMGR components.
The format of your NMCONFIG file may be incompatible with the link driver
version installed on your system. Run NMMGRVER.PUB.SYS to update
your NMCONFIG file to a newer version, or restore an older version from a
backup tape, whichever is appropriate.
If the problem still occurs, contact your Hewlett-Packard Representative
for assistance in using NMMGR to configure 100Base-T
links.
MESSAGE: Subsystem is opening link.
Level: 1580 CLAS0001
CAUSE: An upper level subsystem has called the link module
configurator, which has successfully located configuration for the link,
and will now proceed to start it up ("Transport" = name
of the subsystem which is starting the link, or its subsystem number
if the configurator does not know the name).
ACTION: None. This is an informational event only.
A similar event will be logged when the link is closed.
MESSAGE: Cannot open tracing.
Level: 1600 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator found that the link was
configured to enable tracing at startup, but encountered an error
trying to open the trace file ("Cause" = 32-bit
status from the call to nmopentrace).
ACTION: This is an informational error that tracing was not
started. The link came up, but the error was returned to the upper level
subsystem, which may decide to shut the link back down again.
Using NMMGR, check if a filename was configured. If so, verify it is a
legal MPE filename. A group and account may need to be specified. Make sure
the user starting the link has the necessary capabilities to create that
file in the group and account specified.
Check whether the system is low on disk space. Check whether too many
NMTCnnnn.PUB.SYS trace data files already exist. Purge files as
necessary to free up disk space, or add more disks.
Make sure the version of the NMCONFIG file matches the rest of the system
software, by running NMMGRVER.PUB.SYS.
If none of these suggestions solves the problem, contact your
Hewlett-Packard Representative for assistance with configuring a 100Base-T
link to enable tracing at startup.
MESSAGE: Cannot send a trace request.
Level: 1620 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator found that the link was
configured to enable tracing at startup. After successfully opened
a trace file, the configurator encountered an error trying to enable
driver tracing ("Cause" = 32-bit status from the
call to sio_trace_req).
ACTION: This is an informational error that tracing was
not enabled. The link came up, but the error was returned to the
upper level subsystem, which may decide to shut the link back down again.
Probably the link driver returned an error reply when asked to enable
tracing. The driver may have a problem. Check for other, driver-specific
error messages which may give more information about the problem, and look
them up also. If no other errors are found, see
Appendix A "Submitting a CR".
MESSAGE: Cannot stop tracing.
Level: 1630 CLAS0001
CAUSE: After a link-open operation by an upper level
subsystem failed, the link module configurator tried to clean up,
but encountered an error trying to disable driver tracing ("Cause" =
32-bit status from the call to sio_trace_req).
ACTION: This is an informational error that tracing was
not disabled. If this error occurs it is because some other error
has already occurred. The link open did not succeed.
Probably the link driver returned an error reply when asked
to disable tracing. The driver may have a problem, or may already
have shut down. Check for other, driver-specific error messages
which may give more information about the problem, and look them
up also. If no other errors are found, see
Appendix A "Submitting a CR"
MESSAGE: Cannot read current multicast list.
Level: 1640 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator tried to read the current
list of multicast addresses produced by the subsystem, but encountered
an error on the read ("Cause" = 32-bit status
from the call to ieee_multicast_read).
ACTION: The module configurator cleaned up and returned
an error to the subsystem.
Run NMMAINT.PUB.SYS;PARM=80, and verify that Link Common Services
are present. If present, and if the problem persists, try restarting the
system, then retry the operation. If not present, you may need to obtain
newer patches; contact your Hewlett-Packard Representative for assistance.
If reinstalling software does not solve the problem, see
Appendix A "Submitting a CR"
MESSAGE: The link is already started.
Level: 1650 CLAS0001
CAUSE: During the first link-open operation by an upper level
subsystem, the link module configurator attempted to create a new instance
of the link driver, but discovered the driver was already created and has
been opened at least once ("Cause" = 32-bit status from the call to
io_configure, saying the link is already started).
ACTION: This is an informational warning only. The module
configurator will leave the link driver up and stop trying to start it
again. Usually preceded by another error.
MESSAGE: Cannot add to link table.
Level: 1660 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator successfully started the
driver, but encountered an error trying to add the link to the link
table ("Cause" = 32-bit status
from the call to lsslktbladd).
ACTION: The module configurator cleaned up and returned an error
to the subsystem.
Possibly too many links are started.
If not. try starting a different link, to see if that works. If not, first
try doing a :LINKCONTROL @ command to see if any LSS errors occur.
If they do, you may need to reinstall MPE software; contact your
Hewlett-Packard Representative for assistance. Otherwise try restarting the
system to see if it corrects the problem or LINKCONTROL errors. If none
of these suggestions helps, see
Appendix A "Submitting a CR"
MESSAGE: Cannot freeze a memory area.
Level: 1700 CLAS0001
CAUSE: During a link-close operation by an upper level
subsystem, the link module deconfigurator was preparing to send
new configuration data to the driver, but encountered an error while
trying to freeze that data into memory ("Cause" =
32-bit status from the call to freeze).
ACTION: The system may be low on available memory. Try closing any
unnecessary applications or sessions and retry the operation. The driver
did not receive the updated configuration data. The module deconfigurator
attempted to continue with the close. If this happens every time,
see Appendix A "Submitting a CR"
MESSAGE: Cannot send a port message.
Level: 1720 CLAS0001
CAUSE: During a link-close operation by an upper level
subsystem, the link module deconfigurator was preparing to send
updated configuration data to the driver, but encountered an error
while trying to send the port message ("Cause" =
32-bit status from the call to send_msg).
ACTION: There may be a system problem, or another subsystem has
already shut the driver down while this one was trying to close it. The
driver did not receive the updated configuration data. The module
deconfigurator reported an error, but attempted to continue with the close.
If this happens every time, see
Appendix A "Submitting a CR"
MESSAGE: An unexpected timeout occurred.
Level: 1740 CLAS0001
CAUSE: During a link-close operation by an upper level
subsystem, the link module deconfigurator sent updated configuration
data to the driver, then encountered a timeout while awaiting the
correct reply message ("Cause" = 32-bit status
from the call to extend_receive, saying there was a timeout).
ACTION: The link driver is probably hung because of a
problem in the driver, the driver has already shut down, or the
driver may have sent the wrong message back. The module deconfigurator
reported an error, but attempted to continue with the close. If
this happens every time, see
Appendix A "Submitting a CR"
MESSAGE: Did not receive an expected port message.
Level: 1760 CLAS0001
CAUSE: During a link-close operation by an upper level
subsystem, the link module deconfigurator sent updated configuration
data to the driver, then encountered an error while awaiting the
correct reply message ("Cause" = 32-bit status
from the call to extend_receive).
ACTION: There may be a system problem with message ports, or the
link driver may have sent the wrong reply message. The module
deconfigurator reported an error, but attempted to continue with the close.
If this happens every time, see
Appendix A "Submitting a CR"
MESSAGE: (Varies)
Level: 1780 CLAS0001
CAUSE: During a link-close operation by an upper level
subsystem, the link module deconfigurator sent updated configuration
data to the driver, but the driver returned an error in the reply
message ("Cause" is not used here).
ACTION: If this error occurs, there may be additional
driver-specific errors logged, giving more information about the
problem. Attempt to locate those errors and look them up also. The
module deconfigurator reported an error, but attempted to continue with the
close. If this happens every time, see
Appendix A "Submitting a CR"
MESSAGE: Subsystem is closing link.
Level: 1800 CLAS0001
CAUSE: An upper level subsystem has called the link module
deconfigurator, which has successfully located the link, and will now
proceed to close it.
ACTION: None. This is an informational event only. A similar
event was logged when the link was opened.
MESSAGE: Cannot read current multicast list.
Level: 1840 CLAS0001
CAUSE: During a link-close operation by an upper level
subsystem, the link module deconfigurator tried to read the current
list of multicast addresses produced by the subsystem, but encountered
an error on the read ("Cause" = 32-bit status
from the call to ieee_multicast_read).
ACTION: The module deconfigurator reported an error,
but attempted to continue with the close. Network management services
may have been shut down. Otherwise, if this happens every time,
see Appendix A "Submitting a CR"
MESSAGE: Module Configurator cannot access its context area.
Level: 1880 CLAS0001
CAUSE: During a link-close operation by an upper level
subsystem, the link module deconfigurator checked its context memory
area for validity, but did not find the expected data ("Cause" =
32-bit status saying the context was not accessed).
ACTION: The module deconfigurator's context memory area is being
overwritten, or is not working properly. The deconfigurator did not perform
the close. If this happens every time, wait until the next time the link is
to be closed; instead of closing the link, halt the system and take a
memory dump, and see
Appendix A "Submitting a CR"
MESSAGE: Cannot remove driver from I/O system.
Level: 1900 CLAS0001
CAUSE: During the final link-close operation by an upper level
subsystem, the link module deconfigurator attempted to delete an instance
of the link driver, but encountered an I/O system error ("Cause" = 32-bit
status from the call to io_unconfigure).
ACTION: The deconfigurator stopped trying to close the
link. However, the driver already received updated configuration
data removing the subsystem's multicast information, but
other resources, such as link table, were not updated. The driver
may already have been shut down by some other means, or the system
I/O configuration may have been altered. If this happens frequently,
see Appendix A "Submitting a CR"
MESSAGE: Cannot delete from link table.
Level: 1920 CLAS0001
CAUSE: During the final link-close operation by an upper
level subsystem, the link module deconfigurator attempted to delete
the link from the link table, but encountered an error ("Cause" =
32-bit status from the call to lsslktbldelete).
ACTION: The module deconfigurator reported an error, but
attempted to continue with the close. Network management services
may have been shut down. Otherwise, if this happens every time,
see Appendix A "Submitting a CR"
MESSAGE: Cannot release a system plabel.
Level: 1940 CLAS0001
CAUSE: During the final link-close operation by an upper
level subsystem, the link module deconfigurator encountered an error
while trying to release the link's write initiator procedure
("Cause" = 32-bit status from the call to hprelsysplabel).
ACTION: This is an informational warning that some system
memory resources may have been lost. The module deconfigurator reported
an error, but attempted to continue with the close. If this happens
every time, see
Appendix A "Submitting a CR"
MESSAGE: Cannot delete a buffer pool.
Level: 1960 CLAS0001
CAUSE: During a link-close operation by an upper level
subsystem, the link module deconfigurator encountered an error while
trying to delete an outbound buffer pool ("Cause" =
32-bit status from the call to bmgr_delete_pool).
ACTION: This is an informational warning that some system
memory resources may have been lost. The module deconfigurator reported
an error, but attempted to continue with the close. If this happens
every time, see
Appendix A "Submitting a CR"
MESSAGE: Cannot get a system timer.
Level: 2210 CLAS0001
CAUSE: The driver attempted to get a system timer from I/O
Services but encountered an error ("Cause" = 32-bit status returned by the
call to io_get_timer). This is either caused by exhausting all
timers due to heavy system load, or by system software either failing to
release timers, or having some other bug.
ACTION: This is a fatal software error. The number of available
timers is not configurable, and the driver cannot operate without the
necessary timers. After reporting this error, the driver will die, then
will either attempt an auto-reset or else require a manual shutdown and
restart. Typically followed by another error giving more information about
what kind of timer the driver needed; check log data for that error and
look it up also.
If you suspect a heavy load, you can try shutting some processes down, then
restart the driver. Otherwise use Control-B at the console to halt the
system, take a memory dump, and reboot. See
Appendix A "Submitting a CR"
MESSAGE: Internal error while initiating a dump. Dump failed.
Level: 2230 CLAS0001
CAUSE: While processing a request from an upper level diagnostic
took, the dump surrogate for the PCI 100Base-T driver encountered an error.
Additional messages may have been directed to the console by the dump
surrogate process which provide more detail about the error.
ACTION: The dump surrogate was unable to complete the dump request.
Note any messages from the console; make sure that any dump request issued
in an upper level tool had the proper syntax and linkname specified. If
the problem persists, see
Appendix A "Submitting a CR"
MESSAGE: Cannot reset a system timer.
Level: 2240 CLAS0001
CAUSE: The driver attempted to reset a system timer previously
obtained from I/O Services but encountered an error ("Cause" = 32-bit
status returned by the call to io_reset_timer). This is likely
caused by a bug in system software, or by corruption of the driver's PDA
context memory.
ACTION: This is a fatal software error. The driver cannot operate
without all necessary timers. After reporting this error, the driver will
die, then will either attempt an auto-reset or else require a manual
shutdown and restart. If the problem persists, use Control-B at the console
to halt the system, take a memory dump, and reboot, see
Appendix A "Submitting a CR"
MESSAGE: Driver dump is starting.
Level: 2250 CLAS0001
CAUSE: In response to a request from an upper level diagnostic
tool, the PCI 100Base-T dump surrogate has initiated a dump of the driver.
ACTION: This is informational; the dump was most likely requested
to assist in diagnosing another problem with the driver. Wait for the dump
to complete and then send the dump file (NETDMP##.PUB.SYS) to
Hewlett-Packard for analysis; see
Appendix A "Submitting a CR"
MESSAGE: Cannot free a system timer.
Level: 2270 CLAS0001
CAUSE: The driver attempted to release a system timer previously
obtained from I/O Services but encountered an error ("Cause" = 32-bit
status returned by the call to io_release_timer). This is likely
caused by a bug in system software, or by corruption of the driver's
PDA context memory.
ACTION: This is a warning that some timer resources may
have been lost. The driver will attempt to continue. Unless this
happens constantly, the system should continue to run. Possibly
followed by another error giving more information about what kind
of timer the driver was releasing; check log data for that error
and look it up also. If the problem happens every time, see
Appendix A "Submitting a CR"
MESSAGE: Cannot send a port message.
Level: 2600 CLAS0001
CAUSE: While notifying upper level subsystems that the
driver detected a serious error, powerfail, or reset, an attempt
to send an asynchronous event message to one of those subsystems
failed ("Cause" = 32-bit status returned by the call to send_msg).
ACTION: This is a warning that one or more subsystems
may not be aware the link has had a problem. The subsystem(s) may
have failed to close the driver as part of their shutdown. The driver
will continue with its error recovery actions, and no user action
is required. If this happens every time, see
Appendix A "Submitting a CR"
MESSAGE: Cannot send a port message.
Level: 2630 CLAS0001
CAUSE: During final processing of a fatal driver error, the driver
attempted a standard auto- reset instead of dying. However, its attempt to
send a reset message to itself failed ("Cause" = 32-bit status returned by
the call to send_msg). If this error is reported, it is because
the driver has already encountered some other error.
ACTION: This error is likely an indication of a more serious
system software problem, and may be followed by a system abort. Probably
all message frames have been exhausted by some module running on the
system. Further recovery actions may not be possible; if the system fails,
take a memory dump and reboot.
Otherwise, since the auto-reset failed, the driver dies instead, notifying
upper layer software via an asynchronous event message if possible. The
network and/or link must now be stopped and restarted. Some upper layers
may stop the link on their own in response to an event message. If not,
manually stop the network and/or link via the appropriate operator command
(e.g., :NETCONTROL STOP) and then restart it.
MESSAGE: A driver dump was suppressed. Too many dumps already.
Level: 2660 CLAS0001
CAUSE: During processing of a fatal driver error, the
driver attempted a driver dump, but determined it had already dumped
too many times since it was initially started ("Cause" is
not used here). If this error is reported, it is because the driver
has already encountered some other error.
ACTION: By design, the driver attempts to auto-reset itself after
any driver dump. But after 3 dumps, to avoid uncontrollably filling disk
space with driver dumps, additional dumps are automatically suppressed. No
attempt is made to determine whether the dumps are duplicates of the same
problem. The driver did not dump, but will still attempt to auto-reset
itself, up to a total of 12 times or more.
There is apparently something wrong, since many driver dumps are occurring.
Collect binary copies of all dump files (NETDMP##.PUB.SYS) on tape
for analysis by Hewlett-Packard and see
Appendix A "Submitting a CR"
MESSAGE: Internal error while initiating a dump. Dump failed.
Level: 2690 CLAS0001
CAUSE: During processing of a fatal driver error, the driver
attempted a driver dump, but encountered an error while trying to get or
reset a timer ("Cause" = 32-bit status returned by the call to
lnk_timer_start). This timer was to be used to avoid deadlock in
case the dump process did not respond; the driver cannot attempt a dump if
a dump timer cannot be started. If this error is reported, it is because
the driver has already encountered some other error.
ACTION: Typically preceded by another error message giving better
information about the original cause; check log data for that error and
look it up also. The driver did not dump, but will still attempt to
auto-reset itself, up to a total of 12 times or more.
MESSAGE: Cannot send a port message.
Level: 2720 CLAS0001
CAUSE: During final processing of a fatal driver error, the driver
attempted a driver dump, but was unable to send a dump event to the dump
process ("Cause" = 32-bit status returned by the call to
send_msg). If this error is reported, it is because the driver
has already encountered some other error.
ACTION: The driver did not dump, but will still attempt
to auto-reset itself, up to a total of 12 times or more.
MESSAGE: Internal error while initiating a dump. Dump failed.
Level: 2750 CLAS0001
CAUSE: During processing of some other fatal driver error, the
driver attempted a driver dump, but encountered an error. It then
encountered this second error while trying to clean up, when attempting
to release a dump timer it had obtained ("Cause" =
32-bit status returned by the call to lnk_timer_stop).
ACTION: Typically preceded by another error giving better
information about the original cause; check log data for that error
and look it up also. This error is mainly informational, since the
driver did not dump, but may be indicative of other, possibly-related
problems. The driver will still attempt to auto- reset itself, up
to a total of 12 times or more.
MESSAGE: General error trying to get a buffer
Level: 2780 CLAS0001
CAUSE: When attempting to build a setup frame for the
PCI 100Base-T card (e.g., due to a change in the active multicast
address list), the driver's DVR module encountered an error
while trying to allocate a buffer from the driver's read
buffer pool ("Cause" = 32-bit status returned
by the call to bmgr_get_buffer).
ACTION: The driver logs this error, then attempts to continue.
However, the problem could indicate some serious internal problems within
the buffer manager or its data structures, or with the way the system is
configured.
Although the driver may attempt to continue using the previously read
multicast address list, the failure to allocate a data buffer and send a
new setup frame to the PCI 100Base-T card could result in some network
services/upper layer protocols (ULPs) not operating properly (data frames
intended for those ULPs may not be recognized by the 100Base-T card).
If that occurs, try to quiesce any active network traffic/sessions, then
bring down the network link (e.g., NETCONTROL STOP). Restart the
network.
Note all log messages, especially the "Cause" status for this error, and
check to see if the driver generated an internal dump file
(NETDMP##.PUB.SYS); see
Appendix A "Submitting a CR"
MESSAGE: Cannot read current multicast list.
Level: 2810 CLAS0003
CAUSE: In response to a request to update the multicast
address list (and build a new setup frame for the PCI 100Base-T
card), the DVR was unable to successfully read the current multicast
list of addresses because it was too large for the driver to support.
A maximum of 14 multicast addresses can be active at any one time
on a single PCI 100Base-T link. There are likely too many network
services/upper level subsystems competing for resources on this link.
ACTION: The driver will try to continue to operate using the
previously activated multicast address list, but this error may prevent
some upper level subsystems from operating properly and receiving data over
the network. Try to quiesce any current network activity on the link and
then bring down the network link (e.g., NETCONTROL STOP).
Restart the network link, but limit the load of services/protocols that are
running on the same link. If multiple 100Base-T links are available and
configured on the system, consider balancing the load
of upper level subsystems running over each link.
MESSAGE: Pending message table full. Driver not finishing fast enough.
Level: 3040 CLAS0003
CAUSE: While processing a new blocking request (requiring a driver
exit and later reply) and scanning a table in which to save the request,
the driver found an unused entry, but an entry counter indicated the table
was full ("Cause" is not used here).
ACTION: This fatal software error is only caused by a bug, because
the in use flags and counters should match. After reporting this error, the
driver will die, then will either attempt an auto-reset or else require a
manual shutdown and restart. If the problem persists, use Control-B at the
console to halt the system, take a memory dump, and reboot, see
Appendix A "Submitting a CR"
MESSAGE: Pending message table full. Driver not finishing fast enough.
Level: 3070 CLAS0003
CAUSE: While processing a new blocking request (requiring
a driver exit and later reply) and scanning a table in which to
save the request, the driver was unable to find an unused entry
("Cause" is not used here).
ACTION: This fatal software error is only caused by a bug, since
message port subqueue controls should have prevented the table from filling.
After reporting this error, the driver will die, then will either attempt
an auto-reset or else require a manual shutdown and restart.
Most likely some subsystem has sent a message to an incorrect subqueue. If
the problem persists, try to determine which program, networking subsystem,
or operator command causes it; then activate link tracing, reproduce the
problem, and save the resulting trace file (NMTC####.PUB.SYS) for
analysis by Hewlett-Packard, see
Appendix A "Submitting a CR"
MESSAGE: Illegal access to saved port message area.
Level: 3100 CLAS0002
CAUSE: While completing an old blocking request (requiring
a driver exit and later reply), the driver found that the entry
in the pending message save area, where the request was supposedly
saved, was no longer in use ("Cause" = table entry
number where the request was supposed to be).
ACTION: This fatal software error is only caused by a
bug, because the driver should never be trying to complete the same
message twice. After reporting this error, the driver will die,
then will either attempt an auto-reset or else require a manual
shutdown and restart. If the problem persists, try to determine
which program, networking subsystem, or operator command causes
it; then activate link tracing, reproduce the problem, and save
the resulting trace file (NMTC####.PUB.SYS) for analysis by
Hewlett-Packard, see
Appendix A "Submitting a CR"
MESSAGE: Illegal access to saved port message area.
Level: 3130 CLAS0003
CAUSE: While completing an old blocking request (requiring
a driver exit and later reply), the driver found that the index
specified for an entry in the pending message save area, where the
request was supposedly saved, was not within the range of legal
table indexes ("Cause" = the bad table entry number specified).
ACTION: This fatal software error is only caused by memory
corruption or a bug, because the driver should never pass an illegal
index. After reporting this error, the driver will die, then will
either attempt an auto-reset or else require a manual shutdown and
restart. If the problem persists, try to determine which program,
networking subsystem, or operator command causes it; then activate
link tracing, reproduce the problem, and save the resulting trace
file (NMTC####.PUB.SYS) for analysis by Hewlett-Packard, see
Appendix A "Submitting a CR"ACTION: This fatal software error is only caused by a
bug, since message port subqueue controls should have prevented
the table from filling. After reporting this error, the driver will
die, then will either attempt an auto-reset or else require a manual
shutdown and restart.
Most likely some subsystem has sent a message to an incorrect subqueue.
If the problem persists, try to determine which program, networking
subsystem, or operator command causes it; then activate link tracing,
reproduce the problem, and save the resulting trace file
(NMTC####.PUB.SYS) for analysis by Hewlett-Packard, see
Appendix A "Submitting a CR"
MESSAGE: Out of internal comm frame resources.
Level: 3160 CLAS0001
CAUSE: While attempting to request action from its ISR
module, the driver found that no available communication frames
were available on the referenced queue ("Cause" is
not used here). The number of available comm frames is not configurable,
and the driver cannot operate if frames run out.
ACTION: This is a fatal software error. After reporting this
error, the driver will attempt a driver dump, then will auto-reset
and attempt to continue. Typically followed by another error giving
more information about what kind of comm the driver was trying to
send; check log data for that error and look it up also.
Collect binary copies of all NETDMP##.PUB.SYS dump files on tape
for analysis by Hewlett-Packard and see
Appendix A "Submitting a CR"
MESSAGE: (Varies)
Level: 3190 CLAS0001
CAUSE: While attempting to process a request involving
reading and updating the current multicast address list, the DVR
was unable to queue a new setup frame to be sent down to the PCI
100Base-T card. An error occurred when attempting to create a data
buffer containing the new setup frame. Possibly there are too many network
services/upper level subsystems competing for resources on this link.
ACTION: The driver will continue to try to operate using
the previously activated multicast address list, but this error
may prevent some upper layer protocols from operating properly and
receiving data over the network. Try to quiesce any current network
activity on the link and then bring down the network link (e.g.,
NETCONROL STOP).
Restart the network, but limit the load of services/protocols
that are running on the same link. If multiple 100Base-T links are
available and configured on the system, consider balancing the load
of network services running over each link.
MESSAGE: (Varies)
Level: 3220 CLAS0001
CAUSE: When preparing to send a setup frame to the PCI
100Base-T card, the DVR was unable to reserve an available transmit
descriptor from the descriptor ring. This could be a temporary bottleneck
condition because of heavy data traffic on the network, or it could
indicate an internal problem in the driver or with the PCI 100Base-T card.
ACTION: No action is immediately needed. The driver will
retry the operation automatically to see if more transmit descriptors
have been freed for use (once the PCI 100Base-T card has finished
transmitting previously queued data frames).
However, if the problem persists or there is an interruption of outbound
network traffic, the driver may be broken; run the VGPBA diagnostic and
attempt a Reset function. If the problem still persists, run VGPBA, attempt
a Dump function, and save the resulting file (NETDMP##.PUB.SYS)
for analysis by HP. If the driver still does not become usable after this,
use Control-B at the console to halt the system, take a memory dump, and
reboot, see Appendix A "Submitting a CR"
If none of the above steps resolve the problem, this could also be the
result of a bad PCI 100Base-T card. The card may need
to be replaced.
MESSAGE: (Varies)
Level: 3250 CLAS0001
CAUSE: When preparing to send a setup frame to the PCI
100Base-T card, the DVR was unable to reserve an available transmit
descriptor from the descriptor ring. This could be a temporary bottleneck
condition because of heavy data traffic on the network, or it could
indicate an internal problem in the driver or with the PCI 100Base-T card.
ACTION: No action is immediately needed. The driver will
retry the operation automatically to see if more transmit descriptors
have been freed for use (once the PCI 100Base-T card has finished
transmitting previously queued data frames).
However, if the problem persists or there is an interruption
of outbound network traffic, the driver may be broken; run the VGPBA
diagnostic and attempt a Reset function. If the problem still persists,
run VGPBA, attempt a Dump function, and save the resulting file
(NETDMP##.PUB.SYS) for analysis by HP. If the driver still does
not become usable after this, use Control-B at the console to halt the
system, take a memory dump, and reboot, see
Appendix A "Submitting a CR"
If none of the above steps resolve the problem, this could
also be the result of a bad PCI 100Base-T card. The card may need
to be replaced.
MESSAGE: Could not allocate or reassign an I/O virtual address.
Level: 3280 CLAS0003
CAUSE: While attempting to build a transmit request to
be sent down to the PCI 100Base-T card, the DVR received an error
attempting to obtain the proper virtual address mapping for the
data ("Cause" = 32-bit status
returned by the call to Lnk_load_io_addr_for_virt).
ACTION: No immediate action is required. This could be
a temporary condition caused by heavy system load and I/O resource
contention. The driver will continue operating and will try the
transmit operation again periodically until the required system
resources are available.
If the problem persists, it may indicate a more serious problem
in the I/O system. Halt the system as soon as possible after the
error occurs and generate a system dump, see
Appendix A "Submitting a CR"
MESSAGE: Cannot send a port message.
Level: 3310 CLAS0003
CAUSE: While attempting to send a reply to an earlier
request message from an upper level subsystem or tool, the driver
encountered an error on the send ("Cause" = 32-bit
status returned by the call to send_msg).
ACTION: This error is sometimes fatal, causing the remainder
of the driver's processing ton be skipped. May be followed
by another error giving more information about what kind of reply
the driver was trying to send; check log data for that error and
look it up also. If the link does not seem to be responding, attempt
to shut down and restart the network and/or link. If the problem
persists, wait until it occurs again, then use Control-B at the
console to halt the system, take a memory dump, and reboot, see
Appendix A "Submitting a CR"
MESSAGE: Open table full. Too many drive users.
Level: 3340 CLAS0001
CAUSE: Too many subsystems are attempting to open the
driver at the same time, or subsystems are shutting down without
closing the driver ("Cause" = maximum number of driver opens allowed).
ACTION: The driver allows 11 simultaneous opens. It was
not opened by the additional subsystem. Shut down any networking
subsystems that are not currently needed and try again.
A side-effect of this error may be that the driver becomes unusable; if so,
run VGPBA and execute the Reset function to see
if that restores normal operation.
MESSAGE: Cannot send a port message.
Level: 3370 CLAS0001
CAUSE: While starting up the link, the driver attempted
to request ADA memory from the MPE I/O system, but encountered an
error trying to send a memory request message to the I/O Memory
Port ("Cause" = 32-bit status
from the call to send_msg).
ACTION: This is a fatal software error. The driver cannot operate
the adapter card without ADA memory. After reporting this error, the driver
will return a configuration error, then die and wait to be shut down; the
configuration routine should shut it down automatically.
The problem can be caused either by lack of memory or by a bug. If you
suspect high memory usage and have the GLANCE tool, run it and check system
memory usage. If usage is high, try closing some applications or subsystems,
then retry link startup. If the problem persists, shut down the system to
clear memory, then reboot but try starting the link earlier, before too
many other applications get going.
If still low on memory, you may need to add more memory hardware. First,
however, Hewlett-Packard can try to determine if more memory would
help, or if instead there is a bug. Use NMMGR to make sure all logging
classes are enabled for the link type, for disk logging. Reproduce the
problem, then collect all NM log files (NMLG####.PUB.SYS) and see
Appendix A "Submitting a CR"
MESSAGE: Cannot send a port message.
Level: 3400 CLAS0001
CAUSE: While shutting down the link, the driver attempted
to free ADA memory previously obtained from the MPE I/O system,
but encountered an error trying to send a memory request message
to the I/O Memory Port ("Cause" = 32-bit status
from the call to send_msg).
ACTION: This is a warning that some memory resources may have been
lost. The driver will attempt to continue. Unless this happens frrequently,
the system should continue to run.
If the problem happens every time, enable link tracing via
:LINKCONTROL then reproduce the link shutdown problem (the trace
file will close automatially). Save the resulting trace file
(NMTC####.PUB.SYS) on tape for Hewlett-Packard analysis, and see
Appendix A "Submitting a CR"
MESSAGE: Driver is shutting down.
Level: 3460 CLAS0003
CAUSE: The driver is being shut down. The last subsystem
that was using the driver is now closing it.
ACTION: This event is informational only. No action is
needed.
MESSAGE: No adapter card found on specified PCI bus.
Level: 3520 CLAS0001
CAUSE: During initial driver startup, a PCI bus was not
found at the hardware path specified in NMCONFIG.
ACTION: The driver did not start up. Use NMMGR to verify the path
in NMCONFIG is correct and complete, and matches the path where a supported
100Base-T adapter card is installed in your computer backplane. If the path
resides on a bus converter, use SYSGEN to make sure a path to that bus
converter exists in the I/O configuration. A diagram of the backplane slot
paths, often found in the rear of your system near the backplane, may help
you. If necessary, change the SYSGEN or NMCONFIG configurations or contact
your Hewlett-Packard Representative for assistance in determining paths or
correcting bus hardware problems.
MESSAGE: Driver is shutting down.
Level: 3550 CLAS0001
CAUSE: During initial driver startup, a supported 100Base-T
adapter card was not found at the hardware path specified in NMCONFIG.
ACTION: The driver did not start up. Verify the path in NMCONFIG
is correct and complete, and matches the path were a supported 100Base-T
adapter card is installed in the computer backplane. If necessary, contact
your Hewlett-Packard Representative for hardware
assistance.
MESSAGE: Link tracing is already enabled.
Level: 3750 CLAS0001
CAUSE: The driver received a request to turn link tracing
on when it was already on. Typically this condition is caught at
the C.I. level, however in this case trace may be under the control
of a different mechanism.
ACTION: No action is required; this error is informational
only. An error reply was sent in response to the request. Trace
was not started by this request this time, but it
remains on.
MESSAGE: Bad message for current state.
Level: 3780 CLAS0001
CAUSE: The driver received a request to turn link tracing
on either too early or too late in the driver's life cycle,
or when the driver was already broken ("Cause" =
16-bit encoded value, giving driver input event code and current
state: Hewlett-Packard use only).
ACTION: Retry the same trace command later. An error reply
was sent in response to the request. Trace was not started by this
request this time, and remains off.
MESSAGE: A driver request failed.
Level: 3810 CLAS0001
CAUSE: While processing a request to turn link trace
on, the driver was unable to locate a free storage element in which
to save reply information ("Cause" = 32-bit status
returned by the call to pbt_dvr_save_msg).
ACTION: This informational error should be preceded by
another error giving a more specific reason for the failure; check
log data and look up that error also, for more actions to take.
Most likely the previous error was fatal and the driver is about
to "die", then will either attempt an auto-reset
or else require a manual shutdown and restart.
MESSAGE: Link tracing is already disabled.
Level: 3840 CLAS0001
CAUSE: The driver received a request to turn link tracing
off when it was already off. Typically this condition is caught
at the C.I. level, however in this case trace may be under the control
of a different mechanism.
ACTION: No action is required, this error is informational only.
An error reply was sent in response to the request. Trace was not stopped
by this request this time, but it remains off.
MESSAGE: A driver request failed.
Level: 3870 CLAS0001
CAUSE: While processing a request to turn link trace
on, the driver was unable to locate a free storage element in which
to save reply information ("Cause" = 32-bit status
returned by the call to pbt_dvr_save_msg).
ACTION: This informational error should be preceded by
another error giving a more specific reason for the failure; check
log data and look up that error also, for more actions to take.
Most likely the previous error was fatal and the driver is about
to "die", then will either attempt an auto-reset
or else require a manual shutdown and restart.
MESSAGE: Driver encountered a software problem.
Level: 3900 CLAS0001
CAUSE: Before attempting to forward a protocol rendezvous
(bind) request to its ISR, the driver discovered the ISR was already
in a "dead" state and unable to process requests
("Cause" = 32-bit status stating the driver is "dying").
ACTION: If the operator already knows the driver is in
the process of being closed, this error can be ignored. The driver
attempted to send an error reply for the rendezvous request. The
ISR may also be "dead" as a result of a serious previous error. A
diagnostic reset action may clear this condition.
MESSAGE: Cannot get ADA memory object.
Level: 3910 CLAS0001
CAUSE: During initial startup, the driver attempted to
obtain a memory object via the I/O system, but received a bad status
in the reply for that request ("Cause" = 32-bit
status from the reply message).
ACTION: The link did not start, and the driver attempted
to send back an error reply in response the configuration request
from the module configurator. Probably the amount of frozen memory
on the system is very high; if you have the GLANCE tool you can
try to check memory usage. Try retrying the operation again later,
or first terminate some applications and then retry.
MESSAGE: Driver encountered a software problem.
Level: 3930 CLAS0001
CAUSE: Before attempting to forward a protocol separate
(unbind) request to its ISR, the driver discovered the ISR was already
in a "dead" state and unable to process requests
("Cause" = 32-bit status stating the driver is "dying").
ACTION: If the operator already knows the driver is in
the process of being closed, this error can be ignored. The driver
attempted to send an error reply for the separate request. The ISR
may also be "dead" as a result of a serious previous error. A diagnostic
reset action may clear this condition.
MESSAGE: Bad message for current state.
Level: 3960 CLAS0001
CAUSE: Before attempting to forward a diagnostic or LINKCONTROL
statistics request to its ISR, the driver discovered the ISR was already in
a "dead" state and unable to process requests
("Cause" = 32-bit status stating the driver is "dying").
ACTION: If the operator already knows the driver is in the process of being
closed, this error can be ignored. The driver attempted to send an error
reply for the statistics request. The ISR may also be "dead" as a result of
a serious previous error.
A diagnostic reset action may clear this condition.
MESSAGE: Bad message for current state.
Level: 3990 CLAS0001
CAUSE: Before attempting to forward a diagnostic or LINKCONTROL
statistics request to its ISR, the driver discovered the ISR was already in
a "dead" state and unable to process requests
("Cause" = 32-bit status stating the driver is "dying").
ACTION: If the operator already knows the driver is in
the process of being closed, this error can be ignored. The driver
attempted to send an error reply for the statistics request. The
ISR may also be "dead" as a result of a serious previous error. A
diagnostic reset action may clear this condition.
MESSAGE: Bad message for current state.
Level: 4020 CLAS0001
CAUSE: Before attempting to forward a diagnostic hardware-control
request to its ISR, the driver discovered the ISR was already in a "dead"
state and unable to process requests ("Cause" = 16-bit
encoded value, giving driver input event code and current state:
Hewlett-Packard use only).
ACTION: If the operator already knows the driver is in the process
of being closed, this error can be ignored. The driver attempted to send an
error reply for the statistics request. The ISR may also be "dead" as a
result of a serious previous error. A diagnostic reset action may clear
this condition.
MESSAGE: Bad message for current state.
Level: 4030 CLAS0001
CAUSE: The driver received a release-memory reply message
it was not expecting ("Cause" = 16-bit encoded
value, giving driver input event code and current state: HP use only).
ACTION: The driver may already have changed state because
of a shutdown or another problem, in which case this message can
be ignored. Otherwise, the I/O system may be confused. The driver will drop
this message without further action. If the problem occurs repeatedly,
see Appendix A "Submitting a CR"
MESSAGE: Driver encountered a software problem.
Level: 4050 CLAS0001
CAUSE: Before attempting to forward a diagnostic or LINKCONTROL
statistics request to its ISR, the driver discovered the ISR was already in
a "dead" state and unable to process requests
("Cause" = 32-bit status stating the driver is "dying").
ACTION: If the operator already knows the driver is in the process
of being closed, this error can be ignored. The driver attempted to send an
error reply fro the statistics request. The ISR may also be "dead" as a
result of a serious previous error. A diagnostic reset action may clear
this condition.
MESSAGE: Unimplemented operation attempted.
Level: 4080 CLAS0001
CAUSE: The main driver DVR state machine was passed an
input event for which there is no processing implemented. Either
there is a driver bug or some data corruption has occurred ("Cause" =
32-bit ordinal value of the input event code: Hewlett-Packard use only).
ACTION: Try to determine which operator or program actions led to
this error. Then see Appendix A "Submitting a CR"
After this problem occurs, the driver will enter a "broken" state where is
may not respond to further requests. If possible, run the VGPBA tool
program, and use it to force a driver dump, then forward the resulting
NETDMP##.PUB.SYS file to HP for analysis. After a dump, the driver
will attempt to auto-reset itself and continue. You may also use VGPBA to
attempt a manual reset of the driver, after which it may
be possible to continue.
MESSAGE: Cannot install interrupt handler.
Level: 4110 CLAS0001
CAUSE: During initial driver startup, the driver was
unable to add its ISR into the MPE I/O system, as an interrupt handler
routine for any adapter card interrupts on that EIR bit ("Cause" =
32-bit status returned by the call to io_config_int).
ACTION: The driver did not start up. There is probably an MPE
software installation problem, with incomplete or incompatible O/S software.
Verify the system is running an MPE release which supports PCI 100Base-T
link drivers. The only other cause is a software bug; see
Appendix A "Submitting a CR"
MESSAGE: Internal driver error.
Level: 4140 CLAS0001
CAUSE: During initialization, the driver attempted to
obtain information about the PCI device (BAR information) from the
I/O system but encountered an error ("Cause" =
32-bit status returned from io_get_pci_dev_info).
ACTION: The driver did not start up. Check that the 100Base-T
adapter card is properly seated in its PCI slot and that the I/O path has
been properly configured. If the problem persists, it may indicate a
problem with the system software installation; the software may need to be
reinstalled, or additional software patches may be required, see
Appendix A "Submitting a CR" or contact your
Hewlett-Packard Representative to verify you have the required
level of software installed.
MESSAGE: Driver encountered a software problem.
Level: 4170 CLAS0001
CAUSE: While attempting to reply to a change multicast
list request (most likely from upper level subsystem DLPI), the
driver encountered an error sending the reply message ("Cause" =
32-bit status returned from pbt_dvr_send_reply).
ACTION: The process which sent the multicast list request message
(likely DLPI) may be hung waiting for the reply message that the driver was
unable to send.
If that is the case, try stopping the link to see if that allows the DLPI
process to terminate. Additional errors may have been logged which give
more information about why the send failed.
If the problem persists, collect all available information logged by this
link (driver) from the log file; also check for driver-generated dump files
(NETDMP##.PUB.SYS), see
Appendix A "Submitting a CR"
MESSAGE: Link connected.
Level: 4200 CLAS0002
CAUSE: The first upper layer subsystem to bind to the
driver triggered a link connect, which was successful ("Mode" =
the connection mode: 100BT, 10BT, etc.; "Duplex" =
Full or Half). This event is also logged after the link or cable
has been successfully reconnected after being disconnected, or on
a link reconnect following a severe line hit or other recoverable error.
ACTION: This event is informational only.
No action is needed unless the message appears frequently while the link is
up, indicating possible cabling problems; make sure cabling is securely
connected and properly routed away from sources of interference, and is of
the proper UTP category or grade for the type of link (CAT-5 for
100Base-T).
MESSAGE: Link disconnected.
Level: 4230 CLAS0002
CAUSE: The last upper layer subsystem has unbound itself from the
driver, triggering a link disconnect This event is also logged if the link
unexpectedly drops due to a cable disconnect, hub retrain request,
powerfail, severe line hit, or other recoverable error ("Status" = 32-bit
status giving the reason for the disconnect, 0 = normal).
ACTION: This event is informational only. If the network
is being shut down, no action is required.
However, if the link was supposed to be up or the message appears
frequently while the link is up, this indicates possible cabling problems;
make sure cabling is securely connected and properly routed away from
sources of interference, and is of the proper UTP category or grade for
the type of link (CAT-5 for 100Base-T).
MESSAGE: Driver is starting adapter card.
Level: 4260 CLAS0003
CAUSE: The driver has completed initial startup of the
adapter card, or a restart following a reset, dump, or other recoverable
condition ("Status" = 32-bit status giving the
result of the startup attempt, 0 = successful).
ACTION: This event is informational. No action is required
unless the status is nonzero. Nonzero status indicates the startup
failed; this may be preceded by other specific errors.
MESSAGE: Configuration failed.
Level: 4290 CLAS0001
CAUSE: After successful or unsuccessful completion of
initial hardware startup, the driver attempted to reply to a pending
configuration request from its module configurator, but encountered
an error on the send ("Cause" = 32-bit status
returned by the call to pbt_dvr_send_reply).
ACTION: This is a fatal software error. It might be caused
by heavy CPU load, or by attempting to operate the network subsystem
or tool which started the link at too low of a CPU process priority,
causing a timeout. Any condition, such as a timeout or abort, which
causes the driver's module configurator to cease awaiting
the reply and dispose of its reply port, might also cause this error.
The module configurator did not receive the reply, therefore network and/or
link startup will fail. The driver now "dies" and awaits a shutdown, which
the module configurator should attempt automatically.
MESSAGE: Configuration failed.
Level: 4320 CLAS0001
CAUSE: Following an unsuccessful initial startup of its
adapter card, or a restart because of a powerfail or reset, the
driver sent a bad reply to the pending config request message, if
any, logged this error, then died ("Cause" = 32-bit
status giving the reason startup failed).
ACTION: This event indicates a fatal driver software condition.
May be preceded by other errors giving more information about the
original failure, which may help you determine whether it was a
hardware or software problem.
If this occurred on initial startup, the driver's module configurator
should shut the driver down automatically. If not, it may mean the adapter
card has failed because of a hardware problem, or that a software reset
attempt has failed. The driver may need to be manually shut down and
restarted, using an appropriate network subsystem command (such as
:NETCONTROL STOP). If you wish, you may first try running the VGPBA
diagnostic; execute the Reset function to see if that clears the
problem.
MESSAGE: Configuration failed.
Level: 4350 CLAS0001
CAUSE: During initial driver startup, the driver encountered an
error during configuration ("Cause" = 32-bit status returned by the call to
pbt_dvr_port_msg_exec). Probably there are already too many
opens against the driver.
ACTION: This informational error should be preceded by
another error giving a more specific reason for the failure; check
log data and look up that error also, for more actions to take.
This error can only be caused by a bug, a mismatch between driver's
state and open table.
MESSAGE: Driver is starting up.
Level: 4380 CLAS0003
CAUSE: The driver has just completed initial configuration
and is now starting up ("Vers" = driver version
number, "Pda" = 64-bit pointer to driver context
area: HP use only). This event only occurs on initial startup, not
on restarts after resets, etc.
ACTION: This event is informational. No action is
required.
MESSAGE: Configuration failed.
Level: 4410 CLAS0001
CAUSE: During initial driver startup, the driver encountered
an error during configuration, while attempting to request ADA memory
from the MPE I/O system ("Cause" = 32-bit status
returned by the call to pbt_dvr_port_msg_exec).
Probably a port message could not be sent.
ACTION: This informational error should be preceded by
another error giving a more specific reason for the failure; check
log data and look up that error also, for more actions to take.
The open request failed. The driver will now "die" and must be shut down;
the module configurator should do this automatically.
MESSAGE: Configuration failed.
Level: 4440 CLAS0001
CAUSE: While processing a driver open from an upper layer
subsystem, which was not the first open against the driver, the driver
encountered an error during configuration ("Cause" = 32-bit status returned
by the call to pbt_dvr_port_msg_exec). Probably there are already
too many opens against the driver.
ACTION: This informational error should be preceded by
another error giving a more specific reason for the failure; check
log data and look up that error also, for more actions to take.
The driver returned a bad result to the subsystem, and the
open request failed. The driver will continue to operate all other
subsystems as before.
MESSAGE: Configuration failed.
Level: 4470 CLAS0001
CAUSE: While processing a driver open from an upper layer
subsystem, which was not the first open against the driver, the
driver encountered an error during configuration ("Cause" =
32-bit status returned by the call to pbt_dvr_send_reply).
Probably a port message could not be sent.
ACTION: The driver allows 11 simultaneous opens. The open
attempt by the additional subsystem failed. Shut down any subsystems that
are not currently needed and try again.
A side-effect of this error may be that the driver becomes unusable; if so,
run VGPBA and execute the Reset function to see
if that restores normal operation.
MESSAGE: Bad message for current state.
Level: 4500 CLAS0001
CAUSE: The driver received a new open from an upper layer
subsystem, at a time the driver was not able to process these requests,
such as during shutdown or after a fatal software error ("Cause" =
16-bit encoded value, giving driver input event code and current
state: Hewlett-Packard use only).
ACTION: The open failed. Check the system console; if the driver
is shutting down or doing a dump, wait until that completes. Retry the
operation. If the problem persists, the driver may be broken; run the VGPBA
diagnostic and attempt a Reset function. If the problem still persists, run
VGPBA, attempt a Dump function, and save the resulting file
(NETDMP##.PUB.SYS) for analysis by Hewlett-Packard. If the driver
still does not become usable after this, use Control-B at the console to
halt the system, take a memory dump, and reboot, see
Appendix A "Submitting a CR"
MESSAGE: Bad message for current state.
Level: 4560 CLAS0001
CAUSE: Before attempting to forward a diagnostic request
to its ISR, the driver discovered the ISR was already in a "dead" state
and unable to process requests ("Cause" = 32-bit
status stating the driver is "dying").
ACTION: If the operator already knows the driver is in the process
of being closed, this error can be ignored. The driver attempted to send an
error reply for the diagnostic request. The ISR may also be "dead" as a
result of a serious previous error. A diagnostic reset action may clear
this condition.
MESSAGE: Driver initialization failed.
Level: 4590 CLAS0001
CAUSE: While processing its very first startup message, the driver
encountered a problem ("Cause" = 32-bit status returned by the call to
pbt_dvr_chk_chard_type). Probably the configured hardware is not
present, is not the correct kind of adapter card, or there was a problem
configuring the ISR into the I/O system.
ACTION: This informational error should be preceded by
another error giving a more specific reason for the failure; check
log for that error and look it up also, for more actions to take.
The driver will attempt to send an error reply for the startup request.
It then enters a "broken" state and awaits a shutdown, which the module
configurator should attempt automatically.
MESSAGE: Driver initialization failed.
Level: 4620 CLAS0001
CAUSE: The driver was unable to successfully bind to
its lower manager; the lower manager's port number supplied
by the I/O system is nil.
ACTION: The link did not start, because erroneous information
was passed to the driver by the I/O system. This could indicate
a serious problem with the system software, or a problem with the
I/O system. If the problem persists, halt the system as soon as
possible after the error occurs and generate a dump; see
Appendix A "Submitting a CR"
MESSAGE: Cannot send a port message.
Level: 4650 CLAS0001
CAUSE: During initialization, the driver was unable to
successfully bind to its lower manager. Probably an underlying call
to send_msg failed.
ACTION: The link did not start. This error may be preceded
by other errors in the log file giving a more specific reason for
the failure. Check the log data and look up additional errors for
more possible actions. You may retry the operation (try starting
the link again), but the hardware path may be unusable. If the problem
persists, halt the system and generate a dump; see
Appendix A "Submitting a CR"
MESSAGE: Driver initialization failed.
Level: 4680 CLAS0001
CAUSE: The driver was unable to successfully bind to
its lower manager; an error occurred when attempting to send a bind
request message to the lower.
ACTION: The link did not start. This error may be preceded
by other errors in the log file giving a more specific reason for
the failure. Check the log data and look up additional errors for
more possible actions. You may retry the operation (try starting
the link again), but the hardware path may be unusable. If the problem
persists, halt the system and generate a dump; see
Appendix A "Submitting a CR"
MESSAGE: Cannot send a port message.
Level: 4710 CLAS0001
CAUSE: The driver received a second copy of the first
initialization message it would ever get, indicating a second attempt
to start the driver.
ACTION: The driver sent an error reply in response to
the message. Further action may not be required. If the problem
occurs frequently, try to determine what operator commands or actions
trigger the error, then see
Appendix A "Submitting a CR"
MESSAGE: Cannot send a port message.
Level: 4740 CLAS0001
CAUSE: The driver was unable to successfully unbind from
its lower manager. Probably an underlying call to send_msg failed.
ACTION: No action is required; this is an informational
message. This error may be preceded by other errors in the log file
giving a more specific reason for the failure. Check the log data
and look up additional errors for more possible actions. If the
problem persists, halt the system and generate a dump; see
Appendix A "Submitting a CR"
MESSAGE: Cannot send a port message.
Level: 4770 CLAS0001
CAUSE: During shutdown, the driver was unable to successfully
unbind from its lower manager. Probably an underlying call to
send_msg failed.
ACTION: No action is required; this is an informational message.
There might be a system problem that precipitated the shutdown which is
preventing messages from being sent successfully. If the problem persists,
collect all the relevant data from the log file and check those errors for
additional actions. If the problem persists halt the system as soon as
possible after the problem occurs and generate a dump; see
Appendix A "Submitting a CR"
MESSAGE: Late dump-done message received. Dump took too long.
Level: 4800 CLAS0001
CAUSE: The driver received a driver-dump completion message
when it was not working on a dump ("Cause" = 32-bit
status saying there was a bad message for the current state).
ACTION: This error is informational only. Probably the
Network Dump Process was delayed by other system processing, such
that it exceeded the time limit set by the driver. The resulting
dump file may or may not be incomplete. A more serious driver problem
has already occurred, after which the driver will now attempt to
auto-reset and continue. If you are trying to reproduce a specific
problem but this error occurs every time, reduce the CPU or disk
activity load before the next attempt.
If load is not the problem, see
Appendix A "Submitting a CR"
MESSAGE: Internal error while initiating a dump. Dump failed.
Level: 4830 CLAS0001
CAUSE: The driver's dump timer popped while
performing a dump operation ("Cause" = 32-bit
status indicating a timeout has occurred). Probably a heavy CPU
or disk activity load caused the Network Dump Process to take longer
than the time allowed by the driver.
ACTION: This error is informational only. The resulting
dump file may or may not be incomplete. A more serious driver problem
has already occurred, and by the time this error is logged, the
driver is already attempting to auto- reset and continue. If you
are trying to reproduce a specific problem but this error occurs
every time, reduce the CPU or disk activity load before the next
attempt.
MESSAGE: Cannot initiate a dump. Already dumping.
Level: 4860 CLAS0001
CAUSE: A user attempted to force a driver dump while
a previous driver dump was still occurring ("Cause" =
32-bit status saying a driver dump is starting).
ACTION: A dump of your problem is already being produced. Wait a
minute or two for the dump to finish. Forward the resulting
NETDMP##.PUB.SYS to Hewlett-Packard for analysis if necessary, and
see Appendix A "Submitting a CR"
MESSAGE: A driver dump is starting.
Level: 4890 CLAS0001
CAUSE: A user is forcing a driver dump to occur, typically
via the VGPBA diagnostic tool program ("Cause" =
32-bit status saying the driver dump was forced).
ACTION: This error is informational only. The dump is probably
being forced because the system operator suspects a link driver problem.
Forward the resulting NETDMP##.PUB.SYS file to Hewlett-Packard for
analysis if necessary, and see
Appendix A "Submitting a CR"
MESSAGE: Driver encountered a hardware problem.
Level: 4920 CLAS0001
CAUSE: During initial startup, while attempting to initialize
the ADA data structure, the driver encountered an error. Previous
errors may also have been logged which provide more detail on the error.
ACTION: The link did not start, and the driver attempted to send
back an error reply in response to the configuration request from the
module configurator. Retry the operation again. If the problem persists,
try forcing a driver dump via the VGPBA diagnostic tool program; send the
resulting NETDMP##.PUB.SYS to Hewlett-Packard for
analysis.
MESSAGE: Cannot get ADA memory object.
Level: 4950 CLAS0001
CAUSE: During initial startup, the driver attempted to
obtain a memory object via the I/O system, but received a bad status
in the reply for that request ("Cause" = 32-bit
status from the reply message).
ACTION: The link did not start, and the driver attempted
to send back an error reply in response the configuration request
from the module configurator. Probably the amount of frozen memory
on the system is very high; if you have the GLANCE tool you can
try to check memory usage. Try retrying the operation again later,
or first terminate some applications and then retry.
MESSAGE: Bad message for current state.
Level: 4980 CLAS0001
CAUSE: The driver received a get-memory reply message it was not
expecting ("Cause" = 16-bit encoded value, giving driver input event code
and current state: Hewlett-Packard use only).
ACTION: The driver may already have changed state because
of a shutdown or another problem, in which case this message can
be ignored. Otherwise, the I/O system may be confused. Either way,
some memory may have been lost. The driver will drop this message
without further action. If the problem occurs frequently, see
Appendix A "Submitting a CR"
MESSAGE: Cannot release ADA memory object.
Level: 5010 CLAS0001
CAUSE: During shutdown, the driver requested the I/O
system to release a memory object, but received an error reply in
response ("Cause" = 32-bit status from the mem_reply message).
ACTION: This error should not occur. The driver may be
confused, or there is a system problem. However, the driver will
ignore the error and attempt to continue with the shutdown. If this
problem happens frequently when the driver is shutting down, see
Appendix A "Submitting a CR"
MESSAGE: Bad message for current state.
Level: 5040 CLAS0001
CAUSE: The driver received a release- memory reply message it was
not expecting ("Cause" = 16-bit encoded value, giving driver input event
code and current state: Hewlett-Packard use only).
ACTION: The driver may already have changed state because of a
shutdown or another problem, in which case this message can be ignored.
Otherwise, the I/O system may be confused. The driver will drop this
message without further action. If the problem occurs repeatedly, see
Appendix A "Submitting a CR"
MESSAGE: Bad message for current state.
Level: 5070 CLAS0001
CAUSE: The driver received a request to reset itself
too early in the driver's life cycle before it had ever
brought up the adapter card, or at a point late in shutdown when
recovery is no longer needed ("Cause" = 16-bit
encoded value, giving driver input event code and current state:
Hewlett-Packard use only).
ACTION: This error is informational only. If the reset request was
manually sent by a user, such as via the VGPBA diagnostic tool, an error
reply will be returned; resets are not allowed (or needed) when the driver
is in the state it is currently in. If the reset was automatically
generated by the driver in response to some serious error it detected, this
log event means it is being ignored.
MESSAGE: A driver request failed.
Level: 5100 CLAS0001
CAUSE: During a link close operation, the driver encountered
an error while unconfiguring the link ("Cause" =
32-bit status returned by the call to pbt_dvr_port_msg_exec).
ACTION: The subsystem close did not work. The driver attempted
to return an error reply to the sending subsystem. Reaction to that message
is subsystem-dependent. Probably the subsystem passed an invalid
open ID, or tried to close a link it had not opened. If this problem
happens every time the same subsystem is closed, submit an CR against
that subsystem, describing the problem; see
Appendix A "Submitting a CR"
MESSAGE: Cannot send a port message.
Level: 5130 CLAS0001
CAUSE: During a link close operation, the driver encountered
an error while sending an unconfigure reply message to an upper
layer subsystem ("Cause" = 32-bit status returned
by the call to pbt_dvr_send_reply).
ACTION: This informational error should be preceded by
another error giving a more specific reason for the failure; check
log data and look up that error also, for more actions to take.
The subsystem's access to the link was closed, but the subsystem did not
get the reply; reaction to this situation is subsystem-dependent.
The subsystem have already terminated. If this problem happens every
time the same subsystem is closed, submit an CR against that subsystem,
describing the problem; see
Appendix A "Submitting a CR"
The driver may now enter a broken state and not respond to further
requests, requiring a system reboot to completely shut the
driver down. If other subsystems still need to use the link, if
you wish you may try running the VGPBA diagnostic; execute the Reset
function to see if that restores access for the other subsystems,
until a reboot can happen.
MESSAGE: Bad message for current state.
Level: 5160 CLAS0001
CAUSE: The driver received an unconfigure request message
before it received its first configure request ("Cause" =
16-bit encoded value, giving driver input event code and current
state: Hewlett-Packard use only).
ACTION: This error is informational only. The driver attempted
to return an error reply to the sending subsystem. If this problem happens
frequently, try to determine what actions lead to the problem, then see
Appendix A "Submitting a CR"
MESSAGE: Unimplemented operation attempted.
Level: 5220 CLAS0001
CAUSE: The main driver DVR state machine was passed an
input event for which there is no processing implemented. Either
there is a driver bug or some data corruption has occurred ("Cause" =
32-bit ordinal value of the input event code: Hewlett-Packard use only).
ACTION: Try to determine which operator or program actions led to
this error. Then see Appendix A "Submitting a CR"
After this problem occurs, the driver will enter a "broken" state where is
may not respond to further requests. If possible, run the VGPBA tool
program, and use it to force a driver dump, then forward the resulting
NETDMP##.pub.sys file to Hewlett-Packard for analysis. After a
dump, the driver will attempt to auto-reset itself and continue. You may
also use VGPBA to attempt a manual reset of the driver, after which it may
be possible to continue.
MESSAGE: Driver received an unknown port message.
Level: 5250 CLAS0001
CAUSE: Some module on the system has sent the driver
a message having an unknown message descriptor. The driver does
not implement any messages having that descriptor ("Cause" =
32-bit value of the message descriptor field).
ACTION: The driver took no action on the message, and
dropped it. However, if the problem occurs frequently, your system
may not be set up properly. The driver traces the message which
it received. If you can repeat the problem, first enable link tracing.
Then reproduce the problem, stop tracing, and save the resulting
trace data file for analysis by Hewlett-Packard, see
Appendix A "Submitting a CR"
MESSAGE: Cannot send a port message.
Level: 5650 CLAS0001
CAUSE: During ISR processing, an attempt by the ISR to
wake up the driver by sending a message to it failed ("Cause" =
32-bit status returned by the call to send_msg).
ACTION: This error is likely an indication of a more serious
system software problem, and may be followed by a system abort.
Probably all message frames have been exhausted by some module running
on the system. Further recovery actions may not be possible; if
the system fails, take a memory dump and reboot.
The driver wakeup did not occur, so a link hang is now possible. It is also
possible that if a system abort does not occur, other activity, such as
transmissions by upper layer protocols, will awaken the driver, such that
normal operation continues. If the link hangs and a system abort does not
occur, try using VGPBA to attempt a manual reset, or try stopping and
restarting all networks using the link driver.
MESSAGE: (Varies)
Level: 5680 CLAS0001
CAUSE: While attempting to request action from its DVR module, the
driver's ISR found that no available communication frames were available on
the referenced queue ("Cause" is not used here).
ACTION: This is a fatal software error. The number of
available comm frames is not configurable, and the driver cannot
operate if frames run out. After reporting this error, the driver
will attempt a driver dump, then will auto-reset and attempt to
continue. Typically followed by another error giving more information
about what kind of comm the driver was trying to send; check log
data for that error and look it up also.
Collect binary copies of all dump files (NETDMP##.PUB.SYS) on tape
for analysis by Hewlett-Packard and see
Appendix A "Submitting a CR"
MESSAGE: Cannot send a port message.
Level: 5710 CLAS0001
CAUSE: During ISR processing, an attempt by the ISR to
send a reply to a previously received message failed ("Cause" =
32-bit status returned by the call to send_msg).
ACTION: This error is likely an indication of a more serious
system software problem, and may be followed by a system abort.
Probably all message frames have been exhausted by some module running
on the system. Further recovery actions may not be possible; if
the system fails, take a memory dump and reboot.
If the link hangs and a system abort does not occur, try using VGPBA to
attempt a manual reset, or try stopping and restarting all networks using
the link driver.
MESSAGE: Driver encountered a hardware problem.
Level: 5740 CLAS0001
CAUSE: The ISR attempted to terminate transmit processing
on the PCI 100Base-T card (e.g., in response to a reset or shutdown
request, in order to change active characteristics on the link,
etc.), but did not receive the expected acknowledgment from the
card indicating the request was received and processed.
ACTION: The driver may become unusable or attempt an auto-reset.
If the driver appears to hang, try to shutdown the network manually
and then restart it. Most likely, once the reset is complete and
the driver has "reinitialized" the hardware (card),
the driver can resume operating normally.
If the problem persists, it could indicate a bad PCI 100Base-T card. A new
adapter card may be needed.
MESSAGE: Driver encountered a hardware problem.
Level: 5770 CLAS0001
CAUSE: The ISR attempted to terminate receive processing
on the PCI 100Base-T card (e.g., in response to a reset or shutdown
request, in order to change the active characteristics of the link,
etc.), but did not receive the expected acknowledgment from the
card indicating the request was received and processed.
ACTION: The driver may become unusable or attempt an auto-reset.
If the driver appears to hang, try to shutdown the network manually
and then restart it. Most likely, once the reset is complete and
the driver has "reinitialized" the hardware (card),
the driver can resume operating normally.
If the problem persists, it could indicate a bad PCI 100Base-T card. A new
adapter card may be needed.
MESSAGE: Driver has detected data corruption.
Level: 5800 CLAS0001
CAUSE: While starting up, the ISR was unable to allocate a
transmit descriptor in order to send an initial setup frame to the PCI
100Base-T card. This indicates a corruption of the driver's data
structures, since the descriptor ring should be in a newly initialized
state.
ACTION: The driver did not start up, though it may attempt an
auto-reset. Check to see if the driver was able to generate a dump file
(NETDMP##.PUB.SYS) file, and send the file to Hewlett-Packard for
analysis; see
Appendix A "Submitting a CR"
MESSAGE: Driver has detected data corruption.
Level: 5830 CLAS0001
CAUSE: While starting up, the ISR attempted to allocate
a transmit descriptor in order to send an initial setup frame to
the PCI 100Base-T card, but did not get back the "head" descriptor
as expected. This indicates a corruption of the driver's
data structures, since the descriptor ring should be in a newly
initialized state.
ACTION: The driver did not start up, though it may attempt
an auto-reset. Check to see if the driver was able to generate a
dump file (NETDMP##.PUB.SYS) file, and send the file to
Hewlett-Packard for analysis; see
Appendix A "Submitting a CR"
MESSAGE: (Varies)
Level: 5860 CLAS0001
CAUSE: During startup, while attempting to build an initial
setup frame for the PCI 100Base-T card, the ISR encountered an error.
Other error messages may have been logged which describe the error
in more detail.
ACTION: The driver did not start up, though it may attempt
an auto-reset. Check to see if the driver generated an internal
dump file (NETDMP##.PUB.SYS), and send the file to Hewlett-Packard
for analysis; see
Appendix A "Submitting a CR"
MESSAGE: Could not allocate or reassign an I/O virtual address.
Level: 5890 CLAS0001
CAUSE: During startup, while attempting to send an initial
setup frame to the PCI 100Base-T card, the ISR was not able to map
the I/O virtual address of the data ("Cause" = 32-bit status returned from
lnk_load_io_addr_for_virt). This could indicate resource
contention or severe memory pressure on the system.
ACTION: The driver did not start up, though it may attempt
an auto-reset. If the system is under heavy load, try shutting down
any unnecessary applications and subsystems, and try again. If the
problem persists, this could indicate a serious problem in the I/O
system. Halt the system as soon as possible after the problem occurs
and generate a dump; see
Appendix A "Submitting a CR"
MESSAGE: Driver encountered a hardware problem.
Level: 5920 CLAS0001
CAUSE: During startup, while attempting to complete the
hardware initialization sequence for the PCI 100Base-T card, the
ISR did not receive the expected response from the card (the transmit
process did not suspend after the initial setup frame was sent).
ACTION: The driver did not start up, though it may attempt
an auto-reset. This error could indicate a problem with the PCI
100Base-T adapter card. Check all connections, make sure the card
is properly seated in the PCI slot, and try to restart the link.
If the problem persists, try replacing the card.
MESSAGE: EEPROM read error on adapter card.
Level: 5950 CLAS0001
CAUSE: During link startup or reset, the driver attempted
to read the adapter card's factory station address from
the card's EEPROM non-volatile storage chip, but the read failed.
ACTION: EEPROM read operations are timing-sensitive. If the load
on the system (CPU) is very high, retry the startup operation when the
system is under a lighter load. If the problem persists, the adapter card
has probably failed; try replacing the card.
MESSAGE: Unable to write to adapter card PCI configuration space.
Level: 5980 CLAS0001
CAUSE: During driver startup or reset, the driver attempted
to write the memory BAR information to the adapter card's
PCI configuration space, but the I/O system reported an error. ("Cause" =
32-bit status returned from io_pci_cfg_write_bit32).
ACTION: The adapter card may have been removed, moved to a
different slot, may not be making proper contact with the PCI backplane,
or may not be responding. If the I/O slot has a power indicator, verify it
is on. Reseat the board, and if necessary call your Hewlett-Packard
representative for hardware assistance. If the problem persists,
the adapter card may be bad; try replacing the card.
MESSAGE: Unable to read from adapter card PCI configuration space.
Level: 6010 CLAS0001
CAUSE: During driver startup or restart, the driver attempted
to read the subsystem ID register from the adapter card's
PCI configuration space, but the I/O system reported an error. ("Cause" =
32-bit status returned from io_pci_cfg_read_bit32).
ACTION: The adapter card may have been removed, moved to a
different slot, may not be making proper contact with the PCI backplane,
or may not be responding. If the I/O slot has a power indicator, verify it
is on. Reseat the board, and if necessary call your Hewlett-Packard
representative for hardware assistance. If the problem persists,
the adapter card may be bad; try replacing the card.
MESSAGE: Unable to read from adapter card PCI configuration space.
Level: 6040 CLAS0001
CAUSE: During driver startup or restart, the driver attempted
to read the configuration ID register from the adapter card's
PCI configuration space, but the I/O system reported an error. ("Cause" =
32-bit status returned from io_pci_cfg_read_bit32).
ACTION: The adapter card may have been removed, moved to a
different slot, may not be making proper contact with the PCI backplane,
or may not be responding. If the I/O slot has a power indicator, verify it
is on. Reseat the board, and if necessary call your Hewlett-Packard
representative for hardware assistance. If the problem persists,
the adapter card may be bad; try replacing the card.
MESSAGE: Unable to read from adapter card PCI configuration space.
Level: 6070 CLAS0001
CAUSE: During driver startup or restart, the driver attempted
to read the configuration revision information from the adapter
card's PCI configuration space, but the I/O system reported
an error. ("Cause" = 32-bit
status returned from io_pci_cfg_read_bit32).
ACTION: The adapter card may have been removed, moved to a
different slot, may not be making proper contact with the PCI backplane,
or may not be responding. If the I/O slot has a power indicator, verify it
is on. Reseat the board, and if necessary call your Hewlett-Packard
representative for hardware assistance. If the problem persists,
the adapter card may be bad; try replacing the card.
MESSAGE: Unable to write to adapter card PCI configuration space.
Level: 6100 CLAS0001
CAUSE: During driver startup or reset, the driver attempted
to write data to the device and driver area in the adapter card's PCI
configuration space, but the I/O system reported an error. ("Cause" =
32-bit status returned from io_pci_cfg_write_bit32).
ACTION: The adapter card may have been removed, moved to a
different slot, may not be making proper contact with the PCI backplane,
or may not be responding. If the I/O slot has a power indicator, verify it
is on. Reseat the board, and if necessary call your Hewlett-Packard
representative for hardware assistance. If the problem persists,
the adapter card may be bad; try replacing the card.
MESSAGE: Unable to read from adapter card PCI configuration space.
Level: 6130 CLAS0001
CAUSE: During driver startup or restart, the driver attempted to
read the command and status register from the adapter card's PCI
configuration space, but the I/O system reported an error. ("Cause" =
32-bit status returned from io_pci_cfg_read_bit32).
ACTION: The adapter card may have been removed, moved to a
different slot, may not be making proper contact with the PCI backplane,
or may not be responding. If the I/O slot has a power indicator, verify it
is on. Reseat the board, and if necessary call your Hewlett-Packard
representative for hardware assistance. If the problem persists,
the adapter card may be bad; try replacing the card.
MESSAGE: Unable to write to adapter card PCI configuration space.
Level: 6160 CLAS0001
CAUSE: During driver startup or reset, the driver attempted
to write data to the command and status register in the adapter
card's PCI configuration space, but the I/O system reported
an error. ("Cause" = 32-bit
status returned from io_pci_cfg_write_bit32).
ACTION: The adapter card may have been removed, moved to a
different slot, may not be making proper contact with the PCI backplane,
or may not be responding. If the I/O slot has a power indicator, verify it
is on. Reseat the board, and if necessary call your Hewlett-Packard
representative for hardware assistance. If the problem persists,
the adapter card may be bad; try replacing the card.
MESSAGE: Unable to write to adapter card PCI configuration space.
Level: 6190 CLAS0001
CAUSE: During driver startup or reset, the driver attempted to
write data to the latency timer register in the adapter card's PCI
configuration space, but the I/O system reported an error. ("Cause" =
32-bit status returned from io_pci_cfg_write_bit32).
ACTION: The adapter card may have been removed, moved to a
different slot, may not be making proper contact with the PCI backplane,
or may not be responding. If the I/O slot has a power indicator, verify it
is on. Reseat the board, and if necessary call your Hewlett-Packard
representative for hardware assistance. If the problem persists, the
adapter card may be bad; try replacing the card.
MESSAGE: Driver could not identify the expected PHY on card.
Level: 6390 CLAS0001
CAUSE: After verifying the PHY chip on the adapter card
had been successfully reset, the driver checked the ID of the PHY,
but found it did not match any ID expected for this kind of adapter
card ("Cause" = 32-bit PHY ID
obtained from the card).
ACTION: The PHY chip may have gone bad, or the software may be out
of date.
The link did not connect. Following this error, the driver may "die" and
require a manual shutdown of the network. If the same problem persists even
after the software version has been verified and the adapter card has been
replaced with a known-good card, see
Appendix A "Submitting a CR"
MESSAGE: Driver encountered a software error.
Level: 6420 CLAS0001
CAUSE: While the ISR was attempting to reset the PHY,
an error occurred when the driver tried to start a system timer
("Cause" = 32-bit status from lnk_timer_start).
ACTION: The driver may become unusable or may try and auto-reset.
If necessary, stop and restart the link manually. Check for any driver dump
files (NETDMP##.PUB.SYS) and if present, send to Hewlett-Packard
for analysis; see
Appendix A "Submitting a CR"
MESSAGE: Driver encountered a hardware problem.
Level: 6450 CLAS0001
CAUSE: While the ISR was attempting to reset the PHY,
a read of the MII failed.
ACTION: The driver may have become unusable and may try
to auto-reset. If necessary, stop and restart the link manually.
If the problem persists, the PHY chip may have gone bad; try replacing
the PCI 100Base-T adapter card.
MESSAGE: Driver encountered a software problem.
Level: 6480 CLAS0001
CAUSE: While the ISR was attempting to reset the PHY,
an error occurred when the driver tried to start a system timer
("Cause" = 32-bit status from lnk_timer_start).
ACTION: The driver may become unusable or may try and auto-reset.
If necessary, stop and restart the link manually. Check for any driver dump
files (NETDMP##.PUB.SYS) and if present, send to Hewlett-Packard
for analysis; see
Appendix A "Submitting a CR"
MESSAGE: Adapter card PHY did not finish reset in the time allowed.
Level: 6510 CLAS0001
CAUSE: During a link connect sequence, the driver tried 3 times to
reset the PHY chip, but it still did not go "ready" after the reset.
ACTION: The PHY chip on the adapter card may be bad; replace the
card. If the problem persists with a known good adapter card, contact your
Hewlett-Packard representative for assistance.
MESSAGE: Driver encountered a software problem.
Level: 6540 CLAS0001
CAUSE: While the ISR was attempting to reset the PHY,
an error occurred when the driver tried to start a system timer
("Cause" = 32-bit status from lnk_timer_start).
ACTION: The driver may become unusable or may try and auto-reset.
If necessary, stop and restart the link manually. Check for any driver dump
files (NETDMP##.PUB.SYS) and if present, send to Hewlett-Packard
for analysis; see
Appendix A "Submitting a CR"
MESSAGE: Driver detected a hardware problem.
Level: 6570 CLAS0001
CAUSE: The driver was unable to initialize the PHY chip
on the adapter card.
ACTION: The driver may not start, or may become unusable or try to
auto-reset. Additional errors may have been logged which provide more
specific information about the error; check those errors for additional
suggested actions.
If the problem persists, the PHY chip on the adapter card may be bad; try
replacing the card. If it still occurs with a known good card, contact your
Hewlett-Packard representative.
MESSAGE: Driver detected a software problem.
Level: 6600 CLAS0001
CAUSE: While the ISR was attempting to initialize the
PHY, an error occurred when the driver tried to start a system timer
("Cause" = 32-bit status from lnk_timer_start).
ACTION: The driver may become unusable or may try and auto-reset.
If necessary, stop and restart the link manually. Check for any driver dump
files (NETDMP##.PUB.SYS) and if present, send to Hewlett-Packard
for analysis; see
Appendix A "Submitting a CR"
MESSAGE: Driver detected a hardware problem.
Level: 6630 CLAS0001
CAUSE: During a 100Base-T connect sequence, the driver
attempted to check for presence of a link signal, but encountered
an error trying to read from a register on the PHY chip ("Cause" =
32-bit status from the call to pbt_mii_read16).
ACTION: If there has been an interruption of power, the
driver may recover automatically; otherwise, the MII bus may have
failed; replace the adapter card. If the same problem persists,
see Appendix A "Submitting a CR"
MESSAGE: Driver detected a hardware problem.
Level: 6660 CLAS0001
CAUSE: During a 100Base-T connect sequence, the driver
attempted to check for presence of a link signal, but encountered
an error trying to read from the generic status register on the
PHY chip ("Cause" = 32-bit status from the call
to pbt_mii_read16).
ACTION: If there has been an interruption of power, the
driver may recover automatically. Otherwise, the MII bus may have
failed; replace the adapter card. If the same problem persists,
see Appendix A "Submitting a CR"
MESSAGE: Autonegotiation reports link settings are incompatible with hub.
Level: 6690 CLAS0001
CAUSE: If this error occurs, it is probably because the
link has reported a remote fault. Usually this means the adapter
card and the hub or switch to which it is connected, have failed
to agree on a link speed and duplex setting acceptable to both.
ACTION: Verify that the cable is securely connected to the adapter
card at one end, and to a 100Base-TX or 10Base-T hub at the other.
Verify the cable is a correctly wired, Category-5 UTP cable.
Category 3 or 4 cables are not acceptable.
If a crossover cable is being used, make sure it is correctly wired.
Check the configuration of the hub or switch port to which the adapter card
is connected. Adjust that configuration and, if necessary, use NMMGR to
adjust the configuration of the link, so that something will match. If
necessary, specify a forced speed and duplex setting, and disable
autonegotiation, at both ends.
MESSAGE: Driver encountered a software problem.
Level: 6720 CLAS0001
CAUSE: During a 100Base-T connect sequence, the driver found the
link was not connected yet, but encountered an error while trying to get or
reset a timer ("Cause" = 32-bit status from the call to
lnk_timer_start). This timer was to be used to wait again for the
link connect to finish; the driver cannot connect the link if a PHY timer
cannot be started. If this error is reported, it is because the driver
has already encountered some other error.
ACTION: Typically preceded by another error message giving
better information about the original cause; check log data for
that error and look it up also. The driver did not dump, but will
still attempt to auto-reset itself, up to a total of 12 times or
more. If the problem persists, the system may be low on timers;
try stopping some applications before retrying again.
MESSAGE: Hub did not report link up within time allowed.
Level: 6750 CLAS0001
CAUSE: If this error occurs, it is because the link did
not connect within 25 to 30 seconds after it was instructed to do so.
ACTION: Verify that the cable is securely connected to the adapter
card at one end, and to a 100Base-TX or 10Base-T hub at the other.
Verify the cable is a correctly wired, Category-5 UTP cable. Category 3 or
4 cables are not acceptable.
If a crossover cable is being used, make sure it is correctly wired.
Check the configuration of the hub or switch port to which the adapter card
is connected. Adjust that configuration and, if necessary, use NMMGR to
adjust the configuration of the link, so that something will match. If
necessary, specify a forced speed and duplex setting, and disable
autonegotiation, at both ends.
MESSAGE: Timeout while awaiting link autonegotiation completion.
Level: 6780 CLAS0001
CAUSE: The link appears to be connected, but the driver
thinks it is still waiting for it to connect.
ACTION: This error should not occur. If it happens frequently,
see Appendix A "Submitting a CR" or contact your
Hewlett-Packard representative.
MESSAGE: Driver encountered a hardware problem.
Level: 6810 CLAS0001
CAUSE: While the ISR was attempting perform autonegotiation,
a read of the PHY's BMSR register failed.
ACTION: The driver may have become unusable and may try
to auto-reset. If necessary, stop and restart the link manually.
If the problem persists, the PHY chip may have gone bad; try replacing
the PCI 100Base-T adapter card.
MESSAGE: Driver encountered a hardware problem.
Level: 6840 CLAS0001
CAUSE: While the ISR was attempting perform autonegotiation,
a read of the PHY's ANAR register failed.
ACTION: The driver may have become unusable and may try
to auto-reset. If necessary, stop and restart the link manually.
If the problem persists, the PHY chip may have gone bad; try replacing
the PCI 100Base-T adapter card.
MESSAGE: Driver encountered a hardware problem.
Level: 6870 CLAS0001
CAUSE: While the ISR was attempting perform autonegotiation,
a read of the PHY's ANLPAR register failed.
ACTION: The driver may have become unusable and may try
to auto-reset. If necessary, stop and restart the link manually.
If the problem persists, the PHY chip may have gone bad; try replacing
the PCI 100Base-T adapter card.
MESSAGE: Driver encountered a hardware problem.
Level: 6900 CLAS0001
CAUSE: While the ISR was attempting perform autonegotiation,
a read of the PHY's ANER register failed.
ACTION: The driver may have become unusable and may try
to auto-reset. If necessary, stop and restart the link manually.
If the problem persists, the PHY chip may have gone bad; try replacing
the PCI 100Base-T adapter card.
MESSAGE: Driver encountered a hardware problem.
Level: 6930 CLAS0001
CAUSE: While the ISR was attempting perform autonegotiation
and detect the link speed, a read of the PHY's PAR register failed.
ACTION: The driver may have become unusable and may try
to auto-reset. If necessary, stop and restart the link manually.
If the problem persists, the PHY chip may have gone bad; try replacing
the PCI 100Base-T adapter card.
MESSAGE: Driver encountered a hardware problem.
Level: 6940 CLAS0001
CAUSE: While attempting to update the speed/duplex settings on the
PHY, the ISR first tried to stop the transmit processing on the adapter
card, but received an error. ("Cause" = 32-bit status from
pbt_isr_stop_tx). Additional errors may have been logged with more
information about the failure.
ACTION: The driver may become unusable or attempt an auto-reset.
If the driver appears to hang, try to shutdown the network manually and
then restart it. Most likely, once the reset is complete and the driver has
"reinitialized" the hardware (card), the driver can resume operating
normally.
If the problem persists, it may indicate a bad adapter card;
try replacing the card.
MESSAGE: Driver encountered a hardware problem.
Level: 6950 CLAS0001
CAUSE: While attempting to update the speed/duplex settings on the
PHY, the ISR first tried to stop the receive processing on the adapter card,
but received an error. ("Cause" = 32-bit status from
pbt_isr_stop_rx). Additional errors may have been logged with more
information about the failure.
ACTION: The driver may become unusable or attempt an auto-reset.
If the driver appears to hang, try to shutdown the network manually
and then restart it. Most likely, once the reset is complete and
the driver has "reinitialized" the hardware (card),
the driver can resume operating normally.
If the problem persists, it may indicate a bad adapter card; try
replacing the card.
MESSAGE: Driver encountered a software problem.
Level: 6960 CLAS0001
CAUSE: While attempting to process a link connection failure and
reconnect the link, an extraneous input message was received in the PHY
state machine (pbt_do_phy_state_connfail). The ISR attempted to
stop the PHY timer (a system timer) when the event occurred, but received
an error ("Cause" = 32-bit status from lnk_timer_stop).
ACTION: This is an informational message; the driver will attempt
to recover from this error and continue processing. If it can't, the driver
may try an auto-reset. If the link appears to hang or become unusable, try
shutting down and restarting the network link manually.
If the problem persists, note the conditions under which it occurs, whether
the system is under heavy load, etc. Collect all available information from
the log file(s); see Appendix A "Submitting a CR"
Repeated, regular occurrences of the problem may indicate a problem in the
system software; a system dump file may be needed.
MESSAGE: Driver encountered a hardware problem.
Level: 6990 CLAS0001
CAUSE: While the ISR was attempting perform a link connect
operation, an unexpected event/message was detected in the PHY state
machine. The driver attempted to check the status of the PHY by reading one
of its status registers but the read operation failed.
ACTION: The driver may have become unusable and may try
to auto-reset. If necessary, stop and restart the link manually.
If the problem persists, the PHY chip may have gone bad; try replacing
the PCI 100Base-T adapter card.
MESSAGE: Driver encountered a software problem.
Level: 7020 CLAS0001
CAUSE: While beginning a 100Base-T connect sequence, the driver
started to reset the PHY chip, but encountered an error while trying to get
or reset a timer ("Cause" = 32-bit status from the call to
lnk_timer_start). This timer was to be used to wait for the PHY
reset to finish; the driver cannot connect the link if a PHY timer cannot
be started. If this error is reported, it is because the driver
has already encountered some other error.
ACTION: Typically preceded by another error message giving
better information about the original cause; check log data for
that error and look it up also. The driver did not dump, but will
still attempt to auto-reset itself, up to a total of 12 times or
more.If the problem persists, the system may be low on timers; try
stopping some applications before retrying again.
MESSAGE: Driver encountered a hardware problem.
Level: 7050 CLAS0001
CAUSE: While beginning a 100Base-T connect sequence,
the driver attempted to read data from one of the PHY registers,
but the read operation failed.
ACTION: This is an informational error; it is possible the read
failed because the PHY chip had not completed its reset sequence. The
driver will attempt to continue processing and try the connect sequence
again later. If successive attempts at connecting are unsuccessful, the
link will not start up.
If this particular problem persists and the driver can not
read data successfully from the PHY, it may indicate the PHY chip
is bad; try replacing the adapter card.
MESSAGE: Driver encountered a software problem.
Level: 7080 CLAS0001
CAUSE: During a 100Base-T connect sequence, the driver found the
PHY chip was not reset yet, and started to reset it again, but encountered
an error while trying to get or reset a timer ("Cause" = 32-bit status
from the call to lnk_timer_start). This timer was to be used to
wait again for the PHY reset to finish; the driver cannot connect the link
if a PHY timer cannot be started. If this error is reported, it is because
the driver has already encountered some other error.
ACTION: Typically preceded by another error message giving
better information about the original cause; check log data for
that error and look it up also. The driver did not dump, but will
still attempt to auto-reset itself, up to a total of 12 times or
more. If the problem persists, the system may be low on timers;
try stopping some applications before retrying again.
MESSAGE: Adapter card PHY did not finish reset in the time allowed.
Level: 7110 CLAS0001
CAUSE: During a 10Base-T connect sequence on a PCI 100Base-T
adapter card, the driver tried 3 times to reset the PHY chip, but it still
did not go "ready" ("Cause" is not used here).
ACTION: This is a fatal hardware error. The adapter card
may be bad, and may need replacing.
The driver cannot connect the link if the PHY will not reset. The driver
will enter a "broken" state and await a manual shutdown by the operator.
If you wish you may try running the VGPBA diagnostic and attempt a reset,
however it is unlikely this will fix the problem. If the problem persists
with a known-good card, see
Appendix A "Submitting a CR"
MESSAGE: Driver encountered a software problem.
Level: 7140 CLAS0001
CAUSE: During a 100Base-T connect sequence, the driver attempted
to power up the PHY, but encountered an error while trying to get or reset
a timer ("Cause" = 32-bit status from the call to lnk_timer_start).
This timer was to be used to wait again for the PHY power up to finish;
the driver cannot connect the link if a PHY timer cannot be started. If
this error is reported, it is because
the driver has already encountered some other error.
ACTION: Typically preceded by another error message giving
better information about the original cause; check log data for
that error and look it up also. The driver did not dump, but will
still attempt to auto-reset itself, up to a total of 12 times or
more. If the problem persists, the system may be low on timers;
try stopping some applications before retrying again.
MESSAGE: Driver encountered a hardware problem.
Level: 7170 CLAS0001
CAUSE: During a 100Base-T connect sequence, after resetting the
PHY chip, the driver encountered an error while trying to read the PHY ID
("Cause" = 32-bit status from the call to pbt_isr_init_phy_id).
If this error is reported, it is because the driver
has already encountered some other error.
ACTION: Typically preceded by another error message giving
better information about the original cause; check log data for
that error and look it up also. The driver did not dump, but will
still attempt to auto-reset itself, up to a total of 12 times or
more. Most likely there is an adapter card hardware problem; the
card may need to be replaced.
MESSAGE: Driver encountered a software problem.
Level: 7200 CLAS0001
CAUSE: During a 100Base-T connect sequence, the driver attempted
to set a "watchdog" timer to wait for the PHY to complete bringing the link
up, but encountered an error while trying to get or reset a timer ("Cause"
= 32-bit status from the call to lnk_timer_start). The driver
cannot connect the link if a PHY timer cannot be started. If this error is
reported, it is because the driver has already encountered some other error.
ACTION: Typically preceded by another error message giving
better information about the original cause; check log data for
that error and look it up also. The driver did not dump, but will
still attempt to auto-reset itself, up to a total of 12 times or
more. If the problem persists, the system may be low on timers;
try stopping some applications before retrying again.
MESSAGE: Driver encountered a hardware problem.
Level: 7230 CLAS0001
CAUSE: During a 100Base-T connect sequence, the driver
attempted to check for presence of a link signal, but encountered
an error trying to read from the generic status register on the
PHY chip ("Cause" = 32-bit status from the call to pbt_mii_read16).
ACTION: If an interruption in power has occurred, this
error can be ignored; the driver should recover automatically. Otherwise,
the MII bus may have failed; replace the adapter card. If the same
problem persists, see
Appendix A "Submitting a CR"
MESSAGE: Driver encountered a hardware problem.
Level: 7260 CLAS0001
CAUSE: During a 100Base-T connect sequence, the driver
attempted to check for presence of a link signal, but encountered
an error trying to read from the generic status register on the PHY chip
("Cause" = 32-bit status from the call to pbt_mii_read16).
ACTION: If an interruption in power has occurred, this
error can be ignored; the driver should recover automatically. Otherwise,
the MII bus may have failed; replace the adapter card. If the same
problem persists, see
Appendix A "Submitting a CR"
MESSAGE: Autonegotiation reports link settings are incompatible with hub.
Level: 7290 CLAS0001
CAUSE: If this error occurs, it is probably because the
link has reported a remote fault. Usually this means the adapter
card and the hub or switch to which it is connected, have failed
to agree on a link speed and duplex setting acceptable to both.
ACTION: Verify that the cable is securely connected to the adapter
card at one end, and to a 100Base-TX or 10Base-T hub at the other.
Verify the cable is a correctly wired, Category-5 UTP cable. Category 3 or
4 cables are not acceptable.
If a crossover cable is being used, make sure it is correctly wired.
Check the configuration of the hub or switch port to which the adapter card
is connected. Adjust that configuration and, if necessary, use NMMGR to
adjust the configuration of the link, so that something will match. If
necessary, specify a forced speed and duplex setting, and disable
autonegotiation, at both ends.
MESSAGE: Driver encountered a software problem.
Level: 7320 CLAS0001
CAUSE: During a 100Base-T connect sequence, the driver found the
link was not connected yet, but encountered an error while trying to get or
reset a timer ("Cause" = 32-bit status from the call to
lnk_timer_start). This timer was to be used to wait again for the
link connect to finish; the driver cannot connect the link if a PHY timer
cannot be started. If this error is reported, it is because the driver
has already encountered some other error.
ACTION: Typically preceded by another error message giving
better information about the original cause; check log data for
that error and look it up also. The driver did not dump, but will
still attempt to auto-reset itself, up to a total of 12 times or
more. If the problem persists, the system may be low on timers;
try stopping some applications before retrying again.
MESSAGE: Hub did not report link up within time allowed.
Level: 7350 CLAS0001
CAUSE: If this error occurs, it is because the link did
not connect within 25 to 30 seconds after it was instructed to do so.
ACTION: Verify that the cable is securely connected to the adapter
card at one end, and to a 100Base-TX or 10Base-T hub at the other.
Verify the cable is a correctly wired, Category-5 UTP cable. Category 3 or
4 cables are not acceptable.
If a crossover cable is being used, make sure it is correctly wired, and
that you have software version A00550B0 or later.
Check the configuration of the hub or switch port to which the adapter card
is connected. Adjust that configuration and, if necessary, use NMMGR to
adjust the configuration of the link, so that something will match. If
necessary, specify a forced speed and duplex setting, and disable
autonegotiation, at both ends.
MESSAGE: Timeout while awaiting link autonegotiation completion.
Level: 7380 CLAS0001
CAUSE: The link appears to be connected, but the driver
thinks it is still waiting for it to connect.
ACTION: This error should not occur. If it happens frequently,
see Appendix A "Submitting a CR"
MESSAGE: Driver encountered a hardware problem.
Level: 7410 CLAS0001
CAUSE: While the ISR was attempting perform autonegotiation,
a read of the PHY's BMSR register failed.
ACTION: The driver may have become unusable and may try
to auto-reset. If necessary, stop and restart the link manually.
If the problem persists, the PHY chip may have gone bad; try replacing
the PCI 100Base-T adapter card.
MESSAGE: Driver encountered a hardware problem.
Level: 7440 CLAS0001
CAUSE: While the ISR was attempting perform autonegotiation,
a read of the PHY's ANAR register failed.
ACTION: The driver may have become unusable and may try
to auto-reset. If necessary, stop and restart the link manually.
If the problem persists, the PHY chip may have gone bad; try replacing
the PCI 100Base-T adapter card.
MESSAGE: Driver encountered a hardware problem.
Level: 7470 CLAS0001
CAUSE: While the ISR was attempting perform autonegotiation,
a read of the PHY's ANLPAR register failed.
ACTION: The driver may have become unusable and may try
to auto-reset. If necessary, stop and restart the link manually.
If the problem persists, the PHY chip may have gone bad; try replacing
the PCI 100Base-T adapter card.
MESSAGE: Driver encountered a hardware problem.
Level: 7500 CLAS0001
CAUSE: While the ISR was attempting perform autonegotiation,
a read of the PHY's ANER register failed.
ACTION: The driver may have become unusable and may try
to auto-reset. If necessary, stop and restart the link manually.
If the problem persists, the PHY chip may have gone bad; try replacing
the PCI 100Base-T adapter card.
MESSAGE: Driver encountered a hardware problem.
Level: 7530 CLAS0001
CAUSE: While the ISR was attempting bring up the link
and detect the speed and duplex settings for the link, a read of
the PHY's general status register failed.
ACTION: The driver may have become unusable and may try
to auto-reset. If necessary, stop and restart the link manually.
If the problem persists, the PHY chip may have gone bad; try replacing
the PCI 100Base-T adapter card.
MESSAGE: Driver encountered a software error.
Level: 7560 CLAS0001
CAUSE: During the 100Base-T link connect sequence, the driver
attempted to stop a system timer that was used to coordinate communication
with the PHY chip, but an error was detected ("Cause" = 32-bit status from
lnk_timer_stop). There could be an internal software error or
corruption of data structures.
ACTION: This is an informational message; the driver may attempt
an auto-reset in response to the error. If the problem persists, it may
indicate a problem with the system software or data structures. If possible,
halt the system and generate a dump as soon as possible after the error is
observed; see
Appendix A "Submitting a CR"
MESSAGE: Driver encountered a hardware problem.
Level: 7590 CLAS0001
CAUSE: While the ISR was attempting to check the status
of the link, a read of the PHY's general status register failed.
ACTION: The driver may have become unusable and may try
to auto-reset. If necessary, stop and restart the link manually.
If the problem persists, the PHY chip may have gone bad; try replacing
the PCI 100Base-T adapter card.
MESSAGE: Unimplemented operation attempted.
Level: 7610 CLAS0001
CAUSE: While attempting to enable a loopback mode at
the request of a diagnostic tool, the driver detected that the specified
mode of looback support is not available on the PHY.
ACTION: Not all PHY chips support all loopback modes;
make sure that the proper diagnostic request was issued, and that
the driver supports the operation requested. Also make sure that the
adapter card is the correct type and model number, with a revision level
that is supported by the driver software. Contact your Hewlett-Packard
representative if you need assistance.
MESSAGE: Driver encountered a hardware problem.
Level: 7620 CLAS0001
CAUSE: While attempting to set loopback mode on the PHY, the ISR
first tried to stop the transmit processing on the adapter card, but
received an error. ("Cause" = 32-bit status from pbt_isr_stop_tx).
Additional errors may have been logged with more information
about the failure.
ACTION: The driver may become unusable or attempt an auto-reset.
If the driver appears to hang, try to shutdown the network manually
and then restart it. Most likely, once the reset is complete and
the driver has "reinitialized" the hardware (card),
the driver can resume operating normally.
If the problem persists, it may indicate a bad adapter card;
try replacing the card.
MESSAGE: Driver encountered a hardware problem.
Level: 7650 CLAS0001
CAUSE: While attempting to set loopback mode on the PHY, the ISR
first tried to stop the receive processing on the adapter card, but
received an error. ("Cause" = 32-bit status from pbt_isr_stop_rx).
Additional errors may have been logged with more information
about the failure.
ACTION: The driver may become unusable or attempt an auto-reset.
If the driver appears to hang, try to shutdown the network manually
and then restart it. Most likely, once the reset is complete and
the driver has "reinitialized" the hardware (card),
the driver can resume operating normally.
If the problem persists, it may indicate a bad adapter card;
try replacing the card.
MESSAGE: Driver encountered a hardware problem.
Level: 7680 CLAS0001
CAUSE: While attempting to enable loopback mode, the
driver encountered an error while trying to read a register from
the PHY ("Cause" = 32-bit status from pbt_mii_read16).
ACTION: The driver may become unusable or attempt an auto-reset.
If the driver appears to hang, shut down the network manually and
then restart it. Most likely, once the reset is complete and the
driver has "reinitalized" the hardware (card),
the driver can resume operating normally.
If the problem persists, it may indicate a bad adapter card;
try replacing the card.
MESSAGE: Driver encountered a hardware problem.
Level: 7710 CLAS0001
CAUSE: While attempting to enable loopback mode, the
driver encountered an error while trying to read a register from
the PHY ("Cause" = 32-bit status from pbt_mii_read16).
ACTION: The driver may become unusable or attempt an auto-reset.
If the driver appears to hang, shut down the network manually and
then restart it. Most likely, once the reset is complete and the
driver has "reinitalized" the hardware (card),
the driver can resume operating normally.
If the problem persists, it may indicate a bad adapter card;
try replacing the card.
MESSAGE: Driver encountered a hardware problem.
Level: 7740 CLAS0001
CAUSE: While attempting to enable loopback mode, the
driver encountered an error while trying to read a register from
the PHY ("Cause" = 32-bit status from pbt_mii_read16).
ACTION: The driver may become unusable or attempt an auto-reset.
If the driver appears to hang, shut down the network manually and
then restart it. Most likely, once the reset is complete and the
driver has "reinitalized" the hardware (card),
the driver can resume operating normally.
If the problem persists, it may indicate a bad adapter card;
try replacing the card.
MESSAGE: Driver encountered a hardware problem.
Level: 7770 CLAS0001
CAUSE: While attempting to enable loopback mode, the
driver encountered an error while trying to read a register from
the PHY ("Cause" = 32-bit status from pbt_mii_read16).
ACTION: The driver may become unusable or attempt an auto-reset.
If the driver appears to hang, shut down the network manually and
then restart it. Most likely, once the reset is complete and the
driver has "reinitalized" the hardware (card),
the driver can resume operating normally.
If the problem persists, it may indicate a bad adapter card;
try replacing the card.
MESSAGE: Driver encountered a software problem.
Level: 7820 CLAS0001
CAUSE: After attempting to connect the link, the driver's
ISR module determined the link did come up, then encountered an
error trying to notify the DVR module of the connect ("Cause" =
32-bit status from the call to pbt_isr_copy_send_to_dvr).
Probably no comm frame was available.
ACTION: This informational error should be preceded by
another error giving a more specific reason for the failure; check
log data and look up that error also, for more actions to take.
Most likely the previous error was fatal and the driver is about
to "die", then will either attempt an auto- reset
or else require a manual shutdown and restart. The driver stopped
trying to connect the link.
MESSAGE: (Varies)
Level: 7830 CLAS0001
CAUSE: This is a generic logging location which reports the driver
is having trouble connecting the link. The message varies depending on what
the problem is.
After trying repeatedly for 25-30 seconds to connect the link, the driver's
ISR module determined the link did not come up ("Cause" = 32-bit status
from giving the reason the latest attempt failed, also explained
in the Message).
ACTION: This is a warning only. It only appears once,
and will not appear again until the link is shut down and restarted.
This informational error should be accompanied by a message specific to the
problem. For some reason, the link is not connecting successfully.
Verify that the cable is securely connected to the adapter card at one end,
and to a 100Base-TX or 10Base-T hub at the other.
Verify the cable is a correctly wired, Category-5 UTP cable. Category 3 or
4 cables are not acceptable.
If a crossover cable is being used, make sure it is correctly wired.
Check the configuration of the hub or switch port to which the adapter card
is connected. Adjust that configuration and, if necessary, use NMMGR to
adjust the configuration of the link, so that something will match. If
necessary, specify a forced speed and duplex setting, and disable
autonegotiation, at both ends.
MESSAGE: Driver encountered a software problem.
Level: 7860 CLAS0001
CAUSE: While attempting to logically disconnect the link, the
driver encountered a problem ("Cause" = 32-bit status from the call to
pbt_isr_call_phy_state_machine). Probably a power failure or
system timer problem has occurred.
ACTION: This informational error should be preceded by
another error giving a more specific reason for the failure; check
log data and look up that error also, for more actions to take.
If a power failure has occurred, this error may be ignored; the
driver will soon attempt to recover. Otherwise, most likely the
previous error was fatal and the driver is about to "die",
then will either attempt an auto-reset or else require a manual
shutdown and restart.
MESSAGE: Driver encountered a software problem.
Level: 7890 CLAS0001
CAUSE: While attempting to logically disconnect the link, the
driver encountered a problem ("Cause" = 32-bit status from the call to
Pbt_isr_call_phy_state_machine). Probably a power failure or
system timer problem has occurred.
ACTION: This informational error should be preceded by
another error giving a more specific reason for the failure; check
log data and look up that error also, for more actions to take.
If a power failure has occurred, this error may be ignored; the
driver will soon attempt to recover. Otherwise, most likely the
previous error was fatal and the driver is about to "die",
then will either attempt an auto-reset or else require a manual
shutdown and restart.
MESSAGE: Driver encountered a software problem.
Level: 7920 CLAS0001
CAUSE: While processing a disconnect request, the ISR
detected that upper level subsystem(s) were still rendezvoused to
the driver. It tried to set a "wake up" PHY timer
to try to reconnect the link once the timer popped, but it was unable
to allocate a system timer ("Cause" = 32-bit status
from lnk_timer_start).
ACTION: This is an information message; the driver can
not reconnect the link without successfully setting the PHY timer.
The link may need to be manually shut down and restarted; if the
problem persists, there could be a shortage of system timers. Try
the operation again when fewer applications are running.
MESSAGE: Heartbeat timeout. Adapter card appears to be hung.
Level: 7950 CLAS0001
CAUSE: The LAN controller chip on the adapter card has
failed to produce any interrupt from normal activity for over 5
seconds. It has also failed, for an additional 5 seconds, to respond
to the driver's inquiry by producing a test interrupt.
The driver has decided the card is dead or hung ("Cause" is not used here).
ACTION: This is a fatal hardware error. Replace the adapter card.
The driver will enter a "broken" state and await a manual shutdown by the
operator. If you wish you may try running the VGPBA diagnostic and attempt
a reset. If the problem persists with a known good card, see
Appendix A "Submitting a CR"
MESSAGE: Driver encountered a software problem.
Level: 7980 CLAS0001
CAUSE: The driver was in the middle of a periodic check of whether
the card is still healthy, but encountered an error while trying to get or
reset a timer ("Cause" = 32-bit status from the call to
lnk_timer_start). This same timer has been used repeatedly to
reawaken the driver so it can check the card, so occurrence of this error
probably indicates a larger system problem or corruption of data structures.
If this error is reported, it is because the driver has already encountered
some other error.
ACTION: Typically preceded by another error message giving
better information about the original cause; check log data for
that error and look it up also. The driver did not dump, but will
still attempt to auto- reset itself, up to a total of 12 times or
more. If the problem persists, the system may be low on timers;
try stopping some applications before retrying again.
MESSAGE: Driver encountered a hardware problem.
Level: 8010 CLAS0001
CAUSE: The driver was in the middle of a periodic check
of whether the card is still healthy, but encountered an error trying
to read from the generic status register on the PHY chip ("Cause" =
32-bit status from the call to pbt_mii_read16). Most likely a
hardware problem has occurred, not a power failure.
ACTION: The MII bus may have failed; replace the adapter card.
If the same problem persists, see Appendix A
"Submitting a CR" If a power failure has actually occurred, this
error can be ignored;
the driver should recover automatically.
MESSAGE: Driver encountered a software problem.
Level: 8040 CLAS0001
CAUSE: While attempting to de-select a PHY chip during
diagnostic loopback testing of the adapter card, the driver encountered
some kind of lower- level error ("Cause" = 32-bit
status from the call to pbt_isr_set_loopback_mode).
ACTION: This informational error is typically preceded
by another error message giving better information about the original
cause; check log data for that error and look it up also. Depending
on the cause of that error, you may decide that replacement of the
adapter card is necessary.
Since diagnostic testing is in progress, the driver should
report the error, then attempt to continue. However, later tests
may also fail as a result of this error.
MESSAGE: Driver encountered a software problem.
Level: 8070 CLAS0001
CAUSE: During a link connect attempt, the driver received
an interrupt from the PHY chip on the adapter card and passed that
to a lower level, but the lower level returned an error ("Cause" =
32-bit status from the call to pbt_isr_call_phy_state_machine).
ACTION: This informational error is typically preceded
by another error message giving better information about the original
cause; check log data for that error and look it up also. At this
level, the error is just logged, then the driver will attempt to
continue, if the lower level error was not already fatal.
MESSAGE: Driver encountered a software problem.
Level: 8100 CLAS0001
CAUSE: During a link connect attempt, the driver received
an interrupt from the PHY chip on the adapter card and passed that
to a lower level, but the lower level returned an error ("Cause" =
32-bit status from the call to pbt_isr_call_phy_state_machine).
ACTION: This informational error is typically preceded
by another error message giving better information about the original
cause; check log data for that error and look it up also. At this
level, the error is just logged, then the driver will attempt to
continue, if the lower level error was not already fatal.
MESSAGE: Driver encountered a hardware problem.
Level: 8300 CLAS0001
CAUSE: While attempting to process a restart request, the ISR
first tried to stop the transmit processing on the adapter card, but
received an error. ("Cause" = 32-bit status from pbt_isr_stop_tx).
Additional errors may have been logged with more information
about the failure.
ACTION: The driver may become unusable or attempt an auto-reset.
If the driver appears to hang, try to shutdown the network manually
and then restart it. Most likely, once the reset is complete and
the driver has "reinitialized" the hardware (card),
the driver can resume operating normally.
If the problem persists, it may indicate a bad adapter card;
try replacing the card.
MESSAGE: Driver encountered a hardware problem.
Level: 8330 CLAS0001
CAUSE: While attempting to process a restart request,
the ISR first tried to stop the receive processing on the adapter
card, but received an error. ("Cause" = 32-bit status from
pbt_isr_stop_rx). Additional errors may have been logged with
more information about the failure.
ACTION: The driver may not be able to complete the restart.
If the driver appears to hang, try to shut down the network manually
and then restart it. Most likely, once the reset is complete and
the driver has "reinitialized" the hardware (card),
the driver can resume operating normally.
If the problem persists, it may indicate a bad adapter card;
try replacing the card.
MESSAGE: Driver encountered a software problem.
Level: 8360 CLAS0001
CAUSE: While processing a restart request, the ISR attempted
to stop the previously enabled heartbeat timer, but was returned
an error ("Cause" = 32-bit status from lnk_timer_stop).
ACTION: The restart can not be completed if the driver
can not successfully reinitialize the heartbeat timer. The driver
may do an MESSAGE: auto-reset. If the driver appears to hang, try
a manual shutdown and restart of the network link.
If the problem persists, it could indicate a system software
error or possible data corruption of system data structures. In
that case, try to halt the system and generate a dump as soon as
possible after the problem is detected; see
Appendix A "Submitting a CR"
MESSAGE: Driver encountered a software problem.
Level: 8540 CLAS0001
CAUSE: After completing a start or restart operation,
the driver's ISR then encountered an error trying to notify
the DVR module of the restart completion ("Cause" =
32-bit status from the call to Pbt_isr_copy_send_to_dvr).
Probably no comm frame was available.
ACTION: This informational error should be preceded by
another error giving a more specific reason for the failure; check
log data and look up that error also, for more actions to take.
Most likely the previous error was fatal and the driver is about
to "die", then will either attempt an auto-reset
or else require a manual shutdown and restart.
MESSAGE: Bad message for current state.
Level: 8570 CLAS0001
CAUSE: The driver received a new bind (rendezvous) from
an upper layer protocol, at a time when the driver was not able
to process these requests, such as before receiving its initial
configuration data, during shutdown, or after a fatal software error
("Cause" = 16-bit encoded value, giving driver
input event code and current state: Hewlett-Packard use only).
ACTION: This problem most likely occurred while starting
a new network subsystem. Attempt to determine which subsystem was
being started when the error occurred and, if possible, which upper
layer protocol was binding. The bind failed. The driver logged the
error, then attempted to send an error reply message back to the
protocol module and continue.
Check the system console; if the driver is shutting down or doing a dump,
wait until that completes. In these cases, several protocols may experience
this same error. If the driver is not shutting down or dying, the protocol
may be sending binds to the driver at the wrong time. See
Appendix A "Submitting a CR" and file an CR against
the network subsystem being started.
MESSAGE: One or more bad bind parms passed by upper level protocol.
Level: 8600 CLAS0001
CAUSE: The driver received a bind (rendezvous) from an
upper layer protocol module, but the specified SDI address family
was not one of the values supported by the driver ("Cause" =
32-bit value giving the bad address family which was specified).
ACTION: This problem most likely occurred while starting
a new network subsystem. Attempt to determine which subsystem was
being started when the error occurred and, if possible, which upper
layer protocol was binding. The bind failed. The driver logged the
error, then attempted to send an error reply message back to the
protocol module and continue.
Either there is a bug in the driver or upper layer protocol software, or
there is a system software mismatch. You may require additional software
patches; contact your Hewlett-Packard Representative
for assistance.
MESSAGE: Link common reported a protocol bind problem.
Level: 8630 CLAS0001
CAUSE: While attempting to setup a rendezvous entry (by
calling lnk_rendez), an error was returned to the ISR. ("Cause" =
32-bit integer specifying the SAP that was trying to rendezvous).
ACTION: This problem most likely occurred while starting
a new network subsystem. Attempt to determine which subsystem was
being started when the error occurred and, if possible, which upper
layer protocol was binding. The bind failed. The driver logged the
error, then attempted to send an error reply message back to the
protocol module and continue.
Either there is a bug in the driver or upper layer protocol software, or
there is a system software mismatch. You may require additional software
patches; contact your Hewlett-Packard Representative
for assistance.
MESSAGE: Link common reported an inbound buffering problem.
Level: 8660 CLAS0001
CAUSE: While attempting to complete a rendezvous request, the ISR
received an error from link common (lnk_buf_init) when attempting
to set up inbound buffering for the SAP. ("Cause" = 32-bit integer
specifying the SAP that was trying to rendezvous).
ACTION: This problem most likely occurred while starting
a new network subsystem. Attempt to determine which subsystem was
being started when the error occurred and, if possible, which upper
layer protocol was binding. The bind failed. The driver logged the
error, then attempted to send an error reply message back to the
protocol module and continue.
Either there is a bug in the driver or upper layer protocol software, or
there is a system software mismatch. You may require additional software
patches; contact your Hewlett-Packard Representative
for assistance.
MESSAGE: Subsystem is binding to link driver.
Level: 8690 CLAS0003
CAUSE: An upper-layer protocol has successfully bound
(rendezvoused) to the link driver ("Addr" = 32-bit encoded protocol address
(SAP) value for this protocol module). Being bound means the driver can now
route incoming data frames to this protocol.
ACTION: None. This is an informational message only. A
similar message is logged later, when the protocol unbinds. If this
is the first bind, the link driver will now attempt to reconnect
the link.
MESSAGE: Subsystem is unbinding from link driver.
Level: 8720 CLAS0003
CAUSE: An upper-layer protocol has begun to unbind (separate)
from the link driver ("Addr" = 32-bit encoded
protocol address (SAP) value for this protocol module). Once unbound,
the driver can no longer route incoming data frames to this protocol.
ACTION: None. This is an informational message only. A
similar message is logged earlier, when the protocol binds. If this
is the last bind, the link driver will now attempt to disconnect the link.
If any errors occur as a result of the unbind, they will appear
after, not before, this log event; the unbind will still complete,
and the protocol will be successfully unbound.
MESSAGE: Driver encountered a software problem.
Level: 8750 CLAS0001
CAUSE: While processing a trace enable request, the driver's
ISR then encountered an error trying to notify the DVR module of
the request completion ("Cause" = 32-bit status
from the call to Pbt_isr_copy_send_to_dvr).
Probably no comm frame was available.
ACTION: This informational error should be preceded by
another error giving a more specific reason for the failure; check
log data and look up that error also, for more actions to take.
Most likely the previous error was fatal and the driver is about
to "die", then will either attempt an auto-reset
or else require a manual shutdown and restart.
MESSAGE: Driver encountered a software problem.
Level: 8780 CLAS0001
CAUSE: While processing a trace disable request, the
driver's ISR then encountered an error trying to notify
the DVR module of the request completion ("Cause" =
32-bit status from the call to Pbt_isr_copy_send_to_dvr).
Probably no comm frame was available.
ACTION: This informational error should be preceded by
another error giving a more specific reason for the failure; check
log data and look up that error also, for more actions to take.
Most likely the previous error was fatal and the driver is about
to "die", then will either attempt an auto-reset
or else require a manual shutdown and restart.
MESSAGE: Driver received an unknown port message.
Level: 8810 CLAS0001
CAUSE: The driver received a port message which it does not
implement, or containing a function code which it does not implement
("Cause" = 32-bit ISR state machine input event tag value (Hewlett-Packard
use only).
ACTION: This is an informational error only. If this error
occurred as part of a driver reset operation, it may be ignored.
The driver traced the unknown message then ignored it. The driver did not
attempt to return an error reply to the message sender. That sender may now
be hung, awaiting a reply. Attempt to determine what action caused the
error. Activate link tracing, reproduce the problem, then stop link tracing
and save the resulting NMTCnnnn.PUB.SYS trace data file. See
Appendix A "Submitting a CR"
MESSAGE: Bad message for current state.
Level: 8840 CLAS0001
CAUSE: The driver received a utility register access
request from an upper level tool program such as LNKUTIL, at a time
when the driver was not able to process these requests, such as
before initializing the adapter card, during shutdown, or after
a fatal software error ("Cause" = 16-bit
encoded value, giving driver input event code and current state:
Hewlett-Packard use only).
ACTION: This problem most likely occurred while diagnosing
some previous problem. It will not be possible to complete these
requests at this time. The driver logged the error, then attempted
to send an error reply message back to the sender and continue.
Check the system console; if the driver is shutting down or
doing a dump, wait until that completes. If this happens regardless
of when the operation is attempted, see
Appendix A "Submitting a CR"
MESSAGE: One or more bad utility parms passed to driver.
Level: 8870 CLAS0001
CAUSE: The driver received a utility register access
request from an upper level tool program such as LNKUTIL, but the
register number specified was out of the range of legal register
values for the selected register set ("Cause" =
32-bit value of the selected register-set number, not register number:
Hewlett-Packard use only).
ACTION: This is an informational error only. Retry the
operation using a legal register number for the register set you
have selected.
This problem most likely occurred while diagnosing some previous problem.
The driver logged the error, then attempted to send an error reply
message back to the sender and continue.
MESSAGE: Unable to read from adapter card PCI configuration space.
Level: 8900 CLAS0001
CAUSE: While processing a request from an upper level
tool program such as LNKUTIL, the ISR encountered an error when
trying to read a register (data field) from the adapter card's
PCI configuration space. ("Cause" = 32-bit
status returned from io_pci-cfg_read_bit32).
ACTION: The adapter card may have been removed, moved to a
different slot, may not be making proper contact with the PCI backplane,
or may not be responding. If the I/O slot has a power indicator, verify it
is on. Reseat the board, and if necessary call your Hewlett-Packard
representative for hardware assistance. If the problem persists,
the adapter card may be bad; try replacing the card.
MESSAGE: Unable to write to adapter card PCI configuration space.
Level: 8930 CLAS0001
CAUSE: While processing a request from an upper level
tool program such as LNKUTIL, the ISR encountered an error when
trying to write to a register (data field) in the adapter card's
PCI configuration space. ("Cause = 32-bit status returned
from io_pci-cfg_write_bit32).
ACTION: The adapter card may have been removed, moved to a
different slot, may not be making proper contact with the PCI backplane,
or may not be responding. If the I/O slot has a power indicator, verify it
is on. Reseat the board, and if necessary call your Hewlett-Packard
representative for hardware assistance. If the problem persists,
the adapter card may be bad; try replacing the card.
MESSAGE: (Varies)
Level: 8960 CLAS0001
CAUSE: A general error occurred during processing of
an input event by the main driver ISR state machine, and the code
where the error occurred neglected to specify a sublocation code
value, so the value 8960 was used.
ACTION: Note all logged error messages. The main problem
is described by whatever was logged. But the driver also needs to
be fixed to specify a unique sublocation for those errors. Please
see Appendix A "Submitting a CR"
MESSAGE: Unimplemented operation attempted.
Level: 9020 CLAS0001
CAUSE: The main driver ISR state machine was passed an
input event for which there is no processing implemented. Either
there is a driver bug or some data corruption has occurred ("Cause" =
32-bit ordinal value of the input event code: Hewlett-Packard use only).
ACTION: Try to determine which operator or program actions led to
this error. Then see Appendix A "Submitting a CR"
After this problem occurs, the driver will enter a "broken" state where is
may not respond to further requests. If possible, run the VGPBA tool
program, and use it to force a driver dump, then forward the resulting
NETDMP##.PUB.SYS file to HP for analysis. After a dump, the driver
will attempt to auto-reset itself and continue. You may also use VGPBA to
attempt a manual reset of the driver, after which it may be
possible to continue.
MESSAGE: Internal driver error.
Level: 9390 CLAS0001
CAUSE: While processing a received frame, the ISR detected
an unsupported packet format. ("Cause" = 32-bit status returned from
Lnk_recv_strip_hdr). Because this should have been caught during
the rendezvous with the upper level system (SAP), this is an unexpected
error condition.
ACTION: This is an informational error only. The driver
incremented a statistic, logged the error, then attempted to free the read
buffer and continue. However, the protocol may not have received the
inbound frame, therefore some applications could be hung.
There may be a problem in the upper layer protocol. Also, if the protocol
had already freed the buffer, this may have resulted in a SysAbort from the
Buffer Manager. If the problem occurs frequently, start link tracing,
reproduce the problem, then stop link tracing and save the resulting
NMTC####.PUB.SYS file for analysis by HP, and see
Appendix A "Submitting a CR"
MESSAGE: Internal driver error.
Level: 9420 CLAS0001
CAUSE: While processing a received frame, the ISR encountered
an error when trying to swap buffers between the driver's
receive pool and the SAP's buffer pool. ("Cause" =
32-bit status from Bmgr_io_exchange_pb).
ACTION: This is an informational error only. The driver
incremented a statistic, logged the error, then attempted to free
the read buffer and continue. However, the protocol may not have
received the inbound frame, therefore some applications could be hung.
There may be a problem in the upper layer protocol. Also, if the protocol
had already freed the buffer, this may have resulted in a SysAbort from the
Buffer Manager. If the problem occurs frequently, start link tracing,
reproduce the problem, then stop link tracing and save the resulting
NMTC####.PUB.SYS file for analysis by HP, and see
Appendix A "Submitting a CR"
MESSAGE: Error from upper layer protocol read completor.
Level: 9450 CLAS0001
CAUSE: The driver finished transferring a data frame
and passed it to an upper layer protocol, but the protocol's
read completor returned an error which was not one of the expected,
legal errors the driver was able to handle ("Cause" =
32-bit status returned from the read completor).
ACTION: This is an informational error only. The driver
incremented a statistic, logged the error, then attempted to free
the read buffer and continue. However, the protocol may not have
received the inbound frame, therefore some applications could be hung.
There may be a problem in the upper layer protocol. Also, if the protocol
had already freed the buffer, this may have resulted in a SysAbort from the
Buffer Manager. If the problem occurs frequently, start link tracing,
reproduce the problem, then stop link tracing and save the resulting
NMTC####.PUB.SYS file for analysis by Hewlett-Packard, and see
Appendix A "Submitting a CR"
MESSAGE: Cannot send a port message.
Level: 9480 CLAS0001
CAUSE: The driver finished transferring a data frame,
but encountered an error while trying to send the frame to an upper
layer protocol via a port message ("Cause" = 32-bit
status returned by the call to send_msg).
ACTION: This error is reported at a low level, where the
actual send fails. It should be followed by a another error giving
more information. Locate that error and look it up also. The driver
will now attempt to clean up and continue.
MESSAGE: Error from upper layer protocol read completor.
Level: 9510 CLAS0001
CAUSE: The driver finished transferring a data frame
and passed it to an upper layer protocol, but the protocol's
read completor returned an error which was not one of the expected,
legal errors the driver was able to handle ("Cause" =
32-bit status returned from the read completor).
ACTION: This is an informational error only. The driver
incremented a statistic, logged the error, then attempted to free
the read buffer and continue. However, the protocol may not have
received the inbound frame, therefore some applications could be hung.
There may be a problem in the upper layer protocol. Also, if the protocol
had already freed the buffer, this may have resulted in a SysAbort from the
Buffer Manager. If the problem occurs frequently, start link tracing,
reproduce the problem, then stop link tracing and save the resulting
NMTC####.PUB.SYS file for analysis by Hewlett-Packard, and see
Appendix A "Submitting a CR"
MESSAGE: Link common reported an inbound buffering problem.
Level: 9540 CLAS0001
CAUSE: After completing a read and delivering a data
buffer to an upper layer protocol, the ISR encountered an error
when trying to refill the SAP's buffer cache. ("Cause" =
32-bit status from Lnk_buf_refill).
ACTION: This message is informational; this might be because of
contention on the system for buffers. However, if the underlying contention
or problem persists, the SAP may run out of buffers and no longer be able
to receive data over the network.
If upper level network subsystems appear hung, try shutting them down
manually, or shutting down and restarting the network link; if the problem
persists, see
Appendix A "Submitting a CR"
MESSAGE: Bad message for current state.
Level: 9570 CLAS0001
CAUSE: The driver finished transferring a diagnostic
loopback data frame, but then discovered it was either not in loopback
mode anymore, or there was no pending diagnostic request message
("Cause" = 32-bit encoded value, giving driver
current state: Hewlett-Packard use only).
ACTION: This problem most likely occurred while diagnosing
some previous problem. It an informational error only, and the driver
will log it and attempt to continue. If this happens frequently,
see Appendix A "Submitting a CR"
MESSAGE: General buffer manager error encountered.
Level: 9630 CLAS0001
CAUSE: While attempting to reset the receive descriptor ring data
structure, the ISR received an error from the buffer manager ("Cause" =
32-bit status from Pbt_bmgr_get_buffer).
ACTION: This error message is informational. If the receive
descriptor ring is being reset, the driver may be in the middle
of an auto-restart; the driver will likely try another restart.
If the problem persists, there might be data corruption in the driver or in
the buffer manager data structures. Try forcing a driver dump via the VGPBA
tool and send the dump file (NETDMP##.PUB.SYS) to
Hewlett-Packard for analysis; seem
Appendix A "Submitting a CR"
MESSAGE: Driver encountered a software problem.
Level: 9660 CLAS0001
CAUSE: While attempting to reset the receive descriptor ring data
structure and rebuild the receive descriptors, the ISR encountered an error.
("Cause" = 32-bit status from Pbt_isr_rebuild_rd).
ACTION: This error message is informational. Most likely, the
driver is already in the middle of an auto-reset for some other reason.
The driver will likely have to try another restart.
If the problem persists, there might be data corruption in the driver.
Try forcing a driver dump via the VGPBA tool and send the dump file
(NETDMP##.PUB.SYS) to Hewlett-Packard for analysis; see
Appendix A "Submitting a CR"
MESSAGE: Internal driver error.
Level: 9720 CLAS0001
CAUSE: After processing a received frame, the ISR attempted
to return a receive descriptor the rd ring but encountered an error.
("Cause" = 32-bit status from Pbt_isr_rebuild_rd).
ACTION: This error message is informational. The error
could indicate data corruption in the driver's data structures;
the driver will try to perform an internal dump and perform an auto-reset.
Check for a dump file (NETDMP##.PUB.SYS) and send to
Hewlett-Packard for analysis; see
Appendix A "Submitting a CR"
MESSAGE: Could not unmap an I/O virtual address.
Level: 9750 CLAS0001
CAUSE: Most likely during a shutdown of the driver (normal
shutdown or because of an auto-reset precipitated by an earlier
error), the ISR was attempting to release its data structures, including
previously allocated I/O virtual addresses. However, an error was
returned. ("Cause" = 16-bit SDI status
returned from Lnk_unload_io_addr).
ACTION: This error is informational. The driver will continue
to shutdown. However, if the error persists, there could be data
corruption in the driver or the I/O system. Depending on how frequently
the error is seen, or if other similar errors are noted, this may
require a system dump file to diagnose; see
Appendix A "Submitting a CR"
MESSAGE: Could not unmap and I/O virtual address.
Level: 9780 CLAS0001
CAUSE: Most likely during a shutdown of the driver (normal
shutdown or because of an auto-reset precipitated by an earlier
error), the ISR was attempting to release its data structures, including
previously allocated I/O virtual addresses. However, an error was
returned. ("Cause" = 16-bit SDI status
returned from Lnk_unload_io_addr).
ACTION: This error is informational. The driver will continue
to shutdown. However, if the error persists, there could be data
corruption in the driver or the I/O system. Depending on how frequently
the error is seen, or if other similar errors are noted, this may
require a system dump file to diagnose; see
Appendix A "Submitting a CR"
MESSAGE: Abnormal interrupts detected by adapter cards.
Level: 9810 CLAS0001
CAUSE: The adapter card generated an abnormal interrupt
that was detected by the ISR. ("Cause" = 32-bit status containing the
contents of the adapter card's status register).
ACTION: This error message is informational; the driver
may be able to continue processing and recover from the abnormal
interrupt, after updating statistics and logging the event. However,
if the problem persists, it could indicate a hardware problem on
the network or with the network configuration. The "cause" field
(adapter card status register contents) may indicate which type(s)
of abnormal condition were detected by the adapter card:
Bit 1: Transmit process stopped (this may be in response to a
specific request from the driver, depending on recent events/requests
processed by the driver).
Bit 3: Transmit jabber timeout.
Bit 5: Transmit underflow.
Bit 7: Receive buffer unavailable.
Bit 8: Receive process stopped (this may be in response to a
specific request from the driver, depending on recent events/requests
processed by the driver).
Bit 9: Receive watchdog timeout.
Bit 13: Fatal bus error.
MESSAGE: Driver encountered a software problem.
Level: 9840 CLAS0001
CAUSE: While processing a receive completion interrupt
from the adapter card, the ISR encountered an error ("Cause" = 32-bit
status from Pbt_isr_receive_frame).
ACTION: This error is informational; if possible the driver will
log the error and continue. There may be additional error information and
messages logged which provides more information about the error. The driver
may perform an auto-reset, depending on the severity of the error.
If the problem persists, try forcing a dump of the driver via the VGPBA
tool, or generating a link trace. Send any dump or trace files
(NETDMP##.PUB.SYS, NMTC###.PUB.SYS) to Hewlett-Packard
for analysis; see
Appendix A "Submitting a CR"
MESSAGE: Adapter card reported a fatal bus error.
Level: 9870 CLAS0001
CAUSE: The ISR processed an interrupt from the adapter card and
detected the fatal bus error bit was set in the card's status register.
ACTION: This is a fatal hardware error. The adapter card or system
I/O hardware may have failed. Contact your Hewlett-Packard representative
for assistance.
Complete PDF