System panics while installing 5.0MP3, during patchadd of # 122058-11.

Article:TECH69409  |  Created: 2009-01-06  |  Updated: 2011-08-08  |  Article URL http://www.symantec.com/docs/TECH69409
Article Type
Technical Solution


Environment

Issue



System panics while installing 5.0MP3, during patchadd of # 122058-11.


Solution





ISSUE:
System panics while installing 5.0MP3, during patchadd of # 122058-11. This is only applicable to Solaris 8 systems.


ERROR CODE/ MESSAGE:
Sun Mar 15 15:05:22 2009|
                    | panic[cpu22]/thread=2a100e4fd20:
Sun Mar 15 15:05:22 2009| BAD TRAP: type=31 rp=2a100e4f860 addr=3001147f300 mmu_fsr=0
Sun Mar 15 15:05:22 2009|
                    |
Sun Mar 15 15:05:22 2009| sched:
Sun Mar 15 15:05:22 2009| trap type = 0x31
Sun Mar 15 15:05:22 2009| addr=0x3001147f300
Sun Mar 15 15:05:22 2009| pid=0, pc=0x10036b64, sp=0x2a100e4f101, tstate=0x9900001600, context=0x0
Sun Mar 15 15:05:22 2009| g1-g7: 104fbc00, 0, 0, 30011474000, b300, 1f440e8, 2a100e4fd20
Sun Mar 15 15:05:22 2009|
Sun Mar 15 15:05:22 2009| 000002a100e4f470 unix:die+a4 (31, 2a100e4f860, 3001147f300, 0, 2a100e4f860, d3f21000)
Sun Mar 15 15:05:22 2009|   %l0-3: 0000000000000010 0000000000000002 0000000000000001 0000030005bbd958
                    |   %l4-7: 0000030005bbd568 0000000000000016 0000030005bbdd48 000002a10098fba0
Sun Mar 15 15:05:22 2009| 000002a100e4f550 unix:trap+900 (3001147e000, 1, 6, 0, 2a100e4f860, 0)
Sun Mar 15 15:05:22 2009|   %l0-3: 0000000000000001 000000000000079e 000000001046bd00 0000000000000000
                    |   %l4-7: 0000000000000031 0000000000000000 0000000000010200 0000030005bab4f8
Sun Mar 15 15:05:22 2009| 000002a100e4f690 unix:sfmmu_tsb_miss+66c (104b2740, 0, 30000815ef8, 0, 30000815ef8, 0)
Sun Mar 15 15:05:22 2009|   %l0-3: 0000031006438098 0000000000000000 0000000001f7b368 000003100029f7e0
                    |   %l4-7: 000003001147e000 00000000029244d8 0000000000000000 0000030011470001
Sun Mar 15 15:05:22 2009| 000002a100e4f7b0 unix:prom_rtt+0 (3001147f300, 2a100e4fd20, 1046bce0, ffffffffffffffff, 0, cd)
Sun Mar 15 15:05:22 2009|   %l0-3: 0000000000000001 0000000000001400 0000009900001600 000000001001b0f4
                    |   %l4-7: 0000000002367c28 0000030005b75528 0000000000000000 000002a100e4f860
Sun Mar 15 15:05:22 2009| 000002a100e4f900 vxdmp:dmp_get_exclusive_lock+5c (7824c638, 22f, 167, 1046bd00, 16, 0)
Sun Mar 15 15:05:22 2009|   %l0-3: 0000000010118a2c 0000000000000000 0000000000000000 000002a1004e7d20
                    |   %l4-7: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
Sun Mar 15 15:05:22 2009| 000002a100e4f9b0 vxdmp:dmp_daemons_delete_thread+4 (7824c680, 2a100e4fd20, 20, 0, 9, 9)
Sun Mar 15 15:05:22 2009|   %l0-3: 0000000000000000 000000007824c680 0000030005b75528 0000000000000640
                    |   %l4-7: 00000000000000b0 0000030005bc9558 0000000000000000 000002a100387910
Sun Mar 15 15:05:22 2009| 000002a100e4fa60 vxdmp:dmp_daemons_loop+158 (150, 7824c678, 7824bbf4, 7824c680, 7824bc18, 7824bc20)
Sun Mar 15 15:05:22 2009|   %l0-3: 000000007824bc10 000000007824bc28 000000007824bc00 000000007824bc08
                    |   %l4-7: 000000007865c6c8 0000000000000000 0000000000000000 000002a1003879c0
Sun Mar 15 15:05:22 2009|
Sun Mar 15 15:05:22 2009| syncing file systems...  


PROBLEM DESCRIPTION:
5.0MP3 (122058-11) postinstall script executes 'rem_drv vxdmp' which panics the system whilst unloading the module. Stack of 'rem_drv' command shows:

unix:panic_idle+0x1c(0x2a100f67390, 0x0, 0x30005b4f928, 0x300, 0x0, 0x0)  
unix:prom_rtt+0x0()  
-- prom_rtt regs data  rp: 0x2a100f67390  
pc:  0x10030504 unix:page_ctr_add+0x98:   add   %g4, 0x1, %g4   ( inc   %g4 )  
npc: 0x10030508 unix:page_ctr_add+0x9c:   sllx    %g4, 0x38, %g4  
global:                       %g1         0x10446c00  
   %g2             0x3a50  %g3      0x31007800000  
   %g4                0x1  %g5               0x20  
   %g6                  0  %g7      0x30010e680a0  
out:  %o0         0x10446d40  %o1         0x10446d40  
   %o2         0x10446ba8  %o3      0x31008012480  
   %o4                  0  %o5         0x10035df4  
   %sp      0x2a100f66c31  %o7         0x100304a4  
loc:  %l0         0x105cd288  %l1                  0  
   %l2      0x31006434500  %l3      0x30000815ef8  
   %l4      0x30011486000  %l5      0x3100834d580  
   %l6      0x31006434598  %l7                  0  
in:   %i0            0x1d283  %i1                0x1  
   %i2                0x9  %i3         0x10446cc8  
   %i4                0x2  %i5               0x16  
   %fp      0x2a100f66ce1  %i7         0x10030f20  
<trap>unix:page_ctr_add+0x98(0x31008335460, , , , , 0x16)  
unix:page_list_add+0x114(0x1, 0x31008335460, 0x0, , 0x10458840, 0x0)  
unix:page_free+0x438(0x31008335460, 0x0, , 0x31008335460, 0x11780, 0x30011474000)  
unix:page_destroy(, 0x0) - frame recycled  
unix:segkmem_free+0xfc(, , 0x12000)  
vxdmp:dmp_free_modules() - frame recycled                         <=== Trying to free modules  
vxdmp:_fini+0xfc(, , , 0x0, 0x0, 0x1)  
genunix:moduninstall+0xe8(, , , 0x0, 0x104fbd70, 0x104ce650)  
genunix:modunload+0x24(0xf4, , 0x20, 0xffbef4a0, 0x0, 0xa)        <=== Modunload  
genunix:modctl_modunload+0x2c(0xf4, , 0x0, 0x0, 0x0, 0x0)  
genunix:modctl+0xa4(0x1?, 0xf4, 0x1, 0x2, 0x24980, 0xffbef6b4)  
unix:syscall_trap32+0xa8()  
-- switch to user thread's user stack --  


CAUSE:
The problem is tracked via e1190516 and is targeted to be fixed in Volume Manager 5.0MP3RP2.


WORKAROUND:
Symantec support has modifed VM 5.0MP3 patch (122058-11) which would prevent similar panics on Solaris-8 systems.
Please refer to technote # TECH69476 to obtain this modified patch.
Link for the technote is available in "Related Documents" section below.


PROCEDURE TO INSTALL MODIFIED PATCH:

1) Extract original SF 5.0 MP3 package

2) Replace 122058-11.tar.gz in dvd1-sol_sparc/storage_foundation/patches with the new patch file obtained from Symantec Technical Support.

3) Follow normal installation instructions

4) Reboot the system at the end of installation.

Once VM 5.0MP3 RP2 which has the fix of 1190516 is made available, please install this patch which would prevent this panic while unloading vxdmp in Solaris 8 in future.  


REMEDY FOR PARTIALLY INSTALLED VRTSvxvm PACKAGE:

Remedy for the partially installed VRTSvxvm package caused by the system panic during the 5.0MP3 installation

If the VRTSvxvm package is in partial state with only part of the MP3 installed, please follow the below procedure to fix it.

1. Remove the following statements from the /etc/system file.

* vxvm_START (do not remove)
forceload: drv/vxdmp
forceload: drv/vxio
forceload: drv/vxspec
* vxvm_END (do not remove)

2. Create the following file to prevent VxVM from starting up during system boot.

# touch /etc/vx/reconfig.d/state.d/install-db

3. Reboot the system and make sure that the vxdmp module is not loaded.

# shutdown -i 6 -g 0 -y

After the system is rebooted, then check that the vxdmp module is not loaded.

# modinfo | grep vx

4. Remove the VRTSvxvm package

# pkgrm VRTSvxvm

5. Reinstall the VRTSvxvm package from the 5.0GA release.

# pkgadd -d . VRTSvxvm

6. Install the VRTSvxvm 5.0MP3 patch provided in this technote.

# patchadd 122058-11




 

Supplemental Materials

Value1190516
Description

System panics while unloading vxdmp on Solaris 8



Legacy ID



322815


Article URL http://www.symantec.com/docs/TECH69409


Terms of use for this information are found in Legal Notices