System Panic After Patch by using EIS

Hi,

My system go panic when I rebooted my V100 after patch it with EIS Jan 2007 version. The error show below :

panic[cpu0]/thread=30000f4dca0: BAD TRAP: type=31 rp=2a1002ff340 addr=38 mmu_fsr=0 occurred in module "genunix" due to a NULL pointer deferenceied to the system

I had search through many similar case but i couldn't get a solution for this. Please help.

[390 byte] By [Chrisya] at [2007-11-27 5:10:56]
# 1
hmm .. I manage to roll back the kernel patch 118833-36, 118833-24 then 118822-30. Finally im able to boot up my server ^^Does it mean the patches got problem ? It's working fine for me by using 118822-18 now.
Chrisya at 2007-7-12 10:31:11 > top of Java-index,Solaris Operating System,Solaris 10 Features...
# 2

The latest README for the Solaris 10 Recommended patch cluster, details complications for patch 118833-36. Lots of people are running into problems.

If you are going to try to jumbo patch again, check the special instructions:

Single-user mode, do not use the "-nosave" option, and patch a second time immediately afterwards, again in single-user mode.

cloakesa at 2007-7-12 10:31:11 > top of Java-index,Solaris Operating System,Solaris 10 Features...
# 3

I'm patch it again by take out 118833-24 , now my kernel is 118822-30, and it stuck in system boot up there T_T

strplumb: can't install module drv/dld: err -1

Booting to milestone "milestone/single-user:default".

Configuring devices

.

.

.

.

I can't even go into single user mode and normal boot >.<

Only can go alom and ok prompt. Any remedy !!

Chrisya at 2007-7-12 10:31:11 > top of Java-index,Solaris Operating System,Solaris 10 Features...