System panics with BAD TRAP: type=31 rp=2a10d4cf530 addr=28 mmu_fsr=0 occurred in module "gab" due to a NULL pointer dereference
Article ID: 100008760
Updated On:
Description
Error Message
BAD TRAP: type=31 rp=2a10d4cf530 addr=28 mmu_fsr=0 occurred in module "gab" due to a NULL pointer dereference
Cause
In the event of a network issue in a cluster, GAB needs to close all of its ports that are accessible to user-space and kernel-space clients. The order in which the ports close is not defined. This undefined order means that there is no check to ensure that the last port to be closed is the GAB's internal port. So, there is a possibility that the GAB's internal port may close first. And the last port to be closed is another port that may be left open for a transient period. During this period, if you try to unconfigure GAB, the unconfigure program assumes that GAB's internal port is open instead of the other port and LLT is shut down. The other port remains open. Later, whenever GAB tries to access LLT interfaces on behalf of the port that is open the system panics.
Resolution
Veritas has added an additional check in the unconfigure program to verify that last port to be closed is the GAB's internal port. If the last port is any other port, the program returns an error.
Fix included in Veritas Cluster Server 5.0 MP3 RP5 Hot Fix 1 (148477-01)
Fix will be included in 6.0.1 as well.
Applies To
Solaris 10 / VCS5.0MP3RP5
Issue/Introduction
