Setting Infiniband debug parameter ibtf_debug_buf_size to a larger value dynamically might panic the system (Doc ID 1544443.1)

Last updated on AUGUST 01, 2016

Applies to:

Solaris Operating System - Version 10 3/05 and later
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)

Symptoms

System panic due to null pointer bad trap such as

panic[cpu220]/thread=1001835d7c20: BAD TRAP: type=31 rp=2a10e551350 addr=10 mmu_fsr=0 occurred in module "genunix" due to a NULL pointer dereference

init: trap type = 0x31
addr=0x10
pid=1, pc=0x115c8fc, sp=0x2a10e550bf1, tstate=0x9980001604, context=0x2f
g1-g7: 376fe, 4001171e000, 0, 20ebf58, 0, 0, 1001835d7c20

OR

panic[cpu204]/thread=2a108e0dc60: BAD TRAP: type=31 rp=2a108e0d620 addr=0 mmu_fsr=0 occurred in module "unix" due to a NULL pointer dereference

sched: trap type = 0x31
pid=0, pc=0x1055504, sp=0x2a108e0cec1, tstate=0x4480001600, context=0x0
g1-g7: 0, 1, 0, 10018363e000, 121ff20, 1c, 2a108e0dc60


Changes

Setting ibtf_debug_buf_size dynamically using mdb -kw

# echo "ibtf_debug_buf_size/W 0x8000000" | mdb -kw

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms