HP-UX 11i v3 Installation and Update Guide, September 2008 (Update 3 Release)

Table A-1 Known Install and Update Problems (continued)
Description/ActionProblem
If you attempt to dynamically unload an I/O interface device driver
assigned to a system critical resource, the unload does not succeed.
However, the driver is marked as unused and it is removed from
the kernel configuration for the next system boot. For example:
# kcmodule drivername=unused
ERROR: Unload of the module 'drivername' failed.
- Critical Usages detected for the module.
- More details can be found in /var/adm/cra.log.
NOTE: The requested changes could not be applied
to the currently running system, for the following
reasons:
- The module 'drivername' cannot support the
requested operation.
* The requested changes have been saved, and will
take effect at next boot.
What To Do
Before rebooting your system, run kcmodule -D to see what
modules will be removed at the next boot. For example:
Module State Cause Notes
drivername (now) loaded best loadable, unloadable
(next boot) unused
If the driver controls a system critical resource, run kconfig -H to
discard all changes pending for the next boot. For example:
# kconfig -H
* All changes being held for next boot have been
discarded.
# kcmodule -D
NOTE: There are no module state changes being held
for next boot.
Unloading device driver for
critical resource may cause next
system boot to fail
114 Known Problems and Troubleshooting