Appendix A
Fixed Issues
77
The panic message is
mutex_enter: bad mutex, ...
The panic stack will include the two
nxge
driver functions
nxge_freeb
() and
nxge_post_page
().
If such a panic occurs, the system will recover, and continue to reboot normally. The
system, including the
nxge
interfaces, will come back up with no further panics.
Workaround: Unplumb the interfaces prior to unloading the driver.
▼
To Unplumb the Interfaces Prior to Unloading the Driver
It is usually not necessary to unload a driver from a running kernel. In those rare
cases where it might be called for, you must unplumb all driver instances prior to
unloading the driver.
1. Find out which
nxge
instances are plumbed (active) using the
ifconfig
command:
2. Unplumb each active port (each port named
nxge
plus an instance number, for
example,
nxge2
,
nxge3
, . . .). Example:
#
ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL>
mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
bge0: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS>
mtu 1500 index 2
inet 129.153.54.82 netmask ffffff00 broadcast 129.153.54.255
ether 0:14:4f:2a:9f:6a
nxge2: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS>
mtu 1500 index 19
inet 129.153.54.175 netmask ffffff00 broadcast 129.153.54.255
ether 0:14:4f:6c:85:aa
nxge3: flags=201000803<UP,BROADCAST,MULTICAST,IPv4,CoS> mtu 1500
index 20
inet 129.153.54.171 netmask ffffff00 broadcast 129.153.54.255
ether 0:14:4f:6c:85:ab
#
ifconfig nxge2 unplumb
#
ifconfig nxge3 unplumb
