Customer is experiencing several crashes on his production environment. Amongst these crashes, 6 have been identified to be caused by the ConcurrentMarkSweepThread thread receiving a SIGBUS. The stack trace is identical to one in CR 4985197 (fixed in JDK 1.4.2_05).

JVM arguments used are:
-Xms2048m -Xmx2048m -Xss2m -Xoss2m -XX:PermSize=128m -XX:MaxPermSize=128m -XX:NewSize=768m -XX:MaxNewSize=768m -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:+CMSParallelRemarkEnabled -XX:MaxTenuringThreshold=8 -XX:TargetSurvivorRatio=90 -XX:SurvivorRatio=4 -XX:+UsePerfData -XX:+JavaMonitorsInStackTrace -XX:+UseLWPSynchronization -Xloggc:/wls_domains/blwls009/logs/mps/GC/managed12_blwls009_20100305014413.log -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -Dweblogic.store.MaxFileSize=400000000 -Dbt.weblogic.RootDirectory=/wls_domains/blwls009 -Dweblogic.system.BootIdentityFile=/wls_domains/blwls009/boot.properties -Dbt.weblogic.RootDirectory=/wls_domains/blwls009 -Dweblogic.Name=managed12_blwls009 -Dweblogic.ProductionModeEnabled=true -Dweblogic.management.server=http://10.75.64.76:50305 -Djava.security.policy=/opt/bea/platform/8.1sp6/weblogic81/server/lib/weblogic.policy