Solaris 10 system running VxVM 5.0MP3RP4 PANICed with vxdmp in the stack and illegal instruction.

  • Modified Date:
  • Article ID:000010438


Solaris 10 system running VxVM 5.0MP3RP4 PANICed with vxdmp in the stack and illegal instruction.


unix:panicsys+0x48(0x109c3f0, 0x2a100b35578, 0x18baa30, 0x1, , , 0x9900001602, , , , , , , , 0x109c3f0, 0x2a100b35578)
unix:vpanic_common+0x78(0x109c3f0, 0x2a100b35578, 0x18ec800, 0x1, 0x8, 0x8)
unix:panic+0x1c(0x109c3f0, 0x10, 0x2a100b357d0, 0x600dc72ea80, 0x0, 0x0)
unix:die+0x9c(0x10, 0x2a100b357d0, 0x600dc72ea80, 0x0)
unix:trap+0x1444(0x2a100b357d0, 0x600dc72ea80)

vxdmp:dmp_process_iostatq(0x3) - frame recycled
vxdmp:dmp_daemons_loop+0x160(0x0, 0x0)



Error Message

BAD TRAP: type=10 rp=2a100b357d0 addr=600dc72ea80 mmu_fsr=0



This particular panic of the system, running Solaris 10 with Kernel patch 137137-09 on SPARC occurred due to "illegal instruction", which a hardware error. This panic was not caused by VxDMP.

If such a panic of your Solaris system occurs, please open a case with Oracle/SunW for further analysis and confirmation, as well.



Per analysis from Oracle/SunW HW Engineering, it appears that the issue is dute to  SUNW Bug ID: 6868072  <<<

Synopsis: illegal instruction or I-MMU miss panic happens instead of D-MMU miss

The symptom of this bug on a OPL box is to show as a illegal instruction fault making it looks like a possible CPU issue.

CR6868072 is fixed in 143911-01 (obsolete) and now rolled into KP142909-17 and above (current is KP144488-04).

Please contact Oracle/SunW for the above patch.

In case of a VCS cluster, please install this Oracle/SunW patch on all nodes, running Solaris 10, in a VCS cluster taking a proper action.


Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)