Hi all, not sure if you've met this one, after updating indiana to build 130, I met twice that svc.configd coredumps. Both has same stack traces.
The stack trace looks like there is an assertion being triggered and force the core dump Here is the trace: $ mdb core.svc.configd.1263057165.11 Loading modules: [ svc.configd libumem.so.1 libuutil.so.1 ld.so.1 ] > ::stack libc_hwcap1.so.1`__systemcall+6(3, fedf1b8c, 0, feee24a6) libc_hwcap1.so.1`thr_sigsetmask+0x139(2, fea7e750, 0, feee267a) libc_hwcap1.so.1`sigprocmask+0x31(2, fea7e750, 0, feeca091) libc_hwcap1.so.1`sigrelse+0x60(6, 6, fea7e7a0, fee720f8) libc_hwcap1.so.1`abort+0xb8(65737341, 6f697472, 6166206e, 64656c69, 6372203a, 746f6e5f) libc_hwcap1.so.1`_assert+0x82(80b4788, 80b477c, 501, 8101d30) rc_notify_remove_locked+0x51(830a4ac, 830a468, 893260c, feee7285) rc_notify_info_wait+0x268(8932604, 8932658, fea7eaa4, 2d0) client_wait+0x8c(89325c8, fea7edf8, 8, fea7eaa0, fea7ed90, 0) client_switcher+0x1b1(eb, fea7edf8, 8, 0, 0, 8064d9c) libc_hwcap1.so.1`__door_return+0x3e() > ::status debugging core file of svc.configd (32-bit) from xxx file: /lib/svc/bin/svc.configd initial argv: /lib/svc/bin/svc.configd threading model: native threads status: process terminated by SIGABRT (Abort), pid=11 uid=0 code=-1 panic message: Assertion failed: rc_notify_in_use == 0, file rc_node.c, line 1281 Does this look anything familiar? this is a core i7 system. Thanks Ivan. -- This message posted from opensolaris.org
